Resources for Andriod Terms and Basic Background for Rooting Devices? - Galaxy Tab S Q&A, Help & Troubleshooting

Can someone point toward resources needed to understand the process of rooting an android device. As an example things like the Dalvik Cache, what is it and why wipe it? And a thousand other things. how do we get some background.

Related

Help: Your phone is low on storage space

I had 2.5mb left when I went to SD & Storage setttings.
Uninstalled some stuff, turned it back on and off, now im down to 668kb and I keep getting force close errors on everything, I cant get any email or messages through and I dont know what to do!!
Help!
Root your phone and install Apps2SD
try deleting your internet cache
abc27 said:
Root your phone and install Apps2SD
Click to expand...
Click to collapse
Why have you done this?
I am having similar issues. Coming from a winmob I find it amazing that you cannot install apps to the SD card out of the box and have to go through a long, no doubt complex and warranty voiding process to to be able to do it and then, if my experience with flashing winmobs is anything to go by, the phone will never work quite the same again! That said is there a guide available for rooting a desire and can anyone tell us the dangers / benefits?
DaddyCee said:
Why have you done this?
Click to expand...
Click to collapse
So I can install apps to my sd card? Kind of obvious no?
tingsagwaan said:
I am having similar issues. Coming from a winmob I find it amazing that you cannot install apps to the SD card out of the box and have to go through a long, no doubt complex and warranty voiding process to to be able to do it and then, if my experience with flashing winmobs is anything to go by, the phone will never work quite the same again! That said is there a guide available for rooting a desire and can anyone tell us the dangers / benefits?
Click to expand...
Click to collapse
It's a security issue with Linux based phones. It's not a "long, no doubt complex and warranty voiding process". It's not exactly difficult to do so long as you can follow instructions. The only time consuming part might be downloading a linux live cd to use to complete the rooting process. I've already proved in another thread that the action of rooting itself won't void the warranty, the warranty becomes invalidated only if a defect is caused by the rooting of the device.
Windows Mobile is a whole other animal than Android so don't take that in to account. The rom you flash during the rooting process is a standard generic rom, the only difference is that it gives you root access.
That sounds great abc, very reassuring thanks. Are there any decent instructions you could point me to?
http://android.modaco.com/content/h...ide-now-with-new-improved-easier-root-method/
There ya go.
He's even simplified the process since yesterday
Thanks a lot abc. Have you or anyone else rooted their phones yet? Does it affect the phone detrimentally in anyway? Is the only advantage Apps2SD or are there other benifits? How do you implement Apps2SD once you are rooted? Thanks!
Check your news feed apps, rss feeds etc through the manage applications and check their cache. I found my news feed widget from google has kept 42mb in it's cache, and kept growing every time it updated....
OnlinePredator said:
Check your news feed apps, rss feeds etc through the manage applications and check their cache. I found my news feed widget from google has kept 42mb in it's cache, and kept growing every time it updated....
Click to expand...
Click to collapse
Surely it would store the cache on the SD though?
TheOriginalKi said:
Surely it would store the cache on the SD though?
Click to expand...
Click to collapse
It doesn't. Crazy.

[Q] Root security and A2SD+ related questions

I've been holding out on using rooted ROMs, but am getting sick of all the low memory warnings. The sole reason for me to try out custom ROMs will be to get more space via A2SD+, which I read can't be done without root access. I'd be happy if fellow users can advise on these root-related issues:
1. I've read articles about the dangers of having root on your device, especially malicious apps. Now my question is, am I going to be notified/asked if an application wants to use superuser access for whatever reason? I saw some shots of dialog boxes asking for su permission, but I wasn't sure.
2. I understand that stock Android is relatively safe with its sandboxed environments. Will apps that don't normally ask for root be able to do things they cannot do on stock ROM? For example, access other app's data or generally make a mess of the system files (hypothetically)?
3. Moving app space and cache to the storage card probably increases the load on the card. What effect does A2SD+ have on battery life and speed/performance? From my previous experience with WM phones, moving background service apps to external storage caused drain on the battery.
4. Lastly, and perhaps most importantly, is there a link between the random restarts that I've been reading about about and installing custom ROMs? From what I've read, these reboots happen on stock phones too, but might the problem be triggered or made worse by setcpu, undervolts, etc?
Hopefully others can shed light on these questions. Thank you.
1. yes
2. no
3. 1% more
4. no

