yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] trailblazerz11:
Found some time tonight to work on Google's bionic. I dove right in thinking it wouldn't be too bad however error after error come up, it may take awhile and since I failed and didn't really prepare to revert back, probably no normal builds until it's working.

Progress if you are interested:

Bionic files seem to compile fine.

Dalvik was updated to AOSP since there was some reliance from the new bionic (though quite a bit of other updates)

Having issues mainly with some /externals, bionic is conflicting redefining types/functions with them. Particularly bash and rsync which AOSP doesn't use, so not much reference to find a fix.

Stuck on bash currently, but off to bed, heres the error if anyone could help :confused:

/Users/chet/src/bash/src/parse.y:131:14: error: conflicting types for '__errno'
In file included from bionic/libc/include/signal.h:31:0,
from bionic/libc/include/sys/select.h:34,
from bionic/libc/include/unistd.h:34,
from bionic/libc/include/fcntl.h:34,
from external/bash/include/filecntl.h:24,
from /Users/chet/src/bash/src/parse.y:27:
bionic/libc/include/errno.h:44:22: note: previous declaration of '__errno' was here

...
...

make: *** [/home/juston/cm/out/target/product/mako/obj/EXECUTABLES/bash_intermediates/y.tab.o] Error 1
make: *** Waiting for unfinished jobs....
[Nexus 4 Android Development] trailblazerz11:
Good news is it has built fine, I gave up on fixing external/bash for now and just removed it. Further errors were not as difficult to deal with.

Bad news is it gets stuck on boot animation. Light debugging and googling says perhaps its libcore, I updated it and will try again tomorrow night.

Sorry no builds in the meantime. If this takes more than like 4 or so days I'll setup a repo with old bionic for builds.

Sent from my Nexus 4
[Nexus 4 Android Development] DesertVelo:
Not a problem....! Thank you for taking the time to do the build and making our devices that much better.

Sent from the singletrack....
[Nexus 4 Android Development] elliot.newnham:
So is there a difference between Google code and cm10.1 code that is going wrong? Or is it Google that is pushing improvements that your trying to incorporate into cm10.1
[Nexus 4 Android Development] trailblazerz11:
The Google bionic is actively developed while the CM bionic is pretty much a fork made awhile ago with some Cherry pick updates. They differ quite a bit now.

The issue is that the Google bionic relies on updates to dalvik and libcore (which CM updates every Google release) and it causes incompatibilities everywhere

Sent from my Nexus 4
[Nexus 4 Android Development] tackleberry_crash:
I did successfully build with Linaro last night after fiddling with it whole day.

I have realized local_manifest would be easier then the script, you know which did not pull some stuff last time I used it last

I have forked your repos to my github account and created a local_manifest to remote sync the linaro changes from my github.

Framework_base gave me lots of trouble since you haven't merged the new commited stuff yet but I also pulled them from CyanogenMod's repo.

I did make a tutorial early morning on how to easily build with Linaro. I have to incorporate the last derp in the frameworks_base until you merge your fork with new commits on CM's framework_base repo.

I'll post it when I get home from work today.
[Nexus 4 Android Development] paulpoco:
I am getting multiple text messages, first noticed it on the March 22 build. I was getting the same text from my wife over and over. The multiple texts all have same sent time but different received time. I am going to try going back to March 21.

---------- Post added at 10:06 AM ---------- Previous post was at 09:25 AM ----------

Ok still doing it with March 21, only other thing different is Banks Gapps March 20. Will go back to pure Google Gapps and see if that was it
[Nexus 4 Android Development] elliot.newnham:
Sounds like a service provider issue
[Nexus 4 Android Development] tackleberry_crash:
Never had that kind of thing on this rom or let alone on any cm since version 6

Probably a service provides related problem

Have you tried any other roms?
[Nexus 4 Android Development] paulpoco:
I haven't tried another ROM yet. Only started a few days ago.

I guess I'll have to call service provider.

Get multiple copies would be the messaging app not send or marking text message has been received?

I may also have to try a full wipe.
[Nexus 4 Android Development] tackleberry_crash:
Try a clean flash first. Do a nandroid back and flash away. Probably formatting everything except sdcard is an option too besides data wipe/factory reset.

Probably full wipe and clean flash may solve your problems.
[Nexus 4 Android Development] trailblazerz11:
That would be great if you could release for the time being :)

Moving to Google's is much harder than I had expected and currently have family visiting along with school, found I cannot cannot dedicate much time lately. Should clear up next week.
[Nexus 4 Android Development] tackleberry_crash:
Nightlies Continue

Not sure where you want to put the builds.

I am gonna update this post with each nightly I upload. Newest one will be on the top.

DEV-HOST

Newest Build

cm-10.1-20130330-TackleBerry_Crash-LINAROBEAN-mako.zip - 187.13 MB ----- Md5 : 2d9754dada85f09d81b74c0555693550

Old Builds

cm-10.1-20130329-UNOFFICIAL-mako.zip - build 2 - 187.13 MB ----- Md5 : e176cf3d5c351c4cae3a7ed02e4a910e

cm-10.1-20130329-UNOFFICIAL-mako.zip - 187.13 MB ----- Md5 : 6185e069e7d1e3871820a6011e3aad38

cm-10.1-20130328-UNOFFICIAL-mako.zip - 187.13 MB ----- Md5 : 8e128fc63f36131433be5eb5e55183fe

cm-10.1-20130327-UNOFFICIAL-mako.zip - 187.11 MB ----- Md5 : 00353db7affaa252b26414993ec1da23

cm-10.1-20130326-UNOFFICIAL-mako.zip - 187.11 MB ----- Md5 : 5b274bf1c8e3b00b852597a00c3503ce

cm-10.1-20130325-UNOFFICIAL-mako.zip - 187.09 MB ----- Md5 : f8b35a1e0b9282fe4ff0a2dc0bfcff32

My own mirror
[Nexus 4 Android Development] eRajesh:
CM10.1 next nightly will include basic Pie controls. Did you sync those changes? If not, can you please comeuupwith a new build? Pretty please?
[Nexus 4 Android Development] tackleberry_crash:
hmm this build is from yesterday morning's sync. I sync last night but saw nothing new so I did not build it.

I'll sync and build tonight.

Edit: Yepp, here it is, they merged a bit after I synced :) ;

PIE Controls Come to CyanogenMod 10.1

https://plus.google.com/+CyanogenMod/posts
[Nexus 4 Android Development] <remote>:
Thanks tackleberry_crash for you excellent linaro guide and also trailblazerz11 for his original guide / work.

Changed my CM builds over to linaro took about 10 minutes thanks to your excellent guides and repo source

I hope you guys don't mind I have uploaded the latest trailblazerz11 linaro sync with CM with the pie-controls updated to my box account cm repo sync'd about 1- 2 hours ago been busy so can't remember but I have booted up fine on my n4 with matrix 8 kernel and the pie controls are there with the latest commits on the cm gerrit. I didn't test out pie as tbh I moved off the "other roms" because I can't get on with pie I like the stability and features in CM :) .

https://www.box.com/s/7tkqfbp8oy9sghr45dzk ROM

https://www.box.com/s/7tkqfbp8oy9sghr45dzk MD5 for rom
[Nexus 4 Android Development] jc monkeyballs:
I'm downloading your build now. I'll run a quick backup and install it as soon as it's finished. Thanks!
[Nexus 4 Android Development] AcmE85:
Thanks <remote>.

The build works flawless! :good:
[Nexus 4 Android Development] <remote>:
No problem this is really trailblazerz11,tackleberry_crash and CM's work

Just a guide in case some of you can't get to pie I don't like it but tried it out :)

Go Settings - System

Under battery light is Pie controls ( you can turn on pie controls / show search and trigger position)

Navigate back to System then select Power menu ( choose expanded desktop and whether you want statusbar disabled /visible hidden)

To active pie you need to go to expanded desktop ( to do this with phone unlocked hold power key and select Expanded desktop)

Then pie controls should be active......
[Nexus 4 Android Development] stab244:
Just out of curiosity, I noticed that if you activate PIE controls and hold this other layer pops up that has circles on the top, left, and right borders of the screen. Did CM team say if they were doing anything with those?
[Nexus 4 Android Development] <remote>:
I think it is wip I am sure there will be newer pie commits / patches on the cm gerrit which will appear in later linaro cm builds
[Nexus 4 Android Development] nerdBrain:
Anyone else seeing fc's with the camera/gallery apk in 3/22?
[Nexus 4 Android Development] tackleberry_crash:
Haven't had that problem either, Clear cache and data for gallery app. It may fix it

New build is coming in couple.
[Nexus 4 Android Development] tackleberry_crash:
New Build is UP

http://xdaforums.com/showpost.php?p=39577980&postcount=625
[Nexus 4 Android Development] dougiefresh36:
Can you say what's the difference between trailblazers builds and yours? Thanks for all your work!

Thanks in advance.
[Nexus 4 Android Development] tackleberry_crash:
Nothing at all.

I am just keeping up with the builds while he is busy with some other things in life and google's bionic merge
[Nexus 4 Android Development] tackleberry_crash:
Used PIE for half an hour or so with the New build and could not get used to it. I remember using it when I flashed PA looked at it for 10 minutes :)

I felt like it showed me down.
[Nexus 4 Android Development] stab244:
Same for me. Not to mention that the home button isn't centered when the search button is turned on. Also no easy way to get to Google now that I could see. I would probably only use for playing games in expanded mode.
[Nexus 4 Android Development] thracemerin:
The search button gets you to Google Now.
[Nexus 4 Android Development] shmizan:
was it useful on PA? I see a lot of people praising this PIE feature but I can't understand if it makes life easier or harder.

I mean, after PIE, going to homescreen will require 2 actions instead of 1
[Nexus 4 Android Development] Komodo Rogue:
IMHO:

PIE is generally worse than the stock set-up, although some are probably almost as quick with pie as the standard nav bar.

However, for me, PIE isn't about having a superior setup, it's about having a navigation method that works fairly well when I want to use the expanded desktop - which is fairly rare, but it's really nice when you want to use it.
[Nexus 4 Android Development] shmizan:
thanks for your input.

it's all about the extended desktop. now the real question is will it be able to automate it to only use PIE when the extended desktop is in use

that's up to CM devs though
[Nexus 4 Android Development] thracemerin:
On CM the PIE only works while you're in extended desktop already.
[Nexus 4 Android Development] shmizan:
oh awesome! should've checked it beofore :cyclops:
[Nexus 4 Android Development] stab244:
Even in apps that have a function for search like Gmail?
[Nexus 4 Android Development] thracemerin:
Oh, perhaps not, I only tried from the homescreen.
[Nexus 4 Android Development] 0.0:
Does anyone experience this with the 3/26 build?

Bug: when the keyboard is open, pressing the nav bar button to bring it down acts like a back button. It won't bring the keyboard down but instead go back. Like for the messaging app, in a new message text field, the keyboard is open but pressing the button to make the keyboard go down makes it go back to the conversation list.

Sent from my Nexus 4
[Nexus 4 Android Development] stab244:
I do. Using swiftkey.
[Nexus 4 Android Development] elliot.newnham:
You really need to use PIE for like a week for it to set in, honestly I hated it for the first day or so, then you start getting really quick at it and it isn't as bad.

Edit: should say love this new build. Thanks for giving it to us!

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

Have the same bug, but that's on cm10.1 side. They have a whole website for bug reports :)
[Nexus 4 Android Development] tackleberry_crash:
Oh, swiftkey auto corrected slowed to showed :)

Yeah, I think it is just for game players that want the bottom bar disappeared.

It just did not make my life easier in the half an hour that I used it.

---------- Post added at 05:34 AM ---------- Previous post was at 05:19 AM ----------

I am not sure when this bug was introduced but not long before.At least, I realized this happening last couple days if not week but couldn't look into.

I use swiftkey but happens on all keyboards that I tried including stock.

I have to look for it.

I'll cherry pick the fixes if some one fixes it and they take their time merging it.
[Nexus 4 Android Development] thracemerin:
Already fixed and merged: http://review.cyanogenmod.org/#/c/34618/
[Nexus 4 Android Development] tackleberry_crash:
Oh, thanks I am compiling now.
[Nexus 4 Android Development] notbrodie:
for the people who like to get rid of the nav bar, but don't like PIE controls, check out GMD gesture controls or LMT launcher. I've been using GMD for a couple months. Once you memorize all the different gestures, it becomes leaps and bounds better than PIE or the stock nav controls
[Nexus 4 Android Development] tackleberry_crash:
New Build is UP :thumbup:

http://xdaforums.com/showpost.php?p=39577980&postcount=625
[Nexus 4 Android Development] eRajesh:
Thanks for the new nightly. D host is acting as a ***** though. Getting 30KB/sec download speed
[Nexus 4 Android Development] tackleberry_crash:
I am gonna open up my own mirror tonight.

Supposed to done yesterday but I did not have time yesterday then I had just enough time compile and post the new build in the morning since I had to catch an early flight for a meeting.
[Nexus 4 Android Development] notbrodie:
I'm going to try my hand at this source building game too. i'll let you know how it works tomorrow

i'm also using this to attempt a linaro-optimized build for my wingray xoom. any input? other than a nandroid?
[Nexus 4 Android Development] dxdiag32:
hi trailblazer :D

can i use your bionic optimistic on my maguro and will it works?
[Nexus 4 Android Development] kszaq:
At the moment this ROM is using vanilla CM's bionic repo, as they've merged all optimizations some time ago. Thus, with latest CM nightlies you're getting the best available for this moment.

Another thing is that some of the optimizations were Krait-only, so you won't notice any difference on Maguro anyway. :(
[Nexus 4 Android Development] dxdiag32:
thank you dude :)
[Nexus 4 Android Development] strra:
is anyone else having Google Now crash when you click "Track Package" on a shipment card? i'm on 10/27 nightly
[Nexus 4 Android Development] karnoff:
That's gonna require me to purchase an item. Can't answer that question sir.
[Nexus 4 Android Development] strra:
hmmm i'm getting the crash on my N7 too (which is on rooted stock).. so maybe Google Now doesn't like Portuguese tracking numbers much...
[Nexus 4 Android Development] tackleberry_crash:
Yeah, that can not be a bug from cm then since your n7 is stock:)

I will post the new build when I get back home tonight.
[Nexus 4 Android Development] trailblazerz11:
Quick update

Everyone thank tackle berry for his hard work and providing builds while I am busy.

Don't have time to fix my local repo that has been eviscerated by trying to work in google bionic. Made far too many hacks

I'll make a fresh repo later when I have time and work on google bionic as a side project (that I don't know if it will work)
[Nexus 4 Android Development] markd0wn:
Sorry if this has been asked/explained many times (thread was created over a month ago), but just to make something clear:

If i download the official CM10.1 builds from get.cm -- are those compiled without linaro/bionic optimizations?

If I understand the 'advantage' of the builds from this thread, it's that they have the linaro/bionic optimizations, so I assume the official builds don't (otherwise there would be no difference between the builds here and the official builds).

If that is the case, why doesn't CM10.1 officially adopt linaro/bionic? is it considered unstable, or what? do they plan on making builds with the optimizations at some point?

Thanks in advance.
[Nexus 4 Android Development] trailblazerz11:
CM bionic is nearly identical with this one now, only a few more minor optimizations I added.

As for Linaro, it may cause some bugs and bad assembly code that are very difficult to debug. I find it stable enough for these builds but CM has to support many many more devices. they will stick with what googles using it seems

Sent from my Nexus 4
[Nexus 4 Android Development] markd0wn:
Thanks for explaining, so I guess the Linaro toolchain thing is the main advantage your builds have over the official CM10.1 mako builds.

Speaking of which, down the line, if/when there's a stable/permanent host for these Linaro builds, and assuming CM10.1 won't natively use Linaro in the near future, it may be a good idea to either remove the CM Updater (which will currently download official builds if trying to use it on these Linaro builds) or edit it so it would update builds with the Linaro zips from whatever site will host them on a regular basis (assuming altering the updater and supplying unofficial CM OTA updates is 'allowed'/acceptable by CM)
[Nexus 4 Android Development] tackleberry_crash:
I was just thinking last night that I should remove or somehow alter CMUpdater to pick up OTA Updates from my mirror in the next build.

Waiting for the weekend though to look into it.

As for CM not using Linaro natively Steve Kondik says that AOSP barely moves to GCC 4.6 and Linaro is on GCC 4.7 and he says it may not be stable enough to support that many devices. Work on out N4's pretty good but CM support current and so many legacy devices.

Google may move to GCC 4.7 in Android 5.0 then CM may move to Linaro but I see it very unlikely though from CM to abandon GCC 4.7 at that point for Linaro GCC 4.7.

---------- Post added at 06:15 AM ---------- Previous post was at 06:06 AM ----------

New build and mirror is UP

http://xdaforums.com/showpost.php?p=39577980&postcount=625
[Nexus 4 Android Development] markd0wn:
Personally, I manually download the update files on my computer (faster speed), paste them to the cmupdater folder, then go to the update menu and update from there -- that's what I did with the official builds (since it auto-reboots to recovery, auto-installs, then goes back to android, so basically it's paste+1 click).

Wonder if that would work for the Linaro builds or if it's filename-based -- saves time going to recovery and manually installing. Looking forward to see your weekend results :)
[Nexus 4 Android Development] AcmE85:
@tackleberry_crash

Your latest build (29) shows as "10.1-20130326-UNOFFICIAL-mako" in about phone,

though recent commits are merged.

E.g. this is inside http://review.cyanogenmod.org/#/c/34686/

No biggie, just wanted to let you know.

Does it show the same for you?
[Nexus 4 Android Development] tackleberry_crash:
Yeah I did see that too last night which means that I did not compile with make clobber since then.

Updates weren't anything that will have affected any make files pretty much all system app and some Settings updates.

It takes up to 40mins to compile with deleting build folder comparing to 10 mins at most for small changed.

I am gonna build with make clobber tonight.

I decided to build with make clobber every build.
[Nexus 4 Android Development] cowst:
Why not GooManager?

No need to paste anything then, and can enqueue kernel as well
[Nexus 4 Android Development] <remote>:
You need a goo developer account which takes a while for goo to approve.....
[Nexus 4 Android Development] tackleberry_crash:
Compiling again with today's updates.

-------

As for OTA updating I am looking into some other options too.

Here is the options I can think of;

Somehow make use of CMUpdater

Remove CMUpdater, use GooManager (I don't like goomanager too much, it is personal plus take a long time for them to approve :) )

Remove CMUpdater and use otaupdate center (I have just found about this site/today)

Remove CMUpdater and use the classic way of flashing.

Any more ideas ?
[Nexus 4 Android Development] kszaq:
Actually AOSP switched to 4.6 with Jellybean and now they merged a switch to 4.7 for the next release. What they don't want to use is high optimization (they stick to O2 for arm and Os for thumb mode while we use O3 for both) and strict aliasing. The former produces a bit faster but bigger machine code. The latter is a bit more complicated: to be able to compile with strict aliasing on, the code must follow strict-aliasing rules and many parts of Android don't. Guys from Linaro published lots of patches to address this but it causes many little-and-very-hard-to-track bugs for some devices. That's why we won't see these patches in CM for some time.
[Nexus 4 Android Development] tackleberry_crash:
Probably stuff I have read a bit outdated about AOSP's toolchain for the next release.

I am seeing so many warnings as it compiles while doing other stuff now it is amazing how many warnings are passing by and as you are saying 90 percent of them looks like coming from the strict aliasing.

I am definitely agreeing you about us not seeing these linaro patches in mainstream CM for some time while they are trying to support so many devices at once not even counting numberless unofficial ports.
[Nexus 4 Android Development] tackleberry_crash:
As promised new build is posted :good:

I did build with 'make clobber' so build info in settings is synced.

http://xdaforums.com/showpost.php?p=39577980&postcount=625
[Nexus 4 Android Development] ol@fson:
Just curious .. I have been using CM since day one of my N4. Is there really any noticeable difference between official CM 10.1 and this ROM?
[Nexus 4 Android Development] tackleberry_crash:
Some people say it's a placebo effect some say it is faster but my opinion is Linaro built cm10.1 is a bit more responsive and snappier than the GCC 4.6 toolchain built cm10.1.

If you are asking comparing roms that ra build with GCC 4.6 toolchain and GCC 4.7 Linaro toolchain speed or benchmarking wise, it is hard to come up with an definitive answer for that in my opinion. I think Linaro builds will be definitely faster in some benchmark but not so fast if not equal in some benchmark.

My antutu benchmark did improve by 2000 or so with linaro build. I was getting 19000'ish w,th stock cm10.1 then I got 21110 with linaro build. (franco kernel). Nowadays I am using motley though...

I am happy with it even if it is a placebo effect :D

I am wondering what others have to say about this.
[Nexus 4 Android Development] tackleberry_crash:
New Build is Up :good:

http://xdaforums.com/showpost.php?p=39577980&postcount=625

---------- Post added 31st March 2013 at 12:10 AM ---------- Previous post was 30th March 2013 at 11:36 PM ----------

I have done some progress on OTA for the rom.

I have successfully notified and downloaded the new build tru OTA on my own N4. Nest step is flashing it :)

Needs a system app to be added in the build and 3 line addition to the build.prop.

I am gonna be compiling a test build with these updates also removing CMUpdater while at it tomorrow.

Procedure works on the dry run but I would like to have one or two of you test it first after changes added to the build itself and before releasing it to all.

Just let me know here, I'll PM you as soon as I got it working tomorrow.
[Nexus 4 Android Development] tackleberry_crash:
I have perfected the OTA update build.

I had some weird issues getting it to work but I just did my last flash with it.

Test build is compiling right now.

I'll have to run some errands now so I'll post the test build out tonight.
[Nexus 4 Android Development] renna1992:
wanted to give you a thanks but that stupid 8 thanks limit.

so this post has to do, thank you tackleberry_crash for all those builds :)
[Nexus 4 Android Development] tackleberry_crash:
Thank you :D

I am gonna upload the new build after we have done at least one test cycle today.

New build is gonna be up tomorrow.