I've tried several roms and I keep getting the no connection retry prompt when I open the play store. I've tried removing my account and signing back in, clearing data and caches, toggling sync and anything else I can think of. I also get the red sync error icon under my account in settings and my signal icon is staying gray no matter what I do. It doesn't seem to matter if it's aosp or touchwiz.
Sign into Google with a new account then sync everything then go back to your old account then you should be good.
™Sent From My ™SLIMROM™ BUILD 1.8- 4.3.1 Rom Running BMS Kernel With ™Killjoy™ Script Powered By 7000MAH Of LEMON JUICE Power™
It still won't sync my old one and even with the new account selected in the play store it still gives me the error.
I wish I knew the answer myself, my play store only works on certain roms.
Sent from the S3 of The Afro Samurai
TheAfroSamurai said:
I wish I knew the answer myself, my play store only works on certain roms.
Sent from the S3 of The Afro Samurai
Click to expand...
Click to collapse
This is something new to me. why it only works onn certain roms?
jackthomas251 said:
This is something new to me. why it only works onn certain roms?
Click to expand...
Click to collapse
I wish I knew, my play store only works on stock rooted and synergy. Any other rom I get no connection. I've pretty much given up on it. I've tried every fix I could find about it. I even Odin'ed back to ICS and that had no luck either. I'm happy with synergy until we get 4.3 or I get a new phone whichever comes first...
Try different version of play store. I actually had this problem today(no connection) with one of my phones. One version from team blackout didnt work while a version from official gapps for the specified rom did.
Just try out different Gaaps Packages until one works. Check MD5 on each package
Sent from my SCH-I535 using Tapatalk
Thanks for the gapps suggestions guys but I don't do aosp so that's not my issue, though I have tried pushing different versions of play store into tw roms to no avail.
Sent from the S3 of The Afro Samurai
I'm on 4.3 and after about a week it finally synced and I was able to log in to the play store. Not sure what happened.
TheAfroSamurai said:
Thanks for the gapps suggestions guys but I don't do aosp so that's not my issue, though I have tried pushing different versions of play store into tw roms to no avail.
Sent from the S3 of The Afro Samurai
Click to expand...
Click to collapse
Have you tried this one? I use 4.3.1 now but it worked fine for me when I used touchwiz.
http://forum.xda-developers.com/showthread.php?t=1839871
JennyLikesSka said:
Have you tried this one? I use 4.3.1 now but it worked fine for me when I used touchwiz.
http://forum.xda-developers.com/showthread.php?t=1839871
Click to expand...
Click to collapse
I make regular nandroids so I'll give it a shot, plus I've found another fix that I haven't tried yet. I'll let you know how I come out.
Related
Since this is my first NFC device, I always wanted to play with it. However, I can't stand the sight of touchwiz so here I am on cm9. I've tried this:
http://www.modaco.com/topic/354635-region-device-root-patched-google-wallet-apk-11-r67-v12/
and looked at this even though it says its for touchwiz only (so I haven't tried it):
http://forum.xda-developers.com/showthread.php?t=1769083
My question is, is it possible at the moment for cm9 and google wallet to work together at the moment? If so, how can it be done?
I haven't seen it working on anything but stock yet. I've tried it on 4 or 5 different ROMs.
f3liC said:
Since this is my first NFC device, I always wanted to play with it. However, I can't stand the sight of touchwiz so here I am on cm9. I've tried this:
http://www.modaco.com/topic/354635-region-device-root-patched-google-wallet-apk-11-r67-v12/
and looked at this even though it says its for touchwiz only (so I haven't tried it):
http://forum.xda-developers.com/showthread.php?t=1769083
My question is, is it possible at the moment for cm9 and google wallet to work together at the moment? If so, how can it be done?
Click to expand...
Click to collapse
Hi
I have a nexus S running CM10 Jellybro euroskank nightlies.
I have cerberus anti theft app installed. It works perfectly on wifi, and works on 3g when the screen is on.
But when the screen has been off for a while, I get "problem communicating with your device" error when I try to use cerebus dashboard to connect to the phone.
I understand that cerberus uses google services to connect.
There must be something causing it to cease working when sleeping. But I can't figure out what. I have tried the market version and the flashable zip version of cerberus. I don't have any extra battery saving apps installed.
I really want to get this working.. it used to work on the JB rom I had a while back..
So if anybody has cerberus working perfectly (or at least most of the time) on their ICS nexus S can you kindly tell me which ROM you are using so I can try that?
Or any other suggestions would be greatly appreciated.
Thank you =)
did full wipe yesterday and installed Brainmasters JB.4.1.2.JZO54K.Nexus.S with gapps-jb-20121012-JZO54K-Formula84.
Same stuff happening arghh
I do know with depending the kernel used and cpu governors it can cease most of the phone functionalities when screen off. Try with stock.
Sent from SGH-T959
eksasol said:
I do know with depending the kernel used and cpu governors it can cease most of the phone functionalities when screen off. Try with stock.
Sent from SGH-T959
Click to expand...
Click to collapse
thanks very much.. I just had whatever kernel came with the ROMs.. but I will definitely try that next time
I've just finished installing CM7.2 and setting everything up again. Getting tired of flashing roms and installing everything again for now hehe. And everything is rather snappy on this old gingerbread rom. =) So I will keep this one for a couple of days to see how it goes.. not the easiest thing to test when ya gotta wait 20mins+ to check.
I'm using lynx-1.5.0-oci kernel atm because the one that came with this rom didn't work with droidwall.
Thanks again
azlemad said:
thanks very much.. I just had whatever kernel came with the ROMs.. but I will definitely try that next time
I've just finished installing CM7.2 and setting everything up again. Getting tired of flashing roms and installing everything again for now hehe. And everything is rather snappy on this old gingerbread rom. =) So I will keep this one for a couple of days to see how it goes.. not the easiest thing to test when ya gotta wait 20mins+ to check.
I'm using lynx-1.5.0-oci kernel atm because the one that came with this rom didn't work with droidwall.
Thanks again
Click to expand...
Click to collapse
As I rooted my phone when cm9 was out, I never really were into gingerbread rooms and kernels... Can you advise me something?
jojoost said:
As I rooted my phone when cm9 was out, I never really were into gingerbread rooms and kernels... Can you advise me something?
Click to expand...
Click to collapse
What do you need help with?
Sent from my Galaxy Nexus using Tapatalk 2
so yeah same problem with the cm7.2 and lynx kernel.
I installed an app called "Wake My Android" and set it to wake the phone every 9 minutes.
And yes, it now works sometimes.. I guess right around the times it gets woken by the app
Now to figure out how I can turn off this sleep/ idle thing so that it stops happening and I wont need this Wake My Android app
Will a stock kernel work with CM7.2? will droidwall work too?
Can I disable it in the kernel
Don't know what to say since I don't use Cerberus. I do know Android phones shut off or slow download internet speed when you turn off the screen. In WiFi settings I had to set it to always stay on during sleep and I use kernel with the "WiFi PM FAST" feature.
Try a different app like Zoner antivirus which has antitheft feature.
As I said in my older thread about custom roms, I've successfully installed the liquidsmooth rom on my S3, it is awesome, well it looks awesome but I have a few issues, one is minor but the other is major..
First the minor issues, I discovered that the Google play store app is missing, which made getting stuff a major challenge! Until I figured out a way to install aptoide as a replacement for it, which also wasn't easy, as liquidsmooth comes with a crappy browser that doesn't even launch.. So I had to install Firefox in some way in order to load aptoide, can't remember how I did it, it was one long hectic day yesterday.. Anyway the point is, I tried downloading and installing the play store app and it just keeps crashing when I try to load it. I tried restarting and different versions of it but to no avail, is there no hope for this?
Here's the major issue, one that might force me to abandon liquidsmooth and maybe go with the cyanogen mod, which I tried but didn't really like because of the android version it uses, 4.0.4! I mean on the stock Samsung os I was already in version 4.1.2 so I wasn't happy with having to go backwards.. I digress, the major issue I'm having is with the phone, people tried calling me and it rings once on their end then goes into a busy signal, and my phone doesn't even seem to know it happened! This is a phone first and therefore it doesn't matter how cool liquidsmooth looks and feels, without a proper phone its almost pointless! Is there a fix to this problem guys? I sure hope so.. In addition, sometimes I'm downloading something and it just freezes, none of the buttons work, forcing me to reboot the entire phone, what's up with that? Is liquidsmooth just flawed that way?
Thank you for reading, I hope you can help, I would sure appreciate it.
Peace
Sent from my GT-I9300 using xda premium
I downloaded the new PA 3.60 6/11 build from notta yesterday with KT747 Kernel and RErick universal setup. After using for a while, without attempting to call, I was more than happy. At work today I called my girlfriend and in the middle of our conversation the call dropped. Ever since then whenever I try to make a call I get a "com.android.phone has stopped" message or it will connect, close phone screen but keep call in status bar, show that same message, then drop the call. Sometimes it says "Mobile network not found" after trying to call then will reload my bars after. Can't receive calls either but my network shows I have bars and every IMEI & numbers alike are there. Restored nandroid and calls worked.
Thought it might be kernel combo so tried to wipe everything and reinstall but problem persisted. Any ideas on how to fix?
Thanks in advance!
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
andrewk7750 said:
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I've flashed the 6/10 gapps both times I flashed the ROM, unfortunately. Maybe bad download? I don't know at this point.
Its RErick's from Team Kernelizers setup for the KT747 kernel. Can find him on the TK Mod thread. Great battery life supposedly but didn't get to try it for too long since calls didn't work.
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
antiseen said:
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
Click to expand...
Click to collapse
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
kenbrownstone said:
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Since I've been having so much trouble with any rom I haven't used a custom kernel since my thunderbolt days. I run whatever kernel the rom comes packaged with.
But like I said, it's probably my phone. It has defective bluetooth that I didn't figure out until well after I purchased the phone. It's got constant loud crackling and popping on stock (ironically, non existent on aosp roms). I doubt that's related but just illustrates the weird differences between phones.
Had the same problem less than an hour ago when i really needed to make a phonecall. Had to restore to my backup i made before flashing PA. Hell of a time for it to stop working.
Sent from my SCH-I535 using xda app-developers app
Well after first believing it was just my phone, after reading these comments as well as the PA thread I've come to the assumption that its something with the ROM and how it behaves with the phone app. Hopefully the details will get resolved soon cause I was really enjoying the new PA. Until then, sticking with hyperdrive.
Thanks guys.
had this problem since upgrading to the 6/11 build.
i could make calls out as long as i didnt press the ok button to dismiss the process stopped message.
i could not receive calls hwoever. it does ring like it should, but it does not allow me to answer.
using latest gapps package.
I've had this problem on both 6/12 and 6/14, using the 6/10 gapps.
Any chance anyone has come up with some way to resolve this?
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
ddurandSGS3 said:
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
Click to expand...
Click to collapse
Good suggestion. Really liked PACman for a while, but eventually my call got dropped and I ran into the exact same issue from that point on. At this point I've just decided to go with a TW based rom. With hyperdrive you can still have pie and download Floating Notifications app that is practically the same thing as halo but also has themes available too.
Until that bug can be fixed, going to stick with Hyperdrive. Sweet rom anyway.
I've been having a lot of random reboots when using AOSP based roms. So far I've used CM10.1.0, 10.1.3, 10.2, and liquidsmooth 2.10. As long as it is AOSP, the phone randomly reboots. Sometimes while it's just sitting on the charger or in my pocket.. After digging through this site I tried installing the firmware from here:
http://invisiblek.org/d2firmware.html
but I'm still having random reboots. I have a stock battery, and a later model brown S3 phone. TW roms work flawlessly.
Any advice?
As far as I am concerned CM is not very stable. Plus if you flash nighties that could be your issue. I read other people having random freezes and hot boots on LS 2.10. My suggestion to figure out if it's really AOSP (seriously doubt it) try LS 2.9. probably the most stable AOSP ROM out there. Also I have heard good things about older Slim Bean Builds. Do NOT do anything 4.3 related. 4.3 ROMs are still considered unstable.
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
As far as I am concerned CM is not very stable. Plus if you flash nighties that could be your issue. I read other people having random freezes and hot boots on LS 2.10. My suggestion to figure out if it's really AOSP (seriously doubt it) try LS 2.9. probably the most stable AOSP ROM out there. Also I have heard good things about older Slim Bean Builds. Do NOT do anything 4.3 related. 4.3 ROMs are still considered unstable.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ive been using several 4.3 roms without one issue. Dirty Unicorn and Carbon have been prefect so far. Using latest twrp, full wipe and stock kernels.
Noremacam said:
I've been having a lot of random reboots when using AOSP based roms. So far I've used CM10.1.0, 10.1.3, 10.2, and liquidsmooth 2.10. As long as it is AOSP, the phone randomly reboots. Sometimes while it's just sitting on the charger or in my pocket.. After digging through this site I tried installing the firmware from here:
http://invisiblek.org/d2firmware.html
but I'm still having random reboots. I have a stock battery, and a later model brown S3 phone. TW roms work flawlessly.
Any advice?
Click to expand...
Click to collapse
What revision is your phone? Rev4? Rev5? My phone is a Rev0 and I'm not having any problems with running AOSP based ROMs.
I did too. I'm not sure WTF was going on, but ASOP/CM would be great for about a month, and then it'd start random rebooting. After it'd start random rebooting, the way to stop it would be to ODIN back to stock, and start over. Clean installs, nandroid restores, full formats.. None of it worked.
So here I stay on a crappy 4.1.2 TW ROM.. itching to return, but not really seeing enough improvements to warrant another go.
How are you restoring apps and data? I had problems after restoring via titanium backup, but when I restored selectively (just apps and data I really needed) with helium it's running fine.
this has to be a very late revision of the phone because it comes in the brown color that Verizon didn't start offering until recently. Even so, how do I determine the revision?
Noremacam said:
this has to be a very late revision of the phone because it comes in the brown color that Verizon didn't start offering until recently. Even so, how do I determine the revision?
Click to expand...
Click to collapse
I believe it states the version when in download mode. (Vol down + home + power at a powered off state)
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
I believe it states the version when in download mode. (Vol down + home + power at a powered off state)
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Check in terminal emulator.
Su (enter)
cat /proc/cpuinfo (enter)
This will give you the revision number and a lot more about your phone.
I have "rev 4" on my brown GS3 and have been running CM10.1.3. The only time my phone crashes/reboots is when I attempt to use the front facing camera with a third party camera app.
Is it possible to get some logging of what's triggering the crash, so someone can take a look at it? Also right now, to the person who asked, I am reinstalling my apps from scratch from the play store. Since I haven't built up a lot of custom data for this phone to make it worth backing up.
I miss AOSP something fierce.
Noremacam said:
Is it possible to get some logging of what's triggering the crash, so someone can take a look at it? Also right now, to the person who asked, I am reinstalling my apps from scratch from the play store. Since I haven't built up a lot of custom data for this phone to make it worth backing up.
I miss AOSP something fierce.
Click to expand...
Click to collapse
Download aLogCat from the play store and start the app. Then trigger the crash
Sent from my SCH-I535 using Tapatalk
What do you do if you can't cause it to crash? Mine are always totally random. It'll crash during a call, it'll crash while web browsing, it'll crash while locked in my pocket.. The only time it won't crash is when you want it to!
Do you just end up with a giant log file then or what?