yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Accessories] alphasports:
Yesterday I received both the OEM rubber case and the OEM flip cover, and while the flip cover is kind of awkward for day to day use plus has no back protection (the replacement back is attached to the flip but is an exact replica of the stock back), for laughs I tried putting on the OEM skin at the same time as the flip, and it worked more or less fine. The problem of course is the volume buttons become hidden by the flip "hinge" as well as the rim of the skin case, but a little surgery should fix this, then you have a very nice full-body suit of armor.
[Galaxy Note II Accessories] phreshjoker:
What did you use to cut it out?

Sent From the Van Down by the River
[Galaxy Note II Accessories] brodypie:
Are talking about the samsung protective + case when u say OEM rubber case?
[Galaxy Note II Accessories] Corki2:
I used a small pair of scissors to cut my rubber bumper.
[Nexus S Q&A, Help & Troubleshooting] the1dynasty:
I rarely start a thread and i typically search first and i did that already but couldn't find an answer or someone else with the issue...

So my problem is simple but annoying... When i snap a picture with the stock camera app and flash turned on, randomly my phone shuts off and will NOT turn on again until i do a battery pull... I say randomly because it doesn't always happen... But it happens quite often...

I haven't tried with a 3rd party camera app because I prefer to use stock apps mostly... So I'm not sure if its app related or hardware related... I'm leaning towards hardware because I've had this issue since running 4.1.2 ROMs and I've tried multiple stock/modified camera apps to no avail... Currently on 4.2.1 ROM with of course the 4.2 camera...

Torch toggle works fine, as well as turning on the flash while recording video... This ONLY happens when the flash comes on for taking a photo... And again it only happens randomly...

Anyone else experience this or know how to fix it?
[Nexus S Q&A, Help & Troubleshooting] jayjay3333:
The first thing I would do is flash factory Google. This will rule out it being a ROM issue. If the problem is so there then yes it is a hardware issue.
[Nexus S Q&A, Help & Troubleshooting] the1dynasty:
Great suggestion... I'll try that when i have a computer to back everything up and make sure i can root again!!
[Nexus S Q&A, Help & Troubleshooting] polobunny:
I've seen that happen with a bad battery once. Would occur more often at low charge percentage too, but was relatively fine at 100%. Took a while to figure out what the heck was going on :P
[Nexus S Q&A, Help & Troubleshooting] the1dynasty:
Strangely, it was doing it before i got a new battery a couple months ago... I sorta felt my battery was bad so i went to get a new one from the sprint store... The guy said because "It was rooted and the phone had so much awesomeness.." it was draining the battery faster... I told him a quick reason why i thought it had to be the battery and he just gave me a battery from the drawer without doing any paperwork or anything... My battery wasn't feeling any better after the change and i still had issues with flash...

I think I'll just take some photosphere pics and well lit shots... Who needs flash anyways? Lol
[Nexus S Q&A, Help & Troubleshooting] Gambler_3:
I have the EXACT same issue however long pressing the power button turns on the phone instead of pulling the battery. It also started happening to me only on jelly bean. My GF has the same problem.

I can also tell you it happens with camera zoom FX as well but this cannot be a hardware issue since it only happened in jelly bean. It cant be that "suddenly" our phones developed a problem.

Is nobody using a nexus S to take photos or what? Or is it just a few unfortunate users affected by this? :confused:
[Nexus S Q&A, Help & Troubleshooting] the1dynasty:
Thanks for that post... Now I know I'm not alone here lol... I too noticed it with JB... Its %~°^¶©£ annoying... I wish a dev would look into it... I think it may have something to do with the flash having that instant jolt of high voltage... Idk because I'm no expert... I found a 50/50 chance of making it work correctly... If you hold the shutter button to let it focus, then let it snap, there's a chance it won't shut off... Just something to try and see if it helps!!
[Nexus S Q&A, Help & Troubleshooting] the1dynasty:
just did a complete factory restore back to 4.1.1 unrooted and everything... forgot to test the camera... i rooted again and installed custom recovery... tested camera out several times... no issue at all... tested some more... no issues... decided it WORKS!! so i flashed cm10.1 and updated everything again... tested camera and OFF!!! FU%$&*&@&#&^$%$^@&$^&$^^%$#^%@*@*@&&#^*&@^#*&^@#*^ i'm at a loss for what to do here... i'm glad one other person reported this... but there HAS to be more people out there with this issue...

test it... make sure flash is ON and snap a few pics... maybe a close pic out of focus, etc... idk what else to do... it worked fine unrooted...
[Nexus S Q&A, Help & Troubleshooting] PartimusPrime:
I've had this issue happen randomly to me too...but usually only when my battery is low. And it is VERY annoying when it happens.
[Nexus S Q&A, Help & Troubleshooting] the1dynasty:
doesn't matter my battery level... it happens on my charger too lol...
[Nexus S Q&A, Help & Troubleshooting] Gambler_3:
I didnt have this problem last night on a wedding thankfully as that would have been embarrassing, lots of pics were taken with flash. Its the sheer randomness of this that it makes it so hard to diagnose. :S
[Nexus S Q&A, Help & Troubleshooting] javi.heiwa:
I've been having exactly the same problem. I cannot relate it to Battery Levels, as the battery drains sooo fast since I got the ICS upgrade.

I am now on the Factory ROM 4.1.2 and it is all problems. I am thinking of going back to Ginger Bread... them were the days!!!

J.
[Nexus S Q&A, Help & Troubleshooting] the1dynasty:
if you read above, it worked fine for me when i flashed 4.1.1 factory image... something to do with 4.2 i guess... idk... i'm not stressing it so much... i've learned not to use my camera when its dark or low light lol...
[Nexus S Q&A, Help & Troubleshooting] ejohn3288:
have the same problem

Do you have a link to the stock 4.1 ROM?
[Nexus S Q&A, Help & Troubleshooting] the1dynasty:
it wasn't a ROM, it was the factory image from returning the phone to stock with the program i used to root it... i've given up on pictures with this phone haha
[Nexus S Q&A, Help & Troubleshooting] LexApp:
Its a Battery Problem

I'm suffering from this same issue and after downloading several camera app to no avail, the issue is finally resolved. From my experience, I can safely conclude that my was a hardware battery issue. At first I didn't believe it was a battery problem. I decided to go to different stores and tried several batteries but all shut down the phone when the flash on/flash auto + taking a snap is executed. Then, I pulled out the battery from my friend's brand new S3 and inserted it in my phone's battery compartment, fire on the phone and voila the camera flash worked like a charm without shutting down the phone. I used the same old battery on the new S3 low and behold, the new S3 inherited the flash+camera=shutdown issue instantly.
[Nexus S Q&A, Help & Troubleshooting] musikah_1989:
Same Issue on SGS2 Hercules

Having this issue after flashing a ROM on my GS2 Hercules, good thing I only experience it when my battery level is below 25%. But it would really be a pain if I would want to take a picture with a flash while my battery is low.

Have anybody tried other solution or troubleshooting aside from trying a different/new battery.
[Nexus S Q&A, Help & Troubleshooting] Rookie91:
similar problem here...

the same thing happens to me, but with the difference that i run stock 4.1.2 rooted, and when the phone die after the led flashes, i just press pwr button and the phone turn on like never was happened.

i think it's a problem of corruption of something in the system, if i do a factory reset, for some limited shot the camera+led works, after that the phone die instantly.

similar problem with front camera, if i switch from back to front the camera service crashes and i can't do anything for make it working (manually stop the gallery process, reboot, cleaning data of gallery process), just wait some days and the process came back working (just for the rear camera).

sometimes i notice that while the stock camera app doesn't work, the Whats app camera keep working also with flash!
[Nexus S Q&A, Help & Troubleshooting] towelboy:
same issue with the nexus 5.. taking pictures works and then suddenly shuts down the phone, the power button can't wake the phone and the only way to get it to turn on is to plug it into an outlet.. very annoying.

that said I looked around the forums and it seems like a hardware battery issue, when the voltage supplied is too low or high or something
[Nexus S Q&A, Help & Troubleshooting] lycan_warlord:
flash has caused my phone to shut off.

got GS3 SCH-i535 I've noticed the flash causing the screen to black out completely and shut off phone. I usually have to pull battery. its done it on 4.2 and 4.3 probably even 4.1 i dont remember I'm currently running 4.4.2. it just did it again which has prompted me to look online. as glad as i am to know im not the only one. is there any ****ing solution???
[HTC EVO 3D] NexusS4gFreak:
Anybody know how to fix app associations in ROMs such as Viper? I remember seeing somewhere that you had to edit build.prop and it worked but unfortunately i forgot.
[Epic 4G Q&A, Help & Troubleshooting] zetterwing:
I recently have had an issue with my sd card becoming unreadable after a few hours. After rebooting it reads fine but within a few hours the system fails to access it. I have done a bit of searching and see that it could be corrupted data. Before I go and format is there anything else on the software side I can check? It is a 32 GB card that I got in August. I haven't tried putting in the old card since I am not sure the data on it is up to date with my current setup. I'm running Paranoid Android 2.54 currently. Any ideas?
[Epic 4G Q&A, Help & Troubleshooting] tazfanatic:
As a test put your old card in just what happens. Unless you partition your SD card it won't make a difference on your setup.
[Verizon Samsung Galaxy S III] camero6989:
I've had my S3 for a while, rooted & was running KOPA. Decided for a change so I loaded up CM10 . In the process I realized that no computer will recognize my S3. My phone will charge from a USB port, but it won't even give me a unrecognized hardware message. It's like nothing is hooked up. I've tried it on 3 different computers, two with USB drivers installed, one without. Also on two different USB cables. I'm worried I that some how damaged the data connection on my phone. The problem is, I cant even factory default it via Oden without a operating USB cable. Very aggravating. Any thoughts?
[Verizon Samsung Galaxy S III] bdubb40:
Try to turn off debugging
[Verizon Samsung Galaxy S III] kintwofan:
Do you have fast charge enabled?

Sent from my SGS3 running Eclipse 2.1
[Verizon Samsung Galaxy S III] Terry_blair:
Same thing happened to me(several times)..restarted my computer then it worked
[Verizon Samsung Galaxy S III] StrumerJohn:
Samsung made horrible USB Drivers for this device.

Try one of the following:

1. Remove the USB Cable from both the Computer and The device

2. Plug it in to a different port

1. Uninstall the drivers for SAMSUNG USB MOBILE DEVICES (or something similar) in the control panel

2. Plug in the device and wait for generic MTP drivers to install

1. Use the Camera Mode on the MTP options in the Notification Bar

2. Plug in device to computer; however if transfering ZIPS, it may fail so you'll have to resort to the other steps.

Good luck!

- Rebooting the device and computer can also fix it.

- And these fixes ARE NOT permanent.
[Verizon Samsung Galaxy S III] bobAbooE:
I have had good luck with the Xperia x8 drivers. Been using them for weeks.
[Verizon Samsung Galaxy S III] camero6989:
Sorry, I saw the Q&A section after I posted.

- USB debugging is off

- Tried restarting

- Tried uninstalling / re-installing drivers. Also tried uninstalling and plugging it in without the drivers to see if it would recognize the device

- Fast charge is not option in CM10 as far as I can tell

- Tried every USB port in ever computer I have available to me. plus 2 different USB cables.
[Verizon Samsung Galaxy S III] MrBrady:
I've had this happen frequently recently. What I noticed fixes it is booting into Downloader mode (hold down Home + Volume Down while turning the device on). Once in Download mode, press and hold the power button for 10 seconds or so and the device should restart. USB connected fine afterward.
[Verizon Samsung Galaxy S III] camero6989:
Problem solved. Looks like it is a Hardware issue. Tried one more USB cable. Figured out that if I wiggle the cable and push it as far right as it can go I get a connection. I've never liked how loose the USB port is & think it is part of the reason it is now damaged. I will be getting a touch stone to preserve the connection as long as I can. Thanks a lot for all the help.
[Sprint HTC EVO 4G LTE] gtszzz:
I assume I'd need to root, which I'm working on in just a bit, but is there a way to make my EVO be recognized as a pc to web sites? Where I'm going with this is some sites like Hulu, slingbox, etc will only let you view things on a PC, or will make you pay for an app to run it on any device other than a PC. I want to be able to run these through my browser and have the site think it's just going to a PC so it will allow it.

Thanks so much for any help!
[Sprint HTC EVO 4G LTE] tekno4ever:
Yes... Certain browsers like Dolphin Browser allows you to change your user agent which will make ur phone appear as an iPhone, Windows desktop and so on.

