11-25-2013, 06:22 PM | #166 | |
Junior Member
Posts: 9
Karma: 2582
Join Date: Aug 2013
Device: Kobo Mini
|
Quote:
Code:
Waiting for root device /dev/mmcblk0p2... |
|
11-25-2013, 09:27 PM | #167 |
Junior Member
Posts: 8
Karma: 10
Join Date: Nov 2013
Device: kobo glo
|
|
11-25-2013, 09:41 PM | #168 |
Member
Posts: 23
Karma: 186
Join Date: Jul 2013
Location: France
Device: Kobo glo
|
|
11-25-2013, 11:53 PM | #169 | |
Member
Posts: 23
Karma: 186
Join Date: Jul 2013
Location: France
Device: Kobo glo
|
Quote:
https://www.mobileread.com/forums/sho...&postcount=129 I resume because perhaps that wasn't clear... for the moment I use this workaround: Install SManager from https://play.google.com/store/apps/d...anager%26hl=en or http://smanager.wikidot.com/main:start It permit to launch a shell script after reboot You have just to create a script with Code:
ioctl -d /dev/ntx_io 127 0 --- SManager instructions: Menu, create a new script, give it a name, choose an editor, <type your script> then back, save the script then click on it in the browser (it is at the root), select boot and favorite, record, exit Menu, script should list it. Reboot. ---- or simply run the line in a adb shell or in a term apk at each reboot. (because Smanager is not very user friendly ) ---- I'm trying to install it in init.rc ( thanks to MarekGibek who has made the init.rc persistant) but that doesnt run for the moment... |
|
11-26-2013, 02:42 AM | #170 |
Zealot
Posts: 151
Karma: 676
Join Date: Aug 2007
Device: Kobo Glo, Paperwhite
|
dd366, I have seen your post but you wrote that "It works well (despite tiny char interface) but is not ideal in term of memory usage and power in sleep mode."
So I'll better wait till you will integrate script to init.rc |
11-26-2013, 03:58 PM | #171 | |
Zealot
Posts: 129
Karma: 34471
Join Date: Aug 2013
Location: Cracow, Poland
Device: Kobo Touch N905C
|
Quote:
Code:
bootdelay=0 baudrate=115200 loadaddr=0x70800000 netdev=eth0 ethprime=FEC0 uboot=u-boot.bin kernel=uImage nfsroot=/opt/eldk/arm bootargs_base=setenv bootargs console=ttymxc0,115200 bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm bootargs_mmc=setenv bootargs ${bootargs} root=/dev/mmcblk0p2 rootfstype=ext4 rootwait rw noinitrd init=/init video=mxc_elcdif_fb:off bootcmd_mmc=run bootargs_base bootargs_mmc; mmc read 0 0x70800000 0x800 0x2000; bootm bootcmd=run bootcmd_mmc bootargs=console=ttymxc0 init=/init androidboot.console=ttymxc0 keypad video=mxc_elcdif_fb:off calibration "/mmcblk0p2 rootfstype=ext4 rootwait rw noinitrd init=/init video=mxc_elcdif_fbff" I know it is the hardest part. On the other hand it is not that long string - it's only scarry If you update it correctly you will succeed. I can try to update it for you if you sent me this fragment from your image. If you have different addresses on Kobo Mini (0x70800000?) - you should leave your values untouched. Also this part is very important: 0x70800000 0x800 0x2000 The last value is the max size of the kernel. Please note that Android kernel is longer and it is 0x2000 instead of smaller value whatever it was before. Last edited by MarekGibek; 11-26-2013 at 04:03 PM. |
|
11-26-2013, 04:07 PM | #172 |
Zealot
Posts: 129
Karma: 34471
Join Date: Aug 2013
Location: Cracow, Poland
Device: Kobo Touch N905C
|
Yes. Boot images are placed before first partition. Just like partition table, u-boot block, kernel, ramdisk in previous version, waveform data, hardware configuration, passwords to your bank account and more crazy stuff
|
11-26-2013, 04:17 PM | #173 | |
Enthusiast
Posts: 35
Karma: 946
Join Date: Mar 2013
Device: Kobo Mini
|
Quote:
|
|
11-26-2013, 04:26 PM | #174 | |
Zealot
Posts: 129
Karma: 34471
Join Date: Aug 2013
Location: Cracow, Poland
Device: Kobo Touch N905C
|
Quote:
It's funny that poweroff image is empty (white). Because of that I thought there is no such thing as poweroff image. There is an easier way to change sleeping image. You can put "suspend.jpg" on user partition (/sdcard). |
|
11-27-2013, 12:15 PM | #175 |
Member
Posts: 17
Karma: 190
Join Date: Nov 2013
Device: Kobo Touch
|
I would like to install this on a kobo aura hd. I tried with the touch img but it get's stuck on boot...
Can anyone help me with this? Thanks |
11-27-2013, 01:02 PM | #176 | |
Zealot
Posts: 129
Karma: 34471
Join Date: Aug 2013
Location: Cracow, Poland
Device: Kobo Touch N905C
|
Quote:
I think I know how to do it but Aura HD is so expensive reader that I don't plan to buy it. And merging Android specific stuff to Aura HD's kernel and testing it later is not a one evening job. |
|
11-27-2013, 03:31 PM | #177 | |
Time Waster
Posts: 422
Karma: 289160
Join Date: May 2011
Device: Kobo Glo and Aura HD
|
Quote:
|
|
11-27-2013, 09:24 PM | #178 | |
Member
Posts: 23
Karma: 186
Join Date: Jul 2013
Location: France
Device: Kobo glo
|
Quote:
------------ Where come from the kernel source you recompiled with rotation patch ? The image has HW CONFIG v1.6 I have found only these two kernels: from http://www.tolino.de/at/produkte/tol...hnische-daten/ http://tolino.de/wp-uploads/kernel.tar.gz 158 485 068 HW CONFIG is v1.7 (within ntx_hwconfig.c) from http://naberius.de/category/linux/programming/kernel/ http://tolino.naberius.de/kernel.tar.gz 114 164 844 HW CONFIG is v1.3 (within ntx_hwconfig.c) Or perhaps you have left untouched the HW CONFIG v1.6 from original image and used one of these two above ? [Edit] I have found the kernel on your github account. It's the HWConfig v1.3 version, am I right ? You have only modified drivers/input/touchscreen/zforce_i2c.c ? Last edited by dd366; 11-28-2013 at 09:13 AM. |
|
11-28-2013, 04:21 AM | #179 | |
Junior Member
Posts: 1
Karma: 10
Join Date: Nov 2013
Device: Kobo Aura HD
|
Looking forward to it!
Quote:
|
|
11-28-2013, 08:17 PM | #180 |
Junior Member
Posts: 8
Karma: 10
Join Date: Nov 2013
Device: kobo glo
|
wait front light off path
|
Tags |
android, glo, kobo, shine, tolino |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Glo Synchronizing my own books between Kobo Glo and Kobo Android | ploum | Kobo Reader | 35 | 01-07-2015 06:28 PM |
kobo glo / android phone not detected | danieldo | Devices | 2 | 02-02-2013 12:28 PM |
Glo Screen durability of the glo..is it better than the Nook Glo?? | Tony1988 | Kobo Reader | 4 | 01-10-2013 07:38 PM |
Glo Can kobo glo run android app such as nook glo? | suspect | Kobo Developer's Corner | 1 | 12-28-2012 11:25 PM |
Released 14 HoneyComb ROM MOD for Android OS 1.6 /Android OS 2.1 HCV13.0 B20 | tipstir | Android Devices | 0 | 05-20-2011 02:59 AM |