Related
I've been trying to launch the Camera app but I've been unable to do so. To try to troubleshoot this, I hooked up the N1 to my Mac and fired up ddms.
Here's part of the verbose log:
01-15 19:53:55.508: VERBOSE/RenderScript_jni(513): surfaceChanged
01-15 19:53:55.508: VERBOSE/RenderScript(513): setSurface 800 480 0x606a00
01-15 19:53:55.508: ERROR/Surface(513): surface (id=0, identity=402) is invalid, err=-19 (No such device)
01-15 19:53:55.508: ERROR/Surface(513): surface (id=0, identity=402) is invalid, err=-19 (No such device)
01-15 19:53:55.658: INFO/dalvikvm(1333): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=40)
01-15 19:53:55.718: ERROR/Surface(513): invalid token (-1, identity=0) or client (0x0)
01-15 19:53:55.798: ERROR/Adreno200-EGL(513): egliGetNativeWindowSize: unable to dequeue native buffer
01-15 19:53:55.798: ERROR/Surface(513): invalid token (-1, identity=0) or client (0x0)
01-15 19:53:55.798: ERROR/Adreno200-EGL(513): egliGetNativeWindowSize: unable to dequeue native buffer
01-15 19:53:55.798: ERROR/RenderScript(513): EGL/Surface mismatch EGL (0 x 0) SF (800 x 480)
01-15 19:53:55.918: DEBUG/dalvikvm(1333): GC freed 1329 objects / 92912 bytes in 75ms
01-15 19:53:55.948: ERROR/RenderScript(513): Pending GL Error, 0x3f9698
01-15 19:53:55.948: DEBUG/CameraService(52): CameraService::connect E (pid 1333, client 0x17f60)
01-15 19:53:55.978: VERBOSE/RenderScript_jni(513): surfaceDestroyed
01-15 19:53:55.978: VERBOSE/RenderScript(513): setSurface 0 0 0x0
01-15 19:54:00.458: WARN/WindowManager(67): App freeze timeout expired.
01-15 19:54:00.458: WARN/WindowManager(67): Force clearing freeze: AppWindowToken{44caddc0 token=HistoryRecord{44cadb68 com.android.camera/.Camera}}
01-15 19:54:02.568: DEBUG/dalvikvm(67): GC freed 11814 objects / 607904 bytes in 112ms
01-15 19:54:05.382: WARN/ActivityManager(67): Launch timeout has expired, giving up wake lock!
01-15 19:54:05.655: WARN/ActivityManager(67): Activity idle timeout for HistoryRecord{44cadb68 com.android.camera/.Camera}
Every time I try to terminate just the camera app (after atleast 5 mins of it being up and hung), and restart it, the last line (in bold) is all I see and that is it. Nothing shows up on the screen from there on wards.
This N1 is rooted and is only running Cyanogen's bacon bits, nothing else.
For the time being I will try to uninstall applications that I have recently installed and see if that helps this situation at all. If anyone else has run into this on their N1, please do share your experience.
Everytime I brought up my camera last night it would just black screen for a couple minutes then ask me to force close or wait. It was working fine earlier in the day and I didn't change anything with my phone. I had to do a wipe to get it to work again Also rooted with Cyanogen Bacon 1
Just stopped working again...I think it might have to do if I let my battery die...
I'm having the same problem. I'm rooted but nothing else. I was using my camera fine before, no additional pieces of software installed between when it broke and when it was working... I don't get why it's hanging like this...
My Camera has been functioning fine, I was able to snap a photo while using navigation of a driver doing something stupid (would be impossible on G1) and switch back to Nav with no problem. I suggest that anyone that isn't having any problems do a nandroid backup just in case.
Well I just did a reboot and that seemed to help. A nandroid backup wouldn't hurt... just wish I knew what was causing the problem. Any of you have picsay installed? I uninstalled it and restarted then it seemed fine.
I can restore using Nandroid to a few days back, so I'm not too concerned, but not knowing the root cause just means I could end up in this situation again.
I'll try to keep debugging, but it likely has to do with installation of some application, because nothing else makes sense.
iVisionX01 said:
My Camera has been functioning fine, I was able to snap a photo while using navigation of a driver doing something stupid (would be impossible on G1) and switch back to Nav with no problem. I suggest that anyone that isn't having any problems do a nandroid backup just in case.
Click to expand...
Click to collapse
Are you rooted?
uansari1 said:
Are you rooted?
Click to expand...
Click to collapse
Yes and I have Cyanogen's Addon.
Uninstalling Picsay and then rebooting did address the camera (thx for that hint!).
Reinstalling Picsay and then rebooting, then retry launching Camera caused the same issue. For the time being, I'll keep Picsay uninstalled and report this thread back to picsay devs. See if they have any insight into this. Thx for your help guys.
JunoonX said:
Uninstalling Picsay and then rebooting did address the camera (thx for that hint!).
Reinstalling Picsay and then rebooting, then retry launching Camera caused the same issue. For the time being, I'll keep Picsay uninstalled and report this thread back to picsay devs. See if they have any insight into this. Thx for your help guys.
Click to expand...
Click to collapse
The Gallery and Photoshop Mobile have some basic photo editing tools you can use in the mean time.
burton14e7 said:
Everytime I brought up my camera last night it would just black screen for a couple minutes then ask me to force close or wait. It was working fine earlier in the day and I didn't change anything with my phone. I had to do a wipe to get it to work again Also rooted with Cyanogen Bacon 1
Click to expand...
Click to collapse
Mine did the exact same thing last night; bombed out with the black screen several times over. I rebooted into console and fixed uid's and it's been fine ever since. I've noticed the N1 has some software issues here and there.
BTW, my phone is rooted but nothing else.
This happened to me after updating to the latest "Nexus One Torch" with widget.
Edit: Preliminary reports indicate this is indeed the issue at hand, and that updating to the latest version of Nexus One Torch should resolve this.
kozm0naut said:
This happened to me after updating to the latest "Nexus One Torch" with widget.
Click to expand...
Click to collapse
Ya, the same thing happened to me as well. I removed it and all is well again.
erikku said:
Ya, the same thing happened to me as well. I removed it and all is well again.
Click to expand...
Click to collapse
Check the market again it looked like the dev fixed the problem my camera doesn't hang.
iVisionX01 said:
Check the market again it looked like the dev fixed the problem my camera doesn't hang.
Click to expand...
Click to collapse
Verified. Updated Torch app and camera is back to normal for me.
Interesting, as fixing permissions from console fixed the issue on my phone. I used the camera quite a bit after that too.
Just updated the torch app, hopefully this behind us now.
I have the same problem, unfortunately on a phone i just got and installed just a couple of applications.
I've done factory reset few times since then and the problem still persist, it doesnt seem to be application related here.
SANTilt, you said that you fixed some permissions from the console? Can you tell me how you did that, im new to android.
If that doesn't help i'm pretty sure i got a falty hardware and i dont even have a warranty...
Hey guys. I've been looking around all over for info on the problem with my app. Nothing I found was a concrete answer. here's the problem. I made an app that works really well except it force closes when I hit the back button to finish activity and then start another of the same activity as before. It force closes once in a while when I do this, throwing a log cat error that says out of memory, pointing to where I fill my bitmap cache. There's two reasons im thinking it would be doing this. 1) My bitmap factory is having a problem or 2) I have the context of my activity stored as a variable so I can close activity and that is too much memory. I'm using a panel, which also may add to the problem. Also, another phone can't even start the activity the first time. Any help would be greatly appreciated. This is only problem on app and this fix will make it market ready.
Sent from my SCH-I500 using XDA App
Did you try to explicitly clean up the bitmap references? you should call Recycle() on every bitmap in your activity's onDestroy or wherever you do your cleaning. Another issue I had was with the Bitmap.CreateScaledBitmap method - it leaks, apparently. I made a small static method that uses a transform matrix and then calls Bitmap.CreateBitmap (the overload that takes a matrix, obviously). That change alone solved half my memory issues.
The thing about not loading at all on another phone might be a heap issue. My game loaded just great on my customized SGS, but on the emulator with 24mb of heap it crashed. The reason was that I pre-load all the sprites at the beginning, and apparently 24mb isn't that much
Solution was downscaling and lowering resolution and color depth for the sprites, not much possibilities here - too many bitmaps take too much memory...
I'm guessing the phone you tested likely has a smaller heap than the phone that doesn't make your app crash.
Of course all of the above is mostly guess work, but that's what I can supply right now
i have the problem fc too, but after i upgraded to 2.2. the seem the problem fixed automatically.
Thanks so much! I made it recycle my bitmaps, along with a few minor changes, and it worked great! Thanks for your help!
Sent from my SCH-I500 using XDA App
While poking around today, I discovered that I could deterministically cause "rild" to segfault - every time I tried it.
The method I used was to turn on WiFi with the Mobile Data network already running, and then I would launch the app "Wifi Analyzer" (farproc). Almost immediately the "rild" (Radio Interface Layer Daemon) would segfault. (Strictly speaking, I don't know if using WiFi Analyzer was necessary - my WiFi has beacons turned off, and sometimes I can't establish a session straight away; using a scanner seems to get my AP to come out of it's sleep).
That consistency convinced me to use strace to attach to the already-running "rild" daemon, and spew to a log file.
Note that historically, the SIGSEGV faults that were logged to the logcat output at the moment of the "undead call" implicated a problem in the fclose() call - almost as if something was trying to close a file that had not been opened correctly.
So, there in the strace output, was this:
Code:
16:43:23 writev(6, [{"\3", 1}, {"HTC_RIL\0", 8}, {"(t=1297817003)%% $HTC_3GIND:0\\r\\n\0", 35}], 3) = 44
16:43:23 open("/data/data/com.android.dmportread/history", O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 ENOENT (No such file or directory)
16:43:23 chmod("/data/data/com.android.dmportread/history", 0666) = -1 ENOENT (No such file or directory)
16:43:23 writev(6, [{"\3", 1}, {"HTC_RIL\0", 8}, {"at_notify_cdma_g23_data_entry():Can't open /data/data/com.android.dmportread/history successfully \r\n\n\0",102}], 3) = 111
16:43:23 --- SIGSEGV (Segmentation fault) @ 0 (c) ---
a quick peek at /system/lib/libhtc_ril.so shows that - yep - buried in there is a reference to
/data/data/com.android.dmportread/history
So, I tried the following:
Code:
[COLOR=green][B]
mkdir /data/data/com.android.dmportread
chown radio:radio /data/data/com.android.dmportread
touch /data/data/com.android.dmportread/history
chown radio:radio /data/data/com.android.dmportread/history
[/B][/COLOR]
and guess what - no more segfaults. [SIZE=+3]YES![/SIZE]
If this is the cause of the "undead" call (seems highly likely), the explanation appears to be due to a bug in the HTC vendor library lbhtc_ril.so : a file open() fails, but the corresponding "close()" operation takes place anyway, and that is where the fault (segmentation violation) occurs. There is a stupid dependency of the libhtc_ril.so file on the DMPortRead.apk app.
Probably the only reason that this bug does not express itself in HTC "factory" 2.1 ROMs is because of the presence of DMPortRead.apk app - presumably that creates/maintains the history file.
[SIZE=+1]See the 3rd post of this thread for downloadable patch/script files[/SIZE]
If any of you are consistently experiencing the "undead call" problem, please consider testing the above to see if you think it is the fix. (I believe it is.)
bftb0
I knew I liked you!
I'll have to try this out when I get home.
Here's a flashable .zip and also a shell script which may be used in Gscript lite - you need to unpack the "unpackme.zip" file to get to them. ("unpackme" is NOT flashable).
I realized after I was 95% of the way through putting together the installer script that there was absolutely no reason to do this in an offline fashion (that is, "overflashing" it during a recovery boot) - it is perfectly fine to do what needs to be done in a shell script any time you please with the regular OS is running. Oh well, the ROM devs can look at it and use whatever they want from it (or nothing at all).
You can run the CureUndead_v0.9.sh script either from within the Gscript Lite app (you need to give the script root privilege), or you could use adb to push it to /data/local and chmod it and execute it by hand. Note that Gscript Lite on GingerBread has this annoying bug where it prints "stderr:" for every line in the original script. It's not my script that's doing that - it's either a problem with Gscript Lite, or something unusual about GSB.
Oh, yeah - the way the script is written, you can run it as many times as you want; as a side effect, this will truncate to zero length any prior history file.
MD5's and sizes of contents of "unpackme.zip":
0bf8c49312e61c436d379a24255b12f3 CureUndead_v0.9.sh - 421 bytes
9d459f9f598f51fffa98cf832c524e50 CureUndead_v0.9.zip - 2,678 bytes (this one is flashable)
Going to try it out... Thanks for this!
nice work...
Very interesting... so this is something that would need to be done post flash, what do you think...
... we use that lights.sh script conap put together in /system/xbin/ that runs @ every boot to initialize the lights for trackball/notifications... would it work if I added the lines to that? I'm not sure if it would cause issues running it @ each boot or not?
Trying to figure out a different way to add this pre-build too.
This is huge if it's the fix. Incredible work.
oceanminded said:
This is huge if it's the fix. Incredible work.
Click to expand...
Click to collapse
I think it is the fix
workshed said:
Very interesting... so this is something that would need to be done post flash, what do you think...
... we use that lights.sh script conap put together in /system/xbin/ that runs @ every boot to initialize the lights for trackball/notifications... would it work if I added the lines to that? I'm not sure if it would cause issues running it @ each boot or not?
Trying to figure out a different way to add this pre-build too.
Click to expand...
Click to collapse
Well, I'm putting together a flashable "fix" file that just uses the installer script, so it could be rolled up into a ROM install as well.
The one thing you might want at boot (rather than only at ROM install time) is some kind of zero-ing out of the history file every once in a while, so that it doesn't grow without bound. I only watched it for a short period of time, and it was only 4 lines long; it might not ever grow big, but that seems like the right thing to do.
So I guess I'll wait until one of you genuises makes this "point and click" simple. I don't have a clue how to implement this on my own. Awesome work bftb0 !
Sheesh you're a brain OP. Awesome job!
Sent from my Ginger Tazz using XDA App
Interesting... what's the undead call bug you're talking about? I've been getting this funny bug on long calls where sometimes the phone app just crashes after 15-30mins or so. I get the crash window, and if I force quit, it shows no signal until I reboot the phone. If that's the one, a fix would be really nice. Running KaosFroyo v39 and never flashed a new radio BTW.
I've also seen the same thing on the WiFi signal. I have SSID broadcast turned off, and it takes it's sweet time picking it up on its own, but running WiFi analyzer seems to wake it up.
ufmace said:
Interesting... what's the undead call bug you're talking about? I've been getting this funny bug on long calls where sometimes the phone app just crashes after 15-30mins or so. I get the crash window, and if I force quit, it shows no signal until I reboot the phone. If that's the one, a fix would be really nice. Running KaosFroyo v39 and never flashed a new radio BTW.
I've also seen the same thing on the WiFi signal. I have SSID broadcast turned off, and it takes it's sweet time picking it up on its own, but running WiFi analyzer seems to wake it up.
Click to expand...
Click to collapse
What he is referring to is during a call you get the tones and vibration like the call has been dropped but then you can hear the person on the other end again and the call was never dropped. What you are describing is a new one to me...
CondemnedSoul said:
What he is referring to is during a call you get the tones and vibration like the call has been dropped but then you can hear the person on the other end again and the call was never dropped. What you are describing is a new one to me...
Click to expand...
Click to collapse
Ah yeah, I've had that happen too. I didn't think of it, though, since it wasn't all that annoying to me. I already ran the fix anyways, so I'll see if it helps either problem.
I haven't had the problem for some reason, but I just entered all that in a terminal window on my phone (and wasn't that tedious). Thanks!
Scott586 said:
So I guess I'll wait until one of you genuises makes this "point and click" simple. I don't have a clue how to implement this on my own. Awesome work bftb0 !
Click to expand...
Click to collapse
I put up a script in the 3rd post in this thread which you could use in the Gscript Lite app. You will still need to figure out how to use Gscript Lite, but at least no "adb" or command-prompt typing is needed.
Everybody else - I would appreciate hearing back from you after you try this, especially if you have been experiencing the "undead call" bug frequently. (I've used my phone for calling so little recently I don't think it has happened to me in more than 5 weeks.) The more often it was happening to you in the past, the more valuable your feedback is now.
bftb0
bftb0 said:
I put up a script in the 3rd post in this thread which you could use in the Gscript Lite app. You will still need to figure out how to use Gscript Lite, but at least no "adb" or command-prompt typing is needed.
Everybody else - I would appreciate hearing back from you after you try this, especially if you have been experiencing the "undead call" bug frequently. (I've used my phone for calling so little recently I don't think it has happened to me in more than 5 weeks.) The more often it was happening to you in the past, the more valuable your feedback is now.
bftb0
Click to expand...
Click to collapse
thanks for the script bf, that's all I needed to add it in the rom. I'll be a tester also, as I do experience the bug quite often, but only on long calls which isn't as frequent for me currently. Bravo sir!
P.S. I will be sure to add "# Undead call fix by bftb0" in the rom and OP page
workshed said:
thanks for the script bf, that's all I needed to add it in the rom. I'll be a tester also, as I do experience the bug quite often, but only on long calls which isn't as frequent for me currently. Bravo sir!
P.S. I will be sure to add "# Undead call fix by bftb0" in the rom and OP page
Click to expand...
Click to collapse
dope
this is good news. great job op and workshed if u add it to your gb rom lol
love you both!
flashed it on gsb1.4. i'll let you know how it goes.
:O OMG! That always happens, but I thought I was crazy XD So I'm going to try this.
Sent from my Droid Eris ♥ (running Ginger Tazz v5 [eat your heart out Jobs])
I've tried a couple of different ROMs recently and my phone keeps randomly freezing when I leave it idle.
I'm assuming it's one of the many apps I've got installed, so I'm wondering if there's an app that might help me find out what app is causing it exactly.
I've never used logcat before - but does this sound like the kinda thing it could be used for? Are the logs actually readable by a n00b like me?
Any advice appreciated!
Thanks
Already tried a clean install, without restoring a cwm backup?
Use Titanium to save your apps.
To view the logs of your phone you can use e.g. alogcat from the market.
did you found out what is freezing your phone? Mine is also freezing randomly. Is it better to flash android to your phone with CLK or MAGLDR?
This has happened on several different ROMs, each time i've totally wiped my SD and repartitioned it (with GParted) and also re-flashed with CWM.
sometimes logs get wiped or damaged when you remove the battery, so if you don't find logs useful, here's the hard way:
install apps one by one. Every time you install an app, leave your phone idle and see if it freezes. Use this as a last resort.
when you find what's causing the problems we'd like to know which app was causing the problem
Hmm just managed to log a crash (so to speak!)
The last entry in the log, before it crashed was:
--------------------------------
05-31 09:13:00.207 D/AppWidgetHostView(17704): updateAppWidget mInfo = AppWidgetProviderInfo(provider=ComponentInfo{com.levelup.beautifulwidgets/com.levelup.beautifulwidgets.ClockWidget41})
--------------------------------
So maybe it's my Beautifulwidgets that are causing the lock-ups... or maybe that was just a coincidence.... either way I'll carry on logging and see if a pattern emerges!
usally it's the widgetsthat makes your phone crash.
yz.hd said:
usally it's the widgetsthat makes your phone crash.
Click to expand...
Click to collapse
Yeah. Plus i've just done some Googling and it seems that other people have had issues when using LauncherPro (which i'm also using) alongside BeautifulWidgets...
Might have to ditch one of them!
I have to FC launcherpro every single time I turn on my phone on
Hmm annoying The last few lines of the most recent crash look totally unrelated:
--------------------------------
06-02 23:55:13.918 D/PowerManagerService( 241): New lightsensor value:40, lcdValue:83
06-02 23:55:14.918 D/PowerManagerService( 241): New lightsensor value:90, lcdValue:83
06-02 23:55:14.918 D/PowerManagerService( 241): lightSensorChangedLocked, buttonValue >= 0, mPowerState = 3
06-02 23:55:14.918 D/PowerManagerService( 241): setPenMenuButtonLed: 4
--------------------------------
For anyone that might also get a similar issue (or even cares) I've uninstalled LauncherPro+ and my lockups have completely stopped (just using bog-standard Sense now).
Pooper said:
For anyone that might also get a similar issue (or even cares) I've uninstalled LauncherPro+ and my lockups have completely stopped (just using bog-standard Sense now).
Click to expand...
Click to collapse
I've got Launcher Pro on my phone and it's freezing constantly.
No matter what Launcher I use, no matter what SD card, no matter what build I use.....freeze freeze freeze.
matt
Hey all,
I recently started using App Inventor to try to create a small app for my brother's beauty clinic (essentially a before & after photo app) for an ASUS Transformer. I have taken baby steps to have a button that launches the camera, and when I'm done shooting and hit ok, it should return the picture and set image1 (previously defined) to be that picture.
However, pressing okay does nothing. It stays in the camera app and refuses to return to my app. I also tried this on my N1 and it works fine, image1 shows the picture I just took.
Logcat from the Transformer:
Code:
D/Form ( 896): Form Screen1 got onActivityResult, requestCode = 2,
resultCode = 0
I/CameraComponent( 896): Returning result. Request code = 2, result
code = 0
I/CameraComponent( 896): Deleted file file:///mnt/sdcard/Pictures/app_inventor_1309992125941.jpg
Logcat from the N1:
Code:
D/Form (13091): Form Screen1 got onActivityResult, requestCode = 2,
resultCode = -1
I/CameraComponent(13091): Returning result. Request code = 2, result
code = -1
Any help would be appreciated!
Thanks