Develop Bugs

(Thread Closed)

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.

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

Cyanogenmod 10.1 i747 Bug List (Updated Daily)

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

[Q&A] [ROM][4.4.2 TW] Community Rom

Q&A for [ROM][4.4.2 TW] Community Rom
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

about community rom beta 1.1
I flashed this rom to my note 2 on boostmobile mms didn't send cause I had to change the mmsurl I think but it's working now out the box the devil kept freezing up my phone so I tried increasing the min cpu to 300 so far no freezing no lag or anything but issue I face at the moment is playing music it skips through out the song but not very often
Edit: devil kernel still freezing up phone for some reason

Running your ROM 1.1 Stockish For a week now, couple problems.
Hey, I can't post in the regular forum because I have only 4 posts.
I am coming from Synergy rom, which I used for 1.5 years. I recently switched because I got the rom itch. Synergy is 4.1.2, I have never had anything beyond that. When I flashed, I followed the instructions very closely.
Your ROM is very nice, thanks for all your hard work, it is much appreciated. Here are some things I have found, I have read the entire main thread two times, and followed your instructions to a tee, no missteps and the flash went fine, seems fully working. My 4g icon was wonky, and I flashed the fix in the thread and it worked. WiFi worked as did SMS, no problems. Here are the rest of what I have found:
1) "Unfortunately, Soundalive has stopped." When I pull up any music players. I press "OK" and 3 minutes later it pops up again. After that, it will never pop up again until my device reboots.
2) Pagebuddy does not work. On 4.1.2 when you plugged in headphones, it would bring up the context homescreen and put a headphone icon in the infobar. On this rom (maybe the changed it after 4.1.2) it just adds the icon in the infobar, but does not pull up the Pagebuddy context homescreens.
3)Cannot change lockscreen wallpaper by long pressing the homescreen and selecting wallpapers. However, it does work by selecting "Menubutton>Lock Screen"
4) Every time I rebooted I got the "Deviltools stopped working" until I finally uninstalled devil tools, I guess thats becuase deviltools is not needed with the stockish kernal.
5) Power-Off Charge bug. I flashed the fix, but device still powers up when I plug in the charger. However, I did flash the 4g icon fix and the Power off zips at the same time, without restarting (rebooting recovery) Philz 6.07.9 in between flashing them. Maybe that is why.
I never lost root during the flash, but I flashed SU2.02 after the ROM flash anyhow. Battery life is amazing, I have not had any force closes.
Thanks for this ROM and all your hard work. I read that there will be another update on this ROM. Cant wait. Hope this info helped you in some way.

fleschdnb said:
Hey, I can't post in the regular forum because I have only 4 posts.
I am coming from Synergy rom, which I used for 1.5 years. I recently switched because I got the rom itch. Synergy is 4.1.2, I have never had anything beyond that. When I flashed, I followed the instructions very closely.
Your ROM is very nice, thanks for all your hard work, it is much appreciated. Here are some things I have found, I have read the entire main thread two times, and followed your instructions to a tee, no missteps and the flash went fine, seems fully working. My 4g icon was wonky, and I flashed the fix in the thread and it worked. WiFi worked as did SMS, no problems. Here are the rest of what I have found:
1) "Unfortunately, Soundalive has stopped." When I pull up any music players. I press "OK" and 3 minutes later it pops up again. After that, it will never pop up again until my device reboots.
2) Pagebuddy does not work. On 4.1.2 when you plugged in headphones, it would bring up the context homescreen and put a headphone icon in the infobar. On this rom (maybe the changed it after 4.1.2) it just adds the icon in the infobar, but does not pull up the Pagebuddy context homescreens.
3)Cannot change lockscreen wallpaper by long pressing the homescreen and selecting wallpapers. However, it does work by selecting "Menubutton>Lock Screen"
4) Every time I rebooted I got the "Deviltools stopped working" until I finally uninstalled devil tools, I guess thats becuase deviltools is not needed with the stockish kernal.
5) Power-Off Charge bug. I flashed the fix, but device still powers up when I plug in the charger. However, I did flash the 4g icon fix and the Power off zips at the same time, without restarting (rebooting recovery) Philz 6.07.9 in between flashing them. Maybe that is why.
I never lost root during the flash, but I flashed SU2.02 after the ROM flash anyhow. Battery life is amazing, I have not had any force closes.
Thanks for this ROM and all your hard work. I read that there will be another update on this ROM. Cant wait. Hope this info helped you in some way.
Click to expand...
Click to collapse
1. Sound alive is an issue you can change it in audio settings.
2. The page buddy you are talking about is launcher specific and is not in the s5 launcher.
3. Did not know about that. I usually use gallery for setting wallpaper.
4. Devil tools can not be used with stockish kernel so removal is the correct fix.
5. The power off charge zip is for older versions. You must flash the newest bootloader via odin to fix it.
Hopefully this helps with everything you experienced. Feel free to ask anything you need.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Any help with community rom beta 1.1 can't post in regular forum only have 2 post at the moment
Sent from my SPH-L900 using XDA Free mobile app

