yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dhiru1602:
Samsung Galaxy S2 I9100G which is OMAP4 variant of Galaxy S2 is currently using the 1.9 PVR Driver. If you are building with CM, you could use the samsung_omap4 repo to build the driver.

https://github.com/CyanogenMod/android_device_samsung_omap4-common

#define PVRVERSION_BRANCHNAME "1.9"
#define PVRVERSION_BUILD 2291151

The driver in the CM repo is 1.9@2291151 as opposed to the omapzoom driver listed in this topic which is 1.9@2166536. This means that I9100G is using a newer driver. With this said, I don't think the newer driver would give a "Kitkatish" performance boost, but it should increase performance marginally though.

https://github.com/CyanogenMod/andr.../cm-10.2/pvr-source/include4/pvrversion.h#L61
[Samsung Galaxy Nexus] MWisBest:
Interesting... could probably have a look at the kernel code as well to see if there are any commits needed past omapzoom's p-android-omap-3.0 (I may have that name wrong, can't check right now) branch to support that pvr driver. Thanks.

I did decide to take another stab at this myself, starting with the omapzoom kernel and then merging in the tuna branch... still some things to work out before it builds but it looks promising? I still think kernel stuff like this is just beyond my capabilities, but it can never hurt to try. :)

Maybe the better course of action would be to, rather than merge in the tuna branch entirely, start from the omapzoom kernel and then manually add the things required for tuna, perhaps [MENTION=2838735]aosp[/MENTION] or [MENTION=4243514]Hashcode[/MENTION] might be able to shed some light on this? :D
[Samsung Galaxy Nexus] Mevordel:
Which omapzoom branch are you starting from?
[Samsung Galaxy Nexus] MWisBest:
p-android-omap-3.0, however p-android-omap-3.0-dev might be what I should be using now that I look at it more. >.< Again, this stuff is kinda beyond me, but I'll keep trying things anyways.
[Samsung Galaxy Nexus] bsmitty83:
I believe this one I've tried before I get farther into The build with this but I hit a ton of errors when it gets to some included Linux files ....

Also I get conflicting reports about what omap version my phone is running , one says 4430 one says 4460 ? I think cpu-z is wrong .
[Samsung Galaxy Nexus] tommrazek01:
Those two, AFAIK differ only by frequencies.
[Samsung Galaxy Nexus] Quad.X:
I don't think that it is just because of TI, since Google Glass is running an omap 4430, and they have no plans of retiring Glass.
[Samsung Galaxy Nexus] kuronosan:
Duh. It's very clear that they want to sell N5s. Welcome to Corporations 101.
[Samsung Galaxy Nexus] AndyYan:
Next generation of Glass is coming... Google is seemingly recycling old versions from testers and give them new ones, the hardware of which is yet unknown.

Sent from Samsung Captivate Glide @ CM10.2
[Samsung Galaxy Nexus] malybru:
Mod Edit

Thread cleaned.

If you have nothing important to contribute,then, it is best to say nothing.

Let the devs do their work.

malybru

Forum Moderator
[Samsung Galaxy Nexus] metalspring:
Unless I'm not understanding what you mean, the gnex does have the omap 4460, not the 4430

http://www.phonearena.com/phones/Samsung-GALAXY-Nexus_id5595

http://en.m.wikipedia.org/wiki/Galaxy_Nexus
[Samsung Galaxy Nexus] bsmitty83:
Right , I know the soc is omap 4460 but why does the PVR version say omap 4430? I guess those pics were useless and my real question should have been why under proc/PVR/version say omap4430 ? I could have sworn ive seen omap4460 under proc/PVR /version before
[Samsung Galaxy Nexus] tacosrdelicioso:
Delete
[Samsung Galaxy Nexus] metalspring:
Maybe whatever source you used had omap4430 sources in it that make it read omap4430 under proc/PVR/version

Or maybe it depends on what max speed your kernel is set for

basically the only difference I know of between 4430 and 4460 is the 4430 has a max speed of 1-1.2 GHz while the 4460 has a max speed of 1.2-1.5 GHz listed
[Samsung Galaxy Nexus] bsmitty83:
Yea I think I'm just getting confused since my brain is overworked ATM , I need a break ........

Im thinking that the new driver needs to be built with the ROM ? All the sources pull PVR out of the kernel source and add it to device_Samsung_omap4-common , so I'm not sure if you can simply build the kernel , then build the modules , since all the libs are needed too .

