I flashed a custom ROM [unofficial CM9 ICS4.0.4]. Everything seems to be working fine, but there are a few problems and I'm wondering if this is normal for those using this. It's my first time flashing a ROM on my android and I'm not sure if it's normal. Did some searching in the forum, couldn't find much info too. Maybe I didn't search hard enough!
Anyway, here are some issues, I'm not even sure if it's the ROM.
1. Sometimes, the apps just bring me back to the home screen several times. Example: Running whatsapp brings me to home screen a few times, or when I go into a conversation, it brings me back to the conversation list but eventually it works.
2. On another occasion, every app that I ran would be unresponsive and I needed to end it. Solved it by rebooting.
3. Battery drain is very fast with little usage. I thought running a custom ROM usually provides better battery life.
I've not overclocked it, it's still in it's default value after flashing 1024. So I doubt it's anything to do with that. But since we're on the topic on overclocking. Desire HD didn't have anything beyond Gingerbread. So if we're flashing anything greater, is there a need overclock to be able to work comfortably on a higher OS? Is there a minimum or maximum for it to function comfortably?
Thanks!
Hmm, did more reading up.
Could it be I didn't calibrate my battery after flashing a new ROM?
Just flashed ARHD 6.4, will try to calibrate after that.
Appreciate any other advice though
Related
I've tried several builds and am quite happy with each (getting better and better as I learn more and more). I've gotten newer and newer kernels and builds and am currently using Thoughlesskyle's not so super froyo and am really liking it.
The one deal-breaker issue that's keeping me from using this phone full time is something I'm calling a phone coma. The phone periodically refuses to wake up from sleep. I may have a flashing notification light that makes it look like the phone is sleeping but I am not receiving emails or phone calls when it's in this state. To wake it up, I have to press the reset button.
I think this may be related to battery (http://forum.xda-developers.com/showpost.php?p=9360324&postcount=7) and I'm going to try to debug this a bit but I was wondering if anyone else is seeing this. I don't think it's specifically related to any one build as I've seen this with DZO and Thoughlesskyle.
Just for completeness, I'm running a Kaiser with a 1 year old 1600mAh battery, a 2.6.25 kernel and, currently, both Sys and Data are on NAND.
Anyone experiencing anything like this?
Sorry, read too quickly your post.
usually is a radio problem that hang the kernel. try with different radio firmware.
I seem to get one of those about 1 or 2 hours after every kernel flash (that may just be a cooincidence though), and maybe once or twice a week as well.
I haven't been able to identify any app or other thing that might have caused it, as they usually happen when I haven't been using the phone for a while.
Info:
Kaiser 130, 23-11-10 l1q1d kernel, Fat Free Froyo RLS5
I thought it might be something to do with the screen turning on (ie wrong panel type), as when it "freezes", the keyboard lights still go on and off when you open the keyboard. I've never been sure if my Kaiser is panel 2 or 3, but it's happened to me on both panel 2 and panel 3 nbhs, so maybe it's unrelated.
That is a known issue with the .25 kernel did it give you backwards text too? What's weird is its only froyo that has that issue these freezes are also why dzo started porting the new one
Sent from my HERO200 using XDA App
I've never seen the backward text. I'll look at rebuilding with the .32 kernel. Interestingly, it doesn't seem to happen when plugged in (so far). It's only happened once today so I may let it roll for a few days and see what it's like.
I observed it too
Adomatic said:
I've tried several builds and am quite happy with each (getting better and better as I learn more and more). I've gotten newer and newer kernels and builds and am currently using Thoughlesskyle's not so super froyo and am really liking it.
The one deal-breaker issue that's keeping me from using this phone full time is something I'm calling a phone coma. The phone periodically refuses to wake up from sleep. I may have a flashing notification light that makes it look like the phone is sleeping but I am not receiving emails or phone calls when it's in this state. To wake it up, I have to press the reset button.
I think this may be related to battery (http://forum.xda-developers.com/showpost.php?p=9360324&postcount=7) and I'm going to try to debug this a bit but I was wondering if anyone else is seeing this. I don't think it's specifically related to any one build as I've seen this with DZO and Thoughlesskyle.
Just for completeness, I'm running a Kaiser with a 1 year old 1600mAh battery, a 2.6.25 kernel and, currently, both Sys and Data are on NAND.
Anyone experiencing anything like this?
Click to expand...
Click to collapse
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
doghead said:
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
Click to expand...
Click to collapse
have some patience guys, kernel .25 has this issues, and devs are working hard on kernel .32 to solve this problems, this is a linux kernel and has to mount the file system to read it and then unmount it on shutdown, but recently there have been some issues with the unmounting part on the shutdown (like when u just unplug the power cord on a PC and windows restart with the "blue screen") until devs find a solution, its wise to always keep on hand a recent /data backup. Another word of advice: read! i dont want to sound rude, but all this is commented extensively over the forum.... like l1qu1d would wisely suggest: use the search tool!
doghead said:
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
Click to expand...
Click to collapse
the old kernel only does this with froyo if you still want to use android use n eclair build or donut its not the latest and greatest but they are very stable though
Thanks, I may give it a shot (or I may just buy a samsung captivate ). Your build is very good. Doesn't seem to be as quick as some of the others I've tried but yours has been really stable. I've been running it for about a week. The others
This problem doesn't seem to happen when plugged in - it's only when on battery. I've had some app freeze-ups but, in general, the phone has been really nice.
Adomatic said:
Thanks, I may give it a shot (or I may just buy a samsung captivate ). Your build is very good. Doesn't seem to be as quick as some of the others I've tried but yours has been really stable. I've been running it for about a week. The others
This problem doesn't seem to happen when plugged in - it's only when on battery. I've had some app freeze-ups but, in general, the phone has been really nice.
Click to expand...
Click to collapse
yea not so super is a little bloated if you dont mind a little work fat free is very snappy i just has a blue theme
Hey everyone,
I wanted to ask everyone for advice/opinion on my horrible battery life.
I have been trying out 2.0-RC6 for some time now and I love it, except the fact that the battery is drained in about 10 hours. I am coming from LeeDroid 2.2 and could go sometimes 2 days without charging.
I have searched forums, posts, what have you ... tried different kernels, radios. No joy.
I am now running a virgin RC6 with all caches wiped (S-OFF too). What it comes down to is a mysterious drain of about 100mA even when the phone is sleeping (radio on, bluetooth off, wifi off). Which makes no sense... I used to get really low drain with the laggy HTC Sense rom (about 5-10mA). Again - this is a clean rom there are no apps installed on it apart from a battery widget and setCPU.
Why i think it is the radio's fault is that when I do put the phone in airplane mode the power drain goes to 2mA. I have tried most radios, even flashed the 32.49.00.32U_5.11.05.27_RIL and for some reason the radio is still constantly drawing power.
So, I am stumped. I was wondering if any of you have found some tweaks that have worked for you. Have you experienced this kind of problem and do you have any advice as to how I can go about debugging this issue? I have very little knowledge about radios in general but i'm willing to learn.
There have been people with battery drain issues out there, but no one seems to know how to resolve them (or those issues simply go away when they flash a new rom, which hasn't happened for me).
I would appreciate comments from developers who know how to debug those issues and I think this will be of help to everyone.
Thanks
slyn4ice said:
Hey everyone,
I wanted to ask everyone for advice/opinion on my horrible battery life.
I have been trying out 2.0-RC6 for some time now and I love it, except the fact that the battery is drained in about 10 hours. I am coming from LeeDroid 2.2 and could go sometimes 2 days without charging.
I have searched forums, posts, what have you ... tried different kernels, radios. No joy.
I am now running a virgin RC6 with all caches wiped (S-OFF too). What it comes down to is a mysterious drain of about 100mA even when the phone is sleeping (radio on, bluetooth off, wifi off). Which makes no sense... I used to get really low drain with the laggy HTC Sense rom (about 5-10mA). Again - this is a clean rom there are no apps installed on it apart from a battery widget and setCPU.
Why i think it is the radio's fault is that when I do put the phone in airplane mode the power drain goes to 2mA. I have tried most radios, even flashed the 32.49.00.32U_5.11.05.27_RIL and for some reason the radio is still constantly drawing power.
So, I am stumped. I was wondering if any of you have found some tweaks that have worked for you. Have you experienced this kind of problem and do you have any advice as to how I can go about debugging this issue? I have very little knowledge about radios in general but i'm willing to learn.
There have been people with battery drain issues out there, but no one seems to know how to resolve them (or those issues simply go away when they flash a new rom, which hasn't happened for me).
I would appreciate comments from developers who know how to debug those issues and I think this will be of help to everyone.
Thanks
Click to expand...
Click to collapse
Try the 32.54.00.32U_5.14.05.17 radio and use a RIL designed for it also. For me this gives the best battery life. Also set wifi sleep mode to never by going into wifi settings, menu->advanced
Hello Mates,
I am using Wildpuzzle ROM v0.8, which is having many problems in its stage.
The camera fails to operate sometimes. But I do managed to make it working using an external application.
The major issue remains of the BATTERY.
Its been a disaster for me to use it when EDGE 'on'. When the downloading is taking place, this phone starts draining the battery within 30sec for each percent. Presently i get the battery backup of around 120mins max on data usage.
One more issue lies in, the battery wont get charged beyond 71%. I need to reboot so that it shows somewhere more than 90%.
I have tried to reflash the v0.8 rom but facing similar problem again.
Will Radio update be a better option?
Can you recommend any better Sense Enabled Froyo?
Is this the bug in the ROM itself?
Help me, with your suggestions.
Thank You.
Recalibrate your battery. Just perform a search on XDA, there are many guides. It cant be a bug with WildPuzzle because I have personally tested it extensively, and this issue didnt exist.
Only after a fresh flash of a ROM, I get very bad battery life, but this is normal in all ROms I have tried. After 1-2 charge - discharge cycles, it fixes itself.
But because you are facing issues like it doesn't go beyond 71%, then jumps to 90% etc - Your battery definitely needs recalibration.
Hello all. Ever since I got my EVO, I've been experiencing random restarts, even before I was rooted. Right now, I am running CM7.1 and Tiamat from kernel manager, and I probably have to do about 8 restarts and 5 battery pulls a day, no matter how often I use the phone. For instance, today I woke up and had to do a battery pull because the screen would not turn on. The light was also still orange despite the battery being fully charged. I unplugged it at about 8 in the morning and by 10 with no use, I had to pull the battery again because the screen was frozen off once again. Once I got it back on, the battery was down to 80%. I tried using it and half the apps would force close immediately, so I restarted... You get the picture. Some roms have been better than others, and kernels don't seem to make any difference, and I figured it was about normal. Then, I installed what is supposed to be a really buggy CM7 on my touchpad, and have only had to restart it once in the past 2 days, which makes me question how stable my phone actually should be. Does it seem like I should take it in to sprint, or is my experience about normal?
I also never overclock because of my already poor battery life and have tried underclocking, but don't see any noticible difference
bump. should I post somewhere else?
Run an RUU but stay s-off for the moment and see if the problem persists. If your phone begins working properly, then you can flash a recovery and flash whatever rom you want - but don't restore your backup. I'd start totally fresh if RUUing fixes your problems, don't restore your apps and data, just download them from the Market as you need them.
If the RUU doesn't help and the problem continues, take it in to Sprint. It's up to you if you want to s-on before taking it in - I've never heard of anyone getting problems from Sprint with s-off but without root, but I think it's a general rule to do so.
I hope everything works out for you!
Sent from my Evo + MIUI using Tapatalk!
I have heard and seen on here many times that random reboots are caused by battery problems, and bad software installs. Try calibrating the battery, also use battery monitor widget to see what ur batt temps are. Then reinstall all your apps, do not restore them then see if that helps.
Sent from my PC36100 using XDA App
I'll try an RUU when I get enough time to do some thorough testing. I have reinstalled everything directly from the market multiple times since I've had the phone, and also have used a total of four batteries with no change in behavior. I Will try the RUU soon though. Thanks for the replies
Hi everyone,
I just flashed ARHD 7.0.2 on my Desire HD last night and I'm experiencing the following problem:
The CPU remains at 99-100% all the time, the battery drains excessively fast and the phone gets really hot.
Using "Watchdog Lite", I detected that when the CPU does not stay at 100% (after a battery-pull), the "Phone" process uses 0,0% of CPU.
However, for some reason, after a while it will jump up to 80-90% and stay there, causing the CPU to go berserk.
I suppose the heat-issue comes from the fact that the cpu works all the time at 100%.
The battery drain issue comes also from the CPU.
However, I do not know why the Phone process would suddenly go crazy and use that much cpu - and keeps doing it until the battery is dead.
I'm thinking it is because the ARHD 7.0.2 ROM is actually a stock Sensation XL base and thusly requires another RIL than the one that was on it before that.
Before flashing another RIL or radio I would like it very much if somebody could confirm that the fact that the Phone process goes crazy like that could very well be linked to the fact that the RIL and Radio don't match.
It seems obvious, but I don't know enough of the inner workings to verify this, so therefor: this thread
Thanks in advance to all!
sstm
The RIL should be pretty standard between HTC devices so that shouldn't cause any issues. Did you do a full wipe before the install?
Hello TransientMotion,
Yes I did a full wipe, I even cleared the battery stats for good measure.
I even formatted my SD-card to make sure nothing remained from some app somewhere.
The phone is as if I'd have bought it fresh out of the store with ARHD 7.0.2 on it (and rooted of course)
It's just weird to see that the "Phone" process is using this much cpu, even when on Airplane mode.
Thanks for you reply,
sstm
It may be worth trying out an earlier version of the rom just to see what happens. I used 6..3.1 before I switched over to ICS and never had any major problems with it. If that works fine then try newer versions until you get glitches again or it works without the drain
Hey,
I just found out that it is Llama (kebabApp 'location aware' application) who is causing the problem.
Whenever I leave an area and then re-enter it, the CPU goes berserk and stays that way as if some loop can never be interrupted.
I didn't have this problem on ARHD 6.3.1, but I didn't have the same Llama configuration on it either so I tried the Llama config on ARHD 6.3.1 and it did the exact same thing: cpu 100% and slowness all over.
So conclusion: Llama config is the culprit.
Anyways, thanks for you help TransientMotion.
sstm