yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] juju2011:
None of the links are working for me :(
[Samsung Galaxy Nexus] djtutis:
Aroma installer should be awesome addition! This makes whole project "must have" to all galaxy nexus users! But, you should make this excellent kernel super stable specially this time with all these recognized devs in this! Keep up with this good work!
[Samsung Galaxy Nexus] fracama87:
I'm sure the new kernel work awesome, but link doesn't :D

Your wife's fault...

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Atento:
Completely agree with you. I'm running 4.12 and it's rock solid. No sods, no freezes and as smooth as usual.

It's my fallback now.
[Samsung Galaxy Nexus] michierusama:
Omg everyday there is something new here. Way to go!

What does a kernel has anything to do with videoplayback? Yesterday watching a movie (inception 720 yify ) everything was fine but in some scenes audio would go bad and video lagged using HW+ and mxplayer.

SmittyV and 04/12 build. MHL connection.
[Samsung Galaxy Nexus] ashclepdia:
I've had issues ever since 4.3 and watching HD 720 or 1080(which is mostly unwatchable ugh) on Gnex.

I think someone mentioned issues were fixed by using an old ducati-m3.bin from 4.1.2 I never tried it tho.

Using mxplayer I was only ever able to get actually watchable 720(usually use yify too for my mobile viewing :D ) I would put on SW decoder and then hit menu>playback>Speedup Tricks checked.

I dunno what happened but since 4.3 720p+ playback has been complete shiz on Gnex using HW(or HW+) decoder...

I SOMETIMES had better experience using BSplayer with a certain setting turned on for special type of HW decoder to be used or something...
[Samsung Galaxy Nexus] michierusama:
I use the old ducati "fix" and the video was all good but then sometimes the video lagged and the audio would cut and come back. With cm11 stock kernel everything is fine. That's why I'm asking. Hmm.
[Samsung Galaxy Nexus] bsmitty83:
Updated op with smittyV , [MENTION=4544860]osm0sis[/MENTION] latest suspend trim ramdisk , few touches to zram
[Samsung Galaxy Nexus] wisefreakz:
A hero!!!
[Samsung Galaxy Nexus] osm0sis:
Remember suspend_trim is off by default, so enable it once with Synapse (it persists through reboots), or hunt down my Terminal commands to try it out. :) :good:
[Samsung Galaxy Nexus] michierusama:
When you say watchable is it smooth or with some issues? Thanks...
[Samsung Galaxy Nexus] HONG86:
I used the setting of Neph's Previously .

However , there's no effect on the reduction of fever...when set undervorting...

So, this time, I will try use the settings of büscher's.

Let's Feel the softness during use.:highfive:
[Samsung Galaxy Nexus] ashclepdia:
Well. It depends really which file/movie I'm watching.

And I'm also NOT using the "old ducati bin" 'fix'.

Soo depending on different things like the movie quality and such, I can get anything from perfectly fine playback, to choppy/lagging playback. Usually my most prevelant issue is out of sync audio to video, it won't be crazy off, but just enough that I can tell my device is "having difficulty" decoding it smoothly. But its always WAY better than how it plays using HW or HW+ in MXplayer on anything 4.3+.

I haven't had a chance to check it out on smittyV or anything 4.4 actually yet(I just recently started using 4.4 and 4.4kernels) soon I shall be doing some testing on this issue specifically, gonna try many different apps and kernel/ROM settings(and even some swapping of bins/libs cuz I love experimenting and breaking my gnex lol) hopefully I can start on that Tomorrow after full cleaning of my device (if I finally stop being lazy)

If you wanna join me in trying lotta stuff to experiment hit me up on PM and lemme know what ya plan to try and results, we can work together trying to find better playback for this thing instead of clogging up thread unless you think it's kernel specific although in my own experience video playback issues on Gnex in general aren't specific to any kernel since it's been going on since 4.3 release (unless it was something Google messed up with 4.3 and didn't feel like fixing once they decided to drop tuna support)

Sorry I'm rambling now as usual lol
[Samsung Galaxy Nexus] büscher:
once again I was acting to fast with my script...

reverted highspeed_freq to 920MHz. It just feels a little snappier.

