yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] indian84:
If i remember correctly, on most of the ROMs, if you have secure lockscreen you see the emergency button only after you slide the lock screen. I am running YAOSP on my secondary Hammerhead with PIN Lock. On lockscreen, i don't see emergency, but when i slide up to unlock, i see PIN entry screen with emergency underneath it.

ALso I cannot find a way to change 4G to LTE.
[Android Builders Collective] indian84:
This is how it appears on my N5.
[Android Builders Collective] JaylanPHNX:
Now if only someone could build this for Oneplus One. (I don't have the equipment)

It's baconnn!
[Android Builders Collective] Smallsmx3:
OK thanks for the input. Doesn't cause any problems
[Android Builders Collective] Yank555:
You need this in the device repo :

https://github.com/SlimYAOSP/device_huawei_angler/commit/ef402405fb786ff3ce928c1b7fe8eb6666e5d308

JP.
[Android Builders Collective] Smallsmx3:
I think NFC is broken. It's turned off in settings and freezes when you try to turn it on. I don't use NFC so not a big deal
[Android Builders Collective] indian84:
Yup same here. I use it, but not a big deal.
[Android Builders Collective] Smallsmx3:
Otherwise, for an alpha it's pretty solid so far. A little stutter here and there. And it will be nice when more slim features are added but overall very pleased
[Android Builders Collective] limjh16:
And that is what yank is doing! (increases pressure for a manifest) (jk im not so bad) (wheres intellim) (increases pressure)
[Android Builders Collective] Yank555:
Was it working on YAOSP ?

JP.
[Android Builders Collective] indian84:
I guess it was working. I have been in Garry's PN Builds for a couple of weeks. Can't remember 100% if it worked..

EDIT - It works on Hammerhead running YAOSP. I guess that's irrelevant though..
[Android Builders Collective] Yank555:
Well if it's not working on SlimYAOSP, it could be relevant LOL

JP.
[Android Builders Collective] morfances:
I have no pin for unlocking xD
[Android Builders Collective] indian84:
:rolleyes:

OK. But when I click Emergency, it opens emergency dialer. Hence I guessed. :good:
[Android Builders Collective] Smallsmx3:
Maybe it's a CAF thing?
[Android Builders Collective] razrlover:
When you been homes?

Just wanted to say thanks ezio pure nexus mod for bullhead. Actually 3 builds in 2 days.

I searched thru 19 pages just to call you're attention and say thanks for continuing to work on this build. Glad it finally worked out.

Of course thanks to Ezio, Garrykd, Nate B and everyone else in this thread working on PNMod, and others continually working together as a community should.
[Android Builders Collective] Natakranta:
It happens I know the man with proper building machine and spare bacon to experiment.

Calling [MENTION=5824101]Jax Teller[/MENTION] [emoji16]

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] adm1jtg:
Mine (shamu) shows this as well and I only use the slide to open on my lock screen no pin or pattern

---------- Post added at 11:16 AM ---------- Previous post was at 11:13 AM ----------

nfc at least turns on and off properly for me (shamu) i dont have anything to use it on either but at least no errors
[Android Builders Collective] kantjer:
FYI, NFC was also broken on our Angler Twisted builds. After the rebase with did recently NFC is now working again.
[Android Builders Collective] Grondinm:
Just an FYI. Life has taken an unexpected turn and as a result i will be less active on forums/android dev. I will try to keep building as much as possible but updates to my builds will be less frequent. Just posting this so you guys don't think i just dropped off the face of the earth.
[Android Builders Collective] SteveMurphy:
Best wishes, [MENTION=842211]Grondinm[/MENTION], thank you for sharing what you have thus far, hope all goes well for you.
[Android Builders Collective] Grondinm:
do you smell that. Oven is cooking :)

EDIT: Hammerhead build failed to upload...something up with basketbuild will look into it after work...other builds might upload if it was temporary issue...
[Android Builders Collective] reS28raM:
OK, I can't update SlimLP to aosp rel. 7 right now (messed up my repo) so I built a kk update instead, here it is :D

New build based on SlimKat 8.14 (Nexus 5 Hammerhead)

ROM Compiled with SaberMod 4.8.4

Kernel Compiled with SaberMod 4.9

JustArchi's Optimizations v3

Features:

- Lockscreen Wallpaper

- Lockscreen Blur

- Lockscreen See Through

- Lockscreen Notifications

- OmniROM Download Manager with Pause/Resume

- Show names of optimized packages at boot

Download:

AndroidFileHost

BasketBuild
[Android Builders Collective] Grondinm:
Builds started up again. Watch for them shortly and as always enjoy
[Android Builders Collective] danarama:
anyone else get this when syncing AOSP?

Fetching projects: 100% (483/483), done.
Syncing work tree: 3% (15/482) Traceback (most recent call last):
File "/home/rootsu/android/aosp/.repo/repo/main.py", line 500, in <module>
_Main(sys.argv[1:])
File "/home/rootsu/android/aosp/.repo/repo/main.py", line 476, in _Main
result = repo._Run(argv) or 0
File "/home/rootsu/android/aosp/.repo/repo/main.py", line 155, in _Run
result = cmd.Execute(copts, cargs)
File "/home/rootsu/android/aosp/.repo/repo/subcmds/sync.py", line 675, in Execute
project.Sync_LocalHalf(syncbuf)
File "/home/rootsu/android/aosp/.repo/repo/project.py", line 1204, in Sync_LocalHalf
lost = self._revlist(not_rev(revid), HEAD)
File "/home/rootsu/android/aosp/.repo/repo/project.py", line 2241, in _revlist
return self.work_git.rev_list(*a, **kw)
File "/home/rootsu/android/aosp/.repo/repo/project.py", line 2435, in rev_list
p.stderr))
error.GitError: device/asus/flo-kernel rev-list ('^5dc211dbfad0009f0c101f353876517fc541f8c0', 'HEAD', '--'): fatal: bad object HEAD
[Android Builders Collective] ezio84:
In that situation i usually solve the problem deleting the local folder, and sometimes you could need to remove also the related .git folder under .repo/projects/ and .repo/project-objects/
[Android Builders Collective] danarama:
Thanks I'll give that a go.
[Android Builders Collective] theesotericone:
Why so quite in hear folks? I figured once SlimLP dropped this place would be going off the charts. Maybe everyone is busy building? Or just waiting for more stuff to be added? Either way let's try and get this thread rolling again. It is my second favorite thread on XDA after all. Happy compiling everyone.:cool:
[Android Builders Collective] ralpheboyo:
Quiet before the storm....lol...
[Android Builders Collective] theesotericone:
Yep. This will be a good storm though. Unlike the Q&A section for the N5 right now. That place is a total sh!t storm.
[Android Builders Collective] ralpheboyo:
We like our basement... Lol...
[Android Builders Collective] DroidIt!:
Not sure if it was a much tested feature but wanted to report the ability to lock your phone by proximity of a paired smart watch appears to work really well. I just set up a screen lock, then was able to have the phone unlocked always until my watch is out of range. So that feature works perfect here.

Also have one question. Anybody with any ideas on what the star in the status bar means? I have no idea

And this is what my notification shade looks like

I don't see anything unusual. Anybody with any ideas?
[Android Builders Collective] ptr_hamilton:
The star is the sign for priority notifications only. Toggle your volume and you'll see three sound States. None, priority, all. Where none means really none, not even alarms. And priority can be configured slightly. Custom roms use it for former quite without vibration mode.

