How long should encryption take? Is it even working?! - Galaxy S 5 Q&A, Help & Troubleshooting

Hi all,
Today I tried to encrypt my S5 (klte) running lineage-14.1-20170510-nightly-klte-signed. It has about 11GB used on the internal storage.
I was expecting to see the Android screen that tells me encryption is in progress, with a timer showing estimated completion time, but all I see it the usual LineageOS boot logo. I set this going more than 2 hours ago but it has not completed. The phone is warm, so I assume high CPU activity, and the logo is still animating, so I think it's doing *something*, but it's not what I expected to see.
Is something amiss or should I just be more patient?
Thanks,
Russ
PS I took a backup so I can restore if it doesn't work

OK, something was definitely not right, but it's all worked out OK: After 3+hours I gave up waiting and yanked the battery (it was unresponsive to power button). It then booted up fine, prompted me for password, and the phone is apparently now encrypted and all works as it should.
Worth reporting as a bug, do we think?
Russ

Why would you want it encrypted? Really.

西村大一 said:
Why would you want it encrypted? Really.
Click to expand...
Click to collapse
Any number of reasons, which aren't really relevant to the question about why a feature which *should* work doesn't do so as expected.

Encryption is marked as a bug in most custom roms and recoveries. And I king aget the gist of why you'd want it encrypted, but yeah, whatever floats your boat.

Related

[Q] encryption...

has anyone done this yet? I noticed it in the settings, but it said it can take up to 1 hour... just wondered if it was worth while.
if you have done it, does it slow anything down, and how long did it take you to run?
Sent from my HTC Desire using Tapatalk
iamdarren said:
has anyone done this yet? I noticed it in the settings, but it said it can take up to 1 hour... just wondered if it was worth while.
if you have done it, does it slow anything down, and how long did it take you to run?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
I tried but it appears to not work. You have to be plugged in and fully charged (seems to work from 90% ish), and you have to have unlock PIN set. But once you have selected and confirmed encryption, the screen blanks except for a green line drawing of an Android logo, and then after a minute or so the screen blanks out and then you wait...and wait....and wait...and wait. I gave up after 4 hours.
If at any point you switch screen on, you get the PIN prompt: enter PIN, and you're presented with the blank screen with green line diagram of android logo. I've left it like this for several hours. In the end I reset, and got my device back - but still unencrypted. I've also tried without ever trying to log in until at least 4 hours have elapsed, in case the login attempt disturbed the encryption.
I have logged a defect with Asus for this and a couple of other things, and this morning got a response back saying that "We're still looking into this", which seems to suggest that they agree it is a problem.
Cool in gonna try now, at 95percent battery.
Sent from my Transformer TF101 using Tapatalk
That didn't seem to do anything.... I saw the green android with cog body, maybe I need to give it more time. I will set out before i go bed.
Sent from my Transformer TF101 using Tapatalk
I'm wondering how the encryption is handled, is it software or hardware enabled. I have seen with PC's that use software encryption that there is a performance hit and if the encryption is handled by hardware, like a hardware enabled HDD encryption, there is little to no performance hit. The PC I tested the software encryption on took forever to boot vs the hardware enabled one.
Havoc6266 said:
I'm wondering how the encryption is handled, is it software or hardware enabled. I have seen with PC's that use software encryption that there is a performance hit and if the encryption is handled by hardware, like a hardware enabled HDD encryption, there is little to no performance hit. The PC I tested the software encryption on took forever to boot vs the hardware enabled one.
Click to expand...
Click to collapse
You must have used some strange encryption application or had an old computer.
Try truecrypt - on modern (2 core) computer there is practically no performance hit whatsoever (decrypting and even encrypting on the fly is faster than hard drives - on SSD it could be too slow though). The same goes for standard encryption used by Ubuntu (it's very probable that Android tablets use the same method).
Truecrypt (and probably most other full-disk encryptions too) work like that:
- all the data on hard drive is encrypted (edit: it's encrypted all the time, never, ever is decrypted data written to disk),
- when system reads data - it's decrypted before being send to applications,
- when system writes data - it's encrypted before it's saved to the disk.
Also - Tegra2 should have a part handling encryption and decryption so it could be at least partially hardware encryption.
Your right, it has been a while since I have used encryption due to a bad experience early on. I'll give Truecyrpt a try. The software I used before was Safeguard Easy.
iamdarren said:
That didn't seem to do anything.... I saw the green android with cog body, maybe I need to give it more time. I will set out before i go bed.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I left mine overnight, and it still was not encrypted. I had even done a factory reset beforehand to minimize the amount of data to encrypt.
I'm pretty sure this doesn't work. I'll post as soon as I get a reply from Asus.
It did not work, maybe this feature isn't ready yet?
Sent from my Transformer TF101 using Tapatalk
As a feature, it's not ready for prime time. I have it working on the xoom, but every reset it erases my timezone and sets it to GMT. Also, it uses the same PIN as your lock screen, so if you have a numeric pin for easy access, anyone who sees it now knows your encryption password as well. It really should be two different passwords. I intend this weekend to reset my machine and remove the encryption, because it doesn't serve the purpose it was supposed to serve.
Bump. Any info from Asus? I started it at ~7pm. It's midnight, and on the last few power-ups I get nothing except the green android logo after I enter the PIN. So it seems it's still not doing anything? Gonna reset now I guess.
Same problem here with a Transformer TF-101 Build number HRI66.TW_epad-8.2.3.8-20110423
See nothing but a android robot after enter the PIN. 7 hrs later I manually shutdown the machine.
Same here on the Modaco ROM.
Left it on the android pic for 9 hours... it didn't lock the screen or anything, and at the end, the accelerometer still worked when I rotated the screen, but I had to power off and on to get it back.
What does the encryption do, anyway? Does it stop you being able to load files on from the PC? Does it ask for the password when you plug it into the PC?
So no one has been able to get encryption working? I was just going to test this out and saw this thread. Thanks.
I've seen someone talking about some minor issues when running with encryption, so someone got it working.
That MIGHT have been on xoom, but I think it was the transformer.
Just thought I would share my experience with the encryption feature in Honeycomb since some people can't get it working:
At first I couldn't get it working like some people on this thread, I too was stuck on the green wireframe Android for hours on end until I discovered I could still exit back to the homescreen by pressing the home key on the keyboard dock. This happened on both the stock Asus 3.1 ROM and v1.4 of the PRIME! ROM (installed via nvflash).
I then updated recently to v1.5 of PRIME! via CWM and I can report that I was able to encrypt my Transformer after this update. It displayed the green Android wireframe logo for a few seconds, then rebooted and went into the encryption progress page. I had not really done much with the ROM other than change a few small settings and add my Google account, so the encryption was complete in less than an hour. I think the 'hour or more' estimate Google gives within the encryption description text is probably more accurate if you've installed a few more apps afterwards, but of course your timing will vary.
Furthermore I think that the encryption is likely only partial, because I was then able to flash one of the zip files from this thread via CWM without any issues or prompts. Otherwise I'm sure it would've thrown some kind of error such as not being able to mount the system partition or something of that ilk.
Finally (lol ) I also found this page on the Android source website outlining the details of the encyption implementation in Android Honeycomb for anyone interested. There is a mention somewhere of the 128-bit flavour of the AES algorithm being used to encrypt the master key.
Hope this helps anyone trying to get encryption working on their Transformer .
yet another absolutely useless feature, besides bricking the thing for whoever tries to steal it. keeps your data safe.. even from yourself.
i noticed a problem when inserting a microsd (into the pad itself) that it would not be able to boot as long as this is inserted. i am guessing this is because it tries to decrypt the microsd (that is not encrypted) and therefore is stuck in boot.
This is another aspect one should expect if this was a pre-release software. I am extremely disappointed with this product so far, mostly because of the software. most of (not any of the cameras) the hardware (including the keyboard) is pretty good
I did it 2 days ago, and it worked flawless. It tooks about an hour. I use it since and I have no problems at all.
The only thing is that I have to insert the SD card again each time I power on the transformer. Any idea how to change rhat?
fjoesne said:
yet another absolutely useless feature, besides bricking the thing for whoever tries to steal it. keeps your data safe.. even from yourself.
i noticed a problem when inserting a microsd (into the pad itself) that it would not be able to boot as long as this is inserted. i am guessing this is because it tries to decrypt the microsd (that is not encrypted) and therefore is stuck in boot.
This is another aspect one should expect if this was a pre-release software. I am extremely disappointed with this product so far, mostly because of the software. most of (not any of the cameras) the hardware (including the keyboard) is pretty good
Click to expand...
Click to collapse
You likely have ASUS to blame for this, as my understanding is that the Thinkpad tablet deals properly (from the spec anyway) with SD cards attached to the device even to the point it can additionally encrypt them. Again we are all early adopters, Honeycomb was sort of an experiment for Google, and Ice Cream Sandwich is the real next version of the andoid platform.
And encryption is hardly a useless feature, it means Google is finally trying to consider enterprise usage of their products which is very important to the further growth of the platform.

[Q] Encrypting Nexus 4 - Some Questions

Hi,
I am thinking about encrypting my Nexus 4. I am already using encryption on all my computers but I never tried it on my smartphone, so there are three questions I hope you will answer:
1)
How is battery life affected? Well, fortunately the battery of the Nexus 4 is quite good and I hope encryption won't waste too much.
2)
How is speed affected? My Desktop CPU has AES-NI and there's a SSD, so you don't even recognize system encryption. How is it doing on the Nexus 4? I'm just doing the usual smartphone stuff, means E-Mail, messaging, phoning, checking News &Weather and sometimes playing Doodle Jump. My research on the Internet about encryption performance on Android didn't bring up things I can really rely on so I hope someone here can tell me his experiences.
3)
Which algorithm is used exactly? I know it's dm_crypt and I'm using it on my other computers, too, but on my PC I can choose which algorithm I want and on Android it's given as far as I know.
Regards,
becha
You can't use patter lock to unlock your screen, which is a pian for me right now.
Sent from my Nexus 4 using Tapatalk 2
1. Barely noticeable
2. Same as 1
3. Not sure
Sent from my Nexus 4 using Tapatalk 4 Beta
1) I doesn't notice any real impact on battery life. Used the N4 several months before encrypting it.
2) Booting the phone is slowed down, and not only because you have to enter the key for accessing the encrypted drive. But opening apps and doing backup, etc. isn't slowed down. I guess I wouldn't even notice an encrypted devices and so did no one until now, while using my phone.
I was also doubtful before, because in my experience, on a laptop back in the days (5 years ago), the battery drain and performance impact was just to big. But on the other side, I do a lot more disk based tasks on my laptop, than I do on my phone.
in short, after I lost my last phone, I really wanted to give it a try and I didn't regret it until now.
Hoping to hear good answers to question 3.
@HB_Mosh
Well, that's not too bad for me because I don't use Unlock Patterns.
@Vanhoud @memleak
Thanks for sharing your experiences, I'll give encryption a shot.
becha said:
@HB_Mosh
Well, that's not too bad for me because I don't use Unlock Patterns.
@Vanhoud @memleak
Thanks for sharing your experiences, I'll give encryption a shot.
Click to expand...
Click to collapse
can you please tell us your experiences, i was thinking about it, i guess you can CWM, encrypt then restore backup if you want to revert without starting all over
Yesterday I encrypted my Nexus 4, it took around an half an hour. Until now (well, one day...) I didn't discover any problems apart from the fact, that my Nexus 4 did a simple restart for the first time when trying to encrypt it. Everything went fine when trying the second time. The phone itself runs fluent, so up to now I didn't see any performance problems.
Now I can't backup my ROM - any suggestions? Perhaps Recovery can mount to an external USB storage or something? What a pain! You can't un-encrypt either, and there's no way to mount encrypted storage in Recovery I wanted to backup before installing privacy protection in case it borked my phone.
Another encryption question...
Don't mean to hijack this thread, but can anyone tell me if OTA updates will still work on a stock, unrooted N4 that's been encrypted?
Can't find a definitive answer - some have had success on other devices and others haven't.
I don't see why turning on stock encryption on a stock unmodified device would make any difference?
Sent from my Nexus 4 using Tapatalk 2
DroidBois said:
I don't see why turning on stock encryption on a stock unmodified device would make any difference?
Click to expand...
Click to collapse
I wasn't sure why / if this would make a difference either but as I said, I can't find a definitive answer. Some people say that you need to factory reset in order to remove the encryption before you can apply an OTA update, but others say different.
I'd be interested to know if the OTA would work after simply asking you for your encryption PIN on reboot, or if the encryption would prevent the OTA being applied because of the encrypted storage. Does anyone have any experience of this?
DroidBois said:
Now I can't backup my ROM - any suggestions? Perhaps Recovery can mount to an external USB storage or something? What a pain! You can't un-encrypt either, and there's no way to mount encrypted storage in Recovery I wanted to backup before installing privacy protection in case it borked my phone.
Click to expand...
Click to collapse
You have to use TWRP Recovery, which is able to mount your encrypted internal storage.
No way.. I thought I'd tried every option I could think of in TWRP but I'll take a closer look.
Sent from my Nexus 4 using Tapatalk 2
If you start TWRP, it should automatically ask for your passphrase to read the encrypted internal storage. Latest version of TWRP works for me, older ones had bugs regarding to encrypted devices.

