yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] andQlimax:
If no dev work in it, then its probably a waste of time.. It will not give any real improvement, will only give new bugs

If you like an higher number, you can build a 3.0.x kernel, and change the version to 3.10

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] motorazrv3:
So sad. Galaxy Nexus had got such a huge community and there are no people finding together to write / create a working 3.4 linux kernel.

Before a come to the galaxy nexus world I used a similar old Sony Ericsson neo v. It was released the same year. 2011. Now they build a working 3.4.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4
[Samsung Galaxy Nexus] Sik-1:
The only reason we don't have a working 3.4 is bcuz of our ti-omap processors, it was posted here earlier somewhere, even the sensation has a working 3.4 lol I'm jealous as hell but hey, its still nowhere close to this nexus honestly ,

I suggest u try the bigmem kernels floating around and then u should get back to us an tell us if we really need a 3.4 kernel lol
[Samsung Galaxy Nexus] Pasquale91fg:
+ 1 !!!! So sad.
[Samsung Galaxy Nexus] andQlimax:
Sad because they have 3.4..So their phone make coffee now? What it does more? Nothing..

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Scandy:
I've heard a rumor, that 3.4.x kernel gives much battery life
[Samsung Galaxy Nexus] n1kolaa:
we need to fix galloric and framebuffer,thats core for make display working,also you need to add tuna display instalation and touchsreen instalation.
[Samsung Galaxy Nexus] Carlos_Manuel:
You mean gralloc?

We can't really fix it, because gralloc.omap4460.so is on the vendor files and cannot be built from sources?

framebuffer, about that I don't know really nothing.

Display:

https://github.com/Grarak/grakernel...kpot/arch/arm/mach-omap2/board-tuna-display.c
[Samsung Galaxy Nexus] aosp:
I'm trying to get the great [MENTION=4243514]Hashcode[/MENTION] to help us but have you tried the prebuilt gralloc blob from the notle image or the updated blobs from omapzoom?

http://git.omapzoom.org/kernel/omap...4d1df8a63f;hb=refs/heads/d-kitkat-mr1-release

http://git.omapzoom.org/kernel/omap...250a18f0f9;hb=refs/heads/d-kitkat-mr1-release

http://git.omapzoom.org/kernel/omap...028098dc0c;hb=refs/heads/d-kitkat-mr1-release
[Samsung Galaxy Nexus] Carlos_Manuel:
I've only tested with Google Glass XE16's pvr vendor files (SGX540_120) including needed powervr.ini, gralloc.omap4460.so, pvrsrinit, pvrsrvctl_SGX540_120 and pvrsrvkm_sgx540_120.ko module file. All other vendor files are Tuna's JB 4.3 vendor files (ducati, libbt, etc.)

The links you gave, those have .bin and/or .xem3 files which I can't extract :(
[Samsung Galaxy Nexus] aosp:
You try CONFIG_MODVERSIONS=y in the defconfig?

Try tuna with omapboot?

https://github.com/rbilovol/omapboot/commits/ruslan-p-master-dev-panda5

https://github.com/omapconf/omapconf

https://github.com/swetland/omap4boot

Check out these patches

Panda4: Bringup on K3.4

Add back /sys/board_properties.

Add information about all GPIO's used by HDMI.

Configure VRAM and FBs in new way.

Separate registration of EDID eeprom.

http://review.omapzoom.org/#/c/32424/

[MENTION=5747201]isrcepeda[/MENTION] Patches for panda

OMAP4: Panda: Adding board version and ID · dfde981 · icepeda/omap · GitHub - http://goo.gl/a1540t

Panda: Updating board and clean up · d5bc5a4 · icepeda/omap · GitHub - http://goo.gl/gMitGE

Panda: Updates for ducati and display · d1c8a0d · icepeda/omap · GitHub - http://goo.gl/lgs3p1
[Samsung Galaxy Nexus] Grarak:
[MENTION=4022928]Carlos_Manuel[/MENTION]

Try the blobs with jackpotclavin's kernel
[Samsung Galaxy Nexus] lovejoy777:
if i remember Hashcode rewrote those files from scratch for the kindle omap 4430. he had nothing but uart output
[Samsung Galaxy Nexus] ashclepdia:
We should hit up TI and ask nicely for source access for gralloc and ducati sources since they aren't doing anything with em anymore

Edit::

After searching a while, it seems that reaching out to TI might not be what we would need for sources, it is GPU stuffz we need so contacting the people who made the powerVR sgx540 (isn't it imgtec or something like that?) Would need to be done if we wanted sources. I don't think TI is authorized at all to give the sources for the GPU stuff due to licensing terms. I wish companies would just straight up open source everything once they determine it is EOL and do not provide updates for it. Especially on so-called development devices/platforms...okay I'll stop clogging thread with my nonsensical posts and let the real devs get to... sorry
[Samsung Galaxy Nexus] aosp:
[MENTION=4022928]Carlos_Manuel[/MENTION]

http://omappedia.org/wiki/Android:_Working_with_pre-built_binaries

http://omappedia.org/wiki/4AJ.2.2_OMAP4_Jelly_Bean_Panda_Notes#Building_SGX_driver

Ducati binaries updated to 4AJ.2.5p1 release version

Ducati binaries for blaze_tablet and blaze devices

updated to version 2.1.21

http://goo.gl/eiILYk

Rebuilt sgx binaries required because of a kernel change that requires sgx to be rebuilt.

Tag for sgx build: 084d3dbdab598dfdf1d2497a3fded3b833284fa9

http://goo.gl/Ed5C2A

http://omappedia.org/wiki/4AJ.2.5P2_OMAP4_Jelly_Bean_Release_Notes

L4AJ.2.5P2 Jelly Bean MR1 git history changelog

http://goo.gl/7Wo3FD
[Samsung Galaxy Nexus] n1kolaa:
you cant only update kernel,you also need to make changes in rom,like updating vendor and updating phone cammon and other thing.Im busy in those day i will be after may end,then hollyday start and i will be 2,half mounts free.
[Samsung Galaxy Nexus] Carlos_Manuel:
I din't only "update" "the kernel" If you have read the last pages posts then you understand. I have edited ramdisk for 3.4 kernel and for PVR.

I have only changed required vendor files (PVR SGX) and not any other like libbt which is for BT... I have ported ROMs to my samsung Jét and I am not so stupid to only change kernel... :)

[MENTION=4443334]Grarak[/MENTION] Sure, I'll download his kernel source and then I'll start building :) but should I edit defconfig to use omaplfb, omapdss, or somehting like that? I'm afraid those SGX_120 files on Glass's XE16 system, are only for OMAP4430 and are not compatible with OMAP 4460? and that can also be the reason why screen won't work. But I'm not sure.

---------- Post added at 09:26 PM ---------- Previous post was at 09:23 PM ----------

Thanks, I try, if I can do something with those. :)
[Samsung Galaxy Nexus] aosp:
OMAPzoom is the only source that truly supports our chipset a built ROM from omapzoom for the tuna would be awesome ?
[Samsung Galaxy Nexus] nikodr:
I tried to find out any explainations regarding omap 4430 vs 4460

http://www.ti.com/general/docs/wtbu...ntId=53243&navigationId=12843&templateId=6123

Here it seems only the frequency is different.

http://armdevices.net/2011/10/26/interview-with-the-texas-instruments-omap4-team/

interview from the omap4 teams says that

"Both the OMAP4430 and OMAP4460 processors are clocked at 1.2GHz in recently announced devices, the Droid RAZR and Samsung Galaxy Nexus respectively. Experiences are fairly consistent with both clock speeds, but the 1.5GHz gives an extra boost. The main upgrades to the OMAP4460 processor are an increased GPU performance and improved external memory access performance."

So that means that drivers for 4430 would work on the 4460 ?I assume the only difference would be gpu speed and memory access but i could be wrong?
[Samsung Galaxy Nexus] aosp:
https://android.googlesource.com/kernel/omap/+log/glass-omap-xrv16

Now that's a small update still nothing here

https://developers.google.com/glass/tools-downloads/system

http://androidcentral.com/google-glass-updated-xe161-no-noticeable-changes
[Samsung Galaxy Nexus] pattyboi:):
i think there is something different with the iva chips as well because only the 4430 supports DPLL cascading which is like a lower power level for audio output and its only decently effective on the 4430 according to the omap and google guys
[Samsung Galaxy Nexus] Carlos_Manuel:
(Y)

anyway. If I understood right, then changing duacti-m3.bin into ducati-m3-core0.xem3 should be enough? As init.*.rc doesn't need any changes for that file.

About Building SGX driver, I don't know. Someone else has to do it. I try some stuff and hopefully I can make something useful.
[Samsung Galaxy Nexus] aosp:
Yes renaming it should be ok and you don't have to build the sgx and gralloc modules prebuilt blobs can be found in this archive

Rebuilt sgx binaries required because of a kernel change that requires sgx to be rebuilt.

Tag for sgx build: 084d3dbdab598dfdf1d2497a3fded3b833284fa9

http://goo.gl/Ed5C2A
[Samsung Galaxy Nexus] ashclepdia:
I thought iva was image video accelerator, it also handles audio?
[Samsung Galaxy Nexus] bsmitty83:
I have successfully built the sgx module in the past , but my recent attempts haven't gone as well . I was going to try to get a 3.0 kernel working with the new drivers as I have tried before, but idk .
[Samsung Galaxy Nexus] Carlos_Manuel:
One thing is that, those pvr, sgx, hal bin files doesn't exits on Google Glass's XE16 system and currently I am using its pvr files. I think there's no need to use Glass's hwcomposer.omap4, when it gets built from android sources. If someone wants to try those sgx binaries, then I can upload my ROM. :D

As this is going pretty confusing for me

---------- Post added at 10:27 PM ---------- Previous post was at 10:22 PM ----------

If you try to use omaplfb instead of PVR drivers on the kernel, then it may work. :)

Tuna's kernel may not have omaplfb (drivers/video/omap2??/omaplfb??/...), but Gloogle Glass's 3.0.xx kernels have it. By using that, those newer drivers should work? At least it is worth to try :)

Edit: 3.4 kernel only has omaplfb, maybe it's easily backport-able to 3.0
[Samsung Galaxy Nexus] bsmitty83:
I did use omap lfb , you have to to build the SGX module As it links up with the kernel source . but I'll try again , last time I did pretty much what you are doing now but I probably left something out . but recently when I try , the module errors out during the CC .

Tuna kernel Does have the beginnings of omaplfb , check gpu/pvr of a 3.0 tuna source . its not nearly as developed , but its there .
[Samsung Galaxy Nexus] Carlos_Manuel:
Ok

yeah :)

What do you thing about this?:

https://github.com/manumanfred/grakernel-tuna/commit/12753f73f664ce6f47b1fcb45936835cb6d87584

As I included these from Glass's init.<device>.rc, so then also kernel needs those?

# Wait for RPMSG to properly come up before bringing up the SGX module
wait /dev/rpmsg-omx0
wait /dev/rpmsg-omx1
[Samsung Galaxy Nexus] pattyboi:):
i believe so,as for a kernel for the droid razr it has iva overclock to help with audio issues in apps with alot of audio processing and hdmi output
[Samsung Galaxy Nexus] Grarak:
This won't boot neither

I've tested almost everything
[Samsung Galaxy Nexus] aosp:
[MENTION=4022928]Carlos_Manuel[/MENTION] Can you grab a dmesg instead of the logcat and post it here please
[Samsung Galaxy Nexus] Grarak:
He already posted both
[Samsung Galaxy Nexus] aosp:
[MENTION=4443334]Grarak[/MENTION] Can you try booting with a build using CONFIG_MODVERSIONS=y please
[Samsung Galaxy Nexus] JackpotClavin:
You guys should try building a recovery image and work on getting the panel to initialize. Once you get TWRP or CWM to display, you should try with a legitimate boot image. The issue is not with the 3D graphics or ducati or any proprietary binary.

I would help out but I have no time
[Samsung Galaxy Nexus] blmvxer:
I've been following this thread for awhile. I'm very proud of everyone helping out to make a 3.4 kernel a reality for this device. I'll download the sources and try to do some good myself for the community.

Good job everyone!!!
[Samsung Galaxy Nexus] boype:
Obviously(?), this is the issue:

[ 0.356933] omapdss DSI error: can't get VDDS_DSI regulator
[ 0.356933] omapdss DISPLAY error: failed to init display lcd

I suppose modifying /drivers/video/omap2/omapfb/omapfb-main.c to make omapfb initialize later could help (source):

So what you have to do is this: Replace

late_initcall(omapfb_init);

with

late_initcall_sync(omapfb_init);

and see if that's any good
[Samsung Galaxy Nexus] aosp:
[MENTION=4615478]boype[/MENTION] Welcome aboard brother ✊
[Samsung Galaxy Nexus] matoushybl:
Hi, first of all thanks for your effort in keeping gnex alive I really appreciate it. I am not a dev, but why is memtotal in /proc/meminfo showing just about 500 MB of RAM, is it because the graphics consumes a lot of memory? Thanks
[Samsung Galaxy Nexus] aosp:
[MENTION=4615478]boype[/MENTION] Hit me up on g+ when you can dude ?
[Samsung Galaxy Nexus] Shidell:
Just a thought, related to initializing the display: Could this error be related to the fact that the GNex 4460 has two possible outputs (LCD and HDMI), whereas the Nolte 4430 has one? (LCD)?
[Samsung Galaxy Nexus] Carlos_Manuel:
It can be possible but I don't think that's the problem. I can upload my ROM and then you guys can try to use different pvr libaries.:) as I am not going to try any other pvr libraries, modules, etc
[Samsung Galaxy Nexus] Grarak:
This doesn't help at all

replacing modules randamly won't do anything, if the kernel doesn't initialize the display.

as JackpotClavin said before, build a recovery with the kernel. If the recovery works, then it means the display works as well.
[Samsung Galaxy Nexus] aosp:
Ok so who wants to start a bounty thread to help get ti dev [MENTION=5747201]isrcepeda[/MENTION] a Galaxy Nexus so he can help us on our quest for awesome? Seriously a TI dev is willing to help out the tuna nation but he needs the phone in hand to be productive so anybody that can truly help make this happen please don't hesitate to contact him asap thanks ✊ Viva LA OMAP4!
[Samsung Galaxy Nexus] ILA:
Make a thread that has a good description for what it's goals are. There is a thread and a phone free in the general section, but the thread isn't clear, so nobody is willing to help or even look at it. Maybe you should also make a thread in this section as well with a link to that tread so that everyone gets the news (general and dev thread) :)

Here's the thread:

http://xdaforums.com/galaxy-nexus/general/devs-make-happen-t2717611
[Samsung Galaxy Nexus] aosp:
They was a reason why I asked if somebody was willing to create the thread buddy but the goal is simple update the Galaxy Nexus device and kernel source so the tuna can utilize improvements from kernel.org and omapzoom.org like longer battery life, smarter enhanced memory management, improved graphics performance, multimedia enhancements, true project butter etc...
[Samsung Galaxy Nexus] jhonnyx:
[MENTION=2838735]aosp[/MENTION]

that was already done, please check

http://xdaforums.com/galaxy-nexus/d...el-looking-t2071021/post52080509#post52080509

and the next post.

Now we need to know if the user has PM'd isrcepeda back ;)

[MENTION=5747201]isrcepeda[/MENTION], sir, have you received some feedback from that guy?
[Samsung Galaxy Nexus] ILA:
Yeah, missed the "somebody" part. Seen it after I posted, sry about that... But your response would be the perfect description for the thread! :D

Anyway, hope that isrcepeda got a reply and that there won't be a need for a new thread :)
[Samsung Galaxy Nexus] isrcepeda:
No reply at all :(
[Samsung Galaxy Nexus] ILA:
Strange, the guy is online now... :confused:
[Samsung Galaxy Nexus] isrcepeda:
Got a reply :) we are sharing shipment info. Hope to get it soon
[Samsung Galaxy Nexus] pianistaPL:
Oh, i'm lovin it <3
[Samsung Galaxy Nexus] jhonnyx:
alrighta!
[Samsung Galaxy Nexus] aosp:
It's destiny fellas ✊
[Samsung Galaxy Nexus] dirtyreturn:
Sorry for the threads lack of description. [MENTION=5747201]isrcepeda[/MENTION] check your PM . Phone's dropped off at the post office.
[Samsung Galaxy Nexus] isrcepeda:
Thank you [MENTION=4217078]dirtyreturn[/MENTION] you rock :)
[Samsung Galaxy Nexus] wisefreakz:
I'm having those tingling sensations.... Lol VIVA LA OMAP4
[Samsung Galaxy Nexus] aosp:
S*** is getting real ?
[Samsung Galaxy Nexus] pattyboi:):
i forreal just did a backflip....pumped as hell for this :good:
[Samsung Galaxy Nexus] TheMan0790:
I...ehrm...released some bodily fluids just now...
[Samsung Galaxy Nexus] pattyboi:):
you should get that checked out
[Samsung Galaxy Nexus] mknrls:
Daam you devs are amazing :p u guys should probably create a new tread with better explanation of what happening, all the things working ect, the issuse and what have been fix. Just to make more clean for everyone or new devs that would like to join and see the progress ect lol.I would volunteer to do so :) if u guys wanted
[Samsung Galaxy Nexus] mknrls:
Lool just trying to help haha
[Samsung Galaxy Nexus] wisefreakz:
I know man!!! That was just a fun moment I couldn't avoid!!!

