Related
Hi,
ok, this is most probably the most simple, stupid, unfinished piece of software you have ever seen. I agree. On the other hand, it should do what it is originally meant for. Setup a VOIP configuration on a Smartphone running WM6 without having to play with XML files and stuff.
So, this release, which is not even Beta or Alpha (whatever may be before that) does the job to load a VOIP config based on what you type in. It works on my HTC S620, should work on any VOIP enabled WM6 Smartphone.
For the coding curious, It's being coded (far from being finished) in pure C, without any Framework and MS developers suites. Only freeware stuff is being used for this development.
You'll see menu entries that will bring up only message boxes. Functions are not yet implemented but I'm working on it.
Once you typed in your configuration, press the key linked to "Save" (Left key), this will copy your config to the phone. A Messagebox will tell you the result of the operation and application will exit.
The config you typed in is saved as _setup.xml as well in the \Temp folder.
A file named Voipiser.cfg is saved as well in the \Temp folder, just forget about it atm.
Please, please, take this as hobby development. This is my first Smartphone app and I release it before being fully finished & tested only because I think it could be nice, if it works for you as well, to have it as soon as possible.
View attachment 38358
Hi to Shaun who is developing a much nicer version for PPC.
Cheers,
Ka.
This sounds interesting. I would definitely give it a try.
Doesn't work under wm6 t-mobile rom on dash
Good job!
Hi Kast,
i tried enabling VoIP Support on my HTC S710 by using your small app. As long as i let the example values untouched everything works fine and the app tells me, that the settings were succesfully saved. But when i type in the configvalues of my sipaccount, it says "XML Input malformed" when pressing "Safe". I think the problem is something about the proxyname. If i type in the values but let the proxyfield untouched, the app saves the settings...
Any suggestions here?
Greetz,
Fussel
Doesn't work under wm6 t-mobile rom on dash
Click to expand...
Click to collapse
Uhm, strange, developed it originally and tested on TMo Dash WM6... Would you mind giving me details of the way it crashes?
I think the problem is something about the proxyname.
Click to expand...
Click to collapse
You could send me the proxy name and I'll try to debug it with it.
Thanks all,
Ka.
Fussel1979 said:
Hi Kast,
i tried enabling VoIP Support on my HTC S710 by using your small app. As long as i let the example values untouched everything works fine and the app tells me, that the settings were succesfully saved. But when i type in the configvalues of my sipaccount, it says "XML Input malformed" when pressing "Safe". I think the problem is something about the proxyname. If i type in the values but let the proxyfield untouched, the app saves the settings...
Any suggestions here?
Greetz,
Fussel
Click to expand...
Click to collapse
Just put http:// in front of the proxy server adress and it will save it!
good luck
Hello, i had an "unknown error" when i save config
Hi gregdu13250,
mind telling me what phone you have and the provider you use?
Thanks,
Ka.
I have a s710 htc and the SIP¨provider is Ippi
Hi. Here is all errors which are done by KaSt VoIpiser program in a _setup.xml file.
Code:
1:<wap-provisioningdoc>
2: <characteristic type="VoIP">
3: <parm name="SIPSettings"
[COLOR=Red] 4:[/COLOR] value="<provision key='1232ab01' name='Sipnet'[COLOR=Red]>[/COLOR]
5: <provider name='Sipnet' />
6: <user account='1234567' password='7654321'
[COLOR=Red] 7:[/COLOR] uri='[COLOR=Red]sip:[/COLOR][email protected]'
8: allowedauth='digest'/>
[COLOR=Red]9:[/COLOR] <sipsrv addr='sipnet.ru[COLOR=Red]:5060[/COLOR]' protocol='UDP' role='proxy'>
10: <session party='First' type='pc2pc' />
11: <session party='First' type='pc2ph' />
12: </sipsrv>[COLOR=Red]
13:[/COLOR] <sipsrv addr='sipnet.ru[COLOR=Red]:5060[/COLOR]' protocol='UDP' role='registrar'/>
14: </provision>" />
15: </characteristic>
16: </wap-provisioningdoc>
-------------------------------------------------------------------------
1: <wap-provisioningdoc>
2: <characteristic type= "VoIP">
3: <parm name="SIPSettings"
[COLOR=Red] 4:[/COLOR] value="<provision key='1232ab01' name='Sipnet'[COLOR=Red]>[/COLOR]
5: <provider name='Sipnet' />
6: <user account='1234567' password='7654321'
[COLOR=Red] 7:[/COLOR] uri='[email protected]'
8: allowedauth='digest'/>
[COLOR=Red]9:[/COLOR] <sipsrv addr='sipnet.ru' protocol='UDP' role='proxy'>
10: <session party='First' type='pc2pc' />
11: <session party='First' type='pc2ph' />
12: </sipsrv>
13: <sipsrv addr='sipnet.ru' protocol='UDP' role='registrar'/>
14: </provision>" />
15:</characteristic>
16:</wap-provisioningdoc>
Upper is a genuine _setup.xml file, and lower is a file generated by KaSt VoIpiser program.
I think it it will be easy to correct.
Hi,
thanks for spotting the errors houser21! Great help!
Just one thing... I can't stick 5060 in the config as not all of the proxies are using that port. I know at least one using 5061. Prefer that the user specifies the port when different than 5060 or just by always entering proxyort.
Actually made this tool to ease the setup of the provider I use normally, which accepts the syntax the way it is. Prolly not all of them are so "open".
Will post tomorrow a new version with the changes you highlighted.
Thanks again,
Ka.
I downloaded you're program and everything looks really nice but...
I cant seem to get it working when i config it for voipbuster.
The idea is to set it that if there is Wlan available that the call goes through the internet, is this possible with this program and if so what do i do wrong ??
domain name is missin
Hello Kast
it seems one parameter is missing in the CAB file - the domain name.
the VOIP provider supplied me with 4 parameters:
user anem
password
SIP IP address
domain name.
where so i put the domain name in your application ?
this should fo into the URI field in the setup.xml file
thanks.
Kast, your program works great but I still cant get VoIP to work at all on the S620, calls still go over mobile even when connected to wifi and s620 shows internet calling available. Is there anothe cab file you used to get VoIP working ?
Thanks.
kast said:
Hi,
ok, this is most probably the most simple, stupid, unfinished piece of software you have ever seen. I agree. On the other hand, it should do what it is originally meant for. Setup a VOIP configuration on a Smartphone running WM6 without having to play with XML files and stuff.
So, this release, which is not even Beta or Alpha (whatever may be before that) does the job to load a VOIP config based on what you type in. It works on my HTC S620, should work on any VOIP enabled WM6 Smartphone.
For the coding curious, It's being coded (far from being finished) in pure C, without any Framework and MS developers suites. Only freeware stuff is being used for this development.
You'll see menu entries that will bring up only message boxes. Functions are not yet implemented but I'm working on it.
Once you typed in your configuration, press the key linked to "Save" (Left key), this will copy your config to the phone. A Messagebox will tell you the result of the operation and application will exit.
The config you typed in is saved as _setup.xml as well in the \Temp folder.
A file named Voipiser.cfg is saved as well in the \Temp folder, just forget about it atm.
Please, please, take this as hobby development. This is my first Smartphone app and I release it before being fully finished & tested only because I think it could be nice, if it works for you as well, to have it as soon as possible.
View attachment 38358
Hi to Shaun who is developing a much nicer version for PPC.
Cheers,
Ka.
Click to expand...
Click to collapse
tjmvdz said:
Just put http:// in front of the proxy server adress and it will save it!
good luck
Click to expand...
Click to collapse
I think it doesn't need the http://, when I add the http://, My Voip doesn't work. My phone cann't register and make call.
Blackjack II SGH-i617
Thanks for the effort, though when trying to use this program to save a config, all it does is say unknown error.
Has anyone got a smartphone voip config program working at all?
So my game and all of it's several revisions have worked great in the Emulator, but for whatever reason, my games will not work on ANY Android Phone !!! I've tried 4 types.
All it does is show me my background and nothing in the foreground. No events, sounds, nothing.
So why does most of Googles stuff FAIL SO BAD!!! when people try to use it?
What do you guys use?
I am a graphics artist and I have 3 games ready that look killer, but cannot get them to a market or even a phone.
So do I leave android, or are there solutions for getting things from Eclipse/SDK-ADV to a running state on a freaking phone?
mmm what are you using for the games: canvas, opengl es 1.0 JSR 239 or opengl es 2.0? which devices are you trying to run them into? are the device screen size in the same resolution that the emulator?
Though i really don't see this problem in opengl since the emulator does not have graphics acceleration... So you are using canvas, right? have you check that all your imports are compatible with the version of android of the phones you are testing them? remember that canvas is not accelerated on phones, whereas in the emulator it is, so maybe, if it is too graphic intensive, that might be part of your problem
I've never run into this problem, but I use mostly opengl frameworks, that btw are a pain in the ass to debug with the emulator but work great on the phones (5 vs 40-60 fps)...
For 2d I use andengine, its an opensource gl es 1.0 framework, compatible with devices from 1.6
For physics I use Box2d, that it is an opensource physics jni framework compatible from 2.* if i recall right.
For 3d i have not done anything yet. But you could try using opengl or there is a port of an opensource java 3d framework, can't recall its name, but it was something like jp**-ae i think, probably someone would say its name or you may find it using the search of the forum, cause i read that one in a post from here a few months ago...
I personally don't use canvas, since i find andengine much more usefull and faster for 2d...
I am loading all the graphics/buttons via the xml layout using LinearLayout.
I recently read that "fill_parent" is a bad idea in the layout.xml so I replaced those with "wrap_content"...still have yet to test on the phone.
I am basically just trying to the SkellyApp to even run on my phone, not even snake will go onto it.
I do not use canvas, gps, bluetooth or anything, just touch stuff and text.
I'm still left confused
Here are the Imports I am using;
import android.app.Activity;
import android.content.res.Configuration;
import android.os.Bundle;
import android.view.Menu;
import android.view.MenuItem;
import android.view.View;
import android.widget.Button;
import android.widget.TextView;
import android.view.MotionEvent;
import android.media.MediaPlayer;
import android.media.MediaPlayer.OnCompletionListener;
import android.view.View.OnTouchListener;
import java.util.Random;
you still missing something for us to see what the error is
the fill_parent / wrap_content are just properties, is not that its going to produce that error... it is recommended to use RelativeLayout, just for making it easier to port it to different screen sizes
if you don't want to mess much with the layout settings you could use droiddraw (droiddraw.org)
other than that I don't know what you are doing wrong, have you try logcat to see if you spot an error somewhere? you will probably find your answer there...
I appreciate you sticking with me on this...here is my layout file...is there a problem with me using 2 Linears?
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="wrap_content" android:layout_height="wrap_content"
androidrientation="horizontal"
android:background="@drawable/bg2"
>
<LinearLayout
android:layout_width="wrap_content" android:layout_height="wrap_content"
androidrientation="horizontal"
>
<!-- android:background="@drawable/blank"-->
<Button android:id="@+id/back" style="@style/ActionButton"
android:text="@string/back"
android:layout_width="45dip"
android:layout_height="45dip"
android:layout_alignParentLeft="true"
android:layout_marginLeft="44dip"
android:layout_marginTop="2dip"
android:layout_alignParentTop="true"
android:layout_centerInParent="true"
android:layout_gravity = "center"
android:background="@drawable/green"
/>
<Button android:id="@+id/clear" style="@style/ActionButton"
android:text="@string/clear"
android:layout_width="45dip"
android:layout_height="45dip"
android:layout_alignParentLeft="true"
android:layout_marginLeft="-12dip"
android:layout_marginTop="35dip"
android:layout_alignParentTop="true"
android:layout_centerInParent="true"
android:layout_gravity = "top"
android:background="@drawable/green"
/>
</LinearLayout>
<Button android:id="@+id/butone"
android:text="@string/butone"
android:layout_width="65dip"
android:layout_height="65dip"
android:layout_marginLeft="-349dip"
android:layout_marginTop="158dip"
android:layout_alignParentBottom="true"
android:layout_centerInParent="true"
android:layout_gravity = "bottom"
android:background="@drawable/glow1"
/>
<Button
android:id="@+id/b3i"
android:text="@string/b3i"
android:layout_width="120dip"
android:layout_height="120dip"
android:layout_marginLeft="-120dip"
android:layout_marginTop="95dip"
android:layout_alignParentBottom="true"
android:layout_centerInParent="true"
android:layout_gravity = "top"
android:background="@drawable/b3"
/>
<TextView android:id="@+id/text1"
android:layout_marginLeft="-89dip"
android:layout_marginTop="27dip"
android:layout_width="50dip"
android:layout_height="30dip"
android:textStyle="bold"
android:textColor="#B9B888"
android:freezesText="true"
/>
<TextView android:id="@+id/text2"
android:layout_marginLeft="12dip"
android:layout_marginTop="201dip"
android:layout_width="50dip"
android:layout_height="30dip"
android:textStyle="bold"
android:textColor="#B9B888"
android:freezesText="true"
/>
<TextView android:id="@+id/text3"
android:layout_marginLeft="-160dip"
android:layout_marginTop="201dip"
android:layout_width="50dip"
android:layout_height="30dip"
android:textStyle="bold"
android:textColor="#B9B888"
android:freezesText="true"
/>
<Button
android:id="@+id/exitbutton"
android:layout_width="35dip"
android:layout_height="35dip"
android:layout_marginLeft="222dip"
android:layout_marginTop="-37dip"
android:layout_alignParentBottom="true"
android:layout_centerInParent="true"
android:layout_gravity = "top"
android:background="@drawable/exit"
/>
</LinearLayout>
you could debug your apps on the device using eclipse and see from the logcat where things go wrong
these may help
Code:
http://forum.xda-developers.com/showthread.php?t=821022&highlight=debugging
http://dotnet.dzone.com/articles/android-and-windows-phone-7-%E2%80%93
thank you I will look at those.
Is my layout XML file (look above) correctly structured, etc. ?
your xml is ok. i ran it on my phone and its loading just fine (it displays the same thing as the emulator)
nemoc 23 said:
your xml is ok. i ran it on my phone and its loading just fine (it displays the same thing as the emulator)
Click to expand...
Click to collapse
Thanks again for your help, I'm glad it's working...guess I am learning something
Oh boy...so I created more AVD's using the other size options like 400,432,800,854, and my XML Layout above puts my buttons in different screen locations depending on the AVD used, only the default and the 432 show it the way I need.
How does a person go about making sure their buttons are in the same spot every time for all resolutions using the XML Layout, or another version of mine in the post above?
Sorry to ask for another favor, but this seems too nebulas for me to grasp atm, so a push in the right direction would be great
What were the four devices you tried. Even simple applications can change depending on the devices oem. I have a HTC Droid Incredible and simple things like radio buttons look different than the emulator, so I would see if it is an HTC/Samsung/whatever problem rather than an android problem. I could be wrong, but I have noticed that simple things change, so why not more complex things?
LuvinAndroid said:
Oh boy...so I created more AVD's using the other size options like 400,432,800,854, and my XML Layout above puts my buttons in different screen locations depending on the AVD used, only the default and the 432 show it the way I need.
How does a person go about making sure their buttons are in the same spot every time for all resolutions using the XML Layout, or another version of mine in the post above?
Sorry to ask for another favor, but this seems too nebulas for me to grasp atm, so a push in the right direction would be great
Click to expand...
Click to collapse
It seems that using linear layouts as a base caused the different resolutions to not be created the same. I use a single relative layout as the parent layout, and several views (text, image) and buttons and center everything. I would try surrounding the current xml in a single RelativeLayout, and if that doesn't work, then try breaking each LinearLayout up and converting them to RelativeLayouts (which may seem like a pain because you have to make every item's position relative to the items around it, so it can be tricky to position them exactly right). You could also use a combination of Relative and Linear Layouts to achieve the look and feel you desire for the overall layout. Hope this helps
I was looking through files with root explorer and seen /system/etc/permissions. An seen handheld_core_hardware.XML. I looked in that and it says "if upto 4 independently tracked pointers are supported, there should be file. Android.hardware.touchscreen.multitouch.distinct.XML. so went back to,/etc/ permissions that file is there
Does this mean x8 supports multitouch, or am I wrong?
johnnyw1991 said:
I was looking through files with root explorer and seen /system/etc/permissions. An seen handheld_core_hardware.XML. I looked in that and it says "if upto 4 independently tracked pointers are supported, there should be file. Android.hardware.touchscreen.multitouch.distinct.XML. so went back to,/etc/ permissions that file is there
Does this mean x8 supports multitouch, or am I wrong?
Click to expand...
Click to collapse
2.1 rom doesn't been make only for X8..we shared this rom with others device too..but with diff configuration..from the .xml file u said "if upto 4 independently tracked pointers are supported" its means if deveice have 4 sensor,then the multitouch is unlocked and can be used..but X8 only have 1 sensor which mean X8 doesn't support it..thats from what i've understand
X8 has 2 sensors. 2 sensors files were hided, 1 sensor showed.
Sent from my X8 using Tapatalk
mati96PL said:
X8 has 2 sensors. 2 sensors files were hided, 1 sensor showed.
Sent from my X8 using Tapatalk
Click to expand...
Click to collapse
didn't know that
This is the file I mentioned, that in handheld_core_hardware.XML says should be there on a device if upto 4 independently touched pointers are supported, there is nothing else anywhere in in the phone that mentions whether its single or multitouch
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2009 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
apache.org/ licenses /LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- This is the standard set of features for a touchscreen that supports
independently-trackable multiple-finger multitouch. -->
<permissions>
<feature name="android.hardware.touchscreen" />
<feature name="android.hardware.touchscreen.multitouch" />
<feature name="android.hardware.touchscreen.multitouch.distinct" />
</permissions>
xperia x8/ 2.3.3/ JIT / N class wifi
Is it available, other than recompile one. I found dolphin browser has more CPU usage than stock FROYO one. But the stock browser has no fullscreen function.
alright,find the way to compile.
and just add line in Browser.apk\res\values\styles.xml
<item name="android:windowFullscreen">true</item>
Try opera mobile
Sent from my GT-I9000 using Tapatalk
redbloodhk said:
alright,find the way to compile.
and just add line in Browser.apk\res\values\styles.xml
<item name="android:windowFullscreen">true</item>
Click to expand...
Click to collapse
Wow man! This is cool, now I only use stock browser
Thanks.
Is there a way to mod browser so it could download any file?
One thing to notice this line must be inside (STYLE): example :
<style name="BrowserTheme" parent="@touchwiz:style/TwTheme">
<item name="android:windowFullscreen">true</item>
<item name="android:colorBackground">@android:color/transparent</item>
<item name="android:windowBackground">@drawable/initial_titlebar</item>
<item name="android:windowNoTitle">true</item>
<item name="android:windowContentOverlay">@null</item>
</style>
yes under style name="BrowserTheme"
Opera works good.
redbloodhk said:
alright,find the way to compile.
and just add line in Browser.apk\res\values\styles.xml
<item name="android:windowFullscreen">true</item>
Click to expand...
Click to collapse
I am interested in this hack, just not sure to understand what you mean.
I have unpacked Browser.apk and I do not see "values" directory in "Browser.apk\res\", and of course no styles.xml also.
Using JVP build from Ficeto.
Could you explain a bit or point us to relevant threads?
Thanks.
Ok, I did it,
As explained to me by Daneshm90, the procedure is rather simple
Decompile -> Modify AdroidManifest's android:theme value to :
android:theme="@android:style/Theme.NoTitleBar.Fullscreen"
(replacing "@style/BrowserTheme")
Recompile.
To be noted that decompile and recompile of Browser.apk (found in /system/app on the phone) may be achieved using apk_manager (http://forum.xda-developers.com/showthread.php?t=695701) which uses apktool just don't forget to use the option:
"10 Decompile apk (with dependencies) (For propietary rom apks)"
using twframework-res.apk (found in System/framework on the phone) as input.
then
" 11 Compile apk"
then
"12 Sign apk" as system app
then
"12 install apk"
Stock browser is a lot better in full screen.
Phone screens will always feel too small for web browsing and we need each pixel...
I guess it should also work on SGS2, I will check as soon as I get mine...
I would say Opera Mini is good choice.
Opera Mobile is faster and full screen(need setting in option)
All the way with opera mobile, Faster than stock, cache usage is maybe a bit more than stock, but i can live with that.
Has someone tried this with JVQ-Stock-Browser (much faster than opera mobile/mini imho)?
i used the search function.
how do i set the user agent in opera mini as a desktop? can somebody help me. thanks
I'll try to put this as simple as possible.
PLEASE tell me if I have missed anything or need to add any more information
First, you have Developer Unlock, which put simply, when you submit an app to the store, it gets "signed" with a digital signature. Windows Phone devices will only run applications with that signature. Since if you are developing an app, it is not "signed" so with a Developer Unlock, you are able to run applications without a "signature" on any Windows Phone device but there are limits.
That's where Interop-Unlock comes in. A developer-unlocked device can sideload an app but the app is not able to access the Windows Phone system and Registry. Every app, whether sideloaded or installed from the Windows Phone Store, MUST declare what functions the apps needs to use to function properly. To access certain parts of the system and registry, it needs to declare "ID_CAP_INTEROPSERVICES" in the WMAppManifest.xml. A normal app, for example "Doodle Jump" declares these functions:
Code:
<Capability Name="ID_CAP_NETWORKING" />
<Capability Name="ID_CAP_SENSORS" />
<Capability Name="ID_CAP_MEDIALIB" />
<Capability Name="ID_CAP_GAMERSERVICES" />
<Capability Name="ID_CAP_IDENTITY_DEVICE" />
Which is basically the app telling the phone "Hey man, I need to be able to access the internet (ID_CAP_NETWORKING), access your motion sensor (ID_CAP_SENSORS), media library, Xbox Live and your device's identity.
Those declared functions are allowed by the Store and to be sideloaded. However to edit the registry, the app needs the ID_CAP_INTEROPSERVICES declaration in the WMAppManifest.xml. The Store does not allow apps with this declaration to be uploaded by 3rd-party developers. Nor does the device allow the app to deploy with that declaration.
Here's where the problem is. In order to allow the app with the INTEROPSERVICES cap to be deployed, you need to override an entry in the Registry (setting the maximum allowed apps to be deployed to over 300 overrides the INTEROPSERVICES cap.). But in order to override the entry, you need the INTEROPSERVICES cap to edit the registry (chicken-and-egg, anyone?).
This restriction was introduced in the Windows Phone 7.5 update but thankfully, 1st-party and 2nd-party developers are able to upload apps with the INTEROPSERVICES cap declared (1st-party, namely Microsoft and 2nd-party being OEMs). So what we do is find a weakness, or exploit in the app to be able to edit the Registry.
How this was done for Samsung Windows Phone 8 devices was that the Samsung Diagnosis app that was hidden, had a registry editor hidden somewhere within the app. @GoodDayToDie and -W_O_L_F- found the editor and managed to Interop-Unlock the Samsung ATIV S, which was found to work on other Samsung Windows Phone 8 devices. This does NOT work on other devices as Samsung uses a method to edit the registry that is not found on other devices.
What we are doing now in the Development & Hacking Sub-forum is trying to find exploits in those 1st-party and 2nd-party applications on Windows Phone. We hope to find a way to Interop-Unlock other devices as soon as possible, but only time will tell...
redacted
So from what i understand, apps which Microsoft/Nokia release have the special ability to change the registry and changing the registry can interop unlock your phone. So you find how the app does that and use it to change the registry. Am i right?
hashmiakbar said:
So from what i understand, apps which Microsoft/Nokia release have the special ability to change the registry and changing the registry can interop unlock your phone. So you find how the app does that and use it to change the registry. Am i right?
Click to expand...
Click to collapse
They have permissions to change the registry settings for their own apps, but that is all.
Use snickler's registry app to see it in action.
Sent from my Lumia 928 (RM-860) using Tapatalk