Looks like the folks over in the I9000 forums got tired of it before we did!
aditya_t90 wrote a simple little program available through the market that allows you to toggle the media scanner on and off!
Your phone will start up and it will still prepare media but it doesn't bother scanning it. The cons to this, is that your phone won't detect new music added to it (at least through the default media player), but you can rectify this by simply running the program and invoking a media scan. No more scanning after yanking out your USB cable or extra sluggish phone startups!
Just hit the market and search for: Rescan Media ROOT (Not the regular Rescan Media).
Zilch25 said:
Looks like the folks over in the I9000 forums got tired of it before we did!
aditya_t90 wrote a simple little program available through the market that allows you to toggle the media scanner on and off!
Your phone will start up and it will still prepare media but it doesn't bother scanning it. The cons to this, is that your phone won't detect new music added to it (at least through the default media player), but you can rectify this by simply running the program and invoking a media scan. No more scanning after yanking out your USB cable or extra sluggish phone startups!
Just hit the market and search for: Rescan Media ROOT (Not the regular Rescan Media).
Click to expand...
Click to collapse
Cool. Also the new leaked Captivate ROM is supposed to have a way better media scanner implementation.
Since I never really change anything on my SD card, I'm going to check this out.
I can confirm the new ROM is better... it's about as fast as it is in in the I9000 ROMS, which is to say: tolerable. But this makes it much better on any ROM
Zilch, thank you for this post! I was looking for something having to do with the media scanner as soon as I realized the media player doesn't find new music until I rebooted the phone.
have any of you had an issue with this app just hanging at the:
Doing Stuff
Hardcore background Kung-fu
screen?
Even when I type in the terminal command it hangs. My phone is fully rooted, and haven't had any issues.
I didn't have this problem, but one guy in the I9000 forums did, I'll link you to the comment from the author:
http://forum.xda-developers.com/showpost.php?p=7630532&postcount=16
Just enter that little code snippet into adb, apparently you only have to do it once and the program should run without any issues after that.
krakerx said:
have any of you had an issue with this app just hanging at the:
Doing Stuff
Hardcore background Kung-fu
screen?
Even when I type in the terminal command it hangs. My phone is fully rooted, and haven't had any issues.
Click to expand...
Click to collapse
I don't know much about the Captivate but you could help me out by opening my app while running adb logcat.
Then post the data you get from logcat.
Also are you running a stock rom or are you running a modified ROM?
Also does the Startup Manager work or does that hang too?
I'll try to fix it if I can. You are the first device I have seen with such a unique issue.
You know what's odd, is that I just reflashed to JM5 on my Captivate and went to reinstall it and I was having the same issue.
What makes even less sense is that after turning on debug mode the program ran flawlessly without me even having to terminate the task
Confirmed: I just turned debug mode off, ran it again and its hanging again. Toggled debug back on and it works again. Weird eh?
Let me sleep over it and I'll try and find a soln.
aditya_t90 said:
Let me sleep over it and I'll try and find a soln.
Click to expand...
Click to collapse
Thanks for the support! Hope this turns out to be an easy one
Turning on USB debugging was the key to getting this working on my Captivate running JH2.
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Um...I don't think you even explain you problem. Might want to elaborate a bit.
Sent from my Nexus 6 using XDA Free mobile app
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Andddddddd it stopped working again. Super legit.
Might be similar to my issue.
My camera started only showing front facing..even the option for back facing wasn't there. Did wipes in recovery and app settings. Would work, it seemed, but would revert right back to not working. At one point the camera app wasn't appearing in the app drawer at all even though it was shown in "all apps".
This occurred on stock and custom ROMs. I was advised to try flashing factory IMG but I'm well within the warranty period ( phone less than 2weeks) so I'm locking it back up and have a replacement on the way from ATT...
* I also noticed the issue starting while I was on bliss ROM 1.7
Sent from my Nexus 6 using XDA Free mobile app
My camera is really shaky and won't focus correctly in landscape mode. I returned the first phone I had for basically the same thing because it wasn't focusing in portrait mode but looked fine in landscape. I haven't seen anyone else have this issue. At first I thought the camera was inconsistent but if you zoom in you can see that it doesn't focus properly.
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
you better do it before its too late. id rma it.
cellularticulate said:
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Click to expand...
Click to collapse
There is no sdcard.
Try going back to factory sysimage, and data wipe.
Are you using any "added in" camera software? If so, what?
cellularticulate said:
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
Click to expand...
Click to collapse
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
I have only had issues with the stock camera app. Ive been running Pure Shamu for 2.5 weeks now and only using the Google Camera app from the play store (the one with HDR+ and the icon has the lens filled with rainbow colors) with absolutely no issues and only getting excellent quality pictures.
Had the issue where the camera wouldn't focus and everything on the screen gets jiggly and wavy like there's some sort of interference. I had motion sickness looking at the screen. Called Moto for an advance replacement and after a week of delay due to stock issue...somehow they were kind enough to upgrade me to a CW 64gb model. I hope it's new and no more camera issues.
Has everyone who got the 'no-focuse OIS' issue gotten new phone on RMA?
I took mine to repair few days ago and they said that they won't give me a new phone instantly, rather they try to fix the OIS. Not sure how that is going to work..?
They also suggested that this issue might be "self inflicted" or just an "feature" of the camera itself. fml.
Giants2010 said:
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
Click to expand...
Click to collapse
I returned mine to stock, unroot/locked boot loader, factory reset, before shipping it off and the camera issue was still there. Maybe hardware related I'm thinking.
Sent from my Nexus 6 using XDA Free mobile app
Something rather peculiar Ive noticed...
I didn't really pinpoint this until today, but the camera very consistently starts working when you go into fastboot, load the recovery, and then boot into system. I'm really, sincerely not quite sure why this would be happening, but I still feel like it has something to do with boot.IMG
If any devs can point me in the right direction to try and track down the possibility of this being an issue, I'd love to potentially fix a bunch of people's camera issues (albeit there is probably also a hardware defect direct from moto).
Is logcat going to pick up on issues that originate from boot?
cellularticulate said:
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Click to expand...
Click to collapse
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
cellularticulate said:
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
Click to expand...
Click to collapse
Ohhh man that is weird.
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
rdizzle707 said:
Ohhh man that is weird.
Click to expand...
Click to collapse
It appears a bit more stable now. I tried flashing twrp from my computer and it seems to be a bit more nice. That and normal reboot to twrp doesn't say 2.8.2.1 - let me check twrp manager now.
And my camera and flashlight have worked for almost three days now. Dafuq.
Same issue. "Unfortunately, Camera has stopped."
No flash light available, only front camera working, clicking on HDR exits the app with the aforementioned error message.
Has anyone solved this issue?
I was on 5.1 stock (with root) and now I've updated to 5.1.1, but with no change to the Camera behaviour.
I just downloaded the Android Studio. I am running windows 7 64 bit with 4 GBs of Ram. When I open the application it takes a few minutes to load the studio. It then loads to an error that says there was a rendering problem which I fix by changing the API from the drop down. I put 3 labels on the app and just wanted to see what that looked like so I tried running it. I ran it through the Emulator and after basically freezing my computer up and taking up to 5 minutes to build it works but then I see a blank screen. I don't even see my labels. So I tried running it from my phone and after a few hours I finally got it to where it would even recognize my phone as authorized. However, every time I try to run it it says the app has crashed before it even loads. I am using a Samsung Galaxy s3 so I tried it with API 17. So here are my questions.
#1:
Why is this program soooooooo slow? I have changed the gradle to be offline. I have also added this line to the properties org.gradle.daemon=true and still it takes forever and almost freezes up my computer.
#2:
Why aren't my labels showing when I run it through the emulator? I mean that's about as simple as you can get and it isn't even working.
#3:
Why does my phone crash before even loading the app? I have 32 GB of memory on my phone via an SD card if that even matters.
#4:
Can this program really be as bad as it seems? I've been "working with it" about 3 days now and I can't get it to function properly in any way.
4GB is barely enough for comfortable work. Especially on 64-bit OS and especially with emulator (and maybe browser tabs and some other stuff) running.
Although I used to launch it with 2GB somehow
And if your app doesn't work properly and even crashes, it's most likely bugged. Read the log.
Hello,
I have Redmi Note 10S with official MIUI system and all current updates. Actually since the beginning I had issues with Chrome browser which was crashing and rebooting the whole phone. I thought it was an issue with the browser itself so I tried different one. Unfortunately on Firefox it was crashing and tebooting the phone too. The only browser, which works fine is the one provided with MIUI. I tried with cache cleanup and browser data removal. But because it happens on two indepented browsers it must be something on Android (Android System WebView?) used by both browser. Can you help me?
is it for some special page?
im using chrome beta from the beginning without problems.
can you do adb logcat? it would be great to see what error do you have
No it seems to be random. It can work for days and then suddenly crash. I will try with logcat but the randomness can be a problem.
but rebooting whole phone is not possible by application crash. it is usually HW problem.
me as a developer to reboot device, i need to have root.
there is no function to reboot phone.
so maybe try some benchmark app to see if there is no hw problem
I have checked with Geekbech 5 and it works both for CPU benchmark and Compute Benchamark (OpenCL). And just to clarify because I'm not sure if reboot is a proper word. When loading some website in the browser the screen goes black and the phone is turning on like it was switched off. I would compare it to BSOD on Windows.
is there whole boot? or just immediately pin screen?
still had no issue like this
The screen goes suddenly black and then the MIUI is starting to load. It is exactly the same process as you would press longer power button and selected Reboot option. But it just happens randomly without user interaction when using Chrome or Firefox.
I tried with logcat but so far without success. The browser didn't want to crash this time.