'Mute phone alerts & calls' not working on Marshmallow - Wear OS Q&A, Help & Troubleshooting

I have an LG G watch connected to my Galaxy S5 running CM13.
Even though I have 'Mute phone alerts & calls' turned on in AW, the phone still rings.
This worked properly on CM12.1 and still works if I restore my last twrp backup of CM12.1.
Not sure where to post this because I don't know if it is a problem with Android Wear, Marshmallow, or Cyanogenmod.
I see lots of people posting this problem for lollipop but it appears to have gotten fixed. Now it's back. At least for me.
Anyone else having this problem or is it just me?

Can confirm that I have the same issue since March update. I am running pure nexus April build with April security update and I still face the issue. Seem like a prevelant issue as far as I can read. I really hope google fixes it

SpidySun said:
Can confirm that I have the same issue since March update. I am running pure nexus April build with April security update and I still face the issue. Seem like a prevelant issue as far as I can read. I really hope google fixes it
Click to expand...
Click to collapse
Are you saying you had a version of Marshmallow (CM13) that DID work? If so, what was the last working version?
Thanks

I use Pure nexus rom which is CM based. The Feb build worked like charm and that was marshmallow

SpidySun said:
I use Pure nexus rom which is CM based. The Feb build worked like charm and that was marshmallow
Click to expand...
Click to collapse
I intend to track down the version that broke it so maybe I can spot the actual change and try building with out that change. Could you tell me the last version of CM13 that worked and the first version that didn't? I was a bit late to the CM13 party and the first version I tried was well into March.

Feb update worked
anything after fed doesnt work (atleast in PN rom)

SpidySun said:
Feb update worked
anything after fed doesnt work (atleast in PN rom)
Click to expand...
Click to collapse
Do you have a date for the Feb update that worked? I tried a 3/1 nightly and it doesn't work.

U can check the PN thread for a date

Related

[Q] Problem with updating since 4.4.4-2015-02-18 on S4

Hey guys,
I use version 4.4.4-2015-02-18-jflte-NIGHTLY on my S4. Till this version updating works fine but now no updates are shown at the integrated updater. When I try to update by downloading the rom manually and flashing it with TWRP (2.8.4.0), I loose my IMEI and Baseband and have no connection to mobile network anymore. Restoring the backup let me use my phone again but updating my phone doesn't work.
I searched on the internet and found, it may be a problem with the modem and installing the modem after updating would fix it, but this solution didn't work for me.
Is there anyone with an idea what I can try?
Thank you!
The same problem
Hi,
I'm with the same problem that fukuk: I haven't had connection since February updates
I hope you can help us! Thank you very much for all your work
Since I don't believe @jakew02 no longer has his jflte, we probably should have killed nightlies for this device ages ago.
It's not going to get fixed unless someone who actually owns the device troubleshoots it. There's nothing in the commit history for anything on the 4.4 branch that would explain breakage on February 18 - everyone was working on Lollipop by then.
Entropy512 said:
Since I don't believe @jakew02 no longer has his jflte, we probably should have killed nightlies for this device ages ago.
It's not going to get fixed unless someone who actually owns the device troubleshoots it. There's nothing in the commit history for anything on the 4.4 branch that would explain breakage on February 18 - everyone was working on Lollipop by then.
Click to expand...
Click to collapse
I still have it, it's just been collecting a fine layer of dust for the past few months, I've been overwhelmed with classes (starting to get into doing clinical psych work and writing papers every single week) and a new job..
I do have the android-5.0 branch booting on it right now, I just have to work out some bugs before I push anything to gerrit
jakew02 said:
I still have it, it's just been collecting a fine layer of dust for the past few months, I've been overwhelmed with classes (starting to get into doing clinical psych work and writing papers every single week) and a new job..
I do have the android-5.0 branch booting on it right now, I just have to work out some bugs before I push anything to gerrit
Click to expand...
Click to collapse
No problem. Can you reproduce this issue that supposedly started on Feb 18? I've been seeing various people complaining about it but can't figure out what might have caused it - since no one merged anything to the 4.4 branches around then...
Entropy512 said:
No problem. Can you reproduce this issue that supposedly started on Feb 18? I've been seeing various people complaining about it but can't figure out what might have caused it - since no one merged anything to the 4.4 branches around then...
Click to expand...
Click to collapse
Same here I have this issue..
Still we wait for fix or explain how to fix it.
System and radio logcats from both a working and broken build would be useful, along with a dmesg
Also which exact jflte variant you have WHEN you post the logs.
The problem is, if you look through Gerrit's merge history, nothing was merged between February 13 and February 27.
The only thing that might have caused radio issues is https://gerrit.omnirom.org/#/c/11694/ - but that would've broken things on the February 14 build, and all builds from the 14th onward would be broken - but builds from the 14th to 18th are apparently OK?
Guys, is there any way to download the offical jflte 18-2-2015 version?
your help is much appreciated.
alfayez0z said:
Guys, is there any way to download the offical jflte 18-2-2015 version?
your help is much appreciated.
Click to expand...
Click to collapse
I just flashed the 2015-04-16 build and indeed the ril is broken.
I flashed my android-5.1 build from about an hour ago and rather than having the "no service" icon (outline of signal bars), it just says "No SIM", so I'm pretty sure RIL is working in this android-5.1 build. I just don't have Sprint service (but a Sprint variant, since it was the cheapest on Swappa when I bought this replacement last year) to actually test the calling, BUT a guy at work has Sprint so I can probably bug him this weekend for his SIM card, unless I can get a Sprint tester here?
jakew02 said:
I just flashed the 2015-04-16 build and indeed the ril is broken.
I flashed my android-5.1 build from about an hour ago and rather than having the "no service" icon (outline of signal bars), it just says "No SIM", so I'm pretty sure RIL is working in this android-5.1 build. I just don't have Sprint service (but a Sprint variant, since it was the cheapest on Swappa when I bought this replacement last year) to actually test the calling, BUT a guy at work has Sprint so I can probably bug him this weekend for his SIM card, unless I can get a Sprint tester here?
Click to expand...
Click to collapse
I have the GT-I9505 jfltexx, i will be glad to help if i can. I'm ready
jakew02 said:
I just flashed the 2015-04-16 build and indeed the ril is broken.
I flashed my android-5.1 build from about an hour ago and rather than having the "no service" icon (outline of signal bars), it just says "No SIM", so I'm pretty sure RIL is working in this android-5.1 build. I just don't have Sprint service (but a Sprint variant, since it was the cheapest on Swappa when I bought this replacement last year) to actually test the calling, BUT a guy at work has Sprint so I can probably bug him this weekend for his SIM card, unless I can get a Sprint tester here?
Click to expand...
Click to collapse
Out of curiosity, does a self-build from the 4.4 trees have broken RIL?
If so that says there's something that needs to be cleaned out/up in the build server.
I didn't try out a self build I used the jenkins build from the server to replicate the scenario of a user downloading and flashing normally. I'll fire up a self build now with the 4.4 branches and check.
jakew02 said:
I didn't try out a self build I used the jenkins build from the server to replicate the scenario of a user downloading and flashing normally. I'll fire up a self build now with the 4.4 branches and check.
Click to expand...
Click to collapse
Is there any update?
Entropy512 said:
No problem. Can you reproduce this issue that supposedly started on Feb 18? I've been seeing various people complaining about it but can't figure out what might have caused it - since no one merged anything to the 4.4 branches around then...
Click to expand...
Click to collapse
Entropy512 said:
Out of curiosity, does a self-build from the 4.4 trees have broken RIL?
If so that says there's something that needs to be cleaned out/up in the build server.
Click to expand...
Click to collapse
I'm testing something right now to fix RIL for the 4.4 builds. I had moved the property out of the common device tree and forgot to add it to the jflte specific tree while I was working on another device.
Tonight's nightly should be fine, I'm compiling now to verify before submitting.
jakew02 said:
I'm testing something right now to fix RIL for the 4.4 builds. I had moved the property out of the common device tree and forgot to add it to the jflte specific tree while I was working on another device.
Tonight's nightly should be fine, I'm compiling now to verify before submitting.
Click to expand...
Click to collapse
That's strange - how did it break on Feb 18 as opposed to some other time then?
I don't see any changes to qcom-common or msm8960-common for quite some time?
I fixed it. I pushed a commit to samsung qcom common to move Ril to the device trees while I was bringing up lt03 and npushforgot to push to jf.
It's been fixed so the next nightly build will be working, confirmed on my device. Without Sim it still has signal bars
jakew02 said:
I fixed it. I pushed a commit to samsung qcom common to move Ril to the device trees while I was bringing up lt03 and npushforgot to push to jf.
It's been fixed so the next nightly build will be working, confirmed on my device. Without Sim it still has signal bars
Click to expand...
Click to collapse
Yeah. Thanks for figuring out why it broke.
I still wish I knew how it was working from October through until the build server housecleaning in February, since it should not have been working.
Great, thank you!
When will it be possible to download it? Last available version is 2015-04-17.
Thanks you all, Confirm now it's working fine.

H811 7.0 nougat cm14 rom

So I found that there is a nougat alpha build of cm 14 here.
https://androidfilehost.com/?fid=24591000424966343
I claim no responsibility for the rom I just found it and wanted people to know that there is a build available.
Currently there are no known working and not working details of the rom so comment with details if you end up flashing it.
Android4thewin said:
So I found that there is a nougat alpha build of cm 14 here.
https://androidfilehost.com/?fid=24591000424966343
I claim no responsibility for the rom I just found it and wanted people to know that there is a build available.
Currently there are no known working and not working details of the rom so comment with details if you end up flashing it.
Click to expand...
Click to collapse
Wouldn't bother trying it yet; leave it to devs, but if you want the updated one is here https://androidfilehost.com/?fid=24727369092696651 thanks to codeworkx and genesixx
Android4thewin said:
So I found that there is a nougat alpha build of cm 14 here.
https://androidfilehost.com/?fid=24591000424966343
I claim no responsibility for the rom I just found it and wanted people to know that there is a build available.
Currently there are no known working and not working details of the rom so comment with details if you end up flashing it.
Click to expand...
Click to collapse
I gave a slightly older version (9/14 build) a go last night.
Working: WiFi, cellular data, texting, GPS, NFC (as far as I could tell)
Not working: Camera, audio/video playback of any sort, phone (I could make and receive calls but hearing anything was a no go and the dialer app would randomly force close)
I also experienced the issue where if I flashed the ROM and Gapps in one go via TWRP I'd end up in a loop once the ROM booted where it'd never let me sign into my Gmail account. It'd just boot me back to the WiFi setup. Flashing the ROM itself and booting into it then flashing Gapps after worked fine. Was able to sign in to my Gmail account with no issues at all.
I could live without audio/video playback since I have a backup phone I could use for both but being unable to listen or speak when using the dialer app to make and receive calls is currently a "pass" for me since I'm waiting on some important calls. So if you absolutely need to use your phone as an actual phone wait til the issues there are fixed.
bangishotyou said:
I gave a slightly older version (9/14 build) a go last night.
Working: WiFi, cellular data, texting, GPS, NFC (as far as I could tell)
Not working: Camera, audio/video playback of any sort, phone (I could make and receive calls but hearing anything was a no go and the dialer app would randomly force close)
I also experienced the issue where if I flashed the ROM and Gapps in one go via TWRP I'd end up in a loop once the ROM booted where it'd never let me sign into my Gmail account. It'd just boot me back to the WiFi setup. Flashing the ROM itself and booting into it then flashing Gapps after worked fine. Was able to sign in to my Gmail account with no issues at all.
I could live without audio/video playback since I have a backup phone I could use for both but being unable to listen or speak when using the dialer app to make and receive calls is currently a "pass" for me since I'm waiting on some important calls. So if you absolutely need to use your phone as an actual phone wait til the issues there are fixed.
Click to expand...
Click to collapse
Yeah earlier builds didn't have the audio policies fixed; now they do. Obviously the camera is being worked on
CraigHardy said:
Yeah earlier builds didn't have the audio policies fixed; now they do. Obviously the camera is being worked on
Click to expand...
Click to collapse
i tried the most recent build (v....29) and the phone was still giving no phone or audio. is the newer build giving the same symptoms for you or only the ....21 build has functioning audio?
There is already a thread on CM14 for the H811 here:
http://forum.xda-developers.com/tmobile-g4/general/cm14-t3464339
ashtreylil said:
i tried the most recent build (v....29) and the phone was still giving no phone or audio. is the newer build giving the same symptoms for you or only the ....21 build has functioning audio?
Click to expand...
Click to collapse
Make sure you have updated your H811 to 20o. 20i isn't working very well with CM14 at this point.
AngryManMLS said:
There is already a thread on CM14 for the H811 here:
http://forum.xda-developers.com/tmobile-g4/general/cm14-t3464339
Make sure you have updated your H811 to 20o. 20i isn't working very well with CM14 at this point.
Click to expand...
Click to collapse
i thought i was forgetting something, thanks:highfive:
[ROMs] Source for LG H811 (T-Mobile) CM-14 Nougat
I have begun building CM-14 (Android AOSP 7.0.1, Nougat) for H811 and will post ~weekly builds here. The builds are from the CyanogenMod and Muppets (vendor proprietary) sources on github. This I will do until a developer at CM takes on the task of creating official "nightly" builds for LG H811 CM-14.
Please report problems here and I will forward them on to official CyanogenMod devs.
2016-10-04: Don't expect great things right away. On first builds the phone app crashes continuously and it will soak the battery dry in a few hours.
2016-10-07: The build today is working relatively nicely. Earlier problems may have been partly my error. I've been running today's build all day without major problems. Battery drain is higher than CM-13.0 version but not terrible. I'm planning on running this ROM over the weekend to see what bugs pop up. Only two so far – the external sd access as reported earlier; and flakey navigation button editing. Give it a try!

Best ROM for non-techsavvy individual?

I passed down my Nexus 10 to my father a few months ago, and the current ROM has got some corruption and so I'd like to flash something else.
He's essentially not techsavvy at all. I'm just looking for something rather stable for the moment that's moderately up to date for security reasons.
Once LineageOS starts building snapshots for the Nexus 10 I'll regularly update that with OTAs.
Any suggestions?
If you are ging for security a nougat rom is the best since it has the january security Update. But if you need a fully working rom you should Go for marshmallow. In this case the Last cm Release is fine. But it has only the december security Update in it.
XxM4tzexX said:
If you are ging for security a nougat rom is the best since it has the january security Update. But if you need a fully working rom you should Go for marshmallow. In this case the Last cm Release is fine. But it has only the december security Update in it.
Click to expand...
Click to collapse
Any idea where official cm13 is hosted/archived? I'll take your suggestion and install the last stable build of it. Then update his tablet to lineage once their stable builds start.

No!!! End of Lineage 13.0 official support for Tab Pro 8.4 (mondrianwifi)! ?

https://www.androidpolice.com/2018/02/13/lineageos-13-based-android-marshmallow-now-discontinued/
When I still thought I could continue using LineageOS 13 on my Tab pro 8.4 LTE (SM-T325) longer, and now it got discontinued.
Ending of support for the wifi version, means it should be the same for LTE version. :crying:
Because everything runs so smoothly and stable, unlike LineageOS 14 builds found in the forum which have many bugs like camera, torch not working. :crying:
Any chance of Lineageos 14 for Tab Pro 8.4 (WiFi and LTE) owners with bugs fixed?
Edit: Sounds like all of 13.0, sadly just the last version that supported our device. Makes sense I guess but sad to hear Likely a lot harder to get 14 working as we don't have any compiled drivers for things like camera under the new version of Android (no proprietary Samsung firmware for mondrianwifi runs the later Android and likely never will)
I'm happy to continue using it for the forseeable future
It's such a shame that the Galaxy Tab Pro 8.4 got such a bad software support from Samsung and it was not that popular among the community. Its successor, which is VERY similar, was much better supported. It also came with Kitkat (4.4.2) and it was updated up until Marshmallow (6.0.1). Moreover, LineageOS has an official 14.1 build for it: https://download.lineageos.org/klimtwifi Since they are so similar, isn't there any chance to backport some of the work done on Tab S 8.4 to the Tab Pro 8.4?
So sad but it is true
I just found this out as I had not checked for updates for my 8.4 tab (MondrianWiFi) running 13.0 in the last few months.... When I went to just check for an update there was none and in fact ALL builds were gone. I guess I better save and backup my current build in case it gets corrupt because it's the very last update I will ever get. ? Crap
Is there an Archive somewhere that the last updated version of 13.0 could be found?
I was going to update from the last CM flash I did about 2-3 years ago and I seem to have missed the boat...
TheDevilYouKnow said:
Is there an Archive somewhere that the last updated version of 13.0 could be found?
I was going to update from the last CM flash I did about 2-3 years ago and I seem to have missed the boat...
Click to expand...
Click to collapse
Luckily I went from the CM 12.1 snapshot to lineageos early this month. Here is a mirror I made of 2/11.
drive.google(dot)com/file/d/1oZZbqik-fwEeRN8qKHtlF0hkT9TPo46Y/view?usp=drivesdk
(Sorry, I didn't get the sha)
Looking at the internet archive page web.archive(dot)org/web/20180323182211/https://download.lineageos(dot)org/mondrianwifi
The mirrorbits link has been taken down, but it seems this build is the latest unless someone fixed whatever was preventing new builds.
Sorry for link formatting I don't have 10 posts. I hope it is allowed to post links like this but it seems to be a restriction on the posting itself and not a rule so IDK.
Craftyawesome said:
Luckily I went from the CM 12.1 snapshot to lineageos early this month. Here is a mirror I made of 2/11.
drive.google(dot)com/file/d/1oZZbqik-fwEeRN8qKHtlF0hkT9TPo46Y/view?usp=drivesdk
(Sorry, I didn't get the sha)
Looking at the internet archive page web.archive(dot)org/web/20180323182211/https://download.lineageos(dot)org/mondrianwifi
The mirrorbits link has been taken down, but it seems this build is the latest unless someone fixed whatever was preventing new builds.
Sorry for link formatting I don't have 10 posts. I hope it is allowed to post links like this but it seems to be a restriction on the posting itself and not a rule so IDK.
Click to expand...
Click to collapse
THANK YOU! I just subbed to this thread yesterday, hoping someone would come through with a download. My tablet was running Slim6 perfectly, but I had a memory card crash, so was wanting to check out other options. Came here a tad too late to get the ROM, but fortunately you posted. How is Lineage working for you?
drive.google.com/file/d/1oZZbqik-fwEeRN8qKHtlF0hkT9TPo46Y/view?usp=drivesdk
^^ link for people too lazy to cut, paste, and correct lol
opeth2112 said:
THANK YOU! I just subbed to this thread yesterday, hoping someone would come through with a download. My tablet was running Slim6 perfectly, but I had a memory card crash, so was wanting to check out other options. Came here a tad too late to get the ROM, but fortunately you posted. How is Lineage working for you?
Click to expand...
Click to collapse
I also switched due to SD failure. It has been working nearly perfectly. My only issues so far have been somehow triggering the dismissible internal system problem on boot (failed gltools install?) and android n-ify not working as well.
Haven't bought a new SD yet, so I can't testify about that.
Technically have been having random crashes, but I'm pretty sure it is battery related as it is much more stable at higher percents/charging/low load.
Craftyawesome said:
Luckily I went from the CM 12.1 snapshot to lineageos early this month. Here is a mirror I made of 2/11.
drive.google(dot)com/file/d/1oZZbqik-fwEeRN8qKHtlF0hkT9TPo46Y/view?usp=drivesdk
(Sorry, I didn't get the sha)
Looking at the internet archive page web.archive(dot)org/web/20180323182211/https://download.lineageos(dot)org/mondrianwifi
The mirrorbits link has been taken down, but it seems this build is the latest unless someone fixed whatever was preventing new builds.
Sorry for link formatting I don't have 10 posts. I hope it is allowed to post links like this but it seems to be a restriction on the posting itself and not a rule so IDK.
Click to expand...
Click to collapse
I wonder which version of GApps you're running? The one I tried didn't work at all. Crashes all the time.
KingsX said:
I wonder which version of GApps you're running? The one I tried didn't work at all. Crashes all the time.
Click to expand...
Click to collapse
Open gapps nano (the filename was open_gapps-arm-6.0-nano-20180401.zip)
There are some odd crashes with drive uploads and youtube randomly breaking, but that was happening on my 5.1 setup soo

Any way to remain on stock, but get the security updates?

I've use ROMs in the past, but never with the Essential phone. In fact my phone has run so well, I've never even factory reset it a single time, let alone put a ROM on it. But with Essential gone, I need a way to keep my phone secure.
I'm wondering what the best way to keep stock android (nothing wrong with stock) but allow myself to get the latest android updates as they come out. In looking at the ROMs there still seems to be some issues with bugs, and since this phone is my daily driver, I'd like it to be as stable as possible.
So is there:
1) A way to get the PH-1 on stock, but still get the important security updates somehow?
2) A rom available (even if android 9) that works for PH-1 that would be super stable but also get all new security updates?
Thanks in advance for any help.
holodude said:
I've use ROMs in the past, but never with the Essential phone. In fact my phone has run so well, I've never even factory reset it a single time, let alone put a ROM on it. But with Essential gone, I need a way to keep my phone secure.
I'm wondering what the best way to keep stock android (nothing wrong with stock) but allow myself to get the latest android updates as they come out. In looking at the ROMs there still seems to be some issues with bugs, and since this phone is my daily driver, I'd like it to be as stable as possible.
So is there:
1) A way to get the PH-1 on stock, but still get the important security updates somehow?
2) A rom available (even if android 9) that works for PH-1 that would be super stable but also get all new security updates?
Thanks in advance for any help.
Click to expand...
Click to collapse
Don't want to be rude, but here's the answer:
1. None
2. None
chanh2018 said:
Don't want to be rude, but here's the answer:
1. None
2. None
Click to expand...
Click to collapse
I could have sworn I saw something that basically said you can download the latest stock version (that includes security updates) and flash it every time there is a new update. But I guess I could have misunderstood?
holodude said:
I could have sworn I saw something that basically said you can download the latest stock version (that includes security updates) and flash it every time there is a new update. But I guess I could have misunderstood?
Click to expand...
Click to collapse
That was the case until Essential went out of business - you could do OTA updates, or download and flash yourself. The stock security updates were only provided by Essential, and the Feb 2020 update was the last one for this phone...
holodude said:
I could have sworn I saw something that basically said you can download the latest stock version (that includes security updates) and flash it every time there is a new update. But I guess I could have misunderstood?
Click to expand...
Click to collapse
You are correct: Android GSI. Info >here<
aleph23 said:
Android GSI
Click to expand...
Click to collapse
And how would that be "remaining on stock", as per the OP?
holodude said:
I could have sworn I saw something that basically said you can download the latest stock version (that includes security updates) and flash it every time there is a new update. But I guess I could have misunderstood?
Click to expand...
Click to collapse
No way to stay on stock & get security updates (well you will get some direct from Google ie the Google Play System Update, the last one shown lower down this page
https://source.android.com/security/bulletin/2020-03-01
and can be found in your settings under security, but its only a fraction of patches)
That means your best option is probably the Android 11 GSI when it's out of Developer Preview in a July (?) and hope it's bug free, else Lineage etc .... not that you want custom roms, sorry.
IronRoo said:
No way to stay on stock & get security updates (well you will get some direct from Google ie the Google Play System Update, the last one shown lower down this page
https://source.android.com/security/bulletin/2020-03-01
and can be found in your settings under security, but its only a fraction of patches)
That means your best option is probably the Android 11 GSI when it's out of Developer Preview in a July (?) and hope it's bug free, else Lineage etc .... not that you want custom roms, sorry.
Click to expand...
Click to collapse
Basically I'm looking for something safe and stable, whether it is ROM or otherwise. Right now I'm stable, but not safe. So you think my best bet is move to Lineage (to become safe) and then switch to the GSI when it is out of developer preview (and stable)?
From what I have read and asked here: https://forum.xda-developers.com/essential-phone/development/rom-evolution-x-4-1-69-t4073153
This ROM will give you what you are asking for as far as regular security updates are concerned. I have been waiting for Lineage to release an "OFFICIAL" version of Android 10 for our PH-1's but so far nothing. Also I would not mind going on Android 11 but then I do not think that will get monthly security updates either so I am thinking about trying this Evolution ROM out.... I have never worked with a phone with A/B slots so that is my only concern but after reading all the threads I am starting to understand how that works.
Hope this info helps you out.
holodude said:
Right now I'm stable, but not safe.
Click to expand...
Click to collapse
Security updates are overrated. ?
SirDigitalKnight said:
From what I have read and asked here: https://forum.xda-developers.com/essential-phone/development/rom-evolution-x-4-1-69-t4073153
This ROM will give you what you are asking for as far as regular security updates are concerned. I have been waiting for Lineage to release an "OFFICIAL" version of Android 10 for our PH-1's but so far nothing. Also I would not mind going on Android 11 but then I do not think that will get monthly security updates either so I am thinking about trying this Evolution ROM out.... I have never worked with a phone with A/B slots so that is my only concern but after reading all the threads I am starting to understand how that works.
Hope this info helps you out.
Click to expand...
Click to collapse
You & your big mouth! ?
https://download.lineageos.org/mata
(actually its been out a while, by the looks of it, but no mention here)
I'm the same boat as you, had hoped to flash LineageOS 17 months ago then move to Android 11 in few months time, guess it's decision time now.
---------- Post added at 03:31 AM ---------- Previous post was at 03:23 AM ----------
holodude said:
Basically I'm looking for something safe and stable, whether it is ROM or otherwise. Right now I'm stable, but not safe. So you think my best bet is move to Lineage (to become safe) and then switch to the GSI when it is out of developer preview (and stable)?
Click to expand...
Click to collapse
Guess for stability & functionality it would have to be LineageOS.
Looks like May version is ver 17.1 (Android 10), not sure how this compares to previous version re bugs/working functions, but that means previous ver is already a month out of date on security )
edit: see this post also
https://forum.xda-developers.com/es...7-1-essential-ph-1-mata-t4066163/post82606687
Also DO NOT use the Essential USB cable & DO NOT relock boot loader!
SirDigitalKnight said:
From what I have read and asked here: https://forum.xda-developers.com/essential-phone/development/rom-evolution-x-4-1-69-t4073153
This ROM will give you what you are asking for as far as regular security updates are concerned. I have been waiting for Lineage to release an "OFFICIAL" version of Android 10 for our PH-1's but so far nothing. Also I would not mind going on Android 11 but then I do not think that will get monthly security updates either so I am thinking about trying this Evolution ROM out.... I have never worked with a phone with A/B slots so that is my only concern but after reading all the threads I am starting to understand how that works.
Hope this info helps you out.
Click to expand...
Click to collapse
I'm on EvoX the only thing tht is not t working very well, is tht if u fast forward or rewind on Netflix ur phone reboots, hopefully fixed next update, but I'm happy with this ROM, the touch lag is almost non existence for some reason, glad they managed to fix tht. Also L1 certification is still there. The 360 camera workes better in this Rom for some reason. The best part is the customization though, so much
IronRoo said:
You & your big mouth!
https://download.lineageos.org/mata
(actually its been out a while, by the looks of it, but no mention here)
I'm the same boat as you, had hoped to flash LineageOS 17 months ago then move to Android 11 in few months time, guess it's decision time now.
---------- Post added at 03:31 AM ---------- Previous post was at 03:23 AM ----------
Guess for stability & functionality it would have to be LineageOS.
Looks like May version is ver 17.1 (Android 10), not sure how this compares to previous version re bugs/working functions, but that means previous ver is already a month out of date on security )
edit: see this post also
https://forum.xda-developers.com/es...7-1-essential-ph-1-mata-t4066163/post82606687
Also DO NOT use the Essential USB cable & DO NOT relock boot loader!
Click to expand...
Click to collapse
Very strange that no one has started a new thread in the Custom ROM section about this... (This being an official release version of Lineageos 17.1) you would think it would be bigger news? There is still only an Unofficial thread... strange..
Anyway IronRoo let me know what you decide to do and how it goes... I am still on the fence as my PH-1 is currently working perfect on stock 10 but it is of course on the Feb 29th security patch... plus I haven't done a custom ROM install since my LG G5 but I hear it is like riding a bike... lol :silly::fingers-crossed:
SirDigitalKnight said:
Very strange that no one has started a new thread in the Custom ROM section about this... (This being an official release version of Lineageos 17.1) you would think it would be bigger news? There is still only an Unofficial thread... strange..
Anyway IronRoo let me know what you decide to do and how it goes... I am still on the fence as my PH-1 is currently working perfect on stock 10 but it is of course on the Feb 29th security patch... plus I haven't done a custom ROM install since my LG G5 but I hear it is like riding a bike... lol :silly::fingers-crossed:
Click to expand...
Click to collapse
For LOS, I think we should wait until their server is back, and few more releases come out.
LineageOS 17.1 for Essential is so new, only couple releases, and still in updating state.
chanh2018 said:
For LOS, I think we should wait until their server is back, and few more releases come out.
LineageOS 17.1 for Essential is so new, only couple releases, and still in updating state.
Click to expand...
Click to collapse
Yes, many will agree, though I'm OK with giving it a go but I need to buy a new high quality USB cable as kid damaged my Samsung one and have only a cheap 6" one which I'm not sure I trust to flash without bricking phone.
SirDigitalKnight said:
Very strange that no one has started a new thread in the Custom ROM section about this... (This being an official release version of Lineageos 17.1) you would think it would be bigger news? There is still only an Unofficial thread... strange..
Anyway IronRoo let me know what you decide to do and how it goes... I am still on the fence as my PH-1 is currently working perfect on stock 10 but it is of course on the Feb 29th security patch... plus I haven't done a custom ROM install since my LG G5 but I hear it is like riding a bike... lol :silly::fingers-crossed:
Click to expand...
Click to collapse
Just did a quick websearch and a few have tried flashing it reddit and here on the 16 thread, and it's suggested wait for next release (first recovery had issue, but now fixed, but next release of ROM should have a few fixes & Lineage build servers are down so not sure when new release will drop)

Categories

Resources