search

younglo / cyanogenmod4milestone

Automatically exported from code.google.com/p/cyanogenmod4milestone
0 stars 0 forks source link

Screen does not light up after sleep mode, but touch screen works #498

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Click the power button to get back from sleep mode.
2. The screen will not appear, but if you try to use it 'blindly' you'll notice 
that the touch screen is actually working. For example, try to call the phone 
and move the finger to the right to answer, the call will be answered.
3.

What is the expected output? What do you see instead?
The screen should always appear when you get back from the sleep mode.

What version of the product are you using?
CM7-RC4-11.04.10

Please provide any additional information below.

Original issue reported on code.google.com by die...@gmail.com on 12 Apr 2011 at 1:02

GoogleCodeExporter commented 8 years ago 
Correct version: 0.08-11.04.10 RC4.1
The only solution is removing the battery to restart the phone.

Original comment by die...@gmail.com on 12 Apr 2011 at 1:04

GoogleCodeExporter commented 8 years ago 
Do you have the DSI workaround option enabled or disabled?

When the screen is frozen this way, are you able to connect to phone via adb 
and get logcat and dmesg output?

Original comment by kabal...@gmail.com on 12 Apr 2011 at 2:50

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
DSI is enabled.
When the problem shows up again I'll try to connect it to the computer and 
check adb and logcat in Eclipse.

Original comment by die...@gmail.com on 12 Apr 2011 at 3:02

GoogleCodeExporter commented 8 years ago 
When i have it, i can blindly unlock and restart the Phone, if i remember what 
buttons to press blindly. So it really has a working system underneath.
I had it with the DSI workaround and without it.

Original comment by ben.kell...@gmail.com on 18 Apr 2011 at 8:19

GoogleCodeExporter commented 8 years ago 
Please test the latest CM 7.0.0 release 0.08-11.04.18 and report.
This revert possibly fixes this issue - 
https://github.com/nadlabak/android_frameworks_base/commit/fceeb1f609223d5b16fc7
649dcefe1fdcb9997a2

Original comment by kabal...@gmail.com on 18 Apr 2011 at 9:54

GoogleCodeExporter commented 8 years ago 
I can confirm the issue with CM 7.0.0 0.08-11.04.18 on HTC Hero.

Original comment by vas...@gmail.com on 18 Apr 2011 at 11:35

GoogleCodeExporter commented 8 years ago 
may I point out that this is the issue tracker for MILESTONE? HTC Hero has it's 
own forums.

Original comment by amon...@gmail.com on 18 Apr 2011 at 9:08

GoogleCodeExporter commented 8 years ago 
With the new Version 11.04.18 there is still the same issue but for me only 
when I recieve SMS or I get Messages through WhatsApp...

Original comment by mgvin...@googlemail.com on 19 Apr 2011 at 7:12

