yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] kino13:
Offtopic and my personal opinion. It's not that I don't care about the information in the phone, but as I understood the first time I read about the implementation it was a battery hog, and made the whole phone slower. I am not trading usability for security in this case. My phone never leaves my side, and if at some point someone tries to take it from me I will just smash it on the floor. That's my last point of security.

Similar to the whole "use external sdcard as internal space", really? I have to give up my internal storage to be able to use the sdcard? no way.

Regards

(Maybe things have improved since I read about it...)
[G4 Android Development] kessaras:
Indeed things improved since then. Camera is working, encryption is partially working and the problem with sdcard that was caused from when we got the update to 7.1.1 is now fixed.

Day after day nougat is getting better. Let's not talk about the same things everyday. Eventually everything will be fixed. Besides don't forget that all these are open source. People who work on these they usually do it in their free time. They don't get paid from these. We should support them a little.
[G4 Android Development] kino13:
:D You misunderstood, I am a very happy LAOS daily user, I meant for the way encryption is used and the impact it has on battery and performance.
[G4 Android Development] kessaras:
rephrase :) we don't even know if it has any impact or bugs lately ! truth is that people are scared to try it after those bugs recently ! i don't blame them. who would want to use kdz restore method .... me i'm not even on windows, i have to install a virtual machine before i do that
[G4 Android Development] goorek:
It does not have impact on battery or performance, it's implemented in hardware.
[G4 Android Development] kino13:
I will take your word for it. First time I read about it I had a Nexus 4, and of course in old phones it is CPU based, I never took the time to check what implementation the G4 had.

Regards
[G4 Android Development] :
I agree, we should support the developers who spent their free time to provide us alternative custom roms. I do personally donate regularly to open source projects I use daily (tipee, mozilla, f-droid, ...).

For Nougat I guess we have to wait for LG to release the 7.1 stock rom to get encryption working. Till then I am happy I can use MM on my G4 :)
[G4 Android Development] romgnascher:
I just installed the latest nightly, and can confirm that the camera is definitely not 100% yet.

Photos are fine, but the first time I went to video, the app crashed. After reloading, the video camera loaded fine, but still had the 1s video bug.
[G4 Android Development] raptorddd:
i havent use this rom but i have followed and i know that if you use other camera app that allows you to use API2 then it works fine.
[G4 Android Development] romgnascher:
That's correct. I use open camera, and it's fine. I was just referring to the ROM's stock camera.

However [MENTION=5461026]kesseras[/MENTION] was saying the ROM's camera was working, but that's not correct. Only 50%.
[G4 Android Development] raptorddd:
in a way yes.. cause it is.. if it didnt then it wouldnt matter what camera you use.. :good:
[G4 Android Development] romgnascher:
That's like buying a car, and the dealer says, "yeah, the radio works, you just need to install another one".

When you say "the camera works" on a ROM, you are typically referring to the camera app provided with the ROM.

To say "the camera works" on this ROM right now is misleading, unless you follow that up with "as long as you install another camera app because the stock one won't record video".

I'm a software developer myself. I don't do Android dev work (or really any Java in many years anyway) or I'd definitely throw my hat in the ring and dig into it. However, if I were to tell my boss that "the camera works" and he tested and found only 50% of the camera worked ... I'd be looking for a new job.
[G4 Android Development] kessaras:
haha, exactly. and thank you for letting me know that it doesn't work. there was actually a fix that was shared to us only in one build and propably it's not implemented yet. i didn't know for sure , but now i know :D
[G4 Android Development] romgnascher:
Cool, nice to know a fix is on the horizon. That's really the only thing keeping me from declaring it 100% functional for my purposes. Open Camera is filling the void nicely though so really no complaints.

Big shoutout to [MENTION=5776465]genesixxbf3[/MENTION] for his hard work and dedication to bringing this ROM to us. I for one know what it takes to turn out quality software ... it's not easy and takes far longer than people think.
[G4 Android Development] kessaras:
test footej camera too in the meantime. its api2 by default so its working and has better interface and its a less battery killer
[G4 Android Development] codeworkx:
you can switch to camera api 2 in settings. then it works 95%. ;)
[G4 Android Development] thewild:
I haven't found this option in settings. Is it only available in the latest nightly ?
[G4 Android Development] romgnascher:
I didn't find this setting. Is it hidden somewhere, or only in a "privileged" build?
[G4 Android Development] midzan21:
Hello, sorry for stupid question but I can't find it - IR Blaster works? I'm just asking before doing anything to friends phone (got him unlocked bootloader, twrp and root ) and mine (when I get it soon, price tag ~250-300€ now depends on few things)

Thanks in advance :)
[G4 Android Development] Manuel Marta:
I have this issue on all the aosp roms i've tried when i reboot (restart) the phone and then i wait until screen goes off then when i double tap the screen to turn the screen back on it seems like it doesn't go fully on i got a dim screen then pressing the power button fixes the issue it only happens when i use DT2W the screen has anyone had this issue or what am i missing it's annoying please help!! i really wanna use aosp based rom :(
[G4 Android Development] kessaras:
What's your dpi?
[G4 Android Development] Manuel Marta:
560 why?
[G4 Android Development] kessaras:
i have the same problem but only when i change dpi. on 560 i don't have it.
[G4 Android Development] Manuel Marta:
i have it on 560 dpi as well :c any solutions?
[G4 Android Development] Surly33:
Is anyone else getting a file size discrepancy when downloading? Latest nightly is listed at 525.1 MB, but is downloading with a file size of 501 MB. Tried on a couple of devices with the same result. Some quick help would be greatly appreciated, as I am coming off of the dead lock screen (forgot to turn it off prior to flashing). Also, appears to be multiple files
[G4 Android Development] Nachttier73:
501 MB is right, server is doing some miscalculation...

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] XeniX_Force:
I also have this problem. It appears rarely. Thought it was hardware problem

idk my DPI
[G4 Android Development] DragonautMk:
I'm in 10/01/2017 , i'm the only with a bug that doesn't show calling hud and volume hud?
[G4 Android Development] Nachttier73:
I created a quick query to view all merged commits (except kernel and binary; did i miss something?) for our G4:

Review LineageOS LG G4
[G4 Android Development] knzor:
nice, that's helpful. wouldn't be better to separate h811 and h815?
[G4 Android Development] Zemagiko:
so everything is perfect with this rom but i have a problem everytime i try to take a pic with the flash on the phone turn off and i have to pull out and put back the battery to restart it... so any idea how to fix it ?
[G4 Android Development] gioyann:
Same problem since the first time I turned on the phone on stock OS
[G4 Android Development] steadfasterX:
You mix things here and things have changed. Encryption in the past was a real mess because the hardware was slow and we had no hardware support for encryption. Both has changed in the last years. Either you have fast hardware or hardware based encryption or even both.. Nevertheless performance loss and battery drain are something for the past. I use always encryption also in the past where it slowed down things because I'm aware what can happen if you loose your phone.

Tbh when we talk about encryption in custom ROMs many are NOT using hardware based encryption because they don't care about it. Even if the device would support it. But that's another story.

Then the fact that you wanna smash your phone on the floor which should protect your data. I mean really? It will help just nothing, really nothing to protect your data.

Encryption makes sense. Always and for everyone. But many ppl don't care as they don't care about their data on Facebook, Instagram etc.

They all will wake up some day. Sooner or later. Mark my words ;)

The last thing I wanna add is that you don't need to use your sdcard as internal storage. You CAN if you want to EXTEND your internal storage. That's optional and a feature you may or may not want to use. If you choose to not use the sdcard as internal storage it can be used as usual.

Jm5c.
[G4 Android Development] kino13:
Thanks for clarifying some points. The smash in the floor is in the situation someone tries to steal it from me. No phone, and no easy change to break into my accounts.

Obviously I was expecting things to be better, as I said I only checked when encryption was starting to be implemented. Didn't know that custom roms didn't bother with hardware support.

And for the SDCard, again last time I checked (for Lollipop), you had to give up the internal space, it was either one or the other (or use the sdcard as a normal sdcard as we had been doing).

Regards :highfive:
[G4 Android Development] steadfasterX:
That's what I meant it IS still easy to get your accounts even the phone is broken.. At least when it is not encrypted.. :cool:
[G4 Android Development] XeniX_Force:
Ik its out of topic but just a simple question. when will your beta recovery be official?
[G4 Android Development] steadfasterX:
Haha.. Well tbh just hadn't had the time to push it upstream yet.. ;)
[G4 Android Development] Freddyfre:
Not Found

