Develop Bugs

[Q] [AUDIO BUG] Help me xda developers... You're my only hope.

Get it? The title is a Star Wars reference. As in developers are Jedi? Like in the movie? Nevermind.
I have been having a strange audio bug recently. I flashed RC Mix Runny v1.0 through to v1.4 and each subsequent ROM version did exactly what it should. No issues that weren't listed on the thread.
Then I flashed Runny v1.5, followed by (after the ROM had booted twice) a theme I made on UOT Kitchen. A few days afterwards, when making a phone call, I couldn't hear the phone ringing through the phone's speaker. Nothing. That's the bug.
This only applies to phone calls (or at least the speaker normally used for phone calls). When I select 'speaker phone' the rear speaker kicks in and I can hear the phone call just fine, though a little loud when walking around in public.
The headset also works perfectly.
I flashed RCMix3d 3.5 v1.0 today - no themes this time in case it was the cause last time. The ROM boots up just fine, everything seems perfect but when I go to make a phone call the same bug presents itself. Meaning it's most likely a bug I have caused, not a bug in a ROM.
But what did I do?! Has anyone heard of this behavior before? Could it be radio/RIL related?
If anyone can shed a little light, I would appreciate it greatly.

Max-E-Moose said:
Get it? The title is a Star Wars reference. As in developers are Jedi? Like in the movie? Nevermind.
I have been having a strange audio bug recently. I flashed RC Mix Runny v1.0 through to v1.4 and each subsequent ROM version did exactly what it should. No issues that weren't listed on the thread.
Then I flashed Runny v1.5, followed by (after the ROM had booted twice) a theme I made on UOT Kitchen. A few days afterwards, when making a phone call, I couldn't hear the phone ringing through the phone's speaker. Nothing. That's the bug.
This only applies to phone calls (or at least the speaker normally used for phone calls). When I select 'speaker phone' the rear speaker kicks in and I can hear the phone call just fine, though a little loud when walking around in public.
The headset also works perfectly.
I flashed RCMix3d 3.5 v1.0 today - no themes this time in case it was the cause last time. The ROM boots up just fine, everything seems perfect but when I go to make a phone call the same bug presents itself. Meaning it's most likely a bug I have caused, not a bug in a ROM.
But what did I do?! Has anyone heard of this behavior before? Could it be radio/RIL related?
If anyone can shed a little light, I would appreciate it greatly.
Click to expand...
Click to collapse
Please search before opening a new post as I have seen this pop up alot the past few days with that rom. I would look in the roms thread

I will search more thoroughly. Apologies for any infraction.
Cheers for pointing the way.

Max-E-Moose said:
I will search more thoroughly. Apologies for any infraction.
Cheers for pointing the way.
Click to expand...
Click to collapse
While you are searching for hours for a solution, download a different ROM (other than RCMix) and find out if it is really a bug or some hardware issue. And while you wait for the download and flash, keep searching

hohinder said:
While you are searching for hours for a solution, download a different ROM (other than RCMix) and find out if it is really a bug or some hardware issue. And while you wait for the download and flash, keep searching
Click to expand...
Click to collapse
Thanks for your advice. I heeded it!
I flashed Black Ice [AOSP] to see if it was still persisting. It is.
Seems like it's a hardware problem. I was hoping it wasn't. I didn't want to have to pay to fix it!
Ta for the help!

try changing the radio or kernel see if it helps

SOLVED
NOT SOLVED
rakinisbat said:
try changing the radio or kernel see if it helps
Click to expand...
Click to collapse
I was holding back on changing the radio because I don't like higher risk of bricking. Having done it in the past though, I said it was worth a shot before I blame the hardware entirely and hand over money to fix it.
I had been using radio 26.09.04.11 and it's matching RIL with every ROM I tried.
Once changed to radio 26.13.04.19_M and it's corresponding RIL and the problem was erased. I can hear phone calls on the phone speaker again. (Like normal folk!)
Thanks for the push rakinisbat, I needed it!
Edit: NOT SOLVED. The problem has re-surfaced. I have made absolutely no changes to the system since it started working. I am now going to pay someone to take a look and will report back with results.

Definitely not solved.
This problem with the receiver not working has not gone away.
I have tried ignoring it for the last while and just using the speakerphone on a low volume - not ideal but workable.
A few days ago I changed ROM - curious to try out ICS. I load up the new ROM and a while later, accidentally forgot to put a call I was making onto speakerphone and suddenly the receiver is working again - JOY!
Now, two days later, the receiver is not working again.
I have pry tools now and would happily change the receiver, but this recurring trend of it working for a spell after a new ROM is flashed leads me to believe this is more software related than hardware.
If anyone has ANY ideas or thinks they could help (if I provide a logcat to them or something) then please PM me or respond to this thread.

Everything works fine for me...never experienced this .....check your audio settings....and why you running such an old version??
Sent from my Desire HD using xda premium

harshrocsu;20112881why you running such an old version??[/QUOTE said:
The last time I changed to that radio, my audio bug was fixed (temporarily).
I will update to the new radio (12.65.60.29_26.14.04.28) I saw mentioned a few days ago and see if it changes anything - though I doubt it.
I have done a fair bit of research on this and it is not as uncommon as I thought it was a few months ago. It seems to have happened to the HTC Desire, Desire S and Desire HD - but not en mass. In every case, the phone was working fine, then came intermittent receiver audio, then receiver audio gone altogether.
I have not heard of one working solution, though I have had some helpful people lend an ear!
Click to expand...
Click to collapse

You say the problem is solved for a while when you flash a new ROM. Is there a possibility that a certain app that you install/restore that maybe messes with the speaker?
Just a thought..

if4ct0r said:
You say the problem is solved for a while when you flash a new ROM. Is there a possibility that a certain app that you install/restore that maybe messes with the speaker?
Just a thought..
Click to expand...
Click to collapse
An avenue I had not gone down. I have been restoring mostly the same apps for ages.
Thanks for the idea. I will do a backup and then a fresh install tomorrow (I'm at work) and check. Will report back afterwards.

Ongoing audio issue
I have fully wiped the phone and re-installed a ROM twice now (ICS both times, I know this problem acts the same with GB). I didn't install any apps for a while and had audio in the receiver for phone calls.
The first time I wiped it, I had audio back so decided to install apps from the market - one at a time and test the receiver by ringing the house number after each is installed. I got distracted (it was late) and when I next picked up the phone, audio was gone.
Second attempt, this time stay vigilant. I fully wiped the phone, installed a ROM, and got to work on installing the apps again. I installed a few apps, which I will list here, and audio disappears again.
Installed apps:-
Dictionary.com
Dropbox
Earth
Es File Explorer
Facebook
Goggles (I dunno why, the camera isn't even working - habit maybe)
Google Sky Map
Google+
Messenger
Moon+ Reader Pro
MX Video Player
Streetview For Google Maps
Sugarsync
Tumblr
Twitter
XDA
To my knowledge, apart from MX Video Player, none of the rest these apps should have any effect on the audio.
Today I am going to wipe it and not install any apps for the next 24-48 hours and see if the audio still disappears.
Tune in next time to see if the problem makes my brain crack in two.

Max-E-Moose said:
I have fully wiped the phone and re-installed a ROM twice now (ICS both times, I know this problem acts the same with GB). I didn't install any apps for a while and had audio in the receiver for phone calls.
The first time I wiped it, I had audio back so decided to install apps from the market - one at a time and test the receiver by ringing the house number after each is installed. I got distracted (it was late) and when I next picked up the phone, audio was gone.
Second attempt, this time stay vigilant. I fully wiped the phone, installed a ROM, and got to work on installing the apps again. I installed a few apps, which I will list here, and audio disappears again.
Installed apps:-
Dictionary.com
Dropbox
Earth
Es File Explorer
Facebook
Goggles (I dunno why, the camera isn't even working - habit maybe)
Google Sky Map
Google+
Messenger
Moon+ Reader Pro
MX Video Player
Streetview For Google Maps
Sugarsync
Tumblr
Twitter
XDA
To my knowledge, apart from MX Video Player, none of the rest these apps should have any effect on the audio.
Today I am going to wipe it and not install any apps for the next 24-48 hours and see if the audio still disappears.
Tune in next time to see if the problem makes my brain crack in two.
Click to expand...
Click to collapse
I had exactly the same issue. After rooting my desire HD I installed ARHD 6.3.1 and it was working very fine until I installed the ICE HD theme for ARHD 6.3.1. Sorry, no disrespect to the theme author but I was not able to hear anything through Phone speakers after installing this theme. This is what I did to solve this issue,
1- Use Superwipe to clear everything using ClockworkMod recovery.
2- Install the STOCK 1.32 PD98IMG.zip from here. Put it in your SD card, Flash is using the HTC Stock Recovery (It will detect it automatically). Remember that the Kernel and Radio are inside this ZIP file so you need not to install anything else.
That's it. you are back to old stock ROM and now you must be able to hear you phone speakers. If not, switch off your phone for few hours and then turn on. (I know switching off and on sounds silly but it worked for me). You can install any custom ROM after that rooting again.

kaydee7902 said:
I had exactly the same issue. After rooting my desire HD I installed ARHD 6.3.1 and it was working very fine until I installed the ICE HD theme for ARHD 6.3.1. Sorry, no disrespect to the theme author but I was not able to hear anything through Phone speakers after installing this theme. This is what I did to solve this issue,
1- Use Superwipe to clear everything using ClockworkMod recovery.
2- Install the STOCK 1.32 PD98IMG.zip from here. Put it in your SD card, Flash is using the HTC Stock Recovery (It will detect it automatically). Remember that the Kernel and Radio are inside this ZIP file so you need not to install anything else.
That's it. you are back to old stock ROM and now you must be able to hear you phone speakers. If not, switch off your phone for few hours and then turn on. (I know switching off and on sounds silly but it worked for me). You can install any custom ROM after that rooting again.
Click to expand...
Click to collapse
Thanks so much for getting on to me, I have been hoping that someone out there solved this issue and might read this little thread!
I will be following your advice today and will report back.

Solution seems good so far!
I'm not going to jump the gun again and say that it is definitely solved but my audio came back!
I did what you said, reverted everything back to stock. When it loaded up Froyo and for the first while, the receiver wasn't working. I set about rooting, Radio S-Off, ENG S-Off, adding CWM etc.
About three hours later (I didn't actually leave the phone off, I reset it a lot though) the audio returned to the receiver!
I'm delighted but remain skeptical as it has come back to life and then died again so many times before.
I want to believe!!!... So I remain hopeful. Time will tell.

It fixed itself...(!)
See post below

Absolutely positively finally fixed.
Thanks to everyone for their help in trying to solve this issue.
I replaced the broken receiver with a new one I got from eBay (along with prytools for under €10) and this issue is completely fixed.
What had happened, if anyone is interested, was that the inside of receiver housing and the output on the receiver itself had been clogged with dust, tiny hairs and the like. That must have shorted the tiny thing.
Lesson learned. Get stuck in.

[Q] Bluetooth A2DP audio occasionally drops out for a second on custom ROMs

Hello all,
I have a very odd problem that I'm hoping others may have run into and solved. When I'm playing audio over the A2DP data path to my car, the audio randomly will drop for half a second, then gradually comes back to full volume over perhaps a second of time. Speaking like a programmer, it's almost like something mutes the audio and then slides the volume up in a loop or something.
This problem did not occur on Bombaridier and the older Synergy Kernel, however it is happening with the newer kernel on Juggernaut v5, Paradox and SlickMOD, leading me to believe something in the kernel or newer system binaries might be causing it. This behavior happens in Pandora, Amazon MP3 and also the stock Music app.
Thinking that maybe a stray notification was the problem, I've tried disabling notifications in all of the apps I know of that notify, I've also tried switching the phone into vibrate and finally into full-silent, but it does not seem to affect the behavior. I have found no likely cause. I wish I was able to log alsa changes; maybe a script running constantly with something like:
Code:
while (true)
do cat /proc/alsa/some_alsa_status_entry >> /tmp/alsalog
sleep 1
done
Does anyone else have any ideas as to what this might be? It's really annoying!
Thanks in advance,
Pete

Dirty Pete said:
Hello all,
I have a very odd problem that I'm hoping others may have run into and solved. When I'm playing audio over the A2DP data path to my car, the audio randomly will drop for half a second, then gradually comes back to full volume over perhaps a second of time. Speaking like a programmer, it's almost like something mutes the audio and then slides the volume up in a loop or something.
This problem did not occur on Bombaridier and the older Synergy Kernel, however it is happening with the newer kernel on Juggernaut v5, Paradox and SlickMOD, leading me to believe something in the kernel or newer system binaries might be causing it. This behavior happens in Pandora, Amazon MP3 and also the stock Music app.
Thinking that maybe a stray notification was the problem, I've tried disabling notifications in all of the apps I know of that notify, I've also tried switching the phone into vibrate and finally into full-silent, but it does not seem to affect the behavior. I have found no likely cause. I wish I was able to log alsa changes; maybe a script running constantly with something like:
Code:
while (true)
do cat /proc/alsa/some_alsa_status_entry >> /tmp/alsalog
sleep 1
done
Does anyone else have any ideas as to what this might be? It's really annoying!
Thanks in advance,
Pete
Click to expand...
Click to collapse
I second this as an issue that I have run across quite often. I use this BT for music in my car on a daily basis. I usually get a .5 second audio drop out at lest twice each song. Seems to be about every 2 minutes if I would have to guess.
I have just learned to get used to it but it would be fantastic if this could be resolved.

I've also tried fiddling with the CPU governor ant the IO scheduler, but to no avail. Im wondering if there is a bug in the bluetooth module introduced in the latest kernel.
Sent from my SGH-T989 using xda premium

Works great for me and I've tried just about every rom and kernel over clocked and under clocked. I had it skip once before, I rebooted and it was fine.
Sent from my SGH-T989 using Tapatalk

I'll give this a bump, because I have the exact same problem. Never had this problem on my Blackberry (sad), in the same car. OP has described the issue better than I could have.

scotty-dont said:
I'll give this a bump, because I have the exact same problem. Never had this problem on my Blackberry (sad), in the same car. OP has described the issue better than I could have.
Click to expand...
Click to collapse
Thanks for posting, out of curiosity, what ROM and kernel are you running? Maybe we can find some sort of similarities...
My phone's currently running SlickMOD 3.1 with kernel "2.6.35.14"
-Pete

I've tried black edition and warfare, never had any issues

tomasitoc said:
I've tried black edition and warfare, never had any issues
Click to expand...
Click to collapse
What version of the kernel on your warfare mod? SlickMOD uses the Darkside 2.6.35.14 kernel.

Dirty Pete said:
Thanks for posting, out of curiosity, what ROM and kernel are you running? Maybe we can find some sort of similarities...
My phone's currently running SlickMOD 3.1 with kernel "2.6.35.14"
-Pete
Click to expand...
Click to collapse
Hi Pete,
I've noticed it on Digital Warfare 2.5.1 and BeastMOD 5.0 ("Test 13"), using TDJ's personal kernel and the same 2.6.35.14 above, respectively.
I'll post to Melvin on rootzwiki in the hopes that he can investigate maybe.
It might be better to bring this up in other sections as well. I came across this post by accident while researching extended batteries.

scotty-dont said:
It might be better to bring this up in other sections as well. I came across this post by accident while researching extended batteries.
Click to expand...
Click to collapse
I originally posted it in a different forum, but a moderator kicked it over here. It's not really an accessories question as I'm pretty sure it's a kernel bug, but I wasn't about to argue with site moderators on a forum like this where I'm definitely the new kid on the block.
That being said, if you have some other suggestions as to where we can ask about this, I'm all ears and would be more than willing to help debug/diagnose. I've been a Linux user since '96, so I'm unafraid of poking around in the kernel's guts to get answers.
Pete

Yeah that's the problem with this place... and why I have less than 10 posts.
On second thought, I'm tempted to just wait. It sounds like we will have a proper ICS rom and true kernel on about April 25th, to coincide with the launch of the HTC One S on T-Mobile. I can't find the threads. Hopefully then it will be an issue of the past.
I'm glad I'm not the only one though.

Just a thought....I don’t think this has anything to do with CPU performance
Hi, I have a Galaxy 2s with this exact problem but I wonder if I might offer a suggestion as to what could potentially be the cause. I have no idea how to fix it but I’m hoping that what I share here might help someone who knows more about the way these things work to be able to solve the problem.
I have spent much of my career working in Broadcast Radio, the problem I have heard my phone have with audio dropouts followed by either a ramp up of volume back to the previous level OR an audio dropouts followed by a momentary slight speed shift in the audio playback (sounds a bit like an old cassette recorded when the batteries are starting to fail) many people would probably not notice the later problem because it is very subtle and you have to know what you’re listening for.
Anyway, I believe this could be caused because of a lack of word clock sync between the phone and the bluetooth receiver. I say this because there have been times when I have had digital audio devices such as CD players that are connected to an audio console or digital amplifier and with both devices free running in terms of their clock synchronisation exhibit almost exactly the same symptoms.
You see all digital audio devices require that the audio data be put into frames much the same as regular Ethernet data is transmitted around a network is put into frames, however in order for the audio to be at the correct pitch and speed generally speaking both the playback device (Phone) and the receiving device (Bluetooth receiver) need to have the same word clock, otherwise you end up with the two devices running freely and the audio frames wont by in sync.
Depending on the Error correction implemented (sample rate conversion) on the receiver you can get really odd audio results. I think that this is what is causing this problem. Basically the Bluetooth receiver and the phone aren’t in sync so every few minutes you get a drop out.
It doesn’t seem to happen when you are talking on the phone which makes me think that when you have a call connection as this is bi-directional, the phone is probably synchronised to the Bluetooth device word clock. But when you are listing to music the connection is mono-directional so there is no sync.
Anyway just a thought. Maybe someone out there who understands the way these units synchronise can figure out a fix.

Mine has random just disconnects from the phone altogether. I have Jawbone Era, Voyager Pro Plus, and a Jabra Wave + and all will just randomly disconnect and have a hard time connecting back to phone audio. It will reconnect to media pretty much first time but won't show coonected to phone audio for some reason unleass I turn off BT, turn off headset, and sometimes even re-boot phone.

I am sure you guys have ruled this out, but this was a common problem with bluetooth audio on android. I haven't had the problem for a long time, but I used to have to disable wifi during my commute due to this dropout. Can you turn off wifi and see if the issue still happens? I was able to identify it by changing the time between wifi scan. If you had custom rom settings you could push it out and sure enough, my bluetooth dropouts happened on the same schedule (2s, 10s, more)
Just a thought.

I had this issue when I tried out juggernaut, so I went right back to Bombardier with Synergy kernel. Anyone have this on any if the ICS roms?
Sent from my beastly Galaxy S 2.

Shane_pcs said:
I am sure you guys have ruled this out, but this was a common problem with bluetooth audio on android. I haven't had the problem for a long time, but I used to have to disable wifi during my commute due to this dropout. Can you turn off wifi and see if the issue still happens? I was able to identify it by changing the time between wifi scan. If you had custom rom settings you could push it out and sure enough, my bluetooth dropouts happened on the same schedule (2s, 10s, more)
Just a thought.
Click to expand...
Click to collapse
I disable my wifi while I'm in the car, so this wasn't my issue. Thanks for the suggestion though!

I used to have occasional a2dp problems, however I have not had them since I started using various ICS releasese. The problems I would occasionally have would be a total loss of bluetooth till I rebooted the phone.
Since using Infamous I haven't had the problem other then for some odd reason occasionally having to reenter the PIN #
I'm using a Scoche Bluefusion in my car.

It had to be the fuse.
Sent from my SGH-T959 using xda premium

After upgrading to DARKSIDE's latest ICS rom, this problem has not recurred. I'm assuming that my early thought was correct in that it was some kind of kernel bug.

Dirty Pete said:
After upgrading to DARKSIDE's latest ICS rom, this problem has not recurred. I'm assuming that my early thought was correct in that it was some kind of kernel bug.
Click to expand...
Click to collapse
With Darkside and the stock ROM I have not only this problem, but crackly/staticy audio and my phone and car won't communicate once I've shut the car off. I have to completely re-pair the phone. They're bugs in 4.0.3, which Samsung dumped off on us.
4.0.4 via CM9 already doesn't exhibit the connection issue (I have to turn Bluetooth on and then off though) but I'm not sure about the others yet.

[Q] FI25 Com.android.phone has stopped - [RESOLVED]

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.

Root or stay stock?

I still haven't rooted my note 2. I want to root and get custom roms but scared the roms might not have good battery like stock. I'm not sure what's you guys opinion?
Sent from my SGH-T889V using xda app-developers app

Everything gets better with custom roms
Sent from my SGH-T889 using xda app-developers app

Stock.
Sent from my SGH-T889 using Tapatalk 2

I have rooted every Android I ever owned including ny Note 2... This is the only phone I have unrooted and went back to fully stock. I am very happy with the way this phone runs stock.
Sent from my SGH-T889 using xda premium

I absolutely had in my mind I wasn't going to root etc. but im running the latest jedi rom and it is phenomenal!
Sent from my SGH-T889 using xda app-developers app

There are some cool features tied in with touch wizard specific to our pen capability. If you go custom you may lose that. So I would look more at rooting like such. Do I want root to bypass tethering lockdown from the vendor or to make backups with Titainium? Do I really need to overclock or undervolt? Do a new ROM's features negate the potential loss of pen related features
Sent from my GT-N7105

Im rooted running stock, tried jedirom 10 and had to pull the battery after every phone call. Still havent gotten an answer as to why this was happening. Went back to stock rooted and done with custom roms until this gets ironed out.....on a positive note, that jedi 10 with that kernel was flying and im very disappointed that I couldnt stick with it as it has awsome features.

zellroot said:
Im rooted running stock, tried jedirom 10 and had to pull the battery after every phone call. Still havent gotten an answer as to why this was happening. Went back to stock rooted and done with custom roms until this gets ironed out.....on a positive note, that jedi 10 with that kernel was flying and im very disappointed that I couldnt stick with it as it has awsome features.
Click to expand...
Click to collapse
I was running stock rooted since I got my phone late last December. But today I finally decided to run a custom rom and jedi 10 was it. Flashed with no problems and do not see the problem you have. The rom is really nice. Here are some features I would suggest rooting for:
1. Free wifi tethering (it's a must for me since T-mobile charges $15 for me to use data that I'm already paying for).
2. Wifi calling (good option to have in case I do not have signals) - the jedi 10 rom offers this.
3. Multi-windown (any app) - a cool feature. I don't think I will use it much though. But it's good to use to show off.
4. Samsung keyboard with auto-correct. I wanted to keep the samsung keyboard so that I can use the s-pen sometimes. But the jedi rom has the auto-keyboard switcher embedded.

??????
I rooted my phone I think but now I dont know what to do next! How do I pick a rom and where do I go to pick a rom or download one? Also what are kernals and overclicking?

SAMOANBK47 said:
I rooted my phone I think but now I dont know what to do next! How do I pick a rom and where do I go to pick a rom or download one? Also what are kernals and overclicking?
Click to expand...
Click to collapse
Before you do anything else, search "nandroid" learn all about it, and make one.
Sent from my SGH-T889 using xda premium

I was stock until about 3 days ago. I moved into the Jedi ROM. I used CWM, the non-touch version. I don't know if I'm old school or worried about a non responsive screen but eh.
Originally I'd just thought to stay stock and not rooted so I could get OTA'S. Though with a ROM, I'm already miles ahead of the game.
As another person stated, using the tethering has really been good for me. I'm paying $70 a month, $15 more for the hot spot would of been ridiculously overkill.
Also, I've never seen or witnessed a phone become so buttery smooth and perform so well. I'm happy. ^_^
Just make sure you do back ups through TiBu and do nandroids.
Sent from my SGH-T889 using Xparent Green Tapatalk 2

I rooted, went to Jedi ROM, but had issues, like screen tearing, slow response (probably aggressive underclocking) and some other weirdness. Went to Tweaked ROM, and had to pull battery after using CNN app for 5 minutes. Also phone is very slow to wake. Turning screen off makes music player unusable. I think I should go to stock, but I would love to have TSM Parts thing on it. Wonder if there's a way to install it.

Meanee said:
...Went to Tweaked ROM, and had to pull battery after using CNN app for 5 minutes. Also phone is very slow to wake. Turning screen off makes music player unusable. I think I should go to stock, but I would love to have TSM Parts thing on it. Wonder if there's a way to install it.
Click to expand...
Click to collapse
This would likely be better off reported in the Tweaked thread...
But, w/ the CNN freeze up (was this an app or website? Reading text or watching video/listening to audio?) was there any FC at all? What kernel were you using? What version of Tweaked were you running, and what sort of options did you have installed? A logcat of such an issue would be immensely helpful Also - were you charging the phone and have the MIUI battery bar active? On other phones I've experienced issues w/ video playback and that combo.
Turning screen off makes music player unusable - what do you mean? The long-press volume controls weren't working? The music stops? What app were you using to listen to music?
Very slow to wake - is there anything more specific you can offer here? Like an amount of time it takes to wake? That really shouldn't differ from stock at all - and there will always be a bit of lag there (though I never have anything more than a second or so).
And fwiw TSMParts is regrettably not an independently functional sort of apk. It requires a bunch of other edits throughout aspects of /system to actually work. But man that would be nifty

Fyi...noting what I said before, I am currently running one of Tesh's rooted stock ROMs for the international version. I can run backups, do tethering (no carrier lockdown for international), and run another kernel if I wish. It also allows me to use some of the Exposed installer tweaks to keep the Note2 touchwiz benefits and still use things like per app resultions and all apps in multiwindow.
Sent from my GT-N7105

dwitherell said:
This would likely be better off reported in the Tweaked thread...
But, w/ the CNN freeze up (was this an app or website? Reading text or watching video/listening to audio?) was there any FC at all? What kernel were you using? What version of Tweaked were you running, and what sort of options did you have installed? A logcat of such an issue would be immensely helpful Also - were you charging the phone and have the MIUI battery bar active? On other phones I've experienced issues w/ video playback and that combo.
Turning screen off makes music player unusable - what do you mean? The long-press volume controls weren't working? The music stops? What app were you using to listen to music?
Very slow to wake - is there anything more specific you can offer here? Like an amount of time it takes to wake? That really shouldn't differ from stock at all - and there will always be a bit of lag there (though I never have anything more than a second or so).
And fwiw TSMParts is regrettably not an independently functional sort of apk. It requires a bunch of other edits throughout aspects of /system to actually work. But man that would be nifty
Click to expand...
Click to collapse
I didn't really so a lot of troubleshooting. It was a CNN app. I pushed Back button from an article and got a black screen only with top bar active. Pushed power button, screen turned off. Then it stayed off. Had to do a battery pull. Not charging, no MIUI battery bar.
As for music, turning off the screen makes it stutter and slow down. Turning screen back on fixed the issue. I am guessing with screen off, clock rate is way too low to support music playback.
Very slow to wake could mean 2-3 seconds after I push the power or home button. Same thing with phonecalls. I can hear the phone ring but screen would stay black. 2-3 seconds later I can finally see who's calling.
I guess I can resolve most of these issues by tweaking clock rates, just wish I had time to read up on it.
Edit: Forgot to mention, I am on 1.4. Downloaded and flashed yesterday.

Meanee said:
I didn't really so a lot of troubleshooting. It was a CNN app. I pushed Back button from an article and got a black screen only with top bar active. Pushed power button, screen turned off. Then it stayed off. Had to do a battery pull. Not charging, no MIUI battery bar.
As for music, turning off the screen makes it stutter and slow down. Turning screen back on fixed the issue. I am guessing with screen off, clock rate is way too low to support music playback.
Very slow to wake could mean 2-3 seconds after I push the power or home button. Same thing with phonecalls. I can hear the phone ring but screen would stay black. 2-3 seconds later I can finally see who's calling.
I guess I can resolve most of these issues by tweaking clock rates, just wish I had time to read up on it.
Edit: Forgot to mention, I am on 1.4. Downloaded and flashed yesterday.
Click to expand...
Click to collapse
Hmm... my thoughts:
- That may have just been wonkiness in the CNN app - not sure if anything I did could impact something in the way you described (but of course I could be wrong).
- Yeah that is way slow - and uncharacteristic from my experiences at least
- That plus the music issue makes me wonder - are you just using the stock kernel? If so you can't do much in the way of clock rate tweaking, but I also find it curious as I've heard little in the way of issues regarding the stock kernel.
- Did you do a full data wipe before installing?
Regardless - I am sorry to hear about the poor outcome - feel free to PM me if you want any suggestions/help troubleshooting. I'm not the best at it (especially remotely), but I'll try
Sorry for the off-topic stuff OP!

The question doesn't make sense.
Rooting just means you unlock the root account on the phone to have superuser access. This is required by some useful apps (ProxyDroid, Paragon NTFS & HFS+ which lets you mount any USB stick or hard drive using an OTG cable, backup programs...). You can very well keep the stock firmware and just root it, which is what I ended up doing on the Note II.
On my previous Galaxy S2 CM10 was working like a champ, so I figured I would try it on the Note II... I think at this point it's a total disaster and completely unusable, just not ready for prime time. Bluetooth is completely broken, the camera doesn't work, the video driver has problems, and most of all you lose a lot of the cool things you get with the stock firmware (multi-windows, stylus-specific features, etc...). Good enough if you're contributing to the ROM development and testing for bugs and missing features, but painfully not ready for prime time. The big problem is that you just don't know what feature will break next and will let you down right when you need it.
So for me, it's stock until CM10.1 goes RC. But of course I rooted it because I want to be able to use some apps that require rooting.
Note that some Samsung apps (Readers Hub) detect SuperSU and refuse to run. Uninstall SuperSU and use Superuser instead, and use Voodoo OTA Rootkeeper to temporarily unroot the phone if you need to use them.

Rooted on Stock Rom is the way to go.

I stay on stock ROM for Wi-Fi calling, but I had it rooted in order to transfer application data.

Backup your efs as well, because there has been several people that have lost their imei.

[OFFICIAL] CM10.1 Bug Tracker Thread

So there's been a lot buzz lately about the bugs that are present in the latest build. Therefore, I'm going to maintain the thread to keep track of it all.
RULES:
-This is not a thread for feature requests. It's a thread for bugs, issues, and problems only!
-Before posting, you must swear under oath and punishable by law, that you are referring to a fresh installation and not a dirty flash (a fresh flash can alleviate a lot of the intermittent problems you may be having)
-In order to be a bug, it has to be confirmed by other users under same conditions
Please make sure to actually test bugs instead of saying yes yes yes. I will try to test each bug, but I'm relying on people's integrity as well. We don't want devs wasting time trying to fix something that isn't properly broken. So ensure that your bugs are legit and reproducible. Also, logcats where possible would be an amazing help too. I'm only adding bugs OP that are confirmed by at least a couple users. If it's not in the OP, it's not official.
Current bug list in no particular order:
Lock screen takes a while to draw
GPS works but reports 0-2 satellites only, NMEA data stream seems to be incorrect, so parsing this data may be touchy in some apps
Face unlock doesn't work
Autobrightness is choppy and slow
Pictures from camera show up in the wrong orientation from how they were taken
Bluetooth for headsets does not work, but may work connecting to GPS, etc.
Audio in skype is messed up
Gallery picture editing
Sound delay in calls
Work in progress...

FIXED (latest build)
Music skip/stutter when screen is off
Tethering is broken - M3 Build - thanks budor
No audio in video recording
Data usage/tracking does not work in the settings menu
Keyboard crashes

Current news...
Bluetooth is still broken
New build has an updated kernel with ota support
They are closing in on the audio issues
Stay tuned for a fresh build when the new monthly is released

For the record: this is on CM10.1, on the Samsung Captivate Glide, using the recent 4.2.2 update dated 2/17/2013
- Bluetooth Headset profile doent work
- Audio in video recording not working
- Photosphere unavailable
- audio stutters if screen is turned off (seems to be a CPU sleeping issue)
- Something (i am suspecting Google+, even though i am not actively using it) is filling up my SD card with gigabytes of thumbnails, which i have to delete manually
- lockscreen takes too long to appear
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts). Not a bug per se, but a symlink would've been nice?
- auto-brightness is choppy and slow
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
- face unlock doesnt work (hangs when opening the camera)
- orientation issues when taking photos: if i take a photo in landscape mode, it ends up in portrait mode in the gallery, and vice versa
Since i guess and hope many people will report bugs, and some of them will be not reproducable by others, we should have some mechanism to 'vote' or 'confirm' bugs, i guess?

All of the above...
Connecting to PC with USB, MTP mode does NOT work (it did work in Adam77root's last CM10.1 build ...)
Email - Any mail delivered into sub folders (Using Push MS Exchange) doesn't create a notification.... I miss a lot of email when sorting via rules on delivery. This is new in JB.
Some apps are deleted after reboot. (temporary fix is manually move to sdcard)

The phone connection will drop randomly and not come back until I reboot the phone. Note that I am using a Rogers (Canadian) model, if it has any relevance. Let me know how I can help you diagnose this bug.

mschweini said:
For the record: this is on CM10.1, on the Samsung Captivate Glide, using the recent 4.2.2 update dated 2/17/2013
- Audio in video recording not working
Click to expand...
Click to collapse
+1
- lockscreen takes too long to appear
Click to expand...
Click to collapse
+1
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts). Not a bug per se, but a symlink would've been nice?
Click to expand...
Click to collapse
+1, using Directory Bind as a replacement
- auto-brightness is choppy and slow
Click to expand...
Click to collapse
+1
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
Click to expand...
Click to collapse
GPS lock timeframe +1, not sure about the report
- face unlock doesnt work (hangs when opening the camera)
Click to expand...
Click to collapse
+1
- orientation issues when taking photos: if i take a photo in landscape mode, it ends up in portrait mode in the gallery, and vice versa
Click to expand...
Click to collapse
+1
yohan4ws said:
Some apps are deleted after reboot. (temporary fix is manually move to sdcard)
Click to expand...
Click to collapse
For me, some apps are weird and are missing icons: http://i.imgur.com/CNZ5Nwq.png

face unlock does not work, but it's not that important, just to mention it.

OP updated. Please make sure to actually test bugs instead of saying yes yes yes. I will try to test each bug, but I'm relying on people's integrity as well. We don't want devs wasting time trying to fix something that isn't properly broken. So ensure that your bugs are legit and reproducible. Also, logcats where possible would be an amazing help too. I'm only adding bugs OP that are confirmed by at least a couple users. If it's not in the OP, it's not official.
Sent from my SGH-I927 using Tapatalk 2

Just thought that I would mention that I've noticed that the audio stutter is even more noticeable when the phone is plugged into something using a line in instead of headphones. I'm not sure if this is a issue specific to my device, but if I use a patch cord (audio cable, but w/o the extra contact for a remote) the music sometimes stops altogether, and rarely resumes. This happens whether the screen is on or off. Bluetooth audio stream however is completely fine. No stutter even if screen is off.

Devian50 said:
Just thought that I would mention that I've noticed that the audio stutter is even more noticeable when the phone is plugged into something using a line in instead of headphones. I'm not sure if this is a issue specific to my device, but if I use a patch cord (audio cable, but w/o the extra contact for a remote) the music sometimes stops altogether, and rarely resumes. This happens whether the screen is on or off. Bluetooth audio stream however is completely fine. No stutter even if screen is off.
Click to expand...
Click to collapse
I've never had it stop on me all together.
I feel like this thread should be in the dev section, no? Flag this thread to move it if you think so
Sent from my SGH-I927 using Tapatalk 2

Please don´t throw stones, but bluetooth is or isn´t working? I´d like to try CM 10.1 but I need bluetooth working to use the phone while driving.

brunobbarcelos said:
Please don´t throw stones, but bluetooth is or isn´t working? I´d like to try CM 10.1 but I need bluetooth working to use the phone while driving.
Click to expand...
Click to collapse
2nd post ... says Bluetooth headset profile doesn't work .. this means you can stream Audio to your car's stereo, but you can NOT use your headset... I'm going to assume it's the same accross all ROMs that you can HEAR the other person talk, but the microphone via bluetooth isn't enabled.... my other assumption is that it has to do with the sound driver issues of using skype etc. where when the microphone is activated, all other sound output becomes sloooow motion. -
These are assumptions based on an under educated hypothesis .. a guess.. a shot in the dark ... based on no fact .. and hence, could be completely entirely wrong
Here's a thought, though, why don't you do a nandroid backup in CWM one evening, download the CM10.1 and install it and play with it test bluetooth and some other things, report your findings and if bluetooth deosn't work, revert back to your backup... nothing lost and everything to gain PLUS you'll be helping out the community.

gtmaster303 said:
I've never had it stop on me all together.
I feel like this thread should be in the dev section, no? Flag this thread to move it if you think so
Sent from my SGH-I927 using Tapatalk 2
Click to expand...
Click to collapse
The reason it isn't in the dev section is because it isn't actually a dev thread. The dev section is more for an actual product, whereas this is more documentation for a product, meant to answer questions people might otherwise ask in the general section.

Any of you guys use Whatsapp? It will tell you that tablets are not supported.. :/
And the main Google search app (where you can't type more than one letter from the homescreen) always closes.
Great work BTW. I just got this this afternoon. I'm loving how smooth it is
Sent from my SGH-I927 using xda app-developers app

chrisyjwai said:
Any of you guys use Whatsapp? It will tell you that tablets are not supported.. :/
And the main Google search app (where you can't type more than one letter from the homescreen) always closes.
Great work BTW. I just got this this afternoon. I'm loving how smooth it is
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Whatsapp works for me.
You can fix the google search app by disabling the hotword feature.

Snuuuuupy said:
Whatsapp works for me.
You can fix the google search app by disabling the hotword feature.
Click to expand...
Click to collapse
Yea. Sorry my bad. I had no service at that point. The app could not verify a network and assumed it was a tablet.
Thanks.

Okay. So basically I flash this firmware and before I proceed to use any of the apps I decide to update them. So while the outdated search app still had the hotwords feature on, I updated it. Thereafter, the app will close even before I could get to the setting menu. So the only way is to either use the older version or use the older version to turn off the hotwords feature and update. I know this is minor. Just thought I'd add this to a bugs thread.
And there are some speaker/microphone issues with google hangouts.
Anyone second this?
Sent from my SGH-I927 using xda app-developers app

chrisyjwai said:
Okay. So basically I flash this firmware and before I proceed to use any of the apps I decide to update them. So while the outdated search app still had the hotwords feature on, I updated it. Thereafter, the app will close even before I could get to the setting menu. So the only way is to either use the older version or use the older version to turn off the hotwords feature and update. I know this is minor. Just thought I'd add this to a bugs thread.
And there are some speaker/microphone issues with google hangouts.
Anyone second this?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Open up the older one. Don't update, disable hotwords and that new google feature (cards?). Update, should work fine.

Tethering
Tethering is broken, I didn't see it in the list. Even FoxFi doesn't work.