Develop Bugs

[Q] Issue with LCD screen

I'm running my htc vision with Pyromod v2.0 (2.3.3 gb ROM) with the pyro kernel, which i believe is an altered version of pershoots latest kernel. Fantastic ROM, i've been using it since sunday morning with no problems, it's fast, slick, and incredibly small and responsive...
but, last night i ran the phone, with gps on, and streaming over amazonmp3 app, got to my location, sent a text, closed the keyboard, and hit the power button to put the screen to sleep. I got out of my car, walked up to the front door and was about to call to be let in, take out my phone, screen won't turn on, buttons on the bottom the screen light up and respond as normal. I have it set so i can hit the back button to unlock, so i hit back, and adjust the volume.. i hear the tone, so i knew i was on the main screen and past the lockscreen. After i get into the apt after being noticed, i do a battery pull. The phone reboots, i heard the vibrate that comes on right when the htc boot logo comes up, but STILL NOTHING on the screen! I try this a few more times.. let it boot, and have my girlfriend call me, she does, phone rings and i can answer it, touchscreen is responsive to slide to answer, but NOTHING on screen! phone functions, but the screen won't turn on. i leave the battery out overnight, in the morning my gf puts the battery in while i'm in the bathroom, unknown to me.. i come back and she holds up my phone, booting up, screen on.. needless to say i was thrilled! Flash forward, i'm at work during the day, screen and phone have been working fine.. around 3.. i turn the screen off.. and it doesn't turn back on again, same as before!
Now that i'm home i have messed with it a bit, if i leave the "blank" screen on while the phone is charging, eventually it times out.. but when i hit to power it on again for a 2nd time, the screen returns to life... but if i turn it off i have to do that again.
I've tried changed the cpu scaling, removing software.. but deep down i don't think that it's a problem with the software, does anyone think it could be the rom?
I guess my questions are
-does anyone know how i can test the unit via adb to see what's wrong?
-has anyone experienced anything like this before?
-anyone know where i can find the stock rom in case i have to return this thing?
EDIT: UPDATE: Here is the Logcat from my device
https://rapidshare.com/files/2442882484/logcat.txt
Pretty much this is what happens when i tried to turn the screen on and got nothing
I/power ( 1340): *** set_screen_state 0
W/IInputConnectionWrapper( 3292): getExtractedText on inactive InputConnection
W/IInputConnectionWrapper( 3292): getExtractedText on inactive InputConnection
D/SurfaceFlinger( 1340): About to give-up screen, flinger = 0x93b98
D/TEST] ( 2419): There are 0 instances of Clock
I/com.dropbox.android.activity.lock.LockReceiver( 3322): Received action: android.intent.action.SCREEN_OFF
D/AK8975 ( 1234): Compass CLOSE
D/dalvikvm( 3322): GC_EXPLICIT freed 293K, 51% free 3343K/6791K, external 1K/513K, paused 79ms
D/dalvikvm( 3153): GC_EXPLICIT freed <1K, 51% free 2750K/5511K, external 0K/0K, paused 86ms
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/H7CTransparentBlack_base_small_95.png
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlysunny.png
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlysunny.png
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlysunny.png
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_chancestorm.png
I/System.out( 1428): resolveUri failed on bad bitmap uri: /data/data/com.anddoes.fancywidget.pro/files/weather_mostlycloudy.png
I/power ( 1340): *** set_screen_state 1
D/SurfaceFlinger( 1340): Screen about to return, flinger = 0x93b98
D/AK8975 ( 1234): Compass Start
D/TEST] ( 2419): There are 0 instances of Clock
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 334K, 53% free 2881K/6023K, external 1331K/1444K, paused 42ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 316K, 53% free 2846K/6023K, external 932K/1163K, paused 35ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 53K, 49% free 3127K/6023K, external 1524K/1725K, paused 35ms
D/dalvikvm( 1340): GC_EXTERNAL_ALLOC freed 169K, 53% free 6663K/14151K, external 4375K/4478K, paused 72ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 349K, 53% free 2881K/6023K, external 1314K/1381K, paused 28ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 317K, 53% free 2845K/6023K, external 932K/1163K, paused 34ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 46K, 53% free 2879K/6023K, external 1612K/1725K, paused 35ms
D/dalvikvm( 2419): GC_EXTERNAL_ALLOC freed 316K, 53% free 2844K/6023K, external 932K/1163K, paused 26ms
D/dalvikvm( 1340): GC_EXTERNAL_ALLOC freed 25K, 53% free 6658K/14151K, external 4405K/4478K, paused 69ms
D/GoogleVoice( 3139): MASFUpdateSettingsRpc.createRequestPayload: ENT
D/GoogleVoice( 3139): MASFUpdateSettingsRpc.createRequestPayload: RET
I/System.out( 3139): [INFO:5970349]: LogSource: Running flush
I/System.out( 3139): [INFO:5970352]: LogSource: Sending payload [bytes=660]

Could be anything; from to high OC to bad flash.
Try reflashing and afterwards do not overclock over 900. Also do not underclock. See what happens then.

reflashed via adb lastnight, no luck, also i only overclocked to around 900 normally and managed to disable that before reflashing.. also cleared cache, when i flashed i cleared cache and data, no dice.. as a matter of fact, now i can't seem to even "trick" it to turn on
do you think it could really be a ROM issue? i thought the rom only loaded after the splash screen and/or hboot? I get nothing on screen even as soon as the phone is turned on
anyway called t-mobile and they said it's a "known defect on early models of the g2 (much like the loose hinge)." Managed to convince them to ship me another phone at no charge to me with 3 day shipping.. now i just need to try to downgrade it and get it back to stock in the next 10 days... oh joy.

[Q][HELP] My defy turns off by itself (CM7 and Froyo, catlog available)

Actually I have this problem with CM7 RC1v2, but in the past I had the same issue with Froyo ROM (Barebones one and if a remember well also official one): before going to sleep I put the phone in aeroplane mode and in the following morning I found it switched off.
This is not systematic, or better, last 3-4 days it happened always but from when I flash CM7 the problem seemed to be solved.
Last night I made a CatLog (attached) and reading it today I have noticed the following lines:
07-13 01:37:01.553 D/dalvikvm( 8555): GC_CONCURRENT freed 421K, 52% free 3204K/6663K, external 898K/1410K, paused 3ms+4ms
07-13 01:52:20.514 E/BATTD ( 1923): unrecoverable_error=AP Panic
07-13 01:52:20.514 I/BATTD ( 1923): SBCM_GLUE: Battery Exhausted, Sending 0 capacity to Power down
07-13 01:52:20.522 I/ActivityManager( 2149): Starting: Intent { act=android.intent.action.ACTION_REQUEST_SHUTDOWN flg=0x10000000 cmp=android/com.android.server.ShutdownActivity (has extras) } from pid 2149
I'm not so skilled in linux/android debuging (what is BATTD? sure something related to the battery...), but I think this is the moment that cause the shutdown of the defy.
Due to the fact that the issue happens both with CM7 than Froyo rom, I (unfortunately) suspect that may be a problem of the battery.
Have someone an idea about the possible cause of the problem? Or could it get more information than me from the catlog?
Many thanks.
EDIT: obviously the battery was charged, during catlog logging was around 60%. If the defy is connect to the power supply the issue seems not happen.

No one can help me to understand the catlog?!

Today happened another time, but I have not the catlog.
Please, no one have any idea? Or the only way is to understand is to buy another battery?

Again...
07-25 00:05:25.366 D/dalvikvm( 2286): GC_FOR_MALLOC freed 358K, 46% free 3720K/6791K, external 0K/512K, paused 57ms
07-25 00:22:46.530 E/BATTD ( 1927): unrecoverable_error=AP Panic
07-25 00:22:46.530 I/BATTD ( 1927): SBCM_GLUE: Battery Exhausted, Sending 0 capacity to Power down
07-25 00:22:46.538 I/SSM ( 1935): UEvent: PA Boost - Battery TOO LOW

Id suggest buying a second battery and see if the problem persists. If it does not, ditch your first battery, if it does hope for help
I would buy a cheap after market battery - they should be avaible on ebay fo less than 10$-

Yes, I just ordered one: 2,27 euro shipped from HK ahahah OK, only to see if it resolves the problem and if it reveals good in all, well I was lucky, otherwise I will buy an original one
Thanks for the reply!

[Q] Camera Problem "Cannot connect to camera"

I found a new problem, which can potentially be really annoying since there's no other way to solve it apart from power cycle the phone.
I was messing around with the phone camera and switching between camcorder and camera mode, then the whole screen went black with the soft buttons showing in "dot" form.
I went back to the home screen and launched Camera app once again and still no activity. After a few seconds the OS informed that Camera app stopped working so I hit "Close". Then once I tried starting the Camera app again, there was this error "Cannot connect to camera"
Has anyone had this problem before?

cannot connect to camera
Just had this problem today. Was doing some video of setting up a new generator. That went ok. Got things set up and was going to take a pic. Screen was black. Tried opening a couple of times and got message "cannot connect to camera. I am doing a power cycle now.
Al

yeah I've had it before using cyanogen on my HTC sensation. had to power cycle. its annoying, happens often.
Sent from my Sensation using XDA App

It happened once on mine and I'm running standard 4.02. Never had it happen til yesterday.
Sent from my Galaxy Nexus using Tapatalk

This happened to me yesterday. Running stock 4.02. power cycle was the only way to get the camera working again.

Has happened to me on every rom i've tried, stock 4.0.1, arhd 2.1, cyanogenmod, villianrom etc. Very odd, happens when i try to enter the camera from the lock screen and rotate the device to landscape.

I'm also getting the same issue; has happened about 6 times in 4 days. Power cycle fixes it, which is very annoying. I'm not sure if the camera is active too long? It's usually running in Recent Apps.
I've been trying to exit out of the camera when I'm done as opposed to swapping apps or going to standby to see if that helps.

I'm having the same issue with my G-Nexus... 2nd time it's happened in 5 days.
Read in another blog that it could be caused by apps that access the camera that are not updated for ICS. NOt sure. But I uninstalled all such apps... we'll see.

I have this issue as well on my new GSM G-NEX that I have own for only three days now. Getting "cannot connect to camera" whenever I try to access camera, and power cycling doesn't help.

cannot connect to camera
after installation of cm7.1 i have the same problem with my zte blade. when i open the camera app, it says cannot connect to camera. idont no what to do. please help

I've had that problem a few times, usually from bad camera apps. Force closing the camera apps seem to fix the problem for me
Sent from my GT-P1000 using XDA App

I started having the same problem yesterday after taking a handful of pictures. Tried force stoping the Camera app, tried clearing its data/cache - no luck.
Here's a screenshot of the error:
h ttp://dev.npike.net/public/1325185257.png

I've read that if you have "force GDP rendering" on in the developer options it is screwing up the camera and camera apps

