I have TF700 Infinity with Cromi-X 4.6.9 installed, running hundsbuah's 3.0.6 kernel with Data2SD enabled. I use SanDisk 32GB Mobile Ultra Micro SDHC card, formatted using gparted on Parted Magic linux. Fsync is enabled.
I noticed that my experience with Data2SD is deteriorating. Fresh after formatting Micro SD it works perfectly fine, but after week or two some random freezes start to occur (most often when running app's but sometimes even at lockscreen) forcing me to reboot. With more number of reboots freezes get more often after I'm desperate enough to format Micro SD again and reinstall. I've been trying with _that kernel, but it was no difference. Is that a problem of my SD Card or with Infinity? How can I fix it?
Here is the part of content of last_kmsg
Code:
[ 1789.970823] Switched to NOHz mode on CPU #1
[ 1792.498820] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 1792.971434] cpu_down(3)+
[ 1792.973679] CPU3: shutdown
[ 1792.975627] edp_update_limit: Limiting cpu speed from 1500000 to 1500000 during boot!
[ 1792.976218] cpu_down(3)-
[ 1794.117317] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 1794.841849] cpu ext_temperature=37
[ 1795.971717] cpu_down(2)+
[ 1795.975049] CPU2: shutdown
[ 1795.977786] edp_update_limit: Limiting cpu speed from 1500000 to 1500000 during boot!
[ 1795.978965] cpu_down(2)-
[ 1797.990758] mmcblk1: error -110 transferring data, sector 36657736, nr 344, cmd response 0x900, card status 0xb00
[ 1797.991805] mmcblk1: retrying using single block read
[ 1798.981523] cpu_down(1)+
[ 1798.982526] CPU1: shutdown
[ 1798.983655] edp_update_limit: Limiting cpu speed from 1600000 to 1500000 during boot!
[ 1798.984118] cpu_down(1)-
[ 1799.638992] mmcblk1: error -110 transferring data, sector 36657736, nr 344, cmd response 0x900, card status 0x0
[ 1799.639284] [mmc]:mmc_blk_issue_rw_rq:1101 SD freq. down to UHS_SDR12_MAX_DTR
[ 1799.642246] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1799.642518] mmcblk1: command error, retrying timeout
[ 1800.322357] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 1802.446926] mmcblk1: error -110 transferring data, sector 36657737, nr 343, cmd response 0x900, card status 0xb00
[ 1802.449065] mmcblk1: retrying using single block read
[ 1804.863463] cpu ext_temperature=34
[ 1805.248817] mmcblk1: error -110 transferring data, sector 36657737, nr 343, cmd response 0x900, card status 0x0
[ 1805.251672] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1805.251929] mmcblk1: command error, retrying timeout
[ 1808.053001] mmcblk1: error -110 transferring data, sector 36657738, nr 342, cmd response 0x900, card status 0xb00
[ 1808.053064] mmcblk1: retrying using single block read
[ 1810.851446] mmcblk1: error -110 transferring data, sector 36657738, nr 342, cmd response 0x900, card status 0x0
[ 1810.853818] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1810.853875] mmcblk1: command error, retrying timeout
[ 1813.657813] mmcblk1: error -110 transferring data, sector 36657739, nr 341, cmd response 0x900, card status 0xb00
[ 1813.659954] mmcblk1: retrying using single block read
[ 1814.883548] cpu ext_temperature=32
[ 1816.459651] mmcblk1: error -110 transferring data, sector 36657739, nr 341, cmd response 0x900, card status 0x0
[ 1816.462061] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1816.462161] mmcblk1: command error, retrying timeout
[ 1818.411499] gpio_keys: Pressed KEY_POWER
[ 1819.262896] mmcblk1: error -110 transferring data, sector 36657740, nr 340, cmd response 0x900, card status 0xb00
[ 1819.263004] mmcblk1: retrying using single block read
[ 1822.059974] mmcblk1: error -110 transferring data, sector 36657740, nr 340, cmd response 0x900, card status 0x0
[ 1822.067079] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1822.069317] mmcblk1: command error, retrying timeout
[ 1824.877483] mmcblk1: error -110 transferring data, sector 36657741, nr 339, cmd response 0x900, card status 0xb00
[ 1824.879788] mmcblk1: retrying using single block read
[ 1824.902545] cpu ext_temperature=31
13422 Corrected bytes, 16 unrecoverable blocks
Also after last reinstall I noticed that I can't access ext4 partition of my sdcard. In /storage I see emulated, sdcard0 and sdcard1. Emulated and sdcard0 lead to data that are on my internal sdcard, sdcard1 is empty. However, data2SD is working, because i tested with androbench and the random write speed is 0.3-0.4Mbps and when I removed the Micro SD card from a slot the system booted with all my apps gone, so it made me sure, that my regular installation is on external sd.
"error -110 transferring data" and "timed out sending r/w cmd" indicates problems with your card. The TF700 is known to have troubles with fast microSD cards - some work reliably, some don't.
_that said:
"error -110 transferring data" and "timed out sending r/w cmd" indicates problems with your card. The TF700 is known to have troubles with fast microSD cards - some work reliably, some don't.
Click to expand...
Click to collapse
Well, the card is SanDisk Mobile Ultra, which worked nice for many people from what I've read. Anyway, I think I managed to solve the problem. I've read in one of threads that formatting to ext2 instead of ext4 might work better, so I tried it and so far so good.
Just if someone has simmilar problem - try ext2.
Arquiteto said:
Well, the card is SanDisk Mobile Ultra, which worked nice for many people from what I've read. Anyway, I think I managed to solve the problem. I've read in one of threads that formatting to ext2 instead of ext4 might work better, so I tried it and so far so good.
Just if someone has simmilar problem - try ext2.
Click to expand...
Click to collapse
I had a similar problem with crashing and freezing using Data2SD but I think it was because of a defective card. Since then, I tried using the CROMI-X without data2sd and I was surprised I was still satisfied with the response and speed of the tablet. Data2SD still might be a little bit faster but in my opinion the differences are not that noticeable anymore.
lasallegreen said:
I had a similar problem with crashing and freezing using Data2SD but I think it was because of a defective card. Since then, I tried using the CROMI-X without data2sd and I was surprised I was still satisfied with the response and speed of the tablet. Data2SD still might be a little bit faster but in my opinion the differences are not that noticeable anymore.
Click to expand...
Click to collapse
I think that all the advances made in kernel development and rom tweaks that data2sd is not as beneficial as it used to be
Arquiteto said:
Just if someone has simmilar problem - try ext2.
Click to expand...
Click to collapse
Thanks for the advice. Could you do us all a favor and report back in a week or so? This seems like a useful thing to document.
B00T_Sp0rk said:
Thanks for the advice. Could you do us all a favor and report back in a week or so? This seems like a useful thing to document.
Click to expand...
Click to collapse
Reporting back:
It looked like the problem was solved, as it worked fine... for a few days. And then it was all over again, so I guess the problem is the MicroSD Card after all. However it was a little better with ext2 the freezes returned so I dumped data2sd. My Infinity is now a bit slower, but at least it's stable. I got the freeze one more time without data2sd (checked the last_kmsg it was -110 error) but I'm using it for few days and it was the only time it happened.
You think that I might get a replacement MicroSD from SanDisk if I sent it back?
Arquiteto said:
Reporting back:
It looked like the problem was solved, as it worked fine... for a few days. And then it was all over again, so I guess the problem is the MicroSD Card after all. However it was a little better with ext2 the freezes returned so I dumped data2sd. My Infinity is now a bit slower, but at least it's stable. I got the freeze one more time without data2sd (checked the last_kmsg it was -110 error) but I'm using it for few days and it was the only time it happened.
You think that I might get a replacement MicroSD from SanDisk if I sent it back?
Click to expand...
Click to collapse
You may have a system problem rather than the external SD. Without data2sd, your system still caused the same problem. If you don't have any other solution, you may want to format your internal SD and start out fresh. I use 64G Samsung class 10 and it works fine with data2sd. Good luck.
LetMeKnow said:
You may have a system problem rather than the external SD. Without data2sd, your system still caused the same problem. If you don't have any other solution, you may want to format your internal SD and start out fresh. I use 64G Samsung class 10 and it works fine with data2sd. Good luck.
Click to expand...
Click to collapse
The problem looked the same, as it was -110, but might have been for different reason. And it havn't occured ever again so far, while with data2sd I had it few times a day after a while, so I guess it is the external SD fault after all.
I wonder why the manufacturers and users doesn't bother about the speed of internal memory. OFC most people look at the CPU, GPU and resolution when they buy tablets, but the speed of memory is also important parameter, especially in high-end devices.
Arquiteto said:
The problem looked the same, as it was -110, but might have been for different reason. And it havn't occured ever again so far, while with data2sd I had it few times a day after a while, so I guess it is the external SD fault after all.
I wonder why the manufacturers and users doesn't bother about the speed of internal memory. OFC most people look at the CPU, GPU and resolution when they buy tablets, but the speed of memory is also important parameter, especially in high-end devices.
Click to expand...
Click to collapse
I thought that you still have the same problem without the data2sd but it only happened once then you probably right about the defected external sd. I totally agree with you about the overall design of this tablet if it is intended for a high performance device but one year ago the technical specification was very impressive comparing with other product lines on the market. So to answer your question, I use it for an entertainment when I travel to kill time at the airport and check my personal email at the hotel. I don't expect much out of it and so far it does what it is supposed to do except for the slow internet. I found a solution with a custom rom...:good: I don't know what other users use it for and why manufacturer came up with that designed concept. I am guessing that they want more profit out of this product maybe.
I've installed the newest build for Cyanogengmod 11 that supports my exact phone (XT897c) and it works great. I've only been using it for a few days now and haven't ran into any major issues but one. The problem I continue to have is I cannot install Gapps and have the phone work properly. Everytime I install the correct Gapps (or any other variant for that matter) the phone stays locked up at the initial Motorola boot logo and will never continue loading. I've redownloaded and reinstalled both CM11 and various Gapps KK from different sites and methods without fixing the problem. Anyone have a suggestion?
sulken2000 said:
I've installed the newest build for Cyanogengmod 11 that supports my exact phone (XT897c) and it works great. I've only been using it for a few days now and haven't ran into any major issues but one. The problem I continue to have is I cannot install Gapps and have the phone work properly. Everytime I install the correct Gapps (or any other variant for that matter) the phone stays locked up at the initial Motorola boot logo and will never continue loading. I've redownloaded and reinstalled both CM11 and various Gapps KK from different sites and methods without fixing the problem. Anyone have a suggestion?
Click to expand...
Click to collapse
Download these cm11 gapps from dhacker29 (supports both dalvik and art).
Install CM11. let it boot
Install gapps. reboot which will probably fail.
if the above failed: re-install cm11, wipe cache/dalvik and reboot.
sulken2000 said:
I've installed the newest build for Cyanogengmod 11 that supports my exact phone (XT897c) and it works great. I've only been using it for a few days now and haven't ran into any major issues but one. The problem I continue to have is I cannot install Gapps and have the phone work properly. Everytime I install the correct Gapps (or any other variant for that matter) the phone stays locked up at the initial Motorola boot logo and will never continue loading. I've redownloaded and reinstalled both CM11 and various Gapps KK from different sites and methods without fixing the problem. Anyone have a suggestion?
Click to expand...
Click to collapse
If you're using xt897c CM11 build, you're using very outdated build.
Your exact phone is not xt897c, you have just xt897, as anyone else.
There's no such thing as xt897c phone, xt897c is something I've made up as a temporary measure until we'll be able to do a single world-phone build that will support both GSM and CDMA networks.
Since long time ago, xt897 (gsm) and xt897c (cdma) builds have been unified into a single xt897 (world phone) build which made xt897c builds obsolete.
Later on, the builds for the whole 1st gen family of Motorola msm8960 devices (razr hd, razr m, atrix hd, electrify m and photon q) have been unified into a single moto_msm8960 build. All those devices are very similar and have used a single common kernel from the beginning, since the CM 10.1 time).
If you want to install CM11 on your phone, you should install this:
http://download.cyanogenmod.org/?device=moto_msm8960
Any other CM11 build is obsolete.
Links to recommended CM 11 gapps can be found here:
http://wiki.cyanogenmod.org/w/Gapps
mrvek said:
Download these cm11 gapps from dhacker29 (supports both dalvik and art).
Install CM11. let it boot
Install gapps. reboot which will probably fail.
if the above failed: re-install cm11, wipe cache/dalvik and reboot.
Click to expand...
Click to collapse
I did in fact, download, redownload, install, reinstall, the Gapps from the link you provided, and got no advancements =( Unfortunately, I'll have to start all over from scratch most likely. I really appreciate your prompt response.
kabaldan said:
If you're using xt897c CM11 build, you're using very outdated build.
Your exact phone is not xt897c, you have just xt897, as anyone else.
There's no such thing as xt897c phone, xt897c is something I've made up as a temporary measure until we'll be able to do a single world-phone build that will support both GSM and CDMA networks.
Since long time ago, xt897 (gsm) and xt897c (cdma) builds have been unified into a single xt897 (world phone) build which made xt897c builds obsolete.
Later on, the builds for the whole 1st gen family of Motorola msm8960 devices (razr hd, razr m, atrix hd, electrify m and photon q) have been unified into a single moto_msm8960 build. All those devices are very similar and have used a single common kernel from the beginning, since the CM 10.1 time).
If you want to install CM11 on your phone, you should install this:
http://download.cyanogenmod.org/?device=moto_msm8960
Any other CM11 build is obsolete.
Links to recommended CM 11 gapps can be found here:
http://wiki.cyanogenmod.org/w/Gapps
Click to expand...
Click to collapse
That version still didn't work with Gapps. I've tried the many different ways of clearing cache, system, data, dalvik cache, etc etc. Nothing gets me past the Moto Logo. But, I've made another discovery, once I've installed CM11 on my phone, regardless of which of the two, once the phone has been turned off, it won't properly boot back up because it stays stuck that the Moto logo. The version you suggested loaded properly without Gapps installed just as the xt897c version did. But they both have the same "only works the first time no rebooting allowed" problem and neither work with Gapps.
One thing to note, I've used the CM10.1.3 (Stable) listed in the "xt897c" category as well as the Gapps (20130812) from the cyanogenmod website. Its what gave me the idea that my only option for CM via the CM website is the "xt897c" since that version of CM works flawlessly with Gapps installed (minus the lack of proper data connection (C Spire version) due to the rom having Sprint connection settings)
p.s. that is something I've been trying to search and "fix" for ages. I really hate being with a "lesser" company (C Spire) because of the lack of aftermarket and development support.
sulken2000 said:
That version still didn't work, I've tried the many different ways of clearing cash,system,data,dalvik,cache, etc etc. Nothing gets me past the Moto Logo. Hope there is another way.
One thing to note, I've used the CM10.1.3 (Stable) listed in the "xt897c" category as well as the Gapps (20130812) from the cyanogenmod website. Its what gave me the idea that my only option for CM via the CM website is the "xt897c" since that version of CM works flawlessly with Gapps installed (minus the lack of proper data connection (C Spire version) due to the rom having Sprint connection settings)
p.s. that is something I've been trying to search and "fix" for ages. I really hate being with a "lesser" company (C Spire) for the lack of aftermarket and development support.
Click to expand...
Click to collapse
Please, post the the info I requested here:
http://forum.xda-developers.com/showthread.php?t=2656570
I'm still waiting for any C Spire Photon Q owner to respond, so I could finally add the support for C Spire variant of XT897 to CM 11.0 moto_msm8960 unified builds.
Thanks.
kabaldan said:
Please, post the the info I requested here:
http://forum.xda-developers.com/showthread.php?t=2656570
I'm still waiting for any C Spire Photon Q owner to respond, so I could finally add the support for C Spire variant of XT897 to CM 11.0 moto_msm8960 unified builds.
Thanks.
Click to expand...
Click to collapse
Thanks for the prompt response. I have definitely come across that post in the past few days while trying to fix this irritating problem. I'll do some research to learn how to do that first and try to get you that info asap.
sulken2000 said:
...both have the same "only works the first time no rebooting allowed" problem and neither work with Gapps.
...
Click to expand...
Click to collapse
I noticed your remark above only now.
The symptom you mention seems to be caused by formatting of /data partition by recovery, which causes some not yet preciously determined filesystem corruption.
The second boot seems to be stalled, but what actually happens is that /data filesystem check and repair is running. And this repair will eventually finish, even though it can take tens of minutes. After the repair is done, the Android system boots fine and subsequent reboots are fine and fast.
Which recovery are you using? I use OpenRecovery 2.09 ( http://forum.xda-developers.com/showthread.php?t=2211579 ; see the last pages of the thread for a working download link), which actually does not re-format the /data partition filesystem when you do a data wipe/factory reset, it just deletes the content of the partition. So when using OpenRecovery, this corruption should not happen.
TWRP2.7.0.1
Sadly I'm also having troubles with my second Photon Q, this time from CSpire. Like Sulken's phone (also from CSpire) it doesn't survive reboot - however mine stops on unlocked bootloader warning. I was flashing Carbon 4.4 and suggested GAPPS first, but it wierdly let me send&receive smses and call people while on GSM network, however nobody could call me - line was busy. So I tried with CM11 and here everything is fine, however it also didn't survive reboot. On my first photon I always used TWRP but on this one, from CSpire, it cannot do factory reset - reboots on /data wiping, so I'm using OpenRecovery 2.09 now. Another very weird thing is that the phone won't boot after reflashing custom ROM. I'm doing a factory reset, flashing once again for example CM11 and it won't pass the unlocked bootloader warning, so I have to first do RSDLite+stock CSpire ROM and then flash CM11 once again, and then it works as long as I don't reboot...
I can't believe that nobody before tried SIM-mod & custom ROM on PhotonQ from CSpire... What's wrong? :/
micx_pl said:
Sadly I'm also having troubles with my second Photon Q, this time from CSpire. Like Sulken's phone (also from CSpire) it doesn't survive reboot - however mine stops on unlocked bootloader warning. I was flashing Carbon 4.4 and suggested GAPPS first, but it wierdly let me send&receive smses and call people while on GSM network, however nobody could call me - line was busy. So I tried with CM11 and here everything is fine, however it also didn't survive reboot. On my first photon I always used TWRP but on this one, from CSpire, it cannot do factory reset - reboots on /data wiping, so I'm using OpenRecovery 2.09 now. Another very weird thing is that the phone won't boot after reflashing custom ROM. I'm doing a factory reset, flashing once again for example CM11 and it won't pass the unlocked bootloader warning, so I have to first do RSDLite+stock CSpire ROM and then flash CM11 once again, and then it works as long as I don't reboot...
I can't believe that nobody before tried SIM-mod & custom ROM on PhotonQ from CSpire... What's wrong? :/
Click to expand...
Click to collapse
See my comment here: https://jira.cyanogenmod.org/browse...issuetabpanels:comment-tabpanel#comment-25465
How long have you let the phone to sit at the boot screen after the first reboot from working CM11?
(Make sure the battery is near full and keep the phone plugged to USB or power supply when attempting to wait over this stalled boot.)
If you want to get some information about what's going on while the boot is stalled, you should force a reboot by holding power button while waiting at the boot logo for some time already and also hold the volume-up button to reboot directly to recovery. Then post the content of /proc/last_kmsg captured via adb while the phone is in recovery after this forced reboot.
Code:
adb pull /proc/last_kmsg
Output of /proc/last_kmsg:
Code:
[ 0.211841,0] mot_init_factory_kill: Factory Kill Circuit: enabled
[ 0.221303,0] select_freq_plan: ACPU PVS: Fast
[ 0.221394,0] select_freq_plan: Max ACPU freq: 1512000 KHz
[ 0.224599,0] cpufreq_table_init: CPU0: 12 scaling frequencies supported.
[ 0.224721,0] cpufreq_table_init: CPU1: 12 scaling frequencies supported.
/////////////////////// CUT /////////////////////////
[ 0.946711,0] i2c-core: driver [tabla-i2c-core] using legacy suspend method
[ 0.946772,0] i2c-core: driver [tabla-i2c-core] using legacy resume method
[ 0.947352,0] Loading pn544 driver
[ 0.947443,0] pn544_probe : Probing pn544 driver
[ 0.947627,0] pn544_probe : PN544 Misc Minor: 26
[ 0.947718,0] pn544_probe : requesting IRQ 394
[ 0.948206,0] SCSI Media Changer driver v0.25
[ 0.948939,0] PPP generic driver version 2.4.2
[ 0.949092,0] PPP Deflate Compression module registered
[ 0.949183,0] PPP BSD Compression module registered
[ 0.949824,0] PPP MPPE Compression module registered
[ 0.949885,0] NET: Registered protocol family 24
[ 0.950007,0] SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256) (6 bit encapsulation enabled).
[ 0.950129,0] CSLIP: code copyright 1989 Regents of the University of California.
[ 0.950465,0] tun: Universal TUN/TAP device driver, 1.6
[ 0.950587,0] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
[ 0.951228,0] usbcore: registered new interface driver asix
[ 0.951381,0] usbcore: registered new interface driver cdc_ether
[ 0.951472,0] usbcore: registered new interface driver net1080
[ 0.951625,0] usbcore: registered new interface driver cdc_subset
[ 0.951777,0] usbcore: registered new interface driver zaurus
[ 0.951869,0] usbcore: registered new interface driver MOSCHIP usb-ethernet driver
[ 0.951991,0] cdc_ncm: 04-Aug-2011
[ 0.952083,0] usbcore: registered new interface driver cdc_ncm
[ 0.952235,0] usbcore: registered new interface driver rmnet_usb
[ 0.952601,0] rmnet usb ctrl Initialized.
[ 0.952723,0] wcnss_wlan probed in built-in mode
[ 0.953151,0] rmnet_init: BAM devices[8]
[ 0.955989,0] msm_otg msm_otg: msm_otg probe
[ 0.956142,0] msm_otg msm_otg: OTG regs = e18a8000
[ 0.958492,0] msm_otg_probe: MSM OTG Driver will operate in ACCY CONTROL mode
[ 0.958614,0] msm_otg_init_sm: setting default inputs for ACCY mode
[ 0.959072,0] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.959621,0] usbcore: registered new interface driver cdc_acm
[ 0.959682,0] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 0.959865,0] usbcore: registered new interface driver usblp
[ 0.959926,0] Initializing USB Mass Storage driver...
[ 0.960079,0] usbcore: registered new interface driver usb-storage
[ 0.960140,0] USB Mass Storage support registered.
[ 0.960262,0] usbcore: registered new interface driver ums-alauda
[ 0.960384,0] usbcore: registered new interface driver ums-cypress
[ 0.960537,0] usbcore: registered new interface driver ums-datafab
[ 0.960689,0] usbcore: registered new interface driver ums-freecom
[ 0.960781,0] usbcore: registered new interface driver ums-isd200
[ 0.960933,0] usbcore: registered new interface driver ums-jumpshot
[ 0.961025,0] usbcore: registered new interface driver ums-karma
[ 0.961178,0] usbcore: registered new interface driver ums-onetouch
[ 0.961269,0] usbcore: registered new interface driver ums-sddr09
[ 0.961422,0] usbcore: registered new interface driver ums-sddr55
[ 0.961544,0] usbcore: registered new interface driver ums-usbat
[ 0.961727,0] usbcore: registered new interface driver usbserial
[ 0.961788,0] usbserial: USB Serial Driver core
[ 0.961941,0] USB Serial support registered for Qualcomm USB modem
[ 0.962032,0] usbcore: registered new interface driver qcserial
[ 0.962185,0] usbcore: registered new interface driver usb_ehset_test
[ 0.962307,0] usbcore: registered new interface driver diag_bridge
[ 0.962459,0] usbcore: registered new interface driver mdm_bridge
[ 0.963131,0] msm_hsusb msm_hsusb: [usb_gadget_probe_driver] hw_ep_max = 32
[ 0.964413,0] android_usb gadget: Mass Storage Function, version: 2009/09/11
[ 0.964535,0] android_usb gadget: Number of LUNs=1
[ 0.964596,0] lun0: LUN: removable file: (no medium)
[ 0.965237,0] android_usb gadget: android_usb ready
[ 0.966366,0] diagchar initialized now
[ 0.966549,0] mousedev: PS/2 mouse device common for all mice
[ 0.966854,0] gpio_set_debounce: gpio-184 status -22
[ 0.967037,0] gpio_set_debounce: gpio-11 status -22
[ 0.967312,0] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 0.967373,0] added keypad filter to input dev gpio-keys
[ 0.968533,0] input: keypad_8960 as /devices/platform/msm_ssbi.0/pm8921-core/pm8xxx-keypad/input/input1
[ 0.968655,0] added keypad filter to input dev keypad_8960
[ 0.968930,0] usbcore: registered new interface driver xpad
[ 0.969113,0] usbcore: registered new interface driver usb_acecad
[ 0.969174,0] acecad: v3.2:USB Acecad Flair tablet driver
[ 0.969327,0] usbcore: registered new interface driver aiptek
[ 0.969418,0] aiptek: v2.3 (May 2, 2007):Aiptek HyperPen USB Tablet Driver (Linux 2.6.x)
[ 0.969510,0] aiptek: Bryan W. Headley/Chris Atenasio/Cedric Brun/Rene van Paassen
[ 0.969662,0] usbcore: registered new interface driver gtco
[ 0.969723,0] GTCO usb driver version: 2.00.0006
[ 0.969845,0] usbcore: registered new interface driver hanwang
[ 0.970028,0] usbcore: registered new interface driver kbtab
[ 0.970090,0] kbtab: v0.0.2:USB KB Gear JamStudio Tablet driver
[ 0.970242,0] usbcore: registered new interface driver wacom
[ 0.970303,0] wacom: v1.52:USB Wacom tablet driver
[ 0.970517,0] atmxt_probe: Driver: atmxt-i2c, Version: YN-04-01, Date: 2012-06-28
[ 0.971799,0] atmxt_probe: Probe successful.
[ 0.972195,0] input: light-prox as /devices/virtual/input/input2
[ 0.972470,0] ct406_probe: CT406 part detected
[ 0.973416,0] input: pmic8xxx_pwrkey as /devices/platform/msm_ssbi.0/pm8921-core/pm8xxx-pwrkey/input/input3
[ 0.973935,0] using input dev keypad_8960 for key reset
[ 0.973996,0] using input dev pmic8xxx_pwrkey for key reset
[ 0.974851,0] using rtc device, pm8xxx_rtc, for alarms
[ 0.974942,0] rtc-pm8xxx rtc-pm8xxx: rtc core: registered pm8xxx_rtc as rtc0
[ 0.975309,0] i2c /dev entries driver
[ 0.975614,0] Linux media interface: v0.10
[ 0.975766,0] lirc_dev: IR Remote Control driver registered, major 235
[ 0.975888,0] IR NEC protocol handler initialized
[ 0.975949,0] IR RC5(x) protocol handler initialized
[ 0.976041,0] IR RC6 protocol handler initialized
[ 0.976102,0] IR JVC protocol handler initialized
[ 0.976224,0] IR Sony protocol handler initialized
[ 0.976285,0] IR RC5 (streamzap) protocol handler initialized
[ 0.976377,0] IR LIRC bridge handler initialized
[ 0.976438,0] Linux video capture interface: v2.00
[ 0.976590,0] usbcore: registered new interface driver uvcvideo
[ 0.976712,0] USB Video Class driver (v1.1.0)
[ 0.976987,0] ov8820_power_up R:97 P:95 D:0 A:54 1.8:8921_l29
[ 0.977109,0] ov8820_regulator_on: 8921_l29 1800000
[ 1.069922,0] ov8820 chipid: 8820
[ 1.394750,0] ov8820: match_id success
[ 1.395116,0] msm_sensor_register mctl_node_name[0] = video1
[ 1.395177,0] ov8820_power_down
[ 1.430337,0] ov8820_regulator_off: 1.8
[ 1.440500,0] mt9m114_power_up R:76 D:89 A:82 CLK:24000000
[ 1.500137,0] mt9m114 id: 2481
[ 1.500198,0] mt9m114: match_id success
[ 1.500381,0] msm_sensor_register mctl_node_name[1] = video3
[ 1.500503,0] mt9m114_power_down
[ 1.504379,0] Driver for 1-wire Dallas network protocol.
[ 1.521318,0] lm75 10-0048: hwmon0: sensor 'tmp105'
[ 1.542041,0] pm8xxx_tm_probe: OK
[ 1.542591,0] device-mapper: uevent: version 1.0.3
[ 1.542957,0] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: [email protected]
[ 1.543293,0] cpuidle: using governor ladder
[ 1.543415,0] cpuidle: using governor menu
[ 1.543781,0] mmc0: mci-version: 18
[ 1.545460,0] mmc0: bam physical base=0x12402000
[ 1.545582,0] mmc0: bam virtual base=0xe18b4000
[ 1.545643,0] mmc0: BAM device registered. bam_handle=0xe06d3a00
[ 1.545856,0] sps:REVISION of BAM 0xe18b4000 is 0x5.
[ 1.546162,0] mmc0: Qualcomm MSM SDCC-BAM at 0x0000000012402000 irq 130
[ 1.546284,0] mmc0: Qualcomm MSM SDCC-DML at 0x0000000012400800
[ 1.546375,0] mmc0: No card detect facilities available
[ 1.546650,0] mmc0: Qualcomm MSM SDCC-core at 0x0000000012400000 irq 136,0 dma -1 dmacrcri -1
[ 1.546741,0] mmc0: 8 bit data mode enabled
[ 1.546833,0] mmc0: 4 bit data mode disabled
[ 1.546894,0] mmc0: polling status mode disabled
[ 1.547016,0] mmc0: MMC clock 400000 -> 96000000 Hz, PCLK 0 Hz
[ 1.547077,0] mmc0: Slot eject status = 0
[ 1.547138,0] mmc0: Power save feature enable = 1
[ 1.547260,0] mmc0: SPS-BAM data transfer mode available
[ 1.547474,0] mmc1: mci-version: 18
[ 1.550495,0] mmc1: bam physical base=0x12182000
[ 1.550556,0] mmc1: bam virtual base=0xe18fc000
[ 1.550648,0] mmc1: BAM device registered. bam_handle=0xdff1c000
[ 1.550831,0] sps:REVISION of BAM 0xe18fc000 is 0x5.
[ 1.551106,0] mmc1: Qualcomm MSM SDCC-BAM at 0x0000000012182000 irq 128
[ 1.551228,0] mmc1: Qualcomm MSM SDCC-DML at 0x0000000012180800
[ 1.551838,0] mmc1: Qualcomm MSM SDCC-core at 0x0000000012180000 irq 134,651 dma -1 dmacrcri -1
[ 1.551899,0] mmc1: 8 bit data mode disabled
[ 1.552021,0] mmc1: 4 bit data mode enabled
[ 1.552083,0] mmc1: polling status mode disabled
[ 1.552144,0] mmc1: MMC clock 400000 -> 96000000 Hz, PCLK 0 Hz
[ 1.552235,0] mmc1: Slot eject status = 1
[ 1.552327,0] mmc1: Power save feature enable = 1
[ 1.552418,0] mmc1: SPS-BAM data transfer mode available
[ 1.552784,0] pm8xxx_rgb_led_probe: num_leds is 3
[ 1.552968,0] Registered led device: red
[ 1.553029,0] create_pm8xxx_rgb_led: LED class red, gpio 175, can sleep = 1
[ 1.553151,0] create_pm8xxx_rgb_led: requested pwm for red, pwm_id=0
[ 1.553273,0] Registered led device: green
[ 1.553334,0] create_pm8xxx_rgb_led: LED class green, gpio 176, can sleep = 1
[ 1.553456,0] create_pm8xxx_rgb_led: requested pwm for green, pwm_id=1
[ 1.553639,0] Registered led device: blue
[ 1.553700,0] create_pm8xxx_rgb_led: LED class blue, gpio 177, can sleep = 1
[ 1.553822,0] create_pm8xxx_rgb_led: requested pwm for blue, pwm_id=2
[ 1.555440,0] Registered led device: torch-flash
[ 1.557424,0] usbcore: registered new interface driver usbhid
[ 1.557485,0] usbhid: USB HID core driver
[ 1.557820,0] logger: created 1024K log 'log_main'
[ 1.557942,0] logger: created 512K log 'log_events'
[ 1.558095,0] logger: created 64K log 'log_radio'
[ 1.558248,0] logger: created 64K log 'log_system'
[ 1.558492,0] zram: num_devices not specified. Using default: 1
[ 1.558583,0] zram: Creating 1 devices ...
[ 1.559072,0] zcache: using lzo compressor
[ 1.559438,0] zcache: cleancache enabled using kernel transcendent memory and compression buddies
[ 1.559804,0] usbcore: registered new interface driver snd-usb-audio
[ 1.560781,0] tabla_probe
[ 1.561666,0] msm_pcm_probe: dev name msm-voip-dsp
[ 1.562368,0] msm_pcm_probe: dev name msm-pcm-dsp
[ 1.562612,0] msm_pcm_probe: dev name msm-multi-ch-pcm-dsp
[ 1.562856,0] msm_pcm_probe: dev name msm-lowlatency-pcm-dsp
[ 1.563619,0] msm_compr_probe: dev name msm-compr-dsp
[ 1.563985,0] msm-pcm-lpa msm-pcm-lpa: msm_pcm_probe: dev name msm-pcm-lpa
[ 1.564840,0] msm8960_configure_headset_mic_gpios: US_EURO_, AV_SWITCH gpios not configured!!!
[ 1.564962,0] msm8960_audio_init Fail to configure headset mic gpios
[ 1.753639,0] MMI Battery EEPROM Read 192 Bytes
[ 1.753761,0] MMI Battery EEPROM Page 2 Checksum = 0
[ 1.753822,0] MMI Battery EEPROM Page 3 Checksum = 0
[ 1.753883,0] MMI Battery EEPROM Copyright Valid = 1
[ 1.754005,0] MMI Battery Full Capacity 0xAE
[ 1.754066,0] MMI Battery Peak Voltage 0xB9
[ 1.754188,0] MMI Battery DC Impedance 0x5E
[ 1.754249,0] MMI Battery Cell ID 0x4157
[ 1.772531,0] asoc: snd-soc-dummy-dai <-> MultiMedia1 mapping ok
[ 1.772928,0] asoc: snd-soc-dummy-dai <-> MultiMedia2 mapping ok
[ 1.773233,0] asoc: snd-soc-dummy-dai <-> CS-VOICE mapping ok
[ 1.773630,0] asoc: snd-soc-dummy-dai <-> VoIP mapping ok
[ 1.773935,0] asoc: snd-soc-dummy-dai <-> MultiMedia3 mapping ok
[ 1.774271,0] asoc: snd-soc-dummy-dai <-> SLIMBUS0_HOSTLESS mapping ok
[ 1.774668,0] asoc: snd-soc-dummy-dai <-> INT_FM_HOSTLESS mapping ok
[ 1.774942,0] asoc: msm-stub-rx <-> msm-dai-q6.241 mapping ok
[ 1.775278,0] asoc: msm-stub-tx <-> msm-dai-q6.240 mapping ok
[ 1.775614,0] asoc: snd-soc-dummy-dai <-> MultiMedia4 mapping ok
[ 1.776010,0] asoc: snd-soc-dummy-dai <-> AUXPCM_HOSTLESS mapping ok
[ 1.776316,0] asoc: snd-soc-dummy-dai <-> HDMI_HOSTLESS mapping ok
[ 1.776682,0] asoc: snd-soc-dummy-dai <-> VoLTE mapping ok
[ 1.777018,0] asoc: snd-soc-dummy-dai <-> Voice2 mapping ok
[ 1.777353,0] asoc: snd-soc-dummy-dai <-> MultiMedia5 mapping ok
[ 1.777628,0] asoc: msm-stub-rx <-> msm-dai-q6.12288 mapping ok
[ 1.777933,0] asoc: msm-stub-tx <-> msm-dai-q6.12289 mapping ok
[ 1.778208,0] asoc: msm-stub-rx <-> msm-dai-q6.12292 mapping ok
[ 1.778513,0] asoc: msm-stub-tx <-> msm-dai-q6.12293 mapping ok
[ 1.778788,0] asoc: msm-stub-rx <-> msm-dai-q6-hdmi.8 mapping ok
[ 1.779063,0] asoc: msm-stub-rx <-> msm-dai-q6.224 mapping ok
[ 1.779337,0] asoc: msm-stub-tx <-> msm-dai-q6.225 mapping ok
[ 1.779642,0] asoc: msm-stub-rx <-> msm-dai-q6.2 mapping ok
[ 1.779917,0] asoc: msm-stub-tx <-> msm-dai-q6.3 mapping ok
[ 1.780192,0] asoc: msm-stub-rx <-> msm-dai-q6.32773 mapping ok
[ 1.780497,0] asoc: msm-stub-tx <-> msm-dai-q6.32772 mapping ok
[ 1.780802,0] asoc: msm-stub-tx <-> msm-dai-q6.32771 mapping ok
[ 1.781107,0] msm8960_audrx_init : Tabla version 2
[ 1.781413,0] tabla_codec tabla_codec: Failed to add route ANCRight Headset Mic->MIC BIAS3 Internal1
[ 1.816847,0] asoc: tabla_rx1 <-> msm-dai-q6.16384 mapping ok
[ 1.818373,0] asoc: tabla_tx1 <-> msm-dai-q6.16385 mapping ok
[ 1.818953,0] asoc: tabla_tx2 <-> msm-dai-q6.16389 mapping ok
[ 1.819471,0] asoc: tabla_rx3 <-> msm-dai-q6.16388 mapping ok
[ 1.821364,0] input: msm8960-snd-card Button Jack as /devices/platform/soc-audio.0/sound/card0/input4
[ 1.821669,0] input: msm8960-snd-card Headset Jack as /devices/platform/soc-audio.0/sound/card0/input5
[ 1.824721,0] oprofile: using arm/armv7-krait
[ 1.824965,0] GACT probability NOT on
[ 1.825057,0] Mirror/redirect action on
[ 1.825118,0] u32 classifier
[ 1.825209,0] Actions configured
[ 1.825331,0] Netfilter messages via NETLINK v0.30.
[ 1.825423,0] nf_conntrack version 0.5.0 (12661 buckets, 50644 max)
[ 1.826033,0] ctnetlink v0.93: registering with nfnetlink.
[ 1.826155,0] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
[ 1.826247,0] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
[ 1.826705,0] xt_time: kernel timezone is -0000
[ 1.826888,0] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 1.827132,0] arp_tables: (C) 2002 David S. Miller
[ 1.827285,0] TCP bic registered
[ 1.827346,0] TCP cubic registered
[ 1.827407,0] TCP htcp registered
[ 1.827529,0] Initializing XFRM netlink socket
[ 1.828139,0] NET: Registered protocol family 10
[ 1.829391,0] Mobile IPv6
[ 1.829482,0] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 1.829696,0] IPv6 over IPv4 tunneling driver
[ 1.830489,0] NET: Registered protocol family 17
[ 1.830581,0] NET: Registered protocol family 15
[ 1.830703,0] Bridge firewalling registered
[ 1.830947,0] Bluetooth: RFCOMM TTY layer initialized
[ 1.831039,0] Bluetooth: RFCOMM socket layer initialized
[ 1.831130,0] Bluetooth: RFCOMM ver 1.11
[ 1.831191,0] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 1.831313,0] Bluetooth: BNEP filters: protocol multicast
[ 1.831374,0] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1.831619,0] L2TP core driver, V2.0
[ 1.831680,0] Registering the dns_resolver key type
[ 1.831741,0] VFP support v0.3: implementor 51 architecture 64 part 4d variant 1 rev 0
[ 1.831954,0] Registering SWP/SWPB emulation handler
[ 1.841385,0] clock_late_init() disabled 199 unused clocks
[ 1.849504,0] MSM Watchdog Initialized
[ 1.854509,1] registered taskstats version 1
[ 1.855943,0] Powering up HoneyBadger
[ 1.909690,0] EMU-det(request_gpios): requesting gpio[2] EMU_SCI_OUT_GPIO-205
[ 1.909812,0] EMU-det(request_gpios): gpio 205 is IN
[ 1.909964,0] EMU-det(request_gpios): exporting gpio EMU_SCI_OUT_GPIO-205
[ 1.910056,0] EMU-det(request_gpios): couldn't find OPTIONAL EMU_ID_EN_GPIO
[ 1.910117,0] EMU-det(request_gpios): requesting gpio[0] EMU_MUX_CTRL0_GPIO-107
[ 1.910239,0] EMU-det(request_gpios): gpio 107 is OUT
[ 1.910300,0] EMU-det(request_gpios): requesting gpio[1] EMU_MUX_CTRL1_GPIO-96
[ 1.910422,0] EMU-det(request_gpios): gpio 96 is OUT
[ 1.910483,0] EMU-det(request_gpios): requesting gpio[4] SEMU_PPD_DET_GPIO-174
[ 1.910605,0] EMU-det(request_gpios): gpio 174 is IN
[ 1.910788,0] EMU-det(request_gpios): exporting gpio SEMU_PPD_DET_GPIO-174
[ 1.910849,0] EMU-det(request_gpios): requesting gpio[5] SEMU_ALT_MODE_EN_GPIO-186
[ 1.911033,0] EMU-det(request_gpios): exporting gpio SEMU_ALT_MODE_EN_GPIO-186
[ 1.911094,0] EMU-det(request_gpios): couldn't find OPTIONAL EMU_ID_GPIO
[ 1.911216,0] EMU-det(request_gpios): requesting gpio[7] DMB_PPD_DET_GPIO-204
[ 1.911338,0] EMU-det(request_gpios): gpio 204 is IN
[ 1.911460,0] EMU-det(request_gpios): exporting gpio DMB_PPD_DET_GPIO-204
[ 1.911582,0] EMU-det(request_gpios): requesting gpio[8] DPLUS_GPIO-192
[ 1.911643,0] EMU-det(request_gpios): requesting gpio[9] DMINUS_GPIO-172
[ 1.911765,0] EMU-det(request_gpios): requesting gpio[10] WHISPER_UART_TX_GPIO-18
[ 1.911857,0] EMU-det(request_gpios): gpio 18 is OUT
[ 1.911979,0] EMU-det(request_gpios): exporting gpio WHISPER_UART_TX_GPIO-18
[ 1.912101,0] EMU-det(request_gpios): requesting gpio[11] WHISPER_UART_RX_GPIO-19
[ 1.912162,0] EMU-det(request_gpios): gpio 19 is IN
[ 1.912345,0] EMU-det(request_gpios): exporting gpio WHISPER_UART_RX_GPIO-19
[ 1.912406,0] EMU-det(request_gpios): requesting gpio[12] TX_PAIR_GPIO-173
[ 1.912528,0] EMU-det(request_gpios): requesting gpio[13] RX_PAIR_GPIO-193
[ 1.912650,0] EMU-det(emu_id_protection_setup): No neccessary action
[ 1.912711,0] EMU-det(emu_det_probe): done with gpios
[ 1.933496,0] mmc0: new high speed DDR MMC card at address 0001
[ 1.934411,0] mmcblk0: mmc0:0001 008G4B 7.40 GiB
[ 1.936365,0] mmcblk0boot0: mmc0:0001 008G4B partition 1 2.00 MiB
[ 1.936975,0] mmcblk0boot1: mmc0:0001 008G4B partition 2 2.00 MiB
[ 1.937158,1] msm_otg msm_otg: phy_reset: success
[ 1.943171,0] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30 p31 p32 p33 p34 p35 p36 p37 p38 p39
[ 1.947077,0] apanic: Bound to mmc block device 'mmcblk0p33(259:1)'
[ 1.947169,0] apanic: No panic data available
[ 1.950160,0] mmcblk0boot1: unknown partition table
[ 1.953120,0] mmcblk0boot0: unknown partition table
[ 2.039859,1] EMU-det(request_irqs): requesting irq[1] EMU_SCI_OUT_GPIO-577
[ 2.040470,1] EMU-det(request_irqs): requesting irq[0] SEMU_PPD_DET_GPIO-654
[ 2.040866,1] EMU-det(emu_det_probe): done with irqs
[ 2.041233,1] EMU-det(emu_det_probe): registered callback with PM8921
[ 2.042698,1] EMU-det(emu_det_probe): EMU detection driver started
[ 2.043522,1] rtc-pm8xxx rtc-pm8xxx: setting system clock to 2014-04-06 07:20:10 UTC (1396768810)
[ 2.045444,0] Battery Cell ID Found: 3
[ 2.046909,0] read_shutdown_soc: shutdown_soc = 72
[ 2.048069,0] read_ocv_trim: program rev reg is 0x4b
[ 2.053349,0] adjust_remaining_charge_for_shutdown_soc: shutdown_soc = 72 forcing it now
[ 2.053715,0] adjust_remaining_charge_for_shutdown_soc: To force shutdown_soc = 72, rc = 1263806, pc = 72, ocv mv = 4027
[ 2.054082,0] adjust_remaining_charge_for_shutdown_soc: test revlookup pc = 73 for ocv = 4027
[ 2.054265,0] calculate_state_of_charge: Forcing SHUTDOWN_SOC = 72
[ 2.054631,0] pm8921_bms_probe: OK battery_capacity_at_boot=72 volt = 3755310 ocv = 4027000
[ 2.057652,0] get_prop_batt_status: alarm_state=0,batt_valid=0
[ 2.061193,0] pm8921_is_battery_charging: called before init
[ 2.061468,0] calculate_state_of_charge: Forcing SHUTDOWN_SOC = 72
[ 2.070502,0] get_prop_batt_status: alarm_state=0,batt_valid=0
[ 2.070837,0] get_prop_batt_status: alarm_state=0,batt_valid=0
[ 2.073462,0] calculate_state_of_charge: Forcing SHUTDOWN_SOC = 72
[ 2.083503,0] EMU-det(emu_det_vbus_state): PM8921 USBIN callback: out
[ 2.086464,0] Battery Cell ID Found: 3
[ 2.089760,0] ALSA device list:
[ 2.089913,0] #0: msm8960-snd-card
[ 2.090248,0] Warning: unable to open an initial console.
[ 2.092415,0] Freeing init memory: 992K
[ 2.108713,1] SELinux: 1024 avtab hash slots, 3544 rules.
[ 2.113749,1] SELinux: 1024 avtab hash slots, 3544 rules.
[ 2.113810,1] SELinux: 1 users, 2 roles, 344 types, 1 bools, 1 sens, 1024 cats
[ 2.114054,1] SELinux: 84 classes, 3544 rules
[ 2.114878,1] SELinux: Completing initialization.
[ 2.114970,1] SELinux: Setting up existing superblocks.
[ 2.115061,1] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[ 2.115183,1] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
[ 2.115305,1] SELinux: initialized (dev bdev, type bdev), not configured for labeling
[ 2.115428,1] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[ 2.115550,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 2.115641,1] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
[ 2.121806,1] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
[ 2.121928,1] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
[ 2.121989,1] SELinux: initialized (dev anon_inodefs, type anon_inodefs), not configured for labeling
[ 2.122112,1] SELinux: initialized (dev devpts, type devpts), uses transition SIDs
[ 2.122264,1] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
[ 2.122386,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 2.122539,1] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[ 2.129772,0] EMU-det(detection_work): state CONFIG, time since last run -297880 ms
[ 2.130169,0] EMU-det(alt_mode_setup): SEMU_ALT_MODE_EN is standard
[ 2.139783,0] EMU-det(detection_work): state SAMPLE, time since last run 10 ms
[ 2.141217,0] EMU-det(adc_vbus_get): vbus=34 mV
[ 2.199816,0] EMU-det(get_sense): SEMU_PPD_DET: ID floating
[ 2.252189,1] type=1403 audit(1396768810.700:2): policy loaded auid=4294967295 ses=4294967295
[ 2.252403,1] SELinux: Loaded policy from /sepolicy
[ 2.256493,1] SELinux: Loaded file_contexts from /file_contexts
[ 2.260247,0] EMU-det(get_sense): No need to check DMB_PPD_DET_N
[ 2.260613,0] EMU-det(sense_dp_dm): D+/D- mask: 0x10
[ 2.260827,0] EMU-det(get_sense): irq=0, SESS_END, FLOAT, NO_DCD,
[ 2.261132,0] EMU-det(detection_work): SAMPLE keep waiting ...
[ 2.269952,0] EMU-det(detection_work): state SAMPLE, time since last run 130 ms
[ 2.271448,0] EMU-det(adc_vbus_get): vbus=34 mV
[ 2.329925,0] EMU-det(get_sense): SEMU_PPD_DET: ID floating
[ 2.389928,0] EMU-det(get_sense): No need to check DMB_PPD_DET_N
[ 2.390141,0] EMU-det(sense_dp_dm): D+/D- mask: 0x10
[ 2.390477,0] EMU-det(get_sense): irq=0, SESS_END, FLOAT, NO_DCD,
[ 2.390691,0] EMU-det(detection_work): state IDENTIFY, time since last run 120 ms
[ 2.392217,0] EMU-det(adc_vbus_get): vbus=34 mV
[ 2.460369,0] EMU-det(get_sense): SEMU_PPD_DET: ID floating
[ 2.519975,0] EMU-det(get_sense): No need to check DMB_PPD_DET_N
[ 2.520189,0] EMU-det(sense_dp_dm): D+/D- mask: 0x10
[ 2.520524,0] EMU-det(get_sense): irq=0, SESS_END, FLOAT, NO_DCD,
[ 2.520708,0] EMU-det(detection_work): no accessory
[ 2.521043,0] EMU-det(notify_accy): EMU detection Notify: NONE
[ 2.521471,0] EMU-det(alt_mode_setup): SEMU_ALT_MODE_EN is standard
[ 2.521776,0] EMU-det(emu_id_protection_setup): No neccessary action
[ 2.521989,0] msm_otg msm_otg: received DISCONNECTED event
[ 2.522325,0] msm_otg msm_otg: UNDEFINED --> IDLE
[ 2.523638,0] pm8921_chg_accy_notify: pm8921_chg_accy_notify: accy_state: 7
[ 2.524767,0] msm_otg msm_otg: USB in low power mode
[ 2.526781,0] calculate_state_of_charge: Forcing SHUTDOWN_SOC = 72
[ 3.609095,1] init: could not import file '/init.carrier.rc' from '/init.rc'
[ 3.610621,1] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
[ 3.611689,1] init: do_chown: Could not access /selinux/booleans
[ 3.668213,0] calculate_state_of_charge: Forcing SHUTDOWN_SOC = 72
[ 4.120921,1] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[ 4.122325,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 4.129742,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 4.130627,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 4.131603,1] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 4.280970,1] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[ 4.311277,0] zcache: created ephemeral tmem pool, id=0, client=65535
[ 4.312620,0] EXT4-fs (mmcblk0p37): recovery complete
[ 4.312833,0] EXT4-fs (mmcblk0p37): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,barrier=1
[ 4.313200,0] SELinux: initialized (dev mmcblk0p37, type ext4), uses xattr
[ 4.324034,0] zcache: created ephemeral tmem pool, id=1, client=65535
[ 4.324767,0] EXT4-fs (mmcblk0p39): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
[ 4.325164,0] SELinux: initialized (dev mmcblk0p39, type ext4), uses xattr
[ 4.325927,0] zcache: destroyed pool id=1, cli_id=65535
[ 4.360842,1] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/userdata
[ 4.368197,1] atmxt_tdat_callback: Processing atmxt-r2.tdat...
[ 4.369082,1] input: atmxt-i2c as /devices/virtual/input/input6
[ 4.401312,0] atmxt_set_ic_state: IC state UNKNOWN -> PRESENT
[ 4.401709,0] atmxt_restart_ic: Family ID: 0x82, Variant ID: 0x1A, Version: 0x10, Build: 0xAA, Matrix: 24x14, Objects: 22
[ 4.408484,0] atmxt_message_handler6: Touch IC reset complete.
[ 4.408698,0] atmxt_message_handler6: Touch IC is calibrating.
[ 4.409064,0] atmxt_set_ic_state: IC state PRESENT -> ACTIVE
[ 4.409705,0] atmxt_set_drv_state: Driver state INIT -> ACTIVE
[ 4.410254,0] atmxt_tdat_callback: Touch initialization successful.
[ 4.411719,1] atmxt_active_handler: Received invalid data: 0xFF 0x90 0xE9 0xD5 0x0C 0x00 0x00 0x00 0xFF 0x90 0xE9 0xD5 0x0C 0x00 0x00 0x00.
[ 4.412238,1] atmxt_active_handler: Touch active handler failed with error code -22.
[ 4.413764,1] atmxt_message_handler6: Touch IC calibration complete.
[ 4.558583,1] atmxt_message_handler6: Touch IC is calibrating.
[ 4.591271,1] atmxt_message_handler6: Touch IC calibration complete.
[ 5.421303,0] lm3532_bl_work: enabling PWM
[ 32.090920,0] shutdown_soc_work: not forcing shutdown soc anymore
[ 1404.024049,0] Report pwrkey press event
[ 1404.087501,0] pm8xxx_irq_mask_ack: mask acking rouge irq=664 pmirq=224
[ 1410.810773,0] resout_irq_handler PMIC Initiated shutdown
[ 1410.810834,0] PMIC Initiated shutdown cpu_power_off cpu=0
[ 1410.810834,1] PMIC Initiated shutdown cpu_power_off cpu=1
[ 1410.811017,0] Powering off the SoC
[ 1410.811109,0] Calling scm to disable arbiter
[ 1410.811231,0] SCM returned even when asked to busy loop rc=-4
[ 1410.811292,0] waiting on pmic to shut msm down
18 Corrected bytes, 0 unrecoverable blocks
CPU type is ACPU PVS: Fast
That was after like 20-30 minutes of booting. Thanks in advance
EDIT:
Oups. "The text that you have entered is too long (39454 characters). Please shorten it to 30000 characters long." I'll cut the begining...
EDIT2:
It booted up! I rebooted it once again and left it at my desk. When I came back after 1h, it was already on the home screen! thanks for help kabaldan I think such info could be put as NOTICE on main rom page, I think normally everyone would consider its stuck when it's not booting in a few minutes...
Thank you Kabaldan!
It took exactly 40 minutes my Photon Q to reboot from /data filesystem check. I used:
* cm-11-20140505-SNAPSHOT-M6-moto_msm8960.zip from download.cyanogenmod.org/?type=snapshot&device=moto_msm8960
* TWRP 2.7.0.1
* gapps-kk-20140105-signed.zip from wiki.cyanogenmod.org/w/Google_Apps
micx_pl said:
Output of /proc/last_kmsg:
Code:
…
[ 4.591271,1] atmxt_message_handler6: Touch IC calibration complete.
[ 5.421303,0] lm3532_bl_work: enabling PWM
[U][ 32.090920,0] shutdown_soc_work: not forcing shutdown soc anymore[/U]
[ 1404.024049,0] Report pwrkey press event
[ 1404.087501,0] pm8xxx_irq_mask_ack: mask acking rouge irq=664 pmirq=224
[ 1410.810773,0] resout_irq_handler PMIC Initiated shutdown
…
Click to expand...
Click to collapse
Thanks for that intel. Am I right, that this is the "breaking point" in the log, when the mentioned repair starts and -later- the reset is initiated? My log has the same "breaking point" in it: https://www.dropbox.com/s/0iqdr30jmhft2co/last_kmsg
So is this the same phenomenon? This is the first time I pulled a log using adb, but do not recognise anything going on here.
kabaldan said:
If you want to get some information about what's going on while the boot is stalled, …
Click to expand...
Click to collapse
Edit:
May this also help with errors mounting certain partions within TWRP and is there a way to fix this - maybe through adb? Because doing a quick search I found this guide (fore theKindle, though): http://forum.xda-developers.com/showthread.php?t=1949372
Schattenspieler said:
Thanks for that intel. Am I right, that this is the "breaking point" in the log, when the mentioned repair starts and -later- the reset is initiated? My log has the same "breaking point" in it: https://www.dropbox.com/s/0iqdr30jmhft2co/last_kmsg
So is this the same phenomenon? This is the first time I pulled a log using adb, but do not recognise anything going on here.
Edit:
May this also help with errors mounting certain partions within TWRP and is there a way to fix this - maybe through adb? Because doing a quick search I found this guide (fore theKindle, though): http://forum.xda-developers.com/showthread.php?t=1949372
Click to expand...
Click to collapse
The significant point in the above log is:
Code:
[ 4.360842,1] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/userdata
and the important fact is that it is not followed by any more e2fsck messages, which means that for the duration of the log, e2fsck hasn't finished the work yet.
e2fsck is still repairing userdata and the init is waiting for userdata mount to continue the boot process, but in the end the user keeps power button pressed to enforce reboot, so e2fsck is aborted and the filesystem left damaged.
In your log, you can even see that the active process at the point of premature, user-enforced reboot was e2fsck:
Code:
[ 279.105569,0] Report pwrkey press event
[ 286.105966,0] Power key held for 7 seconds; will reboot on release.
[ 286.473981,1] current process is 140:e2fsck, prio is 120.
kabaldan said:
In your log, you can even see that the active process at the point of premature, user-enforced reboot was e2fsck:
Click to expand...
Click to collapse
Now that you mention it! I didn't think, e2fsck was a specific command, but more of a boot state code (sort of thing). But I should have searched. Now i see the "e2fs" (the filesystem) and "ck" as in check. :silly:
I now restored a TWRP backup with 4.4.3 and have been fine since. So there is either something wrong with the 4.4.4 CarbonROM on the Photon oder with TWRP, when installing the/some ROMs. Seeing this thread, I tend towards the second.
Schattenspieler said:
Now that you mention it! I didn't think, e2fsck was a specific command, but more of a boot state code (sort of thing). But I should have searched. Now i see the "e2fs" (the filesystem) and "ck" as in check. :silly:
I now restored a TWRP backup with 4.4.3 and have been fine since. So there is either something wrong with the 4.4.4 CarbonROM on the Photon oder with TWRP, when installing the/some ROMs. Seeing this thread, I tend towards the second.
Click to expand...
Click to collapse
If you had let it boot, it probably would have been fine.