yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] Misledz:
Like I said, You clearly haven't understood the situation, If this is a Wifi hardware related issue then the Wi-Fi wouldn't even work in the first place.

I have tried numerous ways, Even flashed vivek's Wifi Fix for CM7 in hopes that the modified files would work. But to my surprise, Nada. That didn't work aswell.

It could be a sleep issue?
[Samsung Galaxy SL i9003] skchattha:
Dear skchattha,

Kindly update me with your method of updating to 2.3.5 XXKPM on i9003. Also state your firmware version before update. Curious to know and test your way.

@sonopixy

I was having XXPKH, directly flashed to XXKPM (no XXKPE in between) and it worked like charm every time.

Not sure but may by your internet router/modem settings you can change; which might be compatible with XXPKH but not with XXKPM.

I don't think SAMSUNG would leave such big hole in their latest ROM. You should also directly ask SAMSUNG for the same.
[Samsung Galaxy SL i9003] sonopixy:
Wifi Sleep Policy: NEVER

Guys this is a genuine bug with the XXKPM ROM but some are facing it some are not. I wonder why.

To the guys who are facing it,

I have downgraded to XXKPH and everything fine. I am going to attempt to update to XXKPM again using Samsung KIES.

If anyone has tried KIES way of update (after facing WiFi problem after Odin Flashing) and have found a solution, please share.
[Samsung Galaxy SL i9003] chongns:
@misledz

i have this when i 1st flash kpm, same as your problem, wifi is on but icon is gone.

but some how, i do mistake in ext4 convertion, than i reflash kpm.

than, found the wifi become normal again. the last thing i remember is setting the wifi policy.
[Samsung Galaxy SL i9003] Misledz:
I never touched the WiFi policy, By default it should be set to "Never turn off" , I've flashed every single GB firmware there is almost 40-50+ times due to testing and I've never experienced any Wi-Fi issues or change in policy, be it stock or something else until I flashed XXKPM. :mad:
[Samsung Galaxy SL i9003] crackerizer:
Thanks for making this thread. I have this issue with the xxkpm. I spent a couple days tried to solve the problem but end up with xxkph. I really like the kpm, it is fast and much more responsive. I would be glad if someone can come up with a fix. below are my experience with kpm.

1. the Wi-Fi problem, my workaround is set the IP address manually.

2. seems like there is no problem with some AP (work good at my office but at my house and a coffee shop)

3. the phone do factory reset by itself from time to time after converted to ext4. this is very bad behavior.

4. wifi signal is weaker than xxkph

I may not be an expert but did a lot of firmware update. I already tried anything I can think of but no luck. Hopefully, we can have a fix soon.
[Samsung Galaxy SL i9003] Jack_Random:
exactly

The message you have entered is too short. Please lengthen your message to at least 10 characters.
[Samsung Galaxy SL i9003] Misledz:
Common, Really :\ This issue has already been addressed as an issue handset specific.

I've come across a certain thread that has rectified this issue.

Sadly, Its I9000. I wonder if we share the same Wifi Files. Cause it just may work?

http://androidadvices.com/fix-galaxy-wifi-disconnection-poor-coverage-issue-xxjvs-235/
[Samsung Galaxy SL i9003] falex007:
As I said before in this forum I had a big problem with connection to mi WiFi router:

I can connect to it with my phone with Froyo ROMs, I can connect to it with all my laptops and book readers, but when I flash any GB ROM (stock or even CyanogenMod7) I have problems with ping even google dns (8.8.8.8): about 80÷90% of lost packets.

But Misledz sent a link to the solution for i9000. I took that file and saw that they just changed configuration files in the /system/etc/wifi directory. I took the configs from XXKB3 and replaced GB files with them. And now my problem is solved! :)

in the attach there is a files that I used.

How to install:

1. download the attachment (wifi_xxkb3.zip)

2. with help of root explorer backup /system/etc/wifi directory

3. extract all files from attachment

4. copy extracted files to /system/etc/wifi

If it's interesting I can create update.zip format file to apply it with CWM.

Also remember YOU MAKE IT AT YOUR OWN RISK AND I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE

Also I attached original files from CyanogenMod7 (but I think they are the same as in stock GB ROM)

PS: Now CyanogenMod suits me at all (I have WiFi with home router and I can make photos too :) )
[Samsung Galaxy SL i9003] Misledz:
LOL Bro, I'm glad in a way it works for you, Maybe your hardware is more I9000 oriented than I9003. Regardless from which I wasn't sure those files would work but seem's they are similar on a certain level :] Glad they worked for you bro

Wonder if this might work for XXKPM, Will check later perhaps.
[Samsung Galaxy SL i9003] franzo15:
i've the same issue, but i notice that if i use fix ip address, wifi works perfectly, without lose signal every 60~65 seconds.

I notice that with other access point / wifi router, wifi works with dhcp too.

So, i can think that it's a problem due to dhcp lease or other similar around this.

I'm investigating in /system/etc/wifi folder from KB3 and KPM... there are some difference between config files... i'll continue investigate!!
[Samsung Galaxy SL i9003] falex007:
With my router I had problem with any static IP/ DHCP, WPA2/WEP/unencrypted connection. And the problem was solved only with replacing the config files. About difference: yes I saw this and that;s why I thought to replace the config files.
[Samsung Galaxy SL i9003] franzo15:
I replace the config file from KB3 but it's the same: wifi loose signal every 60~65 seconds if IP address come from DHCP. With fixed ip address no problem
[Samsung Galaxy SL i9003] Misledz:
XXKPN released, Maybe it fixes the issues.
[Samsung Galaxy SL i9003] user28:
So has anybody updated to XXKPN ? Are the bugs fixed? Please anybody post the results here.
[Samsung Galaxy SL i9003] pulsar_swift:
Team,

What is the final solution for this wifi issue on XXKPM ?
[Samsung Galaxy SL i9003] manojks256:
Hi Guys,

I have disabled DHCP on my Router, and assigned static IP Address to my Moblie.

Now its working fine. No issues...

Thank you soo much franzo15

I am suffering a lot with this issue from past 2 days. Finally got solution by you.

This site is helped me a lot. I am new to this site. This is my first post.

Thanks again... Keep rocking...
[Samsung Galaxy SL i9003] srain:
I am facing the same issue with wifi after flashing to DDKP3 from XXKPH no solution worked for me
[Samsung Galaxy SL i9003] Misledz:
I found the problem and the fix to it, It's DHCP, some users who have Belkin router's tend to have DHCP issues with the router. XXKPM/XXKPN has nerfed certain router compatibility so take note.
[Samsung Galaxy SL i9003] cmax24:
and how can i resolve it?? i have belkin router... :(

2. i resolve the issue with a static ip and disabiliting dhcp.... but how is possible xxkph (2.3.4) don't have this problem while xxkpn (2.3.5) have this issue... the updates do hurt
[Samsung Galaxy SL i9003] Misledz:
[Copy pasted from my post in FB]

Finally XXKPM/XXKPN Wifi issues rectified. They nerfed the DHCP timeout phase, in which the router's would constantly communicate with the phone to check if the set IP is in use therefore generating a new one everytime. The fix remains as disabling your DHCP Client table in your router [Most have 192.168.XXX.XXX] as their default router IP. You need to configure the following

Warning before you turn off your DHCP table you need to know your ISP DNS address. If you don't know, search it up in your routers, Check the "Automatically from ISP" if you use a PPOE connection. Copy down DNS1 and DNS2.

IP Address : generated from router, you must know this.

DNS : ISP DNS you should know this too

Netmask : 255.255.255.0 , Prefixed.

Gateway : Router IP Address.

To enable this on your phone, You need to go to WiFi, turn off the WiFi first, then Menu button, and press Advanced -> Use Static IP [ ] Tick the box and enter the details

Warning: You may need to do the same for your PC
[Samsung Galaxy SL i9003] -MattiX-:
probably not.. I've the same issue with XXKPN... and i do not have a belkin router...
[Samsung Galaxy SL i9003] Misledz:
Attempt a static IP :)
[Samsung Galaxy SL i9003] omkarroxx:
when I was on froyo, there was this problem wifi was contineously disconnected, but when I updated to XXKPM, problem was solved.. did you flas XXKPE before XXKPM ?
[Samsung Galaxy SL i9003] inciongd:
So far I have read this thread and a some people are saying that they do not experience the issue. It is probably because they have a good/compatible/lucky router.

1. Lots of posts where people say they experience the issue

2. Lots of posts people say they don't experience the issue

3. No posts saying they fixed the issue (by changing phone not changing router settings)

The router change in DHCP is just a workaround, it's not a fix.

I am now using XXKPQ (2.3.6) and I am still experiencing this issue. Wifi works well when I turn of DHCP on my D-Link DIR-655 router, otherwise, not. However I am not keen on turning off DHCP permanently on my router as I use my desktop as a webserver plus I don't want to go and setup all the devices of my housemates with manual IP settings.

I have a brown SGSL bought in Asia, here is my flashing experience:

1. Bought phone with DXKB1 as default

2. Flashed to DXKP9 via Kies (Asian 2.3.5)

3. Experienced the Wifi issue for the first time and tried to fix it before seeing this thread so i...

4. First flashed directly from DXKP9 to XXKPQ

5. Learned that I should not flash directly from KP9 to KPQ so...

6. Flashed DXKPE twice

7. Flashed DXKPQ twice

8. Saw this thread

So I am sticking with KPQ now because I like the snappiness.. I will just try to live with the intermittent disconnections. I hope there is a fix soon.

I just would like to report that it is not yet fixed on the phone side even with the latest FW (at least for me), although there is a router workaround.
[Android Software/Hacking General [Developers Only]] tevil:
just found this on IGN

not sure if its really news but hell i thought it was neat.

http://www.ign.com/articles/2011/10/20/will-your-device-get-android-ice-cream-sandwich
[EVO 4G General] ctzw:
I flashed MIUI recently. However, I found there was nothing coming out when I dialed coded numbers like: ##3424# (DIAG MODE), or ##786#, or ##3282#. These numbers used to work under other ROMs. But somehow, they are disabled in MIUI. Any solutions?
[EVO 4G General] HipKat:
Those only work on Sense Roms, not on AOSP Roms
[EVO 4G General] ctzw:
Thanks. Is there a similar way to edit the related settings in the phone? I'd like to edit some settings in ##3282#, any equivalent command in AOSP roms?
[EVO 4G General] {ParanoiA}:
No. U have to flash between sense & aosp to use them

Sent From My Pocket
[EVO 4G General] Jfree3000:
No, you have to flash a sense rom to access anything in those menus.
[EVO 4G General] skumar9988:
Install HTC Diag Driver on your PC (Windows OS) and make sure it recognize your HTC Phone.

Enable USB Diagnostic on your HTC Phone. If You don’t understand step 1 and step 2 then forget it, you’re not ready for this yet.

Install adb tool on your PC (just copy paste it to an easy accessed directory on your pc. i.e c:\adb

No, you don’t need Android SDK, or JRE, etc, You just need this tool, about 500Kb in package. Google for it!

Enter the abd mode c:\adb> adb shell

You need to alter the value of enable file located in your phone (/sys/devices/virtual/usb_composite/diag/enable) file from 0 to 1. here’s how :

full path :

echo 1 > /sys/devices/virtual/usb_composite/diag/enable

you don’t have to remember that. You can enter each dir manually and if you forget the next dir you can simply command ls to list directory and file available. After you reach the last dir (/diag) then you can execute theecho > 1 enable command.

Voila, you enter HTC Diag mode on AOSP ROM.
[EVO 4G General] jgra_2003:
im trying your method, but the /diag/enable reset to 0 again after reboot the phone
[EVO 4G General] Pachonk:
Yes bud, this is normal.
[Click General] KingCreole:
As Ginger waste my battery too quick, I decided to put Froyo on my Tattoo.

I tried first with [ROM] ProjectSense 0.1 [2.2.1] [Sense], which is going great ... but no radioFM.

As I use FMradio a lot (for football, of course), I have been looking and I found [ROM] Latest Froyo AOSP for Tattoo v0.50 released (Final Version) and flashed it.

After a long search to find a working GAPPS for that rom (I found it at goo-inside.me), I've flashed it, but my phone stucks on trying to access Google's servers, and have no way out of there unless you turn off the phone.

Anyone else with him?

So difícult is making an FM radio app to work in sense? (the only thing missing from the ProjectSense to be perfect)

Do not be a matter of adding a "driver" or library to "activate" the chip, and so run the "Spirit FM Radio", for example?

If anyone has any answer is welcome.

Sorry for my english (Google Translator doesn't help too much)
[Click General] VuK$3:
Flash this gapps they will work. :)

http://xdaforums.com/attachment.php?attachmentid=424059&d=1287687798

Hit that tiny tnx button if they work xDD
[Click General] KingCreole:
Thanx. By the moment, i'm gonna use ProjectSense Rom. I'll try later if I need it.

Enviado desde mi HTC Tattoo usando Tapatalk
[Click General] mikereidis:
"Spirit FM Radio" is my app. It doesn't care about Sense.

But for a TI chip device like the Click/Tattoo, it requires a Bluez compatible Bluetooth stack, as is found on CM and some other ROMs.

Also, my app needs a way to turn on the FM audio path. On a Sense based ROM this might be the "HTC" Audio Method that needs to be configured.
[Click General] KingCreole:
I supose the problem is ar bluetooth stack, as you say, because ProjetcSense isn't a CM based rom. I installed your app, and configured audio method in all the posibilities, included "HTC", but it's allways saying me "compatible chip not found", or something like.

Today I'm gonna make a backup, an change some files from other Froyo Rom with FMradio working. Another thing I'm going to try is changing some values in build.pro, cause this Rom has BT chip identified as BCM4329-B1, but I read in some threads it's a different one.

Thanks anyway.
[Click General] KingCreole:
The exact message is:

"Sorry, compatible FM chip not found...:(

FM:TI Sh:1 Su:1 Bt:0 Ht:0 H2:0 M0:TIU"

I think it means.. "FM chip is TI, but BT is 0, so I can't make it works". And now, th question is... why BT:0, if Bluetooth is on?
[Click General] VuK$3:
I was cooking a sense 2.2.1 ROM and I made everything work except FM radio.I fond mikereidis thread about TI chip but i was unable to enable it :(

When I try shell command it always says access denied....

Any ideas ?
[Click General] KingCreole:
Something has changed.

I tried to use the fm_script by cm.fyodor, and when I wrote the comman at Terminal CMD, I receive many lines resumed on two: "bttest: not found" and "hcitool not found".:confused:

Looked for the files at Fyodor's [ROM] Latest Froyo AOSP for Tattoo v0.50 released (Final Version), and found them at /system/xbin. So, I'd copy the files to my phone, and retry the "Spirit FM Radio".

But the message I had (2nd line) now is "FM:BC Sh:1 Su:1 Bt:1 Ht:1 H2:0 Mo:BCU".:eek:

After it, I edit settings->debug and check "Use fm_hcitool" and set FM chip to "Automatic", but app is still not working.:(

I've deleted info about BT chip in build.prop. Now, when I try to execute fm_script, the message is "HCI command: XXXXXX Send failed: File descriptor in bad state". Back to previous build.prop, same message: "Send failed":mad:

I'll keep on trying things...
[Click General] mikereidis:
I'm pretty sure this device uses a TI chip for FM, BT and WiFi. My app, and the script that I think came from me originally, was working on this device back when my app generally only ran on the HTC Legend. I think these are the only 2 HTC devices using the TI chip.

Yes, I think the problem is that stock HTC ROMs use the Broadcom or TI proprietary Bluetooth stack. So just about anyone making a Sense based ROM uses that same stack.

"Send failed: File descriptor in bad state" happens when trying to use hcitool with the proprietary stack. (But can also happen with other fatal errors that are fixed by restarting BT.)

If I am correct, then I'd think the HTC FM app would work. Is there a btipsd process running ? That's the proprietary TI stack. On the Legend, there is a btipsd_cli binary that my app can use with this stack. I don't think anyone by myself has ever used this mode, LOL.

Here's the binary if you want to try. The btipsd version might need to match somewhat though: http://www.mediafire.com/file/p0w159ubto2frw6/btipsd_cli.zip

If you copy files from a Broadcom based BT device, then you can confuse the automatic FM chip detection, which is why I think you saw "Mo: BCU" (Broadcom unknown.) You can force to TI still.

Changing audio method won't help until we can see RSSI and seek working,

So, options:

- There's likely some way to run the HTC FM app for Tattoo/Click or Legend if the TI stack.

- My app will work with Bluez stack

- My app might work with btipsd in the TI stack via btipsd_cli.

- I may at some point support a "direct to BT UART mode" that works with BT off, as I have for Broadcom chips.

- I'm also looking to support the Broadcom and TI stacks more directly, but this likely won't happen for several months at least.
[Click General] mikereidis:
This part of my code doesn't care whether or not Android thinks BT is running.

If any of the following processes are running, it will show "BT: 1":

For Bluez BT:

hcid

bluetoothd

hciattach

For TI proprietary BT:

btipsd

For Broadcom proprietary BT:

btld

brcm_patchram_plus
[Click General] KingCreole:
Ok, this is starting to go!!!

I copied your file (btipsd_cli) to /sistem/bin, and after a reboot, start your app. First time, it doesn't work, so I changed settings->debug->FM chip to "Tex Instr (Motorola)", and... Voila!! THE APP IS WORKING!!! But no audio.

The text strings I can see are:

- 0 Aud?

- PI: -1

- Fm:TI Sh:1 Su:1 Bt:1 Ht:1 H2:0 Mo:TIB
[Click General] KingCreole:
After many tries, I noticed this rom got "btld" file ( Broadcom propietary), but no "btipsd" other than btipsd_cli file i've copied.

I'm sorry, but i've no skills enough to understand "processes"...

And... yes, BT:1

I'm still thinking something is wrong in build.prop with BT chip identification:

" # release Bluetooth HW/SW information

ro.bt.chipset	= Broadcom BCM4329-B1

ro.bt.version	= Bluetooth 2.1 + EDR

ro.bt.stack	= Broadcom BTL-A

ro.bt.stack.version	= 2.0.47.005

#0x10000010010100100000011 represent bt profile list

ro.bt.profiles	= 4270339"

Why "ro.bt.chipset= Broadcom BCM4329-B1", if it's TI???
[Click General] mikereidis:
Woohoo ! :)

I've had this "weird" btipsd mode in my app for probably 6 months now and you're the first to report using it. I'd been considering removing it, since it has various problems.

Did you try all the different Audio Methods under Menu -> Settings -> Audio ? You can tune a good station and stay in that config screen trying them all.

Most likely to work I think is the HTC method, although one of the strangely named methods like msm7x30 may work.

Send me a log and I can look. Select Menu -> Help -> EM Logs.
[Click General] mikereidis:
Yes that's rather strange. I can't imagine you have a Tattoo/Click variant with a different chip.

I've been seeing more "universal" ROMs lately that have files for both Broadcom and TI. This makes my automatic chip detection fail sometimes, so I created the Settings -> Debug -> FM Chip option to force a chip type.

Send me a log and I can look. Select Menu -> Help -> EM Logs.

Thanks !
[Click General] KingCreole:
I can't imagine it too. I got installed a CM7 rom with Gingerbread, and your app works perfectly.

I've tried installing HTCMusic.apk from a Donut Sense rom (this app controls both music and FMradio), but gives me a FC (I supose it's normal). I've tried to install FM.apk from an AOSP Froyo rom, but it doesn't work too.

I've sent the log. Thanks for your dedication.
[Click General] mikereidis:
Normal ? Well something is missing or wrong.

Assuming your BT stack is proprietary from TI, I'd bet you could run the FM app from a stock Legend. It's just FM, no music. But I'd rather you run my app.... :)

I'm not aware of any AOSP ROM with an FM app. That would mean Google source code for an FM app and I've never seen any,

I haven't seen any log email from you. Perhaps it didn't go through or I don't know which email is yours. You could just send me the /sdcard/*.txt files that came from my app.
[Click General] KingCreole:
After I received your mail, I noticed something I didn't give any importance in the past: this Rom is ported from HTC Wildfire!

So, I think the dev "mixed" files to make BT work.

I'm gonna try some file changes, and tell what happen.

Enviado desde mi HTC Tattoo usando Tapatalk
[Click General] mikereidis:
And the Wildfire has Broadcom BT/WiFi/FM. Makes sense.

So the ROM will need some additional files, like TI's btipsd, and the startup file(s) will have to initialize the TI BT.

With the ROM you have now, Bluetooth can't work. Make it work with btipsd and my app may work in the TI btipsd mode. I think your apparent previous success in this mode was false.
[Click General] KingCreole:
I'm afraid so. I have no bluetooth device to check it.

I've spent some hours on selecting files from a Legend's Froyo Sense custom Rom, and after paste them on my phone, the only difference is your app isn't showing the "Aud?" string (but, of course, there's no audio).

I'll continue tomorrow.

Enviado desde mi HTC Tattoo usando Tapatalk
[Click General] VuK$3:
I tested Bluetooth on TatFroyoSense,it sometimes work and sometime not...so u must restart phone to work again ,and u cant transfer bigger files becaouse it stops working...:(
[Click General] rallapag:
Interesting topic guys, will be following you.

That was a ported app from MIUI, here is the link for Fyodor git

https://github.com/fyodor/android_packages_apps_FM

Yes this ROM has problem, mostly can do file transfer OK, but i couldn't get bluetooth headset working

How big file did you try to move, I have tried up to 2MB no problem in transfer
[Click General] rallapag:
i have tried to follow the steps that has been discussed so far

and attaching the log you asked for

Hope this helps to understand the problem
[Click General] VuK$3:
I transferd multiple files (few songs and apps) between two htc tattoos,it never transfers all files always some error... :mad:
[Click General] KingCreole:
I supose we have to wait for the devs having time enough for this. Drivers and librarys have to be changed to meet the rigth BT chip, and make it works.

At least, I found the right gapps for the [ROM] Latest Froyo AOSP for Tattoo v0.50 released (Final Version). (thaks to KevinCupraR at Htcmanía). The file is here.:)

"Be patient, my friend..."
[Click General] VuK$3:
How about porting sense to Ginger?? :D
[Click General] KingCreole:
As I said at post #1, I've tried Ginger, and it drains my battery too fast. But, if at any moment they do something about it, I'll try it again.

About porting Sense, I've no knowledge on programming. I hope someone want to do it, but I think first issue they're gonna find is the free RAM ammount left after system + UI are loaded.

Enviado desde mi Click usando Tapatalk
[Click General] mikereidis:
That's what I call the CM FM app.

The MIUI devs started with the "Code Aurora" app to create their MIUI app.

The CM devs started with the MIUI app and created their CM app. One of them added support for TI chips, based on work I did.

CM and MIUI apps are now distinct despite the About for CM App saying "MIUI".