yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Prod1702:
Re: [ROM][KANG] Unofficial Linaro CM 10.1 + Bionic Nightlies

Saw that after I posted but was lazy and didnt want to edit the post. :)
[Nexus 4 Android Development] trailblazerz11:
3/15 nightly out, just a sync.

I'm thinking about building every 2 nights or so, skipping a build if there aren't interesting changes by CM or any additions I find.
[Nexus 4 Android Development] gianton:
Yes that would be enough I think, I'm on 03/11 and will flash today's build now. 03/11 build running rock stable, very smooth and battery friendly with Franco's r102 kernel.

Thanks for your hard work mate and good luck with your exams! :good:
[Nexus 4 Android Development] yukkio:
Thanks for the update but i think i will stay on yesterday nightly, no important changes in this nightly (i think).

BR.
[Nexus 4 Android Development] 75markus:
that makes sense :)

I stopped daily flashing some time ago, it got a lil bit annoying :p

Nexus builds are really stable, 1-2 flashes a week are really enough for me, especially when there are no great new commits
[Nexus 4 Android Development] 0.0:
Re: [ROM][KANG] Unofficial Linaro CM 10.1 + Bionic Nightlies

Has that Google voice bug been fixed?

Sent from my Nexus 4
[Nexus 4 Android Development] gianton:
Google voice working good here.
[Nexus 4 Android Development] darkbasic4:
Can you please test Google+ Hangout with 3g connectivity? I get a network error while with my Galaxy Nexus works flawlessly.
[Nexus 4 Android Development] trailblazerz11:
I believe the issue was with integrating Voicemail and playbacking the voicemails from dialer if I recall correctly. I merged a fix that that I thought fixed it (based on the commit message) Some user reported it still didn't work despite the fix, (I can't test outside of US) but using Official CM libwelhelm.so fixes as before.

:( Unless I stumble upon a true fix I'm clueless, I tried turning down flags earlier too and that didn't fix it either.
[Nexus 4 Android Development] lonelywolf11:
yes,that should be enough, and for me ,weekly is really enough~
[Nexus 4 Android Development] ohliu:
Once a week would do just fine for me. ;)

Even though we're flashholics I'm pretty sure people will understand if you need to focus on your own life.

You've been good to us, man! Thanks for making our phones super duper awesome.
[Nexus 4 Android Development] trailblazerz11:
Btw, I just splurged and upgraded my laptop RAM from 8GB to 16GB (Yes, I know total overkill for anything else ^^ but RAM so cheap nowadays, crazy) My build time dropped from 40 minutes to ~25 minutes and my laptop isn't unusable during build. Very happy.

SSD would be nice but so spendy, I'll wait until my next computer for that, price should be more manageable in 1-2 years hopefully.
[Nexus 4 Android Development] 75markus:
go for a SSD if you can afford it, you will love it :)
[Nexus 4 Android Development] kszaq:
Hello trailblazerz11. Small heads up about the mcpu flag. As you may have already noticed, Linaro has released a new version of their toolchain (2013.03) which - amongst other changes - provides an improved ARM vectorizer cost model (performance improvements, yay!). For this release they used a slightly older version of binutils which causes "DIV usage mismatch" error when compiling with mcpu=cortex-a15. This may be fixed by the patch one of Google's engineers submitted some time ago applied to toolchain. For your convenience, I have pulled Linaro's sources, applied the aforementioned patch and compiled the toolchain. You can download it from here.

Please let me know if it works for you (it has been compiled on i7 machine and might not be compatible with something lacking all its instructions).

For GPL compliance, you can download the sources using Linaro Toolchain Builder and their linaro-android-13.03-release branch plus gcc sources from Launchpad.
[Nexus 4 Android Development] Zainiak:
Re: [ROM][KANG] Unofficial Linaro CM 10.1 + Bionic Nightlies

Is there any way to change navbar height? I just can't use it stock

Please disregard typos.... Sent from my NeXuS 4
[Nexus 4 Android Development] trailblazerz11:
Re: [ROM][KANG] Unofficial Linaro CM 10.1 + Bionic Nightlies

Sorry, wont be able too unless CM adds that feature which I think they said they wont.

Sent from my Nexus 4
[Nexus 4 Android Development] thracemerin:
These two commits are cherry-picked by Euroskank to do it, if you felt like cherry-picking them, not saying you should, but the code is available.

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

