Guest samjam Posted March 13, 2013 Report Posted March 13, 2013 Anyone know which link2sd I app should be using on this ROM?
Guest dalyer Posted March 13, 2013 Report Posted March 13, 2013 The latest? It works with CM ROMs now.
Guest samjam Posted March 13, 2013 Report Posted March 13, 2013 I'm getting lots of hangs. dmesg shows: root@android:/data/data/com.teslacoilsw.quicksshd/home # dmesg root@android:/data/data/com.teslacoilsw.quicksshd/home # dmesg ut ... <3>[90, mmcqd/1] [ 559.829968] mmcblk1: error -110 transferring data, sector 25590, nr 1, cmd response 0x900, card status 0x0 <3>[90, mmcqd/1] [ 559.830783] end_request: I/O error, dev mmcblk1, sector 25590 <3>[1186, MediaScannerSer] [ 559.835776] FAT-fs (mmcblk1p1): Directory bread(block 17398) failed <3>[90, mmcqd/1] [ 559.836373] mmc1: DMA channel flushed (0x80000004) <3>[90, mmcqd/1] [ 559.836471] Flush data: 0000c003 2bda0000 00000000 00400040 00080008 00000003 <3>[90, mmcqd/1] [ 559.836981] mmcblk1: timed out sending r/w cmd command, card status 0x400b00 <3>[90, mmcqd/1] [ 559.837061] mmcblk1: command error, retrying timeout <3>[164, SurfaceFlinger] [ 560.038171] mmc1: CMD17: Data timeout <6>[164, SurfaceFlinger] [ 560.038258] mmc1: SDCC PWR is ON <6>[164, SurfaceFlinger] [ 560.038378] mmc1: SDCC clks are ON, MCLK rate=49152000 <6>[164, SurfaceFlinger] [ 560.038446] mmc1: SDCC irq is enabled <6>[164, SurfaceFlinger] [ 560.038514] ===== SDCC-CORE: Register Dumps @base=0xe081a000 ===== <6>[164, SurfaceFlinger] [ 560.038601] Reg=0x00: 0x00000001, 0x00009b00, 0x000063f7, 0x00001451. <6>[164, SurfaceFlinger] [ 560.038686] Reg=0x10: 0x00000011, 0x00000900, 0x00000000, 0x00000000. <6>[164, SurfaceFlinger] [ 560.038773] Reg=0x20: 0x00000000, 0x00960000, 0x00000200, 0x0000200b. <6>[164, SurfaceFlinger] [ 560.038858] Reg=0x30: 0x00000200, 0x00000000, 0x00000000, 0x008001ff. <6>[164, SurfaceFlinger] [ 560.038941] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000. <6>[164, SurfaceFlinger] [ 560.039024] Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000. <6>[164, SurfaceFlinger] [ 560.039108] Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000. <6>[164, SurfaceFlinger] [ 560.039188] mmc1: ADM mode: busy=1, chnl=10, crci=6 <6>[164, SurfaceFlinger] [ 560.039263] mmc1: xfer_size=512, data_xfered=0, xfer_remain=512 <6>[164, SurfaceFlinger] [ 560.039341] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0 <3>[164, SurfaceFlinger] [ 560.039473] mmc1: DMA channel flushed (0x80000004) <3>[164, SurfaceFlinger] [ 560.039558] Flush data: 0000c003 2bda0000 00000000 00400040 00080008 00000003 <3>[90, mmcqd/1] [ 560.039833] mmcblk1: error -110 transferring data, sector 25591, nr 1, cmd response 0x900, card status 0x0 <3>[90, mmcqd/1] [ 560.039929] end_request: I/O error, dev mmcblk1, sector 25591 <3>[1186, MediaScannerSer] [ 560.042294] FAT-fs (mmcblk1p1): Directory bread(block 17399) failed <3>[90, mmcqd/1] [ 560.042848] mmc1: DMA channel flushed (0x80000004) <3>[90, mmcqd/1] [ 560.042951] Flush data: 0000c003 2bda0000 00000000 00400040 00080008 00000003 <3>[90, mmcqd/1] [ 560.043376] mmcblk1: timed out sending r/w cmd command, card status 0x400b00 <3>[90, mmcqd/1] [ 560.043456] mmcblk1: command error, retrying timeout <3>[574, dhd_dpc] [ 560.243621] mmc1: CMD17: Data timeout <6>[574, dhd_dpc] [ 560.243703] mmc1: SDCC PWR is ON <6>[574, dhd_dpc] [ 560.243818] mmc1: SDCC clks are ON, MCLK rate=49152000 <6>[574, dhd_dpc] [ 560.243884] mmc1: SDCC irq is enabled <6>[574, dhd_dpc] [ 560.243951] ===== SDCC-CORE: Register Dumps @base=0xe081a000 ===== <6>[574, dhd_dpc] [ 560.244031] Reg=0x00: 0x00000001, 0x00009b00, 0x000063f8, 0x00001451. <6>[574, dhd_dpc] [ 560.244104] Reg=0x10: 0x00000011, 0x00000900, 0x00000000, 0x00000000. <6>[574, dhd_dpc] [ 560.244179] Reg=0x20: 0x00000000, 0x00960000, 0x00000200, 0x0000200b. <6>[574, dhd_dpc] [ 560.244251] Reg=0x30: 0x00000200, 0x00000000, 0x00000000, 0x008001ff. <6>[574, dhd_dpc] [ 560.244323] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000. <6>[574, dhd_dpc] [ 560.244394] Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000. <6>[574, dhd_dpc] [ 560.244464] Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000. <6>[574, dhd_dpc] [ 560.244533] mmc1: ADM mode: busy=1, chnl=10, crci=6 <6>[574, dhd_dpc] [ 560.244594] mmc1: xfer_size=512, data_xfered=0, xfer_remain=512 <6>[574, dhd_dpc] [ 560.244663] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0 <3>[574, dhd_dpc] [ 560.244778] mmc1: DMA channel flushed (0x80000004) <3>[574, dhd_dpc] [ 560.244851] Flush data: 0000c003 2bda0000 00000000 00400040 00080008 00000003 <3>[90, mmcqd/1] [ 560.245443] mmcblk1: error -110 transferring data, sector 25592, nr 1, cmd response 0x900, card status 0x0 <3>[90, mmcqd/1] [ 560.248189] end_request: I/O error, dev mmcblk1, sector 25592 <3>[1186, MediaScannerSer] [ 560.252509] FAT-fs (mmcblk1p1): Directory bread(block 17400) failed <3>[90, mmcqd/1] [ 560.253069] mmc1: DMA channel flushed (0x80000004) <3>[90, mmcqd/1] [ 560.253181] Flush data: 0000c003 2bda0000 00000000 00400040 00080008 00000003 <3>[90, mmcqd/1] [ 560.253696] mmcblk1: timed out sending r/w cmd command, card status 0x400b00 <3>[90, mmcqd/1] [ 560.253796] mmcblk1: command error, retrying timeout <3>[574, dhd_dpc] [ 560.453973] mmc1: CMD17: Data timeout <6>[574, dhd_dpc] [ 560.454053] mmc1: SDCC PWR is ON <6>[574, dhd_dpc] [ 560.454161] mmc1: SDCC clks are ON, MCLK rate=49152000 <6>[574, dhd_dpc] [ 560.454218] mmc1: SDCC irq is enabled <6>[574, dhd_dpc] [ 560.454276] ===== SDCC-CORE: Register Dumps @base=0xe081a000 ===== <6>[574, dhd_dpc] [ 560.454351] Reg=0x00: 0x00000001, 0x00009b00, 0x000063f9, 0x00001451. <6>[574, dhd_dpc] [ 560.454426] Reg=0x10: 0x00000011, 0x00000900, 0x00000000, 0x00000000. <6>[574, dhd_dpc] [ 560.454501] Reg=0x20: 0x00000000, 0x00960000, 0x00000200, 0x0000200b. <6>[574, dhd_dpc] [ 560.454576] Reg=0x30: 0x00000200, 0x00000000, 0x00000000, 0x008001ff. <6>[574, dhd_dpc] [ 560.454648] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000. <6>[574, dhd_dpc] [ 560.454719] Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000. <6>[574, dhd_dpc] [ 560.454791] Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000. <6>[574, dhd_dpc] [ 560.454861] mmc1: ADM mode: busy=1, chnl=10, crci=6 <6>[574, dhd_dpc] [ 560.454924] mmc1: xfer_size=512, data_xfered=0, xfer_remain=512 <6>[574, dhd_dpc] [ 560.454993] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0 <3>[574, dhd_dpc] [ 560.455113] mmc1: DMA channel flushed (0x80000004) <3>[574, dhd_dpc] [ 560.455186] Flush data: 0000c003 2bda0000 00000000 00400040 00080008 00000003 <3>[90, mmcqd/1] [ 560.459634] mmcblk1: error -110 transferring data, sector 25593, nr 1, cmd response 0x900, card status 0x0 <3>[90, mmcqd/1] [ 560.461464] end_request: I/O error, dev mmcblk1, sector 25593 <3>[1186, MediaScannerSer] [ 560.472723] FAT-fs (mmcblk1p1): Directory bread(block 17401) failed <3>[90, mmcqd/1] [ 560.473286] mmc1: DMA channel flushed (0x80000004) <3>[90, mmcqd/1] [ 560.473393] Flush data: 0000c003 2bda0000 00000000 00400040 00080008 00000003 <3>[90, mmcqd/1] [ 560.473834] mmcblk1: timed out sending r/w cmd command, card status 0x400b00 <3>[90, mmcqd/1] [ 560.473916] mmcblk1: command error, retrying timeout root@android:/data/data/com.teslacoilsw.quicksshd/home # however as far as I can see nothing is mounted on mmcblk1 Maybe that is my (new!) (sandisk!) sd card
Guest samjam Posted March 13, 2013 Report Posted March 13, 2013 So I erase system again, install link2int, install gapps and reboot, and see how it goes. My SD card works fine on my laptop, but seems to cause trouble here
Guest dalyer Posted March 13, 2013 Report Posted March 13, 2013 Maybe format it (and partition align?) it again:
Guest Manos Aristeidopoulos Posted March 13, 2013 Report Posted March 13, 2013 Really Great job, I am using the rom without any problems for now! Android 4.2 for our G300 Amazing!
Guest pekahk Posted March 13, 2013 Report Posted March 13, 2013 Im not sure if I have the latest gapps installed .. is there any way to check it ? If I install the gapps later .. do I have to wipe something or will I miss something after I install the gapps ?????
Guest dalyer Posted March 13, 2013 Report Posted March 13, 2013 The original post in this thread says: Downloads: ROM available on my GetCM, which allows for OTA updates. Check out "CyanogenMod updates" in the "About phone" menu.ROM: http://getcm.thebron...m/?device=u8815Google apps (12/12/2012): http://goo.im/gapps/...1212-signed.zip goo.im has a later version:http://goo.im/gapps I presume that it's OK to install this but don't know for sure. You might be able to tell what version you have installed by cross checking individual gapps app versions in Manage Apps against what's in the goo.im gapps release notes/change logs. I don't know about wiping etc. but would be inclined to clear cache/data for all gapps just in case. I'm sure that somebody else will know more about this than me! :blush:
Guest Dazzozo Posted March 13, 2013 Report Posted March 13, 2013 I don't update the gapps link until a new build.
Guest samjam Posted March 13, 2013 Report Posted March 13, 2013 I don't think this is right <6>[1, swapper] [ 0.844411] s5k5ca.c: i2c probe ok <3>[0, swapper] [ 0.936934] qup_i2c qup_i2c.0: QUP: I2C status flags :0x1363c8, irq:34 <3>[1, swapper] [ 0.937001] qup_i2c qup_i2c.0: I2C slave addr:0x2d not connected <3>[0, swapper] [ 0.937159] qup_i2c qup_i2c.0: QUP: I2C status flags :0x1363c8, irq:34 <3>[1, swapper] [ 0.937211] qup_i2c qup_i2c.0: I2C slave addr:0x2d not connected <3>[0, swapper] [ 0.937361] qup_i2c qup_i2c.0: QUP: I2C status flags :0x1363c8, irq:34 <3>[1, swapper] [ 0.937411] qup_i2c qup_i2c.0: I2C slave addr:0x2d not connected <6>[1, swapper] [ 0.937443] s5k5ca.c: s5k5ca_i2c_txdata faild <6>[1, swapper] [ 0.937469] s5k5ca.c: i2c_write_w failed, addr = 0x10, val = 0x1! <6>[1, swapper] [ 0.937498] s5k5ca.c: s5k5ca_i2c_write_w 0x0010 0x0001 rc=-5 <6>[1, swapper] [ 0.937649] s5k5ca.c: s5k5ca probe failed!!!! <3>[1, swapper] [ 0.948464] msm_sync_init: failed to initialize <4>[1, swapper] [ 0.948509] msm_camera_s5k5ca: probe of msm_camera_s5k5ca.0 failed with error -5 <6>[1, swapper] [ 0.949468] mt9p017.c: mt9p017_probe called! <6>[1, swapper] [ 1.000708] mt9p017.c: mt9p017_probe successed! rc = 0 <6>[1, swapper] [ 1.021256] mt9p017.c: mt9p017_probe_init_sensor is called <3>[0, swapper] [ 1.104634] qup_i2c qup_i2c.0: QUP: I2C status flags :0x1363c8, irq:34 <3>[1, swapper] [ 1.104686] qup_i2c qup_i2c.0: I2C slave addr:0x36 not connected <6>[1, swapper] [ 1.104721] mt9p017.c: mt9p017_i2c_rxdata failed! <6>[1, swapper] [ 1.104746] mt9p017.c: mt9p017_probe_init_sensor fails <6>[1, swapper] [ 1.104773] mt9p017.c: probe done <6>[1, swapper] [ 1.104994] mt9p017.c: mt9p017_probe_init_sensor failed . <6>[1, swapper] [ 1.105028] mt9p017.c: mt9p017_sensor_probe:2001 <3>[1, swapper] [ 1.115709] msm_sync_init: failed to initialize <4>[1, swapper] [ 1.115751] msm_camera_mt9p017: probe of msm_camera_mt9p017.0 failed with error -5 <6>[20, kworker/0:1] [ 1.144683] android_work: did not send uevent (0 0 (null)) <6>[1, swapper] [ 1.167604] mt9t113.c: i2c probe ok <3>[0, swapper] [ 1.257589] qup_i2c qup_i2c.0: QUP: I2C status flags :0x1363c8, irq:34 <3>[1, swapper] [ 1.257644] qup_i2c qup_i2c.0: I2C slave addr:0x3c not connected <6>[1, swapper] [ 1.257678] mt9t113.c: mt9t113_i2c_rxdata failed! <6>[1, swapper] [ 1.257704] mt9t113.c: mt9t113_i2c_read_w Model_ID failed!! rc=-5 <3>[0, swapper] [ 1.257859] qup_i2c qup_i2c.0: QUP: I2C status flags :0x1363c8, irq:34 <3>[1, swapper] [ 1.257918] qup_i2c qup_i2c.0: I2C slave addr:0x3c not connected <6>[1, swapper] [ 1.257949] mt9t113.c: mt9t113_i2c_rxdata failed! <3>[0, swapper] [ 1.258094] qup_i2c qup_i2c.0: QUP: I2C status flags :0x1363c8, irq:34 <3>[1, swapper] [ 1.258144] qup_i2c qup_i2c.0: I2C slave addr:0x3c not connected <3>[0, swapper] [ 1.258293] qup_i2c qup_i2c.0: QUP: I2C status flags :0x1363c8, irq:34 <3>[1, swapper] [ 1.258343] qup_i2c qup_i2c.0: I2C slave addr:0x3c not connected <3>[0, swapper] [ 1.258491] qup_i2c qup_i2c.0: QUP: I2C status flags :0x1363c8, irq:34 <3>[1, swapper] [ 1.258541] qup_i2c qup_i2c.0: I2C slave addr:0x3c not connected <6>[1, swapper] [ 1.258573] mt9t113.c: mt9t113_i2c_txdata faild <6>[1, swapper] [ 1.258599] mt9t113.c: i2c_write_w failed, addr = 0x28, val = 0xdc47! <6>[1, swapper] [ 1.258739] mt9t113.c: mt9t113 probe failed!!!! <3>[1, swapper] [ 1.269504] msm_sync_init: failed to initialize <4>[1, swapper] [ 1.269548] msm_camera_mt9t113: probe of msm_camera_mt9t113.0 failed with error -5 <6>[1, swapper] [ 1.269696] add tpa2028d1_r driver <6>[1, swapper] [ 1.270549] s5k4e1.c: s5k4e1_probe called! <6>[1, swapper] [ 1.324516] s5k4e1.c: s5k4e1_probe successed! rc = 0 <6>[1, swapper] [ 1.324666] s5k4e1.c: s5k4e1_af_probe called! <6>[1, swapper] [ 1.384513] s5k4e1.c: s5k4e1_af_probe successed! rc = 0 <6>[1, swapper] [ 1.384729] s5k4e1.c: s5k4e1_probe_init_sensor: 730 <6>[1, swapper] [ 1.384758] s5k4e1.c: s5k4e1_probe_init_sensor is called <6>[1, swapper] [ 1.390186] s5k4e1.c: s5k4e1_probe_init_sensor <6>[1, swapper] [ 1.390213] s5k4e1.c: sensor_reset = 0 <6>[1, swapper] [ 1.504936] s5k4e1.c: s5k4e1_i2c_read 0x0 val = 0x4e! <6>[1, swapper] [ 1.505384] s5k4e1.c: s5k4e1_i2c_read 0x1 val = 0x10! <6>[1, swapper] [ 1.505414] s5k4e1.c: ID: 78 <6>[1, swapper] [ 1.505436] s5k4e1.c: ID: 78 <6>[1, swapper] [ 1.505463] s5k4e1.c: probe done <4>[1, swapper] [ 1.505493] ------------[ cut here ]------------ <4>[1, swapper] [ 1.505541] WARNING: at /home/bro_yuki/android/source/cm10.1/kernel/huawei/u8815/drivers/gpio/gpiolib.c:1261 gpio_free+0x11c/0x150() <4>[1, swapper] [ 1.505578] Modules linked in: <4>[1, swapper] [ 1.505651] [<c0060de4>] (unwind_backtrace+0x0/0x128) from [<c0622038>] (dump_stack+0x20/0x24) <4>[1, swapper] [ 1.505714] [<c0622038>] (dump_stack+0x20/0x24) from [<c00db50c>] (warn_slowpath_common+0x5c/0x74) <4>[1, swapper] [ 1.505773] [<c00db50c>] (warn_slowpath_common+0x5c/0x74) from [<c00db550>] (warn_slowpath_null+0x2c/0x34) <4>[1, swapper] [ 1.505826] [<c00db550>] (warn_slowpath_null+0x2c/0x34) from [<c02e9acc>] (gpio_free+0x11c/0x150) <4>[1, swapper] [ 1.505883] [<c02e9acc>] (gpio_free+0x11c/0x150) from [<c045d0f8>] (s5k4e1_probe_init_done+0x3c/0x5c) <4>[1, swapper] [ 1.505939] [<c045d0f8>] (s5k4e1_probe_init_done+0x3c/0x5c) from [<c045e000>] (s5k4e1_sensor_probe+0xe0/0x194) <4>[1, swapper] [ 1.505994] [<c045e000>] (s5k4e1_sensor_probe+0xe0/0x194) from [<c0452a9c>] (msm_camera_drv_start+0x1d0/0x60c) <4>[1, swapper] [ 1.506054] [<c0452a9c>] (msm_camera_drv_start+0x1d0/0x60c) from [<c0620778>] (s5k4e1_probe+0x14/0x1c) <4>[1, swapper] [ 1.506114] [<c0620778>] (s5k4e1_probe+0x14/0x1c) from [<c0345f0c>] (platform_drv_probe+0x24/0x28) <4>[1, swapper] [ 1.506171] [<c0345f0c>] (platform_drv_probe+0x24/0x28) from [<c0344920>] (driver_probe_device+0x158/0x2a4) <4>[1, swapper] [ 1.506226] [<c0344920>] (driver_probe_device+0x158/0x2a4) from [<c0344adc>] (__driver_attach+0x70/0x94) <4>[1, swapper] [ 1.506281] [<c0344adc>] (__driver_attach+0x70/0x94) from [<c03437dc>] (bus_for_each_dev+0x60/0x9c) <4>[1, swapper] [ 1.506333] [<c03437dc>] (bus_for_each_dev+0x60/0x9c) from [<c0344470>] (driver_attach+0x28/0x30) <4>[1, swapper] [ 1.506384] [<c0344470>] (driver_attach+0x28/0x30) from [<c0344038>] (bus_add_driver+0xe4/0x268) <4>[1, swapper] [ 1.506436] [<c0344038>] (bus_add_driver+0xe4/0x268) from [<c03450a0>] (driver_register+0xb0/0x13c) <4>[1, swapper] [ 1.506489] [<c03450a0>] (driver_register+0xb0/0x13c) from [<c0346398>] (platform_driver_register+0x54/0x68) <4>[1, swapper] [ 1.506544] [<c0346398>] (platform_driver_register+0x54/0x68) from [<c002512c>] (s5k4e1_init+0x14/0x1c) <4>[1, swapper] [ 1.506598] [<c002512c>] (s5k4e1_init+0x14/0x1c) from [<c005440c>] (do_one_initcall+0xa0/0x170) <4>[1, swapper] [ 1.506649] [<c005440c>] (do_one_initcall+0xa0/0x170) from [<c0008a2c>] (kernel_init+0x7c/0x118) <4>[1, swapper] [ 1.506704] [<c0008a2c>] (kernel_init+0x7c/0x118) from [<c005b558>] (kernel_thread_exit+0x0/0x8) <4>[1, swapper] [ 1.506798] ---[ end trace 7a495caf7bcbe29a ]--- <6>[1, swapper] [ 1.506944] s5k4e1.c: probe af gpio
Guest NikitoGR Posted March 13, 2013 Report Posted March 13, 2013 I don't update the gapps link until a new build. Uh I updated the gapps one version after 12/12 and I didn't find any problems. :D
Guest samjam Posted March 13, 2013 Report Posted March 13, 2013 Maybe format it (and partition align?) it again: http://www.modaco.co...20#entry2098210 Well that seems to have worked. My 32G card is back in operation Thanks
Guest samjam Posted March 13, 2013 Report Posted March 13, 2013 Also these in kernel log: <6>[9643, akmd8975] [ 7717.654575] AKM8975 AKECS_GetData: data_ready is not set. <3>[9627, kworker/0:1] [ 7719.234900] gpio_tlmm_config(0x000846c3, GPIO_CFG_DISABLE) <sdc3_dat_4> failed: 0 <3>[9627, kworker/0:1] [ 7719.234939] pin 108 func 3 dir 1 pull 0 drvstr 4 <3>[9627, kworker/0:1] [ 7719.234997] gpio_tlmm_config(0x00084153, GPIO_CFG_DISABLE) <sdc3_dat_5> failed: -5 <3>[9627, kworker/0:1] [ 7719.235019] pin 21 func 3 dir 1 pull 0 drvstr 4 <3>[9627, kworker/0:1] [ 7719.235075] gpio_tlmm_config(0x00084143, GPIO_CFG_DISABLE) <sdc3_dat_6> failed: -5 <3>[9627, kworker/0:1] [ 7719.235095] pin 20 func 3 dir 1 pull 0 drvstr 4 ...
Guest Dazzozo Posted March 13, 2013 Report Posted March 13, 2013 Uh I updated the gapps one version after 12/12 and I didn't find any problems. :D Yeah? I didn't say it wouldn't work, merely that I choose not to update the link until a new build.
Guest Dazzozo Posted March 13, 2013 Report Posted March 13, 2013 Also these in kernel log: <6>[9643, akmd8975] [ 7717.654575] AKM8975 AKECS_GetData: data_ready is not set. <3>[9627, kworker/0:1] [ 7719.234900] gpio_tlmm_config(0x000846c3, GPIO_CFG_DISABLE) <sdc3_dat_4> failed: 0 <3>[9627, kworker/0:1] [ 7719.234939] pin 108 func 3 dir 1 pull 0 drvstr 4 <3>[9627, kworker/0:1] [ 7719.234997] gpio_tlmm_config(0x00084153, GPIO_CFG_DISABLE) <sdc3_dat_5> failed: -5 <3>[9627, kworker/0:1] [ 7719.235019] pin 21 func 3 dir 1 pull 0 drvstr 4 <3>[9627, kworker/0:1] [ 7719.235075] gpio_tlmm_config(0x00084143, GPIO_CFG_DISABLE) <sdc3_dat_6> failed: -5 <3>[9627, kworker/0:1] [ 7719.235095] pin 20 func 3 dir 1 pull 0 drvstr 4 ... [/code] All these errors are normal. The camera one is because of Huawei laziness.
Guest Fikret488 Posted March 13, 2013 Report Posted March 13, 2013 (edited) When the update Dazzo? Edited March 13, 2013 by Fikret488
Guest Gabrielius Posted March 13, 2013 Report Posted March 13, 2013 (edited) Hi everyone. Tried to install this one from INFUSION B08 rom, unfortunatelly there is error: symlink: some symlinks failed I did fully wiped, recovered everything, but I keep getting this error, maybe I cannot flash this one because I used INFUSION rom? Any help? EDIT: I did a recovery backup also. EDIT 2: seems, that now it's stuck at huawei logo EDIT 3: I just tried to do another wipe, and the I succesfully flashed this rom :) So far it looks and feels awesome! Huge thanks! Edited March 13, 2013 by Gabrielius
Guest NikitoGR Posted March 13, 2013 Report Posted March 13, 2013 Yeah? I didn't say it wouldn't work, merely that I choose not to update the link until a new build. Oops you said "I don't" nvm
Guest dubitoergosum Posted March 13, 2013 Report Posted March 13, 2013 Hey guys! I had to do a factory reset after ticking something I ought not have to, and now I don't get notifications from gmail about new emails. I reinstalled gmail, still not working. It's set to sync the emails of the past 3 days, automatic sync is enabled, notifications are enabled... Should I reinstall gapps, or what else could be the problem?
Guest Dazzozo Posted March 13, 2013 Report Posted March 13, 2013 Hi everyone. Tried to install this one from INFUSION B08 rom, unfortunatelly there is error: symlink: some symlinks failed That's a bug in the recovery you're using.
Guest peetu20 Posted March 13, 2013 Report Posted March 13, 2013 That's a bug in the recovery you're using. Is this rom almost good for daily use?
Guest Dazzozo Posted March 13, 2013 Report Posted March 13, 2013 Is this rom almost good for daily use? That's subjective. Personally I don't think the DEVICE is good for daily use. :)
Guest andy.hyde4 Posted March 13, 2013 Report Posted March 13, 2013 That's subjective. Personally I don't think the DEVICE is good for daily use. :) Shut up you with your Nexus 4 ;)
Guest NikitoGR Posted March 13, 2013 Report Posted March 13, 2013 That's subjective. Personally I don't think the DEVICE is good for daily use. :) Why daz? I don't have any problems. I'm a heavy user. I'm playing games too :D JB+Daz <3
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now