Is there a way that one of the Kernel developers can find a way to restore the missing Bluetooth profiles to the Galaxy Tab (preferably the Verizon one)?
Searching around the internet I've seen a lot of people upset that the HID profile is missing from the Verizon Tab, and personally, I'd like to be able to use the DUN profile for data tethering.
I unfortunately don't know much about the bluetooth stack implementation in Android, but I can see on the Samsung site that each of the Galaxy Tabs has slightly different implementations that includes or removes certain Bluetooth Profiles.
Is this a bear of a task or is it something that can be patched in or added to a kernel or ROM with only a little effort?
For background, I'm running Boushh's K-Lean ROM (v3) and the Voodoo Kernel (v3) and still can't seem to use the DUN profile for tethering.
Thanks!
Related
Hi guys!
I was wondering why the usb-tethering option is not available in our LGOB?
I came from an cheap Samsung Galaxy Ace - and here i had WiFi-Tethering along with USB-Tethering.
As far as i know, thats a Android Stock-Feature?
Therefore, is there a way to just enable the usb-tethering (e.g. with a line in the build.prop or something similar)?
I dont want to use 3rd party-apps to get this running, since i love a straight, clean system without too many apps.
Looking forward to hear from you!
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!
It may seem a stupid question but, since the news that Samsung won't be releasing ICS for the SGS I've been pondering my alternatives.
I would imagine a port of Nexus S ICS would work on the SGS' given their similar hardware specs but, of course, you would lose TW; Samsung's reason for not developing ICS for the SGS as there is not enough ROM for ICS + TW
I read on another thread that video-calling was not part of the standard Android build and was something that Samsung added. I myself originally bought an ICS because it was the only Android phone with a Bluetooth SAP stack, which I need to support Bluetooth integration with my car.
I have used video-calling and use BT SAP every day so would I be able to add these to a standard ICS build or are they integrated into TW? Back to my original question what else is built into TW?
Touchwiz is the layout of the original samsung galaxy s rom+some unique apps.The problem is in device maybe small amount of RAM and ROM.The Samsung would update to ics but only with touchwiz,like samsung galaxy s II
I hear the Gear S is now totally independent, built in wifi, 4g, etc... Anyways, This thing is a bluetooth device, I'm assuming it's got a built in generic bluetooth dongle and the tizen OS itself handles protocols such as a2dp for headphones, and communication thru their strange SAP protocol. (Samsung Accessory Protocol)
Is it at all possible to achieve internet access for apps with any APIs for the new Gear S? I figured my phone (actual samsung) along with other manufacturers have a Tethering option. I was hoping I could turn on my bluetooth tethering and get actual internet connectivity on the Gear 2 Neo, and start developing real web-oriented apps for the watch without some flaky form of polling using a background process on the phone itself to relay content to the gear 2 neo.
Once I heard you could code for this in as close to HTML/CSS/JavaScript as possible (there are some things that just don't translate to be as simple as it is in any browser) I was hooked, rushed out and bought one, but now I'm disappointed at my purchase realizing there is no way to achieve any content from the web without a back-end running on the phone, and I never liked java, nor do I care to learn it.
Could it be already possible just no way to reference the internet thru the js methods available in the Tizen SDK? This is a form of linux, what about possibly getting perl or node.js in there and maybe making your own interface to sockets? It'd be so awesome to actually have perl on a gear 2 neo.
found thread
I searched before posting this, couldn't find nothing, and an unrelated google search about gear 2 neo ringtones brought up a link... go figure. Anybody else looking can also see the solution I stumbled upon here
http://forum.xda-developers.com/gear-2/general/guide-internet-connection-gear2-5-steps-t2956328/post57140526#post57140526
while it's not perfect, it's a giant leap in the right direction I look forward to more in this thread!
Hi All,
WiFi Calling..... / what is it ??
Is it based and driven on specific hardware (ie: must meet a certain spec / certain chips)
Is it based on network config (ie: like MMS Picture Messaging for all old people) settings to be added?
Is it based on specific modified files, signed by a Network Provider...?
Basically, is this possible / doable on our aging Note? I was having a discussion with a friend who has it on a top flag device. And I basically said its rolled out to high end devices to make them more appealing to customers. I'm fairly certain it doesnt require high-end equipment to make the feature work, and assumed its just some settings that pushed/applied to your network settings. Much in the same way we used to have MMS enabled via a Text Config file, to merge into phones OS settings.
However, bit of a Google-squoogling around, I noticed others talking about it on XDA, saying it requires pre-made/modified FILES that are signed by likes of T-Mobile in order to get the feature working.
So I was wondering, can this be acheived via a patch to the OS, beit file based or via a Module (Xposed) as I also remember reading that CM / Cyanogen promised this feature live in CM13 builds...
.... answers on the back of a postcard please!!!
Cheers, Lister
Hi All,
Ok, quick update... I've just found WiFi calling is already baked into our ROMs (as CM had promised). Searching for it under the network settings, it doesnt appear to show up. However if you search (maginfiying glass) with the word "Calling" it then shows up. It's disabled by default, when you enable it though nothing appears to happen. If you come out of Settings and back in, it's disabled again.
Does this mean its BORKED and broken via Cyanogen and they never got it working in the first place? Or its only intended for certain phones to pickup these settings. Or it depends on certain hardware chipsets??
Cheers, Lister
Hi All,
Just found out it depends on certain ISP settings...
So it does appear to work, just not who I'm with...
Lister