Related
First of all, while this is my first post, I have been a silent browser of xda for some time. This is such a wonderfull site.
My question is, is it possible to somehow get the settings for sideloading and usb/wifi teathering to show up in the settings menus? I assume that these have been removed or hidden somewhere in the source by commenting out or just been deleted. It seems to me that since these functions were built in to other android devices and I assume the I9000, that it sould be possable to reverse there removal. The settings.db has so many referances to other settings that are easily changed that it sould not require root access correct?
Now I must say that I am in no way a developer, and am not very good with linux. These are just some thoughts and conclutions that I have come up with while reading and pondering over countless articals on xda
Finaly , I want to say that I strongly disagree with Att's position on removing these items to increase there bottem line, and I would be with T-Mobile if they had good coverage in my house.
Usb tether is listed - called Pc internet. Sidwloading can be achieved by rooting and changing a settings.db file but no one has a fix for making it show up.
Sent from my SAMSUNG-SGH-I897 using XDA App
I am aware of the option to enable sideloading in the settings.db, all im saying is that there must be a way to but the option back in the settings menus. As for the USB teathering, isnt there an option on other devices to enable disable?
perhaps this thread would be better if it was moved to development?
djpittsford said:
I am aware of the option to enable sideloading in the settings.db, all im saying is that there must be a way to but the option back in the settings menus. As for the USB teathering, isnt there an option on other devices to enable disable?
perhaps this thread would be better if it was moved to development?
Click to expand...
Click to collapse
a) the sideloading thing is ATT and that will never show up in one of their phones (unless they somehow miss it) if you really want it THAT badly, you can flash eugene's vibrant hybrid and it's there
b) USB tether is directly available through the settings menu on stock firmware (looks like ATT missed it, because they had it removed in JH2 and JH3)
c) if you mean the WIRELESS (mobile access point) tethering, that was removed by ATT and we've already found workarounds to have it back.
d) this certainly does not belong in development, thanks for keeping it out of that forum
e) look at SRE, it contains basically all the things you're asking for
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!
Hi Everyone,
I understand SIP has been natively supported on Android for a while now. Is there a Google native application that I can download on my Nexus 7 tablet?
Thanks
GrooveIP
Sent from my Nexus 7 using xda premium
The native SIP client is in the Phone app, but I'm assuming that the Nexus 7 doesn't come with the Phone app?
AZImmortal said:
The native SIP client is in the Phone app, but I'm assuming that the Nexus 7 doesn't come with the Phone app?
Click to expand...
Click to collapse
Thanks for the feedback AZImmortal. You are right it doesn't come with Nexus 7. But isn't the phone app open-source? Can I not somehow get it on the nexus 7? copy and paste style But in all seriousness, I always wondered if the native dialer was customizable?
Thanks
I don't know what kind of customization you're looking for, but if you want a SIP client, you can use SIPDroid.
Groove_IP works great. All ya need is your google voice number and set it up to "chat only" and enter this info into Groove_IP. Very easy setup.
Sipdroid (with pbxes account) is a lot of work to setup but has lots more power. I have not tested Sipdroid/Pbxes on this tablet yet. :good:
If you use Google Voice, GrooveIP works incredibly well.
But you really need headphones or a bluetooth headset other wise it's a speakerphone.
Headphones?
BamAlmighty said:
If you use Google Voice, GrooveIP works incredibly well.
But you really need headphones or a bluetooth headset other wise it's a speakerphone.
Click to expand...
Click to collapse
Will an old iphone earbud set with the built in mic be functional in the N7 headphone jack?
AndroidMilos - Please don't spam for Groove IP. I don't intend to use Google Voice and your answer is not relevant.
Reason why I am after native SIP is because it's native - no bloat-ware...
Maybe this will help me:
Ref: http://forum.xda-developers.com/archive/index.php/t-1109962.html
You might want to see if any of the custom roms already have the Phone app included. If not, maybe you can ask the dev to include it and explain that it's for SIP calls. I believe that the link you referred to is for enabling SIP when the Phone app has it disabled, but since the Nexus 7 doesn't have the Phone app in the first place, I'm guessing you can't follow the thread. You should probably be able to extract it from another JB ROM and insert it, but I'm not sure how to go about doing that. You should give one of the non-native SIP clients a try before you go through too much trouble to see if it will do what you need.
SIPDroid
SIPDroid seems to work.
You can enable the phone app and the built in sip by editing the framework-res.apk file and changing "voice capable" from false to true.
This will enable the phone app however it will only allow you to add a SIP account at a density of 320.
So change the density to 320, reboot, add you SIP account, change the density again to whatever it was before and you got native sip working.
It works well on speakerphone but a little jerky with a BT headset.
If you don't know how to edit the framework-res.apk file let me know the ROM you are on and I will upload it for you.
Sent from my Galaxy Nexus using xda premium
I use sipdroid.
http://www.youtube.com/watch?v=N24HCaxoqYU
I use the Bria Softphone (by Counterpath). I actually work for a VoIP company, and we use the g729 codec, and that was the best client I could find for android that supported it. Granted it's somewhat costly. But it works very well for me.
clubtech said:
You can enable the phone app and the built in sip by editing the framework-res.apk file and changing "voice capable" from false to true.
This will enable the phone app however it will only allow you to add a SIP account at a density of 320.
So change the density to 320, reboot, add you SIP account, change the density again to whatever it was before and you got native sip working.
It works well on speakerphone but a little jerky with a BT headset.
If you don't know how to edit the framework-res.apk file let me know the ROM you are on and I will upload it for you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
How do I edit the framework apk? Any advice would be appreciated
Sent from my Nexus 7 using Tapatalk 2
Yes, I use Bria, excellent, alos, 'VOIP by antisip' works, also has video facility, Sipbdroid works too, I have tried them all, but Bria is superior by far ..... my opinion of course!
clubtech said:
You can enable the phone app and the built in sip by editing the framework-res.apk file and changing "voice capable" from false to true.
This will enable the phone app however it will only allow you to add a SIP account at a density of 320.
So change the density to 320, reboot, add you SIP account, change the density again to whatever it was before and you got native sip working.
It works well on speakerphone but a little jerky with a BT headset.
If you don't know how to edit the framework-res.apk file let me know the ROM you are on and I will upload it for you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hi there,
I'm on last Paranoid Rom, could you tell me how do i edit the framework-res.apk?
I love the native SIP of android, it's the best i've tried on my Nexus S.
Thks
pmauzao said:
Hi there,
I'm on last Paranoid Rom, could you tell me how do i edit the framework-res.apk?
I love the native SIP of android, it's the best i've tried on my Nexus S.
Thks
Click to expand...
Click to collapse
I realize you are looking for native, but I have to recommend CSIPsimple if you don't have any luck with native. Very good, open source and hardly even has an interface - it is very well integrated with the OS.
barryflanagan said:
I realize you are looking for native, but I have to recommend CSIPsimple if you don't have any luck with native. Very good, open source and hardly even has an interface - it is very well integrated with the OS.
Click to expand...
Click to collapse
I've tried both native and CSIPsimple im my Nexus S and the native is way much better, CSIPsimple has lot of echos and noises...
Do you know the best config for CSIPsimple?
I've been using Bria (a third party app by CounterPath) for years.
Yeah, it has some cons and costs money, but it has always worked well for me. It also supports g729 and video.
One thing to keep in mind for VoIP and phones/tablets is if you want to stay connected all the time, versus only occasionally when making calls, you need to use SIP over TCP vs UDP. Most clients/providers default to UDP since it has less overhead works fine on computers/servers/etc. Assuming you are running a VoIP server or client on a computer or phone, especially if it's on the local network, UDP would be the preferred option. The problem on battery powered devices is that it will drain them very quickly. In my testing, leaving the client connected constantly will shorten your overall battery life by about half.
However TCP is much more robust and capable of keeping sessions open through NAT (which your device will pretty much always be behind), and requires less client level activity to keep the session open (hence more deep sleep). As a result, since enabling SIP TCP on my server, I can leave the client running all the time with almost no battery impact. It's like night and day.
Many people complain about VoIP apps and battery drain, and this is a simple fix to eliminate it.
Hi Guys, the browser hack that wipes Samsung phones is not limited to just those handsets. These guys do a better job of describing the whole thing:
http://www.theverge.com/2012/9/26/3412432/samsung-touchwiz-remote-wipe-vulnerability-android-dialer
Here is a direct link to the exploit test:
http://dylanreeve.com/phone.php
I'm running MavRom4 with the China telco radio image and my device is vulnerable. Just wanted to share the info so people are aware; having two dialers and no default will force the exploit to ask you to actively pick a dialer; this would neutralize most cases but that is a pretty annoying work around.
Maybe people can post D3 Roms that aren't vulnerable.
majatt said:
I'm running MavRom4 with the China telco radio image and my device is vulnerable. Just wanted to share the info so people are aware; having two dialers and no default will force the exploit to ask you to actively pick a dialer; this would neutralize most cases but that is a pretty annoying work around.
Click to expand...
Click to collapse
Also, installing DialerOne and making it the default will protect you as well - you do not have to leave it without a default dialer set. DialerOne is actually a good dialer - I used to use it with my Droid Eris with CyanogenMod ROMs, in order to have the dial by name function that the Sense dialer supported back. And you can still leave the stock dialer set in a home page or on the launcher dock - it will still work if you call it up. It will not be called up if you launch the dialer from another app, though, if you make DialerOne the default.
The stock dialer is vulnerable - a predictable result, based on the vulnerability of MavRom, but I did want to say that I tested it. I haven't tested any other ROM - at this point, I don't have much time to try some out, and I think I recently deleted my most recent Liberty and Bionic Nandroid backups.
Let's see how long before Moto releases a critical patch update for stock.
Thanks, this is good to know. I thought it was only Samsung phones that had the issue, but since I'm still on stock 2.3.4 it appears I'm vulnerable. I have GrooveIP Lite installed on my phone, an app that allows you to make voice calls with using your Google Voice number. With this app installed I get a complete action using Dialer or GrooveIP window so I should be safe if I get a random popup Ill be sure to not select Dialer.
I heard about this "wipe" problem and when I saw it was just passing dialer codes to the fone I knew it would affect more than just Samsung.
Does anyone know if they have a list started of fones that might be vulnerable?
I read somewhere (though haven't tested it...) that the D3 does not have a dialer code that resets the phone, as the Samsung phones do/did. So, the D3 fails the display the IMEI test, but I believe that the reset code does not work with the D3.
FYI: CM10 kexec isn't vulnerable. Probably b/c it's JB (I think they fixed the vulnerability in JB). I go to the site and dialer pops up w/ *#06# No IMEI displayed
Sent from my AOKP JB GT-P3113 using Tapatalk
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