Hi
Want to share with you an issue which seems to be fixed in a little different manner. I have been experimenting with different ROM, last was with Ultimate and when the update came i updated to XLT4. Post this series of issues so uninstalled the ROM, rebuild with Paranoid and still issue was there - system will reboot at random intervals. All the kernels tried and experimented as given but restarts wont stop. Worse thing is that it will enter a boot loop or stuck at Samsung log. Also tried to check APN settings, all the technical steps in every forum.....but no result.
Finally the new version XLT5 and XLT6 tried but still the problem existed. As a check i installed Ram booster (though i never believed in task killers) and strange but true no more restarts and works smooth.
I am not sure if this is how this should have been resolved, but will be happy if any users faced this issue and a similar thing resolved the problem. Now running with XLT5 and a RAM Booster things are pretty smooth with all root privileges.
Thanks for your time.
Did you wipe data/factory reset first before flashing roms? That might be causing the problems
Related
Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App
Hi all,
Been trying out MIUI and really like it but I'm getting constant quick reboots (no PIN check, etc. just restart) while running it. Initially did a clean install from the Ezrom base to MCGv5.2. Was having really bad reboot problems with it so tried installing the PE version of the Glitch kernel (MIUI-i9k-GlitchPE-V10.zip). That helped a bit but was still getting random reboots. Tried installing the new release of MIUI (MCGv5.31) there but I'm still getting the reboots. I've run the kernel cleanup script before each flash. Flashes after the initial one were done through CWM.
Does anyone know how to fix this? Love the ROM but there's just too many reboots to use it day to day.
Just a quick update to say that I think the problem is fixed. I think my problem coincided with a problem with the 5.31 release. Looks like my own problem was to do with NoLED being installed. I uninstalled it and there's been no more reboots so far (fingers crossed).
The new release (5.32) is reported to have fixed this problem but I haven't flashed it yet
Updated to official 2.3.5 rooted, added back the pink screen, not done much else except installed a few apps.
Getting random reboots while phone is sleeping. Never happens while actively using phone. My phone will be on my desk and next thing I know it restarts.
Anybody else have this problem or found a solution?
I need to find out if it is the rom or something else causing the problem so I can start to troubleshoot it.
typci said:
Updated to official 2.3.5 rooted, added back the pink screen, not done much else except installed a few apps.
Getting random reboots while phone is sleeping. Never happens while actively using phone. My phone will be on my desk and next thing I know it restarts.
Anybody else have this problem or found a solution?
I need to find out if it is the rom or something else causing the problem so I can start to troubleshoot it.
Click to expand...
Click to collapse
Turn OFF wifi when you're not using the phone. problem solved
If not work try this :
Goto CPU menu -> smartass v2 and make low and high cpu speed settings to 1 ghz.
This will also increase Battery life and must fix random rebooting.
Other way is clear caches and install rom again.
Loureiro:
I'll try turning off the wifi. It sounds like a highly likely solution since: 1) I've only seen my phone at home 2) I always turn wifi on at home.
Is there a specific reason why wifi is causing reboots? Maybe something I can find a fix for?
technogod:
Don't have custom kernal installed, so I can't alter the CPU parameters. Wanted to make sure the phone was stable at stock before changing the kernal.
Speaking of which, what's the most stable kernal for overclocking the 2.3 stock rom?
I'll try clearing the caches as well.
Thanks.
The wifi bug is known fault with the .35 kernel found in the official upgrade. hopefully it will be fixed next week fingers and toes crossed. I am not sure if any of the kernel dev's have found a fix yet.
Without cpu parameters, only way i am found that : clear three caches with clockwork and reinstall your rom. It's working on stock roms or custom roms. I think, this is not rom problem. There is different something. Cache clearing solves problem. Resetting problem started on my phone when i start to try other roms.
I am using miui 2.2.3 now and i will setup 2.2.10 version today. While using stock rom, i have some resetting problem. But now, my phone working without self-reset.
Hi all,
I've recently upgraded from a Samsung Galaxy S3 (i9300) to a Samsung Galaxy S5 (SM-G900F). Phone seemed to be working as desired so decided to go ahead, root, and install a custom ROM for enhanced functionality and customisation. Root process went smoothly, just running a simple CF-AutoRoot with Odin3 (voids KNOX, but no other problems), then installing PhilZ Advanced CWM Recovery.
From there I decided to install an unofficial build of CyanogenMod 11; found information on this forum. Flashing worked perfectly (and took rather little time!), but upon installation I noticed a strange problem. If I hard reboot (power off, power on) the device, with Wifi & Mobile Data off, the time and date are reset to incorrect values. Usually 01/01/xxxx and the time around 00:00. Same problem occurs even if when I turned off Network-allocated time and tried and set time manually.
The same problem occurred with other similar CyanogenMod based builds such as [AICP] and [AOSB]. I decided to restore back to the stock ROM and noticed that the clock and date were set correctly on reboot (and also on custom versions of 4.4.2 such as SpeedROMv7).
I checked with the terminal the value of the 'hwclock' (from BusyBox) and it reported an odd date somewhere in 1970, but different to the ones in found on CyanogenMod etc.
Does anyone have any idea what could cause this kind of problem and how to fix such an issue? If anyone wants any additional information about my device, please don't hesitate on commenting in this post. Would be grateful for any feedback. Thanks! :good:
PS: Also seem to be experiencing a problem with WiFi randomly disconnecting after a period of time. Not seen many threads with this said explicitly however. Problem with no voice in phone calls with headphones still persists but I've acknowledged that this is a known bug at the moment.
A.
Bump
*bump* // Problem still not resolved. Anyone know if it's device chain related?
Anyone?
AlfieJPalmer said:
*bump* // Problem still not resolved. Anyone know if it's device chain related?
Click to expand...
Click to collapse
Same Issue.
I have been encountering this very same problem for a while now, in fact, I am expriencing the same issue with my Galaxy S4 (i9505). So this must really be an issue of the CM code I guess.
Any ideas on how to solve this would be welcome since it is a really annoying issue
remove me
Hi everyone,
Until recently I've been using a KitKat based ROM and I was pretty OK with how my NOTE 3 SM-9005 was performing. However, a few days ago I decided to try a Lollipop based ROM and the problems started. I had similar problems with 3 different ROMs with great reviews. My battery went, for example, from 100% to 15% in ONE HOUR while streaming from YouTube. It never did that before. Also, It sometimes gives a "system stopped responding" error or something like that (it's like the equivalent of explorer.exe crashing on Windows) and after a few seconds it starts working again. Other system apps crash as well every now and then and sometimes the phone just decides to restart by itself.
I initially used Philz recovery and after the initial errors I switched to TWRP and started from scratch. I completely wiped my system internal space before flashing and, of course, I wiped dalvik cache and cache before and after flashing the ROM. I only used recommended gapps. Also, I did not restore any system apps. I started from scratch after the installation and the problem is the same.
To be more exact, I tries flashing so far the following ROMS, experiencing more or less the same problems on each:
temasek's UNOFFICIAL CM12.1
AryaMod V5.4 TW Lollipop Official BOB6
BlissPop 3.5 Unofficial
I also tried the Dirty Unicorns v9.4 ROM from the Original Android Development section but this one went on a reboot loop initially after the first restart so it never really even installed.
At this point I believe I might have done something that I should't have, but it seems strange because this is not the first time I am flashing a new ROM and I never had problems in the past. Also, my NOTE 3 SM-9500 did not have any problem on my previous KitKat ROM. Did I miss something? Should I have used another kernel? If I understood correctly, the ROMs come with a recommended kernel already. If this is not the problem, what could it be? Should I have done any additional thing before flashing a Lolipop ROM after using a KitKat ROM?
I now installed an app for trying to find out what exactly drains my battery but this is not the only problem. The system itself is really unstable.
I would really appreciate some help, suggestions, or opinions. I really don't know what else should I be doing at this point.
Thanks a lot!
Apparently is the media server eating all that battery (currently 68%).
I will format the SD card hoping this fixes the issue.....but could this have something to do with the system error and, sometimes, restarts?
Well I really don't know what to say! A lot of people report battery problems on 5.0 just because they didn't wipe the phone while coming from KK! But you did, so that's no go. Battery life on LP is much better than KK for me, at least 20% better if not more. And I didn't face any system crashing issues either! Don't really know what's going on with you mate.
Someone suggested that maybe I shoud update the bootloader and modem to a Lollipop version but I really couldn't find any info on how to do that.
Formatting the SD card just slightly reduced the battery drain. The phone is still discharging like crazy. Any suggestion on how to update the bootloader and modem?
Thank you.