yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] kessaras:
Don't know guys, i'm no magician (sadly). I don't know what you maybe doing wrong.

no. on dirty flash you also need dirty flash gapps. grab a pico always in your internal or external sdcard and always have them there to easy dirty flash/update within a minute.

Only the official and only using the OTA there is able to survive. (for now)

>>>> News <<<<

Updated the f_fs (function fs) to fix some fs errors i ignored since we booted to O.

https://gerrit.cypheros.co/#/q/stat...2+branch:oreo-mr1-release+topic:"Update+f_fs"

From the next build , O will be even more stable and smooth in the UI than it already is.

I will pass the fs update to N too.
[G4 Android Development] openWeb74:
Did you do anything special... I installed 29A via ZIP...

After that - and first quick wifi-test - i got back to twrp, wiped /data, install the 1801-build and the google-apps...

After boot, wifi-problem is happening...

Perhaps in german, PM?
[G4 Android Development] DosenHatti:
I came from V29 'Stock', open Bootloader. Did a clean flash of 0114 first and afterwards dirty flashed to 0118 and 0119 (deleted system, dalvik, cache only) and pico gapps. No further action. No magisk, no su. Runs like a charm except 'simcard not found' every now and then. 2nd boot works inclusive simcard detection in general.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] Lurensu:
Well, I've got a quite strange behaviour with charging:

With the original charger (1.8 A) and every cable I've tried so far, it won't charge at more than 400 mA. If I enable quick charge in kernel adiutor, it goes up to 700~900 mA for like 5 seconds, then it collapses to about 60 mA.

In the "Ampere" app the voice "max USB curr." says 500 mA.

I don't know what's wrong with it, should I try to clean flash? May it help?
[G4 Android Development] openWeb74:
So, simple "factory reset" and then flashing it?
[G4 Android Development] DosenHatti:
I deleted system, dalvik, cache, data

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] kessaras:
Who knows ? im not experienced with hardware stuff.

Charge is hardware related. cables, motherboard and others connected on motherboard. In kernel i can only change regulator things.

blobs could make a difference but are the same with N.
[G4 Android Development] Lurensu:
Ok thanks, I'll try to clean flash when official is out, probably it's the only thing I can do!
[G4 Android Development] openWeb74:
(re-) tried it with 0114 and also 0122... SSDD... Now there at least is an error: "Not in range"... Strangely the base Rom IS in range and while entering the password the mobile IS in range...

I dont really get it :(

BTW: never had seen this: is it "normal" that the macaddress of my wifi is 00:00:00:00:00:00 while not beeing connected???
[G4 Android Development] obvious:
No. I'm pretty sure you'll need to recover it. Not something I know how to do offhand

Edit: Could try something like https://play.google.com/store/apps/details?id=net.xnano.android.changemymac but you'll ideally need the original WiFi Mac address. Maybe it shows up on a clean flash of stock rom?
[G4 Android Development] kessaras:
you deleted the file that stores the mac address in /data. propably thats why you have those issues to begin with.

/data/misc/wifi/ folder

you did a ****ty clean up. when we say wipe data we mean wipe data Only. Advance wipe in twrp and select only data.

Same goes for when we say delete only system. We don't start cleaning up whatever meets the eye..........

do this in terminal:

adb root

adb remount

adb shell cat /data/misc/wifi/config

You should see your mac address normally. If you see zeros, then you have to find whats your real mac address manually and write it there.

use SALT of [MENTION=5545101]steadfasterX[/MENTION]

export your misc partition.

Open it with a hex editor (me on linux i use ghex)

find your mac address.

It should be pretty obvious whats your mac address into this chaos of hex values. your address will be like this: 5c:a9:00:00:00:00 anyway 12 hex values.

Some hex editors are easier because they have a preview and they show you a translation of the bytes.

When you find it do this:

adb root

adb remount

adb shell

nano /data/misc/wifi/config

paste there your mac like this :

cur_etheraddr=5c:a9:00:00:00:00

replace the above mac with yours ofc. press control+O to save the file (control+o saves in linux terminal, i dont know about windows)

control+x exit

adb reboot

to reboot the phone and its fixed.

And never format everything again. When we say you wipe data** we don't mean that you should actually clean up everything LMAO

EDIT:!

Steps are easy and only 3. It's not hard.

It's just that when you will see how assemply language is like for the first time, you will be like that O_O

Skip that look in the face and search for your Mac address in there.

It's the only way to fix it. Restore, flash kdz , or whatever will fail to fix it.

LAST EDIT:

You may had deleted this some days ago or even before than that. Stock based roms grab the Mac address directly from misc partition so they don't have this problem unless you wipe the misc partition.

Doesn't matter. Now you will fix it and you won't have any wifi issues on any rom.
[G4 Android Development] obvious:
What he said ^
[G4 Android Development] munkeyhead:
If I had more time to devote and this were a back up phone, then I would love to stick with and help development. But this is my daily phone and like I said if WiFi HS is absolutely necessary for my work. I was really just trying to compliment your work. But I'll go sit down now. Sorry
[G4 Android Development] 99mike199:
It's because of kernel. Can it be used with stock LG kernel?
[G4 Android Development] openWeb74:
Thanks a lot!!!! I had the mac in some logs of my homeautomation, so no need to flash something... Edited file directly while new setup... Wifi is back...

Really sorry about that noob problems ;)
[G4 Android Development] DosenHatti:
I played a little with my device and found out that the 'sim card issue' seems only to come up when I 'restart' the device. After 'proper' shutdown and start the sim card was always found. Might help to get things sorted.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] Monkeypox95:
With a restart I had no issue twice in a row. Think it is not really related.
[G4 Android Development] McRoy:
I didn't understand well the steps to install OREO from stock, once I have unlocked bootloader
[G4 Android Development] openWeb74:
Sorry for my stupid problems again, but the setting is not stored permanently... After every reboot i have "cur_etheraddr=00:00:00:00:00:00" in the config file...

BTW: the bluetooth mac (/data/misc/bluetooth/bdaddr) is also 00:00:00:00:00:00

any chance to put these in, lets say an init-script:

echo "cur_etheraddr=12:34:00:00:00:00" > /data/misc/wifi/config
echo "56:78:00:00:00:00" > /data/misc/bluetooth/bdaddr

???

Ok, i AM f***d... i really am ready to try anything... first of all i tried to put the g4 in download mode, and flashing it with the latest MM version 20g to start over... BUT... After starting to flashm, phone reboot from download-mode into recovery!

It it possible to fix anything with simply reflashing the 29a zip? When this rom HAS the right macs and everything works, is it possible to simply copy some files over!?
[G4 Android Development] DosenHatti:
After unlocking BL I installed twrp for G4 and after that the N zip-version. look in that threat how to. When kessaras came around with Oreo, I clean installed this version. And happy running Oreo since then. :)

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] #ApolloLiteProblems:
Download TWRP (you can search for the LG G4 on the website). If you're running on Marshmallow LG made it hard to keep TWRP. You'll need to do a full system wipe (don't remember adb commands, should be easy to find) and then flash the ROM in adb. Finally install TWRP as a recoveryimage ofc (again in adb) and reboot. From there you can go into TWRP and flash Gapps or anything else like Magisk.
[G4 Android Development] tambukey:
Did you try different cables? I've found some cables just don't cut it. Also hold the cable in firmly, I gave a slight push up on it, like pry it towards the screen to ensure pins connect. I don't know how the pins are set up, but my port is getting bad and if i let the chord sag, my charge rate drops to less then 500mA, if i pry it upwards it'll return to 1A+.
[G4 Android Development] Lurensu:
I've tried, but nothing changed...

It happened a couple of times that it charged at 1.6~1.7 A, but completely random, I'll try holding the cable more firmly, but I really don't get it (on Nougat V29A it was fine)... Thanks
[G4 Android Development] #ApolloLiteProblems:
I have a really old cable that still charges my phone in 70 mins.... Are you using a Qualcomm Quick Charge 2.0 power brick?
[G4 Android Development] tambukey:
Yeah the holding it is just cause mine is old and I've definitely yanked cables out of the phone so my Port sucks.

[MENTION=5461026]kessaras[/MENTION] I know you've said before that the addon.d script is broken. Is there any more info you have on that, or is it that we won't be able to get a survival script to work at all?
[G4 Android Development] Lurensu:
I'm using the stock charger and it has always been fine, charging in about one hour and a half (now it takes about 4 hours). On slower chargers (like 1A) it almost doesn't charge at all.

But since this is only happening on my device probably I've messed up somewhere
[G4 Android Development] #ApolloLiteProblems:
Try clean flashing and maybe buy a new charger?
[G4 Android Development] cyberdust:
Hi, I'm using this ROm since about a week and I just updated to the Jan 22 build, and I noticed that my phone got really hot. When I looked in a task tool, the rild process ate about 20% CPU alongside the google messages app with ~14%. However I still had receiption and restarting rild fixed the issue for me. I attached a radio log with the errors and a screenshot with currently running processes. (If this error happens again, I'll tell you about it)
[G4 Android Development] Lurensu:
Yeah I'll try clean flashing...

I don't think the charger is the issue since it's slower on every charger I've tried
[G4 Android Development] Schwarzie2k:
One Question: If i flash this rom, do i have ti wipe and flash my phone everytime an update comes, or is there some OTA functionallity once the Rom is installed for further upgrades?
[G4 Android Development] fi5z.x9:
>>>> News <<<<

Updated the f_fs (function fs) to fix some fs errors i ignored since we booted to O.

https://gerrit.cypheros.co/#/q/stat...2+branch:oreo-mr1-release+topic:"Update+f_fs"

From the next build , O will be even more stable and smooth in the UI than it already is.

I will pass the fs update to N too.[/QUOTE]

Thanks. Looking forward to this on your nougat rom. Pls hope it won't affect battery usage. Your nougat rom is my daily driver and I'm all'bout saving as much juice as i can. Thanks once again.
[G4 Android Development] cartman_73:
This is unofficial build.

You only wipe system, cache, art and then flash rom, gapps and root.

5 minutes of work. :)

---------- Post added at 08:53 PM ---------- Previous post was at 08:53 PM ----------

Try to clean the usb port
[G4 Android Development] sberta:
You can dirty flash the new version+ Gapps. No OTA for now
[G4 Android Development] kessaras:
i said it will work on official only

its slower but not so slow. for me now is 1h 40min 0-100 and on N it was 45min 0-100.

ril wont get fixed. its already fixed. i fixed all its bugs and its switching flawlessly without errors. if you read what i have already said before about this strict O security and see your log too, you will understand. it sais:

Could not create table attempt to write a readonly database

Clearly. And i got no idea how to fix this since its no error exactly. Even strace doesn't have any info about it to help me fix it. for that reason [MENTION=7026648]AlaskaLinuxUser[/MENTION] made a restart ril app and link is in 3rd post.

ota only official , when its ready. unofficial dirty flash manually rom + gapps pico at least for the update.

fs = file system. it can't affect battery unless i did a crap work
[G4 Android Development] Minto107:
Actually he should download it from G4 database hosted by sted(his TWRP btw) and flash it with fastboot flash recovery *filename*.img and then just follow typical fashion flashing procedure ;)
[G4 Android Development] #ApolloLiteProblems:
When flashing TWRP on LG android M it doesn't stay so you have to flash the ROM then TWRP.
[G4 Android Development] Minto107:
Or you can do it other way(as I did when I unlocked it on 6.0)

fastboot boot *filename*.img then flash it in TWRP to recovery partition and it'll survive ;)
[G4 Android Development] #ApolloLiteProblems:
Oh I tried that and it didn't work so I flashed to boot partition, flashed LOS from TWRP and then flashed TWRP to recovery
[G4 Android Development] kessaras:
In the last build you will also find back the live wallpaper picker.

Fixed f_fs error negative value -512.

Partially fixed the wake up issue.

Testing regulator set closer to original (up 'ed it).

Up to now here everything is smooth and stable.
[G4 Android Development] obvious:
I guess you saw the same error in February 2016 (ie pre Oreo) on moto x xt1575 @ https://pastebin.com/xYHuU83b ?
[G4 Android Development] kessaras:
yup, but in N and older we could add sepolicy to allow it. Now in O ril write is in the neverallowpollicies
[G4 Android Development] McRoy:
Thanks man. Then

So full steps:

Unlock bootloader:

http://developer.lge.com/resource/mobile/RetrieveBootloader.dev

Install TWRP and root, form cmd on our abd folder:

adb reboot bootloader
fastboot flash recovery TWRP-LG-H815.img
Fastboot boot TWRP-LG-H815.img
adb reboot recovery (It should appear TWRP)
Install SuperSU.zip and reboot

Installing ROM

adb reboot recovery (To enter in TWRP recovery)

Select Wipe and “Swipe to Factory Reset”

Back to main menu and Install AOSCP.zip

(To install ROM)

Install TWRP again

adb reboot bootloader
fastboot flash recovery TWRP-LG-H815.img
Fastboot boot TWRP-LG-H815.img
adb reboot recovery (It should appear TWRP)

Install GAPPS

adb reboot recovery (To enter in TWRP recovery)

Install GAPPS 8.1 STOCK ARM64 like .zip

Could you check the process? Maybe will be usefull to other users!
[G4 Android Development] Minto107:
Not flash recovery but boot recovery.img and flash recovery in as Apollo said it won't flash it
[G4 Android Development] kinuris:
This is off topic (a little bit)

You made a really great job with your Nougat versions of AOSP, LOS and RR, [MENTION=5461026]kessaras[/MENTION] and team, and you are putting a great effort and time in get AOSP Oreo working(and I can imagine after that you go over LOS an RR, when the main developers progress them).

As I'm in you fabulous last RR build, and all is working 100% for me, low battery drain, bluetooth in the car, wi-fi HS...., I was wondering why all this effort put in migrating to Oreo? Apart from turn AOSP to official, what are the advantages of using Oreo instead Nougat based actually?

Oh, and I can understand the fun in developing, because I'm (better I was) a developer, some years ago, but what about the practical advantages?

I really admire you because your capacity of learning and doing so much things at a time, and the speed of progress is spectacular, only wondering why is so important to be in Oreo.
[G4 Android Development] kessaras:
>>> Kernel TEST <<< | New Panel/Brightness algo.

Users can also read the instruction in TWRP thread when it's about TWRP.

Forget fastboot boot on N bootloader. After you flash N there is no fastboot boot. Instructions in TWRP thread make this clear.

fastboot flash recovery recovery.img and then hardware key combo to enter recovery.

If you are on MM bootloader now and flash N (maybe) that moment will be your last one to use fastboot boot command and then forget about it. Erase that command from your memory :D

im not los maintainer as im AOSCP maintainer. I'm to the AOSP side.

I'm not RR maintainer as genesixxbf3 is the one , plus again i'm in the AOSP side.

My RR gets built using my device tree, blobs and sources and the RR rom.

When RR updates to O i will simply switch to O tree,blobs and sources as i already have them ready here and get RR O building.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++

So, back to our O.

Unzip and

Flash this boot.img ,

adb reboot bootloader

fastboot flash boot boot.img

fastboot reboot

Flash in TWRP your root method if you are rooted.

Test this upgrade with me.

*I added in kernel level new panel / brightness algorithm.

This new algorithm may fix for good this problem we have with the display since LP since 2012.

*Added more selinux policies thay may fix more ril related issues.

If we find this algorithm for brightness better , then i'll switch to it and add it to N too.

Also it will be suggested in MM to [MENTION=5545101]steadfasterX[/MENTION] to improve his MM.
[G4 Android Development] McRoy:
:D

Thanks! (I cannot find TWRP thead - Is this? https://xdaforums.com/g4/development/recovery-twrp-3-touch-recovery-t3442424)

I'm on MM already, I want to install O directly so, after doing the process above, once I've install O Rom, we need to reinstall TWRP (to install gapps). So we need to do:

adb reboot bootloader

fastboot flash recovery TWRP-LG-H815.img (just installed with only that command?)

adb reboot recovery (to check if TWRP is well installed)

And to enter to TWRP:

Power down and pull out the battery. Do not forget to remove any USB cable.

Press power down and hold it down. Put battery back while keeping vol down pressed. Press power button and keep now both buttons pressed. Directly you see the LG logo the first time just release only the power button for 1 second ( do not release vol down ) and then press power again and keep both pressed until you see the factory reset screen. Proceed like you would to the factory reset (as long as TWRP is installed it will not reset but just open TWRP instead).

Sorry about that questions, but It will be my first flash on LG G4 since Nexus 4!
[G4 Android Development] kessaras:
well..... it sais TWRP and it sais Official........ so it can't be anywhere else...

And i said read !

I'm not room service -_-

adb reboot bootloader

fastboot flash recovery TWRP-LG-H815.img (just installed with only that command?)

>>>> this won't work. >>> adb reboot recovery (to check if TWRP is well installed)

When you are in bootloader you can only use fastboot command. fastboot reboot then.

press vol down + pwr until you see LG logo. release only pwr and press it/hold it again until it boot to twrp.

Advance wipe >> data, system

flash rom, gapps
[G4 Android Development] McRoy:
Many many thanks! Now I understand well!

I know your'e not room service. I don't hope that. Sorry If I meant that.

I'm trying to know the process just to not brick the phone and avoid more questions. Also, I wish to make a tutorial to htcmania.com for all the spanish users could install O

I know the hard work that you assume with this development, totally for free. Thanks for that!!
[G4 Android Development] kinuris:
Yes, I know. I was only wondering about what advantages has to progress to Oreo over Nougat in our phones, seeing the difficulty and the time and effort you great people are investing in it.
[G4 Android Development] tambukey:
Just wanted to put in this works to solve waking device with power button. Obviously you lose double tap to wake(not like it worked anyway), but since turning it off I haven't once had to press power button multiple times to wake the device.

[MENTION=5461026]kessaras[/MENTION] So a couple of times now bluetooth crashes when playing music in my car. This causes the phone to freeze as well for a bit, probably eating up all the CPU. I'm attaching logs of a grep "Bluetooth" and the full logs around the time of it. The full logs are show just before I turn on bluetooth until I make it to work and take the log, so it ends up being about 20minutes of logs, and I apologize for that. Hopefully the grep log is all you need. Also for information, I have an LG G watch R that is connected as well, so you're seeing a smart watch and my car. I have not tested without the watch since this is rare when it does this, but it has happened a couple times since at least a few builds ago.
[G4 Android Development] kessaras:
Benefits me as a developer and my ego.

Even though we have 2 bugs , it's already a huge achievement in front of LG work.

And if we had blobs for O we wouldn't even have those two ;) which will eventually solve them.

Plus I'm learning. If I just stay at old stuff I don't learn anything
[G4 Android Development] obvious:
I've never had a problem with touchscreen or double tap to wake but I'm running the test kernel now and, well, it works fine so far.

Fwiw, the only problem I've had previously is the vertical banded multi coloured display (rarely) after a phone call.
[G4 Android Development] McRoy:
Installed from MM and at this time works fine

But....camera app doesn't have Manual Controls and all the features of stock rom. IT's possible to get that APP again?
[G4 Android Development] obvious:
I don't know java or cpp etc so this is 100:1 shot

https://github.com/SiXROM-OREO/system_sepolicy/commit/3692b3189e77c3b058b81f70dd9a1b60837a8138

Relaxing neverallow policy

https://github.com/oreo-victara/and...mmit/de448b5bde4c130a0260680f277706132a4340c7
[G4 Android Development] #ApolloLiteProblems:
Download a 3rd party camera app like Open Camera, or, if you're willing to spend a bit, ProShot.
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
Most important advantage:

http://time.com/5039780/google-cheeseburger-emoji-change/

... just kidding. But I've just checked what are the new features (seehttps://en.wikipedia.org/wiki/Android_version_history#Android_8.0_Oreo_(API_26)) and think there are some which I will use and maybe some of them are also beneficial for you.
[G4 Android Development] #ApolloLiteProblems:
This is 8.1 which is API 27
[G4 Android Development] tqwzUX6fn39GZMEzSnDF:
Yes, but kinuris has asked for advatanges of Android O compared to N - this includes 8 as well as 8.1.
[G4 Android Development] #ApolloLiteProblems:
Fair enough.
[G4 Android Development] kessaras:
no. those come from google and we won't change them, otherwise we open holes which we must close them by pre-dexopt jars
[G4 Android Development] obvious:
So, sacrifice having a phone that makes phone calls. Tough call :eek:
[G4 Android Development] ziomus684:
For me encryption doesn't work. I'm using 23.01 bulid, modem end botloader v29a (no splash). I included encryption end after 2 minutes, when i tried unlock phone got 'bad password'. I used gest password . The second thing 'double click unlock' usually get black or torn display. Also for me this ROM is too slowly. Can you it's speed up?( nougat was faster) End infrared (remote control) doesn't work.
[G4 Android Development] McRoy:
XPOSED and Minimguard are allowed?

Some "bugs" detected....

- Pushing power button doesn't swich on the sreen at first time. Sometimes 2 / 3 pushes are necesary to screen on
[G4 Android Development] cartman_73:
Xposed for Oreo was released in beta version a few days ago, Try it and see if your modules works fine, keep ready the unistaller file to any issue.

Sometime, slowy wake up from power button happens to me too
[G4 Android Development] bedencic:
xposed works, i have installed adblock for more than 1week i think.

as kesseras already told, disable pocket detection, and than it unlocks just fine
[G4 Android Development] Minto107:
Disable pocket detection and unlocking will be fine. IR works with Mi remote(maybe your app doesn't support Oreo yet). For me ROM works quite fast
[G4 Android Development] kessaras:
for me all these work.

and for display i found a way to fix it already. i just haven't shared it yet

About rom being slow.

Rom is like this either you like either you don't like it.

Every developer creates his rom the way he likes and users are free to choose which rom they will use.