olionair

Cyanogen Mod 7 For Blade

235 posts in this topic

I'm available on twitter btw.

ok following, will ask a few questions later.

0

Share this post


Link to post
Share on other sites
ok following, will ask a few questions later.

following but not sure about twitter!

anyway I tried the device tree by downloading it to devices/zte/blade under a CM7 repo, lunch shows the options for blade but when I select it says no known product for zte_blade - do I need to change something else?

0

Share this post


Link to post
Share on other sites
following but not sure about twitter!

anyway I tried the device tree by downloading it to devices/zte/blade under a CM7 repo, lunch shows the options for blade but when I select it says no known product for zte_blade - do I need to change something else?

I think you need to change this in device_blade.mk on the device tree:

PRODUCT_NAME := cyanogen_blade

PRODUCT_DEVICE := blade

PRODUCT_MODEL := blade

(not tested at all by me)

0

Share this post


Link to post
Share on other sites

r3pek, great work!

I hope you can get all up and running, as I said before, give me instructions and I give you a build :lol:

Just a little addition to your config:

please include the T-Mobile theming platform too! :)

0

Share this post


Link to post
Share on other sites
I think you need to change this in device_blade.mk on the device tree:

PRODUCT_NAME := cyanogen_blade

PRODUCT_DEVICE := blade

PRODUCT_MODEL := blade

(not tested at all by me)

Ok I think I got there in the end but I called everything blade, also initially forgot to re-run build/envsetup.sh so it wasn't picking up my changes

trying build now

0

Share this post


Link to post
Share on other sites
Ok I think I got there in the end but I called everything blade, also initially forgot to re-run build/envsetup.sh so it wasn't picking up my changes

trying build now

is RIL working if not talk to HCDRjacob from cyanogen tell him Oliver Haywood sent you

0

Share this post


Link to post
Share on other sites
is RIL working if not talk to HCDRjacob from cyanogen tell him Oliver Haywood sent you

Does he have ideas or does he know exactly what needs doing? There is a flashable by fastboot 2.3 rom we could do with making the ril changes too also. And it's already available.

0

Share this post


Link to post
Share on other sites
Does he have ideas or does he know exactly what needs doing? There is a flashable by fastboot 2.3 rom we could do with making the ril changes too also. And it's already available.

it's also flashable by clockwork or RA http://ul.to/mzrgf0

md5sum e1152af382ee763b1ff637460ebdd306

signed_012711_204602.zip

Edited by hecatae
0

Share this post


Link to post
Share on other sites

It boots!!!

I made some changes to r3peks files and got a working build out of it with some help from fonix232, strangely I have a 32 bit system but didn't have any issues with gingerbread wanting 64 bit. anyway i'll attach my files here, there is an initial get file which will get all the cm7 and r3peks code then you need to apply a patch file to remove some files that weren't on my system (jj7) then there is a build file, at last we have a build that others can potentially help with.

NB THIS IS A DEVELOPER ONLY BUILD it is of no use whatsoever to non-developers.

It's slow and nothing much works, not even wifi and it only has 162meg because of the vmsplit thing but it's a start. I'm wondering if it's worth merging this device tree into code aurora rather than cm7 for the extra memory.

edit - out of attachment space so they are in this post

getcm7.sh

mkdir cm7

cd cm7

repo init -u git://github.com/CyanogenMod/android.git -b gingerbread

repo sync

git clone git://github.com/r3pek/device_zte_blade device/zte/blade

#optional

#git clone git://github.com/r3pek/kernel-zte-blade kernel

cd device/zte/blade

sudo ~/android/sdk/platform-tools/adb kill-server

sudo ~/android/sdk/platform-tools/adb connect 192.168.20.147

./extract-files.sh

echo 'now apply the diff patch'

echo 'then use the buildcm7.sh'

fixcm7.diff

diff --git a/device_blade.mk b/device_blade.mk

index f0a099b..3769cbf 100644

--- a/device_blade.mk

+++ b/device_blade.mk

@@ -78,13 +78,11 @@ PRODUCT_COPY_FILES += \

## OMX proprietaries

PRODUCT_COPY_FILES += \

vendor/zte/blade/proprietary/lib/libmm-adspsvc.so:system/lib/libmm-adspsvc.so \

- vendor/zte/blade/proprietary/lib/libOmxAacDec.so:system/lib/libOmxAacDec.so \

vendor/zte/blade/proprietary/lib/libOmxAmrRtpDec.so:system/lib/libOmxAmrRtpDec.so \

vendor/zte/blade/proprietary/lib/libOmxH264Dec.so:system/lib/libOmxH264Dec.so \

vendor/zte/blade/proprietary/lib/libOmxQcelpDec.so:system/lib/libOmxQcelpDec.so \

vendor/zte/blade/proprietary/lib/libOmxAacEnc.so:system/lib/libOmxAacEnc.so \

vendor/zte/blade/proprietary/lib/libOmxAmrwbDec.so:system/lib/libOmxAmrwbDec.so \

- vendor/zte/blade/proprietary/lib/libOmxMp3Dec.so:system/lib/libOmxMp3Dec.so \

vendor/zte/blade/proprietary/lib/libOmxVidEnc.so:system/lib/libOmxVidEnc.so \

vendor/zte/blade/proprietary/lib/libOmxAmrDec.so:system/lib/libOmxAmrDec.so \

vendor/zte/blade/proprietary/lib/libOmxEvrcDec.so:system/lib/libOmxEvrcDec.so \

@@ -150,6 +148,6 @@ PRODUCT_COPY_FILES += \

$(call inherit-product, build/target/product/full_base.mk)

PRODUCT_BUILD_PROP_OVERRIDES += BUILD_UTC_DATE=0

-PRODUCT_NAME := Blade

+PRODUCT_NAME := zte_blade

PRODUCT_DEVICE := blade

PRODUCT_MODEL := ZTE Blade

diff --git a/extract-files.sh b/extract-files.sh

index 93671f9..c13ae32 100755

--- a/extract-files.sh

+++ b/extract-files.sh

@@ -21,6 +21,10 @@ etc/firmware/yamato_pfp.fw

etc/firmware/yamato_pm4.fw

lib/egl/egl.cfg

+lib/egl/libGLESv1_CM_adreno200.so

+lib/egl/libq3dtools_adreno200.so

+lib/egl/libEGL_adreno200.so

+lib/egl/libGLESv2_adreno200.so

lib/hw/gralloc.default.so

lib/hw/gralloc.msm7k.so

@@ -59,7 +63,6 @@ lib/libmmjpeg.so

lib/liboemcamera.so

lib/libmm-adspsvc.so

-lib/libOmxAacDec.so

lib/libOmxAacEnc.so

lib/libOmxAmrDec.so

lib/libOmxAmrEnc.so

@@ -76,6 +79,8 @@ lib/libOmxVidEnc.so

lib/libOmxWmaDec.so

lib/libOmxWmvDec.so

+lib/libgsl.so

+

lib/librpc.so

"

buildcm7.sh

make -j`grep processor /proc/cpuinfo | wc -l` bacon

Edited by rjm2k
0

Share this post


Link to post
Share on other sites

Yes it builds, but now I'm stuck here:

Install: out/target/product/blade/system/bin/system_server

Install: out/target/product/blade/system/lib/libandroid_servers.so

and make hangs at this. Also, JAVA part compiling takes a lot of time, it made my PC lag like hell for an hour or so.

0

Share this post


Link to post
Share on other sites
Yes it builds, but now I'm stuck here:

Install: out/target/product/blade/system/bin/system_server

Install: out/target/product/blade/system/lib/libandroid_servers.so

and make hangs at this. Also, JAVA part compiling takes a lot of time, it made my PC lag like hell for an hour or so.

