yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tiny4579:
I should be able to just use the super secret TheMuppets repo on github for the vendor files like I do for toro since the extract_files.sh is missing. I'd prefer to do it that way so I can keep up to date with the CM vendor files. Oops, I said it. It's no longer super secret.

I see you started posting before I finished. I just need to add the maguro to mine since I'm using the toro files.

You have a little mistake up there. You're copying the toro device tree to maguro. Also, it doesn't look like the device and kernel trees are needed for CM10.1 at this point. I use a local_manifest instead of default for my local changes.
[Samsung Galaxy Nexus] MBQ_:
My bad, did it in a bit of a rush and copied/pasted from http://rootzwiki.com/topic/32731-ho...les-for-cm10aokpetc-galaxy-nexus/page__st__30 :)

Sorry
[Samsung Galaxy Nexus] tiny4579:
No worries. Everyone makes mistakes. It's the nature of being human.
[Samsung Galaxy Nexus] MBQ_:
Regardless, I have it set up in my build environment :D hahah

I know you're more than capable, but if you ever need help.. Let me know
[Samsung Galaxy Nexus] tiny4579:
I need help with one thing right now, tracking down the cause of this camera force close issue. I prefer to not use the workaround libc.so replacement I have in the third post. I've already scanned vanir and didn't find any fix or via a Google search which mentions a fix in bionic to modify memcpy to work properly with the Galaxy Nexus. So far the only fix after working on this for hours was pull a libc.so from a regular CM10.1 build. I've posted on a couple of the vanir threads on rootz about this issue.
[Samsung Galaxy Nexus] MBQ_:
If we can get a log, I bet we could find the root of the issue
[Samsung Galaxy Nexus] tiny4579:
Logcat is two pages back.

http://xdaforums.com/showpost.php?p=40361406&postcount=27

It looks oddly similar to this bug:

https://bugs.launchpad.net/linaro-android/+bug/1075111

And the commit is here:

https://android-review.googlesource.com/#/c/36645/

I think the problem is that I don't know how to switch memcpy in my build.
[Samsung Galaxy Nexus] MBQ_:
My bad D: couldnt read back though, because im in school. Thanks bro, I have my senior paper to type, and ill read the log(s) and commit

thanks :)
[Samsung Galaxy Nexus] tiny4579:
I think I found a fix.
[Samsung Galaxy Nexus] tiny4579:
I have found a real fix to this but as I am choosing to use my kernel of choice (Tiny 4.0 right now which seems to have some issues), I'm going to hold off until that gets figured out. Did anyone have deep sleep issues with the kernel in this first build or is everyone holding off for the camera that I have a fix in the OP for? (uses pretty much the same one as today's release).
[Samsung Galaxy Nexus] ArnieG:
Deep Sleep issue

I got no deep sleep on this build so reverted to regular CM 10.1. Looking forward to updated release. Also went back to Tiny 3.4.1 because no deep sleep with 4.0.
[Samsung Galaxy Nexus] tiny4579:
Again, I got deep sleep on this build and tonight's build. That answers my question. Maybe it's hardware related that some can take the pretty much meat and potatoes of 4.0 and others can't.

Are you having the suspend_backoff issue too? Please share bbs screenshots or gsam under kernel wakelocks.
[Samsung Galaxy Nexus] ArnieG:
No suspend_backoff issue.
[Samsung Galaxy Nexus] tiny4579:
What is the primary kernel or partial wakelock preventing deep sleep? I'm trying to iron out a possible bug and need as much feedback as I can.
[Samsung Galaxy Nexus] ArnieG:
I've gone back to cm 10.1 4/18 nightly and won't be able to re-create the issue until sometime tomorrow...sorry.
[Samsung Galaxy Nexus] tiny4579:
No worries. I'll be able to figure it out. Either way, I can get the 4.0 features without the deep sleep issue or 4.1 bluetooth support at the very least.
[Samsung Galaxy Nexus] ArnieG:
4/19 build is up.....downloading now.
[Samsung Galaxy Nexus] tiny4579:
It's not complete. Wait please.
[Samsung Galaxy Nexus] un4givn85:
i thought it was a little strange it was only 29 megs lol