Anybody?
Sent from my SPH-L900 using XDA Free mobile app

vipergtsam said:
Anybody?
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
What do you need?
ANDROID--A New Digital Revolution Of Incredible Developers

Seeing if anybody had any issues or fixes for the community rom beta 1.1
Sent from my SPH-L900 using XDA Free mobile app

vipergtsam said:
Seeing if anybody had any issues or fixes for the community rom beta 1.1
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
What type of fixes you looking for?
ANDROID--A New Digital Revolution Of Incredible Developers

I'm having music playback issues it skips sometimes not sure why it's doing it and I get a data error sometimes but not sure if it's because I'm flashed to boost mobile or not but I already figured out why when I first flashed the rom it would freeze cause I had to flash the stockish kernel for it to work correctly but so far I think that's the only problems I'm having at the moment
Sent from my SPH-L900 using XDA Free mobile app

I get music skips also and have yet to find the solution. Data error? Like losing/dropping data?
ANDROID--A New Digital Revolution Of Incredible Developers

Gives an error message when connecting sometimes but it doesn't happen all the time but u notice on Some roms I flash my 3g cuts in and out. And the only way to fix it is a reset or airplane mode to fix it but I think on alpha 3.2 I didn't have the music skipping
Sent from my SPH-L900 using XDA Free mobile app

Yeah dropped data say unable to establish data connection error 106 I think not sure
Sent from my SPH-L900 using XDA Free mobile app
---------- Post added at 07:44 AM ---------- Previous post was at 07:00 AM ----------
Error mip 136
Sent from my SPH-L900 using XDA Free mobile app

Bluetooth connectivity with car
Howdy, y'all!
I just got a new car last night and I'm having issues with connecting it via Bluetooth to my phone. It's properly paired and handles phone calls just fine, but I'm unable to stream audio. The car manufacturer's website confirms that Note II from Verizon and AT&T are compatible phones and are supported as streaming audio devices; my phone is a Sprint Note II, but I cannot think that Sprint's version is much (if any) different in this regard.
So I am wondering if this could potentially be a ROM issue, which is why I'm asking here. I'm using Alpha 3.2+. I use a Motorola Bluetooth headset when I'm running and have no problems with it. So I know that Bluetooth audio does indeed work with this ROM.
Any and all words of wisdom will be greatly appreciated. I will be locked in a padded room if I need to listen to FM radio any longer.

Cancel that request. I found the problem.
My last car supported Bluetooth telephony, but not audio. I had to use an audio patch cable from the headphone jack to the aux input of the car's audio system to use my phone as a media player. This caused a problem, I found, because when I'm playing music from my phone in my car (and that's ALWAYS), it superceded the car's Bluetooth capabilities for phone calls. If I received a call, the other party couldn't hear me because the phone was attempting to use a non-existant microphone instead of the car's Bluetooth microphone.
The solution was an application called SoundAbout. It gives you better control of your Android device's routing of audio output and microphone input. Worked perfectly.
What I had forgotten is that when I'm using my Bluetooth headphones when I'm out for a run, I had to shut SoundAbout down. Music would simply play from the phone's speaker instead of routing it via Bluetooth. So that's all I needed to do - shut down SoundAbout, and now my Benz is connecting with my phone without issue.
It would appear that I no longer even need SoundAbout.

Testing a possible music skipping fix...
ianmb said:
I get music skips also and have yet to find the solution. Data error? Like losing/dropping data?
ANDROID--A New Digital Revolution Of Incredible Developers
Click to expand...
Click to collapse
I have been pulling my hair out for a fix and I am currently trying a fix a found in my many google searches...
The gist of it is to set the governor to ondemand and that should fix the audio skipping. It has something to do with phone going into deep sleep and the wake lock not functioning properly. I am doing this now and it hasn't skipped for about an hour now...
Could anyone else give this "fix" a whirl?

runninglaps said:
I have been pulling my hair out for a fix and I am currently trying a fix a found in my many google searches...
The gist of it is to set the governor to ondemand and that should fix the audio skipping. It has something to do with phone going into deep sleep and the wake lock not functioning properly. I am doing this now and it hasn't skipped for about an hour now...
Could anyone else give this "fix" a whirl?
Click to expand...
Click to collapse
http://android.aokforums.com/viewtopic.php?t=399
Nameless and others are up here temporarily. I'll do beanstalk on both.

stuttering music
Great rom overall with very few bugs that I can live with, except for this one. I experience stuttering while playing mp3 using either the music app or play music. The strange thing about this bug is that the stuttering starts once the screen goes off and stops once the screen comes on and it will never stutter as long as the screen stays on. I didn't add any mods or tweaked anything after installing the rom. Is there any fix for this bug? Thanks and great work on the rom.

I just upgraded from Community Alpha 3.2+ to Beta 1.1 with the stock kernel. Everything works perfectly, JL. Your wonderful work and commitment to the GN2 community will be sorely missed.
One very minor issue, though. My Font size (Settings, My Device, Font size) is set to Tiny. Even that's a bit too big for my tastes, but I can live with it. But some applications - most notably, S Planner and the Internet browser - seem to have a mind of their own with regard to font size. The first picture is of the browser. I'd prefer the address text to be smaller, mostly for the reason that I'd be able to see more of it. The second is of S Planner and pretty much speaks for itself. Everything there is too big. The numbers don't even fit into the calendar squares.
I downloaded and installed a build.prop editor and tried bumping the lcd.density down to 240 from its stock setting of 320. Unfortunately, it carried with it the unwanted side-effect of cramming everything to the top of the screen, leaving the bottom 30% or so completely unused.
Any way to modify this?

How to update profile/prl? Thank you!

[FIX?][E980] Android Wear device with CM12.1's bluetooth problems...

I've found a possible "fix" for the bluetooth problem... (very frequent disconnects from Android Wear and other devices, "Bluetooth Share" crashes, etc) but I need testers.
Attached is a zip you can flash from recovery.
After trying a bunch of stuff to get bluetooth to work properly with no luck, I decided to just rip the "/system/etc/bluetooth" folder off of an official LG 5.0.2 ROM and overwrite the existing bluetooth files in CM12.1. It seems to have worked. My bluetooth hasn't crashed once since, and Android Wear has been happy and synced all day. I'm running it on my E980 with the June 1 nightly build of CM12.1 (which also supposedly has some bt fixes... but bt still crashed on it until I flashed this).
New version July 6, 2015: btpatchv5.zip
v5 is based on bt from the latest (0704) CM12.1 nightly and works very well for me;
v4 is based on the official LG 5.0 ROM and IS tested.
Changes:
>> Bundled in the Ao-Shi app (not my work, all credit to Daniel Baucom for this nifty little tool)
>> Added 3 bluetooth binary files to /system/xbin in an attempt to quell the "bluesleep" wakelock and get some deep sleep.
Let me know how it works for you... grab the download below...
*Regarding the Ao-Shi app that I've included...
If you get an occasional BT crash, fire up the Ao-shi app. Tap "Kill Bluetooth" two or three times (not just once; once doesn't work). Then, click "Revive Bluetooth". For me this usually gets BT working again without a reboot. Again, thank you to Daniel Baucom for this little gem. It even has widgets you can add to your homescreen for faster action.

Thx for sharing this information.I've got another question, aren't you having problems using 'oké googe' on your wear?. I've seems to keeping having problems on my phone,using 'oké google'

stipvroegop said:
Thx for sharing this information.I've got another question, aren't you having problems using 'oké googe' on your wear?. I've seems to keeping having problems on my phone,using 'oké google'
Click to expand...
Click to collapse
Yes... when BT partially craps out, "OK Google" gets wonky. Usually I get a total BT crash shortly after.
I have been heavily experimenting, and I might be on the trail of a true fix, but I need to test more before posting it. Keep your fingers crossed.

stipvroegop said:
Thx for sharing this information.I've got another question, aren't you having problems using 'oké googe' on your wear?. I've seems to keeping having problems on my phone,using 'oké google'
Click to expand...
Click to collapse
I've uploaded a small patch, give it a shot and see if it helps you. It has worked great for me. See the OP for the file.

Mpsantiago, where can I find the patch, and how does it work? Tnx for sharing your solution

stipvroegop said:
Mpsantiago, where can I find the patch, and how does it work? Tnx for sharing your solution
Click to expand...
Click to collapse
It's up above attached to the first post- btpatchv2.zip
All it does is transplant the bluetooth files from the official LG 5.0.2 E9XX ROM into CM12.1.
Flash it from recovery and enjoy. You'll likely have to re-flash it after any nightly upgrade (until the problem gets fixed upstream).

Ok, I've tested the patch with both my Moto360 and my BT speakers- everything seems good.

mpsantiago said:
Ok, I've tested the patch with both my Moto360 and my BT speakers- everything seems good.
Click to expand...
Click to collapse
Still good with BT, do you still have screen flickering?

dpalmer76 said:
Still good with BT, do you still have screen flickering?
Click to expand...
Click to collapse
No, screen flickering is a pretty easy fix compared to BT:
Option #1: Turn off Hardware Overlays every time you boot your device
Option #2: Install the xposed module "NoMoreOverlay"
Option #3: Modify build.prop file, change the line "persist.hwc.mdpcomp.enable" from true to false

Do I only have to flash the zip for BT to stay synced? No need to change anything else?

DanC7766 said:
Do I only have to flash the zip for BT to stay synced? No need to change anything else?
Click to expand...
Click to collapse
Just flash, that's it.
So far, BT has only crashed twice since I first started testing it, and it happened when I was goofing with it pairing different stuff- not during normal use. Both times I was able to revive it without rebooting using this app: https://play.google.com/store/apps/details?id=co.loudbit.ao_shi

I've noticed very little deep sleep while using this solution, possibly related to "bluesleep" wakelock- I'm investigating this to see if I can fix it.
EDIT: I've added a new download to the OP above; not sure if it will fix bluesleep wakelocks but I'm hopeful... I'll be testing it tomorrow... off to bed now for me!

Update
mpsantiago said:
I've noticed very little deep sleep while using this solution, possibly related to "bluesleep" wakelock- I'm investigating this to see if I can fix it.
EDIT: I've added a new download to the OP above; not sure if it will fix bluesleep wakelocks but I'm hopeful... I'll be testing it tomorrow... off to bed now for me!
Click to expand...
Click to collapse
How is this fix working to date?

dpalmer76 said:
How is this fix working to date?
Click to expand...
Click to collapse
So far, so good.
I still get an occasional BT crash, but it's maybe one or two a day instead of one every 15 minutes. I'm actually testing yet another revision to the patch with an additional tweak and another LG BT library file moved over... if it is stable I'll post it next.

Tested the latest (june 4th) version and works so far. I did notice a decrease in battery life afterwards tho, significant vs the non-working bluetooth.

This patch may no longer be needed. I flashed 20150625-NIGHTLY this morning (without patching afterwards) and so far bluetooth has been flawless.

mpsantiago said:
This patch may no longer be needed. I flashed 20150625-NIGHTLY this morning (without patching afterwards) and so far bluetooth has been flawless.
Click to expand...
Click to collapse
sim card ok?

That day I was in a rush... I basically flashed the nightly and threw the phone in my pocket. My watch got all my notification alerts no problem all morning- it wasn't until lunch time that I looked at my phone and noticed the SIM problem.
Hopefully they'll have it sorted soon, though it's still not with the latest build. If it's not fixed by the end of the week I'll probably look into ripping the BT stuff out of the latest nightly and updating this patch with it.

mpsantiago said:
That day I was in a rush... I basically flashed the nightly and threw the phone in my pocket. My watch got all my notification alerts no problem all morning- it wasn't until lunch time that I looked at my phone and noticed the SIM problem.
Hopefully they'll have it sorted soon, though it's still not with the latest build. If it's not fixed by the end of the week I'll probably look into ripping the BT stuff out of the latest nightly and updating this patch with it.
Click to expand...
Click to collapse
Are you using this with blisspop? Wakelocks still?
Sent from my LG-E980 using Tapatalk

UPDATE:
Since the CM12.1 nightly builds still have a borked SIM card (but seemingly working BT), I replaced the bluetooth guts in V5 of this patch with the ones from the latest 12.1 build instead of what I was using before (the official LG 5.0 build). I have only tested it for a few hours, but it seems solid. Have NOT checked for wakelocks or battery drain. Flash at own risk.
I've omitted the Ao-Shi app; you can install it from Play Store if you want. Alternatively, if BT ever crashes you can manually revive it without rebooting:
Settings > Apps > All > Bluetooth Share > FORCE CLOSE then CLEAR DATA; turn Bluetooth back on and it should be fine.
dpalmer76 said:
Are you using this with blisspop? Wakelocks still?
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
Haven't tried with Blisspop, only with cm12.1 nightlies. It should work on any CM12.1 based ROM though. I get decent deep sleep with it. YMMV.