Hi,
I haven't found a similar problem, that's why i'm opening a thread here. I haven't done any unusual changes to the 2.1 that was already on device (no root, no sys file changes, nothing).
The phone reboots at least 2-3 times per day. Every time I check it (when it does that), it asks for PIN. So instead of working properly, all I see is ENTER PIN screen.
Anyone else having similar problems? How could I find out what is causing this?
thank you for replies.
I've got the same problem here.
I've read somewhere, that upgrading to the unofficial Froyo Rom solves that problem. But not confirmed so far...
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
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks
Frosty1148 said:
Hi
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks
Click to expand...
Click to collapse
Maybe it's a bug in the ROM
Try different rom and see if this problem still persists, if yes, maybe a hardware problem related issue
Cheers
There are a few roms with 100% support for the official extended batteries(s). Your best bet is to go with one of them.
Sent from my HD2 using XDA App
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
I have read too many posts and solutions but nothing have solved my s5 problem, which is not rotating.
I lost rotation after flashing a new rom on my s5 (actually suddenly after two weeks of installing the new rom).
I have to mention that if I removed the battery for more than a min, "sometimes" it works again but not for long time, and when the screen shut down it stops from rotating.
I downloaded cyanogenmod roms but also didn't fix it.
I tried to reset my phone using kies, and it worked back for one day, then stopped.
I also tried the method of replacing libgnustl_shared.so file in system/lib and changing permission (as described in this thread http://forum.xda-developers.com/showthread.php?t=2644293), but it didn't work with me.
Please, I am so desperate to fix this problem. Anybody think it is a hardware problem?, if yes, why it works after restart with battery removal sometimes?
I am eager to solve this problem, and thanks for everyone who wants to help
Hello, everyone!
Last week I received a brand new Xiaomi Redmi 3S. Everything seemed fine until I noticed that the phone tends to reboot from time to time. Sometimes, it can't work for a couple of minutes before rebooting and sometimes I can spend hours playing with it before the error happens.
I tried updating to the latest official stable MIUI and the problem persists. I switched to the developer version, to no avail.
Then, I decided to unlock the bootloader and install a custom ROM (from Xiaomi.EU) and it didn't solve the issue.
Reading through some threads in the en.miui forums I found some posts by a guy who claimed that the problem could be solved by using KernelAdiutor... But his method didn't work.
I made a video, as the vendor requested. There, you can see the problem: It rebooted my phone twice in less than 5 minutes.
I think that this problem isn't related to the battery, as the reboots have happened even while the phone is connected, and just before each reboot the phone freezes for a moment, like if a program crashed.
Any ideas on how to solve this issue? Thanks in advance.
Vexelius said:
Hello, everyone!
Last week I received a brand new Xiaomi Redmi 3S. Everything seemed fine until I noticed that the phone tends to reboot from time to time. Sometimes, it can't work for a couple of minutes before rebooting and sometimes I can spend hours playing with it before the error happens.
I tried updating to the latest official stable MIUI and the problem persists. I switched to the developer version, to no avail.
Then, I decided to unlock the bootloader and install a custom ROM (from Xiaomi.EU) and it didn't solve the issue.
Reading through some threads in the en.miui forums I found some posts by a guy who claimed that the problem could be solved by using KernelAdiutor... But his method didn't work.
I made a video, as the vendor requested. There, you can see the problem: It rebooted my phone twice in less than 5 minutes.
I think that this problem isn't related to the battery, as the reboots have happened even while the phone is connected, and just before each reboot the phone freezes for a moment, like if a program crashed.
Any ideas on how to solve this issue? Thanks in advance.
Click to expand...
Click to collapse
No expert here, but seems could be hardware error. Next time if you happen to have such thing, don't unlock the bootloader. But maybe you can relock it (if thats needed) and install stock and send it back to them. The device seems to have a defect.
same issue for ME also ! every day crying with redmi 3s ! F**k