I don't have the option to force hardware acceleration enabled, but here is the output of logcat during the error:
Code:
I/ActivityManager( 185): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.camera/com.android.camera.Camera bnds=[40,785][200,985]} from pid 476
I/WindowManager( 185): createSurface Window{41f14030 Starting com.google.android.camera paused=false}: DRAW NOW PENDING
I/InputReader( 185): Reconfiguring input devices. changes=0x00000004
I/InputReader( 185): Device reconfigured: id=6, name='Melfas MMSxxx Touchscreen', surface size is now 720x1280, mode is 1
I/ActivityManager( 185): Config changed: {1.0 311mcc480mnc en_US layoutdir=0 sw360dp w598dp h360dp nrml land finger -keyb/v/h -nav/h s.29}
D/OpenGLRenderer( 268): Flushing caches (mode 0)
D/OpenGLRenderer( 268): Flushing caches (mode 0)
V/CameraHolder( 3737): open camera 0
W/CameraService( 118): CameraService::connect X (pid 3737) rejected (existing client).
E/CameraHolder( 3737): fail to connect Camera
E/CameraHolder( 3737): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 3737): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 3737): at android.hardware.Camera.<init>(Camera.java:302)
E/CameraHolder( 3737): at android.hardware.Camera.open(Camera.java:264)
E/CameraHolder( 3737): at com.android.camera.CameraHolder.open(CameraHolder.java:131)
E/CameraHolder( 3737): at com.android.camera.Util.openCamera(Util.java:267)
E/CameraHolder( 3737): at com.android.camera.Camera$4.run(Camera.java:1008)
E/CameraHolder( 3737): at java.lang.Thread.run(Thread.java:856)
D/dalvikvm( 3737): GC_FOR_ALLOC freed 142K, 2% free 16021K/16263K, paused 22ms
I/dalvikvm-heap( 3737): Grow heap (frag case) to 16.346MB for 662416-byte allocation
D/dalvikvm( 3737): GC_CONCURRENT freed 1535K, 11% free 15132K/16967K, paused 2ms+4ms
D/OpenGLRenderer( 476): Flushing caches (mode 0)
D/dalvikvm( 3737): GC_FOR_ALLOC freed 18K, 9% free 15476K/16967K, paused 14ms
D/dalvikvm( 3737): GC_CONCURRENT freed 8K, 7% free 15928K/16967K, paused 1ms+2ms
I/WindowManager( 185): createSurface Window{41cf6e00 com.google.android.camera/com.android.camera.Camera paused=false}: DRAW NOW PENDING
I/WindowManager( 185): createSurface Window{41ee9870 com.google.android.camera/com.android.camera.Camera paused=false}: DRAW NOW PENDING
D/OpenGLRenderer( 476): Flushing caches (mode 1)
D/OpenGLRenderer( 476): Flushing caches (mode 0)
I/WindowManager( 185): createSurface Window{42067810 SurfaceView paused=false}: DRAW NOW PENDING
V/camera ( 3737): surfaceChanged. w=960. h=720
I/ActivityManager( 185): Displayed com.google.android.camera/com.android.camera.Camera: +822ms
It sounds like when the Camera app crashes it doesn't release its resources correctly - preventing anything else on the system from acquiring the camera.
Update: I have reported this issue to Google ht tp://code.google.com/p/android/issues/detail?id=23776

Strange.. I had this phone for quite a while and I suddenly started seeing this problem. That's after moving from Franco's kernel to popcorn. I'm wondering if its something to do with the kernel.
Any updates so far?

I've had this problem--but only when I accidentally started the Cartoon Camera app. Essentially, my GN hates it when two apps are using the same camera .

dmmarck said:
I've had this problem--but only when I accidentally started the Cartoon Camera app. Essentially, my GN hates it when two apps are using the same camera .
Click to expand...
Click to collapse
I've also discovered that the official battery might be the factor. I have two official samsung galaxy nexus batteries, I think one is causing the camera to crash everytime. Maybe the NFC inside the battery?

I've had the problem numerous times. Stock 4.0.2. Sometimes it's when I'm out and about. I was beginning to think it could be related to GPS. I've sent several email trouble reports to Google and received no feedback/response.

I have the same issue, it seems to occur when I use the camera for a while, and joum between home and camera a lot. I have a completely stock setup at the moment and it happens much less frequently now than it did when I was running MRC r10.

