[DEV][4.X][YP-G70]Jellybean and 3.0 Kernel Work (OLD)

Mevordel · Sep 3, 2012

History
JackpotClavin first got a 3.x kernel working on the SGP5.0. He used this kernel and a modified Captivate firmware to release a CM10 "preview." Since then, he has done some work on fixing kernel issues, and I worked on trying to fix some things in Android, releasing a "pre-alpha." However, we were limited by the fact it was ported, not built. It took quite a while, but I finally figured out the Android build system and created a device tree. Well, as of 21 November, it has matured enough to create a zip that installs and boots cleanly, and so has entered the "alpha" stage. On November 27, a functional CWM was attained, and on November 28, internal storage was fixed. Then we decided to use the 2.6.35.7 stock-based kernel with back-ported drivers. After a month of off and on work, it booted usably. Things like vibration and button lights were easy to fix, but wi-fi drivers were a headache. So I decided to, for now, use the old and slow ones, because at least they work. A lot of work was done the last week of December, and by New Year's Day, the only things left broken were audio, Bluetooth, and the camera. Well, come to find out Galaxy Tab audio and camera HAL work on our device. So by the end of the day, I had gotten to what I consider a beta.

Going Forward
Now that the beta is out, this thread is for development discussion only.
Eventually, we will probably go back to the 3.0 kernel, but not for a while.

local_manifest.xml for CM10

Code:

<?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" />
  <project name="Mevordel/android_system_vold" path="system/vold" remote="github" revision="jellybean" />
  <project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
</manifest>

Other Git Links
3.0 Kernel source: https://github.com/Mevordel/android_kernel_samsung_venturi_3.0
Initramfs for 3.0 kernel: https://github.com/Mevordel/venturi_cm10_initramfs

Mevordel · Sep 3, 2012

Download
The beta is out. Use it. These are for historical / testing / file-yanking purposes only.
Alpha 7: http://www.mediafire.com/?3ji7u4ifx53v4vy - fixes rotation, almost fixes storage (both), enable int'l home button & software buttons, fixes gps
Alpha 6: http://www.mediafire.com/?yasfuv630v743gr - fixes wi-fi (old drivers), external storage, vibration, button lights
Alpha 5: http://www.mediafire.com/?9u1dhu8qlz6euy4 - first with kernel 2.6.35
Alpha 4: http://www.mediafire.com/?c36chfcrsde7s6s - added storage
Alpha 3: http://www.mediafire.com/?c8o33cjb19rw8zf - added CWM
Alpha 2: http://www.mediafire.com/?9nkguo3y62dwyxl - added WiFi
Alpha 1: http://www.mediafire.com/?nuou91atn1x03tw - built from source
Pre-Alpha: http://www.mediafire.com/?xfaiw6i57cqdexf - captivatemtd port

Workarounds (must be applied each boot)
To enable GPS (Alpha 6 and earlier)
Run as root:

Code:

gpsd -d /vendor/etc/gps.xml

To trick vold and mount internal storage (Alpha 3 and earlier)
Run as root:

Code:

rm "/dev/block/vold/179:8"
mknod "/dev/block/vold/179:8" b 259 9

Then run 'vold' or go to Settings -> Storage and click "Mount."

Cm9aphla · Sep 3, 2012

good now you and jackpot clavin are working on a 3.x kernel

gmillz · Sep 3, 2012

It would he great if we could get a 3.4 kernel. It would make everything easier

Sent from my YP-G70 using Tapatalk 2

spartacus279 · Sep 3, 2012

Looks great, is there any way I could help with patching the 3.0xx kernel?

Mevordel · Sep 3, 2012

gmillz said:
It would he great if we could get a 3.4 kernel. It would make everything easier

The way I'm doing it now is through the kernel.org incremental patches. So going to 3.4 would just mean a few more patches.

spartacus279 said:
Looks great, is there any way I could help with patching the 3.0xx kernel?

