Quarx' CM11 latest: Phone Problem needs reboot - Defy Q&A, Help & Troubleshooting

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.

Related

[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

[Q] Phone is frozen after a call

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.

Crackling Audio Problem

I originally had this audio problem around 3 weeks ago while playing a game so I rebooted and it was working fine again.
A few minutes ago, exactly the same problem has happened again and a reboot hasn't resolved it, this time.
Here's a recording of the audio problem I'm having - http://db.tt/aqB3EM0W
EDIT - Again, it has sorted itself out but there's still clearly an underlying problem to have caused this.
If anyone's had this problem before, could you let me know how you fixed it and roughly how much it cost (if you took it to a repair shop)?
Thanks in advance
KidCarter93 said:
I originally had this audio problem around 3 weeks ago while playing a game so I rebooted and it was working fine again.
A few minutes ago, exactly the same problem has happened again and a reboot hasn't resolved it, this time.
Here's a recording of the audio problem I'm having - http://db.tt/aqB3EM0W
EDIT - Again, it has sorted itself out but there's still clearly an underlying problem to have caused this.
If anyone's had this problem before, could you let me know how you fixed it and roughly how much it cost (if you took it to a repair shop)?
Thanks in advance
Click to expand...
Click to collapse
I had the same problem.I just opened the back cover and hit the mics with my finger several times. Since than I am not facing it anymore. I'm not telling its gonna work for you but you can give it a shot.
I had this problem as well but I fixed it. I found out the culprit causing it was the ROM that I was using. So I flashed back to stock and the crackling was gone! Whew.
Sent from my Nexus 4 using Tapatalk 2
I am facing crackling sound in headphone & also even in speakers , what problem will be ? Its terrible sound, cant even play any music .
KidCarter93 said:
I originally had this audio problem around 3 weeks ago while playing a game so I rebooted and it was working fine again.
A few minutes ago, exactly the same problem has happened again and a reboot hasn't resolved it, this time.
Here's a recording of the audio problem I'm having - http://db.tt/aqB3EM0W
EDIT - Again, it has sorted itself out but there's still clearly an underlying problem to have caused this.
If anyone's had this problem before, could you let me know how you fixed it and roughly how much it cost (if you took it to a repair shop)?
Thanks in advance
Click to expand...
Click to collapse
Which rom/kernel are you running with it?
kilometers4 said:
Which rom/kernel are you running with it?
Click to expand...
Click to collapse
Completely stock. Not even rooted. Since I edited the OP last to mention that it's fine again, it hasn't done it since but there's always a chance it could do it again.
KidCarter93 said:
Completely stock. Not even rooted. Since I edited the OP last to mention that it's fine again, it hasn't done it since but there's always a chance it could do it again.
Click to expand...
Click to collapse
Maybe try rooting? Might solve the problem. I'm rooted and have never had that issue.
kilometers4 said:
Maybe try rooting? Might solve the problem. I'm rooted and have never had that issue.
Click to expand...
Click to collapse
I think the problem must lie deeper than that somewhere because I stayed stock for a few months after getting it without a problem. I then decided to root + flash some ROMs, still with no problem. Then I had no problem for ages even after coming back to complete stock again.
I think I'll just have to wait and see if it does it again and then take it to a mate who'll be able to find out why it's done it and probably fix it

After the New Update Exynos Model (BUGS)

Hello Guys,
I am from India, I got the latest update attached screenshot.
I am facing few issues:-
The phone has become laggy in some departments such as:
1. The fingerprint mark stays on the screen after the screen unlocks.
2. Even after pressing the power button screen doesn't lock. The screen does black out but when I double tab on the screen it directly takes me to the home screen without showing the lockscree first. I am not using Google trusted location or devices to unlock without taking my fingerprint or face recognition.
3. When I try to dial a number it doesn't call at a single go, after pressing multiple times it calls the person whom I am trying to call. It looks very choppy as if the system responding to my commands little later.
4. Whenever I am trying to take the screenshot it doesn't take at a single go, after pressing multiple times the system recognises I am trying to take the screenshot and respond little later.
All the apps are working fine without any lags but the above said things are bothering me a lot.
I hope someone from XDA can assist me with this.
P.S.: I have tried to clear the cache from the boot screen. Also did a test on graphics from the same menu.
****Update v1****
I have got something to support my comments!
https://www.sammobile.com/2019/05/27/latest-galaxy-s10-update-has-some-serious-bugs/amp/
*****Update v2****
Switch off your WiFi, your phone will start behaving normal you will not face this problem in Mobile data usage.
Credit goes to @Whiskey103
None of these problems here. All that tested and works fine. Phone is super fast after update. Oh and i didnt format the phone after update
klemen241 said:
None of these problems here. All that tested and works fine. Phone is super fast after update
Click to expand...
Click to collapse
Thanks for your reply! I hope somebody facing similar problems has overcome and provide suggestions.
But Sammobile blog has also confirmed these issues.
II havent faced any of these issues post update.
Did you try doing a factory reset? If not, try the same if its not too much of an issue for you.
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
shuvadeep said:
II havent faced any of these issues post update.
Did you try doing a factory reset? If not, try the same if its not too much of an issue for you.
Click to expand...
Click to collapse
No I didn't do factory reset as I have checked from other forums that factory reset is not helping, the new update is broken.
Whiskey103 said:
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
Click to expand...
Click to collapse
Wow let me try this, shall update you soon.
Whiskey103 said:
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
Click to expand...
Click to collapse
Wow let me try this, shall update you soon.
***Update***
Yes this trick is working.
---------------
Also one more question I don't know if it's my phone or everyone is facing this issue. Whenever I switch on VoLTE calls (Screenshot Attached) my phone temperature increases and battery drains.
Nitin5556 said:
No I didn't do factory reset as I have checked from other forums that factory reset is not helping, the new update is broken.
Click to expand...
Click to collapse
Not true, its a good update and everything butterysmooth here. Did factory reset after the update though because of the size of the update.
gee2012 said:
Not true, its a good update and everything butterysmooth here. Did factory reset after the update though because of the size of the update.
Click to expand...
Click to collapse
Everyone is not facing this issue, some of them are facing!
Are you using data over WiFi or Mobile data?
Nitin5556 said:
Hello Guys,
I am from India, I got the latest update attached screenshot.
I am facing few issues:-
The phone has become laggy in some departments such as:
1. The fingerprint mark stays on the screen after the screen unlocks.
2. Even after pressing the power button screen doesn't lock. The screen does black out but when I double tab on the screen it directly takes me to the home screen without showing the lockscree first. I am not using Google trusted location or devices to unlock without taking my fingerprint or face recognition.
3. When I try to dial a number it doesn't call at a single go, after pressing multiple times it calls the person whom I am trying to call. It looks very choppy as if the system responding to my commands little later.
4. Whenever I am trying to take the screenshot it doesn't take at a single go, after pressing multiple times the system recognises I am trying to take the screenshot and respond little later.
All the apps are working fine without any lags but the above said things are bothering me a lot.
I hope someone from XDA can assist me with this.
P.S.: I have tried to clear the cache from the boot screen. Also did a test on graphics from the same menu.
****Update v1****
I have got something to support my comments!
https://www.sammobile.com/2019/05/27/latest-galaxy-s10-update-has-some-serious-bugs/amp/
*****Update v2****
Switch off your WiFi, your phone will start behaving normal you will not face this problem in Mobile data usage.
Credit goes to @Whiskey103
Click to expand...
Click to collapse
Mine fingerprints stopped all together..Started to get error that something is wrong with sensor..Went to service centre..they downgraded to april..they conf that some issue in may update..Hope samsung fixes asap..
cbotadra said:
Mine fingerprints stopped all together..Started to get error that something is wrong with sensor..Went to service centre..they downgraded to april..they conf that some issue in may update..Hope samsung fixes asap..
Click to expand...
Click to collapse
Yes the problem is there in the May update.
Samsung should do something about this.
Nitin5556 said:
Everyone is not facing this issue, some of them are facing!
Are you using data over WiFi or Mobile data?
Click to expand...
Click to collapse
Both, but i flashed the rom with Odin. I don`t realy like OTA`s tbh.
gee2012 said:
Both, but i flashed the rom with Odin. I don`t realy like OTA`s tbh.
Click to expand...
Click to collapse
So, you're saying only the ppl that took the OTA are facing the issues? In that case i will probably try that then if the bug returns for me.
For now after switching WiFi On/Off for me it is gone.
Seen reports that plugging in the charger does the same.
Weird stuff indeed.
Also now i see a fellow Dutch, you by any change using Rabobank stuff (Wallet/App) with tripped KNOX and have no problems with it?
#sorryforofftopic
Whiskey103 said:
So, you're saying only the ppl that took the OTA are facing the issues? In that case i will probably try that then if the bug returns for me.
For now after switching WiFi On/Off for me it is gone.
Seen reports that plugging in the charger does the same.
Weird stuff indeed.
Also now i see a fellow Dutch, you by any change using Rabobank stuff (Wallet/App) with tripped KNOX and have no problems with it?
#sorryforofftopic
Click to expand...
Click to collapse
No, its possible that some users who do flash a rom with Odin could face some issues too but i personally don`t. I`am using the ABN bank app and i haven`t rooted for a long time now. I used to do it because of theming and getting updates/upgrades but nowadays i personaly don`t see a reason anymore to root anymore. So i can`t help you with your question.
I happened to flash "ASE5" build two ways :
1. First using ODIN 2 days back . Did a factory reset ,erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced -> None.
2. Went back to previous "ASD5" build, downloaded the "ASE5 OTA" update and installed. Did a factory reset, erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced so far -> None.
*One glitch I'm noticing from the beginning with "ASE5" :
When I click on my apps & games(playstore app>drop down menu on the left), it freezes for a split second while it takes into the main page. With all my effort, I could not fix it. (App cache cleaning only temporarily fixes this).
Virgo_Guy said:
I happened to flash "ASE5" build two ways :
1. First using ODIN 2 days back . Did a factory reset ,erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced -> None.
2. Went back to previous "ASD5" build, downloaded the "ASE5 OTA" update and installed. Did a factory reset, erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced so far -> None.
*One glitch I'm noticing from the beginning with "ASE5" :
When I click on my apps & games(playstore app>drop down menu on the left), it freezes for a split second while it takes into the main page. With all my effort, I could not fix it. (App cache cleaning only temporarily fixes this).
Click to expand...
Click to collapse
A split second delay bothers you? What apps are running in the background? Do you have the FaceBook app installed? How did you set your animations?
gee2012 said:
A split second delay bothers you? What apps are running in the background? Do you have the FaceBook app installed? How did you set your animations?
Click to expand...
Click to collapse
No it does not "bother"but is a step back in smoothness if that counts. It's a "difference" that I noticed since I was testing both builds back and forth for a comparison. Rest be assured that it's not related to apps installed and animations set.
Virgo_Guy said:
No it does not "bother"but is a step back in smoothness if that counts. It's a "difference" that I noticed since I was testing both builds back and forth for a comparison. Rest be assured that it's not related to apps installed and animations set.
Click to expand...
Click to collapse
I have my animations set to 1,0 and i don`t have a delay, on 0,5 however there is a slight delay.
gee2012 said:
I have my animations set to 1,0 and i don`t have a delay, on 0,5 however there is a slight delay.
Click to expand...
Click to collapse
Erase playstore cache and you won't even notice it for a while only to re-appear after sometime.
"Less noticiable" and "very much noticiable" in my usage in 1x & .5x respectively. In ASD5 build, this transition slips like a soap.

SM-910F random reboot/shutdown and time reset

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

Categories

Resources