Hi there,
I made a preliminary port of Froyo for the Liquid.
It needs the Donut radio rom, so it won't work on LiquidE.
You can test it on an Eclair radio, but usb and GSM/3G won't work.
IHMO, It works fine for daily use (I do use it daily.), current known bugs:
-Random lines appearing on the screen on refresh
-No wifi
-Wiping data kills radio
-No tethering
-Unsigned
Hint: to enable App2SD to all apps (by default, only some apps accept it), do
Code:
pm setInstallLocation 2
This will install all apps to SD, you can move them back to phone.
Please use http://code.google.com/p/acer-liquid-froyo/issues/list as bugtracker
(Donate link in my sig also works for my Liquiid's work )
Here's the downlink link:
http://code.google.com/p/acer-liquid-froyo/downloads/detail?name=Froyo.zip
Update:
Full: http://www.megaupload.com/?d=S9P799GO
Update: http://www.megaupload.com/?d=UPAF7YD8
-880MHz
-ramzswap
-USB OTG (seems not fully working)
-working iptables (droidwall works)
-usbnet (tethering kind of works)
-changed H264 resolution limit to 720p
To get tethering working, do echo 1 > /sys/class/usb_composite/rndis/enable
Then go in the appropriate menu and tick the usb tethering option.
The results are random, I don't know why yet. The released sources might help understanding that.
How can I enable apps2sd? Where have I to insert code? I'm a noob and don't understand, I need a step by step sequence.
Thanks.
akira.pwr said:
How can I enable apps2sd? Where have I to insert code? I'm a noob and don't understand, I need a step by step sequence.
Thanks.
Click to expand...
Click to collapse
Install connectbot
Launch it on the "local" protocol, do
su
(the su manager will ask for permission, allow it)
pm setInstallLocation 2
And it's done.
Ok, i'm doing it, it create a partition for apps?
After doing what you posted above, all apps go in my sd automatically?
Connectbot asked me a nickname, i put su, then un screen i writed pm setInstallLocation 2, then i saw the word "killed", is normal?
Superuser never asked me permissions.
Edit: retried more times and finally su requested permissions, i allowed but after insert the code, i read "killed"...
akira.pwr said:
Ok, i'm doing it, it create a partition for apps?
Click to expand...
Click to collapse
Apps go to the normal vfat partition
After doing what you posted above, all apps go in my sd automatically?
Click to expand...
Click to collapse
It should
Connectbot asked me a nickname, i put su, then un screen i writed pm setInstallLocation 2, then i saw the word "killed", is normal?
Superuser never asked me permissions.
Edit: retried more times and finally su requested permissions, i allowed but after insert the code, i read "killed"...
Click to expand...
Click to collapse
You must put su on the console, not as a nickname, the nickname doesn't mean anything.
sorry, but i'm not good, i don't understand how to do it, i put code, but when i put "2", i read proces denied. I give up...
akira.pwr said:
sorry, but i'm not good, i don't understand how to do it, i put code, but when i put "2", i read proces denied. I give up...
Click to expand...
Click to collapse
Giving up is always a lot easier than to keep on trying, \0/(stole the emote from phh lol)
rafyvitto said:
Giving up is always a lot easier than to keep on trying, \0/(stole the emote from phh lol)
Click to expand...
Click to collapse
But i'm a real noob, i tried and retried, but connectbot tells me action denied, any suggestion? When/where have i do su? It never ask me permission.
akira.pwr said:
But i'm a real noob, i tried and retried, but connectbot tells me action denied, any suggestion? When/where have i do su? It never ask me permission.
Click to expand...
Click to collapse
Weird..check on malex recovery to see if your device is rooted, without root you cant run superuser command's, but since your running phhfroyo it should come already rooted...
Related
Hey guys,
Im new to Android and after being a BlackBerry user for 8 years, anyway heres my issue.
1. I did the root rom per the instructions...no problem
2. flashed the recovery and have that working...no problem
3. downloaded the .3 rom with the built in busybox and su...Here's where things get confussing for me.
I tried to use adb and it asks me (are you root?), tried adb remount and got (operation not permitted) the usb debug is on and working and the su app on the phone maintains a black screen....(I think this is not right...)
Then I closed out the current cmd window...opened a fresh cmd window and typed>adb shell and got $, then i entered su and got # from here im stuck, what are the commands to get back to adb shell and su also how do I get the whitelist permissions working...
In short adb shell worked fine with the original root rom, I'm sure its an operator error any help is appreciated.
Chris
SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.
t2noob said:
SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.
Click to expand...
Click to collapse
can you guys post a walk through for noobies? imstuckat black screen
vash8806 said:
can you guys post a walk through for noobies? imstuckat black screen
Click to expand...
Click to collapse
There are plenty around... seriously google it. But, this specific issue I just experienced. Seems on the custom ROM that is out (EvilEris) the SU request screen doesn't work right off the bat. I went and used an app on the device to request root (terminal) then when the black screen pops up, hit back or home, or action. As the phone is basically frozen at this point it prompted me to forceclose the superuser.apk. I did. Once forceclosed, it worked fine.
adb shell
su
look at phone, click allways all
...
..
.
jcase
jcase said:
adb shell
su
look at phone, click allways all
...
..
.
jcase
Click to expand...
Click to collapse
Or just download Terminal Emulator from Market.
open it up.
Type su.
Hit allow/always allow.
Now try it for other stuff (like wireless tether) and see if it pops up instead of a black screen.
haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]
vash8806 said:
haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]
Click to expand...
Click to collapse
niiiice
Hey there everyone. I have a myTouch and when I try and root using visionary it says that I am already rooted but if i go into the terminal emulator and I typer in su it says permission denied. I already wiped the os, cache, and sd. Please help
Thanks
macfan74318
Use the Manual method found here: http://forum.xda-developers.com/showthread.php?t=834225
But the problem is that I can not even get temp root. VISIONary says there is root but the terminal says permission denied when I try and get root access.
Try installing the superuser app from the market
Sent from my anti titanic
Thanks it worked perfectly.
Thanks
macfan74318
macfan74318 said:
Thanks it worked perfectly.
Thanks
macfan74318
Click to expand...
Click to collapse
Edit you post as solved.
thelamacmdr said:
Try installing the superuser app from the market
Sent from my anti titanic
Click to expand...
Click to collapse
macfan74318 said:
Thanks it worked perfectly.
Thanks
macfan74318
Click to expand...
Click to collapse
Seriously?! That's it? Ha!
What?
Why do you think that this is so funny. You have been their at one point and who knows someone else could have the problem and now they know what to do. Attitudes like this is what will lead to the downfall of the android developer community.
macfan74318 said:
Why do you think that this is so funny. You have been their at one point and who knows someone else could have the problem and now they know what to do. Attitudes like this is what will lead to the downfall of the android developer community.
Click to expand...
Click to collapse
No dude you got me wrong. I'm just amused that the problem is really solved that simply. It would never have occurred to me to try that. I've only just started playing with visionary on my phone about half an hour ago so I have virtually zero experience rooting the mt4g so far.
Was not talking **** but I totally appreciate your supportive attitude and I agree with your statements. I was a super-noob and am still pretty darn noobish. I actually enjoy helping where I can and I put links in my sig in case they come in handy for others.
Oh... Sorry for coming off so harsh.
Do you have any questions or need any help?
macfan74318
Since this is no longer development related, I am moving to General section
Okay. Sorry for being off topic. But if you need help please ask here.
Sent from my HTC Glacier using XDA App
macfan74318 said:
Oh... Sorry for coming off so harsh.
Do you have any questions or need any help?
macfan74318
Click to expand...
Click to collapse
No worries, your heart was in the right place. I think I'm ok for now. Going out of town this weekend so won't be able to play with this until probably tuesday night.
Also kinda waiting for CM6 to be available for our phones.
Yup Cyanogen Mod 6.1 will be amazing. They have already booted it but the status of the ROM is unknown
macfan74318 said:
Yup Cyanogen Mod 6.1 will be amazing. They have already booted it but the status of the ROM is unknown
Click to expand...
Click to collapse
Well it boots, but nothing works yet. Give them time.
Well kmobs says that "more will be released tonight". Maybe we will get a nightly build!
Can someone help me root my mt4g.i need wifi tethering.
Sent from my HTC Glacier using XDA App
How to root
First Question? Do you get and OTA Update (You can check by going to System -> About Phone -> Software Information. If you have gotten the update then under Android version it would say 2.2.1.
Next you need to follow this guide. http://forum.xda-developers.com/showthread.php?t=834225
What I did is I downloaded the program droid explorer (PC) (http://de.codeplex.com/) and it set up the whole adb system. All I did was to plug the phone in and copy the two files using Super Manager (Phone) and the ran the 2 commands minus the adb part of the command.
Download Visionary (http://android.modaco.com/content/t...350/10-nov-r12-test-visionary-one-click-root/) and then copy the apk file to your sd card.
Then mount your phone to your pc and copy the two files on to the root of your SD Card
Then open up super manager and go to settings and Enable ROOT Function, and show hidden files.
Then go the the copied files and cut them (Hi-light check box and hit the pair of scissors)
The keep navigating up one level until you cant go up anymore.
Then navigate to data
Then inside of data select local and paste the files there.
Then plug your phone in but dont mount it ( When you plug in it pull down the notification bar and select USB CONNECTION Change Type and change it to charge only.
The open Droid Explorer and it will recognize your phone
Look on the tool bar and hit the icon that looks like the command prompt icon.
The type su an on your phone you will get a prompt for superuser on your phone accept it.
Then copy and paste the following commands
insmod /data/local/wpx.ko You should get an error stating "function not implemented" this is what you want
dd if=/data/local/hboot_dhd.nb0 of=/dev/block/mmcblk0p18
Then type sync and wait about 5 min and then reboot.
Complete Credit for this guide goes to grankin01 I just broke it down step by step.
Hope this helps
Macfan
WiFi Fix for Android 4.0
Description
I recently found out many people in certain countries no matter what kinds of devices they're using, have issues with WiFi when SIM-Card is inserted.
I realized that changing the WiFi Country Code solves the problem and made an application that does this automatically on each boot and on network state changes.
Installation
It's pretty easy; first of all you should root your device.
Then install WiFixManager.apk.
Start WiFix Manager from applications menu and tap Install WiFix (allow SuperUser permission.)
Once installed, you're ready to go. The application will change the country code when needed. You can also invoke it manually by dialing *#94349# (*#WIFIX#) and pressing the call button (don't forget to press call button; it's not a MSL code).
Updates
You can check for updates and install them via WiFix Manager.
Code:
Change Log:
1/14/12 WiFix V1.0, WiFix Manager V1.1:
Initial Release
1/25/12 WiFix 1.1, WiFix Manager V1.2:
Changed minimum SDK version and API Level to 3
Minor layout changes
Minor bug fixes
1/30/12 WiFix 1.2, WiFix Manager V1.3:
Added custom country code support
7/3/12 WiFix V1.2, WiFix Manager V1.31:
Minor layout bug fixes
Compiled with Android SDK 14
12/9/12 WiFix V1.2, WiFix Manager V1.32
Minor bug fixes (Device compatibility improvement.)
Added reboot prompt after installation and removal.
Compiled with Android SDK 16
Known Issues
Sometimes when you reboot your phone with WiFi turned on, you won't have internet access (you can't open webpages, download files etc.) even though it says it's already connected to your AP.
This issue can be fixed by turning WiFi Off and On or dialing *#WIFIX# as described before.
For ROM Cookers
By placing WiFix.apk in /system/app you'll have a WiFix enabled ROM.
If you're publishing that ROM, please include a link to this thread
Newer fix by XDA Member HTCZ715E
As of today, most of the manufacturers (including HTC and Sony) solved this Wi-Fi issue with their ROMs. Fortunately, there's no need for WiFix anymore.
For those who still have issues with custom ROMs and WiFix, try this.
Thanks. Working fine. much simpler to setup than the script.
Not working....
While I have given the app root permissions, when I click "Install WiFix" it replies with:
"Can't get root access. Either your device is not rooted, or SuperUser request has been rejected."
Ironically, it is immediately followed by:
"WiFi Manager has been granted Superuser permissions."
Any suggestions... am I missing something?
jhedfors said:
While I have given the app root permissions, when I click "Install WiFix" it replies with:
"Can't get root access. Either your device is not rooted, or SuperUser request has been rejected."
Ironically, it is immediately followed by:
"WiFi Manager has been granted Superuser permissions."
Any suggestions... am I missing something?
Click to expand...
Click to collapse
It's a little bit strange.
Root access checking routine, basically opens su, and checks the User ID. So either it can't execute su or the id is different when you're root (!!!) or there is a problem with IO streams (I hope not.)
Anyways, you can help me fix this problem by posting the steps (from installation to error message) to reproduce the error.
Please do the following and post the result:
Install a Terminal Emulator app (this one for example) or get into shell with adb (note that installing Terminal Emulator is preferred since you always log-in as root with an insecure kernel.)
Open it and type "su" (without quotes), and press enter.
Allow SuperUser permission request.
Type "id" (without quotes), and press enter.
Post the result here.
Type "exit" (without quotes), and press enter to logout.
It will be useful to post your device and ROM information as well.
Thanks in advance for your help,
I'll fix it as soon as I realize where the problem is
omar302 said:
Thanks. Working fine. much simpler to setup than the script.
Click to expand...
Click to collapse
You're welcome
The main difference between this application and that script is, it sets the wifi_country_code property by interacting with Secure system settings provider, thus it doesn't need to gain root access and execute sqllite for changing the country code. However it should be placed in /system/app to work. (WiFix Manager does this automatically with one time root permission.)
fardjad said:
It's a little bit strange.
Root access checking routine, basically opens su, and checks the User ID. So either it can't execute su or the id is different when you're root (!!!) or there is a problem with output/input streams (I hope not.)
Anyways, if you like, you can help me fix this problem by posting the steps (From installation to error message) to reproduce the error and do the following and posting the result:
Install a Terminal Emulator app (this one for example) or get into shell with adb (note that installing Terminal Emulator is preferred since in rooted devices when you get into shell with adb shell you're already logged in as root.)
Open it and type "su" (without quotes), and press enter.
Allow SuperUser permission request.
Type "id" (without quotes), and press enter.
Post the result here.
Type "exit" (without quotes), and press enter to close the SuperUser session.
It will be useful to post your device and ROM information as well.
Thanks in advance for your help,
I'll fix it as soon as I realize where the problem is
Click to expand...
Click to collapse
My steps were:
1. Install WiFix Manager
-Successfully installed
2. Open WiFix Manager
3. Click "Install WiFix"
4. Click "Allow" on the Superuser Request pop-up
5. I then get the error above.
After entering ID in Terminal Emulator, I get the response "Toolbox!"
I have HTC Vision/G2, running "Virtuous Quattro Beta 9" in Boot Manager.
Thanks!
jhedfors said:
My steps were:
1. Install WiFix Manager
-Successfully installed
2. Open WiFix Manager
3. Click "Install WiFix"
4. Click "Allow" on the Superuser Request pop-up
5. I then get the error above.
After entering ID in Terminal Emulator, I get the response "Toolbox!"
I have HTC Vision/G2, running "Virtuous Quattro Beta 9" in Boot Manager.
Thanks!
Click to expand...
Click to collapse
OK, so the problem is the id command output. normally it should be something like uid=0(root) gid=0(root), most likely it's a rom issue (try fixing your permissions), however I will release another APK (after about 10 hours) that doesn't fail if id does not contain root.
Can I suggest something?
Why not make a flashable zip so "wifix.apk" can be flashed directly to "system/app" without having to use "wifixmanager.apk"
omar302 said:
Can I suggest something?
Why not make a flashable zip so "wifix.apk" can be flashed directly to "system/app" without having to use "wifixmanager.apk"
Click to expand...
Click to collapse
Of course
Here it is.
jhedfors said:
While I have given the app root permissions, when I click "Install WiFix" it replies with:
"Can't get root access. Either your device is not rooted, or SuperUser request has been rejected."
Ironically, it is immediately followed by:
"WiFi Manager has been granted Superuser permissions."
Any suggestions... am I missing something?
Click to expand...
Click to collapse
jhedfors said:
My steps were:
1. Install WiFix Manager
-Successfully installed
2. Open WiFix Manager
3. Click "Install WiFix"
4. Click "Allow" on the Superuser Request pop-up
5. I then get the error above.
After entering ID in Terminal Emulator, I get the response "Toolbox!"
I have HTC Vision/G2, running "Virtuous Quattro Beta 9" in Boot Manager.
Thanks!
Click to expand...
Click to collapse
OK, I updated the first post and uploaded a new APK and a Recovery Flashable Zip.
Please test and report the results
I've these issues with gb on my HTC Desire -_-
I'm not really sure I understand what problem this is fixing. I have a problem with my wifi that I want to check with you first. Mine is basically where the wifi turns itself off when I go out of range of a connected router for a few minutes . When I come back in range of the router I have to manually turn wifi back on before it will connect back to the wifi. This is despite having the sleep policy set to never so I have no idea why wifi won't stay on. I don't want to install this without understanding the issue a bit more first!
Thanks
Shane
jhedfors said:
While I have given the app root permissions, when I click "Install WiFix" it replies with:
"Can't get root access. Either your device is not rooted, or SuperUser request has been rejected."
Ironically, it is immediately followed by:
"WiFi Manager has been granted Superuser permissions."
Any suggestions... am I missing something?
Click to expand...
Click to collapse
Have you tried fixing permission first incase ur Su or binaries are out dated? Or maybe not.
Sent from my PC36100 using xda premium
Which certain countries?
TheBishopOfSoho said:
I'm not really sure I understand what problem this is fixing. I have a problem with my wifi that I want to check with you first. Mine is basically where the wifi turns itself off when I go out of range of a connected router for a few minutes . When I come back in range of the router I have to manually turn wifi back on before it will connect back to the wifi. This is despite having the sleep policy set to never so I have no idea why wifi won't stay on. I don't want to install this without understanding the issue a bit more first!
Thanks
Shane
Click to expand...
Click to collapse
I don't think that this application can solve your problem. Sorry
WiFix simply changes the WiFi country code which might be set incorrectly (?) in IceCream Sandwich builds when SIM-Card is inserted.
qwerty017 said:
Which certain countries?
Click to expand...
Click to collapse
Basically most of the countries located in Middle-east and Africa.
fardjad said:
Basically most of the countries located in Middle-east and Africa.
Click to expand...
Click to collapse
Thanks. Was wondering if it affected me or not.
qwerty017 said:
Thanks. Was wondering if it affected me or not.
Click to expand...
Click to collapse
If your phone can't find WiFi networks or can't connect to them unless you remove the SIM-Card then you're affected.
fardjad said:
Basically most of the countries located in Middle-east and Africa.
Click to expand...
Click to collapse
Very useful for me if I am traveling back home, or visiting family in NZ or AUS. Thank's for posting this.
fardjad said:
If your phone can't find WiFi networks or can't connect to them unless you remove the SIM-Card then you're affected.
Click to expand...
Click to collapse
I would suggest you put in the app introduction to explain in an easier:
"If wifi is working fine in Gingerbread roms, but does not when flashing/upgarding to IceCreamSanwich, then this app will try to fix it!"
Hi all,
First thread here .
So, on with it. I've been a member on this forum for quite some time, but never felt like posting or anything as I didn't have anything interesting to share and all the questions I might've got at some point got already answered...
Anyway, about a year a go I bought a Samsung Galaxy S III. Cute little 'monster', powerful and all... and I got hit by MTP. I'm a Linux user, so getting MTP to work was a huge pain. So I started reading, digging, found out that some guys already implemented some scripts for mounting the external SD as UMS... the problem was that they didn't work on my end.
So I developed my own little app. Nothin' fancy, two buttons to switch from MTP to UMS and back.
In the meanwhile, I changed my phone to a Note 2 LTE and did some more tweaking on my app and now I'm kinda ready to share it with you guys:laugh:.
You need to have a rooted phone equipped with busybox (my app will prompt warnings telling you you're not rooted or you don't have busybox, but I thought it was nice to tell you here the requirements).
One small thing, besides the usual "I'm not responsible to any damages brought to your phone and all": after transferring to / from your SD card, please use the eject command (or the safety remove feature on Windows) to unbind the card from your operating system before changing back to UMS. That way you ensure no harm is brought to you SD card or to the data on it.
All that being said, you can download the app from here: devver.ro/ums-mounter/ (I don't have enough posts to give an external link, so you'll have to enter the text manually in your browser). The text on that page is written both in Romanian (my native language) and English so there shouldn't be any problems .
This app should work on every device that has an SD card and runs Android 4.3+. Oh yeah, there might be some glitches on devices with Samsung's official releases (bummer, I know), but that's related to some screw-ups on their end, 'cause they're random from ROM to ROM.
Anyway, hope you'll like it (if you test it). If you have and problems, comment here and attach a logcat and I'll see if I'm smart enough to help you.
== 2014-06-10 ==
Version 1.1
Changes:
- please uninstall the previous version, as I've changed the signature on the file ;
- added a small sanity check which will force you to unplug your phone from the computer before switching between modes (hopefully this will also force you to safely remove the external sd card );
- fixed (i hope at least) the situation where the card is not mounted as usb on Touchwizz related ROMs;
As usual, the app can be downloaded from devver.ro/ums-mounter. Thanks again for testing .
sleepwalker123 said:
This app should work on every device that has an SD card and runs Android 4.3+.
Click to expand...
Click to collapse
It mounts the card slots (although it needs a reboot sometimes), but the PC shows up two empty usb slots and the sd card is not mounted.
Im running DN3 V5+.
I do hope you can fix it.
Thank you.
@erljayp: that's one ROM which is based on a stock ROM and, as I mentioned in my OP, there might be glitches woth 'em.
I'll setup my phone into dual booting so that's gonna be a bit easier to test these ROMs and hopefully sort them out.
Thanks for testing my little app
your app said that i haven't installed busybox yet. then i tried to install busybox from play store and it said the same. what problem?
ectv96 said:
your app said that i haven't installed busybox yet. then i tried to install busybox from play store and it said the same. what problem?
Click to expand...
Click to collapse
I've used play.google.com/store/apps/details?id=stericson.busybox to install busybox. Basically, after you install the app from the play store, you need to open it in order for it to actually download and install the busybox binaries. If you just downloaded the app from play store but didn't actually open it, that may be the problem
sleepwalker123 said:
I've used play.google.com/store/apps/details?id=stericson.busybox to install busybox. Basically, after you install the app from the play store, you need to open it in order for it to actually download and install the busybox binaries. If you just downloaded the app from play store but didn't actually open it, that may be the problem
Click to expand...
Click to collapse
oh yes, it works. thankyou :good::laugh:
New version, please check OP. Should resolve the DN3 related issues (this should apply to all ROMs which are based on stock Samsung). 'Njoy!
sleepwalker123 said:
there might be glitches woth 'em.
Click to expand...
Click to collapse
I thought you were talking about the "stock" rom. haha.
sleepwalker123 said:
Should resolve the DN3 related issues.
Click to expand...
Click to collapse
Now working in DN3 V5+, but I have fluctuating transfer rates. What is the average transfer rate you have?
Thank you.
@erljayp: i get about a maximum of 2 MB/s transferring a file bigger than 50-100 MB, which I find quite satisfying. Also, if I'm not mistaking, the transfer rates are influences by a lot of factors: the card's class, if you're transferring a lot of small files (mp3's, for example) etc.
Anyway, glad that sorted your problem. Like I said before, my app should now work not only on the DN3, but on all ROMs (CM11 based, AOSP, AOKP, ROM's based on the stock Samsung release). If you find a ROM that won't work, Iemme know and I'll see what's to be done about it .
sleepwalker123 said:
@erljayp: i get about a maximum of 2 MB/s transferring a file bigger than 50-100 MB, which I find quite satisfying. Also, if I'm not mistaking, the transfer rates are influences by a lot of factors.
Click to expand...
Click to collapse
I guess mine is normal.
Well, thank you very much for this great app and goodluck in your future projects.
sleepwalker123 said:
Hi all,
First thread here .
So--------.
Click to expand...
Click to collapse
The App crashes when trying to switch the pages.
Is this working on 4.4.2 TW roms ?
aukhan said:
The App crashes when trying to switch the pages.
Is this working on 4.4.2 TW roms ?
Click to expand...
Click to collapse
Don't try and switch pages All you need to do is "play" with the 2 buttons. I think the "page" you're referring to is something i use for debugging.. will remove it in a future release
sleepwalker123 said:
Don't try and switch pages All you need to do is "play" with the 2 buttons. I think the "page" you're referring to is something i use for debugging.. will remove it in a future release
Click to expand...
Click to collapse
I use Switch UMS and connect USB is that right any requirements to run the app apart from Root and busybox ?
aukhan said:
I use Switch UMS and connect USB is that right any requirements to run the app apart from Root and busybox ?
Click to expand...
Click to collapse
Nope. Those are the only requirements. Could you please give me a link to your ROM's thread?
sleepwalker123 said:
Nope. Those are the only requirements. Could you please give me a link to your ROM's thread?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=36202763#post36202763
Does this support windows or only linux??
aukhan said:
http://forum.xda-developers.com/showthread.php?p=36202763#post36202763
Does this support windows or only linux??
Click to expand...
Click to collapse
Grr... can't test that one...
Could you please connect your phone to your, connect into an adb shell, run mount and give me the output? Or if you have the Terminal Emulator app installed, do it from there and gimme the output.
sleepwalker123 said:
Grr... can't test that one...
Could you please connect your phone to your, connect into an adb shell, run mount and give me the output? Or if you have the Terminal Emulator app installed, do it from there and gimme the output.
Click to expand...
Click to collapse
You want me to run this # mount in terminal emulator and give you the results ?
Should i be connected to PC or not ?
aukhan said:
You want me to run this # mount in terminal emulator and give you the results ?
Should i be connected to PC or not ?
Click to expand...
Click to collapse
You don't have to be connected to the computer. Try and run the following in the terminal emulator:
- su (if you didn't);
- mount > /sdcard/mount.log
And after that, on your internal storage you shall find a file called mount.log. Give me the contents of that file, please.
sleepwalker123 said:
You don't have to be connected to the computer. Try and run the following in the terminal emulator:
- su (if you didn't);
- mount > /sdcard/mount.log
And after that, on your internal storage you shall find a file called mount.log. Give me the contents of that file, please.
Click to expand...
Click to collapse
Usage: mount [-r] [-w] [-o options] [-t type] device directory.
aukhan said:
Usage: mount [-r] [-w] [-o options] [-t type] device directory.
Click to expand...
Click to collapse
I think you ran the command including the dash ("-" sign).
Perhaps i didn't express myself well enough, sorry...
1). su (for gaining root access, no matter if you're doing this from the terminal emulator or from your pc);
2). mount > /sdcard/mount.log
Again, sorry for the confusion.
The option to mount network shares is nice but only grants read permissions to the shares.
I know it's because of security concerns, I also know there's some api and app whitelisting allowing Plex app write permissions.
I don't use the Plex app.
My Shield is rooted through Magisk.
I want all my installed apps to have write permissions to the shares. Imho Shield Experience should allow the user to make this decision.
Without write permissions, for me the mount option is useless.
Can anyone help me to get write permissions to my mounted shares?
ABSOLUTELY ++++++1000000 for this.
Did you get this working @trohn_javolta !??!
That's exactly my problem !! I have two ShieldTV (2017 / 16GB / 8.0.1). Both successfully rooted with Magisk.
How can I give all my installed apps WRITE RIGHTS to my network drive (NAS)?!? Or even specific apps I CAN CHOOSE !!!
It is very annoying that eg RetroArch can not save the scores, savestats, controller settings, ...
Or even xFile Explorer can not write to the my NAS.
IMHO, as long as i am rootet, i should decide by my own how "secure" i want my system !!
Please help us to write on a network drive as normal.
On my Phone i can write to my NAS (ES File explorer) without any problems... So why is the shield not allowed?!
Thank you
Kamikaze01 said:
ABSOLUTELY ++++++1000000 for this.
Did you get this working @trohn_javolta !??!
That's exactly my problem !! I have two ShieldTV (2017 / 16GB / 8.0.1). Both successfully rooted with Magisk.
How can I give all my installed apps WRITE RIGHTS to my network drive (NAS)?!? Or even specific apps I CAN CHOOSE !!!
It is very annoying that eg RetroArch can not save the scores, savestats, controller settings, ...
Or even xFile Explorer can not write to the my NAS.
IMHO, as long as i am rootet, i should decide by my own how "secure" i want my system !!
Please help us to write on a network drive as normal.
On my Phone i can write to my NAS (ES File explorer) without any problems... So why is the shield not allowed?!
Thank you
Click to expand...
Click to collapse
Hi, yes I managed to do so Idk if I recall all required steps but I'll try. Let me know if it worked.
First in Magisk Manager Settings under "mount namespace" set "global namespace".
Then under Download, search and install the Busybox module and restart your shield.
Now open up a terminal, I prefer Termux. Type su, enter.
Now you create the folder where you'll mount your smb share to. Make sure it's in /mnt/cifs:
mkdir -p /mnt/cifs
mkdir -p /mnt/cifs/hdd
chmod -R 777 /mnt/cifs
mount -t cifs -o username=<username>,password=<pw>,rw,dir_mode=0777,file_mode=0666,iocharset=utf8,noperm,sec=ntlmssp,rsize=32768,wsize=32768 "//<ip>/<path to share>" /mnt/cifs/hdd
Since this has to be executed after every reboot, I set up a profile in Tasker App that does this automatically after a reboot. Hope this works for you :good:
trohn_javolta said:
Hi, yes I managed to do so Idk if I recall all required steps but I'll try. Let me know if it worked.
First in Magisk Manager Settings under "mount namespace" set "global namespace".
Then under Download, search and install the Busybox module and restart your shield.
Now open up a terminal, I prefer Termux. Type su, enter.
Now you create the folder where you'll mount your smb share to. Make sure it's in /mnt/cifs:
mkdir -p /mnt/cifs
mkdir -p /mnt/cifs/hdd
chmod -R 777 /mnt/cifs
mount -t cifs -o username=<username>,password=<pw>,rw,dir_mode=0777,file_mode=0666,iocharset=utf8,noperm,sec=ntlmssp,rsize=32768,wsize=32768 "//<ip>/<path to share>" /mnt/cifs/hdd
Since this has to be executed after every reboot, I set up a profile in Tasker App that does this automatically after a reboot. Hope this works for you :good:
Click to expand...
Click to collapse
WoW !! Thank you thausand times !!
I will give it a try at home later and report back
Kamikaze01 said:
WoW !! Thank you thausand times !!
I will give it a try at home later and report back
Click to expand...
Click to collapse
No problem, hope it works.
It's a shame that this still isn't possible without root on latest Shield Experience!
Btw: Are you on latest Shield Experience 8.0.1 (Android Pie) or did you also stay on 7.2.3?
trohn_javolta said:
No problem, hope it works.
It's a shame that this still isn't possible without root on latest Shield Experience!
Btw: Are you on latest Shield Experience 8.0.1 (Android Pie) or did you also stay on 7.2.3?
Click to expand...
Click to collapse
Many thanks for the help !! I am already at 8.0.1 ... Hopefully your workaround will still work: - /
Yes, it is really a shame for nvidia that it is still not possible to have write access to its own network drives.
Above all, this restriction is not widely publicized. I had to deal with it for a long time and I've been looking for the bug for a very long time ON MY SIDE, until I read on the Internet that this problem (write permission on network) is caused by the shield.
Anyway thank you very much for your tips - I'll try it that way and maybe later in the evening i can report.
Currently i am at work and come home later... :good:
Okay... I just tried your tips but got an error from Terminux, that my NAS is read only
So same problem as before... Damn.
Terminux output:
https://imgur.com/a/8gTQYWe
Kamikaze01 said:
Okay... I just tried your tips but got an error from Terminux, that my NAS is read only
So same problem as before... Damn.
Terminux output:
https://imgur.com/a/8gTQYWe
Click to expand...
Click to collapse
Hmmm.. and you did use username and password? Cause it's not in the command on the screenshot.
The message suggests that the share you're trying to mount is read only.
Hello and thanks for the answer.
I have entered the commands exactly as you told.
Terminux does not display the complete command, but I entered PW and USER correctly
I had to do it with controller, because I had no keyboard and mouse available. But i don't think i did any mistakes.
At the moment I use the app "FolderSync" and matched the required folder directly under the two shields.
That's an ugly workaround, but it works ...
Anyway, I thank you very much for the tips and the hint. I will try again with keyboard later maybe...
Still find it very sad from nVidia that they does not give us the freedom (write on NAS) on our own devices
Kamikaze01 said:
Hello and thanks for the answer.
I have entered the commands exactly as you told.
Terminux does not display the complete command, but I entered PW and USER correctly
I had to do it with controller, because I had no keyboard and mouse available. But i don't think i did any mistakes.
At the moment I use the app "FolderSync" and matched the required folder directly under the two shields.
That's an ugly workaround, but it works ...
Anyway, I thank you very much for the tips and the hint. I will try again with keyboard later maybe...
Still find it very sad from nVidia that they does not give us the freedom (write on NAS) on our own devices
Click to expand...
Click to collapse
Make sure to hit the "reply button" under my post, this way I get notified upon your answer :good:
Did you unmount the share via the offcial way before trying to mount in terminal? I mean go to settings -> storage and unmount the share there?
I'll take the leap shortly and will update to latest shield experience version...I just have to decide whether to wait for another update or not.
I'll report back but I see no reason why it shouldn't work on pie.
trohn_javolta said:
Make sure to hit the "reply button" under my post, this way I get notified upon your answer :good:
Did you unmount the share via the offcial way before trying to mount in terminal? I mean go to settings -> storage and unmount the share there?
I'll take the leap shortly and will update to latest shield experience version...I just have to decide whether to wait for another update or not.
I'll report back but I see no reason why it shouldn't work on pie.
Click to expand...
Click to collapse
Hello and thank u for your answer.
I tried again WITH keybord *g* and unmount my NAS before.
THIS time something seem to work, cause Terminux Output sais "Operation beeing performed..." (or beeing executed or something like this).
But another 2 hourl later nothing changed... i restart my shield but only the cifs folder disapeared.
No write access
Did you tried with Shield experience 8.0.1
Thank you
Kamikaze01 said:
Hello and thank u for your answer.
I tried again WITH keybord *g* and unmount my NAS before.
THIS time something seem to work, cause Terminux Output sais "Operation beeing performed..." (or beeing executed or something like this).
But another 2 hourl later nothing changed... i restart my shield but only the cifs folder disapeared.
No write access
Did you tried with Shield experience 8.0.1
Thank you
Click to expand...
Click to collapse
Hmm.. ok. It is expected behaviour that the cifs folder is gone after reboot, that's why I use Tasker to automatically create it and execute mount command after every reboot.
Is it possible that maybe Termux didn't get root rights? You can check that by opening Magisk Manager app and going to "Superuser" tab. There should be Termux entry and root rights enabled, if not do so and try again. I always go to the settings in Magisk Manager first and set "automatically grant root rights".
trohn_javolta said:
Hmm.. ok. It is expected behaviour that the cifs folder is gone after reboot, that's why I use Tasker to automatically create it and execute mount command after every reboot.
Is it possible that maybe Termux didn't get root rights? You can check that by opening Magisk Manager app and going to "Superuser" tab. There should be Termux entry and root rights enabled, if not do so and try again. I always go to the settings in Magisk Manager first and set "automatically grant root rights".
Click to expand...
Click to collapse
Yeah... I remember - you already told me about this problem at reboot.
Is it possible to get your Tasker Profile for that *g*
I know Tasker and already use it on my phone...
Kamikaze01 said:
Yeah... I remember - you already told me about this problem at reboot.
Is it possible to get your Tasker Profile for that *g*
I know Tasker and already use it on my phone...
Click to expand...
Click to collapse
It's a really simple one. As event I chose "booting device" and as task I use a simple execute shell task.
I did more digging and maybe can give more info. Just as a quick checklist:
You installed busybox magisk module? (maybe not required for mount command)
SE Linux mode is set to permissive? (maybe not required anymore, if successfull can be disabled later)
In Magisk Manager settings set "global mount namespace"?
By having magisk flashed, you should already get su and mount commands..
You can try changing the mount command a bit, I found sth. that might work:
su -mm -c mount -t cifs -o username=<username>,password=<pw>,rw,dir_mode=0777 ,file_mode=0666,iocharset=utf8,noperm,sec=ntlmssp, rsize=32768,wsize=32768 "//<ip>/<path to share>" /mnt/cifs/hdd
mm means mount master and should force everything to run in the global mount namespace (so the share can be accessed by every app with read/write permissions, not only with Termux)