yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
The kernel is supposed to be integrated in the zip, but it doesn't boot until I flash the kernel with heimdall.
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
I'm thinking it could be a bad or incomplete updater script but you would know more about that than I would.

Sparx639
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
I got it to work. Just download the kernel and rename it to zImage and put it in the root of the ZIP then delete "boot.img". Then edit the "updater-script" file located in META-INF/com/google/android and delete this line:

package_extract_file("boot.img", "/dev/block/mmcblk0p11");

Replace this line with

assert(package_extract_file("zImage", "/tmp/zImage"),
write_raw_image("/tmp/zImage", "/dev/block/mmcblk0p11"),
delete("/tmp/zImage"));

Then flash the ZIP with CWM and the device should boot.
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
^ There we go

Sparx639
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Ok so the issue is it's using package_extract_file instead of write_raw_image. I'll see if I can fix it.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
Have you tried using files from i9000 sources?

AFAIK they have 100% working jellybean

if not I think I could try to do so
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Yes, yesterday I rebased the device tree on captivatemtd and aries-common to make sure it was updated for 4.1, and today I'll probably look at crespo to see if there's anything interesting there.

If anyone is interested in building CM10 for themselves, the appropriate local_manifest.xml is :

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Mevordel/android_device_samsung_venturi" path="device/samsung/venturi" remote="github" revision="jellybean" />
<project name="Mevordel/android_kernel_samsung_venturi" path="kernel/samsung/venturi" remote="github" revision="jellybean" />
</manifest>

I will be working on this all day, so expect to see changes at https://github.com/Mevordel/android_device_samsung_venturi

Also, there is a minor hack I haven't fixed to get the kernel to compile. You have to manually copy the initramfs to the out directory. (you can't just git clone - and must use the script - due to limitations in git.) So when it errors out in the middle of mka bacon, run

cd kernel/samsung
git clone https://github.com/Mevordel/Initramfs-for-Galaxy-Player-5.0
cd venturi
./build-linux-yp-g70usa # Hit control-c when you see lines beginning with 'HOSTCC'
make mrproper
cp -r kernel/usr -t ../../../out/target/product/venturi/obj/KERNEL_OBJ/kernel/
cd ../../../
mka bacon

Eventually I'll make a recipe to package the initramfs automatically.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
I use virtual machine on poor hardware so compiling rom would take ages.

Can jb kernel be compiled with arm-eabi-4.4.3 like ics kernels?

and by such a commands

export ARCH=arm

export CROSS_COMPILE=~/.....

make XYZ_defconfig

make

youp?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I understand. :cyclops:

Yes, just download kernel and initramfs source into side-by-side folders, export vars, and run. from kernel folder

./build-linux-yp-g70usa

This will integrate modules into ramdisk and ramdisk into kernel.
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
Any progress on the wifi problem? I compiled the latest kernel/initramfs source, but the wifi still did not work. It looked like something with bcm4329.hcd, but I replaced it with the one from pre-alpha 2, and it still did not work. I also copied the rest of the files to /vendor/firmware from the pre-alpha 2 ROM, and still nothing. Here is a link to the logcat: http://pastebin.com/HkUyRtsm
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
The problem is that we didn't have a kernel module built for our 3.0 kernel. I will work on that tomorrow, and bluetooth too. I believe we're close on both, and it'll be much faster now that some build process kinks have been worked out...

IN OTHER NEWS :)

Finally! After 2 full days, a bunch of commits, reading half the Android makefiles, and a crash course in Python, I finally got the build system to cooperate. Now, with only a one-line local-manifest.xml (to add the device tree), it will build everything and in the right order: recovery -> initramfs -> kernel -> boot.img -> zip.

AND IT INSTALLS AND BOOTS WITH NO HACKS!

:cowboy: I guarantee I have spoken too soon, but bugs can be squashed. I believe now is the time to graduate to alpha stage. Hardware is still non-functional (stupid vold...) but our device tree is now fully functional. So, next up: wi-fi, bluetooth, internal storage, and yes, CWM. It's in the ramdisk right now, but it doesn't exactly work right now, probably because I haven't configured it yet.

tl;dr:

So latest tree is on github at the usual place, and first alpha zip will be in the OP as soon as it uploads.
[Samsung Galaxy Player 4.0, 5.0] mrjaredbeta:
Great news! I'm looking forward for the bugs to be squashed.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Me too :p

New zip is in OP. Wipe data before installing it, as your Bluetooth address is saved to the /data partition. (/efs is rfs, which we can't read without Samsung's modules, and they don't work on a newer kernel.)

As a side note to those building kernels: the initramfs repo is outdated and will be removed. Why? because we must build with Android (or at least part of it) to get recovery. However, you can still extract the initramfs from the released kernel with CWM and point CONFIG_INITRAMFS_SOURCE to that folder locally to build your own.
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
Ok, so all the problems are kernel issues? Because i tried using the kernel from pre-alpha 2 with the newest ZIP and wifi didn't work.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Right. It's kinda complicated, because modules were floating around everywhere in roms and ramdisks, but each only works with a certain kernel, so I kept getting version mismatches. Theoretically, since wi-fi worked in pa2, the module was built with the same source as that kernel, but for some reason, it's not being built now.

Modules also cause bluetooth problems, as we no longer can access the /efs (no rfs driver) and have to save the Bluetooth mac address before booting the 3.0 kernel.
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
great..this thread is no longer dead ..i love to read here :D
[Samsung Galaxy Player 4.0, 5.0] KOala888:
So, mevordel

about what you take care right now? I mean with what could I try to not to do same thing as you at the same time if you know what I mean.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
this looks awesome.

trying to flash but i keep getting a device offline error in adb. i've tried everything :/ anybody ever get this error? every kernel or even in recovery, it still reads device offline
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
I think you flash it in Download Mode with Heimdall. Or you can put it in the ZIP and modify the update-script as mentioned in an earlier post.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
the issue is i need to help develop and without adb access, i cannot grab logcats and whatnot. can somebody running linux type "lsusb" in the terminal and post the output?

Also happy Thanksgiving to everybody in the US
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
I dont have linux but reinstaling drivers and puting device on other usb port helped me few times in windows.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Are you unable to use adb before or after flashing this rom? Remember, adb takes like 30 seconds to start in recovery, and threr's a bug in the kernel where it doesn't recognize being plugged in during boot-you have to unplug and replug.

I can send you a lsusb in a bit. Are you seeing anything new in dmesg after plugging it in?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
The update-script is fixed. No hacks or download mode required anymore.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
It's on the computer side. It works fine on another computer. I've tried everything on my main computer though. So frustrating
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
Would we be able to use this kernel on other AOSP ROMs in the future or is it just locked for cm10? Some ROMs seem to like to do that with their included kernels

Sparx639
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
It should work with any jellybean, but I'm not going to try it until I get cm10 working fully (well, except camera - I don't really think that will ever get fixed).
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
No big deal, hw acceleration is what I want which already works

Sparx639
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Ok. Now the ROM is actually usable. My latest build has fixed wi-fi. I'm not at home right now, but as soon as I am it will be uploaded. Also, I think GPS will work if you run, as root, 'gpsd -d /vendor/etc/gps.xml'. The thing is it's supposed to start at boot, but no matter what I've done to the init scripts, it still does not. I still have ideas, though. So this is looking quite good at the moment. Unfortunately, I won't be able to work on it much the rest of the weekend - family and whatnot.
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
For the GPS, what usually keeps a script or a module from loading at boot within Linux anyways? It could just be something small and stupid for all we know. You are doing a great job though

Sparx639
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
New zip is up with fixed wi-fi, and the vold trick in post two should work with it.
[Samsung Galaxy Player 4.0, 5.0] gskillivenom:
Im gettin a Status 7 in CWM. What could be wrong?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
What kernel are you using? I'll check the zip, but I'm quite sure it's the one I'm running now.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I just redownloaded and reflashed without any issues. Try entropy's kernel - your home button won't work, but you don't need that for CWM anyways.
[Samsung Galaxy Player 4.0, 5.0] gskillivenom:
Installed the entropys kernel. Still gettin the status 7 error. Im not sure whats wrong...
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Try redownloading the zip. Otherwise, I don't know what the problem is. Does it give any more information than just 'status 7'? Maybe that can tell me where the error is.
[Samsung Galaxy Player 4.0, 5.0] gskillivenom:
Finding update package...

Opening update package...

Installing update....

assert failed: getprop("ro.product.device")=="venturi" | | getprop("ro.build.product") == "venturi" | | getprop("ro.product.device") =="YP-G70" | | getprop("ro.build.product") == "YP-G70"

E: Error in /sdcard/cm-10-20121122-UNOFFICIAL-venturi.zip

Status7

Installation aborted.
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
Your ro.build.product in your buikd.prop probably says venturi_usa. Change it to venturi and it should work
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
So it had nothing to do with rumirand's kernel. Good. So to fix: either do what Supermaster34 said (basically make one of those succeed by matching it to the build.prop or the build.prop to it) or remove the entire top assert line from META-INF/com/google/android/updater-script in the ZIP. That issue will be fixed in the next release.
[Samsung Galaxy Player 4.0, 5.0] gskillivenom:
Ok I got it fixed now :) Thanks.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
usa keylayout only? not even a chance to test it ; )

too bad
[Samsung Galaxy Player 4.0, 5.0] gskillivenom:
You can enable the software keys on the earlier super-alpha version.

1. Flash the ROM and GApps if u need to

2. When the rom boots , go to the play store and download root browser lite

3. Go to build.prop

4. Go to the very bottom of the prop and type in this qemu.hw.mainkeys=0 and then Save.

5. Turn off the devices and turn it back on ( because reboot doesent work)
[Samsung Galaxy Player 4.0, 5.0] KOala888:
always a solution ;)

thanks a lot, gonna try it later.

Maybe I will try to help with the kernel
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
I don't know what modifications to make for Int'l. But I'd be happy to do them, as long as it still worked for USA.
[Samsung Galaxy Player 4.0, 5.0] Sultanxda:
At some point could Google Apps be baked into the ROM? I can never get it to flash properly.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Technically not quite legal, but as soon as CWM works, life will be easy. Until then, remember that all zips unmount /system when they are done, to make sure all changes get committed before you reboot. That means after flashing one zip, and before the next one, you have to go to "Mounts and Storage" -> "mount /system", otherwise nothing will happen (usually signified by a flash running really fast). I hope that helps!
[Samsung Galaxy Player 4.0, 5.0] gskillivenom:
Well on the new Alpha the build.prop doesent want to save , so INTL users cant test it. So maybe just somehow add soft keys?
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
Modify the framework-res.apk so that soft keys are enabled by default. I tried doing this on an earlier version, but it didn't boot after that. Maybe this method will work on the latest version
[Samsung Galaxy Player 4.0, 5.0] shahrukhraza:
hey guys... if cwm doesnt work then how do we get it back? like how do we get back to some other ROM?
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
You flash Entropys ROM with odin3
[Samsung Galaxy Player 4.0, 5.0] shahrukhraza:
ok... thanks bro

---------- Post added at 03:13 PM ---------- Previous post was at 03:09 PM ----------

and one more question guys... for the code you just need to put that in the terminak in ubuntu right? sorry for all the questions but better safe than sorry!:):thumbup::cool::D
[Samsung Galaxy Player 4.0, 5.0] KOala888:
shouldn't we use libs from device that has same audio chip and cm10?

like note probably? Idk if it has 2 speakers though.

Are your kernel sources ready to compile? Can I just download/modify and compile?

any recommended toolchains? any way of applying zImage?
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Which code? There's a lot on the thread. If you're referring to the second post, that goes in an adb shell or in a terminal on your device.

Aries ones worked. It's asound.conf that controls audio paths.

Yes and no. Kernel is ready, but initramfs must be built with android. For now just extract it from the latest existing kernel. I recommend google's prebuilt - the one that comes with the Android source. Just flash with odin (put in tar) or heimdall.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Right now the choppy audio is a kernel issue. I know this because I went back to ICS where audio worked fine and used the 3.0 kernel and the audio still sounded choppy. Right now I might make a kernel with everything from Gingerbread except for hardware acceleration just so people can have functioning jellybean while we continue work on the 3.0 kernel
[Samsung Galaxy Player 4.0, 5.0] KOala888:
i am not sure if I really understand it but I will try.

about jacpot idea, it is great.

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] Supermaster34:
Do you think it would be possible to get the GB+Hw acceleration kernel to work with ICS as well as JB? The current 3.0 kernel only seems to work with jb
[Samsung Galaxy Player 4.0, 5.0] KOala888:
with jellybean you mean

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
It would probably be best to see if it'll work with ICS first
[Samsung Galaxy Player 4.0, 5.0] gskillivenom:
I dont have any experience with editing APK's. Is it difficult ?
[Samsung Galaxy Player 4.0, 5.0] KOala888:
nope, please keep the topic....
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Right. If you look at /proc/asound/devices (I think), there's a timer device, which is our culprit I believe. I'm currently trying to re-forward-port some of the drivers, as I'm kind of OCD for knowing exactly what went into the kernel. (Yes, I know, git log... I have a bad/good habit of starting things over from scratch if they get too messy.)

Also, how did you get the kernel to go into recovery mode? I can't get it to use recovery.rc unless I use Samsung's Gingerbread /init, which doesn't work for loading anything but adbd (black screen). I'd really appreciate some insight into how that bootloader/init/*.rc interaction works. Thanks.
[Samsung Galaxy Player 4.0, 5.0] shahrukhraza:
OK yeah ... I was just asking about the second post... Thanks
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
I don't think I ever got a working recovery and normal kernel. I know that the cm7 boot image method allows for it to work. I'm most likely gonna use that for my backport of the necessary 3.0 kernel features. I'll make it so once the real 3.0 kernel is done, those files for the working Jellybean backport boot image can be used for the real 3.0 kernel
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Pardon my ignorance, but could you possibly point me to an explanation of this method? :fingers-crossed: I've literally spent days trying to figure out how CWM is integrated in the ramdisk. What boot image format does this method use? Does it have one initramfs or two? Thanks.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Cwm and a normal ramdisk are squeezed into the boot image. Most devices have a boot partition and a recovery, but the Samsung ones use the boot and recovery as one. Therefore, the kernel has a tiny faux initramfs which checks if we are booting into the system or recovery and extracts either ramdisk depending on if we are booting into recovery or not. Then after the chosen ramdisk is extracted, the faux init executes the actual init, which will properly initialize the system or recovery
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Ahh, makes sense now. So the initramfi are tacked onto the end of the zImage, but there is no header before it so the Samsung SBL will still load it, right? Then we can ship the kernel with an initramfs, and use the bootimg.mk to make the boot.img. Is there any specific offest/padding? I'll look at the cm9 one as an example.
[Samsung Galaxy Player 4.0, 5.0] JackpotClavin:
Kind of. The actual zimage just has the faux "init." The rest is done after the recovery image and normal boot image are created. From there the boot and recovery are wrapped into the zimage that contains the faux init script which is basically just a tiny script that checks /proc/cmdline to see if it's supposed to boot into recovery. Depending on what's there, it extracts the actual android or recovery ramdisk at / then executes the real init
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Ok, I understand that method now - that was the mkshbootimg.py in your device tree. But since I have neither the files nor the expertise to extract byte ranges from a currently running kernel image, I created a jellybean-test branch of the device tree implementing the idea I've seen on multiple devices, including here: https://github.com/DerTeufel/samsung-kernel-aries/blob/jelly_helly/usr/captivatemtd_initramfs/init

It boots normally or into recovery correctly with the button combos, but the script I wrote doesn't do the mounting and checking /cache properly, so reboot recovery doesn't work yet. Also, recovery shows a black screen (adbd still runs in recovery mode), so something needs to be fixed there - I'll look at the galaxy S/crespo source.

Last, I realized why we can't exit recovery. Since we have the new kernel, we can no longer use Samsung's param.ko module to reset the bootloader paramater, so the SBL still thinks we want to be in recovery - I had this same issue when I forgot to build modules on GB. So either we can't use the combo, hack the param partition, or go back to 2.6 and backport junk.

Edit: I just saw ambrice's kernel source and now feel insanely stupid. /facepalm Ok, well I will combine everything tomorrow.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
can anybody post initramfs of mevordel kernel? somehow script that extrcts it from zImage doesn't work fir me. I would be very grateful. I need them to compile kernel and help you guys or add some mine features.

Or could you mevordel push it to your git?

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Yes, once I finish writing it ;)
[Samsung Galaxy Player 4.0, 5.0] KOala888:
awesome then :) I will be checking your git regurally

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
See my signature down there? Yes, I'm using the XDA app on jellybean! Latest build has recovery working using Aries graphics.c (which should be perfectly fine) and a combined ramdisk (see shbootimg.mk). I used it to flash the currently uploading cm10 alpha, wipe data, then reboot and delete stuff to free space. Then I went back using reboot recovery in the power menu and flashed gapps, and installed XDA app in the Play Store.

UBER-ULTRA-IMPORTANT NOTE:

I have not yet tried backup and restore, so until tomorrow use those at your own peril. Also DO NOT use the button combo to enter recovery! You will not be able to get out until you flash back to Entropy's and select 'reboot system now'.

Edit: Rom is up. Happy flashing.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
thank a lot for initramfs, I will try to compile asap

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] omaroe666:
Played around with this and when i tap from sound to silent mode on notification bar it keeps staying on silent mode and won't go to sound mode anymore. and can i flash a home button patch on jelly bean im running this on a intl version and the rom is a us version right ? awsome rom and you guys making a great progress :victory:
[Samsung Galaxy Player 4.0, 5.0] dosdude1:
The notification sound toggle getting stuck on silent mode is because the sound is not yet working properly.
[Samsung Galaxy Player 4.0, 5.0] DZonikg:
You cant flash because that patch is for ICS and that patch is just another kernel so you will overwrite existing kernel..i 2 have international..you can download button saviour from market until some better
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Today's nightly has a special treat: Storage settings fc's, and build.prop definitely needs tweaking, but INTERNAL STORAGE NOW WORKS! :D (with no hacks that is). Features also include updated CM10 (4.1.2) codebase, some cleanup tweaks, and a patch to the kernel that (hopefully) enables the home button on European devices.

Uploading now, will update OP when done. Uploaded and updated. As soon as sound is fixed, we move to beta stage. :highfive:

P.S: CWM backup/restore/format/etc. has been tested and works fine for me, so happy flashing!
[Samsung Galaxy Player 4.0, 5.0] YoBob:
This means we can flash this through CWM ? Like one step flash?

Sent using xda app-developers app
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Yes. As long as you don't use the button combo on the 3.0 kernel to get there, because if you do, you can't get out of CWM except flashing a GB kernel and rebooting and going back... basically a mess.
[Samsung Galaxy Player 4.0, 5.0] YoBob:
Is the 3.0 kernel in the Alpha 4 zip or at your kernel source link? Also, if we don't access CWM through button combo, then how do we go into recovery?

Sent using xda app-developers app
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
In the Alpha 4. Power menu -> reboot recovery or type reboot recovery in a shell.
[Samsung Galaxy Player 4.0, 5.0] KOala888:
good news. I see in the first post that sound problem is about libs. So using ones from device with same DAC should help, am I right?

Wysyłane z mojego YP-G70 za pomocą Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
Yeah, if you can get the right ones from another 4.1.2 build or at least compatible ones

Sparx639
[Samsung Galaxy Player 4.0, 5.0] KOala888:
what should I replace?

I mean where can I find libs responsable for sound?
[Samsung Galaxy Player 4.0, 5.0] Sparx639:
Look for a device with the same sound chip, I heard another galaxy tab uses it and has cm10. Just take the libs that have something to do with audio and shove em into ours

Sparx639