Cheers Pete
[Android Builders Collective] DroidIt!:
Posted in the wrong thread, but thanks non the less. I was trying to figure that one out ')
[Android Builders Collective] ezio84:
L is too much different, developers need time, then we could catch their magic :D
[Android Builders Collective] Grondinm:
Keep an eye out...maybe an early alpha based build from me before monday if all goes well
[Android Builders Collective] theesotericone:
I got one in the oven right now. Unfortunately I forgot to add loonybin so I doubt it will actually boot. Plus in all honesty I'm REALLY happy with how SlimKat has been running on my device. Sort of if it ain't broke don't fix it mentality for me right now. I'm sure I'll flash it tomorrow and break my storage and all sorts of other stuff but the N5 is an easy device to recover. I already flashed the new radio(which is awesome in my area btw) and bootloader to prep for it. I'm half temped to just dirty flash it from SlimKat with a system wipe and see what happens. Someones gotta be the guinea pig. If your gonna break stuff you might as well go big. Who thinks that's a really bad idea?:cool:
[Android Builders Collective] pkelly517:
I haven't had a bootloop in ages. Maybe I'll finally get one if I dirty flash between kk and lollipop.

That's the road you're traveling.
[Android Builders Collective] theesotericone:
LOL. No such luck with the bootloop. Coming from SlimKAT 8.10 I wiped system, cache and dalvik(leaving data intact) and flashed the Slim teams alpha build. Then CM 5.0 gapps(i hated it lol), then elemental x, then the viperLP zip then booted up. Not only did I not get a but loop but some stuff actually worked. Play services was hosed as well as root. So I deleted my google account and rebooted into recovery to flash the latest SSU zip. Wiped cache and rebooted. After signing back into my google account play store works as well as root. Clock was also hosed so I cleared data and all is well again All in all I'm amazed. I wouldn't post this info anywhere but here because I know and trust everyone here who does it will be able to recover if things go south.

Eventually I'll do a clean flash but for now it works. Also for now I'm on my way back to KK. Let's hope that backup works lol. I can't live without volume to skip music control.:cool:

PS: [MENTION=2872010]rootSU[/MENTION] I'm still using playfullgods swipeable CWM v4.0.4.5. It refuses to become obsolete still. lol Have a good one man.
[Android Builders Collective] likonvampire:
Hey [MENTION=2033478]Yank555[/MENTION] , One thing I noticed is that on my device it says 4G instead of LTE. Havent tested speeds , its the same network just different terminology being reflected.
[Android Builders Collective] kantjer:
AFAIK on al ROM you can only make an emergency call from a lockscreen (secure or not)

The MCC (mobile country code) determines if 4G or LTE is shown.

If you want you can switch 4G to LTE or vice versa with a layer.

https://github.com/TeamTwisted/plat...mmit/03107664d1cd3962824c5d3ec2b5194cf3a10dc8
[Android Builders Collective] likonvampire:
Edit : No change , also how can i get rid of the superuser icon in the status bar ?

Maybe this can help change the icon ?
[Android Builders Collective] Smallsmx3:
Nope... Sure doesn't...
[Android Builders Collective] adm1jtg:
4g shows on mine as well but if I go into phone info, status, sim status... cellular network type lists as LTE so this is simply just slim displaying 4g for all signals greater then 3g
[Android Builders Collective] Jax Teller:
I'm always around. ?

What do you want me to build?
[Android Builders Collective] Ryther:
You stalkers, you found out my secret build's stash XD I built from vnc on my cell, I had no time to even download it XD was waiting to post the new builds because I didn't try them, glad to hear that they are working!

I will prepare a standard post for my releases, that way I can inform you faster and give due credits to all the fabulous people that made all this possible :thumbup:
[Android Builders Collective] Natakranta:
This for bacon.

You can do it! [emoji8]

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] kantjer:
No that won't work.

The default icon type is set in Framework (AFAIK default for Android is LTE) and can be overwritten with an overlay based on MCC.

As a user there is nothing you can change about it without the dev adding an option or using a layer.

The ROM dev can change default and/or MCC related behavior in the code.
[Android Builders Collective] Yank555:
Purely cosmetic, 4g is the commercial name for lte here.

Icon can be overlaid, will look into how to display lte.

Speed and technology used is unaffected.

JP.
[Android Builders Collective] Smallsmx3:
I've seen other Roms have a toggle for it. But honestly it doesn't matter to much at the moment

---------- Post added at 02:05 PM ---------- Previous post was at 01:07 PM ----------

@Yank555 one of the features of SlimYAOSP shows use Nexus audio files..... The AOSP sounds are what's used. Am I missing something
[Android Builders Collective] Yank555:
Maybe the sounds are overridden by Slim's vendor repo, could be, the commits I have are in fwb and replace the original files, while Slim likely will overlay them at build time.

JP.
[Android Builders Collective] Smallsmx3:
Heard.
[Android Builders Collective] zamula:
Would anyone be willing to build PureNexus Mod for flounder?

I've started reading the thread on setting up a cloud build environment, but I've never built android before so I think it's going to take a while to really get going :)
[Android Builders Collective] Ryther:
I'm going to try to synch slimYAOSP for bullhead tonight ;)

Thank you [MENTION=2033478]Yank555[/MENTION] for all your effort!
[Android Builders Collective] Yank555:
SlimYAOSP reuploading for angler, NFC should be fixed ;)

I'll update the initial post once it's done.

Fix is invendor repo, it's pushed on TheLoonyBin.

JP.

Edit:

Here's the updated angler ROM --> https://www.androidfilehost.com/?fid=24533103863141191

NFC looks working, but I'd need someone to actually test it, I can't test myself.

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

Oh ... latest angler should also fix vzw "roaming" signal icon ... need feedback on that as well.

JP.
[Android Builders Collective] VictorLapin:
I understand that everyone is excited about SlimYAOSP, but.

Here's a piece of "good old" YAOSP for bullhead: https://www.androidfilehost.com/?fid=24533103863141193

Included:

- latest v1.20 sources (MTC19T)

- bullhead device repo with YAOSP features support (bringup) thanks for the invaluable [MENTION=2033478]Yank555[/MENTION] help :)

- stock AOSP kernel
[Android Builders Collective] Smallsmx3:
It turns on. I can't actually test it
[Android Builders Collective] Yank555:
Bringup merged into YAOSP sources on github, so you can reposync and build bullhead, too, now thanx to Victor :D

JP.
[Android Builders Collective] bluerez79:
Didn't check NFC but I still have the roaming signal on angler though I did dirty flash.
[Android Builders Collective] Yank555:
apn is correct ?

I suppose more than that is needes then...

JP.
[Android Builders Collective] bluerez79:
Yes. I believe APN is correct
[Android Builders Collective] Natakranta:
Fastboot flashed latest factory images and without booting system went to TWRP and flashed Slim_YAOSP, open gapps, theme ready hangouts and SuperSU 2.71

Upon every boot I see this message, screen shot below. I don't feel anything is not working. All seams good. Anybody has seen it? What's this?

Angler

[MENTION=2033478]Yank555[/MENTION], mobile data is working fine. I'll check calls and my work WiFi tomorrow.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] theesotericone:
Oh man. That is not good. I had that and it lead to all sorts of ..................

Just kidding man. Flash the vendor image that matches the build number of the ROM your on. Usually that just means flashing the latest vendor image. You can flash it a few ways. I still use fastboot to do it but I'm old and stubborn. TWRP handles it as well.:cool:
[Android Builders Collective] Natakranta:
I'm losing my mind. Are there regional settings for factory images page?

Checking on phone latest angler is MTC19T.

When I downloaded on laptop on Mint there was different image as the latest, MHC19Q, which I fastboot flashed (I'm old school as well) including vendor.img

WTF?

I have MTC19T vendor.img on phone, going to TWRP to flash it now over the MHC19Q.

I've just refreshed page on PC and now I see MTC19T as latest. Why Google is not putting time stamps next to each one?

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] theesotericone:
MTC19T is the latest. If your looking under about phone that's the build number not the vendor image. Custom ROMs do not flash the vendor. So if your favorite ROM (coughTwistedcough) changes to a newer build number you have to flash vendor manually to get rid of that warning. As far as I can tell it doesn't effect anything on the phone performance and usability wise if you stay on the older vendor. You just have to see that stupid warning. lol:cool:
[Android Builders Collective] Ryther:
Sync for "stock" SlimYAOSP running right now :cool:

Here my manifest, I hope I have done everything right :silly:

First building try will start tomorrow ;)
[Android Builders Collective] indian84:
[MENTION=2033478]Yank555[/MENTION] Dirty flashed the latest YAOSP Slim on angler and NFC works fine. The NFC Quick Tile is back too. :good:
[Android Builders Collective] Yank555:
Well at least one thing cleared, vzw showing roaming still to go .. not sure I'll get to that before I leave ... but I still have one evening LOL

JP.
[Android Builders Collective] angelcalibur:
Hi Fellas!

I've got this error when building a testing rom (aosp) :

Install: /home/angel/aosp2/out/host/linux-x86/bin/mkbootimg

Building Kernel

make -C kernel/samsung/jf O=/home/angel/aosp2/out/target/product/jflte/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/angel/aosp2/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androideabi-" zImage

host Executable: mkbootfs (/home/angel/aosp2/out/host/linux-x86/obj/EXECUTABLES/mkbootfs_intermediates/mkbootfs)

Install: /home/angel/aosp2/out/host/linux-x86/lib64/libcutils.so

make[1]: Entering directory '/home/angel/aosp2/kernel/samsung/jf'

target Symbolic: libdl (/home/angel/aosp2/out/target/product/jflte/symbols/system/lib/libdl.so)

/home/angel/aosp2/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /home/angel/aosp2/out/target/product/jflte/obj/ETC/sepolicy_intermediates/policy.conf

external/sepolicy/domain.te:398:ERROR 'unknown type sudaemon' at token ';' on line 9459:

neverallow { domain -dumpstate -shell -su -init -untrusted_app -sudaemon } su_exec:file { execute execute_no_trans };

# su itself execute su.

checkpolicy: error(s) encountered while parsing configuration

external/sepolicy/Android.mk:69: recipe for target '/home/angel/aosp2/out/target/product/jflte/obj/ETC/sepolicy_intermediates/sepolicy' failed

make: *** [/home/angel/aosp2/out/target/product/jflte/obj/ETC/sepolicy_intermediates/sepolicy] Error 1

make: *** Attente des tâches non terminées....

CHK include/linux/version.h

GEN /home/angel/aosp2/out/target/product/jflte/obj/KERNEL_OBJ/Makefile

CHK include/generated/utsrelease.h

Using /home/angel/aosp2/kernel/samsung/jf as source for kernel

make[3]: 'include/generated/mach-types.h' is up to date.

CALL /home/angel/aosp2/kernel/samsung/jf/scripts/checksyscalls.sh

CHK include/generated/compile.h

CHK kernel/config_data.h

Kernel: arch/arm/boot/Image is ready

Kernel: arch/arm/boot/zImage is ready

make[1]: Leaving directory '/home/angel/aosp2/kernel/samsung/jf'

DTBs not enabled

Building Kernel Modules

make[1]: Entering directory '/home/angel/aosp2/kernel/samsung/jf'

GEN /home/angel/aosp2/out/target/product/jflte/obj/KERNEL_OBJ/Makefile

CHK include/linux/version.h

Using /home/angel/aosp2/kernel/samsung/jf as source for kernel

CHK include/generated/utsrelease.h

make[3]: 'include/generated/mach-types.h' is up to date.

CALL /home/angel/aosp2/kernel/samsung/jf/scripts/checksyscalls.sh

Building modules, stage 2.

MODPOST 1 modules

make[1]: Leaving directory '/home/angel/aosp2/kernel/samsung/jf'

