[ztebladeopensource] RE: [ztebladeopensource] 答复: [ztebladeopensource] wifi driver

  • From: "Morgan, Rob" <Rob.Morgan@xxxxxxxxxxxxxxx>
  • To: <ztebladeopensource@xxxxxxxxxxxxx>
  • Date: Mon, 15 Nov 2010 09:54:10 -0000

Hi Benny, someone posted some information about an incompatibility with the 
Blade and the Netgear DG834G v5 router, this seems specific to this router so 
I’m not sure if your developers can do anything if they don’t have one of them? 
  Are there any logs I can ask this person for to provide extra information for 
your developers?







Could this please be fed back to ZTE as a specific reproducible wifi anomaly? 

On disconnecting (whether because of sleep or manual disconnect) from the 
Netgear DG834G v5 the SF will not reconnect successfully unless (until) the 
router is rebooted. 
Phone wifi off/on is not sufficient to reconnect to that router. 
The problem seems to happen on every disconnect from that router. 

Its not about DG834G v5 compatibility. 
Its about the reconnection activity of the SF/Blade not working properly. 
The DG834G v5 gives a solid demonstration of where the problems lie. (The v5 is 
important. I know the v3 behaves differently.) 
If the cause of this were to be determined, it might incidentally be very 
helpful to the many many others suffering occasional failures to reconnect. 
This is a solid problem in the same area and might well shed some light on 
other reconnection difficulties.


From: ztebladeopensource-bounce@xxxxxxxxxxxxx 
[mailto:ztebladeopensource-bounce@xxxxxxxxxxxxx] On Behalf Of 
Sent: 15 November 2010 07:26
To: ztebladeopensource@xxxxxxxxxxxxx
Cc: ztebladeopensource@xxxxxxxxxxxxx; ztebladeopensource-bounce@xxxxxxxxxxxxx; 
Subject: [ztebladeopensource] 答复: [ztebladeopensource] wifi driver


Hello Rob. 

That's comes from our developers. for you issue about the  " Blade Sleeping " 

In most cases it's not a hardware limitation. It's about power consumption. 
Power consumption is a very important aspect of user experience. If you keep 
everything working when the phone goes to sleep, you will definitely suffer a 
battery drain. I think Android has provides you UI interfaces to control the 
behaviour of some hardware modules when the phone goes to sleep (if it makes 
sense to have that module on during sleeping). For example, you can have the 
bluetooth module working when the phone sleeps. But surely it will incur a 
power consumption penalty. It's up to you. For many other haredware modules, We 
don't see any reason to have them on when the phone is suspended. For example, 
the light sensor. What's the point of having light sensor working when the 
phone sleeps? For these modules, users don't have any chance to control their 
sleep behaviour. So technically you can do anything you like, surely at the 
risk of a shorter battery life. 

When USB cable is connected, the phone doesn't really sleep. Only the LCD and 
some other modules are turned off. Generally the LCD(including the backlight 
module) consumes most current on the phone. It's not necessary to go to deeper 
sleep other than turning off LCD because after turning off LCD, the USB cable 
supplies far more current than the amount that the phone consumes. There is no 
need to perform a full sleep. It might take a little bit more time to have the 
phone fully charged than in a full sleep. But it's not noticable. 

WIFI module is special. The chip has a limitation. It must be totally powered 
off and brought up again when the phone wakes up. 

Concerning the key issue you may have some misunderstanding. ZTE handsets 
highly conform with Android conventions. What keys can wake up the phone and 
what keys can turn on the screen? They are different things. You must first 
wake up the phone and then turn on the screen. 7k_handset.kl is only 
responsible for defining keys that can turn on the screen. You edit that file 
but it takes no effect because these keys you add are not even eligible to wake 
up the phone. Keys that can wake up the phone are defined by the manufacturer. 
Users are not encouraged to change it. 

Best regards.

Ben Ying
Smartphone System Department 
ZTE Corporation

Robert Morgan <robertmorgan@xxxxxxxxxxx> 
发件人:  ztebladeopensource-bounce@xxxxxxxxxxxxx 

2010-11-15 03:10 

请答复 给





[ztebladeopensource] wifi driver



Hi, I am still being asked the source to the wifi driver, you mentioned that 
you couldn't provide it because it was given to you by a 3rd party, can you 
please provide contact details for the 3rd party so that I can ask them about 
it?  Also, can you check the license that came with that source just in case it 
is open source in which case you should be ok to release it?



ZTE Information Security Notice: The information contained in this mail is 
solely property of the sender's organization. This mail communication is 
confidential. Recipients named above are obligated to maintain secrecy and are 
not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the originator of the 
message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

Other related posts: