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
Related
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!
There is a mod for the EVO 4G called Slide 2 Wake, it seems pretty awesome. I was wondering can we have kernel with Slide 2 Wake support on SXL?
http://forum.xda-developers.com/showthread.php?t=1346760
I found another one sweep2wake http://forum.xda-developers.com/showthread.php?t=1256668
Its on one x as well in bricked kernel. Its a battery hog but nice feature
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Sweep to wake works on my ordinary Sensation. It's controlled from the Tweaks app but not sure if the kernels are similar in the two phones. Probably not lol.
it will be cool if somebody implement this
shingers5 said:
Its on one x as well in bricked kernel
Click to expand...
Click to collapse
i sow it on different devices, not only One X
cool feature...anyone can write and ask in the original thread what function must be activated...maybe there is a github kernel patch (would be the easiest way)
with kind regards
Nice.. Hoping to see it on my SXL ...
Any Dev Can have a breif look in this...
as i understand it is in sweep2wake.sh script inside of kernel
-=AsteriX=- said:
as i understand it is in sweep2wake.sh script inside of kernel
Click to expand...
Click to collapse
it should be no problem to edit this file and post a kernel... but we must know what to edit....
delete this and paste that...etc....
also is it all...or must be also a edit of framework...or so..
with kind regards
I think that's all
this is a patch i found on github...
https://github.com/showp1984/bricke...mmit/284f0a5cdb45eef6539c3c1a3641256794804035
and the rest all with sweep2wake
https://github.com/showp1984/bricked-shooteru-ics-sense/commits/master
these are kernel commits/patches...can be a bit different from some points because they are made for a different phone...but with some time it can be patched i think
thx to showp1984
with kind regards...Alex
so who can cook kernel with this patch?
Surely its not that easy to enable slide2wake.... I will have a go later and see if it compiles...
[vertigo] said:
I will have a go later and see if it compiles...
Click to expand...
Click to collapse
i`ll be waiting for it
Well it compiled ok but the slide2wake hasn't worked so I'm going to have a closer look...
I am very grateful to you for you are doing this
[vertigo] said:
Well it compiled ok but the slide2wake hasn't worked so I'm going to have a closer look...
Click to expand...
Click to collapse
you only use the main patch..or all other..? i´m unsure if the patches are all..or if framework must be patched also or a build.prob thing...etc...but nice you working on this...
with kind regards
I patched all to start off with, but I did notice that the touchscreen driver in the kernel is different to the SXL, so I tried patching the driver for the SXL and it wouldn't compile....
[vertigo] said:
I patched all to start off with, but I did notice that the touchscreen driver in the kernel is different to the SXL, so I tried patching the driver for the SXL and it wouldn't compile....
Click to expand...
Click to collapse
thank for dont giving up
It's important for everyone to know that since this is a development thread, most, if not all conversation should be dedicated to helping us boot the ROM. All questions related to and including "will our device be able to handle Jellybean?" should be moved to the following thread: http://forum.xda-developers.com/showthread.php?t=1736089
Our biggest problem so far: There are incompatibilities with Jellybean and the Adreno drivers, which our phone needs to function. We can't just remove the Adreno drivers and boot the ROM (I tested this, by removing them from our latest CM9 nightly, which wouldn't boot as a result. I also removed the Adreno drivers and used the Jellybean ramdisk, framework, libs, and bin files but still no boot.).
PureMotive's port
I booted my source-built Jellybean.
Status: ALPHA
Working
Root
ADB
3G
WiFi
Calls (outgoing and incoming)
Signal
UI
Soft keys + lights
RIL
GPS
Brightness settings
Sync
SMS
MMS
Gmail
Gtalk
Twitter
Facebook
Audio
Downloads
Native screenshot (should work now)
Google Now
Untested
Video
Bluetooth
Camera
Broken
Butter
Browser (default)
HWA
Click to expand...
Click to collapse
Albinoman's port
Check his thread located here
Click to expand...
Click to collapse
PORTING FILES:
Code:
Jellybean SDK: [URL]http://d-h.st/EUH[/URL]
Jellybean Ramdisk: [URL]http://d-h.st/XhF[/URL]
Boot.img used in Tiny's port: [URL]http://d-h.st/a0C[/URL]
Vicious Jellybean (VZW GNex port): [URL="http://rootzwiki.com/topic/28486-rom-vicious-toro-jellybean-v3-100-functional-franco-kernel-beats-audio-mods-optimized-link-in-op-for-stock-kernel-added-112am-06302012/"]Vicious Jellybean[/URL]
On vacation. When I get back next week I'll check it out
Sent from my unrootable DROID2
where the hell is the ramdisk
Just wanted to mention my scan of the ramdisk the other night didn't lead to anything conclusive. I checked real quick yesterday I think but didn't really have time to look in depth. I didn't see a problem with the way the system mounted so something else is causing it. I'm trying to port it right now. We'll see what happens.
Maybe I should give it a try.
How about paste bin a logcat?
Here is my current logcat
http://paste.ubuntu.com/1074131/
Sent from my Droid Incredible using xda premium
Shano56 said:
where the hell is the ramdisk
Click to expand...
Click to collapse
Posted in the OP.
PonsAsinorem said:
How about paste bin a logcat?
Click to expand...
Click to collapse
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.
PureMotive said:
Posted in the OP.
Click to expand...
Click to collapse
hehe now u post it. ty
edit: i thought you needed it extracted
PureMotive said:
Posted in the OP.
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.
Click to expand...
Click to collapse
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx
Upload!!!! Lol
Sent from my Droid Incredible using xda premium
tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
zip file coming next.
Click to expand...
Click to collapse
Did you use the ramdisk from the OP or the boot.img I sent you? I got it to the point where it would load the framework .jar files, but haven't encountered what you did in your logcat so I'd consider it progress lol. Seems to be an issue with EGL...
EDIT: Nevermind lol
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
Sounds to me like you are missing /bin/mksh either in ROM or in symlink in updater
Sent from my PG06100 using xda premium
Just wanted to first of all say thanks for this - it's awesome that this is even being worked on. We have such an awesome dev community. Secondly, just wanted to offer my support in any way possible. I don't have a lot of experience with porting Android, but I do have pretty good Linux system knowledge and a willingness to experiment. Downloading tiny's build now, going to mess around with some system files and see what happens. Thanks again guys!
Cm is going to working on cm10.
http://briefmobile.com/cyanogenmod-cm10-coming-with-jelly-bean-source-code-release
Sent from my ADR6300 using xda app-developers app
tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx
Click to expand...
Click to collapse
Hey tiny4579 could you post what you changed/added in your build?
Albinoman said:
Hey tiny4579 could you post what you changed/added in your build?
Click to expand...
Click to collapse
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2
I see progress! I will download your port right now and see what I can help you with.
tiny4579 said:
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium
Albinoman said:
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium
Click to expand...
Click to collapse
I was testing with 2.2.0a1.
Sent from my Galaxy Nexus using Tapatalk 2
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.
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.