Yet another ROM comparison. I've been using CM since I got this phone in May 2013. I love CM. It is clean, fast has a ton of nice features and is NOT TouchWiz. I've been loyal to it since I got this phone. I had it on my previous Atrig 4G, too. The problem is that not everything works in CM on the d2att. I blame Samsung for this, but do not really know where the blame lays. I read reports that Samsung withheld the source which made it tough to get everything working correctly. The Bugs list on CM for this phone is not complete mainly with regards to Dock and Bluetooth, IMO. I have not tried any other AOSP ROMs, but some of these bugs may be there as well.
I recently decided to try the latest 4.4.2 stock rom and it seemed to work OK, but I had to freeze and uninstall so much stuff. I discovered S3Rx and am now very happy with my phone. I still have TouchWiz showing its ugly head (most prevalently in the pull down and dialer/incallUI), but now everything works!!!! The new modem NJ1 has better sensitivity (I can get calls in places when I had no signal previously). Bluetooth works correctly. I can have multiple BT streams and not lock up the phone (Audio and serial or serial and phone). Previously, it would drag down and both would eventually fail. BT connects more reliably and readily. I have not tried dock audio, but there is a selection for it and I am guessing it works. (I did try dock USB audio and not only does it work, but it is not noisy like it was in CM10/early CM11 when it was functional) The only niggle is car dock identification. When you place it in the dock, the car mode icon illuminates, but no app is launched. I had to create a Tasker profile to get it to launch the old Android Car Home app. To get the home button to resume to the Car Home app (known issue with car home), you need to enable the car home button through an exposed framework module. It all seems to just work. Also, no random reboots.
Hope this helps someone who is still trying to get life out of this great piece of hardware. If you are struggling to get the phone to do all it should do and are frustrated with CM, I recommend this rom
keithspg said:
Yet another ROM comparison. I've been using CM since I got this phone in May 2013. I love CM. It is clean, fast has a ton of nice features and is NOT TouchWiz. I've been loyal to it since I got this phone. I had it on my previous Atrig 4G, too. The problem is that not everything works in CM on the d2att. I blame Samsung for this, but do not really know where the blame lays. I read reports that Samsung withheld the source which made it tough to get everything working correctly. The Bugs list on CM for this phone is not complete mainly with regards to Dock and Bluetooth, IMO. I have not tried any other AOSP ROMs, but some of these bugs may be there as well.
I recently decided to try the latest 4.4.2 stock rom and it seemed to work OK, but I had to freeze and uninstall so much stuff. I discovered S3Rx and am now very happy with my phone. I still have TouchWiz showing its ugly head (most prevalently in the pull down and dialer/incallUI), but now everything works!!!! The new modem NJ1 has better sensitivity (I can get calls in places when I had no signal previously). Bluetooth works correctly. I can have multiple BT streams and not lock up the phone (Audio and serial or serial and phone). Previously, it would drag down and both would eventually fail. BT connects more reliably and readily. I have not tried dock audio, but there is a selection for it and I am guessing it works. (I did try dock USB audio and not only does it work, but it is not noisy like it was in CM10/early CM11 when it was functional) The only niggle is car dock identification. When you place it in the dock, the car mode icon illuminates, but no app is launched. I had to create a Tasker profile to get it to launch the old Android Car Home app. To get the home button to resume to the Car Home app (known issue with car home), you need to enable the car home button through an exposed framework module. It all seems to just work. Also, no random reboots.
Hope this helps someone who is still trying to get life out of this great piece of hardware. If you are struggling to get the phone to do all it should do and are frustrated with CM, I recommend this rom
Click to expand...
Click to collapse
Be careful with this type of post as it encourages competition between devs.
Just an option, but how about just "reviewing" Roms,
I created a thread on " whats your favorite Rom and why" and a day later it was pulled by the moderator.
CM has come along very well recently
Related
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.
This problem became evident with DK28 and I was hoping it would be fixed w/ EB13 since, ya know, it was an 'official' update but it still sucks.
Has anyone found a fix for it yet ?
Thanks in advance
I thought I read somewhere that the Odexed eb13 the Bluetooth worked and the deodexed version it didn't. I might be wrong though.
Not the case for me - EB13 not working with Bluetooth with Samsung Sprint Stock version, or ODEX'd or DEODEX'd ROM versions either. See my post here on another Bluetooth thread.
dhvmoon said:
This is a problem that goes away if I simply go back to a DK28 based ROM (which I have no plans of doing), but appears with any flavor of the EB13 update available.
On a day when I didn't have a lot to do, I decided to do some testing to see if I could find the magic combination of EB13 loading (upgrade.apk, ODIN .tar/.pit load, Samsung SWUpgrade and the DEODEXed [stock-ish] ROMS available) to get my bluetooth working like it does on DK28. I have upgraded to EB13 stock, EB13 deodex, deodex w/EXT4 (no member ROMS yet) along with stock/Genocide/Daemon's kernels ... essentially every mix of install, ROM and Kernel available. Add to that, I also cleared data on the OPP application --- I tried to cover every base I could. That being said, I have narrowed down my list of issues with bluetooth on EB13 to:
Paired devices are not saved. I have a Jawbone ICON and I have to add it everytime my phone is rebooted.
(Only add once on DK28)
Unable to Pair and Connect on first attempt. It always takes at least 2 and most of the time 3 presses of Pair and Connect to get the Jawbone paired and connected.
(Paired and connected on first attempt on DK28)
When my Jawbone pairs up, if you watch the notification bar closely, my wifi will also do a quick off/on right after the notification shows "Paired" on the Jawbone. Before you ask - yes, I ran tests with the various radio's on and off just to see if that was the cause. Nope.
(Never saw this on DK28, but then again was not watching for it either)
Like others have said, I can voice dial using the Voice Dialer application on the phone, but I cannot voice dial by pressing and holding the voice dial activation button on the Jawbone (the start/stop/quick disconnect happens on the application).
(Press button, state name, call on DK28)
It did not matter what combination of the above I used, the result was always the above. I'll gladly assist in troubleshooting this issue, so if anyone out there knows what to look for in the logfiles, I'll gladly run a pair/connect sequence and capture the adb logcat output for review.
Thanks in advance ... None of these are showstoppers, in fact I love EB13 and also appreciate all the hard work done by the devs and contributors in these forums (plus I guess I need 10 posts now to add anything relevant to a dev thread ).
- Dan
Click to expand...
Click to collapse
dhvmoon said:
Not the case for me - EB13 not working with Bluetooth with Samsung Sprint Stock version, or ODEX'd or DEODEX'd ROM versions either
Click to expand...
Click to collapse
i saw the other thread and occasionally experience the same anomaly. i also ran into this w/ dk28.
both your problems and the ones i've described were evident on dk28 and i was seriously hoping that EB13 was going to fix it.
Seriously pissed that these are still here. I could deal w/ it on dk28 because it was a leaked build. This is disgusting.
I have the same issues, hopefully if CM6 gets fully ported they'll replace the BT stack. I do wonder, if now that the Froyo source is available, perhaps the community devs can look into it? So far on any of the Deodexed Roms BT either loses pairing or takes several times to connect. It's a bit better coming from a fresh EB13 install, however as all my headsets are a2dp compliant the media audio part connects only about 50% of the time Every new update so far seems to contain "bluetooth enhancements" and yet....
Edit: I checked right after posting and my phone is INDEED popping and clicking, just not as loudly as on DK28 :-(
I would really appreciate a fix for the bt voice dialing. Omg
Epic 4g
Hi, I am using an HTC Droid Incredible with the Skyraider 4.0 Rom with HTC Sense. I know that HTC and Samsung Galaxy S devices are known for their notorious yet annoying, inconvenient, evil, ****ty bluetooth in their stock roms. The main reason why I'm keeping a Sense rom is because of the tv out cable (yay Netflix on the big screen!). I was on CM7 before, which I loved, except for the occasional reboot and the inability to use my tv out cable. I think since I can tether my phone to my laptop and I can get an HDMI cable, it probably won't be a big a deal, but its still nice to have to be able to see your phone scree on the tv screen, especially for gaming. But I'm more impressed with playing these games on the go with both my phone and my gamepad, which so far I had to take apart to get the D-pad working. I still have to get one more button working Not happy that they were careless since I forked over close to 100 dollars, which included shipping.
But onto the point. I tried upgrading my firmware on the unit, but it didn't show the part where it showed to put in the "1234" pin, but did everything else and it looked like it said it was updated. Even before then I was connected to Bluez IME before updating the firmware (supposedly). I was able to type out with the buttons, excluding the few that weren't working and I even configured it with the key mapping in SNesoid, but for God forsaken reason, it didn't do anything when I pushed the buttons. This is really weird and its making me mad I was looking forward to a better experience than this and it's frustrating. I just want to know if there's any solution at all, anything before flashing the CM7 backup again. If there's anyone out there with a problem like this with this phone or similar, I would really appreciate it. Thank you very much.
By the way, I did post on the Pandora forums, but no one responded, not even Craigix or any of the other moderators so this is my only hope right now.
I'm having a similar problem with my SGT(p1010). BlueZ will say connecting in the notifications tray, and then the icp will time out and I get Error: failed to connect to socket. Any ideas anyone?
I believe in the booklet with the iControlPad says the way to do it is to hold Y down and then press and hold start along with Y. Make sure you updated the firmware too before you do anything. I'm loving my iControlPad. I don't have to sacrifice Sense and I can do all my old school gaming on my TV screen thanks to the TV out cable
Sent from my ADR6300 using xda premium
After spending all day on setting it up to my liking, and getting some additional assistance on locating the developer options, I had to say that this is officially my favorite ROM. That being said, I'm running into a couple of small issues, one I can do without, but the other I can't.
First, I have a 64gb SanDisk microSD card that I have used in my phone since I first bought it. It has always worked on every ROM I've ever used, however, now I can't get the phone to see it, no matter how many times I try to mount it. While in the phone, I'm also unable to locate it in Windows Explorer. I can deal without having the card if need be, but if there's something I'm missing, any help would be greatly appreciated.
Second, This is the crucial one...I have a Pioneer Appradio 2 in my car. Like the above problem, every single ROM I have used before has worked flawlessly with the radio with exception to one, however, even the one that didn't work properly still worked to some degree. I just ended up having intermittent snow issues on the screen. With the phone running and connected to the radio, bluetooth works flawlessly, my connection screens come up as they always do while the phone is attempting to make a connection, but once it's connected the screen on the radio goes totally black. What's funny, is I know it's working properly with exception to the black screen, because the touch controls still work, even though nothing is showing up. I can sit with the phone in my lap, and press the screen all day long on the radio and see the apps open on my phone, they just don't display anymore on the radio. Is MHL supported in CM10.1?
I am running the following nightly "cm-10.1-20121227-NIGHTLY-d2att.zip". I am using that nightly, because the one from the 28th left no service on the phone. Any help would be greatly appreciated, as if it's not supported, I'll have to drop the ROM which is something I don't want to do, otherwise my radio is totally useless to me.
Thanks in advance!
find anything?
liquidaluminum said:
After spending all day on setting it up to my liking, and getting some additional assistance on locating the developer options, I had to say that this is officially my favorite ROM. That being said, I'm running into a couple of small issues, one I can do without, but the other I can't.
First, I have a 64gb SanDisk microSD card that I have used in my phone since I first bought it. It has always worked on every ROM I've ever used, however, now I can't get the phone to see it, no matter how many times I try to mount it. While in the phone, I'm also unable to locate it in Windows Explorer. I can deal without having the card if need be, but if there's something I'm missing, any help would be greatly appreciated.
Second, This is the crucial one...I have a Pioneer Appradio 2 in my car. Like the above problem, every single ROM I have used before has worked flawlessly with the radio with exception to one, however, even the one that didn't work properly still worked to some degree. I just ended up having intermittent snow issues on the screen. With the phone running and connected to the radio, bluetooth works flawlessly, my connection screens come up as they always do while the phone is attempting to make a connection, but once it's connected the screen on the radio goes totally black. What's funny, is I know it's working properly with exception to the black screen, because the touch controls still work, even though nothing is showing up. I can sit with the phone in my lap, and press the screen all day long on the radio and see the apps open on my phone, they just don't display anymore on the radio. Is MHL supported in CM10.1?
I am running the following nightly "cm-10.1-20121227-NIGHTLY-d2att.zip". I am using that nightly, because the one from the 28th left no service on the phone. Any help would be greatly appreciated, as if it's not supported, I'll have to drop the ROM which is something I don't want to do, otherwise my radio is totally useless to me.
Thanks in advance!
Click to expand...
Click to collapse
Did you figure it out? Ive just installed 10.1 on my galaxy nexus and have an appradio2... Not yet bought the arliberator app as want to make a final check i t works. Have you got it working and are you using arliberator?
Thanks buddy.
for the first one: you need to reformat your sd card to fat32 instead, your current one is probably exFat which is unsupported for all CM/AOKP based Roms.
second: not sure what that is, but here's the thing, CM10.1 roms are still nightlies, they are bound to have some bugs. either go back to cm10 for stability or just stick with 10.1 and wait for fix
liquidaluminum said:
After spending all day on setting it up to my liking, and getting some additional assistance on locating the developer options, I had to say that this is officially my favorite ROM. That being said, I'm running into a couple of small issues, one I can do without, but the other I can't.
First, I have a 64gb SanDisk microSD card that I have used in my phone since I first bought it. It has always worked on every ROM I've ever used, however, now I can't get the phone to see it, no matter how many times I try to mount it. While in the phone, I'm also unable to locate it in Windows Explorer. I can deal without having the card if need be, but if there's something I'm missing, any help would be greatly appreciated.
Second, This is the crucial one...I have a Pioneer Appradio 2 in my car. Like the above problem, every single ROM I have used before has worked flawlessly with the radio with exception to one, however, even the one that didn't work properly still worked to some degree. I just ended up having intermittent snow issues on the screen. With the phone running and connected to the radio, bluetooth works flawlessly, my connection screens come up as they always do while the phone is attempting to make a connection, but once it's connected the screen on the radio goes totally black. What's funny, is I know it's working properly with exception to the black screen, because the touch controls still work, even though nothing is showing up. I can sit with the phone in my lap, and press the screen all day long on the radio and see the apps open on my phone, they just don't display anymore on the radio. Is MHL supported in CM10.1?
I am running the following nightly "cm-10.1-20121227-NIGHTLY-d2att.zip". I am using that nightly, because the one from the 28th left no service on the phone. Any help would be greatly appreciated, as if it's not supported, I'll have to drop the ROM which is something I don't want to do, otherwise my radio is totally useless to me.
Thanks in advance!
Click to expand...
Click to collapse
For one you REALLY need to update to the latest nightly.. Your build is SERIOUSLY old.. http://get.cm/?device=d2att
Come back if your problems aren't fixed after that.
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.