yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] karnoff:
The 27th build? No voice shutter on it.
[Nexus 4 Android Development] trailblazerz11:
Used it a couple time today. Works quite well. Make sure using CM camera not the gapps one.

Sent from my Nexus 4
[Nexus 4 Android Development] karnoff:
Did a dirty flash over previous nightly like I usually do and didn't flash gapps. Have I been using the gapps camera this whole time? No option anywhere
[Nexus 4 Android Development] 75markus:
you can get the CM cam from [ROM][4.2.2] CyanogenMod 10.1 Nightlies DISCUSSION,TALK, Q&A thread
[Nexus 4 Android Development] markd0wn:
Found another FC which happens on 0427 but doesn't happen on TackleBerry_Crash's 0427 build. Not sure if it happens on official builds.

Reproduce by going to Settings -> Lock screen -> Slider shortcuts, then choose any of the default shortcuts, change the shortcut to 'Empty', and tap the 'save' icon at the bottom right. This results in a FC for me (FC could possibly happen just by tapping 'save' without changing anything, didn't check).

Also, this is probably not related to the issue, but thought it might be worth mentioning: TackleBerry_Crash's build shows build number of JDQ39 in 'about', while I'm almost positive (can't confirm right now) that trailblazerz11's build, and/or the official build, has the updated JDQ39E build (AOSP merge).
[Nexus 4 Android Development] gianton:
No such FC here running 04/27 build.
[Nexus 4 Android Development] tackleberry_crash:
Please post a logcat of the crash that may help a lot.
[Nexus 4 Android Development] markd0wn:
Just did a clean install of 04-28 and attempted logcat, but looks like the problem resolved itself - not happening on 0428 so it's all good..
[Nexus 4 Android Development] darkbasic4:
It seems the solution to every problem is *trying* to make a logcat: while I was doing mine the clock issue suddenly disappeared without any reason :laugh:
[Nexus 4 Android Development] sir*mez:
4-29 does not boot up. Black screen.

Edit: Reverted back to 4-28.
[Nexus 4 Android Development] trailblazerz11:
Thanks, I found the error... compiling again now. Sorry about that
[Nexus 4 Android Development] trailblazerz11:
Uploading now. Turned into 4-30 since just past midnight HK.

CM moved their build time to around now anyways, though kind of annoying since my builds may appear as a day earlier.
[Nexus 4 Android Development] tarroyo:
good looks!
[Nexus 4 Android Development] DesertVelo:
[MENTION=3908838]trailblazerz11[/MENTION] Thank you for keeping up on the builds, I appreciate your work!

Sent from the singletrack...
[Nexus 4 Android Development] gianton:
Flashed 05-01 build, running very smooth with m+ b2 kernel. Thanks for your hard work trailblazerz11!
[Nexus 4 Android Development] barome:
Yes, as I done, I keep this for my base ! Thanks
[Nexus 4 Android Development] louyaorong:
I noticed obvious battery drain since some recent builds, maybe from 04.29 or so. The Android OS and Android system consume a lot in the battery info. Don't know why.
[Nexus 4 Android Development] barome:
Change kernel :) Franco or Motley or Matrix work fine
[Nexus 4 Android Development] louyaorong:
I have tried Franco, but no improvement.
[Nexus 4 Android Development] trailblazerz11:
Odd, my battery life has gotten better since 4-29 since they reverted the new wifi driver, It gave me like an 1-2 hours of suspend_backoff wakelock.
[Nexus 4 Android Development] louyaorong:
I really can't understand why Android OS consume so much battery now. I remember that it was a bug in 4.2.0 or 4.2.1 when nexus 4 was launched and it has been solved in 4.2.2. But I don't know why it occurred again on my phone since recent CM nightlies. I will do a clean install today and see what will happen.
[Nexus 4 Android Development] trailblazerz11:
What's your deadlocks?

Sent from my Nexus 4
[Nexus 4 Android Development] louyaorong:
How can I check what is deadlocks?
[Nexus 4 Android Development] trailblazerz11:
Crap Swype autocorrect, wakelocks. Better battery stats

Also, I'll start a build as soon as github gets their crap together..

Sent from my Nexus 4
[Nexus 4 Android Development] louyaorong:
Have done a clean install, I will see what happen later.
[Nexus 4 Android Development] trailblazerz11:
Any issues with 5-8 nightly, it was like .10 mb smaller and I didn't really see anything glancing at logs. Probably nothing, just paranoid.

Also I had to revert the terminfo change to libncurses since I was getting build errors, probably for using Arch Linux.

EDIT: Absolutely nothing, just a couple ringtones that were removed and I didn't see the review http://review.cyanogenmod.org/#/c/37063/
[Nexus 4 Android Development] markd0wn:
Flashed it about an hour ago, everything seems good so far, didn't notice any problems, will let you know if something weird happens..

EDIT: Replied before your edit.. ringtones would explain it.
[Nexus 4 Android Development] markd0wn:
Official RC1 (cm-10.1.0-RC1-mako) is out -- looking forward to linaro RC1 :)

(Looks like the nightly that would have been compiled as 05-08 on the official build is actually RC1, so it's possible that linaro 05-08 is already sort-of RC1, unless a few commits were added due to build-time differences)
[Nexus 4 Android Development] cowst:
Hi trailblazerz.

Did you do anything particular to fix the cm HDMI bug that leaves the phone screen off while connected to TV?

On your rom it works, while for example on tackleberry not, although I thought he just customized this a bit.
[Nexus 4 Android Development] trailblazerz11:
I did nothing special for hdmi, perhaps CM fixed it.

Sent from my Nexus 4
[Nexus 4 Android Development] trailblazerz11:
I missed a couple commits in 5-8 building earlier but since they didn't seem to add anything else I'll compile now as RC1
[Nexus 4 Android Development] trailblazerz11:
RC1 is in the M folder, should be same commits as CM's official.
[Nexus 4 Android Development] DesertVelo:
[MENTION=3908838]trailblazerz11[/MENTION] - initial flash of RC1 is not booting (dark screen bootloop). I will download again and try a reflash.

Edit: Second download and flash - same bootloop as before. Trailblazerz11, please take a look when you have the chance.
[Nexus 4 Android Development] xploder270:
It lives! :good:
[Nexus 4 Android Development] 75markus:
FYI, everything is fine with old baseband & harsh, too :)
[Nexus 4 Android Development] gianton:
Can you please share your full list of settings?

BTW, flashed Feb 15 rel, running it with Franco's r80. All working great with JDQ39 bootloader and radio.
[Nexus 4 Android Development] trailblazerz11:
Just bumped everything up about 5%

I use these gamma settings http://xdaforums.com/showpost.php?p=37917796&postcount=12471
[Nexus 4 Android Development] gianton:
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/15 Nightly 4.2.2*

Thanks, I'm using the same gamma settings too.

Sent from my Nexus 4
[Nexus 4 Android Development] 75markus:
thanks for your reports, i just upgraded to new bootloader & radio, too.

everything is fine with harsh kernel :)
[Nexus 4 Android Development] xploder270:
TheMuppets git was updated with the new blobs, including an updated 4.2.2 mako-vendor-blobs.mk!

https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-10.1/mako
[Nexus 4 Android Development] Papadon:
Xposed App Settings DPI

Hi all,

Has anyone been able to get Xposed Framework with Appsettings installed on these builds successfully? It just freezes at bootup for me and I really like these builds but rely on having different DPIs for my apps! Any tips are appreciated!

Thanks
[Nexus 4 Android Development] DesertVelo:
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/15 Nightly 4.2.2*

Just checking with everyone... is the pattern lock working for you? When I try to select a pattern matrix (3x3, 4x4), the selection just loops - continues to ask for the matrix. Latest 4.2.2 build Feb 15. Please let me know which gapps version you are using. Thanks.

Sent from the singletrack....
[Nexus 4 Android Development] xploder270:
I experience a lot of wakelocks with both Franco r80 and cm kernel and the device won't go to deep sleep.
[Nexus 4 Android Development] soundwave123:
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/15 Nightly 4.2.2*

Did you clear cache before flashing the latest build?
[Nexus 4 Android Development] xploder270:
Yeah I even wiped system but not /data.
[Nexus 4 Android Development] stocovick:
Can I flash the old gapps?? Is there a new one??
[Nexus 4 Android Development] xploder270:
Banks has updated his gapps package http://xdaforums.com/showthread.php?t=2012857
[Nexus 4 Android Development] stocovick:
Thank you!
[Nexus 4 Android Development] 0.0:
a lot more bionic commits have been added :good:
[Nexus 4 Android Development] gianton:
Running Franco's r80 too, but no wakelocks. Did you check any of your apps keeping the phone to deep sleep?
[Nexus 4 Android Development] xploder270:
Nah, but I guess it was indeed a rogue app that caused it.

Now I'm on my own built cm10.1 with cm kernel and no wakelocks.

msm_wakelock reduction is pretty impressive with cm kernel... I guess google kanged a lot of xda's kernel developers work ;)
[Nexus 4 Android Development] davwman:
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/15 Nightly 4.2.2*

This linaro chain stuff is intriguing. Any benefit to running this over stock rooted debloated with Franco 80? Yes I know its cm10 with the usual tweaks and options. But stock with Franco is crazy smooth and fast already

Sent from my Nexus 4
[Nexus 4 Android Development] trailblazerz11:
Re: [ROM][CM10.1][KANG] Linaro CM 10.1 + Bionic *2/15 Nightly 4.2.2*

Yes, reduced wake lock makes battery life much better off WiFi now, quite satisfied.

Long list of commits Google kanged straight from codeaurora
[Nexus 4 Android Development] trailblazerz11:
Looking into it. Sorry should have tested but I just flashed last nights

EDIT just a stupid error by me fixing some conflicts, pulled the builds. Compiling again now

Sent from my Nexus 4
[Nexus 4 Android Development] DesertVelo:
Thanks... flashed May 8th build for now. I will flash when you have the build up and let you know if I run into any issues. I appreciate the quick response!
[Nexus 4 Android Development] cowst:
I doubt it's that, because I tried tackleberry after several days with this rom, so it must have had a newer cm.

It could be either linaro 4.7 breaking it or some extra cherry pick you have fixing it.
[Nexus 4 Android Development] sir*mez:
New RC1 works. TY!
[Nexus 4 Android Development] trailblazerz11:
Saw RC2 tags when syncing but I'll compile a nightly anyways today
[Nexus 4 Android Development] tarroyo:
RC2 started rolling out to devices earlier today.
[Nexus 4 Android Development] trailblazerz11:
Was planning on compiling again for RC2 but by the time I came home github was having issues so it looks like I'll just be skipping RC2. Too lazy to deal with tags, busy with studying for finals (not really, actually got distracted by linux 3.10 release :p)

I always found official CM stable on nexus devices anyways. I'm testing an addition of another compiler flag now, hopefully github will let me sync soon before I go to sleep
[Nexus 4 Android Development] tibere86:
I just installed 3.10 on my laptop...it's noticeably faster than 3.9.
[Nexus 4 Android Development] sandy-achar:
Can something like delta updates be made for this ? like cyan delta ? I have a really slow internet connection :/
[Nexus 4 Android Development] trailblazerz11:
Always hard for me to notice any change in performance on my laptop. Playing around with dynticks now though.

Probably not, I'll take a look though.

Sent from my Nexus 4
[Nexus 4 Android Development] trailblazerz11:
Not sure, I have no issues with Phone, perhaps a clean install will fix.
[Nexus 4 Android Development] trailblazerz11:
5-13 is uploading, Compiled it last night with a new flag -mvectorize-with-neon-quad and tested working fine.
[Nexus 4 Android Development] DesertVelo:
[MENTION=3908838]trailblazerz11[/MENTION] thanks for the update! Are planning a N7 build?

Sent from the singletrack...
[Nexus 4 Android Development] trailblazerz11:
Yeah uploaded it too, had some build issues before

Sent from my Nexus 4
[Nexus 4 Android Development] cowst:
What is it supposed to do?
[Nexus 4 Android Development] trailblazerz11:
From ARM:

"GCC 4.4 does not support vectorization with varying vector sizes. By default, it vectorizes for doubleword registers only. You can instruct gcc to vectorize for quadword registers instead by specifying -mvectorize-with-neon-quad on the command line."
[Nexus 4 Android Development] JmPTaz09:
Nice rom! Flashed today's version on a clean install; blazing fast! Using it with semaphore kernel. :beer:
[Nexus 4 Android Development] trailblazerz11:
Some issues with mako building, will check on it again in a bit.

Watched all of Google I/O, surprised 4.3 wasn't announced but still some good stuff. Worth staying up til 4am night before an exam :D

Sent from my Nexus 4
[Nexus 4 Android Development] trailblazerz11:
Not sure what caused the make error, something with intermediates but recompile was fine. Tested and running for half an hour for extra measure
[Nexus 4 Android Development] cowst:
Any idea why in latest releases (since may) most of the times I unplug HDMI I get a reboot?
[Nexus 4 Android Development] trailblazerz11:
I don't even have a cable to test :( Haven't been able to follow up on this issue.

What kernel are you using? If it's a hard reboot - perhaps issue with kernel.
[Nexus 4 Android Development] cowst:
Matrix 8.5.

I think I was using it successfully until mid April.

Then beginning of may I tried tackleberry rom, which had a known CM bug showing either phone OR TV screen.

So I went back to your latest rom (May releases) and since then I am having this problem, also with RC release. But this rom doesn't have the CM bug :)
[Nexus 4 Android Development] ata1918:
A CM maintainer fixed this ROM issue which caused slimport problems since the M2 release of CM10.1. It works with some kernels and ROMs and doesn't with others. So far this ROM,the official CM and AOKP worked perfectly with a proper kernel. As far I know a lot of ROMs don't support it.

NB: Faux's newer kernels should work and so far all franco's have worked for me. Or just stick with stock CM/AOKP kernel.
[Nexus 4 Android Development] cowst:
But then why this rom with the same matrix 8.5 kernel worked perfectly until mid April and not after I tried tackleberry and came back to a newer release? :)

To be precise, the CM bug is not there, but it reboots the OS when I unplug HDMI.
[Nexus 4 Android Development] ata1918:
Hmm perhaps you couls try to grab a log cat and post on this thread and on the matrix thread?

Cheers
[Nexus 4 Android Development] trailblazerz11:
last_kmsg for kernel hard reboot.

Sent from my Nexus 4
[Nexus 4 Android Development] cowst:
I'll try next time it happens
[Nexus 4 Android Development] trailblazerz11:
5-18 uploading, added libm: optimistic pow calling from kszaqs git. Built a bit earlier than official CM
[Nexus 4 Android Development] danmerezeanu:
Downloading now...
[Nexus 4 Android Development] stab244:
Using the 5/18 build with faux 14m kernel. For some reason, any game that is in landscape mode doesn't work. My Temple Run works fine but not Angry Birds. All games worked on the 5/11 build. Is this just me?

Edit: Used Goggles to see if it was just a landscape thing but Goggles worked fine. Restored Angry Birds from titanium and it still didn't work. Weird...

Edit2: It seems to happen only when expanded desktop is enabled. But my Plants vs Zombies worked... And so did temple run even though I play that in expanded desktop too. Maybe something related to the new PIE commits?
[Nexus 4 Android Development] dougiefresh36:
Anyone having trouble with pie?
[Nexus 4 Android Development] trailblazerz11:
Probably the new pie commits. Wait for CM fix I guess. I use LMT anyways

Sent from my Nexus 4
[Nexus 4 Android Development] dougiefresh36:
Reboot fixed it. Thanks though.
[Nexus 4 Android Development] notbrodie:
a search didn't pull up anything so: any plans to attempt a build sabermod's 4.9 toolchain?
[Nexus 4 Android Development] Audioboxer:
Good question, sabermod ROMs definitely fly, but so does this one. If it will somehow make it even faster hopefully [MENTION=3908838]trailblazerz11[/MENTION] can have a look into it.
[Nexus 4 Android Development] trailblazerz11:
In the middle of finals, but I'll give it a go after. Linaro is moving to 4.8 now anyways 4.7 just maintenaince.
[Nexus 4 Android Development] cowst:
I hope this helps.
[Nexus 4 Android Development] trailblazerz11:
Last nightly has new bionic cherry-pick libm: sqrt and sqrtf via ARM vsqrt instruction, from kszaqs github. Thank him, I havent had the time to look through bionic stuff
[Nexus 4 Android Development] markd0wn:
You're referring to yesterday's (05-23) or the yet-to-appear 05-24?
[Nexus 4 Android Development] trailblazerz11:
Yesterdays, giving laptop a break today :D

Sent from my Nexus 4
[Nexus 4 Android Development] Carlos_Manuel:
Hi trailblazerz11! :)

If I use your cherrypick.sh file to cherry pick the stuff for building it with Linaro 4.7 then does it also work with Google's Toolchain 4.7 and does it also fix the warnings?

Thanks! :)
[Nexus 4 Android Development] trailblazerz11:
Most of the patches I use fix errors from using O3 optimizations. I'm not sure about 4.7 I would expect it to work okay. Warnings can usually be ignored, do you get any make errors?

Sent from my Nexus 4
[Nexus 4 Android Development] Carlos_Manuel:
OK :)

I got errors but them wasn't same or similar errors what I've got before...

When I tried to compile CM with Google's toolchain 4.7 and the Linaro patches.. Then I saw only more warnings.
[Nexus 4 Android Development] trailblazerz11:
Yeah the linaro builds will have more warnings but its fine. If you paste me your errors, I'll can try and help. (Headed to bed now though)

Sent from my Nexus 4
[Nexus 4 Android Development] Carlos_Manuel:
OK thanks! :)

I've closed the terminal so I can't paste the errors. But when I tried to build with Linaro I was able to build ROM correctly but for some reason yesterday I got kernel errors which I wasn't able to fix even when I edited the makefile.mk and one other file too to fix building error with gcc 4.7.

Btw. I don't remember the file and repository in your github account.. (Maybe external/display/qcom/*) there was one file which original texts are different than on CM so maybe that file needs updating because on CM's repository it is different... Or then Gedit shows it different than in github... :)
[Nexus 4 Android Development] trailblazerz11:
Goo has been getting hammered lately, Just wanted to check if my server is doing ok, are download speeds ok?
[Nexus 4 Android Development] sir*mez:
Yes it's ok. Actually great!
[Nexus 4 Android Development] jcrabapple:
Will we see the RC3 build today by any chance?
[Nexus 4 Android Development] trailblazerz11:
No sorry, didn't have time to build today. The nightlies should be pretty close though.
[Nexus 4 Android Development] barome:
Yes. Builds every 3 days are enough :)
[Nexus 4 Android Development] tarroyo:
U mean RC4 right?
[Nexus 4 Android Development] jcrabapple:
Well yeah, now.
[Nexus 4 Android Development] trailblazerz11:
The latest nightly should be same or close to rc4. Will wait until stable release to put into special folder.
[Nexus 4 Android Development] soumoks:
Hey trying your rom for the first time,a couple of questions..

whats the difference between the roms in the grouper folder and the mako folder?

only linaro customization right?any cherry picks? TIA :)
[Nexus 4 Android Development] trailblazerz11:
Grouper is nexus 7, mako is nexus 4. Nexus 4 has more optimizations specific for Krait.
[Nexus 4 Android Development] soumoks:
sorry for the noob question..

one more question,when upgrading from one nightly to the other,is it necessary to flash gapps as well?we have to do it for other roms but have read many times that its not required for cm,is that true?
[Nexus 4 Android Development] trailblazerz11:
No it's not necessary. Only on a clean install. Official gapps rarely update but the apps themselves update over play store.
[Nexus 4 Android Development] soumoks:
This is epic man! Damn fast!! Which kernel do you recommend for this rom?
[Nexus 4 Android Development] richardddd:
I use Franco #142 super fast and epic battery life
[Nexus 4 Android Development] soumoks:
Will be using that only then :)
[Nexus 4 Android Development] markd0wn:
I use franco.Kernel which is great for this rom in my opinion (and several others who use this combo). At the time of writing this, the newest version is #146, and there's also a Linaro build here (currently using it), if you want a combo of a Linaro rom+kernel.
[Nexus 4 Android Development] soumoks:
will try that also,the same battery life as that of franco's right?
[Nexus 4 Android Development] markd0wn:
Yep, should be.. same for me
[Nexus 4 Android Development] soumoks:
are you finding any difference in performance between this and the actual franco kernel?,am on r142 from the past week or so,its rocksolid and damn smooth!
[Nexus 4 Android Development] markd0wn:
I don't feel any significant difference (maybe tiny placebo) between normal and linaro 146, but since there's is no difference for the worse, I stay on the linaro build just for the 'feeling' of having both a linaro rom & kernel.
[Nexus 4 Android Development] soumoks:
Oh ok,will give it a try anyway.thanks
[Nexus 4 Android Development] gabx:
How did you solved this error ? I have same when building bionic (not an easy task as errors are everywhere !).

Thank you for help.
[Nexus 4 Android Development] trailblazerz11:
Building with Google bionic? That's when I got the error if I remember correctly, testing Google bionic.

Since bash is external added by Cm it's not compatible. I don't remember if I was able to fix it or if I set it aside and just didn't build bash. I'll look when I'm home.
[Nexus 4 Android Development] gabx:
Yes, GOOG bionic. I tried two versions : the one from android source, and this one, which looks better:

https://github.com/android/platform_bionic

My build is full of warnings/errors. This could be due to the GCC 4.8 use, but I do think Bionic is really a pain in the ass to build!
[Nexus 4 Android Development] lonelywolf11:
I cannot see the dots with pattern lock screen..... but in the lock screen options I'm sure that the 'make pattern visible' option is checked~~~is there anybody getting any idea about this ?
[Nexus 4 Android Development] mmaser26:
temp solution to mms not working

Use Facebook messengers SMS function until the issue is fixed. You can send and receive texts on that just fine!
[Nexus 4 Android Development] trailblazerz11:
What rom are you building btw?

I gave up trying to use Google bionic in this ROM, for too much of a hassle. Required updates of Dalvik and libcore and most of the externals CM added broke.
[Nexus 4 Android Development] gabx:
This ROM:

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

If you don't use GOOG bionic, how do you deal without ? Yes, it is a big pain. Can't understand why they don't use eglibc or another light glibc.
[Nexus 4 Android Development] trailblazerz11:
I just use CM's which branched off awhile ago. Cherry pick Google bionic commits when I can.

Not sure with that rom. First glance seems they didn't release their bionic source. They probably made changes that now make Google bionic incompatible. Might be hard to get working if they don't release source.

Pretty sure bionic was made so it would conform to apache. Didn't want any gpl other than Linux.
[Nexus 4 Android Development] gabx:
This rom is very closed to aosp with some CM cherry picks. Everything is open source, including Bionic.

I must admit I am looking for troubles when building with arm toolchain based on GCC 4.8 :(

I can deal with most of errors as they are mostly C syntax issues, but this one about ERRNO is pissing me off
[Nexus 4 Android Development] trailblazerz11:
I have just started touching gcc 4.8 so I dunno :(

Does it build fine with their tool chain and their bionic?