Quantcast
Channel: MobileRead Forums - Kobo Developer's Corner
Viewing all 1561 articles
Browse latest View live
↧

Kobo GPL Violation regarding source availability for the Kobo Arc

April 25, 2013, 12:45 pm
$
0
0
Quote:
Thank you for contacting Tier 2 Kobo Customer Care. We apologize for the delay in our response.
I have contacted our development time regarding your questions about GPL codes for the Arc firmware.
Kobo doesn't use any open source code under the GPL license. So we won't be able to provide you with that information. The Android environment itself may use some. For the licensing information for Android, you can refer to the legal section in the Settings of the Device under About Tablet.
To navigate to this are in your device:
- From the Apps page, Tap on Settings
- Scroll down to About Tablet from the left menu
- Tap on Legal Information
- Under Open Source Licenses, the GPL information displays.

Hope this answers your question. Please let us know if there is any other information you require.
Seriously? Doesn't use any gpl source code? I guess the Kobo Arc's version of Android doesn't run linux.

I think gpl-violations.org would be interested to hear about this doozy. Funny thing is that the full license indicating that source must be provided is there in the license.

Ugh... Why do I bother with this?
↧
Search

New prefix; Firmware bug, issue or request list

April 26, 2013, 3:42 am
$
0
0
Prefix
Can a new prefix be added to postings? Prefix: Touch Glo Mini Aura?
Now it only possible to select one device. A little "problematic" for soms threads as future firmware features requests and firmware bugs: the same bugs and feature request for different devices in different threads (Touch and Glo).
My opinion: firmware releases are the same for all devices (until further notice): Touch, Glo, Mini and Aura. So bugs (and feature requests) apply to all devices. Except when noted or a feature (e.g. front light) is limited to some devices. But still should be posted in the same thread.

Firmware bug, issue or request list
Second, can a list of reported bugs/issues/requests added to the first or second post of the threads? Or in a closed separate thread that is periodically updated based on post in firmware related threads?

At the moment it is quite complicated to find out if a bug already has been reported. As the threads are usually long and also contain remarks, work arounds etc.

E.g.
Known bugs
Open
* (some) dictonaries not functioning: wrong format (#posting number) (# firmware release)
* annotations/bookmark issues (#posting number) (# firmware release)
…
Closed/Solved (by Kobo, no user work arounds)
* issue (#posting number (# firmware release)

Where:
#posting number: first posting reporting a bug/issue in current or previous thread.
# firmware release: bug/issue first appeared in firmware release number x.x.x)
…

You'll get the idea. Better suggestions are welcome.
It also becomes much easier to track Kobo's efforts to solve known bugs.
↧
↧

delete me

April 30, 2013, 8:57 am
↧

rtcwake on Kobo?

May 2, 2013, 10:16 am
$
0
0
after enabling Wifi on/off to save battery, the next step would be to really sleep the processor.

linux has rtcwake for this. but when I try it, it does not seem to work
Quote:
rtcwake -a -s 10
rtcwake: /dev/rtc0 not enabled for wakeup events
i am not into this topic yet. anyone an idea?
↧

Glo Night Mode

May 2, 2013, 1:52 pm
$
0
0
Here's a new hack that will hopefully benefit some people (I know I use it!).




A little while back I released a very hacky white on black display mode for the Glo. Not long after, yoq put together a much nicer version of the hack, which you can download here.


Installation - for firmware version 2.5.1 ONLY!

A word of caution: This hack could potentially cause your Glo to not boot. If that happens, a factory reset (hold the light button while turning on the device) should resolve any issues. Also, this installer is specifically for firmware 2.5.1. It may or may not work on other versions.

You'll need to install the Kobo Tweaks plugin and create a new file named "kobotweaks.ini" in the .kobo folder on your Glo. Put these lines in kobotweaks.ini:
Code:
[Global]
compatFirmware=2.5.1

[CustomCommands]
Toggle Night Mode=tweaks.executeSystemCmd(\"/mnt/onboard/.kobo/nightmode.sh\")
Download "gloNightMode.zip", below. Extract it and put the KoboRoot.tgz file in the .kobo folder on your Glo. After your Glo reboots, open the Library to activate the plugin, then go back to the home screen. Under the "Tools" menu you can now select "Toggle Night Mode" to turn the hack on and off.

Attached Thumbnails
Click image for larger version Name: gloInvert.jpg Views: N/A Size: 138.9 KB ID: 105268  
Attached Files
File Type: zip gloNightMode.zip (5.8 KB)
↧
↧

Touch Is it possible to "restore" a Demo Kobo?

May 3, 2013, 10:54 am
$
0
0
I (stupidly :o) bought a demo Kobo Touch from ebay, thinking that I could restore it as I had several demo Kindles. It was only on searching through the site and being unable to find any methods available, that I realized that perhaps it wasn't possible to "restore" a demo Kobo. However, I thought I might check one more time to see if there are any methods I have missed that might be of some help.
↧

Hack to reopen last book

May 5, 2013, 5:53 am
$
0
0
I would find a way to reopen the last opened book at startup, if I shut down when the book was opened.
What I want to do is to write the document path to some file before the device is shut down if the document is open, and re-open the document when the OS is ready. The problems are:
  1. how can I insert an action before the shutting down?
  2. where can I find the last opened document? I'm quite sure this information is stored somewhere (the db?)
  3. how can I open a document?
↧

Glo How to start customizing the GLO?

May 5, 2013, 7:09 am
$
0
0
Hi all, Im Herman from Belgium got my GLO a few days back and as with all devices i like to customize it to the way I want it, not the firm i bought the device from . :-)

I read and searched about info on how to tweak it but i have a few questions i hope they will be answered because they are prob noobish ones. :thanks:

I downloaded the tweaks file, put it on the GLo in the .kobo dir, after restart nothing happens and file is gone.

Q: Is this because i just put it there with the explorer instead of accesing thru TELnet session?

I read about the Kobotweaks.ini file.

Q: Is this file generated when the above succeed or do i have to manually create one?

These are my 2 questions, hope they are not to Noobisch :smack:

greetz.
↧
Search

(semi)automatic dump of Kobo firmware on a SD card

May 6, 2013, 7:37 am
$
0
0
Hi,

waiting for my Aura to come, I put together a simple hack to automatically dump the internal firmware of a Mark 4 Kobo (i.e. Mini, Glo, Aura and recent Touch) on an SD card. This should work on any recent version of the firmware...

As usual I assume no responsibility for any damage on your device, I have tested it on a Glo and it works for me…

You will need a SD card with enough free space to hold the whole firmware (i.e, 2/4GB for Glo, 4 for Aura, and so on). I used a 16GB SD, just to be sure :)
You should also start with a fully charged Kobo.

The trick uses a modified upgrade-wifi.sh script in /etc/init.d; this script is started during a firmware upgrade when there is a upgrade folder in .kobo, and I modified it to dump the internal card to folder KoboDump in the SD.

In order to dump the firmware, insert an SD with at least 2GB free (I suggest using a larger card…) in your Kobo, connect it to the PC and create an empty folder named KoboDump on the root of the SD. Then extract the contents of DumpScript zip and copy KoboRoot.tgz and upgrade folder in folder .kobo within the internal memory (be careful that KoboRoot.tgz and upgrade should be right within .kobo folder and not in a subfolder).

Now eject your Kobo and disconnect it from the PC: you should see the usual upgrade screens. If everything goes as expected, you should wait for a long time while the script dumps the firmware: on a Glo I waited more than 25 minutes for a 2GB dump.

After a (possibly quite) long time, your Kobo will restart. Connect it again to the PC and you should find that the KoboDump folder has been renamed to KoboDumpDone. Inside it you should find a dump.img file: this is your dump.
Copy it on your PC and you should be able to open it (under Windows) with DiskInternal’s Linux Reader.

To restore the original upgrade-wifi.sh, extract the KoboRoot.tgz from OriginalScript zip to the .kobo folder, disconnect and wait a couple of minutes until the script is copied back.

Let me know if this works for you, and which model you dumped with this.

Attached Files
File Type: zip DumpScript.zip (1.2 KB)
File Type: zip OriginalScript.zip (787 Bytes)
↧
↧

modifying reading stats (number of books read and hours read)?

May 11, 2013, 3:49 am
$
0
0
Hi

Recently I did a factory reset on my kobo and I lost my reading stats(number of book read and hours read.

I was wondering if there was any way to manually modify those numbers in a configuration file or in the database? I've looked at the database but it doesn't seem to be there so my guess is that these numbers are somewhere else!

Thank you
↧

Getting rid of the Header in 2.5.2 epubs

May 14, 2013, 6:02 am
$
0
0
With the patch 2.5.2 Kobo decided to "kobo-fy" the epub rendering engine, by adding a permanent title-line on top of the screen.

I was not really happy with the prospect of not upgrading the Kobo from now on, only to get rid of the bar, so I started to experiment a bit.

The quick and dirty solution I found atm is to just patch the 2.5.1 reader *.so back in after applying the 2.5.2 patch.
After a few hours of reading it seems to work without any problem.

I also tried older reader versions (2.2.1, 2.3.0, 2.4.0) but they don't work, so some dependencies probably have changed with the big 2.5.0 update.

Would be nice to figure out a way to make the older versions work again, to get a version that had working italics for certain fonts, or the back to library function.

The attached file includes the readerapp file from 2.5.1 and from 2.5.2.

Installation procedure is as usual, rename the files to koboroot.tgz and put them in the .kobo folder.

Attached Files
File Type: rar Kobo - adobereader.rar (203.1 KB)
↧

Japanese Kobo Dev - kobohack-j

May 14, 2013, 6:59 am
$
0
0
Searching the Web i stumbled over a few development projects for the Kobo Software.

Sadly my knowledge of the language is almost non-existant and translation software is rather limited especially when it comes to linux based libraries. :P

As far as I can understand it, this first project is an effort to updated internal libraries for increased performance, and to add some additional functionality.

It seems to support up to date kobo firmware 2.5.2.

I hope someone who can read japanese or/and linux, might help the rest of us figure out whats going on there. *g*

kobohack-j
↧

Japanese Kobo Dev - CFW

May 14, 2013, 7:12 am
$
0
0
Searching the Web I stumbled over a few development projects for the Kobo.

Sadly my knowledge of the language is almost non-existent and translation software is rather limited. :P

As far as I can understand it, this project is similar to our kobo Tweaks plugin, with a few other options, like setting a login password.

It is official only supporting firmware version 2.3-2.4 but seems to run on 2.5 with a few problems.

I hope someone who can read Japanese, might help the rest of us figure out whats going on there. *g*

CFW wiki page
↧
↧

disabling flashing LED?

May 14, 2013, 2:00 pm
$
0
0
dear all,

as part of my alternative setup i want to comment out nickel in rcS.
but seems to be responsible for disabling the flashing led after the start process.

currently nickel is started and then stopped with "killall" afterwards.

any idea how i can stop the flashing on my own?
↧

Hacking SD card file system

May 21, 2013, 6:11 am
$
0
0
After some discussions got started over in the Upgrade thread on changing the SD card to a different format than the default FAT32 I thought I would move the discussion over here.

Original request:

Quote:
Originally Posted by jlynton (Post 2519863)
My request is for it to be possible to use an ext3 (or ext4) formatted microSD card, mainly to get around the file limitations in the images directory.
My initial reply:

Quote:
Originally Posted by PeterT (Post 2519911)
Maybe one of the tweakers in the Kobo Developer's Corner could look into this. I have a gut feeling that what is needed is a change to the script used for mounting the SD card.

Quote:
Originally Posted by \usr\local\Kobo\uDev\sd
Code:
DEV="/dev/mmcblk1p1"

if [ "$DEV" == "$DEVNAME" ]; then
        if [ "$ACTION" == "add" ]; then
                dosfsck -a -w $DEVNAME
                mount -r -t vfat -o shortname=mixed $DEVNAME /mnt/sd
                if [ $? != 0 ]; then
#                        mount -r $DEVNAME /mnt/sd
#                        if [ $? != 0 ]; then
                                echo sd mount fail $DEVNAME >> /tmp/nickel-hardware-status &
#                        else
#                                echo sd $ACTION $DEVNAME >> /tmp/nickel-hardware-status &
#                        fi
                else
                        echo sd $ACTION $DEVNAME >> /tmp/nickel-hardware-status &
                fi
        fi
fi
It looks like the ability to mount non FAT32 formats was there at one point, and has now been commented out.
More discussion:
Quote:
Originally Posted by tshering (Post 2520213)
If one makes changes there, one might also consider adjusting usr/local/Kobo/udev/usb.
Quote:
Originally Posted by jlynton (Post 2520249)
This looks interesting, is there an easy way to access these files (glo, without removing internal microSD card)?
Quote:
Originally Posted by tshering (Post 2520310)
One way of modifying these files is by using the upgrade mechanism. Unpack the file "KoboRoot.tgz" from the FW update file, which you can find here ,and then unpack its (KoboRoot.tgz's) content. After modifying some files you can pack them again into "KoboRoot.tgz" (you have of course to preserve the path of each modified file, but there is no need to include all the other files). Copy then "KoboRoot.tgz" to the folder ".kobo" of the reader. After unplugging the reader, it will copy the content of "KoboRoot.tgz" to the system partition. Confer the paragraph "The Kobo upgrade mechanism" of "Hacking the Kobo Touch for DUMMIES". This part is valid for Glo too.
Word of caution: Preserve lower and upper case of file and path names (e.g. udev, not uDev).
If you mess things up, you might have to factory reset the reader. If you have a lot of annotations and highlights, you might consider making a back up of .kobo/KoboReader.sqlite.
Quote:
Originally Posted by jlynton (Post 2520321)
Thanks, this looks like something I could try on my day off. I have looked at the two files usr/local/Kobo/udev/usb and usr/local/Kobo/udev/sd, both have the commented out section that PeterT refers to. I assume that one refers to the internal microSD cards FAT32 partition, and the other to the external microSD card, do you know which is which?
Quote:
Originally Posted by PeterT (Post 2520359)
Actually I believe that the sd is used only for the mounting of the external sd card; note that it mounts the card on /mnt/sd. usb is used for when the device is attached to your PC.

/mnt/onboard appears to be used for the partition that is accessible to us normally, and /mnt/sd to the external SD card.

I think that this section
Quote:
Originally Posted by /usr/local/Kobo/udev/usb
Code:
        if [ -e $DEV ]; then
                mount -r -t vfat -o shortname=mixed $DEV /mnt/sd
#                if [ $? != 0 ]; then
#                        mount -r $DEV /mnt/sd
#                fi
        fi
should be similar to the code in /usr/local/Kobo/udev/sd
↧
Search

linux command to open nickel or Access with a sdcard file argument

May 23, 2013, 12:47 pm
$
0
0
Hi guys,

The architecture of the kobo software is an enigma to me.

But I understand that any command line can be done (for example with the Tweak).

Is there a way to "simply" start the viewer (default or access) by passing a file adress as argument ?

Thank you for your lenience on this probably stupid question.
I guess that if it was easy, we would have had a tree browser with an "open with" button for quite a long time.

François
↧

[Bash] 'sleep' x becomes 'leep' x

May 26, 2013, 8:59 am
$
0
0
Hello,

I just started to write small scripts for my Kobo Mini.
At some points I need the script to pause for a few seconds.
So I used the sleep command.
Unfortunately the scripts don't work as they should.
After every 'sleep' command I get the error: 'leep: invalid number '
Independent of the number I use.
So 'sleep 2' --> 'leep: invalid number '
'sleep 10' --> 'leep: invalid number '

Any ideas how I can solve this Problem or another way to pause a script for a few seconds?

Thanks :)
↧
↧

Glo Is there a way to fix Cyrilic Glo Keyboard

May 28, 2013, 6:17 am
$
0
0
Is there a way to fix Cyrilic Glo Keyboard ?

I think defauly Kobo glo Font must be changed because it doesnt support cyrilic. How can i change default Kobo glo font to check if I can fix this ?
↧

precompiled binaries,

May 28, 2013, 6:55 am
$
0
0
if you need any precompiled binaries you can find them here.
http://mes5devel.mandriva.com/~fbui/.../main/release/

they worked well for me. pain is, that you have to extract them and then copy them over to your kobo (i always remove/mount the internal sdcard).

also if you need ldd to figure out what libs are missing:
glibc-2.14.90-16-mdv2012.0.armv7l.rpm

maybe somebody has an idea to install and use a package manager?

I also managed to compile and run CutyCapt + Xvfb on my KoboTouch.
I will provided the binaries when i have everything smooth and clean.

Greetings
Grunge
↧

Glo Running browser without Wifi connection

May 28, 2013, 3:11 pm
$
0
0
Hi,

I am using kiwix-serve to have a static copy of Wikipedia (on a SD card) to my Kobo. It works, but, as the dump is served using HTTP, I have to connect to localhost with a web browser to read it. However, the Kobo's built-in web browser refuses to work without an active Wifi connection, which is sad as the point is to read the dump offline...

Is there a way to bypass this check or fool nickel into believing that wpa_supplicant is connected to a network? I tried writing into /tmp/nickel-hardware-status following what is done by /etc/udhcpc.d/default.script, but this doesn't seem to change anything. I tried running an strace on nickel with and without a Wifi connection to see if I could identify how the check was performed, but I wasn't able to find anything. Any other ideas?

Thanks!
↧
Viewing all 1561 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>