I saw scrolling through the unofficial pixel expirence rom page and seen Somone state how AOSP ROMS don't work on Verizon but CAF roms do. It's this True?
Long story short I was working at TMobile and now lost the amazing employee discount I had because I got a better job. Now everyone on the plan wants to go back to Verizon and we are and I'm just trying to research how this device work on Verizon being a LTE only device (CDMA-Less)
I'm using lineageos on Verizon with pulse SMS just fine
clapper66 said:
I saw scrolling through the unofficial pixel expirence rom page and seen Somone state how AOSP ROMS don't work on Verizon but CAF roms do. It's this True?
Long story short I was working at TMobile and now lost the amazing employee discount I had because I got a better job. Now everyone on the plan wants to go back to Verizon and we are and I'm just trying to research how this device work on Verizon being a LTE only device (CDMA-Less)
Click to expand...
Click to collapse
Alright, so I have this 6T that I'm not enthralled with due to significant drawbacks (on Verizon specifically) that preclude my typical flashaholism.
The drawbacks actually compound each other, culminating in a frustrating custom ROM experience:
1. Device encryption: unlike Samsung, whole device decryption is not supported. That means that various months' security patches prevent simple flashing without formatting internal storage.
For example, RomA has April security patches, so you cannot flash any Rom with March security patches because the data partition is encrypted with April specifications. To flash a Rom with earlier security patches, you MUST format your internal storage, wiping out all downloads, photos , etc stored there. Which wouldn't be as cumbersome if there was an external SD card built in that you could simply copy stuff from...but there isn't.
2. No external SD card: means that when you format internal storage (which will happen more often than you would think due to device encryption and A/B slots), there's no handy way to recover your wiped stuff. I'm carrying around a thumb drive, for crying out loud.
3. A/B slots: you have to keep track of what rom and oos version you are running on each slot. Furthermore, flashing any rom now includes multiple additional steps and inter-flash reboots to work properly. Even experienced flashers will need to backup their device to external storage devices (thumb drive, because no external SD card) due to this unnecessary complexity.
Finally, on VZW, there isn't a custom ROM available as I write this that has full MMS capabilities. Only Liquid, Havoc, and AOSiP can use MMS and even then it's limited to only jpg under 800kb.
In other words, I'm already potentially plotting my next phone as a Moto z4 force...
I have a developer friend who made his android 11 rom work on my oneplus 6t with verizon. If you're curious it's Kang OS...
reaper000 said:
Alright, so I have this 6T that I'm not enthralled with due to significant drawbacks (on Verizon specifically) that preclude my typical flashaholism.
The drawbacks actually compound each other, culminating in a frustrating custom ROM experience:
1. Device encryption: unlike Samsung, whole device decryption is not supported. That means that various months' security patches prevent simple flashing without formatting internal storage.
For example, RomA has April security patches, so you cannot flash any Rom with March security patches because the data partition is encrypted with April specifications. To flash a Rom with earlier security patches, you MUST format your internal storage, wiping out all downloads, photos , etc stored there. Which wouldn't be as cumbersome if there was an external SD card built in that you could simply copy stuff from...but there isn't.
2. No external SD card: means that when you format internal storage (which will happen more often than you would think due to device encryption and A/B slots), there's no handy way to recover your wiped stuff. I'm carrying around a thumb drive, for crying out loud.
3. A/B slots: you have to keep track of what rom and oos version you are running on each slot. Furthermore, flashing any rom now includes multiple additional steps and inter-flash reboots to work properly. Even experienced flashers will need to backup their device to external storage devices (thumb drive, because no external SD card) due to this unnecessary complexity.
Finally, on VZW, there isn't a custom ROM available as I write this that has full MMS capabilities. Only Liquid, Havoc, and AOSiP can use MMS and even then it's limited to only jpg under 800kb.
In other words, I'm already potentially plotting my next phone as a Moto z4 force...
Click to expand...
Click to collapse
Dude I am sorry but using any phone other than oneplus 6t is just ludicrous to me. Encrypted format data in recovery oh all gone. A/B slots only have to worry about that if you're dual booted and you're not. Me I am running colt & kang on mine. This phone is freaking awesome get enough space you don't need sd card.
reaper000 said:
Alright, so I have this 6T that I'm not enthralled with due to significant drawbacks (on Verizon specifically) that preclude my typical flashaholism.
The drawbacks actually compound each other, culminating in a frustrating custom ROM experience:
1. Device encryption: unlike Samsung, whole device decryption is not supported. That means that various months' security patches prevent simple flashing without formatting internal storage.
For example, RomA has April security patches, so you cannot flash any Rom with March security patches because the data partition is encrypted with April specifications. To flash a Rom with earlier security patches, you MUST format your internal storage, wiping out all downloads, photos , etc stored there. Which wouldn't be as cumbersome if there was an external SD card built in that you could simply copy stuff from...but there isn't.
2. No external SD card: means that when you format internal storage (which will happen more often than you would think due to device encryption and A/B slots), there's no handy way to recover your wiped stuff. I'm carrying around a thumb drive, for crying out loud.
3. A/B slots: you have to keep track of what rom and oos version you are running on each slot. Furthermore, flashing any rom now includes multiple additional steps and inter-flash reboots to work properly. Even experienced flashers will need to backup their device to external storage devices (thumb drive, because no external SD card) due to this unnecessary complexity.
Finally, on VZW, there isn't a custom ROM available as I write this that has full MMS capabilities. Only Liquid, Havoc, and AOSiP can use MMS and even then it's limited to only jpg under 800kb.
In other words, I'm already potentially plotting my next phone as a Moto z4 force...
Click to expand...
Click to collapse
Do you know of a easy method that I can keep track of what ROM and OOS version I am running on each slot short of using fastboot commands and booting into each slot?
rodken said:
Do you know of a easy method that I can keep track of what ROM and OOS version I am running on each slot short of using fastboot commands and booting into each slot?
Click to expand...
Click to collapse
Sorry, but I don't.
Although I am rooted, the absence of twrp for my current device (pixel 6 pro) has left me at stock. Sigh.
Related
Is it possible to boot the HTC HD2 into android (no particular version, at least ICS) using an encrypted SD card, I want to use the phone for going on activist rally's and filming police etc, I'd like no trace to be left on the hardware of the device, only the SD card which can be easily swallowed, tossed or destroyed, the SD card would be a class 10 and I would like to have to enter a password to decrypt the card before it booted.
Theoretically anything is possible, but is this possible with currently available tools or would this be something I would have to create from scratch, I do not want to re-invent the wheel
Thoughts?
I am not going to argue politics here btw, I'm purely looking for technical responses.
davidcampbell said:
Is it possible to boot the HTC HD2 into android (no particular version, at least ICS) using an encrypted SD card, I want to use the phone for going on activist rally's and filming police etc, I'd like no trace to be left on the hardware of the device, only the SD card which can be easily swallowed, tossed or destroyed, the SD card would be a class 10 and I would like to have to enter a password to decrypt the card before it booted.
Theoretically anything is possible, but is this possible with currently available tools or would this be something I would have to create from scratch, I do not want to re-invent the wheel
Thoughts?
I am not going to argue politics here btw, I'm purely looking for technical responses.
Click to expand...
Click to collapse
I don't think it would be possible to make android boot FROM the SD card while it's encrypted. Mainly because I think you'd have to have to decrypt the sd card before allowing the device to access the system files. (But I could be wrong, I'm only assuming here). (Maybe there's a way to do modifications to the "wheel" so that the card is decrypted just for system initiation. Or maybe decrypt only one part of the SD-card that contains the system and encrypt other partitions?) You need someone with knowledge to answer all of this ... And that's not me unfortunately.
On the other hand, you can install the system on NAND. Pick a small ROM so you don't have to use a2sd or any kind of script that is SD-card reliant. Then I think it would be possible to use an encrypted SD card. (Although I think Android still uses the sdcard for apps' data storage ...)
Sorry, I couldn't be of much help
So I finally made the leap from Lollipop to Marshmallow. Everything has been going fine for the most part, but I've hit a huge snag: moving apps to SD.
I use Titanium Backup to keep a full backup of my phone on the external SD card. I depend on this backup for two purposes:
1) it makes updating the ROM (like this time) a lot easier. I do a factory reset, get the base Android going, re-install Titanium Backup from the Play Store, point it to my backups on the external SD card, and then I'm good to restore (either full app+data if that's safe, or I first re-install the app from the Play Store then just restore the app's data using TB).
2) It saves my butt in the event of a phone hardware failure, which has happen several times over my many years as an Android user. I just buy a replacement phone, move the SD card over, and restore my apps/data in a similar manner as in #1.
I have a Galaxy S5 with 16GB of internal storage, which is certainly not enough so I depend on my 64GB external SD card greatly. Between keeping all my large media on the external SD, as well as moving what large apps to SD as I can, this has been fine. I use Bliss ROM.
So make the jump from Android 5 -> 6, and finally get to the point where I need to move some of the apps I've restored to SD... but can't find the option. I do some research, and now am in a panic. From what I can tell, you can only move apps to SD if you use the SD as adopted/internal storage, which means it gets re-formatted, encrypted, and can only be used with that phone. This eliminates the possibility of #1 & #2 above. To continue performing #1 & #2, I need to use the SD as "portable storage" (the way it is now), which apparently leaves no way to move apps to SD.
I am in a pickle now, and feel stuck. I'm hoping I'm missing another option. Help?
sremick said:
So I finally made the leap from Lollipop to Marshmallow. Everything has been going fine for the most part, but I've hit a huge snag: moving apps to SD.
I use Titanium Backup to keep a full backup of my phone on the external SD card. I depend on this backup for two purposes:
1) it makes updating the ROM (like this time) a lot easier. I do a factory reset, get the base Android going, re-install Titanium Backup from the Play Store, point it to my backups on the external SD card, and then I'm good to restore (either full app+data if that's safe, or I first re-install the app from the Play Store then just restore the app's data using TB).
2) It saves my butt in the event of a phone hardware failure, which has happen several times over my many years as an Android user. I just buy a replacement phone, move the SD card over, and restore my apps/data in a similar manner as in #1.
I have a Galaxy S5 with 16GB of internal storage, which is certainly not enough so I depend on my 64GB external SD card greatly. Between keeping all my large media on the external SD, as well as moving what large apps to SD as I can, this has been fine. I use Bliss ROM.
So make the jump from Android 5 -> 6, and finally get to the point where I need to move some of the apps I've restored to SD... but can't find the option. I do some research, and now am in a panic. From what I can tell, you can only move apps to SD if you use the SD as adopted/internal storage, which means it gets re-formatted, encrypted, and can only be used with that phone. This eliminates the possibility of #1 & #2 above. To continue performing #1 & #2, I need to use the SD as "portable storage" (the way it is now), which apparently leaves no way to move apps to SD.
I am in a pickle now, and feel stuck. I'm hoping I'm missing another option. Help?
Click to expand...
Click to collapse
From what I've read there is a method for app2sd to work with mm. I never had success with it though, and downgraded to ll.
ldeveraux said:
From what I've read there is a method for app2sd to work with mm. I never had success with it though, and downgraded to ll.
Click to expand...
Click to collapse
A method other than formatting the card as internal/adopted storage? Did the method involve setting up multiple partitions?
While I could set up a FAT32 partition just for TB, then adopt the rest, my backups aren't the only thing I've needed to access after popping out the SD card. For example, just being able to load media that way is quick and sometimes a life-saver. I've also used that as a way to get zip files on that I could then flash via recovery. I'm also not clear if you can "mount" adopted storage as USB while in recovery so it's visible to the computer as a USB mass-storage device while the phone is connected via USB cable (as you have been able to do normally up to this point).
sremick said:
A method other than formatting the card as internal/adopted storage? Did the method involve setting up multiple partitions?
While I could set up a FAT32 partition just for TB, then adopt the rest, my backups aren't the only thing I've needed to access after popping out the SD card. For example, just being able to load media that way is quick and sometimes a life-saver. I've also used that as a way to get zip files on that I could then flash via recovery. I'm also not clear if you can "mount" adopted storage as USB while in recovery so it's visible to the computer as a USB mass-storage device while the phone is connected via USB cable (as you have been able to do normally up to this point).
Click to expand...
Click to collapse
I'm not the app developer, I have no clue how/if it works. It didn't for me, but did for many others. Go to that thread and read up!
ldeveraux said:
I'm not the app developer, I have no clue how/if it works. It didn't for me, but did for many others. Go to that thread and read up!
Click to expand...
Click to collapse
Which app/thread are you referring to? Or are you talking about Bliss ROM itself? I didn't post in that thread, as this issue seems generically Marshmallow-related, and not specific to Bliss.
sremick said:
Which app/thread are you referring to? Or are you talking about Bliss ROM itself? I didn't post in that thread, as this issue seems generically Marshmallow-related, and not specific to Bliss.
Click to expand...
Click to collapse
It's a marshmallow problem, not Rom specific. In xda's app section there are threads for both link2sd (not working) and app2sd (works for some). Check those, I think that's where I saw the info.
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
sremick said:
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
Click to expand...
Click to collapse
I think the consensus was to use NotifyClean (Xposed module) to eliminate that message at boot. :good: Everything still working for you otherwise? I was thinking of upgrading now, and think this might work too:
http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html
sremick said:
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
Click to expand...
Click to collapse
Is f2fs and exfat supported by stock MM in Apps2SD? Got it formatted with fat32 and ext4.
ldeveraux said:
I think the consensus was to use NotifyClean (Xposed module) to eliminate that message at boot
Click to expand...
Click to collapse
Ugh. I do not want to have to use Xposed.
Everything still working for you otherwise?
Click to expand...
Click to collapse
Well it was working just great... then I rebooted. Apparently some trouble getting the 2nd partition (fsfs, where the apps are being moved to) to mount at boot. Trying to sort it out in this thread:
http://forum.xda-developers.com/android/apps-games/apps2sd-partition-sd-card-link-apps-to-t3122919
andacro said:
Is f2fs and exfat supported by stock MM in Apps2SD?
Click to expand...
Click to collapse
No idea, I never run stock.
I bought myself a new yoga plus LTE yesterday.
I've been working on the big file issue with larger files than 4gb on sdcard.
I fixed that issue by formatting the card as a internal drive and move all apps there.
The thing i dont like is that i lost all the 32GB on ghe original drive as that wont show up anymore as a usable space.
On my friends tab his internal and card got put togheter and he got one large drive containing both the card and the internal storage. (Lenovo tab 3 x50 i believe)
So my tablet seems slow, it hangs on Facebook and messenger and it disconnects wifi etc.
Its buggy...
So, i just recently had a Nvidia shield tablet and it was also slow, so i downloaded the stock rom and adb flashed it with recovery flash and it became superfast again.
I believe after updates some files gets overwritten and it causes problems.
Normal factory reset wont fix it either.
It needs reflashing..
So here is my questions.
I need stock recovery files, and then i also would like to root it so i can get to use my internal drive as internal and to have a Exfat sdcard to be recognized do i also need to know how to get there as well.
Im sure this tablet after full recovery with latest updates, a exfat support will be very nice.
I also maybe need TWRP to flash it with the files needed to get it to read exfat??
I don't wanna return it as i like it but it only needs exfat for me to be perfect.
Please help me out so i can collect all files with links and to have some tutorials of Wich to do first etc.
I will then make a good thread containing all these so we all can enjoy the best of this nice tablet that really gets killed by not recognizing exfat.
I mean i like to have 4K material and i dont wanna be limited by Lenovo beeing to poor to buy the exfat license.
Its been a Lenovo issue for many years i cant understand why they wont fix it.
My tablet is the YT-X703L
MANY THANKS ALL OF YOU BEAUTIFUL PEOPLE!!
veralynn said:
I bought myself a new yoga plus LTE yesterday.
I've been working on the big file issue with larger files than 4gb on sdcard.
I fixed that issue by formatting the card as a internal drive and move all apps there.
The thing i dont like is that i lost all the 32GB on ghe original drive as that wont show up anymore as a usable space.
On my friends tab his internal and card got put togheter and he got one large drive containing both the card and the internal storage. (Lenovo tab 3 x50 i believe)
So my tablet seems slow, it hangs on Facebook and messenger and it disconnects wifi etc.
Its buggy...
So, i just recently had a Nvidia shield tablet and it was also slow, so i downloaded the stock rom and adb flashed it with recovery flash and it became superfast again.
I believe after updates some files gets overwritten and it causes problems.
Normal factory reset wont fix it either.
It needs reflashing..
So here is my questions.
I need stock recovery files, and then i also would like to root it so i can get to use my internal drive as internal and to have a Exfat sdcard to be recognized do i also need to know how to get there as well.
Im sure this tablet after full recovery with latest updates, a exfat support will be very nice.
I also maybe need TWRP to flash it with the files needed to get it to read exfat??
I don't wanna return it as i like it but it only needs exfat for me to be perfect.
Please help me out so i can collect all files with links and to have some tutorials of Wich to do first etc.
I will then make a good thread containing all these so we all can enjoy the best of this nice tablet that really gets killed by not recognizing exfat.
I mean i like to have 4K material and i dont wanna be limited by Lenovo beeing to poor to buy the exfat license.
Its been a Lenovo issue for many years i cant understand why they wont fix it.
My tablet is the YT-X703L
MANY THANKS ALL OF YOU BEAUTIFUL PEOPLE!!
Click to expand...
Click to collapse
Regarding the slow down, flashing an image won't help you there because you will end up with exactly the same system that you have now. This is due to the block based updates. We all have exactly the same system and boot partitions. The only thing you can do is a factory reset
The exfat issue is big annoyance I agree. It's only half Lenovo's fault though. Microsoft is the bad guy here since they conspired to get the exfat file system set as the default file system for large SD cards and want royalties from the OEMs. I don't want Microsoft to get a single dime for something as trivial as a new file system without any special features.
What is Lenovo's fault is giving us old kernel sources that prevent us from easily building custom kernels that include exfat. There were FUSE based solutions for older Lenovo tablets that could potentially be updated to work for us but FUSE isn't ideal since it's slower than a kernel based solution.
Version number "BLU_R0010UU_V8.7_GENERIC_6.0_20170805-1450"
Version size
25.04 MB
Release date
2017-08-05
Where can we verify this?
I received this Sept 13th 2017.
I received too.
Here is the link
Xttps://drive.google.com/file/d/0B7F40Ha8ULj7RGw3bk1OWUpIWDQ/view?usp=drivesdk
Change "X" for "H"
LordDandy said:
Version number "BLU_R0010UU_V8.7_GENERIC_6.0_20170805-1450"
Version size
25.04 MB
Release date
2017-08-05
Where can we verify this?
I received this Sept 13th 2017.
Click to expand...
Click to collapse
What is it you want to verify?
If just that there is an update out , yes there is. The notes say includes android security patches.
Patched TWRP installl-able version will up soon.
Is this the one that just showed up in my auto-update? (09/13/17 on 6:00PM Central time).
If so, it broke my phone, I can't use my microSD card anymore. I can see all the data, but the apps don't show up in my list, I can't update them from the google store, I can't run them except from google store IF it recognizes they are installed, and I can't transfer them to internal storage.
My time is wrong, and my phone keeps rebooting when I try to run my apps.
mrmazak said:
What is it you want to verify?
If just that there is an update out , yes there is. The notes say includes android security patches.
Patched TWRP installl-able version will up soon.
Click to expand...
Click to collapse
Awesome! I'll be waiting. Thanks for the quick update.
KyleStilkey said:
Awesome! I'll be waiting. Thanks for the quick update.
Click to expand...
Click to collapse
I uploaded V8.7 to the stock rom thread.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
I did not debloat or remove ads from 8.7
if you want the rom debloated you can run this command while in twrp with system set to mounted.
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
mrmazak said:
What is it you want to verify?
If just that there is an update out , yes there is. The notes say includes android security patches.
Patched TWRP installl-able version will up soon.
Click to expand...
Click to collapse
mrmazak said:
I uploaded V8.7 to the stock rom thread.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
I did not debloat or remove ads from 8.7
Click to expand...
Click to collapse
Will we see a debloat/removed ads version?
LordDandy said:
Version number "BLU_R0010UU_V8.7_GENERIC_6.0_20170805-1450"
Version size
25.04 MB
Release date
2017-08-05
Where can we verify this?
I received this Sept 13th 2017.
Click to expand...
Click to collapse
I got the same one about the same date, proceeded to install it (after backing up whatever I could). It installed problem-free (I had about 1.5 GB of my 16 GB free, for what it's worth). Almost a week later, the phone is functioning as well as before (no speedup/slowdown/flaky behaviour). The only new feature is the automatic installation of Google Play Protect that automatically scans Apps periodically for who-knows-what (didn't complain about any of my 103 Apps, so it's not super-aggressive).
Terrabull said:
Is this the one that just showed up in my auto-update? (09/13/17 on 6:00PM Central time).
If so, it broke my phone, I can't use my microSD card anymore. I can see all the data, but the apps don't show up in my list, I can't update them from the google store, I can't run them except from google store IF it recognizes they are installed, and I can't transfer them to internal storage.
My time is wrong, and my phone keeps rebooting when I try to run my apps.
Click to expand...
Click to collapse
I'm having many of the same issues, they seem to revolve around the microSD card. For some reason after the update my phone can't seem to access it or the app data stored there. Many of my apps were on my SD card so they're affected. I'm so annoyed I'm about to factory reset my phone to see if that helps. I've reported it to Blu but haven't heard anything.
Any suggestions on how to fix it w/o the factory reset? Thanks!
My guess is that the new update implemented more "security features." Since Google, in its not-so-infinite wisdom, considers SD cards to be inherently insecure, and Apps have become more and more difficult to store on SD cards with recent generations of Android, it is perhaps not so surprising that whatever limited possibility there was of installing Apps on the SD card before was removed with this update, causing the aforementioned problems. Especially for those who have the essentially useless 8 GB version of the R1 HD, which has only 3 GB or so available for Apps, this is not going to be good news.
I don't think a factory reset will help either (since it won't restore to the previous version of Android). The best that can be done is to save your important App data on the SD card by copying its contents onto a computer, then judiciously delete Apps that you don't need and reinstall them on the main memory and manually copy over the App data.
This is speculation, but it would be consistent with my own experiences on previous upgrades on earlier phones (the Blu Life One), where SD card usage for Apps became more and more problematic.
Or upgrade to a phone with more internal memory if you really can't find enough Apps to delete (I know that's not the point of this thread, but I think for the 8 GB R1 HD owners, that day will come sooner rather than later). Nowadays, 16 GB is the minimum for even light users, what with the the OS taking up the better part of 8 GB, and Apps like Whatsapp having no way to store their files, not even space-hogging media files, on the SD card.
Something similar happened to my phone with their spring update. Enough people had similar issues that Blu enabled people to roll it back. I wonder if the issues are related?
Also, I can' t update apps from the play store or download new ones.
tanguero8 said:
My guess is that the new update implemented more "security features." Since Google, in its not-so-infinite wisdom, considers SD cards to be inherently insecure, and Apps have become more and more difficult to store on SD cards with recent generations of Android, it is perhaps not so surprising that whatever limited possibility there was of installing Apps on the SD card before was removed with this update, causing the aforementioned problems. Especially for those who have the essentially useless 8 GB version of the R1 HD, which has only 3 GB or so available for Apps, this is not going to be good news.
I don't think a factory reset will help either (since it won't restore to the previous version of Android). The best that can be done is to save your important App data on the SD card by copying its contents onto a computer, then judiciously delete Apps that you don't need and reinstall them on the main memory and manually copy over the App data.
This is speculation, but it would be consistent with my own experiences on previous upgrades on earlier phones (the Blu Life One), where SD card usage for Apps became more and more problematic.
Or upgrade to a phone with more internal memory if you really can't find enough Apps to delete (I know that's not the point of this thread, but I think for the 8 GB R1 HD owners, that day will come sooner rather than later). Nowadays, 16 GB is the minimum for even light users, what with the the OS taking up the better part of 8 GB, and Apps like Whatsapp having no way to store their files, not even space-hogging media files, on the SD card.
Click to expand...
Click to collapse
I think you're right about the SD card. I did the reset and while it fixed most of my problems I still can't access the sd card so it's useless.
I have had my 32GB (HC Class 10) mSD card corrupted each time updating/clean install newer R1 HD rom - making it unreadable & unusable, getting the prompt to reformat it again for use.
I run my most recent V8.5 modified stock Rom rooted and fairly lean, so there's enough space on the R1 HD (16GB) rom to keep all the Apps on it, without moving them over. Only storing documents, PDF's, photos/images and MP4's on it - using it as my backup/travel phone, etc.
Doing my setup now to prep for updating to latest V8.7 rom, debloating it & planning to run Xposed modules on it again, taking out my mSD card first and will re-insert once the new Rom is done & settled down, let's see how it go ... rather take a few extra minutes to do this instead of moving the contents around or copying them over again, etc.
I did the same thing and only use the sd card for storage for audio books and music files. I updated the phone the other night from the first version of the ROM to 8.7 and the only annoying thing I have noticed so far is that it no longer responds to "ok google" when the screen is off and the phone is being charged. It used to respond before the update. I don't know if this was a Blu-specific change or if it affected all versions of Android. Xposed works fine on 8.7 and I'm glad that I bought the donate version so I was able to save and restore all of the many changes I made to settings in Xposed. It's such great software that the guy deserves to make some money for all his work.
Moving apps to the sd card on previous phones has always been fragile and ended up having issues so I don't even attempt it any more. I just decided to keep only the stuff I really need on the phone.
I want to use a SD card as internal storage on my SM-T580 tablet. I have tried using the ADB Shell commands to set up a 32 GB SD card as 50% internal and 50% external, but I can’t seem to get it to work. I also tried an automated procedure forum here: (https://forum.xda-developers.com/android/software/auto-formatting-sdcard-to-internal-t3583875). This automated procedure seems to be working for others, but not me on my device. I also tried the manual procedure and automated procedure on my Samsung Galaxy S7 (SM-G930V), with no luck either.
Has anyone done this successfully on a Samsung SM-T580 tablet (Android 7 Nougat) and /or a Samsung Galaxy S7 (SM-G930V) (Android 8 Oreo)? Thanks for any help.
migoblu said:
I want to use a SD card as internal storage on my SM-T580 tablet. I have tried using the ADB Shell commands to set up a 32 GB SD card as 50% internal and 50% external, but I can’t seem to get it to work. I also tried an automated procedure forum here: (https://forum.xda-developers.com/android/software/auto-formatting-sdcard-to-internal-t3583875). This automated procedure seems to be working for others, but not me on my device. I also tried the manual procedure and automated procedure on my Samsung Galaxy S7 (SM-G930V), with no luck either.
Has anyone done this successfully on a Samsung SM-T580 tablet (Android 7 Nougat) and /or a Samsung Galaxy S7 (SM-G930V) (Android 8 Oreo)? Thanks for any help.
Click to expand...
Click to collapse
If I am not mistaken that feature has been removed by Samsung on the stock firmware for the T580. If I remember when I google it I found something talking about rooting your tablet and instaling a custom boot imge. They way I got it to work was just by installing a custom rom like Lineage OS.
Take a look at this: (looks like it is only for MM)
https://forum.xda-developers.com/galaxy-tab-a/how-to/samsung-galaxy-tab-10-1-sm-t580-t3659774
Hope this helps.
Thanks, srgrusso. I guess Samsung wants us to buy newer higher capacity devices. I discovered on my Galaxy S7 that triggering Developer Options allowed me to transfer most of the apps to the SD card. So, I think that will suffice for the present, and when I pay off both the SM-T580 and SM-G930V then I will root them. Thanks for the link. Will just rooting the devices allow me to gain the ability to use a SD card as internal storage, or will I also have to install a custom ROM?
migoblu said:
Thanks, srgrusso. I guess Samsung wants us to buy newer higher capacity devices. I discovered on my Galaxy S7 that triggering Developer Options allowed me to transfer most of the apps to the SD card. So, I think that will suffice for the present, and when I pay off both the SM-T580 and SM-G930V then I will root them. Thanks for the link. Will just rooting the devices allow me to gain the ability to use a SD card as internal storage, or will I also have to install a custom ROM?
Click to expand...
Click to collapse
I never did understand why Samsung makes us pay such high prices for average devices full of bloat with next to nothing for storage space. I would recommend a custom ROM unless you like the stock firmware. After I installed my custom ROM I found that I didn't really need the adoptable storage because I gained a couple of gigs of space back do to the fact that I lost all the bloat and bs of the stock firmware. The stock firmware is ridiculously huge and a space hog. I don't know for sure but I think you would still have to patch the stock firmware. I also seen people mention an app called App2SD I don't know much about it though. Here is a link to the XDA thread https://forum.xda-developers.com/android/apps-games/apps2sd-partition-sd-card-link-apps-to-t3122919. There are a couple of drawbacks of adoptable storage. One is speed. You nead to make sure you have a fast sd card. Another is that most sd cards will burn out quickly being used as adoptable storage. Here is a good article about that https://www.androidcentral.com/adoptable-storage.
srgrusso said:
I never did understand why Samsung makes us pay such high prices for average devices full of bloat with next to nothing for storage space. I would recommend a custom ROM unless you like the stock firmware. After I installed my custom ROM I found that I didn't really need the adoptable storage because I gained a couple of gigs of space back do to the fact that I lost all the bloat and bs of the stock firmware. The stock firmware is ridiculously huge and a space hog. I don't know for sure but I think you would still have to patch the stock firmware. I also seen people mention an app called App2SD I don't know much about it though. Here is a link to the XDA thread https://forum.xda-developers.com/android/apps-games/apps2sd-partition-sd-card-link-apps-to-t3122919. There are a couple of drawbacks of adoptable storage. One is speed. You nead to make sure you have a fast sd card. Another is that most sd cards will burn out quickly being used as adoptable storage. Here is a good article about that https://www.androidcentral.com/adoptable-storage.
Click to expand...
Click to collapse
Thanks for the info and the links. I found some instructions that allow me to transfer some apps to the SD card in my Samsung Galaxy S7 (SM-G930V). The instructions are to enable Developer Options, by tapping on the Build Number 7 times, when Developer is enabled, then go to Developer Options, and enable "force allow apps on external ". This has allowed me to gain about 5 GB of internal storage. I think that this will help me until I root the phone and install a custom ROM. Thanks for all your advice and help.
migoblu said:
Thanks, srgrusso. I guess Samsung wants us to buy newer higher capacity devices.
Click to expand...
Click to collapse
Absolutely nothing to do with that and neither does that statement make sense.
Samsung STILL release low capacity budget devices. It wouldn't make sense to release them if they didn't want people to buy them.
Samsung are simply trying to cater for all corners of the market, from budget to Flagships.
Samsung had good reason to remove adoptable storage and in part agree with the decision. However I don't believe it should have been removed entirely, the choice should have been the consumers with a clear stern warning if it used.
The reason?
Basically performance.
Adoptable storage relies on much slower memory.
Samsungs internal NAND memory is way faster read and certainly write than any SD CARD/ flash media.
Even Samsung budget devices use high performance NAND memory.
From Samsungs point of view it would be pointless releasing a device, especially a flagship, with high performance specs and then bottle neck it with relatively slow memory.
All that would happen is that all over the web and forums there'd be people whinging and whining about the performance of their device and how slow it is. Particularly the gaming community and those with higher spec devices.
There'd be countless calls to Samsung support by people questioning the performance of their devices.
It boils down to the fact that many people do not understand what adoptable storage is and how it works.
I created the adoptable storage patch because I believe people should be given the choice. However I don't recommend using it.
I certainly don't, I just manage my storage better.
There's no point in whinging about how much storage capacity the device has.
It's all there in the specs before anyone buys the device.
Yes I agree there is far too much bloat in some of Samsungs roms and this wastes capacity.
However Samsung are learning and Tbh they've slimmed down TouchWiz alot in recent OS releases.
I did it on my Redmi Note 8T 32GB. Just flash the ZIP file which I attached here in Recovery and then you will be able to format SD card as Internal Storage.
*** If it is not working, you must need to FORMAT DATA to delete the encryption, so before of that - make a backup of all your files ***
I tested it on Android 13 and it is working perfectly.
Then you can use for example an app: APP2SD (https://play.google.com/store/apps/details?id=in.co.pricealert.apps2sd) from Google Play to move apps to adopted storage (SD CARD)