yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] n0ri:
Hey [MENTION=5461026]kessaras[/MENTION] and [MENTION=3208754]codeworkx[/MENTION]... Thanks for all your Work in ihr G4 :)

My question beside Thema Rom itself is:

- ist there a source for 29A Firmware which ist needed as u said in topic?

- what about Modem? Do i need special one? (Because on Most other Roms (except original LG one) my signal strenght sucks anderen jumps from 0-100%)!?

- any 29A Rom i could flash for Firmware/bootloader/Modem?
[G4 Android Development] Lurensu:
Try to reboot: sometimes it's detected, other times it's not, I think it will be fixed in the next release.

Could anyone tell me how to use google assistant with the home button? If I long press it opens my google feed, but not assistant (maybe I should move the Google app to system?)

I also have a problem with trusted face in smart lock: I haven't the option (it think it could still be broken in Oreo 8.1)
[G4 Android Development] cartman_73:
I tested your issue and, for me, it didn't happens.

I take four shot with flash in auto, off and on mode and all is normal.

I'm on 20171230 reflashed over the previous version with wipe cache, and art and system only.

Did you have a clean installation?
[G4 Android Development] Minto107:
Trusted face work 100%, Assistant also works correctly. It worked out of the box for me, I only needed to set it up during setup wizard
[G4 Android Development] Lurensu:
Maybe I flashed the wrong gapps? (I've chosen Pico)

Which gapps have you flashed?
[G4 Android Development] Minto107:
Stock as always ;)
[G4 Android Development] kessaras:
https://images.techhive.com/images/.../itw/2011/11/10/uefi-stack-100516590-orig.jpg

firmware is not part and shouldn't be part of a rom.

firmware partitions are in kdz in LG case because thats how they want it and they originally get flashed when we flash a kdz.

extracting kdz we can flash the partitions we choose to, on will.

firmware = modem, bootloader . bootloader = many more partitions.

OP sais minimum requirement 29A. This means that you find the link to 29A firmware flashable zip in g4 community. In freedom rom thread 2nd post, or cleverly browse into [MENTION=5545101]steadfasterX[/MENTION] download server.

Stead has everything there.

Signal is late to respond in stock based roms so you think you have more. That's all.

Signal is carrier and hardware (modem) related.

If drivers work correctly you have signal and data and the phone can switch between 4g,3g,2g,g successfully. So you "have" or "don't have".

If signal is low its the provider's problem to solve or phone hardware

EDIT:

in this case of Oreo here that sometimes you boot without having a sim (in most cases it has a sim), i don't know where is coming from.

Lack of experience. But eventually i will understand why.
[G4 Android Development] n0ri:
Perfect explanation :) Thank you [MENTION=5461026]kessaras[/MENTION]
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
I have used CM / LOS for so many years that I don't know how other roms (incl. stock) handle WiFi and Mobile Data, so maybe my question doesn't belong to here. But maybe someone can explain nevertheless: In tiles I am connected to WiFi as well as Mobile Data. In developer options "Mobile data always active" is off.

My expectation is that software recognizes that I'm connected to WiFi and turns off mobile data, but it seems it doesn't. It looks like both are connected and on. Is this correct?
[G4 Android Development] Minto107:
If you have 4G then it's normal as LTE is always connected regardless of that switch
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
I could have 4G, but I have set my preferred network type to 3G.

The reason for this is that I've noticed much battery drain when I am at home and connected to 4G. This was noticed on LOS and now on AOSCP I also have much battery drain. Setting preferred network type to 3G solved battery drain at LOS but not at AOSCP.
[G4 Android Development] Minto107:
Yeah 3G solves drain for me as well ;) at my home 4G signal is really poor so it drains hell out of my battery
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
But then it is correct that WiFi and Mobile Data are both active?
[G4 Android Development] Minto107:
With 3G? Nope. Mobile data turns off after a min or so
[G4 Android Development] cartman_73:
I flashed the 20171230th version over 20171229 and I have lose my TWRP.

Do anyone else have this issue?
[G4 Android Development] Minto107:
Not really possible. There is no recovery.img inside of ROM zip. Must be something else
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
Mmmhh... Maybe I understand the symbol wrong. I have switched off WiFi. Then symbol of Mobil Data changes to same symbol plus "H". When turning on WiFi "H" is removed but symbol is still black and not grey. Same for you?
[G4 Android Development] Minto107:
I checked in SIM settings, it says that mobile data is disconnected. For me it's enough ;) check it yourself, maybe it's software bug or so, 8.1 is quite fresh. I've found pretty annoying bug already
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
Thanks for hint. It's disconnected there for me, too.
[G4 Android Development] cartman_73:
I didn't believed too but it was happened.

Anyway, I flash again and that's all fall.

Happy New Year to everyone from Italy.
[G4 Android Development] Minto107:
That's weird then. Maybe your recovery got corrupted or something like that
[G4 Android Development] RogerBoy123:
The latest december 30th Oreo build is oreo 8.1, right?
[G4 Android Development] obvious:
Yup
[G4 Android Development] polfrank:
Check in developer options. There is a setting that allows mob. Data to be turned on even when WiFi is connected. This happens to make a faster transition from one to the other. I think this is by default turned on.
[G4 Android Development] obvious:
[MENTION=5461026]kessaras[/MENTION] do you use the adreno blobs from nexus 5x 8.1 factory image? I wonder if they should be the latest for adreno 4xx?

https://developers.google.com/android/images
[G4 Android Development] kessaras:
they are the same since 4th of september when genesix updated them from nexus 5x. didnt change them

https://github.com/TheMuppets/proprietary_vendor_lge/commit/ecfd6ce7313a53be171c8375fb5837b6efeb3c25
[G4 Android Development] obvious:
Ah ok. I think there should be newer. According to http://vulkan.gpuinfo.org/listreports.php?devicename=Adreno (TM) 418

...for the future
[G4 Android Development] kessaras:
i dont understand how and where they get their blobs.

They are not in github or anywhere. I only see vendor .img files scattered in android file host.

When i have time ill download their .img and take a look inside. But i don't get it why they dont share them like everyone else.

And where do they get them ? Nexus 5x still gets official updates from Google ?!
[G4 Android Development] obvious:
I don't get it either. As you see, Xiaomi mi4c has adreno 418 and android 8.1
[G4 Android Development] Usraek:
For those who care, I have got SafetyNet to pass in both the Nougat and Oreo version of this ROM.

Does this ROM detect fast charging properly? My lockscreen states 'Charging Slowly' on Nougat.
[G4 Android Development] RogerBoy123:
(PLEASE READ EVERYTHING!) kesseras I need your help! So I was installing your new Oreo rom like this:

- I wiped System, Cache and Dalvik/ART Cache

- I installed your latest 30 December Oreo ROM.

- I installed open_gapps-arm64-8.1-micro-20171228

- I installed Magisk-v15.1(1510)

- I rebooted.

When the ROM started, my phone-app kept crashing and the android system stopped. Then I pulled out the battery, then I rebooted. It was stuck on the boot animation, so I pulled out battery again, then rebooted back into recovery mode. When I was in TWRP recovery again, I tried to reinstall the ROM like this:

- I wiped System, Data, Cache and Dalvik/ART Cache

- I installed your latest 30 December Oreo ROM again.

- I installed open_gapps-arm64-8.1-micro-20171228 again.

- I installed Magisk-v15.1(1510) again.

- I rebooted.

But this time it didn't even boot at all. It rebooted straight back into TWRP recovery!!! Now it doesn't matter what I do in recovery mode, it will just reboot back into recovery ALL THE TIME!!!

Everytime I try to install the ROM it now says 'Warning: No file_contexts'. I bricked my G4! What is happening? :crying:
[G4 Android Development] steadfasterX:
They extract them from the phone via adb or you can get them from the kdz.

Why they don't share? Again muppets is doing illegal sharing of proprietary blobs and maybe the nexus devs CARE and so don't share.

Which exact TWRP version?
[G4 Android Development] KingKron:
I had same issue yesterday so I restored with lgup and kdz file. Re-flashed twrp and installed Oreo again. Worked fine
[G4 Android Development] cartman_73:
Probably, It would be the only way.

I use the same method for a resurrection remix flash
[G4 Android Development] siiik_:
I've read 20 pages of this thread and nowhere does it talk about this ROMs battery usage. Could anyone say it it spends + or - battery then LOS 14.1. Thanks :good:
[G4 Android Development] straightup:
[MENTION=5545101]steadfasterX[/MENTION] could you please tell me which exact TWRP version is the best to use with the Oreo ROM? Thank you!

And Happy New Year to all of you!
[G4 Android Development] RogerBoy123:
I have TWRP version 3.1.1-0
[G4 Android Development] kessaras:
The no file context is nothing. There is a file context but in sepolicy not in root dir of the device tree.

Anyway. Why do you flash magisk ?

Oreo 8.1 is 2 weeks now, it's a new rom. There is no stable root method out there.

I don't know exactly what you did wrong but now wipe system and data partitions only in advance TWRP wipe menu and flash rom , gapps x64 ofc and reboot. That's all.

Don't flash root if you dont need safetynet pass
[G4 Android Development] cartman_73:
Update It to 3.2.0 and retry
[G4 Android Development] RogerBoy123:
But I only see the newest version is

twrp-3.1.1-1-g4.img

I don't see anything newer. Where can I get 3.2.0 for the LG G4 H815?

---------- Post added at 12:07 AM ---------- Previous post was at 12:04 AM ----------

But I also tried to downgrade back to nougat, I even tried a different ROM, but it still boots me in TWRP all the time instead of system!
[G4 Android Development] kessaras:
Then you didn't do what you said you did.

You either wiped in fastboot either wiped in rom.

Anyway. Format data and wipe system.

Format will fix the boot in TWRP. And yes 3.2 is latest. And even newer than that. Where do you search for TWRP ?

You don't use the thread ? [MENTION=5545101]steadfasterX[/MENTION] download server has everything you need.

Edit:

And if format doesn't fix it then flash stock LG recovery instead of TWRP and reboot. Fixed.
[G4 Android Development] Termehansen:
I guess he means the flashlight. So far you have not stated any change on this issue... I would love to test and change for this ROM, but flashlight is a must have for me, so until a solution to this is found I will stay at LOS (without a developer now [emoji22] ).
[G4 Android Development] kessaras:
and if it was working then something else would be the problem.

maybe google assistant dont connect to the car ECU to control it through a phone app like KIT in Michael Knight series.

I will take a look at it this week for the next Sunday update. Until then use Snapdragon Cam. Works better with our phone.

sorry... flashlight is something i cant add to aoscp (alone!).

the framework is messy from the many commits added and removed again and again since 2 years that nougat came from google.

To add that i have to take a pure code (clean) with nothing on, from google and add 3000+ commits .......... not happening..... its easier to develop VertexOS than add flashlight toggle here

Edit:

I found the cause. It's the auto tile creator fault.

In aoscp instead of adding tiles manually they added a coding for auto tile creation.

That auto tile creation doesn't show any error if a tile is not added because the code is correct. Who knows why flashlight is missing...

So,

