yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] luisangel89:
Ahhhh got it! Thank you sir ;)
[Android Builders Collective] Deadsayer:
The whole story is that I went to text a buddy and realized I hadn't set my default SMS app so it was trying to connect to google hangouts and I didn't have time to mess with it and set it up right so I just locked my phone and stuffed it back in my pocket. When I went to check it later is when it started doing what I described.

I clean flashed the ROM. The Kernel was whatever kernel you used, so I guess that's stock. I don't even know what xposed is so no, I didn't use that. I did not use slim gapps. I used banks gapps. Is that a problem?
[Android Builders Collective] theesotericone:
Not even close. lol Getting the build env set up properly is like graduating kindergarten. Figuring out all the other stuff goes from 1st to 12th grade. Figuring out how to use Git is about college level. Figuring out Smali is a PHd.:cool:
[Android Builders Collective] adomol:
Hi guys... I've got a build question. It's not for slim though, but opti. Hope thats OK?

I'm trying to get a build going for hammerhead and ran into this error...

target thumb C++: libRS <= frameworks/rs/rsAdapter.cpp
error: unknown warning option '-Wno-reserved-id-macro' [-Werror,-Wunknown-warning-option]
error: unknown warning option '-Wno-format-pedantic' [-Werror,-Wunknown-warning-option]
build/core/binary.mk:873: recipe for target '/home/ozric/aosp/optipop/out/target/product/hammerhead/obj/SHARED_LIBRARIES/libRS_intermediates/rsAdapter.o' failed
make: *** [/home/ozric/aosp/optipop/out/target/product/hammerhead/obj/SHARED_LIBRARIES/libRS_intermediates/rsAdapter.o] Error 1

I'm building on an arch linux box (bbq) which I have built slimlp on quite a few times before. Maybe this has something to do with UBERTC? Any ideas?
[Android Builders Collective] physwizz:
Ditto
[Android Builders Collective] reS28raM:
I also built the rom for HH on BBQ and didn't have that error: are you using the unmodified manifest.xml from the rom? OptiPop's manifest has all which is needed (device tree and blobs included) so I suggest to do the first sync using that one alone.

Another thing which is not standard is that the lunch command should be run at the very beginning of every session. No need to run it again for that session though.

Another tip: not all optimizations mix well, if you compile without any, which is the default if you don't enable them in your .bashrc, you'll run into trouble; the same for some combinations of them.

Here the optimizations I used on BBQ/HH (thanks to Lennhart [MENTION=250713]freak97[/MENTION]):

# Enable some OptiPop optimizations
#
export USE_O3_OPTIMIZATIONS=true
export USE_HOST_4_8=true
export KRAIT_TUNINGS=true
export STRICT_ALIASING=true
export FFAST_MATH=true

# Enable to watch kernel compilation closely
export KBUILD_VERBOSE=1

# EOF

If you modify them now don't forget to run ccache -C and make clean.

Hope this help

P.
[Android Builders Collective] AirOne70:
Same thing for me.. Building SlimLP by Ezio for Hammerhead, and this is what I have everytime (even after ccache -C ):

...
Notice file: external/stlport/NOTICE -- /media/airone70/Extended/Android/Builds/slim/out/target/product/hammerhead/obj/NOTICE_FILES/src//system/lib/libstlport.so.txt
/media/airone70/Extended/Android/Builds/slim/out/target/product/hammerhead/obj/SHARED_LIBRARIES/libbacktrace_intermediates/BacktraceThread.o:BacktraceThread.cpp:function vtable for BacktraceThread: error: undefined reference to 'Backtrace::FindMap(unsigned int)'
collect2: error: ld returned 1 exit status
build/core/shared_library_internal.mk:68: recipe for target '/media/airone70/Extended/Android/Builds/slim/out/target/product/hammerhead/obj/SHARED_LIBRARIES/libbacktrace_intermediates/LINKED/libbacktrace.so' failed
make: *** [/media/airone70/Extended/Android/Builds/slim/out/target/product/hammerhead/obj/SHARED_LIBRARIES/libbacktrace_intermediates/LINKED/libbacktrace.so] Error 1
make: *** Attente des tâches non terminées....

#### make failed to build some targets (01:06 (mm:ss)) ####

Any idea ?
[Android Builders Collective] reS28raM:
This is easier because Slim follows AOSP standards on building closely. :)

You should grab ezio's local manifest here (pay attention to the branch!) :

https://github.com/ezio84/scripts/b...tips/local_manifest_backup/local_manifest.xml

Then put it into .repo/local_manifests/ and sync

Damn, ninja'd :)
[Android Builders Collective] Laggalot:
lol Halp. Im on Ezios latest build ( clean flashed 2 days ago) and I just went into Developer settings and checked everything out... well seems like I shouldnt have done that, because 1 second after I had checked the RTL one ( it kinda inverts the whole UI) I get the message " Unfortunately, System UI has stopped." all the time. I dunno how to return back to normal now :P Do I have to flash clean again? XD
[Android Builders Collective] ezio84:
:( Are you on the latest 5.1.1 radio, right?

I use slim gapps only so i don't know how banks behave, but I don't think they were the problem.

But if you have time, try again with slim ones. It could also be just a bad flash or something else.

The error about libbacktrace is due to the latest fwbase, libcore and system core commits. Do a make clobber and reset your ccache to fix it ;)
[Android Builders Collective] AirOne70:
This is already what I'm doing. :silly:

Going to try.. Thanks ! :fingers-crossed:
[Android Builders Collective] reS28raM:
Yep, I saw. I'm building it on Ubuntu but not yet updated so I missed those commits. If they are what I think clearing ccache is mandatory because they are about optimizations but after that all will be ok, never had an issue building Ezio's rom. :)

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Android Builders Collective] ezio84:
Lol now I won't try it :D

Will check if there's a commit somewhere that fixes that, or I'll remove the entry at all :D

Try a system wipe but if the setting is saved, how it should be, in the data partition, you are f###ed lol.
[Android Builders Collective] Laggalot:
Well I could hang in and wait till u get a fix because it shouldnt matter if its saved when it would work again ^^

Im just doing a Nandroid backup right now... XD
[Android Builders Collective] DroidIt!:
You're getting repeated system.ui FC's though right? So if you do a nand you'll just save a borked system ;) I would just do a dirty flash and see if MAYBE that fixes it. Or if ezio's right and he probably is :) then a clean install.
[Android Builders Collective] Laggalot:
I know that XD thing is atm I if he maybe Ezios fixes the problem with RTL and I flashed that build it could work again ^^ Im already thinking about clean flashing again, but man that would suck....
[Android Builders Collective] ezio84:
Grab a logcat, maybe it'd be easier to find a fix.

PS: btw there's a river of rtl commits on cm gerrit, i don't know if it'd be easy to find the fix (and i don't know how that stuff works).
[Android Builders Collective] Laggalot:
Alright Im wiped and now its booting back up. Well the thing is I dont know how :/ since it doesnt let me use the file explorer. ( Does the file explorer in recovery work? ;) )

PS at your PS: well in that case Im just gonna install fresh XD
[Android Builders Collective] ezio84:
Oh cool, so the wipe fixed it? Then nevermind the logcat, i'll just remove the entry, let's avoid too much headaches about this maybe useless feature :p :D
[Android Builders Collective] Laggalot:
yes remove it.... It happened straight away on a fresh install too XD
[Android Builders Collective] ezio84:
Doing it now ;D
[Android Builders Collective] Ryther:
I'm on M8974A-2.0.50.2.26 radio (the 5.1.1 one, just checked) but this is a known problem from the first release of lollipop, i'm having it till the start :rolleyes: https://code.google.com/p/android/issues/detail?id=165558 here the problem report i found, a lot of people seems to have this problem, on a lot of different devices :rolleyes:
[Android Builders Collective] DroidIt!:
I have read of some users actually going back to kk radios and getting better reception. It all depends on your hardware, location, and the strength of the signal where you spend most of your time. I would try going back to a radio, no matter how old where you can remember not having a drain problem. Unless you're carrier has instituted some sort of new feature for your phone (like tmob US did for WiFi calling on the N6) I couldn't imagine you getting any I'll side effects from flashing an old radio. ;)
[Android Builders Collective] AirOne70:
It worked! Thanks! :D

Is this color choice a new feature? Or a glitch lol ?

Every color choice are like this one.

Sent from my Nexus 5
[Android Builders Collective] Ryther:
I will try the KK radio, but the problem is not the reception, I'm getting the best reception I've ever had. The problem is the sync process or something of sort, which doesn't close the established connection thus using a lot of "mobile radio active". But this problem arise only in some phones, my friend have a nexus 5 on stock 5.1.1 without this problem but different operator, but reading the last report on that Google issues tracker, I've seen someone have tried different SIMs of different carries without success :S and a lot of people on different devices (examples are Z3, S6, OPO, Nexus 6, Nexus 5 etc) are getting this same problem after the upgrade to LP, even my girlfriend on a stock, non rooted moto g 2014 is having this problem. Still Google put small priority on this issues :S so I'm actively searching a solution 'cause I want my long battery life back while retaining the latest goodies for application debug purpose (I'm developing some apps)
[Android Builders Collective] ezio84:
The density handling is different (it should be better) in the latest source, set again your density value in Display-LCD Density and it will be fixed ;)
[Android Builders Collective] preacher65:
I suspect I already know this answer to this, which is probably "yes", but... would you folks recommend a clean flash switching builds? Or can I get away with wiping system? Want to try garrykd's mako build, partly since the slimsaber art optimisations in ezio84's build break xposed. (Yeah, I know, xposed, sorry. :p) And partly just to try a different build. :) Can't find a github for garrykd's builds, so not sure if you're using the same art stuff, or what other differences there might be. I know the answer to everything is always clean flash, but...
[Android Builders Collective] efan3719:
i usually just wipe system when i switch between slim builds. but if you notice anything unusual then try the clean flash method. haven't really had any issues just wiping system though.
[Android Builders Collective] preacher65:
Thanks, will try it. Was just looking for some reassurance that at least it might be okay. :) And that's what nandroids are for, right?
[Android Builders Collective] adomol:
Thanks!

Yeah, I didn't set any compiler flags.

Is it the same if I export them in .bashrc or just put them in boardconfig.mk?
[Android Builders Collective] efan3719:
yup. nandroid. break stuff. restore. :D
[Android Builders Collective] reS28raM:
Never gone so deep into Chet's customization which is quite complex and involves a lot of files, if you add them to environment through .bashrc you can be 100% sure they will be read by all modules which uses them. ;) Also this is what [MENTION=250713]freak97[/MENTION] is doing, he is in the development group of the rom.

Glad it helped

P.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Android Builders Collective] DroidIt!:
Well, I would just try flashing an older radio where you were basically getting the same reception without the drain. Flashing an old radio won't remove any of the new features or anything else that the L update brought or for that matter anything M will bring. So, flashing an old radio won't affect any of your deving capabilities at all. The radios are completely separate from any ROM with any features you may run. :)

---------- Post added at 01:03 PM ---------- Previous post was at 12:54 PM ----------

Oh, hey [MENTION=2033478]Yank555[/MENTION] were you planning on throwing up a new N7 build fairly decently soon. Not asking for an ETA, but was just wondering because I'm having issues with a couple of apps fc'ing that didn't fc before that are pretty important for me. Sooo, I was wanting to flash another build and see what happens with them and just don't want to go backwards. :) Again no rush or anything, was just wondering. ;)
[Android Builders Collective] Ryther:
Ok, I'm in the process of charging the phone, so I can reset the stats and start anew. Hope this stop my hungry phone, but I'm not that sure XD
[Android Builders Collective] preacher65:
Tried to look this up in github, but may have failed*. Can anyone tell me if SlimLP always uses AOSP webview, or does it include code to check for the Google Play version and revert to AOSP if not found? If not, is it something that's likely to be included? I've installed the Google version from Play Store, but not sure if there's any point unless the ROM supports it. :) Not really sure how it works though! ;)

* I looked here for something similar to this but not 100% sure if I'm looking in the right place, or understanding what I'm looking at.
[Android Builders Collective] AirOne70:
That's fixed it ! Thanks (again). :victory: For now, everything is perfect. :cool:
[Android Builders Collective] Deadsayer:
I will give it another shot. Probably next month, as the trend around here to set mobile data on by default in ROMs tends to use a lot of my data setting up apps and everything after setup before I can turn it off (Only have 100mb/month. ****'s expensive in Canada) and I'm almost at my limit already for this month.

For the brief time that it did work after I flashed it, the only things I missed from Terminus was the quick pull app tray (pull down from the top right corner and it would pull the app tray down without having to pull the notifications down first and then the app tray) and the option to change the location of the close all button in recents. Not used to having the close all button on the top right. I'd rather have it in the lower right. Other than that it was much snappier than Terminus.
[Android Builders Collective] adomol:
Anyone here building on a server? I'm thinking about getting an inexpensive older server to use for building. My current setup is pretty slow, 2core intel desktop with 2g ram... ?

I can get a cheap used server (less than the price of a 1+1) with these specs:

Poweredge 2950 III

Xeon E5450 [MENTION=3800434]3.0[/MENTION]ghz x2 (8CORES)

32gigs ram ddr2

Includes the usuals... Intel video, networking... blah blah blah.

And of course room for lots of HHD or SSD

Now the question is, is a server good for building with? Its about the same age as my current machine but it has way more balls and its in great condition.

Any thoughts on this?
[Android Builders Collective] Ryther:
Nothing to do, even after changing back to the radio that gave me the better battery time, the mobile radio active problem persist :S back to square one :S
[Android Builders Collective] efan3719:
[MENTION=2095315]ezio84[/MENTION] so i'm trying to add in expandable volume panel and silent mode but i'm getting conflicts and build errors as i am rubbish at fixing conflicts. what all would i need to pick to get that into my rom? i have a feeling i'm not grabbing all the right stuff to begin with... :confused:
[Android Builders Collective] ezio84:
Instead of cherrypicking , use the "git pull" download link on this:

https://review.slimroms.eu/#/c/4350/

and this:

https://review.slimroms.eu/#/c/4329/

and cherry-pick these:

https://review.slimroms.eu/#/c/4330/

https://review.slimroms.eu/#/c/3040/

The git pull link let you pick all commits in the dependency tree in their needed order (the ones you see under "related changes" when you open the top commit of the tree).
[Android Builders Collective] reS28raM:
You are not saying the most important spec: the speed of the SATA bus. I use one 7-years old server and I am very satisfied - best PC I ever had but you'll see the difference between 6Gb/s and 3Gb/s even if you use an SSD: the latter will take around the double to compile. Also double-check the availability of good video drivers for the graphics card, a search on google will suffice for this. I am able to compile the rom in 20 minutes while using the PC normally so my advice is: take it. The biggest issue with those machines is the noise indeed... A brand-new fan will cost >€40 each... If you can live with it, take it.

Edit: the form factor (rack mounting) can be a problem even when adding a simple device, not all of them would fit, I would suggest a "normal" desktop PC, better be safe then sorry. ;)

http://m.ebay.it/sch/i.html?isRefin...-42359-5854-0&rvr_id=843924164652&_mwBanner=1
[Android Builders Collective] Yank555:
Good question, probably not today at least, I'm pretty exhausted after a pretty perfect trackday yesterday, I think I'll pronanly just be doing "nothing" today, just plain wasting my time lying on the couch ;)

But well, I could also get bored doing that and switch over to the PC :D

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Android Builders Collective] DroidIt!:
:) Being lazy myself today. 20+ people over yesterday for a cookout party. Still drinking coffee.
[Android Builders Collective] kagwind:
Have been doing some programing these two weeks, and got back some features I would like to use:

Put SmartPulldown to SlimActions.

Put DoubleTap to navbar.

(Unfortunately, I'm never a PIE guy, and I prefer less buttons. Therefore, this is the only choice.)

Cursor buttons in navbar when typing, click to go left/right, longpress to go up/down.

(I found out Kufi had a commit in kk that almost looked the same at the end of my debugging... , I should have known better.)

Fix Menu button visibility issues.

Try to put a filter in Privacy Guard.

(I'm not sure whether it works as intended. Not all apps are filtered correctly. I tried several different approaches, but eventually back to the Kufi way.)

Don't use PG commit. Broke something.

Tests are welcome. Codes are in

frameworks_base

Settings
[Android Builders Collective] JaylanPHNX:
I'm getting a bit frustrated with [MENTION=2095315]ezio84[/MENTION]'s Hammerhead build, mostly because of including SuperSU by default and putting it (and other things) in Settings. It's not in the app drawer, I'm having Settings force closes, and other trouble. Am I messing stuff up flashing SuperSU zip when dirty flashing? I'm also having device not supported in synapse with code_blue kernel, though I know that's a bit off topic. I'm not *****ing at Ezio, just trying to figure out what's wrong on my wife's phone.

It's baconnn!
[Android Builders Collective] danarama:
Flashing SuperSU won't cause a problem with settings. Many ROMs include it now and I do not routinely. All the flashing does is.replace what's already there so no.harm done. Whatever the source of your force close, it's not SuperSU
[Android Builders Collective] AquilaDroid:
For the "Device not supported" -

In terminal emulator type:

su

UCI reset

uci

Reboot

(I assume you do have UKM 3.8.1 installed)
[Android Builders Collective] theesotericone:
That's the number one reason I build on my laptop. I'm on the couch right now.:laugh:
[Android Builders Collective] JaylanPHNX:
Thanks. I tried that, but forgot the reboot step. Switched to a different kernel control app for now. I'll try again later.

It's baconnn!

---------- Post added at 02:47 PM ---------- Previous post was at 02:43 PM ----------

I reflashed ROM (clearing system and caches) and it worked, then re-applied layer theme: force close. Weird part is I know I was able to open the System Tools under settings with that theme applied before. I may have to clean flash the next build. For now, my wife wants her phone back. [emoji56]

It's baconnn!
[Android Builders Collective] ezio84:
Why are you flashing supersu zip if it's bundled with the rom? It's hidden in the drawer on purpose, you can run it from the System Tools menu.

If you do that to have it back in Settings, expect those problems.

Ps: I won't change that behavior atm, because i like it and I'm too lazy to flash supersu each time [emoji14]
[Android Builders Collective] a g bell:
Ezio does layers work on your ROM?
[Android Builders Collective] ezio84:
Yes.
[Android Builders Collective] a g bell:
😲😲😵

Thanks no need for the song?

Think l might give it s spin then?NO new builds since 31 of last month?

Sent from my Nexus 5 using rooted M
[Android Builders Collective] JaylanPHNX:
Just habit, I guess. I think I have (mostly) everything worked out.

From my SlimTab Pro 8.4
[Android Builders Collective] Yank555:
Ah well ... I made a tiny stop from my 'couch-ing' and updated my shamu kernel to M-preview but for SlimLP 5.1 (so usable for current shamu SlimLP builds).

So far looking good, and a few things (added by Google) I've seen look like potentially interesting improvements.

Anyone willing to test, it's up in my forum (link in my OP, post 14).

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.0 kernel.
[Android Builders Collective] mslatter:
d850 update

Built this about 6 times over the last 4 days with no luck At some point, my packages/apps/Settings/res/layout/dashboard_category.xml had got borked. When I tried fixing the problems, I just created problems somewhere else...so started a full download last night and went to bed. If anyone can tell me how to restart the build process but keep all the downloaded data (so it doesn't take hours to download again), I'd appreciate it.

So this has the latest Slim code, and has run fine for me today so far. One thing I noticed is Softkeyz is NOT working on my phone for some reason, so as before any new flash, be sure to make a full backup.

To avoid problems....

1. Full Wipe

2. Flash Rom

3. Flash Gapps (I used Slim's 06/05 gapps from their XDA thread: http://tinyurl.com/pncj8jk )

4. Flash SuperSu ( http://xdaforums.com/apps...v2-05-t2868133 )

Will post on G+ - let me know of any issues you find please?

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

md5: 5110c3654c9523a8ceca0e9c4a90f7ef

Huge thanks to the following for making all this possible:

Slim Team - for a great ROM

invisiblek - CM device maintainer

arcardinal - Slim device maintainer

ezio84 - RRO fixes (Layers rock)

X-san - commits help / time saving script!

...and of course, XDA members for help / hints e.t.c!
[Android Builders Collective] mcgi5sr2:
Latest i9300 build is up, everything is working fine and dandy. Let me know any issues :)

Slim-i9300-5.1.1.alpha.0.3-UNOFFICIAL-20150607-1954.zip
[Android Builders Collective] efan3719:
New builds for Hammerhead and Flo. Added Expandable Volume Panel and Silent Mode thanks to [MENTION=2095315]ezio84[/MENTION] :good: in addition to Slim Recents. Links are in my sig or post 8 of this thread. Flo is up now and Hammerhead will be up in a few minutes.
[Android Builders Collective] ezio84:
The new build is quite ready, Griff should have fixed all slim recents bugs with the latest patchset so when I got home I'll try it and if all good I'll push the build :D

EDIT: still something to fix.

The point is that you usually don't need to open supersu, it's kinda a flash and forget app (at least you see its popup when a new app requires root permissions). That's why i like to hide it from the drawer and put it in the system tools menu.

Btw the last stock superuser, bundled with slim, is now working well and it's handled by privacy guard too, I'll try to switch to it and see how it goes.

About built-in apps, I think I'll remove Adaway since the new incoming build, because if the user want to try an a different anti-advertising app and removes the adaway apk, the system tools menu FC.
[Android Builders Collective] csolanol:
Could you help me to revert the recents commit from your repo and add the new one?. I am bored at work and would love to build and test too.

Ty.

Edit: If i git revert commit_id i get some conflicts.