Hi,
I bought a ZR 6 weeks ago, updated to android 4.3 with official Sony releases. It did not fall nor jump to water.
Everything ran fine, but it happens more and more that the screen suddenly turns black.
At the beginning, switching the phone to sleep and waking it up used to reactivate the screen; it tends not to work any more.
Under a low light the display can be guessed, but the screen itself brings absolutely no light.
I managed to enable the debug link under a low light, and here is what logcat shows me:
I/PowerManagerService( 772): Waking up from sleep...
I/QCOM PowerHAL( 772): Perflock released.
D/SurfaceFlinger( 320): Screen acquired, type=0 flinger=0xb7475150
D/qdhwcomposer( 320): hwc_blank: Unblanking display: 0
D/lights-module( 320): led 'backlight' opened 34 times
E/lights-utils( 314): Unable to write '1': Invalid argument
D/qdhwcomposer( 320): hwc_blank: Done unblanking display: 0
W/qdhwcomposer( 320): Excessive delay reading vsync: took 11728 ms
D/SurfaceControl( 772): Excessive delay in unblankDisplay() while turning screen on: 169ms​
I could find no information about this light-utils stuff.
What do I have to check or do?
Thanks a lot
--
Matthieu
Hmm, looks like the light does not respond on i2c, here's what the boot sequence logs when the brand's logo isn't even displayed:
I/illumination-service( 320): Started
E/lights-core( 320): assign_theme: No led 'backlight' found
I/leds-dogo( 320): lights_init
E/lights-lm3533_als( 320): intf_open: unable to open '/sys/bus/i2c/devices/0-0036//als_result' (-2)
E/lights-lm3533_als( 320): add_lm3533_als: Device '/sys/bus/i2c/devices/0-0036/' not found.
E/lights-utils( 320): Unable to open '/sys/bus/i2c/devices/0-0036///rt_rate_ms': No such file or directory
E/lights-utils( 320): Unable to open '/sys/bus/i2c/devices/0-0036///rt_rate_ms' (-1)
E/lights-lm3533( 320): set_rates: write error (No such file or directory)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-red/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-red/brightness' (-1)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-green/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-green/brightness' (-1)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-blue/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-blue/brightness' (-1)
E/lights-core( 320): LED 'backlight' is not of type 0
E/lights-core( 320): LED 'battery' is not of type 0
E/lights-core( 320): LED 'notifications' is not of type 0
E/lights-core( 320): LED 'button_rgb' is not of type 0
E/lights-core( 320): LED 'pattern_2' is not of type 0
E/lights-core( 320): LED 'pattern_3' is not of type 0
E/lights-core( 320): LED 'pattern_1' is not of type 0
E/lights-core( 320): LED 'attention' is not of type 0
E/lights-core( 320): LED 'button_2' is not of type 0
Any possibility to locate the hardware problem and fix it?
--
Matthieu
fropmontois said:
Hmm, looks like the light does not respond on i2c, here's what the boot sequence logs when the brand's logo isn't even displayed:
I/illumination-service( 320): Started
E/lights-core( 320): assign_theme: No led 'backlight' found
I/leds-dogo( 320): lights_init
E/lights-lm3533_als( 320): intf_open: unable to open '/sys/bus/i2c/devices/0-0036//als_result' (-2)
E/lights-lm3533_als( 320): add_lm3533_als: Device '/sys/bus/i2c/devices/0-0036/' not found.
E/lights-utils( 320): Unable to open '/sys/bus/i2c/devices/0-0036///rt_rate_ms': No such file or directory
E/lights-utils( 320): Unable to open '/sys/bus/i2c/devices/0-0036///rt_rate_ms' (-1)
E/lights-lm3533( 320): set_rates: write error (No such file or directory)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-red/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-red/brightness' (-1)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-green/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-green/brightness' (-1)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-blue/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-blue/brightness' (-1)
E/lights-core( 320): LED 'backlight' is not of type 0
E/lights-core( 320): LED 'battery' is not of type 0
E/lights-core( 320): LED 'notifications' is not of type 0
E/lights-core( 320): LED 'button_rgb' is not of type 0
E/lights-core( 320): LED 'pattern_2' is not of type 0
E/lights-core( 320): LED 'pattern_3' is not of type 0
E/lights-core( 320): LED 'pattern_1' is not of type 0
E/lights-core( 320): LED 'attention' is not of type 0
E/lights-core( 320): LED 'button_2' is not of type 0
Any possibility to locate the hardware problem and fix it?
--
Matthieu
Click to expand...
Click to collapse
Not sure about hardware problems but maybe it could be a software problem?? Have you tried factory resetting or reflashing the rom you are using?? Maybe that will fix. Also when your phone boots up and the Sony Logo shows is that bright?? OR is that really dark as well. Either way I would reflash the rom and see if the problem goes away otherwise contact Sony Support. Thanks!!
gurinderhans said:
Not sure about hardware problems but maybe it could be a software problem?? Have you tried factory resetting or reflashing the rom you are using?? Maybe that will fix. Also when your phone boots up and the Sony Logo shows is that bright?? OR is that really dark as well. Either way I would reflash the rom and see if the problem goes away otherwise contact Sony Support. Thanks!!
Click to expand...
Click to collapse
Yep, I did a factory reset. The boot logo is sometimes bright, but more often dark.
I've returned the phone to my local dealer, I'm expecting it back within 2-3 weeks.
Thanks
Matthieu
Related
Hi,
I have the standby mode disabled via cab or mortscript in the registration but it is not accepted by the system.
BattSuspendTimeout = 0
RegWriteDWord ("HKLM", "System\CurrentControlSet\Control\Power\Timeouts","BattSuspendTimeout",0)
Hmm can't you just set that in settings -> power?
hey does somebody knows a way to disable the auto rotation for the rhodium dialer...it's not listed in the whitelist.
Go to
[HKEY_CURRENT_USER\Software\HTC\HTCSENSOR\GSensor]
"AutoRotation"=dword and set from 1 to 0
cprog to the whitelist and then set to 0
or use gsen and cprog is the phone
the whitlist is for enabling the rotation and to disable the gsensor is not a real workaround.
Go to whitelist and delete key with value "dialog" and then dialer stops rotating, but "settings", when you inputing text in new message, etc with window name "dialog" stop rotating too...
Hello.
Before ask I did a lot of researching in 2 days but unfortunately it did not success.
The question:
An encrypted android phone will ask password when boot the system.
I have a xperia android phone and I set the language to english,
but on the password screen it always load language (chinese) from my sim card.
How can I set the specific language of this screen?
Basiclly I want inject the boot process.
Things I found:
1. Languages setting are stored in /data/property/persist.sys.language,
but it's on the decrypted fs,
on the password screen /data will mount to tmpfs so it won't be load from here.
2. Sim language are stored in prop gsm.sim.operator.iso-country and gsm.operator.iso-country,
and managed by telephonymanager,
can see some releated codes by searching PROPERTY_ICC_OPERATOR_ISO_COUNTRY and ACTION_SIM_STATE_CHANGED.
3. Then I patched /system/bin/mount and /system/bin/setprop,
let them call "setprop persist.sys.language us" after "realcommand [email protected]"
but looks like android not use these command during the boot process.
There's another way to do:
1. decompress and modify telephony-common.odex,
but it's signed, if I modify it the system wont boot.
2. modify kernel.sin and init.rc, require the factory reset so I didn't try yet,
I even not sure set persist.sys.language will work.
Log:
<quote>
D/PhoneStatusBarPolicy( 995): updateSimState for subscription :0
I/PowerManagerService( 734): Boot animation finished.
I/ActivityManager( 734): Config changes=1400 {1.0 ?mcc?mnc en_US ldltr sw360dp w360dp h567dp 320dpi nrml port finger -keyb/v/h -nav/h skinPackageSeq.1 s.6}
D/QcConnectivityService( 734): getMobileDataEnabled returning true
D/StatusBar.NetworkController( 995): In updateSimIcon simState= ABSENT
D/StatusBar.NetworkController( 995): refreshViews: Data not connected!! Set no data type icon / Roaming
D/PhoneStatusBarPolicy( 995): updateSimState for subscription :0
D/StatusBar.NetworkController( 995): In updateSimIcon simState= READY
D/StatusBar.NetworkController( 995): refreshViews: Data not connected!! Set no data type icon / Roaming
D/PhoneStatusBarPolicy( 995): updateSimState for subscription :0
D/StatusBar.NetworkController( 995): In updateSimIcon simState= UNKNOWN
D/StatusBar.NetworkController( 995): refreshViews: Data not connected!! Set no data type icon / Roaming
D/PhoneStatusBarPolicy( 995): updateSimState for subscription :0
D/StatusBar.NetworkController( 995): refreshViews: Data not connected!! Set no data type icon / Roaming
I/ActivityManager( 734): Config changes=3404 {1.0 ?mcc?mnc zh_CN ldltr sw360dp w360dp h567dp 320dpi nrml port finger -keyb/v/h -nav/h skinPackageSeq.1 s.7}
I/WifiService( 734): WifiService trying to set country code to cn with persist set to true
I/InputMethodManagerService( 734): Selected default: com.sonyericsson.textinput.chinese/.glue.InputMethodServiceGlue
I/ActivityManager( 734): Config changes=1403 {1.0 460mcc2mnc zh_CN ldltr sw360dp w360dp h567dp 320dpi nrml port finger -keyb/v/h -nav/h skinPackageSeq.1 s.8}
W/InputMethodManagerService( 734): Illegal subtype state: old subtype = null, new subtype = null
D/QcConnectivityService( 734): getMobileDataEnabled returning true
D/StatusBar.NetworkController( 995): refreshViews: Data not connected!! Set no data type icon / Roaming
D/StatusBar.NetworkController( 995): refreshViews: Data not connected!! Set no data type icon / Roaming
D/StatusBar.NetworkController( 995): In updateSimIcon simState= UNKNOWN
</auote>
If you have any experience about it please help me, thanks !
Resolved, use the deodex way.
Just follow http://forum.xda-developers.com/galaxy-s2/themes-apps/how-to-manually-deodex-odex-t1208320 and modify two location:
let defaultLanguageForMcc return "en", and let countryCodeForMcc return "us".
I want to create a task for sending my location to some specific contact on whatsapp (when my battery falls below a certain value).
I have created and tested just 1 line yet: Launch app > Whatsapp (long press) > Location picker 2
All options/ data have been left blank. It gives the following error on execution. Any clue?
12.54.32/Utils startActivityWrapper: unexpected exception: java.lang.SecurityException: Permission Denial: starting Intent { act=android.intent.action.MAIN flg=0x30200004 cmp=com.whatsapp/.LocationPicker2 } from ProcessRecord{56f967f 32183:net.dinglisch.android.taskerm/u0a94} (pid=32183, uid=10094) not exported from uid 10069
12.54.32/E Launch App: failed to launch com.whatsapp.LocationPicker2.
Click to expand...
Click to collapse
I've tried using both Location Picker as well as Location picker 2, but to no avail.
I will try and figure out how to select the contact using Auto Input or some other app, but I'm not even able to get past the 1st line still.
Hello,
I would like to create a task, that would popup a snackbar, with some music apps after I connect headphones.
My profile is like:
if ( headphones had been connected & screen is on )
then show popup ONCE
I have almost finished doing it, yet I have one obstacle that I do not know how to overcome. Headphones (headset) is being detected as a state, so it is continuous. I would like to use it more like an event.
By having it like as a state this popup shows everytime I unlock my screen, yet I would like it to be only once.
To be clear, screen on is needed in case I want to use other app than Poweramp, which automatically plays music after I connect headphone. That way, I would get the most of both worlds
Any help?
Export task to xml and put here
You can ad some "if".
Show popup If %Plugin = 0
And as last step add Enter task - set %Plugin to 1
Exit task: set %Plugin to 0
or something similar.
frrancuz. said:
Export task to xml and put here
You can ad some "if".
Show popup If %Plugin = 0
And as last step add Enter task - set %Plugin to 1
Exit task: set %Plugin to 0
or something similar.
Click to expand...
Click to collapse
Well, I thought so as well. Unfortunately, when screen goes off, this means that exit task is being triggered.
@domi.nos
Try
http://fii.cz/qmpcmdv
it is very simple, to show you how it works.
frrancuz. said:
@domi.nos
Try
http://fii.cz/qmpcmdv
it is very simple, to show you how it works.
Click to expand...
Click to collapse
Thanks for your help. I just solved it on my own, it turned out as if I set both Screen and Headphones State as triggers, this popups show all the time, but after moving Screen State to be checked in the task, it just works
Instead of opening a window when you plug your headphones, you could add audio widgets and shortcuts to one of you homescreens and then when you plug your headphones it jumps to that homescreen.
When you unplug them, you could set it to jump to your main homescreen.