I have to remove the auto tile creation (that's easy , I revert that commit). But I don't know after that where the error will hit so I will add all the tiles one by one while checking conflicts or missing parts.

Expect flashlight to be fixed soon.

And no comments here about other roms or devs.

The difference unofficial with official is only that the official has access to the org repos when the unofficial has to fork them to make changes.

-------------------------------------------------------------------------------

[MENTION=4928665]Termehansen[/MENTION] , no luck with the flashlight toggle in this rom... sorry...

reverting the renspossible commits caused way too many errors and it was since april of 2016.

Since april of 2016 aoscp had no flashlight toggle and there are more than 3500+ commits to take care of. So can't fix that toggle.
[G4 Android Development] lbnd:
Hello and thank you for the good work kessaras!

I've just switched from LOS Official (h815, default kernel, 20p bootstack, Magisk, OpenGApps) to AOSCP (again with default kernel, Magisk, OpenGApps but with 29a bootstack). Booted successfully, no heating or apparent battery drain whatsoever at the moment. Two issues I've found:

- The phone can't find my Bluetooth speaker. (I did make the speaker visible.) I have no other Bluetooth equipment to test with. It worked with LOS though.

- Some Play Store apps like "Footej Camera" (really like it), "Forvo Pronunciation Guide", "Yandex.Navigator" do not show an install button. I've yet to test installing from apkmirror, and I'm aware of prior messages here saying these are permission issues.

A logcat from when I fiddled with Bluetooth: https://www.dropbox.com/s/xo6n9qgs71ku5h6/201710081357.txt?dl=0 This is my first logcat ever, I used the command "adb logcat -v long > 201710081537.txt", feel free to suggest a better way.

Edit: Alright, Footej works, installed from apkmirror!
[G4 Android Development] tulen_kobi:
I want to share my weird experience with the previous build. Not today's one. I unlocked bootloader and flashed the TWRP and nougat firmware and the ROM+mini gapps afterwars. I let the google to download all my apps and than I decided that I will play with the google camera settings. On one setting that I cannot recall now(I think that afterwards I checked full support in options ) the phone rebooted on taking the photo. Afterwards the phone booted fine so I decided to change another setting in the camera, but this time the phone not only rebooted but it did not boot at all. I was stuck at the boot animation. So in TWRP I decided to do a factory reset but it did not help, the phone was still stuck at the boot animation. I was scared that I am experiencing the bootloop issue so I reverted back to stock and now phone works fine. I absolutely do not understand what happened and I unfortunately do not have any log of it.

EDIT:

When I was at the rom I was unable to connect to my mi band 2 using MiFit, maybe it is fixed on the newest build.
[G4 Android Development] Termehansen:
Is it only the toggle as such that is not working or also flashlight apps and widgets?
[G4 Android Development] kessaras:
Test this kernel and tell me if it works. i dont have any bluetooth equipment to test it with.

extract the zip and flash the .img as boot.img in twrp.

no flashlight toggle at all.

you cant use the phone to see in the dark unless you use the camera.
[G4 Android Development] lbnd:
Doesn't work. And for some the reason the log is huge now (tens of thousands of lines just from the last few minutes where I fiddled with Bluetooth again.)

Log (tar.gz): https://www.dropbox.com/s/eytuwh5r8lukw7y/201710090052.txt.tar.gz?dl=0

Thank you.

(I also tried with no Magisk and wiped cache.)
[G4 Android Development] kessaras:
today i built AOKP and VERTEX. it looks like all AOSP roms are like that on our nougat. Flashlight toggle is missing and bluetooth connects only to random specific devices.

Maybe i will move on to a Los based rom in the near future.

Although AOSP are the best stable roms and battery holds for 2 days, we dont have good compatibility to all phone features and we no longer have; 1. official support and 2. nougat support as everyone moved on to Oreo.

EDIT:

There is no other rom more stable than this one out there for G4.

Maybe i will not stop it, but i will keep the updates to a rarerer rate. Maybe every 2 weeks instead of 1.
[G4 Android Development] tulen_kobi:
Is there anything that I should know before attempting to build it?
[G4 Android Development] kessaras:
hi. the aoscp repos for our phone don't work anymore they r outdated.

you must use the ones from our org in op link (branch aoscp and kernel nougat-dev-a)
[G4 Android Development] marn3us:
Thanks for all your work, updates with less frequency is still great, take your time! :)

I also hope you will still be developing for G4 when AOSCP 5 will release, I'm sure you will be much better at fixing bugs and improving performance than the AOSCP team ;)
[G4 Android Development] Mulchergun:
lost dt2w

hey guys i really don' t nknow why my dt2w is f****d, please help me!!

i really need dt2w because the position of the power button, so if anyone knows how to solve (even modifying with a root explorer some file) let me know
[G4 Android Development] kessaras:
settings -> gestures
[G4 Android Development] Mulchergun:
Is active , if I use an app for the kernel management it tells me that my kernel doesn't support wake gestures and I have the same result with titan kernel & others, please help me I'm m desperate and I don't t want to thrash this phone, I performed also an hardware test

---------- Post added at 04:19 PM ---------- Previous post was at 04:15 PM ----------

It doesn't work, i.' be tried also with kernel management programs and it told me that my kernel doesn't support wake gestures, same result with various kernels, please help me I love this phone and I constantly follow your work, thanks in advance
[G4 Android Development] kessaras:
help how ?

in sources the double tap is enabled. If it doesn't work, it's a hardware problem.

that was old bug. i have fixed it here. it was an overlay problem. when waking screen for the first time, the phone tried to load multiple overlays that were not there.

And the "driver" for double tap is in kernel and works. The switch to enable it in all Roms is in "g4-common". Of course its enabled. Nothing i can do to help, if clean or (dirty, it doesnt matter) flash doesnt work then you have a hardware problem.
[G4 Android Development] Mulchergun:
Is like I miss some drivers.

Also sometimes when I press power button it appears a glitchy screen at super low brightness.

In he test everything works fine

---------- Post added at 04:31 PM ---------- Previous post was at 04:22 PM ----------

Anyways thanks for everything, i'll try to find out the problem, I've really tried everything so I'll try harder :)

---------- Post added at 04:21 PM ---------- Previous post was at 03:31 PM ----------

hey, i' ve unmounted screen + digitalizer and everything seems fine, like in the result of the test i' ve done in mini os, do you have any "software idea" of what is not working on my lg g4... for example i' ve noticed that in my root folder there isn' t any ic2 ecc subfolder in

---------- Post added at 04:21 PM ---------- Previous post was at 04:21 PM ----------

hey, i' ve unmounted screen + digitalizer and everything seems fine, like in the result of the test i' ve done in mini os, do you have any "software idea" of what is not working on my lg g4... for example i' ve noticed that in my root folder there isn' t any ic2 ecc subfolder in
[G4 Android Development] Brandon9231:
Clean flash this ROM or switch to a different one to know if it's a hardware issue or not. That's a common issue with G4s though, and AFAIK there's no fix, you'll need a replacement phone if it is the hardware
[G4 Android Development] Mulchergun:
i' ve tried other roms with the same result ever
[G4 Android Development] Brandon9231:
Then it's the hardware issue. Sorry but there's nothing left to do but get a replacement if you really need dttw. Maybe try the quick circle case so the screen turns on when you open it? Kind of redundant since you're on an aosp ROM but that's the only other way to turn the screen on without the power button
[G4 Android Development] kessaras:
ok , forget dtw. find an alternative if you dont like using the button.

use wave to unlock.

ye

https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree&hl=el
[G4 Android Development] RogerBoy123:
Format didn't work, but if I flash stock recovery, then does that mean I can't install custom roms ever again?
[G4 Android Development] steadfasterX:
my latest preview builds. Custom-N is fine.

That's the reason for the TWRP bootloop.

Use the latest preview version and its fixed.
[G4 Android Development] cartman_73:
I checked the official site and there is only 3.1.1 what you said but I sure that the latest is 3.2.0.

Anyway, here you are.

http://droid.binbash.it:8008/TWRP/
[G4 Android Development] steadfasterX:
Wrong url. Pls folks read the official TWRP thread and choose the right version.
[G4 Android Development] kessaras:
......................................................

now fastboot flash twrp again. who said you can't ?

move the discussion in twrp thread. i want it clean here and i also hate it to ask moderators delete posts.
[G4 Android Development] sperelli:
i falshed supersu 2.82, not interested in safety net. root is working fine, yet i think TiBackup not freezing apps can be related.

i have ”charging" and "slow charging” according to specific charger used.

problem found: phone didn t charge once reached 3%, a reboot solved.
[G4 Android Development] Monkeypox95:
Happy new year to all !

I confirm a previous post. I dirty flashed (wiped system+cache+dalvik) the 30 Dec version onto the previous . The gapps didn't survived. I flashed again the gapps and no success. I had to clean flash all and everything is ok.

As far as I'm concerned, I use a lot the WiFi hotspot and it doesn't work here in Oreo. It activates properly with the good settings but my other devices don't see the network.

Have a good day!
[G4 Android Development] kessaras:
hotspot is a tough one. will need time to finish with other bugs first more important than hospot and then ill look into it.
[G4 Android Development] f4lkon:
Went from lineageos to aoscp. Did a clean install with usual steps. Used steadfasterX latest twrp from

http://droid.binbash.it:8008/TWRP/custom-n/

and

aoscp_815-5.1 latest 8.1

Magisk-v15.1

open_gapps-arm64-8.1-pico

I have to say, I love it. I did not excpext such a stable build this early. I had not one single crash so far. My only issues were that I had to reboot twice because no sim was found and after the first boot the whole ui was very laggy. The only thing I miss from lineage is the double tap on the home button to go into standby. I know I can double tap the status bar but its not very comfortable for me. Since I avoid using google services I cant post this into the aoscp g+ group. Ok but since this is a dev thread here is the stuff I really want to say:

I noticed that the app Luna uses a noticeable amout of battery. Looking at the logs with level error and warning I see that the ThermalEngine is very noisy with following message:

ACTION: CLUSTER - Setting CLUSTER[1] to 1234000

I get this message every 10 ms
[G4 Android Development] niccotaglia:
How do I disable the QS quick pulldown?
[G4 Android Development] tulen_kobi:
Please upload the whole log.
[G4 Android Development] kessaras:
Thermal is only informing what it does. It's how it works.

In all phones.

Luna doesn't spent a lot of battery , those stats are perncentages of the drain. It's just that you have slightly less screen drain because of my kernel so if the biggest percent is lower it looks like other things drain more , but they don't.

Double tap will be added. Oreo is only 2 weeks old

In backup settings there is a reset switch for that. Careful you don't press the wrong reset and wipe the whole rom and result in bootloop