yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] wg2000:
And something else I noticed. After installing latest unofficial from genesixx, phone started to charge really slow. I mean needing about 8 hours to go from 35% to 100%... When I reverted back to my official twrp backup, everything seemed normal but the correct pattern could not be used to unlock my phone.

I adb shell using twrp, deleted /data/system/locksettings.db* and re-set the lock screen configuration which is now back to normal. The slow charging has remained, tough. Any ideas?
[G4 Android Development] se1988:
Sounds like a HW problem. Did you try another charger/cable?
[G4 Android Development] wg2000:
Yes. And the battery is brand new, only one month old.
[G4 Android Development] se1988:
Original battery? I've had many "original" batteries (from ebay) behaving exactly like you described.
[G4 Android Development] wg2000:
Well, that particular one came directly from LG so it is genuine...
[G4 Android Development] crankidiot:
Torch is working fine, even quick settings tile. Yes, flash the newer modem and bootloader, as mentioned several times.
[G4 Android Development] Surly33:
Camera and torch not working on the 24-NOV genesixx unofficial build for the H811. On the v20 modem is there a fix for this? I cannot locate newer modem and bootloader files for the H811 after several searches.
[G4 Android Development] macart:
thanks, will check it out, hope it's for cm14, I already bricked once by flashing cm13 version to try it out on cm14. will report on results.

---------- Post added at 04:05 PM ---------- Previous post was at 03:32 PM ----------

focus is fixed now! many thanks [MENTION=5776465]genesixxbf3[/MENTION] for the fix and [MENTION=1300126]theslam08[/MENTION] for bringing it to my attention!
[G4 Android Development] ashkan-khatar:
Umm, quick and possibly dumb question, what would happen if I manually replaced all of the files and folders of the ROM with those of a rooted stock ROM on a 818P (since there's no recovery or anything)?
[G4 Android Development] Nachttier73:
Here're some logs regarding sdcard. I'va done this:

- formatted sdcard as internal storage

- reboot

- tried to move an app -> error

Hope this will help...

http://cloud.tapatalk.com/s/58121c53e3b10/2016-10-27_17.14.zip
[G4 Android Development] popy2006:
thx for the hint.

but ill think its not necessary, i have restored an /Sygic/ Folder backup i have made before i flashed cm14 and now sygic runs perfectly and also downloading of new maps to internal storage works like a charm!

pOpY
[G4 Android Development] japi2000:
Hey guys. 815 international version user here, running v20e-TWN-XX software version (stock).

I wanted to ask if there's something to consider in this device/software before installing this CM14 rom (I don't want to brick it) :)

Thanks!
[G4 Android Development] kessaras:
1. its still beta, so you will have to be patient with cm14 and do your updates.

2. forget FMradio. AOSP in LG G4 has no radio.
[G4 Android Development] japi2000:
Hi!

1. Not sure what you mean by being patient, I just asked for advice if there's anything to consider before trying this rom to avoid bricking the device :)

2. It is ok, I don't care about FM radio

Thank you
[G4 Android Development] kessaras:
The procedure is the same on all phones. If you know what to do, then there is nothing to consider.

I thought that coming from a stock LG you would be more interested to know what are the only dissadvantages and consider your decision before you actually do it.

Anyway. CM14 is beta, by being patient i mean that you have to "keep living" with the bugs and keep updating until one day they will be fixed.
[G4 Android Development] japi2000:
Alright, got it thanks!

Just wanted to be sure, as there are variants of the hardware and software, just to be safe :)

Will install it tonight and report back any issue if I find any that hasn't been reported

Thanks!
[G4 Android Development] Fenderstratocaster87:
Same problem....wipess ROM reboot and then gapps
[G4 Android Development] raptorddd:
am afraid you cannot as your variant cant have bootloader unlocked..
[G4 Android Development] Ogre77497:
Running CM14

I wanted to give you a big THANK YOU, and the Rom a big THUMBS UP. :good:

I'm having no problems with my H811 and CM14. Wifi, Bluetooth, cellular, video playback .. everything works, with the exception of the camera. I'm still having a few problems with it, but I'm using Open Camera with good results.

I've been running it with the stock kernel and with LlamaSweet. No apparent hiccups.

I was so impressed this week that I deleted my CM13 nandroid backup.
[G4 Android Development] japi2000:
What

I don't understand

If the 815 bootloader can't be unlocked, what are the 815 roms in this thread for? :eek:
[G4 Android Development] tech2pc:
Same here! Great rom!
[G4 Android Development] raptorddd:
815 from some countries from europe. Do a search on

lg g4 that can be unlocked see the list..

---------- Post added at 04:29 PM ---------- Previous post was at 04:27 PM ----------

Does everything work? Would you tell what ismt working. Tjank you
[G4 Android Development] japi2000:
Bummer

So I'm stuck w/ stock roms on this phone ?? :(
[G4 Android Development] stegalli:
In the latest builds is there still the bug using the gallery, and the bug that does not allow to write/read on the SD?
[G4 Android Development] TheLoonyRebel:
Just curious as I'm a bit behind on following CM14 has the theme engine been put in as of yet?
[G4 Android Development] kessaras:
make a thread in the help section. there is also flashfire that can help you install xposed and edit the stock the way you like it, but before that you have to be sure that there is a way to restore it with the LG software on your pc.
[G4 Android Development] phuongbkhn:
I took it to stock ROM by kdz, and then tried to flash lastest CM13 nightly, it's OK now.

p/s: with H811, I have to use v20o version, with v20i, i faced with the same issue.
[G4 Android Development] caponex:
Hi, guys. Maybe silly question but still wanted to ask whether the double tap to wake/lock works on the G4 with the LOS? I have a h815 and very keen on trying out this 14.1. Thank you
[G4 Android Development] kessaras:
its in our device tree , its a device feature and works on all roms , unless we remove it.

https://github.com/Suicide-Squirrel...orks/base/core/res/res/values/config.xml#L277
[G4 Android Development] kinuris:
Hi, can I uninstall or block cLock app? Is it only a widget or is needed for system work correctly?
[G4 Android Development] obvious:
It's just a lock screen widget. Not needed by system
[G4 Android Development] se1988:
Then RMA it. You probably got a faulty battery.
[G4 Android Development] wg2000:
Bootloop caught me! Sent it for repair, thankfully there will be no charge... which means I get a warranty extension for another 2 years for the motherboard, yae!
[G4 Android Development] se1988:
Ah, theres your problem then ;)

The phone will always act up some time before looping
[G4 Android Development] matosc:
Now that LineageOS removed H811 and H815 from the 14.1 branch due to "outstanding unfixed issues", is the LG G4 officially dead? LineageOS has been my daily driver and I was really looking forward to v15.1.

Ref: lineageos.org/Changelog-15/
[G4 Android Development] belrik:
We need a fix for encryption. Other than that it's not dead. Several unofficial builds, once those devs submit commits to the official LOS Gerrit the official builds can move forward. I'm gonna stay on the last official build for now and see if an encryption fix appears.
[G4 Android Development] codeworkx:
Where can we buy one?

Wasted some hours today on it without success.

So it will stay offline till someone fixed it.
[G4 Android Development] belrik:
Pardon, what are you buying? I read the TWRP bug regarding encryption but can't remember the details right now. I'm sure you've seen this yourself in the past. Any chance that LG will release any more sources?
[G4 Android Development] se1988:
That would be nice
[G4 Android Development] codeworkx:
Please try if encryption and lockscreen security is working:

lineage-14.1-20171211_195722-UNOFFICIAL-h815.zip
[G4 Android Development] Surly33:
I continued to have issues with the unofficial build for the H811 (crashing & no torch/camera). I switched back the official build and haven't experienced any of these issues. I am running the 20v base, which I suspect is the issue with unofficial build. How have other H811 users been running the unofficial build? Any thoughts on where I can find the most recent H811 stock base (29a or equivalent)?
[G4 Android Development] lq092009:
Rom report

If you use the nougat kernel source, you need a nougat modem to work with the lock screen and encryption.
[G4 Android Development] belrik:
---------- Post added at 04:42 AM ---------- Previous post was at 04:39 AM ----------

Nougat modem firmware required for this encryption fix?
[G4 Android Development] codeworkx:
Probably. The modem image contains keymaster firmware (kmota.*).

Can't say if it has been changed or not.
[G4 Android Development] Netsab:
Hi, I'm on 07122017 unofficial nighlty and everything (I use) works, thank you all, my phone is so nice to use i' thoses

Just a last thing disturb me, there is some thing strange with NFC. When I put my phone on NFC tags like sound bar or printers, pairing works. But when I try to use contact less payment or even Android Beam, nothing happens... Is this normal behavior atm?
[G4 Android Development] genesixxbf3:
No

but grab a logcat
[G4 Android Development] genesixxbf3:
Guess g4 is not totally dead
[G4 Android Development] Netsab:
Oups, it's sems that my "Qi charging moded" back cover was the problem.

Sorry.

Even the DRM seems to be back ! Molotov.tv works !

This is it, i've got the perfect phone ! (According to me of course)

Thank you all devs and helpers.
[G4 Android Development] JK-FINN:
For me that would be a pity, I really like this phone. Everything has been fine after replacing the bootlooping mainboard to a newer revision, under guarantee.

In Finland they replace the mainboard to a new one for free, even after guarantee is out.
[G4 Android Development] obvious:
Thanks for trying to crack it but not working yet here on H815.

Encryption appears to go well but then fails to recognise unlock pattern. TWRP 3.2 preview for custom N ROMs also failed to accept unlock pattern.
[G4 Android Development] steadfasterX:
Do you had enabled HW encryption in device tree for this?
[G4 Android Development] codeworkx:
https://github.com/LineageOS/android_device_lge_g4-common/blob/cm-14.1/board/qcom-platform.mk#L8
[G4 Android Development] steadfasterX:
I see. I would give it a try without..

I saw issues in the past when enabled so maybe worth a try..
[G4 Android Development] nullbert:
Software or hardware isssues?

I apologize in advance if any of this has been covered before but I can't seem to find anything about these issues.

Let me preface this post by saying these issues might be user-caused hardware issues, seeing as my phone got spilled apple juice on last summer. I thought I'd figure out if it's related or if they're known bugs.

The phone is my daily driver, a h815 currently on the lineage-14.1-20171207_004555-UNOFFICIAL-h815 build, but the bugs were present on the official builds and on the lineage13 builds as well.

1. When charging through USB, and pressing the power button, my screen wakes up but with no backlight. To fix this I have to press the power button twice and sometimes more to wake the phone again with backlight. I haven't tested much whether it is related to any display settings as it is quite inconsistent.

2. My cellular data connection is also very sporadic, I get the bars with the X in the corner and have to do a hard reboot to fix it. The speeds are fine, it either works or it don't.

There are some posts on this issue in the forums, but none are solved as far as I could see.

I can probably provide logs if it is of interest, I just figured I'd check with you guys whether you thought it was worth it. I am hoping to hold on to this phone a bit longer as I want my next phone to both be cheaply(-ish) priced and support Project Treble. A fix for these issues would make the wait more bearable as it seems to be at least six months away.
[G4 Android Development] se1988:
Do you get these issues on other roms?
[G4 Android Development] nullbert:
Haven't really tried other ROMs. Once the flashlight bug was squashed I figured I could live with the other two. I have cached/offline music for when I leave the house (wifi), and a do a quick reboot for the longer trips.

I just remembered I still get notifications, but loading a Snap from Snapchat takes forever. So 2G is at least partially working I guess.

I could try another ROM next week. Could be a nice little holiday project. Any suggestions as to which is the most stable? Maybe I should try stock first...
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
Happens sometimes to me, too. But couldn't find out how to reproduce.

I don't have this. Might come from your provider.
[G4 Android Development] se1988:
The stock nougat rom is pretty nice.
[G4 Android Development] zeduck:
What about encryption?

Did you test it [MENTION=5545101]steadfasterX[/MENTION]?
[G4 Android Development] codeworkx:
Makes it just worse. The flag enables qcom cryptfs_hw which is a hook into qseecom for getting and storing the keys.
[G4 Android Development] mymeatb18:
1. I believe this screen thing happens on all ROMs, not very often though

2. Never happens to me, not currently on this ROM.
[G4 Android Development] kessaras:
is this related ?

01-02 02:16:23.257 528 528 I keystore: Found keymaster1 module Keymaster QTI HAL, version 100
01-02 02:16:23.257 528 528 I SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 131: Creating device
01-02 02:16:23.257 528 528 D SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 132: Device address: 0x745543e000
01-02 02:16:23.383 653 653 E QSEECOMD: : Loading keymaste app failied
01-02 02:16:23.802 653 653 E QSEECOMD: : Loading keymaster app failied
01-02 02:16:24.066 528 528 E keymaster1_device: Keymaster loaded/ queried from Qseecomd
01-02 02:16:24.077 528 528 E keymaster1_device: TA API Major Verion: 1
01-02 02:16:24.077 528 528 E keymaster1_device: TA API Minor Verion: 0
01-02 02:16:24.077 528 528 E keymaster1_device: TA Major Verion: 1
01-02 02:16:24.077 528 528 E keymaster1_device: TA Minor Verion: 10
01-02 02:16:24.077 528 528 E keymaster1_device: set_version_req->flags: 1
01-02 02:16:24.078 528 528 D keystore: Wrapping keymaster1 module Keymaster QTI HAL with SofKeymasterDevice
01-02 02:16:24.078 528 528 D SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 178: Reinitializing SoftKeymasterDevice to use HW keymaster1
01-02 02:16:24.081 528 528 I SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 131: Creating device
01-02 02:16:24.081 528 528 D SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 132: Device address: 0x745543e400
[G4 Android Development] codeworkx:
Just says that keymaster got loaded successfully.
[G4 Android Development] kessaras:
yes. i did some "hacks" adding files from hammerhead and im gonna test tomorrow if they work too, not only load fine.
[G4 Android Development] codeworkx:
hammerhead is different platform. (msm8974 vs msm8992)

bullhead would be right but already tried to use keymaster/gatekeeper from there.
[G4 Android Development] Netsab:
So it's seems that I have a NFC problem even with original back cover. Sometimes tags work (like my sound bar Bluetooth connection), when I put back to back with some phone, I have a vibration, some times nothing happens. And I never sucess a NFC payment since I'm on 14.1 (worked fine on 13), nothing happens when I put my phone on payment terminal.

I could make a logcat if I know how to... Sorry...
[G4 Android Development] genesixxbf3:
http://lmgtfy.com/?q=how+to+logcat
[G4 Android Development] Netsab:
Ok OK, sorry, lazy me. Hope you'll find what you expect with this.
[G4 Android Development] kessaras:
[MENTION=3208754]codeworkx[/MENTION] , you still own a g4 ?

Could i share my Oreo device tree, kernel and blobs and ask for some help ?

i booted but i try make it stable
[G4 Android Development] codeworkx:
Currently not. My old i9300 died recently so i gave the g4 to my family.

Booting oreo is like 1%. Getting everything working is the hard part. :D
[G4 Android Development] genesixxbf3:
damn a i9300 still alive (until now) :eek:
[G4 Android Development] maxauvy:
Keeping you guys updated about my "back-from-repair" H815 that could not take pictures anymore.

I'll get back to my parents' for Christmas and thus will be able do test several things. I think I'll first try [MENTION=976442]tulen_kobi[/MENTION] 's build with [MENTION=5461026]kessaras[/MENTION] 's device tree.

Also noticed that for those who want a semi-official build (at least the outdated build based on official LaOS source), there's the microG option (ya know, that microG thing if you want to use Google Play Services without full Google proprietary software that is going to eat your battery and stole personal data). They started to build for the same devices as LaOS, only adding their patches for signature spoofing that allow microG to work, and F-Droid.

Even if LaOS stopped building for the H815, microG is still built on a daily basis. I use this build on my tablet, it's just working fine, so if you wanna try...

https://download.lineage.microg.org/h815/

When I'll have a little free time, I'll try to build with Suicide Squirrel's device tree and microG patches, if anyone's interested.
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
Good luck and please let me know your results.

I've tested AOSCP, but same problem with camera.

What I found out: Torch doesnt't work, too. But if you switch torch on you can see a little red light where the torch should be.
[G4 Android Development] kessaras:
huh ?

i dont have any bug in AOSCP sorry and torch is fine too.

One bug i have with encryption and 1 small now with the Oreo device tree i used in Nougat to test it and will fix that too when im done with Oreo and is stable.
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
It's not your bug, it is - from my understanding - in every rom.

We already wrote about it, please see

https://xdaforums.com/g4/development/rom-cyanogenmod-13-0-lg-g4-t3477475/post74412618#post74412618

and next pages.

I followed your AOSCP thread and read about camera (1st december?), that's why I've tried AOSCP - but 100% identical behavior than at lineage.

If you are interested to solve, just let me know. I'd really appreciate it and support as much as I can (what is unfortunately not much...). I've provided logs already in this thread but didn't find (will search more if interested or can make new one).

Edit: Found logs:

https://xdaforums.com/g4/development/rom-cyanogenmod-13-0-lg-g4-t3477475/post74552514#post74552514
[G4 Android Development] kessaras:
i see. thats a lib there doing all that. Are you sure it happens in all roms ?

it doesnt happen to others only you and thats strange, but its something that can be fixed.

but before that, flash my AOSCP (from 1-12, not latest with the Oreo device tree that im testing in nougat too), and clean flash of course.

Use the google camera which is stock there (if it gets deleted while flashing gapps , download it from apkmirror and install it back).

Provide me same logs to see that you really have same issue.

Then i will fix it locally and see how my phone will react to this change, (i dont want to fix your and break all the others) and i will update blobs so my roms and other roms use the same.
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
Great, thank you. I'm not the only one. It's me and [MENTION=4851489]maxauvy[/MENTION] and - most probably - everyone who got a "new" H815 (at least motherborad like [MENTION=4851489]maxauvy[/MENTION], I've got a totally new one from manufacturing date end of July 2017).

I will leave tonight and will travel for Christmas, but come back end of next week, then I will do as requested and provide logs. I need to wait until I am back because last time I switched to AOSCP it crashed (most probably due to Magisk (and / or TWRP?), please see full story here: https://xdaforums.com/g4/developmen...ed-devices-t3499478/post74760054#post74760054 ).

Of course I don't know if this is at "every" Rom, but it was at AOSCP and Lineage and I was wondering if any else would work.

I've tried different camera apps incl. google camera, but of course will do again and provide logs approx next friday or saturday.

Thank you!
[G4 Android Development] genesixxbf3:
Please no micro g talks here

Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
[G4 Android Development] Minto107:
Mine still is ;) S3 is the legend. Best android phone ever created
[G4 Android Development] belrik:
I still have an i9000.... Original Galaxy S! New battery of course. ?

Of course the RAM, CPU and storage speed make i9000 and even i9505 hard to use if you're in a hurry.

Long live user-replaceable batteries!
[G4 Android Development] Minto107:
Damn, I wanted to get original i9000 myself. I9305(LTE and 2GB RAM) still rocks. If not screen burn and 1h SOT I'd use it over G4. It has way better screen colors and sharpness and it's still usable for 2017
[G4 Android Development] codeworkx:
Depends on what phones you've used so far.

After you've used one of the latest QCom 8-Core SoCs paired with 8 GB of Ram and 128 Gb blazing fast storage you wont call anything else "usable". :D
[G4 Android Development] Minto107:
Fortunately, I don't have an access to such phones, at least till August, S9 or Note 8 is coming ;)
[G4 Android Development] ahmed10g:
does this rom suport h818p ????

if not

can any one tel me which custom rom support h818p ?

thanks
[G4 Android Development] tulen_kobi:
Currently no one, but [MENTION=5545101]steadfasterX[/MENTION] is developing unofficial bootloader unlock so you should be good to go soon.
[G4 Android Development] kessaras:
Deleted
[G4 Android Development] tulen_kobi:
[MENTION=3208754]codeworkx[/MENTION] Can you please help us to merge these changes to our kernel? It breaks quite a lot of things. The phone than stays at the boot logo with lots of errors.

Kernel link: https://github.com/Suicide-Squirrel/Titan-Kernel-LG-G4/tree/oreo-mr1-release/fs/sdcardfs

Your Gerrit review for leeco_msm8996: https://review.lineageos.org/#/c/199666/

EDIT: The goal is to merge this:

https://android.googlesource.com/kernel/common.git/+/e24c0d6be128607deb7ac11a69deadf9e4eff7d2^!/

EDIT2: Now the link is correct, thanks for mentioning [MENTION=5776465]genesixxbf3[/MENTION]

EDIT3: All commits after Move directory unlock before touch are missing.

https://android.googlesource.com/ker...10/fs/sdcardfs
[G4 Android Development] genesixxbf3:
It is merged since n bringup on los kernel

Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
[G4 Android Development] tulen_kobi:
This one is not, it is a new change. We are at the same level if you compare:

https://github.com/LineageOS/android_kernel_lge_msm8992/commits/cm-14.1/fs/sdcardfs and

https://github.com/Suicide-Squirrel/Titan-Kernel-LG-G4/commits/aosp/fs/sdcardfs
[G4 Android Development] genesixxbf3:
but the commit you linked is merged
[G4 Android Development] tulen_kobi:
Shout, my bad. I thought this one: https://android.googlesource.com/kernel/common.git/+/e24c0d6be128607deb7ac11a69deadf9e4eff7d2^!/

I will update it. The Gerrit change is about this.

EDIT: All commits after Move directory unlock before touch are missing.

https://android.googlesource.com/kernel/common.git/+log/android-3.10/fs/sdcardfs
[G4 Android Development] ChristosPas:
I installed the zip and went to boot the phone up, but for the last 15 minutes all it's doing is showing a dot moving along a curved line. How long should it take for the phone to boot up? is it normal?