and thx [MENTION=4544860]osm0sis[/MENTION] for this suspend_trim. That's what seems to be a good medication to my borked storage. Everytime after a fstrim my storage gave me very high throughputs compared to if not trimmed... hope that will speed up thing on my phone.

Humm, where do I find that switch in synapse? Or do I need something more than just SmittyV 4/16?

Edit: I think adding a "1" to the third line of /data/trimhelper will do the trick
[Samsung Galaxy Nexus] Swede2008:
Under Misc, second from bottom
[Samsung Galaxy Nexus] büscher:
That was a "SCheckBox has failed" before I added the "1" in trimhelper

Maybe because the line was empty before and not filled with a 0?
[Samsung Galaxy Nexus] Swede2008:
Uhhhh, shrug, worked fine for me with no changes lol
[Samsung Galaxy Nexus] gohamstergo:
[MENTION=3317173]büscher[/MENTION] I notice in your dirtyv script it has

# Set zen as governor
echo "sioplus" > /sys/block/mmcblk0/queue/scheduler

# Set Read Ahead KB
echo "5632" > /sys/block/mmcblk0/queue/read_ahead_kb

I think the "set zen" and "5632" are typos? Since you mention in your thread post that sioplus RAB should be 512?
[Samsung Galaxy Nexus] HONG86:
well. I think Neph's setting is more smooth.

Sent from my Gnex
[Samsung Galaxy Nexus] büscher:
uh yes, thank you, thats a typo

Yep, thats possible. My settings should be a little more battery friendly than Neph's. Also that typo mentioned sure has a impact on smoothness.

I just changed that.
[Samsung Galaxy Nexus] Droiderat:
[MENTION=3317173]büscher[/MENTION]

Is the MinFree setting correct in your latest script? A single value of 512?

Edit: now updated, I see.
[Samsung Galaxy Nexus] büscher:
oh goddammit, i hate that mediafire built in editor...

also fixed that.

please redownload to be sure...

[MENTION=4153477]HONG86[/MENTION]: you may want to give it a try again. this clearly was a big error

edit fyi: I maintain this script on three different places: my phone, mediafire and dropbox. sorry for the errors
[Samsung Galaxy Nexus] p34rp34r:
So I'm still having trouble changing I/O Schedulers. Tried Trickster, Synapse, and Perf Control. Device locks up every time I try to change it and requires a battery pull. I've already tried clearing app data before changing anything.

And on an unrelated topic, I see a lot of this in my logcat:

D/AndroidRuntime( 7532):
D/AndroidRuntime( 7532): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 7532): CheckJNI is OFF
D/dalvikvm( 7532): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 7532): Added shared lib libjavacore.so 0x0
D/dalvikvm( 7532): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 7532): Added shared lib libnativehelper.so 0x0
D/dalvikvm( 7532): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
D/dalvikvm( 7477): JIT code cache reset in 0 ms (4096 bytes 5/0)

which is usually preceded or followed by

E/memtrack( 9956): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug( 9956): failed to load memtrack module: -2
D/AndroidRuntime( 9956): Calling main entry com.android.commands.am.Am
D/AndroidRuntime( 9956): Shutting down VM

This can sometimes just repeat over and over, with the PID constantly changing. I also see a lot of the same apps constantly restarting, usually the Google apps like Calendar or Music or Youtube.
[Samsung Galaxy Nexus] HONG86:
I try again. + neph's undervolt

and I got a good result.

don't know about battery, but smooth and same score with neph's

thanks for your posting and feedback :)

Sent from my Gnex
[Samsung Galaxy Nexus] wisefreakz:
SYNC_LOST is back.... YES!!! SmittyV FTW... Lmfao... As long as it remains smooth... Bring it back *****e$$...
[Samsung Galaxy Nexus] osm0sis:
Bingo! Add a 0 to the 4th line as well. :good:

That's because you used a suspend_trim version from before I added the master switch. Anyone else in this boat should just delete /data/trimhelper and reboot to have it automatically reinitialize itself. :)

Haha apparently that happens when OMAP Gamma Contrast is set to anything other than 0?
[Samsung Galaxy Nexus] Atento:
Try to set OMAP Gamma to 0 and test again. Let us know if it solved.
[Samsung Galaxy Nexus] wisefreakz:
That was it!! Damn... I feel a lil sad now...hahahahaha
[Samsung Galaxy Nexus] michierusama:
Thanks to the script maker we now know that causes the sync lost. Hell yeah!
[Samsung Galaxy Nexus] osm0sis:
Yup! Thanks [MENTION=3317173]büscher[/MENTION] for that one!

http://xdaforums.com/showpost.php?p=51903351&postcount=8100
[Samsung Galaxy Nexus] DR3W5K1:
I just can NOT deal with the way 0 looks so....

I'm just going to deal with it. Plus I'm not seeing any ill affects from the sync errors.
[Samsung Galaxy Nexus] gohamstergo:
Really? I use neph's screen settings and changing that to zero really doesn't even change anything visually, noticeably.
[Samsung Galaxy Nexus] DR3W5K1:
6 really makes your whites well.... um.. white

I can notice it because I keep my screen dim if possible.
[Samsung Galaxy Nexus] ashclepdia:
To me, using 6vs0(5) makes the colors slightly more saturated and less washed out. The difference is easily noted if u use trickster to set it and keep your eye on those color bars at the top. It kinda "darkens" them slightly. Hard to describe, but more easily noticed if u set it to 4, and then go to 6, you see it go from washed out to saturated.

That was a good catch by the way, I had been trying to figure out what caused that as well and had suspected something to do with setting force GPU rendering combined with one of the color settings. But I couldn't get it to show. Very nice catch. I think there might be another thing in dmesg that might have to do with color settings that shows up sometimes though I haven't been certain yet. I just know it has SOMETHING to do with display (the line s6e8aa0 shows up saying something about "factory expects.... But received....")

And yea. Now that we know what causes the sync errors, it also doesn't appear that they are any apparent I'll effects besides the spamming of dmesg lol.
[Samsung Galaxy Nexus] büscher:
Was that old suspend_trim installed in a previous version of smittyV?

Well I'll delete that then :good:

And I'm glad to help where I can with my limited knowledge ;)
[Samsung Galaxy Nexus] osm0sis:
Previous SmittyV-Synapsed, maybe also SmittyV, yeah. :)
[Samsung Galaxy Nexus] bsmitty83:
Op updated SmittyV-4.17

changelog

temp_control: increase the maximum temperature threshold to 80*C

DRIVERS: MISC: Add OMAP4430 Static Thermal Policy …

add /dev/hci_tty module for userspace BT in 4.2.1 …

mmc: Fix bug to enable DDR on MMC …

mmc: OMAP HSMMC: DDR support added. …

omap: Add ION system heap to omap board file …

usb: ehci: fix the host wakeup state machine. …

rpmsg: omx: implement separate register ioctl for sgx buffers …

rpmsg-omx: Use ion abstraction to get handle from PVR fd …

rpmsg-omx: tiler_virt2phys called for 1D buffers …

rpmsg: omx: re-work buffer lookup to support contiguous NV12 …

rpmsg: omx: add return values to the pa to da convert function …

fs/fat/dir.c:43: warning: 'de' may be used uninitialized in this func… …

rpmsg: omx: initialize completion event in rpmsg_omx_open …

rpmsg: omx: send disconnect only if omx state is connected …

rpmsg: omx: fix copy_to_user in register/unregister ioctls …

rpmsg: omx: return ENXIO in rpmsg_omx_write …

rpmsg: omx: copy_from_user() errors should return -EFAULT …

rpmsg: omx: return actual user-provided bytes written in write …
[Samsung Galaxy Nexus] osm0sis:
Sweet! I'm going to rebase the ramdisk tomorrow (seemed like there were a lot of tweaks from CM lately..) and see about making you a proper pull request again. ;)

Can you let me know if you can add back LMK donotkill so all the Synapse controls are 100% working again? :)
[Samsung Galaxy Nexus] milojoseph:
To the death of me I can never reach 14000...... Only 8000
[Samsung Galaxy Nexus] HONG86:
On Carbon and LiquidSmooth, I got only 12500-12800. (1500/512)

how possible 14000?;;;

Sent from my Gnex
[Samsung Galaxy Nexus] osm0sis:
I just extracted all the OMAP4/OMAP 4460/PowerVR SGX540 libraries/drivers from the Glass XE16 Factory Image posted earlier today.

Going to see what mischief I can get into with them. ;)
[Samsung Galaxy Nexus] michierusama:
This is growing good job everyone. Have a good night. Thanks smitt
[Samsung Galaxy Nexus] HONG86:
What a great work!

I hope 3.4 :)

thx for your work bro.

Sent from my Gnex
[Samsung Galaxy Nexus] ashclepdia:
hrm...

all of the sudden i cannot get adb to connect.

shows as charging via usb, but i get no notification and adb devices doesnt show any device listed.

dunno if it's kernel related though. (yes it's enabled lol) this is first time i tried using adb since using 4.12 version, used to work before, just curios if anyone else has seen this as well before i start flashing away with different kernel versions :D

(before it's asked, no it isn't issue with my laptop, no it isn't driver needed(i use linux), and yes it worked previously...this post sint meant as any type of bug report, just asking if anyone else has this as well on smittyV4.12)
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4443334]Grarak[/MENTION]

Linux 3.4 update for glass? ?

https://android.googlesource.com/kernel/omap/+log/glass-omap-xrv15c
[Samsung Galaxy Nexus] DR3W5K1:
Update your SDK
[Samsung Galaxy Nexus] luckana:
On the latest CM11 nightly using DirtyV-R 12.04 + buscher settings - i have never ever seen my phone being so smooth and responsive and fast and etc.. It's awesome
[Samsung Galaxy Nexus] ashclepdia:
Yea that was the issue I had before when it didn't work..

Oh crap... now that I think about it, I might have not updated it since 4.4 release.

I'll try that whoopsie I hate when I do that lmao

Edit::

Damn..didn't work..

Thanks tho, I'll keep messing around
[Samsung Galaxy Nexus] luckana:
why don't the increased RAM versions of the kernel get updated ??
[Samsung Galaxy Nexus] ashclepdia:
They DO ;)

SmittyV is his personal builds.

Then if things work good for him( and whoever decides to run it) the extra ram ones get updated with the new changes.

I used to swear by extra ram kernels, until running smittyV. I feel like I have many /more video playback issue and other things with extra ram kernels...I don't see a necessity for them in my own use anymore, except "having a bigger amount" showing as free/available...I'm no longer seeing any benefit from an extra 30-50mb of ram in my usage...

SmittyV FTW! :)

But yea, they will get updated AFAIK
[Samsung Galaxy Nexus] luckana:
yea, everything depends on how you use and especially for what you use ur device. In my scenario, extra ram makes difference, that's why i am asking (sorry for OT)
[Samsung Galaxy Nexus] DR3W5K1:
They get updated if Smitty has time in between experiments updates etc.

Smitty v is more experimental dirty is based on stability (tried and true Smitty v's).
[Samsung Galaxy Nexus] ashclepdia:
Not really OT ;)

Still has to do with kernel and such, I was mainly stating that only because I used to be "hardcore" supporter of the extra ram stuffz, but found on Smitty that it wasn't a big deal to me anymore due to how well things ran with just stock values. I was definitely pleasantly surprised :) (it wasn't intended as trying to say that those versions aren't needed at all or anything like that, re-reading my post I see it reads kinda like that lol sorries)
[Samsung Galaxy Nexus] pvkiniyan95:
Happy birthday buddy [MENTION=4244313]MBQ_[/MENTION]
[Samsung Galaxy Nexus] ASHURiCAN:
Happy birthday [MENTION=4244313]MBQ_[/MENTION] ;)
[Samsung Galaxy Nexus] DR3W5K1:
Can someone enlighten me on what we stand to gain if this glass 3.4 kernel is ported.

---------- Post added at 05:57 AM ---------- Previous post was at 05:55 AM ----------

Happi berfday buddy!
[Samsung Galaxy Nexus] sym_m:
Happy birthday :)
[Samsung Galaxy Nexus] GilGameshn1:
[MENTION=4244313]MBQ_[/MENTION] ... HAPPY BIRTHDAY ...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Yea idk about the do not kill list , I'm not sure if it'll work or not , I'll try it today .
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=4608636]bsmitty83[/MENTION] I see that in new versions you don't use metalsprings toolchain. Is that permanently change?
[Samsung Galaxy Nexus] agayabag:
[MENTION=4608636]bsmitty83[/MENTION] The camera ain't working on 417 version. Reverted back to 416, it works just nice.

Don't forget to update at 20th for 420 present. Hahaha. Cheers yo
[Samsung Galaxy Nexus] cujo6801:
[MENTION=4244313]MBQ_[/MENTION]

Happy Birthday Bro...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] pvkiniyan95:
camera not working on 17/4
[Samsung Galaxy Nexus] GilGameshn1:
Even after cleaning dalvik/cache and clear app data ? Pls report back .[emoji106]

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pvkiniyan95:
Either a force close or blank screen after cache clean and clearing app data
[Samsung Galaxy Nexus] dbt816:
Here's where the camera barfs on 4/17:

I/ActivityManager( 703): Displayed com.android.camera2/com.android.camera.CameraLauncher: +1s587ms

D/DOMX (21277): ERROR: DOMX Write failed 0xffffffff -1

D/DOMX (21277): ERROR: failed check:status >= 0 - returning error: 0x81001 - Write failed

D/DOMX (21277): ERROR: RPC function returned error 0x81001

E/CameraHAL(21277): OMX_UseBuffer-0x80001001

E/CameraHAL(21277): Exiting function UseBuffersPreview because of ret 0 eError=80001001

E/ion (21277): ioctl -1073460991 failed with code -1: Bad file number

F/libc (21277): invalid address or address of corrupt block 0x61228 passed to dlfree

F/libc (21277): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 21288 (Binder_3)
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4443334]Grarak[/MENTION]

Enable OMAP RPC by default for Tesla.

http://goo.gl/ZN89S2

Update notle_defconfig to better match TI config.

http://goo.gl/lNdhBD

Setup OMAP board properties

Run the codepath to initialize the OMAP board properties. SGX drivers

need this to figure out what kind of chip you have.

http://goo.gl/6qgcGx

OMAP4: Blaze: populate board file with sgx config data

This sgx data will be needed in multi display configuration

to reflect number of framebuffers and swapchains to allocate

http://goo.gl/NI0zmt

Add multimedia ION heap

http://goo.gl/kdqTv9

Reduce ION multimedia heap size to 165mb (for 1gb devices)

http://goo.gl/dXNZ2d

Enable audio driver plus tweaks for headset

Enables and configures the omap-abe audio driver. Also includes a few

tweaks to the USB driver to allow headset detection to function.

http://goo.gl/mda7Jc

Revert "sgx_omaplfb: cleanup static configuration"

This reverts commit a33f0a13e374e7d3aa94678ec7c818f190a4bab4.

The configuration of framebuffers was moved to board files and

The default configuration was removed from OmapLFB after it.

This brokes Blaze because Blaze has no specific configuration

for OMAPLFB driver.

This revert adds a default configuration for devices which

has no a specific configuration for OmapLFB in a board file.

http://goo.gl/Y3uNms

Notle bringup on kernel 3.4

Port of Notle board file + some drivers to kernel-3.4. Things known to

function on this are the display, touchpad, wifi, adb.

http://goo.gl/wht7a3
[Samsung Galaxy Nexus] HONG86:
dalvik+cache wipe doesn't help workibg...

camera is not working on 4.17

3rd party camera app is not working too.

just go back 4.16

Sent from my Gnex
[Samsung Galaxy Nexus] cujo6801:
+1

--

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Punkiderma:
also here apps using camera crashes
[Samsung Galaxy Nexus] qu4nd:
+1

Tried some stuff like clearing data etc without success... Back to 16-4 which works pretty awesome here! Probably my new backup kernel from now on...
[Samsung Galaxy Nexus] Unzitron:
Camera crash on 4.17 too.
[Samsung Galaxy Nexus] bsmitty83:
I haven't used his toolchain in a month or so . just didn't see any gains over current linaro GCC
[Samsung Galaxy Nexus] bsmitty83:
Camera isnt working for me either . gotta look into it

Edit got it back .....
[Samsung Galaxy Nexus] Madsunable:
How did you do that

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] bsmitty83:
Magic .... Lol

I rebuilt the kernel real quick , it'll be ready for todays release .
[Samsung Galaxy Nexus] borax:
Hello can some one help me resolve this error I am running Latest Carbon kk nightly I get this error with Imperia Online game with any ROM I tried except CM ... Can any help please I read in a post to change the minfree settings but I lowered them to 0 and did not resolve the issue...any ideas???
[Samsung Galaxy Nexus] jhonnyx:
Is this error related to the kernel? doubt so. I'm running Dirty on LiquidRom - 0 issues. Not that I've got this game but.... will give it a shot.
[Samsung Galaxy Nexus] osm0sis:
Zero is very wrong-bad.

P.S. Happy birthday [MENTION=4244313]MBQ_[/MENTION]! Stay dirty. ;)
[Samsung Galaxy Nexus] ak:
Happy birthday man ... From a real friend [emoji7]

ak
[Samsung Galaxy Nexus] michierusama:
Feliz cumpleaños

Happy birthday

XD
[Samsung Galaxy Nexus] wisefreakz:
Feliz aniversario [MENTION=4244313]MBQ_[/MENTION]
[Samsung Galaxy Nexus] gabrielss:
Hi! Need help please!

I'm having lots of problems with latest smitty's 4.16. Lots of random reboots, and launcher crashes. When the phone reboots itself it appears a constant error with system.ui and if I reboot it again the error dissappears. I love this kernel and It was just fine with previous versions.

I'm running CM11 nightly. Another thing is that I just bought a new extended battery and I don't know if the problem is the new battery...

And, here it comes the newbie question.. How do I see the log file to see what happened like some of you do?

Btw, Happy birthday [MENTION=4244313]MBQ_[/MENTION]

And thanks!
[Samsung Galaxy Nexus] HONG86:
You should try 10th...

I also got error 17 and 18.

roll back

Sent from my Gnex
[Samsung Galaxy Nexus] dbh369:
[MENTION=5324641]gabrielss[/MENTION]: Download syslog from play, run it right after you see a problem, and you get a zip file with all logs; post that.
[Samsung Galaxy Nexus] ASHURiCAN:
This is not kernel related, it's CM. Having same problem without flashing Smitty kernel.
[Samsung Galaxy Nexus] gabrielss:
Ups, you're right, many people reporting the same in CM11 post.

Thanks!
[Samsung Galaxy Nexus] krweby:
Must be the same problem I'm seeing with the newest aokp nightly. Looks like the grabbed the new theme engine from cm for this build.
[Samsung Galaxy Nexus] cmoG530:
Are you using stock or a custom theme?
[Samsung Galaxy Nexus] ASHURiCAN:
Stock.
[Samsung Galaxy Nexus] sagara.sandaru:
Deleted!
[Samsung Galaxy Nexus] Unzitron:
What is a good RAB to use for tripndroid scheduler?
[Samsung Galaxy Nexus] osm0sis:
So I hear [MENTION=4443334]Grarak[/MENTION] made the kernel-side changes for our GPU that come from Glass XE16 :D
[Samsung Galaxy Nexus] wisefreakz:
Which means a 3.4 working-bootable kernel?
[Samsung Galaxy Nexus] Carlos_Manuel:
https://github.com/manumanfred/device_samsung_tuna_kernel_3.4 Some changes for 3.4 kernel.

I'm still looking for the needed changes for device repository. Hopefully he got the screen working. :)
[Samsung Galaxy Nexus] osm0sis:
We don't have the same chipset as Glass (though it's close). We do have the exact same GPU.

3.4 is still a very difficult task, but stealing some patches for our graphics performance should be easy. :good:

Oh snap!
[Samsung Galaxy Nexus] Carlos_Manuel:
Omap 4460 :3
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION]

Not expressly for our device, but this sounds awfully familiar:

http://review.cyanogenmod.org/#/c/62017/
[Samsung Galaxy Nexus] bsmitty83:
Op updated , all 3 kernels . let me know how they work as always .

Have fun .
[Samsung Galaxy Nexus] osm0sis:
Any luck? :D

I'm rebasing right now and updating Synapse stuff. :good: