Related
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?
Guys,
I haven't updated my H8 to Nougat because of the bugs with EMUI5.
Are the issues fixed? Are there still issues? Is so what are they?
Can somebody provide a honest opinion. Because the current EMUI4.1 is so good and i don't want to regret the upgrade. Thanks.
Emui 5 is far better than emui 4.1,but the battery backup is soon good in emui4.1
Rommco05 said:
Which issues you mean?
Click to expand...
Click to collapse
I heard there was a gyroscope issue. And what about performance and battery. Is there slowness in overall user experience?
bala1701 said:
I heard there was a gyroscope issue. And what about performance and battery. Is there slowness in overall user experience?
Click to expand...
Click to collapse
All are good
If you're a heavy user and value battery efficiency more than having the latest Android firmware, then don't upgrade. I went back to EMUI4. 1 a week ago due to excessive battery drainage in EMUI5.
I used Nougat since it became available for the H8 and battery life was less than in MM and even worst with the latest update for the US version (B385). My screen on time went from 6 hours to barely 4 hours.
Also having to recharge my phone 3 to 4 times in a day was not worth it staying with EMUI5. I even rebranded my phone to use the L19's firmware (B389) but it was the same story with the battery in addition to loosing VoLTE and band 12.
But don't get me wrong, I do like the interface updates and the improvements in performance in Nougat. It's just that for me battery is more important.
Zero issues in B389, battery a tad better the MM versions. Never charge device more than 1x/day, sometimes 1x/1.5 day.
Dominikrod said:
If you're a heavy user and value battery efficiency more than having the latest Android firmware, then don't upgrade. I went back to EMUI4. 1 a week ago due to excessive battery drainage in EMUI5.
I used Nougat since it became available for the H8 and battery life was less than in MM and even worst with the latest update for the US version (B385). My screen on time went from 6 hours to barely 4 hours.
Also having to recharge my phone 3 to 4 times in a day was not worth it staying with EMUI5. I even rebranded my phone to use the L19's firmware (B389) but it was the same story with the battery in addition to loosing VoLTE and band 12.
But don't get me wrong, I do like the interface updates and the improvements in performance in Nougat. It's just that for me battery is more important.
Click to expand...
Click to collapse
Thanks. Mine is Indian version. I'm a heavy user and battery life does matter to me. I was so tempted to press the update button but pulling myself out of it. I already get only 4.5 to 5 hours on heavy usage. So will skip the upgrade then. Thanks again!
Rommco05 said:
Performance is higher how on Marshmallow and with battery I don't have any problems, this can be related which model you have and which firmware you are able to install. Gyroscope issue... I don't know
Click to expand...
Click to collapse
Mine is Indian version
bala1701 said:
Thanks. Mine is Indian version. I'm a heavy user and battery life does matter to me. I was so tempted to press the update button but pulling myself out of it. I already get only 4.5 to 5 hours on heavy usage. So will skip the upgrade then. Thanks again!
Click to expand...
Click to collapse
Bro b330 update i got 6hr+
venugopalu007 said:
Bro b330 update i got 6hr+
Click to expand...
Click to collapse
You mean nougat update for FRDL02 has no battery issues? But at top of this thread you also mentioned this :
"Emui 5 is far better than emui 4.1,but the battery backup is soon good in EMUI4.1"
Im confused..
bala1701 said:
Thanks. Mine is Indian version. I'm a heavy user and battery life does matter to me. I was so tempted to press the update button but pulling myself out of it. I already get only 4.5 to 5 hours on heavy usage. So will skip the upgrade then. Thanks again!
Click to expand...
Click to collapse
Use i am also saying that emui 4.1 sucks less compared to 5.0 . Emui 4.1 is the best for battery but we want the new version of Android should have to leave the old one
Also in emui 5.0:
In lockscreen clean up disable apps to run in back ground . U can also get 6+
Rommco05 said:
Anyway if compare look betwen EMUI4 and EMUI5, emui5 is much better, looks a bit more stable and fast. Google security patches is newest how on emui4 and in future if want upgrade to Andoid O (hopefuly we got it) u will must anyway upgrade first to emui5 Nougat. Emui5 have lot of settings which can help improve battery life
Click to expand...
Click to collapse
I can't get security patches on MM Emui 4 unless I upgrade and that's sad. But the performance with EMUI 4 on H8 is truly amazing. I have never had a single instance of lag or slowness in the two months I have had this. Truly flagship device. Buttery smooth and I'm thoroughly enjpyong this beauty. I'm afraid this will not be the case once I upgrade. So let me stay with this till we get the news on Android O.
bala1701 said:
Guys,
I haven't updated my H8 to Nougat because of the bugs with EMUI5.
Are the issues fixed? Are there still issues? Is so what are they?
Can somebody provide a honest opinion. Because the current EMUI4.1 is so good and i don't want to regret the upgrade. Thanks.
Click to expand...
Click to collapse
There are still some minor bugs, which you will never notice (maybe). But I would like to say its 96% stable. :fingers-crossed:
bala1701 said:
Guys,
I haven't updated my H8 to Nougat because of the bugs with EMUI5.
Are the issues fixed? ...
Click to expand...
Click to collapse
Personally, I wouldn't touch the EMUI 5 and Android 7 combination.
I did the upgrade long time ago (I think it was B360, and it was done automatically; I just had to touch a button that said "Upgrade", and kept prompting me for two weeks).
Battery had to be recharged every 2 hours, even without using the phone. Temperature was so hot that I had to put the phone in the refrigerator, honestly.
Many essential application were totally messed up or became useless, including the camera software.
Following a Huawie customer service rep in live communication to go back to EMUI 4.1 and Android 6 resulted in bricking the phone.
I sent it to their service center in Texas (per their instructions).
They found that the excessive heat had caused plenty of internal component deterioration, so it was useless to unbrick it and send it back.
Since it was still under warranty, they sent me a new one (with EMUI 4.1 and Android 6).
Service was fast and excellent.
I became a happy camper again.
EMUI 5 is most likely better than 4.1, but the problem of installing it is that you must install Android 7 as well.
I'm sure Android 7 is better and more advanced than 6, but it is not optimized for the Honor 8.
I would NOT touch that combination of EMUI 5 and Android 7 on the Honor 8 with a 100 foot pole!!
From what I understand, EMUI 5.1 is released.
That is my experience, and it is up to you if you decide to upgrade.
Cool_Man99 said:
Personally, I wouldn't touch the EMUI 5 and Android 7 combination.
I did the upgrade long time ago (I think it was B360, and it was done automatically; I just had to touch a button that said "Upgrade", and kept prompting me for two weeks).
Battery had to be recharged every 2 hours, even without using the phone. Temperature was so hot that I had to put the phone in the refrigerator, honestly.
Many essential application were totally messed up or became useless, including the camera software.
Following a Huawie customer service rep in live communication to go back to EMUI 4.1 and Android 6 resulted in bricking the phone.
I sent it to their service center in Texas (per their instructions).
They found that the excessive heat had caused plenty of internal component deterioration, so it was useless to unbrick it and send it back.
Since it was still under warranty, they sent me a new one (with EMUI 4.1 and Android 6).
Service was fast and excellent.
I became a happy camper again.
EMUI 5 is most likely better than 4.1, but the problem of installing it is that you must install Android 7 as well.
I'm sure Android 7 is better and more advanced than 6, but it is not optimized for the Honor 8.
I would NOT touch that combination of EMUI 5 and Android 7 on the Honor 8 with a 100 foot pole!!
From what I understand, EMUI 5.1 is released.
That is my experience, and it is up to you if you decide to upgrade.
Click to expand...
Click to collapse
Thanks. I have made up my mind to stay with EMUI4.1 based on the inputs on this thread and yours add up to the list. When it comes to Android I always believe a phone works best only out of the box and any upgrade takes it a step back. I have had this experience with a lot of devices. So i think it's best to stay with the version that comes out of the box if you want to really enjoy the device. Because this is the version that was tested/ optimized/advertised by the manufacturer. Just my opinion... :good:
Cool_Man99 said:
Personally, I wouldn't touch the EMUI 5 and Android 7 combination.
I did the upgrade long time ago (I think it was B360, and it was done automatically; I just had to touch a button that said "Upgrade", and kept prompting me for two weeks).
Battery had to be recharged every 2 hours, even without using the phone. Temperature was so hot that I had to put the phone in the refrigerator, honestly.
Many essential application were totally messed up or became useless, including the camera software.
Following a Huawie customer service rep in live communication to go back to EMUI 4.1 and Android 6 resulted in bricking the phone.
I sent it to their service center in Texas (per their instructions).
They found that the excessive heat had caused plenty of internal component deterioration, so it was useless to unbrick it and send it back.
Since it was still under warranty, they sent me a new one (with EMUI 4.1 and Android 6).
Service was fast and excellent.
I became a happy camper again.
EMUI 5 is most likely better than 4.1, but the problem of installing it is that you must install Android 7 as well.
I'm sure Android 7 is better and more advanced than 6, but it is not optimized for the Honor 8.
I would NOT touch that combination of EMUI 5 and Android 7 on the Honor 8 with a 100 foot pole!!
From what I understand, EMUI 5.1 is released.
That is my experience, and it is up to you if you decide to upgrade.
Click to expand...
Click to collapse
bala1701 said:
Thanks. I have made up my mind to stay with EMUI4.1 based on the inputs on this thread and yours add up to the list. When it comes to Android I always believe a phone works best only out of the box and any upgrade takes it a step back. I have had this experience with a lot of devices. So i think it's best to stay with the version that comes out of the box if you want to really enjoy the device. Because this is the version that was tested/ optimized/advertised by the manufacturer. Just my opinion... :good:
Click to expand...
Click to collapse
Maybe it happened with just you. You cannot blame EMUI for the trouble. Yeah I admit that it had some bugs at the beginning. Almost all the Android Phones get them at the beginning, even iOS. An year or two ago I had Galaxy Grand Prime and it didn't boot up after it's lollipop/marshmallow update. So I sent it to Samsung and they fixed it. @Cool_Man99 same as they fixed yours. And it's totally functional even today. Well my mom is using that now. And yeah maybe you faced the problem with your device unnecessary heating, so did I. My device also used to get hot while listening to music at night or maybe while i am in school. Also i was not able to install any 3rd party apps in it. As much as I remember they released some patches and I swear now there are no issues that I am facing. Ooh yeah, I never had the battery draining issue, ever. You can ask other people on the forum too if all of them faced issues like you. ?
@bala1701 maybe you did set your mind to stay but you can just give EMUI 5 a try. Then if you think you are having any issues you can just roolback. It's not that hard.
Saeem said:
Maybe it happened with just you. You cannot blame EMUI for the trouble. Yeah I admit that it had some bugs at the beginning. Almost all the Android Phones get them at the beginning, even iOS. An year or two ago I had Galaxy Grand Prime and it didn't boot up after it's lollipop/marshmallow update. So I sent it to Samsung and they fixed it. @Cool_Man99 same as they fixed yours. And it's totally functional even today. Well my mom is using that now. And yeah maybe you faced the problem with your device unnecessary heating, so did I. My device also used to get hot while listening to music at night or maybe while i am in school. Also i was not able to install any 3rd party apps in it. As much as I remember they released some patches and I swear now there are no issues that I am facing. Ooh yeah, I never had the battery draining issue, ever. You can ask other people on the forum too if all of them faced issues like you. ?
@bala1701 maybe you did set your mind to stay but you can just give EMUI 5 a try. Then if you think you are having any issues you can just roolback. It's not that hard.
Click to expand...
Click to collapse
Yes sure I will definitely give it a try in the future. But as of now I am at peace with EMUI4.1/MM
@Saeem
No it didn't happen just to me.
Lots of people were having similar problems, and that was all over the Internet, including here at XDA and at Huawie forums and Support sites.
Huawie back then created a page with downloadable packages and instructions to switch back to EMUI 4.1 / Android 6.
As I had mentioned before, the battery drain and the excessive overheat were happening even without the phone being used at all, and with the screen turned off.
It wasn't even possible to turn the phone off, or to restart it. These soft buttons were messed up and not functioning properly.
Huawie did not fix the phone, as I had indicated. They replaced it with a new one. It was not fixable..
Glad you and your mom are having no issues.
You might be able to experiment with new software/firmware releases, but many people use the phone for business purposes, and other critical issues. In such uses they cannot afford to be experimenting with buggy Beta releases of software.
Such people use their phone to do things other than play games, text a classmate, or chat with their moms.
You will understand what I mean someday down the road.
Thanks for your input, though.
Cool_Man99 said:
@Saeem
No it didn't happen just to me.
Lots of people were having similar problems, and that was all over the Internet, including here at XDA and at Huawie forums and Support sites.
Huawie back then created a page with downloadable packages and instructions to switch back to EMUI 4.1 / Android 6.
As I had mentioned before, the battery drain and the excessive overheat were happening even without the phone being used at all, and with the screen turned off.
It wasn't even possible to turn the phone off, or to restart it. These soft buttons were messed up and not functioning properly.
Huawie did not fix the phone, as I had indicated. They replaced it with a new one. It was not fixable..
Glad you and your mom are having no issues.
You might be able to experiment with new software/firmware releases, but many people use the phone for business purposes, and other critical issues. In such uses they cannot afford to be experimenting with buggy Beta releases of software.
Such people use their phone to do things other than play games, text a classmate, or chat with their moms.
You will understand what I mean someday down the road.
Thanks for your input, though.
Click to expand...
Click to collapse
I didn't know that. But thanks :good:
https://twitter.com/sarvikas/status/955753890770665472
Get it here :
https://www.nokia.com/en_int/phones/betalabs
Cool. Bought the phone today, and it's already on 8.1. Hoping Nokia will keep up the pace
I have been battering it since installing and i cant make it cough, splutter or hiccup, seems all but finished to me rather than a beta.
Not quite. I discovered and reported a rather annoying kernel wakelock that doesn't allow CPU deep sleep for hours, causing battery drain.
amunarjoh said:
Cool. Bought the phone today, and it's already on 8.1. Hoping Nokia will keep up the pace
Click to expand...
Click to collapse
Do you mind doing a system dump for me? If you need help look up how to do a system dump, but I think you need root and do adb /pull system .
xterminater07 said:
Do you mind doing a system dump for me? If you need help look up how to do a system dump, but I think you need root and do adb /pull system .
Click to expand...
Click to collapse
Hi, and thanks for asking. At the moment I am so happy with the barbone Android, that I don't see a reason to root. Maybe at some other point in time...
By the way, it took just a few seconds to enter Nokia beta and download the 8.1.
aoleg said:
Not quite. I discovered and reported a rather annoying kernel wakelock that doesn't allow CPU deep sleep for hours, causing battery drain.
Click to expand...
Click to collapse
Thats weird, everyone else is reporting better battery life.
amunarjoh said:
Cool. Bought the phone today, and it's already on 8.1. Hoping Nokia will keep up the pace
Click to expand...
Click to collapse
amunarjoh said:
Hi, and thanks for asking. At the moment I am so happy with the barbone Android, that I don't see a reason to root. Maybe at some other point in time...
By the way, it took just a few seconds to enter Nokia beta and download the 8.1.
Click to expand...
Click to collapse
I do not have the phone, I have another phone that uses the same sensors as the Nokia 8, that's why I would like to have the system dump so I can see some information regarding cameras. Or if you can link me to the beta download that would be great. I can try to pull files and info from it.
I haven't noticed any crashes on this beta, but the battery life is definitely worse for me.
This device has no root, so pulling the system will be difficult I think.
MrBelter said:
Thats weird, everyone else is reporting better battery life.
Click to expand...
Click to collapse
That's what beta testing is for. "Works on my computer", you know, is not an acceptable excuse for programmers doing paid work. In some circumstances, on some models, in some regions, with some mobile service providers, etc, etc, you get intermittent weird problems that are impossible to catch during the "closed" beta testing phase. On my phone, there is almost no CPU deep sleep due to some kernel wakelock (I cannot get more details than this without root access, and there's no root for this model). After 3 days on 8.1 beta, I rolled back to 8.0 stable; no wakelock issues whatsoever. Of course, I submitted a comprehensive bug report before rolling back, so hopefully HMD catches and squashes this bug.
If you set animations to 0.5x you can notice the speed improvement more. Though could be placebo. Before 0.5x was more choppy and 8.1 feels smoother.
8.1 is definitely smoother!
The double tap on recent apps (for fast change) are waaay faster and without a single hiccup for me.
Battery have better stand-by with wifi and auto sync on.
Less than 1% per hour! (almost two hours to drain 1%)
Sent from my Nokia 8!
aoleg said:
That's what beta testing is for. "Works on my computer", you know, is not an acceptable excuse for programmers doing paid work. In some circumstances, on some models, in some regions, with some mobile service providers, etc, etc, you get intermittent weird problems that are impossible to catch during the "closed" beta testing phase. On my phone, there is almost no CPU deep sleep due to some kernel wakelock (I cannot get more details than this without root access, and there's no root for this model). After 3 days on 8.1 beta, I rolled back to 8.0 stable; no wakelock issues whatsoever. Of course, I submitted a comprehensive bug report before rolling back, so hopefully HMD catches and squashes this bug.
Click to expand...
Click to collapse
Wow chill your beans, i am fully aware what beta testing is and i certainly do not need preaching to about it by the likes of you.
I was about to report that the standby times on my phone are also reduced but i don't think i'll bother now, you seem to have it all covered with your comprehensive report.
I observe that when i take my phone out of my pocket it automatically unlocks the screen lock( i put my finger on fp sensor when i take my phone out of my pocket). After that i checked if there is a problem with the light sensor, so i covered it so it couldn't get any light but still unlocked the phone when i used my fp to unlock it. Do you guys have that problem? Also to note that when i am making phone calls light sensor works like normal.
Sent from my TA-1012 using XDA Labs
USB tethering also doesn't seem to be working correctly and causes reboots.
still no ambient display......
Also the pop up when i want to disable the mobile data is frustrating. Is there a way to disable this?
Sent from my TA-1012 using XDA Labs
bluetooht not working
bluetooht also doesn't seem to be working correctly and causes reboots. when i make calls over carkit
hennieh said:
bluetooht also doesn't seem to be working correctly and causes reboots. when i make calls over carkit
Click to expand...
Click to collapse
I'm using Bluetooth with two different car kits, speaker and headphones. No issues at all. Actually it seems to be using less power than on 8.0.
On 8.0 sometimes I couldn't connect to car kit. On 8.1 this issue seems to be gone.
This is the kind of battery life i am getting now after a few days running the beta, i still think standby times are worse but not shockingly so.
Just out of curiosity of how many of us here downgraded from Oreo to Nougat.
I just downgraded last night from N to O after running it for about a month or so and to be honest the Bluetooth unstable connection on Oreo was just getting out of hand, plus I felt like the device was slower and battery life is a little worse?
Might be me but I felt Nougat was the sweet spot for this device. I tried resetting my phone a few times and nothing got me satisfied with the update. In fact just last night I was out of town, I had to use Google Maps to get around and I had music playing, 5 mins later went to check my phone and it crashed! Yes this is the first time I have ever experienced this phone crashed and restarted out of almost the year I've owned this device. Also the system notifications were getting quite annoying but that's very minuscule. Not downing on Oreo but I believe Huawei could've done a better job with this update, truly disappointed, got back at 3am and got back to Nougat and haven't looked back since, at least until some good comes out of Oreo.
Did you downgraded from Oreo to Nougat?
If so, what are your reasons and why?
XERO_Racer said:
Just out of curiosity of how many of us here downgraded from Oreo to Nougat.
I just downgraded last night from N to O after running it for about a month or so and to be honest the Bluetooth unstable connection on Oreo was just getting out of hand, plus I felt like the device was slower and battery life is a little worse?
Might be me but I felt Nougat was the sweet spot for this device. I tried resetting my phone a few times and nothing got me satisfied with the update. In fact just last night I was out of town, I had to use Google Maps to get around and I had music playing, 5 mins later went to check my phone and it crashed! Yes this is the first time I have ever experienced this phone crashed and restarted out of almost the year I've owned this device. Also the system notifications were getting quite annoying but that's very minuscule. Not downing on Oreo but I believe Huawei could've done a better job with this update, truly disappointed, got back at 3am and got back to Nougat and haven't looked back since, at least until some good comes out of Oreo.
Did you downgraded from Oreo to Nougat?
If so, what are your reasons and why?
Click to expand...
Click to collapse
Downgraded cause I missed Xposed framework, then updated and decided to give it a real go, playing asphalt 8, and the game gets slow, then crashes the phone completely, resulting in a restart, not sure if it's the game though or the phone, **** never happened on nougat though, procrastinating about going back to it, cause it was cool.
I did downgrade to Nougat because i felt that with Oreo my phone got a little slower, xposed of course, media volume steps that i couldn't increase on Oreo.
shae23 said:
Downgraded cause I missed Xposed framework, then updated and decided to give it a real go, playing asphalt 8, and the game gets slow, then crashes the phone completely, resulting in a restart, not sure if it's the game though or the phone, **** never happened on nougat though, procrastinating about going back to it, cause it was cool.
Click to expand...
Click to collapse
For a few weeks it was an off and on debate to go back to Nougat till yesterday finally happened, no regrets either
gioarvdv said:
I did downgrade to Nougat because i felt that with Oreo my phone got a little slower, xposed of course, media volume steps that i couldn't increase on Oreo.
Click to expand...
Click to collapse
Yeah I had the impression the phone felt much slower with Oreo
Same here, Nougat seems to be best fitted - snappy, fast fingerprint, background services friendly. Only incall volume steps could be doubled (like in Oreo).
I've downgraded twice now. (it is much easier I found to downgrade to nougat in order to rebrand the device). Also, since you can use hisuite to downgrade (not on all firmwares but most, it makes it so easy). I have also used Firmware Finder to downgrade and has worked for me too. As for experience wise thus far, I have still upgraded and gone back to oreo. Like some of the added features.
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.