Related
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
What is CyanogenMod ? It is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones.
Notes: CyanogenMod's stock kernel forces encryption. If you're unencrypted use a custom kernel to keep it.
Also this thread assumes you have kept up to date bootloader and radio !!!
The latest can be downloaded here Shamu Factory images around 1gb!. But i recommand you to flash through TWRP the Bootloader and Radio from here Radio and Bootloader around 60mb.
Installation is simple
1/Download rom + gapps (C-apps optional)
2/flash through recovery (Twrp or CM recovery)
3/Enjoy!!!
----->CyanogenMod Download<-----
----->Open GApps<-----
last--CM13--nightlylast--CM12.1--nightly
Changelog
CyanogenApps
Twrp
Sources: Kernel & Rom
XDA:DevDB Information
[ROM] CyanogenMod14.1 {Nightlies and Snapshots} & Cm13, ROM for the Nexus 6
Contributors
Dead-neM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Up to date firmware (Fastboot+Radio)
Version Information
Status: Nightly
Current Stable Version: Everymonth
Current Beta Version: Everyday
Created 2016-04-22
Last Updated 2016-11-21
Reserved
Q&A
hum yes post your problem here after some research and you'll be helped
...
Reserved
Do not declare a bug here in the idea that they'll be fixed. Here we discuss, share everything related to our CM N6
so this is where we post from now on?
wmfreak said:
so this is where we post from now on?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using Tapatalk
Yay! Best ROM IMHO.
Can i run this in F2FS partitions Lety me know Thank's in advance!!!
Sent from my shamu using XDA Labs
caballon said:
Can i run this in F2FS partitions Lety me know Thank's in advance!!!
Sent from my shamu using XDA Labs
Click to expand...
Click to collapse
Sure, CM13 has been compatible since at least the beginning of this year
Hi, Thank you all making CM work and supporting this device. I particularly love this phone since this is Motorola (well, sort of) with a AMOLED screen, but more importantly it's the CM's custom features that urged me chose this phone.
I have been using the 160402 nightly with no major problem, only having two live lock screen force closes after reboot. Yesterday I hoped to upgrade to a more recent nightly, but that turned out to fail. I got constant FC's on Phone app, although the LLS ones were gone.
I tried cleaning Phone app's data, disabling xposed, but no help. I don't want to wipe data or otherwise I have to TiBu and then manually set up a ton of things.
The new post OP gives me a hint maybe my radio is too old (MDM9625_104662.22.05.32R) so I'm now trying to flash the latest factory radio and flash the yesterday's nightly again. Also it may be true but not so obvious that my cell signal (Tmobile LTE) gets frequently dropped (no signal/emergency only). I didn't test long before TWRPing back to the old working nightly.
Just want to check out at now if there is any other thing I have missed? Or why am I getting constant Phone app FC?
Edit: I updated the radio to .34R but it didn't help. The Phone app crashes every time I launch it, without giving a report button and it even didn't give me a chance hit the OK button before it disappears. I managed to call somebody with the contacts app and I heard the dialing tone. I was able to hang up the call with the notification action button. Everything looks fine except for the "Dialer" app.
Has the Sprint LTE issue been fixed by CM yet? IIRC the issue is once the Nexus 6 (running CM13 of course) drops down to 3G, it will never go back to LTE.
@cyrildtm
Going to have to bite the bullet and clean flash then.
Lawlrus said:
@cyrildtm
Going to have to bite the bullet and clean flash then.
Click to expand...
Click to collapse
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Snap camera in this version yet?
cyrildtm said:
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Click to expand...
Click to collapse
Yeah, I mean I clean flash everything but I know everyone is different.
That's the nice thing about ROMs though, you don't HAVE to flash every nightly, I know I sure don't lol.
If they push a new commit I like then I update, but if everything is kosher, then the hell with it.
Yeah, is the sprint LTE issue fixed?
Sent from my Nexus 6 using XDA-Developers mobile app
cyrildtm said:
Hi, Thank you all making CM work and supporting this device. I particularly love this phone since this is Motorola (well, sort of) with a AMOLED screen, but more importantly it's the CM's custom features that urged me chose this phone.
I have been using the 160402 nightly with no major problem, only having two live lock screen force closes after reboot. Yesterday I hoped to upgrade to a more recent nightly, but that turned out to fail. I got constant FC's on Phone app, although the LLS ones were gone.
I tried cleaning Phone app's data, disabling xposed, but no help. I don't want to wipe data or otherwise I have to TiBu and then manually set up a ton of things.
The new post OP gives me a hint maybe my radio is too old (MDM9625_104662.22.05.32R) so I'm now trying to flash the latest factory radio and flash the yesterday's nightly again. Also it may be true but not so obvious that my cell signal (Tmobile LTE) gets frequently dropped (no signal/emergency only). I didn't test long before TWRPing back to the old working nightly.
Just want to check out at now if there is any other thing I have missed? Or why am I getting constant Phone app FC?
Edit: I updated the radio to .34R but it didn't help. The Phone app crashes every time I launch it, without giving a report button and it even didn't give me a chance hit the OK button before it disappears. I managed to call somebody with the contacts app and I heard the dialing tone. I was able to hang up the call with the notification action button. Everything looks fine except for the "Dialer" app.
Click to expand...
Click to collapse
Hi I'm not using the stock dialer app but the Google one from playstore and i don't have force close so that's not a radio problem but an app problem. In fact having radio up to date normally improve stability over network cell comprehension etc... That's not a big deal but it is better to have a Marshmallow fastboot + radio on a Cm13 build which is Marshmallow based
Cm13 nightly can be really messed up a day but not an other. i think you just catch the wrong one
cyrildtm said:
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Click to expand...
Click to collapse
Used titanium to restore data of system app have always been buggy for me on every phone tablet that i've possessed. TiBu is usefull for data app
Btw a clean flash doesn't mean to restore data of a previous rom lol
Lawlrus said:
That's the nice thing about ROMs though, you don't HAVE to flash every nightly, I know I sure don't lol.
If they push a new commit I like then I update, but if everything is kosher, then the hell with it.
Click to expand...
Click to collapse
I agree with you. Nightlies sometimes can be awesome but sometimes awful. I went to look at the github page for the dialer app and found they recently put quite a lot of commits so maybe one or two is breaking things but anyways those smart people will figure it out sooner or later. I will just wait and take another free software
I bumped up from a March nightly mainly because of a recent CVE patch (of course that went into the 0401 build mod). Other than that I don't really see any urgent reason for increasing the counters in my daily driver again.
Dead-neM said:
Hi I'm not using the stock dialer app but the Google one from playstore and i don't have force close so that's not a radio problem but an app problem. In fact having radio up to date normally improve stability over network cell comprehension etc... That's not a big deal but it is better to have a Marshmallow fastboot + radio on a Cm13 build which is Marshmallow based
Cm13 nightly can be really messed up a day but not an other. i think you just catch the wrong one
Click to expand...
Click to collapse
I'm now on MOB30D radio (34R shown in settings, didn't copy down the version number shown in bootloader, but it did increase after flashing) and I can always make a phone call even now with an older nightly. so I can confirm the radio is working. I also noticed after flashing and first boot, when CM is about to finish "optimizing apps" the system gets a hot reboot (restart from animation) - oh btw another long-time bug is i never get themed boot animation unless i make a hot reboot (by FCing or any other way). Anyone same here?
From what I can remember the Dialer app has been a failure to me for more than a week. They did make a NPE fix there but seemed no help. Maybe I should install the Google's dialer as you do. I can still remember the AOSP English keyboard endless crash :silly: when I was on CM12.1 with an older device
Dead-neM said:
Used titanium to restore data of system app have always been buggy for me on every phone tablet that i've possessed. TiBu is usefull for data app
Click to expand...
Click to collapse
One of the hard lessons I have learned.
Lawlrus said:
Yeah, I mean I clean flash everything but I know everyone is different.
Click to expand...
Click to collapse
Dead-neM said:
Btw a clean flash doesn't mean to restore data of a previous rom lol
Click to expand...
Click to collapse
Oh lol it never means that! A clean "flash" is no more than 90 seconds to me but a clean "install" means recovering a whole shelf of over a hundred apps from .... the play store .... no the auto re-install only works if i got the same android id
Custom Kernel
I've been using nightlies for quite a while now, since my Nexus One and then my Samsung GS3. I've been reading up on Kernels but there are just so many... and they all say the same thing "Best balance of battery life and performance."
Yes, I could just try all 10 or so out there, but would like to be a little more efficient with my time, so I ask: What do you guys think is a good starting point for trying Kernels? I'm looking for obviously a good balance, but I'm a little more towards the performance side... CM13 has been a little laggy for me, especially with Swapps and rendering backgrounds loaded by chainfire's 500 Firepaper app. And I'll be damned if a colleague's iPhone is faster or more responsive than my Nexus!!!! :laugh:
Franko? ElementalX?
skim7x said:
I've been using nightlies for quite a while now, since my Nexus One and then my Samsung GS3. I've been reading up on Kernels but there are just so many... and they all say the same thing "Best balance of battery life and performance."
Yes, I could just try all 10 or so out there, but would like to be a little more efficient with my time, so I ask: What do you guys think is a good starting point for trying Kernels? I'm looking for obviously a good balance, but I'm a little more towards the performance side... CM13 has been a little laggy for me, especially with Swapps and rendering backgrounds loaded by chainfire's 500 Firepaper app. And I'll be damned if a colleague's iPhone is faster or more responsive than my Nexus!!!! :laugh:
Franko? ElementalX?
Click to expand...
Click to collapse
Try this one https://www.androidfilehost.com/?fid=24499762636000737
This is the latest singularity kernel
Also on post 2 I've post 2 kernel Blackbird and Singularity which in my opinion are the best
I don't like elementalx and Franco but I'm open mind and I'll add link if you find an other good kernel
Does anyone tried any Android Pie Treble GSI roms on our device? is it working fine?
I know our device supports Treble but I didn' t see any successful installation with 9.0 GSI roms, always bootlooping..
phone bootloops so do not try it
TurkO546 said:
phone bootloops so do not try it
Click to expand...
Click to collapse
Can anyone try to help one of the treble devs figure it out why it bootloops on our device? I think phhusson might be willing to help + it seems like the treble roms are built on top of his gsi.
Redcalibur said:
Can anyone try to help one of the treble devs figure it out why it bootloops on our device? I think phhusson might be willing to help + it seems like the treble roms are built on top of his gsi.
Click to expand...
Click to collapse
Do you contacted @phhusson ?
SGH-i200 said:
Do you contacted @phhusson ?
Click to expand...
Click to collapse
I reached out for him in his thread so he should be aware, but I got no answer back probably because I couldn't provide logs of the bootloop (my device isn't unlocked yet). If you got any logs that you could provide him, please do so either in his thread in the treble forums or his github issues page.
https://github.com/phhusson/treble_experimentations/issues
Redcalibur said:
I reached out for him in his thread
Click to expand...
Click to collapse
Can you provide a link to your post, please? In the XDA app I can't see a list of your posts.
SGH-i200 said:
Can you provide a link to your post, please? In the XDA app I can't see a list of your posts.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page63
It isn't anything special really. I just asked him if he might know any reason why it doesn't boot for our devices.
Redcalibur said:
Can anyone try to help one of the treble devs figure it out why it bootloops on our device?
Click to expand...
Click to collapse
Redcalibur said:
https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page63
Click to expand...
Click to collapse
This ROM is very much experimentel, as the many error reports in that thread show. I will try the ROM in a month or so, when it is more stable.
SGH-i200 said:
This ROM is very much experimentel, as the many error reports in that thread show. I will try the ROM in a month or so, when it is more stable.
Click to expand...
Click to collapse
I think nearly every Pie Treble rom is based on this rom, so you got to wait for this one to get updated before the other ones also get updated. Most people are pretty happy with how they perform. We also need to get it to run first before he fixes device specific bugs, so if anyone can get him the logs of the bootloop, please do so.
Pontential solution
This may not matter anymore(given that the last post was from a while ago), but I manged to get the GSI's to boot by flashing magisk right after flashing the image. I found the solution in this thread.
Hopefully this helps anyone who comes upon this thread and needs help getting the GSI's to work.
Generic123. said:
This may not matter anymore(given that the last post was from a while ago), but I manged to get the GSI's to boot by flashing magisk right after flashing the image. I found the solution in this thread.
Hopefully this helps anyone who comes upon this thread and needs help getting the GSI's to work.
Click to expand...
Click to collapse
May I asked which one you tried as I've been reading though them an they all seem to have one bug or another?
lilbrat said:
May I asked which one you tried as I've been reading though them an they all seem to have one bug or another?
Click to expand...
Click to collapse
Sure! I have to mention that I'm not the most tech savvy, so I don't use these ROM's looking for bugs or anything like that, nor do I really read the forums for the GSI's(I just flash and try it out).
I've tried 2 of them: HavocOS and Resurrection Remix(currently using). Both are Pie GSI's. These are my initial impressions.
Both of them seem to work fine to me(calls, videos, data, Bluetooth, audio, etc.), but they do have a few bugs.
HavocOS's brightness slider is screwed up; scrubbing through it will give you random brightness values. All of the brightness values are there; they just seemed to be placed at random along the slider.
Resurrection Remix is 1.5GB, and you will not have enough space to flash any GAPPS(at least for me). To fix this, resize your system partition using TWRP after flashing the GSI and Magisk(go to wipe -> advanced -> select system -> repair or change file system -> click resize once -> flash GAPPS). Other than that and a crappy minimum brightness, I can't find any other significant issues(although I have not used it for very long).
The fingerprint sensor doesn't seem to be always active for both, which bums me out a little.
Other than those things, these GSI's are stable enough(take note that I have been using these GSI's for a short amount of time, so be careful), and the fact that they are Pie means that the camera should work(although the pictures are not too great).
There are most likely bugs that you may notice that I have not; like I said, I don't really look for bugs in these things. Sorry.
Generic123. said:
Sure! I have to mention that I'm not the most tech savvy, so I don't use these ROM's looking for bugs or anything like that, nor do I really read the forums for the GSI's(I just flash and try it out).
I've tried 2 of them: HavocOS and Resurrection Remix(currently using). Both are Pie GSI's. These are my initial impressions.
Both of them seem to work fine to me(calls, videos, data, Bluetooth, audio, etc.), but they do have a few bugs.
HavocOS's brightness slider is screwed up; scrubbing through it will give you random brightness values. All of the brightness values are there; they just seemed to be placed at random along the slider.
Resurrection Remix is 1.5GB, and you will not have enough space to flash any GAPPS(at least for me). To fix this, resize your system partition using TWRP after flashing the GSI and Magisk(go to wipe -> advanced -> select system -> repair or change file system -> click resize once -> flash GAPPS). Other than that and a crappy minimum brightness, I can't find any other significant issues(although I have not used it for very long).
The fingerprint sensor doesn't seem to be always active for both, which bums me out a little.
Other than those things, these GSI's are stable enough(take note that I have been using these GSI's for a short amount of time, so be careful), and the fact that they are Pie means that the camera should work(although the pictures are not too great).
There are most likely bugs that you may notice that I have not; like I said, I don't really look for bugs in these things. Sorry.
Click to expand...
Click to collapse
Did you just put the system image over the stock rom, or flashed the AOSP based roms first then system image?
The stock based setup is more stable while latter I can use gcam… But both are unstable with the network for me, I mean phone and the data connection
Riskypedia said:
Did you just put the system image over the stock rom, or flashed the AOSP based roms first then system image?
The stock based setup is more stable while latter I can use gcam… But both are unstable with the network for me, I mean phone and the data connection
Click to expand...
Click to collapse
You should first flash a stock firmware using newflasher or flashtool, then flash TWRP. Then factory reset or format using TWRP, and flash the GSI(AOSP ROM) and Magisk right after.
Not sure what bootloops you guys talk about, but I tried 2 GSI ROMs on my XZ1 and both worked fine. Tried these:
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
https://forum.xda-developers.com/pr...-device-development/gsi-havocos-v2-0-t3855601
manxp85 said:
Not sure what bootloops you guys talk about, but I tried 2 GSI ROMs on my XZ1 and both worked fine. Tried these:
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
https://forum.xda-developers.com/pr...-device-development/gsi-havocos-v2-0-t3855601
Click to expand...
Click to collapse
Are you still using one? Which one do you prefer? Resurrection Remix seems to do it for me.
Yes, I still use RR. It has some annoying bugs, which were also reported by other users; BT sound only works with headphones and doesn't work with in-car hands-free device, scrollable widgets don't work, battery charging light doesn't work, auto-updater is broken, no adaptive lighting support. I think that's all, so ROM is pretty usable still.
Havoc has a serious bug with brightness (also reported by many users) - sliding brightness slider has 0 effect or works totally randomly, so it's impossible to set desired brightness. Which makes whole ROM unusable.
manxp85 said:
Yes, I still use RR. It has some annoying bugs, which were also reported by other users; BT sound only works with headphones and doesn't work with in-car hands-free device, scrollable widgets don't work, battery charging light doesn't work, auto-updater is broken, no adaptive lighting support. I think that's all, so ROM is pretty usable still.
Havoc has a serious bug with brightness (also reported by many users) - sliding brightness slider has 0 effect or works totally randomly, so it's impossible to set desired brightness. Which makes whole ROM unusable.
Click to expand...
Click to collapse
Thanks for the info! Scrollable widgets seem to work for me(using calendar right now). The battery light does not work, like you mentioned. Auto update is also broken. Can't really test Bluetooth car audio right now. I'm bummed out by the lack of auto brightness.
Do you use this month's build? I have January build, maybe they fixed widgets in February build after many complains...
If you can test and report car's BT later, that would be great... It's the most serious issue for me so far...
manxp85 said:
Do you use this month's build? I have January build, maybe they fixed widgets in February build after many complains...
If you can test and report car's BT later, that would be great... It's the most serious issue for me so far...
Click to expand...
Click to collapse
Yeah, I'm using this month's build. I'll check car Bluetooth later when I get home.
Hi, its October 2019, and I'm still rocking this phone as my daily driver. With Lineage 15.1 installed it feels brand new and snappy, tho occasionally some apps will crash but nothing major.
What I want is a better camera experience and gcam comes up a lot.
After going round and round through threads I landed on this page
https://www.celsoazevedo.com/files/android/google-camera/
But which latest version of gcam works, using both camera modules and night sight?
The best I can come up with is to use version 6.1, but not exactly sure where to start on that.
Appreciate any input.
davestuarts said:
Hi, its October 2019, and I'm still rocking this phone as my daily driver. With Lineage 15.1 installed it feels brand new and snappy, tho occasionally some apps will crash but nothing major.
What I want is a better camera experience and gcam comes up a lot.
After going round and round through threads I landed on this page
https://www.celsoazevedo.com/files/android/google-camera/
But which latest version of gcam works, using both camera modules and night sight?
The best I can come up with is to use version 6.1, but not exactly sure where to start on that.
Appreciate any input.
Click to expand...
Click to collapse
I use this exact version:
NoHex_MGC_6.1.021_MI8_V2a+
You can enable switching cameras in settings. Everything works fine for me.
jc9896 said:
I use this exact version:
NoHex_MGC_6.1.021_MI8_V2a+
You can enable switching cameras in settings. Everything works fine for me.
Click to expand...
Click to collapse
I don't see that one myself in the link. Is NoHex the dev? I though cstark did the LG ones or has that changed now?
jc9896 said:
I use this exact version:
NoHex_MGC_6.1.021_MI8_V2a+
You can enable switching cameras in settings. Everything works fine for me.
Click to expand...
Click to collapse
Awesome, thanks for your input after a trying again a new day I finally figured it out. And installed Arnovas advanced 1.7 with a g5 config file and it works in most ways
ezzony said:
I don't see that one myself in the link. Is NoHex the dev? I though cstark did the LG ones or has that changed now?
Click to expand...
Click to collapse
I downloaded Arnovas oreo version from here under
Google camera 6.1 section. Version : Arnovas advanced 1.7 from here :
https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/
Then opened the configs link and searched for g5 and downloaded the xml file . I installed the apk and installed the g5.Xml as described on the page.
Most things work, except slow motion..it crashes.
If you go to settings, aux camera switch method.
I changed that to long press, so doing so will switch between wide and normal.
Hope this all makes sense.
Side note.. There's so many options in this Gcam version.
ezzony said:
I don't see that one myself in the link. Is NoHex the dev? I though cstark did the LG ones or has that changed now?
Click to expand...
Click to collapse
If I'm not wrong, that apk comes from cstark.
davestuarts said:
Awesome, thanks for your input after a trying again a new day I finally figured it out. And installed Arnovas advanced 1.7 with a g5 config file and it works in most ways
I downloaded Arnovas oreo version from here under
Google camera 6.1 section. Version : Arnovas advanced 1.7 from here :
https://www.celsoazevedo.com/files/android/google-camera/dev-suggested/
Then opened the configs link and searched for g5 and downloaded the xml file . I installed the apk and installed the g5.Xml as described on the page.
Most things work, except slow motion..it crashes.
If you go to settings, aux camera switch method.
I changed that to long press, so doing so will switch between wide and normal.
Hope this all makes sense.
Side note.. There's so many options in this Gcam version.
Click to expand...
Click to collapse
On the version I suggested (not sure if present on Arnova's mod) there is a setting for switching the slow motion FPS which resolves the crashes.
jc9896 said:
On the version I suggested (not sure if present on Arnova's mod) there is a setting for switching the slow motion FPS which resolves the crashes.
Click to expand...
Click to collapse
Oh excellent. Yes, theres the option to change fps 120, which now works. Thx
incidentally arnova's 1.7 was crashing more than I liked, so I tried arnova's 1.6, which seems more stable.
I wonder what the difference is between your suggestion and the MGC_6.1.021_MI8_V2e.apk listed
I don't understand what the Nohex means, unless thats a developer too.
I'm just waiting for Lineage 16 to be more stable and want to try the next gcam versions.
davestuarts said:
Oh excellent. Yes, theres the option to change fps 120, which now works. Thx
incidentally arnova's 1.7 was crashing more than I liked, so I tried arnova's 1.6, which seems more stable.
I wonder what the difference is between your suggestion and the MGC_6.1.021_MI8_V2e.apk listed
I don't understand what the Nohex means, unless thats a developer too.
I'm just waiting for Lineage 16 to be more stable and want to try the next gcam versions.
Click to expand...
Click to collapse
Cstark is the developer of the one I suggested.
NoHex has something to do with the Hexagon DSP hardware components, though I'm not sure what.
jc9896 said:
Cstark is the developer of the one I suggested.
NoHex has something to do with the Hexagon DSP hardware components, though I'm not sure what.
Click to expand...
Click to collapse
Oh OK. Well, the G5 has the hexagon dsp, unless gcam was causing issues with it, hence a nohex version.
Thx for your input again
jc9896 said:
Cstark is the developer of the one I suggested.
NoHex has something to do with the Hexagon DSP hardware components, though I'm not sure what.
Click to expand...
Click to collapse
Wondering if the "best" (most current/feature-rich) suggestion for the LG has changed in the last 6+ months? I've finally gotten my TMO LG G5 H830 flashed with LOS 17.1 and everything (basically) is working as desired with the one notable exception of no GCam port yet.
Would *really* appreciate any feedback on the current best option?
mgreig said:
Wondering if the "best" (most current/feature-rich) suggestion for the LG has changed in the last 6+ months? I've finally gotten my TMO LG G5 H830 flashed with LOS 17.1 and everything (basically) is working as desired with the one notable exception of no GCam port yet.
Would *really* appreciate any feedback on the current best option?
Click to expand...
Click to collapse
Not very sure, my G5 has gotten some rather nasty battery issues so I'm not using it now. You can try some of the Android 10 compatible apks (7.2.x and up) here:
https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2-beta/
Hi,
I tried using the search functionality, but all the threads I've found are either dated or irrelevant.
I'm currently using the PE10+ ROM, but a few bugs got me looking to change.
I'm looking for a stable daily driver, hopefully with gcam incorporated, but I can flash it later.
I do use banking apps like gpay, and don't plan on rooting the device.
I've been thinking about LOS, but let me know what you think, and whether or not it supports banking apps
Kind regards.
you can use miui eu its preety neat and bloat free. Have been using it for more than 18 months feels solid.
csakthikumar said:
you can use miui eu its preety neat and bloat free. Have been using it for more than 18 months feels solid.
Click to expand...
Click to collapse
Thanks for the reply!
I tried MIUI for a while when I just got the device, but it had bugs that really annoyed me:
1. I keep my phone on vibrate during the day, but during the nights i set it to DND on a timer (after so and so hours it comes out of DND). On MIUI, it never came back to vibrate, but rather switched to ringing on a low volume setting.
2. If I listened to FM radio, and got a Whatsapp alert, the FM radio would mute, and never come back. I had to kill the app and open it again.
Guttmann said:
Thanks for the reply!
I tried MIUI for a while when I just got the device, but it had bugs that really annoyed me:
1. I keep my phone on vibrate during the day, but during the nights i set it to DND on a timer (after so and so hours it comes out of DND). On MIUI, it never came back to vibrate, but rather switched to ringing on a low volume setting.
2. If I listened to FM radio, and got a Whatsapp alert, the FM radio would mute, and never come back. I had to kill the app and open it again.
Click to expand...
Click to collapse
FM I haven't used in years so I cannot comment on that. I am using MIUI 12 eu rom. I don't face the vibrate issue you are facing. Night mode works flawlessly for me.
You can try Havoc & Evolution X. Both of them support banking apps without root.
You can use Pixel Experience for banking accounts, but I think you'll still have to use magisk hide thus be rooted. Best option is to relock bootloader after installing the stock rom and stock recovery.
Try Oxygen OS it's really good in battery backup and touch response and sound with mono audio , with gcam( have to flash though but working good ) , ambient display with pulse notification and video enhancing alll are good man it's worth a try !
Banking apps supprts in some versions and in some don't ! In my rom g pay and p pe half working , can open check balance and receive but can't able to send so I'm using paytm bank and it's working flawless .
If other than Oxygen os i suggest to go for evolution and PE with 10+ version .. it's awesome and can be your regular driver . Hope you likes one of them . Have a good poco exp
Hi folks!
I have an issue with my Samsung S9+(G965F) display:
After locking the screen and reopening it, my display turns into a blurred, whiter color everywhere, menu, settings, no matter what I check.
These issues came for the first time after the Android 10 update from April 2020, now I got the latest update on the 30th of October 2020 which didn't fix this issue!
My software version is G965FXXUCFTJ2/G965FOXMCFTJ2/G965FXXUCFTJ1
Security patch level: October 1, 2020
One UI version is 2.5
Android 10.
After hours of Youtube, forums and other sources I got a temporary solution for this:
If the Always On Display is set to Show always, then after reopening the phone has its original color like it should be...weird! If I tap the screen after locking it then the AOD appears as well and the colors are fine.
The problem with this solution is that if I lock the screen and want to reopen it quickly in 1-2 seconds (before the AOD comes up on my screen) then the display color is once again blurred, whiter.
The problem appears only if the AOD is off or appears too late on the lock screen.
I have tried also many solutios but until now this is the best that I found.
Other tried solutions:
Google Play Books app, blue light off doesn't work!
Samsung factory Blue Light filter settings doesn't work!
Display settings don't fix this issue!
No other themes are installed, only the Samsung stock, blue theme is installed on my phone!
After I installed Nova Launcher I tried to find the Night Light app in it , but I couldn't.
Maybe in the old Nova launcher version there was one but now there is not.
Wipe cache partition delete, doesn't work!
Reset and Factory Reset doesn't work!
Check the attached screenshoots which were taken with an S8 because my S9+ takes just blurred, whiter screenshoots, strange!
First and third photo are after AOD appears on the lock screen, 2nd and 4th are without AOD on the screen lock, blurred and whiter!
Any other ideas maybe?
Thank you in advance for your replies (hopefully I will get some) and sorry for my poor english
Love , peace & understanding!
Best wishes: adrianonimus
Find app called "OLED Saver" and install it. It's available on google play store.
App will control your phone light but before you start using it turn on your screen light to maximum then adjust from app to what ever level you want. I had similar problem and this worked for me, using it for more then 2 weeks, not happened even once after.
ivica122 said:
Find app called "OLED Saver" and install it. It's available on google play store.
App will control your phone light but before you start using it turn on your screen light to maximum then adjust from app to what ever level you want. I had similar problem and this worked for me, using it for more then 2 weeks, not happened even once after.
Click to expand...
Click to collapse
Hi ivica122!
Thank you for your reply, I tried this app also, not so bad, wonder if the factory brightness has to be set always at max, how will this influence my battery....any observations about that?
In fact my problem will be if I want to sell this mobile to someone and have to say something about this whiter screen...
I was waiting for the latest software update with big hope that this bug will be fixed, but unfortunately they didn't....
At least with this app I can turn off the AOD
But anyway, this is a solution, but still waiting for a software fix or whatever...
Thank you for your answer, have a nice day.
Yes, it will be a problem if you want to sell it, i also hope some update will fix this but starting to doubt.
About battery life - with oled saver you can lower down phone brightness as much as you want, you can even use auto brightness from oled saver, it will keep your screen problem free and battery will be used like you lower down brightness from your phone. I didn't notice any difference. Look at the app like override of phone brightness functionality.
You know what, maybe you can try downgrading it to the latest android 9? If that fix a problem you can sell it like that, because when i was reading about this all people that has a problem said that problem started after upgrading to android 10.
ivica122 said:
Yes, it will be a problem if you want to sell it, i also hope some update will fix this but starting to doubt.
About battery life - with oled saver you can lower down phone brightness as much as you want, you can even use auto brightness from oled saver, it will keep your screen problem free and battery will be used like you lower down brightness from your phone. I didn't notice any difference. Look at the app like override of phone brightness functionality.
You know what, maybe you can try downgrading it to the latest android 9? If that fix a problem you can sell it like that, because when i was reading about this all people that has a problem said that problem started after upgrading to android 10.
Click to expand...
Click to collapse
I cannot downgrade my phone as is not rooted, so this option is not my solution...
I will use this app and wait for the next update, who knows
But anyway, thank you for your alternative.
Hy guys! I have your problem after last update my s9+ begin to have green screen. Anyone try to downgrade at android 9 ?
aranbonjo said:
Hey! I have your problem after last update my s9 + starts to green screen. Anyone trying to downgrade Android 9?
Click to expand...
Click to collapse
nic nie dało wrócenie do androida 9 i androida 8 to samo dalej jest
Translation: Going back to android 9 and android 8 did not work, the same goes on
Hi! Just want to inform you guys that even with the latest minor updates from the last 3 months I still have this problem, I'm now on the latest version: G965FXXSEFUA1
Android 10
One UI 2.5
Security patch: 2021.February 01.
So no fixes here at all.
As I said before, my phone display colour is clear only if I open the phone with the AOD always on, so that I can see it.
If I will open my display before I see the AOD, (1-2 second) the colours are blurred, whiter, so no change here at all.
If I don't use at all the AOD then the display is always whiter, blurred!
My phone is not rooted, I don't want to root, and the OLED Saver app is only a kind of solution...of course the display is better with this app, but if I will sell my phone I will have to say something about this issue, so I'm afraid I will not get a good price....
I want to change my phone and I want to believe that this issue is not a common problem on other Samsung phones, even if I read about this problem affects Note 9and 10 also...
So, help me GOD!
I'm not in to this anymore but have you tried to find the way to downgrade it to android 9? Here on xda? I will try to find.
ivica122 said:
I'm not in to this anymore but have you tried to find the way to downgrade it to android 9? Here on xda? I will try to find.
Click to expand...
Click to collapse
I really don't want to root my phone, but anyway. thank you.
I will try to make once again a factory reset, but I have so much things which I have to reset and reload etc.
Anyway, I will update this thread after, hopefully it will fix this.
BTW, I want to change or to buy a new Samsung S20 FE or Samsung S10+, which is better? I guess the S20 FE model worth better...
Don't know which is better but root is not required for downgrade, if this tutorial is true. I am downloading last android 9 update from samfrew.com and will give it a try:
How To Flash Stock Firmware on Samsung Phone Using Odin
Now you can install stock firmware right from your home without leaving your phone at service center. Yes! In this guide, we will guide you on how to in
www.getdroidtips.com
ivica122 said:
Don't know which is better but root is not required for downgrade, if this tutorial is true. I am downloading last android 9 update from samfrew.com and will give it a try:
How To Flash Stock Firmware on Samsung Phone Using Odin
Now you can install stock firmware right from your home without leaving your phone at service center. Yes! In this guide, we will guide you on how to in
www.getdroidtips.com
Click to expand...
Click to collapse
OK, but for me is not so easy this, I use my home also for work and if I do this with Odin the security changes will stop for my enterprise stuff....so only the factory reset is my solution, anyway let me know about, thank you.
Factory reset will not delete that? I'm not so sure I think it will delete all installed software and remove all logs and cookies and stuff like that, but good luck, i'll downgrade mine as soon as i have time and will write here if the problem is solved.
ivica122 said:
Factory reset will not delete that? I'm not so sure I think it will delete all installed software and remove all logs and cookies and stuff like that, but good luck, i'll downgrade mine as soon as i have time and will write here if the problem is solved.
Click to expand...
Click to collapse
Tomorrow I will make a factory reset, I will tell you what's up after, waiting for your downgrade result, thank you.
Btw, if your downgrade is successful you will upgrade also to the latest Android 10? Or you will stay on the 9?
I already did factory reset to my phone a couple of times and that didn't help, because the problem is in firmware and some people noticed that problem started with ui 2.0, which is part of android 10, so i will not upgrade again to android 10, i will stay on 9, i don't care about android 10, i really don't see much difference, i only want camera firmware upgraded and that happened with latest android 9 for this phone (night mode, for example), that's all i need so i will be very happy if 9 is working like i remember it, with no screen problems at all.
I don't know why i find this now and not earlier but it seems that samsung phones can't be downgraded, at least not from android 10 to 9. I bet people who new this are now laughing instead of telling us that it's impossible but i just tried and failed, you can't downgrade from newer binary to older. So oled saver app will have to be enough.
This is very disappointing from samsung, first they update my phone with faulty firmware and then don't allow me to go back to older one that was good.
ivica122 said:
I don't know why i find this now and not earlier but it seems that samsung phones can't be downgraded, at least not from android 10 to 9. I bet people who new this are now laughing instead of telling us that it's impossible but i just tried and failed, you can't downgrade from newer binary to older. So oled saver app will have to be enough.
This is very disappointing from samsung, first they update my phone with faulty firmware and then don't allow me to go back to older one that was good.
Click to expand...
Click to collapse
Yes, I guess is only possible if you root your phone before the downgrade, I saw here something about, but I will not try with my phone as I'm not interested, I just wanted to know if somebody else has this problem and maybe there is a fix for it, unfortunately it looks only this OLED Saver app is an option.
Same problem. Been using oled saver for a while now. Works, but I'd rather a cure than a band-aid
ddjr said:
Same problem. Been using oled saver for a while now. Works, but I'd rather a cure than a band-aid
Click to expand...
Click to collapse
So one more of us Did you noticed when this problem started? With android 10 or earlier?
I honestly think mine started after I dropped the phone. I could be wrong.
Here what i found