Develop Bugs

[Q] MIUI rooted Desire randomly restarts

So, I have HTC Desire with rooted MIUI rom for a while.
HTC Desire, GSM, MIUI 2.1.6
It was okay until 5th January. I have about 25 installed apps and anything was fine. Few days ago I noticed strange "Force stop" in apps like Twitter, Foursquare, Internet Browser.
Then the same started to happen with random restarts of the phone. The phone simply started, then restarted and entered into bootscreen loop, so I ejected battery and inserted and so on. Clearing Dalvik Cache doesn't help.
Also when I try to enter Wi-Fi settings it freezes and gives out "Force close application?" That's just ridiculous!
I have lately updated from previous MIUI version 2.1.4 because that problem started there, but with no changes.
Can you please help here?

i have always faced similar issues with MIUI , my phone doesnt like it
so i have simply stopped using it
edit: if you still want to use MIUI id suggest you stick with a stable version for a while rather than weekly updates

Well, it really might be like that. Seems like I fixed those issues by doing a full phone wipe and fresh flash. Which release can you suggest me?

Wich releases did you try before ?
Sent from my HTC Desire using XDA App

I have MIUI on mine and flash each update. The biggest issue I have is that it tries to update and always fails with an E:\SDCard error in recovery. I just download and then flash the full rom (no wipes) and it works a treat. The one issue I have with 2.16 is that SMS messages disappear below my 'Better Keyboard' where they didn't in the version prior. I've switched to Android keyboard now but have yet to see if the issue persists. That said, it is by far the most stable ROM I've ever used and I'm running 40+ apps on it with zero problems.

MarcelHofs said:
Wich releases did you try before ?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
The last previous version before 2.16, but I still got another problems with it.
Parva4 said:
I have MIUI on mine and flash each update. The biggest issue I have is that it tries to update and always fails with an E:\SDCard error in recovery. I just download and then flash the full rom (no wipes) and it works a treat. The one issue I have with 2.16 is that SMS messages disappear below my 'Better Keyboard' where they didn't in the version prior. I've switched to Android keyboard now but have yet to see if the issue persists. That said, it is by far the most stable ROM I've ever used and I'm running 40+ apps on it with zero problems.
Click to expand...
Click to collapse
As far as it is, it looks fine. No big problems at all. The only issue is that I backed up 5000+ messages back to phone, I like to store them there. Sometimes seems like it is a little hard for android to hold so many sms's.

Problems Updating OTA - Stock Non-Rooted

I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?

robertlewisca said:
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
Click to expand...
Click to collapse
I was having the same exact problem. I even changed phones thru warranty. The new phone did the same thing. New SIM card didn't help. I had a guy at tech support to push the update to me.

I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.

IDK, co-worker with a Skyrocket has had the same issue, but he doesn't care about the update, so he hasn't bothered to get it resolved.
If I didn't have a red GS3, I could goof around and tell you that is what the problem is...
Actually, if it were me having the issue, I'd walk into AT&T and have their guys mess around with it. No telling why some have more issues than others.

robertlewisca said:
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
Click to expand...
Click to collapse
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?

Not really a solution but you could install this http://forum.xda-developers.com/showthread.php?t=1902178 to be fully stock LH9 with Root. Or use the OTA zip from here http://forum.xda-developers.com/showthread.php?t=1896773.

aboveusonlysky said:
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Click to expand...
Click to collapse
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.

78c10 said:
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
Click to expand...
Click to collapse
You mention in your signature that your phone is rooted. So, did you update OTA then root, or did you update after rooting through some other method? The challenge some of us are having is that we are not rooted, and cannot update OTA because of the 'server error' it gives us everytime we try.

Problem Solved - for me at least
Well, the problem is solved for me, and I thought I would share what I found out here in hopes it helps someone else.
First, I had the phone replaced under warranty. It appears to be a brand new phone. When I received the new phone, I started it up, went through the normal startup stuff - entered my Google account information, it backed up my info and settings. Before I loaded any apps, I went straight to the update screen, and tried to check for an update. I again got the 'communication failed' error. Bummer.
So, then, I did a factory reset on the new phone, but this time instead of entering the initial Google account info on the startup screens, I skipped through all of the initial screens, got to the home screen, then went straight to the update screen - and this time it worked! So, it must be something to do with the initial screens, and entering Google account information that caused the problem.
Then, I got to thinking - perhaps this might work on my old phone too. Since I just got the warranty phone today, I still had my old phone (which needs to be sent back). So, I did a factory reset on it, skipped all of the initial screens where it asks for Google account information, and it still didn't work on the old phone. So, I'm not sure what the original issue was.
By the way, after the update installed on the new phone, and I went through and entered all of the Google account settings, and then checked for the update again, and there was no error.
So, perhaps this might be helpful for others?

[Q] Repeat system update notification

I've got an unrooted, completely stock, unlocked Galaxy Nexus. A few weeks ago, I updated it to 4.3 when prompted by the usual notification ("System update downloaded: Touch to install"), and the update went fine.
However, since then I keep getting the same notification again, and pressing it seems to reinstall 4.3. The notification then reappears after a week or so. I know the update isn't failing, as I can see in the settings that it's running 4.3.
Does anyone know why it might be doing this, and how I can stop it?!

6chrisp said:
I've got an unrooted, completely stock, unlocked Galaxy Nexus. A few weeks ago, I updated it to 4.3 when prompted by the usual notification ("System update downloaded: Touch to install"), and the update went fine.
However, since then I keep getting the same notification again, and pressing it seems to reinstall 4.3. The notification then reappears after a week or so. I know the update isn't failing, as I can see in the settings that it's running 4.3.
Does anyone know why it might be doing this, and how I can stop it?!
Click to expand...
Click to collapse
I have the same problem

Probable solution
I found a solution in this thread
http://forum.xda-developers.com/showthread.php?t=2413535&page=11

[Q] com.android.phone has stopped after reverting to stock

Hello,
I rooted my M919 and tried a few ROMs to hopefully find one that I liked, but it seems that they all have bugs that make the phone unusable for me. (Flashed a Google Edition rom, the proximity sensor didn't work anymore, so I couldn't end a call, ever).
Now I am trying to flash the stock firmware, and it seemed to have worked, except I get the com.android.phone has stopped, CONSTANTLY. I already have tried clearing data/cache several times, no luck.
Any ideas?
Thanks!

jtleniger said:
Hello,
I rooted my M919 and tried a few ROMs to hopefully find one that I liked, but it seems that they all have bugs that make the phone unusable for me. (Flashed a Google Edition rom, the proximity sensor didn't work anymore, so I couldn't end a call, ever).
Now I am trying to flash the stock firmware, and it seemed to have worked, except I get the com.android.phone has stopped, CONSTANTLY. I already have tried clearing data/cache several times, no luck.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Try using a different recovery. I've had that problem before, baseband and IMEI were shown as unknown and com.android.phone would force-close constantly. I don't know why the recovery would cause that, but switching recoveries worked for me.

I had this same issue yesterday, very strange that I would see this listed here about the same time. I haven't done anything different, that I haven't done before. Then I flashed the stock T-Mobile rom and it still kept doing it. Apn settings disappeared when this happened.

[Q] M8 International stock, frequently crashing

Hi,
I bought my m8 international about 2 months ago. It was working fine up to now, with an occasional crash and reboot (4 times since I have it). Since yesterday evening it has crashed and restarted about 20 times. I have no idea what has changed and there seems to be no consistent reason for the crash. I tried to restore to factory settings and even clear the SD card, but on the first reboot it crashed when I was entering my sim unlock code.
I rooted all my previous phones but did not try it on this one yet, so it is completely stock.
Is there a way to find out what is causing the crashes without having root?
thanks for your replies.
Fyretb

Fyretb said:
Hi,
I bought my m8 international about 2 mpnths ago. It was working fine up to now, with an occasional crash and reboot (4 times since I have it). Since yesterday evening it has crashed and restarted about 20 times. I have no idea what has changed and there seems to be no consistent reason for the crash. I tried to restore to factory settings and even clear the SD card, but on the first reboot it crashed when I was entering my sim unlock code.
I rooted all my previous phones but did not try it on this one yet, so it is completely stock.
Is there a way to find out what is causing the crashes without having root?
thanks for your replies.
Fyretb
Click to expand...
Click to collapse
I take it you have updated the firmware via OTA's? I had a similar experience when I first got my M8 (a couple of weeks ago), it would reboot randomly several times a day, tried factory resetting and it didnt help. I installed the prompted OTA's and running 4.4.3 which fixed it. Was a bit annoying as I was trying to hold off updating until I seen what my options were for root/s-off etc, now I have the latest bootloader and would have to use Sunshine to s-off. Still havent rooted as everything is running great for me at the moment so happy enough.

gsmyth said:
I take it you have updated the firmware via OTA's? I had a similar experience when I first got my M8 (a couple of weeks ago), it would reboot randomly several times a day, tried factory resetting and it didnt help. I installed the prompted OTA's and running 4.4.3 which fixed it. Was a bit annoying as I was trying to hold off updating until I seen what my options were for root/s-off etc, now I have the latest bootloader and would have to use Sunshine to s-off. Still havent rooted as everything is running great for me at the moment so happy enough.
Click to expand...
Click to collapse
Yeah, installed all the OTA's, but last one was a couple of weeks ago. I just double checked, but there's nothing to update at this point.

Fyretb said:
Yeah, installed all the OTA's, but last one was a couple of weeks ago. I just double checked, but there's nothing to update at this point.
Click to expand...
Click to collapse
Are you getting the HTC error log messages when you boot up again, should appear as a notification? I got a few of these when mine was crashing, you can view the log if you tap into the notification. It will be a massive log, I tried copying and was going to paste to an email or doc but it wouldnt let me as there was too much data.

gsmyth said:
Are you getting the HTC error log messages when you boot up again, should appear as a notification? I got a few of these when mine was crashing, you can view the log if you tap into the notification. It will be a massive log, I tried copying and was going to paste to an email or doc but it wouldnt let me as there was too much data.
Click to expand...
Click to collapse
Yeah, I get those. As you say it's massive and not readable, at least not for me. I couldn't even manage copying it..