Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

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

OP Mevordel

3rd September 2012, 09:16 PM   |  #1  
OP Senior Member
Thanks Meter: 1,033
 
925 posts
Join Date:Joined: Apr 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_...ng_venturi_3.0
Initramfs for 3.0 kernel: https://github.com/Mevordel/venturi_cm10_initramfs
Last edited by Mevordel; 2nd June 2013 at 05:33 AM.
The Following 35 Users Say Thank You to Mevordel For This Useful Post: [ View ]
3rd September 2012, 09:24 PM   |  #2  
OP Senior Member
Thanks Meter: 1,033
 
925 posts
Join Date:Joined: Apr 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."
Last edited by Mevordel; 2nd January 2013 at 05:07 AM.
The Following 22 Users Say Thank You to Mevordel For This Useful Post: [ View ]
3rd September 2012, 10:11 PM   |  #3  
Cm9aphla's Avatar
Senior Member
Flag South Holland
Thanks Meter: 46
 
126 posts
Join Date:Joined: May 2012
Donate to Me
More
good now you and jackpot clavin are working on a 3.x kernel
3rd September 2012, 10:40 PM   |  #4  
gmillz's Avatar
Senior Member
Flag Shreveport
Thanks Meter: 1,739
 
720 posts
Join Date:Joined: Mar 2012
Donate to Me
More
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
3rd September 2012, 10:43 PM   |  #5  
spartacus279's Avatar
Senior Member
Flag New York
Thanks Meter: 15
 
105 posts
Join Date:Joined: Jun 2012
Looks great, is there any way I could help with patching the 3.0xx kernel?
3rd September 2012, 11:45 PM   |  #6  
OP Senior Member
Thanks Meter: 1,033
 
925 posts
Join Date:Joined: Apr 2012
Quote:
Originally Posted by gmillz

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.

Quote:
Originally Posted by spartacus279

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
4th September 2012, 12:10 AM   |  #7  
zaclimon's Avatar
Recognized Contributor
Flag Montréal
Thanks Meter: 2,817
 
3,397 posts
Join Date:Joined: Aug 2011
Donate to Me
More
Quote:
Originally Posted by Mevordel

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 .
4th September 2012, 12:41 AM   |  #8  
OP Senior Member
Thanks Meter: 1,033
 
925 posts
Join Date:Joined: Apr 2012
Quote:
Originally Posted by zaclimon

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.
4th September 2012, 12:53 AM   |  #9  
Account currently disabled
Thanks Meter: 269
 
1,586 posts
Join Date:Joined: Oct 2011
great share!Thanks for your work!
4th September 2012, 01:08 AM   |  #10  
zaclimon's Avatar
Recognized Contributor
Flag Montréal
Thanks Meter: 2,817
 
3,397 posts
Join Date:Joined: Aug 2011
Donate to Me
More
Quote:
Originally Posted by Mevordel

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?

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes