Related
I have the tablet version .apk installed that was posted in the collection of Transformer apps, I think in the Xoom forum. Anyways, it opens fine before it force closes, but when I try to open my resume it crashes. I tried installing it outright and also putting in system/app. Both ways give the same results, it opens then crashes when opening a file. I cleared the data, reset the device, nothing.
jkuhna3449 said:
I have the tablet version .apk installed that was posted in the collection of Transformer apps, I think in the Xoom forum. Anyways, it opens fine before it force closes, but when I try to open my resume it crashes. I tried installing it outright and also putting in system/app. Both ways give the same results, it opens then crashes when opening a file. I cleared the data, reset the device, nothing.
Click to expand...
Click to collapse
Did you check the apk details to see if there's some sort of license/drm check?
Many apps and games are now coming with a license check, just like computer software to make certain people aren't pirating them. Something could be checking for a serial number.
I don't know if that's a paid version too. If so, I'm pretty sure discussing pirated apps is against ToS. If it's a freely available thing then, no worries. I'm waiting, maybe forever for a LibreOffice port to Android. Probably be a long while, dunno how well Dalvik and something that big would play together.
muqali said:
I don't know if that's a paid version too. If so, I'm pretty sure discussing pirated apps is against ToS. If it's a freely available thing then, no worries. I'm waiting, maybe forever for a LibreOffice port to Android. Probably be a long while, dunno how well Dalvik and something that big would play together.
Click to expand...
Click to collapse
That's true, it may be a paid app. If so I'm not trying to do anything that's frowned upon here. I do know that the app isn't available in the market yet. I think I'm gonna put this off for a while and see what happens with the official release because it's obviously not working right now.
From what little I can learn Polaris Office comes preiinstalled on the Transformer tablet only. I found advice that I needed to move two lib files over to system/lib to make it work. Well I only found one lib file, copied to system/lib and still crashes. I can get it display some stuff but it won't let me start a new doc or read an exist in doc. There are some nice YouTube videos showing how it works, and it looks real nice. I hope some can figure it out.
Look at this post. http://forum.xda-developers.com/showthread.php?t=1114100
The two files are libpolarisoffice_Clipboard.so and libpolarisoffice.so. It works fine for me without any FCs.
Yep, It Works For Me Too..
but you have to push the two lib files to system/lib using ADB (or Root Explorer)
Thanks for the names of the two file...it works! I am amazed at how this info is found and shared
bpivk said:
Look at this post. http://forum.xda-developers.com/showthread.php?t=1114100
The two files are libpolarisoffice_Clipboard.so and libpolarisoffice.so. It works fine for me without any FCs.
Click to expand...
Click to collapse
Perfect, thank you. I knew there had to be a way.
However (you just knew there was going to be a however!), Polaris Office loads OK, but many of the functions don't work. For example I am able to type in text for a new document but very few of the tools at the top work and I can't highlight any portions of the text. There must still be something missing to make it work correctly. When I do a check for updates within the program it says I am up to date. Any one else seeing these problems?
daveheine said:
However (you just knew there was going to be a however!), Polaris Office loads OK, but many of the functions don't work. For example I am able to type in text for a new document but very few of the tools at the top work and I can't highlight any portions of the text. There must still be something missing to make it work correctly. When I do a check for updates within the program it says I am up to date. Any one else seeing these problems?
Click to expand...
Click to collapse
Seems to be OK for me, I've had it running for nearly 2 weeks now. What functions specifically aren't working for you? I'll try them on mine...
I found a couple of YouTube videos by andyxover that I was able to try out. I could do all of his examples.
The problems/limitations that jumped out at me were
(1) you can not move pictures around in a document (MS Word limits you also)
(2) in spreadsheets you have to type in the blind when you are making enties into boxes
I need to ply around more to get a better feel for this UI.
daveheine said:
I found a couple of YouTube videos by andyxover that I was able to try out. I could do all of his examples.
The problems/limitations that jumped out at me were
(1) you can not move pictures around in a document (MS Word limits you also)
(2) in spreadsheets you have to type in the blind when you are making enties into boxes
I need to ply around more to get a better feel for this UI.
Click to expand...
Click to collapse
1. Yes you can. Single tap on the image and it will select.. Then you can move it where you want within reason.
2. There is no "in cell" editing. Editing is in the text box at the top of the screen.
bpivk said:
Look at this post. http://forum.xda-developers.com/showthread.php?t=1114100
The two files are libpolarisoffice_Clipboard.so and libpolarisoffice.so. It works fine for me without any FCs.
Click to expand...
Click to collapse
Hello, I was readig your posts looking for help and maybe you can help me, as I can see you solved the problem.
I have an Acer Iconia A500 w/Honeycomb and tryed to install Polaris Office.
I donwloaded the P.O. files and read the txt file: (Using root explorer or adb, push the two lib files to system/lib.).
Downloaded and install rootexplorer, copy to pen drive "lib files", opened rootexplorer, copied lib files then went to System File, opened lib file, did hit paste and a warning message says this file is reading only.
I began to investigate and found that needed to root the device, I did it and tested with root checker, it said it was rooted succesfully, and then repited the hole process, again, read only file.
I was reading posts and found that what I think is the problem, "Fix permissions", so it let me paste the 2 lib files. But still havent found the answer to this. Is there a step I missed? or I'm just doing it all wrong?
I thought if I could find the way to solve the "fix permissions" problem and could paste the 2 lib files in System/lib folder it would be the solution, but can´t paste the 2 files. What should I do?
Thanks in advance for reading and helping me.
It's kind of funny.
You've missed an option in Rootexplorer. It has a button on the top corner that says "Mount R/W" press it and copy the files. You have an old version of rootexplorer if it doesn't have that option.
Ok, here goes:
OPEN Rootexplorer,
top right is the Remount as R/W button, click on it and it changes to Remount R/O
found MNT folder and click, foun usb_storage folder and click,
found the folder I made with 2 lib files and click,
Multiselect and mark: libpolarisoffice.so and libpolarisoffice_Clipboard.so files and Copy
Back to System folder and then to lib folder, click PASTE and " You cannot paste here because the file system is read-only.
What happen??? What am I doing wrong?
aero2much said:
Ok, here goes:
OPEN Rootexplorer,
top right is the Remount as R/W button, click on it and it changes to Remount R/O
found MNT folder and click, foun usb_storage folder and click,
found the folder I made with 2 lib files and click,
Multiselect and mark: libpolarisoffice.so and libpolarisoffice_Clipboard.so files and Copy
Back to System folder and then to lib folder, click PASTE and " You cannot paste here because the file system is read-only.
What happen??? What am I doing wrong?
Click to expand...
Click to collapse
By the way, the 2 lib files have an icon in golden color with a star i brown color, would it mean something?
aero2much said:
By the way, the 2 lib files have an icon in golden color with a star i brown color, would it mean something?
Click to expand...
Click to collapse
Opened the system file folder, found the lib file folder, opened and tried to paste:
the same answer "You cannot paste here because the system file is read-only"
But I noticed something, when I click R/W it changes to R/O, when I open system folder to Paste the Remount automaticaly changes to R/W again after it was R/O, I don´t know if it something important to this case, afted denied access I cilk the remount button again, just to see if it changes to R/O, but it doesn´t.
I usually just copy the files and then press the r/w button and paste. I don't leave the folders. You shouldn't have problems if you're rooted.
bpivk said:
I usually just copy the files and then press the r/w button and paste. I don't leave the folders. You shouldn't have problems if you're rooted.
Click to expand...
Click to collapse
Just double check with rootchecker and it says I have root access.
I don't know! Maybe is not for me this time.
Thanks a lot for your time
[TIP/TRICK] Stop Stock Gallery From Creating .thumbnails Folder! Save SD Card Space!
First off, I'll start by saying: "I am not responsible if you brick your phone! Always make a nandroid backup before using my steps/messing with Autostarts! (It's a very powerful application!)"
If you use a 3rd party gallery app (Like QuickPic, my personal favorite...) - You are probably tired of wasting over 100mb of space on your SD card... (And waiting a long time for booting up as well...) I had no need for the /sdcard/DCIM/.thumbnails folder taking up space on my SD card, so this is how to disable the stock Gallery app from doing so!
I researched a little on how to accomplish this and came up with little information, so I thought I'd share:
What you'll need:
1.) Autostarts app (I used: Version 1.7.0)
---
Steps/Directions:
1.) Run Autostarts
2.) Look for these entries: Media ejecting/mounted
3.) Choose either entry (ONLY CHOOSE ONE, IT DOES NOT MATTER WHICH! Choosing one entry will disable both entries in Media ejecting AND Media mounted!)
4.) Click on BootReceiver
5.) Choose Disable (A popup will show saying "This is a system app, are you sure? etc.)
6.) Done! Reboot. On boot, go to /sdcard/DCIM/ and look inside for the usual .thumbnails folder, it should be contained with a few (SMALL) files now!
Note: (Make sure you disable the entry BootReceiver ONCE, it should "strikeout" (as in: draw a line through) the entry BootReceiver, to show it has been disabled on boot.) - zmag
Hmm, seems I just looked in my folder and I saw the darn .thumbnails file again... If anyone knows how to disable the stock Gallery app from wasting boot time & sd space; PLEASE TELL ME!!! - zmag
Well, it looks like this is not a big issue for anyone out there - but it still annoys me.
I have since "frozen" the stock Camera and Gallery apps with Titanium Backup Pro, and still; no luck.
Now, granted when I reboot my phone and look in my DCIM folder it doesn't seem to be creating the .thumbnails folder 100% of the time. But the folder is still being created somehow, and my only guess is from a third-party app (and I can't seem to pinpoint which one) but I'm gonna test to find out which and post my results...
I wish someone out there could give me some input, I've been talking to myself here for too long. - zmag
This isn't the same, but you can create a filetype named '.nomedia' and place it at the root of the folder where you want and it will stop displaying the thumbnails in the gallery app.
http://smartadopter.wordpress.com/2...mbnails-showing-in-the-android-photo-gallery/
OK I believe I may have found the possible solution to this problem.
I was searching around on how to fix this problem as well, and tried a few things myself and believe I have found a solution, so I had to sign up for xda to share with everyone else. So please be gentle as this is my first post, although im a long time lurker.
I also got rid of the stock gallery (uninstalled with Titanium Backup) and now use Quick Pic. although I have removed the stock gallery it still builds that 60mb+ thumbnails directory on my SDcard. I was using SD Maid to delete it but it gets annoying that it kept reappearing even after the uninstall of stock gallery.
Now to start fixing,
I realized it was actually a large single file itself named ".thumbdata3-1967290299" in "sdcard/DCIM/.thumbnails/" that was taking up the 60mb+ , the smaller individual thumbnails Quick Pic created only added up to a 1mb or so.
So what I did was I just grabbed a random useless file from my SD card I didn't need anymore (an alarm clock plus backup .bak file, but I would assume the *new file" option in root explorer would do the same) and I renamed the unneeded file the same name as the file in /.thumbdata/ (the the .thumbdata3-19672902099).
Now I had a .thumbdata file that was only 1.75kb and just simply moved it to the sdcard/DCIM/.thumbnails/ folder and replaced the 60mb .thumbdata file with the smaller one.
After a few restarts of my phone, opening and browsing Quick Pic, checking my thumbnail size a few times with both SD Maid and Root Explore - I now have a much smaller 1.75kb file instead of the old 60mb file.
Hopefully this well help some of you out and solve your problem as well, as far as I can tell it is no longer making that thumbnail file expand so large on my phone.
Phone: HTC Hero CDMA
ROM: Cyanogenmod 7.1
Carrier: i-wireless/sprint
hewillmakehell said:
OK I believe I may have found the possible solution to this problem.
Click to expand...
Click to collapse
i've tried both your copied file trick and making a new file with root explorer, both to no avail. ".thumbdata3--1967290299" always reverts to its old size if any app associated with the gallery is opened.
has yours really stopped reappearing?
i can't figure out where the large thumbnail data is stored, but it must be in the system somewhere...
problem solved
hey i figured out how to fixed this on my atrix. should be the same for all android phones.
http://forum.xda-developers.com/showthread.php?p=28447099#post28447099
There's no "external.db" inside my "com.android.providers.media" folder.
However, I didn't even understood what I was supposed to do with this file. What he meant with "trim the thumbnails table with an sql editor"?
I quoted the post you linked below:
i found the place where the thumbnail data is stored, which was making the huge thumbnail file and crashing Entertainment Center.
it isn't storing the entire ".thumbdata3--1967290299" file (which can be hundreds of mb for some people), rather a large (tens of mb) .db database file that is being used to recreate it on demand.
/data/data/com.android.providers.media/databases
external.db
with Root Explorer i could view the file, and Speed Software also sells an sql editor which you can use to trim the thumbnails table.
*be careful: deleting entries from this file also seems to delete it from the device! i deleted all records from the thumbnails and images tables..
learn from my mistake. i thought it would regenerate, but it deleted all images from /sd card. good thing i backed up all my photos first, but better to use the filter option and trim out only the records for files that are no longer on the device.
".thumbdata3--1967290299" now reappears, but a whole lot smaller.
Gallery opens so much faster now, and Entertainment Center works again!
hope it helps!
Click to expand...
Click to collapse
i bet it is hiding somewhere. maybe it's slightly different on other phones.
the issue was that i had an ever-expanding sdcard/dcim/.thumbnails/.thumbdata3--1967290299 file being recreated every time i accessed the gallery viewer, even after that thumbnails folder was erased.
my device was keeping track of ALL the media files that were ever on it, not just the ones presently on it. so the more files that passed through my device, the bigger the thumbdata file kept getting. the external.db file contains a table that lists all media files along with a bunch of attributes for each. apparently this db file is used to generate the thumbdata file. all the info for deleted files just leads to more padding inside the thumbdata file, so it keeps getting bigger.
by trimming the table i meant to delete the records in the external.db that correspond to thumbnails for media no longer on the device. that file is an SQLite file, so to open it you need a special viewer/editor. i first used the SQLite Viewer that comes with Root Explorer. with that, i could see the all the redundant thumbnail entries. to edit it, i got the SQLite Editor, though i'm sure there are other ways. then it's a matter of recognizing which files it lists that are no longer on your device, and getting rid of those rows from the table. in my case the external.db file went down from 8mb to 500kb after i did that.
screenshot 1 showing tables inside external.db, using SQLite Editor
screenshot 2 showing 'thumbnails' table
TBN FILE 2gb
hi
i have a huge thumbnail file in he sd card its almots 2GB
i have already came to opeing the list for thumbnails in the editor
but i dont know how to filter it that i can delete only the files which are not in the sd card (i.e already deleted ) plss guide me throught ,,, this and u will be a star:good:
whitebreadstyle said:
i bet it is hiding somewhere. maybe it's slightly different on other phones.
the issue was that i had an ever-expanding sdcard/dcim/.thumbnails/.thumbdata3--1967290299 file being recreated every time i accessed the gallery viewer, even after that thumbnails folder was erased.
my device was keeping track of ALL the media files that were ever on it, not just the ones presently on it. so the more files that passed through my device, the bigger the thumbdata file kept getting. the external.db file contains a table that lists all media files along with a bunch of attributes for each. apparently this db file is used to generate the thumbdata file. all the info for deleted files just leads to more padding inside the thumbdata file, so it keeps getting bigger.
by trimming the table i meant to delete the records in the external.db that correspond to thumbnails for media no longer on the device. that file is an SQLite file, so to open it you need a special viewer/editor. i first used the SQLite Viewer that comes with Root Explorer. with that, i could see the all the redundant thumbnail entries. to edit it, i got the SQLite Editor, though i'm sure there are other ways. then it's a matter of recognizing which files it lists that are no longer on your device, and getting rid of those rows from the table. in my case the external.db file went down from 8mb to 500kb after i did that.
screenshot 1 showing tables inside external.db, using SQLite Editor
screenshot 2 showing 'thumbnails' table
Click to expand...
Click to collapse
I had the sam issue, but unfortunately your solution didn't help me. I have only a couple of pictures on my phone, but a lot of GBs of music on SDCard and I think this is he reason why .thumbdata3 file is so large on my phone.
I also tried using SDRescan as proposed here: http://forum.xda-developers.com/showpost.php?p=28516079&postcount=6, but that didn't help either.
I've done some more research and found a solution here: http://www.mobilephonetalk.com/show...in-memory-card&p=311954&viewfull=1#post311954. After I deleted the .thumbdata3 file, created a blank one with Root Explorer and removed write permission to it, the file stays at 0 bytes and Camera and Gallery apps still work fine.
mihir880 said:
hi
i have a huge thumbnail file in he sd card its almots 2GB
i have already came to opeing the list for thumbnails in the editor
but i dont know how to filter it that i can delete only the files which are not in the sd card (i.e already deleted ) plss guide me throught ,,, this and u will be a star:good:
Click to expand...
Click to collapse
it sure would be nice if android did that automatically
i don't know how though, sorry.. maybe there is a way, but it is surely safer to backup the media files to another drive, trim the db, then move them back if necessary.
---------- Post added at 09:47 PM ---------- Previous post was at 09:42 PM ----------
strom87 said:
I've done some more research and found a solution here: http://www.mobilephonetalk.com/show...in-memory-card&p=311954&viewfull=1#post311954. After I deleted the .thumbdata3 file, created a blank one with Root Explorer and removed write permission to it, the file stays at 0 bytes and Camera and Gallery apps still work fine.
Click to expand...
Click to collapse
i guess that's one way of doing it. it just means all the thumbnails have to be recreated every time you open the gallery or file browser.
strom87 said:
I had the sam issue, but unfortunately your solution didn't help me. I have only a couple of pictures on my phone, but a lot of GBs of music on SDCard and I think this is he reason why .thumbdata3 file is so large on my phone.
I also tried using SDRescan as proposed here: http://forum.xda-developers.com/showpost.php?p=28516079&postcount=6, but that didn't help either.
I've done some more research and found a solution here: http://www.mobilephonetalk.com/show...in-memory-card&p=311954&viewfull=1#post311954. After I deleted the .thumbdata3 file, created a blank one with Root Explorer and removed write permission to it, the file stays at 0 bytes and Camera and Gallery apps still work fine.
Click to expand...
Click to collapse
How did you removed write permission from the thumbdata3 file with RootExplorer. If I try this, then I get a message, that that is not possible on the SD-Card and nothing happens!! The permissions stay !!!
Sunnymen1975 said:
How did you removed write permission from the thumbdata3 file with RootExplorer. If I try this, then I get a message, that that is not possible on the SD-Card and nothing happens!! The permissions stay !!!
Click to expand...
Click to collapse
You can try creating a folder instead of a file(no need to set permissions). So far, it's working
lbrfabio said:
You can try creating a folder instead of a file(no need to set permissions). So far, it's working
Click to expand...
Click to collapse
Another quick way that seems to work:
Code:
rm -rf /mnt/sdcard/DCIM/.thumbnails && touch /mnt/sdcard/DCIM/.thumbnails
rm -rf /mnt/sdcard/external_sd/DCIM/.thumbnails && touch /mnt/sdcard/external_sd/DCIM/.thumbnails
Hello, I also have this problem. Now I put another file with that name and that seems to work.
However, I came on this because my device went suddenly very slow.
Is it possible that the application that writes these .thumbnail files is still searching through the complete device, even when it cannot update the file?
And, how can I inspect what app is causing this file or slow down?
Fixed!... deleted .thumbnails folder and then created a file called .thumbnails using root explorer....thats worked for me in my THL w1..saved 1.2 gb of space!
Is there anyway to stop the stock camera from posting pics in the DCIM folder? I am somewhat ocd and would like them to be posted in a folder of my choosing.
estranged1977 said:
Fixed!... deleted .thumbnails folder and then created a file called .thumbnails using root explorer....thats worked for me in my THL w1..saved 1.2 gb of space!
Click to expand...
Click to collapse
Created a file or a folder?
petrsiri said:
Created a file or a folder?
Click to expand...
Click to collapse
try create folder (I do this and see no more thumbdata3-files yet two months)
I am really pissed about this one.. tried to make a Titanium Backup of my stuff before I unrooted and wiped the phone to ODIN the ANE update (it refused to update after being towelrooted).. So that was my first introduction to the bug that prevents TiBu from writing to the extSD.. I found several threads pointing to adding a line to the profiles.xml file in system/etc/permissions. Well I added the line using ES3 note editor (copied the original file to .bak first), saved and rebooted, and as soon as I unlocked the phone, the toasts started popping up that nearly everything was crashing - repeatedly. I went and deleted the modified file and changed the .bak back to normal, but it did not fix it. No apps would open, and I had no data connection (neither Wifi or 3G). The only thing that fixed it was booting into recovery and wiping it.
And then it happened AGAIN when I tried it again (after the ANE update was flashed via ODIN, so I know it was clean). So WTF is happening, and why does restoring the original file not fix it??
At this point I can't even get TiBu to back up to the internal storage.
Taz420nj said:
I am really pissed about this one..
Click to expand...
Click to collapse
There is no obvious reason why it shouldn't work of you reverted the changes. But of course that is the ultimate value of a tested backup method.. that ability to roll the clock back and revert accidental or inexplicable changes.
If you are certain that you reverted the edits.. no typos or line feed errors e.g.you used a linux aware file editor.. not notepad on a PC or something similar - then it's likely a permissions error.
What permissions does the file currently have? And what app did you edit the .xml with?
.
fffft said:
There is no obvious reason why it shouldn't work of you reverted the changes. But of course that is the ultimate value of a tested backup method.. that ability to roll the clock back and revert accidental or inexplicable changes.
If you are certain that you reverted the edits.. no typos or line feed errors e.g.you used a linux aware file editor.. not notepad on a PC or something similar - then it's likely a permissions error.
What permissions does the file currently have? And what app did you edit the .xml with?
.
Click to expand...
Click to collapse
As I said, I made a copy of the file and edited it with ES3 Note Editor right on the phone. Then I renamed the original file to platform.xml.bak, and copy/pasted the new platform.xml file into system/etc/permissions. When everything went haywire, I didn't try editing the file back (I couldn't - the toasts were popping up almost faster than I could clear them and Note Editor kept crashing), I just deleted the modified file and renamed platform.xml.bak back to platform.xml. I never edited the original file at all, so that's how I am 100% positive there are no errors in it - and that's why I can't figure out why renaming it back doesn't fix the mayhem.
Now I am a total weenie when it comes to Linux - I know OF the -rw-r--r-- permissions and what they mean, but I don't know how to make the phone tell me.. But in ES3 Explorer under file properties it simply says Readable: Yes Writable: Yes Hidden: No.
What sucks is I've had to go through and set the phone back up twice now, and lost all my settings/data in the meantime over this.. And I STILL don't have a working backup method, so if it borks again I'll be doing it all over again.. I am unwilling to blow the Knox fuse, hence not having a custom ROM at this point.. But I'm fine using Towelroot just so I can unbloat and install some things.
No one wishes for things to go awry. But of course they do sometimes and it would be imprudent not to plan for that eventuality. You didn't, nor do you seem to realize just how risky the changes you have been making are to your basic system stability. You are modifying critical, system level files and properties. The expected result if there is a typo or permissions error is chaos and corruption. If I was unable to have a working backup method (from refusing to increment Knox), I wouldn't risk the changes you are making.
It's all well and nice to customize features when things turn out smoothly. But all along you have been working without a safety net, so it's not reasonable to complain about the onerous amount of work it is to reinstall the firmware when fate bites you. You can't have it two ways at once. Either you incremement Knox, allowing inclusive backups and a way to recover. Or you accept that that you are taking crazy risks and having to start over the price for doing so.
You'd be in a better position if you had some basic tools to delineate what is going on. But you haven't taken the time to learn how to read file permissions. You are working deep within a linux filesystem, so this is a very basic and useful skill.
You don't use the same file manager as me, with mine (fx), you would long press and view details. Or even easier, use the ls command e.g. ls -la. There are a dozen ways you could check permissions and a simple forum search would elaborate on many of them. It sounds like you have permissions errors, i.e the system can't access the restored .xml sheet thereby causing numerous apps to crash.
.
Uhhh, except in order to implement the safety net I have to make this simple change to this one critical system file. It's no different than not having a means to backup before rooting/flashing (since TiBu requires root and you can't do a nandroid from stock recovery) and something goes wrong.
Adding the <group gid="media_rw" /> line to the profile.xml is posted in MANY locations as a "this is all you have to do" solution to this rather stupid quirk in 4.4, with no mention whatsoever of checking/verifying permissions or any other cautions, and other people are not having this issue.
I installed FX, and it lists the permissions of all the files (including the copies of platform.xml and platform.xml.bak that I had saved on the SD card, and the virgin file currently in use) as 0644.
Taz420nj said:
Uhhh, except in order to implement the safety net I have to make this simple change to this one critical system file
Click to expand...
Click to collapse
It's your phone so you can do as you like. But risks don't go away because you ignore them. There is nothing wrong with accepting a risk that you may have to start over if things go sideways. But plunging ahead recklessly then complaining about the work to recover is patently unreasonable
I had no problem effecting the changes you are attempting. Nor have many others. Perhaps you made a typo or followed a thread with erroneous advice. You may well have a permissions error because you didn't explicitly set it or check to see if it was correct.
It's all about attention to detail e.g. checking permissions and being prepared to deal with fallout when things go astray.
.
I'm on the stock rom and I tried following this guy but I'm too dumb to figure out how do anything passed installing a ROM. So instead of following that guy, I tried doing the Nexus 4 method in the link. I probably made a stupid mistake so that's on me. I copied the just the generic.kl file using ES File Explorer and pasted it into a folder outside the system files. I made another copy of the file and started editing one. I pasted the edited generic.kl file back into the root location and restarted my phone. Nothing happened except now my power button doesn't operate correctly. It doesn't wake or put my phone to sleep. What makes this worse is my Knock-On is sorta broken because I dropped my phone so I have to tap about 30~ times to get it to function once. I tried copying the backup I made back into the folder but it didn't change anything. What can I do that isn't a factory reset? Would a factory reset even work? I'm only rooted, no unlocked bootloader.
Hi, I have a Galaxy note 3 Sm-N9005 european version, I was trying to edit the gpio-keys.kl in order to disable the volume buttons, I tried adding a "#" before the text, with and without a space after it, I tried changing the "volume_up" to "UNKNOWN" , I tried deleting the "Wake_dropped" part of the line... It doesn't matter what I do, It does nothing.
I even deleted the file (I did a backup previously), rebooted the phone, and the keys still worked.
There is a bizarre problem also. In the process, I renamed gpio-keys.kl to gpio-kksks.kl in order to be able to copy the backup since I was having some trouble. Now I have 2 files, the original gpio-keys file and that renamed file, that if I try to delete, it does nothing. If I open it with a text editor it says "no such file or directory" as a text, and If I delete that text, the file weighs 0,00kb, but it still appears on the system folder.
So 2 questions, what do I do to definitely delete that gpio-kksks.kl file? and what do I do in order to dissable the volume keys? I hope someone can help me.
Thanks.