Hit the Thanks button if this helps you
[Sprint HTC EVO 4G LTE] scoot0073:
Maxton Browser which I use gives u the option to load page in Pc desktop mode and other different modes.

Same with Google Chrome.
[Sprint HTC EVO 4G LTE] detcup4evr:
The stock one will allow you to do it as well, type about:debug in address bar then go to settings find ua string and set it to desktop

For hulu to work ur need a hacked version of flash, as hulu does a couple checks, I attached one from captain throwback below,
[Sprint HTC EVO 4G LTE] gtszzz:
Thanks guys, It worked, kind of. I was mainly trying to get slingbox to work. I tried the Dolphin browser and that worked other than now it needs to be able to download the player to view and from what I see it's trying to download one for windows but the player won't work on the droid so I would have to download the app anyway.
[Captivate Q&A, Help & Troubleshooting] southernblonde:
I feel like an idiot after reading this forum for the last couple of weeks. My problem started when I really wanted Jelly Bean on my i897 instead of the stock Gingerbread. I found out I failed to install Cyanogenmod and ended up with a phone that could no longer go into download mode, couldn't get into recovery, my laptop no longer recognized the phone and when I powered up the phone it was bootlooping on the AT&T screen.

I ended up buying a jig. It came in the mail today and I got into download mode and using Heimdall flashed I897UCKK4 Stock, NO Bootloaders, Wipe-One-Click.

I wanted to root my phone so I flashed Corn Kernel. My phone didn't go into download mode (it showed the battery charging when I tried) so I had to use the jig to get into into download mode. When I tried to get into recovery, it bootlooped on the AT&T screen. And I noticed during a normal power up of my phone, right after the AT&T screen, I see rainbow colored lines.

I asked someone who has been nice to enough to help me these last couple weeks and he said that the garbled lines mean I'm trying to use a gingerbread kernel and I don't have gingerbread bootloaders. Would the easy way to fix this is to use the same Heimdall One Click I used flashing the same stock and CHECK flash bootloaders this time?

Thanks for your help in advance!
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
No...u need the one with bootloaders option included...because if the one u have is the one i packaged then the bootloaders are not even included in that package, so even if u chose the bootloader option it would not work.

And if i remember correctly, even with the Heimdall One Click that has the option to install bootloaders etc., it will require two flashes to get the bootloaders. The first flash installs the firmware and then the second installs firmware with the bootloaders. That is just the way it is with heimdall. Just follow the promps and u should be good.

There r other ways of gettin the i897 gb bootloaders of course. The Odin kk4 one click that contains them that i put together in that same one click stickied thread in the dev forum. Also TRusselo has a download of them alone in his Guide that is a stickied thread in the q & a forum. See his op for them.

And etc. etc. :thumbup:
[Captivate Q&A, Help & Troubleshooting] southernblonde:
Will that solve my problem of not being able to get into download mode or recovery, by adding the bootloaders this time? I don't want to brick my phone, although I've been reading that its nearly impossible to brick. ha

Thank you.
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
Yes the i897 gb bootloaders have solved users problems with button combos to get in download and recovery mode.

But always be careful flashin bls. Mixed matched bls or bad flash of them...loosin power to ur pc during the flash of them or loosin connection of ur usb/micro usb cord during the flash will possibly hard brick ur phone.

So just be sure to have a constant power source, reliable usb/micro usb cable, and don't interupt the flash during the few seconds it takes to install the boot.bin and sbl.bin files. And once u have installed the gb bootloaders there is absolutely no need to flash bls again. If u ever need to flash back to stock just use kk4 with No bls.

Keep us posted on how it goes...
[Captivate Q&A, Help & Troubleshooting] southernblonde:
I downloaded the Heimdall package WITH the bootloaders this time and my phone is having the same problems. I watched it flash twice but I didn't notice Heimdall installing anything different the second time. Was I supposed to check "flash bootloaders" at any time?
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
Yep. That gives permission for the install of the bootloaders. Check it before u begin the flash.
[Captivate Q&A, Help & Troubleshooting] m1batt1:
My personal preference is to do an odin flash of just the bootloader package from here http://xdaforums.com/showthread.php?t=1350266 ... I bought my wife a cappy about a month ago and was trying to do a one-click to kk4 w/bl and it kept hanging. After a lot of fighting with it I ended up just flashing to bootloader package and then a custom kernel and all was good.
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
Yep. Some of the Captivates do not like one click packages. Mine is a 1009 build and thankfully has not had a problem with 'em.
[Captivate Q&A, Help & Troubleshooting] southernblonde:
FIXED! Thank you so much. No more rainbow pixels, I can get into download mode and recovery now.