http://review.cyanogenmod.org/#/c/29635/
[Nexus 4 Android Development] darkbasic4:
Nobody uses hangout?
[Nexus 4 Android Development] AcmE85:
Navbar height adjustment would be the icing on the cake.

I tried it recently and love it, the downside is that other Roms come with tons

of additional stuff merged, which is changing too much.

It would be great if you would reconsider adding these two commits.
[Nexus 4 Android Development] trailblazerz11:
Re: [ROM][KANG] Unofficial Linaro CM 10.1 + Bionic Nightlies

Hmm. Leaning on adding it. I wanted pure CM but thats the most requested feature. Its not like it affects people that dont use it and if makes some people happy i guess why not?

Probably try tomorrow

Sent from my Nexus 4
[Nexus 4 Android Development] darkbasic4:
What about proid? It is very useful and it doesn't affect peoples who don't use it :)
[Nexus 4 Android Development] fluffenforliberty:
Re: [ROM][KANG] Unofficial Linaro CM 10.1 + Bionic Nightlies

For you guys that want more options why not go with Carbon, PA, Liquid smooth? They are freaking fast because they also got all the optimization buzz word magical thingys ;)
[Nexus 4 Android Development] gianton:
Re: [ROM][KANG] Unofficial Linaro CM 10.1 + Bionic Nightlies

+1 keeping it pure CM with only linaro toolchain and bionic patches is what I like most of this ROM. Euroskank has the navbar options and other ROMs have loads of other options.
[Nexus 4 Android Development] AcmE85:
I am on Euroskank right now for testing. There is no option for navbar height.

Previously tested JellyBeer and it was there.

The thing is, these roms have way to much additions, (PhabletMode, DPI, Pie...)

Btt:

Why shouldn't there be navbar settings, if puting every widget on lockscreen is included?

It's not the case with official cm and I don't use widgets on lockscreen, but It does not bother me.

Good if someone actually profits from this merge.

In the end it all comes down to what trailblazerz11 wants to be in his rom.

I will flash back to his rom as soon as the next build is up no matter what he decides.

I am sorry to have started this off-topic discussion
[Nexus 4 Android Development] trailblazerz11:
After thinking about it for awhile (sorry changed opinions several times), I won't not to merge Nav Bar size edit. The reviews on gerrit explain why it was not merged to CM.

I have decided to reaffirm the goal of this ROM is a CM kang with added Linaro/bionic and other optimizations, no additional features. (I completely forgot about widgets on lockscreen, I may just get rid it later) Personally, I like CM and always end up on it after trying other ROM's. Clean and has the features I need.

Thanks all for the suggestions everyone, appreciated. I would like to make everyone happy but in the end thats not possible but hopefully the majority are. I highly encourage compiling your own ROM with your personal taste if you have the time and interest. (Hopefully my terrible tutorial helps a bit if you want linaro, I am thinking about a way to rework my branches and make it easier though)
[Nexus 4 Android Development] darkbasic4:
+1 for a revised linaro tutorial :good:
[Nexus 4 Android Development] trailblazerz11:
And just when I get started on it, CM github has issues... Can't even repo sync...

My plan is to upload every branch with changes by me, you would get CM repo then could repo start a linaro branch and use a script I would make to automate pulling changes from my github branches. No need to manual apply patches and afterwards just treat like CM repo.

I think it *should* work.. hopefully.
[Nexus 4 Android Development] darkbasic4:
I was wondering... is there any Gentoo user here? It would be awesome having a linaro crossdev toolchain :laugh:
[Nexus 4 Android Development] EvoXOhio:
LOL really? Mine is at least 10 degrees farenheit cooler if not 15. How did you install? I flashed stock .img files from Google and then downloaded the OTA and applied through CWM.

I ask because if you tried a 4.2.2 ROM that may not be a good comparison since the mako device tree isn't in AOSP yet so those ROMs are just hacks.

---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------

I just went out for an hour and my wakelocks showed 20% of msm_hsic_hosts wakelock. But my battery only dropped 2%, which is pretty good. I'm wondering if Google is even going to fix the issue. They've know had 2 releases since the issue was reported and there's been no fix.
[Nexus 4 Android Development] gianton:
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/14 Nightly*

I flashed stock images of 4.2.1 and then the 4.2.2 OTA zip in TWRP.

Also my 3G speed dropped by at least 50%.

Sent from my Nexus 4
[Nexus 4 Android Development] EvoXOhio:
Weird that we have such different results. I haven't tested my data speeds, will do that tonight. You sure you got the new baseband and everything?
[Nexus 4 Android Development] gianton:
Yes all stuff updated, I had about 41c while browsing/reading for an hour. Usually I have 36-38c with this ROM and franco's r72 kernel. Also at the same location my data speed was 5-7mbit/sec download while with this setup I have 10-15mbit/sec. Maybe I'll give it another try in a few days.

Most disappointing thing though, is that Google haven't fixed the BT bug. :(

---------- Post added at 09:17 PM ---------- Previous post was at 08:42 PM ----------

Working great, uninstalled Lux no need for it with new gamma settings.
[Nexus 4 Android Development] swaggerwocky:
Love that backlight curve adjustment, uninstalled Lux here as well. Thanks for these builds, trailblazer!
[Nexus 4 Android Development] 0.0:
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/14 Nightly*

4.2.2 has made it to the mako. I don't think it's available yet though. Still more stuff to do

Source: CyanogenMod Google+ page/account

Sent from my Nexus 4
[Nexus 4 Android Development] rootuser11:
really like this rom. thanks! keep up the good work!
[Nexus 4 Android Development] trailblazerz11:
4.2.2 seems to be out of staging and currently getting merged into the cm-10.1. line.
[Nexus 4 Android Development] gianton:
Thanks for the heads up.
[Nexus 4 Android Development] trailblazerz11:
Just wait for the big boys to finish :)

Be warned though, there might be some conflicts with Linaro and bionic patches along with new code causing errors with Linaro.

Note there's a new bootloader and radio in 4.2.2 factory images, I've flashed them on 4.2.1 with no issue, might be a good idea to if you know how to fastboot.
[Nexus 4 Android Development] gianton:
Already on full 4.2.2, flashed all stock images from JDQ39. Currently testing Carbon 4.2.2 but will switch to yours once updated. :good:
[Nexus 4 Android Development] 0.0:
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/14 Nightly*

Can't wait! As long as there are some bionic and linaro patches, it'll be fine

Sent from my Nexus 4

---------- Post added at 09:45 PM ---------- Previous post was at 09:19 PM ----------

so the bootloader and the radio from the factory image is called:

bootloader-mako-makoz10o & radio-mako-m9615a-cefwmazm-2.0.1700.48

am i correct? also, how do i flash the baseband and baseband in fastboot?
[Nexus 4 Android Development] trailblazerz11:
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/14 Nightly*

fastboot flash bootloader [filename]

Reboot bootloader

fastboot flash radio [filename]

Reboot bootloader

Start
[Nexus 4 Android Development] 0.0:
are the files that i listed the correct file names? dont want to break anything :(
[Nexus 4 Android Development] trailblazerz11:
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/14 Nightly*

Yes, from what I remember. As long as pulled from factory images
[Nexus 4 Android Development] AcmE85:
You can flash modem and bootloader with this zip through twrp or cwm.

http://xdaforums.com/showthread.php?t=2147194

Just flashed it without a problem, wifi still works (I am on motley kernel b35).

Patiently waiting for your build :fingers-crossed:
[Nexus 4 Android Development] trailblazerz11:
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/14 Nightly*

Merge went OK. Only a couple conflicts.

Not at my laptop right now but when I get back I'll track down the proprietary files and try to build.
[Nexus 4 Android Development] 75markus:
cool :good:
[Nexus 4 Android Development] tibere86:
Yummy. Can't wait. :good:
[Nexus 4 Android Development] xploder270:
Is there already a proprietary vendor git I can use to build mr1.1-staging?

TheMuppets seems to have the old files.
[Nexus 4 Android Development] trailblazerz11:
Spent a couple hours redoing my overall process then uploading all changed branches to github (linaro branch), but this should automate everything for those that want to compile themselves.

The tutorial has been updated, I am tired and sleepy now, please see if it works I haven't actually tested on a New CM repo so there might be some derps on my part (actually quite likely zzzzzzz)
[Nexus 4 Android Development] darkbasic4:
Thanks but I can't test it right now, I just made a new desktop pc and I'm waiting for the Voyager GT Turbo USB 3.0 128GB to set up my new linux box. My laptop doesn't have enough power nor free space to compile it :laugh:
[Nexus 4 Android Development] milesmarrero:
Hey, I understand your decision not to incorporate navbar height, but do you know if it's possible for me to just remove it? I like just using the status bar and lmt launcher... can I just like crash the navbar and get it out of my way, or do I have to compile that change myself or? Im a noob so give me a break haaha
[Nexus 4 Android Development] dannyyung:
Re: [ROM][KANG] Unofficial Linaro CM 10.1 + Bionic Nightlies

If you like to disable the navigation bar, go setting, system, power menu, and disable the nav bar only. Then press power button to extend the desktop.
[Nexus 4 Android Development] trailblazerz11:
Later than usual but compiling 3/18 nightly now. Seems to be an issue with new mako kernel git branch not syncing automatically.

Testing the new branches, hopefully will work out any derps

EDIT: Fixed mako kernel git and libcore and some derps with linarize script. Should be good now.
[Nexus 4 Android Development] yukkio:
Hi, I've problems syncing some google features like calendar o browser. Using 3/17 version, anyone?

Thanks.

BR.

Edit: problem fixed in 3/18
[Nexus 4 Android Development] hoseth0711:
Sv: [ROM] Unofficial Linaro CM 10.1 + Bionic Nightlies *Tutorial, Compile Yourself!!

@trailblazerz11 What linux distro do you use?

Sendt fra min Nexus 4 med Tapatalk2
[Nexus 4 Android Development] cobhc:
Does this include any of the above from kszaq?
[Nexus 4 Android Development] karnoff:
I saw it either mentioned by him or in the OP, but its Ubuntu 12.10
[Nexus 4 Android Development] kszaq:
Yes, it does. :)
[Nexus 4 Android Development] stocovick:
I've been getting an error regarding busybox and trickstermod on the latest nightly. It says I don't have the correct version installed.
[Nexus 4 Android Development] karnoff:
Anyone else's lightflow crashing on startup after 3.18 flash?
[Nexus 4 Android Development] <remote>:
I had this problem on this build.Just ran my own build 1hour ago and problem gone in nightly cm standard. I reflashed busy box earlier when I had the issue and trickster worked ok
[Nexus 4 Android Development] stab244:
I have this issue too with the new gmail update. Only started after I updated. Weird.
[Nexus 4 Android Development] karnoff:
looks like they just updated it (light flow), fixed the crashing for me.
[Nexus 4 Android Development] stab244:
Yeah I just saw and was about to post that lol. Thanks anyways.
[Nexus 4 Android Development] kszaq:
Hello everybody.

Another heads-up regarding mcpu flag: thanks to this commit, we no longer need TARGET_CPU_VARIANT := cortex-a15 in mako's BoardConfig.mk. :)

I can see that Google engineers are unifying those flags in AOSP and we'll have to eventually switch to TARGET_CPU_VARIANT, but as long as CM uses TARGET_ARCH_CPU_VARIANT I think we should stick to it.
[Nexus 4 Android Development] Smallsmx3:
Wondering how much if at all these patches are added to the kernel?
[Nexus 4 Android Development] Komodo Rogue:
I'm kinda talking out of my ass, but I don't think the bionic patches have been added, I think CM is working on bigger issues. I think they (CM) apply CPU optimization patches like the one for Cortex a15, and could, presumably, do the same for bionic, unless it would be some kind of copyright violation to qualcomm? Or are the bionic patches proprietary binaries? I don't believe I ever remember reading anything bionic related in the CM changelogs, although qualcomm is referenced now and then (but that could be about something completely unrelated).

Sorry for the idiot question - I love tech, but my technical understanding is painfully small - but one thing I don't understand: why doesn't CM us Linaro? AFAICT, Linaro could be aplied to any CM 10.1 based rom, and the benefits of Linaro optimizations are universally acknowledged, even if the extent of their benefit may be in question. Would this create too many headaches or something with development and/or fixing bugs? Does this ROM remove a toolchain used by CM when compiled?

On a completely unrelated point, I don't know why this ROM isn't way more popular. Almost everyone wants a stock-ish device that's largely compatible with everything else and good for a daily driver, but with some extra flare (CM) and speed designed to take advantage of the hardware (bionic/linaro)... Keep up the good work OP, I won't have time to learn to compile until the summer!
[Nexus 4 Android Development] thracemerin:
The majority of the bionic patches are in stock CM.

As for the linaro optimizations, CM builds for multiple platforms and multiple chips using multiple architectures, the main benefit of linaro is the ability to use the -O3 flag, many CM devices will not build with this flag even some fairly recent devices, and given that the actual benefit is in question depending on whose benchmarks you believe, it's not worth adding the additional work to add optimizations for some devices and not others given that it would require different modifications for new features, etc...
[Nexus 4 Android Development] bakedpatato:
Thanks for the explanation.

