yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] corrsea:
I've hit a problem dirty flashing. Phone bootloops after updating all the apps then after about 5 minutes starts updating apps again, and so on.

MDsum checks out so download appears OK. I've tried the obvious such as wiping cache and dalvik both before and after flashing. Also removed layers and xposed but same result.

I've given up for now as it was getting a bit tedious and I've run out of ideas.

I'll probably redownload and clean flash tomorrow unless anybody has any other ideas?
[Android Builders Collective] JaylanPHNX:
Did you try wiping system along with caches? Sometimes that's the next best thing to clean flashing.

From my SlimTab Pro 8.4
[Android Builders Collective] Yank555:
Uh ... a very important info ... best is to remove layers before flashing. I don't think about it as I made a zip which removes system apps I don't use which also removes layers that I flash after the rom before first boot.

(At least this is very important on devices which have a separate vendor partition, which is where layers are stored, so angler and flounder, shouldn't be necessary on shamu)

As for xposed, no idea as I don't use it, maybe best also to remove it ?

So far I've never hit an issue, and I must have dirtyflashed a 100 times at least already, if not more ;)

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.93
[Android Builders Collective] VictorLapin:
I always flash with /system and caches wipe, like [MENTION=3195615]JaylanPHNX[/MENTION] suggested, never had an issue
[Android Builders Collective] rignfool:
What Gapps?
[Android Builders Collective] Yank555:
I use either opengapps (nano) or PureNexus.

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.93
[Android Builders Collective] rignfool:
Sorry... I was asking the guys with the FC's...

It sounds like an android version mismatch...
[Android Builders Collective] Yank555:
Oh, lol ;)

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.93
[Android Builders Collective] dharmabm:
Oh my, no props to dankoman? :P
[Android Builders Collective] Yank555:
Lol ... of course ;) switched when I got my angler because of 64bit, back then slimgapps 64bit wasn''t available ... and well, never clean flashed my 6p ever since ;)

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.93
[Android Builders Collective] corrsea:
Thanks for the suggestions guys.

I'll try a system wipe and report back.

For the record I'm using purenexus gaaps.

As to xposed JP I'd like to drop it as the only use I have for it is to install root cloak so that my banking apps will run. I'm pretty sure there is another way to install it but I'll research that once I'm up and running again..

Edit

Wiped system and flashed a different gaaps. Went perfectly.[emoji1] Thanks for the help guys.
[Android Builders Collective] pkelly517:
Put it in the freezer.

It sounds like the kernel thermal throttle isn't kicking in, and the reset hardware kicks in.

Google sent me a new hammerhead years ago for this very reason. Happened every time the dalvik/art cache was built.

Edit: Or do what you did

[emoji3]
[Android Builders Collective] corrsea:
That could have been the reason as the phone was running very hot during the process.

Anyway sorted now.
[Android Builders Collective] VictorLapin:
And hammerhead! :p

https://www.androidfilehost.com/?fid=24411628330026035
[Android Builders Collective] Yank555:
Seen that on HH, but must say never on shamu.

And thermal throttling is set to pretty low temps, so I don't think it was that (it'll throttle freq. at 70°c and go dualcore if it still rises at 75°c). Used to run mine at 80/85 all the time :D

But if you do run into sth similar, we can try to lower those settings ;)

JP.
[Android Builders Collective] adm1jtg:
got kinda an odd question... do you know what file and location the information for immersive mode is stored at? I dirty flashed another rom over yours (formatted system but not data) and it still has immersive mode on. The rom however has no settings built in for immersive mode. So wanted to look at the config file itself and see whats what... or maybe just remove the offending file so I dont have to complete wipe data. Would also be great to know so I could backup those settings for future installs of your rom
[Android Builders Collective] corrsea:
I doubt if the temperature ever got that high. From memory it got up to high 40s while in TWRP, probably a bit more while bootlooping.

Hopefully it won't happen again.
[Android Builders Collective] endomatic:
[MENTION=5790246]VictorLapin[/MENTION] [MENTION=2033478]Yank555[/MENTION] Who are we gonna have to pay to get a Bullhead build around here??
[Android Builders Collective] Yank555:
Well in the settingsprovider DB somewhere, it's not a separate file, it's where all the settings go.

Commits are here 1 & 2

But I don't see how this would be working (at least not per app) without at the very least the frameworks_base commit ...

Hmm ... someone who owns a bullhead, I suppose ;)

Sources are all up, all it needs is the device repo, shouldn't be too much trouble, but without the device, too timeconsuming, and time is like the ring .. you know ... precious :D

JP.
[Android Builders Collective] dankoman:
i'm sure there are many people willing to maintain bullhead if you ship them a phone ;)
[Android Builders Collective] rignfool:
[MENTION=3292224]franciscofranco[/MENTION] has stated that shamu, regardless where the throttle is set... Will start to pull cores out at 36°C

He has been fighting it since he has removed all active hotplugging from his kernel...

FYI
[Android Builders Collective] Yank555:
Odd !?

I monitored my cores all the time on shamu, never had an issue with that on my kernel ? I'm using faux's intellithermal, though, don't think he's using that in his kernels. So stock thermal control is not active in my kernel (if kernel config is set accordingly, which is the case if you use the ROM as is with included kernel).

Will recheck later tonight with that in mind.

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.93

EDIT :

Thanx for this, cause that made me realise I forgot something in the device tree, to disabled that ;)

This core shutdown is Qcom's bcl (battery current limit), it will also do that if it detects unstable current coming from that battery, a hardware flaw on many shamu (all ?) :

--> https://github.com/SlimRoms/device_motorola_shamu/commit/5f35c43408fffcc2baadacc4fc79b79541d41a94 (this is in ramfs, could also be disabled by default in kernel sources)

shamu is recompiling with that corrected !

Note this will indeed make shamu go dualcore at 36° if it's enabled.

Proof it's working, see attachment.
[Android Builders Collective] Yank555:
Updated YAOSP-MM v0.93 shamu build is up :

Look at the build date, you need v0.93 dated 20160212.

This includes disabling bcl (makes your device go dual-core on lower battery, or CPU temps above 36°)

Changelog & Download links : https://github.com/YAOSP/manifest#changelog﻿

JP.

PS: Github shamu device repo updated.
[Android Builders Collective] adm1jtg:
Is your kernel Cm compatible? Aka if i pulled the boot.img and flashed it would that be 100% functional? Just looking at options till you get answers bout wifi calling.
[Android Builders Collective] Yank555:
I would be very surprised...

But you can achieve the same with an init.d script.

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.93
[Android Builders Collective] Mrcactuseater:
What app is that you're using to monitor that?!

Tapatalk'd from my Twisted, Yank'd Nexus 5
[Android Builders Collective] DroidIt!:
Looks like 3c toolbox ;)
[Android Builders Collective] Mrcactuseater:
Thanks [emoji4]
[Android Builders Collective] adm1jtg:
how would I do that as your yankactive governor doesn't appear to be on any other kernel an I am sure t here are other tweaks like the above mentioned thermal stuff that also aren't in other kernels
[Android Builders Collective] Yank555:
It's not the governor ;) Governors control freqs. not plugging.

You just need to disable bcl, just add an init.d script with this :

echo "disable" > /sys/devices/qcom,bcl.39/mode

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.93

---------- Post added at 09:22 ---------- Previous post was at 09:21 ----------

It is ;)

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.93
[Android Builders Collective] hlxanthus:
Really liking this ROM, just the right level of mods and tweaks. Will you be releasing only here? Just want to know where to keep an eye out!
[Android Builders Collective] Yank555:
Best is to follow me on Twitter or G+ (links in the link you quoted above), I always post there whenever there's an update available.

Keeping an eye here should do, too, I tend to not forget to post here as well ;)

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.94
[Android Builders Collective] adm1jtg:
I meant to gain the FULL yank kernel experience on Cm like in the original question
[Android Builders Collective] dharmabm:
Some of us don't use Twitter or trust Google, so please keep posting here! :P
[Android Builders Collective] kantjer:
[MENTION=2033478]Yank555[/MENTION] is nav bar button glow working on your Angler build?

We cherry-picked your nav bar commit on our Twisted build but I can get the button glow working.
[Android Builders Collective] Yank555:
Yup, working fine ... weird.

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.94
[Android Builders Collective] Real_Justus:
Please don't stone me... I am pretty stuck trying to get ROOT on the YAOSP 0.93. I did the standards and flashed latest SuperSU. What would be the right way?

Gesendet von meinem Nexus 6 mit Tapatalk
[Android Builders Collective] VictorLapin:
YAOSP-MM v0.94 for Hammerhead: https://www.androidfilehost.com/?fid=24415232478676356

Changelog: https://github.com/YAOSP/changelog/blob/YAOSP-MM-6.0.1_r13/changelog/YAOSP-M_Changelog.txt
[Android Builders Collective] Yank555:
No clue ... I still use "good old" SuperSU 2.52, never failed me so far...

I always flash :

- ROM

- gapps

- SuperSU

What exactly are the symptoms ?

JP.

---------- Post added at 01:40 ---------- Previous post was at 01:39 ----------

What exactly is the issue ? No glow, color not applied ... ?

JP.
[Android Builders Collective] hlxanthus:
For the record, 2.67 SuperSU (but it installed in system, wierd) is working just fine for me here on shamu. I flashed ROM and open gapps (full) and booted (didn't realize it wasn't prerooted). Then I rebooted to recovery and flashed su.
[Android Builders Collective] Yank555:
I've added that info to the Download section of the readme on github, thanx for pointing that out ;)

JP.
[Android Builders Collective] dharmabm:
I'm having the same problem but didn't post because I'm running as secondary in multirom, tried both 2.65 and 2.67. No errors when flashing, it says successful. Will try again with the latest build.

---------- Post added at 01:10 PM ---------- Previous post was at 12:14 PM ----------

*update* well, I just clean flashed everything (still in multirom) and everything is working fine now. Go figure! :P
[Android Builders Collective] kantjer:
I can select the glow color in settings as expected but regardless of what I set it it's always stock white.

The selected color just isn't applied.
[Android Builders Collective] Yank555:
I seem to remember running into this ... is this correctly applied in your pick ?

https://github.com/YAOSP/frameworks...2775#diff-3d9c8edc9e8835b2c0d1e4485edc4320L78

An this obviously :

https://github.com/YAOSP/frameworks...2775#diff-3d9c8edc9e8835b2c0d1e4485edc4320R85

JP.
[Android Builders Collective] Real_Justus:
Thank you for fast response! I simple have no idea, what went wrong. But Victor postet the v0.94. I flashed the Hammerhead just as usual - and all was good. I thought, that the Version was the issue.
[Android Builders Collective] limjh16:
Could anyone help? Having this problem when trying to compile slimsaber. This happens with/without compiling with ubertc. Roomservice if that helps debugging.

I tried this and this is what I found.
[Android Builders Collective] kantjer:
thanks, those changes are correctly applied.

for now I can't find the cause but I wil keep searching
[Android Builders Collective] ezio84:
Hey fellas! :D

Got back trying custom roms. stock aosp has become boring after all these months :D

Atm i'm on PureNexus, here's a commits list if you want to add some features to the official build:

https://github.com/ezio84/scripts/blob/mm/My_mods-commits_and_tips/Commits-list-with-links.txt

Here's the actual changelog if you want to sync and build with my local manifest (Click:

Added Slim Recents

Long press on recent button to switch to last app: remove custom animation and switch back to the stock aosp one (from bottom to top)

Show icon of package associated with Toast

Charging connected/disconnected sound notification

Let's use the home button during a ringing call

Built-in htop terminal task manager

Set animations speed back to 1.0x instead of 0.5x under Dev settings

Removed apps:

HTML Viewerp

Aosp Messaging

Add back mka bootzip

Added missing italian translations for the main Settings menu and some Framework/SystemUI parts

Other very good roms i'm trying with multirom: Yank's, Twisted, Krexus.
[Android Builders Collective] chykal:
I am running the [MENTION=2033478]Yank555[/MENTION] build that [MENTION=5790246]VictorLapin[/MENTION] posts for hammerhead. It is running very well and I enjoy the regular updates. Thanks guys!

Is there any chance of getting the status bar brightness control added? That is the only feature I miss. Everything else is perfect.
[Android Builders Collective] kantjer:
Welcome back my friend.
[Android Builders Collective] ezio84:
Thanks B!!

I was always lurking you guys, thank you too for all the work on your builds ;)
[Android Builders Collective] randman2011:
Well, looks like life is coming back to this thread. I guess I'll have to follow through on my promise to being up the bullhead device tree so us 5X owners can profit from Slim again.

Anyone know of any guides or something that I can read through? I'd have no idea what I'm doing.
[Android Builders Collective] chykal:
I used to follow your builds here religiously. Looking forward to seeing more from you.
[Android Builders Collective] ezio84:
Slim still hangs, so you could use a ready bullhead base, like Twisted :good:
[Android Builders Collective] csolanol:
Yummy!
[Android Builders Collective] hooliganx:
[MENTION=2095315]ezio84[/MENTION]

unless, till now, working good and 3 days of calls. on and off ear... speaker working perfectly. and don't notice nothing wrong with screen

n5sk8.8.aow10.26artgapps327

codeblue.r450rd2.21v4atwrp2.8.0.1

------------------------------------------------------------------------

doubts about Slim? click here:

http://slimroms.net/index.php/faqandmanual
[Android Builders Collective] ezio84:
Yes [MENTION=5497766]aow1980[/MENTION] was telling me now that at least the speakerphone seems to work with patchset 1 on hammerhead.

Patchset 3 (the one with BT/headset logic) has no way atm :(
[Android Builders Collective] ralpheboyo:
Man E.... This is now my new girlfriend... Loving Kate... Thxs for the heads up...
[Android Builders Collective] ezio84:
:D :D

Check also its keyboard shortcuts configuration, there's some good stuff (i like the CTRL+B one).
[Android Builders Collective] ralpheboyo:
Will be building again to include (touchscreen firmware update)

https://gerrit.slimroms.net/#/c/15996/
[Android Builders Collective] nooktablet:
[MENTION=2095315]ezio84[/MENTION]

Can you make your unofficial ROM use Google now launcher by default?
[Android Builders Collective] ezio84:
Now the default launcher is the Slim one, but you can install and set as default any launcher you want in Settings->Home Page ;)
[Android Builders Collective] Minux31:
I've built for the opo with this, if someone want to try : https://s.basketbuild.com/filedl/de...-4.4.4.build.8.9-MinuxBuild-20141028-1854.zip
[Android Builders Collective] ralpheboyo:
running a couple hours now...slight improvement...on first boot device got warmer than ususal but settled in quickly...will continue to test...but so far its good...
[Android Builders Collective] csolanol:
Hey [MENTION=2095315]ezio84[/MENTION], what happened to the stove?. Is it chilled?
[Android Builders Collective] ezio84:
Just strengthening the build :laugh:

Yesterday i did again a couple of tests about the auto speakerphone feature (without success lol, but Slim guys are still working on it) and catched some fixes like this one (useful with popups like pushbullet ones):

https://github.com/ezio84/frameworks_base/commit/8a1cfb4726338135f9bbc9b60c865df1aaf15a57

and no more LSnotifications FCs when using face unlock (thanks to [MENTION=842211]Grondinm[/MENTION] ).

And there are some new Slim Launcher features like advanced gestures, [MENTION=4527723]gmillz[/MENTION] is doing an amazing work :victory:
[Android Builders Collective] csolanol:
Ok Thanks. Waiting patiently :eek:
[Android Builders Collective] Grondinm:
Updated Multirom TWRP re-packs are going up now.

EDIT: And of course...as soon as i do this new version of TWRP comes out
[Android Builders Collective] ezio84:
Slimkat Mod 8.9 for Nexus 4 (mako) and Nexus 5 (hammeread) :D

Mako and Hammeread download: https://s.basketbuild.com/devs/ezio84-xda

Tips of the day:

- The Slim Launcher is updated with today translations and the new advanced gestures, try it!

Changelog:

Project name: hardware_qcom_keymaster

*Hariprasad Dhalinarasimha - qcom: keymaster: Include keymaster in all targets

Project name: vendor_slim

*Josue Rivera - Bump to 8.9 for weekly

Project name: device_lge_hammerhead

*Jubakuba - Hammerhead: Add device overlay for proximity wake

Project name: frameworks_base

*ezio84-xda - By Paranoid: Floating window Fix possible NPE

*gwindlord - fb: translation - RU

*Jubakuba - Framework: StatusBar Ticker (1/2)

*Jubakuba - Framework: Don't collapse if showing quicksettings

*Jubakuba - Framework: Don't needlessly create shared pref objects

Project name: packages_apps_SlimCenter

*ezio84-xda - updated faq link

Project name: packages_apps_Settings

*ezio84-xda - LSNotifications: fix npe when using face unlock

*Jubakuba - Settings: StatusBar Ticker (2/2)

*ezio84-xda - Strings about proximity wake are fine, restore them

*ezio84-xda - Revert "Settings: Update ES translations"

*Carlos Solano - Settings: Update ES translations

*gwindlord - Settings: translation - RU

*ezio84-xda - Strings about proximity wake are fine, restore them

*ezio84-xda - Revert "Settings: translation - RU"

*ezio84-xda - Revert "Merge "Settings: update DE translation" into kk4.4"

*ezio84-xda - Revert "Merge "Settings Cleanup and Reorganization: italian translation" into kk4.4"

*gwindlord - Settings: translation - RU

*Andreas Blaesius - Settings: update DE translation

Project name: packages_apps_SlimLauncher

*Andreas Blaesius - SlimLauncher: initial Dutch (NL) translation

*Andreas Blaesius - SlimLauncher: Update PL translation

*Andreas Blaesius - SlimLauncher: Update IT translation

*Andreas Blaesius - SlimLauncher: Update EL (Greek) translation

*ersersoy - SlimLauncher: Update TR translation

*Andreas Blaesius - SlimLauncher: update DE translation

*Andreas Blaesius - SlimLauncher: Update ES translation

*gwindlord - SlimLauncher: translation - RU

*Griffin Millender - Cleanup I missed

*Griffin Millender - Fix last app

*Griffin Millender - Add hide homescreen indicator

*Griffin Millender - Add last app

*Griffin Millender - Add more gestures

*Griffin Millender - Ability to hide dock

*Griffin Millender - Add permission for widgets

*gwindlord - SlimLauncher: translation - RU

*Andreas Blaesius - SlimLauncher: Multi-Language update

*Flamefire - SlimLauncher: Hidden-apps setting

*Danesh Mondegarian - SlimLauncher: Icon pack support

*Griffin Millender - First attempt at settings change without restarting launcher

*Griffin Millender - Remove Launcher Backup Helper
[Android Builders Collective] houbaba:
Hi Ezio84,

Your build has got a JustArchi's optimizations or not ?

Thank you for your work. :)
[Android Builders Collective] ezio84:
Post 6, click on "Additional features" and you'll find all info :p

Yes, build is compiled with O3.
[Android Builders Collective] houbaba:
OK i see that. Thank you.
[Android Builders Collective] Grondinm:
Updated Standard TWRP repacks to 2.8.1.0...gonna be working on a few new curtains this weekend if time permits...and i'll update the TWRP images as soon as it is out

Edit:And Multirom Done
[Android Builders Collective] Garrykd:
Sigh....had problems this morning and had to make clobber :(

The good news is, 8 1/2 hours later, a new build is available:)

http://xdaforums.com/slimroms/general/rom-builders-collective-t2861778/post55121772

.....I need a new computer:rolleyes:

:p:p
[Android Builders Collective] kantjer:
Just updated my sig ;)
[Android Builders Collective] Yank555:
You mean the slide statusbar to change brightness ?

Could have a look.

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.94
[Android Builders Collective] chykal:
Yes that's it. Thanks for looking in to it.
[Android Builders Collective] theesotericone:
Nice to see you back for a bit man. You have got the most organized git I've ever snooped.:cool:
[Android Builders Collective] meduza:
Great to have you back and active :)

So is there any hope for tab S ... .

m.
[Android Builders Collective] Yank555:
YAOSP-MM v0.95 available for angler, shamu

flounder will be up in 1 hour max (flounder compiling)

- Display - Advanced doze options : Double-tap to wake on doze option

- German & French translations updated (100% translated)

Changelog & Download links : https://github.com/YAOSP/manifest#changelog﻿

Sources are updated.

Note :

If you wonder what the new feature is, let me try to explain ;)

You have ambient display enabled (like on pickup).

Whenever you pickup the device, and doze will show, if you touch the display, the device will be turned fully on.

If you enable the new feature, touching the display while dozing won't do anything.

To turn the device fully on while dozing, you'll have to double-tap instead.

So you can pickup your device and place it in your pocket immediately, without the need to wait until doze fades out to avoid turning the device on by inadvertently touching the screen.

I hope my explanation is halfway understandable :D

If not, ask, I'll try to explain, or just test it yourself ;)﻿

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r13 v0.94
[Android Builders Collective] csolanol:
Really nice to see you back with your builds.

As you are a hammerhead user, are you going to upload the builds for it?. My hd can't support another rom sources sync.

Ty!
[Android Builders Collective] VictorLapin:
And hammerhead! :D :D

https://www.androidfilehost.com/?fid=24415232478677226
[Android Builders Collective] ezio84:
Sure, i'll do soon after polishing something!

But i'm still debated about which rom to run as default[emoji14]

Great idea ;)
[Android Builders Collective] theesotericone:
Yes. No more turning the damn phone on when I'm putting it in my pocket. This is up there with speaker follows proximity in terms of usefulness. Excellent work Yank. Thanks
[Android Builders Collective] Natakranta:
You guys make it harder and harder not to buy 6P :) [MENTION=2095315]ezio84[/MENTION], good to see you wiped dust off your building machine.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] theesotericone:
I had a lot of reservations about the 6P. I got one figuring I would end up returning it. How wrong I was. It's a really solid device. Get it.:cool:
[Android Builders Collective] Natakranta:
I'd love to. I just can't justify spending that much cash on new phone when my OnePlus One is still running great. I'm waiting for serious price cut. Unfortunately 64GB version is back on 700 EUR (from 600 EUR, it's been on sale last few weeks), but let's not start another N6P piece discussion.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.