Device encryption

Was curious about this feature of the phone. ...I know what encryption is. ... but, in regards to phones, I do not. Can anyone shed some light on this for me? Like, what it does exactly, how it works, does implementing it in my device effect it on an os level or kernel?...any other general information about it is very appreciated. ..... tried google, but it just kept bringing up "15 things you must know about your s5" articles and the like.
beav3r
Skynyrd420 said:
Was curious about this feature of the phone. ...I know what encryption is. ... but, in regards to phones, I do not. Can anyone shed some light on this for me? Like, what it does exactly, how it works, does implementing it in my device effect it on an os level or kernel?...any other general information about it is very appreciated. ..... tried google, but it just kept bringing up "15 things you must know about your s5" articles and the like.
beav3r
Click to expand...
Click to collapse
You can encrypt the device (Settings > Security >Encrypt). However, you will NOT be able to use the fingerprint scanner if you do this. This process takes around one hour and scrambles all the data. Every time you turn on the device you need to enter a passcode before it boots. This helps to provide an extra layer of security on top of the regular PIN or password.
Read more: http://www.itpro.co.uk/mobile/22034/samsung-galaxy-s5-top-15-tips-and-tricks#ixzz319NY0W4G
kprice8 said:
You can encrypt the device (Settings > Security >Encrypt). However, you will NOT be able to use the fingerprint scanner if you do this. This process takes around one hour and scrambles all the data. Every time you turn on the device you need to enter a passcode before it boots. This helps to provide an extra layer of security on top of the regular PIN or password.
Read more: http://www.itpro.co.uk/mobile/22034/samsung-galaxy-s5-top-15-tips-and-tricks#ixzz319NY0W4G
Click to expand...
Click to collapse
Also recovering data off a damaged phone is impossible.
Unless you require your data to be fully encrypted and don't care if you lose it, because it is backed up; do not encrypt.
Thanks guys. Does anyone know the processes the phone goes through while encrypting? Or decrypting. ... just wondering if it would be beneficial at all If someone did a log cat while doing both, just to see if there is a hole that could have an exploit vulnerability. ... and, would dalvik vs ART during the process change that answer, since you're running "custom"while ART is on. ... I'm 99% sure it isn't going to help s#!%, but, never know, little things usually get overlooked.
beav3r

TWRP freezes in flashing - Powers off then, but no 'BLOD' (logs attached)

I was on oreo
I have backup so data not an issue thankfully.
Was using Nitrogen rom with its stock kernel but rom is not the issue since literally no one else is affected, im positive its my phone. Possibly hardware related.
Short version: As you can tell from the title. My phone is freezing randomly while flashing, or sometimes on booting it just stays at google logo. After freezing for 20 seconds and the phone getting hot, the screen goes off. It does not however bootloop.
It does not power off when the screen goes off in the normal sense either since if i attach a charger nothing shows, no battery icon, but i know it charges because then if i go into bootloader and then twrp back again, battery is increased. but if no charger, the screen stays off and battery is not decreased, like a power off :/ what is wrong?!
Full disclosure: i had my cpu(motherboard) repaired 2 weeks ago when it just dropped dead after freezing and me trying to reboot it, which it never did.(that was aquarius rom)
After repair i flashed nitrogen and all went fine until it happened yesterday too but thankfully i could access bootloader and occasionaly twrp. i somehow (after the 100th time of it finally not freezing in flashing or splash screen) managed to clean flash my rom again and it booted.
All went good for a day then suddenly it froze today and when i hard rebooted it, it never went past the google logo again, and screen turns off, which is where i am now. But now i can access twrp most of the time without it freezing now.
What ive done so far: Since this time it actually opens twrp 90% of the time unlike yesterday and freezes only few times, ive managed to flash a few different rom versions and even tried going back to nougat. ALL leading to -> Google logo 20 seconds, screen off.
I'm in the process of downloading factory images and OTAs, which will take 6 hours since i have a slow connection. but i dont know which i should flash (ill be using Heisenbergs guide). Which is a better option at succeding?
what i think is wrong: probably the flashing takes a toll on the cpu and it just freezes n gets hot n shuts off. NO bootloop. Ive attached logs from ''copy log'' option in twrp, i dont know if that will help.
Can it be a hardware issue? Anything else i can do besides factory images/OTA? Should i look into disabling my big cores?
I'd highly appreciate some technical expertise and advice as to how i should procees from now.
Thank u for taking the time to read it!
Lord. Tech said:
.... Can it be a hardware issue? Anything else i can do besides factory images/OTA? Should i look into disabling my big cores? I'd highly appreciate some technical expertise and advice as to how i should procees from now. Thank u for taking the time to read it!
Click to expand...
Click to collapse
Probably a hardware issue related to the motherboard, but you should treat it as a bootloop and follow the workaround you mentioned. If that solves your issue then you will know it is hardware for sure. I guess you don't have a warranty on the motherboard because you didn't mention that route. If you do get it running on small cores, run Accubattery (if you haven't already) and get an estimate of remaining capacity of the battery. If you do send it back for 2nd repair, replace the battery at the same time. Why not? It's only $20 and there would be no labor.
v12xke said:
Probably a hardware issue related to the motherboard, but you should treat it as a bootloop and follow the workaround you mentioned. If that solves your issue then you will know it is hardware for sure. I guess you don't have a warranty on the motherboard because you didn't mention that route. If you do get it running on small cores, run Accubattery (if you haven't already) and get an estimate of remaining capacity of the battery. If you do send it back for 2nd repair, replace the battery at the same time. Why not? It's only $20 and there would be no labor.
Click to expand...
Click to collapse
Yes im out of warranty sadly. Im going to try flashing stock images, if that doesnt work then will look into turning off my big cores. Any advice on if full OTA images would be better than flashing Factory images?
i agree, i shoulve gotten it replaced the first time i had it fixed, regretted that as soon as i got it back. accubattery showed 60% left, the rest seems degraded.
i really hope something works. I'm starting to get fedup of this device i loved so much n still do surprisingly! i hate that google did this to us, that too out of all the devices on the last and most anticipated 'nexus' of all time! Embarassing end to the series.
Lord. Tech said:
Yes im out of warranty sadly. Im going to try flashing stock images, if that doesnt work then will look into turning off my big cores. Any advice on if full OTA images would be better than flashing Factory images i agree, i shoulve gotten it replaced the first time i had it fixed, regretted that as soon as i got it back. accubattery showed 60% left, the rest seems degraded.
i really hope something works. I'm starting to get fedup of this device i loved so much n still do surprisingly! i hate that google did this to us, that too out of all the devices on the last and most anticipated 'nexus' of all time! Embarassing end to the series.
Click to expand...
Click to collapse
Flash full images because OTA's don't contain the full partition image. Just set up fastboot on your PC and follow Google's instructions on the page you d/l the images from. Due to using several custom ROMs, I would recommend you fastboot format Boot, System and Userdata before flashing, then use Google's flash-all.bat script. Battery: at 60% your battery is beyond toast and may well be contributing to your problem. You need a new battery, period. Good luck. :good:
v12xke said:
Flash full images because OTA's don't contain the full partition image. Just set up fastboot on your PC and follow Google's instructions on the page you d/l the images from. Due to using several custom ROMs, I would recommend you fastboot format Boot, System and Userdata before flashing, then use Google's flash-all.bat script. Battery: at 60% your battery is beyond toast and may well be contributing to your problem. You need a new battery, period. Good luck. :good:
Click to expand...
Click to collapse
Thank u for the how-to advice! i was a little confused with the particulars, Glad u cleared it up for me. The images are still downloading, damn the slow connection, so it'll be while before i know if it works, i'll update with the results soon.
Yes, ur spot on. i barely got 2.5 hours SOT, usually just 1.5 hours! if i can get my phone running again, im ordering a battery tomorrow as well!
Lord. Tech said:
Thank u for the how-to advice! i was a little confused with the particulars, Glad u cleared it up for me. The images are still downloading, damn the slow connection, so it'll be while before i know if it works, i'll update with the results soon. Yes, ur spot on. i barely got 2.5 hours SOT, usually just 1.5 hours! if i can get my phone running again, im ordering a battery tomorrow as well!
Click to expand...
Click to collapse
Just be sure you're clear on fastboot formatting Boot, System and Userdata. Make sure they all finish without errors. If any errors, capture the text. Important. Problem with the battery (for you) is getting a quality one. Lots of junk out there and you are located in BFE.
fastboot format boot
fastboot format system
fastboot format userdata
v12xke said:
Just be sure you're clear on fastboot formatting Boot, System and Userdata. Make sure they all finish without errors. If any errors, capture the text. Important. Problem with the battery (for you) is getting a quality one. Lots of junk out there and you are located in BFE.
fastboot format boot
fastboot format system
fastboot format userdata
Click to expand...
Click to collapse
LOL i agree, cant even get a decent internet connection out here let alone battery spare parts to a back-closed phone 95% people haven't even heard of, including the 3 repair shops i took it to the first time!! i had to google it and show them pics and videos on how to open it imagine. But since it was dead weight at the time, that botched joke surgery of my phone was still my best hope haha.
well, in other news, nothing worked i guess the phone is toast now. it just keeps freezing no matter what, stock images, 4 cores off, modified boot.img, everything. I got it in Pheonix Arizona from best buy 2 years ago when they had the 50$ off on the gold version. so cant even freaking RMA it to google! Gonna send it in for repair as a last resort, though i dont know what they can do at this point, repair cpu?
Maybe i should start looking into replacements perhaps the OP3T.... damn this is depressing.
Thanks for the help, i guess u win some, u lose some...

Android 11 - Pixel 2xl review!

Hey guys,
Since this is the last major update for our phones, I thought it will be a good idea to have a review discussion as to how Google left 2xl lines with Android 11 (I hope there is one update somewhere in future to iron out any bugs)
So! How is your phone's
1) Performance
2) Battery life
3) Sound (speaker/Bluetooth)
4) Ram management
5) Misc/Any bugs?
Let's have a discussion!
Heres my review:
Wait, its not worth it, yet
Thanks for your time
I was on it for about an hour before i noticed so many apps etc wouldnt work, and really it shouldnt have been so much of a difference that would result in so much breakage...
73sydney said:
Heres my review:
Wait, its not worth it, yet
Thanks for your time
I was on it for about an hour before i noticed so many apps etc wouldnt work, and really it shouldnt have been so much of a difference that would result in so much breakage...
Click to expand...
Click to collapse
I'm curious.. What's broke? I've been on 11 since the first beta sign-up started and didn't experience any major problems with my day to day usage. It's about the same on battery and performance as it was on 10.
Sent from my Pixel 2 XL using Tapatalk
73sydney said:
Heres my review:
Wait, its not worth it, yet
Thanks for your time
I was on it for about an hour before i noticed so many apps etc wouldnt work, and really it shouldnt have been so much of a difference that would result in so much breakage...
Click to expand...
Click to collapse
Wow that's strange. Really curious as to what is broke for you? Are those Google apps or others?
thewraith420 said:
I'm curious.. What's broke? I've been on 11 since the first beta sign-up started and didn't experience any major problems with my day to day usage. It's about the same on battery and performance as it was on 10.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Nice! I feel the smoothness has increased a bit as i found Android 11 was more smooth than 10 right from the beta phase. Although, I'm kind of disappointed in the whole. Chat bubbles doesn't seem to work and conversation is left to developers to adapt.
100rabh7791 said:
Nice! I feel the smoothness has increased a bit as i found Android 11 was more smooth than 10 right from the beta phase. Although, I'm kind of disappointed in the whole. Chat bubbles doesn't seem to work and conversation is left to developers to adapt.
Click to expand...
Click to collapse
Chat bubbles work for the Google messages app for me. I even set it so all my contacts bubble Instead of having to set each one to bubble
Sent from my Pixel 2 XL using Tapatalk
thewraith420 said:
Chat bubbles work for the Google messages app for me. I even set it so all my contacts bubble Instead of having to set each one to bubble
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Unfortunately my usage of messages is very limited. I use WhatsApp mainly for communication and it is not yet working. Although, high priority conversation shows pictures in notification which is a good addition i feel.
thewraith420 said:
I'm curious.. What's broke? I've been on 11 since the first beta sign-up started and didn't experience any major problems with my day to day usage. It's about the same on battery and performance as it was on 10.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
100rabh7791 said:
Wow that's strange. Really curious as to what is broke for you? Are those Google apps or others?
Click to expand...
Click to collapse
For one Migrate, the backup app i use and have for eons, wont restore apps/app data properly, so i would literally have to reinstall everything from scratch. Anyone want to do that for 113 apps? Considering there really isnt that much of a leap under the hood, why are apps, and even simple apps like Migrate...which uses simple scripts to restore, failing.....
There were at least 4 core apps i use that wouldnt work out of the gates. It took clearing the data for them sometimes twice to get them to work. It just turned into a lot of work. Rolled back to 10 and Migrate seamlessly worked as did every app i use.
When you can downgrade and have everything working, whats your takeaway? The upgraded OS isnt up to it yet.
Ill wait for a point release...
Also the repeated prompts to complete setup 3 times, when id already done it, got on my nerves..again, never happened on 10
It did not feel complate, felt rushed, despite however many betas they ran
Sticking with 10, and folks im usually a bleeding edger...i dont give a rats about battery and perfomance if my apps dont work...
73sydney said:
For one Migrate, the backup app i use and have for eons, wont restore apps/app data properly, so i would literally have to reinstall everything from scratch. Anyone want to do that for 113 apps? Considering there really isnt that much of a leap under the hood, why are apps, and even simple apps like Migrate...which uses simple scripts to restore, failing.....
There were at least 4 core apps i use that wouldnt work out of the gates. It took clearing the data for them sometimes twice to get them to work. It just turned into a lot of work. Rolled back to 10 and Migrate seamlessly worked as did every app i use.
When you can downgrade and have everything working, whats your takeaway? The upgraded OS isnt up to it yet.
Ill wait for a point release...
Also the repeated prompts to complete setup 3 times, when id already done it, got on my nerves..again, never happened on 10
It did not feel complate, felt rushed, despite however many betas they ran
Sticking with 10, and folks im usually a bleeding edger...i dont give a rats about battery and perfomance if my apps dont work...
Click to expand...
Click to collapse
Far different experience than I am having.. I even did a fresh install, and Google restored all 180 of my apps and put all my screens back how I had them. No aftermarket backup app needed. All I had to do was make sure my account synced before I wiped.
Sent from my Pixel 2 XL using Tapatalk
thewraith420 said:
Far different experience than I am having.. I even did a fresh install, and Google restored all 180 of my apps and put all my screens back how I had them. No aftermarket backup app needed. All I had to do was make sure my account synced before I wiped.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
1) I always clean flash, full wipe. I never dirty flash.....
2) Never used Google for backup, and never will, for starters it doesnt back up data from all apps, only apps that specifically have google backup capability built in - people do not realise that devs have cook that in. Telling people to just use google backup just garauntees theyre going to cry when they realise most of their apps do not backup app data.
So again, my issues with 11 stand
73sydney said:
For one Migrate, the backup app i use and have for eons, wont restore apps/app data properly, so i would literally have to reinstall everything from scratch. Anyone want to do that for 113 apps? Considering there really isnt that much of a leap under the hood, why are apps, and even simple apps like Migrate...which uses simple scripts to restore, failing.....
There were at least 4 core apps i use that wouldnt work out of the gates. It took clearing the data for them sometimes twice to get them to work. It just turned into a lot of work. Rolled back to 10 and Migrate seamlessly worked as did every app i use.
When you can downgrade and have everything working, whats your takeaway? The upgraded OS isnt up to it yet.
Ill wait for a point release...
Also the repeated prompts to complete setup 3 times, when id already done it, got on my nerves..again, never happened on 10
It did not feel complate, felt rushed, despite however many betas they ran
Sticking with 10, and folks im usually a bleeding edger...i dont give a rats about battery and perfomance if my apps dont work...
Click to expand...
Click to collapse
Oh well, I understand your frustration. True, Android 11 is a half baked update. I don't think apart from 2-3 features there is anything. I can consider this a feature drop than a full os upgrade.
Agreed about the Google backup it screwed my backup as well and although I didn't roll back to 10, it was quite frustrating.
Maybe you can update after the last bug update which probably will happen in December.
I'm just hoping that Google don't just stop with the security patches yet
My device never felt so complete and smooth.
Stock rooted 10 -> boot twrp.img -> dirty flash 11 ota.zip -> wipe -> first boot.
Boot twrp.img -> flash debug magic.zip, reboot.
Browse and install canary magic apk.
Only thing I think to notice is the sound seems somewhat distorted/overloaded somewhat, sometimes.
Never in calls.
Battery life and responsiveness improved. It feels less rough on the edges.
Mother_Teresa said:
My device never felt so complete and smooth.
Stock rooted 10 -> boot twrp.img -> dirty flash 11 ota.zip -> wipe -> first boot.
Boot twrp.img -> flash debug magic.zip, reboot.
Browse and install canary magic apk.
Only thing I think to notice is the sound seems somewhat distorted/overloaded somewhat, sometimes.
Never in calls.
Battery life and responsiveness improved. It feels less rough on the edges.
Click to expand...
Click to collapse
I actually felt the sound quality improved. Yes it's more responsive. I'm still testing out the battery life can't say for sure if it improved much.
I'm liking that the keyboard is so smooth now, pops up smoothly
Came from a stock rooted 10 with only TWRP and Magisk installed, was starting to notice some hiccups and slow downs in usage. Decided to clean install which I hadn't done in a while to hopefully regain some performance as well as storage. Phone feels smooth again, haven't noticed any loss of performance or stability. Can confirm that audio seems a bit tuned up, having to set all the volume sliders a bit lower.
My real comments on the process is also more with the Google backup/restore. Since I had dirty flashed basically everything throughout A10 I didn't know what to expect. While it reinstalled all the apps, resetup all the home screens with apps/widgets, wifi passwords, and saved my wallpaper. It didn't save my custom notification/ringtone sounds, bluetooth devices, notification settings (specifically which apps were silenced), and most frustratingly my tasker profiles (my fault for not remembering to back them up). Fortunately, A11 has a new rules section in the settings that can change ringer state based off wifi which is what 3/4 of my profiles did. I have only tested the feature at home so far but it worked great. Had the phone on vibrate, setup a profile that when connecting to home wifi to turn the ringer on... had it connect to wifi and it immediately turned off vibrate and turned it back on when I disconnected wifi. Should do the same thing for work, just wish it had a bluetooth state so I could make a rule for the car.
All in all I'm glad I upgraded early, even though I didn't realize ahead of time the issues with canary magisk and TWRP installed. First attempt worked great, cleaned flashed and immediately installed TWRP, setup the phone/apps, then rebooted to install magisk. This was the bootloop but as soon as I read here the two weren't compatible I was able to reflash the update to remove bootloop. Booted to TWRP to install canary magisk and Elemental Kernel and it's working perfectly so far.
Storage issue
After Android 11 update can't access android/data folder. 3rd party file managers shows access denied. Few games can't be run due to restricted storage access. Does anyone know what's wrong. Can I root Android 11 and downgrade to Android 10. If yes any guidance available online. My Pixel 2 XL is not rooted yet.
gamebond007 said:
After Android 11 update can't access android/data folder. 3rd party file managers shows access denied. Few games can't be run due to restricted storage access. Does anyone know what's wrong. Can I root Android 11 and downgrade to Android 10. If yes any guidance available online. My Pixel 2 XL is not rooted yet.
Click to expand...
Click to collapse
Your data folder was encrypted when using the previous version.
How did you upgrade?
If the bootloader is unlocked you could try booting a twrp.img to see if you can access /data.
Disable any pin you may be using before trying and if twrp asks for a password you could try default_password
Made any backups?
If the encryption key is lost you should just reformat the partitions to make the storage available again.
Maybe you can still recover the key to unlock the data if you didn't wipe it.
Mother_Teresa said:
Your data folder was encrypted when using the previous version.
How did you upgrade?
If the bootloader is unlocked you could try booting a twrp.img to see if you can access /data.
Disable any pin you may be using before trying and if twrp asks for a password you could try default_password
Made any backups?
If the encryption key is lost you should just reformat the partitions to make the storage available again.
Maybe you can still recover the key to unlock the data if you didn't wipe it.
Click to expand...
Click to collapse
Bootloader is not unlocked yet.
I updated ota. Last night got it in notification, 1.4gb update.
I did backup all data.
In Android 10 I was able to access data folder. Now data & obb folders shows empty.
Can I still unlock bootloader?
Initially I dirtyflashed what caused a show phone.
Afterwards I did a clean install and it was done, but I went back to Bliss what ist the best right now

Resources