Cheers
[Samsung Galaxy Nexus] AbhishekS:
Sorry for a post that doesn't contribute anything to the development. Just wanted to pop in and say on behalf of all the Galaxy Nexus users that we LOVE ALL OF YOU. Devs like you make this community so strong and wonderful!
[Samsung Galaxy Nexus] boype:
[ 0.367523] could not allocate tiler block

Now the issue seems to be that no memory can be allocated to the gfx subsystem(s).

The method that was used in the tuna 3.0 kernel to allocate the static memory carveouts has been replaced in several commits. If I find some time, I'll look out for those commits in the omapzoom repo.

I'm sorry I lack the time to support the 3.4 development more actively.

P.S.: When we get the display working, porting all the other tuna specific drivers should not be be a big issue. It just takes some time. However, getting the display working is still a big 'if' in my personal opinion.

[edit]

I have just seen the DSI regulator still throws errors at us :/
[Samsung Galaxy Nexus] aosp:
Please check out the display commits I linked a few posts back from [MENTION=4243514]Hashcode[/MENTION] 3.4 bring up when you have a chance ?
[Samsung Galaxy Nexus] boype:
Alright, those commit might actually help with getting the display working.

However, I just had a look on the state of the 3.4 kernel source that is used for the current development here. It just misses so many necessary commits from the 3.0 tuna kernel that we're not even close to bringing up the display :( Most of the code for display initialization has been cut or commented out, so there's the reason for various error messages in the log. Don't mistake my words for for some sort of criticism, I'm just trying to analyze what's going on
[Samsung Galaxy Nexus] aosp:
The one linked in the op or [MENTION=4443334]Grarak[/MENTION] latest attempts?

https://github.com/Grarak/grakernel-tuna/commits/glass-omap-xrv15c
[Samsung Galaxy Nexus] Grarak:
https://github.com/Grarak/grakernel-tuna/tree/glass-omap-xrv15c-jackpot
[Samsung Galaxy Nexus] aosp:
https://android.googlesource.com/kernel/omap/+log/glass-omap-xrv22
[Samsung Galaxy Nexus] n1kolaa:
maybe some of those parts form old display.c will help us to make it bootable :)

LEFT SIDE IS NEW display.c,RIGHT SIDE OLD tuna display.c driver.

http://www.diffchecker.com/baq51sds
[Samsung Galaxy Nexus] aosp:
start pvr early · e22f010 · KFire-Android/android_device_amazon_otter · GitHub - http://goo.gl/nYTdns
[Samsung Galaxy Nexus] Carlos_Manuel:
Cool, Thanks. :)
[Samsung Galaxy Nexus] aosp:
Fix issue when passing mem size via bootargs. · 7c4903c · Grarak/grakernel-tuna · GitHub - http://goo.gl/RKtlXu
[Samsung Galaxy Nexus] wisefreakz:
Did [MENTION=5747201]isrcepeda[/MENTION] receive the phone?
[Samsung Galaxy Nexus] aosp:
He should be receiving it tomorrow
[Samsung Galaxy Nexus] cujo6801:
Yes he did..

I saw it up on ebay today.... :eek::p:D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] wisefreakz:
Cha Chin
[Samsung Galaxy Nexus] isrcepeda:
No yet, it is in transit, expecting delivery tomorrow :)
[Samsung Galaxy Nexus] nikodr:
We are all waiting for any status updates :)

Hope good news or boot pictures will be with us soon ;)
[Samsung Galaxy Nexus] aosp:
http://59.124.231.13/index.php/How_to_Replace_Ducati_Firmware_Image_In_Jorjin_OMAP4_APM

Panda4: Bringup on K3.4

Add back /sys/board_properties.

Add information about all GPIO's used by HDMI.

Configure VRAM and FBs in new way.

Separate registration of EDID eeprom.

