Thread Closed !!
New Google's Android 4.2.1 Features
-> Photo Sphere
-> Gesture Typing
-> Multi-User Support (Tablets Only)
-> Miracast Wireless Display Support
-> Daydream
-> Notification Power Controls
-> Google Now Improvements
For More Information on Which of the above features available in CyanogenMod, Come to My New Thread T989 Official CM10.1 4.2.1 Discussion (Coming Soon)
Enjoy !!! :good:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
theandroidrooter88 said:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
Click to expand...
Click to collapse
This is why i started this Thread, So we can discuss Bugs in the latest versions. :highfive:
I heard AOKP JB is stll having SODs and RRs. Do u find anything like these?
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
First we have to fix our flashing methods and recoveries used. I for one haven't experienced one single RR or SoD since I started flashing official nightlies. People are probably causing these issues themselves to begin with. Expecting a fix for an issue that has no identifiable cause.. I wonder if any other phones outside the t989 forums are experiencing RR and SoDs with Jelly Bean..
Sent from my SAMSUNG-SGH-T989 using xda premium
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
garth719 said:
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
Click to expand...
Click to collapse
Great to hear that your running latest 10-Oct Nightly. A Simple advice to you & all other users, is to restore app without data if your are using any backup tools such as TitaniumBackup etc., Restore Apps with data cause Problems.
srikanth.t989 said:
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
Click to expand...
Click to collapse
Sorry, I don't mean to crap on the thread but unless you can confidently say that SODs and RRs have been fixed (changelogs, yourself writing the code, etc.), going by your own experience shouldn't be the end-all-be-all to say whether something is fixed or not. Just like with call echo, some devices are worse than others.
I see that supposedly the issue with audio and docking has been addressed. However, the docking option is still grayed out for me when docked. Just looking for audio pass-through while docked...
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
eight_heads said:
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
Click to expand...
Click to collapse
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
I'm on recent CM10 Oct10 nightly and the BLN lights stay on, even with the Oct 7 nightly.
Update: fixed my own problems. This post helped: go to menu - systems - advanced settings - sensor and uncheck and check enable keys notifications and then send yourself a text or email. It actually should work out the box mine always has. Make sure you have notifications checked off in the apps like sms and gmail.
Also check display - notification light to make sure it enabled and you can add the apps you want to have the light enabled to work
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
garth719 said:
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
EDIT:
Just ran the music player for 45min on a run. no skips, nothing.. ran a 90 mb mp3 file too which usually gives my ipod trouble.. good sign
Click to expand...
Click to collapse
So is that how we're saying we don't get random reboots anymore? We just call them something else??
algorhythm said:
So is that how we're saying we don't get random reboots anymore? We just call them something else??
Click to expand...
Click to collapse
well there was a difference in this reboot because my phone didnt actually fully shut off. the "cyanogenmod" boot animation came up and the phone was ready to go in about 20 seconds. there was no usual vibration indicating that the phone has shut off and no "samsung" boot image as a regular reboot would do. call it what you will
Quote:
[email protected]: on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
Try updating it on the market
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Laazyboy said:
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Run only One ROM. Do a clean reflash. We are not experiencing any SODs or RRs. Use only one ROM because Flashing different ROMs one after the Other will Make your device weak. The data left by the AOKP causes some errors to CM10. Thats why i said that don't restore the apps with data.
Related
Hi everyone,
I've looked for a solution all over the net, but seems like no one had this problem before (guess i'm a special girl...):
The vibrate feedback when touching the screen just stopped working, in spite of the settings under "settings -> sounds -> vibrate on touch".
It started after an update to AOKP rom - milestone 5 (based on ICS 4.0.4) + Franco kernel nightly r151, but effects all the other roms. Maybe one untouched system file damaged.
I've tried everything: restore from previous nandroid backup, another rom (CM9), another kernel, another launcher, I even wiped everything and flashed new and clean rom-stock from google developers' page. And yet - no vibrate feedback.
The wired thing is that the haptic feedback is working in few specific applications, like the build-in ICS keyboard and the dialer Dialer-One, so it probably not some hardware failure.
All this time there are five softkeys that still have haptic feedback: the buttons of the nav-bar, the button that opens the applications drawer and the google-search widget.
I've tried using "KickBack" instead, but it's too aggressive and very uncomfortable.
PLEASE, PLEASE - Help me!
Same thing happened to me. I had the exact same setup and the haptic feedback went away after I flashed the kernel. Since I've had lots of issues when trying custom kernels, I just restored a nandroid and went back to the kernel included with aokp.
Sent from my Galaxy Nexus using XDA
Restore fixed my issue, so I'm not sure exactly what to tell you.
Sent from my Galaxy Nexus using XDA
taappel said:
Restore fixed my issue, so I'm not sure exactly what to tell you.
Click to expand...
Click to collapse
I've seen some ppl's msgs that even simple reboot fixed their vibrate problem.
Didn't work for me, unfortunately
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm also using Franco kernel, but I don't think this is the problem because i've tried some other kernels and none of them fixed my haptic.
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
nich0145 said:
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
Click to expand...
Click to collapse
Thanks guys, but as I wrote in the first msg, those actions didn't help.
Is there any pro here who can offer a profound solution that I didn't tried before?
Which system file responsible for the haptic feedback?
Guess I'll have to stuck without haptic feedback...
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Click to expand...
Click to collapse
How can I adjust the haptic feedback feature in Trinity kernel?
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
takomar said:
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Click to expand...
Click to collapse
Dacian said:
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
Click to expand...
Click to collapse
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
im starting to believe its a hardware issue (well at least for me) i mean i dont even get a vibration upon booting or turning off the phone...and i even went back to full stock...same thing
maybe it might have been some software issue that led to the overburning of the motor(doubt that though)
what is weird though is that the same scenario happened to us so im lost...
maybe i should start talking to samsung for my replacement
meanwhile...im very open to suggestions that might help my case
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
takomar said:
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
Click to expand...
Click to collapse
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
TaliKa said:
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
Click to expand...
Click to collapse
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
takomar said:
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
Click to expand...
Click to collapse
I couldn't find it in play store either, but i download it from here:
http://code.google.com/p/eyes-free/downloads/detail?name=kickback-v1.1.1.apk
works fine for me.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
Good to know. I went ahead and flashed the base image and it restored vibration, then I rooted and flashed AOKP again. It worked for about that day and then this morning when I woke up the vibration is gone again. I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Dacian said:
I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Click to expand...
Click to collapse
Which kernel do you use? and did you set the quite hours on?
If you succeed to restore the vibrate, i'd like to hear exact instructions how to do that, including links to download the boot image, if you plesae...
Please post any bugs you experienced and what nightly they are found in. This is going to be updated daily starting with the 1/06 nightly. PLEASE check if someone already posted the bug so repeats are minimal. This thread is also intended to be a place to discuss workarounds and fixes for bugs.
Nightly: 2/21
Confirmed Bugs:
-Bluetooth issues (media streaming and calls)
-random bug where everything is taken as a long press
-Occasional flickering (very rare)
.........-FIX: Ktoonsez 4.2.1 Kernel 1/1 Build. Download link: goo(dawt)gl(slash)xUrML
........ -FIX2: disable HW overlay in developer options
-terminal emulator and movie studio force close
......... -FIX: delete then install from Play Store
-Hotspot issues
......... -FIX: use SVTP
-Visual voicemail issues
-Pandora keyboard issue
Unconfirmed Bugs:
-MMS issues (works on and off)
-First few seconds of songs in Apollo are louder than normal.
-screen mirroring
-dock audio
-WiFi stability problems
-Notification light does not work with unread text messages once the screen has timed out.
-When pressing the power button to turn screen off, there is a delay.
Resolved Bugs
-echo when calling using speakerphone
-Quiet in-call volume
-ringtone is distorted when on full volume
-screen flickers when changing volume in YouTube, Google Music, browsers, and some other apps
-delay for the other person to hear you when your answer the phone call
Add This One
Bug:
1) EXTREMELY quiet in-call volume, both with the front facing speaker and the rear speaker phone. This affects all 4.2 AOSP ROMs.
And just so the people who don't search can see it as well :
2) Bluetooth does not work for streaming media, and is flaky for calls
3) Screen flickering in Gallery - hard to recreate on-demand but is definitely there in the Gallery and some other apps. Can be fixed (mostly) by using Ktoonsz's 4.2.1 kernel ( I have had the best results with the 1/1 test release and can provide a link if needed). Disabling HW Overlay on Developer Options can help most cases of this
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
jakew02 said:
Add This One
Bug:
1) EXTREMELY quiet in-call volume, both with the front facing speaker and the rear speaker phone. This affects all 4.2 AOSP ROMs.
And just so the people who don't search can see it as well :
2) Bluetooth does not work for streaming media, and is flaky for calls
3) Screen flickering in Gallery - hard to recreate on-demand but is definitely there in the Gallery and some other apps. Can be fixed (mostly) by using Ktoonsz's 4.2.1 kernel ( I have had the best results with the 1/1 test release and can provide a link if needed). Disabling HW Overlay on Developer Options can help most cases of this
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I appreciate your help.
farice said:
Thanks, I appreciate your help.
Click to expand...
Click to collapse
I run the CM nightlies and update every morning before , so I'll keep updating that post for ya as I find new stuff to report
Also, here is a link to ktoonsez's post with the 1/1 experimental kernel
http://forum.xda-developers.com/showthread.php?p=36156163
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
jakew02 said:
I run the CM nightlies and update every morning before , so I'll keep updating that post for ya as I find new stuff to report
Also, here is a link to ktoonsez's post with the 1/1 experimental kernel
http://forum.xda-developers.com/showthread.php?p=36156163
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I can't post links yet because I just made this XDA account, but I will add it ASAP.
of wsnouk
I have encountered the unconfirmed screen flicker when using google music, also have encountered the delayed time for answering a call. I've also encountered a couple random restarts not too sure what its from but happened earlier today when using facebook messenger the app just froze then device restarted I'm on 01.04/13 build with stock kernel
Can someone elaborate on the quiet in call volume? Is it quiet for send or receive or both? Does it effect earphones?
Does MTP work?
I switched from a cm10 daily to cm10.1 (01/3) and when I plugged my phone into my computer nothing happened, but the phone started charging.
Also, when I went into recovery because the SD card had changed locations, I could not restore to my cm10 back up. Anyone else have these problems?
Penguyen said:
Can someone elaborate on the quiet in call volume? Is it quiet for send or receive or both? Does it effect earphones?
Click to expand...
Click to collapse
The low volume only affects you, not the person on the other end. It happens with both the front facing speaker and the speaker phone on the back next to the camera. However, while your on speakerphone the mic sensitivity is not very good so the other person will find it harder to hear you unless you have your mouth right next to the mic. It'll be worked out soon enough.
buckfritzl said:
Does MTP work?
I switched from a cm10 daily to cm10.1 (01/3) and when I plugged my phone into my computer nothing happened, but the phone started charging.
Also, when I went into recovery because the SD card had changed locations, I could not restore to my cm10 back up. Anyone else have these problems?
Click to expand...
Click to collapse
Android 4.2.1 creates an "emulated" storage system to help manage the multiple user idea. Being the main user (user 0) will have their files stored in /0. User 1 will be in /1. It really isn't practical for a cell phone it was more designed for multi user tablets and I'd not fully incorporated yet as far as I know. However, you will need to boot back into the ROM and move any backup files to your /0 directory and then you'll be able to see them. I'd recommend copying instead of moving them there just so you have more than one place to check while in recovery. Regardless your files are all there they just have to be moved to the proper directory on the SD card.
Also, switch to the latest TWRP recovery so you don't end up with multiple /0 folders within themselves
2nd topic on your post. No 4.2.1 or touch wiz ROMs support UMS , or USB mass storage. The only ones that did were CM / AOSP 4.1.s based
farice said:
Unconfirmed Bugs:
-ringtone is distorted when on full volume
-screen flickers when changing volume in YouTube and some other apps
-delay for the other person to hear you when your answer the phone call
Click to expand...
Click to collapse
I can confirm, along with many others running CM10.1 nightlies, Tasks AOKP builds, and all the other 4.2.1 ROMs that the ringtone is distorted when on full volume for music/videos/media and ringtones. And there is a delay after answering for about 5 seconds.
---------------------------------
This thread is good. We need to get into contact with one of the d2 device maintainers for CM to check this out once we get a few more into the confirmed category. They didn't know about the mobile data issue that was present until the 12/29-12/30ish nightlies for a while because I don't think anyone had been reporting anything to the CM team other than posting in the thread here
jakew02 said:
This thread is good. We need to get into contact with one of the d2 device maintainers for CM to check this out once we get a few more into the confirmed category. They didn't know about the mobile data issue that was present until the 12/29-12/30ish nightlies for a while because I don't think anyone had been reporting anything to the CM team other than posting in the thread here
Click to expand...
Click to collapse
I agree, we should definitely do that. I think this will be a very helpful resource for CM developers and modders eventually.
a. when using the speakerphone my voice echoes to the person on the line
b. terminal emulator force closes. have to remove and install from market
farice said:
Please post any bugs you experienced and what nightly they are found in. This is going to be updated daily starting with the 1/06 nightly. PLEASE check if someone already posted the bug so repeats are minimal. This thread is also intended to be a place to discuss workarounds and fixes for bugs.
Nightly: 1/06
Confirmed Bugs:
-Quiet in-call volume
-Bluetooth issues (media streaming and calls)
-Occasional flickering (much rarer than in previous builds)
.........-FIX: Ktoonsez 4.2.1 Kernel 1/1 Build. Download link: goo(dawt)gl(slash)xUrML
........ -FIX2: disable HW overlay in developer options
-ringtone is distorted when on full volume
-sound distortion/low sound quality on full volume for all media
-screen flickers when changing volume in YouTube, Google Music, and some other apps
-delay for the other person to hear you when your answer the phone call
Unconfirmed Bugs:
Click to expand...
Click to collapse
I get the flicker when changing volumes in browser apps.
1/07 Nightly is up. Are all of these bugs still present? I'm in the airport about to leave, so I can't confirm myself until tomorrow. Thanks everyone.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
For those using the latest nightly, was the data bug fixed?
I'm on an ATT S3 and switched a few days ago because the data drops were driving me nuts.
inkblaze said:
For those using the latest nightly, was the data bug fixed?
I'm on an ATT S3 and switched a few days ago because the data drops were driving me nuts.
Click to expand...
Click to collapse
I don't have any data issues
Randomly missing Group MMS.
Sometimes I get them and sometimes I don't. Sometimes I get a notification and no message, sometimes I get the message fine, and sometimes I get no notification or message.
Edit: Ignore sig, I need to fix that...
Home button randomly bugs out and starts going to the app switcher rather than homescreen. Annoying, but restarting phone fixes it.
I've noticed the same problem, but I also find that the menu soft key bugs out and opens up Google Search/Now without long press. Might be like something is turning the behavior of one touch on these keys into automatic long presses? And its not just the specific launchers (I'm using Apex)...I tested with others. Really annoying, but restarting the phone does provide a temporary fix.
1.Sometimes when playing music using Apollo, the first 3 seconds of the song ,after song change, would be louder than normal. (Happens with YouTube too)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Alright everyone the 1/9 nightly is up. There were several fixes merged to correct in-call volume all, and call echo while on speakerphone. If a majority rules saying it is now fixed, let's move that bug to the "resolved" section
Sent from my SGH-I747 using Tapatalk 2
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.
Hello! Since I can't post this in Sprint Galaxy Note II Original Android Development until I posted ten times so this is really for CyanogenMod 11 nightlies ROM experts.
I'm using nightly CM11 2/22/14 with plasma kernel. This issue has to do with a headphone jack while plug in and using either Apollo or any other music player. If I open another app the sound goes off but when I close the app the sound comes on. This is also true with using the status bar, when I move the status bar down sound goes off and comes back on when status bar goes back up. The same is also true if the phone goes to sleep.. again sound goes off.
There is no problem with the sound system when I unplug the jack. I haven't had this problem in the past with the Official CM11 ROM. Does this has something to do with nightlies? I tried using Soundabout and other music players but still no luck.
Anyone out there experiencing the same or know how to fix this? Any help would be grateful! Thanks in advance.
I was on the 2/11 nightly for a couple weeks and had similar issues. I use Play Music app, stock kernel and V4A. I installed Carbon KK last night and its just as bad if not worse. With headphones in, audio seems to cut out if anything takes focus over player.
Sent from my SPH-L900 using xda app-developers app
Skeptical said:
I was on the 2/11 nightly for a couple weeks and had similar issues. I use Play Music app, stock kernel and V4A. I installed Carbon KK last night and its just as bad if not worse. With headphones in, audio seems to cut out if anything takes focus over player.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Thanks! Gonna try tonight nightly and see if that resolve the issue. Wish me luck.
jplecher said:
Thanks! Gonna try tonight nightly and see if that resolve the issue. Wish me luck.
Click to expand...
Click to collapse
It was the nightly! Seemed to be working fine now! :good:
Are you still on CM then? Still having the issue with Carbon so maybe I'll need to switch back for a bit. Thanks for confirming.
Sent from my SPH-L900 using xda app-developers app
Skeptical said:
Are you still on CM then? Still having the issue with Carbon so maybe I'll need to switch back for a bit. Thanks for confirming.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Sorry just back from vacation... yes still using CM latest nightly 2/24.
Has this problem been fixed in the latest cm11 builds?
Blabah said:
Has this problem been fixed in the latest cm11 builds?
Click to expand...
Click to collapse
I still have it and after searching, I have not come on a fix.
My problem is exactly as OP described. I had the issue with builds from the 3rd, 6th, 9th, and 13th of April.
Edit:
Combination of fixes:
1. Disable hot word detection in Google Now launcher. Go home, then menu button, settings, voice, and turn hot word off.
2. Start playing the music before you plug in the headphones.
Google Play Music's volume cuts off when Google Hot word detection if ON...
I had the same issue... and have tried multiple CM nightlies with the same result. it was driving me nuts. As soon as i changed to another application Or checked the status bar the sound would mute. You are correct in turning OFF the Google "hot word" detection which turns off "OK Google" as the solution to the problem. Not sure if the problem is on Google's end OR in the CM's Team's ROM?
Thanks,
NH Apache said:
I still have it and after searching, I have not come on a fix.
My problem is exactly as OP described. I had the issue with builds from the 3rd, 6th, 9th, and 13th of April.
Edit:
Combination of fixes:
1. Disable hot word detection in Google Now launcher. Go home, then menu button, settings, voice, and turn hot word off.
2. Start playing the music before you plug in the headphones.
Click to expand...
Click to collapse
Headphone sound issue fix CM11
I found a fix that worked for me. Install AGNI CM OC kernel. During install, check off the 2nd option for sound engine. Not the one that says '(recommended)'. Worked for me, all is good now.
About CyanogenMod
CyanogenMod is a free, community built, aftermarket firmware distribution of Android which is designed to increase security, performance, reliability and customization over stock Android.
About nightly builds
Nightly builds are automatically compiled builds of the latest CyanogenMod source from github. These builds are not officially supported. If you find bugs or issues please discuss here. Do not submit bug reports for nightly builds on the CyanogenMod issue tracker.
How to install
Preparation
Ensure you have a working copy of ADB for your PC. A simple search should find versions for all major operating systems.
If you are running "stock" (ColorOS), the first thing you will need is a recovery. There are many recoveries available. The most popular ones are CWM and TWRP. Please consult other threads to find and install a suitable recovery.
Once you have a suitable recovery, download from download.cyanogenmod.org to your PC.
If you wish to have Google applications available such as the Play Store, download a current copy of gapps. CM recommended gapps are shown at wiki.cyanogenmod.org.
Reboot your phone into recovery.
Installation
If you wish to save any of your current data, back it up. Details vary by recovery. The app "Titanium Backup" is also popular to backup and restore your installed apps.
Wipe your internal data. Again, details vary by recovery. The option is usually called "wipe data / factory reset" or something similar. This is absolutely critical and required if you are coming from a stock ROM or a different third party ROM. Note! If you are coming from a previous nightly build of CM11, you can often get away with keeping your data. But if you encounter any issues, please wipe data and retry.
Find an option in your recovery that looks like "Install from sideload" or Install from ADB" and select it. On your PC, run "adb sideload cm-11-yyyymmdd-NIGHTLY-find7.zip". ADB should show a progress indicator. When the file has completed uploading, it should install. Repeat with your gapps package if desired.
Reboot your phone. The first boot after install can take a few minutes (usually no more than 5 minutes) so be patient.
Enjoy!
tdm
Systems Engineer
Cyanogen, Inc.
Known Issues
* Find7s: Screen may not wake when phone is hot.
This is apparently an interaction between the thermal throttling code and the video/gpu driver. It has been reproduced and we are working on a fix.
* Find7s: Notification light sometimes misbehaves.
We are working on a fix.
* Find7a: Battery sometimes drains too quickly.
This issue is under investigation. We do not have a repro or a fix at this point.
* Find7a: Mic doesn't work while on speakerphone.
This issue is under investigation. We do not have a repro or a fix at this point.
@tdm,
thanks for this, could you please let me know what the bugs for this are?
About time we hade a thread for CM in here!
Thanx and good work @tdm.
Would like to know what Recovery we must use. CWM or can we also use TWRP? What GAPPS - BANKS or PA GAPPS. Also when u use the package with google camera it breaks the camera functionality!
Answered my own question:
TWRP and CWM both work good.
Use PA GAPPS with NO! Google Camera
Cm works pretty well for me. When the Android OS is not draining my battery I can easily hold it out for over 24h, hope it gets fixed soon.
Is there something I can do to help in helping fixing this problem?
Besides I've had it a few times now that when I unlock my screen that my flashlight turns on, very weird, but only had it since today/latest nightly.
Willthor said:
I've had it a few times now that when I unlock my screen that my flashlight turns on, very weird, but only had it since today/latest nightly.
Click to expand...
Click to collapse
That has happened to me many times. The screen gestures are very sensitive. This is a firmware/hardware issue. I believe we plan to use the proximity sensor to mitigate the issue, not sure if that has been committed already or not.
Will CM include this following?
*50 MP Camera Snapper like on ColorOS
*Breathing Notifications (not Blinking Notifications like implemented now on CM).
Also there is a problem when you charge via VOOC Rapid Charger when the device is turned off, the output process on the screen will be an endless loop of Oppo logo->then Charging Indicator->Oppo Logo-> Charging Indicator again and just repeatedly same process.
hulicow said:
Will CM include this following?
*50 MP Camera Snapper like on ColorOS
*Breathing Notifications (not Blinking Notifications like implemented now on CM).
Also there is a problem when you charge via VOOC Rapid Charger when the device is turned off, the output process on the screen will be an endless loop of Oppo logo->then Charging Indicator->Oppo Logo-> Charging Indicator again and just repeatedly same process.
Click to expand...
Click to collapse
I believe Oppo is reserving 50mp for their own ROM.
Don't know about breathing notifications.
I'll try to look into off mode charging.
I'm on 07/15 nightly and the only bug I have is mic on speaker calls.
This is my daily driver now.
Anyone knows of a camera app that can take slow shutter photos like on colorOS camera?(about the only feature I miss from colorOS)
I don't need the 50mp camera thing. But proper hdr and more reliable auto focus would be nice. Up get a lot of out of focus pics on CM compared to ColorOS.
And a fix for the busted HLS streaming in kitKat would be sweet.
One more thing...a solid newb proof fix for the stupid partition layout would be awesome.
Finally...Auto brightness is borked. It's an issue on every ROM I've tried. Really frustrating.
Sent from my X9006 using XDA Premium 4 mobile app
tdm said:
Known Issues
* Find7s: Screen may not wake when phone is hot.
This is apparently an interaction between the thermal throttling code and the video/gpu driver. It has been reproduced and we are working on a fix.
* Find7s: Notification light sometimes misbehaves.
We are working on a fix.
* Find7a: Battery sometimes drains too quickly.
This issue is under investigation. We do not have a repro or a fix at this point.
* Find7a: Mic doesn't work while on speakerphone.
This issue is under investigation. We do not have a repro or a fix at this point.
Click to expand...
Click to collapse
Is the battery draining issue still there?
Juiceboy125 said:
Is the battery draining issue still there?
Click to expand...
Click to collapse
No battery drain for me at least.
But I can't seem to take a proper panorama photo, not even with OnePlus camera.
Other than those few annoying bugs it's the smoothest experience I 've ever had.
gamotom said:
No battery drain for me at least.
But I can't seem to take a proper panorama photo, not even with OnePlus camera.
Other than those few annoying bugs it's the smoothest experience I 've ever had.
Click to expand...
Click to collapse
Well, that's good to hear. I've had this rom for awhile and I just wanted to make sure. But, if you mind me asking, how much screen time do you usually get? I get about 5 and a half average.
Juiceboy125 said:
Well, that's good to hear. I've had this rom for awhile and I just wanted to make sure. But, if you mind me asking, how much screen time do you usually get? I get about 5 and a half average.
Click to expand...
Click to collapse
I get about 1,5 days of use with 4 and a half SOT. But keep in mind that I like my display bright so I've tweaked up autobrightness values.
Has anyone here experienced screen going unresponsive after a bit of browsing on chrome. No issues using Mozilla Firefox though!
Re battery drain: the battery drain happens in standby. Then the battery looses ~1.5-2% per hour, meaning almost 15-20% overnight. It should be only a few instead.
To investigate this, can you guys with no battery drain let us know which modem/firmware you guys are using?
Thanks!
Using the last few nightlies, I've noticed that the gestures no longer work with the screen off. Specifically, double tap to wake and drawing a circle to start the camera.
Not sure if it's something I did on my end or a more common issue
nihir said:
Using the last few nightlies, I've noticed that the gestures no longer work with the screen off. Specifically, double tap to wake and drawing a circle to start the camera.
Not sure if it's something I did on my end or a more common issue
Click to expand...
Click to collapse
double tap 2 wake works with flashing last 3 nightlys!
silasje1 said:
double tap 2 wake works with flashing last 3 nightlys!
Click to expand...
Click to collapse
Hmm. Must be something I've done. Thanks!