Related
Does anyone know of a good 4.4.x ROM that still enables Webtop to function as normal? I would like to upgrade to 4.4 to hopefully get a Samsung Gear 2 to connect to the Droid 4, but not lose Webtop due to a system wipe.
Thanks in advance.
After some looking through XDA, does anyone happen to have a copy of the 4.3 Pac Man Rom? The links to that forum no longer work. From what i understand, Webtop runs from virtual slot 2, the stock Rom runs on virtual slot 1, and a custom Rom can run from another virtual slot if the bootloader is locked?
I have had some issues with my phone since unlocking with sunshine. See separate thread http://forum.xda-developers.com/droid-turbo/help/help-bricked-xt1254-unlocking-to-t3279581 for description. I have a theory about this now and would like some opinions from folks with more experience.
I used device encryption on my Turbo before the OTA update to Lollipop. After encrypting the phone I would be prompted to enter my PIN to decrypt the data partition before the phone would boot, and then I'd have to enter the PIN again after boot to unlock it. After the OTA I no longer had to enter my PIN when booting the phone, but I would still have to enter it after boot to unlock. After the OTA the phone still reported that it was encrypted in the system security settings even though it didn't need a PIN to decrypt at boot time. That makes sense from what little I know because encrypting the device re-writes the data partition, and the OTA didn't touch the data partition and could not un-encrypt it. I was baffled by this, but I didn't want to factory reset and wipe the data partition to let me re-encrypt the phone.
So after the OTA, the data partition of my phone was still encrypted, but magically the phone was able to decrypt data and boot without my PIN. I don't know why. But one clue is that after unlocking and installing TWRP I looked at TWRP log and saw a log message saying something about decrypting with default PIN. Anyway, I never wiped data, but my phone somehow manages to boot. Re-flashing system and recovery caused problems at first, but now it seems to be back to the way it was. I haven't flashed a new ROM yet, but I expect that when I do I'll have to wipe data and that will get everything back to normal.
My question is has anyone else experimented with device encryption and is this behavior expected?
Thanks.
Not having to enter a PIN with the factory image was a bug I initially discovered, and reported, during the *initial* Android L SOAK test. Needless to say, they never fixed the bug (plus one of the Stagefright CVEs) during the second SOAK rollout. I reported it then, too. They did nothing. That second SOAK was the straw that broke the camel's back, for me. I will never participate in another.
As far as this bug goes, what I would do, is an FDR, and re-encrypt your device to wipe the key store and start over.
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.
I got notifications that the SU4TL-49 OTA was ready to install on my phone, and I had read that if you try to install it with anything but stock recovery that you get into a boot loop. I figured it was a matter of time before I ended up accidentally installing the OTA upgrade and so decided to wipe my phone and go back to stock, and I would use that opportunity to re-encrypt the phone. It took me a couple of tries before I discovered that factory reset isn't enough to remove the encryption, and that I had to reformat the data partition. This took a few hours of going back and forth between reverting to stock, upgrading, rooting, configuring and starting over before I finally got it right, but eventually the phone said that it wasn't encrypted and gave me the option to encrypt. What a pain. After setting up all my apps for the third or fourth time I thought I was done. Whenever I rebooted I was prompted for my PIN before android booted. I even had to enter my PIN to run TWRP.
At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Astrobrewer said:
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Click to expand...
Click to collapse
Encryption is totally broken on CM13. The issue is that our version of TWRP cannot decrypt it. I contacted the maintainer of TWRP for our device about this issue and he said that he tried to fix the issue, but he failed.
Also, official CM13 has been out for a while now for the Turbo. No need to go with the unofficial version.
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Astrobrewer said:
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Click to expand...
Click to collapse
Just FYI, our TWRP maintainer has fixed decryption. You can get the latest version here: https://www.androidfilehost.com/?w=files&flid=39562 (version 3.0.2-0 mod 02 as of this writing). I still had trouble decrypting a partition that was previously formatted using the stock recovery menu, but once I formatted the data partition using this version of TWRP and re-encrypted, it decrypted fine.
TheSt33v said:
Just FYI, our TWRP maintainer has fixed decryption...
Click to expand...
Click to collapse
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Astrobrewer said:
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Click to expand...
Click to collapse
Most people don't seem to think it's worth the impact that it has on performance.
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Astrobrewer said:
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
TheSt33v said:
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
Click to expand...
Click to collapse
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
oldidaho said:
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
Click to expand...
Click to collapse
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
TheSt33v said:
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
Click to expand...
Click to collapse
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RR. I need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
oldidaho said:
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RRI need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
Click to expand...
Click to collapse
Well, just as you used CM13 Marshmallow and RR Marshmallow just fine without encryption, not sure why you went to CF Lollipop instead of RR just because encryption didn't work. It just seems you were implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
But it's your phone, so you can run what you want.
I do commend you for having a recent backup on your PC.
ChazzMatt said:
Well, just as you used CM13 and RR just fine without encryption, not sure why you went to CF instead of RR just because encryption didn't work. But it's your phone.
Just not sure why you are implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
I do commend you for having a recent backup on your PC.
Click to expand...
Click to collapse
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
oldidaho said:
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
Click to expand...
Click to collapse
Strange. I've been using RR M encrypted for several weeks now with no issues. Oh well. If you're happy with modified stock, that's all that matters. You can encrypt that too if you like. I'm a big fan of the Moto features as well, and RR M has basically all of them built in besides Voice (chop chop flashlight was removed for a while, but it has been added back). Although I've never understood what Voice offers that Google Now does not.
Mystery solved!
Astrobrewer said:
... At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
Click to expand...
Click to collapse
I have been running the CM13 ROM for the past few months and it's been great, but now that Verizon came out with official Marshmallow I decided to go back to a stock-based ROM again because I've been missing VOLTE. So I flashed ComputerFreak274_MM. After flashing and rooting I was back in the stupid state of the phone saying that it was encrypted but booting without a PIN. It seemed unreal that Moto/Verizon would have left this bug in MM too. So I reformatted data, re-flashed and rooted the ROM and tried encrypting. Then I discovered that it won't encrypt if it's rooted. So back to wiping, re-formatting and flashing again, but this time I am able to successfully encrypt before rooting. Success! Now root and start setting up the phone. Now I have to enter my PIN before it will boot into the system or into TWRP. Yay! By now it's 1:00am and I have to be at work early, so I let it sit overnight while my apps download. In the morning I flash SuperSU and notice that I wasn't prompted for a password to decrypt when I booted into TWRP and I wasn't prompted for password when booting system after flashing SuperSU. WTF!!! More time wasted. It seemed that stock ROMs just don't like encryption. :crying:
Anyway, after stewing about it all day I randomly chanced into the solution. In the Security settings menu there's an option under Encryption called "Secure start-up" which only becomes available when phone is encrypted. The Secure start-up options says:
"You can further protect this device by requiring your PIN before it starts up. Until the device starts up, it can't receive calls, messages, or notifications, including alarms. This helps protect data on lost or stolen devices."​Secure start-up defaults to disabled for some reason, and when it's disabled the phone automatically decrypts itself when it boots without requiring PIN entry. So you can encrypt your phone and still be totally unprotected. What a dumb-ass default!
But when I enable Secure start-up then encryption works the way it should -- with phone prompting for PIN before booting. Maybe I just didn't notice it, but I didn't see anything when I encrypted the phone saying to enable Secure start-up to actually protect the phone. I'm guessing that this option was there in Lollipop too; but who knew???
I think there are compatibility issues between Supercell games and my SD card. I'm getting SD card unexpectedly removed error when I tried to open Clash of clans. I faced the same problem before while I was playing Boom beach. I use a SanDisk Ultra MicroSDHC 16GB UHS-I Class 10 Memory Card.
skarthikpt said:
I think there are compatibility issues between Supercell games and my SD card. I'm getting SD card unexpectedly removed error when I tried to open Clash of clans. I faced the same problem before while I was playing Boom beach. I use a SanDisk Ultra MicroSDHC 16GB UHS-I Class 10 Memory Card.
Click to expand...
Click to collapse
i don't think so. i use the same SD card but a 32 GB variant and it works as flawlessly as it could. so honestly it doesn't seem like it's a compatibility issue.
Now i can advice you to troubleshoot it in this manner.
1. check when does it occur (the un-mounting message).
2. check whether it happens only on the current ROM or with the current kernels. (sometimes when your i/o options are not well tweaked as per your needs unexpected things can happen).
3. check for ROM bug fixes.
4. Try flashing another ROM like CM 12.1 latest nightly. it works flawlessly for me (as we have the same pair of hardware, might as well come handy).
5. Do a basic factory wipe i.e System, Data(Not Internal Storage), Cache, Dalvik Cache. This might aid you big time. so do not forget to wipe. but use it correctly otherwise can loose your storage in seconds.
you can try the above steps and see whether its a problem with your ROM or kernel.
if not come back for any other assistance with any unusual issue.
sanjumalik720 said:
i don't think so. i use the same SD card but a 32 GB variant and it works as flawlessly as it could. so honestly it doesn't seem like it's a compatibility issue.
Now i can advice you to troubleshoot it in this manner.
1. check when does it occur (the un-mounting message).
2. check whether it happens only on the current ROM or with the current kernels. (sometimes when your i/o options are not well tweaked as per your needs unexpected things can happen).
3. check for ROM bug fixes.
4. Try flashing another ROM like CM 12.1 latest nightly. it works flawlessly for me (as we have the same pair of hardware, might as well come handy).
5. Do a basic factory wipe i.e System, Data(Not Internal Storage), Cache, Dalvik Cache. This might aid you big time. so do not forget to wipe. but use it correctly otherwise can loose your storage in seconds.
you can try the above steps and see whether its a problem with your ROM or kernel.
if not come back for any other assistance with any unusual issue.
Click to expand...
Click to collapse
I'm on stock ROM. The message pops up exactly when I open Clash of Clans (Boom beach, few days back). I have a Moto G 2nd Gen. My device is not rooted. Is factory wipe same as Factory resetting the device? Moto G 2nd Gen is receiving Marshmallow now. I'll try again after upgrading to MM.
skarthikpt said:
I'm on stock ROM. The message pops up exactly when I open Clash of Clans (Boom beach, few days back). I have a Moto G 2nd Gen. My device is not rooted. Is factory wipe same as Factory resetting the device? Moto G 2nd Gen is receiving Marshmallow now. I'll try again after upgrading to MM.
Click to expand...
Click to collapse
did you try resetting your device? if not do it for once. it may trigger some possible issue fix. but tbh if its not into the rom it might be an issue with the hardware. so to be on a save side i recommend checking for the ROM issues manually by rooting and then installing a stable and working rom. like cm12.1 which may help you big time.
sanjumalik720 said:
did you try resetting your device? if not do it for once. it may trigger some possible issue fix. but tbh if its not into the rom it might be an issue with the hardware. so to be on a save side i recommend checking for the ROM issues manually by rooting and then installing a stable and working rom. like cm12.1 which may help you big time.
Click to expand...
Click to collapse
I am going to wait till MM update for Moto G. Also, I have requested a replacement from sandisk.
skarthikpt said:
I am going to wait till MM update for Moto G. Also, I have requested a replacement from sandisk.
Click to expand...
Click to collapse
Sandisk accepted my replacement request. They have asked me to send my SD card and they'll provide a new one it seems.
skarthikpt said:
Sandisk accepted my replacement request. They have asked me to send my SD card and they'll provide a new one it seems.
Click to expand...
Click to collapse
Very Well. Do let the community know whatever solves your issue. ciao.
I'm using EMMC CWM-based recovery v6.0.4.6 and my rom is Cyanogenmod 11-20141008-SNAPSHOT-M11-ovation.
I would love to upgrade to a faster and more stable rom if there is such a thing. I definitely don't need bleeding edge up to date stuff. I just want speed and stability. Advice appreciated, thanks!
Hi, I've tried various Marshmallow and Nougat ROMS but from my experience they are not as fluid as the CM 11 ROMs - so I've gone back to these as they do everything I need them to do (apart from using the SDCARD as internal storage).
I would be happy to hear other people's experiences though.
herges said:
Hi, I've tried various Marshmallow and Nougat ROMS but from my experience they are not as fluid as the CM 11 ROMs - so I've gone back to these as they do everything I need them to do (apart from using the SDCARD as internal storage).
I would be happy to hear other people's experiences though.
Click to expand...
Click to collapse
I finally convinced my husband to let me update his stock HD to CM 11 (the version archived at the very end of that thread). It was fine except for the need to hold in the power button to make sure it shut down, but he got used to that.
We began to run afoul of a few apps (like our local newspaper) that really wanted Lollipop or better, so I decided to take the plunge and installed the CM 12.1 in @amaces obsolete folder (and a pico GApps). For my husband, it's all good as long as the HDMI port still works
So far no complaints or odd behaviors with the CM 12.1 (same power button issue which apparently is like the poor--it will always be with us). I can't speak to relative speed (are any of these ROMs truly fast?) but it's certainly faster than AOSP 7.0 which I am running on my Nook Tablet, although I would not have known the difference if I had not been tweaking his tablet for him
So we're both happy.
Edit: oh, and that thing about using the SD card as internal storage? I got sucked into that with my AOSP 7.0. The thing is, any backup I make with TWRP is trapped on the tablet. It can't be copied off--can't even be seen outside of TWRP. It eats up at least 2 gb of space that I begrudge. I would not recommend that option and would opt for portable storage if I were setting it up again.
nmyshkin said:
I finally convinced my husband to let me update his stock HD to CM 11 (the version archived at the very end of that thread). It was fine except for the need to hold in the power button to make sure it shut down, but he got used to that.
We began to run afoul of a few apps (like our local newspaper) that really wanted Lollipop or better, so I decided to take the plunge and installed the CM 12.1 in @amaces obsolete folder (and a pico GApps). For my husband, it's all good as long as the HDMI port still works
So far no complaints or odd behaviors with the CM 12.1 (same power button issue which apparently is like the poor--it will always be with us). I can't speak to relative speed (are any of these ROMs truly fast?) but it's certainly faster than AOSP 7.0 which I am running on my Nook Tablet, although I would not have known the difference if I had not been tweaking his tablet for him
So we're both happy.
Click to expand...
Click to collapse
nmyshkin said:
Edit: oh, and that thing about using the SD card as internal storage? I got sucked into that with my AOSP 7.0. The thing is, any backup I make with TWRP is trapped on the tablet. It can't be copied off--can't even be seen outside of TWRP. It eats up at least 2 gb of space that I begrudge. I would not recommend that option and would opt for portable storage if I were setting it up again.
Click to expand...
Click to collapse
I have Nook HD for a few days so you will not be surprised by my questions.
Do you use twrp-3.0.1-0-hummingbird.zip / twrp-3.1.1-0-hummingbird.img (experimental) from amaces or twrp-3.1.1-0-hummingbird.img from twrp.me?
Is there any USB OTG or Enable MTP in the Mount menu and none of it works?
Does any of these versions have Select Storage in the Backup menu and does not work?
ze7zez said:
I have Nook HD for a few days so you will not be surprised by my questions.
Do you use twrp-3.0.1-0-hummingbird.zip / twrp-3.1.1-0-hummingbird.img (experimental) from amaces or twrp-3.1.1-0-hummingbird.img from twrp.me?
Is there any USB OTG or Enable MTP in the Mount menu and none of it works?
Does any of these versions have Select Storage in the Backup menu and does not work?
Click to expand...
Click to collapse
No, if it concerns TWRP, I am not surprised. I flashed 2.8.7.5 to emmc when I did the CM 12.1 upgrade, but did not use it. Thankfully that install can be accomplished with CWM from the SD card. I have not even looked at the TWRP, but on my Nook Tablet I have had nothing but trouble with TWRP (now 3.0.2-0 I think). You have to touch things twice--sometimes. When you touch something you often get something entirely different. Sometimes it can't see the SD card until you boot several times into recovery. I hate it. Too bad CWM just didn't keep going. I don't care about the clunky interface. What good is a touch screen UI if the result is often random?
[Vent]
This rom is OBSELETE PLEASE USE @Linux4 lineage
https://forum.xda-developers.com/ga...om-lineageos-17-1-galaxy-tab-s6-lite-t4167037
What's working or not working?
Thanks for posting this!!
c_86 said:
What's working or not working?
Thanks for posting this!!
Click to expand...
Click to collapse
Everything is working fine from what I know been using it for a week. I think restarting and turning off takes a while though. That's what I've seen
Ok great but the download link doesn't work.
Fixed
Great thanks it's working now..
It doesn't looks like we have the same version of the Galaxy Tab S6 Lite. On my European SM-P910; I already tried both of you roms and it's always a boot loop. I tried different version of the stock rom before flash (XAR) and with blank vbmeta.tar with factory reset or/and cache but it never works for me. Like the other guy for the AOSP I go back to stock.
S Pen Functionality
Hello,
I'm new so please bear with me for this question. Do S Pen functions remain after installing lineageos? I got the device yesterday and I find it to be not as snappy as I'd like.
asiancurry said:
Hello,
I'm new so please bear with me for this question. Do S Pen functions remain after installing lineageos? I got the device yesterday and I find it to be not as snappy as I'd like.
Click to expand...
Click to collapse
You guyz are lucky. There's no development for Tab s6.
Can you make a microg version?
Greetings!
I successfully managed to install the lineage rom on my SM-P610. Initially i faced infinite boot-loop even after doing a factory reset in the recovery. After some experiments, i made it work. Heres what is did to get it work.
1. First, unlock and root your device. Use the method mentioned in the other xda thread. It works.
2. Keep your rooted boot.img safe.
3. Download the lineage os tar from the thread.
4. Using 7-zip, open the tar package and delete the included boot.img fiile,
5. Replace the boot.img with the rooted boot.img obtained from the first step.
6. Flash the modded lineage package with Odin 3.14.1-3b patched under AP (do not check the re-partition in ODIN).
7. After reboot, boot into recovery and do a factory reset.
8. After a couple of reboots, Lineage logo should appear
Will write what works and what doesn't in my next post.
Thanks to @Awesomeslayerg for porting Lineage OS and AOSP to Tab s6 lite. It is really good to see a snappy lineage ROM for the device. Good Work! :highfive:
Here is the list what works and what doesn't.
The ROM is comparatively faster and snappy although the Geekbench results are identical with the stock rom. The reboot time is at par with the stock and the rom is stable. No random reboots or app crashes whatsoever.
Here are the stuff that works
Spen with pressure sensitivity works. Checked with Penup and bamboo paper app.
Can use SD card as primary storage but it is quite buggy. The apps on the SD card always crashes.
Battery backup is way better compared to stock.
Widevine is L1. Netflix HD content playback works.
Dual stereo speakers works.
Double tap to wake works as well
Comes with minimal gapps
All Bluetooth accessories work.
cts profile verification in magisk is "true".
Here is what doesn't work (or might be buggy).
The mouse pointer rather than the dot on the screen. Not sure whether there is a workaround
Magnetic flip cover doesn't work
GPS doesn't seem to work.
Cannot format SD card and use it as a portable media. upon formatting, it always shows "corrupted".
Camera is basic.
Hope you will find this info helpful.
gauthamrgramalingam said:
Thanks to @Awesomeslayerg for porting Lineage OS and AOSP to Tab s6 lite. It is really good to see a snappy lineage ROM for the device. Good Work! :highfive:
Here is the list what works and what doesn't.
The ROM is comparatively faster and snappy although the Geekbench results are identical with the stock rom. The reboot time is at par with the stock and the rom is stable. No random reboots or app crashes whatsoever.
Here are the stuff that works
Spen with pressure sensitivity works. Checked with Penup and bamboo paper app.
Can use SD card as primary storage but it is quite buggy. The apps on the SD card always crashes.
Battery backup is way better compared to stock.
Widevine is L1. Netflix HD content playback works.
Dual stereo speakers works.
Double tap to wake works as well
Comes with minimal gapps
All Bluetooth accessories work.
cts profile verification in magisk is "true".
Here is what doesn't work (or might be buggy).
The mouse pointer rather than the dot on the screen. Not sure whether there is a workaround
Magnetic flip cover doesn't work
GPS doesn't seem to work.
Cannot format SD card and use it as a portable media. upon formatting, it always shows "corrupted".
Camera is basic.
Hope you will find this info helpful.
Click to expand...
Click to collapse
Thanks alot will add this to the list
Thanks again to @Awesomeslayerg for making this rom. Here is a couple of points from my experience.
I flashed from linux using heimdall, which may be why my experience was different than @gauthamrgramalingam.
To flash I just followed the directions and, unlocked the bootloader, went to download mode a flashed. I didn't need to do all the extra steps that @gauthamrgramalingam listed. I did have to factory reset 2 times though, once from the bootloader and once from in lineage. Here are the things I've noticed:
1. Wifi doesn't seem to be working on 5g and seems to have some disconnects, also seems like I can't connect on lower bands of 2.4g, like channel 1.
2. GPS works great for me, no issues
3. Screen brightness, this is hard to confirm, but it at least SEEMS dimmer than stock firmware. I tried adjusting with the treble settings but that didn't seem to do anything.
4. netflix doesn't play videos for me at all. in info, it does show wildvine L1 or w/e and says it'll play HD but when I play a video I just get a generic error and it never plays. I've reset and reinstalled netflix to no avail.
5. SD card is weird, if I format it as portable, I run into the same issues that have been discussed, however if I format it as "phone storage" it seems to work somewhat. Can't seem to move apps to it, but I can put other files on it. Not sure whats going on.
Anyways, thanks again, I thought i would give my feedback to see if it helps.
Zeropoint said:
Thanks again to @Awesomeslayerg for making this rom. Here is a couple of points from my experience.
I flashed from linux using heimdall, which may be why my experience was different than @gauthamrgramalingam.
To flash I just followed the directions and, unlocked the bootloader, went to download mode a flashed. I didn't need to do all the extra steps that @gauthamrgramalingam listed. I did have to factory reset 2 times though, once from the bootloader and once from in lineage. Here are the things I've noticed:
1. Wifi doesn't seem to be working on 5g and seems to have some disconnects, also seems like I can't connect on lower bands of 2.4g, like channel 1.
2. GPS works great for me, no issues
3. Screen brightness, this is hard to confirm, but it at least SEEMS dimmer than stock firmware. I tried adjusting with the treble settings but that didn't seem to do anything.
4. netflix doesn't play videos for me at all. in info, it does show wildvine L1 or w/e and says it'll play HD but when I play a video I just get a generic error and it never plays. I've reset and reinstalled netflix to no avail.
5. SD card is weird, if I format it as portable, I run into the same issues that have been discussed, however if I format it as "phone storage" it seems to work somewhat. Can't seem to move apps to it, but I can put other files on it. Not sure whats going on.
Anyways, thanks again, I thought i would give my feedback to see if it helps.
Click to expand...
Click to collapse
5ghz wifi works fine for me. I wont br able to fix these issues sadly as i dont have time to research and fix. To be honest i just learned how to build a kernel from samsungs sources. But thanks for the feedback
Awesomeslayerg said:
5ghz wifi works fine for me. I wont br able to fix these issues sadly as i dont have time to research and fix. To be honest i just learned how to build a kernel from samsungs sources. But thanks for the feedback
Click to expand...
Click to collapse
I figured you wouldn't, but I thought I'd let you know. again, thanks.
---------- Post added at 07:19 PM ---------- Previous post was at 06:49 PM ----------
Awesomeslayerg said:
5ghz wifi works fine for me. I wont br able to fix these issues sadly as i dont have time to research and fix. To be honest i just learned how to build a kernel from samsungs sources. But thanks for the feedback
Click to expand...
Click to collapse
I forgot to ask, does this have root? because I was trying to do some debugging on the issues but I can't seem to get a root shell in adb.
Messing with it more, couple updates:
1. wifi 5g confirmed working.
2. netflix still not working at least for me.
Magnetic cover, might be due to SELINUX. I see this in the adb debug:
kworker/5:2: type=1400 audit(0.0:2321): avc: denied { open } for path="/sys/devices/virtual/sec/sec_key/hall_detect" dev="sysfs" ino=45321 scontext=u:r:kernel:s0 tcontext=ubject_r:sysfs:s0 tclass=file permissive=0
the magnetic cover might use the hall sensor, but not sure. There is another sensor that is getting AVC denied as well. Worth a look.
Awesomeslayerg said:
If it doesnt boot or bootloops thanks @gauthamrgramalingam
1. First, unlock and root your device. Use the method mentioned in the other xda thread. It works.
Click to expand...
Click to collapse
Which thread? Can someone link it?
Someone and I are working on a TWRP and Lineage nom-gsi version at the moment so stay tuned!!
Awesomeslayerg said:
Someone and I are working on a TWRP and Lineage nom-gsi version at the moment so stay tuned!!
Click to expand...
Click to collapse
awesome, let me know if you need any help.