yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tiny4579:
From the dev of the mod:

It works for inductive charging through the pogo pins (i.e. wireless charging pad). Or at least it did when I wrote the original patch. Its been a pretty long time so lots of stuff in the kernel could have changed by now. If I remember though, the dock uses a different resistor so that it knows to switch to dock mode. I don't know if I'll have time to look into it, but it shouldn't be too hard to implement a change for it.
[Samsung Galaxy Nexus] butler360:
Wow, thanks for checking that out for me! It would be an awesome feature to have, since driving using GPS, LTE, and Google Music streaming eats the battery pretty fast.
[Samsung Galaxy Nexus] Jose Viegas:
I'm using this kernel on Maguro with great results, fast, great battery and none of the common bugs found in other kernels so far :good:
[Samsung Galaxy Nexus] BOY_:
Tiny, I flashed 2.3 last night and I'm getting serious battery drain :( Google services is consuming approx 1/2 my battery in keep awake (various syncs). Literally, been unplugged 11 min and down 4%. Not sure what's going on (tired to cycle BT, got a fresh GPS lock). I do notice that when unlocking the phone, the WiFi and phone icons are not connected to Google (grayed out). Thoughts?
[Samsung Galaxy Nexus] tiny4579:
Not sure what is causing it but it definitely has nothing to do with the kernel. Try flashing the ROM again followed by gapps and the kernel. Wipe cache and dalvik for safe measure.
[Samsung Galaxy Nexus] tiny4579:
5.1 is meant for JB 4.3 but it may work fine on JB 4.2.2.
[Samsung Galaxy Nexus] zoomy942:
I looked several pages back and didn't see what dynamic interactive was?
[Samsung Galaxy Nexus] zoomy942:
Did a ton of searching. Looks like it's interactive with the ability to change it's own tunables
[Samsung Galaxy Nexus] zoomy942:
Boype was talking about timer slack so I thought I'd share it with you.

[KERNEL] Fancy Kernel r39 [Android 4.3] [Linux 3.0.93] [AUG-20-2013]

http://xdaforums.com/showpost.php?p=44899678
[Samsung Galaxy Nexus] zoomy942:
Found more.

http://xdaforums.com/showthread.php?p=44922850
[Samsung Galaxy Nexus] tiny4579:
I wasn't aware of this info before. Thank you bunches. Looks like I have to update now.

The second link more or less points back to the post you first linked,
[Samsung Galaxy Nexus] zoomy942:
After all you've done for devices I've owned over the years-you are most welcome sir.
[Samsung Galaxy Nexus] zoomy942:
Side note. I'm very much enjoying hot plugging interactivex.
[Samsung Galaxy Nexus] zoomy942:
I've been googling all over and dynamic interactive is hard to find. Hot plugs? Changes settings? Omniatic asked for it so I'm trying to find more info.
[Samsung Galaxy Nexus] chelseafcfan:
did anyone having a restarted phone after making a phone call? Or it's just mine?
[Samsung Galaxy Nexus] omniatic:
Check MBQ's guide. I think it's listed in there. I believe that it can adjust voltages and some other settings on the fly as needed.

I've been using it on 4.2.2, and found it smoother than interactive. Try it out, you may have a new favorite.
[Samsung Galaxy Nexus] kuronosan:
I'd love to download it but I just can't get it to work. It keeps downloading 7kb files or not downloading it at all.
[Samsung Galaxy Nexus] tiny4579:
What link are you using? If you're using the mbqonxda link and you're in a mobile browser you need to enable desktop mode in the browser. Goo should work properly regardless. I think their speed is better now.
[Samsung Galaxy Nexus] zoomy942:
Hi MBQ. Care to share any details of it? Hot plug? Specs? Those things?
[Samsung Galaxy Nexus] kuronosan:
Doing it through goo and it downloaded a quick file. It does that with all of them.
[Samsung Galaxy Nexus] tiny4579:
Mobile or pc? I just downloaded from goo and it's the right size. Maybe it's your browser. That can happen if it doesn't properly handle redirects.
[Samsung Galaxy Nexus] AbhishekS:
I downloaded Battery Monitor Widget. Now where do I look at the charging speed? Sorry I'm a noob at this. :p

I just see 'AC plugged'. Is that it? Or can I see the actual charging speeds?
[Samsung Galaxy Nexus] kuronosan:
Goo also doesn't update my twrp to the latest. I'll try downloading from dolphin.
[Samsung Galaxy Nexus] MBQ_:
Sup :)

