yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] timn_13:
sorry to slice & dice your question, but i can only offer a little advice on updating - and this may just be me aka YMMV; but dirty flashing a new version with magisk enabled seems to cause the device to go directly to the bootloader screen instead of booting into android. so - when i update, i boot into TWRP, back everything up to the micro sd-card then i flash the Magisk Uninstaller.

side note: if you haven't updated to it, flash the newest TWRP (3.22 i believe is current, you can grab it from [MENTION=5545101]steadfasterX[/MENTION]'s leech server, it likely has "preview" in the name but it's all good) and give it a reboot to recovery *then* flash the rom and gapps. i personally didn't bother wiping cache/dalvik, and then to make sure it's working reboot to the system and let android boot.

if it boots up fine, reboot back into TWRP and flash Magisk and reboot back into android to test that you have root - i suggest this order as i've had to clean flash twice before i paid more attention to the messages/actions in recovery. i suspect that the survival addon script in Magisk leaves some dirty hooks or something around in the boot image and when flashing a newer version it doesn't like it. (the other alternative is to dirty flash, then flash *just* the boot.img via adb from the new rom - but i found it easier to do the uninstaller and install each part separately in case something goes wrong.)

i also run xposed via magisk, and again i disable that before i update as i know it's not necessarily always the most stable thing. i've had no problems with Magisk/Xposed since i started this process, and the past few updates have gone very smoothly. it just takes more reboots to ensure that everything is working, and backups between because that's always a good plan imo. i'm actually running a version or so back myself as i was sick for a bit and didn't feel like flashing my daily driver just in case i broke it (PEBKAC is always a possibility lol) - that being said, i haven't experienced any of the overheating/crashing problems other people have mentioned after some tweaking. i've previously posted my kernel aduitor settings in this thread, they're not much different from stock but when i bought an extended battery i put a fair bit of effort into tuning my device and have a lot of graphical stuff disabled/dialed down and keep a lot of programs/services/radios under tight leash. i don't play games or keep all my sensors/radios on or do anything super intense other than tumblr or browse the web, so that *may* be why i'm not getting demigod screens or heat crashes.

take everything i've said with a grain of caution - but definitely make sure you do an TWRP backup to external sdcard before you update just in case. if you have success with uninstalling magisk and reinstalling it after a dirty flash/reboot, please let me know as i'm curious if this is actually what makes it work or if i'm having placebo dreams and been really lucky! frankly, though, each new version i've flashed has been better than the last, so i hope you'll join us here in july :B
[G4 Android Development] Geckyn:
Is it possible for ril hack to cause damage on a hardware level...my device now barely detects network irrespective of ROM. have to power off and on several times and if I'm lucky it picks up. Restarting makes the phone believe its on airplane mode for no reason
[G4 Android Development] ThePiGuy:
What ROMs have you tried. All Oreo ROMs for the G4 (AOSCP, Lineage 15.1, AICP etc) use this ril hack. You'd need nougat or below to use it without.

And to answer your question, no it can't. All the hack does is restart the ril service until it connects properly
[G4 Android Development] freak97:
my phone won't boot into aoscp_h815-4.2-20180421-unofficial.zip. Why I try to set it up for the first time, it will shut down, what am I doing wrong?
[G4 Android Development] Geckyn:
I was on stock lg F500L nougat v30b before I first flashed the cypheros Oreo everything worked. Later I tried the lineage is 15.1 and switched to AICP Oreo and then that's when the network issues started - SIM is detected but it says "Emergency Only". So I went to back to RR 7.1.2 which used to work fine and then same network issues occurred there... Tried Dirty unicorns , Crdroid it persisted on all of them.. The funny thing is that on all ROMs including stock restarting shows no network and on trying to dial a number it says airplane mode is on even though it isn't. Power off and on is the only way out now...and with that too it only detects network when it feels like. . Ive tried other SIMs too and it's the same issue but the SIMs work fine on other phones. I even tried flashing nougat v29A modem had a demigod screen so I flashed my models usu baseband and there was no crash but the issue is still there..Restarting is now forbidden. Today I just got lucky.
[G4 Android Development] ThePiGuy:
So your device is UsU'd. Maybe check you have everything set up correctly and also maybe see if [MENTION=5545101]steadfasterX[/MENTION] knows anything about this issue.
[G4 Android Development] Geckyn:
Ummm my device isn't UsU'd....when I first bought the device it was an H811( on software version ) But Imei said it's an F500S...I tried upgrading it to marshmallow that's when it hard bricked ( I noticed F500K was written in the download mode during the upgrade so it wasn't an H811 ) PC only showed Qualcomm 9008...So I used QFIL flashed an H815 fire horse stuff which didn't work but the H811 files did work so I had download mode again ...all the T-Mobile firmwares kept bricking it so I realized it wasn't an H811 so I flashed F500L lollipop which worked and I later upgraded to F500L v30b nougat. I didn't flash the F500S because I didn't want the bootloader to get locked.. I still get the secure boot error when I'm booting tho. All H815 custom ROMs work too
[G4 Android Development] ThePiGuy:
I'll be honest, that device is a complete mess :D

I'm utterly lost there - however, all the RIL hack does is restart the ril service so that should not cause any damage to the hardware
[G4 Android Development] Geckyn:
Haha I know...messed up my first lg phone :D . I still don't know its true variant :D
[G4 Android Development] deltadiesel:
Take it apart. It will say on the motherboard
[G4 Android Development] steadfasterX:
Yes your device IS UsU'd. Why? Well you have used "h811 qfil" files AND you see a secure boot error.

but.... THERE ARE NO H811 QFIL FILES!!! Even WHEN that would be a bad idea if you don't have a h811 mainboard.

The one you flashed have the NAME of h811 but thats it. The guy who created them was either an idiot or don't care about. Well on a REAL h811 it doesn't matters that much as you can overwrite that by using lgup as the h811 has firmwares with ARB 2 available but others like h815,f500,...not.

That's why I write everywhere that using QFIL is incredible dangerous but no one listens..

The files you have flashed converted your device to a ls991 including the debug bootloader of the ls991 which is the heart of UsU.

That's why it even boots. You have a Frankenstein device and the only way to find out what files you need is to disassemble the mainboard or to test all UsU baseband files of all models. Interesting enough is that you flashed UsU files even when you think you haven't UsU'd..?!?

But again: the qfil files you have used blow ARB fuses (one of the main reasons why no one should use qfil unguided).

so let's say your real mainboard is a f500 (which has an ARB of 0). As you have flashed the h811 qfil files your ARB is now 2... of the COMPLETE bootloader stack. That means you can NOT BOOT the bootloader stack of the f500 anymore (as it has an ARB of 0)! Never! Why is that bad? The bootloader stack initializes the hardware so your modem radio which now tries to load the one of the ls991.

Just start SALT to find out your current ARB and model..

Anyways. Find out the REAL model written on your mainboard and flash the correct UsU baseband package would be your best chance to bring back life to your device.

For any further discussion use the UsU unlock thread and consider to read and follow faq 25 there once you know your REAL model!

I HIGHLY recommend to do a SALT basic backup before doing anything though.

Btw: UsU have no such restrictions as you would keep your REAL bootloader stack BUT that part is too late on yours...
[G4 Android Development] bedencic:
can you pay with this app, if card has nfc, instead of using google pay?

https://play.google.com/store/apps/details?id=com.cardsapp.android&hl=en_US

i only get qr code when i choose my credit card.
[G4 Android Development] AerogamingHD:
Would anyone know what this error means??

I unlocked bootloader using official lg method.

I then flashed twrps

Then installed a custom ROM (lineage is 15.1) I understand it's in wrong forum but no one is replying on there.

I randomly get this error (photo)

I also have got a laggy camera and when listening to music it very laggy and unclear.

Is there a way I can fix this? If this ROM is 8.1 should I flash this and see if it works??
[G4 Android Development] tmihai20:
[MENTION=7078206]AerogamingHD[/MENTION]: try this https://www.reddit.com/r/LGG3/comments/3xngrj/the_demigod_crash_handler_strikes_me/. It says there to remove the battery, to let it cool down (if it is too hot to touch) and to remove the sim. I never heard of anything like this until now.
[G4 Android Development] AerogamingHD:
I don't think it's an over heating issue. Because I was not using my phone it was on the side and when I went back to it, it was showing that error.

Also my phone is quite laggy and the camera framerate is shocking. Is there a way to fix that with a kernel or something??
[G4 Android Development] kessaras:
a kernel panic is caused by several reasons. without kmsg or dmesg i can't debug it. so.... dmesg please.
[G4 Android Development] AerogamingHD:
How would I KMSG or DMESG?
[G4 Android Development] AerogamingHD:
Just installed this rom and I can't hear anything while calling how do I fix?
[G4 Android Development] deezid:
Does someone else have problems with no audio over Bluetooth (Nougat version)?

It just routes over to the loudspeaker even if the right profiles (calls, media) are selected.
[G4 Android Development] jorgecft:
How is official 6.0.0 working? Is it safe to update coming from 5.2? The updater doesn't seem to find any update, so I just flash it via twrp? Gapps too or is not needed in such case?
[G4 Android Development] Mogster2K:
I'm not sure whether it's safe to do a dirty flash. Personally, I would do a clean install. I actually wasn't aware there was an official version yet; been running the unofficial version, and it seems pretty solid on my H811. You will need Gapps and the preview version of TWRP. Check the first post for links.
[G4 Android Development] WiZaRd981:
Hello guys.. Can someone tell me the best kernel settings for auditor to just keep temperature low, idc anymore about battery life and perfomance.. Just to have a normal phone.. Tnx and srry for my ENG

I sent an attachment with temperature when is on charging
[G4 Android Development] grantdb:
Default should be good. Temps are higher when charging.
[G4 Android Development] rock2rap:
About Camera mod. after download apk at Post #2 why "App not install" ?

I'm on CypherOS 4.2 by steadfasterX
[G4 Android Development] grantdb:
Using aoscp_h811-6.0.0-CBNP.8102.03.07052-unofficial.zip on my H812 UsU unlocked device because I messed up calling audio on the usu stock nougat. I love this ROM! I get better upload/download speeds than stock for some reason. Ril works better than other ROM's and the default settings for the kernel seem excellent. I did find that the display brightness is very low when hitting power to turn on the display when auto brightness is enabled. I had to reduce video camera to 1080 but that's still great for me. Baseband actually shows too not the usual unknown.

I would be willing to test and post logs for anything if that would be helpfull!

Thanks a bunch for this amazing Oreo ROM!

Cheers!
[G4 Android Development] grantdb:
***NOT A ROM ISSUE PLEASE IGNORE***

No audio for music in default music app mxplayer or poweramp.

Logs are for each of the above in that order.

I think this might be something to do with atmos audio majisk module that I used in other roms.

Thank you

EDIT: This has nothing to do with the ROM it's definitely left over from another ROM. Going to do a clean flash. Sorry for jumping the gun lol.

EDIT2: Clean flash working fine.
[G4 Android Development] feysp:
Can you send this file please

Thx

Pieter
[G4 Android Development] elou-end:
Freeze and green sreen

I have a problem since I have flash, when my phone are hot, I play a game or something like that. My phone freeze and show a green screen. :confused:

Can you help me, thank's ;)
[G4 Android Development] dvaquero:
I found some information about the calls and music Bluetooth issue.

We need to activate the developer options to change the default Bluetooth audio codec. But it seems to fail at trying to change that setting. The official answer from lineageos to the change codec issue is they only allow to change the codec when the device originally brings the aptx codec support by default. But the Lg G4 comes officially with that support by default :(

It seems the default Bluetooth audio codec is too heavy for that kind of connection with the car headset.

There is another setting to change, that's the quality of the streaming. You can prioritize quality vs bandwidth needs.

We can try to change the settings to optimize the streaming quality for connection quality over audio quality.
[G4 Android Development] ThePiGuy:
What device, ROM version, firmware version etc

BT music streaming works fine for me. Is this for BT calling? If so, what makes you think swapping codecs will work?
[G4 Android Development] dvaquero:
Yes, the music sound fine, but the problem is for BT calling, only for earing, not for being eared.

I found some links about that problem in reddit and this forum. But I can't link it right now because i'm a noob for this forum XD.

Search in google:

aptx lg g4 -> first result for me -> this link defines that the lg g4 has the support of the aptx codec by default

bluetooth codec lineageos car fix -> first link -> [KB-Article] Troubleshooting Bluetooth Issues on LineageOS 14 devices -> this post shows typical problems solved by changing the Bluetooth settings

I can't find the link telling about the change of the codec fixes the incoming call sound on Oneplus :(

The information page that I found before was talking about the sound rate was too large for the bandwidth of some Bluetooth connections. I'll try some combinations of this parameter with my car , and I'll post it here the results.

Update:

I've tried different presets without luck :(

It seems that Oreo have change and broke some Bluetooth configs, about this presets...
[G4 Android Development] ThePiGuy:
If only it was that simple ;)

We think it is something wrong in the HAL for our broadcom Bluetooth adapter (the only other device with the same BT adaptor and also running Oreo custom ROMs, the Nexus 5, also has the same issue)
[G4 Android Development] dvaquero:
Can you put here the BT adapter model?
[G4 Android Development] ThePiGuy:
Broadcom BCM4339
[G4 Android Development] levider:
Is chromecast built in TV works on this rom?

Or any other Oreo?
[G4 Android Development] nigxxx:
is it too early to ask if we are going to see P for our G4 ? :)
[G4 Android Development] ThePiGuy:
Simple answer: yes, it's a bit early ;)

Longer answer: maybe in the next few days I'll try building a pure aosp P build. However, as I'm sure you know, this takes time to get it to work so no promises for anything ;)
[G4 Android Development] nigxxx:
i was just kidding, but it will be nice just to try. good luck mate
[G4 Android Development] ThePiGuy:
Hehe...my first time trying this so who knows what the outcome will be :D
[G4 Android Development] dvaquero:
Do we know the firmware version of the chip on the last oreo release?

It's possible that an firmware upgrade can solve this?

https://android.googlesource.com/pl...7e28a2151d78d76076bdc/bcmdhd/firmware/bcm4339
[G4 Android Development] grantdb:
Successful so far so I have high hopes.

?
[G4 Android Development] steadfasterX:
I tried every available Broadcom Firmware and even those directly from kernel.org. As I said a while ago I don't think it's a broadcom firmware issue. It's in the framework of system Bluetooth drivers together with the fact that this is Broadcom. The solution lays in the android code though.
[G4 Android Development] dvaquero:
Found some information about Bluetooth changes in Oreo:

http://blog.bluetooth.com/what-bluetooth-developers-should-know-about-android-o

I'll try to track this issue in your android code....

Update:

This bluetooth issue is an only H815 thing or an lg g4 common thing?
[G4 Android Development] ntnlzr:
google nexus 5 same problem
[G4 Android Development] steadfasterX:
Yea we know..
[G4 Android Development] ntnlzr:
i know about you know, i've just answered to dvaquero :P
[G4 Android Development] Candyfloss478:
Bluetooth and Flashlight issues

First of all thank you so much for making this rom. It looks great and is stable and has completely revived my lg g4.

I have tried this for a month. The only things not working is the flashlight (works on camera but not on quick toggle) and bluetooth which disconnects after 10 seconds or so of inactivity (so if nothing is playing on bluetooth it switches off and then back on again which is a little annoying).

If you could fix these issues that would be amazing but thank you anyway for all the effort so far!
[G4 Android Development] Minto107:
If you would have read this thread you would have already known that installing flashlight tile fix for Kenzo works for G4 as well
[G4 Android Development] theophg:
Bluetooth, Flashlight, and Network

Hello everyone.

Thank you a lot for this amazing custom ROM that helped a lot.

I've been using AOSCP, for now, fifteen days, and have detected some bugs (the two first have already been given in this thread) :

-Bluetooth, as said, is stopping after 10 sec of inactivity.

-Flashlight, working only w/ camera, but can be solved w/ Kenko app so :good:

-and the cell network. Apart from the SIM card not detected, simple to solve with a restart, the phone isn't able to detect the name of the network, and my phone number. I've been in different countries during these two weeks, and even at home, the network name is not detected (I'm European). (the cell connection works well, vocal and data, but the thing is that the ntwk name isn't detected) Does anyone have a solution ? :o

Thank you :)
[G4 Android Development] kessaras:
It's not an issue. It's how our bluesleep driver works and I like it because very often we just forget the bleutooth.

Everyone,

by the way , don't worry about me being away. I'm still here , I just don't develop before September.

When I will start, I will start with Android 9.
[G4 Android Development] aanarchyy:
I have a bit of a question if you wouldn't mind helping me a bit. So i have an lg g4 VS986 with verizon svs, rooted with SALT and installed cypheros. At the moment, 4g data seems to work just fine(youtube, hangouts, etc), but I cannot make or receive calls or texts(Says "Emergency calls only). I am not sure if I am missing something or what, I tried searching the forum and was unable to find anything. Any help would be appreciated.
[G4 Android Development] nigxxx:
When I will start, I will start with Android 9.[/QUOTE]

allright, here we go.... P is coming :)
[G4 Android Development] franky_z:
Still love this phone, still great camera, possibility to change battery (got a 6500mah battery and over 10 hours sot), ir remote. I don't see any phone with so many different specs. It would be great to get Android 9. Thank you so far and for this rom! :)
[G4 Android Development] bonner1928:
Installation questions

Hi,

I'd like to install CypherOS and read this thread for hours - so please don't blame me for asking these stupid questions:

I'm running LOS15.1 right now, but never did any kernel update -> tried it yesterday, but the latest TITAN-version crashed my system. So I want to make sure to install the correct files:

- latest AOSCP rom -> seems to be quiet clear to me :)

- Gapps <ARM64-7.1-X> -> is this still correct, or should it be an oreo version?

- Kernel -> which one should I use (H815)? Is it important to flash it first, then reboot to recovery and flash ROM, or doesn't it matter?

- any other files to update?

Thank you!
[G4 Android Development] deltadiesel:
Use gapps 8.1 arm64

I'm not sure there are Oreo kernels available.
[G4 Android Development] bonner1928:
Thank's for your reply, but that's not what I ment:

I want to install CYPHEROS, so what would be very helpful for me (and others) is a short list of Kernel/ROM-combinations (filenames) which work fine. Installing Titan_kernel_H815_N_LOS_Based_v1.8 crashed my LOS15.1 system and I'm scared of crashing it again...

For example:

1) Advance wipe

2) Install lastest CYPEROS rom and Gapps (7 or 8?), then boot into recovery

3) Install (whatever) kernel

4) enjoy

Maybe step 3 has to be done before step 2?

I've got twrp-3.2.1-0-g4 installed, should I get a newer version?

Thanks!
[G4 Android Development] ThePiGuy:
There is no step 3 any more

The

only

Oreo kernel is Titan, but not the version you flashed. (That's for nougat, hence the issues). Titan is default on all Oreo ROMs anyway so just leave it as it is

Also, gapps must be 8.1 version
[G4 Android Development] bonner1928:
Wow...you're fast :good:

So installing the CypherOS-Rom includes the kernel, right?
[G4 Android Development] ThePiGuy:
Yes it does

Just flash and enjoy ;)
[G4 Android Development] Minto107:
Yeah. It always used to be like that. All Oreo ROMs are powered by Titan kernel and there isn't any other kernel available(yet?)
[G4 Android Development] gh7531:
Hey together,

I tried installing AOSCP on my h815 (G4 int.) but after the first boot the setup process (pixel-something?) crashed after the LockScreen Settings. I could choose between "restart the app" and "wait" but neither of it worked and the setup process started again.

I'm coming from an AICP Nougat build, using the latest TWRP (3.2.3) preview. I tried both offical AOSCP 2018-07-17 and unoffical 2018-Jul-03 versions with ARM64 GAPPS 8.1 pico.

Before flashing AOSCP I did both, a factory reset and a compete wipe of the internal storage.

Steps I took:

1. Titanium Backup and TWRP backup. Shouldn't cause a Problem.

2. Booting to TWRP and doing a Factory Reset for a clean flash since I'm coming from AICP Nougat.

3. Flashing AOSCP, GAPPS and Magisk 16 one after another. I also tried flashing only the ROM without GAPPS and Magisk.

4. Pressed the Wipe Cache/Dalvik and did another Factory Reset

5. Booting the device and tried setting it up (Language, Name, Location permissions, LockScreen Settings ...) and after this step, during some "Update... please wait" screen, the app, (I don't know if it is a specific app or part of the Launcher?) keeps crashing and I have to start the setup process all over again.

I'm sorry if did something obvious wrong but I can't figure it out, so please tell me what I could try to do :(

Thanks a lot.

Edit: Tried to make my explanation more clear
[G4 Android Development] fi5z.x9:
Yo.. Your explanations isn't very clear. However, I usually follow this steps.

1. Reboot to recovery (twrp) 2.Wipe data, delvik cache, system, cache. 3. Flash rom + gapps (select option for add another zip, so they flash consecutively). 4. Boot to system (finish some basic setups) 5. Reboot to recovery and flash Magisk. 6. Wipe cache and delvik cache. 7. Boot back to system and restore apps using TB. ☺

Hope this helps.
[G4 Android Development] absinth:
Hi guys, now i have the H-ROM G4 H815 (sw VERSION v29a) and I want to try this CypherOS . To install the ROM can i do the wipe directly with TWRP and then install the ROM or there are other thing to do?
[G4 Android Development] tmihai20:
[MENTION=221383]absinth[/MENTION]: you should also have the Oreo corresponding TWRP version if you want to have the correct time displayed in TWRP.