Hi everyone,
I've got an ATT I337 running the awesome Hyperdrive ROM version 17.1. Several of us --but clearly not all of us!-- over in that thread have noticed a problem with incoming calls. I think there's a setting somewhere that can fix it, so I'm opening it to a wider audience by posting it here, in hopes someone from this group will know what to tweak.
Here's the specific problem.
If my cell phone receives a call from a known contact "Bob" and Bob's contact info (being a U.S. phone number) is 317-555-1212, so far the phone seems to recognize the call as coming from Bob. However, it reports it as coming from +317-555-1212. When I go into the call log and try to return the call, it dials +317-555-1212, and the extra + causes the system to interpret it as an international call attempt, and the call fails. Cannot be completed as dialed, the message says. If it's an non-contact number, the + is still added. IT's not JUST for contacts.
Let's say Bob leaves a message. The voicemail indicator shows and it says offers to dial *86, the correct access code for voice mail for ATT as I understand it. However, tapping that actually dialed +11 then my ten digit phone number. Call fails.
At the dialpad, pressing and holding 1 to invoke voicemail has the same problem.
In Contacts, contacts are NOT listed with +s, and clicking the call button for them makes them dial OK without a + being prepended.
So, this looks like some international feature is being enabled that I'm not sure how to turn off. Does anyone have any idea how to turn this off? Sorta puts a crimp in the basic phone functionality. Seriously, who actually calls anyone these days? But it would be good to fix.
Please, if anyone has an idea of what might be at the root of this, I would appreciate your help!
Marc
I am confused. Does this only happen on the Hyper rom or all roms for you.
Not sure how anyone else does their contacts. But, I always enter numbers as 1-555-555-5555 even if local.
My voicemail number is set as +15555555555
I never had issues--
I remember some talk of that on Hyper awhile back. But, never paid attention--
Only happens on Hyperdrive. Or at least, I can say I never saw it on stock. Hyper is the only ROM I've actually gotten so far as to run while SIM card is inserted. :good:
My contacts are almost all US based and are just ten digits, no leading 1. I did try editing the contact to my work cell phone by adding a 1 to it, and calling my S4 phone. It still was registered as +317-555-1212 format and return call didn't work.
So, it's not really about the way the contacts are stored, more about how the phone interprets incoming calls.
Try the 1+ and see what happens. Just do a few of your most used numbers to start--
Can you put a different dialer on phone and see
rugmankc said:
Try the 1+ and see what happens. Just do a few of your most used numbers to start--
Can you put a different dialer on phone and see
Click to expand...
Click to collapse
Just edited above, adding 1 to the way contacts are stored doesn't change the behavior. I can certainly try a different dialer and see what happens, but it seems to be based on how incoming calls are interpreted. I'm guessing there's a build.prop item or somesuch that needs a-tweaking.
Marc
so you changed the contact number to 1-555-555-5555 with hyphens
i ran hyper for quite a bit awhile back never any issues. of course could be something new--
i am not thinking rom or a lot more would have issue--
I did some tests.
On the phone in question, I edited the google contact for a test phone number. I then called the phone from that tested phone number.
It didn't matter whether the contact was saved in the formats:
317-555-1212
1-317-555-1212
+1-317-555-1212
+317-555-1212
In all cases, the incoming call was recognized as +317-555-1212, which isn't a valid call-back number, and return calls failed. Since this only happened when I put a custom ROM on, I'm sure it's something buried inside the ROM. However, I'm at a loss as to where to check various settings.
Gotta be something deep in there...
If all else fails you can Odin back to stock, reformat your internal card and reroot.
Under Phone Settings/Additional Settings/My Phone Number--is it in format 15555555555
Also, and I don't know where to check, your country code may not be set. I don't know if we even have that setting anymore or would it be in Build Prop.
Probably under ro.something
rugmankc said:
If all else fails you can Odin back to stock, reformat your internal card and reroot.
Under Phone Settings/Additional Settings/My Phone Number--is it in format 15555555555
Also, and I don't know where to check, your country code may not be set. I don't know if we even have that setting anymore or would it be in Build Prop.
Probably under ro.something
Click to expand...
Click to collapse
Interesting thought. I had gone into the dialer settings, and checked the Current Country... it listed United States of America. Then I stopped. But looking further it turns out that in the Assisted Dialing settings just below that, there might be stuff that matters. Currently my assisted dialing is OFF. The settings inside are:
Country code: 1
IDD prefix: 011
NDD prefix 1
City/area code: 131
National number length: 11
The area code probably doesn't matter, but I'm interested in the national number length. Ours tend to be 10. Could you please see what your settings are in there, and let me know if anything is different?
I can always backup (ug, safestrap backup), return to stock, poke around, re-root/restore. But if you could take a quick peek I'd be grateful.
Thank you!
Marc
I tried an alternative dialer... it acted just like the stock with the + thing.
I am on a rom that doesn't have those settings--sorry
Thanks anyway! I experimented changing the last setting to 10, and enabling assisted dialing, and it didn't change anything. Sigh.
Ok, you can still go back to stock with Odin. Or, try one of iB's roms they are very good too, I use them almost exclusively now--
Good Luck--:good:
Yeah. I've been back to stock a couple times with Odin. I've got the process down pat! I prefer the hyperdrive rom if I can work through the few small warts. It's just such an elegantly crafted piece of work. Worth the effort, if I eventually sort out the call issue. Appreciate your help.
Sent from my SCH-I337 using Tapatalk
Frankenscript said:
Yeah. I've been back to stock a couple times with Odin. I've got the process down pat! I prefer the hyperdrive rom if I can work through the few small warts. It's just such an elegantly crafted piece of work. Worth the effort, if I eventually sort out the call issue. Appreciate your help.
Sent from my SCH-I337 using Tapatalk
Click to expand...
Click to collapse
i got the same problem too. We'll get it figured out!
Damani311 said:
i got the same problem too. We'll get it figured out!
Click to expand...
Click to collapse
I figured out the clock on status bar thing. Like someone else said it was under the alignment options ... hidden by default. One by one warts going away.
Sent from my SCH-I337 using Tapatalk
Have the same issue here ..can't dial vm..on hyper
Sent from my SCH-I545 using XDA Premium 4 mobile app
jshua said:
Have the same issue here ..can't dial vm..on hyper
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you haven't done so yet i suggest noting the issue in the hyper thread ... either the Verizon or att one depending on your phone. Seems to be a bunch of us... more folks report it the common thread will emerge.
Sent from my SCH-I337 using Tapatalk
Same issue here i can not dial voicemail and can not call a number back without typing the number in manually. Deal breaker for me hope it gets fixed soon so i can go back to Hyperdrive. Or somebody comes up with some sort of fix.
Download Prefixer and remove the + for outgoing call
BBG037 said:
Download Prefixer and remove the + for outgoing call
Click to expand...
Click to collapse
When I get back from vacation I will have to try this. Thanks!
Related
As we all know Gingerbread has been in the oven... And I was one of those people who could not wait for it to cool off. As soon as I saw the leak early saturday morning, I was already downloading. what could go wrong, right? I odin'd the ef02.tar, started her up and wow, she's beautiful, save the extra ugly 4g symbol in the window sill (notification bar) that looks even worse now than previous desserts.
Keep in mind this is a stock .tar. No root. No cwm. No nothing. Except bloat. Low and behold my beautiful lil girl had a very serious functionality flaw. After my first reboot, no more incoming phone calls :^(...
So I've tried everything, I gained root, installed cwm 3.1.0.1 wiped data, cache, dalvik multiple times. Re odin'd the .tar. Flashed Decad3nce's odexed and deodexed roms. Updated modems. Tried frozen on ec05, took a shot at simply AOSP, odin'd a stock ec05, even went all the way back to eb13, with cwm 2.5 (changing file systems when needed) now I'm back to a bone stock ec05 from the stickies in development... Still no incoming phone calls. I called sprint technical and they were unable to resolve the issue.
Funny thing is I can make calls, I have data (3&4g), I can text, just won't receive.
Has anybody else seen anything remotely close to this. If so please comment, if not, comment anyways. I wanna get some opinions on my situation.
P.S. feel free to laugh at my short comings, lord knows just thinking about it brings chuckles to my mind...
Sent from my Epicly Failing Samsung Galaxy Player using Tapatalk
Something kinda similar is happening to me. It was after flashing marcusaunts i1 rom, i lost the ability to receive texts, i can send them though. Im not sure if i can make calls, but i can receive them. i have to press one to accept every call though. Im calling sprint soon, its been like this for 3 days.
Have you tried reprovisioning under Settings>About Phone>System Updates>update profile
spitefulrain said:
Something kinda similar is happening to me. It was after flashing marcusaunts i1 rom, i lost the ability to receive texts, i can send them though. Im not sure if i can make calls, but i can receive them. i have to press one to accept every call though. Im calling sprint soon, its been like this for 3 days.
Click to expand...
Click to collapse
Sound looks you installed google voice, theres an option in the website to change that... But if I were you I would be happy I'm just getting calls...
Sent from my SPH-D700 using Tapatalk
NEXUS 4G said:
Sound looks you installed google voice, theres an option in the website to change that... But if I were you I would be happy I'm just getting calls...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Mine has been perfect. Calls, texts, GPS, Netflix, everything. I'm on EF02 with the EF10 modem and I updated PRL also.
NEXUS 4G said:
Sound looks you installed google voice, theres an option in the website to change that... But if I were you I would be happy I'm just getting calls...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
You know, i did install google voice. But ive installed it multiple times until now, so i figured it was unrelated. But this past time it did take my texts through there, which had never happened before. thats why i uninstalled it. Im gonna check that out and see if it fixes it. Good luck with your issues.
Sounds like you clicked yes to Sprint integration (ports your number temporarily to google). So they go to your google voice account, however you can check an option to have them sent also to your phone as well (although if you do this with google voice installed you will probably get 2 notifications per 1 sms). Also call screening is an option that is enabled by default, option in google voice (desktop web interface). I had to turn that off too (the press 1 thing). Hope this helps, its just options. Also you could go online and disable the integration and go back to normal.
EDIT: Also make sure your phone is listed to receive calls in the web interface (via a desktop). I know it should do this by default but maybe it didn't for god knows what reason?
compuw22c said:
Sounds like you clicked yes to Sprint integration (ports your number temporarily to google). So they go to your google voice account, however you can check an option to have them sent also to your phone as well (although if you do this with google voice installed you will probably get 2 notifications per 1 sms). Also call screening is an option that is enabled by default, option in google voice (desktop web interface). I had to turn that off too (the press 1 thing). Hope this helps, its just options. Also you could go online and disable the integration and go back to normal.
EDIT: Also make sure your phone is listed to receive calls in the web interface (via a desktop). I know it should do this by default but maybe it didn't for god knows what reason?
Click to expand...
Click to collapse
Thanks. Nothings back to normal yet though.
poit said:
Have you tried reprovisioning under Settings>About Phone>System Updates>update profile
Click to expand...
Click to collapse
Yup and prl too
Sent from my SPH-D700 using Tapatalk
compuw22c said:
EDIT: Also make sure your phone is listed to receive calls in the web interface (via a desktop). I know it should do this by default but maybe it didn't for god knows what reason?
Click to expand...
Click to collapse
I clicked desktop version from my phone but didnt see an option to choose phone recieves calls. Can u be a lil more specific. Or do i actually have to use a computer
Sent from my SPH-D700 using Tapatalk
Uninstalling it won't do anything. You must deactivate it via voice settings at voice.google.com frm a pc. (Or dolphin w desktop ua)
compuw22c said:
Uninstalling it won't do anything. You must deactivate it via voice settings at voice.google.com frm a pc. (Or dolphin w desktop ua)
Click to expand...
Click to collapse
Well well well my friend, seems like i'm the idiot, and your the genius. I tried doing it on opera and the stock browser and could click on the gear on the top right corner, but never get into the settings section. Just did it from dolphin and boom. Going to the xda site right now to say thx
Sent from my SPH-D700 using Tapatalk
compuw22c said:
Uninstalling it won't do anything. You must deactivate it via voice settings at voice.google.com frm a pc. (Or dolphin w desktop ua)
Click to expand...
Click to collapse
I had disabled it, it just took a bit. but its all working again Thanks so much man.
I remember when I did that... Sat there for an hour pulling out my hair before I realized I needed to click the number on the right side of the GoogleVoice Page to change the settings. Not my proudest moment.
Yea, I think if multiple people on smart enough to flash a rom get confused I think google needs to make thinks a bit easier to understand. Glad I could help.
The GV set up options really suck. i already have a gv number and always have to go into the desktop voice application and disable the integration.
compuw22c said:
Yea, I think if multiple people on smart enough to flash a rom get confused I think google needs to make thinks a bit easier to understand. Glad I could help.
Click to expand...
Click to collapse
I just came back from the sprint store, and none of there techs could give me anything in depth about google voice. They just said it was beta and somewhat "finneky" however my phone works perfect now. I had to use a pc at the store while I was warranting my samsung dock (fyi don't use desk dock with any charger other than tge one provided)
I have searched for this on the xda app, no luck.
Has any one been able to get this to work I am using a ported mexdroid, and can't see any of my voice mails. I have called my self from work ans left a voice mail its not showing, so any help will be nice. Thank you.
Sent from my glaicer melting due to CPU warming
Do you have the VVM service add-on activated for your account?
Ya I do that's the pain in the ass part, I was talking to a tech and asked him should being rooted have any affect and he said it shouldnt cause he has a rooted phone also and works on his.
Sent from my glaicer melting due to CPU warming
andrewdoessuck said:
Ya I do that's the pain in the ass part, I was talking to a tech and asked him should being rooted have any affect and he said it shouldnt cause he has a rooted phone also and works on his.
Click to expand...
Click to collapse
Yeah, I've used VVM on multiple rooted phone models running several different ROMs and never had an issue. My guess is it's a problem with your T-Mobile account settings. In my experience, just because one rep didn't see a problem doesn't mean there isn't one.
It's because you do not have the Voicemail number. It's empty in AOSP.
Go to Settings>Call Settings>Voicemail Settings
Then set VM number to "123"
Now go to dial pad and long press "1" to call voicemail, once you have the VM number copy it or write it down exactly what it says, even the "+" symbol.
Go back to VM settings and replace "123" with the VM number you just copied.
Now go to Visual VM and it should be working fine now. Let me know if that worked. Works for me every time I use AOSP.
mackster248 said:
It's because you do not have the Voicemail number. It's empty in AOSP.
Click to expand...
Click to collapse
That's good to know. I'll keep that in mind when I switch to AOSP from Sense. You know...when the sky falls...
TeeJay3800 said:
That's good to know. I'll keep that in mind when I switch to AOSP from Sense. You know...when the sky falls...
Click to expand...
Click to collapse
Haha! I'm sure once Ice Cream is upon us via CM8, you'll make the inevitable switch.
I always added my vm number but never thought of doing the 123 learned that at cm7. Will try that and report back
Sent from my glaicer melting due to CPU warming
Ok I did what you said to the tee, no luck. So I decided to uninstall and reinstall it. I checked market and well I can't find it there any one else have this issue?
Sent from my glaicer melting due to CPU warming
REDACTED
FaultException said:
To participate in this poll, download the LATEST CM9 nightly from here, keep everything stock, no kernel changes, framework, or build.prop mods. Follow the instructions in this post, if it fails, do what it says in the post, and provide me with that dumpstate file (via a PM, do not post it here).
* By "completely stock" in the poll question, I mean completely stock CM9, not the stock Android that came with your phone.
* By submitting a poll choice, you agree that you are running COMPLETELY VANILLA CM9; STOCK KERNEL; STOCK FRAMEWORK; STOCK BUILD.PROP
Click to expand...
Click to collapse
For this test, do any of your updated GPS kernels count as stock?
Thanks.
salazar.r1 said:
For this test, do any of your updated GPS kernels count as stock?
Thanks.
Click to expand...
Click to collapse
Yes they do.
Awkward experience, I tested it with my first Vibrant (I have 2) and it didn't work, so i voted The call failed. Then i thought about it, and tried it with my other Vibrant, and returned it to stock CM9, and it worked. Unfortunately the call supporter i got was a big **** about me calling to check in if my location was posted etc. So i didn't call multiple times, but the first time i called with second Vibrant, it worked.
I honestly think its just random for this to happen.
xriderx66 said:
Awkward experience, I tested it with my first Vibrant (I have 2) and it didn't work, so i voted The call failed. Then i thought about it, and tried it with my other Vibrant, and returned it to stock CM9, and it worked. Unfortunately the call supporter i got was a big **** about me calling to check in if my location was posted etc. So i didn't call multiple times, but the first time i called with second Vibrant, it worked.
I honestly think its just random for this to happen.
Click to expand...
Click to collapse
You didn't reboot after the call on your first Vibrant did you? Get me that dumpstate file...
I said in the OP if it fails get me the file
My bad, I actually already flashed another ROM.
I'll get back onto you with that possibly tomorrow. Busy studying for a test tomorrow, so I may get back to you on that. I'll call them again.
xriderx66 said:
My bad, I actually already flashed another ROM.
I'll get back onto you with that possibly tomorrow. Busy studying for a test tomorrow, so I may get back to you on that. I'll call them again.
Click to expand...
Click to collapse
No problem, it's just important to get that file when it does fail, so I can take a look. I raised the note to red letters and a bigger size, so hopefully everyone else that tries will see it.
FaultException said:
To participate in this poll, download the LATEST CM9 nightly from here, keep everything stock, no kernel changes, framework, or build.prop mods. Follow the instructions in this post.
If it fails, provide me with a dumpstate file (via a PM, do not post it here).
The instructions on how to get that file are also in the above link.
* By "completely stock" in the poll question, I mean completely stock CM9, not the stock Android that came with your phone.
* By submitting a poll choice, you agree that you are running COMPLETELY VANILLA CM9; STOCK KERNEL; STOCK FRAMEWORK; STOCK BUILD.PROP
Click to expand...
Click to collapse
Can the dumpstate file be created with terminal? I want to help test, but adb is somehow not working for me. Is there some way that I can produce the file using only commands on my phone?
Thanks,
I tested and reported success in the poll.
I discovered one thing in my testing - it may be of interest to other testers.
I use the "dialer one" app to dial phone numbers. When I dialed 911 and pressed the "call" button, the call did not directly dial - instead I wound up at the built in dialer screen. On the dialer screen "911" was in the number display, and I had to press the "call" button on the build in dialer to actually make the call. Typically a second press of the "call" button is not required to make a call.
Bottom line - when testing 911, if there are any unexpected results, make sure that there is not another dialing application involved in the process. Similarly if there is a real emergency you may want to just use the real dialer.
I hope this is helpful (feel free to leave a thanks if it is
ewillner said:
Can the dumpstate file be created with terminal? I want to help test, but adb is somehow not working for me. Is there some way that I can produce the file using only commands on my phone?
Thanks,
Click to expand...
Click to collapse
Yes:
Code:
su
dumpstate -o /sdcard/CM_dumpstate.txt
ewillner said:
I tested and reported success in the poll.
I discovered one thing in my testing - it may be of interest to other testers.
I use the "dialer one" app to dial phone numbers. When I dialed 911 and pressed the "call" button, the call did not directly dial - instead I wound up at the built in dialer screen. On the dialer screen "911" was in the number display, and I had to press the "call" button on the build in dialer to actually make the call. Typically a second press of the "call" button is not required to make a call.
Bottom line - when testing 911, if there are any unexpected results, make sure that there is not another dialing application involved in the process. Similarly if there is a real emergency you may want to just use the real dialer.
I hope this is helpful (feel free to leave a thanks if it is
Click to expand...
Click to collapse
Maybe Dialer One defers the 911 call to the standard dialer just to be safe.
Just thought I'd throw this out there for anyone who's not getting notifications for their carrier voicemail. This fix worked for me and was a little hard to find. It should work for all CDMA phones (the string is not present, nor is a similar string on my T-Mobile SGS3). I take no credit for the actual fix. Requires root (does that even need to be said?).
Possible fix:
There could be a string missing in a settings file, /data/data/com.android.phone/shared_prefs/com.android.phone_preferences.xml
<string name="vm_number_key_cdma">##########</string>
Click to expand...
Click to collapse
Where ########## is your 10 digit phone number.
If you just edit that file (make a back up if you want to be safe) and add the line above somewhere between the <map> </map> XML tags, replacing the ########## with your phone number (no dashes or parentheses), then reboot, you should be getting notifications again.
Check out the source for more info.
Source:Phandroid
The file doesn't appear for me even if I leave a voicemail
Sent from my Galaxy Nexus using Tapatalk 2
Scratch that. I find the file but a reboot doesn't get the voice mail icon to come back. If I go into the file again it says there is a voice but no notification pops up.
Sent from my Galaxy Nexus using Tapatalk 2
Has anyone figured out this issue yet? I tried the suggested fix above but it doesn't work for me either. I'm running 4.2.2 Carbon ROM on a Samsung Fascinate and do not get any notifications when I have voicemails. I've searched around this forum and google as well and there isn't too much information on this issue. Some say it's a known issue in all recent 4.2.2 ROMs, some say it's in all AOSP-based ROMs, etc... Anyone out there know of a fix?
sp1k3s said:
Has anyone figured out this issue yet? I tried the suggested fix above but it doesn't work for me either. I'm running 4.2.2 Carbon ROM on a Samsung Fascinate and do not get any notifications when I have voicemails. I've searched around this forum and google as well and there isn't too much information on this issue. Some say it's a known issue in all recent 4.2.2 ROMs, some say it's in all AOSP-based ROMs, etc... Anyone out there know of a fix?
Click to expand...
Click to collapse
I have had the issue for as long as I can remember it seems, no matter the rom. Its to the point I expect it and/or just have learned to accept it. I don't get that many lately for it to be a huge huge deal besides the whole job hunting process lol Tried prolly most things things have popped up over time but no solid fixes. With messing around I can get it to pop up a few times and it is always delayed or random when it does and it will also stick in the status bar for a bit even after clearing any unread till it randomly goes away or I clear the responsible/corresponding system apk's data. and that be the most I ever see of it, a downfall i guess & either you deal with it or your don't I suppose. Your not alone brotha lol
Voicemail fixed in Gee-Wiz rom
LasVegasRomeo said:
I have had the issue for as long as I can remember it seems, no matter the rom. Its to the point I expect it and/or just have learned to accept it. I don't get that many lately for it to be a huge huge deal besides the whole job hunting process lol Tried prolly most things things have popped up over time but no solid fixes. With messing around I can get it to pop up a few times and it is always delayed or random when it does and it will also stick in the status bar for a bit even after clearing any unread till it randomly goes away or I clear the responsible/corresponding system apk's data. and that be the most I ever see of it, a downfall i guess & either you deal with it or your don't I suppose. Your not alone brotha lol
Click to expand...
Click to collapse
Voicemail indicator worked in 4.1.x, but broke in 4.2.x. there is only one ROM - GEE-WIZ, where the dev actually figured out what was wrong and fixed it. It is now my daily driver, although I miss some of the AOKP features. None of the other developers have picked up the fix and implemented it in their ROMs. The voice mail indicator problem has to do with the code looking for a SIM card and not finding it. Eveyone else seems content with using google voice as a work around, I don't find that a good solution, except when I want a few laughs from bad transcriptions.
I just wanted to say that this actually sort of got notifications working for me again. I'm using a Droid Incredible 2 running PAC 4.2.2, and ever since upgrading to it, I would not receive voicemail notifications.
I made the appropriate change to the file, rebooted, left a voicemail in my box, rebooted again, and I had a notification saying that there was a message waiting!
The reason I say "sort of working" is because I didn't receive the notification while waiting directly after leaving the message. Normally, I'll receive a new voicemail notification within a minute of one being left. But, I suppose this is better than nothing.
If any new developments or fixes are found, please update this thread!
Its still broke. Voicemail notification has always come up after a reboot but that is of no use. This is not an improvement.
Is there anyone working on this?
Or close to being done?
ForceRom has them on the to do list.
But im not sure on progress.
anyone have any updates?
Also I know some international roms have in app call recording toggle, is there anyway to port that for sprint? I dont see why it wouldnt work since it has nothing to do with the phone radio. Im guessing it the rom it will just be the secphone.apk? If someone confirms that ill give it a shot and report back.
I, too, really want the Call Recorder function but it seems like either no one on the Sprint side knows how to implement it or don't care enough about it. I know the Wanam rom for the i9505 has Call Recording enabled. You could flash that rom & get it. Just follow the tutorial for installing ROMs from other S4's to our S4.
optimummind said:
I, too, really want the Call Recorder function but it seems like either no one on the Sprint side knows how to implement it or don't care enough about it. I know the Wanam rom for the i9505 has Call Recording enabled. You could flash that rom & get it. Just follow the tutorial for installing ROMs from other S4's to our S4.
Click to expand...
Click to collapse
do you have a link to that to tutorial?
So I decided im going to try using thee Wanam Lite secphone.apk, and push it to Force Rom.
I am downloading Wanam right now, so when I get done ill report back and let yall know if it worked or not.
It will be super awesome if this works, because I know many sprint users would love to have call recording,
and this should be a pretty simple process.
com.sec.phone kept crashing over and over. and I had no signal.
shuld I get the com.sec.phone from wanam also?
Another Sprint S4 user had success & got Call Record working by flashing the entire Wanam ROM. The tutorial has been deleted, it seems. If I remember correctly, you're supposed to flash the Wanam ROM then flash a Sprint S4 kernel right after in the same session.
Perhaps create a nandroid first then try? If I remember that user's name, I'll let you know or maybe he'll chime in here.
optimummind said:
Another Sprint S4 user had success & got Call Record working by flashing the entire Wanam ROM. The tutorial has been deleted, it seems. If I remember correctly, you're supposed to flash the Wanam ROM then flash a Sprint S4 kernel right after in the same session.
Perhaps create a nandroid first then try? If I remember that user's name, I'll let you know or maybe he'll chime in here.
Click to expand...
Click to collapse
I dont mind flashing it, but the thing is i saw a thread talking about it and apparently people still couldnt get data after, even after they flashed the sprint kernel. Also read it needs to be a touchwiz kernel.
i flashed it, and its working great. everything works on it except for data.
so can anyone help me out with the apns?
and where do I enter the apn settings on the gs4?
chase357_501 said:
i flashed it, and its working great. everything works on it except for data.
so can anyone help me out with the apns?
and where do I enter the apn settings on the gs4?
Click to expand...
Click to collapse
Exactly
I posted this in another thread, not sure if it works. My guess is that you'd have to copy the settings from a Sprint ROM and then manually input them after flashing an I9505 ROM.
http://www.phonebuff.com/2012/07/configure-apn-settings-for-android/
You should be able to get to some if not all of those settings, by dialing ##3282##. You will need to enter your MSL number. There is a thread here in the Sprint forum, on how to get your MSL. I used, get my MSL from Gplay and it worked. Just follow the directions Once in, right down all of the settings and then put those settings in, once the different carrier's rom is installed. Good luck, and let us know the outcome
cerj said:
You should be able to get to some if not all of those settings, by dialing ##3282##. You will need to enter your MSL number. There is a thread here in the Sprint forum, on how to get your MSL. I used, get my MSL from Gplay and it worked. Just follow the directions Once in, right down all of the settings and then put those settings in, once the different carrier's rom is installed. Good luck, and let us know the outcome
Click to expand...
Click to collapse
1st of all, my main problem, was finding the apns in the wanam rom. I was able to find them in the sprint rom, because ##data# works. but when you go to the i9505 rom, that dial code does not work. I actually ended up getting access to the aps by using an app from gplay, called offline sim apn database. it has an option that opens up your apn list, and from there you can edit them, so I took all 4 of my sprint apn's, and entered them. there was 2 lte apn's and 2 ehrpd apn's. Well after high hopes, that was all I had. nothing happened. so there is definitely more than just entering apn's. I messed around with *#0011# for like 2 hours, trying to figure something out, but I got no results. so imo, we will just have to wait til something gets figured out. I personally am stuck for now,
chase357_501 said:
1st of all, my main problem, was finding the apns in the wanam rom. I was able to find them in the sprint rom, because ##data# works. but when you go to the i9505 rom, that dial code does not work. I actually ended up getting access to the aps by using an app from gplay, called offline sim apn database. it has an option that opens up your apn list, and from there you can edit them, so I took all 4 of my sprint apn's, and entered them. there was 2 lte apn's and 2 ehrpd apn's. Well after high hopes, that was all I had. nothing happened. so there is definitely more than just entering apn's. I messed around with *#0011# for like 2 hours, trying to figure something out, but I got no results. so imo, we will just have to wait til something gets figured out. I personally am stuck for now,
Click to expand...
Click to collapse
If you decide you really want to do it, check around XDA for Rom porting threads. There are a few easy to follow TUT's on this. They may just get you where you wanna be
Stock TW has a flashlight widget called "Assistive Light" that is built in and super quick.
Sent from my SPH-L720 using Tapatalk 2
For a flashlight toggle, I'm using "Mappz Quick Settings" from Play Store. It gives you AOSP-style Quick Settings tiles, including one for Torch, that you get by pulling down from the center of the top. If you pull down from the top left or top right you get the regular TW Quick Settings and Notifications.
The "Torch" moment's likely csn be interested into the Lockscreen and prolly added to the notification tray. I'm hoping to finish the toggle for turning on/off the am/pm & Time today. I'll look I to the Torch toggle this afternoon.
Sent from my SPH-L720 using Tapatalk 2