I have flashed so many custom ROMs and find the dailer mostly drains much battery. the dailer includes phone and dailer storage is always top 2 battery user in the battery statistic.
in fact, I just make a little calls during the whole day, less than 10 minutes.
who can help me?
allen oddest said:
I have flashed so many custom ROMs and find the dailer mostly drains much battery. the dailer includes phone and dailer storage is always top 2 battery user in the battery statistic.
in fact, I just make a little calls during the whole day, less than 10 minutes.
who can help me?
Click to expand...
Click to collapse
You're right, this has been identified before and is mentioned in other threads within this forum, unfortunately no solution has yet been found yet as far as I'm aware.
The dialer is always kept in memory. The app doesn't get killed. Maybe this is the reason.
Sent from my HTC Desire S using XDA Premium App
ben_pyett said:
You're right, this has been identified before and is mentioned in other threads within this forum, unfortunately no solution has yet been found yet as far as I'm aware.
Click to expand...
Click to collapse
I have tried to remove the stock dailer app(htcdialer.app in system/app) and replace with third-part dailer app such as smartdailer. It works well, but the entire dailer still drains so much battery life.
I have no idea.
Didn't want to open a new thread since a found this one, wanted to reactivate it maybe someone had found a solution.
After some hours of google, xda and other forum i didn't find a solution.
Many users mentioned that this issue appeared after the 2.3 Android update.
Even after switching off all the 3 features connected to the proximity sensor the Dialer is still there.
Hopeing for a solution from a brilliant mind here.
Tryed on Runny, Virtuos, Endymion....on all the same issue.
Thanks
cpx07 said:
Didn't want to open a new thread since a found this one, wanted to reactivate it maybe someone had found a solution.
After some hours of google, xda and other forum i didn't find a solution.
Many users mentioned that this issue appeared after the 2.3 Android update.
Even after switching off all the 3 features connected to the proximity sensor the Dialer is still there.
Hopeing for a solution from a brilliant mind here.
Tryed on Runny, Virtuos, Endymion....on all the same issue.
Thanks
Click to expand...
Click to collapse
Tried cyanogenmod? I don't get problems with the dialer, but then again I don't use it very often
Sent from my Desire S using xda premium
Related
sometimes when i unlock the lockscreen it doesnt work, i have to lock it and unlock it again to get it working (this usually happen when im playing games or when i just unlock it...
i searched and i didnt find a thread of this
is this also happening to someone else or is just to me??
im using TB fusion 1,2,0,1
renehd2 said:
sometimes when i unlock the lockscreen it doesnt work, i have to lock it and unlock it again to get it working (this usually happen when im playing games or when i just unlock it...
i searched and i didnt find a thread of this
is this also happening to someone else or is just to me??
im using TB fusion 1,2,0,1
Click to expand...
Click to collapse
You may need to try BROWSING the sections, too. It's been asked a million times.
Non-rom specific touchscreen driver issue it is suspected.
Some people experience it, some don't.
I, for one, haven't, but many people have.
well when you put the topic of the thread it gives you some similar options to your problem and no one of the options was even close to my request so thats why i did it.. can you give the link where was asked the same question as me please?
thank you
Bumb...........!!
Will the touchscreen driver also make parts of the screen non responsive randomly? I am having that happen to me and wondering if I should try and exchange it.
Running Cm7 nightly in case thatd help
I've had this problem on multiple roms.
I've had this issue on multiple roms as well it's not horrible at all though just have to touch it a second time. the weird thing is I can pretty much predict it for example when scrolling through my apps in tibu it gets stuck at the same spot every time. and also the xda app on the first scroll. it's been discussed many times but I'll throw it out there again. NOT A ROM ISSUE, HTC ISSUE. MANY PHONES ARE AFFECTED. don't stress over it
Sent from my Inspire 4G using XDA Premium App
As some of you have come from the captivate know what I did there with Rom Q&A threads. I am doing the same here. In an effort to clean up the site. All Rom related question shall from now on be posted in the proper Q&A or will be deleted on sight.
Just saying it should be Android Revolution HD
Thanks for your effort!
mike1986. said:
Just saying it should be Android Revolution HD
Thanks for your effort!
Click to expand...
Click to collapse
We'll shall change that
Sent from my HTC Inspire 4G using XDA Premium App
WiFi not working?
I just installed this Rom and now wireless is not working any suggestions?
EDIT: It was my router config all is well.
Gps Issues
I love this Rom but I can't get my gps to work very well. I tried Lee's and cyno just didn't like them but the GPS worked. I really don't want to have to switch away from it just because I can't use apps that use my gps ( mapmyrun, google latitude)
Sometimes, it will work with an accuracy of like 800-2000 ft after fixing for 10-15 minutes. I have tried every solution on the Android Revolution F.A.Q section Q.14. It worked fine before and if I switch to a different ROM. Also, I have tried apps like GPS FIX, Faster fix, and Gps essentials. My radio is the suggested one for the ROM.
Any ideas I'm desperate?
Also I have noticed when trying this fix.
http://forum.xda-developers.com/showpost.php?p=12185980&postcount=20784
Under my
gps.conf file (inside system\etc):
I have no gps.conf file at all.
Any ideas?
So my question.. By far ARHD is my favorite rom, the only issue I'm having is that every once in awhile when i try to unlock the phone it won't respond the anything. The only way to get it to turn on again is a battery pull. I remember when I had my captivated I had similar issues but muuuuch worse. I followed the flashing directions line by line and did a full wipe. The last time it happened was today right before I updated to 5.2.4 so ill see if this makes it any better. Any ideas why this is happening, does my processor not like OC and I need to scale it down? Other than that I love everything about the rom thanks in advance for any help.
Does anybody have any idea why I can't set a permanent screen lock? It's like everytime I set a pattern lock or PIN lock, it works once then no longer requires a pattern or PIN to unlock my phone depending on which one I chose to use. Any help would be appreciated.
Sent from my Inspire 4G using XDA App
ryan09266 said:
So my question.. By far ARHD is my favorite rom, the only issue I'm having is that every once in awhile when i try to unlock the phone it won't respond the anything. The only way to get it to turn on again is a battery pull. I remember when I had my captivated I had similar issues but muuuuch worse. I followed the flashing directions line by line and did a full wipe. The last time it happened was today right before I updated to 5.2.4 so ill see if this makes it any better. Any ideas why this is happening, does my processor not like OC and I need to scale it down? Other than that I love everything about the rom thanks in advance for any help.
Click to expand...
Click to collapse
That is a good guess. Test it out by scaling it down and monitoring what the behavior is. Mike's rom should be set at 1.152gHz out of the box. That is not high at all but every phone is different and if you have yours set higher your particular phone may not like it.
XPLiiCiiT said:
Does anybody have any idea why I can't set a permanent screen lock? It's like everytime I set a pattern lock or PIN lock, it works once then no longer requires a pattern or PIN to unlock my phone depending on which one I chose to use. Any help would be appreciated.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
That is a strange one. Mine works with no problems on AR. Sorry I could not give you a better clue as to why this is happening. Possibly try flashing again to see if that solves it. Either that or do you have any lock switch type apps that may be causing some kind of problem?
Wolf_2 said:
That is a strange one. Mine works with no problems on AR. Sorry I could not give you a better clue as to why this is happening. Possibly try flashing again to see if that solves it. Either that or do you have any lock switch type apps that may be causing some kind of problem?
Click to expand...
Click to collapse
Hmm. I don't have any type of apps that could cause this and I've already tried flashing it again but the problem still persists. Oh well, no biggie. Thanks for the reply.
Sent from my Inspire 4G using XDA App
XPLiiCiiT said:
Hmm. I don't have any type of apps that could cause this and I've already tried flashing it again but the problem still persists. Oh well, no biggie. Thanks for the reply.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
After you set the pattern or pin did you change the inactivity setting? I believe default is it will only lock after 5 minutes of inactivity. After you set the pattern/pin the second setting down is "Lock phone after" then gives you the selections immediately, 3 mins, 5 mins and so on. Make sure its set to immediately. That would be my best guess from the info you provided.
cbronson41 said:
After you set the pattern or pin did you change the inactivity setting? I believe default is it will only lock after 5 minutes of inactivity. After you set the pattern/pin the second setting down is "Lock phone after" then gives you the selections immediately, 3 mins, 5 mins and so on. Make sure its set to immediately. That would be my best guess from the info you provided.
Click to expand...
Click to collapse
Yeah, it's set to immediately but still does the same thing. Thanks for the help.
Sent from my Inspire 4G using XDA Premium App
I am currently using this rom and I think its great. The only problem I've had was downloading from the Android market. But it started to work all of a sudden a few days ago.
Thanks for the ROM. Great work.
Well, I just upgraded from 5.2.5 (which I installed this morning) to 5.2.6... very smooth upgrade.
Well, mostly smooth anyway. I have the sense 3.0 lockscreen installed and although it works in terms of pulling the ring up to unlock, there are no icons (and yes, I have configured the ones I want there) and no matter which lockscreen I choose under personalizations, I just get the same background I have on my home screen with no icons, no clock, no weather, no nothin'. I did so a SuperWipe when I installed 5.2.5 this morning, but the dev's notes say you don't have to SuperWipe if you are installing over another 5.2 release.
Incidentally, I saw the exact same misbehavior under 5.2.5 and was hoping it might get fixed.
Other than that it seems to run real well though. Is the 3.0 lockscreen working for others?
Installed the "Restore HTC Lock-Screen for Android Revolution HD 5.2.x " mod to revert to the non sense 3.0 lockscreen, and it works, but I notice that under "personalize -> lockscreen" it still shows the sense 3.0 ones, and lets you modify and select one, but it doesn't work.
Although I normally use an external bluetooth GPS, I just tested the internal one with 5.2.6 and it locked on quickly and gave about 16' accuracy.
I've been using this ROM for the past few days and I think its great.
However, I didn't flash a new radio (the one suggested on the thread). Is that alright? Will I see a huge difference flashing a new radio over the stock one?
does the new APN trick work with AR HD for the wifi tethering?
Hi everyone, my desire s is acting strange since few days back.. it keeps on restarting for no reason. At first I thought its due to kernel updates to modified kernel 3. But then I installed reaper gingerbread. It restarted when I opened camera.
Then I installed Nik's project x . Still same problem sometimes when I open camera or other heavy application.
It restarts continuously 5-6 times without completely booting and battery drains to 10-15% from 80-90% within 5 minutes..
I've not got this problem when in charging mode..
I'm now using ice_ds 4.3
If anyone have same problem before , is there a solution to this?
Thanks in advance..
Sent from my HTC Desire S using xda app-developers app
I think it's my Battery problem. Now it restart as soon as I unplugged the power cable.
I didn't find a way to close this thread,
Could anyone tell me how do I close this thread ?
Just add [Solved] to the front of the title, then people will know (edit the first post)
Sent from my Desire S
uktel3315 said:
Hi everyone, my desire s is acting strange since few days back.. it keeps on restarting for no reason. At first I thought its due to kernel updates to modified kernel 3. But then I installed reaper gingerbread. It restarted when I opened camera.
Then I installed Nik's project x . Still same problem sometimes when I open camera or other heavy application.
It restarts continuously 5-6 times without completely booting and battery drains to 10-15% from 80-90% within 5 minutes..
I've not got this problem when in charging mode..
I'm now using ice_ds 4.3
If anyone have same problem before , is there a solution to this?
Thanks in advance..
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
I get this too on all custom ROMS.. sometimes if I knock the phone a certain way it resets.. so it must be hardware related.
Can you let me know what your 'SOLUTION' is? All I see if the cause. Thx
Ziplock9000 said:
I get this too on all custom ROMS.. sometimes if I knock the phone a certain way it resets.. so it must be hardware related.
Can you let me know what your 'SOLUTION' is? All I see if the cause. Thx
Click to expand...
Click to collapse
Dudeeee read the 2nd post?
Sent from my HTC Desire S
Ziplock9000 said:
I get this too on all custom ROMS.. sometimes if I knock the phone a certain way it resets.. so it must be hardware related.
Can you let me know what your 'SOLUTION' is? All I see if the cause. Thx
Click to expand...
Click to collapse
my solution: buy new battery :laugh:
Put a bit of paper between the battery and the holder clip, that fixed it for me to keep the battery in place.
I have a problem with my phone shutting down randomly sometimes when being used (usually when going online and halfway through the battery bar). After i turn on the phone again the battery would loose about 20% prior to the shut down. Any1 got a solution?
What ROM, kernel are you using? And what is the clocking on the kernel?
Sent from my HTC Sensation 4G using xda app-developers app
I've been using insert coin for awhile for awhile. It started happening a month after i updated to version 2.2. Then i tried using cyanogenmod 9 and it still happens. Then I switch back to insertcoin, but with version 2.3 and still the same thing.
what solutions did you tried until now ?
and did you care to search in q&a section ..there are lot of threads with the exact same random shutdown issues ...and the solutions were posted there..do a quick search in this q&a section and help yourselves
Thanks for the advise, but your suggestion are only for people who are new to the forum. Searching is the first thing I did. I mentioned above that did try changing rom into CM9 and that had the same results. I also checked if the battery is loose, but it wasn't. If there is a particular solution that I missed please point me to the thread.
qpqpqp said:
Thanks for the advise, but your suggestion are only for people who are new to the forum. Searching is the first thing I did. I mentioned above that did try changing rom into CM9 and that had the same results. I also checked if the battery is loose, but it wasn't. If there is a particular solution that I missed please point me to the thread.
Click to expand...
Click to collapse
see..i was about to give you the thread which solves battery loose connection ..thats why i said what solutions you tried ..if you have updated that in OP that would prevent people from posting the solutions that you already tried ..
now to the point ..reflash the firmware that you are using and see..as changing roms didnt solved your issue
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
koszor said:
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
Click to expand...
Click to collapse
It only happens for some people and the reason behind it is unknown. For some it is a major issue, and for others it's never existed. Only way to get it to (maybe only temporarily) go away is to reboot. Not much you can do about it, but some have said it's better if camera apps are changed to user apps rather than leaving them as system apps.
Lethargy said:
It only happens for some people and the reason behind it is unknown. For some it is a major issue, and for others it's never existed. Only way to get it to (maybe only temporarily) go away is to reboot. Not much you can do about it, but some have said it's better if camera apps are changed to user apps rather than leaving them as system apps.
Click to expand...
Click to collapse
Interesting, do you think running a custom ROM or a different kernel will help... or hope and pray Android L fixes it?
koszor said:
Interesting, do you think running a custom ROM or a different kernel will help... or hope and pray Android L fixes it?
Click to expand...
Click to collapse
I doubt it, it might be a hardware driver issue, nobody knows what the real cause is. Personally I don't have this issue, I don't think another ROM or kernel will change anything much, although it's worth a shot if the drain applies to you.
It gives me a good reason to change ROMs.. haha. Ill give it some time and see what happens thanks for the quick reply so early in the morning!
koszor said:
It gives me a good reason to change ROMs.. haha. Ill give it some time and see what happens thanks for the quick reply so early in the morning!
Click to expand...
Click to collapse
Depends where you are in the world.. 10:46pm here in Australia. :angel:
But yeah, I have no idea if another ROM would fix the issue in any way. If it helps a little it's more likely because it's a clean flash, not because of the ROM itself, but who knows. Kernel won't affect this at all.
well, the camera daemon is normal to show up, especially when you use the camera or apps that use the camera. and its normal for it to take a larger % of battery than the camera app itself. what you havent really done is actually describe your problem. as far as i know, you dont have an issue, at least until you describe it. again, its normal for the camera daemon to appeae. now please, describe your actual problem. screenies?
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
what's not normal is if it continues to drain battery, which i havent seen personally in a while, nor read any real complaints on it in a long time.
koszor said:
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
Click to expand...
Click to collapse
I've heard it only happens now when you leave the offending app that uses the camera (snapchat, skype, etc) running in the background. I can't confirm though as I've never had the issue even before the update.
simms22 said:
well, the camera daemon is normal to show up, especially when you use the camera or apps that use the camera. and its normal for it to take a larger % of battery than the camera app itself. what you havent really done is actually describe your problem. as far as i know, you dont have an issue, at least until you describe it. again, its normal for the camera daemon to appeae. now please, describe your actual problem. screenies?
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
what's not normal is if it continues to drain battery, which i havent seen personally in a while, nor read any real complaints on it in a long time.
Click to expand...
Click to collapse
I can confirm I have the continual drain, unfortunately this was the other day and since then I have rebooted and charged my phone. I'm glad its only once in a while but from what I researched it should have been fixed in 4.4.4.
More info is available in the link I posted in the 1st post including screenshots and even links to XDA. The problem I have experienced a few times so far on 4.4.4 is identical to the link in OP.
bblzd said:
I've heard it only happens now when you leave the offending app that uses the camera (snapchat, skype, etc) running in the background. I can't confirm though as I've never had the issue even before the update.
Click to expand...
Click to collapse
Its gotta be snapchat, it used to lock up and soft boot my nexus 4 from a 'bug' or something like that ><
oh well, ill just have to keep an eye out for it.. I will try CM for a month or so and post my results back tho!
koszor said:
I can confirm I have the continual drain, unfortunately this was the other day and since then I have rebooted and charged my phone. I'm glad its only once in a while but from what I researched it should have been fixed in 4.4.4.
More info is available in the link I posted in the 1st post including screenshots and even links to XDA. The problem I have experienced a few times so far on 4.4.4 is identical to the link in OP.
Click to expand...
Click to collapse
do you have any apps that use the camera? and i mean any, there are many. if you used that app, and iy continued running in the background, the the camera daemon would also run in tbe background. if it is the old camera daemon issue that youre experiencing, then it would happen every time the camera is used, not occasionally. if its only once in a while, something else is causing your issue. i had the issue before, every single time i used the camera, not occasionally.