I've never built a kernel with sources outside of the kernel source itself , I feel like I'm chasing my tail with this craziness
[Samsung Galaxy Nexus] metalspring:
I'm no kernel or rom expert but I do know some so wouldn't it work building the kernel inline with a rom?

If so maybe a rom Dev could add the needed source and you could help them get the kernel part of the source to build right?
[Samsung Galaxy Nexus] Mevordel:
Then we get into the issue that 4.3 disabled module loading... I know that can be configured out, but it's still a bit of an issue if we're going for full AOSP compatibility.
[Samsung Galaxy Nexus] bsmitty83:
Exactly , I'm not sure how this can be accomplished , but as for the kernel side I'm pretty sure you just have to remove PVR from the kernel as its built outside after the kernel is compiled so AFAIK it should be all on the ROM side , (or at least a majority)

I'm definitely no expert so someone plz correct me if you think I'm wrong I'm just thinking out loud now
[Samsung Galaxy Nexus] Mevordel:
In his original try, JackpotClavin said he tried starting with the omapzoom 3.4 branch (he didn't say which one; there are a few), but couldn't get it to boot to adb, so he used vanilla 3.4.y. I've taken a good look at the omapzoom kernel, and I've noticed that android-omap-tuna-3.0 is a direct fast-forward of android-omap-3.0, and that p-android-3.4 merges with only two minor conflicts with the current vanilla linux-3.4.y.

In the interest of not reinventing the OMAP wheel (making use of what work TI's already done), I've applied all of the patches from the fork to android-omap-tuna-3.0 up to the same place JackpotClavin got, and then modified it, using "git log --grep" and what he did as a guide, so it compiles. Some things he had to remove/hack around work on the branch I used, so that's good. No, it doesn't boot to adb yet, but my UART cable will get here tomorrow, so hopefully that will be easily achievable.

It is just finished uploading to Github right now (https://github.com/smaeul/kernel_samsung_tuna), and the .config I used is attached (only minor USB and Framebuffer changes).
[Samsung Galaxy Nexus] bsmitty83:
That's awesome man , if you can get it booting to adb I'm more than happy to attempt to work further on it . thanks for sharing your git too :thumbup:
[Samsung Galaxy Nexus] beekay201:
maybe useful

http://xdaforums.com/showthread.php?t=1461986
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Have you checked these?

https://github.com/KFire-Android/kernel_omap_otter-common/commits/p-android-omap-3.4

https://github.com/KFire-Android/android_device_amazon_otter/commits/cm-10.2-k34

https://github.com/KFire-Android/android_device_amazon_otter-common/commits/cm-10.2-k34

https://github.com/KFire-Android/android_device_amazon_omap4-common/commits/cm-10.2-k34

https://github.com/KFire-Android/proprietary_vendor_amazon/commits/cm-10.2
[Samsung Galaxy Nexus] Mevordel:
Yeah, I have the jig built and working, so when I get home this evening hopefully I can just plug the USB adapter cable in and it'll work.
[Samsung Galaxy Nexus] dhiru1602:
Don't forget to turn on kernel debugging

CONFIG_DEBUG_LL=y

CONFIG_EARLY_PRINTK=y

Assuming Galaxy Nexus wouldn't get KitKat, I am looking for cheap deals on used phones. Let's see if I get lucky.
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Forgot the tate that uses the OMAP4460 like the GNeX [MENTION=4243514]Hashcode[/MENTION] is a mad genius and if you look at the commits I forgot we can update our iio sensors too ;)

https://github.com/KFire-Android/android_device_amazon_tate/commits/cm-10.2

https://github.com/KFire-Android/kernel_omap_bowser-common/commits/cm-10.2

Also the GT-i9260 that is another Samsung phone using the OMAP4 soc is now official in CM10+

https://github.com/ljzyal/android_device_samsung_superior/commits/cm-11.0

https://github.com/ljzyal/android_device_samsung_piranha/commits/cm-11.0

https://github.com/ljzyal/android_kernel_samsung_piranha/commits/cm-11.0

https://github.com/ljzyal/android_vendor_samsung_superior/commits/cm-10.2

OMAP4xxx ain't dead!
[Samsung Galaxy Nexus] >stylz:
Idea

not sure if anyone had in mind, but maybe we could ask mighty chainfire to help us out, like when he wrote chainfire 3d, ,maybe an option, and ignore those desperate unpolite people spamming this thread :D greetz!
[Samsung Galaxy Nexus] bsmitty83:
I did check out the otter branches , I've looked at so many gits lol , but its all useful in some way shape or form . Im gonna take Jackpots original kernel and try to work it up , piece by piece . I'm pretty sure it booted to adb , although he was flashing the kernel to recovery to do adb , it should boot and if I can get some logs at least I wont be flying blind , my biggest focus is on getting the screen code in there after that and hopefully get it to run a ROM even if it fc's or whatever .

But real life and work come first so I'll get at it later tonight . thanks again for the help (everyone ), I definitely appreciate it
[Samsung Galaxy Nexus] Mevordel:
Yeah, it turns out that UART debugging requires kernel support, so I'll have to merge up to those commits and see what I get.

Edit: Yay for git bisect! (Note: it's made for regression testing, so bad here means good.)

f3899bc510fd879059691bac463f877530298cfb is the first bad commit
commit f3899bc510fd879059691bac463f877530298cfb
Author: Adam Hampson <ahampson@sta.samsung.com>
Date: Wed Jul 20 15:17:43 2011 -0700

ARM: omap4: tuna: 4th Sample USB Mux Support

4th sample hardware uses a pair of FSA3200 switches
instead of a single FUSB63UMX 3-way switch.

Change-Id: Ief12ff5449511b600240408b4c745fbfcfc686eb
Signed-off-by: Adam Hampson <ahampson@sta.samsung.com>
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Samsung GT-i9260 is live in CM11

https://github.com/CyanogenMod/android_device_samsung_superior/commits/cm-11.0

https://github.com/CyanogenMod/android_device_samsung_piranha/commits/cm-11.0

https://github.com/CyanogenMod/android_kernel_samsung_piranha/commits/cm-11.0

https://github.com/TheMuppets/propr...mmit/4359694e9a58fa4614cdb9d51a95eccef122378c

So we got the kindles from [MENTION=4243514]Hashcode[/MENTION] especially the tate and now the piranha from [MENTION=1719128]ljz[/MENTION] for OMAP4 phone reference ;)
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] I Just checked again and it does look like ljzyal used a kindle device tree from [MENTION=4243514]Hashcode[/MENTION] for reference so it's possible ;)

https://github.com/ljzyal/android_device_amazon_jem
[Samsung Galaxy Nexus] bsmitty83:
Its definitely possible :thumbup:

I've been messing around between builds of my incredible2 kernels (I'm currently maintaining 4 separate ones lol) with the 3.4 aosp common branch , I added all the missing files , and changed all the kconfigs and makefiles accordingly , I'm using the updated ddk that got reverted back to 1.8 , obviously I'm getting lots of build errors but I'm better at changing things than starting from scratch , so we'll see what happens .

