Develop Bugs

Huge sound settings bug

You can easily miss this one but it is very unpleasant if it catches you off-guard. Please read carefully. I posted this in the Desire and Desire S forums because those are the phones on which I discovered the bug. If anyone has anything against it please feel free to delete either thread.
I found a humongous BUG in a new Sense / GingerBread (I haven't tried FroYo, it may exist there also). I confirmed it on Desire with AceSMod007, SGBS and Cool3D Sense 3.0 and original stock ROM on HTC Desire S. Whatever the culprit is, whose ever fault it was, HTC or Google screwed up big time (something like famous -88dBm-wifi-stupidity)!!
Problem and how reproduce it:
1. Put your child to sleep (important!)
2. (…2 hours of hard work later ) Set the ringer volume to minimum so that you can hear it in a complete silence while your kid sleeps and you are working on your computer. Or you could be on a meeting… my point remains. Let's say that 30% is enough for the ringer volume.
3. Do whatever you want with the phone: play YouTube video (on very low volume, of course), enter your favorite navigation app, browse contacts, surf the web, change sound profiles with the official HTC widget… but please, for the love of god, DO NOT touch the Dialer App (the big phone button at the bottom of the screen)
4. As soon as you enter your Dialer App (weather you are about to make call or you are answering the incoming call or you just want to see call history) the strangest thing happens: our beloved phone decides that it would be appropriate to increase System sounds volume to maximum.
5. That is not the biggest problem. This one is IMPORTANT: After you initiate a call (using Dialer) ringer volume goes back to the value it had previously when you received your last call. Weird?! Steps to reproduce a problem:
a. set your ringer volume to X%, (X > 0)
b. receive a call (call yourself from your other phone and reject it), note that X% should now be "remembered"
c. set ringer volume manually to Y% (Y ≠ X, use some extreme values to tell the difference easily, say 10% and 90%)
d. enter Dialer app and call anyone (12345 will do),
e. hang up
f. check the ringer volume – it went back to X% (scary? )
g. in special case, if you initially set X to 0% the ringer volume will not revert to 0% but will stay Y% instead (hence the X > 0 restriction in the first step)​​
6. Ask yourself: Why the hell Dialer app changes my systems sounds or ringer volume and should I really (REALLY?!?!) check the ringer volume each time after using my phone just to be sure nothing will go wrong in a "silent environment"??? WTF?!?
Can you guys confirm this please? I checked system sounds volume using sound mixer in Notification Toggle app but I am sure there are other ways to check it. Ringer volume is present in the settings.
I am planning to contact HTC but knowing how useless is their support do you think a petition is the solution? Or should we send them a ton of mails?
Note: Once more, this is tested with Sense ≥ 2.1 and GingerBread ROMs (including Desire S stock). You can try it with FroYo if you like.
Best regards to all of you!! I enjoy being part of this community and during past few years it taught me a lot.
Thank you!

Nice catch, any reports on devices from other makers than HTC?

interesting..

Nasty!
For those that have the all powerful (although not free) tasker application, I wonder if we could use it in order to reset volume levels to ensure that you don't get bitten again!
Not got time right now to test....I wonder if bug still there on sense 3.0 and sense 3.5?

hmmm very interesting...

ben_pyett said:
Not got time right now to test....I wonder if bug still there on sense 3.0 and sense 3.5?
Click to expand...
Click to collapse
I am also planning to test it on Sensation (as soon as I get hold to it)
coolexe said:
hmmm very interesting...
Click to expand...
Click to collapse
I really hoped that devs like you will stumble upon this thread. Now we have a chance... or at least a hope.
I wonder how things are doing with AOSP GB ROMs? Anyone?

ben_pyett said:
Nasty!
For those that have the all powerful (although not free) tasker application, I wonder if we could use it in order to reset volume levels to ensure that you don't get bitten again!
Click to expand...
Click to collapse
Thanx for the suggestion! I am using Llama for a while and I totally forgot about Tasker. I played a bit with Tasker Trial version today and it can be "fixed" this way. Althougt Tasker must be paid for after 7 days and this is not actual solution... but it works If anyone needs Tasker guidance feel free to contact me.

This strange sound bug is present in the official ("developers") 2.3.3 Gingerbread update for the Desire, tested and confirmed!

[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.

[Q] Why can't I control my Desire's volume?

I'm really annoyed by the fact that I miss calls because the ringer volume was too low. But I have tried everything, and I mean everything, to try to correct that. You name the ringer volume locking app, I no doubt tried it. Tasker, etc. as well. None of them work at either locking the ringer volume at 100%, or raising it to 100% when a call comes in.
Since other people don't seem to have this problem.... I'm wonder, is it possible that the Manu kernel I install could be blocking something? Or what about the MIUI XJ ROM I got from here? Any other clues?!

When you're playing a music file without headphone, is the speaker giving loud sound then?
If yes, then your speaker is allright.
If no, plug in headphones and check the volume through your headphone. If the volume is also low there, then your amplifier is broken.

Cyanoid said:
I'm really annoyed by the fact that I miss calls because the ringer volume was too low. But I have tried everything, and I mean everything, to try to correct that. You name the ringer volume locking app, I no doubt tried it. Tasker, etc. as well. None of them work at either locking the ringer volume at 100%, or raising it to 100% when a call comes in.
Since other people don't seem to have this problem.... I'm wonder, is it possible that the Manu kernel I install could be blocking something? Or what about the MIUI XJ ROM I got from here? Any other clues?!
Click to expand...
Click to collapse
I use Volume Control app. But then again you said you tried every volume app there is.
Manu is not blocking anything as I've been with ManU kernel for a long while.
Try to change your ringtone. Some ringtones are louder than others.

Well, the problem has nothing to do with the choice of ringtone I'm using. If the volume is too low, I'm obviously not going to hear the phone, regardless of the volume of the ringtone.
TheRamon: I think you may have misunderstood the issue. It's not that the volume is low all the time. It's that it may have been turned down or off for various reasons, and I need the ringer vol to be 100% when a call comes in.
There are many apps that will do this, but absolutely none have worked properly on my Desire. So if we've ruled out the kernel, and others with Desires have managed to accomplish this through apps.... why am I not able to do the same?!
There is no particular indication anywhere that the phone is not working properly.

Have you ever flashed another rom to test?
via xda app

stankyou said:
Have you ever flashed another rom to test?
via xda app
Click to expand...
Click to collapse
No, I haven't. But that's because it's a big deal (for me, anyway) to do that. I have to go through hours and hours settings things back up similar to what I had. So I don't change ROMs too often. Truth be told, I never really had luck with any ringer volume lock app on the Desire, and that's 2 years looking. They all mess up in one way or another, making them unuseable. It's just that it seems to be even more the case since I installed MIUI XJ with the Manu kernel. But I don't know. There may be no connection. All I know is that other Desire users have no (or little) problems with the ringer lock apps and I do!

Cyanoid said:
No, I haven't. But that's because it's a big deal (for me, anyway) to do that. I have to go through hours and hours settings things back up similar to what I had. So I don't change ROMs too often. Truth be told, I never really had luck with any ringer volume lock app on the Desire, and that's 2 years looking. They all mess up in one way or another, making them unuseable. It's just that it seems to be even more the case since I installed MIUI XJ with the Manu kernel. But I don't know. There may be no connection. All I know is that other Desire users have no (or little) problems with the ringer lock apps and I do!
Click to expand...
Click to collapse
Im not really asking you to switch rom. What im saying is nandbackup your current rom and flash a different one. Check if the volume issues disappear or not. Since you are using an AOSP based rom, my suggestion is to flash a Sense based rom and see if the issue remains. At least you'll have an idea if its just a rom related issue or not and determine the next troubleshooting step from there. It will be difficult to find a solution if you don't try to isolate where the problem is coming from.
via xda app

Ok, I actually did switch ROMS.... I'm on the latest stock MIUI GB ROM for the Desire, after wiping everything, and all stock apps. I just downloaded and tried a couple of locking apps; Ring Lock, Smart Volume.... they don't work! Smart Volume buzzes when I change the volume, but it happily allows me to do so!
So now I'm wondering if its MIUI itself that is preventing volume locking. Yet I doubt it, because I think we'd have heard that from MIUI users. Each volume control app seems to have its own reason for not working. Some will lock volume settings with each other, but still allow you to change the ringer volume. Some will have dialog boxes go into an infinite loop if you try to change the ringer volume. Some will vibrate a notification when you change the ringer vol., but will still allow you to do so. Even in Tasker, I set a profile to change the brightness and the volume upon ring... it changes the brightness, but not the volume. Since each app has a different type of failure, one would logically conclude that it's the apps that are simply faulty.
But then there's the irrefutable fact that while some find these apps faulty (sometimes for the same reason I did), I'm guessing not everyone with a Desire has been unable to get the ringer volume to stay locked. So I still don't know if it's an inherent problem with the Desire. But if it's due to MIUI, I'll have to live with it. Because... I like MIUI a bit more than I hate the fact that I can't control the ringer volume!

Update: I just discovered this, so I've yet to confirm.... but I just tried an escalating ring app.... and it actually worked on my Desire. I left the phone on low, the app started low and took the volume to max. That means, the volume is/may be controllable on this device, by a 3rd party. Just before this, I started messing about in Superuser, looking at the tons of logs it creates. Turns out, by default, Superuser was not giving full permissions to my apps - specifically the right to make calls and related etc. I set all such.apps to full permissions.
I will try with a ring locker app tomorrow (but even the escalating ring app is actually perfect for my needs!)..

Spontaneous call

Hello,
I bought new a new headphone yesterday (sennheiser cx400 precision ii)
When I am walking around with these new earphone's they sometimes call the last person in my list.
The music stops playing and I hear the same sound as when I hang up.
Then the music continues playing.
When I opened the call information it told me I called like 10 times today.
Each of the calls was 1 sec or so?
Does any of you guys know how this can happen?
~ Archcry

HTC Sense lock screen tends to unlock often in my pocket, and i had similar problem.
Try to do that: in settings/security/screen lock set lock method ( i use pattern )
This kept my phone from unlocking in my pocket.

staviq said:
HTC Sense lock screen tends to unlock often in my pocket, and i had similar problem.
Try to do that: in settings/security/screen lock set lock method ( i use pattern )
This kept my phone from unlocking in my pocket.
Click to expand...
Click to collapse
I already have a pattern, it does not solve the problem.

archcry said:
I already have a pattern, it does not solve the problem.
Click to expand...
Click to collapse
ok,
Does this happen only with this headphones, or with other too ? ( this maybe a stupid question, but if the headphone plug does not fit correctly, it might trigger 4th "pin" that some earphone/microphone sets have for picking up and making calls, at least this is my guess )
Does this happen on stock / other roms ? new ARH is out ( v17 ) you may try to update.

staviq said:
ok,
Does this happen only with this headphones, or with other too ? ( this maybe a stupid question, but if the headphone plug does not fit correctly, it might trigger 4th "pin" that some earphone/microphone sets have for picking up and making calls, at least this is my guess )
Does this happen on stock / other roms ? new ARH is out ( v17 ) you may try to update.
Click to expand...
Click to collapse
Yea that's what I was thinking, it might hit the 4th pin, so is there a way to disable this 4th pin as I do not have a button on my headphone anyways?
Yes it only happens with headphones.

archcry said:
Yea that's what I was thinking, it might hit the 4th pin, so is there a way to disable this 4th pin as I do not have a button on my headphone anyways?
Yes it only happens with headphones.
Click to expand...
Click to collapse
Maybe this will help, I don't have any kind of headset with a button to try it:
https://play.google.com/store/apps/...DEsImNvbS5pZHVubm9sb2wuaGVhZHNldGJsb2NrZXIiXQ..

staviq said:
Maybe this will help, I don't have any kind of headset with a button to try it:
https://play.google.com/store/apps/...DEsImNvbS5pZHVubm9sb2wuaGVhZHNldGJsb2NrZXIiXQ..
Click to expand...
Click to collapse
Well I am going to try this sometime soon, thank you for your help.
I might aswell get another plug installed on my headset (with 4 rings) leaving one of the rings without a signal.
This will make sure the plug isn't touching anything else.
But ill try the widget first.
~ Archcry

archcry said:
Well I am going to try this sometime soon, thank you for your help.
I might aswell get another plug installed on my headset (with 4 rings) leaving one of the rings without a signal.
This will make sure the plug isn't touching anything else.
But ill try the widget first.
~ Archcry
Click to expand...
Click to collapse
The app does not work for ICS nor JB, I am currently running JB.
More suggestions?
I've tried the normal htc head-set and pressing the button 3 times in a row gives me the same problem as described before.
So the new headset is indeed triggering a signal, would replacing the 3ring plug with a 4ring plug solve this problem?
The 4th ring wont be connected to annything thereby making the signal 0.
The apps I found do not work, they work for music and other stuff but not for the call problem (pres 3 times)
Could there be a way to dissable this in the android software itselve, as I do have root access?
~ Archcry

archcry said:
The app does not work for ICS nor JB, I am currently running JB.
More suggestions?
I've tried the normal htc head-set and pressing the button 3 times in a row gives me the same problem as described before.
So the new headset is indeed triggering a signal, would replacing the 3ring plug with a 4ring plug solve this problem?
The 4th ring wont be connected to annything thereby making the signal 0.
The apps I found do not work, they work for music and other stuff but not for the call problem (pres 3 times)
Could there be a way to dissable this in the android software itselve, as I do have root access?
~ Archcry
Click to expand...
Click to collapse
I found a headset with button and indeed pressing it 3 times makes call and drops it after about 1 sec.
I also tried a few apps from market and none of them is working as expected.
On the kernel level it seems like only reading this button is possible, and apps that "block" it only try to intercept a button press and register its own handler, but on new androids 4+ registering handler for this button does not suppress further processing of button press action so its looks to me like blocking it by app is not possible
Hardware solution may be the only way
I have an idea but I'm at work so i cant try it now: you may try to insulate the area of jack plug where 4th pin is supposed to be, like here:
http://forum.xda-developers.com/showthread.php?t=829723
EDIT:
This thread is worth linking, maybe They will find something
http://forum.xda-developers.com/showthread.php?t=2032828

[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.