yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Yank555:
Hmm ... well I last synced my repos on sunday evening around almost midnight (CET) ... either the culprit wasn't in there at that time, or, if that f2fs commit in the kernel might be an issue, I always flash my own kernel right after flashing SlimLP, maybe worth trying to flash the ROM an a custom kernel right after that before first boot ? Just wild guessing here based on the few posts I just saw here...

JP.
[Android Builders Collective] :
I agree. But maybe you could do a build without that commit and see if it boots? If it does then I think that commit needs to be addressed in some way...

Edit: also it's definitely not [MENTION=2033478]Yank555[/MENTION] 's mod and/or patch 9. I've done 2 builds with that one today and both flashed and booted normally on Hammerhead.
[Android Builders Collective] srkmagnus:
I was under the impression that creating a Volume was the same as partitioning. That assumption is purely my ignorance for not researching to fully understand and figured going the external drive route would be less problematic for my case in the future.

Thank you for the clarification.
[Android Builders Collective] JaylanPHNX:
Sorry, No one was saying you were rude. I made a joke based on a typo; you typed you thrust Robbie, rather than trust. I was just being silly.

From my SlimTab Pro 8.4
[Android Builders Collective] Nucleonic:
I reverted the commit and trying another build. I'll let you all know my results!

Out of curiosity, how would we go about reformating to f2fs?
[Android Builders Collective] inffy:
Twrp has a an option to chase the f2fs
[Android Builders Collective] Yank555:
Battery mod pushed to gerrit

(non-caf branch)

I still have the idea of a breathing text (size up & down) for text only style and also intend to recode the battery portrait/landscape icon drawing code so the level/bolt will be partially inverted as battery level drops. But before going there I wanted to complete the featureset, so this is what I came up with tonight...

Text only will show charging by replacing the "%" by a "~" ("85~" instead of "85%") ... I know it's not THAT sexy, but it was a missing piece and I wanted to at least have a clue if the device was charging or not, it at least gets the "job done" for now ;)

I consider this a v1 with full features and tested working fine on my end. I may still do a code review, but not tonight, need some "couch time" :angel:

Please let me know if there's anything misbehaving.

Links :

https://gerrit.slimroms.net/24334

https://gerrit.slimroms.net/24335

JP.
[Android Builders Collective] Nucleonic:
The standard TWRP (1/13/15 version) or one that has been modded? I saw a reference to a modded TWRP but did not see any options on the standard TWRP for reformatting to f2fs. There is an option for formatting as part of wipe, but not sure that is what is intended.
[Android Builders Collective] inffy:
The official 2.8.4. 0

Requires a wipe for the partition which you want to convert
[Android Builders Collective] :
Super! Added and building - will give feedback tomorrow :)
[Android Builders Collective] Nucleonic:
On TWRP, if I go to advanced wipe, I see now the button for repairing or changing file systems. If I pick one, like system, I only get EXT2, EXT3, EXt4, FAT and exFAT for options. No f2fs.

Also, which partition needs to be re-formatted to f2fs to deal with the commit? System? Can the rest remain as is?
[Android Builders Collective] Silentbob999:
I actually had to use a translator... for some reason this word was completely lacking from my knowledge. The type of thing an autocorrect feature never teach you ;)

Thanks lol
[Android Builders Collective] pkelly517:
[MENTION=2033478]Yank555[/MENTION] Well, i tried to pick it. Not so much luck. I've got to get my daughter off to dance in the next 10 minutes, so I thought I'd post the error message, have someone point out the totally obvious way to fix it, and check back in a couple hours.

peter@crichton ~/SlimRoms/lollipop/frameworks/base $ git reset --hard HEAD
HEAD is now at e65ea11 Layers: Making DocumentsUI fully themeable
peter@crichton ~/SlimRoms/lollipop/frameworks/base $ git st
# Not currently on any branch.
nothing to commit (working directory clean)
peter@crichton ~/SlimRoms/lollipop/frameworks/base $ repo sync .
Fetching project SlimRoms/frameworks_baseFetching project repo

remote: Finding sources: 100% (3/3)
remote: Total 3 (delta 0), reused 3 (delta 0)
Unpacking objects: 100% (3/3), done.
From https://gerrit.googlesource.com/git-repo
24245e0..126e298 master -> origin/master
Fetching projects: 100% (2/2), done.

