Database Info

[BETA 2] AOSP Gingerbread 2.3.7

Hi Guys....I'm PROUD to release the first BETA of the AOSP rom!)) Let's see the features:
AOSP pure code based on 2.3.7
kernel .35
REVERTED TO AOSP LOCKSCREEN-NEW!!!!!!!!!
Imported power menu from CyanogenMod ( imported only reboot.h library )
USE OF ALL APPS FROM AOSP SOURCES-NEW!!!
Used Mik_os frameworks folder for resolve many bugs so maybe you can find traces of CyanogenMod code
Rooted during compilation
NEED GBAPPS TO FLASH MARKET!!!!(ALSO AOSP NEED THIS AND THIS IS A SURPRISE FOR ME)
FOR OLD BASEBAND!!!!
MODIFIED SURFACEFLINGER.H AND SURFACEFLINGER.CPP TO SUPPORT PERSIST.SYS.USE_16BPP_ALPHA TO GAIN SMOOTHNESS WHEN SCROLLING
OVERALL UI PERFORMANCES GAINED-NEW!!!!!
MODIFIED A BIT EGL DRIVER(@729 OBTAINED 300FPS IN 1ST QUADRANT TEST AND 15 FPS IN 3THD QUADRANT TEST)-NEW!!!!
IMPLEMENTED LATEST FRANCO.KERNEL-NEW!!!!
FIX FOR ELECTRONBEAM ANIMATION THAT LIGHTS UP AFTER UNLOCK(maybe a bug in StageFright replaced with CAF but i need test)-NEW!!!!!
SOME OPTIMIZATIONS CODE!-NEW!!!!!
FIXED HSDPA ICON!(NOW IT SHOWS CORRECTLY)
It works:
Usb
Wifi
adb
audio
sd
gps
camera
shutdown
Usb
GSM-NEW!!
UI-NEW!!
BLUETOOTH-NEW!!
ACCELEROMETHER-NEW!!!!!
doesn't work:
ScreenShots
Headset icon is not showing in statusbar but headset are workin'
AOSP browser still don't work
here the link for the download:http://www.multiupload.com/C1SBJLC0UL
Thanks to
Mik and Andy for help me fixing some bugs
FranciscoFranco for his kernel
drnotor for help me with annoynig NTFS filesystem (looooool)
*******WHAT'S NEXT*************
Workin' on ICS!!!!

Was waiting for a aosp rom, good luck with this.

Thanks for yuA hard work
Sent from LG O¹ • miks cyanogen7.1 with latest testing release kernel v1.1 and v19.3♦• using tapatalk

I really hope you'll make this work, an AOSP rom is just what I would like now.
Good luck with your work!
BTW, if you need some beta testing I think I can help you

Finally a nexus s I CAN AFFORD! Thanks!

Wasn't andy's ROM AOSP too?

ciaox said:
Wasn't andy's ROM AOSP too?
Click to expand...
Click to collapse
Yes it was, but now we don't have another one...

ciaox said:
Wasn't andy's ROM AOSP too?
Click to expand...
Click to collapse
22VIN said:
Yes it was, but now we don't have another one...
Click to expand...
Click to collapse
Yes and no. Andy's rom was based on CAF code (if i remember correctly). CAF code is based on AOSP but it is a different code. Mine rom is based totally on Google code.
Howewer i had an idea......AOSP android 2.3.5 doesn't allow to use 2.2 libraries(i thinked so but it isn't unfrotunately) like CM7.....and i've used these from mik's github...we have a gingerbread update and so 2.3 libraries...i can retrieve these with dsxida's kitchen.....then try to recompile the entire system (even if lg **** 2.3.3 code will doesn't annoying me)but i have the suspect that i must use the new baseband.......see what happens in the next days

any update??????

He has started the thread yesterday only. Let us give him some time to work on it first.

Ok, one question... Is it based on .32 kernel or .35 kernel? Or best someone who ports .38 kernel...
Sent from LGE XDA phone wit Matt's v6.5.7(1.1)

dax4182 said:
Ok, one question... Is it based on .32 kernel or .35 kernel? Or best someone who ports .38 kernel...
Sent from LGE XDA phone wit Matt's v6.5.7(1.1)
Click to expand...
Click to collapse
based on .35 kernel!....now i'm trying to resolve gsm problem (maybe it is a binder problem i've applied some fixes)!

lupohirp said:
based on .35 kernel!....now i'm trying to resolve gsm problem (maybe it is a binder problem i've applied some fixes)!
Click to expand...
Click to collapse
Cool, hope never bricks my phone...
Sent from LGE XDA phone wit Matt's v6.5.7(1.1)

gkarthik16 said:
He has started the thread yesterday only. Let us give him some time to work on it first.
Click to expand...
Click to collapse
Yeah!! But eager to know about his awesome working progress
Sent from my LG-P500 using Tapatalk

grrrrr... NOTHING!!!! it still gave me the same error!(((
Code:
rild
dlopen failed: Cannot load library: link_image[1962]: 2048 could not load neede
d library 'liblgdrm.so' for 'libril-qc-1.so' (reloc_library[1311]: 2048 cannot
locate '_ZNK7android6Parcel16enforceInterfaceERKNS_8String16E'...
)
i've reworked the parcel adding this in PARCEL.CPP
Code:
// LGDRM Section for rild
bool Parcel::enforceInterface(const String16& interface) const
{
return enforceInterface(interface,NULL);
}
and in Parcel.h
Code:
#ifdef _INTERNAL_BINDER_PARCEL_
bool enforceInterface(const String16& interface) const;
#endif
but without success ((((...could anyone help me????i don't think it is only a permission problem.....

Need more patient i think, i saw andy have problem like u... u can read on his topic, before he build last rom and after he delete cm7 rom.. he said something strange with code.. i think u need go and search on another forum.
Have a good luck sir, hope u still doing this project...
Sent from my LG-P500

lupohirp said:
grrrrr... NOTHING!!!! it still gave me the same error!(((
Code:
rild
dlopen failed: Cannot load library: link_image[1962]: 2048 could not load neede
d library 'liblgdrm.so' for 'libril-qc-1.so' (reloc_library[1311]: 2048 cannot
locate '_ZNK7android6Parcel16enforceInterfaceERKNS_8String16E'...
)
i've reworked the parcel adding this in PARCEL.CPP
Code:
// LGDRM Section for rild
bool Parcel::enforceInterface(const String16& interface) const
{
return enforceInterface(interface,NULL);
}
and in Parcel.h
Code:
#ifdef _INTERNAL_BINDER_PARCEL_
bool enforceInterface(const String16& interface) const;
#endif
but without success ((((...could anyone help me????i don't think it is only a permission problem.....
Click to expand...
Click to collapse
Better, you use CAF instead of AOSP: CAF is optimized for MSM devices,
so you have some more luck to get things work.
BTW: RILD cant be used as a compiled thing from android source, LG has
many modifications made to use the baseband. these baseband version
differs in AOSP and CAF/CM7, so better use compiled **** from LG - that should
work.

andy572 said:
Better, you use CAF instead of AOSP: CAF is optimized for MSM devices,
so you have some more luck to get things work.
BTW: RILD cant be used as a compiled thing from android source, LG has
many modifications made to use the baseband. these baseband version
differs in AOSP and CAF/CM7, so better use compiled **** from LG - that should
work.
Click to expand...
Click to collapse
infact i'm downloading the coeduarora sources and try their rild libraries ...BTW i've maded some modifcations to opensource gralloc (set 16 bit per pixel instead of 32 bit in framebuffer.cpp to gain more smoothness ) but i dunno how to compile it.....i've only to copy the libgralloc folder in device/lge/thunderg and then compile or i must call somewhere in the device folder????sorry for the dumb question but i'm very new to android ((

lupohirp said:
infact i'm downloading the coeduarora sources and try their rild libraries ...BTW i've maded some modifcations to opensource gralloc (set 16 bit per pixel instead of 32 bit in framebuffer.cpp to gain more smoothness ) but i dunno how to compile it.....i've only to copy the libgralloc folder in device/lge/thunderg and then compile or i must call somewhere in the device folder????sorry for the dumb question but i'm very new to android ((
Click to expand...
Click to collapse
I'm not even sure P500 supports 32-bits framebuffer, not even my x5 does so that was a good call.

franciscofranco said:
I'm not even sure P500 supports 32-bits framebuffer, not even my x5 does so that was a good call.
Click to expand...
Click to collapse
infact i use the opensource libgralloc.....and i founded that it use a 32-bit per pixel (think was the reason also to the strange UI behaviour that i have) i set 16 bit and see...also made some changes to framework....now i'm going to recompile to see what happens...i've copied only libgralloc folder in device

[KERNEL] The unknown kernel for I9103LA build with CWM 5.0.2.8 [REV 1.2a]

So this is it, this is the patched I9103ZCLD4 kernel with voodoo sound, but also with the latest CWM built from CM repo as well as ro.secure = 0.
The rev 1.2a builds have made the following changes :
- Boost the performance change by using several specific gcc and linker options.
- Make a kernel based on I9103ZCLD4 instead.
However the following parts still remain, and I will finish them once I made the I9103XWLA4 build :
- Try to compile the kernel with '2 way calling recording enabled'
- Made modification on the default.prop and init.rc which can further boost the performance.
- Try to port touchable recovery to the system.
- Update recovery image to use I9103ZCLD4 recovery kernel.
So right now, it should be okay for you guys to install superuser from the market. And yea, enjoy the fun of using a rooted kernel.
Installation guide
---------------------------------------------------
Just flash the tar.md5 file via odin in the PDA tab.
---------------------------------------------------
To get rooted, just install superuser from the market. su binary is already put in the ramdisk to use.
Download : Revoked as the 1.2a causes problem on installing application
btw, since Rev 1.2a, my kernel will be called Ultimate kernel instead of Unknown kernel. I will add a string to build number to identify that later.
Back on working on XW build now.

UnknownzD if I knew that you would join our community I would think twice before I traded my SGR. You're really reviving and boosting development here. Great job!
It's really good to see SGR finally getting some real piece of android cake.

could you share? CWM 5.0.2.8

Serp87 said:
could you share? CWM 5.0.2.8
Click to expand...
Click to collapse
It is in the ramdisk already, just unpack it yourself.

I understand that the wipe Battery Stats in this version does not work!

Serp87 said:
I understand that the wipe Battery Stats in this version does not work!
Click to expand...
Click to collapse
Thanks for pointing that out, I will work on patching it, if possible.

UnknownzD said:
Thanks for pointing that out, I will work on patching it, if possible.
Click to expand...
Click to collapse
it would be great if it works wipe Battery Stats in this version!

Hey unknown.
Great to hear, that you support us with stuff for i9103
Do you maybe know how to get bln (backlight LED notification) mod for the kernel, for using bln control on the i9103?
It would be so great to get bln for the galaxy r like sg2 or lg optimus
Greetz

A minor update has been released.
In this new r1.2a kernel release,
- Boosted the performance by using several specific linker and gcc options
- Updated to use I9103ZCLD4 kernel src instead

UnknownzD said:
A minor update has been released.
In this new r1.2a kernel release,
- Boosted the performance by using several specific linker and gcc options
- Updated to use I9103ZCLD4 kernel src instead
Click to expand...
Click to collapse
Dude, Galaxy R has separate recovery partition

Adi_Pat said:
Dude, Galaxy R has separate recovery partition
Click to expand...
Click to collapse
What ?
There's no link to your statement and his !
The iPad 2. Revolutionary. (jk)
No I don't care if you're anti-Apple.

EmoBoiix3 said:
What ?
There's no link to your statement and his !
The iPad 2. Revolutionary. (jk)
No I don't care if you're anti-Apple.
Click to expand...
Click to collapse
I quoted by mistake. I don't see recovery files in ramdisk. Galaxy R has separate recovery partition.
Sent from my GT-I9003 using xda premium

Adi_Pat said:
I quoted by mistake. I don't see recovery files in ramdisk. Galaxy R has separate recovery partition.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Ohhh , I see .
This was sent from a Galaxy Ace. Problem?

Trying to port kernel 3.0 for i9003, please help

Hello,
I have been porting kernel 3.0 to i9003 since last month.
Now, platform specific codes and most of the drivers are ported.
Today, I am able to finish the kernel build with minor warnings.
but I have problems customizing the init scrits to be used with the kernel.
Any help from more experience devs would be appreciated
Current status:
- Platform specific code and all drivers except battery are ported.
- The kernel is built successfully
- trying to pack it into normalboot.img
I can release the source now due to its size. ( asking a guy at github to increase my storage space). But will do asap.
Sorry to post in the wrong forum but I dont have permission to post in the dev forum.

crackerizer said:
Hello,
I have been porting kernel 3.0 to i9003 since last month.
Now, platform specific codes and most of the drivers are ported.
Today, I am able to finish the kernel build with minor warnings.
but I have problems customizing the init scrits to be used with the kernel.
Any help from more experience devs would be appreciated
Current status:
- Platform specific code and all drivers except battery are ported.
- The kernel is built successfully
- trying to pack it into normalboot.img
I can release the source now due to its size. ( asking a guy at github to increase my storage space). But will do asap.
Sorry to post in the wrong forum but I dont have permission to post in the dev forum.
Click to expand...
Click to collapse
Thank u very much! You could contact dhiru
Sent from my GT-I9003 using XDA

Great...but main question is that whether device boot or not??? Because many people have successfully compiled kernel 3.0 but device doesnt boot.

vishal24387 said:
Great...but main question is that whether device boot or not??? Because many people have successfully compiled kernel 3.0 but device doesnt boot.
Click to expand...
Click to collapse
That what I'm going to find out. For now, I'm trying to modify the init script and looking for help from some devs here to speed it up.

my wish- that you release it as fast as you can

R u using
This?
i have also used this guide n compiled a kernel 3.0 successfully packed it using dhiru's boot.img from alpha 6
i have also modified sum codes
but still no luck i think these files need alot of config changes!!!!
n lastly best of luck i hope u get success

sachin sharma said:
R u using
This?
i have also used this guide n compiled a kernel 3.0 successfully packed it using dhiru's boot.img from alpha 6
i have also modified sum codes
but still no luck i think these files need alot of config changes!!!!
n lastly best of luck i hope u get success
Click to expand...
Click to collapse
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).

crackerizer said:
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).
Click to expand...
Click to collapse
I will suggest u to start ur thread in development thread. In general section developers mostly dont come here. Also u should upload ur source code to github. It will help to other developers to look into ur source code & find out the problem.

vishal24387 said:
I will suggest u to start ur thread in development thread. In general section developers mostly dont come here. Also u should upload ur source code to github. It will help to other developers to look into ur source code & find out the problem.
Click to expand...
Click to collapse
He needs to pump up his post count first buddy
Sent from my GT-I9100 using xda premium

ephraim033 said:
He needs to pump up his post count first buddy
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
oh...I forgot about that Anyway how many posts one has to do so that he can post a thread in development section?

vishal24387 said:
oh...I forgot about that Anyway how many posts one has to do so that he can post a thread in development section?
Click to expand...
Click to collapse
Not sure, i think it's 10?
Sent from my GT-I9100 using xda premium

ephraim033 said:
Not sure, i think it's 10?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, 10!

crackerizer said:
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).
Click to expand...
Click to collapse
all we need is config file in /arch/arm/config for kernel 3.0 for our devices
all we have now is config file for kernel 2.6.7 thats wats preventing our devices to boot
i followed same procedure mentiond in that blog after that i used zoom config file edit it at some places wer i thought shud be a change like device name to galaxy sl etc
renamed it latona_galaxy_sl
even then no benefit but i havn't givn hope m still trying!!!!
main problem is that we dont know how to configurate config file as "make config" command gives a hell lot of options!!!!

@crackeziner is your 3.0 kernel booting ?

anuraagkochar said:
@crackeziner is your 3.0 kernel booting ?
Click to expand...
Click to collapse
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.

Skander1998 said:
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.
Click to expand...
Click to collapse
what can do now??

Skander1998 said:
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.
Click to expand...
Click to collapse
Just give it try. Don't let it down guys
Sent from my GT-I9003 using XDA

sachin sharma said:
all we need is config file in /arch/arm/config for kernel 3.0 for our devices
all we have now is config file for kernel 2.6.7 thats wats preventing our devices to boot
i followed same procedure mentiond in that blog after that i used zoom config file edit it at some places wer i thought shud be a change like device name to galaxy sl etc
renamed it latona_galaxy_sl
even then no benefit but i havn't givn hope m still trying!!!!
main problem is that we dont know how to configurate config file as "make config" command gives a hell lot of options!!!!
Click to expand...
Click to collapse
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.

crackerizer said:
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.
Click to expand...
Click to collapse
u mentiond that u r getting errors while compiling right?
that means ur deconfig file is still not correct
all the codes needs to be changed according to "kernel 3.0"
not by porting codes from other kernels or previous kernels
n lastly all drivers are already given in the source code thers nothing to change in it except that u just have to compile!!!!!!

crackerizer said:
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.
Click to expand...
Click to collapse
But did it boot?? Did u test that? When do u think u will be able to test that?

[DEV] team for building kernel version 3.6.11

For everyone who has knowledge in building kernels
we try to build kernel version 3.6.11 for our device using this source
we need to setup repo on github
can anyone download this source then push it to github so we can all work on it
thanks

Already tried it. The problem are the proprietary LinuStoreIII drivers.

MarcoToo said:
Already tried it. The problem are the proprietary LinuStoreIII drivers.
Click to expand...
Click to collapse
But Maroc-OS did it , Workaround ?

Might have modded the module API or sth. On a 'normal' compilation Linux ver and toolchain have to match
via XDApp

Is this kernel for something like jb or ics???

rather try to compile 2.6.35.14

Mohamed.Anwar said:
For everyone who has knowledge in building kernels
we try to build kernel version 3.6.11 for our device using this source
we need to setup repo on github
can anyone download this source then push it to github so we can all work on it
thanks
Click to expand...
Click to collapse
i downloaded it i am creating now a repo to upload it i think it will be uploaded in like 10-20 mins

GB is specified working with v2.6 kernel. I wonder if you'll succed. compared to v3.2 our kernel structure is a lot different. someone have tried to use v2.7 source code in the past but it didn't boot on GB rom.

You all don't understand
I can't do it my self as I'm a noob
I created this thread to make you build this kernel
I mean I'm 100% sure it's possible

i start uploading the files to my github
https://github.com/cosminx13/sgy_3.6.11_kernel_source
it will take some yime to add all the files because github client crash if there are over 15000 files in a sync

hi guys !
its is really hard ..
a lot of devs exp on world try and no sucess...
btw source of rasperry no is good for start on my opnion !
for port 3.x kernel will need know alls drivers useds on gy and need for backports a lot .... lol
would be more useful to try porting 2.6 kernel more current!
btw I updated in 1.3.3 kernel 2.6.35.14 the source for about 30%
but after that I completely corrupted the source! hehe
sorry my bad english !

finished uploading source to github please pm me your names to add you to the callaborators

Only little fix to patch from 2.6.35.7 to 2.6.35.14 but for 3.x.x its change lot kernel structur so goodluck guys..
Ps. Thanks whiteXP for.. u know..

[KERNEL][SOON] HakyKernel 3.1.2

Will be updated soon
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.

haky 86 said:
After done some google search about to find similar devices to our phone and some guys on Whatsapp group give me some useful information about Samsung Galaxy S Duos 2 that device share same broadcom chipshet but the kernel is more updated (3.4.5), so I decide to port this version to our phone Samsung Galaxy S2.
I start some tests witnout arch-capri drivers in kernel/samsung/3.4/arch/arm just to see if Android boot or not, the result was really fantastic so from today we can port 3.4 kernel without any problems.
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.
Click to expand...
Click to collapse
Okey. Is this for stock or asop based roms?

rs tony said:
Okey. Is this for stock or asop based roms?
Click to expand...
Click to collapse
for both roms :good::good:

thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone

SmzAmir said:
thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone
Click to expand...
Click to collapse
Sure once finish 5.1.1 i can recall other devs to share experience and make 3.4 work perfect:thumbup::thumbup:
Sent from my GT-I9105P using XDA Free mobile app

haky 86 said:
for both roms :good::good:
Click to expand...
Click to collapse
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?

cracker12 said:
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?
Click to expand...
Click to collapse
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.

haky 86 said:
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.
Click to expand...
Click to collapse
Thanks... Keep up

[*]23/04/2015:
-drivers are imported without problem.
-now i'm fix compilation errors to see if will done or not.

Hey u make this
It awesome
---------- Post added at 03:40 AM ---------- Previous post was at 03:37 AM ----------
Hope you will fixed the issues in future
Do it have enhanced gpu

Man, you do a lot of great work.

thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..

left it open haky..maybe they are busy for now..we need it bro

haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
sad news!
I was really looking forward if someone can port a new kernel, but as you said it's not an easy job and no devs are intrested

haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
So this one is really down? Hey, man, we need you, continue your work

why me? the best succeed I got is integrate part of capri's kernel archecture into 3.4 and entire code should be readpted to work on our phone. in case of even ported, I will not release the source coz I will not do the homeworks of others

3.1.2 Kernel
-update patch like 3.0.31 -> 3.0.32 is adapted as well.
-now im apply the patch to update the code see ya.

3.1.2 in progress
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance

haky 86 said:
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance
Click to expand...
Click to collapse
Upload your source man, else noone can help you
I hope you don't have just changed the version numbers...

no i didn't, here my new branch
https://github.com/hak86/android_kernel_samsung_galaxys2plus-common/tree/3.1.2-lp
Compilation is work fine, now i will try to compile with make -j4 bootimage to get the modules and use them on nebula's flashable.