Database Users

[HELP] DHD wakes up by itself

Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!

I've a similar problem a bunch of months ago, my phone turn on automatically, without no logic. I've resolved the problem pulling out the battery for a night, after that the problem disappeared.
I hope that will help you to resolve your problem,
Rodomar705

Thanks, I will try that out tonight and report!

Ok, I tried it out last night, but it did not work
Does anybody have a different idea?

Dabarr said:
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Click to expand...
Click to collapse
Did you check the date and time once you'd insert battery inside DHD? I think to solve the problem that way, you should leave DHD without battery until the internal battery will be totally discharged. It takes approx. 12-14 hours, and you can be sure only if turning on DHD you'll find time and date set to 12:00am, 1st jan 1980 (or something like that).

Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^

Dabarr said:
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
Click to expand...
Click to collapse
same here, i have the MIUI ROM, will try with another version.

Dabarr said:
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Click to expand...
Click to collapse
Sorry mate!! Just wait for a week, ist not so long time, and you'll get back your phone as new as when you bought first time!! Hope this makes you feel a little bit of joy!!

Ok, I have gotten my phone back on thursday (after one week)...
SO far so good, everything worked again, they even set the proximity sensor right again... Then I rerooted it and put another MIUI on it...
On friday then, I put Vipermod back in and undervolted it by 50 mA... BOOM, the issue came back, I couldn't remove it, so I took the battery out and waited for 12 hours, as you suggested... and it worked... Issue was gone... Then I ran vipermod again and BOOM the issue was there again... It didn't even help to set the mA values back to normal, I had to reset it again by taking out the battery for 12 hours.
So my conclusion is that this issue is directly related to the actual USE (not just the installation) of vipermod... Can anyone confirm? Don't want to put out false information in the vipermod thread without having others to confirm...

need help also

Stinger696 said:
need help also
Click to expand...
Click to collapse
have you tried pulling out the battery already?

xlxl said:
same here, i have the MIUI ROM, will try with another version.
Click to expand...
Click to collapse
As I have stated before: Rom change haven't helped me.. Did it work for you ???

Dabarr said:
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Click to expand...
Click to collapse
If changing the ROM didn't help then it is an app issue. One of your apps is causing it. Time to look deeper

I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).

freakshock said:
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
Click to expand...
Click to collapse
Only way to find out is to test them one by one by reinstalling them one at a time

Quarx' CM11 latest: Phone Problem needs reboot

Since 20140415 nightly update (installed via CMupdater) I'm experiencing the Phone Problem. The translated German text would be
"there was a problem with your phone's modem, the device needs to be rebooted..."
I've had those before, but to a small extend. Now it's more like: it takes around 30 Minutes from reboot until the "Problem" reappears.
I'm sorry, I cannot post to the dev-thread, yet. If any logs are needed, I'd update back to 20140415 or 20140416 (where this also happened) and try to grab'em.
EDIT: it might be important information: I've come from the "full" nightly "11-20140407-NIGHTLY_mb526", then used cmUpdater on the 14th, the 15th and the 16th April (so: the last three days), at least that are the files present in my /sdcard/cmupdater folder. The problem has appeared yesterday.
Question: if I do incrementals, will I have to update every day?

oops - it seems not to be the ROM I guess
As I didn't have those problems with 20140407, I downgraded to that version. Seems it didn't have an effect - just about half an hour after downgrade, I had the "Problem", again.
I'll reboot once and if the "Problem" reappears at the same rate, I'll do a full-wipe reinstall.

St0fF said:
As I didn't have those problems with 20140407, I downgraded to that version. Seems it didn't have an effect - just about half an hour after downgrade, I had the "Problem", again.
I'll reboot once and if the "Problem" reappears at the same rate, I'll do a full-wipe reinstall.
Click to expand...
Click to collapse
It is a hardware problem of the Defy, it will go away with time.

hotdog125 said:
It is a hardware problem of the Defy, it will go away with time.
Click to expand...
Click to collapse
I'm having this since 3 days and I'm barely reachable because of that - what are the experiences, how long may it take until this goes away?

St0fF said:
I'm having this since 3 days and I'm barely reachable because of that - what are the experiences, how long may it take until this goes away?
Click to expand...
Click to collapse
For me, the system stabilises after 36 hrs of uptime.

Defy / temporary failure
hotdog125 said:
For me, the system stabilises after 36 hrs of uptime.
Click to expand...
Click to collapse
That sounds really weird! After it stabilizes - when does the problem return? Any idea what caused this effect?

