Database Info

[Source] LGP506 (AT&T LG Thrive GoPhone)

http://www.multiupload.com/7FCS3EORXF
The source for the lgp506 (Aka LG Thrive), im hoping devs well get on this, and apply a p506 version for there existing roms, for them to work with the p506 correctly. Otherwise, from what i've been able to surmise is, the only issue with porting roms from the p500 to other variations seem to correlate from the kernel.
and in regard to the p506, the current cm7 rom port works, only the screen is 8-bit and showing only 3-4 pallets of blue.
Hope this source helps out.
if you dont like or cant use multiupload, other means to get the source is just going to http://www.lg.com/global/support/opensource/opensource.jsp and searching lgp506go.

its 2.2 or 2.2.x ?

ccdreadcc said:
its 2.2 or 2.2.x ?
Click to expand...
Click to collapse
i thought it was 2.2.1

Interesting
Searching the internet for phone specs.

I diff'ed the source against the P500 source.
Practically the only difference is that the P506 has two framebuffer(?) drivers (novatek and hitachi) rather than one (just hitachi), with runtime detection of hw.
Relevant kernel config is CONFIG_FB_MSM_MDDI_NOVATEK_HVGA.
Since /proc/mtd is the same for P500 and P506, I guess roms and recoveries go through with just this display glitch issue, but it'd be great to have a proper one.
Does anyone know whether it is possible to just replace the zImage in CWM/amon_ra, or a compilation is required?

I have installed a 2.2.1 P500 ROM on my P506 with my stock kernel and I can verify that the color issue is history. We just need devs to port there kernels to the P506 and we can utilize the ROMs for the P500.
Please devs help us Thrive / P506 users out a little!
Sent from my LG-P506 using XDA Premium App

Ciaox u use linux?

Any devs looking into this?
Sent from my LG-P506 using XDA Premium App

devs wont be interested, if p506 user base is very low. getting more p506 users to comment here might get devs attention ><

ccdreadcc said:
Ciaox u use linux?
Click to expand...
Click to collapse
Yes I do. Why?
BTW I love AT&T

What do you guys need? A kernel? If so get more users to coment this topic and I'll see if its reasonable to release a kernel with the extra framebuffer. But I need to be sure the user base of this phone is high enough, otherwise it's pointless.

We mostly need help with understanding the following:
Will sticking the stock P506 zImage in a cwm/amon_ra recovery, keeping the initrd and everything, just work? e.g., using mkbootimg.sh ?
The diff between P500 and P506 froyo kernels has the following changes. Are they all relevant? were some of these fixed upstream?
Novatek fb driver (and renaming of hitachi fb functions)
ami304 driver changes (support for gyro and pedometer?), including ami306 support(?) EDIT: it's the driver from Optimus V.
some minor added functionality in drivers/input/sensor/kr3dh.c
LG's fix for the touchscreen bug (?) in drivers/input/touchscreen/mcs6000_ts.c
Camera modifications (parameters, added sports scene) in /drivers/media/video/msm/isx005*
MMC changes, incl. not powering down sdcard on suspend
A change of BRCM_WLAN_SLOT to 100 instead of 2 (BCM432X related)
Units change (mul by 10) in drivers/power/msm_battery.c
USB changes in drivers/usb/gadget/msm72k*
added a call to sock_setsockopt in net/socket.c, function kernel_connect()
Would applying the diff to your kernel (or any froyo kernel) would just compile and work (assuming no conflicts)?
Would applying the diff to a gingerbread kernel work, or gingerbread has some major changes?
Is the change (at least the FB one) simple enough to convince you and/or other P500 kernel developers to incorporate it in your builds (so no fork needed)?
Thanks,
R.

+1 for interest, I've already rooted but when I looked into roms etc. for the P506 I found there weren't any so I'd be glad to test recoveries/roms

OK, I got some answers for my questions, and some new questions.
Swapping p506 zImage for p500 zImage in AmonRa 2.2.1b recovery soft-bricks. Fastboot FTW.
Swapping p506 boot.img in a stock P500h rom boots and works in full color, but the logcat is filled with an AMI304-related error.
E/AmitDaemon( 1289): [AMI304D] AMI304MID_IOCTL_GET_CONTROL error​(I also get "battery hot" warnings, but maybe they're unrelated).
Not sure if accelerometer works, had to restore nandroid.
webosguru: do you have this error as well?
I think I saw that some IOCTL codes have changed in the new ami304 driver, so I guess it should be skipped in custom compilation (or fix AmitDaemon, wherever it is).
EDIT: I think this could be also fixed by using system/bin/ami304d from the AT&T rom. I wonder what other native executables I should take from stock AT&T?
I cannot find the 3 buttons required to get to recovery. Power+Home gets to fastboot, with or without VolDown. I have to use adb or rom manager.
Any ideas?
When booting a recovery via fastboot boot recovery.img, keys are not functioning. adb works, so I can flash and/or reboot recovery, but why won't they work?
I tried to grab froyo source via the repo tool, but it seems to download every piece of code ever written and then fail with some missing manifests. Ideas?
Next thing I'll do is probably to deodex and debloat the stock AT&T rom.

just happy progress, however small, is being made. Lots of smiles today.

Pursuing the deodexed stock AT&T rom path, I found out that my stock backup is (next to) worthless; it didn't include OOB info, and unyaffs fails to extract it.
I used dd if=/dev/mtdX of=/sdcard/mtdX.img instead of nandroid. I wonder if dd'ing it back and then a nandroid backup would work.

I have been following this thread. I am new to android but can help with testing out kernels.
Sent from my LG-P506 using XDA App

Really would love to see some ROM development happen for the Thrive!
Sent from my LG-P506 using XDA App

webosguru said:
I have installed a 2.2.1 P500 ROM on my P506 with my stock kernel and I can verify that the color issue is history. We just need devs to port there kernels to the P506 and we can utilize the ROMs for the P500.
Please devs help us Thrive / P506 users out a little!
Sent from my LG-P506 using XDA Premium App
Click to expand...
Click to collapse
How did you do the install without a custom recovery? Or, if you have a custom recovery, which one did you use?
And, +1 re wanting a custom kernel from P506/P505.

sd_matto said:
How did you do the install without a custom recovery? Or, if you have a custom recovery, which one did you use?
Click to expand...
Click to collapse
Install CWM for Optimus One P500 via Rom Manager.
Recovery shows weird colors, but regular rom uses a different kernel.
Now pick your favorite P500 FroYo rom, replace boot.img with your original boot.img and flash via CWM.
I still do not advise it since the ami304 daemon has problems, btw.

Porting Roms Confusion

Okay this question has been bugging me for a while now. Everyone is waiting on RC aka Ricardo AKA..... on getting the ported p990 to then be ported over to p999. We have many fine Developers here like Eagleblood , Rafase282, tonyp, Kashamalaga and many MIA ones that may or may not return like nycelitemaster, owain94, x0xhellx0x and my favorite Mr. Apocalypse.
My question is simple and would love one of these guys to answer it if possible.
Why are we waiting for RC to port it over when anyone of you guy have done it before. Am I wrong when saying that most of you have ported P990 over to P999 before? I respect everyone I have named. You have brought new life to my G2X. JUst wondering why we wait for RC, like he is the only one who can do this. Please if I am missing something let me know. thanks

I believe they are waiting for a more stable release of CM10 for the P990 before they bother to port it over for the P999. They should have many of the same bugs that need to be worked out. There is no need to do it twice.

I felt the same thing. Can some of the Developers list above or others I missed confirm this? Maybe this can stop or slow down the rants. The only reason I feel it may not be a difficult thing to do it because of this guys post...
Lezo OS
Hello everyone.
This is a port of the P990 Lezo OS a CM based rom. I am not a developer, just someone who was lucky enough to have this work It's just another piece of a so called "Crack Flashing Series". There are plenty of roms provided to our community, and this also brings people with different likes and dislikes. I aim only to share some of the other roms out there with the community. Maybe you want to try something out inbetween updates from your favorite rom, well, try this.
None of this would out be possible without the help of guides from dubntz and blindndumb. If you like any of the ports thank them as well.
This guy has done it before with other p990 Roms with little experience.

When we were on Cm7 we were able to port roms by using the already created cm7 base. The problem now is we don't even have a P999 cm10 base to port with, which is why we're waiting on RC since he needs to create the base.
Sent from my Nexus 7 using xda app-developers app

That seems to make sense. thanks. Can any Developers confirm this. Is RC truely the only one? Or is he just the only one with the spare time to help us? thanks

We need kernel and some of the drivers for our device which only ricardo has for jb. Like all of you, i am myself waiting for it. I might be moving on to nexus4 depending on money in hand. 16gb will run for almost $400 after tax.
Sent via G2X-SINGH-UI

nycelitemaster said:
We need kernel and some of the drivers for our device which only ricardo has for jb. Like all of you, i am myself waiting for it. I might be moving on to nexus4 depending on money in hand. 16gb will run for almost $400 after tax.
Sent via G2X-SINGH-UI
Click to expand...
Click to collapse
Don't we already have the drivers and Kernal? They are part of p990 and then don't they just need to port it over.

More then likely it would be easier to port tonyps experimental ics. We can compile a kernel for it and have the drivers. We just need the experience lol
Sent from my LG-P999 using Tapatalk

Here's what I think based off what I have read:
I think first and foremost, our Dev's who all own P990's are working in wrapping their wits around the sources for their phones, us and our G2x's are the red-headed step-children (figuratively) of LG. The phone has potential, but gets little attention. I also believe that the Devs are waiting for a kernel to be built with the new sources, which those sources have to be altered to work with the G2x, as they did for the O2x. Something which I don't think our Devs want to do. I may be wrong, but I would think that Bene, or Dj V. have the know-how to do it. Again, we're back to the fact that they're (understandably) going to do work for their phones first.
Sent from my LG-P999 using xda premium

As far as I know, the kernel sources for su660 has some issues compiling kernel for p999. It can be one of the reason why we don't have cm10 yet. I believe the developers are working on it. Also the kernel source comes with locked boot loader. So its essential to port old boot loader which is not locked to the new kernel. This might also be preventing other developers from building kernel. If I have time, I will try to see if I can compile the kernel with old boot loader or not this weekend. I am a full time science student. I think to port the p990 ROM we just need a p999 kernel and some p999 specific drivers such as ril drivers. I do hope the cm10 comes asap though. I might be wrong.

While I do not consider myself a developer, I thank you for listing me there. I personally do not have the time and knowledge required to build a cm10 base for the p999 based off the p990. The kernel and rom needs to be change to work for our phones. Also as it was said already, it would make no sense to make an early port, based on RC work which will most likely piss him off if we start kanging and using his work while it is not even stable enough to build for our phone. So I would say that out of respect and time/knowledge required most people able to make the port would either wait for help debugging the p990 version so it can be ported to other devices without the same issues to be fixed twice or more times.

In order to port you need a current rom with jb drivers for our phone. Porting will rip the kernel out of our rom and plug it into the ported rom. Thus why we can't port yet.
Sent from my LG-P999 using xda app-developers app

guitarist5122 said:
In order to port you need a current rom with jb drivers for our phone. Porting will rip the kernel out of our rom and plug it into the ported rom. Thus why we can't port yet.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
A regular port from one rom to another with a CM base is mostly replacing a bunch of files with the ones you which to port while keeping the specific libs and files for your particular device, so besides the kernel, you need to make a compatible base if there is not one, then the proprietary blobs and editting files to fix issues. Porting can be very easy or very hard depending what you want to port.

who wants a kernel?
I've posted a kernel built from the cm10 lge-kernel-star repo in the dev thread, maybe somebody feels like taking it for a spin.

was wonder why the mixed results on the p990 CM 10 by RC then it hit me they have like 14 basebands. Things should be better for us we only have 2.

rosevilletoyota said:
was wonder why the mixed results on the p990 CM 10 by RC then it hit me they have like 14 basebands. Things should be better for us we only have 2.
Click to expand...
Click to collapse
In theory, I believe that a main issue for our guys did have to do with the absence of lge_star_ril being not present in the sources. That then caused the data, Gps, and battery issues.
Sent from my LG-P999 using xda premium

Rafase282 said:
A regular port from one rom to another with a CM base is mostly replacing a bunch of files with the ones you which to port while keeping the specific libs and files for your particular device, so besides the kernel, you need to make a compatible base if there is not one, then the proprietary blobs and editting files to fix issues. Porting can be very easy or very hard depending what you want to port.
Click to expand...
Click to collapse
Which is the problem for the G2x when it comes to Wifi Calling for example...the Kinecto .ko is a GB module at best. Same goes for the Tegra HDMI blob(whch I monkeyed around a very LONG time with);thankfully the P990 has the same HDMI blob. We will never have as good of a port as the P990 because at least the P990 has a ICS leak so kangers for P990 can use modules that work better in ICS leak in CM while all we have to build on is GB blobs and libs.
(PS:awesome avatar...ochem was a long time ago so I can't figure out the formula and nice use of -ase in your name!)

bakedpatato said:
Which is the problem for the G2x when it comes to Wifi Calling for example...the Kinecto .ko is a GB module at best. Same goes for the Tegra HDMI blob(whch I monkeyed around a very LONG time with);thankfully the P990 has the same HDMI blob. We will never have as good of a port as the P990 because at least the P990 has a ICS leak so kangers for P990 can use modules that work better in ICS leak in CM while all we have to build on is GB blobs and libs.
(PS:awesome avatar...ochem was a long time ago so I can't figure out the formula and nice use of -ase in your name!)
Click to expand...
Click to collapse
For my name the division is Rafa-sé It is just that in many places I cant use the é. SO I left it as an e and use use é for the phonetic part.
Morphine! :highfive:

Волк said:
In theory, I believe that a main issue for our guys did have to do with the absence of lge_star_ril being not present in the sources. That then caused the data, Gps, and battery issues.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Is the lge_star_ril something LG was supposed to have included? From my (limited) kernel knowledge, that bit seems pretty vital to having a properly working phone.
Without it, how hard is it going to be to get working calls/data/gps without having serious battery and quality issues as you've alluded to?

It was missing from the old sources, and yea, like I said alot of the deal-breaking issues were due to that, the ICS (which I think was already hacked) was hacked into JB.
Sent from my LG-P999 using xda premium

[H] Kernel

Can anyone extract boot.img of any Jelly Bean Based ROM & give kernel to me? (ParanoidAndroid would be better )

I wonder why would you need that.
I have really bad upload speed, so it would be hard for me.
Sent from my SGH-I997 using xda app-developers app

The kernel is the same for all JB roms. PA is the same as CM etc. Can't imagine what you need it for or why you can't just download a package and extract it, but I'll attach it here anyway..

Low Bandwidth
zpzp96 said:
I wonder why would you need that.
I have really bad upload speed, so it would be hard for me.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Whizzpopper said:
The kernel is the same for all JB roms. PA is the same as CM etc. Can't imagine what you need it for or why you can't just download a package and extract it, but I'll attach it here anyway..
Click to expand...
Click to collapse
I'm on low bandwidth. & i needed kernel not boot.img. Well, thanks for boot.img
P.S. I need it for compiling PA 2.57 for infuse 4G

i to am wondering why you need the kernel...
samsung boot.img are unlike others, and there isn't tool that i know of that will extract it for you...there is actually no known way to me to extract it...there is also no known way to re inject it into a boot.img...only thing i can think of that might work is to compile a new boot.img from source and use the kernel as a prebuilt...idk if that would work though
anyways if you want the kernel alone your gonna need someone to build it from source and send you the proper file as it cant be extracted as far as i know...then agai its been a while since ive tinkered with things

mg2195 said:
i to am wondering why you need the kernel...
samsung boot.img are unlike others, and there isn't tool that i know of that will extract it for you...there is actually no known way to me to extract it...there is also no known way to re inject it into a boot.img...only thing i can think of that might work is to compile a new boot.img from source and use the kernel as a prebuilt...idk if that would work though
anyways if you want the kernel alone your gonna need someone to build it from source and send you the proper file as it cant be extracted as far as i know...then agai its been a while since ive tinkered with things
Click to expand...
Click to collapse
I'm from Galaxy Fit Forum. I'm compiling PA for infuse 4G, I took CM 10 device config from GitHub. Kernel is not there. So it is stopping d compiling.
AFAIK we need kernel file in device config. During building it uses kernel & compiles boot.img & include it into .zip

RishabhAd said:
I'm from Galaxy Fit Forum. I'm compiling PA for infuse 4G, I took CM 10 device config from GitHub. Kernel is not there. So it is stopping d compiling.
AFAIK we need kernel file in device config. During building it uses kernel & compiles boot.img & include it into .zip
Click to expand...
Click to collapse
Have a look at scotthartbti's github. He has cm, pa, and his own build.. Great dev.
There you will find the kernel, aries-common, proprietary files, and device repos. I bet those are much up to date
Www.github.com/scotthartbti

defy cm10.1 alpha

this is just a demo of a kernel based on quarx 3.0.8 kernel sources,maybe later i'll try to merge several fixes or something but till then lets say i've reached a small milestone like finishing to compile this kernel,booting it up,take some screenshots from it.
known bugs,just like initial quarxs or blenchose commits.
Warning:flash at your own responsability,works only with cm 10.1 under boot options by ticking 2ndboot and ticking adb disable
link to kernel:http://www.mediafire.com/?vdjoj438tlvz2lw
NOTE:kernel sources are based on quarx repo on github:https://github.com/Quarx2k/jordan-kernel

What's this? A fix for CM10.1 23/01?

I think it's a 3.0 kernel... so not a fix.

i think , quarx2k also made many changes with his CM 10.1-3.0 branch which corresponds to the 3.0 kernel ..( eg - hwcomposer sources)
so it will be better if u can compile and upload both ROM + KERNEL package in order to have maximum working efficiency

Shubhamqweasd said:
i think , quarx2k also made many changes with his CM 10.1-3.0 branch which corresponds to the 3.0 kernel ..( eg - hwcomposer sources)
so it will be better if u can compile and upload both ROM + KERNEL package in order to have maximum working efficiency
Click to expand...
Click to collapse
you're right,because i could not boot this kernel on 4.1.2 so tried with 4.2.1 without adb manual boot,the difference is that i added forced module unloading and allow old eabi binaries to run with this kernel trying to get some backwards compatibility thus my conclusion is that either this kernel needs scratch bins in the os for propper functioning

rodrigoswz said:
What's this? A fix for CM10.1 23/01?
Click to expand...
Click to collapse
nope,my bad to mention that is an kernel build on quarx repo

You know opening a new thread was unnecessary as we already have a 3.0 kernel thread and CM10.1 also.... BTW the kernel and CM10.1 are both easily compiled if you know what you're doing
Let's Go ^_^

Kayant said:
You know opening a new thread was unnecessary as we already have a 3.0 kernel thread and CM10.1 also.... BTW the kernel and CM10.1 are both easily compiled if you know what you're doing
Let's Go ^_^
Click to expand...
Click to collapse
The thread is already reported
Sent from my MB526 using xda premium

nogoodusername said:
The thread is already reported
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
thank you for your support nogood username,that helps alot and to what i can do for this comunity,for example my own kernel sources for linux kernel 3.7.5,as of this post was just an test to see if it works and 3.7.5 yup it likes the cpcap drivers and firmware,just some gpu issues to display under menuconfig

drunk_ryder24 said:
thank you for your support nogood username,that helps alot and to what i can do for this comunity,for example my own kernel sources for linux kernel 3.7.5,as of this post was just an test to see if it works and 3.7.5 yup it likes the cpcap drivers and firmware,just some gpu issues to display under menuconfig
Click to expand...
Click to collapse
I appreciate your work, and I'm not the one that reported (as far as I remember)
Sent from my MB526 using xda premium

nogoodusername said:
I appreciate your work, and I'm not the one that reported (as far as I remember)
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
maybe i started wrong but my intention was to give some help for the comunity,as for my attempt on kernel 3.7.5:bump cant port sgx drivers,got cpcap to show up in menuconfig even mapphone but its like impossible to show up,tried a workaround with similar devices to get the gpu drivers but no chance

drunk_ryder24 said:
maybe i started wrong but my intention was to give some help for the comunity,as for my attempt on kernel 3.7.5:bump cant port sgx drivers,got cpcap to show up in menuconfig even mapphone but its like impossible to show up,tried a workaround with similar devices to get the gpu drivers but no chance
Click to expand...
Click to collapse
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.

Kayant said:
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.
Click to expand...
Click to collapse
thats the whole point,everithing gets trouc the cross compiler even battery and every hw aspect for defy,but cant seem to get sgx drivers on it it boots but only backlight flickers,also the importance of this is that one day we might bump in a problem like this(maybe future android versions will use kernel 3.7.5 as default)and my opinion is that we should have some widen experience about it in any way possible

Kayant said:
Thanks for your efforts I think I was the one that reported it can't remember now ..... The reason I did it was because like you said you're trying to port 3.7.5 which we already have thread for where you cab discuss about porting 3.0.0 kernels
Some advice and questions......
I was wondering why are you trying to port 3.7.5 which is not even on any other android device yet??
IMO I think a higher version of the 3.0 base kernel is not needed as am sure most of the new things in it would not benefit us as we probably couldn't use it anyway since we have old drivers, old cpu/gpu etc.....
Getting it to show up in defconfig is not the hard part you can activate anything you want from there they are just the configuring files the hard part is configuring the activated drivers for the defy which requires dev work and debugging just look Quark's commits
I think what we have is fine and I don't think anything much higher would be any benefit for us also we have older drivers and the things we need for 4.2 to work properly are in 3.0.8 like the new wifi drivers maybe Quarx will update it to a higher minor version later like he did with 2.6.32.9 to 2.6.32.60......
Don't worry yourself to much there are many other things you can do to help us in the defy community. This is not worth your time trust me from experience :cyclops:
Btw the menuconfig iust activates the stuff you want for your device and mapphone_defconfig is where all the options you picked from menuconfig is stored. Each defconfig is different as they are specify to one device.
Click to expand...
Click to collapse
and how is that a problem if someone wants to attempt a higher version kernel?
if there is no benefit then there is no loss either

I understand your point and even I know nothing is impossible.
BUT, there has to be a logic in things that you are doing, isn't it? Believe me, Nobody is discouraging him. Anyways, its a matter of understanding and not a debate.
FYI and to my knowledge, very few devices like xperia T/V has kernel 3.4

abhifx said:
and how is that a problem if someone wants to attempt a higher version kernel?
if there is no benefit then there is no loss either
Click to expand...
Click to collapse
Like brajesh.sharma87 said am not trying to discourage him anything am just giving him some advice. This is mainly just my opinion based on experiences I had trying to port the newer wifi drivers from 3.0 base to our 2.6 kernel..... he doesn't have to listen to what am saying.
Like brajesh.sharma87 said it's matter of knowledge because the Linux kernel changes so much between versions and the work Quarx has done on the 3.0.8 base may become outdated and needs to be changed to get it to work for the new base.
Am just trying to put things into prospective as I think it's not worth his time and effort trying to port a higher version kernel without good knowledge and experience on kernel porting. Again that's for him to decide.
Drunk_ryder24 if you still want to try here are is something you can do that may help -
If you haven't already tried this but try cherry-picking Quarx's commits from the p-android-omap3-3.0 branch since the code is related to the defy but keep in mind not all of Quarx's work may work on the new base.

Kayant said:
Like brajesh.sharma87 said am not trying to discourage him anything am just giving him some advice. This is mainly just my opinion based on experiences I had trying to port the newer wifi drivers from 3.0 base to our 2.6 kernel..... he doesn't have to listen to what am saying.
Like brajesh.sharma87 said it's matter of knowledge because the Linux kernel changes so much between versions and the work Quarx has done on the 3.0.8 base may become outdated and needs to be changed to get it to work for the new base.
Am just trying to put things into prospective as I think it's not worth his time and effort trying to port a higher version kernel without good knowledge and experience on kernel porting. Again that's for him to decide.
Drunk_ryder24 if you still want to try here are is something you can do that may help -
If you haven't already tried this but try cherry-picking Quarx's commits from the p-android-omap3-3.0 branch since the code is related to the defy but keep in mind not all of Quarx's work may work on the new base.
Click to expand...
Click to collapse
well ive done cherry picking from quarx repo and i must say that quarx done an excelent job compiling the modules since they are recognized and compiled by the toolchain with no major errors,just a few ignorable errors,boy quarx must have nerves of steel to bare so much time in developing from scratch,oh btw i will post this as a reply in 4.1.2 tread,ive mixed kernel zimage and ramdisk of quarx 2.6.32.60 after applying sevenrock's kernel 2.6.32.9-the whole point is that it might have been something changed in either ril or wifi module cause 2.6.32.60 seems just a little laggy but no ringtone bug or reboots by this method

drunk_ryder24 said:
well ive done cherry picking from quarx repo and i must say that quarx done an excelent job compiling the modules since they are recognized and compiled by the toolchain with no major errors,just a few ignorable errors,boy quarx must have nerves of steel to bare so much time in developing from scratch,oh btw i will post this as a reply in 4.1.2 tread,ive mixed kernel zimage and ramdisk of quarx 2.6.32.60 after applying sevenrock's kernel 2.6.32.9-the whole point is that it might have been something changed in either ril or wifi module cause 2.6.32.60 seems just a little laggy but no ringtone bug or reboots by this method
Click to expand...
Click to collapse
That sounds good am I bit surprised it worked so well with not that much errors but thats's good Yh I know Quarx is unstoppable and good luck with the project ..... If you need any more advice or help just shoot me up with a pm and I will see what I can do

kayant said:
that sounds good am i bit surprised it worked so well with not that much errors but thats's good yh i know quarx is unstoppable and good luck with the project :d..... If you need any more advice or help just shoot me up with a pm and i will see what i can do
Click to expand...
Click to collapse
thanks for your support,its wellcomed

[Q] How openFIMG and samsung FIMG works?

I spent the last two months analyzing and studying kernel sources, driver sources, openFIMG sources... But i can't get how Samsung FIMG and openFIMG works! I want to get Samsung FIMG on the latest Alpha9 (possibly MTD) because IMHO openFIMG are still not good for daily usage, and lot of textures won't show up. At first i tried to compile the whole CM7 removing libsgl and adding samsung proprietary files instead, FAIL, then when i checked out the G3MOD initramfs and i discovered that i needed some module to make the whole thing work i converted my phone back to BML, flashed G3MOD 2.4.1 and then copied samsung proprietary files to /system/lib/egl , gralloc.apollo, copybit.apollo etc... to /system/lib/hw and libChunkAlloc.so to /system/lib, the phone booted but nothing (not even the bootanimation) showed up on the screen. So i checked out the marcellusbe's MTD kernel initramfs and i saw that it had no modules, so after looking the thread i realized that modules in MTD version were in the /system partition, so i checked the system partition and i saw that there was no 3D module!
If someone can point me to the right direction i would be really glad, because i'm really confused right now
And sorry for bad english.

You desperately need @marcellusbe and @hillbeast to help you.
Sent from my DEATH NOTE with Shinigami by my side!

superfrancy97 said:
I spent the last two months analyzing and studying kernel sources, driver sources, openFIMG sources... But i can't get how Samsung FIMG and openFIMG works! I want to get Samsung FIMG on the latest Alpha9 (possibly MTD) because IMHO openFIMG are still not good for daily usage, and lot of textures won't show up. At first i tried to compile the whole CM7 removing libsgl and adding samsung proprietary files instead, FAIL, then when i checked out the G3MOD initramfs and i discovered that i needed some module to make the whole thing work i converted my phone back to BML, flashed G3MOD 2.4.1 and then copied samsung proprietary files to /system/lib/egl , gralloc.apollo, copybit.apollo etc... to /system/lib/hw and libChunkAlloc.so to /system/lib, the phone booted but nothing (not even the bootanimation) showed up on the screen. So i checked out the marcellusbe's MTD kernel initramfs and i saw that it had no modules, so after looking the thread i realized that modules in MTD version were in the /system partition, so i checked the system partition and i saw that there was no 3D module!
If someone can point me to the right direction i would be really glad, because i'm really confused right now
And sorry for bad english.
Click to expand...
Click to collapse
Oh dear. There's a lot wrong with what you're trying to do so let me try and explain it as best I can:
Android libraries are not like Windows where you can mix and match drivers to different versions. Every time Google makes a new version of Android, they change how they want to do the graphics drivers. It's really annoying that they do this, but they aren't trying to make a desktop OS, they are making an embedded OS that the phone manufacturer then modifies to get it going on their hardware. This means that drivers for Eclair don't work on Froyo, and drivers for Froyo don't work on Gingerbread, and drivers for GB don't work on ICS. There are hacks and ugly mods you can do to make them kind of work, but basically it doesn't work. If you can get the drivers to work, it's so broken and laggy that you don't want it to be working.
Samsungs FIMG drivers are made for Eclair and Froyo, and that's only because those were the two firmwares Samsung made for the Apollo. Gingerbread did a lot of changes to the graphics subsystem and this basically breaks all compatibility with Froyo drivers
Replacing the OpenFIMG libraries with the Samsung FIMG libraries won't work because the Android frameworks in CM7 were compiled around OpenFIMG. When marcell had it working on Samsung FIMG drivers, he had to modify the interfaces for the graphics libraries that communicates between the Android framework and the hardware specific libaries (OpenFIMG/Samsung FIMG) to make it talk to it the way the Samsung FIMG libraries worked. When he moved to OpenFIMG he would have reverted it back to how Google would want it because OpenFIMG is made for GB/ICS+ and doesn't need this compatibility wrapper.
G3MOD works differently to the CM7 kernel. G3MOD needed to support many different firmwares and many different graphics modes. This means that to make it work on other firmwares, we had to modularise components of it so certain kernel functions were used on certain firmwares. This is why there are modules for G3MOD to work with OpenFIMG and not on other kernels.
Kernel modules are kernel specific. They only work with the kernel they were compiled for. You can't use a G3MOD module on Fugumod and vice versa.

hillbeast said:
Oh dear. There's a lot wrong with what you're trying to do so let me try and explain it as best I can:
Android libraries are not like Windows where you can mix and match drivers to different versions. Every time Google makes a new version of Android, they change how they want to do the graphics drivers. It's really annoying that they do this, but they aren't trying to make a desktop OS, they are making an embedded OS that the phone manufacturer then modifies to get it going on their hardware. This means that drivers for Eclair don't work on Froyo, and drivers for Froyo don't work on Gingerbread, and drivers for GB don't work on ICS. There are hacks and ugly mods you can do to make them kind of work, but basically it doesn't work. If you can get the drivers to work, it's so broken and laggy that you don't want it to be working.
Samsungs FIMG drivers are made for Eclair and Froyo, and that's only because those were the two firmwares Samsung made for the Apollo. Gingerbread did a lot of changes to the graphics subsystem and this basically breaks all compatibility with Froyo drivers
Replacing the OpenFIMG libraries with the Samsung FIMG libraries won't work because the Android frameworks in CM7 were compiled around OpenFIMG. When marcell had it working on Samsung FIMG drivers, he had to modify the interfaces for the graphics libraries that communicates between the Android framework and the hardware specific libaries (OpenFIMG/Samsung FIMG) to make it talk to it the way the Samsung FIMG libraries worked. When he moved to OpenFIMG he would have reverted it back to how Google would want it because OpenFIMG is made for GB/ICS+ and doesn't need this compatibility wrapper.
G3MOD works differently to the CM7 kernel. G3MOD needed to support many different firmwares and many different graphics modes. This means that to make it work on other firmwares, we had to modularise components of it so certain kernel functions were used on certain firmwares. This is why there are modules for G3MOD to work with OpenFIMG and not on other kernels.
Kernel modules are kernel specific. They only work with the kernel they were compiled for. You can't use a G3MOD module on Fugumod and vice versa.
Click to expand...
Click to collapse
Thank you for your answer :laugh: now i eventually understood how graphics driver works. So basically the only way to get proprietary fimg on alpha9 is getting alpha7 sources and apply all the alpha9 patches manually except the ones of openFIMG or i'm still thinking in the wrong way?

superfrancy97 said:
Thank you for your answer :laugh: now i eventually understood how graphics driver works. So basically the only way to get proprietary fimg on alpha9 is getting alpha7 sources and apply all the alpha9 patches manually except the ones of openFIMG or i'm still thinking in the wrong way?
Click to expand...
Click to collapse
If it compiles, it could... unfortunately, I lost alpha7 sources and I can't spend (a lot of time) to done it again ...
The other way is to get surfaceflinger, libui (and probably others) libs sources from froyo .. You will have errors when compiling (because of the CRT animations, screenshot implementations in GB) but it's possible to fix the errors.
It works. I currently have cm7 mtd with samsung's fimg libs but now camera need to be fixed, re-implement screenshot and CRT anim and some color problem when rendering pictures.
You asked kernelmtd sources. I will upload them to github today.
edit : sources uploaded here -> https://github.com/sdadier/gb_kernel_2.6.32.9-mtd

marcellusbe said:
If it compiles, it could... unfortunately, I lost alpha7 sources and I can't spend (a lot of time) to done it again ...
The other way is to get surfaceflinger, libui (and probably others) libs sources from froyo .. You will have errors when compiling (because of the CRT animations, screenshot implementations in GB) but it's possible to fix the errors.
It works. I currently have cm7 mtd with samsung's fimg libs but now camera need to be fixed, re-implement screenshot and CRT anim and some color problem when rendering pictures.
You asked kernelmtd sources. I will upload them to github today.
edit : sources uploaded here -> https://github.com/sdadier/gb_kernel_2.6.32.9-mtd
Click to expand...
Click to collapse
R u still working on g3?
Sent from my DEATH NOTE with Shinigami by my side!

Arjav23 said:
R u still working on g3?
Sent from my DEATH NOTE with Shinigami by my side!
Click to expand...
Click to collapse
Not seriously ... only when I have nothing better to do

marcellusbe said:
Not seriously ... only when I have nothing better to do
Click to expand...
Click to collapse
It would be great sir if you could spend a little of your valuable time in giving a try of whether kitkat could be ported to g3
Or
Help us to get a 3.4.x kernel!
Sent from my DEATH NOTE with Shinigami by my side!

Arjav23 said:
It would be great sir if you could spend a little of your valuable time in giving a try of whether kitkat could be ported to g3
Or
Help us to get a 3.4.x kernel!
Sent from my DEATH NOTE with Shinigami by my side!
Click to expand...
Click to collapse
Wow ... it's about 2 years of work for me !
I can't dedicate much time for g3.

marcellusbe said:
If it compiles, it could... unfortunately, I lost alpha7 sources and I can't spend (a lot of time) to done it again ...
The other way is to get surfaceflinger, libui (and probably others) libs sources from froyo .. You will have errors when compiling (because of the CRT animations, screenshot implementations in GB) but it's possible to fix the errors.
It works. I currently have cm7 mtd with samsung's fimg libs but now camera need to be fixed, re-implement screenshot and CRT anim and some color problem when rendering pictures.
You asked kernelmtd sources. I will upload them to github today.
edit : sources uploaded here -> https://github.com/sdadier/gb_kernel_2.6.32.9-mtd
Click to expand...
Click to collapse
Uhm, i have lot of free time so i will give it a try, who knows, maybe i'm going to learn something useful :laugh:! I found alpha7 device folder in venkat kamesh's github account could that be useful?

marcellusbe said:
Wow ... it's about 2 years of work for me !
I can't dedicate much time for g3.
Click to expand...
Click to collapse
But @hillbeast got a start already.
Won't that help?
Sent from my DEATH NOTE with Shinigami by my side!

marcellusbe said:
Not seriously ... only when I have nothing better to do
Click to expand...
Click to collapse
do you have the cm9 sources? becuase i couldnt fin them and wanted to fix the superuser problem

marcellusbe said:
If it compiles, it could... unfortunately, I lost alpha7 sources and I can't spend (a lot of time) to done it again ...
The other way is to get surfaceflinger, libui (and probably others) libs sources from froyo .. You will have errors when compiling (because of the CRT animations, screenshot implementations in GB) but it's possible to fix the errors.
It works. I currently have cm7 mtd with samsung's fimg libs but now camera need to be fixed, re-implement screenshot and CRT anim and some color problem when rendering pictures.
You asked kernelmtd sources. I will upload them to github today.
edit : sources uploaded here -> https://github.com/sdadier/gb_kernel_2.6.32.9-mtd
Click to expand...
Click to collapse
I should take the " surfaceflinger, libui (and probably others) libs sources" from froyo or AOSP?