[WIP/DEV] [April 14th] 3.0 Kernel and CM10.1 for the Samsung Galaxy Player 5.0

This will be our development thread so we will no longer clog up Mevordel's CM10 thread.

There's still the partitioning issue I need to figure out for everybody else's Players fixed 3/27
The camera still doesn't work fixed FFC 100%, rear still does not work
Audio won't play out headphones even though they're plugged in fixed 3/28
No bluetooth fixed 4/9
Plugging the device into a charger ALWAYS assumes it's plugged into a USB even if plugged into an AC outlet fixed 4/9
GPS might not acquire a lock, but I believe I found a solution fixed 4/2

Before installing, backup your current setup!

Here's my CM10.1 alpha with my 3.0 kernel that I've been working for the past month or so:

If coming from any ROM OTHER THAN CM10.1:

I just installed the linked CM10.1 build coming from CM10, Paranoid, and Entropy's clockwork recovery from a year ago and had no issues; so hopefully you guys will too. Do me a favor and prior to installing wipe /system, /data, /dbdata (or /datadata or something), and /cache; THEN install. Don't wipe after or else you might wipe the /system_app directory that we're using to install the /system/app on a different partition because our /system isn't large enough.

If coming from a previous version of CM10.1

My zips wipe your /system and /system_app directory (which is the /system/app partition symlinked). That means that you will have to reinstall the Gapps package at the end of every zip! Also, go to the advanced menu in clockwork and wipe your dalvik-cache

In order to boot into recovery after installing this ROM, you must enable development settings by pressing on the build number in the Settings app 7 times; then go into development settings and enable "Advanced reboot." Then reboot your device by holding power and selecting recovery.

The standard CM10.1 Gapps package from http://goo.im/gapps/ will work and fit on our devices



4/14 (Third build: fixed Bluetooth, fixed AC charging, fixed touchscreen scrolling/zooming being weird, rebooting into recovery with Volume up + power now works!, kernel version from 3.0.72 to 3.0.73, CM10.1 source synced 4/14 3:20PM EST, Still no rear camera)
April 14th
md5sum: 041296ca25b4b33c97f83aed543aee13 cm-10.1-20130414-UNOFFICIAL-venturi_usa.zip (it's signed as well)
Remember to install Gapps after you install the ROM!

If you have a non-US Galaxy Player 5, install the correct boot.img after you install the ROM:
International device: http://www.mediafire.com/?pu0p12s7g9coo4q
# Korean device: Try using the international kernel above since the camera does not work, anyways



4/7 (Second build: fixed GPS lock, FFC, .android_secure is on the external sdcard, kernel version from 3.0.70 to 3.0.72, CM10.1 source synced 4/7 1:00PM EST)
Since the .android_secure folder was on the internal sdcard in the first zip, it will be correctly-placed on the external sdcard in this one. Because of this, you should move your apps that are currently on the sdcard back to the phone or else you will lose them when you install this new zip. After it's installed, you can move them back to the sdcard.
April 7th
md5sum: 02b7949c9f88f472260af802c18a4065 cm-10.1-20130407-UNOFFICIAL-venturi_usa.zip (it's signed as well)

4/2 (Alpha build: first .zip, no GPS lock, camera, bluetooth, .android_secure is on internal sdcard)
April 2nd
md5sum: 0f781b90fb4232c24dadce602dd26fd5 cm-10.1-20130402-UNOFFICIAL-venturi_usa.zip (it's signed as well)

Hope you guys enjoy CM10.1 with the 3.0 kernel

Re: [WIP/DEV]3.0 Kernel and CM10.1 for the Samsung Galaxy Player 5.0

This ROM was built from vibrantmtd and aries-common sources from the CyanogenMod team. The three source trees used (device, vendor, and kernel) provided a fantastic
base for modifying them to run on the Galaxy Player 5.0 USA (venturi_usa). Most files were merely modified to accommodate for the differences between the Aries devices' hardware and that of the Galaxy Player 5

Device source: https://github.com/JackpotClavin/android_device_samsung_venturi_usa
Vendor source: https://github.com/JackpotClavin/android_vendor_samsung_venturi_usa
Kernel source: https://github.com/JackpotClavin/android_kernel_samsung_venturi galaxyplayer5_defconfig

Pro tip:

If you are making kernel modifications, instead of building the entire ROM just to see your kernel modifications, try typing:

. build/envsetup.sh
lunch cm_venturi_usa-userdebug
mka installclean
mka bootimage

This will generate your boot.img (should be around 5.6MB)

Re: [WIP/DEV]3.0 Kernel and CM10.1 for the Samsung Galaxy Player 5.0

Mmmm-) said:

Now I don't really know what I'm talking about here, but you mentioned that you removed an unneeded partition to free up more space for gapps etc, but this basically mucked up the naming of the partitions right? What if, instead of deleting the partition, you just made it very very small? Then you'd free up space and there'd be no renaming problem!

Would that help?

I apologise if I'm talking complete rubbish.

Click to expand...

Click to collapse

Yep I think that's exactly what we're going to do. I don't know how to implement this however because people's partition maps vary depending on the device

Sent from my Galaxy Nexus using xda app-developers app

Re: [WIP/DEV]3.0 Kernel and CM10.1 for the Samsung Galaxy Player 5.0

I did it in recovery with adb using the fdisk command. The thing is that you need to manually do it because it requires keyboard input to enter the values for which block you're partitioning up to. Even if I could use a script, it's risky because not everybody's partitions land on the same block because our devices are weird and finicky

Sent from my YP-G70 using xda app-developers app

Re: [WIP/DEV]3.0 Kernel and CM10.1 for the Samsung Galaxy Player 5.0

arceusg said:

I notice earpiece isn't in the bug list. Is it fixed in CM10.1?

Sent from my YP-G70 using xda app-developers app

Click to expand...

Click to collapse

Not sure about that. What app can I use to test that out?

Sent from my YP-G70 using xda app-developers app

I think what I'm gonna do is have the actual /system/app directory installed on the /dbdata partition which should be enough for the entire stock ROM + gapps that normally are stored on /system/app. So after the partitions are mounted as directed by the init.venturi.rc, I will symlink /dbdata/app with /system/app so Android will be spoofed into thinking everything is 100% normal

Edit: Now I don't think that will work since symlinks are destroyed once the filesystem is mounted in recovery

The issue here is that in recovery, we want the installation of the ROM to install to /system, but I want the /system/app directory to be on a different partition as the actual /system, but if I symlink /system/app to another partition, then mount the /system partition, then that /system/app symlink gets destroyed on mount, and installing the ROM will install the entire thing to the /system partition, which is not large enough for the ROM + Gapps.

If I get everything working 100% I'd like to submit the device for official CyanogenMod nightlies, but I don't think they will take it if so many hacks have to be done like cutting down on the things installed to the /system or using a non-standard Gapps package. I think the best course of action will be to re-partition the device and make /dbdata as small as possible, so we will still have 17 mmcblk partitions and won't upset any recoveries which may lead to data loss like I did to my device before.

I also might bump up the RAM allocation for MFC0 and MFC1 to stock values, which will make the RAM available for userspace apps a bit less than 412 MB free (more like 390-something)