I was following the instructions word by word cuz I didn't want to screw anything up and it didn't say to check the box. I'm ignorant.

Thanks again!
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
^ :thumbup:

Glad u got it. Now off u go to get ya some jellybeans. :D
[Captivate Q&A, Help & Troubleshooting] m1batt1:
WOOOO JellyBeans!!!
[Captivate Q&A, Help & Troubleshooting] southernblonde:
Ha! Watch me screw it all up again. But its all good cuz I've got a jig now, I feel a lot safer.

I think my lack of knowledge regarding Odin and Heimdall on the same computer probably had something to do with my loss of the laptop being able to recognize my phone. I learned that I need to stay away from Odin, it never worked right for me.
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
Haha...u ought to be fine. Just remember, no need to flash bootloaders again. And the only other possible thing to be concerned about is the "Encryption Unsuccessful" error that has happened with users of this phone and several other phone models. There are two threads in the development forum if u wanna know more about that subject. Other than that the Captivate is a really tough phone. I have enjoyed mine for over 2 yrs now.
[Captivate Q&A, Help & Troubleshooting] m1batt1:
One thing I will mention is this... Coming from any other version to Jellybean, when you do the initial flash of the ROM it will either reboot automatically or show that the flash completed really quickly and then you'll reboot thinking you're installed. Either scenario will likely land you in a boot loop. Don't freak out because this is normal when you are first flashing to Jellybean. Its because of the partition layout differences and it just requires a reboot. Just get yourself back into recovery and flash everything again and all should be good.
[Captivate Q&A, Help & Troubleshooting] southernblonde:
Is Cyanogenmod supposed to be installed before I flash Jelly Bean? I'm going to be using Slim Bean. Thank you!
[Captivate Q&A, Help & Troubleshooting] BWolf56:
No, just flash Slim Bean twice. Flash the first time, get back in recovery and reflash Slim Bean right over it.
[Captivate Q&A, Help & Troubleshooting] southernblonde:
The first time I attempted to flash it, when it rebooted, it was stuck on the AT&T screen forever. I didn't know whether or not it had froze or not so I took the battery out, powered it up, and then it started bootlooping between the AT&T and Semaphore screens.

I should have put it back into download mode again and reflashed it?
[Captivate Q&A, Help & Troubleshooting] BWolf56:
No, you go back in recovery and reflash it. The first time, it needs to rewrite the partition so it won't fully flash. After the first flash is over, you get back in recovery and flash right over it (what we call a dirty flash). Then it should boot up just fine!
[Captivate Q&A, Help & Troubleshooting] southernblonde:
You guys are so smart, its sick :laugh:

I was just reading over Slim Bean installation and it says I need to boot up with CM9 or CM10. Is it still necessary to install it? Since I'm coming from Gingerbread. Here's where I read it at: http://www.slimroms.net/index.php/installation
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Can't see that page as I'm at work (yay for Gov's internet..)

As long as you have the GB bootloaders, you don't have to worry about much. Just make sure you have a cwm recovery (often gotten from flashing Corn kernel with Odin 1.85). But if you are already on a custom GB ROM, you don't have to worry about that.

Next is to factory reset, clear cache and dalvik in recovery and flash Slim Bean (Twice*) and finally the Gapps.

The process is the same for pretty much any JB ROM.

I'm a bit confused though, did you already flash it or not?
[Samsung Galaxy Nexus] cartisdm:
I have been in love with all things Android for years but there is a certain level of proficiency that I don't think I'll ever reach. I'm reaching out to anyone who can provide me with some assistance in this issue. I have a Nexus (my wife's) that constantly crashes the Talk and Camera apps. I've tried dozens of solutions posted online but I think the only one that actually addresses my issue is provided in the link below. Unfortunately, when it comes to compiling Android source code I get in over my head.

Could someone please give me instructions on how to implement this fix? I would like to run AOKP JB Milestone 1. It appears I need to swap out the binaries before compiling and flashing this ROM but that's about as much as I can tell.

Please help!

Link describing the fix -------------> http://anders.com/cms/435