nfc task launcher - Sprint Samsung Galaxy S III

I keep getting a download error when downloading nfc apps. Anyone else have this problem?

You need to be a bit more specific. I've downloaded it just fine. What rom are you on? Did you try wiping the market cache?

Sorry, I'm on blazer 1.8. I'm going to attempt a screenshot here.Well I can't figure out out. Anyways it gives me an error processing purchase. Only on things involving nfc software. I cleared cache and no change.

swipe the side of your palm across the screen for a screen shot..(yes the entire side of your palm)

Ok see if this works

Related

[Q] Problems with SyndicateROM Frozen

Hi all,
I recently installed SyndicateRom Frozen after I got stuck on Eb13 thanks to Sprint. It worked out really well (so fast!) for a while but I am now having problems varying from strange but tolerable to very bad.
Here is the exact order of what I've done:
1) from eb13, I used odin to get DI18, then modem only to EC05, installed CWM3 and wiped data/cache/dalvik cache 3x each.
2) I used CWM3 to flash SyndicateRom Frozen (the latest version)
3) it worked pretty well, but then I (stupidly I guess) installed Go Launcher Ex and then everything went to hell
4) it ran for a while then suddenly EVERYTHING force closed. restarting it just gave me 9000 more force close boxes. so I...
5) wiped data/cache/dalvik 3x, re-flashed syndicateROM
So here I am now with the following problems:
1) The phone randomly freezes irreversibly (only solution is to pull the battery). It seems like it happens in the browser only (stock Syndicate browser)
2) The phone randomly freezes for a little while only (all the time)
3) The email app force closed (fixed this for now by clearing its data, from forum)
4) With auto-rotate OFF, nothing rotates EXCEPT my phone page.. What the heck? The phone page (ie click the phone icon) rotates regardless of what setting auto-rotate is on
5) The phone sometimes just decides to restart itself. And rarely, the restart never finishes.
6) Whenever I open up google navigation, it says "checking navigation availability" for 5-10 seconds. This never happened before
Now, what do I have running?
-SetCpu (this was running before I had go launcher and I had no problems). it's set very modestly -- 200-400 with screen off (and I dont have the no-wakeup problems some people talk about) and 400-10000 with the screen on, on demand.
-Ultimate Juice
If anyone knows what I can do to fix this, I'd really appreciate it. Thanks.
Thanks for the detailed post - it helps. Your issues, though, are almost definitely kernel-related. Freezing is a sign you need to use kernel version 1.0.4 linked from the second post, or VisionKernel. Try VisionKernel first. If it solves your issue, you're good to go.
Anything related to screen rotation is outside of the ROM - run the sensor calibration process.
k0nane said:
Thanks for the detailed post - it helps. Your issues, though, are almost definitely kernel-related. Freezing is a sign you need to use kernel version 1.0.4 linked from the second post, or VisionKernel. Try VisionKernel first. If it solves your issue, you're good to go.
Anything related to screen rotation is outside of the ROM - run the sensor calibration process.
Click to expand...
Click to collapse
Thanks for the quick reply. I'll try installing a new kernel when I get home tonight. BTW, awesome work with the ROM.
Xinlitik said:
Thanks for the quick reply. I'll try installing a new kernel when I get home tonight. BTW, awesome work with the ROM.
Click to expand...
Click to collapse
Thanks for your support!
im having similar problems, but mine only occur when the battery dies
after i restart a lot of my apps are force closing without even running them, and when i press the home button the screen is blank. (i also use go launcher)
You kno this same thing happened to me. I finally realized it was probably because I was restoring my apps with titanium. I decided to just re-download my apps and restore only app data with titanium (angry birds etc.). This helped me. And this was all after installing launcher pro. So there was some sort of conflict there. Are you restoring apps?
Sent from my SPH-D700 using XDA App
i didnt restore my apps with titanium that time but i switched from go launcher to launcher pro and i dont have that problem anymore
Hmm...i guess just stay away from that launcher then...haha.
Sent from my SPH-D700 using XDA App
I'm not sure if his problems were strictly Go Launcher related. I've been using Go for 2 days now, with no problems (yet... knock on wood).
Sent from my SPH-D700 using XDA App
So here's an update:
-No, I'm not using Titanium backup.. I manually reinstall all my apps.
-I tried out the VisionKernel and it seemed ok for a bit, but I'm freezing again and my apps are all force closing. I uninstalled SetCpu completely in case that was causing a problem, but it didn't make a difference.
I'm going to try using v1.04 next... if that fails I guess I just can't use this rom
Would setting myself back to DI18 -> EC05 -> Syndicate possibly work? (as opposed to just re-flashing syndicate)
This was happening to me regardless of my kernel, and I even (twice) ODIN'd to [DI18?] then OTA to EC05 and then wiped everything 3 times, and flashed, 1st flash never works for me, so 2 flashes both times completely clean as well as when flashing kernels
1.0.2 worked just fine for me but as soon as 1.1.0 came I get freezes and FC's all over the place. I have given up on 1.1.0 and will try it when a newer version comes out
Media
First off want to say, love the ROM so far, you guys rock. After a few failed attempts at getting CWM 3 on my phone, I was finally able to do so and get everything installed. The only problem I'm having is with my media files. I get random FC when I play my music, my photo gallery doesn't appear, when I try to access my mp3's directly from my SD card, it says "file type not found" and it does not like the Zedge app at all. I've tried both the standard and fully loaded versions with the same results. I have the visionkernel downloaded, just in case I need to try it, but if at all possible, I'd like to stick with the twilight (I use the camcorder often). Any other suggestions? Thanks in advance!
androikid said:
This was happening to me regardless of my kernel, and I even (twice) ODIN'd to [DI18?] then OTA to EC05 and then wiped everything 3 times, and flashed, 1st flash never works for me, so 2 flashes both times completely clean as well as when flashing kernels
1.0.2 worked just fine for me but as soon as 1.1.0 came I get freezes and FC's all over the place. I have given up on 1.1.0 and will try it when a newer version comes out
Click to expand...
Click to collapse
Yea, did basically the same thing last night. It went fine for a day, but it went to hell again tonight. Oh well, we'll have to wait for a new version I guess.
Xinlitik said:
Yea, did basically the same thing last night. It went fine for a day, but it went to hell again tonight. Oh well, we'll have to wait for a new version I guess.
Click to expand...
Click to collapse
As noted many times in many places, if you're having issues with 1.1.0 that aren't freezing/battery life (these are both the kernel and have been discussed everywhere), a few simple troubleshooting steps will get you exactly where you need to be.
allheilkingmatt said:
First off want to say, love the ROM so far, you guys rock. After a few failed attempts at getting CWM 3 on my phone, I was finally able to do so and get everything installed. The only problem I'm having is with my media files. I get random FC when I play my music, my photo gallery doesn't appear, when I try to access my mp3's directly from my SD card, it says "file type not found" and it does not like the Zedge app at all. I've tried both the standard and fully loaded versions with the same results. I have the visionkernel downloaded, just in case I need to try it, but if at all possible, I'd like to stick with the twilight (I use the camcorder often). Any other suggestions? Thanks in advance!
Click to expand...
Click to collapse
Format your SD card.
As noted many times in many places, if you're having issues with 1.1.0 that aren't freezing/battery life (these are both the kernel and have been discussed everywhere), a few simple troubleshooting steps will get you exactly where you need to be.
Click to expand...
Click to collapse
My issue is freezing, and I tried all of the alternate kernels. Sorry if my language wasn't precise- I mean new kernels.
I've actually given it one last try...I'm wondering if the clock is set too low for my phone by default, so I've got setcpu on min400 max1000. I'll let ya'll know how it turns out... (Stable so far although suddenly my home key doesn't work, hah.)
Xinlitik said:
My issue is freezing, and I tried all of the alternate kernels. Sorry if my language wasn't precise- I mean new kernels.
I've actually given it one last try...I'm wondering if the clock is set too low for my phone by default, so I've got setcpu on min400 max1000. I'll let ya'll know how it turns out... (Stable so far although suddenly my home key doesn't work, hah.)
Click to expand...
Click to collapse
400mhz shouldn't be necessary. If your freezes were wakelocks, and you had your minimum frequency at 100mhz, that was your problem - not all devices can handle it, and need to be at 200mhz.
400mhz shouldn't be necessary. If your freezes were wakelocks, and you had your minimum frequency at 100mhz, that was your problem - not all devices can handle it, and need to be at 200mhz.
Click to expand...
Click to collapse
They were actually freezes during use-- I luckily never got a single wakelock.
I'm not sure if there was a pattern or not, but I think the Market, Go SMS Pro, stock Email, and stock browser were the main freezes. Then again, those are also the apps I use quite frequently
Sorry to double reply, but I can't edit yet.
@androikid
It just occurred to me that the freezes wouldn't be that bad if not for the force closes that occur afterward (due to data corruption). Maybe we should just turn journaling on so the a freeze just means a restart, rather than a re-flash.

Camera Error - Cannot connect to camera.

Anyone else getting this error? After reading the two main errors seem to be faulty camera hardware and bar code scanning apps. I uninstalled my bar code scanner and the problem persists. There is a small dent next to my flash under the camera but this came with the phone and my camera worked for a while. Taking the battery out and putting it back in fixes the problem about half of the time, but only is good for one to two uses. I'm thinking of sending this in, but I'm waiting until the SGSII HD is out in case they offer to replace it with any phone. Wishful thinking, I know.
And here's the error:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
HJZS2K said:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
Click to expand...
Click to collapse
Stock ROM not rooted. No modifications what-so-ever.
8mileroad said:
Stock ROM not rooted. No modifications what-so-ever.
Click to expand...
Click to collapse
Try doing a factory reset. Sometimes an app installed on the phone might screw up with a hardware's function. For example, I've always use Screebl Pro on my phone to let it control how my screen turns off. I decided to try their new Beta version. A few days later, I cannot seem to manually turn off my screen by pressing the power button. Every time I press the power button, the screen will come back on on its own. I can try up to 4-5 times before it eventually goes off. I though my phone finally broke as I tried uninstalling and reinstalling apps, changing settings here and there to no luck. I finally realized about the beta Screebl I had installed, and decided to disable it. The moment I did that, the phone was back to normal, no weird things happening to it.
So try doing a factory reset first before sending it back.
Strangely enough uninstalling Reconage has seemed to fix this. Can anyone else confirm it breaks your camera? The comments don't say it does so it must be something with the Nitro.
I get it too on cm7 all the damn time. I can record 1 video then after I stop, it messes up and I have to reboot to record again.
Any more definitive answer on this issue? My wife's Nitro HD has started giving this error in the last few days and no amount of rebooting seems to be fixing it. She is stock plus a few apps. I uninstalled nearly everything that uses the camera, reboot the phone, and still have the problem.
Alternatively, is there a way to see what apps were installed/updated by date? The last photo she took was on 6/13, so if we can figure out what apps have been updated since then that might help us get to the bottom of the issue.

[Q] Maps/Navigation force closing on custom ROM/Kernel - HELP Please!

Hi all,
Hopefully someone can shed some light on this and help a tortured soul. By no means am I an Android expert, but I definitely am not a noob. I had an S2 in the past and done plenty of flashing there, and now own a Bell SGH-I747M S3... my precious...
First off I tried a whole bunch of different ROMs, of all flavors (AOSP, AOKP, CM10, PARANOID, and some TW), and a lot of them are awesome. However, I found that after having done so much flashing and customizing using other people's work, it was now time for me and attempt to make my own ROM. I feel I now have the knowledge to do so. Don't get me wrong, I am far from a Dev, and I don't do much coding at all. I found this great suite called Android Kitchen, which pretty much guides you through the steps for making your own ROM, and it's great for learning.
In the end, I was able to come up with a final working version of my own ROM, built from scratch using the original official Bell JB 4.1.1 update file. and I have to say I am quite proud of it, as it has all the apps, features and theming that I want, and works quite well I might add. I get great results performance and battery wise (for my taste and needs) when using my ROM with KToonsez kernel.
BUT!!... as good as I think the ROM is, it is unfortunately not flawless. I do have an issue (the only one I could find so far after 2 weeks using it), and for me it is a BIG issue. Maps/Navigation does not seem to like the ROM/kernel combo on MY phone. I say MY phone because I have setup a friend with pretty much the same thing, and he is not experiencing the same issue.
Here is a description of the problem I get. Let's say I go to my contacts and select one with an address. I will touch the address, then Maps opens no problem, and finds the place, and I also get fast GPS lock, no issues there either. Then I will select Navigate to get a voice turn by turn description while driving. The Nav app starts OK as well and seems to work fine. Then after a few minutes (sometimes 2 sometimes 10), Navigation will shutdown, and I get a pop-up saying "Unfortunately Maps has stopped working...". When I OK that, after a few seconds, Navigation starts talking to me again, although not on screen. Also a Navigation icon will appear in the notification area, and if I hit that it resumes Nav, as if nothing had happened. Another few minutes like that, and then I get the same message again, but this time it crashes for good. ALWAYS!!
Troubleshooting:
- Flashed the ROM/Kernel 3 times now. Always wiping and formatting ALL!
- Cleared cache and data from Android Settings/Applications
- Cleared cache from Maps settings.
- Re-installed Maps
- Wiped phone cache, dalvik cache and fixed permissions from recovery.
- Changed kernel back to stock (that seems to work fine btw,, but I do not want stock kernel, plus the setup I want works well on my friend's S3, same as mine, which I setup myself for him (he's a total noob)).
- Changed kernel again from stock to KToonsez (that also works fine after that, however I get other things that start not working well... too many).
- I always wipe cache, dalvik cache and fix permissions after changing kernels.
I have been poking at this for about a week now, and I am tired! I was hoping someone would have a suggestion, maybe from past experience. The only thing I can think of that is different on his phone and mine is the apps that we restore after installing the ROM and kernel (Titanium Backup, user apps and data only, nothing related to system is touched). I am guessing one of my apps could cause a conflict, but pardon my laziness, but I really do not feel like testing / installing my apps one by one to hopefully without guarantee find a culprit... way too many apps for that So I am testing my luck here on XDA... there are a lot of smart people here
I appologize for the lenghty post, but this way, there is less chance I left anything out... PLEASE HELP!!!
Raz...
Sorry for the bump guys... I was really hoping someone can give some input here. Desperate for a solution here!!
Thanks

[Q] Apps crashing since Kit Kat OTA update

I checked for OTA update on 2/6, 8:47pm and 4.4.2 was found and 'successfully' installed: HTC6500LVW_3.11.605.1_R2-2.10.605.1
Ever since, apps have been crashing on the phone like crazy. "Unfortunately, ____ has stopped." The apps that crash most often are Maps (about 5-10 sec after opening each time), Sense 5.5 and Gmail, but others that I don't use as often have done the same. The phone also now reboots itself frequently (5+ times a day).
Two other issues I've noted are (1) when returning to home screen after closing an App, it sometimes takes around 10 sec for icons to appear (possibly Sense restarting?), and (2) when I wake the phone up, the screen turns on and then I try to swipe down from the top to check notifications and the screen goes blank.
Has anyone else seen this type of instability with HTC One and KitKat? Any suggestions?
I've tried searching for a new update hoping they've fixed some of these bugs, but it tells me I'm up to date.
Have you tried clearing the cache and data for the apps that are crashing? There are no bugs like that in kk. It sounds like some data just got corrupted during the update. If wipimg the individual apps data dosent work you may have to do a factory reset or an ruu.
cmlusco said:
Have you tried clearing the cache and data for the apps that are crashing? There are no bugs like that in kk. It sounds like some data just got corrupted during the update. If wipimg the individual apps data dosent work you may have to do a factory reset or an ruu.
Click to expand...
Click to collapse
I'll try clearing the caches. Should I clear it for Sense though? I figured out the screen going blank when I go to swipe it, it seems to be a proximity sensor sensitivity issue. If I approach with my finger from the right (opposite the sensor), there's no issue. So it's just the sensor now picking up my finger passing over to swipe and thinking it's me putting my phone up to my face maybe?
Yeah you can clear it for sense too, but if you clear data it will wile out all the apps settings. For sense that means all the settings in the settings menu. But i dont really see what else you could do, other than a factory reset, or ruu, which will wipe everything.

stuck in portrait

Having a bit of an issue with the auto rotation on my OP3 where the screen snaps back into portrait after being rotated either by me or by an app, then locks the device. (if the lockscreen is activated) most apps respond by crashing once this happens.
I've dug all through my settings and come up empty on finding something that could be responsible. So I'm thinking it must be an app, or Xposed module, but again dug through everyone's who could possibly have setting that could do it, again came up empty.
So I'm really frustrated by now and wondering if anyone else has seen behavior like this, or knows what could be the cause.
I'm on the Resurrection Remix OS and as mentioned Xposed is installed. I'd be happy to post a txt of all my apps if someone is interested.
Thanks in advance, Idk what else to do but wipe it.
So figured I'd at least ask you guys before I do, just in case.
(Edit)
Guess I can add no recents menu to the list of effected. Plus now that I have that "on button push" ability to trigger this, I see it's actually resetting the system UI. It seems to crash then reload immediately, triggering the screen back to portrait and the system bar up top to redisplay (usually hidden).
I see a factory reset in my near future...
Well that's got to be a first, seems all I had to do to fix it was threaten to wipe it and it fixed its self!?
Seriously I haven't done anything since I posted this at lunch today, except start a Titanium backup, (which is still running) and as soon as I get home ready to delete it, I opened it up to a landscape view that wasn't durping out. How bazaar... Not sure now if I can trust it to behave or maybe I should wipe it anyway to be sure...

Categories

Resources