Android on Kobo: "Tips and Apps" - Page 17

JimMcLaren · 05-30-2014, 12:37 PM

Quote:

Originally Posted by space4

The text/icon can be made bigger by adding a line in file /system/build.prop
eg.
ro.sf.lcd_density=265

I have bad eyes. I put in value 320 to make the text even bigger.

Previously I found the UC Mini Browser can tap to turn page / use on-screen buttons to turn page, but the text is too small to be comfortably read. After making the above change, the text is readable now!

I'm having a hard time doing this. I can't save build.prop or copy over it. If I run "chmod 777 build.prop" from a terminal I get "Unable to chmod build.prop. Read only file system" If I try to change permissions in es file explorer I just get a less than helpful error, probably for the same reason. Any suggestions on how to proceed would be appreciated.

JimMcLaren · 05-30-2014, 05:15 PM

Well I figured it out. For those trying to do the same thing, here's what I did.

cat /proc/self/mountinfo - This was just to get the list of mountpoints
mount -o rw,remount -t yaffs2 /dev/root / - This mounts the drive for read/write
chmod 777 build.prop - This allows me to overwrite or edit the build.prop
edit the build.prop and save it
chmod 750 build.prop - I'm not 100% certain this is the right permissions for build.prop but it should be safe.
reboot

The device is certainly more usable now.

embryo · 05-30-2014, 07:13 PM

Quote:

Originally Posted by JimMcLaren

I'm having a hard time doing this. I can't save build.prop or copy over it. If I run "chmod 777 build.prop" from a terminal I get "Unable to chmod build.prop. Read only file system" If I try to change permissions in es file explorer I just get a less than helpful error, probably for the same reason. Any suggestions on how to proceed would be appreciated.

I see that you found a way to do this, but using 'ES File explorer' was enough for me.
I could change permissions and then edit build.prop in 'ES Note editor' without problems.

To work as root you have to turn ON the "Root Explorer" switch at the 'ES explorer' settings.

space4 · 05-31-2014, 04:33 AM

Quote:

Originally Posted by JimMcLaren

Well I figured it out. For those trying to do the same thing, here's what I did.

cat /proc/self/mountinfo - This was just to get the list of mountpoints
mount -o rw,remount -t yaffs2 /dev/root / - This mounts the drive for read/write
chmod 777 build.prop - This allows me to overwrite or edit the build.prop
edit the build.prop and save it
chmod 750 build.prop - I'm not 100% certain this is the right permissions for build.prop but it should be safe.
reboot

The device is certainly more usable now.

The / is mounted as read-only. To be able to change any file under it, make / writable first. It can be done in a few clicks in ES File Explorer.
Tools -> Root Explorer -> ON
click on Root Explorer -> Mount R/W -> change / to be RW
(remember to change it back to RO after modifying the file)

Sanxel · 06-02-2014, 04:17 PM

Quote:

Originally Posted by embryo

The solution to my memory problems (for the time being) is the V6 SuperCharger script, that I use also on my phone.
The version I used was this one.

Thanks for the tip. Did you install all the scripts in V6SuperCharger? And what version of BusyBox did you use? Thanks

embryo · 06-02-2014, 08:16 PM

Quote:

Originally Posted by Sanxel

Thanks for the tip. Did you install all the scripts in V6SuperCharger? And what version of BusyBox did you use? Thanks

Xmm, I don't remember many details.
I didn't install a 3G script, and I made the Launcher Hard to Kill.
The BusyBox is the one that came with the image (1.18.4).
Does it make a difference?

Sanxel · 06-03-2014, 07:34 AM

Quote:

Originally Posted by embryo

Does it make a difference?

Thanks for the reply. I've installed it the same way, but with the default setting for the Launcher. All seems good, but i still experienced one reset in Opera(maybe too many tabs). In the instructions it's recommended to install busybox v1.19.4....

embryo · 06-03-2014, 02:34 PM

Quote:

Originally Posted by Sanxel

In the instructions it's recommended to install busybox v1.19.4....

I installed the 1.19.4 version and I'm checking for differences

I hope that you have the 99SuperCharger.sh run on boot, otherwise some of the settings don't work.

Sanxel · 06-04-2014, 01:49 AM

Quote:

Originally Posted by embryo

I hope that you have the 99SuperCharger.sh run on boot, otherwise some of the settings don't work.

Yeah, I do.
I installed this recommended version "busybox_v1.19.4_wraithdu--installer_script_v14. It persisted after reboot, so no need in busybox_v1.19.4_wraithdu--boot_reinstaller_script_v14--installs_every_boot. So far no resets, but I guess they cannot be completely avoided...

Krytes · 06-05-2014, 12:27 AM

Is there another place to download Angor's patches? Dropbox says the links are shut down due to too much traffic.

So far I've only managed to install the image on my SD card and rearrange the partitions (30 Mb unallocated, 6.5 Gb Kobo EXTSD (Fat32), 695 Mb Android Data, 198 Mb Android System). Booting the kobo gives an error message "We couldn't recognize your Micro SD card. Please format it to FAT32 and try again", and holding down the glow button while booting just does a factory reset. I'm assuming that the errors are just because I haven't installed the patches yet?

Sanxel · 06-05-2014, 04:45 AM

How to make an app not killable? Because I experience BatteryOverlayPercent and DisplayBrightness disappearing from time to time....

embryo · 06-05-2014, 07:01 AM

Quote:

Originally Posted by Krytes

Is there another place to download Angor's patches? Dropbox says the links are shut down due to too much traffic.

Here you go ...

OP updated.

embryo · 06-05-2014, 07:10 AM

Quote:

Originally Posted by Sanxel

How to make an app not killable? Because I experience BatteryOverlayPercent and DisplayBrightness disappearing from time to time....

If you are using the V6 SuperCharger, maybe you can try the 16th option (BulletProof Apps).

Never used it, so you're on your own ...

Krytes · 06-05-2014, 12:57 PM

Thanks!

Krytes · 06-05-2014, 03:00 PM

Hmm, I'm still having problems getting it to work - still get the "Can't recognise microSD card, please format to FAT32" message every time. I've tried it with two different cards now - an 8 Gb type 10, and a 16 Gb type 4. Both cards were fine initially, and then after I installed the image and rearranged the partitions, neither is recognised by Kobo (they're both still recognised by my computer just fine). Once they're not recognised, they seem to stay not recognised - even completely reformatting the SD card to all FAT32 doesn't help.

What am I doing wrong? I used USB duplicator image writer to write the image and minitool partition wizard to move the partitions. I'm using Windows 7. I've been writing the image and moving the partitions while the SD card is in the kobo, if that makes a difference.

05-30-2014, 05:15 PM	#242
JimMcLaren Addict Posts: 260 Karma: 1014230 Join Date: Jan 2010 Device: Onyx Boox T68, Kobo Aura HD, Pocketbook 302, Pocketbook 912, Nook HD+	Well I figured it out. For those trying to do the same thing, here's what I did. cat /proc/self/mountinfo - This was just to get the list of mountpoints mount -o rw,remount -t yaffs2 /dev/root / - This mounts the drive for read/write chmod 777 build.prop - This allows me to overwrite or edit the build.prop edit the build.prop and save it chmod 750 build.prop - I'm not 100% certain this is the right permissions for build.prop but it should be safe. reboot The device is certainly more usable now.

06-05-2014, 12:27 AM	#250
Krytes Enthusiast Posts: 48 Karma: 24 Join Date: Jul 2008 Device: Kobo Clara BW, Boox Tab Mini C, Boox Note 2	Is there another place to download Angor's patches? Dropbox says the links are shut down due to too much traffic. So far I've only managed to install the image on my SD card and rearrange the partitions (30 Mb unallocated, 6.5 Gb Kobo EXTSD (Fat32), 695 Mb Android Data, 198 Mb Android System). Booting the kobo gives an error message "We couldn't recognize your Micro SD card. Please format it to FAT32 and try again", and holding down the glow button while booting just does a factory reset. I'm assuming that the errors are just because I haven't installed the patches yet? Last edited by Krytes; 06-05-2014 at 12:35 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Users tips, apps and FAQs for the new reader models	paola	PocketBook	181	04-17-2023 01:29 PM
I'm new to Android - tips?	Queensjoy	Android Devices	19	09-11-2013 10:41 PM
Android Where to Get Android Apps	obsessed2	enTourage Archive	2	05-05-2011 05:01 PM

06-05-2014, 04:45 AM	#251
Sanxel Member Posts: 16 Karma: 10 Join Date: Mar 2014 Device: Kobo Glo	How to make an app not killable? Because I experience BatteryOverlayPercent and DisplayBrightness disappearing from time to time....

06-05-2014, 12:57 PM	#254
Krytes Enthusiast Posts: 48 Karma: 24 Join Date: Jul 2008 Device: Kobo Clara BW, Boox Tab Mini C, Boox Note 2	Thanks!

06-05-2014, 03:00 PM	#255
Krytes Enthusiast Posts: 48 Karma: 24 Join Date: Jul 2008 Device: Kobo Clara BW, Boox Tab Mini C, Boox Note 2	Hmm, I'm still having problems getting it to work - still get the "Can't recognise microSD card, please format to FAT32" message every time. I've tried it with two different cards now - an 8 Gb type 10, and a 16 Gb type 4. Both cards were fine initially, and then after I installed the image and rearranged the partitions, neither is recognised by Kobo (they're both still recognised by my computer just fine). Once they're not recognised, they seem to stay not recognised - even completely reformatting the SD card to all FAT32 doesn't help. What am I doing wrong? I used USB duplicator image writer to write the image and minitool partition wizard to move the partitions. I'm using Windows 7. I've been writing the image and moving the partitions while the SD card is in the kobo, if that makes a difference.

Advert

Advert