Related
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....
--------
CyanogenMod 12.1 is a free, community built distribution of Android 5.1.x (Lollipop) which greatly extends the capabilities of your phone.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is the support thread for CM12.1 on the AT&T Galaxy S3. All bug reports must be submitted with a log. Feature requests will be ignored, I only work to make the ROM stable on this phone, I do not work on major enhancements to the ROM itself.
Known issues:
Front camera does not work in some apps like Retrica and Instagram.
Install instructions:
1. Install TWRP Recovery for "d2att".
2. Download your correct, updated bootloader/modem. For the US variant you should be on NJ1.. Note that you must do MJB -> NE4 -> NJ1 in order. After MJB you can no longer downgrade your bootloader! Be warned if you are coming from earlier versions. See here and here for the files for the US d2att. I will add links for SGH-i747m if someone sends them to me.
3. Get the nightly build here.
4. Reboot into recovery and install both.
Follow the changelog!
http://www.cmxlog.com/12.1/d2att/
I stole the nice colors above from a post by @InfiniteCaffeine
XDA:DevDB Information
CyanogenMod for d2att, ROM for the AT&T Samsung Galaxy S III
Contributors
Nardholio, invisiblek
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: NJ1 bootloader/modem
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-05-05
Last Updated 2015-05-04
Reserved
Yahoo! First!!
Thanks for this! I hope this fixes the issue I have with Lollipop where when I hit the home button my device goes black except for the status bar!
Thanks!
I installed this and kept having issues with the keyboard not working at all. When I restored via nandroid to my stock setup, nothing worked. It was super whacky. I had to factory reset and restore everything via TiBu. Gonna try a newer nightly and see what happens.
slicetwo said:
I installed this and kept having issues with the keyboard not working at all. When I restored via nandroid to my stock setup, nothing worked. It was super whacky. I had to factory reset and restore everything via TiBu. Gonna try a newer nightly and see what happens.
Click to expand...
Click to collapse
In my side all working good except mobile network the slide all time off..see pic
bluetooth
ok so i dont know if im able to ask this or not but are all the features in this in the unofficial one my amf66
also is bluetooth working
just wondering
thanks
again sorry
So I got it working on my phone, but honestly, I kinda hate Lollipop. I don't like the notifications on my lockscreen instead of at the top in the status bar. I don't like the new animations (I turn all that **** off anyway). I'm not feeling the whole way the sound/alarms/notifications thing is going, either.
Guess I'll downgrade back to my 4.4.2 and be happy with how well things worked on there.
Works great
Installed the 20150504-NIGHTLY last night (dirty flash) and had no issues. No reboots. no signal drop. no camera problems. Thank you!
Hi,
Dirty flashed it over amf66's 4/28 version. It seems very stable, I had one reboot, but I'm sure it was because the phone was overheating (GPS + stuck in traffic + sunroof + warm sunny day).
The only concern I have is regarding bluetooth. It works very well, but the autoconnect fuction does not seem to work. I have to manually connect it (not pair, connect) every time. Once connected, it's smooooth.
This said, I tried to redo de pairing, with multiple devices, screen on / off, cleared "bluetooth sharing" data, etc.
Basically, I have two ways of using it:
Either I keep bluetooth off and turn it on when i'm near a device, it will connect right after turning it on. I can also leave it on and simply select my device when it is in range, and it will connect flawlessly. BUT, if for any reason, the device is turned off, the phone won't reconnect unless I do it manually.
Any thoughts? Anyone else? If i'm the only one with this problem, i'm probably good for a clean flash.
On the 05/05 build I had Dialer force close this morning that required a reboot before it would function again. Haven't gotten it to repeat since the reboot, although it did happen once just now when swiping in Dialer from the lockscreen. Also wanted to note that long press media controls are working again. It's been nonfunctional the past 3 or 4 builds and it's great to have them back!:good:
Aw, yeah. Official thread is a go!
Thanks for maintaining our trusty ol' S3, nardholio. This ROM runs even better than CM11 did on my phone.
I'll throw in a quick bug report, though. In all of these builds (including the unofficial ones) YouTube videos tend to freeze briefly about 8-10 seconds in. This happens with every video when viewed in the YouTube app, regardless of resolution or quality. I haven't noticed it happening with videos using the YouTube API in other apps such as Relay for Reddit.
That's pretty much the only issue I've ever had with these builds. They're pretty fantastic.
Hello guys,
Just a little update regarding the bluetooth issues. I did a clean flash, and it made it somehow better but not perfect. Now, as long as the screen is on or if there is something streaming, everything works well. But, if the phone screen is off, the bluetooth commands stop working (play, next...)...and they work fine if I turn the screen back on. Same goes for the auto connect, it does work when the screen is on, but won't connect if it isn't.
What I think is that the way lollipop acts when the phone is standby simply prevents the bluetooth app from updating it's status or recieving inbound commands. Now, the thing is that it used to work fine in previous builds (amf66 before 4/28 if I remember correctly), and that would mean that some setting was changed, probably in the CM source.
Once again, good job on maintaining our old devices, it really is appreciated.
And..no pressure here, just something I think would be worth looking into.
Dom
Try turning off ambient display for your Bluetooth issues. I'm thinking of permanently disabling it for the S3 anyway as it eats battery.
Nardholio said:
Try turning off ambient display for your Bluetooth issues. I'm thinking of permanently disabling it for the S3 anyway as it eats battery.
Click to expand...
Click to collapse
Tried it this morning, you are on the right track. Once connected, commands now work (phone, play/payse, next etc) even if the screen is off. But, I still have to connect it from the phone, and if the bluetooth device is turned off, it won't reconnect.
Thanks for the support! Are there any other functions that might prevent the phone from scanning for bluetooth devices?
Running the 5/4 nightly. Did the cleanest install possible - formatted through TWRP everthing on the phone, installed the ROM and gApps, then let the play store install all my apps. Everyting is running well for almost 4 hours now. Not a single reboot. Bluetooth has worked for several calls.
Issues I have noticed are -
1. Audio throug the car dock is broken. Once again, as has happened numerous times in the past on Cyanogen, the audio is not being routed through the dock with the phone is docked. I really hope this one gets fixed. Much of my phones use is inthe dock in the car.
2. Although the phone initially bootted with LTE working, it eventiually lost it. As has been noted elsewhere, removing all the other APNs and only leaving the one required for your particular provider fixes this.
3. Was getting pretty bad battery drain about 5-7% per hour at idle. Turned out that fixing the LTE issue as noted in #2 also fixed this issue. Somewhat surprising since the phone is almost always on Wi-Fi anyway. FWIW, I did not have wakelocks from Google Play. Battery concumption over the last hour of idle is only .9% per hour as reported by BBS.
So now, really only issue #1 remains!
jswclw said:
3. Was getting pretty bad battery drain about 5-7% per hour at idle. Turned out that fixing the LTE issue as noted in #2 also fixed this issue. Somewhat surprising since the phone is almost always on Wi-Fi anyway. FWIW, I did not have wakelocks from Google Play. Battery concumption over the last hour of idle is only .9% per hour as reported by BBS.
Click to expand...
Click to collapse
Which BBS version do you have working with android 5.1.1? I've tried a few of the betas with mixed results, but mostly FC's.
jason2678 said:
Which BBS version do you have working with android 5.1.1? I've tried a few of the betas with mixed results, but mostly FC's.
Click to expand...
Click to collapse
I used the latest BBS, 2.1b3 I believe. Also had to flash the helper app, then install BBS again. In the end, it does work.
Is it still recommended that we deny Google Play Services' Wake Up and Keep Awake permissions in Privacy Guard? I had them denied when I was rocking the earlier unofficial builds, but I have had them unblocked as of late. I didn't notice any difference at first, but not Google Play Services is my top battery drainer again.
I notice that I had the contacts repeated. Only one of the contacts had information.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
does it works on the sgh-i747m ?
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!
Just curious to see what people use this tablet for these days. I'm trying to find a good use for mine and am coming to the conclusion that if you want what has features its going to come with issues. But Lineage is quite fast just no features.
Curious on others opinions!
Having installed a12 I was disappointed with its work (compared to stock a6). The rom works fine (except for quick settings, the curtain always lags) until additional programs are installed
Then disappointed in the A12, I decided to switch to the A11, namely the OFFICIAL latest CRDROID. It also started to work worse when a bunch of programs I needed appeared, but not so, it could be in use. However, when I tried to listen to music all night because of him, he was unloading Spotify (he seems to have serious problems with working with RAM. Of course, another reason is 2 GB of RAM)
I also had a strange bug that the tablet completely hung, and after restarting the ROM broke. The blind did not want to open completely, there were problems with the software.
As a result, I returned to a12, put fewer programs, tried to configure the kernel, the system to be more or less comfortable to use it. Of course, this is not the level of a6 or a9, but if you want Something new, cool design, why not.
In my opinion, it is better to use the 9-11 android, as well as install the kernel with overclocking, it is very necessary here.
I'm still new to using this device, so I haven't used much ROM, but it's probably in the future
From here ... > ... The best
No need to look at a high Android!
erdar said:
Having installed a12 I was disappointed with its work (compared to stock a6). The rom works fine (except for quick settings, the curtain always lags) until additional programs are installed
Then disappointed in the A12, I decided to switch to the A11, namely the OFFICIAL latest CRDROID. It also started to work worse when a bunch of programs I needed appeared, but not so, it could be in use. However, when I tried to listen to music all night because of him, he was unloading Spotify (he seems to have serious problems with working with RAM. Of course, another reason is 2 GB of RAM)
I also had a strange bug that the tablet completely hung, and after restarting the ROM broke. The blind did not want to open completely, there were problems with the software.
As a result, I returned to a12, put fewer programs, tried to configure the kernel, the system to be more or less comfortable to use it. Of course, this is not the level of a6 or a9, but if you want Something new, cool design, why not.
In my opinion, it is better to use the 9-11 android, as well as install the kernel with overclocking, it is very necessary here.
I'm still new to using this device, so I haven't used much ROM, but it's probably in the future
Click to expand...
Click to collapse
CrDroid isn't broken but it does have an odd systemUi bug likely to the system partition and other things being so outdated. Whenever restarting the tablet it will continue to respring until it decides to boot the best way to handle this is just to leave it be I've found that more often then not it will eventually start up, other times it refuses to start at all and I will have to reboot again most times I try to refrain from turning it off. Unfortunately this seems like the only way to get good features for this tablet. Wishing someone would take interest like forkLineage or EvoX perhaps
Mr.Conkel said:
"CrDroid isn't broken but it does have an odd systemUi bug ....."
Click to expand...
Click to collapse
I agree, although I prefer pixel experience (and the like).
As for the CRDROID ... My problem was that the curtain does not open, and many programs were not launched, and there was an arrow in the bar, which is displayed only when the navigation bar is two Buttons, and I had gestures enabled) Very strange, actually. It's funny that it all started after the ROM crashed .. I still wanted to try at least lineage 18.1, but after reinstalling a12 I'm too lazy
Running unofficial LineageOS 17.1. I don't really use the tablet or anything really. My touch screen doesn't really work, along with the tilt sensor. It's really slow which is to be expected. I use my Fire 7 since it's faster and less frustrating to use.
I pulled my old nexus out from the cupboard a few weeks ago and was amazed that the battery still had decent life after yrs not being used. I managed to unlock bootloader and install twrp before the micro USB charging port stopped working. I now have DotOS android 9 installed and am using the nexus as my eReader, charging via Qi wireless
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?