So I stepped out of my OG droid and into the new s3 (awesome btw) and now I have this droid laying around calling my name..
Its rooted and flashed to jellybean, not sure which ROM because I did it forever ago.
I basically want to mount it on my rc car, and take video with it. I understand this is just as simple as hitting the record button, but I also want to be able to track top speed.
Problem is, my GPS doesn't work with the jellybean ROM, and I don't know of any apps other than Google Tracks that logs speed.
Should I flash back to the original 2.3.xx or is there a faster gingerbread ROM out there with working cam and GPS?
Also does anyone know of a speed logging app?
Thanks!
Sent from my S3 Pip-Boy
Bump?
Sent from my S3 Handcomputer
I can't say anything about droid roms but there are plenty of them.
I think measuring speed with gps is possible but the results are very inaccurate.
You can search for apps in the Play Store for apps, like this one for example.
Thanks a lot that was about what I needed, I guess I was just searching the wrong terms..
Does anyone know if I'm going to have any problems downgrading from from jb to honeycomb?
Sent from my S3 Pip-boy
Your welcome.
Downgrading shouldn't be a problem, you only have to wipe everything, even data.
( I'm not sure if you can find a perfectly working honeycomb, if you find at all, as it is developed for tablets. I think you should stick to a stable froyo or gingerbread rom. )
Sorry it been a while, but today I finally flashed back to steel droid. GPS works again and I took it for a test run on my RC truck, and I recorded a top speed of 57mph!
Now I guess its time to fab up a mount..
I zip tied it down, and flipped the truck going about 50. Phone whats fine but I blew a shock.
Pffffffffffffffffffftt.
Is the of droid comparable with an otg cable? If so would it be possible to rub the otg cable from the d1 to a gopro camera? Anyone have any ideas on how to make them work together with GPS speed and video
Pffffffffffffffffffftt.
Related
well, i'm not really sure what i did but i seem to have managed to stop autofocus from working. this is a real problem because it means the barcode scanners can't focus.
i haven't been monkeying around in root or anything (obviously) just installing and uninstalling random apps, but i'm at the bottom of the android learning curve and don't really know how to begin trouble shooting this.
any advice on where to begin would be appreciated.
thanks
I actually think I may have a very similar issue (as it ONLY happens when using a bar code scanning app) but I thought it was just me. Is this what is happening to you...
When I am using a bar code scanning app, the camera starts focusing on the image and just as it gets in focus, it goes out of focus again and then repeats this cycle endlessly. Sometimes it is able to get a lock before it focuses again but not always. I thought it might be a low light issue. I tried turning up the light and it wasn't much different though.
I have this problem, too. I can't focus the camera, it makes the sound, but there is no change at all in the focus when I tap to focus. Also, barcode reader / shop savvy is useless, as the focus on the barcode never occurs.
It seems like this happened when I went to 2.2 via one of many ROMs I've tried.
I suppose it could just be a hardware issue?
What rom and radio are you guys using?
Sent from my Incredible using XDA App
Virtuous 2.7 with the default adrynalyne Kernel
Radio is 2.15.00.07.28
in virtuous 2.7 the focus on my camera sux, especially for night pics w/ flash.
radio 2.05.00.06.11
Just sharing my two cents. I'm running virtuous 2.7 with king's kernal #4, rooted with s-off and 2.15 radio, also on 2.2. Just checked camera after reading this thread and not experiencing any probs thus far. Auto focus working, using touchscreen to take photos.
Im a newb, so I didn't do any modifications other than following directions on this site for rooting, adding roms, etc.. Not any help to you guys, sorry.
I tried downgrading back to stock 2.1, then applied the OTA Update.zip to 2.2, still no luck with the camera focus.
I have a new DInc coming to me under a warranty claim with Verizon.
Hold 'er steady...
Same story for me - won't 'lock on' to the image in order to scan the barcode ~ stock camera. Also tried the EVO camera available in the one of the ROM Manager d/l sections - not much different - for me.
Anecdotally, oddly, I let someone else try w/ my handset, and it worked for them.
SO...... either they have a more steady hand, or.....
Not being able to post on the Development sections cramps on my style a bit, but I have a couple of questions:
* First of all, I am still on Oxygen, do you guys think there's any good reason to switch? I like Oxygen a lot and apart from a couple of issues (see below) I've been very happy with it... Will dzo ever show up again and merge the new drivers into his release?
* Have the camera and GPU driver from the official 2.3 been ported to any other ROM?
* I've been seeing a lot of ICS related ROMS in Development as of late, is there a fully functional ICS ROM yet? What's stopping us, since it seems almost every other device is making some progress with it (i.e: having hardware acceleration enabled, radios working, etc.)?
Problems with Oxygen:
* Light Sensor behaves strangely: for example, with auto brightness enabled, turning on or off the light in my room makes no change in screen brightness. If I put the device close or directly under a lightbulb it will only then begin to change. I can confirm this with some sensor testing apps. Is there any way to calibrate the light sensor?
* Microphone acts strange: I have never seen anyone report this, but when I connect headphones, then try to use for example voice dialing or voice commands it will not work (wait forever) or simply give an error. If I disconnect the headphones after I tried to use voice it will never work again unless I reboot. If I connect headphones, never use voice, and then disconnect them and use voice it will work as it should
* Signal Strength very irregular: I live in a area with difficult reception, but signal strength is insane, sometimes is goes from 0 to full bars like no big deal
* Camera's FPS very jumpy (new drivers will fix this?)
* No access to internal storage: I knew this going in, but still...
* Flash videos sometimes green and overlapping the screen. This happens with both the YouTube app and any video player that can play FLV. It only happens from time to time and I can't reproduce it.
I went straight from stock (TMN Portugal) to Oxygen, never messed around with any other ROM (I tried CM7 for half an hour or so) but these little things start to bother me, plus it breaks my heart to know that the camera and GPU could be much smoother just by using different drivers. It also scares me that Huawei disabled the standard method of installing Recovery and rooting, so I'd prefer not to upgrade to the official ROM right away. So, is it worth to change ROM at this point? Can you help me with any of my problems with Oxygen?
Hi!
I tryed "all" ROMs I found here in XDA, Oxygen for me is not enough, it just lacks of "options" I love the Cyanogen Settings, you can do a lot of customizations there. Im on custom ROMs for 5 months now, never had a problem with the phone itself. Strange rebooting, camera stopped working and drainage of the battery does NOT count in here. I would suggest you try CM for more than a half hour since - in my opinion - it is the best. I hate the original Froyo, because it lacks of customization. So MIUI is not an option for me, it is just to simple. I was thinking I know all about flashing, but yesterday I just bricked my u8800, simply because I did not notice the + on the end of the official 2.3 update and installed update for u8800+.
My suggestion is, to follow guides here on XDA (they are excellent) and try all the ROMs, and see which one suits you best.
I'm also very happy with Oxygen, I'm still on r1 and have no major issues at all, so thank you very much dzo!
But I hope for the future that dzo will continue to update this rom so we can get better drivers for camera and other small fixes. It looks like the official rom will never be an stable option for us...
Mach III
I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app
So i finally gave cm 12.1 a chance because it's been rolling for a while now... and i was actually pretty impressed. The one issue i couldn't deal with is the bluetooth audio playback in my car. Basically it was playing too fast, then pausing every 10-20 seconds and then continuing to play too fast again (also at a slightly higher pitch). I was able to temporarily fix the problem by turning bluetooth off and on but it came back. other than this i didn't see many issues and thought it was pretty good, but for no i'm going to go back to stock until this issue is fixed, i did find that it was already reported to the cyanogenmod team and they are already working on a fix so i'm waiting impatiently until it's fixed and i'll probably be moving from stock kitkat as my main rom to cm 12.1. How has everyone elses experience been with cm 12.1 nightlies so far?
What doesn't work. (if i missed something here post so i can update)
- saving 4k video (1080p works tho)
Battery life ?
- used to be terrible but it's almost as good as stock now but with better performance.
hey
i would like to use CM as i was doing that on my Moto G. the questions I have to users of the newest CM version:
- does quickcircle, google text-to-speech, intelligent screen (LG app) features work?
- what is the quality of videos and pictures taken by the phone running CM opposite to android v20i?
thank you.
Brtnsk said:
hey
i would like to use CM as i was doing that on my Moto G. the questions I have to users of the newest CM version:
- does quickcircle, google text-to-speech, intelligent screen (LG app) features work?
- what is the quality of videos and pictures taken by the phone running CM opposite to android v20i?
thank you.
Click to expand...
Click to collapse
1. Quickcircle won't work. To make it work again you have to install a special app. Google text-to-speech works ok for me (I haven't test it too much). LG features/apps won't work
2.For me the quality of pics and videos are the worst I have ever seen!!!! (Much better in the stock LG)
My experience with CM12.1 was average. I was waiting for something better. Camera is awful in the Custom roms. Battery life wasn't the best. In terms of performance the cm12.1 is better than the stock lg.
i've only been running cm 12.1 for a few days now so i don't have alot of substantive input, i did find a fix for the bad bluetooth car audio using a macro/tasker app but i think they have fixed it in the nightly released today, i'm downloading it now it says bluetooth stream parameters in the patch notes so i wont bother sharing my fix until i try this nightly to see if they already fixed it. i'll give a better review of whats working and the camera/video quality after i have a chance to play around with it more.
by the way anything running ART instead of DALVIK cache/runtime is going to perform better but it's at the price of xposed modules and such, i'm not expert on it but i know they switched to ART cache/runtime to be more competitive with the iphone. On Kitkat and lower an android device needs better hardware to output the same performance as an iphone with lesser hardware. ART should fix that problem. If you are curious google ART vs DALVIK
*edit* yeah bluetooth is fixed with the newest nightly update... atleast for my car which is a mazda 3. (yay)
Avrage camera and bugs like video not saving after recording is main culpit to not use CM 12.1. Otherwise it is good as clean android can be.
it's getting alot better every day now
netmaniack said:
Avrage camera and bugs like video not saving after recording is main culpit to not use CM 12.1. Otherwise it is good as clean android can be.
Click to expand...
Click to collapse
Videos do save. It is a issue with 4K video ONLY. Switch to 1080p video and videos save just fine.
c_brown93 said:
Videos do save. It is a issue with 4K video ONLY. Switch to 1080p video and videos save just fine.
Click to expand...
Click to collapse
I found that myselfe, tnx. But I believe that issue is fixed already. Maybe Im wrong, but I did see in changelog or other forum. Maybe someone can test it?
I switched to stock kitkat, I love CM, been running CM since it was 10.1, the problem is that it starts really really fast and after a while CM 12.1 becomes laggy it drives me crazy, other than that is the camera quality which doesn't bothers me as the performance issue,
I guess we'll need to wait for LG to release the G3 source file but who know's when that's gonna happend
good news the latest daily added some balancing between power and battery life. I went from losing a huge chunk of my battery during work when my phone is in my pocket to going 9.5 hours at work and coming home with 94% battery. (that is alot of standby but i use my phone at lunch and have bluetooth running for about 50 minutes of driving). Basically it got alot better, i'm not sure what they did but i did notice that there is a balanced setting in battery screen that i didn't notice before. Anyways I think those who were concerned about battery drain my have had their wishes answered over the last few nightlies.
netmaniack said:
I found that myselfe, tnx. But I believe that issue is fixed already. Maybe Im wrong, but I did see in changelog or other forum. Maybe someone can test it?
Click to expand...
Click to collapse
i still can't get 4k video to save but 1080p did.
Do knock on and knock code work?
Lucenzo7 said:
Do knock on and knock code work?
Click to expand...
Click to collapse
Knock on works but knock code doesn't, which is quite normal considered it's an LG feature.
Lucenzo7 said:
Do knock on and knock code work?
Click to expand...
Click to collapse
Partly working. You can turn screen on by clicking anywhere, and turn it off by knocking at notification bar.
Phone encryption not working?
I've just flashed the 20150603 CM12.1 and I cannot seem to get the phone encrypted. On the reboot to start the encryption, the phone gets stuck in the CM boot animation and the encryption process never starts. Any ideas or suggestions? Many thanks in advance.
I'm on 06/05 nigthly. When I plug the phone in my computer, it's not being recognized. If I change from MTP to PTP, then it works.
I've tried going to Device Manager, and could see that my phone is being recognized as a Nexus device. I tried installing latest drivers from Google's website, but I got a message saying that I'm already on the latest version. So that didn't do anything. I've tried uninstalling that "nexus" driver and rebooting my PC, but it somehow came back when I plugged my phone in. Trying to update gave me the same message.
If I run "adb devices", I can see that there's no devices (it's enabled in developer settings). If I enable ADB over WiFi and try to connect -- it works, and I can do whatever I want. But only over WiFi and not via USB.
Tried different cable and different port as well.
Okay so I'm gonna describe my problem as clearly as possible and will hope someone can find a fix for this.
Device: Nexus 6P
OS: Android 6.0.1 (latest vendor & security patch - June 2016)
Bluetooth devices used: Sony MDR 600BT, SOL republic tracks air, jbl synchros earphones, jbl flip 2 speaker.
1) pair earphones/speakers
2) start playing music on earphones/speakers
3) works fine on first run and when screen is off
4) when I switch on my screen to change the song the music stutters for 10 full seconds, then stuttering stops.
5) I change the song and again put screen off, works fine.
6) i put my phone in my pocket and suddenly my phone audio stops skipping??? Wtf???
7) so I change my pocket and put it in my hoodie pocket. (Nearer to earphones - maybe distance is the problem I thought)
8) audio still skips............:crying:
9) put my screen on to change song, audio starts stuttering again like crazy and then stops.
10) I request anyone here to heed this request and tell me how to workaround this problem
Currently running latest android MM 6.0.1 and no improvement .....:crying:
I don't understand one thing - top of the line flagship device and still these problems? Not getting value for my hard earned money. This is wrong.
I tried it with my iPod and it works like a charm. No stutters. No skips. Nothing.
Tried different Bluetooth headphones too in case my Sony earphones were the problem. NO IMPROVEMENT SAME PROBLEM PERSISTS.
TRIED USING IT ON ANY BLUETOOTH SPEAKER THE ABOVE THINGS KEEP HAPPENING AND I AM GETTING REALLY ANNOYED WITH THIS PHONE WHEN IT COMES TO BLUETOOTH.
I'm sorry for agonizing so much. But I hope you'll can understand my problem. And hopefully there's a fix somewhere in the world.
I am having the same issue, and my searches came up with this:
http://forum.xda-developers.com/nexus-6p/help/bluetooth-audio-stutter-wake-unlock-t3384324
Is this a Play Music issue? I don't have these issues, but I don't use Play Music. usually stream through YouTube or something like that instead. Works on BT Headset and Sony BT head unit in my car.
blackwrx02 said:
Is this a Play Music issue? I don't have these issues, but I don't use Play Music. usually stream through YouTube or something like that instead. Works on BT Headset and Sony BT head unit in my car.
Click to expand...
Click to collapse
I can't speak for Zapjack12345, but I notice it with PowerAmp, Pandora, Spotify, YouTube, basically any app that is pushing audio through bluetooth. Audio is fine when the screen is off, but as soon as I pick up the phone, and turn it on to check notifications, things get screwy with the audio
Strange. I just checked with Pandora, YouTube, and IheartRadio and all seem fine with screen off and turning it on, using the pulldown menu, or changing songs. I'm using a cheap set of bluetooth earbuds from Amazon (no-name brand), and am stock with the phone, not rooted (yet) and on June updates. Phone was purchased in May new from Best Buy.
Same issue for me as well. I'm specifically using Amazon and Pandora most of the time. Its very annoying. On Chroma and franco kernel.
What rom are you using? This has been a well documented CM rom issue so any rom that uses CM as a base will and has had this issue since mid-January. Stock and AOSP based roms dont have this issue (from what I've seen and tried).
I'm currently using the 6/15 nightly for OMNIrom and do not have these issues.
As a sidenote, this was also an issue with Android N Dev Preview 2.
uodii said:
What rom are you using? This has been a well documented CM rom issue so any rom that uses CM as a base will and has had this issue since mid-January. Stock and AOSP based roms dont have this issue (from what I've seen and tried).
I'm currently using the 6/15 nightly for OMNIrom and do not have these issues.
As a sidenote, this was also an issue with Android N Dev Preview 2.
Click to expand...
Click to collapse
I'm currently on Pure Nexus 5/6/16. Nothing out of the ordinary installed. Tried clearing the Bluetooth cache, as the issue I am noticing was similar to issues that the Samsung S5 was having, but there was no difference.
I am going to look to go back to stock and see what happens, but looking at what OP posted, it looks like they're on stock, and having the same issue.
I am about to throw my phone in the sea. BT seems like it's getting worse and worse with each update. Cmon Google/Huawei. Don't make me lose faith.
Sent from my Nexus 6P using Tapatalk
krakerx said:
I am having the same issue, and my searches came up with this:
http://forum.xda-developers.com/nexus-6p/help/bluetooth-audio-stutter-wake-unlock-t3384324
Click to expand...
Click to collapse
I had a little less issues when using the Dev Preview 3 but there was another issue that arised that I hope gets fixed.
If you're using bluetooth when driving around when you lose signal or drop/gain data connection the audio skips for a quick second. Through past testing I've done working with kernel devs on 2 phones, the issue is related to how the hotplugging works for the cores. If only one core is running when the connection drops there is an issue with how the cpu ramps up and/or turns on another core to handle the workload. I thought this regression was pretty interesting seeing as one the things they were boasting about at the Google conference was how android would fix slow downs and issues when losing/gaining network connectivity with N. Hopefully it'll be fixed before final release.
akarol said:
I am about to throw my phone in the sea. BT seems like it's getting worse and worse with each update. Cmon Google/Huawei. Don't make me lose faith.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You and me both. I am on my 3rd 6P and my BT problems are still the same. If the BT problems were only effecting one particular device I could understand but my Microsoft band, BT earbuds and car all seem to disconnect continuously on a bare/stock phone.
Okay guys. I changed my ROM from Resurrection Remix to Paranoid Android and this issue has been solved. Thank you so much for all your help and answers!
Does anyone else have any updates regarding this issue? Literally wanted to throw my phone out of the window during the morning commute.
Zapjack12345 said:
Okay guys. I changed my ROM from Resurrection Remix to Paranoid Android and this issue has been solved. Thank you so much for all your help and answers!
Click to expand...
Click to collapse
Don't use cm based roms
Smallsmx3 said:
Don't use cm based roms
Click to expand...
Click to collapse
Yep, this is 100% the reason. It is a CM issue. AOSP roms like Paranoid Android and Pure Nexus don't have this issue. I love Resurrection Remix, but this is starting to bug me. I may jump to PA rom soon...
Smallsmx3 said:
Don't use cm based roms
Click to expand...
Click to collapse
Thanks. Was about to ask this question. It is a CM issue.
I have had issues with BT dropping randomly in my car on 2 different 6P's. No rhyme or reason, and it doesn't happen often, but annoying when it does. Happened on MM and DP4 currently.
On the flip side, my audio quality went down on my S7E over BT when my smartwatch was connected. Somehow, that doesn't happen with the 6P meaning I can keep my watch on in the car, so I am happy.
Hey, I just found this thread and surprised it took me this long considering I've been having this issue since I got my phone in November.
My 64gb 6P was stock until earlier this week, when I finally rooted and flashed xposed. The issue stopped the day I rooted my phone, and I was thrilled.
After reinstalling most of my apps and getting back into my routine, the problem came back. I've tried booting my phone into safe mode several times before rooting so I'm fairly confident the issue doesn't exist because of a specific app interaction, but I can't figure out what it is to save my life. I might backup again and restore to the backup I made right after rooting to see if I can narrow down the problem.
Other than that, I am very new to this stuff and honestly just thrilled to have found other people having the same issue.
I only experience the problem while connected to my car (2015 Chevy Cruze), and not any other bluetooth device.
Let me know if you guys find/have found anything I suppose?
I kinda have up on trying to narrow down the issue. I tried PureNexus, Paranoid Android, I tried different kernels, different cases. Still kept skipping and jumping, no matter how far, or close it was to my Bluetooth device (car stereo, speakers, home audio system). I went back to stock, no root, no Xposed, pure and simple Android, and I have not had a single issue, it's beautiful.