Jump to content

[ROM] Honeycomb SDK Port 15.07.2011 [GEN2 only]


Guest hecatae

Recommended Posts

Guest Ippe H

Any ideas how fix this? Do i need startup that ar6000 with some command like mode=XX, etc..?

<4>[03-03 14:49:26.431460] [509: AR6K startup]ar6000_available

<1>[03-03 14:49:26.431460] [509: AR6K startup]AR6000: Unsupported configurationopcode: 3

<4>[03-03 14:49:26.443450] [509: AR6K startup]Firmware mode set

<1>[03-03 14:49:26.443450] [509: AR6K startup]AR6000: Unsupported configuration opcode: 3

<1>[03-03 14:49:26.456470] [509: AR6K startup]AR6000: Unsupported configuration opcode: 5

<4>[03-03 14:49:26.464106] [509: AR6K startup] BMI enabled

<4>[03-03 14:49:26.471465] [509: AR6K startup]ar6000_avail: name=wlan0 hifdevice =0xe428a000, dev=0xe32ae000 (0), ar=0xe32ae2e0

<4>[03-03 14:49:26.471465] [509: AR6K startup]old options [0] old sleep [29]

<4>[03-03 14:49:26.486508] [509: AR6K startup]Set hi_refclk_hz : Ref Clock=26000000

<4>[03-03 14:49:26.493621] [509: AR6K startup]AR6000: eeprom transfer by HOST

<4>[03-03 14:49:26.493621] [509: AR6K startup]eeprom_ar6000_transfer: Enter

<4>[03-03 14:49:26.506643] [509: AR6K startup]enable_SI

<4>[03-03 14:49:26.511453] [509: AR6K startup]eeprom_ar6000_transfer: checking eeprom file /data/misc/wifi/athSavedEeprom.bin

<4>[03-03 14:49:26.522095] [509: AR6K startup]eeprom_ar6000_transfer: Valid eeprom file /data/misc/wifi/athSavedEeprom.bin was saved already

<4>[03-03 14:49:26.534163] [509: AR6K startup]eeprom_ar6000_transfer: load eeprom data from file /data/misc/wifi/athSavedEeprom.bin

<4>[03-03 14:49:26.545445] [509: AR6K startup]read_eeprom_from_file file offsetopsition: 0h

<4>[03-03 14:49:26.553343] [509: AR6K startup]read_eeprom_from_file: length=768

<4>[03-03 14:49:26.561455] [509: AR6K startup]disable_SI

<4>[03-03 14:49:26.561455] [509: AR6K startup]AR6000: BMISetAppStart

<4>[03-03 14:49:26.561455] [509: AR6K startup]AR6000: enable HI_OPTION_TIMER_WAR

<4>[03-03 14:49:26.577563] [509: AR6K startup]AR6000: firmware_transfer

<4>[03-03 14:49:26.583638] [509: AR6K startup]firmware_transfer: Enter, filename =/system/wifi/athwlan.bin.z77

<4>[03-03 14:49:26.593013] [509: AR6K startup]firmware_transfer file offset opsition: 0h

<4>[03-03 14:49:26.593013] [509: AR6K startup]firmware_transfer: length=96720, address=0x502070

<4>[03-03 14:49:26.608726] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192

<4>[03-03 14:49:26.651451] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192

<4>[03-03 14:49:26.681463] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192

<4>[03-03 14:49:26.721766] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192

<4>[03-03 14:49:26.761455] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192

<4>[03-03 14:49:26.801460] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192

<4>[03-03 14:49:26.841461] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192

<4>[03-03 14:49:26.881573] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192

<4>[03-03 14:49:26.911513] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192

<4>[03-03 14:49:26.951788] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192

<4>[03-03 14:49:26.991456] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192

<4>[03-03 14:49:27.031461] [509: AR6K startup]firmware_transfer: BMILZData: len=6608, org_len=6608

<4>[03-03 14:49:27.061716] [509: AR6K startup]firmware_transfer: Enter, filename=/system/wifi/data.patch.hw2_0.bin

<4>[03-03 14:49:27.061716] [509: AR6K startup]firmware_transfer file offset opsition: 0h

<4>[03-03 14:49:27.076223] [509: AR6K startup]firmware_transfer: length=1328, address=0x52d6d0

<4>[03-03 14:49:27.084290] [509: AR6K startup]ar6000_init() Got WMI @ 0xe4379600.

<4>[03-03 14:49:27.241451] [510: ksdioirqd/mmc1]mac address = 00:24:14:3a:5a:11

<4>[03-03 14:49:27.241451] [509: AR6K startup]ar6000_init() WMI is ready

<4>[03-03 14:49:27.241451] [510: ksdioirqd/mmc1]wmi_control_rx() : Unknown id 0x101e

<4>[03-03 14:49:27.258240] [510: ksdioirqd/mmc1]AR6000 Reg Code = 0x61

<4>[03-03 14:49:28.761458] [510: ksdioirqd/mmc1]AR6000 scan complete: 0

#

Edited by Ippe H
Link to comment
Share on other sites

Guest Lew247

Thanks - which do people want? leave this her and the rom thread as well or merge the two with a link in the 1st post of this thread with the rom location?

Link to comment
Share on other sites

Guest jonas.lindberg

I've got an app, or rather a game I'd really miss when switching from CM7 to this one, but sadly I get an FC on boot. The game is called TURF (avaiable on market), could someone try it and tell me if it works or if there is anything I could do to make it work?

Edited by jonas.lindberg
Link to comment
Share on other sites

Guest hecatae
Thanks - which do people want? leave this her and the rom thread as well or merge the two with a link in the 1st post of this thread with the rom location?

if you merge this one in as well http://android.modaco.com/content/zte-blad...ndroid-3-0-sdk/

Ippe H and I will have control of the first post and be able to update it

edit: thank you lew247

Edited by hecatae
Link to comment
Share on other sites

Guest hecatae
I've got an app, or rather a game I'd really miss when switching from CM7 to this one, but sadly I get an FC on boot. The game is called TURF (avaiable on market), could someone try it and tell me if it works or if there is anything I could do to make it work?

if you can provide a logcat we can have a look at it, though it may not be fixable til honeycomb hits aosp as this is a heavily modified sdk system image

Link to comment
Share on other sites

Guest hecatae
Any ideas how fix this? Do i need startup that ar6000 with some command like mode=XX, etc..?

<4>[03-03 14:49:26.431460] [509: AR6K startup]ar6000_available
<1>[03-03 14:49:26.431460] [509: AR6K startup]AR6000: Unsupported configurationopcode: 3
<4>[03-03 14:49:26.443450] [509: AR6K startup]Firmware mode set
<1>[03-03 14:49:26.443450] [509: AR6K startup]AR6000: Unsupported configuration opcode: 3
<1>[03-03 14:49:26.456470] [509: AR6K startup]AR6000: Unsupported configuration opcode: 5
<4>[03-03 14:49:26.464106] [509: AR6K startup] BMI enabled
<4>[03-03 14:49:26.471465] [509: AR6K startup]ar6000_avail: name=wlan0 hifdevice =0xe428a000, dev=0xe32ae000 (0), ar=0xe32ae2e0
<4>[03-03 14:49:26.471465] [509: AR6K startup]old options [0] old sleep [29]
<4>[03-03 14:49:26.486508] [509: AR6K startup]Set hi_refclk_hz : Ref Clock=26000000
<4>[03-03 14:49:26.493621] [509: AR6K startup]AR6000: eeprom transfer by HOST
<4>[03-03 14:49:26.493621] [509: AR6K startup]eeprom_ar6000_transfer: Enter
<4>[03-03 14:49:26.506643] [509: AR6K startup]enable_SI
<4>[03-03 14:49:26.511453] [509: AR6K startup]eeprom_ar6000_transfer: checking eeprom file /data/misc/wifi/athSavedEeprom.bin
<4>[03-03 14:49:26.522095] [509: AR6K startup]eeprom_ar6000_transfer: Valid eeprom file /data/misc/wifi/athSavedEeprom.bin was saved already
<4>[03-03 14:49:26.534163] [509: AR6K startup]eeprom_ar6000_transfer: load eeprom data from file /data/misc/wifi/athSavedEeprom.bin
<4>[03-03 14:49:26.545445] [509: AR6K startup]read_eeprom_from_file file offsetopsition: 0h
<4>[03-03 14:49:26.553343] [509: AR6K startup]read_eeprom_from_file: length=768
<4>[03-03 14:49:26.561455] [509: AR6K startup]disable_SI
<4>[03-03 14:49:26.561455] [509: AR6K startup]AR6000: BMISetAppStart
<4>[03-03 14:49:26.561455] [509: AR6K startup]AR6000: enable HI_OPTION_TIMER_WAR
<4>[03-03 14:49:26.577563] [509: AR6K startup]AR6000: firmware_transfer
<4>[03-03 14:49:26.583638] [509: AR6K startup]firmware_transfer: Enter, filename =/system/wifi/athwlan.bin.z77
<4>[03-03 14:49:26.593013] [509: AR6K startup]firmware_transfer file offset opsition: 0h
<4>[03-03 14:49:26.593013] [509: AR6K startup]firmware_transfer: length=96720, address=0x502070
<4>[03-03 14:49:26.608726] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192
<4>[03-03 14:49:26.651451] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192
<4>[03-03 14:49:26.681463] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192
<4>[03-03 14:49:26.721766] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192
<4>[03-03 14:49:26.761455] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192
<4>[03-03 14:49:26.801460] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192
<4>[03-03 14:49:26.841461] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192
<4>[03-03 14:49:26.881573] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192
<4>[03-03 14:49:26.911513] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192
<4>[03-03 14:49:26.951788] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192
<4>[03-03 14:49:26.991456] [509: AR6K startup]firmware_transfer: BMILZData: len=8192, org_len=8192
<4>[03-03 14:49:27.031461] [509: AR6K startup]firmware_transfer: BMILZData: len=6608, org_len=6608
<4>[03-03 14:49:27.061716] [509: AR6K startup]firmware_transfer: Enter, filename=/system/wifi/data.patch.hw2_0.bin
<4>[03-03 14:49:27.061716] [509: AR6K startup]firmware_transfer file offset opsition: 0h
<4>[03-03 14:49:27.076223] [509: AR6K startup]firmware_transfer: length=1328, address=0x52d6d0
<4>[03-03 14:49:27.084290] [509: AR6K startup]ar6000_init() Got WMI @ 0xe4379600.
<4>[03-03 14:49:27.241451] [510: ksdioirqd/mmc1]mac address = 00:24:14:3a:5a:11
<4>[03-03 14:49:27.241451] [509: AR6K startup]ar6000_init() WMI is ready
<4>[03-03 14:49:27.241451] [510: ksdioirqd/mmc1]wmi_control_rx() : Unknown id 0x101e
<4>[03-03 14:49:27.258240] [510: ksdioirqd/mmc1]AR6000 Reg Code = 0x61
<4>[03-03 14:49:28.761458] [510: ksdioirqd/mmc1]AR6000 scan complete: 0
#[/code]

