Develop Bugs

911! need help something wrong

k i read about an app called spare parts on here so i figured hey i'll try it out. i did saw what extra setting were there and decided i wasn't gonna use it didn't even change any settings.
after opening the app and then pressing home something wierd happened i saw a white screen with HTC in green in the center for about 3-5 seconds my backround with a loading pop-up and nothing else for about another 3-5 seconds. this is happening every time i press the home button or exit out of an app. it's getting infuriating, i'm also getting wicked bad lagg in sense and lot's of hang up's and force closes. also wicked bad battery life. i don't know what to do to fix it.
i have the OTA and rooted last night with unrevoked method, this morning is when i tried the app around 10 or 11 not sure last couple days is a blur.
can anyone help, how can i restore what i had previously, do i have to do a full wipe.

nobody...... anyone plz, it is cripling my evo

thorpe24 said:
k i read about an app called spare parts on here so i figured hey i'll try it out. i did saw what extra setting were there and decided i wasn't gonna use it didn't even change any settings.
after opening the app and then pressing home something wierd happened i saw a white screen with HTC in green in the center for about 3-5 seconds my backround with a loading pop-up and nothing else for about another 3-5 seconds. this is happening every time i press the home button or exit out of an app. it's getting infuriating, i'm also getting wicked bad lagg in sense and lot's of hang up's and force closes. also wicked bad battery life. i don't know what to do to fix it.
i have the OTA and rooted last night with unrevoked method, this morning is when i tried the app around 10 or 11 not sure last couple days is a blur.
can anyone help, how can i restore what i had previously, do i have to do a full wipe.
Click to expand...
Click to collapse
get used to it if you intend to use sense, the screen you speak of is sort of like the htc sense/rosie intro. If you dont like it you can go vanilla and use another launcher, like adw froyo,launcherpro, or even the extra launcher thats included....

Sounds like you enabled aggressive handling of apps. Can you get in there to turn it off?

jmxp69 said:
Sounds like you enabled aggressive handling of apps. Can you get in there to turn it off?
Click to expand...
Click to collapse
Or just do a factory reset.

also, you are experiencing some isolated problems which leads me to beleive the issue is software related rather than hardware.I have experienced NOT ONE of the issues you speak of. Make sure you update prl. I can vouch for that one. My data was 90% broken till i did. Also try and wipe data, that would prolly fix everything as well.....FYI, i cannot gurantee the problem lies with your hardware OR software. Thats just my diagnosis. Good luck

Thats what it was the agressive handling of processes thanks alot guys feel like a fool.....
Sent from my PC36100 using Tapatalk

thorpe24 said:
Thats what it was the agressive handling of processes thanks alot guys feel like a fool.....
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Heh...I did that once on my hero. I know the feeling.

some versions of spare parts come with a launcher. the problem is that when you press the home button now, it's trying to goof with /system, which is forcing the reboot. even though you may be rooted, you don't have rw privileges in /system while messing with android.
you may be able to get away with accessing /system and erasing your goofy installed spare parts app. you'll have to do that through adb shell, and the custom recovery. do a search for 'remove apps', you should find it easily enough. i think the thread was moved from dev to general, or q and a.
anything that will call a write to /system (i.e. a rooted app that needs access to it to work right) has the potential to cause the phone to reboot. when i installed adfree, it had the same effect. trying to install hosts (which write to /system/etc) caused a reboot. i had to install hosts through recovery with a push after remount.
hope that helps

Hmm I installed autokiller and it appears to work doesn't mess with anything that is
I really dunno a way of testing that its actually working though if you where looking for a way to manage memory

I was using a task killer but read up on stuff and turned it off just keeping it in case I need it for something that wont close and the phone is running great and battery life keeps getting better and better.
Sent from my PC36100 using Tapatalk

autokiller
People you need to be careful with autokillers!
Make sure that you are not closing down sense items.
Put anything that says htc or sense on ignore.
If not you are shutting down parts of sense. Then sense has to reboot. Witch is why you see the white screen with the htc logo in the middle.

[Q] Answer phone

every other time my phone rings I cant answer it. The accept button just wont move?? is it just me or have anyone else had this error I have a dezire z

Do you have set CPU set to 245MHz @ screen off?

no i dont, why?

Well that could be one cause, maybe it's a bad app causing your phone to temporarily freeze? Can you slide it the other way and ignore the call?

Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.

Utorrent76 said:
Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.
Click to expand...
Click to collapse
why do you suggest this? how do you know hes using kernels? im just trying to see what your connection to the solution is -its quite a specific answer to a problem that hasnt really been examined. what rom is he on, etc before you can start talking about kernels -- so can you clarify?
accept button - do you mean the slider? if you have cmod - just activate settings to disable lock menu/trackball/ whatever --also you could try the no-lock unless you have security issues.
if no cmod -- theres apps to reduce the lockage -- that may help you get your phone calls but still doesnt fix the problem? you could try enomther's and his awesome extra ssettings app has all those options

Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.

jaypeg123 said:
Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.
Click to expand...
Click to collapse
If its a stock DESIRE Z and not a G2 then I think it's safe to assume its got sense on it and not AOSP. Did you try hard resetting it? (power down and pulling the battery for at least 30 sec) other than that id check for any OTA updates in the settings menu. OR if you're willing/know how, you can root it and run CM or virtuous. Both ROMs are excellent. If you do that and the problem persists, it could very well be a faulty unit. You have a lot of options!

I found I had problems answering calls when I had a specific make of screen protector on the phone. As soon as I took that off and went back to a previous one I'd used then it was fine again ! It's a long shot, but I thought I'd throw it in there.

Problem solved, An update did the trick, thanks for helping out my friends,

same problem , cannot answer with swipe keys
I have the same problem, which update did you use

same problem , cannot answer with swipe keys
I have the same problem, which update did you use

[Q] Sporadic Black Screen of Death, any solution?

I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2

nomad4ever said:
I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Same thing here, never had an issue with 4.1.2 but now it happens 2-3 times a day
Sent from my Galaxy Nexus using xda premium

same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..

andQlimax said:
same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..
Click to expand...
Click to collapse
Let me know how that works... I have been having this problem also. Screen is blank every 2 days it happens once. Ever since 4.2 update. Before that I had no issues like this.
Also un related but I've started to notice faint horizontal lines in my screen. I use auto brightness. Is this normal or return for warranty?

i can confirm this happens to me too.
4.2 stock only rooted with custom recovery.

Same here folks, It may a bug in the 4.2 builds since Sprint did not officially release 4.2 yet.

This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).

same issue here, I'll try to keep the brightness to manual to see if it works

chanchan305 said:
same issue here, I'll try to keep the brightness to manual to see if it works
Click to expand...
Click to collapse
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.

MondoMor said:
This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).
Click to expand...
Click to collapse
bfprd0 said:
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.
Click to expand...
Click to collapse
I experience this issue, but not that frequent. Once every 4 or 5 days, i don't know. I've managed to pull a logcat today as i was near of pc, as posted before, adb/phone is responsive, it even locks the screen normally, there was nothing useful on dmesg. I don't normally use auto-brightness, but enabled it a little while ago, although now i'm not sure if it was enabled the first time it happened. This last time, it wasn't enabled, that I'm sure.
It happened to me both when I was using XDA-app. I have almost 0 user apps installed right now, also uninstalled XDA. Reporting back in a few.

the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude

ogdobber said:
the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude
Click to expand...
Click to collapse
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.

bk201doesntexist said:
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.
Click to expand...
Click to collapse
ok...star this issue https://code.google.com/p/android/issues/detail?id=40019

[Q] Galaxy Nexus Sleep of Death

Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
 The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
 The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
 The problem seems to be irrelevant to the Apps installed.
 The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
 I manually reboot my phone at most every two days.
Solutions tried, but don’t work
 Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
 Turning off the auto-brightness control, as suggested by some post on the Internet.

Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app

Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.

Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.

Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?

Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...

eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.

Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.

I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL

I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.

NVM
Screen still goes dead.
Anyone find an actual fix to this?

isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)

Can't press 'Install' when installing an APK

Good evening, just lately I have encountered a bug when trying to install APK's. When I go to install via Package Installer it will open up the screen and when I go to press next it doesn't do anything, I have tried rotating the screen and pressing Next and it just doesn't work whatsoever...
I powered off my device and powered back on and this seemed like it fixed the problem.
Is/has anyone else encountered this? I've also noticed ometimes when typing on the keyboard the sound goes tinny for 5 seconds or so and go back to normal, it's been like this since unboxing too.

I haven't had this issue exactly, but when I install a new app and it asks for permission to access my location/storage/etc.. I can't press Allow.. I can press Deny though no problem at all. Right now I'm manually going into apps/permissions and granting all my apps whatever I think it needs.. Just a pain to do it that way though!

I had this issue the other night. It seems an invisible overlay gets stuck sometimes. Not sure what app or why, but clearing all the recent apps fixed it for me. Try that if it happens again instead of waiting for the phone to restart.
Sent from my G3223

Also had this problem two days ago and restarting seemed to fix it. I was disabling some of the stock apps at the time so I wondered if that had something to do with it but I don't know, don't think I re-enabled any of the apps or anything before or after the reboot and so far it's been working since.

mikeandjaimie said:
I haven't had this issue exactly, but when I install a new app and it asks for permission to access my location/storage/etc.. I can't press Allow.. I can press Deny though no problem at all. Right now I'm manually going into apps/permissions and granting all my apps whatever I think it needs.. Just a pain to do it that way though!
Click to expand...
Click to collapse
Thanks for your feedback and I have also had that problem too. Of course yes we can go into app settings and enable and like you stated it's a pain haha. I know this isn't the place to point these problems out and get them fixed but it's nice to know I'm not the only one ??
redincali said:
I had this issue the other night. It seems an invisible overlay gets stuck sometimes. Not sure what app or why, but clearing all the recent apps fixed it for me. Try that if it happens again instead of waiting for the phone to restart.
Click to expand...
Click to collapse
Yes dude, that's correct and thanks for that valuable information I do clean my cache regularly and can't say I've come across the problem for a while, so thanks again.
exonym said:
Also had this problem two days ago and restarting seemed to fix it. I was disabling some of the stock apps at the time so I wondered if that had something to do with it but I don't know, don't think I re-enabled any of the apps or anything before or after the reboot and so far it's been working since.
Click to expand...
Click to collapse
I'd like to mention I have disabled and uninstalled quite a lot too, but I can't say if this adds to the problem. It'd just be really nice to hopefully get the new build of software that was recently announced on Xperia Blog but I can't say if this will fix the problems etc. I don't know? ??
Sent from my Sony Xperia XA1 Ultra using XDA Labs

LevsOG said:
Good evening, just lately I have encountered a bug when trying to install APK's. When I go to install via Package Installer it will open up the screen and when I go to press next it doesn't do anything, I have tried rotating the screen and pressing Next and it just doesn't work whatsoever...
I powered off my device and powered back on and this seemed like it fixed the problem.
Is/has anyone else encountered this? I've also noticed ometimes when typing on the keyboard the sound goes tinny for 5 seconds or so and go back to normal, it's been like this since unboxing too.
Click to expand...
Click to collapse
I've experienced this issue as well and the culprit seemed to be an overlay permission from another app. As I'm sure everyone knows, this phone's screen is very bright even at it's lowest setting. I like to read at night and the light bothers my wife so I started using an app called Nightowl that further dims the screen. Nightowl produces a overlay that dims the entire screen. If i happen to be running nightowl and try to install the app, I can't tap install. Once I turn off the app I'm able to install like normal. Hope that helps lead you in the right direction as restarting the phone every time a problem presents itself is kind of a bummer.