yashsingh1/xdaforums huggingface dataset:
[myTouch 4G Q&A, Help & Troubleshooting] aznprodgy:
+1...a rom could run blazing fast and smooth as ever, but still achieve a score of around 2500-ish which most consider to be a low score. its all about your personal preference. if YOU like the way YOUR phone runs, then Id say thats all that matters:D
[G2 and Desire Z Q&A, Help & Troubleshooting] Slarti77:
Hey all,

I have a new 32 gb micro sd for my G2. I have a couple of questions.

1. do I have to unmount the original 8 gb card prior to taking it out?

2. What are the ramifications if I don't unmount it?

3. do I have to format the new card after it's in the phone?

4. I have unchecked all the apps so that none are storing on the SD card. Is there a way to move the remaining data from the SD card to the phone?

5. Is it possible to "Clone" the data from the current SD card to the new one?

Thx

Mark
[G2 and Desire Z Q&A, Help & Troubleshooting] ArmedandDangerous:
1. No need to unmount, since you'll need to remove the battery anyway to insert the new card.

2. Nothing

3. Would be best

4. Copy and paste contents to new card

5. See 4
[G2 and Desire Z Q&A, Help & Troubleshooting] Slarti77:
Hey A&D

Thx for the quick reply ...

So can I Simply plug the phone into the computer, copy everything that shows up under the directory for the phone to th computer ...then copy it all back to the new SD card once I install it in the phone?

Also, when the phone is plugged into the computer and shows up as storage am I only seeing data on the SD card or is it showing data on the internal memory as well?

Thx

Mark
[G2 and Desire Z Q&A, Help & Troubleshooting] Ditamae:
Yes, that should work. If you have any apps installed to the SD card through Applications setting, I'd move them back to phone memory before you make the switch. They are stored in the .android_secure folder. Also you might want to format your new SD to FAT32 on your PC before moving your data back. But sounds like you're on the right track.

And you should not be seeing anything from internal memory while the SD is mounted.
[Nexus S General] XK72:
I've seen a couple posts regarding getting Google Wallet to work (and hopefully I'm not being redundant with this post). I've had Google Wallet working on my own 2.3.5 source ROM for quite some time now and I figured I'd share what got it working for me. As a matter of disclosure, I do have the 4G, but I haven't seen anything in the code that would give reason for why this wouldn't work.

While I'm able to build a ROM, I for some reason, don't know how to put together a flashable update. Maybe somebody with a little more know-how can piece this together and try it out, or at least tell me I'm wrong.

Files needed from the GWK74 ROM:

system/etc/permissions/com.google.android.nfc_extras.xml

(I just added the permission entry to the existing com.android.nfc_extras.xml file instead to keep the clutter down).

system/framework/com.android.nfc_extras.jar

The version in the GWK74 ROM contains code that has yet to be released, since korg is down and all. The extra file has something to do with NFC emulation, but I've only glanced at it, so I really couldn't tell you what it does.

system/app/Wallet.apk

Obviously.

Here's the catch: The Wallet app requires permissions from Nfc.apk (NFCEE_ADMIN). By default, the Nfc.apk is signed with the "platform" key, but as long as these two files are signed with the same key, it will grant it the proper permissions to Wallet.apk no matter what key that may happen to be. Considering that Nfc.apk also requests other permissions from "platform" as well, certificate consistency would be advisable.

Hope this works out or at the very least, gets the ball rolling.
[Nexus S General] droidance:
Hopefully, someone can make like a flashable zip for CM7 or at least let us know which files need to be copied to our GSM phones so we can extract those files and copy it to system :D
[Nexus S General] david279:
do you mind zipping up the files used and posting them here?
[Nexus S General] XK72:
They're basically the stock files from GWK74 with Wallet.apk and Nfc.apk signed with the same key. My only concern is that since I've used a private key on my own ROM for a while now, I don't remember/know how many or which non-stock ROMs are signed with anything other than the testkeys or which key would be the best for (most) everyone. If the testkeys work universally, I could do that, but I'd hate for someone with differing platform keys getting upset that it's still doing the same FC as before.

For those familiar with using the Android Kitchen, it can do the signing and packaging with testkeys if you're willing to reflash. Might be an easier step for some to take if the command line method seems overwhelming.
[Nexus S General] apreichner:
As far as Google Wallet working on a GSM Nexus S. I believe there is more protection than it appears. I firmly believe Google has not only modified the NFC drivers and added NFC security to both the drivers and the Firmware. But I also think they added security to the rils and network checks.

How did I get to these conclusions? Well I actually ported the whole NS4G rom over to the GSM. The only things I really had to change were ril libs and the build.prop. Everything else is pretty similar between the two phones. NFC worked and I was able to start up Google Wallet, however, when attempting to add a card to Google Wallet, it kept loading for like 10 minutes until it gave an error. No real description of the error and logcats revealing nothing. Taking out my sim card, I was greeted with a message in Google Wallet that I should check my sim card and insert it if its not inserted. Why would Google Wallet even have anything to do with carriers even connected to wifi? There must be some other things added.

Then I went ahead and decided to revert to a backup of my CM7. I noticed NFC no longer would turn on, it kept giving me an error. Looking at a logcat it looked like it was trying to download and install firmware but failed. Other NS4G users have experienced this same error. Logcats show that it is downloading firmware but failing to be able to install it. My theory: Google added extra security to the firmware located directly onto the NFC chip itself. So now no ROMs (including the new 2.3.6) give me working NFC except for that 2.3.7 rom. I'm still working on trying to fix.

Now I am happy you posted this thread, because maybe if I backport these additions to a GSM rom I might be able to fix NFC. I'm not sure as of yet. I am going to attempt Odin next, but I can already guarantee Formatting System, Boot, Cache, Data did not resolve the issue.
[Nexus S General] Rem3Dy:
They definitely added something to the firmware. After flashing GWK74 nfc no longer works on 2.3.5. If I flash back to GWK74 it works no problem.
[Nexus S General] snandlal:
U could test that driver theory with a chip that hasnt gotten the 2.3.7 update.
[Nexus S General] david279:
Need some help i get this error message when i push the files to newest Cm7 nightly based on 2.3.7. Any ideas?
[Nexus S General] tobiasly:
Well keep in mind it's not just Google that's involved, but MasterCard, Citi, MoneyNet or whatever that service is that processes the transactions... they may have mandated that some extra security measures be taken to keep the initial rollout limited to a relatively small specific group.
[Nexus S General] XK72:
I encountered the same issue a while back. It's related to the signature keys on Wallet, which is signed with Google's key out of the box. If the rest of your build is signed with testkeys (which appears to be the case), you can resolve that by signing Wallet.apk with testkeys as well.
[Nexus S General] XK72:
While Google Wallet is a proprietary application, and as such, Google or the forces that be could possibly be responsible for what's occurring and I wouldn't be able to discern whether or not that is true, I personally don't believe that is the reason behind what is happening.

(This is just as I understand it). There certainly are security measures in place for NFC, which the Android system is responsible for handling. The Wallet app is essentially an interface that is PIN secured on the user end and requests relevant permission from Nfc.apk that manages interaction with the NFC-related subset on its behalf. If anything, the credit card companies are concerned with unauthorized transmissions that could result in financial liability on their end. The fact that Wallet requires signature-protected permission authorization from Nfc to access the NFC element shows that Android is not leaving security duties up to the Wallet app alone.

I think the hindrances in getting this to work for everyone is that the people who could develop a fix probably don't have access to the Nexus S hardware variants. I started with the same or similar issues that people faced when trying to incorporate Wallet into their build and eventually got it to work on a 2.3.5 sourced build was the steps above, but I also don't own a standard Nexus S for me to test with, so I couldn't proclaim that it was a definitive fix. I was hoping, at the very least, that it might be contributive towards finding a fix for everyone.
[Nexus S General] david279:
How do I sign apks? Can you send me a wallet apk signed with test keys?

---------- Post added at 06:03 PM ---------- Previous post was at 05:39 PM ----------

Ok i found a app in the market for signing apks, zips, etc. but im getting the same error.
[Nexus S General] apreichner:
I will attempt to port it over. Good news is there's some 2.3.7 source available now to build with. I don't have much hope though because a full port didn't even work on a GSM device. Although newer libs might help.
[Nexus S General] XK72:
Do you know where they're hosting the 2.3.7 source? I just realized that they released the 2.3.7 binaries for both crespo and crespo4g, so between those two, there really shouldn't be anything else getting in the way of making this work.
[Nexus S General] Tenhi:
Here: http://xdaforums.com/showthread.php?t=1284517

People are reporting that Wallet works just fine on I902x phones and stock rooted 2.3.6. I'm only one there unable to add prepaid card. Guess it's because my IMEI is generic, and i'm pretty sure that google is using IMEIs for authentication and similar processes...
[Nexus S General] matt2053:
One factor may be branch of code. In build numbers, the letters have meanings. First letter is Android version (G for Gingerbread). Second letter is branch. Usually this is R for Release. The build for NS4G is W. I don't know what this W branch is. Maybe special "Wallet" branch.

http://source.android.com/source/build-numbers.html
[Droid Pro General] digital_cha0s:
Hey fellas I just got this phone for my ol lady and out of not knowing this answer I felt like asking. Has this device received the OTA gingerbread update yet?

Sent from my Not So Superior Any More Android Device

Future Bionic Owner or maybe the next big thing lol

nevertheless all will change
[Droid Pro General] dutchbastard:
No not officially. But the zip that's floating around does work beautifully.

Sadly I don't have the link for you.
[XPERIA X8 Q&A, Help & Troubleshooting] Alenos:
Hi, i am a total noob in android phones

I have an x8 and i have installed the custom rom Ginger Dx v015, my problem is that i cant make call and recieve them, but i can send messages.

When i try to call the phone show me "Sorry! The process com.android.phone has stopped unexpectedly. Please try again."

Please, i need some help!

Thanks for your time and sorry for my english... I am from Argentina
[XPERIA X8 Q&A, Help & Troubleshooting] rav3n_pl:
Load phone fix for v15.

Or install GO contacts/dialer or ONE dialer to replace broken app.
[XPERIA X8 Q&A, Help & Troubleshooting] Alenos:
Thank you so much, no it works :D
[Samsung Galaxy S (4G Model)] alien001:
Hi, I just got my phone a couple weeks ago, found this site and have been reading through the threads as much as possible. After reading through the step by step guide created by FB (thread link below) I feel confident that this shouldn’t be too difficult. When you get to step 11 it says to flash the GB you put on your SD cards. Do you need to do anything before that? The reason I’m asking is most of the ROM’s included their own install procedure like Audiophile FTW says, factory reset, wipe cache, check mounts etc. I wasn’t sure if that still needs to be done?

Also, since I’m starting with a stock phone would it be a good idea to flash Bali for Froyo first to get CWM and do a back-up before I try this?

Thanks for any help that can be provided.

http://xdaforums.com/showthread.php?t=1223765
[Samsung Galaxy S (4G Model)] alien001:
Sorry I meant odin bali not flash.
[Samsung Galaxy S (4G Model)] jager555:
you should always wipe data and clear cache before flashing a rom. you will not need to odin bali prior to fb's procedure. after you flash gb files, you will automatically have cwm.
[Samsung Galaxy S (4G Model)] alien001:
Thanks, so I don't need to worry about backing up stock phone before I got to gb?
[Samsung Galaxy S (4G Model)] jager555:
To be honest, I made backups ever single time I flashed a ROM. And I only fully restored once or twice. Back up once you are in GB. That way you can restore data. Once you are on GB, you won't go back to Froyo...
[Samsung Galaxy S (4G Model)] alien001:
Sounds good. Thanks again for your help.
[Samsung Galaxy S (4G Model)] alien001:
Two More Questions

Sorry, I have two more questions if anyone can help.

1 - I want to flash icbinb KI3 1.3. It states if you have problems with converting to EXT4 the flash FB's busybox installer before icbinb ROM, however if I follow the guide I should do the below. If I follow the below instructions instead of flashing busybox installer before will i have any problems?

Go into the voodoo menu > enable lagfix and /system lagfix on

11) Flash the GB rom you put on your sd card

12) Flash the busybox_installer.zip

13) Reboot

2- Also, the above guide has you enable lagfix & /system lagix before you flash, but when you flash icbinb KI3 1.3 it says to flash ROM and then enable voodoo. Is it still OK to enable lagfix then flash?

I'm probably making this more complicated than it really is. Again, any advice is appreciated. Thanks!
[Samsung Galaxy S (4G Model)] FBis251:
Voodoo doesn't get enabled until you hit reboot. The order in which you enable voodoo (before or after flashing a rom) doesn't matter, as long as you do the flashing AND the voodoo enabling before you reboot.
[Samsung Galaxy S (4G Model)] alien001:
Thanks...That makes perfect sense. As I said I think I was making it more complicated than it was. Also, Thanks for making the guide!
[Samsung Galaxy S (4G Model)] alien001:
Finally had the time to do this. It was really easy and had no problems at all. I'm just in the process of calibrating my battery and working on restoring my apps. Having a couple problems with some apps not wanting to restore via TB, but I'm sure I'll figure it out.

Anyone that wants to jump to GB just follow FB's guide and you should have no problems.
[Epic 4G Q&A, Help & Troubleshooting] lonnie23:
Im on the EH17 , and I'm getting my messages late . . Is there anyway to change this or fix this ?
[Epic 4G Q&A, Help & Troubleshooting] omair2005:
Try to Odin the modem, update your prl and profile.. if that doesn't work go back to EC05
[Epic 4G Q&A, Help & Troubleshooting] KennyG123:
Yup this ^^^^^^^^^^^^^

and also check if it is a Sprint network error if you know someone also on Sprint on the same tower.
[Epic 4G Q&A, Help & Troubleshooting] GituSum:
This was happening to me the last few days and I'm on EC05 so it could be a sprint thing.

GituSum Epic4G
[Epic 4G Q&A, Help & Troubleshooting] ac16313:
Same here. Damn and

I can't for the life of me get 3g here in Phoenix! every time it shows I'm on 1x !

Sent from my SPH-D700
[Samsung Epic 4G Touch] ajamer:
With the big Samsung/Google conference in 2 weeks with likely Ice Cream Sandwich device unveiling or maybe upgrade path details, I was wondering who else is returning their phone?

I'd hate for the Galaxy Nexus to come out next month with ice cream sandwich and the Galaxy S 2 not be upgradable for a while (espically with all the rooting problems)

Also, the battery/driver issue with the galaxy is driving me crazy. I'm glitched with hundreds of other people into only have ~12 hours of battery life doing absolutely nothing while others say they're getting 30+ hours.

I'll rebuy the phone once this stuff gets sorted out if nothing better is coming in October
[Samsung Epic 4G Touch] walord:
No.

The google phone is also going to be a Samsung. If you're having issues with the battery on this phone what makes you think another Samsung phone is going to be better? I doubt that it'll run any longer or charge at a higher rate (the previous galaxy s phones shared the same charging restrictions as the current g2's as does the nexus S)

There's always something better / different around the corner and you don't really need a dumb reason to switch... you could just switch because you want to.
[Samsung Epic 4G Touch] wase4711:
Returning your phone based on something that "might" be coming out sometime in the future???

and, since when is ~12 hours of battery life on a super powerful, feature laden powerful phone a "issue"?

We'll miss you...
[Samsung Epic 4G Touch] maddoggin:
thats why the economy sucks and gas prices are thru the roof atm. for speculators like this one!! lmao!!
[Samsung Epic 4G Touch] Snazzytime:
I was told I would have to pay a ~$30 restocking fee if I wanted to return it. If anyone is returning, are they getting past this fee?
[Samsung Epic 4G Touch] ajamer:
12 hours of standby battery life is a huge issue, as other smart phones give you 8+ hours of TALK time. Apparently it's a glitch with Samsung since Gingerbread, so if an ice cream sandwich model is right around the corner and fixes it, it's well worth it.

If the conference doesn't reveal anything coming in the next month or two, I can always buy it again and hopefully will get one without the glitch.

I returned a Nexus S last month (picked it up for free) and didn't pay a restocking fee to best buy.

How has Samsung/Sprint's track record been with porting updates once Google releases them?
[Samsung Epic 4G Touch] crawrj:
You need to return your phone and have it repaired. I get way more than 12 of actual use time. I could get three or four days easily in just standby time. Hell I have gotten about seven hours of screen on time.
[Samsung Epic 4G Touch] AbsolutZeroGI:
yeah, like this one won't get ice cream sandwich :rolleyes:

remember the nexus s being released and it had gingerbread? and everyone wanted to buy it because it had the same guts (1Ghz processor, etc etc) but it had GINGERBREAD...now everyone's got gingerbread and the thing that made the nexus s great is a common thing.

Go enjoy getting ice cream sandwich a few months before the rest of us...but you better believe you won't be the only one who gets it ;)
[Samsung Epic 4G Touch] ajamer:
There's a huge thread about this problem on the main page with 15,000 views

One guy swapped his phone out and then had the problem again. Other people are reporting great battery life as this phone SHOULD technically have.

I'm hoping Samsung will address it soon, but it appears to be related to Gingerbread and multiple Samsung devices. or just wait to see if ice cream sandwich fixes it

I'd bet the jump from Gingerbread to Ice cream sandwich will be bigger than the jump from Froyo to Gingerbread. You're really getting the honey comb improvements and going from Android 2.3 to Android 4.0
[Samsung Epic 4G Touch] musclehead84:
My battery life is great. I'm at 24 hours now with 5 hours screen on time and still have 20% left. Plus I have some sns sync as well.

Sent From My Evo Killer!!!
[Samsung Epic 4G Touch] walord:
Historically they rank third place behind HTC and Motorola with the number of phones that recieve updates, and an average wait in days as 156.

This is from 2010, and includes low and midrange phones. I find that Samsung is much more motivated to support and upgrade their top-tier smartphones. Hopefully, the wait times will continue to get shorter with each update as they learn to be more efficient.

article:

http://blogs.computerworld.com/17649/android_upgrades
[Samsung Epic 4G Touch] craigbailey1986:
With 15000 views and only 220 post half of which saying they don't have a battery issue, another portion saying it happened after they rooted and went away after going back to stock, another portion saying once they took their sd cards out the drain was fixed... get where I am going with this?????

Unfortunately there is not enough evidence to say their is a problem, with only about 8 people in that thread saying there was a problem. I feel bad for those who are having these bugs because you're obviously not getting the same great experience I am getting... wish you all the best but jumping ship on a phone that may or may not come would be foolish!
[Samsung Epic 4G Touch] wase4711:
13 hours here, 8 hours screen time, and 61% battery left..lots of phone calls, texts and tons of emails, with about 2 hours of listening to streaming music

My EVO 3d would have been dead by now...

Hope the 8 folks with battery issues get their problem fixed, 'cause there isn't one here!
[Samsung Epic 4G Touch] Sterist:
now there is, in fact, a regression in kernel 2.6.38 that drains battery ....... BUT (most, if not all?) gingerbread is on 2.6.35

reboot your phone after usage and it will idle normally. unfortunately this be necessary.
[Samsung Epic 4G Touch] Duce HD2:
This is the best, fastest and most lag free phone available on the market atm hands down. We'll get ics etc, and wait a few months and the dev community will get this thing flying.
[Samsung Epic 4G Touch] mngdew:
I already returned mine, but it looks like mine was also having the battery issue.

Mine can only last about 12 hours, but I thinks it was all due to Sprint bad data coverage in L.A. area. It constantly looked for data signal.
[Samsung Epic 4G Touch] strippedman:
I have done nothing battery-saving-wise other than installing Juice Defender and my phone is lasting forever. I bought an extra battery and charger when I bought he phone because I knew I'd be abusing it and didn't want to have to worry about charging in the middle of the day...haven't had to swap out the battery even once yet. I don't know my full stats, but I'm using it to the max and easily lasting all day. So yeah, not returning this mofo, it's my lover.
[Samsung Epic 4G Touch] madsquabbles:
the evidence does show that there is a problem with some of our phones. what hasn't been found yet is what's causing it. on mine root doesn't affect it, but flashing to zedomax's v3 may have. i can't say for sure without testing as it could just have been coincidence. i'm back on zedo v4 after going back to stock + root for the last 5 days with no problems.

as long as i have root + stock with no problems i'm happy. this is the first phone i've had in quite a while that i've had no plans on returning b/c of bugs or performance.
[Samsung Epic 4G Touch] moeinyoho:
im returning because touchwiz is awful
[Samsung Epic 4G Touch] Vega:
change the prl. simple
[Samsung Epic 4G Touch] graffixnyc:
I dont plan on returning it. Honestly 4.52 is as big as I want to go. I still think 4.3 is perfect size but for me 4.5 is the max. The next nexus is rumored to have over a 4.6 screen. I know that doesnt seem like a lot but IMO the 4.52 is already pushing it in size..
[Samsung Epic 4G Touch] killerbicycle:
did you consider an alternate launcher? I think Touchwiz looks too similar to iOS, i don't want my phone mistaken as an iphone, i want it known that its not another piece of apple garbage (personal opinion). But if touchwiz is the only problem you have with the phone, try another launcher with a new theme.
[Samsung Epic 4G Touch] Vega:
just get a differnt launcher. try go just trie after a year using somethng else. they have come along way!
[Samsung Epic 4G Touch] eman3316@optonline.net:
Sorry, I am not believing anyone is getting 7 - 8 hours of on screen time with this phone or any other android phone for that matter with a stock battery.