Database Info

[Q] Car Kit popping out everytime I install a new rom

So something weird happened with my Inspire where it somehow got unlocked in my pocket and opened a few programs. One of them was car kit, and even though I kept exiting the program it still pops up. I tried unticking the box where it says open automatically but it still didnt work. I resorted to clearing my cache and wiping data and flashing a new ROM, but the weird thing is the first thing I see when the phone first boots up is the car kit mode. Also another thing that changed with my phone is the way the backlight behaves. It just turns on all of a sudden randomly even if it is unlocked. Also what I like about the Inspire is its feature of dimming the backlight when it is near your ear during a phone call and returns to its normal brightness when its not. This feature is also gone. Has anybody experienced this sort of problem? Is there a way around it? Like bringing ALL the system files to ABSOLUTE default then flashing again?

I would definitely run the RUU to stock, then rerun the hack kit and see what happens.

So I got the car kit to stop opening all the time, but the problem of the backlight still persists. But another problem is the phone backlight turns on when the phone is moved just a LITTLE bit. Its definitely annoying me, since it is a major battery drainer.
PS. I just found out that it only happens when it is plugged in.

I just discovered something strange about my Inspire: I have an adapter to step the size down from mini-USB to micro-USB. When I use one particular charger, the phone switches to the Car Panel as soon as I plug it in. I've got no idea. Phone is completely stock, not rooted. I originally sideloaded a Swype keyboard but deleted it and installed the Slide-It after I realized the Swype would quit working every time the publisher issued a new beta.

Screen won't stay off from proximity sensor or using the power button

I have searched and all that came up are a bunch of issues with the screen not coming back on. This is not my issue, I wish mine would stay off. I have tried every method I know and my cheek keeps switching calls, hanging up, and dialing other numbers while I am trying to make a call. I've tried the power button method of hitting the power button and continuing the call, but even that hasn't fixed the issue. For the life of me, does anyone know of a "fix" for this? I'm about ready to break this thing in half. Thanks for any and all help.
One more thing, does anyone here use the google VVM? I had it working at one point on my D2, but ever since I switched to the TB I have had trouble getting it to work. I have tried the *71 or whatever method, but I still can't get it to forward. I can log in and see my old messages fine, but for some reason I can't get this one to forward the calls to GV for a message.

Ok, are you rooted, and of so, what ROM are you using.
I've seen some posts where people have problems with their proximity sensor, and they said blowing compressed air in the speaker (back of phone under kickstand) has helped.
Has far as Google voice goes, I've never had a problem setting it up. Again, what Rom are you running (though I don't think I've tried a Rom that didn't like Google voice.)
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1

Bamf 1.8.6 remix. I'll try that. I just don't understand why it still comes back on after hitting the power button while on a call. I had it set up on my phone before changing roms, and I had it working on the D2. And I'm kinda being misleading by saying that it's not "working". I can connect to GV via the app, but I can't get the settings in the VM menu to "stick" as the GV. It keeps giving me the prompt that it is not supported by the "carrier". So I tried the long method of forwarding my missed calls to GV via *71 and two other * numbers seceded by my GV number. But for some reason the calls still won't forward if sent to VM. The only reason I have it is so that I can delete my messages without having to ever actually listen to them, I hate VM altogether, but verizon keeps giving me those popups when I have a message and they won't go away till they are either listened to, or deleted. And I'm not paying 3 or whatever dollars a month just so I can use something that is free though other methods. Thanks for your help.

My proximity sensor has never been the slightest bit reliable on any rom including stock

The proximity sensor on the Thunderbolt is located on the top front face of the device, inside the "V" of the Verizon logo. It can seen under bright light. It seems to be quite sensitive to dust, which causes the screen to turn on/off unexpectedly.
Carefully blow a bit of compressed air into the earpiece grill, and into the small gap between the glass and plastic housing shown in the circle, and it should clear it up.

I've had problems with my proximity lately as well.. Been hanging up on people (it's very embarassing) during important calls. It's making me almost switch phones. This happens on ANY rom these days so it tells me it's a hardware problem at this point. Also, usually after I get a phone call and hang up afterwards, the entire phone is unresponsive until I hit the power button on top and hit it again to wake up, then everything is functional again. So annoying.

Diversion said:
I've had problems with my proximity lately as well.. Been hanging up on people (it's very embarassing) during important calls. It's making me almost switch phones. This happens on ANY rom these days so it tells me it's a hardware problem at this point. Also, usually after I get a phone call and hang up afterwards, the entire phone is unresponsive until I hit the power button on top and hit it again to wake up, then everything is functional again. So annoying.
Click to expand...
Click to collapse
I've always felt like it was a hardware problem.

[Q] CM7 Home button opens clock app, calls go direct to speakerphone

It's apparently a semi common problem.
My Wildfire running CM7 will always open up the clock app when I press the home button. Freezing the clock stops this happening.
Similarly, when I answer or make a call, the speakerphone is automatically activated. From what I can tell, the phone thinks it's docked, and indeed, if I set the phone to make a sound when it's docked, you do hear the notification.
If I plug in the power cable and wiggle it around, I can get it to activate/ deactivate this, but I dont have this problem at all if I go back to the Sense backup I have. (Should note, I've cleaned out the power socket with all manner of stuff, to no avail (thought it might be lint etc))
Basically, is there any way I can stop the phone from thinking it's docked/ just remove the dock facility entirely?
I found a thread somewhere that said something about changing the name of a dock related apk somewhere, but I can't for the life of me find it again.
Thanks!

I would start with a fresh install if you haven't tried that already.
Hit that thank button if I helped!

Yup, should've mentioned I've done that numerous times with different versions of stable CM7. Did a full wipe and cleared the dalvik cache each time too.
The problem doesnt happen until the phone has fully loaded i.e. the home button works normally for the first 10 seconds or so of the phone being on. Then I hear the notification to say the phone has been docked, and the problems begin.

Have you thought of uninstalling the docking software, and then rebooting?
Hit that thank button if I helped!

Well that's what I'm asking - how exactly do I do that?

I would download this,
http://www.apkapplications.com/2011/07/root-uninstaller-pro-apk-v121-download.html
Then look for the docking .apk
Hit that thank button if I helped!

Well I used that to freeze the clock before and that worked to stop the home button going to the clock, but the speakerphone issue remained.
There was no docking apk as far as I could tell.

Okay, I've "solved" this, and I feel compelled to share how I did it, since EVERY thread on this on every forum is unresolved.
My problem was something in the USB jack - I thought I had cleaned it properly, but after some WD40 and jamming a paperclip in there, I no longer get the problem...at least for now.
I still find it bizarre that I never had this problem with the stock sense ROM (and didnt have it when I reverted back to my backup of it), but what can you do!?

flamph said:
Okay, I've "solved" this, and I feel compelled to share how I did it, since EVERY thread on this on every forum is unresolved.
My problem was something in the USB jack - I thought I had cleaned it properly, but after some WD40 and jamming a paperclip in there, I no longer get the problem...at least for now.
I still find it bizarre that I never had this problem with the stock sense ROM (and didnt have it when I reverted back to my backup of it), but what can you do!?
Click to expand...
Click to collapse
Glad you got it fixed!
Sent from my DROID3 using XDA App

same problem here, tried everything, reflashing, data wipe, cache wipe.
and same as OP sense based roms do not show this symptoms.
I have this problem with CM7 and almost on every rom based on it.
I searched in many places, but there aren't any positive solutions.
please help.
P.S.- cleaning the USB port also didn't work for me..

I found a way to disable dock mode. there is an app called NoDock which disables the dock mode at OS level.
It requires root permission to disable the dock. so your phone must be rooted.
unlike apps like DockNothing this actually does the job.
no more auto speakerphone modes, no more home button taking to clock app.
m.appszoom.com/android_applications/tools/nodock-free-trialneed-root_ogod.html

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] 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