Develop Bugs

Working android linux from Fbettag for our BA's

Screenshot here , it shows the android's UI displayd on a BA
http://picpaste.de/IMG_0093.JPG note:this is from hes phone not mine
he wrote on google groups:
fbetag "Altogether i've put up two tbz2:
- http://evil-packet.org/android/vfat-bootloader-kernel.tbz2
Just copy this to the vfat partition (first partition) on your SD-
Card.
Android will autoboot as soon you plug the card into your BA.
- http://evil-packet.org/android/ext2-android-htc-blueangel-arm.tbz2
Copy it to the ext2 partition (second partition) on your SD-Card.
/bin contains busybox with the according symlinks.
I moved /init (android loader) to /sbin/android.
And i also cross compiled strace and dropbear (which doesn't work
yet).
My /sbin/init is to be customized with your own start-stop stuff.
If you boot Android while your BlueAngel is in it's USB Cradle and
your Linux Computer on the other end got USBnet (so that usb0 appears
on both devices), then my /sbin/init will configure usb0 with
192.168.1.201/24 and start telnetd. The default root password is
"android".
I think this is a fairly good base to start of hacking for this
device Let's do it.
Finally i got some questions google.com couldn't answer me:
- What ANDROID_ environment-variables are there?
- What does it take to make my TS Input Device (tsc2200) available?
Here are several outputs:
--- dmesg ---
<5>Linux version 2.6.21-hh20-omap1 ([email protected]) (gcc version
4.2.3 (Sourcery G++ Lite 2008q1-126)) #5 PREEMPT Sun Aug 3 21:26:21
CEST 2008
<4>CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE), cr=0000397f
<4>Machine: HTC Blueangel
<4>Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 32768
<7> DMA zone: 256 pages used for memmap
<7> DMA zone: 0 pages reserved
<7> DMA zone: 32512 pages, LIFO batch:7
<7> Normal zone: 0 pages used for memmap
<6>Memory clock: 99.53MHz (*27)
<6>Run Mode clock: 398.13MHz (*4)
<6>Turbo Mode clock: 398.13MHz (*1.0, inactive)
<4>CKEN=0x10a71 CKEN11_USB=0x800
<4>CKEN=0x10a71
<4>CPU0: D VIVT undefined 5 cache
<4>CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32
sets
<4>CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32
sets
<4>Built 1 zonelists. Total pages: 32512
<5>Kernel command line: root=/dev/mmcblk0p2 rootdelay=10
console=ttyS0,115200n8 console=tty0
<4>PID hash table entries: 512 (order: 9, 2048 bytes)
<4>Console: colour dummy device 80x30
<4>Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
<4>Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
<6>Memory: 128MB = 128MB total
<5>Memory: 126336KB available (2868K code, 502K data, 104K init)
<7>Calibrating delay loop... 397.31 BogoMIPS (lpj=1986560)
<4>Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: ok
<4>android_power_init
<4>android_power_init done
<6>NET: Registered protocol family 16
<6>[ 0.420000] asic3: using irq 108-177 on irq 26
<4>[ 0.430000] Initializing blueangel tsc2200 ssp... done
<4>[ 0.440000] tsc2200_probe: SPI: cr0 0000138f cr1 60000010 sr:
0000f024 it: 00000000 to: 00000000 ps: 00000000
<6>[ 0.470000] Bluetooth: Core ver 2.11
<6>[ 0.470000] NET: Registered protocol family 31
<6>[ 0.480000] Bluetooth: HCI device and connection manager
initialized
<6>[ 0.490000] Bluetooth: HCI socket layer initialized
<6>[ 0.510000] Time: pxa_timer clocksource has been installed.
<4>[ 0.520000] pxa2xx-udc-gpio: Generic driver for GPIO-controlled
PXA2xx UDC
<6>[ 0.530000] NET: Registered protocol family 2
<4>[ 0.640000] IP route cache hash table entries: 1024 (order: 0,
4096 bytes)
<4>[ 0.650000] TCP established hash table entries: 4096 (order: 3,
32768 bytes)
<4>[ 0.660000] TCP bind hash table entries: 4096 (order: 2, 16384
bytes)
<6>[ 0.670000] TCP: Hash tables configured (established 4096 bind
4096)
<6>[ 0.680000] TCP reno registered
<4>[ 0.720000] blueangel_lcd_init
<4>[ 0.720000] Blue Angel Board ID 0x6
<4>[ 0.730000] in blueangel_lcd_probe
<4>[ 0.740000] HTC Blueangel DS1WM driver
<4>[ 0.740000] blueangel_pcmcia_socket_init
<4>[ 0.750000] blueangel_pcmcia_configure_socket
<4>[ 0.760000] Reset:0 ,Vcc:0 ,Flags:0
<4>[ 1.030000] blueangel_pm_init
<4>[ 1.030000] retval=0
<6>[ 1.040000] input: blueangelkb as /class/input/input0
<5>[ 1.050000] Probing PXA Flash 1 at physical address 0x00000000
(32-bit bankwidth)
<4>[ 1.060000] mymtd=00000000
<6>[ 1.070000] ttyS8 at MMIO 0x10800000 (irq = 91) is a DPRAM
<4>[ 1.080000] dpram hwident: 'HTC-DPRAM ASIC P/N:30H80037-00-L'
<5>[ 1.090000] HTC Blueangel Phone Modem Driver
<6>[ 1.090000] PXA CPU frequency change support initialized
<4>[ 1.110000] NetWinder Floating Point Emulator V0.97 (double
precision)
<6>[ 1.120000] JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat,
Inc.
<6>[ 1.140000] io scheduler noop registered
<6>[ 1.140000] io scheduler anticipatory registered (default)
<6>[ 1.150000] io scheduler deadline registered
<4>[ 1.160000] Corgi Backlight Driver Initialized.
<4>[ 1.170000] Found w3200 at 0x08000000.
<4>[ 1.210000] blueangel_pcmcia_configure_socket
<4>[ 1.220000] Reset:0 ,Vcc:50 ,Flags:0
<4>[ 1.230000] Console: switching to colour frame buffer device
60x53
<6>[ 1.250000] fb0: w100fb frame buffer device
<6>[ 1.400000] TI Calypso / HTC firmware GSM UART line discipline
ver 0.1<6>pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 15) is a
FFUART
<6>[ 1.420000] pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 14)
is a BTUART
<6>[ 1.440000] pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 13)
is a STUART
<6>[ 1.450000] pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 0) is
a HWUART
<6>[ 1.470000] pxa2xx-ir-serial: Initialized
<4>[ 1.480000] RAMDISK driver initialized: 4 RAM disks of 8192K
size 1024 blocksize
<6>[ 1.500000] loop: loaded (max 8 devices)
<6>[ 1.510000] tun: Universal TUN/TAP device driver, 1.6
<6>[ 1.520000] tun: (C) 1999-2004 Max Krasnyansky
<[email protected]>
<4>[ 1.530000] acx: this driver is still EXPERIMENTAL
<4>[ 1.530000] acx: reading README file and/or Craig's HOWTO is
recommended, visit http://acx100.sf.net in case of further questions/
discussion
<7>[ 1.560000] acxcs_init()
<6>[ 1.570000] I2C: i2c-0: PXA I2C adapter
<6>[ 1.580000] pxa2xx_udc: version 4-May-2005
<7>[ 1.600000] DPM: pda_udc: Turning off port
<4>[ 1.600000] ether gadget: using random self ethernet address
<4>[ 1.630000] ether gadget: using random host ethernet address
<4>[ 1.650000] blueangel_pcmcia_configure_socket
<4>[ 1.670000] Reset:1 ,Vcc:50 ,Flags:240
<4>[ 1.680000] blueangel_pcmcia_configure_socket
<4>[ 1.700000] Reset:0 ,Vcc:50 ,Flags:200
<6>[ 1.710000] usb0: Ethernet Gadget, version: May Day 2005
<6>[ 1.730000] usb0: using pxa2xx_udc, OUT ep2out-bulk IN ep1in-
bulk
<6>[ 1.750000] usb0: MAC 1e:bf:a5:a0:28:2d
<7>[ 1.770000] DPM: pda_udc: Turning on port
<6>[ 1.780000] input: gpio-keys as /class/input/input1
<4>[ 1.780000] pxa_gpiodev_get_value(8)
<4>[ 1.810000] Registering tsc2200 buttons driver
<5>[ 1.820000] pccard: PCMCIA card inserted into slot 0
<5>[ 1.840000] pcmcia: registering new device pcmcia0.0
<7>[ 1.860000] acx_attach()
<7>[ 1.860000] acx_cs_config(0xc0622600)
<6>[ 1.870000] MEMORY WINDOW FOUND!!!
<6>[ 1.880000] requesting Irq...
<4>[ 1.890000] pcmcia: request for exclusive IRQ could not be
fulfilled.
<4>[ 1.920000] pcmcia: the driver needs updating to supported
shared IRQ lines.
<4>[ 1.950000] blueangel_pcmcia_configure_socket
<4>[ 1.960000] Reset:0 ,Vcc:50 ,Flags:200
<4>[ 1.980000] blueangel_pcmcia_configure_socket
<4>[ 1.990000] Reset:0 ,Vcc:50 ,Flags:220
<7>[ 2.050000] RequestConfiguration OK
<4>[ 2.050000] acx: found ACX100-based wireless network card
<7>[ 2.070000] initial debug setting is 0x000A
<6>[ 2.070000] memwinbase=2c000000 memwinsize=4096
<7>[ 2.080000] using IRQ 40
<4>[ 2.110000] ACX radio type 0x0d
<7>[ 2.120000] requesting firmware image 'WLANGEN.BIN'
<4>[ 2.120000] 9<6>input: tsc2200-keys as /class/input/input2
<4>[ 2.150000] tsc2200_ts_probe IRQ: 39
<6>[ 2.170000] input: tsc2200-ts as /class/input/input3
<7>[ 2.190000] sa1100-rtc sa1100-rtc: rtc intf: sysfs
<7>[ 2.190000] sa1100-rtc sa1100-rtc: rtc intf: proc
<7>[ 2.200000] sa1100-rtc sa1100-rtc: rtc intf: dev (254:0)
<6>[ 2.200000] sa1100-rtc sa1100-rtc: rtc core: registered sa1100-
rtc as rtc0
<6>[ 2.230000] Driver for 1-wire Dallas network protocol.
<4>[ 2.250000] DS1WM w1 busmaster driver - (c) 2004 Szabolcs Gyurko
<4>[ 2.280000] blueangel_ds1wm: OWM_EN Low (active)
<6>[ 2.310000] 1-Wire driver for the DS2760 battery monitor chip
- (c) 2004-2005, Szabolcs ..."

can you post the image of Android? ("initrd-android" etc)

its alrdy there mate use the second link to download it , it says "ext2-android-htc-blueangel-arm.tbz2" 32mb file

thanks, i'll try it someday

Tryed, the touch screen doesnt work.

root said:
Tryed, the touch screen doesnt work.
Click to expand...
Click to collapse
Hi,
I'm one of the maintenair of this kernel, last time i look to android, it seem you have to patch the kernel to get the touchscreen working with android.
They do something special. maybe you can try with datas from latest SDK.

Very interested things!
I'm very interesting with this! So, are you working on this? I'll try to make something better but don't known where to start.
Anybody know about extract android's image file in emulator to SD card?
What the android distro it is folllowing? I mean: debian, redhat or anything else.

so what are the cons and pros of using Android instead of WinMo?

The biggest pro here is that you can get away from M$oft and try something new and have a new experiance.

system lose connection to SD card

Hi, I am the happy owner of a DHD for more than a year and a half now, and quickly installed a LeeDroid rom (v2.2 about a year ago, based on Froyo with HTC Sense). It works fantastic, however I wanted to see how the roms evolved since then, so I tried new ones, Gingerbread and ICS based ones.
And here the problems start, whatever new rom I try, the SD card after a not very long time (maybe 10 or 20 minutes) stop being recognized by the new system. If I unplug it, the system goes off, so I restart, but then the same problem happen anyway.
The SD card I am using is a 32GB model I bought about a year ago. I never had any problem with LeedDroid rom with it, and actually still have no problem with it (thanks to ClockworkRecovery here, I could revert to the working rom)
Has any one heard of a problem of this kind ? I googled quite a bit but didn't find anything ... Could it be that this big SD card (32GB is quite big) needs more power, and newer kernel try to save a bit too much of it ?
I'll make more test, maybe there is a specific action I do at the moment where I lost the SD card, but I haven't identified it yet ...
Any help or suggestion is welcome !

Some informations about what I found in kernel traces :
It starts with :
<4>[ 524.603302] [BATT] [x0]3 [x8]16 90 9 80 64 a0 f6 f6 e 5c
<4>[ 524.603546] [BATT] V=3928(64a) I=-228(fffffdbe) C=954.0/1230(e5c) id=1(98) T=340(169) KADC=802
<4>[ 524.603668] [BATT]S=2 P=776 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137676592]
<6>[ 525.652435] [VIB] Binder Thread #(parent:zygote): vibrates 0 msec
<6>[ 525.652740] [VIB] Binder Thread #(parent:zygote): vibrates 15 msec
<6>[ 525.653717] [ATS][set_vibration][successful]
<6>[ 525.667907] [VIB]vibrator_timer_func
<6>[ 525.668945] [VIB] er.ServerThread(parent:zygote): vibrates 0 msec
<4>[ 554.611755] [BATT] [x0]3 [x8]16 90 9 90 64 80 f7 b6 e 57
<4>[ 554.611999] [BATT] V=3923(648) I=-209(fffffdee) C=952.0/1230(e57) id=1(99) T=340(169) KADC=786
<4>[ 554.612213] [BATT]S=2 P=774 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137706600]
<6>[ 565.466949] [VIB] InputReader(parent:zygote): vibrates 0 msec
<6>[ 565.469573] [VIB] Thread-87(parent:zygote): vibrates 10 msec
<6>[ 565.470153] [ATS][set_vibration][successful]
<6>[ 565.479705] [VIB]vibrator_timer_func
<6>[ 565.500000] [VIB] Thread-87(parent:zygote): vibrates 30 msec
<6>[ 565.500976] [ATS][set_vibration][successful]
<6>[ 565.530212] [VIB]vibrator_timer_func
<6>[ 568.204559] binder: 1333:1339 transaction failed 29189, size 4-0
<6>[ 568.204803] binder: send failed reply for transaction 40612, target dead
<6>[ 573.939361] [VIB] Binder Thread #(parent:zygote): vibrates 0 msec
<6>[ 578.933837] [VIB] Binder Thread #(parent:zygote): vibrates 0 msec
<4>[ 584.621307] [BATT] [x0]3 [x8]16 90 9 80 64 20 f4 d8 e 52
<4>[ 584.621337] [BATT] V=3908(642) I=-282(fffffd36) C=950.0/1230(e52) id=1(98) T=340(169) KADC=796
<4>[ 584.621368] [BATT]S=2 P=773 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137736609]
<4>[ 611.101196] Return_dpc value is : 0
<4>[ 614.632995] [BATT] [x0]3 [x8]16 80 9 80 64 20 f6 24 e 4c
<4>[ 614.633148] [BATT] V=3908(642) I=-249(fffffd89) C=947.0/1230(e4c) id=1(98) T=340(168) KADC=782
<6>[ 614.633361] [BATT] ds2746_notify: 1 77 at 610429628432 (2012-06-05 05:03:15.677851169 UTC)
<6>[ 614.633697] [BATT] power_supply_changed: battery at 610429964125 (2012-06-05 05:03:15.678186862 UTC)
<4>[ 614.647460] [BATT]S=2 P=770 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137766635]
<6>[ 631.344360] microp_led_pwm_brightness_set, data[1] = 255
<6>[ 638.891937] request_suspend_state: sleep (0->3) at 634688051285 (2012-06-05 05:03:39.936365574 UTC)
<7>[ 638.892333] [LS][ISL29028] lightsensor_ioctl cmd 2
<6>[ 638.892456] [LS][ISL29028] lightsensor_disable
<6>[ 638.892761] [R] early_suspend start
<6>[ 638.893096] sleep_stat.0: 0ms 0 0ms 0 - 0 0 0 - 0 0 - 0 0 0 0 0(2012-06-05 05:03:39.937586277 UTC)
<6>[ 638.893310] [DISP]lcdc_blank: ()
<4>[ 638.893432] [lcm]spade_sharp_panel_blank
<7>[ 638.896453] [LS][ISL29028] lightsensor_release
<6>[ 638.897125] microp_led_pwm_brightness_set, data[1] = 0
<6>[ 638.900238] [COMP] Compass disable
<4>[ 638.909484] dhd_get_dtim_skip bcn_li_dtim=3 DTIM=1 Listen=10
<6>[ 638.913208] [VIB] er.ServerThread(parent:zygote): vibrates 0 msec
<6>[ 638.924102] [DISP]lcdc_suspend: suspending
<4>[ 638.924652] [lcm]spade_sharp_panel_uninit
<4>[ 638.925231] [lcm]spade_sharp_panel_power(0):
<6>[ 638.945770] [GSNR] Gsensor disable
<6>[ 638.996826] [R] early_suspend: sync
<7>[ 639.397155] [COMP][AKM8975] AKECS_GetOpenStatus:
<6>[ 639.472778] [R] early_suspend end
<4>[ 644.660858] [BATT] [x0]3 [x8]16 80 9 90 64 b0 f9 38 e 47
<4>[ 644.661010] [BATT] V=3930(64b) I=-171(fffffe4e) C=945.0/1230(e47) id=1(99) T=340(168) KADC=780
<4>[ 644.661224] [BATT]S=2 P=769 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137796649]
<4>[ 674.690887] [BATT] [x0]3 [x8]16 90 9 b0 65 40 fc 44 e 44
<4>[ 674.691009] [BATT] V=3952(654) I=-94(ffffff11) C=944.0/1230(e44) id=1(9b) T=340(169) KADC=779
<4>[ 674.691223] [BATT]S=2 P=768 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137826679]
<4>[ 704.712310] [BATT] [x0]3 [x8]16 90 9 a0 65 40 fc 6d e 41
<4>[ 704.712432] [BATT] V=3952(654) I=-90(ffffff1c) C=943.0/1230(e41) id=1(9a) T=340(169) KADC=778
<4>[ 704.712646] [BATT]S=2 P=767 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137856701]
<4>[ 734.732086] [BATT] [x0]3 [x8]16 90 9 b0 65 50 fc 38 e 3f
<4>[ 734.732421] [BATT] V=3955(655) I=-95(ffffff0e) C=942.0/1230(e3f) id=1(9b) T=340(169) KADC=783
<4>[ 734.732940] [BATT]S=2 P=766 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137886721]
<3>[ 761.839172] mmc2: Data timeout
<3>[ 761.839324] mmc2: DMA channel flushed (0x80000004)
<3>[ 761.839447] Flush data: 0000c003 2ad35120 00000000 00400040 00400040 00000003
<6>[ 761.839752] mmc2: Controller has been reset
<6>[ 761.839965] mmc2: Worked around bug 1535304
<4>[ 761.840209] mmcblk1: retrying using single block read
<3>[ 762.058135] mmc2: Data timeout
<3>[ 762.058258] mmc2: DMA channel flushed (0x80000004)
I get for a few seconds lots of error of this kind :
<3>[ 762.807312] mmc_blk_issue_rq failed!!
<3>[ 762.814666] mmcblk1: error -123 sending read command, response 0x0
<4>[ 762.814788] mmcblk1: retrying using single block read
<3>[ 762.814971] mmcblk1: error -123 sending status comand
<3>[ 762.815093] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 762.815368] end_request: I/O error, dev mmcblk1, sector 27564800
<3>[ 762.815612] mmc_blk_issue_rq failed!!
Then eventually I get this :
<3>[ 763.182128] end_request: I/O error, dev mmcblk1, sector 27564800
<3>[ 763.182342] mmc_blk_issue_rq failed!!
<6>[ 763.190399] spade_sdslot_switchvdd: Disabling SD slot power
<6>[ 763.191040] mmc2: mmc_remove_sd_card exit
<4>[ 764.740875] [BATT] [x0]3 [x8]16 90 9 a0 64 f0 fa 9 e 3d
<4>[ 764.740997] [BATT] V=3940(64f) I=-150(fffffe83) C=941.0/1230(e3d) id=1(9a) T=340(169) KADC=786
<4>[ 764.741210] [BATT]S=2 P=765 chg=0 cable=000 flg=110 dbg=0000 fst_dischg=804/989 [3137916729]
<3>[ 765.404113] FAT: Directory bread(block 28471360) failed
<3>[ 765.404266] FAT: Directory bread(block 28471361) failed

