Hello dear Developers,
i am currently dealing with an Galaxy S and Android 2.2 on it.
I am writting an app that uses a FTP connection to another device.
So after first test i only reached 7kbyte/s as maximum download speed.
On my Laptop i had the same issue caused by the delayed acknowledge "feature" turned on in Windows XP. After turning off i had 300kbyte/s downloadspeed.
Does anyone know how about to switch delayed acknowledge of in android devices?
Best regards,
Rotesmofa
EDIT: Okay i found the socket options here (link to developer.android.com/reference/java/net/SocketOptions)
But now due to that iam new to android development, i dont know how to set the No_delay Option.
Related
I know this have been asked many times before but is there any chances we can get a Wifi Hotspot app for WP7?
Is it even possible with the actual version? Maybe we will have to wait until Mango?
I know you guys hate this kind of question but i'm on this forum for more then 1 year i've never created a topic. Always searched and found what i wanted to know...
Even if the app is not free i really don't care cause it's essential for me...
Thanks in advance
Atomos
Sorry for my english
I'm dreaming for one too...
currently only USB tethering is possible, not even sure if all devices are supported
mango should make it possible... but not offical
It mean i'll have to wait until october...
Well i am shure i saw somewhere a Dev who said that it was actually possible with the actual tools to create such app...
Thanks for the reply by the way
I got a frustrating behavior from my phone. I created a WiFi hotspot on my Laptop on Windows 7. The hotspot enabled other phones to connect to internet via my wired connection on laptop. The frustrating part is ONLY WINDOWS PHONE 7 DEVICES were not able to detect the hotspot !!!!!
With the developer beta out, is there any new information regarding wifi hotspot capabilities for WP7?
webwalk® said:
currently only USB tethering is possible, not even sure if all devices are supported
mango should make it possible... but not offical
Click to expand...
Click to collapse
I have the HTC Arrive and I can tell you that thus far usb tethering does not work.
The devices that do work do not have a qwerty keyboard so it may be only a line or 2 of code needs to be added to the xap to make it function like it does for everyone else, or it may be something else. The device appears to dial out though so I believe this problem is definitely fixable with some help.
DVFN the creator of df router also said the code for wireless tethering is in the original diagnostic app, unfortunately because some people erased the app and can now no longer connect to zune they started to complain. Because of this I haven't even gotten a response from df and he probably left the community
Hi, my name is Francis. I am an advanced computer user but an android noobie, I have a problem and hope that by joining this forum I can get some quick help for my frustration. I have the Pantech Crossover P8000 (which by all indications on this forum is an archaic phone). I recently did the ota upgrade to Gingerbread 236 and since then my wifi cannot stay on for more than a minute at a time. This is annoying because I rely on my home wifi for most everything. How do I get this problem resolved, otherwise how do I revert to the original Froyo?
Francis
Tested with Skype version 3.2.0.6673 (released 1st July 2013) on various
Android devices (Sony Xperia Z, Samsung Galaxy Note 2, Huawei Premia 4G
The Skype for Android application appears to have a bug which permits the
Android inbuilt lockscreen (ie. pattern, PIN, password) to be bypassed
relatively easily, if the device is logged into Skype, and the "attacker"
is able to call the "victim" on Skype.
This can be reproduced as follows with 2 Skype accounts, and 2 separate
devices to use with Skype. The target phone is presumed to have an Android
lockscreen configured and in use, and to be locked during the test.
1. Initiate a Skype call to the target device, which will cause it to
wake, ring, and display a prompt on the screen to answer or reject the call
2. Accept the call from the target device using the green answer button
on the screen
3. End the call from the initiating device (ie. the device used to call
the target phone)
4. The target device will end the call, and should display the
lockscreen.
5. Turn off the screen of the target device using the power key, and
turn it on again
6. The lockscreen will now be bypassed. It will remain bypassed until
the device is rebooted
Similar to (ironically enough):
http://arstechnica.com/security/201...een-lock-on-up-to-100-million-android-phones/.
Seems that internet based calling apps might well be "unlucky".
I suggest logging out of skype when not using it, until there is a fix.
Thanks to Turl for originally bringing this to my attention.
Greetings pulser_g2,
Thanks for posting this. I found that all these screenlock bypass vulns (including yours) won't work if a enterprise policy is enforced on the target device. I've tested with 2 different smartphones, Note 8.0 and Note 2. Both with the current stock firmware. Can you or anyone else confirm this?
Cheers,
Michael
c0rnholio said:
Greetings pulser_g2,
Thanks for posting this. I found that all these screenlock bypass vulns (including yours) won't work if a enterprise policy is enforced on the target device. I've tested with 2 different smartphones, Note 8.0 and Note 2. Both with the current stock firmware. Can you or anyone else confirm this?
Cheers,
Michael
Click to expand...
Click to collapse
Hi Michael,
Thanks for the tip. However, forcing enterprise policy onto a device that does not need it should not be a solution for a bug like this (not ranting against you, please don't take it that way). Skype was already informed about this a couple of weeks ago and nothing has been done afaik.
I received a Skype update today from the market, so I guess it might be worth checking if the bug can be repeated or if it has been fixed.
Hi egzthunder1,
I don't take your post personal. My post was not made with the intent to be a bugfix. I just want someone else who also has access to provisioned devices to confirm my observation. Additionally if my observation is correct then it should be mentioned in a security advisory that enterprise provisioned devices with an enforced password seem to not be affected by all these lockscreen bypasses. I'm just discussing here
Does andybody know which wrong usage of the Android-API might be used here? I'm developing myself an app which switches the Screen on and shows information without the need to unlock the device. Know I'm concerned that I might use the API wrong, too. There were also such bugs in other apps in the past month, so there must be some wrong usage type. Saidly I didn't find anything about it via googling. If you have links, please share.
SamsungPisser said:
Does andybody know which wrong usage of the Android-API might be used here? I'm developing myself an app which switches the Screen on and shows information without the need to unlock the device. Know I'm concerned that I might use the API wrong, too. There were also such bugs in other apps in the past month, so there must be some wrong usage type. Saidly I didn't find anything about it via googling. If you have links, please share.
Click to expand...
Click to collapse
It seems to be related to the use of the permission to disable the lockscreen.
I.e. http://stackoverflow.com/questions/12021800/disable-delay-android-lock-screen-programmatically
You want to ensure you definitely disable the option once done. I suggest you create a test plan and ensure even if everything goes wrong, the lock will still get enabled again in the end.
c0rnholio said:
Hi egzthunder1,
I don't take your post personal. My post was not made with the intent to be a bugfix. I just want someone else who also has access to provisioned devices to confirm my observation. Additionally if my observation is correct then it should be mentioned in a security advisory that enterprise provisioned devices with an enforced password seem to not be affected by all these lockscreen bypasses. I'm just discussing here
Click to expand...
Click to collapse
Hmmm that is interesting actually.
I need to see if I can replicate this by forcing provisioning manually.
I don't have an exchange server unfortunately (I use my own mail server that uses the protocol but doesn't do the complex provisioning.)
I'll have a look though as I think it supports provisioning in the configuration where it emulates Exchange. I believe this likely is a workaround for enterprise users.
This would be enough motivation actually to look at setting up proper provisioning of my devices.
Thanks for letting me know
For nearly a year we have not be able to upgrade our 1000+ Android devices operating with 4.1 Jellybean because the Bluetooth will not work properly. We recently discovered that this problem apparently began with Android version 4.2, coinciding with the change in the Bluetooth stack from BlueZ to Bluezoid. Here is the story: We use an Anoto digital pen with bluetooth and an app installed on an Android device (Kyocera Torque cell phone). After pairing the pen with the phone, individual transactions, written by the pen on paper are sent to the phone after a "send" box is checked. The phone then responds by activating its camera, pictures are taken then pen data and photos are sent to our server. This is the process which has been working flawlessly. The problem: After 4.1, the pen must be paired then the phone restarted. The "send" box must be checked twice before phone responds. After 8 sends, the process reverts to the correct process and remains until 20 total "sends" upon which the bluetooth function stops. The phone must be restarted. The pattern repeats. We have tested this on a variety of devices using Android 4.2 all the way to Marshmallow, all with the same results.
Please advise as to where we might to go or with whom we may consult to resolve this problem. Our engineer is very capable and is hoping we can find someone who can help us find a work-around or hack without having to re-install the BlueZ stack, which if it is possible is likely a very big project.
Hello,
Welcome to XDA.
I'm not sure what kind or how much help you will find with something like that but I'm sure that you will be a lot closer to having a solution with help here at XDA.
Try posting your question/issue in the forum linked below.
http://forum.xda-developers.com/android/help
The experts there may be able to help.
Remember to register an XDA account so you can post and reply in the forums. Good luck.
I just bought my first ever Android phone, Acer Liquid Zest Plus.
It's not quite working in the limited ways I was hoping it to work.
First, I drive a Honda, which has handsfreelink system for connecting the phone to the car. The phone connects to handsfreelink ok, but then shows some weird behavior, in that when using the car's controls to place a call through handsfreelink, handsfreelink immediately apparently hangs up the call (i.e. the car's display shows that it hung up the call). However, this does not actually hang up the call on the phone itself, as the call gets placed nonetheless and when someone picks up on the other side, I can have a conversation through the car's audio system. Seems to almost work, but the weird behavior just described means that I can't hang up a call without pulling the phone out of my pocket and hanging it up from the phone (as opposed to hanging up using the car's controls) while driving, which takes a lot away from the point of it all.
What could be the issue with this? Note that I had a Blackberry Passport before, which used to work all as intended with handsfreelink, and my family member's iPhone 7 Plus also works as intended with handsfreelink. Is it that my Acer Liquid Zest Plus does not have the necessary bluetooth profile/stack to works with Honda's handsfreelink? Is it that handsfreelink proprietary to Honda and uses something unique, as opposed to being a generic bluetooth device of the kind? Is a bluetooth device link this, used by other auto manufacturers, feature the same generic bluetooth thing, or is this something only Holda can possibly answer for me?
Could updating the phone solve this issue? If so, how? I go into Settings -> About phone -> System updates and it tells me that my device is up to date (I did not update it since pulling it out of the box). I notice that it's on Android 6.0 , and a quick Google search showed some discussions that it is highly unlikely that the phone will get newer Android update. The "Android security patch level" shown in "About phone" says December 5, 2016. That's a long time without a security patch. Should I, and is it possible to, update the phone?
I've heard of rooting an Android device and installing custom Roms before. Where can I find a guide for my device and the custom Rom files? I am hoping this might solve my issue with handsfreelink.
I know I am all around the place with my questions, but essentially, the issue I am having is that bluetooth connection to my car's audio system does not work as expected, and I am wondering how I might fix it. I am wondering if an OS update (either official version by manufacturer or a widely-used custom Rom) might solve this issue, or simply adding an extra bluetooth profile to the phone.
A solution would be awesome, but I'd be asking too much if I was hoping for that. Instead, if anyone can just provide me some pointers in terms of how to do research on what I should be doing to solve this, or clarify some concepts (to the extent you can tell I got it wrong from reading this post) for me, it would be really appreciated.
I've already been to Honda's handsfreelink website and Acer's support page for this product and there's nothing helpful there.
Thank you very much.
ACER
monotious said:
I just bought my first ever Android phone, Acer Liquid Zest Plus.
It's not quite working in the limited ways I was hoping it to work.
First, I drive a Honda, which has handsfreelink system for connecting the phone to the car. The phone connects to handsfreelink ok, but then shows some weird behavior, in that when using the car's controls to place a call through handsfreelink, handsfreelink immediately apparently hangs up the call (i.e. the car's display shows that it hung up the call). However, this does not actually hang up the call on the phone itself, as the call gets placed nonetheless and when someone picks up on the other side, I can have a conversation through the car's audio system. Seems to almost work, but the weird behavior just described means that I can't hang up a call without pulling the phone out of my pocket and hanging it up from the phone (as opposed to hanging up using the car's controls) while driving, which takes a lot away from the point of it all.
What could be the issue with this? Note that I had a Blackberry Passport before, which used to work all as intended with handsfreelink, and my family member's iPhone 7 Plus also works as intended with handsfreelink. Is it that my Acer Liquid Zest Plus does not have the necessary bluetooth profile/stack to works with Honda's handsfreelink? Is it that handsfreelink proprietary to Honda and uses something unique, as opposed to being a generic bluetooth device of the kind? Is a bluetooth device link this, used by other auto manufacturers, feature the same generic bluetooth thing, or is this something only Holda can possibly answer for me?
Could updating the phone solve this issue? If so, how? I go into Settings -> About phone -> System updates and it tells me that my device is up to date (I did not update it since pulling it out of the box). I notice that it's on Android 6.0 , and a quick Google search showed some discussions that it is highly unlikely that the phone will get newer Android update. The "Android security patch level" shown in "About phone" says December 5, 2016. That's a long time without a security patch. Should I, and is it possible to, update the phone?
I've heard of rooting an Android device and installing custom Roms before. Where can I find a guide for my device and the custom Rom files? I am hoping this might solve my issue with handsfreelink.
I know I am all around the place with my questions, but essentially, the issue I am having is that bluetooth connection to my car's audio system does not work as expected, and I am wondering how I might fix it. I am wondering if an OS update (either official version by manufacturer or a widely-used custom Rom) might solve this issue, or simply adding an extra bluetooth profile to the phone.
A solution would be awesome, but I'd be asking too much if I was hoping for that. Instead, if anyone can just provide me some pointers in terms of how to do research on what I should be doing to solve this, or clarify some concepts (to the extent you can tell I got it wrong from reading this post) for me, it would be really appreciated.
I've already been to Honda's handsfreelink website and Acer's support page for this product and there's nothing helpful there.
Thank you very much.
Click to expand...
Click to collapse
Acer is just the brand and few software smartphonne.they just order big amount of phones and sell them. the phone shows as Shanghai Huaqin Telecom Technology Co.,Ltd),have seen this on my old --vodaphonne-.The only emergenncy update from january 05 2018 and this is as far you go with ACER. YOU will never get any update .The name LIQUID is there PR name of there LAUNCHER,that´s all.ROOTING??? no point,waste of time no one will till today do it. Have the same phone and feel that I did a mistake and lost money.ACER stopped to sell smartphones. If you want to modiffy the phone the LAWNCHAIR launcher is good ,aswell others. But keep in mind that will be always android 6 and no security updates
Freudeauf2 said:
Acer is just the brand and few software smartphonne.they just order big amount of phones and sell them. the phone shows as Shanghai Huaqin Telecom Technology Co.,Ltd),have seen this on my old --vodaphonne-.The only emergenncy update from january 05 2018 and this is as far you go with ACER. YOU will never get any update .The name LIQUID is there PR name of there LAUNCHER,that´s all.ROOTING??? no point,waste of time no one will till today do it. Have the same phone and feel that I did a mistake and lost money.ACER stopped to sell smartphones. If you want to modiffy the phone the LAWNCHAIR launcher is good ,aswell others. But keep in mind that will be always android 6 and no security updates
Click to expand...
Click to collapse
your bluetooth -you have to install a app from third party and then configure the rest in the app and in setting device.Importend timer schould be always set as on in bluetooth .Standard is few minutes.good luck
---------- Post added at 02:23 PM ---------- Previous post was at 02:06 PM ----------
Freudeauf2 said:
your bluetooth -you have to install a app from third party and then configure the rest in the app and in setting device.Importend timer schould be always set as on in bluetooth .Standard is few minutes.good luck
Click to expand...
Click to collapse
To keep all your apps uptodate I use from FDROID app the YALP STORE ,there you can in settings update your system apps,as I sad this is the way as far you go with ACER. Hope it helps