Related
Issue: Unable to enable Bluetooth while in Airplane mode.
Reason: I hike and would like to disable all connectivity to save battery while still leaving Bluetooth enabled so I can use my external GPS in the mountains in conjunction with software on my phone. This all works fine however as is. However, I must keep the cell radios on even though I have the "No service" emblem showing and my phone is just burning battery looking for cell signal.
Rom: Calkulin's 3.0 GB rom
I have found several forums dealing with this subject on other phones but not one for the epic 4g touch. Other forums have flashable zips that fix the issue or changing of roms that enable what I am asking.
Since I am on a TW based rom could anyone confirm that one of the other roms actually enable this function? such as CM9 CM10 AOSP AOKP ?
Is it possible that I am worrying about nothing? Will enabling the function I am desiring actually save much battery? I would assume it would, however I am by not means an expert.
Perhaps I should clarify. Could someone on a few of the none TW based roms take the short amount of time needed to turn on Air plane mode and see if you can then turn on bluetooth while air plane mode is left active and post the results. I would prefer not going through the time it would take to flash all these myself only to find out it is just a limitation of this device. thank you.
Hi
I'm new to this rom flashing stuff and I have a question about the pie navigation.
I am using a Spring Samsung Galaxy Note 2 and I have just finished rooting the phone and installed the Whompasaurus ROM onto the phone. As i was fiddling with the Pie navigation and customizing it. I soon realized that when the "Show status info" configuration is on, it freezes my phone for about 10 seconds before going back to normal upon activating the pie feature for too long. It shows me the time and the first set of status, but when it animates to show the second set of status the pie navigation freezes.
I was wondering if anyone else was having this trouble, if so how do you fix it? I love the pie navigation its very easy to use and very reliable at times. I would still like to get the full aspects of the pie navigation. Any help would be great!
If you do have a solution please explain it in a simple manner, like I said before I'm new to these kinds of things >.<.
Timmy.
Hi all,
I was wondering if anyone else was experiencing this, and/or had any solutions - as it's slowly driving me mad.
I do love my M8, but it's getting old and slow running Sense 6/7, and I much prefer the 'pureness' of GPe/CM12.
My phone is SuperCID'd and fully unlocked, and currently flashed the latest RUU for GPe (full firmware) then Candy5 ROM v2.5.5 flashed (based on CM12).
I've tried various Sense firmwares, and other hacked/full GPe firmwares... Bluetooth seems the same on all - works fine on Sense, but not as reliable on non-Sense.
The biggest issue I have is that I have a LG G Watch R and it will disconnect after a few hours, sometimes days, and won't reconnect unless I turn off and on Bluetooth on the phone. Even then it's temporary - I find Wiping Data on com.share.bluetooth makes it stable again for a few more hours/days.
And no, it's not the watch, as if I'm in the car at the same time - that will disconnect and not reconnect either. It's definitely the phone...
Now I generally keep Bluetooth and WiFi on at all times. I only use WiFi at home.
I have noticed it seems to become unreliable if WiFi is on, but hasn't been connected to anything for a while. It's almost like it's "scanning" buffer is full and it's affecting both WiFi and BT (as it's the same chip).
If I keep WiFi off, and only on at Home where it stays connected - my Bluetooth seems really reliable and I don't have an issue.
This isn't a fix, though. As I don't want to have to rely on Llama to switch my WiFi on and off based on my location. Surely a potential battery drain versus just keeping it on at all times.
I've tried a Tasker task to wipe com.share.bluetooth every couple of hours, but it didn't fix it. Would still die beforehand.
I've tried various GPe ROMs, and CM12 ROMs - all as Clean Flashes and not restoring Bluetooth data in Titanium Backup (I only restore user aps + data).
Just wondered if anyone had any ideas!!
Thanks for reading.
I'm having the exact same issue.
Gpe and sense work fine, but cm12,1 just won't stay connected to my car or watch. Very frustrating.
I really want to run cm as my daily driver, but it's totally incapable of keeping Bluetooth up.
Is anyone running cm 12.1 and has working Bluetooth? If so, can you let us know which radio firmware you're using?
I took a stab in the dark and applied firmware 4.16.401.10. So far my watch's connection has been solid. Still haven't tested the car, but will test today. Hopefully it'll be stable - if it is then I'll finally be able to use CM as my daily driver!
Full commute without Bluetooth disconnecting from my car, and I've had a solid connection to my watch for over 24 hrs! WOOOOOOOT!!!!
4.16.401.10 is the trick. Anyone having Bluetooth issues on CM12.1 should go download and apply the firmware. (must be s-off, obvs.)
Firmware is here (courtesy of Mike1986 of ARHD fame)
Ah great news - thanks.
I'll give it a go later!
Should know within 15 mins after if the bug is fixed!
Thanks again.
Update - looks like that's the fix!
Strange it doesn't seem to be mentioned anywhere else but at least it's now here for anyone else.
Thanks for the tip!
Hello people,
I was wondering if there is someone out there daily driving the latest LineageOS build on their OP9Pro, who could tell me if it runs smoothly and whether there are any major bugs or inconveniences. I am thinking about flashing LineageOS on my device, but I am still uncertain if it is worth the hassle, as I rely on the phone working properly and with all/most of the features.
However I wasn't able to find much information about known issues or user reports.
I used to flash CyanogenMod on my own devices when it used to be relevant so I have a little bit of experience regarding flashing.
What I would like to know:
- Hardware working? (5G, Bluetooth, Wifi, NFC, Cameras, fingerprint, alert slider etc)
- Do all apps still work? (Banking, Netflix, GPay etc.)
- Does VoLTE/VoWifi work? (spec. German carrier T-Mobile)
- How is the update process? (OTA via system updater?)
- Major problems or known issues as stated above
I am really unsatisfied with the current state of OxygenOS (stock rom) as there are many bugs that probably won't be fixed, which is why I am looking into custom Roms again.
Also I own the EU version of the phone if relevant.
Thank you for your answers
Hi,
In case you're still wondering:
I just bought a used OnePlus 9 Pro with LIneageOS 19.1 installed.
- All of the hardware works (except I have not tested NFC - I don't use it.)
- I did not install microG or anything to use Goolge apps, I only use apps from F-Droid, so sorry I can't help you there. I don't know if any of your required apps will work.
- Phone calls work on WiFi Calling and the 4G/5G networks on USA T-Mobile service.
- OTA updates work fine.
- The only issue I have is that the Android 12 Desktop Mode doesn't work (the launcher button and two navigation buttons show up on the monitor, but they don't do anything. On my OnePlus 7 Pro with LineageOS 18.1, Android 11 Desktop Mode works pretty well.
Yes, thanks for the reply. I think i will wait for the upcoming Oxygen13, but I don't actually have high hopes for it being good. If I'll be disappointed with the update I'm likely going to flash LineageOS, as I am annoyed by the integration of Oppo's ColorOs into Oxygen, while there are still so many bugs and inconsistent UI.
akaYunus said:
Yes, thanks for the reply. I think i will wait for the upcoming Oxygen13, but I don't actually have high hopes for it being good. If I'll be disappointed with the update I'm likely going to flash LineageOS, as I am annoyed by the integration of Oppo's ColorOs into Oxygen, while there are still so many bugs and inconsistent UI.
Click to expand...
Click to collapse
My pleasure. Good luck!
Daily driving it for several months now and so far so good. The only issue I sometimes have, is that I press the power button and the screen turns black (still giving haptic feedback, but shows nothing on the screen.) I need to force reboot to fix this.
But it performs waaaaaaay better then ColorOS / "Oxygen OS" and read that the beta is again full of bloat.
I did install Gapps with this and works like a charm (thought I've picked Pico)
Hope this will help you with your choice
Dn_nS said:
Daily driving it for several months now and so far so good. The only issue I sometimes have, is that I press the power button and the screen turns black (still giving haptic feedback, but shows nothing on the screen.) I need to force reboot to fix this.
But it performs waaaaaaay better then ColorOS / "Oxygen OS" and read that the beta is again full of bloat.
I did install Gapps with this and works like a charm (thought I've picked Pico)
Hope this will help you with your choice
Click to expand...
Click to collapse
Yes, thank you aswell. I'm certainly going to install Gapps. Can you confirm that NFC/GPay is working? I rely on that as my main payment method.
Dn_nS said:
Daily driving it for several months now and so far so good. The only issue I sometimes have, is that I press the power button and the screen turns black (still giving haptic feedback, but shows nothing on the screen.) I need to force reboot to fix this.
But it performs waaaaaaay better then ColorOS / "Oxygen OS" and read that the beta is again full of bloat.
I did install Gapps with this and works like a charm (thought I've picked Pico)
Hope this will help you with your choice
Click to expand...
Click to collapse
Hmmm, I have never run into that power button issue. That is annoying!
akaYunus said:
Yes, thank you aswell. I'm certainly going to install Gapps. Can you confirm that NFC/GPay is working? I rely on that as my main payment method.
Click to expand...
Click to collapse
Sorry man, don't use Gpay and did not use NFC thus far.
So far, LOS 19.1 has been running like a dream on my 9 Pro. The only complaint I have is that calls using Bluetooth audio have a "stutter" effect, like the sound has little micro-dropouts; it's annoying enough that I try to avoid Bluetooth calls, but not so much that I can't put up with it if I have to. (Bluetooth music isn't affected, it's as smooth as lake ice.) I'm hoping we'll see a fix eventually.
MJPollard said:
So far, LOS 19.1 has been running like a dream on my 9 Pro. The only complaint I have is that calls using Bluetooth audio have a "stutter" effect, like the sound has little micro-dropouts; it's annoying enough that I try to avoid Bluetooth calls, but not so much that I can't put up with it if I have to. (Bluetooth music isn't affected, it's as smooth as lake ice.) I'm hoping we'll see a fix eventually.
Click to expand...
Click to collapse
That's fine as long as it doesn't affect wireless AndroidAuto. If anybody has experience with using it and maybe even with an AAWireless device I'd like to know as well. I have a 1st gen unit I use everyday while driving.
I'm running the version bundled with microg and am quite happy. It's a lot better than the last release of 18.1 that I was on in terms of battery life. I don't game, so I have no idea about it in that regard.
I've been running LOS 19.1 for about two weeks now, but must say I'm not all too happy with it:
- bluetooth calling (using wired android auto) audio quality is very poor, both ways (so for me and the person I'm calling with)
- fingerprint unlock works, but the 'scan area' seems to be more finicky. it often quickly switches to number based unlock. never had that with oos
- the battery life is considerably poorer for me
- the device gets much hotter while charging
- I've once had the top right part of my screen becoming unresponsive. only a reboot fixed that.
GoeniGoeGoe said:
I've been running LOS 19.1 for about two weeks now, but must say I'm not all too happy with it:
- bluetooth calling (using wired android auto) audio quality is very poor, both ways (so for me and the person I'm calling with)
- fingerprint unlock works, but the 'scan area' seems to be more finicky. it often quickly switches to number based unlock. never had that with oos
- the battery life is considerably poorer for me
- the device gets much hotter while charging
- I've once had the top right part of my screen becoming unresponsive. only a reboot fixed that.
Click to expand...
Click to collapse
That's sad to hear but maybe it will be fixed in future updates.
Still might give it a try in the near future. Does the version of the device matter? (EU, US or international)
Gpay works great on lineage
akaYunus said:
Yes, thank you aswell. I'm certainly going to install Gapps. Can you confirm that NFC/GPay is working? I rely on that as my main payment method.
Click to expand...
Click to collapse
Can confirm, though I did install a fork of magisk to get it to work
So, to summarize answers:
- "everything is fine, but I don't use nfc, gapps, banking apps. Bet everything else is fine"
- battery is worse than on Oxygen
- fingerprint sensor works, but it works worse
- "charging works, but, phone is hot. I don't use fast charging and fast wireless charging but yeah charging works, I am able to charge my phone"
- Google Pay works, but actually it does not work, you need "patched Magisk"
Can I ask additional questions?
- can I use all cameras and switch camera during movie recording?
- can I take heic photos?
- can I record 8k movie?
Poco F5
MIUI 14.0.6 TMREUXM
Android Auto 9.4.631624
Car: Škoda Scala
Poco F3 worked flawlessly. F5 fails to connect. Tried different cables.
It correctly detects the phone on the car and prompts me to connect via AA or Mirrorlink.
On the phone, USB connectivity menu appears. I select data transfer / Android Auto.
And then the car tells me it failed.
Is this known? Is is a weird issue with car compatibility?
Any way to make it work by messing with settings?
Seems Android Auto works on EU Rom or other non-official ROMs. Marble doesn't have proper certificate so car's audio component cannot accept pairing and fails to establish a connection in wired mode. It is probably the reason it fails in wireless mode too.
What's "marble"?
Is this a bug that could be fixed by an update or deliberate?
I need to figure out if I should return this phone, as this is serious.
I'm having the same problem.
I am having the same problem. I tried with 3 different cables but the result did not change. I'm thinking of returning it. Incredible problem!!
My car Skoda Scala 2020
I've seen multiple reports associated with android auto,. i have poco f4 gt and getting the same problem right after I upgraded my phone to miui 14 and android 13. they are saying that it's from android 13 version cause all of them getting the issue has Android 13 ,, even in samsung phones and other brands, they are getting the same issue. The only similarity that I noticed is that they all have android 13 on their phone.
I have no experience with the stock rom.
I'm using Xiaomi EU and Android Auto works both wired and wireless mode. Even better than my previous Flip 3
bellissimo.io said:
I have no experience with the stock rom.
I'm using Xiaomi EU and Android Auto works both wired and wireless mode. Even better than my previous Flip 3
Click to expand...
Click to collapse
good to know tho,, so aside from android 13 there might be another factor that affects android auto with most devices.
Got a generic reply from support, so it seems they are not really familiar with this or interested.
Please reinstall the latest update package to eliminate possible errors during installation. Settings - About phone - MIUI LOGO - 3 items - Download last update package.
Next, you can also check the functionality of the device in Safe Mode. To enable Safe Mode, you need to turn off your smartphone first, then press the Power Button and Volume Plus at the same time, once the Recovery Menu appears let go of the buttons. In the recovery menu, please select the Safe Mode option.
All third-party apps are disabled in Safe Mode and will not be displayed. If the device works fine, please reboot to exit Safe Mode and boot the device in "Normal Mode". Please then uninstall the last three apps that were installed and check the functionality again.
If the problem persists, reset the device to factory settings. Please note that before you factory reset the device, please backup your data first, otherwise all your data (pictures, videos, music, apps, etc.) will be lost.
Click to expand...
Click to collapse
I might finally consider custom rom, most likely xiaomi.eu, but I am really hesitant to do this.
There is a lot of uncertainty regarding warranty, and everything working, and conflicting reports about battery life and bugs. Most are seemingly happy, but there are lso reports of it not really working that well.
Or I might return it and wait and see what Nord 3 is priced like.
I know you've said you tried different cables. I was having connectivity issues with Android Auto when my previous phone (Poco F1) had no issues whatsoever.
I've been using an Amazon Basics USB 3.1 cable for a few days now and touch wood, everything is fine. Perhaps the Poco F5 is just very particular about what cables it uses.
Hm..
I suppose it's easier to try with that then to return the phone, though my current cable is 90 degree on one end for practical reasons, and I want a short one.
And some people online are reporting that it works on one car and does not on another, but I don't remember they said it was tested with the same cable.
But I could try. This is like a MUST feature. I would not buy a car without it, let alone a phone.
Though my car is C plug, so I have to try with random cables :/
Android Auto is definitely possible with the proper software. This is definitely a software issue and not a hardware issue. I will revisit this thread once a stable solution (not via custom rom) has been applied. Marble devices (Poco F5/Redmi Note 12 Turbo) should be able to use Android Auto starting from Android 13. Ig we just need to provide some feedback via SocMed so we can be heard.
Same problem with Skoda and Poco f5 pro miui14 latest.
Any known solution to come or throw this phone away ?
You can sell it, don't throw it away.
I might get the Nord 3 if they have an early sale. Though oneplus is allegedly prone to bugs. So I can't be smart about this, just reactionary.
Did you guys try a new cable? I never had problems with my F5 but as I wrote before it happened in the past with another phone and the solution was 1) change the cable 2) unpair the phone/car and pair them again from scratch
It's not the cable. I tried multiple different C-C cables, 2.0 and 3.1. I only have not tried 3.2.
It could be that for some reason it's not standard spec USB, so it does not work with all infotainment systems. There are a few posts about Škoda/VW specifically, but also Honda and some others. My car is USB-C, so maybe for some reason it only works in cars with USB-A?
It could also be MIU14 bug, as there are multiple posts about Xiaomi phones being upgraded to MIUI14 and having these issues, Poco F3 included, and I have that one, works fine with MIUI13. But it's again not all users of the same model, just some.
In my case, it definitely seems to be USB related, because the phone does charge, but keeps dropping connection. When I am charging, it does not. I just remembered I have not yet tried connecting to my laptop and see if it drops connection there, that would be an easy test.
My F3, MIUI13/12, works flawlessly.
I sent my to service, as there was also a post where someone sent a Xiaomi phone to service with the same symptoms and allegedly they fixed it.
It is frustrating to say the least, as it is a crucial functionality for me.
Unfortunately, I don't have any other convenient car I can try it on. Everyone I know has older cars, no AA :/
I mean some do, but nobody where I can try it conveniently.
Now I'm kinda optimistic, becuse the phone also can't be connected to a PC. Nothing happens. nd it also keeps reconnecting.
nd, when I was switching stuff over via cable from my F3, this did not work, so I had to use wireless option.
I say optimistic, because it appears it is clearly an issue with USB, so service might be able to solve it.