yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Yank555:
Should be good, although shamu sometimes reports 'no charging current' even though it's charging LOL

Needs some more debugging I suppose ;)

Will also set 'fast' threshold to 1100mA/h for hh and shamu I think, more tomorrow, though, time to sleep, toigh day #2 at work tomorrow...

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r22 v1.01
[Android Builders Collective] adm1jtg:
Happy to help you test and debug if you need additional eyes and shamu testers
[Android Builders Collective] atomizasser:
Hi ezio84.

I'm trying your custom build of PureNexus ROM. I'm very satisfied with it but i found 2 bugs (i don't know if were reported):

- Ambient display: color inversion for loockscreen notification isn't working. All notification are in black color.

- Sound and vibrate when you plug in: If you select vibrate and sound when plug the phone with cable, but you select NO sound, always sound the default notification sound. You can change sound, but if you only want vibrate without sound, is not possible.

Thanks
[Android Builders Collective] kantjer:
Enable Charging sounds and Vibrate and set Notification sound to none.

That works for me
[Android Builders Collective] ezio84:
Same as kantjer, here the charge sound setting works well: if i set "nothing" as sound, it doesn't play anything.

The build has the last PN ambient display code, but i haven't tested it. I'll take a look at the color inversion feature, tnx.

EDIT: tested now, it works well too. Keep in mind this: you need to disable the inversion for dark themes, and enable it for bright ones and stock aosp.
[Android Builders Collective] ezio84:
A little maintenance update to strengthen the 14th build, now all main things should be at a very good level :D

PureNexus mod 6.0.1-20160316

Download for Hammerhead (FOR TAPATALK USERS: copy past the link in Chrome): https://www.androidfilehost.com/?w=files&flid=50100

Wipes not needed if coming from the previous build.

Changelog:

Nav/Pie: fix big back icon in the buttons settings menu

Some framework fixes/improvements:

- [WindowManagerService] fix starting window issue

- force to remove window for BinderDied case

- Make accessing mWaitingForDrawn thread-safe

- MediaScanner: do not scan a file which cannot be read (this results in having broken entries showed up in e.g. Album app)

Device specific:

- Nexus 5: hammerhead does not have a pickup sensor available during sleep, hide the related feature from Doze settings

- Nexus 6P: fix a possible UI freeze after unlocking the device with the fingerprint sensor

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.
[Android Builders Collective] Yank555:
Can you give this one a go ?

--> https://www.androidfilehost.com/?fid=24459283995298355

It's set to consider 1100mA/h and above as fast, anything below 500 as slow (stock).

Works for me...

JP.
[Android Builders Collective] adm1jtg:
[MENTION=2033478]Yank555[/MENTION]

Mostly working here is what I tested and what I found.

Tested with cable directly to laptop ( .45 A) green light

Tested with standard charger #1 (1.23A) blue light

Tested with standard charger #2 (1.09A) blue light

Tested with true fast charger blue light

I have a usb passthrough device that measure amps this is how i know the actual output of the above chargers. As you can see I have 2 chargers that are in the 1A range and they are both still showing as blue. Can we up the limit to lets say 1300 or 1400 as I think that would get much more accurate results as I have never seen a standard charger that is rated higher then about 1200. I am thinking 1400 would build in a fudge fctor as the 1.09 still showed with your roms algorithm as above 1100

Update just pulled out my old blackberry charger which is rated about 700ma (.61A actual) and its still blue. Tested same cable again on laptop and it was green.

The lockscreen listed 1500ma even on the low end blackberry charger. Its like its reading if the data wires are in use for charging not the actual amps.

Enabling fastcharge in kernel seems to make no difference. Still green on laptop port.
[Android Builders Collective] Yank555:
Thing is, actual current drawn is not the same as the max negociated current the device is allowed to draw, I have such a device to measure, too ;)

Decision for led color and lockscreen text compare threshold with negociated, for one as that tells the device the kind of charger it's connected to (draw is lowered as battery gets closer to full to avoid heatIng up the battery which would damage it), and secondly as phones don't have a way to measure true current passing, so that info is simply not available.

I used 1100 as back in the days 1000 was 'normal a/c' while below (500/900 usb2/3) was 'slow'.

But, yep we could up the threshold, 1300 sounds good.

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r22 v1.01
[Android Builders Collective] adm1jtg:
I updated even my 700ma wall wort is still blue so there is still an issue
[Android Builders Collective] Garrykd:
Ooops . Caught napping :o:D

Angler version up now

https://www.androidfilehost.com/?w=files&flid=52030
[Android Builders Collective] Fastrite:
And I was enjoying the synchronized building! ;p

#whiteuimustdie
[Android Builders Collective] Garrykd:
....that reminds me, i can't find my nose plugs either....

... Damnit!

:p:p
[Android Builders Collective] efan3719:
If you were napping I must have been in a coma. :eek:

Here's the Flo build : https://www.androidfilehost.com/?fid=24459283995298509
[Android Builders Collective] Yank555:
Yep, that just depends on what shamu's kernel reports, and that is a sheer oddity unfortunately...

How much mA/h does lockscreen info report when you connect to it ?

When I connect my shamu to my PC, it detects "0" !!! So lockscreen doesn't even show it's charging, but it actually does as 1. LED goes on (so battery status is set to "charging" but doesn't report it to be connected to any charger, wtf !?) and 2. battery % go up...

I'm afraid moto has just been lazy / bad here (once again), I don't think there's gonna be a 'proper' solution for 'improperly' reported chargers on shamu :(

HH, angler both work perfectly fine, reporting correctly what they are connected to on everything I've been connecting them to (angler depending on the cable used, but usb-c cables are known to be mostly out of spec).

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r22 v1.01
[Android Builders Collective] Garrykd:
It was a nice day... I was tired from all the walking.......and what kind of guy hides in the bushes taking pictures of old men??!?

I suppose it was you that threw the peanuts in my mouth too? .... Sheesh, kids these days...

:p:p
[Android Builders Collective] Mikulec:
Thanks.

[MENTION=2095315]ezio84[/MENTION] - I loved one feature on custom Lollipop roms, "see through lockscreen" could it be possible to add it?
[Android Builders Collective] ezio84:
Yes, it was nice. But i'm a bit scared about loockscreen additional stuff: the sysui freeze on angler when unlocking with the fingerprint scanner was due to the lockscreen bouncher custom alpha feature (or the bouncher bypass one).

The keyguard code is very complex and a lot of its stuff is handled by other sysui features too (statusbar and so on). It's really easy to f##k something :D
[Android Builders Collective] Mikulec:
Thats why I ask, it was a little bit tricky even on Lollipop and only few roms have that implemented.
[Android Builders Collective] adm1jtg:
Just tested with elite kernel and seems like its ignoring anything you coded and does as follows now:

If ac charging then its blue

If usb charging then its green

The 700ma wall wort shows up as 1500ma fast charging in lock screen

Probably not worth more time on this as its a very minor feature anyway just irks me when I cant explain things or they simply dont work as they are supposed to.
[Android Builders Collective] chykal:
[MENTION=2095315]ezio84[/MENTION] thanks for the great ROM. It has all the features I need...perfect! Just an FYI there seems to be an issue with the link for the current build. I was able to browse to it from your profile in AFH and download it just fine.
[Android Builders Collective] dankoman:
those weren't peanuts...
[Android Builders Collective] Garrykd:
:eek::eek:

[YOUTUBE]XDBCEWy29Kg[/YOUTUBE]
[Android Builders Collective] dankoman:
they were cashews! i wouldn't feed you peanuts, not after i was publicly ridiculed in the slim kitchen for having peanuts on my thai burger ;).

lesson learned - there are certain nuts i know never to put in garry's mouth.
[Android Builders Collective] Garrykd:
Peanuts should be an optional garnish:p

mumble mumble mumble mumble...
[Android Builders Collective] ezio84:
It's a tapatalk bug, it cuts the link when you click on it to open in the browser. Damned app lol
[Android Builders Collective] Yank555:
Well it's interesting at least to see there is a difference.

What I coded is purely ROM side (and not a big deal code-wise). But it will just rely on whatever the kernel does report as "max. charging current".

That goes against the slow and fast threshold (stock AOSP for Lockscreen info, stock slow = 500mA/h, stock fast = 1500mA/h).

I relied on that and added the same test for fast only to set a different color when fast is detected.

And to quote you, it irks me pretty much a lot, too :p

So I'd not be unpleased to be able to get this sorted eventually.

Given it's a different thing with a different kernel, at least opens the door to do something on the kernel side. I have faux123's fastcharge mod in my kernel, I'd have to check what's in ElementalX and see how it's in stock kernel. Will try to make a build with stock charging code to test.

JP.
[Android Builders Collective] NeBouse:
[MENTION=2033478]Yank555[/MENTION]

Do you think that could help me to build YAOSP for my G4 ? It's new from yesterday, pure AOSP with absolutely no addition :

http://xdaforums.com/g4/development/rom-android-source-project-t3337687

The OP also posted the link to the device tree :

https://github.com/cile381/android_device_h815
[Android Builders Collective] Yank555:
Well looks promising, you have a device and kernel repo on his github, you just need to grab vendor (which I expect he got from TheMuppets, aka. CM's vendor stuff), likely from here :

https://github.com/TheMuppets/proprietary_vendor_lge

It certainly is worth a shot !

JP.

---------- Post added at 20:40 ---------- Previous post was at 20:25 ----------

Kay ... so I checked the usb forced fastcharge code, no way that'd brake anything, but since I started the build remotely, I had it finished, so I tested, conclusion, yep, that doesn't change anything at all.

But well, I'll have a look at the kernel code now I'm at it... let's see if I can find a derp in there.

JP.

EDIT : Dawm I fell alseep while typing on shamu in terminal emulator ... guess now is not the right time :(
[Android Builders Collective] NeBouse:
Nice !!

I'm sorry to bother you with so much questions but, what do I have to do now ?

FYI, your repo is synced on my computer.

What do I do with the device tree and vendor stuff ? (and more important, how ^^).

Regarding the kernel, I'd like to use a "custom" one, which is available here (and AOSP compatible) :

http://xdaforums.com/g4/development/kernel-llama-sweet-kernel-t3286514

Do I have to build it or can I use the prebuilt one and add it to the ROM package ?

Again sorry for all these questions, but I'm trying to learn lol.

Thx.
[Android Builders Collective] coolek33:
Hey [MENTION=2095315]ezio84[/MENTION]. I remember that on any slim rom we could swipe down (longer swipe) on lockscreen for notifications/QS to expand. Is there any mod you could implement for this behavior?
[Android Builders Collective] Yank555:
No problem asking ;)

You could add those repos to the manifest (.repo/manifests/default.xml). Have a look inside, it's not too complicated to understand how it is built (but ask if you're unsure ;)). Then just repo sync again, so it'll sync what's missing.

