Recently more and more Android developer start to developping and propose to upgrade their OS from old Froyo (Android 2.2/2.3 ) to Android 4.0 (ICS)system,even though low level 600MHz CPU/256Mb RAM Android phone
(ex. Huawei U8150 ) :
Refer to beneath thread of their activities:
1. Port ICS transition animations on EVERY ROM & EVERY PHONE Thread
( http://forum.xda-developers.com/showthread.php?t=1342117 )
2. [Huawei U8150] Ice Cream Sandwich AOSP Alpha 3 WIFI+SD WORKS
: http://forum.xda-developers.com/showthread.php?t=1366404
I hope someone of our Archos developer also can consider to develop Android 4.0 (ICS)system for Gen 8 ASAP
well the answer is easy:
and if u would have spend some time in this forum - reading - u would have it already...
Atm we got 3 main developers for our archos devices: sauron/bubu/divx
Since sauron will stick to his UD for a while as it seems hes out of the race atm
The other 2 are wokring on CM7 (-> Ginger) atm.
Even they are doing a great job we still dont have a fully bug free and installable CM7 yet...
CM9 (-> ICS) is in a very early development stage (as u already can see in any other android forum here - mostly alpha builds with barely functionality) so it's kinda meanless to switch over to it atm - since we dont have enough developers for it.
Once CM7 is fully working I think bubu/divx will head on to CM9 ofc (if they still own an archos then )
Even I know u just had good intensions - I think those [Request] threads are meanless most time - as they won't "help" anyone sadly.
Imho: if u want to contribute and take the development a step further or want to help them - join the Cyanogen Bull RC development discussions and help out with bug-reports or anything else u can do...
greez
Hello FrEcP:
Thanks for your update informations.
Sorry!I do not know how to develope Linux or Android OS and just a Android system user
However I always keep watch the new OS improvement and contribute my testing result to developer all the time and wish Archos Gen8 could be better
performace than before!!
ICS Port to our gn8 started!
letama, made an alpha version of an ICS Port for our devices
Look: http://forum.xda-developers.com/showthread.php?t=1404492
Currently the only thing that seems to run is the touchscreen (Actually the launcher is pretty smooth)! And it's booting of course
nice to see progresses in ics development for ics!!
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
So i got my Go and its pretty good overall, but im so dissatisfied that it hasnt gotten the ics update yet, even though sony has been telling us that we would have it already. so i decided to take this in my own hands and try and build my own ics, or even jb rom i have found some great Resources like linaros Linux 3.4 kernel for Android novathor and the cyanogen work in progress for the device, but since im not exactly experienced i have some questions,
what rescources from the Linux kernel are needed to run Android, and how can i make sure that a build ive made wont crash my device, can i try it in some kind of emulator, or is it too Hard to set an emu up wih the right settings for my phone?
and once again, can we please get a subforum for go here? it has the same processor as p, u and sola, and more than 55 People have requested it in the ***New device forum*** post, how many does it take?
Hi! This is maybe a general dev question, but I'd like to get an answer anyway:
what is exactly the link between an Android release and the kernel it works upon?
I noticed most recent releases use 3.0+ Linux kernels, and others (like the DSCs) use the Phoenix Universal Kernel, which is based on a 2.6.35... So I wonder: is ICS/JB in any way dependant on "newer" kernels?
I understand the answer must be closer to "no", since the pre-alpha build also uses a fork of the PUK, but the fact that it uses a *different version* makes me wonder how much work does it take to get a kernel ready for a newer release, and most importantly... why?
Thanks a lot! Total n00b here, but eager to know more.
Newer kernel not required at least for ICS.
All GB/ICS kernels are based on this kernel (and it's a Dell's lie about using same sources for 407 release as SoD was fixed there without switching timer source):
http://opensource.dell.com/releases/streak/4.05_and_4.07/
kibuuka successfully applied kgsl/genlock patch and it's the only thing actually needed for ICS.
List (a bit old) of changes in Phoenix kernel and later derivatives:
http://forum.xda-developers.com/showpost.php?p=25291276&postcount=3812
Hello XDA Forum!
I'm a new member in the forum, recently iv'e discovered the inner geek in me and decided to explore the world of roms. (yes im a newbie lol)
I hope to contribute to the forum as much as i can.
Anyway, Here's the story:
I have a Motorola Atrix 4g of course and i'm using epinter's excellent cm 10.1 rom
The only problem i have is that my favorite game Leauge of Shadows isn't working. I had the game working on epinter's cm 10 rom based JB 4.1.2 with 2.6 kernel and the game works on other JB roms with 2.6 kernel. So i believe the problem is with the kernel. With the current kernel i have ( 3.1.10) the game start but crashes alot and touchscreen doesn't work.
So my question is, is there anyway to run this game? can i run a specific app in a 2.6 kernel will my device has 3.1.10?
I've tried to install diffrent kernel but failed to install for some reason.
Any help will be much appriciated!!
Hi! Welcome to the forums!
Short answer: Not yet.
Long answer: As you should know, anything with the 3.1 kernel is considered an (not so) early stage alpha. It isn't meant to be used as a daily driver, only as testing and development. Right now, the focus of the development is set into modem drops and audio issues, once all basic things are working, then they can focus on other things, like the issue you have.
Also, kernel is the main piece of software any device (computer, smartphone, etc) uses. on windows xp, the kernel is ntkernel.exe, on linux and android is vmlinuz.
So far the only solution is to install a rom that doesn't use the 3.1 kernel, such as cm10 (not 10.1), cm7 or early iterations of atrics
Thanks!
andresrivas said:
Hi! Welcome to the forums!
Short answer: Not yet.
Long answer: As you should know, anything with the 3.1 kernel is considered an (not so) early stage alpha. It isn't meant to be used as a daily driver, only as testing and development. Right now, the focus of the development is set into modem drops and audio issues, once all basic things are working, then they can focus on other things, like the issue you have.
Also, kernel is the main piece of software any device (computer, smartphone, etc) uses. on windows xp, the kernel is ntkernel.exe, on linux and android is vmlinuz.
So far the only solution is to install a rom that doesn't use the 3.1 kernel, such as cm10 (not 10.1), cm7 or early iterations of atrics
Click to expand...
Click to collapse
Thanks for the answer!