yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] Surly33:
Also, having the frozen lockscreen issue. Able to boot and run the rom for a day or two. Eventually, the home button stops responding, and I reboot to a non-functional lockscreen. Phone is operational, however it appears that the system UI or something similar is not loading. I can access status bar and notifications, but cannot unlock or see any lockscreen/homescreen display. Please let me know what I can do to assist in the diagnosis of this issue. Thanks for your help in advance!
[G4 Android Development] sejmand:
I found out in another thread, that it is necessary to wipe data in advanced wipe in twrp.

I try it in a few hours when I'm at home and let you know.

update:

home. loading files...
[G4 Android Development] Dervisk:
I don't use that sorry..!
[G4 Android Development] sejmand:
look here

I did it and it worked!!!

my way:

reboot recovery - factory reset - "wipe data" in advanced wipe - flash cm14.1 12/17 - gapps 12/17 - wipe cache + dalvik (I think not necessary) - no more lockscreen-freeze + reboot (took a long time...)

(my explanation: old systemui was no longer in data partition because of advanced data wipe)

great thanks to: [MENTION=5461026]kessaras[/MENTION]

UPDATE:

did couple of reboots: all fine and suddenly systemui crashes:

AGAIN LOCKSCREEN-FREEZE!!!

whats that...? no idea.... :confused:

**** back to cm13...
[G4 Android Development] kessaras:
genesix has to take a look at this. this time you did it right. you clean flashed.

a logcat could help him from someone that has this error. more than 3 people report the same problem , at least someone send a logcat....
[G4 Android Development] sejmand:
a little light on the end of the tunnel...

---------- Post added at 12:43 AM ---------- Previous post was at 12:41 AM ----------

at witch point is it possible to send a logcat? I can't get "in the rom" and get the logcat.... I'm not a depvelopper... perhaps I can help, but not shure...
[G4 Android Development] kessaras:
not anymore since you are not on cm14.1.

the way to get the logcat is to use your pc terminal or cmd

and

adb logcat > (path where you want to save the logcat)/logcat.txt
[G4 Android Development] papsr6:
I have a stupid question.

If I want to go at cm12.1 now I must have boot.img bootloader.img and modem.img from lollipop installed on my device?

Sorry but I have not good experience.
[G4 Android Development] kessaras:
only rom cm12.1
[G4 Android Development] codeworkx:
You better do not. 12.1 has some security bugs which are fixed in 13 and 14.1.
[G4 Android Development] Lilim:
Does anyone have problems with Pixiv app on 14.1? It worked flawlessly on 13 but since updating to 14.1 (clean flash) logging in doesn't stick (I can log in normally, but after exiting and reopening the app I'm logged out again) and some sections simply don't load like home or newest works from following artists, both put out a try again error). Dunno if it's an app or rom problem.
[G4 Android Development] sejmand:
So I flash again cm14.1, install logcat, check debugging mode, reboot several times to force the bug, and then:

1. How can I know that logcat is logging during boot Prozess?

2. Can I get the logcat folder with adb pull? Or should I reboot to recovery where I can access the storage with file transfer app on my Mac.

PS: since 2 days I have an old Windows machine in my cellar with win 10. Perhaps also a way...
[G4 Android Development] kessaras:
how to create a logcat

logcat is only a name.

its the usual name of a live log output. since its "live" it shows exactly what you did and where the bug is.

the command

adb logcat

starts logging in your terminal and you see "live" whats happening in the phone right now.

the

> ~/(path you want to save it)/logcat.txt

just saves the logcat to computer or mac.

for example lets say i want a log in my home directory. i will do this:

adb logcat > ~/logcat.txt

the above will create a .txt named logcat in home directory and it will keep logging until i stop it.

so now i press control+C and i stop it. i think on a mac its meta+C ?
[G4 Android Development] sejmand:
I test the Prozess in cm13 and when I'm familiar, I start a cm 14 try.

This will my 5. attempt with cm14.1 and I'm quite routined with this Prozess

update:

hahaha, very simple!

to stop it is: "ctrl + c" :)

to save its "adb logcat -d > logcat.txt"

and the log is from beginn the boot?
[G4 Android Development] atoml:
Everytime I try to use a camera app like "Manual Camera" the app closes (no forceclose dialog). I want to shoot raw.

logcat

http://pastebin.com/h42NfjaM

---------- Post added at 11:55 AM ---------- Previous post was at 11:51 AM ----------

Start "adb logcat -d > logcat.txt" before you boot the device and let it boot for some time (logs are only printed after certain module shave loaded which may take some time).

Wünsche dir noch einen schönen vierten Advent.
[G4 Android Development] sejmand:
shall I try to make a logcat or just wait until it's fixed...

when do I know that it's fixed?
[G4 Android Development] brossovitch:
The app, Manual Camera doesn't work on G4. Not on any version of Android. Not without a few tricks to make it work. But it typically doesn't work. Even though the compatibility test app says it will.
[G4 Android Development] XeniX_Force:
So i thought id install quick memo and i got this.

What existing package?
[G4 Android Development] genesixxbf3:
please don't be dumb it's an lge apps
[G4 Android Development] XeniX_Force:
Ah right. Found it some where else. Thought it was another memo app
[G4 Android Development] Dervisk:
Since I got the lockscreen freeze I disabled it to avoid any hassle. I'll re-enable it when it will be fixed. I think that's the best thing to do for now..!
[G4 Android Development] codeworkx:
On which build do you have the bug?
[G4 Android Development] sejmand:
I got the bug in the 12/17. earlier build also, but I there I only wiped factory not "advanced data"
[G4 Android Development] Dervisk:
17/12 and earlier builds as well. I just have to reboot the phone and it's temporarily fixed though so it doesn't seem as bad as some other people in the thread. I don't mind not having a lockscreen.
[G4 Android Development] kessaras:
not having a lockscreen ? you can install holo lockscreen which is like the cm11 lockscreen until this one is fixed. set none in settings and use another one
[G4 Android Development] Dervisk:
Well I almost prefer not having one and accessing my content quicker :) Maybe you misread the post!
[G4 Android Development] kessaras:
i read it, but if it gets stolen ?

the lockscreen along with disabled power button can prevent the thief hide it until you locate it with google's help :D

happened many times here.
[G4 Android Development] Dervisk:
I guess you're right, I'll check out some alternatives in the meantime!
[G4 Android Development] codeworkx:
I'll stay on 14/12. :P
[G4 Android Development] genesixxbf3:
I DID NOTHING IT'S NOT ME !!!

#BlameCodeworkx
[G4 Android Development] sejmand:
In my case, reboot was not possible. It ends always in the freeze...
[G4 Android Development] :
A lock screen gives a false sense of protection. Just boot into TWRP and download all the files straight from the device. Or disable the lock screen by deleting some files (/data/system/locksettings.db*). Disabling the lock screen is interesting as you can access all the web pages the user automatically logs into.

The only way to protect your personal files is by using encryption in combination with something like Snooperstopper (shuts down the device after a defined numbers of failed login attempts).
[G4 Android Development] kessaras:
Me I only use xposed (when it will come to sdk25) to disable the power button. Lock screen works fine as protection. I don't need anything else. I can use my other phone to locate my stolen one. Same thing I do with iPhones and cydia.
[G4 Android Development] :
It's a G4, you only have to remove the battery to power it down ;) Next you power it up and boot directly to recovery, no internet connection and thus no location there.
[G4 Android Development] 3-4:
Lockscreen doesn't works

Model H815 international

Last installed: cm-14.1-20161218-NIGHTLY-h815.zip

From the first time I installed CM (both 13 and 14.1) lockscreen code never worked.

When I try to set it, I insert a value and then the app crash and ask me if I want to restart the app or disable until next reboot.

Please how to do to check correct values in text editor?

What would be the default right values?

There's some workaround to make work the lockscreen code?

Thanks!!
[G4 Android Development] XeniX_Force:
Lol no one is blaming no one. But what is causing this error. Thankfully i dont have it. Ive been doing delta updates so i guess that prevented it
[G4 Android Development] kessaras:
i feel stupid now :D

i forgot its removable. its my first lg since p880 1st release. i was used to iphones and htc ones
[G4 Android Development] genesixxbf3:
i know but you should know it's always better to blame codeworkx even tought i do all the misstake :p
[G4 Android Development] thewild:
I had a Blue Screen of Death yesterday, 17.12 nightly, 17.12 nano gapps, Llama Kernel.

Shoud I rather report in Llama thread ?

I also disabled the lockscreen, I like to go straight to the launcher.

I use Cerberus, it works great and it got my previous phone back (the police officer where amazed ;)).

I guess it's the same as Android Device Manager, but it survives a factory reset (I believe ADM does not ?).
[G4 Android Development] XeniX_Force:
What is causing it though?
[G4 Android Development] thewild:
Some settings are not translated anymore in 17.12.

I'm not 100% sure but I think they were OK on the release I had flashed before. It was a dirty flash from CM13 to CM14 though.

Also "Status Bar" all the way down in settings, just before Developer Options. Weird.
[G4 Android Development] kessaras:
it is the new lockscreen.

Maximum protection. :D
[G4 Android Development] genesixxbf3:
then go help translating
[G4 Android Development] Freddyfre:
Client email of default lack request read report

Many times does not reach the new mail notification

I cant download my mail sending folder with Gmail (with outlook works)
[G4 Android Development] thewild:
I said I believe it was translated before.
[G4 Android Development] genesixxbf3:
yeah but translation has changed so maybe it's not anymore
[G4 Android Development] Surly33:
I inadvertently induced the dead lock screen issue by attempting to theme with substrantum. However, I had not connected my phone to my computer for debugging prior to causing the dead lock screen, and was not able to acknowledge the debugging prompt. Is there a way to get log from a device in this state should it occur again?
[G4 Android Development] genesixxbf3:
well if you use substratum then it's not a cm problem
[G4 Android Development] kessaras:
no, and just like the op said, a substratum problem must be reported to substratum theme dev.

to simple remove the substratum theme that caused you the error, go to twrp file manager , navigate to /system/vendor/overlay and delete the overlay that caused the error
[G4 Android Development] papsr6:
The camera app settings is not very good simplicity..

Developers must make manual settings in other section to be more simple and easy to change them.

Is not good all together... Too much complicate.
[G4 Android Development] fishears:
Hello

Would someone here mind checking one thing for me please? We're looking at a problem with the LG gpad 8.3 and CM 14.1. With SD card formatted as internal we're getting a "not enough space" error when trying to move apps from SD to internal storage. So, to see if this is device specific could someone here attempt to move any app in the same way? It would be very helpful. Thanks
[G4 Android Development] kessaras:
if you were on another rom and used the sd as internal , the sd is recognised only at that specific rom as internal.

that means that you have to format the sd every time you change a rom.

There is also a bug currently that came with the 7.1.1 patch from google.

I would also want to know more about it.

The sd needs format and remount every time we do an update ......
[G4 Android Development] XeniX_Force:
Guys. This is out of topic and a little stupid. But if i miss a delta update (using cm downloader) i will get the features in the earlier update i missed. Right?
[G4 Android Development] kessaras:
lol. ofc unless the feature gets removed in the next build haha
[G4 Android Development] fishears:
The build for gpad (v500) does not have the format & remount bug that you describe - might be worth taking a look at the v500 device tree (I'm not the maintainer). Still if someone who has their SD formatted as internal could try moving an app to and from the internal and SD card then that would help with debugging.

Is the G4 using FUSE or SDCARDFS for the sd?
[G4 Android Development] xwerhelat:
I keep having the same issue, the wifi isn't working because my adress is 00.00.00.00.00
[G4 Android Development] codeworkx:
Mac addresses are stored on misc partition and are unique per device. You got a problem.
[G4 Android Development] xwerhelat:
when I install the stock kdz it works, but not on this rom :( (it worked before but I did something to mess it all up), any idea on how to fix this?
[G4 Android Development] kessaras:
There is someone that might have an idea and he had same problem 1 week ago. I'll find him and ask him here , but will do it much later tonight cause i write exams in digital electronic systems later.

And don't worry it can be fixed.
[G4 Android Development] xwerhelat:
I'm requesting an image of the misc partition from anyone on here with a working LG G4 H815. The phone can be running any ROM, and prior to flashing was ideally running V20D.

Process to generate a image of misc is as follows:

Reboot into TWRP recovery.

Run "adb shell" or open a recovery terminal.

Run "ls /dev/block/platform/*/by-name/misc" to identify the path to your misc partition.

Mine is "/dev/block/platform/f9824900.sdhci/by-name/misc"

Run "dd if=/dev/block/platform/f9824900.sdhci/by-name/misc of=/sdcard/misc.img"

Replace "f9824900.sdhci" if appropriate for your device, using the value found in step 3.

You now have a file misc.img in your storage directory. You can either use "adb pull /sdcard/misc.img" to download it onto your PC, or you can upload it directly using XDA mobile.

If anyone here can follow the above steps and upload the resulting image, I'd be deeply grateful.

Thanks in advance!

---------- Post added at 02:12 PM ---------- Previous post was at 02:09 PM ----------

thank you my friend
[G4 Android Development] codeworkx:
U dont need a image.

Get a image of your own misc partition and add your macs using a hex editor.

Wifi mac is at 0x3000

BT mac is at 0x4000

Then write it back to your device.
[G4 Android Development] xwerhelat:
how do I write it back to my own device?
[G4 Android Development] XeniX_Force:
In the way u were to planning to write someone else's image
[G4 Android Development] xwerhelat:
I don't know how you do that...
[G4 Android Development] codeworkx:
adb root
adb shell
dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc

be carefull and do not write to any other partition.
[G4 Android Development] pontusl:
Anyone else having trouble with the reception running 14.1-201612-18-NIGHTLY-h815?

In places where I earlier had OK reception (running stock ROM mainly) have none now. And in places where I earlier had LTE I now have HSPA.

I'm guessing this could be fixed with flashing a new modem? Right? If that is the case, could someone recommend one?

Am I right in assuming that by just installing CM14.1 I get the modem linked to in the first reply? This one: http://downloads.codefi.re/autoprime/LG/LG_G4/H815/H81520D/LG-H81520D-Flashable.Modem.zip

If not, could my issue be solved by flashing that?
[G4 Android Development] codeworkx:
Try 20g modem. See autoprimes rom collection post.
[G4 Android Development] xwerhelat:
OMG IT WORKED :victory::victory: THANK YOUUUUUUUUU

---------- Post added at 06:05 PM ---------- Previous post was at 05:34 PM ----------

When I try to click the "Developers Option" the settings app seems to crasch, any idea why? :/
[G4 Android Development] genesixxbf3:
try to clean cache
[G4 Android Development] sejmand:
dead end of lockscreen:

shall I try to get a logcat of this bug?
[G4 Android Development] xwerhelat:
Didn't do anything :(
[G4 Android Development] genesixxbf3:
have you flashed supersu ?
[G4 Android Development] xwerhelat:
Yes and also open gapps. But I reflashed the rom and didn't install any of them and now it's working!

Was it the gapps or SuperSU that messed it up?
[G4 Android Development] genesixxbf3:
SuperSU mess up
[G4 Android Development] brossovitch:
Despite the latest changelog (20161220-nightly) having video recording fix, it still doesn't work for this device.

Also, everytime I update I need to reset all of my notifications and ring sounds. Every time. Is this because builds for this device have broken sd card function?
[G4 Android Development] Surly33:
Sent one in yesterday, but I can't imagine another would hurt.
[G4 Android Development] genesixxbf3:
where have you seen that ?

edit found it (i think )

try to add that to your build.prop and test

persist.camera.HAL3.enabled=1
[G4 Android Development] genesixxbf3:
saw your but nothing relevent
[G4 Android Development] kessaras:
here they have a point.

you take your own images the way you said we do it, then you edit them just like genesix said, then you push them back the same way you were gonna push ours.

i think [MENTION=6287517]brossovitch[/MENTION] had a similar problem with his mac address and fixed it on his own.

if he can confirm it ?

~EDIT: ah nevermind its being solved. ... im too late :p took long to finish the exams
[G4 Android Development] sejmand:
Where shall I send my log, when I (hopefully) was able to get/grab one?
[G4 Android Development] brossovitch:
I did not. I just couldn't connect to WiFi. But fixed it.

There's always z

KDZ to stock then reflash TWRP. That I've done a few times this month.

All in all, this ROM is going very well and seems like the only ROM my device will accept now.

Does anyone know if we CM Recovery is fully functional? I tried on one of my other CM14.1 devices and ended up bootlooped when wiping and it wouldn't flash the ROM
[G4 Android Development] kessaras:
latest twrp update beta 5 that merged our devices is working fine.
[G4 Android Development] genesixxbf3:
Use gist
[G4 Android Development] brossovitch:
Well the latest Official TWRP 3.0.2-0 for h811 works perfectly as well. Just wondering about CM Recovery. Because I was thinking of sticking with all things CM rather than not. But then again, if something goes wrong you can't boot recovery with CM because it will just factory reset rather than boot recovery. So I guess nevermind.
[G4 Android Development] kessaras:
:D

i think you don't have a rom to flash tonight thats why you dig around.

maybe you need a bug to help you flash rom again :D
[G4 Android Development] sejmand:
Sorry for the noob-question:

I created an account.

Now, where to post/address the log?
[G4 Android Development] genesixxbf3:
create new gist??
[G4 Android Development] kessaras:
Hahahahahahaha

Upload it here man . since you don't know gist , forget about it. Upload it here in 10 seconds and you are done. No big deal.
[G4 Android Development] brossovitch:
Nope. Jist read the changelog and then flashed the latest build. Tried 5 others yesterday killed all three of my batteries too. Hahaha

I also don't understand. What do you mean? There's plenty of bugs in this ROM, more than enough for the rest of the year.

Dig around? By downloading and updating? Not quite digging when CM Downloader Premium does it automatically. But okay. And like I'd told you before. More than 90% of my issues were resolved when I stopped using the llama.
[G4 Android Development] kessaras:
Start using it again. We need logcats to help our dev make it work flawlessly like in h815
[G4 Android Development] sejmand:
Hahaha lol

I flashed 20.12. Version and did about 5 reboots and no frozen-lockscreen anymore...

cross fingers...

I keep on trying to reproduce the "bug"
[G4 Android Development] brossovitch:
Hahaha!

No problem. I guess I can ise the Llama again, but I won't report issues using it here.. I miss it so much. But it hates my SD card.

As far as the SD card issue with notification. Seems the System needs several minutes to acknowledge the sd card and any sounds in all storage during boot.

When I restart the device after flashing new ROM, if I go into a sounds option anywhere the list is either empty or incomplete. But after a few minutes it fixes itself. But thos is clearly a CM issue and has nothing to do with the device. I've noticed on 2 other devices.

But I'll grab the cat log for any issues I can. And when I can actually afford it, I will donate. Thanks for all the work you do for us [MENTION=5776465]genesixxbf3[/MENTION] & [MENTION=3208754]codeworkx[/MENTION]

Und Happy Holidays to the G4 community.
[G4 Android Development] sejmand:
Rebooting in many ways... no issues!

Thanks a lot for helping and your patience, I learned a lot of things. (Hoping I'm not too "spam"y)

UPDATE:

now I got the lockscreen freeze again, after backing up system in twrp, then reboot from twrp...

---------- Post added at 10:48 PM ---------- Previous post was at 10:08 PM ----------

"h815 lockscreen freeze 20.12.2016"

https://gist.github.com/sejmand/b222b0956acd8ba782f28178d677f244

is the (far to long) log...

user: sejmand

Can you find this?

---------- Post added at 10:55 PM ---------- Previous post was at 10:48 PM ----------

reboots without any effekt... still the freeze

is this better?

"log4.zip" should be the right one!
[G4 Android Development] Azrith:
Anyone else seeing issues (intermittently) with GPS locking? G4 stock was always pretty solid but now I see after a few weeks of running CM that it sometimes takes a min or two to lock for nav in maps or will sometimes drop after running accurately for a while. I tried the usual GPS fix apps to clear and reset GPS data but seems to happen again even so. Could be Llama kernal but also could be my user error. Feedback appreciated.
[G4 Android Development] genesixxbf3:
Blaming kernel for GPS well done.
[G4 Android Development] brossovitch:
Nope navigation works perfectly with location on Device only mode. No stutters or errors.
[G4 Android Development] slshults:
How are you getting back to CM13?

After I flash cm-13.0-20160726-NIGHTLY-h811.zip the dialer crashes. (I've done lots of wiping)

Do you know where I can find a later version of the cm13 nightlies? Thanks.
[G4 Android Development] kessaras:
in gapps. aroma gapps and choose dialer+framework.

in capps. thats another dialer.

in rom, extract it from the system
[G4 Android Development] slshults:
Thanks. I'd asked how to get back to CM13, but if I can get the dialer working in 14.1 I'm happy.

I'd tried nano and stock gapps but I'll try the aroma route with dialer+framework, and will report back. (Currently working with your cm-14.1-20161220-UNOFFICIAL-h811.zip , but please let me know if you suggest I drop back to 12.17 official or your 12.17)
[G4 Android Development] kessaras:
Not mine :D

im just a little guy haha

as a user i suggest you wait until next update, but if its important (which i think it is, since its the dialer)

go back to cm13.

my device here is h815 and all are working, its hard to tell.

wait a little until someone with h811 see the problem. if its only you, then you didn't really wipe.

we had same problem a couple of days ago again, people do factory reset because they believe that that wipes. It does not.

Wipe is : advance -> wipe -> system,data,cache,dalvik-cache.

anyway, just wait a couple of hours to get a h811 user opinion.

the only thing i can help is to extract the dialer to send it to you but that wont fix anything if you wiped properly and clean flashed.