yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Mike2040:
Hi,

I have a few questions:

1. New builds are released almost each day, any differences, how to know, they all seems the same, size too........How does one find the changes/change log Or how often should one reflash the new released build?

2. When do you plan to induct the theme engine?

3. Why do icons of visited site not show up in Chrome history, is that done by you, since they do appear in CM 14.1 Nightly?

4. Camera app, while taking pics of devices like TV or pc shows waves, how to remove them to not appear?

5. Can it be rooted, shall the root remain after flashing the new build.....link for SU for this ROM?

6. Do you recommend installing Greenify on this ROM?

7. Am testing it as a daily driver, approx how much should be the SOT on this N ROM? Flashed as a clean install and factory reset, not running as a MultiROM.

Thanks.

PS: Kindly PM regarding donation.

---------- Post added at 07:51 PM ---------- Previous post was at 07:42 PM ----------

Never showed on picking the phone.

Displays a dull display on receiving a text, email etc.

---------- Post added at 08:30 PM ---------- Previous post was at 07:51 PM ----------

Won't appear, am on Jan 15 build?

Thanks.
[ONE Android Development] giaur:
Actually no changes between builds. This is because there are no commits for our device. There is also no any simple way to see changelog filtered for opo, here you have all devices: http://cmxlog.com
[ONE Android Development] Mike2040:
So how often should a lay person flash a new build?

Thanks.
[ONE Android Development] J_E_F_F:
Just because there are no changes "specific" to our device, that does not mean there aren't changes throughout to things common to all devices.

There are changes to these common items pretty much daily.

As an example the monthly security updates, snap camera, etc. All have changes but not specific to the OPO.

Flash at least monthly once the security updates are rolled in, then maybe every 2 weeks or weekly at most.
[ONE Android Development] thedamager:
There are changes to common packages. You are probably only looking at android_device_oneplus_bacon and android_kernel_oneplus_msm8974.
[ONE Android Development] giaur:
No, I looked at all merged commits. There are many commits for various devices (not for opo) and their kernels. However, nothing or almost nothing in common packages so far. One thing proves no changes - first boot after upgrade is usually as fast as nomal boot. This means actually (almost) the same has been flashed. No need to optimize any apps at boot

For example, comparing yesterday and today build: no any single commit merged for device oneplus, kernel oneplus and any common package. So actually yesterday build is equal today build.

I also can't see any new commit merged today. Only commits for other deviced and no commits for common packages. So tommorow build will be the same as today one. Really, I see no reason to keep building it everyday.
[ONE Android Development] thedamager:
I find "nothing" and "almost nothing" to be fairly different, but to each their own. From what I found, there are more than 40 changes to common stuff in the last 6 days.

With regards to everyday building, many people have automated setups, but if you're doing it by hand, you're right, there's no need to...
[ONE Android Development] giaur:
Show me any MERGED change for opo in last 2 days. Opo specific or any common package. Well, 2 small kernel changes that affect nothing and some BT code cleanup. No changed since yesterday.
[ONE Android Development] thedamager:
https://review.lineageos.org/#/c/154019
[ONE Android Development] J_E_F_F:
No it doesn't, all that means is you didn't flash properly and wipe the caches like you are suppose to.
[ONE Android Development] giaur:
Wipe caches? On every update? What for? :eek:
[ONE Android Development] J_E_F_F:
it's the accepted practice due to all the little changes, the proper way to flash nightlies. It's why it is on the TWRP screen immediately following a flash.

This explains why http://android.stackexchange.com/questions/25859/why-do-i-need-to-wipe-dalvik-cache

Probably why people have little issues and force closures here and there.
[ONE Android Development] Programming4life:
Can you guys please create a new thread and talk about this there thanks :)

My opinion.

Should I flash everyday? Your choice. Flash a new build whenever you want. I my self used to flash cm-14.1 weekly. The builds that I post currently I usually flash my self first before uploading it just in case its a bad build.

Is there always a new commit/change everyday? Yes, believe it or not there is a new commit almost everyday. The commit maynot be a big bug fix/feature, but there's usually a commit each day. Android is VERY large with many small git repos coming together to make android. You can find the list of all "base" android repos that make up android here https://github.com/LineageOS/android/blob/cm-14.1/default.xml There are also more repos that are not llisted at the url.
[ONE Android Development] giaur:
Well, actually all you need is to apply update, absolutely no need to wipe anything, updater script will do all needed operations for you. You even can't perform any wipe, because cmupdater restarts phone immediately aftery applying update.

(sorry for offtopic).
[ONE Android Development] eagledipesh:
Hello, I edited build.prop to enable volte and WiFi calling, now I can enable WiFi calling from settings but I am not sure if it really works. How can I check??

Edit :build.prop

#ifdef VENDOR_EDIT

persist.dbg.ims_volte_enable=1

persist.dbg.volte_avail_ovr=1

persist.dbg.vt_avail_ovr=1

persist.data.iwlan.enable=true

persist.dbg.wfc_avail_ovr=1

#endif
[ONE Android Development] giaur:
I think it won't work, you need rom branded by your operator. This is how it works in my country at least
[ONE Android Development] eagledipesh:
I have oneplus 2 and in that volte is enabled...After Updating to latest firmware provided by opo team. It's not branded by the operator.
[ONE Android Development] giaur:
OxygenOS is closed source, maybe they managed to add support for your operator. I would not count ony anything similar on LineAge
[ONE Android Development] Link_of_Hyrule:
Heads up unless the ROM is compiled with settings other than default, su is now disabled by default and requires you to flash it as an add-on. I'm not sure if the official add-on is released yet. I already use the su magisk flashes and that works fine imo. Personally, I'm in favor of this change since it means a lot closer to stock experience out of the box. Those that need root can easily flash it and wth the official add-on it'll survive between updates.

https://review.lineageos.org/#/c/154019
[ONE Android Development] Ficusretusa:
Same for me from a week, approx.

Do you have solved?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] giaur:
Can anybody confirm root is missing now? If so, I need to hold on and don't update. [MENTION=5341763]Programming4life[/MENTION] - do you plan to compile with root support?
[ONE Android Development] Link_of_Hyrule:
It won't be until the next build.
[ONE Android Development] giaur:
Ok, this is why I'm asking if [MENTION=5341763]Programming4life[/MENTION] is planning to use option to enable root or not, in his future builds
[ONE Android Development] Link_of_Hyrule:
I imagine it won't be much longer for the official builds to kick in. It's unlikely they'll revert a change to an unreleased project when no one should be using it anyways technically.

There are many open source su options you can use that don't cause boot loops that are tried and tested by thousands of people. Nightly builds themselves cause boot loops occasionally 99% of the time you can just clear your cache the other 1% you can simply revert to the last build until the next one.

If you're afraid of third parties having root access you can read the source code if not you probably shouldn't be using unofficial third party software and should stick to your OEMs stock updates.

We're all excited and want the official Lineage OS to be out and I'm sure it will be within the next month or two so we just have to be patient [emoji106]
[ONE Android Development] hallo dare:
Would be nice to see xposed come out at the same time.
[ONE Android Development] giaur:
Well, in any case, I'm waiting for confirmation about next builds here - once somebody flash build made after that commit, please confirm is built in su still there or not. Or op please confirm ?
[ONE Android Development] tk8lm6:
Wait ... Is built-in in root being deprecated? I still have the option under developer options and it looks like one of my apps that requires root stopped working normally but others seem to get root just fine.

I'm sorry ... Maybe I'm thick, but I have been unable to get clear on this vague talk about "root going away on unofficial build" or whatever. I had using third party root apps when the built in root works so well and simply.

Tk8lm6
[ONE Android Development] giaur:
Built in root has been removed. Next build (?) will contain commit that removes built in root. To get built in root available as before, you need non standard build. I hope [MENTION=5341763]Programming4life[/MENTION] 's builds are going to have built in root, if not I will start to flash only my own builds.

I would not call it deprecated... they just decided to remove it.
[ONE Android Development] tk8lm6:
Well isn't that just ducky. I always have rough times with 3rd party root apps. Well ... At least SuperSU. I don't get it ... Having built in root is one of my best reasons for when using a custom ROM. So convenient and trouble free. I was a chainfire SuperSU paid user for a long time but something would always go sideways.

So after tomorrow's nightly no more built in root option? Makes no sense to me but what do I know. :(

Tk8lm6
[ONE Android Development] giaur:
I have no idea, it depends how it will be built.
[ONE Android Development] detted:
yes for the built-in root. no need and not interested in an extra app like SU.
[ONE Android Development] Link_of_Hyrule:
It'll be exactly the same as it is now except you'll have to flash a zip once and after the it'll survive updates.
[ONE Android Development] haimn:
According to the commit message:

I build the rom from the source code for myself from time to time, so if [MENTION=5341763]Programming4life[/MENTION] don't want to include the root, I'll upload a build with root when I'll build it for myself. (every 3-4 days).
[ONE Android Development] libove:
I just installed Programming4life's LineageOS unofficial nightly 14.1-20170116 for bacon on my OnePlus One, along with SuperSU 2.79, and all is well.

Many thanks.
[ONE Android Development] Mike2040:
I personally feel root should be an option, not included. Some may not want to root. Like official COS.

Benefits of a root, besides Xposed, Adaway?

More effort should be spent on improving cam app, battery, WI-FI data reset bug, improve font quality, COS like theme engine...

I feel its the best, most stable bug free N ROM for OPO.

Like posted some where, maybe Lineage comes out with a official N for OPO in a couple of months.
[ONE Android Development] Programming4life:
What ever lineage does goes. I'm just a build server not trying to create a rom or something so what ever commits lineage merges gets included in the builds.

If you want root you can just flash super su not a big deal.
[ONE Android Development] alleykat2561:
I'm on the build dated the 16th and still have cm-su, at least according to titanium backup...
[ONE Android Development] giaur:
You don't need to create rom. Lineage has leaved choice if you want built in su or not, by defining WITH_SU env variable . Your choice is to build without root, which is default now. Well, I will keep flashing my own builds then. Thanks for clarification.
[ONE Android Development] Mike2040:
Does the font and display size affect battery drain?

I keep Font at default and Display at smaller.

My OPO's are 2 .5 yrs old, though CPU-Z displays battery heallth as Good, should I get it replaced?

Any suggestions please.

Thanks.

Edit:

Or before replacing, I should perform a factory reset, and 3 cycles.

Cause on COS 13.1.2, it didn't drain as quick. On that it would last 24 hrs plus, on this I have to charge at times twice in a day?

Any other ways to check battery health, they day Li-on battery life decreases by 30% after 2 years.....is that correct?
[ONE Android Development] giaur:
My build is in progress now, we'll see how will it work.
[ONE Android Development] J_E_F_F:
build 20170117 from the OP still has default built-in root, just installed and tested.
[ONE Android Development] giaur:
Damn... again Gello problem? My build fails with error message:

[ 0% 121/16543] Download: /home/michal/lineage_build/out/target/common/obj/APPS/Gello_intermediates/org.cyanogenmod.gello-40.apk
FAILED: /bin/bash -c "(mvn -q org.apache.maven.plugins:maven-dependency-plugin:2.10:get	org.apache.maven.plugins:maven-dependency-plugin:2.10:copy	-DremoteRepositories=central::::https://maven.cyanogenmod.org/artifactory/gello_prebuilds	-Dartifact=org.cyanogenmod:gello:40:apk	-Dmdep.prependGroupId=true	-Dmdep.overWriteSnapshots=true	-Dmdep.overWriteReleases=true	-Dtransitive=false	-DoutputDirectory=/home/michal/lineage_build/out/target/common/obj/APPS/Gello_intermediates/ )"
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:get (default-cli) on project standalone-pom: Couldn't download artifact: Could not transfer artifact org.cyanogenmod:gello:apk:40 from/to central (https://maven.cyanogenmod.org/artifactory/gello_prebuilds): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[ERROR] org.cyanogenmod:gello:apk:40
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false),
[ERROR] central (https://maven.cyanogenmod.org/artifactory/gello_prebuilds, releases=true, snapshots=true)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ONE Android Development] haimn:
My build completed successfully right now, I'm flashing it now.

This guy have the same error like you: https://xdaforums.com/showpost.php?p=69773201&postcount=770

you can ask him if he solved this.
[ONE Android Development] giaur:
I managed to import cert manually into java keystore, no more errors so far. Let's see what next...
[ONE Android Development] Pizzini:
Tomorrow's build will finally have a new boot animation.

https://review.lineageos.org/#/c/156893/

In action:

https://drive.google.com/file/d/0B6qZP1xW9VRwaVZPdE03NjIwNEk/view?usp=sharing
[ONE Android Development] makova:
I have an error in compiling today. Great job new boot animation.
[ONE Android Development] haimn:
Well, that's worth a new build, I'll update my source and build it right now!
[ONE Android Development] giaur:
Same here :)
[ONE Android Development] makova:
Hi. My source is not compile :(
[ONE Android Development] Pizzini:
If someone can compile, could you upload bootanimation.zip here? :fingers-crossed:
[ONE Android Development] haimn:
Mine on 99% now, but you can download it here: https://github.com/LineageOS/android_vendor_cm/blob/cm-14.1/bootanimation/bootanimation.tar

and it finished successfully, flushing it now.
[ONE Android Development] Pizzini:
But the . tar file has a resolution not adecuate for OPO.
[ONE Android Development] haimn:
OK, so I uploaded the bootanimation.zip here.

I upload the full rom to androidfilehost too, it's on 45% now.
[ONE Android Development] Mike2040:
Hi, [MENTION=2893695]haimm[/MENTION]n yours and [MENTION=1566226]Pizzini[/MENTION]s builds are the same or different from the ones of programming4life ones?

Thanks.
[ONE Android Development] haimn:
They are exactly the same, but [MENTION=5341763]Programming4life[/MENTION] have OTA and we aren't so I recommend you to use [MENTION=5341763]Programming4life[/MENTION]'s builds.

Here is my 20170117 build: https://www.androidfilehost.com/?fid=673368273298924545

but if you flash it you won't get [MENTION=5341763]Programming4life[/MENTION]'s OTA, so I recommend to wait until tomorrow for Programming4life's build.
[ONE Android Development] giaur:
Damn it... my build has finished, but it's not booting. It only stays in 1+ logo and then nothing happens. No boot animation, no boot. Is your buid booting?

I also noticed my build is smaller size than 15.01 one from [MENTION=5341763]Programming4life[/MENTION] -size is aporox 30 MB smaller.

---------- Post added at 10:14 PM ---------- Previous post was at 10:10 PM ----------

But his builds won't be rooted anynore
[ONE Android Development] haimn:
My build is booting and working good (and the bootanimation is beautiful!).

you can download my build from here: https://www.androidfilehost.com/?fid=673368273298924545 , but as I said, if you want [MENTION=5341763]Programming4life[/MENTION]'s OTA you might want to wait until tomorrow for his build.

BTW, I use the WITH_SU flag, so my build have root in it.
[ONE Android Development] giaur:
I must have something screwed up with my new build environment... have you used custom manifest? Your build works fine, mine does not and it's almost 50 MB smaller than yours. It's ridiculous... Tomorrow I will try to build on my home computer, which was ok previously
[ONE Android Development] haimn:
This is my manifest:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_oneplus_bacon" path="device/oneplus/bacon" remote="github" />
<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" />
<project name="LineageOS/android_kernel_oneplus_msm8974" path="kernel/oneplus/msm8974" remote="github" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="TheMuppets/proprietary_vendor_oneplus.git" path="vendor/oneplus" remote="github" />
<project name="TheMuppets/proprietary_vendor_oppo.git" path="vendor/oppo" remote="github" />

</manifest>

It's almost identical to the original, but I have added the proprietary from TheMuppets as I told in LineageOS's IRC.
[ONE Android Development] Pizzini:
I'm sorry, but I have not made any builds. Maybe in the future ...
[ONE Android Development] Mike2040:
Thanks for explaining.

But his don't have OTAs, CM updater, won't update, they have to be dirty flashed..

Thanks again!
[ONE Android Development] haimn:
Anyway, this is his thread, I don't want to take it from him / SPAM his thread.

So I'll try to answer on technical questions only.
[ONE Android Development] Mike2040:
That's fine. Shall you create you're thread?

Thanks.
[ONE Android Development] jhedfors:
I am curious - what is the hesitation to flashing root, such as the open source PHH Superuser?
[ONE Android Development] giaur:
For me, it's unnecesary bloatware and risk of problems in future lineage releases. I preffer built in su, perfectly integrated with system. Unlike any 3rd party softwate

---------- Post added at 12:13 AM ---------- Previous post was at 12:09 AM ----------

Hmm, build on my home pc (my old environment) is fine. Manifest is similar to yours, muppet included. This may be reason, I'll try to put the same manifest to my new server and see if it works.
[ONE Android Development] jhedfors:
I see. It sounds like LineageOS will be releasing a separate Superuser zip that will survive OTA updates. That should alleviate any compatibility concerns. :svetius:
[ONE Android Development] Mecca EL:
Not sure where you found this, but everything is activated on my end. Thank you!
[ONE Android Development] giaur:
Is it actually working for you?
[ONE Android Development] Mecca EL:
VoLTE, no.

I'm not near a WiFi source at the moment, to test WiFi Calling.
[ONE Android Development] SirSoviet:
It's nice to see that this thread has turned into an actual development thread.
[ONE Android Development] jester450:
You should be able to get to the option by dialing *#*#4636#*#* and then go into Phone information.

Odd - I'm on 2017-01-17 release and mine shows off.

What release are you on?
[ONE Android Development] Mecca EL:
1-17-2017 nightly, but I used the build.prop tweak to activate those features.
[ONE Android Development] giaur:
Something big is coming. All systems are operational: https://status.lineageos.org/ but https://download.lineageos.org/ is error 500 so far.
[ONE Android Development] jhedfors:
Yeah, I noticed that this morning. It is odd that the dashboard shows everything operational, but the site is down.
[ONE Android Development] giaur:
Also wiki has been removed from list.

[edit]

download is missing too on status list
[ONE Android Development] haimn:
I noticed this yesterday, I think they just removed from the list the servers the didn't create yet, so the list can show the status of existing servers and not the future servers.

I guess they will add the wiki and download server to the list when they done with them.
[ONE Android Development] bastard79:
http://wiki.lineageos.org/Build_for_bacon.html

http://wiki.lineageos.org/bacon_Install.html

wiki works :)
[ONE Android Development] haimn:
I'm happy to hear that! I used the wayback machine from Internet archive to use the old cyanogenmod wiki, I'm glad they uploaded the new site.
[ONE Android Development] giaur:
Interesting, without custom manifest I'm getting broken builds, thy haven't mentioned it on their wiki
[ONE Android Development] haimn:
They did, this is this part.