Sure. I posted what I'm doing at the top of the 2nd post. I'm working my way down. If you or someone else wanted to start somewhere else in the list then just reply so I know, and send me the files you've edited when you're done.

Just in case, to explain what I'm doing, I'm trying to edit the listed files so they do not cause conflicts when I apply the mentioned patch. So what I'm doing is attempting to patch, looking at the "rejects file," and noting what the file is "supposed" to look like before patching - that is, before the "+" lines are added and the "-" lines are removed. The reason the patches fail is because the file doesn't look like that. So I'm editing the files in the appropriate places so that they do match up.

If you don't understand, feel free to ask questions, and if you still don't think you can help, that's OK too. Not everyone is cut out to be a kernel dev

zaclimon · Sep 3, 2012

Mevordel said:
The way I'm doing it now is through the kernel.org incremental patches. So going to 3.4 would just mean a few more patches.

Sure. I posted what I'm doing at the top of the 2nd post. I'm working my way down. If you or someone else wanted to start somewhere else in the list then just reply so I know, and send me the files you've edited when you're done.

Just in case, to explain what I'm doing, I'm trying to edit the listed files so they do not cause conflicts when I apply the mentioned patch. So what I'm doing is attempting to patch, looking at the "rejects file," and noting what the file is "supposed" to look like before patching - that is, before the "+" lines are added and the "-" lines are removed. The reason the patches fail is because the file doesn't look like that. So I'm editing the files in the appropriate places so that they do match up.

If you don't understand, feel free to ask questions, and if you still don't think you can help, that's OK too. Not everyone is cut out to be a kernel dev

How do you patch? This could be interesting for the 4.0 users

.

Mevordel · Sep 3, 2012

zaclimon said:
How do you patch? This could be interesting for the 4.0 users .

In addition to releasing a source tarball for each kernel release, kernel.org also releases patches (at the bottom) that will upgrade your sources from the previous release (to conserve bandwidth, etc.). I'm using those patches, but most of the work is cleaning up where Samsung and mainline both modified files.

john9 · Sep 3, 2012

great share!Thanks for your work!

zaclimon · Sep 4, 2012

Mevordel said:
In addition to releasing a source tarball for each kernel release, kernel.org also releases patches (at the bottom) that will upgrade your sources from the previous release (to conserve bandwidth, etc.). I'm using those patches, but most of the work is cleaning up where Samsung and mainline both modified files.

the patches are the .sign files right?

Mevordel · Sep 4, 2012

zaclimon said:
the patches are the .sign files right?

No, they are the patch - somenumber .bz2 or .xz, for example patch-2.6.12.xz

I just realized that the main kernel.org no longer keeps minor patches for that old of a release, so you'll have to look on a mirror.

hanthesolo · Sep 4, 2012

Are you sure this will work? I claim no knowledge whatsoever of kernels, but Oisis has been trying to boot a 3.0x kernel for the 4.0, and he's still missing these files:

CONFIG_VIBETONZ - drivers/misc/Kconfig:481 - missing in 3 - to do
CONFIG_TOUCHSCREEN_QT602240 - drivers/input/touchscreen/Kconfig:624 - missing 3 - to do
CONFIG_VIDEO_ISX005 - drivers/media/video/Kconfig:1142 - missing in 3 - to do
CONFIG_SENSORS_MMC31XX - drivers/misc/Kconfig:341 - missing in 3 - to do
INPUT_BMA222 - drivers/input/misc/Kconfig:55 - missing in 3 - to do

Perhaps you guys have them, perhaps not, but i'm just throwing that out there

.

EDIT: Now I seem like an idiot for not fully reading the OP

. It looks like you guys are missing many of the same files we are, but fortunately we only have these left to patch.

Mevordel · Sep 4, 2012

hanthesolo said:
Are you sure this will work? I claim no knowledge whatsoever of kernels, but Oisis has been trying to boot a 3.0x kernel for the 4.0, and he's still missing these files:

CONFIG_VIBETONZ - drivers/misc/Kconfig:481 - missing in 3 - to do
CONFIG_TOUCHSCREEN_QT602240 - drivers/input/touchscreen/Kconfig:624 - missing 3 - to do
CONFIG_VIDEO_ISX005 - drivers/media/video/Kconfig:1142 - missing in 3 - to do
CONFIG_SENSORS_MMC31XX - drivers/misc/Kconfig:341 - missing in 3 - to do
INPUT_BMA222 - drivers/input/misc/Kconfig:55 - missing in 3 - to do

Perhaps you guys have them, perhaps not, but i'm just throwing that out there .

EDIT: Now I seem like an idiot for not fully reading the OP . It looks like you guys are missing many of the same files we are, but fortunately we only have these left to patch.

I'm not sure what you mean by missing... All of the files are there in Samsung's stock kernel source, they just aren't the 3.x versions (if those exist).

Attached is some of those files, taken from my current working tree.

Neodymium · Sep 4, 2012

hanthesolo said:
Are you sure this will work? I claim no knowledge whatsoever of kernels, but Oisis has been trying to boot a 3.0x kernel for the 4.0, and he's still missing these files:

CONFIG_VIBETONZ - drivers/misc/Kconfig:481 - missing in 3 - to do
CONFIG_TOUCHSCREEN_QT602240 - drivers/input/touchscreen/Kconfig:624 - missing 3 - to do
CONFIG_VIDEO_ISX005 - drivers/media/video/Kconfig:1142 - missing in 3 - to do
CONFIG_SENSORS_MMC31XX - drivers/misc/Kconfig:341 - missing in 3 - to do
INPUT_BMA222 - drivers/input/misc/Kconfig:55 - missing in 3 - to do

Perhaps you guys have them, perhaps not, but i'm just throwing that out there .

EDIT: Now I seem like an idiot for not fully reading the OP . It looks like you guys are missing many of the same files we are, but fortunately we only have these left to patch.

QT602240 Is not needed. It is already included in kernel named xt2240. And all the files you have listed is the differences between galaxy s and galaxy player

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

theraf · Sep 4, 2012

Neodymium said:
QT602240 Is not needed. It is already included in kernel named xt2240. And all the files you have listed is the differences between galaxy s and galaxy player

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

surely you can just pull these files from the samsung opensource website

Sparx639 · Sep 5, 2012

How do you build kernels? I would help but don't know too much about it. I can learn easily though

zaclimon · Sep 5, 2012

theraf said:
surely you can just pull these files from the samsung opensource website

Yeah but the qt and mxt drivers are for the same touchscreen which the the MXTxxx (I don't remember the model).

Mevordel · Sep 5, 2012

Sparx639 said:
How do you build kernels? I would help but don't know too much about it. I can learn easily though

First, it requires a working Linux environment. When you download the source code, some pointers are in the README_Kernel.txt file, and Entropy512 created a nice helper script, called build-linux-yp-g70usa. I'd look there first. Also useful is the "configuring the kernel" section in the main readme.

In short:
1. download toolchain (listed in Readme_kernel), kernel source (from Entropy's or my github or samsung opensource [see OP]) and initramfs source (from Entropy512's github).
2. edit Makefile (search for "cross_compile") to point to toolchain.
3. open a terminal in kernel folder
4. type ./build-linux-yp-g70usa
5. if it all works, you'll have a heimdall/odin-flashable zImage in arch/arm/boot/

omaroe666 · Sep 5, 2012

i was thinking guys ? is the flashlight working ? like the camera is now letting the device hot reboot if you open it but can you use the flash ? im not asking for eta's i was just thinking if the flashlight would work ?

Neodymium · Sep 5, 2012

I didn't see the GB70 source but maybe it would be same as the method used to GB1-just change camera source

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

[DEV][4.X][YP-G70]Jellybean and 3.0 Kernel Work (OLD)

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Inactive Recognized Contributor

Senior Member

Senior Member

Inactive Recognized Contributor

Senior Member

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Inactive Recognized Contributor

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts