Database Info

Display / menus freezing and / or disappearing, system apps force closing

I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.

That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.

Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.

Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.

Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..

If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.

I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!

Np. Keep us updated.
Sent from a dream.

I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!

awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues

I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.

I've a smartphone which tends to shutdown randomly on its free will. Help, please.

Hi there,
I'm having a problem with my smartphone and i felt like this is the #1 place to ask for guidance on android issues over the interwebz.
I have a low-budget Samsung Galaxy Y GT-S5360.
It's running what it came with, Android 2.3.6 / Gingerbread.XXLK3.
30 minutes after having it, i foolishly decided i need more internal memory and rooted the device, in order to remove the useless apps on it.
It was a total slaughter. I think i even pwnd Samsung Apps app.
Anyway, device worked well for months after the bloody carnage, but recently backfired right into my face with random shutdowns.
I have no proper idea on the reasoning of these shutdowns but i've collected some data on the subject, here they are;
- It randomly shuts down almost every day. Just 3-5 times a day if it's on a good mood. Over 10-12 if it feels down.
- Device never shuts down while being charged or connected through USB.
- Device usually shuts down after i used power button to lock the screen.
- It's not being locked on black screen, it definitelly shuts down, not properly tho. (no small time vibrating)
- I feel like front sensors (which turns off the screen during calls) might be causing this, because lately it's shutting down whilst calls on my face. I even managed to shut it down by wiping the mentioned sensors with my thumb.
- Sometimes it can be shut down by brute force. I mean putting it down to table a little bit harder than average.
- My SDCard is problematic, it gets unmounted and says its damaged but i tend to ignore it and just reply with "sssh everything is gonna be alright" (format and reuse)
- I have only a handful of apps which contains bank & password apps etc. Nothing serious going on with my services.
PLEASE HELP ME OUT IF YOU RECOGNIZE THE SEMPTOMS.
What should i do? A custom rom? New battery?
Thanks in advance.

Bonus information;
I've never seen it shutdown with my own eyes.
It usually happens when its' screen is blacked out, when i put it in my pocket or table.
Or when i try to make a call and put it against my head.
So whatever is happening, it happens while the screen is blacked out.
It neves turned off while listening to music either.

straud said:
Bonus information;
I've never seen it shutdown with my own eyes.
It usually happens when its' screen is blacked out, when i put it in my pocket or table.
Or when i try to make a call and put it against my head.
So whatever is happening, it happens while the screen is blacked out.
It neves turned off while listening to music either.
Click to expand...
Click to collapse
might be you should go to recovery mode and do a data factory rest and also might need to clear the cache partition.
try it..

prafull07 said:
might be you should go to recovery mode and do a data factory rest and also might need to clear the cache partition.
try it..
Click to expand...
Click to collapse
Ah yes, i did that. Sorry that i forgot to mentioned it.
I've factory reseted it and while i was there i got curious and did the cache-clearing too.
But the problem persists.

straud said:
Ah yes, i did that. Sorry that i forgot to mentioned it.
I've factory reseted it and while i was there i got curious and did the cache-clearing too.
But the problem persists.
Click to expand...
Click to collapse
I think you should try flashing your stock rom with the help of Odin.

[Q] Bluetooth will not turn on...

Just got a replacement N5 from Google for a warranty issue and after full re-root and setup I went to get in the car today and use bluetooth and I noticed a problem. Bluetooth will not turn on. Tapping the slider moves the position to on but it remains greyed out and, in fact, off. I tried a restore of the bluetooth share and pairings from Titanium backup and that just hung and never completed. I can always factory reset it but I hate to go back through that ... anyone got a way to 're-install' bluetooth and save a reset and reconfiguring for me?

SWBgHz said:
Just got a replacement N5 from Google for a warranty issue and after full re-root and setup I went to get in the car today and use bluetooth and I noticed a problem. Bluetooth will not turn on. Tapping the slider moves the position to on but it remains greyed out and, in fact, off. I tried a restore of the bluetooth share and pairings from Titanium backup and that just hung and never completed. I can always factory reset it but I hate to go back through that ... anyone got a way to 're-install' bluetooth and save a reset and reconfiguring for me?
Click to expand...
Click to collapse
This apparently has been problem for Nexus 4 and Nexus 5. One poster from android central posted this for his Nexus 4:
I called Google technical support and they found a solution for me.
-In your Nexus 4, go to parameters/Applications/All/Bluetooth
-Here: erase cache, data and updates.
-Resart your phone.
In Nexus 5 Settings>Apps>All>Bluetooth Share. There you might try Clear data and Clear cache.
Got nothing to lose. Hope it works. I cannot test it myself since my Bluetooth is working.

Thanks for the suggestion. I had looked around and saw a couple mentions loosely similar related to the N4 but wasn't sure if same applied to N5. Looking though ... I do not have a bluetooth share app installed. That must be the issue, anyone got a way to re-install that Bluetooth Share, seems my backups from Titanium won't restore it.

Found thread where someone had your issue and solved it with reset.
http://forum.xda-developers.com/google-nexus-5/help/activate-bluetooth-t2595761
Maybe you could do backup to PC and get this restored with reset.
I know it is a PITA.

I figured a reset would square it away, was just hoping to find a way to avoid that if I could. I suppose next w/e I will reset if I don't find another way to get BY back.
Sent from my Nexus 5 using xda app-developers app

SWBgHz said:
Thanks for the suggestion. I had looked around and saw a couple mentions loosely similar related to the N4 but wasn't sure if same applied to N5. Looking though ... I do not have a bluetooth share app installed. That must be the issue, anyone got a way to re-install that Bluetooth Share, seems my backups from Titanium won't restore it.
Click to expand...
Click to collapse
It is working in Nexus 5 same as N4, Go ahead same way it will work
https://play.google.com/store/apps/details?id=com...bluetoothfixrepair‎

I tried, but there is no Bluetooth Share app installed that I can see in the program manager.
Sent from my Nexus 5 using xda app-developers app

joannn said:
https://play.google.com/store/apps/details?id=com...bluetoothfixrepair‎
Click to expand...
Click to collapse
When I run this app, it says no BT folder found. Seems the issue is that somehow this BT Share app just isn't there.

Another fix...
I know you already solved your problem, but I thought for people like me, who have found this thread later on, I'd just sign up to XDA and post my fix.
I didn't want to do a hard reset, so I played around with the "Bluetooth-Share"-thing in the Android app manager.
I cleared the cache and the data, that didn't do anything, even after a reboot I couldn't get the Bluetooth toggle from beging greyed out.
After that, I found that button at the very top right, that is labeled as " Uninstall Updates" or something like that. I tapped it and tapped OK at the following prompt. Where the "Uninstall Updates" button was before, should now be a greyed out "Disable" button. Then you need to reboot.
Try to enable Bluetooth. The toggle should turn blue after a few seconds as usual. Bluetooth should work normally now.
I hope my post helped anybody, :cyclops:
-hiwye

I am not having any luck. My bluetooh stopped working after doing a hard reset. Please note I've never rooted or flashed a ROM, or unlocked boot loader or anything. My N4 and N5 have always been completely stock.
I've tried everything in this thread, except I am not sure what hiwye is talking about as I cannot find an uninstall updates. I went ahead and tried another factory restore/wipe and still have same issue. I hit toggle to turn Bluetooth on, it then immediately toggles back to off.
Just as a side note, my bluetooh was working fine until the factory wipe/reset. I did the reset in an attempt to fix a sim card slot issue, that is also still not resolved. Upon restarting my phone, I get "no sim card" message. I got a new sim card and also confirmed the sim card works fine in other phones..... i can turn off, pop it out and back in and boot it again. sometimes it will see the sim card again. It may take 20 times, but finally work..... I should probably start a new thread on the sim card thing, but wondering if my motherboard needs replaced.....
hiwye said:
I know you already solved your problem, but I thought for people like me, who have found this thread later on, I'd just sign up to XDA and post my fix.
I didn't want to do a hard reset, so I played around with the "Bluetooth-Share"-thing in the Android app manager.
I cleared the cache and the data, that didn't do anything, even after a reboot I couldn't get the Bluetooth toggle from beging greyed out.
After that, I found that button at the very top right, that is labeled as " Uninstall Updates" or something like that. I tapped it and tapped OK at the following prompt. Where the "Uninstall Updates" button was before, should now be a greyed out "Disable" button. Then you need to reboot.
Try to enable Bluetooth. The toggle should turn blue after a few seconds as usual. Bluetooth should work normally now.
I hope my post helped anybody, :cyclops:
-hiwye
Click to expand...
Click to collapse

Prodeje79 said:
I am not having any luck. My bluetooh stopped working after doing a hard reset. Please note I've never rooted or flashed a ROM, or unlocked boot loader or anything. My N4 and N5 have always been completely stock.
I've tried everything in this thread, except I am not sure what hiwye is talking about as I cannot find an uninstall updates. I went ahead and tried another factory restore/wipe and still have same issue. I hit toggle to turn Bluetooth on, it then immediately toggles back to off.
Just as a side note, my bluetooh was working fine until the factory wipe/reset. I did the reset in an attempt to fix a sim card slot issue, that is also still not resolved. Upon restarting my phone, I get "no sim card" message. I got a new sim card and also confirmed the sim card works fine in other phones..... i can turn off, pop it out and back in and boot it again. sometimes it will see the sim card again. It may take 20 times, but finally work..... I should probably start a new thread on the sim card thing, but wondering if my motherboard needs replaced.....
Click to expand...
Click to collapse
I get the same Sim card missing screen I have tried a new sprint Sim and same issue. They way I have been fixing it is to pop off back cover and where the vibration motor sits (stays attached to cover) I put my finger in the hole and squeeze the 2 parts together and hold tight till it finishes booting and it will see the card. I'm not sure what's exactly the problem is but it works as temp fix and will stay until the next reboot.
Sent from my Nexus 5 using XDA Free mobile app

31ken31 said:
I get the same Sim card missing screen I have tried a new sprint Sim and same issue. They way I have been fixing it is to pop off back cover and where the vibration motor sits (stays attached to cover) I put my finger in the hole and squeeze the 2 parts together and hold tight till it finishes booting and it will see the card. I'm not sure what's exactly the problem is but it works as temp fix and will stay until the next reboot.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
can you take a pic of where you apply pressure?
Any other issues? My bluetooth still doesnt work.

Prodeje79 said:
can you take a pic of where you apply pressure?
Any other issues? My bluetooth still doesnt work.
Click to expand...
Click to collapse
Only device so doing it and taking PUC not gonna happen let me look up some images and I'll post them its not that difficult if you have had the back cover off before its very obvious where motor is. The motor is literally just under the flash led. Pop off cover starting at the top and slowly down each side with a guitar pick there is a tiny bit of adhesive at the bottom of rear cover about where the soft keys are when phone is on. Peel that up slow and you will see the vibration motor stuck to rear cover. See the space it came out of and put finger in that hole. And other finger opposite the first one on the glass and squeeze.... Not crazy so you break screen. Don't take much pressure. Start light and boot it. Says no Sim, try again with a little more pressure. When it first happened I googled sh*t for 2 days and couldn't find a fix. And this worked when I tried and a few reboots after. I shut phone off or battery dies I gotta do it to get Sim recognized.
Sent from my Nexus 5 using XDA Free mobile app

Docarut said:
In Nexus 5 Settings>Apps>All>Bluetooth Share. There you might try Clear data and Clear cache.
Click to expand...
Click to collapse
Worked for me, thanks.

[Q] Nexus 5 stopped being able to vibrate

So I recently bought a Nexus 5. A short time after, I noticed that when I would type on the keyboard, it would sometimes stop vibrating. When this would happen, nothing would make it vibrate. The back and home buttons wouldn't vibrate (yes, they should according to the settings), and my phone wouldn't vibrate when receiving texts or other notifications (again, they should be). It seems the fix was to just turn the screen off and back on. Now however, it seems vibration constantly doesn't work. Nothing that should be vibrating according to the phones settings would vibrate. Occasionally, vibration would randomly start working again, but once I turned the screen off and back on, vibration would stop working again. This was on Android 4.4.4. When the factory images for 5.0 were released yesterday, I installed it on my phone using the android sdk, instead of waiting for the OTA. I figured since this caused a factory reset, that it would fix the vibration issue. Nope, still there. Is there anyway that I can fix this, or is this just a hardware issue and I'm stuck dealing with whether it wants to work or not? Oh, when it does vibrate, it doesn't vibrate weakly. It vibrates as it should.

thexlizardxking said:
So I recently bought a Nexus 5. A short time after, I noticed that when I would type on the keyboard, it would sometimes stop vibrating. When this would happen, nothing would make it vibrate. The back and home buttons wouldn't vibrate (yes, they should according to the settings), and my phone wouldn't vibrate when receiving texts or other notifications (again, they should be). It seems the fix was to just turn the screen off and back on. Now however, it seems vibration constantly doesn't work. Nothing that should be vibrating according to the phones settings would vibrate. Occasionally, vibration would randomly start working again, but once I turned the screen off and back on, vibration would stop working again. This was on Android 4.4.4. When the factory images for 5.0 were released yesterday, I installed it on my phone using the android sdk, instead of waiting for the OTA. I figured since this caused a factory reset, that it would fix the vibration issue. Nope, still there. Is there anyway that I can fix this, or is this just a hardware issue and I'm stuck dealing with whether it wants to work or not? Oh, when it does vibrate, it doesn't vibrate weakly. It vibrates as it should.
Click to expand...
Click to collapse
Hardware. The vibration module is located on the backcover and is attached by a small sticky pad which can become dislodged or loose for various reasons. Some who have the issue have reported success giving the phone a smack, others choose to open it up (careful, lots to damage) while others take the RMA route wanting to keep their warranty intact.

bblzd said:
Hardware. The vibration module is located on the backcover and is attached by a small sticky pad which can become dislodged or loose for various reasons. Some who have the issue have reported success giving the phone a smack, others choose to open it up (careful, lots to damage) while others take the RMA route wanting to keep their warranty intact.
Click to expand...
Click to collapse
Well, I'm going to avoid opening the phone up. Tried smacking it, but that has yet to work. Would Google replace the phone because of this, or am I just stuck with how it is?

thexlizardxking said:
Well, I'm going to avoid opening the phone up. Tried smacking it, but that has yet to work. Would Google replace the phone because of this, or am I just stuck with how it is?
Click to expand...
Click to collapse
Of course. If the vibration module isn't working as intended then they will accept your RMA request and send you a refurbished replacement device.

bblzd said:
Of course. If the vibration module isn't working as intended then they will accept your RMA request and send you a refurbished replacement device.
Click to expand...
Click to collapse
That's good. I hit it a couple more times, and it's working right now. I'll see how it progresses.
Thanks

[Q] Weird beeping sounds

Hey guys. So I have had a Nexus 5 ever since they were released. I'm currently on my second one and but I had the problem in my first one too so here it goes....
I seem to be getting random beeping sounds coming from the speaker. I turned off NFC/Bluetooth/wifi/data and even rebooted in Safe mode to see if it was an app i had installed but the annoying beeps persist even in safe mode (and as I type this).
Any ideas where its coming from?

Just to exclude anything software-related: If you modified the system on your phone (flashing, rooting, ...) go back to stock first by flashing the latest factory image.
Test if the issue is still present. If so, I'd RMA the device.
Does it even happen while the screen is off or just under certain circumstances?
- experience7

Doesn't matter if the screen is off or on. I haven't modified the device. It is weird that this is also happening on my second Nexus 5 that's why I'm inclined that it is something I'm doing.

Okay. Then just try to flash the factory image and don't install any app. Just leave the system as it is. Try again. If the issue is still present call Google support. I had to RMA mine, too. Didn't take longer than 2 days for my new device to arrive
Much luck!