[UNOFFICIAL][DEV/GEEKS-ONLY] Cyanogenmod 9 (Android 4.0.3)[BETA4][KANG TEST BUILD]

bedman3 · Feb 5, 2012

Yes it is Chinese
The first option of the setting in labs

Sent from my ME865 using XDA App

hccompany · Feb 5, 2012

kinurabi said:
BTW after my first restart that i mentioned, the phone was lagging a looot. I had to manualy restart it to get it to normal. What I am saying is that after some usage (19 hours in my case) the phone starts lagging. Looks like some memory overflow or some kind of garbage collector is needed. I'm just sayin

Sent from my LG-P500 using XDA App

I confirm this... But not after 19 hours it happened to me after like 4 hours... And it still happens sometimes... The phone gets so laggy and becomes sooooo slow... More like unusable... Plus the previous kernel with chainfire gave me better performance than this one. I think we should fix gpu before anything else...

Sent from my LG-P500 using XDA App

gontadu · Feb 5, 2012

My phone suddenly decided to forget what google account it was linked to. Restored some settings from titanium backup and then a couple restarts later it was ok. Also every restart it forgets i have set the network to 2G only.

DroidVPN · Feb 5, 2012

I hope lupo can also compile tun.ko with his new kernel

Arjen · Feb 5, 2012

gontadu said:
My phone suddenly decided to forget what google account it was linked to. Restored some settings from titanium backup and then a couple restarts later it was ok. Also every restart it forgets i have set the network to 2G only.

Did you flash gapps before this happened?
It's the only thing I know this happens.
About forgetting the settings for 2g, guess it's linked with the cm overclock forgetting settings.
I'm putting it on the list

Ps, camera not working yet, but I made progress, camera libs are loading, but won't keep running...
So need to find out why.

Sent from my LG-P500 using XDA App

kinurabi · Feb 5, 2012

Actualy I wouldn't say it is a kernel issue. I think it is related to the ROM. This kernel is much stable and fast for me. But I would let the devs decide that. Probably they are familiar with these probs. I'm waiting for the final version, untill then ill try to help us much as I can

Sent from my LG-P500 using XDA App

visaac · Feb 5, 2012

I thought FRANCO 3.0 means kernel 3.0.
Is it not ?

d3s3rt_eagle · Feb 5, 2012

visaac said:
I thought FRANCO 3.0 means kernel 3.0.
Is it not ?

No, it's 2.6.35 with kgsl 3.0 driver ;-)

tenea · Feb 5, 2012

clem_ita said:
If I'm not wrong paolo's sources should be out there: in the discussion mentioned earlier Roqu3 says that he added some patches to paolo-kernel-v6 and successfully compiled it, so he must have got paolo sources.

The first link in quote block points to a file named kernel_2.6.35.14-V6-source.tar.gz. I don't know if these are the sources of original paolo-v6 or if they are the sources of Roqu3. In any case we can simply ask Roqu3. Probably the are paolo sources, but in any case we know what are the patches applied by Roqu3, so we can easily revert them if needed

Edit: just checked on the italian forum, PaolO-V6 sources are here http://www.multiupload.com/18Y712HS9G

Well, maybe it can be worked out for ICS compatibility

Sent from my LG-P500H using Tapatalk

visaac · Feb 5, 2012

d3s3rt_eagle said:
No, it's 2.6.35 with kgsl 3.0 driver ;-)

I feel the stock kernel was smoother
Is Kernel_KGSL_TEST_3.0 or FRANCO_3.0 better ?

papax · Feb 5, 2012

FRANCO_3.0 is more stable

yuripg1 · Feb 5, 2012

visaac said:
I feel the stock kernel was smoother
Is Kernel_KGSL_TEST_3.0 or FRANCO_3.0 better ?

I think it's because latest franco.kernel uses a touch screen driver that doesn't ramp up the CPU as much as the stock drivers from LG kernel on touch, so the rendering of scrolling and thing like that are not that smooth.

lupohirp, could you make the kernel use the stock touch driver again? (has franco kept the old code after he wrote his own driver?) This way, it would be much smoother.

Thanks anyway. Marvelous job!!!

paul678 · Feb 5, 2012

yuripg1 said:
I think it's because latest franco.kernel uses a touch screen driver that doesn't ramp up the CPU as much as the stock drivers from LG kernel on touch, so the rendering of scrolling and thing like that are not that smooth

Could you please test before asking for something..try the new kgsl franco and you will see that is not using the latest touch driver,prove me wrong

-since i'm here quick one:can you wake your phone while offline charging?i sure can't

Sent from my LG-P500 using XDA App

LastStandingDroid · Feb 5, 2012