Also i was thinking that if anyone's trying to do this the proper way ( like the OP has done ;) ) by cherry picking the start of the tuna branch and merging with Linux 3.4 , I think you'll have to dust off an old ICS ROM to test on until it gets brought up to jb
[Samsung Galaxy Nexus] Grarak:
Read the OP

JackpotCalvin picked all tuna commits
[Samsung Galaxy Nexus] bsmitty83:
You misunderstood me , I'm not saying Jackpot didn't do it proper , I was simply saying that I, myself wasn't . I know he picked all tuna commits but he started from the initial tuna bringup . I don't think it'll work on jb . I am trying to basically merge the two newest 3.0 and 3.4 kernels :sly:
[Samsung Galaxy Nexus] aosp:
For those asking me why bother or is it possible well with the way Google supported the GNeX you would of never thought the soc we utilize is open lol

OMAP (Open Multimedia Applications Platform)

http://en.m.wikipedia.org/wiki/OMAP

http://omappedia.org/wiki/Main_Page

http://omappedia.org/wiki/Source_Trees

qcom has codeaurora and omap has omapzoom ;)
[Samsung Galaxy Nexus] aosp:
GNeX does not depend on many closed sourced binaries too especially if we go open source

imgtec and ti ;)

broadcom)
* * TO_EXTRACT="\
* * * * * * system/vendor/firmware/bcm4330.hcd \
* * * * * * "
* * ;;
* csr)
* * TO_EXTRACT="\
* * * * * * system/vendor/etc/sirfgps.conf \
* * * * * * system/vendor/lib/hw/gps.omap4.so \
* * * * * * "
* * ;;
* imgtec)
* * TO_EXTRACT="\
* * * * * * system/vendor/bin/pvrsrvctl \
* * * * * * system/vendor/lib/egl/libEGL_POWERVR_SGX540_120.so \
* * * * * * system/vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so \
* * * * * * system/vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so \
* * * * * * system/vendor/lib/hw/gralloc.omap4.so \
* * * * * * system/vendor/lib/libglslcompiler.so \
* * * * * * system/vendor/lib/libIMGegl.so \
* * * * * * system/vendor/lib/libpvr2d.so \
* * * * * * system/vendor/lib/libpvrANDROID_WSEGL.so \
* * * * * * system/vendor/lib/libPVRScopeServices.so \
* * * * * * system/vendor/lib/libsrv_init.so \
* * * * * * system/vendor/lib/libsrv_um.so \
* * * * * * system/vendor/lib/libusc.so \
* * * * * * "
* * ;;
* invensense)
* * TO_EXTRACT="\
* * * * * * system/vendor/lib/libinvensense_mpl.so \
* * * * * * "
* * ;;
* nxp)
* * TO_EXTRACT="\
* * * * * * system/vendor/firmware/libpn544_fw.so \
* * * * * * "
* * ;;
* samsung)
* * TO_EXTRACT="\
* * * * * * system/bin/fRom \
* * * * * * system/lib/libsecril-client.so \
* * * * * * system/vendor/lib/libsec-ril.so \
* * * * * * "
* * ;;
* ti)
* * TO_EXTRACT="\
* * * * * * system/vendor/firmware/ducati-m3.bin \
* * * * * * "
* * ;;
* widevine)
* * TO_EXTRACT="\
* * * * * * system/lib/libdrmdecrypt.so \
[Samsung Galaxy Nexus] rollerdyke44:
just wanted to see the progress of this

