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

[Verizon] [rom]jbsourcery v5.4-lte[06/07/13] jb4.2.2 The Final Call

Per T-Dev's recommendation, I am trying various kernels in Tools in an attempt to clear up my Bluetooth issue. So far I know that Trinity and Popcorn kernels send my Nexus into bootloops. On Tiny kernel now, and it's still breaking up.

This isn't a connectivity issue, as it breaks up on both 4G and wifi, with the phone MAYBE 3 feet from the headset. I normally get a 50-60 foot range.

I hate to think I may have to revert back to 4.5 or 4.6, but Bluetooth connectivity is vitally important to me. If anyone has any ideas, I'm ready to try just about anything here...

:(
 
SecondShot said:
Tdev:

I figured it out. When pattern lock is selected it breaks the lockscreen security choice.
Click to expand...
It doesnt for me.. not sure why some see this issue while the bulk of the users do not. Try grabbing a logcat next time it fails.. betting there is another app working on conjunction with this that I dont have loaded
 
SecondShot said:
Weird, getting a force close on the lockscreen security and settings selection in settings. Anyone else?

This is on a clean install too, FYI.
Click to expand...

Add me to the list, fc when I i tap lockscreen in sourcery settings. Error says "unfortunately settings have stopped"
 
Was able to duplicate. Had to change lockscreen to pattern. Then later go back into lockscreen security...got force close.

Was able to go into normal security settings change back to slide, this then fixed the force close in the jbs lockscreen section.
 
Hey Triton, agreed...see my previous post. This was my experience in replicating the problem too. I could get and undo the forceclose by turning on and off "patternlock." I wonder if Chronos has something to do with it. Do you have that loaded?
 
I was able to follow these steps and get force close to stop, that is until I set a by new security and then it's back to force close.
Tdev, where should I send the log?
 
The_Chief said:
Per T-Dev's recommendation, I am trying various kernels in Tools in an attempt to clear up my Bluetooth issue. So far I know that Trinity and Popcorn kernels send my Nexus into bootloops. On Tiny kernel now, and it's still breaking up.

This isn't a connectivity issue, as it breaks up on both 4G and wifi, with the phone MAYBE 3 feet from the headset. I normally get a 50-60 foot range.

I hate to think I may have to revert back to 4.5 or 4.6, but Bluetooth connectivity is vitally important to me. If anyone has any ideas, I'm ready to try just about anything here...

:(
Click to expand...


I am having the same problem with my Bluetooth receiver since I jumped from 4.5 to 5.0
 
Two questions for the Dev team:

#1 What kernel was used for 4.5, does it work with 5.0, and where can I get it?

#2 I suppose the little "present" in IRC can be flashed with a cache and Dalvik wipe?

Thanks :)


EDIT: Okay, I was under the obviously mistaken impression that the Magic Clock UI controls the DeskClock. However, I un-bolded everything there but that stupid 4.2 clock's hour is still bold! I had high hopes that I could make use of the latest & greatest without flashing the old 4.1 Clock back in... and I hope you can tell me what I'm doing wrong. And please tell me what exactly the Magic Clock UI controls!

:confused:

I so loathe that thick hour that I will go to such lengths to be rid of it.
 
The_Chief said:
Two questions for the Dev team:

#1 What kernel was used for 4.5, does it work with 5.0, and where can I get it?

#2 I suppose the little "present" in IRC can be flashed with a cache and Dalvik wipe?

Thanks :)


EDIT: Okay, I was under the obviously mistaken impression that the Magic Clock UI controls the DeskClock. However, I un-bolded everything there but that stupid 4.2 clock's hour is still bold! I had high hopes that I could make use of the latest & greatest without flashing the old 4.1 Clock back in... and I hope you can tell me what I'm doing wrong. And please tell me what exactly the Magic Clock UI controls!

:confused:

I so loathe that thick hour that I will go to such lengths to be rid of it.
Click to expand...

magic clock is the chronos clock...
works on the lockscreen.
Like the dash clock for it much better.

1. will have to check, dont remember which one it was
2. Yes
 
Okay, so I suppose that there is no way to use the 4.2 desk clock and my live wallpaper at the same time like the 4.1 desk clock.

I further suppose that there is no way to thin or un-bold the hour in the 4.2 desk clock, or change the color of the clock display from white.

Is that correct?

I have set colors for the clock in Magic Clock UI and nothing on my phone has changed. I guess I have some more experimenting to do.

Sent from my Galaxy Nexus using SwiftKey Flow
 
I too am having the lockscreen security and settings FCing. I have face unlock on with a PIN.
And maybe another bug, but my google voice left a voicemail notification and when I clicked the notification, it opened google voice like i was sending a message.
 
You must log in or register to reply here.
Back
Top Bottom