Develop Bugs

GPS not working on SlimKat 4.4.4

Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo

drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.

I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?

drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?

serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP

Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.

serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.

drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.

Installed CM 12.1 everything went fine, went to flash gapps, getting UID error

Coming from stock rooted / unlocked Touchwiz KitKat
Cm12.1 installed just fine but when I rebooted and went to flash gapps I get a non-stop error saying "there's an internal problem with your device, and it may be unstable until you factory data reset."
So I factory reset the device and even installed CM 12.1 without gapps and it still gives me this error.
Factory reset again, try my recovery and I get an error mentoning UID's being messed up (I did this and it did not help http://forum.xda-developers.com/and...on-finally-t3151579/post61729442#post61729442 ) . So I factory reset again and flashed CM 12.1 without gapps and everything is fine.
Boot into recovery and flash gapps and boom the error again. Seems like the only way to get rid of the error (After many trials and errors) is to Restore recovery -> factory reset -> flash rom. The only problem is when I also flash gapps the error comes back.
Now here is the part where I can use YOUR help, in TWRP I keep saying red text that says
"E:error opening '/data/data/com/google.android.gms/files/images/games/de7f5650'
E:error: Not a directory"
on everything I do, from formating the system to flashing a rom. I think this is where my problem lies.
Other notes: No sd card,
when CM is working, I am getting no reception (Looks like a full but has ! next to it)
When CM is working, the messaging app does not even open and just instantly closes

OK I'll break into parts I see 1: gapps 2 signal 3:msg app.
1: GAPPS
cm 12.1 is android 5.1.* so you need to verify you have correct gapps. Use gapps for 5.1 hopefully that will fix problem. Factory reset, flash cm 12.1, flash gapps 5.1, wipe dev/cache, and reboot. Should be working fine after.
2: Signal is due to rom bugs but usually due to bad/wrong apn settings or bad efs/modem pretty much all the time from my experience. So I'll break that down from easiest to the latter and hopefully we'll fix it.
a: check you apn settings and see the attachments. I'm on lte tmo so if you aren't the Google apn setting for your carrier.
b: flash back up of moden/efs
3: msg app might be fixed since gapps was installed but if not only thing I can think of is clear data/cache for msg app.
Hope I could help

