yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] NHNXDA:
Is there allot of differences between the yank rom & ezio's, as I like the featureset.

I have pure on my N5X that I se as a backup atm, but problem is I need torch on the nav bar & pure hasn't added this as yet as a configurable option lol
[Android Builders Collective] indian84:
You can add torch button on Nav Bar. Again, I'm on Garry's PN build for Angler. But I'm sure Ezio is also using Slim Navbar. So you should have it too.
[Android Builders Collective] NHNXDA:
That's great, so I can test ezio's to see if it runs any quicker.
[Android Builders Collective] ezio84:
My build has volume wake and slim navbar, all main custom features are in post #6

Pn and YAOSP are both aosp based, so i don't think there are noticeable performance differences between the builds.

If you like YAOSP and it became a little slower, try also wiping caches and check background apps ;)
[Android Builders Collective] NHNXDA:
I've checked what I can, whatsapp is a pita to load tbh & that was a clean install, its got 6.7GB of whatsapp data but that's not all preloaded, as 99.99999% of that are images & video just sat doing nothing, actual whatsapp messages aren't exactly a killer for cpu, so I'm a bit perplexed why now it runs like a dog.

I did a full clean flash of the latest google stock rom, then flashed twrp, then yaosp, then added all my apps & uploaded all my data, of which my most widely used app is whatsapp for work.

Any advice how to track down the very sluggish behaviour would be much appreciated.

TIA.
[Android Builders Collective] ezio84:
Yes those issues are always hard to track down.

I had poor performances too some time ago and it was due to a crap version of Google play services, updating gapps fixed that.

Sometimes are just bad behaving apps.

Or the built-in kernel governor settings are not the best for your way of using the device.
[Android Builders Collective] NHNXDA:
TBH mate, its the 1st time I've ever had the N5 play up like this, I really don't know why tbh, its my reason why I haven't moved to my N5X as the N5 has been such a great handset, perfect size, fast, etc, it still fits the bill.

It has loads of memory available, so its not this, its weird.

I'll check for updated gapps, I use the one from.....I cant remember his name now damn it lol.
[Android Builders Collective] razrlover:
What up builders collective! Definitely have enjoyed yaosp and Purenexus mod by Garrykd for Angler

Now i am on Bullhead and Angler is gone. Been checking thru pages for couple days and just saw the uber yaosp build, thanks for uploading it

Will def flash, haven't seen any pn mods for Bullhead yet so just checking As I could have missed it.

Anyways very grateful for the community here!
[Android Builders Collective] Ryther:
My next step is build ezio's mod for bullhead, so stay tuned ;)

On the other hand, I have uploaded the UBER YAOSP on AFH: UBER YAOSP on AFH
[Android Builders Collective] razrlover:
Sounds good!

---------- Post added at 11:28 PM ---------- Previous post was at 10:39 PM ----------

Volte on Bullhead with rom/kernel working with tmobile.
[Android Builders Collective] dorqus:
[MENTION=4575569]Ryther[/MENTION] your bullhead build is working fine - thank you!
[Android Builders Collective] Yank555:
Well the changes on v1.10 are really minimal, no change in kernel or kenrel config (except the few commits of april's security patch), so if the previous versions have behaved fine, and now you see sluggish behaviour, it's most unlikely a ROM issue, rather some app updated that misbehaves.

But I totally agree, it's a pita to get behind such a problem :(

JP.
[Android Builders Collective] Ryther:
Ok, I've finished the preparation of all the scripts, got manifest from PureNexusProject, local_manifests from [MENTION=2095315]ezio84[/MENTION] (modded by me out of necessity) and now ezio's PureNexus sources are downloading, if everything goes right expect to have a UBER PureEzio later today (here in Italy it's 3 am - 12 to 20 hours of wait) or, at worst, tomorrow morning :good:

If I iron out some problems I'm facing with Linaro 4.9 toolchain, expect a Linaro version of YAOSP's and PureEzio's builds ;)
[Android Builders Collective] Mrcactuseater:
You are on fire, and it's great!

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Android Builders Collective] Ryther:
UBER PureEzio has been compiling since about 3 hours :thumbup:

In 4 hours I think I'll have a link for it ;)
[Android Builders Collective] razrlover:
Sounds great thanks!!
[Android Builders Collective] amphi66:
Good job! & Thanks . .. .. . out of curiosity, what kind of performance improvements do you expect using the Linaro Toolchain?
[Android Builders Collective] Ryther:
In the end the build failed :( dunno why, a problem with apks, and the suggested solution from the compiler was to use make update-api o.O

Moving onto your question, I don't know how much of an improvement Linaro will bring, I'm building with modded toolchains out of curiosity... Who will use the build will tell once I get Linaro working ;)
[Android Builders Collective] theesotericone:
I"m betting a lot of us here could give your our opinion on all the TC's available. I've built with most of them. But that would spoil all the fun your about to have. Make sure to try out SaberMod and Uber once you get linaro to build. :cool:
[Android Builders Collective] Ryther:
The YAOSP version I built is made with UBER ;) but yeah, I want to build with all 3 :D

I already have all 3 prebuilts available, all 4.9 except Linaro, which is 5.1 because with 4.9 I had an error about a command not present in a bin and I think I need a more recent version, but I got this one from Linaro site :confused: but with 5.1 building stops after 5 minutes :sly:

Which hint can you give on how to prepare a build for modded TC? Like "must" fixes etc?
[Android Builders Collective] mslatter:
How does one get the phone to prompt for adb connection permission (rsa fingerprint)? I'm running PureNexus - mod on my N6. I have tried with two different Windows machines (One Windows 7 and one Windows 10) and even Ubuntu 14 .04 and all I get on "adb devices"is my serial number and the word" unauthorized". I have tried different USB ports, I have tried different connection types, I have tried different cables, I have tried with SDK adb and Wugfresh, I have uninstalled and reinstalled drivers and I just cannot get the phone to prompt for permission. It used to be that you went into root settings and checked two boxes - one for applications and one for ADB. I no longer see that option or an option to revoke permissions (that I've read so much about) .... And I'm about at my wits end! Lol Any advice is appreciated.
[Android Builders Collective] efan3719:
i had this issue with my Nexus 7 recently but for the life of me i can't remember what i had to do to fix it. i think it happened right around i started messing with encryption. i think i wound up either fully wiping the device and starting from scratch or flashing the factory images again. i'll try to look around and see if i can remember what i did to fix it.
[Android Builders Collective] pkelly517:
You should have a notification that you are attached 'Charging Only'.

Press this for more options. Select PTP. Bam!
[Android Builders Collective] mslatter:
I have tried all the connection types... MTP, PTP and the others in there, with no luck. I've searched and searched with no luck so thought I either had to be missing something obvious or this is a new issue that not many have had. Thanks for the suggestion and I will try it again. Then I'll load a different kernel and if no luck, try a stock ROM. I never had this much of an issue with my G3 so thought I must have been doing something stupid. Who knows, maybe I still am. Lol.
[Android Builders Collective] ezio84:
Try all suggestions here, especially #9:

http://stackoverflow.com/questions/18011685/cant-connect-nexus-4-to-adb-unauthorized
[Android Builders Collective] indian84:
To break the silence in the thread. My battery stats on Garry's Pure Nexus Mod built and ElemementalX Kernel.
[Android Builders Collective] efan3719:
nice. have you had to replace the battery in your phone since getting it? towards the end on my N5 nothing i did would get it more than 2 hours SOT until i swapped the battery for a new one.
[Android Builders Collective] Ryther:
Update on my PureEzio building attempts: nothing to do, I got errors even on standard TC, I'll try to download again all the sources and see if I can compile it with standard TC :rolleyes:

In my search for info on my new 5X I have found this thread [GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life! it's applicable to all devices, not only latest nexuses ;) I'm trying it now and it seems it's doing well, no lag and the cpu time-in-state looks promising :good:
[Android Builders Collective] indian84:
No. I git a used device from one of my friends.
[Android Builders Collective] randman2011:
I'm really interested in this. I've been running your YAOSP port and am liking it more than Chroma but a settings FC in the hotspot menu is keeping me from loving it. I followed [MENTION=2095315]ezio84[/MENTION] religiously when I had my N5 and still have a soft spot for his work.

Now that the device tree has been sorted I may be looking into some Bullhead builds of my own as I've got a beefy BBQLinux desktop waiting for instructions. That made me hungry...
[Android Builders Collective] Ryther:
If you provide a log for the FC I can try to fix it, I don't know if I'm capable but trying never hurts ;)

The PureEzio stopped syncing tonight for an error, I've restarted the sync right now, I hope it finish quickly :silly:
[Android Builders Collective] razrlover:
Thanks for continuing! Steady checking from time to time. Glad you have persisted. How about using Garrykds source? Instead of PureEzio if your next attempt stops shy of complete?

Just a thought, thanks again
[Android Builders Collective] Ryther:
Thank you for the tip, that possibility never crossed my mind :D but I think I will try to ask ezio for help, I think the problem is at the application level where ezio made modification, because the OS part compiled correctly; usually my builds takes 5hr to complete because I'm working from a VM, the last attempt stopped at 4hr :silly: so I think I can gain more experience trying to solve the problem than taking a different road ;)

[MENTION=2095315]ezio84[/MENTION] can you try to look at this logs? I've already tried to google them, but the only thing I came upon is a "make upgrade-api" that stop for errors :silly: LOGS

EDIT: hastebin links:

stderr

stdout
[Android Builders Collective] kantjer:
Have you tried "make clobber" before starting the build?

And please next time use something like hastebin to post a log. That makes reading it for those trying to help much easier.
[Android Builders Collective] Ryther:
That error also came up right after a new repo init - sync, without any prior builds try; if I'm not mistaken, make clobber delete all generated files from previous builds (I'm building for YAOSP and PureEzio in different, independent folders) or I'm wrong? However I always use my script to launch the building process, and it automatically does a make clean before starting.

Thank you for the tip about hastebin, I'm still new to this world and this kind of advice are really useful to me :good:
[Android Builders Collective] kantjer:
If you already have a script doing "make clean" there is no need to clobber (it's the same thing)

Is the sync without errors?
[Android Builders Collective] Ryther:
Yes, it synced without error, I always check if sync completed correctly. Now I've downloaded again all the repos, tonight I will try again to build and report back, but I think I will get the same error :silly:
[Android Builders Collective] kantjer:
Try "repo sync -j4 -c -f --force-sync", that will force your local source to be in sync with the git.

I expect that if it's a source issue [MENTION=2095315]ezio84[/MENTION] himself will also have build issues.
[Android Builders Collective] Ryther:
This is my command from my repo_sync script:

time repo sync -j4 -c -f --force-sync > >(tee ${CUSTOM_ROOT_PATH}/logs/stdout/${ROM_NAME}/stdout_repo_sync_sh.log) 2> >(tee ${CUSTOM_ROOT_PATH}/logs/stderr/${ROM_NAME}/stderr_repo_sync_sh.log >&2)

The added part only logs the stdout and stderr on differents files whilst showing on the console, so I think it's not a source problem, maybe I miss something in my system enviroment? But YAOSP builds without errors, so I'm a little lost on this :rolleyes:

EDIT: added links to hastebin in the previous post
[Android Builders Collective] kantjer:
Have you ever been able to build with PureNexus source and Ezio's local_manifest?
[Android Builders Collective] Ryther:
No, this is my first try. I'm trying to port it to bullhead, if this can help
[Android Builders Collective] kantjer:
That should be straightforward, don't think any porting is needed.

I trust you used PN source and added Ezio's local_manifest.

I expect all device specific repo's to already be included in PN source
[Android Builders Collective] Ryther:
Exactly, used PN source and forked ezio's local_manifest, added some lines to remove unused devices and kernels etc

This is how my manifest looks
[Android Builders Collective] kantjer:
Try with "vendor/google" in (not sure if it's needed but worth a try)
[Android Builders Collective] Ryther:
My thought too, thank you for the hint!

EDIT: I looked into the vendor_google's repo, the only thing there is a molly device that I think is Android TV; I think it's unrelated to the problem (YAOSP doesn't even have it).
[Android Builders Collective] mslatter:
I simply can't get the phone to prompt for ADB authorization (RSA fingerprint)... I have spent hours (over a week) trying various things I've found online and still can't get the adb connection to work on my N6. ADB's "unauthorized" still persists regardless of what I've done with all the settings and I've tried so many things (on windows 10 tower, windows 7 tower and Ubuntu tower) that I've forgotten half of them. All those machines were used with my G3 though. I know I never hooked up my G3 or N6 to my laptop though, so I can try from scratch on it.

My ultimate goal for all this was to try Android N. So I tried doing the OTA thing to get Google to simply download it to my phone, but I'm getting the "Unfortunately, there are no eligible devices associated with this Google account" error.... Again, loads of research, loads of trying this and trying that, and no go. Not sure if it's because the N6 is rooted or not, or if it requires having a stock ROM, but I'm tired....

I guess I only need fastboot to work (which appears to work fine). Would there be any danger with me flashing the N preview when I'm still not able to get adb to work? Or could something happen where I absolutely had to use ADB and I'd be stuck?
[Android Builders Collective] NHNXDA:
Ok 2 things.

Whenever I do a search & select the google ad link at the top of search results in chrome or the included browser, it fails to ever get to googleadservices.com, used to work fine until I swapped to yaosp.

2nd, is there a way to default so that when you plug into USB it will auto select mtp so I don't have to drop down the status bar to select USB options & mtp to connect to my pc, ATM its a pita to jeep going that lol.

TIA.
[Android Builders Collective] Yank555:
Odd, no such FC on my angler.

I'd be interested to see the log as well.

Been quiet on YAOSP front lately, been busy bringing up Slim6 angler, shamu an hh past week, all 3 are up ;)

JP.

---------- Post added at 06:00 PM ---------- Previous post was at 05:56 PM ----------

1st : This is due to the adblocking hosts file in my ROM. You need to replace the file with just 127.0.0.1 line.

2nd: Dunno, the setting is 'not persistent' in AOSP.

Although it autoswitches to mtp for me when I connect it to my Linux VM.

JP.
[Android Builders Collective] Mikulec:
Hows the Slim6 in terms of features? Are some features already in?
[Android Builders Collective] Yank555:
Not yet, polishing the base is going on atm ... features should get in shortly.

JP.
[Android Builders Collective] ezio84:
You have a lot of errors about changed api in /home/ryther/android/PureNexus/out/target/common/obj/PACKAGING/public_api.txt

Maybe your build script didn't do a make clean: delete the OUT folder and build again, maybe it'd do the trick ;) Also try to reset ccache if you switched between toolchains.

---------- Post added at 09:01 PM ---------- Previous post was at 09:00 PM ----------

Very weird....

Btw you can flash factory images (M or N-preview) with fastboot, you won't need adb for that.
[Android Builders Collective] mslatter:
Thanks Ezio, had just realized I'd posted in the wrong thread....never knew how folks do that but now I know! LOL. Yeah, I even flashed Pure-Nexus-Mod clean (only used google authentication to get it to boot) along with SuperSu 2.65 (the stable one) as I'd been using 2.71. I'd read somewhere that 2.71 doesn't work on all apps (as I type it maybe it was related to N) but I thought....I'll try clean with the stable SuperSu and still Unauthorized. I'll get it figured out one way or another :good:

Thanks again, very much!
[Android Builders Collective] ezio84:
My build has built in system mode supersu (2.68 at the moment), flashing another version can break something ;)
[Android Builders Collective] mslatter:
LOL sometimes it's the little things we miss along the learning tree that can cause huge pain down the road. Reason I always flash SuperSU is once (a while ago) I flashed a ROM that had Root built in - and I was told NOT to flash SuperSU. So I skipped that step, and I turned root on in Settings, then restored all my apps with Titanium. I rarely use all my apps all the time, but a few days later another ROM came out. So I backed up all my apps again with Titanium, and installed the new ROM not thinking anything about it. Restored with Titanium again and then realized some of my apps didn't have any data in them...odd. So I restored my previous backup and realized that some of the apps hadn't restored all the data when I didn't flash SuperSU.....and I'd then backed up unfinished apps over the good ones, and lost it all =(

So I've always installed SuperSU as an extra step and it's never let me down....until maybe now =) I'm on N but when I switch back, I'm going to have to try NOT flashing SuperSU and see if adb works. If it does, you're my hero...again!
[Android Builders Collective] ezio84:
It could be the culprit, fingers crossed ;D
[Android Builders Collective] adm1jtg:
Will you be continuing yasop as well as slim6 or will you be moving your focus to just slim6 now?
[Android Builders Collective] randman2011:
I was getting force closes from Google Now, but that was a layers issue. No such luck solving this one. I can't access the Hotspot menu at all from the settings, but I can add the hotspot QS tile. While toggling that does nothing I can long press it to get to the hotspot menu. From there, trying to enable a hotspot gives me a FC. Log attached.
[Android Builders Collective] Ryther:
I'm sure the make clean is done, observed it while testing the script ;) now I've cleaned ccache, synced all the files and using standard TC, I will report tomorrow :good:

[MENTION=2033478]Yank555[/MENTION] I'm requesting your kernel masteries here :D there is a way to set a cpu governor tunables at compilation time? Like target_load in interactive, for example? I've tried all the afternoon, checking in the kernel code but... nothing :silly:
[Android Builders Collective] Ryther:
Nothing to do, standard tc, completely new working space, cleaned ccache, same error :crying:

I've already checked the source code for interactive in driver/cpufreq/cpufreq_interactive.c and found nothing regarding tunables :( can you link to me something about the init.[device].power.rc (or .sh)? I've found this , I think I need to put in there lines like

echo /sys/devices/system/cpu/cpu0/target_load xxxxxxxxxxxxxx

Which carrier do you have a contract with? On mine 5X tethering is working without problems.

Try to put this line

net.tethering.noprovisioning=true

in the build.prop and reboot
[Android Builders Collective] Yank555:
You need to change/add lines here settong the tunables :

https://android.googlesource.com/device/lge/bullhead/+/master/init.bullhead.power.sh#78

Kind of like this :

https://github.com/YAOSP/device_moto_shamu/commit/d4550eb2212c87bbf15ae77126db0547f22df268

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

I tried to load a different kernel with your yaosp rom for shamu (elite kernel) and had all kinds of LTE/connectivity issues. I posted logs in their thread as I have never had any such issues with your original rom and kernel combination. They told me you have a heavily modified ramdisk and this was the cause of the issue.

Now I am torn as you know I have followed and used your rom since it was first made available and I think it is definitely one of the best out BUT I also miss the flexibility to play with other kernels and mods. Is there some way I can use your yaosp for shamu and also have a standard ramdisk so I can test with elite as well? Maybe flash a kernel like leankernel first as if I recall that one has its own ramdisk based on stock?

I should mention I would like the ability to easily go back to your custom setup as I may well find i like it better.
[Android Builders Collective] ezio84:
Yes i removed the build due to the rotation issue on hammerhead:

http://xdaforums.com/showpost.php?p=56661310&postcount=28602

Will push a new build when the Slim team fixes it ;)
[Android Builders Collective] DroidIt!:
Ah OK. I don't use the rotation lock anyways but understandable. I'll be quiet and patient now. :)
[Android Builders Collective] lordvj:
Hey Ezio, Love your slimkat builds, Just facing a quirk. Could you tell me how to turn off TRLS/TRDS ? I want to use the stock android theme. Once TRDS/TRLS is activated , I can't seem to find a way to turn it off.
[Android Builders Collective] kagwind:
Source from Dankoman:

http://xdaforums.com/showpost.php?p=56664179&postcount=28612
[Android Builders Collective] ezio84:
Oh so Slim devs have fixed the sensors issue, building again :D

That's how it's intended to work :P Probably you just need to get used with it.
[Android Builders Collective] Grondinm:
Hey guys. I know i've been quiet of late been messing around with LP but new builds are coming today one last thing to test and i will push the builds. Probably about 1h or so...then i'm going to work on updating the TWRP curtains with material...watch for those hopefully i feel up to it today...
[Android Builders Collective] fusionjack:
those actually are not the fix. :p

the device needs to be updated with this commit:

http://review.cyanogenmod.org/#/c/75774/

Sent from my One A0001
[Android Builders Collective] Grondinm:
and we are off. Builds building as i write this.

Updated to slim 8.12.1 code

UKM updated to V3.5

Flo kernel compiled with cortex_a15 optimized toolchain 4.9 thanx to [MENTION=4911350]RobbieL811[/MENTION] for the fixes(please let me know if it fails to boot...i'm going with it can't test as tablet is occupied...easy fix if it fails to boot)

Enjoy
[Android Builders Collective] danarama:
So who else is building L?

[MENTION=4911350]RobbieL811[/MENTION] ?

What did you do about the binary stuff?

I used the CM extract-files.sh but that only pulls vendor/lge files off the device. Where did you get broadcom and qcom from?
[Android Builders Collective] Grondinm:
The loony bin is updated with the preview blobs...at least for nexus devices
[Android Builders Collective] DroidIt!:
Downloading and updating anyways. I feel like a flash and too good of an update [emoji16]

---------- Post added at 11:03 PM ---------- Previous post was at 10:56 PM ----------

Oh wait, so the proximity issue isn't fixed in your newer new rebuilt rebuild? ?
[Android Builders Collective] RobbieL811:
Use the binaries from TheLoonyBin. Just make sure to pull from the lp5.0 branch. We have updated that branch with the preview binaries until source comes.
[Android Builders Collective] danarama:
Awesome guys. Thank you.