Related
Why my LG Optimus 2X freezes and/or reboot?
Most of us have the same problem, we are trying to find a solution. In the meanwhile we can solve only removing battery.
Is it related to baseband version?
It does not seem related to baseband version. The problem is present in last baseband versione too:
1035.21_210110405
FRG83G
V10b
Is it related to ROM Version?
Apparently it happens on both stock and custom ROMS
I read that it is due to wall charger problem
Some of us have the same problem recharging both from USB PC and Wall Charger
I read this is due to overheat problem
Some of us still have the problem in standby mode with battery under 25° C.
LG told me to ask for a replacement
Some of us did it and had the same issue on the replaced phone.
I read it is due to hidden menu/car navigation/ecc. ecc.
There are no prooves about it.
Could it be a ROOT problem?
No. Same thing happens on both rooted and original phones.
I got it. It's a SD problem
Some of us has this problem both with or without SD card
So it's a HW problem
We are not sure about it. Most of us (me too) think this is a SW related issue. Some other thinks about a HW one.
Anyway it looks like a Nvidia/Tegra related problem.
It happens on Motorola Atrix too:
http://forum.xda-developers.com/showthread.php?t=969974
http://forum.xda-developers.com/showthread.php?t=1009510
So: what can I do?
Follow this thread and partecipate
Try to install latest version v10b and do a full reset.
Try to uninstall the "Any cut" application.
Try removing your SD.
NOTE: These are temporary solutions while we wait to understand something more.
Nothing else?
Sure, you can add informations here to keep updated the FAQs.
What about contacting LG?
It looks like something is moving and a new update will be released soon:
http://translate.google.com/transla...alligevel-problemer-med-optimus-2x,lid.15324/
Hey, new V10C is available. Does this solve?
Not sure yet. Some of us still have problems, but some others solved with this upgrade.
How can I help?
You can sign this petition on line
http://www.petitiononline.com/LGO2XPrb/petition.html
Last updated: Tue 7th July 2011
Mine has now shut down 3 times while i was in a call, battery pull on each occasion to rectify the problem
Added in the first question that pulling off the battery temporary solves.
1 week ago I do faced 2 time reboot each after receive sms during standby mood.
Dont know what happen.
Later I remember the reboot problem started after I had installed "Any cut" sw and started to activate the hidden menu.
Then I uninstall it and now haven facing any reboot no more.
Already 1 week pass and no reboot at all. I also never restart my O2X yet and seem everything is OK, no lag or etc on the system.
Hope this help.
Was using the original lg rom only for a good day and had one shutdown. Switched to custom rom and didnt have a reboot or shutdown yet in over a week. Appears to be software related.
Sent from my LG-P990 using XDA App
Useful topic, thanks!
My experience in 15 days of use.
with stock rom V10a and external sd:
- 1 time screen locked black in a warm day during standby
with stock rom V10a without external sd:
- many times screen locked black just after a notification (almost always after sms incoming notification)
with official rom V10b without hard reset and without external sd:
- 1 time reboot after pressing power button to exit from standby
- 2 times screen locked black the day after I've changed the useragent setting from the hiddenmenu and installed "AutomateIt" app
with official rom V10b after a hard reset 2 days ago and without external sd:
- no problem till now (2 days of use)
All the time I used both original charger (at home) and a generic usb adapter with an output current of 1mA (at office).
This is the sort of stuff that should be sent to LG to deal with. Not the idiots at call centres but the people who made the phone and get them to work on it.
Problem with these phone guys, they make a phone and then just stick out to the salesman and then when things like this happen to everyone we get no support or real contact.
It's always send it for repair. The phones are like a month old and that is really a valid response?
Time LG were held accountable (as well as other company's)
Ok, added some "Possible solutions"
Good thread, will hopefully cut down on some of the idle speculation that has been going on!
I believe that it is a software bug, namely in Nvidia's cpufreq-dvfsd driver. I saw this process misbehaving when doing a 'top' command via an ADB shell after it froze, and I'm not the only person to have witnessed that. I've posted that info over at MoDaCo.
As kholk is the only person other than Paul I know around here who might be familiar with a Linux kernel, I've asked him to take a look. Not sure what will come of that, if anything.
And just to add fuel to my argument that this is a Tegra/Nvidia issue, and *not* necessarily an LG one, check this out (from Moto Atrix forums):
http://forum.xda-developers.com/showthread.php?t=969974
http://forum.xda-developers.com/showthread.php?t=1009510
Read from the postings that, for charger-specific reboot/lockup problem, it might be better charging from a computer USB port or a charger with lower current output (I think someone is using as low as 350mA).
Fyi, I've never had AnyCut installed and I've had these problems.
Yup, we do not have still found THE cause, but some events.
We are trying to understand if they are related to the issue.
I am reporting infos from the other thread and from this one to help people ti find a partial solution.
Very interesting withoutwings
A problem related to tegra system could explain why LG can't solve anything?
Checking all of the messages I can see that the problem is one ( phone locking/restart) but the symptoms are very different and almost always unrepeatable.
Is also strange that many people have a lot of apparently casual restart/lock and many other people have no problems. If a part of source code is corrupted I think the problem should occurs for all the phone.
follo said:
Very interesting withoutwings
A problem related to tegra system could explain why LG can't solve anything?
Checking all of the messages I can see that the problem is one ( phone locking/restart) but the symptoms are very different and almost always unrepeatable.
Is also strange that many people have a lot of apparently casual restart/lock and many other people have no problems. If a part of source code is corrupted I think the problem should occurs for all the phone.
Click to expand...
Click to collapse
Not necessarily. In embedded/real-time systems, timing is crucial and in some components varies according to manufacture tolerances, heat, etc. Also everybody's phone has different apps and they do things at different times so you can't say that everybody's phone is just "the same" as everyone else's.
And this bug could well be one that only happens for some very specific condition that the original developer didn't forsee when he wrote that code or tested it. But the law of chance means that so many of us are seeing it - some more than others, and some days worse than other days.
So this would explain why people think that doing something like switching launcher or taking out an SD card might be solving or making the problem worse, because every action can and does change the likelihood of this specific condition occurring by changing how the phone behaves overall, workload, sleep time, etc etc. And why all these "solutions" that people are posting are so random and unrelated but each person is convinced that theirs is the one that works!
Basically, we need more evidence from logs to see what is really going on...
LG Denmark has just announced that they have acknowledged the problems and found a fix for it - they are currently sending out an update to correct it as we speak
Should be available OTA soon (how soon depends on each carrier)
http://www.mobilsiden.dk/nyheder/lg-alligevel-problemer-med-optimus-2x,lid.15324/
mikeyd85 said:
Fyi, I've never had AnyCut installed and I've had these problems.
Click to expand...
Click to collapse
Im not an expert, but its work for me. I will keep you all updated if reboot happen again.
Edit: just having my FB hang in 15 second and force to close. This definately due to sw problem.
Sent from my LG-P990 using XDA App
i will believe only when i will see one
spawndk said:
LG Denmark has just announced that they have acknowledged the problems and found a fix for it - they are currently sending out an update to correct it as we speak
Should be available OTA soon (how soon depends on each carrier)
http://www.mobilsiden.dk/nyheder/lg-alligevel-problemer-med-optimus-2x,lid.15324/
Click to expand...
Click to collapse
they said that gingerbread update will be on 18 april to and didnt
They said jun/jul. Check out dk site.
lmerega said:
They said jun/jul. Check out dk site.
Click to expand...
Click to collapse
Well thats the most realistic schedule
To the admins I apologize if this is in the wrong section if it is please move it accordingly.
Hello everyone, I have an issue, hopefully someone can hel me and it starts like this. I and everyone else have been waiting for months for a safe root method and a recovery system such as TWRP OR CWM just incase I fudge something up flashing custom roms so I can always go back to stock. I came across a safestrap article and decided it was something similar to what I was looking for. So I decided to root using the big K. I know not the best choice, you can boo me now.
After a successful root, I installed safestrap. Unfortunately safestrap kept crashing upon starting the app, I couldnt even get it to set up. thats fine, I was just going to unroot and keep on living life, but then I stumbled upon Xposed installer, that modified and tweaked like a custom rom but without all the risk according to a website. I said hey thats worth a try and I did. After the Xposed installer setup and a reboot, I wad looking for mods on the web and all of a sudden my apps and system files started crashing to the point that I could not use my phone. I immedeately uninstalled Xposed installer ss soon ad my phone stabalized and unrooted.
I thought everything was good, 4 hours later the apps and system files started crashing again, so I did a reboot and I noticed that custom with the lock came up on intial startup. though I was told I was unrooted by the K program and even double checked using a rootchecker app, which stated I had indeed an unrooted phone. I did another reboot and no custom or logo came out. At this point I just wanted a working phone and As much as I hated doing so I did a factory reset. This seemed to have fixed the problem, but 4 days later my phone randomly went into a bootloop. I couldnt get it to stop so I took out the battery and that did not fix it.It was strange becuase I thought it might have been unrelated since it wasnt doing this when I had the issue with Xposed installer.
After yet another factory reset my phone seems to be fine, its still too early to tell though since its only been about a day. I had the normal google playstore and gvoice app crashing...Sigh..the only thing different was that sometime yesterday after the second factory reset a notification popup of unfortunately a sytem file stopped working came up. I acknowledged it, but thankfully I havent gotten any problems. I forgot what the notification read. hopefully its not related to what happened the other day.I dont know if this is related to one another, but I did notice that before I rooted my android system had automatically upgraded. I looked for issues like this on the net and saw people where having random bootloops after system upgrades and that unchecking scanning for wifi fixed the problem. though I did this and it did not work, thats why I did the second factory reset.
Now Im asking for help if any further issues arise. I love my Note3 and at this point I just want a reliable working device. Im keeping my fingers crossed and hopefully that will be the end of it, but in case it started to act up again, what can I do? any information and help is greatly appreciated. thanks.
Never uninstall any Xposed app that changes system files without first reverting any changes you made with it. Some of them are permanent until they are turned off in the App. Then you can disable the module.
You may want to look into this http://forum.xda-developers.com/showthread.php?t=2559715
I cannot stress this enough.
READ READ READ.
Too many times have I seen someone read a line or 2 then rush right in ultimately turning their very nice phone into the most expensive paperweight one could own.
On that link I posted, read it until your eyes are bleeding if you truly need to start from scratch.
I am not joking here.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks man. it makes sense. I will look into it. you mentioned read. I have read what I thought was plenty, but always ideas and opinions differ, sometimes knowing too much and causing what they say decision paralysis. Because I still read about the Xposed experiences and different people go about it in a different way. but what you mentioned about reverting back makes alot of sense.
Hello all, wanting to use ADB to do a backup of my device. Running OSX 10.9, Moto X 4.4.2 VZW, unrooted, stock. I've downloaded the Android SDK, ran it, and updated it; downloaded and installed the Motorola drivers; enabled USB debugging; navigated to adb and can run commands, but when I run adb devices, it does not list my device. Any thoughts?
Thanks!
Its your drivers. They aren't letting your PC see the phone.
Now, I know nothing of Mac....so not sure what you can do. Except uninstall them completely. Download again and be sure they're the right ones. Also, try another cable perhaps.
KJ said:
Its your drivers. They aren't letting your PC see the phone.
Now, I know nothing of Mac....so not sure what you can do. Except uninstall them completely. Download again and be sure they're the right ones. Also, try another cable perhaps.
Click to expand...
Click to collapse
The phone is being recognized by the computer. I can transfer data and connect to Android File Transfer, etc. Just isn't being recognized by ADB. I'll try reinstalling the drivers, though.
patheimata said:
The phone is being recognized by the computer. I can transfer data and connect to Android File Transfer, etc. Just isn't being recognized by ADB. I'll try reinstalling the drivers, though.
Click to expand...
Click to collapse
Sometimes adb has issues while booted into android. Try this: Unplug the phone from the usb cable. Power it off.
Now, hold down the VOL DOWN button, and power it back on. You should boot into the bootloader. The screen will say something about "AP Fastboot Mode".
Now, plug the usb cord back in. adb devices should now respond with your connected phone, and your adb commands should work.
May I ask why you are backing up your phone via adb? Or more aptly, what do you plan to do with the backup? With a locked bootloader, there should be no way you will be able to restore whatever backup you plan to make. What am I missing?
Good Luck
samwathegreat said:
Sometimes adb has issues while booted into android. Try this: Unplug the phone from the usb cable. Power it off.
Now, hold down the VOL DOWN button, and power it back on. You should boot into the bootloader. The screen will say something about "AP Fastboot Mode".
Now, plug the usb cord back in. adb devices should now respond with your connected phone, and your adb commands should work.
May I ask why you are backing up your phone via adb? Or more aptly, what do you plan to do with the backup? With a locked bootloader, there should be no way you will be able to restore whatever backup you plan to make. What am I missing?
Good Luck
Click to expand...
Click to collapse
Thanks, I had intended to try the bootloader and quite frankly forgot as I got caught up troubleshooting other methods. I'll try that shortly and post results.
Meanwhile, you may be right. I've found lots of conflicting information. At least one person in the Motorola forums claims to have been able to do an adb backup and then restore it on his locked device after a FDR. I need to do one to try to deal with some battery issues. I was trying to find the path of least resistance for backup and restore, although I'm two days into researching this, so I can pretty well say this is no longer the path of least resistance, but I haven't wanted to give up, either, if it's possible...
patheimata said:
Thanks, I had intended to try the bootloader and quite frankly forgot as I got caught up troubleshooting other methods. I'll try that shortly and post results.
Meanwhile, you may be right. I've found lots of conflicting information. At least one person in the Motorola forums claims to have been able to do an adb backup and then restore it on his locked device after a FDR. I need to do one to try to deal with some battery issues. I was trying to find the path of least resistance for backup and restore, although I'm two days into researching this, so I can pretty well say this is no longer the path of least resistance, but I haven't wanted to give up, either, if it's possible...
Click to expand...
Click to collapse
My best advice would be to make a list of all the apps you need, save any pictures or files you need, do FDR, then use the list to re-install your apps, and copy your pictures / files back, and set everything back up the way you want it.
Even if you are able to 'backup via adb', and do a FDR, once you subsequently do your 'restore', you will have the exact same issues you are having now. Battery issues are usually caused by misbehaving apps, but even if you assume the issue is caused by something else, the method you are pursuing is ill-advised.
Ok, so when you do a FDR, it clears the data and cache partitions, essentially returning the device to factory assuming you haven't tried to do root exploits or similar.
If you do a restore, it writes to....(you guessed it!) the data and possibly cache partitions. You'll essentially be right back at square 1 so to speak because -whatever- the problem is, you'll RESTORE it...
EDIT: What kind of battery life are you getting on your X? Can you give us an idea how long it is lasting, and tell us a little about your usage patterns. How much time do you spend on calls, and how much of the time is the screen on?
With what I would consider 'average' usage, I normally get 14~18 hours between charges. This includes very little talk time, but regular internet usage, and usually 1-3 hours of internet radio streaming.
I'm just curious how long yours is lasting between charges.
samwathegreat said:
My best advice would be to make a list of all the apps you need, save any pictures or files you need, do FDR, then use the list to re-install your apps, and copy your pictures / files back, and set everything back up the way you want it.
Even if you are able to 'backup via adb', and do a FDR, once you subsequently do your 'restore', you will have the exact same issues you are having now. Battery issues are usually caused by misbehaving apps, but even if you assume the issue is caused by something else, the method you are pursuing is ill-advised.
Ok, so when you do a FDR, it clears the data and cache partitions, essentially returning the device to factory assuming you haven't tried to do root exploits or similar.
If you do a restore, it writes to....(you guessed it!) the data and possibly cache partitions. You'll essentially be right back at square 1 so to speak because -whatever- the problem is, you'll RESTORE it...
EDIT: What kind of battery life are you getting on your X? Can you give us an idea how long it is lasting, and tell us a little about your usage patterns. How much time do you spend on calls, and how much of the time is the screen on?
With what I would consider 'average' usage, I normally get 14~18 hours between charges. This includes very little talk time, but regular internet usage, and usually 1-3 hours of internet radio streaming.
I'm just curious how long yours is lasting between charges.
Click to expand...
Click to collapse
Absolutely.
First, agreed on the app and cache situation. I was going to exclude apps on the adb backup and just use it for pictures, settings, text messages, etc., and leave out of the backup would be potentially corrupting it after the FDR. I've used other apps in the past to back those things up, but the promise of adb seemed easier (and more fun), thus going that route. I think I've thrown in the towel on that plan at this point, but it has been a good learning experience as I learned a lot commands and troubleshooting methods in that department.
As far as battery life goes, I've had two devices. Started with a dev edition, and while I had that, I was really impressed that it would make it all day long and still have some battery leftover at the end of the day. I exchanged it for a MotoMaker edition, though. I'm not sure I ever remember this one getting as good as battery life as the other, although it's been 5 months, so it's hard to tell. Nevertheless, 18 hours would be fantastic for me.
GSAM says my average fully charged battery lasts 14 hours, with 7 hours and 4 minutes active time. That sounds pretty on par with you, but looking at the charts, I believe they're projecting from 100%–0% as I wouldn't say I typically make it from 100%–20%, which is when I always try to recharge by. The 7 hours active is where I assume my problem lies, and thus the desire to try an FDR. I use my phone a lot, but I'm not active on it for over 7 hours a day. GSAM says my average screen on time is 2h 8min, max of 2h 33min. (These averages are over a 2 month period.) In light of that, I'm regularly charging midday to make sure I can make it through the end of the night.
Regular usage patterns include very little by way of voice calling. I felt like I was on the phone a lot today, that was probably no more than 10–15 minutes. Most of the rest of the SOT time split between texting and internet/light app usage.
Android OS is of course the far and away process consuming battery, which I realize tells us nothing and isn't that uncommon, especially when the phone isn't in use.
Over the past few months, I've tried isolating the typical likely suspects (Facebook and Facebook Messenger, Google+, location services, etc.), uninstalling them, and looking for battery improvements to no avail. The only time I ever really saw a direct correlation with a particular app that I could trace has been with Google Camera. I haven't reinstalled it since they're most recent update, but while it was installed, after it's first update I dropped to about 6–8 hours of battery life.
I've also participated a good amount in this forum on the issue: https://forums.motorola.com/posts/6675cef7e3?page=31 which also happens to be where I read of user jason.motox's experience backing and and restoring with adb.
Alright, I think that's a good start from there. Would love anyone's thoughts on best practices, etc. As much as I hate the thought of adding a few apps at a time every few days, I know that's the best way to go to ensure it's not an app. But anything else that anyone else is aware of to watch out for would be useful. Also happy to post a list of currently installed apps if that would be useful.
EDIT (A thought I started and never completed in the original post): I have read in the Motorola forums of at least one user eventually having the cellular radio replaced in theirs, which solved their battery life. In a 31 page thread, I had only seen one user have a FDR actually fix their battery problems, so I haven't exactly been hopeful that it would help mine. In addition to that, since I remember my Dev Edition getting better battery life all things being equal, it does make me wonder if mine is more hardware related than app or software/firmware.
patheimata said:
Absolutely.
First, agreed on the app and cache situation. I was going to exclude apps on the adb and just use it for pictures, settings, text messages, etc., and leave out of the backup would be potentially corrupting it after the FDR. I've used other apps in the past to back those things up, but the promise of adb seemed easier (and more fun), thus going that route. I think I've thrown in the towel on that plan at this point, but it has been a good learning experience as I learned a lot commands and troubleshooting methods in that department.
As far as battery life goes, I've had two devices. Started with a dev edition, and while I had that, I was really impressed that it would make it all day long and still have some battery leftover at the end of the day. I exchanged it for a MotoMaker edition, though. I'm not sure I ever remember this one getting as good as battery life as the other, although it's been 5 months, so it's hard to tell. Nevertheless, 18 hours would be fantastic for me.
GSAM says my average fully charged battery lasts 14 hours, with 7 hours and 4 minutes active time. That sounds pretty on par with you, but looking at the charts, I believe they're projecting from 100%–0% as I wouldn't say I typically make it from 100%–20%, which is when I always try to recharge by. The 7 hours active is where I assume my problem lies, and thus the desire to try an FDR. I use my phone a lot, but I'm not active on it for over 7 hours a day. GSAM says my average screen on time is 2h 8min, max of 2h 33min. (These averages are over a 2 month period.) In light of that, I'm regularly charging midday to make sure I can make it through the end of the night.
Regular usage patterns include very little by way of voice calling. I felt like I was on the phone a lot today, that was probably no more than 10–15 minutes. Most of the rest of the SOT time split between texting and internet/light app usage.
Android OS is of course the far and away process consuming battery, which I realize tells us nothing and isn't that uncommon, especially when the phone isn't in use.
Over the past few months, I've tried isolating the typical likely suspects (Facebook and Facebook Messenger, Google+, location services, etc.), uninstalling them, and looking for battery improvements to no avail. The only time I ever really saw a direct correlation with a particular app that I could trace has been with Google Camera. I haven't reinstalled it since they're most recent update, but while it was installed, after it's first update I dropped to about 6–8 hours of battery life.
I've also participated a good amount in this forum on the issue: https://forums.motorola.com/posts/6675cef7e3?page=31 which also happens to be where I read of user jason.motox's experience backing and and restoring with adb.
Alright, I think that's a good start from there. Would love anyone's thoughts on best practices, etc. As much as I hate the thought of adding a few apps at a time every few days, I know that's the best way to go to ensure it's not an app. But anything else that anyone else is aware of to watch out for would be useful. Also happy to post a list of currently installed apps if that would be useful.
I have read in the Motorola forums of at least one user eventually having the cellular radio replaced in theirs
Click to expand...
Click to collapse
Who is your carrier? Are you rooted, or are you able to unlock your BL? There is a root app called "Greenify" that many people swear by. It helps identify potential 'problem apps', and actually allows you to 'hibernate' them.
This basically 'hides' the app from the system completely, but you don't notice. When you explicitly launch the app it functions 100% normally, but a short time after you exit it, it gets hibernated again so it can't suck any power.
If you are rooted, or if you may consider unlocking, I would suggest giving Greenify a try. It always sucks to have to charge mid-day.
Also remember that even if moto won't unlock your BL, the gentleman from China will...for a small fee of course
samwathegreat said:
Who is your carrier? Are you rooted, or are you able to unlock your BL? There is a root app called "Greenify" that many people swear by. It helps identify potential 'problem apps', and actually allows you to 'hibernate' them.
This basically 'hides' the app from the system completely, but you don't notice. When you explicitly launch the app it functions 100% normally, but a short time after you exit it, it gets hibernated again so it can't suck any power.
If you are rooted, or if you may consider unlocking, I would suggest giving Greenify a try. It always sucks to have to charge mid-day.
Also remember that even if moto won't unlock your BL, the gentleman from China will...for a small fee of course
Click to expand...
Click to collapse
Sadly I'm a Verizon user, and since I didn't keep my Dev Edition, my bootloader is locked down hard core. I'd love to use Greenify. Had it on my GNex (speaking of atrocious battery life!), but no such luck here. I've contemplated unlocking and rooting, but I have read a lot of horror stories of OTA updates with the X for those who are unlocked and/or rooted and just didn't want to deal with all that. In moments like these, though, it makes me want to send a few bucks to that Chinese gentleman...
patheimata said:
Sadly I'm a Verizon user, and since I didn't keep my Dev Edition, my bootloader is locked down hard core. I'd love to use Greenify. Had it on my GNex (speaking of atrocious battery life!), but no such luck here. I've contemplated unlocking and rooting, but I have read a lot of horror stories of OTA updates with the X for those who are unlocked and/or rooted and just didn't want to deal with all that. In moments like these, though, it makes me want to send a few bucks to that Chinese gentleman...
Click to expand...
Click to collapse
There are just a few caveats to being unlocked:
If a new OTA comes out, it is recommended to return to stock before accepting the OTA. This is because OTAs include a "manifest" of the files that SHOULD be present on the device, along with their checksums. A modified device often won't match the manifest.
Don't let this scare you though. We may not be updated past 4.4.2 heck, 4.4.3 hasn't been released on anything yet. And if we do get another OTA, you can SBF back to stock, take the update, and then re-install everything.
In my humble opinion, the ability to use root apps (especially TETHER) is much more important to me that the minor inconvenience of possibly having to set everything back up again in the future.
If you're considering it, I recommend you take the plunge. You will get your money back if he doesn't have your code. I was able to unlock my device using the China method this 2nd time around and my device is from Nov 2013 - he still had my code. So there ARE some 2013 models in his database for sure....or I wouldn't have gotten one.
If you suspect this is a hardware problem, unlocking is ill-advised as your warranty will be void. Even if you re-lock the bootloader, it will never show "LOCKED" - it will say "RE-LOCKED" instead......and they will know you had unlocked it.
Good Luck
Idk what's the problem with Samsung phones and updates. I had the same problem with my Note 3 when KitKat got released, I had to get a replacement phone. Lucky for me the replacements Note 3 didn't have the update on it. However I wasn't so lucky with the Note 4.
I accidently hit the update on my notifications when I was half sleep.
Anyways.
Every since Lollipop been installed on my Note 4, it has been a nightmare from hell.
When I installed it on my original Note 4, I kept having my keyboard become unresponsive. Force close on multiple apps (stock Web, camera, calender, and more).
I called T-Mobile to see if they could send me a replacement. They "tried" to fix it, saying that I should do a factory reset and clear cache , which I already tried before I called numerous times.
Finally they said they said they were going to send me out a replacement phone.
I also asked if anyone have been complaining about Lollipop they said no, they were totally oblivious to Lollipop having any kinks (as always ). It's crazy they said that because I have read over 100 post bashing the new update.
I received the Note 4. I turned the phone on and Lollipop was already installed. I called T-Mobile and asked why was Lollipop installed on my replacement, they informed me that they are sending out the phones with Lollipop, and assured there would be no problems with it.
With in the first hour, my phone would turn off and not turn back on. I knew there was nothing wrong with the battery because it was on 90% and it worked flawless with another phone. So I drained all the electricity out the phone and put the battery back in. That worked, but it did over 20 times within that day. I called T-Mobile again , they told me I would have to go to a store and see if they could diagnosis the phone.
The next day I went to the store, everything came back clear on the diagnosis, but they could see it turn off randomly.
I called customer care and explained the situation and told them I need a replacement.
Now I am waiting on a replacement. If this one don't work, I think I will have to get on whole different phone. I'm on the verge of getting a flip phone because I know that I don't want to have an iPhone.
Anyone having these issues with the update Lollipop?
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
MajorTom_ said:
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
Click to expand...
Click to collapse
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
W0man09 said:
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
Click to expand...
Click to collapse
As long as you can get it into download mode something may be possible.
Odin to stock lollipop, factory reset / data wipe.
Additionally, I would consider a custom rom.
..........
If you really like kitkat better you could also Odin to stock kitkat, factory reset / data wipe.
MajorTom_ said:
As long as you can get it into download mode something may be possible.
Click to expand...
Click to collapse
Lol thanks for the help. I can't even get it to turn on, to get it in download mode. ??
. Now I'm just waiting on T-Mobile to send the replacement.
I tried an OTA of Android Pie tonight, this was from EE UK.
First the system update couldn't verify, so I had to hard power off the phone, on powering on it re-installed and loaded up.
I unlocked the phone from the lock screen and it went to "Android Starting" and after a few moments rebooted.
Now the phone loads up but I can't unlock it, I just get constant PIN incorrects. It's a software issue because you never get to the limit of pin attempts, or the forgotten password option.
Contacted Sony, they've heard of it numerous times today, can't do anything about it.
They'll tell you to use Sony Companion to backup and restore, which you can't do unless the phones unlocked. So basically demand a full reset all data lost.
Update at your own risk, maybe consider removing device pin before the update if you can.
Same problem here in France.
There's a thread on talk.sonymobile: https://talk.sonymobile.com/t5/Xperia-XZ1-Compact/Can-t-access-phone-after-updating/td-p/1351581/page/2
So far no working solution.
The french sonyxperia twitter account is also useless.
No problem with the update here. Although, I don't have a device PIN, but a password.
After the update, some apps seem to run less stable than before...
zwan33 said:
No problem with the update here. Although, I don't have a device PIN, but a password.
After the update, some apps seem to run less stable than before...
Click to expand...
Click to collapse
backup ur photos/videos and make a factory reset, everything works flawlessly for me.
rideti.me said:
So basically demand a full reset all data lost.
Click to expand...
Click to collapse
It's a painful lesson, but backing up everything before doing anything is a must, even when doing something like an OTA update which you expect to work. I'm just waiting for a customized UK ftf to become available and will be doing a complete wipe which alleviates any unforeseen conflicts.
I had full backup, the corruption was in the pincode, therefore encryption control is lost. The backups are encrypted, I've recovered apps, messages, contacts etc.... But none of the appdata was recoverable without de-crypt.
I feel lucky: I used the repair function because I did not want to have all those small issues usually coming with a big OTA update. I did not expect such a big problem though.
Not to shove it in the face of all the people having this annoying issue, but I can confirm that with a fresh install everything is smooth and I haven't experienced any "big" bug as of yet. The phone seems even faster than with Oreo.
To be honest, besides the long process to reactivate the app of my bank, I don't even mind resetting all my apps every now and then, I noticed that it preserves battery life and performances. But I do understand that this may not be an option to some of you...
TechIntrigue said:
Just curious, why wait for the customized UK version? Does that have any benefits over the other firmware releases?
Click to expand...
Click to collapse
TBH, I'm not so sure, about either. Having read yesterday that the Singapore fw only has the Amazon app as bloat I'm going to install it today.
EDIT: Going back to Oreo as Substratum doesn't work without root.
Has anyone affected managed to do a full reset ?