read the last 1-2 pages and i dont understand $h!t lol :P

so good luck guys to whatever youre trying to achieve :D
[Samsung Galaxy Nexus] TheMan0790:
Just smile and wave...smile and wave
[Samsung Galaxy Nexus] aosp:
Not sure you seen this tool but it might help you its from the original googler that brought up the tuna board before release ;)

Tools to boot omap44xx over USB.

tuna: switched from UART4 to UART3, remove dead code · 0f7a229 · swetland/omap4boot · GitHub - http://goo.gl/ukGlh9
[Samsung Galaxy Nexus] aosp:
[MENTION=4610477]Mevordel[/MENTION] As always forgot something lol

OMAPCONF: Texas Instruments OMAP Processors Diagnostic Tool

http://goo.gl/DpY5MC

[OMAP4460][OPP][HACK] Hack for Samsung Galaxy Nexus to detect VDD_IVA OP... · 633bb0b · omapconf/omapconf · GitHub - http://goo.gl/NbQzsK

[OMAP4460][GALAXY NEXUS][AUDIT][SYSCONFIG][HACK] skip DSS modules when D... · 6ecc6ca · omapconf/omapconf · GitHub - http://goo.gl/vQw3T6

[TEMP][OMAP4460][GALAXY NEXUS] handle JOP40D specific file name for band... · 837e642 · omapconf/omapconf · GitHub - http://goo.gl/WJLaH7

Forgot one more ;)

[KINDLE][GALAXY NEXUS] better identify Kindle Fire HD and Galaxy NEXUS d... · e53bd04 · ptitiano/omapconf · GitHub - http://goo.gl/tSF0hG
[Samsung Galaxy Nexus] protowave:
Omni ROM supports i9100g which is the Omap variant of gs2. They're working on 4.4 but same graphical glitches :( Kernel is 3.0.x.

jacinto6 drivers is being updated, but for what I see is for 3.8.
[Samsung Galaxy Nexus] krasoski:
Any chance to get back in bussines with the droid 3 with this news? Many people would thank you A LOT!!!!!!!!
[Samsung Galaxy Nexus] kaijura:
Here is a simple explanation that should help understand if you are not developing.

Each finalized kernel for every phone out there is like a "potpourri". Each component of the potpourri mixture applies to a specific element of the kernel - the video drivers, codecs, VPN, wifi, cpufreqs, governers, and so on.