peter@crichton ~/SlimRoms/lollipop/frameworks/base $ git fetch https://gerrit.slimroms.net/SlimRoms/frameworks_base refs/changes/34/24334/11 && git cherry-pick FETCH_HEAD
From https://gerrit.slimroms.net/SlimRoms/frameworks_base
* branch refs/changes/34/24334/11 -> FETCH_HEAD
error: could not apply 5c2ac7c... [2/2] Settings: Add options for battery icon and text in status bar
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
peter@crichton ~/SlimRoms/lollipop/frameworks/base $ git st
# Not currently on any branch.
# Changes to be committed:
#
# modified: core/java/android/provider/Settings.java
# modified: packages/SystemUI/res/layout/status_bar.xml
# modified: packages/SystemUI/res/values/arrays.xml
# new file: packages/SystemUI/res/values/slim_arrays.xml
# modified: packages/SystemUI/res/values/slim_strings.xml
# modified: packages/SystemUI/src/com/android/systemui/BatteryMeterView.java
# modified: packages/SystemUI/src/com/android/systemui/statusbar/phone/KeyguardStatusBarView.java
# modified: packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java
# modified: packages/SystemUI/src/com/android/systemui/statusbar/phone/StatusBarHeaderView.java
#
# Unmerged paths:
# (use "git add/rm <file>..." as appropriate to mark resolution)
#
# both modified: packages/SystemUI/res/layout/keyguard_status_bar.xml

Why am I getting 'both modified'?
[Android Builders Collective] Nucleonic:
I found the following link from DHacker:

http://d-h.st/aKkU

Going to download and flash it. Supposed to have f2fs support. Does the system partition only need to be f2fs?

I also noticed while gathering acorns in the Google wildnerness that some kernels may not work with f2fs currently. Lean kernel which comes with the source, should. But, my favorite EX may not.
[Android Builders Collective] fraz14:
[MENTION=5131448]reS28raM[/MENTION]

Today I installed the Power menu button.

Works without problems, but if you have installed a theme it does not work.

---------- Post added at 11:17 PM ---------- Previous post was at 11:05 PM ----------

Sorry!!!!!, not true. I had to re-enable it again only.

Until now, I can find no errors:good::good::good:

---------- Post added at 11:42 PM ---------- Previous post was at 11:17 PM ----------

Sorry, works for me but not really. Problems with the tones and the keys do not respond properly
[Android Builders Collective] PerfectSlayer:
Hi all,

I post some pictures of my network meter. Feel free to comment and give your opinion about the idea, graphics, integration…

Only the incoming traffic is displayed for the now but I think about adding outgoing too (I hate waiting in front of my screen whereas the phone don't make any request at all !).

NOTE: the real network speed text will not be present in final version. I add it only to help me debugging the meter ;)

About the settings, there is a toggle in Slim interface to display / hide the meter.

I will also add a setting to tune the refresh frequency but I want to keep update low (It just a meter, something like every 1s, 2s, 5s and 10s should be enough :))
[Android Builders Collective] DroidIt!:
There's apps for finding lost car keys. Maybe we should make an app to find lost developers. Hit a button and kufi dings or it zaps him [emoji14]
[Android Builders Collective] efan3719:
It'd break from the abuse. We just need a Slim Team bat signal type thing.
[Android Builders Collective] Garrykd:
Try tossing frameworks/base, repo sync, then try the cherry pick again.

If you get the same error, pastebin your packages/SystemUI/res/layout/keyguard_status_bar.xml
[Android Builders Collective] NovaSlim:
[MENTION=4911350]RobbieL811[/MENTION] Another Layer commit:

https://github.com/BitSyko/platform...mit/dda095c4f07bb358e8c20b97c55957fa40a7e1e5﻿
[Android Builders Collective] DroidIt!:
So I saw a story on the news just now [MENTION=2640853]Garrykd[/MENTION] Was this you? [emoji15]
[Android Builders Collective] Garrykd:
Why are you watching news from 4 years ago? :silly:

(....and no, it's not me)

[YOUTUBE]mrveNdW_sj0[/YOUTUBE]
[Android Builders Collective] RobbieL811:
Lol. I just told you that you can't do it that way and you're telling me that you can lol. There are multiple reasons that you can't. manifest's can't have duplicate paths for one reason, so there's no way possible that you would even be able to sync the 2 roms. You can't have 2 default manifests, and you definitely can't merge them. How would you be able to do it? It doesn't work like the way you are thinking in your head. I'm telling you.
[Android Builders Collective] TONY206:
I just flashed your build from today over your last build and my navbar is messed up. I am set at stock 560 lcd density.

Is this because of your 400 dpi navbar fix?
[Android Builders Collective] endomatic:
That is what we (my kayaking buddy and I of long ago) call the Gomer run. When it is time and the proverbial tank is empty, you get out of your wheelchair and into your boat, shove off sans paddle and have a good ride.

Best
[Android Builders Collective] inffy:
[MENTION=4453916]Nucleonic[/MENTION] did you get your build to boot
[Android Builders Collective] theesotericone:
Just flashed my build for hammerhead from last night. It boots fine so that pretty much confirms what everyone has been saying. Sorry it took so long my 10 hour day turned into a 12 hour day real fast. You'll figure it out man. Good luck.
[Android Builders Collective] Nucleonic:
Been a fun evening.

I found TWRP that has the f2fs capability built in. Not knowing what the hell I was doing, I erased everthing in the interest of science. Reflashed the Nexus factory image and was back in action.

I figured out that I needed to have System and cache formatted to f2fs. Did so, and my build would not mount. Also, my f2fs formats wouldnt stay f2fs. I do a wipe and presto back to eX4.

I built a ROM with the f2fs commit reverted. Still won't boot. Just the SlimLP animation.
[Android Builders Collective] inffy:
Not good...not good at all.
[Android Builders Collective] RobbieL811:
Who in here has tiles going on an AOSP device, and they are working properly? I need to look at something.

Sent from my 1+1
[Android Builders Collective] Silentbob999:
As I said. I have no knowledge about manifest. I have an understanding of GIT but not of REPO. Now I read this and it make more sense to me.

I did some test fast on windows with Github for windows.

In Git Shell, repo is unknown command so I cannot test further... but I did the equivalent of repos init with git command and so far so good. default.xml manifest for caf and non-caf.

git init

git checkout -b lp5.0
git checkout -b lp5.0-caf

git checkout lp5.0
git clone git://github.com/SlimRoms/platform_manifest.git -b lp5.0
git add platform_manifest
git commit -m "init lp5.0"

git checkout lp5.0-caf
delete platform_manifest folder manually from file explorer*
git rm platform_manifest
git clone git://github.com/SlimRoms/platform_manifest.git -b lp5.0-caf
git add platform_manifest
git commit -m "init lp5.0-caf"

git checkout lp5.0
cat /platform_manifest/default.xml

git checkout lp5.0-caf
cat /platform_manifest/default.xml

I also read this http://xdaforums.com/showpost.php?p=55178446&postcount=77

Since it have no repo and cannot repo sync, I don’t have /.repo/local_manifests. I don’t really know where they will go and how everything will react.

But I am certain that if you do an ini git at top level... make 2 clean branch with a slimroms folder in it. If it is done properly it can work… Now, do you still need to apply your commit separately on both? (YES). Is it needed (NO), is it easier (ABSOLUTLY NOT), is it possible (it look like), can you save space (maybe). Is it fun to test (I think so).

Maybe one advantage of this would be 0 chance to get to a point where you have to erase everything and waste your bandwidth, you can always reset to the first commit and start fresh from there.

[MENTION=251020]inffy[/MENTION] , [MENTION=2888538]letmedanz[/MENTION]

If you want to test the code below and adapt the syntax and the step you are usually doing I think it should work.

mk android*
git init

git checkout -b lp5.0
git checkout -b lp5.0-caf

git checkout lp5.0
mk slimroms
cd slimroms
** do what you usually do here begin **
repo init
repo sync **** lp5.0
** do what you usually do here end **
cd ..
git add slimroms
git commit -m "init lp5.0"

git checkout lp5.0-caf
rm slimroms
mk slimroms
cd slimroms
** do what you usually do here begin **
repo init
repo sync **** lp5.0-caf
** do what you usually do here end **
cd ..
git add slimroms
git commit -m "init lp5.0-caf"

** You have to go back to /android/ and "git add slimroms" and do a commit BEFORE switching branch (each time).

Maybe you will find a way to get a workflows that will help you to apply your commit to both branch.

Maybe it is just more complicated for no reason lol

It’s one of those day where I am a thickheaded* (translation ok?). I hope you don’t mind those type of answer.

Good night all
[Android Builders Collective] inffy:
Another test and another failure.

I synced Slim repo 20mins ago and did a stock build. Wiped my device and installed the rom --> Reboot and again bootloop.

Here is a logcat if [MENTION=4911350]RobbieL811[/MENTION] could forward this to the dev team (or have a looksie)
[Android Builders Collective] RobbieL811:
What device are you trying to build for?
[Android Builders Collective] inffy:
Nexus 6
[Android Builders Collective] RobbieL811:
Yeah. I saw it in the log after I asked you lol. Why wouldn't you give this to Cordell? I think he is the one maintaining Shamu right now. Or [MENTION=1277872]dankoman[/MENTION]
[Android Builders Collective] inffy:
Didn't actually know who maintains it :P

How can I send it to cordell, or is [MENTION=2098827]cordell[/MENTION] reading this? :)

EDIT: Found his gmail from gerrit
[Android Builders Collective] Yank555:
Yep, says so in the changelog, I've increased the space from the edges as on 400dpi the keys are way too far away from each other.

You can use the other (2 days older) build, it does not contain that change and is mostly on par with the latest.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.5 kernel.
[Android Builders Collective] SFG:
Does anyone here build for the Nexus 10 (manta)?
[Android Builders Collective] inffy:
[MENTION=4453916]Nucleonic[/MENTION] and all other shamu builders! I got a reply from cordell

The source is messed up because of the ffmpeg merges.

To fix it you need these:

https://gerrit.slimroms.net/#/c/24561/

https://gerrit.slimroms.net/#/c/24620/1

https://gerrit.slimroms.net/#/c/24621/1

https://gerrit.slimroms.net/#/c/24622/1

https://gerrit.slimroms.net/#/c/24623/

And in that order :)
[Android Builders Collective] inffy:
After these patches are picked, it boots again :)

---------- Post added at 13:49 ---------- Previous post was at 13:16 ----------

Looks very nice!
[Android Builders Collective] Nucleonic:
Thanks inffy!!!!!
[Android Builders Collective] damngood98:
weeklies should be starting soon enough. and i'm sure you've looked in the official manta thread....there's one there that's only about a week old
[Android Builders Collective] tysonwald:
Hoping for a new build soon then? :)
[Android Builders Collective] inffy:
Today yes :) when I get my source updated with some more additions
[Android Builders Collective] Yank555:
Crap ... we're going morsecode now ... where was that damn doc on how to decrypt this again ... hmmm ;)

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.5 kernel.
[Android Builders Collective] inffy:
Finally!

New hoppy is uploaded

CHANGELOG hoppySLIM v1.5:

Download: https://www.androidfilehost.com/?fid=95916177934523556
[Android Builders Collective] Mistertac:
I just want to say you Slim guys in here are very cool... Helping each other to put out these builds is very nice to see!

Oh and

.. . .... .. .
[Android Builders Collective] tysonwald:
yes, thank you! downloading now!:D
[Android Builders Collective] Skripka:
Flashed before you got the announcement up, restoring now. :good:
[Android Builders Collective] tysonwald:
running like a dream so far!
[Android Builders Collective] inffy:
Good [emoji317]
[Android Builders Collective] jtwlbz:
Network indicator!!! Great ROM now I can use!! [emoji5]
[Android Builders Collective] ifwillems:
[MENTION=251020]inffy[/MENTION] can you do one for N5? Please.
[Android Builders Collective] Nucleonic:
Inffy,

Do you have a link to ezio's commits for network indicator? Do we know of these were going to be pushed to Gerrit?
[Android Builders Collective] letmedanz:
Thanks Bob

I get what you saying & it feels like it should work too..

as it's a different branch, it shouldn't matter.. but that would mean extreme diligence to ensure that we are always on the right branch..

if not the SWHTF :D

Thanks again.. i am going to give this a go both ways (just freed and added 300gb) :D
[Android Builders Collective] srkmagnus:
Thank you for the help yesterday, [MENTION=4911350]RobbieL811[/MENTION] & [MENTION=2770867]akselic[/MENTION]. I was able to get the build going after deleting the slim_manfifest file I made then allowing things to be added manually. However, my build failed due to errors. I'm don't have the exact error code right now, but recall seeing something about busybox and recovery sources not found (something along those lines).

I'll be doing some reading up today and hopefully find what the problem is then retry later tonight/tomorrow. Thank you two again for the help in getting this going.
[Android Builders Collective] inffy:
Sure :)

---------- Post added at 17:33 ---------- Previous post was at 17:32 ----------

Not at the moment I don't have the link. It think it is exits signature/on his posts on this thread.

I don't think that they are going to be pushed to gerrit. PerfectSlayer is working on a new patches considering the network indicators
[Android Builders Collective] tysonwald:
anything on today's build change as far as layers would go? applying the same layers as last build, but the notification part of them isn't displaying correctly.
[Android Builders Collective] :
[MENTION=2033478]Yank555[/MENTION] I made a build with the latest merged patches @ Gerrit (4 and 12) and everything seems good. Absolutely loving your mod and the touch for %only while charging is cool - at least now it differentiates from non-charging status. Thanks again!

To other N5 users I'm testing my latest build on a clean flash and if I don't run into problems I'll upload a new ACSlim build tomorrow. Will post changes here when I'm uploading.
[Android Builders Collective] reS28raM:
Not understood here if you are still talking about the power button or the Rom? All is good here, I can assure you: no bugs and the rom flies, literally :)

Maybe it is time for a clean install for you? I solved long-standing issues with network etc that way: clean flash...

---------- Post added at 05:05 PM ---------- Previous post was at 04:52 PM ----------

IEHIE if I remember well from my army's days lol

_._. .. ._ ___
[Android Builders Collective] Silentbob999:
I have a fear. I am not sure that it is require to go back to the root folder to change branch. Which mean you are somehow bind to the main git on top. I have no idea how repo internal mechanism will deal with that. If you are willing to test report back. I am curious
[Android Builders Collective] :
After deleting the self-made manifest file and letting the sync create it for you, did you then add the LoonyBin lines in the now created slim_manifest or another local manifest?
[Android Builders Collective] inffy:
what notification part?
[Android Builders Collective] tysonwald:
Heads up, notification pull down and the lock screen. The notifications are black text on black background with today's update. On the last build they displayed correctly, using the same layers as before.

Not a huge deal I just uninstalled the layer that controls that, just figured I'd give you a heads up in case something changed
[Android Builders Collective] inffy:
Hmm no changes considering layers. It might have something to do with the network indicator commit but that also seems unlikely
[Android Builders Collective] :
I noticed the same effect between my builds earlier this week vs after I synced to the SlimRoms added commits. Basically notifications with Layers worked when I had my own commits but since Slim merged Layers commits, I reverted them from my build and synced the source. After that notifications in dark Layers themes have the same effect in my builds too.

Short version: I think it's something in the Slim source (their Layer commits) and any Slim custom build will have that same effect until it's fixed, changed or updated at source level.
[Android Builders Collective] letmedanz:
i will.

No other way to learn other than experimenting :good:
[Android Builders Collective] dankoman:
fixed :D

https://gerrit.slimroms.net/24671

https://gerrit.slimroms.net/24674
[Android Builders Collective] chykal:
At the place I work we use Google apps and Google device policy to securely access email, calendar, drive and hangouts which all integrates nicely on 4.4.4. I have tried the latest Slim 5.0x and the previous versions and it doesn't support this setup the same way. Adding my Google account in device policy takes me through the two step verification process and I end up accessing Google apps through a web browser interface instead of the Google apps integration that I got with 4.4.4. Once the device is approved by our Support Center it does integrate but it uses exchange which doesn't give access to Hangouts and some of the other features that used to be available. What is the reason for this loss of functionality and do any of the 5.0x SBC builds support this the way 4.4.4 did?
[Android Builders Collective] inffy:
Here is a hammerhead build:

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

No idea if it boots or not, no promises. Please report back :)
[Android Builders Collective] srkmagnus:
I put the TheLoonyBin files within the created slim_manifest.xml file (~/.rep/local_manifets/slim_manifest.xml). After

repo sync

I went in and checked that the blobs were added and they appear to be there. Also, there were no errors when

repo sync

and

. build/envsetup.sh && lunch

were initiated. Only after

mka hammerhead

or

make -j# otapackage

were entered.

When I get home I'll run again and try searching the errors and/or post here for further help if needed. Thank you!
[Android Builders Collective] inffy:
Yeah these stuff I can see on the lockscreen. But it is not with all apps. Press, Outlook do not show right colors on the lockscreen notification (white on white), also Whatsapp misbehaves etc.

---------- Post added at 20:14 ---------- Previous post was at 20:02 ----------

I have kept the lp5 stuff on folder slim and caf stuff on slim-caf.

Even with those different directories the upkeep is real pain in the ass, as you hve to be really sure where to push the commits. And when many of slim repos are only on lp5.0 branch it is even "trickier"
[Android Builders Collective] ifwillems:
[MENTION=251020]inffy[/MENTION] ... works fine! Haven't tried out V4A yet .. but will shortly.

Besides V4A what are the major differences with the standard build that [MENTION=1277872]dankoman[/MENTION] put out yesterday? I did notice that your status bar settings are more elaborate.

Thank you very much.

edit:

Just noticed that after a reboot the SlimRom Center Update notification appears in the status bar.