[KERNEL][STOCK/CM10][ALL MDPI] nAa's 3.x eXtend [20130926]

kakarotdroid

Senior Member
May 9, 2013
91
22
0
kollam
One small cause for concern. Does the kernel affect charging speed?
Plugged in for half an hour and charged up by 3%
88-91 in 32 minutes
Usually it would have reached 96-98%
Connected to wall port or charger itself
No wifi or data enabled
GPS disabled
In 2g
Power master point at 98
All applications turned off

Its charging as if it is connected to a pc

Am I the only one facing this?



Sent from my WT19i using xda app-developers app
 

mdfzhi

Senior Member
Jun 15, 2011
4,148
3,853
0
One small cause for concern. Does the kernel affect charging speed?
Plugged in for half an hour and charged up by 3%
88-91 in 32 minutes
Usually it would have reached 96-98%
Connected to wall port or charger itself
No wifi or data enabled
GPS disabled
In 2g
Power master point at 98
All applications turned off

Its charging as if it is connected to a pc

Am I the only one facing this?



Sent from my WT19i using xda app-developers app
Doesn't really understand what you're asking, whether charging is too slow or too fast, but either way, battery reading really is buggy in kernel 3.4. Sometime it'll just stuck at one random level and won't change until reboot.
 

kakarotdroid

Senior Member
May 9, 2013
91
22
0
kollam
Doesn't really understand what you're asking, whether charging is too slow or too fast, but either way, battery reading really is buggy in kernel 3.4. Sometime it'll just stuck at one random level and won't change until reboot.
Battery charging is too slow.

But since you pointed out that battery reading could be stuck, I'll check it and pm you.

Sent from my WT19i using xda app-developers app
 

Mysteryagr

Recognized Developer / Recognized Contributor
Aug 16, 2012
3,085
1,330
253
Cairo
Battery charging is too slow.

But since you pointed out that battery reading could be stuck, I'll check it and pm you.

Sent from my WT19i using xda app-developers app
I'm sure 99% that battery reading is stuck.
isn't that a known issue?
anw. you can try to unplug the charger and wait few min. then plug it again, or reboot the device to get the Correct reading.
 

january73

Senior Member
Jan 30, 2009
139
69
58
For Active last version (20130616) - all is working exsept FM Radio (rom MIUI v5 3.6.7). Older version recowery not working (error backup), now working.
 

parid_hilton

Senior Member
Nov 27, 2012
82
7
0
Hi!,i face random reboot on build 616,buid 613 more stable for me!.i'm on cm10 m66b.

sorry for my bad english,I'mjowo tulen!
 
Last edited:

Mysteryagr

Recognized Developer / Recognized Contributor
Aug 16, 2012
3,085
1,330
253
Cairo
Hi!,i face random reboot on build 616,buid 613 more stable for me!.i'm on cm10 m66b.

sorry for my bad english,I'mjowo tulen!
Build 16 is more stable than 13 for me.
But you know, Random reboots exist in the base kernel, so it is also there in every extended update.

Sent from my ST15i using xda app-developers app
 

mdfzhi

Senior Member
Jun 15, 2011
4,148
3,853
0
so anyone with reboot actually bother to upload logs? most important is /proc/last_kmsg after the reboot.

i've seen many, many, many reports in naa original thread, in all rom thread that uses naa 3.x kernel like mike's and pcfighter's, but no one seems bother to upload any logs at all.

anyway, the reboot doesn't happen to me in case anyone wanna ask me back why can't i get the logs myself.
 
Last edited:

parid_hilton

Senior Member
Nov 27, 2012
82
7
0
so anyone with reboot actually bother to upload logs? most important is /proc/last_kmsg after the reboot.

i've seen many, many, many reports in naa original thread, in all rom thread that uses naa 3.x kernel like mike's and pcfighter's, but no one seems bother to upload any logs at all.

anyway, the reboot doesn't happen to me in case anyone wanna ask me back why can't i get the logs myself.
This? https://www.box.com/shared/6slmx0es6lrnqxkvwcdg

sorry for my bad english,I'mjowo tulen!
 
  • Like
Reactions: mdfzhi

mdfzhi

Senior Member
Jun 15, 2011
4,148
3,853
0
This? https://www.box.com/shared/6slmx0es6lrnqxkvwcdg

sorry for my bad english,I'mjowo tulen!
thanks.
that looks like the classic case of kernel panic due to wifi interrupt. strange that it never happen to me. probably it got something to do with router configuration.

but still, keep them logs coming. i need to see if reboot also cause by low pmem_sf memory
https://github.com/M66B/cm-xtended/issues/94

and if it is, probably raising the amount would resolve it.
 
Last edited: