yashsingh1/xdaforums huggingface dataset:
[Desire HD Q&A, Help & Troubleshooting] weelo97245:
after a new update proposed by android, my camera doesn't work anymore :(:(:(... someone have a solution ?
[Desire HD Q&A, Help & Troubleshooting] dlads:
I don't think your the only person with this problem

It's a new thread but it's always nice to see someone else with a problem similar to yours

http://xdaforums.com/showthread.php?t=902202

I would use a custom rom to be honest as i don't think that all the dhd's out there are taking to this update very well.
[TG01 General] fxdjacentyfxd:
Hi.

My tg01 typically work in sleep mode. When in battery mode, baclight should be off after 1 minute, phone should sleep after 2 minutes.

When I recieve SMS and I don not know about it, backlght goes on and still stays on discharging battery. Phone does not go sleep too. I have to confirm notification and then phone work as it sholud. Could anybody give me any hint how to fix it ?

Regards

fxdjacentyfxd
[XPERIA X2 General] RRF9:
Hi,

My memory card is occupied 30% but XperiaX2's camera with R32A Vodafone says that there is no free space.

I believe that everything works bién except the camera.

Can someone help me?

Thank you​
[XPERIA X2 General] gbajzelj:
did you install the sdfix.cab? check if you can see memmory card in file explorer.

try a hardreset the device if you dont fing a solution. i do a hard reset every week or 2 and the device is always great no problems. afcorse font instal the panel manager and that stupid panels. and slideviev. they are no use to me. have almost clean wm6.5.3 and it works fine.
[G2 and Desire Z Q&A, Help & Troubleshooting] TheBiles:
Looking for some battery life here. What would you recommend?
[G2 and Desire Z Q&A, Help & Troubleshooting] KiNG OMaR:
Honestly, with the stock CM kernel I stretch out 18 hours easily with heavy usage (non-stop texting :p)

That is of course with NO profiles @ 806 MHz using the ondemand governor. If I need more power I just simply crank up the processor, no need to stay OCed all the time :)

With that said, 806 MHz is perfect, I experience no lag at all. So there really is no need to stay OCed at 1.5MHz unless you want to kill your battery :cool:

Hehe, I actually love you for UPGRADING from a crap NS to a G2 :)
[G2 and Desire Z Q&A, Help & Troubleshooting] TheBiles:
I got some lag on ADW EX at the stock speed, so I decided to melt it away with buttery OC goodness. I'll actually see how it lasts today, and if it's killing me I'll try clocking down until I get something acceptable. I was just wondering if there were any especially good UV kernels or anything of the like.
[G2 and Desire Z Q&A, Help & Troubleshooting] BootloopedMillennials:
What kernel did you end up going with?

I use pershoot's kernel and get pretty good battery life for being overclocked at 1.5ghz.
[G2 and Desire Z Q&A, Help & Troubleshooting] TheBiles:
Right now just the stock CM6.1.1 kernel.
[G2 and Desire Z Q&A, Help & Troubleshooting] PanCubano:
Go with pershoot's kernel.
[G2 and Desire Z Q&A, Help & Troubleshooting] TheBiles:
Is the one on ROM Manager compatible with CM6?
[HD2 Android Q&A, Help & Troubleshooting and Genera] sandeman11:
i have the same problem as mentioned here: http://xdaforums.com/showthread.php?t=774866&page=2

if i press the home button nothing happens. is there any way to solve my problem (without losing any data?)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Bakano:
a coworker of mine had the same issue today. I'm just reposting the link from another website, since I typically come to xda to find answers to stuff like this... either manually type this into your ANDROID browser, or if you could somehow make it to this page from your phone, just click this link... from your phone lol

market://search?q=pname:org.adw.launcher

it is the direct adwlauncher link to the android market!

hope this helps! =)
[HD2 Android Q&A, Help & Troubleshooting and Genera] TheATHEiST:
Then why not post in that thread?? No need to create a new thread if one already exists on your exact issue.
[G1 Q&A, Help & Troubleshooting] tearsphere:
I am on a G1 with 2708 radio and 0013d SPL ... As we all know, by having this, our 3G icon seemed to changed to H ..... To my knowledge, it didn't mean anything, but when my friend bought a G2 on our phone plan.. His phone shows the 'H' also....

So.... Is the new radio making the G1 data go at 4G speeds? ... Can someone explain
[G1 Q&A, Help & Troubleshooting] dhkr123:
H is for "HSPA". Yes, the Dream is capable of HSPA (3G), it always has been. No, Dream is NOT capable of 14.4 Mb/s like Vision. No, Vision is NOT capable of 4G, despite the outright lies told by tmobile. In fact, tmobile has precisely ZERO 4G infrastructure and doesn't sell EVEN ONE SINGLE PHONE that is 4G capable.
[G1 Q&A, Help & Troubleshooting] decoderone:
The G1 had always support for HSDPA but the Icon always show 3G. Maybe they didn't think it is that important. Cyanogen adds a new htc ril driver into the roms which give us the possibility to show the appropiate icon.

No 4G support sorry :)
[XPERIA X8 General] Blitzkri3g:
Hello people! I stumbled upon this UOT Kitchen site.

http://circle.glx.nl/

From what I could understand I could use this to change for example my stock battery icon in the notification area of my X8 to look like a circle with the battery percentage in it,right?

So,I just have to choose my settings,upload my framework and the use xRecovery to install the generated zip file from my SD Card?

Or did I understand the whole procedure in the wrong way? :p

N.
[XPERIA X8 General] apemania:
no, it doesnt work!!

I have tested it...
[XPERIA X8 General] XperianPro:
Maybe you do something wrong.

Will be good if someone realy try this.
[Galaxy S I9000 Q&A, Help & Troubleshooting] BlademasterL:
I have a Samsung GT-I9000 and a few days after I started using it it kept crashing and giving me the "com.android.phone force close" message, after which I would get a notification telling me that I have lost my signal, etc. Soon afterwards everything would be back to normal, only for it to crash again a few minutes later.

First I changed my Network Settings to only use GSM, as I figured that my 3G coverage might just be crap. This seemed to work fairly well, but after a week or 2 when I changed it back to Auto (i.e. GSM or WCDMA) it started crashing again. After that it just kept crashing no matter what mode it was in.

I read in another forum that getting a newer sim card might help. While it did work for a friend of mine, my phone is crashing even more after I got my new sim card.

I suspect it is a network problem, as it never crashes in flight mode or when I put a "dead" sim card in.

I have not rooted nor done anything else to my phone, so it's still running on 2.1, etc.

Anyone have any ideas? I am at a complete loss. :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] JJEgan:
Try backing up data then a factory wipe and reset .

jje
[Galaxy S I9000 Q&A, Help & Troubleshooting] BlademasterL:
I tried that before getting a new sim. Will try it again though!
[Galaxy S I9000 Q&A, Help & Troubleshooting] Metusion:
I had this same problem. Factory reset plus install of new darky rom 8.0 fixed the problems.. I did have signal problems but that has been addressed already.
[Galaxy S I9000 Q&A, Help & Troubleshooting] BlademasterL:
Ok, so I've had my "new" reset running faultlessly for a few hours now. Hoping for the best! Definitely upgrading to Darky soon though!

Many thanks! =D
[Captivate General] gunstar3035:
Yep...Go get it. :D

EDIT: I mean Kies...The update box was in my way when I was typing lol
[Captivate General] A.VOID:
So what is the ROM version name?
[Captivate General] gunstar3035:
Just a min, update failed...I think cause launcher pro was the default home...trying again damn it.
[Captivate General] tjsooley:
Someone post a odin copy.

?
[Captivate General] jcabibi:
Let the BRICKING begin! :P
[Captivate General] loonieryan:
Would love an ODIN of this ROM... looking forward to it!
[Captivate General] alexvtr:
Installed Kies... Update process starts but Kies crashes. Anyone else have this issue? I'm currently trying to unroot to see if that makes a difference.

Edit: Exact issue is: MSC.Thunder.FirmwareUpdate has stopped working.

Does it regardless if I choose to backup or not the contacts and data.

Edit 2: Unroot changes nothing.

Edit 3: Doing a factory reset on the device doesn't help either. WTF?
[Captivate General] Fortysixandtwo:
connected to Kies - message "This device will be supported soon"
[Captivate General] alexvtr:
http://www.samsung.com/ca/support/detail/supportPrdDetail.do?menu=SP00&prd_ia_cd=01012200&prd_mdl_cd=SGH-I896ZKARWC&prd_mdl_name=SGH-I896&prd_ia_sub_class_cd=P#

Get it here
[Captivate General] ScottyNuttz:
Wonder if it'll be 2.2.1...
[Captivate General] gunstar3035:
Ok so I just got back from writing an exam and will try to reinstall Kies. I tried 2 times to update through my computer this morning and once on my wife's PC (She has a Captivate as well)

All 3 attempts it says that Its downloaded the update but then it fails when it tries to install. Now remember I've not rooted or anything, so i think that there might be a newer version of kies or something...going to look now.

But anyways it tries to update it says a bunch of stuff like: You phone Jsomething1 and the update is supposed to be Jsomething2...I dont get it.

Remember I dont hack or mod phones in the slightest, so I have no clue what this J1 (mine) and the update of j2 is...?

The update is big though, takes a few minutes to download and I have a 16mps download speed...
[Captivate General] gunstar3035:
Downloading this version of Kies and will try again:

http://www.samsungapps.com/about/onPc.as
[Captivate General] alexdemers:
I'm with Rogers with an AT&T Captivate (Rooted and Cognition 2.3b6). Will I be able to update my device to it? I much prefer the Rogers software than AT&T's. I don't care if I have to use Odin or erase everything.
[Captivate General] silvertag:
What ROM are you on ?

Did you put the phone in recovery mode when you have the first pop up menu ?
[Captivate General] silvertag:
Nope it's 2.2
[Captivate General] Enhanced:
Where does it say it was released?
[Captivate General] silvertag:
Did you put your phone in Recovery mode like the first pop up is asking ? (Unplug usb cable from phone (not the computer), power off the phone, Hold vol up/down button and plug usb cable. You should now be in download mode (black/yellow screen with a shovelling droid)
[Captivate General] alexvtr:
Stock ROM from Rogers

No, not recovery mode.

PC runs W7-32 for what it's worth.

In the meantime, I did some research on the error I mentioned above.

It appears it's a very common issue with KIES.

There are a few workarounds.

So far, I tried the "SIM-out" method and it doesn't work for me.

Next, I'm trying the regedit method.

Will report on results.

@silvertag: your upgrade worked fine or you haven't tried yet?
[Captivate General] silvertag:
Nowhere you have to check Kies server to know it's been released. There is still no confirmation from Rogers last i checked.
[Captivate General] silvertag:
Yes it worked fine you HAVE to put the phone in download mode before you start downloading the update or it will fail at the upgrade part. :)
[Captivate General] ~~mitch~~:
I work for Rogers. I will look into this tomorrow and see what I can find.
[Captivate General] gunstar3035:
I have been using the 2.2 update all day with Launcher pro and its been fantastic. The Camera also had a firmware update! My phone feels twice as fast and my wife says her captivate seems faster too.

Been fantastic! But the boot up sequence is a bit odd now, but other than that its all good. Flash is blazing fast on the browser!
[Captivate General] inningsdefeat500:
Please Help: Stuck at Downloading...

1-Open Kies (You have to be in TW Launcher, not LauncherPro or other for Kies to detect the phone and do a firmware update)

2-Plug in your phone with Kies firmware update On (in Settings/Application/usb settings)

3-Select Firmware Update in Kies

4-Click the Update button

5- Wait for the download to finish then unplug the usb cable from the phone

6-Power it off

7-Hold the volume up/down buttons together and replug the usb cable

8-You should now be in Download mode (Black/yellow screen with a shovelling

droid)

When KIES Finished it said, above steps in a separate Window, I unplugged, Powered OFF, Held Vol Buttons, Downloading.. is on Screen but when I pressed OK on the pop up window, it said Kies cannot find phone, press OK or Cancel, pressed OK like 10 times, did nothing, pressed Cancel and Kies back to Normal with no connected device and Phone at download..?

What should I do now
[Captivate General] inningsdefeat500:
It updated, on the Big S and Galaxy S in the bottom, Kies says Completed, the device will be rebooted. So do I wait here or? unplug or reboot
[Captivate General] mjk37:
I had problems updating until I set the default launcher to TW Launcher then it all went just fine

Win 7 64bit Latest version of Kies
[Captivate General] Enhanced:
I have had this running for half a day and in my experience, it runs very stable. I have not experienced any of the problems you guys have save for the spelling mistake. I do find it suspect that there wasn't an announcement at all, but it doesn't mean this firmware is unstable. I've done the update on 3 separate phones without any issues you guys have experienced so far. Keep in mind though that on all 3 phones, they were never rooted/lag fixed or anything.

For the start up sequence, overall startup time is reduced so everything is sped up.
[Captivate General] inningsdefeat500:
EDIT: DONE, update success
[Captivate General] fluidd:
Is it necessary to re-calibrate the battery, after updating to 2.2?
[Captivate General] fluidd:
I'll just go ahead and do it anyway, what does it hurt right? hmm.
[Captivate General] shawn122:
Just completed the update and my phone also seems to be vibrating randomly...
[Captivate General] gunnyman:
maybe it's happy? :p
[Captivate General] redjersey:
I got a question, I have my rogers rom rooted, do I have to unroot first in order to install the 2.2?
[Captivate General] tjsooley:
HAS anyone posted the odin package.

you need to decrypt the temp file that kise makes.
[Captivate General] shawn122:
Hahaha.... lol

This update is very buggy. Swype doesn't work as well.

Anyone know how to downgrade?

_______
[Captivate General] TheEscapist:
To the guys with issues, you odin'd back to JI2 stock, and wiped cache/user data, right?
[Captivate General] shawn122:
I was on the original stock Rogers ROM. I had only rooted.

Seems like the vibrate issues are caused by the Swype Keyboard. I chose another keyboard for input (Swift Key) and those issues went way.
[Captivate General] Holmes108:
Weird, I'm having issues as well but swype had been fine. Not even peoples problems are consistent.

I've wiped user data and cache (after installing froyo) and see if that helps. If not I suppose I'll try and downgrade then wipe and reinstall. Z4root isn't working though. Has anyone tried that super one click yet?
[Captivate General] k-0s2:
Hey if I just flashed and installed Perception 10.1 what do I need to do to do this upgrade?
[Captivate General] silvertag:
Yes it was mentionned before ...

z4root does NOT work on 2.2

.

You need to use SuperOneClick v1.5.5

NOTE: No need to unroot before updating but you have to remove any lagfix.
[Captivate General] ed116:
guys if you wanna get swype to work, try downloading TiBu (titanium back-up) , delete swype and download the latest version (preferably over applanet) and see if that helps
[Captivate General] yobbei:
I couldn't get SuperOneClick to work. It just stuck at waiting for device.
[Captivate General] desilla:
Is anyone having issues with their GPS after this update???

I cant get a lock on anything after the update
[Captivate General] silvertag:
Yes it's normal behaviour.

When it's looping you have to

-Unplug the usb cable from the phone

-Uncheck the usb debugging option

-Replug the phone

-Wait a few sec

-Unplug the phone, recheck the usb debugging

-Replug the phone

Then it should continu and root
[Captivate General] tbrummell:
After installing the "app", run it from your programs drawer, it will then flash the new camera firmware and ask you to reboot. I did it on mine, camera still works. Took some night pictures last night and it really seems to work better. Loving my Captivate more & more now.
[Captivate General] jasonchewy:
Just adding my input:

For people having trouble connecting the phone to Kies (ie stuck at connecting to device on kies screen).

What I did was under the top left down down on the Kies screen, there's an option to reinstall the drivers. I unplugged my phone, ran that, then plug the phone back in, windows (7 64bit) then ran through the usual new hardware procedure, then Kies finds the phone normally, then the rest of the update went on.

btw, I've also noticed weird vibration and unusual startup sequence, other than that, everything seems fine.

Question about hard reset on Android, I came from the Windows Mobile side. Whenever I hard reset on WM, all the default apps/settings are all reinstalled back from the ROM. For Android, if I rooted, and deleted stock apps, and hard reset, will the deleted apps come back as well?
[Captivate General] yobbei:
Ok so when it is not on USB debugging which mode should I choose? Kies, Mass Storage, or media player?

So anyone gotten it to root after the upgrade? I couldn't get superoneclick to work.
[Captivate General] tbrummell:
Yes they will. You will need to re-root and remove the apps again.
[Captivate General] jasonchewy:
Thanks, now I can start removing crap without worrying.
[Captivate General] dverse:
just wanted to let you guys know, i found out last night that the update was available.

I had 1.5.3 and i figured to install 2.x whatever, it only works for the wave (wtf). So i installed 1.5.3 again and went to sleep.

Woke up reading some people with issues and some that the phone took forever, i decided to risk it coz i have a 9780 around just in case.

It went flawlessly, the phone was stuck on the S logo for maximum 4 minutes.

Phone seems good, now the GPS isnt locking me exactly where i am (im in the basement of my house) yet its 3 streets closer than before so maybe with time?

Anyone noticed anything with the GPS (i have the details recommended through the *#*# process
[Captivate General] foxbat121:
Nope. WM equivlent hard reset is not available in Android. The only way to get back the removed crapware is to re-flash the firmware.
[Captivate General] silvertag:
Should not matter.. The trick is removing the debug mode and reapplying it.. this makes SOC redetect the phone and complete the rooting process.

So when it says "Waiting for device" unplug, remove debugging, replug, unplug, add debugging,replug. Redo until you get root.
[Captivate General] tbrummell:
Eh? I seem to recall on my Magic (I have not removed any stock apps from my Captivate, or done a wipe yet) that if I had removed an app, used the phone for a while, then did a wipe that it would reinstall said apps. Is this not so?

PS: Now that I think if it, that was using AmonROM Recovery, maybe wiping user data from within the Android GUI itself does a different process. What's the worst that is going to happen? It's just going to put the stock apps back on, to which you will just remove them again....
[Captivate General] dverse:
*#*#1472365#*#*

doesnt seem to be working under 2.2
[Captivate General] yobbei:
Well if anyone successfully rooted after the 2.2 update please let us know how.

I have tried:

z4root

superoneclick 1.5.5

update.zip downloaded using galaxy s tweak

still no luck

I think this rom is OK so far but I really want to lag fix it to see how it performs.
[Captivate General] tbrummell:
As mentioned previous, Super 1 Click worked for me, as did OCLF once I was rooted.
[Captivate General] yobbei:
great to hear.

I am using superoneclick. I have tried what you mentioned:

1. plug in phone USB debug on

2. click root

3. "Waiting for device"

4. unplug phone and set USB debug off

5. plug in phone in Kies mode

6. waited for a bit... Still "waiting for device"

7. unplugged, turn usb debug on, plugged

8. still "waiting for device"

Anything I did wrong?
[Captivate General] silvertag:
Easiest way.

Install Launcher Pro. Create a shortcut - activity - LBSTESTMODE.

Or check on Google for lbstestmode.apk to point you on the right thread on xda to download it.

EDIT: new code in Froyo is

*#*#3214789650#*#*
[Captivate General] foxbat121:
Android doesn't do that. Nor will it unroot your phone.

The reason ppl asking for it is for the purpose of return or exchange the phones. Rooting technically voids your warranty. Hence the need to restore to out of box factory condition.
[Captivate General] tbrummell:
Well that will teach me for speaking out of turn. Sorry for the misinformation.
[Captivate General] yobbei:
Ok I finally gotten it to root and OCLF.

I had to use another machine with .net 3.5 (instead of 4)

I also installed the samsung driver instead of Kies which I download from here:

http://briefmobile.com/wp-content/uploads/SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip

And then ran superoneclick first with debugging mode off, when waiting for device unplugged, USB debug on, plugged, and then it just continue all the way thru.

The Quadrant score is 1966 which is quite a bit slower then 23xx with 2.1 and OCLF.
[Captivate General] 10ee:
Thanks CB650 Wolf. This info is bang on.

My product code is indeed borked. The correct product code for Rogers Captivate is SGH-I896ZKARWC. Mine is showing up as SGH-I896ZKAATT. Right model, wrong code.

For Kies, in the registry under HKLM_CURRENT_USER\Software\Samsung\Kies\DeviceDB there are numbered keys which represent devices. If one device has only been connected, under Key <1> that device's product code will show up under the REG_SZ (string) named "Product Code".

I took the easy way out and found a friend who has an un-modded Captivate running Rogers stock 2.1, and hooked it up to one of my PCs running Kies and his showed up as SGH-I896ZKARWC, so now we at least know the right product code for these darn things in case it gets blown up again by FunROMs.

Thanks again, now I'm gonna try this, explode my phone and live a peaceful life. Let's see if I can get this working.

I might (again) take the easy way out and hook up my friends phone, start the download, and then when I re-plug in download mode, plug my phone in, and watch it blow up.

Cheers!
[Captivate General] Riker2k:
Just wanted to add that I ran into this exact issue last night although my product code had been changed to end in KAKOR instead of what Kies / Rogers is looking for which is, as you noted, ends in KARWC. What you need to do is either restore a backup of your original nv_data.bin before you applied an AT&T or other ROM, OR you need to edit the nv_data.bin with a hex editor to change the product code to end in KARWC.

Don't have time to detail the whole thing right now but that's the gist of it. The hex offsets in the various forum threads about restoring product ID to the AT&T product code are the same here so it can be fixed. I fixed mine with an nv_data.bin restore but the edit should work too if done carefully.

HTH

Update: A couple of notes - I don't recall the hex codes for the RWC but I can probably track them down later today if you still need them. The owner and group need to be radio.radio for this ROM and not 1001:1001 like those guides indicate. You should be able to do a chown radio.radio nv_data.bin once you get the edited or restored nv_data.bin pushed back onto your Captivate. You will need to delete the nv_data.md5.bin from the device as well which should get recreated when the device is rebooted. Permissions on nv_data.bin in the /efs folder should be 700 (rwx --- ---) after you put the file back. I think most of that is covered in those threads that CB Wolf linked but just wanted to cover the couple of areas that I ran into a snag and had to sort out. This post gives a good snapshot of what the folder structure + permissions should look like when you are done.