I can't post in in Development, yet, so I need to post here. I've also done searches on A2DP and bluetooth, but no luck, yet. I have a Blueant Q1, updated to the latest firmware. I am pretty sure the A2DP was working prior to installing the SyndicateROM, but now I can only get phone calls. Has anyone else had problems, or can anyone shed some light on what the issue might be? I just moved from the Moment, and I have high confidence in the Q1's A2DP's capabilities.
For future reference, don't post questions about anything in development. It will just get moved to q&a
Sent from my always stock, EC05 Epic 4G
I'm phrasing it as a question here, but I'm really reporting this as a potential bug. I need to get my device back to stock and check it, and verify if it is really SyndicateROM where it screws up.
Have you verified that "media audio" is enabled for that device in your epics Bluetooth settings?
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
Have you verified that "media audio" is enabled for that device in your epics Bluetooth settings?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Go to Settings-> Wireless and Network->Bluetooth Settings
Long-press the entry for your device in the device listing to get the pop-up menu.
Select Options.
Make sure "Media" (that's A2DP) is checked, and the device is connected.
Sent from my mind using telepathitalk
Thanks for the responses. I should have mentioned the things I had already tried. Among them was going to the device in Bluetooth Settings, long-clicking on it, going to options, and noting that in Profiles it says it is connected to "phone audio". I also have the Q1 bluetooth app installed. I've tried clearing the device from the phone, rebooting, etc. I have not tried going back to stock, yet, though I may.
All non-phone audio goes through the phone speakers.
On a side note, again, because I can't post this in dev, when I do 24-hour mode, the status bar pushes most of the clock off screen to the right. In 12-hour mode, the status bar clock is properly aligned/justified. This is something I set after I installed SyndicateROM, so I can't claim it wasn't like that in stock EC05. However, I haven't been able to find that issue posted, either because it is not common, or I haven't searched the right terms.
Please disregard about the clock issue. Turns out, it was right there in the SyndicateROM thread, with a "Fix 24-hour time" add-on.
feuertier said:
Please disregard about the clock issue. Turns out, it was right there in the SyndicateROM thread, with a "Fix 24-hour time" add-on.
Click to expand...
Click to collapse
Yes, yes it was.
Well, I think I confirmed that my headset doesn't work with DI18 after going back to stock. I used Odin to go back. Anything else anyone could think might need to be cleared in order to really clear the device?
Related
Does anyone know what this icon on my status bar is? It is driving me nuts that I cannot figure it out. It started appearing on my replacement EVO, even though I installed the same applications (pretty sure) as my original device.
alecwyn said:
Does anyone know what this icon on my status bar is? It is driving me nuts that I cannot figure it out. It started appearing on my replacement EVO, even though I installed the same applications (pretty sure) as my original device.
Click to expand...
Click to collapse
Are you using stock Sense? It looks like it may be a speakerphone indicator, but not sure if it should be displaying when you're not on a call...
I remember seeing a post for a fix where the ear wouldnt go away, i believe after flashing a certain rom but i cant remember what one...is that the issue it wont go away?
fchipm said:
Are you using stock Sense? It looks like it may be a speakerphone indicator, but not sure if it should be displaying when you're not on a call...
Click to expand...
Click to collapse
Yes, I am using the stock Sense. Sorry, forgot to mention that.
Cy_n_ic said:
I remember seeing a post for a fix where the ear wouldnt go away, i believe after flashing a certain rom but i cant remember what one...is that the issue it wont go away?
Click to expand...
Click to collapse
I just don't know the application that put it there. I have never seen it. I am just trying to figure it out, so I can make a decision if I want it or not.
@fchipm - didn't see last question...the icon appear at all times.
It is the hearing aid icon...You have hearing aid compatibility turned on. it makes the earpiece louder.
Setting is Menu>Settings>Call>Hearing Aids . Just uncheck it and the icon will go away
Thanks GeoTX!!
I don't know if anyone else has come across this, but it seems that I can't get Tasker to actually stay running in the background - it loads up and allows me to create profiles etc, and after clicking the green tick to apply, the Tasker notification appears (to allow it to stay running), but after a few seconds it disappears. I've tried this both with profiles in the app, and after a clean reinstall of the app with nothing setup, and have the same experience.
I'm going to email a bug report to the developer, but just wanted to see if anyone else had also had this issue, to try and figure out what the cause is.
ROM: MCR Ir4
Tasker Version: 1.1.1u2m
Don Vincenzo said:
I don't know if anyone else has come across this, but it seems that I can't get Tasker to actually stay running in the background - it loads up and allows me to create profiles etc, and after clicking the green tick to apply, the Tasker notification appears (to allow it to stay running), but after a few seconds it disappears. I've tried this both with profiles in the app, and after a clean reinstall of the app with nothing setup, and have the same experience.
I'm going to email a bug report to the developer, but just wanted to see if anyone else had also had this issue, to try and figure out what the cause is.
ROM: MCR Ir4
Tasker Version: 1.1.1u2m
Click to expand...
Click to collapse
I haven't installed Tasker on my Gnex, but it worked fine on my Nexus S with ICS.
Luxferro said:
I haven't installed Tasker on my Gnex, but it worked fine on my Nexus S with ICS.
Click to expand...
Click to collapse
Interesting - I had assumed it was an OS incompatibility, but maybe it's something else...
Tasker works for me on G Nexus
Same here....
Sent from my Galaxy Nexus using xda premium
DDM123 said:
Tasker works for me on G Nexus
Click to expand...
Click to collapse
rijin said:
Same here....
Click to expand...
Click to collapse
Could you tell me - are you both running stock ICS, or a custom ROM?
Stock Galaxy Nexus CDMA
There's a number of threads on the Google support group for Tasker re ICS issues, including notification icon disappearing. Pent's waiting on ICS for his Nexus S to look into it further.
I'm due to receive my GN tomorrow and am a *very* heavy Tasker user so will be interested to see whether I hit any issues..
Either way I have faith that Pent will sort it; he's never let us down before
the icon disappears sometimes for me but when a profile kicks in the icon comes back, so I think it does actually run. For me anyway.
Sent from my Galaxy Nexus using XDA App
Running fine for me, stock ICS, light usage (very new)
As for alsex87 I only have an icon when a profile is doing something.
Tasker work perfect in my phone.
Sent from my Galaxy Nexus using XDA App
Works fine on my GN too. Agree with other comments that it comes back when profiles change. So I'm pretty sure it's still running.
Well it's looking good so far for my setup; had to tweak tasks setting volume levels as I moved from an Atrix but everything else seems intact (including deactivating the lock screen when in 'sleep' mode). Will know for sure by the weekend.
Re: the notification icon, I have run in foreground unchecked and no icon showing. Doesn't seem to have had a negative effect so far..
It doesn't work for me. Same thing. Allows me to create a profile, but then keeps crashing.
Won't run at all for me, I was assuming it was an ICS compatibility issue. I kept waiting for an update but when I never got one, I figured I would google it. Well, I found here that it's working for most people, so I don't know what it is that's wrong.
I am a heavy Tasker user too. Just got my profiles installed. The "home" profile (wifi near) activates, then both the Tasker icon and my "home" icon disappear.
As a side question is there an easy way to copy the backup files from an old phones sd card to the Nexus? The SD card folder doesnt show up when I plug into my computer.
gotbeer said:
I am a heavy Tasker user too. Just got my profiles installed. The "home" profile (wifi near) activates, then both the Tasker icon and my "home" icon disappear.
As a side question is there an easy way to copy the backup files from an old phones sd card to the Nexus? The SD card folder doesnt show up when I plug into my computer.
Click to expand...
Click to collapse
I've seen some people leaving it in MTP mode, but I have the best luck transferring files in PTP mode. When you plug it in to a computer, select the various modes by clicking on the USB symbol in the notification tray. Just don't switch it up while moving data.
This isn't immediately pertinent, but Locale (which I'd consider the predecessor to Tasker) seems to work fine. The only problem I have is that I can't split notification volume from ring volume (I silence emails at night but leave ringer on), but that's not Locale's fault as ICS itself doesn't seem to offer the option.
CodeMonkey said:
There's a number of threads on the Google support group for Tasker re ICS issues, including notification icon disappearing. Pent's waiting on ICS for his Nexus S to look into it further.
I'm due to receive my GN tomorrow and am a *very* heavy Tasker user so will be interested to see whether I hit any issues..
Either way I have faith that Pent will sort it; he's never let us down before
Click to expand...
Click to collapse
Pent now has ICS - expect reported / found issues to be resolved with the upcoming v1.2 release of Tasker per http://groups.google.com/group/tasker/browse_thread/thread/e3a1ec4dd8e30a0a
Tasker crashes for me when I try to launch it. Running a Sensation with Android 4.0.3.
Hi there, I don't know what or how I had this happen but I suddenly have voice reading off every line in any browser I use. I have stock browser, dolphin mini, and skyfire. I'm not totally sure what caused it to start our what application. I've checked all the normal settings, accessibility, development, sounds, etc. I see nothing not set correctly. I've gone back and forth the last two days and finally i'm asking for help... Im running codename 1.3.3 with lean kernel 1.7.4 I believe. The last kernel read as stable.
Any ideas?
Thanks in advance! I'm going crazy with this...
I had this problem when using lightflow. It needs accessibility permissions. Check your settings->accessibility->talkback for lightflow.
Sent from my Galaxy Nexus using xda premium
Ok, will try that but have no idea what light flow is unless it's coupled with other software. Will post back in just a few.
Nope, didn't do it. I mean, the "talk back" option was in fact enabled once I dug into it. (how this happened I'll probably never know) Even better, it showed as "off" with no text block showing it's enabled however it most surely is the case. I have tried freezing different programs such as tapatalk pro, Google "voice" anything. I've gotten it to take a break but has returned. I think this became an issue when I flashed "lean" kernel over the codenamed android 1.3.3 already included kernel for sake of "true battery loss" minimized.
So i'm further behind then when I started as at least I thought I had the fix for the issue.
Now i'm spent... Any more thoughts anyone before I bury my head, shed a tear drop, give in to my ego and need of solving problems.....
Boot back into recovery and restore a nandroid backup...
I guess for as many I've made and never used vs the few times I skipped it and caused my self tons of extra work...
Me - 0
Android galaxy nexus - +1
Mmmmm This is a problem I have experienced also. See my thread here
http://forum.xda-developers.com/showthread.php?t=1388205
I eventually worked out as the guy above said, it was lightflow. I uninstalled it.
If you don't know what it is then i guess you don't have it on your phone.
Have a look through my thread see if there is ought in there that might help.
Also have a look at this other thread i started on another forum.
http://android.modaco.com/topic/349660-nexus-talking-to-me/page__p__1864309#entry1864309
Hope something helps.
Johnboy
In Settings>Accessibility, change Install Web Scripts to Not Allowed. Your problem will be solved.
It seems like we are almost close to see the public ICS version. FC07 is also one of the best ROM that we've seen so far and many issues from the previous version are already fixed on FC07.
But, I still see many peoples are complaining about the issues on FC07 from here and there. So, it would be great if we can see all real or possible issues in one place. This is the reason why I'm starting this thread.
Because I started, I want to add one :
Occasionally, GPS lock notification is not disappeared even the GPS turned off and there's no app using it.
Story - After flashing FC07 from FC06, I was checking individual apps and opened Go Weather app. Go Weather app asked be to enable My Location, so I did. Go Weather asked me 'GPS module is diabled. do you want to go to GPS settings?', so I turned on GPS and came back to Go Weather. It started searching and locked the GPS. After that, GPS notification always showed even I closed the App.
Just like happened in FC06, after the reboot, I do not see the same problem any more. Fortunately, I kept the screenshot of it.
[Update]
Now my FC07 ROM works much better than any of previous ROMs - sreenshots available in this post and post #50.
First, how stupid I was!
Late last night, I disabled the Battery saver script - Juice defender - and after that my Stock (rooted) FC07 ROM started working flawlessly. Even the battery life is showing great. After unplugged, it only used 10% for two hours.
Only one problem that I saw was GPS lock notification. It was there even I turned off everything. As we mentioned many times, only the workaround for this is just rebooting the phone.
Since last night, I do not see any apps FC'd. GPS working great, my wifi status is always updated even after the sleep.
So, if you see some weird issue on your ICS Rom, make sure you test your phone with any battery saver application. What I did during last night was, disabled Juice Defender and disabled some startups which I really don't need. One more thing I did was, configured CPU thru System Tuner Pro to use the ondemand govener. That's it and I'm happy with this FC07 ROM.
(Before this change, I also made the GPS tuneup on post #47, it's still effective on my phone and working great)
Right now, my phone stays cool without any issues.
(ps I updated Google map in this morning. I think this updated app is much better than previous version)
[Update]
I hope this would be the last update before I jump into coming FC13.
This afternoon, after a sleep mode, wifi did not show the signal bar again. But at this time, just turning off and on worked. Wifi signal came back to normal (don't need to reboot).
* Adding two more screenshots showing excellent battery life on FC07*
Exchange doesn't sync contacts or calendar.
Wifi is slow to lock
Sent from my SPH-D710 using Tapatalk
jamesey said:
Exchange doesn't sync contacts or calendar.
Wifi is slow to lock
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
THIS!!
Thanks for saving me the trouble of flashing this rom only to be disappointed.
DevalB said:
THIS!!
Thanks for saving me the trouble of flashing this rom only to be disappointed.
Click to expand...
Click to collapse
You can easily change the apks for exchange. In fact I posted them. Just stating what needs to be fixed
Sent from my SPH-D710 using Tapatalk
The gps disconnects frequently. It does connect fast but cannot hold a signal and when it does lose signal you have to reset the phone to be able to reconnect again. Also they have not fixed the issues with the media scanner. It still messes up the camera app a work around to open a 3rd party camera app and restart the phone this fixes this issue.
---------- Post added at 04:02 AM ---------- Previous post was at 04:00 AM ----------
kobridge said:
It seems like we are almost close to see the public ICS version. FC07 is also one of the best ROM that we've seen so far and many issues from the previous version are already fixed on FC07.
But, I still see many peoples are complaining about the issues on FC07 from here and there. So, it would be great if we can see all real or possible issues in one place. This is the reason why I'm starting this thread.
Because I started, I want to add one :
Occasionally, GPS lock notification is not disappeared even the GPS turned off and there's no app using it.
Story - After flashing FC07 from FC06, I was checking individual apps and opened Go Weather app. Go Weather app asked be to enable My Location, so I did. Go Weather asked me 'GPS module is diabled. do you want to go to GPS settings?', so I turned on GPS and came back to Go Weather. It started searching and locked the GPS. After that, GPS notification always showed even I closed the App.
Just like happened in FC06, after the reboot, I do not see the same problem any more. Fortunately, I kept the screenshot of it.
Click to expand...
Click to collapse
The gps lock notification does disappear with the EL29 modem. So maybe the problem is with the modem and not the Rom. Also Copilot 9 works with the EL29 modem and this Rom with no problems because the gps lock notification disappears when it is not in use.
jamice4u said:
The gps disconnects frequently. It does connect fast but cannot hold a signal and when it does lose signal you have to reset the phone to be able to reconnect again. Also they have not fixed the issues with the media scanner. It still messes up the camera app a work around to open a 3rd party camera app and restart the phone this fixes this issue.
---------- Post added at 04:02 AM ---------- Previous post was at 04:00 AM ----------
The gps lock notification does disappear with the EL29 modem. So maybe the problem is with the modem and not the Rom.
Click to expand...
Click to collapse
Had GPS on for awhile when I ran FC07 (with the modem) never had the icon stay when I turned it off it went away like it should. Some people are having the issue however so not really sure it's with the modem.
I agree with GPS sticking around even after closing sometimes, which drains battery and warms the phone.
Other then GPS issues this has been a solid phone made better with the ICS roms
Thanks for starting this thread since I believe Samsung is monitoring this forum.
Double post
No system wide font size from what I hear. Can we call that an "issue"? =P
Has anyone gone in and taken a look at the build.prop "settings" for wifi?
Sometimes it happens that the wifi.suppplicant_scan_interval on roms based on these stock leaks we get is set as high as like 240..THAT is one thing that could definitely be lowered to like 90, and the lock would be much faster...
(I can't check it myself right now, because my ET4G is in transit due to a hard-brick replacement.)
It's definitely something someone might wanna take a look at.)
yourbrotherrex said:
Has anyone gone in and taken a look at the build.prop "settings" for wifi?
Sometimes it happens that the wifi.suppplicant_scan_interval on roms based on these stock leaks we get is set as high as like 240..THAT is one thing that could definitely be lowered to like 90, and the lock would be much faster...
(I can't check it myself right now, because my ET4G is in transit due to a hard-brick replacement.)
It's definitely something someone might wanna take a look at.)
Click to expand...
Click to collapse
Mine shows 15 and I never touched this option. So, I believe it would be the stock default.
For me, the main thing that has been fixed is stability...but then again the leaks are coming way to fast to truly test stability (aka running for over a week). My two biggest gripes with the ics leaked roms hasn't been fixed since the early leaks...notification sounds sometimes still disappearing, and the gps bug still exists (albeit less frequently).
kobridge said:
Mine shows 15 and I never touched this option. So, I believe it would be the stock default.
Click to expand...
Click to collapse
15?
I can't say I've ever seen that value placed so low in ANY rom on any phone....90 is usually the go-to 'custom' setting most "chefs" will use...15 doesn't seem like it would give the wifi even enough time to establish a connection before it went in to re-scan mode.
Hm.
yourbrotherrex said:
15?
I can't say I've ever seen that value placed so low in ANY rom on any phone....90 is usually the go-to 'custom' setting most "chefs" will use...15 doesn't seem like it would give the wifi even enough time to establish a connection before it went in to re-scan mode.
Hm.
Click to expand...
Click to collapse
It seems like '15' is not a strange value.
Found the same value from many places -
http://forum.xda-developers.com/showthread.php?t=1351003&page=2
http://forum.cyanogenmod.com/topic/34675-wifi-scan-interval/
http://adrynalyne-teachtofish.blogspot.com/2011/11/how-to-change-wifi-scan-interval.html
To save the battery, I see many places are recommending '90' but anyway, FC07's stock value is '15'.
15 is the same on the GB rooms too.
kobridge said:
It seems like '15' is not a strange value.
Found the same value from many places -
http://forum.xda-developers.com/showthread.php?t=1351003&page=2
http://forum.cyanogenmod.com/topic/34675-wifi-scan-interval/
http://adrynalyne-teachtofish.blogspot.com/2011/11/how-to-change-wifi-scan-interval.html
To save the battery, I see many places are recommending '90' but anyway, FC07's stock value is '15'.
Click to expand...
Click to collapse
OK. My bad....thanks for checking... Must be something else.
Don't expect GPS fix.
Samsung engineers can't write GPS drivers to save their own lives. Pretty much every Samsung phone have had serious GPS issues.
HTC GPS = Godmode. Samsung GPS = Failmode.
jerryparid said:
Don't expect GPS fix.
Samsung engineers can't write GPS drivers to save their own lives. Pretty much every Samsung phone have had serious GPS issues.
HTC GPS = Godmode. Samsung GPS = Failmode.
Click to expand...
Click to collapse
LOL. Mine literally just got a lock on me (and on the correct side of the house) in about 4 seconds.
Well, most of this thread has been about GPS, but I'll throw my hat into the ring with something different.
I still can't get Bluetooth to pair with my Sony car stereo, and while I can pair with my Infinity car system, trying to play any audio causes Bluetooth to force close. It works fine in both cars on the GB ROM so this is certainly a ICS build issue. Although not necessarily only on FC07. It hasn't worked on any of the builds.
Sent from my E4GT via Tapatalk
Dchibro said:
Well, most of this thread has been about GPS, but I'll throw my hat into the ring with something different.
I still can't get Bluetooth to pair with my Sony car stereo, and while I can pair with my Infinity car system, trying to play any audio causes Bluetooth to force close. It works fine in both cars on the GB ROM so this is certainly a ICS build issue. Although not necessarily only on FC07. It hasn't worked on any of the builds.
Sent from my E4GT via Tapatalk
Click to expand...
Click to collapse
I am glad you are checking the Bluetooth car connectivity. I am checking the leaks with my stereo headphones and my regular Bluetooth but that's good you caught that car connection issue. It seems like there aren't many people checking the Bluetooth side of these leaks
Sent from my SPH-D710 using xda premium
I'm currently running Re-Calked.E4GT.0.2.1.FI25. For the most part everything is solid, and getting some of the best battery life I've ever gotten out of the phone (24 hrs with ~2hrs screen time no problem if in a good signal area).
The one little problem I'm having is any time I finish a call using my in-car bluetooth device, the screen blacks out for a while then I get a message saying Com.android.phone has stopped.
The device is still connected to bluetooth (music starts streaming again, etc...), but if I try to make another call, the dialer won't enable bluetooth (a lot of weirdness about finding a bluetooth device when you tap the bluetooth button on the dialer UI). A hot-boot puts everything back again the way it should be until my next call. This happens 100% of the time on bluetooth, never on a regular call - speaker or otherwise.
I don't think it's Re-Calked's fault, I've experienced the same problem on the stock ROM (FH25). It was fine on FH13, and I'm fairly certain FI03 was good too, but I got dismal battery performance on these kernels.
Any suggestions? This is a real downer for me ... I'd hate to have to try an older ROM since everything else is effin' fantastic! (BIG thanks tdunham!!)
UPDATE:
If anyone else runs into this problem, flash the FF18 Phone from THIS POST (thanks tdundham)
The problem appears to be related to the phone being in landscape orientation, which is only available during a call when docked in a car dock.
I'm using the Official Samsung Vehicle Mount
Wish I had an answer for this for you but...
I've seen several frustrated posts concerning Bluetooth pairing with vehicles on ICS with no clear workaround/solution. I don't have a vehicle with onboard Bluetooth to troubleshoot the issue. I bet it's a doable fix too if it's just a matter of porting over some older library files or something from FI03. Maybe we can experiment with some file replacements to see if we can get it working.
You listen to music over Bluetooth too? I wonder if the media player is conflicting too somehow. What happens if you don't have streaming music and recieve a call?
Edit: It would help if you could backup and flash back to FI03 to verify if the problem still exists on that version.
tdunham said:
Wish I had an answer for this for you but...
I've seen several frustrated posts concerning Bluetooth pairing with vehicles on ICS with no clear workaround/solution. I don't have a vehicle with onboard Bluetooth to troubleshoot the issue. I bet it's a doable fix too if it's just a matter of porting over some older library files or something from FI03. Maybe we can experiment with some file replacements to see if we can get it working.
You listen to music over Bluetooth too? I wonder if the media player is conflicting too somehow. What happens if you don't have streaming music and recieve a call?
Click to expand...
Click to collapse
Actually it's not a built-in bluetooth. It's a "Belkin Bluetooth Car Hands-Free Kit for Apple iPod, Apple iPhone, BlackBerry,and Android Smartphones, US Version" ... search for that on Amazon ... tried to post a link, but I'm too much of a noob to post links yet, apparently.
I have the phone in a Samsung windshield mount, and the Belkin device ports all audio through the aux-in jack of my car stereo. It also has a built-in microphone so that I can use it for calls.
I have experimented a bit to see if it was a conflicting app, but it still happens even if I'm using nothing else. Worked fine on the older kernels, even with multiple apps running (Car Home Ultra, Waze, and Play Music are typical) went wonky as of FI25. I even tried disconnecting it from the dock and disabling car mode. The only thing that causes it is being connected to bluetooth and ending a call, and then it happens every time. Doesn't matter if I initiate the call or receive it. (Which is useful, because I could easily test by calling 611)
I wish I had another Bluetooth device to test if it was specific to the Belkin ... but that's all I've got.
No problem. I live out of Waze. Glad I found the fix for the full navigation voice cutoff for that (and Google Voice) and included it in the FI25 rom. I'll look into posting a couple of flashable zips for you to experiment with for the Bluetooth library files.
tdunham said:
No problem. I live out of Waze. Glad I found the fix for the full navigation voice cutoff for that (and Google Voice) and included it in the FI25 rom. I'll look into posting a couple of flashable zips for you to experiment with for the Bluetooth library files.
Click to expand...
Click to collapse
Thanks for that ... can't wait to try. Going to flash your new Re-Calked update soon too.
On a tangent regarding Waze ... did you install the latest update? I can't stand the way they use 30% of the screen with that black bar ... even worse when you get close to your destination and that other menu bar pops in above it. 50% of the screen covered with useless info.
I rolled back to the prior version from my Titanium backup.
I only used Waze this morning once after the update but didn't really check it out.
Backup your phone.
Flash this first - FI03.flash.first.zip
Test bluetooth, if it isn't working move on...
Flash this second - FI03.stock.lib.zip
Test bluetooth. Even if it is working, flash this next. FI03.stock.lib.zip
Very cool. I'll give it a shoot tomorrow at lunch if I get a moment.
Sent from my SPH-D710 using xda app-developers app
romgnascher said:
Very cool. I'll give it a shoot tomorrow at lunch if I get a moment.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yeah, don't forget to backup first.
Sent from my SPH-D710 using xda premium
So, it looks like I was wrong with my initial investigation.
I did flash the first file ... everything connected fine. Placed and disconnected a call no crash. But what I DIDN'T do was put the phone in the car dock.
So, I think the problem isn't bluetooth at all. I think it's some interaction with the car dock. If the phone is connected to the car dock when I disconnect the call ... that's when com.android.phone crashes (I can start the call connected, just need to disconnect before I end the call). I also had a suspicion that Car Home Ultra might have been a factor, but it happens even if Car Home Ultra is not running. I thought I had tested this scenario originally, but I guess I missed that one.
I'll flash back to my nandroid later and reconfirm these results. In the mean time ... any thoughts on what the car dock might be doing to trip up the phone?
UPDATE:
Now that I've narrowed it down to the dock, I found this bug report that appears to be related to my issue (yay, I'm not the only one):
http://code.google.com/p/android/issues/detail?id=34612
Down the end of that thread, it appears that the issue seems to be related to the phone being in portrait mode ... not necesserily the dock, it's just that you can only get portrait mode during a call when docked.
Just curious. Does your dialer rotate when docked so you can make a call?
Anyway, I sent you something in a PM check it out.
Edit: I'm working on one more thing to add to that. Give me a little while.
Cool, I'll look at it afterI get the kids to bed.
Yes, the dialer rotates in the dock. Also, when in a call, the contact's photo is also rotated and moved left.
Sent from my SPH-D710 using xda app-developers app
Ok we're running out of choices I guess. Try this older stock dialer and if that doesn't work, I guess that's it for now.
Thanks for your efforts whatever the outcome!
I'll flash this tomorrow and see how we go.
I just flashed the new Re-Calked update by the way. No problems, good stuff and it's been idling at around 1.6%/hr.
Changing out the phone did the trick!
OP updated with resolution.
Sent from my SPH-D710 using xda app-developers app
Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.
tdunham said:
Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.
Click to expand...
Click to collapse
Cool, I'll look at this one too. Have an answer for you by lunch time.
tdunham said:
Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.
Click to expand...
Click to collapse
So I tried that phone. Crashes on disconnect just like the others. Back to the FF18 phone and it works like it should.
romgnascher said:
So I tried that phone. Crashes on disconnect just like the others. Back to the FF18 phone and it works like it should.
Click to expand...
Click to collapse
That's fine, as long as we got it working for you.