Database Info

Nexus 5 and various issues, anything that can be done?

Alright,
Phone: Nexus 5 2013
Android: 5.1.1
Country: Canada
So I've started to get a lot of issues on my Nexus 5 that I ordered back in November 2013 (when it was released) and they are too big to be left alone. If I cannot fix them, I'll have to buy a new cellphone and there's none that interest me right now, nor that I want to change my current Nexus 5.
Issues:
My Nexus 5 doesn't connect to my cellular network anymore. I'll stay on "No service" and refuse to connect to any Operator Network stating that the network is unavailable at the moment, even thought it is. Sometimes, it'll connect to the network for 15 to 30 minutes, before losing it for the next 8 hours.
It becomes hot really, really quick randomly. The upper back part of it becomes hot, and according to the Nexus 5 architecture, the battery isn't even located there so I don't know what could make it heat up like that. This happens even without it being charged, and without me using it a lot (games, apps, etc.)
The phone will randomly restart for no reason, and sometimes stay stuck on a "boot loop" (Starting apps X of Y... before restarting).
The vibrate mode is messed up. It'll vibrate every 30 seconds for a notification (email, Facebook, SMS, etc.) despite the fact that there's nothing, absolutely nothing. Right now I disabled the vibration/sound mode to avoid that issue.
The battery gets drained really, really fast. Like overnight, while not being used it'll fall from 100% to 5%. It never used to do that. When I don't use it overnight, it would lose maybe 20%, even less than that. It started recently as well.
All these issues were present in past versions of Android, starting at 4.4 so I doubt the version is in cause here, but it's still a possibility I guess.
I got my SIM card changed for a brand a new one, troubleshooted the phone with everything I could find online before giving up and restoring it to it's default settings, but the issues are still present. I don't know what I should check anymore. If you have any comments, experiences or solutions I could try to solve my issues, please let me know since at this point I'll most likely try all of them. Also, if you need more information on my phone, system, etc. let me know as well.
Thank you.

Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk

There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.

firemaned said:
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It used to be rooted, but it's not anymore. Any way I can make sure that it's rooted or not? When I used the SuperSU app back then I realized at some point that it wasn't rooted anymore (it was telling me that this app can only be used on rooted devices). I think the bootloader is unlocked because when I open my device, it shows me the little lock icon, but it's open (unlocked). Also, it's freshly reset to factory default (from yesterday).

dahawthorne said:
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
Click to expand...
Click to collapse
I already did a Factory Reset on my phone yesterday, so I guess I don't have to do another one? Right now, if I follow what you just told me, I should wait until the release of Android 6.0 (M) and upgrade to it then see if it solves my issues. I just hope that it won't take a long time to be pushed to my phone like it was with Android 5.0. Or your other solution is to flash the latest preview for Android 6.0 (M) on my phone and see how it goes, right?

If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.

dahawthorne said:
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
Click to expand...
Click to collapse
That was my original plan. I called the Play Store support this week and they told me that my phone was elligible for a replacement till April of 2016. I found that weird because it would make it a 2 years and a half guarantee but at least I had my backup plan in mind. Then I called today to order a replacement and the guy told me that my guarantee expired back in November 2014 (1 year after I bought my Nexus 5, which made sense) so now I'm stuck with this one. I don't know why, but since this morning (after creating this thread), the cellular network cameback. It still drops sometimes but only for a few seconds and if not, I enable/disable the Plane mode to make it connect again. However, the battery drain, phone heat, random restart and messed up vibration issues are still present. I can deal with them however until Android 6.0 (M) gets released. The most important thing was the cellular network. We'll see tomorrow how it goes. Still awaiting tips and tricks for my other issues if anyone have some.
For the battery draining issue, I think I have the paid version of Greenify somewhere and was thinking of using it to see if it helps, even though I didn't have that issue at the beginning.

Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app

