Just rambling here. In order to get ICS ported to the Venue, we need compatible kernel drivers. It appears, from what I can find on the 'net, that Qualcomm isn't releasing drivers for the QSD8250 for ICS. Looking around XDA, I see the HTC Desire (GSM), also based on the '8250, has a working ICS beta found here: http://forum.xda-developers.com/showthread.php?t=1403113. This appears to use a Tiamat kernel, http://tiamat-dev.com/tiamat_bravo/. Using the AOSP 4.0.x repository, the Dell info from http://opensource.dell.com/releases/venue/v4.06/ and the Tiamat kernel, is it possible to pull together an ICS port? I wish I had more experience with this type of stuff...
Dell used the CAF 8260 GB sources when building 4xx roms, they simply backported whatever they need to from their already working 3xx codebase for whatever was needed (i assume)
CAF itself dropped support for 8x50 in their GB codebases, but the 8x60 is close enough it didnt really matter ultimately.
Much of the drivers arnt even in the kernel, they're in the android userland which is Apache and not gpl, hence the driver issue.
Which ever method you (presumedly do) to get the kernel booting under ICS doesnt really matter, but the more difficult/time-consuming methods will ultimately be more useful for porting to newer kern versions.
Don't forget the Nexus One and, IIRC, the HD2 also use the 8250
I would think this would help too: http://www.xda-developers.com/android/qualcomm-releases-adreno-2xx-gpu-binaries-for-ics/
Too bad the development work is well outside my capabilities. Maybe our Korean friends are working on it though.
Guys.!!! Dell venue n dell streak 5got same rom n environment hardware too just diffrence is venue is Hdpi n dell streak is Mdpi .so why do nt we join hands n make ics work for dell or on other hand u can take advantage of our dell streak 5 formus there r few good roms like longhorn 2.8 with Hdpi support for dell Venue and Dcs 1.1.which supports both hdpi n mdpi just need to edit build.prop n may be kernel....whish u all safe cooking ...n Friends in need friend indeed ..
Max
Sent from my Dell Streak using xda premium
Sent from my Dell Streak using xda premium
Folks, I can see that Qualcomm released Adreno 200 drivers for ICS several months ago (Mar) (https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources).
Information in the above page also says that, the drivers has been tested on CAF M8960AAAAANLYA1030. As I noticed, whenever we get the source code from Code Aurora, there is also a kernel directory included. Do you think that we can start from that kernel to port ICS to Venue?
chacona said:
Folks, I can see that Qualcomm released Adreno 200 drivers for ICS several months ago (Mar) (https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources).
Information in the above page also says that, the drivers has been tested on CAF M8960AAAAANLYA1030. As I noticed, whenever we get the source code from Code Aurora, there is also a kernel directory included. Do you think that we can start from that kernel to port ICS to Venue?
Click to expand...
Click to collapse
Yes we can,
But I aint that good into dev
This mobile has what it requires to run ICS
The kernel itself ultimately doesnt matter, as long as it has the right code changes merged in.
The current S5 ICS kernel's lineage is:
S5/405 (dell) -> Phoenix kernel/GB (n0p) -> Phoenix/cm7.2 (hPa) ?-> Phoenix/cm9 (hPa) -> Phoenix/AOSP (kibuuka)
Only the final step involved merging in any changes to make it work with ics, ultimately it's based mostly on the phoenix GB kernel which itself is based on the S5's 405 kernel
S5 405 = S5 408 = V 406 = V 408, they're all the same kernel (with ifdefs/configs for the S5/V).
I'd imagine getting a V kernel to boot ICS period is 85% of the work as the S5's froyo/GB kernels can directly boot V froyo/gb roms, and the reverse would likely hold.
The kernel 405/6/7/8 from Dell can be built successfully, however there are known issues such as after charging, we won't be able to boot the kernel up. I do not have a Streak, so I wonder whether those issues are fixed well in Phoenix kernel Manii? Can you show me how to get the source for the latest phoenix kernel that you're using with your Streak AOSP? Maybe I will try to build with Venue myself to see how things work!
phoenix kernel/ICS - Github
It's currently in the process of being merged back in.
You could try diffing S5 405 with V 406 and seeing what's changed in the source, they're nearly identical, but I dont expect them to be bit identical
TheManii said:
phoenix kernel/ICS - Github
It's currently in the process of being merged back in.
You could try diffing S5 405 with V 406 and seeing what's changed in the source, they're nearly identical, but I dont expect them to be bit identical
Click to expand...
Click to collapse
Sounds interesting, that's exactly what I did in my custom overclocked kernel. However, I will be able to save some time by using their kernel directly. In fact, I think that 405/407 kernel is not very different from 406 since my build for 405 also ran on DV too.
I will try with their "master"/experimental14 branch kernel first (to CM 7.2.0). Thanks for your information!
chacona said:
I will try with their "master"/experimental14 branch kernel first (to CM 7.2.0). Thanks for your information!
Click to expand...
Click to collapse
Will be waste of time as only streak-specific file is board-qsd8x50_austin.c, other changes are device-independent.
Changes that essential to run ics with hwa:
kgsl3.8 - kernel-side drivers are in drivers/video/msm - direct drop in instead of one that's shipped with stock 405 kernel
include/linux/msm-kgsl.h - to make kgsl3.8 build
(not really)*streak-specific*changes to arch/arm/mach-msm/board-qsd8x50_austin.c - changes in hardware init routines needful for kgsl3.8 (updated data structures, powerrail). In short - do a diff for board-qsd8x50_austin.c between Phoenix and ics branches to find out what's changed - to be honest - changes are generic for qualcomm devices, so direct copy/paste of changes into your device's board file will do the job
Other patches that were applied to ics branch are optional (cpu governors, io schedulers, netfilter specific changes (these are only needed if you need ics' mobile data usage collecting/limits features)) or affect streak-specific drivers only (and are not ics-specific).
So, in short - update your device's board file and use ics branch - that would be enough.
kibuuka said:
So, in short - update your device's board file and use ics branch - that would be enough.
Click to expand...
Click to collapse
Do you think I can start with the stock kernel, download the ICS tree including the kernel, then do the diff/merge between device's board file from ICS kernel to Dell kernel? After that, the original Dell kernel is patched with new stuffs for ICS, and can be used with ICS ROM?
i can also provide you with all patches made for streak against aosp source tree for shortening your mileage and instructions for a quickstart (my streak is broken at the moment, so i've suspended my development activities and got spare time for that)
please mention kernel for streak's ics is being built separately at the moment (i've got plans incorporating it in aosp build process, but it will take some time)
when i've messed with streak kernel making it ics-friendly i've realised that most of stuff can be made cross-compatible between two devices.
It's 95% the kernel, the only thing left is to turn off the rotation patch and swap out the BCM4325 for BCM4239 drivers.
On stock 3/4xx i can directly load venue roms on my S5 and only wifi is broken. (with a S5 kernel) Everything else works.
TheManii said:
It's 95% the kernel, the only thing left is to turn off the rotation patch and swap out the BCM4325 for BCM4239 drivers.
Click to expand...
Click to collapse
rotation is triggerable through kernel configuration menu. check.
as of wifi - is there any known-to-be-trustable list of hardware components for venue?
The V is just an S5 without the hdmi and whatever provides usb hosting.
The only other notable change is the wifi chip.
All the other sensors are compatable, and so is the modem+ril.
(I was able to get 3g working, but not wifi due to the chip being different)
I dont think anyone has done a (good quality) teardown on the V though.
Most I can offer is to pull details android gives back while it's on.
I'm guessing that's how CM7.2 was ported, since hPa didnt actually own a V,
he just took his S5 build, and flicked a few switches.
(it helped a lot that CM7.2 doesnt need any kernel changes to boot, it's just the stock 408 one with a modded ramdisk)
He only had access to a V for like a day or so.
kibuuka said:
i can also provide you with all patches made for streak against aosp source tree for shortening your mileage and instructions for a quickstart (my streak is broken at the moment, so i've suspended my development activities and got spare time for that)
please mention kernel for streak's ics is being built separately at the moment (i've got plans incorporating it in aosp build process, but it will take some time)
when i've messed with streak kernel making it ics-friendly i've realised that most of stuff can be made cross-compatible between two devices.
Click to expand...
Click to collapse
Hi Kibuuka, that sounds good, could you please share?
One more thing I would like to ask is, the stock kernels 405/407 and 406 have issues regarding power (sometime I can see the issue that after charging, screen goes black and we can only quit that situation by removing the battery). How did you address it? (I notice that your kernel works well on my CM7, without that issue - or is just simply because it has not happened yet?)
n0p did enormous amount of work addressing sleep of death issue (which, i believe is one you refer to), so dsc kernels (opposed to stock ones) are free of this bug. Ask him for details (i wasn't involved to dsc development at the point he managed to fix it) as he's best source of information on SoD issue fix you could find
As of aosp patchset - will upload it during weekends.
For whatever it's worth, as soon as we get a working ICS level kernel, I plan on porting TWRP and CWM-touch.
Those require ICS kernels (or rather it's a great deal more difficult to make them run on GB kernels) and I cant port them until then.
I've already gotten TWRP and CWM-touch working on the S7, and plan on porting TWRP to the S10 now.
Edit: come to think of it, I actually have TWRP running on a 5xx kernel (which is HC), i'll try simply porting and seeing what happens
Hi,
I picked up the kernel code released by Samsung for SCH-R950 (US Cellular) from opensource.samsung
Kernel version: 3.0.31
Build Number: JR003C.R950VXALJ1
I changed the kernel code to accommodate my changes, compiled and flashed using ODIN. The phone came up well but the back and menu buttons stopped working. I undid my changes, compiled and flashed again. This time again the back and menu buttons didn't work. So, it seems that the source code or the build instructions released by Samsung has some issue. The config file used was t0uscc_04_defconfig (released along with the code). Has someone faced a similar issue before? I have attached the build config file.
Any help is highly appreciated.
sachingarg2k1 said:
Hi,
I picked up the kernel code released by Samsung for SCH-R950 (US Cellular) from opensource.samsung
Kernel version: 3.0.31
Build Number: JR003C.R950VXALJ1
I changed the kernel code to accommodate my changes, compiled and flashed using ODIN. The phone came up well but the back and menu buttons stopped working. I undid my changes, compiled and flashed again. This time again the back and menu buttons didn't work. So, it seems that the source code or the build instructions released by Samsung has some issue. The config file used was t0uscc_04_defconfig (released along with the code). Has someone faced a similar issue before? I have attached the build config file.
Any help is highly appreciated.
Click to expand...
Click to collapse
Can someone please help me out.
Hi Every body ,
i want to flash a modified kernel in to my I 9100G phone , and am wondering is there any body could help me
by sharing a download link of the AnyKernel.zip tool
Ps: i want to flash my ZImage and the ramdisk with the built modules .
best regards
Hey.
I hope you know, what you are doing anyway https://github.com/koush/AnyKernel this is what you are asking just download zip.
Oh and you can give me a shout if something goes wrong
Thank you for your Help , i will try flash the kernel today,
adding information that, am trying to build the "GT-I9100G_ICS_Opensource_Update2", and i choose this tool to help me flashing my Zimage with the ramdisk (initramfs) including the Built modules .
Thak you, i will give you shouts
hi,
thanks to Mantulis for sharing the link .
After downloading AnyKernel.zip , i did the necessary steps by moving my zImage to "kernel folder" and the built modules in "/system/lib/modules/" folder , but it seems that i couldn't flash it using the CWM ,
i had the message like :
finding update package ...
Opening update packages ...
Installing update ...
AnyKernel Updater by Koush
Extracting system files ...
.
.
.
Done ...
but when viewing my Kernel version i found that it's the same old on (the kernel didn't flashed for real !!!!)
Ps:
I rebuilt the GT-I9100G_ICS_Opensource_Update2 kernel, and i get my Zimage,
i am using :
- Ubuntu 11.04,
-i tried the "arm-2010q1" toolchains and the "arm-eabi-4.4.3" one ,
- am using initramfs of Mr superatmos, that he mentioned in his thread http://forum.xda-developers.com/show....php?t=1587482 .
- i am working with "android_t1_omap4430_r03_user_defconfig", imade no changes to the .config file just the CONFIG_INITRAMFS_SOURCE.
my phone is on the ICS 4.0.3 ROM, with the 3.0.8-TH [email protected] #1 kernel version
Hi people,
after downloading AnyKernel.zip, and flashing the .zip to my I9100G phone, i always got a boot loop,
After the researches that i made, i understand that the Anykernel.zip was developed to HTC smartphone and not for te I9100G,
i Solved the boot loop situation by getting a new initramfs from the CWM kernel source and compiling my zImage with the arm-2010q1 toolchains.
Salutations.
I downloaded the zip and flashed it...
Still in a boot loop. Could more light be shed on this operation. Thank you.
Hey Guys,
I'm following sony tutorial on how to build stock kernel.
It is my first time doing something like that so I don't have a lot of knowlodge.
I done the following.
- Downloaded the source
- Downloaded prebuild toolchain by doomlord
- configured the kernel
- edited menu config and got zimage
Then I'm stuck , don't know what to do next...
So my questions is :
1- from where should I get stock ics ramdisk ?
2- How can I merge the ramdisk and zimage to get my boot.img ( I mean finishing compiling process ) ?
Other questions
1- Do I need to edit menu config only to get ext support? ( I used "ncurses-devel" which enables me to edit menu config via terminal , and I think I found ext2/3 is enabled by default if I'm not mistaken!!!! )
2- How to upstream the kernel to the latest available ?
3- how to add a patch ( like power button + home key = fast reboot )
I just want to create a simple kernel close to sony's one with tiny modifications , and have some fun by compiling too
I'm using ubuntu for this...
If anyone could help by answering my questions or pointing me to the right tutorial , I'll be thankfull.
Mysteryagr said:
Hey Guys,
I'm following sony tutorial on how to build stock kernel.
It is my first time doing something like that so I don't have a lot of knowlodge.
I done the following.
- Downloaded the source
- Downloaded prebuild toolchain by doomlord
- configured the kernel
- edited menu config and got zimage
Then I'm stuck , don't know what to do next...
So my questions is :
1- from where should I get stock ics ramdisk ?
2- How can I merge the ramdisk and zimage to get my boot.img ( I mean finishing compiling process ) ?
Other questions
1- Do I need to edit menu config only to get ext support? ( I used "ncurses-devel" which enables me to edit menu config via terminal , and I think I found ext2/3 is enabled by default if I'm not mistaken!!!! )
2- How to upstream the kernel to the latest available ?
3- how to add a patch ( like power button + home key = fast reboot )
I just want to create a simple kernel close to sony's one with tiny modifications , and have some fun by compiling too
I'm using ubuntu for this...
If anyone could help by answering my questions or pointing me to the right tutorial , I'll be thankfull.
Click to expand...
Click to collapse
1.you can get ics ramdisk from ics stock kernel.
2.get kernel kitchen
1.1you need to edit ramdisk to add suport
1.2you need to find your way to upstream it.
1.3its not posibole to go to fast boot with that module coz semc bootloder use menu bootn.that conbinacion is used on samsung phones.
n1kolaa said:
1.you can get ics ramdisk from ics stock kernel.
2.get kernel kitchen
1.1you need to edit ramdisk to add suport
1.2you need to find your way to upstream it.
1.3its not posibole to go to fast boot with that module coz semc bootloder use menu bootn.that conbinacion is used on samsung phones.
Click to expand...
Click to collapse
1. Is this the right way to get the ramdisk from 2011 xperia stock kernel
Edit: used kernel kitchen for this
2. I have kernel kitchen Should I use it to assemble boot.img ?
Also in sony tut. they used mkbootimg program
Edit: will figure it out myself insted of looking dumb xD
1.1 ok
1.2 still searching but do not know how!
need help
1.3 I didn't mean fastboot I meant device reset Home + power key , already there in some xperia 2011 stock based and JB kernels.
Thanks for answering my questions , I'm noob trying to learn here
Mysteryagr said:
1. Is this the right way to get the ramdisk from 2011 xperia stock kernel
Edit: used kernel kitchen for this
2. I have kernel kitchen Should I use it to assemble boot.img ?
Also in sony tut. they used mkbootimg program
Edit: will figure it out myself insted of looking dumb xD
1.1 ok
1.2 still searching but do not know how!
need help
1.3 I didn't mean fastboot I meant device reset Home + power key , already there in some xperia 2011 stock based and JB kernels.
Thanks for answering my questions , I'm noob trying to learn here
Click to expand...
Click to collapse
look at naa kernel,its for reset keyboard...look at his source its inside kernel
ok will check that...
another thing
Can I take cwm recovery from other custom kernel and simply put it in my ramdisk sbin folder or it needs modifications?
Compiled successfully
Kernel Compiled successfully, and I flashed it to my phone. booted fine
But now I've a problems:
- A message shows "are you sure you enabled root"
I already changed ro.secure=1 to =0 in defualt.prop in ramdisk
anything else to do?
I was trying to build Kernel from original HTC Source. My rom on phone has version 2.18.401.3, but the original HTC kernel source (enru-3.1.10-g7f360be.zip) with this version did not build, because it contains only hox (endeavour) "in arch\arm\mach-tegra" not HOX+ (enrc2b). I was using the extracted config from my device. The HTC kernel source with the biggest number (2.18.1136.2, enrc2b-3.1.10-42105bd.zip) builds properly but the merged boot.img did not boot. I checked with other boot.img from HOX+ i.e. from cyanogenmod (unpack, repack) whether I generate a correct one, but it was binary same. So I believe the zImage has some defect. Please help.
Trivalik said:
I was trying to build Kernel from original HTC Source. My rom on phone has version 2.18.401.3, but the original HTC kernel source (enru-3.1.10-g7f360be.zip) with this version did not build, because it contains only hox (endeavour) "in arch\arm\mach-tegra" not HOX+ (enrc2b). I was using the extracted config from my device. The HTC kernel source with the biggest number (2.18.1136.2, enrc2b-3.1.10-42105bd.zip) builds properly but the merged boot.img did not boot. I checked with other boot.img from HOX+ i.e. from cyanogenmod (unpack, repack) whether I generate a correct one, but it was binary same. So I believe the zImage has some defect. Please help.
Click to expand...
Click to collapse
use this, I kept it in tact for this reason :
https://github.com/Lloir/htc_kernel_oxp/tree/master
It's the source straight from htc
you'll also need this commit https://github.com/Lloir/htc_kernel_oxp/commit/b3cade38f9d17682778ea767722d20b94696f6ae which has the defconfig unless you already have it.
Enjoy
Lloir said:
use this, I kept it in tact for this reason :
https://github.com/Lloir/htc_kernel_oxp/tree/master
It's the source straight from htc
you'll also need this commit https://github.com/Lloir/htc_kernel_oxp/commit/b3cade38f9d17682778ea767722d20b94696f6ae which has the defconfig unless you already have it.
Enjoy
Click to expand...
Click to collapse
I tried the master branch, but it make boot loop all the time. Another test would be, if you can provide me a boot.img what I can test.
I found the solution, is for me a little bit strange but it works. In case somebody can show me the big difference that I can understand the "why", whould be fine.
I used for build this toolchain: prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin stored: git clone --depth=1 https://android.googlesource.com/platform/prebuilt
before I was using arm-eabi-4.8/bin/ from master branch(not sure about git clone path)
There is now one point I did not understand, I build original source, why is then my SIM not working? (no question for pin), (Answer: Maybe are the orignal modules signed. After change the modules on /system/lib/modules/ it was working like before), because after flashing the android revolution boot.img, it was all working. Any ideas? (Answer: It is because they didn't change th zImage)