Jump to content
Dazzozo

[ICS] [CM9] [4.0.4] CyanogenMod 9 for the ZTE Crescent [ROM] [Last updated: 13/07]

Recommended Posts

Neat, working on CWM 5.5.0.4, and I found a way to find your touchscreen model without the stock ROM and this should work in Terminal Emulator within Android, too.

su

cat /proc/touchscreen/ts_information

  • Upvote 1

Share this post


Link to post
Share on other sites

Just wondering if it's safe for me to uninstall Rom Manager and Google Talk via Titanium Backup?

Thanks

Share this post


Link to post
Share on other sites

Just wondering if it's safe for me to uninstall Rom Manager and Google Talk via Titanium Backup?

Thanks

Yep. I do the same with ROM Manager and Terminal Emulator (prefer knowing its a market version of the latter)

Edited by Dazzozo

Share this post


Link to post
Share on other sites

So I've stared at an over-bright screen for most of the night trying to get better Bluetooth and Wi-Fi support for our BCM4330. It seems we are going to need that SmartTab source that Fuzzra tried to port about two months ago as that's where the problem seems to lie.

I grabbed a later version of the source than the one he committed to his fork of the kernel (in the hopes that it would actually work now as the SmartTab guys seem to have had success with it) and suffice to say it's going to take a lot of effort to get this going.

I can't just try to half ass port it over - we're missing stuff, I add it, and we're missing even more stuff. I'll probably have to go the full way and edit a lot of this myself. Their board is msm8x60, after all. :(

I'll look at it tomorrow (when it's not 1am and my eyes aren't sore), it's quite a nice challenge really. ;)

Share this post


Link to post
Share on other sites

I have a phone!

And now I have an unlocked phone...

Made me smile. ;)

Share this post


Link to post
Share on other sites

And finally I have CM9 up and running. Back camera works but not fluantly (did not try with stock rom), wifi works right away (used it to set up google account), Bluetooth doesn't start:

Feature request: Youtube app and flashlight app

Share this post


Link to post
Share on other sites

And finally I have CM9 up and running. Back camera works but not fluantly (did not try with stock rom), wifi works right away (used it to set up google account), Bluetooth doesn't start:

Feature request: Youtube app and flashlight app -> installed some flashlight apps but the led seems not to work, doens't flash when using camera either

Made me smile. ;)

Uhu :) It looks very nice and it really goes a lot faster than stock. Keep up the good work!

Edited by techsolo

Share this post


Link to post
Share on other sites

YouTube - add it yourself

Flashlight - well we can dream :)

Found the youtube app and flashplayer.

Share this post


Link to post
Share on other sites

Camera preview slowness has already been fixed in some changes committed this morning, though it's still tearing but that'll be fixed in time.

Also changed some of the OMX proprietary libs this morning. Next focus will be BT/Wi-Fi.

Share this post


Link to post
Share on other sites

Feature request: Youtube app and flashlight app

That won't happen, this isn't a custom rom, it's CyanogenMod, it has to be the same across all releases. If you want to then take it and insert your own apps that's fine but I doubt you'll ever see anything in our CM9 that isn't in the rest. Glad you've finally got to enjoy the CM9 rom tho :)

I would heartily recommend using the Nova Launcher (paid version) and the Reloaded ICS addon

Edited by PsYcHoKiLLa

Share this post


Link to post
Share on other sites

Apex all the way :P

What do you prefer Nova for Psycho? I did like the look of it initially, but free Apex does what I want for free.

Share this post


Link to post
Share on other sites

So I had another go at the bcm4330_b1_b2_zte driver today and got it to actually compile after messing around with our board file. Doesn't work straight out of the box yet but it's looking good.


<4>[05-12 22:15:36.400000] [1077: insmod]chengjiatest: bcm_wlan_power_on onoff =1
<4>[05-12 22:15:36.400000] [1077: insmod]bcm_power
<4>[05-12 22:15:36.400000] [1077: insmod]bcm_power close bt_config_power_on by xum
<3>[05-12 22:15:36.400000] [1077: insmod]gpio_request: 26 to 0 ok-xm!
<3>[05-12 22:15:36.400000] [1077: insmod]gpio_request: 20 to 0 ok-xm!
<3>[05-12 22:15:36.430000] [1077: insmod]gpio_request: 26 to 1 ok-xm!
<3>[05-12 22:15:36.430000] [1077: insmod]gpio_request: 20 to 1 ok-xm!
<4>[05-12 22:15:36.430000] [1077: insmod]GPIO_XUM end ok-xm!
<4>[05-12 22:15:36.430000] [1077: insmod]chengjiatest: enable sdcc4 detect!
<4>[05-12 22:15:36.430000] [1077: insmod]
<4>[05-12 22:15:36.430000] [1077: insmod]Dongle Host Driver, version 5.90.125.16.1
<4>[05-12 22:15:36.430000] [1077: insmod]Compiled in /home/yuki/android/builds/ics-tilal/../.. on May 12 2012 at 22:33:59
<4>[05-12 22:15:48.430005] [1077: insmod]chengjiatest: bcm_wlan_power_off onoff= 1
<4>[05-12 22:15:48.430005] [1077: insmod]bcm_power
[/CODE]

@ tilal: am I good to fork the kernel temporarily while I work on this? I'll send a pull request when it's 100% and delete the fork. That is, if I can get it 100%.

  • Upvote 1

Share this post


Link to post
Share on other sites

BT is a known issue. Dazzozo is currently working on it. Camera flash works no problem on my TMV. Don't think anyone else has reported that.

Edited by fr0do

Share this post


Link to post
Share on other sites

I can afford to work on the Wi-Fi/BT driver as the camera can just be stolen from the Skate.

Share this post


Link to post
Share on other sites

BT is a known issue. Dazzozo is currently working on it. Camera flash works no problem on my TMV. Don't think anyone else has reported that.

I did report that the camera flash isn't working (and the camera preview is shokking)

Share this post


Link to post
Share on other sites

So I decided to try to get the BT working again in its current, Wi-Fi dependent state before even adventuring in to that. If I root up, turn the Bluetooth online (echo 1 > /sys/class/rfkill/rfkill0/state) and run the init.qcom.bt.sh script, I get what seems to be good results.


get_bdaddr: after: 0e.be.cc.b2.1a.68
Baud rate parameters: DHBR=0x 0,DLBR=0x 0
[/CODE] And logcat confirms this.
[CODE]
I/qcom-bluetooth( 1108): init.qcom.bt.sh: start_hciattach: pid = 1107
E/bluez_hciattach( 1107): Call init_uart
E/bluez_hciattach( 1107): ->bcm2035
E/bluez_hciattach( 1107): read HCD file ok, size=38135
E/bluez_hciattach( 1107): download hcd file success
E/bluez_hciattach( 1107): bt-addr:0x0ebeccb21a68
E/bluez_hciattach( 1107): Set PCM ok
E/bluez_hciattach( 1107): Set sleep mode ok
E/bluez_hciattach( 1107): BT chip change BaudRate to: 3000000
E/bluez_hciattach( 1107): <-bcm2035
E/bluez_hciattach( 1107): Device setup complete

However this does not translate in to working BT in the OS. The BT switch is still snapping back to off, with or without this manual work.

Any ideas?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.