Simple question. Does the stock GB on the Bionic have the integrated SIP stack stripped from the OS or not? This is more important to me now with all the rumors of Verizon tracking / limiting rooted users. If I'm forced to use the stock OS then what other liberties did these clowns take to try to prevent me from doing things they don't want? (e.g. backing me into a corner so I still have to pay their ridiculous voice service charges)
This might be the time I decide to cancel my Verizon altogether and go with TracFone + Galaxy WiFi Player (use VoIP when in WiFi range, otherwise use backup prepaid phone). Buncha greedy jerks.
Can someone who owns the phone already check this for me? Should be able to tell by going to "Settings -> Call Settings" and looking for an "Internet Calling" configuration section. If it's not there then they likely stripped it from the OS.
Thanks!
MIA. Looks like it's been stripped.
there are better alternatives anyway - like sipdroid - i wouldnt let the lack of GB native VOIP hinder your decision. Just my thoughts
thanks guys!
to the point about external apps offering SIP support. yes, you're right, but there are numerous advantages to using the native SIP stack vs external apps like sipdroid.
a few come to mind:
* sipdroid/csipsimple has some hardware/driver issues on some phones and makes it hard to work around them at the software level.
* i've found the NAT punching/traversal these programs offer is sometimes lackluster (do they even use libjingle?) making my voip inoperable on public wifis without special port trigger setup or putting my phone in a DMZ.
* it's nice having the SIP stack integrated into OS so it's fully supported by the native dialer and other phone functions
so, i do have interest in making sure my next purchase has this feature. i'm also not sure i'm willing to sign a 2 yr commitment with a provider that limits which features i can use in the OS... that seems to be their power trip going a bit too far.
FYI -
I just got done trying the Galaxy S2 fix for this (see thread http://forum.xda-developers.com/showthread.php?t=1109962) where you add the android.software.sip.voip.xml back to the system\etc\permissions folder but it did not bring the feature back. Looks like Motorola was more effective than Samsung in their stripping of the feature.
jeffason said:
Looks like Motorola was more effective than Samsung in their stripping of the feature.
Click to expand...
Click to collapse
This feature disabled in BlurPhone. It is hardcoded as mSipSupported = 0 and no way to activate it.
i'm trying to re-enable this by editing blurphone.apk. i see in phoneapp.smali constructor this code:
Code:
.line 299
iput-boolean v1, p0, Lcom/android/phone/PhoneApp;->mIsSipSupported:Z
now, how do i change it to set the field to true instead of false? (sorry, i'm new to this)
Man I reallly hope someone has some luck with this - it's the only thing about the Bionic I have a problem with...ha
i tried changing the dalvik opcodes myself to force mIsSipSupported to true, then recompiled, resigned, and pushed to my system files but it crashes (force close) everytime it tries to access the BlurPhone.apk functionality now =(
not sure what approach should be, maybe someone has more info they can chime in with regarding modifying this .apk without it crashing
I'd love if someone figured this out I used to use CSIP SIMPLE and Google Voice Call back, which worked great, but having those running in the background was juicing my battery like no other. Hope someone can find a native SIP workaround!
I made a post/request in the developer forums @ http://forum.xda-developers.com/showthread.php?t=1322163
I'm ponying up $20 to a dev that can restore SIP support in a couple different ways on the Bionic. If this feature is valuable to you then join me by pooling in some funds for a dev to help us out!
Hope we will have a solution soon!
Related
I'm sorry if this has already been debated elsewhere. I did search and try to locate threads on this already, but didn't come up with anything which (seemed) relevant to this problem.
If anyone has a link handy for another thread which already discusses this, I'll close the thread if that is wanted.
With that said... Here's my issue.
As stated elsewhere, one of the main things which excited me about Gingerbread was the ability to do native SIP dialing. About time, I say! Now I've flashed Gingerbread on my SGS and so far the results has been below underwhelming.
From what I can tell this is how you get SIP/VoIP/Internet calling on your phone using Gingerbread:
1. Sign up for Google Voice.
2. Install Google Voice and sign in.
3. Voila. Your Gingerbread Android-device now has a bunch of SIP settings and options.
This is ofcourse, unless your manufacturer has somehow crippled your phone's software.
That might be the case with Samsung's firmware, but I wouldn't know because the steps outlined above is absolutely impossible for anyone outside the US. You cannot sign up for Google Voice anywhere else. End of story.
So. Is this for real? Did Google release a smartphone OS for worldwide consumption, touting "native SIP", native internet calling as feature and then implement it in a way which means it will only work in one country, all else be damned?
I seriously find this very hard to believe. There has to be a way to get this functionality up and running otherwise. Seriously? The internet maestros at Google implements a core OS-level function tied to (one) geo-location? Is third-party solutions ala Sipdroid the solution for everyone else?
So... Please tell me I am completely mistaken and that there are steps for getting SIP running on my phone, despite me not have an adress of residency ending in "US".
Any hints or links in any direction so that I can actually get to try this out would be über appreciated.
Bump.
I realize posting this while Europa were getting ready for sleep and only US-people were around might have been bad timing.
Just bumping this again to see if there's any more response. I can't seriously be the only one wondering about this.
If bumping is severely against forum policies, let me know and I'll make a note of it and wont do it again.
http://forum.xda-developers.com/showthread.php?t=1043016
Use this zip as an update from CWM recovery, enables the menu "Internet call settings" under "Call settings".
Works on odex and deodex ROMS [I have the same JVB as the OP]
Problem solved
Thanks Vinnie.
Since I already have some framework-res.apk dependent mods, I just pushed the permissions-file as mentioned in that thread, and now I have "Internet calling options" available.
Yes, I realize this will only work while on wifi and SIP over 3G will be disabled, but at least it gives me something to experiment with so that later I will know if handing over my other mods for 3G VoIP/SIP will be worth it.
Thanks for the response and handy link. Now if XDA had better search, I might not have needed to pollute the forums with duplicates like this
Edit: Checked the entire thread and saw that there is an update.zip with eyecandy as well. Will try it out later.
Hi folks,
I'm looking for someone who can either provide a guide for replacing existing BlurPhone.apk with .apks that work with the native gingerbread SIP stack OR someone who successfully hacks BlurPhone.apk so mIsSIPSupported is not hard-coded to false.
I personally will provide $20 Paypal payment to anyone who is the first to do either of these two things. I've been patiently waiting for ROM releases on this phone only to find out that all the options we currently have still utilize the stock BlurPhone app...
Anyone else who would like to offer bounties for this accomplishment please chime in here.
Thanks!
MODERATOR MESSAGE
XDA accepts no responisbility of a scam of any sort.
No offense intended to anyone, just a disclaimer.
This is actually a HUGE thing for me - so I'll toss in $20 too.
Dumb question: Would this just be standard SIP support that I remember Google talking about 12 months ago, or would this also include the ability to use Google Voice right in the OS?
Google Video Chat works ridiculously well so I can only imagine how well Google Voice calls would sound (requires less bandwidth) if it was built right into the OS. As it stands, I use GrooveIP and it is always very frustrating to the recipient of my call.
this request is specifically about the functionality disabled by motorola in blurphone.apk
bump...
anyone? anyone?
Very much needed
I will also be willing to put in money if this gets done. What was Motorola thinking taking it out?
good news...new ICS CM9 has working built-in sip ..whoot
It's supprising how few people use sip at least those who own Razri. I found it very useful and money saving, especially when travelling.Unfortunatelly Razri uses proprietary phone.apk as a part of Motoblur and Motorola stripped off the entire Internet calling part from the application. It was the case in previous ICS and it remains in JB. Other manufacturers which opt for the similar solution use predictive way to remove android.software.sip.xml from the system and change sip value to false in framework-res.apk. But not Motorola. It obviously used more sophisticated approach. Both above mentioned files remains intact as far as the sip is concerned.
There is an application on the Google Play named Sipswitch which enable widget to enter voip credentials. In previous ICS you couldn't activate the connection. Suprisingly with JB the system accepts the credentials and communicates with the VOIP provider. And the SIP app appears as an extension of the Motorola Phone.apk. But unfortunatelly the SIP is not triggered though it is enabled. There is still the missing link remains. Is the failure result of the fact that Sipswitch is not the system application?
I'm aware that there are many SIP applications on the market. I tried most of them but with Razri they have voice issues. I have best experience with native Voip from previous phones. Does someone else plays with SIP or has otherwise useful advice how to proceed?
piskr said:
It's supprising how few people use sip at least those who own Razri. I found it very useful and money saving, especially when travelling.Unfortunatelly Razri uses proprietary phone.apk as a part of Motoblur and Motorola stripped off the entire Internet calling part from the application. It was the case in previous ICS and it remains in JB. Other manufacturers which opt for the similar solution use predictive way to remove android.software.sip.xml from the system and change sip value to false in framework-res.apk. But not Motorola. It obviously used more sophisticated approach. Both above mentioned files remains intact as far as the sip is concerned.
There is an application on the Google Play named Sipswitch which enable widget to enter voip credentials. In previous ICS you couldn't activate the connection. Suprisingly with JB the system accepts the credentials and communicates with the VOIP provider. And the SIP app appears as an extension of the Motorola Phone.apk. But unfortunatelly the SIP is not triggered though it is enabled. There is still the missing link remains. Is the failure result of the fact that Sipswitch is not the system application?
I'm aware that there are many SIP applications on the market. I tried most of them but with Razri they have voice issues. I have best experience with native Voip from previous phones. Does someone else plays with SIP or has otherwise useful advice how to proceed?
Click to expand...
Click to collapse
Nobody engaged with the SIP? OK, since I'm not a programmer I'm kindly asking developers to take a close look to the attached applications. The first is Motorola's Blur Phone.apk, the second is original ICS Phone.apk. My question is: supposed I root the phone, if I delete Blur Phone.apk and install the original one (which has SIP option included) into the system, do I solve the problem or this is not the appropriate method? Perhaps because of diferrent apk frames or something else? Or must I replace the appropriate (original) Contact.apk as well? Thanks.
Aw: [q] sip/voip
Hi, i have the same problem. I'd like to use my VoIP number with the standard phone app.
I hope that someone can help with this.
Sent from my XT890 using xda app-developers app
me too!
Hi,
I have same problem (ThL W8 phone JB4.1.2 with mt6589 cpu) great phone, but SIP capability has been crippled somehow. Its in the framework-res.apk and the other setup files are there, it seems to be in the code for phone.apk, but there is nothing visible in the menu's and the SIP tester app reports no sip or voip capability. I'd love to know what has been done and how to undo it. It seems somebody has spent quite a lot of time and effort hiding this capability and the only reason I can see is bowing to pressure from the 'airtime sellers'.
I hope someone will point us in the right direction and soon.
gmincca said:
Hi,
I have same problem (ThL W8 phone JB4.1.2 with mt6589 cpu) great phone, but SIP capability has been crippled somehow. Its in the framework-res.apk and the other setup files are there, it seems to be in the code for phone.apk, but there is nothing visible in the menu's and the SIP tester app reports no sip or voip capability. I'd love to know what has been done and how to undo it. It seems somebody has spent quite a lot of time and effort hiding this capability and the only reason I can see is bowing to pressure from the 'airtime sellers'.
I hope someone will point us in the right direction and soon.
Click to expand...
Click to collapse
Well, you missed the forum, but regarding your problem it is not quite the same as here. If the SIP tester doesn't recognize the necessary conditions for SIP, you can try this method: http://forum.xda-developers.com/showthread.php?t=1592890
Motorola as the most qualified phone company uses more sophisticated and dirty methods to screw its customers: the SIP tester does detect sip capability and all necessary files and settings are enabled. But the SIP part is simply stripped off from the core phone.apk.
If you don't dare to try the suggested method you could always use Keyyo voip which has been updated recently and works flawlessly: https://play.google.com/store/apps/...DEsImNvbS5rZXl5b21vYmlsZS5hbmRyb2lkLnZvaXAiXQ..
piskr said:
Well, you missed the forum, but regarding your problem it is not quite the same as here. If the SIP tester doesn't recognize the necessary conditions for SIP, you can try this method: http://forum.xda-developers.com/showthread.php?t=1592890
Motorola as the most qualified phone company uses more sophisticated and dirty methods to screw its customers: the SIP tester does detect sip capability and all necessary files and settings are enabled. But the SIP part is simply stripped off from the core phone.apk.
If you don't dare to try the suggested method you could always use Keyyo voip which has been updated recently and works flawlessly: https://play.google.com/store/apps/...DEsImNvbS5rZXl5b21vYmlsZS5hbmRyb2lkLnZvaXAiXQ..
Click to expand...
Click to collapse
Hi,
Thanks, but the whole point of my posting is because all of the sip information in post 1592890 is already in place, everything looks as though SIP should work, but SIP tester doesn't recognise sip or voip capability and there is nothing in the menus. As for sip/voip apps yes there are countless of them good and bad, but this capability is built into Android and I want to be able to use it as I did on my old 2.3.6 phone. I'm just completely lost as to how to get it enabled.
So thanks, but really not much help so far.
gmincca said:
Hi,
Thanks, but the whole point of my posting is because all of the sip information in post 1592890 is already in place, everything looks as though SIP should work, but SIP tester doesn't recognise sip or voip capability and there is nothing in the menus. As for sip/voip apps yes there are countless of them good and bad, but this capability is built into Android and I want to be able to use it as I did on my old 2.3.6 phone. I'm just completely lost as to how to get it enabled.
So thanks, but really not much help so far.
Click to expand...
Click to collapse
If you have both files set correct (SIP enabled in framework-res.apk and xml) than you have virtually the same problem as it is with RazrI. The core phone.apk is rebuild in the manner that the sip part is stripped off. I prefer native SIP too, regarding my previous experience is the best, but I'm afraid that the only solution in our case is to get AOSP Phone.apk (or similar with SIP as CM) and reconstruct the framework-res.apk accordingly. I'm not the programmer, I'm not sure if it could be done with this method or the whole system is to be replaced with AOSP or CM since Phone.apk is a core application cross related with a lot of other stuff.
What you can try eventually is to deploy two apps: SipSwitch Widget and Zeynalov's Call Manager (Google Play). Sip Switch Widget enables inserting your voip providers credentials and Call Manager supposed to serve as sip trigger. For me the combination wasn't work and I doubt that it would in your case since in your case sip is even not recognised as existed. But it cause no harm to give them a try.
Just use this method, works for me:
http://forum.xda-developers.com/showpost.php?p=24710862&postcount=2
Reposting from where I previously put this, on the suggestion that folks here might have more idea what I am talking about.
Yes, this is a question but I couldn't see that it fit in better to one of the other forums. If I am wrong please accept my apologies and redirect me, thanks.
I'm trying to work with a custom build of Android based on KitKat to incorporate a stylus, copying some of the functionality (though not code) from Samsung which sells Android-with-stylus builds for e.g. the Note 3. I'm not including details of the specific device because right now I am working on a custom dev device and my aim is to write code which is generic enough to be usable from any Android (based on KitKat). The build (written by others) already incorporates drivers and sends stylus events correctly as motion events etc. Programming at the app level I can receive onHover, onTouch, onClick etc
The specific functionality I am trying to achieve is to pick up a stylus-button-click while hovering. It's perfectly possible to do this in any app, using an onGenericMotion Listener.
However, I want to make my "stylus-action" have system-wide effect - so that anywhere (in any other app, or in the launcher or whatever) I will pick up the event (prior to any other app) and bring up my custom menu. (just like AirCommand in Samsung Note 3) I guess in my custom Android this would then make that particular action somewhat protected or unusable for other users, but I'm ok with that.
In older Android (prior to ICS) you could try something by putting up a System Overlay (i.e in regular app code, without hacking the ROM at all), but this is no longer possible.
This is not an attempt to tapjack or whatever, I understand why this functionality has been removed from the domain of the regular programmer, and I don't want to regress my ROM back to pre-ICS behaviour by allowing the System Overlay hack. Now I am programming the system (if my change is good enough I'd like to submit it back to AOSP) so I would like to know the best method to address this. Since Samsung have already done this, it must be legal (using legal in the terms of "Android will allow it"), and I want to do it right.
Is it possible to write something similar to the System Overlay when you are running from a system service? Or is there a good choke-point to capture events before they are broadcast to the current running apps?
I was looking at (sorry, not allowed to post links) AndroidXRef /frameworks/base/core/java/android/view/View.java specifically in the function dispatchHoverEvent() which looks like a promising place. My naive idea is that I would place code here checking the MotionEvent to see if the button is pressed and if it is, don't call any listeners and instead call my little menu app (or broadcast a custom message, or something anyway). However, I've never written code on the ROM level before (LOTS of experience writing app code) so I don't know if this is a really bad point or a good point to add in code. Should I be putting things at a higher level or a lower one? Will this capture all events or not? Is it all just trial and error?
If this is the wrong place to ask questions like this, please tell me where on XDA I should be asking it. If it's the right place - please answer
Thanks
Kibi
I have used Chroma in the past with minimal issues, but prefer the pure stock over a rom - so my question is; is there any way to use the Chroma Rom Dialer on the stock 5.1.1? (since I know there's several telephony, dialer, phonesky apps/files) I am not sure how I would go about doing that, or what all I would need to change in order to pull it off - if this is even possible at all?
Reason for my question, I like that it has BUILT IN native call blocking ability that the stock dialer doesn't, other than THAT feature it's identical to the stock dialer. I don't care if it's the Chroma dialer, or another rom dialer, I just want the STOCK dialer (or stock-like) to have this ability.
I know there's 3rd party apps for this type of thing, and I've used many of them, but I very much so prefer NOT to have to use a 3rd party app for something that (IMO) should have been built in to begin with.
If you wish to know why this is important to me, read the spoiler:
So, I get ~3-6 calls every day that's just the same BS; Scam calls saying I can lower my CC interest rates and to press 1 to speak to a representative. They always call from a different number, so blocking them individually doesn't work since it's never the same twice (typically - you'll understand after reading below). If you DO press 1 you get a rude person who will cuss at you, call you names, or laugh at you if you ask to be removed from their calling list. Doing that will only make it worse. I've recorded dozens of calls where they say really effed up things to me. Beyond harassment, it's straight up abuse.
I have been getting them for years, I DO NOT own a credit card, never have owned one, and have never even applied for one - plus there's THOUSANDS of pages on Google about these type of calls being a major problem. Even the FCC has a $50,000 bounty for anyone who can legally or illegally stop them - no questions asked (how badass is that!?) - THAT should tell you how hard they are to catch, find, or stop.
After more than 2 years of filing formal complaints/reports with the FCC, Local PD, FBI (as told to by the FCC), USCC, and have seeked legal advice from my lawyer as to getting this stopped via getting a subpoena so uscc has to release the real call origin trace, I'm on the Do Not Call list... - I've been met with ONE solution that has been common on all counts; change my number. That's not really an option, I've had this number since 1997, I'm not about to change it for obvious reasons.
Now, I've tried many apps to get this stopped, ranging from free to paid, and have not found one that ACTUALLY works toward getting it stopped, many are difficult to use or require WAY too much effort and personal information in order to do anything but ask you to donate.
So far I have logged (through Google Voice VM) a growing total of 566 *different* numbers they have called me from - from all over the US and some that are unused anywhere on earth.
In conclusion, Ive logged 566 different numbers that have called me a total of 11,925 times since 2008.
If that isn't justification for this request, then IDK what is. Shy of ditching my phone altogether, I'm out of ideas.
Bumping - I'd really appreciate any help, gents.
iRub1Out said:
Bumping - I'd really appreciate any help, gents.
Click to expand...
Click to collapse
Have no idea. If dialer would work would need boh contacts and dialer apk. Have no idea where the code for that mod is and if ASOP dialer will even work on stock. Then you have odex vs deodex to work through.
If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
As a side note, I've recorded several where I just screw with them for as long as I can - then put it on YT after they realize they've been trolled and blow up. It's a small, yet, satisfying "middle finger" I can do.
iRub1Out said:
If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
Click to expand...
Click to collapse
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.
prdog1 said:
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.
Click to expand...
Click to collapse
I concurr, your talking about taking apk's not meant for a certain rom and adding them in to pray it works. Did you look in the market t.o see if there was a KB you liked there? You can't just switch around apk's like that because you could easily get force closes. If you want to try just copy and paste it into a rom. you wont brick doing that, it may work
I know it isn't as easy as swapping apks - I had *hoped* it would be similarly easy, but figured there was no way.
Idk what the mod is, or how Chroma did it - but the dialer looks stock other than the addition of that option under the advanced menu in the dialer settings.
I've looked in the market, used many of them, Mr. Number was my go to for a long time but it is iffy on 5.1 as *sometimes* a call will get through for a couple rings then gets blocked. It would also block known contacts on a rare occasion, I would go a couple days without knowing I had missed a call from a family member because it didn't show up in Mr. Number or the stock dialer - somehow it blocked it and had no record of the call even coming in.
That's why I was hoping to find a way to get this option in the stock dialer - without porting anything or swapping apks, that way it's a native feature to the dialer and I wouldn't have to depend on 3rd party apps to do it.
I've asked Google, but their solution was to add them to one contact and send the calls to VM - while that essentially works, that means I'd have to add all 500+ numbers to a single contact, and they OFTEN call from spoofed numbers I've never seen before - so that really doesn't solve anything.