yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] ntnlzr:
enable from dev option hci bluetooth

then adb pull /sdcard/btsnoop_hci.log
[G4 Android Development] ThePiGuy:
That is your problem. You need to use the latest

beta

TWRP from steadfasterX. The latest official TWRP (which by the way is made by the same developer), is only version 3.1.1, whereas the latest beta is version 3.2.1, which fixes this issue.

You need to go to http://droid.binbash.it:8008/TWRP/N/ (steadfasterX's personal website), where you will find all the betas (which are stable enough for daily use). Currently, the latest is twrp-3.2.1-PREVIEW-103_g4_N.img
[G4 Android Development] Frazzy:
Just to be sure:

Enable hci Bluetooth

Make a call

Pull log

Right?

I'm curious if something shows up though. It sounds like it's oversampling or something
[G4 Android Development] ntnlzr:
yep tnx u :)
[G4 Android Development] kessaras:
Don't you see the damn TWRP thread ?

It was the last TWRP question. Next time --> block.

It's making me so angry to see out of topic questions especially when they 've been answered one million times , and you are ignorant enough to keep avoiding the search button or even the Google search.
[G4 Android Development] Frazzy:
adb: error: failed to stat remote object '/sdcard/btsnoop_hci.log': No such file or directory

I did some searching and could this (https://stackoverflow.com/a/46674486) be the case? Or am I doing something wrong?

Frans
[G4 Android Development] tambukey:
The file they mention doesn't have any paths or anything indicating where the snoop log would be saved. Tried to do a log my self, and am currently searching through the whole phone to see if it showed up anywhere. Gonna be a minute.. Maybe because of the bt_stack.conf coming from an open source it should be edited for our phones?

Edit: found the issue through use of my old G3 with Lineage. Inside bt_stack.conf they have this:

#Enable Btsnoop logging function
#valid vaule : true, false
BtSnoopLogOutput=false
BtSnoopExtDump=false
#BtSnoop log output file
BtSnoopFileName=/data/misc/bluetooth/logs/btsnoop_hci.log
#Preserve existing BtSnoop log before overwriting
BtSnoopSaveLog=false

However this is Lineage and running android 7.1.2 so I am not sure of any differences But the rest of the bt_stack.conf on the G4 is roughly the same
[G4 Android Development] Frazzy:
In the message I linked they state this isn't true anymore in Android 8

But I can try to add it and see what happens. Do you have any thought about the missing BtSnoopFileName and BtSnoopLogOutput in the Bt_stack.config [MENTION=5461026]kessaras[/MENTION]?
[G4 Android Development] tambukey:
I added the lines and no logs took. I even manually entered true for taking log, and cycled bt and phone a few times but still no log.
[G4 Android Development] kessaras:
If I add/enable bt logging then you won't be able to remove it. It will log up 1gb file logs per week and they will all be useless. You won't find anything there for the Bluetooth problem.

The Bluetooth problem is an audio caf problem.

Or maybe I should give it a chance to the open source audioserver Hal to see if it will work or cause bootloop.

And if it works I will proceed further . It's not something you guys can find , test or fix.
[G4 Android Development] Frazzy:
Where can I find the source for the audio server? I want to satisfy my curiosity ;)
[G4 Android Development] kessaras:
nowhere , lol.

thats what i was looking right now.

there is no opensource for that, f*ck.......

we r stuck with LG sh*t.

anyway , its a hard one. i got no idea how to fix it yet and anyway the bluetooth logging is useless. Just wait until steadfasterX has time to team up with me so we try fix it.
[G4 Android Development] Frazzy:
I really have to read up on this. In my eyes this problem should be as simple as one setting somewhere. Everything works great but only the sound coming from the phone is to loud for Bluetooth.

So if we could disable the amplification or lower the input volume. It should bring us back to Android 7 quality.

If only I had as much time as you...
[G4 Android Development] Minto107:
I have aptx compatible headphones and with or without module, it reverts back to SBC. Sadly, I have no other Oreo enabled device to check if its phone fault or maybe some incompatibility with headphones(will give you respond 6 months later when my tablet will receive Oreo lol)
[G4 Android Development] tambukey:
Yeah the apt-x has nothing to do with the issue. It is just a compression style. I just tested it with that, and either it is because in dev options nothing other than sbc will stick or it just doesn't work for this device.

Edit [MENTION=5461026]kessaras[/MENTION] the rild bug occurred on my phone again. Sorry for no logs, if they even really help, I stopped it before I considered a log.

https://drive.google.com/file/d/1oQjUmDpAxD1Cla98aVu38WxTvXtSzaZ0/view?usp=drivesdk
[G4 Android Development] Minto107:
Battery life in standby seems very solid. 8 hrs less than 8% used with 3G, WiFi, Bluetooth and high accuracy location on
[G4 Android Development] SeewolfPK:
This morning I do not trust my eyes. My device running 24 hours and battery using only 25%.

Never before have I had such good results.

I say: double Thumbsup for [MENTION=5461026]kessaras[/MENTION]
[G4 Android Development] DosenHatti:
Same here battery +++

THX [MENTION=5461026]kessaras[/MENTION]

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] obvious:
Well it looks like another full wipe for me lol. Lost 30% overnight and can't see what used it.
[G4 Android Development] kessaras:
It's only Minto who realised that we r running on performance governor. Otherwise I wouldn't know.

At least not any time soon.

And think that before I fix it, you run a whole day on performance with CPU locked on 1800+ mhz
[G4 Android Development] DosenHatti:
So then this THX goes [MENTION=5387684]Minto107[/MENTION] as well

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] SeewolfPK:
I also have to say: THX [MENTION=5387684]Minto107[/MENTION]
[G4 Android Development] Minto107:
You're welcome guys ;) glad I could help making this great ROM even better ;)
[G4 Android Development] obvious:
Fame doesn't fulfill you. It warms you a bit, but that warmth is temporary. Remember the little people ;)
[G4 Android Development] Minto107:
We're all equal ;) some of us know more stuff, some are younger but together we can do more and that's the thing ;)
[G4 Android Development] obvious:
Lolz
[G4 Android Development] Lurensu:
Yeah thank you [MENTION=5387684]Minto107[/MENTION]!

Anyway I've noticed that the big cores are turned off all the time, or at least this is what both CPU-Z and kernel adiutor say.

[MENTION=5461026]kessaras[/MENTION] should I trust them?
[G4 Android Development] fi5z.x9:
[MENTION=5461026]kessaras[/MENTION] please could we get some of those new power tweaks for the next nougat patch release too. :angel:

Great team efforts guys. Thanks. :svetius:
[G4 Android Development] ThePiGuy:
I completely re-did my system (the AOSCP source was the only stuff on it anyway as I only recently set it up) by reinstalling Ubuntu and re-running repo sync. I then used ". build/envsetup.sh", followed by "brunch aoscp_h815-user" (I hope that last command is correct - I didn't want the user debugging stuff. Unfortunately I got the same error again, and it fails at 35% built

I don't have a log file, as I don't know where to find one (if it exists and you know where it is, then please tell me and I will be happy to provide it), but I have copied the last portion of my terminal output into a txt file and attached it below.

Thanks for your help
[G4 Android Development] steadfasterX:
Ok just a little off topic but I must leave it here:

I run latest titan on marshmallow RR now :laugh: don't ask how ;)

Super smooth so far.. I'm excited about how the battery life goes...
[G4 Android Development] ntnlzr:
i suggest to build userdebug version instead of user version
[G4 Android Development] ThePiGuy:
What differences would there be (I sort of assumed the userdebug version would create logs I didn't want - maybe this isn't the case)
[G4 Android Development] Minto107:
Enable them in kernel adiutor ;)

Wait... You run Nougat kernel on marshmallow ROM? Wtf[emoji23][emoji23][emoji23]
[G4 Android Development] Lurensu:
How should I do it? (Sorry but I'm a noob for this stuff)

Kernel adiutor only shows 4 cores
[G4 Android Development] Minto107:
Try to disable core control first(it's in thermal) then force close kernel adiutor and try again. If it wont work try to disable core control and make it apply it on boot, reboot and try to enable big cores ;)
[G4 Android Development] ThePiGuy:
Has this fix been merged into the main cypherOS github, as I am building my own version (mainly for satisfaction purposes) and I am interested as to whether this will be in it.
[G4 Android Development] steadfasterX:
:) you got it. I love to hack.. ;)
[G4 Android Development] Minto107:
Holy **** [emoji23][emoji23][emoji23] how much SOT do you get out of this?
[G4 Android Development] rotoko:
after the latest update, the kernel is working properly ...
[G4 Android Development] kessaras:
big cores should not be disabled.

at least they are not for any of us.

i didnt tweak anything. i simply fixed the errors i had. this battery consumption in O is normal because O has a better standby/sleep algorithm than N.

remove it locally

https://github.com/CypherOS/device_...e771deffe68bd7803fcfc/sepolicy/hwaddrs.te#L11

i can't remove a rule that doesn't give me a never allow error in Official or locally or at steadfasterX server.

building user is your problem for the error you get. user is even more strict.

userdebug won't flood you with annoying logs. only 1 thing is extra logging. the prebuilt loc api2 by LG.

Nothing else will log anything extra. i have removed the most annoying and useless logs when i fixed the bugs there.
[G4 Android Development] Lurensu:
Thanks man, this did it!

Anyway now VDD restriction is disabled all the time, I hope that's fine (it should limit voltage I think)
[G4 Android Development] ThePiGuy:
Ok. Building as userdebug has not given me the error, so if there are not many logs being created then I am happy to use that instead of user
[G4 Android Development] MatteoB92:
Because drivers/modules are into kernel, this could mean no bt call bug with the hack? [emoji7]

Inviato dal mio LG-H815 utilizzando Tapatalk
[G4 Android Development] steadfasterX:
The bt issue is complete another story.
[G4 Android Development] Lurensu:
Did you guys notice a stange behaviour of the vibration on the latest build?

When I press a button of the navbar it feels like it vibrates 2 times and also it vibrates when I pull up the notification list and when I unlock the phone.. is this normal? ?

It wasn't like this on official
[G4 Android Development] MatteoB92:
Sad to read this, but seeing an answer from you let me hope for the future status of development of Oreo [emoji256]

Inviato dal mio LG-H815 utilizzando Tapatalk
[G4 Android Development] kessaras:
Ye it was always like this normally. Before this build, in O at first, I used wrong vibration hidl**. I noticed yesterday.
[G4 Android Development] steadfasterX:
Well yea I'm working almost every day together with kessaras but we both have different focuses atm ;)

Once I have finished UsU (unofficial unlock) I can very likely help more...
[G4 Android Development] kessaras:
stead, https://github.com/CypherOS/kernel_...ers/input/touchscreen/touch_synaptics.c#L6771

haha ! Sh*t LG
[G4 Android Development] steadfasterX:
Hahaha unbelievable..
[G4 Android Development] fackuu94:
Hello, Im in Nougat room version from 1st January....its recommended update to the version to 1st february? there are bugs or something like that?
[G4 Android Development] kessaras:
https://play.google.com/store/apps/details?id=com.cabooze.buzzoff

and the premium one is even more customisable.

you can disable the internal dnd to save the 1 or 2 cached ram blocks it reserves (but who cares for so little ram amount)

and use the one from playstore. it will give you full control over dnd and maybe even better so that someone (who is in danger or something important) can find you.

EDIT::

stock aosp is always pure and clean for the reason that we can do whatever we like without having extra bloat.

Also the pie you use , its good that it works for you that way. Since you get a clean rom with nothing on , you r free to transform it to whatever you like.

And thats one reason i dont understand those who like the stock based roms since they can have a clean aosp transformed to whatever they like.

Htc ui ? lg ui ? samsung ui ? there is no limit
[G4 Android Development] wadken1:
That's sounds like a good idea but I would need to know what the APN parameters should be. Are these normally available from my service provider website?

Also, just found an odd thing. My selected APN is freedompop ! Whereas my provider is Three UK. Tried switching it but it failed to connect. Don't know what's going with that at the moment.

---------- Post added at 10:10 AM ---------- Previous post was at 10:01 AM ----------

That app looks interesting but I've also noticed that CypherOS has built-in "do no disturb" feature in settings. I might give that a try first.
[G4 Android Development] marn3us:
Yes, they should be available on your provider's website :)

Try to reboot and select the correct APN, then double check that all parameters are correct (and clear the proxy value).

I hope it helps, let me know if it worked!
[G4 Android Development] wadken1:
Weird stuff happening:

Edited my service providers APN to the published values, selected it and tested without reboot. It worked but I found that it the phone had reverted back to the freedompop APN. I deleted it and reselected by edited APN and tested, didn't work. Rebooted, connection made no problem but then found that the phone had used a different APN without all the correct parameters. I'm going to delete all except my edited APN and see how that goes.