[Q] New ROMs and Titanium Backup Pro restore apps/data

I'm pretty sure that this hasn't been covered specifically so I'm posting a new thread.
I backed up all my apps and data on a stock rooted Sprint 4.24.651.1, 2.3.3 ROM via TBU Pro. I also performed a backup of my current ROM with ROM Manager. I then installed Team Nocturnal _Shooter_RLS_2.3.(after, of course, all the recommended wipes and resets) When I went to restore my apps and data I wondered if some of the previous app versions (where both ROMs have same apps/diff versions) would hose things up. It did, I think. Maybe all that I needed to do was clear some app caches and reboot. Not sure, I couldn't get any of the HTC widgets to load but I did see in another thread that cache clearing may fix that. But other stuff was goofy after the restore too. It became buggy and horribly slow, so I think that there's more to it than just the HTC stuff. I wonder if something I restored and maybe shouldn't have hosed it up. What I'm wondering is if someone would be so kind as to scan down my app lists and tell me which apps and/or data that are obvious that I shouldn't restore? For example, this new ROM has a different dialer, it makes sense to me that I wouldn't restore that. Same with anything to do with Sense, since this particular ROM I believe has a newer version, but not sure. I am thinking that any time I install a different ROM this will be a consideration but maybe I have the wrong idea about the whole thing. I have attached 30 images captured (incl the Software info screen) of my app list in TBU.
Lastly, I'll add that since making the move to Android from WinMo about a year ago I am very glad I did it. I could not have possibly been able to learn and do the things (rooting, S-off, flashing ROMS) that I have done without XDA! You folks are brainiacs and I greatly admire what you all do. (blatant a**-kissing)Thank you, thank you!
You have to be very careful about what you restore using Titanium when you are moving from one ROM to another. I found this from personal experience (moving from Stock to Synergy RLS1 and then to MikG). There is some good info in the Titanium Backup Wiki.
The part that you need to be careful about is restoring system data that is incompatible with the newer system apps in your new ROM. Your best bet is to only restore the User Apps and their data. You can do this in Titanium by selecting Menu > Batch > Restore missing apps with data.
There is some system data that you can restore without getting into trouble (probably bookmarks, SMS Messages, Sprint Voicemail) but you are going to have to experiment. I restored my missing apps using the batch option and then went to the Backup/Restore screen to look at the System Apps and Data one by one to see if there was anything that I could restore. Sometimes I would restore some data that would cause a problem and I would have to Wipe that data (also in Titanium Backup/Restore screen) and move along. I know at least once I was forced to start fresh and Wipe and reflash the ROM.
gbweller said:
I'm pretty sure that this hasn't been covered specifically so I'm posting a new thread.
I backed up all my apps and data on a stock rooted Sprint 4.24.651.1, 2.3.3 ROM via TBU Pro. I also performed a backup of my current ROM with ROM Manager. I then installed Team Nocturnal _Shooter_RLS_2.3.(after, of course, all the recommended wipes and resets) When I went to restore my apps and data I wondered if some of the previous app versions (where both ROMs have same apps/diff versions) would hose things up. It did, I think. Maybe all that I needed to do was clear some app caches and reboot. Not sure, I couldn't get any of the HTC widgets to load but I did see in another thread that cache clearing may fix that. But other stuff was goofy after the restore too. It became buggy and horribly slow, so I think that there's more to it than just the HTC stuff. I wonder if something I restored and maybe shouldn't have hosed it up. What I'm wondering is if someone would be so kind as to scan down my app lists and tell me which apps and/or data that are obvious that I shouldn't restore? For example, this new ROM has a different dialer, it makes sense to me that I wouldn't restore that. Same with anything to do with Sense, since this particular ROM I believe has a newer version, but not sure. I am thinking that any time I install a different ROM this will be a consideration but maybe I have the wrong idea about the whole thing. I have attached 30 images captured (incl the Software info screen) of my app list in TBU.
Lastly, I'll add that since making the move to Android from WinMo about a year ago I am very glad I did it. I could not have possibly been able to learn and do the things (rooting, S-off, flashing ROMS) that I have done without XDA! You folks are brainiacs and I greatly admire what you all do. (blatant a**-kissing)Thank you, thank you!
Click to expand...
Click to collapse
Yeah, I had a feeling that there would be conflicts like that before I even restored. I never thought to read the TBU wiki...thanks for that tip! It looks like I have a lot more homework to do before I flash again. I really have to decide if the time investment is really worth the return. There are so many cool ROMs out there but what a lot of B.S. sorting out what works and what doesn't. It is excruciating to have to read through 50+ posts following a ROM release to find out what you're in for. What would be super-cool is if someone was able to construct a spreadsheet of the most popular ROMs in a column with all of the popular features (4G, Wifi Tether, Mirroring, etc), kernel compatibility, Sense or no Sense, etc in a row at the top, with check marks indicating whether or not the feature works or is baked in. I'd pay to see that. Especially if it were linked to the downloads to the ROMs and kernels.
Thank you very much for the reply!

