yashsingh1/xdaforums huggingface dataset:
[Nexus One General] PrawnPoBoy:
Not your bad, Opera's bad. They should do a better job of saving application state so that when the OS shuts it down it doesn't cause you to lose the page you were on.
[Nexus One General] RogerPodacter:
OK i'm having this same exact problem again. All day yesterday i was browsing with opera mini, press home button to perform other tasks, and come back and it is still showing the same web page i was reading.

but then last night all i had to do was check my email real quick, i switch away from opera with the home button press, and go back to opera and it now has to re-load the entire app, taking me to the start page again. surely this is some problem with the way android OS handles multitasking, no? i mean the app obviously was saving my page all day yesterday, just like its supposed to. but then it suddenly STOPS doing this.

my free RAM was again down near 30MB because the OS has loaded a million apps that i dont need. yet the OS then will close the one app i DO need, opera mini, while leaving all these useless apps running, which i didnt even ever need or open in the first place!!

am i the only one who has a problem with this method of OS task management?

i'm sure a reboot will free up all the RAM and things will work normally again. but isnt android a linux based OS? shouldnt linux be able to run for days or even weeks without the need to reboot the phone just to set the RAM back on track?

very frustrated!
[Nexus One General] ChillRays:
If you have a mirror handy, kindly gaze into it and you will find your problem.

http://www.youtube.com/watch?v=BFytHoXdG3E

lol
[Nexus One General] PrawnPoBoy:
No.

Again, this isn't a problem with Androids method of multitasking, it's a problem with the way Opera was written. It's not saving it's state properly. It should, but they haven't written it properly.

Opera obviously doesn't behave the way you expect, so my suggestion is to use something else until they have fixed it.
[Nexus One General] RogerPodacter:
I just can't get on board with that argument. so the OS is giving priority to apps like tuneWiki, which I haven't opened in 3 weeks, over an app that I just switched away from 10 seconds ago is the best way for the OS to operate?

I would agree if my issue happened every single time. but 95% of the time opera stays open like its supposed to. so that tells me it IS doing what its supposed to. but in certain situations it just magically disappears even though it was just in use a few moments before.

I agree that opera is not saving state properly when the OS decides to close it. but why can't the OS leave it open with all the RAM and CPU power this phone has? this situation shouldn't even be happening whether opera is coded right or not.

I made a post on the opera forums to see if maybe they know about it and have a solution.
[Nexus One General] Paul22000:
I'm not sure you're understanding what everyone else in this thread is saying, so here's another way to think about it:

Can you name another big-name app that behaves in the same constant state-losing behavior as Opera?
[Nexus One General] PrawnPoBoy:
The fact that it feels like tuneWiki hasn't been closed even though you haven't used it in 3 weeks lead me to believe that the tuneWiki guys have done it correctly and as a result the user can't tell if the app has been running the whole time or if it is actually loading up a fresh copy of it (loading speed might be the only way to tell). Opera with tabs open probably uses a lot more memory than most programs, so it's a good candidate to close down when memory is needed which is probably why it keeps happening to you.

What Opera should be doing is taking a snapshot of the tabs you have open when you switch to a different applications and writing it to permanent storage so that if it does happen that it get's closed down by the system, when it starts up again later it can reload all of the tabs. It doesn't need to store the page data, just the URLs. I don't know why they don't do that for Opera Mini as their desktop browser does it perfectly.

If you are interested, this developer video on Android application lifecyle might clear things up a bit:

http://developer.android.com/videos/index.html#v=fL6gSd4ugSI
[Nexus One General] diversificationied:
Send Opera an email and tell them to use meta data to remember where you were.

Each properly coded app speaks up and says "I Have _____displaying on screen, I have ____data on hand and I'm doing______".

If the OS says "sorry bud, you gotta go away cause the guy that's always fondling me(you the user) needs to do something else, go away" then that program is killed and that information saved.

Next time you open up your app, the OS asks "alright, I just got finished showing this guy settings, now he needs you again, do you remember where you were when I sent you away?"

If yes, then boom, you are back to where you were. If not then, your app goes back to square one.

Seems opera mini isn't properly implementing their save states. It's an issue with the application not the OS.
[Nexus One General] ztm.000:
YOU MUST UNDERSTAND THAT THIS IS OPERA'S FAULT. THE DEVELOPERS DID NOT PROPERLY WRITE THE PROGRAM TO SAVE CURRENT STATE. IT HAS NOTHING TO DO WITH ANDROID OS

This is already an issue that has been brought up in a previous post. They came to the conclusion that it was the app, and in all common sense, it is the app. There is no reason to blame the OS, that is Android. Might i recommend rooting your phone and uploading a fine ROM like CyanogenMOD? I think it would be on your best interest to do so.
[Nexus One General] RogerPodacter:
just to be clear I literally haven't opened tuneWiki in 3 weeks, and have done many reboots since then. it was just an example of one of the many apps I see running in the background, which I've never opened in weeks, yet the one I just used is the first to close.

to the other replies, I'm not confused and understand what's going on. I just think its a major flaw whether opera is saving state correctly or not.

9 out of 10 times I can switch away, do my tasks, come back and opera is still there where I was browsing. I just don't like the inconsistency. I feel like I have nocontrol over what and how I want my apps to run.

also if opera mini DID have to save my tabs and reload them, then that would be horrible as it takes certain time to get the proxy server going and then reload the pages. the current method where It's just instantly there, still in memory, is the best way for it to happen. and it DOES work this way majority of the time.
[Nexus One General] Paul22000:
Correct! Opera, not Android.

So you do understand.

Hmm, ok, maybe not.

Instead of "my apps", that should read "this one particular app".

P.S. You didn't answer my question.

.
[Nexus One General] GlenH:
Just use a custom ROM with all the RAM enabled. Then you'll have maybe ~150mb to play with and no problems.
[Nexus One General] RogerPodacter:
yeah you guys are right though, i am just gonna root this thing so it opens up the other half of my RAM, then this will NEVER happen!

but i did wanna wait till 2.2 was released...i can still get the 2.2 update while rooted, right?
[Nexus One General] Paul22000:
You'll get it weeks before people who haven't rooted ;)
[Nexus One General] RogerPodacter:
is this the question i didnt answer? well i dont install many apps, probably only 10 apps or so that i have installed. but no none of them seem to exhibit this behavior except for opera mini.
[Nexus One General] Paul22000:
Yes.

That was my point :) :cool:

You keep criticizing Android for a fault of Opera's.
[Nexus One General] RogerPodacter:
i'm criticizing android because regardless it's not the best way an OS can multi task. there are much much better ways. for starters, they should keep the same mechanism they have now which decides if it needs more RAM and saves state of the app, but apply it to ONLY the apps the user specifically opens. if i havent opened tunewiki in 4 weeks, it should not in a million years be opened automatically by the OS.
[Nexus One General] BigDamHero:
I understand what you are trying to say here. It is this bit that people just aren't reading properly:

You are (I think) unhappy fundamentally with how Android manages processes. You'd like to be able to tell it what it can and cannot kill off when the ram gets low. I'd like this too – to be able to say “well I always want Opera running” and have it not kill it off when ram gets low. Equally I'd like to be able to tell the system what the most expendable processes are. I'd live it to kill Amazon MP3 before it killed my browser! Sometimes it just doesn't seem to make efficient choices. Amazon MP3 bloody starts on its own!! Why?!!?

However as you say Opera isn't behaving as it should really, and if it saved its state properly there would be less of a problem (though still an increased load time when you switch back to it). You sound like you have a pretty firm grasp on it anyway, but I thought this was a really good summary of where Opera's problem lies:

And Paul for god's sake you are driving me nuts! Please read threads before you hit the reply button. You did this on my thread earlier and you did it earlier in this thread too when you missed the fact he was on the stock rom. Read this – then read the top quote in this post.

He's not doing this. If anything he is criticising Android for its own sake. He just doesn't like how Android manages processes, regardless of the problem Opera has. Whether you agree or not you should at least realise the point he is making.

Sort....of, but this is a bit misleading. You won't get the actual Google update, but the enhancements that it contains often find their way into custom roms before their official release (or developers come up with their own code that does the same thing).

However if I were you I would wait for the official distribution of 2.2. Its rumoured to be coming out around 19 May (though you've probably already seen that on the forums). Once again its only rumour but one of the enhancements is supposedly going to be “releasing” the currently unused ram. If you can live with your current set-up until the end of May I'd do that. You can always root later on if FroYo isn't all it is cracked up to be.

Some 2.2 info - http://www.phonesreview.co.uk/2010/04/22/htc-magic-running-android-2-2-aka-froyo-new-features/ google for more

Let us know how you get on anyway.

Thanks
[Nexus One General] :
The OS doesn't not call ANY apps to open except system apps. If tunewiki is starting up everytime you boot, it's because tunewiki is set to autostart on boot.

Again, you're blaming poor code from an application on the OS.

Sidenote: You can use any of the various task managers on the market to exempt any app from being auto killed by the OS. "System Panel App/Task Manager" is one app that includes such functionality.
[Nexus One General] DarkDvr:
This is opera's problem, they don't follow the way "pages" or current status data objects are passed in android.
[Nexus One General] RogerPodacter:
interesting. so how do I change apps like tuneWiki to not auto start on boot up? I couldn't find that option anywhere in tuneWiki's settings. do I need to use a task manager for that?
[Nexus One General] Paul22000:
It's just a poorly written app most likely.

You can get an Auto Killer app to kill it every time you turn off the screen. But they might have written code to auto-start, which means it would be killing battery auto-killing and auto-starting all the time.

I'd just leave it alone. Have you noticed any dramatic drops in battery life since installing TuneWiki?

Actually, you said you haven't used it more than 4 weeks. Just uninstall it. :cool:
[Nexus One General] robkoehler:
Autostarts. Get it.

Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
[Nexus One General] ztm.000:
HEY EVERYONE, i forgot where to check to see how much ram we have... how do we check/know? CM 506
[G1 Q&A, Help & Troubleshooting] rootlinuxusr:
I press and hold the [home] and [power] keys and it boots to nothing, even tried the [camera] and [power] keys on my G1, nothing. Current rom/SPL posted below, is it possible there's a changed key setting for the rom?

Rom: CaNNoN202-CompleteEclair-v2.0

SPL: Danger

Firmware version 2.1

Baseband Version 62.50S.20.17U_2.22.19.26I

Kernel 2.6.29.6-bfs-Firerat

Build Complete Eclair 2.0
[G1 Q&A, Help & Troubleshooting] peshal:
Try reflashing the recovery image via terminal

$su

#flash_image recovery /sdcard/recovery.img "assuming your recovery image is n root of sdcard and you renamed the recovery image as recovery.img"

#reboot recovery

See if that boots to recovery
[G1 Q&A, Help & Troubleshooting] techn0crat:
How can you get to the terminal if the phone won't boot past the first screen?

camera+power goes to the first screen, home + power goes to the first screen, trackball + power doesn't load a screen, but turns a blue led on.

I have adb. How can I do it using that??
[G1 Q&A, Help & Troubleshooting] billquinn1:
Does adb see your device?

At cmd prompt type

adb devices

If it shows up type

adb remount

If that works...

adb shell

You will have

#

Type the commands in the post above after putting a recovery image on your sd card.

If the first step does not work, you may be bricked.
[G1 Q&A, Help & Troubleshooting] rootlinuxusr:
Just to clarify, the phone does boot up, and is fully functional aside from the [home] key working. I assume if I follow those directions, I could possibly use the android default img, and restore that, and unroot the phone for return possibilities?
[G1 Q&A, Help & Troubleshooting] billquinn1:
From cmd prompt type

adb reboot recovery

See what it does.
[G1 Q&A, Help & Troubleshooting] rootlinuxusr:
I tried to type that and now my E, and R keys are dead...I even tried purchasing Better Terminal Emulator on the news that I can use the virtual keyboard and/or copy paste text. While this works, it allows SU, but when I type

adb reboot recovery

it says "sh: adb: not found" So what I figured I'm stuck doing is to restore it to non-root status, or is there a way I can run commands on it from my laptop? The phone itself works great, makes calls, sends txt messages, just won't let me press the [home] key, and now apparently the E, and R keys.

EDIT:

I installed JDK, and the ADB packages, and can get it to the recovery screen from that menu, but I've run into another issue in regards to installing any update.zip through the cyanogen recovery menu. That being that you have to press [home] to confirm you want to do any action...
[G1 Q&A, Help & Troubleshooting] r3s-rt:
adb is ran from your computer, not terminal.

and yes, your home key not working means you won't be flashing a new rom through recovery anytime soon.
[G1 Q&A, Help & Troubleshooting] rootlinuxusr:
Once I figure out how to push an update package(rc33) and upgrade to cupcake/donut, will it be effectively unrooted(for purposes of sending it back)?
[G1 Q&A, Help & Troubleshooting] r3s-rt:
you don't push it. and you don't technically "upgrade" to cupcake. you downgrade. :P

however, yes, it will be ok to send back.

here's how:

http://xdaforums.com/showthread.php?t=491350
[Desire Themes and Apps] alanjp168:
There seems to be a quite nice lockscreen app on the market - Lockbot Pro which costs $3.5! It has several lockscreen styles that

you can use and it includes the iphones as well. Quite amazing! But.. while most of the feedbacks are great but some say it breaks

the notification bar and lags when locking or does not lock at all(mostly on G1 and Droid.). :eek:

So if anyone here actually tried it on the Desire please tell me how it performs. very much appreciated!
[Desire Themes and Apps] keleko:
I've tried the free version and its pretty good apart from one major issue.........the Home button is still active!!!

When the phone is locked the Home button will wake the phone up without a lock screen. Once this has been fixed then it will be well worth $3.50 :)
[Desire Themes and Apps] ENDOSKELLETONT800:
I have the Lockbot Pro 1.3 on my HTC Desire and it works fine but you can´t disable the home button ;(
[Desire Themes and Apps] Eddiemc:
I tried it, and here's my take:

Full lock replacement, lots of looks and plenty of themes. Choose your own background image. You can choose weither or not to have the notification bar on lockscreen, and if you do you can access it the same way as when you're in home.

The lag is there, but nothing major. Basically if you lock and unlock within half a sec, you'll notice the lag. As long as you lock, leave it, and unlock later (normal usage) there's no problem.

I don't think it shows album info, sms or even alarms on the lockscreen.... But I didn't really pay attention to this because:

My biggest issue is that its an app, not a lockscreen, so it gives you NO security at all. The main reason why i do not use lockbot is that I need a security pattern.

This one bypasses androids security lock, but has its own built in version which is ok. You can choose either code or pattern.

BUT the problem is that you can hit home and you bypass all security! Whats the point of security if you can bypass it??

Hit home and lock gone, security or not.

Also another issue is that security pattern delay app doesn't work. I want security to kick in after 30 min...

You can wake screen with all buttons, which is nice, but no exclude function. (I dont wanna wake it with volume buttons..)

If lockbot adds security delay timer and makes sure you cannot bypass it no matter what, and also adds an option to chose which buttons to wake screen with, it would be the best app out there.

ATM i think it stinks (reason: security), but thats just my 2 cents;)
[Desire Themes and Apps] simonthor:
newest

I just tried the newest version. I think they fixed the home button thing. But it's kinda hard choosing a background for it. (and it's not so smooth as the default lock)
[Desire Themes and Apps] JonasDroid:
Home button bug is finally fixed.

But it really sucks that I'm in a country where I can't dowload paid apps. Is there any other lib where I can BUY! it?

Anyone who knows if I would be able to download it if I would go to the Netherlands?
[Desire Themes and Apps] snudel:
for me its very smooth. the background choosing sucks really. but you do that once in a while.

lockbot pro works very well

the only disadvantage is that its not locking on incoming call
[Desire Themes and Apps] berre:
second that! great app, but this is something that should be fixed!

anybody know how to reach the developer to check if this is planned or not?

Thx

B
[Desire Themes and Apps] MasDroid:
I currently use WidgetLocker - it allows you to set different styled lockscreens (e.g. vanilla stock, vanilla rotary, etc) and even add widgets to the lockscreen.

Cool app imo ;)
[Android Software/Hacking General [Developers Only]] jsujendro:
hi!

where can i download the su (binaries) and Superuser.apk (for rooting) that is compatible with Milestone running Android 2.1?

thanks and regards.
[Android Software/Hacking General [Developers Only]] moosefist:
check one of the cyanogen roms for the droid. if i understand, koush puts them together. I also would suggest checking out modmymoto.com and androidspin.com for droid/milestone development.
[HD2 General] redzepplun:
I have been clipping along just fine tweaking my phone via cabinet files. Now for some reason I no longer have the option to convert files into cabs. I had this problem a couple weeks ago but somehow I found a string to enter into my registry editor and that fixed the prob. Now I can't for the life of me find the string again to do the reg edit on my home PC......:confused:

Anyone know by chance what the string is?

Gracias
[HD2 General] redzepplun:
Anyone have an idea.
[HD2 General] samsamuel:
there is no built in option to convert files to cabs. Most people use something like winCEcabmanager on the PC to create cabs.

Maybe it was something you had installed? certainly nothing ive seen.(but then again im not an app whore, heh)
[myTouch 3G, Magic Android Development] collins521:
Alright so I just picked up a MT3G that's a 32B, the previous person has 2.1 and it's rooted but he didn't do it and had someone else do it. So before I start just going flash crazy and seeing what I come up with I figured I'd ask you guys on the best way to start. Problem I'm running into is when I turn off the phone and hold the back button and hit the red button the screen goes all blurry and hard to see the screen to figure out everything.

I can tell I'm a 32B, the HBoot section is extremely hard to read but I can make out 1.33, and the Radio is 2.22.19.60 I'm guessing. Weird thing is if I reboot it from the fast boot screen it will be blurry but when I hit the red button to turn off the screen and then back on it comes back into focus.

What's the best way to start fresh and figure out what the person that rooted it and updated it did.

Any help would be greatly appreciated!

****

Info from the Settings - About Phone:

Baseband Version:62.50S.20.17U_2.22.19.26I

Kernal Version: 2.6.29.6-gf2b4a65-dirty

Build Number: aosp_sapphire_us-eng 2.1 ERD79 eng. ben.20100414.191543 test-keys
[myTouch 3G, Magic Android Development] knny1491:
Do you want to root from fresh? if so download the Sappimg.nbh file for your phone, use that to downgrade it to 1.5, then use flashrec.apk to install the CM recovery image, then use that image to flash your chosen rom(For a 32b I suggest superD or the latest Cyanogen, or a 2.1 rom fo your choice.)
[myTouch 3G, Magic Android Development] collins521:
Ya I basically want to start fresh...what worries me is the out of focus screen whenever I go into the fast boot...anyone hear of that?

Also to downgrade to 1.5, do you mean the stock 1.5 from T-Mobile?
[myTouch 3G, Magic Android Development] knny1491:
Yes that is correct.

Sent from my ipad using the XDA mobile application powered by Tapatalk
[myTouch 3G, Magic Android Development] collins521:
Ok, so since this is all new to me what's the best way to load the recovery from?
[myTouch 3G, Magic Android Development] crypysmoker:
Turn of the phone... then hold home and power till the recovery boots and see which it is. If its newer, then you can connect usb, transfer whatever rom over, wipe and flash.
[Hero CDMA Themes and Apps] Jedis:
Do you have the same problem with the NexusMod live wallpaper randomly disappearing when you wake the phone up?

While my phone is plugged into my computer and is charging, everytime I wake the phone up, the live wallpaper is still there and chugging along. However, when the phone is not plugged into the computer or charging, the phone randomly loses the live wallpaper and reverts to my old wallpaper.

I'm just wondering if perhaps the phone is doing this to conserve on the battery or if it's just a glitch?

Does anyone else have this same issue? Would appreciate it if people could test having it connected to the computer/not connected and post their results. Perhaps someone could chime in with a fix if we collect some data.

Thanks!
[Hero CDMA Themes and Apps] mrinehart93:
That's a known problem, and if I'm not mistaken, the LWP fix posted in Flip'z Fresh ROM thread has the fix for download.
[Hero CDMA Themes and Apps] smw6180:
Yep. But it installs a different version of OpenGL which breaks all kinds of things, not the least of which slows Gallery down to a crawl, busts 3d in Google Maps, etc.

It's not worth it, in my opinion.
[Hero CDMA Themes and Apps] abcdfv:
Take note that the OpenGL "fix" breaks OpenGL for everything but LWP. GoogleNav will have no on screen nav, just audio, any games that use OpenGL will be damn near unplayable, etc etc.
[Hero CDMA Themes and Apps] mrinehart93:
Hence the reason I decided to just screw LWP's all together and put the old OpenGL on my rom... LWP's just seem to be too much of a hassle.
[Hero CDMA Themes and Apps] smw6180:
Some of them work just fine. Digital Rain, Bezier, a couple others, on the version that comes with the current roms.
[Hero CDMA Themes and Apps] Street_Knowledge:
well that explains why my nav was acting janky. any fix for this?
[Hero CDMA Themes and Apps] abcdfv:
I just reflashed.