Why still no official status of Lineage OS? Fp issue is solved i guess!
LineageOS community is pretty strict about how they should host a ROM image for any particular phones / tablets on the official website, in fact they have set of rules which you HAVE to abide by, before they would bother to dish up the LineageOS ROMs for, for example, our OnePlus 6T. They do not want half-a**ed builds (that wastes their time).
There are a few bugs still remaining, and we now have to deal with a new problem, hardware mismatch warning (OnePlus have just done something to the recent bootloader in International version of the OxygenOS to discourage the T-Mobile OnePlus 6T users from trying to do conversion from T-Mobile to International, thus the dreaded hardware mismatch warning, however since the Linux kernel just check for two things, bootloader ID and modem status, it can be bypassed) to tackle first before we would see official LineageOS 16 ROM, and it will be distributed via LineageOS page pretty soon.
Related
Coming from a Note 1 (N7000), I'm quite satisfied with the work of XDA developer bauner . He set his focus on providing a stable CyanogenMod based ROM wich is always updated with the latest security patch level - no fancy, just stable and secure. He is even working on a CM14.1 ROM.
I got an old Note 3 from my son. I'm not sure, if I should keep it, despite it's way better hardware wise than my Note 1 from 2011. I keep some business related data on my phone, so my focus is on security.
From looking around, I found several ROMs for the N9005 which haven't been updated for months. I found some other ROMs (based on Note 7 stuff) which are updated frequently, but seem to focus on fancy stuff, nice features, but never mention any security related update.
So I'm wondering: is there really no ROM for N9005 with focus on security? Or did I miss one?
I'm sure most of the CM13 roms comes with the latest security updates. Trader is still updating temaseks cm13 with security upgrades for example. You can also go go ahead and try out one of the two CM 14.1 roms here on the forum.
The CMs are constantly updated. If you want 6.0, there is Temasek's. Otherwise, there are also the CM14.1 builds from trader418 and christer12, even if the first one seems to be more stable
still can't find a suitable ROM
Thanks for your response.
Reading your comments, I was continuing searching all XDA ROM threads for Cyanogen ROMs. Google is pushing security updates on a monthly base. So I was looking for a ROM which follows this path. I would even pay a monthly fee for it.
From what I've read so far, I got the impression that the work on Temasek CM13 ceased in favor of the CM14 builds (which are not stable enough for my personal use case). From android-hilfe.de (German forum)
Is there anybody working on this ROM? - No, work on CM13 stopped
Click to expand...
Click to collapse
Looking at the Temasek thread I can see under "current info"
Android Version: 6.0.1_r30
Click to expand...
Click to collapse
A quick google search shows this version is from April 2016. Looking at his repository, Temasek stopped his commits in August and I wasn't able to find another repo which is still maintained. Trader is developing CM14 and he is supporting CM13 for Verizon. There's a Temasek 12.2 from October, also build by Trader, but I don't know the patch level. Looking at his Twitter account, Trader is busy with university stuff at the moment, so he had to reduce work on the ROMs - he omitted at least two patch levels (or even more).
Looking at Purify, the last version is also from October (hmm, does he depend on the work of Trader?). And finally Christer closed his threads CM threads for unknown reasons. Maybe because he was not providing his kernel sources, like the XDA guidelines demand for GPL stuff.
So, which CM based ROM did I miss? Is there one I'm not aware off? It seems I still can't find any CM13 ROM which is actively maintained on a regular basis.
Snoere said:
Thanks for your response.
Reading your comments, I was continuing searching all XDA ROM threads for Cyanogen ROMs. Google is pushing security updates on a monthly base. So I was looking for a ROM which follows this path. I would even pay a monthly fee for it.
From what I've read so far, I got the impression that the work on Temasek CM13 ceased in favor of the CM14 builds (which are not stable enough for my personal use case). From android-hilfe.de (German forum)
Looking at the Temasek thread I can see under "current info"
A quick google search shows this version is from April 2016. Looking at his repository, Temasek stopped his commits in August and I wasn't able to find another repo which is still maintained. Trader is developing CM14 and he is supporting CM13 for Verizon. There's a Temasek 12.2 from October, also build by Trader, but I don't know the patch level. Looking at his Twitter account, Trader is busy with university stuff at the moment, so he had to reduce work on the ROMs - he omitted at least two patch levels (or even more).
Looking at Purify, the last version is also from October (hmm, does he depend on the work of Trader?). And finally Christer closed his threads CM threads for unknown reasons. Maybe because he was not providing his kernel sources, like the XDA guidelines demand for GPL stuff.
So, which CM based ROM did I miss? Is there one I'm not aware off? It seems I still can't find any CM13 ROM which is actively maintained on a regular basis.
Click to expand...
Click to collapse
My fork of temaseks cm13 is found at GitHub.com/trader418. I'll upload an update later today with the latest security patch. I aim for a monthly update at the least however uni work had been getting on top of me. But now I'm finished for Christmas I have more time.
One of the biggest reasons why I can still bear my OnePlus 2 and its Snapoven 810 is because of custom kernel and ROM support. I was curious if anyone knows of some developers who are planning on working on the OP5. Or if you are a developer yourself, feel free to tell us your plans.
When I read the a couple of the discussion threads there were posts that outright said that person X intended to develop a custom ROM based on the usual bases (e.g. AICP). Unless OnePlus does an about face on their policies seen with the 3 and 3T their devices for all intents and purposes these phones are the new Nexus line. Oneplus have unlockable bootloaders, publishes their code, use Snapdragon processors and are almost unbrickable. Heck with their last two phones you don't loose your warranty if you unlock the bootloader and install a custom ROM.
Unless their is some nasty surprise either to those development policies and or to the hardware itself I'll be unlocking the bootloader within the first hour after proving the handset works simply to avoid the user data wipe later on. That even before a recovery image is available (e.g. TWRP).
Seraph08 will be making 2 ROMS. He's already got some builds ready for testing.
flar2 and Lord Boeffla will be doing stuff for the Oneplus 5
Lord Boeffla = Boeffla Kernel
flar2 = ElementalX Kernel
Hey guys,
I'm just looking for someone to point me in the right direction. Basically, my school has this web portal logon thing called Cloudpath (formerly xpressconnect) that requires you to log on to the portal's network in order to follow the instructions in your web browser for your specific OS. The problem arises with Android. It requires you to download an app, which does all the nitty gritty certificate installation and configuration for you. However, whenever I try this on a CUSTOM ROM (LOS-based and DU), I end up in a connecting loop. I never get connected to the secured network even though the certs appear to be installed correctly. I've tried using the app and doing it manually by downloading the certs myself. This only occurs on custom nougat roms, but works on stock MM (I haven't tried MM roms, because I want nougat).
As far as I know this problem only affects this phone after I install the rom and OpenGapps. Some of my peers have LOS and have gotten it to work, so I'm the only one, and the tech staff have no idea what to do. I don't have the log file on me, but if you need it, I can post it (they're pretty long, but seem to be detailed up until the connection part which just flops between CONNECTED and DISCONNECTED).
Is this a problem with the modem or the roms themselves? I was going to wait until the nougat kernel blobs got integrated to LOS, before trying again as I don't want to use the experimental build because it's a month old now. This problem has been around since at least January of this year. If there is a non-los based nougat rom, I would be glad to try that too. otherwise, I'm at a loss and I need some direction.
Any help is appreciated!
Seeings as how all of our Nougat ROMs are a mixed bag of partial MM and part Nougat still, and all custom ROM's for the MXPE use LoS's device tree, I am thinking this is a ROM issue, probably with some binary blob we don't have yet. The kernel source just released a few weeks ago, give it time and custom ROM's will get better (we think), and if the MXPE ever gets official Nougat, we will probably have better binary blobs too.
If it works on stock Marshmallow, it obviously isn't a radio thing, because your Nougat ROM's use the same radio firmware.
I don't have much else to say, but I would try a custom Marshmallow ROM and see if it works... if it fails as well, the problem is something in the LoS core device tree and it will need some developer's special attention (good luck with that, since we are considered to have a stable device tree it takes some work to get it changed), but if it works, chances are good that once custom Nougat ROMs get updated more it will likely work.
In a last ditch effort. I tried flashing the experimental build after posting this article, and it actually works! Now, this isn't the ideal situation given that there are some bugs (that I haven't run into yet) and that this build is a month old now. But for now, I'm satisfied. I just hope these blobs get integrated to official LOS soon.
Progress on that is here: https://review.lineageos.org/#/q/project:LineageOS/android_device_motorola_clark
If there are any roms out there that are considered stable and have these implemented now, I would appreciate it, otherwise, I think I'll be set for a little while. Thanks for your help!
Hey guys! Some very talented developers have been working on unofficial releases for a while already, and I am unsure whether to go for their takes or wait until an Official version is released. Any predictions on when this might happen? Or should I just void my warranty and go for Vache's build? Thanks!!!
I might also like this. While Motorola says they will release Oreo for Potter, they seemingly haven't provided any timetable for that. I am a bit hesitant to install a LineageOS nightly on my daily driver, but I would love having the option, especially if it turns out that Motorola botches the Oreo upgrade.
jtull89 said:
I might also like this. While Motorola says they will release Oreo for Potter, they seemingly haven't provided any timetable for that. I am a bit hesitant to install a LineageOS nightly on my daily driver, but I would love having the option, especially if it turns out that Motorola botches the Oreo upgrade.
Click to expand...
Click to collapse
I have been using Vache's/fAIyaZ 7.1.2 build for some days now. Only found one bug, Skype wouldn't manage to access the camera for video-chatting, but I found a solution for it (activating Camera 2 API from this thread: https://forum.xda-developers.com/g5-plus/themes/potentially-google-camera-port-t3684264 ). Other than that, everything works perfectly (and a lot better than the Moto built-in tracking suite they ship the phone with).
Applying an unofficial fix to an unofficial port sounds a bit problematic. Do you think it would be possible for Vache/fAlyaZ to fix this in their port somehow? Or would it be more of a gapps thing? Or neither?
It seems so insane to me that there is no official LineageOS for Potter yet? I couldn't have even imagined that it wouldn't be released quickly when I bought the Moto G5 Plus - I though it is such a popular phone, so well reviewed for the price, able to be unlocked, etc. How can it no be better supported by the LineageOS team?
Sorry to necro this thread, but Oreo has now been officially released for Potter, after seemingly forever. What are the chances of getting an official 15.1 build for Potter any time soon?
I know Vache's unofficial build is much loved on here, and I think there's a 16.0 unofficial build I've seen flowing around as well, but some of us would rather go with an official build if one is available.
Don't mean to be a d*ck, but just follow the trending topics on the forum and you'll see where everyone has flocked to. At the moment I believe there's no need to program Lineage for Pie, when we have one extremely good AOSP based version online. Install the Pie version of the system that can be shot from a bow and never look back... Vache did a great job for as long as he did it, and a couple of other contributors too, so <3 thank you
now everyone seems to be somewhere else, that's how it goes
all the previous versions and knowledge gained from them kept being passed forward to ports from the next version of Android as well, so you'd have to look at Lineage Pie. Lineage16 seems to still be too raw for Potter, which means you likely won't see any official version soon. With Pie out, everyone's efforts turn to it, so you can see also that the 15.1 thread is pretty much dead.
I'm currently using LOS 15.1 for my axon 7 but since it's not maintained anymore, I was wondering if there were any other ROMs that were being made or maintained for this device. Thanks in advance!
Im currently using stock A2017G B03 and move on with Huawei Mate 20x, i have been there done that with all known working GSI Roms and to be honest nothing feels as stable as stock especially when you need dolby atmos and banking apps, but if your device is not your primary device then you can try GSI Roms from Erfan or nFound.
Blankisblank said:
I'm currently using LOS 15.1 for my axon 7 but since it's not maintained anymore, I was wondering if there were any other ROMs that were being made or maintained for this device. Thanks in advance!
Click to expand...
Click to collapse
A lot of people have Treble'd their device and went with GSIs
I'm on LiquidRemix which seems to work nice with Speedy Vendor and Baddar Kernel
ibphantom said:
A lot of people have Treble'd their device and went with GSIs
I'm on LiquidRemix which seems to work nice with Speedy Vendor and Baddar Kernel
Click to expand...
Click to collapse
So I'm a bit confused, is LOS not made from a GSI? Or what's the difference between GSI's like LiquidRemix versus LOS?
Blankisblank said:
So I'm a bit confused, is LOS not made from a GSI? Or what's the difference between GSI's like LiquidRemix versus LOS?
Click to expand...
Click to collapse
When you Treble your device you split some partitions of your phone, particularly the vendor partition which opens the possibility of using ROMs from other phones. LOS offers a ROM version and GSI. The ROM versions are usually made just within the threads of the particular device. Some GSIs are broken, but that's because of a hardware mismatch but an updated vendor usually takes care of any mismatches. Each GSI/ROM has it's own custom set of features.
If you like LOS, you could try out the latest LOS16
But check out Havoc or LiquidRemix if you want to test GSIs
Keep in mind that we *may* have one official ROM supported for our phone. But GSIs are usually built monthly by a group of devs and they keep the security features up to date and make small changes like the AOSP public chain from Google.
ibphantom said:
When you Treble your device you split some partitions of your phone, particularly the vendor partition which opens the possibility of using ROMs from other phones. LOS offers a ROM version and GSI. The ROM versions are usually made just within the threads of the particular device. Some GSIs are broken, but that's because of a hardware mismatch but an updated vendor usually takes care of any mismatches. Each GSI/ROM has it's own custom set of features.
If you like LOS, you could try out the latest LOS16
But check out Havoc or LiquidRemix if you want to test GSIs
Keep in mind that we *may* have one official ROM supported for our phone. But GSIs are usually built monthly by a group of devs and they keep the security features up to date and make small changes like the AOSP public chain from Google.
Click to expand...
Click to collapse
So GSI's like LiquidRemix or Havoc are supported across multiple devices while ROM's are built more to match that specific device? Would that be correct? And we have a supported ROM still?
Blankisblank said:
So GSI's like LiquidRemix or Havoc are supported across multiple devices while ROM's are built more to match that specific device? Would that be correct? And we have a supported ROM still?
Click to expand...
Click to collapse
Yeah. GSIs are meant to be shared across devices with similar hardware and issues with a broken GSI are tweaked by having an updated Vendor file. ROMs are specifically made to match all the hardware in a particular model of phone. I think all the ROMs for the Axon 7 are unofficially supported at this point, which means a 3rd party dev decided to pull the source code of a popular ROM like Lineage and build it for our particular model just because they were feeling nice and appreciated by the people who use it.
ibphantom said:
When you Treble your device you split some partitions of your phone, particularly the vendor partition which opens the possibility of using ROMs from other phones. LOS offers a ROM version and GSI. The ROM versions are usually made just within the threads of the particular device. Some GSIs are broken, but that's because of a hardware mismatch but an updated vendor usually takes care of any mismatches. Each GSI/ROM has it's own custom set of features.
If you like LOS, you could try out the latest LOS16
But check out Havoc or LiquidRemix if you want to test GSIs
Keep in mind that we *may* have one official ROM supported for our phone. But GSIs are usually built monthly by a group of devs and they keep the security features up to date and make small changes like the AOSP public chain from Google.
Click to expand...
Click to collapse
ibphantom said:
Yeah. GSIs are meant to be shared across devices with similar hardware and issues with a broken GSI are tweaked by having an updated Vendor file. ROMs are specifically made to match all the hardware in a particular model of phone. I think all the ROMs for the Axon 7 are unofficially supported at this point, which means a 3rd party dev decided to pull the source code of a popular ROM like Lineage and build it for our particular model just because they were feeling nice and appreciated by the people who use it.
Click to expand...
Click to collapse
Okay so one last question, is there anything that you lose from moving to a GSI compared to a ROM? Like for example, would I still be able to use the superior audio DAC of the axon 7 or would that not be possible since that's too device specific? Thanks in advance!
Blankisblank said:
Okay so one last question, is there anything that you lose from moving to a GSI compared to a ROM? Like for example, would I still be able to use the superior audio DAC of the axon 7 or would that not be possible since that's too device specific? Thanks in advance!
Click to expand...
Click to collapse
Not that I know of. I'm able to use VoLTE and Viper4Android for the HD DAC and I'm on GSI.
Edit: And now that I remember, you should check out raystef66 ROMs. Those are still active for our phone and from an awesome dev.