[Q] Need Help Creating a flashable ROM

So, I have been attempting this on my own for a couple weeks with little to no luck, and searching XDA hasn't really been fruitful, so I thought I would ask.
So I work in Tech Services at the library at my local university. My team is in charge of electronic equipment loans, and recently purchased 20 Galaxy Tab 3 10.1s for student checkout. What I am trying to do is make a straight factory ROM that is flashable through TWRP but with a set of 3 e-book apps added into system apps. The 3 apps I need added are Kindle, Overdrive Media Console, and Bluefire Reader (it is after all, a library). Doesn't need to be rooted or anything, but to speed up turn-around time, it would be nice if it would wipe data automatically as part of the flashing process so we don't have to worry about peoples passwords or account info being compromised. I have tried many different things, but can't seem to get A: the apps added correctly (they install but FC as soon as I try to open them) and B: a script added that would wipe before flashing the ROM. As far as I can tell through my research, it might be possible, but far beyond my skill and knowledge levels. Honestly, I am not even sure if flashing through recovery is the best solution. I have looked at Samsung Configurator as well as many 3rd party MDM tools and none of them seem to be able to do what I want. Possibly something that could be flashed through Odin?
Any thoughts, suggestions, advise, help, etc. would be greatly appreciated.
Moderators: If this needs to be moved, feel free to do so. I wasn't sure where it belonged, but figured this would be okay.
Thanks everyone!
Edit: Don't know if it matters, but they are Wifi only models.
karlkarloff said:
So, I have been attempting this on my own for a couple weeks with little to no luck, and searching XDA hasn't really been fruitful, so I thought I would ask.
So I work in Tech Services at the library at my local university. My team is in charge of electronic equipment loans, and recently purchased 20 Galaxy Tab 3 10.1s for student checkout. What I am trying to do is make a straight factory ROM that is flashable through TWRP but with a set of 3 e-book apps added into system apps. The 3 apps I need added are Kindle, Overdrive Media Console, and Bluefire Reader (it is after all, a library). Doesn't need to be rooted or anything, but to speed up turn-around time, it would be nice if it would wipe data automatically as part of the flashing process so we don't have to worry about peoples passwords or account info being compromised. I have tried many different things, but can't seem to get A: the apps added correctly (they install but FC as soon as I try to open them) and B: a script added that would wipe before flashing the ROM. As far as I can tell through my research, it might be possible, but far beyond my skill and knowledge levels. Honestly, I am not even sure if flashing through recovery is the best solution. I have looked at Samsung Configurator as well as many 3rd party MDM tools and none of them seem to be able to do what I want. Possibly something that could be flashed through Odin?
Any thoughts, suggestions, advise, help, etc. would be greatly appreciated.
Moderators: If this needs to be moved, feel free to do so. I wasn't sure where it belonged, but figured this would be okay.
Thanks everyone!
Edit: Don't know if it matters, but they are Wifi only models.
Click to expand...
Click to collapse
Just off the top of my head...this is what I would do.
Root the tabs (probably need to install custom recovery for that, but I'm not sure since I don't follow the 10 in forum).
Install Titanium Backup
Install the 3 apps that you want to make as "system" apps (install as any normal app).
Use Titanium backup to "convert to system app" (this will place app in the /system/app" directory).
Uninstall Titanium Backup and use the unroot option in SuperSu.
This should leave you those 3 apps installed as system apps.
You can then, perform a factory reset when the Tabs are returned and still have those apps available. Factory reset does not wipe the system partition, so the apps will remain.
Thanks! I will definitely try that!

Can you revert lollipop back to Dalvik?

Hi,
I've been enjoying lollipop v20A since yesterday already and it's cool I have to say, but I miss using programs like titanium backup and Xposed framework. I just need to use xposed once to enable tabletmetrics for Spotify and also titanium backup to remove mcaffee antivirus. My device is rooted with busybox installed already. Anyone know how to revert back to Dalvik?
There is no Dalvik any more, ART (which stands for Android Runtime) has been built from the ground up by Google for android, it works a million times better than Dalvik, and Android L is the first release to use ART fulltime, with no alternative options available to us.
Dalvik is never going to make a return.
Titanium works perfectly on android L, you just need to install the Titanium beta version.
I am familiar with runtime environments.. All I want is a way to operate dalvik for once. It can be through a Patch or a kernel or whatever.
stilkus said:
I am familiar with runtime environments.. All I want is a way to operate dalvik for once. It can be through a Patch or a kernel or whatever.
Click to expand...
Click to collapse
never going to happen.
stilkus said:
I am familiar with runtime environments.. All I want is a way to operate dalvik for once. It can be through a Patch or a kernel or whatever.
Click to expand...
Click to collapse
There are other ways to do what you want without Xposed or Titanium.. Root browser, ADB and a few other root/Dev tools can/will be your best friend.
pattielipp said:
There are other ways to do what you want without Xposed or Titanium.. Root browser, ADB and a few other root/Dev tools can/will be your best friend.
Click to expand...
Click to collapse
I'm scared of a world without xposed lol
Hope it 'll be a fix soon...fingers crossed
stilkus said:
Hi,
I've been enjoying lollipop v20A since yesterday already and it's cool I have to say, but I miss using programs like titanium backup and Xposed framework. I just need to use xposed once to enable tabletmetrics for Spotify and also titanium backup to remove mcaffee antivirus. My device is rooted with busybox installed already. Anyone know how to revert back to Dalvik?
Click to expand...
Click to collapse
Its not even possible android lollipop is built around art dalvik isnt even present not at all its not even compatible with lollipop so dalvik cant work with lollipop and a kernel updat would not change a thing the whole system the whole lollipop release would have to rebuid to even make dalvik work and only google can do that.
I'm gonna make this work!
I am currently working on a cross-compatible version of the dalvikVM runtime that might solve the whole issue. It's based on KK dalvik, so the work is a bit buggy, but should something be stable enough for general use, I will supply it with instructions on how to implement it in the system.
I honestly don't believe that the Android RunTime is ready to be used yet. We aren't prepared for it's power, or even the lack thereof.
As far as lollipop goes, I love the UI, I just want Dalvik back as well, and I WILL get the best of both worlds, even if I have to brick a few devices along the way.
TheUnbricker said:
I'm gonna make this work!
I am currently working on a cross-compatible version of the dalvikVM runtime that might solve the whole issue. It's based on KK dalvik, so the work is a bit buggy, but should something be stable enough for general use, I will supply it with instructions on how to implement it in the system.
I honestly don't believe that the Android RunTime is ready to be used yet. We aren't prepared for it's power, or even the lack thereof.
As far as lollipop goes, I love the UI, I just want Dalvik back as well, and I WILL get the best of both worlds, even if I have to brick a few devices along the way.
Click to expand...
Click to collapse
Any news?

Categories

Resources