Related
UPDATE: 4/30/11
Thumb KB 4.0, Beta 3.1 is now available at the following location: http://thumb4beta.blogspot.com/
If you have Thumb KB already installed from the Market, you must uninstall that version first before installing the new beta.
Some very nice changes so far....enjoy!
Thanks to Paul @ Beansoft for his very hard work on this new version!!
------------------------------------------------------------
Original Post:
I have been working with Paul, developer of the Thumb Keyboard (TKB) app, over the last couple of weeks to fine-tune the various layouts available on the TKB for the NookColor.
As of today, we tested the various layouts and they are working great! No longer does the bottom row disappear like it does with the current version available in the Market. A new version, with the new enhancements for the NC, should be available tomorrow.
This is great news, as this keyboard is incredibly easy, intuitive, and flexible to use on my NC. Appelflap is a very responsive dev and is doing a great job in supporting the NC community with these recent changes to his app.
A big thanks goes out to him for his patience with my testing and for a great app that makes typing on my NC so much better.
[My NC: Rooted, running v1.1.0r2 by Decad3nce, OC'd using 1.1Ghz OMAP3630 by Dalingrin]
I'm really looking forward to this, I have big fingers so I'm "all thumbs" to start with.
Went to market and picked it up but could not figure out how to enable it in the nook. Looks like an interesting concept. Will buy again but can you tell me how to activate it? Refunded until then.
DatterBoy said:
Went to market and picked it up but could not figure out how to enable it in the nook. Looks like an interesting concept. Will buy again but can you tell me how to activate it? Refunded until then.
Click to expand...
Click to collapse
I second that. I bought it too but have no clue how to get it to show up i the list of keyboards. I've done everything from renaming the zip to apk, renaming the latin ime and even copying the zip and the apk to system still to no avail. I see theres going to be an update tomorrow hopefully it fixes the the installation issue but if not can anyone who has gotten this to work please offer a solution.
kamillion said:
I second that. I bought it too but have no clue how to get it to show up i the list of keyboards. I've done everything from renaming the zip to apk, renaming the latin ime and even copying the zip and the apk to system still to no avail. I see theres going to be an update tomorrow hopefully it fixes the the installation issue but if not can anyone who has gotten this to work please offer a solution.
Click to expand...
Click to collapse
the apk that you have to move to system/app (as with other keyboards) is actually located in data/app-private. move that guy over and maybe change permissions. its been a while but i think thats how i got this working.
edit: after doing that, i also had to reinstall by clicking on the apk that i moved. it then showed up as a selectable keyboard.
DatterBoy said:
Went to market and picked it up but could not figure out how to enable it in the nook. Looks like an interesting concept. Will buy again but can you tell me how to activate it? Refunded until then.
Click to expand...
Click to collapse
This is what I did to finally get it working. It took me a very long time to get this keyboard recognized in the NookColor Tools as an optional keyboard, but here is what I did:
1) Backing up the Thumb KB on my Droid X using "My Backup Pro" app
2) Transferred the newly created backup from my DX to my NC
3) Used Root Explorer to go into the backup file and and copied the .apk to /System/App
4) From within Root Explorer, installed the .apk (I was already mounted as R/W)
I could just not get it installed from the Market, for whatever reason...even after copying the .apk from /Data/App-private to /System/App.
As a side note, it does seem like renaming the LatinIME.apk in /system/app was something I tried and worked, in addition to what I performed above. I have since renamed that file back and I still have the Thumb KB in my menu option.
Let me know if this works, realizing that backing up from another device may not be possible for everyone.
when you tried copying the apk from data/app-private, did you then install by clicking on the apk while it was in system/app? that was the key point for me.
Sent from my SCH-I500 using XDA App
jadambpharm said:
when you tried copying the apk from data/app-private, did you then install by clicking on the apk while it was in system/app? that was the key point for me.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
After copying the .apk to the /system/app folder, I did run the installer directly from within Root Explorer and this worked for me.
I was also helping the Dev out and testing this, and it works great. I did do a restart after I moved the .apk to the system/app folder. Using this keyboard makes a lot more sense for a tablet than the other keyboards. I can type faster now without having to put down the Nook, or feel like I going to drop it on accident.
Been looking forward to seeing the "not completely compatible with Nook" note go away. Thanks for the heads-up. =)
This worked for me
jadambpharm said:
the apk that you have to move to system/app (as with other keyboards) is actually located in data/app-private. move that guy over and maybe change permissions. its been a while but i think thats how i got this working.
edit: after doing that, i also had to reinstall by clicking on the apk that i moved. it then showed up as a selectable keyboard.
Click to expand...
Click to collapse
Thanks alot, your instructions worked flawlessly. Ive been trying to get this thing working for days.
problem parsing package
I downloaded thumb keyboard from the market and then moved the
com.beansoft.keyboardplus.apk
from data/app-private into /system/app (with root explorer)
In root explorer I tapped on the apk and hit install
then I got "problem parsing the package"
any help?
Saw this today. Looks like great minds think alike...
http://androidandme.com/2011/02/applications/swiftkey-bringing-tablet-keyboard-to-honeycomb/
problem parsing package - fixed
I don't know what happened but somehow I had my order cancelled (must have hit something somewhere along the line). I downloaded from the market again and it is working.
I've only trie dit for a few minutes but I think I am going to love it!
Exact same problem with parsing package. Looking forward to getting this working.
Sent from my LogicPD Zoom2 using XDA App
Same issues as above. Great idea though. Refunded until confirmed it can install from market with no tinckering.
Thanks 360Razir for helping me out by testing the keyboard on the NC!
For people with a parser error: do you rename the apk when copying it over? Renaming could be the source of the parsing problem.
Furthermore I turned off copy protection on the market. This should reduce the installation hassle a bit.
I'm planning to make a installer for (rooted) NCs. Can someone describe the exact steps that have to be taken to install TKB on a NC? That would be great (please use the non protected app on the market as the starting point of the description)
One minor issue I noticed; when using the 7" symbol/numeric keyboard in portrait, when I press the ., key, it enters a period in the text box as it should, but the key confirmation popup displays a 0 .
appelflap said:
Thanks 360Razir for helping me out by testing the keyboard on the NC!
For people with a parser error: do you rename the apk when copying it over? Renaming could be the source of the parsing problem.
Furthermore I turned off copy protection on the market. This should reduce the installation hassle a bit.
I'm planning to make a installer for (rooted) NCs. Can someone describe the exact steps that have to be taken to install TKB on a NC? That would be great (please use the non protected app on the market as the starting point of the description)
Click to expand...
Click to collapse
Thanks. I uninstaled and redownloaded from market. Copied the file over, installed from the new location, and am typing this with it now.
Sent from my nook color using XDA App
tj!2k7 said:
One minor issue I noticed; when using the 7" symbol/numeric keyboard in portrait, when I press the ., key, it enters a period in the text box as it should, but the key confirmation popup displays a 0 .
Click to expand...
Click to collapse
Thanks for noticing. Have to work a bit on the symbol keyboards anyway.
really dont have much time now, to show SS's or review the game play im in a hurry, but i build.prop edited to match my droid x.. runs so far
waited a long time 2 find nook wasnt compat... for long ^^
Thank you for tip, game works great!
np, was gunna post a link but i cant cuz im nooby ranked : /
youtu.be/s6nvV_t7cmI <--
If you could be more spacific, what build.prop options did you change and what to, thanks in advance
Sent from my Nook Color using Tapatalk
tsukisan said:
If you could be more spacific, what build.prop options did you change and what to, thanks in advance
Sent from my Nook Color using Tapatalk
Click to expand...
Click to collapse
Yeah, specifics would be nice. I have changed the build.prop to reflect a Droid X, and I still don't see it in the market. On my nook or my EVO.
1) Download ES File Explorer (Or any other root file editor)
2) In ES File Explorer, go into Setting > Root Settings and enable both check boxes
3) Navigate to /system/ and copy/paste build.prop to /sdcard/ (just in case)
4) Open & edit /system/build.prop
5) Change the following lines to make your phone think it is a Droid X
ro.product.model=Droid X
ro.product.manufacturer=Motorola
Save and overwrite.
Use Google to find the apk. Install and update.
Here's a small video that I did showing that it work.
youtube.com/watch?v=RoIck5AblkE
vi3tl0v3r said:
1) Download ES File Explorer (Or any other root file editor)
2) In ES File Explorer, go into Setting > Root Settings and enable both check boxes
3) Navigate to /system/ and copy/paste build.prop to /sdcard/ (just in case)
4) Open & edit /system/build.prop
5) Change the following lines to make your phone think it is a Droid X
ro.product.model=Droid X
ro.product.manufacturer=Motorola
Save and overwrite.
Click to expand...
Click to collapse
I know how to change my build.prop, but thanks .
vi3tl0v3r said:
Use Google to find the apk. Install and update.
Click to expand...
Click to collapse
That's the part I needed to see. So this requires a cracked apk to work?
vi3tl0v3r said:
1) Download ES File Explorer (Or any other root file editor)
2) In ES File Explorer, go into Setting > Root Settings and enable both check boxes
3) Navigate to /system/ and copy/paste build.prop to /sdcard/ (just in case)
4) Open & edit /system/build.prop
5) Change the following lines to make your phone think it is a Droid X
ro.product.model=Droid X
ro.product.manufacturer=Motorola
Save and overwrite.
Use Google to find the apk. Install and update.
Here's a small video that I did showing that it work.
youtube.com/watch?v=RoIck5AblkE
Click to expand...
Click to collapse
will this break netflix? and how would we update?
the game runs an update check at the beginning of running it, although i dont know when there actually is an update if it will just patch or make me reinstall a new apk.
got it working, fun game! and netflix still works
Just an fyi, quite a few devices work with this game, my Nook's build.prop is set to the Samsung Nexus S and both netflix and this game work fine.
Sent from my Nook Color using Tapatalk
works perfectly, thanks!!!
if you have SwypeBeta installed and change your nook's build.prop ID, it'll give you a snarky "this ain't licensed anymore" message, but it doesn't seem to have affected my NC at all...
johnnypollen said:
if you have SwypeBeta installed and change your nook's build.prop ID, it'll give you a snarky "this ain't licensed anymore" message, but it doesn't seem to have affected my NC at all...
Click to expand...
Click to collapse
It probably will. I think they have a time delay before it goes to "reduced functionality" which basically means you can no longer swype, only touch type.
Worked
Thanks for the tip, got it up and running and downloading the updates right now!
It was somewhat difficult to find a good link to the apk though, a lot of them have been removed or are broken, and I'd be afraid to repost the link where I found it for fear of that one being removed as well.
However, I really want to be able to support gameloft so they keep pumping out awesome games, but the only way to get this on the nook is to download the apk free. Is there a way to give to gameloft what they earned?
Got it up and running last week, but a new update was released that makes it unable to play. If anyone has a work around for this, That would be cool. It is an error after I log in that says to update before I can play. But I can't find any way to update the game manually, and I can't access it through the market....
Do a google search for the latest version by number and you will find a download link for the game.
For anyone editing the build.prop....
You DO NOT have to CHANGE the lines...
Just ADD the new info at the TOP of build.prop... it will use the first entry it finds... this makes undoing changes much easier...
You can also use my IMEI Generator to do these edits... since they have to be done every nightly update... just remember to edit the ini file in the Generator...
Thanks for the info!
Worked for me
Im currently in the market for a tablet that can at least run games of this nature, how exactly is the performance on the NC? Im debating on waiting for the Kindle Fire, but if this runs smooth on here, i can save a few $$ and get a refurbed NC on the cheap.
Thanks for the feedback!
myke66 said:
Im currently in the market for a tablet that can at least run games of this nature, how exactly is the performance on the NC? Im debating on waiting for the Kindle Fire, but if this runs smooth on here, i can save a few $$ and get a refurbed NC on the cheap.
Thanks for the feedback!
Click to expand...
Click to collapse
For me it runs pretty smooth, plus you can use chainfire3d app to make it smoother reducing graphics. I haven't tried with chainfire3d since for me it runs good as it is Haven't played it in a while I need to update to check if it still runs the same way.
Edit:
I modified this post because this has become more involved than simply the fb app. It has evolved more towards the build.prop file being modified.
Original post:
i tried to download the facebook app from the market, and it's not showing. so i did a titanium backup of it from my phone and installed it on the nt, initially i was able to open it and sign in. i went to a few posts, looked at a few friends, etc. after turning it off, it would force close each time i tried to reopen it. i dont know whats happening to make it force close. i presume since it's not showing in the market, it's communicating with facebook or the market and one or the other is telling it no.
is there anyway to tell the market this is another device so it will show other apps that are not available right now?
Go check out this thread:
http://forum.xda-developers.com/showthread.php?p=20422014
If this post helped click the thanks button!
jsp254 said:
i tried to download the facebook app from the market, and it's not showing. so i did a titanium backup of it from my phone and installed it on the nt, initially i was able to open it and sign in. i went to a few posts, looked at a few friends, etc. after turning it off, it would force close each time i tried to reopen it. i dont know whats happening to make it force close. i presume since it's not showing in the market, it's communicating with facebook or the market and one or the other is telling it no.
is there anyway to tell the market this is another device so it will show other apps that are not available right now?
Click to expand...
Click to collapse
Get your Facebook apk from this compressed file found in this post. Once you unpack/unzip it navigate to the extracted apps folder to find the facebook, Twitter etc. apk's
I'm going with dodgepot's method. I've noticed other apps were not available since posting this. This method should clear it up. It will be late tonight before I'll get a chance but I'll let you guys know the results.
Sent from my PG06100 using xda premium
Honestly the facebook app is not that good any version, its better if you access it by browser just bookmark the page.
~Veronica
Oppinions vary on the fb app. I like it personally. I did get it to work however. I installed the updated app just fine from a backup of my evo shift. However... I tried the build.prop mod. Nogo. I tried the nexus s and the .... crap.. drawn a blank here... the second mod listed in the linked page. Neither worked. Anyone with experience modding the build.prop file, I have a few questions. In the original file there are more of the ro. fields listed than what are shown on each of the mods. Do these other original lines have to remain in place or should they be deleted? Some of them look to me as if they would conflict with the new lines. Also, what's the endresult of a screwed up build.prop file? Does something other than market rely on this file? If its geeked up, will I brick or have to re-root? Also, I presume this file is something that comes with the 1.4.0 rom. Is this something that could/should be replaced when the root process is taking place to prepare the device for the market? I guess when cm roms, etc. come out they will have there own build.prop that will define the device as something else to the market so more apps are available since google doesn't recognize the nt as a "market" device?
Sent from my PG06100 using xda premium
jsp254 said:
Oppinions vary on the fb app. I like it personally. I did get it to work however. I installed the updated app just fine from a backup of my evo shift. However... I tried the build.prop mod. Nogo. I tried the nexus s and the .... crap.. drawn a blank here... the second mod listed in the linked page. Neither worked. Anyone with experience modding the build.prop file, I have a few questions. In the original file there are more of the ro. fields listed than what are shown on each of the mods. Do these other original lines have to remain in place or should they be deleted? Some of them look to me as if they would conflict with the new lines. Also, what's the endresult of a screwed up build.prop file? Does something other than market rely on this file? If its geeked up, will I brick or have to re-root? Also, I presume this file is something that comes with the 1.4.0 rom. Is this something that could/should be replaced when the root process is taking place to prepare the device for the market? I guess when cm roms, etc. come out they will have there own build.prop that will define the device as something else to the market so more apps are available since google doesn't recognize the nt as a "market" device?
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Do not remove7touch the other .ro's of build.prop just change the lines provided. The end result with a screwed up build.prop basically will be that your device won't be recognized by market and certain apps if not all, for ex. airdroid when i login in my browser to access my nook it recognize it as Droid3 because i changed my build.prop to Droid3. You won't brick or have to re-root your device if you mess up with it, by using adb push of the original build.prop is enough. Build.prop can be changed to a modified one before root i did it and worked like a charm.
~ Veronica
How To Get 50 GB of Free Space on Box.Com?
======================== Removed ============================
Let me know if it still working...!!!
alexlinggo said:
[*]Download this App and install it on your Android device (no special instructions for installing this app, you just need to do it like you install any other application).
Click to expand...
Click to collapse
What does that app do?
P.S. On their site, Box states the following:
If you already have an older version of the Box app on your device, you just need to sign into your account on your device and the upgrade should be complete.
Click to expand...
Click to collapse
I myself have just created an account but at first login it's 5GB. And the second. Damn :-/ (using it on my MB526)
*EDIT* Okay, I figured out that this promotion is for LG only, so I got your app and got my free 50GB! I hope your promise is true, though.
Cheers!
thanks dude. it works.
For everyone: do as the steps say. im enjoying my 50GB!!
thanks it works great. now Im enjoying my 50GB
Or just rename your device in build.prop to VS910 4G and LG as manufacter....
niksy+ said:
What does that app do?
P.S. On their site, Box states the following:
I myself have just created an account but at first login it's 5GB. And the second. Damn :-/ (using it on my MB526)
*EDIT* Okay, I figured out that this promotion is for LG only, so I got your app and got my free 50GB! I hope your promise is true, though.
Cheers!
Click to expand...
Click to collapse
Sorry dude... I don't know what the app doing to get 50 GB, i just find it from other site and share it here...
If you doubt to use this app, check your account in https://www.box.com/ via browser....or make other email to make your primary email safe....
Thank's in advice....
works great thankssss
heartreaper said:
thanks dude. it works.
For everyone: do as the steps say. im enjoying my 50GB!!
Click to expand...
Click to collapse
kuca93 said:
thanks it works great. now Im enjoying my 50GB
Click to expand...
Click to collapse
baronsamedi said:
works great thankssss
Click to expand...
Click to collapse
Thank's for report guys....
thanks . it works.
mihovil13 said:
Or just rename your device in build.prop to VS910 4G and LG as manufacter....
Click to expand...
Click to collapse
I think you have to set the manufacturer to "LGE", not "LG". Here's a quick tutorial:
First, install the Box app from the Market and create a free account. (You'll get 5 GB of free space already.)
Next, find the build.prop file on your phone's internal memory. (On some ROMs, it may be in the root directory; for me, it was in the "system" folder). Copy the file to your SD card and also make an extra copy of it for backup. Long-press one of those copies and select "Open As," choose "Text," and open it. Look for the line that says
ro.product.manufacturer=Motorola
and change it to
ro.product.manufacturer=LGE
Also find the line that says
ro.product.model=MB525
and change it to
ro.product.model=VS910 4G
Save the edited file, then use a root-enabled file explorer (like ES File Explorer) to copy your edited "build.prop" file from your SD card and paste it back where you got it in the system folder of the phone's internal memory, overwriting the original file. Then reboot the phone, log into your Box app again, and you should see a message saying you've been upgraded to a 50GB account.
Then copy the backed-up (non-edited) version of your build.prop file and paste it back in the system folder (the same way you did with the edited version), and reboot the phone again. Your phone is now back to normal (and all your apps, etc. will correctly recognize it as a Motorola DEFY), but you'll still have your 50GB of free space!
Thanks. It's work.
Sent from my MB525 using XDA App
OK, someone please enlighten me: is this service for file sharing or file stealing? How do they guard against copyrighted material being "exchanged"?
OK, I called Box and spoke with customer service and they claim they are not just another version of MegaUpload but have, apparently, 100% zero checks in place to prevent IP theft. They said, however, they are going to "shoot my question upstairs" and get back to me.
tHANK YOU!
nice
Nice one thanks for the heads up
that's cool, working and its great
thanks
Still works.
Got a Headache? It's all in your Head.
thanks, i signed for that account and got 50Gb, but soon deleted it because i liked more minus, i liked it more i dont have as many limits as in box.com
I use box its cool
Sent from my MB525 using xda premium
Well, since it was a promotion from Box (install their app within a certain period and get automatically 50GBs for life) I made an account too. The good news is that Titanium Backup Pro got updated a few days ago with support for Box syncing (so those 50GBs make sense now, despite the user being limited to max. 100MB files).
Not really a problem
Sent from my MB525 using xda premium
Since the Note 3 is new, and so far, there is only one custom Rom, I've seen the "how do I disable camera sounds" question asked a few times.
I'm sure your favorite developer will incorporate this feature, into future Roms, like they have in the past, for previous devices. This is mainly for us impatient noobs.
You must be rooted. Using a root explorer, navigate to /system/csc. Backup your feature.xml. Navigate to /system/csc/SPR/system/csc. Copy feature.xml. Navigate back to /system/csc. Paste the new file, over writing the old one. Open the new feature.xml, scroll to the camera section, and change:
<CscFeature_Camera_ShutterSoundMenu>false</
CscFeature_Camera_ShutterSoundMenu>
to:
<CscFeature_Camera_ShutterSoundMenu>true</
CscFeature_Camera_ShutterSoundMenu>
Save, exit,
Set permissions to rw-r--r--
Reboot
Note: I used 'Root Explorer'. ES File Explorer may also work.
Here is a list of potential csc parameters, gathered from other phones. I didn't create this list. I found it about a year ago, and thought it might be interesting, to play around with.
Edit: the text file came from @kkoolpatz
http://forum.xda-developers.com/showthread.php?t=2033894
I followed this exactly I'm still not getting that option to silence the shutter. Is there a detail you left out or am I just missing something? I tried twice
Sent from my SM-N900P using XDA Premium 4 mobile app
SantinoInc said:
I followed this exactly I'm still not getting that option to silence the shutter. Is there a detail you left out or am I just missing something? I tried twice
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I edited the OP, to make it clearer, and modified the method, slightly.
One other possibility. Backup your feature.xml. Navigate to /system/csc/SPR/system/csc. Copy feature.xml. Navigate back to /system/csc. Paste the new file, over writing the old one. Open the new feature.xml, and change:
<CscFeature_Camera_ShutterSoundMenu>false</
CscFeature_Camera_ShutterSoundMenu>
to:
<CscFeature_Camera_ShutterSoundMenu>true</
CscFeature_Camera_ShutterSoundMenu>
(You're changing 'false' to 'true,)
Save, exit,
Set permissions to rw-r--r--
Reboot
Very useful. Thank you.
Thanks for the clarification in the OP. I now got it to work. Problem I had before was that I did not realize that I was simply changing false to true. Super simple.
Sent from my SM-N900P using XDA Premium 4 mobile app
12MaNy said:
Very useful. Thank you.
Click to expand...
Click to collapse
I'm glad it worked for you. Thanks for the feedback.
SantinoInc said:
Thanks for the clarification in the OP. I now got it to work. Problem I had before was that I did not realize that I was simply changing false to true. Super simple.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Great! It's good to hear that the instructions where clear enough to be followed. There's a lot more that can be enabled, such as using the camera during calls. It's the same principle, just a matter of searching through the feature.xml, and flipping or changing the variables.
Something to add to the first post. Make a backup of the original in case you ever screw up.
Compusmurf said:
Something to add to the first post. Make a backup of the original in case you ever screw up.
Click to expand...
Click to collapse
Always good advice, but it's already there. Unless you're talking about a nandroid...
Must have missed it. I was going to post the same thing since that was one of the first things I did when rooted but never got around to it. Glad someone posted it for others. Always good to share info. However you should have done it in the DEV section with a [MOD] Tag. Post some of the other tweaks too. It'll disappear here in General.
Compusmurf said:
Must have missed it. I was going to post the same thing since that was one of the first things I did when rooted but never got around to it. Glad someone posted it for others. Always good to share info. However you should have done it in the DEV section with a [MOD] Tag. Post some of the other tweaks too. It'll disappear here in General.
Click to expand...
Click to collapse
Yeah, maybe so. I went back and forth in my mind, and decided that this really isn't development, so here we are in 'General'.
I had a bunch of these edits, when I had my Note 2. I'll have to dig through, and see what additional features we can enable on the Note 3. Any help is definitely appreciated.
Geez, i wonder why Sprint wont include this option by default. On the at&t Note 3, the option to silence is already baked in.
optimummind said:
Geez, i wonder why Sprint wont include this option by default. On the at&t Note 3, the option to silence is already baked in.
Click to expand...
Click to collapse
Sprint can't afford a lawsuit when some idiot takes a silent upskirt photo and someone decides to sue them for not having it make noise.
I'm on stock rooted and es explorer gives me a permission denied error when I try to overwrite features.xml from the SPR folder to system/csc, also unable to rename or edit directly from system/csc but I can copy and paste elsewhere to back up.
Tavo_7 said:
I'm on stock rooted and es explorer gives me a permission denied error when I try to overwrite features.xml from the SPR folder to system/csc, also unable to rename or edit directly from system/csc but I can copy and paste elsewhere to back up.
Click to expand...
Click to collapse
Open ES File Explorer and tap the phone menu button. A pane should open on the left side of the screen. Scroll to the bottom, and turn "Root Explorer" on. When the Super User prompt pops up, be sure to allow it.
Root explorer was already on, but I toogled on off just in case and it still fails. See screenshots
Tavo_7 said:
Root explorer was already on, but I toogled on off just in case and it still fails. See screenshots
Click to expand...
Click to collapse
I'm not sure what the problem is. ES File had some problems with root, about a year ago, but I thought they got that fixed. I use it everyday, but not the root functions. Maybe you can try going into SuperSU, selecting ES File, and tapping "forget", then go back into ES, and accept the SU prompt.
LMMT said:
I'm not sure what the problem is. ES File had some problems with root, about a year ago, but I thought they got that fixed. I use it everyday, but not the root functions. Maybe you can try going into SuperSU, selecting ES File, and tapping "forget", then go back into ES, and accept the SU prompt.
Click to expand...
Click to collapse
Still failing after forgetting, I also reinstalled both ES and SU and no good. Any other free root explorers I can test? Or can anyone else using es verify if it's working for them?
Tavo_7 said:
Still failing after forgetting, I also reinstalled both ES and SU and no good. Any other free root explorers I can test? Or can anyone else using es verify if it's working for them?
Click to expand...
Click to collapse
There are several free in the Play Store. Maybe try a few?
LMMT said:
There are several free in the Play Store. Maybe try a few?
Click to expand...
Click to collapse
I downloaded 'Root Browser' from the play store and this did the trick, ES Explorer is having root issues with the Note 3, well at least on my phone since no one else confirmed. I added the shutter menu (working) , enabled camera during calls (working), and tried to add a call button from the logs list but this didn't appear to work.
Thanks again!
Tavo_7 said:
I downloaded 'Root Browser' from the play store and this did the trick, ES Explorer is having root issues with the Note 3, well at least on my phone since no one else confirmed. I added the shutter menu (working) , enabled camera during calls (working), and tried to add a call button from the logs list but this didn't appear to work.
Thanks again!
Click to expand...
Click to collapse
Good. I'm glad you got it working.