Even after uninstalling it with titanium backup,root explorer and native android in menu it keeps popping up in notification bar with these ill-effects:
It closes out any apps or programs I was using!
It automatically puts me on speaker when I make or receive calls
Screen orientation cannot be disabled
Screen lock cannot be disabled
Volume is lowered when playing music
stays at the same volume and cannot be adjusted.
Some suggestions were to disable automatic startup and bluetooth in Car Home's menus when it pops up, I did not see such option. Now the menu does not pop up anymore, only the steering wheel icon pops up in notification bar to let me know its here to make my day a living hell again. Everyday, Every Hour, Every minute. I've done full wipe,cache,dalvik, and reinstall of cm6 6.1.2 and it just wont GO AWAY! Please HELP!
I have the same thing. silly thing keeps poping up. trying somethings if i get it to stop ill let you know. let me know if you get it to stop
Go into a roms zip file, find carhome apk, delete it and wipe and flash. I'm not sure if this will work since I don't know if you have to change the code too
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
Or use Root Explorer and go to /system/app and delete it there. I never used it anyway.
I had that same problem on that rom
I found 2 carhome apk's in my system apps. I deleted both but then had fc's.
So I'm curious off you find a solution
Swyped from a galaxy far far away......
thanks i tried that did not work. just done got a older nan backup and put it ok it seems ok for now.
thanks m8
car home is a virus
i tried. i lookd into the roms, cm7 rc1 n rc2 n none of them have it. i figured if i delete the car home apk off gapps.hdpi.zip file it would work.. since thats the only other place its located in. nothing. it still pops up. i being dealing with thins for the last week. i did everythin. clean factory wipe, went from cm7 to cm6 in all the versions available. n nothing. car home still pops up.
other known issues that i think might be connected;
calls are answered with speaker on.
when usb is connected, the notification does not give you the option to mount sd (only in cm7 rc1 n rc2)
robenever said:
i tried. i lookd into the roms, cm7 rc1 n rc2 n none of them have it. i figured if i delete the car home apk off gapps.hdpi.zip file it would work.. since thats the only other place its located in. nothing. it still pops up. i being dealing with thins for the last week. i did everythin. clean factory wipe, went from cm7 to cm6 in all the versions available. n nothing. car home still pops up.
other known issues that i think might be connected;
calls are answered with speaker on.
when usb is connected, the notification does not give you the option to mount sd (only in cm7 rc1 n rc2)
Click to expand...
Click to collapse
gapps.hdpi.zip? WTF? Quit running your own GApps. Wipe everything, get RC2, flash 20110307 GApps and go from there. Solves all problems.
Not sure if this will help you much but I had this same problem once and ended up unrooting my phone and even then it did it so I went into a sprint store and they replaced it free of charge.
crakerjaks said:
Even after uninstalling it with titanium backup,root explorer and native android in menu it keeps popping up in notification bar with these ill-effects:
It closes out any apps or programs I was using!
It automatically puts me on speaker when I make or receive calls
Screen orientation cannot be disabled
Screen lock cannot be disabled
Volume is lowered when playing music
stays at the same volume and cannot be adjusted.
Some suggestions were to disable automatic startup and bluetooth in Car Home's menus when it pops up, I did not see such option. Now the menu does not pop up anymore, only the steering wheel icon pops up in notification bar to let me know its here to make my day a living hell again. Everyday, Every Hour, Every minute. I've done full wipe,cache,dalvik, and reinstall of cm6 6.1.2 and it just wont GO AWAY! Please HELP!
Click to expand...
Click to collapse
i flashed to Sense then updated PRL, then Profile. Then i flashed back to CM6 its bn working eversince
i rather make my own gapps n take my chances than just sit here n do nothing. however, i am working unrooting my phone and rerooting it again. if that doesnt work.. then its back to the sprint store
I did a full wipe and reflashed CM7 RC2 along with the gapps that came with it, and so far no problems *knocks on wood*.
I had this problem and found that the culprit was pocket lint lodged in the phone's usb port--grounding out one or more pins.
I read a post about a guy who made his own car dock cable by grounding pin4, auto-triggering car home, like the real evo car dock, whenever he connected his cable.
I got thinking and grabbed out my jewlers loupe and saw some crud at the base of the usb jack. With the battery removed I got a slender sewing needle and bent the tip slightly with a plires to make an "r" shaped hook.
I gently scraped around the bottom and edges of the usb jack on the phone with the needle and pulled out a years worth of greazy lint crud that literally wedged against the pins, no doubt grounding out one or more of them, thus kicking up the car dock shenanigans. Seriously, a lot of lint.
Once the dock issue showed up, prior to cleaning the jack, the car home app showed up EVery time i plugged in usb.
I havent seen car home nonsense at all since cleaning out the jack.
prior to cleaning i called sprint having read about others doing the same. Without much hassle they sent me a warranty refurb (with 2.3.3 installed) to replace mine,
With a clean jack, i can send them back the refurb and keep mine as is.
hope this helps
So cleaning the USB jack solved the Car Dock app nonsense, that app is no longer popping up. However at present the phone is still defaulting to Speaker Phone ON for outgoing and incoming calls.. Will try reflashing etc later on to see if it has an effect
slackard said:
So cleaning the USB jack solved the Car Dock app nonsense, that app is no longer popping up. However at present the phone is still defaulting to Speaker Phone ON for outgoing and incoming calls.. Will try reflashing etc later on to see if it has an effect
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1107759
A story of how I fixed this problem over a month ago. Refer to post 5.
It's actually a hardware issue. There is a circuit on the EVO board that is fried. Of course sprint won't acknowledge this but have seen it happen on other phones.
Sent from my PC36100 using XDA App
tnerb123 said:
It's actually a hardware issue. There is a circuit on the EVO board that is fried. Of course sprint won't acknowledge this but have seen it happen on other phones.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My circuit board fried, then fixed itself?
I would be interested in where you got this information from.
Sprint does acknowledge this. I have the same issue and thought i solved it by cleaning the USB jack--not so.
I was just in the sprint store the other day with my faulty phone and after some digging the tech found a bug report titiled something like "speaker phone always on" in their bug database. Recommendations in that bug report were to clean usb leads and if that doesnt solve, replace the phone.
Sprint offered to replace mine without too much hassle and shipped a refurb overnight, but the new phone came with gingnerbread and is therefore unrootable (at the time of this post), so i started looking for another solution--to disalbe the dock features entirely.
I came across the app NoDock, which loads a kernel module that interupts communication between the dock sensor and the OS, preventing the dock & speakerphone shenanigans.
I dug around in adb shell a bit and found the kernel module being loaded by the NoDock app.
Its located in /data/data/com.nothize.free.nodock/files/ and titled "nodockm_2_6_37_4_cyanogenmod_01388_g0374804.ko"
I was able to load this module by hand as SU in adb shell with the following:
#su
#insmod /data/data/com.nothize.free.nodock/files/nodockm_2_6_37_4_cyanogenmod_01388_g0374804.ko
I will work on moving this module out of the NoDock app directory and see if i can get it to load on-boot without needing the timelimited APK. No offense to the app's author, just not interested in a pay to play 'app' that loads simply loads a kernel module that can be loaded with a simple script etc or by hand.
I already sent the gingerbread phone back to sprint and will stick with this solution for the time being.
Hope this helps anyone with similar problems.
Well you're not offending me, you're just thinking in a different way than I'm and (if) you haven't leave any destructive comments about it.
What the app worth is really the kernel module.......the app interface however, provides settings that may serve other use cases.
I wrote the kernel module myself, but not ripped off from anything else, so you cannot say that you are not willing to pay for just the "app" that loads the kernel module. In fact, you're paying the novel ideas and the novel kernel module too that took most of the time for the research to make it works for various phones including S2. You can read more if you have visited my website. So if you got the knowledge and skills, as I've already documented how I am doing this, you should be able to write your own kernel module.
The free trial app was a free app a long time ago......until I felt offending by some "free version users". They emailed me for support, they left silly comments, complains and complains out of a reason. I lost my hope to them while the paid users have so much better quality.
And you're lucky to extract the old free trial version....IIRC, the expire has been introduced to the kernel module too since some version.
slackard said:
No offense to the app's author, just not interested in a pay to play 'app' that loads simply loads a kernel module that can be loaded with a simple script etc or by hand.
Click to expand...
Click to collapse
I had the same issue. Turned out that my issue wasn't a piece of pocket lint in the USB jack (which DOES cause the same issue)....instead it was a bent pin in my charger. I bought a new charger for $3 on Ebay and I have never had the issue since then. Common sense tells you that if you've gone through all avenues of software issues and the problem is still recurring then you need to start looking at physical aspects of the phone. In this case, the device that triggers car home automatically......aka the USB port and anything connected to it.
Related
I finally decided to root/s-off/ROM last week, and after following the many excellent guides around I got to a place where I liked the features and speed of the ROM I settled on (Incredible 2 HD 4.something).
Here's a breakdown of what I passed through to downgrade/s-off/root/recovery/ROM:
Friday
Downgraded from 2.3.4/Hboot0.98. Successful.
Installed CWR, su, busybox. All well.
Boot once into stock VZW GB 2.3.3.
Grab full nandroid backup of "stock" 2.3.3 as a failsafe.
Back to CWR 5.0.2.0. Installed CM7 / gapps. All still well. I wanted Sense back, so hunted for a good candidate ROM.
Settled on Incredible 2 HD from themikmik.com
Initial flash acted like I wasn't rooted (CWR .zip install said (bad) when I selected the ZIP. md5sum is perfect, so it's not a bad copy. Battery pull later and a few full wipes, install is fine.
Saturday
Inc2HD ROM is really sluggish so I decide to nuke it from orbit and start over again.
I grab the Super Wipe script and run.
Reinstall DInc2HD ROM.
Rom is very responsive, acting much better.
Start reinstalling all my apps again.
Deal with the stupid problem of sms messages from VZW (http://www.droid-life.com/2011/06/2...age-from-vzwnmn-here-is-how-to-stop-them/]fix detailed here[/URL]).
Receive and place several calls as normal throughout the day.
Gradually reinstall apps only as I need them. Keeps down the clutter
Sunday
Receive and place several calls as normal throughout the day.
Gradually reinstall more apps only as I need them.
Getting to a good state with apps re-authed and reinstalled. Decide to grab another nandroid checkpoint backup.
Backup is fine, resume normal daily use.
Monday (today)
[*]Alarm goes off as intended (yay - I have 'Clock' back after being missing on my phone since 2.3.3!)
[*]Listen to some spotify paired to my car on the drive into work
[*]Colleague calls me .. and I can't hear him. I figure it's a bad connection so I call him back. Still can't hear him through the earpiece. As a quick test I switch to speakerphone, I can now hear him.
I figured this was a one-time thing, but start test calls to DInc2 from my desk.
Damn - earpiece isn't passing any audio. Speakerphone toggle gets me audio, as does plugging in my 3.5mm earphones.
I then test other apps I know I can toggle to playback through earpiece, and no dice (Google Voice, etc). All I can hear is a very very faint buzz while a call or playback should be coming from the earpiece. When I hang up, the faint buzz in the earpiece goes dead again.
Made sure bluetooth radio was off to rule out pairing to other devices (though I haven't re-paired since wiping anyway). No wifi radio on either. All alone with the mobile network radio.
Now I know I've done a lot to the phone over the weekend, but I can't find any common cause of what might have happened between the last good call I placed on Sunday evening and today (Monday). Phone sat all night charging on my nightstand. No physical damage or anything like that.
Thinking this may be a ROM or app issue, I bounce back to my known-good snapshot of the 2.3.3 stock ROM. Problem persists - crap.
To further rule out, I full wipe and install CM7.1.0.1 from scratch just to get another baseline. Still no earpiece audio - getting frustrated!
Whatever it is, it isn't exhibiting signs of being a ROM or app issue because it persists full wipes (wipe/cache clear/dalvik wipe, and another pass even with the super-wipe script).
Yes, I've checked basics like making sure In-Call Volume is not muted. I've also installed Audio Manager to make sure there's not some lurking audio volume problem. All sliders maxed before, during and after test calls.
Uninstalled any audio-related app to attempt to remove any hold on audio output. But recall here - it's following across ROMs and wipes, so this is just busy work.
Logic says then that either
I hit some rare bug?
The process of mucking around with recoveries, ROMs, and other lower-level items has flipped a bit somewhere that will persist full user-space wipes/partitions/formats.
it's faulty hardware (which I have a hard time believing, but stranger things have happened!) This would just have to be horrible timing.
Searches on here and other sites don't bring up too much for the Incredible 2 and this kind of earpiece issue. There's a passing mention of a "silent audio bug" here, but doesn't seem relevant (nor much detail given).
I've grabbed output 'c:\> adb logcat -v time -b radio > alogcat.radio.txt' while making a call and switching between earpiece (default) and speakerphone. No really good clues there. Changes in logging verbosity didn't show too much of interest. I'll pastebin it after I scrub my phone number out if anyone's interested.
So after the wall of text ... anyone have any ideas?
I'm in it to win it with this, so I'm not unrooting and warrantying this pig I'm due for a new phone but there's nothing I want other than to just have my DInc2 back working.
I'm off to keep searching. Wondering if there are other debug-level tools/switches via adb that'd let me poke at devices, but I'm guessing those interfaces may not be as readily exposed as I'd like.
Thanks in advance all.
tl;dr - Incredible 2 earpiece randomly stopped working, but speakerphone and headphones still output phone call audio fine. Follows across wipes/ROM installs. LOLWTFBBQ?
I hate to say it, but your earpiece is probably broken... U may have smashed it with your keys in your pocket (did that on og dinc)...
Sent from my Incredible 2 using xda premium
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Sent from my Incredible 2 using xda premium
faehsemc said:
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Click to expand...
Click to collapse
Fair enough. I hadn't ruled out full-on hardware failure I just found it to be the least-likely of the candidates.
I had to replace the speaker in my original Incredible, so I figure it can't be too much tougher to do in this one. I'm going to exhaust some other troubleshooting first (my wife has a functional stock DInc2 that I want to compare some logcat output from, see if anything stands out when making a standard voice call).
I'm always careful to change ONE thing at a time then test to make sure my variables are where I expect them to be, so this one threw me. I'll post back with results, and hopefully get my earpiece back .
OK, I ordered a replacement earpiece and replaced it. This did not fix the audio. I tested both the original earpiece and the new earpiece before installation by using a low speaker-level source and confirmed that BOTH actually work fine and produce sound as expected.
While the phone was disassembled, I made sure all contact points were good for the earpiece. This isn't a physical problem.
So, this takes me back into the software/firmware/radio arena.
And more specifically, in order to persist all wipes and reinstalls, this has to be something below.
I'm going to use adb to flash a radio (I think there's one newer than the one I have installed, something.622? Not down at bootloader to check right now).
If this doesn't do it, anyone want to buy a DInc2 for parts and dev?
The newest radio is .1111 before that .722
Sent from my Incredible 2 using xda premium
Good call on the 1.09.01.1111 firmware. I found and flashed that instead of .722.
No effect unfortunately.
So next I'm thinking that perhaps whatever kernel I brought with me from the first ROM flash could have jacked something up in terms of audio modules or packages. It's a long shot, but I'm going to grab something like nc2_2.6.35.14#21-2.3.4.zip (non-AOSP) and flash that.
Now that I have ruled out actual hardware failure, I'm just too stubborn to give up on this .. open to productive ideas on things to check, methods to troubleshoot or rule out, etc. TIA.
What about Tue hardware connection from the speaker to phone itself? I don't know much of the board on the phone so I can't give you ideas of where to test, but if you can see where the leads go I would say follow it
Sent from my Incredible 2 using xda premium
Right. I disassembled the phone again late last night and traced back to the extent I could follow. I didn't find anything glaringly obvious or bad.
Also of note, if I'm in a super-quiet room and keep the earpiece near me with no call in progress, I hear literally nothing. As soon as a call is initiated, I hear a very faint "sputtering" sound from the earpiece (original or new earpiece), which means the symptom here clearly impacts either speaker.
So something upstream from it ... whatever pathway sends audio to this device isn't getting instantiated properly? That'd make me look to the kernel or driver to understand what pathway does work when routing audio output to the rear speaker that doesn't properly route it to the earpiece for the same call.
Recapping for my own sanity:
- Physical causes == none seen, mostly ruled out via disassembly and inspection, earpiece replacement with known-good part and known-good reassembly.
- Radio == upgrade to .722, .1111 and back to .622, no change.
- ROM == not likely culprit (problem persists any ROM replacement)
Can't fight off the nagging feeling that the act of starting down the road to S-Off + su + rooting did something here.
Given that there are guides to un-rooting (don't think you can un-S-off per se though, right) I may give that a shot since this phone is essentially a guinea pig now. Going to see how far down this rabbit hole I can go.
While I'm stewing on that does anyone have links to android filesystem reference material? I'm thinking the high-level relation between things like bootloader, recovery partition, user-space filesystem and on which levels I can address these with tools like adb. I want to try to understand if some bit could have been flipped at a layer lower than what flashing a ROM or kernel can recover, but perhaps higher than a baseband radio flash. Knowing where all these live and how they interrelate sounds interesting to me. Then I can form a better working theory on what could cause the stupid problem I'm having and if it's plausible to be in software/firmware somewhere.
There is an unrooting guide on YouTube. I find it hard to believe its software, but I work on a radar weapon system that has proven me wrong many times... But if you have flashed multiple roms then the kernel would've been reflashed atleast once and if you are doing a full boot and system wipe, whatever drivers previously installed would have been overwritten... I'm leading to believe there is a shorted componant on your board and because the voltage is so low on these, there moght not be any visual evidence. Unless u have schematics of what voltage is applied where, there isn't a way to test most of them. Especially if the gates are set to be low when applied, vice highs. I would s-on factory reset and of that doesn't work, its hardware
Sent from my Incredible 2 using xda premium
Agreed. I work with enterprise hardware/storage/cluster systems, so I'm driven by nature to root cause this silly thing - but yeah, occam's razor seems to say here that it's just a really stupid coincidence that some random component failed just at the time I began making other changes. And I can't let it go
This is even more frustrating to me because I always make a point to introduce only one change at a time then test the outcome!
After poking through the SDK/reference guide about AudioManager, I was reminded that GV has access to the earpiece audio path. While I could just make test calls in/out, this saves me from burning minutes in the process.
As a quick-and-dirty workaround (for anyone who may stumble on this in the future), you can use Google Voice to act as an internal earpiece playback test tool.
Install and then go to settings and tell it to play back via the earpiece by default and not the speaker. Then (assuming you have voicemails to play), attempt playback. You can toggle between the two audio outs in a much quicker way than I've seen in any other app. Works close enough for me to serve as a test tool as I make discrete changes as I go through troubleshooting.
Maybe there are other media playback apps that'd offer a toggle to the earpiece for playback (but why?), though I didn't look. Seems like the AudioManager reference guide implied that the earpiece was a more "protected" audio path than the speaker (but that's likely just for actual carrier network voice calls).
Cheers,
I'm really getting a kick troubleshooting.. I've been recruiting for a year and a half now.. miss working on gear.. one and a half years left and back to my ship... Can't wait
Sent from my Incredible 2 using xda premium
I actually doubt it's your ROMs --- I'm running latest unmodified vz gingerbread and all of a sudden about 5 days ago I could no longer get earpiece to function - my only guess is something shorted out because of an off-market USB charger that I got 3 of for 7 dollars off Amazon...
Anyways, I had the same sorta flutter that you seem to hear when on a call and there should be sound... and otherwise silence when silence is expected... anyways I replaced it with a brand new earpiece and EXACT same issue is happening still.
Not sure whats up but this may be the world telling me to use my Bluetooth headset more anyways... I'll post if I find anything that fixes it, but I ain't gonna hold my breath given how few ppl seem to be experiencing this issue.
Good luck
Since I am not seeing any posts with this issue I am going to assume that it's something stupid that I am missing, possibly a setting or whatnot.
Anyhow; to the problem: I am being plagued with "card mode" on my device, it's been popping up periodically and stops all connections whether WiFi or standard 3G/4G network. In addition to stopping all incoming connections and interrupting whatever action being performed at the time. It generally causes the apps that are running to hiccup and occasionally crash (crashes usually limited to things like ROM updater or any keyboard [stock or added] that I happen to be using) this hadn't happened when I originally flashed the ROM, I installed it correctly, Talk never crashed, never had a single problem. But, then I got the updated version of the ROM (1.0.4.4) (was running on the slightly earlier version initially with 1.0.4.3 with no problems). I thought it may just be a glitch in the updated ROM, so I loaded up the backup of what should have been the stable iteration I had last month with no glitches. So, I did a complete wipe of the phone from boot (with the exception of the ROM backup which I had moved to an SD card with no other data just as temporary storage) No dice; the car mode notification and setting started popping up on the backup about 45 min into flashing it. Am I missing a setting that should display "car mode" parameters? I do NOT have the option to set card mode on the device normally, and I do not see any options to change this setting in the standard systems menus. I uninstalled most of the apps that I had just in case one of them was causing the issue, but now that the phone is pretty much clear with the exception of APEX (which was standard), contacts, Sprint VM and STOCK Gmail and Talk (the non-Kuban-themed stock apps).
Current system setup: Blu Kuban v 1.0.4.5 with default Kernel (speaking of which, anyone have a suggestion for a favored Kernel to use with BK?)
Any nudge in the right direction would be appreciated. I don't mind having to flash my system fresh again as I have done it several times thus far (until I started using BK, that is) but bear in mind that I have already flashed it fresh just recently.
Usually car mode trips like this are caused by a short in the microusb/charging port. Sometimes its dust, dirt or pocket lint, others it's actual physical damage to the port or its connection to the board. If its dust or other debris a can of computer duster or a toothpick(for lint/fuzz) will usually correct the issue. However if its physical damage replacement may be in order as repairs aren't always striaght forward and can do more harm than good when attempted.
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
Check in settings/language and input/text to speech output
There is a driving mode toggle there you may have set. It's not checked by default.
A far as the kernel goes, you can't beat the Kuban kernel that comes with it. He's got so many tweaks built into it, your gonna have a hard time finding a better option.
Yeah, I still don't know WHY it was triggering. Took some canned air and sprayed the USB port and then took a duster to it just in case. Driving mode was disabled through the tts-output, so instead I have enabled it and unchecked all the settings. That seems to have done it, so cheers! I love how when I look for something I focus out areas that don't make sense to me and I never even thought of language input for the text to speech option.
I know this will sound dangerous, but I fixed this by taking a toothpic and very gently pushing down on the little piece inside your USB port.
This happened about a month ago and it's never happened since I did that trick.
Obviously be careful please
Sent from my SPH-D710 using xda premium
NihilistZealot said:
Yeah, I still don't know WHY it was triggering. Took some canned air and sprayed the USB port and then took a duster to it just in case. Driving mode was disabled through the tts-output, so instead I have enabled it and unchecked all the settings. That seems to have done it, so cheers! I love how when I look for something I focus out areas that don't make sense to me and I never even thought of language input for the text to speech option.
Click to expand...
Click to collapse
The canned air probably did the trick. About 99% of the time this occurs it's from dust or lint shorting the port and causing it to think the dock in plugged in. Ever so often it's caused by physical damage from a cord getting yanked out or inserted too roughly. Glad u got it fixed
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
hi everyone, been coming to this forum over the last couple of years since i got my htc evo and it was a very helpful site to get my phone rooted.
as of a couple days ago, my phone has become problematic that it answers all the calls with speakerphone on, I've done everything under the sun and its a hardware and software problem combined and revolves around car panel mode. I think my son may have forced the charger cable and messed up a pin or two.
anyway, long story short, i am about a month away from renewal, dont want to spend any more money on this phone, im looking for a basic rom that excludes car panel app but has the rest of the day to day use functions of the regular phone
I used freshevo 4.3.3 (i think thats the build #) for 90% of the time, i threw on CM7 and tested out calls, it did not kick it into speaker mode, then I went to download apps thru market, no market, i then got GAPPS downloaded and that inlcuded the car panel mode (DOH!) so i went into the GAPPS file, removed the car panel APK and reloaded, it still have some remnant of it in the GAPPS and im not a developer so i dont know the programming side of things but it kicks into car panel mode (but without the car panel app installed)
any recommendations? please? i just need something to get me by for another month or so. the rom can be a stripped down version but has all functionality of the phone (dont care about 4g) and without any car panel software.
Thanks!!!
Yeah...
Either...
Reinstall the rom...
Or redownload the car panel app and turn off the option that is enabling this.
I don't understand why there are pieces of car panel still there. What did you uninstall it with?
jwitt418 said:
Yeah...
Either...
Reinstall the rom...
Or redownload the car panel app and turn off the option that is enabling this.
I don't understand why there are pieces of car panel still there. What did you uninstall it with?
Click to expand...
Click to collapse
The way i removed the car panel APK was uncompress the GAPPS folder, removed the APK directly from that, recompressed it without it in there but like I said, the app is gone but there is something still there that makes it think it is...sucks!
OK...how about this.....i can reinstall CM7....is there a watered down GAPPS that ONLY has market and maybe Gmail inlcuded in it?
HvNd4Speed said:
The way i removed the car panel APK was uncompress the GAPPS folder, removed the APK directly from that, recompressed it without it in there but like I said, the app is gone but there is something still there that makes it think it is...sucks!
OK...how about this.....i can reinstall CM7....is there a watered down GAPPS that ONLY has market and maybe Gmail inlcuded in it?
Click to expand...
Click to collapse
You can go under the apps and themes section. Look for topic with inverted gapps. You can install them individually
I searched the AT&T Galaxy S III General forum and saw no other posts similar. Essentially, I was wondering if anyone had experienced other bugs in the stock firmware. I am not rooted and have not modified my phone's software from stock.
There are two bugs I currently have seen. One I can and will provide screenshots of. This is where during the lockscreen the formatting will be incorrect, such that the last number on the time will be small and the charging text appears on the same line. Also note that the lockscreen shortcuts at the bottom are spaced oddly. I always have five icons, yet sometimes only 3 or 4 show spaced unevenly. I can reproduce this by watching Netflix and while a video is playing, I lock the screen. When I first unlock it, this will happen. This will fix itself if I relock the screen and wake the device again.
The second bug is in the messaging app. Sometimes when my device falls asleep by itself while I have the keyboard up and active on a thread, and I wake it, the keyboard is unusable. I can click on the message block to bring up the keyboard, but all of my keystrokes are not entered into the message block. I have to back out of the keyboard and thread, to the thread list, then go back to the thread. My previous keystrokes are still not showing, but the keyboard will then work.
Anyone else noticed any bugs?
I'm fine on my phone
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I've had the second bug happen with the keyboard maybe a handful of times since I got the phone but definitely not a regular occurrence.
I wouldnt worry too much about it but if it bothers you that bad just try a factory reset.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
No problems here
Sent from my SAMSUNG-SGH-I747 using xda premium
MercilessLTD said:
The second bug is in the messaging app. Sometimes when my device falls asleep by itself while I have the keyboard up and active on a thread, and I wake it, the keyboard is unusable. I can click on the message block to bring up the keyboard, but all of my keystrokes are not entered into the message block. I have to back out of the keyboard and thread, to the thread list, then go back to the thread. My previous keystrokes are still not showing, but the keyboard will then work.
Click to expand...
Click to collapse
I've only experienced this issue that you describe. I've gotten used to it, so I'm now indifferent towards it.
I've had issues with the battery life however and how the actual "percentage" is being reported, but I think that it's just Jelly Bean that is causing the issue when my device is restored to stock setup as opposed to running ICS. Sometimes, my phone gets really warm overnight (and I can assure you that nothing is running in the background). Looking at the battery graph, I see a sharp drop within the space of about 20 minutes. This causes the back cover of my phone to be discolored. My i747 is only 5 weeks old and I'm the original owner.
phone minimizes
I have an issue where my phone screen turns off when I'm it for a while (typically at work I use a wired headset). When I wake the phone up and swipe on the lock screen, the phone shows the phone "app" for a second then it jumps to the home screen (as if I hit the home button). Typically I'm unlocking the phone so I can either hit a number on the phone (like, press 1 for English) or I'm wanting to hang up. So I have to go back into the phone application to do either task.
ICS didn't do that to me.
Me and a few others have experienced a bug where the external sd unmounts itself at random. Mostly when the screen goes to sleep. For one freezing the MTP application with tibu solved his sd problem but by doing that you cant mount your phone to a pc. As far me nothing has helped yet. My external sd just unmounts at random and I have to remove it and put it back several times to get it to work again and sometimes and I have to format it in the pc to get it to work again. This has happened to a a lot of tmobile users. I never noticed this problem on ics so im assuming its a jb problem. Its not a micro sd card being bad because it does it with my other cards to and one is a very expensive Samsung card..
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
get2brad said:
I have an issue where my phone screen turns off when I'm it for a while (typically at work I use a wired headset). When I wake the phone up and swipe on the lock screen, the phone shows the phone "app" for a second then it jumps to the home screen (as if I hit the home button). Typically I'm unlocking the phone so I can either hit a number on the phone (like, press 1 for English) or I'm wanting to hang up. So I have to go back into the phone application to do either task.
ICS didn't do that to me.
Click to expand...
Click to collapse
I think this has happened to me once or twice. But I guess with the scarcity it's happened I thought I was bumping the back button or home button with my face, i.e. a failure of the proximity sensor to correctly detect my face.
I just started noticing the Keyboard Messaging bug myself. Wasn't sure why it was happening.
I just remembered (or refreshed my memory since my phone just started doing it) that whether or not TalkBack is off or on, my phone needs to tell me which number screen I am whenever I slide my finger across the dots at the bottom of the home screen or the app drawer. Is this a different setting I am missing or is this another bug?
I have had the messaging bug occur a couple of times. No biggee to me considering it has only happened twice in a month's time. I have seen other phones with much more persistent and annoying bugs and by comparison, this is nothing.
no problems here... i like it a lot now
Problem on Stock/root
Hey, not sure if this is the right place for this post, but my GS3 is on stock jelly bean and rooted. For some reason I am not receiving incoming calls. I tried calling my phone from gmail and the phone rings, but nothing happens on my phone. Any ideas as to why this is
Luker161 said:
Hey, not sure if this is the right place for this post, but my GS3 is on stock jelly bean and rooted. For some reason I am not receiving incoming calls. I tried calling my phone from gmail and the phone rings, but nothing happens on my phone. Any ideas as to why this is
Click to expand...
Click to collapse
I'm not sure if this is the right place either, since this is generally non-rooted, although the topic doesn't specify that I suppose.
However, I would venture a guess that you may need to wipe your data and cache. Sounds like a default app issue to me.
If I use bluetooth headphones on my walk to work, then plug in wired headphones at work, the audio plays out of the speaker.
It's really annoying because it happens every morning (as it's too early for me to remember things like that) and blasts my podcasts to my coworkers. Removing the wired headphones and reinserting fixes the issue.
No issues here.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have never had any of these issues
Sent from my SAMSUNG-SGH-I747 using xda premium
miketigerwoods said:
If I use bluetooth headphones on my walk to work, then plug in wired headphones at work, the audio plays out of the speaker.
It's really annoying because it happens every morning (as it's too early for me to remember things like that) and blasts my podcasts to my coworkers. Removing the wired headphones and reinserting fixes the issue.
Click to expand...
Click to collapse
Actually, I've had a similar issue. I use Google Play Music (as a carry-over from my Nexus S). When the first song of the playlist would finish (using the headphone jack to play through my car stereo), the second song would start on the phone speaker.
It doesn't seem to happen anymore, but it did directly after the JellyBean update.
PIN Lock Instantly with power button
I am upset that the "Lock Instantly with Power Key" option missing from 4.1.1. I have been searching for a fix, but I must be the only one annoyed by this, or I'm bad at searching.
...
I have a pin lock but am used to a 15 min delay before I need to enter the pin, and being able to push power to shut the screen off at will. That is no longer an option as it always will lock to the PIN screen if the power button is pushed. It is very annoying to me.
Another bug is the Keyboard defaulting Samsung Keyboard on reboot. Every time I restart, I have to go back into settings to select Swiftkey.
Here's the deal. I have an iBolt car dock (that specific really shouldn't matter) and Tasker profiles to turn on GPS, Bluetooth, etc while my phone is plugged in. Been like that for months. Up until about a week and half to two weeks ago, my phone app would crash when trying to receive a call while in said dock. The message I got was "unfortunately, the process com.android.phone has stopped". When I noticed, I was running Carbon. I clean flashed the nightly I was on and same result. I then tried Deviant, Slim, JellyBeer, PAC-man, etc. All of them gave the same result. Same wipe procedure for all of them. Same apps as I've always had. I then flashed AOKP M1 and everything worked. Then I tried Task's AOKP. Same thing. Everything worked. I don't get it. I posted the issue without a logcat (as pulling one of those while driving is a no no) in those respective dev's threads but it seems they don't know what's going on with everyone else. Hence, this thread. If you are running any of the ROMs I mention and experienced the same problem, post here. If you have logcats (ballsy), even better. I figure this would be the best way for all the devs of those ROMs to see what is happening and so the problem can be nailed down.
I'm also using an iBolt dock. Posted this in Xone Deviant thread: http://forum.xda-developers.com/showthread.php?t=2215840&page=55
itsmikeramsay said:
Not 100% sure bro, haven't been able to test it...
Click to expand...
Click to collapse
CrackerTeg said:
@ itsmikeramsay. Did you see this a few pages back? Thoughts?
Click to expand...
Click to collapse
Same here. Phone ui crashes when call is initiated but call goes through. Catlog attached.
Glad to see someone else feels my frustration with this. I battle this issue all the time. I have 2 iBolt docks(the regular one & the pro dock) & have had this issue with both. If not the not the incoming calls freezing the phone, its the phone rebooting when pluging it in, or the dev will update the rom and the usb audio doesn't work at all. I'll give task's AOKP a try to see how things with it. I was a huge fan his roms in the past up untill an update and the usb audio stopped working. In that situation, I usual just try a couple different roms untill one works. But then, the incoming issue happens or it reboots when docked and I feel like throwing my phone out the window
btw, i got an email today about the prodock cables being shipped. I've been using the one that came with the first iBolt
If my wallet would allow it, I would buy a headunit with bluetooth and use a NFC chip to put the phone in dock mode and not have this issue regardless of what rom i'm running. but my wallet stays empty
---------- Post added at 01:16 PM ---------- Previous post was at 12:41 PM ----------
I'm pretty sure the usb audio out working on some roms/updates vs. not working others is due to something in the kernel. Ex. I flashed the latest deviant xone update(2.0) and the didn't work. So I reflashed the previous version (1.0 stableish) and the audio works.
I hope this gets resolved 'cause I enjoy listening to podcasts & playing ingress during my commute only to have it ruined by a phone call that freezes my phone, rebooting booting and listening to my wife "quit ignoring my phone calls"
Sent from my SGH-I747 using xda premium
Interesting. My complaint has nothing to do with the audio out portion of it as I use my phone for browsing and as a phone. I have my tablet or iPod for the music in my car. So the complaint has nothing really to do with the iBolt but the phone being docked and not being able to use the actual phone function. If the usb audio gets fixed, bonus but I'm much more concerned with the primary function of this device.
After doing a bit of research, it seems that samsung didn't implement call audio through the dock connector. I know this is not your direct complaint BUT if you are using the ibolt cable that has the dock resistor( that tells the phone to go in dock mode) and the Rom/kernel is trying to route the audio via the usb than the phone may be getting confused. I think the solution to your issue, since your not concerned about audio out, is to replace the supplied cable with a standard data/charging cable. I haven't tested this theory, but i'm pretty sure taking the dock resistor out of the equation will fix the phone freezing when receiving a call.
I did have a rom installed at one point that had audio out working AND didn't freeze on incoming BUT had an unrelated bug that drove me nuts, so flashed another rom. It's too bad I can recall which rom and which release it was
Thing is, I have a Parrot bluetooth adapter that my calls go through. They don't go through the dock at all. I have a tasker profile that triggers the phone to go into car mode with Google's no longer supported Car dock app when the device is plugged in. It also turns on bluetooth, GPS, blah blah. Like I said in the OP, everything was just peachy up until two weeks ago where something in those ROMs got borked. Either way, I'm now running Carbon's latest and the issue is gone. Whatever got messed up is now fixed. I wish I knew what it was tbh but I can't read git.
I would like to add my two cents.
I too have an iBolt dock for SGS3, and an after-market radio with bluetooth.
I have tried several ROMs (CM stable, LiquidSmooth, ParanoidAndroid), and all of them exhibit the same behavior:
Going into the docked mode is flakey at best. 90% of the time the phone doesn't recognize it has been docked.
Now comes the "best" part: on disconnect from the dock the phone's bluetooth stack apparently crashes. The bluetooth connection gets immediately lost, and the phone's bluetooth status is stuck in 'ON' position. After that there is no way to turn the phone's bluetooth 'OFF' and back 'ON'. The only way to restore is to reboot the phone.
I haven't tried to pull the logs from the phone yet, but it may be possible if I take the dock home and try to repro the condition.
Not asking for answers, just voicing my frustration hoping to draw dev's attention to the problem.