yashsingh1/xdaforums huggingface dataset:
[P3600 General] jeffbeach:
I wound uptaking my 810 back to the Dopod service center. The guy said they had to replace my camera. What that means and if that can actually be done I am not sure. I would guess they replaced an entire board. They did re-flash the ROM on my phone as well. Prioir to taking the phone in for service I had not tried to re-flash the rom. I had only done a hard reset with no success.

One side light of my camera going down is... They put the same ROM back on my phone that was previously installed. After the service I have noticed that my GPS gets a "cold" fix much faster than before (twice as fast +/-)
[P3600 General] eldaria:
Interesting, I had this exact same error, but on my previous phone, a Samsung D900.

They tried everything, including completely wiping the phone, but nothing helped so in the end they replaced the camera in the phone.
[P3600 General] landwomble:
i had this on a tornado

...turned out to be hardware, too.
[P3600 General] timmey78:
mainboard error on mine

htc service replaced the camera module twice before they replaced mainboard and cured my phone. I had this problem the first 6 months with my p3600.

Try taking a softreset with the camera on. this worked for me a couple of times

Regards
[P3600 General] Hobbit_CZ:
Possible solution

Possible solution http://xdaforums.com/showthread.php?t=384854

Simply take out battery for at least 15 minutes.
[P3600 General] xiance78:
Having the same problem but on front camera ..

Hi,

I having a similar problem but with my secondary (front side) camera. I'm using Dopod D810 with WM6.0.

So, any solutions on this ?

Regards,

Daneal
[P3600 General] sirus.ss:
I have problem Unable to start Camera in htc desire 500

I reset factory but I have this problem. I don't known.what can I do???? please help me

this my number phone 09192561895 in IRAN
[Nexus 7 Q&A, Help & Troubleshooting] justinxfan:
I downloaded the m-kernel zip a75 (lollipop 5.1.1) and flashed it through cwm. It reported a successful flash. I rebooted and it went to the google screen, then the boot screen, and then.......... the horrid optimizing apps screen! So, I waited for the apps to be optimized, and then it reported starting apps. The window closed and I expected it to boot but up but instead met by a brief NFC thing failure message and the device went back to the bootscreen and started doing everything over and over again. Please help! I really don't want to reset my device! Why isn't it working and what should I do?
[Nexus 7 Q&A, Help & Troubleshooting] fwayfarer:
youre beat. i did the same thing. the kernel does not work with 5.1.1 so unless you TOOK A BACKUP BEFORE FLASHING there is nothing you can do but reset.

you can try reflashing the rom without wiping the data partition, or restoring only the BOOT partition from backup. it will work, thats what i did until they get the kernel situation figured out. youre not the first to encounter this.
[Greenify] ticktock666:
This is a recurring problem for me Every time I update/switch roms, the donation package goes bananas, but this time nothing seems to be working.

after getting the LP update for my Z2, I did a clean stock flash, with full device wipe (including internal storage), all of my other apps work fine except for Titanium Backup and Greenify, after I install the pro key and I get the "thank you for your donation", I open the app and get a message about being unable to connect to google and to recheck my internet connection.

I've tried uninstalling/reinstalling the app and the key, did a full wipe reinstall of stock rom and many others (AOSP/CM) but always getting the same results, so I'm not sure what else I can try to get this to work, I've reported this on the app/key pages on the store but still no response.

I've also tried the solutions mentioned here and the Amazon fix from here, but neither worked, once I update to the latest greenify version from the store the donation key stops working.

I hope the dev can help on this issue, as it gets really annoying after a while.
[Greenify] harrymason37:
Make sure you're using the same account which you bought it
[Greenify] ticktock666:
First sorry for the late reply.

Second, how would I be able to download the donation key if I wasn't using the same account in the first place ? I appreciate the attempt to help, but this is not device related, not a local issue since it persists over many flashes of different roms.

When I open the app and go to the Experimental features, I get a "can't connect/error 291" in orange at the bottom, I've tried everything but the app either doesn't see my wifi or it doesn't want to see it, this seems to be an issue shared by greenify and titanium (at least for me, although both app pages are full of the same complaints from other people).

The fact that I can easily find a "working" full version online, while my own paid app won't work properly says a lot of stuff, at least IMHO.
[Greenify] ticktock666:
well, I've had it with the app, I've COMPLETELY wiped my device, and Only installed this app with xposed and donation key, but I keep getting "network error 291, please check your connection", even though I'm connected and installing other working paid apps from the store, so this obviously an app issue.

I really liked the app, but the response from the dev team is non-existent (3 weeks and not even a response from the dev) , so I'm gonna try to dispute my purchase with google, no use having the purchase if I can't use the app.

I can totally understand this attitude if the app was free, but tbh when money is paid service should be provided, or at least a level of courtesy.

I hope the dev will move to a different payment confirmation method, because this one is outdated and is causing issues for the apps using it (see titanium too).
[Greenify] TNSMANI:
May be the Play Store is acting up. Try rolling back to a previous version. Wipe data and cache of Play Store and then try to enable the Experimental features of Greenify. Check the following:

http://xdaforums.com/showthread.php?t=1566770
[Greenify] ticktock666:
not likely, since I've tried with the stock store in the Sony latest rom, then updated to the latest store/services available, but still the same result.

other purchased apps I have work normally, : Lux, cfLumen, listen audiobook and others, the only ones that are not working are greenify and titanium, which use "pro key" apps.
[Greenify] oasisfeng:
Recent beta versions fixed some donation package related issues. Have you tried the latest 2.6.2 beta 7?
[AT&T LG G3] eriqjaffe:
Lately, my proximity sensor has been giving me trouble - at least, I think it's the proximity sensor. The symptoms:

1) I can't unlock the phone unless there is enough ambient light. Generally not a problem, but a little inconvenient.

2) As soon as I start a call, the screen goes black and will not turn back on no matter what, making it impossible to bring up the dialpad or hang up. I've enabled the "power button to hang up" setting, but it doesn't seem to be doing anything. The only way to end a call is to wait for the other side to hang up or remove the battery. The former is fine if I'm actually talking to a person, but if I get into an auto-attendant tree I'm screwed. It happens regardless of whether I'm holding the phone to my face or not. Flat on a table, same behavior.

The phone is rooted, are there any apps or things I can do to verify that it's the proximity sensor? Is there any way to just disable the proximity sensor in software?
[AT&T LG G3] samsat:
Use the hidden menu (3845#*850#) and go into device test.

There is a proximity sensor test there. As you move your hand near the sensor it wall say near and as you move it away it will give you a light reading.
[AT&T LG G3] eriqjaffe:
Thanks - the top always says "Proximity: NEAR". The bottom one says "Light: off" If I wave my hand hear the sensor, it turns blue and give me a reading hovering around 10. Closer to the phone and it's red and gives me a lower reading. Holding my finger on the phone, completely blocking the sensor, gives me the "Light: off" reading again.

I'm not quite sure what to make of that.
[AT&T LG G3] Nakhon7:
I've had similar problems with my international version G3. Both times I have had to take off the back cover, remove the various screws around the top half of the phone, pull off the plastic casing, and then use compressed air to spray out the area around the proximity sensor. After this the phone works fine for a month or so.

Somehow dust seems to be getting into the phone quite easily. I'm wondering if the area around the speaker grill is not fully sealed.
[AT&T LG G3] eriqjaffe:
I finally took the time to disassemble my phone and sure enough, the proximity sensor was filthy. A couple seconds with a can of compressed air and things seem to be back to normal.

Thanks!
[AT&T LG G3] Kaylamichell3:
I have a lg g stylo the sensor is so sensitive .. I wave my hand over my phone and the screen goes black I am trying to figure out how to turn it off ..
[AT&T LG G3] TheMadScientist:
If it does become a problem there is an exposed module just for diabling prox sensor
[AT&T LG G3] devilonway:
Proximity Sensor Issue Solved

Just opened the Mobile yesterday night, and after a little hectic; i had managed to clean the dust from board sensors.

Working Perfect now, like a charm !
[One (M7) Q&A, Help & Troubleshooting] haykweb:
Anybody have this problem?when i updated programs in play market (Android system webview, htc service pack,etc) my infrared remote port stopped working.not working my remote controls for TV and my audio system. My ROM is MaximusHD 52.0 with kernel ElementalX 20.1
[One (M7) Q&A, Help & Troubleshooting] Val D.:
Uninstall the updates, reboot the device, clear cache. Is IR working again?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] wolfc86:
Hi there. I was prepping to install JasmineRom 5.0.2 tonight but messed up and am hoping someone can help.

I was coming from Eclipse 2.2 (Android 4.4.2) with the NC2 firmware (http://xdaforums.com/showthread.php?p=53508270#post53508270).

I booted into Safestrap and did a full wipe, but I got the error "E: Unable to mount internal storage". I then rebooted recovery thinking it would just reboot me back into Safestrap so I could try wiping again. Instead it booted me into what I guess is the stock recovery and now I can't get back into Safestrap.

Any thoughts? Everything is the same, I just lost my ROM. Any way to ODIN back to a working rooted state to try again?

Thanks!

Edit:

Since I'm on the NC2 firmware, could I just do the following?

1. ODIN the NC4 Stock Tar.

2. Root with Towelroot. Install Busybox, etc.

3. Install Safestrap 3.75.

4. Pickup where I left off with trying to install JasmineROM 5.0.2

Edit 2:

Alright I recovered with stock NC4 and re-rooted with Towelroot. Common knowledge to the rest of you, I'm sure! Sorry for a dumb post! Mods, feel free to delete.
[Sprint Samsung Galaxy S6 Edge] Alpine-:
What's the deal? I'm using the stock charger and it doesn't say fast charging. In addition, no way to enable it under battery settings.

Did sprint disable it temporarily by default? Read there were some heat issues causing fast charging and s6 Edge issues. Maybe they disabled it until new firmware? I got one of the newer inventory models that is the platinum gold-colored 32gb that was not available until 4/27. I'm on build OCF, says it's fully updated. Perplexed because I've read the battery options shows a toggle for fast charge (which mine doesn't).

Someone educate me!
[Sprint Samsung Galaxy S6 Edge] Alpine-:
Update:

Very odd. Once I used an older USB cable from my s4 with the new fast charge AC adapter, fast charging worked! However with the USB cord that came with the S6 Edge it would only do a regular charge. No idea why, but if they have cable issues with what was shipped out, it's going to cause a lot of headaches for tech support and warranty claims etc.

I see others having tho issue also.

http://xdaforums.com/showthread.php?t=3093015
[Sprint Samsung Galaxy S6 Edge] fernando sor:
Yeah I changed cords and now fast charger is working. Kind of a big screw up by Samsung to ship with the wrong cord.
[Sprint Samsung Galaxy S6 Edge] Alpine-:
They'll pay for it in tech support calls and replacements, etc. You can bet some entire phones get replaced because some idiots didnt check the cord itself.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] odinn:
new here and need help root sch-I925 4.1.2 verizon

it is a note 10.1 on verizon and i like to root it so i can used the sd card
[Motorola Droid 4] joefuf:
I had some odd issues with my phone that seemed to come out of nowhere today.

My phone was lagging and after a number of reboots, it seemed to clear up, but I couldn't run any apps without them crashing. My Hangouts wouldn't send any SMS messages without Hangouts stopping and having to be closed; Settings couldn't even get to the Running apps for me to Force Stop things; I couldn't even backup SMS messages in SMS Backup and Restore.

I tried to clear dalvik cache in Terminal by entering the following code:

su
cd /data/dalvik-cache
rm *
exit

It seemed to work and I tried to reboot. I walked away for several minutes and when I came back, it still had the "Rebooting..." screen on and hadn't shut off. This only started happening to me today. I tried to force shutdown the phone by holding the power button, and it shut off.

I noticed today that I have been unable to boot into Safestrap Recovery, and on the reboot, I tried to boot into Safestrap because I hoped clearing Dalvik would fix that, but it didn't after I let the phone sit for a while. I held the power button again and tried to reboot and start up normal this time. Now the phone gets through the M logo, the Safestrap splash, and then the screen backlight just stays on after the buzz past the Safestrap splash. Nothing has come up on the screen and I've tried powering off and rebooting again, but nothing so far on the second run either after 15 minutes.

Any help? Do I have to re-SBF now? the phone isn't even detected by my computer at this point. I really wanted to be able to backup my SMS messages and anything else I have locally on the phone.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] Armaiz:
I am try to mimic the way the notification bar looks on s5 to the stock lollipop. I color it the same but the only problem is the header (area with the time and settings button) is too thin. Is there a way to make it larger? I have root and I am using moar rom. Thanks!
[T-Mobile LG G3] Shotgun4:
Hey all,

Just rooted my LG G3. I have setCPU installed but it won't let me even run the phone at full throttle. Any reason why ? stays clocked at 900Mhz .. which is driving me CRAZYYY .. any ideas why i cant hit the 2.4?

thanks
[8525, TyTN, MDA Vario II, JasJam General] Michael_514:
Guys,

Don't flame me... I haven't fully tested my theory, but so far it's working well!

As you know, MANY of us have issues with the card not being recognized sometimes; the device hangs; the camera doesn't capture images, etc.

Well, today I was trying to take some pictures facing downwards (of a leak in my car door), and I would just get a black image almost every single time.

I would then do a test and snap a picture of my garage, and it worked.

Back to the door, it didn't work.

Etc.

I wasn't sure if there wasn't enough lighting or what.

HOWEVER.....

I then realized that everytime the unit was pointing down, THAT is when it didn't work!

I examined where the contacts are on the card (top), and sure enough, it MAY be that by the force of gravity, one or two contacts are losing contact.

So I tested my theory.

I stuck my thumbnail (the REAL one, not a mini image ;)) under the card, and pressed it up.

EVERY single picture worked PERFECTLY.

No freezing! No black! No issues!

So, I took a small peice of paper, and slid it under the card, like a shim. (It was actually a piece of an envelope, so it's a big thicker.

Gentlemen... Since I put that paper underneath the card, my 8525 has worked flawlessly.

I just took 20 pictures, stored on the SD card, and not one issue!

And this is a 2GB Sandisk, by the way.

I will do more tests, but I am really feeling confident that this may solve some of our problems.

(I hope this is not a "welcome to last week" thread! I have seen LOTS of threads regarding the camera, freezes, and SD issue.. but I never read anything about solving problems with a piece of paper!)

Thoughts???
[8525, TyTN, MDA Vario II, JasJam General] pvs:
Hi Michael_514,

While I appreciate your efforts here, the one thing that seems to have solved ALL of my SD Card issues was upgrading to WM6. Nothing to do with gravity nor Elfen registry edits ... just a new OS.

While I think your tack, dealing with gravity and the directional orientation of the device is interesting, I think the heart of the problem exists in the drivers for the SD Cards, which were corrected (or at least ameliorateed) in the newer OS builds.

All the same, I am interested in your final results, so please continue this post.

All the best,

-pvs
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Don't forget guys, maybe you are both right! We should not assume that everyone has the same problem - though the symptoms may be the same. Actually, when reading the many posts on this issue, I AM convinced there is in some cases a poor contacts issue that will afect the camera and other software/files on the SD card. I am also convinced there is in other cases a driver/software issue that may well be improved with WM6.

Always be cautious, yet open minded about claims from folks to have solved an issue. It may be for some but not all, and a different solution may exist for others.

Mike
[8525, TyTN, MDA Vario II, JasJam General] pvs:
Point taken, Mike. Thanks for that!
[8525, TyTN, MDA Vario II, JasJam General] barrr:
Just tried it. I will keep you informed tomorrow.
[8525, TyTN, MDA Vario II, JasJam General] Michael_514:
Thanks for the responses, PVS & Mike.

Mike -- Love your 'have an open mind' role! I guess that's why they call you a Moderator!

I would agree with Mike... both answers could be correct.

I am convinced that 90% of our Hermes woes ARE SD Card related.

I feel that because I had these units for 7 straight days, in use almost all day, with not one crash or hang...

..and then on day seven, I did a SD Card copy/paste, to switch cards with my dad's unit, and from that day on, freeze.. freeze.. freeze... Sometimes the unit is great for three days, sometimes, 3 reboots in one hour are required....

...Same thing happened when I reinstalled the firmware....

...that I just 'knew' that the freezes and hangs were DEFINITELY related to my swapping of the cards. Especially since I installed no weird apps.

Dirty contacts; bad connection; bad card controllers; I KNEW that my woes were not 'OS-related', 'sbd Pocket-plus-related', nor firmware related... Especially since I did three reinstalls of the firmware.

PVS - I totally agree with you. Perhaps WM6 has some better error checking, or a better algorythm for handing missing bits over the card bus.

I know a little about how computers and electronics handle this. It's why you can make a scratch in a CD, and it still plays. Check bits / error correcting / over-sampling / etc. etc.

I agree that a more advanced OS, like WM6, can better "handle" missing bits.

..but I am trying to get to the root of the problem.

I just went to the bathroom and took about 30 photos while sitting there :). ALL 30 worked! No black photos. No "New SD Card Inserted" message. No freezing. 30 on 30. I am thrilled so far!

After spending three weeks racking my brains out, dealing with the problems, I am starting to truly feel like I may be on the right track.

Let's keep our minds open... Let's remember how many 8525 issues do point to the cards. Let's keep in mind that half the people love their Sandisks, and half the people love their Kingstons.

A new OS may solve people's problems, as could a piece of paper jammed in there to make the contacts tighter.

I spent $720 on two of these units, and let me tell you.. I MISS MY 8125!

I am as eager to solve this as anyone. I use this machine for business. It's not just a hobby for me.

Maybe we are on the right track...!

Let's see what others say...!

I will keep everyone posted.

I do have to laugh at my make-shift solution, though! There is something funny about staring at my unit, with a little piece of envelope visible under the SD card. Talk about a low-tech solution to a high-tech problem! :)

M
[8525, TyTN, MDA Vario II, JasJam General] Ogier:
Michael_514, I love your theory. I hope it's that easy a solution for some of us if not all.

It seems from reports that Sandisk cards have this problem more often?

If owners could report their card's thickness using a micrometer, this might help confirm if an electrical contact issue is more likely?

My Corsair 1Gb card is 0.70mm thick, just behind the electrical contacts.

I've had issues with the card not being detected both with WM5 and now WM6. One time was fixed by wiping the contacts clean, but other times ejecting & reinserting the card make no difference. I've ignored the problem and many hours later the card would be visible again.

When I read your post, I straight away folded up some paper and pushed it in above the card, on the same side as the contacts - the memory card was still accessable within the phone, so I'm thinking my issue isn't a physical one.

Next time the card vanishes from explorer, I'll insert some paper to shim it towards the contacts and see if it helps.

Has anyone pulled apart their phone? I'm wondering if perhaps there's some type of pressure applied to the back of the card forcing it to contact electrically? Maybe if this is a mechanical device it is getting stuck?

My old phone's SD card slot broke when I dropped it once and it no longer ejected cards normally, but still worked perfectly.

Cheers! Oggy.
[8525, TyTN, MDA Vario II, JasJam General] Michael_514:
Hi there!

I just wanted to confirm where I put the paper.

I put it UNDER the card, effectively 'pushing the contacts up'.

That is where I stuck my thumbnail when I could not take a successful picture of my car door.

When I said to myself, "Why do all photos of the sky work, but not photos of the ground??", that is when I realized that I wanted to "push it up".

And in terms of the:

This firmware vs. that firmware...

Kingston vs. Sandisk...

WM5 vs. WM6...

Made in Taiwan vs. Japan...

Those are NOT the answers.

Too many people in too many threads have proven that.

I am not saying my method is correct... I will need a week of testing... But I know people DID have problems with WM6. People DID have problems with Kingston. People DID have problems with 512MB.

I started another Kingston vs. Sandisk thread, and reading those responses has shown me that it ain't the answer.

And as Ogier says, "I've had issues with the card not being detected both with WM5 and now WM6."

So, that also isn't the answer.

Let's all keep our fingers crossed, because I HATE rebooting this unit! :)

But to confirm, I put the paper underneath to 'force up' the contacts....!
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
@ Michael_514

Just another thought. There is also a difference between photos of the sky and photos pointing down and that is the light level. I know you are testing the idea about the contacts and angle of the phone, but to confirm it's nothing to do with the light level sensor/software you might need to test by taking high light level pics (pointing downward at a lamp say), just to rule out any light level sensor issue. I have noticed that the camera seems to incrementally adjust light level but in general it will be at a different setting pointing up as opposed to down.

As I say just a thought and something to rule out or in.

Mike