Help - Xiaomi Poco X3 NFC Questions & Answers

So I purchased two pocox3 NFC phone at once, both can at once, so a Mr and Mrs have both the same phones, we have used for a few weeks. Now we noticed a big difference between the two phones. See image. Any help be great

It's normal that some are factory updated while some may be from a older batch. Since you're on the NFC Europe version you obviously have access to Android 11 while the other device probably has an update waiting. Just check for updates and both phones will be on Android 11 (12.0.6).
As far as the navigation buttons...those can be disabled/enabled on Full Screen Display - Show Buttons.

Related

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?

M5 - Android Enterprise

I missed this, both the 10in & 8.4in are part of the Android Enterprise program, delivering at least one major OS update (9) and "Delivery of Android security updates within 90 days of release from Google, for a minimum of three years"
https://www.google.com/amp/s/www.bl...ar-of-excellence-for-enterprise-mobility/amp/
https://www.android.com/enterprise/device-collection/#android_enterprise_recommended
I'm wondering if Huawei will release Android 9 (Pie) in 90 days. It would be really cool. I hope they will.
edit: It looks like, it is meant just for security patches
The commitment to get googles enterprise seal of approval is all of the following;
Patches for 3 years within 90 days of google release
At least 1 major OS version update
So at minimum, Android pie, and a patch every 3 months for 3 years. But possibly more...
Just give me 8.1 so I can use Netflix PiP. That's all I want.
Sent from my HTC U12+ using Tapatalk
EU device stuck on July update, as soon as Google drop the October patch on my pixel, I'm starting a media campaign about how Huawei have already broken the Android Enterprise 90 day commitment. I'm returning both our devices for refund as they were sold under deception. I
Tick tock.....
The media lap up this sort of news.
I got .182 ist (C432) on my CMR-W09 20 minutes ago. IT has Security fix 01.08.2018.
Gesendet von meinem CMR-W09 mit Tapatalk
with CMR-AL09 still in 8.0.0.161(C432) / Security Patch: June 1, 2018,
3 months passed, almost 4 months
After a month, still the same situation.
No security patches, no 8.1, and I should stop because speaking about Android P on M5 is just an illusion.
Firmware with july, august and September security patches (on October) are "available" on HFF.
Shame yourself Huawei, shame yourself.
Inviato dal mio CMR-AL09 utilizzando Tapatalk
You really need to be talking to Google to get Huawei booted off the Android Enterprise programme, it's giving the programme a bad name. At least Samsung had the decency not to enrol rather lie about updates ...
Funny how I thought Huawei will make sure all their flagship tablets will be updated regularly.
I am also stuck on .169 with july security update but via HFF I keep seeing some other regions are getting their updates and it makes me wonder if it is really Huawei's fault or just some regional bureaucracy stoppage.
I don't quite understand why updates with Android is so difficult. For Windows, updates will go to ANY computers, any brand or no brand. If anything, Windows 10 updates are forced down the users' throat wanted or not.
Why can't Google take more control of their own OS's updates? It is not as if PC makers don't mess with and install crap over Windows, yet the core OS will get updated without the need for any help from the PC makers.
alvinlwh said:
I don't quite understand why updates with Android is so difficult. For Windows, updates will go to ANY computers, any brand or no brand. If anything, Windows 10 updates are forced down the users' throat wanted or not.
Why can't Google take more control of their own OS's updates? It is not as if PC makers don't mess with and install crap over Windows, yet the core OS will get updated without the need for any help from the PC makers.
Click to expand...
Click to collapse
Google is going into that direction now with Treble, but unless almost all OS versions are not treble compatible there is no force to do so. In addition as Google has no possibility to push out updates to end customer devices directly (beside Pixel / Nexus devices) but only by the channel of producer / provider they need their cooperation ... but unfortunately updates don't sell new devices, in contrary they stimulate people to use their devices longer. Do you see the dilemma?
AndDiSa said:
Google is going into that direction now with Treble, but unless almost all OS versions are not treble compatible there is no force to do so. In addition as Google has no possibility to push out updates to end customer devices directly (beside Pixel / Nexus devices) but only by the channel of producer / provider they need their cooperation ... but unfortunately updates don't sell new devices, in contrary they stimulate people to use their devices longer. Do you see the dilemma?
Click to expand...
Click to collapse
I completely agree with this part "updates don't sell new devices". However it can also apply equally to computers. I cannot understand why Windows can retain control of their OS (too much in fact for Windows 10) but Google cannot. Is it not in Google's interest to have a stable and secure OS?
I think Project Treble (and Android One I think) is a way to retain control, but Google stills leaves it to manufacturers to implement it or not right?
alvinlwh said:
I don't quite understand why updates with Android is so difficult. For Windows, updates will go to ANY computers, any brand or no brand. If anything, Windows 10 updates are forced down the users' throat wanted or not.
Why can't Google take more control of their own OS's updates? It is not as if PC makers don't mess with and install crap over Windows, yet the core OS will get updated without the need for any help from the PC makers.
Click to expand...
Click to collapse
windows is a massive mess when it comes to updates, Microsoft has to tip-toe around drivers, and even then they always mess up, and you end up waiting for the OEM to release a driver update package, which they never do. Then you hunt the drivers yourself, and find the OEM's who made the parts, are now out of business, or simply do not support the products anymore.
I have an Asus T100taf and I don't think autobrightness will ever work again on it, quite a shame really.
Michaelflat1 said:
windows is a massive mess when it comes to updates, Microsoft has to tip-toe around drivers, and even then they always mess up, and you end up waiting for the OEM to release a driver update package, which they never do. Then you hunt the drivers yourself, and find the OEM's who made the parts, are now out of business, or simply do not support the products anymore.
I have an Asus T100taf and I don't think autobrightness will ever work again on it, quite a shame really.
Click to expand...
Click to collapse
At least my 8 years old Windows 7 laptop is still getting updates. Can't say the same for a 2 years old Android.
I noticed you are having problem with a Windows 10 tablet, that one is indeed a massive mess, no option to delay or turn down updates, Windows will force the updates through no matter you like it or not, often disrupting the use of equipment with massive slowdowns or reboot. Worse, sometimes bricking the computer. At least on Windows 7, I can delay accepting updates for a few weeks/months to give them a chance to pull dodgy updates.
Point I am trying to make here is on Windows (7 at least), I can tell the OS to look for an update from its makers and install it if it is available, the OEM of the machine have no input in this process. Where as on Androids, I have to depend on the maker of the OEM to update my OS which is not made by them. I know that OEMs often customise (meaning mess around) with the Android OS but so do many Windows computer OEMs yet the core Windows OS still get updated regularly.
Also, Asus is not quite out of business, but they are the worse for providing updated firmware. I had a ZF3 (Android) for a few months and every single update breaks the phone a little. They released a final update that breaks many functions for many users (check their own forum) and then say they will not be providing anymore updates. I now avoid anything with an Asus name on it.
alvinlwh said:
At least my 8 years old Windows 7 laptop is still getting updates. Can't say the same for a 2 years old Android.
I noticed you are having problem with a Windows 10 tablet, that one is indeed a massive mess, no option to delay or turn down updates, Windows will force the updates through no matter you like it or not, often disrupting the use of equipment with massive slowdowns or reboot. Worse, sometimes bricking the computer. At least on Windows 7, I can delay accepting updates for a few weeks/months to give them a chance to pull dodgy updates.
Point I am trying to make here is on Windows (7 at least), I can tell the OS to look for an update from its makers and install it if it is available, the OEM of the machine have no input in this process. Where as on Androids, I have to depend on the maker of the OEM to update my OS which is not made by them. I know that OEMs often customise (meaning mess around) with the Android OS but so do many Windows computer OEMs yet the core Windows OS still get updated regularly.
Also, Asus is not quite out of business, but they are the worse for providing updated firmware. I had a ZF3 (Android) for a few months and every single update breaks the phone a little. They released a final update that breaks many functions for many users (check their own forum) and then say they will not be providing anymore updates. I now avoid anything with an Asus name on it.
Click to expand...
Click to collapse
I had a ZF3 also, that phone didn't really last that long, but I found it fine for the year I had it, accidentally took it swimming (RIP). I had a good experience with the updates, Zen UI was a bit heavy, but it did get Android N, shame about Oreo. But after that I have ditched them, there are better manafacturers, I was considering the Asus Zenfone 3 zoom as my next phone, but they sabotaged it with a snapdragon 625. I would have preferred something faster. Every phone they have has a flaw on it, which is a real shame. I would get an Asus 5z for example, but LCD err no, my OP5T has spoiled me with Amoled glory
Asus is still in business, but I mean on the individual device level, I can't find a driver for a "Capella Micro Brightness sensor xxxx" can't remember the numbers but I put it into Google and nothing, can't find any drivers for that, so bye bye autobrightness. That tablet also is kinda dead, I broke the screen on it, and apart from 2 that I replaced (and broke again, by opening the device too far!!) the replacements don't work, they have phantom touches or are very weak. The device was flawed from the get-go, it was mainly held together with the front glass, now I removed it, it is very wobbly and weak.
Android tablets, at least they aren't broken by updates so much, I had an Asus tablet, but an update came along, and bricked it!! I told Asus and they agreed about an RMA (within warranty period thank god), but I also managed to break the screen on that (god I'm a nightmare, except my phone has no scratches or scuffs ) but besides that tablet I don't think has any updates, it topped out at Android N also, despite having a relatively simple SOC and everything.
This one, the MediaPad M5 has been the best so far, I've had about 3 updates, bug fixes mainly, but also GPU Turbo, they did take a while pushing that to the EU, but at least it was still done!
At least I can root and do what I want with my devices now, unlike my Mediatek Asus tablet, and the Windows one, that is toast now anyway, slow atom cpu.
Funnily enough, the MediaPad M5 is the most powerful laptop I own, it zips through web pages where my Asus devices will be chugging along, and well my iPad 2 might load it tomorrow
Windows was good, until 10. I have a windows XP laptop, that is fully supported on 7, missing a GPU driver for Windows 10, but there is a fan made one! (never heard of this happening before) and it works, but I prefer windows 7 as it's more fitting for the device.
Michaelflat1 said:
I had a ZF3 also, that phone didn't really last that long, but I found it fine for the year I had it, accidentally took it swimming (RIP). I had a good experience with the updates, Zen UI was a bit heavy, but it did get Android N, shame about Oreo. But after that I have ditched them, there are better manafacturers, I was considering the Asus Zenfone 3 zoom as my next phone, but they sabotaged it with a snapdragon 625. I would have preferred something faster. Every phone they have has a flaw on it, which is a real shame. I would get an Asus 5z for example, but LCD err no, my OP5T has spoiled me with Amoled glory
Asus is still in business, but I mean on the individual device level, I can't find a driver for a "Capella Micro Brightness sensor xxxx" can't remember the numbers but I put it into Google and nothing, can't find any drivers for that, so bye bye autobrightness. That tablet also is kinda dead, I broke the screen on it, and apart from 2 that I replaced (and broke again, by opening the device too far!!) the replacements don't work, they have phantom touches or are very weak. The device was flawed from the get-go, it was mainly held together with the front glass, now I removed it, it is very wobbly and weak.
Android tablets, at least they aren't broken by updates so much, I had an Asus tablet, but an update came along, and bricked it!! I told Asus and they agreed about an RMA (within warranty period thank god), but I also managed to break the screen on that (god I'm a nightmare, except my phone has no scratches or scuffs ) but besides that tablet I don't think has any updates, it topped out at Android N also, despite having a relatively simple SOC and everything.
This one, the MediaPad M5 has been the best so far, I've had about 3 updates, bug fixes mainly, but also GPU Turbo, they did take a while pushing that to the EU, but at least it was still done!
At least I can root and do what I want with my devices now, unlike my Mediatek Asus tablet, and the Windows one, that is toast now anyway, slow atom cpu.
Funnily enough, the MediaPad M5 is the most powerful laptop I own, it zips through web pages where my Asus devices will be chugging along, and well my iPad 2 might load it tomorrow
Windows was good, until 10. I have a windows XP laptop, that is fully supported on 7, missing a GPU driver for Windows 10, but there is a fan made one! (never heard of this happening before) and it works, but I prefer windows 7 as it's more fitting for the device.
Click to expand...
Click to collapse
Going off topic now but...
My Asus ZF3 is the ONLY phone (Android or not) that I had problem pairing the Bluetooth with my car. I am not the only one with the problem, people from US, TW, ES, BR, MY, etc all had reported the same problem. What Asus suggested is changing the car and some guy from US actually did that and still cannot pair his phone with his car. Instead of admitting that there is a fault with their messing around with the core firmware that broke the Bluetooth function, they insist it was someone else's fault. 2 or 3 updates later, the Bluetooth function was fixed BUT then they broke the camera focus (by then I had already dumped it). Based on their own forum, it seem that the update caused the OIS motor to burn out making it impossible move the lens to focus. For many owners, this point in time is already beyond 1 year of the original purchase date, making the phone out of warranty and costing them money to fix it, thanks to Asus's own update. Looking at their forum today, after the final update (Asus abandoned the phone now), the camera problem is still not fixed and there now are battery fast draining problem, WiFi problem, OTG problem, signal strength problem, missing VoLTE... Their support is useless, asking them something as technical as you "Capella Micro Brightness sensor xxxx" problem will get them all confused.
On to Windows, I hated Windows 10 so much that I actually use my 8 years old Windows 7 i3 laptop more often than my 3 years old Windows 10 i5 laptop. While the i3 is slower and less powerful, it is more predictable without the random crashes of Windows 10. Worse of all, Windows 10 likes to install updates and reboot without warning, causing serious inconvenience and could lead to a brick if it try to install an update on shutdown when the laptop is low on power.
...going back on topic now about the M5
I do agree with you that the M5 is pretty damn good in most aspect except the DPI and the thing seems to be confused about if it is a phone or a tablet, causing strange rendering of some apps. However (personally) I do find that Android devices do slow down to a point of almost unusability after around 18 months and I am very careful about installing the "final" update. I had 2 tablets (Toshiba AT300 and Nvida Shield K1) so far that are kind of rendered almost unusable after the "big final" update.
I do not root my devices anymore after a really bad experience where I bricked a brand new Motorola Atrix 4G thanks to a guide with incorrect instructions (I copied and pasted the commands so it was not a mistype by me) and I got laughed out of the forum (cannot remember if it is here or somewhere else) without any help. Can't afford to brick brand new devices all the time.
alvinlwh said:
I don't quite understand why updates with Android is so difficult. For Windows, updates will go to ANY computers, any brand or no brand. If anything, Windows 10 updates are forced down the users' throat wanted or not.
Why can't Google take more control of their own OS's updates? It is not as if PC makers don't mess with and install crap over Windows, yet the core OS will get updated without the need for any help from the PC makers.
Click to expand...
Click to collapse
Its very simple. A mobile phone is not a PC. There is no IBM PC specification, no BIOS or common HAL. On a PC you need to install drivers and do all sorts of other maintenance. You have problems with abandoned PC hardware, which in a PC you can swap out with something else, you have driver incompatibility problems left right and centre, a fragile registry, DLL dependency hell, a joke of a security model, A PC slows down badly over time, due to its bloated servicing model, Android devices don't (unless the manufacturer is bullied into putting a version of OS it was never intended to run on it). PC is a upgradable long term device, mobiles are non upgradable disposable devices.
Its very clear you don't understand the technical difference between a PC and a mobile device. Come back when you do. Don't feel bad, the cretins in the tech press don't understand either, and it's their job to understand...
CrazyPeter said:
Its very simple. A mobile phone is not a PC. There is no IBM PC specification, no BIOS or common HAL. On a PC you need to install drivers and do all sorts of other maintenance. You have problems with abandoned PC hardware, which in a PC you can swap out with something else, you have driver incompatibility problems left right and centre, a fragile registry, DLL dependency hell, a joke of a security model, A PC slows down badly over time, due to its bloated servicing model, Android devices don't (unless the manufacturer is bullied into putting a version of OS it was never intended to run on it). PC is a upgradable long term device, mobiles are non upgradable disposable devices.
Its very clear you don't understand the technical difference between a PC and a mobile device. Come back when you do. Don't feel bad, the cretins in the tech press don't understand either, and it's their job to understand...
Click to expand...
Click to collapse
It is very similar to a PC, well a linux running PC. Yes there are a few limitations, but you can run alternate OSes on android devices, eg. remember the Ubuntu on your phone type thing, that didn't last long because driver support doesn't really exist for components in your phone.
It's a shame it isn't i suppose, but then again i made the decision to buy a tablet over a windows laptop. I can't really argue which one is better, since we could be here all day. Sometimes it's nice to have a mobile device, others it is a crushing limitation. Thankfully i got my bootloader unlock code before it was too late!
What a shame
Android 9 and no Netflix PIP . Can't believe that I choose wrongly with the M5 ... There's a lot of potential but lack of interest by developers ( Netflix to be specific) and Huawei itself.