GoogleCodeExporter commented 8 years ago 
experienced this issue with 11.04.18 (not 11.04.18b, but that's not supposed to 
fix this if I'm not mistaken). I received an SMS and a Google Talk message (LED 
was blinking 2 colors, that's how I know).

Original comment by bart.crijns on 20 Apr 2011 at 12:39

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Bug is still present in CM7 0.08-11.04.18b 7.0.0 :(

Original comment by Mircosal...@gmail.com on 21 Apr 2011 at 4:50

GoogleCodeExporter commented 8 years ago

Original comment by kabal...@gmail.com on 24 Apr 2011 at 8:51

GoogleCodeExporter commented 8 years ago 
Bug still present in CM7 for Milestone.

Original comment by FelpetoF...@gmail.com on 26 Apr 2011 at 6:02

GoogleCodeExporter commented 8 years ago 
bug still present in 7.1.0, 5.03. I got a sms shortly before, maybe that info 
helps you. Wanted to switch phone on to read it.

Original comment by fenr...@gmail.com on 4 May 2011 at 2:11

GoogleCodeExporter commented 8 years ago 
hardly anyone seems to know that, but you can trigger a reboot by pressing 
left-shift+right-alt+del on the hw keyboard ;-)

no need for a battery pull..

Original comment by pontome...@gmail.com on 4 May 2011 at 4:20

GoogleCodeExporter commented 8 years ago 
Experienced same issue in 11.04.18b. my dmesg has a ton of lines like this:

<4>[56219.636352] Mailbox full trying again count 3 

Don't know if that is relevant but...

Original comment by raubvo...@gmail.com on 4 May 2011 at 5:50

Attachments:

GoogleCodeExporter commented 8 years ago 
I had this problem with official 2.1. With 0.08-11.04.05 RC4 and 0.08-11.04.18b 
7.0.0 i have't got this problem. Now with 7.1.0-RC0-11.05.03 got once.

Any suggestion for apk which saves logs without user interaction and can be 
used by quicklauhes?

Original comment by jik...@gmail.com on 5 May 2011 at 8:35

GoogleCodeExporter commented 8 years ago 
I can confirm the issue with CM on Milestone

Original comment by gian.sal...@gmail.com on 6 May 2011 at 12:20

GoogleCodeExporter commented 8 years ago 
i confirm the bug is still present in CM7.1.0 RC3 11.05.15

Original comment by divi...@gmail.com on 16 May 2011 at 2:07

GoogleCodeExporter commented 8 years ago 
I can confirm this is still present in CM7.1.0 RC3 11.05.15 as well.
Just had it after playing music, tried to turn screen on - Touch is responsive, 
phone gets calls, but screen won't turn on.

Original comment by meiri.ta...@gmail.com on 17 May 2011 at 5:39

GoogleCodeExporter commented 8 years ago 
Same here. Can't reproduce it, but it happens very frequently.
CM7.1.0 RC3 11.05.15

Original comment by c.schmei...@gmail.com on 19 May 2011 at 1:20

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I still get this in 7.1.0 RC3, but contrary to other reports, my screen works 
normally again if I switch the screen off (well, it's off already of course) 
and on again with 2 successive short presses on the power key. No reboot 
necessary for me.

Original comment by bart.crijns on 19 May 2011 at 1:28

GoogleCodeExporter commented 8 years ago 
Can confirm that I have just experienced this on CM7.1.0 RC3 11.05.15.
Will test bart.crijns 'double press' technique when this happens again.

Original comment by wilko...@gmail.com on 20 May 2011 at 10:40

GoogleCodeExporter commented 8 years ago 
What is strange is that I had this issue happen only once or twice in the last 
4 months (=since the first CM7 build)...
What does it trigger so often for some? Overclock/vsel (125MHz?), governor? 
Something else?
I would surely need to see both main and kernel logs:
/cache/logger/AOL_main.ap.bin
/cache/logger/AOL_kernel.ap.bin

Original comment by kabal...@gmail.com on 20 May 2011 at 9:21

GoogleCodeExporter commented 8 years ago 
This also happened to me funny thing is I disabled the screen-on animation( 
since it was not working) and this error disappeared.

Original comment by naresh.1...@gmail.com on 23 May 2011 at 5:28

GoogleCodeExporter commented 8 years ago 
I can confirm that this happens on RC7. And this is the first time I'm seeing 
it on CM7 ROM. This used to happen frequently on the 2.2 stock rom. I have used 
RC0 for about 20 days and this didn't happen with that version. 

Does the logger delete logs after every restart? If not, then I can post the 
AOL* logs.

PS: How do I add labels, can't find anything on this page?

Original comment by vikas...@gmail.com on 30 May 2011 at 6:58

GoogleCodeExporter commented 8 years ago 
Should be fixed by this commit:
https://github.com/nadlabak/android_frameworks_base/commit/1397c1c3f6ef884762128
a379321cf5a5d184c06

It will be included in the next build.

Original comment by kabal...@gmail.com on 30 May 2011 at 9:36

GoogleCodeExporter commented 8 years ago 
False alarm, no fix available yet.

I really need to see the logs, as I can't reproduce this issue.
In RC8, the logger is disabled by default. Enable it by uncommenting the lines 
64-74 in /system/etc/rootfs/init.mapphone_umts.rc
https://github.com/nadlabak/android_device_motorola_umts_sholes/blob/gingerbread
/prebuilt/etc/rootfs/init.mapphone_umts.rc#L64

On restart, the logger renames the logs from previous boot to 
AOL_[buffername].ap.bin.old, so they are still available.

Original comment by kabal...@gmail.com on 3 Jun 2011 at 10:06

GoogleCodeExporter commented 8 years ago 
I think it is worth noting that when this issue appears the "M" logo during the 
boot doesn't show up at all (making it allmost unpossible to get to the 
recovery menu - the screen is black). After the phase when the Moto logo should 
be displayed the CM animation is displayed properly. I was able to workaround 
this issue by flashing fbses (android 2.0->2.1->2.2) but it looks like that 
even if the issue disaperas for a while it keeps coming back. 
Kabal could you write me a short howto to provide you some logs ('couse I'm not 
familiar with bug reporting in android :) ). 
Cheers and looking forward to you answer.

Original comment by swierkow...@gmail.com on 4 Jun 2011 at 2:02

GoogleCodeExporter commented 8 years ago 
Happens to me as well with 7.1.0-RC9-11.06.07
Did never happen on 7.1.0-RC7-11.05.27

I use a dockingstation and it looks like it is related to it somehow.

Original comment by quas...@gmail.com on 9 Jun 2011 at 7:09

GoogleCodeExporter commented 8 years ago 
Ok haven't got one of these in a while, but got one today. 
Was just reading my twitter timeline, it suddenly stopped, no artifacts, and 
froze for the normal length the screen stays on (1min). Screen turned off, 
clicked power button, screen remained off but could feel unlock bar.
Changes made to cm7: 
running older 07app2ext script (last one that moved cache folder to sdcard). 
Only one app installed to /system/app, miuicamera.apk. 
Replaced phone.apk with new one with background call notification. 
No memory management scripts at all, everything default settings.
Might be relevant: auto-brightness was on.
Governor: interactive, frequencies: min 400 max 1000, default vsel values.
DSI fix is off
JIT off
Keep home on
Keep sms off
VM set to 24mb
Brazil baseband radio installed from openrecovery.

Here are the links to the files (AOL_main.ap.bin.old and AOL_kernel.ap.bin.old, 
right after reboot):
http://dl.dropbox.com/u/15548218/AOL_kernel.ap.bin.old
http://dl.dropbox.com/u/15548218/AOL_main.ap.bin.old

Original comment by subbi...@gmail.com on 9 Jun 2011 at 11:10

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Today I got this for the first time ever.
I simply had my Milestone lying around for a while. It did make a sound during 
that time (some notification like e-mail or sms, but I dont know what it was 
anymore) but I did not pick it right up, but just left it there after the 
notification sound. When I tried to look at it later, the problem occured 
(black screen but touch screen activated).
I use RC9 (the one including "last minute changes") and barely changed anything 
(no scripts etc).
I did edit different colors for LED to different apps and I turned off some 
effects with spare parts. I also added 2G/3G option to status bar and activated 
the absolute silence mode (=when silenced, vibration turned off).
WiFi is set to turn off with screen.
I dont use a docking station and have not changed any CM7 specific apps.
Here are the file links to AOL_....ap.bin.old shortly after reboot.
kernel:
https://www.sugarsync.com/pf/D362553_6113435_862578
and main:
https://www.sugarsync.com/pf/D362553_6113435_862571

Original comment by iPhysics...@gmail.com on 11 Jun 2011 at 11:19

GoogleCodeExporter commented 8 years ago 
subbie: your issue is a classic showcase of DSI errors. Hopefully fixed for 
good in RC10 by the dsifix kernel module.

Thomas (iPhysics): Maybe it's a false lead, but there may be a connection 
between the black screen issue and wifi start-up. Can you set your wifi sleep 
policy to never and report whether the issue persists? (Settings>Wireless & 
networks>wi-fi settings>menu>advanced>wi-fi sleep policy)

Original comment by kabal...@gmail.com on 14 Jun 2011 at 12:28

GoogleCodeExporter commented 8 years ago 
I will change the wifi settings, but if it does not show up, I dont know how 
strong of an arguement it will be. This is the first time it happened and I've 
been using CM7 for quite a while now.
A little pointer towards your idea Nadlabak: Only since ~15.5.11 I've changed 
my wifi setting from 'never' to 'when screen turns off'. Before that I never 
had this problem, though ~3 week later is too big of a timespan to really say 
that changing wifi settings caused this problem.
I'll try for a week or so and then change back. If you dont hear from me again 
(changing to RC10 tonight), thats  a good thing :)
Thanks for all your work.

Original comment by iPhysics...@gmail.com on 14 Jun 2011 at 12:59

GoogleCodeExporter commented 8 years ago 
Do you guys see motorola M logo after the screen issue, 'couse I cannot go
to bootloader becouse of that. Is it just me or you have same problem?
14-06-2011 13:59 użytkownik <cyanogenmod4milestone@googlecode.com> napisał:

up after sleep mode, but touch screen works

how strong of an arguement it will be. This is the first time it happened
and I've been using CM7 for quite a while now.

changed my wifi setting from 'never' to 'when screen turns off'. Before that
I never had this problem, though ~3 week later is too big of a timespan to
really say that changing wifi settings caused this problem.

again (changing to RC10 tonight), thats  a good thing :)

Original comment by swierkow...@gmail.com on 14 Jun 2011 at 1:35

GoogleCodeExporter commented 8 years ago 
Please update - do you still experience the issue when running the recent 
builds - e.g. RC15?

Original comment by kabal...@gmail.com on 10 Sep 2011 at 11:02

GoogleCodeExporter commented 8 years ago 
I have not experienced this after RC10 or RC11 anymore.

Original comment by quas...@gmail.com on 11 Sep 2011 at 6:41

GoogleCodeExporter commented 8 years ago 
No. I don't remember exactly when this stopped, but I haven't experienced it 
anymore in latest releases.

Original comment by afa...@gmail.com on 12 Sep 2011 at 12:30

GoogleCodeExporter commented 8 years ago 
great.
closed

Original comment by kabal...@gmail.com on 13 Sep 2011 at 3:10