yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] protowave:
Don't know what you exactly mean...

For me is almost the same:

With 150k i hit return two time to enter fiq debugger but sometimes after 3 second it got disabled, I don't understand if is my fault or kernel lacking of conf.

With 523k I got clean boot messages, compare strange chars in my first post with battery stats in second. After that I enter fiq debugger with double return and than I can ask for dmesg with kmsg command.

I have a console command too, but I don't know how to use it.
[Samsung Galaxy Nexus] MWisBest:
Don't get too excited just yet guys, dhacker's stuff isn't finished yet, but he is doing an amazing job with spearheading this. I did test what he has done so far and it's bootlooping for me, I was hoping I might be able to get at adb to do something further with it to help out but it doesn't boot that far and I don't have access to UART. :( In the mean time, I'll go rummage around for a spare micro USB cable, some resistors (but I'll probably have to buy some, as the chances of me having the correct one are slim to none >.<), and hack it apart to get at it.
[Samsung Galaxy Nexus] Link_of_Hyrule:
Hopefully you guys are able to get it to not with the new kernel and drivers keep up the great work.
[Samsung Galaxy Nexus] dhacker29:
I pushed it so I wouldn't lose anything. I need to make more changes to the board-*tuna files in kernel to get it booting. That was 1577 commits from omapzoom/ti to the kernel lol. I'll work on it again tomorrow. If anyone gets serial console output from a build please post. I haven't set that up.
[Samsung Galaxy Nexus] aosp:
Googlers get paid I'm sure hefty and they completely ignored all the OMAP4 optimizations from omapzoom all we got was a push and a revert like screw this let xda figure it out and put it together then they dropped it lol thanks for the support it is a shame how greedy these corps are becoming making people feel left out so they force upgrades on folk Goo you poo

You saw my last about the WiFi drivers too cause they figure we don't need range or display before they gave us the boot Google Nexus Support style :)
[Samsung Galaxy Nexus] Ashtrix:
Thanks Aosp & all the devs for the KitKat update job :) , it would be great if we can have a custom kernel loaded with all new features :good:...Still running 4.3 for the time being. If i knew how to build a kernel, i'd be the first to build one :rolleyes:
[Samsung Galaxy Nexus] metalspring:
Building a kernel is actually pretty easy

Its modifying the source that is the hard part lol

Oh and btw dhacker, great job on the kernel work, I actually use your source for the kernel included in my cm-11 builds :good:
[Samsung Galaxy Nexus] protowave:
Don't know how to build. :(

Can someone give me (simple) instructions?

Than i'll test all attempts :)
[Samsung Galaxy Nexus] stranostrano:
that's a little start for beginning to understand something about android kernel building http://www.kandroid.org/online-pdk/guide/build_system.html.

And of course xda how to http://xdaforums.com/showthread.php?p=38144723

And the xda university http://xda-university.com/as-a-developer/adding-features-to-your-kernel

Not exaustive but it's a start.
[Samsung Galaxy Nexus] protowave:
Thanks, actually i've built right now, pvr branch of [MENTION=4112553]dhacker29[/MENTION]:

proto@proto-vaio:~/android/kernels/dhacker29_tuna/arch/arm/boot$ file zImage
zImage: Linux kernel ARM boot executable zImage (little-endian)

Using these vars:

export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
export PATH=/home/proto/android/toolchains/arm-eabi-4.6/bin:$PATH

I got the zImage, but than I need to include binaries or not?

and how to create a zip to flash it on CM11? Can AnyKernel by Koush work for us?

PS: sorry for so many simple questions, but i'm not into android kernel development and I'm at the beginning of my learning curve.
[Samsung Galaxy Nexus] kostheback:
This kernel which run on rom?

for example:http://xdaforums.com/showthread.php?t=2525351
[Samsung Galaxy Nexus] aosp:
I linked the links for the links in my last few posts but I say wait for [MENTION=4112553]dhacker29[/MENTION] to patch it up right I don't think it boots current state ;)
[Samsung Galaxy Nexus] aosp:
Don't go flashing everything on the web bro wait for dev to update first post with the ROM source code and flashable .zips are different ;)
[Samsung Galaxy Nexus] metalspring:
If you want to know a few basics of kernel development just pm me

I'm no expert by any means, but I know enough on how to build and package kernels and some menuconfig options

I'd rather not spam the thread with explaining how to make kernels lol
[Samsung Galaxy Nexus] aosp:
[MENTION=3390093]MWisBest[/MENTION] Can you link me some logs adb or dmesg of those bootloops please?
[Samsung Galaxy Nexus] Mevordel:
It disables itself so it can save power (drop wake lock). I think the difference comes from using different versions of the kernel (the builds I was testing didn't have FIQ enabled).

---------- Post added at 08:23 AM ---------- Previous post was at 08:19 AM ----------

Install abootimg or another program that can unpack boot images (or build Android yourself), and extract the RAM disk from a CWM image. The flash it in fastboot:

fastboot flash:raw arch/arm/boot/zImage path/to/cwm.ramdisk.img

---------- Post added at 08:25 AM ---------- Previous post was at 08:23 AM ----------

I probably can this evening if nobody else does.
[Samsung Galaxy Nexus] Grarak:
https://github.com/RomSwitchers/RomSwitcher-tuna/blob/master/build.sh
[Samsung Galaxy Nexus] aosp:
[MENTION=4610477]Mevordel[/MENTION] Would appreciate it logs are my thing always a mystery too decipher ;)
[Samsung Galaxy Nexus] aosp:
[MENTION=4112553]dhacker29[/MENTION] Have you spoken with [MENTION=1719128]ljz[/MENTION]yal regarding the newer PVR drivers? https://github.com/CyanogenMod/andr...ee4fe1aafd9895355f0e892#commitcomment-4653099
[Samsung Galaxy Nexus] stranostrano:
Wow! Look promising. Really nice (and huge; and clean) work.
[Samsung Galaxy Nexus] MWisBest:
Unfortunately it bootloops before the device even shows up as connected to my computer. What happens is all of a sudden the white "Google" and "unlocked icon" will turn purple, and get more and more purple, and then eventually it reboots. If I had access to UART I'd probably be able to get some sort of logs. Something I did notice with the kernel is that the "omaplfb" sources aren't in the kernel tree, and I thought with the DDK 1.9 versions that it was maintained right in the kernel, but I don't understand how the pvr module could compile if that was really the case. Honestly, I'm beginning to think the best course of action to get this stuff going at this point would be to start with just a bare non-tuna omapzoom git branch, and then "manually" add in all the stuff required to get it building for tuna. I'll probably give that a shot tonight, I have some things to do around the house first.
[Samsung Galaxy Nexus] bsmitty83:
Omap lfb moved from drivers/GPU to drivers/video/omap2 with the new ddk and for it to work you needs to compile the Eurasia PVR source after the kernel is built . also for this to work it needs to compile with a ROM to make all the new bins and libs. I've been attempting this and so far have a good plan just need the time to do it . but untill we get the new bins and libs the complied kernel will not work on it's own
[Samsung Galaxy Nexus] protowave:
Can you share your plan with us? :)

I'm downloading cm11 platform specific gits and including dhacker29 Kernel. Tomorrow I'll build and have some tests.

Thanks [MENTION=4328678]metalspring[/MENTION] for your support!
[Samsung Galaxy Nexus] bsmitty83:
For sure , its a pretty simple one . I know the PVR source needs to be moved from the kernel , built as a module . I'm gonna use aosp kk as my test build and am gonna add all the relevant commits ( basically everything everyone else is gonna do lol ) . I think that once one ROM gets made with the new binaries , they should work transplanted into any ROM . any performance or cleanup commits I'll add later. Right now I'm focusing on the necessities . I'm pretty confident in my kernel being OK , not sure how the ROM build will go , I've only built vanir a few times for myself .
[Samsung Galaxy Nexus] aosp:
[MENTION=4112553]dhacker29[/MENTION] github has the plan look at his repos modifying the tuna repos to be inline with omap4zoom should be the only plan for easy merging in the future break loose from Google

The GNeX is not alone

https://github.com/CyanogenMod/android_device_samsung_i9100g/tree/cm-11.0

https://github.com/CyanogenMod/android_device_samsung_omap4-common/commits/cm-11.0

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

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

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

https://github.com/KFire-Android/android_device_amazon_jem

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

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

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

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

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

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

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

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

https://github.com/ljzyal/android_device_amazon_jem

https://github.com/omnirom/android_device_samsung_omap4-common/commits/android-4.4
[Samsung Galaxy Nexus] Garridon:
I don't I know too much about this stuff, but are those ones not used in current kernels or whatever? And if they are newer than the ones currently being used then would they fix the problem of tethering to an Xbox possibly?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Bewinxed:
I wish you guys all the good luck, You're doing an amazing job :')

I'm gonna be traveling to UAE in a week & half (New/First Job) And I'm gonna hand this phone over to my brother, So I have basically prepped the phone to be a logcat/testing machine, If you guys need some testing I'll be glad to, Just sayin'

<3
[Samsung Galaxy Nexus] MWisBest:
I am building it with a ROM and everything, and I know omaplfb is supposed to be in drivers/video/omap2, but it isn't there in dhacker's sources currently. I'm using the exact kernel sources he has minus my temperature sensor code cherry-picked in there, the commit updating the proprietary bins and libs is in there as well, and so is the commit adding the PVR source to android_device_samsung_tuna. Right in my build is the pvr module, it's built automatically.
[Samsung Galaxy Nexus] dehein:
Do newer wifi drivers exist, with wireless display. (Early to ask for features) just from my point of understanding, Google did not include the latest updates for everything, only necessary ones.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] bsmitty83:
Almost got my local ready to build , if it builds it may work Lol , fingers crossed guys , this will take a while but I'm catching up ;)

Edit : building now , hope it keeps going lol
[Samsung Galaxy Nexus] kenshin33:
or

fastboot boot (doesn't flashanything just boots the image and upon a reboot goes back to previous kernel)
[Samsung Galaxy Nexus] protowave:
I'll try it!

Perfect for a quick and dirty test.

But for uart debug? Will I be able to exchange cables and get serial console?
[Samsung Galaxy Nexus] aosp:
Missing will happen ;)
[Samsung Galaxy Nexus] MWisBest:
Ah, I didn't see his post here! My bad.
[Samsung Galaxy Nexus] aosp:
Webview graphic glitches finally fixed in CM11 ;)

gpu: Refactor GpuMemoryBuffer framework for multi-process support.

http://goo.gl/FZBhFe
[Samsung Galaxy Nexus] PlayfulGod:
yup, cherry-picked and tested it earlier. ;)
[Samsung Galaxy Nexus] aosp:
You merge in the new WiFi drivers I linked you?
[Samsung Galaxy Nexus] PlayfulGod:
not yet, thinking about doing that here in a bit.

What do they add/improve?
[Samsung Galaxy Nexus] aosp:
Tons of WiFi fixes too many since they updated the tuna lol

Also Our GNeX can use the new android sync framework too with some small changes

TARGET_RUNNING_WITHOUT_SYNC_FRAMEWORK := false

merge below commits in tuna kernel ;)

staging: sync: Add synchronization framework · 7ad530b · android/kernel_common · GitHub - http://goo.gl/yUeF5K

staging: sw_sync: Add cpu based sync driver · 9d1906e · android/kernel_common · GitHub - http://goo.gl/RDKKJl

[MENTION=4112553]dhacker29[/MENTION] I'm still digging lol
[Samsung Galaxy Nexus] aosp:
[MENTION=4112553]dhacker29[/MENTION] besides the WiFi drivers you could merge the new sync framework into the tuna from the defy git

https://github.com/Quarx2k/jordan-kernel/commits/p-android-omap3-3.0/drivers/staging/android
[Samsung Galaxy Nexus] Link_of_Hyrule:
Good to see at least half the problem has been fixed hopefully the new GPU drivers and kennel can fix the rest only thing keeping me back from kitkat is my need for Voice+ :P
[Samsung Galaxy Nexus] AbhishekS:
Great work guys. I love you people so much. You guys are doing a fabulous job!!!!

Love and respect from India. :)
[Samsung Galaxy Nexus] PalmerCurling:
when can we expect to see these gpu fixes implemented in ROMs/CM source?
[Samsung Galaxy Nexus] ashclepdia:
whenever people start building with it :D

looks like playfulgod has already started doing it

but as for CM's source i assume once you see a change in status here http://review.cyanogenmod.org/#/c/54291/

tho im not certain on how that works...

no eta's lol, soon ;D
[Samsung Galaxy Nexus] bsmitty83:
I'm still waiting on my test build to finish compiling since its the first build I'm running it as slow as I can to catch errors , its still compiling as of now , I added the new ddk and my kernel to mbq s' aosp ROM , also I grabbed that patch from cm for the kk glitch .

I'm gonna let it run overnight and I'm sure even if it compiles I doubt it'll work 1st shot so eta is hopefully close
[Samsung Galaxy Nexus] Enter The Nexus:
Sorry for a dumb question, but how did you all learn to code? I want to be able to build ROMs and other Android related tinkering...
[Samsung Galaxy Nexus] David 617:
To build roms you don't need to learn any programming. There are tutorials from CM and other places on xda proving you with instructions on how to compile a custom rom.

Check out this - https://www.youtube.com/watch?v=1_H4AlQaNa0

and this - http://wiki.cyanogenmod.org/w/Development

and this - http://xdaforums.com/showthread.php?t=2515305

With regard to Android programming, I learnt Android programming from an excellent YouTube tutorial series, Marakana's Android Bootcamp - https://www.youtube.com/playlist?list=PLE08A97D36D5A255F You'll need a background in Java for that.

Kernel development is a whole different ballpark. Those guys are wizards ;). I think it involves C and C++, but I don't know for sure.

Oh, and this is really not a dumb question. Kudos to you for wanting to learn more. I look forward to using your roms in the future :highfive:
[Samsung Galaxy Nexus] Suxsem:
Incredibile job men, you're awesome :) sorry for the off topic :)
[Samsung Galaxy Nexus] kenshin33:
once it boots you can do what you want, until you reboot the phone. At that point i t will revert to old kernel (the one on boot parition)
[Samsung Galaxy Nexus] dhiru1602:
The GPU drivers should be patched for sync framework support. This again may require compatible userspace binaries. :cyclops:
[Samsung Galaxy Nexus] PlayfulGod:
Well I gave it a try last night but... it seems some parts of each commit have been already merged in and other parts left out. Thus confusing the hell of of me on what/where to add it. I'm not a kernel guru! ;)
[Samsung Galaxy Nexus] metalspring:
I might be able to give it a try if you link me to the latest source on them

Try being the key word :p

Edit: is this what you were talking about adding in?

https://github.com/android/kernel_common/commit/e222a63afbaba352c523970f7b25af95e4ba2eb1
[Samsung Galaxy Nexus] PlayfulGod:
if I can track down aosp's post again were he linked em for me lol. I was trying to add em to cm's tuna kernel. dhacker29 has a fork of hes been pushing to too.
[Samsung Galaxy Nexus] metalspring:
I have dhackers source but it doesnt seem to match up very well against any of the wifi sources aosp had up there, there was a lot of stuff missing and i dont know enough kernel knowledge to just add it in and say it would work :(

I'll keep looking through it but idk, might take someone with more kernel knowledge
[Samsung Galaxy Nexus] PlayfulGod:
yea i had that issue with cm's tuna src too. lol
[Samsung Galaxy Nexus] aosp:
[MENTION=2999829]PlayfulGod[/MENTION] [MENTION=4328678]metalspring[/MENTION] Merge the below commit first and let me know if it works

bcmdhd: upgrade to 1.28.4 (r339952) - Thanks to Master: renaudallard · d21079a · anarkia1976/AK-tuna · GitHub - http://goo.gl/Ih5Wwk
[Samsung Galaxy Nexus] kenshin33:
booted and seems working

copied replaced bcmdhd directory in cm-11 kernel tree with the one in this :

https://android.googlesource.com/kernel/common.git/+/e222a63afbaba352c523970f7b25af95e4ba2eb1
[Samsung Galaxy Nexus] aosp:
Simple enough lol seems working?
[Samsung Galaxy Nexus] Link_of_Hyrule:
What exactly does that mean are the graphical glitches fixed?
[Samsung Galaxy Nexus] albsat:
No. We have new WiFi drivers as it seems.
[Samsung Galaxy Nexus] aosp:
[MENTION=1664077]kenshin33[/MENTION] Grab that folder after this update

net: wireless: bcmdhd: Change the parameter for TDLS · 07485c0 · android/kernel_common · GitHub - http://goo.gl/AETXTh

Or just copy paste ;)

https://github.com/android/kernel_common/tree/android-3.4/drivers/net/wireless/bcmdhd
[Samsung Galaxy Nexus] Link_of_Hyrule:
Well that's good too but hopefully GPU drivers soon too.
[Samsung Galaxy Nexus] kenshin33:
so far so good
[Samsung Galaxy Nexus] aosp:
New WiFi drivers for the GNeX that fixes lots of issues that you don't see besides better battery life but my goal is to help update what we can ;)
[Samsung Galaxy Nexus] Link_of_Hyrule:
Yeah me drivers are usually always good :) it does seem like you guys are making progress I wish I could help but I can't do much but test roms. I used to be liquid smooths main tester for the htc thunderbolt so I tested the first working ICS ROM. Anyways keep up the great work hopefully we see progress after you get it to build with the new GPU drivers.
[Samsung Galaxy Nexus] kenshin33:
well after initial change I entend to cherry-pick all relevant commits to the latest (to keep history)

EDIT on 2nd thought ehat purpuse would that serve ... screw it I'm grabing the lastest !
[Samsung Galaxy Nexus] aosp:
Glad it worked out ;)
[Samsung Galaxy Nexus] MrObvious:
Not trying to crap this thread but how hard would it be to get some of this stuff ported to other OMAP4 devices? Honestly you guys are doing great work and it would be really cool if it could be done. I'm mainly thinking of the Moto Droid line. Pm me if you don't want to waste thread space.
[Samsung Galaxy Nexus] kenshin33:
https://android.googlesource.com/kernel/common.git/+/001e0940660b96251c3ffc8da23b819c356f06ea^!/#F0 this makes it fail
[Samsung Galaxy Nexus] aosp:
Besides swapping the folders did you make any other changes to the source or defconfigs?

did it compile clean with no errors?

WiFi drivers compiled as modules?

Check logs adb, dmesg or secpolicy /data/misc/audit/audit.log

Try syncing upto this only

net: wireless: bcmdhd: Update to version 1.88.45 · e222a63 · android/kernel_common · GitHub - http://goo.gl/luwkwo
[Samsung Galaxy Nexus] kaijura:
Well it's good step but it seems the fix is just to use CommandBuffer to handle GLImages, which seemed to be causing those black webview glitches?

Hopefully this doesn't make anyone give up on merging the newer OMAP sources but I haven't been successful with it so far
[Samsung Galaxy Nexus] metalspring:
Did you make sure everything worked though?

Like does wifi tethering work, does wifi direct work, do all the different types of wifi security work, does 5 GHz frequency band work, etc?.

---------- Post added at 01:07 AM ---------- Previous post was at 12:52 AM ----------

Btw, anyone see these yet?

https://github.com/dhacker29/android_kernel_samsung_tuna/commits/pvr

https://github.com/dhacker29/androi...mmit/1116cc2dca06f3a0b8422cbee891e55112b3690b

https://github.com/dhacker29/propri...mmit/3515f2a1d4de5ef822cce8dbdced3079913dc3bb

[MENTION=4112553]dhacker29[/MENTION] can't the toro: Upgrade PVR to 1.9@2291151 go to maguro and toroplus?

Or are you just focusing on toro until you get it worked out and then pushing those changes to the other 2 devices?

Nice job btw, but do your android_device_samsung_tuna and proprietary_vendor_imgtec build, boot and work properly with those commits?

If they do I'd definitely try switching to your repos on those instead of cm's and see how they work with different things to help test
[Samsung Galaxy Nexus] kenshin33:
did nothing as there was nothing to change (the only Kconfig option that was added is toenable/disable bcm4339)

by default cm_defconfig builds wireless drivers in kernel.

e222a63 worked, it was the first thing I copied. I mean wifi connected .. didn't check anything else (wifi direct or tethering)

I reverted the said patch and it worked. (As it worked with e222a63)
[Samsung Galaxy Nexus] bush911:
Thank you all guys for what you have done and what will be doing. Thank u.
[Samsung Galaxy Nexus] Culex316:
Thank you guys for keeping my phone alive :thumbup:
[Samsung Galaxy Nexus] oli20021978:
Dear God.......please stop with spamming........this is a dev thread. You are thankful? Donate to the people or thank via xda.
[Samsung Galaxy Nexus] dhacker29:
I'm just focusing in toro as that's what I have but it will be universal when it's working. It's not finished and not booting yet
[Samsung Galaxy Nexus] aosp:
Below doesn't and should give us more butter while saving battery also could help us get rid of fake butter power.tuna.so ;)

omapfb: implement vsync sysfs, make uevents optional · 4f7d068 · CyanogenMod/android_kernel_samsung_t1 · GitHub - http://goo.gl/gUcpsZ

hwc: support vsync notification via sysfs · 53cacd8 · CyanogenMod/android_hardware_ti_omap4xxx · GitHub - http://goo.gl/VNn11K

hwc: fix timing issue with vsync sysfs loop · 62b870e · CyanogenMod/android_hardware_ti_omap4xxx · GitHub - http://goo.gl/0tujeX

BOARD_USES_HWCOMPOSER := true

BOARD_USE_SYSFS_VSYNC_NOTIFICATION := true

OMAP_ENHANCEMENT_MULTIGPU := true

OMAP_ENHANCEMENT := true
[Samsung Galaxy Nexus] metalspring:
Unfortunately, its as I feared...

It connects and disconnects fine but breaks wifi tethering completely :(
[Samsung Galaxy Nexus] aosp:
Paste a logcat of the failure please
[Samsung Galaxy Nexus] metalspring:
Im finding this every time I tried to use tethering...

E/hostapd ( 5766): Configuration file: /data/misc/wifi/hostapd.conf

I/hostapd ( 5766): rfkill: Cannot open RFKILL control device

E/hostapd ( 5766): nl80211: Failed to set interface wlan0 into AP mode

E/hostapd ( 5766): nl80211 driver initialization failed.

E/hostapd ( 5766): Failed to initialize interface
[Samsung Galaxy Nexus] supernova_00:
I'm pretty sure that is why none of the kernels currently use those drivers because they broke wifi tethering and connecting to routers with no security or whatever the crappy security is that shouldn't be used anymore. *brain fart*.
[Samsung Galaxy Nexus] aosp:
Does the rom you using have hostapd_cli in /system/bin ?

Other WiFi features besides tethering working?
[Samsung Galaxy Nexus] metalspring:
Yes, it did have that file, I'll flash the stock cm kernel later to make sure that nothing broke it somehow

Also, that's about all I can test...

I have never used and have no idea how to use WiFi direct, plus only access to one WiFi router so I can't test other password encryption types or 5GHz, etc