If you want more detail, let me know.

(Oh, this is also a preview for MBQs CPU guide 2.0 ;))
[Samsung Galaxy Nexus] kuronosan:
Finally got it to work; love it.
[Samsung Galaxy Nexus] zoomy942:
Got what to work?

Tiny, any word on timer slack? I saw Franco fixed it on his but your kernel is best
[Samsung Galaxy Nexus] tiny4579:
I haven't had a chance to work on it yet. I also need a way to set that one parameter on boot. Maybe a ramdisk edit with sed. I believe the other could be done in init.d.
[Samsung Galaxy Nexus] zoomy942:
You take your time good sir.
[Samsung Galaxy Nexus] midnightdevil66:
Gotta admit that I tried multiple kernels on my toro but keep coming back to tiny as it plays the best with my phone. Right now running it with slim bean and running like a champ. Thanks tiny!

Sent from my Toro
[Samsung Galaxy Nexus] tiny4579:
I believe to have it implemented now. The only thing that may be confusing is there is is no logical reason to give a kernel bump without any code changes to the kernel itself at all though I should bump the version just so people know that something new or a fix is in place.

Oh, I haven't uploaded it yet.
[Samsung Galaxy Nexus] omniatic:
5.1a?
[Samsung Galaxy Nexus] tiny4579:
Close, 5.1.1. I never liked letters in release versions.

This is the same 5.1 kernel you all know and love. I bumped versions for differentiation. The only change is that I added scripts to the zip to edit the ramdisk to enable timer_slack and also provided an init.d script to set it to the default value as mentioned in the FancyKernel thread that zoomy942 linked.
[Samsung Galaxy Nexus] zoomy942:
Awesome. Thank you sir!
[Samsung Galaxy Nexus] T-Keith:
How does the dynamic interactive governor work? Do I have to use another app or script?
[Samsung Galaxy Nexus] parkson:
Just set and forget
[Samsung Galaxy Nexus] normanx:
You going to be making anymore changes to the 4.3.0 for 4.1.2? Just curious as it works flawlessly anyway.... Thanks so much for all you have done thus far.
[Samsung Galaxy Nexus] gpzbc:
I just tried Tiny kernel for the first time and I am quite pleased. I am running it with Shiny ROM and am getting some of the best battery life I have ever had on my GNex.
[Samsung Galaxy Nexus] flytechguy:
What governor are you running?
[Samsung Galaxy Nexus] gpzbc:
I am just running default settings (interactive).
[Samsung Galaxy Nexus] DoesntPostAThing:
IMO default settings are quite amazing already on this kernel.
[Samsung Galaxy Nexus] zoomy942:
Bumping for 5.2 for you guys.

Hot plug works great on interactive x
[Samsung Galaxy Nexus] gpzbc:
Great! Excited about the enabling of BIGMEM. Thank you!
[Samsung Galaxy Nexus] ashclepdia:
seeing this as a gmail notification as a response had me excited that Tiny added this in.

:(

did i miss something?

(i have my own reasons for liking bigmem versions lately... not just "wanting it Cuz other kernels have it" kinda thing lol)
[Samsung Galaxy Nexus] gpzbc:
What do you mean by, "did I miss something"? Maybe check out the OP.
[Samsung Galaxy Nexus] tiny4579:
I think it was addressed to me. He was probably saying, how did I miss the addition of the new cool feature.
[Samsung Galaxy Nexus] omniatic:
Surprised me, too. Thanks, works great. Gonna have to check in on things more often.
[Samsung Galaxy Nexus] zoomy942:
And we that thank you good sir.
[Samsung Galaxy Nexus] MBQ_:
Dude this kernel is really good
[Samsung Galaxy Nexus] tiny4579:
The one with bigmem or the builds before that?
[Samsung Galaxy Nexus] omniatic:
5.2 with bigmem is really good on the battery. I've noticed a big difference over the others.
[Samsung Galaxy Nexus] MBQ_:
All of em dude.
[Samsung Galaxy Nexus] ashclepdia:
Yup

Pretty much exactly what I was saying :)

I hadn't been checking the rootz forums lately, didn't respond here Cuz I caught up over there.

Finally did a full device cleaning(needed to be done haha) and I'm trying out vanir for first time, will be checking out the bigmem tiny versions for sure very soon!

Thanks tiny!
[Samsung Galaxy Nexus] konjiki7:
Is big mem a special version of the kernel or is it baked into 5.2?
[Samsung Galaxy Nexus] bluerez79:
I believe baked in
[Samsung Galaxy Nexus] chrisloveskaos:
bumps
[Samsung Galaxy Nexus] tiny4579:
For new build?
[Samsung Galaxy Nexus] kmcrane:
Yes! There's lots of rumors on rootz about 5.3.... :)
[Samsung Galaxy Nexus] konjiki7:
Any advice on ocing the gpu to 512mhz?

I don't care about the CPU speed as much as the GPU since 4.3 utilizes the GPU more.
[Samsung Galaxy Nexus] Phazmos:
Just do it, I'm always at 512
[Samsung Galaxy Nexus] dereaper:
I've always got mine at 512 it should be fine it will use the same voltage regardless of the frequency anyway
[Samsung Galaxy Nexus] tiny4579:
Higher frequency uses more power even if the voltage is the same. I think 384 is the best combo of speed and battery.
[Samsung Galaxy Nexus] dereaper:
sorry about that could have sworn I read somewhere that they all used the same voltage somehow , my bad
[Samsung Galaxy Nexus] tiny4579:
Voltage is not the only factor in power consumption. Frequency is as well. They may be the same voltages as each other. I think 307 and 384 share voltages at least.

EDIT: To clarify, the voltages are the same at 307, 384, and 512 MHz. So you won't see a big increase in power consumption. Though, one formula that describes power consumption is P = cfv^2 where c is capicitance (which we'll assume is a constant) and f is frequency and v is voltage. As you see voltage has a bigger impact on power usage than frequency but frequency can affect power usage.

Also, 5.3 should be out tomorrow.
[Samsung Galaxy Nexus] ashclepdia:
I believe you may be referring to I think imoseyon's comments on this subject when there was information from a Google developer stating that the power consumption from OC to GPU outweighed any benefit.

There was mention that imoseyon had UV the GPU when running at higher freq enough so that it was actually using a lower voltage than the STOCK GPU freq did at stock values. And thus the added battery drain was in turn WAY LESS than what it was thought/claimed to be.

So even tho of course the battery drain is slightly more, its actually pretty negligible.

In my own experiences, I really don't see any kind of noteworthy difference in battery life due to OC of the GPU freq. But then again, on the Gnex I haven't seen much performance gain from GPU oc either. It's just the way it is from what I understand. The N7 is different story. When I had mine I used to OC GPU and get MAJOR performance gains in heavy gaming and even 'daily usage' with slightly more impact on battery life(tho not enough to be a major detriment too my normal expectation)
[Samsung Galaxy Nexus] johnco1972:
Will 5.3 be built on linaro 13.09?
[Samsung Galaxy Nexus] konjiki7:
I get artifacts and tearing when i try 512mhz with this kernel. And the phone freezes...work with golden though. I prefer this kernel due to the higher network Io.

There several games that simply are not smooth on this phone unless you're at 512mhz. Do you think a slight jump in voltage will grant some stability.
[Samsung Galaxy Nexus] tiny4579:
Maybe but try 384 first as your phone may not be able to handle that voltage. There is no GPU voltage control code on the gnex in existence so it'd have to be added manually. I can't tailor in every way to every user though I try.

If needed I can bump the 512 voltage up slightly for the next release.
[Samsung Galaxy Nexus] konjiki7:
384mhz has always worked well. Understandable there is no way you can anticipate how everyones phone is going to react. Sound like the next build is going to be the holy grail of kernels for my gnex.
[Samsung Galaxy Nexus] tiny4579:
I'm going to see what lean and Franco are set to for 512. I may be due for a voltage increase for that speed anyways.

I plan on keeping 5.3 similar to 5.2 except a few small changes (maybe just the voltage change and asram). That should be a pretty much final kernel. I'm not going all out as much on the 5.x builds.