tweeted @HCDRJacob to see if he has any ideas on it

Edited by hecatae
Link to comment
Share on other sites

Guest vulpy

Fabulous, had a quick run at it and it sure does look fantastic... don't complain about the resolution, it is a 1-1 port from a tablet environment!

for someone with good eyes, this makes the blade as good as a tablet :(

Sure, it still needs polishing (speed improvement and other stuff) but check this out: cell radio working = you are connected baby !

Link to comment
Share on other sites

Guest MKD73

Wow , for a cheap handset this is amazing , blows my SE Xperia X10 out of the water with regards to flavours , devs on another board work so hard trying to run froyo/ginger , cm7 on the X10 but because the bootloader is locked down tighter than a nuns ***** its impossible .

P.S i'm trying to compile an AOSP 2.3.x for this handset (newb dev) cm7 is good i just like my OS stock hehe

Back on topic , defo giving this a go keep up the good work

Link to comment
Share on other sites

Guest uskixboy

Tried this on my blade this morning... amazing work. It will be great to see the bugs worked out over time but for now I am well impressed. The resolution is great and though it doesn't run very fast that is not all that surprising considering honeycomb is designed for tablets with minimum 1Ghz processor, or so I have heard. Anyway many thanks for the time and effort and keep up the good work.

Link to comment
Share on other sites

Guest fonix232
OH MY GOD! It has got full hungarian language support!

Even 2.2 and 2.3 didn't have this

CM7 from nightly 11 got it too :(

Good work Ippe, but a question. What is wrong with wifi? The log you posted shows it loads the firmware of the AR600 stuff, and sets it's freq, channels, etc.

Only problems I've noticed the unkown opcodes, and this:

<4>[03-03 14:49:27.241451] [510: ksdioirqd/mmc1]wmi_control_rx() : Unknown id 0x101e

Link to comment
Share on other sites

Guest domenico lamberti

used this as my daily ROM for a full 2 days and the only thing i missed was wifi, and occasionally callin, the keyboard was great, i went into spare parts and increased text size, multi-touch in browser was (dare-i-say-it) iphone fast and it wasnt too bad for a 600Mhz processor , better than some of the 1Ghz ive seen

Link to comment
Share on other sites

Wow, this is something I wasn't expecting... nice work! It's cool, but I guess it's probably of little practical use, as the Honeycomb UI is geared towards large screen tablets. Or is Ippe intending to fix up the shiny Honeycomb kernel then make it more phone-usable by sticking the old Android phone UI back on?

Link to comment
Share on other sites

Guest hecatae
Wow, this is something I wasn't expecting... nice work! It's cool, but I guess it's probably of little practical use, as the Honeycomb UI is geared towards large screen tablets. Or is Ippe intending to fix up the shiny Honeycomb kernel then make it more phone-usable by sticking the old Android phone UI back on?

using the cm7 zte kernel source at present, from Tom G's github

Link to comment
Share on other sites

Guest jonas.lindberg

By the way, are they working on making the work or can I give up the dream of this a everyday-ROM right here and now?

Link to comment
Share on other sites

Guest IronDoc
By the way, are they working on making the work or can I give up the dream of this a everyday-ROM right here and now?

Probably give up on that, though I imagine they will fix the more glaring bugs. I don't really see why you'd want this as an everyday ROM.

This is just speculaiton ofc.

Link to comment
Share on other sites

Guest HCDR.Jacob

Just to say, I'll be working on Honeycomb myself but only once we get source, and I may never release. It all depends on how usable and functional it is on phones.

Link to comment
Share on other sites

using the cm7 zte kernel source at present, from Tom G's github

Fair enough, I missed that bit - I assumed it was using the honeycomb kernel with the RIL modules etc from CM7. My point still stands though; unless the UI is modifiable it probably isn't hugely practical for everyday small-screen phone use. Still pretty awesome though :(

Link to comment
Share on other sites

Guest jonas.lindberg
if you can provide a logcat we can have a look at it, though it may not be fixable til honeycomb hits aosp as this is a heavily modified sdk system image
Well, there where a hell lot of lines, but I think these are the most relevant

 03-03 22:33:57.661 I/ActivityManager(135): Starting: Intent { act=android.intent.action.MAIN cat= [android.intent.category.LAUNCHER] flg=0x10104000 pkg=se.turfwars.android cmp=se.turfwars.android/.activity.Splash bnds=[466,407][752,455] } from pid 195 03-03 22:33:57.891 I/ActivityManager(135): Start proc se.turfwars.android for activity se.turfwars.android/.activity.Splash: pid=2782 uid=10052 gids={3003} 03-03 22:33:59.541 I/ActivityManager(135): Displayed se.turfwars.android/.activity.Splash: +1s652ms (total +55s430ms) 03-03 22:34:01.255 I/ActivityManager(135): Starting: Intent { cmp=se.turfwars.android/.activity.Main } from pid 2782 03-03 22:34:05.581 W/ActivityManager(135): Force finishing activity se.turfwars.android/.activity.Main 03-03 22:34:06.121 W/ActivityManager(135): Activity pause timeout for ActivityRecord{41260ee8 se.turfwars.android/.activity.Main} 03-03 22:34:08.321 E/InputDispatcher(135): channel '41390e28 se.turfwars.android/se.turfwars.android.activity.Splash (server)' ~ Consumer closed input channel or an error occurred. events=0x8 03-03 22:34:08.321 E/InputDispatcher(135): channel '41390e28 se.turfwars.android/se.turfwars.android.activity.Splash (server)' ~ Channel is unrecoverably broken and will be disposed! 03-03 22:34:08.321 I/WindowManager(135): WINDOW DIED Window{41390e28 se.turfwars.android/se.turfwars.android.activity.Splash paused=true} 03-03 22:34:08.331 I/ActivityManager(135): Process se.turfwars.android (pid 2782) has died. 03-03 22:34:08.331 I/WindowManager(135): WIN DEATH: Window{41118878 se.turfwars.android/se.turfwars.android.activity.Main paused=false} 03-03 22:34:08.341 E/InputDispatcher(135): channel '415e6330 se.turfwars.android/se.turfwars.android.activity.Main (server)' ~ Consumer closed input channel or an error occurred. events=0x8 03-03 22:34:08.341 E/InputDispatcher(135): channel '415e6330 se.turfwars.android/se.turfwars.android.activity.Main (server)' ~ Channel is unrecoverably broken and will be disposed! 03-03 22:34:08.411 I/WindowManager(135): WIN DEATH: Window{415e6330 se.turfwars.android/se.turfwars.android.activity.Main paused=false} 03-03 22:34:08.441 I/WindowManager(135): WINDOW DIED Window{415e6330 se.turfwars.android/se.turfwars.android.activity.Main paused=false} 03-03 22:34:16.681 W/ActivityManager(135): Activity destroy timeout for ActivityRecord{40de1030 se.turfwars.android/.activity.Splash} 03-03 22:34:16.721 W/ActivityManager(135): Activity destroy timeout for ActivityRecord{41260ee8 se.turfwars.android/.activity.Main}

Link to comment
Share on other sites

Guest Ippe H
CM7 from nightly 11 got it too :(

Good work Ippe, but a question. What is wrong with wifi? The log you posted shows it loads the firmware of the AR600 stuff, and sets it's freq, channels, etc.

Only problems I've noticed the unkown opcodes, and this:

<4>[03-03 14:49:27.241451] [510: ksdioirqd/mmc1]wmi_control_rx() : Unknown id 0x101e

Nothing :( it's working now.. coming to next release.

Next need find solution to that audio issue..

Edited by Ippe H
Link to comment
Share on other sites

Guest mELIANTE
Just to say, I'll be working on Honeycomb myself but only once we get source, and I may never release. It all depends on how usable and functional it is on phones.

Hey Jacob, care to drop some news in the Cyanogenmod thread? We are getting lonely :(

About Honeycomb, great proof of concept :(

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

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