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??
Related
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
So I switched to GB from WM65 and found it's pretty slow but usable. I don't have time to switch back to WM65 so I'll stick with GB.
Now, one big issue I have is the phone app (not wifi app, just plain phone). When I dial a number, the screen goes black to prevent pressing the wrong button with your ear etc. Problem is, I can't get back to the screen, meaning I don't have access to the dialpad. Annoying when you're on queue and you need to press a key to get to a menu... like repeat a message on your messagebank for instance.
Second issue, is after the call, the phone is frozen for about a minute or two. Nothing responds. Then it comes back alive.
I haven't found any threads on this, though users seem to complain about wifi calling, which is not my case.
Anyone has seen this ?
Txs.
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
I had this problem with almost every gingerbread build on my HD2.
Im not sure what's causing it, but i fixed this issue by installing screebl lite from play store. While this app enabled, phone would wake up normally after a call in 99.9% of the cases. You should try the same.
Strangely, i don't have any issues on ICS or JB roms.
Marvlesz said:
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
Click to expand...
Click to collapse
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Boags said:
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Click to expand...
Click to collapse
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Marvlesz said:
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Click to expand...
Click to collapse
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Boags said:
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Click to expand...
Click to collapse
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Marvlesz said:
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Click to expand...
Click to collapse
Right, I'll go with the hypothesis that a dirty screen hinders proximity sensors. That should affect a black screen DURING a call (issue I'm also facing) but that should not affect the phone once the call is terminated, should it ? What I mean is, in my case, when I hang up a call, I can't use my phone for a couple of minutes, until it comes back to life. I will get a new "screen protector" and see what happens in the meantime though.
As for a hotfix, seems odd there is none out there. Thanks for trying.
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.
Hi Guys,
I have a big problem. I bought a Redmi 3s for a family member. It has the bloatware rom from Tinydeal so I installed the global developer version on it. I needed the dev version because my relative cannot speak english and that version has Hungarian support. So the phone seemingly works fine but in about every 2 day it just turns off. And it does not turn of properly because we need to push the power button for about 1 minute to turn on and last time we needed to push the power+volume button to turn on.
Just one additional note. I dont know if the phone is really turned off or it is just froze but it acts like it was turned off.
Does anyone has any idea what could be the problem? I hope it is not a hardware issue because sending back will not be quick...
I hope someone could help me. Thanks
mad.droid said:
Hi Guys,
I have a big problem. I bought a Redmi 3s for a family member. It has the bloatware rom from Tinydeal so I installed the global developer version on it. I needed the dev version because my relative cannot speak english and that version has Hungarian support. So the phone seemingly works fine but in about every 2 day it just turns off. And it does not turn of properly because we need to push the power button for about 1 minute to turn on and last time we needed to push the power+volume button to turn on.
Just one additional note. I dont know if the phone is really turned off or it is just froze but it acts like it was turned off.
Does anyone has any idea what could be the problem? I hope it is not a hardware issue because sending back will not be quick...
I hope someone could help me. Thanks
Click to expand...
Click to collapse
I have been facing this type of problem for almost two months. I was using xiaomi eu weekly rom. most of the time it shutdowns in pocket. I have searched in net about this problems and found no permanent solution. Later, I saw that someone told about proximity sensor issue. After deep sleep in whole night, it started the problems. So, he told to restart the phone after waking up in the morning. So, I did and it never shutdown in the whole day but did shutdown at night. I tried stable rom instead of dev rom. Seems like stable rom has less issue with it because i used stable rom more than 3 days and it never shutdowns during that period.
nafeesdipta said:
I have been facing this type of problem for almost two months. I was using xiaomi eu weekly rom. most of the time it shutdowns in pocket. I have searched in net about this problems and found no permanent solution. Later, I saw that someone told about proximity sensor issue. After deep sleep in whole night, it started the problems. So, he told to restart the phone after waking up in the morning. So, I did and it never shutdown in the whole day but did shutdown at night. I tried stable rom instead of dev rom. Seems like stable rom has less issue with it because i used stable rom more than 3 days and it never shutdowns during that period.
Click to expand...
Click to collapse
Hi. Thanks for your comment. Unfortunately I cannot user the global stable nor the eu rom as none of them the Hungarian language support my relative needs. I might try this restart everyday method...
mad.droid said:
Hi. Thanks for your comment. Unfortunately I cannot user the global stable nor the eu rom as none of them the Hungarian language support my relative needs. I might try this restart everyday method...
Click to expand...
Click to collapse
Restart or turn off your device for 2-3 minutes. And please tell us it works for you or not.
Looks like restart method every morning is not working. device shutdown mostly in pocket in beta eu & official rom. I used eu 8.0.5 stable rom for around 2-3 days without shutdown issue. now I flashed 8.0.6 eu stable rom and lets see how this thing go.
Hi there, here is my problem.
I flashed Havoc V2 latest rom and i experience random reboots or shutdowns, including time reset. Problem is that i am away from PC for a few days and i can't try many things since i don't use an sd card, so full wipe is not an option right now.
Also, i noticed that time and date is reseting to rom's build date and not at a random one. Any ideas what is going wrong and how can i fix it will be appreciated.
Thank you in advance.
akisg said:
Hi there, here is my problem.
I flashed Havoc V2 latest rom and i experience random reboots or shutdowns, including time reset. Problem is that i am away from PC for a few days and i can't try many things since i don't use an sd card, so full wipe is not an option right now.
Also, i noticed that time and date is reseting to rom's build date and not at a random one. Any ideas what is going wrong and how can i fix it will be appreciated.
Thank you in advance.
Click to expand...
Click to collapse
Any chance of using OTG +USB stick?
Regarding time : did you try to uncheck automatically time taken from network to a manual setting?
bmwdroid said:
Any chance of using OTG +USB stick?
Regarding time : did you try to uncheck automatically time taken from network to a manual setting?
Click to expand...
Click to collapse
That's not an option right now, but if i find a USB stick i'm gonna give it a try with a different rom.
I'm having the time reset prob when time is set to manual, in network mode seems ok, but reboots/shutdown are still happening.
I was thinking maybe its a modem issue since i never flashed one (maybe there is an updated version that i missed, phone was sitting powered off with an old rr version for a long time) or a kernel issue, but i didn't see any reports on the havoc thread.
akisg said:
That's not an option right now, but if i find a USB stick i'm gonna give it a try with a different rom.
I'm having the time reset prob when time is set to manual, in network mode seems ok, but reboots/shutdown are still happening.
I was thinking maybe its a modem issue since i never flashed one (maybe there is an updated version that i missed, phone was sitting powered off with an old rr version for a long time) or a kernel issue, but i didn't see any reports on the havoc thread.
Click to expand...
Click to collapse
It doesn't help you right now but I've tested several Q ROMs and I've found crDroid 6.9 the most stable one.
With Havoc and AOSP I had issues while lineage doesn't offer that many individuality.
Used RR 7 by mobspyguy myself before switching as it got any longer patches.
Gotta admit that mine is only a backup device and I don't use it longer then 5 hours.
If you used the latest firmware before switching to custom ROM there's no newer modem anyhow.
Thanks a lot for the info. I'm gonna flash another rom when i get the chance to see if the problem is rom related and see how it works.
Thanks again
akisg said:
Thanks a lot for the info. I'm gonna flash another rom when i get the chance to see if the problem is rom related and see how it works.
Thanks again
Click to expand...
Click to collapse
the emmc is dying
you can try this https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448
or try this
as long as you can (until reboots) - download quickly an app - https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
this app will stop the phone going in deep sleep
launch the app Wake Lock PowerManager - set it on partial wakeup (level 4), it's doing it's job pretty well , no big deal on battery consumption
my son has it a 910F and it's still working after 5 months with this app installed
w41ru5 said:
the emmc is dying
you can try this https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448
or try this
as long as you can (until reboots) - download quickly an app - https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
this app will stop the phone going in deep sleep
launch the app Wake Lock PowerManager - set it on partial wakeup (level 4), it's doing it's job pretty well , no big deal on battery consumption
my son has it a 910F and it's still working after 5 months with this app installed
Click to expand...
Click to collapse
Thanks, i was looking into this thread when i was searching for my problem and now i'm gonna give it a try when i get back home, since the wakelock app seems that is not working in my case. As i was afraid, it looks like a hardware issue after all.
akisg said:
Thanks, i was looking into this thread when i was searching for my problem and now i'm gonna give it a try when i get back home, since the wakelock app seems that is not working in my case. As i was afraid, it looks like a hardware issue after all.
Click to expand...
Click to collapse
sorry for your loss