Develop Bugs

Home screen reboots after returning to it or pressing home button

Lately everytime I pressed the home button or returned to the home screen the home screen reboots with a "Loading..." box and no inputs are accepted except dragging down the notification bar. Any ideas? Memory issues?
I've tried uninstalling a few apps to free up some memory, but nothing seems to really work. Also checked if my task killer was "killing" the home screen in some way but didn't see anything wrong there.
Currently running LeeDroid 2.2f Desire GSM
Any help would be appreciated!

Ideas anyone??

Boot in safe mode and see if it happens again.
If it doesn't it's a third party process that is causing it.
If it does, you'll probably need to reflash, but first you may try to erase cache and data of the "htc sense" system process.

3722 said:
Boot in safe mode and see if it happens again.
If it doesn't it's a third party process that is causing it.
If it does, you'll probably need to reflash, but first you may try to erase cache and data of the "htc sense" system process.
Click to expand...
Click to collapse
By "safe mode" do you mean recovery or bootloader or what is safe mode?
Tried clearing data on HTC Sense process but all it did was erase my home screens, still has to reload the sense UI everytime I exit a full screen app.
I guess I'll try to reflash sometime, maybe I'll give cyanogen a try.

To enter safe mode you need to power on your device while holding the menu button till the home screen shows up.

Are you rooted? Try clearing cache and dalvik cache? I used to have that problem and clearing the caches helped (I have sense moved on to other roms though)

Tried safe mode and cleared both caches no apparent difference.
Will try updating to Cyanogen and see if the problem is persistent. Will update with how this goes!

Let me know how this goes, I recently flashed LeeDroid 2.2f and started to experience the exact same problem.
Flashed to 2.3b yesterday, so far no homescreen problems but we'll see how it goes.

Just flashed most recent Cyanogen, S-OFF, custom MTD partition, Firerat's a2sd, with launcher pro plus and quickdesk.
No more homescreen reloads!
But I must say this is the best configuration I've used thus far! Love the Cyanogen features compared to the more simple LeeDroid feature list and I can configure launcher pro to work the same as Sense but better. also have a lot more space for apps as well.
For those who dont know what quickdesk is TRY IT. IT IS AWESOME. Works swimmingly with any homescreen launcher.

Hmm, might give it a try then!
Is that Cyanogen or DeFroST?#
Cheers.

b0ng0 said:
Hmm, might give it a try then!
Is that Cyanogen or DeFroST?#
Cheers.
Click to expand...
Click to collapse
Cyanogen. I don't see anything in the features list in DeFroST that Cyanogen doesn't already have.

[Q] How do I keep Sense from being shutdown due to OOM

Ever since I received the upgrade to gingerbread (first 4.06 and now 4.08), Sense will get shut down when I am in other applications. Then when I hit the home button I get the white "HTC" screen and then sense has to start up and reload all my home screens and widgets. It typically happens when I use the browser but has sometimes happens when in other applications.
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
* renice <htc.com.launcher process> -20
* installed Auto memory manager (AMM) and set it to "aggressive" mode
* using AMM reset the priority of "HTC Sense" from 6 down to 2 and specified "always keep alive" but the kernel seems to just reset the priority.
What's really annoying is when I look at the list of processes, things like facebook and weatherbug have a higher (meaning lower number) priority than Sense. Does anyone have any idea how to force Sense to be given priority over other apps so it can stop from being shut down?
tia,
John

swindelljd said:
Ever since I received the upgrade to gingerbread (first 4.06 and now 4.08), Sense will get shut down when I am in other applications. Then when I hit the home button I get the white "HTC" screen and then sense has to start up and reload all my home screens and widgets. It typically happens when I use the browser but has sometimes happens when in other applications.
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
* renice <htc.com.launcher process> -20
* installed Auto memory manager (AMM) and set it to "aggressive" mode
* using AMM reset the priority of "HTC Sense" from 6 down to 2 and specified "always keep alive" but the kernel seems to just reset the priority.
What's really annoying is when I look at the list of processes, things like facebook and weatherbug have a higher (meaning lower number) priority than Sense. Does anyone have any idea how to force Sense to be given priority over other apps so it can stop from being shut down?
tia,
John
Click to expand...
Click to collapse
with any OTA its recommended to do a factory reset. did you do this? its a pain to loss all your data but it might fix your problems.
sorry i didnt have my morning coffee yet.... If you wiped dalvik then that means you have root. your phone is not shutting down. something is killing rosie (the sense launcher.) and that why the white HTC splash screen comes up again. What rom are you runing? i know its the OTA but is it the RUU or one of the devs roms based off RUU??

swindelljd said:
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
Click to expand...
Click to collapse
If you read his entire post you would know he did a factory reset.
My best guess is to go back to stock sense before the last ota (by rooting and flashing or whatever way you wish..sbf or whatever) then download the ota on your computer and try manually updating your phone..if that doesn't work then I don't know
/Droid3

What about bulletproofing the launcher with V6 Supercharger?
Sent from my ADR6300 using XDA App

RamAir02 said:
What about bulletproofing the launcher with V6 Supercharger?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
That worked for me.

synisterwolf said:
... i know its the OTA but is it the RUU or one of the devs roms based off RUU??
Click to expand...
Click to collapse
Most recently I am running the stock 4.08 version starting with applying the 4.06 RUU and then applying the 4.06 to 4.08 update file. I do have root and really use it for monitoring/managing the /data/data partition.
RamAir02 said:
What about bulletproofing the launcher with V6 Supercharger?
Click to expand...
Click to collapse
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.

swindelljd said:
Most recently I am running the stock 4.08 version starting with applying the 4.06 RUU and then applying the 4.06 to 4.08 update file. I do have root and really use it for monitoring/managing the /data/data partition.
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
Click to expand...
Click to collapse
There's no risk of brick with v6. It just tweaked a couple parts of the kernel.
Sent from my ADR6300 using Tapatalk

swindelljd said:
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
Click to expand...
Click to collapse
You'll just want to make sure you have busybox 1.18.2 installed, then run the script with Script Manager, and you'll want to select either 6 or 7 (I use option 7), then reboot. It won't brick your phone, but you can always run a nandroid backup to have something to fall back to.

RMarkwald said:
You'll just want to make sure you have busybox 1.18.2 installed, then run the script with Script Manager, and you'll want to select either 6 or 7 (I use option 7), then reboot. It won't brick your phone, but you can always run a nandroid backup to have something to fall back to.
Click to expand...
Click to collapse
Is this the correct script manager app: https://market.android.com/details?id=os.tools.scriptmanager ?
Noob question, how do I check which version of busybox I have installed. I found one in TitaniumBackup that is 1.18.14 but that looks like it is local to TitaniumBackup. I did find "toolbox" in /system/bin which looks like the stock rom's version of busybox. Is this what I should be looking at or is busybox installed somewhere else?

swindelljd said:
Is this the correct script manager app: https://market.android.com/details?id=os.tools.scriptmanager ?
Noob question, how do I check which version of busybox I have installed. I found one in TitaniumBackup that is 1.18.14 but that looks like it is local to TitaniumBackup. I did find "toolbox" in /system/bin which looks like the stock rom's version of busybox. Is this what I should be looking at or is busybox installed somewhere else?
Click to expand...
Click to collapse
Yes, that's the app.
Download this app as well: Busybox Installer
It'll tell you what version you have (if you have it), then you can select what version you want to install. No need to adjust where it installs, just leave that at the default, just select version 1.18.2, then hit Install.

I read through the script just to get a sense (no pun intended) of what it was doing and then installed Busybox 1.18.2 and applied setting 11 "Hard to kill launcher" from the script. I've done a bunch of browsing to sites that normally caused Sense to get shut down and so far so good.
I initially installed busybox with symlinks and it the script threw a ton of errors so I reinstalled with symlinks to fix that.
Thanks for all the help. For completeness, here is a link to V6 Supercharger so all the links are in this one thread http://forum.xda-developers.com/showthread.php?t=991276 .
One thing I did have to change because I am running Sense and not a stock android launcher is the name of the launcher process itself.
On line 64, I changed this "pidof com.android.launcher" to this "pidof com.htc.launcher"

will the V6 script it just tells the android memory system to not reclaim memory from the launcher app so it stays on no matter what happens. only way to kill it is to go to settings and FC the launcher. also with the script you cant brick the phone because its not ran till after the phone boots. The term brick means : that the phone will not boot at all. you just have a phone that does nothing at all not even turn on. You can soft brick the phone meaning the software will not boot. all you need to do is make a backup before installing the script and you will always have a way back if anything happens.
for me i run the beta V6 script option under -=*512HP*=- which is more of a balanced one with bullet prof launcher and its is wonderful. but each phone is different so just try them out and see what works for you.

synisterwolf said:
... You can soft brick the phone meaning the software will not boot. ...
Click to expand...
Click to collapse
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.

swindelljd said:
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
Click to expand...
Click to collapse
Yeah, you kinda need that one there!
Good job getting it replaced using adb and all, good to hear you figured it out!

swindelljd said:
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
Click to expand...
Click to collapse
yes that will do it. lol i did that a long time ago when i wanted to edit it my fat finger deleted it. now as good practice i always make a copy of it but add .bak at the end of it so if i do delete it i can just replace it before reboot.

I've been using options 1, 8, and 12 in the V6 Supercharger and my phone has been running great. What options did everyone else choose?

[Q] Widgets background problem

Hi,
I am using RunnyDrOiD v5.0 on my desire z with sense 3.5 / Android 2.3.5
Out of sudden, and without installing new application, I am not able to see the background of the widgets (weather, clock, mail ...) and the icon description on the screen locker are showing in big red.
Attached are the pictures of whats going on.
Any idea what is the problem and the possible resolutions? Hope I don't have to install the ROM again and wipe data.
Thanks in advance.

Seems like your launcher doesn't start properly.. If rebooting doesn't solve your problem, then you can try to reflash without wiping. All System files are then put back to their original state, but your settings and installed apk's are not touched.
If that doesn't work, I think that you'll have to reflash with a full wipe.

lineaira said:
Seems like your launcher doesn't start properly.. If rebooting doesn't solve your problem, then you can try to reflash without wiping. All System files are then put back to their original state, but your settings and installed apk's are not touched.
If that doesn't work, I think that you'll have to reflash with a full wipe.
Click to expand...
Click to collapse
Thanks man... SOLVED!
Re-flashed the ROM without wipe and everything works fine now.
Any idea why this happened? so that to avoid in future.

Saldy I have no clue.. Most likely there were some settings wrong or the launcher took to much ram memory to start properly, but I can't tell for sure. If this happends again, just reflash, and it works again.

[Q] can't get clock app working after attempted install of 3.0 version

Verizon version running 4.2.2 stock rooted. Tried installing the 3.0 desk clock apk from android 4.4. I first backed up the apk with titanium, then removed 2.3.0. Then installed the 3.0 apk. The new app crashed immediately. Tried to uninstall 3.0 and restore 2.3 but now that crashes too. Tried everything from reboots and reinstalls, even recovery mode and wiping dalvik cache. Nothing works and I am stuck with no clock app.
Help.

Got the same issue a few minutes ago! I fixed it by
Settings > Apps > all > Clock ( the smaller one, about 0,88 in my case. Not the bigger one with 3mb)
Clear data in the main (bigger) App.
Working for me perfect so far! I guess the FC is caused by the clock settings for lock screen... Hope that works for you too!

Lizard82 said:
Got the same issue a few minutes ago! I fixed it by
Settings > Apps > all > Clock ( the smaller one, about 0,88 in my case. Not the bigger one with 3mb)
Clear data in the main (bigger) App.
Working for me perfect so far! I guess the FC is caused by the clock settings for lock screen... Hope that works for you too!
Click to expand...
Click to collapse
No dice. Nothing works for me. I fear I may need to re-flash the stock ROM. Although, at this point I might as well flash a 4.3 ROM since Verizon is still holding out.

Just did a factory reset and still the clock crashes....... arrrrgh!

Had to do a full wipe, flash 4.2.2 and re-root. But now my clock works.
Next time I will wait for the update!

[Q] System Strings Corrupted

Hi, I've been trying to google this for a while, but can't seem to find what I need.
I just installed the stock rooted deodexed rom from captain throwback: http://forum.xda-developers.com/showthread.php?t=1671395
specifically 5.07.651.6 Stock Rooted - Deodexed
Everything worked great. Then I installed CT's circle battery mod, a random quick settings mod, and a random advanced power menu mod, cleared cache and dalvik cache, and rebooted multiple times.
Now some system strings are strange, like when adjusting the normal volume, it says "Playing through bluetooth" although nothing is connected via bluetooth or headphones, etc. Also when you pull down the top bar, it used to say "click to enable USB debugging" or something like that, but now it just says "Select input method", although everything seems to still function properly.
Where can I find these corrupted system strings to adjust them back?
Thanks

Just reflash the ROM. Not all of those old mods will work on the newest base. I believe there's some hex-editing that needs to be done in a framework file somewhere to fix that, but I don't know anymore than that.

Thanks for the quick response. In that case, which mods would you recommend as far as getting circle battery mod, quick settings, and advanced power menu? Should I leave it alone if I don't want to corrupt the strings again?

linucksrox said:
Thanks for the quick response. In that case, which mods would you recommend as far as getting circle battery mod, quick settings, and advanced power menu? Should I leave it alone if I don't want to corrupt the strings again?
Click to expand...
Click to collapse
I can't recommend any mods, as I haven't tested them. But the Circle Battery you should still be able to do yourself with UOT Kitchen. When it comes to APM & Quick Settings, that's where you're going to run into issues.

Awesome. I'm pretty sure it didn't happen until the APM mod, so I'll abandon that one. Thanks again for your help.
Edit: reflashing worked, and I was able to bake the honeycomb circle battery using UOT kitchen, plus the quicksettings I got from tommytomatoe works great. I wonder if I could have fixed the original issue by reinstalling the original framework-res.apk, systemUI.apk, and/or com.htc.resources.apk instead of having to reflash the whole rom. I guess I'll find out next time