Database Develop

[DEV][ICS+SENSE][Mar.20.2012]HTC One V development[Source+RUU]

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!

Slide 2 Wake

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

[DEV][HowTo]Resolve CM9 Bugs

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.

How Is an aosp kernel made for sense devices ?

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.

[Kernel][4.4.3] Falter v2.0

[Kernel][4.4.3] Falter v2.0
Stock kernel for Android 4.4.3
Feel free to use it for ported from HTC One Android 4.4.3 ROMs
Falter-v2.0 Kernel for Android 4.4.3
Source: GitHub
Compiler: Linaro GCC 4.8.4
Kernel Version: 3.4.10
defconfig: dlxp_ul_defconfig
Download Falter release from GitHub
XDA:DevDB Information
Falter for Android 4.4.3, Kernel for the HTC Butterfly S
Contributors
Matri}{
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2014-09-10
Created 2014-09-10
Last Updated 2014-09-12

I hope Butt S 4.4.3 ROM soon to be release!!!

No 4.4.3. Thanks any way.

farz2farz said:
No 4.4.3. Thanks any way.
Click to expand...
Click to collapse
There was no 4.4.3 rom because of kernel. I'm already using InsertCoin 4.0.3 (ported from htc one), privately ported.

Matri}{ said:
There was no 4.4.3 rom because of kernel. I'm already using InsertCoin 4.0.3 (ported from htc one), privately ported.
Click to expand...
Click to collapse
Will be doing 4.4.3 tonight. Been real busy with my life and haven't updated any of my roms in a while

@Matri}{
Please contact me Via PM for you taking over IC. As i need you gmail for hangouts and so our team can contact you and for publishing DLXPUL post on our website. Cant do blind developing anymore and need you to keep giving this forum updates.

Thanks. Your kernel is awesome. D2w is working great. But is there any way to enable only D2w and disable sweep2 wake. Pls it's a must thing I want.
Sent from my HTC Butterfly s using xda app-developers app

Sorry but i don't understand. Where can I found a ROM to install this kernel?

Any tutorials for port the Rom from HTC one?

dioooi said:
Any tutorials for port the Rom from HTC one?
Click to expand...
Click to collapse
Waiting on matri}{ response on taking over IC.

Users InsertCoin 4.4.3 is up and ready to be flashed by this kernel. So I hope @Matri}{ continues development.. I would also say I'd love to bring you 4.4.4 sense 6 but that's even more of a hassle then 4.4.3 was. But is very possible with this kernel.

xXminiWHOOPERxX said:
Users InsertCoin 4.4.3 is up and ready to be flashed by this kernel. So I hope @Matri}{ continues development.. I would also say I'd love to bring you 4.4.4 sense 6 but that's even more of a hassle then 4.4.3 was. But is very possible with this kernel.
Click to expand...
Click to collapse
Sorry guys, I'm here from time to time and looking for new features for our kernel.
Here is a brief guide to port any Sense-based rom from HTC One:
You need original ROM for Butt S (1) and ROM you want to port (2). You can use MaximusHD 13 as (1).
1. In (2) Replace boot.img with Falter's boot.img
2. In Aroma scripts change "block" numbers. I intentionally do not specify them here. Go figure out or wait until someone will port ROMs
3. Copy and replace from (1) to (2)
/system/etc/bluetooth/bt_stack.conf
/system/etc/bluetooth/bt_vendor.conf
/system/etc/permissions/*
/system/lib/modules/libimu.so
/system/lib/modules/hw/nfc.dlxpul.so
/system/lib/modules/hw/sensors.msm8960.so
/system/usr/keylayout/synaptics-rmi-touchscreen.kl
4. Edit /system/build.prop
change ro.storage_structure = 8 to ro.storage_structure = 10
5. Open /system/framework/framework-res.apk in (2) and replace /res/xml/storage_list.xml with one from (1)
Any other changes in build.prop and other files are optional.

Matri}{ said:
Sorry guys, I'm here from time to time and looking for new features for our kernel.
Here is a brief guide to port any Sense-based rom from HTC One:
You need original ROM for Butt S (1) and ROM you want to port (2). You can use MaximusHD 13 as (1).
1. In (2) Replace boot.img with Falter's boot.img
2. In Aroma scripts change "block" numbers. I intentionally do not specify them here. Go figure out or wait until someone will port ROMs
3. Copy and replace from (1) to (2)
/system/etc/bluetooth/bt_stack.conf
/system/etc/bluetooth/bt_vendor.conf
/system/etc/permissions/*
/system/lib/modules/libimu.so
/system/lib/modules/hw/nfc.dlxpul.so
/system/lib/modules/hw/sensors.msm8960.so
/system/usr/keylayout/synaptics-rmi-touchscreen.kl
4. Edit /system/build.prop
change ro.storage_structure = 8 to ro.storage_structure = 10
5. Open /system/framework/framework-res.apk in (2) and replace /res/xml/storage_list.xml with one from (1)
Any other changes in build.prop and other files are optional.
Click to expand...
Click to collapse
Already beat you to the punch I'm working on v4.0.7 for these guys already.... Trying my hardest to be active here.. but oh boy I need coffee. Any helpers

Matri}{ said:
Sorry guys, I'm here from time to time and looking for new features for our kernel.
[...]
2. In Aroma scripts change "block" numbers. I intentionally do not specify
[...]
Click to expand...
Click to collapse
Sorry I'm newbie about it, you meant to change the blocks numbers in "updater-script" to boot=36, system=38 and cache=39?
Thanks a lot!
Slán!

foggydew88 said:
Sorry I'm newbie about it, you meant to change the blocks numbers in "updater-script" to boot=36, system=38 and cache=39?
Thanks a lot!
Slán!
Click to expand...
Click to collapse
Not only updater-script, but all Aroma scripts and init.d scripts.
cat /proc/emmc