• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Terminology

right. got it! finally :-)

well I did a Mybackup backup

I can't recall doing a backup from recovery....but I might have done.
sorry terrible memory :-)
 
Never quite sure if I should start a new thread..or continue in the same one...
At any rate, I can no longer get into recovery?? I hold down VolDown and power - nothing happens...

EDIT!
I poked around on google, and found a solution, athough it was for a different phone, it still worked. I had to go into Settings - Applications - and turn off Fastboot. Voila - I can get into recovery now.

What 'zactly IS fastboot?
 
Oh you're on a newer sense ROM. Fastboot is too things.

1) It is what comes up when you press back and power. This is where you do fastboot flash.

2) HTC in their infinite wisdom decided to call the ability to quick boot the phone (by it hibernating instead of shutting down) "Fastboot". Very annoying of them.
 
right. got it! finally :-)

well I did a Mybackup backup

I can't recall doing a backup from recovery....but I might have done.
sorry terrible memory :-)
Easy to tell: use your favourite file manager to look in the folder clockworkmod/backup on your SD card. If there is a folder in there whose name is a date/time string (e.g. 2011-09-21.18.55.07) then that's a recovery backup, aka nandroid backup. The folder will contain a set of .img files totalling several hundred MB, plus a text file called "nandroid.md5" that contains the information the recovery uses to check that the backup hasn't been corrupted.

If the clockworkmod/backup folder is empty then you didn't take a recovery backup. In which case, count your blessings that everything worked, but do make sure you take one next time :). The reason to take one of these is that if something goes wrong when you flash a new ROM (or a modification to the current one) and the phone won't even boot, you can restore the nandroid and have everything back the way it was. Basically it's a painless way of undoing mistakes without losing data.

The difference between this and a MyBackup or Titanium backup is that you can use those to restore apps and data to a new ROM, but you need to be able to boot android to run those apps. You use a nandroid to restore the complete state of the phone (ROM, apps and data) back to where it was when you took the backup. You only need to be able to access recovery for this, so it doesn't matter if the ROM won't boot, but conversely you cannot use a nandroid to restore your apps to a new ROM as it will replace the ROM as well! So they are both necessary, but they are used for different things.

I've assumed here that you are using clockwork - if you are using Amon RA then I don't know the folder name where the backup will be, but a quick browse through the root of your SD card should find it (you would be looking for the place where "Amon RA recovery" stores its "nandroid backups", so I expect one of those keywords would provide the answer).
 
You use a nandroid to restore the complete state of the phone (ROM, apps and data) back to where it was when you took the backup. You only need to be able to access recovery for this, so it doesn't matter if the ROM won't boot, but conversely you cannot use a nandroid to restore your apps to a new ROM as it will replace the ROM as well! So they are both necessary, but they are used for different things.

Should a person do a nandroid back up regularly?
I made one before I rooted - all went well - should I do one again now that I am rooted and on a new ROM?
 
I tend to make a nandroid once I'm happy with the setup of a ROM, then make a new one before flashing a new ROM or any update or mod to the current one (since a bad flash may mean the phone won't boot, in which case a nandroid is the simplest fix).

You can make as many as you want, but they are quite large. I keep a few recent ones on my card, and a larger archive on my laptop.
 
I tend to make a nandroid once I'm happy with the setup of a ROM, then make a new one before flashing a new ROM or any update or mod to the current one (since a bad flash may mean the phone won't boot, in which case a nandroid is the simplest fix).

You can make as many as you want, but they are quite large. I keep a few recent ones on my card, and a larger archive on my laptop.

Just to clarify as it was not clear, this is what I meant.
 
This is off the original tpoic, but it falls under a 'terminology' question. If I should start a new thread just let me know.

Being new to Android development and working my first app, I know what I want to do now and there is probably an answer out there, I just don't know how you word my search with the right terminology. Anyways, here goes...

My app works fine right now and when I press the 'back' button, my app goes away to wherever the OS sends it, but it seems to still be working in the background as I'm getting notification messages from my app.

So, is this application:

Closed?
Hibernating?


How do I get my application back so I can see it again. If I click on the application icon it seems to start a second instance and I start getting double notifications.

Sort of like Windows where you can Alt-TAB and cycle through your running apps, is there something similiar on Android. I found the 'Manage Applications' option, but I could only Force Close or Uninstall. I could not figure out how to recall/reactivate a running application.

Also, programmatically if I start the application a second time can it detect the first instance of the app and just reactivate it?

Thanks for any help...
 
Long press home should call your recent apps and you just select your app from the list. You wont be starting the app again, unless you force closed it. If you didnt force close it, you are calling it from RAM and will most likely be in the state you left it in.

In regards to the rest of your questions, it may be better for you to look here:

Application Development - Android Forums
 
Thanks SURoot. I have the Vodafone 858 and the 'home' button looked like an 'email' button. That sorted out the recent apps question and now I can call up my running app from the 'recent' list, but it's not showing the original data in the edit fields so it looks like a new instance of the app.

But that's a question for the Developer's forum.

Cheers.
 
Back
Top Bottom