• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM 10.1 Nightlies Discussion

IMUcarmen said:
I don't know. I don't follow any android related news other than what phones are coming out but I guess it has been almost a year since jellybean was released and we should be due for a new version soon...time goes by so fast it seems like there are updates all the time.
Click to expand...

From what I understand KLP won't be out till October, or whenever the Motorola X comes out, possibly. HTC has leaked some info on 4.3, which may be out in the next few weeks. We'll know in just over a week, I'm sure (Google I/O).
 
hayneskr said:
Anyone see this over on XDA? http://forum.xda-developers.com/showthread.php?t=2267708
nexwave-mat found a work around for the p930 and bluetooth with cm10.1 :). He rolled back a couple of commits in the lge-kernel-iproj.

And cm fixed another issue with bluetooth and null socket. https://github.com/cyanogenmod/andr...mmit/ef61f8ebbf1119a29617dddbcf0a7753bf29bf2b

Good stuff! :)
Click to expand...
Excellent!!! .... what does this mean though? How soon will this fix carry over to the Spectrum?
 
trav06 said:
Excellent!!! .... what does this mean though? How soon will this fix carry over to the Spectrum?
Click to expand...

Not sure, but has anyone tried today's nightly 5/7? Would be interesting to see if cm's fix for the null socket has any bearing on the bluetooth failure we have been experiencing.. :)
 
CharismaRansom said:
Fix crash during BT shutdown item under Bluetooth in the CM 5-7-13 nightly.
Click to expand...

In the xda forums under nitro, several have said this bt shutdown fix does not correct the problem.

The problem is most likely the implementation of bluedroid, one xda member was able to revert 2 commits in the lge kernel iproj and get bluetooth working again on the nitro. I think we may be able to do something similar but will need to recompile kernel. It will take a bit more work to fix the issue in cm 10.1.

But at least there is more info now and we have a starting point!
 
hayneskr said:
In the xda forums under nitro, several have said this bt shutdown fix does not correct the problem.

The problem is most likely the implementation of bluedroid, one xda member was able to revert 2 commits in the lge kernel iproj and fet bluetooth working again on the nitro. I think we may be able to do something similar but will need to recompile kernel. It will take a bit more work to fix the issue in cm 10.1.

But at least there is more info now and we have a starting point!
Click to expand...

Why would it take more work? That should be essentially the same kernel we have now.

Sent from my VS920 4G using Tapatalk 2
 
Yoinx said:
Why would it take more work? That should be essentially the same kernel we have now.

Sent from my VS920 4G using Tapatalk 2
Click to expand...

When tdm rolled his work into the mainstream cm10.1, the kernel was recompiled and several changes were made by others to add Bluedroid stack. 2 of these commits seem to be the ones that have caused our bluetooth issue.

Not sure rmcc would let 2 reverts slide back into our main kernel, but he might. Also, the fix has only worked on att/skt versions. Have not tried it on vzw yet. I'm pulling down kernel source now.

The reason I say it may take some work is if we have to "fix" the code without rolling back the 2 commits that caused the issue.
This link was to Register bluesleep uart for bluedroid.
This link was for bluesleep: implement to support bluedroid in our kernel.
which was just modifiying drivers/bluetooth/bluesleep.c to add Bluedroid in place of Bluez. We might be able to set +#define BT_BLUEDROID_SUPPORT 0 instead of 1 and try but lots lines removed in the one commit that may cause problem with BLUEZ working. Just not sure.

I'm still learning so I may be way off base here, so someone with more kernel knowledge may be able to fix this easily. :) I'm trying! :D
 
hayneskr said:
When tdm rolled his work into the mainstream cm10.1, the kernel was recompiled and several changes were made by others to add Bluedroid stack. 2 of these commits seem to be the ones that have caused our bluetooth issue.

Not sure rmcc would let 2 reverts slide back into our main kernel, but he might. Also, the fix has only worked on att/skt versions. Have not tried it on vzw yet. I'm pulling down kernel source now.

The reason I say it may take some work is if we have to "fix" the code without rolling back the 2 commits that caused the issue.
This link was to Register bluesleep uart for bluedroid.
This link was for bluesleep: implement to support bluedroid in our kernel.
which was just modifiying drivers/bluetooth/bluesleep.c to add Bluedroid in place of Bluez. We might be able to set +#define BT_BLUEDROID_SUPPORT 0 instead of 1 and try but lots lines removed in the one commit that may cause problem with BLUEZ working. Just not sure.

I'm still learning so I may be way off base here, so someone with more kernel knowledge may be able to fix this easily. :) I'm trying! :D
Click to expand...


No idea, I'm no dev. It makes sense though I guess. Watching logcat with bluetooth messing up. It looks like the service tries to connect but gets rejected because the hardware thinks that it's already connected to something, then just starts running through a failing loop where it tries to connect.

If those patches/reverts make it actually power down or sleep... that would probably fix, at least that part of it, I would guess.
 
Anyone else on rc2 or earlier even use Pandora? For the life of me I can't figure out a setting or something, but I can't add channels or search anything. When I tap the search bar the screen just flashes.

I have wiped everything and reisntalled rc2 and still have the same problem.
 
scottfan81 said:
Anyone else on rc2 or earlier even use Pandora? For the life of me I can't figure out a setting or something, but I can't add channels or search anything. When I tap the search bar the screen just flashes.

I have wiped everything and reisntalled rc2 and still have the same problem.
Click to expand...

I've had this problem in the pandora app forever.

I usually just add stations through the web browser. Then access them through the app.
 
Yoinx said:
I've had this problem in the pandora app forever.

I usually just add stations through the web browser. Then access them through the app.
Click to expand...

I know. It sucks. Lol. But I thought there might be a setting on the phone. I remember people talking about DPI settings? I think. But I'm a noob so not sure how to try that or if it would even help. :(
 
Any word on when development for the HTC one xl (evita) will resume? Nightlies stopped in march due to a dmca takedown.
 
matxor said:
Any word on when development for the HTC one xl (evita) will resume? Nightlies stopped in march due to a dmca takedown.
Click to expand...

You'd probably be better off asking in a forum for that hardware. Perhaps even on the Cyanogenmod forums.

Here's the subforum here for it.

HTC One X/XL - Android Forums


I doubt anyone in this LG Spectrum Subforum will be able to tell you much about that phone.
 
Can anyone confirm an app called Viber working and being able to make/hold phone calls on RC2? I'm on beta4, and that is the only app that doesn't work. Really hopping it starts working again as its the main app I use for communication..
 
YoungGun said:
Can anyone confirm an app called Viber working and being able to make/hold phone calls on RC2? I'm on beta4, and that is the only app that doesn't work. Really hopping it starts working again as its the main app I use for communication..
Click to expand...
The microphone not working for things not being phone calls has been a problems since Quattrimus. We still don't have a fix.
 
  • Like
Reactions: tdm
You must log in or register to reply here.
Back
Top Bottom