Everytime I reboot my phone and it boots up, this notification appears saying cant find your location. It goes away in about 2-3 seconds. I have checked my location settings and eveything is on except for location history. I don't know what is causing this. Also, I have noticed around this same that this started that there are times when I phone lags quite a bit, it doesn't do it all the time and it seems to happen randomly. I don't know if these two issues are related or not. If anyone has any suggestions it would be greatly appreciated. Thanks
Anyone have any suggestions?
Well what rom are you on? Have you made any changes to the build.prop? have you modified your gps.config file? These are all thing that can cause this and here are some fixes:
*New rom (cm 12 works nice)
*Go and do a 100% unroot and factory reset (Here's the link: http://forum.xda-developers.com/showthread.php?t=2785089 -Not my fault if your device(s) break).
*You could go and redownload the rom you are on then do this:
1) Extract the .zip file
2) Locate the gps.config (Name my be different)
3) Place it in the right spot/fix premissons
4) Work?
5) Don't blame me if something happens make a backup!
1619415 said:
Well what rom are you on? Have you made any changes to the build.prop? have you modified your gps.config file? These are all thing that can cause this and here are some fixes:
*New rom (cm 12 works nice)
*Go and do a 100% unroot and factory reset (Here's the link: http://forum.xda-developers.com/showthread.php?t=2785089 -Not my fault if your device(s) break).
*You could go and redownload the rom you are on then do this:
1) Extract the .zip file
2) Locate the gps.config (Name my be different)
3) Place it in the right spot/fix premissons
4) Work?
5) Don't blame me if something happens make a backup!
Click to expand...
Click to collapse
I am on the bar rin rom. I have not made any changes to the buildprop.
I'm on BarRin, and haven't noticed any GPS problems.
Try going into the application manager and clearing cache for LocationServices. It won't hurt to go into TWRP and clear cache and Dalvik cache, either (It's under Wipe, Advanced). No guarantees, but it could help.
Related
Speaking about this thread: http://forum.xda-developers.com/showthread.php?t=752007
More information about it here: http://www.xda-developers.com/android/patched-gallery3d-for-higher-resolution/
Since this app is included in the Samsumg rom, we would have to flash it. Anyone willing to be the guinea pig and see if it works (and is worth it) ?
Guinea pig here. Does nothing but a FC loop.
- oh well, thanks for trying at least !
Flashing doesn't work on I9000 either, but the .apk works. You just have to uninstall the existing gallery3d with root explorer, and then reboot, go to settings-manage applications and unintall the leftovers of the gallery. Then install the .apk with astro or similar.
I only did he update. I am going to try the longer way in a bit to test.
Sent from my SGH-T959 using XDA App
So, I was able to get the updated Gallery3dm.apk loaded onto my Vibrant. Using AndroidMate, I copied the original \system\app\gallery3d.apk to my SDcard (as a backup), then deleted the \system\app\gallery3d.apk from my system + the corresponding ODEX file. Reboot. Next, I copied the Gallery3dm.apk (updated version) from my SDcard to \system\app, selected it, and chose Install. Worked fine.
My thoughts? It does have a higher quality when you zoom in, but it seems to have some drawbacks too -- like VERY low-res versions of the files upon first load (and after, it seems), some display strangness (graphic tearing), and the occasional lag. Most of all, the difference is not THAT noticeable. You can check out the *before* and *after* attachments I've uploaded.
I'll be going back to the original Gallery3D.apk for now, but I sincerely hope that Samsung (or whoever) can figure out how to allow for crisp zooming in.
Thanks,
Yip
Were you able to switch back to the old gallery?
(On i9000):
I've tried putting my backup copy of Gallery3D.apk (and odex) into /system/app but it doesn't do anything (doesn't appear in apps menu etc).
If I click on the Gallery3D.apk to try install it, it asks if I want to replace existing system application (yes) but ends up with "Application not installed".
It seems I'll have to stick to the Gallery3Dm till my next FW flash.
Edit:
Oh nvm, seems a reboot did the trick
JimiJam said:
Were you able to switch back to the old gallery?
(On i9000):
I've tried putting my backup copy of Gallery3D.apk (and odex) into /system/app but it doesn't do anything (doesn't appear in apps menu etc).
If I click on the Gallery3D.apk to try install it, it asks if I want to replace existing system application (yes) but ends up with "Application not installed".
It seems I'll have to stick to the Gallery3Dm till my next FW flash.
Edit:
Oh nvm, seems a reboot did the trick
Click to expand...
Click to collapse
Wow! The reboot did it for you, eh? Trust me... I rebooted *several* times, but no luck. Finally had to restore from backup. Oh, well...
This is a more detailed edited version of how to install the Resurrection ROM by westcrip...
as have seen too many users that seem to be skipping parts or confused of the installation.
This is also for users like myself, who just started on this site and can't post on Development side to find their answers.
BACKUP your apps of course...but DO NOT backup system data.Repeat!! DO NOT BACKUP SYSTEM DATA. Restoring system data can give you some problems because if you don't know what you're doing, can accidentally replace something from the fixes that screws things up!
-----------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------------------------
PART-1
Rom Installation (you MUST follow these steps! )
**Go to recovery mode( Vol UP + Power+ Home and hold until the Samsung Galaxy screen comes on)
1- Wipe data / Factory reset then (can Wipe cache partition or go straight to)
Install ResurrectionV1.1_official_remix_ics_4.0.3_XXLPE_FULL-WiPE.zip
*if you did not Wipe cache, can go straight to install from cache...
but if you Wiped cache then you go to install from external SD card and install 1.0_CWM.zip (this will be touch version)...
then choose - install zip from sdcard. - choose zip from sdcard. Scroll down to Download folder and select ResurrectionV1.1_official_remix_ics_4.0.3_XXLPE_FULL-WiPE.zip.
Please wait a moment.
2-Install gapps_for_remix_v1.1.zip
3-Install gapps_fixer.zip then go back and go to Advanced.
4-Wipe dalvik cache (required)
and Fix permissions and go back to
5-Reboot system
(at this stage it may take a while for first bootup, because we have wiped cache. It needs to rebuild it, so don`t panic.
It may take a while *average around 3-5min before getting to Installing applications screen)
At this stage, boot to system and configure the phone (change language settings, etc).
When finished, again reboot into recovery and follow PART-2
PART-2 (required)
This part it's mandatory here are contained the language, theme, AOSP apps and the T9 dialer if you want it...
or use default. ONLY install one of these:
*note: you're in regular CWM using up and down volue + power button to enter.
If you want the touch - reinstall it like before.
1.- Install the SMSfixupdate-afterboot+T9 Dialler.zip
or
SMSfixupdate-afterboot+default remix dialler.zip
go back
2.- Reboot into system
After finishing the boot it's highly probably that you receive a force close from android phone.
It's normal and it's the only FC that you should get.
Enjoy!
**There is a RAM Manager Fix (When you open the Task Manager app, there's a section called RAM and a button to Clear Memory.
The fix enables that button again... for those not working).
Here is a mirror link for this and other files: RAM Manager Fix and others
PART-3 (optional)
*This can apply to many other files you want to flash.
If you want to install Siyah kernel:
Place Siyah-v3.0rc4-CWM.zip (or whichever version you're using) in the root of internal SDcard memory ("download" folder) and go to recovery mode (Vol Up + Power + Home).
Go to Install zip from SDCard... and select it.
Yes and install... Fix permissions... Reboot.
**battery issues with Siyah?
go to recovery
wipe dalvik
go to "kernel specific options" to reset them or other performance tweaks.
reset kernal
fix permission
reboot
**No more video player?
Get the VideoPlayer.apk file (*have to do a search for it now until I find another working link to it)
and copy it to system/app using something like Root Explorer
Reboot
Hope this helps. I'll edit this when I have time (usually busy with other projects).
*Version 1.2 is out now Check it here.
Good job
Tho make sure you spend a bit of time regularly checking the thread (depending on how much action the thread gets, obviously). Once you make threads like these people invariably ask questions & it's best if the person who detailed the method answers most of them.
Thank you sir.
I will give as much time as I can on this, when questions come up... and I'll be sure to keep up with bugs going on on original thread... though they will be updating this ROM soon to 4.0.4.
When that happens, guess will have to update this lol.
(oh no, what have I gotten myself into )
Language problem
Hello!
Thanks for the thread, really useful for noobs needing help to fix some problems.
I am a noob... and I have a problem.
Everything is working fine, battery is ok, no fc... but language seems to be messed up, I get my language (spanish) in almost all settings and menus, but dialer is invariably in english. Some contacts dialogs show this behaviour too.
Thank you very much in advance!
Thanx a lot, really useful...cant wait for 1.2
SMSafter-reboot is the only fix i needed to fix my dialer fcs issue, after a dalvik cache clean and permission fixing. That was the only way, if some1 has same issue.
Sent from my GT-I9100 using XDA
Hi Miguel. The ROM is mostly for English and some language settings are off here and there. Mine too shows Chinese characters in some parts. I think this has to do with where the phone is originally from.
Version 1.2 will be out soon (based on 4.0.4) and should have more bugs fixed. I will see if there's anything can be done to help you with Spanish settings.
*glad it's helpful for you guys.
Thanks for a good simple guide.... it is getting pretty difficult to find answers with so many posts in the main thread.
Will you be making a similar step by step guide for ver 1.2 that should be out soon?
If it is needed I will. Will have to wait for it to come out and see if instructions changed. The process will be easier (after what westcrip said), not needing to add gapps fix, etc now I think.
Anyways, if I think needs more detail for newer users, I'll add a new thread for it and post a link here to it too.
Which dialler
I'm a true noob and I'm rooted with CWM installed and I'm giving serious consideration to this rom. My only question at this point is what are the differences btw the 2 diallers and do most folks prefer one over the other?
Hi tlmacson. It's a very good fast and smooth rom with good support. 1 dialer gives you T9 abilities... which means when you start dialing some number, it shows you contact(s) that much those numbers.
But there are some bugs in it not working for some, so recommended to install the default one and add some other app that does the same, or install T9 on after the default.
PS
If you want to give this ROM a try... the new 1.2 version will be out any moment which should have easier installation with hopefully less bugs ^^
I have been using it for a few weeks now. It has run really smooth, the only bugs are very small and do not effect the use of it daily.
I had a few problems with the dialler, so I installed exDialler. I actually prefer it, it has t9 searching and can be skinned to look like ics dialler.
I will definatly give ver 1.2 of the rom a try too.
Yes, that's the 3rd party app people like for T9 use: exDialer
It also allows you to give it black theme.
HELP!
Cyber i'm wondering if you did test the 1.2 PRO resurrection I want to upgrade to it but i don't know if it is a FULL WIPE or not because westscript didn't mention it also there are no GAPPS and FIXER within the thread can you please confirm for me this?
I think that I may just do that since I'm not having any real issues with the leaked "stock" XXLPQ. I appreciate your advice and dialer explanation.
nHorus - For v1.2 it works better if you do a full wipe Do a full wipe(factory reset+cache+dalvik cache), though you can try without it.. and just do the factory reset. Then install ROM and Siyah kernel and reboot to do initial setup. Then comeback to recovery mode and install navigation button fix and app themes, reboot.
Test
Thank you cyberboob.
I will try 1.2 and see how it goes, anyway I will install exDialer to fix my languages "problems" (it is not a dealbreaker but is disturbing seeing some dalogues in other language).
According to 1.2 changelog this version is promising.
cyberboob said:
nHorus - For v1.2 it works better if you do a full wipe Do a full wipe(factory reset+cache+dalvik cache), though you can try without it.. and just do the factory reset. Then install ROM and Siyah kernel and reboot to do initial setup. Then comeback to recovery mode and install navigation button fix and app themes, reboot.
Click to expand...
Click to collapse
thank you. i'll try without the wipes
Sorry.. a full wipe is needed again (or more bugs will be present).
Follow these steps:
Do a full wipe(factory reset+cache+dalvik cache)
Install the Main ROM
Install Siyah-v3.0.1-CWM.zip
Reboot
Do the initial setup of things
Go back to CWM and install navigation button fix
Reboot
Then go back to CWM and install app themes (there are some bugs, but if you want the black themes, then install classic first, then black)
Reboot
Some people have other issues after, but see how this goes.
I would change the DPI settings to 184 or 210 for everything to work fine from market apps.
*Also westcrip will post a new fix update for some new bugs reported by some users.
cyberboob said:
nHorus - For v1.2 it works better if you do a full wipe Do a full wipe(factory reset+cache+dalvik cache), though you can try without it.. and just do the factory reset. Then install ROM and Siyah kernel and reboot to do initial setup. Then comeback to recovery mode and install navigation button fix and app themes, reboot.
Click to expand...
Click to collapse
I know I'm showing my "noobness" but I thought that the kernel was part of the ROM; so how do I install the kernel after the ROM?
Same way you installed the main ROM.. go into recovery mode and select the folder you placed it in (usually internal sd card "download" folder) and flash it "yes". Fix permissions if want and reboot. Same with anything else you need to flash/CWM after/before.
Hi all;
as someone already know, I made some ultra cleanings in my ROM (as in my signature). Used system try and see what happens mostly I have deleted some of apks on /system/app and rebooted if it could affect something that I need... Suceeded and my ROM got about 10MB of free RAM extra, so I was satisfied Also made a custom framework, modded the resources (not UOT etc.); just replaced some image files.
Hovewer, few days I found that my ringtone volume is too quiet. So I went into settings > volume and what? FC ! So I tried many other settings and also found that same is with brightness control.
Ï decided that I deleted something that is related with settings - looked into deleted apks in my backup and didnt found anything that yould be related with it... So finally copied back all of apks as are on default ROM from Wolfbreak and rebooted and fixed permissions. But, as I was surprised, FCs were still present ! So it was dissapointed very much and tried to reflash the whole ROM - FCs still present ! -> made Full wipe and reflashed another ROM and FCs still present althought FULL WIPE !!!
Finally, first totally dissapointed with Android behavior, restored the whole backup of ROM, which I made first. Happened two another amazing things:
- lost lockcreen (phone doesnt lock; after bootup lockcreen appears once...)
- lost items in shutdown menu - now I have only Shutdown and Reboot option...
- home button doesnt work (back and menu works), long or short click
So, I am asking for android experts What are these things related to files? I modded framework-res.apk and deleted and restored apks in /system/app. Nothing more...
So I need to point which apks or res are sources are related to this? I will check permissions or try to restore it. Or even where are stored data for responsible apks for these FCs...
Any ideas are surely welcome !!!
The lost option in the shutdown menu are frawework-res,related,and birghtness and volume are settings.apk
I suggest you to restore the framework and settings.apk,put them in your sd card,copy them to system,inside system give proper permissions,and after that mode them to its places,reboot in xrec,wipe cache,wipe dalvik cache,fix permissions,and then reboot.
kalel29 said:
The lost option in the shutdown menu are frawework-res,related,and birghtness and volume are settings.apk
I suggest you to restore the framework and settings.apk,put them in your sd card,copy them to system,inside system give proper permissions,and after that mode them to its places,reboot in xrec,wipe cache,wipe dalvik cache,fix permissions,and then reboot.
Click to expand...
Click to collapse
Yes, know this. Tried it already, but in other order.
Now tried in this orded you suggested and after reboot I lost also PIN unlock page (so phone is out of network) and battery icon shows not empty battery (charged it few hour ago).
It seems that also another files are related to these problems, but cant imagine what else - tried almost everything.
Its weird... I am flashing again stock ftf...
I had flashed RootBox, the most recent one, and I started getting Low Storage Space warnings after every reboot. I thought reflashing might solve this problem, so I did the following :
1. In recovery, Wipe Data/ Factory reset
2. Wipe Cache
3. Wipe Dalvik Cache
4. Format /system
5. then Flashed SlimBean 4.2.2 v1 Stable
Now, again I am getting the same problem, I haven't installed many apps though, the list of apps installed are:
1.Chrome
2.Download All Files
3.ES File Explorer
4.Titanium Backup
5.instagram
6.Maps
7.jetAudioPlus
8.MX Player
9.ROM Toolbox
10.Viber
11.WhatsApp
12.YMail
That's All...
I don't know what problem might be.. I have also searched a lot, in XDA as well as Google. but no suitable solution.
Anyone can help me solve this.??
guru_iyer said:
I had flashed RootBox, the most recent one, and I started getting Low Storage Space warnings after every reboot. I thought reflashing might solve this problem, so I did the following :
1. In recovery, Wipe Data/ Factory reset
2. Wipe Cache
3. Wipe Dalvik Cache
4. Format /system
5. then Flashed SlimBean 4.2.2 v1 Stable
Now, again I am getting the same problem, I haven't installed many apps though, the list of apps installed are:
1.Chrome
2.Download All Files
3.ES File Explorer
4.Titanium Backup
5.instagram
6.Maps
7.jetAudioPlus
8.MX Player
9.ROM Toolbox
10.Viber
11.WhatsApp
12.YMail
That's All...
I don't know what problem might be.. I have also searched a lot, in XDA as well as Google. but no suitable solution.
Anyone can help me solve this.??
Click to expand...
Click to collapse
Its viber thats causing your problem look here http://forum.xda-developers.com/showthread.php?t=2117444 under the letter S for storage. I found this answer in 15 seconds under the root box thread. Please look at rom threads for solutions before posting.
Viber Low Storage error when pressing "Hold to Talk"
gaosphappy said:
Its viber thats causing your problem look here http://forum.xda-developers.com/showthread.php?t=2117444 under the letter S for storage. I found this answer in 15 seconds under the root box thread. Please look at rom threads for solutions before posting.
Click to expand...
Click to collapse
None of the suggestions in this thread worked for me. Including the alternative thread you suggested.
Although my problem has very similar symptoms - the cause (and therefore the solution) is different.
Symptoms: Viber (version 4.1.1) gave me a "Low Storage Space" message whenever I pressed the "Hold and Talk" button.
My Solution: I discovered that there was a file called "_ptt_id_counter" in folder /data/data/com.viber.voip that had incorrect uid/gid.
The uid/gid were not the same as every other file and folder in this subtree.
I guess that "ptt" means "press to talk". I also guess that the id_counter (4 bytes in size) is probably a long integer and should be able to be
both written and read. The permissions were only 600 on the file. So, I used adb to chown the uid & gid to be the same as the other files/folders.
It then worked.
I am not an Android programmer. However, I have worked with Unix since 1982 and Linux since 1997.
I also tried booting into recovery and running permissions check/fix. But, I guess there isn't a manifest that specifies what the correct file permissions should be? (I haven't got that far in my OO learning).
I think the culprit that (somehow) caused the error was the Backup app I was using. (Ultimate Backup by Jrummy) but, I can't be sure and I don't want to "point the finger".
If someone could please tell me where in an APK one could locate a "spec"/"layout" of what files should have what permissions - it would be helpful. I know that uid/gid doesn't need to be specified generally because each app runs in it's own sandbox and the uid/gid is set to that of the owning pid. But, there must be something somewhere that specifies what the "chmod" permissions are. Isn't there?
If not - then I just have to assume it's a memory corruption and (perhaps) related to the CM11 Nightly that I am using. But, I am a Newbie and I am not permitted to post in that forum (yet).
-----------------------------------------------------------------
Phone: HTC Desire HD
Rom: Daily driver - unofficial CM11 by Mustaavalkosta.
Radio: 12.69a.60.29U_26.17.14.11_M
**I am not responsible for any damage you do to your phone. This as any other mod is done at your own risk. This is just a guidline on how to get a real fix for blocking mode on your VZW Jelly Bean device.**
This blocking mode fix has been confirmed on both the VZW Note 2 and the VZW Galaxy S3
*You need to be rooted.*
IF YOUR ON A NON-VZW BASED ROM:
JUST FOLLOW PART 3!! (and part 4 if you like!)
IF YOUR ON A VZW BASED ROM:
Part 1
There are two apks that are the reason for blocking mode not working. The two files are the secContacts.apk and the secPhone.apk. You will need download these two apks from a other carriers rom and replace them in the system/app folder in root explorer (or your choice system file explorer) and change the permissions.. (For example download a flashable "att" note 2 rom and copy the secContacts.apk and the secPhone.apk and paste them into your system/app folder. Restart then change the permissions then restart again. Same thing with the Galaxy s3 only you have to download files from another carrier galaxy s3 Rom. From this point on blocking mode will work 100 percent.
Part 2
Now that you have blocking mode working, how can you access it. You can get a shortcut maker app and have a blocking mode home screen icon... OR..You can have it in the settings menu like it's supposed to be! Now just like before there is an apk that VZW had changed to block this. It is the secSettings.apk. So from the same rom you downloaded from before copy the sec.Settings.apk from the other carrier Rom and paste it in your system/app folder in root explorer. At this point you may or may not get a chance to restart your phone (it might freeze for a sec and restart by itself. Once phone restarts change the permissions and restart again. **NOTE: Some roms settings mave have more or less options then the stock. To access these just also copy and paste the secSettingsProvider.apk and everything will work perfectly** **NOTE: menu appearance will not change yet!**
Part 3
Last step. Now that you have the new menu there are still two more files that are causing the menu to change. In root explorer navigate to /efs/imei and delete the map_code.dat and then go to /system/Csc and delete the sales_code.dat. Now restart your phone and you are good to go. **NOTE: after deleting these files any VZW apps on your phone or in market will not be recognized on your phone. For example if you try to download a VZW app from the market it will say your device is not recognized. But they have 'market unlocker' apps that can trick the market to see you as any carrier you want. Also VZW Apps like backup assistant might not work properly.
Part 4
This is not really related to blocking mode but I though I might throw it in here as a bonus. If you copy the feature.xml from another carrier (ex is use the ATT one) and paste it in you /system/csc (I'm my opinion) makes your VZW phone better.The stock email app for example will never try to connect to the VZW server again. It will just go straight to the email app. It also seems to make your phone more responsive and work better with certain samsung apps. (Ex: the samsung apps.apk connects better with samsung push service.* Like I said just a little something extra I noticed.*
ENJOY!
EDIT: If anyone is having trouble with part 2 and the secsettings.apk or any other file, try using files from this rom:
EDIT: You may need to wipe first.
http://forum.xda-developers.com/showthread.php?t=2055170
pulled the files from cleanrom, calls still come though. guess on what went wrong?
[QUOTERloadie;39892074]pulled the files from cleanrom, calls still come though. guess on what went wrong?[/QUOTE]
Which rom are you on. Are you sure you used the correct files? The secphone.apk and seccontacts.apk? I would try again and make sure you used the clean rom files. Also check the blocking mode settings allowed contacts list and make sure you have that setup right. If it says none, no calls will go through.
EDIT: Replace the files in the system/app folder with the ones from clean rom and change the permissions and restart. Then clear cache and restart again.
Which rom are you on. Are you sure you used the correct files? The secphone.apk and seccontacts.apk? I would try again and make sure you used the clean rom files. Also check the blocking mode settings allowed contacts list and make sure you have that setup right. If it says none, no calls will go through.
EDIT: Replace the files in the system/app folder with the ones from clean rom and change the permissions and restart. Then clear cache and restart again.
first, thanks for the quick reply. i'm on the VRZ stock rom i605VRALB. pretty sure i grabbed the correct files. tried again, wiped cache, reboot between each step. calls still come though?
loadie said:
Which rom are you on. Are you sure you used the correct files? The secphone.apk and seccontacts.apk? I would try again and make sure you used the clean rom files. Also check the blocking mode settings allowed contacts list and make sure you have that setup right. If it says none, no calls will go through.
EDIT: Replace the files in the system/app folder with the ones from clean rom and change the permissions and restart. Then clear cache and restart again.
first, thanks for the quick reply. i'm on the VRZ stock rom i605VRALB. pretty sure i grabbed the correct files. tried again, wiped cache, reboot between each step. calls still come though?
Click to expand...
Click to collapse
i think i know what the problem is. im gonna send you some files to try hold on..
alphamik3 said:
i think i know what the problem is. im gonna send you some files to try hold on..
Click to expand...
Click to collapse
Try These files:
http://www62.zippyshare.com/v/83374521/file.html
alphamik3 said:
Try These files:
http://www62.zippyshare.com/v/83374521/file.html
Click to expand...
Click to collapse
i really appreciate your helping with this.still didn't work. i'll play around a bit more and see if i can figure out where i'm going wrong.
what is the ds store file?
There is a missing step somewhere for the note 2, I stumbled onto it guide a few days ago in the S3 forum and couldn't get it working 100%
I'm on an at&t ROM with the correct files and modded the files needed, can get blocking mode activated but it only worked about 50% of the time....even switched back to beans ROM and followed necessary steps again and that way only worked about 25% of the time.
Not sure what the extra step its gonna be but I have been working on it for a few days...
jimmydene84 said:
There is a missing step somewhere for the note 2, I stumbled onto it guide a few days ago in the S3 forum and couldn't get it working 100%
I'm on an at&t ROM with the correct files and modded the files needed, can get blocking mode activated but it only worked about 50% of the time....even switched back to beans ROM and followed necessary steps again and that way only worked about 25% of the time.
Not sure what the extra step its gonna be but I have been working on it for a few days...
Click to expand...
Click to collapse
Yea. I don't know how mine works perfectly all of the time but a lot of people are saying they're having trouble. I'm not sure what the deal is. The two roms I tested it on were both clean rom for a vzw note 2. And i tried on a vzw sgs3 on an executioner rom. All three times it worked flawlessly for me.
the phone and mms files in cleanrom are from the verizon rom so thats why thats not working