is the camera fix in this?
[Samsung Galaxy Nexus] tiny4579:
Yeah, I'm building with Linaro's bionic tree so things should be smoother sailing now. Goo was uploading slow so it may have given issues and been incomplete.

The build is fully uploaded now.
[Samsung Galaxy Nexus] un4givn85:
still only showing 121 megs?

the first one was 171?

is that right?

edit: nevermind, the download is 171, the hover on goo shows 121 tho
[Samsung Galaxy Nexus] tiny4579:
I think you guys were jumping too quick, lol.
[Samsung Galaxy Nexus] un4givn85:
thats very possible lol

downloading now, will report back later

thanks man
[Samsung Galaxy Nexus] ArnieG:
Is it up now? (she whispered...blushing)
[Samsung Galaxy Nexus] tiny4579:
It's good.
[Samsung Galaxy Nexus] ArnieG:
Great ROM

Your take on CM 10.1 plus Tiny 4.0.1 may be the best combo I've used. Performance and battery are great! Thanks.
[Samsung Galaxy Nexus] laureanop:
I installed this combo this morning and I concur. My new daily driver. Linaro optimized CM is what I've been looking for. Thanks Tiny

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] zoomy942:
How's that awful lag bug?
[Samsung Galaxy Nexus] tiny4579:
It doesn't seem to lag too bad. I don't think it's fixed but I applied the patches I expected should make some difference and with Linaro optimizations it should help.

The short answer is that it's fixed in 4.1.2 or 4.2.1.

I thought people were complaining about lag in 4.2.1 but maybe it was never as bad as 4.2.2.
[Samsung Galaxy Nexus] zoomy942:
I've been watching its progress all over.

Its 4.2.2. And generally its a low fps and /or redraw bug people notice in the app switcher or as the home button is pressed exiting an app.
[Samsung Galaxy Nexus] laureanop:
It's definitely 4 2 2. But this Rom is great so far. Even Bamf which has a lower , memory footprint has the lag at times.

The relentless pursuit of the perfect rom

---------- Post added at 06:13 AM ---------- Previous post was at 06:12 AM ----------

My nexus 7 tablet running stock 422 is unusable at times.

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] un4givn85:
just an update

been running the latest build with no problem and similar battery life to cm10.1 nightlies

great job man
[Samsung Galaxy Nexus] tiny4579:
I'm thinking about doing a quick build non linaro of cm10 and applying a few of my cherry picks from cm10.1. I think the systemui memory leak was in cm10. It just didn't get fixed until cm10.1. This further proves the memory leak is not related to the lag in 4.2.2.
[Samsung Galaxy Nexus] zoomy942:
I'll agree with that
[Samsung Galaxy Nexus] yepitsme19:
Why can't people just admit that 4.2.2 is a horrible update? 4.2.2=lag. It's not rocket surgery. I personally think Google f***ed up but the typical Android fanboi will say there is no lag and if there is, it must be the person building it, how they built it, what they forgot to add, etc... Just my $0.02 :D
[Samsung Galaxy Nexus] laureanop:
I think quite a few of us are, including Tiny. I agree 100 % with you. 4 2 2 is a step back for Android. I am strongly considering going back to 4.1x

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] tiny4579:
Yeah. Not impressed with 4.2.2 at all. I made a 4.1.2 CM10 build last night. I'll upload it tonight. It has part of the systemui memory leak fix from CM10.1 as the other part doesn't seem to be needed. It also has some dalvik fixes. CM10 was always good as it was. I don't need to do too much to improve it. Maybe I can do Linaro but it doesn't seem to be worth the headache for a small difference.
[Samsung Galaxy Nexus] bustedukulele:
I'd love to try this if you get a chance to upload it. Haven't been on 4.1.2 in awhile.
[Samsung Galaxy Nexus] tiny4579:
As promised I uploaded a CM10 build to my CM10 folder. Since CM10 isn't changing much I won't build again likely but CM10 was woefully out of date.
[Samsung Galaxy Nexus] bustedukulele:
Thanks man. I really appreciate it. I just got the gnex a few months ago so ive never run anything except 4.2.2.
[Samsung Galaxy Nexus] dirtsky:
Hey tiny you wouldn't happen to have the proprietary blobs for the toro would you? I'm having issues trying to setup adb on my machine and I really don't want to try pulling them manually on a windows machine.
[Samsung Galaxy Nexus] bustedukulele:
I couldn't get the CM10 build to boot. It got stuck at the Google screen every time I tried.
[Samsung Galaxy Nexus] tiny4579:
Check your md5. Also what kernel are you running? I dirty flashed from CM10 stable.
[Samsung Galaxy Nexus] tiny4579:
I just pull them from TheMuppets repo using a local_maifest file:

<remote fetch="http://github.com/" name="gh" revision="master" />
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-10.1" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="TheMuppets" />
<project name="proprietary_vendor_imgtec" path="vendor/imgtec" remote="TheMuppets" />
<project name="proprietary_vendor_broadcom" path="vendor/broadcom" remote="TheMuppets" />
<project name="proprietary_vendor_invensense" path="vendor/invensense" remote="TheMuppets" />
[Samsung Galaxy Nexus] dirtsky:
I'm noob to building so forgive my noobness. Wouldn't I just add these to the local_manifest.xml and then do a repo sync once again to refresh it?
[Samsung Galaxy Nexus] tiny4579:
Yep. That will work. That location is deprecated so it's advised to move to the new location. It is builddir/.repo/local_manifests/whatever.xml
[Samsung Galaxy Nexus] tiny4579:
New CM10.1 build about to be uploaded featuring the following change:

I have a pretty strong feeling this will help:

http://review.cyanogenmod.org/#/c/36440/
[Samsung Galaxy Nexus] dirtsky:
Nice. Thanks for the help. I'll add them lines to my manifest and sync then when I get home from work start a build.
[Samsung Galaxy Nexus] scotty1825:
Tiny, what's the difference between the two ROMs you have posted today on goo.I'm? Tiny and unofficial?
[Samsung Galaxy Nexus] dirtsky:
Hey tiny just wanted to let you know that I now have a successful build and running nice. Thanks for the help again.
[Samsung Galaxy Nexus] zoomy942:
Tiny is a cm10.1 build adjusted to Linaro. The unofficial is a cm10 build I think.
[Samsung Galaxy Nexus] tiny4579:
Actually there was a partial unofficial CM10.1 build that I cancelled and forgot to delete. If you have that 4/25 from yesterday delete it as it's no good.

The CM10 unofficial was from 4/23.
[Samsung Galaxy Nexus] bunnahabhain:
So tiny my friend i got some questions to annoy you :P

*What is the difference between this and Jellbro, only the cherry picks?

*Maguro Builds planed or is that deprecated?

:D
[Samsung Galaxy Nexus] ericsdeadinside:
Hmm mine is already set to 96 according to pimp my rom
[Samsung Galaxy Nexus] parkson:
The page suggests 64m for heapgrowthlimit and 256 heapsize (default).
[Samsung Galaxy Nexus] ericsdeadinside:
Ah ok read it wrong.
[Samsung Galaxy Nexus] tiny4579:
I still haven't published them. The annoying part is posting the changelog.

No maguro builds. I only build for what I own. If you can't tell from my sig, I just got the HTC One, which is awesome, so I'll have a little less time for the Galaxy Nexus.
[Samsung Galaxy Nexus] un4givn85:
you wouldnt happen to have a mirror for the newest build would you?

goo is "experiencing technical difficulties" lol
[Samsung Galaxy Nexus] tiny4579:
Due to the awesomeness of goo right now, I am reposting the newest build as a mirror:

cm-10.1-20130425-TINY-toro.zip - 170.87 MB
[Samsung Galaxy Nexus] ericsdeadinside:
Since goo seems to be completely dead could you possibly mirror the 10 build too I'd like to try that.
[Samsung Galaxy Nexus] Baby_Phil:
I wish I would have checked your thread it took 5 hours to download lol
[Samsung Galaxy Nexus] tiny4579:
Not tonight. If someone has it they can mirror it and post in this thread.
[Samsung Galaxy Nexus] RyanTX:
I wish the One would come to Verizon.
[Samsung Galaxy Nexus] tiny4579:
Dev-host mirror of CM10 build due to goo issues:

cm-10-20130423-UNOFFICIAL-toro.zip - 157.79 MB

Also, how is everyone liking the new CM10.1 build? Does the heapgrowthlimit change to 64 from 96 seem to be helping?
[Samsung Galaxy Nexus] zoomy942:
I'm no using your build (yet) but using the kernel.

Anyway. I changed my build prop to 64 yesterday. Its working much better for now.

---------- Post added at 07:02 PM ---------- Previous post was at 06:49 PM ----------

And I just noticed the screen off max of interactive is 700? Awesome.
[Samsung Galaxy Nexus] scotty1825:
I've been running your new ROM since late last night and love it. This one works a lot better on my phone than your 4-19 build. Thank you.
[Samsung Galaxy Nexus] zoomy942:
Just had my first UI lag with 64 build prop.

Tiny, does your build include some ideas to prevent that?
[Samsung Galaxy Nexus] tiny4579:
The fix needs to be on Google's end.I'm done with this silly fixing game. I have a few tweaks. Just try it out.
[Samsung Galaxy Nexus] zoomy942:
From the HTC One. Nice pick my friend.

---------- Post added at 03:30 AM ---------- Previous post was at 02:50 AM ----------

What android version dod iut ship with?
[Samsung Galaxy Nexus] ericsdeadinside:
4.1.2 kicksass so fast and smooth. And battery doesn't empty just by looking at it wrong.
[Samsung Galaxy Nexus] tiny4579:
4.1.2 though even if it had 4.2.2 it wouldn't necessarily have all of Google's features.
[Samsung Galaxy Nexus] zoomy942:
You mean the systemUI "feature?"

:p

---------- Post added at 02:19 PM ---------- Previous post was at 02:11 PM ----------

The only feature I like on 4.2.2 is that swipe keyboard
[Samsung Galaxy Nexus] tiny4579:
Get the real Swype. It's much better in my opinion.
[Samsung Galaxy Nexus] zoomy942:
Testing it now.
[Samsung Galaxy Nexus] klobkelosh:
Yeah, the newest play store release of swype is excellent. Best swiping, better than stock or swiftkey. Plus they have a holo theme now
[Samsung Galaxy Nexus] tiny4579:
The holo theme has orange trails which I don't care for though but it works great. It was a dollar but might have gone up.
[Samsung Galaxy Nexus] zoomy942:
Not sure about the dragon built on feature to be honest
[Samsung Galaxy Nexus] bravac:
Does the cm10 reversion have the old bt stacks? Ie the ones that had avrcp 1.3 or 1.4 which displayed meta data correctly? Thanks!
[Samsung Galaxy Nexus] tiny4579:
CM10 is CM10. Why would it have anything from 4.2? It's pure CM10 and Android 4.1.2.
[Samsung Galaxy Nexus] klobkelosh:
I like the orange!

actually, I've always wanted to build a theme where all the holo blue becomes orange. Never got around to learning how to build a theme chooser theme.

You can just turn it off like I do.
[Samsung Galaxy Nexus] surfboard3r:
I'm having a problem where every other time I turn off the screen Pandora crashes.any tips? Also my reception is very weak in areas where I can actually see the tower.

Thanks for your work
[Samsung Galaxy Nexus] danielkuhlman:
First Rom I've flashed since I've been back in the states. Gotta say, I'm pretty impressed. Thanks!
[Samsung Galaxy Nexus] T-Keith:
I kept getting reboots on CM10.1 and tiny's kernel so I tried this ROM instead. Unfortunately the reboots and lockups are back. I was on weatley so I tried ktoonservative and got a lockup within a few hours. I can't seem to get last_kmsg to work it keeps saying no such file name. I also tried the app syslog but that doesn't seem to work either. FWIW I have the same crash messages from Pandora.
[Samsung Galaxy Nexus] tiny4579:
How are you trying to pull last_msg?

I need a logcat of the Pandora crashing as I haven't seen it myself.
[Samsung Galaxy Nexus] T-Keith:
I got it to work, sorry. I will email you the logs. Ironically my phone locked up in the middle of emailing them to you.

thanks,

-Keith
[Samsung Galaxy Nexus] tiny4579:
I hear there's a new build up with the battery bar added as well as the voice activated shutter with CM's native camera app.
[Samsung Galaxy Nexus] MBQ_:
Guess it's time to switch to your ROM again. :)
[Samsung Galaxy Nexus] laureanop:
Running smooth with your latest kernel. The switch to 64mb heapgrowth limit indeed does make a difference. Tried it on Cm, slim, carbon and yours and the difference is noticeable, specially when you use memory intensive apps like Facebook a lot

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] tiny4579:
Thanks. I submitted the revert of the heapgrowth limit for 1GB RAM phones back to 64mb to CM and they actually merged that commit. I was surprised that Cyanogen himself merged my commit to change that.
[Samsung Galaxy Nexus] laureanop:
Yeah I read their discussions in gerrit and they all agreed in the improvement.

That's awesome that Steve Kondic merged it himself

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] dirtsky:
I use this fix in my PAC Rom that I started building. It smooths things out so much better.

Sent from my PAC infused Galaxy Nexus
[Samsung Galaxy Nexus] KlugN:
Hmm I'm going to have to give this a try tomorrow!
[Samsung Galaxy Nexus] tiny4579:
Added build instructions link to OP for those who would like to be able to compile CM10.1 with Linaro.

The only things missing from them are the additional dalvik commits I pulled from Rascarlo who pulled from AOSP master, the battery bar as it requires some effort to merge, and the goo.im OTA feature howto.
[Samsung Galaxy Nexus] T-Keith:
Thanks for the rom. I cleared data on Google services and now it is running smooth. How do you use the voice feature on the camera.
[Samsung Galaxy Nexus] tiny4579:
In the options wheel as I'm calling it, go to the little alarm clock thingy that's crossed out and select the little image of Cid. If you don't have that, you need to flash the gapps without the camera added from the OP after doing a system wipe and reflashing the ROM.

Then once you see that little Cid logo, you can trigger it by saying Whisky, Cid, or Cheese.
[Samsung Galaxy Nexus] T-Keith:
Ok, thanks I'll have to flash that.

How is the HTC one? Was your contract up with Verizon? I'm stuck until this December. Which carrier did you go to?
[Samsung Galaxy Nexus] zoomy942:
Can I remove the camera apk? Then flash the ROM and the camera will be readded?

---------- Post added at 05:29 PM ---------- Previous post was at 04:53 PM ----------

I remembered its gallery.
[Samsung Galaxy Nexus] tiny4579:
Yeah that should work. CM's backup process will try to backup a gallery that's not there and will be unable to overwrite the CM gallery when it restores.
[Samsung Galaxy Nexus] Alton (Halo 2):
Speeeeed!
[Samsung Galaxy Nexus] zoomy942:
Hmm. No picasa sync in gallery?
[Samsung Galaxy Nexus] tiny4579:
Nope. You need the gallery from gapps.
[Samsung Galaxy Nexus] zoomy942:
Bummer. Cm cam or photo sync...
[Samsung Galaxy Nexus] tiny4579:
Actually, you can push the GalleryGoogle.apk from the gapps to have both but you'd also have two cameras and galleries. No way to have both features without having two copies. I believe Go Launcher Ex allows hiding apps from the app drawer though.
[Samsung Galaxy Nexus] T-Keith:
Crap, now I remember why I never used cm's camera.
[Samsung Galaxy Nexus] chris61292:
I can't seem to get WiFi tether to work. Full wipe and md5s checked.
[Samsung Galaxy Nexus] tiny4579:
I should have noticed it before you guys decide to wipe when it isn't needed. Either way, from my rootz thread:

So far with what little tinkering I've had no luck with tethering. It worked for you guys prior to the 5/2 build right? I don't think anything changed on my end. I haven't updated the kernel since 4/19.
[Samsung Galaxy Nexus] tiny4579:
I switched to stock kernel due to issues with tethering for the 5/6 build which should be up in about 10 minutes. Also, I should have probably done this anyway as it uses the CM hostapd compiled hostapd versus the prebuilt and better promotes letting users pick their kernel.

All should be right in the world of tethering for the 5/6 build provided you use the stock kernel or the Tinykernel 4.0.1 build with the old wifi drivers. Let me know if the newwifi tinykernel gives issues though.

Edit: still should work on tinykernel 4.0.1 newwifi so we should be in business. I just verified I could connect to my Gnex from another device but obviously no data (no VZW service). I don't think I'll readd it to the builds though as the ROM should be built to be compatible for all devices and all WiFi networks.
[Samsung Galaxy Nexus] RyanTX:
Is there any way to get the center clock option or will I have to go to another ROM for that option?
[Samsung Galaxy Nexus] tiny4579:
I try to keep cherry picked features to a minimum. The goal of this ROM is to provide a Linaro-enhanced, nearly pure CM experience as possible, while aiming to improve smoothness. If you need all the bells and whistles, CM is the wrong ROM though it has quite a few features.

With that all said though, the answer is neither no nor yes.
[Samsung Galaxy Nexus] zoomy942:
I'll give this a try tomorrow. Been using cm 10.1 with tiny kernel. This is pretty much cm 10.1 just with certain fixes added in.

---------- Post added at 04:14 AM ---------- Previous post was at 03:37 AM ----------

Is the battery bar option able?

EDIT - If I flash this and then gapps, it'll overwrite the camera yes? And are dirty flashes supported as newer versions come out?
[Samsung Galaxy Nexus] zoomy942:
Installed. Noticed it didn't have your latest kernel included?
[Samsung Galaxy Nexus] kevdliu:
Hello tiny,

I know you said you are trying to keep this as pure CM as possible but I have a really small (around 10 lines of code give or take a few thousand. jk around 10-20) commit that will be really useful to those of us who changes the media volume way more often than the ring volume. It it already in CM's gerrit but it has been more than two weeks and no signs of review.

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

Give it a look. Thanks
[Samsung Galaxy Nexus] tiny4579:
I wouldn't worry about that one too much. It looks like it could be merged soon. It doesn't usually get rebased unless one of the devs is interested in possibly merging it. I think you commenting on it might have given them encouragement to look at it again. I'd say wait a few and see if it gets merged. Plus I updated my build instructions recently to make it possible to build this pretty easily.
[Samsung Galaxy Nexus] kevdliu:
Lol it just got approved. :) I guess sometimes it just takes a little push to get the commit in front of the pages of translation ones.
[Samsung Galaxy Nexus] T-Keith:
Wow is the cm10.1 camera bad! And they are at release candidate? It randomly starts in hdr mode, sometimes starts taking burst mode even when it's turned off, if you switch to the front camera and switch back it gets stuck at 1.3 megapixels, and is slower than ever.

All I want is power button shutter and Picasa sync like back in cm7. Is there anything like that out there?
[Samsung Galaxy Nexus] omniatic:
I've been on the 05/06 build for a week now. It's been running very good, nothing to kick at. So, any plans for an updated build? Wasn't sure if there were a lot of changes over the past week, so I thought I should ask.

Thanks,
[Samsung Galaxy Nexus] tiny4579:
Hopefully something this week.

Maybe a wipe is needed as I haven't run into that issue. Another option is that you could instead try clearing data for gallery to reset its settings.
[Samsung Galaxy Nexus] kevdliu:
Tiny do you know if your build or maybe official CM builds have -O3 or other optimizations? The official CM builds are much slower (laggier) than your builds and other AOSP ROMs. I am curious on why. Is it because CM maybe forwent these optimizations to ensure compatibility with the giant range of devices?
[Samsung Galaxy Nexus] tiny4579:
I use -O3 with the Linaro toolchain and patches. CM uses -O2 with the AOSP GCC 4.6 toolchain without any Linaro patches. As you said above this is to preserve compatibility.
[Samsung Galaxy Nexus] kevdliu:
Thanks for the info. I knew there has to be a reason besides placebo. Cant wait for your new build then