Open GoogleCodeExporter opened 9 years ago
I'm not a app developer but based on the error log I'm guessing this problem
has to do with Kindle not supporting DISABLE_KEYGUARD permission.
http://stackoverflow.com/questions/9826334/kindle-fire-and-disable-keyguard-perm
ission
Original comment by ampru...@gmail.com
on 19 Jan 2013 at 2:10
This issue can probably be closed, as a code commit was done in January 2013
that likely addressed it.
Original comment by stephen....@gmail.com
on 12 Jun 2013 at 3:42
I'm sorry but I don't have Kindle anymore so I can't test it. Thank you anyway.
Original comment by mranso...@gmail.com
on 12 Jun 2013 at 4:35
I have a Kindle and will test it later tonight.
Original comment by bpru...@gmail.com
on 12 Jun 2013 at 4:51
just downloaded 3.1 beta and tested on my Kindle Fire HD 8.9 with my Fritzbox
as registrar. Does not receive incoming calls. Application crashes on outgoing
calls, displaying an active call that is not active at all.
Can I turn on some logs to provide more details? I am really interested in
getting Sipdroid to work with my Kindle.
Thanks & Best regards, Joachim
Original comment by j....@live.com
on 23 Jun 2013 at 11:18
The problem is with the mKeyguardLock.disableKeyguard() line. I wrapped it in a
try catch block. Also with my phone provider, I had to reinitialize the audio
device when receiving calls to properly establish two way audio because my
phone provider would first answer with a hold request and then send a
re-invite/modify request. SipDroid wasn't handling this properly. Can I attach
files to this issue board? If so I can attach an APK with the changes so you
can test and also the patch file of the code changes.
Original comment by bpru...@gmail.com
on 29 Jun 2013 at 12:05
Since I can't seem to attach anything (Issue attachment storage quota
exceeded), I've included the patches below.
The patch to CallScreen.java resolved the issue of SipDroid crashing on the
Kindle.
The patch to UserAgent.java resolved an issue I had where my phone provider
would initially send a hold request for incoming calls (c=0.0.0.0) and then
send a re-invite with the correct ip address. I think this issue could help in
resolving some of the long outstanding issues reported in Issue ID 2
(http://code.google.com/p/sipdroid/issues/detail?id=2)
Index: org/sipdroid/sipua/ui/CallScreen.java
===================================================================
--- org/sipdroid/sipua/ui/CallScreen.java (revision 639)
+++ org/sipdroid/sipua/ui/CallScreen.java (working copy)
@@ -193,14 +193,21 @@
enabled = true;
}
if (enabled) {
- mKeyguardLock.disableKeyguard();
- if (Integer.parseInt(Build.VERSION.SDK) >= 16)
- mKeyguardManager.exitKeyguardSecurely(new OnKeyguardExitResult() {
- public void onKeyguardExitResult(boolean success) {
- }
- });
- enabled = false;
- enabletime = SystemClock.elapsedRealtime();
+ try
+ {
+ mKeyguardLock.disableKeyguard();
+ if (Integer.parseInt(Build.VERSION.SDK) >= 16)
+ mKeyguardManager.exitKeyguardSecurely(new OnKeyguardExitResult() {
+ public void onKeyguardExitResult(boolean success) {
+ }
+ });
+ enabled = false;
+ enabletime = SystemClock.elapsedRealtime();
+ }
+ catch(Exception e)
+ {
+ //Keyguard not enabled
+ }
}
}
Index: org/sipdroid/sipua/UserAgent.java
===================================================================
--- org/sipdroid/sipua/UserAgent.java (revision 639)
+++ org/sipdroid/sipua/UserAgent.java (working copy)
@@ -590,6 +590,9 @@
return;
}
printLog("RE-INVITE/MODIFY", LogLevel.HIGH);
+
+ closeMediaApplication();
+ launchMediaApplication();
// to be implemented.
// currently it simply accepts the session changes (see method
Original comment by bpru...@gmail.com
on 8 Jul 2013 at 3:52
How can I apply these two patches to my version of Sipdroid (using a kindle
fire hd)?
Should I save them as .java files and then use a file manager to place them
into the appropriate folder?
Original comment by ari.nach...@gmail.com
on 11 Aug 2013 at 5:26
SipDroid can file a request with the developer relations team at Amazon Digital
Services to get "whitelisted" if they want to use the DISABLE_KEYGUARD
permission.
@Ari.Nach... you'd need to download and install the latest SipDroid version to
get the fix. I'm sorry, but replacing .java files won't work.
Original comment by murt...@gmail.com
on 5 Feb 2014 at 9:30
Original issue reported on code.google.com by
mranso...@gmail.com
on 9 Dec 2012 at 12:19