yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] neonsector:
I lol'ed irl, but in all true them dudes would be all over you even if you weren't holding anything :D
[Galaxy S II Q&A, Help & Troubleshooting] PureMind0:
Hello

I was using CM7 ROMs and few days ago moved to Omega aokp

with the cm ones I used to have a problem with the phone freezing and then rebooting itself, usually when an app tried to use data when there's no signal and sometimes just by scrolling in the music library. also with the market but that's a known bug I think with gb versions

now with the Omega rom I don't seem to have the problem as often and it's not happening on the same occasions but sometimes when on an app (mostly online games) the app would freeze (and not auto reboot like it was on cm) so I need to manually reboot.. also the online games seem to work slower (both with wifi and data no matter the speed) and behave a bit weird with the touch

maybe the games are not yet working good with 4.04 but not sure

can it be a bad root?

and if so, which is the recommended way to root? didn't do that for awhile
[Galaxy S II Q&A, Help & Troubleshooting] Deleted member 4038153:
Revert to stock and factory reset. If that doesn't resolve your problems, contact the developers of whatever games you're using.
[Galaxy S II Q&A, Help & Troubleshooting] PureMind0:
will I need to root again after that?
[Android Q&A, Help & Troubleshooting] ictleerling:
Dear all,

I hope you guys have a solution for the following problem:

I wan't to AUTO connect 2 bluetooth devices in my car.

1 device uses phone-audio (parrot) and the otoher ad2p protocol (car-radio)..

It only auto-connects 1 device. Somethimes the parrot and the other time my radio. When i connect the other device by hand its connected to 2 devices.

I have an origonal rom on my HTC sensation. I had the same problem with the revolution rom.

Tnx (sorry for my bad english)
[Android Q&A, Help & Troubleshooting] ictleerling:
nobody ? :P
[Android Q&A, Help & Troubleshooting] wag3slav3:
You are not alone in this. I can only find one bluetooth auto-connect app, it will only allow the selection of a single device.

Also, it uses the device hardware name, not the name you entered into your BT menu. I have two dongles that are the same name, but since it doesn't differentiate I can't even use it for the single device if the other one has been paired and not deleted, it seems to randomly pick one of the devices.

If the dev would allow multiple devices to be auto-connected and at least differentiate via BT MAC rather than device name it would cover me fine.

http://xdaforums.com/showthread.php?t=1543666
[Android Q&A, Help & Troubleshooting] ictleerling:
The app 'quick bluetooth lite' works. It now connects 95% of the time.
[Galaxy S III Q&A, Help & Troubleshooting] micxploed:
Reason is, t mobile won't be getting the quad core version. I have two new HTC one s's and I'm thinking of trading them both for an international gs3. Or, I'm going to sell them both. I have an offer from a salesman to buy the international gs3 for $700 even. What do you guys think I should do?
[Galaxy S III Q&A, Help & Troubleshooting] WCCobra:
I believe it's like the One X. Yes, it will work but you'll be limited to 3G speeds (also limited to 1GB ram instead of 2GB in the US version).
[Galaxy S III Q&A, Help & Troubleshooting] MadJoe:
The RAM thing i think makes it worth it to just go with the US version. The S4 handles vet nicely, and the majority of apps don't bother to take advantage of quad core anyway, so to me the US for once gets the better end of the stick with regard to the GS3.
[Galaxy S III Q&A, Help & Troubleshooting] Mr.Mischief:
That is incorrect. For a phone to be able to utilize T-Mobile 3G/4G, it must support the both 1700 and 2100 frequencies. While the international S3 does support the 2100 band, it doesn't support the 1700 band. That is the entire reason Samsung is making a specific T-Mobile S3.

The international S3 will work with T-Mobile, but only at 2G speeds.
[Galaxy S III Q&A, Help & Troubleshooting] setzer715:
It will be 2G only, for now. Once T-Mobile has 1900 3G up and running it will be 3G again, which should be done for all major markets by the end of the year.

On another not. I've seen the TMOUS SGSIII in action and trust me, you don't need the quad core. 2GB of RAM with dual core is WAY better than 1GB of RAM with quad core.

EDIT: One more thing, the EU version is limited to 21Mbps while the TMOUS will be 42Mbps, twice the data rate.
[Galaxy S III Q&A, Help & Troubleshooting] JDenson77:
Yes I agree if I had my choice I would get tha quad 4 with 2 gigs ram but since it dosnt come that way more ram is more noticeable and quad core is nice but really what are you doing with it your running linux.
[Galaxy S III Q&A, Help & Troubleshooting] Totòòò:
Get the tmobile version. You wont notice the cpu difference at all. and never trade two htc one s for one sgs3 lol thats crazy.
[Galaxy S III Q&A, Help & Troubleshooting] witeboy07:
Hell no...two phones that just came out for one phone..don't do it..sell them separately. Higher cash value,buy s3 and have extra cash..lol
[Galaxy S III Q&A, Help & Troubleshooting] micxploed:
Yea, I figured trading two for one might be a little crazy. It sucks that I got this phone weeks before the gs3 hits shelves. I guess we shall see how awesome the gs3 is.
[Galaxy S III Q&A, Help & Troubleshooting] micxploed:
Well, it happen. I sold my HTC one s and now I wait for the SGS3 in three days.
[Galaxy S III Original Android Development] viulian:
Since I have received the JB update, I have rebuilt the cifs.ko module for my kernel version 3.0.31-256827 as well as 3.0.31-204919

If you have other kernel versions, please let me know and I will try to build the modules for that specific version.

Good news is that patchs3k is not needed anymore! Samsung did the right thing and we don't need to patch the kernel at runtime.

Per [MENTION=278676]jfrm[/MENTION] request, UTF-8 module is now included but DO NOT FORGET to add iocharset=utf8 as options when defining the share in CifsManager.

Download

Use at your own risk!

For JB Kernel 3.0.31-368423

cifs_md4-368423.tar.gz

For JB Kernel 3.0.31-256827:

cifs_md4-256827.tar.gz

For JB Kernel 3.0.31-204919

cifs_md4-204919.tar.gz

For JB Kernel 3.0.31-566833

cifs_md4-566833.tar.gz

For JB Kernel 3.0.31-742798

cifs_md4-742798.tar.gz

------

Old topic below, related to the 4.0.1 versions / firmware

Attached you will find a bundle (including the cifs.ko module) that allows you to mount Samba shares on your Galaxy S3 phone. md4.ko module is also included.

You do not need to flash a different kernel, it works with the stock one!

Supported firmwares: XXALE8, XXALEF, ZSALED

Install

a) copy cifs_s3.tar.gz to your /sdcard folder

a) create folder /system/xbin/lib (after you remount your /system as read/write)

b) unpack the tar into that folder

c) execute script load_cifs.sh

cd /system/xbin/lib
tar xf /sdcard/cifs_s3.tar.gz
./load_cifs.sh

The archive includes the patchs3k executable I have created that changes the live stock kernel to accept any module.

Without running the patchs3k file, no modules can be inserted ...

It means that you cannot use tools that insert the modules at reboot since they will fail if patchs3k is not executed before that.

For this, you will find the load_cifs.sh which is already written so that it can be executed from Script Manager at boot / as super user.

Then you need to use CifsManager (or other mount managers) to mount everything you want

Download

Use at your own risk!

For firmware: XXALE8, XXALEF

cifs_s3.tar.gz

For firmware: ZSALED

cifs_s3.ZSALED.tar.gz
[Galaxy S III Original Android Development] vasha100:
ZSALED can't use it.

Unfortunatly, when I try to run insmod, I get this: insmod: init_module '/system/xbin/lib/cifs.ko' failed (Exec format error)
[Galaxy S III Original Android Development] viulian:
@vasha100 - thanks for letting me know. I tested only on European one, XXALE8 ...

I will send you a PM and I can get it to run for your firmware too, not the module - the module stays as it is, but I will post another patchs3k file.
[Galaxy S III Original Android Development] zsoft:
on firmwares: XXALEF works,

Thank you so much!
[Galaxy S III Original Android Development] viulian:
Thanks for the feedback, I have updated the main post - so that people could see what firmwares are supported. If the exact kernel image is used, chances are that the patchs3k will work.
[Galaxy S III Original Android Development] jaidev.s:
thanks!
[Galaxy S III Original Android Development] E:V:A:
Nice work!
[Galaxy S III Original Android Development] viulian:
Thank you,

With help from fellow member vasha100 - I was able to test the release for ZSALED and confirmed it working too. Everything had to be recompiled, since the kernel is not exactly what runs on the other firmwares ..
[Galaxy S III Original Android Development] Phuongld:
Could you build tun.ko module? That will be great if you do this.
[Galaxy S III Original Android Development] viulian:
tun.ko was my first choice before starting :) but I was surprised to see that is already precompiled in the stock kernel.

You can just install the OpenVPN installer and Settings apps, copy over your certificates and so on and it will work.
[Galaxy S III Original Android Development] zsoft:
updated the fw to XXALF5, the last official update for Russia (it is on wi-fi, accidentally pressed the install)

method of root CF-Root v6.3

Сopy cifs_s3.tar.gz - all the instructions ... execute script load_cifs.sh, restart your phone....

Сopy cifs_s3.ZSALED.tar.gz, execute script load_cifs.sh, wrote the script is executed ...

I go to the cifsmanager, run a share, write error (mount no such device)

need your help)
[Galaxy S III Original Android Development] mrmrmrmr:
I have kernel XALEB

what can I do ?
[Galaxy S III Original Android Development] viulian:
Hello guys,

I will shortly put a tutorial on how you can send me the details which would help create the patch.
[Galaxy S III Original Android Development] mrmrmrmr:
this has worked on my kernel XALEB when I run patchs3k.

But I really wonder the affect of patchs3k on the kernel. What does it really do ?

it doesn't modify the kernel but changes a parameter in /proc ?

now , I need to run this in each boot.

how can we automize it ?
[Galaxy S III Original Android Development] viulian:
@mrmrmrmr

The effects of patchs3k is that it cancels the checksum verifications of module symbols. This is done within the kernel and it can't be done just by changes within /proc filesystem.

As for adding support of other kernels not already supported, please do the following and post here the values as well as your firmware:

cat /proc/kallsyms | grep -A 1 check_version

and

uname -a

I will get them done in few days ...
[Galaxy S III Original Android Development] mrmrmrmr:
Hi,

My baseband: I9300XXLE8

Build: IMM76D.I9300XXALEB

cat /proc/kallsyms | grep -A 1 check_version

c00b5200 t check_version
c00b52d0 t get_modinfo
--
c03cd0b0 t picolcd_check_version
c03cd188 t picolcd_probe

uname -a :

Linux localhost 3.0.15-554452-user #1 SMP PREEMPT Fri May 18 00:04:22 KST 2012 armv71 GNU/Linux

if you prepare a cifs.ko for these values, I assume I will not need to run patchs3k at every boot.

am I correct ?

Btw, I have a linux box with armv7 compiler. Can you tell me how to prepare the setup for compiling a kernel (or modules) for Galaxy S3 ?

is there a quick guide ?

Thanks.
[Galaxy S III Original Android Development] zsoft:
Baseband: I9300XXLF5

Build: IMM76D.I9300XXALF5

uname -a

linux localhost 3.0.15-686526-user #1 SMP PREEMPT Thu Jun 7 20:04:56 kst 2012 armv71 GNU/Linux

cat /proc/kallsyms | grep -A 1 check_version

c00b5248 t check_version
c00b5318 t get_modinfo
--
c03cd574 t picolcd_check_version
c03cd64c t pricolcd_probe
[Galaxy S III Original Android Development] mrmrmrmr:
I'd appreciate an answer :)
[Galaxy S III Original Android Development] viulian:
wow how many kernels are out there ??

Kidding :) I will do them this weekend..
[Galaxy S III Original Android Development] vI3Tz:
Hi,

can you give me a more detailed description how to do this? Is it done via file explorer and terminal app on the phone itself? Because i tried it this way and cant create the required folder.

Sorry for the stupid question, but Im quit new to this stuff.
[Galaxy S III Original Android Development] ascariz:
You here viulian! Welcome to s3. :)
[Galaxy S III Original Android Development] Stetanchi:
Hi it works very well, but when the Phone runs out of battery I need to execute the script again.

Is there any chance to apply this permanently?

Thanks, Stef.
[Galaxy S III Original Android Development] viulian:
I welcome you to S3 too :laugh:

If you want to execute it after each boot - I think you could use Script Manager or something similar ?
[Galaxy S III Original Android Development] rmagere:
Will it work with XXLFB (baseband) XXBLFB (build)?

Also could you expand on the instructions below? Is it just a terminal emulator?

Thanks

Edit:

Additional question: why does cifsmanager not work without this patch while AndSMB works out of the box? (although AndSMB is not as good a solution as it does not emulate local availability)
[Galaxy S III Original Android Development] weezil:
Running omega 9.1 rooted, kernel XXBLG1 ??

I did:

$su

app_128@android:/system/xbin/lib # ./patchs3k

1|app_128@android:/system/xbin/lib # ./load_cifs.sh

insmod: init_module '/system/xbin/lib/md4.ko' failed (Exec format error)

insmod: init_module '/system/xbin/lib/cifs.ko' failed (Exec format error)

Cat:

kallsyms | grep -A 1 check_version <

c00b520c t check_version

c00b52dc t get_modinfo

--

c03ce1cc t picolcd_check_version

c03ce2a4 t picolcd_probe

app_128@android:/system/xbin/lib # uname -a

Linux localhost 3.0.15-782020-user #1 SMP PREEMPT Thu Jul 5 10:09:44 KST 2012 armv7l GNU/Linux

app_128@android:/system/xbin/lib #

Hints? Tips? Help?
[Galaxy S III Original Android Development] enzephalon:
Hello

I tried the modul, but it doesn't work on SGS3 ALF6.

If I start load_cifs.sh the device is rebooting.

Its a problem with compatibility or did I something wrong?

Best regards

EnzephaloN
[Galaxy S III Original Android Development] enzephalon:
I switched to the new stock-kernel (see below), but knothing changed by using cifs-module :(
[Galaxy S III Original Android Development] jfrm:
Newest Builds?

Any chance to get modules for last stock kernels?
[Galaxy S III Original Android Development] ninocass:
also keen to get something working on

Model: GT-i9300

Android V: 4.0.4

Baseband: I9300XXLG8

Build: IMM76D.I9300XXBLG8

Kernel - 3.0.15-928452

I'll have a go at building the tool chain too.
[Galaxy S III Original Android Development] viulian:
Hey guys,

I will attempt to do it for ALF5 (XLF5) this weekend since this is what my phone reports as being the latest for me.

Anybody else using this version ?
[Galaxy S III Original Android Development] andreasy:
Any plans for latest jelly bean DLIB FW?
[Galaxy S III Original Android Development] mrprozac:
Thanks for the modules but unfortunately it doesn't work for me on XXBLH1

The device returns the same error as ZSALED used to do.

insmod: init_module '/system/xbin/lib/cifs.ko' failed (Exec format error)
[Galaxy S III Original Android Development] viulian:
After a waiting that took forever, few days ago I have finally received the JB update for my S3.

I have rebuilt the modules for my kernel version which is 3.0.31-256827 - and you will find the link in the first post of the thread : http://xdaforums.com/showthread.php?p=27113380#post27113380

Firmware numbers don't matter on JB apparently, if you guys have other stock kernel version, please let me know and I'll try to build the modules for that specific version if I get some spare time.
[Galaxy S III Original Android Development] Iron3d:
Hi guys, my s3 is flashed with the JB XXDLJ2 firmware, kernel 3.0.31-319653.

How can i get cifs support working?

That's what i see when i try to run "load_cifs.sh"

insmod: can't insert '/system/xbin/lib/md4.ko': invalid module format

insmod: can't insert '/system/xbin/lib/cifs.ko': invalid module format

Thanks in advance!

Kwartz
[Galaxy S III Original Android Development] viulian:
@Iron3D - the new modules do not need the patchs3k .. are you using it somehow ?
[Galaxy S III Original Android Development] alexx910:
hey ironman, before insmod the modules (i guess you want to make a xbox360 controller work like me :D) you have to get su

so just write "su -"

then the $ sign changes to #

good luck.

and at the topic starter:

Hey man, how do you compile these modules, can you make a very short guide for me? :) pls

I'm totally new in this section and dont have an idea how to get further with my plans make a x360 controller works.
[Galaxy S III Original Android Development] jfrm:
Finally a new version for JB...

Thanks for your nice work.

How should I install the new modules?

there is not any script inside...
[Galaxy S III Original Android Development] viulian:
Well :) the commands below should do the job:

insmod md4.ko

insmod cifs.ko

Or, you can use the script from the previous archive and just delete the line with the patchs3k command.

What kernel version do you have ?
[Galaxy S III Original Android Development] jfrm:
Thanks,

I'm on 3.0.31-204919 (the one that came with XXDLIB) but I was planning to search wich rom has the one you are working in, because i really need Cifs.

By the way, which is your current Rom?
[Galaxy S III Original Android Development] viulian:
@ jfrm

Please check first post, I built it for your kernel - no need (hopefully!) to change ROM. Please let me know if you try it out and it works :) otherwise I have to take it down from there.

Also, in the unlikely event that it doesn't work, please tell me the errors in dmesg - maybe they could help sorting out the problem.
[Galaxy S III Original Android Development] jfrm:
Wow!!!

Taylor made...

Wil try right now and report.

You are so kind...

EDIT:

Already try your modules an all is workig. I Really thank you.

Just one question: is unicode charset supported? I'm finding a lot of odd characters while browsing my spanish named files ...
[Galaxy S III Original Android Development] viulian:
You are right, I keep all my files in with English names so I did not spot the difference. Please redownload from first post - nls_utf8.ko is now included.

Also, do not forget the iocharset=utf8 as options when you define the share in CifsManager (or you can Edit it and add the options, then remount).
[Galaxy S III Original Android Development] jfrm:
Again all working, even our beloved spanish "ñ" and all the accents.

You'r my hero....

If any one is using mount manager, instead of cifs manager, and want to add the new charset you will need to add a property to the share (+ button), select charset and then write utf8. The charset option don't appear by default.
[Galaxy S III Original Android Development] viulian:
¡Muy bien! :cowboy:
[Galaxy S III Original Android Development] djmwj:
Thanks for your work. I was hoping you could give a brief run through on how you compiled the modules. I have kernel 3.0.31-329968 on jellybean with sonic gs3 rom. I was hoping to build modules for it. Thanks.
[Galaxy S III Original Android Development] viulian:
cifs module (as well as the other 2 companions, the nls_utf8 and md4) are already part of the kernel source - so as long as you can build your kernel, you should also obtain the necessary modules.

I don't have a tutorial on how to build the kernel, but you have to start by editing the EXTRAVERSION and CROSS_COMPILE variables within the root Makefile. Please do a Google search including these two keywords, and you should be good to go.
[Galaxy S III Original Android Development] viulian:
On request from a fellow member - rodrimartins, I have also added build for version 3.0.31-368423 of the kernel.

Please check the first post of the thread.
[Galaxy S III Original Android Development] ninocass:
EDIT: Seems to be working now, bizzare!

Thanks for building this but im having some issues the following is over adb:

shell@android:/system/xbin/lib # id
uid=0(root) gid=0(root)

shell@android:/system/xbin/lib # pwd
/system/xbin/lib

shell@android:/system/xbin/lib # insmod cifs.ko
insmod cifs.ko

shell@android:/system/xbin/lib # lsmod
lsmod
md4 3393 0 - Live 0x00000000
cifs 242799 0 - Live 0x00000000
dhd 412467 0 - Live 0x00000000
btlock 1576 0 - Live 0x00000000
exfat_fs 17079 0 - Live 0x00000000 (P)
exfat_core 59623 1 exfat_fs, Live 0x00000000 (P)

shell@android:/system/xbin/lib # mount -t cifs //<ip>/storage/ /mnt/cifs
mount: No such file or directory

cifs manager and mount manager also fail to work :S
[Galaxy S III Original Android Development] viulian:
@ninocass

You have to specify username and password otherwise mine says Invalid Argument.

Can you please try also with -o ?

mount -o username=XXXX,password=XXXX -t cifs //ip/share /mnt/cifs

Of course, /mnt/cifs has to exist.
[Galaxy S III Original Android Development] mrmrmrmr:
is there any compiled cifs module for kernel 3.0.31-487742 ?

can I use the closest one in OP ?

---------- Post added at 11:25 PM ---------- Previous post was at 10:39 PM ----------

I just tried it.

The module loads but does not work.

Can't mount any cifs share.

So, I guess I need a cifs module specially for kernel 3.0.31-487742
[Galaxy S III Original Android Development] viulian:
Is there any output in dmesg related to the module not working ?

What error do you get ? I will try to build one tonight for your version of kernel - can you please post the output of mount command above when you are trying to connect ?
[Galaxy S III Original Android Development] mrmrmrmr:
I don't get any error when I introduce the module with insmod.

And after that I can see the module added in "lsmod" output.

On dmesg, I grep "cifs" and nothing shows up.

So there is no problem in adding the module.

But when I try to use it with cifs manager, I get error "mount: No such file or directory"

Prior to 4.1.2 rom, I was able to use same app with SiyahKernel and its cifs module.

p.s:if I don't insmod the module I get a different error on cifs manager : "mount: No such device"

thx.

---------- Post added at 10:15 PM ---------- Previous post was at 10:04 PM ----------

oops, I've found the problem.

if I insmod also md4.ko and nls_utf8.ko, then it works !

but with the 4.1.1 rom and SiyahKernel, I didn't need that.

What's the difference ?

And how can I force insmodding other modules with cifs manager ?

(normally, cifs manager insmods cifs.ko automatically)
[Galaxy S III Original Android Development] viulian:
Excellent :)

About CIFS manager, it is not obvious that it can load multiple modules, but it can:

On the "Path to cifs.ko" when you edit it, you CAN actually add more modules if you separate them with semicolons like the label of the popup indicates:

/module1.ko:/module2.ko etc.

Please make sure md4 and nls come first, before cifs and that you use full paths just to be sure (but you can test if you want).
[Galaxy S III Original Android Development] mrmrmrmr:
ok; I've found the way for adding 2 module in cifs manager

entered " /mnt/sdcard/cifs/md4.ko;insmod /mnt/sdcard/cifs/cifs.ko" in cifs manager and now it's working.

But I still wonder how it was working in previous rom/kernel pair...
[Galaxy S III Original Android Development] viulian:
Well, it worked probably because the ROM was built in such a way that the /lib/modules had the correct paths containing the kernel versions (Linux like, but not the way it is on most Android phones) and then the modules could actually "ask" for their dependencies to be loaded so it was transparent for you.

One explanation. Maybe there are others, I don't know the ROM so it is just guess..

About CIFS, you don't need to have insmod command, just the path to each module separated by ':' Also you need nls if you have UTF8 characters in your shares names.