Alternatively, you could clone them with git to the correct folders (I'd add them to the manifest).

JP.
[Android Builders Collective] NeBouse:
Ok, noted.

Will have a look at the manifest tomorrow, class will be over for this week so i'll be able to switch back to Ubuntu.

Thx again.
[Android Builders Collective] kantjer:
Fist make sure you can build with stock kernel.

Changing kernel is usually quite easy, just swich repo and deconfig.

For example this is al I did to build Pure Nexus with ElementalX kernel
[Android Builders Collective] ezio84:
It already doest that, if you swipe down (e.g. from the middle of the lockscreen to the bottom) it shows notifications. Also the quick pulldown feature works if you swipe from lockscreen statusbar.

Or do you mean a different thing?
[Android Builders Collective] DroidIt!:
See....and that's why you should NEVER underestimate the [MENTION=2095315]ezio84[/MENTION]. Did you know he helped build Android? Invented fire? Cavemen copied the wheel from him before he could patent it. When Chuck Norris talks of the boogie man, he's talking about Ezio. Ezio showed David Copperfield everything he knows....OK done now :silly:
[Android Builders Collective] ezio84:
But Chuck is still a step over everyone :rolleyes: :D

When Chuck speaks about the boogieman, the boogieman becomes Chuck.
[Android Builders Collective] DroidIt!:
Lol :) How's it going Ezio. Good I hope. Miss talking to you guys. Two jobs, a new workout plan and an accelerated masters program and that basically leaves me with enough time to flash and not much else. I always keep an eye here though. :) I'll try to start popping in more often again. ;)
[Android Builders Collective] ezio84:
You're always welcome dude! :D

You know, here in south Italy we usually have two workout sessions instead of two works: one at gym, one at lunch. And the latter is harder :D
[Android Builders Collective] coolek33:
But I there are no notifications it does nothing. On slim it brought QS down if I remember right. Not a big thing without it but it would be another step for easier 1 hand phone control :p Luv your last build BTW.
[Android Builders Collective] amphi66:
I've continued to play w/ the AOSP Brower, but it continues to close on your latest. Works fine on Chroma (marshmallow) and on SlimLP. Thanks

I've uploaded to Dev-Host http://d-h.st/WrWq
[Android Builders Collective] coolek33:
Oh I remembered one more thing about swipes on lockscreen. We could swipe anywhere right/left on lockscreen for these 2 shortcuts on the bottom. That was pretty comfy. Do you Remember this [MENTION=2095315]ezio84[/MENTION]?
[Android Builders Collective] rignfool:
Chuck... Testa?
[Android Builders Collective] ezio84:
Found the culprit, and it's not a rom fault ;)

I took a logcat, this is the important error line:

E AndroidRuntime: Caused by: java.lang.NoSuchMethodError: No static method getPreferredHttpHost(Landroid/content/Context;Ljava/lang/String;)Lorg/apache/http/HttpHost; in class Landroid/net/Proxy; or its super classes (declaration of 'android.net.Proxy' appears in /system/framework/framework.jar)

It means the slim browser app is calling this method: getPreferredHttpHost

but it doesn't find it in the rom framework.

Indeed, that method has been deprecated since a lot of time:

https://github.com/android/platform...26d#diff-84a34f461109ce4d99ad600ae1ac28b0L206

I could add it back, but it means going against the latest android framework APIs. I don't think it's a good way.

Anyway, if you still want the stock aosp browser, grab the apk from a Cyanogenmod L or M build, they updated the stock Browser source removing that method: http://review.cyanogenmod.org/#/c/89923/

Mmm maybe we can set the smart pulldown for lockscreen, i'll take a look at it.

That was the old lockscreen widget implementation.

Maybe there are still some lockscreen widgets that let you do that.

Croce :D But Chuck always win a coin toss :D
[Android Builders Collective] NeBouse:
Could anyone please have a look at my manifest.xml ?

I've modified it to add the device tree, vendor tree and kernel (a custom one) for my device, but i get a fetch error...

Looks like i did not do it properly but i don't know what's wrong ^

https://dl.dropboxusercontent.com/u/23889066/default.xml

(Look for the "h815" parts ;) )

Thx.
[Android Builders Collective] Mikulec:
[MENTION=2095315]ezio84[/MENTION] [MENTION=2640853]Garrykd[/MENTION] Guys, does the "double press of power button" launch the camera app? Its not working for me. It just vibrates and do nothing. I am on latest Garrys build.
[Android Builders Collective] ezio84:
This line is wrong:

<project path="vendor/lge/h815" name="TheMuppets/proprietary_vendor_lge/h815" remote="github" revision="cm-13.0" />

You must use the main path without the "/h815" at the end:

name="TheMuppets/proprietary_vendor_lge/

Tried now, it works (at least on HH). I'm using PN gapps.

---------- Post added at 01:30 PM ---------- Previous post was at 01:28 PM ----------

[MENTION=653788]Mikulec[/MENTION] : found it, did you change the right camera lockscreen shortcut? If yes, that's why it doesn't work. The aosp code for the double tap power button action is linked to the camera lockscreen shortcut.
[Android Builders Collective] Mikulec:
Yes I did, looks like I have to put the shortcut back, lol. Thanks.
[Android Builders Collective] NeBouse:
Isn't it gonna sync sources for every lge device on my computer ?

EDIT : now I get this ...

error: Cannot fetch genesixx/LlamaSweet-msm8992 | 411.00 KiB/s
[Android Builders Collective] ezio84:
Yes.

If you don't want to sync all subfolders in that tree, you need to fork it, then remove the unneeded stuff, then push the changes to your fork, then add your fork into the manifest instead of the original TheMuppets tree.
[Android Builders Collective] NeBouse:
Ok, it means i need a github account lol

Gonna create one later in the day, I need to move now.

Btw, i have a new error message now :

error: Cannot fetch genesixx/LlamaSweet-msm8992.

Looks like there is also a problem with the kernel github.
[Android Builders Collective] kantjer:
Can be but those errors are almost always because of a typo in the manifest
[Android Builders Collective] ezio84:
genesixx/LlamaSweet-msm8992 seems online: https://github.com/genesixx/LlamaSweet-msm8992

Try to sync again in a while, and check for typos in the manifest as suggested by K.
[Android Builders Collective] NeBouse:
Yeah I meant in my manifest ;)

EDIT : Damn, i wrote "revison" instead of "revision"...
[Android Builders Collective] amphi66:
Thank you. That analysis was beyond me. As we see elsewhere, some old Slim features have just reached their time. Glad you are doing your thing!
[Android Builders Collective] ezio84:
Maybe the old slim browser source is still buildable with M framework source, after changing that method stuff.

I'll check it in a while.

EDIT: nope, too many build errors due to the different frameworks. It's easier to grab the Browser apk from a CM rom zip.
[Android Builders Collective] NeBouse:
Ok, found the culprit, a stupid typo (forgot an i in "revision").

Github account is created, repo is forked, and i'm actually cloning it to my computer.

Time to go now, I'll be back in 2 hours, hopefully all we be downloaded and I'll just have to remove the unneeded stuff and push to my github...
[Android Builders Collective] liquidreign:
I have shamu build from the 21st of Feb and when I try to dirty flash the latest build I get errors like play services is missing or installer is missing and I am unable do anything. Will clean flashing clear this up or is there something else I can do? What gapps should I use?
[Android Builders Collective] NeBouse:
[MENTION=2095315]ezio84[/MENTION] or [MENTION=2033478]Yank555[/MENTION]

Ok, repo forked, cloed to the computer, unnecessary stuff removed, and modifications pushed to my github :

https://github.com/NeeeeB/proprietary_vendor_lge/tree/cm-13.0

Now I have another problem...

Repo sync exits due to this : (it says duplicate)

<!-- Vendor repos for YAOSP -->
<project path="vendor/broadcom" name="YAOSP/vendor_broadcom" remote="github" revision="YAOSP-MM-6.0.1_r22" />
<project path="vendor/huawei" name="YAOSP/vendor_huawei" remote="github" revision="YAOSP-MM-6.0.1_r22" />
[B]<project path="vendor/lge" name="YAOSP/vendor_lge" remote="github" revision="YAOSP-MM-6.0.1_r22" />[/B]
<project path="vendor/moto" name="YAOSP/vendor_moto" remote="github" revision="YAOSP-MM-6.0.1_r22" />
<project path="vendor/qcom" name="YAOSP/vendor_qcom" remote="github" revision="YAOSP-MM-6.0.1_r22" />
<project path="vendor/htc" name="YAOSP/vendor_htc" remote="github" revision="YAOSP-MM-6.0.1_r22" />
[B]<project path="vendor/lge" name="NeeeeB/proprietary_vendor_lge" remote="github" revision="cm-13.0" />[/B]

What can I do ? How to add my stuff in the existing "lge" folder ? or do I have to create a new folder only for my stuff ? (which would be stupid since my device is "lge"...:silly:)

Thx. (I've learned more about github in 2 days than with my Java teacher :laugh:)
[Android Builders Collective] Yank555:
Oh crap, sorry lol I didn't comnect the dots ... lge <-> lge, I could have figured this out sooner :D

You should remove my entry and just leave your's.

I already have a vendor lge in my manifest for Nexus 5, that's clashing with your's, this needs to go :

<project path="vendor/lge" name="YAOSP/vendor_lge" remote="github" revision="YAOSP-MM-6.0.1_r22" />

Likely you'd need to delete the current vendor/lge subtree and resync.

Just don't test-build hammerhead, as that would then fail.

JP.

Sent from my Nexus 6P running Yank555.lu YAOSP-M 6.0.1_r22 v1.01
[Android Builders Collective] NeBouse:
Ok thx, gonna do this, yeah ofc won't try to build for HH ^
[Android Builders Collective] Garrykd:
.

Happy Birthday Slim Knight!! [MENTION=1277872]dankoman[/MENTION]

[YOUTUBE]NCQmRKs_SEQ[/YOUTUBE]

:p:p
[Android Builders Collective] NeBouse:
Ok guys guys, i'm ready to try to build.

I've tried the commands you told me before but it looks like some things are missing.

source build/envsetup.sh returns this :

including device/asus/deb/vendorsetup.sh
including device/asus/flo/vendorsetup.sh
including device/asus/fugu/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/htc/flounder/vendorsetup.sh
including device/huawei/angler/vendorsetup.sh
including device/lge/bullhead/vendorsetup.sh
including device/lge/hammerhead/vendorsetup.sh
including device/moto/shamu-kernel/vendorsetup.sh
including sdk/bash_completion/adb.bash

My device doesn't seem to be seen (h815).

And then , lunch aosp h815-userdebug returns this :

Invalid lunch combo: aosp

Thx.
[Android Builders Collective] kantjer:
did you setup your device in vendorsetup.sh

https://github.com/TeamTwisted/plat...mmit/df68c060bb7dbcf4fa1532d070ca0a17cc385204
[Android Builders Collective] NeBouse:
Nope, but I was on my way to do it.

I did have a look at all these vendorsetup.sh files and figured I had to do it for my device too.

Thx btw.

EDIT: ok, I've added a vendorsetup.sh file to my device folder (device/lge/h815) , and edited it to change to h815.

source build/envsetup.sh is ok now, i can see my device in the list.

But lunch aosp h815-userdebug still returns me "invalid lunch combo : aosp"...

I must have forgotten something but i dont know where.
[Android Builders Collective] VictorLapin:
[MENTION=2360351]NeBouse[/MENTION] and don't forget the underscore "_" between aosp and the rest. I see you put a space there.