Thread: TunerView App Testers Needed!

Well she's workin now. I took your advice zen and after a few trys a box popped up that I hadn't seen before asking me for the bluetooth adapter code. It gave me a suggestion to try 0000 or 1234 and when I added 1234 hit enter the bt adapter finally connected. Didn't get a chance to run the car as it's kinda late so will tomorrow but the tps gauge was reading so it should work fine.

It looks like some android OS or hw issue. I never had those issues and hard to reproduce it, so its hard to fix too. I always check the crash reports, so if you have Force close and a Send report button appears just hit it and i will see where it crashed. Sometimes it doesnt help to find the solution but maybe i can find it.

My guess is that its a hardware or OS issue as its a Chinese head unit with a poorly hacked up Android KitKat ROM.

Personally, I would prefer that you do NOT fix the crashes as they are the only way I can easily get the software working on my head unit 100% of the time.

I want to fix all possible bug, but sometimes i get crash report that i don't understand how it happens.
For example on one device the RPM bar show a 360 circle when the values is 0. I don't know how it happens, because the RPM bar is hard coded. And its not a chinese low cost device, its a Moto X.