Related
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
I called today the customer service of my carrier "oi" and I spent kinda 30 minutes talking, trying to solve a problem.
When I saw, my phone was in a bootloop with the cyanogenmod boot and I was continuing to talk, without any interrumption.
The only difference was thet the phone was hot!
Running at 1.4 with the last netarchy kernel my max was 38!!! (low)
Random reboots are a S/W problem, Google is aware of the issue and will be pushing out an update that fixes the problem.
there is nothing your carriers can do about the issue
slowz3r said:
Random reboots are a S/W problem, Google is aware of the issue and will be pushing out an update that fixes the problem.
there is nothing your carriers can do about the issue
Click to expand...
Click to collapse
I hope so!
Serious_Beans said:
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
Click to expand...
Click to collapse
Just a couple of questions. Are you using a frequency changer app example, setcpu cpu tuner? Do you have the set on boot checked for main profile? I have found if the set on boot is check to have random reboots on calls. I uncheck and no longer have the reboots on calls. That was the only time I ever had the reboots happen. Just a question and something to check in your settings.
Serious_Beans said:
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
Click to expand...
Click to collapse
Your running netarchy 1.2.4 which is still in its test phase. That's where your issue is. If you switch to a more stable one then you should be fine
Sent from my Nexus S using XDA App
No random reboots here, got it on the 3rd. Phone runs smooth as silk. I'm on stock 2.3.2. Out of all the phones I've owned this has been the most stable.
Could my phone possibly be from a different batch? I'm not experiencing any of the issues alot of other people are besides 100% init process, which I solved with keeping USB debugging on.
Sent from my Nexus S using XDA App
ruben8448 said:
Your running netarchy 1.2.4 which is still in its test phase. That's where your issue is. If you switch to a more stable one then you should be fine
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I don't think it's the kernel, even stock users have the reboot problems.
I don't have any such problem on Cyanogenmod 7 rc1...
iKitsunee said:
I don't think it's the kernel, even stock users have the reboot problems.
Click to expand...
Click to collapse
We get random reboots from time to time but with the freezing and all the other issues it sounds like the kernel. I tried that kernel and I had the same issues. I just switched to 1.2.2 and I was good to go
Sent from my Nexus S using XDA App
ruben8448 said:
We get random reboots from time to time but with the freezing and all the other issues it sounds like the kernel. I tried that kernel and I had the same issues. I just switched to 1.2.2 and I was good to go
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ah, I'm actually using that kernel as well, hasn't happened to me but I suppose it might vary from phone to phone.
jerrycycle said:
Just a couple of questions. Are you using a frequency changer app example, setcpu cpu tuner? Do you have the set on boot checked for main profile? I have found if the set on boot is check to have random reboots on calls. I uncheck and no longer have the reboots on calls. That was the only time I ever had the reboots happen. Just a question and something to check in your settings.
Click to expand...
Click to collapse
I have it set on boot,but I'm running at stock speeds. I am not overclocking and still having these problems. I'm going to try a bunch of other roms and kernels and see what my results are, it COULD be the phone it self, but I doubt it.
And thanks everyone for all the responses.
Serious_Beans said:
I have it set on boot,but I'm running at stock speeds. I am not overclocking and still having these problems. I'm going to try a bunch of other roms and kernels and see what my results are, it COULD be the phone it self, but I doubt it.
And thanks everyone for all the responses.
Click to expand...
Click to collapse
The kernel is set to default at stock setting so no need to have it set on boot. It isn't going to overclock unless you raise the cpu past 1g
google have already said that the problem its just s/w and they are going to fix it with an update and it's not the new 2.3.3! Hope it don't take much longer!!
Sent from my Nexus S using XDA App
There is a stock kernel for cm7 out that has all the voodoo engagement and ext 4 hack
I've had random reboots and it only happens to me when I'm using bluetooth.
Sent from my Nexus S using XDA App
its been over one month now and i never had such problem with mine..its running smoothly both with stock and cm7..
I experienced my first random reboot today. Installed clocksync and was fine. Today I loaded the app... screen was blank then saw the boot animation.
Sent from my Nexus S
I experienced 2 reboots in a row trying to retrieve a service from my mobile operator. I got so frustrated ´cause the mobile operator service takes too long,
the last time I looked, elapsed 7 minutes, few minutes later, reboot...
Became afraid to call again from the nexus, not trusting anymore
wifi on, sync on, bluetooth off, gps off, it was charging with the regular charger, factory rom and kernel, not rooted, launcher pro
I also have random reboots. it's strange though, it goes to the boot animation for some time, looks like the phone reboots, then all the apps and launcher is reloaded, but if you check the phone boot time under settings -> about, the uptime is not reset.
can you guys confirm that your boot times are also no reset during the randon reboots oft he known google android software issue for nexus s?
thanks,
Does anyone experience wifi disconnect and reconnecting while browsing?
Sent from my GT-S5360 using xda app-developers app
Noo..
yes i do
I do too. So that makes two of us? What can be the problem?
Sent from my GT-S5360 using xda app-developers app
Oh c'mon guyz..
Why u never read.
Its in the same post of hyperion..
U got to go to..
Settings>wifi>option button>deep sleep policy nd change it to dont disconnect
** rooting is new for me,
nd i am a noob to root....**
menewtoroot said:
Oh c'mon guyz..
Why u never read.
Its in the same post of hyperion..
U got to go to..
Settings>wifi>option button>deep sleep policy nd change it to dont disconnect
** rooting is new for me,
nd i am a noob to root....**
Click to expand...
Click to collapse
Yes, this worked for me too. :good:
booterbotter said:
Yes, this worked for me too. :good:
Click to expand...
Click to collapse
i knw it worked ..
next time plz read full article..
carl didnt wrote all that just to pass time..
** rooting is new for me,
nd i am a noob to root....**
menewtoroot said:
Oh c'mon guyz..
Why u never read.
Its in the same post of hyperion..
U got to go to..
Settings>wifi>option button>deep sleep policy nd change it to dont disconnect
** rooting is new for me,
nd i am a noob to root....**
Click to expand...
Click to collapse
agree
Random reboots in Hyperion 8
Overall the Hyperion 8 ROM is a nice-good-looking one. However, I've found 2 major bugs(?):
It reboots randomly at least once a day.
The "Restart" option doesn't work. The phone shuts down but never comes on.
In both cases, when booting, it gets stuck in the Samsung logo. To boot up, I have to remove the battery.
Also, it takes ages to reboot, about 6 min.
Does anyone is experiencing the same issues? Any possible solutions?
Cheers.
Blue.Ghost said:
Overall the Hyperion 8 ROM is a nice-good-looking one. However, I've found 2 major bugs(?):
It reboots randomly at least once a day.
The "Restart" option doesn't work. The phone shuts down but never comes on.
In both cases, when booting it gets stuck in the Samsung logo. To boot up, I have to remove the battery.
Also, it takes ages to reboot, about 6 min.
Does anyone is experiencing the same issues? Any possible soluctions?
Cheers.
Click to expand...
Click to collapse
I would say try re-flashing it following the install instructions from the Hyperion 7 thread exactly.
I have had the same thing as you when I first installed hype 8 but no random reboots and restart works fine on my current install
One problem I have with Hype 8 is that the stock browser included with the ROM will not connect via wi-fi, at all - although all other apps like Play store do, the browser only works on 3G. I usually use One Browser but that doesn't work either. I am currently using Opera Mini as that will work but I have no idea why this is...and yes I have pruned the hosts file and checked the Droidwall is not on (even if it was I have configured all apps to have access). Annoying, like the way the data toggle sometimes doesn't turn off - but hardly a game-breaker when Hype is so excellent on battery life and memory usage :good:
Cheers,
Stokey
Blue.Ghost said:
Overall the Hyperion 8 ROM is a nice-good-looking one. However, I've found 2 major bugs(?):
It reboots randomly at least once a day.
The "Restart" option doesn't work. The phone shuts down but never comes on.
In both cases, when booting, it gets stuck in the Samsung logo. To boot up, I have to remove the battery.
Also, it takes ages to reboot, about 6 min.
Does anyone is experiencing the same issues? Any possible solutions?
Cheers.
Click to expand...
Click to collapse
I been using it since it came out & its never restarted on me or failed to boot
I suggest you reinstall it and use hells fusion #50 kernel
hey i m using jellyblast..how do i get hyperion 8 widout bricking my sgy...ive got d zip files
Sent from my GT-S5360 using xda app-developers app
Dhaval Bhatt said:
hey i m using jellyblast..how do i get hyperion 8 widout bricking my sgy...ive got d zip files
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Do a data wipe/reset ie wipe data system & cache
Mount everything ie system & data
Install zip from sd card
Select zip file
Done
a simple method
change your ROM
Hyperion bugs
stokeyblokey said:
I would say try re-flashing it following the install instructions from the Hyperion 7 thread exactly.
I have had the same thing as you when I first installed hype 8 but no random reboots and restart works fine on my current install
One problem I have with Hype 8 is that the stock browser included with the ROM will not connect via wi-fi, at all - although all other apps like Play store do, the browser only works on 3G. I usually use One Browser but that doesn't work either. I am currently using Opera Mini as that will work but I have no idea why this is...and yes I have pruned the hosts file and checked the Droidwall is not on (even if it was I have configured all apps to have access). Annoying, like the way the data toggle sometimes doesn't turn off - but hardly a game-breaker when Hype is so excellent on battery life and memory usage :good:
Cheers,
Stokey
Click to expand...
Click to collapse
Thanks for your reply Stokey. In my case, I've got no problems at all with the stock browser; it is able to connect via either wifi or 3G. I wonder if such differences may be due to the build we're using. I downloaded Hyperion 8 build 2 with the default Savie kernel. Are you using the same build?
Theroretically build 2 would be more stable, isn't it? Should I revert back to build 1?
Cheers,
Blue Ghost
Blue.Ghost said:
Thanks for your reply Stokey. In my case, I've got no problems at all with the stock browser; it is able to connect via either wifi or 3G. I wonder if such differences may be due to the build we're using. I downloaded Hyperion 8 build 2 with the default Savie kernel. Are you using the same build?
Theroretically build 2 would be more stable, isn't it? Should I revert back to build 1?
Cheers,
Blue Ghost
Click to expand...
Click to collapse
I'm using build 2 with hells fusion #50 - no problems at all
Make sure you have disabled wifi deep sleep in wifi settings
Blue.Ghost said:
Thanks for your reply Stokey. In my case, I've got no problems at all with the stock browser; it is able to connect via either wifi or 3G. I wonder if such differences may be due to the build we're using. I downloaded Hyperion 8 build 2 with the default Savie kernel. Are you using the same build?
Click to expand...
Click to collapse
No, I only had build 1 because every download of build 2 was interrupted I am trying again now as I really would prefer not to use Build 1 for obvious reasons! I only installed it because of a weird wifi issue I was having on Hype 7 - I did all the tweaks to fix wifi but even though it was on all the time, if I didn't use it for a short while sometimes the signal icon would go grey and stay grey - forever! Although connected and showing an IP address in the advanced wifi settings, nothing at all could connect through wifi and I only had 3G - this has happened 3 times with Hype 7 and necessitated a reinstall via stock each time, hence me wanting to try 8 as I needed the wifi connection and a battery that lasted a full work day for the last 2 days.
Theroretically build 2 would be more stable, isn't it? Should I revert back to build 1?
Click to expand...
Click to collapse
I would say stick with Build 2 for a couple of reasons: the launcher is not a paid-app; I think build 2 uses his Hype 7 launcher which I actually prefer (sometimes less functionality suits better); if there were any fixes from Build 1 they will be included although I don't think there were any that were mentioned...
Same kernel on both builds (thank you Savie! :good but as others are saying, you can use at least one other kernel - I have never changed just the kernel but maybe that would help fix my Hype 7 issues...anyhow, I am off to try Build 2 - good luck with yours - let us know how you get on.
Cheers,
Stokey
EDIT: Can anyone help me to get the AudioFX widget to actually do something other than be almost invisible whatever settings I use? Or suggest an alternative that works with Hype 8?
stokeyblokey said:
EDIT: Can anyone help me to get the AudioFX widget to actually do something other than be almost invisible whatever settings I use? Or suggest an alternative that works with Hype 8?
Click to expand...
Click to collapse
Open AudioFX in drawer app then adjust the transparency settings. Make it 20% then 40% then 60% then back to opaque. It will show up.
Sent from my GT-S5360 using xda premium
stokeyblokey said:
No, I only had build 1 because every download of build 2 was interrupted I am trying again now as I really would prefer not to use Build 1 for obvious reasons! I only installed it because of a weird wifi issue I was having on Hype 7 - I did all the tweaks to fix wifi but even though it was on all the time, if I didn't use it for a short while sometimes the signal icon would go grey and stay grey - forever! Although connected and showing an IP address in the advanced wifi settings, nothing at all could connect through wifi and I only had 3G - this has happened 3 times with Hype 7 and necessitated a reinstall via stock each time, hence me wanting to try 8 as I needed the wifi connection and a battery that lasted a full work day for the last 2 days.
I would say stick with Build 2 for a couple of reasons: the launcher is not a paid-app; I think build 2 uses his Hype 7 launcher which I actually prefer (sometimes less functionality suits better); if there were any fixes from Build 1 they will be included although I don't think there were any that were mentioned...
Same kernel on both builds (thank you Savie! :good but as others are saying, you can use at least one other kernel - I have never changed just the kernel but maybe that would help fix my Hype 7 issues...anyhow, I am off to try Build 2 - good luck with yours - let us know how you get on.
Cheers,
Stokey
EDIT: Can anyone help me to get the AudioFX widget to actually do something other than be almost invisible whatever settings I use? Or suggest an alternative that works with Hype 8?
Click to expand...
Click to collapse
Agreed! Or use BeatsWidget included in other roms like USSrv9 and ota of JellyBlast. Its beats themed and looks cooler than the default one.
Thank you to makeouttactics and GaEuL (pressed!).
This was driving me mad!
Oh, and today whilst using Opera Mini to post on Facebook I had a spontaneous reboot - first one on Hype 8...will keep you posted.
Cheers,
Stokey
This topic has been discussed a lot of times on internet but I am really concerned about fixing my phone as no matter what, if i am on 2G, 3G or WIFI I stop having notification after 15-20 minutes. In fact I tried PINGING my device and PING stops really after 15 minutes. Anyways, currently I am desperately waiting for 4.3 and there is just no NEWS of the RELEASE DATE whatsoever. But also I am not much into CUSTOM ROM or KERNELS but was wondering if I can only update the KERNEL version (i.e., FRANCO if any one suggest) and solve this issue. I want to be remain on STOCK ANDROID but is it possible to only upgrade the kernel ?
Also I would need tutorial for the quickest root and the safest kernel to follow and keep upgrading it all the time. Thank you.
ibrahim52 said:
This topic has been discussed a lot of times on internet but I am really concerned about fixing my phone as no matter what, if i am on 2G, 3G or WIFI I stop having notification after 15-20 minutes. In fact I tried PINGING my device and PING stops really after 15 minutes. Anyways, currently I am desperately waiting for 4.3 and there is just no NEWS of the RELEASE DATE whatsoever. But also I am not much into CUSTOM ROM or KERNELS but was wondering if I can only update the KERNEL version (i.e., FRANCO if any one suggest) and solve this issue. I want to be remain on STOCK ANDROID but is it possible to only upgrade the kernel ?
Also I would need tutorial for the quickest root and the safest kernel to follow and keep upgrading it all the time. Thank you.
Click to expand...
Click to collapse
The choices and threads are out there for you if this is truly bothering you. You can stay stock and flash a couple of files to test out if your issue is fixed. Rooting is not the end of the world and you can always go back. As for tools there are multiple stickied root methods just choose one. Also no guarantee 4.3 fixes the issue. I flashed a couple files from Development in the Wifi/Fix thread and my problems went away. May for you it may be the prima drivers but you wont know until you do it
playya said:
The choices and threads are out there for you if this is truly bothering you. You can stay stock and flash a couple of files to test out if your issue is fixed. Rooting is not the end of the world and you can always go back. As for tools there are multiple stickied root methods just choose one. Also no guarantee 4.3 fixes the issue. I flashed a couple files from Development in the Wifi/Fix thread and my problems went away. May for you it may be the prima drivers but you wont know until you do it
Click to expand...
Click to collapse
I will be still waiting till 4.3 is released but just one thing I wanted to confirm when you said your problem was FIXED. Was it on both 3G / WiFi because this issue occurs on both interface.
Are there any other particular apps that still gets notification after everyone don't?
Sent from my Nexus 4 using xda app-developers app
QuackDuck said:
Are there any other particular apps that still gets notification after everyone don't?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
any APP has the same issue. I use the following and in everything it is the same frustrating issue.
whatsapp
Talk.to
Email (Even if the settings are on 1 hour INBOX CHECK, it never works until i manually do the sync)
These are the only apps I always expect to notify me INSTANTLY. Also it was the same in Google talk and any other IM apps.
ibrahim52 said:
I will be still waiting till 4.3 is released but just one thing I wanted to confirm when you said your problem was FIXED. Was it on both 3G / WiFi because this issue occurs on both interface.
Click to expand...
Click to collapse
for me I had mostly issues on wifi and now I can ping my phone after 30 minutes and it still going. I never honestly noticed it on 3g but either way you have options try them first
playya said:
for me I had mostly issues on wifi and now I can ping my phone after 30 minutes and it still going. I never honestly noticed it on 3g but either way you have options try them first
Click to expand...
Click to collapse
Thanks but it also happens in 2G because 3G I can't use due to my work environment where I can't keep charging my phone and in 3G this phone battery drains quickly. Well, two more weeks ill wait for 4.3 and if Google is still fooling then I will go ahead with ROOT and some KERNEL experiments. Thanks a load.
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.
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