yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jhonnyx:
Neh, just my two cents. I prefer the "nightly" style.

There are people who:

-Likes to remain stable and rock solid (stable)

-Likes to get updated over the latest fashion-able software (testing)

-Likes to sail on uncharted waters (experimental)

You're on stable and I'm on testing.

I get the point, you prefer to have something that works pretty stable regarding the benefits of having the latest update.

Regardless of that, most of the people are on the bridge of testing without knowing.

I like to test stuff, I respect your point of view, but Kinda of liked the way I can get easily off-the-topic.

Sorry dude :)
[Samsung Galaxy Nexus] bsmitty83:
Tuna kernel is far from optimized . compare a stock tuna branch to a stock 3.0 git from say omap zoom and you'll see how far behind our stuff is .

Moving up to 3.4 would have lots of long term benefits .

Hey we gotta start somewhere , of course the first images won't be great but again long term this would be huge .

And as for the why ? That's easy ...... Because . [emoji14]
[Samsung Galaxy Nexus] pattyboi:):
well,the guy i know at school,he did work with software dealing with 4460's in general,he wouldnt tell me much else tho cause he was busy..one more thing he told me tho:

he did alot of stuff with omap zoom...he said he will talk to me tomorrow during my study hall,ill let you guys know if he has anything useful to send our way...
[Samsung Galaxy Nexus] ScardracS:
In your scale i'm an experimental loool :)
[Samsung Galaxy Nexus] bsmitty83:
Can you get him on g+ or xda??
[Samsung Galaxy Nexus] pattyboi:):
nah,hes not the social kind of guy,thats the 2nd thing i asked him,ill get his email tomorrow :good:
[Samsung Galaxy Nexus] isrcepeda:
Hi, just wondering if the new thread to get resorces to get gnex was open. I may get my oldone but need to wait to get it from my family but it might be in december :(
[Samsung Galaxy Nexus] thoiloidainhan:
OK so now we have a phone and the dev has expressed his interest. Can we get this thing rolling???
[Samsung Galaxy Nexus] aosp:
[MENTION=4179234]trevd[/MENTION] [MENTION=4636351]Quallenauge[/MENTION] [MENTION=4243514]Hashcode[/MENTION] [MENTION=5747201]isrcepeda[/MENTION] [MENTION=2875964]dhiru1602[/MENTION] [MENTION=4307430]n1kolaa[/MENTION] ?

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] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4443334]Grarak[/MENTION] ??
[Samsung Galaxy Nexus] Ashutos1997:
Can you give a link of this kernel (3.4) and can I test it now in my gnex ? Just asking.
[Samsung Galaxy Nexus] HONG86:
Those are 'google glass' 3.4 kernel.

Just same omap device...not for use Gnex...

so wait a great work :)

Sent from my Gnex
[Samsung Galaxy Nexus] Enter The Nexus:
You know TMo pays off the ETF, right? You could switch to TMo without worries.
[Samsung Galaxy Nexus] bsmitty83:
The source isn't any different than ozoom 3.4

I like that they named the board "nolte" ........[emoji44]

I pulled the source a few days ago

Edit , there are a bunch of differences they did to make it work for a phone and not a tablet . this could be interesting ........
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION]

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
[Samsung Galaxy Nexus] MBQ_:
trying to convince my mom to switch :) lol
[Samsung Galaxy Nexus] Culex316:
Lo

Awesome. Will reducing the ION multimedia heap mean more free user space RAM without having to resort to hackery like with SuperRAM kernels?
[Samsung Galaxy Nexus] aosp:
Linux 3.4 has alot optimizations for better ram management so no hackery will be needed yes ?

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 allocatehttp://goo.gl/NI0zmt

Add multimedia ION heaphttp://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] Ashutos1997:
Can we get a stable 3.4 kernel ?
[Samsung Galaxy Nexus] Shidell:
Google Glass was just updated to 4.4, as well as kernel 3.4, and is using the TI OMAP 4430 chipset--basically a lower-clocked 4460, which the GN uses.

Might we be able to use this to our benefit for 3.4 kernel and/or driver purposes?

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

