I built kernel 2.6.32 with vmsplit 3g, which is required for cm7, yesterday and rictec compiled a cm7 build with that kernel and it booted fine, at least once battery was removed.
Basically, its not in a usable state at all but the fact we got it booting is nice progress and we're working on fixing each issue at a time.
Issues:
No Radio, No Wifi, No Camera
No USB (Mounting / ADB broken)
Battery has to be removed if not blue screen occurs (doesn't happen to all testers, might be specific to some S7's Revisions)
rictec deserves most of the credit since he is the one who did the vendor config.
I am currently cleaning that vendor config up and progress is going fine.
Currently: Discussion is mostly done on irc but discussing on here is fine.
irc channel #androidtablets on freenode irc server.
Current Developers/Tester:
Razor950
Rictec
Joenilan
WillEY_
I will post a link to a extremely alpha release once we get usb working but if you would like to test, just drop by the irc
cannot wait for this!! thanks in advance for all your hard work and effort!!!
major props for working on this. I returned my s7 until I have time to do this sort of thing or until someone else does it
Project died?
nop
in my case is i lost the spare time i had so this is going to take longer thats it
video call
i hope in this rom there's a video call feature, really need it..
I want to bring some help but I need some info on compiling the aosp.
how the progress of this project? hope this project will completed soon xD
died progress???????
razor950
Try this kernel: http://threader.zapto.org/s7/kernel/2.6.32.9-ideos-fs-snd-drm-sane-5-vmsplit3g.tar.bz2 Tested it for a few days now in android and linux, seems stable, i really only need to do some more fiddling with alsa to get it working in linux.
threader said:
razor950
Try this kernel: http://threader.zapto.org/s7/kernel/2.6.32.9-ideos-fs-snd-drm-sane-5-vmsplit3g.tar.bz2 Tested it for a few days now in android and linux, seems stable, i really only need to do some more fiddling with alsa to get it working in linux.
Click to expand...
Click to collapse
still nothing with this kernel. one of our friend used this kernel to build CM7, still got difficulties with rendering andreno performance
Please dont let this project die.
Sent from my U20i using XDA App
txpxsx
I compiled that kernel some weeks ago for my Gnu/Linux project ( http://forum.xda-developers.com/showthread.php?p=14417403#post14417403 ), making the sources compile required hours for fixing errors and ponds of coffee, who did the kernel work for you guys? I believe the andreno is used using a propriety library on android, isnt it? I will certainly try compiling 2.3.7 tho.
Can you port original kernel 2.3.2 to 2.3.7?... If yes we can try a ICS port.
I have the original 2.3.2 kernel.
Sent from my GT-I9000 using Tapatalk
i have 2.3.7 compiled, i just need to figure out how to make a boot image the device will accept, compiled 2.3.7 tonight, seems the 3g split doesnt boot here, probably runs out of address apace?.
Okay, im at the gfx corruption bit now, thing is , it also happens with 2.2.2, so the problem is probably in the ramdisk, i've used this kernel with 2.2.2 before, but then with the old ramdisk
Ok, merged the init's and stuff, but noticed in the end the problems were down to one permission in ueventd.rc ....
/dev/kgsl-3d0 0666 root root
/dev/kgsl-2d0 0666 root root
gaah!
That error occurs from system/core/rootdir/ueventd.rc . The huawei s7's kernel uses the "old" way of kgsl-3d0 and 2d0 instead of just kgsl 0/1
anyway, andreno is now back to usable in 2.2.2 , no corruption etc. http://threader.zapto.org/experimental/boot-new-1.img Testing it now with dragon fly.
Now i just need to back everything the hell up and try 2.3.7 =) (bootloop currently)
Well, i've been making steady but slow progress, im currently using these to boot android 2.2.2:
http://threader.zapto.org/experimental/boot.img.orig
.orig btw because i was sidetracked with trying to increase the /data partition with a 2gig ext4 partition and use userdata as swap
I also just discovered some malconfiguration for my 10x atleast, in BoardConfig.mk
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00500000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x0fa00000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x0a000000
BOARD_FLASH_BLOCK_SIZE := 131072
BOARD_DATA_DEVICE := /dev/block/mtdblock4
BOARD_DATA_FILESYSTEM := yaffs2
BOARD_SYSTEM_DEVICE := /dev/block/mtdblock2
BOARD_SYSTEM_FILESYSTEM := yaffs2
Isnt this still an option?
http://gitorious.org/cm4l/vendor/bl...1a8af28f1/cyanogen/products/cyanogen_salsa.mk
#Build with 2G map (Acer used for their ROMs), or remove this line to build with 3G/1G (standard build that works with phhusson's Froyo kernel)
#PRODUCT_SPECIFIC_DEFINES += TARGET_PRELINKER_MAP=$(TOP)/vendor/cyanogen/prelink-linux-arm-liquid.map
Anyway, i fixed up the kernel some more, discovered a problem with the previous 3g split one using some flags that didnt work. Tested this one properly for a good few in linux before releasing.
2g/2g split. - Usable with 2.2
http://threader.zapto.org/s7/kernel/2.6.32.9-ideos-fs-snd-drm-sane-12.tar.bz2
http://threader.zapto.org/s7/experimental/boot.img-2g
http://threader.zapto.org/s7/experimental/recovery.img-2g
3g/1g split - Usable with 2.3
http://threader.zapto.org/s7/kernel/2.6.32.9-ideos-fs-snd-drm-sane-12-hard-3gsplit.tar.bz2
http://threader.zapto.org/s7/experimental/boot.img
http://threader.zapto.org/s7/experimental/recovery.img
Edit 27/2/12 - Compiled android with 4.5.x :
NOT FOR END USER! ONLY FOR PEOPLE THAT CAN HELP DEBUG USING EITHER FASTBOOT AND/OR CHROOT AND LOGCAT ETC!
This is my result so far
3g/1g vmsplit 2.3.7
http://threader.zapto.org/experimental/system.img.bz2
http://threader.zapto.org/experimental/system-1.tar.bz2 # Tar achive of img content
2g/2g vmsplit 2.3.7 - That only almost boots with a 3g/1g kernel even though i've used a 2g prelink map and all, why?
http://threader.zapto.org/experimental/system-2g.img.bz2
To get some useful information.
fastboot -c 'androidboot.hardware=qsd8k_s7' boot boot.img
I dont know exactly what im doing wrong here, but no matter how much i fiddle with executable binaries, libraries, frameworks or whatever else, i still cannot get this to boot properly. If anyone's a rom wiz please give me a shout, experience on the qsd8k would help! There has to be something obvous im missing. It gets to the point where its launching zygote, then two processes crash, and this it can do all year long if i leave it.
I know threader is trying to get 2.3.7 running at the moment, which would be amazing, however I noticed that someone on the cyanogenmod forums has a CM7 ROM up and running.
http://forum.cyanogenmod.com/topic/12370-huawei-ideos-s7/
maybe devs from both forums can get together. If not then maybe something of use there for threader to get his kernel fixes working.
Either way its great to see a CM7.2 port that boots
Sweet, thanks, got it, found that file a few moons ago, but i couldnt download it then :S
Apparently there were problems with my kernel config and init.rc for 2.3, libcutils, and andrino_200.so, and perhaps one more, it also could not create /dev/dun, but atleast im able to debug these problems now and spit out something that will work. ;>
The new kernel is called blaah*-13 in the kernel directory, but i will spend some more time on all this once i have the system running properly. Thanks, i was pretty much searching everywhere else for the problem! That cm7 boot image kernel has 1ghz chosen but have forgot to bump the voltage to 1300 tho btw.
Hey guys, keep up the good work on 2.3, tablet is currently for sale in Germany (80 €), so there will be some new users soon
Related
Can we expect Dell to release the kernel source? Are they required to release it?
Yes.......
they are supposed to release it ...
weather they do is another thing...
and if they don't who's gona fight em ... no one can afford it
http://gpl-violations.org/
how do we tell them that we want the source of dell and get them to get it??
@MattAtDell tweeted the other day in reply to some other random user that he would look into it, so its a good outlook that the kernel source will be made available... This will probably be the first phone I'd be willing to try and build a kernel for, lol. I'm sure we'd have a vanilla build of Android 2.1 (probably a bit broken) already IF we had the kernel source, 1.6 and 2.1 run the same kernel version 2.6.29 (froyo is 2.6.32 so it might actually take a bit more effort). This also explains why they show a 2.1 build even though they've committed to go straight to 2.2.
Random user my arse..
He was the first one from Dell that bothered to respond to *MY*query.
You can already build a vanilla froyo including kernel, but its taking a lot of experimenting to get a working combination of settings (I'm using the codearoura (qualcomm) surf ) git..
I may try a generic android git to see if it works..
jmhalder said:
@MattAtDell tweeted the other day in reply to some other random user that he would look into it, so its a good outlook that the kernel source will be made available... This will probably be the first phone I'd be willing to try and build a kernel for, lol. I'm sure we'd have a vanilla build of Android 2.1 (probably a bit broken) already IF we had the kernel source, 1.6 and 2.1 run the same kernel version 2.6.29 (froyo is 2.6.32 so it might actually take a bit more effort). This also explains why they show a 2.1 build even though they've committed to go straight to 2.2.
Click to expand...
Click to collapse
Any success compiling a kernel 2.6.33+ for Streak?
Any success compiling a kernel for Dell Streak? Where to start for it? I've been trying cyanogen kernels, but they don't seem to work or maybe I am doing something wrong creating the boot.img file. Any doc for it?
Thanks in advance!
Kernel source for Dell Streak?
Hi,
I was wondering whether the android kernel uses some kind of standardized kernel versions and configurations that allow people to add a module to an existing kernel in, let's say a dell streak tablet/smartphone.
Is it easy to get the kernel configuration and patches to compile modules for the streak?
Do they put some kind of locking so that nobody having a jtag tool can make the configuration changes to make the kernel read a new module?
jsmanrique said:
Any success compiling a kernel for Dell Streak? Where to start for it? I've been trying cyanogen kernels, but they don't seem to work or maybe I am doing something wrong creating the boot.img file. Any doc for it?
Thanks in advance!
Click to expand...
Click to collapse
ive had lots of success in building kernels, its just that none of them boot!
(technically I think this is known as not succeeding )
Building != Booting
So we have same situation... It's not a matter of building a kernel but booting it right on the device.
But what would be failing? Has anybody seen any log about what is happenning during boot to know what is failing? Because I would understand that a valid kernel would boot the device but some parts that would need propietary code wouldn't work (for example wifi, or whatever)... but no boot at all is quite strange.
Can anyone confirm at least a successful module compiling/running?
Not me
maxrfon said:
Can anyone confirm at least a successful module compiling/running?
Click to expand...
Click to collapse
Not me! Is it really impossible the get it running?
If you ask dell for the linux source code, they must provide it. They have to make the exact source code available that can be used to compile the shipped binaries.
If they won't make it available upon request go inquire with http://gpl-violations.org as recommended earlier.
hey dcordes glad to see you here, I have asked via a few avenues, but was waiting till its available in the USA before pressing them further
theres a Guy popped up on modaco yesterday that thinks the boot.img needs 2k page file but 4k padding and suggested some changes to makeimg to get it to boot properly.
I'll play again later on
quiet bump, tweet by me:
http://www.twitlonger.com/show/3g0ebt
I also put something on twitter.
If you are as pissed as everybody about the lack of the sources, go write a mail to https://lists.gpl-violations.org/mailman/listinfo/legal
They are the attorney to each user of GPL licensed software ! They will tell you what to do. If you browse the archives they will advise to keep asking for sources. We did that. No it's time to collect evidence of the ignored requests and take further steps.
But first we should let that mailing list know ! If nobody will mail it in the next few days I will. I don't have the device but I hate industry going ignorant on customers. It is also an insult to everybody working on the Linux kernel source code. And that's many and includes myself.
cheers
dcordes said:
But first we should let that mailing list know ! If nobody will mail it in the next few days I will. I don't have the device but I hate industry going ignorant on customers.
Click to expand...
Click to collapse
I do have the device.
http://lists.gpl-violations.org/pipermail/legal/2010-September/002235.html
Hey guys. So would anyone like to help me out in building an AOSP ROM for the LG Optimus S?
Currently, I have compiled the LG AOSP 2.2 kernel (zImage), and compiled the Android 2.2 AOSP system. Apparently now I need to get the LG vendor tree so I can compile that too into a working system? Can anyone help me out with that? This is my first time ever building a ROM from source code.
i hope someone will listen your help request
I hope so too... I hope so too.
I hope so too, would be nice to have another ROM option for the Optimus S. And this is a stepping stone to CyanogenMod on it
I'm also interested to create a fully working build of 2.2.2 AOSP Froyo.
But I'm new to the Android's world. I need that someone teach me how to build android from source. Also I need to know how to port the LG's drivers.....
I'm willing to help, but I can't program in any language. However, I know the basics, I can compile stuff, can do fairly well with the command line, I use Arch Linux as my main OS (so I can pretty much do compilations and stuff without a problem), etc.
I still don't know much about Android at this time, and contributing to this "project" may be my way of getting to know things
Count be in.. i m good with C,C++ ,shell scripts .tell me wat to do..i m new to android
Building Android from source can be quite tricky when proprietary software must be compiled in. I'm compiling since 2 months on gingerbread and nothing but phone is working... no USB,no camera, no bluetooth ... its now simply a phone^^
But, if your are lucky with Froyo you need only the source from android 2.2.x and the one shipped by LG (I know there are some sources for Optimus One, but don't know about Optimus S). Put it all together and compile the code - while/after compiling you will see lot of errors, there must be fixed by yours.
Have a look at cyanogen CM6.1, there have many fixes built in. If you would like to build a brand new system from scratch by yourself, i'll wish you many luck and lots of time
andy572 said:
Building Android from source can be quite tricky when proprietary software must be compiled in. I'm compiling since 2 months on gingerbread and nothing but phone is working... no USB,no camera, no bluetooth ... its now simply a phone^^
But, if your are lucky with Froyo you need only the source from android 2.2.x and the one shipped by LG (I know there are some sources for Optimus One, but don't know about Optimus S). Put it all together and compile the code - while/after compiling you will see lot of errors, there must be fixed by yours.
Have a look at cyanogen CM6.1, there have many fixes built in. If you would like to build a brand new system from scratch by yourself, i'll wish you many luck and lots of time
Click to expand...
Click to collapse
So in your opinion it would be a lot easier to just build a CyanogenMod 6.1 ROM? Sounds like a plan. I read that I could just pull stuff from the Legend and use that as well? Could you help me with that stuff (pulling from the Legend source, that is)?
Legend stuff is less compatible then i thought. You can't use nothing from there.
As my work at 2.3 is now stopped (I haven't bugs related to working stuff, I have no idea what to do with 3d and gps and I too lazy to patch libcamera now) I hope to start work on CM6 next holiday's.
mik_os said:
Legend stuff is less compatible then i thought. You can't use nothing from there.
As my work at 2.3 is now stopped (I haven't bugs related to working stuff, I have no idea what to do with 3d and gps and I too lazy to patch libcamera now) I hope to start work on CM6 next holiday's.
Click to expand...
Click to collapse
We'll work on it together then? I started a GitHub. github.com/mrinehart93
mrinehart93 said:
We'll work on it together then? I started a GitHub. github.com/mrinehart93
Click to expand...
Click to collapse
As I already got working GSM/Audio/WiFi/Bluetooth/USB/Sensors in 2.3 (port to 2.2 is easy) I will continue work in my repo https://github.com/mik9
Ypu can send your patches via "pull request" functionality.
mik_os said:
As I already got working GSM/Audio/WiFi/Bluetooth/USB/Sensors in 2.3 (port to 2.2 is easy) I will continue work in my repo https://github.com/mik9
Ypu can send your patches via "pull request" functionality.
Click to expand...
Click to collapse
I won't have any time to work on CM tonight or probably the rest of this week, but as soon as I do I'll set up my Github.
I'm working on a Gingerbread kernel for the Streak, working from the 309 drop from Dell and tracking the android-msm-2.6.35 branch from CodeAurora.
In another thread I saw DJ_Steve mention that there's a tight coupling between AMSS and kernel version. How much of an issue is that going to be with a significantly different kernel?
It mostly only applies with stock roms.
Streakdroid is still based on the 309 kernel but for the most part it wont care what baseband you have as long as it's a 3xx one. All the other libs are mostly from what the stock version they're based on. 1.7/318 1.8/322 1.9/345
Stock kernels might check more closely to see that they match and complains if they dont.
yea the amss is only related with stock kernels, custom doesn effect much, and theirs a newer kernel available direct from dell now thanks to me and a couple contacts in dell
I for one cannot wait for your next rom Steve - keep up the good work
DJ_Steve said:
yea the amss is only related with stock kernels, custom doesn effect much, and theirs a newer kernel available direct from dell now thanks to me and a couple contacts in dell
Click to expand...
Click to collapse
Yep, I see the Gingerbread alpha on the open source site. Thanks!
I took a look at the Dell GB Alpha and noticed that Dell is working from an older CodeAurora drop. So I've decided to merge the Dell changes into the work I've already done so as to be able to track CodeAurora.
Something else I noticed was that they're including the bcm4325 drivers. The msm tree uses 4329 drivers that support both the 4325 and 4329.
yes because the 4329 driver wont compile yet
I don't know if they _work_ yet, but the latest bcm4329 drop from CodeAurora compiles fine. Or, I should say, they at least build "drivers/net/wireless/bcm4329/built-in.o". I've got one last issue in merging the Dell source with CodeAurora before I can get it to fail building System.map which is when I'll know for sure that they compile
This is a dev thread. Do not install this release unless you know what you're doing. Do not post if you have nothing to contribute.
This is very early build, we're behind other qsd8k devices but will eventually catch up
Big thanks to all qsd8k developers working on this (N1, Desire, HD2, X10).
[KERNEL]
- ol' good 2.6.29-SEMC
- fixed touchscreen driver (now backward-compatibile with Gingerbread)
[ROM]
- partially based on drewis release (thanks!) - currently I don't have access to PC that could handle compilation of the whole thing
If someone could compile clean es209ra build and upload it would be awesome.
[WORKING]
- it boots
- radio, calls, txt (sms)
- audio partially working (in-call is fine, playing mp3/ringtones leads to WLOD)
- bluetooth, GPS seem to work
- wifi almost working ("can't find wlan0 device")
- mobile data (it gets IP but disconects afterwards, needs investiagtion)
[NOT WORKING]
- most of the stuff does not work
- quite unstable
[SOURCES]
Will upload all of the useful code/fixes here.
- ICS + GB compatibile touch driver: es209ra_touch_mt.c
- compatibile ramdisk (props FXP): http://www.mediafire.com/?1n51pn1upwv79ur
[DOWNLOAD]
Alpha1 ROM (for CWM5) + corresponding kernel (flashtool) is here:
http://www.mediafire.com/?ht6p6tbpj2988d4
Cheers,
z
Just did a major clean up on this thread mates....no more "thanks" posts please. If thankful... click the thanks button.
Regards,
M_T_M
Finally we get it. aZuZu is working on ASOP ICS 4.0.1. This may help him work easier. So with locked bootloader, can we flash cause' you wrote there CWM5?
VIDEO
here's a video for ics on x10 alpha build 1
http://www.youtube.com/watch?v=bsOFn4YLvZU
@frosty666 please kindly include this on your ics discussion thread.
thankz
hi zdzihu, its great to see you back! is this only temporary or, are you going to be more active, like before?
mmmkay, I'm not dev, but I want to ask if you're compiling this from ground up (like Jerpelea's CM7), or you're like just mashup of current SE and ICS sources. if its a mashup, I can help. but I do very little design from ground up things.
Sent from my X10i using xda premium
if you have fixed audio hw sources i could recompile..
altho i have complete es209ra compile with ics hw, old cm gralloc / copybit sources and generic audio..
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
I help if u want
Hello guys, I'm new to the forum and I hope to see well with you.
I would be willing to help compile the source since EXCLUSIVELY use only Linux operating system and is much easier to work on programming because most of the libraries are already installed by default, I hope I was clear.
greetings
Joseph
zdzihu said:
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
Click to expand...
Click to collapse
yaay Z!!!
glad to see back!
now i feel so bad & depressed that i dont have a working x10 with me
hope that service center guy is able to repair it again...
@aZuZu
can u please upload ur work-in-progress sources to git... i know how much fixing u have done... it might help other too
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
so good
I will try to build ICS this weekend!
I have no time this weekday
Zdzihu, if the wifi still reports the same error (can't find wlan0 device), it probably means that the kernel refers to wlan interface as eth0. Try changing the wifi.interface entry in build.prop to eth0.
little help for folks that compile ICS on weak pc
make: *** [out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/noproguard.classes-with-local.dex] Killed << if processes during compile get killed try this script > Fix Swap
Well to me helped so maybe it helps other ppl.
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
WHAT IS IT WITH SOME OF YOU GUYS, IT IS DEV ONLY THREAD AT THE REQUEST OF THE DEVELOPER, IF YOU CAN'T FOLLOW SIMPLE RULES THEN INFRACTIONS WILL BE HANDED OUT, YOU HAVE NOW BEEN WARNED!
wbbigdave said:
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
Click to expand...
Click to collapse
gunzip -c <ramdisk.gz> | cpio -i
Cheers,
z
The next member who disregards a developers request and posts in a non helpful way will be banned for a week.
i encourage any dev or helpful member to pm me or any other mod with the offending post and the user will be dealt with
Please don't reply tp them to tell them they are breaking th rules as you post will then also be rule break worthy
Hugs and kisses
PiLoT
http://review.cyanogenmod.com/#q,status:merged+project:CyanogenMod/android_frameworks_base,n,z
sorry for posting here. but is for development. for ICS, can we used modified 2.6.29, and modify, like what zdzihu did, it so it 100% or do we have to use 3.x (or whatever) becuase I'm starting to do kernel mods and I want to see what I can contribution.
so in all, does the newest kernel have to be ported? or can we continue using good old 2.6.29 and keep Modding it? (hopefully camera will work, drivers have to be rewritten for kernel. and no one likr to write drivers)
Sent from my X10i using xda premium
In case, we can see here how they get the SD Card working
http://forum.xda-developers.com/showthread.php?p=19774268#post19774268
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