Database Info

[Q] Inspire thinks it's in a car dock with non-Inspire based kernels

Now, from what I can gather, this problem stems from a faulty or dirty Micro-USB port. I tried compressed air, but it did nothing for me.
I decided to do a complete unroot, S-ON, factory restore and call HTC to see if I could get it fixed. To my surprise, the problem vanished. Thinking I had lucked out and that fixed it, I re-rooted the phone and the problem still didn't reappear.
Then, thinking I would start small, I flashed a Sense kernel. As soon as I rebooted it went straight to Car Home and began answering in speakerphone. For laughs I went ahead and flashed MIUI then CM7, both of which exhibited the same behavior.
After all of this, I got to wondering just why the stock ROM and kernel worked but nothing third party would. Then it hit me that all the 3rd party stuff I had been using were DHD ports, and not based off the Inspire. I downloaded and flashed ClearDroid, which has an Inspire base, and the problem is once again dormant.
The only sense I can make from it is that HTC has implemented some kind of fix for shoddy USB ports in the Inspire kernel.
So now here's the question: Does anybody know anything about this, and would it be possible to implement said fix in, say, and AOSP kernel?

When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.

Also Im pretty sure when your rooted this setting will take effect as to where a nonrooted phone doesn't allow the permission to execute the command.

Gizmoe said:
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Click to expand...
Click to collapse
I'll try that, but I can completely wipe my phone (cache, system, data, d-cache), flash CM 7.1.0, and without even logging into my Google account it happens.

After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.

Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?

Agoattamer said:
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Click to expand...
Click to collapse
Both.
With the stock ROM and kernel, everything is fine. With the stock ROM and a DHD-based kernel it happens. With any AOSP ROM it happens.
Removing the Car Dock app keeps it from launching, but the phone still defaults to speakerphone for all calls (incoming and outgoing).

Gizmoe said:
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Click to expand...
Click to collapse
The problem about warrantying it is when it's in a stock state, it works fine.
I've never dealt with HTC, but I can't exactly see it going over well if I call up and say "My phone acts funky when I run CyanogenMod".
The airplane mode fix is something I haven't heard before. I guess I'll give it a go.

Most unusual..

My Thunderbolt is locked somehow, and I have no way to restore it to factory defaults. What I mean by "locked" is as follows:
I remove two apps from the device, change the wallpaper and delete a contact. Then, I restart the device - when it boots back all of the changes I made are gone. It's like in read-only mode, the changes look like they take affect but after a reboot everything is restored to it's current FC'ing on everything state.
I've tried factory resetting the device but instead of booting to recovery it just boots to the picture of a phone with the red caution symbol showing, it does not do anything else.
I've tried flashing over a stock RUU image but the flash either 1) looks like it works then boots back to the state it was before, 2) hangs on part of a flash and reboots to the normal state.
The device is not rooted, I've tried revolutionary and get the following error:
"rawadb_handle_msg" and then it loses connection.
Any ideas would be appreciated, I've never seen anything like this.

Turn it on and let it boot up if it can then pull the battery while its on and leave power off for 5 minutes then try again.
Also can try, with power off, hold power button and volume down button together for a few seconds and when it gets to the white screen wait for about 10 seconds then select reboot from there

Latest OTA patched the Revolutionary exploit (so it won't work). You may want to root using ADB and flash the rooted RUU. Can't say I've ever seen R/O behavior; but then again, I've been rooted for months - currently on AOSP (ShiftAo5p 2.8) and waiting for an ICS with data
I know, not too helpful, but there are still ways to root.
Any feedback from VZW or a "real" corporate store? They're actually quite helpful here with tech junkies.
OK, one more suggestion - early on, I couldn't do anything either (Market, etc) and the fix was to pave (format) my SD card. I know it sounds weird, but I was going to exchange my phone (ordered, then sent back replacement). I figured, what the heck. Took the uSD card out, put it into my PC's USB port and formatted it FAT32, popped it back in and VOILA - happy happy joy joy.
Granted I copied all the data off of it before paving - then copied back selectively (highly recommend AirDroid, by the way, no more cables). Might give this a shot.

Hey guys, thanks for the suggestions - unfortunately no luck on my end with that

nautical34 said:
Hey guys, thanks for the suggestions - unfortunately no luck on my end with that
Click to expand...
Click to collapse
I inserted the card freshly formatted (I wasn't rooted at that point) - nothing on it, and I booted up, I was able to install Market apps (which I couldn't do before) - Note - AFTER I also did (multiple) a factory reset, I was good.
That didn't work for you? Maybe try again? Or just No-Go?
Also helps prove every 'Bolt has its own personality
Good luck on your CLNR ...
I have no idea what errant app or corrupted data may have been on the card, but totally paving and starting over "fixed it". Soon after, I rooted Then I had choices Granted I've had times I've had to do a factory reset (but not pave the SD) and set up all again - I've found the larger games (haven't determined which yet) cause my phone to get into reboot fits if I do actually reboot (which I need to do sometimes to get the radios to get data again); so, boring maybe, but very few games installed. That's OK, I prefer to learn or listening to music during idle time. Good luck.

HELP! SGS4G Multiple issues: no sound in calls, music, and screen remains on in call!

I have been experiencing some issues with my phone recently. I have flashed multiple roms and everything was working fine for the past 3 months or so. Last week I flashed Hebrew Valhalla, it worked fine for a few days then all hell broke lose! I started experiencing the following issues with the phone:
1. In calls, people can hear me but I cannot hear them through the front speaker. I have to either put it on speakerphone or use my headphones.
2. Whenever I cannot hear people in calls (issue #1 above) then there is also no sound coming from the back speaker when I play music. It only works with headphones.
3. Sometimes when I play music, sound only comes from the phone's speaker. Yes the tables literally turn! Even if I plug in headphones, it keeps playing through the phone's speaker. I use stock music player no mods nothing and yes my headphones and their jacks are good I tried multiple ones.
4. The screen does not turn off while in calls. I used 2 apps to test the proximity sensor and it is working fine. Sometimes when on a call the screen randomly turns on and off but most of the time it remains on.
5. Although the vibration intensity is set to max, when typing, the intensity is random. Sometimes it is strong, other times it is weak. Completely random and it is only for typing. It works fine for notifications and pressing back button or whatever. The keyboard is swype and it used to work fine before.
SOMETIMES when I reboot the phone, Issues #1,2 and 3 fixes themselves; I can hear people in calls, music works fine both in speaker and headphones when necessary, but issue #4 is persistent.
The phone has not taken any falls/hits or anything, so I doubt it can he hardware related? So I assumed it is software related, I went to flash other roms, including the ones I used previously that was working fine and still nothing!!! I even flashed Heimdall one click and started from scratch, and still the same problems in the stock rom.
I have spent days searching all over to no avail. Please if anyone knows the solution or workaround to any of the issues above it will be greatly appreciated!!!!!

How old is the phone? If I were you and it's still under warranty I would consider a handset exchange through your phone provider, and if you choose that method make sure you go back to stock an unroot first before you send
Sent from my SGH-T959V using XDA

Cannot do
The warranty has long expired, so that's not an option.

Look for the Gremlin Remover in the Dev section.

Trying
I have been trying for the past 5 hours to get the GR to connect to the phone but it just is not working. I have tried installing and uninstalling all drivers rebooting phone, pc, remove battery everything and it just does not work!!!
The only time GR connects to the phone is when it is starting up, or when the os has loaded up fully. whenever I reboot to download mode it disconnects and never connects back to odin when in download mode. What am i doing wrong? I used the drivers in the GR file but it does not work.
Can anyone link to the drivers that will make odin see the phone while in download mode?

Look at the guide in the second link of my signature. Read the notes about drivers, odin and heimdall. You need to completely, thoroughly and patiently make sure you remove them all.
Go to the wiki for the samsung drivers or use kies mini to install the drivers. ODIN is a samsung software and they use the same drivers.

Still not working
So I found the right drivers and just finished flashing GR twice and the problems are still there. after flashing GR the second time I just flashed Hebrew Valhalla and the problems are still there
I really dont think there is anything else I can do?

Did you do ALL of the steps that Thomas posted? Not just the flashing GR.

Yes I did all the steps: 1, 2 then 3, not the "Filesystem Cleaner" part.

You have nothing to lose doing all the steps.

Ok I will do the Filesystem Cleaner part now and update in a while
EDIT:
I installed the android SDK to connect to adb. Thomas's instructions says to go to recovery mode, but the pc only see's the phone as adb when the phone is booted up in normal mode, not when it is in recovery mode.
I used the universal driver installer, is there specific adb drivers for recovery mode?

So before I got the adb to work I kept rebooting the phone and pushed and removed the headphones in the headphone jack multiple times and I was suprised everything started working. I could how hear people in calls, the screen turned off fine during a call, music worked fine. Rebooted again and everything still worked fine! My memory card was formatted so I copied back some of the files that were on it (music, pictures and apk installers for certain apps, and titanium backup folder). I went to install my apps from the apk's not titanium backup, so I did not restore any data just fresh install the apk's....
.....Rebooted the phone and all the problems came back!!!! I tried uninstalling the apps and reboot multiple times but the problems remained, so I said I will try the entire process again.
Ok so I found the drivers and completed ALL the steps now including the adb stuff and the filesystem cleaner. The status was already clean but I still ran the cleaner just to be safe. Then I flashed Gremlin Remover again and the problems still exist. I flashed Octane 3, problems still exist. flashed Hebrew Valhalla and the problems were still there...rebooted multiple times and the incall volume is working FOR NOW, but the screen does not turn off anymore.
I pushed the headphones in and out many times as it worked the first time but it made no difference now. I really do not know what more is there to do

How are calls just using your phone? No headphones. If things were fine before restoring your sd card shouldn't that tell you there is a good chance something on your sd card is messing with your phone?
You should start over again. Be thorough. Do all the Gremlin Remover steps. Leave your sd card fresh after format. Install apps one at a time with time between from the playstore. Don't mess with your headphones yet. And see what state your phone is in.
It could be your phone. An app. Your sd card or some data on it. Or your headphones. Process of elimination.

Do you have accidental damage insurance? Hammer anyone?lol
Seriously though, with using the gremlin remover and system cleaner processes, everything bad should have been removed. However, you stated that the problems reoccoured after restoring your sdcard. My guess would be either a virus (yes it is possible to get a virus or malicious file on our phones) or a corrupt file/files that is contained in your files that you restored to your sdcard. As much of a pain in the ass it may be, you should restore each file one by one and test. Once the issue reoccours, then you know what is the cause. there are some directories/files you should not restore:
Code:
.android_secure
.cache
Android
CachedImages
data
gps
LOST.DIR
temp
tmp
Voodoo
and any folders that pertain directly to any apps you use like 360launcher, goweather, etc.
As lumin said, everything worked fine until you restored your sdcard...

lumin30 said:
How are calls just using your phone? No headphones. If things were fine before restoring your sd card shouldn't that tell you there is a good chance something on your sd card is messing with your phone?
You should start over again. Be thorough. Do all the Gremlin Remover steps. Leave your sd card fresh after format. Install apps one at a time with time between from the playstore. Don't mess with your headphones yet. And see what state your phone is in.
It could be your phone. An app. Your sd card or some data on it. Or your headphones. Process of elimination.
Click to expand...
Click to collapse
Sadly, this is where I am right now. I did start all over again, formatted the card and only put Hebrew, Octane and Anton's kernel. This is all that is on the card, when I installed them some of the default folders were created. I am yet to put anything else on the memory card, and at the time of this typing I only have basic market apps installed, nothing from transferring from pc to memory card or anything.
1. I have fully cleaned the system using all the steps in GR so I doubt the problem can be with the software on the phone.
2. I doubt it can be an app causing it because even after restoring the official rom just after GR it still does not work.
3. I am not sure if it can be the memory card, since I formatted it so many times, if it had a virus shouldn't it be gone by now? Not sure, just asking. I have some other memory cards handy I will format them and start back from square one again to see how it goes.
4. As for the headphones, I tried different headphones all the same thing. If anything then the problem about the incall sound might be with the headphone port itself. Maybe the phone's hardware or something in that port got stuck or something just something that is making the phone detect a headphone when there is actually none, maybe that's why...that's the most plausible thing I can think of relating to the incall and music volume. Now since I pushed it and out multiple times that maybe fixed it? Not sure..
As for the screen not going off I have no idea; so I will do everything again using a new memory card, not restoring anything, only install market apps one at a time and let you know how it goes.

I followed all the instructions down to the last letter. Did everything over. Removed battery left for some time. Formatted new memory card and only put the cleaner, one mp3 song for testing, Octane and Anton's kernel on it. Did the adb cleaning. Flashed Gremlin Remover. Left for 15 min. Flashed Octane and then Anton's kernel. Reboot and waited 15 min. Did not install anything whatsoever. First thing I did: make a call and play the mp3 file and suprise!! All the problems were still there. Nothing changed. Screen still remained on, no sound in call, no sound from music player; only through headphones like in square 1. Pissed off to the max.
I quit.

sherman619 said:
I followed all the instructions down to the last letter. Did everything over. Removed battery left for some time. Formatted new memory card and only put the cleaner, one mp3 song for testing, Octane and Anton's kernel on it. Did the adb cleaning. Flashed Gremlin Remover. Left for 15 min. Flashed Octane and then Anton's kernel. Reboot and waited 15 min. Did not install anything whatsoever. First thing I did: make a call and play the mp3 file and suprise!! All the problems were still there. Nothing changed. Screen still remained on, no sound in call, no sound from music player; only through headphones like in square 1. Pissed off to the max.
I quit.
Click to expand...
Click to collapse
Honestly, if you did all that, your device should be running it's best ever... You may have some sort of hardware malfunction. Even after trying different ROMs you still have the same issues correct?
I can tell you, I started experiencing some really bad things (not near as bad as yours) after I flashed a ROM WIP, and it took me several flashes to get my phone up and working again. But the only thing that was even remotely hardware related was the mis-calibration of the screen... I have to say, your problem is one of a kind...
However, have you tried pulling a logcat to see if by some chance there was something in there?

thomas.raines said:
Honestly, if you did all that, your device should be running it's best ever... You may have some sort of hardware malfunction. Even after trying different ROMs you still have the same issues correct?
I can tell you, I started experiencing some really bad things (not near as bad as yours) after I flashed a ROM WIP, and it took me several flashes to get my phone up and working again. But the only thing that was even remotely hardware related was the mis-calibration of the screen... I have to say, your problem is one of a kind...
However, have you tried pulling a logcat to see if by some chance there was something in there?
Click to expand...
Click to collapse
I don't know anything about logcat and how to interpret it. I see nearly 20k lines of text when I did it, what exactly should I look for?
I added it to my dropbox account if it is going to be helpful, here is the link:
This is the logcat I saved from my phone. Click it

I'm almost positive that it's some mechanical/electrical problem with the headphone jack. Something is stuck there, or it's dirty, so the controller erroneously detects like something is always plugged in. Hint: you said earlier that it suddenly started working when you were actively plugging-unplugging headphones.

AntonX said:
I'm almost positive that it's some mechanical/electrical problem with the headphone jack. Something is stuck there, or it's dirty, so the controller erroneously detects like something is always plugged in. Hint: you said earlier that it suddenly started working when you were actively plugging-unplugging headphones.
Click to expand...
Click to collapse
Yes I believe so too. I will try to open the phone to see what I can find concerning the headphone issue.
What about the screen not going off? Any suggestions?

Sound problems

Ok. Here's the skinny. About 3 weeks ago, my phone decided that it didn't want to charge anymore. Ok. I can deal with that. Then it decided about 3 days later that it didn't want to produce sound from the 3.5mm jack. Ok. I can deal with that too. Now, just recently, it decides that it doesn't want to produce sound from the rear speaker. Hmm. Actually. Ringtones and notification tones I can hear. But I can't hear the 'click' that you would normally hear when you make a selection. The feature is turned on in the settings menu. What really bothers me is that I can no longer hear music or any audio from games I play on the device. For a while, I was only able to hear audio from the rear speaker and that would be fine. But now its come to the point to where I can't hear anything but the notification tones and ringtones. I've tried wiping the phone and re-installing the OS. It fixs the problem for a few hours. Then it will revert back to the way it was. I also thought it might be a corrupted file inside the ROM itself on the SD card. So I replaced the ROM file on the card. Also fixed the problem for a little bit, but soon reverted back to old ways. I'm running Valhalla Final with no tweaks or new kernels, irreguardless of what my signature may say. My next step is to start over without using TB. Reinstall all the apps that I use one by one. When I reinstall the OS, I never reinstall the system apps, just so you know. I'm at a loss gang. If anyone has any kinds of suggestions, they would be greatly appreciated.

Flash back to stock with heimdall and flash Valhalla again.

One thing I forgot to mention about this problem. Since my phone no longer charges via the charge port, i'm unable to connect it for odin/heimdall. When I go into download mode, no matter how I hold the cable it won't recognize on the computer. However, i'm able to get it into mass storage mode if I hold it just right when i'm connected to the computer.

Just wanted to give everyone an update in case someone has the same issues. With great patients and a very steady hand, I was able to get my charging cable to stay connected to my phone for a brief time. Still, won't charge though. Oh well. Anyways. I ran Gremlin Remover on the phone and got back to stock. Fixed the sound problem. th3controller had mentioned to use Heimdall. Thx for the suggestion. Couldn't get my phone to connect long enough to run it. But the oneclick GR did the job. Also fixed the sound. So anyone who has this problem, flash back with GR to get all the crap out and load ur rom again. Mod can close this thread now.

Issues with calls and various other things.

Hello! Here I am with my Q.
I got it last week, rooted w/o BL unlock, then a few days later I went to Moto to unlock the boot loader. all went well. (AHAHA, They worded the terms for the unlock as if EVERYTHING at ONCE will break. It seems to me that this has become reality.)
Then I had issues with GPS and Camera not working at all.
With each flash I got one or the other working, not usually both.
Now Both Camera and GPS are working wonderfully. Here's the kicker, I've found that calls are not working well.
I make calls, they go through but end shortly after they start with silence. when you attempt to end the call, it wont do it, or it will about 5 minutes after end has been pressed.
On receiving calls, often times it wont come through at all, if it does there's a chance that you wont get to pick it up. It will act like the caller has hung up. Missed call. Some times it will let it through, and a few seconds in and go to silence.
Here was my process.
1. Rooted with Motochopper. Played around in stock for a while then got fed up with it and all of it's bloat. Not to mention horrible batterylife.(Still has horrible battery life on CM, even when underclocked.)
2. Unlocked bootloader via Motorola.
2a flashed OpenRecovery, CM10.1 (Yes the CDMA version)and gapps.
3. Yay CM. Sadly, nothing works right. (Yes there were wipes.)
4. Was suggested to flash JB FXZ, did that.
5. Flashed TWRP and CM+Gapps. (No camera, but GPS worked.)
5a. Flashed 5/20 Build. Camera worked but no GPS.
5b. Flashed 5/26 build over 5/20 and both Cam and GPS work now.
The call issues were persistent throughout all of the builds I tried.
5/20 5/23 5/26
Sys info screenshot
lionspaws.net/android/ignoreme/Screenshot_2013-05-29-21-48-50.png
Please help me diagnose this.
I'm not looking for "It's you/your device/doin' it wrong/works for me" or "go back to stock"
I'm looking for help. I need a working device.
Here's some logs with a test call.
it failed about 2 sec in. Skype hung up due to dead line. Phone wont hang up.
Radio reset, data resync.
then I powered off the device after it 'hung up'(radio reset)(If I dont hit hang up, the call timer will continue count up)
lionspaws.net/android/ignoreme/logs.zip (zip,bzip2)
Halp!

Bump?

I've been having the same call issues, with every rom except stock.

Sounds like you tinkered alot.
I suggest you do a full reflash with rsd/ stock rom. Since u have unlocked bootloader I suggest you to install custom recovery like twrp or cwm. That will also root your device. After that retry flashing cm10.1 nightly and gapps exactly as described in their threads.
Everything else would be tinkering around broken builds. So start with fully clean device through rsd.
Also about the gps problem: it is suggested to get a gps lock on stock rom before installing aftermarket rom.

I'm having the same problem, I've RSD'd to stock and all that stuff too. I ALWAYS clean install. Yet I'm having this problem on most roms. I haven't tried any kernels yet, so maybe that would help things but I dunno. I'm gonna play around with that some time and figure it out.

xLoveHateLegend said:
I'm having the same problem, I've RSD'd to stock and all that stuff too. I ALWAYS clean install. Yet I'm having this problem on most roms. I haven't tried any kernels yet, so maybe that would help things but I dunno. I'm gonna play around with that some time and figure it out.
Click to expand...
Click to collapse
This is the first I have ever heard of this type of issue...
Logs please, with thorough detail on what happened. I can't recreate this, and 99% of others can't either (or just put up with a non-functional phone. Seems doubtful...)
Edit - as far as I know, the OP has fixed all of the issues they were having... maybe they can chime in with the process, but my kernel would have nothing to do with cell service.

Alright, here's a logcat... it's weird, I can only hear the first word they say and vice versa. Then the call gets quiet but stays connected. Then after clicking hang up, the call isn't really hung up. I have to go back to the dialer and click hang up again. Then, after a minute or so I'll hear the hang up tone and it'll finally hang up. I'm doing clean installs so I'm not sure what's going on here. Hopefully this will help resolve this issue, 'cus it's a huge problem for me :/
EDIT: Just flashed a stock rom and I'm not having this issue at all.
Sent from that one MoPho... Q

Anyone have a clue what's going on with my phone?