0B10 Testbed for dev research purposes.

[Guest Society]

Some examples of 0B10 devices seem to exhibit problems after flashing such as the touch capability of the screen not always being active on boot. Mine is one of these.

It has been suggested in another thread that there may, for example, have been a hardware change which is responsible for this erratic behaviour but researching a solution would, in any case, need a knowledgeable dev to get their hands on a device which exhibits the undesired characteristics.

If any such dev has the time and inclination to address this problem then I would make my contribution by making my OSF-UK 0B10 available on loan for this purpose. Anyone interested?

[Guest oh!dougal]

Handsome offer I'm sure, but probably looking at your phone's standard firmware will likely provide the clues.

Which LCD is your phone fitted with?

http://android.modaco.com/content/zte-blad...-lcd-is-better/

[Guest Society]

Handsome offer I'm sure, but probably looking at your phone's standard firmware will likely provide the clues.

Which LCD is your phone fitted with?

http://android.modaco.com/content/zte-blad...-lcd-is-better/

I was so focused on following flash instructions absolutely precisely that I didn't take the obvious preliminary step of taking a backup of stock ROM. Is there a way to identify type of TFT if not using stock ROM?

Tried JJ9 & FLB-r10b which were both erratic in activating touch and currently with SS-RLS2 which also failed to boot with touch activated the first time but seems to now be behaving as one would hope! I've even put the back on now I don't need to keep pulling the battery until I get a successful boot.

Trying Swedish Spring was subsequent to #39 in this thread:

http://android.modaco.com/content-page/334...uk-b10/page/20/

in which I noted the Product Code per my OrangeUK retail box is OZTN1122

[Guest kozlovda]

Handsome offer I'm sure, but probably looking at your phone's standard firmware will likely provide the clues.

Which LCD is your phone fitted with?

http://android.modaco.com/content/zte-blad...-lcd-is-better/

Based on last reports it's always OZTN1122, which is:

Color: Grey

Display: LEAD or TRULY

Label: ZTE P729B

Product Code: OZTN1122

Almost sure that neither IMEI nor EAN barcode mean nothing in this case. It's all about product code and corresponding touchscreen module - see this post

This is not a hardware "bug" since reverting back to original ROM (backed up) revives touchscreen. It's rather about drivers...

Also some people reported that with some ROMs they could saw ".." highlited dots at the left bottom corner of screen.

Btw, looking for backup files from original stock device... Bypassed backing up mine... to my regret Were kindly provided by chig00.

UPD reason: provided links to stock ROM backup image

Edited March 25, 2011 by kozlovda

[Guest ronc2000]

I think Product Code:

OZTN1122 = grey

OZTN1120 = white

[Guest sambartle]

I was so focused on following flash instructions absolutely precisely that I didn't take the obvious preliminary step of taking a backup of stock ROM. Is there a way to identify type of TFT if not using stock ROM?

Hook it up with USB,

run: ADB shell (from the SDK)

and then run this in the shell: cat /proc/kmsg

Sleep the phone and resume it and look in the output for this:

<4>[03-25 12:25:35.710540] [7: suspend]lcdc_panel_off , g_lcd_panel_type is 1(1 LEAD. 2 TRULY. 3 OLED. )

The number before the brackets corrosponds to the LCD Panel type.. LEAD in this example

i'm sure theres an easier way.. but this works :D

It seems likely that the touch controller model is actually what you need to know though and not the panel type (or is it part of the LCD on phones?)

Edited March 25, 2011 by sambartle

[Guest sambartle]

<deleted - stupidity on my part>

Edited March 25, 2011 by sambartle

[Guest the_fox]

Same issue here, but it's a OBE_P729BV1.0.0B02 (from Belgium, Mobistar)

info:

LCD:

IC: NT35580

Glass: Lead.

TouchScreen:

module: synaptics

i2c: 0x22

IC type: 2000 series

firmware: TM1541

module: synaptics + TPK

[Guest EazyDuz]

Doesnt seem like anyone can work this problem out. Mine doesnt seem to do it if i hold the up vol button while it turns on, or if i have pattern lock on.

Will probably get a new phone (Not a Blade) in the next month or so if this cant be fixed.

[Guest mario85]

Same issue here, but it's a OBE_P729BV1.0.0B02 (from Belgium, Mobistar)

info:

LCD:

IC: NT35580

Glass: Lead.

TouchScreen:

module: synaptics

i2c: 0x22

IC type: 2000 series

firmware: TM1541

module: synaptics + TPK

Same problem and same specs here with ZTE_P729BV1.0.0B02 (Wind, Greece). We're waiting for an official 2.2 upgrade the following days. Could this help find out what the problem is (or perhaps the same boot.img can work for the other blades too)?