Jump to content

23/Sep: Kernel Source

Guest PaulOBrien

By Guest PaulOBrien
in ZTE Blade / Libra ROMs & ROM customisation

 Share

Recommended Posts

Guest rjm2k

Guest rjm2k

Posted
Posted
He wants you to get that??

I have asked for it, they said they would be releasing it soon and would let me know when they do.

  • Replies 486
  • Created
  • Last Reply

Popular Days

Popular Days

Popular Posts

Guest Matty-p
Guest Matty-p

(Quote name='sorrowuk' date='Nov 2 2010, 03:11' post='1461472'] So is it easy to make a froyo 2.2 build using this source ? Yes but it is slower beacause its on a. 29 as apose to a 32

Posted Images

Guest deltronuk

Guest deltronuk

Posted
Posted

I spent some time looking at the source last night. ZTE used an out-of-tree driver for the wifi interface (ar6000) but didn't include the source. I believe it's part of the linux-sdio project. As far as I am aware they are obliged to release the source for this too.

Guest rjm2k

Guest rjm2k

Posted
Posted
I spent some time looking at the source last night. ZTE used an out-of-tree driver for the wifi interface (ar6000) but didn't include the source. I believe it's part of the linux-sdio project. As far as I am aware they are obliged to release the source for this too.

passed to ZTE

Guest screwface

Guest screwface

Posted
Posted (edited)
He wants you to get that??

yeah

Edited by screwface
Guest vl4d1m1r

Guest vl4d1m1r

Posted
Posted
passed to ZTE

We just spent a few hours trying to patch in ar6000 code from elsewhere with no luck, so this is pretty crucial unfortunately. Hopefully there will be a speedy fix.

Guest twatter

Guest twatter

Posted
Posted (edited)

Apologies... sort of related to this thread....

It seems to me that than zte blade / san fran... is an purchased oem design......

i.e http://news.oneindia.in/2010/11/05/tech-lg...ptimus-one.html

Maybe this will help for 2.2 (source code release by Lg)......time will only tell

Thanks for the work everyone has one done

Edited by twatter
Guest hero protagonist

Guest hero protagonist

Posted
Posted

The Optimus One is a different design (e.g. screen is only 340x480)

Guest Mark D

Guest Mark D

Posted
Posted
The Optimus One is a different design (e.g. screen is only 340x480)

Yes screen type is different but chipsets and spec look the same ( remarkably so)and it's 2.2 on .32 kernel so it could be very useful for debugging/building Blade Froyo.

So close and yet.....

Guest oh!dougal

Guest oh!dougal

Posted
Posted
Nah its the same one that people are working on at the moment, released 30/10

There's a lot of confusion around.

The San Francisco code has a claimed publication date of "8/23/2010" --- AUGUST ???

And there's Eclair code for the Chinese Blade with a date of "8/30/2010" ---- August again? And Eclair? I thought it was getting FroYo for its initial release ...

http://support.zte.com.cn/support/news/NewsMain.aspx and then click 'Service Bulletins'

Guest Bonzo1

Guest Bonzo1

Posted
Posted (edited)
There's a lot of confusion around.

The San Francisco code has a claimed publication date of "8/23/2010" --- AUGUST ???

And there's Eclair code for the Chinese Blade with a date of "8/30/2010" ---- August again? And Eclair? I thought it was getting FroYo for its initial release ...

http://support.zte.com.cn/support/news/NewsMain.aspx and then click 'Service Bulletins'

The 'ZTE-BLADE open source code for Android Eclair' on there has a 'last modified' date of 13/10/2010, the links are the same links as those under 'San Francisco/Tactile internet 2 open source code for Android Eclair'

Edited by Bonzo1
Guest ddotpatel

Guest ddotpatel

Posted
Posted
There's a lot of confusion around.

The San Francisco code has a claimed publication date of "8/23/2010" --- AUGUST ???

