I've read a lot about certain MTK phones having a number of issues running GSI Roms. In addition, I've read a decent amount about the changes in treble implementation for phones released with 9.0 as opposed to 8.0 or 8.1. I'm debating getting the Umidigi F1 and am wondering if there is any reason to be hopeful that it may be more successful running GSI roms than previous phones? I'm on T-Mobile and bands 2/4/12 are very solid in my area with band 71 still a ways out. As a result, I really like the hardware for the price point, but given reviews for their other phones as well as Umidigi's history, I don't really have much of an interest running the phone with its stock software. Assuming it's not going to have a development community, I thought I'd throw it out those far more knowledgeable on the technology and ask if I could reasonably hope for it to be fully functional on a stock GSI?
Thanks
We have the phone rooted (though only on Magisk 17.3, help @topjohnwu?). The stock software is not super but also not completely terrible. The most offensive thing about it to me is the Google bloatware, ironically. It's missing the Pie gesture navigation, but it does have a decent navbar implementation and a passable if a little outdated gesture navigation system with a few decent options, all involving a swipe up. It's not too bad, and can be extended further with some Play Store apps. I mean, it's basically the typical "pretty much AOSP, but with a couple odd MediaTek tweaks" that I've come to expect from western targeted MediaTek devices from manufacturers like BLU. The Fingerprint sensor is pretty bad. I can only hope UMIDIGI will make it better with software updates. I find it's usable after you get used to it, and it gets used to you, but still occasionally annoyingly inaccurate, and not super duper fast at that (actually passing a fingerprint test is very fast on the off chance it works the first time but unlocking takes a sec). These would basically be my major gripes with buying one at this time.
I haven't really tried getting anything with Treble running, but we do have a TWRP that supports it (though I will openly admit it's kinda shady).
Check out UMIDIGI's forums. They let people talk about rooting their phones in the device sections, and even post guides for how to do it themselves, lol.
EDIT: It's probably also worth noting that UMIDIGI will probably never attempt to lock this phone down in any way. It having shady Chinese firmware is a blessing because for the most part, no matter how hard you brick the phone, you can use MediaTek's SP Flash Tool to unbrick it, and unlike BLU, UMIDIGI probably will never take that away. To be fair, that also comes with certain security risks, because not only is the bootloader easily unlockable (in a somewhat Nexus-like fashion with fastboot), I don't think it actually verifies the boot signatures even if the bootloader is locked. Fastboot won't let you flash anything but you can use SP Flash Tools to bypass that and flash unsigned software anyway. Personally I would still unlock the bootloader anyway. Even though it extends the boot time by five seconds, it allows you to use standard Android platform tools for your usual, non debricking activities, because I don't like MediaTek's much.
Thanks for all the insight on the phone. Your observations seem to echo a lot of what I have seen written about their products in general of late. It should essentially be a stock experience, as they advertise their OS as such, but their version of "stock" seems to come with it's own set of quirks that can be frustrating. In addition, they seem to do a poor job of writing software that lives up to the hardware, as exhibited by your fingerprint experience or some of the things I've read about their camera software. All of the little minor issues are why I was hoping it could run a Pie GSI with fewer hangups on account of it being released with 9.0. Admittedly, I don't know much about the details, just read enough to be optimistic about the newer phones playing a little nicer with GSI roms.
I did notice that it had an unofficial TWRP version for the phone. I may take a shot at it and hope for a little development or successful GSI experience down the road. It is nice knowing that your stock experience isn't terrible, though. I've read some horror stories about previous Umidigi phones and hopefully that is no longer the case with their newer releases.
Thanks again for the thoughts.
ColtonDRG said:
We have the phone rooted (though only on Magisk 17.3, help @topjohnwu?). The stock software is not super but also not completely terrible. The most offensive thing about it to me is the Google bloatware, ironically. It's missing the Pie gesture navigation, but it does have a decent navbar implementation and a passable if a little outdated gesture navigation system with a few decent options, all involving a swipe up. It's not too bad, and can be extended further with some Play Store apps. I mean, it's basically the typical "pretty much AOSP, but with a couple odd MediaTek tweaks" that I've come to expect from western targeted MediaTek devices from manufacturers like BLU. The Fingerprint sensor is pretty bad. I can only hope UMIDIGI will make it better with software updates. I find it's usable after you get used to it, and it gets used to you, but still occasionally annoyingly inaccurate, and not super duper fast at that (actually passing a fingerprint test is very fast on the off chance it works the first time but unlocking takes a sec). These would basically be my major gripes with buying one at this time.
I haven't really tried getting anything with Treble running, but we do have a TWRP that supports it (though I will openly admit it's kinda shady).
Check out UMIDIGI's forums. They let people talk about rooting their phones in the device sections, and even post guides for how to do it themselves, lol.
EDIT: It's probably also worth noting that UMIDIGI will probably never attempt to lock this phone down in any way. It having shady Chinese firmware is a blessing because for the most part, no matter how hard you brick the phone, you can use MediaTek's SP Flash Tool to unbrick it, and unlike BLU, UMIDIGI probably will never take that away. To be fair, that also comes with certain security risks, because not only is the bootloader easily unlockable (in a somewhat Nexus-like fashion with fastboot), I don't think it actually verifies the boot signatures even if the bootloader is locked. Fastboot won't let you flash anything but you can use SP Flash Tools to bypass that and flash unsigned software anyway. Personally I would still unlock the bootloader anyway. Even though it extends the boot time by five seconds, it allows you to use standard Android platform tools for your usual, non debricking activities, because I don't like MediaTek's much.
Click to expand...
Click to collapse
teeterteeter said:
Thanks for all the insight on the phone. Your observations seem to echo a lot of what I have seen written about their products in general of late. It should essentially be a stock experience, as they advertise their OS as such, but their version of "stock" seems to come with it's own set of quirks that can be frustrating. In addition, they seem to do a poor job of writing software that lives up to the hardware, as exhibited by your fingerprint experience or some of the things I've read about their camera software. All of the little minor issues are why I was hoping it could run a Pie GSI with fewer hangups on account of it being released with 9.0. Admittedly, I don't know much about the details, just read enough to be optimistic about the newer phones playing a little nicer with GSI roms.
I did notice that it had an unofficial TWRP version for the phone. I may take a shot at it and hope for a little development or successful GSI experience down the road. It is nice knowing that your stock experience isn't terrible, though. I've read some horror stories about previous Umidigi phones and hopefully that is no longer the case with their newer releases.
Thanks again for the thoughts.
Click to expand...
Click to collapse
I mostly bought the phone for the excellent North American band support, it's one of the few cheaper Chinese phones that do. I'm a fan of Xiaomi's products but band support is typically pretty limited unless you pick up the really high end ones. My biggest gripe with TWRP right now is that USB doesn't work which means you have to transfer all your zips to a microSD card since internal storage is borked thanks to forceencrypt, which we can disable now. I don't mess with the camera too much, typically, but the app itself looks pretty basic. It again reminds me of the usual stuff you would get on MTK phones, there aren't a whole lot of options but the ones that are there look OK-ish? Idk, again, I don't take many pictures. This morning I tried to flash a GSI and my phone just started bootlooping but I didn't follow the procedure at all so I probably missed a step. I will try some more in the future and let you know.
The band support was the biggest reason I was looking at the phone as well. There are certainly a ton of cool, unique new phones coming out that lack the necessary bands in the US.
Thanks again for sharing all the first-hand experience with the phone. You certainly don't need to go out of your way to flash any roms, but it would be cool to hear if you run into something that works well for you in the future.
ColtonDRG said:
I mostly bought the phone for the excellent North American band support, it's one of the few cheaper Chinese phones that do. I'm a fan of Xiaomi's products but band support is typically pretty limited unless you pick up the really high end ones. My biggest gripe with TWRP right now is that USB doesn't work which means you have to transfer all your zips to a microSD card since internal storage is borked thanks to forceencrypt, which we can disable now. I don't mess with the camera too much, typically, but the app itself looks pretty basic. It again reminds me of the usual stuff you would get on MTK phones, there aren't a whole lot of options but the ones that are there look OK-ish? Idk, again, I don't take many pictures. This morning I tried to flash a GSI and my phone just started bootlooping but I didn't follow the procedure at all so I probably missed a step. I will try some more in the future and let you know.
Click to expand...
Click to collapse
Mmm I think I did a bad thing with my F1. I actually tried to flash a ROM via fastboot (PowerShell) and it failed. I was able to successfully restore it, but upon doing so I now have red text in the upper right of the screen. Everything else seems to be fine, though! I even followed a tutorial to restore IMEIs 1+2 and MEID.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: Actually solved now. Bencebacsi on the UMIDIGI forums posted a special version of the SN Writer tool that addresses this.
https://1drv.ms/f/s!AsqLR2yZd3fMiO9GKQIRNhiplqVcNA
I not only got root, but customized it to look the way I want. I also experimented in removing Umidigi's Quickstep system app; I succeeded. Initially, it kept bringing up a prompt indicating an instability, but after a reboot it hasn't appeared again. A side effect of this is that my Recent Apps view is now stacked vertically with the pseudo 3D look like it used to be in Android; apps are dismissed by swiping to the left or right.
I'm only sad that I can't adjust the display size.
Veiran said:
https://1drv.ms/f/s!AsqLR2yZd3fMiO9GKQIRNhiplqVcNA
I not only got root, but customized it to look the way I want. I also experimented in removing Umidigi's Quickstep system app; I succeeded. Initially, it kept bringing up a prompt indicating an instability, but after a reboot it hasn't appeared again. A side effect of this is that my Recent Apps view is now stacked vertically with the pseudo 3D look like it used to be in Android; apps are dismissed by swiping to the left or right.
I'm only sad that I can't adjust the display size.
Click to expand...
Click to collapse
How did you get substratum working? Mine is broken...
mrram said:
How did you get substratum working? Mine is broken...
Click to expand...
Click to collapse
If you have it loaded and granted SU, it's just a matter of downloading a good theme and applying it in the correct fashion.
Starting off with Building and Updating. Select the right apps/services in the Themes tab to enable it for; some are going to be incompatible and you'll receive an error if you try to do so. Once you've got the proper ones selected, there's that button on the bottom right which opens four options. Press the Build & Update one. If everything goes well, it won't return errors.
Next, you'll restart your phone and reopen Substratum. Go to the Manager tab, select the apps/services that should show up here, then go to the bottom-right button and press Enable selected. The screen should blink as substratum enables it.
I have the umi one pro it has booted every P ,Q gsi ever made
bzo22 said:
I have the umi one pro it has booted every P ,Q gsi ever made
Click to expand...
Click to collapse
Any major bugs? Did NFC worked well?
I have a Umidigi one pro too and I can't root, and the notch in landscape on cutout. But the big problem is the root. All the other things go good with a minor bugs. I'm refer to pie.
SnapTheRipper said:
Any major bugs? Did NFC worked well?
Click to expand...
Click to collapse
NFC doesn't work in any build I've flashed
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
Botandroid said:
I have a Umidigi one pro too and I can't root, and the notch in landscape on cutout. But the big problem is the root. All the other things go good with a minor bugs. I'm refer to pie.
Click to expand...
Click to collapse
You should flashed asop v112 gsi it come with gapps and root
bzo22 said:
NFC doesn't work in any build I've flashed
Click to expand...
Click to collapse
Maybe on F1 it's different? I'm using it btw, not the One Pro!
Botandroid said:
I have a Umidigi one pro too and I can't root, and the notch in landscape on cutout. But the big problem is the root. All the other things go good with a minor bugs. I'm refer to pie.
Click to expand...
Click to collapse
Use Magisk 17.1/17.2 it's the best for pie roms
Btw can we get miui/flymeOs/colorOs rom on our device?? I'm using Umi one pro too and I love those roms than aosp roms
Botandroid said:
I have a Umidigi one pro too and I can't root, and the notch in landscape on cutout. ...
Click to expand...
Click to collapse
I flashed phhusson v204 (Android 10) on the One Pro. Is there any chance to get the wide notch considered ? Would the Android9 fix work ?
Related
After nearly three years with my trusty Sony Xperia Z5 Compact, I feel it's time to move on. Got my eyes on this phone since like forever and now that OP6 is releasing I'm hoping for some nice price drops. Anyway, I've read some threads on getting started modding the phone, but I still have a few questions.
With my phone I'm used to having one (usable) ROM, recovery and kernel combo. However, OP5t seems to have quite a few. Which ones are recommended? Do I need to patch the kernel to be able to boot with a modded system partition and to modify it while Android is running? (dm-verity and Sony RIC on my Z5C, respectively.)
Which is the go-to Windows app for flashing ROMs? (Like Flashtool for Sony?)
Do I have to back up a partition so that the camera keeps working and to still be able to play DRM-protected content after bootloader unlock? Which partition do I need to restore to completely lock the bootloader in case I change my mind (and need warranty again)? (So it shows "locked" instead of "relocked".) (On Sony I had to do these with the TA partition.)
Thanks a lot for reading through, I know I wrote a rather huge wall of text.
QWERTYsystems said:
After nearly three years with my trusty Sony Xperia Z5 Compact, I feel it's time to move on. Got my eyes on this phone since like forever and now that OP6 is releasing I'm hoping for some nice price drops. Anyway, I've read some threads on getting started modding the phone, but I still have a few questions.
With my phone I'm used to having one (usable) ROM, recovery and kernel combo. However, OP5t seems to have quite a few. Which ones are recommended? Do I need to patch the kernel to be able to boot with a modded system partition and to modify it while Android is running? (dm-verity and Sony RIC on my Z5C, respectively.)
Which is the go-to Windows app for flashing ROMs? (Like Flashtool for Sony?)
Do I have to back up a partition so that the camera keeps working and to still be able to play DRM-protected content after bootloader unlock? Which partition do I need to restore to completely lock the bootloader in case I change my mind (and need warranty again)? (So it shows "locked" instead of "relocked".) (On Sony I had to do these with the TA partition.)
Thanks a lot for reading through, I know I wrote a rather huge wall of text.
Click to expand...
Click to collapse
You're entering into Oneplus country, options rule the roost. You are going to have to read about all the roms and kernals and make a decision on what best meets your needs.
I wouldn't start there though, OOS is pretty good in it's own right so the smart money is on taking it for a spin before you move on to the roms. Many who do will stay there and many of those who leave for the roms come back to it. It really is that solid. To that end I would start by either simply updating the phone to the latest stock and rooting/recovery or go to the open beta with rooting/recovery. The latter have been by and large very stable as a whole so you are usually safe using them in daily driver duties. In either case useful upgrades to stock android that came on the phone along with some tuning via magisk will get a lot of users where they want to go with stock reliability and functionality.
To install you're going to use fastboot so you'll need to set that up, there are several tutorials available if you're unfamiliar with it. Some people just don't want to take the time to get fastboot 101 capable, if you're of that mind you can use several tools which are available in the development section.
You didn't ask but I'm going to throw something out there for your consideration. The 6 is going to be here soon, I get the impression you hang onto your phones a long time making it perhaps a better choice. You'll wait a bit more than a month but gain a half a year in "newness" to start that long journey.
QWERTYsystems said:
After nearly three years with my trusty Sony Xperia Z5 Compact, I feel it's time to move on. Got my eyes on this phone since like forever and now that OP6 is releasing I'm hoping for some nice price drops. Anyway, I've read some threads on getting started modding the phone, but I still have a few questions.
With my phone I'm used to having one (usable) ROM, recovery and kernel combo. However, OP5t seems to have quite a few. Which ones are recommended? Do I need to patch the kernel to be able to boot with a modded system partition and to modify it while Android is running? (dm-verity and Sony RIC on my Z5C, respectively.)
Which is the go-to Windows app for flashing ROMs? (Like Flashtool for Sony?)
Do I have to back up a partition so that the camera keeps working and to still be able to play DRM-protected content after bootloader unlock? Which partition do I need to restore to completely lock the bootloader in case I change my mind (and need warranty again)? (So it shows "locked" instead of "relocked".) (On Sony I had to do these with the TA partition.)
Thanks a lot for reading through, I know I wrote a huge wall of text.
Click to expand...
Click to collapse
Came from the Xperia Z2 after about 4 years and just recently bought the OP5T.
AFAIK, there's no Flashtool like application for OnePlus devices so you just have to rely on TWRP and there's no such thing as that stupid TA-Partition on the OP5T (or any OnePlus device). You won't lose anything when you unlock your OnePlus device, not even your warranty.
I don't have a recommended custom kernel or rom since I'm very pleased with OxygenOS but the main reason why I'm not switching to a custom ROM is that of Portrait Mode and Face Unlock which aren't available on custom ROMs.
There is Skipsoft and another, the name escapes me but it's there in the development section. Face unlock (Google) and portrait are available depending on the rom but are problematic on most. It is a good point because the google face unlock is not as good as the OP implementation. There are also the nav gestures which most seem to like and I'm among them.
Thanks everyone! Already learned so much! (But I still have some more.) You said OOS is stable (I heard it has some RAM management issues), should I go for the open beta? Do the new features outweigh the bugs? How is Magisk and themeing on OOS (does the former have bugs/random reboots, is latter even possible (Andromeda on Oreo, maybe))? Is there a way I could preserve my data between ROMs? Are there some must have apps/mods I should totally try out? (such as stereo sound mod and Google Camera) Speaking of, is there a recommended Google Camera port for this phone? And lastly, how is the audio quality?
EDIT: Oh and can this phone be easily bricked? I remember no matter what I did with my Z5C I could always reflash it in flashmode.
OOS is stable as can be, even the beta is pretty darn stable, more so than some stable releases. Realistically if the beta isn't offering something you want there is no reason not to go with the official release. You can read about the beta and it's various changes over on that thread.
The only issue either OOS or it's beta in terms of RAM management is that it makes engineers over at Samsung envious, this wont be a problem for most of us.
I'm not a theme guy of I've nothing to offer there. Magisk has been fully functional and has worked without a hitch in my use. As with any device the more modules you load the more you increase your odds of having a conflict in much the same way as you run into with exposed. I'm using the stereo mod, modded youtube, volume steps, and Sony framework with their player. I've had Viper on and it worked without problems but I've since broke down and purchased high(ish) end headphones and don't use it now. You'll have to try your faves and see how it goes but if their mainstream and you don't go overboard with the modules I'd expect them to work.
I use a combination of Ti and nandroids and do a clean flash with every new rom, normally I'll backup and then just dirty flash when going to the next iteration of the same rom. The phone is difficult to brick as long as you follow instructions and pay attention to what your doing, That would apply to almost any modern android phone though, they aren't easy to brick and typically even when you think you've bricked it you haven't, you just don't now how to get out of it. As good fortune would have it a lot of people here have already stubbed their toe on almost any problem you can have and between them and the guru's you will seldom be left with an actual honest to God brick. Pay attention and you shouldn't have to encounter a day of "oh crap" while you wait for others to help you.
I'd rate the audio on speaker as just OK, the in-call quality up at the ear has enough volume and is clear but not special. That puts it right about the same place as I rate most flagship phones.
For now don't overthink all this stuff, the 5T is an excellent value as most will say but more it's in many respects a better day to day phone than my Note 8 was which I've since given to one of my kids. You don't have to make excuses for this phone, outside of a camera which is behind the flagship curve it's solid.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have only woken up and my battery drained like crazy. Somehow, 9GAG is the one which drained the most, I don't really care about that, I will uninstall it later if needed. The point here is that the Carrier services, Android system, Google Play services, Google Play store and Cell standby have really high usages! I have just done a factory reset yesterday and things have seem to get only worse. I used to have 500-700 mAh usage for the android system and that used to be about it. Right now, just over night, I have something almost twice as consuming! If I were to continue the day without having the need to recharge right now, everything would have been around 2000-3000 mAh just for the "system/needed apps" in order for the device to run. I do not find this thing normal. Can anyone please help me?
Mobile data drains battery like crazy...
There's factors that can affect the endurance of your phone's battery. These factors may be caused by a malfunction in your phone, or there's simply a global issue that may be affecting the devices in your area.
LTE does use more battery than Wi-Fi, yes. But not that lot, if everything was stable. But, you know, mobile networks are not stable, and sometimes it can struggle with the signal.
If yesterday, your phone used to last the whole day just fine, and the problem suddenly appeared, it may suggest there's an event affecting it.
Try using your phone on Wi-Fi for an hour, and compare the consumption with LTE for the same length. I suggest turning on aeroplane mode when testing the Wi-Fi.
Carrier Services should not be using that large amount of battery. The main purpose of this app is to help carriers communicate with your phone. To enable their exclusive features and so on.
I can't think of 9GAG more than Reddit, social media apps usually don't drain that much battery (TikTok is an exception). Maybe you'll wake up the next day with your phone resurrected.
ImTheRealMarco said:
View attachment 5423459
I have only woken up and my battery drained like crazy. Somehow, 9GAG is the one which drained the most, I don't really care about that, I will uninstall it later if needed. The point here is that the Carrier services, Android system, Google Play services, Google Play store and Cell standby have really high usages! I have just done a factory reset yesterday and things have seem to get only worse. I used to have 500-700 mAh usage for the android system and that used to be about it. Right now, just over night, I have something almost twice as consuming! If I were to continue the day without having the need to recharge right now, everything would have been around 2000-3000 mAh just for the "system/needed apps" in order for the device to run. I do not find this thing normal. Can anyone please help me?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...xperience-official-aosp.4196041/post-85702201
https://forum.xda-developers.com/t/...xperience-official-aosp.4196041/post-85586743
Although your signature says this: 'This was sent from my Huawei P20 Lite (nova 3e) ANE-LX1 through XDA Labs mobile app."
Are you posting in the correct forum/thread?
Compass.
Compass Linux said:
https://forum.xda-developers.com/t/...xperience-official-aosp.4196041/post-85702201
https://forum.xda-developers.com/t/...xperience-official-aosp.4196041/post-85586743
Although your signature says this: 'This was sent from my Huawei P20 Lite (nova 3e) ANE-LX1 through XDA Labs mobile app."
Are you posting in the correct forum/thread?
Compass.
Click to expand...
Click to collapse
Yeah.... Sorry about that, haven't used this forum in a long time and I didn't even remember that I have a signature xD. Now I do have a Xiaomi Redmi Note 8 Pro, global version.
parkourz said:
Mobile data drains battery like crazy...
Click to expand...
Click to collapse
Yeah.... I wouldn't expect it to get over 1000 mAh just from the Google services... More like 100-300..
parkourz said:
Mobile data drains battery like crazy...
Click to expand...
Click to collapse
Also, isn't that getting "counted" in the cell standby thing?
Mohamedkam000 said:
There's factors that can affect the endurance of your phone's battery. These factors may be caused by a malfunction in your phone, or there's simply a global issue that may be affecting the devices in your area.
LTE does use more battery than Wi-Fi, yes. But not that lot, if everything was stable. But, you know, mobile networks are not stable, and sometimes it can struggle with the signal.
If yesterday, your phone used to last the whole day just fine, and the problem suddenly appeared, it may suggest there's an event affecting it.
Try using your phone on Wi-Fi for an hour, and compare the consumption with LTE for the same length. I suggest turning on aeroplane mode when testing the Wi-Fi.
Carrier Services should not be using that large amount of battery. The main purpose of this app is to help carriers communicate with your phone. To enable their exclusive features and so on.
I can't think of 9GAG more than Reddit, social media apps usually don't drain that much battery (TikTok is an exception). Maybe you'll wake up the next day with your phone resurrected.
Click to expand...
Click to collapse
I don't know what you mean in the last part with the resurrection but yeah, I should try doing a test and see if android system and the others calm down if I'm only on Wi-Fi. Also it's been here for a few days already and it's annoying as hell. I have a friend with the same model and he's kinda got the same problem but not that big. He only got like half of what I have. He does have a bug where the gallery app uses 800-1000 mAh if it won't force close it, but that's another thing since I do not face any issues like that.
Compass Linux said:
https://forum.xda-developers.com/t/...xperience-official-aosp.4196041/post-85702201
https://forum.xda-developers.com/t/...xperience-official-aosp.4196041/post-85586743
Although your signature says this: 'This was sent from my Huawei P20 Lite (nova 3e) ANE-LX1 through XDA Labs mobile app."
Are you posting in the correct forum/thread?
Compass.
Click to expand...
Click to collapse
I don't really understand what you are trying to say but if are trying to tell me that it's because of the 12.5 update, well it kinda isn't. My battery halved when I installed MIUI 12. I have debloated my phone and now the results are as following: *also 1:48 hours with 22% battery drain which is kinda impressive because if things go like this it low-key means that I can totally go for approximately 8 hours now. My phone was debloated before too but it didn't do much. Right now, I've mostly been on Wi-Fi because in the area I had to go, there isn't really any 4G/signal. It's either thanks to not using mobile data, which I did use for like 1/4 of the usage time until now, either to debloating it.*
ImTheRealMarco said:
Yeah.... Sorry about that, haven't used this forum in a long time and I didn't even remember that I have a signature xD. Now I do have a Xiaomi Redmi Note 8 Pro, global version.
Click to expand...
Click to collapse
Welcome to the club!
ImTheRealMarco said:
I don't really understand what you are trying to say but if are trying to tell me that it's because of the 12.5 update, well it kinda isn't. My battery halved when I installed MIUI 12. I have debloated my phone and now the results are as following: *also 1:48 hours with 22% battery drain which is kinda impressive because if things go like this it low-key means that I can totally go for approximately 8 hours now. My phone was debloated before too but it didn't do much. Right now, I've mostly been on Wi-Fi because in the area I had to go, there isn't really any 4G/signal. It's either thanks to not using mobile data, which I did use for like 1/4 of the usage time until now, either to debloating it.*
Click to expand...
Click to collapse
MIUI 12.5.x for our device came with many problems. Battery drain being one of them.
I'm assuming that you're using Stock MIUI 12.5.x. If that's your case, you have to wait for an update that fixes the battery drain.
https://github.com/PixelExperience/android-issues/issues/388 (the ROM maintainer explains better the issue)
Compass.
Compass Linux said:
Welcome to the club!
MIUI 12.5.x for our device came with many problems. Device drain being one of them.
I'm assuming that you're using Stock MIUI 12.5.x. If that's your case, you have to wait for an update that fixes the battery drain.
https://github.com/PixelExperience/android-issues/issues/388 (the ROM maintainer explains better the issue)
Compass.
Click to expand...
Click to collapse
I already have the phone for a year and a half but thanks . Also.. are we sure that we are going to get a fix in the next update relating to this battery drain issue?.. Or is it something that we EXPECT to happen?... Also yes, I'm using the stock debloated version! I could rollback to an older version but will that actually fix something? I still had the issue even on MIUI 12, not 12.5. MIUI 11 was the only one which had no problems .
Ah yes, the android system has kicked in again with a spectacular 245 mAh used! Will update in a few hours.
EDIT: In AccuBattery it's only showing as this: *look at the attached photo*. Are the MIUI battery stats wrong? Does AccuBattery not record the actual Android System usage? Does it put it in another category, like for example the app I was using at that time?
ImTheRealMarco said:
I already have the phone for a year and a half but thanks . Also.. are we sure that we are going to get a fix in the next update relating to this battery drain issue?.. Or is it something that we EXPECT to happen?... Also yes, I'm using the stock debloated version! I could rollback to an older version but will that actually fix something? I still had the issue even on MIUI 12, not 12.5. MIUI 11 was the only one which had no problems .
Click to expand...
Click to collapse
Welcome to the sh!t where Xiaomi breaks it's budget phones with every update to force it's clients to buy new budget phone every year or pay 3xprice for higher-shelf device... Oh! And welcome to the Mediatek sh!t which deters developers, too!
It's 2 times when I bought Xiaomeme phone: first and last...
parkourz said:
Welcome to the sh!t where Xiaomi breaks it's budget phones with every update to force it's clients to buy new budget phone every year or pay 3xprice for higher-shelf device... Oh! And welcome to the Mediatek sh!t which deters developers, too!
It's 2 times when I bought Xiaomeme phone: first and last...
Click to expand...
Click to collapse
Alright BUT if I buy a 400-500$ phone it's gonna "break" in 2 and a half years instead of 1 and a half years huh? Any other option besides Xiaomi?
ImTheRealMarco said:
I already have the phone for a year and a half but thanks . Also.. are we sure that we are going to get a fix in the next update relating to this battery drain issue?.. Or is it something that we EXPECT to happen?... Also yes, I'm using the stock debloated version! I could rollback to an older version but will that actually fix something? I still had the issue even on MIUI 12, not 12.5. MIUI 11 was the only one which had no problems .
Click to expand...
Click to collapse
Users: We expect the bugs to be fixed with future updates.
Xiaomi: We expect not to fix bugs especially if they can push the sales of other phones.
Jokes aside, keep your fingers crossed that this battery drain issue is fixed by Xiaomi soon. Especially because our device will be EOL November/2021.
As for MIUI 12.0.x also having a battery drain problem I don't know. I started having this issue with PE+ when it started using MIUI 12.5.x as its base.
Compass.
Compass Linux said:
Users: We expect the bugs to be fixed with future updates.
Xiaomi: We expect not to fix bugs especially if they can push the sales of other phones.
Jokes aside, keep your fingers crossed that this battery drain issue is fixed by Xiaomi soon. Especially because our device will be EOL November/2021.
As for MIUI 12.0.x also having a battery drain problem I don't know. I started having this issue with PE+ when it started using MIUI 12.5.x as its base.
Compass.
Click to expand...
Click to collapse
Also, since you seem pretty knowledgeable about custom ROMs, if you don't mind me asking, is using a custom ROM still safe? Like for inputting banking info etc etc.? And if it is, what are the downsides? And is there a way to break my phone like for real/forever? And what ROM would you recommend? Also, do you know if unlocking the bootloader voids my warranty? *It's not like I got much more of it left* And by the way, what's your address experience on using a custom ROM? How's the battery life? Anddddd sorry for the all questions, its fine if you don't wanna take the time to answer xD.
ImTheRealMarco said:
Also, since you seem pretty knowledgeable about custom ROMs, if you don't mind me asking, is using a custom ROM still safe? Like for inputting banking info etc etc.? And if it is, what are the downsides? And is there a way to break my phone like for real/forever? And what ROM would you recommend? Also, do you know if unlocking the bootloader voids my warranty? *It's not like I got much more of it left* And by the way, what's your address experience on using a custom ROM? How's the battery life? Anddddd sorry for the all questions, its fine if you don't wanna take the time to answer xD.
Click to expand...
Click to collapse
Is using a Custom ROM safe (for banking, PayPal etc)? I cannot give a proper answer for this. Custom ROMs are usually a mix of open source code (from the Custom ROM developer(s)) and binary blobs from the manufacturer (I might be missing something here). You could build a Custom ROM from the source code and add the binary blobs yourself to be sure, but that's quite a lot of work. I chose PE+ for now which has a decent user base. I do use banking applications with it (even with root). Now let's suppose you work for the CIA or the NSA. I wouldn't recommend a Custom ROM for you, and certainly would have reservations for stock MIUI too. It depends on your mileage;
Downsides? I'll talk specifically about the RN8Pro. In the past it was easier to hard brick the device, which meant that you needed to contact an authorized service center to fix it (or go online but I won't detail it here). So depending on the mistake you do when you flash a Custom ROM yes, you can hard brick it (read #3 to unbrick). Another thing that's possible to damage is the IMEI. It's always advisable to make nandroid backups of the relevant IMEI partitions in case you ever need them (restoring the IMEI partitions should only be done if absolutely needed and might still fail for whatever reason);
Breaking your phone. There is now an unbrick method that fixes a hard brick without the need for a service center. You can do it yourself too.
;
Recommended Custom ROM. My suggestion is that you stay as close to Stock ROM as possible, so try
. This modded Stock MIUI 12.5.x should have an update soon;
Warranty for a unlocked bootloader. Yes, you'll void your warranty but you can also re-lock your bootloader if necessary. Unlocking your bootloader will format your data (you'll lose apps + data in the process). I don't know if re-locking does the same, but I guess it does;
My experience on using a Custom ROM. I've only used PE+ as my daily driver. For the good and the bad (there's probably other stuff I didn't mention) read https://forum.xda-developers.com/t/...xperience-official-aosp.4196041/post-85697555. That's my resumed review of the latest release at that time;
Time. I don't mind taking my time to answer your questions (and being corrected too).
If you do decide to try a Custom ROM there are a bunch of channels in Telegram. Most developers have migrated to there and don't usually reply to queries here at XDA. There's a lot more Custom ROMs available on TeleGram than here. You'll have to search for those.
This YouTube channel should have answers for most of your Custom ROM flashing questions:
https://www.youtube.com/c/AlltricksCoIn/videos
Compass.
Compass Linux said:
Is using a Custom ROM safe (for banking, PayPal etc)? I cannot give a proper answer for this. Custom ROMs are usually a mix of open source code (from the Custom ROM developer(s)) and binary blobs from the manufacturer (I might be missing something here). You could build a Custom ROM from the source code and add the binary blobs yourself to be sure, but that's quite a lot of work. I chose PE+ for now which has a decent user base. I do use banking applications with it (even with root). Now let's suppose you work for the CIA or the NSA. I wouldn't recommend a Custom ROM for you, and certainly would have reservations for stock MIUI too. It depends on your mileage;
Downsides? I'll talk specifically about the RN8Pro. In the past it was easier to hard brick the device, which meant that you needed to contact an authorized service center to fix it (or go online but I won't detail it here). So depending on the mistake you do when you flash a Custom ROM yes, you can hard brick it (read #3 to unbrick). Another thing that's possible to damage is the IMEI. It's always advisable to make nandroid backups of the relevant IMEI partitions in case you ever need them (restoring the IMEI partitions should only be done if absolutely needed and might still fail for whatever reason);
Breaking your phone. There is now an unbrick method that fixes a hard brick without the need for a service center. You can do it yourself too.
;
Recommended Custom ROM. My suggestion is that you stay as close to Stock ROM as possible, so try
. This modded Stock MIUI 12.5.x should have an update soon;
Warranty for a unlocked bootloader. Yes, you'll void your warranty but you can also re-lock your bootloader if necessary. Unlocking your bootloader will format your data (you'll lose apps + data in the process). I don't know if re-locking does the same, but I guess it does;
My experience on using a Custom ROM. I've only used PE+ as my daily driver. For the good and the bad (there's probably other stuff I didn't mention) read https://forum.xda-developers.com/t/...xperience-official-aosp.4196041/post-85697555. That's my resumed review of the latest release at that time;
Time. I don't mind taking my time to answer your questions (and being corrected too).
If you do decide to try a Custom ROM there are a bunch of channels in Telegram. Most developers have migrated to there and don't usually reply to queries here at XDA. There's a lot more Custom ROMs available on TeleGram than here.
Telegram channel/group links:
t.me/RedmiNote8ProOfficial (for queries; check /rules and /notes before asking)
t.me/RedmiNote8ProUpdates (for releases)
This YouTube channel should have answers for most of your Custom ROM flashing questions:
https://www.youtube.com/c/AlltricksCoIn/videos
Compass.
Click to expand...
Click to collapse
Thanks a lot man, I wonder if re-locking the bootloader will "regain" my warranty like if I re-lock it and send it to service, will they say something? Also I have heard that you are going to brick your phone if you re-lock the bootloader while you have a custom ROM or something like that, which I don't know anything about. So that may be fake. Thanks once again for all the explanations!! By the way, do you know what the average Android System usage should be? Or for example, what's your daily usage?
ImTheRealMarco said:
Thanks a lot man, I wonder if re-locking the bootloader will "regain" my warranty like if I re-lock it and send it to service, will they say something? Also I have heard that you are going to brick your phone if you re-lock the bootloader while you have a custom ROM or something like that, which I don't know anything about. So that may be fake. Thanks once again for all the explanations!! By the way, do you know what the average Android System usage should be? Or for example, what's your daily usage?
Click to expand...
Click to collapse
Re-locking your bootloader is the same as buying it new and locked. Xiaomi phones don't act like Samsung's Knox, which goes to 0x1 once the bootloader is unlocked and cannot be set back to 0x0.
To re-lock your bootloader you basically flash a Stock MIUI and enable the re-lock option (when using SP Flash Tool if I'm not mistaken). I've never heard of re-locking a bootloader with a Custom ROM installed (I don't think it's possible).
I'll attach screenshots with my Android System usage, but since I've just charged and turned on my phone I don't think it'll help you.
I don't know what the average usage for the Android System should be. It should vary with the phone's use.
Compass.
Compass Linux said:
Re-locking your bootloader is the same as buying it new and locked. Xiaomi phones don't act like Samsung's Knox, which goes to 0x1 once the bootloader is unlocked and cannot be set back to 0x0.
To re-lock your bootloader you basically flash a Stock MIUI and enable the re-lock option (when using SP Flash Tool if I'm not mistaken). I've never heard of re-locking a bootloader with a Custom ROM installed (I don't think it's possible).
I'll attach screenshots with my Android System usage, but since I've just charged and turned on my phone I don't think it'll help you.
I don't know what the average usage for the Android System should be. It should vary with the phone's use.
Compass.
Click to expand...
Click to collapse
Yeah.... Besides that you just charged it, I cannot see the mAh used by it but it seems pretty high but mime's almost double the %. I wonder if the Kernel (Android OS) gets into the Android System tab for me, unlike for you. Also, do you know if AccuBattery is accurate? Because if it is, then the Android System isn't using almost anything. I did also have 4 hours of SoT with 50% so the battery life is about as good as it can be, I think? By the way, I have heard that disabling MIUI optimizations could help. Do you know anything about that?. Thanks a lot in advance, once again!
Hi All,
Been a while on here - please be gentle!
I have spent the last 6 hours looking into updating my firmware from Android 10!
I have done this on previous phones, but my current phone is proving a little more difficult. For the life of me, I cannot find the correct ROM to flash. Whenever I come to something I think I have found I seem to have another issue.
I've tried using various tools (Bitfrost) but got errors.
I'm in the UK, and as far as I can tell, my phone is “XAA”, “USA unbranded (default)”. I'm not bothered about changing the region code (unless it can be done easily).
Details::
SW ver.: SAOMC_SM-N975U_OYN_XAA_PP_0001
XAA/XAA/ATT
I would really appreciate some help from you guys who are way more informed and cleverer than me!
Thanks guys and gals!
Simon
EDIT: I have found a bit more informstion - I think I would be ok using SM-N975U1 - is this correct?
That's the umlocked Snapdragon variant...
I have two N10+'s; N975U/Pie, N975U1/Android 10. I would stay on Android 10 unless you want cpu cycle sucking scoped storage in all its glory.
Personally I prefer Pie to 10, better functionality and usability. With 11 you lose even more and 12 is fubar... in my opinion.
The best way to trash a stock N10+ is to mess with its firmware.
Rule #1 if a OS is fulfilling its mission, let it be!
Upgrades/updates can and do break things.
blackhawk said:
That's the umlocked Snapdragon variant...
I have two N10+'s; N975U/Pie, N975U1/Android 10. I would stay on Android 10 unless you want cpu cycle sucking scoped storage in all its glory.
Personally I prefer Pie to 10, better functionality and usability. With 11 you lose even more and 12 is fubar... in my opinion.
The best way to trash a stock N10+ is to mess with its firmware.
Rule #1 if a OS is fulfilling its mission, let it be!
Upgrades/updates can and do break things.
Click to expand...
Click to collapse
Thanks for that info ... I actually have no beef with A10 other than one issue which I thought maybe a firmware issue.
My NFC works (I can transfer files between phones) however, I cannot use Google Pay, or Samsung Pay. I have read somewhere that this was a firmware issue, hence my desire to update.
I have tried literally everything to get it working (cleared cache, re-booted). NFC Tools confirms it works, but it just does nothing at the checkout.
If I can fix this issue, I'll be happier!
Ratzz2 said:
Thanks for that info ... I actually have no beef with A10 other than one issue which I thought maybe a firmware issue.
My NFC works (I can transfer files between phones) however, I cannot use Google Pay, or Samsung Pay. I have read somewhere that this was a firmware issue, hence my desire to update.
I have tried literally everything to get it working (cleared cache, re-booted). NFC Tools confirms it works, but it just does nothing at the checkout.
If I can fix this issue, I'll be happier!
Click to expand...
Click to collapse
You're welcome. It may be doing that because big sister Google thinks you need to upgrade to be secure. May have to do with the region you're using it in. I don't know. I never use those features and don't want them on the phone. Don't want anything to back door in using that route.
Depends how hell bent you are on having those features. You could easily lose more than you gain by upgrading, worse it may not resolve the issue. The N10+ is a valuable and reliable work horse that will run for years... just as it is. If it's running well otherwise I would try to find the root cause of this issue or simply use other workarounds rather than the shotgun approach.
Yeah, I was wondering about being in the UK with a phone registered in the US. But NFC doesn't read my credit card either. Would have thought that would be an option.
I'm not necessarily a huge NFC user, but the other day I forgot my wallet at the petrol station after filling my car. If I'd have had my NFC working, I'd have been able to fire it up and avoid the embarrassment!
Anyway, thanks for your help!
Be glad you have the Snapdragon variant. They are very reliable and run well stock when optimized. If you do upgrade to 11 a rollback to 10 isn't possible if you upgrade the boot loader.
There's always at least a small risk when flashing firmware which can trash the device. The only time I would flash a N10+ is if the rom was corrupted which barring a hardware failure is a very rare SUE, single upset event.
I never tried mine to see if Pay works nor have I ever set a screen lock. The fingerprint scanner could be dead for all I know.
The flip side to that is never being locked out* of my own device, no data lose, and double tap on/off. The device is glued to me as physical security is the only real security. I realize this may seem extreme to some, but it works well in the real world.
*a SEU or partial hardware can lock you out of your device. Had no lock been set, no lockout would have occurred. Got locked out of a PC bios like that. The password -was- correct
That caused a mountain of trouble...
Thank you my friend. Wise words indeed and duly noted...
Like the title says will our devices be able to get this too?
I hope so but I'm afraid not.
There's been a dev tweaked ver. for my old Pixel 4a (A/B) for 10, 11 & 12 but req. certain kernels w/lmza ramdisk (blu-spark and fsoc tribute). Lost track cuz I traded my 4a in for $300 off P6a n free G Budz. Was apparently working good enuff he took it to git hub Someone needs to send him a aosp stock 13 phone...he got chops!!
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com
J0nhy said:
Like the title says will our devices be able to get this too?
Click to expand...
Click to collapse
Why? This is a pixel, it has fastboot.
Really need TWRP for P6P & P7P
96carboard said:
Why? This is a pixel, it has fastboot.
Click to expand...
Click to collapse
Twrp is way faster for anything, installing a custom rom, magisk, etc... Plus you don't need a pc every time
J0nhy said:
Twrp is way faster for anything, installing a custom rom, magisk, etc... Plus you don't need a pc every time
Click to expand...
Click to collapse
Its not faster, its impossibly slow and does nothing of any use.
96carboard said:
Its not faster, its impossibly slow and does nothing of any use.
Click to expand...
Click to collapse
Brick city too
Gytole said:
Brick city too
Click to expand...
Click to collapse
How's twrp any more dangerous then flashing a rom with fastboot?
Twilightsparklez said:
How's twrp any more dangerous then flashing a rom with fastboot?
Click to expand...
Click to collapse
You're joking right? Fam...if you're out and about and bork with twrp. Or accidentally wipe your phone and internal, it happens....then you'll SOL and if like me on vacation a few years back and my girlfriend booted into twrp and wiped my phone trying to get back into android, DON'T ASK ME HOW it SUCKED.
BUT...if you bork with fastboot you're already attached to the PC.
Xc4
Gytole said:
You're joking right? Fam...if you're out and about and bork with twrp. Or accidentally wipe your phone and internal, it happens....then you'll SOL and if like me on vacation a few years back and my girlfriend booted into twrp and wiped my phone trying to get back into android, DON'T ASK ME HOW it SUCKED.
BUT...if you bork with fastboot you're already attached to the PC.
Click to expand...
Click to collapse
So? If you wipe internal storage while out you're a moron who shouldn't be rooting anyway. Don't let anyone else use a rooted phone even if they're someone close. I'm sorry for your situation, but next tike maybe a
Gytole said:
You're joking right? Fam...if you're out and about and bork with twrp. Or accidentally wipe your phone and internal, it happens....then you'll SOL and if like me on vacation a few years back and my girlfriend booted into twrp and wiped my phone trying to get back into android, DON'T ASK ME HOW it SUCKED.
BUT...if you bork with fastboot you're already attached to the PC.
Click to expand...
Click to collapse
I guess that's more a reminder to do a full system backup then a reason not to use twrp. Doesn't it have a nand backup thing?
Nandroid backups like an android standard goto. Then google switched to their 'seamless' aka dynamic updates using A/B partitions aka 'slots' and that started slamin' the door on any hopes of a decent custom recovery option...esp for something like what acronis does for PCs...to be able to take an exact 'snap shot' image of the system at a given moment an send it to an SD, to ur pc via lan wifi connect or to the cloud by ur wifi or lte/data link! And now with ufs 3.0, even faster! I know he got it mostly running on his P4a (with slot a/b) on 12.1...just with he had axx ro a current stock (aosp) A13 phone...I bet he'd sort it for A13 too!! And I have problems with running Blu-Spark or FSociety Tribute kernels what so ever! Js....and a lil' dreamin too...lol
Maybe nikamura has something to say?
nikamura
Gytole said:
You're joking right? Fam...if you're out and about and bork with twrp. Or accidentally wipe your phone and internal, it happens....then you'll SOL and if like me on vacation a few years back and my girlfriend booted into twrp and wiped my phone trying to get back into android, DON'T ASK ME HOW it SUCKED.
BUT...if you bork with fastboot you're already attached to the PC.
Click to expand...
Click to collapse
how tf you accidentally wipe someones phone through twrp
w_tapper said:
how tf you accidentally wipe someones phone through twrp
Click to expand...
Click to collapse
I'm asking dame ****
Twilightsparklez said:
96carboard said:
Its not faster, its impossibly slow and does nothing of any use.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
By faster i meant not having to waste time connecting your phone yo the PC every time, so it saves us time
Disclaimer: I am responsible for LineageOS on the Pixel 6 and 7 series.
The way Pixels are designed, they can't boot a recovery image with "fastboot boot". In turn, you can't get TWRP, unlike say a OnePlus or Samsung where TWRP is still viable. IMHO still beats OnePlus 10's locked-behind-credentials MSM tools tho.
While I'd love to have TWRP on Pixels, it's simply not an option anymore. Hence why Lineage Recovery is the only option for LOS on Pixel devices, and other Pixel ROMs are flashed via fastboot versus recovery.
neelchauhan said:
Disclaimer: I am responsible for LineageOS on the Pixel 6 and 7 series.
The way Pixels are designed, they can't boot a recovery image with "fastboot boot". In turn, you can't get TWRP, unlike say a OnePlus or Samsung where TWRP is still viable. IMHO still beats OnePlus 10's locked-behind-credentials MSM tools tho.
While I'd love to have TWRP on Pixels, it's simply not an option anymore. Hence why Lineage Recovery is the only option for LOS on Pixel devices, and other Pixel ROMs are flashed via fastboot versus recovery.
Click to expand...
Click to collapse
wait are you working on the real official one? i thought it was npjohnson
Josh.haveman1 said:
What prevents it from booting into a recovery image?
Why are these people talking smack on TWRP? I cannot imagine ****ing around with custom roms without a custom recovery. To be fair, I've only messed with my BLOD Nexus 5X. Is android unmodifiable these days? I have a feeling 90% of the "hardware issues" of pixel 6 are actually purposeful software issues that aren't being fixed so that people buy pixel 7.
I intended on degoogling this phone and keeping it for 6+ years. Pixel used to be for us, for us to modify. If I can't easily modify this phone, I'm just going to throw it in the garbage. I'm not okay with the amount of data this phone collects without my permission. Why is Google half assing their attempt at competing with apple? I expected 2nd gen Tensor to be fully bespoke. Tensor will never compete with apple silicon otherwise. Google is literally a decade behind Apple.
Google just keeps adding processes to their overly complex OS, making it slower, more prone to failure, and more battery intensive, but they don't add features (MANUAL ****ING FOCUS FOR **** SAKE). They just add covert processes that no one even knows about. I'm sick of Google at this point. Maybe I'll go back to my Nexus 5X or fix my Pixel 4XL. They should not have released Pixel 6 in 2021. They should have waited a year and released a working phone. Pixel 7 is plagued with many of the issues of Pixel 6, like overheating, connectivity problems, and the general ****tiness of Android 13.
Click to expand...
Click to collapse
Pixels are just stock Android Galaxy phones at this point. Sick of it.
Josh.haveman1 said:
Pixels are just stock Android Galaxy phones at this point. Sick of it.
Click to expand...
Click to collapse
how exactly does that make them bad?
w_tapper said:
how exactly does that make them bad?
Click to expand...
Click to collapse
Galaxy phones have extremely mid tier hardware, overheat all the time, are difficult to modify, yet cost as much as, or sometimes more than iPhones. Phones with curved glass are also counterintuitive because it simply causes annoying glare and seriously weakens the screen. My 6 Pro is the first phone I've ever cracked, and it only fell out of my pocket. Gorilla Glass Victus is supposed to be really strong, but the curve of the screen completely nullifies this. I'm not the kind of guy to use cases, and this has never caused me a problem with a phone with a flat display. Apple openly talks about why they don't use curved screens, and very few people were excited about the curve on the 6 Pro. I do not understand why they kept it on the 7 Pro. It shows the blatant lack of skill in their engineering teams.
I expected tensor to be custom. Not to just be an off brand snapdragon. Tensor is as stupid as exynos. They should have built a new architecture from the ground up instead of using mediocre off the shelf parts.
Stock android isn't lightweight anymore, it comes with a ton of bloat.
I'm just tired of Android. They keep adding new problems instead of fixing the ones they already have. It's completely senseless. Android has so much potential but Google has absolutely NO IDEA what to do with it. They cannot hire skilled engineers, because the skilled engineers do not support Google's mission. It's only the mediocre people who do.
Josh.haveman1 said:
Galaxy phones have extremely mid tier hardware, overheat all the time, are difficult to modify, yet cost as much as, or sometimes more than iPhones. Phones with curved glass are also counterintuitive because it simply causes annoying glare and seriously weakens the screen. My 6 Pro is the first phone I've ever cracked, and it only fell out of my pocket. Gorilla Glass Victus is supposed to be really strong, but the curve of the screen completely nullifies this. I'm not the kind of guy to use cases, and this has never caused me a problem with a phone with a flat display. Apple openly talks about why they don't use curved screens, and very few people were excited about the curve on the 6 Pro. I do not understand why they kept it on the 7 Pro. It shows the blatant lack of skill in their engineering teams.
I expected tensor to be custom. Not to just be an off brand snapdragon. Tensor is as stupid as exynos. They should have built a new architecture from the ground up instead of using mediocre off the shelf parts.
Stock android isn't lightweight anymore, it comes with a ton of bloat.
I'm just tired of Android. They keep adding new problems instead of fixing the ones they already have. It's completely senseless. Android has so much potential but Google has absolutely NO IDEA what to do with it. They cannot hire skilled engineers, because the skilled engineers do not support Google's mission. It's only the mediocre people who do.
Click to expand...
Click to collapse
you are greatly underestimating how hard it is to make a whole custom chip, and if tensor was truly custom I doubt whether roms would exist for it and in my opinion I would much rather have tensor be based on exynos than be a bad attempt at a custom chip
for Android being bloated you could just use degoogled lineageos or grapheneos
Just updated my Magic4 Pro to Android 13, Magic OS 7.1, Build number: 7.1.0.136 and I cannot switch between apps; the functionality is simply broken.
I've got a video demonstrating it on Twitter...would therefore suggest not upgrading until this is (and potentially other bugs) fixed.
UPDATE:
I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
Was it à regular updates from Honor ?
TotallydubbedHD said:
Just updated my Magic4 Pro to Android 13, Magic OS 7.1, Build number: 7.1.0.136 and I cannot switch between apps; the functionality is simply broken.
I've got a video demonstrating it on Twitter...would therefore suggest not upgrading until this is (and potentially other bugs) fixed.
Click to expand...
Click to collapse
I suggest you to perform a hard reset. I don't meet this issue. It's very strange!!!
marcox92 said:
Was it à regular updates from Honor ?
Click to expand...
Click to collapse
Yes it's a regular and official update.
Curious, didn't receive the update
nico97470 said:
I suggest you to perform a hard reset. I don't meet this issue. It's very strange!!!
Click to expand...
Click to collapse
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
marcox92 said:
Curious, didn't receive the update
Click to expand...
Click to collapse
You should tape in the three points upper in right in the app Honor Club( system update). Trying versions.
TotallydubbedHD said:
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
Click to expand...
Click to collapse
I'm going to perform a hard reset because of draining battery and others bugs. I was before a beta tester. This update, too soon!!! Honor should have waited!!! I'm angry !
nico97470 said:
I'm going to perform a hard reset because of draining battery and others bugs. I was before a beta tester. This update, too soon!!! Honor should have waited!!! I'm angry !
Click to expand...
Click to collapse
Agreed.
Doing a reset will solve it, I have not done it and it works fine, I have been lucky.
TotallydubbedHD said:
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
Click to expand...
Click to collapse
Unfortunately you might just have to do a backup and do it when it comes to android in general not just honor platform updates tend to break things and only way to fix those bugs is to reset simple as that you can complain left and right but that's just how it is happens on ios mac os and Windows as well
wolfaas12345 said:
Unfortunately you might just have to do a backup and do it when it comes to android in general not just honor platform updates tend to break things and only way to fix those bugs is to reset simple as that you can complain left and right but that's just how it is happens on ios mac os and Windows as well
Click to expand...
Click to collapse
I used to flash ROMs and kernels weekly on my SGS1, but I can't ever recall one breaking basing navigation functionalities.
With that said, I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
It was very relieving to find this thread and make my phone usable again. It was horrible experience trying to use the phone without an ability to switch apps.
Ja5ka said:
It was very relieving to find this thread and make my phone usable again. It was horrible experience trying to use the phone without an ability to switch apps.
Click to expand...
Click to collapse
Sorry to hear that but glad I could help!
TotallydubbedHD said:
I used to flash ROMs and kernels weekly on my SGS1, but I can't ever recall one breaking basing navigation functionalities.
With that said, I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
Click to expand...
Click to collapse
"It didn't happen before so it can't happen now" great logic also that was super long time ago lmao back in SGS1 days we only had 1 navigation type so it either fully worked or didn't there were no variables these days we have 2-3 so obvs stuff can break plus don't forget with a clean install there are 0 variables that's why bugs, if they happen, are caught by honor or whoever makes the update with apps and custom settings thrown in there's thousands of variables that can make stuff go haywire
wolfaas12345 said:
"It didn't happen before so it can't happen now" great logic also that was super long time ago lmao back in SGS1 days we only had 1 navigation type so it either fully worked or didn't there were no variables these days we have 2-3 so obvs stuff can break plus don't forget with a clean install there are 0 variables that's why bugs, if they happen, are caught by honor or whoever makes the update with apps and custom settings thrown in there's thousands of variables that can make stuff go haywire
Click to expand...
Click to collapse
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
TotallydubbedHD said:
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
Click to expand...
Click to collapse
No its garbage logic in fact yes its been in dev for 13 years it has also been adding features for 13 years changin things for 13 years for same 13 years its also been supporting over 20k+ devices and working on them bugs are about normal with majority phones we dont see a lot cuz devs squash them before they push the update but variables that i mentioned prevent devs from covering all scenarios so shenanigans happen my problem was not with bug itself my problem is people like you talking crap because they refuse to wipe or expect flawless experience every time nothing is perfect especially software
TotallydubbedHD said:
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
Click to expand...
Click to collapse
I think you are an expert. Do you think it is possible to install Google Services Framework on Magic5pro? I have one but dunno how to do so. Thank you for your sharing.