EDIT: Both mine and lean are the same voltages for 307/384/512. Franco actually uses a slightly lower voltage for 384 and a slightly higher voltage for 512 than I use.
[Samsung Galaxy Nexus] tiny4579:
Yes, but I doubt there will be any noticeable improvement from Linaro alone but I like to keep my trend of building with the latest linaro toolchain.
[Samsung Galaxy Nexus] sajty:
SlimBean stable is out.I will wait for Tiny 5.3 and give it a try.We will see,which kernel is better,Fancy or Tiny :).
[Samsung Galaxy Nexus] dereaper:
all you're going to find out is which one works better for you
[Samsung Galaxy Nexus] tiny4579:
My 5.3 build rebooted last night. Not sure if it was the undervolting or ASRAM that caused it. I need more time to test.
[Samsung Galaxy Nexus] tiny4579:
5.3 is out. It's only available on the mbqonxda.net mirror right now due to goo.im issues - check the OP for the link. I will try to upload again to goo tomorrow.
[Samsung Galaxy Nexus] MBQ_:
You're still using my site.. :D
[Samsung Galaxy Nexus] zoomy942:
Flashing over 5.2 now. That ok with this one?
[Samsung Galaxy Nexus] omniatic:
Bootloops...lots of them. Got so many that I had to revert back to 5.2. Lost a few apps, and my theme, but restored my backups. Used default settings, got to the point where I had to pull the battery. Sorry, couldn't get a logcat or last kmsg. Just didn't want to stay running.
[Samsung Galaxy Nexus] gpzbc:
I am excited about trying 5.3 but unfortunately my phone keeps rebooting constantly with 5.3. Back to 5.2 for me.
[Samsung Galaxy Nexus] kmcrane:
Anybody have a successful flash of 5.3?
[Samsung Galaxy Nexus] Alton (Halo 2):
Bootloops... Bootloops everywhere
[Samsung Galaxy Nexus] gkaurin:
Flashed fine, but I have had random reboots and apps that have gone missing after I had used them to minutes prior. Just went back to 5.1. It ran good for about 5 hours then got screwy.
[Samsung Galaxy Nexus] tiny4579:
Ick.

Check the fine size for me guys. Maybe a bad upload. Not sure. It was fine for me.
[Samsung Galaxy Nexus] loverppc:
+1
[Samsung Galaxy Nexus] kmcrane:
Not true bootloops.. It loads perfect, and boots fine. Lasts about 10 seconds.. Then reboots. And will reboot forever. I tried clean flash and dirty flash. 4.55 mb file size. Flash 5.2 and all is good.
[Samsung Galaxy Nexus] claytonjn:
Here's the MD5 I have for 5.3: 064b3b68cd484dc0c966bf77419e980f
[Samsung Galaxy Nexus] tiny4579:
So guys I can kind of see what you're talking about. It doesn't seem to be a bad download. If anyone knows how to compile can they try to build with the regular aosp toolchain? I think its either the linaro 4.8 toolchain or the GPU commit I did.

The last_kmsg I have shows a PVR error. It's probably the GPU commit. What GPU speeds are you guys at when you tested?
[Samsung Galaxy Nexus] MBQ_:
384MHz has historically been the most 'stable' for Tuna.
[Samsung Galaxy Nexus] konjiki7:
I too got reboots untill i went into trickster mod. After that i've been fine.

512mhz has always worked on golden kernel.

Seems to be working fine on this kernel now.
[Samsung Galaxy Nexus] kmcrane:
That's when it would reboot for me. I open trickster and move a couple pages and bam reboot, before I could change anything.
[Samsung Galaxy Nexus] konjiki7:
I had to roll back because the 5.3 started bootlooping
[Samsung Galaxy Nexus] johnco1972:
Tried the 5.3kernel. It looks like it made it about 75% through rebuilding the dalvic when it seems to have stopped. My touch screen and hard buttons were unresponsive. Tried waiting about 5 min, but could not wake the phone up after screen timed out. Had to revert back to previous kernel.
[Samsung Galaxy Nexus] MBQ_:
That's frustrating. :|
[Samsung Galaxy Nexus] tiny4579:
So it seems likely that it's the 4.8 toolchain causing the stability problems. I had forgotten that 4.8 is problematic on the Galaxy Nexus.
[Samsung Galaxy Nexus] konjiki7:
Codefire rom is built off 4.8 toolchain. It comes package w/ lean kernel... ( not sure if lean is built of linaro)
[Samsung Galaxy Nexus] tiny4579:
Yes but what toolchain for the kernel? 4.8 is perfectly fine for the ROM but there seem to be reboot issues with 4.8 for the kernel.
[Samsung Galaxy Nexus] konjiki7:
Yeah unfortunately I have no idea what lean is built off. Maybe someone else could chime in.
[Samsung Galaxy Nexus] tiny4579:
I believe they use Linaro 4.7 toolchain to build the kernel. Now the question is whether the ROM uses a prebuilt lean kernel or builds it with the ROM. If the kernel is prebuilt, it's going to be the Linaro 4.7 toolchain. If it's built with the ROM, it's up to the ROM developer to decide.

Anyway, 5.3.1 is up on the mbq mirror. If all goes well, I'll add it to the OP and goo.im.
[Samsung Galaxy Nexus] kmcrane:
Back when it was Eos they ran lean kernel exp 230... And updated it to the rom as the kernel was updated.

There is a noticeable lag using that kernel compared to yours.
[Samsung Galaxy Nexus] konjiki7:
Thats why I was trying provide a lead to the issue w/ 5.3.

I got some interesting data to the post

---------- Post added at 12:31 PM ---------- Previous post was at 12:18 PM ----------

Stock asop

anatutu 7353

Ram 1263

CPU interger 1770

CPU float 1370

2d GPU 497

3d GPU 1832

Io 365

SD r 67

SD w 189

Tiny 5.0

anatutu 7606

Ram 1289

CPU interger 1816

CPU float 1377

2d GPU 509

3d GPU 1913

Io 435

SD r 80

SD w 187

Tiny 5.3.1

anatutu 10597

Ram 1392

CPU interger 1885

CPU float 1378

2d GPU 585

3d GPU 3067

Io 452

SD r 79

SD w 187

Golden

anatutu 7606

Ram 1289

CPU interger 1816

CPU float 1377

2d GPU 509

3d GPU 1913

Io 435

SD r 80

SD w 187
[Samsung Galaxy Nexus] creepinm3:
What kernel version is this? I'm curious because I like to compare each version.
[Samsung Galaxy Nexus] tiny4579:
[MENTION=3850256]konjiki7[/MENTION], I guess since you were able to benchmark 5.3.1 then that means the reboot issue has been solved.
[Samsung Galaxy Nexus] zoomy942:
It has been for me. Solved and working great. What was the issue in the previous one that you fixed?
[Samsung Galaxy Nexus] tiny4579:
There were random reboot issues in 5.3, most likely due to the Linaro 4.8 toolchain. I just switched to Linaro 4.7 for 5.3.1.
[Samsung Galaxy Nexus] gpzbc:
5.3.1 seems to be working well for me.
[Samsung Galaxy Nexus] creepinm3:
DELETE.
[Samsung Galaxy Nexus] tiny4579:
Edit. Never mind
[Samsung Galaxy Nexus] wmarcin:
So far, so awesome. No problems. Even smoother than the previous version.

Thanks tiny4579!
[Samsung Galaxy Nexus] konjiki7:
If you haven't downloaded 5.3.1 you need to do it now absolute perfection!
[Samsung Galaxy Nexus] DavidFlory:
Total agreement! 5.3.1 is GREAT. :laugh:
[Samsung Galaxy Nexus] zoomy942:
1440 interactivex. Works great.
[Samsung Galaxy Nexus] konjiki7:
What are some governors you would recommend for this kernel?
[Samsung Galaxy Nexus] sivarticus85:
What rom are you guys running along with this kernel?
[Samsung Galaxy Nexus] konjiki7:
Codefire Xperiment for me
[Samsung Galaxy Nexus] omniatic:
Tiny's...are there others?

Can I assume that 1080p video recording will work again?

Yup, it does.
[Samsung Galaxy Nexus] gpzbc:
Shiny is the smoothest for me.
[Samsung Galaxy Nexus] MBQ_:
So 1080p works? :D
[Samsung Galaxy Nexus] claytonjn:
Just tested and it worked for me.
[Samsung Galaxy Nexus] MBQ_:
Sweet! Was going to flash this on my next flashing of my self-compiled Vanir no matter what, but that is the icing on the cake! :highfive:
[Samsung Galaxy Nexus] shag_on_e:
Wow, I've been just checking the tiny goo site from my bookmarks, I had no idea there was a 5.3.1! And I like the changes I see, it'll be nice to get full recording back with a RAM boost. My ignorance cost me on this one. Thanks for the great work tiny!

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] d00dr:
Precisely!
[Samsung Galaxy Nexus] tiny4579:
The goo.im server is in a read-only state. I can't upload anything to it right now so I had to use the mirror. The mirror should be faster anyways.
[Samsung Galaxy Nexus] zachdroid:
Anyone have a dl link for the 5.3.1 download. When I go to goo, all I get is a screen saying welcome to nginx! Needless to say, that sucks, lol.

If anyone has a link or a mirror, I would really appreciate it.

Thank you.
[Samsung Galaxy Nexus] cujo6801:
Give me a minute..

sent from the DOG pound
[Samsung Galaxy Nexus] zachdroid:
Sweet, thank you very much.
[Samsung Galaxy Nexus] cujo6801:
Here you go

https://db.tt/8vDTg53P

sent from the DOG pound
[Samsung Galaxy Nexus] zachdroid:
Thank you very much, getting ready to flash now
[Samsung Galaxy Nexus] cujo6801:
Anytime bro...

sent from the DOG pound
[Samsung Galaxy Nexus] tiny4579:
For future reference, the op also has a mirror.
[Samsung Galaxy Nexus] wmarcin:
Hello tiny4579. Do you have plans to work on a Kit Kat kernel? It would be superawesome if you do. :)
[Samsung Galaxy Nexus] sajty:
Good question.
[Samsung Galaxy Nexus] gpzbc:
Is 5.3.1 not compatible with 4.4?
[Samsung Galaxy Nexus] wmarcin:
Good question.
[Samsung Galaxy Nexus] T-Keith:
I would say no. It is never a good idea to use a kernel unless it is specifically made for the Android version. Most kernels need to be updated.
[Samsung Galaxy Nexus] tiny4579:
This is not always the case. This is generally the recommendation for supported nexus devices.

Go for it. It's not like there's new source out for 4.4. The 4.4 ROMs use the 4.3 stock kernel so why would mine be any different?

TL:DR; it will function the same as the kernel that is built with 4.4 ROMs which still use the kernel from 4.3.
[Samsung Galaxy Nexus] DavidFlory:
I have installed 4.3.1 and am running KitKat 4.4 and all is working. Still testing but it seems fine.
[Samsung Galaxy Nexus] zachdroid:
What device and what rom are you on?
[Samsung Galaxy Nexus] DavidFlory:
from my signature:

Device: Samsung Galaxy Nexus (Toro)

Carrier: Verizon Wireless, Kernel: Tinykernel 5.3.1

ROM: Shiny ROM - KK 4.4 KRT16M - 11/02/2013

(a refugee from MMuzzzy)

which, I guess, does not show in Tapatalk.
[Samsung Galaxy Nexus] zachdroid:
Sorry, yeah, I didn't see it while mobile. Thanks for the heads up. I do appreciate it.
[Samsung Galaxy Nexus] sajty:
Trying this kernel for the first time. Performance looks promising, but I really miss 2 things:

1) 5xx MHz step

2) bfq scheduler

Any plans with those things?

Sent from my GN
[Samsung Galaxy Nexus] wmarcin:
Quick question: anyone else having trouble with Bluetooth auto-connecting since 5.3.1 update. I actually have to unpair and re-pair with car Bluetooth each time I want to use it. Before, it was auto-connecting just fine. Once it's paired it works fine.

I'll try again after clearing Bluetooth Share data and cache.
[Samsung Galaxy Nexus] tiny4579:
When did it last work fine? I haven't made any changes to Bluetooth. It's the same as it was in 5.0, 5.1, and 5.2.
[Samsung Galaxy Nexus] wmarcin:
Thanks for a prompt response, tiny. BT definitely worked fine with your previous kernel (5.2, I think). Then I didn't use it for a week or 2, and I think I upgraded to 5.3.1 during that break. At first, I didn't notice the problem, because I switched cars, and the external BT-to-Aux adapter I was using never auto-connected for me. I deleted the pairing for my regular car, as my temporary car with BT adapter erroneously tried to use that pairing. I re-paired with the BT adapter, as it couldn't connect to my previous pairing, either.

Now that I went back to my regular car (with built-in BT), I keep having to re-pair (which is a 5-step process) BT, as it doesn't recognize the existing pairing.

BTW, clearing data & cache did not help.

I thought it may be kernel related, because other than updating apps, I didn't really change anything about my phone.

I could reflash 5.2 to see if it makes any difference, but I really like 5.3.1. Or just wipe cache and dalvik cache and.

I'll play around -- I just wanted to get a feel if it was an isolated incident.