I didn't get that , but I'm using an unsupported dev environment!

0

Share this post


Link to post
Share on other sites
I didn't get that , but I'm using an unsupported dev environment!

Finally compiled, had to run make a few times ;)

So far, it boots. Yay!

- No RIL (expected)

- No WiFi (there should be)

- No Bluetooth

- No sound

- menus are bugged

- effects disabled, no cool screen on-off animation

- No USB connection (only ADB)

- Random reboots

Edited by fonix232
0

Share this post


Link to post
Share on other sites
Finally compiled, had to run make a few times ;)

So far, it boots. Yay!

- No RIL (expected)

- No WiFi (there should be)

- No Bluetooth

- No sound

- menus are bugged

- effects disabled, no cool screen on-off animation

- No USB connection (only ADB)

- Random reboots

i'm not sure if r3pek has changes he hasn't commited yet as he seemed to suggest that some stuff was working

0

Share this post


Link to post
Share on other sites
i'm not sure if r3pek has changes he hasn't commited yet as he seemed to suggest that some stuff was working

All of that stuff can sit on the backburner though. The priority should be RIL through and through. At the end of the day our beautiful little devices are actually phones. ;)

0

Share this post


Link to post
Share on other sites
All of that stuff can sit on the backburner though. The priority should be RIL through and through. At the end of the day our beautiful little devices are actually phones. ;)

You can put RIL in your a*s if you got no WiFi, BT, GPS, sound, etc. Of course it is important, but first fix the things what are there in Tom G's generic 2.3 build.

Also, CM Settings generates reboot too.

0

Share this post


Link to post
Share on other sites
You can put RIL in your a*s if you got no WiFi, BT, GPS, sound, etc. Of course it is important, but first fix the things what are there in Tom G's generic 2.3 build.

Also, CM Settings generates reboot too.

Yeah i know but what i meant was we know the other things are fixable already (mostly). To me i don't mind a rom being unstable if phone part works whereas i wouldn't ever flash a rom no matter how well it worked if there were no phone part. But this is all opinion and a bit off topic.

;)

0

Share this post


Link to post
Share on other sites
All of that stuff can sit on the backburner though. The priority should be RIL through and through. At the end of the day our beautiful little devices are actually phones. ;)

some of the stuff is needed so ril can be worked on though, without debugging for example you can't see whats going on that stops ril working, also wifi missing makes it difficult to get stuff onto the phone

0

Share this post


Link to post
Share on other sites
some of the stuff is needed so ril can be worked on though, without debugging for example you can't see whats going on that stops ril working, also wifi missing makes it difficult to get stuff onto the phone

Yeah i know i think my comments have been made a little too literally. All i meant was ril should be high priority, obviously random reboots etc need to be ironed out to be able to actually test stuff ;)

0

Share this post


Link to post
Share on other sites
There now seems to be yet another repo for this https://github.com/HCDRJacob/device_zte_blade , looks more uptodate that r3peks but haven't tried it yet. I wish the devs would get together and grant others rights to their git rather than everyone creating a seperate copy.

based on z71, aka ZTE x876.

builds does not boot

0

Share this post


Link to post
Share on other sites

Same here, couldn't get it to boot; checking various things....

0

Share this post


Link to post
Share on other sites
Same here, couldn't get it to boot; checking various things....

Looks like the partition sizes & kernel base address are wrong.

0

Share this post


Link to post
Share on other sites
It's slow and nothing much works, not even wifi and it only has 162meg because of the vmsplit thing but it's a start. I'm wondering if it's worth merging this device tree into code aurora rather than cm7 for the extra memory.

Here's what you need to change for 2G vmsplit:

https://www.codeaurora.org/gitweb/quic/la/?...ae3a7ef4b2cb9bb

At least on 2.2 that is what you need to do. If you want to make a quick hack, just replace the original prelink-linux-arm.map with the 2G version and change the two defines in prelinkmap.c.

Edited by kallt_kaffe
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.