Edit: finally got accurate APN details and reduced entries to just one. It now appears to be working well. Ultimate test will be tomorrow morning after a night in size mode. I'll report back then.
[G4 Android Development] tulen_kobi:
Well I do not think that using Marsmallow bootloader and modem is a good idea at the Nougat rom. As this rom is build against Nougat kernel sources and using Nougat hw blobs.

You can technically use Lollipop modem on Nougat rom but it can cause issues.

Another ROMs(except unofficial LOS) use old marshmallow sources so there flashing Nougat bootloader and modem is not necessary.

Can somebody clarify this to be sure?
[G4 Android Development] tmihai20:
Well, I made a flashable zip just for the modem only, I am still on MarshMallow bootloader. Everything is working as it should for me.
[G4 Android Development] deltadiesel:
Its not necessary here either

Only time I flash a kernel is if there one released with it.

Flashing another modem is a big no no.

Sometimes there are other kernels you can flash on any ROM that is cyagen mod based like Sweet lama kernel. Or stock ROM based like imperium kernel.

Don't do that again or you really will overheat the motherboard (specifically the ram chip that sits on top of CPU) and will never get out of bootloop. You will end up having to purchase another phone

So everything is fine now?

Skip this step in the future

ROM has kernel and modem built in even if you were on MM......flashing another kernel and modem makes the device unstable

---------- Post added at 01:28 PM ---------- Previous post was at 01:24 PM ----------

Aoscp is like the real aosp version of slim ROM :good::)
[G4 Android Development] tulen_kobi:
Well if it is actually better not to use nougat bootloader and modem I would be glad. It is really pain in the ass to flash kdz on the v29 bootloader. The LAF(lglaf script for backup) not working on v29 bootloader. And the only option when you are stuck at the bootloader mode is to flash v20p kdz using the library extracted from the F500 variant of this device.

But when I flash nougat modem before flashing this rom, it has any impact?
[G4 Android Development] kessaras:
Why don't you all stop experimenting with things you don't really understand ?

Modem of 20p may work because the ril is the same.

Bootloader is not the same.

A bootloader update is not necessarily bad or overheating or what else I read past few hours. A bootloader update is done for mostly security reasons and nothing else. LG or any other company do not update the bootloader with the thought to lock us out , or block our mods , or block TWRP , or slow down the device , or whatever.

The bootloader updates are clearly for security reasons against hacker attacks , they usually fix a "hole" forgotten in the past.

Ok this time they added a really crappy font to the warning , but besides that they closed holes too.

So..... Keep your bootloader up to date and don't think about stupid things. Bootloader update won't affect your after boot experience
[G4 Android Development] marn3us:
Well said!

The new LG bootloader warning screen is ugly as hell though lol
[G4 Android Development] tulen_kobi:
You can download Kessaras's modded variant without the uggly screen: LG-H815_29a_Modem_and_Bootloader_no_splash.zip
[G4 Android Development] deltadiesel:
Whats it look like?
[G4 Android Development] conar:
So I switched from stock to Cypher and I'm getting perfect Bluetooth performance and it's staying connected to my MI Band 2. Thanks Kessaras!!!

I've a strange issue with whatsapp now though in that after a while running I no longer get notifications.

Reset and it works fine for a few hours then none. Not just on watch but on the phone too.

I removed whatsapp from battery optimisations in case that was causing it but no luck.

Is there something I'm overlooking here? No hidden wake lock blocker or anything?
[G4 Android Development] kessaras:
yeah. do a clean flash and do not restore apps using lame 3rd party app restorers. Google can restore your apps after completing setup and only later pick and restore the most important ones.

When you restore apps using 3rd party crap apps you break the gcm wakelock which is rensponsible for the messages apps to check for messages
[G4 Android Development] conar:
I actually did a clean flash and used Google to restore the apps.

Reckon it's still worth another go or is there something else that could be causing it?

Getting amazing battery life by the way. Almost 4 hours screen time on a battery that's 2 years old.
[G4 Android Development] kessaras:
it's gapps error when you don't get messages. Something breaks the gcm broadcast and receiver. I never had this problem personally so I don't know any other way to solve it than clean flash.

Maybe you can also try dirty flash again rom and gapps and see if dirty flash works too if that saves your time
[G4 Android Development] conar:
Will try that first so.

Thanks!!
[G4 Android Development] marn3us:
It's like a horrible screen with some horrible font and colors saying some sh*t like "Your phone cannot be checked for corruption. Please visit this website to get more information. Press power button if you want to stop boot"

It's really dumb LOL nobody is going to re-lock their bootloader just because they see that screen xD