The requested URL /genesixx/LineageOS/h815/ was not found on this server. :(
[G4 Android Development] sejmand:
http://eu.host.erwanleboucher.fr/genesixx/LineageOS/h815/
[G4 Android Development] Freddyfre:
THX

changed link fr to eu :rolleyes:

We hope soon to receive official updates from LineageOS
[G4 Android Development] gioyann:
So then, it's enough to clear only data and caches to flash this ROM, if coming from CM 14.1? :)
[G4 Android Development] knzor:
I dirty flashed cleaning nothing since CM 14.1 was out. YMMV.
[G4 Android Development] satbir7:
How's the battery holding up for you guys?

Mine is not doing good....
[G4 Android Development] DragonautMk:
Same
[G4 Android Development] mis2417:
more or less (a bit less actually) than cm13 here
[G4 Android Development] satbir7:
Thanks guys... So, it's not just me...

I even clean flashed, without wiping internal memory, no change...
[G4 Android Development] PhrostB:
Just wanted to mention that official weekly is coming soon.

https://review.lineageos.org/#/c/155809/57/lineage-build-targets

https://review.lineageos.org/#/c/155809/
[G4 Android Development] theslam08:
You're not alone, I have that problem on every non-stock ROM too.

I also love the DT2W and I think that was always the culprit but no one been able to fix it. Pretty certain it was around during cm13 as well.

I always run the default dpi that comes with the ROM so don't think that's the issue. I really have to see if I can get a log of it because it is crazy annoying when it happens.. [MENTION=7872492]Manuel Marta[/MENTION] see if you could get one when it happens
[G4 Android Development] kessaras:
get used to that bug or use another lockscreen. on another lockscreen it doesn't happen. has something to do with the overlay and it needs so much time to detect it and fix it that i don't think anyone will ever try to fix it

~EDIT:

also i don't think the whole lockscreen overlay will change because of incompatibility with just one or two phones. this bug i've never seen it on any other of my phones at least
[G4 Android Development] XeniX_Force:
Well im having great battery life.

Im using llama kernel and init.d scripts from [MENTION=5461026]kessaras[/MENTION] for llama.

The 90less script gives you awesome battery
[G4 Android Development] tommihut:
Where can I find those scripts?

Lähetetty minun LG-H815 laitteesta Tapatalkilla
[G4 Android Development] kessaras:
yeah , they help a little. They can't perform miracles. It's the best i can do
[G4 Android Development] mis2417:
https://xdaforums.com/g4/general/llama-sweet-kernel-tweaks-t3515753

from what I see it's mostly performace limiters (and hostname setter???), so I'd rather stick to original kernel and setting the battery performance, but thanks for the tips
[G4 Android Development] sejmand:
I also got this bug. Only from time to time but it doesn't bother me...
[G4 Android Development] ew:
Apologies if I am out of place asking the following on this thread.

I found some builds for the H811 on https://www.androidfilehost.com/?w=files&flid=126235&sort_by=date&sort_dir=DESC

Has anybody tried those builds?

I noticed that the file size is larger than the files on the ftp site maintained by the OP (http://eu.host.erwanleboucher.fr/genesixx/LineageOS/h811/)
[G4 Android Development] gibbsnich:
I'd go with OP's builds: they're "pretty much" official. Who knows what those extra bits are ;)
[G4 Android Development] mis2417:
i have a weird issue to report.

since CM14.1 days (and of course in LineageOS too) captive portal login has wrong UID.

Let me explain. While connecting to WiFi captive portal *thing* is used to determine internet access. in CM13 this was handled by CaptivePortalLogin process with UID 10039 in CM14.1/LOS UID 1000 is used instead, which of course is called system/settings/quickcircle/flipflap/whatever.

Is this a bug or a feature and if so is it possible to separate CaptivePortalLogin?
[G4 Android Development] romgnascher:
One app that doesn't work...

Overall my experience with this ROM has been outstanding. However, I have one app (which I really kinda need) that doesn't seem to play nice.

The app is MBTA mTicket. The app worked fine on this phone before using this ROM. The app worked fun under CM13 on a different phone (never tried CM13 on this phone). A co-worker has a Nexus 6 running 7.1.1 and the app works fine on his phone ... suggesting there's something specific to this phone/ROM combination.

I've tried looking at log information using a few different log viewers, but I admit I'm far from an expert at debugging Android.

Reproducing the issue does not expose any personal info, so if someone could confirm the issue on their own phones I'd be much obliged.

To reproduce:

1. Install/open the app.

2. Click "Buy Ticket"

3. Choose an "Origin" station (doesn't matter which)

4. Choose a "Destination" station (again ... doesn't matter which)

5. At this point, you should see a "loading" indicator and the app should be unresponsive. If you are able to continue to the stage where you'd enter payment information, the issue is not reproducible on your phone. If that's the case, then the issue is in my own phone somewhere that I'll need to identify ... but since this is really the only misbehaving app I have, I'd be surprised.

I'm happy to provide further information in the form of logs, etc... but I'll need a little guidance to get what you need as my own attempts at reading the logs have provided very little info...
[G4 Android Development] billyx1:
What is the quality of the camera? Is it on the same level than the stock one?
[G4 Android Development] ew:
I thought I would try the new build as an experiment (and noticed that there were some more recent builds available). Flashed with no issues, and I didn't notice any more bloat or apps in the bigger build. Perhaps the zip compression is less - I really have no explanation for the difference is size of the builds. The newest build does have what must be the Lineage boot animation - and I happen to like it. Very minimalist...

I just thought I would report my findings.
[G4 Android Development] wadken1:
Latest Builds

[MENTION=5776465]genesixxbf3[/MENTION]. I'm not trying to complain, just want to be sure I haven't missed something. The latest build on you linked download page is 01/15/17. Are they on hold just now or moved perhaps?? Cheers
[G4 Android Development] genesixxbf3:
I have issues with sending the build via ftp

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[G4 Android Development] thewild:
Hi [MENTION=5776465]genesixxbf3[/MENTION], what's up with gello ? It's not on the LineageOS 13 build that I installed.

Should I just update to a newer one, or is it something that still needs to be transferred from CM ?

Edit : sorry, wrong thread.
[G4 Android Development] wadken1:
OK thanks for the update and, as always, many thanks indeed for this great ROM.
[G4 Android Development] holunder:
Wipe necessary for official builds?

Hey, will I be able to upgrade [MENTION=5776465]genesixxbf3[/MENTION]'s unofficial builds to the official builds without wiping? I read somewhere different signatures prevent this but there are some devs working on a solution directly in LineageOS that would reassign the keys to the official ones. Can I trust in this functionality?
[G4 Android Development] Velcorn:
At the risk of making myself look dumb, but I prefer dropping a short question: I'm currently still running CM12.1, what would be the best, and safest way to upgrade to CM 14.1/LinageOS 14.1?
[G4 Android Development] utefan42:
I have a similiar question to the one above. If I am currently running Rresurrection Remix do I need to roll back to stock or can I just flash this one over it? Also, what is the difference between this rom and the new Lineage OS roms? What is best if I still want to be able to use themes, but also want Android Pay back? is that possible?
[G4 Android Development] vmartinez39:
As long as the firmware has been updated first, you cam go to CM 14.1/LineageOS. I recall that you need to flash the latest firmware from LG G4 stock variant you have. You'll have to either flash it LG UP kdz, and then install TWRP again.

You can try making an Nandroid first and saving your internal SD card before experimenting. Try going from CM 12.1 -> CM 13. Then go from CM 13 -> Lineage OS. I know for a fact you can go from CM 13 to Lineage without wiping. I've done that enough times for it to work.

Also brings me to the question I came to ask, using the Latest TWRP, is restoring Nougat/CM14/Lineage backups safe? I noticed that on OnePlus 2, ever since CM14/Lineage, whenever I restore a backup it's not 100% and stuff and settings are missing. SMS definitely is corrupted, common settings just aren't restored and all kinds of unknown issues just are there. Can anyone else confirm this to be true on LG G4? I'm trying to remember because I had my phone repaired and when I got it back I had to go to a CM13 backup, then upgrade to Lineage but I've not tried doing any backup and restores of TWRP since I had a bad experience with it on my OnePlus 2.

twrp-3.0.2-0-h811.img

Anyone please confirm.

Thanks
[G4 Android Development] Velcorn:
Thanks for the answer. I was thinking of flashing either the full 20D stock rom or simply flashing the bootloader + modem through TWRP and then flashing Lineage. I guess I can just make a backup and try :P
[G4 Android Development] troullis2004:
On the latest build, under developer options, I don't have the adb and apps option for root. How can I enable root? Thank you.
[G4 Android Development] Freddyfre:
Also here only abd no root app, solution?
[G4 Android Development] troullis2004:
I fixed it by flashing supersu beta version.
[G4 Android Development] gbok:
20-1 nightly same problem with root access for apps.

Is supersu now compatable with this rom?

Maybe wait till next nightly, hopefully with solution?

Advice anyone?
[G4 Android Development] Freddyfre:
Update today with:

lineage-14.1-20170121-UNOFFICIAL-h815.zip

505.49MB

2017-01-21 07:14:49

Root not works :crying:
[G4 Android Development] :
Source: http://lineageos.org/Update-and-Build-Prep/
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
Next (todays) Nightly is already available, but no root.

Maybe [MENTION=5776465]genesixxbf3[/MENTION] or [MENTION=3208754]codeworkx[/MENTION] could advise if it is plan of lineage to have no built-in root anymore and we could use SuperSu now or if it is only temporary and built-in root will come back later?
[G4 Android Development] genesixxbf3:
No

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[G4 Android Development] troullis2004:
No problems with supersu latest Experimental zip. Not the problems with telephony and no sim.
[G4 Android Development] thewild:
Actually that's excellent news for people who need safetynet or things like that.
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
https://lineageos.org/Update-and-Build-Prep/
[G4 Android Development] Piemo:
Hi there,

I'm yet on slim80 "stock LG" ROM. But I'm suddenly missing the good old time of a pure CM (?!) ROM. Is it worth to go through there and leave LG UI?

Just a couple of questions:

-How goods are camera driver?

-Battery?

I'm afraid of leaving back xPosed to go on N. Is there that much difference between M and N to make it useful? I'm very unsure (and lazy to make nandroid)

Inviato dal mio LG-H815 utilizzando Tapatalk
[G4 Android Development] codeworkx:
Official builds will be shipped without root.
[G4 Android Development] Jirrick:
Live Display

Hi, does the Live Display works in latest nightlies?

I'm currently on older CM nightly where the feature is broken, but can be substituted by f.lux, which unfortunately needs root.

As this is the only daily use of root for me, i really consider the no pre-root way of Lianage as good idea, but the night-time red shift is essential feature for my eyes.

Thank you for answer.
[G4 Android Development] sejmand:
What is now the best way to gain root again?

Just flash superuser by chainfire? And if, which one?
[G4 Android Development] gbok:
Latest beta supersu seems to work fine. Titanium etc working again:D
[G4 Android Development] xrad:
First off, always make a nandroid. Doesn't cost much, leave it sitting around on your ext sd just in case.

Battery life is very good, camera is decent but no match for the stock camera in terms of quality and UI. I suggest making a nandroid and try it. If it's not for you, restore the nandroid.
[G4 Android Development] Piemo:
Well, thinking of how good stock camera is, it's a pity to lose it. But in fact it seems that everyone is saying that AOSP ROM are an improvement of the phone, but can't understand if it's something just to be "better" or if it's for real

Inviato dal mio LG-H815 utilizzando Tapatalk
[G4 Android Development] Freddyfre:
Latest(V2.79):

Recovery Flashable.zip MD5:f4ecbf5814215bf569ff3324fc1c91f5

http://www.supersu.com/download
[G4 Android Development] holunder:
Live Display

It works now (tested on a Nexus 5 with recent Lineage) but you will have to switch it manually off in the system settings, I couldn't find the system widget for the pull down menu (or just set it to automatically).

I want to repeat my question: Will a wipe be necessary for the switch to official builds?
[G4 Android Development] Jirrick:
Thank you, will give it a try myself.

For your question see http://lineageos.org/Update-and-Build-Prep/ I'm personally going to do full wipe and clean flash.
[G4 Android Development] tachiquan3:
Sorry for the off topic. I just wanna know if you're still going to continue llama kernel?
[G4 Android Development] welder73:
You don't have to leave anything,just flash another rom on data slot with Dual Boot Patcher...

I use two roms for a long time ;)
[G4 Android Development] brossovitch:
Didn't the blog post say LineageOS will no linger come with prebuilt root? So, flash Superuser App of your choice.