Quad Board auto reset probrlm?

Discussion in 'Troubleshooting' started by Linus, Nov 7, 2013.

  1. Linus

    Linus New Member

    Joined:
    Oct 23, 2013
    Messages:
    5
    Likes Received:
    0
    Hi,
    Why my quad board always auto reset (atuo reboot)?
    My quad board used UDOO power adapter(12V 2A).
    OS: android(update to ver1.1)(ver 1.0 the same)

    PS: Dual board no this probelm.

    thanks~
     
  2. DracoLlasa

    DracoLlasa UDOOer

    Joined:
    Oct 15, 2013
    Messages:
    419
    Likes Received:
    3
    does the same thing happen when running Linaro?
    Does it happen when there is no activity? when it just sits idle?
    Does it happen when it is active running apps or browsing the web?
    Is there any common trigger or time frame or is it random... 5 mins after start up, or 30 minutes regardless of you doing something or nothing it just reboots?

    I haven't seent his specific bug reported, but we do know that the current Android build is very buggy and a new release is due out from UDOO any day now
     
  3. Linus

    Linus New Member

    Joined:
    Oct 23, 2013
    Messages:
    5
    Likes Received:
    0
    Hi Draco~
    No running any program and apps.
    Restart trigger is random, (5 sec,10 sec,1 min,any time...)
    Even occurs when initial boot at standby mode(standby to unlock mode).
    A trigger would have been repeated restarts.
    :? :? :?
     
  4. DracoLlasa

    DracoLlasa UDOOer

    Joined:
    Oct 15, 2013
    Messages:
    419
    Likes Received:
    3
    did you create your SD card or did it come with the Board?
    If you created the SD card are you sure you are using the latest 1.2 version?
    Have you applied any updates? 2 main patches have been released, one official(that you should have) and one unofficial (which doesn't address anything like this
     
  5. Linus

    Linus New Member

    Joined:
    Oct 23, 2013
    Messages:
    5
    Likes Received:
    0

    I just try "udoo_quad_android_1.1.zip" and "udoo_quad_android_1.0.zip" image file from UDOO. Is the same.(means restart)

    I haven't applied any updates.
     
  6. delba

    delba Administrator Staff Member

    Joined:
    May 8, 2013
    Messages:
    1,063
    Likes Received:
    9
    Linus,

    have you tried ubuntu 1.2 image? it returns the same problem?
    We updated the android image (still called 1.1) friday, if you didn't reflash it by then i suggest you to redo the procedure.

    Let me know so i can give you more specific information.

    Cheers
     
  7. Linus

    Linus New Member

    Joined:
    Oct 23, 2013
    Messages:
    5
    Likes Received:
    0
    Hi~
    The Quad board run Linaro Ubuntu 11.10(udoo_quad_ubuntu_1.3.zip) no restart problem.
    But run Android(try new 1.1 image) still happen random auto restart problem.
    I I also tried another power adapter(12V 3A) and another mouse the problem still here.
    What do I need to try ?
    thanks!
     
  8. delba

    delba Administrator Staff Member

    Joined:
    May 8, 2013
    Messages:
    1,063
    Likes Received:
    9
    Linus,

    i thought was a watchdog problem (hardware) but if with ubuntu 1.3 UDOO doesn't auto-restart and with Android 1.1 it does, the problem is somewhere else. We never experienced anything like that with android, we'll verify the issue and let you know asap.

    Cheers
     
  9. andcmp

    andcmp New Member

    Joined:
    May 8, 2013
    Messages:
    161
    Likes Received:
    0
    Do you have the ethernet cable plugged in when the board reboots?
     
  10. Linus

    Linus New Member

    Joined:
    Oct 23, 2013
    Messages:
    5
    Likes Received:
    0
    Hi andcmp~
    No plugged in ethernet cable.
    Quad board just plugged one mouse and HDMI cable.
     
  11. eric

    eric New Member

    Joined:
    Nov 21, 2013
    Messages:
    26
    Likes Received:
    0
    I'm having a similar issue. It seems to have just started today.
    I've had my quad now for 4 days, and I think it's been fine for those days, but now it seems to restart often, at very random intervals.
    I'm running the latest version posted in the downloads section.
    I don't seem to recognize a trigger, it's sitting idle. I have been playing with the Arduino side of things recently, attempting to get the ADK working, but other than that Android isn't doing anything.
     
  12. tararasss

    tararasss New Member

    Joined:
    Nov 29, 2013
    Messages:
    10
    Likes Received:
    0
    Got charge quad board thanks.
    constant rebooting problem on all versions of android. restarts at random intervals for no reason, and yactoo just do not boot!
    Normally only works on Ubuntu
    What to do?
     
  13. Lifeboat_Jim

    Lifeboat_Jim New Member

    Joined:
    Sep 16, 2013
    Messages:
    399
    Likes Received:
    1
    If it works fine on Ubuntu then it's not a hardware related issue.

    Sounds like you need to download Android images again, check the SHA-1 checksum, and burn it to SD Card and try again. If it still doesn't work, try burning the card again etc. There are many reports of: a) bad download b) bad card writing - which repeated attempts fix.
     
  14. Lifeboat_Jim

    Lifeboat_Jim New Member

    Joined:
    Sep 16, 2013
    Messages:
    399
    Likes Received:
    1
    Has anything changed on day 3 or 4? EG did you change the SD Card content (like trying Ubuntu 12.04 which came out yesterday) as you said you are 'running the latest version'.
     
  15. tararasss

    tararasss New Member

    Joined:
    Nov 29, 2013
    Messages:
    10
    Likes Received:
    0

    all done by the description, and still does not boot android
    sometimes nothing at all happens when the power supply, and sometimes restarts on window launch
     
  16. tararasss

    tararasss New Member

    Joined:
    Nov 29, 2013
    Messages:
    10
    Likes Received:
    0
    SHA-1 are the same
    giving otg. what do I do? then reboot or blank screen

    U-Boot 2009.08-svn24 (Nov 05 2013 - 03:04:40)

    CPU: Freescale i.MX6 family TO1.2 at 792 MHz
    Thermal sensor with ratio = 180
    Temperature: 32 C, calibration data 0x5744e369
    mx6q pll1: 792MHz
    mx6q pll2: 528MHz
    mx6q pll3: 480MHz
    mx6q pll8: 50MHz
    ipg clock : 66000000Hz
    ipg per clock : 66000000Hz
    uart clock : 80000000Hz
    cspi clock : 60000000Hz
    ahb clock : 132000000Hz
    axi clock : 264000000Hz
    emi_slow clock: 132000000Hz
    ddr clock : 528000000Hz
    usdhc1 clock : 198000000Hz
    usdhc2 clock : 198000000Hz
    usdhc3 clock : 198000000Hz
    usdhc4 clock : 198000000Hz
    nfc clock : 24000000Hz
    Board: i.MX6Q-UDOO: unknown-board Board: 0x63012 [POR]
    Boot Device: NOR
    I2C: ready
    DRAM: 1 GB
    MMC: FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3
    *** Warning - bad CRC or MMC, using default environment

    In: serial
    Out: serial
    Err: serial
    Net: got MAC address from IIM: 00:c0:08:88:1b:12
    FEC0 [PRIME]
    Hit any key to stop autoboot: 0
    kernel @ 10808000 (4305072)
    ramdisk @ 11800000 (186957)
    kernel cmdline:
    use uboot command line:
    console=ttymxc1,115200 init=/init video=mxcfb0:dev=hdmi,1920x1080M@60,if =RGB24,bpp=32 video=mxcfb1:eek:ff video=mxcfb2:eek:ff fbmem=28M vmalloc=400M androidbo ot.console=ttymxc1 androidboot.hardware=freescale mem=1024M

    Starting kernel ...

    Initializing cgroup subsys cpuset
    Initializing cgroup subsys cpu
    Linux version 3.0.35-svn24 (udoo@ubuntu) (gcc version 4.6.x-google 20120106 (pre release) (GCC) ) #5 PREEMPT Mon Nov 4 02:58:07 PST 2013
    CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine: i.Mx6 UDOO Board
    Ignoring unrecognised tag 0x41000901
    Memory policy: ECC disabled, Data cache writeback
    CPU identified as i.MX6Q, silicon rev 1.2
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 223232
    Kernel command line: console=ttymxc1,115200 init=/init video=mxcfb0:dev=hdmi,192 0x1080M@60,if=RGB24,bpp=32 video=mxcfb1:eek:ff video=mxcfb2:eek:ff fbmem=28M vmalloc=4 00M androidboot.console=ttymxc1 androidboot.hardware=freescale mem=1024M
    PID hash table entries: 2048 (order: 1, 8192 bytes)
    Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    Memory: 640MB 240MB = 880MB total
    Memory: 879172k/879172k available, 169404k reserved, 491520K highmem
    Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000 ( 4 kB)
    fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
    DMA : 0xfbe00000 - 0xffe00000 ( 64 MB)
    vmalloc : 0xd9800000 - 0xf2000000 ( 392 MB)
    lowmem : 0xc0000000 - 0xd9000000 ( 400 MB)
    pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
    modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
    .init : 0xc0008000 - 0xc0036000 ( 184 kB)
    .text : 0xc0036000 - 0xc0b53f58 (11384 kB)
    .data : 0xc0b54000 - 0xc0ba2880 ( 315 kB)
    .bss : 0xc0ba28a4 - 0xc0ccfae8 (1205 kB)
    Preemptible hierarchical RCU implementation.
    NR_IRQS:624
    MXC GPIO hardware
    sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
    arm_max_freq=1GHz
    MXC_Early serial console at MMIO 0x21e8000 (options '115200')
    bootconsole [ttymxc1] enabled
    Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
    pid_max: default: 32768 minimum: 301
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
    print_constraints: dummy:
    NET: Registered protocol family 16
    print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal
    print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
    print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
    print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
    print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
    print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
    ####Called set_gpios_direction
    failed to get MX6_IO_MICRO: -16
    Resetting ethernet physical layer.
    hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
    hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
    hw-breakpoint: maximum watchpoint size is 4 bytes.
    L310 cache controller enabled
    l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size: 1048576 B
    bio: create slab <bio-0> at 0
    print_constraints: vmmc: 3300 mV
    vgaarb: loaded
    SCSI subsystem initialized
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    Freescale USB OTG Driver loaded, $Revision: 1.55 $
    imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
    imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
    mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed
    mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a
    MIPI CSI2 driver module loaded
    Advanced Linux Sound Architecture Driver Version 1.0.24.
    Bluetooth: Core ver 2.16
    NET: Registered protocol family 31
    Bluetooth: HCI device and connection manager initialized
    Bluetooth: HCI socket layer initialized
    Bluetooth: L2CAP socket layer initialized
    Bluetooth: SCO socket layer initialized
    cfg80211: Calling CRDA to update world regulatory domain
    i2c-core: driver [max17135] using legacy suspend method
    i2c-core: driver [max17135] using legacy resume method
    Switching to clocksource mxc_timer1
    NET: Registered protocol family 2
    IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
    TCP established hash table entries: 65536 (order: 7, 524288 bytes)
    TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
    TCP: Hash tables configured (established 65536 bind 65536)
    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 named UNIX socket transport module.
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    Unpacking initramfs...
    Freeing initrd memory: 180K
    PMU: registered new PMU device of type 0
    Static Power Management for Freescale i.MX6
    wait mode is enabled for i.MX6
    cpaddr = d9880000 suspend_iram_base=d98f0000
    PM driver module loaded
    IMX usb wakeup probe
    add wake up source irq 75
    IMX usb wakeup probe
    cpu regulator mode:ldo_enable
    i.MXC CPU frequency driver
    highmem bounce pool size: 64 pages
    ashmem: initialized
    JFFS2 version 2.2. (NAND) В© 2001-2006 Red Hat, Inc.
    fuse init (API version 7.16)
    msgmni has been set to 757
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    MIPI DSI driver module loaded
    mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi
    mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1
    fbcvt: 1920x1080@60: CVT Name - 2.073M9
    imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines
    imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
    mxc_sdc_fb mxc_sdc_fb.1: Can't get fb option for mxcfb1!
    mxc_sdc_fb mxc_sdc_fb.2: Can't get fb option for mxcfb2!
    imx-sdma imx-sdma: loaded firmware 1.1
    imx-sdma imx-sdma: initialized
    fbcvt: 1920x1080@60: CVT Name - 2.073M9
    Serial: IMX driver
    imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
    imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
    console [ttymxc1] enabled, bootconsole disabled
    console [ttymxc1] enabled, bootconsole disabled
    imx-uart.3: ttymxc3 at MMIO 0x21f0000 (irq = 61) is a IMX
    loop: module loaded
    request BOSSA_CLK IRQ
    registering IRQ 419 for BOSSAC Arduino erase/reset operation
    vcan: Virtual CAN interface driver
    CAN device driver interface
    flexcan netdevice driver
    FEC Ethernet Driver
    fec_enet_mii_bus: probed
    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
    PPTP driver version 0.8.5
    usbcore: registered new interface driver rt2800usb
    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 75, io base 0x02184000
    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
    add wake up source irq 72
    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 72, io base 0x02184200
    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: 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
    USB Serial support registered for Qualcomm USB modem
    usbcore: registered new interface driver qcserial
    ARC USBOTG Device Controller driver (1 August 2005)
    android_usb gadget: Mass Storage Function, version: 2009/09/11
    android_usb gadget: Number of LUNs=1
    lun0: LUN: removable file: (no medium)
    Gadget Android: controller 'fsl-usb2-udc' not recognized
    android_usb gadget: android_usb ready
    Suspend udc for OTG auto detect
    fsl-usb2-udc: bind to driver android_usb
    mousedev: PS/2 mouse device common for all mice
    i2c-core: driver [isl29023] using legacy suspend method
    i2c-core: driver [isl29023] using legacy resume method
    using rtc device, snvs_rtc, for alarms
    snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
    i2c /dev entries driver
    Linux video capture interface: v2.00
    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16
    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17
    i2c-core: driver [mag3110] using legacy suspend method
    i2c-core: driver [mag3110] using legacy resume method
    imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
    device-mapper: uevent: version 1.0.3
    device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) 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
    sdhci: Secure Digital Host Controller Interface driver
    sdhci: Copyright(c) Pierre Ossman
    mmc0: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
    mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
    VPU initialized
    mxc_asrc registered
    revserved_memory_account:viv_gpu registerd
    Thermal calibration data is 0x5744e369
    Thermal sensor with ratio = 180
    Anatop Thermal registered as thermal_zone0
    anatop_thermal_probe: default cooling device is cpufreq!
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    logger: created 256K log 'log_main'
    usb 2-1: new high speed USB device number 2 using fsl-ehci
    logger: created 256K log 'log_events'
    logger: created 256K log 'log_radio'
    logger: created 256K log 'log_system'
    usbcore: registered new interface driver snd-usb-audio
    mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
    asoc: mxc-hdmi-soc <-> imx-hdmi-soc-dai.0 mapping ok
    ALSA device list:
    #0: imx-hdmi-soc
    Netfilter messages via NETLINK v0.30.
    nf_conntrack version 0.5.0 (13739 buckets, 54956 max)
    ctnetlink v0.93: registering with nfnetlink.
    NF_TPROXY: Transparent proxy support initialized, version 4.1.0
    NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
    xt_time: kernel timezone is -0000
    IPv4 over IPv4 tunneling driver
    GRE over IPv4 demultiplexor driver
    ip_tables: (C) 2000-2006 Netfilter Core Team
    arp_tables: (C) 2002 David S. Miller
    TCP cubic registered
    NET: Registered protocol family 10
    ip6_tables: (C) 2000-2006 Netfilter Core Team
    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)
    mmc0: new high speed SDHC card at address aaaa
    Bluetooth: RFCOMM TTY layer initialized
    mmcblk0: mmc0:aaaa SU08G 7.40 GiB
    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
    L2TP IP encapsulation support (L2TPv3)
    L2TP netlink interface
    L2TP ethernet pseudowire support (L2TPv3)
    lib80211: common routines for IEEE802.11 drivers
    hub 2-1:1.0: USB hub found
    mmcblk0: p1 p2 p3 < p5 p6 p7 p8 > p4
    hub 2-1:1.0: 4 ports detected
    VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
    MMDC: unable to set irq affinity irq=139,
    Bus freq driver module loaded
    Bus freq driver Enabled
    mxc_dvfs_core_probe
    DVFS driver module loaded
    snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:01 UTC (1)
    Freeing init memory: 184K
    input: A4TECH USB Device as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.1/2-1.1:1.0/input/input0
    generic-usb 0003:09DA:054F.0001: input,hidraw0: USB HID v1.11 Keyboard [A4TECH USB Device] on usb-fsl-ehci.1-1.1/input0
    input: A4TECH USB Device as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.1/2-1.1:1.1/input/input1
    generic-usb 0003:09DA:054F.0002: input,hidraw1: USB HID v1.11 Mouse [A4TECH USB Device] on usb-fsl-ehci.1-1.1/input1
    usb 2-1.3: new high speed USB device number 4 using fsl-ehci
    init: cannot find '/system/bin/ingsvcd', disabling 'ing'
    android_usb: already disabled
    android_usb: already disabled
    mtp_bind_config
    adb_bind_config
    adb_open
    root@android:/ # warning: `zygote' uses 32-bit capabilities (legacy support in use)
    request_suspend_state: wakeup (3->0) at 14478501670 (1970-01-02 00:00:04.528560333 UTC)
    eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:06, irq=-1)
    Warning: Product ID of physical layer not recognized [id = 0x1622 unknown]
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    acc_open
    acc_release
     
  17. tararasss

    tararasss New Member

    Joined:
    Nov 29, 2013
    Messages:
    10
    Likes Received:
    0
    я заново скачивал образы, безрезультатно
    я пробовал 3 шт. sd card , безрезультатно
    я пробовал 2 шт. компьютеров , безрезультатно
    Android без перерыва перезагружается
    Что мне делать?
    Как из источников собрать систему самому? (очень подробное описание)

    I re-downloaded the images, to no avail
    I tried 3 pcs. sd card, to no avail
    I tried 2 pcs. computers, to no avail
    Android reboots without interruption
    What do I do?
    How to assemble a system from the sources yourself? (very detailed description)
     
  18. eric

    eric New Member

    Joined:
    Nov 21, 2013
    Messages:
    26
    Likes Received:
    0
    I just got my new class 10 micro SD card for my UDOO and am still having this issue. The only reason I bought this thing is for Android, and it's currently unusable, it keep rebooting at random intervals.
     
  19. DracoLlasa

    DracoLlasa UDOOer

    Joined:
    Oct 15, 2013
    Messages:
    419
    Likes Received:
    3
    At this point i might be best to open an actual support ticket with UDOO if you havent already
    They have a new ticketing system, you can find the link in my signature.
     
  20. delba

    delba Administrator Staff Member

    Joined:
    May 8, 2013
    Messages:
    1,063
    Likes Received:
    9
    That's my advise as well. Open a new ticket defining as help topic "Technical Support" explaining your problem.
     

Share This Page