yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] richyy74:
Working for me.

Thanks

Just a quick question because I failed with it: did you do any config other than enabling cifs?
[Galaxy S II Original Android Development] m_pascal:
Now "insmod cifs.ko" command has been accepted but "insmod slow-work.ko" tell me that that module has been inserited.

If the actual module is the same of yesterday there are no problem because yesterday I inserited it, otherwise I need the command for to remove the old module.

Let's go for try this hack!!! Thanks!!!
[Galaxy S II Original Android Development] jps1974:
The new version is working for me on stock KE2 (now Mount Manager isn't working with the Galaxy S II, but that's a different story ;) -> CifsManager works fine). Thanks!

May I ask what was changed in the latest version to make it work?
[Galaxy S II Original Android Development] m_pascal:
Grrrr!!!! I've installed Astro and his SMB module but, when I click on wifi button in the program, Astro crashes.

On Galaxy S I had the same problem.

Is there another program for to try this cifs.ko with pc?

Question 2: With this hack is possible to stream videos from pc to SGS2, viceversa, or both the directions? And It's the same for http/ftp connections?
[Galaxy S II Original Android Development] jps1974:
You don't need the SMB module - that's the whole point of the cifs module, so you can mount your shares within the phone's file system. Try CifsManager from the market, it will mount your shares to /mnt/cifs/<share> by default so you can access it with any file manager, and yes, any video player. It can also load the modules - put in the following to load both (my modules are in /sdcard/):

slow-work.ko;insmod /sdcard/cifs.ko
[Galaxy S II Original Android Development] mdalacu:
I've used Android Terminal and Cifs Manager to get this working. And really works!

Can we increase the read ahead buffer for cifs, does such a thing even exists? I need this because i've tried to play a 480p avi with mobo player and it was choppy because of constant buffering.

Thank you.

This is what i've used with Android Terminal after i've extracted the contents of cifs-for-GT-I9100.zip (from first post) to the root of my internal sdcard (/mnt/sdcard):

Note: After i have disabled wifi and put the phone in standbay for 30 minutes, it was very hot so i have restated it. Any ideeas?
[Galaxy S II Original Android Development] jackleung:
nls_utf8.ko for Galaxy SII?

Hi I have some files/folders in Chinese. Where can I find the nls_utf8.ko for Galxay SII, thx?
[Galaxy S II Original Android Development] jps1974:
Should not be necessary, AFAIK the kernel has this built in. You do need to use the mount option 'iocharset=utf8' though.
[Galaxy S II Original Android Development] rocketrobot:
I am interested in this as well, any video with a high bit rate seems to be jumpy.
[Galaxy S II Original Android Development] adverse:
All of this quiet over whelming is there a simpler way to enable this for stock kernel?

the *nood* way. Just wondering, not trying to piss anyone off.
[Galaxy S II Original Android Development] jackleung:
I am root and using stock KE7 kernel. Once I use this option in CifsManager, it reports segmentation fault error. Without such option, I can mount ok but with garbage characters for those Chinese named folder.

edit: you are right. It's built-in and I can mount properly with CLI. Probably something wrong with CifsManager. Someone already report this issue to the developer (http://xdaforums.com/showpost.php?p=13480264&postcount=351)
[Galaxy S II Original Android Development] Toss3:
This is all really simple(requires root) - download the cifs. ko and slow-work.ko files and put them on your sdcard. Then just download "terminal emulator" from the market and "cifs manager". Now open up the terminal and input the following:

$su

# insmod /mnt/sdcard/slow-work.ko

# insmod /mnt/sdcard/cifs.ko

(remember to click "Allow" at the root privlidges popup)

Then open cifs manager and click "Add new share.." and input the ip adress and folder for your share and voila you're done! Shouldn't take you more than a minute or so! ;)

Note: I got an input/output error when I tried mounting a shared folder on an account without a password(Windows 7 64-bit).
[Galaxy S II Original Android Development] Slick_42:
Copy the two files to the sdcard and use cifsmanager from the Android market. Add the line "/mnt/sdcard/slow-work.ko:/mnt/sdcard/cifs.ko" to the advanced settings. Activate the "load per insmod " and the load on start options.
[Galaxy S II Original Android Development] thanku:
Many thanks this made very simple for me too.

However for me I have to type the the following in cisfs manger to get it to work

/sdcard/slow-work.ko:/sdcard/cifs.ko

Many Thanks
[Galaxy S II Original Android Development] huzz:
Great Stuff, thanks for tegrak!

Thought is it me or streaming files is laggy on the other hand plex works great, odd :/ Also on the same network my XOOM streams just fine via cifs itself.

Cheers.
[Galaxy S II Original Android Development] Slick_42:
The only solution for the lag I found so far is using the rock player in software mode.
[Galaxy S II Original Android Development] tegrak:
You're welcome :) XOOM.. my address is.. I'm waiting to arrive your zoom to me. :D
[Galaxy S II Original Android Development] mdalacu:
It also working great using Mobo player using software docoding. :)
[Galaxy S II Original Android Development] Slick_42:
The only problem is that software decoding eats through the battery and only work on low bitrates. Does anyone know where the lag with hardware decoding comes from? Is there a way to avoid it? Maybe a faster WLAN AP?
[Galaxy S II Original Android Development] mdalacu:
I think wireless speed has nothing to do with it, more something like irq/bus/something sharing between wireless chip and HW decoding chip part.

I really hope that is not a HW problem and this can be solved with a patch.
[Galaxy S II Original Android Development] Slick_42:
Has anyone tried the supercurio kernel with cifs? Is there the same problem?
[Galaxy S II Original Android Development] imutes:
It seems that Android does not work with 2.3.4 Is it necessary to update the module?

Thank
[Galaxy S II Original Android Development] Slick_42:
Tegrak: Could you please built a cifs.ko for stock kg1?
[Galaxy S II Original Android Development] elban:
This module works well on darky's rom 2.3.4, don't know about stock rom though.
[Galaxy S II Original Android Development] intronauta:
it doesn't work with 2.3.4 and CFroot KG1 :(
[Galaxy S II Original Android Development] xenoncorp:
Not working in xxkg1 (2.3.4) and cf/root

I don´t get to work it too in KG1.

Any idea!!!

Anybody can rebuild for Android 2.3.4.

Thanks.
[Galaxy S II Original Android Development] tegrak:
we need 2.3.4 kernel source.

you already know, KG1 is a leaked version.

therefore, there is no source code now. :)
[Galaxy S II Original Android Development] carlos67:
Just my tuppeneth worth chaps.

This works for me using the instructions provided earlier in the post. I'm on cf-rooted stock KE7. I needed to install Astro file manager because cifs manager complained that it needed this to work but after installing Astro it worked like a champ.

Now able to connect to my PC shares like before on HTC Desire. :D

Just wish I could find a circle battery mod for stock rooted KE7 odexed. Hate the boring stock one, you never know how much juice is left!!! Anyone?:confused:
[Galaxy S II Original Android Development] docn:
so that there is no source code for 2.3.4 cause its leaked... i have to get back to my old sftp method to access files from server... and wait until the sc is released.

for the future... ill wait for your lulz release @tegrak :o
[Galaxy S II Original Android Development] elban:
You can use a compiled kernel like supercore which is into darky's rom 2.3.4

It's the same old source, working on 2.3.4, probably without some enhancements made by samsung in the latest kernel, but it works with this cifs module for me :-)
[Galaxy S II Original Android Development] pierro78:
Sorry for the noobish question but is it supposed to work with the modules from the OP and the tegrak

Lulz Kernel Build 7

as found on http://xdaforums.com/showthread.php?t=1118918 ??

I tried the said modules on the said kernel but I had an error like :

"init_module '/mnt/sdcard/slow-work.ko' failed (Invalid argument)"

(not completely sure I remember the error correctly because I then tried another rom which was supposed to have working cifs [but its supplied cifs.ko didn't load either :(] )

Anybody can tell me what I am missing ??

Thanks !
[Galaxy S II Original Android Development] HellcatDroid:
Has the kernel code really changed in 2.3.4?

Don't thing so as my XXKG2 (Android 2.3.4) still says 2.6.35.7 as kernel version....

Or is it something / some module(s) in the initial ramdisk that breaks compatibility with those modules?

Or maybe something totally different?
[Galaxy S II Original Android Development] elban:
I heard the modules compiled with 2.3.3 kernel source do not load with the new kernel.

Probably kernel configuration has changed or something.
[Galaxy S II Original Android Development] HellcatDroid:
OK, wanted to try to compile those modules myself, but got a bit confused here:

Now, where is it that I have to add those lines, slow-work.c or timer.c? Or both?

And what good does it to add those functions, they are never called, are they? :confused:

// EDIT

Nevermind, I think I figured it out :)

At least the modules compiled fine and loaded without giving me an error (the precompiled ones on the first post errored with something like "exec type error").

Too bad I can't test mounting an SMB/Windows share now, have to wait till I'm home.... but if this works, I'll implement them into the kernel I am currently working on :)
[Galaxy S II Original Android Development] imutes:
I hope that these modules work well and that you share with us.

thanks
[Galaxy S II Original Android Development] HellcatDroid:
I too hope they work.... at least they did on the kernel I compiled them with (currently running on XXKG2).

And yes, sharing was definitaly the plan :)

For those who want to try them, see attachment :)

I finally managed to try them myself (i.e. actually connecting to a Windows share, not just loading the modules) - well, let pictures talk :D

- -

For the log, here's links to the original, fullsize screenshots (used smaller versions for better thread readebility ;))

http://p.lui.li/img-10721_sc20110721103844_p-r-full.png

http://p.lui.li/img-10721_sc20110721103807_p-r-full.png

http://p.lui.li/img-10721_sc20110721104353_p-r-full.png
[Galaxy S II Original Android Development] tegrak:
Wow, you already did it. and also I've just made it :)

I added the cifs module link at OP.
[Galaxy S II Original Android Development] imutes:
Fantastico!

But... something does not work for me...

Copy the modules in the root of your sdcard

In CifsManager add the line:

/ mnt / sdcard / slow - work.ko: / mnt / sdcard / cifs.ko

or

/ sdcard / slow - work.ko: / sdcard / cifs.ko

message, mount: no suhc device

Well... test terminal ( with root permissions ), enter the following:

$ su

# Insmod / mnt / sdcard / slow - work.ko

Message: $ su

Insmod: init -module "/ mnt / sdcard / slow - work.ko " failed (Exec format error)

I do not start modules :o

Tanks.
[Galaxy S II Original Android Development] HellcatDroid:
Just try without the slow-work.ko.

For some reason it's now giving me that error too, but cifs.ko loads fine and shares also mount fine via CifsManager.

Just teased a buddy with it "look what my S2 can do :p" *lol*
[Galaxy S II Original Android Development] pierro78:
is there a kernel I can download and use with these CIFS 2.3.4 modules ?

Thanks so much for the modules !

Sorry for the dumb question but is there a kernel I can download and use with these 2.3.4 modules ??

(last time I tried the 2.3.3 modules with

Lulz Kernel Build 7

but they wouldn't load :( ...)

(I am on a Cognition v1.15 XXKG1 rom ...)

Thanks again folks !!! :)
[Galaxy S II Original Android Development] HellcatDroid:
Try KG1/KG2 stock or CF-Root kernels.
[Galaxy S II Original Android Development] pierro78:
Working with CF-Root-SGS2_XX_OXA_KG1-v4.1-CWM4.zip !

(using cifs manager)

Thanks so much !!! :)

(now on to finding a good video player ;D ... EDIT : rockplayer in soft mode is working great as I've read before :D )
[Galaxy S II Original Android Development] mdalacu:
Working great with kg2, but still choppy with hw video decoder... why?
[Galaxy S II Original Android Development] imutes:
Does not work for me with CF- Root- SGS2_XX_OXA_KG2 - v4.1 - CWM4.

Cifs on the sdcard, test without slow-work module:

Activated the "load per insmod " and the load on start options.

:/sdcard/cifs.ko mount no such device

What 's wrong?
[Galaxy S II Original Android Development] pierro78:
I ve put ";" instead of ":" in my "path to cifs.ko" :

/sdcard/slow-work.ko;insmod /sdcard/cifs.ko
[Galaxy S II Original Android Development] imutes:
Great!

downloading again the modules and repeating the whole process, works now and very well.

Thank you very much.
[Galaxy S II Original Android Development] fuzijacz:
Thanks Tegrak, works fine with Litening 2.2 KG1
[Galaxy S II Original Android Development] arvati:
Any chance to this cifs.ko module work with Motorola ATRIX?
[Galaxy S II Original Android Development] Edwrib:
Hi, can rebuild to ICS LPH?

TY.
[Galaxy S II Original Android Development] sunx:
tks, it works fine on galaxy note too
[Wildfire General] sergeicapone:
can anyone help me.Windows XP SP3 I can not extract rom.zip from the official firmware. Because if I run RUU.exe it after a while (10 seconds) all disappears Local>temp. In Windows Vista everything works.

Have you try to swap Hboot from 2.1 and 2.2?
[Wildfire General] f0xy:
Think you can change the. Exe to. Zip and do it that way
[Wildfire General] sergeicapone:
thanks, but none
[Wildfire General] bx19:
Rom extraction works for me even on XP MODE virtual machine. The path to be checked is "C:\Documents and Settings\USER NAME\Local Settings\Temp".

That might be due to other issues of ur pc . And AFAIK changing extension of exe to zip will not work (maybe bcoz exes are compiled archives).

And swapping hboot makes signature lost, so no success (or downgrade not possible).
[Wildfire General] sergeicapone:
have you try to open HBoot from 2.1 or 2.2 by Hex editor and see what the difference between them ?

P.S.

(That came when you try to install Mac OSX on normal PC)
[Wildfire General] bx19:
No i haven't tried. Even if we find the differences, we can't edit the things and replace the content without loosing the signature. I think someone has tried it unsuccessfully.
[Wildfire General] sergeicapone:
I not gonna tell you where this idea came from ( long story), but we try.

Phone Wildfire Hboot 1.xxx S-OFF by xtc clip

What we have when we flash the rom.zip- HBOOT 0.80

1. Then try to put recovery clockwork-3.0.xxx

2. We load the phone, but not the network

3. then phone start to freze, and we have to roll back to buck up.

Problem maybe because hboot was from 2.1 Rus, but we need En-Tmob.

P.S.

DO NOT TRY THIS, YOU CAN BRICK YOUR PHONE.
[T-Mobile LG G2x] aquariumdrinker:
The G2x appears in the chart in the image at this post with "Mid July" under the heading "Get Healthy". Anybody have any idea what this means? Is my G2x sick now? :)

http://www.tmonews.com/2011/06/t-mobile-g2-about-to-hit-end-of-life/
[T-Mobile LG G2x] UCFJake:
I don't work for T-Mobile but my guess is a "healthy" stock level is no problems at all ordering more or getting replacements to customers and retail locations. Probably likely in stock at every location. I dunno for sure though...
[Captivate General] 1tontomato:
Just thought if give this a bump

Sent from my SAMSUNG-SGH-I897
[Captivate General] Rhiannon224:
Shouldn't this be stickied in the development section or stickied here in general.

Sent from Gingerbread on a Captivate using XDA Premium App
[Captivate General] 41LY45:
It better be. Been looking for this awhile back.

Mods, please? :D
[Captivate General] Dlev7:
Perfect timing I have always used Odin on my desktop PC, but now that I have a macbook I figured out how to get Heimdall running on my Mac.

My problem though is after I flash everything works but it goes like this:

1. AT&T Screen

2. 3G Jet across

3. Galaxy "S"

4. Black screen.

Happens everytime and then I have to use Odin to flash back to stock when Heimdall gives me the black screen.

Any idea why.

*Note everytime this happened I tried coming back to stock ROM the same exact method I use on Odin from CM7 then I tried with a JVO ROM. Both gave me the same result.
[Captivate General] axis01:
I did this a couple weeks ago with Andro3. I ran into one small problem which I finally figured out. When I ran Zadig, I had no listing for "samsung usb device". I had a device listed as "USB Gadget". Turns out, this was my Captivate. Just thought i'd share that incase any of you run across it. Once I got the proper driver in, everything went fine. Had one small hiccup when I hit start, but hit it a second time and it went through fine. I'm running W7 64bit.
[Captivate General] Superalpaca:
Huh, so I gave this a go tonight. It kept having issues with being unable to flash the factoryfs.rfs file, but then after 4 tries it worked just fine, happily flashing to stock JF6 with no kinks or anything. All pre-requisites were met, drivers were loaded properly, nothing was out of place, computer is clean, etc.

Is the program itself somewhat unstable, or could it have just been a funky download?
[Captivate General] tbrass:
No apparent changes between 1&4, but in the last attempt it worked?

Weird. You might try the command line instead of the gui ( shouldn't make a difference, but what you described shouldn't happen). I use Heimdall cli with Linux extensively and. never had a hiccup. Not even when my port had a short.
[Captivate General] TCalt7:
mac bull****

Oh god why did i switch to mac.....all of this crap for no valid reason!
[Captivate General] vladvlad12:
On windows 10 I keep getting error " The application was unable to start corectly" when trying to run heimdall. Installed all microsoft c++ 2010,2012,2015,2017,2019 still same problem. Net framework version 4+ installed. What is the problem here?
[Captivate General] SZC64:
Can it flash custom Gsi roms?
[Android] danarama:
Hi All,

Hope someone can help me with a specific error I am receiving please. I have overcome some errors already but this one, I just cannot see the wood for the trees.

I am new to compiling AOSP. Other than copying a bit from the CM7 repository, everything else is pure AOSP source. I haven't altered anything myself.

Some of the error:

make: *** [out/target/common/obj/APPS/ApplicationsProvider_intermediates/proguard.classes.jar] Error 137
make: *** Waiting for unfinished jobs....
make: *** [out/target/common/docs/doc-comment-check-timestamp] Error 45
make: *** [out/target/common/docs/api-stubs-timestamp] Error 45
Preparing output jar [/home/dan/mydroid/out/target/common/obj/APPS/AccountAndSyncSettings_intermediates/proguard.classes.jar]
Copying resources from program jar [/home/dan/mydroid/out/target/common/obj/APPS/AccountAndSyncSettings_intermediates/classes.jar]

Full Error and some lines above that here:

http://pastebin.com/5QL0bpxC

Any advice and help greatly appreciated.

Thanks in advance, Dan

Edit, if it helps, I'm trying to compile AOSP for the HTC desire (Bravo)
[Android] jbirdvegas:
What projects did you fork into from CM? You may have to fork some more in since alot of the packages are codependent.
[Android] danarama:
Thanks for the reply.

I used the cm script to obtain the proprietory files from cm7.0.3

I used hardware/qcom/gps/libbloc-api/android.mk and also a camera folder (off the top of my head can't remember the exact path. It had 2 folders in it, one of which was called test.

That's all though. Both in response to errors received on those modules.

The gps was a LOCATION_MODULE error, which I read up on but by the time I'd finished I'd forgotten what changes I'd made. I knew cm compiled fine so just swapped it out.
[Android] jbirdvegas:
did you use the entire package?

if not the entire package I would fork https://github.com/CyanogenMod/android_hardware_qcom_gps into the build from hardare/qcom/gps down
[Android] danarama:
Thanks. I shall try that and feed back :)
[Android] danarama:
No dice I am afraid.

The compile runs for 20 minutes or so before its killed. I'm pretty sure its quite far along.

I've pasted more here:

http://pastebin.com/SDqvuNtc

Last 1500 lines (or just over) if it helps identify where in the process this occurs?

Any further guidance greatly appreciated (as always ;) )
[Android] jbirdvegas:
You can try forking in cyanogenmod/framework_base_core

But then you start moving pretty far from aosp

Humm... not sure
[Android] danarama:
Thanks ill look at that and maybe revisit the location module tag too.

It would be nice if the source would just compile "out of the box" :)
[Android] gen_scheisskopf:
Found in first log- line 160:

/bin/bash: line 26: 23801 Killed LD_LIBRARY_PATH=out/host/linux-x86/lib javadoc \@out/target/product/bravo/obj/JAVA_LIBRARIES/doc-comment-check_intermediates/droiddoc-src-list -J-Xmx768m -J-Djava.library.path=out/host/linux-x86/lib -quiet -doclet DroidDoc -docletpath out/host/linux-x86/framework/clearsilver.jar:out/host/linux-x86/framework/droiddoc.jar:out/host/linux-x86/framework/apicheck.jar......

IMO there are 2 possibilities:

1.build environment is not set properly

-did you install compatibility libs that are mentioned for Froyo? These can also be needed

-is sun java set as default JVM? Check update-alternatives for java and javac

2. some files can be from a different branch (line 58)

Note: Some input files use or override a deprecated API.

(this happened to me when I accidetaly merged fixes for Arabic support into standard framework)
[Android] danarama:
Brilliant. Thanks for your response. I will double check all these things.

I did not:

Java 5: for Froyo and older

$ sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu dapper main multiverse"
$ sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu dapper-updates main multiverse"
$ sudo apt-get update
$ sudo apt-get install sun-java5-jdk

Or...

For building Froyo or an older release on a 64-bit system, several other packages are necessary to establish a 32-bit build environment:

$ sudo apt-get install gcc-multilib g++-multilib libc6-i386 libc6-dev-i386
[Android] gen_scheisskopf:
You don't need java5 (since you have java6 which is OK for Froyo also), but I'd recommend to install "several other packages are necessary to establish a 32-bit build environment"- this won't hurt but can help.

I don't remember which packages I had to install to build Redux 1.2
[Android] danarama:
Well checking the environment, I did install the froyo stuff and there is only Java so nothing to configure there with sudo update-alternatives --config java

Guess its option 2 then....

Other than the camera folder I imported (forget which it is now - Bad Dan), I imported vendor/htc/bravo for proprietary files and device/htc/bravo (so I can build) both from the CM repository

Would it be better to lunch for passion? It was that bit I was never certain of (and couldnt find the answer) so I just guessed it.

EDIT> The camera was frameworks/base/services/camera/

Sounds possible cause