I will flash a rom which can add and delete APN's backup all of those, and see if i can restore to ics

vlt96 · Feb 5, 2012

paul678 said:
Could you please test before asking for something..try the new kgsl franco and you will see that is not using the latest touch driver,prove me wrong
-since i'm here quick one:can you wake your phone while offline charging?i sure can't

Sent from my LG-P500 using XDA App

Franco kernel doesn't support offline charging...

paul678 · Feb 5, 2012

vlt96 said:
Franco kernel doesn't support offline charging...

Dumb me forgot it was kernel related,thanks!

Sent from my LG-P500 using XDA App

lupohirp · Feb 5, 2012

great news :

in gralloc enabled rgba in framebuffer.cpp but maybe i've fixed color banding issues

if you see in kernel /drivers/video/msm/msm_fb.c
BITS_PER_PIXEL_DEF is 16

this override my first indication in gralloc/framebuffer 'cause at hardware level set 16bpp automatically...now i'm going to set 24bpp and see what happens

ok guys situation is this

case MDP_RGB_565:
fix->type = FB_TYPE_PACKED_PIXELS;
fix->xpanstep = 1;
fix->ypanstep = 1;
var->vmode = FB_VMODE_NONINTERLACED;
var->blue.offset = 0;
var->green.offset = 5;
var->red.offset = 11;
var->blue.length = 5;
var->green.length = 6;
var->red.length = 5;
var->blue.msb_right = 0;
var->green.msb_right = 0;
var->red.msb_right = 0;
var->transp.offset = 0;
var->transp.length = 0;
bpp = 2;
break;

this is our case rgb 565....look at bpp = 2 ...at the end of cases code multiply *8 bpp 2*8 =16 bingooo!

now i'm going to set 3

yuripg1 · Feb 5, 2012

paul678 said:
Could you please test before asking for something..try the new kgsl franco and you will see that is not using the latest touch driver,prove me wrong

No need to be rude, man...

1. I am testing the beta2+franco3.0.
2. Since the FRANCO_3.0 is based on franco.kernel .35, I assumed it was using the touch driver from franco's sources.
3. I looked the last 50 posts of lupohirp and found not a single mention to reverting touch driver to stock on the FRANCO_3.0.
4. Searching for "touch" on the thread also revealed no answer to this matter.

This is a very active thread, so I may have missed something. Could you please show me where you saw it's using the stock touch driver? Thanks in advance.

Until then, I will keep thinking the FRANCO_3.0 has the rewritten touch driver by franco. Now "prove me wrong

" (if there's anybody who knows the answer, please tell us if you can

)

Snickers · Feb 5, 2012

yuripg1 said:
No need to be rude, man...

1. I am testing the beta2+franco3.0.
2. Since the FRANCO_3.0 is based on franco.kernel .35, I assumed it was using the touch driver from franco's sources.
3. I looked the last 50 posts of lupohirp and found not a single mention to reverting touch driver to stock on the FRANCO_3.0.
4. Searching for "touch" on the thread also revealed no answer to this matter.

This is a very active thread, so I may have missed something. Could you please show me where you saw it's using the stock touch driver? Thanks in advance.

Until then, I will keep thinking the FRANCO_3.0 has the rewritten touch driver by franco. Now "prove me wrong" (if there's anybody who knows the answer, please tell us if you can )

BTW guys i've no forgot you...do you want some icy biscuits to test? here the franco.kernel with KGSL 3.0 drivers! testing from this morning with overclock (played also fruit ninja seems smooth) no kernel panic! also shutdown fixed test and let me know

it was written by Lupo on page 193

k2wl · Feb 5, 2012

great..

lupohirp said:
great news :

in gralloc enabled rgba in framebuffer.cpp but maybe i've fixed color banding issues

if you see in kernel /drivers/video/msm/msm_fb.c
BITS_PER_PIXEL_DEF is 16

this override my first indication in gralloc/framebuffer 'cause at hardware level set 16bpp automatically...now i'm going to set 24bpp and see what happens

ok guys situation is this

this is our case rgb 565....look at bpp = 2 ...at the end of cases code multiply *8 bpp 2*8 =16 bingooo! now i'm going to set 3

great going..

i'm trying to port kernel 3.0 for your ICS.

hope so i'll be suceed...it will take time...as i'm no developer...just learning online and trying to help...
keep up...

[UNOFFICIAL][DEV/GEEKS-ONLY] Cyanogenmod 9 (Android 4.0.3)[BETA4][KANG TEST BUILD]

Senior Member

Senior Member

Senior Member

Senior Member

Retired Forum Moderator

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

LastStandingDroid

Guest

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts