Galaxy S3 rooted, CM10, NFC gone, help? - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I've been using the nightlies for about a week now and everything has been going smooth. I wanted to activate Google Wallet on here so I followed the guide on how to install it on the SGS3, and when I unzipped the file, Wallet was there. When activating, it said I needed to turn on NFC, but it was nowhere to be found. I downloaded the nfc.apk but it wouldn't install for whatever reason. I've been lurking but I can't find anything to get it back. Any help?

I'm running CM10 M1 and NFC is working fine out of the box. Go to system settings -> Wireless & Networks -> More... and you will find the check box to turn NFC on.
-darren
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Wipe everything, reflash with stock kernel. Sounds like a bad flash
Sent from my SGH-I747 using Tapatalk 2

It isn't CM10, I flashed that a while ago and had it up until I unzipped Wallet. Is there any way to get NFC back without restoring?

Same issue...only with CM10...
...it seems so anyway. Flashed ROMOW and NFC is working fine.
CM10, as of the last nightly build (21-09-2012) shows as either unticked or when ticked, greyed out and unresponsive...can no longer change the setting.

marcusleemitchell said:
...it seems so anyway. Flashed ROMOW and NFC is working fine.
CM10, as of the last nightly build (21-09-2012) shows as either unticked or when ticked, greyed out and unresponsive...can no longer change the setting.
Click to expand...
Click to collapse
Yeah, I don't know why this isn't more popular on the forums. I ended up having to restore and I'm afraid of trying again, because I want NFC to work.

narya1 said:
Yeah, I don't know why this isn't more popular on the forums. I ended up having to restore and I'm afraid of trying again, because I want NFC to work.
Click to expand...
Click to collapse
Just came across this issue too in a cm10 nightly and found this post. I also get it on slimbean 2.5... The option is there but it greys out when I try to tick it.

thazlett said:
Just came across this issue too in a cm10 nightly and found this post. I also get it on slimbean 2.5... The option is there but it greys out when I try to tick it.
Click to expand...
Click to collapse
I am having a similar problem, but the NFC options aren't there at all. CM10 M2 release D2VZW.

Ditto.
jammerml said:
I am having a similar problem, but the NFC options aren't there at all. CM10 M2 release D2VZW.
Click to expand...
Click to collapse
Ditto, I have M2 on my S3 Verizon and have no option under Wireless at all! I'm surprised this gets so little attention or mention!

Yep, I got the same thing going on with CM10 M2 D2Tmo when trying to flash Wallet. NFC options do not exist anymore. I'm going to restore from my backup and try running just the modded APK file listed in the Wallet thread and see what happens. I'm predicting that what will happen is I will give up and go to lunch

Figured it out.
So, apparently we've been doing it wrong, as we've been flashing nfc libs that we don't need. I think.
If you edit your build.prop file with these settings, do not use the htc_jewel.
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
Then, in this thread, http://forum.xda-developers.com/showthread.php?t=1769083
go to the bottom of the first post and download this file.
com.google.android.apps.walletnfcrel.modaco.1.5-r79-v5-2.zip - [Click for QR Code]
Reboot to recovery, wipe your cache and your dalvik cache, flash this file and reboot.
Google Wallet will say unsupported device at the top, but it's basically just yelling at you for rooting your device because it will compromise the security of google wallet.
So, either you care or you don't care.
I was able to add my bank debit card that I use in google play without a fight.
Hope it helps,
Good Luck!
---------- Post added at 03:47 PM ---------- Previous post was at 03:44 PM ----------
Oh yeah, it would be a good idea to edit your build.prop back to what it was before that way you reduce the risk of bricking your device or something else equally unexciting to deal with.

Related

[How to] Google Wallet on AOSP ROMs

This brief guide is to help others get Google Wallet working on AOSP based ROMs. There are guides already by Dafoxs and Antiochasylum but they are apparently for Samsung based ROMs and the lib files, etc are incompatible with AOSP based ROMs. Personally, I tried several times and the NFC setting kept getting wiped out so I had to do restores. These instructions are what ManelScout4Life posted and the thread is at his request. All the credit goes to the DEVs that made this possible - I am NOT a developer - Seriously... Lastly, the typical disclaimer applies - I take no responsibility for bricking your phone, etc. I highly recommend making a nandroid backup before any mod like this. These instructions worked on JellyBAM 3.2 compiled by ManeelScout4Life - http://forum.xda-developers.com/showthread.php?t=2069164
1) The lib files should not be modified like the posts for the SamSung based ROMs. However, you will need the modified Google Wallet .apk that is included in the zip you can download from their threads. I used the attached file that I downloaded from this thread - http://forum.xda-developers.com/showthread.php?t=2037372&highlight=google+wallet
2) I already had NFC enabled so ensure it is on in settings if you haven't already.
3) You need to modify /system/build.prop. I used Root Explorer (remember to change to RW) and you have to modify three lines. I made a copy of the existing build.prop before editing because you will revert to the existing file once complete to match your actual device.
3a) ro.product.model=Galaxy Nexus
3b) ro.product.name=yakju
3c) ro.product.device=maguro
4) I then rebooted before installing Google Wallet from the Play store. I then opened the app and performed the setup. The other guides mention getting FCs on NFC and to continue on but I never had any and the setup completed. YMMV.
5) Once the setup is complete with the version of the app from the store, you need to replace the app with the modified version that you downloaded in step 1. I used TB to force stop the app before I deleted it from /data/app.
6) I then use Root Explorer again to place the attached apk in /system/app (remember RW). I checked permissions and removed the group write check but again am not certain if that was necessary.
7) I then changed the build.prop.bak file to build.prop so it is back to before you started.
8) Reboot and hopefully it will work.
Hopefully, this helps and is clear.
Note: I see a prompt in the app shown in the attached pic but it will still work. It is really just a warning about a rooted device.
I pretty much did this, and it didn't work until I fixed permissions on the modded file that I moved to system/apps at the last step, like I saw in the YouTube video
Sent from my SGH-I317 using xda premium
capite said:
I pretty much did this, and it didn't work until I fixed permissions on the modded file that I moved to system/apps at the last step, like I saw in the YouTube video
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
So, I assume you removed the group write permission like I mentioned in step 6 and that fixed it for you? I assume it is the same video referenced in the link I have in step 1. The person checked permissions and removed that one check but he didn't say you had to. I did it anyway and maybe that is why it worked for me the first time that I followed the instructions I listed - from ManelScout4Life.
Thanks for this!
Sent from my Samsung Galaxy Note II
Yes
Sent from my SGH-I317 using xda premium
So, I assume you removed the group write permission like I mentioned in step 6 and that fixed it for you? I assume it is the same video referenced in the link I have in step 1. The person checked permissions and removed that one check but he didn't say you had to. I did it anyway and maybe that is why it worked for me the first time that I followed the instructions I listed - from ManelScout4Life.
told me to reset the app...and its hanging at 98%...thoughts?
If you reboot and check the "about device", does it show Galaxy Nexus before you even download the app?
Have you double checked the spelling on the other two lines?
What ROM and version are you on?
Sent from my SAMSUNG-SGH-I317 using xda premium
All I did was change name, model and device in build prop let me download and install and runs flawless no need for modified app
Sent from my Galaxy Nexus using xda premium
crisis187 said:
All I did was change name, model and device in build prop let me download and install and runs flawless no need for modified app
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I assume the reason for the modified app is for it to continue working after you change the build.prop back to an unsupported device. I guess on AOSP ROMs where S-pen apps don't work, then the proper build.prop isn't as important. You will lose access to external sd card possibly and other issues possibly.
Sent from my SAMSUNG-SGH-I317 using xda premium
I switched back the info seems to work still haven't fully tested yet
**EDIT
After installing multi window support to jelly bear ROM wallet force closes when trying to add account
Sent from my SGH-I317 using xda premium
How about if you complete the instructions above - adding the modded app, changing permissions, deleting the downloaded app, etc?
Sent from my SAMSUNG-SGH-I317 using xda premium
RichMD said:
If you reboot and check the "about device", does it show Galaxy Nexus before you even download the app?
Have you double checked the spelling on the other two lines?
What ROM and version are you on?
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
sorry for the delay...yes everything was spelled correctly, said Galaxy Nexus etc etc...I'm running CM10 by madmack...with it hanging i forced out, deleted pushed modded apk fixed perm and rebooted...opened the app and it hung on "setting up google wallet" for a good 15min...so i forced out and left it at that.
MonsterBandit said:
sorry for the delay...yes everything was spelled correctly, said Galaxy Nexus etc etc...I'm running CM10 by madmack...with it hanging i forced out, deleted pushed modded apk fixed perm and rebooted...opened the app and it hung on "setting up google wallet" for a good 15min...so i forced out and left it at that.
Click to expand...
Click to collapse
With the Galaxy Nexus build.Prop and Google wallet downloaded from the store, the setup needs to complete before you move to the next steps of reverting the build.prop and pushing the modded app. Those steps are to keep the app working without having issues due to a Galaxy Nexus build.prop. I would delete the app, and start over. I assume you never got an email stating you activated wallet.
Sent from my SAMSUNG-SGH-I317 using xda premium
Also, did you ever use the steps/zip posted by dafoxs or the other thread (forgot the name)? If so, your NFC setting might be gone or you have incompatible lib files, etc. I would revert to the nandroid backup if you made one before following those procedures which are for Samsung based ROMs rather than AOSP/CM10
Sent from my SAMSUNG-SGH-I317 using xda premium
crisis187 said:
I switched back the info seems to work still haven't fully tested yet
**EDIT
After installing multi window support to jelly bear ROM wallet force closes when trying to add account
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Wait. You installed multi window support on jelly beer!?
ManelScout4Life said:
Wait. You installed multi window support on jelly beer!?
Click to expand...
Click to collapse
LOL!
Modified build.prop and now my phone won't turn on. Any help?
---------- Post added at 02:37 PM ---------- Previous post was at 02:30 PM ----------
Took out battery, replaced it. Boot to recovery and restored Nandroid. Not sure what went wrong but I think I'll give up hopes of Google Wallet. Made me a little skiddish now.
This method of getting Google Wallet appears to break both Google Now and video output on cm10.1 variants that are running the open source audio hal.
Google Now goes into the 'Didn't catch that, retry?' Loop.
Steps to reproduce:
Install cm10.1 later than 01/26/2013
Allow it to boot and stabilize.
Setup Google Now.
Modify build.props to reflect Galaxy Nexus, yakju, maguro as dictated in OP.
Reboot.
Google Now will now have the 'Didn't catch that' error if you attempt voice recognition.
Sent from my "berry", spelling may vary.
bofhemeritus said:
This method of getting Google Wallet appears to break both Google Now and video output on cm10.1 variants that are running the open source audio hal.
Google Now goes into the 'Didn't catch that, retry?' Loop.
Steps to reproduce:
Install cm10.1 later than 01/26/2013
Allow it to boot and stabilize.
Setup Google Now.
Modify build.props to reflect Galaxy Nexus, yakju, maguro as dictated in OP.
Reboot.
Google Now will now have the 'Didn't catch that' error if you attempt voice recognition.
Sent from my "berry", spelling may vary.
Click to expand...
Click to collapse
Thanks,
I can't confirm this works on 10.1 (Android 4.2.x) - only confirmed on 4.1.x even though I expect Google Now, etc will be fine after reverting your build.prop. I'm "assuming" Google Wallet will work as indicated in these steps but Google Now, etc may have problems while the bulld.prop stilll indicates the wrong device - temporary until your wallet is working.
However, were you able to get Google Wallet to setup properly?
If you did get it working, did you try changing the build.prop back to original? I don't know if that would solve the Google Now but your steps listed don't indicate that you finished reverting the build.prop.
Please reply with your results for others.
Hello -
I did actually revert the build.props file to the original settings, and Google Now continued to give the same error. I'm about to test it without opening Google now until after the revert and reboot.
Thanks for your help!
If you like my work, donate to the Juvenile Diabetes Research Fund.

Google Wallet thinks I'm the Devil

I have been working on this Google Wallet thing with no luck.......maybe I am just retarded.
I gave in an rooted my phone. I have SuperSU, ROM Toolbox Lite, Root Browser Lite, and Root Explorer installed.
Ok, so it started as unsupported.....rooted and that fixed that problem. Now, it just goes to add account. I select my email address, then it goes to an error "insufficient secure element privileges for this system image (release-keys).
I the rooted ROM. I changed the build.prop to Galaxy Nexus thing.....and I download a new APK com.google.android.apps.walletnfcrel.magn2o.1.5-r75-v6.apk and copied that to the system/apps folder.......still no luck......what am I doing wrong? Does Google just hate me? I just don't get this....can someone please suggest my best opinion......I have dug through all the posts and tried 100 different things and can't figure this out.
PLEASE HELP....
ericu571 said:
I have been working on this Google Wallet thing with no luck.......maybe I am just retarded.
I gave in an rooted my phone. I have SuperSU, ROM Toolbox Lite, Root Browser Lite, and Root Explorer installed.
Ok, so it started as unsupported.....rooted and that fixed that problem. Now, it just goes to add account. I select my email address, then it goes to an error "insufficient secure element privileges for this system image (release-keys).
I the rooted ROM. I changed the build.prop to Galaxy Nexus thing.....and I download a new APK com.google.android.apps.walletnfcrel.magn2o.1.5-r75-v6.apk and copied that to the system/apps folder.......still no luck......what am I doing wrong? Does Google just hate me? I just don't get this....can someone please suggest my best opinion......I have dug through all the posts and tried 100 different things and can't figure this out.
PLEASE HELP....
Click to expand...
Click to collapse
You missing one step:
4-boot to recovery and flash SGS3-TW-US_variants-lib&nfc-fix.zip for ics touchwiz roms or SGS3-TW-US_variants-lib_nfc-fix-jellybean_4.1-1.zip for jellybean touchwiz roms and then wallet version com.google.android.apps.walletnfcrel.modaco.1.5-r87-v15.zip
(for CM9/10, I9300, aokp, aosp roms just flash the wallet zip)
Orginal Post is here
norbarb said:
You missing one step:
4-boot to recovery and flash SGS3-TW-US_variants-lib&nfc-fix.zip for ics touchwiz roms or SGS3-TW-US_variants-lib_nfc-fix-jellybean_4.1-1.zip for jellybean touchwiz roms and then wallet version com.google.android.apps.walletnfcrel.modaco.1.5-r87-v15.zip
(for CM9/10, I9300, aokp, aosp roms just flash the wallet zip)
Orginal Post is here
Click to expand...
Click to collapse
What does that mean "Flash"......how do I do that?
Not a tech person.........psychologist
ericu571 said:
What does that mean "Flash"......how do I do that?
Not a tech person.........psychologist
Click to expand...
Click to collapse
You need to install custom recovery via Rom Manager from play store.
Here is great guide , READ READ READ
Here is video how to flash rom on Galxy S3. This is way how to flash anything else.
Here is another exelent guide
Ok, so I did everything I had to do......I got to the point of adding the card.....I added my card.
When I go online I see the Galaxy Nexus showing on my Google Wallet account.
I then went to steps 9 and 10 and I returned my settings to the old Galaxy S3 ATT settings....now my Google Wallet is saying unsupported device.
ericu571 said:
Ok, so I did everything I had to do......I got to the point of adding the card.....I added my card.
When I go online I see the Galaxy Nexus showing on my Google Wallet account.
I then went to steps 9 and 10 and I returned my settings to the old Galaxy S3 ATT settings....now my Google Wallet is saying unsupported device.
Click to expand...
Click to collapse
Google Wallet is supposed to say unsupported device if your device is unsupported. This is unavoidable. You can still use Google Wallet just fine, though.
No, I mean I cant even open the app because it has a popup that say unsupported on your device and network, I click ok, and it kicks me out.......as if I never rooted my phone and installed.
I went back to the Galaxy Nexus build.prop and it works fine when I leave that alone. But the minute I change it back to the original build.prop.....it starts the unsupported thing again and not able to open app.
ericu571 said:
I have been working on this Google Wallet thing with no luck.......maybe I am just retarded.
I gave in an rooted my phone. I have SuperSU, ROM Toolbox Lite, Root Browser Lite, and Root Explorer installed.
Ok, so it started as unsupported.....rooted and that fixed that problem. Now, it just goes to add account. I select my email address, then it goes to an error "insufficient secure element privileges for this system image (release-keys).
I the rooted ROM. I changed the build.prop to Galaxy Nexus thing.....and I download a new APK com.google.android.apps.walletnfcrel.magn2o.1.5-r75-v6.apk and copied that to the system/apps folder.......still no luck......what am I doing wrong? Does Google just hate me? I just don't get this....can someone please suggest my best opinion......I have dug through all the posts and tried 100 different things and can't figure this out.
PLEASE HELP....
Click to expand...
Click to collapse
ericu571 said:
What does that mean "Flash"......how do I do that?
Not a tech person.........psychologist
Click to expand...
Click to collapse
How does your phone make you feel when it does this?....
WickR1 said:
How does your phone make you feel when it does this?....
Click to expand...
Click to collapse
it makes me feel like taking some Xanax......lol......not funny.....lol
ericu571 said:
Ok, so I did everything I had to do......I got to the point of adding the card.....I added my card.
When I go online I see the Galaxy Nexus showing on my Google Wallet account.
I then went to steps 9 and 10 and I returned my settings to the old Galaxy S3 ATT settings....now my Google Wallet is saying unsupported device.
Click to expand...
Click to collapse
Samsung Galaxy S3 on ATT is not supporting Google wallet. That why we using diffrend one by changing build.prop to make wallet work.
Do not restore you nandroid after your wallet is working just restore your build.prop
In my google Wallet account my phone is showing as Nexus too but wallet is working.
I left wallet open, then restored my build.prop. everything has worked great. I dont even have the unsupported device notice
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
WickR1 said:
How does your phone make you feel when it does this?....
Click to expand...
Click to collapse
Lmao....
Galaxy S III I747
norbarb said:
Samsung Galaxy S3 on ATT is not supporting Google wallet. That why we using diffrend one by changing build.prop to make wallet work.
Do not restore you nandroid after your wallet is working just restore your build.prop
In my google Wallet account my phone is showing as Nexus too but wallet is working.
Click to expand...
Click to collapse
That is the issue...all I did was go back into build.prop and changed the values back. I don't believe I even made a nandroid. Actually I am not even really sure what a nandroid is.
ericu571 said:
That is the issue...all I did was go back into build.prop and changed the values back. I don't believe I even made a nandroid. Actually I am not even really sure what a nandroid is.
Click to expand...
Click to collapse
How did you install your Google Wallet? Did you follow instruction in post i give it to you or did you install Google Wallet from Play Store?

Cyanogenmod help

I've looked through the forums for hours now and according to the noob video made by xda. I'm asking for help. I have an at&t Samsung galaxy s3 with the CyanogenMod installed (as the title implies) and to be honest its not worth the hastle. I'm having problems left and right. First off, the camera app that comes with the phone is missing. Or if theres a custom one. Its not included. I'm aware that I can find and install an external apk but I'll get to the problem with that in a bit. I followed very detailed instructions on installing the cyanogenmod and gapps and everything was fine (stable version) but the notifications suggested I update the mod so I did. Now I have the camera but my play store will not work. It opens for a split second then closes. Also, the file manager is gone. So I downloaded multiple file managers and it seems after first use that they can no longer open anything. I can't even access the files. I checked the superuser allowed and disallowed apps and everything seems fine. Now with the apk problem. Almost any apk I download will not install on my phone. Sorry for the erratic problems just jumbled everywhere in this post but I'm using my phone to write this so its a bit difficult to organize. Any feedback would greatly be appreciated. A link to a post already like this (which I couldn't find) or a link to a tutorial maybe or troubleshooting these problems. I will delete this post as soon as I find a solution so I don't use up space on the forums with a somewhat personal problem. Thanks in advance!
Using AT&T SAMSUNG Galaxy S3-SGH-I747
GoLordNibbler said:
I've looked through the forums for hours now and according to the noob video made by xda. I'm asking for help. I have an at&t Samsung galaxy s3 with the CyanogenMod installed (as the title implies) and to be honest its not worth the hastle. I'm having problems left and right. First off, the camera app that comes with the phone is missing. Or if theres a custom one. Its not included. I'm aware that I can find and install an external apk but I'll get to the problem with that in a bit. I followed very detailed instructions on installing the cyanogenmod and gapps and everything was fine (stable version) but the notifications suggested I update the mod so I did. Now I have the camera but my play store will not work. It opens for a split second then closes. Also, the file manager is gone. So I downloaded multiple file managers and it seems after first use that they can no longer open anything. I can't even access the files. I checked the superuser allowed and disallowed apps and everything seems fine. Now with the apk problem. Almost any apk I download will not install on my phone. Sorry for the erratic problems just jumbled everywhere in this post but I'm using my phone to write this so its a bit difficult to organize. Any feedback would greatly be appreciated. A link to a post already like this (which I couldn't find) or a link to a tutorial maybe or troubleshooting these problems. I will delete this post as soon as I find a solution so I don't use up space on the forums with a somewhat personal problem. Thanks in advance!
Using AT&T SAMSUNG Galaxy S3-SGH-I747
Click to expand...
Click to collapse
Go in application settings and delete your play store's data/cache. That should fix it.
Without it, it's kinda hard to install apps unless you sideload. If you do sideload, you need to allow it in your settings (security I believe).
if you're using the stable version of CM
you might have to go to Date & Time setting
and fix the date on there in order to make play store works
and everything you say about camera, it is weird indeed because not only CM, every rom out there should include a camera app
if that problem still exists for you, you might want to clean/wipe everything, from cache to system and then flash the rom again
Thank you guys. I tried wiping the cache and it still didn't work. I don't mind side loading which is what I've been doing but its not ideal. I can only search for the exact app(s) I want rather than exploring via play store. Also, you guys didn't mention the problem with the file managers not working after first try. If you have any feedback it'd be great. I would like to keep the cyanogenmod but its just not worth the time and effort (opinion). If I can't fix the problem or find a solution I'll just go back to my phones stock UI because even though I think flashing ROMs is awesome. It really isn't worth frustrating myself with something that's an option and not a necessity. Thanks in advance for feedback.
Sent from my SAMSUNG-SGH-I747
Have you tried a factory reset?
GoLordNibbler said:
Thank you guys. I tried wiping the cache and it still didn't work. I don't mind side loading which is what I've been doing but its not ideal. I can only search for the exact app(s) I want rather than exploring via play store. Also, you guys didn't mention the problem with the file managers not working after first try. If you have any feedback it'd be great. I would like to keep the cyanogenmod but its just not worth the time and effort (opinion). If I can't fix the problem or find a solution I'll just go back to my phones stock UI because even though I think flashing ROMs is awesome. It really isn't worth frustrating myself with something that's an option and not a necessity. Thanks in advance for feedback.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
the file manager part is really weird.
if you clean install, especially the stable version, everything should works just fine
however, it sounds like bad install though
how about this this
Download Titanium Backup and wipe data + cache for file manager only and see if it works
if not, try the longer way
download stock att rom(4.1.1)
go to recovery, wipe everything
go to download mode
flash stock rom with odin
restart to recovery, wipe dalvik and cache
root the phone
Re-Download CM10 stable
go to recovery, wipe everything, including System
flash cm10
reboot and see if everything works
Yeah I've tried a factory reset. It only deleted my user data not really resetting the phone. Thank you pcchano (sorry if I got name wrong) I'll try and erase everything and reinstall from scratch but its not my first time using custom ROMs so I'm sure I did it right but I'll give it a go. Also, someone told me that I need to completely wipe any data associated with Google wallet before I root or else play store will not work. Has anyone tried out this theory or know anything about it? It doesn't make sense to me seeing as wallet is saved server side beside the basic user data stored on the phone. But please let me know. You guys are all very helpful thanks for the feedback.
Sent from my SAMSUNG-SGH-I747
Also, I've never had to wipe dalvik before? Could that be my problem? I also noticed that when I updated cm the info panel said 'experimental' even though I chose the stable version to start with? Could some of these problems be associated with cm rather than blaming it on my phone? Thanks in advance for any feedback.
Sent from my SAMSUNG-SGH-I747
GoLordNibbler said:
Also, I've never had to wipe dalvik before? Could that be my problem? I also noticed that when I updated cm the info panel said 'experimental' even though I chose the stable version to start with? Could some of these problems be associated with cm rather than blaming it on my phone? Thanks in advance for any feedback.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
i have like 2 s3 using CM10 stable version and no problem with it (other than the play store wouldn't connect due to the date in setting wasn't correct) while I myself am using CM10.1 and other than the bugs that come with CM10.1 or google source code, it is a functional rom
so i would rather say, it is your phone
and you should always wipe dalvik cache along with cache partition before flashing new rom.
OK pcshano thanks very much. I'll just erase everything and start from scratch. Thanks everyone who helped me. This forum and you people are awesome. I'll delete this post as soon as I reinstall the ROM to make sure it worked. Thanks again!
Sent from my SAMSUNG-SGH-I747
The stable cm is of the 10 variety. The experimental builds are 10.1 if I'm not mistaken. In which case you should only need to flash the appropriate gapps package to get the play store functioning and camera as well. The file manager issue I don't know beyond the external sd card being a bit sketchy on 4.2 builds. Are you using an external sd card? Start with a fresh flash of 10.1 if you want to go with that, flash a 4.2 gapps zip and see what happens from there.
Sent from my SAMSUNG-SGH-I747 using xda premium

[ROM] [CM 10.2] Unofficial - 09-09_2045 [CM Accounts]

Hello all,
This is a straight up compile of Cyanogemod's source. Only thing added was CM Accounts. I have been contemplating whether or not to start this thread simply because I really don't have time to maintain a thread with work, school, and family but since I have not seen a working build posted yet (actually chenxialong has working builds for all jf devices), I decided to give mine. From what I have seen (I have been using as daily driver) CM 10.2 is pretty stable for our devices already.
I compile at least once a day, and usually twice so these builds will be my latest. If there are no significant changes upstream, I will not post a new build. I am really not a coder, although I have a little experience, so please don't ask me to fix things because I most likely won't know how to. Like I said, I am compiling directly from source.
My build names are time stamped as to when they were compiled, right down to the minute (PDT). The Gapps I post are the ones I used. I am not sure which thread I acquired them from, so I am truly sorry to the original poster. I tried many and most were bloated with uneeded apps so I chose this one. If they are yours, please let me know so I can give credit.
This thread will pretty much become obsolete once nightlies for 10.2 are available.
ROM is hosted on Google drive. Any mirrors are welcome.
Full wipe is needed if coming from any other non CM 10.2 ROM. If root is needed, go to Settings-->About Phone-->Tap Build Number seven times. Developer options are now available in settings. Under Developer Options-->Root Access select Apps and ADB.
There have been reports of issues with PhilZ recovery and CM builds. If you are using Philz and have issues, try a different recovery.
Credits:
Cyanogenmod https://github.com/CyanogenMod
TheMuppits (Vendor Files) https://github.com/TheMuppets
Changelog - http://10.2.cmxlog.com/?device=jfltetmo
Gapps - http://goo.im/gapps/gapps-jb-20130813-signed.zip
Gapps Mirror - https://docs.google.com/file/d/0B6vNNLDt_uoWMlZKSEV3MFl5RUU/edit?usp=sharing
ROM
09-09_2045 - https://docs.google.com/file/d/0B6vNNLDt_uoWT0ViMUdEZWN4ajg/edit?usp=sharing
Old Builds
09-08_1931 - https://docs.google.com/file/d/0B6vNNLDt_uoWckNOUHhEYTA4ZUU/edit?usp=sharing
09-08_0813 - https://docs.google.com/file/d/0B6vNNLDt_uoWSldmTGhiTDFxQWM/edit?usp=sharing
chea buddy
mrvirginia said:
chea buddy
Click to expand...
Click to collapse
Thanks man!
Awesome. Thanks for this.
Seems like root isn't working. When I try to use titanium backup, it says it cant acquire root.
hitman818 said:
Seems like root isn't working. When I try to use titanium backup, it says it cant acquire root.
Click to expand...
Click to collapse
Just added to the OP as far as how to get root.
Gonna give this a try soon. Thanks!
Also when I try to restore my apps from tb, it says theres a problem parsing the package.
hitman818 said:
Also when I try to restore my apps from tb, it says theres a problem parsing the package.
Click to expand...
Click to collapse
I'm sorry for your tribulations, yeah I said tribulations, but I don't really know what the problem might be. I do know that, in 4.3 there is a change that is being implemented as far as how the system handles root and apps that require it. I backed up my apps using the save to a flashable zip option in Titanium. I would imagine that is is still an option even though you are already booted into CM. You can try that. I am also considering using Helium for backups since it will not require root in the fashion Titanium does.
hitman818 said:
Also when I try to restore my apps from tb, it says theres a problem parsing the package.
Click to expand...
Click to collapse
In t.b. preferences change the storage location to legacy
SeNt FRoM thE 4th GalaXy of the AnDroid uNiVerSeā„¢
jaestreetss said:
In t.b. preferences change the storage location to legacy
SeNt FRoM thE 4th GalaXy of the AnDroid uNiVerSeā„¢
Click to expand...
Click to collapse
I cant find where that setting is. I pressed menu, then went into preferences and I cant find it.
hitman818 said:
Seems like root isn't working. When I try to use titanium backup, it says it cant acquire root.
Click to expand...
Click to collapse
I use titanium backup and it didn't work on google edition 4.3 so i use helium app to backup and restore for android 4.3
Sym_Link said:
I'm sorry for your tribulations, yeah I said tribulations, but I don't really know what the problem might be. I do know that, in 4.3 there is a change that is being implemented as far as how the system handles root and apps that require it. I backed up my apps using the save to a flashable zip option in Titanium. I would imagine that is is still an option even though you are already booted into CM. You can try that. I am also considering using Helium for backups since it will not require root in the fashion Titanium does.
Click to expand...
Click to collapse
one of my teammates reported that there's still titanium issues with CM 10.2 even after titanium was updated for 4.3
Hey Sym! Good to see you went public with these! You are doing a service to the community! Many thanks!
When I was on Virginia 4.3 ROM I had no problems restoring apps and data with titanium. I keep my backup location always on my external card. Hope this helps.....
After installation no boot, black screen.
boterkaaseneieren said:
After installation no boot, black screen.
Click to expand...
Click to collapse
Maybe a bad download? It booted fine here.
New build in OP
Downloading now, camera ok? First build was no boot animation so I thought it was not booting lol
boterkaaseneieren said:
Downloading now, camera ok? First build was no boot animation so I thought it was not booting lol
Click to expand...
Click to collapse
Yeah, camera is fine. In fact it has the new CM Focal camera as well.
Sym_Link said:
Yeah, camera is fine. In fact it has the new CM Focal camera as well.
Click to expand...
Click to collapse
Just flashed it, broken camera and no apn settings. Flashed all today's builds also at fltexx and same problem.

google wallet roll out

nfc still only available for sprint and us cellular. at least we finally got the app.
Edited...
If youre running the hacked method to get it to work (Tmobile users)then do not update the app.
I just finished installing the new Wallet app. This isnt directly downloaded from the PlayStore. Im testing a .zip from a developer.
The new Setup is kinda wierd and im not sure if tap and pay is the same as before or if I have to choose a default card for it to work. Will report results after I make a successful transaction.
Im sure the developet will create a thread when bugs are fixed.
Please merge.
Double0EK said:
I just finished installing the new Wallet app. This isnt directly downloaded from the PlayStore. Im testing a .zip from a developer.
The new Setup is kinda wierd and im not sure if tap and pay is the same as before or if I have to choose a default card for it to work. Will report results after I make a successful transaction.
Im sure the developet will create a thread when bugs are fixed.
Click to expand...
Click to collapse
thanks for guinea-pigging this for us. I hope the new .zip version works well. I'd really like to run the most current version and have the added functionality. at present, I have the old nfc enabled version on my note 2 and the current, but non nfc enabled version on my tablet and old phone. It would be nice to be able to run the current version with NFC.
shizenyasuya said:
thanks for guinea-pigging this for us. I hope the new .zip version works well. I'd really like to run the most current version and have the added functionality. at present, I have the old nfc enabled version on my note 2 and the current, but non nfc enabled version on my tablet and old phone. It would be nice to be able to run the current version with NFC.
Click to expand...
Click to collapse
Heres what happened. I tried to make a purchase earlier this morning at 7-11 and it didnt work. From what the developer and I briefly discussed is that the modified NFC files might be the culprit. What I suggest that you can do is restore the factory NFC files and install the Wallet app directly from the PlayStore and test that way.
I dont have a copy of my factory NFC files anymore and dont want to odin back so im just waiting. As of right now im using the previous Wallet app.
Double0EK said:
Heres what happened. I tried to make a purchase earlier this morning at 7-11 and it didnt work. From what the developer and I briefly discussed is that the modified NFC files might be the culprit. What I suggest that you can do is restore the factory NFC files and install the Wallet app directly from the PlayStore and test that way.
I dont have a copy of my factory NFC files anymore and dont want to odin back so im just waiting. As of right now im using the previous Wallet app.
Click to expand...
Click to collapse
I installed the new app on my note 2 after updating the rom so i didn't have the cracked version anymore (yes i reset google wallet app first) With the updated app loaded, i looked through settings and it said tap to pay wasn't available, so after configuring the rest of my new rom (jedi master 17) I reinstalled the cracked version and (i havent tried it yet, but it loos the same as ever) nfc tap to pay should work again, just still on that oudated GW app. Fingers crossed one of the brainiacs at modaco will release an updated cracked version.
Go to the Note2 Themes & Apps Section. There is a new flashable .zip .
Few things you should do first.
1. Turn Off NFC & S-Beam.
2. Clear Google Wallet Data and Cache
3. Flash the New .zip
4. Check to see if Tap and Pay is active.
Double0EK said:
Go to the Note2 Themes & Apps Section. There is a new flashable .zip .
Few things you should do first.
1. Turn Off NFC & S-Beam.
2. Clear Google Wallet Data and Cache
3. Flash the New .zip
4. Check to see if Tap and Pay is active.
Click to expand...
Click to collapse
IT work just fine:good: but if you're a heavy S-pen user like me then i say don't install as you will lose S-pen functionality. Because your Note-2 will show as the (Nexus)
thugmafia said:
IT work just fine:good: but if you're a heavy S-pen user like me then i say don't install as you will lose S-pen functionality. Because your Note-2 will show as the (Nexus)
Click to expand...
Click to collapse
Thats only in the app. My build.prop and About Phone shows the proper name. And my S-Pen functions fine.
Double0EK said:
Thats only in the app. My build.prop and About Phone shows the proper name. And my S-Pen functions fine.
Click to expand...
Click to collapse
same here no issues with S-Pen or anything else....
got tap & play to show it's working using the new zip on stock rom- just been leery of trying it out yet...

Categories

Resources