There are finished 3.0 kernels, from the official google kernel or other variations where developers tweaked and specialized that 3.0 kernel. (eg: franco, Mpokang, etc).

But in today's date, the 3.0 is already considered an old product (See: http://en.wikipedia.org/wiki/Linux_kernel#Maintenance ). Most modern devices released in 2013 are on 3.4 (flo, mako, etc). So the original intent of the OP (JackPotCalvin) was to get it from 3.0 to 3.4, which he managed to do. It's an accomplishment for developers, but for the user side you don't notice anything since it isn't working for you.

Hashcode is one of the few developers who accomplished a working 3.4 kernel for the OMAP SoC for the Kindle. Other devs here are trying to accomplish the same but for the galaxy nexus. aosp is sharing his findings on updated commits (aka the potpourri components) out there that seem appropriate for the Galaxy Nexus while others in here are trying to build this kernel and adding those changes. But we are stuck on building, because picking and merging new commits means having to fix unpredictable problems and build errors.

The final product is supposed to be a nice, working 3.4/3.0 kernel compatible with KK without the glitches users are currently experiencing in almost all other 4.4 roms, since those kernels aren't updated.

Hope that helps clears up any confusion for what is going on. So the progress of the Gnex kernel right now is to contribute by posting information that is helpful to building the kernel, until all quirks are figured out and it is working.
[Samsung Galaxy Nexus] RedDeadDorito:
so ift his 3.4 kernel does get done, we're pretty much ready for the next couple Android versions as long as they stay within the 3.4 kernel?
[Samsung Galaxy Nexus] aosp:
That belongs in the op ;)
[Samsung Galaxy Nexus] metalspring:
it might be possible?

omap 4430 and omap 4460 are basically the same except for top cpu speed and the droid 3 (along with a bunch of other popular phones) use the omap 4430, although motorola phones do have the whole locked bootloader thing to deal with

I'll just make a quick list of popular phones/tablets that use omap 4430 or 4460 so devs here can check those sources (if there are any) and so others have an idea what this might help.

omap 4430-

Motorola Droid 3/Milestone 3, Motorola Droid Bionic, Motorola Droid RAZR, Samsung Galaxy S II (GT-I9100G), Samsung Galaxy Tab 2 (7.0), Samsung Galaxy Tab 2 (10.1), Amazon Kindle Fire, Google Glass

omap 4460-

Samsung Galaxy Nexus, Huawei Ascend D1, Huawei Ascend P1/P1S, Nexus Q, Kindle Fire HD 7

source- http://en.wikipedia.org/wiki/OMAP
[Samsung Galaxy Nexus] :
[WIP/DEV] I've got a "booting" NEXUS 5! :p
[Samsung Galaxy Nexus] kuronosan:
With inferior hardware to other phones.
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4610477]Mevordel[/MENTION] Did I forget to tell you guys that the great [MENTION=4112553]dhacker29[/MENTION] owns a GNeX and he is also working on it ;)

https://github.com/dhacker29/android_kernel_samsung_tuna/commits/p-android-omap-3.4

OMAP dead?
[Samsung Galaxy Nexus] thetakerfan:
I dont see anything new there since Feb, 9 months ago. I subscribed to this thread awhile ago to keep tabs on what developments came about but all I'm seeing are links to various gits and wikis, no actual development? This thread confuses me. I haven't the faintest idea how to actually fix anything here just try to follow along and keep tabs, but this one is all over the place.
[Samsung Galaxy Nexus] aosp:
He synced upto Linux 3.4.29 so far and p-android-omap-3.4 is upto Linux 3.4.48

http://omapzoom.org/?p=kernel/omap.git;a=commit;h=31b9c766ecb29bbef4b835892ee267ee9aabd21b

Linux 3.4.48 · 39869ce · smaeul/kernel_samsung_tuna · GitHub - http://goo.gl/UPGa7I
[Samsung Galaxy Nexus] 47th_Ronin:
Yep and his twitter has and link for cm11 with "updated kernel"

But i have no idea what was done to it or by whom...

Im flashing it any damn way though lol...
[Samsung Galaxy Nexus] metalspring:
i tried it and after about 5 minutes of using it i got a lockup where a battery pull was needed and graphical errors were still there so it doesnt seem like much has been changed on the surface yet

also its the "bare minimum" cm kernel with practically no options lol

that said, at least he is working on it

edit: On second thought, maybe his "updated kernel" simply means updated to 3.0.101... these are his latest commits (branch cm-11.0) and most of the commits are Merge tag 'v3.0.101' into cm-11.0

https://github.com/dhacker29/android_kernel_samsung_tuna
[Samsung Galaxy Nexus] aosp:
http://twitter.com/dhacker29/status/401290832172433408

CM-11.0 for Verizon Galaxy Nexus (toro) with updated kernel (no random reboots so far) http://t.co/zI3hgFniXh

Gapps: http://t.co/xqsbCibCW9

[MENTION=4112553]dhacker29[/MENTION] is most likely using the CM11 branch for this one

https://github.com/dhacker29/android_kernel_samsung_tuna/commits/cm-11.0
[Samsung Galaxy Nexus] xolanir:
Can this kernel be flashed on the Shiny 4.4 ROM?
[Samsung Galaxy Nexus] LiquidXed:
Y not try and let us know❔
[Samsung Galaxy Nexus] metalspring:
...you'd have to build that particular kernel from source first lol

not to mention its nothing special, still only linux version 3.0.101 and the cm kernel has almost no options to change in it
[Samsung Galaxy Nexus] aosp:
The kernel he used for that build is this one

https://github.com/CyanogenMod/android_kernel_samsung_tuna/commits/cm-11.0
[Samsung Galaxy Nexus] wavedashdoc:
Dirty flashed over shiny. No issues.
[Samsung Galaxy Nexus] akash3656:
Are the graphical glitches with webview still there?
[Samsung Galaxy Nexus] kuronosan:
Kernel link? I'll test it.
[Samsung Galaxy Nexus] wavedashdoc:
Yes. But so far. No reboots. Seems pretty stable. Good.

---------- Post added at 10:45 PM ---------- Previous post was at 10:37 PM ----------

Yeah I've already done way more multitasking than the previous ROM and Kernel allowed before reboot. I'm going to call it. CM 11.0 is the most stable rom yet for toro.

---------- Post added at 10:53 PM ---------- Previous post was at 10:45 PM ----------

I flashed this new ROM over Shiny 11/10/13 with ART enabled with TWRP and no issues. With have nexus phones guys....you the really can't mess up. Make a nandroid and all that jazz if you're worried.
[Samsung Galaxy Nexus] Link_of_Hyrule:
Good to hear there is a little progress but hopefully we can get the graphical glitches sorted out soon keep up the great work :D
[Samsung Galaxy Nexus] kuronosan:
Works great, can't tweak, isn't rooted, no glitches yet. Unfortunately because the settings don't stick I had to revert. Running Shiny.
[Samsung Galaxy Nexus] xolanir:
Did you just flash the kernel, or GAPPS as well?

What tweaks are you referring to, and as far as root is concerned, can it be "flash" rooted?
[Samsung Galaxy Nexus] DaRk_dOg:
https://twitter.com/dhacker29/status/401578453800980480

Just a heads up ;)
[Samsung Galaxy Nexus] :
Just so I'm on the same page as you guys, is this 3.4 kernel or 3.0.x?
[Samsung Galaxy Nexus] metalspring:
the one used in the cm-11 build is 3.0.101
[Samsung Galaxy Nexus] Pasquale91fg:
where can I find the zip to flash? you have flashed below to Android 4.4??
[Samsung Galaxy Nexus] gh0stslayer:
The best build for maguro till date
[Samsung Galaxy Nexus] Ashtrix:
Can't download from the university net :( .

[MENTION=3013827]DaRk_dOg[/MENTION] Your Crystal2 theme is awesome. An update for nova will be great (Fixing the icons scaling, smooth look) !! thankx buddy :cool:
[Samsung Galaxy Nexus] gh0stslayer:
here is the twitter post by dhacker with the link for rom.zip and gapps, factory reset and flash as usual
[Samsung Galaxy Nexus] AbhishekS:
Does that ROM has all CM customizations like Pie and Quick Toggles?
[Samsung Galaxy Nexus] gh0stslayer:
not yet, but almost all the things you can find on slimkat right now, save a few like safe volume headset, statusbar brightness

still no reboots till now, i'm running it since this morning
[Samsung Galaxy Nexus] Royal King:
No graphical glitches? :eek: