yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] steadfasterX:
Only one kernel for all models. Just the kernel conf is unique for every model (which ofc are all in titan path) and so is every DT mostly identical except of blobs path and kernel config (and the model name etc ofc)
[G4 Android Development] kessaras:
ok that i can do then
[G4 Android Development] ConradP:
Which TWRP you are using? Did you clean all from phone? I have no issues - none. ROM is great.
[G4 Android Development] miXXed404:
I'm using twrp-3.3.1-0, yeah always full wipe before flashing, tried other versions of twrp but same result
[G4 Android Development] ConradP:
OK. So maybe try changing GAPS to micro or nano - if I have issues with builds I am sometimes even doing first run without GAPS installed.

This is probably a strange idea but you can try it. You can install Chrome or Facebook without Play Store.
[G4 Android Development] kessaras:
graphic lag fixed. rebuilding today build.

officially everything is fixed. if there is still any bug let me know about it.

today build will be up in an hour and h815 build will replace the one thats there.

EDIT:

Just a reminder. Do not encrypt yet.

I need to check vold policies first to make sure that vold is allowed to encrypt.

Todays build is a debug build.

Use with care. Send me logs for everything you see and looks like an error. (Not 3rd party apps errors. Those are already denied. Ask the apps dev to fix them)
[G4 Android Development] busattovini:
Thank you so much! :o

Oh, sorry for my unfamiliarity, but what is an encryption?
[G4 Android Development] kessaras:
Lol.

Encryption = protect data with password.

How does it feel to run pie now ?
[G4 Android Development] busattovini:
Wow, thank you! ^^

It's so fast, no lags at all. It seems like I'm using a new smartphone, lol. :o <3

Battery life is also even better.

Oh, a request for the upcoming builds: can you, please, create an option to turn off that battery light in Do Not Disturb mode?
[G4 Android Development] racav1904:
Thanks man for you're great work I am using you're pie builds and I have a cuestión, why I can't use Shazam app??? When I search for the app in playstore I can't install cause it's compatible with my device?? Why it's that???
[G4 Android Development] busattovini:
No issues here!
[G4 Android Development] kessaras:
Ask Google , they are the ones that restrict countries, restrict actions , restrict whatever ?

When Google doesn't let you install an app, what's the first thing to do ???

Download it from apkmirror and enjoy.
[G4 Android Development] racav1904:
So, do you think I don't tried that??? What is that answer man? When I tried to install the app shows a message that it is: you're device isn't compatible with this version.
[G4 Android Development] racav1904:
Look.
[G4 Android Development] wotofoko:
I have the same issue. Instagram, messenger, Viber and several other less known apps that I am using weren't available in the play store because it's not compatible with my phone as it says.

Also Facebook is available but it downloads a version of like 4 years ago.

Could this be because I used a build of gapps back from may?

As for the ROM itself, I can only say that I'm really surprised of how smooth it feels. Very polished and everything works perfectly. I came back to aoscp from other pie ROMs of the forum, not expecting a much better experience but I couldn't be more wrong. Hard work really shows, good job.
[G4 Android Development] busattovini:
What is the version of GAPPS that you are you using?
[G4 Android Development] kessaras:
I was honest.

Google manages those. Ask Google.

Or download from apkmirror.

Me here I can't use other apps that are available there.

Apkmirror ftw
[G4 Android Development] busattovini:
Hey, I've noticed graphic bugs in some apps. Would you solve it in the next builds?

This same issue was happening to another ROM I had installed before, so I think that it has something to do with the lack of OpenGL (sorry, I know nothing about it).

Please, help us! Haha. ? But I'll say it again: AMAZING ROM.

" Unfortunately for the tearing, there is nothing we can do. Its due to an issue with the default renderer on older devices, like the G4..

You can test this parameter via editing with Build Prop editor:

debug.hwui.renderer=opengl" — [MENTION=4956374]aoleary[/MENTION]

So, do you think this parameter works?

EDIT: IT WORKS.
[G4 Android Development] kessaras:
It doesn't. Opengl makes everything rendering slow.

If you like it slow , do it locally and set it inside build.prop. Me I like my phone fast.
[G4 Android Development] busattovini:
Sorry... ??

I think it's fast here, really.
[G4 Android Development] doomanix:
[MENTION=5461026]kessaras[/MENTION] I'm constantly getting a Yellow/Green screen crash while using both this ROM and AEX.

I switched to this ROM from AEX because of the new (old) RIL but was using the latest builds of both (July 1st on AEX, July 2nd for AOSCP). I'm using a H812 G4 with modified update-script. I'm not sure what causes the issue, or how I'd properly report it. I currently don't have access to a Computer with normal USB (one of those stupid Macbooks with no normal USB ports or a dongle) but am happy to purchase one if it's needed.

Currently The Yellow Screen Reads as follows:

RPM Reset!

Demigod Crash Handler: RPM Reset!

(blahs about how to get raw dump)

reboot_reason: 0x6d630202

gcc_reset_status: 0x0

pon_pon: 0x200a0

(board info) --- Will add if relevant

Invalid Ram Console!
[G4 Android Development] kessaras:
you be patient. we will unify the devices and you will have a h812 build instead of modifying this one.
[G4 Android Development] busattovini:
WOW, It seems like you've uploaded a new build today. Thank you so much! ?
[G4 Android Development] kessaras:
Updating our kernel today. I use the 4.4.X from Op6T.

Wait until you see the next build ?

Edit:

Ah I found what's the problem with that graphic glitch on top and on the bottom.

We have to define that device has no notch. That's all.

To test it out, you can go in developer settings, select a notch and then select default again which removes the notch.

Afterwards test any app you like. You won't have any glitch again until your next reboot.

I'm gonna fix that in the next build.
[G4 Android Development] ConradP:
Great news. It pisses me off. But it was absent in the builds before July.
[G4 Android Development] kessaras:
it wasn't there because while i was absent , they made use of opengl which is removed in pie.

pie uses skiagl but libskia doesn't work in qcom devices.

pie framework has only ported a small part for opengl.

result ?

we can't use opengl because it slows down the device. we r rendering at slow motion at some places.

we need to definately use skiagl and thats what we do. so the rendering bug is back, its me i brought it back, in order to fix it.

So tomorrow i fix it.
[G4 Android Development] busattovini:
You're amazing. I'll never stop saying that. ♥️
[G4 Android Development] kessaras:
i'm the new Torvalds ? wtf ? haha

https://gerrit.cypheros.co/#/c/CypherOS/kernel_lge_msm8992/+/9117/

https://gerrit.cypheros.co/#/c/CypherOS/kernel_lge_msm8992/+/9116/

im building now for the people. I want to see reactions after you boot it and wait a couple of minutes to finish caching.

Then tell me how it feels
[G4 Android Development] PhantomWhisper:
Hi,

Just tried todays build 05.07.19 with nano gapps 04.07.19 feels really fluid haven't noticed any stutter at all, great job! :)
[G4 Android Development] ConradP:
Flashed the last version from today.

No graphic gilches :good::good::good:

:laugh::laugh::laugh::laugh:
[G4 Android Development] busattovini:
Very stable, and there are no graphic glitches anymore. Thank you! ?
[G4 Android Development] raptorddd:
are we going to see RR pie soon.?
[G4 Android Development] ozukoc:
Recently flashed new build and it is first time im flashing aoscp. Migrating apps and data right now but seems stable for now. Big thanks to [MENTION=5461026]kessaras[/MENTION] [MENTION=5545101]steadfasterX[/MENTION] and [MENTION=8699949]ThePiGuy[/MENTION] for such an effort to G4.

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

Recently flashed new build and it is first time im flashing aoscp. Migrating apps and data right now but seems stable for now. Big thanks to [MENTION=5461026]kessaras[/MENTION] [MENTION=5545101]steadfasterX[/MENTION] and [MENTION=8699949]ThePiGuy[/MENTION] for such an effort to G4.
[G4 Android Development] kessaras:
No because it is extremely hard to maintain this device nowdays.

It's a 2012-2013 smartphone and it takes many many many hours to maintain it.

Imagine I quit doing anything in AOSCP and since a week I'm only working to this phone.

Plus that I don't get paid for doing all these....

LG at least should pay me for doing all these ****. Not even the stock firmware was that stable.

The work this device needs in kernel and in device tree is way too much...

EDIT: [MENTION=5308112]raptorddd[/MENTION]

https://github.com/CypherOS/kernel_...e=d9b422d5efe1f180b940abc619b125c055f7402c+35

if you go back and see what i committed the past days you will get crazy. Those are all from 4.4.X kernel.

3.10 doesn't have anything to offer since 2 years.

All these , even though i kept the original author, because thats the right thing to do, are hard coded line by line to work in 3.10 kernel, in sd808 and in gpu a418.

imagine i spend 8 to 12 hours per day after work for these. my eyes are like zombie and i sleep 4 hours past few days just to bring this sh-it up to date with everything :)

I like it because i learn everyday something new. No complains.

It's just that it's impossible to port other roms now. If someone has a device good enough , he can do it and share the build with everyone. It's not hard to port another rom since we have everything ready here
[G4 Android Development] WiZaRd981:
If you want ROM with good features.. Flash Havoc.. If you want ROM with stock features, flash Cypher.. RR stuck from Oreo time.. G4 is REBORN By the way.. Excellent job [MENTION=5461026]kessaras[/MENTION] and [MENTION=5545101]steadfasterX[/MENTION] .. :angel:
[G4 Android Development] busattovini:
BTW, I recommend the UC Turbo Browser. It's really soft and fast, way better than the Google-RAM.Exterminator-Chrome.
[G4 Android Development] coast2coast:
Amazing rom, big thumbs up to the dev!

However, in newest build I can't get rid of the black stripe in the nav bar, while in homescreen. Had to flash earlier version because the black bar gets in my way. Hopefully there is an easy way to make it transparent again.

Cheers
[G4 Android Development] kessaras:
No. It's my choice to be black because I try reduce the GPU stress here because we are forced to use skia in pie.

Maybe in future if they fix the graphic issues with skia to remove that
[G4 Android Development] busattovini:
Battery life has also improved a lot.
[G4 Android Development] coast2coast:
Fair enough, I already flashed the latest again!
[G4 Android Development] raptorddd:
i see.

i was just wondering.
[G4 Android Development] busattovini:
Now it's happening to me... Some apps are missing in the Play Store (like Shazam), and they were there before in the previous builds. I tried to install Tinder via apk, but it crashes. Do you know how to fix this issue? :)
[G4 Android Development] busattovini:
Even Dollify! lol! And, when I install the app, all I get is a white page.

I've tried to install other apps as well, and they didn't work, even though they're pretty simple.
[G4 Android Development] busattovini:
I'm going to reinstall the ROM, and then I tell you what happens.

EDIT: same issue.
[G4 Android Development] kessaras:
Yeah many apps are gone here too. I guess Google changing something.
[G4 Android Development] polfrank:
Try clearing cache and data of play store and play services, it may help!
[G4 Android Development] raptorddd:
launcher crashes when click on settings. also flashed laos 16. i found laos 16 smoother than aoscp.
[G4 Android Development] busattovini:
Oh, I see! I hope they solve it! Anyway, thank u. :good:
[G4 Android Development] kessaras:
I know. It's looking for fingerprint sensor which we don't have.

Good for you. Stay with Los please. Because I really dont care.

You see , I'm not selling anything. I'm just sharing the rom I use at my phone.
[G4 Android Development] busattovini:
SLAY

---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------

Also, I just installed Smart Launcher 5 from Play Store, but actually it is Smart Launcher 3.

---------- Post added at 04:01 PM ---------- Previous post was at 04:00 PM ----------

GOOGLE, YOU'RE A MONSTER

Haha
[G4 Android Development] busattovini:
Lol, ancient Facebook app version haha

Do you know if it's happening to other ROMs as well?
[G4 Android Development] jabashque:
Regarding people getting ancient app versions when downloading off Google Play, I remember seeing something similar on LineageOS 16.0 for bacon where Google Play was serving 3-4 year old app versions to devices with the bacon CyanogenOS Marshmallow fingerprint (which LineageOS was using). Changing to the fingerprint used in CyanogenOS Lollipop fixed the issue. As for why Google Play was doing that, I have no clue...
[G4 Android Development] ozukoc:
I had same issue with google play but when i flashed latest build i also used migrate app for app and data so i had problem with just instagram and facebook ( apps were crashing needed to reinstall ) and i installed them with apk so not a big problem, rom is very stable and smooth everthing works like a charm. There is just one thing somewhere theres a shortcut assigned that tries to open camera and couldn find where it is :D ( either in power button or home button or both ) so need to deactivate it. Anyways big thanks to [MENTION=5461026]kessaras[/MENTION] !!
[G4 Android Development] ConradP:
Hey there.

I just experienced a kernel crush on H815 latest pie.

Dunno why. I had to remove battery to reset the phone.

Did you have had any issues like that.

I am using Kernel Adiutor but iI use only slightly moderated parameters.
[G4 Android Development] steadfasterX:
The reason for that is Google restricts app access due to (at least) 2 reasons:

1) by region

2) by device compatibility

The first one can only be solved by using a VPN to a country where the app is allowed but for the second there is a better way.

Share the output of:

adb shell
getprop ro.product.model
getprop ro.product.name
getprop ro.product.device

Google will check "ro.product.name" and depending on that (+ the vendor name) it will show an app as compatible or not (see here)

When it is not "p1_global_com" (I assume you will see "g4_global_com" instead) that is likely the reason for that.

you can change that in system/build.prop or

wait for the unified device tree

I am working on.

To be sure if that is the reason (I am 95% sure) pls do the above commands and (if you know how) do the build.prop adjustment (backup "system" before) as well.

I am not sure why that happens now and not before but likely Google tightened some stuff on their site shortly and that's why it didn't happen before.

.-
[G4 Android Development] kessaras:
if they change it in build.prop

also stop playstore and clear playstore data/cache before reboot
[G4 Android Development] racav1904:
Why navigation bar it's full black??? Can I change that???
[G4 Android Development] kessaras:
Outer space ?

Haven't you noticed that we have rendering issues when we use opengl and when we use the skiagl we have distorted graphics ?

I must reduce the stress on GPU until we figure out how to fix the opengl rendering in pie. That's something all older devices have.
[G4 Android Development] ConradP:
I have tested other Pie ROM for 2 days. I couldn't longer - it Was a hard experience. Now I am back and staying on this one:)
[G4 Android Development] kessaras:
In the end after they all merge latest patches and after they all fix rom bugs , they have same result.

And sorry for latest build.

It has a sensor experiment and it will have some more battery drain. Tonight I will build again and fix that.
[G4 Android Development] ConradP:
I have now same issue with Google Store. I noticed it only on Nova Launcher - it only allows to instal v. 3.3 and it is like 6.7 now.

I have changed ro.product.model to p1 and no luck.

Can I do maybe something more?

Edit: I took apk from the web directly and it works:)

Stupid GOOGLE:P
[G4 Android Development] kessaras:
Ya. Google block as by country for sure.

I already tested to certify my device, pass safetynet, pass dm verity check, pass everything and still failed.

Also they ban devices.

Can't install many apps, so thats why I already said that apkmirror , or fdroid , or Aptoide , are best alternatives.
[G4 Android Development] avirgosm:
Thanks a lot

Your 20190710 install perfect and runs great but after a one day of use it start to reboot UI

Will wait happily for today release
[G4 Android Development] kessaras:
Uploading now. In one hour it's there.
[G4 Android Development] lordc:
Installed. Runs ok, ****ed Google playa not avalaible apks. No problem ussing apkmirror

Thanks!!
[G4 Android Development] kessaras:
Today's build is the last one until the next security patch and|or when i'm done with the next work i'm about to start in kernel level.

There is a great increase in performance right now , so i bring back the transparent UI which i removed in the previous builds.
[G4 Android Development] lordc:
Thanks mate
[G4 Android Development] sianos:
Hi, thanks for your work on this rom.

I have just a question before flashing it.

Is there any "known issues" section somewhere (as i'm used to roms with that section) or there shouldn't be any issues?

Thanks in advance
[G4 Android Development] racav1904:
I need help!!! I can't root my device using superSU Zip through CWM recovery, I installed in recovery, do not shows any error, it's supposed that it is rooted, but when I install the SuperSU app says root undetected.
[G4 Android Development] raptorddd:
use latest TWRP frpm steadfasterX and use magisk to root.
[G4 Android Development] gixxergabi:
Thanks new build. 07.17 :good:

Google Play work?

I try, but some apk do not support, (chrome, viber....) to download from the internet...
[G4 Android Development] kessaras:
I've got no idea why apps are disappearing.

I don't know what Google is looking for and if it doesn't find it they block us.
[G4 Android Development] kessaras:
Wakelock FIX

i need your help everyone , otherwise some people may result with a broken bluetooth.

Ofc im talking about everyone because it's kernel related.

For this test h815 devices are enough and

not UsU unlocked

because the kernel is for h815 only.

If your device is h815 and unlocked officially, keep reading.

If your device is not h815 or it's UsU unlocked, you can skip this post, but you must know that the fix will also apply to you too.

(i simply built one kernel for the test , that's all, but if the test is a success , the fix will be applied for everyone).

Story:

While i woke up today and i saw my battery down by 10% , i asked myself "Why did this happen".

So i grabbed a dmesg and checked what kept the phone awake during the night.

Problem:

[17310.451461] gic_show_resume_irq: 57 triggered qcom,smd-modem

[17310.451461] gic_show_resume_irq: 200 triggered qcom,smd-rpm

[17310.451461] Suspended for 0.383 seconds

Trace:

I followed the irq to see which one it is and where it is from

and i ended up to the old common bluesleep wakelock we have since years.

Applying a fix:

I hard coded a fix i found from the "Loire kernel" in our 3.10.108 kernel.

I added a kernel switch to turn off bluesleep if bluetooth is off and a switch to turn on bluesleep if bluetooth is on.

Testing:

I will need one day to test it if the switch is working, because the phone needs to be in deep sleep state only and since my p20 pro is bricked , g4 is my only device and i use it.

So tomorrow morning i'll grab a dmesg and if the wakelock is fixed, i will apply it in our kernel for all devices.

But, thats where i also need you.

I need a couple of guys that use the bluetooth a lot, to use it as they always use it.

Do your stuff , do what you always do and check if bluetooth is ok and if it makes connection just like it always did.

If you do not do the test, i will simply merge the wakelock fix if it works and if something is broken , you will just have a broken bluetooth.

How to perform the test ?

Download the kernel from this post, unzip it and flash it in bootloader or in TWRP selecting the boot partition.

1. fastboot flash boot boot.img

or in TWRP

2. adb push boot.img /tmp

Press install

Navigate to /tmp

Flash image to boot partition.

Do what you always do, no more or less. Enjoy your day and come back later tonight or tomorrow morning and tell me if bluetooth worked like it always did.

:good:

Respect the thread, do not flood below with useless posts , the more people see this post and do the test, the better.

Post only for telling me if bluetooth is ok.
[G4 Android Development] ConradP:
For now my MiBand connected without problems. Same with JBL and Panasonic headphones. Tested also BT calling - no issues.
[G4 Android Development] kessaras:
Thank you.

Also do this.

Disable Bluetooth background scanning. In pie it's hidden.

That option only appear when searching for it in settings , or when you enable Bluetooth and disable it again. Below the on/off switch it has some small letters.

When you disable that , the wakelock bluesleep should now be stopped when Bluetooth is off

Google hide it well ?
[G4 Android Development] ConradP:
Ok. Done. ?
[G4 Android Development] kessaras:
ok its ready. i don't need anything else, no need to tell me anything else here or in telegram.

i'm building now , today update will have many fixes in kernel level and i suggest everyone to sync to them.
[G4 Android Development] ConradP:
Could I ask for Face Unlock module?

Oh and I just found out that XDA app is identifying my H815 as AT&T LG4 which means I think H810.

That could be some clue about the Play Store problems maybe...
[G4 Android Development] kessaras:
It's in schedule
[G4 Android Development] MrVoidex:
What's new with new build? (19 July)
[G4 Android Development] kessaras:
ah and sorry for setting default vib sensor to the max. My vibrator sensor here is half dead. I use a pincer and i make it work temporary until it will act again.

So just for your information everyone out there, my g4 lived long enough.

Android Q may be the last one for me here , if it's still alive until then.

Me i will do my best. But i won't fix my g4. When the vib sensor dies for good, i will uninstall it from inside and i hope the other parts keep going for a few more years.

This :

https://www.ifixit.com/Store/Android/LG-G4-Vibration-Motor/IF303-037?o=1

If anyone send it to me, i will fix my phone. Otherwise i will keep it like this. I'm not spending even a euro for this fossil , lol
[G4 Android Development] avirgosm:
[MENTION=5461026]kessaras[/MENTION]

Maybe

m.es.aliexpress.com/item/32886118349.html?pid=808_0005_0109&spm=a2g0n.search-amp.list.32886118349&aff_trace_key=540800b8c41c43b9aeb299b53f75d06e-1563705787899-08360-UneMJZVf&aff_platform=msite&m_page_id=5654amp-WZ45NFwep7ltcF3TX3U0JQ1563705984006
[G4 Android Development] kessaras:
its working for now.

I glued a tiny magnet on the vibrator :D

besides the vibrator sensor is just a stupid magnet. So i enforced it a bit.

I will build later and set back the intensity to normal level because now the phone vibrates more than a sex tool
[G4 Android Development] avirgosm:
jajjaja. Clever guy!!! Any sexy preview of new features on next builds?