http://goo.gl/tExySz

Panda4: device specific configuration to run on K3.4

http://goo.gl/aOBHtm

panda: Enable TI features

http://goo.gl/xTui0M
[Samsung Galaxy Nexus] aosp:
ARM: DTS: OMAP4 BlazeTablet: change kernel command line for Android · b485eb2 · rbilovol/kernel · GitHub - http://goo.gl/vTTMW0

OMAP4: DSS: Add panel for Blaze Tablet boards · 6f81180 · rbilovol/kernel · GitHub - http://goo.gl/DOZXA2

OMAP4: DSS: TC358765: add DeviceTree support · 37fe559 · rbilovol/kernel · GitHub - http://goo.gl/n2sC8T

ARM: OMAP4: Add OMAP4 Blaze Tablet support · ddb090f · rbilovol/kernel · GitHub - http://goo.gl/gV3wiX

ARM: OMAP4: BlazeTablet: Add display support. · 88f6c6d · rbilovol/kernel · GitHub - http://goo.gl/uffUDp

ARM: DTS: OMAP4 BlazeTablet: mux fref_clk4_out for display panel support · 8e785d9 · rbilovol/kernel · GitHub - http://goo.gl/byIyf9

ARM: DTS: OMAP4 BlazeTablet: add toshiba panel driver binding · d3ce42c · rbilovol/kernel · GitHub - http://goo.gl/jJ8fU1

HACK: OMAP4: BlazeTablet: make omapconf happy by shifting i2c busses · b7f8939 · rbilovol/kernel · GitHub - http://goo.gl/QXhUJV

blaze_tablet: Switch to upstreamed OMAP4 Blaze Tablet DT machine name. · bda11ee · rbilovol/device-ti-blaze_tablet · GitHub - http://goo.gl/BFP5Hj

eurasia_km: fixes for 3.8 · f283130 · rbilovol/eurasia_km · GitHub - http://goo.gl/IOWwOV

blaze_tablet: enable device tree booting · d0321e4 · rbilovol/omapboot · GitHub - http://goo.gl/gxX8Wx

init: add support for DT · d5252af · rbilovol/platform-system-core · GitHub - http://goo.gl/pP9Xxe
[Samsung Galaxy Nexus] aosp:
PowerHAL: Rename functions and variables to blaze_tablet

Blaze Tablet PowerHAL is copied from Tuna's PowerHAL

with the Tuna's functions and variables names.

The patch basically does s/tuna/blaze_tablet/

Also it replaces a few tab indentations by spaces.

http://goo.gl/0X9Nb9
[Samsung Galaxy Nexus] isrcepeda:
Gnex received :) starting to get hands on code now
[Samsung Galaxy Nexus] pattyboi:):
gods speed buddy ;)
[Samsung Galaxy Nexus] gh0stslayer:
and so it begins [emoji2]
[Samsung Galaxy Nexus] wisefreakz:
May the force be with you!
[Samsung Galaxy Nexus] aosp:
I'm happy that is all ?
[Samsung Galaxy Nexus] Utkarsh-ezzo:
OMFG.... you guys are really doing great.....awesome you guys are

...

missing all this already...

ezzo
[Samsung Galaxy Nexus] pianistaPL:
You can always send me Nexus 4 and buy GNex again :cool:
[Samsung Galaxy Nexus] Utkarsh-ezzo:
lol

ezzo
[Samsung Galaxy Nexus] wisefreakz:
Is this silence bad or good?
[Samsung Galaxy Nexus] pattyboi:):
shhhh....listen...hear that? thats the sound of progress my friend,all will be heard in fair time :D ;)
[Samsung Galaxy Nexus] ashclepdia:
Yea, a moment of silence right now to me only means that work is being done. Can't work and post at same time ;)

And most don't like to post update about incomplete works :)

We all must just have faith.

Even if nothing happens from this, the effort and time is appreciated highly!

---------- Post added at 02:41 PM ---------- Previous post was at 02:40 PM ----------

If updated kernel is pushed to git over dial-up modem...does it make a sound still? Lol sorry that was dumb... Couldn't resist it though
[Samsung Galaxy Nexus] pattyboi:):
if over dial up.you will hear the sound of dying baby seals lol
[Samsung Galaxy Nexus] ashclepdia:
And crying pandas too!

Okay... sorry devs..enough OT from ash lol