CalculatedRisk said:
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
And I imagine that the factory image is still present on the device? This is what I find weird, because when I "reset" my factory to defaults, it restores it to Android 5.1.1 even though the device came with 4.x. I come from the computer field, and a Factory Reset on a computer uses the manufacturer's image present on the CD, DVD, USB or partition given with the computer to reinstall the original OS that was present on it and the OEM software as well. If the computer was eventually upgraded to Windows 8.1 and came with Windows 7, Windows 7 will be restored, not Windows 8.1. So I can understand now that a "Factory Reset" doesn't really return the device to its factory state, right?

I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.

dahawthorne said:
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
Click to expand...
Click to collapse
I did have an OTA update to 5.1.1, yes.
And I talked to one of my friend who's really into phones (used to work for Bell and he's usually the person I go to whenever I have issues with my cellphone), and he suggested me to wait until Android 6.0 comes out, and then to fastboot it on my Nexus 5 since OTA updates can be buggy sometimes. I could actually fastboot the phone right now (well tonight) with Android 5.1.1, but if Android 6.0 is to come out next week (or the one after), it might worth the wait, depending on whether or not I can keep the cellular network working. Otherwise I would have to go through 2 flashboots in 2 weeks and I can't really be bothered to do that
And I don't know where the CPU is in the Nexus 5 (I could look it up) but the zone where the heat is isn't where the battery is so there's that. However, my friend told me that the fact that my cellular network isn't working could explain why the battery is being drained so fast, but can't explain the vibrate mode and random restarts issues.

I was having battery issues on Stock ROM, but now I am using CM12.1 so battery is not draining very fast.
When I am inside my home or in some other house or building, the network disconnects very often. However, if I am outside, the network works pretty well.
The notification LED, when being configured using CM12.1 settings, shows blue color on green color selection and green color on blue color selection.

I had some of the same problems with my phone, it would reboot randomly throughout the day. With mine if I charged it overnight with it off when I turned it on in the morning it would only be at 85%. I ended up contacting LG and I paid $170 to get it fixed, they have replaced the mainboard twice so far. After the second time it had no issues, and that lasted a couple months but I have sent it back again to be fixed. If you bought the phone on a credit card they usually extend the warranty by a year, that's what I did, filed a claim and they sent a cheque for the repair cost, very simple actually. But I suspect it might be the same problem as mine, some hardware issue, especially if you've reset the phone.

Just for info, the CPU is indeed at the top rear of the phone, so this is undoubtedly where the heat is coming from.
https://www.ifixit.com/Teardown/Nexus+5+Teardown/19016 - see step 11 saying "The Quad-core, 2.26 GHz Snapdragon 800 SoC is layered beneath the RAM".
I reckon it's a rogue app, which I hope isn't a system app, running wild - a system app will be hard to cure.
A ROM refresh is probably a good place to start, and if you can wait for Android 6.0 then why settle for less...

Wiped my os on nexus 5 trying to install nethunter only comes on in twrp. very new to this be easy on me ive previously installed a vm lab with kali linux.
I have downloaded adb and fastboot
Using winace . Before this my pc would not recognize my device, "no drivers". But now it shows up on the pc control panel as active and found
However snap pea still cant find drivers although now it says are you fornatting your phone with only one option "yes" then it just dissappear. ... but before I downloaded adb, fast boot ... snap pea was simply saying no drivers found.... Please help. ..thank you.
Sent from my GT-I8190 using XDA Free mobile app

Here's an update on my situation: the cellular network is back at both my house and my workplace. The way it works, it seems that it takes it a day to "adapt" itself to the location and then gives me network. So at first after the Factory Reset, I didn't have network at my house, the day after I did. Now, when I went to work on Monday I didn't have network, but when I did on Tuesday, I did. My job is an hour of road away too, and at some places on the road I don't get any network, but it happens less and less as I travel back and forth.
The random restart and overheating issue are still present however. I didn't test the notifications (on vibrate) but I will soon. As long as I have my cellular network, I don't care about the other issues, until Android 6.0 (M) gets released and I fastboot it on my phone.
Now, since I bought my Nexus 5 using a MasterCard, I remembered that they have a promotion which double the guarantee on electronics (up to a 1 year), which means that I have a 2 years guarantee on my phone. So I called LG, and they have a promotion right now, $150 to get my phone repaired by their tech center IF it can be repaired. If they can't, they send it back and gives me a 50% refund (around that number).
My current plan of action is to wait for Android 6.0 (M) to get released, flashboot it on my phone and see how it goes from there.
Thank you for all the replies so far, they really helped me and still help me today

Good luck man. Keep us updated.
Sent from my Nexus 4 using XDA Free mobile app

Alright so, I fastbooted Android 6.0 on my Nexus 5, and it seems to have done the trick. I have network everywhere now, even on the road. I still lose it from times to times (a few seconds only), but this is a "normal" behavior considering the carrier I have. The notification issue is also gone, and so does the restart issue since I didn't have it once so far. But I only fastbooted it yesterday evening so it might be too soon to say that.
Now, I still have the "overheating" issue, but it could be from me playing Fallout Shelter, I really don't know. I used to play Clash of Clans alot, and graphically speaking, I think it's more demanding than FS, but I never had that overheating effect before. One thing I noticed however is that after fastbooting Android 6.0, my battery drops real fast, even when idle. I thought that Android 6.0 was supposed to improve the battery life. I'll try to see what process, app or activity is taking the most juice out of it, but I'm sure this isn't normal.

Alright so it took me an hour to go from my house to my workplace, and my battery went from 34% to 12%, while being on standby. This isn't normal I guess. I'll need to charge it to 100% once, and then use the Battery setting to see what's taking all the juice.

Might have spoke too soon. When going to work today, I went in a room where there's usually no signal (or the signal is very weak), and lost the network. It's normal in that room so I didn't pay much attention to it, but now I'm not able to get back on the network. Even searching for the Network Operator fails. Sigh, it really looks like I'll have to send it to LG for repair. I guess I need to fastboot it first to erase all my data, because they need to use my phone to test the repairs they make?

Battery life lineage OS versus Color OS

Hi, I am thinking to flash lineage OS to my oppo R7 plus and I was wondering how good is the battery line in lineage OS as consider to color OS. Battery life is the most imp thing for me in my cell phone. Any body using lineage OS work oppo R7 plus - can your answer me with some figures. I wil like to know some numbers. Like if I am getting 24 hours in color OS, how many hours I will get in lineage OS?
Thanks for any answers.

Hey there i'm on the latest LineageOS build , your mileage may vary but from 100% to 0% in my experience is in 1 day and multiple hours , Screen on time around 7-8 hours. Good luck !

Hi, thanks for the reply. That sounds good. One more question, VOOC charging is supported by Lineage OS?
Thanks

aiglesh said:
Hi, thanks for the reply. That sounds good. One more question, VOOC charging is supported by Lineage OS?
Thanks
Click to expand...
Click to collapse
Of course. you'll see charging rapidly on your lock screen.

Thanks a lot.
Two last questions before I can go for it.
1. If I don't like lineage OS and want to go back to stock color OS, is there any tutorial for that ( I searched but found nothing and even the official international oppo forms are closed recently).
2. Any major drawback of lineage OS as compared to Color OS? Any major features that is not working on lineage OS?
Thanks again.

how did you managed to flash lineage os ? please help me

There is tutorial here on the forums. I have not yet flashed it though.

aiglesh said:
Thanks a lot.
Two last questions before I can go for it.
1. If I don't like lineage OS and want to go back to stock color OS, is there any tutorial for that ( I searched but found nothing and even the official international oppo forms are closed recently).
2. Any major drawback of lineage OS as compared to Color OS? Any major features that is not working on lineage OS?
Thanks again.
Click to expand...
Click to collapse
If I were you, I wouldn't touch LOS with a barge pole on this phone.
I've been running the nightlies (which are really weeklies) for months and they just seem to get less and less usable.
Firstly, forget Bluetooth if you use LOS. Using any BT headset or speaker usually results in an extremely sluggish and/or resetting phone if a call then happens. I can be quite happily walking along listening to TuneIn on a BT headset but, if a call then comes in, I have about a 20% chance of taking it without the phone dying. Same if I place a call. Which basically makes BT useless unless you never want to talk to anyone., which is kinda what they're for.
I also sometimes experience frequent random slowdowns just by activating the phone (maybe once per 2-3 days). It was working fine when I put it down. Then I pick it up and press the on switch. It then takes over a minute for the screen to come on, and further interaction with it is glacially slow until you reboot it.
Other times, it doesn't become unusably slow but is still noticeably sluggish (after activating) for no apparent reason.
Various apps crash that didn't crash before. Not always, but often enough to be annoying. In particular, Titanium Backup crashed on startup for months. It doesn't now. I don't know what changed.
Double tapping the screen to wake it up sometimes works and sometimes (maybe every 10 days) doesn't.
Battery life is noticeably less than stock.
GPS (Google Maps) doesn't always work. A few days ago I had to visit somewhere I'd never been to before. I tried to follow myself, on the bus. My position didn't update after leaving the bus station.
And don't get me started on TWRP as the recovery. It claims to support USB OTG but it doesn't, which is a major problem if you want to back up the phone to a USB flash stick. You can't. And the developer completely ignores bug reports about it.
I have two of the phones, both of the r7plusf model, so I'm sure these aren't problems with a specific phone.
And the nature of most of these problems is that you can't capture logs to file a bug.
All in all, if you have this phone just stick with what OPPO gives you, warts and all, unless you *really* want an ulcer. Or, if you really want to use LOS, get another phone.
Sorry for the late reply.
PS - if a dev happens to be listening, contact me. I'd love to help fix this stuff in any way I can.

NeBlackCat said:
If I were you, I wouldn't touch LOS with a barge pole on this phone.
I've been running the nightlies (which are really weeklies) for months and they just seem to get less and less usable.
Firstly, forget Bluetooth if you use LOS. Using any BT headset or speaker usually results in an extremely sluggish and/or resetting phone if a call then happens. I can be quite happily walking along listening to TuneIn on a BT headset but, if a call then comes in, I have about a 20% chance of taking it without the phone dying. Same if I place a call. Which basically makes BT useless unless you never want to talk to anyone., which is kinda what they're for.
I also sometimes experience frequent random slowdowns just by activating the phone (maybe once per 2-3 days). It was working fine when I put it down. Then I pick it up and press the on switch. It then takes over a minute for the screen to come on, and further interaction with it is glacially slow until you reboot it.
Other times, it doesn't become unusably slow but is still noticeably sluggish (after activating) for no apparent reason.
Various apps crash that didn't crash before. Not always, but often enough to be annoying. In particular, Titanium Backup crashed on startup for months. It doesn't now. I don't know what changed.
Double tapping the screen to wake it up sometimes works and sometimes (maybe every 10 days) doesn't.
Battery life is noticeably less than stock.
GPS (Google Maps) doesn't always work. A few days ago I had to visit somewhere I'd never been to before. I tried to follow myself, on the bus. My position didn't update after leaving the bus station.
And don't get me started on TWRP as the recovery. It claims to support USB OTG but it doesn't, which is a major problem if you want to back up the phone to a USB flash stick. You can't. And the developer completely ignores bug reports about it.
I have two of the phones, both of the r7plusf model, so I'm sure these aren't problems with a specific phone.
And the nature of most of these problems is that you can't capture logs to file a bug.
All in all, if you have this phone just stick with what OPPO gives you, warts and all, unless you *really* want an ulcer. Or, if you really want to use LOS, get another phone.
Sorry for the late reply.
PS - if a dev happens to be listening, contact me. I'd love to help fix this stuff in any way I can.
Click to expand...
Click to collapse
I'm on the same nightlies , i don't have any issues you mentioned (yes even bluetooth works perfectly) ! the only bug i have started with last month's nightlies which makes headphones audio stutter at low volume.

rch.aj34 said:
I'm on the same nightlies , i don't have any issues you mentioned (yes even bluetooth works perfectly) ! the only bug i have started with last month's nightlies which makes headphones audio stutter at low volume.
Click to expand...
Click to collapse
This blows my mind. What didn't I do right? Didn't I sacrifice enough chickens?
TBH the Bluetooth problem (at least) is well documented, as well as being a massive dealbreaker.
Funnily enough though I don't have an audio stutter problem. But I don't use physically attached headphones.
Are you open to a crash-off, in which we both install the same LOS version and (if necessary) start adding apps until we either see my problems or we don't?

rch.aj34 said:
Of course. you'll see charging rapidly on your lock screen.
Click to expand...
Click to collapse
This helped me too, thanks. I put an inline meter and it was only drawing 1.x amps but without the meter I can see "rapidly charging" on the lockscreen. Pity there is no battery icon change for Oppo's in LineageOS (14.1).
One more thing, if you're still active... which country are you in? I first put 15.1 on my R7Plusf and right off the bat WiFi didn't work.. even after reboot etc.
I flashed 14.1 and every single thing works perfectly so far!

Android 10 issues/bugs

Since Android 10 dropped, if anyone notices any bugs or issues I figured it would be good to make a thread about them. Been using Android 10 since it dropped, and one issue that I have noticed is my signal is more sloppy and inconsistent which may be a radio issue. I am using Sprint, but the signal has been more spotty and the reception overall has declined.

Biggest issue, battery drained so fast after update. Standby mode eat up more juice compare to Android 9. 9 was giving me 6-7 hrs SOT now it's just about 3-4 hrs SOT. Few apps which were using battery percentage half of it's usage time now using double battery.look like apps are not yet optimized for Android 10.

omky_b4u said:
Biggest issue, battery drained so fast after update. Standby mode eat up more juice compare to Android 9. 9 was giving me 6-7 hrs SOT now it's just about 3-4 hrs SOT. Few apps which were using battery percentage half of it's usage time now using double battery.look like apps are not yet optimized for Android 10.
Click to expand...
Click to collapse
I've had that too, but it's not too significant, and i wouldn't worry about it for the first few days while things optimize but i also noticed slight battery drain.
Been trying to update the signals. The radio is definitely having issues for my carrier.

Pixel 3 in the Call Application, my screen goes black after call in connected and I can't seem to get the screen to become active again until call is over and I hit the power button twice. This just started after an OTA update to 10...

I updated to 10 OTA and since updating my wifi calling isn't working. Whenever I try to toggle it, it just says that it's unavailable and to try again later. I haven't performed a factory reset because it's always such a pain to do that (especially with all the accounts I have using 2FA w/ Google Authenticator).
My cell/data reception has also been significantly decreased, according to my little indicator in the notifications.
Anybody else having these issues?

My reception has always been poor with this phone so I cannot confirm our deny that it's worse on Android 10 stable.
However I ota updated from final beta to stable 10 and my phone randomly goes home while I'm using it. Really annoying when having an app open to have the home screen constantly appear.

Personally I'm having between 2 and 3 hours of SOT, and always had those stats on Android 9 too, for very basic using (no calls, no gaming, no videos, slight browsing, few SMS, etc). Hope battery will be much better for the Pixel 4...

I forgot about this. My phone initially also got stuck on the boot screen. I was like oh great here we go. Apparently it's an issue. Android 10 appears to still be in beta mode despite being released as stable.
https://bgr.com/2019/09/05/android-10-update-for-pixel-phones-sensors-bug-explained/amp/

Unbeliavable, how google tries to force you towards its search engine!! I could probably get used to thr new gestures, but not to that notorious search bar!! There is no reason to block all Launchers from working with gestures. I hope somebody will soon hack that!

you are furthering probably biggest bug of Q (not affecting everyone though, but many people)
https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904

As I said in another thread, I have not been able to flash the factory image of either the .019 or .020 firmware. I've been doing the method of running the flash.bat file minus "-w" to prevent it from wiping my phone, using the latest SDK Platform Tools and after trying both they both cause a bootloop. My phone will attempt to boot up 2 different times and fail (assuming once for each partition, A & B?) then go back to fastboot mode.
Considering this other major bug with the sensors now not working, I guess holding off may actually a good thing for me for now.

