Related
I got the new phone 15 days ago, thinking it'll be as amazing as Zenfone Max ZC550KL (Great Camera, everlasting battery) but it had super annoying issues, specially the battery draining too fast. Even during deep sleep (screen off for hours) the battery drained from 100% to 70% in like an hour or so, without any SIM/WiFi/Hotspot.
I had to fix this as it was impossible to go outside for a day and not have it switch off on my face when I needed it. None of the power saving settings helped.
So, I unlocked the bootloader following a youtube guide (it was a batch file on windows, not the original app which I found out about 10 mins ago), and flashed TWRP into it. Took a full system backup of all partitions and rooted it by flashing the latest SuperSU Binary. Worked like a charm. Installed CPU Tuner, deleted all triggers and set frequency to manually locked 500 MHz. When I need to play a game or do something which needs performance, I'd just go and manually pull the slider ahead to 2.3 GHz.
The avg. battery drain during deep sleep or screen off for hours, reduced from 1120 mAh to 10 mAh which is HUGE (found out with an app I cant remember). I'm happy with it as now it can last about a day and about 3 days if I'm mostly not using it, with WiFi on all the time. Its just slightly not as butter smooth with the UI as before.
Now, the camera quality is the worst I've ever seen. During dark, the PixelMaster Camera makes things crippling dark and too much purple pixelated noise and grain, pics taken from it look like from my Galaxy Tab 2 which I bought in 2012, and I tried different camera apps and everything I could, no luck. Where, the image taken from almost the same place at the same time, both phones held side by side, my old phone ZC550KL takes a million times clearer picture, brighter, perfectly visible and great looking. I also tried setting the same enhancements and stuff but nothing helped.
Some posts on googling it, suggest to update the system firmwire to improve camera quality but it requires the original recovery mode to be there, where I have TWRP.
I want to update the system as I have nothing to lose, already have 4-5 complete TWRP backups of every state (Original before rooting, rooted once, some modifications later, etc). Just if the phone gets bricked or doesn't boot anymore, that would be the problem.
I've messed around with almost everything I could on my Windows 7 and Windows 10 Desktop over past 6 years, so I have an idea about how things work.
Now, how do I update the system?
I think I could flash an update manually downloaded on my PC using adb and fastboot drivers... If so, how?
Current Software Information:
Current Android Version: Lollipop v5.0
Build Number:
LRX21V.WW-ASUS_Z00A-2.20.40.184_20160504_4658_user_044030427
Available System Update from the inbuilt app:
Last Check: 09/14/2017 12:00 PM (today)
Build Number: WW_2.20.40.198_20160930_8756_user_rel (93.31 MB)
CaptianXLAB said:
I got the new phone 15 days ago, thinking it'll be as amazing as Zenfone Max ZC550KL (Great Camera, everlasting battery) but it had super annoying issues, specially the battery draining too fast. Even during deep sleep (screen off for hours) the battery drained from 100% to 70% in like an hour or so, without any SIM/WiFi/Hotspot.
I had to fix this as it was impossible to go outside for a day and not have it switch off on my face when I needed it. None of the power saving settings helped.
So, I unlocked the bootloader following a youtube guide (it was a batch file on windows, not the original app which I found out about 10 mins ago), and flashed TWRP into it. Took a full system backup of all partitions and rooted it by flashing the latest SuperSU Binary. Worked like a charm. Installed CPU Tuner, deleted all triggers and set frequency to manually locked 500 MHz. When I need to play a game or do something which needs performance, I'd just go and manually pull the slider ahead to 2.3 GHz.
The avg. battery drain during deep sleep or screen off for hours, reduced from 1120 mAh to 10 mAh which is HUGE (found out with an app I cant remember). I'm happy with it as now it can last about a day and about 3 days if I'm mostly not using it, with WiFi on all the time. Its just slightly not as butter smooth with the UI as before.
Now, the camera quality is the worst I've ever seen. During dark, the PixelMaster Camera makes things crippling dark and too much purple pixelated noise and grain, pics taken from it look like from my Galaxy Tab 2 which I bought in 2012, and I tried different camera apps and everything I could, no luck. Where, the image taken from almost the same place at the same time, both phones held side by side, my old phone ZC550KL takes a million times clearer picture, brighter, perfectly visible and great looking. I also tried setting the same enhancements and stuff but nothing helped.
Some posts on googling it, suggest to update the system firmwire to improve camera quality but it requires the original recovery mode to be there, where I have TWRP.
I want to update the system as I have nothing to lose, already have 4-5 complete TWRP backups of every state (Original before rooting, rooted once, some modifications later, etc). Just if the phone gets bricked or doesn't boot anymore, that would be the problem.
I've messed around with almost everything I could on my Windows 7 and Windows 10 Desktop over past 6 years, so I have an idea about how things work.
Now, how do I update the system?
I think I could flash an update manually downloaded on my PC using adb and fastboot drivers... If so, how?
Current Software Information:
Current Android Version: Lollipop v5.0
Build Number:
LRX21V.WW-ASUS_Z00A-2.20.40.184_20160504_4658_user_044030427
Available System Update from the inbuilt app:
Last Check: 09/14/2017 12:00 PM (today)
Build Number: WW_2.20.40.198_20160930_8756_user_rel (93.31 MB)
Click to expand...
Click to collapse
very first of all you must update to MM latest MM it has improved battery life and there are also security related issues fixed. the very best thing to do is.. go to the following link. see the section flash firmware without AFT. (you do not need to change recovery or boot image or any thing just follow the instruction)
reboot your phone in fastboot mode and run each and every command step by stem. even if some of them fails.. not reboot, after first boot go to recovery mode and factory reset. start again and then again sideload latest MM from asus website
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Not so sure I wana upgrade to MM though. Feels like something will definitely go bad during that.
On ASUS support site, in the firmwire tab, I found a LOT of options to download. It'll take time to find the correct version.
Say I found the correct version (or ROM) and downloaded it. (about 1.2 GB), what are the steps to flash it on my phone? Can it be done using TWRP?
Worth upgrading to Marshmallow IMHO
No freezing, less ram usage, better battery usage especially with a new battery, more compatibility to newer apps, Permissions control (love it)
If you say that you are handy on PC then great, cos you may need to be
ASUS ZenFone2 (ZE551ML) software Image: V4.21.40.352 for WW SKU only*(andriod M)
Thats the current version of MM
Download and place onto SD card, unplug cord and system should recognise.
Plenty of info on the web about upgrading however you need to unroot and renable all disabled.
More then likely will brick phone but piss easy once you have done many times lolol
Check out the Unbrick threads
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
https://forum.xda-developers.com/zenfone2/general/guide-recover-fastboot-bricked-zenfone-t3284337
And what i initially used
http://www.techyoutubers.com/2017/04/fixed-how-to-fix-zenfone-2-hard-brick.html
https://www.youtube.com/watch?v=fsAse5F5xtM
CaptianXLAB said:
Not so sure I wana upgrade to MM though. Feels like something will definitely go bad during that.
On ASUS support site, in the firmwire tab, I found a LOT of options to download. It'll take time to find the correct version.
Say I found the correct version (or ROM) and downloaded it. (about 1.2 GB), what are the steps to flash it on my phone? Can it be done using TWRP?
Click to expand...
Click to collapse
as i suggested it is foolproof method to update to MM. i am 100 percent sure you will not brick if you follow what i suggested. don't see multiple threads. multiple instructions. do as i told earlier
Sorry to be away for such a long time... I'm back. xD
As soon as my exams are over, to do this upgrade.
I'll do it like this:
1. Copy the update zip file to MicroSD. [Filename: UL-Z00A-WW-4.21.40.352-user.zip]
2. Full system image backup using TWRP - All Partitions to MicroSD, then transfer to my PC (Just because I want to xD )
3. Clean format all partitions on my phone (I've had enough "errors after updating" issues on PC, so)
4. Select the update zip file from TWRP, flash it.
5. HOPEFULLY there won't be any errors (If there will, I'll simply restore everything from the backup I just made on step 2. Nothing lost!)
6. Reboot and pray for it to work xD
[if it still works and boots just fine]
7. Remove SIMs, MicroSD, etc., Factory Reset (again. Just cos I want to xD )
[Hope for it to still work on rebooting]
8. Check if everything's working (all apps, calling, playstore, etc. just to make sure)
9. Install everything, sync up, make it my phone again
10. Reboot, boot into Recovery (to see if TWRP is still there?)
11. if TWRP isn't there, Boot into Fastboot, flash a stable TWRP recovery to replace the default one using my PC.
12. Create a MM (before-root) backup of all partitions. (Actually, I'll create THREE backups, can't risk any failures xD )
13. Download the latest SuperSU, Flash it. Download a supported Viper4AndroidFX v5 apk or flashable zip, install/flash that too.
14. Set up root apps (CPU Tuner, Titanium Backup, BusyBox, etc) and first thing to see if Viper4Android works.
[Cos if my phone aint havin' v4a, everything above is useless for me because I can't live without that perfected sound and I'll just revert! xD ]
That seems to be about it. Will all this work? Any suggestions?
Some questions I still have -
There's also a recovery.img file in that zip. Will it overwrite TWRP?
Will the bootloader be locked again after this update? (unlocking it was a long search for android LP)
And the main reason not-that-tech-related I'm wanting an upgrade now (Substratum!):
Spoiler
Will Substratum Theme Engine work with MM? (I just want EVERYTHING BLACK - to rest my eyes. I'll buy themes too)
How well can substratum skin my phone? (I want literally everything dark themed, as much as possible)
Will backgrounds of apps like messenger/facebook be dark themed?
I have a D855 with KitKat 4.4.2 (10h). It is rooted and (now) has the latest TWRP (3.3.1.0)
I have never updated from Kitkat because it runs perfectly rock solid. Until now.
I have noticed that a number of apps I use on Play Store can no longer be updated. I think they have stopped supporting KitKat, so I must upgrade to the latest version of Android, to make sure my beloved G3 lives a little longer.
I have updated TWRP to the latest version from the TWRP website. Which was surprisingly hard to achieve, as I was unable to get into Fastboot or Download modes. After several tries, the TWRP app finally flashed successfully.
Also, I finally got the G3 into Download mode (although I had to hold down the power button for about 30 seconds to get back out of Download mode, after disconnecting the USB cable).
I now need to flash a new rooted MM custom ROM, but I seem to remember the partitions changed from KK to LP/MM.
So before jumping and in, and potentially bricking the G3, I just wanted to ask if any one could offer me some advice on upgrading from Kitkat to MM. To ensure I am successful.
Looking at the old threads, people usually did this back in 2017, and things are a little different two years later, so I thought that it would be worth asking the question now, in case there are newer/different options to consider.
I would appreciate some advice. Thanks.
Many thanks for those who had a look at my question.
I was hoping for some advice on RPM/TZ partitions etc. , Modems, Bump! etc but I guess it was naive to expect the forum for a 5 year old phone to be active.
For my part, a good phone is a good phone. And the LG G3 was a good phone.
I came from a Sony Z1 which was a great daily driver, slightly workman-like but rock solid with good vanilla-style OS.
Moving to the G3,the build quality wasn't quite up to Sony's standards but I suddenly discovered how good audio on a phone could be. The screen was great, the OS was rock solid, which is why I stayed on Kitkat for so long. Also, the G3's removable battery allowed me to use a Mugen 6000mah battery, which has provided amazing battery life.
FYI, I considered going back to a Sony but the G3 was so good, I bought a G5. Which is a decision I have always regretted.
The G5 OS was good, like the G3. The bootloader could be unlocked. The audio and screen were as good as the G3. But the hardware was only mostly good. The phone overheats all the time and successive ROM updates have never resolved this issue. Also, battery life is beyond poor, possibly the worst I have ever experienced with a mobile phone.
If I brick my G3, I think I will replace it with a Sony.
I am going to go ahead and flash an MM ROM, Fulmics or CleanROM. I have a Kitkat bootloader so hopefully that will help (now that Autorec has been removed from Playstore).
I will post how things go.
Safest way to do it:
1. Upgrade to LP from KDZ. Root the phone, install TWRP and flash some MM (or newer) ROM.
2. Upgrade to MM (30b or 30f) from KDZ. Root the phone with king root, install twrp and flash some MM (or newer) ROM.
Thanks for the advice, MESA.
Unfortunately, I have already flashed the latest Fulmics for d855.
Did a clean flash. Appears to be working with no issues.
Upgrading does appear to have resolved the various app issues I was having. Looks like some big companies/organisations are no longer supporting KitKat.
But, now, I have no idea which RADIO/MODEM, RPM, TZ or CUST I now have installed. Also, I do not know whether the kernel is set to permissive.
If you have any advice on anything I should do now, please let me know.
If I am in a class of 1 in terms of rank stupidity please feel free to delete this post. :silly:I got sick of the updater nags. With a couple of previous Xiaomi phones I got away with finally saying yes to the OTA update which would inevitably fail after which the nags would stop for a good long while.
Not this time. I now have Miui 11 (which I did not want and which has a completely broken feedback function, btw) but lost root, magisk, and exposed.
I should also note that another Max 3 user posted here that permitting the OTA update bricked their device, so I guess things could be worse.
About to see if I can re root using the same method as before the update.
Sorry if I wasted anyone's time on the blindingly obvious.
Update: The Miui 11 OTA update completely broke screencasting on my phone. While previous updates crippled native miracast you could still use it within apps such as media players prime video etc. Not anymore. The new casting and widi settings see devices but do not connect successfully while apps with casting ability see no devices at all. If I can't get around anti rollback I'll have to buy a new phone.
brasscupcakes said:
Update: The Miui 11 OTA update completely broke screencasting on my phone. While previous updates crippled native miracast you could still use it within apps such as media players prime video etc. Not anymore. The new casting and widi settings see devices but do not connect successfully while apps with casting ability see no devices at all. If I can't get around anti rollback I'll have to buy a new phone.
Click to expand...
Click to collapse
Don't worry about anti-rollback unless you go back to rom that has no anti rollback. I go from miui 10 global to miuieu 11 P beta to miuieu 11 Q beta then back to miuieu 10 P stable. Now I settled on miuieu 11 P stable, yes miui 11 Q is very buggy. A few of my app don't work properly.
[Fix] Root on latest MIUI 11 build !
Just update Magisk Manager to 20.2 !
What's with a screen when charging, it keeps turnin on? Happens after MIUI 10 install...
Since the first version of Android Q, I could never do it Root, I can't make Magisk work, whatever I do.
I install it without problems, but when restarting it is not installed, I never have root.
Try 20.1 and 20.2, it still doesn't work.
I have a Mi Max 3 6/128
I installed the latest Miui 11 OTA update last night - taking a full Orangefox backup beforehand. After reboot, the phone was full of ads suddenly and it took me a while to figure out that root had been removed. I soon discovered that Orangefox had also been removed and replaced with a clunky-looking version of TWRP. I reflashed Orangefox and Magisk - coming back to recovery inbetween-times and it booted fine but the ads were still there so I tried to install Xposed via Magisk and that seems to have pretty much soft-bricked it. I can get into Orangefox where it said 'No Rom' which didn't seem like a good sign. I tried to re-flash the full backup I'd made with Organgefox yesterday (and this not really understanding Orange fox that well) but that hung at 'System image' - so I tried to flash without that and that succeeded but it's still totally bootlooping.
I'd very much appreciate some advice:
1. The Orangefox backup I made was with all the boxes ticked - i.e back up everything. I have the dim idea that trying to simply restore all of this won't work (it certainly doesn't seem to work). What parts of the full backup should I try to restore?
2. If I install the latest Global Miui 10 ROM - which is still Android 9 - using the Miui repair tool, will this brick the phone because of ARB? Or is it safe to do this?
3. Will dirty-flashing the latest Miui 11 rom via OrangeFox likely make something I can at least boot up and get some data (it turns out that 'SMS backup and restore' hasn't been working for weeks so I don't have a pile of work texts that I really wouldn't like to lose)?
4. Any other suggestion most gratefully received. Thanks in advance.
(Thinking about it, this thread is for the OTA breaking the MI Max 3, not my particular woes with restoring an Orange Fox backup - so, with apologies, I'll post in the Mi Max3/Orange Fox thread.)
PS: Flashing the OTA again fixed it, short term: no root is better than no phone.
Hey,
I have to apologize, since I am new in this topic. I assumed it to be a bit easier. However.
I bought a OnePlus 7 Pro and went through some up and downs now. Finally I did the following:
I unlocked the bootloader
I updated to OxigenOS 10.X, X I guess was 3 or so.
I managed to find the right TWRP image that worked perfectly: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
I went into recovery TWRP and installed the zip, additionally magesk or so. Was somewhere suggested to do so.
I rebooted into OxygenOS. So far everything was working.
I rebooted into recovery mode, into the TWRP app.
Now my intention was to install LineageOS, I choose 17 because the OxygenOS 10, I heard was based on Android Q
I wiped out the storage as suggested in the corresponding manuals
I installed LineageOS 17 zip-file via TWRP
I rebooted => Result: Nothing works anymore.
What means Nothing: When I start the phone I come into the FastBoot Bootloader Menu. That's it. No recovery. No TWRP. No OxigenOS and for sure no LineageOS. For sure I can flush img files. But non TWRP image I have chosen worked again like before.
Having spent a day now in this topic as a newbie leavs me a bit weak and disappointed now. Since I probably miss a little bit the appropriate vocabulary I am not able to find something helpful in the net.
So, what am I looking for. I need to bring that phone back into something usable. Maybe into it's original state. Still prefer to have a LineageOS 1X with TWRP installed. It was a great 5 minutes experience. For installing LineageOS 16 I guess I would have needed OxygenOS 9 installed and not 10 (like after my update).
So is there any way to safe my phone?
As the title says. I've seen some older posts from 2019 about it not working, and need to know its status as of right now. I checked their website, and it provides a guide for this specific model, but it doesn't work. What else can I use?
Twrp has not worked on our phones since Android 9. So no it does not work on 10 or on 11
Tom Dude said:
As the title says. I've seen some older posts from 2019 about it not working, and need to know its status as of right now. I checked their website, and it provides a guide for this specific model, but it doesn't work. What else can I use?
Click to expand...
Click to collapse
According to the TWRP website their latest release 3.5 does work on Android 10 and they are working to get it usable on Android 11
Unfortunately our device tree is outdated; there is no android 10 branch let alone 11. The latest release for our device is for those still on android 9, as denoted by TeamWin's new naming convention. If a new branch for 10 and/or 11 can be added to Github, maybe we'll see a build that works for those that have moved on from pie.
GitHub - TeamWin/android_device_google_bonito
Contribute to TeamWin/android_device_google_bonito development by creating an account on GitHub.
github.com
41rw4lk said:
Unfortunately our device tree is outdated; there is no android 10 branch let alone 11. The latest release for our device is for those still on android 9, as denoted by TeamWin's new naming convention. If a new branch for 10 and/or 11 can be added to Github, maybe we'll see a build that works for those that have moved on from pie.
GitHub - TeamWin/android_device_google_bonito
Contribute to TeamWin/android_device_google_bonito development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
so what does this mean?
i just got a brand new 3a XL
i updated it to 11 and now the phone has so many issues that it is not even useable for me anymore, i need to go back to 9 or flash a custom ROM
so can i downgrade it to pie or dirty flash a stock pie rom and then install TWRP on it and flash a custom rom?
or am i now stuck on a 11 with no way to flash to an older stock rom or custom rom or install TWRP?
also if you install TWRP on 9 then i assume you can still flash a stock 10 or 11 rom and revert back to 9 right
gdroid666 said:
so what does this mean?
i just got a brand new 3a XL
i updated it to 11 and now the phone has so many issues that it is not even useable for me anymore, i need to go back to 9 or flash a custom ROM
so can i downgrade it to pie or dirty flash a stock pie rom and then install TWRP on it and flash a custom rom?
or am i now stuck on a 11 with no way to flash to an older stock rom or custom rom or install TWRP?
also if you install TWRP on 9 then i assume you can still flash a stock 10 or 11 rom and revert back to 9 right
Click to expand...
Click to collapse
i see you quoted my post but it is blank
also i am having major problems navigating this new site now , it logs me out whenever i do anything or move between pages and then i can no longer log in it gives an error " Security error occurred. Please press back, refresh the page, and try again. "
on chrome
First you might want to post what issues you are having in 11 as really there have not been many postings about issues on 11 at all.
That said to answer your question:
Android 9 is very old and of course no longer being updated. I cannot even think of a custom rom that is still based on android 9, but if your dead set on going back to 9 and being a huge security risk you need to download the last android 9 full from from google factory images and run the flash-all file either vat or sh depending on what os your on, This will completely wipe your phone.
If you want to try a custom rom there are very few that are actively updated. The only one I can think of that I KNOW is updadated and current is LOS. Unfortunately while it works really well there is absoluetly no support at all for it on our phone. Not even a dedicated xda thread for it. I wqas on it for a while but ran into an issue with dialing 911. Not sure if it was an LOS issue or not but immediately went bqck to stock with custom kernel after that and have been that way ever since.
To summarize:
Android 9 is basically dead and outdated.
Android 10 lives on only in the very few custom roms available
Android 11 at least for me is at least as stable and usable as 9 or 10 was
TWRP is likely never going to return to our phone and honestly really isnt needed anymore. Really the only thing we cannot do anymore is flash something directly from our phone. Without TWRP you must now flash all images and kernels and such from a pc.
Yeah this site is not quite ready for prime time yet. I also have constant issues with it. Hopefully the reply goes through this time
gdroid666 said:
so what does this mean?
i just got a brand new 3a XL
i updated it to 11 and now the phone has so many issues that it is not even useable for me anymore, i need to go back to 9 or flash a custom ROM
so can i downgrade it to pie or dirty flash a stock pie rom and then install TWRP on it and flash a custom rom?
or am i now stuck on a 11 with no way to flash to an older stock rom or custom rom or install TWRP?
also if you install TWRP on 9 then i assume you can still flash a stock 10 or 11 rom and revert back to 9 right
Click to expand...
Click to collapse
Haven't seen a reply
gdroid666 said:
i see you quoted my post but it is blank
also i am having major problems navigating this new site now , it logs me out whenever i do anything or move between pages and then i can no longer log in it gives an error " Security error occurred. Please press back, refresh the page, and try again. "
on chrome
Click to expand...
Click to collapse
Did you see the reply this time?
adm1jtg said:
Haven't seen a reply
Did you see the reply this time?
Click to expand...
Click to collapse
yes i can see it
the problems i have are
1)using assistant via "hey Google" does not respond to what i say, instead it brings up a menu of suggestions , and i have to repeat myself
or sometimes it won't work at all just says can't reach google try again later
2) smart lock trusted device does not work it constantly relocks my phone after minutes no matter what trusted bluetooth devices are paired , not only annoying but dangerously distracting while driving"
3) problems with android auto and android auto with assistant ,
4) bug where pressing the volume rocker to adjust media or ringer volume (in either direction) causes all sound, media or ringer to just stop
5)problems with the accessing the phone screen while in a call
when i pull the phone from my ear and go to use the screen when in a call the screen goes off and is not responsive to touch then it goes on for a split second , then off, then on, then off , then on
seems like the software service that controls the (light?) sensor that detects if the phone is being held to your ear is not working right, i had issues with this on my nexus 6p too though but it had a different sort of behavior , it would just be black and unresponsive and i had to press the power button to wake the screen again, and i had to stop using power button ends call cause it would end the call whenever i needed to use my screen while in a call and the glitch happened and kept the screen from waking when i pulled away from my ear
6) sometimes get glitches with the app switcher/recents
sometimes the "pill" gesture does not respond and i can not bring it up at all,
and the animations are all glitched out too nearly all the time
animations are a mess jumpy, glitchy ,shaky
it's going to give someone a seizure
7) no visual VM tab in the stock phone dialer app
this was working on 9 on another 3aXL ut stopped after update to 10 ,same carrier but this had been a problem on the nexus 6p too
off /on issue , mostly off
8) texting photos to IOS devices does not go through now
i thought it said you could install TWRP on the 3a XL if you were on Android 9
so what i was asking is, what happens if you dirty flash a stock Android 9 ROM? then would i be able to install TWRP from there
or i can not do it now since i updated it to 11?
I am just curious if it can be done, I will probably just take your advice and stay on 11 for now though and hope there is aoe improvements in android 12 developer preview
i am not at all hopeful though
and after testing my old phone some of the same assistant and auto bugs are on those devices too so i guess it is just issues with assistant that cropped up the same ties i updated
gdroid666 said:
yes i can see it
the problems i have are
1)using assistant via "hey Google" does not respond to what i say, instead it brings up a menu of suggestions , and i have to repeat myself
or sometimes it won't work at all just says can't reach google try again later
Cant comment on this as I dont use assistant
2) smart lock trusted device does not work it constantly relocks my phone after minutes no matter what trusted bluetooth devices are paired , not only annoying but dangerously distracting while driving"
Dont use smartlock either
3) problems with android auto and android auto with assistant ,
Dont use android auto either
4) bug where pressing the volume rocker to adjust media or ringer volume (in either direction) causes all sound, media or ringer to just stop
Never had this happen and had this phone on both stock 10 and 11 and also on LOS 17.1
5)problems with the accessing the phone screen while in a call
when i pull the phone from my ear and go to use the screen when in a call the screen goes off and is not responsive to touch then it goes on for a split second , then off, then on, then off , then on
seems like the software service that controls the (light?) sensor that detects if the phone is being held to your ear is not working right, i had issues with this on my nexus 6p too though but it had a different sort of behavior , it would just be black and unresponsive and i had to press the power button to wake the screen again, and i had to stop using power button ends call cause it would end the call whenever i needed to use my screen while in a call and the glitch happened and kept the screen from waking when i pulled away from my ear
Never had this happen with any of the above roms either
Could your tempered glass somehow be blocking the sensor as I have heard of symptoms like that being caused by one.
6) sometimes get glitches with the app switcher/recents
sometimes the "pill" gesture does not respond and i can not bring it up at all,
and the animations are all glitched out too nearly all the time
animations are a mess jumpy, glitchy ,shaky
it's going to give someone a seizure
Not helpful I know but also never seen this occur in all my time using many android phones
7) no visual VM tab in the stock phone dialer app
this was working on 9 on another 3aXL ut stopped after update to 10 ,same carrier but this had been a problem on the nexus 6p too
off /on issue , mostly off
Only seen this when your not using the correct/default stock phone apk
8) texting photos to IOS devices does not go through now
I text stuff to iphones all the time, could be a carrier or apn issue
i thought it said you could install TWRP on the 3a XL if you were on Android 9
I was never on android 9 on this phone but I believe thats correct. However you would lose all security updates for well over a year and a half or so. I BELIEVE the last android 9 rom update was aug 2019
so what i was asking is, what happens if you dirty flash a stock Android 9 ROM? then would i be able to install TWRP from there
or i can not do it now since i updated it to 11?
You could go back but it would not be advised and since twrp shares the boot partition as soon as you flashed any rom greater the android 9 you would lose twrp.
I am just curious if it can be done, I will probably just take your advice and stay on 11 for now though and hope there is aoe improvements in android 12 developer preview
i am not at all hopeful though
and after testing my old phone some of the same assistant and auto bugs are on those devices too so i guess it is just issues with assistant that cropped up the same ties i updated
Click to expand...
Click to collapse
ugh I really am not liking this new forum format. I answered each of your line items under each number but it really isnt showing up very well.
Sorry it has taken so long to respond but i wanted to give a complete answer. Given all the issues you are having and that in my personal opinion going back to 9 really isnt a good idea I would recommend giving los 17.1 a try. It will NOT get you twrp but it is based on android 10, and updated weekly. The only downside to LOS 17.1 is that there is literally no support at all. Even the responsibvle dm's I dont believe even own our phone. That said it ran perfactly for me except a wierd 911 issue that may or may not have been due to LOS. I am seriously thinking of going back to LOS myself, am just really lazy as I would have to redo my entire phone and start with a clean android 10 stock flash.
When you have backup religion: 'tWRp IsNt NEedEd ANyMoRE'
Yet nobody can answer OP's question.
ssurell said:
When you have backup religion: 'tWRp IsNt NEedEd ANyMoRE'
Yet nobody can answer OP's question.
Click to expand...
Click to collapse
There is no alternative for our device running 10 or 11. If we had a device tree newer than 9 we could probably get an auto build from teamwin, but as of now there is none.
As for backing up, most things are backed up using cloud services, not to mention twrp isn't so elegant on a/b devices. You have to reinstall after updates, it can interfere with built in updaters, and restoring backups on a/b devices seem to cause more problems that anything.
41rw4lk said:
There is no alternative for our device running 10 or 11. If we had a device tree newer than 9 we could probably get an auto build from teamwin, but as of now there is none.
As for backing up, most things are backed up using cloud services, not to mention twrp isn't so elegant on a/b devices. You have to reinstall after updates, it can interfere with built in updaters, and restoring backups on a/b devices seem to cause more problems that anything.
Click to expand...
Click to collapse
An often repeated mantra it seems that has little to do with creating and restoring partition images. Where I might agree is the lack of need for an elaborate gui to perform update and flash procedures. Seems LOS recovery could fit a dd function into the recovery partition. But lack of user control over boot slot after a crap system update is all the code politics I need to know. No wonder DU folded up.
I have a working TWRP for Android 11.
Captain_Throwback said:
I have a working TWRP for Android 11.
Click to expand...
Click to collapse
Well throw us a link and give any disclaimers you may have about us using it lol
adm1jtg said:
Well throw us a link and give any disclaimers you may have about us using it lol
Click to expand...
Click to collapse
I posted it in the Telegram group here: https://t.me/pixel3a/161825