21 replies to this topic

[XMasterNinni]

Hi guys.

Here's a beta port of KonstaT's SwedishSnow.
All credits go to KonstaT.

Advanced users only!


IMPORTANT:

• This Build is extremely BETA!
  
• Use at your own risk!
  
• Only for the SF2!!
  
• May not boot!

I just did the basic porting, you have to fix the ROM yourself!
If you're familiar with adb logcat/ddms it won't be that hard.

I'm not responsible for any damage this ROM makes!


Download

[raverrr]

Nice one i take it this just got put though your tool? while I'm at it do you have a list of what your tool moves/copies so i run in to less dead ends while testing.
thanks again. this rom is awsome on the blade

[Dazzozo]

For a start, this suffers from the same issue as the ROM iharrybao ported, dhd.ko is missing. Only the Blade Wi-Fi module and firmware is present and there is no sign of the Crescent's at all.

Edit: in response to raverrr, the porting tool seems to have a preset list of files in each directory, some of which we could do without as they're the same for all devices, and some extra that could be needed (dhd.ko for Crescent) though mostly it's a very good start and does a ton of the work for you.

The things to test really are the hardware functions (Bluetooth, RIL, Wi-Fi, etc.)

Edited by Dazzozo, 03 June 2012 - 06:09 PM.

[XMasterNinni]

I would be glad if you could tell me what files have to be changed, so I can add them to my script!

I just used the standard setup from Blade...

[Dazzozo]

