yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] tambukey:
I think it requires root because I can edit my list, but it gets updated with every new flash I do. I also think the issue may be people trying to flash the wrong modem. Just like how the h811 stock modem works with this to rom, they probably don't need to update modem unless it's an h815
[G4 Android Development] Minto107:
Maybe. I don't have non 815/811 to test but maybe if they use other than v29 or v20p modem then baseband says unknown and most likely then it's impossible to change APN settings
[G4 Android Development] nummer:
Aight then, just one last thing, does the rom detect sensors? (use http://v.ht/JXbx to find out) and does the IR blaster work?
[G4 Android Development] tambukey:
For my h811, yes and yes
[G4 Android Development] slim902:
Yeah everything in that app is working.

I don't use the it blaster but tested it using this method and it seems to be working.

https://peel.freshdesk.com/support/...now-if-my-phone-ir-blaster-is-working-or-not-
[G4 Android Development] RogerBoy123:
Hey kessaras, I've been gone for a while and your ROM seems to be official now. Sorry if it sounds dumb, but does that mean that you are the official maintainer of CypherOS for the G4 now?
[G4 Android Development] spartan268:
It works fine for me. Maybe I'm one of the lucky ones who's APN stuck around after a flash.

In general the main issues you come across is the cell issue which is across the board. The video being choppy. And maybe notification sounds not working, I've yet to properly investigate into it since I'm on silent most of the time for work. For me it's a non issue cause of that. Asides from those issues its been treating me fairly well and I'm beyond satisfied with everything.
[G4 Android Development] nummer:
Thanks for the reassurement, flashed this ROM on my h812 and everything is working fine and dandy :D

Edit: after a reboot, the sim is not being detected... Back to stock :(
[G4 Android Development] MatteoB92:
Mate, I have a question : I'm on Nougat, 4.1.2 released on 20180218.

I saw on 3rd of March it has been published a new version http://droid.binbash.it:8008/aoscp/nougat/h815/

But I wasn't able to find a changelog, can I update to this version?

Which are the improvements introduced?

Because I noticed the last releases had all the 4.1.2 suffix..

Inviato dal mio LG-H815 utilizzando Tapatalk
[G4 Android Development] kessaras:
3rd ? 6th you mean !

no. N doesn't have any update anyway. N development stopped with the release of O since months. It only gets security patches and kernel improvements (if there is any i can add from O to N).

Nothing changed.
[G4 Android Development] MatteoB92:
I meant obviously 6th of March, I was tired.

Recognized the N situation, I understood this release was an auto-build generated from the server, so if aren't security patches or kernel improvements I'll stand at the window with the 18th of February build..

Inviato dal mio LG-H815 utilizzando Tapatalk
[G4 Android Development] SeewolfPK:
[MENTION=5461026]kessaras[/MENTION]: What about Changelog Oreo? Your next unofficial I see: 20180312

Edit:

With this ROM device hot as hell.

u0_a40 runs with min 98,3% to 117% CPU

Device is slow as a snail

so it is unusable

Restore my Backup with twrp _103: First try: Boot freezing. I think device to hot.Wait some minutes.Again Backup: Bootloop. Only way to get a working device: Install 20180228
[G4 Android Development] tambukey:
u0_a40 is usless to us. That is just an assigned "user" from your device based on when it starts. If you list the actual name, maybe we can help. If I take a guess, it probably was related to com.google.android.* (probably gms.persistant) as this always spikes on first boot after a new install. You have to give it some time, and then also a couple reboots. Make sure you have a good data connection as it is probably updating/processing a lot of info in the background. Don't hate on the rom if you don't put in the effort to fix it yourself. Try to restart the process, try to kill it entirely. Reboot a few times, do something more than "booted and was slow so I uninstalled"
[G4 Android Development] ThePiGuy:
Finally running aoscp again. Looking very good :). Only thing I have noticed (on mine at least), standby battery is very good but as soon as the screen switches on it starts draining reasonably quickly. Has anybody else got this?
[G4 Android Development] SeewolfPK:
In terminal I see now on 20180228 also u0_a40 running but only 1% CPU under ARGS I see: com.android.systemui.

How can I find out more?
[G4 Android Development] tambukey:
Again u0_a40 is arbitrary. The numbers change every boot. Those numbers are assigned based on when the process is called and has nothing to do with a specific process. I suggest if you want the latest AOSCP rom, install it, then wait a while after that inital boot. Let the OS do its thing for a bit. Once it starts to settle down, perform a reboot. After that then watch the process list. If something refuses to calm down after a while on its own, it may be a problem. But try to restart the process. You could use

am restart (package name e.g. com.android.systemui)

If it is a process that isn't required try killing it.

EDIT: keep in mind, restarting systemui is like a soft restart. it will blackscreen then load the ASOCP rom.
[G4 Android Development] SeewolfPK:
Sorry, nothing helps. Device runs now 10 minutes and kill 15% off battery. Alway the process running until 117% CPU

(how can use over 100%?)

How can I find out which prozess it is? Terminal did not show more info.

Device going hot.

Never before I have had this problem. What did the new ROM make? 20180225 runs without this problem.
[G4 Android Development] tambukey:
Are you rooted? If so

su
top

will show you the full list of processes.(stop this by typing q ) It can achieve over 100% because of big and little cores. I haven't switched to the 0312 build yet, im still on 0307 so I cannot confirm if this is a consistent thing or not. I would assume though since I have had processes do the same thing, that it is either the RILD process, com.android.systemserver /or systemui, or com.google.gms.persistant. These processes are all normal, but sometimes seem to run away. RILD can be fixed either with a reboot or the RIL Control app(if rooted) the rest all get fixed with reboot. I will attempt to install the 0312 build here shortly to see if I have the same issues or not.
[G4 Android Development] DosenHatti:
Same here with last unofficial. But not with official 20180311.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] nummer:
[MENTION=5461026]kessaras[/MENTION] since recently sfX developed an unlock for all g4 models, do you know if you will make builds for models other than h811 and h815?
[G4 Android Development] kessaras:
Not my fault. Here is fine.

