Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 2 days, 17 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 2 days, 18 hrs ago -
Maemo repository (3)
to Community by torsen - 3 days, 10 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 4 days, 7 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 5 days, 14 hrs ago - more...
 |
|
2012-03-29
, 21:49
|
|
Posts: 857 |
Thanked: 1,206 times |
Joined on Dec 2009
@ Chertsey in the Thames, United Kingdom
|
#2
|
Back up the device and re-flash
__________________
Proud owner of Jolla phone, number 274.
Proud owner of Jolla phone, number 274.
|
|
2012-03-30
, 19:22
|
|
Posts: 9 |
Thanked: 6 times |
Joined on Mar 2012
@ Germany
|
#3
|
Hmm,
seems that it is not a common issue. I'd hoped that someone would have a more differentiated advice, so let's see. Anyhow, I thought of a similar approach as I am running out of ideas.
So, does it mean a 'real re-flashing' following the hot rated thread here or might a reset from the phone's menue will do the job?
Thanks
seems that it is not a common issue. I'd hoped that someone would have a more differentiated advice, so let's see. Anyhow, I thought of a similar approach as I am running out of ideas.
So, does it mean a 'real re-flashing' following the hot rated thread here or might a reset from the phone's menue will do the job?
Thanks
|
|
2012-05-18
, 19:01
|
|
Posts: 3 |
Thanked: 1 time |
Joined on Feb 2012
@ Tampere, Finland
|
#4
|
I started having the same problems. The display does not switch off anymore after idling. Any new ideas on how to solve this? Gconf? Some ini file?
No idea whether this is related but I updated the maps in Maps application yesterday. The update seemed to leave the screen on. I manually switched the screen off with the power button but when I unlocked the phone again, the update and Maps had stopped. So I had to update again and leave phone unlocked and let it update. So could this update have left my N9 in some invalid state?
Thanks already for the answers!
No idea whether this is related but I updated the maps in Maps application yesterday. The update seemed to leave the screen on. I manually switched the screen off with the power button but when I unlocked the phone again, the update and Maps had stopped. So I had to update again and leave phone unlocked and let it update. So could this update have left my N9 in some invalid state?
Thanks already for the answers!
|
|
2012-05-18
, 19:33
|
|
Posts: 9 |
Thanked: 6 times |
Joined on Mar 2012
@ Germany
|
#5
|
Hi,
unfortunately the only thing that helped me out was the stupid thing to reset my phone. I checked a lot of things and also the suspicion that a particular app or tool I installed might have caused the problem. But meanwhile I have "manually restored" the old state and bunch of apps I also had before and the problem did not show up again.
So, would be cool to know at least afterwards what was the problem, so anyone having an idea or a hint is highly welcome ;-)
Good luck and best regards.
unfortunately the only thing that helped me out was the stupid thing to reset my phone. I checked a lot of things and also the suspicion that a particular app or tool I installed might have caused the problem. But meanwhile I have "manually restored" the old state and bunch of apps I also had before and the problem did not show up again.
So, would be cool to know at least afterwards what was the problem, so anyone having an idea or a hint is highly welcome ;-)
Good luck and best regards.
 |
|
2012-05-18
, 19:34
|
|
Moderator |
Posts: 2,622 |
Thanked: 5,447 times |
Joined on Jan 2010
|
#6
|
I think that reflashing has more chances to solve your problem. That reset switch will kill more of your data, and I am not sure it will reset everything. Maemo doesn't have a ROM partition with the factory settings like symbian does. Reflashing restores the OS to factory, but your application settings and data stay intact (unless you flash MyDocs too)
EDIT: A minute too late...
Happy you solved it.
EDIT: A minute too late...
Happy you solved it.
__________________
Proud coding competition 2012 winner: ρcam
My other apps: speedcrunch N9 N900 Jolla –– contactlaunch –– timenow
Nemo UX blog: Grog
My website: qwazix.com
My job: oob
Proud coding competition 2012 winner: ρcam
My other apps: speedcrunch N9 N900 Jolla –– contactlaunch –– timenow
Nemo UX blog: Grog
My website: qwazix.com
My job: oob
|
|
2012-05-18
, 19:38
|
|
Posts: 9 |
Thanked: 6 times |
Joined on Mar 2012
@ Germany
|
#7
|
Originally Posted by qwazix
I was not so aware about the differences of re-flashing vs. re-setting but at some point I think I feel even saver to correct the problem whatever it was - although it was some more work ...
Reflashing restores the OS to factory, but your application settings and data stay intact (unless you flash MyDocs too)
Originally Posted by qwazix
Like it, that this forum is well lived !
EDIT: A minute too late...
Happy you solved it.
|
|
2012-05-19
, 06:36
|
|
Posts: 3 |
Thanked: 1 time |
Joined on Feb 2012
@ Tampere, Finland
|
#8
|
Thanks for the info. I'll try too seek for some easier fix first but if I can't find one then I guess I'll go with the re-flash. Never done that so the threshold to do that is a bit high 
Any help/tips are still welcome about the problem!
Any help/tips are still welcome about the problem!
|
|
2012-05-21
, 18:50
|
|
Posts: 3 |
Thanked: 1 time |
Joined on Feb 2012
@ Tampere, Finland
|
#9
|
SOLVED!
The problem was that /system/osso/dsm/display/inhibit_blank_mode GConf value was invalid. It had value 3 (Inhibit dimming/blanking) instead of the valid value 0 (No display blanking inhibit).
So the fix was to run this command in terminal:
I guess using GConfik app works too but it seemed to change the type of the property from Int to String (so I guess terminal command is safer).
The solution was found by googling what each relevant "display" gconf property meant and this came up: http://www.gossamer-threads.com/list...rs/61201#61201
The problem was that /system/osso/dsm/display/inhibit_blank_mode GConf value was invalid. It had value 3 (Inhibit dimming/blanking) instead of the valid value 0 (No display blanking inhibit).
So the fix was to run this command in terminal:
Code:
gconftool -s --type int /system/osso/dsm/display/inhibit_blank_mode 0
The solution was found by googling what each relevant "display" gconf property meant and this came up: http://www.gossamer-threads.com/list...rs/61201#61201
| The Following User Says Thank You to terohe For This Useful Post: | ||
|
|
2012-08-12
, 23:22
|
|
Posts: 428 |
Thanked: 226 times |
Joined on Dec 2010
@ Philippines
|
#10
|
This worked for me.
I am curious as to what causes this to happen (low-power screen/display no longer blanks out when the sensor is covered). Strange. By the way I only experience this whenever I have NITDroid (Alpha 3) installed. Could that be causing it?
In the link you provided, one of them said that:
There is another approach in the same thread where the recommendation is to do:
One of them responded, saying that:
What are your thoughts on this?
I am curious as to what causes this to happen (low-power screen/display no longer blanks out when the sensor is covered). Strange. By the way I only experience this whenever I have NITDroid (Alpha 3) installed. Could that be causing it?
In the link you provided, one of them said that:
On 11/05/2010 12:54, David Weinehall wrote:
> An (undocumented) alternative is:
>
>>Code:gconftool -s --type int /system/osso/dsm/display/inhibit_blank_mode 3
> Replace the 3 for whatever inhibit mode you want:
>
> 0 -- No display blanking inhibit
> 1 -- Inhibit dimming/blanking if charger is connected
> 2 -- Allow dimming, but inhibit blanking if charger is connected
> 3 -- Inhibit dimming/blanking
> 4 -- Allow dimming, but inhibit blanking
Try:
instead (every 30s should be enough).Code:dbus-send --system --type=method_call --print-reply --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.req_display_blanking_pause
And that'll change the user setting, which might not be a good idea from
an application developer pov.
I might have done something stupid by tweaking my N9 (PR1.2 30.2012.07-1_PR_001), but can not reveal what is wrong and also looked through a lot of threads but have not found a hint, maybe someone may help me:
Since a few days my display will not shut off, power down anymore although set to go to sleep after 30sec. I tried all other time settings already, uninstalled the last added apps, changed developper mode on and off and much more things. Rebooting did not help either.
Please help, I currently have to switch off the display everytime manually otherwise the battery will be drained quickly. Setting the "standby screen" or or off does not affect the situation, also setting the energy saver mode to on/off/auto does not solve the problem.
I hope someone has some advice, your help is much apperciated.
Thanks & Regards,
Timm
Last edited by TimmW; 2012-03-29 at 19:16.