bins seem fine, though in the future (if I fix Bluetooth being dependent on Wi-Fi) you might need to add btld to that list (it's not in CM7 yet), and that might also require BrcmBluetoothServices.apk (not entirely sure on this, just noting it before I forget).

BCM4330B1_002.001.032.0518.0520.hcd seems missing from etc and the same can be said for the aforementioned dhd.ko (we don't have source for a kernel build) at lib/modules for Wi-Fi. As far as I can tell, the firmware files for the Wi-Fi are missing too. The Blade seems to have the /system/wifi convention (this is present in the Swedish Snow port above and contains the Blade Wi-Fi firmware) while I believe our dhd.ko expects them in /system/etc/ (fw_4330b1.bin, etc.)

Most of what isn't necessary to be ported (the ones in the ROM can be kept) should be the EGL libs, libril and liboemcamera (these are identical for the Crescent and Skate at least, I don't know enough about the Blade to comment there, though)

This would need much more extensive testing and is just what I can tell from a first glance.

[XMasterNinni]

Thanks bro!

Will have a look into it.

[Dazzozo]

Additionally, you might want to transfer /usr/keylayout and /usr/idc straight across from the base ROM. I just had some issues with having the infamous cursor to drag around instead of using the touchscreen properly because of missing idcs.

[XMasterNinni]

I just pulled /usr/keychars/*device*_keypad.kcm and /usr/keylayout/*device*_keypad.kl...
There is actually no usr/idc on Blade (and I think on Skate) ROMs.

Is the whole /keychars and /keylayout needed or only the keypad stuff?

The most common *need to fix* things on my ports for Blade are RIL, HW Rendering/Handling/, BT and WIFI.

RIL is tricky. You said libril isn't necessary to port?
DDMS didn't tell me much, but I think it's a bit about smali replacing in framework.jar, could that be?

Edited by XMasterNinni, 05 June 2012 - 04:03 PM.

[Dazzozo]

XMasterNinni, on 05 June 2012 - 03:59 PM, said:

I just pulled /usr/keychars/*device*_keypad.kcm and /usr/keylayout/*device*_keypad.kl...

Not enough. We have atmel-touchscreen.idc, synaptics-rmi-touchscreen.idc and synaptics-rmi4-ts.idc as one of the phones has capacitive buttons attached to the screen (and various touchscreen models), and keylayouts to go with these, though I believe this is 4.0 specific... Let the headache begin!

XMasterNinni, on 05 June 2012 - 03:59 PM, said:

There is actually no usr/idc on Blade (and I think on Skate) ROMs.

Is the whole /keychars and /keylayout needed or only the keypad stuff?

What's to lose in copying it all? A ROM isn't going to have anything useful here, it's for device support and device support only.

XMasterNinni, on 05 June 2012 - 03:59 PM, said:

The most common *need to fix* things on my ports for Blade are RIL, HW Rendering/Handling/, BT and WIFI.

RIL is tricky. You said libril isn't necessary to port?
DDMS didn't tell me much, but I think it's a bit about smali replacing in framework.jar, could that be?

RIL files from the Skate work on the Crescent, so I'm assuming from this that they're all compatible. It would need testing on the Blade.

What do you need to change in smali? I ported something and RIL works.

Edited by Dazzozo, 05 June 2012 - 07:32 PM.

[XMasterNinni]

On 2.3.7 ROMs, RIL (and nearly everything) works like a charm but not on 2.3.5 ones...

I get a hell more errors on those...

[Dazzozo]

If you want the names for the Wi-Fi files:

/lib/modules/dhd.ko -or- /lib/dhd.ko (differs based on ROM which is a pain)
/etc/fw_4330b1.bin
/etc/fw_4330b2.bin
/etc/fw_4330_b1_apsta.bin
/etc/fw_4330_b2_apsta.bin
/etc/nv_4330b1.txt
/etc/nv_4330b2.txt

...and for Bluetooth:

/etc/BCM4330B1_002.001.032.0518.0520.hcd
/bin/BCM4330B1_0243.0000_ZTE_P736V.hcd

[XMasterNinni]

Thanks...

Are these files implented in all ROMs or only in 2.3.5 ones?

[Dazzozo]

XMasterNinni, on 07 June 2012 - 05:14 PM, said:

Thanks...

Are these files implented in all ROMs or only in 2.3.5 ones?

They're in all and necessary for the function of Wi-Fi and Bluetooth. dhd.ko is in either one of the locations, though I think you can assume it's in /lib/dhd.ko if and only if it's 2.3.5 (stock).

Interestingly, if it is 2.3.5 stock, /lib/modules/ can actually contain some other KO files, such as tun.ko (which is present in FnC), so I'm not sure how you want to handle these (you could ignore them, they're not completely necessary and some ROMs do ignore them (FLB2), but do provide additional functions).

[Dazzozo]

I think your best bet would be to copy the modules directory and then /lib/dhd.ko if present.

[XMasterNinni]

Yeah, would be the best. Will change some things today

PS: Do you know what a  _FORTIFY_SOURCE error during compilation is? A PM would be nice!

[Dazzozo]

XMasterNinni, on 08 June 2012 - 08:33 AM, said:

Yeah, would be the best. Will change some things today

PS: Do you know what a  _FORTIFY_SOURCE error during compilation is? A PM would be nice!

I'll reply later - on my phone. Spending some time with the missus

[raverrr]

Having a little crack at this today. With a slightly different aproach. I'm going to use FNC as a base for the port. Hopefully make things easier.

[XMasterNinni]

@raverrr

Can I use FnC as the default base_rom for my tool?

[Dazzozo]

XMasterNinni, on 16 June 2012 - 12:17 PM, said:

@raverrr

Can I use FnC as the default base_rom for my tool? data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAMAAAC6V+0/AAAABGdBTUEAANbY1E9YMgAAAdRQTFRFV0AI////V0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIW0IIV0AIW0IIW0QJW0IIV0AIV0AIV0AIQzQQa0oJbEwJbVELbk4Kb0wJb1QMcVILc1cMlF8Ll2oNmXEQnn8Vo2gLpGgLpGoMpW8NpXEOp3YQq4MUrH0Rro0Xr4QUsI4XsZAYuXQNwIkSwI0VyIAOyocQyqcdy4QQzosS1Kod1rIf3ZMS3ZUT3a8c3o4Q3rcf4ZER5JUR5ZYS5ZgS5aIW55wT554U6KkZ6qQV6qUW6qYW6qcX66gW7Lsf7a0X7a0Y7a8Z7bEb7rAY7rEY7rMa7rMb77Ma77cd77oc8bob8b4f8cUh8skh870c88If88kk89Im9Mwl9cch9scf9skh9swi9swk98og988k99Mm+dMk+dYm+9cl+9gl+9kn+9on+9oo+9op+9so/Ngl/Non/Nso/N0o/N0p/eAp/eEp/uAn/uIq/uMp/uMq/uQq/+An/+En/+Eo/+Io/+Ip/+Mo/+Mp/+Mq/+Qp/+Qq/+Qr/+Uq/+Ur////QENjqgAAACd0Uk5TAAABCQoLHCYnMDY4OjuCg4WHiImKm56fx8jJys3P1Ofp6enq7/DyAdnyKAAAASJJREFUGNNjYMQCGBgZgICZi09CRUWCj4sZxIMIsgnr2ngW5HlYaQmzQQWZOOWM8xvaWuurSmOM5DiZwILsSq4NHb2zZvS015ZnOsmzgwRZxewbu9TVZ82cqa5eW5JmKcoCFOTRr2hXB4pMV582Sb0yN0ybGygoZFfXPX369GlTpkyZ3FldmGAhABSU8WuZChaZOHHihKbiFHdJoKBKdrO6OkhkYn9/n7p6srcCUFA1q0Z9tjoUzFaP9wIJyvpUqs+GA/UoN2mgoIhtMbJgqJkgUJBXL70MLqoe6a/DA3K8uHVGEVRUPTrQVIwV5E0OZcfUHIg94YEOiuywADEMjktKjI0I8TWABQgo6DTNXYICnE004EEHDmR+KTU1KX54IGMBAGd3XCYdIc62AAAAAElFTkSuQmCC

What do you even use at the moment? FLB2?

[raverrr]

XMasterNinni, on 16 June 2012 - 12:17 PM, said:

@raverrr

Can I use FnC as the default base_rom for my tool? data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAMAAAC6V+0/AAAABGdBTUEAANbY1E9YMgAAAdRQTFRFV0AI////V0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIV0AIW0IIV0AIW0IIW0QJW0IIV0AIV0AIV0AIQzQQa0oJbEwJbVELbk4Kb0wJb1QMcVILc1cMlF8Ll2oNmXEQnn8Vo2gLpGgLpGoMpW8NpXEOp3YQq4MUrH0Rro0Xr4QUsI4XsZAYuXQNwIkSwI0VyIAOyocQyqcdy4QQzosS1Kod1rIf3ZMS3ZUT3a8c3o4Q3rcf4ZER5JUR5ZYS5ZgS5aIW55wT554U6KkZ6qQV6qUW6qYW6qcX66gW7Lsf7a0X7a0Y7a8Z7bEb7rAY7rEY7rMa7rMb77Ma77cd77oc8bob8b4f8cUh8skh870c88If88kk89Im9Mwl9cch9scf9skh9swi9swk98og988k99Mm+dMk+dYm+9cl+9gl+9kn+9on+9oo+9op+9so/Ngl/Non/Nso/N0o/N0p/eAp/eEp/uAn/uIq/uMp/uMq/uQq/+An/+En/+Eo/+Io/+Ip/+Mo/+Mp/+Mq/+Qp/+Qq/+Qr/+Uq/+Ur////QENjqgAAACd0Uk5TAAABCQoLHCYnMDY4OjuCg4WHiImKm56fx8jJys3P1Ofp6enq7/DyAdnyKAAAASJJREFUGNNjYMQCGBgZgICZi09CRUWCj4sZxIMIsgnr2ngW5HlYaQmzQQWZOOWM8xvaWuurSmOM5DiZwILsSq4NHb2zZvS015ZnOsmzgwRZxewbu9TVZ82cqa5eW5JmKcoCFOTRr2hXB4pMV582Sb0yN0ybGygoZFfXPX369GlTpkyZ3FldmGAhABSU8WuZChaZOHHihKbiFHdJoKBKdrO6OkhkYn9/n7p6srcCUFA1q0Z9tjoUzFaP9wIJyvpUqs+GA/UoN2mgoIhtMbJgqJkgUJBXL70MLqoe6a/DA3K8uHVGEVRUPTrQVIwV5E0OZcfUHIg94YEOiuywADEMjktKjI0I8TWABQgo6DTNXYICnE004EEHDmR+KTU1KX54IGMBAGd3XCYdIc62AAAAAElFTkSuQmCC

Yep,yep go ahead