yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] kessaras:
[MENTION=2459020]shdmitch[/MENTION]

z2 is a msm8974 with a 801 cpu.

z3 same.

z3+ is a msm8994 with a 810 cpu.

Only devices with msm8992 (snapdragon 808) and the same bcm4339 audio chipset have the same issue we have.

I looked in their bluetooth development and its equal to ours, with differences like waking up from ioctl when our's is waking up from proc.

What anyone can try, but i bet it will break the bluetooth, is to grab the bluetooth firmware from a shinano device from path : /system/etc/firmware/

it's named BCM something, and replace with it ours BCM4339 in /system/vendor/firmware and reboot.

99% it will break bluetooth, but you may test it if you want.
[G4 Android Development] Bluto666:
Same chipset was available from Cypress, maybe somewhere there are different configuration files available to try?

CYW4339
[G4 Android Development] Mogster2K:
You can also try using a different launcher like Nova or Apex.
[G4 Android Development] fi5z.x9:
Turns out changing some APN settings was all I needed. Switched from IPV4 to IPV4/IPV6 for both APN Protocol and APN roaming protocol.
[G4 Android Development] ososmam:
Anyone have problem with charging with fast charge or that only me i'm using Oreo version with usu bootloader v29a
[G4 Android Development] VmasterL:
I have before, just toggle switch chargers or unplug and replug a few times.
[G4 Android Development] ososmam:
Didn't work still get same error

It charges from PC only
[G4 Android Development] VmasterL:
Try reflashing clean or clean flash modem and bootloader.
[G4 Android Development] bonner1928:
battery calibration & root access

Hi,

I'm using the CypherOS 6.0.1 for quite a while and decided to change battery. Buyed a Duracell battery which seems to have a nice performance but causes crashes sometimes. So maybe battery calibration makes sense... Tried one app, but most of them need root - and I suppose root would make the app work better.

1) Any suggestions how to calibrate the battery best?

2) Need recent SuperSU as installable ZIP via TWRP -> the link mentioned on the first page of the forum doesn't work anymore...

Thank you !!!
[G4 Android Development] kessaras:
There is no recent SuperSU. It's dead long ago.

Your best chance is if a dmesg and a logcat has any valuable information to help me "allow" your lame battery.

Duracell generally has a good name in batteries but not for smartphones.

Gimme logs to see what I can do.

Battery calibration is just a file in data. You could try a clean flash and see if it fixes your crashes
[G4 Android Development] bonner1928:
I'll try the clean flash first before stealing your time by analysing log files ;)

But what exactly does it mean? Wipe cache, installing the rom again or what...?
[G4 Android Development] kessaras:
Wipe data and cache

Not format ! Advance wipe
[G4 Android Development] bonner1928:
...****...cleared data, then restored backup, removed locksettings.db -> face unlock is gone :crying:

Tried to install GApps and rom again, but without success ... face unlock was my favorite feature, can anyone help?
[G4 Android Development] Bluto666:
Try to delete also the following files (or equal ones, if available) in /data/system:

password.key

pattern.key

locksettings.db-wal

locksettings.db-shm

In LG stock roms are also files named gatekeeper.password.key, gatekeeper.pattern.key etc., dont know if they are available in custom roms too.

Do this on your own risk!

Then you have to setup face-unlock again.
[G4 Android Development] Mogster2K:
The latest (last?) SuperSU is 2.82.

https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
[G4 Android Development] bonner1928:
None of these files exist.

But I did a full backup before, it must be possible to restore the state as is was before, I guess... I do not understand why a full restore can make face unlock disappear... :confused: Do I have to format/wipe some partitions first? Don't want to brick my device...

Thank you for help!
[G4 Android Development] bonner1928:
User IQ too low - error :p

Didn't know the google trust agent has to be activated before face unlock appears in menu. It somehow turned off, now everything is working fine!

But the battery problem still exists. Kassandra asked me to wipe cache and data - this would clear my apps etc, right? And what about dalvik chache?

As far as I understood the file which stands for battery statistics must be resetted this way, right?

Sorry for all these questions, but I'm sure many folks out there are interested in what to do after changing battery (I know 4 peaople at least :))

---------- Post added at 12:18 PM ---------- Previous post was at 12:14 PM ----------

...by the way...the battery seems to last quite long, but is has some funny behaviour -> sometimes it goes down to lets say 12 percent and after a while its back at 15 percent ... must be my energetic aura of mystery :)
[G4 Android Development] aha360:
Kassandra? Did you assume [MENTION=5461026]kessaras[/MENTION]'s gender? LMFAO!

---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------

Kassandra? Did you assume [MENTION=5461026]kessaras[/MENTION]'s gender? LMFAO!
[G4 Android Development] bonner1928:
ups....sorry...I'm on my way to being banned or at least ignored by kessaras....
[G4 Android Development] Bluto666:
I think this is for security reasons. I always had the same issue when restoring from a backup, but I use pattern-lock and so I had to delete pattern.key / gatekeeper.pattern.key and locksettings.db to unlock the phone an get pattern-lock back to work. Maybe the settings for face-unlock are stored in a special secured section of the phone, in the same way as fingerprint data are stored. Anyway, I dont have enough knowledge, to solve the problem for you. The only solution I can provide: In future remove any screen lock via the android settings, before backing up and after restoring you have only to reenable your prefered unlock method without any need to delete the previously named files from the phone.
[G4 Android Development] kessaras:
Noob alert !

I said to wipe data. If you restore data you restore the files and the problem. Wtf is wrong with you ?

Just Wipe the data and use the phone to see if the error is gone , otherwise send me a dmesg and a logcat.

EDIT:

And I'm suspecting you don't know when to log.

I need to see the crash in the log so that I can read why it crashed. So the logs , the dmesg and the logcat must be taken right before the crash until the crash.
[G4 Android Development] berkantkz:
Deleting /data/system/users/0/settings_*.xml files brings back the Smart Lock feature. However, you lost your preffered settings. Some parts of systemui (such as quick toggles) and settings app restores values to the default.

Just telling it if anyone wonders and afraid to lose data while testing.
[G4 Android Development] Phanty:
I gave my G4 to my significant other temporarily. I reverted it back to Nougat to regain bluetooth calling and it's an h811. However, now I am receiving bluescreens and I am wondering if I ever did upgrade the bootloader.

I took a look on the leech server and saw this zip:

/stock/LG/h811/20p_arb3/h811_20p_ARB3_bootloader.zip

What's the easiest method of checking the bootloader version?

Can I simply flash this on top of the latest nougat build, or is there a process? I flashed using the official unlock method, not UsU, if that helps.

Thanks in advance!
[G4 Android Development] steadfasterX:
The easiest is to flash the bootloader again. The other way is to dump the bootloader stack (SALT or TWRP with dd) and compare md5sums of all KDZs of your model.

My leech server contains now also the latest version 20x for the H811 as a TWRP flashable zip ( http://leech.binbash.it:8008/stock/LG/h811/ ).

If you want to use that one ensure you copy the md5 file as well to the device to ensure TWRP will verify the zip before flashing.

No process. Either boot to fastboot and flash each image file or flash the TWRP flashable one. Check for any error messages: if there are any do NOT reboot and ask for help.

The TWRP flashable one does not contain the recovery partition so TWRP will stay as it is so flashing, checking for flashing errors, rebooting. That's all.

.-
[G4 Android Development] fedeanimation:
Hi guys I have a problem with my lg g4.

When is in standby often its turn-on the screen like if I try to use the camera, or appear the number keyboard to input the unlock code. It happens many time during the day, this condition drain the battery life.

Someone can help me?
[G4 Android Development] kessaras:
It's not happening here in aoscp. I removed double tap to wake which bugged and did that.
[G4 Android Development] fedeanimation:
Thanks now is perfect!!!

PS maybe do you have a solution to use the bluetooth in the car?
[G4 Android Development] kessaras:
maybe a jack to bluetooth reciever or a micro usb to bluetooth reciever. one of these two may work to bypass the bluetooth distorted audio.

about your car if it doesn't make a connection, i got no idea. at mine it connects fine. check bluetooth version in developer settings
[G4 Android Development] fedeanimation:
It recognize the bluetooth of the car but when I am during a call I can't switch to bluetooth, it not appear the button in the call screen.
[G4 Android Development] F1Fanatic27:
Not sure what I'm doing wrong here. I've read up on TWRP issues in the forum and I've tried manually installing the 'preview' version of TWRP from steadfasterX's server (tried both Oreo images) via fastboot, but I still cannot boot into TWRP using the key combo, or with 'adb reboot recovery', or by booting the recovery image through fastboot (although I did read that was an issue specific to v29a firmware). I used TWRP to install the ROM and Gapps, of course, but I haven't been able to get into it since then and I need to install Magisk. Even if I was to revert to v29a stock, then reinstall the ROM, Gapps and Magisk before booting into the ROM and setting up as normal, I would still like future access to TWRP to flash additional zips, or for backups, and so on.

Any ideas on what I'm missing? I should mention I'm coming from a fresh install of full stock v29a Nougat firmware. I did install one other Oreo AOSP-based ROM before changing to this one, although I wouldn't think that affected anything as I wiped everything necessary, including the system partition (as well as the usual data, cache and dalvik-cache). Also, I had this issue before when I was using this ROM previously, about a year ago (can't remember if it was an Oreo or Nougat build I was using) and I fixed it by flashing a boot.img that someone posted around the time, which allowed me to get into TWRP. I haven't yet gone back to find that img file, but in any case I didn't think it would help as it's now over a year old. If anyone confirms that boot.img was definitely the same as the one used in the latest Oreo builds (I'm on 2018-10-16 currently), but with the necesary changes for TWRP access, I'll gladly take the route of flashing that if this is the only fix, however I can't help thinking there's a better way of solving this. :laugh:
[G4 Android Development] kessaras:
We have a TWRP thread and developer for a reason.

Me I got no idea about TWRP. I can't even do the most simple thing , to build it, I can't even imagine debugging it.

I couldn't do it even if it was in my dreams. So go there and ask help. Tell him everything step by step and he will guide you
[G4 Android Development] F1Fanatic27:
Ah I completely forgot about the TWRP thread, I used that last time! :laugh: Thanks!
[G4 Android Development] themarang:
Any update or info about when pie is gonna be release ?
[G4 Android Development] raptorddd:
i think it wont work it has ril problems. and is available to tey but ril not working and may never work.
[G4 Android Development] choice2rejoice:
Aaahhh, great. Time for a new phone. ??
[G4 Android Development] deltadiesel:
I know this kessaras guy that can fix it
[G4 Android Development] nardndoka:
Android Pie 9.0 not available

When you try to open the Pie folder http://leech.binbash.it:8008/aoscp/pie/ you need a username and a password to access it.
[G4 Android Development] adam_s_459_:
It's in development and not out for public on this thread
[G4 Android Development] Flaggusp:
Is really weird to see in the thread name that there is a pie build when clearly is not, very deceiving.

Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk
[G4 Android Development] WiZaRd981:
OP have rights to set announcement for build even with thread name.. Pie is there but it is at development and not accessible to public.. (RIL bug) :)
[G4 Android Development] Minto107:
You're like a 1000th person to ask that. Little bit of research before posting would provide you the answer [emoji13]
[G4 Android Development] deltadiesel:
He is right thought it should not be in thread title if there is no pie build released. It is misleading

---------- Post added at 12:14 AM ---------- Previous post was at 12:02 AM ----------

@kassaras

Please fix ril bug
[G4 Android Development] jovanv:
This is a wonderful ROM by [MENTION=5461026]kessaras[/MENTION], stable and excellent battery life. Any chance to get a new Nougat build with security patches from March? The latest N in [MENTION=5545101]steadfasterX[/MENTION] server is from mid-January. Thanks!
[G4 Android Development] kessaras:
Yeah I'll update it but not yet. Per 2 months I do it unless it's seriously important to update
[G4 Android Development] Bluto666:
Why are people always on the hunt for security patches? I run a LG G4 with rooted stock Nougat, a Pipo M9pro Tablet with Android 4.4.2 and a unrooted Zopo ZP999 with Android 4.4.2, I never ever had any security issues over all the years due to outdated security patches. Is this only for a better feeling like "Oh, Im so secure now!"?
[G4 Android Development] nigxxx:
if you dont know, official G4 support ended with 6.0 . " official " Nougat that has been leaked is BETA version.

you should at first thank everyone here who made it possible that we get custom nougat, which is well maintained and updated, and even Oreo. and you are complaining because topic title says P. if you dont like and appreciate this hard work, you should buy yourself new phone which has Pie from the box.
[G4 Android Development] Bluto666:
But it is absolutely stable! Using it since it has been released. :good:
[G4 Android Development] kessaras:
Security patches close security holes. If you use a lot your phone to pay online several stuff and you happen to get hacked then you will change your mind about security. Security is no1.

It's the reason for Google changing in Oreo the apis.

It's also the reason about everything they do.
[G4 Android Development] Bluto666:
I do all the stuff with my phones and tablets and I think/have always thought, the problem is not a hacker, its the person in front of the phone/tablet/pc who is clicking on content in omnious emails and such stuff. In more than 20 years of internet usage and online banking never ever has any fraud happened to me.

Of course, closing security holes is very important, but I cant understand, why people are longing for the latest patches nearly every minute, but using a potential unsecure custom rom or long outdated phones.
[G4 Android Development] sperelli:
It would be great if you update the RR 7.1.2. Latest version dates Feb 2018.
[G4 Android Development] nigxxx:
Little OT from me... I just want to say thank to everybody here on G4 topic, by first to [MENTION=5461026]kessaras[/MENTION] , to [MENTION=8699949]ThePiGuy[/MENTION], [MENTION=5545101]steadfasterX[/MENTION], and many others,for their huge effort and time invested in G4. i learned so much, and i enjoyed here reading and talking. Just sold my G4 after almost 2 years of having it, and i hope this topic will live for some time more, and that you guys will get Pie update. I bought Xiaomi Mi8 lite, so i will be on that forum here on xda. thanks once again, greetings from Croatia. cheers !
[G4 Android Development] raptorddd:
unfortunatelly he cant.
[G4 Android Development] jjcdennis:
I did some searching in this thread and did not find much on the LG G4 issue with the screen going blank when lifting the phone to the ear proximity sensor). This is a big problem for me, as I cannot access the dial pad, or use the power key during calls. The exposed module for disabling the sensor doesn't work for me, nor do any of the other apps I have tried. The sensor tests I have used show that it works, but I am unable to prevent the blank screen.

So is this an issue with CypherOS as well? Is there a solution?
[G4 Android Development] MariuszO:
Had you LCD replaced?
[G4 Android Development] deltadiesel:
My phone does same thing. Resurrection and Aoscp I don't have thus issue

Your referring to the screen going black and doesn't matter what button u press it doesn't appear again right?
[G4 Android Development] MariuszO:
I had samme issue with my phone after broken LCD replacement. It shows that i didn't transfer small rubber part from old screen into new one. This part is a "nest" for proximity sensor. It causes such symptoms when missing.
[G4 Android Development] VladMatao:
ad
[G4 Android Development] fi5z.x9:
[MENTION=5461026]kessaras[/MENTION] please please please... could you give back the freedom to disabling the 2 big cores for good on the oreo based roms? If you could share a flashable kernel, it'd be much appreciated. Thanks. Much respect.
[G4 Android Development] jjcdennis:
Yep. I did have the screen replaced but confirmed that the little black plug is in place. I'm running Cypher and ran steadfasterx's 15.1 Oreo rom before and had the problem on both roms. I've tested the sensor and it appears to work. I can't find a way to turn on the phone.
[G4 Android Development] fi5z.x9:
[MENTION=5461026]kessaras[/MENTION] I can't game on oreo becAuse of overheating ... Even scrolling through Twitter makes my phone warm.
[G4 Android Development] deltadiesel:
If you don't see screen at all at anytime that kcd is defective

---------- Post added at 04:38 AM ---------- Previous post was at 04:35 AM ----------

Only option is disable big cores. You won't have this problem...sure ull loose a couple hundred mhz but not enough to notice difference
[G4 Android Development] fi5z.x9:
Ikr, everytime I deactivate it or try to change the governor, it restores back to default settings.
[G4 Android Development] deltadiesel:
Pretty sure I saw a twrp version with big cores disabled version somewhere on here
[G4 Android Development] Mogster2K:
Can't help you with a kernel, but here is a script you can run after the phone has booted:

echo 0 > /sys/devices/system/cpu/cpu4/online
echo 0 > /sys/devices/system/cpu/cpu5/online

and to re-enable the cores:

echo 1 > /sys/devices/system/cpu/cpu4/online
echo 1 > /sys/devices/system/cpu/cpu5/online
[G4 Android Development] fi5z.x9:
Thanks for reaching out. I've tried disabling the big cores using kernel Adiutor, but the big cores come back online after a while also the apply on boot doesn't stick to disabling the big cores.

Please how do I run this script that makes it stick with each reboot?
[G4 Android Development] Mogster2K:
You would need an app that can run the script each time the phone boots. ROM Toolbox Lite can do it.
[G4 Android Development] fi5z.x9:
Nope. It doesn't work ??. The big cores come back online eventually. Believe it's the way the kernel was designed. Usually, it stays off on Nougat using just kernel Adiutor.
[G4 Android Development] steadfasterX:
Read the "x cores guide" linked here https://bit.do/ilapofixg4
[G4 Android Development] fi5z.x9:
Heeeeeelp!! I'm such a dumb noob. ??
[G4 Android Development] fi5z.x9:
Hi everyone, please help a noob in need. Thanks.

https://xdaforums.com/g4/help/understanding-steadfasterx-guide-to-t3916530
[G4 Android Development] Mogster2K:
Sounds pretty straightforward to me. To be clear, are you running the unofficial version from SteadfasterX's server, and which version of the G4 do you have?
[G4 Android Development] fi5z.x9:
I'm using H811. Dunno if the rom matters considering they'll run on Titan Kernel for oreo, kinda hoping I could flash the custom kernel on any oreo rom. But rn I'm on the latest LOS Oreo (unofficial) from SteadfasterX server.

I could upload my kernel/bootloader backup if you want considering that my variant H811 might be different from yours. Also, thanks so much for reaching out. Really do appreciate.
[G4 Android Development] Mogster2K:
H811 is the T-Mobile variant, so they should all be the same. Anyway, I modified the boot image from "aoscp_h811-6.0.1-20181016-unofficial.zip". Unzip it and test it with "fastboot boot" before flashing to make sure it works. I can't test it right now because my G4 is running Nougat.

https://mega.nz/#!7tExyATa!W9JmBQhB8dmTjD9tFh5OIKhC95L_foOxSsPsyuvTNjc
[G4 Android Development] DarrenNewsgroup:
Is the nougat version the best one to use for my daughter who wants to use the best camera (so I guess that means stock based and not custom ROM) with no Bluetooth calling bugs. I used to have this G4 but gave it to her when I got my G6. The phone was on Imperium but when he battery dies it gets stuck booting (not a boot loop as such but it stays stuck at the bootanimation). Only a factory reset will get it started again (nobody found which program is causing the hang, wipe dalvik and cache did nothing). So now I want to move from that ROM to another. Is this AOSCP N (4.2 build 20190118) the ROM I need?

Thanks

Darren
[G4 Android Development] Mogster2K:
AFAIK the only thing the Nougat build is lacking is full-device encryption.
[G4 Android Development] Bluto666:
Try the original Nougat Stock Rom H815 Nougat Stock [v29A][Int. variant][Official] for the G4. Im running it for more than 1 year now without any problems. Bluetooth calling is working fine and the original LG camera app is still the best. I have a Powerbear extended battery with 6500mAh in my phone and on normal usage it lasts for more than 3 days. I tried several custom roms for the G4, but each had bugs or unusable features and broken bluetooth-calling simply is a no-go for me, also unstable camera-apps (gcam) or camera-apps from the Playstore, which dont support all features of the G4 camera.
[G4 Android Development] sdembiske:
[MENTION=5545101]steadfasterX[/MENTION]

I have recently run into this issue myself with the H812 UsU LineageOS 15.1 rom.

It seems directly related to the Google Phone app version (11.0) that is installed with the rom/Open GApps.

My workaround has been to uninstall the pre-installed Google Phone app (back it up first with Titanium or do a TWRP backup) and then download from Play Store the latest Google Phone app. However, a couple of things have to be done then with respect to the app permissions in Settings > Apps & notifications > Phone - scroll down and

allow

Display over other apps and Modify system settings, then scroll back up to > Permissions - click on and turn on all of them listed there.

Seems to have resolved the issue for me so far - bonus for me is that the new version also has a Dark theme setting in the app.
[G4 Android Development] DarrenNewsgroup:
Have you debloated it? The Imperium ROM was debloated.

---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------

Have you debloated it? The Imperium ROM was debloated I think. Just don't want some of the crapware on it.

Thanks

Darren
[G4 Android Development] Bluto666:
My phone is rooted and I removed everything that I dont need with TitaniumBackup.
[G4 Android Development] DarrenNewsgroup:
Oh ok, I think she needs safetynet for some apps so root is out of the question even with magisk hide and deleting apps in titanium backup?
[G4 Android Development] Bluto666:
Dont know, never used Magisk.
[G4 Android Development] DarrenNewsgroup:
Ok thanks
[G4 Android Development] jjcdennis:
Thanks for that. The only app I see for phone is called Phone and the owner as Google LLC. Version is #30. Is this the app you mean? The lg phone app (on my phone) in Apps is called Phone, version 3.00.00 com.android.dialer.

---------- Post added at 09:11 PM ---------- Previous post was at 09:07 PM ----------

Just to confirm are you running the stock rom with a uSu enabled LG G4?