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.
Hello, guru's.
I've got a problem with CSipSimple after flashing HyperSensation-CM7.1-v0.3 — it hangs up after call. Not every call, but with a chance of 75% I believe. Only reboot could return it to life.
As far this is obviously ROM problem, I'm not writing to Regis, but here.
The question is: How can I diagnose what is happening with it and maybe fix it later?
I'd like not to flash another ROM as HyperSensation is just I always wanted — nothing but phone at the beginning and only my favorite apps installed.
Thanx in forward.
What exactly is it about android that makes developing new roms so difficult? For example, most ICS roms for the G2x are somewhat unstable, is that just because devs need to write drivers from scratch, or is it something else that I'm missing?
Another way of saying this would be, what makes "installing" Android different from installing Windows on a PC? (I understand Android needs to flash roms and windows can just install from a disk, but beyond that?)
Also, I don't mean to complain at all, I very much appreciate all the hard work the devs have been putting into these roms; I'm just curious what specifically makes it so challenging?
the problem most of the time comes from how the rom interacts with the hardware.
when an app needs to do something, it calls a function (for example turn on wifi) the rom gets this call and passes it to the kernel. the kernel then passes this call to the hardware which powers on the wifi.
APP>ROM>KERNEL>HARDWARE
a problem can occur at any point in that chain. the app can call a function that does not exist in that version of android, or the rom can call part of the kernel which is not there, or the kernel can try to do something that cant be done hardware wise.
oversimplifying it, porting a version of android is basically matching the function calls from the rom, to that of a kernel that works for this phone.
Now, alot of the problems we have been having with ICS on our phones is because of Hardware Acceleration. we have no offical kernel that supports it. without that we have no way for the calls from the rom to get to the hardware.
the INCREDIBLE devs at Cyanogen figured this out, they wrote those functions themselves. the part that makes this incredible is the fact that they did not know what to call, or where to send it. they had to guess at EVERYTHING! unfornately this also causes problems, while they may have gotten the functions 90% correct, 10% is still wrong. and that is what is most likely causing problems for us. (a stupid example i saw once is that they made a new brightness driver, but it was off by 1 number, so most of the brightness settings would work, but if you tried to set it to 0, it would really set it to -1 and all hell would break loose)
The reason it works so well for windows, is because when a hardware manufacturer makes a piece of hardware (wifi card) they also provide drivers that are pre-made for that version of windows, that way windows can call on standard functions, and that driver will answer those calls! unlike computers, phones very rarely switch hardware, so the hardware manufacturers only give the information of how to make drivers to the phone manufacturers
i hope you get what im trying to say.... i tend to ramble
Klathmon said:
the problem most of the time comes from how the rom interacts with the hardware.
when an app needs to do something, it calls a function (for example turn on wifi) the rom gets this call and passes it to the kernel. the kernel then passes this call to the hardware which powers on the wifi.
APP>ROM>KERNEL>HARDWARE
a problem can occur at any point in that chain. the app can call a function that does not exist in that version of android, or the rom can call part of the kernel which is not there, or the kernel can try to do something that cant be done hardware wise.
oversimplifying it, porting a version of android is basically matching the function calls from the rom, to that of a kernel that works for this phone.
Now, alot of the problems we have been having with ICS on our phones is because of Hardware Acceleration. we have no offical kernel that supports it. without that we have no way for the calls from the rom to get to the hardware.
the INCREDIBLE devs at Cyanogen figured this out, they wrote those functions themselves. the part that makes this incredible is the fact that they did not know what to call, or where to send it. they had to guess at EVERYTHING! unfornately this also causes problems, while they may have gotten the functions 90% correct, 10% is still wrong. and that is what is most likely causing problems for us. (a stupid example i saw once is that they made a new brightness driver, but it was off by 1 number, so most of the brightness settings would work, but if you tried to set it to 0, it would really set it to -1 and all hell would break loose)
The reason it works so well for windows, is because when a hardware manufacturer makes a piece of hardware (wifi card) they also provide drivers that are pre-made for that version of windows, that way windows can call on standard functions, and that driver will answer those calls! unlike computers, phones very rarely switch hardware, so the hardware manufacturers only give the information of how to make drivers to the phone manufacturers
i hope you get what im trying to say.... i tend to ramble
Click to expand...
Click to collapse
That's a very good explanation! Makes perfect sense to me.
Sure does!!!
Sent from my LG-P999 using xda premium
I have been a Fan of Beanstalk rom 4.4.247 that was recently released...however, I have formatted/wiped the cache and did the clean installation of the ROM and still I have noticed that the Audio and video stops playing while the phone is off and playing in background....
Also, to add to it...I am also seeing the phone is getting heated with this custom rom...any fix for this...too...would really help
I tried other players and still nothing seems to work just that the audio stops playing... I can't post this as I am new this world of Beanstalk and need help in fixing the audio/video to continue using the custom roms and I really need to move from Stock to custom...however, some bugs like this changes my mind to goback though I am not intented to....
Please help me to fix the issue or let us know if anything I need to do to resolve this or need your advice...please help
Many people have the same problem as I do with xperia l. Any game which uses dual joysticks or both fingers for movement and aim will cause each other to be affected such as suddenly stop moving and such even though the multi touch test shows nothing wrong. Now after researching, the only solutions I found for 4.2.2 with latest official firmware (which is what I have) are;
1) downgrade to 4.1.2 (which I'm not a fan of)
2) you can't due to the hardware (which I doubt because some people don't have the problem but I don't know what they're running)
Now I want to clarify for certain what is a proper fix for this. The OI gaming rom or something said it fixed the multi touch problem but is it the problem I have or the old buggy problem where you couldn't even use both your fingers at the same time?
Can someone just tell me that if I flash a custom rom, will the problem still persist? Or is it truly a hardware problem?
hardware problem.
Tyrano71 said:
Can someone just tell me that if I flash a custom rom, will the problem still persist? Or is it truly a hardware problem?
Click to expand...
Click to collapse
It is a hardware problem...
Latest stock firmware (.17) seems to tone it down a bit. Its still there.....but much,much better then previous firmware.
(and i dont know what are you talking about 4.1.2 because the multitouch is 10x worse there)
Im on stock .17 and i can finnaly play FPS games just fine with minor multitouch issues....
And no....custom roms wont help.
If this is a hardware issue, is it possible to use a joystick instead? I haven't seen anyone test this. And all I have is one of them usb controllers but there are apps that allows it to be a usable android joystick. My only problem is that it emulates the touches, would it be affected by the hardware issues?