[TESTING] .39 Kernel **NEW** - Touch Pro2, Tilt 2 Android Development

Hey all,
This is a shiny new test kernel from none other than WisTilt2 and jonpry.
***NOTE***
The new acoustic code is in this kernel. If you're not running a system image that supports the new acoustic code, you will lose all sounds! This includes in call audio, speakerphone, everything!!
***********
They have been working hard on getting a new codebase out, and this is a result of their work.
Note - things are going to be broken in this kernel. Most things from .27 will work, the second post will serve as a list of confirmed broken things & workarounds if they exist. Initially I'd like to see what people report, so let me know! If you report a issue that is listed in the next post, put your flamesuit on, you're asking for it.
This kernel is RHOD only. It may boot other devices, but they are untested. Run at your own risk!
This kernel also requires some changes to haret & the startup.txt, which I will outline below.
Steps:
1. Download the alternate haret version (attached). I have found that this alternate version will boot other 'normal' kernels, but you must use this haret to boot this kernel.
2. Add this line to your startup.txt (I added it after the set initrd line):
Code:
set initrd_offset 0x00a00000
3. Download the kernel from the .39 (autobuild service), replace as you normally would, and boot!

Broken Things​
The additional modules are now provided, however wifi is still broken...
adb now works, but the usual indicator in the notification bar is missing...
BT obviously won't work, as the new audio routing code is not in this kernel. It has the standard audio routing from the autobuild.
user.conf files don't seem to be getting processed... Help on this would be appreciated, I'm honestly baffled that the kernel would affect this, but it seems to be.
Overclocking hasn't worked for anyone as of yet. WisTilt2 was thinking the statement is ignored currently.
End call seems to be failing. It's related to the new zoombar enhancements unfortunately... **These are going to be temporarily pulled until the issue is resolved**
Booting on the new HaRET may fail completely. See this post!
Wifi does not work. There's a fix! Thanks to detule & jonpry for it!

DEVELOPERS ONLY​
Now that's out of the way...
There is a public git repo for .39, assuming you want to see the action live!

no wifi no camera...how is this better than other versions? just curious

prexzone said:
no wifi no camera...how is this better than other versions? just curious
Click to expand...
Click to collapse
Newer code base, so presumably old bugs are fixed, new bugs are present.

prexzone said:
no wifi no camera...how is this better than other versions? just curious
Click to expand...
Click to collapse
The .39 kernel is the future, off which all future updates will presumably be based. However, work has just started on it, which is why it's got a lot broken still.
The .27 kernel which we've been using to date is a hacked together mess that is woefully outdated. Froyo and Gingerbread were never designed to work with this old kernel, and as a result, hacks had to be hacked together, and the whole thing is creaky and hard to improve upon.
I personally was looking at developing a driver for the zoom bar to emulate multitouch pinch-to-zoom for Rhodium/Topaz. However, multitouch wasn't added to the Linux kernel until I think .31, so I gave that up for now.
I was also looking at switching our file systems to the much faster ext4 filesystem, but support was not added for that until .28.
So it may not be better now, but it's pretty much our only hope for progress. There are also crashing and other stability bugs that were fixed in newer kernels, that we simply don't have. I also understand that the .39 kernel is faster.

Thank you all! First impressions with my RHOD100/AUO with FRX06:
Instant sleep and wakeup! It seems that the intermediate sleep state led (blinking green) is not available in this kernel, so amber=awake and green=sleeping. Trying to wake up the phone while freezing applications (screen off, amber -- former blinking green) brings up the backlight but not the panel, touching the screen brings up the panel. This is 100% reproducable.
Data works great with hyc's ril2.
In-call audio did not work correctly, but this was also the same with the .27 kernels, a problem which seems to be specific to my phone. Only JB's audio routing code solved this problem completely, I can only hope that this will be integrated sometime in the future.
However, FB and overall android interface did not get faster (which was discussed in IRC). I can say that it is just about the same as in .27. Don't know exactly if the android interface is hardware accelerated, I am going to try the updated GLES library.

prexzone said:
no wifi no camera...how is this better than other versions? just curious
Click to expand...
Click to collapse
Cam does work (sorry about that!), and wifi is being worked on. With modules I've heard it scans, but doesn't connect.
xanathar said:
Thank you all! First impressions with my RHOD100/AUO with FRX06:
Instant sleep and wakeup! It seems that the intermediate sleep state led (blinking green) is not available in this kernel, so amber=awake and green=sleeping. Trying to wake up the phone while freezing applications (screen off, amber -- former blinking green) brings up the backlight but not the panel, touching the screen brings up the panel. This is 100% reproducable.
Data works great with hyc's ril2.
In-call audio did not work correctly, but this was also the same with the .27 kernels, a problem which seems to be specific to my phone. Only JB's audio routing code solved this problem completely, I can only hope that this will be integrated sometime in the future.
However, FB and overall android interface did not get faster (which was discussed in IRC). I can say that it is just about the same as in .27. Don't know exactly if the android interface is hardware accelerated, I am going to try the updated GLES library.
Click to expand...
Click to collapse
Thanks for the feedback! Interesting that you didn't feel any speed boost. I've been having some oddities with severe slowdowns, but when those aren't happening it seems very fast .
You're right about the rest too, I can confirm that I've had some issues where it won't wake properly when the LED is orange - and you're also right that there's not intermediate blinking state, just solid orange or solid green. I need to flesh out the first post .

when boot up, windows found an unknown device "ethernet gadget", where can I found this driver
When SMS in , phone auto reboot

muziling said:
when boot up, windows found an unknown device "ethernet gadget", where can I found this driver
When SMS in , phone auto reboot
Click to expand...
Click to collapse
I said adb doesn't work... I guess I should refine that and say "nothing USB works".
No clue on your SMS issue, sounds wacky. Post logs.

arrrghhh said:
I said adb doesn't work... I guess I should refine that and say "nothing USB works".
No clue on your SMS issue, sounds wacky. Post logs.
Click to expand...
Click to collapse
not USB works ,how to use dmesg to get logs?
May be wifi is the only way
Command in file /sdcard/conf/froyo.user.conf seems not be executed, I add "rm -f /sdcard/fsck*.rec", file not deleted, switch back to .27 kernel , work normal.

muziling said:
not USB works ,how to use dmesg to get logs?
May be wifi is the only way
Click to expand...
Click to collapse
But don't forget wifi doesn't work

I noticed a decent speed up and no stability problems with my short testing. Will do some more testing tomorrow.

Took it out for a little spin on my semi-retired RHOD400. Keyboard repeat bug is still there it seems. I'll post a dmesg dump if it's useful.
http://db.tt/YP4kMo5
-- Starfox

Test in my RHOD100 with my daily working CWM1.8 plus froyo blue :
Sleep and Wakeup works well just like WisTilt2's 4/15 test kernel.
EDGE works.
Still have no incall but outcall works well.
Also i didn't feel faster since i still get some lag when go into drawer of adw, but it is good to see a .39 working in our phone!
Looking forward to wifi!

muziling said:
not USB works ,how to use dmesg to get logs?
May be wifi is the only way
Command in file /sdcard/conf/froyo.user.conf seems not be executed, I add "rm -f /sdcard/fsck*.rec", file not deleted, switch back to .27 kernel , work normal.
Click to expand...
Click to collapse
Hrm, that's interesting the kernel would affect whether or not that file is processed...
Anyways, you can always just pull up a command line and pull logs there, dump 'em to the SD card. C'mon, this thread kinda assumes you know what you're doing. If you don't, you probably shouldn't be mucking with such an advanced things... Thanks!

hmmm phone does not reboot when receiving a sms but it just goes to sleep
else booting is way faster then the previous kernels.
data connection works . wifi idd not.
nothing else noticed yet

Do I need the modules for bluetooth? My BT does not start.

the new...
...kernel .39 killed my wifi, i now get an error

latinohot said:
...kernel .39 killed my wifi, i now get an error
Click to expand...
Click to collapse
Um, did you bother to read the second post (known issues) at all?

Related

[TESTING] Updated 5/14/11 New Kernel - Temp Test - SOD Fix!

Hey kiddos.
WisTilt2 wanted to get some more testers for this kernel, so please download and put it thru the ringer!
This is RHOD ONLY! Please, don't ask if any other devices will work as currently it probably will not! Use at your own risk!
UPDATE 5/14/11 Temp test, SOD prevention!
So the newest autobuild has been plagued with an odd SOD condition. WisTilt2 thinks he traced the issue, and he wants people to run this kernel to see if it's SOD-free (compared to the newest autobuild).
WisTilt2 said:
Current git tree, my pm/fb patch with the proc_comm test. Need to see if anyone gets SOD's. Should have very fast sleep and wakes still, leds are like autobuild also.
Click to expand...
Click to collapse
Let me know guys, thanks!
(In this case, I will leave the old kernel - but do please test this new kernel against the autobuild, see if the SOD's disappear...)
Archive:
UPDATE 4/15/11 SCBS integration
This is the new battery meter code that jonpry has been working hard on. To get the full benefits, you'll need an APK and a new rootfs.img. Please see jonpry's thread on PPCG for more information.
So download this kernel, grab the apk and rootfs from jonpry's thread (don't grab the kernel in his thread!) and follow his instructions if you want to give SCBS a spin. I've already noticed a difference, and I haven't generated a model yet. Rule of thumb with generating the model/algo is the more data the better - so go thru a few charge cycles, some heavy use, some sleep - the more usage the better the algo! Enjoy!
Just to be clear - this new kernel only has the updated SCBS code. Nothing else has been changed since the previous 4/4 test kernel.
UPDATE 4/4/11 Minor fixes...
Just an update to the previous kernel, stylus should be fixed (meaning it will boot into landscape again, fix needs to happen in userland) along with the button lights (when keyboard is open, button lights do not light now). Nothing major!
UPDATE 4/2/11 *Hopefully* failed panel wakes are gone!
WisTilt2 said he found and irq that was set wrong... and it was related to the touchscreen - hence the reason touching the screen wakes it! So this kernel seems to wake very nicely for me - how does it for you?
UPDATE 3/31/11
WisTilt2 said:
This fixes the button lights so they go out when you open kbd and they turn on when you close kbd just like winmo. Also fixed the portrait/landscape unlock screen so at boot it should be in portrait so you don't have to do the back arrow trick to switch it.
Click to expand...
Click to collapse
Update: On the button lights, when the keyboard is open - the button lights will act odd... seems the kernel is torn, it flips them on and then quickly back off .
UPDATE 3/30/11 Button lights, PM Rework, kbd flicker/repeat key, and failed wake fixes!!
WisTilt2 has been trying to clean up his code so he can commit - this is working towards that goal. This new kernel has fixes for the kbd flicker/repeat ("stuck") key bug, the failed panel wakes have also disappeared for me - the panel doesn't always wake instantly, but I've never had to touch the screen to get it to wake - it's ALWAYS come up! Let me know, YMMV as always! Oh and yes, the 4-button light LEDs should now work perfectly as well .
Update - ok, might've jumped the gun on the repeat letter thing - but it does seem better... Just not perfect yet .
RHOD100/AUO users - really need to know if this new kernel breaks your phones! I also would like to know if the SoD issue is actually squashed. I haven't had an SoD in forever, so to those who have recently, let me know!
Perhaps also good to note, is the sleep LED is changed in this one. Initially it will blink green to show that processes are going down and it's trying to sleep (a wakelock of some sort is present in other words). Solid green is full, deep sleep. So you should see blinking green when charging, with GPS enabled etc. You won't get a solid green LED until it's completely sleeping, as usual.
In addition, WisTilt2 has changed the boot screen. Hopefully it'll boot faster, but you'll see a lot less flying text - don't panic! It's normal .
Enjoy! Please feel free to report how this kernel works, so we can get the changes committed!
**Notice**
These kernels are meant for testing purposes - there is no public GIT repo that this kernel code resides on, however the majority of the changes get pushed to the master GIT repo for XDAndroid. The ones that don't didn't work or were simply in place for testing - again the changes that are being tested here are eventually destined for autobuild. Please contact me if you have any technical questions related to this kernel, I will do my best to explain the changes - if you want specifics, I can put you in contact with WisTilt2, the man in charge of pumping out these test kernels. Feedback is not only welcomed but encouraged, please reply to this thread with it!
Downloading and testing now...
UPDATE: Sorry this is taking so long but strangely I've had 5 boots in a row that have resulted in that slow, 100% cpu issue...I've never had that many in a row but can't say that it's the test kernel...I'll keep trying...btw is this built off of the 1245 kernel or an older one?
Yep, testing now.
Incidentally, with both this and 1245 I cannot seem to boot my neopeek system. They fail to see the root partition at /dev/mmcblk0p2 and either hang or reset.
The 1242 kernel still works fine . Weird
Anyway, I will test this out with my XDAndroid setup.
Cheers!
Sorry to be an echo of the others... before I test it, is it built from the 1245 kernel?
1245 seems to be working sweet for me so far....
This should have all the newest commits + WisTilt2's modifications. He said all but bzo's latest commits... I guess git died on him. I'll upload a new one if he builds another.
First impressions on Rhod400:
Speakerphone volume is still fairly low for my taste...when the volume setting is at 1/3 it is barely audible...at full I have to hold it fairly close to hear all words clearly...
Also there is a lot of background "noise" when the external speaker is on...sounds like white noise or static...
Otherwise everything is running smooth...
New Test Kernel (WisTilt2) - 2nd edition - Rhodiums Only
Info: WisTilt2 has another test kernel he'd like some helpful volunteers with rhodiums to test. This test kernel is based on the previous test kernel posted by Arrrghhh earlier in this thread. In addition, it adds bzo's overclock with pm.sleep_mode=1 patch for even better battery life when you're overclocking. So set pm.sleep_mode=1 in your startup.txt when trying this, regardless of whether or not you're overclocking. It also adjusts the volume level of the speakerphone mic to make it easier to hear. Please report any problems you encounter with these kernels, including but not limited, to battery life and speakerphone. Please also mention your rhodium model. They may not all behave the same. Thanks.
WARNING: This kernel is for RHODIUMS only. This kernel could potentially -BRICK- a non-rhodium. So only try this out if you have a rhodium.
Wifi:There is a possibility that rhodium wifi is broken in the stripped version. (WisTilt2 and I use different toolchains. He built it, I stripped it to reduce its size. Our toolchains should theoretically be interoperable, but the resulting modules file is half the usual size. So I'm not entirely sure about that.) If rhodium wifi doesn't work with the stripped version of the modules file, please give the fatter non-stripped version a try. Either way wifi isn't what we're testing here.
Rhodium Only - Kernel & Stripped Modules File(1.94MB version):
wistilt2-kernel-pack-stripped.zip
Rhodium Only - Kernel & Non-Stripped Modules File ("fatter" 8.69MB version, grab this only if you use wifi and the stripped version doesn't work):
wistilt2-kernel-pack.zip
@pdawg17 the static is expected atm, but how loud is it compared to the actual call. same volume or pretty quiet?
People that post here, make sure to specify which model you have, eg. 100, 300. If you don't know you likely shouldn't be testing experimental kernels.
F22 said:
Info: WisTilt2 has another test kernel he'd like some helpful volunteers with rhodium owners to test. This test kernel is based on the previous test kernel posted by Arrrghhh earlier in this thread. In addition, it adds bzo's overclock with pm.mode_sleep=1 patch for even better battery life when you're overclocking. So set pm.mode_sleep=1 in your startup.txt when trying this, regardless of whether or not you're overclocking. It also adjusts the volume level of the speakerphone mic to make it easier to hear. Please report any problems you encounter with these kernels, including but not limited, to battery life and speakerphone. Thanks.
WARNING: This kernel is for RHODIUMS ONLY. This kernel could potentially -BRICK- a non-rhodium. So only try this out if you have a rhodium.
Wifi:There is a possibility that rhodium wifi is broken in the stripped version. (WisTilt2 and I use different toolchains. He built it, I stripped it to reduce its size. Our toolchains should theoretically be interoperable, but the resulting modules file is half the usual size. So I'm not entirely sure about that.) If rhodium wifi doesn't work with the stripped version of the modules file, please give the fatter non-stripped version a try. Either way wifi isn't what we're testing here.
Rhodium Only - Kernel & Stripped Modules File(1.94MB version):
wistilt2-kernel-pack-stripped.zip
Rhodium Only - Kernel & Non-Stripped Modules File ("fatter" 8.69MB version, grab this only if you use wifi and the stripped version doesn't work):
wistilt2-kernel-pack.zip
Click to expand...
Click to collapse
Hey just to report back both kernels do not load it keeps saying that the sd card didn't mount then when I go back to an old kernel it works perfectly so i didn't even get a chance to test the new kernel. Hope it can get fixed so I can start testing for you guys. Thanks and sorry about the bad news
I have RHOD100_de with pm.sleep=1
Well i can say that:
1) The screen is not coming back from stand-by, it remains black while i will nor swipe the unlock pattern (from left to right). It was so on the first stages of kernel with screen turn off feature. UPD: actually screen backlight turns on, but screen doesn’t come back from black...
2) WiFI shows error
3) The in-call/speakerphone volume seems OK
4) Auto backlight function seems to be OK, since it was OK in other kernels.
5) unfortunately currently I don't have enough time to check how battery usage is, i will try to post later.
If You say me on what exactly to focus i'll give more info
So far testing the Rhod kernel:
1) Wifi shows "error" with stripped or "fat" module...I have never had a problem with this on past kernels...
2) In-call volume is great...speakerphone volume is still low to me...the "noise" is lower/better than before but it was be nice for the voice to be a bit higher as in WM it is definitely louder...
3) A couple of times when I woke the phone from sleep the screen was very dim and did not adjust...it was like the auto backlight did not kick in...
4) Sleep mode=1 with my overclock is fine so far...it has woken up all 20 times or so...
5) Occasionally when waking the phone everything is slow/stuttery for a few minutes afterwards...this has occurred the last 3 kernels or so...
I'll keep it running today to see how battery life is...
Otherwise it is great! I'll keep testing!
UPDATE: Just realized my data at some point stopped working too...turning airplane mode on and then off fixed it...
UPDATE 2: Weird...once I did the airplane mode trick my wifi now works AND immediately the stuttering/slowness disappeared and my smooth phone is back!
Rhod400 (Sprint TP2)
Rhod 400. LED is not solid green but occasionally will turn on/off. SOD occured after sleeping for 30 minutes. Speakerphone is much louder but still has static
pdawg17 said:
Downloading and testing now...
UPDATE: Sorry this is taking so long but strangely I've had 5 boots in a row that have resulted in that slow, 100% cpu issue...I've never had that many in a row but can't say that it's the test kernel...I'll keep trying...btw is this built off of the 1245 kernel or an older one?
Click to expand...
Click to collapse
This isn't built off of 1245. I believe it's built off of 1238 with WisTilt2's modifications on top as well as some of the newer patches like 1239 and 1241 added into the mix. I don't believe commits 1243-1245 made it into this test kernel.
Rhodium 100 Panel Issue
solevi said:
I have RHOD100_de with pm.sleep=1
Well i can say that:
1) The screen is not coming back from stand-by, it remains black while i will nor swipe the unlock pattern (from left to right). It was so on the first stages of kernel with screen turn off feature. UPD: actually screen backlight turns on, but screen doesn’t come back from black...
Click to expand...
Click to collapse
Most rhodiums have an EID panel. Some rhodium 100's however have an AUO panel instead. The kernel doesn't properly initialize the AUO panel yet, it only worked before because Win Mo set it up and the kernel never fully turned it off. So now that the kernel is turning it off some rhod 100's aren't waking up. This issue isn't limited to just this test kernel, but exists in all recent kernels. ACL is working on getting the init info for your panel into the kernel. Hopefully it's just the two panels. Should there be a 3rd panel out there it will still be screwed until we can get a volunteer to grab the panel init info from it via haretconsole for us.
2) WiFI shows error
Click to expand...
Click to collapse
Both the stripped and non-stripped versions of the modules file? And are you getting the same stuttery slowness that pdawg17 is experiencing?
3) The in-call/speakerphone volume seems OK
Click to expand...
Click to collapse
Good. That was one of the new things in this test kernel.
4) Auto backlight function seems to be OK, since it was OK in other kernels.
Click to expand...
Click to collapse
Good.
5) unfortunately currently I don't have enough time to check how battery usage is, i will try to post later.
Click to expand...
Click to collapse
Get back to us on that one when you can. That's one of the new modifications that WisTilt2 is specifically testing in this kernel.
If You say me on what exactly to focus i'll give more info
Click to expand...
Click to collapse
Battery.
SD Card Issue
thomas d said:
Hey just to report back both kernels do not load it keeps saying that the sd card didn't mount then when I go back to an old kernel it works perfectly so i didn't even get a chance to test the new kernel. Hope it can get fixed so I can start testing for you guys. Thanks and sorry about the bad news
Click to expand...
Click to collapse
Back up your data via Titanium Backup (downloadable from the market) and try renaming your data.img file to something else. Android will recreate it the next time you boot and hopefully your sd card issue will be gone.
Stuttery Slowness
pdawg17 said:
So far testing the Rhod kernel:
1) Wifi shows "error" with stripped or "fat" module...I have never had a problem with this on past kernels...
2) In-call volume is great...speakerphone volume is still low to me...the "noise" is lower/better than before but it was be nice for the voice to be a bit higher as in WM it is definitely louder...
3) A couple of times when I woke the phone from sleep the screen was very dim and did not adjust...it was like the auto backlight did not kick in...
4) Sleep mode=1 with my overclock is fine so far...it has woken up all 20 times or so...
5) Occasionally when waking the phone everything is slow/stuttery for a few minutes afterwards...this has occurred the last 3 kernels or so...
I'll keep it running today to see how battery life is...
Otherwise it is great! I'll keep testing!
UPDATE: Just realized my data at some point stopped working too...turning airplane mode on and then off fixed it...
UPDATE 2: Weird...once I did the airplane mode trick my wifi now works AND immediately the stuttering/slowness disappeared and my smooth phone is back!
Rhod400 (Sprint TP2)
Click to expand...
Click to collapse
The stuttering slowness means system_server was running amok on your handset. When it goes berserk, it puts a stranglehold on the cpu, preventing wifi and other things from getting their fair share of resources. This issue has existed for months, but it used to be much less common. It appears to be occurring far more frequently in newer kernels with the latest system.ext2.
Thanks for the feedback!
Sleep of Death
vnes1984 said:
Rhod 400. LED is not solid green but occasionally will turn on/off. SOD occured after sleeping for 30 minutes. Speakerphone is much louder but still has static
Click to expand...
Click to collapse
Has the SOD occurred again since? Have you experienced this problem with any other recent kernels? Has anyone else experienced Sleep of Death with this kernel? (Not counting rhod100 users whose panels won't reinitialize after going to sleep. That's a separate issue.)
LOL, thanks for takin care of mah thread F22
Not much for me to do there tho
F22 said:
until we can get a volunteer to grab the panel init info from it via haretconsole for us.
Click to expand...
Click to collapse
Already uploaded to ppcgeeks.
And I did some more testing:
1) I've renamed data.img file and commented lines in froyo.user.conf (from tiad8's 3D Package post) to have a clean system.
2) Tried with stripped modules: Wifi shows error.
3) Deleted this newly created data.img file and tried to boot with not stripped kernel modules: Wifi seems OK.
As told pdawg17 screen lights up, then dim out. Sometimes it is working OK. This behavior exist either with autobacklight enabled or disabled.
Still not enough time to check battery :-(
F22 said:
Has the SOD occurred again since? Have you experienced this problem with any other recent kernels? Has anyone else experienced Sleep of Death with this kernel? (Not counting rhod100 users whose panels won't reinitialize after going to sleep. That's a separate issue.)
Click to expand...
Click to collapse
I haven't experienced this with other kernals. well for awhile. I've since updated to the most recent kernal after the SOD. (working very well btw) It seemed the test kernal had very inaccurate battery readings compared to other kernals. I would hit the power on button to wake and the screen would flicker slightly, it wasn't until I swiped my thumb across the bottom of the screen that the phone would wake up. Once I left it sleeping for about an hour and tried everything to wake it up but no such luck. (rhod400)

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

Hello all,
I have a very odd problem that I'm hoping others may have run into and solved. When I'm playing audio over the A2DP data path to my car, the audio randomly will drop for half a second, then gradually comes back to full volume over perhaps a second of time. Speaking like a programmer, it's almost like something mutes the audio and then slides the volume up in a loop or something.
This problem did not occur on Bombaridier and the older Synergy Kernel, however it is happening with the newer kernel on Juggernaut v5, Paradox and SlickMOD, leading me to believe something in the kernel or newer system binaries might be causing it. This behavior happens in Pandora, Amazon MP3 and also the stock Music app.
Thinking that maybe a stray notification was the problem, I've tried disabling notifications in all of the apps I know of that notify, I've also tried switching the phone into vibrate and finally into full-silent, but it does not seem to affect the behavior. I have found no likely cause. I wish I was able to log alsa changes; maybe a script running constantly with something like:
Code:
while (true)
do cat /proc/alsa/some_alsa_status_entry >> /tmp/alsalog
sleep 1
done
Does anyone else have any ideas as to what this might be? It's really annoying!
Thanks in advance,
Pete
Dirty Pete said:
Hello all,
I have a very odd problem that I'm hoping others may have run into and solved. When I'm playing audio over the A2DP data path to my car, the audio randomly will drop for half a second, then gradually comes back to full volume over perhaps a second of time. Speaking like a programmer, it's almost like something mutes the audio and then slides the volume up in a loop or something.
This problem did not occur on Bombaridier and the older Synergy Kernel, however it is happening with the newer kernel on Juggernaut v5, Paradox and SlickMOD, leading me to believe something in the kernel or newer system binaries might be causing it. This behavior happens in Pandora, Amazon MP3 and also the stock Music app.
Thinking that maybe a stray notification was the problem, I've tried disabling notifications in all of the apps I know of that notify, I've also tried switching the phone into vibrate and finally into full-silent, but it does not seem to affect the behavior. I have found no likely cause. I wish I was able to log alsa changes; maybe a script running constantly with something like:
Code:
while (true)
do cat /proc/alsa/some_alsa_status_entry >> /tmp/alsalog
sleep 1
done
Does anyone else have any ideas as to what this might be? It's really annoying!
Thanks in advance,
Pete
Click to expand...
Click to collapse
I second this as an issue that I have run across quite often. I use this BT for music in my car on a daily basis. I usually get a .5 second audio drop out at lest twice each song. Seems to be about every 2 minutes if I would have to guess.
I have just learned to get used to it but it would be fantastic if this could be resolved.
I've also tried fiddling with the CPU governor ant the IO scheduler, but to no avail. Im wondering if there is a bug in the bluetooth module introduced in the latest kernel.
Sent from my SGH-T989 using xda premium
Works great for me and I've tried just about every rom and kernel over clocked and under clocked. I had it skip once before, I rebooted and it was fine.
Sent from my SGH-T989 using Tapatalk
I'll give this a bump, because I have the exact same problem. Never had this problem on my Blackberry (sad), in the same car. OP has described the issue better than I could have.
scotty-dont said:
I'll give this a bump, because I have the exact same problem. Never had this problem on my Blackberry (sad), in the same car. OP has described the issue better than I could have.
Click to expand...
Click to collapse
Thanks for posting, out of curiosity, what ROM and kernel are you running? Maybe we can find some sort of similarities...
My phone's currently running SlickMOD 3.1 with kernel "2.6.35.14"
-Pete
I've tried black edition and warfare, never had any issues
tomasitoc said:
I've tried black edition and warfare, never had any issues
Click to expand...
Click to collapse
What version of the kernel on your warfare mod? SlickMOD uses the Darkside 2.6.35.14 kernel.
Dirty Pete said:
Thanks for posting, out of curiosity, what ROM and kernel are you running? Maybe we can find some sort of similarities...
My phone's currently running SlickMOD 3.1 with kernel "2.6.35.14"
-Pete
Click to expand...
Click to collapse
Hi Pete,
I've noticed it on Digital Warfare 2.5.1 and BeastMOD 5.0 ("Test 13"), using TDJ's personal kernel and the same 2.6.35.14 above, respectively.
I'll post to Melvin on rootzwiki in the hopes that he can investigate maybe.
It might be better to bring this up in other sections as well. I came across this post by accident while researching extended batteries.
scotty-dont said:
It might be better to bring this up in other sections as well. I came across this post by accident while researching extended batteries.
Click to expand...
Click to collapse
I originally posted it in a different forum, but a moderator kicked it over here. It's not really an accessories question as I'm pretty sure it's a kernel bug, but I wasn't about to argue with site moderators on a forum like this where I'm definitely the new kid on the block.
That being said, if you have some other suggestions as to where we can ask about this, I'm all ears and would be more than willing to help debug/diagnose. I've been a Linux user since '96, so I'm unafraid of poking around in the kernel's guts to get answers.
Pete
Yeah that's the problem with this place... and why I have less than 10 posts.
On second thought, I'm tempted to just wait. It sounds like we will have a proper ICS rom and true kernel on about April 25th, to coincide with the launch of the HTC One S on T-Mobile. I can't find the threads. Hopefully then it will be an issue of the past.
I'm glad I'm not the only one though.
Just a thought....I don’t think this has anything to do with CPU performance
Hi, I have a Galaxy 2s with this exact problem but I wonder if I might offer a suggestion as to what could potentially be the cause. I have no idea how to fix it but I’m hoping that what I share here might help someone who knows more about the way these things work to be able to solve the problem.
I have spent much of my career working in Broadcast Radio, the problem I have heard my phone have with audio dropouts followed by either a ramp up of volume back to the previous level OR an audio dropouts followed by a momentary slight speed shift in the audio playback (sounds a bit like an old cassette recorded when the batteries are starting to fail) many people would probably not notice the later problem because it is very subtle and you have to know what you’re listening for.
Anyway, I believe this could be caused because of a lack of word clock sync between the phone and the bluetooth receiver. I say this because there have been times when I have had digital audio devices such as CD players that are connected to an audio console or digital amplifier and with both devices free running in terms of their clock synchronisation exhibit almost exactly the same symptoms.
You see all digital audio devices require that the audio data be put into frames much the same as regular Ethernet data is transmitted around a network is put into frames, however in order for the audio to be at the correct pitch and speed generally speaking both the playback device (Phone) and the receiving device (Bluetooth receiver) need to have the same word clock, otherwise you end up with the two devices running freely and the audio frames wont by in sync.
Depending on the Error correction implemented (sample rate conversion) on the receiver you can get really odd audio results. I think that this is what is causing this problem. Basically the Bluetooth receiver and the phone aren’t in sync so every few minutes you get a drop out.
It doesn’t seem to happen when you are talking on the phone which makes me think that when you have a call connection as this is bi-directional, the phone is probably synchronised to the Bluetooth device word clock. But when you are listing to music the connection is mono-directional so there is no sync.
Anyway just a thought. Maybe someone out there who understands the way these units synchronise can figure out a fix.
Mine has random just disconnects from the phone altogether. I have Jawbone Era, Voyager Pro Plus, and a Jabra Wave + and all will just randomly disconnect and have a hard time connecting back to phone audio. It will reconnect to media pretty much first time but won't show coonected to phone audio for some reason unleass I turn off BT, turn off headset, and sometimes even re-boot phone.
I am sure you guys have ruled this out, but this was a common problem with bluetooth audio on android. I haven't had the problem for a long time, but I used to have to disable wifi during my commute due to this dropout. Can you turn off wifi and see if the issue still happens? I was able to identify it by changing the time between wifi scan. If you had custom rom settings you could push it out and sure enough, my bluetooth dropouts happened on the same schedule (2s, 10s, more)
Just a thought.
I had this issue when I tried out juggernaut, so I went right back to Bombardier with Synergy kernel. Anyone have this on any if the ICS roms?
Sent from my beastly Galaxy S 2.
Shane_pcs said:
I am sure you guys have ruled this out, but this was a common problem with bluetooth audio on android. I haven't had the problem for a long time, but I used to have to disable wifi during my commute due to this dropout. Can you turn off wifi and see if the issue still happens? I was able to identify it by changing the time between wifi scan. If you had custom rom settings you could push it out and sure enough, my bluetooth dropouts happened on the same schedule (2s, 10s, more)
Just a thought.
Click to expand...
Click to collapse
I disable my wifi while I'm in the car, so this wasn't my issue. Thanks for the suggestion though!
I used to have occasional a2dp problems, however I have not had them since I started using various ICS releasese. The problems I would occasionally have would be a total loss of bluetooth till I rebooted the phone.
Since using Infamous I haven't had the problem other then for some odd reason occasionally having to reenter the PIN #
I'm using a Scoche Bluefusion in my car.
It had to be the fuse.
Sent from my SGH-T959 using xda premium
After upgrading to DARKSIDE's latest ICS rom, this problem has not recurred. I'm assuming that my early thought was correct in that it was some kind of kernel bug.
Dirty Pete said:
After upgrading to DARKSIDE's latest ICS rom, this problem has not recurred. I'm assuming that my early thought was correct in that it was some kind of kernel bug.
Click to expand...
Click to collapse
With Darkside and the stock ROM I have not only this problem, but crackly/staticy audio and my phone and car won't communicate once I've shut the car off. I have to completely re-pair the phone. They're bugs in 4.0.3, which Samsung dumped off on us.
4.0.4 via CM9 already doesn't exhibit the connection issue (I have to turn Bluetooth on and then off though) but I'm not sure about the others yet.

[OFFICIAL] CM10.1 Bug Tracker Thread

So there's been a lot buzz lately about the bugs that are present in the latest build. Therefore, I'm going to maintain the thread to keep track of it all.
RULES:
-This is not a thread for feature requests. It's a thread for bugs, issues, and problems only!
-Before posting, you must swear under oath and punishable by law, that you are referring to a fresh installation and not a dirty flash (a fresh flash can alleviate a lot of the intermittent problems you may be having)
-In order to be a bug, it has to be confirmed by other users under same conditions
Please make sure to actually test bugs instead of saying yes yes yes. I will try to test each bug, but I'm relying on people's integrity as well. We don't want devs wasting time trying to fix something that isn't properly broken. So ensure that your bugs are legit and reproducible. Also, logcats where possible would be an amazing help too. I'm only adding bugs OP that are confirmed by at least a couple users. If it's not in the OP, it's not official.
Current bug list in no particular order:
Lock screen takes a while to draw
GPS works but reports 0-2 satellites only, NMEA data stream seems to be incorrect, so parsing this data may be touchy in some apps
Face unlock doesn't work
Autobrightness is choppy and slow
Pictures from camera show up in the wrong orientation from how they were taken
Bluetooth for headsets does not work, but may work connecting to GPS, etc.
Audio in skype is messed up
Gallery picture editing
Sound delay in calls
Work in progress...
FIXED (latest build)
Music skip/stutter when screen is off
Tethering is broken - M3 Build - thanks budor
No audio in video recording
Data usage/tracking does not work in the settings menu
Keyboard crashes
Current news...
Bluetooth is still broken
New build has an updated kernel with ota support
They are closing in on the audio issues
Stay tuned for a fresh build when the new monthly is released
For the record: this is on CM10.1, on the Samsung Captivate Glide, using the recent 4.2.2 update dated 2/17/2013
- Bluetooth Headset profile doent work
- Audio in video recording not working
- Photosphere unavailable
- audio stutters if screen is turned off (seems to be a CPU sleeping issue)
- Something (i am suspecting Google+, even though i am not actively using it) is filling up my SD card with gigabytes of thumbnails, which i have to delete manually
- lockscreen takes too long to appear
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts). Not a bug per se, but a symlink would've been nice?
- auto-brightness is choppy and slow
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
- face unlock doesnt work (hangs when opening the camera)
- orientation issues when taking photos: if i take a photo in landscape mode, it ends up in portrait mode in the gallery, and vice versa
Since i guess and hope many people will report bugs, and some of them will be not reproducable by others, we should have some mechanism to 'vote' or 'confirm' bugs, i guess?
All of the above...
Connecting to PC with USB, MTP mode does NOT work (it did work in Adam77root's last CM10.1 build ...)
Email - Any mail delivered into sub folders (Using Push MS Exchange) doesn't create a notification.... I miss a lot of email when sorting via rules on delivery. This is new in JB.
Some apps are deleted after reboot. (temporary fix is manually move to sdcard)
The phone connection will drop randomly and not come back until I reboot the phone. Note that I am using a Rogers (Canadian) model, if it has any relevance. Let me know how I can help you diagnose this bug.
mschweini said:
For the record: this is on CM10.1, on the Samsung Captivate Glide, using the recent 4.2.2 update dated 2/17/2013
- Audio in video recording not working
Click to expand...
Click to collapse
+1
- lockscreen takes too long to appear
Click to expand...
Click to collapse
+1
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts). Not a bug per se, but a symlink would've been nice?
Click to expand...
Click to collapse
+1, using Directory Bind as a replacement
- auto-brightness is choppy and slow
Click to expand...
Click to collapse
+1
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
Click to expand...
Click to collapse
GPS lock timeframe +1, not sure about the report
- face unlock doesnt work (hangs when opening the camera)
Click to expand...
Click to collapse
+1
- orientation issues when taking photos: if i take a photo in landscape mode, it ends up in portrait mode in the gallery, and vice versa
Click to expand...
Click to collapse
+1
yohan4ws said:
Some apps are deleted after reboot. (temporary fix is manually move to sdcard)
Click to expand...
Click to collapse
For me, some apps are weird and are missing icons: http://i.imgur.com/CNZ5Nwq.png
face unlock does not work, but it's not that important, just to mention it.
OP updated. Please make sure to actually test bugs instead of saying yes yes yes. I will try to test each bug, but I'm relying on people's integrity as well. We don't want devs wasting time trying to fix something that isn't properly broken. So ensure that your bugs are legit and reproducible. Also, logcats where possible would be an amazing help too. I'm only adding bugs OP that are confirmed by at least a couple users. If it's not in the OP, it's not official.
Sent from my SGH-I927 using Tapatalk 2
Just thought that I would mention that I've noticed that the audio stutter is even more noticeable when the phone is plugged into something using a line in instead of headphones. I'm not sure if this is a issue specific to my device, but if I use a patch cord (audio cable, but w/o the extra contact for a remote) the music sometimes stops altogether, and rarely resumes. This happens whether the screen is on or off. Bluetooth audio stream however is completely fine. No stutter even if screen is off.
Devian50 said:
Just thought that I would mention that I've noticed that the audio stutter is even more noticeable when the phone is plugged into something using a line in instead of headphones. I'm not sure if this is a issue specific to my device, but if I use a patch cord (audio cable, but w/o the extra contact for a remote) the music sometimes stops altogether, and rarely resumes. This happens whether the screen is on or off. Bluetooth audio stream however is completely fine. No stutter even if screen is off.
Click to expand...
Click to collapse
I've never had it stop on me all together.
I feel like this thread should be in the dev section, no? Flag this thread to move it if you think so
Sent from my SGH-I927 using Tapatalk 2
Please don´t throw stones, but bluetooth is or isn´t working? I´d like to try CM 10.1 but I need bluetooth working to use the phone while driving.
brunobbarcelos said:
Please don´t throw stones, but bluetooth is or isn´t working? I´d like to try CM 10.1 but I need bluetooth working to use the phone while driving.
Click to expand...
Click to collapse
2nd post ... says Bluetooth headset profile doesn't work .. this means you can stream Audio to your car's stereo, but you can NOT use your headset... I'm going to assume it's the same accross all ROMs that you can HEAR the other person talk, but the microphone via bluetooth isn't enabled.... my other assumption is that it has to do with the sound driver issues of using skype etc. where when the microphone is activated, all other sound output becomes sloooow motion. -
These are assumptions based on an under educated hypothesis .. a guess.. a shot in the dark ... based on no fact .. and hence, could be completely entirely wrong
Here's a thought, though, why don't you do a nandroid backup in CWM one evening, download the CM10.1 and install it and play with it test bluetooth and some other things, report your findings and if bluetooth deosn't work, revert back to your backup... nothing lost and everything to gain PLUS you'll be helping out the community.
gtmaster303 said:
I've never had it stop on me all together.
I feel like this thread should be in the dev section, no? Flag this thread to move it if you think so
Sent from my SGH-I927 using Tapatalk 2
Click to expand...
Click to collapse
The reason it isn't in the dev section is because it isn't actually a dev thread. The dev section is more for an actual product, whereas this is more documentation for a product, meant to answer questions people might otherwise ask in the general section.
Any of you guys use Whatsapp? It will tell you that tablets are not supported.. :/
And the main Google search app (where you can't type more than one letter from the homescreen) always closes.
Great work BTW. I just got this this afternoon. I'm loving how smooth it is
Sent from my SGH-I927 using xda app-developers app
chrisyjwai said:
Any of you guys use Whatsapp? It will tell you that tablets are not supported.. :/
And the main Google search app (where you can't type more than one letter from the homescreen) always closes.
Great work BTW. I just got this this afternoon. I'm loving how smooth it is
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Whatsapp works for me.
You can fix the google search app by disabling the hotword feature.
Snuuuuupy said:
Whatsapp works for me.
You can fix the google search app by disabling the hotword feature.
Click to expand...
Click to collapse
Yea. Sorry my bad. I had no service at that point. The app could not verify a network and assumed it was a tablet.
Thanks.
Okay. So basically I flash this firmware and before I proceed to use any of the apps I decide to update them. So while the outdated search app still had the hotwords feature on, I updated it. Thereafter, the app will close even before I could get to the setting menu. So the only way is to either use the older version or use the older version to turn off the hotwords feature and update. I know this is minor. Just thought I'd add this to a bugs thread.
And there are some speaker/microphone issues with google hangouts.
Anyone second this?
Sent from my SGH-I927 using xda app-developers app
chrisyjwai said:
Okay. So basically I flash this firmware and before I proceed to use any of the apps I decide to update them. So while the outdated search app still had the hotwords feature on, I updated it. Thereafter, the app will close even before I could get to the setting menu. So the only way is to either use the older version or use the older version to turn off the hotwords feature and update. I know this is minor. Just thought I'd add this to a bugs thread.
And there are some speaker/microphone issues with google hangouts.
Anyone second this?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Open up the older one. Don't update, disable hotwords and that new google feature (cards?). Update, should work fine.
Tethering
Tethering is broken, I didn't see it in the list. Even FoxFi doesn't work.

[ROM][CM12.0] UNOFFICIAL CM12.0 for LS970

BACKUP YOUR EFS THROUGH FREEGEE AND/OR TWRP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a preview of CM-12.0 built entirely from CM sources. There are few modifications (listed below in features).
Features
- Settings->About Phone->CyanogenMod updates uses wfhome.net servers (my builds)
Latest Build
I have started Nightly's
Downloads
Latest Builds
http://goo.gl/kQP3f8 - Private Hosting (no ads, no waiting, enjoy)
Old Builds
http://goo.gl/Sz2K7a - Android File Host
Google Apps
http://forum.xda-developers.com/android/software/gapps-google-apps-flashable-package-t2930266
TWRP - 2.8.3.0
http://teamw.in/project/twrp2/155
Known Issues
- "No SIM Card" message on lock screen (CM12 issue)
- Built in Messenger App doesn't work right (CM12 issue)
- Nothing else that I have noticed
All changes can be viewed on the CyanogenMod gerrit.
Thanks to all who have developed CyanogenMod and the device and kernel trees for the Optimus G.
I'm using a modified version of @JulianXhokaxhiu CyanogenModOTA tools on my web server.
https://github.com/julianxhokaxhiu/CyanogenModOTA
Source
http://github.com/CyanogenMod
http://github.com/rjwil1086
The E970 and LS970 are slightly different, have you used the LS970 sources to build? The LS970 has minor differences in the camera as well as it being CDMA and not requiring a SIM card. Are these taken into affect? I am going to test because this is actually based on US hardware so I am hoping for most things to work that do not because other builds are based from international versions.
dopy25 said:
The E970 and LS970 are slightly different, have you used the LS970 sources to build? The LS970 has minor differences in the camera as well as it being CDMA and not requiring a SIM card. Are these taken into affect? I am going to test because this is actually based on US hardware so I am hoping for most things to work that do not because other builds are based from international versions.
Click to expand...
Click to collapse
I did use the LS970 sources. I have AT&T and Sprint phones (just not an LS970) so I am aware of the network differences. I am also aware of the 13MP camera the LS970 has. This is built entirely with CM sources (I'm using a fork of http://github.com/TheMuppets for vendor blobs; I added some gps blobs to get gps working). The device tree for these two phones share a lot of stuff as they are broken into 3 repositories (gproj-common, ls970-common, and ls970). The e970 also uses gproj-common and ls970-common which are about 95% of the device tree code for both phones. There is already a CM-12.0 branch on github for the ls970 so I'm assuming it was updated just like the e970. Just need someone with hardware to check it out.
rjwil1086 said:
I did use the LS970 sources. I have AT&T and Sprint phones (just not an LS970) so I am aware of the network differences. I am also aware of the 13MP camera the LS970 has. This is built entirely with CM sources (I'm using a fork of http://github.com/TheMuppets for vendor blobs; I added some gps blobs to get gps working). The device tree for these two phones share a lot of stuff as they are broken into 3 repositories (gproj-common, ls970-common, and ls970). The e970 also uses gproj-common and ls970-common which are about 95% of the device tree code for both phones. There is already a CM-12.0 branch on github for the ls970 so I'm assuming it was updated just like the e970. Just need someone with hardware to check it out.
Click to expand...
Click to collapse
Great! Sounds like you know what you are doing. I am downloading it right now and am at 20%. I will flash when done and absolutely report back.
EDIT FOR FINDINGS
@rjwil1086 GREAT JOB! The ROM is working great on my device (LS970) so I will send some feedback
PROS
1) Everything seems to work for the most part except items listed under CONS.
2) Calls and data are working from flashing, no extra steps needed to achieve calls or data. 4G coverage included.
3) Superuser is integrated (THANK YOU)
4) Camera works superb, even quality is amazing. (see cons)
5) Voicemail by long pressing one works and on other CM12 does not.
6) You can turn on "flash" while video recording so you have overhead light. Maybe I've missed that in every other ROM but that's great! (Does not cause phone to power down, see #6 cons)
CONS
1) Messaging app does not send a text from within the built in app (Quick reply works fine) I think this is CM issue and not device because it is in all CM based roms currently.
2) Swipe texting does not work with built in keyboard.
3) No SIM card appears in notification bar on lock screen (once again in other CM12 ROMS).
4) Data usage is not tracked at all, it says no apps used data right after I used the browser and the Play Store to download something.
5) NEW FINDINGS:: Phone calls will not end, pressing the end icon only makes the end option go away but the phone call is still in progress. I tried using a bluetooth headset and only the device. My work around is to enable Airplane Mode then disable it, that shuts the phone call off.
6) using flash in any camera app causes device to power off, overhead light during video recording is fine though.
7) Volume control on screen lock is not possible. You must unlock the screen to alter the volume (notable in music playing)
8) Very important!! While making a call, the phone immediately disconnects. When I call back, the other caller is still connected so it goes to voicemail. I have to ask them to ignore the first call so I can make it again. This happens every time and is very difficult to manage since I have to enable airplane mode to end the call.
On another note, I am using the Multiboot method and have this installed as primary, I haven't tested any secondary ROMs but I do not expect them to boot and that is due to a specific patch being required for the kernel that is not compatible with gproj. Also, it will not install as secondary, it fails upon flashing. The only thing I noticed is that it takes awhile longer at the boot screen to get past it than other roms. No issues though since it works to my expectations.
I will continue to use this to see if anything else comes up, but over all this is awesome. I look forward to CM fixing things upstream. Please keep those builds coming, they work.
Looks good. Once those CM bugs get worked out, this ROM will be fantastic! Thank you for this ROM! Willing to test any new updates. Seems like dopy did a pretty solid review so far.
This ROM running Android Lollipop 5.0?
RegKilla said:
This ROM running Android Lollipop 5.0?
Click to expand...
Click to collapse
Yes, CM12 is 5.0 (in this case 5.0.1)
EDIT: @rjwil1086 ...
GREAT JOB ON THAT UPDATE. I'm not sure if it was you that fixed it or CM fixes, but some of the previous issues are gone. Now this is extremely stable. I definitely recommend it to anyone with an LS970.
Fixed issues: (calls are main thing fixed)
1) Calls end perfectly fine
2) Phone no longer shuts off at flash of the camera.
3) no issues with music. (I didn't mention it before but when I would try to play music from any app, it would say it was playing but the song would not progress and there was no sound. I also attributed it to my bluetooth headset, but now the issue is gone)
4) Adaptive brightness and notification bar brightness adjustment has always worked with this ROM. (basically all aspects of brightness work)
still existing issues
1) Volume control on inactive lock screen. (still have to turn on screen)
2) Data usage still not tracked by settings/data usage.
3) messaging app will not show active send, pressable icon (cannot send text from within the app but quick reply still works) (I'm certain CM issue)
4) Swipe texting with built in keyboard (most likely CM issue)
5) Not really an issue but lock screen still says "No SIM card" (CM issue?)
Great update, more than half of the major issues have been fixed, now it seems like mostly CM issues , and not even major problems.
dopy25 said:
Yes, CM12 is 5.0 (in this case 5.0.1)
EDIT: @rjwil1086 ...
GREAT JOB ON THAT UPDATE. I'm not sure if it was you that fixed it or CM fixes, but some of the previous issues are gone. Now this is extremely stable. I definitely recommend it to anyone with an LS970.
Fixed issues: (calls are main thing fixed)
1) Calls end perfectly fine
2) Phone no longer shuts off at flash of the camera.
3) no issues with music. (I didn't mention it before but when I would try to play music from any app, it would say it was playing but the song would not progress and there was no sound. I also attributed it to my bluetooth headset, but now the issue is gone)
4) Adaptive brightness and notification bar brightness adjustment has always worked with this ROM. (basically all aspects of brightness work)
still existing issues
1) Volume control on inactive lock screen. (still have to turn on screen)
2) Data usage still not tracked by settings/data usage.
3) messaging app will not show active send, pressable icon (cannot send text from within the app but quick reply still works) (I'm certain CM issue)
4) Swipe texting with built in keyboard (most likely CM issue)
5) Not really an issue but lock screen still says "No SIM card" (CM issue?)
Great update, more than half of the major issues have been fixed, no it seems like mostly CM issues , and not even major problems.
Click to expand...
Click to collapse
Yup all those were fixed by CM developers. I saw several CDMA fixes in the ril code. I'm sure there were more elsewhere in the code. Swipe on the keyboard is disabled in CM because it doesn't work on any of my devices.
rjwil1086 said:
Yup all those were fixed by CM developers. I saw several CDMA fixes in the ril code. I'm sure there were more elsewhere in the code. Swipe on the keyboard is disabled in CM because it doesn't work on any of my devices.
Click to expand...
Click to collapse
So the 12/20/14 build fixes those bugs?
Downloading now. Thank you for this again! Breathes some life into this old phone lol.
Edit; I would just like to add; you sir, have made me love cyanogenmod once again.
I use to use CM 10.2 all the time, but honestly, when the official CM11 came out with LS970 sources, it always felt, not laggy, but not responsive. As in just sluggish. Gee Roms always ran fast on my optimus, but always over heated easily too.
I absolutely love this ROM. It is extremely fast and uses LS970 sources. I can finally leave stock confidently. Is there anyway I can repay you? I am on mobile, so I can't see much, but do you have a donation link? I'd pay to keep this going.
Fantastic job. It works great!
Never had this much responsiveness on a LS970 cm ROM before.
Edit 2: Does anyone know how to disable mobile data? I like to turn it off so it doesn't suck battery in low service areas. Thanks again.
Whiplashh said:
Edit; I would just like to add; you sir, have made me love cyanogenmod once again.
I use to use CM 10.2 all the time, but honestly, when the official CM11 came out with LS970 sources, it always felt, not laggy, but not responsive. As in just sluggish. Gee Roms always ran fast on my optimus, but always over heated easily too.
I absolutely love this ROM. It is extremely fast and uses LS970 sources. I can finally leave stock confidently. Is there anyway I can repay you? I am on mobile, so I can't see much, but do you have a donation link? I'd pay to keep this going.
Fantastic job. It works great!
Never had this much responsiveness on a LS970 cm ROM before.
Edit 2: Does anyone know how to disable mobile data? I like to turn it off so it doesn't suck battery in low service areas. Thanks again.
Click to expand...
Click to collapse
I agree, it is definitely snappier than any ROM I've ever used on this phone.
As far as data, I don't know. I tried a few widgets and shortcuts to no avail. I'm sure it's a matter of time before it's enabled in settings from CM.
I did have some partial success with quick shortcut maker. Run a search for "data" and try to use the shortcut to data roaming under "phone." What it did was say settings has force closed, but it shut off my mobile data. It caught me off guard but a reboot turned it back on.
On the plus side, battery life is pretty wicked already.
dopy25 said:
I agree, it is definitely snappier than any ROM I've ever used on this phone.
As far as data, I don't know. I tried a few widgets and shortcuts to no avail. I'm sure it's a matter of time before it's enabled in settings from CM.
I did have some partial success with quick shortcut maker. Run a search for "data" and try to use the shortcut to data roaming under "phone." What it did was say settings has force closed, but it shut off my mobile data. It caught me off guard but a reboot turned it back on.
On the plus side, battery life is pretty wicked already.
Click to expand...
Click to collapse
Even with data on the battery is good? That's awesome!
Just a heads up, the build does still have some phone issues. Can't call on first try and hangup without hitting airplane mode. Calls coming in work perfectly, but out can be a hassle.
Whiplashh said:
Even with data on the battery is good? That's awesome!
Just a heads up, the build does still have some phone issues. Can't call on first try and hangup without hitting airplane mode. Calls coming in work perfectly, but out can be a hassle.
Click to expand...
Click to collapse
From what I've noticed, it is absolutely great on battery. I'll post some screen shots. I was in and out of 3/4G. Downloaded a few files, probably 500mb worth. Played tapped out, which is a freaking battery hog. And still lasted a whole day. I did just notice that the total hours don't seem to be tracked, that's odd.
On the phone thing, I am so sorry you're still having that issue, it is gone for me. Are you sure you're on the 12/20 build? Maybe we did something different.
I flashed the 12/18 and GApps since I tried it first (then restored the backup of it because I had since flashed another ROM and neither would work as secondary on my multi boot setup) then I flashed the 12/20 build to update (dirty flash over 12/18) cleared cache's twice because I like to. And it seemed to work. That's a real bummer that it doesn't work for you. Incoming or outgoing work fine for me, for now anyway.
screen shots I'll have to post later, I always have issues doing that on my phone
dopy25 said:
From what I've noticed, it is absolutely great on battery. I'll post some screen shots. I was in and out of 3/4G. Downloaded a few files, probably 500mb worth. Played tapped out, which is a freaking battery hog. And still lasted a whole day. I did just notice that the total hours don't seem to be tracked, that's odd.
On the phone thing, I am so sorry you're still having that issue, it is gone for me. Are you sure you're on the 12/20 build? Maybe we did something different.
I flashed the 12/18 and GApps since I tried it first (then restored the backup of it because I had since flashed another ROM and neither would work as secondary on my multi boot setup) then I flashed the 12/20 build to update (dirty flash over 12/18) cleared cache's twice because I like to. And it seemed to work. That's a real bummer that it doesn't work for you. Incoming or outgoing work fine for me, for now anyway.
screen shots I'll have to post later, I always have issues doing that on my phone
Click to expand...
Click to collapse
I clean flashed the 12/20 build. Wiped everything twice because thats how I do. Had to go back to stock so I could make calls and organize a friends bday party. Hopefully this flash will be better.
Whiplashh said:
I clean flashed the 12/20 build. Wiped everything twice because thats how I do. Had to go back to stock so I could make calls and organize a friends bday party. Hopefully this flash will be better.
Click to expand...
Click to collapse
The weird thing is, it's happening intermittently for me as well. But it seems more like making calls from the first call screen. Selecting recents seems to not do it. Also seems like it happens more when LTE is on. I haven't tried switching to 3G only but it dedi definitely didn't do it when I only have 3G.
dopy25 said:
The weird thing is, it's happening intermittently for me as well. But it seems more like making calls from the first call screen. Selecting recents seems to not do it. Also seems like it happens more when LTE is on. I haven't tried switching to 3G only but it dedi definitely didn't do it when I only have 3G.
Click to expand...
Click to collapse
It just happens all the time. I'm using CWM recovery so I don't know if that effects it. Hopefully it will work out soon. That and the messaging bug. Loving the ROM so far. Once those 3 things are fixed, this phone won't see stock again lol.
(Data toggle, messaging send which IS a cm thing, and the phone issue).
Whiplashh said:
It just happens all the time. I'm using CWM recovery so I don't know if that effects it. Hopefully it will work out soon. That and the messaging bug. Loving the ROM so far. Once those 3 things are fixed, this phone won't see stock again lol.
(Data toggle, messaging send which IS a cm thing, and the phone issue).
Click to expand...
Click to collapse
I can only assume that recovery shouldn't be an issue as long as it's semi up to date. But some people are having sensor issues on all other builds and it very well could be related, I don't know enough on the subject. I will keep up on this because this ROM really is slick. I use textra for messaging but I really like the built in messenger. Google messenger is almost identical but has MMS issues. Nothing on textra, it works perfectly. So I'm still using this daily. I'm sure data toggle will go in soon. I see an APN update in the change log so I'm sure it's coming soon. I'll keep you updated.
dopy25 said:
I can only assume that recovery shouldn't be an issue as long as it's semi up to date. But some people are having sensor issues on all other builds and it very well could be related, I don't know enough on the subject. I will keep up on this because this ROM really is slick. I use textra for messaging but I really like the built in messenger. Google messenger is almost identical but has MMS issues. Nothing on textra, it works perfectly. So I'm still using this daily. I'm sure data toggle will go in soon. I see an APN update in the change log so I'm sure it's coming soon. I'll keep you updated.
Click to expand...
Click to collapse
Thank you!
Whiplashh said:
Thank you!
Click to expand...
Click to collapse
Give today's build a shot. I just made about 10 phone calls to various numbers from various locations within the dialer and all connected the first time, and disconnected fine.
There is still no data toggle, but data is now being tracked (or at least showing that it was previously tracked) I also do not see any apn settings but that might not have been an update for our device that I saw.
Messaging still does not send from within the app but quick reply is fine (I use Textra SMS and everything works in it)
If there's anything else you want me to check just say the word. I wonder if it's a cache issue with the dialer or something causing the phone to misbehave, but it seems to be working fine now.
dopy25 said:
Give today's build a shot. I just made about 10 phone calls to various numbers from various locations within the dialer and all connected the first time, and disconnected fine.
There is still no data toggle, but data is now being tracked (or at least showing that it was previously tracked) I also do not see any apn settings but that might not have been an update for our device that I saw.
Messaging still does not send from within the app but quick reply is fine (I use Textra SMS and everything works in it)
If there's anything else you want me to check just say the word. I wonder if it's a cache issue with the dialer or something causing the phone to misbehave, but it seems to be working fine now.
Click to expand...
Click to collapse
That's one down. Like I said, I love this ROM. The camera is AMAZING. I'll test it and see what happens.

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

Categories

Resources