And there's Eclair code for the Chinese Blade with a date of "8/30/2010" ---- August again? And Eclair? I thought it was getting FroYo for its initial release ...

http://support.zte.com.cn/support/news/NewsMain.aspx and then click 'Service Bulletins'

Is there no chance one of them is froyo,... even though it is labled eclair?

The files on the ZTE site have been fixed. In doing so the news of ZTE’s first Android 2.2/Froyo slipped out. It’s called the V880.Our mole inside ZTE tipped us the wink that the files sitting on its support web site are the correct ones for the UK.
Guest deltronuk

Guest deltronuk

Posted
Posted
I spent some time looking at the source last night. ZTE used an out-of-tree driver for the wifi interface (ar6000) but didn't include the source. I believe it's part of the linux-sdio project. As far as I am aware they are obliged to release the source for this too.

Just some further information on this; the version of the code we're looking for is:

Atheros AR6002 olca driver version 2.2.1.103 maintainer [email protected]
This is the path it was compiled under: 
/home/tanbaihua/P729B/P729B_USR/android_b09/kernel/../vendor/zte/olca/host/os/linux/ar6000_drv.c

Guest David Horvath

Guest David Horvath

Posted
Posted

So we have the source of the kernel, and is no use?

Guest kallt_kaffe

Guest kallt_kaffe

Posted
Posted
So we have the source of the kernel, and is no use?

From my experience with Huawei the original AR6000.ko should work as long as you don't mess around to much with the config. However as it seems the kernel source released may not be 100% identical to the one used to compile the original kernel on the Orange San Francisco so I guess that may cause problems? I don't have a blade yet so I can only guess.

Guest rjm2k

Guest rjm2k

Posted
Posted (edited)

Since the launch in France still had 2.1, I asked ZTE if they were likely to launch the blade outside of china with 2.2 on, response is good but we will have to wait a while.....

"It will launch with 2.2 outside of China soon. But still not in Europe. "

and

"Hi , i'm so sorry that our R&D engineers are too busy to reply your issues that you mentioned in your early mails.

There is our harvest time now :rolleyes:

i will mail you if they have any progress.

The question your gived in your last mail that "but maybe just an indication if it will happen at all or whether 2.2 support is only ever going to be available in China?"

i assure you that we will lanch our Blade with Froyo around the world.

I will mail to this maillist when we release our Froyo Open Source Code as early as i can.

Pls take it easy :huh:

With best wishes

"

Edited by rjm2k
Guest Spooke

Guest Spooke

Posted
Posted

Again is anyone working on a ROM? Apart from Stephen :huh:, as people were asking for the source, they got it and nothing seems to have happened?

If someone is can I test a ROM? :rolleyes:

Guest rjm2k

Guest rjm2k

Posted
Posted (edited)
Can anyone confirm / give evidence that these are now the correct source files for 2.1

http://support.zte.com.cn/support/news/New...?newsId=1000322

Worth a look but unlikely, they updated the "blade" source a couple of weeks ago but it still wasn't correct. There was an announcement yesterday that they released the R750 source, but it points to the same "blade" source released a couple of weeks ago. I don't know, maybe they actually updated the source and announced it only for the R750 rather than other devices too but I'm sceptical about their ability to update their website.

I am in direct communication with ZTE, I would expect that they would have mentioned that they had updated the source.

An interesting and worrying implication of all of this is that ZTE have clearly little or no Source Code control and have in fact lost the code that was used to produce the Kernel for the SF as delivered to Orange. Any professional outfit should be able to quickly identify and re-build the source that was delivered into production no matter what has happened or been released since. Orange should also have been sent the Source for the kernel that they have sold to people.

Edited by rjm2k
Guest Maringer

Guest Maringer

Posted
Posted

It all seems rather shambolic to me.

Quite how a company which designs such high-tech devices (and does it pretty well in the case of the Blade) can be so lax with their website and/or keeping track of the source code for devices is really beyond me.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...

Important Information

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

  I accept