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
Hello! I just recently got a brand new MyTouch4GSlide ($5 from t-mobile xD) Anyhow since the lack of development going on for this phone I decided to join in and do my part... My original plan was to create a simple CM7 Kernel with support for UV and OC + Smartass... I have successfully in the past week set up my ubuntu virtual machine, kernel source, kitchen (boot.img extract/compile), voltage table & have successfully compiled a custom working kernel for my device, but i just need a bit of help.... I have 3 specific questions wich hopefully someone will be able to answer so I may get better with developing and continue developing in the future...
1) Adding new frequencies to the kernel
-I have created my voltage table and have added it to the file acpuclock-8x60.c (Which is corresponding to my device) located in /arch/arm/mach-msm O have also disabled the performance lock in the .config file using the make menuconfig command but when I compile the kernel and flash it setcpu does not recognize the frequencies... Did I not edit the correct file? Am I missing a lock placed by HTC somewhere else?
2) Adding Smartass
-I have found 1 source for the smartass module but whenever I try to compile the module I get #define OFS_KALLSYMS_LOOKUP_NAME 0xc009684c // kallsyms_lookup_name any reason why this is? am I using the wrong source? is there an easier way?
3) WiFi Module
-Whenever I compile my kernel the WiFi does not turn on... Probably because I have not compiled a Wifi module -_- but how can I compile a WiFi module? do I use the same source as the kernel? how would I go about doing this? how do I pack it with the boot.img?
Thats all for now... I shall edit this if I have more questions... I shall constantly be checking this thread hoping for some responses... I am eager to get this working!
Thanks in advanced! ~GiGoO
P.S. If you want you may add me on Skype if you would like to help me with this xD (robster105)
gigoo25 said:
Hello! I just recently got a brand new MyTouch4GSlide ($5 from t-mobile xD) Anyhow since the lack of development going on for this phone I decided to join in and do my part... My original plan was to create a simple CM7 Kernel with support for UV and OC + Smartass... I have successfully in the past week set up my ubuntu virtual machine, kernel source, kitchen (boot.img extract/compile), voltage table & have successfully compiled a custom working kernel for my device, but i just need a bit of help.... I have 3 specific questions wich hopefully someone will be able to answer so I may get better with developing and continue developing in the future...
1) Adding new frequencies to the kernel
-I have created my voltage table and have added it to the file acpuclock-8x60.c (Which is corresponding to my device) located in /arch/arm/mach-msm O have also disabled the performance lock in the .config file using the make menuconfig command but when I compile the kernel and flash it setcpu does not recognize the frequencies... Did I not edit the correct file? Am I missing a lock placed by HTC somewhere else?
2) Adding Smartass
-I have found 1 source for the smartass module but whenever I try to compile the module I get #define OFS_KALLSYMS_LOOKUP_NAME 0xc009684c // kallsyms_lookup_name any reason why this is? am I using the wrong source? is there an easier way?
3) WiFi Module
-Whenever I compile my kernel the WiFi does not turn on... Probably because I have not compiled a Wifi module -_- but how can I compile a WiFi module? do I use the same source as the kernel? how would I go about doing this? how do I pack it with the boot.img?
Thats all for now... I shall edit this if I have more questions... I shall constantly be checking this thread hoping for some responses... I am eager to get this working!
Thanks in advanced! ~GiGoO
P.S. If you want you may add me on Skype if you would like to help me with this xD (robster105)
Click to expand...
Click to collapse
Hey Rob, I wish you the best of luck and don't give up!
The one thing I can say is when I was compiling my own kernels a while back and when I was trying to do the exact same thing and add different frequencies, if I remember correctly, there is a couple files that need to be changed, not just one, but don't quote me on that
I would also try getting help from other phone developers too. Post in the Q&A section of the phones, you might get more help that way.
Other then that good luck!
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Hello folks!
So I read that Franco had released his kernel for our flounder/volantis. Problem is, I'd like to use fastcharge/2A charging and need the appropriate fixes for selinux and the theme engine of CM12 (all ROMs I like use the theme engine, using permissive mode doesn't help much, still crashes).
I am totally new to compiling from source, I have already managed to clone the repo for flounder from his GitHub though (https://github.com/franciscofranco/flounder).
Steps I have already done:
Code:
git clone https://github.com/franciscofranco/flounder --branch lollipop
I can't find any guides on how to compile for the N9 though, I have pretty much no idea what I need to do. Managed to understand how to apply patches, but I can't find the most important one, the one for the selinux and theme engine support. It was merged in a nightly of CM12 a few weeks/days ago, but I can't find it anywhere on the codereview page or anywhere else. I have already googled around how to compile for other devices and got the required utilities and applied some of the steps that seemed universal/exchangable with the device name I am building for. So could somebody be so kind and give me a little guide on what I need and maybe give me the link to at least the commit with the selinux patch? I'm looking forward to your replies, thank you!
Saw it on Sony development Web yesterday...it will be awesome if any developers can make a fully functional rom
Well, haven't you seen the 7.1.1? The dev is still working on it, and the next build will be on O. We're working on it now. We have a channel for the news - https://t.me/joinchat/AAAAAELTVKqh1eeAesWWXw.
p.s. Thread must be deleted now, IMHO.
Thumbs-up to kamil ochman and other devs for your great work
To do list
https://gist.github.com/bartcubbins/69d44e166b529de192f2621b498f8030
What? Me?
Hi,
I downloaded the AOSP sources from Sony the other night to build a barebones from for my Z3. However, the Leo wasn't in the device tree, but what I did see were options for the E2303 & E2333. This was for 8.0.0 OPR3, mind you, so is an Oreo.
I was successful in building the images required for flashing, however the kernel fails to boot due to missing DTB. I am currently attempting to fix this so that the boot.img will boot and hopefully have a working Oreo for our M4. The inline kernel fails, so if anyone with skills in this particular area would be greatly appreciated. I'm not a developer, merely a tinker with determination. I am currently trying different patches seen on github for tulip, however no matter what I do I can not get the missing DTB into boot.img.
Dutch Burdock said:
I was successful in building the images required for flashing, however the kernel fails to boot due to missing DTB. I am currently attempting to fix this so that the boot.img will boot and hopefully have a working Oreo for our M4. The inline kernel fails, so if anyone with skills in this particular area would be greatly appreciated.
Click to expand...
Click to collapse
Write me in PM as quick as possible, we have a team of devs, and your help will be appreciated)