Copy the content off the card, format it in recovery and put everything back. Have you done that already?
Sent from my Desire HD using xda premium

Before putting the content back, try it without....
After a while then try it with the content.
Formatting and putting things back on...well, you know.
Sent from a dream.

I didn't try that , but it will take a long long time since I have about 20GB of data on this card
Ok I'll start to make a backup. What is the recommended type of filesystem to format a big SD card ?
When I see the kernel log, I don't think it is a problem at the filesystem level, but rather at a lower level, so I am not quite sure it will help.

Just format it in recovery, it'll format it correctly. If you want to do it manually then format it to Fat32 with 32kB cluster size. That'll increase your read and write speed when copying large files between the phone and computer, rather than use the 'default allocation side's in Windows.
Also try this, first make a backup and format the card in recovery, then go to tools-check filesystem and follow through. Skip the first two steps if you don't want to create a sd-ext and swap partition. My SD card was acting funny and this helped it. It said my partition wasn't properly aligned. If it says it's properly aligned for you then no need to do this.
I don't know if this option is there in CWM, but it's there in 4ext.
Sent from my Desire HD using xda premium

Thanks for the reply. So I reformatted the disk, even added an app partition, though I probably won't use it ... And now it seems to work with cm7.1
I have however a very annoying issue now, USB transfers to the SD card under cm7.1 are very very slow. apparently I am not the only one to experience this (forum.cyanogenmod.com/.../33323-very-slow-usb-sd-transfer-rates/), but I haven't found a solution, if there is one ...

Yeah I've heard of that too. But I never used CM7.1. I started using CM from 7.2 RC0, and I think that was fixed. I remember my USB transfer speed was fine, the same as it was when transferring through recovery or through a memory card reader. Try CM 7.2 RC3. It's the latest. It's a bit misplaced in the Desire HD section of the CM downloads website. You'll find it under 'nightly' instead of 'experimental releases'.
Sent from my Desire HD using xda premium

Modem kernel panic help

Hi, I am trying to get the latest version of CM KitKat to allow modem resets, but instead I get rebooting. Can anyone make heads or tails from the following crash? Also, it works fine in older roms, and the second output shows that it handles the reset fine without rebooting.
[ 436.254661] SMSM: Modem SMSM state changed to SMSM_RESET.
[ 436.260521] Notify: start reset
[ 436.260552] Probable fatal error on the modem.
[ 436.260552] modem subsystem failure reason: (unknown, smem_get_entry failed).
[ 436.260552] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = 1.
[ 436.260582] Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.
[ 436.260613] [<c0013d84>] (unwind_backtrace+0x0/0xe0) from [<c0741084>] (panic+0x88/0x1f8)
[ 436.260613] [<c0741084>] (panic+0x88/0x1f8) from [<c0050844>] (subsystem_restart_dev+0xf8/0x124)
[ 436.260643] [<c0050844>] (subsystem_restart_dev+0xf8/0x124) from [<c0051928>] (restart_modem+0xa0/0xd4)
[ 436.260674] [<c0051928>] (restart_modem+0xa0/0xd4) from [<c002ff28>] (notify_smsm_cb_clients_worker+0xa4/0x1c4)
[ 436.260674] [<c002ff28>] (notify_smsm_cb_clients_worker+0xa4/0x1c4) from [<c0086314>] (process_one_work+0x22c/0x428)
[ 436.260704] [<c0086314>] (process_one_work+0x22c/0x428) from [<c00866d8>] (worker_thread+0x19c/0x2bc)
[ 436.260704] [<c00866d8>] (worker_thread+0x19c/0x2bc) from [<c008ad08>] (kthread+0x84/0x94)
[ 436.260735] [<c008ad08>] (kthread+0x84/0x94) from [<c000e9e4>] (kernel_thread_exit+0x0/0x8)
[ 436.366030] CPU0: stopping
[ 436.368777] [<c0013d84>] (unwind_backtrace+0x0/0xe0) from [<c0012e0c>] (handle_IPI+0x100/0x1cc)
[ 436.377414] [<c0012e0c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[ 436.386052] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000db00>] (__irq_svc+0x40/0x70)
[ 436.394384] Exception stack(0xec939e48 to 0xec939e90)
[ 436.399359] 9e40: c0c7ff38 373cff38 00205b3e 00000000 00000001 0000000f
[ 436.407569] 9e60: 00000029 00000003 c0c7ff54 00000003 c0b61970 60000113 00000000 ec939e90
[ 436.415717] 9e80: c006ec50 c006f128 60000113 ffffffff
[ 436.420723] [<c000db00>] (__irq_svc+0x40/0x70) from [<c006f128>] (vprintk+0x3a8/0x420)
[ 436.428658] [<c006f128>] (vprintk+0x3a8/0x420) from [<c074120c>] (printk+0x18/0x24)
[ 436.436319] [<c074120c>] (printk+0x18/0x24) from [<c0020e24>] (modem_notifier_test_call+0x3c/0x54)
[ 436.445200] [<c0020e24>] (modem_notifier_test_call+0x3c/0x54) from [<c0090270>] (notifier_call_chain+0x38/0x68)
[ 436.455333] [<c0090270>] (notifier_call_chain+0x38/0x68) from [<c0090304>] (__srcu_notifier_call_chain+0x40/0x58)
[ 436.465557] [<c0090304>] (__srcu_notifier_call_chain+0x40/0x58) from [<c0090330>] (srcu_notifier_call_chain+0x14/0x18)
[ 436.476239] [<c0090330>] (srcu_notifier_call_chain+0x14/0x18) from [<c0086314>] (process_one_work+0x22c/0x428)
[ 436.486220] [<c0086314>] (process_one_work+0x22c/0x428) from [<c00866d8>] (worker_thread+0x19c/0x2bc)
[ 436.495406] [<c00866d8>] (worker_thread+0x19c/0x2bc) from [<c008ad08>] (kthread+0x84/0x94)
[ 436.503677] [<c008ad08>] (kthread+0x84/0x94) from [<c000e9e4>] (kernel_thread_exit+0x0/0x8)
[ 436.612147] Rebooting in 5 seconds..
[ 441.616511] Going down for restart now
[ 441.619471] msm_restart : clear reset flag
Here is the same thing in a working rom.
<3>[ 166.851182] SMSM: Modem SMSM state changed to SMSM_RESET.
<3>[ 166.851396] Notify: start reset
<3>[ 166.851518] Modem SMSM state changed to SMSM_RESET.
<3>[ 166.851518] Probable err_fatal on the modem. Calling subsystem restart...
<6>[ 166.851670] subsys-restart: subsystem_restart(): Restart sequence requested for modem, restart_level = 3.
<6>[ 166.851762] subsys-restart: subsystem_restart_thread(): [d9091b00]: Shutting down modem
<3>[ 166.882038] unvote_dfab: dfab is already off
<4>[ 166.882038] [<c010eb68>] (unwind_backtrace+0x0/0x108) from [<c0122658>] (unvote_dfab+0xa4/0xcc)
<4>[ 166.882069] [<c0122658>] (unvote_dfab+0xa4/0xcc) from [<c0123318>] (bam_dmux_smsm_cb+0x134/0x748)
<4>[ 166.882069] [<c0123318>] (bam_dmux_smsm_cb+0x134/0x748) from [<c0129900>] (notify_smsm_cb_clients_worker+0x10c/0x254)
<4>[ 166.882099] [<c0129900>] (notify_smsm_cb_clients_worker+0x10c/0x254) from [<c018ed7c>] (process_one_work+0x14c/0x444)
<4>[ 166.882099] [<c018ed7c>] (process_one_work+0x14c/0x444) from [<c018f3ac>] (worker_thread+0x174/0x37c)
<4>[ 166.882130] [<c018f3ac>] (worker_thread+0x174/0x37c) from [<c0193dcc>] (kthread+0x88/0x90)
<4>[ 166.882130] [<c0193dcc>] (kthread+0x88/0x90) from [<c0108f70>] (kernel_thread_exit+0x0/0x8)
<3>[ 166.882221] release_wakelock: bam_dmux wakelock not locked
<4>[ 166.882252] [<c010eb68>] (unwind_backtrace+0x0/0x108) from [<c012090c>] (release_wakelock+0xc0/0xec)
<4>[ 166.882252] [<c012090c>] (release_wakelock+0xc0/0xec) from [<c0129900>] (notify_smsm_cb_clients_worker+0x10c/0x254)
<4>[ 166.882282] [<c0129900>] (notify_smsm_cb_clients_worker+0x10c/0x254) from [<c018ed7c>] (process_one_work+0x14c/0x444)
<4>[ 166.882282] [<c018ed7c>] (process_one_work+0x14c/0x444) from [<c018f3ac>] (worker_thread+0x174/0x37c)
<4>[ 166.882282] [<c018f3ac>] (worker_thread+0x174/0x37c) from [<c0193dcc>] (kthread+0x88/0x90)
<4>[ 166.882313] [<c0193dcc>] (kthread+0x88/0x90) from [<c0108f70>] (kernel_thread_exit+0x0/0x8)
<3>[ 166.882588] ch_notify: smd closed
<3>[ 166.882588] ch_notify: smd closed
<3>[ 166.882618] ch_notify: smd closed
<3>[ 166.882618] ch_notify: smd closed
<3>[ 166.882618] ch_notify: smd closed
<3>[ 166.882618] ch_notify: smd closed
<3>[ 166.882649] ch_notify: smd closed
<3>[ 166.882649] ch_notify: smd closed
<6>[ 166.882649] diag: clean modem registration
<6>[ 166.886311] subsys-restart: subsystem_restart_thread(): [d9091b00]: Powering up modem
<7>[ 166.886311] load_image: load modem_fw.mdt image
<6>[ 167.219807] pil_qdsp6v4 pil_qdsp6v4.1: brought out of reset
<7>[ 167.220479] load_image: load modem.mdt image
<6>[ 168.853898] bl_level:40,cd:2:Candela:40 aid_change:1
<6>[ 169.392156] pil_qdsp6v4 pil_qdsp6v4.2: brought out of reset
<6>[ 169.393224] subsys-restart: subsystem_restart_thread(): [d9091b00]: Restart sequence for modem completed.
<3>[ 170.125438] Notify: smsm init
<6>[ 171.607202] diag: incomplete pkt on Modem CNTL ch
<6>[ 171.632565] diag: event mask not set yet, so no update
<6>[ 172.412513] sps:REVISION of BAM 0xe5b14000 is 0x5.
<3>[ 175.133770] handle_bam_mux_cmd: dropping invalid LCID 10 reserved 0 cmd 4 pad 0 ch 10 len 0
<3>[ 175.133862] handle_bam_mux_cmd: dropping invalid LCID 11 reserved 0 cmd 4 pad 0 ch 11 len 0
<6>[ 175.473401] pm8921_enable_batt_therm: [pm8921] enable Vref_batt_therm
<6>[ 175.983122] pm8921_enable_batt_therm: [pm8921] disable Vref_batt_therm
<6>[ 175.983122] sec_bat_monitor_work: battery check is present (1 time )
<6>[ 175.984800] [battery] level(99), vcell(4346250), therm(248)
<6>[ 175.984800] [battery] cable_type(1), chg_status(1), health(1)
<6>[ 175.984800] [battery] timeout_chgstp(0), chg_enabled(1), rechg_status(0)

Galaxy Trend GT-S7560M Latin America WiFi on CustomROM

So it seems that the LA version of the GT-S7560M has a different WiFi module than other GT-S7560M editions (or is it just South America?).
I wonder if there is a way to the developers of this device out there know what exactly is the WiFi module in our devices so they can figure out what to include in their builds to make this work.
Personally I have no idea about Android Hacking, so I wouldn't know what to do, but I know my way around the commandline in OS X and Linux and at work I have access to Windows 7 too, so I could feed you with the specs of my device.
I'm currently running StockROM with Sadman's Kernel (3.0.8 [email protected]) ) #5 PREEMPT Tue Mar 11.....
I tried to run CyanogenMod with Sadman's Kernel, but that just won't boot.
So how could we users post what exactly, to help you developers to figure out what is different with our devices, so maybe together we could make our devices work with your ROMs?
Personally I have a Samsung Trend GT-S7560M from Tigo Bolivia.
Thanks

I support
In america central not working wifi and tried diferents options to make it work the wifi and not working. And it's good that we do see that here ay people around the world and we should look for ways to solve our problems.
Saludos desde Costa Rica.

hhpss said:
So it seems that the LA version of the GT-S7560M has a different WiFi module than other GT-S7560M editions (or is it just South America?).
I wonder if there is a way to the developers of this device out there know what exactly is the WiFi module in our devices so they can figure out what to include in their builds to make this work.
Personally I have no idea about Android Hacking, so I wouldn't know what to do, but I know my way around the commandline in OS X and Linux and at work I have access to Windows 7 too, so I could feed you with the specs of my device.
I'm currently running StockROM with Sadman's Kernel (3.0.8 [email protected]) ) #5 PREEMPT Tue Mar 11.....
I tried to run CyanogenMod with Sadman's Kernel, but that just won't boot.
So how could we users post what exactly, to help you developers to figure out what is different with our devices, so maybe together we could make our devices work with your ROMs?
Personally I have a Samsung Trend GT-S7560M from Tigo Bolivia.
Thanks
Click to expand...
Click to collapse
Youre very lucky that you didn't hard-brick your phone
sadmans kernels are for STOCK and seriously not meant for cm
Sent from my GT-S7560M using XDA Premium 4 mobile app
---------- Post added at 01:57 AM ---------- Previous post was at 01:52 AM ----------
hhpss said:
So it seems that the LA version of the GT-S7560M has a different WiFi module than other GT-S7560M editions (or is it just South America?).
I wonder if there is a way to the developers of this device out there know what exactly is the WiFi module in our devices so they can figure out what to include in their builds to make this work.
Personally I have no idea about Android Hacking, so I wouldn't know what to do, but I know my way around the commandline in OS X and Linux and at work I have access to Windows 7 too, so I could feed you with the specs of my device.
I'm currently running StockROM with Sadman's Kernel (3.0.8 [email protected]) ) #5 PREEMPT Tue Mar 11.....
I tried to run CyanogenMod with Sadman's Kernel, but that just won't boot.
So how could we users post what exactly, to help you developers to figure out what is different with our devices, so maybe together we could make our devices work with your ROMs?
Personally I have a Samsung Trend GT-S7560M from Tigo Bolivia.
Thanks
Click to expand...
Click to collapse
If the wifi problem hardware related is why is the wifi working on my Galaxy Trend (and also some other users).
thats not logic
i have a (maybe) a fix:
my wifi is working, so i can make (after vacation) a nandroid backup (twrp 2.7) of cm10.2, cm11 and PAC 4.4.4 and upload them i hope that it would fix it
Sent from my GT-S7560M using XDA Premium 4 mobile app

Anas Karbila said:
If the wifi problem hardware related is why is the wifi working on my Galaxy Trend (and also some other users).
thats not logic
i have a (maybe) a fix:
my wifi is working, so i can make (after vacation) a nandroid backup (twrp 2.7) of cm10.2, cm11 and PAC 4.4.4 and upload them i hope that it would fix it
Click to expand...
Click to collapse
my question:
How could we read the poper hardware specs of the WiFi module to compare it?
I found this on StackExchange to get NIC id with dmesg, but I can't figure out what could be my wifi module maybe you can:
Code:
[email protected]:/ # dmesg | grep -i lan
<4>[ 2.160213] wlan_status entered
<4>[ 2.160226] (wlan_status) entered GPIO_RESET_VAL=0
<4>[ 2.160678] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c0095620>] (wlan_suspend_gpio_config+0x34/0x7c)
<4>[ 2.160713] [<c0095620>] (wlan_suspend_gpio_config+0x34/0x7c) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.160748] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.161354] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c009562c>] (wlan_suspend_gpio_config+0x40/0x7c)
<4>[ 2.161388] [<c009562c>] (wlan_suspend_gpio_config+0x40/0x7c) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.161421] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.161971] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c0095638>] (wlan_suspend_gpio_config+0x4c/0x7c)
<4>[ 2.162004] [<c0095638>] (wlan_suspend_gpio_config+0x4c/0x7c) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.162036] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.162588] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c0095644>] (wlan_suspend_gpio_config+0x58/0x7c)
<4>[ 2.162621] [<c0095644>] (wlan_suspend_gpio_config+0x58/0x7c) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.162653] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.163204] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c0095650>] (wlan_suspend_gpio_config+0x64/0x7c)
<4>[ 2.163238] [<c0095650>] (wlan_suspend_gpio_config+0x64/0x7c) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.163271] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.163819] [<c022d160>] (gpio_direction_output+0x84/0x154) from [<c00956a4>] (wlan_status+0x3c/0x50)
<4>[ 2.163851] [<c00956a4>] (wlan_status+0x3c/0x50) from [<c0397760>] (msmsdcc_probe+0xaa0/0x120c)
<4>[ 2.164188] register_wlan_status_notify --enter<4>[ 5.785766] ebi_grp_3d_clk is unbalanced
<6>[ 7.709036] SDCC CH 2 : msmsdcc_runtime_suspend WLAN SKIP Suspend
<6>[ 26.796343] wlan_setup_ldo_33v - set by BT : on<6>[ 26.796349] wlan_setup_ldo_33v - old wlan_33v_flag : 0
<6>[ 26.796356] wlan_setup_ldo_33v - new wlan_33v_flag : 2
<4>[ 26.796364] wlan_set_gpio - 109 : on
<6>[ 26.796376] wlan_set_gpio: before (1) :: gpio_get_value = 0
<6>[ 26.796393] wlan_set_gpio: after (1) :: gpio_get_value = 1
<6>[ 28.849579] wlan_setup_ldo_33v - set by BT : off
<6>[ 28.849588] wlan_setup_ldo_33v - old wlan_33v_flag : 2
<6>[ 28.849594] wlan_setup_ldo_33v - new wlan_33v_flag : 0
<4>[ 28.849603] wlan_set_gpio - 109 : off
<6>[ 28.849614] wlan_set_gpio: before (0) :: gpio_get_value = 1
<6>[ 28.849631] wlan_set_gpio: after (0) :: gpio_get_value = 0
<4>[ 34.540856] ath6kl_pm_probe()wlan_setup_power on --enter
<6>[ 34.540869] wlan_setup_ldo_33v - set by Wifi : on
<6>[ 34.540876] wlan_setup_ldo_33v - old wlan_33v_flag : 0
<6>[ 34.540883] wlan_setup_ldo_33v - new wlan_33v_flag : 1
<4>[ 34.540891] wlan_set_gpio - 109 : on
<6>[ 34.540904] wlan_set_gpio: before (1) :: gpio_get_value = 0
<6>[ 34.540919] wlan_set_gpio: after (1) :: gpio_get_value = 1wlan_set_gpio - 33 : on
<6>[ 34.541169] wlan_set_gpio: before (1) :: gpio_get_value = 0
<6>[ 34.541181] wlan_set_gpio: after (1) :: gpio_get_value = 1
<6>[ 34.541273] WLAN: wake lock timeout 0.5 sec...
<4>[ 34.669293] wlan_status entered
<4>[ 34.669314] (wlan_status) entered GPIO_RESET_VAL=1
<6>[ 34.669366] SDCC CH 2 : msmsdcc_runtime_resume WLAN SKIP Resume
<7>[ 34.856439] ath6kl: ath6kl_core_init: name=wlan0 dev=0xd0c35000, ar=0xca0c8ae0
<7>[ 35.600853] ath6kl: ath6kl_target_config_wlan_params() vif_index=1 is not yet added
<3>[ 35.768514] init: cannot find '/system/bin/wlan_tool', disabling 'wlan_tool'
<6>[ 36.329033] ADDRCONF(NETDEV_UP): wlan0: link is not ready
<6>[ 37.606724] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<7>[ 47.724691] wlan0: no IPv6 routers present
hhpss

[Q] Random power offs