Android 10 obliterated my phone.

As the title says.
My phone has no longer been the absolute powerhouse that it once was since Android 9.
I'm aware many of you will spout that "U shld downgrid bak 2 vershion nooin?!?!"
Believe me I have.
The issues are still present.
So my issues are as follows:
My camera app is completely broken on version 10.3.3 (downgrading fixes this stupid issue / rooting removing and replacing the app)
Light sensitivity / screen rotate module is broken / turned off as most apps are telling me that it's non existent / not plugged in. (Downgrading / rooting / custom ROM does NOT fix this issue) I've tried all the usual crap with this case.
The keyboard issue
The stupid bar at the bottom that we can't utilise as we AREN'T PIXEL DEVICES ONEPLUS. I've heard a few people say to me that it's there for additional features and that we should get used to it. Well contrary to that information is the fact that the OnePlus team "fixed the keyboard bar" on the latest Beta ( which is now redundant ((cheers onepiss))
Battery related issues (Which can be fixed with downgrade / ROM)
To me it just seems like the Dev team gave up trying to optimise every OnePlus 6 phone they have out there as I seem to be a very specific case. I wanted this phone to last me at least four years but it feels like the dodgy updates are ensuring my regrets with buying a OnePlus phone.
:silly:
By mistake i did try it....
Aplications crash.....freeze.......
In resume:
I nuke it, and return to 9.0.9 full rooted and unlocked.
My best mode at this time would be a new physical battery....
Glad I'm not the only one!

Lenovo table yoga yb1-x90f EOL but maybe not

Lenovo has stopped all updates to android tablet yb1-x90f several years ago. It's a non-phone, wifi tablet. Machine is nice, has great screen display, keyboard is nice, and works well but software is now getting 3-4 years old.
I recently dissambled it to replace battery. Broke keyboard in removal process but got a new one installed. All works well (new battery and keyboard) but would like to update software.
I'd like to resume system android updates or, perhaps, even remove android and replace with linux if it will work. I have a pinephone that I am getting to finally work decently.
thanks for any knowledgeable ideas. tom kosvic
Updates ( read: patches to existing OS ) only get rolled by OEMs if they deem it necessary.
Yes, lenovo discontinued updates but can I restart them in some manner or even replace OS with linux?

Question Terrible battery drain then not syncing with phone related to Android 13?

Over about the last week my Watch4 Classic (SM-R890) went from lasting about 2 1/2 days on a charge to well less than a day. I could not figure out what was going on. I ended up resetting my watch and uninstalling/reinstalling all software on phone. After this I could not setup/sync watch to phone. I did everything I saw on-line to resolve this issue. No luck. My watch is unusable. I saw some reports on-line that there are issues with Watch4 and Android 13. It then occurred to me that I started having the battery issues about the time I updated my phone ( Pixel 6 Pro) to Android 13. Is anyone else here having battery/sync issues since updating to Android 13?
So I was able to setup watch finally. Surprisingly I was able to setup watch correctly when I disabled wifi on my phone. I have no idea on why this worked. After resetting my watch and uninstalling/reinstalling all software on phone I sill have battery issues. Definitely well less than a day. Last night as I slept I lost about 50% battery and I had bedtime mode on. Two weeks ago I would lose 5 - 8% overnight with bedtime mode. Other people are having this issue:
https://www.reddit.com/r/GalaxyWatch/comments/wqo3iu
https://www.reddit.com/r/GooglePixel/comments/x6fb76
I'm not running Samsung health on phone. This is apparently probably not a watch software or watch hardware issue. This is being reported with multiple wearos devices across manufacturers (Like TWP3). It appears to be related to Android 13.
Is there anyone here that has Android 13 on their phone who is not having battery issues?
Not that anyone cares based based on replies but apparently the Sept. Android 13 update addresses Bluetooth issues.
https://9to5google.com/2022/09/06/android-13-pixel-september-update/
I'm in US on Verizon. Apparently Verizon updated yesterday (9/12) the Pixel 6 Pro (TP1A.220905.004.A1). I keep checking for update, not yet. It is definitely Bluetooth issue with Android 13. I turned off Bluetooth on my phone and battery on watch is same as before Android 13 update. Hoping update fixes....
Sorry bro for no replies, it's just that we don't have Android 13 yet.
I am on the Android 13 beta on my Samsung S22 Ultra with the Watch 4 Classic. The watch has the latest load on it since I was on the watch beta. I have had no issues with my watch not lasting at least a full day. I have seen no difference from Android 12 to Android 13.
I received the Android 13 Sept. update (TP1A.220905.004.A1) and sadly this does not fix the issue. Such a bummer. You would think that Google would get this fixed. Given this is an issue with other wearos watches I wonder if this will impact the Pixel Watch...
Fixed issue. After trying many things ultimately it ended up the issue was related to updating from Android 12 to 13 instead of clean update. When I factory reset my phone the watch's battery life is back to normal. It was not Google Assistant or Samsung Health.
Android 12 battery & watch syncing has been working good for me. I have not tried 13 yet....
GW4C and A13, no issues at all..
Sorry people weren't replying and showing you love princess.

Categories

Resources