Related
I just tried applying the patch to address Android issue 8804 (no link because I'm a new user and don't have permission to include it, but it's in the Google code issue tracker for Android) to the stock froyo-release branch from git and recompiled wpa_supplicant using the following command line:
mm WPA_SUPPLICANT_VERSION=VER_0_6_X WPA_BUILD_SUPPLICANT=true
However, after building this and copying over the resulting wpa_supplicant binary, I found that wifi on my Droid 2 no longer worked. It appears the issue is that only wext driver support was compiled in:
$ ./wpa_supplicant
wpa_supplicant v0.6.10
...snipped...
drivers:
wext = Linux wireless extensions (generic)
options:
...snipped...
The stock version shows wext and tiwlan0 drivers:
$ ./wpa_supplicant.stock_droid2
wpa_supplicant v0.6.10
...snipped...
drivers:
wext = Linux wireless extensions (generic)
tiwlan0 = TI Station Driver (1271)
options:
...snipped...
I don't see the tiwlan0 driver in the source tree or as a configuration option. I'm suspecting that TI has not made it available or else someone else would likely have created a patched wpa_supplicant already.
Is it possible to build a patched version of wpa_supplicant that includes the tiwlan0 driver?
Any news it this subject - of tiwilan0 driver to wpa_supplicant? (same situation is on Archos gen8 devices...)
$aur0n said:
Any news it this subject - of tiwilan0 driver to wpa_supplicant? (same situation is on Archos gen8 devices...)
Click to expand...
Click to collapse
+1
i need the same patch for Archos 70
we have wpa_suppliant sources, we can obtain Archos sources too
someone can get this built pls?
10x 2 Steve , we have such version, but unfortunately it doesn't work on my Archos
http://code.google.com/p/android/issues/detail?id=8804
You can try it :
download
Here's a few more modules for the stock kernel if anyone's interested.
CIFS (+slow-work.ko) should work with CIFS Manager (in the market), but I have yet to test it (can't here at work).
And I know Sogarth was looking to try out a FUSE solution for the webtop, so I went ahead and added that module.
Haha. Neat.
btw, has anybody verified if the kernel on the 4.1.57 update is different/incompatible? It claims to be kernel 2.6.32.9-00005-gde8e6dc.
Sogarth said:
Haha. Neat.
btw, has anybody verified if the kernel on the 4.1.57 update is different/incompatible? It claims to be kernel 2.6.32.9-00005-gde8e6dc.
Click to expand...
Click to collapse
You mean did they change CONFIG_MODVERSIONS to 'n' ? Otherwise, our source tree should be close enough for most purposes right?
PS. Nice work agentdr8.
EDIT: Here are the differences in the orig/OTA kernel. Mostly VPN related?
Code:
diff config.orig config
4c4
< # Sat Feb 5 02:50:36 2011
---
> # Tue Mar 1 09:16:01 2011
435c435
< # CONFIG_XFRM_MIGRATE is not set
---
> CONFIG_XFRM_MIGRATE=y
437c437,439
< # CONFIG_NET_KEY is not set
---
> CONFIG_XFRM_IPCOMP=y
> CONFIG_NET_KEY=y
> CONFIG_NET_KEY_MIGRATE=y
452,453c454,455
< # CONFIG_INET_AH is not set
< # CONFIG_INET_ESP is not set
---
> CONFIG_INET_AH=y
> CONFIG_INET_ESP=y
457,459c459,461
< # CONFIG_INET_XFRM_MODE_TRANSPORT is not set
< # CONFIG_INET_XFRM_MODE_TUNNEL is not set
< # CONFIG_INET_XFRM_MODE_BEET is not set
---
> CONFIG_INET_XFRM_MODE_TRANSPORT=y
> CONFIG_INET_XFRM_MODE_TUNNEL=y
> CONFIG_INET_XFRM_MODE_BEET=y
461c463,464
< # CONFIG_INET_DIAG is not set
---
> CONFIG_INET_DIAG=y
> CONFIG_INET_TCP_DIAG=y
467,475c470,479
< # CONFIG_IPV6_PRIVACY is not set
< # CONFIG_IPV6_ROUTER_PREF is not set
< # CONFIG_IPV6_OPTIMISTIC_DAD is not set
< # CONFIG_INET6_AH is not set
< # CONFIG_INET6_ESP is not set
< # CONFIG_INET6_IPCOMP is not set
< # CONFIG_IPV6_MIP6 is not set
< # CONFIG_INET6_XFRM_TUNNEL is not set
< # CONFIG_INET6_TUNNEL is not set
---
> CONFIG_IPV6_PRIVACY=y
> CONFIG_IPV6_ROUTER_PREF=y
> # CONFIG_IPV6_ROUTE_INFO is not set
> CONFIG_IPV6_OPTIMISTIC_DAD=y
> CONFIG_INET6_AH=y
> CONFIG_INET6_ESP=y
> CONFIG_INET6_IPCOMP=y
> CONFIG_IPV6_MIP6=y
> CONFIG_INET6_XFRM_TUNNEL=y
> CONFIG_INET6_TUNNEL=y
2136c2140
< # CONFIG_CRYPTO_NULL is not set
---
> CONFIG_CRYPTO_NULL=y
2163c2167
< # CONFIG_CRYPTO_HMAC is not set
---
> CONFIG_CRYPTO_HMAC=y
2173c2177
< # CONFIG_CRYPTO_MD5 is not set
---
> CONFIG_CRYPTO_MD5=y
2195c2199
< # CONFIG_CRYPTO_DES is not set
---
> CONFIG_CRYPTO_DES=y
2208c2212
< # CONFIG_CRYPTO_DEFLATE is not set
---
> CONFIG_CRYPTO_DEFLATE=y
2231a2236
> CONFIG_ZLIB_DEFLATE=y
Cool..I just did the OTA update to 4.1.57, any possibility to get this module for that version of the kernel. Although the version appears to match, the 4.1.57 kernel string
is
2.6.32.9-00005-gde8e6dc
EDIT: Damn should have read the previous thread, sorry. So has anyone verified, otherwise I might give it a shot here.
bekarhoo said:
2.6.32.9-00005-gde8e6dc
EDIT: Damn should have read the previous thread, sorry. So has anyone verified, otherwise I might give it a shot here.
Click to expand...
Click to collapse
Even though the major & minor kernel versions haven't changed, the addition of the localversion might throw off the vermagic in the original modules I posted.
I recompiled them with the localversion set to 00005-gde8e6dc so see if these work with the OTA update (I haven't applied the update and probably won't until true root is found, so I can't test these). I checked the vermagic with modinfo -F vermagic and they check out as 2.6.32.9-00005-gde8e6dc SMP preempt mod_unload modversions ARMv7
EDIT: Removed attachment -- not working on new kernel
agentdr8 said:
Even though the major & minor kernel versions haven't changed, the addition of the localversion might throw off the vermagic in the original modules I posted.
Click to expand...
Click to collapse
They seemed to insmod fine for me on .57 (the originals)
agentdr8 said:
(I haven't applied the update and probably won't until true root is found, so I can't test these).
Click to expand...
Click to collapse
Hmm I'm pretty OK copying su around. I kinda hope we save whatever gems are left for gingerbread. I sense more OTAs coming, there are so many bugs left... we could give up all our aces with a cat and mouse game
agentdr8 said:
Even though the major & minor kernel versions haven't changed, the addition of the localversion might throw off the vermagic in the original modules I posted.
I recompiled them with the localversion set to 00005-gde8e6dc so see if these work with the OTA update (I haven't applied the update and probably won't until true root is found, so I can't test these). I checked the vermagic with modinfo -F vermagic and they check out as 2.6.32.9-00005-gde8e6dc SMP preempt mod_unload modversions ARMv7
Click to expand...
Click to collapse
I'm getting:
insmod: error inserting 'cifs.ko': -1 Unknown symbol in module
I have rooted .57
Edit: May be it is because the way I installed cifs.ko.
I just remounted /system and copy cifs.ko in /system/lib/modules/
Did I forgot something?
Try using the original ones for the stock kernel. I think someone said they work fine with the new OTA kernel.
I already did that and no luck. I'm doing something wrong ...
Edit: I'm an idiot. slow-work.ko has to go first, then everything works. Thanks!
Any chance someone would be willing to walk a noob getting this on the atrix? I've updated to the latest 1.83. I'm real interested in getting cifs up and running. To be honest, I'm floored it's not included by default. Any risks/issues with doing this? I got no problem hacking away at this so long as there's some clear step-by-step directions so I'm confident I won't botch it up
Thanks!
Looking for a working utf8.ko
Help
Sent from my MB860 using XDA App
Can someone please post the new versions that would work for the latest GingerBread build from OTA update? Thanks!
these modules are included in faux custom kernel, not sure about others
Enviado desde mi MB860 usando Tapatalk
My kernel is 2.6.32.9 from new version 2.3.6. Does anybody could help me to compile an cifs module to work on this new stock rom (my bootload is locked yet).
2.3.6 kernel mods
I'm interested in getting isofs.ko and udf.ko and ext4.ko kernel mods working, I've tried compiling from source that's posted on source forge, but it's not working.
here's a thread I was working out of: http://forum.xda-developers.com/showthread.php?p=26892952#post26892952
Please help!
Cifs.ko module for galaxy tab 7.7 for stock galaxy kernel.
EDIT - pinkowl has updated the cifs module with nls_utf8 support.
Please see use his updated download link from post 12.
cheers
Should allow mounting of windows/samba shares.
from terminal (connectbot, script etc)
$ insmod cifs.ko (where you saved cifs.ko path)
Please could you test. For me it is working. however a few issues:
but video players stutter but so far bs player lite works best me for media network streaming.
edit - is it down to poor wifi performance - however same files play fine over http streaming from nas!
so proper dev required to looked into performance issues.
Using cifs manager to mount share & es explorer free edition allows you to copy to root etc.
Looks good to me ~8mins for 501M (what are you aiming for?):
P6810(wifi), RTN-16 router,Fedora16 samba share
bash-4.2# insmod cifs.ko
bash-4.2# mount -t cifs -o user=XXX,passwd=XXXXXX //192.168.2.113/XXX /data/local/tmp/mnt
bash-4.2# pwd
/data/local/tmp
bash-4.2# cd mnt
bash-4.2# ls
Desktop
Documents
Downloads
Music
Pictures
Public
Templates
Videos
eclipse
workspace
bash-4.2# time cp /data/local/tmp/junk_1 junk_1_back
real 8m20.644s
user 0m0.275s
sys 0m35.175s
bash-4.2# time cp junk_1_back /data/local/tmp/junk_2
real 7m46.706s
user 0m0.240s
sys 0m24.630s
bash-4.2#bash-4.2# md5sum ../junk_2
b6cee9135f8f4fd8ed03bfcc641de7b1 ../junk_2
bash-4.2# md5sum ../junk_1
b6cee9135f8f4fd8ed03bfcc641de7b1 ../junk_1
bash-4.2#
bash-4.2# ls -l ../junk*
-rw-rw-r-- root root 524288000 2012-01-22 03:42 junk_1
-rw-r--r-- root root 524288000 2012-01-22 04:35 junk_2
Awesome - worked perfectly with the root pack from this forum as well.
Now.... do you have tun.ko for this tab as well please?
Ive found a couple of versions - but they have not been compiled for this rom from the looks and do not load correctly.
Is the tun.ko file available at all yet?
Did another run with some optimisations:
Locked router to N mode instead of mixed
Discovered busybox cp poor performer, used /system/bin/cat instead
Tried kernel setting on
echo 1 > /proc/sys/net/ipv4/tcp_low_latency
Which definitely helps my ssh session, but not sure much impact on this test.
#same 501M file as previous post
#copy server to 7.7
time cat junk_1_back > ../junk_1_47
real 6m52.908s
user 0m0.240s
sys 0m24.390s
#copy from 7.7 to server
bash-4.2# time cat ../junk_1 > junk_1_xxx5
real 3m35.079s
user 0m0.040s
sys 0m19.890s
#copy server to /dev/null on 7.7
bash-4.2# time cat junk_1_xxx3 > /dev/null
real 6m45.223s
user 0m0.115s
sys 0m15.695s
All files intact, I think your module is good, I think kernel tcp params or wireless may need tweaks as suspected in wireless problem thread.
---------- Post added at 11:29 AM ---------- Previous post was at 11:17 AM ----------
cbdrift said:
Awesome - worked perfectly with the root pack from this forum as well.
Now.... do you have tun.ko for this tab as well please?
Ive found a couple of versions - but they have not been compiled for this rom from the looks and do not load correctly.
Is the tun.ko file available at all yet?
Click to expand...
Click to collapse
? Its built-in to kernel:
bash-4.2# uname -a
Linux localhost 2.6.36-P6810DTKL5-CL604290 #3 SMP PREEMPT Wed Dec 14 18:05:58 KST 2011 armv7l GNU/Linux
bash-4.2# ls -l /dev/tun
crw-rw---- vpn vpn 10, 200 2012-01-24 08:23 tun
ezynow:
thanks for sharing the cifs.ko module.
willl you be kind enough to teach me how to get my Windows 7 home premium hooked with cifs?
i tried and search the www and the closest solution i had is to view my shared folder using Ghostcommander with SMB plugin.
however, i cannot mount the share drive as a folder using either
cifsmanager or mount manager
i have tried to do regedit in my Win7 home premium since there is not "local security policy" program for this version of Win7.
Sorry for disturb
Plz, can anybody tell me what is this and how to use it?
i got an error when i add the iocharset=utf8 in the option at cifs manager, how can i make it use utf8?
I place this file in root directory of my sd card.
use terminal emulator program and type
insmod /mnt/sdcard/cifs.ko
but I got
insmod: init_module '/mnt/sdcard/cifs.ko' failed (Operation not permitted)
what should i do
Sent from my GT-P6800 using xda premium
theerachai said:
I place this file in root directory of my sd card.
use terminal emulator program and type
insmod /mnt/sdcard/cifs.ko
but I got
insmod: init_module '/mnt/sdcard/cifs.ko' failed (Operation not permitted)
what should i do
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
try from root
su
then insmod /pathtocifs.ko/
solved, thank you very much
Sent from my GT-P6800 using xda premium
The issues with video playback is not really with cifs, but with caching done by the players.
Typically, a player streaming over http expects a long delay and will use a larger buffer. Playing over cifs, the player will think it's locally stored and no buffer is necessary. That lack of buffer is causing the problems.
I have compiled the nls_utf8.ko module as well as recompilied the module cifs.ko for those of you that needs it. Files are attached in this post.
This is for the stock kernel from the LA2 firmware which I am using. If you are using the stock kernel from Samsung, this should work for you.
If this helps you, pls click on the "thanks" link.
Thanks for this module. I've known about cifs but never tried it before. Now I thought I'd give it a go and it's great. Had a few initial noob problems but now all OK. And using Cifs Manager makes mounting my NAS a breeze.
I can watch all my 720p video files stored on my NAS. Using BS player as suggested by ezynow.. Thanks ezynow!
Thank
Tested ,work well .
pinkowl said:
If this helps you, pls click on the "thanks" link.
Click to expand...
Click to collapse
I'm new here.
can you tell me where the "thanks" link is? pls
because your file helps me a lot~
pinkowl said:
I have compiled the nls_utf8.ko module as well as recompilied the module cifs.ko for those of you that needs it. Files are attached in this post.
This is for the stock kernel from the LA2 firmware which I am using. If you are using the stock kernel from Samsung, this should work for you.
If this helps you, pls click on the "thanks" link.
Click to expand...
Click to collapse
Nice one - i will update the main thread & creditation to you for this
Thanks a lot for these modules. I use them to access shares on my home network.
I found only one small problem accessing shares on my Windows 7 x64 host. If I use iocharset=utf8 as a parameter I can see the segmentation fault message when trying to mount a share from this host. Without iocharset parameter it works ok (apparently all unicode filenames are not shown correctly)
Exactly the same setup works fine with shares from my router and unicode filenames are displayed correctly.
@original poster
Can you rebuild this for ICS, please?
m0bster said:
@original poster
Can you rebuild this for ICS, please?
Click to expand...
Click to collapse
You can't rebuild this until Samsung release the ICS source code used to compile the kernel. Hopefully they do so soon but I am not holding my breath.
New kernel released. Can anyone compile cifs.ko and nls_utf8.ko?
I have 2 Touchpads with CM9 Alpha 2. They both have the same bluetooth address.
It looks like this was a problem in CM7 Alpha 3.5 as well (see Rootzwiki CM7 Alpha 3.5 post #1411, sorry not allowed to post external links yet). I tried the "bdaddr" command but it was "not found".
Open Terminal Emulator then type the following list below
su
bdaddr [new bluetooth address] && hciconfig hci0 reset
Click to expand...
Click to collapse
Does anyone know how to change the bluetooth address or have a workaround for two devices having the same bluetooth address? Thanks.
Hi guys,
i need some help with wifi tethering/Portable Hotspot
right now i using CM7.2 GINGERBREAD V10 (ALFS kernel V7 ICS) with ALFS V7 ICS kernel.
As i read in the CM7.2 thread, i install Wifi Tether attach in post #2,
i start the wifi tether, and it say, "start with error, please check the log" or something like that
Please check the attachment for the log.
What did i do to solve this problem :
Start Fresh, Wipe data, cache, dalvic cache, format system
install stock ROM + Kernel (E15i_2.1.1.A.0.6_RU.ftf) using flash tool,
and Install NAA kernel 11 + MiniCM7-2.1.9 (As i read NAA + miniCM rom support Native GB hotspot) - The result is : when i start Portable Hotspot it start ok, connecting ok, but cannot browse the web, in the laptop it says "DNS ERROR"
So i flash again ALFS V7 ICS kernel over NAA and flash CM7.2 GINGERBREAD V10,
trying again with wifi tether and no luck
My Question :
1. What happen with my phone? is this something i do wrong when flashing?
2. Is it possible the carrier/operator blocking Tethering?
3. Is there someway to solve this problem?
Please note :
1. Before i was successful starting Portable Hotspot with NAA kernel, but because a2sd error i think i try to start fresh with NAA kernel + MiniCM rom, n thats when this problem occurs
2. I can connect to wifi or Adhoc wifi with no problem
Thanks Guys n sorry for the bad english
Looking at the two screenshots where you got errors reported it would seem as the wireless tether thingy doesn't find the required kernel modules, although they should be part of both kernels you mentioned - though I'm not sure if the "CM7.2 GINGERBREAD V10" ROM is compatible with Alfs.
I would ask in either Alfs' or nAa's thread about what may be wrong here; from my viewpoint it's missing modules that should be part of the kernel already.
B.Jay said:
Looking at the two screenshots where you got errors reported it would seem as the wireless tether thingy doesn't find the required kernel modules, although they should be part of both kernels you mentioned - though I'm not sure if the "CM7.2 GINGERBREAD V10" ROM is compatible with Alfs.
I would ask in either Alfs' or nAa's thread about what may be wrong here; from my viewpoint it's missing modules that should be part of the kernel already.
Click to expand...
Click to collapse
hi... thanks for ur reply
can we check it? i mean for the module?
maybe we can look on a folder n check that the module is there or not?
for the CM7.2 GB V10 ROM, i think it only using ALFS Kernel (ALF V7 ICS), so it should be compatible.
i really like to post on the NAA and ALFS thread but as u can see, iam lack of post
lanjor said:
hi... thanks for ur reply
can we check it? i mean for the module?
maybe we can look on a folder n check that the module is there or not?
for the CM7.2 GB V10 ROM, i think it only using ALFS Kernel (ALF V7 ICS), so it should be compatible.
i really like to post on the NAA and ALFS thread but as u can see, iam lack of post
Click to expand...
Click to collapse
Errr.... no, you won't find the modules as files - they should be compiled into the kernel (hence "part of it")
What you can try is to look into this thread, though that modules shouldn't be needed on Alfs or nAa, just on stock kernel.
However, if it works afterwards it might be worth trying.
B.Jay said:
Errr.... no, you won't find the modules as files - they should be compiled into the kernel (hence "part of it")
What you can try is to look into this thread, though that modules shouldn't be needed on Alfs or nAa, just on stock kernel.
However, if it works afterwards it might be worth trying.
Click to expand...
Click to collapse
i check n read the link above, n i think i just jump to
"You can use iptables executable now and check if works:" Part :
because like u say, this module should be part of the kernel, n if i flash the kernel right, the module should be there, dont u think.
so i try run the command via terminal :
- iptables -L
the result are :
Code:
$ export PATH=/data/local/bin:$PATH:.
$su
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
#
- iptables -t nat -L
the result are :
Code:
$ export PATH=/data/local/bin:$PATH:.
$ su
# iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
#
- cat /proc/net/nf_conntrack
The result are :
Code:
$ export PATH=/data/local/bin:$PATH:.
$su
# cat /proc/net/nf_conntrack
ipv4 2 tcp 6 431959 ESTABLISHED src=10.89.156.230 dst=216.155.195.253 sport=42914 dport=80 src=216.155.195.253 dst=10.89.156.230 sport=80 dport=42914 [ASSURED] use=1
ipv4 2 tcp 6 431972 ESTABLISHED src=10.89.156.230 dst=173.192.219.136 sport=44146 dport=443 src=173.192.219.136 dst=10.89.156.230 sport=443 dport=44146 [ASSURED] use=1
ipv4 2 tcp 6 431876 ESTABLISHED src=10.89.156.230 dst=61.145.124.115 sport=41129 dport=5222 src=61.145.124.115 dst=10.89.156.230 sport=5222 dport=41129 [ASSURED] use=1
ipv4 2 tcp 6 426586 ESTABLISHED src=192.168.0.5 dst=216.155.195.253 sport=52694 dport=80 src=216.155.195.253 dst=192.168.0.5 sport=80 dport=52694 [ASSURED] use=1
ipv4 2 tcp 6 426570 ESTABLISHED src=192.168.0.5 dst=61.145.121.120 sport=56854 dport=5222 src=61.145.121.120 dst=192.168.0.5 sport=5222 dport=56854 [ASSURED] use=1
ipv4 2 tcp 6 431982 ESTABLISHED src=10.89.156.230 dst=216.155.195.253 sport=56242 dport=80 src=216.155.195.253 dst=10.89.156.230 sport=80 dport=56242 [ASSURED] use=1
ipv4 2 tcp 6 426550 ESTABLISHED src=192.168.0.5 dst=173.194.72.188 sport=58555 dport=5228 src=173.194.72.188 dst=192.168.0.5 sport=5228 dport=58555 [ASSURED] use=1
ipv4 2 tcp 6 220 ESTABLISHED src=10.89.156.230 dst=209.85.175.188 sport=56186 dport=5228 src=209.85.175.188 dst=10.89.156.230 sport=5228 dport=56186 [ASSURED] use=1
#
Only this one is different from the result expected
-----------------------------------------------------------------
so what do you think ? the module is there? n why is the last command result is different?
Well, the last output you got HAS to be different because "nf_conntrack" reads, fully spelled: Net Filter Connection Tracker
This means the nf_conntrack in /proc/net shows entries of connections currently established on your phone (outgoing and incoming).
It actually looks like as if the modules are in the kernel (as they should) - otherwise you would have gotten a error message from iptables.
Now don't ask me why the "tethering-update" ZIP from Alfs won't work or why nAa's tethering doesn't like you...
B.Jay said:
Well, the last output you got HAS to be different because "nf_conntrack" reads, fully spelled: Net Filter Connection Tracker
This means the nf_conntrack in /proc/net shows entries of connections currently established on your phone (outgoing and incoming).
It actually looks like as if the modules are in the kernel (as they should) - otherwise you would have gotten a error message from iptables.
Now don't ask me why the "tethering-update" ZIP from Alfs won't work or why nAa's tethering doesn't like you...
Click to expand...
Click to collapse
oh.. okey
at least i know the module is there
just last question B.Jay, if it's ok with u,
1. is there a possibility something wrong with superuser?
thanks for ur help B.Jay
Don't think so, you were able to run "su" commands in the terminal.
Just check with some app that requires superuser rights ... like Titanium Backup or Root Explorer ... when they get su granted then Superuser should work.
B.Jay said:
Don't think so, you were able to run "su" commands in the terminal.
Just check with some app that requires superuser rights ... like Titanium Backup or Root Explorer ... when they get su granted then Superuser should work.
Click to expand...
Click to collapse
Ok thanks B.Jay
---------------------------------------------------------------------------
Still trying to figure out the problem
Well check the ROM info maybe the tethering is not working.... or its just a kernel bug....
HIT THANKS IF I HELPED!
ZeWhiteRabbit said:
Well check the ROM info maybe the tethering is not working.... or its just a kernel bug....
HIT THANKS IF I HELPED!
Click to expand...
Click to collapse
if u read the first post, i already write it, before it was working good
----------------------------------------------------------------------------
Anyway i figure it out, it is my carrier/operator
i tried to change sim card from different operator n
the tethering works really good
i dont know what they do, but i cannot change proxy, i cannot change DNS, and i cannot use wifi tethering/portable hotspot
but at least the problem solved thanks to B.Jay for helping me
On mini+nAa wifi tether works really good
Sent from my E15i using XDA App