yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] coolek33:
Quick. Someone mention [MENTION=4790322]kufikugel[/MENTION] and [MENTION=3087740]Jubakuba[/MENTION]! ;)
[Android Builders Collective] SteveMurphy:
All this talk about gambling is getting on my nerves, because no one has mentioned this yet, and I don't know why...

It is wonderful to see familiar names.
[Android Builders Collective] chykal:
Whiskey and cigarettes on the Muppets. Gotta love that.
[Android Builders Collective] Yank555:
YAOSP-M Changelog v1.04 - Angler only

Just reuploaded a testbuild for angler with fixed volume rocker music control.

It also includes a few changes to cpu freq behaviour :

- touchboost is lower than stock (freq.)

- touchboost uses in-kernel touchboost only

- touchboost only applies to the LITTLE cluster

- big cluster runs on lower min. freq.

- big cluster uses a slightly cooled down interactive governor (yankactive-like)

This, I hope, is a first step to lower battery consumption. As of now it's not a change in kernel code, rather interactive being setup differently for big cluster and changes to userspace touchboost (device repo).

A little feedback on the general behaviour (snappyness, lags...) and of course impact on battery life (esp. SOT) very appreciated.

Note : Obviously this only will work if you keep the kernel that comes with the ROM.

Download Link

JP.
[Android Builders Collective] indian84:
Will get back to you in a day. At work now.

EDIT - Do hell with work. I am flashing the build. Will report sooner now.

:P
[Android Builders Collective] VictorLapin:
My builds were *the* YAOSP, with hammerhead as my daily driver device I've just managed to make a build faster than [MENTION=2033478]Yank555[/MENTION] He keeps up the pace lately though :)
[Android Builders Collective] galakanokis:
Just flashed and testing but it's 2am so more reporting much later today. I never really used your built in kernel but EX so I cannot give comparisons to previous builds but I will let you know how usage with this one goes.

Volume to skip is working though.
[Android Builders Collective] dankoman:
lost cause, don't hold your breath for a response - you'll never get one. probably works for Bundesnachrichtendienst or something...

you'll get a response from this one eventually, if you're extremely persistent ;)
[Android Builders Collective] indian84:
[MENTION=2033478]Yank555[/MENTION]

Amazing build JP. Loving it so far. Smooth, fluid, no lags whatsoever. Running it for almost 7 hours with 1.45 hours of SOT and have 72% battery left.
[Android Builders Collective] mslatter:
Hey guys,

Just just returned my LG G3 (D850) which I built 5.1.1 Slim for, thanks to many folks here! Because AT&T won't offer Angler and my work provides my phone, I had to go with Shamu - which I'm absolutely loving. First ROM installed (within 2 hours of box opening) was Yank's YAOSP of course! Super smooth and a great introduction to a new device (for me). Curious though, does anyone build Slim6 for Shamu? I've searched and searched can't find anything recent (last couple of months). Or is Slim just sliding back out of the lime light?
[Android Builders Collective] Yank555:
There's no Slim6 yet as of now. I've based on AOSP and added those Slim features I used to have a daily driver for my angler. And ended up building it for all of my Nexus family (angler, shamu, hammerhead, flounder and flo).

As soon as there's new for Slim I'll be back building it, but likely gonna keep YAOSP going as well.

JP.
[Android Builders Collective] mslatter:
Well that would explain why I couldn't find it! LOL. Thanks JP, always thoroughly enjoyed your builds and all the effort you put in to this. YAOSP will definitely be a favorite for a long time to come!

Cheers.
[Android Builders Collective] indian84:
[MENTION=2033478]Yank555[/MENTION]

This should give you idea about battery life. Great mix of smoothness and battery for me.

Coming from Garry's PN build, I miss one touch data toggle on/off on quick tiles. Also long press same tile to enter mobile network settings.

Is it on your roadmap?
[Android Builders Collective] Yank555:
Nice, better than mine, but I guess bt being always on with watch and handsfree connected a bunch, plus high acc. location etc. I shouldn't be surprised ;)

Well one touch toggle, nope, cause I hate it :angel: I don't want to switch data off that easily lol I always changed that on my Slim builds :D

I consider a single tap should show details, like secondary action if it was in first row. esp. you won't get feedback what the state is when you're not connected (or connected to WiFi).

As for long press, doesn't it do just that ? ;)

JP.
[Android Builders Collective] indian84:
I'm OK with two taps to toggle data on/off.. But can you look at long press on the tile to enter below screen? I'm just checking possibility. I'm OK with the current implementation too.

I have a horrible LTE coverage in my city. So I am mostly on 2G, I turn on LTE only when I want to browse something.

But like I said, all up to you. I'm happy with the ROM as it is now.
[Android Builders Collective] indian84:
Forgot to add the image.
[Android Builders Collective] VictorLapin:
And why do you need it constantly in high accuracy mode, if I may ask?
[Android Builders Collective] Yank555:
That is exactly what I get on a long press on mobile data tile, or did you mean a different tile ?

JP.

---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------

Well for Google Now to stop bugging my it's not, tbh LOL

JP.
[Android Builders Collective] VictorLapin:
Hmmm, it doesn't for me
[Android Builders Collective] ezio84:
PureNexus mod 6.0.1-20160330 :D

Download for Hammerhead: https://www.androidfilehost.com/?w=files&flid=50100

Changelog:

- Recents: Fix for launching App from Recent Apps on first click

- Added missing ita translations

From last PN source:

- Powermenu Torch option

- Themes: add more customizable elements (e.g. packageinstaller tab)

- Definitive fix for the statusbar BT icon behavior

- angler: Add Vendor Overlay for CarrierConfig (ALOT of FIXS)

- Heads up new features:

* added an option to force heads up in all apps

* added an option to adjust the timeout of heads up notifications

* added an option to force heads up in certain apps (whitelist)

* added an option to turn off heads up from certain apps (blacklist)

* added an option to turn off heads up in certain apps (do not disturb)

Installation, tips, info: check the 6th post of this thread: http://xdaforums.com/showpost.php?p=55121776&postcount=6

PS: if you have problems, call A-team or clean flash.

---------- Post added at 11:36 PM ---------- Previous post was at 11:35 PM ----------

[MENTION=4911350]RobbieL811[/MENTION] glad to see you still around!! :highfive:
[Android Builders Collective] RobbieL811:
Yup. I'm still kicking!
[Android Builders Collective] Yank555:
They removed that dn tile saying it could be better ... if only ... lol

Gonna have to test this again ;)

JP.
[Android Builders Collective] Garrykd:
.... and as usual, the angler version :D https://www.androidfilehost.com/?a=show&w=files&flid=52030

.....and Hi Robbie..... still need a hacker? :p;):D

.
[Android Builders Collective] Yank555:
OK, so don't that say only stupid people never make up their mind ? :angel:

So ... to not appear to be in that category, I just added something that should be exactly what you hoped for ;)

Thanx go to Griffin, though, cause he kind of enabled me to actually go in that direction afterall ... a little secrecy for now, you'll love what he did !

Suffice to say, YAOSP will have cellular tile enable/disable data on click, show more detail on secondary click (when icon is used in top row) and it will open mobile details on long click.

Hope I can push the next update tomorrow, now sure there a few details to check still and it's past bedtime already, so no promise ;)

JP.
[Android Builders Collective] efan3719:
And here's the Flo version - https://www.androidfilehost.com/?fid=24459283995309232

... did i do it right this time [MENTION=2640853]Garrykd[/MENTION] ? :p
[Android Builders Collective] smartymcfly:
Is there somewhere that lists what you changed in "pure nexus mod" vs "pure nexus"?

I found it. Thanks anyway.
[Android Builders Collective] Garrykd:
:good:.... if anyone else is looking for the list of changes from official purenexus... both [MENTION=2095315]ezio84[/MENTION]'s and my op's have a list.... here and here :)

.
[Android Builders Collective] indian84:
Woot Woot. Thanks for considering man.

:highfive:
[Android Builders Collective] dharmabm:
I've installed it to both my Bacon and hammerhead, kinda interesting but not really usable as a daily. No camera and hardly any apps available but still fun to play around with. Easy to install with multirom
[Android Builders Collective] RobbieL811:
Cool! Thanks. I took a look at it, but never flashed it. The latest build I could find was from like a year ago. Looks like the guy that was working on porting it to OPO just quit. I opted to not flash anything. Would be awesome to have a fully working version! I'm ready for it!
[Android Builders Collective] mslatter:
Hey Ezio,

I couldn't find a shamu build for this, so wondered if you'd mind me trying to build off your Pure Nexus Mod content? I have the hardware, may have the time, and am willing to give it a go if you're OK with it?

Cheers.
[Android Builders Collective] ezio84:
Guys lol no need to ask! :D

You can do what you want with the source ;)
[Android Builders Collective] Mrcactuseater:
[MENTION=2033478]Yank555[/MENTION], does the YAOSP kernel from hammerhead support Zram?

Tapatalk'd from my Dirty, Hellspawn'd Mako
[Android Builders Collective] Yank555:
Better, it has zswap and it's in use by default. Why ?

Have a look here.

JP.
[Android Builders Collective] Mrcactuseater:
Excellent, no reason at all! I'm just curious?

Tapatalk'd from my Twisted, Yank'd Nexus 5
[Android Builders Collective] Natakranta:
Thanks!

My Flo couldn't live without those Italian translations update [emoji12]

In opposition to my Tapa signature, happy dirty flashing.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] formicae:
Finally made the jump from the last Hammerhead SlimLP to the latest [MENTION=2033478]Yank555[/MENTION] YAOSP build, just needed to find the time. Been three days and absolutely great so far, it's nice to see little Slim touches. Do you accept donations? I'd love to buy you a couple of beers or some sausage. If not, many thanks to you and your co-conspirators, at least.

One question: any plans to implement denser pattern locks? Getting used to 3x3 is rough (but all things considered, a small suffering). If there's an option, I've missed it.
[Android Builders Collective] Yank555:
Thanx for the kind words. No need for donations, I love to do this for the fun of it and learning experience ;)

Haven't considered it as I use a PIN ;) But should be no big deal to add, it's on the todo.

JP.
[Android Builders Collective] Setting.Out:
You should pop in and say hi in the bacon forum, but then again, you'd get hounded for development requests.. :)

Hope you're doing well.. :)
[Android Builders Collective] galakanokis:
Quoting myself here.

I may have spoken a little to soon on the volume to skip feature, it occasionally works. Seems pretty random when it works, like every other song kind of thing. I'll try to grab a log later if the kids don't drive me nuts or I watch the hockey game.

Battery life seems pretty good, no glaring issues anyways. Currently 10hrs off charger with 3hr 15min screen on with 62% remaining. I don't do anything fancy to save battery.
[Android Builders Collective] adm1jtg:
[MENTION=2033478]Yank555[/MENTION] or anyone else for that matter

HELP!!!!!!

Run into a MAJOR issue just with yasop 103 and 104 I think, didnt notice it before that. I will be talking on the phone and after about 10-15 min or so the user on the other end is no longer able to hear me at all. I can still her them fine. This has happened 4 times now. Let me tell you what I have done and the results and also have log files for you though I am afraid they are very long.

First three calls i just kept calling back and that solved the problem for the 10-15 min but it kept recurring. This was in my car on LTE on the bluetooth. So I was like ok my own fault I dirty flashed a few times.... So I reinstalled 104 completely clean and even manually installed apps and reset them all manually. Talking to my dad tonight (regular phone no headset) same thing happened again on this completely clean build. On previous build I was on elite on this new clean one I am on pure yasop. Your rom your kernel never loaded v4a or xposed at all. I did move the previous install of yasop to a secondary rom for later reference if needed and will move this clean one to a secondary rom as well. So yes I am using multirom but have been since the first build you released of yasop. The log from the 30th is when I had the issue 3 times .... going from memory but wanna say the time stamp should be around 11am or so... the log from the 31st (today) the problem occurred approx 8pm maybe as late as 8:30pm I was in a phone call afterall and didnt note the exact times, The first log i captured only errors to try and cut down what ya might have to look through the second long i captured errors and warnings just in case the first didnt reveal enough. Needless to say for me making calls is critical and will have to go back to stock on my primary until we can figure this out. Hopefully you can help me as I really love your stuff and am heartbroken I have to leave it even for this short period of time.

logs:

http://bit.ly/1opuNpL

http://bit.ly/1PIEaHh

http://bit.ly/25zqDxy
[Android Builders Collective] Yank555:
This is very odd, especially as there hasn't been any noticable change to the ROM in the last few versions that would affect shamu (kernel/device/vendor) ... in fact, last change to shamu was last security patch by Google (rebase on r22).

I don't think it's a ROM-side issue, as I'd have notices on my angler, as just as for you, I need my phone to work.

Can you validate the issue is not present on stock ROM ? Note that you are facing some kind of hardware issue ?

It's 3am ... and I'm pretty exhausted, so maybe I'm missing sth right now :angel:

JP.
[Android Builders Collective] adm1jtg:
Going to run more tests as I have older backups next up in testing is yasop 97a and the if necessary pure stock will report back but may take a while thats why i posted the logs in hopes something would show.
[Android Builders Collective] formicae:
Yeah, everyone uses a PIN, I should probably just get used to it, but I love just swiping a pattern.

Flashing your Flo build now, and using Opengapps Mini, I get infinite setup wizard closes. Any idea which gapps I can use? (used the same ones for Hammerhead without issue)

[on Flo, full wipe, factory 6.0.1 install, boot, root, install recovery, flash YAOSP build]
[Android Builders Collective] Yank555:
Keep me posted. I'll try to have a look at the logs when I can (just got up ;)).

I've been using PureNexua gapps, had strangely the same issue with opengapps on flo, though no idea why, as I'm running opengapps on my angler, but haven't cleanflashed in months...

JP.
[Android Builders Collective] runtime@xda:
[MENTION=2033478]Yank555[/MENTION] I have two things that don't work on latest YAOSP for Hammerhead. Double tap to sleep on statusbar and Volume rocker music controls (tried on built-in Music and PowerAmp).
[Android Builders Collective] Yank555:
Gonna test ... odd, fix for angler would have broken hh ? :(

JP.

Edit :

dt2s on statusbar confirmed non-working on angler as well, never noticed as I don't use i anymore since I added dt2s on navbar.
[Android Builders Collective] VictorLapin:
Banks Gapps were fine for me, no issues on Flo
[Android Builders Collective] Yank555:
volume to skip music indeed broken on hh ... damn

Kay gonna have to check both on shamu and hh...
[Android Builders Collective] runtime@xda:
Thanks! Dt2s on statusbar not a big deal at all, 'cause i don't use it either, but Volume rocker bug gave my ears a little "Uuaaarggghhh!" this morning :)
[Android Builders Collective] Yank555:
Hehe, well a broken feature in the ROM is a big nono to me ;)

Compiling a testbuild with hopefully fixed volume rockers, dt2s will be next...

JP.
[Android Builders Collective] runtime@xda:
That's why i reported a bug that didn't bother me.

I'll test a fixes build as long as you upload it and report back.
[Android Builders Collective] Yank555:
Good news is, the angler fix makes it work on hh, just tested, so next build will be fine on the volume skip track.

Gotta go now, but I'll fix the dt2s on statusbar plus one little more bug on a new feature to squash and a new build should be out tonight, I hope at least :D

JP.
[Android Builders Collective] mslatter:
Hey [MENTION=2095315]ezio84[/MENTION],

Forgive the noob question but my last build setup was quite extensive with adding custom drivers etc for the G3 and then specifying what model of G3 I had (d850) . I repo synced PureNexus last night to get a good base and then for kicks did a brunch while I slept. This morning I find the build was successful?!

It can't be that easy right? How / where do I add custom files to make sure it builds for AT&T, or are those modem files never touched? I saw a post this morning noting that I need to add Google driver files to the build's root directory (GPS, WiFi etc) which I didn't do... So I'm surprised it built successfully.

I haven't tried the test build yet because of these questions... I'm too scared. My next step will be to start adding your modifications :)

Cheers
[Android Builders Collective] Yank555:
Hehe, welcome to the world of Nexus ;)

I don't know for PureNexus, but I added vendor repos to the manifest of my ROM. If Nate did the same, it should be good, or if he has roomservice added and you brunched. the needed repos might have been added to your local manifest.

Check to see if you have vendor/moto repo in your sourcetree.

What sizeis the zip ?

JP.
[Android Builders Collective] mslatter:
Thanks JP! Damn I just saw your response as I headed to work. I downloaded the zip anyway and it is 369.62 but I am not sure if I should flash it LOL I will check the Manifest when I get home. It makes sense to add the vendor files though. That is why I thought it was odd that it built successfully. Thanks again for the tip and TGIF!
[Android Builders Collective] ezio84:
As suggested by Yank, check if the vendor files are in your source too. Otherwise the build process can end without errors but the rom won't be bootable.

Here's my local manifest if you want to set my custom trees:

https://github.com/ezio84/scripts/tree/mm/My_mods-commits_and_tips/local_manifest_backup
[Android Builders Collective] mslatter:
Thanks Ezio! I will check it out this weekend :good: Appreciate the direction!
[Android Builders Collective] Yank555:
File size sounds about right, so I'm confident it should be all good ;)

JP.
[Android Builders Collective] mslatter:
Clearly I need to understand exactly what happens when we flash ROMS and how some people permanently brick their devices.... Your note gave me the gahonies to give it a try, and it works like a champ. Thanks to both of you guys! I'll work on getting Nate's changes pulled in soon!

Cheers!
[Android Builders Collective] kantjer:
Building a ROM is easier than bricking your device.

Even if I really tried I wouldn't know how to brick my phone just by flashing a custom ROM.

But some users manage to find a way :D

Make sure you have a nandroid, in my experience things that can happen when something did go wrong with the build

ROM won't boot

Bootloop

Not everything is working as expected

In all those cases a nandroid is your friend
[Android Builders Collective] mslatter:
I've had bootloops many times since I started with the Nexus One, and you're right, almost every time a nandroid saved me. There was a time when I wiped everything.... including internal storage...which wasn't pretty but the phone had external storage, so I put a new ROM/Gapps on it and flashed it all back. But then I read about these guys that need to restore modem or write over certain parts of their phones somehow and they're permanently bricked. Because I don't understand how that happens, I'm a bit gun shy about just flashing away.... but maybe those are phones other than Nexus devices. One day I'll take the time to read up on how it all ties together =)
[Android Builders Collective] SteveMurphy:
I'm piping in here, just because I can. :cowboy:

As long as your recovery is in a separate partition (like the Nexus devices, and most others these days), there's almost no way to brick them because no matter the firmware flashed you can always boot into recovery and restore.

The problem and danger you could run into is when you do NOT have separate partitions for your recovery. I came from an old S2 variant (the i777, which still runs well, BTW) that has this; both the kernel and the recovery are built together, so there is no way to flash them independently. That made building/flashing extremely shady at times, especially if you decided to port. Samsung firmware's were the ones we had to deal with that would always flash modems and kernels from (mostly) compatible devices, and you had to preemptively replace modules and bins and a whole host of things to ensure your build/port would flash correctly, and not leave you with an expensive brick.

Hopefully I've offered a bit of reassurance for you to have faith in your builds - I'm sure you did great.
[Android Builders Collective] JaylanPHNX:
I remember back in the old HTC MyTouch4G days, when just rooting your phone could brick it if not done just right (and it strangely involved pulling the battery at just the right moment).

From my SlimTab Pro 8.4
[Android Builders Collective] adm1jtg:
Loaded back an old 97a nandroid with older elite kernel and been running it bout the last 5 hours or so made 2 longish phone calls and didnt have the issue on either call. Hopefully when you get time the logs will show something. No idea if it rom or kernel or some app on my phone or what but really looks like not a hardware issue as I havent been able to duplicate the problem on 97a at all. Will continue testing.
[Android Builders Collective] Yank555:
Both are fixed ;)

About to start compiling v1.05...

Here's a changelog of what is to come :

YAOSP-M Changelog v1.05

- QS Customization by Griffin Millender
- up to 3 dual (big) tiles on first row
- editor allows to populate first row with 0,1,2 or 3 tiles
(0 = same as now removed option to not enlarge first row)

- top row QSTiles support long click

- cellular tile behaviour aligned with WiFi and Bluetooth
- simple click toggles mobile data
- long click opens mobile settings
- secondary click shows more details

- add support for alternate WebView provider package

- fix double-tap to sleep on statusbar

- fix long press volume rockers when screen is off to skip tracks

- angler only : consider charging fast above 1300mA/h rather than 1500mA/h (lockscreen and battery LED)

- angler only : add vendor overlay for CarrierConfig (Thx to Beanstown)
- this could fix carrier specific issues (like WiFi calling etc.)

Building for 5 devices will take a bit, so I'll upload likely 1-2 tonight, the others tomorrow morning after a good night's sleep (have two such nights to catch up :D).

Only drawback on the QS Tile editor, dragging top row tiles (big, dual ones) will only work from the label, not the icon. For now that's the price to pay to have longclick on first row tiles. Will try to fix, took me hours til I actually figured out the issue, next I need to figure out a solution, but it's more than good enough to be pushed ;)

Huge thanx to Griffin for this !! :D

JP.
[Android Builders Collective] mslatter:
Thanks Steve, that actually provides a lot of reassurance. Flashing time! :good: