Jump to content

Recommended Posts

Guest carkev
Posted (edited)

To be absolutely sure which screen type you have:

Dial *983*24474636# in the dialer.

(refer to “Glass” to determine which screen category your phone falls under)

OLED

LCD Information:

IC: TL2796

Glass: Samsung

TFT/LCD

IC: NT35580

Glass: LEAD OR

Glass: TRULY

So to conclude if you have Glass:Samsung then it is OLED (No ifs and buts)

I have been very lucky here ... the one I got from Orange shop in early Dec was Oled,

then I bought another from them for my wife in late Dec ... sadly this one was TFT,

BUT

it also had very poor reception (bad antenna) and Orange kindly replaced it Jan 29th ... with a brand new/boxed Oled !!

so they do still have some stock around

Edited by carkev
Guest Arr Too
Posted

Note: that dialler code requires ChiperTest.apk which has been removed from some ROMs. And it's easier to remember as: *ZTE*CHIPINFO#

Guest Phoenix Silver
Posted

LCD Information :

nothing :unsure:

other infos work

Guest carkev
Posted
LCD Information :

nothing :unsure:

other infos work

I'm not quite sure what you are saying here .. (LCD nothing ?)

my phone is all original and what I said works fine,

as such my post was meant to be helpful to new SanFran/Andriod users like myself.

is it that some rooted phones don't have the standard dialler, so my tip would be of no use to them ?

if so I'll keep my mouth shut in future.

Guest Phoenix Silver
Posted

screen display this

ChiperTest

LCD Information:

TouchScreen Information:

touchscreen module

name :synaptics

.

.

.

.

nothing under LCD Information

Guest Arr Too
Posted

Try it on your stock ROM? There may be new/different options that some ChiperTests don't understand, I suppose.

Guest Phoenix Silver
Posted
Try it on your stock ROM? There may be new/different options that some ChiperTests don't understand, I suppose.

not very important not enough to backup / restore stock / froyo roms :unsure:

Guest Arr Too
Posted
not very important not enough to backup / restore stock / froyo roms :unsure:

Although if you have a copy of your stock ROM (Orange France's Internet Tactile II?) then Seb is still waiting for one.

Guest gambieter
Posted (edited)

On Finnish Fillyjonk RLS4 I get a Force Close of Dialler, and a request for my PINcode of the SIMcard.

(OLED)

Edit: probably due to lack of Chipertest.apk in that ROM

Edited by gambieter
Guest Phoenix Silver
Posted
Although if you have a copy of your stock ROM (Orange France's Internet Tactile II?) then Seb is still waiting for one.

made :unsure:

P.S. : for gambieter just adb push chipertest.apk in /system/app in custom rom

Guest Krinyo
Posted

If You see backlight on the screen edges (look at low angle), the You have TFT. If not, it's OLED.

Simple. :unsure:

Guest Phoenix Silver
Posted
If You see backlight on the screen edges (look at low angle), the You have TFT. If not, it's OLED.

Simple. B)

i know mine is a tft

just strange nothing displayed under LCD info

(perhaps because of japanese rom :unsure: )

Guest Arr Too
Posted
just strange nothing displayed under LCD info

(perhaps because of japanese rom :unsure: )

Japanese ROM has a different arrangement of the Engineering Mode stuff. What do you get if you try this:

adb shell cat /proc/msm_lcd

Guest Phoenix Silver
Posted
Japanese ROM has a different arrangement of the Engineering Mode stuff. What do you get if you try this:
adb shell cat /proc/msm_lcd

phoenix@phoenix:~/Downloads/Android/Roms$ sudo ./adb shell cat /proc/msm_lcd

0

Guest Arr Too
Posted
0

Cor! That's not an acceptable answer! :unsure: Wonder what sets that value? And why yours is invalid? New screen that they've just not added the option for?

Guest Phoenix Silver
Posted
Cor! That's not an acceptable answer! :unsure: Wonder what sets that value? And why yours is invalid? New screen that they've just not added the option for?

msm_lcd

msm_memory

msm_pm_stats

msm_sdcc

all zero B)

Guest Arr Too
Posted

Goodness me -- what have you done to your poor little Blade?!?!

Guest Phoenix Silver
Posted (edited)
Goodness me -- what have you done to your poor little Blade?!?!

lol

but it works pretty well :unsure:

we should see if other jellyfish's users have the same thing

Edited by Phoenix Silver
Guest Arr Too
Posted (edited)

I'm using the excellent Jellyfish! (Release 2)

# cat /proc/msm_lcd

40
# cat /proc/msm_memory

SAMSUNG 4G NAND
# cat /proc/msm_pm_stats

Clocks against last TCXO shutdown:

Last power collapse voted for TCXO shutdown


idle-request:

  count: 2114490

  total_time: 40859.598229609

   <	 0.000062500:	7983 (0-61666)

   <	 0.000250000:   23125 (63333-249999)

   <	 0.001000000:   90980 (251666-999999)

   <	 0.004000000:  288666 (1001666-3999999)

   <	 0.016000000:  743570 (4001666-15999999)

   <	 0.064000000:  882596 (16001666-63998333)

   <	 0.256000000:   67906 (64001666-255998333)

   <	 1.024000000:	9664 (256001666-609966666)

   <	 4.096000000:	   0 (0-0)

  >=	 4.096000000:	   0 (0-0)

idle-spin:

  count:	 207

  total_time: 0.001998328

   <	 0.000062500:	 207 (1666-36667)

   <	 0.000250000:	   0 (0-0)

   <	 0.001000000:	   0 (0-0)

   <	 0.004000000:	   0 (0-0)

   <	 0.016000000:	   0 (0-0)

   <	 0.064000000:	   0 (0-0)

   <	 0.256000000:	   0 (0-0)

   <	 1.024000000:	   0 (0-0)

   <	 4.096000000:	   0 (0-0)

  >=	 4.096000000:	   0 (0-0)

idle-wfi:

  count: 2114283

  total_time: 17957.516677983

   <	 0.000062500:  365131 (6666-61667)

   <	 0.000250000:  361659 (63333-249999)

   <	 0.001000000:  334124 (250000-999999)

   <	 0.004000000:  129774 (1000000-3999999)

   <	 0.016000000:  315297 (4000000-15999999)

   <	 0.064000000:  608294 (16000000-59944997)

   <	 0.256000000:	   2 (119964993-219956652)

   <	 1.024000000:	   2 (292926658-329944978)

   <	 4.096000000:	   0 (0-0)

  >=	 4.096000000:	   0 (0-0)

idle-standalone-power-collapse:

  count:	   0

  total_time: 0.000000000

   <	 0.000062500:	   0 (0-0)

   <	 0.000250000:	   0 (0-0)

   <	 0.001000000:	   0 (0-0)

   <	 0.004000000:	   0 (0-0)

   <	 0.016000000:	   0 (0-0)

   <	 0.064000000:	   0 (0-0)

   <	 0.256000000:	   0 (0-0)

   <	 1.024000000:	   0 (0-0)

   <	 4.096000000:	   0 (0-0)

  >=	 4.096000000:	   0 (0-0)

idle-failed-standalone-power-collapse:

  count:	   0

  total_time: 0.000000000

   <	 0.000062500:	   0 (0-0)

   <	 0.000250000:	   0 (0-0)

   <	 0.001000000:	   0 (0-0)

   <	 0.004000000:	   0 (0-0)

   <	 0.016000000:	   0 (0-0)

   <	 0.064000000:	   0 (0-0)

   <	 0.256000000:	   0 (0-0)

   <	 1.024000000:	   0 (0-0)

   <	 4.096000000:	   0 (0-0)

  >=	 4.096000000:	   0 (0-0)

idle-sleep:

  count:	   0

  total_time: 0.000000000

   <	 0.000062500:	   0 (0-0)

   <	 0.000250000:	   0 (0-0)

   <	 0.001000000:	   0 (0-0)

   <	 0.004000000:	   0 (0-0)

   <	 0.016000000:	   0 (0-0)

   <	 0.064000000:	   0 (0-0)

   <	 0.256000000:	   0 (0-0)

   <	 1.024000000:	   0 (0-0)

   <	 4.096000000:	   0 (0-0)

  >=	 4.096000000:	   0 (0-0)

idle-failed-sleep:

  count:	   0

  total_time: 0.000000000

   <	 0.000062500:	   0 (0-0)

   <	 0.000250000:	   0 (0-0)

   <	 0.001000000:	   0 (0-0)

   <	 0.004000000:	   0 (0-0)

   <	 0.016000000:	   0 (0-0)

   <	 0.064000000:	   0 (0-0)

   <	 0.256000000:	   0 (0-0)

   <	 1.024000000:	   0 (0-0)

   <	 4.096000000:	   0 (0-0)

  >=	 4.096000000:	   0 (0-0)

idle-power-collapse:

  count:	   0

  total_time: 0.000000000

   <	 0.000062500:	   0 (0-0)

   <	 0.000250000:	   0 (0-0)

   <	 0.001000000:	   0 (0-0)

   <	 0.004000000:	   0 (0-0)

   <	 0.016000000:	   0 (0-0)

   <	 0.064000000:	   0 (0-0)

   <	 0.256000000:	   0 (0-0)

   <	 1.024000000:	   0 (0-0)

   <	 4.096000000:	   0 (0-0)

  >=	 4.096000000:	   0 (0-0)

idle-failed-power-collapse:

  count:	   0

  total_time: 0.000000000

   <	 0.000062500:	   0 (0-0)

   <	 0.000250000:	   0 (0-0)

   <	 0.001000000:	   0 (0-0)

   <	 0.004000000:	   0 (0-0)

   <	 0.016000000:	   0 (0-0)

   <	 0.064000000:	   0 (0-0)

   <	 0.256000000:	   0 (0-0)

   <	 1.024000000:	   0 (0-0)

   <	 4.096000000:	   0 (0-0)

  >=	 4.096000000:	   0 (0-0)

suspend:

  count:	 514

  total_time: 152572.391601566

   <	 1.000000000:	   0 (0-0)

   <	 4.000000000:	  24 (1995544433-3996520997)

   <	16.000000000:	 173 (4578613281-15997283935)

   <	64.000000000:	 105 (16995330810-62997497559)

   <   256.000000000:	  29 (64997192383-221999816895)

   <  1024.000000000:	 183 (259627655029-899012695313)

   <  4096.000000000:	   0 (0-0)

   < 16384.000000000:	   0 (0-0)

   < 65536.000000000:	   0 (0-0)

  >= 65536.000000000:	   0 (0-0)

failed-suspend:

  count:	   0

  total_time: 0.000000000

   <	 0.000062500:	   0 (0-0)

   <	 0.000250000:	   0 (0-0)

   <	 0.001000000:	   0 (0-0)

   <	 0.004000000:	   0 (0-0)

   <	 0.016000000:	   0 (0-0)

   <	 0.064000000:	   0 (0-0)

   <	 0.256000000:	   0 (0-0)

   <	 1.024000000:	   0 (0-0)

   <	 4.096000000:	   0 (0-0)

  >=	 4.096000000:	   0 (0-0)

not-idle:

  count: 2114490

  total_time: 4707.711114649

   <	 0.000062500:  499374 (3333-61668)

   <	 0.000250000:  547735 (63333-249999)

   <	 0.001000000:  546686 (250000-999999)

   <	 0.004000000:  442064 (1000000-3999999)

   <	 0.016000000:   63877 (4000000-15999999)

   <	 0.064000000:	8368 (16003333-63981668)

   <	 0.256000000:	3954 (64009999-255886668)

   <	 1.024000000:	2070 (256266672-1023920005)

   <	 4.096000000:	 325 (1024351677-3985755006)

  >=	 4.096000000:	  37 (4217135002-14947010008)
# cat /proc/msm_sdcc

off

Edited by Arr Too
Guest Anton2k
Posted

I have a tft thought it was an oled i was getting but wasnt..... can u change the screen from tft to oled? not that the tft is bad its good quality screen

Guest gambieter
Posted
P.S. : for gambieter just adb push chipertest.apk in /system/app in custom rom

Don't need it, I know I have OLED :unsure: (bought it in October)

Posted

on mine it says LCD information:/proc/mam_lcdisn't exsit or you hasn't the read authority!

WTF???

Guest Arr Too
Posted
on mine it says LCD information:/proc/mam_lcdisn't exsit or you hasn't the read authority!

That's two people with phones that have that bit messed up! Is yours a plain Orange SanFran? I wonder which bit sets up this data? And what might have wiped/changed it? Could it be a sign of a refurb?

Guest Mike_P
Posted

Hmm more confusion from the hi-tech 'solution'. :unsure:

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.