After becoming completely tired of my Sony Tablet S shutting down on a daily basis due to the poor memory management and the reality that there will never be a JB update, I decided to see what Sony could do about it.
After generic advice from Sony Support to reset the device, update the firmware etc. they agreed to take it in for repair. The turnaround was surprisingly quick but upon receiving it back today the first thing I noticed was the old honeycomb clock. After initial setup, I checked the software info and sure enough the repair has apparently consisted of reflashing the tablet with Android 3.2 build 1.10.001100003.
This basicly says to me, "our updates are of such poor standard that your device is better off without them". Sadly though, the performance is still not great and I've already had one shutdown while reinstalling apps from the store, not to mention the plethora of features (from both Android and Sony) that are missing from this old version, but presumably I am to infer that I should now ignore the available system update which would comedically undo the "repair" and repeat the cycle.
Aside from being of interest to those who want root access, just what use is reverting the device to an older firmware. Has anyone else had any joy getting Sony to acknowledge the problems they've created and ignored with the Tablet S?
MikLSP said:
This basicly says to me, "our updates are of such poor standard that your device is better off without them".
Click to expand...
Click to collapse
No, they just installed the stock firmware, which the tabelt had when it first came out, that means they did a full wipe..
Yes, I'm aware it is the Tablet's original firmware, I didn't mean to imply that it had been replaced with stock Android Honeycomb.
Actually though, I have just noticed something I missed before on the accompanying document. In the itemised repairs, along with "basic tests" of various hardware components, it seems they have actually replaced the motherboard! At least that's how interpret Part: MBX - V0A0 MB ASSY A1 Qty:1
That would explain a little better why the device is back on the original firmware and certainly makes the repair look more logical now!
Hopefully, it will show some improvement....time will tell.
Related
I am certain that by now (over) half of the (normal) Archos G9 users really only want one thing and NOBODY (including Archos) seems to care at all about doing it!
Very few need/want 'rooted' firmware (not to mention it wastes valuable memory space because the original Archos firmware is still leftover).
What MOST of us actually want (and in many cases need) is a simple way to just remove the totally idiotic restriction that Archos has put in their firmware that prevents us from ever installing an older firmware version (that is KNOWN to work correctly on our specific device).
At one point, somewhere during the problems with the 4.0.x firmware releases Archos did actually provide a way for users to go back to 3.2.80. WHY they have not provided us with a way to go back from the the 4.0.2x (worthless garbage) firmware releases to older firmware that we KNOW actually works makes no sense at all. Seems like they just hope you will be stupid enough to by a newer Archos model (something I sure will never ever do with that kind of idiot way of dealing with us users).
It's bad enough that Archos does not care at all about us users, but... there are some really sharp and smart people here on XDA that SHOULD be able to hack around things. Yet, it seems like none of them have any interest in doing so. WHY???
firmware
55mls said:
It's bad enough that Archos does not care at all about us users, but... there are some really sharp and smart people here on XDA that SHOULD be able to hack around things. Yet, it seems like none of them have any interest in doing so. WHY???
Click to expand...
Click to collapse
Because the most likely result would be a bricked tablet. It is not an easy thing to do and people who could do this are not wanting to use older firmware. Not that I'm one of the sharp and smart people but I think archos has keys you would need and they don't release them to the public.
stevemp said:
Because the most likely result would be a bricked tablet.
Click to expand...
Click to collapse
At this point I would be happy to brick my 101 G9 since it's of absolutely no use to me now anymore without having to install SDE and rooted 4.0.7 firmware (I've come close to bricking it a few times with all the various rooted/custom/alternative firmwares and other crazy things I've tried myself already). In other words, if NOBODY ELSE finds a way... I'll just keep trying things myself until it either works or ends up bricked. Not like it really matters now to me now anymore
It is not an easy thing to do and people who could do this are not wanting to use older firmware.
Click to expand...
Click to collapse
Although I'm no expert on things, I actually think that it really is NOT all that hard to do (if anybody that actually knows what they are doing would care to do it). I think you are dead on with how all the so-called 'developers' simply only care about whatever the next thing they can do instead of about actually fixing anything with the actual Archos firmware. Seems rather foolish to me though when they could actually PROVE how good they are by actually doing something instead of just adding all kinds of extra fluff (most of which can be downloaded/installed from Google Play for anyone with a stock rooted ROM if they really wanted that junk).
Not that I'm one of the sharp and smart people but I think archos has keys you would need and they don't release them to the public.
Click to expand...
Click to collapse
And that brings us right back to my original question... WHY? By now, Archos has already totally ruined their reputation. They've gone out of their way to totally trash as many G9 tablets as they could, then hoped people would just buy their newer devices... and NONE of their newer devices actually work right either. So, WHY would a company want to continue running their reputation down the toilet when they COULD actually do something that MIGHT actually improve it?
In other words, the one single thing that Archos COULD have done for us G9 users was to provide a way to install whatever older 'official' firmware version that we KNOW actually did work on our devices? So, again we're right back to WHY had Archos not done what us G9 users actually need/want instead of locking us into crap we NEVER WANTED?
I suppose I COULD live with rooted stock 4.0.7 if I ABSOLUTELY HAVE TO, but...
Installing SDE and the kernel files for rooted firmware use up some RAM space. And, with only 512MB to start with, well every single bit (pun intended) alters the capabilities and performance of the device. Heck, just going from official Archos 3.2.80 to official 4.0.7 already was at a cost of both RAM and system memory space.
On top of that, installing a 'rooted' firmware always uses up even more of the system flash memory. Depending which ROM, that ranges from 300MB to 500MB. When you only have an 8GB device, that really only ever had a little over about 6GB of usable flash left with official Archos firmware...
Well, when installing a 'rooted' ROM, that uses up more space for the ROM on top of the space that the original Archos firmware. And, that's the part that really bugs me!!! I had already been suckered into that the device had 8GB of Flash, then found out only really had about 6GB of "usable" memory, then had to install SDE and a 'rooted' ROM to ever get it to work right again ending up with only about 5GB of flash in the end (even deleting the leftover archos.ext4.backup file does not get back to what the device originally had).
Now, if somebody could tell me how to remove/delete ALL of the supposed 'official' Archos firmware so that I would actually have what I originally would have with the 'official' Archos firmware... well, I MIGHT just be happy enough to live with it (even though it DO NOT WANT 'root').
Anyway, I just don't care anymore!!! I simply want ALL TRACES of that horrible crappy Archos official 4.0.2x firmware TOTALLY REMOVED from my device!!! I'd prefer that it be totally reset to something close to whatever it came with (maybe something like 3.2.79) and then be able to upgrade to whatever higher firmware I want from there.
Oh, wait a minute, there ARE companies that actually do repair/refurbish these G9 tablets and CAN reset them... so, it would cut into their profit making if anybody else ever told us how they do it. Sure, now I get it... paid $250, now pay another $200 to get it to work again. NOT GOING TO HAPPEN!!!!!!!!!!!!!!!!!
I'll totally brick this thing and throw it into the garbage before paying to have it fixed now anymore. Damn LiThion batteries only last 2 years before the drop way down in usage, and I'm already coming up on a year and a half since this piece of Archos crap came out. Now I get it, just throw it away and NEVER buy another Archos procduct again!!!
I called up Archos today and had a stock answer when I asked about this.
I didn't give up and they have passed the issue to the tech department. (my hopes aren't high) however the bloke I spoke to said he hadn't had any calls or feedback regarding this.
he suggested formatting then loading up the older firmware, after instructing me how to download older firmwares by copying link then pasting, then editing build number for firmware I wanted.
I told him that Archos doesn't allow for this and everyone else does, so it isn't software from google but from archos that is blocking the install.
he took my number and said I would get a callback....
will update if I ever get one
y2grae said:
he took my number and said I would get a callback....
Click to expand...
Click to collapse
Welcome to a group of thousands that will very likely never get any response back from Archos!
Pretty clear that is not going to happen simply because of the totally idiot instructions that gave you. Seems like EVERYBODY ELSE except the people at Archos already KNOWS FOR A FACT that you can not install any older firmware version. Why they ever told you to even try to do that is just pure stupidity on there part.
Of course, if they actually do call you back an provide any USEFUL information I'm all ears, but I don't expect anything from Archos on this matter at all now anymore, or they WOULD have already told us how to do it. After all, it was about 3 months before they got around to putting out 4.0.28... and even then the screwed it up and there are actually 3 different versions of 4.0.28 they put out (am I the ONLY one that caught that and actually cares about it?... Seems surdu_petru has NOT bothered to update his rooted ROMS to the last of what Archos put out).
Really sick of Archos trying to con people over and over and over and over and over and over (am I repeating myself of is Archos?).
Hi
My LG G5 is just under 18 months old, so still covered by the 2 yr UK warranty in that sense. It has started to only accept a USB connection (for charging, data connection, anything) once before it needs rebooting to accept it again.
So, I sent it back to LG. They sent the phone back to say it is rooted and wouldn't fix it.
I have eventually got to someone at Head Office and they still say the same, that as the OS has been modified then they will not repair it (the warranty does state that they will not repair a fault CAUSED by a modification by the way)
So I ran the internal software check as mentioned here - https://forum.xda-developers.com/lg-g5/help/how-tell-g5-rooted-t3528248 - and it does indeed come up with a positive, it says that SUPERUSER (a rooting related app) was installed on 1/1/17. - see attached image
I well remember doing a full wipe and reinstall of the phone on new years day and Google Play installed all the apps on my account and I had to delete the ones that I didn't use anymore. I have rooted various devices and that is why Superuser was in my Google Play account. It did install on the phone that day and was uninstalled (never run) the same day. The phone has never been rooted (it has been mine since new, I know how to root phones and would know if I had! I have also had no reason to) and I have run Android Pay and the banking apps on it all the time.
I can actually get the phone repaired for £25 anyway so it's not so much the repair that is the issue right now, it's that I think LG shouldn't get away with treating customers like this and I want to make a point.
Before I go through the various public attempts to make the point (Twitter, Trading Standards, Tech mags) I do want to be 100% clear of the facts, so if I am mistaken then please do tell me.
The Head Office guy said that even though Android Pay etc still works, that they have different checks and that a program has been run that has modified the OS. Their own internal phone software tells me that this program is Superuser. My understanding is that superuser does nothing at all unless a phone is rooted. Then, on a rooted phone, it will act as a 'middle-man', intercepting anything that wants root access and asking for permission from the user.
Am I correct in saying (and LG incorrect) that Superuser makes NO change to the OS? All the version numbers in About in Settings are the current legit ones.
In my opinion, they are technically intelligent enough to know that there is no technical issue with my circumstances, they just want to get out of fixing the phone (which has already cost them me buying the next incarnation of the series at the end of my contract and my next TV too). Even if it had been modified, the app was installed on 1 Jan, the issue started a month ago, and LG happily fixed another fault (fingerprint sensor) on the phone back in April with no complaining about root! There could be no proof that the fault was caused by Superuser.
Any advice/ammunition to talk to them would be appreciated.
They don't know what they saying.. superuser app could not modify the os if it is not rooted and have not unlocked bootloader...
Exactly what I thought.
I should probably have posted this in the Superuser forum, is it possible to move it? I don't want to repeat post. If anyone could say what Superuser DOES do, that would be ideal..
Thanks
Thanks Gerciolst.. they have now agreed to repair it!
TL;DR cliffs - suspecting backdoor install after phone screen repair, would like to flash stock ROM, is a trusted source available?
I recently broke the screen on my Samsung A50 from Verizon, and had it repaired by an "authorized" repair shop recommended from Samsung.
This is the second time I've done this. The first time, I took it to a non authorized repair shop, and the fingerprint sensor stopped working and the price for repair was no less expensive than the authorized one, only more convenient location wise.
So this time, I got it done at the authorized shop called UBREAKIFIX.
When I arrived for the AMOLED screen repair they asked me what the password/pattern was, and I thought that was really weird considering it's just a hardware replacement, and asked why do you need the password? The guy gave me some gibberish about how they need to make sure blah blah blah and I was so desperate to just get my phone back and didn't want to argue so I just told them, thinking what's the worst that could happen?
So a few things.
- I dropped it off with a full battery, and got it back with 30% charge level when I got the repair done maybe 3 hours later.
- The battery now drains a lot faster with little/no use. I've always taken good care of the device, it's fairly new as I had it replaced under warranty for a brand new one due to fingerprint sensor issues mentioned previously
- When getting on wifi I am now suddenly getting a warning I've never gotten before:
"Apps are using mobile data
0 apps are using mobile data when when your phone is connected to WiFi. Tap here to manage these apps"
Of course no app is listed that is using the mobile data. It's never shown this warning before..
- A few apps seems to have been opened at the very least, including Signal, a secure messaging app which was at the very least launched and appears the messages were tampered with. WTF.
I am suspecting some employee has installed some backdoor/Trojan but I can't prove it. I'd like to install a clean stock ROM to give me better peace of mind. Hopefully this will solve the battery issue as well?
Can't quite explain the battery draining fast issue if it's not a backdoor... Did they possibly damage the battery while removing it to replace the screen, and maybe install an inferior one?
All in all I am horribly regretting the decision on paying $150 to have it repaired instead of spending $225 for an Amazon certified refurbished one. With the +$75 refurbished option and a screen replacement that I would attempt myself, I would have the base for a second WiFi device that I use for work, which would actually come in handy (since my current WiFi device is a J3 with 2gb RAM which can be very slow for some things).
I went for the lazy repair option because I didn't want the headache of having to reconfigure the phone to my likings again, .with the 10 or so OTA updates which must be painstakingly done one at a time with a reboot between every one, can be an all-day process.
is there a trusted source for a stock ROM image that I can flash, and instructions for doing so?
Bump
Contact Verizion to obtain the source of the Stock ROM.
Is asking for (and receiving) ROM images a thing now?
Correct me if I'm mistaken, but I am fully anticipating having to jump through all sorts of hoops and "escalations" only to be told that this type of thing isn't supported by Verizon.....
I have a A52 5g and a tab S7+ wifi, that are both remotely controled and monitored, and serve as gateway to my home network and basicaly every device connected to it. I noticed it at first and mew NOTHING related to this, didnt even know what open source was. Since then i have come to understand that, somehow, my phone seems to run a custom version of android, my guess is, built from AOSP and designed to disguise itself as oem samsung ui, but in background enables remote access and total takeover of every function. I have discovered, using total commander, that storage has been partitioned in 2 separate locations, and that one folder in there is called root system file, and filled with data/apk/installkits/etc.. this has me asking for help in 2 specific questions:
Am i holding a rooted device or is there another possibility that creates this situation? I was convinced its rooted untill i read here that root prevents from using samsung pass, secure folder etc.. and those seem to work on mine(or is it a version of those apps?) If its indeed rooted, will it wype everything if i flash it with the stock rom? And should i trust a small cell repair store to do that or learn how to do it myself?
2: i have bought 3 brand new phones since august, and made sure not to use my usual accounts, no use backups, not even set it up near my home wifi, and it almost instantly started self installing harmful software in background. I see no other way for it to link itself to be owned by me at initial setup, but for the sim card, new of course, but with my usual phone number and service transfered to it. Is that enough to make a breach and compromise a new device? If so, what would be different after fpashing the stock rom, if everything reinstalls itself? Do i need to change my number? Change cellular service provider even? I know its an unusual request but im a fast learner, i have compiled lots of technical info on specific apps, ip's, servers, build id numbers etc.. that i know would make more sense to anyone more qualified than me, and i am about ready to try and wype/flash the thing myself, i just would feel better with a little help since i have gone this far pretty much alone, since no service provider or manifacturer actualy feels like this is their problem to solve....
Here you can download firmware for your phone and flash with Odin, which you can also download at the bottom of the page, there are instructions on how to do it also.
Make sure to download correct firmware for exact device you have. There are few different A52 5G models.. SM-A526B, SM-A526U, SM-A5260, SM-A526U1, SM-A526W.
You will lose all data after flashing new firmware. After this your phone will be like brand new from Samsung..
If your device is rooted then that means your warranty is void and manufacturers and carriers are under no obligation to help you.
I'm trying to understand your situation but its so conflicting I don't know where to begin.
For example, you say your device runs a custom AOSP with a Samsung UI. Thats exactly how it actually works. Samsung take the AOSP, customise it with their own functionality, then overlay their own skin as the UI. Theres absolutely nothing unusual about that.
I'm conflicted as to whether your rooted or not. If the manufacturer or carrier has physically seen the device and won't repair it then that would suggest your definitely rooted. If you spoke to them virtually and told them your rooted then they will use it as an excuse whether you're truly rooted or not. The partitions you mention could be the internal storage and an sd card which can be seen non-rooted. I dont know what you mean when you mention a "root system file". Is it an actual folder called "root" or is the app you're using just telling you that you've reached the "root" of the filesystem? I can't quite work out what you mean. You also say Knox-powered apps still work which just adds to the confusion.
You stated you have had 3 new devices and they all self-installed harmful software. To get one device compromised is possible. To get three compromised means your either a high profile government target (which I doubt because they wouldn't be so sloppy as this) or your doing something to compromise your own devices such as continuously visiting dodgy websites.
Flashing will fix things but so would having a new device. The only common denominator is you so either you're doing something wrong or you truly are a government target in which case I wish you good luck!
First let me appologise for the long silence, i cut off most online activity for a while and just read your answers. To clarify, i have not solved my prolem yet. But ill try to explain better what you ask about my situation:
About de os version arobase40 got it right. I Asked google play help reps. And a stock samsung version of android would not trigger googles warning about running a custom version of android. So that point to a modified after-the-fact more than to the fact samsung has their propierary version installed.
About beeing rooted or not, ylwhat you are asking is what im not totaly certajn of, also. I know partition can happen without rooting, its seems to have created a "virtual sd card" since its named as such when sd card slot is actualy empty. About the root files folder, i cant say for sure, all i can say is that its holding a large amount of Gigs that dont get taken into account when looking at storage capacity and usage, and accessing that folder gives me a message that root files cant be access from this device. Does it mean my device had root acess privileges revoked to prevent viewing files that hide what is given control of the software remotely, so i dont find out or have the capacity to remove or alter those files?
What is absolutely sure is that if it is rooted, it wasnt done by me. As for the chance the devices were not factory brand new, 1 of them was not, got it opend box from amazon, a saudi arabia version, but my prkblems had started months before getting it, did not keep it more than 2 months, and all others before and since are 100% pure factory new, some directly from my cellular service provider, as financed device came with 2 year agreement of service,(actualy 2 of them i got this way) and the last one is my tab s7+ i got online directly from samsung canada website, on preorder, delivered on release day.
And lastly the fact i cant seem to shake those persistent leeches, is not from having reckless habbits online, but from having careless and uneducated habbits before that all started, usual older lazy dude stuff, like not changing my wifi password after a ruff breakup with bipolar psycho ex gf, or having only a few passwords reused on most my accounts. I have stopped doing those things long ago now that i know better, but i suspect that i could have been unaware something gettnng installed and staying dormant for a while, maybe? The ex had way more opportunities than needed to do something like this and is more than psycho enough to realy do it also. For having the skills to do it, lets say she has "assets" that can easily get her guys willing to help about that. It may also be coming from somwhere else, but as you say im not a super spy or a high ranking gov. Official. Im not even that interesting, and have absolutely no usable id for fraud or anything, my credit history would raise more red flags then there is in all china. So after so long struggling with this still very active, i cant even think of a rational reason to do so much effort into this, theres nothing to gain, i only can imagine that maybe a twisted mind seeking revege, or with a sick way of amusing themselves could see the point to all that, but i dont realy care. I only want to get rid of it.
As for the way it manages to be so much persistent, i can only see one option left i didnt remove from the process, and its through my phone number/account on the sim card, even a new sim on a new phone, still is linked to my cell service. I did initial setup with only that new sim card, accounts freshely created during setup, with no info or anythink linkable to my previous accounts, and even did it sitting outside, far from any building that could get me in range of a wifi network. And it still was no more effective at staying secure.
Thats why i did not yet try to flash a stock rom myself on my device, because it would, at best, become exactly like it was when brand new, and i know that this is not enough to keep it secure, and that means theres still something im missing in the whole picture.
Pretty much as the title says. I'm stock and unrooted, but the idea of an update that blows a physical fuse and can't be undone gives me the shakes. So I held off since it came out. We're about a month into deployment of the update, so I'm now considering applying it. Has anything in terms of major bugs/performance problems come out that should factor into my decision? I've read various threads here and not seen much major stuff.
Thoughts and input? Thanks in advance.
One reason for not going to Android 13 would be that It can mess up the wireless charging function . Mine has not worked properly since I updtaed , even after the patch ( which was supposed to fix it ) it still doesnt work .
Thanks. I've never used wireless charging but I appreciate this caveat to the A13 update.
Other than that all seems good , bit annoying for me as I use wireless charging a lot , have one in my car and this was a major factor in me buying a Pixel 6 . Had high hopes when they rolled out a patch pretty quick but nothing seemd to of changed .
Sad to hear it broke.
I'm afraid to accept major updates after the very final update ever for my OnePlus 6T broke several key functionalities I relied on. That led me to the Pixel 6, which I don't love but it is working "fine" and I hope A13 won't nuke me. I will likely update this weekend unless I hear something widespread and impactful to how I use the phone.
accessibility service not possible in non-store apps
miss said:
accessibility service not possible in non-store apps
Click to expand...
Click to collapse
WHAT... That's horrible... ACR won't work ) :
miss said:
accessibility service not possible in non-store apps
Click to expand...
Click to collapse
Just go to app info, click on 3 dot menu to bypass restriction.
I updated and I'm pretty happy. IIRC there's now a "developer" Android 12 build that works on the Android 13 bootloader if it ends up not being for you for any reason. I haven't seen any significant issues, though now I see people mentioning wireless charging I did notice it kept popping up the little "100%" screen every 5 or 6 minutes like I'd just put it on the charger when I was using the one in my car, after it hit full, but not the one in my room that provides a higher wattage. Either way, not a big issue to me.
Just be sure to read the other threads about updating to 13 and sideload the OTA after you update if you want to be certain you won't accidentally brick booting the un-updated partition after updating. It gave me a hassle sideloading from both of my PCs, but if you use USB 2.0 it'll go through, just... reeeeeally... sloooowly - so you could let it go overnight.
Jaitsu said:
I updated and I'm pretty happy. IIRC there's now a "developer" Android 12 build that works on the Android 13 bootloader if it ends up not being for you for any reason. I haven't seen any significant issues, though now I see people mentioning wireless charging I did notice it kept popping up the little "100%" screen every 5 or 6 minutes like I'd just put it on the charger when I was using the one in my car, after it hit full, but not the one in my room that provides a higher wattage. Either way, not a big issue to me.
Just be sure to read the other threads about updating to 13 and sideload the OTA after you update if you want to be certain you won't accidentally brick booting the un-updated partition after updating. It gave me a hassle sideloading from both of my PCs, but if you use USB 2.0 it'll go through, just... reeeeeally... sloooowly - so you could let it go overnight.
Click to expand...
Click to collapse
So, even unrooted and stock I have to fuss with the side load update thing?
Frankenscript said:
So, even unrooted and stock I have to fuss with the side load update thing?
Click to expand...
Click to collapse
You don't have to, it's just eliminating an unlikely risk. It'll work fine after just updating. Even if the update somehow failed you'd be safe as it would just roll back; the risk only lies in if you update, successfully boot, and then something causes Android to fail to boot, which should never happen if you're not rooted and tinkering with things.
Basically:
* Your phone has two "system" slots.
* Either taking an OTA from an automatic system update, or manually sideloading it, updates the slot you're not on, then switches to it.
* When you update to 13 and it successfully boots, a flag is set that permanently prevents booting with an older bootloader. (This is a one-time thing and shouldn't happen again with future updates.)
* At this point, if something caused Android to fail to boot, it might try to boot into the un-updated system slot. Because that flag is set and it still has the old bootloader, it wouldn't boot and would be bricked.
* Sideloading the OTA again (or even getting another automatic update, but that won't happen immediately) ensures this won't happen by updating the other slot.
Personally I'd just do it because I'm paranoid (and moreso because I personally do root and tinker with things I shouldn't all the time ).
Lughnasadh said:
Just go to app info, click on 3 dot menu to bypass restriction.
Click to expand...
Click to collapse
with any apk file, any application?
I use many that are not from any official store, such as motomedialink, which needs to have accessibility permission to work
miss said:
with any apk file, any application?
I use many that are not from any official store, such as motomedialink, which needs to have accessibility permission to work
Click to expand...
Click to collapse
As long as the accessibility permission has been restricted for that app because of the new policy (applies to Notification Access permission as well), it should work.
So far the update to A13 seems to have gone smoothly. I honestly haven't noticed anything different yet.
For what it's worth, one benefit I've noticed so far is that certain applications don't get shut down so aggressively as under A12. Despite all the tweaks I made previously, Angry Birds 2 would get shut down pretty much as soon as I did anything else on the phone, and Sound Profile would shut down randomly. Both of these seem fixed under A13.
Haven't noticed a downside yet in terms of how I use the phone.
I've been on A13 for two weeks now and everything seems to run smoothly, definitely dropped phone temperatures. I don't use wireless charging so can't tell about that. I'm on 13.0.0 (TP1A.220624.021.A1, Aug 2022) rooted. Tried loading 13.0.0 (TP1A.220905.004.A2, Sep 2022) but it won't boot, I'm getting "your device is corrupt it can't be trusted and may not work properly" error, had to revert back to previous one. Shame as I'm struggling with biometrics and this new update was suppose to fix the issue. Might try to flash_all with -w option this weekend to see if it makes any difference, can't be asked to be setting up my phone from scratch after three days of festival