They tell you to extract the proprietary blobs from an existing system.

The custom manifest is just if you don't want extract it but download it from github.
[ONE Android Development] giaur:
It's not clear for me where to extract that blobs, I guess somehwere inside .repo folder for my build

P.S. Is it possible to include modem blobs as well?
[ONE Android Development] haimn:
It's very simple:

Just cd ~/android/system/device/oneplus/bacon and then run the script extract-files.sh, it will do all the work.
[ONE Android Development] giaur:
I guess it should be /<my-build-fodler>/android/system/device/oneplus/bacon, ~/android/ is only example path, right?
[ONE Android Development] haimn:
Yes.
[ONE Android Development] luke_c94:
What does the <20 flag symbol mean when using the camera? It's in the bottom left and only appeared when I flashed the nightly from the 14th
[ONE Android Development] lucien68:
Yes i would like to know if VoLTE is working.
[ONE Android Development] giaur:
Maybe no reason, just to look nice?
[ONE Android Development] MuMia:
Probably photo counter, shows how many shots left before phone memory will be full.
[ONE Android Development] giaur:
Counter is counter, but what the flag means?
[ONE Android Development] MuMia:
Maybe "finish" flag :)
[ONE Android Development] luke_c94:
I have 16GB of storage left so it definitely isn't, and it doesn't decrease when I take pictures. It's quite annoying as it's always sitting there in the bottom left of the viewfinder.
[ONE Android Development] giaur:
Well, your problem is really strange.
[ONE Android Development] luke_c94:
This is what it looks like:

[IMG="Camera"]http://i.imgur.com/pBJz5Zt.jpg[/IMG]
[ONE Android Development] giaur:
So there is a flag. Probably it means nothing. You are forced to live with that
[ONE Android Development] Bembee:
I also have this flag, I don't know what it means. I have enough free space, so it have no connection with the storage. Anyway, my counter works well.
[ONE Android Development] MuMia:
Try change resolution of picture and check, now I got 24gb free and 13mpix is the around 4000 photos to end, after change to 1mpix got over 53k to end.