Develop Bugs

Can't flash newer roms

Alright guys, I did quite a bit of research. Basically all roms before 6.5.1 flash just fine. But, only a very select few with 6.5.1 and the newest manilla, seem to flash with error. This is all just so odd.
You name it, I have tried it. On two pc's, and flashing from the microSD card, and yes I formatted the card to FAT32 first.
Flashing from the pc and microSD card always results precisely the same with every rom. This tells me that there is absolutely no doubt that it is, the phone itself...
I flashed the first version of HARDspl, both manual and automatic, and did the same with the latest version of hardspl. I have tried more combination's of roms and radios than I can even recall.
After some researching of the, flash error code 226, I read more than a few people stating that similar problems were the result of an inability to write to the Extended ROM in the phones flash memory. I guess its also called ExtROM.
This made sense to me because ALL of the rom flashes that fail, do so in the last 94-99%. This obviously tells me that the error is in the last bit of info attempting to be written to the device.
Basically I am stuck. No idea how to flash the newer roms, specifically the EnergyROMS.
Help?

Does anyone have any advice?

Okay this is weird. I can flash any newer rom that has TF3D 2.1 but only a select few that have 2.5xx. Weird right?
Seriously? No one has any advice for me? I am really held back by this, I love this forum and I love trying new roms.
I guess I have covered all bases and no one knows what to say...
It seems like a portion of my TP2's primary partition is damaged somehow...
I dont know how to rewrite over that, I have tried two different T-Mobile stock roms with their appropriate radios. I always do a hard reset after every flash.
Any input please? Even if you have no advice just some response would be great, thanks.

ALL AOSP Roms FAIL, Help

I don't post here often, but I am on IRC all the time for those of you that do know me. I have been having serious issues with the AOSP Roms. Cyanogen, Ruby, and Incredible Does all either freeze on me or reboot sooner or later. I've went so far as to install nothing else except the Rom and it still freezes or reboots. I've done this test with all three, I even dialed down the processor while on them and still NO DICE. I'm not an Android expert, but I do have a bachelor's in IT so I feel I'm pretty tech savvy. I was told on IRC that others are having similar problems with all the AOSP roms. I'm trying to get a consensus of who else is experiencing this and some more suggestions on how to fix this.
I appreciate all the help
~Thanks , AnthonyKash

Yeah this is very odd. A couple of us in ##incredibleroms have been working with AnthonyKash to figure this out. So far we have had no luck at all. No Sense UI ROMs do this to him, it seems like it's only vanilla ROMs. Very strange............

anthonykash said:
I don't post here often, but I am on IRC all the time for those of you that do know me. I have been having serious issues with the AOSP Roms. Cyanogen, Ruby, and Incredible Does all either freeze on me or reboot sooner or later. I've went so far as to install nothing else except the Rom and it still freezes or reboots. I've done this test with all three, I even dialed down the processor while on them and still NO DICE. I'm not an Android expert, but I do have a bachelor's in IT so I feel I'm pretty tech savvy. I was told on IRC that others are having similar problems with all the AOSP roms. I'm trying to get a consensus of who else is experiencing this and some more suggestions on how to fix this.
I appreciate all the help
~Thanks , AnthonyKash
Click to expand...
Click to collapse
I know you posted this months ago but was wondering if you figured out what is causing this? I too can't use ANY aosp Rome because they all end up being unusable after a couple of hours. It's almost like the CPU slows down to a dramatic crawl. Only way to fix is to do a battery pull to reset. I have cleared cache, dalvik, uninstalled setcpu, all with no luck. Anyone have any insights?

Check integrity and space of SD card - maybe even remove, copy contents to PC, reformat to FAT32, copy a few nandroids back to SD and reinstall in device. Also make sure there is ample space on SD.
Absent that, have you tried a different SD card? AOSP ROMs interface w/ the SD considerably more than Sense ROMs.
Also, check radio version - recommend at least 2.15.xx
HBOOT version may come into play as well.

+1 to the above post. Seems like some sense files are bring left somewhere.
Sent from my ADR6300 using XDA App

smtom said:
Check integrity and space of SD card - maybe even remove, copy contents to PC, reformat to FAT32, copy a few nandroids back to SD and reinstall in device. Also make sure there is ample space on SD.
Absent that, have you tried a different SD card? AOSP ROMs interface w/ the SD considerably more than Sense ROMs.
Also, check radio version - recommend at least 2.15.xx
HBOOT version may come into play as well.
Click to expand...
Click to collapse
I don't think its my SD Card, I just got a new one a month ago and the same thing happened with my old SD Card. I have 4 gigs left empty of a 16 gig sd card. Would it make a difference if I installed from EMMC using RA recovery?
Hboot 0.92
Radio 2.15.00.09.01
Am on the latest versions of Hboot and radio right?

One thing I do find very weird is that even after doing full wipes of user data, cache and dalvik, when I boot up on CM7 my wifi settings still work. I would have expected I needed to reenter all of those settings. Or does this stuff get saved to the SD or internal storage...normal? If it is not, then why are data wipes in Recovery not cleanning up my files?

I've not had this problem.
Sent from my ADR6300 using XDA App

greatchief1 said:
I don't think its my SD Card, I just got a new one a month ago and the same thing happened with my old SD Card. I have 4 gigs left empty of a 16 gig sd card. Would it make a difference if I installed from EMMC using RA recovery?
Hboot 0.92
Radio 2.15.00.09.01
Am on the latest versions of Hboot and radio right?
Click to expand...
Click to collapse
Yep, those are the latest versions.
AOSP ROMs offer automatic reinstall of apps and data to Google when flashing, if that option is checked when flashed. That's where/how/why settings and/or apps still appear as before.
So, if Sense ROMs are not wonky, maybe it is an app you have installed on the AOSP ROM?
Long diagnostic road, (well understood by us IT folk ) but perhaps uninstall apps in reverse install date order of the app, reboot as you go thru, see which one may have been a culprit.
Absent that, perhaps factory reset in recovery, install an AOSP rom w/out choosing to reinstall apps.
Maybe try another different AOSP ROM?
I know the SD interacts quite a bit more with the SD compared to Sense ROMs - again, maybe copy SD card contents to PC, reformat SD to FAT32 either on the PC or in phone, maybe both - then d/l an AOSP ROM on a clean SD, see if it's still wonky.

smtom said:
Yep, those are the latest versions.
AOSP ROMs offer automatic reinstall of apps and data to Google when flashing, if that option is checked when flashed. That's where/how/why settings and/or apps still appear as before.
So, if Sense ROMs are wonky, maybe it is an app you have installed?
Long diagnostic road, (well understood by us IT folk ) but perhaps uninstall apps in reverse install date order of the app, reboot as you go thru, see which one may have been a culprit.
Absent that, perhaps factory reset in recovery, install an AOSP rom w/out choosing to reinstall apps.
Click to expand...
Click to collapse
Sense ROMS work great, its AOSP roms that are giving my phone fits lol. Well last night I tried something new.
-I changed my radio from 2.15.00.09.01 to 2.15.00.07.28 Official Froyo radio.
-Installed CM7 #14 from the EMMC versus SD CARD.
-"Hit Wipe All" in recovery about 10 times in a row before I flashed CM7
I hope changing the radio to "official" is what does it. Anyone running AOSP roms using the leaked radio 2.15.00.09.01 ?

Radio?
Yes, do let us know whether the xx.09 radio was the (a) culprit.
I run the older 2.15.xx.07.28 one, never had issues w/ AOSP ROMs.

I had an issue with this using cm7 nightlies, and I WOULD post it there but the new, ~totally awesome~ rule they are implementing (can't post in the dev forum w/ less than 10 posts) prevents me from doing that (Which means I have to spam the other sub forums?).
ANYWAYS, I got a bigger sd card from a friend, and I went to erase it under the sd card settings. Then i got a low space notification, saying I had 9 mb free of 7 Terbytes. Rebooting the phone caused it to go into boot loop. If your situation sounds like mine then do this
Boot into CWM, and from there you can mount the SD card and format it, as well as copy any backups.
I did not have any luck with restoring the phone to a previous AOSP rom, even after wiping the cache/dalvik. Maybe there's another one that could be wiped that I didn't do. Anyways, I installed a Sense based rom, and from there I was able to install Cyanogen mod.
Good luck.

smtom said:
Yes, do let us know whether the xx.09 radio was the (a) culprit.
I run the older 2.15.xx.07.28 one, never had issues w/ AOSP ROMs.
Click to expand...
Click to collapse
Well it turns out that the radio version I was using was not the issue because the phone became unresponsive this morning when I tried to wake it up. To be specific, it does allow me to swipe to unlock but painfully in slow motion.
So that rules at the radio...which leaves me with its either the ROM/Kernel or some rogue app.
So this morning I wiped all user data in recovery and reinstalled CM7#14 but this time I did not log on to my google account during setup and have not installed any apps. So far no issues, but the true test is trying to wake the phone up tomorrow in the morning. If there are no issues, then that solves it (ITS A FREAKING APP).
If it is a rogue app that has been haunting me these past couple of weeks then who has the best way to identify which one is the offender? Why would a rogue app only affect me using AOSP roms and not Sense?
My suspicions are with..(Locale, Beautiful Widgets, ADW EX, Swype, CardioTrainer, Handcent) but I guess process of elimination is what its going to take.
Thanks to all for the help and recommendations.

cougar618 said:
I had an issue with this using cm7 nightlies, and I WOULD post it there but the new, ~totally awesome~ rule they are implementing (can't post in the dev forum w/ less than 10 posts) prevents me from doing that (Which means I have to spam the other sub forums?).
ANYWAYS, I got a bigger sd card from a friend, and I went to erase it under the sd card settings. Then i got a low space notification, saying I had 9 mb free of 7 Terbytes. Rebooting the phone caused it to go into boot loop. If your situation sounds like mine then do this
Boot into CWM, and from there you can mount the SD card and format it, as well as copy any backups.
I did not have any luck with restoring the phone to a previous AOSP rom, even after wiping the cache/dalvik. Maybe there's another one that could be wiped that I didn't do. Anyways, I installed a Sense based rom, and from there I was able to install Cyanogen mod.
Good luck.
Click to expand...
Click to collapse
Please tell me u meant 7gb not 7tb
If you have a SD card that huge I beg you to tell me where to get it
I've heard of a 2tb SD but they haven't released it
Sent from my Incredible using XDA App

just wanted to give an udate on my issue...as I suspected it was an app that was causing my phone to crash using aosp roms. The offending app is Locale, wierd that a it never gave me problems using Sense based roms.

greatchief1 said:
just wanted to give an udate on my issue...as I suspected it was an app that was causing my phone to crash using aosp roms. The offending app is Locale, wierd that a it never gave me problems using Sense based roms.
Click to expand...
Click to collapse
Good stuff. Glad to see it all finally worked out.

[Q] Random shutdowns & bootloop on all roms!

Hi Everyone
I was hoping someone would be able to help me out as I’m a total Noob!
I have an HTC Desire on the Orange network in the UK. I started to get a few problems with my phone shutting down and restarting, my GF’s brother had been recommending that I root and flash a different rom for a while, and seeing as he has a Desire on the T-Mobile network and had never had any trouble with rooting his phone or any of the roms he used I decided to give it a shot.
I followed everything in Linkslovesandroid’s noob thread found here:
http://forum.xda-developers.com/showthread.php?t=1016084
I first tried CyanogenMod7 on GF’s brother’s recommendation, worked ok for a bit but I had problems with constant shutting down and restarting over and over again, is this called bootlooping? The only way to stop it was to remove the battery, even then it was no guarantee. Other things were going wrong like the screen freezing, certain buttons were unpressable etc.
I gave my phone to him and he couldn’t explain why such weird things were happening as his Desire experienced no problems at all. He suggested I try something different like GingerVillain. GV never loaded or booted up for me, I wiped data / factory reset, wiped cache, wiped dalvik, installed zip from SD, the rom would then install okay but when I rebooted the phone never ever got past the Alpha Rev S-off screen. This happened when I tried to install GV 2.5 and 2.6, I see that 2.7 has just been released but don’t see the point in trying seeing as the other 2 versions wouldn’t work.
I then tried Oxygen, again, worked ok for a while but started giving me random shut downs and restarts. Once I was driving down the motor way using sat nav software and the phone just shut down! I had to find somewhere to pull over to restart the sat nav software and again it restarted itself! Lol!
One day my phone went into an endless bootloop, no matter how many times I took the battery out the phone just wouldn’t stay on, I had to flash a new rom just to get the phone to fully boot up! I went back to CM7 but have the same old problems, so now I’m using MIUI and I’m still getting shutdowns!
What is wrong with my phone? If anyone has any ideas what I might’ve done wrong, or whats causing problems please offer your suggestions! I don’t really like the sense Roms, I’d like to try GingerVillain but I could never get it to install! I just need my phone to be stable enough to know I can send an SMS to someone without it restarting! If you need to know about Kernels or radios or anything please just ask me (and tell me where I can find out!) Like I said, I’m a noob when it comes to phones!

Same kind of problems here. Random restarts (no shutdowns) on various roms, including the original stock froyo. Happens mostly while installing stuff from the market.
Any ideas?

Sounds like the motherboard is faulty/hardware error. Send back to repair. Usually the kernel can cause problems and OCing (restarting), but you said, that it happens randomly on every ROM, so that means it is more likely a hardware problem.

I had this too, same symptoms sent it back to HTC, duff motherboard, back in 14 days and all working fine.
Only thing is it got reset to original contract so had to pay to unlock it and then root etc.
But well worth it!

Hi Guys
Thanks for your replies so far!
So is it likely that my motherboard was faulty all along? I used to get random restarts sometimes when I was on the sense that came pre-installed on the phone, but nowhere near as often as I get now I've rooted and flashed new roms.
Is it possible that I've damaged it in some way? That could get me in some trouble because when I rooted I'd have voided my warranty, if I send it back to Orange as faulty now they'll know and could pretty much tell me tough luck!
I've heard you can unroot and put your phone back to how it was, but they'd still be able to tell wouldn't they?
Has anyone ever sent a phone back for repair through Orange UK?
Thanks again for your responses so far guys!

For me it turned out that the SD card was corrupt in some way. Repartitioned and reformatted it, and this does help for now. Might try that first, before sending into repair.
Good luck!

reynard80 said:
For me it turned out that the SD card was corrupt in some way. Repartitioned and reformatted it, and this does help for now. Might try that first, before sending into repair.
Good luck!
Click to expand...
Click to collapse
I agree. If you have system files on your SD and if the SD gets corrupted you might get the result you've described.

That's interesting, the other night when I had such a severe bootloop that I had to flash a new rom just to get the phone to fully boot up, it only booted after I'd removed the SD card.
To begin with I was very happy because I thought I'd solved the problem and all I'd need was to buy a new SD card, however a short while later it happened again with no SD card inside at all!
I decided to give Ginger Villain another go hoping that removing the SD card after "install zip from SD card > reboot" would allow it to boot up, it didn't. Never got past the alpha rev screen.
How will I know if I have system files on the SD card? Should I maybe try the G-Parted stage of the noob guide again to reformat the card and create the ext-4 partition?
Thanks again for your time and help by the way!

dellaclearing said:
That's interesting, the other night when I had such a severe bootloop that I had to flash a new rom just to get the phone to fully boot up, it only booted after I'd removed the SD card.
To begin with I was very happy because I thought I'd solved the problem and all I'd need was to buy a new SD card, however a short while later it happened again with no SD card inside at all!
I decided to give Ginger Villain another go hoping that removing the SD card after "install zip from SD card > reboot" would allow it to boot up, it didn't. Never got past the alpha rev screen.
How will I know if I have system files on the SD card? Should I maybe try the G-Parted stage of the noob guide again to reformat the card and create the ext-4 partition?
Thanks again for your time and help by the way!
Click to expand...
Click to collapse
If your rom requires an sd-ext partition than it stores system files on the SD. Try a rom that doesn't require that. I would go as far as bringing the phone to stock just to verify if it's the phone or the SD. Bringing it back to stock is a requirement for you to return it for servicing if you realize that it's a problem with the phone not the SD.

paul.c said:
If your rom requires an sd-ext partition than it stores system files on the SD. Try a rom that doesn't require that. I would go as far as bringing the phone to stock just to verify if it's the phone or the SD. Bringing it back to stock is a requirement for you to return it for servicing if you realize that it's a problem with the phone not the SD.
Click to expand...
Click to collapse
Hi Paul, is it only stock roms that don't store system files on the SD or can you recommend a rom that doesn't require an ext partition as I'm not too sure what I'm looking for? I realise that I'll have to unroot before I can return the handset but if there's another custom rom out there I can test before unrooting that'd be good!
However, if you fully recommend returning the phone to stock to test then that's what I'll do!

dellaclearing said:
Hi Paul, is it only stock roms that don't store system files on the SD or can you recommend a rom that doesn't require an ext partition as I'm not too sure what I'm looking for? I realise that I'll have to unroot before I can return the handset but if there's another custom rom out there I can test before unrooting that'd be good!
However, if you fully recommend returning the phone to stock to test then that's what I'll do!
Click to expand...
Click to collapse
This ROM http://forum.xda-developers.com/showthread.php?t=896213 doesn't require SD for system files.

I'd first try the complete stock rom with a completely formatted SD card. You can be completely sure that there isn't a software problem with a custom rom.
If this doesn't work, try replacing the SD card. This did help for me.
If still no succes, send it for repairs.

paul.c said:
This ROM http://forum.xda-developers.com/showthread.php?t=896213 doesn't require SD for system files.
Click to expand...
Click to collapse
Thanks for linking me to that rom.
I did a bit of reading about roms that use ext sd partitions and have so far concluded that its for A2SD so an entire app can be run from the sd card instead of internal memory.
So anyway, I've just installed the Redux rom you linked me to that doesn't store sytem files on the sd, first 2 boots had a sudden shutdown and restart! I'm on the 3rd boot now, it's holding okay but I need to put it through its paces to see how long it can go and what sort of performance it will allow before it starts shutting down on me!

reynard80 said:
I'd first try the complete stock rom with a completely formatted SD card. You can be completely sure that there isn't a software problem with a custom rom.
If this doesn't work, try replacing the SD card. This did help for me.
If still no succes, send it for repairs.
Click to expand...
Click to collapse
Hi Reynard. If the Redux rom I've just flashed (less than 10 minutes ago) doesn't use the sd for system files, then if it keeps rebooting on me would that diagnose a faulty motherboard as reliably as using a stock rom?
I'm gonna unroot and flash a stock rom soon anyway, that way I can be sure before I send it back to Orange for repair, although apparently there isn't an official Orange UK stock rom available so I'm just gonna have to get as close as I can and hope they don't notice!

dellaclearing said:
Hi Reynard. If the Redux rom I've just flashed (less than 10 minutes ago) doesn't use the sd for system files, then if it keeps rebooting on me would that diagnose a faulty motherboard as reliably as using a stock rom?
I'm gonna unroot and flash a stock rom soon anyway, that way I can be sure before I send it back to Orange for repair, although apparently there isn't an official Orange UK stock rom available so I'm just gonna have to get as close as I can and hope they don't notice!
Click to expand...
Click to collapse
Probably there is a ROM just that it hasn't been leaked so I hope you won't get in trouble.

paul.c said:
Probably there is a ROM just that it hasn't been leaked so I hope you won't get in trouble.
Click to expand...
Click to collapse
Haha! Me too!

Dayamn! I didn't have a reboot all day on Redux, got home from work and installed Sygic sat nav software and the phone rebooted 3 times just while downloading the map! I had to remove the battery once as well.
Decided I'd just test Google maps navigation while driving to pick up the Mrs from work and it shut down on me
If I can get hold of another sd card to test I'll see if it makes a difference, but there's not really a lot more I can do now other than unroot and send it back to Orange. The strange thing is that it never used to reboot half as much on the stock rom the phone came with, and it never did it while I was sat nav'ing ever. It just used to happen randomly when I was texting or web browsing. Odd.
Where might be the best place to find the closest to stock rom for Desire Orange UK?

Just wanted to update you all.
I found my original SD card that came with the phone, I fully formatted it and then did a completely fresh install of Redux and performed the same tests and got the same results. Still crashed and rebooted! So that tells me it's the phone and not the card!
I'll be restoring to stock and calling Orange tomorrow to get a replacement / repair.
Thanks to everyone who helped me out along the way, your time and effort is very much appreciated!

Hi guys,
I made a goldcard and tried installing the stock ruu, it seemed to work but when I hold vol down and power on it still says:
AlphaRev
BRAVO PVT1 SHIP S-OFF
HBOOT 6.93.1002
I read on the Alpharev website that recent versions of Alpharev aren't overwritten by stock ruu's hboot so it must first be downgraded. I used android flasher to flash the Alpharev downgrader, then it just froze at the "why so serious" screen. I was advised to flash the stock bravo hboot found on the alpharev website, which I did and then I was finally able to install the ruu. Obviously I've done something wrong and I'm guessing its flashing the stock bravo hboot...
Would it be okay to use android flasher again to run just the downgrader image, and then using fastboot flash the ruu again?
Any ideas? I don't want to risk sending my phone back for repair still saying S-Off!

Okay, I kept reading through XDA and found a post by Dzumagos advising someone to do exactly what I just asked, use Android Flasher to run the Alpharev downgrader image and then reflash stock ruu, so I grew a set and tried it myself!
Bravo PVT1 SHIP S-ON
HBOOT-0.93.001
Voila! I'm now back to S-ON, so now I feel I'm ready to call Orange and tell them about the constant shutdowns and restarts, which have still been happening on stock btw, the phone also feels really hot too!
I just hope the replacement they send me is issue free!
Thanks again to everyone who helped out in this thread and in the orange uk ruu thread!
Cheers everyone!

[Q] Quantum v3 beta issue: /.android_secure

After several days of tinkering I've come to admit that I can't solve this problem I'm having with the Quantum v3 beta ROM on my SGH-I747M. When installing certain apps, I get the message "couldn't install on usb or sd card." Most apps install fine, but a few very important ones, like Swiftkey, just won't. I tried all kinds of solutions, including formatting everything (system, data, sdcard, etc), unrooting, and then re-rooting from scratch and going straight to Quantum; same issue. I've not been able to replicate the issue on any other ROM--that said, the other ones are all 4.3. Online solutions to similar issues suggest unmounting or pulling the SD card, or deleting a temporary file that sometimes appears in either mnt/asec or sdcard/.android_secure. Neither solution has worked. It's worth noting that when Quantum is installed and I wipe user data in CWM, while wiping /data I get the error line "couldn't mount" or "error reading /.android_secure." Whereas there's no problem if any other ROM is installed. This is consistent whether or not I actually have an SD card plugged in.
I would have posted this right in the Quantum ROM topic where it would have made a lot more sense, but XDA won't let me until I have 10 posts, so here it is. Thanks for any help with this; I'm specifically looking for people who have encountered and solved the issue or have seen the solution posted. Until I see that there's already been a solution to this, I'm just going to stick with PAC ROM and wait for 4.4 ROMs on the S3 to improve.
Cheers.

[Q] Lollipop and storage / SD card use?

One major problem I have with my Tab S 8.4 is the limited storage. I mainly install games, and they can't move their data to the SD card, nor can I use the SD card with programs like AGS, because of KitKat security limitations. I'm holding off upgrading to Lollipop because the upgrade screen warns me that I'm going to lose at least 950MB of storage (and I know from my Nexus 7 2012 that Lollipop does indeed add quite a bit to storage use).
What I'd like to know is how Lollipop handles the SD card. If I can move game data to it, that would be great, instantly worthy of an upgrade. If the download folder can be moved to the SD card on Lollipop, that would also be quite good. Even if I could only move AGS data to it (without it becoming read only) that would be interesting enough to consider the upgrade.
So I'd love it if someone could tell me from experience whether the SD card is more useful with Lollipop. It's annoying to have a 64GB card that's mostly empty while internal storage is constantly full.
(I hope that someone can help answer me this question. Haven't been able to find someone to answer me this elsewhere, and looks like others on the XDA forum asked this for other devices and didn't get an answer, so I'm not all that hopeful, but I'll be very grateful if I get a good answer. Thanks in advance!)

Root your device and your problem is easily solvable. Without even on lollipop there are still restrictions.
I am running lollipop but not stock, I'm running iron Rom. Which is practically stock without all the bloat, runs great and it shaved at least a gig off the stock Rom.

Thanks for the reply. What does using a custom ROM solve (from what I mentioned above: installing game data on SD card, download directory, SD card access by apps), and is that an expected part of any custom ROM I install (assuming I pick one listed on this site) or would I have to do anything extra or pick a specific ROM?

Like I said Iron Rom is lighter compared to stock so that's an extra internal storage, plus it comes prerooted so you can then give write access to the sd card and install Link2sd.

Thanks. People who already know all the things sometimes don't remember that others have no clue. So thanks a lot for mentioning Link2sd. If I understand correctly, all I need is to root the device and install Link2sd and then I can move apps to the SD card. No need to install a custom ROM for that, right?

ET3D said:
Thanks. People who already know all the things sometimes don't remember that others have no clue. So thanks a lot for mentioning Link2sd. If I understand correctly, all I need is to root the device and install Link2sd and then I can move apps to the SD card. No need to install a custom ROM for that, right?
Click to expand...
Click to collapse
That's correct.

Thanks. I'll have to look into how rooting affects my tablet's warranty, but if there's no problem with that then I'd likely go that way.
I would still be interested in knowing whether Lollipop by itself improves anything over KitKat in terms of handling the SD card.

You will lose warranty with root, but if you are kitkat you can try the latest version of kingroot as it won't trip Knox.
Before using Link2sd you need to create an ext2 partition on the sd card.
Look on Google there are plenty of guides how to use link2sd.

I did not know that i will loose 950MB of my tiny 16GB storage when i upgrade to lollipop, is this true? , we not Samsung hauled over the coals in the press a few months ago because of the amount of free storage space left to the user after the system was installed, If i will loose 950mb, that is another reason not to upgrade to lollipop, things just seem to get worse, somebody give me a nudge i must be dreaming or is this a nightmare.
John.

As far as lollipop goes, if you go to Settings>Applications>SD CARD you can see a list of Apps that can be moved to the SD card. Not all apps will be able to be moved. As far as games go, I will have to test that out and get back to you. I have no games installed at the moment. any specific one in mind?

Tinderbox (UK) said:
I did not know that i will loose 950MB of my tiny 16GB storage when i upgrade to lollipop, is this true? , we not Samsung hauled over the coals in the press a few months ago because of the amount of free storage space left to the user after the system was installed, If i will loose 950mb, that is another reason not to upgrade to lollipop, things just seem to get worse, somebody give me a nudge i must be dreaming or is this a nightmare.
John.
Click to expand...
Click to collapse
I upgraded to Lollipop last night and there was no warning that I would lose 950MB of storage. There was a warning that I needed at least a couple GB free in storage so that the system could proceed with the update. The U.S. lollipop OTA update itself is about 925.21MB. Other versions will be more or less around that number. Maybe he was mistaken the update size with losing that amount of storage space.

So it only needed`s a couple of gb of free flash space from my 16gb temporarily, while doing the update and then i will get it back, once the update is complete and the temp files are delete, is this what it looks like, I intend to do a reset before and after i upgrade to lollipop whenever we get it in the UK
I just hope lollipop is as stable as kitkat, as i bought my T800 10.5" just before Christmas, and it has never been rebooted or turn off, crashed or anything in 196 Days according to the battery history.
John.
LakersDroid said:
I upgraded to Lollipop last night and there was no warning that I would lose 950MB of storage. There was a warning that I needed at least a couple GB free in storage so that the system could proceed with the update. The U.S. lollipop OTA update itself is about 925.21MB. Other versions will be more or less around that number. Maybe he was mistaken the update size with losing that amount of storage space.
Click to expand...
Click to collapse