Related
I tend to be dependent on Wi-Fi calling at some times. Would anybody have a CWM zip that can enable this in miui? I tried installing the apk from another Roman, but it wouldn't install.
Sent from my SGH-T959V using XDA App
Wifi calling on miui was also a problem on the vibrant as i recall
Sent from my SGH-T959V,SGH-T959 using xda premium.
I have no idea the dynamics of Miui...
But enabling WiFi calling on an early release required adding back code to the build.prop and required some lib files. Raver has mentioned in his Miui thread that he "gave you a more standard build prop" on his upcoming release. You may wait until then and see.
I've been trying a few JellyBean roms and they work quite smoothly I must say
but one feature that is still missing for me is the hability to connect to adhoc networks just like in old modded ICS roms.
I've patched and recompiled Team EOS3 wpa_supplicant that allows to see adhoc networks.
(although it should be the same source for other JB roms most likely too)
Unfortunately using Roach's default kernel it still doesn't list adhoc networks,
by using Guevor's kernel V23-JB-EOS it is able to list them.
However it is timing-out while trying to connect to it. :\
I'm not sure, but it might be related to the wifi module that comes with the rom / kernels.
If anyone knows what else should be changed in order to get it to work, feel free to contribute
It'd be nice to get it working on JB again
If you want to give it a try and report what works or doesn't work with each rom / kernel combination of your choice, I've attached the modified wpa_supplicant.
To test:
- turn off wifi
- su and remount /system rw
- mv /system/bin/wpa_supplicant /system/bin/wpa_supplicant.ori
- gunzip the file
- cp wpa_supplicant /system/bin/
- chmod 755 /system/bin/wpa_supplicant
- turn wifi back on.
If you want to switch back to the previous wpa_supplicant:
- turn off wifi
- mv /system/bin/wpa_supplicant.ori /system/bin/wpa_supplicant
- turn on wifi
Click to expand...
Click to collapse
Credits:
- jl7854 for the wpa_supplicant ICS patch.
- Team EOS for the original wpa_supplicant and EOS3 JellyBean rom sources.
I know this is for Transformer so my post is pretty off topic, but this actually is the first modified wpa_supp that allows me to turn on wifi again on Nexus S with stock JB. Unfortunately it doesn't show me ad hoc network either
The only ICS ROM that works in adhoc mode for me is Revolver. I have tried Guevor and Harmnony kernels and they both work. I wish I knew more to help the cause. Ricardopvz started to work with me to fix this in Megatron but he got sidetracked and never continued. I suppose someone could look at the driver in Revolver to see how that one works and see if the changes can be ported to JB.
Adhoc tethering is important to me because my old Droid-1 can't tether to my tablet in infrastructure mode. Bluetooth tethering is slow and inconvenient. Thanks for carrying the flag on this. I will try to help with the testing.
jenda.69 said:
I know this is for Transformer so my post is pretty off topic, but this actually is the first modified wpa_supp that allows me to turn on wifi again on Nexus S with stock JB. Unfortunately it doesn't show me ad hoc network either
Click to expand...
Click to collapse
Ah yeah, glad it could help still
I don't think wpa_supplicant is much different from rom to rom, so good to know that one works on Nexus S too.
Next is to figure out what might be missing either in the rom or in the wifi module or such...
archcantor said:
The only ICS ROM that works in adhoc mode for me is Revolver. I have tried Guevor and Harmnony kernels and they both work. I wish I knew more to help the cause. Ricardopvz started to work with me to fix this in Megatron but he got sidetracked and never continued. I suppose someone could look at the driver in Revolver to see how that one works and see if the changes can be ported to JB.
Adhoc tethering is important to me because my old Droid-1 can't tether to my tablet in infrastructure mode. Bluetooth tethering is slow and inconvenient. Thanks for carrying the flag on this. I will try to help with the testing.
Click to expand...
Click to collapse
Thanks
I have the same problem with my Nokia phone, it can only do adhoc network for sharing its 3G connection.
I can connect fine through it with bluetooth from a PC too, but android is not able to see the modem through bluetooth unfortunately.
So I definitely need adhoc to work
Maybe Ricardopvz or someone could participate for the JB roms if they have an idea what to modify next, I can have a look too.
I'll have a look in what could be changed in the BCM wifi driver in the meantime.
This makes the RaymanFX CM10 ROM see ad-hoc's but timeout on connect. Hope someone will fix this as ad-hoc is kind of necessary for me
theres a few things that have to in place for ad-hoc connections to work. just modifying the wpa_supplicant is not the answer. first the linux kernel on your device has to have CONFIG_NETFILTER, CONFIG_IP_NF_IPTABLES, and CONFIG_NETFILTER_XT_MATCH_MAC features. These are required for tethering (ad-hoc) to work in linux/android. also binaries like iwconfig will need to be included. ad hoc connections from droid to droid are sketchy and flaky because there are so many different kernels, wireless cards, and third party apps on so many different devices. I see why so many people dont like to use bluetooth tethering. typical cellular data service data transfer rates are much slower than the theoretical limits of Bluetooth, making the potential higher bandwidth of WiFi irrelevant.
these are the theoretical maximum speeds for various Bluetooth versions
Bluetooth Basic Rate (BR) 1Mbit/s
Bluetooth 2 Enhanced Data Rate (EDR) 2-3Mbit/s
Bluetooth 3 + HS (high Speed) 24MBit/s
So on the face of it, Wifi will normally give you a faster connection however the limitation is probably going to be the speed of your phone's data connection.
haxin said:
theres a few things that have to in place for ad-hoc connections to work. just modifying the wpa_supplicant is not the answer. first the linux kernel on your device has to have CONFIG_NETFILTER, CONFIG_IP_NF_IPTABLES, and CONFIG_NETFILTER_XT_MATCH_MAC features. These are required for tethering (ad-hoc) to work in linux/android. also binaries like iwconfig will need to be included. ad hoc connections from droid to droid are sketchy and flaky because there are so many different kernels, wireless cards, and third party apps on so many different devices.
Click to expand...
Click to collapse
Well, what I'm trying to achieve here is connect to an existing adhoc network which would already be doing the NAT, so you wouldn't need any of that on the client tablet.
Android doesn't use iwconfig by default.
Netfilter/iptables support would be in cases you'd in addition want to share your internet connection through the tablet.
For connecting to an existing adhoc network, it mostly boils down to wpa_supplicant and the kernel wifi driver, and maybe some android-space process
But seeing that it times-out while trying to connect even by using directly wpa_cli commands, that should eliminate the android space process from the loop.
That should leave only wpa_supplicant and the wifi driver.
timduru said:
I've been trying a few JellyBean roms and they work quite smoothly I must say
but one feature that is still missing for me is the hability to connect to adhoc networks just like in old modded ICS roms.
I've patched and recompiled Team EOS3 wpa_supplicant that allows to see adhoc networks.
(although it should be the same source for other JB roms most likely too)
Unfortunately using Roach's default kernel it still doesn't list adhoc networks,
by using Guevor's kernel V23-JB-EOS it is able to list them.
However it is timing-out while trying to connect to it. :\
I'm not sure, but it might be related to the wifi module that comes with the rom / kernels.
If anyone knows what else should be changed in order to get it to work, feel free to contribute
It'd be nice to get it working on JB again
If you want to give it a try and report what works or doesn't work with each rom / kernel combination of your choice, I've attached the modified wpa_supplicant.
Credits:
- jl7854 for the wpa_supplicant ICS patch.
- Team EOS for the original wpa_supplicant and EOS3 JellyBean rom sources.
Click to expand...
Click to collapse
Didnt break the wifi card, but everything acted like the original file. No ad-hoc.
With the file i can see the ad-hoc networks around but can not connect them...
Sent from my HTC Sensation using xda premium
little off topic..but might help for those wanting a quick fix..
http://forum.xda-developers.com/showthread.php?p=32719405
confirmed working for me..
Foxfi running on papasmuffs CM9 HTC EVO build..
using 'Pdanet Tablet' on the Asus Transformer stock rooted .27
Thanks for the thread as was going nuts playing with the old tether program..
Search is your friend
Click to expand...
Click to collapse
Sent from my Transformer TF101 using Tapatalk 2
not work for me. I am running AOKP JB.
baseband: I9300BULE6
Any help for this matter?
yea i cant tether from my phone because the script finds the ad-hoc network but it wont connect to it
Sent from my Transformer using Tapatalk HD
Model : GT-I9000
Android V: 4.2.1
Baseband : I9000XXJVT
Karnel v: 3.0.60-Samaphore_JB_2.9.8s [email protected]
Build: Tsunami X 4.2
wpa_supplicant fix is not working for me
timduru said:
I've been trying a few JellyBean roms and they work quite smoothly I must say
but one feature that is still missing for me is the hability to connect to adhoc networks just like in old modded ICS roms.
I've patched and recompiled Team EOS3 wpa_supplicant that allows to see adhoc networks.
(although it should be the same source for other JB roms most likely too)
Unfortunately using Roach's default kernel it still doesn't list adhoc networks,
by using Guevor's kernel V23-JB-EOS it is able to list them.
However it is timing-out while trying to connect to it. :\
I'm not sure, but it might be related to the wifi module that comes with the rom / kernels.
If anyone knows what else should be changed in order to get it to work, feel free to contribute
It'd be nice to get it working on JB again
If you want to give it a try and report what works or doesn't work with each rom / kernel combination of your choice, I've attached the modified wpa_supplicant.
Credits:
- jl7854 for the wpa_supplicant ICS patch.
- Team EOS for the original wpa_supplicant and EOS3 JellyBean rom sources.
Click to expand...
Click to collapse
babai93 said:
Model : GT-I9000
Android V: 4.2.1
Baseband : I9000XXJVT
Karnel v: 3.0.60-Samaphore_JB_2.9.8s [email protected]
Build: Tsunami X 4.2
wpa_supplicant fix is not working for me
Click to expand...
Click to collapse
Babai,
Check out this thread.. I posted into EOS#4 thread the other day as I read somewhere some other's where having problems.. as you can see I am running the same phone as you.. but I am on Yanks kernel.. Look for my post in that thread and you will see the setup that worked for me.
I was reading through the posts today and through I come across some guy with tethering issues..
I just upgraded to #94 and are using this tether program with the SIII I9000, working great...
[App-Mod/Source] WifiTether for JB TouchWiz Roms
http://forum.xda-developers.com/showpost.php?p=34037922&postcount=1
That is Phone to Transformer.. not the other way around..]
Click to expand...
Click to collapse
So what I have to do now to get it works? I using windows mobile to share internet over WiFi hot spot.
Wants to access all my android mobile will get connected to the WiFi hot spot .
dgcruzing said:
Babai,
Check out this thread.. I posted into EOS#4 thread the other day as I read somewhere some other's where having problems.. as you can see I am running the same phone as you.. but I am on Yanks kernel.. Look for my post in that thread and you will see the setup that worked for me.
Click to expand...
Click to collapse
babai93 said:
So what I have to do now to get it works? I using windows mobile to share internet over WiFi hot spot.
Wants to access all my android mobile will get connected to the WiFi hot spot .
Click to expand...
Click to collapse
Check out my post in that thread..
these are the settings I am using..
Working fine for me.. 3g & HCDMA out on my Android G. SIII I9000 - XXEMA2 - Deodexed
http://forum.xda-developers.com/showpost.php?p=37533605&postcount=398
dgcruzing said:
Check out my post in that thread..
these are the settings I am using..
Working fine for me.. 3g & HCDMA out on my Android G. SIII I9000 - XXEMA2 - Deodexed
http://forum.xda-developers.com/showpost.php?p=37533605&postcount=398
Click to expand...
Click to collapse
Serially I am not able to get any thing out of the post. Please guide in a simple way...
vess_csm said:
oh, would love if a solution for JB comes up
Click to expand...
Click to collapse
[MOD]Adhoc WIFI support for Android JellyBean (Tested
by me with JoikuSpot)
http://forum.xda-developers.com/showthread.php?t=2163363
pssecretajent said:
[MOD]Adhoc WIFI support for Android JellyBean (Tested
by me with JoikuSpot)
http://forum.xda-developers.com/showthread.php?t=2163363
Click to expand...
Click to collapse
i have tried this but still not working, any suggestion plz
Sent from my A15 using Tapatalk 2
I'm having a strange problem with every 4.1.X ROM i try. All apps that use location data seem to think it still needs to be enabled - even though it is. Gps on, Wifi and cell data share on, but I'm still reminded to enable them for better performance.
This isn't much of a problem with anything except Google Now. Maps still gets a gps fix despite telling me gps is disabled, but Now only shows the "enable location data" card. Any idea how to fix it? I've tried 5 different roms, fixed permissions, did several data and cache wipes, nothing works.
My sister has a stock S 4G with the OTA update and hers works flawlessly.
Have you tried flashing a custom kernel? Did you wipe data/cache/dalvik/boot/system before each ROM install? JB doesn't seem to play nice with some people's phones. Maybe 4.1.2 might fix your problem once someone gets it running on our 4G variant. Also, I believe this belongs in the NS general forum?
Sent from my Nexus S 4G using Tapatalk 2
I've used matr1x 22.5-23.5 along with stock kernel or included kernel variant packed with each rom and no luck.
And I AM running a 4.1.2 ROM right now, that's why I said 4.1.X because the issue is with both versions
Sent from my Nexus S 4G using xda app-developers app
Well that's interesting because I've never had such an issue with jelly bean but future reference don't post in android development section unless your releasing a ROM or kernel or even a recovery... I'm reporting this thread so it can be moved
Sent from my Nexus S 4G using Tapatalk 2
Hi Developers and Testers
Update: Upgraded to
[Flinny] Andromadus Test builds - CM10.1[10] Bluetooth working
[Flinny] Andromadus Test builds - CM10.1[9] Bluetooth issue - no change, patienece is needed
[Flinny] Andromadus Test builds - CM10.1[8] Bluetooth issue as below no change - unfortunately
[Flinny] Andromadus Test builds - CM10.1[7], still Bluetooth issue, acknowledged by developer Flinny as upstream i.e. google issue
However please check as below Samsung Galaxy S running with CM 10.1 no BT issue - Why?
[Flinny] Andromadus Test builds - CM10.1[6], unfortunately Bluetooth issue continues.
[Flinny] Andromadus Test builds - CM10.1[5], unfortunately same issue for Bluetooth.
Still connecting (pairing) but can not make call or receive call
Unfortunately I do not have enough posts so I can not add to the thread
[14-12-12][Flinny] Andromadus Test builds - CM10.1[4] (Development Section)
where this finding would belong, maybe somebody could paste it there http://forum.xda-developers.com/showthread.php?t=2031694.
I am testing the [14-12-12][Flinny] Andromadus Test builds - CM10.1[4] and it works great with my Desire S. Thanks Flinny for the sensational work.
However as with other testers I can not operate my in car Bluetooth speaker system, it connects (pairs) however I can not make or receive calls.
Following the thread it was mentioned that Google changed the Bluetooth code, therefore it would not work, especially with older build in Bluetooth car speaker systems
Today I installed on my second android device Samsung Galaxy S9000 CM 10.1 ROM (cm-10.1-20121221-NIGHTLY-galaxysmtd.zip) and tested bluetooth. I could pair, connect and make and receive calls. So I do not believe it is the Google code as such that is the issue for the BT not working with inbuilt car speaker system.
Could you experts please comment.
thanks,
Kla
Have a great productive 2013
What recovery are you using to flash it?
If you're not on 4EXT, flash 4EXT and reflash the ROM, then try again.
I had read about bluetooth problems on other recoverys...
Issue with BT upgraded rom 10.1 (4)
Jann F said:
What recovery are you using to flash it?
If you're not on 4EXT, flash 4EXT and reflash the ROM, then try again.
I had read about bluetooth problems on other recoverys...
Click to expand...
Click to collapse
Hi Jann,
I am using clockworkmod recovery.
Could somebody please explain why 4ext would make a difference to the BT issue?
Is there a compile error in clockworkmod?
thanks in advance.
Kla
I really don't know why, but it should solve this issue...
Just try 4EXT
klagor said:
Hi Jann,
I am using clockworkmod recovery.
Could somebody please explain why 4ext would make a difference to the BT issue?
Is there a compile error in clockworkmod?
thanks in advance.
Kla
Click to expand...
Click to collapse
I'm not an expert but the recovery ain't the reason. Everyone using the rom, no matter what recovery he flashes with, has it.
It is a bug and the developer has been working on it.
Sent from my Desire S using xda app-developers app
I have also issue with Andromadus Test builds - CM10.1[5] on Desire S with my car bluetooth.
Connect, but doesn't work.
I have no Bluetooth headset but I have other small issues.
- no access to contacts/sms on sim
- notification LED should be green not orange
I'm on build 4 anyone seeing this as well?
Sent from my Desire S using xda app-developers app
Bluetooth JB 4.2.1
On Jellybean 4.2.1 Google started using a new Bluetooth stack, they left Bluez and are now using Broadcom which is still giving problems (even on the official Nexus 4, Nexus 7, etc).
So have a bit of patience
Me am having problem with the wireless... Can't connect to my wireless Internet.. Wireless works just fine with cm7.. And Yes I did clean flash.. Wipe every data I need to
Sent from my HTC Desire S using xda app-developers app
bigkendo said:
Me am having problem with the wireless... Can't connect to my wireless Internet.. Wireless works just fine with cm7.. And Yes I did clean flash.. Wipe every data I need to
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Are you htcdev unlocked? Did you flash the boot.Img?
Why do they call it rush hour when nothing moves?
- Mork, Mork and Mindy
jugg1es said:
Are you htcdev unlocked? Did you flash the boot.Img?
Why do they call it rush hour when nothing moves?
- Mork, Mork and Mindy
Click to expand...
Click to collapse
Yes I am htcdev unlocked and
Yes I Flashed boot. Img via adb.. The wireless comes on, finds the network but does ever connect successfully and it only seem to only see WPA2 PSK wireless networks only.. Everything was working fine on CM7.2 I connect successfully to different type of wireless network
Sent from my HTC Desire S using xda app-developers app
New Bluetooth stack by Broadcom?
The new bluetooth stack (broadcom) seems to be causing a lot of problem with many users. Why did Google decide to use it anyway?
Could anybody tell me what the supposed advantages of this new stack would be?
I am (almost) forced to revert to CM10.0 because Android 4.1.2 still has bluez. It is quite frustrating so far, sorry to say this.
Is Android 4.2.2 the solution?
imaguari said:
Is Android 4.2.2 the solution?
Click to expand...
Click to collapse
NO. Android 4.2.2 is not the solution.
Also problems with sim contacts and it irritating me. Isnt there a solution?
A few days ago I got my new Galaxy Note 10.1 wifi edition (the n8013 I believe). I rooted it then flash the latest CM 10.1 nightly only to find wifi does not work... I subsequently tried a few other custom roms (I think they were all based on cm10.1 which may be the problem). Wifi will turn on and recognize my network but when I try to connect it simply says "connecting" and then a few second later goes back to "saved, secured with WPA2". I'm relatively sure it is not my router since my laptop and phone are constantly connected and my tablet could connect on TouchWiz.
I've looked all around XDA and other forums to see if anyone has this issue and I could only find one topic but it had no resolution. I figure this must no be too common since Wifi, at least for the n8013, is the only way of connecting to the internet.
Any one have a similar problem or know how to fix it? Should I try flashing a rom that isn't based on CM10.1? I could just go back to stock TouchWiz but I'd rather not...
There's some good roms that are based on stock. I never used cm 10.1 so I don't have an answer for that. I am on an experimental build of 10.2 and wifi works just fine.
Sent from my EVO using xda premium
fluffy312 said:
A few days ago I got my new Galaxy Note 10.1 wifi edition (the n8013 I believe). I rooted it then flash the latest CM 10.1 nightly only to find wifi does not work... I subsequently tried a few other custom roms (I think they were all based on cm10.1 which may be the problem). Wifi will turn on and recognize my network but when I try to connect it simply says "connecting" and then a few second later goes back to "saved, secured with WPA2". I'm relatively sure it is not my router since my laptop and phone are constantly connected and my tablet could connect on TouchWiz.
I've looked all around XDA and other forums to see if anyone has this issue and I could only find one topic but it had no resolution. I figure this must no be too common since Wifi, at least for the n8013, is the only way of connecting to the internet.
Any one have a similar problem or know how to fix it? Should I try flashing a rom that isn't based on CM10.1? I could just go back to stock TouchWiz but I'd rather not...
Click to expand...
Click to collapse
U have mistake when flash rom not for 8013. Now U only 1 way is flash stock rom and factory reset after the first boot.
If U wanna CM rom, u have to reconized what rom affordable for 8013 first.
Sent from my GT-N8013 using Tapatalk 2
having same issue
Tried a few roms and wifi doesn't work. Any suggestions?
*ZeuS* said:
Tried a few roms and wifi doesn't work. Any suggestions?
Click to expand...
Click to collapse
What rom which you had tried? I think you back to stock rom to fix wifi driver first
Sent from my C6802 using Tapatalk
Cm10.2, paranoid android
Sent from my GT-N8013 using XDA Premium HD app
WiFi is a function of the kernel .