Well, from what I am experiencing, it's something about task switching (like what TheBishopOfSoho mentioned) and also probably something about screen rotation. I have very little apps which I allow to rotate (camera is one of them) so it has to vigorously switch rotation when I switch apps.
But overall, the prob always comes unexpectedly.. so it's hard to pinpoint it
EDIT: One thing that has remained constant throughout my experience is that all camera problems were present when I was using the Popcorn kernel. Franco's kernel hasn't experienced it yet.
Franco 18.2: OK
Popcorn 7.x : Cam problems started appearing (can't remember which version I used)
Franco: 18.5: OK
Franco: 18.6: OK so far...
So maybe it's something in the kernel.. the cpu governor, speed, etc..
Just trying to get as much info as possible so hopefully we can find out the root cause of this..

Crashed now Stuck on Boot Screen CM9 - Alpha 4

Hey Guys,
Woke Up this morning and did the usual of checking the time on my phone, to my surprise the screen was on and it seemed to be stuck on 08:31, So I thought oh it's just a crash and pulled the battery out, but now it's just stuck on the CM9 Boot logo (Running Alpha 4), I need my texts and call log and contacts (Can get contacts of Google Mail) But I've tried running logcat while it's in the state and all I'm getting is "09:39:38.124 Debug dalvikvm 1858 GC_CONCURRENT freed 1836K, 37% free 5319K/8323K, paused 2ms+3ms" and Something about Starting service ScreenFlinger, I would rather not wipe it but if I have to I have to.
Any Idea's?
Jamie

Anything anyone?

HTC ONE M8- Sudden Power Off When Battery Is Below 50%

Sudden power off when battery is less than 50 percent
Hi community,
I would be very glad to get some help for the problem below. Or maybe you can guide me how to provide more information to investigate it.
Problem
The phone sometimes powers itself off abruptly which can lead to database corruption. So it is very annoying...
However, it only seems to occur in some cases:
It happens as soon as battery is below 50% (this is not exact, but pretty close)
It only happens when the screen is off. May happen after 30 sec to 5 min.
It never happens when a USB cable is connected (power-only or computer)
It does not seem to happen when a "background task" is running
In some rare cases, it does not happen at all, or maybe just has not happened for a longer period of time. I could not determine what is different about the state of the phone then. When I turn the screen on once, and off again, the chances are high that it will power off very soon!
By "background task" I mean something like playing music, but I can not exactly define it. It can stay on like for one hour without any problems (screen turned off). It also stays on when, for instance, the timer is running and the screen is on.
So it does not seem to be a problem of the battery...
ROMs
I tried the following ROMs, all with the same issue. When switching ROMs, I always wiped system, data, cache, dalvik-cache. Never flashed another Zip on top (like Gapps). The device is unlocked using the official procedure by HTC.
Two official versions of cm12.1
A BlissPop v3.9 earlier build than below
BlissPop-v3.9-m8-OFFICIAL-20150827-0154 (currently running)
SkyBliss-v3.2.1-m8 (fantastic ROM, btw!)
Stock v4.19.111.2 + OTA to v4.19.111.3
More details of stock:
Relocked and flashed the Firmware v4.19.111.2 (Android File Host fid=95916177934521492)
Unlocked, flashed TWRP, then Stock v4.19.111.2 (Android File Host fid=95916177934527598)
Relocked and receive OTA v4.19.111.3
Debug
Below is a Logcat session. The numbers are line numbers. Of cource, they are not relevant, but they put things into perspective.
1163: I/PowerManagerService: Going to sleep due to screen timeout (uid 1000)...
1371: I/PowerManagerService: Dozing...
1389-1466, 5 times occured: E/libsuspend: Error writing to /sys/power/state: Device or resource busy
1467: I/PowerManagerService: Waking up from dozing (uid 1000)... (I pressed the power button to see, if it is still alive)
...
2743: I/PowerManagerService: Going to sleep due to screen timeout (uid 1000)...
2931: I/PowerManagerService: Dozing...
2942, once: E/libsuspend: Error writing to /sys/power/state: Device or resource busy
2959: The phone is dead
There are also a log of those lines when the screen is off:
I/qdhwcomposer: handle_blank_event: dpy:1 panel power state: 0
(dpy:0/1 changing a lot)
Troubleshooting
I changed the CPU governor in my current BlissPop ROM: was Lionheart, tried Ondemand, Intellidemand, and Interactive. Subjectively, it slightly reduced the amount of battery percentage when the problem begins to occur. However, the problem persists and I did not take note of the battery charge.
Left default setting for "power safer".
???
What can I do about it?
Are there any tools to investigate the problem in more detail?
Does anyone have the same problem?
Thanks a lot,
Adi

Added Debug section