Hi, I have xperia zl and yesterday accidentally magnet touched my zl...screen turned off and after that it powered on and worked but there were some errors in dmesg. Now it is randomly(or not, I think only when it is a bit overloaded) powering off but if I connect it to to pc it is not rebooting but some strange stuff appears in dmesg ( http://pastebin.com/pckHxMZF ). Any suggestions? Thanks
Also i`m using cm11.0
UPD: Connected with adb over network and waited untill it reboots, here are last lines of dmesg
Code:
<3>[ 400.473968] wlan: [4146:E :HDD] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
<3>[ 426.057586] wlan: [4162:E :SME] sme_FTUpdateKey: Unhandled state=0
<3>[ 440.554016] wlan: [4146:E :HDD] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
<6>[ 453.081512] mdm_status_change: unexpected reset external modem id 0
<6>[ 453.086883] mdm_start_ssr: Resetting mdm id 0 due to mdm error
<6>[ 453.092590] subsys-restart: subsystem_restart_dev(): Restart sequence requested for external_modem, restart_level = 3.
<6>[ 453.103515] subsys-restart: subsystem_shutdown(): [e9fc3480]: Shutting down external_modem
And looks like my wlan0 mac address changed
Found something here - http://forum.xda-developers.com/xperia-z/help/xperia-zbricked-wi-fi-t2409804/page3
It is wifi related, maybe that`s why my mac changed
Now this is dmesg before shutting down:
Code:
<4>[ 229.088745] CPU1 didn't collape within 1ms
<4>[ 229.092071] Modules linked in: wlan(C)
<4>[ 229.096557] [<c010c470>] (unwind_backtrace+0x0/0x11c) from [<c017d1ac>] (warn_slowpath_common+0x4c/0x64)
<4>[ 229.105804] [<c017d1ac>] (warn_slowpath_common+0x4c/0x64) from [<c017d244>] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 229.116027] [<c017d244>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0150f28>] (msm_pm_wait_cpu_shutdown+0xa8/0xc4)
<4>[ 229.126922] [<c0150f28>] (msm_pm_wait_cpu_shutdown+0xa8/0xc4) from [<c011e8dc>] (platform_cpu_kill+0x20/0x30)
<4>[ 229.136749] [<c011e8dc>] (platform_cpu_kill+0x20/0x30) from [<c010b214>] (__cpu_die+0x4c/0x78)
<4>[ 229.145019] [<c010b214>] (__cpu_die+0x4c/0x78) from [<c08a2e24>] (_cpu_down+0x118/0x214)
<4>[ 229.152648] [<c08a2e24>] (_cpu_down+0x118/0x214) from [<c08a2f44>] (cpu_down+0x24/0x40)
<4>[ 229.160644] [<c08a2f44>] (cpu_down+0x24/0x40) from [<c08a46b4>] (store_online+0x2c/0x78)
<4>[ 229.168914] [<c08a46b4>] (store_online+0x2c/0x78) from [<c049fa78>] (dev_attr_store+0x18/0x24)
<4>[ 229.177307] [<c049fa78>] (dev_attr_store+0x18/0x24) from [<c028a3f4>] (sysfs_write_file+0x100/0x148)
<4>[ 229.186981] [<c028a3f4>] (sysfs_write_file+0x100/0x148) from [<c023a0f8>] (vfs_write+0xa8/0x180)
<4>[ 229.195220] [<c023a0f8>] (vfs_write+0xa8/0x180) from [<c023a3e8>] (sys_write+0x34/0x68)
<4>[ 229.203155] [<c023a3e8>] (sys_write+0x34/0x68) from [<c0106120>] (ret_fast_syscall+0x0/0x30)
<4>[ 229.212249] ---[ end trace da227214a82491c7 ]---
<4>[ 237.840850] ------------[ cut here ]------------
<4>[ 237.844879] WARNING: at ../../../../../../kernel/sony/apq8064/arch/arm/mach-msm/pm-8x60.c:995 msm_pm_wait_cpu_shutdown+0xa8/0xc4()
<4>[ 237.857116] CPU1 didn't collape within 1ms
<4>[ 237.860595] Modules linked in: wlan(C)
<4>[ 237.864349] [<c010c470>] (unwind_backtrace+0x0/0x11c) from [<c017d1ac>] (warn_slowpath_common+0x4c/0x64)
<4>[ 237.873840] [<c017d1ac>] (warn_slowpath_common+0x4c/0x64) from [<c017d244>] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 237.883880] [<c017d244>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0150f28>] (msm_pm_wait_cpu_shutdown+0xa8/0xc4)
<4>[ 237.893402] [<c0150f28>] (msm_pm_wait_cpu_shutdown+0xa8/0xc4) from [<c011e8dc>] (platform_cpu_kill+0x20/0x30)
<4>[ 237.906341] [<c011e8dc>] (platform_cpu_kill+0x20/0x30) from [<c010b214>] (__cpu_die+0x4c/0x78)
<4>[ 237.914611] [<c010b214>] (__cpu_die+0x4c/0x78) from [<c08a2e24>] (_cpu_down+0x118/0x214)
<4>[ 237.922973] [<c08a2e24>] (_cpu_down+0x118/0x214) from [<c08a2f44>] (cpu_down+0x24/0x40)
<4>[ 237.930145] [<c08a2f44>] (cpu_down+0x24/0x40) from [<c08a46b4>] (store_online+0x2c/0x78)
<4>[ 237.938812] [<c08a46b4>] (store_online+0x2c/0x78) from [<c049fa78>] (dev_attr_store+0x18/0x24)
<4>[ 237.946838] [<c049fa78>] (dev_attr_store+0x18/0x24) from [<c028a3f4>] (sysfs_write_file+0x100/0x148)
<4>[ 237.956481] [<c028a3f4>] (sysfs_write_file+0x100/0x148) from [<c023a0f8>] (vfs_write+0xa8/0x180)
<4>[ 237.964721] [<c023a0f8>] (vfs_write+0xa8/0x180) from [<c023a3e8>] (sys_write+0x34/0x68)
<4>[ 237.972595] [<c023a3e8>] (sys_write+0x34/0x68) from [<c0106120>] (ret_fast_syscall+0x0/0x30)
<4>[ 237.982147] ---[ end trace da227214a82491c8 ]---
<3>[ 245.350189] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
<3>[ 245.356719] afe_callback: cmd = 0x100dc returned error = 0x3
<3>[ 245.362152] afe_send_hw_delay: config cmd failed
<6>[ 250.620727] SLIM_CL: skip reconfig sequence
<3>[ 250.700622] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
<3>[ 250.707305] afe_callback: cmd = 0x100dc returned error = 0x3
<3>[ 250.712829] afe_send_hw_delay: config cmd failed
<6>[ 254.915313] SLIM_CL: skip reconfig sequence
<3>[ 258.102020] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
<3>[ 258.109100] afe_callback: cmd = 0x100dc returned error = 0x3
<3>[ 258.114227] afe_send_hw_delay: config cmd failed
<6>[ 275.903686] msm_vidc_dec: Inside vid_dec_open()
<4>[ 275.907257]
<4>[ 275.907257] res_trk_download_firmware(): Request firmware download
<4>[ 275.949737]
<4>[ 275.949737] VIDC: vidc_freq = 266670000, req_perf_lvl = 244801, set_perf_lvl = 244801
<3>[ 275.965454] Rate 266670000 for vcodec_clk is greater than highest Fmax
<6>[ 275.984374] fw_version 8:30:2013
<4>[ 276.108154]
<4>[ 276.108154] VIDC: vidc_freq = 200000000, req_perf_lvl = 244800, set_perf_lvl = 244800
<6>[ 276.118316] WARNING: H264MaxLevelExceeded : 51
<6>[ 276.121643] profile 4 level 0 progressive 1
<4>[ 276.125823]
<4>[ 276.125854] VIDC: vidc_freq = 200000000, req_perf_lvl = 244800, set_perf_lvl = 244800
<4>[ 276.135559]
<4>[ 276.135589] VIDC: vidc_freq = 200000000, req_perf_lvl = 187680, set_perf_lvl = 244800

Do your have any installs or changes last time?
If yes - first method it is facotury defaults, or backup. Maybe you can only remove last installs..
Second - it hardware problem... power controller, maybe, or usb block

freask5 said:
Do your have any installs or changes last time?
If yes - first method it is facotury defaults, or backup. Maybe you can only remove last installs..
Second - it hardware problem... power controller, maybe, or usb block
Click to expand...
Click to collapse
Replacing battery helped

suleymanovemil8 said:
Replacing battery helped
Click to expand...
Click to collapse
Great)) Congratulations))