Skip to main content
20 events
when toggle format what by license comment
May 23, 2017 at 12:40 history edited CommunityBot
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Jan 24, 2013 at 12:05 vote accept Tahir Hassan
Jan 24, 2013 at 12:05 comment added Tahir Hassan TBH, I agree with user999999999 in that I, as most users are, am only interested in a quick and dirty solution. Running a script at boot time is actually not that dirty at all.
Jan 22, 2013 at 0:26 comment added cnexus Whoops. Sorry, I think in rwx type, but anyway you get the point
Jan 21, 2013 at 0:02 comment added Izzy Just thinking aloud: If the original permissions were 0666, and you've changed them to 0777 -- all you did is make it executable for everybody (bit 1), as it before already was set read (bit 4) and write (2) for everybody. a) what should that achieve? and b) do you think it's really a good idea to keep it read- and writeable for every process? Original was rather 0644, my guess ;)
Jan 20, 2013 at 21:47 comment added t0mm13b Ha! Fair enough then I suppose! :) Yeah, if everyone is enthusiastic about it... well that's what we're here for!!!! :D
Jan 20, 2013 at 21:45 comment added cnexus I know, but my answer was simply based on the fact that the majority of people who post on places like this are only looking for quick-and-dirty solutions...not mind-numbing learning processes, unfortunately :)
Jan 20, 2013 at 21:44 history edited cnexus CC BY-SA 3.0
deleted 4 characters in body
Jan 20, 2013 at 21:40 comment added t0mm13b You'd learn so much by doing that and makes you appreciate what Linux, Android has to offer :D
Jan 20, 2013 at 21:33 history edited cnexus CC BY-SA 3.0
added 298 characters in body
Jan 20, 2013 at 21:25 comment added cnexus I know what you're talking about, but the solution proposed above is most likely a more viable solution for users in general, and probably for the OP as well. Your solution may be more permanent, but requires more knowledge of Android, boot.img splitting, and the Linux file system
Jan 20, 2013 at 21:19 comment added t0mm13b What I have stated is a more permanent solution but worthwhile instead of relying on third-party apps. And also, init-scripts are where the permissions are set at boot prior to Android loading - Simples really, instead of resorting to fiddly hacks such as the above answer each time Android boots...
Jan 20, 2013 at 21:06 history edited cnexus CC BY-SA 3.0
The HTML tags are allowed, as seen in the post here: http://meta.stackoverflow.com/questions/1777/what-html-tags-are-allowed-on-stack-exchange-sites
Jan 20, 2013 at 21:03 history rollback cnexus
Rollback to Revision 1
Jan 20, 2013 at 21:01 comment added cnexus Well obviously someone doesn't read answers fully. And not necessarily. A permanent solution can still be achieved without any need to dive into the boot.img and split the ram-disk from it. The OP can put the commands above in a script and download a third-party program to run it at boot. There are plenty of applications that have that capability and your solution is most likely too complex anyway.
Jan 20, 2013 at 20:53 review First posts
Jan 21, 2013 at 0:02
Jan 20, 2013 at 20:41 comment added t0mm13b That will work provided the handset is not rebooted, for a more permanent solution, the init.rc script would have to be modified and rebuilt within the ram-disk and for that the boot.img would have to be re-created.
Jan 20, 2013 at 20:40 history edited t0mm13b CC BY-SA 3.0
Reformatted and stripped out html tags
Jan 20, 2013 at 20:37 comment added t0mm13b Are you sure this will work, as that sounds a temporary measure, ie. permissions will be lost upon reboot? BTW: OP's handset is not-rooted so not a good answer either!
Jan 20, 2013 at 20:34 history answered cnexus CC BY-SA 3.0