Currently I am using Endymion as the stable ROM on my device and I am pretty happy with its performance as well as the battery life, except for some random reboots.
But because of the limitations on some apps on Play store, which are not compatible on gingerbread, I wanted to try some JB roms.
With the andromadus builds (I know they are betas, but still many people say they are good for them, even if not for permanent usage at the current stage of developments), I have two issues:
1. My workplace wifi has wpa2 encryption with static ip addresses. And with both Flinny's and nk111's builds, both the latest and the ones prior to them, I cannot connect to the wifi despite several attempts. Though, my home wifi connection, which uses Auto-settings (with wpa2 encryption), the connection is almost instant. Is there any remedy for that or am i doing something wrong. Also, with few newer Sense ROMs like Fallout 5 and Sabsa 8.5, wifi has never given me problem.
2. Also, with those builds, I have severe graphical glitches with the default settings. I tried to toggle the hardware acceleration overlay in settings, but no success. The graphical glitches are in the form of suspension of the phone, and only when I touch the screen, the process goes forward. In other words, if I have to type 'abc' on the keyboard, after I press 'a', the phone stops, and only when I press 'b', the 'a' appears, and so on. I hope I am able to convey the issue. Is this problem common or only I am affected by it.
For flashing, I first do a complete wipe (Format all except sdcard option in 4ext Recovery), then flash the .zip and then the gapps followed by Fix permissions. But the problems start from the first boot itself. I have tried 5-6 times, but things remain like this.
I do have S-off, with eng hboot of 0.98.2000, and I had applied the latest radio 20.76.30.0835U_3831.19.00.110.
Thanks in advance.
Hi I'm using viper Rom saga1.0 it is Android 4.04 it's been running very smoothly and hasn't had any graphical glitches. I highly recommend it. Try it out and see if it fixes those problems for you.
Sent from my HTC Desire S using xda premium
ben_s247 said:
Hi I'm using viper Rom saga1.0 it is Android 4.04 it's been running very smoothly and hasn't had any graphical glitches. I highly recommend it. Try it out and see if it fixes those problems for you.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Thanks for the answer.
I have tried out a few ics roms, namely fallout, iceds and sabsa, all of which work well and smooth without the two issues I have pointed out in the experimental jb roms. Except for endymion, all other roms give me serious battery drainage.
Eg, in endymion, the phone goes into deep sleep, with no change in the battery percent indicator overnight.
While with reaper (smooth, but overnight it goes from 100 to 45%), with ics roms (again smooth, but overnight battery goes from 100 to 0, and phone shuts off). In all cases the battery usage culprit comes out to be Android OS. I have tried the latest amidabuddha kernels too, but same result. All testing done using default Rom settings and the settings of my normal endy tweaks (245-1024, ondemand, noop, with low manual brightness, WiFi/data off, sim on).
It seems like my phone remains to be married to endymion.
Sent from my HTC Desire S using xda app-developers app
if thats what you need something to work for days on end with out charge personally i havn't had that same battery drain issue with this rom but it would not last two days. Any way If your happy I'm happy.
ben_s247 said:
if thats what you need something to work for days on end with out charge personally i havn't had that same battery drain issue with this rom but it would not last two days. Any way If your happy I'm happy.
Click to expand...
Click to collapse
I will tell you after I use Vipersaga.
WiFi doesn't work in latest(2012-12-06) build of NK111...I just tryed a clean install but it doesn't switch on!
I roll back to nk111 2012-11-16 and it goes well...Andromadus CM 10.1 boot but crashes phone app..
reo_sam said:
Thanks for the answer.
I have tried out a few ics roms, namely fallout, iceds and sabsa, all of which work well and smooth without the two issues I have pointed out in the experimental jb roms. Except for endymion, all other roms give me serious battery drainage.
Eg, in endymion, the phone goes into deep sleep, with no change in the battery percent indicator overnight.
While with reaper (smooth, but overnight it goes from 100 to 45%), with ics roms (again smooth, but overnight battery goes from 100 to 0, and phone shuts off). In all cases the battery usage culprit comes out to be Android OS. I have tried the latest amidabuddha kernels too, but same result. All testing done using default Rom settings and the settings of my normal endy tweaks (245-1024, ondemand, noop, with low manual brightness, WiFi/data off, sim on).
It seems like my phone remains to be married to endymion.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Well i think you're battery is dying. i never had a 100%-0% draining in any rom i tested.
Have a look on Betterbatterystats here on xda to find which app is misbehaving. There are a lot of reasons which can cause this high drainage. Upload BBS logs after the night and we'll know more.
---------- Post added at 08:01 AM ---------- Previous post was at 07:54 AM ----------
Changed my IP settings to static on home router (WPA2) and connection works. Aren't you using MAC filtering at work?
Jelly Bean isn't stable enough for desire s.
personally, i think ICS is the ultimate ROM we can try on this device.
jjeeff1013 said:
Jelly Bean isn't stable enough for desire s.
personally, i think ICS is the ultimate ROM we can try on this device.
Click to expand...
Click to collapse
What are your reasons for thinking that? Have you even tried jb? It's working better now than ics (cm/aosp). Apart from the non-sony panels...
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
TheLegendGZ said:
WiFi doesn't work in latest(2012-12-06) build of NK111...I just tryed a clean install but it doesn't switch on!
I roll back to nk111 2012-11-16 and it goes well...Andromadus CM 10.1 boot but crashes phone app..
Click to expand...
Click to collapse
Have you flashed the boot.img of the new version?
Yes of course i've flashed the boot img...
But i think it's an ADB compatibility problems with Windows 8...Now i change the HDD and i retry with Win 7!
Edit: Now It works fine..Gallery settings still doesn't load!
Related
Hey guys,
The topic of this thread has change slightly since I started it. Please disregard the first few posts after this one.
The problem is that when I install a new ROM, it works perfectly for an hour or perhaps even the day, and then I start getting random shutdowns. These seem to start out of the blue and I cant work it out.
When installing a new ROM, I always check the MD5 and perform a superwipe before starting to use the ROM. Ill put back a few apps using titanium backup pro.
I don't use any hacked apps or task killers.
I have searched but cant find anything useful.
Currently using Insertcoin Sense 4 RC5. Firmware 3.32.
I have tried three different kernals (Bricked, Sebastian and RCMix), all with the same problem.
Update: tjamaican has kindly sent me a fix he found of the forums, its for a battery fix that worked for me on insertcoin's ICS Sense 4 RC4.1 ROM. However I have just moved to RC5 and the problem is back even with the fix.
http://www.mediafire.com/?2a8837bcatym1ju
I am going to try and set a lower CPU level, already down to 1.2 Ghz with max screen off at ~500Mhz. Seems stable for now, been running 24hrs - no restarts.
This is interesting because I had a GB Rom running at 1.5Ghz with no problems, maybe its something to do with ICS.
Any ideas?
[SOLVED]
Sent the phone off to htc and they have replaced the motherboard. Its all fine and dandy now!
They dont know why it happened or how to avoid it in the future...useful, but if you're still in warranty then send it off, it took exactly a week to get back to me (Monday to Monday). Good luck!
Max
Well no need for factory reset. Superwipe? Yes.
What roms cause this?
What firmware is ur senny on? Ex: 1.17? 3.24?
Phone have physical damage?
Has it been wet?
Sent From Space Using My ICS Flavored Sensation
Thanks for your reply.
No, the phone is basically new, but as I said this has happened before.
Running this ROM on 3.24:
http://forum.xda-developers.com/showthread.php?t=1468683
But this does happen on other ROMS too, they work perfectly for a while and then slowly begin to develop problems. At this stage I usually install the latest version of the ROM but I'm actually happy with the ROM at the moment and dont want to have to keep changing it!
I've been running Darkforest ROM since early stages and have had no problems so far. Maybe try that one. It's on v 5.1.5 now and it's very fast and very stable, moreso than many other ROMs i've tried.
Could be a defective device possibly? Are u using the kernel that comes with the rom?
Sent From Space Using My ICS Flavored Sensation
I would download 1-click cleaner and clean the cache every week. Also you might want to boot into recovery and wipe cache and dalvik cache every two weeks.
Sent from my HTC Sensation 4G using XDA App
I dont think there is anything wrong with the device, I'll try wiping the cache's and see if that makes a difference. Thank you very much for all your answers so far.
Max
Could possibly be an app try removing all your apps and install 1 by 1 give it a couple of weeks see if it happens again, I got a problem from juice defender pro (payed for) worked alright for few days then my launcher started force closing all the time took me ages to figure it out but got there by removing all my apps and installing them 1 by 1 long and time staking but worth a try
Sent from my HTC Sensation Z710e using xda premium
Okay well ive tried clearing the cache and davlik cache with no luck, less restarts but they are still there. I am resistant to start removing apps as I use them on a daily basis. Before I try this, does anyone have any other ideas?
Thanks,
Max
I have the same problem :/ it happens in both GB and ICS but It never happened to me till about 2 or 3 months ago
Sent from my HTC Sensation Z710e using xda premium
This is still happening, but now its starts to happen more quickly, the new Sense 4 insert coin ROM works fine for the first DAY then I get trouble
darksupernova said:
This is still happening, but now its starts to happen more quickly, the new Sense 4 insert coin ROM works fine for the first DAY then I get trouble
Click to expand...
Click to collapse
Please elaborate more of the problem/concern, so we could atleast help you somehow.
Sent from my HTC Sensation XE with Beats Audio
ardom said:
Please elaborate more of the problem/concern, so we could atleast help you somehow.
Sent from my HTC Sensation XE with Beats Audio
Click to expand...
Click to collapse
What other information would you like?
I think it may be a kernel issue, I'm going to try a few...
Tried three different kernals now, all with the same problem which would indicate its not a kernal problem? Something else perhaps? (Tried bricked, sebastian and RCMix)
its not a problem, its with network connection
I've had this problem since ages and couldn't fix it yet. First thing, download LTE switch and change the value from wcdma preferred to gsm auto. see if it avoids the restarts. Another thing you can try is, change the sim card (I havent tried it yet). Or, if possible, change the back cover. But I'm pretty pretty sure its the problem with the network.
Please reply.
Danyal93 said:
I've had this problem since ages and couldn't fix it yet. First thing, download LTE switch and change the value from wcdma preferred to gsm auto. see if it avoids the restarts. Another thing you can try is, change the sim card (I havent tried it yet). Or, if possible, change the back cover. But I'm pretty pretty sure its the problem with the network.
Please reply.
Click to expand...
Click to collapse
Pretty sure its a power/bat problem for me.
Update: tjamaican has kindly sent me a fix he found of the forums, its for a battery fix that worked for me on insertcoin's ICS Sense 4 RC4.1 ROM. However I have just moved to RC5 and the problem is back even with the fix.
http://www.mediafire.com/?2a8837bcatym1ju
I am going to try and set a lower CPU level, already down to 1.2 Ghz
Any ideas?
Well I have been at the 1.2GHz level for almost 24 hours now without too much trouble. Im not sure if it was lowering the CPU clock for screen on, or raising the CPU clock for screen off. Either way I can notice the device is slightly slower. I dont see why ICS doesnt like overclocking on this phone, GB was fine with it?!
Max
Update:
Just had a random shutdown, could have been anywhere in the last 20 mins. I really don't know what else to try!
Having EXACT ones you are having. Buy another battery if that doesn't work its a hardware problem. I still need to buy my battery but will post and let you know if it worked.
---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------
darksupernova said:
Well I have been at the 1.2GHz level for almost 24 hours now without too much trouble. Im not sure if it was lowering the CPU clock for screen on, or raising the CPU clock for screen off. Either way I can notice the device is slightly slower. I dont see why ICS doesnt like overclocking on this phone, GB was fine with it?!
Max
Update:
Just had a random shutdown, could have been anywhere in the last 20 mins. I really don't know what else to try!
Click to expand...
Click to collapse
I'm also starting to think its caused by not letting the battery fully die and recharging it a lot but that's just my guess?
I switched back to gingerbread yesterday and so far I've had no problems which would indicate its not a hardware issue...? Usually by now I've had a few shut downs..
So I went as far as unrooting and switching batteries with my bro and the problem continues idk what to do
sickorwuut said:
So I went as far as unrooting and switching batteries with my bro and the problem continues idk what to do
Click to expand...
Click to collapse
Yeah the problems started again for me on gingerbread. I've read its a motherboard problem I think I'm gonna have to send it off to HTC... Great... 3 weeks no phone...
Hello everyone,
I have looked around the forum and it seems like most of you guys with Sensation + 3.12 or 3.24 or 3.30 firmware and ICS Roms have good or great battery lives.
This is not the case for me unforunately with Sensation XE. battery drain is so crazy that if i go to sleep with 100% charged - the battery is dead when i wake up (in a metter of 8-10 hours) while the phone is not used at all, wi-fi and mobile network off.
I have tried
- full-wipe
- reflash
- calibration
- discharging to 0% and recahrging - couple cysles
- waiting 4-5 days until the ROM settles down
- removing microSD
- canging batteried (i have anker and stock htc both in good health)
- i am not overclocking
but still the battery drain is very bad.
I am now using Battery Monitoring widget but i cannot find what app or process is causing the problem.
Here are my questions
1) What is the normal mA value (displayed on battery monitor widget)?
what are your lowest and highest values? for me lowest is about 65mA and highest over 700mA. Is it to much? Those of you guys with nice battery drain - could you please install Battery Monitor Widget and let me know you values?
2) How can I find the app (if its an app) that takes the juice? I tried to see stats in battery monitor widget - but all I can see is some k.workers
I even tried to full-wipe and not to install any apps. Currently i have GoLauncher, GoSMS and Battery Monitor Widget, PlayerPro and Android Pro Widgets.
3 ) here is my battery history. Does it look normal?
Code:
2012/02/27|15:15:36|-553mA|100%|4026mV|25.4oC|1|0
2012/02/27|15:16:08|-553mA|100%|4026mV|25.4oC|1|0
2012/02/27|15:17:32|-581mA|100%|4008mV|25.5oC|1|0
2012/02/27|15:22:31|-138mA|100%|4089mV|25.2oC|2|0
2012/02/27|15:27:32|-137mA|100%|4080mV|25.3oC|0|0
2012/02/27|15:32:31|-153mA|100%|4068mV|25.3oC|0|0
2012/02/27|15:37:31|-75mA|100%|4086mV|25.2oC|0|0
2012/02/27|15:42:31|-70mA|100%|4083mV|25.2oC|0|0
2012/02/27|15:47:31|-73mA|99%|4080mV|25.2oC|0|0
2012/02/27|15:52:31|-70mA|99%|4077mV|25.2oC|0|0
2012/02/27|15:57:31|-96mA|98%|4074mV|25.2oC|0|0
2012/02/27|16:02:31|-71mA|98%|4071mV|25.2oC|0|0
2012/02/27|16:07:31|-98mA|98%|4071mV|25.3oC|2|0
2012/02/27|16:12:31|-79mA|97%|4068mV|25.2oC|0|0
2012/02/27|16:17:31|-73mA|97%|4065mV|25.2oC|0|0
2012/02/27|16:22:31|-71mA|96%|4062mV|25.2oC|0|0
2012/02/27|16:27:31|-71mA|96%|4059mV|25.2oC|2|0
2012/02/27|16:32:31|-69mA|95%|4053mV|25.2oC|0|0
2012/02/27|16:37:31|-73mA|94%|4044mV|25.2oC|0|0
2012/02/27|16:42:31|-111mA|93%|4011mV|25.3oC|0|0
2012/02/27|16:47:31|-207mA|93%|4017mV|25.2oC|0|0
2012/02/27|16:52:31|-194mA|91%|3993mV|25.2oC|0|0
2012/02/27|16:57:31|-186mA|90%|4002mV|25.3oC|0|0
2012/02/27|17:02:31|-177mA|89%|3999mV|25.3oC|0|0
2012/02/27|17:07:31|-189mA|87%|3960mV|25.3oC|0|0
2012/02/27|17:12:31|-157mA|86%|3987mV|25.3oC|0|0
2012/02/27|17:17:31|-156mA|85%|3969mV|25.2oC|0|0
2012/02/27|17:22:31|-128mA|84%|3978mV|25.2oC|0|0
2012/02/27|17:27:31|-95mA|83%|3978mV|25.2oC|0|0
2012/02/27|17:32:31|-86mA|82%|3972mV|25.2oC|0|0
2012/02/27|17:37:31|-92mA|81%|3972mV|25.2oC|0|0
2012/02/27|17:42:31|-70mA|81%|3969mV|25.2oC|0|0
2012/02/27|17:47:31|-72mA|80%|3966mV|25.2oC|0|0
2012/02/27|17:52:31|-89mA|80%|3963mV|25.2oC|0|0
2012/02/27|17:57:31|-85mA|79%|3960mV|25.2oC|0|0
2012/02/27|18:02:31|-104mA|79%|3957mV|25.2oC|2|0
2012/02/27|18:07:31|-81mA|79%|3954mV|25.2oC|0|0
2012/02/27|18:12:31|-78mA|79%|3954mV|25.2oC|0|0
2012/02/27|18:17:31|-74mA|79%|3954mV|25.2oC|0|0
2012/02/27|18:22:31|-80mA|78%|3951mV|25.2oC|0|0
2012/02/27|18:27:31|-119mA|78%|3951mV|25.2oC|0|0
2012/02/27|18:32:31|-87mA|78%|3945mV|25.2oC|0|0
2012/02/27|18:37:31|-82mA|77%|3945mV|25.2oC|0|0
2012/02/27|18:42:31|-84mA|77%|3942mV|25.2oC|0|0
2012/02/27|18:47:31|-75mA|76%|3939mV|25.2oC|0|0
2012/02/27|18:52:31|-77mA|76%|3933mV|25.2oC|0|0
2012/02/27|18:57:31|-79mA|75%|3933mV|25.2oC|0|0
2012/02/27|19:02:31|-82mA|75%|3930mV|25.2oC|0|0
2012/02/27|19:07:31|-89mA|74%|3927mV|25.2oC|0|0
2012/02/27|19:12:31|-81mA|74%|3924mV|25.2oC|0|0
2012/02/27|19:17:31|-83mA|73%|3921mV|25.2oC|0|0
2012/02/27|19:22:31|-81mA|73%|3918mV|25.2oC|0|0
2012/02/27|19:27:31|-114mA|72%|3894mV|25.2oC|0|0
2012/02/27|19:32:31|-80mA|71%|3909mV|25.2oC|0|0
2012/02/27|19:37:31|-102mA|71%|3906mV|25.2oC|0|0
2012/02/27|19:42:31|-85mA|70%|3909mV|25.2oC|0|0
2012/02/27|19:47:31|-57mA|69%|3903mV|25.2oC|0|0
2012/02/27|19:52:31|-57mA|69%|3903mV|25.2oC|0|0
2012/02/27|19:57:31|-96mA|69%|3888mV|25.2oC|0|0
2012/02/27|20:02:31|-74mA|68%|3894mV|25.2oC|0|0
2012/02/27|20:07:31|-78mA|68%|3891mV|25.2oC|0|0
2012/02/27|20:12:31|-76mA|67%|3888mV|25.2oC|0|0
2012/02/27|20:17:31|-84mA|67%|3885mV|25.2oC|2|0
2012/02/27|20:22:31|-89mA|66%|3879mV|25.2oC|2|0
2012/02/27|20:27:31|-101mA|66%|3867mV|25.2oC|2|0
2012/02/27|20:32:31|-93mA|65%|3867mV|25.2oC|0|0
2012/02/27|20:37:31|-87mA|64%|3867mV|25.2oC|0|0
2012/02/27|20:42:31|-87mA|63%|3864mV|25.2oC|0|0
2012/02/27|20:47:31|-82mA|63%|3858mV|25.2oC|0|0
2012/02/27|20:52:31|-119mA|62%|3849mV|25.2oC|2|0
2012/02/27|20:57:31|-81mA|61%|3846mV|25.2oC|0|0
2012/02/27|21:02:31|-125mA|61%|3837mV|25.2oC|2|0
2012/02/27|21:07:31|-86mA|60%|3843mV|25.2oC|2|0
2012/02/27|21:12:31|-79mA|59%|3837mV|25.2oC|0|0
2012/02/27|21:17:31|-79mA|59%|3837mV|25.2oC|0|0
2012/02/27|21:22:31|-69mA|58%|3831mV|25.2oC|0|0
2012/02/27|21:27:31|-80mA|58%|3825mV|25.2oC|0|0
2012/02/27|21:32:31|-76mA|58%|3828mV|25.2oC|0|0
2012/02/27|21:37:31|-83mA|57%|3825mV|25.2oC|0|0
2012/02/27|21:42:31|-78mA|57%|3822mV|25.2oC|0|0
2012/02/27|21:47:31|-76mA|56%|3819mV|25.2oC|0|0
2012/02/27|21:52:31|-81mA|56%|3816mV|25.2oC|0|0
2012/02/27|21:57:31|-77mA|55%|3816mV|25.2oC|0|0
2012/02/27|22:02:31|-91mA|55%|3804mV|25.2oC|0|0
2012/02/27|22:07:31|-87mA|55%|3810mV|25.2oC|0|0
2012/02/27|22:12:31|-77mA|54%|3810mV|25.2oC|0|0
2012/02/27|22:17:31|-77mA|53%|3810mV|25.2oC|0|0
2012/02/27|22:22:31|-79mA|53%|3804mV|25.2oC|0|0
2012/02/27|22:27:31|-77mA|52%|3804mV|25.2oC|0|0
2012/02/27|22:32:31|-77mA|52%|3804mV|25.2oC|0|0
2012/02/27|22:37:31|-86mA|52%|3801mV|25.2oC|0|0
2012/02/27|22:42:31|-85mA|51%|3798mV|25.2oC|0|0
2012/02/27|22:47:31|-183mA|50%|3783mV|25.3oC|0|0
2012/02/27|22:52:31|-182mA|50%|3777mV|25.3oC|0|0
2012/02/27|22:57:31|-178mA|50%|3762mV|25.3oC|0|0
2012/02/27|23:02:31|-180mA|50%|3783mV|25.3oC|0|0
2012/02/27|23:07:31|-173mA|50%|3768mV|25.3oC|0|0
2012/02/27|23:12:31|-170mA|49%|3771mV|25.2oC|0|0
2012/02/27|23:17:05|-131mA|48%|3777mV|25.2oC|1|0
2012/02/27|23:22:04|-320mA|46%|3780mV|25.2oC|2|0
2012/02/27|23:27:04|-101mA|46%|3771mV|25.2oC|0|0
2012/02/27|23:32:04|-75mA|45%|3783mV|25.2oC|0|0
2012/02/27|23:37:04|-85mA|45%|3780mV|25.2oC|2|0
2012/02/27|23:42:04|-114mA|45%|3783mV|25.2oC|2|0
2012/02/27|23:47:04|-107mA|44%|3780mV|25.2oC|0|0
2012/02/27|23:52:04|-115mA|43%|3765mV|25.3oC|0|0
2012/02/27|23:57:04|-83mA|42%|3774mV|25.2oC|0|0
2012/02/28|00:02:04|-82mA|42%|3777mV|25.2oC|0|0
2012/02/28|00:07:04|-73mA|41%|3774mV|25.2oC|0|0
2012/02/28|00:12:04|-92mA|41%|3774mV|25.2oC|0|0
2012/02/28|00:17:04|-77mA|41%|3771mV|25.2oC|2|0
2012/02/28|00:22:04|-83mA|41%|3765mV|25.2oC|0|0
2012/02/28|00:27:04|-92mA|40%|3771mV|25.2oC|0|0
2012/02/28|00:32:04|-73mA|39%|3768mV|25.2oC|0|0
2012/02/28|00:37:04|-73mA|39%|3768mV|25.2oC|0|0
2012/02/28|00:42:04|-85mA|38%|3762mV|25.2oC|0|0
2012/02/28|00:47:04|-82mA|38%|3768mV|25.2oC|0|0
2012/02/28|00:52:04|-78mA|38%|3765mV|25.2oC|0|0
2012/02/28|00:57:04|-79mA|38%|3765mV|25.2oC|0|0
2012/02/28|01:02:04|-97mA|38%|3756mV|25.2oC|0|0
2012/02/28|01:07:04|-91mA|37%|3762mV|25.2oC|0|0
2012/02/28|01:12:04|-88mA|36%|3759mV|25.2oC|0|0
2012/02/28|01:17:04|-83mA|36%|3762mV|25.2oC|0|0
2012/02/28|01:22:04|-89mA|36%|3753mV|25.2oC|0|0
2012/02/28|01:27:04|-127mA|36%|3759mV|25.2oC|0|0
2012/02/28|01:32:04|-114mA|36%|3753mV|25.2oC|0|0
2012/02/28|01:37:04|-85mA|36%|3759mV|25.2oC|0|0
2012/02/28|01:42:04|-77mA|35%|3759mV|25.2oC|0|0
2012/02/28|01:47:04|-79mA|35%|3756mV|25.2oC|0|0
2012/02/28|01:52:04|-72mA|34%|3753mV|25.2oC|0|0
2012/02/28|01:57:04|-105mA|34%|3747mV|25.2oC|2|0
2012/02/28|02:02:04|-84mA|33%|3750mV|25.2oC|0|0
2012/02/28|02:07:04|-75mA|33%|3750mV|25.2oC|0|0
2012/02/28|02:12:04|-126mA|33%|3744mV|25.2oC|0|0
2012/02/28|02:17:04|-100mA|33%|3735mV|25.2oC|0|0
2012/02/28|02:22:04|-99mA|31%|3747mV|25.2oC|0|0
2012/02/28|02:27:04|-79mA|31%|3744mV|25.2oC|0|0
2012/02/28|02:32:04|-77mA|30%|3741mV|25.2oC|0|0
2012/02/28|02:37:04|-100mA|29%|3738mV|25.2oC|0|0
2012/02/28|02:42:04|-71mA|29%|3741mV|25.2oC|0|0
2012/02/28|02:47:04|-73mA|28%|3735mV|25.2oC|0|0
2012/02/28|02:52:04|-100mA|28%|3732mV|25.2oC|0|0
2012/02/28|02:57:04|-85mA|27%|3735mV|25.2oC|0|0
2012/02/28|03:02:04|-88mA|27%|3732mV|25.2oC|0|0
2012/02/28|03:07:04|-97mA|27%|3729mV|25.2oC|0|0
2012/02/28|03:12:04|-83mA|25%|3732mV|25.2oC|0|0
2012/02/28|03:17:04|-82mA|25%|3720mV|25.2oC|0|0
2012/02/28|03:22:04|-85mA|24%|3726mV|25.2oC|0|0
2012/02/28|03:27:04|-73mA|23%|3723mV|25.2oC|0|0
2012/02/28|03:32:04|-83mA|23%|3717mV|25.2oC|0|0
2012/02/28|03:37:04|-88mA|22%|3720mV|25.2oC|0|0
2012/02/28|03:42:04|-80mA|22%|3717mV|25.2oC|0|0
2012/02/28|03:47:04|-86mA|20%|3714mV|25.2oC|0|0
2012/02/28|03:52:04|-103mA|20%|3708mV|25.2oC|0|0
2012/02/28|03:57:04|-78mA|19%|3711mV|25.2oC|0|0
2012/02/28|04:02:04|-83mA|19%|3705mV|25.2oC|0|0
2012/02/28|04:07:04|-77mA|19%|3705mV|25.2oC|0|0
2012/02/28|04:12:04|-92mA|19%|3696mV|25.2oC|0|0
2012/02/28|04:17:04|-86mA|18%|3699mV|25.2oC|0|0
2012/02/28|04:22:04|-112mA|18%|3693mV|25.2oC|0|0
2012/02/28|04:27:04|-75mA|18%|3693mV|25.2oC|0|0
2012/02/28|04:32:04|-75mA|17%|3690mV|25.2oC|0|0
2012/02/28|04:37:04|-114mA|16%|3666mV|25.3oC|0|0
2012/02/28|04:42:04|-204mA|16%|3657mV|25.2oC|0|0
2012/02/28|04:47:04|-91mA|16%|3681mV|25.2oC|0|0
2012/02/28|04:52:04|-158mA|16%|3669mV|25.3oC|0|0
2012/02/28|04:57:04|-122mA|16%|3678mV|25.2oC|0|0
2012/02/28|05:02:04|-78mA|16%|3678mV|25.2oC|0|0
2012/02/28|05:07:04|-87mA|16%|3669mV|25.2oC|0|0
2012/02/28|05:12:04|-86mA|16%|3678mV|25.2oC|0|0
2012/02/28|05:17:04|-87mA|16%|3672mV|25.2oC|0|0
2012/02/28|05:22:04|-82mA|16%|3675mV|25.2oC|0|0
2012/02/28|05:27:04|-81mA|16%|3666mV|25.2oC|0|0
2012/02/28|05:32:04|-104mA|16%|3663mV|25.2oC|0|0
2012/02/28|05:37:04|-85mA|15%|3663mV|25.2oC|0|0
2012/02/28|05:42:04|-72mA|15%|3669mV|25.2oC|0|0
2012/02/28|05:47:04|-79mA|15%|3663mV|25.2oC|0|0
2012/02/28|05:52:04|-72mA|14%|3654mV|25.2oC|0|0
2012/02/28|05:57:04|-84mA|13%|3642mV|25.2oC|0|0
2012/02/28|06:02:04|-89mA|11%|3624mV|25.2oC|0|0
2012/02/28|06:07:04|-97mA|9%|3591mV|25.2oC|0|0
2012/02/28|06:12:04|-85mA|6%|3570mV|25.2oC|0|0
2012/02/28|06:17:04|-98mA|4%|3528mV|25.2oC|0|0
2012/02/28|06:22:04|-97mA|3%|3489mV|25.2oC|0|0
2012/02/28|06:27:04|-93mA|2%|3444mV|25.2oC|0|0
Any advise and help will be much appreciated.
Thanks
It seems high but not outrageous. You gave about 70-100mAh when not in use which is about what I had with factory rom. I assume all the usual things are done like GPS off, brightness low, wifi on etc.
Do you have poor signal, and are you using mobile data a lot? That increases battery usage.
To assess more fully the processes running I use system tuner pro. This allows you to see user, system & kernel processes and sort by memory, CPU time etc.
I currently see around 30-60mAh when idling.
Sent from my Pyramid-T
Hello,
thanks for reply.
My Signal is good (full-bars) Mobile Data is off, WIFI, GPS are off as well
and brightness low... but actually the screen is off when i am sleeping...
I understand smartphones use power, especially on mobile-data and WiFi, but I hate that feeling when I wake up and see my phone's battery dead....
never got as low as 30mAh even when completely not in use with everything off.
I will try to use System Tuner Pro - maybe will find out somethinh.
OK post back results perhaps I can help more.
I'm looking at STP now, using task manager I can see my top processes in terms of CPU time are:
STP
android system
Xda premium
Android keyboard
/system/bin/surfaceflinger
Gmail
System UI
do nothing untoward, I would expect those to be running given my usage right now.
Use STP to record a period when you sleep, you can then do this process check to see what's running.
Sent from my Pyramid-T
My battery is pretty much the same and I'm on a fresh ics install. This device seems to just suck a lot of battery. The screen especially.
Sent from my HTC Pyramid using Tapatalk
Hmmm my sensation XE used to have at least 1.5 times as much power (when used) and 2 to 3 times as much power when not used befor upgrading to 3.12, 3.24 and 3.30.
I know what you will tell - go back to Gingerbread.
I am actually considering this. but many people say with ICS their battery is better then ever before.
Is it ICS who sucks the power then?
Thanks
From your stats you are losing 1% in 5 minutes in standby, my sensation (with virtuous inquisition ROM) uses less than 1% per hour - that's with a good 4G connection in standby. My 1900mAh battery lasts over 24hrs with up to 6hrs screen on during that time.
To eliminate hardware flash a fresh ROM and firmware, boot a couple of times (don't install any apps) then remove the SD card and put the phone in airplane mode and leave it overnight on standby. If you're losing more than 1% per hour, then your phone may be faulty. If not then you'll need to try things one by one, turn airplane mode off, insert SD, then apps until you find the problem.
Looking at the instant mAh figures won't help you a lot, the battery driver for the sensation is useless and BMW has to estimate the figure.
Thanks for advice.
Could you please let me know the firware you are using?
3.12, 3.24 or 3.30 ?
boomboomer said:
From your stats you are losing 1% in 5 minutes in standby, my sensation (with virtuous inquisition ROM) uses less than 1% per hour
Click to expand...
Click to collapse
umka83 said:
Thanks for advice.
Could you please let me know the firware you are using?
3.12, 3.24 or 3.30 ?
Click to expand...
Click to collapse
3.12. I had the 3.24 ready to load when VI 3.5 was released but everything worked fine on 3.12 so I left well alone.
Ok here is what happened
1) i falshed new 3.30 RUU and ROM with fullwipe etc
2) booted the rom put it to settle fo 30 mins
3) rebooted 3 times
4) then charged to 100%, and switched airplane mode ON
with Airplane Mode on - I have lost 25% of battery during 3 hours without touching the phone. That makes 12 hours without using the phone at all.
I am starting wondering if it is not the firware that is causing the problems... Maybe i should go back to 3.12 or even earlier.
Anyone can please point me to some firmware earlier to 3.12?
I do not think it is a faulty phone, because I have 2 phones and both have same problem. and both started having this problem after upgrading to ICS...
let me know you thoughts and please a link to an earlier firmware (earlier than 3.12)
battery drain
i would say you have normal operation .
mine is between 50-100 MA and yet when not using it during night in the morning i am still at 100%......
when keeping it for a whole day not using it i am droping from 100% to 87% for about 24 hours idle use ....
so i would say check your battery when it starts or is it from the day you got your device .....
Thanks for reply, oferyama
Normal operation ??
You lose 23% in 24 hours while
me - I lose 1% every 5 minutes = teh phone is dead after 10 hours of idling.....
Probalby mAh reported vaules is incorrect, and the important thing is how many % you lose per hour
Did you flash a custom kernel at all?
What rom is this problem occurring with?
Sent from my Pyramid-T
I have tried many ICS ROMS - Elegancia ICS, AnroidMe ICS, LeeDroid ICS = same problem. i also tried 3.12, 3.24 and 3.30 firmwares
but I cannot remember if the problem started when i upgraded to 3.12 or 3.24.....
From today I have 3.30 jsut for testing... and if everything fails - planning to go back to Gingerbread to see if it helps...
Hi umka, I had same problem as you. Try this to figure out what's eating your battery: http://forum.xda-developers.com/showthread.php?t=1179809
I'm using VI 3.5.1 beta and battery drain varies from 30 to 82mA while not touching a phone at all on stock XE battery. While i'm typing this, I have 78% battery, phone is unplugged for 10h and 6 minutes. I'm using SebastianFM kernel 1.11 (this one: http://dl.dropbox.com/u/64017594/HTC Sensation/Overclocked_kernel_v1.11_1512_MHz_by_SebastianFM.zip) on my Sensation XE. Radio is stock for FW 3.30. Adequate RIL of course. Lots of apps installed, many of them are disabled from autostarting. I'm using Shnizlon's theme (just aosp bar).
Desktop: minimalistic text with weather info, updating every 3 hours.
Hope this brief info will help you to figure something out.
Good luck!
Thanks for reply - trying this right now....
Amon87, could you please let me know what was eating batery in your case?? I have just flashed a new ROM and did not isntall any applications at all... Where shoud I look at?
I was suspecting the radio, but i tried different ones... and i tried airplane mode - but even in airplane mode when radio shoud not make any difference the battery drain is terrible..
i will post you on the results
umka83 said:
I have tried many ICS ROMS - Elegancia ICS, AnroidMe ICS, LeeDroid ICS = same problem. i also tried 3.12, 3.24 and 3.30 firmwares
but I cannot remember if the problem started when i upgraded to 3.12 or 3.24.....
From today I have 3.30 jsut for testing... and if everything fails - planning to go back to Gingerbread to see if it helps...
Click to expand...
Click to collapse
So no kernels flashed desperately to rom?
Did you have any results from STP finding the battery killer? Do you restore app/data after each flash e.g. with TiBu?
Sent from my Pyramid-T
Sorry to say, but i just don't remember the name of that app. For sure, main problem for me was radio and unmatching RIL.
I recommend you to try different kernel and change governor. I'm using system tuner pro to change this. When screen on: ondemand 192-1.51. Screen off: interactive 192-648MHz. But try powersave.
Another clue. Maybe somehow second core is constantly turned on?
What recovery are you using to flash roms, kernels etc? For me it's newest 4ext recovery test build.
stringer7 said:
So no kernels flashed desperately to rom?
Did you have any results from STP finding the battery killer? Do you restore app/data after each flash e.g. with TiBu?
Sent from my Pyramid-T
Click to expand...
Click to collapse
1) In most case I used default kernels provided with the ROM (somtimes flashed custom ones)
2) I am not good yet at looking at STP and BMW stats - so amybe I am missing something, but so far I did not find the battery killer. How do you find the battery killer? a process using more than 10%-20% CPU or smth like that?
3) I used to restore the apps using Titanium Backup, but then, to find out the problem, i just flashed a fresh ROM and did not install any apps at all..
and still losing at least 10% per hour with DATA off, Mobile Network OFF, GPS and WIFI off and Airplan Mode ON.
amon87 said:
Sorry to say, but i just don't remember the name of that app. For sure, main problem for me was radio and unmatching RIL.
I recommend you to try different kernel and change governor. I'm using system tuner pro to change this. When screen on: ondemand 192-1.51. Screen off: interactive 192-648MHz. But try powersave.
Another clue. Maybe somehow second core is constantly turned on?
What recovery are you using to flash roms, kernels etc? For me it's newest 4ext recovery test build.
Click to expand...
Click to collapse
- Well right now I do not have any apps installed yet, excpet those that come default with 3.30. So its definetely not an application.
- !!! Myabe it is indeed unmatching RIL adn RADIO - coudl you please give me more info on that? How do I find out what is matching. I am in Japan and i bought my phone in HongKong (so it shoould be asia) and default ROM was doing just fine... Could you please point me to correct RIL and Radio - or advice where to look?
- From what i have seen in STP yesturday - second core is off. not sure about now - cause i do not have STP installed after flashing stok 3.30
- I am using ext4 recovery latest.
Hey all,
I have a very fun and exciting cell phone now thanks to rooting my phone and installing the Virtuous Inquisition ROM on my phone.
However, now that I've done all that, I've got the itch to do more to my phone. I really like VI as a ROM, but is there anything else I can do to my phone?
Thanks!
Flash hypernonsense, it's like VI but with the remaining few bugs fixed, better battery life (with stock kernel) and a later ICS build. Make sure you have firmware 3.33 to avoid reboots.
boomboomer said:
Flash hypernonsense, it's like VI but with the remaining few bugs fixed, better battery life (with stock kernel) and a later ICS build. Make sure you have firmware 3.33 to avoid reboots.
Click to expand...
Click to collapse
I've been tempted to flash hypernonsense too, as its basically like an updated VI. How is firmware 3.33, do you have any wifi signal issues and if so where are you based? Its the only thing holding me back, as I've seen people saying that their wifi is affected after upgrading to 3.33.
gsmyth said:
I've been tempted to flash hypernonsense too, as its basically like an updated VI. How is firmware 3.33, do you have any wifi signal issues and if so where are you based? Its the only thing holding me back, as I've seen people saying that their wifi is affected after upgrading to 3.33.
Click to expand...
Click to collapse
I'm in the UK, 3G signal strength is improved and wifi is no different than it was in VI - it all works perfectly including tethering.
The biggest improvement is battery life - over 1d 16hrs, with 5 to 7hrs screen on time is the norm now (using the Anker 1900).
boomboomer said:
I'm in the UK, 3G signal strength is improved and wifi is no different than it was in VI - it all works perfectly including tethering.
The biggest improvement is battery life - over 1d 16hrs, with 5 to 7hrs screen on time is the norm now (using the Anker 1900).
Click to expand...
Click to collapse
Thanks, im also in the UK, so might just give this a shot. Just biding my time for a fully stable CM10 release as it doesnt seem to far away now, so will feed my flashing needs for now. Also been looking at the Anker battery, looks good value for a tenner. On the stock battery on VI, I'm getting around 20-24hr(+) with 3-3.5 hrs screen on time.
boomboomer said:
I'm in the UK, 3G signal strength is improved and wifi is no different than it was in VI - it all works perfectly including tethering.
The biggest improvement is battery life - over 1d 16hrs, with 5 to 7hrs screen on time is the norm now (using the Anker 1900).
Click to expand...
Click to collapse
really? hrm... (I also use the Anker 1900s).
I'll check it out. I think I had HyperNonSense before I had VI and switched for some reason.
Thanks.
boomboomer said:
Flash hypernonsense, it's like VI but with the remaining few bugs fixed, better battery life (with stock kernel) and a later ICS build. Make sure you have firmware 3.33 to avoid reboots.
Click to expand...
Click to collapse
Does this rom have any bugs that stop you using it on a daily basis?
I'm experiencing a GPS issue with CM9.1 so may need an alternative but I'm not keen on sense anymore so want to stick with the whole stock android look/feel.
Really like the way CM9 works in comparison to CM7, it may just be the change over from gingerbread to ICS but its awesome.
Sent from my HTC Sensation using xda app-developers app
You can find the "bug" list for this Rom .and for all other roms on the first page of download section .'
Sent from my HTC Sensation 4G using xda premium
Repoman123 said:
Does this rom have any bugs that stop you using it on a daily basis?
I'm experiencing a GPS issue with CM9.1 so may need an alternative but I'm not keen on sense anymore so want to stick with the whole stock android look/feel.
Really like the way CM9 works in comparison to CM7, it may just be the change over from gingerbread to ICS but its awesome.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
No bugs, been using it as my daily for months now. The only thing not working is the fm radio.
boomboomer said:
No bugs, been using it as my daily for months now. The only thing not working is the fm radio.
Click to expand...
Click to collapse
Thanks for the response.
So you think this could be one of the closest roms to CM9? In terms of user interface and features?
(Sorry for the noob questions, I've only ever used 2 roms. CM7 and CM9!)
Sent from my HTC Sensation using xda app-developers app
Repoman123 said:
Thanks for the response.
So you think this could be one of the closest roms to CM9? In terms of user interface and features?
(Sorry for the noob questions, I've only ever used 2 roms. CM7 and CM9!)
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I have no idea, never installed either of those. I aim for a lightweight ROM with maximum battery life as I need the phone for what it can do, rather than eyecandy and features I don't use.
It's as close to an AOSP ROM that has everything working, if that helps.
I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?
tmar89 said:
I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?
Click to expand...
Click to collapse
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.
anactoraaron said:
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.
Click to expand...
Click to collapse
No, I mean with the aftermarket ROMs, do any others besides CM 10 have issues with the flash or toggle? I have no problems with the stock Blaze 4G torch
I'm on the latest CM10 Nightly and the included Torch works fine.
LBN1 said:
I'm on the latest CM10 Nightly and the included Torch works fine.
Click to expand...
Click to collapse
Thanks, I'm going to try the stable CM10
tmar89 said:
Thanks, I'm going to try the stable CM10
Click to expand...
Click to collapse
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
dammit.. and I just flashed and loaded my apps and settings..
anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
Why do you say that the stable build isn't that stable? I've been running it and it works fine for me. It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.
keiichidono said:
It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.
Click to expand...
Click to collapse
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.
anactoraaron said:
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.
Click to expand...
Click to collapse
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?
keiichidono said:
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?
Click to expand...
Click to collapse
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.
anactoraaron said:
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.
Click to expand...
Click to collapse
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?
keiichidono said:
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?
Click to expand...
Click to collapse
Racings unofficial AOKP + lightning zap = WIN
Snappy snappy, stable(no reboots period), best battery life for any jelly bean ROM I've tried, and the built-in toggle torch works perfectly.
just my 2 cents
Sent from my AOKP Blaze
installed newest
(date 27.1.2014 with GAPPS modular mini from: http://forum.xda-developers.com/showthread.php?t=2530073)
did full wipe (factory reset, system, cache) as in info
have some major problems with stability, looks like system degrades quickly after leaving screen off mode
After restart I can set up everything fine, can use network, launch apps, change system settings etc
but after first turning off and turning on lock screen starts to show first problems, dots (I'm using pattern unlock) sometimes start to activate on their own, not always but sometimes this happens, but I'm still able to logon...
after second 'screen off' and 'screen on' I'm having big problems trying to unlock screen - sometime dot's don't react to touches, sometimes they do not end connecting after taking away finger from screen...
after third off/on I'm unable to pass unlock screen - it becomes unresponsive, dots start to connect randomly, sometime even 'emergency calls' gets activated...
what can cause this? full phone restart appears to fix problems for short time, but after few off/on have problems agains...
this did not happen in builds from few months ago
tried to set higher min cpu frequency to 384MHz but that doesn't help
other things that I chaged are:
- cpu governor -> badass
- i/o -> noop
- active 'allow purging of assets'
anyone got ideas what could cause this? and how to fix
phone:
htc sensation xe, unlocked
hboot 1.29, radio 11.24a.3504.31_m
can provide other info if needed
It's easy to be fixed, install stock rom.
nlooooo said:
It's easy to be fixed, install stock rom.
Click to expand...
Click to collapse
thank you, very helpful
What firmware are you on? Did you experience any of these problems on any other rom?
You say the dots connect themselves. As if the touchscreen is used? Sounds somehow like a broken digitizer.
zodi79 said:
thank you, very helpful
Click to expand...
Click to collapse
Do you know how many threads like yours have been opened recently? Is it that hard to search and why do you expect flawless rom?
When will people learn, it's unofficial, it's custom, it's a new android version tied to the old hardware with the old drivers, it will, probably never be perfect.
nlooooo said:
Do you know how many threads like yours have been opened recently? Is it that hard to search and why do you expect flawless rom?
When will people learn, it's unofficial, it's custom, it's a new android version tied to the old hardware with the old drivers, it will, probably never be perfect.
Click to expand...
Click to collapse
I must have missed all of these threads. There were some threads about cm11 but they had other issues.
This phone is 3 years old and you're using Badass. Since you want more performance, set your CPU governor to Ondemand and set I/O scheduler to BFQ or SIO.
Sent from my Nexus 5 using xda app-developers app
Sultanxda said:
This phone is 3 years old and you're using Badass. Since you want more performance, set your CPU governor to Ondemand and set I/O scheduler to BFQ or SIO.
Click to expand...
Click to collapse
ok, will try
atm had to move back to previous cm 10.1 based on 4.2.2 prepared few months ago, it appears to work much better but still have some stability issues. Doesn't look like problem with touch screen as most (now like 97%) it works flawlessly... yeah, not 100% so it could be hardware problem, just that didn't happen before
and yeah, I know these are unstable, beta like, etc roms - I like to test new features on my sens xe and one prepared by sultanxda is atm the best for me, keep up great work and thank you for time spent working on this rom.
zodi79 said:
ok, will try
atm had to move back to previous cm 10.1 based on 4.2.2 prepared few months ago, it appears to work much better but still have some stability issues. Doesn't look like problem with touch screen as most (now like 97%) it works flawlessly... yeah, not 100% so it could be hardware problem, just that didn't happen before
and yeah, I know these are unstable, beta like, etc roms - I like to test new features on my sens xe and one prepared by sultanxda is atm the best for me, keep up great work and thank you for time spent working on this rom.
Click to expand...
Click to collapse
Why not try my CM10.2 ROM? CM10.2 is far more stable than CM11, and, personally, CM10.2 feels smoother than CM11.
first of all - sorry for misinformation but I found cause of my problems with interface... looks like minimal amount of water must have got under the cover when I few days ago applied new screen protection, yesterday I got this idea of what could cause this sudden problems... few hours phone stayed on the room heater (not too hot ofc) and touch screen problems are gone! yeah, tbh I love this phone and was very angry thinking I'd have to replace it, now I don't have to
back to rom - atm back to your (sultan) rom based on CM 11 with update from 29.1.2014, it has some small problems but I like to test new features
problems I've found so far:
- less responsive and smooth
- launcher3 doesn't allow to create new home screens on the left, had to create new to the right then make some rearangments before I got things right
- some widget resize problems under launcher3
- other small problems all I can live with
but I like more available memory and better battery life, going to test ART soon
and it is good that messanging is back, hangouts is just... not for me
Why cant i find my phone contacts on SIM ??? Its say no contacts found? When i import some numbers from vCard from SD why cant i move them to SIM???
cm10.2 - cm11
Sultanxda said:
Why not try my CM10.2 ROM? CM10.2 is far more stable than CM11, and, personally, CM10.2 feels smoother than CM11.
Click to expand...
Click to collapse
funny ... i tried a lot of rom and i dont have real problem except with your latest rom ([ROM][Android 4.3.1][Camera works] CM10.2 with ION [Jan 30, 2014]) : lags, reboot , ...
Now i use your latest rom on CM11 ([ROM][Android 4.4.2][Camera works] CM11 with ION [Jan 29, 2014]), realy good no problem, thank's for all.
romadd said:
funny ... i tried a lot of rom and i dont have real problem except with your latest rom ([ROM][Android 4.3.1][Camera works] CM10.2 with ION [Jan 30, 2014]) : lags, reboot , ...
Now i use your latest rom on CM11 ([ROM][Android 4.4.2][Camera works] CM11 with ION [Jan 29, 2014]), realy good no problem, thank's for all.
Click to expand...
Click to collapse
I tested it for 3 hours and it was working well
Sultanxda said:
I tested it for 3 hours and it was working well
Click to expand...
Click to collapse
I had fresh install, but configured cpu clock speed 1674 mhz (maybe the problem ?)
And i had the same symptom describe by Firehawk989 http://forum.xda-developers.com/showpost.php?p=49938883&postcount=3341
Any way i run already with your CM11 and it seem more stable for me except a little problem
http://forum.xda-developers.com/showpost.php?p=49353701&postcount=1
This is another story