Hey guys,
I used only stock based ROMs for a long time and did not follow the forums very closely so I was wondering if you could help me shine light into the ROM jungle.
What are the top 3 most used lollipop ROMs atm? You can also add your experiences with the ones you used if you like.
Also it would be awesomus maximus if you could give your assessment if the ROM is stable + battery efficient, because that is what I am mainly looking for (+ I guess I am not the only one)
Thanks fellow ROM-junkies!
You ca try next ROMS:
I tried Ressurection Remix & Team UB. Both of them are very stable & looks good:ะพ
my device is t0lte
i tried
nameless -- not sure if they still support N7105 after 4 march
xposed can not run on this rom
Team UB -- 0325 build
low volume in calls
data connection issues
sensor problem --
when the phone's ringing to get the screen turned on, the screen was turned off as soon as i grabbed the phone.
Thus i had to manually turn the screen back on to answer the phone whenever i got a phone call.
Sometimes after the contact being imported from storage, the whole contact list would disappear altogether
On this rom are lots of settings for users to tweak and play with
cm12 nightly -- builds after 12 march
data connection issues
GPS issues
low volume in calls
wilson3q's cm12 unofficial builds --
overall, it's a nice rom. smooth and good performance.
it aint got the problems stated above.....
but i have been suffering serious graphic glitches while browsing the internet and this happened to whatever browsers i was using.
other users dont seem to have such trouble tho....
--------
Hello,
I used nexus 4 for a long time. I used custom rom with Android 7 and it was nice. Time for a change came, and I picked up MI6, It's nice, but it gives me some issues... Did you experience any of these ?
I am running 64gb version with MIUI 9 Global.
1. I didn't see vanilla android 8 roms for this device here on xda ?
2. My google assistant doesn't respond to most of my queries in voice. While on nexus4, when I asked about weather, GA responded in voice. On MI6, GA only displays me the weather without voice feedback. The same situation transpires with other commands - e.g. how does my commute to home look like. Nexus4 would just tell me about the traffic, here only map is displayed. Not all voice is not workingn however, when I ask MI6 GA to say my name, she will respond in voice no problem. Did you experience any of this ?
3. Since I seem to be unable to find vanilla rom, I wanted to install google now launcher, phone, messages so that I can use these apps instead of the Xiaomi's. While Now Launcher, and Messages installed properly and work fine, the phone app from google says it's not compatible with my device...
4. This feels like a quality phone, but my volume rocker is loose, and when you shake the phone (delicately) you can hear it banging around - does your device have the same ? It feels like I should return the phone as broken.
Hopefully this will not get removed Cheers!
Hi, welcome to the mi 6 community
1, yes there are android O roms, we got los15 and aicp13 both are 8.0
2, dont use google assistant, so i dont know anything about that.
3, you can try install these apk's from apk mirror
4, i have my phone in a case since this is a really slippery phone
cheers m8
my mi 6 volume rocker is shaky as well, so it might be xiaomi's problem
I cannot confirm any quality problems. My Mi 6 doesnt have any loose buttons.
the sound might not be coming from volume rocker.. It must be the camera because of the ois....
Volume rocker I just checked on my phone and its lose. I am new to Xiaomi is well.
Volume button has more 'play' in the normal 6 than on the ceramic versions.
It's not broken just loose. A little too loose if you ask me but it's a common thing it seems.
Hi every one... I'm writing this post due to a problem I'm facing on ALL Oreo ROMs:
I always configure WhatsApp notifications in one specific way (not pup on screen, no sound and not vibration)... In order for me to have that configuration working, I have to do what you see in the picture (establish "make sound" in importance and select "none" as ringtone; so that it doesn't show pup on and doesn't sound). This is totally ok at the moment of establishing it, it does work.. BUT, after certain amount of time (which I haven't counted) the configuration I had done goes away and it returns to the default configuration (which is make sound and show pup on). This is having me hitting the roof and I would like to find a solution.
Any help will be appreciated... Thanks in advance!
Note: that happens on ALL Oreo ROMs (no exceptions, at least for me)
Not for aosip 8.1 whatsapp notification working well
i have same problem too, position in AEX 5.2 + latest ARBeast kernel + magisk root
I took delivery of a Tesla Model 3 on March 30 of this year. At the time, it was running Tesla's software 2019.5.15, but within a day it had upgraded to 2019.8.4, then 2019.8.5, then 2019.12.1 a couple of days ago, and finally to 2019.12.1.1 today. Through all of this, I've had no problems with Bluetooth connections to my OnePlus 5t phone for media streaming; however, I have had problems with placing and receiving phone calls, and the problem has gotten worse with Tesla's 2019.12.1 or 2019.12.1.1 (I'm not sure which).
I never tried making phone calls in the day or so I had Tesla's 2019.5.15, but I did with 2019.8.x, with about a 50% success rate. Sometimes it would work fine, but other times I'd get very stuttery sound, as if the connection was cutting in and out about ten times per second. Initially, I was running LineageOS 15.1; however, in part because I hoped to resolve this problem, I updated my phone to LineageOS 16 about two weeks ago. That update did not fix the problem, unfortunately, but it also did not make it any worse.
Since my car has updated to 2019.12.1 or 2019.12.1.1, though, the problem has gotten worse: Now, when I try to place a call, at best I'll hear a brief click, short series of clicks, or beep, and then I get silence. When receiving a call, the phone rings, I hear a ring tone over the Tesla's audio system, and the Tesla's screen shows an incoming call. I can answer the call via the Tesla's screen, but again, I get no audio. Worse than all of this, sometimes, on both incoming and outgoing calls, the Tesla's screen has gone completely blank a few times. This isn't guaranteed to happen, but it's happened at least four times to me today as I've been testing things.
Some of what I've tried, with no success:
Adjusting volume settings on both the car and the phone
De-pairing the phone and the car, rebooting both, and then re-pairing them
Updating the phone to the very latest LineageOS build (lineage-16.0-20190428-nightly-dumpling-signed.zip)
Using "developer mode" Android options to adjust every Bluetooth option I could find (AVRCP version, audio codec, audio sample rate, bits per sample, channel mode [stereo vs. mono], LDAC codec)
Testing with both incoming and outgoing calls
This same phone works fine with a Bluetooth headset. On my previous car (a 2017 Chevy Volt), I had few problems, although on about 5% of the calls, I did experience the stuttering audio problem that kicked up to 50% frequency with the Tesla before it stopped working altogether.
I've gone to Tesla's Web site and used their "contact us" link to file a bug report (although there was no "bug report" option, so it may not get routed correctly).
Does anybody here have any other ideas of what I could do, short of replacing my phone or installing another Android version? (I'm really trying to avoid the pain of setting everything up again!)
srs5694 said:
I took delivery of a Tesla Model 3 on March 30 of this year. At the time, it was running Tesla's software 2019.5.15, but within a day it had upgraded to 2019.8.4, then 2019.8.5, then 2019.12.1 a couple of days ago, and finally to 2019.12.1.1 today. Through all of this, I've had no problems with Bluetooth connections to my OnePlus 5t phone for media streaming; however, I have had problems with placing and receiving phone calls, and the problem has gotten worse with Tesla's 2019.12.1 or 2019.12.1.1 (I'm not sure which).
I never tried making phone calls in the day or so I had Tesla's 2019.5.15, but I did with 2019.8.x, with about a 50% success rate. Sometimes it would work fine, but other times I'd get very stuttery sound, as if the connection was cutting in and out about ten times per second. Initially, I was running LineageOS 15.1; however, in part because I hoped to resolve this problem, I updated my phone to LineageOS 16 about two weeks ago. That update did not fix the problem, unfortunately, but it also did not make it any worse.
Since my car has updated to 2019.12.1 or 2019.12.1.1, though, the problem has gotten worse: Now, when I try to place a call, at best I'll hear a brief click, short series of clicks, or beep, and then I get silence. When receiving a call, the phone rings, I hear a ring tone over the Tesla's audio system, and the Tesla's screen shows an incoming call. I can answer the call via the Tesla's screen, but again, I get no audio. Worse than all of this, sometimes, on both incoming and outgoing calls, the Tesla's screen has gone completely blank a few times. This isn't guaranteed to happen, but it's happened at least four times to me today as I've been testing things.
Some of what I've tried, with no success:
Adjusting volume settings on both the car and the phone
De-pairing the phone and the car, rebooting both, and then re-pairing them
Updating the phone to the very latest LineageOS build (lineage-16.0-20190428-nightly-dumpling-signed.zip)
Using "developer mode" Android options to adjust every Bluetooth option I could find (AVRCP version, audio codec, audio sample rate, bits per sample, channel mode [stereo vs. mono], LDAC codec)
Testing with both incoming and outgoing calls
This same phone works fine with a Bluetooth headset. On my previous car (a 2017 Chevy Volt), I had few problems, although on about 5% of the calls, I did experience the stuttering audio problem that kicked up to 50% frequency with the Tesla before it stopped working altogether.
I've gone to Tesla's Web site and used their "contact us" link to file a bug report (although there was no "bug report" option, so it may not get routed correctly).
Does anybody here have any other ideas of what I could do, short of replacing my phone or installing another Android version? (I'm really trying to avoid the pain of setting everything up again!)
Click to expand...
Click to collapse
Hello again from TMF (turok3000) . Can confirm I see exactly the same as you (lineage 16.0 + tesla 2019.12.1.1).
I would say you're best off posting here: https://forum.xda-developers.com/oneplus-5t/development/rom-lineageos-16-0-pie-oneplus-5t-t3843026
Do you happen to have tried with latest stock oxygenos ? I'm guessing not since you mention not wanting setup hassle (I'm in a similar situation).
Thanks for the suggestion of posting in another thread. I've done so, with a few updates.
I did back up the phone and tried installing stock OxygenOS as a test; however, the installation went badly -- it hung with a spinning logo on first boot. Thus, I restored my (mostly) working configuration. I may give it another try later, but there's only so much time I can invest in this sort of thing each day.
Any luck with this? I also have a Tesla Model 3 and the same exact problem as you. I'm using crDroid but it is largely based on LineageOS.
Maybe there is something I can try? I messed with all the dev options for bluetooth.
I've worked around it by re-installing OnePlus's OxygenOS. I'd prefer LineageOS or something else more open, but for the moment, switching to OxygenOS seems like the only solution. A caveat: I haven't tried any recent build (from the last month or so). It's conceivable it's been fixed and I just don't know it yet. Also, some others, using OnePlus phones other than the 5t (IIRC, the OnePlus 6 and/or 3) report that reverting to OxygenOS does not help them. If you've got a 5t, though, reverting to OxygenOS, although a nuisance, may be worth trying. There's a thread tracking the problem on a Tesla forum here:
https://teslamotorsclub.com/tmc/threads/bluetooth-problems-on-phone-calls-only.150774/
The problem is common on LineageOS for multiple phones, but it also occurs on some other phones, even including some iPhones. At least one unofficial LineageOS build is not affected; but that build may have been tweaked or rely on proprietary drivers. Overall, then, it looks like more of a Tesla problem than a phone problem, but it's hard to be sure without digging into the code and running diagnostics that I'm not competent to do.
srs5694 said:
I've worked around it by re-installing OnePlus's OxygenOS. I'd prefer LineageOS or something else more open, but for the moment, switching to OxygenOS seems like the only solution. A caveat: I haven't tried any recent build (from the last month or so). It's conceivable it's been fixed and I just don't know it yet. Also, some others, using OnePlus phones other than the 5t (IIRC, the OnePlus 6 and/or 3) report that reverting to OxygenOS does not help them. If you've got a 5t, though, reverting to OxygenOS, although a nuisance, may be worth trying. There's a thread tracking the problem on a Tesla forum here:
https://teslamotorsclub.com/tmc/threads/bluetooth-problems-on-phone-calls-only.150774/
The problem is common on LineageOS for multiple phones, but it also occurs on some other phones, even including some iPhones. At least one unofficial LineageOS build is not affected; but that build may have been tweaked or rely on proprietary drivers. Overall, then, it looks like more of a Tesla problem than a phone problem, but it's hard to be sure without digging into the code and running diagnostics that I'm not competent to do.
Click to expand...
Click to collapse
Ah well thanks for getting back. That is disheartening, as I had been using OOS since I got the phone on release day & finally thought I should try something different. It sounds like I'm gonna have to go through all the efforts to revert back to OOS.
For reference, it did not work for me using crDroid builds from 6/23/19 and 6/30/19.
I'll use Tesla's feedback system to put my "vote" in towards fixing these bluetooth issues.
My Model 3 received an update yesterday to 2019.24.4 and the Bluetooth calling works! Just thought you should know. I'll cross post on TMC.
It was working just fine. I was listening to YouTube while I was doing other things over a Bluetooth device. Stopped YouTube, put it in my pocket, and ate dinner. Went to walk my dog, and it wouldn't play any audio. When I went to call someone to check, I only had "Speaker" as an option along with Bluetooth. I tried my Bluetooth stack by toggling it off, and rebooting the device. When stock Android 11 came up, got at System UI error after unlock. Hoped it was a glitch and turned on Bluetooth, it reconnected, but no audio, and mic doesn't pick up volume. Turned it off, did a reboot and had the headphones turned off also. got the System UI error and it doesn't show any option for audio on call for anything but Speaker. Thought crap, did a Factory format, same. Reinstalled via ADB the same version, same issue and still had the System UI crash on unlock.
Did a wipe back down to 8.0, and I didn't verify the phone worked first, but no system UI crash. Installed 10.0, and no crash on System UI, but only had speaker. Updated to latest 11.0 with the updates, and it got the System UI errors each time. I'm rolling back to 8.0 right now to verify, but I am flummoxed. Everything else works, but I have no phone option and get system UI Crashes. When I call, it vibrates, but no audio when I pickup or when I speak into the mic (used a land line to verify). Since it is Out of Support I had been considering getting a new phone, but this was still viable until today (wish Google had released a 5XL). I'm going to go back to 8.0 and test, also going to test a ROM (not sure what would be recommended, been happy with vanilla for a while, but loved Paranoid Android way back in the day on my Samsung stupid long named Nexus powered by Sprint).
But in the event that 8.0 does work, does anyone have any ideas on how to get audio to work again on a more modern android?
Sorry for the ramble, but I'm seriously confused, and it is late.
An issue like yours, that suddenly appears and persists regardless of the version of Android installed is not a good sign. In general, if it were a firmware issue you were having it should disappear upon a clean install of Android. Thus, assuming Android 8.0 doesn't work, and I don't think it will, the only answer left from my perspective is a hardware problem.
As for wishing there was a Pixel 5 XL, the 4a with 5G would fill the bill. Its screen is larger, albeit only 60Hz, and in day-to-day use it's going to sound better than the Pixel 5. The 5 taking a page from the Sharp Aquos and vibrating the entire screen to produce sound isn't something you see every day, and there's a good reason for that.