these days I'd use LineageOS for the Note 3/SM-N900T (I use nightlies and my note 3 used on wifi only) I can't test the normal 2g 3g 4g or lte cuz I dont have a compatible sim card (I have a nano sim in my j7 prime so it won't fit) it takes a bigger sim so yeah......I have gapps installed for my android version and they work fine for me

BsB5068 said:
N900TUVUCNB4
Click to expand...
Click to collapse
Rolatnor said:
these days I'd use LineageOS for the Note 3/SM-N900T (I use nightlies and my note 3 used on wifi only) I can't test the normal 2g 3g 4g or lte cuz I dont have a compatible sim card (I have a nano sim in my j7 prime so it won't fit) it takes a bigger sim so yeah......I have gapps installed for my android version and they work fine for me
Click to expand...
Click to collapse
lineageos 16.0 is what I've been running on it, i needed a newer os cuz stock 5.0 was the last official version, and pokemon go was dropping support for the note 3 with stock roms, now switching to LineageOS 17.1 on my note 3 i'll update whether gapps works so you know
LineageOS Downloads
download.lineageos.org
LineageOS 17.1 is android 10

btw I have sd cards in all my spare phones 8gb normally, so I am recommending a small sd card 4gb-16gb because it makes it easier to flash roms with twrp

google play works, gmail works, yt works, sound works, flashlight works, and camera works on LineageOS 17.1
note 3 sm-n900t
i used the nano gapps from opengapps
the newest file version of lineageos 17.1 on their site

Experimenting with ROMs

I'm looking for an S7E/N5 hybrid with mostly everything working. Coming from a N3, this would be a Dark Lord ROM with fingerprint and NFC.
I started with a stock BPA1 phone which I unlocked/rooted. I wanted to upgrade to a true 6.0.1 ROM which meant upgrading firmware. I started with Odin flashing a tar.md5 of the CPD1 firmware - bad idea. It failed and messed up the bootloader. So broke phone.
I was able to Odin the stock BPA1_BPA1 and the BPA1_CPD1 firmwares. In each case though, it was very hard to obtain root. If it rebooted or locked up for any reason, I had to go back and reflash the stock firmware, wipe and reinstall kingoroot. Otherwise I was stuck in a bootloop with DL Mode saying I was locked. This is what lead me to fix it. I noticed after the first flash of samsung_unlock_n4-fix (root took that time and no crashes) it would bootloop. I went into DL Mode to reflash firmware but it finally showed Developer Mode. I gave it a shot and flashed twrp without issue. Instead of having to install the n4-fix twice or go through multiple roots, turns out that it took just took once to reclaim Dev Mode.
(I had been thinking that Dev Mode was wiped out with aboot when flashing the stock BPA1. Guess not)
So the bootloop I figured was due to a kernel issue. With Dev Mode, I Odin flashed TWRP. I formatted my sdcard and put a kernel on it, using twrp to flash it. And tada, working phone. This worked on both the BPA1_BPA1 and the BPA1_CPD1. So I was able to load the 6.0.1 firmware. It took so long to do this though that I didn't get a chance to try more than a few roms.
From a brief visit to these ROMs, I am still looking for something that has everything:
From T-Mobile:
Maximum OvrDrive 6.0.1 MM v.8 - Great ROM but I didn't have wifi afterloading it. I'm sure I was missing something to get it to work but I realized this was not an S7E port either.
Maximum OvrDrive S7 v3.7 - It's a 5.1.1. ROM and works well but is missing AOD, fingerprint and most importantly hotspot.
General forum:
Dr.Ketan 6.1.1 - could not get this to load. It bootlooped after flashing the M5 rom (910g?), kernel, datafix and supersu as per instructon. Will revisit.
Verizon forum:
Kyubi Note 5 Port - One of the first ROM I tried and it is amazing. This is a very stable ROM with almost all the bells and whistles. I wouldn't even look at another ROM except it doesn't offer AOD and a few minor tweaks (haven't figured out how to skin my status bar clock for example). I posted in the thread a fix for MMS btw. It's a 5.1.1 ROM of course and lacks in a few ways.
I'm still looking for a perfect ROM for me. Will update the list as I try them.

I flashed the Noble ROM yesterday. So far, so good.

If you get time this rom by @aukhan and the Emotriod team is great. It's a pure note 4 with edge features, but I can't remember if mobile hotspot works or not. I'm using the Nameless Rom at the moment and really enjoying it as well. On the Nameless Rom mobile hot spot works, I'll check to see if fingerprint works, everything else as far know works well. One more option is Kurama Rom, I got it to boot with data/mobile/wifi, but to be honest I didn't stick with it too long because as soon as I got it set up, the Emotriod Rom caught my eye and I just had to have it.

douger1957 said:
I flashed the Noble ROM yesterday. So far, so good.
Click to expand...
Click to collapse
Hahaha....I've been on Noble for a few weeks now, and just flashed hsbadrs cm13 7.17. release for a change. Noble is a beautiful rom, and I themed it with Marshmallow dark theme from the Samsung theme store. CM13 is just slightly more fluid, and used to be my favorite, Noble is by far the most stable s7 port on my phone.
Sent from my SM-N910V using XDA-Developers mobile app

Dr Ketan rom you need to flash rom then m5 fix right away let it boot (can take up to 11 minutes no longer average 5-6) dont sign into anything ( google, samsung, etc.) then go back into recovery and flash louforgiveno's data fix for your bootloader and ketan rom. then reboot. It has to be a clean flash in my experience. It will take about 5 minutes to get data signal but it comes. The roaming indicator off text stays on lock screen it does not mean you are roaming though (check in about device), there is a way to get rid of it but i didn't doesnt bother me.

Does anyone know if there is a way to add Wifi calling to any of the N910F roms?

UPDATE: I went back to Ketans Rom but on the BPA1 bl and it works very nicely. I had to utilize my MMS fix to get the native app to send mms. I'm currently working on finding an Xposed framework that boots. Neither Wanam mod's or the stock seem to fit. Ketens is so far the most kitted out N5/S7E rom I've seen, with even a cobbled together version of AOD. Anyone have any luck with Xposed running the H Vitamin kernel? I'm thinking of switching to some other kernel to see how it works.

kevintm78 said:
If you get time this rom by @aukhan and the Emotriod team is great. It's a pure note 4 with edge features, but I can't remember if mobile hotspot works or not. I'm using the Nameless Rom at the moment and really enjoying it as well. On the Nameless Rom mobile hot spot works, I'll check to see if fingerprint works, everything else as far know works well. One more option is Kurama Rom, I got it to boot with data/mobile/wifi, but to be honest I didn't stick with it too long because as soon as I got it set up, the Emotriod Rom caught my eye and I just had to have it.
Click to expand...
Click to collapse
Just curious what kernel and data fix are you using with the emotroid rom. I have tried Lous MMs fix v4 and also the 3b version but MMS is all not working properly.

Is there anything wrong with the mm bootloader? Seems like a lot of ppl Including me is having trouble flashing roms on it. So we Convert back to the lollipop bootloader... How can we get roms to work on the mm bootloader. I can't find any reason to this.

Most stable Rom for LG g-pad 7.0 v410?

Hi, I have the latest CM12 installed in my tablet, but I have a lot of issues, especially when installing multiple apps or if I try to change the Launcher. It gets into boot loop and there is nothing one can do but re-flash the rom, which is pretty annoying. It has happened to me already 3 times in a short while and I am thinking of flashing LineageOS. However, I hear it is still very buggy, especially the issues with wifi. So I would like to ask which is the least buggy Rom for 7.0 v410 or if there is a way to avoid CM12 from getting the problem with boot loop.
Boot loop has been caused when trying to change Launcher (because trebuchet regularly crashes), when installing x-plore file manager and in a clean flash when I attempted to install multiple apps at the same time. In all cases it got stack in boot loop, or would start only to restart after a while, endlessly.

Finally, I opted for LineageOS 14.1.
I had the 11-11 Nightly for some time and seemed fine. Today I updated to 25-11 Nightly. It feels maybe slightly laggy, but still checking it.
I have also installed "Best WiFi Keeper" app from play store and it generally keeps me connected. However, if connection is lost (e.g at restart or if I get out of range), I have to reconnect manually. I tried few apps for reconnecting but nothing worked. It appears that although the WiFi network is seen, the tablet cannot really re-establish the connection automatically.

I found Nothing stable yet.. In last few days, I have installed CM 12.1, same trouble.. I installed Tipsy and Tesle, unable to install apps from playstore. Tried CM 13 and Lineage OS latest build as you, Wifi Teathering and USB teathering not working and same problem with wifi connectivity. Keed posted if you find something better.. I shall too...

Tesla works great for me. I'm running a lollipop version that's still on androidfilehost; I'm not sure if GZR ever got updated beyond 5.1 for V410.
I've had CM 14.1 (long enough ago it was still CM and not LOS) on the tablet, and it felt like it would get laggy. That could just be from junk my kid installs though, but I don't seem to have that problem with Tesla.

I installed Tesla (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip from https://androidfilehost.com/?fid=24052804347807214) with open G apps but getting errors while installing apps from Play store(Some error code 963 - tried cleaning cache of playstore, play services download manager, removing google account and adding again - Nothing works). Same situation with tipsy. Any help?

kingzones said:
I installed Tesla (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip from https://androidfilehost.com/?fid=24052804347807214) with open G apps but getting errors while installing apps from Play store(Some error code 963 - tried cleaning cache of playstore, play services download manager, removing google account and adding again - Nothing works). Same situation with tipsy. Any help?
Click to expand...
Click to collapse
That is probably what I'm running, I don't have my tablet right now. I think I flashed it with opengapps nano. I didn't have to do anything unusual to get play store to work.
Tipsy uses the same base as Tesla and Validus. Since it is persisting across multiple flashes and roms, consider formatting the internal storage if it isn't too much hassle, the TWRP wipe where you have to type "yes" to confirm. Sometimes some remnants in userdata that aren't touched by the normal system/data/cache/dalvik wipe cause problems like this and can persist the way you're describing.
Just make sure you have rom and gapps on an external SD or you have confirmed you can push files to the tablet in TWRP over usb via mtp or adb before you blank the internal storage.

jason2678 said:
That is probably what I'm running, I don't have my tablet right now. I think I flashed it with opengapps nano. I didn't have to do anything unusual to get play store to work.
Tipsy uses the same base as Tesla and Validus. Since it is persisting across multiple flashes and roms, consider formatting the internal storage if it isn't too much hassle, the TWRP wipe where you have to type "yes" to confirm. Sometimes some remnants in userdata that aren't touched by the normal system/data/cache/dalvik wipe cause problems like this and can persist the way you're describing.
Just make sure you have rom and gapps on an external SD or you have confirmed you can push files to the tablet in TWRP over usb via mtp or adb before you blank the internal storage.
Click to expand...
Click to collapse
can you tell me if hotspot and usb tethering is working on tipsy? Thanks.

xdause said:
can you tell me if hotspot and usb tethering is working on tipsy? Thanks.
Click to expand...
Click to collapse
I'm on Tesla, but it has the same base as Tipsy. I don't have data on the tablet so it isn't a 100% conclusive test, but it doesn't seem to work. The switch for USB tethering never turns on. Wifi turns on but never connects properly. My laptop does briefly show connection then disconnects with both USB and wifi tethering. It could be because there is no data connection on my tablet, but looking through dmesg on the laptop gives me the impression that something on the tablet isn't working right.

kingzones said:
I found Nothing stable yet.. In last few days, I have installed CM 12.1, same trouble.. I installed Tipsy and Tesle, unable to install apps from playstore. Tried CM 13 and Lineage OS latest build as you, Wifi Teathering and USB teathering not working and same problem with wifi connectivity. Keed posted if you find something better.. I shall too...
Click to expand...
Click to collapse
I'm on lineageOs 14.1 which is alright though the wifi issue is still there. However, someone may have found a solution, but I don't know how to implement it. Check posts 207, 210 and 215 in this thread: https://forum.xda-developers.com/g-...eageos-14-1-v400-lg-g-pad-7-0-t3583952/page22

nicospanas said:
I'm on lineageOs 14.1 which is alright though the wifi issue is still there. However, someone may have found a solution, but I don't know how to implement it. Check posts 207, 210 and 215 in this thread: https://forum.xda-developers.com/g-...eageos-14-1-v400-lg-g-pad-7-0-t3583952/page22
Click to expand...
Click to collapse
Would you (or anyone who sees this) please tell me is it possible to flash TWRP if I'm on 5.0.2? Or must I downgrade first?
I'm rooted already. TBH stock is pretty solid and if the custom roms have too many bugs I might pass. But I would like to flash Viper4Android and don't think I've ever installed it without a custom recovery. Many thanks in advance.

KLit75 said:
Would you (or anyone who sees this) please tell me is it possible to flash TWRP if I'm on 5.0.2? Or must I downgrade first?
I'm rooted already. TBH stock is pretty solid and if the custom roms have too many bugs I might pass. But I would like to flash Viper4Android and don't think I've ever installed it without a custom recovery. Many thanks in advance.
Click to expand...
Click to collapse
I made the same question more or less, over a year ago here: https://forum.xda-developers.com/android/development/help-installing-cm-t3483074
You cannot flash another rom over lollipop and I've never seen twrp for android 5.0.2 for v410. I am not 100% sure because my question was a bit different, but I assume from the replies, that probably not.

nicospanas said:
I made the same question more or less, over a year ago here: https://forum.xda-developers.com/android/development/help-installing-cm-t3483074
You cannot flash another rom over lollipop and I've never seen twrp for android 5.0.2 for v410. I am not 100% sure because my question was a bit different, but I assume from the replies, that probably not.
Click to expand...
Click to collapse
Thanks. That's more or less what I thought. From what I'm hearing there are some bugs in the roms that no doubt aren't being maintained at this late stage so I think I'll stick with stock (would be nice to have a custom recovery though.)
Not that it matters (a year later) but lots of people root with Kingroot when there isn't another option and there's several ways to remove all the bits left behind and switch it to supersu.
Thanks again!

Well, I have a work around to stop wifi from disconnecting in lineage os. After that I did not know when wifi got disconnected and reconnected.
Just download E-Robot from playstore.
https://play.google.com/store/apps/details?id=com.bartat.android.robot
And set it to settings as per screen shot.

kingzones said:
Well, I have a work around to stop wifi from disconnecting in lineage os. After that I did not know when wifi got disconnected and reconnected.
Just download E-Robot from playstore.
https://play.google.com/store/apps/details?id=com.bartat.android.robot
And set it to settings as per screen shot.
Click to expand...
Click to collapse
It works! Thank you so much! It seems the LOS developers have stopped trying to fix the wifi issue but it is important. The workaround even works at restart, with some delay, but it works!
Just to clarify to newbies like me, where ssid you have to put the name of the network you want to connect. I wonder if one can add more networks, so it can connect to any saved network according to where you are. You think that's possible?

nicospanas said:
It works! Thank you so much! It seems the LOS developers have stopped trying to fix the wifi issue but it is important. The workaround even works at restart, with some delay, but it works!
Just to clarify to newbies like me, where ssid you have to put the name of the network you want to connect. I wonder if one can add more networks, so it can connect to any saved network according to where you are. You think that's possible?
Click to expand...
Click to collapse
That would be great.. I shall try.. if successful, I shall post results.

I have a uk410, the US Cellular variant of the v410. I tried the CM12.1 "stable" release cm-12.1-20151117-SNAPSHOT-YOG7DAO1K5-v410.zip found here (archive.org/download/cmarchive_snapshots), along with Open GApps nano for 5.1 (opengapps.org/?api=5.1), and quickly got the infinite rebooting issue.
I then switched to the Telsa ROM mentioned earlier in this thread (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip) found at androidfilehost.com/?fid=24052804347807214, again with Open GApps nano for 5.1 (build open_gapps-arm-5.1-nano-20180922.zip), and have been running it with no issues for two days. My wifi is connected, and stays connected (tested two different routers), Play Store and apps have been working fine, and no crashes so far.
I'm using TWRP 3.1 (twrp-3.1.0-0-v410.img).
Thanks for mentioning Tesla, @jason2678 !

So like all of you I was looking for a rom to install on this v410 7" tablet, and it looks like I should just give up or stick with 4.4.2 stock if I want to go through the rooting process.
Basically all the development roms end with the same problems, wifi dropping, hostspot not working, no ir blaster, volume problems, bluetooth errors, and several hundred posts about lolipop memory leaks crippling the tablet because of only 1gb mem.
So, I am asking all of you, is there any real reason to root it, besides going back to stock 4.4.2?
And lastly, is the stock 4.4.2 kdz image that is floating around a test version, and if so is there an actual official kdz image somewhere that isn't a test image?
Thanks...

CrDroid by far in my opinion. Lineage based, 7.1.2.
Also, e/ os has been unofficially released. No Google anything...an entirely new Google list operating system by lineage. It's lightning fast and runs magisk perfectly. It's basically like nothing you've ever seen before and if you look under LG g pad 7.0 on Android file host, go to the second page and click on the last user who goes by the name anonymous and you'll find the ROM there. I had no idea what it was until my g pad boot it up and I saw the e logo. I pretty much **** myself in excitement

Question Bluetooth Issues

Does anyone have issues with bluetooth? When I connect to my car it will reboot my phone in around 15-20 mins. I"m on crDorid now but it also happened on Syberia but everything was fine on stock global 12.5.2. I have already flash back to stock Miui and then reinstall crDorid rom, It still having the same issues. I have also turn off location scan for wifi and bluetooth.
Thanks

I have same issue but im in LineageOS, I tested ArrowOS and it was the same.

Swapped to evox and still having the same issue. I might just go back to stock rom.

I'll have to test it too.. I was bored to pair it to be honest but I'll do it to check it.

Not sure if it helps but I'm using another ROM with I think is not allowed on XDA (helluvaOS), and used a bluetooth headphone for 35min today, without problems.

spoonsports said:
Swapped to evox and still having the same issue. I might just go back to stock rom.
Click to expand...
Click to collapse
Spoonspots, I reinstalled Lineage Os and install imersity kernel and now its working fine, i dont know if it was for the clean installation or the kernel.

.

franko_m19 said:
Spoonspots, I reinstalled Lineage Os and install imersity kernel and now its working fine, i dont know if it was for the clean installation or the kernel.
Click to expand...
Click to collapse
Thanks for letting me know. I had to go back to stock because my phone was rebooting every 5 mins at some locations. But after I saw shadowam said that the banned OS was working so I gave that a try and its been good so far. Only 1 random reboot after using android auto the whole day.