Ok guys, thanks to munjeni we've got a working ICS CM9 ROM but there are a few bugs so I will look over other devices sources and come with some ideas.
Camera Bug
Here are our sources and here are the sources from a similar device. If you look closer you will see that this file is similar to this file, same thing applies for the other files but there is one file that is different, this one.
I'll come with an edit as soon as I find the problem.
Audio bug
Like mujeni said: " I dont know which android audio library source code to use with this rom?" but I think that these files should do the job https://github.com/cm2pico/ics_htc_pico/tree/master/libaudio or we can take the libs from HTC desire V.
WIFI
I will come with an edit as soon as I find anything
CM9 ramdisk
Same here
These are just possibilities, for the moment.
Anyone with some C++ knowledge could help, here you should find more helpful things.
camera + audio + wifi fix ?
sorry easy english, not understand ?
Thank you thank you thank you!!!!!!!!!
Sent from my HTC Desire C using xda app-developers app
TheRedHunter said:
Ok guys, thanks to munjeni we've got a working ICS CM9 ROM but there are a lot of bugs so I will look over other devices sources and come with some ideas.
Camera Bug
Here are our sources and here are the sources from a similar device. If you look closer you will see that this file is similar to this file, same thing applies for the other files but there is one file that is different, this one.
I'll come with an edit as soon as I find the problem.
Audio bug
Like mujeni said: " I dont know which android audio library source code to use with this rom?" but I think that these files should do the job https://github.com/cm2pico/ics_htc_pico/tree/master/libaudio or we can take the libs from HTC desire V.
WIFI
I will come with an edit as soon as I find anything
CM9 ramdisk
Same here
Anyone with some C++ knowledge could help, here you should find more helpful things.
Click to expand...
Click to collapse
Have you actually gotten the audio and camera to work? Or are these just possibilities?
SeannyM said:
Have you actually gotten the audio and camera to work? Or are these just possibilities?
Click to expand...
Click to collapse
Doesn't work yet... the sources are a bit different, munjeni is using a header, the other developer doesn't. About audio bug, I haven't tested yet, maybe I will try with the libs from desire V.
So yes, for the moment these are just possibilities.
@uchihasparky don't thank me ...I am just trying something, you should go on every munjeni's post and thank him.
Lol I also thought you had for sure fixed these things.
Sent from my HTC Desire C using xda app-developers app
I can help you try to fix this, I have been trying to do this too. I will download source now.
hi,I m cm dev for HTC pico
Just take cm10 HTC pico source from my github,change name,u will have functional cm10.HTC golf is very similar to pico...
We have developed fully functional cm9 and cm10
Galaxys2 : Powered by Exynos4 Dual ™
Wow , hope this works
Btw sakindia kudos to you and the other devs for successfully porting the linux 3 kernel from golfu to pico :thumbup:
Sent from my HTC Desire C using xda app-developers app
U will just have to make changes for WiFi,USB and bluetooth
Galaxys2 : Powered by Exynos4 Dual ™
@sakindia123 could you try to compile a rom for a preview for us, to see what works on this phone?
OMG I so want that to work
Sure, I'll compile the sources soon, thank you very much.
CM10 if it ends up working I will go insane!!
Sent from my HTC Desire C using xda app-developers app
aaaawesome!
If this does work, post how to set up environment workspace. It would be much appreciated, and would help with my ROM.
So guys,I am documenting the changes required for golf for cm10 from source
1)Kang our cm10 pico device config,change pico to golfu or golf
2)Set up your vendor tree as exactly how I have done in my github,but with binaries pulled from your device
3)Add support for NFC(golf has a pn544 NFC chip,pico has squat)
4)Change vold configuration and lunfile(u guys use a ChipIdea USB controller ,we use a standard msm72k controller)
5)Change Bluetooth configuration(golf uses Texas Instruments chip,we use Broadcom one
5)Change user space firmware for atheros 6000 WiFi driver,we have a broad com one.Getting WiFi to work might be tricky,atheros is known for not documenting sources .
Bam.U have fully functional Cm10.i am also working on cm10.1 for HTC msm7x27a devices, so u will have a base
KangBanged from my Galaxys2 : Powered by Exynos4 Dual ™
Eu desire c does not have NFC , so 3 step is unnecessary
Sent from my HTC Desire C using xda app-developers app
iluhanich said:
Eu desire c does not have NFC , so 3 step is unnecessary
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
The uk one does tho so be handy to have nfc support if it can be done easily
Sent from my HTC Desire C using xda app-developers app
sakindia123 said:
So guys,I am documenting the changes required for golf for cm10 from source
1)Kang our cm10 pico device config,change pico to golfu or golf
2)Set up your vendor tree as exactly how I have done in my github,but with binaries pulled from your device
3)Add support for NFC(golf has a pn544 NFC chip,pico has squat)
4)Change vold configuration and lunfile(u guys use a ChipIdea USB controller ,we use a standard msm72k controller)
5)Change Bluetooth configuration(golf uses Texas Instruments chip,we use Broadcom one
5)Change user space firmware for atheros 6000 WiFi driver,we have a broad com one.Getting WiFi to work might be tricky,atheros is known for not documenting sources .
Bam.U have fully functional Cm10.i am also working on cm10.1 for HTC msm7x27a devices, so u will have a base
KangBanged from my Galaxys2 : Powered by Exynos4 Dual ™
Click to expand...
Click to collapse
How do you pull the binaries from our device? There is no extract-files.sh? How to change bluetooth, vold, lunfile, user space firmware, wifi? Could you please give exact steps? Sorry to bother you, it's just your steps aren't very detailed, at least for me.
Related
I've been trying to port over ICS from DHD but no success(ROM doesn't boot, stuck at HTC splash screen)
Since I'm a noob to ROM porting any help would be appreciated.
I followed a simple guide which told me to replace certain files in the boot.img and system folder along with a couple of files more.
I used the ICS rom of DHD and MIUI ICS rom for IncS.
cooljais said:
I've been trying to port over ICS from DHD but no success(ROM doesn't boot, stuck at HTC splash screen)
Since I'm a noob to ROM porting any help would be appreciated.
I followed a simple guide which told me to replace certain files in the boot.img and system folder along with a couple of files more.
I used the ICS rom of DHD and MIUI ICS rom for IncS.
Click to expand...
Click to collapse
a suggestion for you...try the cm7 rom instead of miui ics build.
thanks for your effort. i will also dig about it but after my last exam. i request everyone who could contribute....its for our phone.
keep trying bro.
If it is simple enough I could give it a try, any moderate to advanced programming I wouldnt have a clue
I have been working on this over the last couple of days and so far my port has touchscreen, audio, RIL, wifi, 2D HW acceleration, notification LED and proxy sensor working (pretty much the same as the DHD port I think). Last I tried the microphone wasn't working for calls but it should be fixed in my new build.
I will post it up in the next couple of days once it's ready to be used. I've been busy with other things so haven't had a chance, plus I don't have access to the developer section yet.
st.matt said:
I have been working on this over the last couple of days and so far my port has touchscreen, audio, RIL, wifi, 2D HW acceleration, notification LED and proxy sensor working (pretty much the same as the DHD port I think). Last I tried the microphone wasn't working for calls but it should be fixed in my new build.
I will post it up in the next couple of days once it's ready to be used. I've been busy with other things so haven't had a chance, plus I don't have access to the developer section yet.
Click to expand...
Click to collapse
good job. if you need any help just let us know. i will try to look into it today night positively.
Anyone got any guides/tutorials kinda stuff for this?
Nopes, no tuts as such... just small guides....
Any links??
Keen to see how much of your port is working so far as well
EDIT: just tried it myself using a guide in other thread. used the DHD beta 3 and vivo latest CM7 nightly and is stuck at htc splashscreen
EDIT2: didnt sign the rom before, lets try that again...
EDIT3: still stuck on splashscreen
I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.
st.matt said:
I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.
Click to expand...
Click to collapse
Sounds good, what ROMs did you use to port it?
st.matt said:
I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.
Click to expand...
Click to collapse
Looks like a nice birthday gift... ;D
Unfortunately I wasn't able to get market working.. but anyway here is the first Alpha.
It is based on a combination of the Desire HD build and using the kernel by TwistedUmbrella. I have a device setup to work with TwistedUmbrella's ICS tree but I don't know if it will 100% build successfully at this stage (takes forever to build on my 5 year old computer..). All credits go to the DHD guys as they have done basically everything, I've just made it work (or at least, most of it) on the vivo.
Working:
- Hardware 2D/3D Hacks
- Touchscreen
- Bluetooth
- Wifi (not tethering)
- RIL
- Data
- Sound
- Sensors
- Rotation
- Status LED
Not Working:
- Hardware video acceleration
- Tethering
- UMS (use adb instead)
- USB tethering
- Camera
- Google account (so Gmail, Market all not working)
The account error seems to be something to do with xt_qtaguid.. here is the log info:
Code:
I/qtaguid ( 3029): Failed write_ctrl(u -1) res=-1 errno=9
I/qtaguid ( 3029): Untagging socket -1 failed errno=-9
I/GLSUser ( 3029): GLS error: NetworkError
Might be a problem with the kernel, but I'm not really sure. Any help would be nice, I've spent about 5 hours on this and gotten nowhere.
Link: http://www.multiupload.com/Z4JKSC1JK2
Please don't post bugs reports just yet. This is the first alpha, it's not really a daily driver and I know that there are bugs. Post fixes instead.
Sounds awesome Matt! what are you using to break down and build the rom??
Will give it a go in the morning and post any other feedback
Nice work you got slot further than I did! I will see if I can contribute anything to your build once I have it installed.
The Desire S version is pretty good, and the hardware is almost identical to the Inc S, maybe that would make for a better base?
Sent from my HTC Incredible S using xda premium
l0st.prophet said:
Nice work you got slot further than I did! I will see if I can contribute anything to your build once I have it installed.
The Desire S version is pretty good, and the hardware is almost identical to the Inc S, maybe that would make for a better base?
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
That's probably not a bad idea. I will see if I have time tonight to try and see if I can get market working by using some of the desire s stuff.. or maybe someone else could try as well.
For anyone that gives it a go, just keep in mind that the button backlight levels are in framework-res.apk, and will need to be recompiled from source or decompiled and edited to get the levels right.
P1n3apqlExpr3ss said:
Sounds awesome Matt! what are you using to break down and build the rom??
Will give it a go in the morning and post any other feedback
Click to expand...
Click to collapse
Well so I have checked out TwistedUmbrella's ICS tree and 7x30 kernel, and have made a vivo config for both. I've then used the prebuilt DHD ICS rom and taken out the DHD stuff and put in stuff from the vivo Miui.us rom. Then I've just gone through and fixed the boot ramdisk, built the kernel and put it together for the boot image.
In future I will try building from source, but as I said it takes a very long time for me.
st.matt said:
Well so I have checked out TwistedUmbrella's ICS tree and 7x30 kernel, and have made a vivo config for both. I've then used the prebuilt DHD ICS rom and taken out the DHD stuff and put in stuff from the vivo Miui.us rom. Then I've just gone through and fixed the boot ramdisk, built the kernel and put it together for the boot image.
In future I will try building from source, but as I said it takes a very long time for me.
Click to expand...
Click to collapse
This sounds WAY over my head, all I tried was unzipping CM nightly 146 and the DHD build and changing files, rezipping and signing it. No wonder I got stuck at the HTC splashscreen...
Keep up the good work
st.matt said:
Unfortunately I wasn't able to get market working.. but anyway here is the first Alpha.
It is based on a combination of the Desire HD build and using the kernel by TwistedUmbrella. I have a device setup to work with TwistedUmbrella's ICS tree but I don't know if it will 100% build successfully at this stage (takes forever to build on my 5 year old computer..). All credits go to the DHD guys as they have done basically everything, I've just made it work (or at least, most of it) on the vivo.
Working:
- Hardware 2D/3D Hacks
- Touchscreen
- Bluetooth
- Wifi (not tethering)
- RIL
- Data
- Sound
- Sensors
- Rotation
- Status LED
Not Working:
- Hardware video acceleration
- Tethering
- UMS (use adb instead)
- USB tethering
- Camera
- Google account (so Gmail, Market all not working)
The account error seems to be something to do with xt_qtaguid.. here is the log info:
Code:
I/qtaguid ( 3029): Failed write_ctrl(u -1) res=-1 errno=9
I/qtaguid ( 3029): Untagging socket -1 failed errno=-9
I/GLSUser ( 3029): GLS error: NetworkError
Might be a problem with the kernel, but I'm not really sure. Any help would be nice, I've spent about 5 hours on this and gotten nowhere.
Link: http://dl.dropbox.com/u/52030869/vivo_ics.zip
Please don't post bugs reports just yet. This is the first alpha, it's not really a daily driver and I know that there are bugs. Post fixes instead.
Click to expand...
Click to collapse
great job bro! just need the camera and gmail account. rest everything is perfect ! i will try it today and see. thanks for your efforts
Download link not working... Too much traffic :/
Sent from my Incredible S using XDA App
Splux said:
Download link not working... Too much traffic :/
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
yes its not working. can we get other links please?
Yeah sorry I didn't realise dropbox imposed download limits. Here is another download link: http://www.multiupload.com/Z4JKSC1JK2
I think I may have fixed Google accounts though, so there might be another download in another 30 minutes or so.
Original APP folder from most current leak::
App Folder
Original Framework folder from most current leak::
Framework Folder
Tiny's One_V Port so far:
(Boots to the Bootanimation.)
tiny4579 said:
Here is my logcat, maybe someone can figure it out. I'm taking a break for now:
logcat.txt
My current ROM is below.
sense-ics-inc.zip
Click to expand...
Click to collapse
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTCCN_CHS_1.68.1400.2_Radio_20 .67.30.0831U_3831.15.00.28_M_release_254948_signed .exe
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
HTC_One_V_Ramdisk:
V_Ramdisk Download
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
PureMotive said:
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
Click to expand...
Click to collapse
I thought of that too. But since the DInc is a 'QSD' (1000Mhz Qualcomm Snapdragon) and the Desire HD and the Desire S are 'MSM' (Mobile Station) We can't use their ports to help us :/
Being that the DInc is a qsd8k (8650 to be exact) we'll need to keep an eye out for ports with the same processor.. Oh man I wish the old Desire could get a port of this, lol. We'd have no problem at all..
Tribulattifather said:
Saw nobody was getting this started.
I am currently working on it a bit but I defenitley need help compiling a kernel.
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTC_Europe_1.56.401.1_Radio_20.66.30.0831U_3831
(For the newbies)
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
Kernel Source:
HTC Sensation XE (HTC Europe) - ICS CRC - 3.0.16 kernel source code
Look at the 9th one in the list
I hope that we can get this working for our DInc's.
Click to expand...
Click to collapse
kernel source wont help you at all for the 3.xx kernel from other htc phones, so dont bother
i ported sense 4 to the inc 2 (admittedly a lot easier cuz its msm7x30 which most of the ports are) and will give it a shot on my og inc time permitting
see inc2 port here: http://forum.xda-developers.com/showthread.php?t=1553357
the hacked .35 kernels from your ics aosp roms *should* be good (only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
When you say
nitsuj17 said:
(only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
Click to expand...
Click to collapse
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Tribulattifather said:
When you say
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Click to expand...
Click to collapse
no, you need the zimage from one of the ics aosp inc roms and the extracted ramdisk from the htc one v
Okay. Thank you for clarifying for me.
I'm getting down to business now ^>^
PonsAsinorem said:
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
Click to expand...
Click to collapse
can u tell the link to wildstang83 porting guide thread?
orochi9999 said:
can u tell the link to wildstang83 porting guide thread?
Click to expand...
Click to collapse
★wildstang83's Guide For Basic Porting★
PonsAsinorem said:
★wildstang83's Guide For Basic Porting★
Click to expand...
Click to collapse
thank u!
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
2012oasis said:
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
Click to expand...
Click to collapse
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Tribulattifather said:
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Click to expand...
Click to collapse
can you get a logcat or pm me a ROM link? I'd like to look. No guarantees of success. Sadly the sense devs that could figure it out I think have left the incredible.
Also a working ramdisk still doesn't mean the kernel is good. The kernel may need some changes.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Tribulattifather said:
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Click to expand...
Click to collapse
I'd like to try tonight if I can. I'm hoping that an HWA enabled AOSP ICS kernel works with it.
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Ahh! Excited..
Sent from my HTC Droid Incredible using Tapatalk 2 Beta-5
Tribulattifather said:
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Click to expand...
Click to collapse
I'm actually stabbing in the dark as much as you. Never messed much with roms. I'm more of a troubleshooter rather than a rom/kernel chef. I find tweaks and adapt for my kernels. But I noticed there's no init.inc.rc in that ramdisk. Other than that my mind's dead so I'll have to look tomorrow/this weekend.
I apologize for the delay in posting the port link. You'll have to forgive my internet. But, I assure you that the download is as fast as I can get it with my own server that I use.
EDIT: Port is on the next page --->
Just to make sure that everyone is on the same page - This port is NOT a working port.
It will flash to the DInc and it will install properly but it does not boot. And it is obvious why, lol, because we are still missing the piece to the puzzle to make a working kernel.
I hope that this will give you what you need to get this project I started the thrust in the right direction.
As for my method thus far, I am using the zImage from and AOSP ICS port with Ramdisk parts from the One_V.
Post Script - Today is my third year anniversary being apart of XDA. And I can only hope many more years to come.
CHEERS ALL!
Hi i would like any information on how i would go about making an aosp kernel for a sense based phone.
the lack of support for this device has got me mad!! :crying:
im good with the linux side of things just need to know what is required to make an aosp kernel from sense source code??,
now obviously the sources are available for our phone but as i understand it its for a sense kernel only
so im going to start on an aosp rom for my phone, any advice or guidance would be appreciated
also would htc primo (v) be a good phome to port an aosp rom from
onejay09 said:
Hi i would like any information on how i would go about making an aosp kernel for a sense based phone.
the lack of support for this device has got me mad!! :crying:
im good with the linux side of things just need to know what is required to make an aosp kernel from sense source code??,
now obviously the sources are available for our phone but as i understand it its for a sense kernel only
so im going to start on an aosp rom for my phone, any advice or guidance would be appreciated
also would htc primo (v) be a good phome to port an aosp rom from
Click to expand...
Click to collapse
Well, i tried to port and some of the hardware works, not all.
This AOSP term to the kernel is pretty much an exageration... Mainly because PrimoU (v) runs a fully working CM9 on the sense kernel with no modifications (almost, i mean no porting or something like that).
This being said, the actually job you need to do is to find the right ramdisk configuration for it.
There are people working on this but with no experience or very little experience. Both me and anders are working on this, but i have my finals now and i will not work that hard for it, and compiling CM9 and testing it is pretty much a time-consuming job.
Well, you can start by making the enviroment ready and download the CM9 sources, hang around the irc channel and download the device tree from my github account.
hey lex just found your git while searching cms repo lol, made me smile seeing that, shame you havnt got the time right now, ill read up some more for now and see what i can do, thanks for the quick reply i appreciate your advice pal!
also would fastboot boot img be a good idea for testing
and how did you go about with the testing, eg used an aosp rom with the kernel tests or just used a logcat?
good luck with your finals btw!!
edit why has koush forked your git is he interested?
onejay09 said:
hey lex just found your git while searching cms repo lol, made me smile seeing that, shame you havnt got the time right now, ill read up some more for now and see what i can do, thanks for the quick reply i appreciate your advice pal!
also would fastboot boot img be a good idea for testing
and how did you go about with the testing, eg used an aosp rom with the kernel tests or just used a logcat?
good luck with your finals btw!!
edit why has koush forked your git is he interested?
Click to expand...
Click to collapse
He forked my git in order to get official CWM Recovery to our device, right now it does not compile for some reason, don't know why as on the same sources mine compiles... But that will be fixed some time in the future...
--
Other than that, flashing from fastboot the boot.img does not seem to me a great ideea as i like to minimise as much as possible the use of fastboot, so, i always use flashable zips for kernels, you can download one of my kernel releases and use the zip as a template, just change the files needed in it and flash at your own pleasure.
--
As for AOSP Rom and kernel, the thing is pretty much simple, at first i tried porting ROM's and things seemed to work to some degree, but not fully functional, so i figured out that the easiest way to do this is the hard way, compiling from source, putting up a device tree and so on, in this way we can keep up with any AOSP-based ROM released or that will be realeased, but as this device didn't recieved too much atention, the device tree needs to be made almost from scratch, well, i used as a template the PrimoU device tree, and made some changes to it to fit our device, but CM9 does not really like the actual tree as all that works is...booting fine, rotation, touch-screen...and that's it, also, the interface is buggy, so not usable at all, but i didn't work on it for some time now, will resume work after the finals.
--
I am also working on a project on porting 3.4.0 kernel for Dell Streak 5, this project will also benefit the future development of the custom kernel for our device, so things are still rolling around here, but at a slower pace as i'm rather new in this field.
Lexmazter said:
He forked my git in order to get official CWM Recovery to our device, right now it does not compile for some reason, don't know why as on the same sources mine compiles... But that will be fixed some time in the future...
--
Other than that, flashing from fastboot the boot.img does not seem to me a great ideea as i like to minimise as much as possible the use of fastboot, so, i always use flashable zips for kernels, you can download one of my kernel releases and use the zip as a template, just change the files needed in it and flash at your own pleasure.
--
As for AOSP Rom and kernel, the thing is pretty much simple, at first i tried porting ROM's and things seemed to work to some degree, but not fully functional, so i figured out that the easiest way to do this is the hard way, compiling from source, putting up a device tree and so on, in this way we can keep up with any AOSP-based ROM released or that will be realeased, but as this device didn't recieved too much atention, the device tree needs to be made almost from scratch, well, i used as a template the PrimoU device tree, and made some changes to it to fit our device, but CM9 does not really like the actual tree as all that works is...booting fine, rotation, touch-screen...and that's it, also, the interface is buggy, so not usable at all, but i didn't work on it for some time now, will resume work after the finals.
--
I am also working on a project on porting 3.4.0 kernel for Dell Streak 5, this project will also benefit the future development of the custom kernel for our device, so things are still rolling around here, but at a slower pace as i'm rather new in this field.
Click to expand...
Click to collapse
So then it is not only me that can't get the device tree to compile. Strange. ...
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
anders3408 said:
So then it is not only me that can't get the device tree to compile. Strange. ...
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
You are using the ICS branch, that compiled fine, on Cyanogenmod repo is the Jellybean branch.
Lexmazter said:
You are using the ICS branch, that compiled fine, on Cyanogenmod repo is the Jellybean branch.
Click to expand...
Click to collapse
It first compiled fine after changing some stuff. Still struggling with audio
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
ok im going to do fresh setup today and get it compiled so i can test and have a look, is vold fstab ok for 1.28 s-off hboot? :fingers-crossed:
have you found any similar devices (board wise) we could take a look at? may give some insight to it..
also whats the current state of working not working, eg what works atall?
onejay09 said:
ok im going to do fresh setup today and get it compiled so i can test and have a look, is vold fstab ok for 1.28 s-off hboot? :fingers-crossed:
have you found any similar devices (board wise) we could take a look at? may give some insight to it..
Click to expand...
Click to collapse
There is 3. Desire HD , one v also called primou and incredible s also called vivo. They all uses same screen resolution , same CPU and GPU so that is the closes you get. I will soon be found at the Irc chat then we can have a look together. Just join #runny-dev at freenode, also to be found in my signature.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
onejay09 said:
ok im going to do fresh setup today and get it compiled so i can test and have a look, is vold fstab ok for 1.28 s-off hboot? :fingers-crossed:
have you found any similar devices (board wise) we could take a look at? may give some insight to it..
also whats the current state of working not working, eg what works atall?
Click to expand...
Click to collapse
Also, the current branch tree supports all hboots, you will surely still need the right vold.fstab file, but other than that, yes, is ok, i also use that hboot.
Hey what do i do about vendor srtup.sh and wheres the make directory for lex repo, had a little trouble with the build enviroment,
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Sv: How Is an aosp kernel made for sense devices ?
onejay09 said:
Hey what do i do about vendor srtup.sh and wheres the make directory for lex repo, had a little trouble with the build enviroment,
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Click to expand...
Click to collapse
It is not included in his repo, if you find my repo : WWW.github.com/anders3408
The vendor files he used is there.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
ok, figured it out thanks, whats your directory layout,
iv got
home/android_source/projects/device/htc/ now should i keep the name runnymede? (device)
home/android_source/projects/vendor/htc/ ????
ok so i extract files.sh first also then . build envsetup.sh && lunch?
also ive added the project to an xml file is that right ?
Sv: How Is an aosp kernel made for sense devices ?
onejay09 said:
ok, figured it out thanks, whats your directory layout,
iv got
home/android_source/projects/device/htc/ now should i keep the name runnymede? (device)
home/android_source/projects/vendor/htc/ ????
ok so i extract files.sh first also then . build envsetup.sh && lunch?
also ive added the project to an xml file is that right ?
Click to expand...
Click to collapse
Root of sourcefiles/vendor/htc/runnymede
And device tree in root /device/htc/Runnymede
And also the common files in HTC folder.
Then fix things envsetup.sh and lunch and buildwhatyouwant.
Then find out oh it is not working, make clobber
Then fix things and all over. No need to extract, only used when you have no vendor files.
Good idear is compare to others github
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Ok everything is setup, exept when i run . build/envsetup.sh it says no such file or directory? Am i typing in wrong folder? Or Am i missing some compile tool?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Sv: How Is an aosp kernel made for sense devices ?
onejay09 said:
Ok everything is setup, exept when i run . build/envsetup.sh it says no such file or directory? Am i typing in wrong folder? Or Am i missing some compile tool?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Click to expand...
Click to collapse
I will be on irc chat after a cigaret then i will help you
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
You will need to be in the root of android sources then write it, and it should work...
Thanks think iv figured it out, iv not got android/system i pulled cyanogenmod/android.git -b ics it took 2hours/ terminal never prompted after the git pull though, what am i missing?
I must have wrong or incomplete source because i have no build directory in the repo i pulled, im at work right now so no internet connection, maybe tomorrow
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Turns out git gc had a thread issue with python, so i finally got it pulled with sync repo -j1, compiling runnymede now, is it booting with current board config etc?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Finally got a full build of cm 9, had to set
Board_uses_qcom_audio_resetall :=false in boardconfig common.mk in msm7x30 just to get it to compile
Ive added for now a stub
Board uses generic audio = true
so no audio in this build yet
Any advice?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
onejay09 said:
Finally got a full build of cm 9, had to set
Board_uses_qcom_audio_resetall :=false in boardconfig common.mk in msm7x30 just to get it to compile
Ive added for now a stub
Board uses generic audio = true
so no audio in this build yet
Any advice?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Click to expand...
Click to collapse
Well, i got it fully built and booted with my current device repo, and anders reported he managed to get it compile only by using cyanogenmod's 7x30 common repo, i can't remember what common i used, but since he reported that, then most probably i used that too.
The kernel that will result in the flashable zip is unusable because of the ramdisk, i have a good ramdisk that get it booted so i need to update the repo when i have time with the right ramdisk so the resulting flashable .zip will work, probably.
Also, i did some changes in the flashable .zip to get some things working, so everything is pretty much WIP and i need to get past the finals to resume my work on this, so be patient and try to join IRC channels where other developers are hanging, so you can ask more experienced developers.
I'm pretty much a newbie in this field, as i didn't compile from source a fully working ROM so far.
I got working Recoveries on 2 devices for now, fully working ones so, this is pretty much what i can do, incorporate things in kernels and port recoveries from scratch.
Hi, as you know lexmazter and anders are working on the cm9 project, iv offered my help with the project, as i see it this device has poor support, so im giving in and lending a hand anybody who is willing to help, preferably with some dev skills is welcome, im personally quite new to this so please have some patience, this might take more time than we all hope!
Update:
ive been struggling with the boot.img thats compiled with the build
device is booting to cyanogen bootloader screen, finally made a working device tree from htc saga.
will be logcatting for a while : )
update 2:
phone finally boots to ui!
more fixing todo yet
issue with cache dalvik cache is causing a lot of the problems
will be fixed tonight
Reserved
Please be patient with me, as iv got a family and work at night so my time is a little limited as is lex and anders
Finally got a full build of cm 9, had to set
Board_uses_qcom_audio_resetall :=false in boardconfig common.mk in msm7x30 just to get it to compile
Ive added for now a stub
Board uses generic audio = true
so no audio in this build yet
Any advice?
We could do with tester, wouldnt trust the kernel so id advise fastboot run the zimage maybe?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
onejay09 said:
Finally got a full build of cm 9, had to set
Board_uses_qcom_audio_resetall :=false in boardconfig common.mk in msm7x30 just to get it to compile
Ive added for now a stub
Board uses generic audio = true
so no audio in this build yet
Any advice?
We could do with tester, wouldnt trust the kernel so id advise fastboot run the zimage maybe?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Click to expand...
Click to collapse
Sweet Jesus! Someone help this man, I had almost given up hope for this device. Props to you brother for giving it a go.
Trust me im trying to im gonna release an huge update on the AIO tool in the weekend. To night i am going to work on cm9 again i will be on the irc chat then
Ok sounds good, it looks like well have to rewrite some files to get it working, do you have an idea why it fails on line 576 msm resetall? ill be on runny-dev tonight, some people had sucsess changing gcc and g++ to older vers, so i tried gcc4.4, didnt help, others also had sucsess with different msm-7x30-common files.
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Sv: REQUEST/DEV HELP-CM9. Lexmazters anders3408 CM9 project
onejay09 said:
Ok sounds good, it looks like well have to rewrite some files to get it working, do you have an idea why it fails on line 576 msm resetall? ill be on runny-dev tonight, some people had sucsess changing gcc and g++ to older vers, so i tried gcc4.4, didnt help, others also had sucsess with different msm-7x30-common files.
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Click to expand...
Click to collapse
Imod going to compile again and see the error myself . dont use my repo, going to make a new one instead
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
onejay09 said:
Ok sounds good, it looks like well have to rewrite some files to get it working, do you have an idea why it fails on line 576 msm resetall? ill be on runny-dev tonight, some people had sucsess changing gcc and g++ to older vers, so i tried gcc4.4, didnt help, others also had sucsess with different msm-7x30-common files.
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Click to expand...
Click to collapse
The thing is that we could use the already built htc-acoustic.so lib, everything that we use prebuilt will go into the vendor tree.
That being said, considering that we build CM9 over already ICS for our device, we just need to find the right libs we need and the wrong ones to be compiled or kanged from primou.
Other than that, wait to get past my exams and i'll be back in business
audio
so do we declare that in runnymede-vendor-blobs.mk,? i was under the impression that the libaudioalsa.so would be slighty different to cm, would it work, so pull it to out/target ?
edit
just found this in vendor blobs
PRODUCT_COPY_FILES += \
vendor/htc/runnymede/proprietary/lib/libaudioalsa.sobj/lib/libaudioalsa.so
# Audio Blobs
PRODUCT_COPY_FILES += \
vendor/htc/runnymede/proprietary/lib/libaudioalsa.so:/system/lib/libaudioalsa.so \
first off i cant find reference to libaudioalsa.so vendor-blobs.mk in any other cm based tree
second i cant understand why it would be called twice to different locations?
onejay09 said:
so do we declare that in runnymede-vendor-blobs.mk,? i was under the impression that the libaudioalsa.so would be slighty different to cm, would it work, so pull it to out/target ?
edit
just found this in vendor blobs
PRODUCT_COPY_FILES += \
vendor/htc/runnymede/proprietary/lib/libaudioalsa.sobj/lib/libaudioalsa.so
# Audio Blobs
PRODUCT_COPY_FILES += \
vendor/htc/runnymede/proprietary/lib/libaudioalsa.so:/system/lib/libaudioalsa.so \
first off i cant find reference to libaudioalsa.so vendor-blobs.mk in any other cm based tree
second i cant understand why it would be called twice to different locations?
Click to expand...
Click to collapse
First of all, the vendor blobs are files already built and i just edited the runnymede-vendor-blobs.mk to suit our device, that file could also be compiled, and, you can try to comment the first file and see what happens.
As far as i know the 2 are there because, the first is copied ad compilation and the second is copied in the respective folder for the flashable zip.
Also, i'm on irc, you can find me there for more details.
im compiling now with some changes see if it gets past the error
ok fixed the audio error, still need a working ramdsik, wheres lexmazter lol??
Just sharing some usefull links here :
Cyanogenmod porting intro
Envsetup help
Dealing with build errors
Building basic
integrated kernel building
Now the status is that we can compile a cm9 without compiler stopping, but no boot or anything. So i am just sharing some usefull infos to read and to understand what is happining when compiling
CM9 boot.img and modules + RomManager.apk file
^^ONLY TO USE IN CM9 ROMS NOTHING ELSE^^
oh and the boot.img should work, it boots my cm9 port just fine with wifi and so on and it also reads the camera driver , just stops at audio but that is rom related.
Come on, lets get this thing up and going
---------- Post added at 03:48 PM ---------- Previous post was at 03:24 PM ----------
also, i think to make it more easy for us all, we need to put vendor , device tree and common files to github so we can compare if something works for one of us
First you will need to edit .repo inside the vendor folder and device tree folder and common folder, or else it is trying to push it to where you have pulled it from then after that use the link
pushing to github
---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
Just remeber to name the repo correct : like this for device tree:
android_device_htc_runnymede
Sv: REQUEST/DEV HELP-CM9. Lexmazters anders3408 CM9 project
I know it is off topic , but how cool is that, I had buy a cheap HTC sensation , found out it had an hardware error, even after unlocked and soff , flashed stock ruu and send it in for repair to see if warranty took it. And now today me brand new HTC sensation arrived thank you htc
Note: the phone was 20 month old
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Update:
ive been struggling with the boot.img thats compiled with the build
device is booting to cyanogen bootloader screen, finally made a working device tree from htc saga.
will be logcatting for a while : )
Sv: REQUEST/DEV HELP-CM9. Lexmazters anders3408 CM9 project
onejay09 said:
Update:
ive been struggling with the boot.img thats compiled with the build
device is booting to cyanogen bootloader screen, finally made a working device tree from htc saga.
will be logcatting for a while : )
Click to expand...
Click to collapse
Can you push it to your git hub then I will try and help again
Sent from my HTC Sensation using xda premium
AW: REQUEST/DEV HELP-CM9. Lexmazters anders3408 CM9 project
Hey there I cant Post in dev section so i will do it here. I installed your cm9 port anders. Runs pretty good. Found 2 more bugs you did not mention in op post. Flashlight app force closes and GPS does not work at all. Keep up the good work and sry if this is in the wrong thread.
Helly
Sent from my Sensation XL with Beats Audio X315e using xda app-developers app
Sv: REQUEST/DEV HELP-CM9. Lexmazters anders3408 CM9 project
xcsvxangelx said:
Hey there I cant Post in dev section so i will do it here. I installed your cm9 port anders. Runs pretty good. Found 2 more bugs you did not mention in op post. Flashlight app force closes and GPS does not work at all. Keep up the good work and sry if this is in the wrong thread.
Helly
Sent from my Sensation XL with Beats Audio X315e using xda app-developers app
Click to expand...
Click to collapse
I will add that. It usres camera interface to use flashlight do that is the reason for it to fc. But thanks
Sent from my HTC Sensation using xda premium
AW: REQUEST/DEV HELP-CM9. Lexmazters anders3408 CM9 project
Nice to hear other things seem to be pretty stable
Sent from my Sensation XL with Beats Audio X315e using xda app-developers app
Hi There we have found complete sources of our phone Micromax A110 MTK 6577
We were hoping if any one Awsum Dev could compile an omni rom for our Beloved Phone here is the link to the sources http://pan.baidu.com/s/1ACPRk#dir/path=%2F8377%E8%BD%AF%E4%BB%B6%E5%8C%85
If u want u can contact our devs u can contact @[email protected] and @khan_frd2002 and also our kernel dev @varun.chitre15
And for compiling there is this guide http://wenku.baidu.com/link?url=GlZC...3XdjfuZXcip5zm
I hope i will receive Positive results and replies
Thnx
Andromodgod:cyclops:
if possible please upload to a better file hosting site. this is so slow it's causing the download to fail
cybojenix said:
if possible please upload to a better file hosting site. this is so slow it's causing the download to fail
Click to expand...
Click to collapse
Thnx for the reply 2 Questions
Are you from the omni team I.E help us in making rom
How long would the compilation take
U can contact all of us we are at http://forum.xda-developers.com/micromax-a110/development
Or Here
http://forum.xda-developers.com/micromax-a110/
Link will be provided as soon as possible :angel:
I'm a contributor there. I'm just curious as to what parts they change. seeing as mtk devices are dirt cheap here, I might consider getting some to work on if their sources aren't desperately bad
edit:
compilation doesn't take long. getting to the stage of getting a working compilation may take a while though
ps can the file labelled "alps patch" be uploaded first please. thanks
Thnx
@cybojenix Thnx for ur interest in our Phone one developer @[email protected] is already working on cm 10.2
And Varun Chitre is also a great dev u can ask anyone and all of them will help u
About the mirror i dont think it is possible cuz most of the people(Dev) Live in india or other places where the Internet connection is slow u can use an extension for firefox i will link it to you https://addons.mozilla.org/en-US/firefox/addon/downthemall/
ANd please try not to post cuz if u see ur post it say """"555 Posts"""" Lucky number
U can PM Me Thnx
I will ask devs to mirror it
yes buddy mirroring is needed....the downloading speed is so less that my downld has failed more than 4 tiimes..
Alps Patch file
Here is the link to patch file @cybojenix http://d-h.st/BAg
Leeching that to take a look.
Since none of us have a 6577 device, someone else will have to do the bringup work, but it would be interesting to see how much commonality there is between 6577 and 6589.
Unfortunately the problem is MTK's sources are a disorganized mess, and in many cases, their HALs are just wrappers around a blob. The source we have for R819 is for 4.2 - while xplodwild got 4.3 partially booting on R819, so far, the display drivers just crash on boot on 4.4.
Entropy512 said:
Leeching that to take a look.
Since none of us have a 6577 device, someone else will have to do the bringup work, but it would be interesting to see how much commonality there is between 6577 and 6589.
Unfortunately the problem is MTK's sources are a disorganized mess, and in many cases, their HALs are just wrappers around a blob. The source we have for R819 is for 4.2 - while xplodwild got 4.3 partially booting on R819, so far, the display drivers just crash on boot on 4.4.
Click to expand...
Click to collapse
From what I've looked at so far in the uploaded patch file, it doesn't seem to be too good. I was expecting to see diff patches.. from what is included in it, it seems to be partial, and out of the camera, there are only headers.
Waiting for the full source to be uploadec
Sent from my Nexus 7 using Tapatalk
cybojenix said:
From what I've looked at so far in the uploaded patch file, it doesn't seem to be too good. I was expecting to see diff patches.. from what is included in it, it seems to be partial, and out of the camera, there are only headers.
Waiting for the full source to be uploadec
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Source are uploaded here you go http://forum.xda-developers.com/showthread.php?p=48303269
Sent from my Nexus 4 using XDA Premium 4 mobile app
[SOURCE]Full MTK6577 AOSP tree + proprietary source: http://forum.xda-developers.com/showthread.php?t=2172440
*edit: These are sources for ICS. Reason: http://forum.xda-developers.com/showpost.php?p=48307124&postcount=134
Progress
Any report on the progress @cybojenix
andromodgod said:
Any report on the progress @cybojenix
Click to expand...
Click to collapse
Sources seem somewhat unhelpful at a first glance, however going deeper into them may reveal key parts that have Been overlooked
Sent from my Nexus 7 using Tapatalk
Any Good News
DO we have any good news from u @cybojenix
We are eagerly waiting for u
andromodgod said:
DO we have any good news from u @cybojenix
We are eagerly waiting for u
Click to expand...
Click to collapse
Please, check this comments:
http://forum.xda-developers.com/showpost.php?p=48628112&postcount=43
http://forum.xda-developers.com/showpost.php?p=48642380&postcount=44
mtk你还是放弃吧，很多都没有开源的，mtk提供整套方案给生产商，连生产商都没有源代码的。
Sent from my One X using xda app-developers app
I thought it is complete
Sent from my Nexus 4 using Tapatalk
Any news?
Related:
MediaTek driver sourcecode (want custom ROMs? read this!): http://forum.xda-developers.com/showthread.php?p=50146816
No complete source, nothing to accomplish.