Related
Hey with this new kernel that has been really impressive to me
I want to work with any Devs out there to bring this kernel to them for testing
I think a lot of people would really like it since it has choices for CFS/BFS RHack/NoRHack
So, if any devs want to work with me on bringing this any build - email me
[email protected]
Hopefully, I want to create a kernel for everyone to use - I know CM's has been more popular for its features - but this one has the features plus a really good speed
I would really like to work with any Eclair Devs to improve the speed of this before I make my Eclair ROM (sooner or later - may need a break first for life lol)
I was really behind on this working on the kernel way too much - so 2wks behind
wesgarner said:
Hey with this new kernel that has been really impressive to me
I want to work with any Devs out there to bring this kernel to them for testing
I think a lot of people would really like it since it has choices for CFS/BFS RHack/NoRHack
So, if any devs want to work with me on bringing this any build - email me
[email protected]
Hopefully, I want to create a kernel for everyone to use - I know CM's has been more popular for its features - but this one has the features plus a really good speed
I would really like to work with any Eclair Devs to improve the speed of this before I make my Eclair ROM (sooner or later - may need a break first for life lol)
I was really behind on this working on the kernel way too much - so 2wks behind
Click to expand...
Click to collapse
are you saying that it has the same features as the CM kernel, but it's faster?
prince.siraj said:
are you saying that it has the same features as the CM kernel, but it's faster?
Click to expand...
Click to collapse
That's what it looks like.
Need this in a Hero ROM
Would love this for SuperD.....
hey i just tried out your kernel on eclair. i used your kernel from 2.6 cfs w/ ram hack on my custom speed demon build of eclair using manups ramdisk and i am unable to pass splash screen. prolly needs more implementation of eclair goodies
What files did you "transplant" to use the kernel on another build?
u must unpack the boot.img's then replace kernel
Hero_Over said:
u must unpack the boot.img's then replace kernel
Click to expand...
Click to collapse
THanks, Im gonna do some experimenting on a 1.6 build later
Anyone else trying this kernel on Eclair other then Herver?
I'm waiting to switch to Eclair until a fast/responsive kernel is implemented.
Tried BFS/RAMHACK with Manup's Eclair ROM, kernel loaded properly, ran quickly, only issue was that bluetooth didn't work.
My issue with all these different kernels out there, is that I'd like to see source code accessible, or at the very least, maybe attach the .config file, so I know what exactly has been changed.
Ok lol who wants for what ROM?
You have to grab a few things from it - such as the rootdir plus setup xbin if it doesn't use it
hi wes.
i would certainly like to help the cause and assist in improving upon things (where possible and if feasable), but i would really need to see the source and .config to make advancements.
is this available on your github?
you're handing these out pre-built? Do you have somewhere we could download the source?
Figured I'd test it, and figured it wouldn't work...
The kernel (CFS + ram hack) doesn't work as a direct drop-in on dwang.
wesgarner said:
Ok lol who wants for what ROM?
Click to expand...
Click to collapse
You should do one for hero/espresso.
wesgarner said:
Ok lol who wants for what ROM?
You have to grab a few things from it - such as the rootdir plus setup xbin if it doesn't use it
Click to expand...
Click to collapse
If you wanna help me, then
g'day Wes,
like the rest - I am curious to know if it possible to see the source and the .config? Is there anyway you could make this available? thanks in advance mate...
peace..
bump for update dammit. Donut is still ALive!
R3N0V4D0 said:
bump for update dammit. Donut is still ALive!
Click to expand...
Click to collapse
No it isn't, go back to sleep and don't be bumping ancient threads.
To make it perfectly clear: This is a vanilla development kernel. It has absolutely no features the stock kernel does not have (no ext4, no OC, no nothing). But it may cause problems (SOD, eat battery, the apocalypse... you get the idea). This kernel only exists, because all earlier efforts to compile a stabel kernel have not been successfull.
EDIT: And this one isn't either. SOD-issue not solved - may occur less often, though. I'm not releasing the kernel, because it remains faulty.
EDIT2: Samsung released new sources on the 18th of November. Use these and the new toolchain instead!
First things first: The setup.
The Samsung GB source is used. Extract it to a new directory - do not copy it over the Froyo sources, simply because it says "Update1". You should now have something like
Code:
/home/<user>/<working_directory>/Kernel/...
and a folder for the platform - the latter will not be used.
The toolchain is from Codesourcery: Sourcery G++ Lite 2009q3-68 for ARM EABI. Extract it to wherever you like. Just remember the path (<your_path>).
The path to the toolchain, and the correct EXTRAVERSION are adjusted in the Makefile. Nothing else. The EXTRAVERSION is different for every firmware - see: settings => about phone.
Code:
cd /home/<user>/<working_directory>/Kernel/
gedit Makefile
Look out for:
Code:
...
EXTRAVERSION=.7-CL467143
...
CROSS_COMPILE=/<your_path>/toolchain/arm-2009q3/bin/arm-none-linux-gnueabi-
Thanks to Skin at this point, for his helpful tips!
A little spring cleaning is performed
Code:
cd /home/<user>/<working_directory>/Kernel/
make mrproper
This will delete all precompiled files and the config.
The config is extracted directly from the device with
Code:
cd /home/<user>/<working_directory>/
adb pull /proc/config.gz
gunzip config.gz
cp config /Kernel/.config
What happens after setting up everything:
The kernel is compiled.
Code:
make
The Samsung readme recommends another alternative:
Code:
make android_latona_r08_eng_defconfig
make
Do not run this, if you want to keep the .config from the device intact! This will overwrite it, and you will compile with different settings than the kernel on your i9003.
With the help of Skins unpack-repack-tools (look here), a flashable PDA is created. The CF-root normalboot.img from the 21.08.2011 is used as a basis (I like this one, no special reason ). Only the zImage is replaced with the self-compiled kernel.
The PDA is flashed with ODIN.
After the first reboot, the cache and Dalvik-cache are cleaned in CWM.
Have fun testing! And remember to make a nandroid backup. If you want to go back, flash Skins original CWM, and restore the nandroid backup afterwards.
What do you mean by stable here,XXKPH is quite stable for me
yamchirobe said:
What do you mean by stable here,XXKPH is quite stable for me
Click to expand...
Click to collapse
Dude he is talking about custom kernal & not about stock kernal. Problem with gb sources is that whenever we compile a kernal it has SOD problem. So this thread is suggesting info how to build a stable kernal.
vishal24387 said:
Dude he is talking about custom kernal & not about stock kernal. Problem with gb sources is that whenever we compile a kernal it has SOD problem. So this thread is suggesting info how to build a stable kernal.
Click to expand...
Click to collapse
There is no problem with the sources...it depends on how they compile the kernel...that is causing the bugs!!
Sent from my GT-I9003 using XDA App
ronhoover88 said:
There is no problem with the sources...it depends on how they compile the kernel...that is causing the bugs!!
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
Do u mean that source code.is correct then skin said that it is not compatable & codes are older. I have used skin & amit's oc version. Both have sod problem Are they doing any mistake in compiling kernal?? Please clear doubt.
No what i meant was the sources which were released (could be) for the dev releases XXKP7/KP9/KPE may be after next official update...we could have GB sources!!
Sent from my GT-I9003 using XDA App
You should post here the kernel so more people will test it.... if you have solved SOD and oher issues i can say that you are great... BTW good work, with your explanation many other people can try...
Seems I didn't - phone didn't wake from standby this afternoon.
But I noticed, that it did respond. I could change speaker volume, the soft keys were lid - only the screen remained black. I'm getting really curious...
XDA_Bam said:
Seems I didn't - phone didn't wake from standby this afternoon.
But I noticed, that it did respond. I could change speaker volume, the soft keys were lid - only the screen remained black. I'm getting really curious...
Click to expand...
Click to collapse
I study on it.... the different between normal sleep and SOD is that, if you have a SOD, when you press the button to wakeup the phone the proc modemctl doesn't work and also the display driver cannot be activated.. i'm not sure if modemctl is responsable of turning up the LCD but this is what i found...
Another thing.... can i say now that must be something wrong in the sources?
Hmmm... I just checked: The last edit made in the GB kernel source files is from the 28. of June. There is no way, these are the XXKPH sources.
XDA_Bam said:
Hmmm... I just checked: The last edit made in the GB kernel source files is from the 28. of June. There is no way, these are the XXKPH sources.
Click to expand...
Click to collapse
I wrote again to sammy;
Here my 1st email:
Hi again. I apologize but i have to ask something else.
I try again to build the kernel with the KPH source and i have the same issue (some time cannot wake - up from lock - sleep).
I follow perfectly the guide on kernel compilation so i really don't understand why that issue happen.
I have to insist on the fact that the source is not completely updated or maybe i'm doing something wrong.
I'm saying that the source are not updated cause the issue is part of precedent GB release but not of KPH.
Wish that you check again and report me if i have to do something else.
Thanks again
... they didn't answer so i wrote another:
Hi, i'm sorry but i have to write again. I tryed many times to compile a working kernel and what i build works correctly except that sometime the phone cannnot wakeup from sleep.... we ( me and other xda members) call this SOD. Also other members have compiled the kernel with your source and all have the same problem.
Please, check the source, they cannot be for the XXKPH FW. Or, at least, show us how to solve our issue.
THIS IS THE ANSWER:
Thank you for your continuous interest in our product.
This web site is intended to provide Open Source Software used in our product.
As mentioned previous mail, some of samsung proprietary codes are not included in the kernel. (codes that are not affected GPL - loadable modules) Please understand we do not guarantee opensource code is executable in target device.
We are sorry for not giving you an correct anwser upto your satisfaction.
Please accept our apology for not being able to handle your request up to your satisfaction.
Best Regards
You may find the source code
and if someone can explain me the meaning of "You may find the source code" woud be great....
XDA_Bam said:
Hmmm... I just checked: The last edit made in the GB kernel source files is from the 28. of June. There is no way, these are the XXKPH sources.
Click to expand...
Click to collapse
xcuseme bro... 28 June = KPH? Can you explain better?
Skin1980 said:
xcuseme bro... 28 June = KPH? Can you explain better?
Click to expand...
Click to collapse
These are old sources for XXKPE and below builds and not for XXKPH i guess coz XXKPH was built in august
We better wait for next official GB release and hope they release latest sorce codes...
You better continue with your OC kernel for froyo now...
Sent from my GT-I9003 using XDA App
When i send source codes to doomlord related to usb otg he also mentioned that 'source codes are always present some what in broken form. They never provide complete source code. We have to manage with that'.
May be doomlord know better about this matter.
Mother effin sammy. Proprietary? it's not even proprietary information that we're asking for. We are just asking complete source codes that function properly. Is it something that they own that makes fix for the SOD? I freakingly don't believe so? Can someone pm me their email address?
go to samsung opensource, search for i9003, then send a message
ronhoover88 said:
These are old sources for XXKPE and below builds and not for XXKPH i guess coz XXKPH was built in august
We better wait for next official GB release and hope they release latest sorce codes...
You better continue with your OC kernel for froyo now...
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
Everyone of us might write to sammy... for the kernel i'm sorry but i really don't intend to go back to froyo.... haven't enouth time....
I have a suggestion. We have 3-4 gb releases present with us by samsung. Firs gb source was facing SOD problem a lot. But after that in later version till kph they removed problem successful. Can we compare those kernals & find the differce & come to know what exact changes they have made in kernal so that they reached to stable kernal of kph.
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/previous changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Current Version changelog
CM10 build 133
There was an issue with the backup tool in the last build that will break gapps and your account's etc when flashing this build, the solution is to re-flash gapps at the same time as the rom and you should be fine. This build should fix it so that the next build will work as it should
Changes.
Synced with CM - Again not many changes upstream.
Basically everything relevant to our phones up to the 4th of February in the following has been merged
http://review.cyanogenmod.org/#/q/status:merged+branch:jellybean,n,z
Kernel updated to Andromadus Current - 3.0.62
might need this
First
Its Awsome, Running it since last 3 days
Great
And maybe I didn't go to sleep. Maybe
Sent from a device waiting for the Kernel 3 source code. WAKE UP HTC !!!!!
I get one more rom to base..
BTW my camera fix can be a temp fix for camera
Great :good:
- EDIT -
Wait ! Does It Says Kernel 3
the camera issue atm is kernel, i dont think it will help your fix, you can try...
Edit:
Yeah, it says kernel 3
Yup, this ROM is based off the kernel 3 source by Andromadus. Who needs HTC?
Sent from a device waiting for the Kernel 3 source code. WAKE UP HTC !!!!!
Woah?! I thought i was in the wrong section for a moment! Great work!
Alternative upload than goo.im?
What the HELL!? Superkid is back, with Kernel 3!
Does I understand it right, that this is a real Kernel 3 compiled for desire s? Not a port? From wich source?
Unbelievable!! Will testing right now!
Andromadus team took the primou source and changed it to work with our device
Guys, remember, its all on alpha/beta.. kernel and rom!
After all, is the first aosp rom with kernel 3 for saga
Is the jerkiness normal? I flashed over CM10. Will a full wipe fix it?
Sent from my Desire S using Tapatalk 2
Good job man! Keep it up!
Iztipkano sa Dizajr S BRE!
Nice
Nice!
The third JB Rom.
I MUST try it!
But I need my cam. So if this work I will flash it.
Source of kernel released :
http://forum.xda-developers.com/showthread.php?p=29552861#post29552861
https://github.com/Flemmard/htc7x30-3.0
have fun and push fixes!
My congrats on that Rom.
I have a little Problem with play store...my apps arent there and bought Jones are like not bought.
Other than that.....
WOW
Sent from my Desire S using xda app-developers app
Guss one of the legends is back.........with a bang working his magic.......
Sent from my HTC Desire S using xda premium
dan-fish said:
Is the jerkiness normal? I flashed over CM10. Will a full wipe fix it?
Sent from my Desire S using Tapatalk 2
Click to expand...
Click to collapse
You can try.
This is because the kernel 3 is not optimized yet
Tapatalked from a Desire S waiting for Kernel 3 sources. WAKE UP HTC!!!!!!
The first Kernel 3,:good:,thanks
OMG!!! Kernel 3... That's cool.
Must be a tremendous amount of work by the dev.
Thx to dev and superkid. :good:
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
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