sfx will handle that in his server to auto build. ROMs are same with a few changes in defconfig. No need for me to do anything there
[G4 Android Development] SeewolfPK:
The Information I posted are from terminal su top.There is no other Information to seen.

I am atm back to 20180228. That run without problems.

Kessaras say it is not his fault. I did not understand that 20180228 runs fine and the new one not.

That's too high for my mind :D
[G4 Android Development] ThePiGuy:
Weird. This is on my home-built version that I built on the 11/03
[G4 Android Development] NickName777:
One last thing.

I'have to update first the bootloader and then install the rom or vice versa?
[G4 Android Development] ThePiGuy:
Doesn't matter. Stock ROM can't run on a newer bootloader than it came with, but AOSCP runs perfectly well on marshmallow bootloader
[G4 Android Development] tambukey:
Quick question, are you using the official or unofficial? I can't download from Steadfaster's server on my work internet... So I cannot test until I get home.
[G4 Android Development] NickName777:
Sorry but I don't get one thing.

Now I'm running stock LG Android 6.0 v20g.

If I want to update to last oreo aoscp I have to flash or not the V29A firmware?
[G4 Android Development] ThePiGuy:
You can but it's not essential
[G4 Android Development] NickName777:
Ok thank you!

I think I'm going with the v20g and if I experiment some bug I'll update to V29A
[G4 Android Development] SeewolfPK:
I am on kessaras unofficial.
[G4 Android Development] ThePiGuy:
I have literally just discovered that my headphone jack doesn't work. I know it did on earlier versions. Is anybody else experiencing this?

Edit: turns out the headphone icon doesn't appear. The headphones themselves work
[G4 Android Development] lordc:
Hi! I am about confused,

So on SFX server we have a 20180312 realease that is automatically generated without kessaras magic or if it's generated with all the magic? I get confused due the main thread states that we get builds o 1thnd 15th of every month.

Sorry if I made a dumb question
[G4 Android Development] kessaras:
.....................

they asked me about N. O is not auto. i can't automate something that gets random update, random google updates, random features, random everything. if it was auto it would be a miracle
[G4 Android Development] trqzhangkai:
I flashed the 5.3 rom but the wifi doesn't wok,and the mac-address is 00 00 00 00 00 00,my device is H815p unlocked by the UsU.
[G4 Android Development] ziomus684:
When you repair infrared for remote control, hotspot end decrypting in twrp?
[G4 Android Development] Minto107:
I think it has something with touch boost. When I'm not touching the display(watching videos etc) battery drain is fine, standby drain is unnoticeable. I haven't had that good standby drain since I moved to G4. I'm still on previous build but we'll see how it'll go. Stats for now: 9h30m on battery 2h7m SOT 31% left
[G4 Android Development] ThePiGuy:
That would make sense. It did appear to be when I am scrolling down an article when it drained. Your SOT is also very similar to mine (2hr 49m at 16% left)
[G4 Android Development] Minto107:
Yeah but now 3 mins SOT consumed 2% battery. My battery is in pretty bad shape but I feel its warming up too so it must be connected
[G4 Android Development] NickName777:
Somebody can tell me if i have to download the rom from the official site of the aoscp project or the unofficial build hosted on steadfasterX's server? Also TWRP on the official site i found the 3.1.1, instead on steadfasterX's server there is the 3.2.1.

If I am on v20g I have to go with the MM build of steadfasterX, right?

Damn with my old galaxy gio the modding was not so hard!:(:(
[G4 Android Development] ThePiGuy:
Nougat 3.2.1 from steadfasterX. At the moment, official and unofficial AOSCP are the same as they were both built on the 11th so it doesn't matter
[G4 Android Development] hteles:
aoscp_h815-5.3-20180312-unofficial.zip Burns The phoe

Had to do a factory reset ( after putting the phone in the fridge for 4m ), sadly didn't do a backup.

I'm reinstalling now http://droid.binbash.it:8008/aoscp/oreo/h815/aoscp_h815-5.3-20180307-unofficial.zip.

Brief history:

H815 refurbished

Unlocked with sfx USU

Installed the first custom ROM last sunday, the previous aoscp version.
[G4 Android Development] tambukey:
Did you happen to see what process was causing the issue? I will be installing later today, trying to see if what people are reporting is fixable on our end or not.
[G4 Android Development] NickName777:
But excuse me why if i'm running on a MM bootloader i have to install a N version? I don't get it at all..

I've also seen that exists a modded versione made by Kessaras. What this differ from the standard version?

By the way excuse me ThePiGuy, today i'm making you crazy ahah.
[G4 Android Development] choice2rejoice:
Yeah mine is cooking too. 80 degrees seems not so strange at the moment. Attached the top
[G4 Android Development] hteles:
Top Processes by CPU time

com.android.systemui

system_server

com.google.android.gms.persistent

com.google.android.gms

Even after a clean install, yes, i did a factory reset ( no prior backup unfortunately ) the same happened

Regards..
[G4 Android Development] tambukey:
Okay so it looks like on most recent build systemui is using all processing power. I'm still going to confirm myself later and try some things. I see it stayed after factory reset, what about after multiple boots? Has any one tried a few reboots to see if it stays?
[G4 Android Development] hteles:
I did try a few, but it stayed the same. Also did few rild restarts.
[G4 Android Development] tambukey:
Since it is systemui, RILD won't affect it. Something changed between build for systemui. I believe they were working on adding the Ambient play on/off and adding ambient weather. Don't remember if the weather has been added yet. Can't view commits and changes at work though. Maybe someone who can right now can check the changes between builds.
[G4 Android Development] choice2rejoice:
Yeah did a few reboots, but nothing changed.
[G4 Android Development] Rookie69:
I'm very happy with the latest release aoscp_h815-5.3-20180312-unofficial.

Of course the phone got hot the first half hour after burning the rom, but after a reboot the CPU goes to deep sleep. Absolutely no problems.
[G4 Android Development] choice2rejoice:
"Of course....." ?? 30 minutes of frying? Hahaha Never had that problem. And even now it was a lot longer than 30 minutes. Flashed the earlier version and the temp dropped "immediately" after flashing.
[G4 Android Development] fahrer17:
A friend asked me today if I could update his H815. Searching around I came across this thread and I must say AOSCP looks rather promising.

Now I have some questions for which I didn't find an answer:

- What Android version (Nougat or Oreo) are AOSCP 4.x and 5.x?

- How can this ROM be updated, OTA or manually?

- There is no "not working" section in the first post - is there something that's not working?

- How is the camera quality? My friend's quite afraid of losing the good stock camera.

Sorry if some of the questions are already answered but as mentioned before I discovered this thread today. And it's more then 300 pages... :o
[G4 Android Development] lordc:
Thanks mate, sorry for any annoyance

---------- Post added at 08:44 PM ---------- Previous post was at 08:39 PM ----------

You should search on thread but

1. Oreo=5

2. Manual update (the unofficial one) official aoscp is very slow on updates

3. Sure not FM radio. Not sure NFC, some problems with Netflix (lastest version maybe DRM ****, but Netflix 4 -search on apkmirror is OK)

4. Quality is nice and you can try bsg gcam mod for more photo stuff (portrait, hdr+)
[G4 Android Development] tambukey:
So far after I got the new rom installed I have the same Problem [MENTION=5461026]kessaras[/MENTION] currently a couple of us are experiencing com.android.systemui running around 100% CPU, or I am also seeing system_server running at 100% with systemui at about 80. Restarting systemui currently hasn't fixed it. rebooting phone hasn't either. I am going to try safe mode in a sec. I am currently looking through logs.

EDIT:So looking at logcat through adb while doing nothing on phone, i keep getting this repeating over and over. I also turned off ambient play recognition

3-13 15:17:52.492 21035 21145 D sensors_hal_Time: tsOffsetIs: Apps: 1305554432833; DSPS: 42903865; Offset : -3767617658 (diff 6458 @5)
03-13 15:17:53.724 21785 22175 E AmbientPlayRecognition: 0 bytes recorded!?
03-13 15:18:08.724 21785 22175 I chatty : uid=10039(com.android.systemui) Thread-3 identical 5 lines
03-13 15:18:11.725 21785 22175 E AmbientPlayRecognition: 0 bytes recorded!?
03-13 15:18:12.494 21035 21145 D sensors_hal_Time: time_service_sensor1_cb: msg_type 2
03-13 15:18:12.494 21035 21145 D sensors_hal_Time: time_service_sensor1_cb: Sn 24, msg Id 3, txn Id 0
03-13 15:18:12.494 21035 21145 D sensors_hal_Time: tsOffsetIs: Apps: 1325556598138; DSPS: 43559296; Offset : -3767619700 (diff 6302 @5)
03-13 15:18:14.725 21785 22175 E AmbientPlayRecognition: 0 bytes recorded!?
03-13 15:18:26.725 21785 22175 I chatty : uid=10039(com.android.systemui) Thread-3 identical 4 lines
03-13 15:18:29.725 21785 22175 E AmbientPlayRecognition: 0 bytes recorded!?
03-13 15:18:32.500 21035 21145 D sensors_hal_Time: time_service_sensor1_cb: msg_type 2
03-13 15:18:32.501 21035 21145 D sensors_hal_Time: time_service_sensor1_cb: Sn 24, msg Id 3, txn Id 0
03-13 15:18:32.501 21035 21145 D sensors_hal_Time: tsOffsetIs: Apps: 1345559182297; DSPS: 44214740; Offset : -3767598705 (diff 6198 @5)
03-13 15:18:32.725 21785 22175 E AmbientPlayRecognition: 0 bytes recorded!?

EDIT2: So on the third attempt using kill command with the PID of systemui, it is now not using any cpu basically.
[G4 Android Development] choice2rejoice:
Also after a few reboots?

Still strange thought, that a guy didn't had this problem.
[G4 Android Development] tambukey:
I'm not sure why it didn't occur for him. But like i said after a kill (PID) command it was working fine, and honestly on the newest rom, cpu usage was the lowest I have seen it. And also since the kill fixed it, reboots seems to keep it in the right spot too. Takes a little bit for the boot to settle back down, but once it does everything is super smooth.

EDIT: so i also disabled Ambient play while systemui was going crazy. and tried a few other things. Since getting it back to normal I only turned back on Ambient Weather and auto-face unlock. (No idea if those even affect anything or not, just stating the few things I did)
[G4 Android Development] choice2rejoice:
Ok. Thx for the solution. Will flash it again (tomorrow) and kill the system UI.
[G4 Android Development] tambukey:
Sorry one more thing I did, since I have to do this every time I flash to fix the settings search function, I cleared settings data. That could have helped as well, but remember when you clear that you need to re-enable developer options and verify OEM unlocked is still on.(I found it off before, but this time it was still on).
[G4 Android Development] ThePiGuy:
The N version is the version [MENTION=5545101]steadfasterX[/MENTION] (the TWRP device maintainer) is currently working on. It is the one getting all the fixes etc, and the only other difference is that it can't decrypt MM OS's if they are encrypted (the N and MM versions are not dependent on bootloader at all)

It's fine :) we've all been there
[G4 Android Development] choice2rejoice:
:D Ok. When deleting the pid only doesn't work, I will try this too. ?
[G4 Android Development] Lurensu:
I flashed the latest unofficial after a pretty bad experience with the official build (the phone was way too hot all the time) and everything runs great... But the wifi doesn't work (I cannot connect to any network)

[MENTION=5461026]kessaras[/MENTION]

Here there's a log that I took when I tried to connect to wifi
[G4 Android Development] Rhese:
Can confirm that 1 kill of systemui did the trick for me too :good:
[G4 Android Development] tambukey:
Follow what I put down earlier. You need to do a kill (pid) of systemui as that is most likely the cause. Multiple users are reporting it.

good I'm glad that seems to fix it.

Has anyone gotten the ambient weather to actually show up on the lock screen?
[G4 Android Development] Lurensu:
Weren't you talking about the cpu usage of systemui?

Sorry if I misunderstood
[G4 Android Development] tambukey:
Yes which high cpu usage is about the only reason for high temperature. Since fixing the systemui, for me, everything else has been good. Nothing getting hot or abnormal issues thus far.
[G4 Android Development] Lurensu:
Got it, thanks.

I just wanted to tell kessaras about the wifi issue in case he doesn't know...

Tomorrow I will go back to official until it's fixed
[G4 Android Development] tambukey:
I just re-read the other post again and realize you were talking about the latest official having issues. Sorry I thought you were saying the unofficial was the issue. Granted they are the same build, well they should be, but I'm not sure for the wifi. Mine is working fine and so far no one has mentioned it.
[G4 Android Development] Gone2Plaid:
Lost TWRP with AOSCP 5.2

I did a complete wipe from Lineage OS 14 on my H811 and then flashed AOSCP 5.2 + GAPPS. Booted and then discovered I couldn't get back into TWRP. Now I want to update to the latest AOSCP 5.3. I have FWUL and can issue ADB and FASTBOOT commands. Trying to reflash TWRP 3.2.1 Preview 103 N fails with the error "FAILED (remote: unknown command)". How can I get TWRP going again, or how can I use ADB or FASTBOOT commands to update my AOSCP?
[G4 Android Development] cartman_73:
Your recovery is still there, maybe. Try to enter in it with physical buttons, confirm when it ask you to go in factory reset then recovery should be start
[G4 Android Development] Lurensu:
Uh, so you are on the unofficial as well?

Damn, so the issue is on me only
[G4 Android Development] vwbottom:
Anyone else having problems applying icon packs on Luna Launcher? Crashes everytime. Using 0703 unofficial.
[G4 Android Development] choice2rejoice:
Flashed it, killed the pid, no change. Deleted data from system, no change. Killed it again (because it was there again) and just got just a little change. Waited, no change. Waited longer, no change. Rebooted, no change. Rebooted twice and the system UI was cooking my phone again. Waited, no change. Killed the pid, no change. Went back to the 3-7 version and everything is back to normal. ? So, maybe I'm gonna try the official, but this is ok for now.
[G4 Android Development] tambukey:
Man that's terrible. I'm not sure why it works for some and not others. If you use ADB you can watch a logcat on your pc while your phone is just sitting, I wonder if you get the same repeating errors that I posted a while back. Once I finally got mine working those repetitions stopped.
[G4 Android Development] choice2rejoice:
You mean the Ambient error? I had them the first time, but didn't think of it to check again. Will check for it next time
[G4 Android Development] tambukey:
Not just the ambient error but also the

03-13 15:18:08.724 21785 22175 I chatty : uid=10039(com.android.systemui) Thread-3 identical 5 lines

That line also went away for me. That looks like systemui duplicating errors and logcat won't read them because they are identical lines. Unfortunately that also means it isn't showing the exact error, at least one that I don't see.

According to another site due to the chatty, logcat won't show the actual error. If you get the new rom back on, try these out to see if you can see the full error

You can avoid this behaviour by whitelisting your app for logcat:

adb logcat -P '<pid or uid of your app>'

You can print the current white and black lists by executing:

adb logcat -p

Also this command is helpful to print logcat statistics:

adb logcat -S
[G4 Android Development] choice2rejoice:
Ok, I will. Thanks for being so helpful.
[G4 Android Development] tambukey:
Not a problem.

Also I figured out how to get Ambient weather working on the latest update. I had to go into apps&notifications and find Omnijaws, turn on location under permissions, I then cleared the cached. On the main app info screen is a little cog wheel on the top right. click that and ensure your location is on, then turn on enable. If you have a good data connection and location up it should refresh right away and show up on the lock screen. I had to play with it a bit, enable on and off, location on off, and whatnot but it eventually showed up. Currently there is no way to manually refresh it, at least I don't see it. Once it found the info it stays until the next update. You can try putting in a custom location to determine if it is working or not.
[G4 Android Development] fahrer17:
Well, actually I did... But to be honest: xda search and me, we're not the best friends... :(

Thank you, that helps a lot! I'll see how he will decide. If it was MY phone, I'd sure give it a try!