Toronadian said:
.
Considering this other major bug with the sensors now not working, I guess holding off may actually a good thing for me for now.
Click to expand...
Click to collapse
i would definitively if i were you. not everyone is affected but some are so...

Sensors bug fixed thanks to great teamwork of many members in this forum! Solution available in sensors bug thread!!

Had no issue with sensors but am stock unrooted since the phone was purchased. From that link it appears it may be a rooting issue. I'm surprised that that it didn't go away though after wiping and reflashing stock images and relocking the bootloader

mikeprius said:
Had no issue with sensors but am stock unrooted since the phone was purchased. From that link it appears it may be a rooting issue. I'm surprised that that it didn't go away though after wiping and reflashing stock images and relocking the bootloader
Click to expand...
Click to collapse
still nobody knows what caused it but according to some users it seems it happened also for people who never modified their phones (people with not unlockable bl)

It's weird, this sensor bug everyone is having i never once had sth like that, flashed the official q factory image from beta 6 via the tool-all-in-one app. What i was thinking is, does the phone have different hardware revisions ? I am with the initial rev and can't tell

Gotten at least 3 random reboots since taking. Anyone else getting periodic recent app switching freezing or random reboots?

Hello.
I have the freeze too. Random freezing from the notification. Freezing with the recent app. Sometime black wallpaper with Nova Launcher.
The Q is with bug who don't have the beta or Android 9....

mikeprius said:
Gotten at least 3 random reboots since taking. Anyone else getting periodic recent app switching freezing or random reboots?
Click to expand...
Click to collapse
Yes, I've had a few random reboots since updating. It's been happening randomly in Google maps, YouTube, etc. I don't really want to factory reset unless I have to though.

Hey guys here is an android 10 bug on my Verizon pixel 3, when I goto the recent apps and try to clear them they will all get cleared and then when I go back to it they are all still there. Anyone else having this problem?
Im using google Launcher, and when I change the gestures sometime they all clear for good but sometimes they still won't until I restart the phone.

Is Oneplus became flagship to be killed?!

Hi
Idea if flagship killer was very cool to me so I really fall in love with OnePlus. I became part of community and I really want to help OnePlus to became really killer.
Today, after 4 Oneplus phones I am really disappointed, Oneplus became expensive top brand, flagship company. Rolling out Android 10 without serious testing for company's most expensive phone is most selfish and irresponsible move I ever seen. Looks like to me whole company working on Oneplus 7T Pro, and no one cares too much about "old" phone. This morning I was late for my work because alarm did not ring?! I don't know reason, I don't care why, I am user of 800€ phone and I don't expect that.
Wake up Oneplus,
I'm running official GM21AA on my GM1913 for 2 days, no root, just stock phone.
So far I noticed this problems:
- This morning my alarm did not ring?!
- After that disappointing situation I notices mobile data was off, so I have to turn it on manually
- Choppy audio on Bluetooth in my car ( I have to keep screen on for normal reproduction)
- Horizon Light don't work at all
- During Viber video call, video connection shuts down every few minutes, so I have to turn off then on video call constantly.
- Battery life was very nice first day, but second became terrible. Btw I have no issue with Viber, alarm clock, mobile data and Car Bluetooth during first day of using Android 10.
Any suggestions beside rolling back on Android P or selling and leaving OnePlus and back to Pixel phone

Why not do some research? There are a dozen things you can try to fix your issues. I updated from Stable 9 to 10 using Oxygen Updater and I have none of the issues you have so what is the difference? Maybe you have one or more apps that are not playing well with 10? Maybe you need to uninstall them and reinstall them so that they work better with 10? Maybe you need to do a factory reset (yes it is a pain) and DO NOT let your apps automatically reinstall from Google, to see if that fixes your issues? Or you could just sell the phone and go back to a Pixel! Then when you have the same types of issues with your Pixel you can complain on their forums about bugs and issues that you are not willing to try and fix. Solved!

NO. Still doesn't have wireless charging (which I miss A LOT) and the camera software is still not good.

Question Why does MIUI 13 (Android 12) feel so sluggish and generally-speaking slow on X3 Pro?

Hi everyone,
I was thrilled last night when my X3 Pro showed an upgrade to Android 12-based MIUI 13 was available. I downloaded the thing (all 3.1 GB of it...), install went without a hitch, ditto reboot, but I'm severely disappointed so far.
Everything feels slow and sluggish, even with the power slider set to Performance and the screen refresh rate pegged at 120 Hz.
Navigation in the Settings menu is OK, but all the other applications are slow to react. Scrolling up and down my Twitter timeline doesn't feel as snappy as it did before, when I was still on MIUI 12.x and Android 11.
Have any of you noticed the same thing? Did Xiaomi jump the gun with this update? I know Android must rebuild some system and application caches after each upgrade and all, but still, this doesn't quite feel right.
The only good thing is the battery life, which seems to have improved a bit, but that's all. DevCheck shows CPU peaks at 2.4 GHz under strain, but the Kryo core that's supposed to clock at 2.9 GHz never seems to wake up.
Did Xiaomi underclock the CPU the way Samsung does sometimes, to preserve battery life? Like I said, something's not right here...

Why do you even MIUI in the first place ?

I had the same. Only the factory reset showed the miui13 claw on Android 12. Tetaz everything runs smoothly. The battery holds up better.

I'm not inclined to do that just now. I've got tons of music and stuff on my phone and I really don't have the time at the moment, but push come to shove, maybe I'll have to do it.

jarco1 said:
Should i factory reset broh my miui updater was not working and everytime it was downloading corrupted zip so i downloaded it from the web with exact same name of the zip file from xiaomi server and updated in miui additional update.
Click to expand...
Click to collapse

Just updated my X3 Pro about an hour ago and I'm totally disappointed. It feels heavier and slower to respond overall. Apps like Twitter, Telegram, and Instagram seem much slower and laggy and stutter when scrolling. Twitter in particular runs like disaster. My phone was buttery smooth and did not have any lagging issue even when I tried to create one before this stupid update!!! Should I factory reset or wait for another update or something guys?

omidsr said:
Just updated my X3 Pro about an hour ago and I'm totally disappointed. It feels heavier and slower to respond overall. Apps like Twitter, Telegram, and Instagram seem much slower and laggy and stutter when scrolling. Twitter in particular runs like disaster. My phone was buttery smooth and did not have any lagging issue even when I tried to create one before this stupid update!!! Should I factory reset or wait for another update or something guys?
Click to expand...
Click to collapse
Mine is slowly getting there, in terms of ease of use and overall smoothness, so I suppose it's a matter of Android reconstructing apps and system caches after all. It's not quite as smooth as it was under 12.5.9, though, and some "features" are mildly annoying, like the fact that I have to tap the Return to home button twice to actually close some apps (but not all of them). It's hard to tell if the app itself is causing this or if it's an Android 12 trait.

UglyStuff said:
Mine is slowly getting there, in terms of ease of use and overall smoothness, so I suppose it's a matter of Android reconstructing apps and system caches after all. It's not quite as smooth as it was under 12.5.9, though, and some "features" are mildly annoying, like the fact that I have to tap the Return to home button twice to actually close some apps (but not all of them). It's hard to tell if the app itself is causing this or if it's an Android 12 trait.
Click to expand...
Click to collapse
I'm also seeing some improvements over time! Totally agree with you! It's getting better as things get reconstructed and stuff but STILL it feels slower than the snappy phone it was before the update. Seems we need to be patient! I don't think a factory reset is worth the time and hassle now that things are showing signs of getting back to normal.

I totally agree. I resort to factory reset only when necessary, with a gun to my head and a knife to my throat...
Let's give it a week or so and we'll see; After all, it's a big upgrade: new MIUI version + moving from Android 11 to Android 12.
Time will tell, but I'm relieved to see it's not my imagination if the phone feels slower!

UglyStuff said:
I totally agree. I resort to factory reset only when necessary, with a gun to my head and a knife to my throat...
Let's give it a week or so and we'll see; After all, it's a big upgrade: new MIUI version + moving from Android 11 to Android 12.
Time will tell, but I'm relieved to see it's not my imagination if the phone feels slower!
Click to expand...
Click to collapse
Agreed! Yup, it definitely is slower to my eyes too. It's no imagination. Sure, it's a BIG update and many enhancements and fixes are to follow in the near future!

Everyone decides for himself what he wants to do. I just wrote that after the update, the phone was stuttering and restoring the factory settings made it run faster and smoother as on miui 12.5.9.0 and it heats up less

Its 2022 and people still dont get that its good to do any major updates on clean phone or do factory reset to remove any issues, official or not, its just how android work really :/
People always had such issues and they probably will have them in the future.
Its not like your life depend on getting new software, so just update later when you have some free time to do clean install or do factory reset.
It remind me of installing custom ROMs when you get feeling that its smoother. Well most of that speed came from having clean system, and after month or two you loose some of it. Here you have clooged system with your stuff and app cache, and you throw on top new OS... you will get some issues...

You guys should know that it is highly recommended to reset during a major Android update if you don't then don't be surprised by weird bugs.

its the common rule,when you are updating any rom on any device,its proper to factory reset and built from then.....i believe its a dirty installation even if you factory reset-install rom-restore data from recovery....even that it will give you some errors....noticed last time with a11,restored from backup ,and the time between restarts,is way to more.....

I have the same problem. I updated it on March 16 (Wednesday) and it's obviously buggy and slow. Google discover on the home screen was so unstable I had to remove it altogether. Phone lags in being unlocked by fingerprint, and locking it with two taps is done without any animation. Gallery is un-usable too as it's become to slow and it stutters. The game boost slider in games is un-usable as it interferes with the game so I've disabled it. I am NOT happy with this upgrade.
Battery might've improved but I suspect they've sacrificed the performance.

just install a custom rom

John1337 said:
I have the same problem. I updated it on March 16 (Wednesday) and it's obviously buggy and slow. Google discover on the home screen was so unstable I had to remove it altogether. Phone lags in being unlocked by fingerprint, and locking it with two taps is done without any animation. Gallery is un-usable too as it's become to slow and it stutters. The game boost slider in games is un-usable as it interferes with the game so I've disabled it. I am NOT happy with this upgrade.
Battery might've improved but I suspect they've sacrificed the performance.
Click to expand...
Click to collapse
You can read. After all, many people wrote that after such a large update, and even more so, switching from android 11 to 12, it is advisable to do a factory reset and you will not have any problems. The fluidity will increase significantly and the battery will hold better. It's so hard to understand. The same is done when installing a custom rom.

jarco1 said:
You can read. After all, many people wrote that after such a large update, and even more so, switching from android 11 to 12, it is advisable to do a factory reset and you will not have any problems. The fluidity will increase significantly and the battery will hold better. It's so hard to understand. The same is done when installing a custom rom.
Click to expand...
Click to collapse
Maybe work on your grammar and semantics first, and then talk about things being difficult to understand. It's common knowledge that a factory-reset is advisable after an upgrade, and it's not like you're imparting arcane knowledge by saying a factory-reset should be done. What is being discussed here are bugs encountered after an upgrade, and since it's android 12 it's expected that a factory reset shouldn't be needed.
Check your attitude, no one asked for help.

In my opinion, Miui's overall optimization on this phone is a disaster. In one year they haven't been able to correct the Google Discover's tremendous lag yet (I think they haven't even tried to). I have done a totally clean installation of Miui 13 Android 12 via fastboot (using miflash). I must say that the optimization now is even worse than it was before the update. The phone just feels slower. Of course we can use custom roms, but it is Xiaomi's responsability to do a much better work with their software.

I hid the notification and I will not update for a long time until I know that there are improvements to something, since the beta I read that the version has problems :/