EDIT: Nevermind, I didn't know that Notle was the code name for Glass.
[Samsung Galaxy Nexus] Grarak:
You don't say?
[Samsung Galaxy Nexus] ILA:
1. Can we use any of the nolte board files for our maguro and are they helpfull for us at all?

2. Does nolte have the same GPU (SGX540) as our maguro since they do have similar chipsets. If so, this can be very usefull for us, right?
[Samsung Galaxy Nexus] jhonnyx:
in Will Ye we trust. Hope you can get good results from your research!
[Samsung Galaxy Nexus] Carlos_Manuel:
Would be nice to get the screen working, so I could try to do something, but unfortunately I can't do really anything with kernels...

I knew this copy/paste method won't work, but I just wanted to see what kind of errors will it give. Isn't there currently any hackish way to make screen working?

CC drivers/gpu/pvr/omaplfb/omaplfb_displayclass.o
/home/carlos/android/system/kernel/samsung/tuna/drivers/gpu/pvr/omaplfb/omaplfb_displayclass.c: In function 'ProcessFlip':
/home/carlos/android/system/kernel/samsung/tuna/drivers/gpu/pvr/omaplfb/omaplfb_displayclass.c:1023:3: error: implicit declaration of function 'ProcessFlipV1' [-Werror=implicit-function-declaration]
/home/carlos/android/system/kernel/samsung/tuna/drivers/gpu/pvr/omaplfb/omaplfb_displayclass.c: In function 'OMAPLFBInitFBDev':
/home/carlos/android/system/kernel/samsung/tuna/drivers/gpu/pvr/omaplfb/omaplfb_displayclass.c:1224:14: error: 'OMAPLFB_FBINFO' has no member named 'psIONHandle'
/home/carlos/android/system/kernel/samsung/tuna/drivers/gpu/pvr/omaplfb/omaplfb_displayclass.c: In function 'OMAPLFBDeInitFBDev':
/home/carlos/android/system/kernel/samsung/tuna/drivers/gpu/pvr/omaplfb/omaplfb_displayclass.c:1301:17: error: 'OMAPLFB_FBINFO' has no member named 'psIONHandle'
/home/carlos/android/system/kernel/samsung/tuna/drivers/gpu/pvr/omaplfb/omaplfb_displayclass.c:1303:3: error: implicit declaration of function 'ion_free' [-Werror=implicit-function-declaration]
/home/carlos/android/system/kernel/samsung/tuna/drivers/gpu/pvr/omaplfb/omaplfb_displayclass.c:1303:12: error: 'gpsIONClient' undeclared (first use in this function)
/home/carlos/android/system/kernel/samsung/tuna/drivers/gpu/pvr/omaplfb/omaplfb_displayclass.c:1303:12: note: each undeclared identifier is reported only once for each function it appears in
/home/carlos/android/system/kernel/samsung/tuna/drivers/gpu/pvr/omaplfb/omaplfb_displayclass.c:1303:37: error: 'OMAPLFB_FBINFO' has no member named 'psIONHandle'
cc1: some warnings being treated as errors
CC fs/proc/kmsg.o
make[5]: *** [drivers/gpu/pvr/omaplfb/omaplfb_displayclass.o] Error 1
[Samsung Galaxy Nexus] Grarak:
I made a 3.4 kernel based on notle source which is buildable

https://github.com/Grarak/grakernel-tuna/commits/glass-omap-xrv15c

I didn't test it yet

if you want to build use tuna2_defconfig
[Samsung Galaxy Nexus] pattyboi:):
holy ****
[Samsung Galaxy Nexus] Grarak:
Well as I expected, doesn't boot, because gpu drivers are missing right now

I will try to get an usb connect

but first I gonna sleep
[Samsung Galaxy Nexus] jhonnyx:
while Garak sleeps, xda universe moves... well... at least xD

thanks Garak!
[Samsung Galaxy Nexus] Maromi:
ddk 1.12 2701748?
[Samsung Galaxy Nexus] wisefreakz:
Finger crossed!!
[Samsung Galaxy Nexus] Culex316:
Cool, so I assume this stuff has not been backported to the 3.0+ Linux kernel yet or requires the 3.4 base somehow..
[Samsung Galaxy Nexus] pattyboi:):
not necessarily,those commits are things that "may" help us get a 3.4 kernel to graphically function. like as grarak said,it boots,but there is no display at all,those commits are for a device with the same chipset so we have a reference to set the 3.4 kernel for our needs
[Samsung Galaxy Nexus] Carlos_Manuel:
I don't know if these can help in any way to get display working:

http://listas.gnu.org.ve/pipermail/powervr-devel/2012-September/000036.html

http://git.goldelico.com/?p=gta04-k...961da81145bee45c5f87aa1649094bd437a8c;hb=HEAD
[Samsung Galaxy Nexus] aosp:
Negative

[MENTION=4544860]osm0sis[/MENTION]

Could you make a proper extracted boot and system image from the xe16 factory images and link me please ?

https://dl.google.com/glass/xe16/glass_1-img-1124447.zip

https://dl.google.com/glass/xe16/boot.img
[Samsung Galaxy Nexus] osm0sis:
I only extracted the libraries the other night and then deleted, but here's how I do it:

http://xdaforums.com/showpost.php?p=28181832&postcount=2 (bottom of the first paragraph) for system.img

http://v.ht/AIK- for boot.img

Go ahead. Pretty straightforward. :good: :)
[Samsung Galaxy Nexus] Carlos_Manuel:
But what about this?:

board_notle.c

static struct sgx_omaplfb_config notle_omaplfb_config[] = {
{
.tiler2d_buffers = 2,
.swap_chain_length = 2,
}
};

static struct sgx_omaplfb_platform_data notle_omaplfb_plat_data = {
.num_configs = 1,
.configs = notle_omaplfb_config,
};

defconfig: this and some other lines...

CONFIG_OMAPLFB=y

Damn, it sucks when I don't really know nothing about kernels and only thing what I can do with it is only some minor modifications and copy+paste.
[Samsung Galaxy Nexus] pattyboi:):
i feel you bro
[Samsung Galaxy Nexus] cujo6801:
Pervert....... :eek::D:p

Sent from the "DOG" pound
[Samsung Galaxy Nexus] pattyboi:):
coming from the guy with the "boobs Xl" live wallpaper xD
[Samsung Galaxy Nexus] Carlos_Manuel:
I just saw that Grarak reverted PVR and changed it to omaplfb from his modified glass-omap-xrv15c kernel... So... With those things I was somehow right.Today at morning I tried to use lfb but I just got errors and I didn't know how to fix them. Hopefully Grarak will get it working. :3
[Samsung Galaxy Nexus] nikodr:
What about usb connection?Despite missing gfx does it work?Can we assume that there is something that boots despite no gfx?
[Samsung Galaxy Nexus] ILA:
Adb should work, only no display and other stuff AFAIK
[Samsung Galaxy Nexus] nikodr:
So is there a compiled zip for us to test that new 3.4 kernel with all that stuff that has been discovered?Would love to see the adb outputing something from within
[Samsung Galaxy Nexus] Carlos_Manuel:
Here's Google Glass's imgtec vendor files for tuna with kernel 3.4, if Grarak's kernel works with omaplfb:

http://www.upload.ee/files/4011578/imgtec-tuna-kernel3.4.zip.html

Here is the changes for init.tuna.rc:

These changes to init.rc:

SGX module loading...

service pvrsrvinit /vendor/bin/pvrsrvinit

Remove pvrsrvctl There's one typo :P line 11

uevetnd.tuna.rc:

For PVR

EDIT:

I was building Grarak's 3.4 kernel, but some errors came:

make[2]: *** [.tmp_vmlinux1] Error 1

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory `/home/carlos/android/system/kernel/samsung/tuna'

make: *** [TARGET_KERNEL_BINARIES] Error 2

make: *** Waiting for unfinished jobs....
[Samsung Galaxy Nexus] Grarak:
You have to provide the full log
[Samsung Galaxy Nexus] Grarak:
you have to use tuna2_defconfig

and it won't boot anyway
[Samsung Galaxy Nexus] Carlos_Manuel:
Whoops, I forgot to save BoardConfig.mk. :D My bad.
[Samsung Galaxy Nexus] ILA:
Ok, so as you can see from the he post above, it won't boot, and ofc there is no .zip
[Samsung Galaxy Nexus] nikodr:
Actually i am not looking for boot and to access android but for a way to communicate to and from the phone with adb,i suppose having a kernel that usb debug works will make things easier later right?

I want to use adb from terminal and see if the kernel will allow the adb to understand that a phone exists
[Samsung Galaxy Nexus] Carlos_Manuel:
If anyone is interested of trying anything, then here's boot.img (AOSPA sources, Grarak's 3.4 kernel with my modifications for init.tuna.rc and ueventd.tuna.rc for pvr files..) Check an attachment.

I built the kernel and my ROM and I also included those vendor files from Google Glass to my ROM:

What happened when I booted:

first Google splash screen appears, after 3 - 5 seconds screen shows lines and screen goes blank. Nothing is showed and when I press buttons, nothing happens..

The vendor files and pvrsrvkm_sgx540_120 module should be needed. http://xdaforums.com/showpost.php?p=52037120&postcount=1144

What I can try to do is to try porting Google Glass's system to Tuna and then with that I can try to use this kernel, but I don't think that this would help anything.

Guys do some magic please :D
[Samsung Galaxy Nexus] Grarak:
You can add many things as you want, aslong the kernel doesn't boot up, nothing will happen
[Samsung Galaxy Nexus] Carlos_Manuel:
Mmhh... Ok. :/
[Samsung Galaxy Nexus] aosp:
[MENTION=4443334]Grarak[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] Have you guys checked out this tuna 3.4 repo?

https://github.com/smaeul/kernel_samsung_tuna
[Samsung Galaxy Nexus] Grarak:
Same repo as jackpotclavins
[Samsung Galaxy Nexus] Carlos_Manuel:
is it a good idea to try mske omaplfb working on tuna 3.0 kernel and if that can be done successfully then at least we know it's not omaplfb which breaks booting on 3.4 mernel..?. I'm on phone so there might be somne typos
[Samsung Galaxy Nexus] Grarak:
Good news

After merge the notle kernel with jackpotclavin's source

I got a signal

Linux version 3.4.83-gc2f69b7 (willi@ilovegrarak) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #4 SMP PREEMPT Sun Apr 20 13:52:02 CEST 2014

thanks again JackpotClavin!

source is on my github

gettings logcat doesn't work same problem as jackpotclavins kernel, but the 3.0 kernel at the same stage can get a logcat

probably the kernel can't initialize the partitions

here is the kmsg

http://pastebin.com/xteCEqzw
[Samsung Galaxy Nexus] nikodr:
Thank you.

I suppose these messages near the end mean that kernel initializes the usb correctly?

<6>[ 25.611724] android_work: sent uevent USB_STATE=CONNECTED

<6>[ 25.622344] gadget: high-speed config #1: android

<6>[ 25.627532] android_work: sent uevent USB_STATE=CONFIGURED
[Samsung Galaxy Nexus] JackpotClavin:
Try making a recovery image with the kernel and see if the panel works
[Samsung Galaxy Nexus] nixholas:
Nope. Nothing.

I've made changes to the GPU drivers, but i dare not release it yet. Still stuck at booting. There are flickers on my side though
[Samsung Galaxy Nexus] ScardracS:
So now i have ubuntu 14.04... If you want i can help you :)
[Samsung Galaxy Nexus] thagringo:
well done !!

kenel apparently detects the hardware and its partitions :

<6>[ 2.969055] mmc0: new high speed MMC card at address 0001
<6>[ 2.975311] mmcblk0: mmc0:0001 VYL00M 14.6 GiB
<6>[ 2.980407] mmcblk0boot0: mmc0:0001 VYL00M partition 1 512 KiB
<6>[ 2.986877] mmcblk0boot1: mmc0:0001 VYL00M partition 2 512 KiB
<6>[ 3.000305] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13

and even mounts 2 ext4 partitions :

<6>[ 3.344055] EXT4-fs (mmcblk0p12): mounted filesystem with writeback data mode. Opts: (null)
<6>[ 5.392791] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: (null)

as far as i understand it what fails is init on line 324, to me this looks like its looking for init in the wrong place.

maybe there is some ramdisk hackery missing ?

juts my 2 cents ...

cheers guys !
[Samsung Galaxy Nexus] Grarak:
I didn't look through the whole log

the partitions fails here

<3>[ 37.008178] fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/platform/omap/omap_hsmmc.0/by-name/system at /system options: (null) error: No such file or directory
[Samsung Galaxy Nexus] thagringo:
yes, if you look to the timing is takes around 20 seconds to get from the first init failure i posted to yours. Which again to me looks like init is looking for the scripts to launch, looks everywhere, finds nothing and gives up.

the only thing im trying to say is that it might not be only kernel related but maybe some userland trick has to be done.

could you maybe try to compile a kernel with all full debug on ? maybe there is sth. obvious happening.

again, just my 2 cents. I do have some kernel knowledge and i have hacked the linux kernel previously but i do have almost zero knowledge about the linux kernel in android world.

cheers guys !
[Samsung Galaxy Nexus] Carlos_Manuel:
Could this help?: https://github.com/manumanfred/devi...mmit/633a2c23f94ab0e2bd4944bbaa62dc3ef54e022e

and this:

# create filesystems if necessary
service setup_fs /system/bin/setup_fs \
/dev/block/platform/omap_hsmmc.0/by-name/cache \
/dev/block/platform/omap_hsmmc.0/by-name/userdata
class core
user root
group root
oneshot

Google Glass XE12 - XE16 init.omap4430.rc
[Samsung Galaxy Nexus] aosp:
[MENTION=4443334]Grarak[/MENTION] What [MENTION=1369025]thagringo[/MENTION] said and [MENTION=4022928]Carlos_Manuel[/MENTION] Thanks fellas and yes we must attack it from both sides kernel+userland ?

[MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] Carlos_Manuel:
https://github.com/manumanfred/device_samsung_tuna_kernel_3.4/blob/cm-11.0/fstab.tuna fstab.tuna edited too. see: http://git.omapzoom.org/kernel/omap...bdc8f7b1f97;hb=refs/heads/d-jb-mr2.0-release:

# Android fstab file.
# <src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/block/[B]platform/omap_hsmmc.1[/B]/by-name/system [B] /system ext4 [/B] ro wait
/dev/block/platform/omap_hsmmc.1/by-name/efs /factory ext4 ro wait
/dev/block/platform/omap_hsmmc.1/by-name/cache /cache ext4 noatime,nosuid,nodev wait,check
/dev/block/platform/omap_hsmmc.1/by-name/userdata /data ext4 noatime,nosuid,nodev wait,check
[Samsung Galaxy Nexus] ScardracS:
So could somebody make a post with all the repos you have used?
[Samsung Galaxy Nexus] Carlos_Manuel:
https://github.com/JackpotClavin/3.4-Kernel-Tuna

https://android.googlesource.com/kernel/omap/+/glass-omap-xrv15c

https://github.com/Grarak/grakernel-tuna/tree/glass-omap-xrv15c

https://github.com/Grarak/grakernel-tuna/tree/glass-omap-xrv15c-jackpot

https://github.com/manumanfred/device_samsung_tuna_kernel_3.4
[Samsung Galaxy Nexus] thagringo:
umm, could be, looks relevant at least. would be worth a try adding these lines to the main init.rc.

cheers
[Samsung Galaxy Nexus] ScardracS:
Thank, i'm starting to download kernel sources
[Samsung Galaxy Nexus] Carlos_Manuel:
Init.rc should not be needed to be edited. Init.tuna.rc must be edited because if kernel finds init.rc then it also imports other needed .rc files "impot init.{ro.hardware.rc}, etc.

Hopefully someone can try these because I don't have kernel sources on my notebook and I'm in the dorm and here's the school's network way too slow, so downloading kernel sources takes over 1 hour
[Samsung Galaxy Nexus] ScardracS:
How i can clone that repos? https://android.googlesource.com/kernel/omap/+/glass-omap-xrv15c
[Samsung Galaxy Nexus] Carlos_Manuel:
Git clone https://android.googlesource.com/kernel/omap -b glass-omap-xrv15c
[Samsung Galaxy Nexus] jhonnyx:
[MENTION=5747201]isrcepeda[/MENTION]

http://xdaforums.com/galaxy-nexus/general/devs-make-happen-t2717611
[Samsung Galaxy Nexus] isrcepeda:
I just sent a PM, lets see if I can get it to start having fun with you guys :)
[Samsung Galaxy Nexus] aosp:
Ever since Google dropped Galaxy Nexus support I can now finally rest in peace ? Viva LA OMAP!

Thanks for proving that some devs still care you rock dude ?
[Samsung Galaxy Nexus] Carlos_Manuel:
I built my ROM with https://github.com/Grarak/grakernel-tuna/tree/glass-omap-xrv15c-jackpot and I edited init.tuna.rc and ueventd.tuna.rc and I also used Google Glass's pvr files.

Result:

After Google splash screen, blank screen, no vibration either.

Windows detected MPT and ADB
[Samsung Galaxy Nexus] Carlos_Manuel:
One another thing:

It's looking for files which I have renamed...
[Samsung Galaxy Nexus] Grarak:
the kernel can't initialize the display

adding blobs doesn't help
[Samsung Galaxy Nexus] Carlos_Manuel:
Yep.

I don't think I can do anything more to make screen working.

So what now..? :|
[Samsung Galaxy Nexus] Ziyan:
First of all, I suggest you to use our stock Google kernel (and stock 4.3), not Fancy, it will be easier ;)

If something goes wrong, you can always pull out your battery, and restore your phone using fastboot or recovery. I can help a bit, as I'm a junior software engineer, but I don't have much time nowadays :(
[Samsung Galaxy Nexus] ak:
If your kernel won't boot you have to use an UART cable for debugging at low level.

;)
[Samsung Galaxy Nexus] :
yay anarkia is here! let's get this going!
[Samsung Galaxy Nexus] protowave:
I think it won't boot for the first 20-30 tries.:highfive:

Tonight i'll meet a friend who has 3.3V TTL/USB chip, so i'm gonna try UART debug.

Is 619K resistor right?

I'm reading Accessing uart on Galaxy Nexus : http://xdaforums.com/showthread.php?t=1461986

Hope is the right thread.
[Samsung Galaxy Nexus] drive2droad:
Quite excited to see Anarkia here , dude we need your help & support !!
[Samsung Galaxy Nexus] Pasquale91fg:
watch here:

http://omappedia.org/wiki/4AJ.2.5_OMAP4-Panda_Jelly_Bean_Release_Notes
[Samsung Galaxy Nexus] nixholas:
Peeps, My second GNex is here :D Even though my exams are starting soon, I'll still be working on this (: I'll drop by again with some news. As of now, I've successfully re-wired a few drivers, namely the WIFI drivers and the bluetooth drivers.

I'll be back :)

Peeeeep :D
[Samsung Galaxy Nexus] flip360:
Great news, hope you get a working base :)
[Samsung Galaxy Nexus] zandander:
Good news amp!
[Samsung Galaxy Nexus] drive2droad:
Here's a thread on another forum where they are working to possibly bring 3.6 ... http://rootzwiki.com/topic/32023-wi...1-developers-needed-a-community-kernel/page-4
[Samsung Galaxy Nexus] Scandy:
It's almost dead for 1 year...
[Samsung Galaxy Nexus] Pasquale91fg:
How do for flash this kernel?
[Samsung Galaxy Nexus] drive2droad:
Sadly I found this out after posting it here , I still think that 3.1.x is easily achievable but no kernel developer here wants to make the jump ??
[Samsung Galaxy Nexus] Sparx639:
Then let's slowly work our way up

Sent from my sock drawer