had this device all of a week (barely), seemed to work great out of the box, have left it stock intentionally.
take the April security update, reboot.
Have completely lost pinch zoom / multitouch and it seems as though the screen's settings, software or combination are completely misaligned / out of whack regarding touch input.
It's the kind of behavior you get when you have a droplet on your screen and the phone screen is getting erratic input... like it's compromised or fragmented somehow.... I've increased sensitivity which made the phone more usable, but I can barely use the bottom row of my home screeen. If I switch to left hand and try my L thumb, it better detects the input (if I aim WAY LOW). Almost like the calibration for the screen touch has been completely FUBAR.
Hoping custom software and lack of OTA updates fixes this? Has this community seen this issue and are custom ROMs a way out of the mess, or is this a hardware issue that absolutely requires the device to be returned and replaced? Seems odd the change happened with no physical change to the phone.
Same issue here when updating. Complete factory reset fixed mine
@beflythis hey did you figure the fix out? I have a similar issue. Factory reset didn't help me
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
anshuuu03 said:
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
Click to expand...
Click to collapse
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
This is definetly an issue with what seems to be the software, not sure exactly what is wrong though (I dont know too much about kernel driver code),
anshuuu03 said:
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Click to expand...
Click to collapse
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Do let me know if it works. It would be a life saver
fbievan said:
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
Click to expand...
Click to collapse
I think downgrading to Android 10 has worked for almost everyone facing this problem
vovapolischuk said:
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
Click to expand...
Click to collapse
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Now that i know that im now going crazy, and atleast one other person has very very similar story to mine, there needs to be a proper fix. I do know that android 10 and android 11 do have different touchscreen drivers. Downgrading then upgrading back wont work, atleast to my knowledge. I've done plenty of looking, and just don't know whats wrong. If any kernel devs that know their way around touchscreen drivers, and pixel 4as. Would be a life saver. But I have little idea of whats actaully going wrong.
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Yep, downgrading again to Android 10 alllows multittouch to work
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
fbievan said:
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
Click to expand...
Click to collapse
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
fbievan said:
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
Click to expand...
Click to collapse
Make sure to test, test, and test
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
Can I ask: has that worked for you?
fbievan said:
Can I ask: has that worked for you?
Click to expand...
Click to collapse
I think I will try and do the 10 > 11 > 12 > 13 in a few days. I am stuck with some work and cannot afford to keep resetting my phone atm. But I will update here whatever is the update on that
Related
Hi All,
I have a two Relays that have served me well, and I enjoyed having them, but the time has come to pass them on to someone else. Before I do that, I'd like to update them to the most recent versions of stable-release software that is available for them.
For Cyanogen, I have:
cm-11-20150831 (this is stable)
cm-11-20160523 (this is a nightly build)
For recovery I have:
philz touch 6.48.4
I'd like to replace Philz with a newer TWRP, but the Relay is no longer listed on the TWRP website. I'm also wondering if there was ever a stable CM release newer than the one I have.
Does anyone have sources for the above?
Thanks.
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
mrigancb said:
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
Click to expand...
Click to collapse
Although I'm not a developer I have been working on my SGH T699 from T Mobile. You may already know of the JellyBean and before. Recently I've noticed new builds for the samsung Galaxy S Relay 4G like the Validus 5.0.2 or the Fat Toad. I haven't tried those yet I was trying for a higher version. With 8.0 Oreo it requires partitioning and I need to brush up on that. So I went lower to the 7.0 or the 7.1 Nougat. I started noticing a lot of broken or old links so I had to resort to fishing the internet for most of the packages apparently lost in XDA. I pretty much have all of them and was just starting to try a few out when I ran into problems like I want to keep using the keyboard and Wifi calling or a related Wifi issue. It also crashed, went into bootloop or even soft bricked within a few days. The Roms and packages I've found are highly unstable and I see many had flashing issues. So far I've been tricking my device into taking the flash and even then it doesn't hold long. I'd like 6.0 MarshMallow if I can, maybe 7.1 if they ever get stabler that'd be great. But so far the ROMs for the Galaxy S (relay) are fairly horrible to say the least. I get the impression these so-called developers aren't testing their ROM creations more than 5 minutes and then handing them off to noobs who may be very likely to brick their device trying to get it in and running, only to have it crash repetedly! Or worse, hard-bricked.
I like this device. I think I'll keep working on it.
Casper Young.
I got a bug in nokia5.3 after the android 11 update, any scroll that was broken, the keyboard didn't respond, even though the android keyboard, the game that was touched didn't respond, very sorry to update to android 11
Switch back to Stock ROM.
jwoegerbauer said:
Switch back to Stock ROM.
Click to expand...
Click to collapse
this is stock rom
adiepribumi said:
I got a bug in nokia5.3 after the android 11 update, any scroll that was broken, the keyboard didn't respond, even though the android keyboard, the game that was touched didn't respond, very sorry to update to android 11
Click to expand...
Click to collapse
Me too!
I read a lot about the after android 11 update problems.
I have no idea how to fix the upper left touch screen problem.
It simply freezes after a while until I reboot it.
Looking to revert back to android 11 and need to know what to do to not brick my phone.
Currently have an unlocked galaxy s21 plus, Odin is installed and so is a 4 file firmware package for Android 11..
I have USB debugging checked and most things backed up before I perform a factory reset..
Is there anything else that I'm missing, am I completely wrong? Sorry, it's been a long time since I've done anything like this
As long as it wasn't a OTA upgrade that also updated the bootloader version you should be able to roll back.
Make sure all critical data is redundantly backed up. Verify it's all there and readable.
So did you succeed in this?
Edit: It's downgradeable ez pz. Just download the latest Android 11 and flash via Odin. I have the Exynos version.
0rigin said:
So did you succeed in this?
Edit: It's downgradeable ez pz. Just download the latest Android 11 and flash via Odin. I have the Exynos version.
Click to expand...
Click to collapse
But what if the bootloader was updated? Maybe Snapdragon is different
JeffATL said:
But what if the bootloader was updated? Maybe Snapdragon is different
Click to expand...
Click to collapse
Probably. On the N10+'s snaps apparently it's not so you can roll back from 12 to 11 but no further. I'm still running Pie and 10 on my N10+'s and will not upgrade either.
blackhawk said:
Probably. On the N10+'s snaps apparently it's not so you can roll back from 12 to 11 but no further. I'm still running Pie and 10 on my N10+'s and will not upgrade either.
Click to expand...
Click to collapse
11 is the best iteration out of all mentioned, so I recommend you upgrade to that at least. 12 was a beta testing software, but 13 is again a step in the right direction and OneUI 5 is really becoming a powerhouse. Now if only they got rid of the bloatware, but that's also easier than ever to manage nowadays.
JeffATL said:
But what if the bootloader was updated? Maybe Snapdragon is different
Click to expand...
Click to collapse
You'll have more luck finding answers in the S21 Ultra section. Can't remember the exact bootloader versions, but if it's one of the later ones, you won't be able to revert. Android 12 is a piece of trash.
0rigin said:
11 is the best iteration out of all mentioned, so I recommend you upgrade to that at least. 12 was a beta testing software, but 13 is again a step in the right direction and OneUI 5 is really becoming a powerhouse. Now if only they got rid of the bloatware, but that's also easier than ever to manage nowadays.
Click to expand...
Click to collapse
I doubt that as cpu cycle sucking scoped storage is fully active on 11 and above. On Android 9 and 10* it isn't. Not willing to risk screwing up 2 fast, stable, clean running machines that are fulfilling their mission by changing the firmware. To hell with global elitist Google's disinformation and hype Gookill... I see you
Not vaxing my N10+'s either☠
Bloatware is easy to stop from at boot up on stock Samsung's with Package Disabler (not on Playstore). Fastest and easiest solution.
*haven't used my N10+ Android 10 much so I need to do a comparison with my other one loaded with Pie. Will a 2 5+ yo Pie load beat out a freshly loaded and configured Q load? Q seems to get slightly worse SOT, so far, but I need to play with it more as it may not be fully dialed in yet.
My oldest N10+/N975U/Pie runs like a bat out of hell. It's current load is 2.5+yo. It is my most stable platform of any OS in the last 18 years.
Anyone that already got the update can comment any improvements or problems you are experiencing?
I have big battery drain with Android 12
My experience with Xperia phones is that there is often a period of increased battery drain the weeks after an Android version upgrade. Sometimes, I needed a factory reset to make it go away. But, I didn't have to do that when my 5 II went from Android 10 to 11.
jcms666 said:
Anyone that already got the update can comment any improvements or problems you are experiencing?
Click to expand...
Click to collapse
Nope. And after the 12 update, phone doesn't get warm when charging
Any advice to get the update on the states?
I'm super curious how to get the update, OTA has nothing and the xperia app tells me I'm updated, but I'm still on Android 11 and https://xpericheck.com/XQ-BC52/23119804 tells me it's been out for weeks. I'm in Denmark so I'm guessing it's the right package in the URL.
Feel like a noob asking but it's super weird if they stagger it so long I think
glovesave said:
I'm super curious how to get the update, OTA has nothing and the xperia app tells me I'm updated, but I'm still on Android 11 and https://xpericheck.com/XQ-BC52/23119804 tells me it's been out for weeks. I'm in Denmark so I'm guessing it's the right package in the URL.
Feel like a noob asking but it's super weird if they stagger it so long I think
Click to expand...
Click to collapse
True that. Also have the XQ-BC52, and I got the update via OTA about two weeks ago, I'm from Sweden. Really nice update since it seems like all the "heating issues" is gone now Now this phone is pure pleasure!
glovesave said:
I'm super curious how to get the update, OTA has nothing and the xperia app tells me I'm updated, but I'm still on Android 11 and https://xpericheck.com/XQ-BC52/23119804 tells me it's been out for weeks. I'm in Denmark so I'm guessing it's the right package in the URL.
Feel like a noob asking but it's super weird if they stagger it so long I think
Click to expand...
Click to collapse
i'm afraid you are forced to flash your update via Newflasher. Probably you got my same problem (but with 5 II): your device don't receive OTA updates at all? If is this the case, then yes, you have to update it manually. Sorry.
KnockOut^9 said:
i'm afraid you are forced to flash your update via Newflasher. Probably you got my same problem (but with 5 II): your device don't receive OTA updates at all? If is this the case, then yes, you have to update it manually. Sorry.
Click to expand...
Click to collapse
Hi and thanks, my 5III did get two security updates so it's able to get OTA.
Interestingly enough the xperia companion also is stuck on Android 11 it seems telling me there is no new update...mmmm I'll wait a bit before trying to flash the official version manually
glovesave said:
Hi and thanks, my 5III did get two security updates so it's able to get OTA.
Interestingly enough the xperia companion also is stuck on Android 11 it seems telling me there is no new update...mmmm I'll wait a bit before trying to flash the official version manually
Click to expand...
Click to collapse
I made repair fon and get A12 from xperia companion. But its like a factory reset!
so I waited until the OTA update after Android 12 and that brought my 5 III up to 12 and on that OTA version so that was easier
Cheers guys !!
No issues with Android 12. Battery seems a little better. New UI is meh. Not a big upgrade, but not bad.
Hi everyone,
This is driving me mad. I've been trying to install a bunch of different ROMS on my Samsung Galaxy A10 and while it seemingly installs just fine, when I press "reboot system" it gets into a perpetular loop. Am I doing something wrong here?
Bliss OS Rom v14 w/ Android 11 for Samsung A10 Arm64 ( Stable Unofficial ) released 2021
IMO you should contact developers of Bliss OS to get your issue fixed.
Recovering Spaghetti said:
Hi everyone,
This is driving me mad. I've been trying to install a bunch of different ROMS on my Samsung Galaxy A10 and while it seemingly installs just fine, when I press "reboot system" it gets into a perpetular loop. Am I doing something wrong here?
Click to expand...
Click to collapse
I don't have experience with Samsung phones in particular, but with Moto phones I've used the online recovery tool to restore the phone back to stock and start over. Not sure there is anything similar with Samsung? Good luck!
jwoegerbauer said:
Bliss OS Rom v14 w/ Android 11 for Samsung A10 Arm64 ( Stable Unofficial ) released 2021View attachment 5799499
IMO you should contact developers of Bliss OS to get your issue fixed.
Click to expand...
Click to collapse
Hi,
The thing is I also tried DotOS & OctaviOS & the issue perseveres
vdun1188 said:
I don't have experience with Samsung phones in particular, but with Moto phones I've used the online recovery tool to restore the phone back to stock and start over. Not sure there is anything similar with Samsung? Good luck!
Click to expand...
Click to collapse
Hi, I believe there is, but the thing is that this is like my third ROM on this phone (Decided to install a new one after my bluetooth headphones refused to connect with my phone while being able to connect just fine to literally everything else) & this is the first time I'm having issues like that. Before, when I managed to install the ROM then it was smooth sailing since hence why I'm asking for help. I've spent a few hours trying different ROMS already.
Recovering Spaghetti said:
Hi, I believe there is, but the thing is that this is like my third ROM on this phone (Decided to install a new one after my bluetooth headphones refused to connect with my phone while being able to connect just fine to literally everything else) & this is the first time I'm having issues like that. Before, when I managed to install the ROM then it was smooth sailing since hence why I'm asking for help. I've spent a few hours trying different ROMS already.
Click to expand...
Click to collapse
Since it has worked fine up to now I'd like to first exhaust all the concievable solutions before going for the nuclear option of stock firmware.
Recovering Spaghetti said:
Since it has worked fine up to now I'd like to first exhaust all the concievable solutions before going for the nuclear option of stock firmware.
Click to expand...
Click to collapse
Understood. For some reason that is beyond my comprehension, it seems it is sometimes suggested to install stock and then a different custom ROM. Again, I don't know what it is actually supposed to do, as I've stayed with LineageOS to keep it simple. I'm not saying to stay with stock, just use it to get phone back to default, then start from there.
nuclear option..stock - hahaha )
Gawd Damit, I tried LineageOS too & a bunch of other stuff & it's always the same problem. I'm all out of ideas now.
Please help, Tried every ROM, same result, doesn't boot
Hi, I've got a Samsung Galaxy A10 SM-A105F and I tried installing all kinds of different roms on it and they install just fine but then when i go to boot to system I end up in this hell hole of perpetual booting and restarting. I've been at it...
forum.xda-developers.com