Database Users

Camera problem

A strange problem has suddenly appeared.
When I start the camera, after a while performing the loading icon, the cycle in the center of the screen showing that the device is working, the following error appears :
Unable to start preview mode. Internal error 36001:101:1
Has anyone got any clue?
I use the camera rarely, and since the last time I used it, I have installed and uninstalled various applications.
Sound really strange to me, so any clues will be appreciated !

The problem may come from some pisture viewer software such as Resco or spb imageer.
That program is set to use as default viewer for picture image.
The resolution for this problem that i can think is install CAMERA again by extract file from Ext ROM and install again in your device.
or You may try hard reset first. If problem still occur .you may need to flash ROM again.

It may also be caused by a movie player or something that uses the ATI hardware chip. Does the error only occur after you have played a movie or something? Try closing all running applications prior to starting the camera and see if that helps (if you have a movie player running, close it using its own exit option so that it 'tidies up').
Failing that, does the camera start OK after a soft reset?

The problem may come from some pisture viewer software such as Resco or spb imageer.
Click to expand...
Click to collapse
It may also be caused by a movie player or something that uses the ATI hardware chip.
Click to expand...
Click to collapse
I have none of the applications you mention installed on my device.
I even deselected all applications from my today screen, soft reseted the device and still have the same problem.
Thanks a lot for your suggestions.

Certainly sounds strange :? What version of ROM have you got installed?
Perhaps re-installing the Camera app will fix it. This is in the Extended ROM.

I have 1.72 installed.
I agree with you.
I think I will have to reinstall the camera application

unhandled error in the shell?

Every so often I get this message:
"An unhandled error has occurred in the shell. Attempting to restart the shell."
The only thing I can do is hit OK and it restarts. This is my second wizard and the first had this problem as well. I thought that it might be the registry edit that I made to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shell\Rai\:WMPLAYER
I changed string 1 to replace wmplayer.exe to another program but changed it back in an attempt to fix the problem but I still get the same error.
Any ideas?

Any chance you're trying to close the programs app or the control panel (proper close, not OS minimise). This also causes such a crash.
V

Hi Vijay,
I am also gettign this error, except mine only seems to happen EVERYTIME I close the Program Folder.
i am runing a Vodafone VPA Compact III (TYTN)
Any Ideas on how to fix this?
Thanks.

Yes, don't close the programs folder. VJOkButt has exceptions for the Programs Folders and Control Panel and other system folders, because closing them crashes the OS.
So as Beverly Crusher would say, "don't move your arm".
V

i g3t this also
i also get this.. not all the time but when closing file explorer i dont kno what it could b?

i started getting this a few weeks back. after readuing this post i can confirm it happens when i close my "Programs" folder. what gives???
any help is appreciated
thanks

This recently started happening to me too. Until 2 weeks ago i had never seen tis, not it happens every day.
It seems to happen under different circumstances, but often when i am using Opera.
The odd thing is that i have not changed and settings or installed any new apps...
...however, i did start happening around about the time it started experimenting with over clocking. I have since stopped overclocking, but still get this.
It damn annoying, i really do not want to do a hard reset.

the hard reset will not help. I also re installed the rom and still got the same message. this is really weird.
i guess there is some file somewhere corrupted.
as I played with the phone, I realized that the HTC X button, when set to close the apps, it causes this issue. so I uninstalled it. and I get no more popups.

It has started happening to me too and I have pinpointed it to trying to close the programs folder before the icons load. Any fix available yet?

Help with memory leak

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

[SOLVED] Eris "Undead Call" Problem (AOSP/Froyo/GB) Fixed!

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])

How to find out what app is causing my phone to freeze. Logcat?

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