make[1]: Entering directory '/home/angel/aosp2/kernel/samsung/jf'

INSTALL drivers/scsi/scsi_wait_scan.ko

DEPMOD 3.4.107-aosp-ga3d60db

make[1]: Leaving directory '/home/angel/aosp2/kernel/samsung/jf'

Anyone can help me to finish this build? i'am nearly the end :fingers-crossed:
[Android Builders Collective] csolanol:
Hi [MENTION=2033478]Yank555[/MENTION], we are having an issue with hardware keys on Mi 4c. they turn off when your turn off the screen, but, usually, they turn on again half a sec later. Then sometimes they turn off and sometimes stay on while screen is off. Logcat doesn't say too much about it and i don't know where to look at. Where should i look for it, Power hal?.

Ty,
[Android Builders Collective] Natakranta:
[MENTION=2033478]Yank555[/MENTION], soft reboot when listening to music on earphones few minutes after screen went off. Soft reboot because it didn't ask me for sim card pin afterwards.

/proc/kmsg is empty. I'm at work, no PC to run log. Anyway to find what it was?

Angler SLIM_YAOSP latest.

BTW, latest solved NFC bug, on original I had it on by default and couldn't turn it off, grayed out. It was causing ongoing wake lock. Now it's fixed. I can turn it off and NFC wake lock is gone.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Android Builders Collective] Real_Justus:
Hey all,

I am in trouble - again...!

I am using Nexus 6 (Shamu) with Yanks MYAOSP v1.20. The device is encrypted with trusted face and PIN plus trusted location. The device worked fine until this morning. I use to restart the device every morning. Today it restarted and began to prepare the cache (just like Android is starting after cleaning cache and Dalvik/ART). When this is finished, the device reboots and starts to prepare the cache again. This behavior loops... I have to mention, that I added the trusted location yesterday. Might this cause the issue?

I did a dirty flash with wiping system and the caches. After the flash the phone booted normally once. Then it showed the strange behavior again.

I tryed to repair the cachepartition just in case... But I got that feeling, that says that the problem is related to the trusted location thing...?

Does anybody have a clue how to get out of the vicious cycle?
[Android Builders Collective] Yank555:
Maybe ... I've been Nexus only since before I started on ROMs, no idea about h/w key backlight.

On i9300 that was handled by kernel only, later a patxh made it ROM-side controlled through sysfs interface...

Should be device/kernel/vendor...

no kmsg on a softreboot...

On a sidenote : which device is it again ? Newer devices use pstore for last kernel dmesg.

Don't think it'll be easy to find out the culprit w/o logd :(

JP.
[Android Builders Collective] angelcalibur:
Hi [MENTION=2511007]csolanol[/MENTION] and [MENTION=2033478]Yank555[/MENTION]

Hardware keys have to be set before the build here :

https://github.com/CyanogenMod/android_frameworks_base/blob/cm-13.0/core/res/res/values/config.xml

i had the same kind of issu and i always had to set them like this:

<!-- Control the behavior when the user long presses the home button.
0 - Nothing
1 - Menu key
2 - Recent apps view in SystemUI
3 - Launch assist intent
4 - Voice Search
5 - In-app Search
This needs to match the constants in
policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
-->
<integer name="config_longPressOnHomeBehavior">2</integer>

Here, you choose the number to allow an action.

If i remember well, here are the change too:

https://review.slimroms.org/#/c/8240/

Another by robbie :

https://review.slimroms.org/#/c/3097/

https://review.slimroms.org/#/c/3098/
[Android Builders Collective] NeBouse:
Guys I'm back lol

I've set up a build environment on Google Cloud, with a good VM.

(It's free for 2 months !!)

I'd really like to be able to bring up my device (G4) on Slim before development starts again.

So , in order to test my build environment, what rom should I try to build ?

Any Slim6 available for building ? (for any device I mean, just to test if it builds).

And if so, any platform-manifest to give me ?

Thx.