Develop Bugs

Touch "gets stuck" on letters while typing

Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J

Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...

Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4

Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.

I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app

I get this issue when playing a game or typing.

pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.

Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.

Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly

This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.

That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4

player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.

OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:

danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates

I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app

sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.

danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.

So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?

danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.

LG G Pro Freezes

My LG G pro freezes or lags randomly. sometimes i need to hold the home button so long to get it back working. any help that could fix this problem?

DracoPiece said:
My LG G pro freezes or lags randomly. sometimes i need to hold the home button so long to get it back working. any help that could fix this problem?
Click to expand...
Click to collapse
Stock Rom or custom?

vladmir said:
Stock Rom or custom?
Click to expand...
Click to collapse
both. i dont know if it is hardware related. but when i push the home button about 3 mins it became normal

DracoPiece said:
both. i dont know if it is hardware related. but when i push the home button about 3 mins it became normal
Click to expand...
Click to collapse
I'm full stock, sometimes he freezes for a short time due the heavy load.
Try to do a factory reset or a fresh flash.

vladmir said:
I'm full stock, sometimes he freezes for a short time due the heavy load.
Try to do a factory reset or a fresh flash.
Click to expand...
Click to collapse
i already tried reflashing and a factory reset. but it's still happening. i think this is hardware i better check this on a repair center

Just deal with it. This is Android. Which means Google-Linux Frankenstein beta. Everything is beta. Nothing is stable. And the devs want money for their unoriginal ideas.
Until you're ready to plunk down big bucks for an iPhone 6 ( a real smartphone) accept the limitations of these over priced Korean devices.
Unfortunately, Camera has stopped.

hahaha
Perry2547 said:
Just deal with it. This is Android. Which means Google-Linux Frankenstein beta. Everything is beta. Nothing is stable. And the devs want money for their unoriginal ideas.
Until you're ready to plunk down big bucks for an iPhone 6 ( a real smartphone) accept the limitations of these over priced Korean devices.
Unfortunately, Camera has stopped.
Click to expand...
Click to collapse
wow dude ???

Perry2547 said:
Just deal with it. This is Android. Which means Google-Linux Frankenstein beta. Everything is beta. Nothing is stable. And the devs want money for their unoriginal ideas.
Until you're ready to plunk down big bucks for an iPhone 6 ( a real smartphone) accept the limitations of these over priced Korean devices.
Unfortunately, Camera has stopped.
Click to expand...
Click to collapse
Lol wow I hope your joking...... Gtfo with that garbage...... Lame ....
2SHAYNEZ

shayneflashindaily said:
Lol wow I hope your joking...... Gtfo with that garbage...... Lame ....
2SHAYNEZ
Click to expand...
Click to collapse
The whole Android experience is a mix and match of parts. Nothing is completed. Sure, there is not as much lag as there was four years ago, but there's glitches and hiccups and hassles and headaches all over the place.
I will not be getting another Android phone.
And google is a sorry company that only sees projects part of the way through. Sure, there are some really good apps, like Keep. It synchronizes well across the desktop and mobile.
But they have no interest in fully developing certain items such as Google Maps. Right now, Maps reroutes the driver even when he is not off course. Sometimes several times in a minute. When I'm driving in downtown Boston, this is a bad thing to be happening.
And I'll never get another Android phone. FLashing roms. I hope I get to a point with a new phone where I don't have to hear that term again.
You flash this rom and wow, you can drop down to 3G if you like. But hey, the speaker volume sucks. Okay, well try this fix. Now the phone is in boot loop.
Wipe the phone. Now try this. Ok great that works. Except now all my contacts won't sync.
LTE won't stick. Screen burn in with Note 2. With certain launchers, much lag.
Crappy arse cameras that take too long to focus or they capture the shot while there is blur. I've gone through at least 15 camera apps in my google android Frankenstein LOVELY phurking experience. None compare the iphone 4s which is what, three years old now?
And this is just the tip of the iceberg. I've got things to do this morning or I would start listing off many other issues with Google Android Samsung junkity junk junk.
And no, I won't gtfo. Don't read my posts if you don't like!

Lol alright buddy good luck to you.
2SHAYNEZ

DracoPiece said:
My LG G pro freezes or lags randomly. sometimes i need to hold the home button so long to get it back working. any help that could fix this problem?
Click to expand...
Click to collapse
Actually i experience freezes in the internal browser on turkey KK on some websites.
In the past i had system hang up with a specific app for Bluetooth in the car.
Maybe it's app related in your case ?

Solution to Lags caused on g pro
Just install clean master and do a memory boost....and the device will no longer experience any kind of lag.....:good:.....also frequently clean the cache.

I understand at some point and is frustrating sometimes but phone makers NEED BRING REAL ANDROID EXPERIENCE and NO FULL BLOAT CRAP APPS this is why I think more what was my next phone for now LG is on mark
Samsung is dead for me except S3 and Gnote 1 truly outstanding phones. after that all is the same sh****

For thouse, who run stock 5.0.x-5.1.x, why to risk the device?

I have some thumb rule, never update to the newest firmware, and reed the comments. Also at home I have a router, that the manufacture update the firmware from time to time, but I used to run one firmware before the last one. It just an example, but since all the Lollipop, people complain, so why bother? Can't you wait for a while, till Google resolve all the issues? Do you consider Kitkat was perfect then? Or does Lollipop runs perfect on Nexus 6 & 9? I'm starting to think, it intentionally, like iOS 7 on iCrap 4, on iOS 6 it was fine, just think of it, maybe Google do it intentionally, to make us buy a new device? Or they just do a bad optimization job for older devices, and put all effort toward new devices? Any thoughts? I know we all nexus user, are a free beta testers, but if running latest firmware, means it brick out devices, it's hard to thrust Google like that, so I think it's better to stay on Kitkat till better times.
Sent from my hammerhead using Tapatalk

The people who's tablets work fine (the vast majority I'd guess) don't complain. You only here from the people who have problems.
I've been on lollipop since the preview and it's been great. I'll be flashing 5.1.1 the second it's out. Kitkat is dead to me, and very ugly looking back. It certainly was not perfect.
If my device gets the brick people are talking about it would suck but I really, really doubt it has anything to do with the firmware. Some hardware failure most likely. No reason to stay on an old release.

5.0.2 was horrible. While I disregard majority of users complaining of battery life, some of them weren't spewing nonsense.
5.1 is an improvement. I'm one of the guys who do not post every complaint or dissatisfaction I encounter with the Nexus 7. I know what the problem is, I know where to ask for help to pinpoint the cause, now it's my turn to make a decision, stay on Lollipop? or revert to KitKat? Or remove the cause, in other words the app itself.
Back to the OP, there is no risk updating to 5.x. Your device won't magically break. If you like to play it safe, maybe it's better for you to wait for user feedback and ignore the OTA.

OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?

I wouldn't take an ota myself. Not because of "the brick," I think thats a hardware problem, I feel it's a cleaner update with fastboot and if something fails I'll know what.
And you can (and should) make full nandroid backups in a custom recovery (cwm, twrp etc.).
But to the poster aboves comment it just goes to show you people are having different experiences. 5.0.2 was fantastic for me, great battery life, best it's ever been actually (still as good on 5.1 ~8 hours screen time over two days.)
The memory leak was/is a problem. Oh no I had to reboot once a week. Huge headache. On 5.1 I'm at 270 hours uptime and system ram's at 479. It is creeping up slooowly but better than 5.0.2
I guess it depends what you do with the tablet and especially what apps you have installed. I use my **** pretty heavily though so I don't know why I'v had no problems.

donisan969 said:
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
Click to expand...
Click to collapse
Hard bricks have been reported from both OTA and ADB updates, but very seldom from users of custom ROMs... Most likely cause is eMMC failure due to faulty hardware, though the issue is present on nexus 4 and 5 as well... Possibly faulty bootloader software too.

^Bootloader faults could be possible.. that has pretty low level access. I don't know low enough to corrupt the chip. I don't know. Asus/google probably does but guaranteed you'll never hear a word from them.
I hope it's not something like the infamous s2 brickbug. Then you're just playing russian roulette. Maybe entropy can help lol.
What emmc chips are the 4 and 5 using? I'll have to look.

I'm not sure this is true but if you use Greenify I think the memory is kept in check better, although it requires root. I still see the occasional launcher redraw but not nearly as bad as it was in 5.0. I was on 5.0.2 for several weeks and wouldn't have updated if I hadn't read about the hardware failures.

Well if you don't update your tab, than you don't need a Nexus, buy some cheap chinese tabs for 70-100$, almost all of them are on kitkat, most of them vanila android, no updates, and they all work fine.
This is Nexus.It's a developers tab, for testig, trying, people who like the freshest system on their device, who like clean android....if something's not working, there's always an image of the old system or a bunch of ROMs to test and use...

I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk

donisan969 said:
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
Click to expand...
Click to collapse
Device OEM is irrelevant in that regard, the quality of internal components is really the crux of understanding hardware failure IMO. of the major android OEMs, all of them have in the past put forth devices that were predisposed to early hardware failure, mostly due to choices of components used during the manufacturing process. Hardware revisions on individual devices of the same model is also a valid form of comparison.

It Seems That OOS 11 Beta is Delayed Due to Finally Having to Fix The OP7T Decryption Error

As per a statement posted on XDA, the OnePlus Nord OOS11 beta should be coming sometime this week, though the builds for the 7 series are still delayed as OnePlus is finally confronting the dreaded decryption issue that has plagued the series since its inception. This means, that, likely after Android 11 is released for our devices, that we should be able to have a fully functional TWRP along with more custom ROM development on the way. This is very good news for the tinkering community. Hope more is to come in the near future.

I mean, we can hope, but at this point, I am afraid it's still just wishful thinking.

gboybama said:
I mean, we can hope, but at this point, I am afraid it's still just wishful thinking.
Click to expand...
Click to collapse
Well, seeing as it's the very reason for the delay, it wouldn't make sense for OnePlus to announce that they were delaying the beta to fix the encryption issue just for them to not fix it. If that were the case, they would just not say it, you know?

You're a couple days late;
And;
>This means, that, likely after Android 11 is released for our devices, that we should be able to have a fully functional TWRP
except decryption that is, blobs are the same so I am not confident TWRP will be able to decrypt on OOS11. We have to wait and see, but they may have broken it on a hardware level.
> along with more custom ROM development on the way
No, it does not mean this.

Lossyx said:
You're a couple days late;
And;
>This means, that, likely after Android 11 is released for our devices, that we should be able to have a fully functional TWRP
except decryption that is, blobs are the same so I am not confident TWRP will be able to decrypt on OOS11. We have to wait and see, but they may have broken it on a hardware level.
> along with more custom ROM development on the way
No, it does not mean this.
Click to expand...
Click to collapse
On a good note it seems a couple more roms have come about

SenyorMauricio said:
Well, seeing as it's the very reason for the delay, it wouldn't make sense for OnePlus to announce that they were delaying the beta to fix the encryption issue just for them to not fix it. If that were the case, they would just not say it, you know?
Click to expand...
Click to collapse
Hoping I'm wrong of course, but the pessimistic scenario is that OP forgot there was an issue with the 7T and was caught flatfooted while testing the update on their various devices. Then, they start looking for a cheesy workaround that doesn't undo the original problem.
Considering the recent, less than impressive, decisions coming out of OnePlus, I'm feeling it's more likely that some quick, unsatisfying shortcut to patch the problem is rolled out. I can't imagine a world where they dedicate the precious time of a couple of heroic developers to undo a tricky design mistake on an old device.
Heck, that's not even the worst scenario. If they were really caught with their pants down on this and it looks like the update is really difficult to apply, I wouldn't put it past their managers to conclude that the 7T is a niche phone with a declining base and they could decide to just leave it on Android 10, saying it couldn't be updated.
Again, though, I hope I'm wrong!

gboybama said:
Hoping I'm wrong of course, but the pessimistic scenario is that OP forgot there was an issue with the 7T and was caught flatfooted while testing the update on their various devices. Then, they start looking for a cheesy workaround that doesn't undo the original problem.
Considering the recent, less than impressive, decisions coming out of OnePlus, I'm feeling it's more likely that some quick, unsatisfying shortcut to patch the problem is rolled out. I can't imagine a world where they dedicate the precious time of a couple of heroic developers to undo a tricky design mistake on an old device.
Heck, that's not even the worst scenario. If they were really caught with their pants down on this and it looks like the update is really difficult to apply, I wouldn't put it past their managers to conclude that the 7T is a niche phone with a declining base and they could decide to just leave it on Android 10, saying it couldn't be updated.
Again, though, I hope I'm wrong!
Click to expand...
Click to collapse
Yeah, I'm hoping for the best. In the original article, it says that had to team up with Qualcomm to begin fixing the issue, so I'm thinking it's both a hardware-software problem, but I wouldn't know since I'm not very literate when it comes to technical issues like encryption. But we shall see! I really just want Oxygen OS on Android 11 since most of the ROMs right now have bugs (as far I've seen—haven't been able to find a ROM that doesn't irritate me in one way or another).

I've read somewhere that the encryption issue has been fixed.and that it's assumed closed betas ether started or will start soon I'll see if I can find the article or if someone knows it feel free to post it

rob420p said:
I've read somewhere that the encryption issue has been fixed.and that it's assumed closed betas ether started or will start soon I'll see if I can find the article or if someone knows it feel free to post it
Click to expand...
Click to collapse
For them yes.
But here's the thing.
Let's assume it's the same issue.
They probably broke or implemented encryption differently on a hardware level, hence contacting Qualcomm to help them workaround (not fix) the issue. We as in users, don't know what broke or is different, and since we don't have the source code we can't possibly know how OnePlus worked around it to decrypt data.
Let's hope something else was broken / implemented differently and not in a hardware level, then maybe it's fixed.

In fact, I have tried the first version of the closed beta version of oosA11. I tried to flash the English version and the Chinese version of twrp in this version. His decryption work still cannot be decrypted. This is only the first closed beta version. Maybe in the future public beta version. Will solve the problem. I don’t know at least the decryption problem in the first closed beta version or not. Currently they are undergoing the second closed beta version test. I don’t know if the second closed beta version has solved the problem. Maybe in the future public test. Version will solve this problem!

谷歌原生 said:
In fact, I have tried the first version of the closed beta version of oosA11. I tried to flash the English version and the Chinese version of twrp in this version. His decryption work still cannot be decrypted. This is only the first closed beta version. Maybe in the future public beta version. Will solve the problem. I don’t know at least the decryption problem in the first closed beta version or not. Currently they are undergoing the second closed beta version test. I don’t know if the second closed beta version has solved the problem. Maybe in the future public test. Version will solve this problem!
Click to expand...
Click to collapse
I'm moving into the camp of saying I'd bet serious money they don't fix the encryption issue.

Are we even getting the beta at this point, it's 20th Jan

[QUOTE =“ gboybama，：84324093，：1342510”]
Yes, I don’t think they will solve the problem. They used a weird decryption method to push their OS to update when they upgraded to 11. They might not solve this problem fundamentally.

gboybama said:
I'm moving into the camp of saying I'd bet serious money they don't fix the encryption issue.
Click to expand...
Click to collapse
Yes, I don’t think they will solve the problem. They used a weird decryption method to push their OS to update when they upgraded to 11. They might not solve this problem fundamentally.

Question Random reboot

Been using my phone consistently for 24 hours. No root. Set it down after a messenger message, and couple seconds later, random rebooted. When it came back up, the gesture pill was flashing. Rebooted properly, and no more flashing. Weird. Anyone been having this?

There are several threads on the topic, and yes it seems to be quite the widespread issue. Some where able to fix this by doing a factory reset WITHOUT a backup from another device, some (like me) needed a replacement device.
We still do not know if its a software or hardware issue, or if these are two separate issues that are similar in symptoms but differ in cause (hardware failure/bug caused reboot & software/backup problem).
I'd suggest you either contact Google and get a replacement immediately or try a factory reset and manual setup (I assume you copied over your files from another phone?).

Wow, that is unsettling. Yes, I copied from an S21U backup. I've only seen this once so far, how extreme does it get? I searched before posting but did not see any discussions. I will look more. Thank you.

Replacement device ordered. More issues arose beyond the reboots, slow charging (6 hours from dead!), apps crashing, settings crashing, wifi issues. I love the phone, but not these issues from a 1k phone!

Have you tried a factory reset, then not restoring from backup (or if you did a cable backup/restore, try a cloud restore instead)?
I hate to suggest it because I restored my Note 10+ cloud backup with no issue, but enough other folks have suggested factory reset and not restoring a backup at all. Worth a shot. Good luck, whatever route you take.

pre4speed said:
Replacement device ordered. More issues arose beyond the reboots, slow charging (6 hours from dead!), apps crashing, settings crashing, wifi issues. I love the phone, but not these issues from a 1k phone!
Click to expand...
Click to collapse
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.

Morgrain said:
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.
Click to expand...
Click to collapse
Ugh, I am not liking hearing that. First pixel phone.

pre4speed said:
Ugh, I am not liking hearing that. First pixel phone.
Click to expand...
Click to collapse
That is some bad luck. Sorry to hear that. But the Packers won today so that's good

TrustAugustus said:
That is some bad luck. Sorry to hear that. But the Packers won today so that's good
Click to expand...
Click to collapse
Is what it is. I should know better than to adopt a new release anything lol. And GO PACK GO!

Morgrain said:
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.
Click to expand...
Click to collapse
I am on beta One UI 4 on my s21u currently, and the bugs on that are not the same bugs as the pixel, that's for sure. At least not the random reboots. But Samsung so heavily skins android, that is not a surprise. One of the main reasons I want to go pixel. Tired of Samsung putting their trash over vanilla Android