[Q] Need Help With Wifi Tethering/Portable Hotspot [SOLVED] - XPERIA X8 Q&A, Help & Troubleshooting

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

Related

Speedmod Kernel K13C - Kernel debug logging

First of all sorry for opening a new thread about this topic, but i am not allowed to answer in the developer thread as i am a newbie.
This is about the disabled kernel debug logging facility in the latest speedmod kernel (K13C).
I'm a user of Droidwall (iptables front-end) and extended it by a couple of scripts for more filtering, but i miss the log target extension support from the latest speedmod kernel.
About iptables Target Extensions:
"""
Target extensions allow some specialized actions and packet treatment to be done, such as NAT or load balancing. Please refer to iptables manual to know more about available target extensions. Here are some important ones:
* LOG
This one allow to log (via kernel logging, you can see using the command dmesg) any message you wish when a certain packet matches. A good rule is to include a logging rule right before any rejected traffic. This way, finding out problems with your firewall is easy, as you can see what and when it is dropping something. This target accepts an option –log-prefix, that allow to prefix a text to each log message.
"""
Does anybody else noticed this (at least to me) important feature missing from the kernel? BTW, this is not ANDROIDLOGGING!
Any chance to get logging back - i doubt it uses a lot of power to have it in!
EDIT: except for this missing feature the kernel is super fantastic
Cheers
Your newbie - not noob i hope
Alex
---
Samsung Galaxy S i9000GT
with speedmod-k13c-500hz Kernel
Same here... *bummer*...
FUGU Kernel enabled iptables log feature ?
anyone knows ?
Fugu is interesting anyway (especially because of btrfs )
Android logger in tweaks config?
ttf said:
Android logger in tweaks config?
Click to expand...
Click to collapse
Nope. AndroidLogger in Tweaks is for the Syslog
iptables LOG is a kernel module (compiled or not).
Andro1d said:
Nope. AndroidLogger in Tweaks is for the Syslog
iptables LOG is a kernel module (compiled or not).
Click to expand...
Click to collapse
You right, but was not sure.
AlexAlien1966 said:
This is about the disabled kernel debug logging facility in the latest speedmod kernel (K13C).
I'm a user of Droidwall (iptables front-end) and extended it by a couple of scripts for more filtering, but i miss the log target extension support from the latest speedmod kernel.
Click to expand...
Click to collapse
Dear Alex,
I fully support your suggestion on bringing back kernel logging to the speedmod kernel. I miss the feature especially in tweaking my Droidwall firewall, where I do not have any logging of the firewall traffic anymore because it depends on an active kernel logging.
Perhaps hardcore may rethink his decision on this topic?
Regards,
x600
----------------------
Samsung Galaxy S i9000GT, speedmod-k13c-500hz, Droidwall 1.5, Stock JQ3 ROM.
Same here... logging is not working...
I would be nice if kernel logging would be an option in tweak menu...

[Q] DEVELOPERS, Need help to get VPN work (tun.ko)

Hi! I just created a tun.ko file for the current DK-Rom (Kernel 2.6.32.21-ge5a759b)
Here is an update-flash package with openvpn connection gui and tun.ko included.
http://www.megaupload.com/?d=CN3D0PRP
if i try to "insmod /system/lib/modules/tun.ko " i got an error: device / resource busy...
lsmod shows no tun.ko loaded...
Also tried before :
mkdir /dev/net
mknod /dev/net/tun c 10 200
Anyone an idea ?
Maybe i found the problem. Need some free time to get the fix to work.
BUT , (Cisco) VPN-Pack is on the WAY for Wildfire Froyo
try cm7, tun.ko is included on the rom.. also the openvpn app.. i got it working
Thanks for the Information. I would like to get it work with my rom.
ijestan said:
try cm7, tun.ko is included on the rom.. also the openvpn app.. i got it working
Click to expand...
Click to collapse
Sent from my HTC Wildfire
Now finally working vpn pack arrived !
Look into main thread.
This thread can be closed now...
Thread closed by OP request.

[KernelModule] Overclock

**** Do Not Repost! Link back to this thread! ****
*** Update: This works on Thrill/Optimus 3D. There are seperate kernel modules for Froyo/GingerBread/CyanogenMod kernels***
Here ya go... I prefer this method rather than hard coding changes in the kernel. Assuming you have both kernel modules extracted to /sdcard
Switch to root
Code:
$ su
Copy files from sdcard to /system/lib/modules directory - You only do this once
Code:
# cp /sdcard/symsearch.ko /system/lib/modules/symsearch.ko
# cp /sdcard/opperator.ko /system/lib/modules/opperator.ko
Load modules, always do symsearch.ko first - You do this every time you reboot
Code:
# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/opperator.ko
Set Frequency - You do this when you want to change frequency - in hz, that's 6 additions Zero's to make Mhz
Code:
# echo 1188000000 > /proc/opperator
This uses SYMSEARCH by Skrilax_CZ
https://github.com/SkrilaxCZ
Inspired by Milestone Overclock by Tiago Sousa, but totally rewritten for omap kernel 2.6.35-7 and above.
http://code.google.com/p/milestone-overclock/
This is a stripped down version. I'm working on a fully featured version, that will allow you to play with voltage as well. There are some hurdles to overcome before that is ready for prime time... In the mean time, lets see what stock voltage can do... 1188 is my sweet spot on stock voltage, what is yours? I get up to 1235 without reboots, or real noticeable lags but the linkpacks are all over the place, where it stays in the 80's at 1188. And remember, the number is in hz a.k.a. cycles per second, so to get Mhz, you must add 'Six Zeroes' to the end of your desired Mhz.
* Note2Devs: Feel free to put this in your ROM, but please do credit me for the Overclock in your release, and link back to this thread. You can also post a link to your ROM here as a way to make myself and other aware of it. Thanks...
* Echts shows us how he integrate's the module into his own ROM. TY, Echts...
http://forum.xda-developers.com/showpost.php?p=19542521&postcount=52
* Thanks to greenbats for helping figure out the O3D gingerbread kernel issue!
** And don't ask to put it in an app. I won't be happy about that. I'm serious! **
Here go some of my Recording Engineer work...
http://www.youtube.com/watch?v=Je8K_hCej3s
http://www.youtube.com/watch?v=yfBfcdSL1pc
http://www.youtube.com/watch?v=iIU8DO4rdKI
http://www.youtube.com/watch?v=msavF7LIdvY
Essentially, hardware wise, the Thrill has exactly the same specs as the Optimus 3D ? I mean, CPU wise.
It's the same hardware
omgomg said:
Essentially, hardware wise, the Thrill has exactly the same specs as the Optimus 3D ? I mean, CPU wise.
Click to expand...
Click to collapse
Yes, give this a go on the O3D, the module is actually compiled against the cyanogenmod cosmo kernel, which is really for the O3D. Should work.
for test \
How do I install this on the optimus 3D?
greenbat said:
How do I install this on the optimus 3D?
Click to expand...
Click to collapse
No real installing... It's just the modules... You can throw them in /system/lib/modules, and then use an init script to load them up, then set the frequency, but don't do that until you know what works *STABLE* for you.
If you have a favorite ROM, let the dev know about this, and maybe they'll integrate it.
I'm not sure if custom kernels like acurateam's might be too different to work properly at this point. But it won't hurt to try. Just don't start loading it at boot right away.
tekahuna said:
No real installing... It's just the modules... You can throw them in /system/lib/modules, and then use an init script to load them up, then set the frequency, but don't do that until you know what works *STABLE* for you.
If you have a favorite ROM, let the dev know about this, and maybe they'll integrate it.
I'm not sure if custom kernels like acurateam's might be too different to work properly at this point. But it won't hurt to try. Just don't start loading it at boot right away.
Click to expand...
Click to collapse
Thanx for your advice and Great find!!!
I have send your xda link to acura. Hopefully he can integrate it.
greenbat said:
Thanx for your advice and Great find!!!
I have send your xda link to acura. Hopefully he can integrate it.
Click to expand...
Click to collapse
I didn't find this. I made it! First OC'd OMAP4 period! Unless you count RAZR's... hah
Great invention
tekahuna said:
I didn't find this. I made it! First OC'd OMAP4 period! Unless you count RAZR's... hah
Click to expand...
Click to collapse
Great invention and congratulations!
Great job.... we use to use this type of script in motorola defy and moto bravo. It was easier with those because of the 2nd init recovery booting.
Sent from my LG-P925 using XDA App
tekahuna said:
**** Do Not Repost! Link back to this thread! ****
Here ya go... I prefer this method rather than hard coding changes in the kernel. Assuming you have both kernel modules extracted to /sdcard
Switch to root
Code:
$ su
Copy files from sdcard to /system/lib/modules directory - You only do this once
Code:
# cp /sdcard/symsearch.ko /system/lib/modules/symsearch.ko
# cp /sdcard/opperator.ko /system/lib/modules/opperator.ko
Load modules, always do symsearch.ko first - You do this every time you reboot
Code:
# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/opperator.ko
Set Frequency - You do this when you want to change frequency - in hz, that's 6 additions Zero's to make Mhz
Code:
# echo 1188000000 > /proc/opperator
Is it possible for you to change this into a scriptmanager file?
Click to expand...
Click to collapse
Type this in scriptmanager shell.
greenbat said:
tekahuna said:
**** Do Not Repost! Link back to this thread! ****
Here ya go... I prefer this method rather than hard coding changes in the kernel. Assuming you have both kernel modules extracted to /sdcard
Switch to root
Code:
$ su
Copy files from sdcard to /system/lib/modules directory - You only do this once
Code:
# cp /sdcard/symsearch.ko /system/lib/modules/symsearch.ko
# cp /sdcard/opperator.ko /system/lib/modules/opperator.ko
Load modules, always do symsearch.ko first - You do this every time you reboot
Code:
# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/opperator.ko
Set Frequency - You do this when you want to change frequency - in hz, that's 6 additions Zero's to make Mhz
Code:
# echo 1188000000 > /proc/opperator
Is it possible for you to change this into a scriptmanager file?
Click to expand...
Click to collapse
What I'd really like is for the ROM making dev's to come to a consensus as to how to integrate this... Mainly, the best place to throw the script that does this at boot on these phones. I know how we did it on droid X, but I haven't dug deep enough into this phone just yet to be sure... I'll update the OP as methods improve and I get more feedback.
Click to expand...
Click to collapse
Or use callmearia kernel and make script for system/etc/init folder... havent tried his kernel but it should support the script at boot up. Acura roms should work that way too.
The way most roms use overclock is the init script that starts at boot...
Sent from my LG-P925 using XDA App
rdannar said:
Great job.... we use to use this type of script in motorola defy and moto bravo. It was easier with those because of the 2nd init recovery booting.
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
Those would have been based on Milestone Overclock... Which is where I gained most of my knowledge by contributing to getting the droidx/2 side of things working. MO's method of manipulating frequency and voltage no longer works on OMAP4, or rather kernel 2.6.35+... I had to come up with a new way of doing things, which didn't fit well under the existing framework of MO. So, I started from scratch... This is just the tip of the iceberg... Basic, basic, basic...
i get insmod: init_module /system/lib/modules/symsearch.ko failed (exec format error).
What am i doing wrong?
I also get the same error: insmod: init_module '/system/lib/modules/symsearch.ko' failed (exec format error)
Is it because I have gingerbread?
Must I use froyo?
borelis said:
i get insmod: init_module /system/lib/modules/symsearch.ko failed (exec format error).
What am i doing wrong?
Click to expand...
Click to collapse
Both O3D's, huh? What kernel are you running? give me output of
# dmesg
and
# busybox uname -a
And if it's acurateam, a link to their kernel source
tekahuna said:
What kernel are you running? give me output of
# dmesg
and
# busybox uname -a
And if it's acurateam, a link to their kernel source
Click to expand...
Click to collapse
"LINK Boot_2.0 More RAM, No Lags, More Speed.." from acura. Think he uses stock kernel. Im on GB by the way.
Outputs is a bit over my head. Tell me how and i´ll provide it for you.

[GT-P6800][3g]cifs.ko - module

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?

[KERNEL] Building additional modules for JB stock kernels

Some background info:
I'm the author of PPP Widget which is an app that enables mobile data connections on Android devices with USB host capabilities - even if they are WiFi-only.
It turned out that many Android devices have the drivers for 3G sticks already on board, included with the stock kernel. The one large exception are Samsung devices ...
I started to provide the missing drivers as modules (mostly "ppp_async" and "option" which depends on "usb_wwan"). That worked well for some Google devices and also for Samsung devices running ICS, using the source packages from
http://opensource.samsung.com/
In their JB kernels though, Samsung enabled the "MODVERSION" option. Furthermore, compiling the modules with the officially recommended toolchain resulted in a different "module_layout" checksum than in the modules provided in the firmware.
This prevents using any additonal modules on the devices. "insmod" refuses to load these modules.
The only explanation for this problem is that the custom device configuration provided in the source packages does not match the configuration of the device kernel.
This is the case for all GT-P31xx and GT-P51xx models as far as I can tell.
My take is that Samsung is required to provide the correct kernel configuration under the rules of the GPL. Maybe anyone else wants to contact Samsung on this behalf; I already did several times - still waiting for an answer ...
That's the reason why I build everyting from source including the GPU driver and lost exFAT support http://forum.xda-developers.com/showthread.php?t=1859227 and the boot image result http://forum.xda-developers.com/showthread.php?t=1855700 .
ketut.kumajaya said:
That's the reason why I build everyting from source including the GPU driver and lost exFAT support
Click to expand...
Click to collapse
Unfortunately, replacing the kernel is no option for end users. The modules I provide are going into a folder on the sdcard, and can be "insmod'ed" from there with no problem - once their magic string and the "modversions" are matching the kernel on the device. The latter is the wall I'm hitting ...
JFDee said:
Unfortunately, replacing the kernel is no option for end users. The modules I provide are going into a folder on the sdcard, and can be "insmod'ed" from there with no problem - once their magic string and the "modversions" are matching the kernel on the device. The latter is the wall I'm hitting ...
Click to expand...
Click to collapse
Thanx alot for such a great development. ...
Adi™
Creator Of Sungsonic™HD
I have received a reply from Samsung. They have updated the JB open source package for GT-P3110, GT-P5110 and GT-N7100 (which previously included a config file from 3.0.15 for a kernel version of 3.0.31 !!).
Unfortunately, the modversions of the compiled kernel are still different and incompatible. I have replied with these finding.
Waiting again ...
BTW, the only recent kernel config consistent with the actual device kernel that I have found is for the GT-N8000 (3.0.31). So it is possible to provide a matching configuration.
JFDee said:
I have received a reply from Samsung. They have updated the JB open source package for GT-P3110, GT-P5110 and GT-N7100 (which previously included a config file from 3.0.15 for a kernel version of 3.0.31 !!).
Unfortunately, the modversions of the compiled kernel are still different and incompatible. I have replied with these finding.
Waiting again ...
BTW, the only recent kernel config consistent with the actual device kernel that I have found is for the GT-N8000 (3.0.31). So it is possible to provide a matching configuration.
Click to expand...
Click to collapse
If You will start to work with kernel I'm willing to beta test with my P5110. Only issue for me is that I need to know what 3G dongle to buy (well need it anyway so would prefer an advice from someone who know something about it). I'm living in Poland and Ireland (once here once there) so I can even test LTE modems (well donations here, myself can spend up to ~50€ on 3G one) because in Wroclaw, Poland I heard it's quite good, also I got H+/H on SGSII here. While in Ireland signal is not THAT strong due to fact most of places are quite remote (except Dublin, Galway etc). Hope I can help in either way
This is what I wrote to Samsung concerning the botched configuration file provided with the latest GT-P3110 kernel source:
Thank you for the source code update.
However, I have asked for the kernel configuration that matches exactly the kernel on the GT-P3110.
I have compiled the kernel from the provided update, but the module layout checksum does *not* match the one from the kernel running on my device.
On the device: module_layout 0xb5a27644
From source: module_layout 0x143474f1
I have used the recommended toolchain "CodeSourcery 2010q1" and the unchanged config file provided with the source ("android_espresso_omap4430_r04_user_defconfig").
Please be aware that you are obliged by the GPL to provide the correct config file for the binary kernel that you are distributing.
As a side note: the configuration provided with the kernel source for the GT-N8000 *does* match the kernel on the device, so there is no doubt that it is possible to get the configuration right.
Other Android vendors are just enabling the "embedded" config file in the kernel, so that the correct configuration is simply available on the device as "/proc/config.gz". This is so much less trouble. I suggest that you enable this option for Samsung kernels too.
Regards,
...
Click to expand...
Click to collapse
The GT-N8010 is also in the same situation you describe - config for 3.0.15 and jb stock kernel at 3.0.31, can't build working modules for stock.
davp, there seems to have been some activity at the Samsung open source center after my messages.
I suggest you make yourself heard as well. Use the "Inquiry" button next to the package download link in the table for your device.
To be able to add working modules to the device, the kernel configuration for the source has to be 100% compatible. It does not matter if any closed drivers are missing as we don't want to replace the kernel - but all those general debugging config options should be correct.
BTW, there is a history of similar issues:
http://forum.xda-developers.com/showthread.php?t=1123643
The kernel source for the GT-P3110 has been updated once more, and this time they have fixed the configuration.
With the latest JB update we can actually build working modules for the current firmware.
I confirmed this to the Samsung people and reminded them of the other devices in need of this fix: GT-P3100, GT-P5100, GT-P5110, GT-N7100 and probably more (like the GT-N8010).
JFDee said:
The kernel source for the GT-P3110 has been updated once more, and this time they have fixed the configuration.
With the latest JB update we can actually build working modules for the current firmware.
I confirmed this to the Samsung people and reminded them of the other devices in need of this fix: GT-P3100, GT-P5100, GT-P5110, GT-N7100 and probably more (like the GT-N8010).
Click to expand...
Click to collapse
So for now we might get stock kernel which will support 3G modems via USB OTG? How about other kernels such as CM10.1?
I'm looking for good 3G dongle then Any advices?
Additional kernel modules for stock JB P31xx (tested) and P51xx (untested), contains:
- usb_wwan, ppp_async, and option module for PPP Widget
- dns_resolver, md4, and cifs module for cifs/samba filesystem support
- sunrpc, lockd, and nfs module for nfs filesystem support
Kernel config file attached.
FTDI Single Port Serial Driver added.
cifs.ko not working on P3100 JB 4.1.2 (stock rooted)
ketut.kumajaya said:
Additional kernel modules for stock JB P31xx (tested) and P51xx (untested), contains:
- usb_wwan, ppp_async, and option module for PPP Widget
- dns_resolver, md4, and cifs module for cifs/samba filesystem support
- sunrpc, lockd, and nfs module for nfs filesystem support
Kernel config file attached.
Click to expand...
Click to collapse
Hi ketut.kumajaya,
I'm trying to use cifs.ko but i get:
/system/lib/modules # insmod cifs.ko
insmod: can't insert 'cifs.ko': unknown symbol in module or invalid parameter
I have:
/system/lib/modules # uname -a
Linux localhost 3.0.31-1084989 #1 SMP PREEMPT Mon Mar 25 14:53:07 KST 2013 armv7l GNU/Linux
I tried other cirs.ko with same result.
Can you give me some clues of what can I do?
Thank you.
Try insmod in order:
insmod dns_resolver.ko
insmod md4.ko
insmod cifs.ko
If something goes wrong, see the kernel messages using dmesg.
ketut.kumajaya said:
Try insmod in order:
insmod dns_resolver.ko
insmod md4.ko
insmod cifs.ko
If something goes wrong, see the kernel messages using dmesg.
Click to expand...
Click to collapse
Great!!!
That's the solution.
In my Tab 10.1 4.0.4 I'm loading (different kernel and different modules, of course):
insmod cifs.ko
insmod md4.ko
insmod nls_utf8.ko
So I was not thinking I should use a different order.
Thank you.

Categories

Resources