It is perfect to use Pixel Rom 1.60 with Air Kernel v3.50. After upgraded kernel to Air Kernel v3.60, I experienced crash when using T9 dialup, and sometimes icon disappeared in desktop. But after reboot, the icon re-appeared. And I believed the system rebooted automatically at least one time in a week.
Do other users have similar problem?
(I cannot reply thread in [KERNEL] Air Kernel v3.6 [14 MAR 2012] [STABLE] [3.0.24] [SMOOTH|SPEEDY|VOODOO|MOD], so I ask here.
I agree 100%
tajtokgxt said:
It is perfect to use Pixel Rom 1.60 with Air Kernel v3.50. After upgraded kernel to Air Kernel v3.60, I experienced crash when using T9 dialup, and sometimes icon disappeared in desktop. But after reboot, the icon re-appeared. And I believed the system rebooted automatically at least one time in a week.
Do other users have similar problem?
(I cannot reply thread in [KERNEL] Air Kernel v3.6 [14 MAR 2012] [STABLE] [3.0.24] [SMOOTH|SPEEDY|VOODOO|MOD], so I ask here.
Click to expand...
Click to collapse
Air Kernel 3.5 worked fine for me on both Pixel and Gummy. But here is my misfortune: before I went to sleep, I flashed 3.6 on Gummy. I woke up and turns out it was in a never-ending boot for who knows how long? I pulled the battery and let it boot fine. Then 2 hrs later, I suffered a reboot once again. Pulled battery and so on. 2 reboots later, I had enough, and I re-flashed Pixel and 3.6. To my surprise I suffered a reboot without doing so much as clicking the browser. 1 more reboot later and I restored a Nandroid backup of Gummy and 3.5. Avoid that sh*t like the plague.
I Flashed Phone Back to Air Kernel 3.5
wolfomega23 said:
Air Kernel 3.5 worked fine for me on both Pixel and Gummy. But here is my misfortune: before I went to sleep, I flashed 3.6 on Gummy. I woke up and turns out it was in a never-ending boot for who knows how long? I pulled the battery and let it boot fine. Then 2 hrs later, I suffered a reboot once again. Pulled battery and so on. 2 reboots later, I had enough, and I re-flashed Pixel and 3.6. To my surprise I suffered a reboot without doing so much as clicking the browser. 1 more reboot later and I restored a Nandroid backup of Gummy and 3.5. Avoid that sh*t like the plague.
Click to expand...
Click to collapse
Finally I flashed the phone back to Air Kernel 3.5 and the phone works fine again. I don't know if kernel 3.0.24 in Air Kernel 3.6 has something to do with the instability, as I remember, Air Kernel 3.4 update the kernel from 3.0.22 to 3.0.23 and soon Air Kernel 3.4.5 was published with kernel reverted back to 3.0.22.
tajtokgxt said:
It is perfect to use Pixel Rom 1.60 with Air Kernel v3.50. After upgraded kernel to Air Kernel v3.60, I experienced crash when using T9 dialup, and sometimes icon disappeared in desktop. But after reboot, the icon re-appeared. And I believed the system rebooted automatically at least one time in a week.
Do other users have similar problem?
(I cannot reply thread in [KERNEL] Air Kernel v3.6 [14 MAR 2012] [STABLE] [3.0.24] [SMOOTH|SPEEDY|VOODOO|MOD], so I ask here.
Click to expand...
Click to collapse
im using pixelrom 1.6 with air kernel without problems..look what is going on..the pixel rom already have a very pushed tweaked system.flashing air kernel could cause instability..try to flash pixel rom step by step let it work for a while(without o/c) and after 5 minutes flash again the air kernel.i would suggest you to stay in normal speeds and its already very fast.no o/c no o/v!i hope all these can help you out!
In normal speed 1,000MHz already
currenter said:
im using pixelrom 1.6 with air kernel without problems..look what is going on..the pixel rom already have a very pushed tweaked system.flashing air kernel could cause instability..try to flash pixel rom step by step let it work for a while(without o/c) and after 5 minutes flash again the air kernel.i would suggest you to stay in normal speeds and its already very fast.no o/c no o/v!i hope all these can help you out!
Click to expand...
Click to collapse
I used Pixel Rom 1.60 with Air Kernel 3.5 for over a week and it worked perfect. As Air Kernel has update so I flashed the latest Air Kernel 3.6. After several days, I started to experience app crash, app icon disappearance and reboot problem. As the CPU of my phone is very weak, it will reboot even overclock to 1,100 MHz, so I set to 1,000 MHz all the time.
tajtokgxt said:
I used Pixel Rom 1.60 with Air Kernel 3.5 for over a week and it worked perfect. As Air Kernel has update so I flashed the latest Air Kernel 3.6. After several days, I started to experience app crash, app icon disappearance and reboot problem. As the CPU of my phone is very weak, it will reboot even overclock to 1,100 MHz, so I set to 1,000 MHz all the time.
Click to expand...
Click to collapse
maybe you should download again a new link for air kernel coz maybe broken.try to backup your apps and make a factory reset again.flash a new link of pixel rom let it work a little bit and flash again the air kernel.if all these doeasnt work perhaps rewind to old air kernel 3.5.im using this combination 3 days now without problem and with o/c 200-->1200 mhz.stock voltages.try to work out with NSTOOLS.i hope you figure out what is going on..
Using Air Kernel 3.5 is fine to me, waiting a more stable Air Kernel version
currenter said:
maybe you should download again a new link for air kernel coz maybe broken.try to backup your apps and make a factory reset again.flash a new link of pixel rom let it work a little bit and flash again the air kernel.if all these doeasnt work perhaps rewind to old air kernel 3.5.im using this combination 3 days now without problem and with o/c 200-->1200 mhz.stock voltages.try to work out with NSTOOLS.i hope you figure out what is going on..
Click to expand...
Click to collapse
Thanks for your suggestion.
Apart from Pixel Rom 1.6 ICS (Android 4.0.4), I have also tried nuhetri-reloaded-v2.3.0, CyberGR-MOD.NS.NGN_ver.7_Hybrid_Stormy_2_Final_ICS_ENG_crespo_signed, CyberGR-MOD.NS.NGN_ver.8_Hybrid_Stormy 3_Final_ICS_ENG_crespo_signed, Slim_ICS_crespo_v2.4, update-cm-9.0.0-RC0-NS-signed.no.v2.p1, update-cm-9.0.0-RC0-NS-signed.no.v3.p0, update-cm-9.0.0-RC0-NS-signed.no.v3.p3, update-cm-9.0.0-RC0-NS-signed.no.v3.p4, aokp_crespo_build-25, aokp_crespo_milestone-3, crespo_IMM26-v1.1.
Regarding kernel, I have tried 3.1.10_any-kernel-speedy-7, air_kernel_v2.9_voodoo_colors-05022012, air_kernel_v3.0_voodoo_colors-02102012, air_kernel_v3.1_voodoo_colors-02222012, air_kernel_v3.3_voodoo_colors-02272012 -noani, air_kernel_v3.4.5_voodoo_colors-03032012-noani-, air_kernel_v3.5_voodoo_colors-03112012-noani, air_kernel_v3.6_voodoo_colors-03142012-noani, GLaDOS-cfs-V2.10, Matr1x-cfs_v16.0, Matr1x-cfs_v16.5, Matr1x-cfs_v17.0, Matr1x-cfs_v17.5, SG-NS-ICS_05022012, SG-NS-ICS_27022012.
I use NSTools, Governor performance, min 1000MHz, max 1000Mhz. I tried to overclock, but never succeeded even slightly to 1100MHz, whether with default voltages or using 1275 mV for 1100MHz. The overclock was performed with quite a lot of combination of rom + kernel.
I just thought my phone CPU is "weak".
I flashed back to Air Kernel 3.5, it just works fine again, as if rebooting never happened before.
Try downloading the version without a boot animation. Every version of air kernel I use with a boot animation for some reason gives me revolts and bad battery life. Me personally I'm on 3.45 with the voodoo colors only version. It has been the best for me.
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (100 - Noop)
v6 Supercharged
309041291a said:
Try downloading the version without a boot animation. Every version of air kernel I use with a boot animation for some reason gives me revolts and bad battery life. Me personally I'm on 3.45 with the voodoo colors only version. It has been the best for me.
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (100 - Noop)
v6 Supercharged
Click to expand...
Click to collapse
as far as i read from air kernel post the best download link is the one with [65 Fps + Blue Colors]..im always using these updates and never had a problem..
AC 3.6 is faster but my NS froze after starting the camera app.
Returned to AC 3.4.5 and Pixel work smooth and stable again.
doa4ever said:
AC 3.6 is faster but my NS froze after starting the camera app.
Returned to AC 3.4.5 and Pixel work smooth and stable again.
Click to expand...
Click to collapse
I too, am still running 3.4.5, quick and super stable, not a reboot or any lag for days now
Sent from my Nexus S using xda premium
Curious. I have been using Pixel 1.6 with air kernel 3.6 with the same settings as the Pixel ROM developer and I have not had any issues like that. Today, my battery is being abused by way of long voice calls, emails, and posting via Tapatalk. But under normal circumstances I get 75-120 minutes of use out of 10% of the battery.
Sent from my Nexus S using Tapatalk
T9 Dialup Froze
ballroom dru said:
Curious. I have been using Pixel 1.6 with air kernel 3.6 with the same settings as the Pixel ROM developer and I have not had any issues like that. Today, my battery is being abused by way of long voice calls, emails, and posting via Tapatalk. But under normal circumstances I get 75-120 minutes of use out of 10% of the battery.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
The most weird thing is that the T9 Dialup froze after upgraded to Air Kernel 3.6. Happened at least three times. And lost app icon two times. Back to Air Kernel 3.5, it is normal again. If the T9 Dialup was not frozen, I would continue to use Air Kernel 3.6, but frozen T9 Dialup means the phone could not perform phone function ...
tajtokgxt said:
The most weird thing is that the T9 Dialup froze after upgraded to Air Kernel 3.6. Happened at least three times. And lost app icon two times. Back to Air Kernel 3.5, it is normal again. If the T9 Dialup was not frozen, I would continue to use Air Kernel 3.6, but frozen T9 Dialup means the phone could not perform phone function ...
Click to expand...
Click to collapse
Is t9 dialup an app or are you talking about the phone dialer itself?
Sent from my Nexus S using Tapatalk
T9 Dailup
ballroom dru said:
Is t9 dialup an app or are you talking about the phone dialer itself?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
It is the default phone dialer.
Related
Hello, Just thought I would post my stats using the new Starburst rom with Pershoot's Kernel. Getting great speed and the system runs very smooth but it feels like my battery is draining quite abit faster...
I have setcpu set as "OnDemand" 300mhz-1400, 256mhz when screen is off. Is this battery drain normal? Ran for 4 hours idle while working, then during break i used my tablet for about 15 min, idle another 4 hours and then after work I only got about 2 1/2 hours of use from my tablet before getting the 15% battery warning (79% to 15% in two and a half hours).
Before installing any TW rom and using Pershoot's older (non-TW) kernel with same settings I was getting atleast 4 hours after having the system idle all day while i work (10 hrs), this was with about 40%+ battery left to spare. Please take a look at my stats and feel free to give any suggestions to help me get more battery
The performance now is very good, but before TW i was getting about 150 less points in quadrant (2950ish)with the extra battery life. Also i dont let any apps run wild while idle and have gps,bluetooth,wifi turned off during working hours.
Quadrant Score, Starburst TW + Pershoot's Kernel Aug/9/2011 builds (score:3100).
http://imageshack.us/photo/my-images/842/sc20110810234001.jpg/
Battery Stats, notice the steep drop at the end? Thats the only time I really used my tablet... about 2 1/2 hours, web surfing (14 hours 35min total on battery).
http://imageshack.us/photo/my-images/707/sc20110811003248.jpg/
why is your screen on and awake bar completely full if you only used it for the last 2:30?
In GENERAL
Screen on time 8-10 hours
Standby time ~100-500 hours depending on whats on/apps installed.
No idea why it says the screen was on, it was not... And I had the unit on but as far as i know there isn't a sleep option so the unit was awake but not being used.
If you know of a sleep option please let me know, thanks for your reply
Yeah I'm still testing this exact rom/kernel combo and there is something up with it.
On a reboot, does the battery level go up? Does it stay up for a little while then drop back down?
Also have you done a battery calibration? If so, how?
I'm just trying to narrow down what could be causing the problem. I'm no dev by any stretch of the imagination, but for some reason I really want to find out what is causing this. It doesnt seem to affect all machines so in finding the simularities of those that are having this issue, we can squash this bug....
I was using this combo and my google music kept force closing.
Sent from my ADR6400L using XDA Premium App
it should goto sleep automatically, and if screen was off it should be indicated as off. maybe something is wrong. im currently on pershoot's kernel as well and have had some issues with battery calibration (reporting bogus stats).
i think pershoot is looking into the issues on his thread.
im using 10.1-Wifi, Touchwiz UX (OTA, GT-P7510)
It's a kernel problem. Try going back to stock or an older version of pershoots.
It'll be fixed today from what I've read.
Late last night reinstalled Starburst with its original rom, after my 10 hour work day it still has 95% battery left (after some galaxy on fire 2 during my break), hella lot better than it was yesterday.
I will wait for Pershoot's revised kernel and test it out again. And thanks again for all the devs making custom roms and kernels! Much love to ya! <3
*Stock Starburst kernel is showing my screen being off (when it is off) and my system as not awake when screen is off under battery usage in settings
Kayak83 said:
It'll be fixed today from what I've read.
Click to expand...
Click to collapse
From what I've read, he claims there is no problem with the kernel, the problem is with the user. We havent calibrated the battery correctly according to pershoot himself. Problem is, I cant figure out the secret to a correct calibration process....
texasredrider said:
From what I've read, he claims there is no problem with the kernel, the problem is with the user. We havent calibrated the battery correctly according to pershoot himself. Problem is, I cant figure out the secret to a correct calibration process....
Click to expand...
Click to collapse
Flash Starburst or stock rom then charge your tablet 100%, once your battery is fully charged flash Pershoot's kernel.
I have not tried this myself but from what I have read it works, right now im happy with the performance on stock Starburst kernel, quadrant is at 2300 compared to Pershoot's 3100 but its running so smooth I cannot notice the difference. Going to wait for Pershoot's reworked kernel and then flash it, I gots to have my voodoo!
Update:
Today I reset my battery, and installed Pershoot's kernel. I'm still getting battery drain, used for 5 min this morning and its down to 80% (just browsing web)... Also my clock got stuck at around 5:08am and my alarm did not work this morning until i turned my screen on. After I installed Pershoots kernel alot of apps were acting up and not running properly but after a reboot my clock and apps started working as normal.
And I have to hit/hold the power button like 5 times to turn on the unit now. Going back to original Starburst for now.
jzen said:
Flash Starburst or stock rom then charge your tablet 100%, once your battery is fully charged flash Pershoot's kernel.
I have not tried this myself but from what I have read it works, right now im happy with the performance on stock Starburst kernel, quadrant is at 2300 compared to Pershoot's 3100 but its running so smooth I cannot notice the difference. Going to wait for Pershoot's reworked kernel and then flash it, I gots to have my voodoo!
Update:
Today I reset my battery, and installed Pershoot's kernel. I'm still getting battery drain, used for 5 min this morning and its down to 80% (just browsing web)... Also my clock got stuck at around 5:08am and my alarm did not work this morning until i turned my screen on. After I installed Pershoots kernel alot of apps were acting up and not running properly but after a reboot my clock and apps started working as normal.
Click to expand...
Click to collapse
Darn. I was just about to give this a try. Oh well I'll try it anyways, nothing to lose. Just remember all the issues that may or may not be caused by the kernel is actually user error
Did anyone try the newest version of the kernel? Posted 19/aug/2011.
bambam82 said:
Did anyone try the newest version of the kernel? Posted 19/aug/2011.
Click to expand...
Click to collapse
I'm using it now & it's a very good finish product. His last version gave me battery issues like no other. I believe he withdrew it after numerous complaints over battery issues.
Working great.
I always wipe Dalvik and Cache before flashing the new kernel.
Silenus21 said:
Working great.
I always wipe Dalvik and Cache before flashing the new kernel.
Click to expand...
Click to collapse
sorry for the noob question but what does dalvik and cache contain?
Edit: Nvrmind. Found out my answer. I shall do this the next round of installing kernel
Currently I'm using Starskys Rom 1.5 and Samurai 3.01 60Hz and 250 Mhz GPU overclock.
I'm wondering what's your guys setup and do you guys get reboots and how's your battery life going? I'm asking because I'm getting terrible battery life and lag a lot even on lagfree governor sometimes, and I also do have Sony UI TSM. I average about 6 to 12 hours on battery life. Before on SRF 1.2 I average a day and a half. I had atleast 6 reboots today alone. And 2 times where my phone completly shut off on its own? I was at 24% and 3% when it happened
Sent from my SPH-D700 using xda premium
I'm glad somebody is bringing this up now due to the rapid influx of updated kernel distributions and ROMs. Personally, I've been using ACS ICS v5.5, (although I have tried out the new/latest CleanGB, Starsky, Marcusant Revival, Thunder, and Sleeper).
What has worked best on my phone so far, which is running an EI22 modem is:
ACS ICS v5.5 + Samurai v2.0.6 (when running the default governor and no changes).
I would LOVE to have a newer, stable ROM that handles Samurai v3.0.1.
Here are my general observations on ACS ICS v5.5 + Samurai kernels... (just some thoughts)...
The sad thing is that I'm not really sure what the *&#^ is going on with all of the new releases of Samurai kernel and how they are or are not compatible with ACS ICS v5.5. I don't overclock, and I haven't had any glitches or bumps with running the Samurai v2.0.6 kernel, but it was pulled from the Samurai distribution post thread... I've searched that thing by hand and run a search and can't seem to find out why the download link isn't still available or if anybody else has had instability problems with it. The initial compilation of v2.0.8 caused lag and instability in my system, (yes, I did a factory clear, installed the rom, then installed the kernel before boot loading).
I am running kernel v3.0.1 Samurai ALL STOCK right now, and I still think it's inferior in general performance and stability compared with v2.0.6 on ACS ICS v5.5. One example is battery performance after a full clear of battery stats, a battery drain and reset (again), full charge, and then testing to see how long it performs during the day. v2.0.6 doesn't give me any weird battery charge artifacts (or hysteresis-like behaviour, whereas v3.0.1 does... including stalled battery monitor stats or increasing battery monitor stats over the period of 10-30 minutes of general SMS usage). Also, the battery monitor increases routinely by 20% when unplugged and reboot. Ex., I reboot at 48% charge and it boots up and is at 68%.
I'm running the newest cm7 build with 0 reboots. I use my phone heavily and today I squeezed 14 hours on the battery without calibration. If I left the phone alone all day, who knows how long I could make the batt last.
Sent from my SPH-D700 using XDA App
I was on cm7 until today, I've been rocking Urban Precision and the ShadowKernel and loving it
Sent from my SPH-D700 using XDA Premium App
I'm running ACS 5.5 with samurai 1.2.1. I tried 3.0.0 and 3.0.1 and had similar with lagging so I went back to what I had before. Reboots are not a problem for me. I am a heavy user running Pandora/Bluetooth all day so batttery life is horrible anyway. If I take it easy, 1 day is no problem on the battery.
Sent from my SPH-D700 using XDA App
yep same here I'm running ACS ICS v5 with samurai_gen 1.2 Kernel I use my gps all the time and music and battery life is okay I get 10 hrs a day? everything works great for me no lag speed is great no more random reboots whatsoever.for me works great.
Sent from my SPH-D700 using XDA App_
Legendary 2.1 with 3.0.1++ (300mhz gpu) Using shake and bake theme never had a reboot yet since flashing when the two came available.... battery life is great now that I've calibrated it in low signal areas yesterday. Ill post screens. I think legendary seems to be the best for me. I think you'll find just as good.
Oh and the smartbench is 2011 on 2010 I got 1700/4200.
Sent from my OG Epic
Jeeez guys. Acs ics is outdated...
Sent from my SPH-D700 using XDA App
Im Running 2.2
But its in my sig
i dont think im switchin 2 GB just not happy with it
i think imma wait until a new phone so i have no choice. lol
but good work on the roms im jus picky
Legendary 2.1, Shadow Kernel. Have yet to have a reboot on GB even when using all versions of Samurai. Switched because I reformatted my sd card and it started to lag on Samurai 2.0.8 and be generally flaky. Shadow has solved it. May be completely my own fault and didn't feel like troubleshooting.
Miui with stock mtd kernel
Sent from my SPH-D700 using Tapatalk
ERA RC2 (not 2.1) with the ShadowKernel. No reboots, quick, seems to be a good combo for me. No undervolting, slight OC to 1100mhz. I'm more about stability and reliability than super-awesome-fast-lighting-quick-ness. Battery life seems good, pretty on par with most other things, slightly better if anything. I don't castrate my phone so data is always on unless I'm in a bad signal area in which case I'll turn it off or the battery will get eaten alive.
marcusant said:
Jeeez guys. Acs ics is outdated...
Click to expand...
Click to collapse
LOL! So true!
That being said, if you can tell me what new and wonderful improvements any other ROMs have made since you worked on v5.5, then I'm all ears and will gladly download them! Remember, I don't overclock.
(Oh, and I loved Revival... but for some reason my dumb *&# can't get the battery meter to display. Yes, it's a personal problem and I will figure it out someday).
Your friendly, neighborhood Lagomorph,
--SN
Cm7. Zero reboots. Amazing battery.
Sent from my SPH-D700 using xda premium
omair2005 said:
Miui with stock mtd kernel
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
This.....Its a beautiful thing!
Sent from my SPH-D700 using XDA App
starskyrob said:
Cm7. Zero reboots. Amazing battery.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I need 911 though i mean if anything ever were to happen i like the safeness. and seems to still have a lot of bugs still that im still waiting on to be fixed? sorry but but when is your 1.6 Coming out anytime this week?
kernel version 2.6.35.8-LoStKernelExp+
Build Number StarBurst11.13.11 v1.9.8r
1 reboot a day, due to los daemon
Great battery life.
Using Revival V1, and Shadow V1.0.1+OC, I haven't gotten a reboot on this since I removed the lock mod. Running great.
My phone had issues with The samuri Kernel's after 2.0.4, kept doing strange things after 12+ hours of uptime. It would lag badly for no reason. A reset would fix it, but I didn't like it.
The only problem I have with this setup is running the stock browser will cause the phone to lockup and reset.
badkarmah187 said:
kernel version 2.6.35.8-LoStKernelExp+
Build Number StarBurst11.13.11 v1.9.8r
1 reboot a day, due to los daemon
Great battery life.
Click to expand...
Click to collapse
Wrong phone.
Sent from my SPH-D700 using XDA App
Updated
My own custom built rom
Shadow Kernel v1.0.2+ OC
Frequencies -
200, 400, 800, 1000, 1200 all UV -50
IO Scheduler -
Noop
CPU Govenor -
Smartass v2
Voodoo Color Settings -
Gamma table voodoo profile v1
Screen colors multipliers
Red = 164
Green = 214
Blue = 264
Screen v1 gamma hack
Red = -30
Green = -20
Blue = -10
Brightness set to 25%
Theme -
ICS Lockmod 2.1
Launcher -
ADW EX
No reboots, lag, or issues of any kind whatsoever. Fair battery life, 10hrs+ with very heavy usage.
Sent from my SPH-D700 using Tapatalk
Hello,
from yesterday are available version version cm 10.1 monthly.
here limks:
http://get.cm/?device=crespo&type=snapshot
http://get.cm/?device=crespo4g&type=snapshot
*Delete
Sent from my Baked Nexus S using Tapatalk 2
ops...where is it?
*Delete
Sent from my Baked Nexus S using Tapatalk 2
Are different release!!!
monthly are between nightly and stable version!
ziociccio said:
Are different release!!!
monthly are between nightly and stable version!
Click to expand...
Click to collapse
Oops. I read nightly in your title.
Sent from my Baked Nexus S using Tapatalk 2
I couldn't click anything in the dock when i installed this yesterday? Was a clean install.
Edit: Just had to update Nova and it's fine.
R: [ROM][4.2.1] Official Cm10.1 monthly for Nexus S & Nexus S 4G
any feedback?
i flashed this rom over xylon rom,based on cm10.1
no issue or problem.
I'm on this ROM from yesterday (full wipe), with stock CM kernel.. no issues so far.. Only one Trebuchet FC, but probably was my fault..
BatteryLife seems normal, no drain etc..
Everything work good, and smooth enough for a 4.2 rom.. but too many animation ...
I give you some feedback using this ROM as my daily driver..
Put the M release on last night. Using marmite 7.2.3. Works well, smooth and battery life seems ok.
Installed it straight over the top of the CM 10.1 nightly i was on.
Will try marmite 7.3 sometime soon, but had a few issues with that for battery life on the recent nightlies.
Many thanks for this ROM CM people.
Just as an aside, i had a horrible time with the phone over the last few days. Not sur what happened but it wouldn't boot past the bootloader, and somehow i lost the recovery (TWRP). Had to go back to the factory 4.1 version and rebuild the lot from there. Then it all happened again.
Finally worked out why, apart from me being an idiot. I had used Titanium Backup to load apps and settings back after an update, and they were backups of 4.2 apps, not 4.1. So, rebuilt from scratch on 4.1, got a nandroid backup of that. then built from scratch on a CM10.1 nightly from December that i knew was good and reinstalled all apps and settings manually. Much cursing and gnashing of teeth.
battery drain is very very slow.
I lost only 2% after 9h in stand-by mode. with others roms ithe minimun was 6%.
Keep in mind that this is the first 4.2 ROM i've installed:
I'm facing the AndroidOS 50% battery drain sometimes... Yesterday this value was 45-50%; today, after a full charge and a reboot, the value is 7-10% (Stock CM Kernel)..
I've noticed that even with other ROMs and Kernels on 4.1.. probably it is related to apps installation and first launch.. so not a real issues...
Two minor "aesthetic-personal-issues":
- "clear all recent apps" is in the top-right corner, totally invisible when more than 3 apps are running, hope CM team will set it on the top left or leave the decision to user...
- sometimes is hard to know if some "toggle" in user bar are ON, OFF or inactive (like WiFi On but not connected, Gps etc).. probably this needs some work2do to clarify the behaviour of this tiles... or maybe it is just personal taste...
And I hope that in future they add the option to set 4 or 5 tiles per rows in user bar...
Battery life is not different from CM10 or other 4.1 ROMs...
I just had a literal nightmare with this rom. While I was just swiping through the desktop with the phone charging suddenly everything started to black out. What was scary was how gradual it was happening i almost thought my phone is going to explode now or something lol. Didn't help the fact that I was using the phone at night in pitch darkness.
Took out the battery immediately and rebooted just fine for now. I updated from cm 10 stable without wipe as i was prompted for an ota update.
Sent from my Nexus S using xda app-developers app
Gambler_3 said:
.....While I was just swiping through the desktop with the phone charging suddenly everything started to black out...
Click to expand...
Click to collapse
same happened to me, but without the charger and stock CM kernel... Now I'm testing Marmite 7.3 and everything work good...
I think that this is related to some background operation that slow down the device..
Currently running PA 3.99 RC1. Used Franco kernel Linaro first, used the regular Franco Kernel today for a bit.
When I flashed PA first, I used the normal .84 radio of course. As I've seen that many had a problem with this radio with an MVNO (I use Mobile Vikings in the Netherlands, which is an MVNO from KPN), it would drain battery life immensely.
So I flashed the .48 radio (the android 4.2.2 one) back since yesterday. Didn't help so it seems.
I've had one train trip of an hour draining the battery from 80% to 20%. I had to recharge the phone in college with my external battery (which was only 2h long), up to 50% again, only to use it back in the train where I had to hook it up again to the external battery.
Wakelocks are PowerManagerService.Wakelocks (30%) and msim_hsic_host (for 11.8%)(<- although I have seen this on top at 20% too).
It's obviously only when connecting to new 3G poles, but come on. I can't use a new nexus 4 like this if it drains from 80 to 20% in one hour on the train. My old Galaxy S I9000 only spent a small 20% on that trip, and that phone was 2,5y old! (and a 1500 mhz battery).
What do I need to do to get my new phone to an acceptable level? What radio, kernel,...? Do I need to do a full factory reset for it to work? (I did wiped cache and dalvik cache in between the flashing above though)....
(Also, the phone gets really hot at times, I'm almost burning my finger! System monitor reports a max of 54C, but Franko Updater app status gives 70C. Don't know what to believe. I guess this is in line with the problems above though).
Svardskampe said:
Currently running PA 3.99 RC1. Used Franco kernel Linaro first, used the regular Franco Kernel today for a bit.
When I flashed PA first, I used the normal .84 radio of course. As I've seen that many had a problem with this radio with an MVNO (I use Mobile Vikings in the Netherlands, which is an MVNO from KPN), it would drain battery life immensely.
So I flashed the .48 radio (the android 4.2.2 one) back since yesterday. Didn't help so it seems.
I've had one train trip of an hour draining the battery from 80% to 20%. I had to recharge the phone in college with my external battery (which was only 2h long), up to 50% again, only to use it back in the train where I had to hook it up again to the external battery.
Wakelocks are PowerManagerService.Wakelocks (30%) and msim_hsic_host (for 11.8%)(<- although I have seen this on top at 20% too).
It's obviously only when connecting to new 3G poles, but come on. I can't use a new nexus 4 like this if it drains from 80 to 20% in one hour on the train. My old Galaxy S I9000 only spent a small 20% on that trip, and that phone was 2,5y old! (and a 1500 mhz battery).
What do I need to do to get my new phone to an acceptable level? What radio, kernel,...? Do I need to do a full factory reset for it to work? (I did wiped cache and dalvik cache in between the flashing above though)....
(Also, the phone gets really hot at times, I'm almost burning my finger! System monitor reports a max of 54C, but Franko Updater app status gives 70C. Don't know what to believe. I guess this is in line with the problems above though).
Click to expand...
Click to collapse
try a different kernel. ive heard/read many reports of franco kernel not being very battery friendly as of recently http://forum.xda-developers.com/showthread.php?t=2449982
Depending on how long you have the phone you probably want to replace the battery with a new one (although its probably hard to find a reliable battery that isn't used or fake capacity.)
My settings:
-Neo kernel: CPU 192MHz-1350MHz ondemand. GPU 320MHz ondemand.
-Manually disable data/wifi/gps/syncing and use lower brightness whenever I can.
-Use Greenify app to disable apps from autostarting.
Otherwise no other fancy stuff. I can get up to 4hours of screen on time.
simms22 said:
try a different kernel. ive heard/read many reports of franco kernel not being very battery friendly as of recently http://forum.xda-developers.com/showthread.php?t=2449982
Click to expand...
Click to collapse
Thanks for the link, will try Trinity TF4H then as that seem to be the best from the test, and features color correction like franco's (I like a little bit of saturation)
eksasol said:
Depending on how long you have the phone you probably want to replace the battery with a new one (although its probably hard to find a reliable battery that isn't used or fake capacity.)
My settings:
-Neo kernel: CPU 192MHz-1350MHz ondemand. GPU 320MHz ondemand.
-Manually disable data/wifi/gps/syncing and use lower brightness whenever I can.
-Use Greenify app to disable apps from autostarting.
Otherwise no other fancy stuff. I can get up to 4hours of screen on time.
Click to expand...
Click to collapse
As I see in the benchmark topic they are going to test Neo, I'll wait that out first. As from the OP; it's a new phone. Have it just since this month, got it in the sales lately. Screen backlight was off during the entire day, and I do use greenify.
Svardskampe said:
Thanks for the link, will try Trinity TF4H then ase seem to be the best from the test, and features color correction like franco's (I like a little bit of saturation)
As I see in the benchmark topic they are going to test Neo, I'll wait that out first. As from the OP; it's a new phone. Have it just since this month, got it in the sales lately. Screen backlight was off during the entire day, and I do use greenify.
Click to expand...
Click to collapse
trinity doesnt feature color correction like francos, it doesn't include gamma editing. you can edit the red/green/blue however. there is a newer release of trinity though, if you want that one instead, tf5zeta http://goo.gl/wxnAfy
when flashing trinity, dont wipe anything, not dalvik, not cache. just flash it
I would say flash hells-core b38. You can also change color presets with trickstermod from playstore.
I use purity rom with hells kernel and got amazing sot times. Mostly between 4 a 5 hours.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Unjustable said:
I would say flash hells-core b38. You can also change color presets with trickstermod from playstore.
I use purity rom with hells kernel and got amazing sot times. Mostly between 4 a 5 hours.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+:good:
Unjustable said:
I would say flash hells-core b38. You can also change color presets with trickstermod from playstore.
I use purity rom with hells kernel and got amazing sot times. Mostly between 4 a 5 hours.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do u custom your kernel setting, or it's come with the kernel already? I used it once back in b37 but only got 2-3 hours SOT from full charge drain out to around 30% batt
As for updates on this topic:
Currently running PA with Trinity. As for real test goes in the wild, we'll have to wait till monday at least , but so far looking incredibly promising. 3H screen on time when playing ingress, so continuous GPS location on, GPU working, changing network poles, internet, and I don't have LTE so everything over 3G/HDSPA and screen is only responsible for 33% used. Patch is necessary for running JSS kernels on JWR roms.
Trinity kernel topic: http://forum.xda-developers.com/showthread.php?t=2083904
The patch: https://drive.google.com/?usp=folder&authuser=0#folders/0B_2NNDoNW6ejTWhKR0ZUZUZrNHM
1. Flash PA first, and PA gapps. Let it boot.
2. Back in recovery, flash the kernel
3. flash the patch for JSS kernels on JWR roms.
Don't wipe anything in between in terms of cache or dalvik cache. (it's an anykernel kernel).
Only real downside is still the saturation. EDIT: added in TF11
I also have the problem my GPS couldn't find a fix. Installing GPS status and toolbox along seems to bring the fix time down to a minute.
https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
I have tested many kernels with stock rom KOT49H such as: franco, matr1x, hellcores, helldoctors, bricked but dt2w feature sometimes doesn't work when I put my nexus 4 in pocket for a long time (I must press volume or power button to make it works again). An other case lockscreen becomes unreponsive when receiving an incoming call (or put in pocket for a long time), I can't do anything except turn off my phone!
My battery is not good as I expect. It drain 1.5% per hour in idle mode (turn off all connection).
Can someone tell me about the best kernel for my problems? Thank you!
nguyenhaiphuc said:
I have tested many kernels with stock rom KOT49H such as: franco, matr1x, hellcores, helldoctors, bricked but dt2w feature sometimes doesn't work when I put my nexus 4 in pocket for a long time (I must press volume or power button to make it works again). An other case lockscreen becomes unreponsive when receiving an incoming call (or put in pocket for a long time), I can't do anything except turn off my phone!
My battery is not good as I expect. It drain 1.5% per hour in idle mode (turn off all connection).
Can someone tell me about the best kernel for my problems? Thank you!
Click to expand...
Click to collapse
Dt2w is buggy(as always have been) so you have to wait for the fix.For now I personally recommend stock kernel.If you tried those kernel you should give stock a shot.
Try out touch control. Has dt2w, and is much stabler IMO
I tested the touch control with franco and stock kernel modify but the same problem^^
Then maybe switch to s2w?
I have tried most of the kernels that you mentioned and s2w works great with or without touch control.
Unleashed by my Nexus 4
I'd suggest that you use the Semaphore kernel. I switched to it for the very same reason, and ever since, I haven't had a single issue with its DT2W feature. And in the unlikely event that you run into one, the developer has added a fail-safe trigger to reset the touchscreen (tap on the screen with more than 3 fingers). In addition to the above, the kernel's pretty much well-rounded with features. And the developer is a well-spoken bloke too.
Try semaphore you won't be sorry.
Sent from my Nexus 4 using Tapatalk
yak84 said:
Try semaphore you won't be sorry.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I'm using matr1x kernel and having the same issue, seems that you saved me a lot of time, I was about to try a lot of kernels to see if I can get a better dt2w implementation. I think I'm gonna skip to Semaphore and see what happens.
jjforums said:
I'm using matr1x kernel and having the same issue, seems that you saved me a lot of time, I was about to try a lot of kernels to see if I can get a better dt2w implementation. I think I'm gonna skip to Semaphore and see what happens.
Click to expand...
Click to collapse
Also Hell core kernel has excellent dt2w and now it's the only supported (no more s2w).
RASTAVIPER said:
Also Hell core kernel has excellent dt2w and now it's the only supported (no more s2w).
Click to expand...
Click to collapse
No issues at all? The OP said he tried hellscore and was the same as matr1x when it comes to dt2w.
jjforums said:
No issues at all? The OP said he tried hellscore and was the same as matr1x when it comes to dt2w.
Click to expand...
Click to collapse
This post is like 7 months old.
Since then there must have been over 15 newer versions for each kernel.
So, no comparison between what was happening then with current situation.
RASTAVIPER said:
This post is like 7 months old.
Since then there must have been over 15 newer versions for each kernel.
So, no comparison between what was happening then with current situation.
Click to expand...
Click to collapse
I can say that, at least on matr1x kernel, I have the same issue with the current version.
If I'm not mistaken, both the newer (after b47) HellsCore and Matr1x both use stratosk's dt2w. I've been using on HellsCore, and it works great. Much better than the earlier implementation of dt2w, which would turn the phone on inside my pocket constantly. stratosk's dt2w though is very specific to the center of the screen, and works great.
HellsCore is renowned for great battery life. But it's up to you to test for yourself, and to try different settings to see what works best for you, considering how you use your phone.
Planterz said:
If I'm not mistaken, both the newer (after b47) HellsCore and Matr1x both use stratosk's dt2w. I've been using on HellsCore, and it works great. Much better than the earlier implementation of dt2w, which would turn the phone on inside my pocket constantly. stratosk's dt2w though is very specific to the center of the screen, and works great.
HellsCore is renowned for great battery life. But it's up to you to test for yourself, and to try different settings to see what works best for you, considering how you use your phone.
Click to expand...
Click to collapse
This is what I use with Matr1x, problem is not phone waking in my pocket, is that sometimes, it doesn't wake at wall using dt2w, I have to use power button, then it start working again.
But I'm gonna try for some more days, then I decide what to do.
Hellscore b47 or the newest version: b57 :3 don't use this 3rd party apps cuz it will drain ur battery very fast. 3rd party apps use module instead of tweak, so it's so bad
i would sugest this one.
http://forum.xda-developers.com/showthread.php?t=2845768