yashsingh1/xdaforums huggingface dataset:
[LineageOS News & Discussion] jmonline86:
Nightly/weekly

Can someone just confirm something for me please.... The official Lineage nightlies, are these called nightlies but actually built weekly (they mentioned weekly releases in the blog post)?

I only ask because the nightly for my device (Oneplus one bacon) is dated 23rd Jan and its now the 29th.

Thanks.
[LineageOS News & Discussion] CutGlass:
Yes. (not much of an answer, not meant to be sarcastic). Historically "nightlies" were "unstable" and CM14.1 had very frequent builds and just decided on that name, "unstable" means buggy and there are automated processes that build a new version every night, hopefully with more fixes than errors. This is not to say that "unstable" does not mean it does not work, early nightlies are more prone to bugs or oddities. CM took the decision not to build in the theme engine until after 14.1 reached a certain point in stability and that may be a problem in the future.

Remember all you are looking at is a link on a website, the devs are building these unstable version many times a day, the date on the newer version is quite irrelevant because all you are looking at is a download that someone has decided was necessary to update, possibly a major bug was fixed, of the developer may just be going on holiday. "Weekly" is a very fluid notion and probably an aim rather than a law. Remember with LineageOS (other people are starting to call it LOS in other threads) you have more security than relying on a carrier over the air update (OTA) of for example Microsoft and Adobe have "Patch Tuesday" the first tuesday of every month, so if a security issue happens then your PC is vulnerable until that time if things are set in stone, I bet what will happen is "weekly" will mean that the section of LOS which notifies about updates in the settings will ping every week if there an update, because someone has decided that to put that restricting after CM's collapse on a back burner. In reality I think this will change and updates will be daily to spread out the server load.
[LineageOS News & Discussion] jmonline86:
Excellent thank you
[LineageOS News & Discussion] jerflash:
Quick question. I downloaded the new nightly via the system on my device. When I go to install via recovery in TWRP I cannot locate the folder with the update... On CM it was just called cm update. Any ideas? Thanks
[LineageOS News & Discussion] jhedfors:
/data/data/org.lineageos.updater/app_updates
[LineageOS News & Discussion] CutGlass:
Yes a Russian gentleman find it at /data/data/org.lineageos.updater/apps_data or something really close to that. :)
[LineageOS News & Discussion] jerflash:
Oh alright thanks! Just wonder why they would not put the update file on the root directory to make it easy to find... Lol
[LineageOS News & Discussion] CutGlass:
Security? I believe that an app downloading data into that named directory is the only one that can play around with it even with su (I couldn't put a PC download into that file using file manager when rooted) whereas the original download location would have need world writeable permissions.

A nice design compromise would probably be to put in a link to that folder from the original CM download location.
[LineageOS News & Discussion] jerflash:
OK well I was just comparing it to CM is all. If this is the case wouldn't it be best that when I hit install on the device that a script would run as soon as recovery launches? Some Roms have been able to do this in the past. Unsure if it can be made compatible with TWRP though
[LineageOS News & Discussion] CutGlass:
I agree we've been having this discussion over at the LineageOS M8 thread as there's also a developer option to replace the recovery image but because of the twrp incompatibility it doesn't work. So later on I'll be testing with the last CM recovery to see what happens and posting screenshots as to functionality compared to twrp. It would be better if the whole updater were twrp compatible, I also have an encypted phone so have to double check and decrypt to check it's not that which is blocking the installation of the LineageOS recovery (possibly it should be made available as a separate download in extras like su ?).
[LineageOS News & Discussion] jerflash:
Ah ok i was also thinking of trying CM recovery on the 2 devices i have LineageOS running on currently LG V500 and LG V410 tablets. I dont think it is encryption alone because both of my devices are not encrypted. It would be great if they could make the updater TWRP compatible.

CM recovery might not work either considering the download location for the update file is in a different place... have to see.
[LineageOS News & Discussion] CutGlass:
How about divide and conquer, I take encrypted, you take non-encrypted? save me more than half the work. I'm going to attempt the last recovery from 25/12/2016 - though thinking about that it may not support encryption.
[LineageOS News & Discussion] jerflash:
OK but it would be later on tonight since i have to work a bit late. Lets see what we get
[LineageOS News & Discussion] CutGlass:
I can save you the trouble :)

Firstly CM recovery from the 25th December refused to recognise the encrypted partitions, I ended up going back to twrp and formatting everything unencrypted.

I chose to use the Lineage OS update from 30th Jan, clean flashed to then download the one on the 31st into the correct location.

As we already know twrp is not supported for recovery scripts. Neither is the CM recovery image, (see images below) and also interestingly the developer options for the 30th do not include the option to overwrite the recovery image (but it never got close to that anyway). The only other option that I can think of to place the lineageOS zip where CM recovery would find it to update, you might like to try that and see if the 31st has a recovery image in it that move CM recovery out of the way (in unofficial nightlies there has also been a message in the logs to the opposite effect where it kept the recovery image). If one of the developers would like to chime in about unzipping the LineageOS zip and where the recovery image is located so that one could flash it through fast boot it would be appreciated, (or release it as an extra in zip format). I'm tired and have a phone to restore and re-encypt :D

Btw add-ons was installed and permissions grants to add and apps to avoid any potential permissions issues.

Captions for Images below:

Stock 30th Jan no Gapps installed

Correctly registers that update to 31st is available

Confirmation that the 30th is installed.

Correctly downloaded and ready to install

Recovery script not compatible with CM recovery image from 25th.
[LineageOS News & Discussion] CutGlass:
Update

The difference in the 30th and 31st developer options is an additional feature called Update Recovery

Found the recovery image in the zip complete with an installation script referencing a patch. Too tired to currently investigate further but the script looks for a specific file (probably put into place by update recovery) and then applies a patch. This script should output a log message, but installing the zip directly in twrp does not appear to initiate it as there is no message in the logs. Tomorrow I may try and flash the recovery image to see what is what, or look at the files involved if I'm feeling less reckless :cowboy:
[LineageOS News & Discussion] CutGlass:
I failed :( having opened the zip, read the scripts and tried various things, it looks like to get the LineageOS recovery image one needs to applypatch which seems to be a delta patch on a binary file in an in memory environment. It's beyond my abilities (well I could use an emulator to build but it's not man hour efficient) so I guess the only way is to ask the LineageOS devs for an extras package for the recovery image, or to fix the updater to be twrp compatible.

---------- Post added at 11:53 AM ---------- Previous post was at 11:14 AM ----------

Now done, bug requests submitted (in the wrong location, but they'll probably see it :fingers-crossed:) for link to download folder for the updater installer, TWRP compatibility, recovery image released as an add-on and recovery image generated by default by installed only dependent on the setting in developer settings (so for example a person could choose not to overwrite the recovery image, but have a device specific LineageOS image to test out with fast boot).
[LineageOS News & Discussion] bigsupersquid:
if you want recovery.img it's easy enough to get with ROM source code. mka recoveryimage instead of mka bacon.

mka bacon builds recovery as well as ROM. you can ask you're device maintainer for a recovery.img maybe.

But the issue with the patching you found in the zip is (if I've read it right) patching recovery from boot.img
[LineageOS News & Discussion] CutGlass:
Interesting, it's a few things though.

the updater is not twrp compatible so several devices are requesting the location of the downloaded zip entirely

former ROM's used to build a recovery image but keep it renamed so as to give the option to overwrite.

the update recovery setting in developer tools is not working

I may try that out, there is a script /system/bin/install-recovery.sh but it doesn't appear to work. In the zip applypatch is used to patch an image possibly created on installation but I can't find it and as the Update Recovery setting is non-responsive...

Unfortunately the bug report was closed. The lineageOS team apparently are only working on "regression" and not open to bug fixing on the weekly/ nightly builds yet.
[LineageOS News & Discussion] bigsupersquid:
The install recovery script only runs if developer settings are set to install recovery. If that is broken there's not a good easy way to use applypatch to create a recovery.

Roms still build with a recovery image, that just usually doesn't get uploaded anywhere because it's seperate from rom.zip and maintaining recovery as well as rom is extra hassle.

The image that is patched with applypatch for recovery is the boot.img

Edit: sorry about the OT in the index thread
[LineageOS News & Discussion] CutGlass:
The developer settings appear broken, in that script see the log messages for either build failure or success? They never appear in any output. I also recall with one ROM (can't remember which), that it was very verbose and explicitly stated "built recovery, moving to new filename to avoid overwriting" or something very similar. I'd like to see LineageOS's recovery image, CM's wasn't as good as twrp IMHO, but I would like at least to be able to make the choice, or having the new updater work with twrp would be nice.

I've attempted the good netizen thing and answered multiple times the location the Updater uses for downloads on my device, also as the feature is undocumented,

holding down on a download in the LineageOS Updater gives you the option to delete it

(sorry, hoping that will get picked up on search through the forum). My concern is that with the incompatibility then people will download the ROM twice (putting more strain on lineageOS's new servers which did appear to be having issues on my device thread with being able to complete and verify a download) once to the updater, once to a PC to twrp, and filling up their storage with ROM's in a location that they don't know where to delete.
[LineageOS News & Discussion] bigsupersquid:
Haven't ever once tried the updater, even back in cm. I've never owned an officially supported device and for years I've had to build my own roms. Sometimes recovery too. So I'm not aware of any of the issues with the ota updates.

Last time I looked at it this year the cm recovery was still what was built, I haven't seen any lineage changes (though my last build was at the beginning of the year, they may well have changed up the recovery since then.)

My OT comment meant that this non-release discussion should probably be moved to a more appropriate thread.
[LineageOS News & Discussion] CutGlass:
Possibly the INDEX should be removed from the heading as originally this was an unofficial build thread to keep things going during transition, and the LOS Updater and location of files is a cross-device issue?
[LineageOS News & Discussion] bigsupersquid:
well, anyway, fyi, just did repo sync and built... recovery still says cm recovery and doesn't look special. I've not set up an ota server to test updates or anything.
[LineageOS News & Discussion] CutGlass:
Tell me Sensei, where did you attain the skills to build for an unsupported devices? and the firmware? (I had a brief look at how to build a ROM, seems like firmware's pretty important). Can you point me in the direction of thread or guide?
[LineageOS News & Discussion] abhikhampariya:
I just installed lineage OS on my Samsung note 2. Flashed the Rom through CWM. Flashed Gapps through it too. Now when I open any Google app including playstore, it says Google play services has stopped or Google play services keeps stopping. Flashed gapps again but the problem is still there. I know there are several other threads for the same problem but I'm in a hurry. Sorry for creating this new thread. Please help me out here. I flashed android 7.1.1 ARM stock Package.
[LineageOS News & Discussion] CutGlass:
Dirty flash? what were you updating from ? Did you read the instructions about using experimental (if you were upgrading from non-lineageOS).
[LineageOS News & Discussion] abhikhampariya:
I was updating from stock Android 4.4.2. My device was always rooted but never really thought of flashing a different Rom as I'm using a oneplus 2 now. But I did it tonight and I'm in trouble now. Yes I read the instructions and everything is working fine but the Google apps
[LineageOS News & Discussion] jhedfors:
[MENTION=5039686]mgbotoe[/MENTION] This thread needs to be seriously cleaned-up and/or closed. The discussions here have gone seriously off-topic (seriously people! Those discussions belong in the specific ROM threads).
[LineageOS News & Discussion] CutGlass:
I agree somewhat, but with issues like the new LOS updater being cross-device where would that fit into xda rather than having the same questions scattered through multiple devices (namely the location of the downloaded file, that twrp doesn't work, that the Update Recovery setting in developer options does not work).

The LOS devs needs to be able to find this information too :fingers-crossed: as they are not accepting weekly/nightly bugs from the public.
[LineageOS News & Discussion] mgbotoe:
Closing is not a bad idea.

I have mention before, stay on topic so I do not have to look through a lot of unneeded posts. Makes my task hard than it needs to be.
[LineageOS News & Discussion] mgbotoe:
I have placed enough links in the initial posts to report things. Developers do not look in here for development informations.
[LineageOS News & Discussion] mgbotoe:
Please as in the appropriate forum, preferably the QnA section.
[LineageOS News & Discussion] CutGlass:
As mentioned LOS's jira is closed to the public.
[LineageOS News & Discussion] bigsupersquid:
Agreed, I'll be quiet here now
[LineageOS News & Discussion] nikhilbhalwankar:
Official lineage OS is available for Moto G 2014 Titan. Pls update the links section.
[LineageOS News & Discussion] twidledee:
I need some help with my Elsa tmo [H918 stock j ] I soft bricked it about a 9 days ago while I was installing gapps on top of lineage OS 14.1. I had rooted using Cow mid January , 17.

Using fat I resized, formated, wiped ----system, data, cache--- partitions. Then I formated Dev/Art in F2FS which resulted in some very interesting stuff. Now that I've gotten TWRP back on it ( or helped it revive ) through fastboot.

File system looks good.

/system

file system ext4

size 5416MB

free 5405MB

used 10MB

backup size 10MB

/data

file system ext4

size 52528MB

free 5245MB

used 0MB

backup size 0MB

/cache

file system ext4

size 0MB

free 0MB

used 0MB

backup size 0MB

Is there any cmds, coding, prompts.... etc.... i can run in the twrp terminal to gather more information to the condition of the device?

No stock. No roms. Nothing except Android I think

A clean blank state?

The device Had full SElinux and MTP this whole time it was bricked
[LineageOS News & Discussion] jhedfors:
Could you please move this to another thread, as this has nothing to with the purpose of this thread. Thanks.
[LineageOS News & Discussion] twidledee:
ok
[LineageOS News & Discussion] elsquare:
[MENTION=5039686]mgbotoe[/MENTION]

Another one for the Samsung S4, but LOS 13 for those who can't live without xposed/xprivacy (which may come to N some day - fingers crossed!). Runs fine for me.

[ROM][GT-I9506][ks01ltexx] CyanogenMod 13.0 UNOFFICIAL for the Galaxy S4 LTE-A By: [MENTION=4861355]kyasu[/MENTION] / [MENTION=7485732]gebaya[/MENTION]

https://xdaforums.com/showthread.php?t=3264134
[LineageOS News & Discussion] dantexaiver:
Getting worried as very few devices have been presented
[LineageOS News & Discussion] Aamod Joshi:
What is the aim of LineageOS? Like Cyanogen had an aim to "put a bullet through Google", similarly, does LineageOS have an aim like that?
[LineageOS News & Discussion] CutGlass:
That would be difficult since google provides the codebase.

Google gives away android for free, their business model is to charge for the closed source apps installed on a manufacturer's phone like Maps and Hangouts, neither of which Lineage or CM were going to provide a viable alternative.

What is the point? Well with the slim as near to AOSP as possible (that's the google code base) you have something that is near as pure android / nexus / pixel that you can get and with a nano or pico package you can install very few apps. The lack of apps means less memory requirements, the near to AOSP means that when google release a security update, like the one in Feb where Apps could take over a phone, then in theory lineage will respond a lot quicker with an OTA than your handset manufacturer. (Alas I believe that they were slightly delayed on that update but it's coming next week apparently which is still an order of magnitude faster than a manufacturer). Manufacturers discontinue support for perfectly decent phones, the HTC M8 being a personal favourite which will be stuck on Marshmallow with no security. Even with current phones, then the manufacturer will not provide an update before the production line moves on and makes the model obsolete.

So quite a few good reasons, but attempting to put a bullet in google led only to three or for hardware ranges and bankruptcy.
[LineageOS News & Discussion] Aamod Joshi:
Yeah, you have a point.
[LineageOS News & Discussion] iza3265008:
[MENTION=5039686]mgbotoe[/MENTION] Can you add to the Unofficial Builds list the link to the Thread for Unofficial LineageOS 14.1 builds for ha3g (SM-N900) Samsung Galaxy Note 3 by [MENTION=4925642]tincho5588[/MENTION] ?

[7.1.x|SM-N900| Unofficial LineageOS 14.1 (ha_3g)] By: [MENTION=4925642]tincho5588[/MENTION]
[LineageOS News & Discussion] Ibuprophen:
I second that... with a caveat....

As long as the information for Unofficial Builds are either from a Lineage Developer (many/most of them do release Unofficial Builds) OR if the Developers Unofficial Builds have stood the test of time with quality and support behind their releases.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

***PLZ THANK ME WITH A THUMBS UP***
[LineageOS News & Discussion] CutGlass:
I think people should also read one of my first posts https://xdaforums.com/showpost.php?p=70500946&postcount=151 in this forum and indeed this thread about security and the number of sites offering custom ROMs, when I read about CM's demise a quick google search showed a plethora of domain names similar to LineageOS pushing ROMs from unknown sources with one can only guess. The owners of these domains were hidden behind privacy, though it may just have been an advertising revenue opportunity, (best case scenario).

Blu (massively discounted chinese handset manufacturer) and LeNovo both had malware found on the production line firmware in November 2016 (unfortunately Amazon gave Blu a very large sales push on Black Friday deals, there has never been any comment on how many infected handsets were released or whether OTA's removed the problem). Original link to an article here: https://www.theregister.co.uk/2016/11/15/android_phoning_home_to_china/ arstechnica included samsung devices about ten days ago https://arstechnica.co.uk/security/...lware-targets-android-users-of-two-companies/ so it's an ongoing issue.

Criminals with compilers that is the world we live in.
[LineageOS News & Discussion] theandroidguy:
In short the AIM of lineage is to provide users with a lightweight but feature rich rom nd creating an environment for a developer where he can do anything with his rom like integrating something new or removing something from the rom etc...

And the most imp thing is to revive old devices which do not get further updates from OEMs. I use lineage on my desire 816 nd installed 7.1 rr rom on my sister's galaxy s duos 2 which came installed with jellybean
[LineageOS News & Discussion] Cradelit:
[MENTION=5039686]mgbotoe[/MENTION] apologies if this information is already here. I wasn't able to locate it this thread.

I have been using this build by [MENTION=2107489]bryan2894[/MENTION] as my daily os on SGH-T989 (samsung galaxy SIIX) for a couple weeks and had only minor issues. The newest one (lineage-14.1-20170314-UNOFFICIAL-celox.zip) seems to have fixed the web view problems as well. It requires repartitioning using a custom twrp that is also included in the thread below

https://xdaforums.com/galaxy-s2-tmobile/development/rom-cyanogenmod-14-0-celox-t3470659
[LineageOS News & Discussion] takertx:
I can't get past Samsung Logo

[/COLOR]

Hey man,

You sure thing thing really works!? I flash it onto my Galaxy S4 I9500 but the phone can't seem to get past the Samsung logo. After that I have a black screen which will eventually take me into the TWRP recovery!

Any help is much appreciated.
[LineageOS News & Discussion] sunilpaulmathew:
[MENTION=5039686]mgbotoe[/MENTION]

Just released ;)

https://xdaforums.com/galaxy-s4/i9500-orig-develop/rom-lineageos-14-1-samsung-galaxy-s4-t3586561
[LineageOS News & Discussion] Magneto2528:
Can I install ressurection remix over lineage os without losing data and apps??
[LineageOS News & Discussion] sunilpaulmathew:
You can dirty flash RR over Lineage OS. After flashing, just wipe cache/ dalvik cache (don't wipe anything else). Mostly it will work... Remember to backup everything before trying...
[LineageOS News & Discussion] Magneto2528:
Bro which is better?? Ressurection remix or lineage os?
[LineageOS News & Discussion] sunilpaulmathew:
Both are really nice in different ways... and it largely depends on the user... If you like a simple, clean and smooth interface, I recommend Lineage... If you want extreme customization, go with RR.
[LineageOS News & Discussion] Magneto2528:
Thanks bro :)
[LineageOS News & Discussion] Magneto2528:
Where i can get the official themes of ressurection remix?
[LineageOS News & Discussion] CutGlass:
Possibly it would be better to ask in the RR section of the forum? :confused: Sorry i've no idea.
[LineageOS News & Discussion] baljeets97:
Please release LOs for redmi note 4 snapdragon also
[LineageOS News & Discussion] Mort015:
LineageOS is very good and Stable on my Galaxy S5. But i had problems with flashing. It says always Error:7. Then i have tried to bypass my Model number because i modified that to watcg YT in 1080p. But not helped. then i first flashed CM13.1 and then i dirty flashed successfully LineageOS 14.1. later it succes a clean install of LineageOS. Good ROM!
[LineageOS News & Discussion] Mort015:
What about SystemUI tuner?