mklmkl said:
That sounds really weird! After it stabilizes - when does the problem return? Any idea what caused this effect?
Click to expand...
Click to collapse
It doesn't return. Hence I said the system stabilizes.
Sent from my Nexus 7 using Tapatalk

Try to flash new modem.Latest or just different.Try BasesbandSwitcher .I Had simillar problems with CM10 and I dont know how exactly i solved it - flashing,switching,trying...Some says that CM ROMs dont change the modem because it have no modem in CM ROMs.

That's the infamous RIL bug. Try disabling and re-enabling location. Doesn't make much sense, but fixed it for me.

propov said:
Try to flash new modem.Latest or just different.Try BasesbandSwitcher .I Had simillar problems with CM10 and I dont know how exactly i solved it - flashing,switching,trying...Some says that CM ROMs dont change the modem because it have no modem in CM ROMs.
Click to expand...
Click to collapse
That's what fixed it for me: I reflashed to factory, then installed cm10/cm11 freshly.
dau_ said:
That's the infamous RIL bug. Try disabling and re-enabling location. Doesn't make much sense, but fixed it for me.
Click to expand...
Click to collapse
Thanks for that information - I'll try to remember next time I get banged by this.

Another search result
[email protected],
i just thought about perhaps creating another thread that may be made sticky, collecting all possible reasons, explanations and most likely workarounds for the RIL Bug - and I found this answer:
http://forum.xda-developers.com/showpost.php?p=50830467&postcount=5
It says undervolting might be a factor. My Defy is undervolted. So I'll try to figure out some less extreme settings, as RIL just reappeared on my phone.
P.S.: I couldn't find that post originally, as at that time I wasn't aware of the bug's name - searching for "RIL bug" in fact returns a lot of results.

St0fF said:
That's what fixed it for me: I reflashed to factory, then installed cm10/cm11 freshly.
Click to expand...
Click to collapse
that's the only thing which helped me too. many rom's worked okay for me and had no RIL reboots ever, but when i've tried to use them again instead of newer ones i tried - i got constant reboots. reflashed to factory and no more ril's again.

Discussion Thread : Cm12 unofficial rom by Grarak

Hi buddies
As Grarak chose to close the thread of his rom and that maybe some of you want to have some more return and exchanges about the way the rom works, discuss about bugs etc, i open this thread, so that we will be able to do what a forum is done for : talk and exchange together.
New version is 12082014, any return?
Testing soon..

Is calling with sim 2 in 2g working Now?
If not how to use it Any tetsters!
Edit :still No sound from sim2
and there is No way to chose network type
and No 3g from sim 2 too

Im on 9-12-14 build....2g sim not working same as official cm11....3g sim is working......

i 've had terrible battery life, and searching on google lead me to a battery misc processus eating battery, problem solved with 5.0.1 by google
do you guys have the same experience, and have heard about a fix incorporation in the new builds? :good:

I had to go all the way back to the 11-20-14 build. I tried updating to the new builds 12-8, 12-9 and 12-10. No data at all on any of these builds.

Flashed the newest build! We're on Lollipop 5.0.1 now This update is supposed to help battery life. We'll see.
The new music app automaticaly force closes, and the DSPmanager was replaced with AudioFX.

thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?

fabulous69 said:
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
Click to expand...
Click to collapse
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.

FoxyDrew said:
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
Click to expand...
Click to collapse
mhm then i think a change that has broke the app. I m sure Grarak will correct it in the next release

Ok, the ROM was going great for me, then yesterday at work my phone turned off when it was in my pocket. I tried turning it on, it booted, started doing the boot animation and then did that for five minutes before it shut off again. This time it wouldn't turn back on no matter how many times i tried power cycling or booting into bootloader. When I got home I tried charging it and the light wouldn't even come on. So I plugged it into my PC and the phone showed up as qhsusb_bulk. After researching that i found it means the bootloader got wiped somehow. My question is, how could my bootloader be gone, because as far as I know, no one has gotten their device S-OFF.

your device is bricked
seems there is a solution on the web but not working for everybody and for specific devices
i dont know what to advice you...
i dont know if it is rom related, but if it is, i wont flash this !

Yes that's what i figured. Luckily Amazon was nice enough to give me a new phone once I send that one in. I was just trying to figure out how it would even be possible that my bootloader got fried, considering my device was still S-ON.

any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not

DRAGONMM2010 said:
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
Click to expand...
Click to collapse
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.

kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
Completely agreed.

kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx

fabulous69 said:
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
Click to expand...
Click to collapse
Didn't test it. Haven't spent enough time on Lollipop because of the no data issue.

I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.

thirteen_percent said:
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
Click to expand...
Click to collapse
Yah data works...just not good. It has to do with not being able to access APN's.
No one want's to sit "for a WHILE" to open a webpage or read an email.

On the latest build, System UI crashes.

Smart Lock not working 90% of the time.

Currently running the latest Chroma rom with the stock kernel. The little circle that's supposed to show up around the lock icon at the bottom doesn't show up 90% of the time (http://prntscr.com/abhku3). I'm trying to unlock it with a bluetooth (not NFC) fitness band.
This isn't a problem with the band, because I tried putting Face Unlock as well, but the detection doesn't show up most of the time.
Is there any way to fix this?

sixaxis94 said:
Currently running the latest Chroma rom with the stock kernel. The little circle that's supposed to show up around the lock icon at the bottom doesn't show up 90% of the time (http://prntscr.com/abhku3). I'm trying to unlock it with a bluetooth (not NFC) fitness band.
This isn't a problem with the band, because I tried putting Face Unlock as well, but the detection doesn't show up most of the time.
Is there any way to fix this?
Click to expand...
Click to collapse
I haven't had an issue with smart unlock before, I pair it with my Moto 360. I don't know if it's the kernel because I personally use the Taurus kernel and not the stock one, that might be a reason but again I don't know for sure at all. Maybe on Multirom I'll install a second Chroma and leave it on stock and see if I can get it to reproduce what you're having, I'll get back to you in about 20-30 minutes on how it goes.
-Edit- Might be a bit longer since I need to redownload the latest build. My internet can be slow at times
-Edit 2- I haven't had the issue, at least with my watch. Not too sure how much further I could help you :/

fireball0093 said:
I haven't had an issue with smart unlock before, I pair it with my Moto 360. I don't know if it's the kernel because I personally use the Taurus kernel and not the stock one, that might be a reason but again I don't know for sure at all. Maybe on Multirom I'll install a second Chroma and leave it on stock and see if I can get it to reproduce what you're having, I'll get back to you in about 20-30 minutes on how it goes.
-Edit- Might be a bit longer since I need to redownload the latest build. My internet can be slow at times
-Edit 2- I haven't had the issue, at least with my watch. Not too sure how much further I could help you :/
Click to expand...
Click to collapse
Thanks for helping out! I tried with the Quanta v10 kernel but had the same problem. Reinstalled the rom. No dice :/
This is strange

sixaxis94 said:
Thanks for helping out! I tried with the Quanta v10 kernel but had the same problem. Reinstalled the rom. No dice :/
This is strange
Click to expand...
Click to collapse
It is a bit strange. I do have one final thing to test out actually. I just remembered my girlfriend got a generic bluetooth fitness band thing for her senior year, I'll charge that up and see if that gives the same issue since I still have the multirom boot with it. It'll take probably an hour to charge it since it's just a generic one.

fireball0093 said:
It is a bit strange. I do have one final thing to test out actually. I just remembered my girlfriend got a generic bluetooth fitness band thing for her senior year, I'll charge that up and see if that gives the same issue since I still have the multirom boot with it. It'll take probably an hour to charge it since it's just a generic one.
Click to expand...
Click to collapse
I'm certain it's not the band's fault cause gave unlock isn't detected either. I'll try the pure nexus and cm roms to see if it makes a difference.

sixaxis94 said:
I'm certain it's not the band's fault cause gave unlock isn't detected either. I'll try the pure nexus and cm roms to see if it makes a difference.
Click to expand...
Click to collapse
Especially if the band was working fine on other roms or devices. CM 13 is my main daily driver rom and I haven't had a single issue with several bluetooth devices I own, I always will recommend it xD The fitness band is almost charged and I'll test that out here real soon

fireball0093 said:
Especially if the band was working fine on other roms or devices. CM 13 is my main daily driver rom and I haven't had a single issue with several bluetooth devices I own, I always will recommend it xD The fitness band is almost charged and I'll test that out here real soon
Click to expand...
Click to collapse
I only got the band 2 days ago and have just tested it on Chroma.
Quick question, does CM13 support Volume Key to unlock AND double tap status/nav bar to lock? My power button is screwed up and it barely registers. Also, are the latest nightlies stable or should I go with an older build, if I don't plan to update my rom in the next month?

sixaxis94 said:
I only got the band 2 days ago and have just tested it on Chroma.
Quick question, does CM13 support Volume Key to unlock AND double tap status/nav bar to lock? My power button is screwed up and it barely registers. Also, are the latest nightlies stable or should I go with an older build, if I don't plan to update my rom in the next month?
Click to expand...
Click to collapse
Double tap to sleep, yes. Let me quick boot into it to make sure for the volume key. If you get Kernel Auditor and the right kernel you can have double tap to wake which is wonderful. Ok it does have the option for volume key unlock. I haven't had any issues with the nightlies, a while back I had one that would randomly freeze my touchscreen but that was early last month.

fireball0093 said:
Double tap to sleep, yes. Let me quick boot into it to make sure for the volume key. If you get Kernel Auditor and the right kernel you can have double tap to wake which is wonderful. Ok it does have the option for volume key unlock. I haven't had any issues with the nightlies, a while back I had one that would randomly freeze my touchscreen but that was early last month.
Click to expand...
Click to collapse
Sweet, I'll give CM a shot! I hope the smart unlock was a rom problem and not a hardware one. My phone's nearing the end of it's life, so it's more than possible.

sixaxis94 said:
Sweet, I'll give CM a shot! I hope the smart unlock was a rom problem and not a hardware one. My phone's nearing the end of it's life, so it's more than possible.
Click to expand...
Click to collapse
How's CM holding up for you? Is Smartunlock working on it at all?

fireball0093 said:
How's CM holding up for you? Is Smartunlock working on it at all?
Click to expand...
Click to collapse
I haven't gotten around to it yet. I'll try it later this week and report back

fireball0093 said:
How's CM holding up for you? Is Smartunlock working on it at all?
Click to expand...
Click to collapse
It was a problem with Chroma. I'm running CM now and the Smart Lock works flawlessly!

sixaxis94 said:
It was a problem with Chroma. I'm running CM now and the Smart Lock works flawlessly!
Click to expand...
Click to collapse
Glad to hear it's working! I've been having some issues on Marshmallow in general lately, contacts aren't syncing from Google. But, I'm gonna open up my own help thread for that xD

phone Doesn't gets unlocked back when screen goes in sleep mode

I recently flashed a custom mokee rom ( android M) after removing MIUI 9 on my redmi 2 prime. the rom works fine but when i leave the phone in idle state and when the screen gets locked after that if i try to unlock the phone it doesn't show anything on screen except the notification lights..

It happens to me too. I also need help on this topic. I can send logcat for fatal errors if needed. I wanted to create a new thread but found someone having the same problem as me. Any rom I flash( From Lollipop to Oreo) faces this problem. The phone refuses to turn on or restart even it I hold the power button well over 15 seconds. I tried calling my device in this state and I found out that the phone is switched off ( or atleast the sim card services are not active ). The only roms working are either miui or some modded version of the same (presently using MIUI pro). This problem didn't exist a few months back. This started after I tried out MIUI 9 which I think is not good enough. I don't suppose there's something wrong with the hardware because MIUI works just fine on it. But this does happen to me on MIUI if I I don't use the phone for a really long time ( eg for 12 hrs).

Same problem
S4xk said:
It happens to me too. I also need help on this topic. I can send logcat for fatal errors if needed. I wanted to create a new thread but found someone having the same problem as me. Any rom I flash( From Lollipop to Oreo) faces this problem. The phone refuses to turn on or restart even it I hold the power button well over 15 seconds. I tried calling my device in this state and I found out that the phone is switched off ( or atleast the sim card services are not active ). The only roms working are either miui or some modded version of the same (presently using MIUI pro). This problem didn't exist a few months back. This started after I tried out MIUI 9 which I think is not good enough. I don't suppose there's something wrong with the hardware because MIUI works just fine on it. But this does happen to me on MIUI if I I don't use the phone for a really long time ( eg for 12 hrs).
Click to expand...
Click to collapse
Exact same problem .... Can send log

I am also facing the same problem...i tried almost every rom.But still i have this problem... everything works well in miui..but its not well in custom rom...

Are we the only ones who is facing the issue?? Any dev who can help us out??

S4xk said:
Are we the only ones who is facing the issue?? Any dev who can help us out??
Click to expand...
Click to collapse
i have asked some of the developers,but they are not providing and solution for this...and this bsod is happening in not in every phone...only in selective number of phones... so we r in tht selective list

Dan_nomad said:
i have asked some of the developers,but they are not providing and solution for this...and this bsod is happening in not in every phone...only in selective number of phones... so we r in tht selective list
Click to expand...
Click to collapse
Is it the hardware??

S4xk said:
Is it the hardware??
Click to expand...
Click to collapse
it can't be a hardware problem... because stock rom works very well without any problem...

Guys, I think I've figured something out... The lineage os (Oreo-8.1) ROM is not facing this problem, when the hotspot is turned on. Every thing works fine except the battery life sucks. I think something's wrong with doze mode. Some apps that prevent doze also help in this case.

Aosp based roms doesnt have sod on my device, but all los based roms got sod

What is sod BTW??