I'd like to have the user configurable, accessing the server as root isn't the way to go.
(Unless this 'root' user is only for internal samba use and not global.
Another one:
I have checked the WiFi autostart but the service does not start (CM10 nightly from 01112012) at phone booting.
That's the problem!Thanks for the reply. I tried editing the settings, reinstalling and disable+enable wifi but still have the same type of errors.
Attached you can find some further screenshots including the contents of the folder you mentioned.
I noticed that on the first run it gives the error "cannot find a valid WiFi interface" as can be seen in the screenshot.
Thanks for your time and help!
Sent from my GT-N7100 using Tapatalk 2
Sureany chance we can have an option to auto-run the server @ boot ?
how about an on/off widget ?
any chance we can navigate to / and not just sdcard ?
![]()
I confirm that the user 'root' is only a "dummy" name by now (I plan to add multiusers support in the future).I'd like to have the user configurable, accessing the server as root isn't the way to go.
(Unless this 'root' user is only for internal samba use and not global.
Please forget the "Server String" option, I will probably remove that option in the next release.I'm a bit puzzled by the Netbios name vs Server String incidentally. I assume Netbios is the name under which the device will appear on the Windows network? So what's Server String?
Oh, and the tiny 'Log' button is right above (and far too close to) an advert, which needs to be moved to avoid accidental presses on the ad.
Andre
Could you be so kind to reinstall the application and see you still have problems on the first startup?I also had a problem starting the service at first, but after a reboot it started automatically...
The idea is to allow the user to configure as many shares as needed (it's on my TODOWorking great so far on my I9305, so a big thanks!
When you have time, could you please add support for the extSdCard as at the moment I can only see my internal card.
Also, how can I send the intents via Tasker? I have added the string to Send Intent/Action with Target set to broadcast receiver but cannot get it to work. I assume I am missing something as have not used Intents before, any advice welcome!
Thanks again!
Once the application will be available on the market, I'll support some in-app purchases to allow features like this: I already have experience in this (in particular with my game Drysic) so it should take not much work.How can I switch off the ads?
I do not tolerate any advertising apps on my phone.
Is there a pro version without ads planned or available that I can buy somewhere?
That's the problem!
Please help me in solving this by:
- Paste/attach here the content of the file /system/build.prop
- Give me a link of the rom you are using so that I can download it
- Paste here the output of the command "netcfg" (this should really help): you can invoke the command from your PC with adb (adb shell netcfg) or from the a terminal emulator directly in the device.
The output should be something like this:![]()
Once the application will be available on the market, I'll support some in-app purchases
I just found a bug in the code that prevent to correctly save the options, please wait for the next beta (next week)After testing on my home network, using a Galaxy Tab 10.1 (generic Samsung ICS 4.0.4 upgrade, rooted) I found:
cut
After testing on my home network, using a Galaxy Tab 10.1 (generic Samsung ICS 4.0.4 upgrade, rooted) I found:
- With wi-fi on, the App starts and says the service is running. I've set a suitable Netbios share name within the app, and used my standard Windows Workgroup name (as used for my home network).
- The shared device does not appear in my Windows 7 Network view (where I do see my other Android ICS devices listed, which are both running the old Samba app).
- If I enter the direct IP address manually (e.g. typing \\192.168.1.211 into the path area) then I do get a login prompt, but I can't seem to get it to authenticate. I just get the standard Windows "network is not accesible / you might not have pemissions" message.
- I've tried with and without a password set within the App (using 'root' as the login username from Windows) and also tried disabling the App's password tickbox, but I always get the same Windows error message.
- If I turn the app off, as expected I no longer see a login prompt when I enter the IP address in Windows (so at least I know it's your app that's responding).
Should I be typing anything else into the IP address line (a path for example?)
Andre
As I suspected the param "wifi.interface" isn't set in your build.prob file.Here is what you need:
1) build.prob attached
2) Link to my current ROM: http://www.hotfile.com/dl/177136417/0acdb72/N7100XXALJ3_N7100DBTALJ2_DBT.zip.html
3) Output of netcfg attached
Let me know if you need anything else on this..
Thanks a lot!
private String detectWifiInterface()
{
String wifiInterface = null;
try
{
for(Enumeration<NetworkInterface> i = NetworkInterface.getNetworkInterfaces(); i.hasMoreElements();)
{
wifiInterface = i.nextElement().getName();
if(wifiInterface.toLowerCase().contains("wlan"))
return wifiInterface;
}
}
catch(Exception e)
{
}
return null;
}
Thanks :good:
Ok so next "few days" has comeSure I'll wait for the next beta...![]()
I don't really have any other alternative apps for this functionality on my Android device at the moment!
Thanks a lot and let me know if you need anything else from my end to help you test or resolve any issues.
berserker_devel said:I just found a bug in the code that prevent to correctly save the options, please wait for the next beta (next week)![]()
Translated line:<string name="ftp_user_invalid_password">Invalid password</string>
Please do not translate anything inside the "name" attribute:<string name="ftp_user_invalid_password">My translation of Invalid password</string>
But only:
I already implemented a fix for this situation in the 1.0.2 betaYou figured out a solution on your own by re-installing it, but if I pointed you in the right direction, you're welcome. Another solution, if Berserker's hunch is right, would've been to change the owner of the "nmbd" folder to "root" via Solid Explorer (on the same page as the "Change" button that I mentioned earlier) or other file manager. Anyways, the problem was even simpler than realized. I take it that you had Android 4.1 (CM10) with SambaDroid installed, backed everything up with Titanium Backup, flashed Android 4.2 (CM10.1), then restored your backup. Like you said, it could be an issue with Titanium Backup not restoring ownership rights or permissions correctly for SambaDroid's folders and files. If so, it doesn't sound like a huge, huge problem, but, maybe, as a workaround for users' sakes, SambaDroid could check for and fix incorrect permissions (or, at least, somehow detect a problem and recommend a re-installation).