Guys,
Since SMS / USSD Mod can be done successfully on XOOM 3G, MZ601 Devices, I thought to ask if you guys need to test this on MZ602, MZ616 Rooted Devices.
For that, I need testers with the following devices:
1) MZ602, Some 4G LTE devices are thought to not be able to have SMS enabled because of carrier blocking... We will check about that..
2) MZ616,
I will also give a script for roll-back procedure in case the MOD doesn't work...
wesamothman said:
Guys,
Since SMS / USSD Mod can be done successfully on XOOM 3G, MZ601 Devices, I thought to ask if you guys need to test this on MZ602, MZ616 Rooted Devices.
For that, I need testers with the following devices:
1) MZ602, Some 4G LTE devices are thought to not be able to have SMS enabled because of carrier blocking... We will check about that..
2) MZ616,
I will also give a script for roll-back procedure in case the MOD doesn't work...
Click to expand...
Click to collapse
Shoot it this way my friend - I will test
I know that sms mods work wonders for non US GSM Xoom devices,
would love to see it work on US CDMA/LTE Xoom.
Im down to test as well. My xoom is on a granfathered plan that has unlimited data and texting.
BTW my xoom is the lte model
Great. Thank you guys...
So plz send me your framework-res.apk and your location/carrier.
Sent from my MZ601 using Tapatalk 2
Still seeking?
wesamothman said:
Guys,
Since SMS / USSD Mod can be done successfully on XOOM 3G, MZ601 Devices, I thought to ask if you guys need to test this on MZ602, MZ616 Rooted Devices.
For that, I need testers with the following devices:
1) MZ602, Some 4G LTE devices are thought to not be able to have SMS enabled because of carrier blocking... We will check about that..
2) MZ616,
I will also give a script for roll-back procedure in case the MOD doesn't work...
Click to expand...
Click to collapse
If you are still looking for testers, I'm willing to do.
I have a 77.1.128.MZ616.Retail.en.EU with Android 4.0.4
Carrier is e+ in Germany
leicksta said:
If you are still looking for testers, I'm willing to do.
I have a 77.1.128.MZ616.Retail.en.EU with Android 4.0.4
Carrier is e+ in Germany
Click to expand...
Click to collapse
Yup, why not. Send me your framework-res.apk. it is in /system/framework/
I assume you are rooted.
I've attached it.
And yes 'm rooted.
leicksta said:
I've attached it.
And yes 'm rooted.
Click to expand...
Click to collapse
Here is the MOD
SMS-USSD enabler for MZ616: http://www.mediafire.com/download.php?oacihj4kniap2qn
Rollback in case it doesn't work: http://www.mediafire.com/download.php?bqo75tl6k7nata2
How to install:
1) download both files to your XOOM SD CARD
2) reboot into recovery and flash the mod (enabler)
3) reboot to system
4) make sure you have your SIM mounted for 3G.
5) open the messaging app (will be installed by the mod) and send an sms to another number; or better if you use gosms pro from the market. and send from another number to the one in your XOOM (send/receive tests)
6) open phone and dial a ussd code *#1234#; the number is different from provide to provider.
7) test and report back.
8) upon failure, nothing works, flash the rollback zip from recovery to go back to your original framework.
Hi, I tested your framework-res.apk but had to install (and recover) it with adb and busybox, because I don't have a custom recovery. Afaik I can't install one at the MZ616 due to the locked boot rom. If you know a way to custom recovery like twrp, I would give it a try
The result of swapping the framework-res.apk was the tablet was hanging in the startup with the "waving" Motorola logo.
One thing I noticed was the size of the new file: with 4881 kb it was very small compared to the 8254 kb of the original one.
Is there anything I may have missed, or any other clues?
Lothar
Sent from my XOOM 2 using xda app-developers app
leicksta said:
Hi, I tested your framework-res.apk but had to install (and recover) it with adb and busybox, because I don't have a custom recovery. Afaik I can't install one at the MZ616 due to the locked boot rom. If you know a way to custom recovery like twrp, I would give it a try
The result of swapping the framework-res.apk was the tablet was hanging in the startup with the "waving" Motorola logo.
One thing I noticed was the size of the new file: with 4881 kb it was very small compared to the 8254 kb of the original one.
Is there anything I may have missed, or any other clues?
Lothar
Sent from my XOOM 2 using xda app-developers app
Click to expand...
Click to collapse
Aha, I thought you are rooted which to me should mean you have unlocked boot loader with custom recovery installed. Didn't know you don't have that sort of recovery not installed... you got a boot loop maybe because you used the stock recovery .
Don't worry about the size of file, it is just a matter of compression level during building the apk...
Unfortunately, I don't own mz616 and I yet don't know a way to get twrp on it. Please lease with runandhide05 who might be able to get twrp up and running on your device first.
I'm working with runandhide05 on custom recovery.
But I also made some progress with your framework-res.apk and mms.apk: I installed them again (just to be sure) over adb shell with busybox, and now it worked and my xoom 2 rebooted fine. Now I can receive SMS, but only one time to read with SMSPopup. Sending does not function (I'm using Go SMS). I don't see any other SMS app, but the phone app shown up. If I try to open phone, I only get the message that contacts won't responding. If I open contacts, everything shows up ok, only the phone links don't work. I get the message thart com.android.phone is not responding.
Hope that helps yuo investigating further.
Best regards Lothar
Sent from my XOOM 2 using xda app-developers app
leicksta said:
I'm working with runandhide05 on custom recovery.
But I also made some progress with your framework-res.apk and mms.apk: I installed them again (just to be sure) over adb shell with busybox, and now it worked and my xoom 2 rebooted fine. Now I can receive SMS, but only one time to read with SMSPopup. Sending does not function (I'm using Go SMS). I don't see any other SMS app, but the phone app shown up. If I try to open phone, I only get the message that contacts won't responding. If I open contacts, everything shows up ok, only the phone links don't work. I get the message thart com.android.phone is not responding.
Hope that helps yuo investigating further.
Best regards Lothar
Sent from my XOOM 2 using xda app-developers app
Click to expand...
Click to collapse
On your ROM, stock one, do you have phoe.apk? Or MMS.apk without installing my mod?
I mean before you install my mod, can you check /system/app and see if you have MMS.apk there? If so, please send them to me. I am afraid the ones I included are for xoom1 family, not Xoom 2
wesamothman said:
On your ROM, stock one, do you have phoe.apk? Or MMS.apk without installing my mod?
I mean before you install my mod, can you check /system/app and see if you have MMS.apk there? If so, please send them to me. I am afraid the ones I included are for xoom1 family, not Xoom 2
Click to expand...
Click to collapse
I had before in /system/app: Phone.apk, PhoneAddons.apk, SmscSettings.apk, SMSPopum.apk and Contacts.apk
I only found and installe Mms.apk in your mod. Before the mod I only see Contacts as an App and after the mod also Phone shown up. But I don't see Mms in the apps.
I've attached the original (stock) apks.
leicksta said:
I had before in /system/app: Phone.apk, PhoneAddons.apk, SmscSettings.apk, SMSPopum.apk and Contacts.apk
I only found and installe Mms.apk in your mod. Before the mod I only see Contacts as an App and after the mod also Phone shown up. But I don't see Mms in the apps.
I've attached the original (stock) apks.
Click to expand...
Click to collapse
Oh, OK. Let me see if I can find compatible MMS.apk for your Xoom 2
leicksta said:
I had before in /system/app: Phone.apk, PhoneAddons.apk, SmscSettings.apk, SMSPopum.apk and Contacts.apk
I only found and installe Mms.apk in your mod. Before the mod I only see Contacts as an App and after the mod also Phone shown up. But I don't see Mms in the apps.
I've attached the original (stock) apks.
Click to expand...
Click to collapse
Alright,
I did some modifications to your framework-res.apk;
Indeed, there was this config defined in your framework
"config_text_sms_receive" but there was no send config
What I did is that I added send configuration "config_text_sms_send" and complied it. Also, changed the MMS.apk to a generic one that works across devices. I decompiled the compiled APK and I can see it persists in bools.xml and in public.xml; therefore, the reference was created successfully.
From SmscSettings.apk that you sent, I can see the option that your device can set the SMS Center number. You may wanna try to check that and put the SMS center number the same as the one of your phone "of course from the same service provider". And then try. I hope this works for you know; I can't test it cuz I don't have MZ616 device.
Here is the link; download it and flash it. http://www.mediafire.com/download.php?2b317ejrp7my9ew
In case you need to rollback, couple of posts earlier I included the rollback to original framework.
Good luck and let me know how it goes.
NOTE: I also enabled SIP capabilities for you; so I think you will be able to use your device as a SIP hub and SIP phone over IMS (IP Multimedia Subsystem).
Hi, this is really good news. It is a shame that this function is left out of the deveices ...
Is there any chance for getting that running on the MZ608, ICS4.0.4 ?
koerc said:
Hi, this is really good news. It is a shame that this function is left out of the deveices ...
Is there any chance for getting that running on the MZ608, ICS4.0.4 ?
Click to expand...
Click to collapse
Xoom mz608 is 3g media edition , I don't have it to test. Upload your build.prop and framework-res.apk for me to check and for you to test
wesamothman said:
Alright,
I did some modifications to your framework-res.apk;
Indeed, there was this config defined in your framework
"config_text_sms_receive" but there was no send config
What I did is that I added send configuration "config_text_sms_send" and complied it. Also, changed the MMS.apk to a generic one that works across devices. I decompiled the compiled APK and I can see it persists in bools.xml and in public.xml; therefore, the reference was created successfully.
From SmscSettings.apk that you sent, I can see the option that your device can set the SMS Center number. You may wanna try to check that and put the SMS center number the same as the one of your phone "of course from the same service provider". And then try. I hope this works for you know; I can't test it cuz I don't have MZ616 device.
Here is the link; download it and flash it. http://www.mediafire.com/download.php?2b317ejrp7my9ew
In case you need to rollback, couple of posts earlier I included the rollback to original framework.
Good luck and let me know how it goes.
NOTE: I also enabled SIP capabilities for you; so I think you will be able to use your device as a SIP hub and SIP phone over IMS (IP Multimedia Subsystem).
Click to expand...
Click to collapse
Hi, sorry for the late feedback. I checked your new framework and mms and the new mms shown up as an app and could be started. But there is no change with sending SMS and also old received SMS are not seen by the apps (mms and go sms). Only the sms popup app is showing an incoming sms just one time. If I try to send a sms with mms, I get the message that mms is not responding. The other messages or behavior has not changed to the previous test. Could it be that one app is blocking access to the sim card?
Regards Lothar
wesamothman said:
Xoom mz608 is 3g media edition , I don't have it to test. Upload your build.prop and framework-res.apk for me to check and for you to test
Click to expand...
Click to collapse
Hi, sorry to intrude, but I'm interested in these features. Here are the requested files.
Thanks
jyoshinari said:
Hi, sorry to intrude, but I'm interested in these features. Here are the requested files.
Thanks
Click to expand...
Click to collapse
Any news guys?
Related
Myself and apparently many others like the AOSP apps better than the sense apps. I find the interface for the AOSP messaging, calendar, browser, calculator, and dialer/contacts applications to be more attractive and in some cases more usable. I really liked Bugless Beast 0.4 since it featured these applications, but I have had a hard time with the bug that keeps disk drive from working, and there are various reports of some syncing and battery issues. The EVO-NonSense series has been great too, but I use HDMI out sometimes and like having some of the sense stuff installed. Big thanks to both BuglessPete and tjohnsonjr for their AOSP work.
(7/18/2010) I have attached some of the files I have been using, see descriptions at the bottom of the post.
So since it took a little digging for me to figure out how to do this (even though to advanced users this is easy) I thought it might come in handy for other new users. Additionally I'm hoping by posting this someone can help me figure out how to get the dialer/contacts stuff working, I have the others working fine.
I've done the below on DamageControl, and I think another (baked snack maybe, can't remember). I'll probably throw together an update.zip that can patch these in place later, but I'd rather get the dialer/contacts part figure out first.
Setup:
1. You will need a fully rooted (toast root part 2, NAND unlocked) phone, and adb up and running. There are several explanations for both parts, but the ones listed in the "useful threads" sticky are joeykrim's for adb and toast's part 1 and part 2 for root.
2. I have been using the apk's from BuglessPete's bugless beast 0.4 ROM. The thread for it is available here.
Once you unzip the file, you will find the needed apks in the /system/app folder.
Note: Please donate to pete, he doesn't even have an EVO yet and is doing some great work. Hopefully if he has a phone to work on he can get some of these small bugs squashed and keep the development for BB going.
3. Backup your phone. If you don't know how to reboot into recovery and restore from a nandroid backup, you do not want to do this yet, especially if you want to try help me figure out how to get the dialer running. The idea with the dialer is to try different things until something works. In all likelihood you will hit a point where things are FCing so much you can't do anything. You will almost certainly need to restore from a Nandroid backup at some point.
Important: More than likely anything I list here can't break a phone in a way that a nandroid restore won't fix, but I can not and will not be accountable for any problems with your phone.
Which files:
One nice thing about adding files this way is you can pick and choose what to use. If you like the stock messaging but want the AOSP calendar, you can do just that.
Calculator: Calculator.apk
Calendar: CalendarProvider.apk and Calendar.apk
Default "Navigator" application: CarDock.apk <- you can keep both
Internet: Browser.apk and HTMLViewer.apk <- doesn't show previews of each tab, but allows up to 8 instead of 4. There may be other functionality gained or lost, I dunno.
Clock: DeskClock.apk (can exist beside HTC clock, and can be installed without this procedure)
Messaging (SMS, Text): Mms.apk <- Many people have trouble with this one.
####### Not Working! See post #2 ########
# Phone: Phone.apk, ContactsProvider.apk, Contacts.apk
###################################
To install:
I think you can use adb to do this install with the files still on the computer, but I go ahead and throw all the needed apks onto my sdcard, typically in a folder. Also, if you need to be in the Android SDK's /tools directory to use adb (this depends on your configuration) do that. Connect your phone, and make sure it is in "Charge Only" so the sdcard stays mounted. To make sure adb sees the phone properly issue:
Code:
adb devices
and you should get a return listing the device ID. If so we will mount the /system partition as read-write:
Code:
adb remount
Log into the phones local shell:
Code:
adb shell
you are now on the phones command line and file system, not on your local machine. Now we can start installing files. I'll use Calculator in this example, and I have the apk in a folder on the sdcard called AOSP_apks:
Code:
install /sdcard/AOSP_apks/Calculator.apk /system/app
You can do a couple at a time, and you must do more than one at a time when installing a provider like CalendarProvider.apk and Calendar.apk.
Once you are done, exit the phone's shell, and reboot the phone:
Code:
exit
adb reboot
The change may show up immediately, but the phone and applications aren't designed to change these core functions on the fly, so make sure to reboot the phone. Once it reboots you will probably notice the AOSP icon has replaced the former, and you have the AOSP skin and/or functionality.
Post #2 will deal with progress so far on the dialer/contacts.
(added 7/17) Notes on different apks: The BB Launcher2.apk has his skin on the google search widget, or grab the apk from something else like DC for stock. Launcher.apk from BB is the one with the wide drawer and (I think) 9 screens.
Music.apk from DC is the modded music app from Cyanogen. It has some very nice UI tweaks.
Attached:
- Music.apk used in Cyanogenmod from DC
- Calendar, CalendarProvider, Browser and HTMLViewer from BB 0.4
- CarDock, Calculator, and MMS from AOSP EVO-NonSense
Contacts/Dialer Progress: I'm sure some of the more advanced developers know the answer to this, so ideally someone can fill me in. In the meantime I'll report my findings here, and if others can add feedback to the thread on what they have done, I'll update this post. Hopefully in the long run there will be a straightforward explanation for this I can add to the above post.
I have installed the three files listed above (ContactsProvider.apk, Contacts.apk, and Phone.apk) which seems to install the right bits, but I get FCs.
Later on I added Telephony.apk and FutureDialService.apk, which didn't improve anything. Finally I noticed that Bugless Beast didn't have HTCDialer.apk, so I removed that as well. I think this was the point things went from the dialer and contacts applications FCing to non-stop FCs that kept me from doing anything on the phone.
Attached are the three apps I'm sure are involved for the Contacts/Dialer, pulled from tjohnsonjr's AOSP EVO. More files may be needed, but I'm still trying to figure out which.
The Dialer/Contacts apk used to work, I believe on ROMs that are not based off the newest OTA. Since it worked for me, but stopped once I started using ROMs based of the newest OTA. Anyways great post.
I installed the files and I cant see them. They're in the folders but its like they're hidden from the OS.
I tried to do this before since I love BB but the wake bug in v4 was killing me. I always got install errors. Did you delete the Mms.apk first.. THEN install Mms.apk and reboot? Or did you just install over it? I got errors either way. Also it totally disabled texting on my phone even after reinstalling the HTC Mms.apk.
I had to clean cache/reset then reflash my Nand backup and even then my texting was still broken until I sent one to my wife and then magically I got the 10-15 test "texts" I had sent.
RikusHaven said:
The Dialer/Contacts apk used to work, I believe on ROMs that are not based off the newest OTA. Since it worked for me, but stopped once I started using ROMs based of the newest OTA. Anyways great post.
Click to expand...
Click to collapse
Thanks and thanks. This is interesting. Of course BB is based on the older ROM, so maybe that is why BB works but this doesn't. I'll have to grab an older ROM and try that. It may be an issue of grabbing a newer build of the dialer or something.
warmachine69 said:
I installed the files and I cant see them. They're in the folders but its like they're hidden from the OS.
Click to expand...
Click to collapse
Did it overwrite the existing files? Or do you totally not have whatever you installed, AOSP or sense? Which ROM and version?
MikeBrWade said:
I tried to do this before since I love BB but the wake bug in v4 was killing me. I always got install errors. Did you delete the Mms.apk first.. THEN install Mms.apk and reboot? Or did you just install over it? I got errors either way. Also it totally disabled texting on my phone even after reinstalling the HTC Mms.apk.
I had to clean cache/reset then reflash my Nand backup and even then my texting was still broken until I sent one to my wife and then magically I got the 10-15 test "texts" I had sent.
Click to expand...
Click to collapse
Were you able to successfully do the adb remount first? The way I did it just overwrote the existing Mms.apk.
Also what ROM and version are you running?
laydros said:
Thanks and thanks. This is interesting. Of course BB is based on the older ROM, so maybe that is why BB works but this doesn't. I'll have to grab an older ROM and try that. It may be an issue of grabbing a newer build of the dialer or something.
Did it overwrite the existing files? Or do you totally not have whatever you installed, AOSP or sense? Which ROM and version?
Were you able to successfully do the adb remount first? The way I did it just overwrote the existing Mms.apk.
Also what ROM and version are you running?
Click to expand...
Click to collapse
BBv3 and yes the remount worked.. I am currently in my 84th hour of a long battery duration test so I can't plug it in and try it right now since it will wipe my stats. However it would give some "parse" error and then fail to install. If I forced it by just cp'ing the apk and chmod'ing the exec permissions it would fail horribly.
84th hour of a battery duration test? details please?
MikeBrWade said:
BBv3 and yes the remount worked.. I am currently in my 84th hour of a long battery duration test so I can't plug it in and try it right now since it will wipe my stats. However it would give some "parse" error and then fail to install. If I forced it by just cp'ing the apk and chmod'ing the exec permissions it would fail horribly.
Click to expand...
Click to collapse
Was it something like
Code:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
If so, I had the same error when I didn't have the /system partition fully mounted as read-write. Did you get any errors from the "adb remount" command?
davebu said:
84th hour of a battery duration test? details please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7154719&postcount=993
This is my post talking about it.. I am on hour ~91 of the test.. still running with 8% battery left... BBv3 rocks!
laydros said:
Was it something like
Code:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
If so, I had the same error when I didn't have the /system partition fully mounted as read-write. Did you get any errors from the "adb remount" command?
Click to expand...
Click to collapse
Hmmm maybe I did and didn't notice it.. I am down to 8% right now so by mid day my battery will probably die. I am hoping to make the 100Hr on one charge mark, after that I will try again and note any errors.
MikeBrWade said:
Hmmm maybe I did and didn't notice it.. I am down to 8% right now so by mid day my battery will probably die. I am hoping to make the 100Hr on one charge mark, after that I will try again and note any errors.
Click to expand...
Click to collapse
ok so I just redid your steps and I didn't get the error code this time (maybe my remount didn't work the last time I tried it). But now I get FC everytime I try and launch the text app. I installed over the Htc mms.apk =(
Anyone got an HTC Mms.apk handy they can post so I don't have to restore nand?
If you have the AOSP apps available, could you please post them all in .zip folder in the OP?
MikeBrWade said:
ok so I just redid your steps and I didn't get the error code this time (maybe my remount didn't work the last time I tried it). But now I get FC everytime I try and launch the text app. I installed over the Htc mms.apk =(
Anyone got an HTC Mms.apk handy they can post so I don't have to restore nand?
Click to expand...
Click to collapse
NVM I extracted it from an old nand backup. So, for me at least the Mms.apk from AOSP causes FCs and won't run at all . Put the HTC Mms.apk back and it works fine. =( Urgh any hints?
edited to add the HTC Mms.apk incase someone does what I did and kills it, so they dont' have to go through the process of trying to extract it.
MikeBrWade said:
NVM I extracted it from an old nand backup. So, for me at least the Mms.apk from AOSP causes FCs and won't. Put the HTC Mms.apk back and it works fine. =( Urgh any hints?
edited to add the HTC Mms.apk incase someone does what I did and kills it, so they dont' have to go through the process of trying to extract it.
Click to expand...
Click to collapse
The only issues I've had with the AOSP Mms.apk was the lack of actual mms functionality.
thanks for the apk so I could go back
I[E said:
The only issues I've had with the AOSP Mms.apk was the lack of actual mms functionality.
thanks for the apk so I could go back
Click to expand...
Click to collapse
Interesting that you say that, since I had some MMS texts in my cache. Wondering if when the AOSP version couldn't deal with them so it just FC'ed instead.
So I tried that, deleting ALL my texts so it wouldn't have some MMS collision or something. But that didn't work either, HTC Mms.apk works fine.. the AOSP.apk FC's. Could the OP or something with a working AOSP Mms.apk post it maybe it's my copy. Mine has an MD5 of : 441e3b8863bc3ab88ce6ad9bc1671f22
I have mms messages in my cache too. The AOSP apk shows them fine, just can't send new mms messages. Maybe your file is corrupt?
Sent from my PC36100 using XDA App
I going to upload all the AOSP apks that I include in my ROMs when I get home tonight.
Can you tell us how you got contacts.apk to work? I'm trying with FreshRom and I pulled the Contacts.apk from your Rom and it won't recognize the file when I push it using adbshell. The file is in the app folder but android ignores it.
I[E said:
I have mms messages in my cache too. The AOSP apk shows them fine, just can't send new mms messages. Maybe your file is corrupt?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Does does your md5 match mine?
this is for Rogers users who have wifi calling in their plan.
How to get wifi calling working on htc sensation.
You need lib files from Rogers EVO, I found them in KingCobra3Dv1.6 ROM
(http://forum.xda-developers.com/showthread.php?t=1267131):
libganril.so
libhtc_ril.so
libhtc_ril_switch.so
libkineto.so
librilswitch.so
Copy them to /system/lib
then you will also need apk for rogers wifi calling from kineto. I've found one on this forum (googled it):
MS-HTC-SHT-GB-2.3-48407-06.1.apk
This file is from Rogers EVO uploaded here by nice user(http://forum.xda-developers.com/showthread.php?t=1216683&page=2). You will need to put it in
/system/app
Last step is to add to your build.prop this line:
rild.libpath=/system/lib/librilswitch.so
restart, enjoy!
Hey folks,
does anyone have Android 4 (ICS) ROM for EVO 3D with Rogers?
Im looking for lib file from this ROM ----> libhtc_ril.so
WiFi calling wont work after upgrading to newst radio , the lib is outdated
do we need root access?
DenDen2012 said:
do we need root access?
Click to expand...
Click to collapse
Since you have to write to /system yes you need root.
Sent from my HTC Sensation 4G
I have done some research on how to root my sgs2. Once I do that today I will try and install the fix you have suggested. The lib files can be found in the file tree of the mod you suggested? I can just browse its folders, correct? No need to actually install it on my sgs2? Thanks for your help.
How is the workaround working for you? Are you getting uma without issues? Does it drain battery like alot of evo users have been reporting?
Ive followed everything you described step by step. It doesn't work. I see the icon when i click on it, it launches but exits from the app two seconds afterward. No error..
In the app it says wifi calling "enabling..." with the checkbox being checked of. I can click on other menu options and it doesn't close the app.
I can also assure you that I have wi-fi calling access on my account.
DenDen2012 said:
I have done some research on how to root my sgs2. Once I do that today I will try and install the fix you have suggested. The lib files can be found in the file tree of the mod you suggested? I can just browse its folders, correct? No need to actually install it on my sgs2? Thanks for your help.
How is the workaround working for you? Are you getting uma without issues? Does it drain battery like alot of evo users have been reporting?
Click to expand...
Click to collapse
Yes, the libs are in lib directory, all I did is just copy them to lib on my phone. You may want to extract the zip on pc.
As for battery, it is in fact better since it turns off radio once it connects to WiFi.
There is no issues so far and voice quality is pretty good considering my moderate internet speed of 1.3M
Sent from my HTC Sensation Z710e using XDA App
DenDen2012 said:
Ive followed everything you described step by step. It doesn't work. I see the icon when i click on it, it launches but exits from the app two seconds afterward. No error..
In the app it says wifi calling "enabling..." with the checkbox being checked of. I can click on other menu options and it doesn't close the app.
I can also assure you that I have wi-fi calling access on my account.
Click to expand...
Click to collapse
Well. First question; after reboot did you get a window pop up saying something like " did you know that your phone can make WiFi calling" ?
This indicates that the libs are working, apk itself won't work. Also is the icon red, kind of Rogers like? If its not then you have T-Mobile apk which again doesn't work.
If it works , you actually don't open the app, it will turn on automatically when signal is too low. There is no force mode to use WiFi instead of GSM.
You can in fact open it with winrar or any zip software and search for rogers string, to make sure.
Also its good to check if the prop.build file has the line I've mentioned. I had my system dir in read-only mode and it was not saved.
I put the line at the end but I doubt it matters.
Otherwise I'm pretty sure that is all you need.
Oh, yeah, Im sure u have the feature but if you have a chance to test it in any blackberry, give it try. I checked mine before.
m
Sent from my HTC Sensation Z710e using XDA App
I wanted to follow up. I did everything that was described and had the app on the phone but still couldn't make calls. I added the one line in the build.Prop file. In theory I did all that was required then I noticed my imei was gone. It took me 2 hours to get my phone back to original state. Clockworkrecovery mod saved me and I ended up restoring my phone. I would still like to get this thing to work as I am going nuts without signal coverage.
I come from the world of blackberry and I know uma worked.
I wish there was an easier way for this to get going. I am a persistent noob when it comes to android, so I know I will get this working. I appreciate your help in this manner.
Rogers should release an app on the market allowing all android and iphones to have this, it would only benefit everyone involved. As a rogers employee I will continue to lobby for this to happen.
I will need to revisit this once my exams are done. I will do more research on this as well.
PS. I did not get the pop up when I booted my phone. There was an htc file in there. Does it matter that I have an sgs2?
The libs are from rom for sensation, I'm not sure if they work for Samsung. In fact I think not. But the apk should be fine. It's made providers. See if you can find similar lib files from sgs2 ROM
Sent from my HTC Sensation Z710e using XDA App
Hey guys im not sure if this thread is still going on but i just got my hands on a rogers evo 3d thats updated to ics 4.0.3 i would like to be able to use wifi calling on my other phones with ics, how do i get these files?
Hi Guys,
I have a evo 3D with ICS 4.0.3, I am trying to get Rogers calling to work on a Samsung Galaxy S2.
I have uploaded the files outlined in this thread here (http://forum.xda-developers.com/showthread.php?t=2006763)
Anyone have any idea how to get this to work on a S2?
yuiou said:
Hi Guys,
I have a evo 3D with ICS 4.0.3, I am trying to get Rogers calling to work on a Samsung Galaxy S2.
I have uploaded the files outlined in this thread here (http://forum.xda-developers.com/showthread.php?t=2006763)
Anyone have any idea how to get this to work on a S2?
Click to expand...
Click to collapse
wrong forum man
this is only for sensation/xe/4g
rzr86 said:
wrong forum man
this is only for sensation/xe/4g
Click to expand...
Click to collapse
This was for people in this thread looking for ICS HTC files.
The Google Now Installer/Restorer v1.1
Purpose
There have been a lot of users with issues installing and uninstalling Google Now for ICS. This is my solution for those users.
This is only an installer for the many different variations of Google Now that were created in this news worthy thread: The Google Now for ICS Project
This installer allow user of different types of roms and devices to quickly install Google Now to see if it works for them and if it does not, it allows these users to restore their original Google Search.
This thread is not and will not be about issues with specific modded Google Now apks, go here: The Google Now for ICS Project for that. I have no problem incorporating new apks into the installer. But I will not attempt to deal with issues outside of the installer.
Testing(Green = working, Red = not working)
(Need more people to test as many different devices, roms, and recoveries)
Devices
HTC EVO 3D
HTC EVO 4g LTE
Roms
OTA_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2-2.17.651.5
Tranquility rls1b
Recoveries
CWM 5.0.2.0
TWRP s-on
So if you experience any issues, I will attempt to help, but understand that I if you are not setup the exact same, I may not know what is wrong.
Touch recovery is not active in this aroma installer, so use up and down to make a selection and the power button to confirm the selection.
Requirements
Rooted
ICS
CWM (only recovery tested, others may work, you let me know)
Instructions(should already know this, but here you go)
1. Transfer .zip to the root of your sd card
2. Boot into recovery
3. Select "install zip from sdcard"
4. Select "choose zip from sdcard"
5. Select "GoogleNowforICSInstaller_v1.0.zip"
6. Select "Install GoogleNowforICSInstaller_v1.0.zip"
Once the installer is up, the rest should be self explanatory, if not just follow the prompts.
I hope this helps someone.
Change Log
v1.1
-- Change file host
-- Added support for different versions of Google Search
-- Added support for Velvet
v1.0
-- Initial
Downloads
Google Now for ICS Installer v1.1
I havent been following google now lately, but it seems that you're using stock rooted ics on evo where this works. is this also true for touchwiz phones?
will it work on stock rooted samsung?
Just checked it out on my HTC EVO 4g LTE running tranquility rls1b and TWRP s-on, works great back and forth. Thanks!
YoColdRain said:
I havent been following google now lately, but it seems that you're using stock rooted ics on evo where this works. is this also true for touchwiz phones?
will it work on stock rooted samsung?
Click to expand...
Click to collapse
It should work on any ICS phone, but it has only been tested on the phone listed in the 1st post.
jdcasino confirms that it works on his HTC EVO 4g LTE.
Download link is down
Hello,
Any chance we can get another link?
Regards
MichaelMun0z said:
Hello,
Any chance we can get another link?
Regards
Click to expand...
Click to collapse
link seems to be up. If someone has a mirror I can post it in the 1st post.
MichaelMun0z said:
Hello,
Any chance we can get another link?
Regards
Click to expand...
Click to collapse
I just upload it for you, i'll not try it now
http://ge.tt/api/1/files/3NAw6KM/0/blob?download
frooss said:
I just upload it for you, i'll not try it now
http://ge.tt/api/1/files/3NAw6KM/0/blob?download
Click to expand...
Click to collapse
Got it, it's in 1st post.
reekotubbs said:
Got it, it's in 1st post.
Click to expand...
Click to collapse
Great, thank you :good:
Will this work on any phone running ICS you think?
Ive got the Korean SGS III, a lot of things arent made for this phone......
reekotubbs said:
It should work on any ICS phone, but it has only been tested on the phone listed in the 1st post.
jdcasino confirms that it works on his HTC EVO 4g LTE.
Click to expand...
Click to collapse
yes, but if I remember correctly, touchwiz differs from sense in framework files or something. I have epic 4g touch. can anyone else confirm that google now can work on stock rooted touchwiz phone if /system space wasn't an issue?
[email protected] said:
Will this work on any phone running ICS you think?
Ive got the Korean SGS III, a lot of things arent made for this phone......
Click to expand...
Click to collapse
Sure, give it a try.
edit: there may be an issue with the Installer not finding the original Google Search apk, someone posted this and basically it states that you may have a some extra characters at the end of the apk.
YoColdRain said:
yes, but if I remember correctly, touchwiz differs from sense in framework files or something. I have epic 4g touch. can anyone else confirm that google now can work on stock rooted touchwiz phone if /system space wasn't an issue?
Click to expand...
Click to collapse
I don't think it has anything to do with sense or touchwiz, the modified Google Now was modded for AOSP, which doesn't have either, but has worked on HTC and Samsung.
reekotubbs said:
I don't think it has anything to do with sense or touchwiz, the modified Google Now was modded for AOSP, which doesn't have either, but has worked on HTC and Samsung.
Click to expand...
Click to collapse
thanks, I've used the installer and works flawless as far as finding that my /system doesnt have enough space. need to figure out what i can get rid off to make some space.
I wl ging to try.......
porky008 said:
Since it won’t let me post to the forum I thought I would just do it this way. On my Verizon S3 I’m rooted, unlocked, OTA kernel, running a stockish rom (cleanrom) and CMW 6.0.1.2. The installer said it worked but it broke Google search. In the installer it said everything was fine but nope. I went to do the restore and it said it couldn’t find the backup so I went with the one provided and that worked fine. When setting up I chose the first one which I think was v7 for arm7. If I chose wrong I’ll try again but otherwise I’ll just wait for an updated version. Unlike others I’m in no hurry and was just testing it out on my phone. If you want more info I can try to install it again and try to provide whatever you might need or want.
Click to expand...
Click to collapse
What do you mean by it broke Google Search (what were the indications that it did not work)?
When you restored did Google Search work again?
Check if you hae the follow "GoogleQuickSearchBox.apk" in your "/system/app"
Are there other files with this same name?
larva_pro said:
Hello , sorry for bother you with a PM ,, but forum dont let me post in the topic because i have less of 10 post.
your installer is great , i really like the features on it. but i do have a problem. everytime i try to install the Google now
no matter what files from the installer it always return the error that i need to free space on the devide. and i have 4GB free on the external
and 2gb in the internal.
im using ICE stock rooted. with AGAT CWN. my device is the epic 4g touch.
any advice here?
also i tried to install with this instructions. http://forum.xda-developers.com/showpost.php?p=29756226&postcount=2856
and i does install but google now opens and close cant do anytnig at all with it.
Click to expand...
Click to collapse
How much space does it state that you have free in the /system directory?
It would seem that you don't have enough space in your /system directory of your internal memory.
One thing to try to see if this is the case, when you do it manually, don't modify or add any files to /system/usr/srec/ directory
larva_pro said:
if i go to settings>storage its says
Device memory: Total 1.97GB ; available 1.3GB.
i did installed manually with out changing nothing on the /system/usr/srec . and im able to opent he register of google now.. as soon i click im'in
it close and dont show nothing.
in the notification bar i get cards notification but if i click to open it it close again. i cant see any card. nor command .....nothing.
Click to expand...
Click to collapse
To get the total /system directory size you need to run the following command in a program like "Terminal Emulator" or "aShell":
df /system
Click to expand...
Click to collapse
porky008 said:
Yes I have that GoogleQuickSearchBox.apk in /system/app and yes it is without the _usa after it. On the line under it it has the odex version. Then the Google search widget apk and odex. It is this way with before and after I try to install.
Just tried it again choosing mikeyxda v7 it says created backup ok and return status 0. Google now installed return status 0 once the phone boots up it says “unfortunately, Google search has stopped”. I also get that message no matter how i try to search or tap on the google app it puts on it. Double checked the permissions from the main thread and all permissions are set right, if that helps. Went to restore and it says I never backed it up but I can use the generic one which I select and get again return status 0 for everything and once the phone comes back up Google search works just fine again. Hope this helps.
Click to expand...
Click to collapse
That's good to know. I see that the problem has to do with your system being odexed.
The reason it FCs is because when replacing the Google Search apk there is no matching modified odex.
This is modified for deodexed roms.
Check on this thread and ask about a modified odexed velvet.apk and velvet.odex
reekotubbs said:
That's good to know. I see that the problem has to do with your system being odexed.
The reason it FCs is because when replacing the Google Search apk there is no matching modified odex.
This is modified for deodexed roms.
Check on this thread and ask about a modified odexed velvet.apk and velvet.odex
Click to expand...
Click to collapse
I'm using GN on an odexed ICS ROM, no problems. Just had to delete the *.odex files for the apk's that the installer replaces.
Sent from my ADR6425LVW using Tapatalk 2
**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: Those of you having trouble with step 2 with the secSettings.apk, try the file from either of these rom:
EDIT: You may need to wipe first.
4.1.1: http://forum.xda-developers.com/showthread.php?t=2033132
or
4.1.2: http://forum.xda-developers.com/showthread.php?t=2113436
or
4.1.2: http://wanamlite.com/2013/03/07/romcwmxxemb5jelly-bean4-1-2-deodexed-stock-rom/
alphamik3 said:
**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!
Click to expand...
Click to collapse
what does deleteing the /efs/imei, and sales_code.dat. do?
Sec settings crashes after I replace it, fix permissions, and reboot. Tried cache wipes, etc. No luck on that part. Using a Sprint base MB1 for all files.
countryfolk07 said:
Sec settings crashes after I replace it, fix permissions, and reboot. Tried cache wipes, etc. No luck on that part. Using a Sprint base MB1 for all files.
Click to expand...
Click to collapse
I didn't mess with it long, but I got it to work once, but then I wiped and tried again and the same method I used didn't work, so I tried following the OP and didn't work.
if deleting those two files isn't that big of a deal I may try and figure out how to appropriately port this MOD using VZW .apks edited using int. .apks
andybones said:
I didn't mess with it long, but I got it to work once, but then I wiped and tried again and the same method I used didn't work, so I tried following the OP and didn't work.
if deleting those two files isn't that big of a deal I may try and figure out how to appropriately port this MOD using VZW .apks edited using int. .apks
Click to expand...
Click to collapse
Which rom are you on? I can give you the files iv been working with if you want to try. Iv been working with an ATT Rom. This method after wiping worked with the files iv been using.
As for the sales_code.dat and map_code.dat as i know that are just for the market to reconginze your device a VZW.for certain VZW apps. Like i said the only thing it did after deleting them for me was the market thing. certain apps like backup assistant might not work properly. everything else is fine.
Also yea a port might be better. Let me know whats up.
alphamik3 said:
Which rom are you on, and is your boot loader unlocked? I can give you the files iv been working with if you want to try. Iv been working with an ATT Rom. This method after wiping worked with the files iv been using.
As for the sales_code.dat and map_code.dat as i know that are just for the market to reconginze your device a VZW.for certain VZW apps. Like i said the only thing it did after deleting them for me was the market thing. certain apps like backup assistant might not work properly. everything else is fine.
Also yea a port might be better. Let me know whats up.
Click to expand...
Click to collapse
I have CleanROMACE downloaded, I got it working with that, very strange though, I did get it showing, blocking mode did turn on and everything got he noti in the status bar I didnt test to make sure they work im sure they do.
I did comb through the VZW secsettings.apk and the one that makes it work and I cannot find a single thing that is making blocking mode show..
very weird..
I'm going to try going thru the SecConacts.apk and SecPhone.apk to see if I an get a port. if you don't use the att secconacts andsecphone, does blocking mode what just not work? fc? do you know by chance?
thank you
andybones said:
I have CleanROMACE downloaded, I got it working with that, very strange though, I did get it showing, blocking mode did turn on and everything got he noti in the status bar I didnt test to make sure they work im sure they do.
I did comb through the VZW secsettings.apk and that makes it work and I cannot find a single thing that is making blocking mode show..
very weird..
I'm going to try going thru the SecConacts.apk and SecPhone.apk to see if I an get a port. if you don't use the att secconacts andsecphone, does blocking mode what just not work? fc? do you know by chance?
thank you
Click to expand...
Click to collapse
Ok so on my note 2 I am also on clean Rom ace. So all I did was delete the Sale_code and map_code files and it will show blocking mode in the menu and blocking mode already works. no need to replace any files because clean rom uses generic apks i guess that work for all carriers. so blocking mode already works.. as for the galaxy s 3 i used an att rom to get blocking mode to work with the method in the op. I will upload the files and send you a link in a minute
alphamik3 said:
Ok so on my note 2 I am also on clean Rom ace. So all I did was delete the Sale_code and map_code files and it will show blocking mode in the menu and blocking mode already works. no need to replace any files because clean rom uses generic apks i guess that work for all carriers. so blocking mode already works.. as for the galaxy s 3 i used an att rom to get blocking mode to work with the method in the op. I will upload the files and send you a link in a minute
Click to expand...
Click to collapse
I found the post i got the files from: http://forum.xda-developers.com/showthread.php?t=2033132
This is for the Galaxy S3. This rom is for the ATT/Bell/Rogers/Telus version. i used the above method on a vzw based rom and it wokerd.
For the Galaxy Note 2. i just used the files on clean rom ace on a vzw based rom on the note 2 with the above method and it worked.
alphamik3 said:
I found the post i got the files from: http://forum.xda-developers.com/showthread.php?t=2033132
This is for the Galaxy S3. This rom is for the ATT/Bell/Rogers/Telus version. i used the above method on a vzw based rom and it wokerd.
For the Galaxy Note 2. i just used the files on clean rom ace on a vzw based rom on the note 2 with the above method and it worked.
Click to expand...
Click to collapse
can you upload the feature.xml you pulled from there so i don't need to DL a whole package just to compare the xml's? thanks!!
alphamik3 said:
I found the post i got the files from: http://forum.xda-developers.com/showthread.php?t=2033132
This is for the Galaxy S3. This rom is for the ATT/Bell/Rogers/Telus version. i used the above method on a vzw based rom and it wokerd.
For the Galaxy Note 2. i just used the files on clean rom ace on a vzw based rom on the note 2 with the above method and it worked.
Click to expand...
Click to collapse
that ROM is 4.1.1 though, and we are on 4.1.2
---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------
Thebear j koss said:
can you upload the feature.xml you pulled from there so i don't need to DL a whole package just to compare the xml's? thanks!!
Click to expand...
Click to collapse
the feature.xml from my cell/message block should actually work
andybones said:
that ROM is 4.1.1 though, and we are on 4.1.2
---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------
the feature.xml from my cell/message block should actually work
Click to expand...
Click to collapse
the files still work.. i will try to find a 4.1.2 rom though
and here is a link to the feature.xml i am using.. it was from the ATT CSC from clean rom ace 4.6.1
http://www72.zippyshare.com/v/65690441/file.html
alphamik3 said:
the files still work.. i will try to find a 4.1.2 rom though
and here is a link to the feature.xml i am using.. it was from the ATT CSC from clean rom ace 4.6.1
http://www72.zippyshare.com/v/65690441/file.html
Click to expand...
Click to collapse
here is a european stock 4.1.2 rom: http://wanamlite.com/2013/03/07/romcwmxxemb5jelly-bean4-1-2-deodexed-stock-rom/
here is a link for SynergyROM: http://forum.xda-developers.com/showthread.php?t=2113436
i would try the european rom first. but the should both work.
Another way to do this is to use the 23 lidroid toggle MOD and just enable the "dormant mode" that is blocking mode, this way you don't have to mess with settings.apk and anything with market. long press the toggle to access the settings. and flash the phone and contacts. i havent tested to see if anything works but it should id imagine. if not at least u dont have to mess with settings..
andybones said:
Another way to do this is to use the 23 lidroid toggle MOD and just enable the "dormant mode" that is blocking mode, this way you don't have to mess with settings.apk and anything with market. long press the toggle to access the settings. and flash the phone and contacts. i havent tested to see if anything works but it should id imagine. if not at least u dont have to mess with settings..
Click to expand...
Click to collapse
This worked for me.
Sent from my SCH-I535 using xda app-developers app
andybones said:
Another way to do this is to use the 23 lidroid toggle MOD and just enable the "dormant mode" that is blocking mode, this way you don't have to mess with settings.apk and anything with market. long press the toggle to access the settings. and flash the phone and contacts. i havent tested to see if anything works but it should id imagine. if not at least u dont have to mess with settings..
Click to expand...
Click to collapse
True. Although I personally could are less about any of verizons apps. I think they all are garbage, so for me i dont care about the market saying my device isnt recognized because i dont use them anyway. And the whole reason behind verizon changed everything in the the first place P*$$ed me off and drove me to want to change everything back, the way it should be, the way ALL the other carriers have there phone set up. This is how i found my method. So swapping the settings.apk for another, and deleting 2 (IMO) useless files, will make the menu look the way it was intended to with blocking mode in the menu, no replacement airplane mode toggle, and NO permenant backup assistant accounts, which shows up even if backup assistant is deleted on your phone. There is obviously more than one way to achieve this a blocking mode fix. Its good to have options.
alphamik3 said:
True. Although I personally could are less about any of verizons apps. I think they all are garbage, so for me i dont care about the market saying my device isnt recognized because i dont use them anyway. And the whole reason behind verizon changed everything in the the first place P*$$ed me off and drove me to want to change everything back, the way it should be, the way ALL the other carriers have there phone set up. This is how i found my method. So swapping the settings.apk for another, and deleting 2 (IMO) useless files, will make the menu look the way it was intended to with blocking mode in the menu, no replacement airplane mode toggle, and NO permenant backup assistant accounts, which shows up even if backup assistant is deleted on your phone. There is obviously more than one way to achieve this a blocking mode fix. Its good to have options.
Click to expand...
Click to collapse
I wasn't posting this to put you down, just a simpler way to do it.
Just because you don't think that those file are important doesn't mean EVERYONE else feels that way. I give you mad props for finding the other two (useless) files to get it to show in settings (which isn't even made for our phones and adds a lot of MORE useless crap).. IMHO
I'm sure many users enjoy your method, but I think many others will also appreciate NOT having to replace their settings.apk and remove files that a VZW phone needs. Pushing the Phone.apk and Contacts.apk from Synergy is no biggie since we use that ROM anyway.
No need to get defensive bud. Team work is the key here, I'd like to eliminate all int. .apks, and try and port w.e code is missing from our VZW .SecPhone.pk and SecContacts.apk.
again, like I said - mad props for figuring this out bro, many many people across VZW on sgiii and note2 were requesting this like crazy.
and again wasn't trying to put your method down by any means, just letting those know of another way.
andybones said:
I wasn't posting this to put you down, just a simpler way to do it.
Just because you don't think that those file are important doesn't mean EVERYONE else feels that way. I give you mad props for finding the other two (useless) files to get it to show in settings (which isn't even made for our phones and adds a lot of MORE useless crap).. IMHO
I'm sure many users enjoy your method, but I think many others will also appreciate NOT having to replace their settings.apk and remove files that a VZW phone needs. Pushing the Phone.apk and Contacts.apk from Synergy is no biggie since we use that ROM anyway.
No need to get defensive bud. Team work is the key here, I'd like to eliminate all int. .apks, and try and port w.e code is missing from our VZW .SecPhone.pk and SecContacts.apk.
again, like I said - mad props for figuring this out bro, many many people across VZW on sgiii and note2 were requesting this like crazy.
and again wasn't trying to put your method down by any means, just letting those know of another way.
Click to expand...
Click to collapse
I wasn't trying to sound like I was getting defensive I was just saying what I thought. Thanks you for the props. I also have to give you props. I agree the missing code is a better and easier method then mine. And I agree team work makes the dream work lol.. I have no idea how to edit the code and go through lines of code of apks so your skills clearly surpass mine.. but yeah glad I can help with what I discovered and hope we can figure it out properly.
I've been trying to use the CM MMS.apk on my rooted TW. I know that adding the apk into the apps folder allows the SMS application for texting. My question is how to get MMS picture messages working. I saw something about decompiling but I'm not fluent enough to know what I'm doing or looking at. Is anyone successfully running the MMS apk on the 4.3 update. If so how or can you link to the file? I really like the quick reply functionality.
BungeBash said:
I've been trying to use the CM MMS.apk on my rooted TW. I know that adding the apk into the apps folder allows the SMS application for texting. My question is how to get MMS picture messages working. I saw something about decompiling but I'm not fluent enough to know what I'm doing or looking at. Is anyone successfully running the MMS apk on the 4.3 update. If so how or can you link to the file? I really like the quick reply functionality.
Click to expand...
Click to collapse
Actually, the work has already been done for you! You can go HERE. Just flash this in recovery and if all is well, it should work.
Note: I am not the creator of this file, complete credit goes to member old&slow.
Note: I can say this works on old&slow's stock deodexed rom, however I am not sure how this all plays out with the new locked bootloader that seems to be causing trouble for many.
Hope that helps
EDIT: In case it is not the Mms.apk you like, according to old&slow's instructions, you can push your own Mms.apk to /system/apps
yosterwp said:
Actually, the work has already been done for you! You can go HERE. Just flash this in recovery and if all is well, it should work.
Note: I am not the creator of this file, complete credit goes to member old&slow.
Note: I can say this works on old&slow's stock deodexed rom, however I am not sure how this all plays out with the new locked bootloader that seems to be causing trouble for many.
Hope that helps
EDIT: In case it is not the Mms.apk you like, according to old&slow's instructions, you can push your own Mms.apk to /system/apps
Click to expand...
Click to collapse
I appreciate the link to the file. Do you mind linking to the original thread you found it? Also, on 4.3 I can't boot into recovery, it tells me that I am running a non-legit version yadda yadda. How can I flash this otherwise?
BungeBash said:
I appreciate the link to the file. Do you mind linking to the original thread you found it? Also, on 4.3 I can't boot into recovery, it tells me that I am running a non-legit version yadda yadda. How can I flash this otherwise?
Click to expand...
Click to collapse
As for the recovery stuff, I'm not sure at the moment. But as for the thread, you can find it here. The third post on the thread should have a "MODS" section where you can find a link to the zip I linked to earlier.
Hope that helps