Same problem with whatsapp happens to me as well (only rarely though) from the 15/10 update (I clean flashed and did not restore anything, neither with google nor 3rd party).

It is a bit annoying but I think that the improved kernel and amazing battery life are much more worth it ;)
[G4 Android Development] kessaras:
thank you for your kind words.

look, for the whatsapp issue you have its a gapps error. thats 100%. GCM broadcasts and the apps GCM receiver wakesup the app in the background.

It's not a rom issue so i can't fix it. (also here it works just fine , i use it too, its my main communication app) When you have more time, try a clean flash with a different gapps package.

Maybe on Sundays update , download new gapps and try again. Ok ? its google core apps issue and its (usually) caused from a bad restore
[G4 Android Development] deltadiesel:
I remember on my Motorola device there was a patch someone created that took care of that altogether..

It would look like normal bootloader.....even after it was unlocked

Did not say bootloader is unlocked....even though it was

I wonder why no one has done that

All it really was is changing a value to 0

Not sure how that works for lg g4 though, not a developer
[G4 Android Development] fi5z.x9:
Well, there's the updated security patch & I also believe that there are some other new tweaks included.

---------- Post added at 01:27 AM ---------- Previous post was at 01:25 AM ----------

Thanks for explaining that, but could nougat also get some charging time boost? ;)
[G4 Android Development] kessaras:
when i have time i always update my N.

EDIT:

Do not flash todays N
[G4 Android Development] mobidor:
What Gapps? There is 20180217 Gapps 8.1
[G4 Android Development] deezid:
Stuck on nougat right now, because the big cores died.

First tried freedom rom, didn't see the Los based version. But my phone felt like 2012 in terms of speed and really bad battery. Thought it was the 2 cores disabled...

Back to aoscp nougat with Los based Titan kernel. Phone flying again, like these 2 big cores aren't even off. And 3-4h of SOT at least.
[G4 Android Development] SeewolfPK:
I use newest from https://sourceforge.net/projects/unofficial-opengapps-8-1/files/arm64/
[G4 Android Development] kessaras:
Those who still use N ,

before you flash this build, keep a backup in TWRP.

It has february security patch and i'm testing something else too.

I updated to Oreo r36 latest google sources for N.

It will take a lot of time on reboot to start. it will rebuild cache and dalvik-cache.
[G4 Android Development] deezid:
Thank you will try.

Is it ok to flash Titan Kernel 1.8 (need the no big cores patch).

Would it make sense to disable the two big cores entirely?

I really don't notice any performance difference, but many people - me included - have problems with the 2 big ones.
[G4 Android Development] steadfasterX:
There is a guide where you can disable them on your own

https://xdaforums.com/g4/general/guide-create-custom-x-cores-boot-image-t3718389
[G4 Android Development] kessaras:
Would be better to make a flashable tool.

It's easy. dd to extract boot in tmp.

Unpack boot.img there (same way they do it in all in one kernel tool)

sed to find and write the command we want

Repack and flash.
[G4 Android Development] steadfasterX:
Lol sure. Do it..

I have already done about 60% of a flashable TWRP tool which can modify the cores but it's not finished yet. That's why I made that thread as I have not time to finish it yet but I wanted to help ppl in the meanwhile. It's all in the works...
[G4 Android Development] Minto107:
[MENTION=5461026]kessaras[/MENTION]

I noticed something weird, maybe it can(somehow?) help fixing RIL bug completely(read till the end). I noticed that if I restart phone RIL works sometimes correctly BUT if you plug USB in order to charge phone, it will ALWAYS work correctly(tried restarting few times, either its luck or it has something to do with it, especially when I unplugged and rebooted it couldn't start RIL correctly again). Maybe it has something to do with charge detection? (if you don't have charger plugged when booting, it won't show charge text on the bottom). Maybe it's just stupid luck or something, but maybe you can get something useful from that
[G4 Android Development] Lurensu:
Personally I restart the phone only when it's plugged all the time (because of the charging icon and text) and sometimes sim is not detected anyway.. even if I have to say that now most of the time it's recognized
[G4 Android Development] Minto107:
Well, damn. For me I don't remember time when it would not recognize sim when on charger, at least I think it has better detection ratio, but it's random
[G4 Android Development] MatteoB92:
I'll switch from stock, can I take it easy with a clean flash?

Inviato dal mio LG-H815 utilizzando Tapatalk