So when someone compiles a rom with the gcc toolchain with linaro optimizations, they're optimizing more than just the kernel(or otherwise trailblazerz would be releasing a kernel).What parts of android are being optimized(ie:what parts of android are c/c++)? Does linaro have an improved version of gcj for all the java files in Android(which according to AOSP is a lot of the project)?
[Nexus 4 Android Development] thracemerin:
Well, one major difference is that Linaro toolchains are based on GCC 4.7, where Google toolchains for AOSP are based on GCC 4.6. There are other tweaks and optimizations involved in the Linaro toolchains vs standard GCC 4.7, but I'm not well versed in the exact differences and I don't want to give you bad information.
[Nexus 4 Android Development] trailblazerz11:
Correct me if I am wrong but the following is my understanding

Without being specific and exact, basically the parts of android that are C/C++ is the low-level layers, Native. Mostly the Library files (.so), also some hardware services, obviously linux kernel. For instance Bionic includes Androids C , C++ library (which is why optimizations here may optimize much of the lower level.) Linaro is optimizing these specifically for ARM SoC's.

I think something like half of the files compiled during build are Java which won't be affected by Linaro (and unfortunately ccache >_<)

About C/C++ and Java, you need to understand their differences. Code compiled in C/C++ outputs binary instructions that are architecture dependent (you see arm, x86, mips gcc compilers in aosp) This is where Linaro comes in optimizing the binary code for ARM architecture. (And also fixing errors so O3 optimization can be used)

Java on the other hand outputs architecture independent code during compilation. When executed the code is run through Java Virtual Machine, or Dalvik in Androids case which is translated by the Just-in-Time compiler for the specific architecture. So no optimizations like Linaro does can be made by the Java compiler during ROM compilation.

Luckily been doing some research on it lately, probably the most useful resource was the new book from Karim Yaghmour

Embedded Android

Great read if you have interest in the topic.
[Nexus 4 Android Development] biggiephat:
Don't wanna be a jerk but if I download your script for linaro would I be able to change the bottom line repo out for any ROM repo I want? I build for three devices.
[Nexus 4 Android Development] trailblazerz11:
Sorry, asking if you can use script for another ROM from source right? (Not a jerk at all)

The script doesn't actually apply patches it pulls from my git projects forked from CM so anything not CM probably isn't going to merge cleanly.

Sent from my Nexus 4
[Nexus 4 Android Development] bakedpatato:
Ok so all the NDK libs, makes sense.

What I was talking about for java improvement is little micro improvements that javac and gcj have implemented to emitted bytecode.

Ex: make an apk with a for and foreach loop iterating over a generic array of type <String>. Last time I did this(during the froyo era) the smali bytecode emitted for the for and foreach are slightly different with a slight performance edge towards the foreach loop. And while dalvik uses a lot of NEON and vfp, no one knows if dalvik's JIT uses ThumbEE.

Seeing that linaro is building exclusively for newer arm CPUs, there's probably room for improvement on that end(but as to how much work they can do without breaking compatibility is probably a huge question,there's probably a reason why they haven't touched java).

All this micro optimization really interests me because as a .net developer, the community is big on that(The head architect of C#, Anders Hejlsberg is huge on making C# as fast as he can)

I really have to finish Embedded Android, I got it for Christmas and I've been too busy to finish it!

(PS:you live in HK? I lived there for a week at at buddy's flat. Man, the crowding gets to you!)
[Nexus 4 Android Development] trailblazerz11:
You probably know more than I do on the matter. I haven't even thought of optimizations for Java, my thought was leave it to Oracle and Dalvik ^^

Yes, I am in Hong Kong for a year. Yes crowding and pollution are quite annoying,,
[Nexus 4 Android Development] yukkio:
Downloading 3/21 thanks!
[Nexus 4 Android Development] sandy-achar:
Damn i just downloaded the 3/11 build ! Anyway the rom is blazing fast :D thanks , also was volume rocker wake removed by you ?

EDIT: Sorry it was stupid of me to download by seeing the change log. and my question still persists.
[Nexus 4 Android Development] stab244:
Good news though is that newest nightly has it back. :D
[Nexus 4 Android Development] trailblazerz11:
:-[ FYI for anyone trying the tutorial. Frameworks/base doesn't rebase cleanly on a repo sync, something with a location service file. Need to manually git pull for now.

Also I will be attempting to switch to Google / code aurora bionic. Actively developed and has optimizations specific to krait. Unfortunately been busy lately but hopefully will have a build working with these bionic changes soon.