Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader > Kobo Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 12-08-2013, 08:07 AM   #211
bulnes123
Member
bulnes123 doesn't litterbulnes123 doesn't litter
 
Posts: 17
Karma: 190
Join Date: Nov 2013
Device: Kobo Touch
Android on Aura HD

Any advances on kobo aura HD? Can anyone tell me what to do to make it work? I tried the touch image but it hangs after power on
bulnes123 is offline   Reply With Quote
Old 12-08-2013, 08:51 AM   #212
diogo_abdalla
Junior Member
diogo_abdalla began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Sep 2013
Device: kobo glo
Hello. Sorry to be such a newbie, but I just got here and found about this and got very excited, but this thread is pretty big already and I dont know where to start.

So, has anybody set up a guide (or tutorial or something) on how to install android on the kobo (I have a Glo, by the way)? Can someone please direct me to where I can find some instructions on how to do it?

Thank you
diogo_abdalla is offline   Reply With Quote
Old 12-08-2013, 01:03 PM   #213
stasys
Zealot
stasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enough
 
Posts: 147
Karma: 598
Join Date: Aug 2007
Device: Kobo Glo, Paperwhite
I'm presuming you have Windows.

Download the working Android image from this post: http://www.mobileread.com/forums/sho...&postcount=151

Get image writer from here: http://www.vconsole.com/client/?page=page&id=29

Insert blank SD card into card reader and put Android image to your card. If your card is bigger than 2GB, you can expand partition which is Fat32 to fill all your card space with this program: http://www.partitionwizard.com/free-...n-manager.html

Switch off your Kobo Glo and open it as per instructions from here: http://www.mobileread.com/forums/sho...48&postcount=2

Remove SD card from KoboGlo and put it into safe place. Insert there your SD card with Android image into KoboGlo.

Switch on your Kobo Glo.

If you do not like blinking LED, switch it off as per instructions from here: http://www.mobileread.com/forums/sho...&postcount=167

To connect AndroKoboGlo to PC you will need a driver - get it from here: http://translate.google.com/translat...-play-32350%2F
Follow the instruction from step 8

For driver installation in Windows 8 fxp33 advised to do the following:
click the : 2_vendor_id.bat before doing 3_install_su.bat

Note 1: Alreader which comes with the Android image above is outdated, newest one you can get from here: http://alreader.com/download.php?file=AlReader.apk

Note 2: You need Tolino reader to connect to PC, so before uninstalling it, as embryo advised get program "Auto Mount Your SD Card". After that you can uninstall Tolino reader.

Last edited by stasys; 01-05-2014 at 06:01 AM. Reason: driver on Windows 8/ remove Tolino reader
stasys is offline   Reply With Quote
Old 12-08-2013, 03:51 PM   #214
phoinikos
Junior Member
phoinikos began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Dec 2013
Device: Kobo Mini
Quote:
Originally Posted by mastnacek View Post
Go Go Go I cant wait
Hey,

Any update on the Kobo Mini side?
phoinikos is offline   Reply With Quote
Old 12-08-2013, 11:42 PM   #215
embryo
Addict
embryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the end
 
embryo's Avatar
 
Posts: 259
Karma: 31140
Join Date: Aug 2013
Device: Kobo Glo
Quote:
Originally Posted by stasys View Post
Note 1: Alreader which comes with the Android image above is outdated, newest one you can get from here: http://alreader.com/download.php?file=AlReader.apk
Question: With this version, when you go to the library, can you read the fonts on the black background?

Quote:
Note 2: Do not uninstall Tolino reader, or you will not be able connect to PC.
Well, I did froze it with TitaniumBackup, and I can connect to the PC with "Auto Mount" https://play.google.com/store/apps/d...utomount&hl=en
embryo is offline   Reply With Quote
Old 12-09-2013, 05:37 AM   #216
stasys
Zealot
stasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enough
 
Posts: 147
Karma: 598
Join Date: Aug 2007
Device: Kobo Glo, Paperwhite
Quote:
Originally Posted by embryo View Post
Question: With this version, when you go to the library, can you read the fonts on the black background?
What black background? This version has e-ink tick box in settings. I have it ticked and never seen any black background.
stasys is offline   Reply With Quote
Old 12-09-2013, 07:25 AM   #217
diogo_abdalla
Junior Member
diogo_abdalla began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Sep 2013
Device: kobo glo
Quote:
Originally Posted by stasys View Post
I'm presuming you have Windows.

Download the working Android image from this post: http://www.mobileread.com/forums/sho...&postcount=151

Get image writer from here: http://www.vconsole.com/client/?page=page&id=29

Insert blank SD card into card reader and put Android image to your card. If your card is bigger than 2GB, you can expand partition which is Fat32 to fill all your card space with this program: http://www.partitionwizard.com/free-...n-manager.html

Switch off your Kobo Glo and open it as per instructions from here: http://www.mobileread.com/forums/sho...48&postcount=2

Remove SD card from KoboGlo and put it into safe place. Insert there your SD card with Android image into KoboGlo.

Switch on your Kobo Glo.

If you do not like blinking LED, switch it off as per instructions from here: http://www.mobileread.com/forums/sho...&postcount=167

To connect AndroKoboGlo to PC you will need a driver - get it from here: http://translate.google.com/translat...-play-32350%2F
Follow the instruction from step 8

Note 1: Alreader which comes with the Android image above is outdated, newest one you can get from here: http://alreader.com/download.php?file=AlReader.apk
Note 2: Do not uninstall Tolino reader, or you will not be able connect to PC.
Thank you a lot! Im actually uasing linux, but I guess the only change is in how to write the image, right?
diogo_abdalla is offline   Reply With Quote
Old 12-09-2013, 07:31 AM   #218
embryo
Addict
embryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the end
 
embryo's Avatar
 
Posts: 259
Karma: 31140
Join Date: Aug 2013
Device: Kobo Glo
Quote:
Originally Posted by stasys View Post
What black background? This version has e-ink tick box in settings. I have it ticked and never seen any black background.
I did also, but when I am in the library the text is black on black background.
I can't see a thing

I must be doing something wrong...

Edit: Never mind. It was a version thing.
With 1.41 the library is readable.

Last edited by embryo; 12-27-2013 at 10:13 PM.
embryo is offline   Reply With Quote
Old 12-10-2013, 03:12 AM   #219
stasys
Zealot
stasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enough
 
Posts: 147
Karma: 598
Join Date: Aug 2007
Device: Kobo Glo, Paperwhite
Quote:
Originally Posted by diogo_abdalla View Post
Thank you a lot! Im actually uasing linux, but I guess the only change is in how to write the image, right?
Yes. And how to connect to PC, but here I can not give you any advices - I've never used Linux.
stasys is offline   Reply With Quote
Old 12-12-2013, 09:08 AM   #220
embryo
Addict
embryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the endembryo knows the complete value of PI to the end
 
embryo's Avatar
 
Posts: 259
Karma: 31140
Join Date: Aug 2013
Device: Kobo Glo
Quote:
Originally Posted by dd366 View Post
Finally there is still two points I wish to fix or be fixed: (Glo related)
- 1 Ghz cpu (hwconfig 1.7 kernel has code for that)
- Hall sensor support (Smart cover, not sure for this kernel but the Kobo kernel has code for that)
Is there any progress at that front?
These are the only 2 things (1 for Touch owners) left to make the android system perfect for Glo.

BTW I wonder if the wrong processor clock is responsible for the misalignment of the device's time reference (the normal clock), that happens from time to time but not always...
embryo is offline   Reply With Quote
Old 12-12-2013, 01:38 PM   #221
masterjet
Junior Member
masterjet began at the beginning.
 
Posts: 2
Karma: 10
Join Date: Jan 2012
Device: Kindle 4NT
Quote:
Originally Posted by diogo_abdalla View Post
Thank you a lot! Im actually uasing linux, but I guess the only change is in how to write the image, right?
Download image_writer from repositories or use dd
under root "dd if=~/kobo_image of=/dev/sd(number of your card) bs=1024"
but be carefull, you can mistype and erase your hdd
masterjet is offline   Reply With Quote
Old 12-13-2013, 08:46 AM   #222
aStone
Junior Member
aStone began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Nov 2013
Device: Kobo Glo/AuraHD
Quote:
Originally Posted by dancol90 View Post
I've replaced uboot and hwconfig section with the original mini ones, but it does not work, it stucks with this message:

Code:
Waiting for root device /dev/mmcblk0p1...
I've also tried to change bSysPartType in HW CONFIG section from type3 (the kobo one) to type8 (the one used in your image) but nothing change. For more info you can look in board/freescale/mx50_rdp/ntx_hwconfig.c (line 123) in uboot sources.

I think that the kernel parameters are hard coded in the bootloader, but I have no idea how to change them from sources.

This is the complete serial log:

Spoiler:
Code:
U-Boot 2009.08-dirty-svn ( 8æ 29 2012 - 11:15:18)


CPU:   Freescale i.MX50 family 1.1V at 800 MHz

mx50 pll1: 800MHz

mx50 pll2: 400MHz

mx50 pll3: 216MHz

ipg clock     : 66666666Hz

ipg per clock : 66666666Hz

uart clock    : 24000000Hz

ahb clock     : 133333333Hz

axi_a clock   : 400000000Hz

axi_b clock   : 200000000Hz

weim_clock    : 100000000Hz

ddr clock     : 200000000Hz

esdhc1 clock  : 80000000Hz

esdhc2 clock  : 80000000Hz

esdhc3 clock  : 80000000Hz

esdhc4 clock  : 80000000Hz

Board: MX50 RDP board

Boot Reason: [POR]

Boot Device: SD

I2C:   ready

DRAM:  256 MB

MMC:   FSL_ESDHC: 0, FSL_ESDHC: 1, FSL_ESDHC: 2

*** Warning - bad CRC or MMC, using default environment


In:    serial

Out:   serial

Err:   serial

[_get_sd_number] g_sd_number:2


MMC read: dev # 2, block # 1023, count 1 partition # 0 ... 

1 blocks read: OK


MMC read: dev # 2, block # 1024, count 1 partition # 0 ... 

1 blocks read: OK

zforce read 7 0 (2 bytes)

zforce read 1 0 (2 bytes)

zforce read 2 0 (2 bytes)

zforce read 3 0 (2 bytes)

zforce frame start not found !

zforce frame start not found !

PCB ID is 9

Power key released!!

ram p=70000000,size=268435456


MMC read: dev # 2, block # 18431, count 1 partition # 0 ... 

1 blocks read: OK


MMC read: dev # 2, block # 18432, count 759 partition # 0 ... 

759 blocks read: OK


MMC read: dev # 2, block # 14335, count 1 partition # 0 ... 

1 blocks read: OK


MMC read: dev # 2, block # 14336, count 2228 partition # 0 ... 

2228 blocks read: OK

Kernel RAM visiable size=254M->254M

init TPS65185 power ...

Hit any key to stop autoboot:  1  0 


MMC read: dev # 2, block # 2047, count 1 partition # 0 ... 

1 blocks read: OK

kernel size = 3347004


MMC read: dev # 2, block # 2048, count 6543 partition # 0 ... 

6543 blocks read: OK

hwcfg rootfstype : 2

hwcfg partition type : 7

## Booting kernel from Legacy Image at 70800000 ...

   Image Name:   Linux-2.6.35.3-ga50a7ec-dirty

   Created:      2013-11-23  11:09:35 UTC

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    3262640 Bytes =  3.1 MB

   Load Address: 70008000

   Entry Point:  70008000

   Loading Kernel Image ... OK

OK


Starting kernel ...


Uncompressing Linux... done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 2.6.35.3-ga50a7ec-dirty (marek@marek-Satellite-L300) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #163 PREEMPT Sat Nov 23 12:09:29 CET 2013
CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Freescale MX50 Reference Design Platform
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 64516
Kernel command line: console=ttymxc0,115200 rootwait rw no_console_suspend lpj=3997696 hwcfg_p=0x7ffffe00 hwcfg_sz=512 logo_p=0x7ffa1000 logo_sz=388608 waveform_p=0x7fe8a800 waveform_sz=1140736 mem=254M rootfstype=ext4 root=/dev/mmcblk0p1
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
allocated 1300480 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
Memory: 254MB = 254MB total
Memory: 246688k/246688k available, 13408k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xf9e00000 - 0xffe00000   (  96 MB)
    vmalloc : 0x90000000 - 0xf4000000   (1600 MB)
    lowmem  : 0x80000000 - 0x8fe00000   ( 254 MB)
    pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
    modules : 0x7f000000 - 0x7fe00000   (  14 MB)
      .init : 0x80008000 - 0x80038000   ( 192 kB)
      .text : 0x80038000 - 0x80875000   (8436 kB)
      .data : 0x8089e000 - 0x80903740   ( 406 kB)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:368
MXC GPIO hardware
MXC IRQ initialized
MXC_Early serial console at MMIO 0x53fc0000 (options '115200')
bootconsole [ttymxc0] enabled
Console: colour dummy device 80x30
Calibrating delay loop (skipped) preset value.. 799.53 BogoMIPS (lpj=3997696)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
Initializing cgroup subsys debug
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys blkio
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
i.MX IRAM pool: 128 KB@0x90040000
hwcfg_size_setup() hwcfg_szie=512
hwcfg_p_setup() hwcfg_p=7ffffe00,vaddr=9006ee00,size=512
hwcfg_p_setup() pcba="E50610" !!
CPU is i.MX50 Revision 1.1
[check_hardware_name-329] PCBA ID is 9
Using SDMA I.API
MXC DMA API initialized
IMX usb wakeup probe
IMX usb wakeup probe
bio: create slab <bio-0> at 0
regulator: DCDC_3V15: 3150 mV 
SCSI subsystem initialized
CSPI: mxc_spi-2 probed
Freescale USB OTG Driver loaded, $Revision: 1.55 $
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.23.
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
mc13892 Rev 0.0 FinVer 0 detected
Initializing regulators for mx50 rdp.
regulator: SW1: 600 <--> 1375 mV at 600 mV 
Device spi3.0 probed
[msp430_probe-663] MSP430 firmware version B83A
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
LPMode driver module loaded
Static Power Management for Freescale i.MX5
PM driver module loaded
sdram autogating driver module loaded
Bus freq driver module loaded
mxc_dvfs_core_probe
DVFS driver module loaded
i.MXC CPU frequency driver
DVFS PER driver module loaded
ashmem: initialized
msgmni has been set to 481
alg: No test for stdrng (krng)
cryptodev: driver loaded.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
By setting, SII driver will not be enabled
waveform_size_setup() wf_size=1140736
waveform_p_setup() wf_p=7fe8a800,vaddr=90200800,size=1140736
logo_size_setup() logo_szie=388608
logo_p_setup() logo_p=7ffa1000,vaddr=90100000,size=388608
root_path_setup() rootdev=0,rootpart=1
[epdc_firmware_func]:fw p=90200800,size=1140736
[mxc_epdc_fb_fw_handler-3619] 
drivers/video/mxc/mxc_epdc_fb.c(3662):V220 FPL platform 
fbcvt: 1024x768@60: CVT Name - .786M3
drivers/video/mxc/mxc_epdc_fb.c ******** mxc_epdc_fb ntx_get_battery_vol: 50
fake_s1d13522_parse_epd_cmdline : epd cmdline parse already done .
client0 ,addr=0x68,name=tps65185-1
TPS65185 versions : major=0x1,minor=0x2,version=0x5,RevID=0x65
Serial: MXC Internal UART driver
mxcintuart.0: ttymxc0 at MMIO 0x53fc0000 (irq = 32) is a Freescale i.MX
console [ttymxc0] enabled, bootconsole disabled

console [ttymxc0] enabled, bootconsole disabled
mxcintuart.1: ttymxc1 at MMIO 0x53fbc000 (irq = 31) is a Freescale i.MX

mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 33) is a Freescale i.MX

loop: module loaded

MXC MTD nand Driver 3.0

i.MX GPMI NFC

vcan: Virtual CAN interface driver

Freescale FlexCAN Driver 

FEC Ethernet Driver

PPP generic driver version 2.4.2

PPP Deflate Compression module registered

PPP BSD Compression module registered

PPP MPPE Compression module registered

NET: Registered protocol family 24

tun: Universal TUN/TAP device driver, 1.6

tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci.0: irq 18, io base 0x53f80000

fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2

fsl-ehci fsl-ehci.1: irq 14, io base 0x53f80200

fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

usbcore: registered new interface driver cdc_acm

cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver usbserial

usbserial: USB Serial Driver core

USB Serial support registered for GSM modem (1-port)

usbcore: registered new interface driver option

option: v0.7.2:USB Driver for GSM modems

ARC USBOTG Device Controller driver (1 August 2005)

Android usb driver initialize

android_usb gadget: android_usb ready

fsl-usb2-udc: bind to driver android_usb 

android gadget: register function adb

android gadget: register function usb_mass_storage

android gadget: register function rndis

rndis_pdata null in rndis_function_bind_config

android_usb gadget: usb_mass_storage, version: 2009/09/11

android_usb gadget: Number of LUNs=2

 lun0: LUN: removable file: (no medium)

 lun1: LUN: removable file: (no medium)

mice: PS/2 mouse device common for all mice

MXC keypad loaded

input: mxckpd as /devices/virtual/input/input0

input: mxc_power_key as /devices/virtual/input/input1

PMIC powerkey probe

[__zForce_ir_touch_init-104] zForce controller with v2 command sets.

[zForce_ir_touch_probe-572] Set touch resolution 600x800

input: zForce-ir-touch as /devices/virtual/input/input2

[zForce_ir_touch_recv_data-178] command BootComplete (0)...

pmic rtc probe start

using rtc device, mc13892_rtc, for alarms

pmic_rtc mc13892_rtc.1: rtc core: registered mc13892_rtc as rtc0

pmic rtc probe succeed

i2c /dev entries driver

IR NEC protocol handler initialized

IR RC5(x) protocol handler initialized

IR RC6 protocol handler initialized

IR JVC protocol handler initialized

IR Sony protocol handler initialized

Linux video capture interface: v2.00

usbcore: registered new interface driver uvcvideo

USB Video Class driver (v0.1.0)

APM Battery Driver

MXC WatchDog Driver 2.0

device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised: dm-devel@redhat.com

Bluetooth: Virtual HCI driver ver 1.3

Bluetooth: HCI UART driver ver 2.2

Bluetooth: HCIATH3K protocol initialized

Bluetooth: Generic Bluetooth USB driver ver 0.6

usbcore: registered new interface driver btusb

[drivers/mxc/pmic/mc13892/pmic_battery.c-1024] pmic_battery_probe...

mxsdhci: MXC Secure Digital Host Controller Interface driver

mxsdhci: MXC SDHCI Controller Driver. 

mmc0: SDHCI detect irq 0 irq 3 INTERNAL DMA

mxsdhci: MXC SDHCI Controller Driver. 

[zForce_ir_touch_recv_data-203] firmware version 0001 0000 0000 0001 

mmc1: SDHCI detect irq 0 irq 2 INTERNAL DMA

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

logger: created 64K log 'log_main'

logger: created 256K log 'log_events'

logger: created 64K log 'log_radio'

logger: created 64K log 'log_system'

Cirrus Logic CS42888 ALSA SoC Codec Driver

No device for DAI imx-ssi-1-0

No device for DAI imx-ssi-1-1

No device for DAI imx-ssi-2-0

No device for DAI imx-ssi-2-1

No device for DAI imx-spdif-dai

ALSA device list:

  No soundcards found.

nf_conntrack version 0.5.0 (3854 buckets, 15416 max)

IPv4 over IPv4 tunneling driver

GRE over IPv4 tunneling driver

ip_tables: (C) 2000-2006 Netfilter Core Team

TCP cubic registered

NET: Registered protocol family 10

IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

NET: Registered protocol family 15

can: controller area network core (rev 20090105 abi 8)

NET: Registered protocol family 29

can: raw protocol (rev 20090105)

can: broadcast manager protocol (rev 20090105 t)

[k_wait_update_complete]waitupdate ret=-22,4294937479->4294937479


========== upd_data.update_region( l, t, w, h ) = ( 0, 0, 800, 600 )============

Bluetooth: L2CAP ver 2.14

Bluetooth: L2CAP socket layer initialized

Bluetooth: SCO (Voice Link) ver 0.6

Bluetooth: SCO socket layer initialized

Bluetooth: RFCOMM TTY layer initialized

Bluetooth: RFCOMM socket layer initialized

Bluetooth: RFCOMM ver 1.11

Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Bluetooth: BNEP filters: protocol multicast

Bluetooth: HIDP (Human Interface Emulation) ver 1.2

L2TP core driver, V2.0

PPPoL2TP kernel driver, V2.0

VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2

TPS65185 temprature data = 0x17,23

[PROGRESS_BAR-2912] No progess ...

read_time: 113/10/24 21:21:52

pmic_rtc mc13892_rtc.1: setting system clock to 2013-11-24 21:21:52 UTC (1385328112)

Waiting for root device /dev/mmcblk0p1...

I think root device would be /dev/block/mmcblk0p2...
Did you try it?
aStone is offline   Reply With Quote
Old 12-13-2013, 04:56 PM   #223
phoinikos
Junior Member
phoinikos began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Dec 2013
Device: Kobo Mini
Quote:
Originally Posted by aStone View Post


I think root device would be /dev/block/mmcblk0p2...
Did you try it?

According to the post below, the issue could be with

Quote:
Originally Posted by MarekGibek View Post

I think there are a few important things you must have to run Android. Especially this:

"/mmcblk0p2 rootfstype=ext4 rootwait rw noinitrd init=/init video=mxc_elcdif_fbff"
I am still hoping to see Android on Kobo Mini.
phoinikos is offline   Reply With Quote
Old 12-14-2013, 05:13 PM   #224
neil.bartlett
Junior Member
neil.bartlett began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Dec 2013
Device: kobo touch
Quote:
Originally Posted by stasys View Post
If your card is bigger than 2GB, you can expand partition which is Fat32 to fill all your card space with this program: http://www.partitionwizard.com/free-...n-manager.html
Thx for the instructions.

So simply extend the FAT32 partition to fill the SD card ?

What about the "android system" and "android data" ext4 filesystems ? Do these need to be need to be resized too?

Thx
Neil
neil.bartlett is offline   Reply With Quote
Old 12-15-2013, 04:43 AM   #225
stasys
Zealot
stasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enoughstasys will become famous soon enough
 
Posts: 147
Karma: 598
Join Date: Aug 2007
Device: Kobo Glo, Paperwhite
I didn't touch them. Maybe one with Linux knowledge can do that, but I'm windows guy
stasys is offline   Reply With Quote
Reply

Tags
android, glo, kobo, shine, tolino

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Glo Synchronizing my own books between Kobo Glo and Kobo Android ploum Kobo Reader 16 08-15-2014 11:39 PM
kobo glo / android phone not detected danieldo Devices 2 02-02-2013 01:28 PM
Glo Screen durability of the glo..is it better than the Nook Glo?? Tony1988 Kobo Reader 4 01-10-2013 08:38 PM
Glo Can kobo glo run android app such as nook glo? suspect Kobo Developer's Corner 1 12-29-2012 12:25 AM
Released 14 HoneyComb ROM MOD for Android OS 1.6 /Android OS 2.1 HCV13.0 B20 tipstir Android Devices 0 05-20-2011 03:59 AM


All times are GMT -4. The time now is 01:14 AM.


MobileRead.com is a privately owned, operated and funded community.