yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] shiftymccool:
Thanks [MENTION=4450173]camcory[/MENTION]! This had been an issue for me with a handful of ROMs but some have gotten it right. I know it's taboo to mention other projects specifically but if you want some working examples I can provide them on request.
[Nexus 6 Android Development] camcory:
Sure I don't mind mention of other teams (Just not negative). Most of us talk on a regular basis anyways.
[Nexus 6 Android Development] shiftymccool:
Ok, just thought I would make sure first.

The most recent ones I've used that work are Resurrection Remix (Neo) and AOKP (bthorne79). Not sure if LineageOS vs AOSP makes a difference but it seems to work more often on LineageOS than AOSP.

Let me know if you need more info.

Thanks!
[Nexus 6 Android Development] camcory:
Update

Ok long press power button for torch is working good. Double tap still needs lift to check enabled and the double tap needs to be fast (so this is still kinda wonky). If anyone wants to try I've uploaded to AFH you should have no issue with dirty flash as I have just done it a couple of times this morning.

Edit: This was a fresh sync so this is all in there. Gerrit
[Nexus 6 Android Development] gothy.gothy:
This is a REAL PROFESSIONAL,

BIG THANK YOU!
[Nexus 6 Android Development] shiftymccool:
WOW! Thanks for looking into it so fast! Unfortunately, I won't be able to try it myself for a few more hours. I'll report back when I can.

No kidding, that's some major response time there!
[Nexus 6 Android Development] :
Sometimes that happens to me using Google Messages and it happens to me on any rom. I didnt have it happen on this rom when I had it installed. Like you said though, sometimes.
[Nexus 6 Android Development] emraz786:
Perhaps there is some solution or advice to resolve this, as I would like to receive notifications at the time they are sent to me.

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6 Android Development] Feimitsu:
Did you perform a clean install? Could you post a screenshot of your Settings - Battery - 3 dots - Battery optimization screen?
[Nexus 6 Android Development] ChristianF2:
hi there, i experimented in video at full screen the nav bar don't hide i dont foun yet how to set, Anybody can help me out?
[Nexus 6 Android Development] Yoyomatx:
Go to setting-display-advance-expand desktop. This is how you hide your nave bar.
[Nexus 6 Android Development] ChristianF2:
Thank you

thank you it worked...
[Nexus 6 Android Development] Yoyomatx:
You're welcomed. I love this ROM. I'll keep this ROM until my phone is dead. :laugh:
[Nexus 6 Android Development] Feimitsu:
Anyone who did a clean flash can make a screenshot of Battery Optimization list? Thank you!
[Nexus 6 Android Development] wavedashdoc:
I'll be releasing AOSiP with the March 2019 Security patch this weekend. Stay tuned.
[Nexus 6 Android Development] Jason928591:
Update

Thank you for updating it!
[Nexus 6 Android Development] Guapo613:
You are the man ?. Too anyone using this ROM, get a new battery for your Nexus 6, you won't believe how much more smoothly your N6 will be.
[Nexus 6 Android Development] Feimitsu:
I'm asking this because, unlike in the stock rom or in LOS, there's no permanent whitelist on apps that don't need to be optimized. I made a test by optimizing all apps (including Google Play services) and now I don't remember what are the default apps not to be battery optimized for Nexus 6. Anyone?
[Nexus 6 Android Development] cujo6801:
Thanks a lot bro...

I really appreciate it...
[Nexus 6 Android Development] relaxable:
Thank you for your work!!!! (And the later post about another update coming).

I've been running older version of AOSip and kind of gave up on checking for update since VoLTE (Verizon) is so important to me and this rom has everything I need.

And I'm not ready to get a new phone - I think my next phone should be foldable so I can get huge screen, and I gotta wait till it becomes more available and affordable....

Anyway, I'm intrigued by this post as the statement that IMS is hacked to worth with PIE - can anyone provide a little more info about that - like what roms to try. Since I have 2 N6s, I'd like to give it a try on one...
[Nexus 6 Android Development] Yoyomatx:
How do you wipe cache partition on this ROM?
[Nexus 6 Android Development] wavedashdoc:
Weekend is here early.

Download:

https://www.androidfilehost.com/?w=files&flid=291328

Source:

https://github.com/wavedashdoc?tab=repositories

Includes all March 2019 security patches from here:

https://review.lineageos.org/q/topic:%22O_asb_2019-03%22+(status:open+OR+status:merged)

Thanks as always to [MENTION=4450173]camcory[/MENTION] and [MENTION=3383960]Elektroschmock[/MENTION] for their excellent work. And of course, super stable AOSiP.
[Nexus 6 Android Development] cujo6801:
Oh hell yes....

perfect perfect perfect...

You're the man bro....

Downloading now
[Nexus 6 Android Development] cujo6801:
Dirty Flashed and all's good..

thanks again bro...
[Nexus 6 Android Development] beeewell:
After dirty flash, Footej camera didn't work, but it did work after clean flash.

Thank you wavedashdoc for all of your contributions here.
[Nexus 6 Android Development] beeewell:
I couldn't get the flashlight to work on latest build. Anyone else? Works fine on previous build.

Edit: I clean flashed new build, and flashlight is working. It had been greyed out, so not sure what went wrong before. Thanks for the responses.
[Nexus 6 Android Development] sac164:
The flashlight works fine for me. I did a clean flash of the latest build.
[Nexus 6 Android Development] wavedashdoc:
No issues with the flashlight here. Is it greyed out? Log please.
[Nexus 6 Android Development] cujo6801:
Flashlight all good here too
[Nexus 6 Android Development] emraz786:
Does ROM not support Face Unlock?

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6 Android Development] Elektroschmock:
You need a gapps package which supports face unlock
[Nexus 6 Android Development] emraz786:
I installed with nano

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6 Android Development] emraz786:
Supported

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6 Android Development] cujo6801:
Nice little nugget to find on AFH today.....

Thanks bro....
[Nexus 6 Android Development] wavedashdoc:
So I've done a lot of work on this build. I've introduced minor over clocking with the CPU and GPU. I'm testing a some changes where the system ramps up the GPU first, before the CPU which appears to be keeping the phone cooler while increasing performance. I've also used a few commits from Vindicator Kernel that bring down the voltages across the table to keep the phone cooler. I haven't noticed any negatives from this. Also, standby time should be significantly increased.

For those that want to try this build here's the link:

https://androidfilehost.com/?fid=1395089523397924822

I've been running it for 2 days. Please provide feedback if you notice an increase in performance and better battery life.

And proceed with caution and make a backup. My CPU is binned very high at 13 so your mileage my vary.

Source for the kernel changes:

https://github.com/wavedashdoc/android_kernel_moto_shamu/tree/oreo-mr1-test3?files=1
[Nexus 6 Android Development] cujo6801:
So far I like it

seems quicker

little smoother and faster

Dirty Flashed....
[Nexus 6 Android Development] Feimitsu:
I remember when I asked for the chance of undervolting, and i've been bashed harshly. Thanks for bringing this to our Shamu :)
[Nexus 6 Android Development] RabbleCake:
i'm not sure if it's just me or franco kernel v77. I flashed franco kernel and afterwards it would just boot loop and the first time it went to a "decryption unsuccessful" state with password correct but data was corrupted. IT was working before so :eek:

Using https://www.androidfilehost.com/?w=files&flid=291328 build and latest gapps
[Nexus 6 Android Development] Elektroschmock:
For a reason!

Undervolting is dangerous, as ist might work on most, but not all devices.

Also a developer can't test it under all load and environmental cases.

So the general recommendation is: Don't do it.

Responsible ROMs even don't allow it: https://github.com/LineageOS/charter/blob/master/device-support-requirements.md
[Nexus 6 Android Development] wavedashdoc:
So the CPU frequencies are stock for the CPU. That hasn't been altered and like any ROM can be changed via a kernel tunning app.

The changes to voltages (screen mostly) I've made are here: (courtesy of old work from the Vindicator Kernel).

https://github.com/wavedashdoc/andr...mmit/b03f437f5d2dcebb67a124fbc44bea755049ad9d

If users have a noticeable problems, I welcome them to speak up. This is a test build, which I have thoroughly tested but I'm looking for feedback. I also properly warned users and hope they understand like all other ROMs and kernels, I accept no responsibility for anything that happens to their phones.

At this point I'm trying to push the device as much as possible and see where improvements in performance and battery life can be made this late in the game.

Heads up: I'm looking to change a few things based off my usage around BCL and thermals. I've noticed that watching YouTube videos runs the phone hot so I need to figure out away to prevent this with the current changes.
[Nexus 6 Android Development] Feimitsu:
We'll have to agree to disagree. I perform undervolt on any desktop/laptop I come across, and I notice only benefits from it. It takes a while to find the lowest possible voltages, but it's worth it. Having said that, I'm not sure if mobile chips binning is more accurate compared to desktop CPUs. It could well be that default voltages set by manufacturers are already near the lowest possible.

I understand that each device might have different tolerances, but it could also be there's a certain undervolt value that will be accepted by all devices. I am fine being a test user for this purpose :)
[Nexus 6 Android Development] wavedashdoc:
You can check your binned number for you CPU too. ( Sorry at work don't have the link, but it's here on XDA)

Mines a 13 which I believe the max is 15. So I'm undervolted on each frequency by about 20-25. This is my settings changed within kernel auditor and not default. Yes [MENTION=3383960]Elektroschmock[/MENTION], you're right there is a risk, but I would hope that users do enough research before undervolting. This is an enthusiasts forum, but I know we can't account for everyone so...

WARNING: CONTAINS UNDERVOLTING AND EXPIREMENTAL FEATURES. Proceed with caution.
[Nexus 6 Android Development] shann0ns:
Any suggestions on where to get a new battery?
[Nexus 6 Android Development] Guapo613:
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/391955509003
[Nexus 6 Android Development] wavedashdoc:
Hey guys, just a heads up the test build AOSiP-8.1-WVDD-OC10-shamu-20190324.zip might have an issue where TWRP no longer sees the data partition, as [MENTION=8887229]RabbleCake[/MENTION] had an issue when trying to flash franco kernel. I believe I have found the issue having to do with an incomplete F2FS commit which was reverted by Lineage just recently. But I would immediately backup ALL DATA on your phone to your computer just to be safe.

When booting into TWRP this evening, I was greeted by the unable to mount data warning, but was able to boot back into the ROM and backup before wiping.

I apologize for any inconvenience. I'd advise flashing back to the Stable March 2019 build here for now: https://androidfilehost.com/?fid=1395089523397914172

If you are having this issue, back up all data, and try flashing the march 2019 build. If unable, you will have to wipe.

Again, I apologize for any inconvenience. I'm working on a new build now, and reverting that comment and the undervolting just to be safe. Shamu is still my DD which I need working lol.

Update: I've talked to Camcory, it is due to this commit: https://github.com/wavedashdoc/device_moto_shamu/commit/53db1da9be9fcc9b59ea9dc8bf9e50fa24f225ff. He's saying that you will need to flash back to stock in order to fix the storage issue.

Update 2: Looks like you don't need to flash stock. Just wipe the data partition and flash ROM, Gapps and magisk. Boot into ROM and reboot the phone about 3 times. Then reboot to TWRP to see if it's fixed. I had to wipe a second time because it appeared to linger. I have reverted this comment and I'm building a new version now.

Update 3: Here is the thread post where this is acknowledged. https://xdaforums.com/showpost.php?p=79098691&postcount=265
[Nexus 6 Android Development] wavedashdoc:
Here is the fixed ROM: https://www.androidfilehost.com/?fid=1395089523397926681

I'm going to bed....
[Nexus 6 Android Development] dreamteam:
appreciate your effort
[Nexus 6 Android Development] Elektroschmock:
It has nothing to do with fs2fs, The commit itself is fine, it's just that TWRP can't deal with the changed partitions.

You just need to revert the commit and flash the build via sideload

After that it'll be fine as soon as a fsck has run which occurs usually after one or two boots.
[Nexus 6 Android Development] wavedashdoc:
Yeah, commit is reverted in the build I posted last night. I removed builds OC9 and OC10. OC11 contains all the latest changes.

I wonder if someone could modify our TWRP to support it. If I remember correctly [MENTION=5480152]followmsi[/MENTION] was able to make newer versions of TWRP for the Nexus 7. Perhaps he could do similar for us, if we ask nicely.

Also [MENTION=3383960]Elektroschmock[/MENTION] I'd like to propose a request. A) could we get a resolution switcher (aka 2k to 1080p) similar to the Galaxy Phones? Or B) could you point me to the file where I can set 1080p at boot. For whatever reason setting it through command line makes the recent zoom in and look in correct causing inconsistency.

Thanks again for everyone's understanding and support around the data storage problem.
[Nexus 6 Android Development] Feimitsu:
Can this be flashed from TWRP over the "faulty" ROM?
[Nexus 6 Android Development] wavedashdoc:
You can try TWRP, but I would suggest side loading through ADB like [MENTION=3383960]Elektroschmock[/MENTION] suggested.

Either way backup everything first.
[Nexus 6 Android Development] Feimitsu:
Just tried to reboot to TWRP but got the error you mentioned. I think I'll keep this ROM for now as I don't wanna lose the undervolt, and I don't use TWRP all that much really.
[Nexus 6 Android Development] wavedashdoc:
The new version I uploaded (OC11) still contains the undervolting.
[Nexus 6 Android Development] Feimitsu:
Alright thanks, I flashed the new build with adb sideload, rebooted 3 times, now TWRP detects the data partition correctly. Thank you!
[Nexus 6 Android Development] wavedashdoc:
Awesome. Thanks for providing feedback!
[Nexus 6 Android Development] wavedashdoc:
New build:

https://www.androidfilehost.com/?fid=1395089523397929775

This is a stability release:

- Reverted voltage changes to the screen. (This was causing the screen to display artifacts at low brightness levels on my device.)

- Implementing a safer thermal throttle that throttles at 55c but doesn't clock the CPU down as significantly.

- Improved GPU throttling

- Updated interactive settings.

here's the full list since Wednesday.

https://github.com/wavedashdoc/device_moto_shamu/commits/oreo-mr1-test2

Look forward to the April security patch as soon as Lineage 15.1 implements it.
[Nexus 6 Android Development] maddog3030:
Dirty flash on my wife's phone, even though she runs a slew of stupid apps on her phone solid so far.
[Nexus 6 Android Development] cujo6801:
Interesting I heard Google just put out an update for 8.1....

Anybody else hearing this?...

[MENTION=4183312]Droid_Life[/MENTION]: Not done yet! Google just posted the April update for it.

8.1.0 build OPM8.190405.001.
[Nexus 6 Android Development] wavedashdoc:
New Build:

https://www.androidfilehost.com/?fid=1395089523397931165

Change log:

- April 5th 2019 Security Patch

- Continued Changes to Interactive Governor
[Nexus 6 Android Development] Guapo613:
Is it possible to get the latest security patch/ update to the ROM without the changes to the governor?. In other words, just stock AOSiP 8.1 with April security patch?
[Nexus 6 Android Development] Elektroschmock:
Why don't you compile it yourself if you have special needs?

It's far from being rocket science.
[Nexus 6 Android Development] Guapo613:
Why so testy???. All I did is ask. Some people call a plumber while some fix it themselves. Some people take their car to a mechanic while some fix it themselves. Some people compile their own ROMS while some come here looking for help.

It's really no big deal at all, no need to get salty.
[Nexus 6 Android Development] Elektroschmock:
I didn't mean to sound testsy. I guess it's the language barrier causing me to not always find the right tone.

What I meant is that it's unlikely that [MENTION=3777325]wavedashdoc[/MENTION] will provide a seperate build for every user.

When you asked for a build without the changed governor settings I implied that you have the knowledge to judge them and therfore should be able to do a build by your own.

But after looking at the code aI saw that you can always override those settings with an app like Kernel Adiutor or similar if you really don't like them.

So no need to compile anything.

And by the way your comparison falls short, because usually you pay your plumber and your mechanic while the people here do the development in their free time. ;)
[Nexus 6 Android Development] Guapo613:
Language barrier???, I thought we all spoke/type English here??........ lolololololol
[Nexus 6 Android Development] wavedashdoc:
On a side note, [MENTION=3383960]Elektroschmock[/MENTION] can you take a look at my device tree (oreo-mr1-test3) I've tried twice now to Port the QCOM power hal and have had no luck. The phone attempts to boot but gets stuck at the boot animation. What am I missing? Thanks again for the continued support of Shamu!
[Nexus 6 Android Development] Elektroschmock:
Yes, but it's not my native language.

I guess you should revert the equivalent of https://github.com/LineageOS/androi...mmit/5ec37737e95bb45759ad900b914b2e8ac769e568 instead of the commit you picked from atharvalele
[Nexus 6 Android Development] Feimitsu:
I am suffering spontaneous reboots with this build, until now it happened twice while fast charging. Also experiencing launcher (Pixel launcher from Gapps stock) soft crashes (no EM, just desktop goes black and icons get repopulated)
[Nexus 6 Android Development] wavedashdoc:
Try these settings in kernel auditor. This has been keeping my phone cooler as it doesn't clock up to OC as often.

I haven't made a new build yet with these changes.

Just a heads-up I'm in the process of implementing the Lineage QCOM Power Hal into AOSiP, thanks to the help of [MENTION=3383960]Elektroschmock[/MENTION] . Unfortunately I haven't had success yet, it's quite the challenge but we should benefit greatly from it once it's properly working.
[Nexus 6 Android Development] wavedashdoc:
New Build:

https://www.androidfilehost.com/?fid=1395089523397935891

1. Implemented QCOM Powerhal and Samsung mpdecision (HUGE thanks to [MENTION=3383960]Elektroschmock[/MENTION] for helping me troubleshoot and get this working over the weekend)

2. Updated kernel with latest LOS updates and security patches

Note: the Kernel will now hot-plug two cores correctly and there should be no loss of performance. The phone should run much cooler and stay at a normal temperature on the charger. Let the phone sit for about 10 minutes after first boot.

Quick back story, Google unfortunately gave us a half baked PowerHal and Mpdecision which is why you've seen countless dev's implement different hot-plugging solutions over the years in attempt to fix Googles blunder. Elektroschmock spent a good amount of time adapting the QCOM Power Hal to work properly with our device but that was only one piece of the puzzle. With the change to Samsung correctly working Mpdecision we should see huge improvements as these two work together and cannot benefit without the other.

In it's current state the ROM is working well, but there is still more to add to continue to improve it. But since this took most of my weekend, I'm taking a break for a bit. Take this build for a spin and let me know what you think.

EDIT: ONE MORE THING. DO NOT change anything with the kernel. It will mess MPDecision up and you will have to reboot.
[Nexus 6 Android Development] beeewell:
Thanks so much Wavedashdoc. :good: :good:

I clean flashed, reinstalled most of my apps, and all looks good so far.

If I'm not mistaken, previous builds either defaulted to, or had an option to launch camera via double clicking power button. I can't seem to find the option to do that now.

Did it go away, or am I not finding it? I'm using Footej camera.

Edit: Phone seems to be running warmer to the touch.
[Nexus 6 Android Development] wavedashdoc:
Are you seeing anything being repeated or spammed over and over in the log? Again, make sure you're not setting anything with Kernel Auditor or any kernel app. It should not be running warm. You should see two cores turn off when the phone screen is on but idle.

The double tap camera gesture is in Owls Nest -> Gestures -> AOSP gestures.
[Nexus 6 Android Development] beeewell:
Thanks Wavedashdoc,

I'll give it another go in the next few days and report back here. I should have searched settings for camera launch :crying:
[Nexus 6 Android Development] beeewell:
Clean flashed again. Took my time setting up & reinstalling apps. All is well so far. No heat issues to report. Great work Wavedashdoc !!
[Nexus 6 Android Development] wavedashdoc:
New Stable Build:

https://www.androidfilehost.com/?fid=1395089523397937303

Changes:

- Latest Lineage Kernel commits

- Removed Overclock for CPU and GPU (No longer needed with new QCOM PowerHal and MPDecision)

- Removed 268mhz lower Clock Speed (Again not needed anymore)

- Returned to stock stable voltages and throttling.

Note: I will no longer build the ROM with Overclocking as continuous testing with the new Powerhal gives us the same or better performance with stock frequencies.

Please provide feedback and enjoy.

Second Note: AGAIN DO NOT CHANGE ANY KERNEL SETTINGS OR MPDECISION WILL BREAK AND YOU'LL HAVE A BAD TIME.
[Nexus 6 Android Development] cujo6801:
Just wanted to say thanks for all the work you put in....
[Nexus 6 Android Development] Jason928591:
Just wanted to say thanks for the new rom builds! Only strange thing that I have noticed is that sometimes when I would plug my phone in to charge (or take off the charge) the battery percentage will jump up or down. It went from 100% full charge, to something like 90% when I noticed within a few minutes. My battery replacement is fairly new and cant say I have noticed this before. No clue if it's the rom or my phone (Or battery somehow). It just feels like a new issue.
[Nexus 6 Android Development] wavedashdoc:
New Test Build:

https://androidfilehost.com/?fid=1395089523397937518

Changes:

- Latest Lineage Kernel Commits

- Updated Interactive profile to test with new power hal

- fixed camera warning log spam (thanks to [MENTION=3383960]Elektroschmock[/MENTION] )

I will periodically release test builds. Please provide user feedback if you think this build is smoother, runs cooler, makes your bed better than the stable build.

Edit: Raise the hispeed freq to 883200 if it's too sluggish.
[Nexus 6 Android Development] dreamteam:
sdcard i/o is sluggish with 04/10 test1
[Nexus 6 Android Development] wavedashdoc:
That may be because of the test changes to the governor. Try upping the hispeed to 1190 and report back if you've already bumped it to 883200 or 960000
[Nexus 6 Android Development] Blaiser47:
On latest stable, for some reason Netflix just shows a black screen (no themes and no night mode). Is this just me? This is on a dirty flash. If just me, I'll clean flash and see if that fixes it. Thanks for your continued support for our device!
[Nexus 6 Android Development] beeewell:
Try installing magisk module liboemcrypto disabler.
[Nexus 6 Android Development] Blaiser47:
Thanks! I did that and also a few other things and it's working again, even with that module now removed. Weird but whatever.