Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[ROM] [AeroKernel] Unofficial CyanogenMod 11

OP Quarx

19th December 2014, 05:15 PM   |  #501  
Senior Member
The Gulag
Thanks Meter: 123
 
557 posts
Join Date:Joined: Dec 2011
Had a random restart and seems it can't play .mov even if player supports it. (MxPlayer)
22nd December 2014, 10:59 AM   |  #502  
labsin's Avatar
Senior Member
Flag Antwerp
Thanks Meter: 235
 
665 posts
Join Date:Joined: Apr 2011
More
Does anyone got otg working. Whatever I connect, it keeps giving me following errors: (last 100 dmesg lines after trying 2 times)

[spoiler]
<4>[ 382.170269,0] gic_show_resume_irq: 203 triggered
<4>[ 382.170269,0] gic_show_resume_irq: 222 triggered
<6>[ 382.170750,0] PM: resume_noirq longest - msm_watchdog(0xc015964c) (0.002 msecs)
<6>[ 382.171568,0] PM: noirq resume of devices complete after 0.966 msecs
<6>[ 382.172041,0] Report pwrkey press event
<6>[ 382.172565,0] PM: early resume of devices complete after 0.308 msecs
<6>[ 382.175199,0] PM: resume of devices complete after 2.621 msecs
<4>[ 382.178558,0] Restarting tasks ...
<4>[ 382.182872,0] QSEECOM: qseecom_receive_req: Interrupted: exiting Listener Service = 8192
<3>[ 382.183110,0] QSEECOM: qseecom_ioctl: failed qseecom_receive_req: -512
<4>[ 382.183274,0] QSEECOM: qseecom_receive_req: Interrupted: exiting Listener Service = 12288
<3>[ 382.183361,0] QSEECOM: qseecom_ioctl: failed qseecom_receive_req: -512
<4>[ 382.183522,0] QSEECOM: qseecom_receive_req: Interrupted: exiting Listener Service = 11
<3>[ 382.183677,0] QSEECOM: qseecom_ioctl: failed qseecom_receive_req: -512
<4>[ 382.183771,0] QSEECOM: qseecom_receive_req: Interrupted: exiting Listener Service = 10
<3>[ 382.183924,0] QSEECOM: qseecom_ioctl: failed qseecom_receive_req: -512
<4>[ 382.188302,0] done.
<6>[ 382.188817,0] PM: suspend exit 2014-12-22 09:45:14.885503349 UTC
<6>[ 382.247446,0] ct406_work_prox_start: Prox mode start
<6>[ 382.312725,0] ct406_disable_prox: Prox mode stop
<6>[ 382.350206,0] Report pwrkey release event
<6>[ 382.365178,0] mdss_dsi_on+: ctrl=e4818010 ndx=0
<6>[ 382.388580,0] mdss_dsi_on-:
<6>[ 382.388594,0] mdss_dsi_panel_on+: ctrl=e4818010 ndx=0
<3>[ 382.579927,0] qup_i2c f9927000.i2c: QUP: I2C status flags :0xc1300c8, irq:131
<3>[ 382.579956,0] qup_i2c f9927000.i2c: I2C slave addr:0x20 not connected
<3>[ 382.579972,0] synaptics_dsx_i2c 5-0020: synaptics_rmi4_i2c_write: I2C retry 1
<6>[ 382.607642,1] synaptics_dsx_sensor_state: state change SUSPEND -> ACTIVE
<6>[ 382.608242,1] mdss_dsi_panel_on-. Pwr_mode(0x0A) = 0x9c
<6>[ 382.625312,0] qcom,leds-qpnp leds-qpnp-e4a31400: backlight on
<6>[ 382.781940,0] wlan: [1750:E :HDD] hdd_conf_arp_offload: 1106: fenable = 0
<6>[ 394.456848,0] wlan: [1595:E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
<6>[ 395.851727,0] msm_otg f9a55000.usb: USB exited from low power mode
<6>[ 396.066928,0] msm_hsusb_host msm_hsusb_host: Qualcomm On-Chip EHCI Host Controller
<6>[ 396.067449,0] msm_hsusb_host msm_hsusb_host: new USB bus registered, assigned bus number 1
<6>[ 396.096940,0] msm_hsusb_host msm_hsusb_host: irq 166, io mem 0xf9a55000
<6>[ 396.116656,0] msm_hsusb_host msm_hsusb_host: USB 2.0 started, EHCI 1.00
<6>[ 396.116875,0] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 396.117054,0] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 396.117229,0] usb usb1: Product: Qualcomm On-Chip EHCI Host Controller
<6>[ 396.117329,0] usb usb1: Manufacturer: Linux 3.4.42-AeroKernel-g63fb0d2 ehci_hcd
<6>[ 396.117506,0] usb usb1: SerialNumber: msm_hsusb_host
<6>[ 396.118404,0] hub 1-0:1.0: USB hub found
<6>[ 396.118604,0] hub 1-0:1.0: 1 port detected
<6>[ 396.436776,0] usb 1-1: new full-speed USB device number 2 using msm_hsusb_host
<3>[ 396.646861,0] usb 1-1: device descriptor read/64, error -71
<3>[ 396.966841,0] usb 1-1: device descriptor read/64, error -71
<6>[ 397.196715,0] usb 1-1: new full-speed USB device number 3 using msm_hsusb_host
<3>[ 397.406833,0] usb 1-1: device descriptor read/64, error -71
<3>[ 397.726637,0] usb 1-1: device descriptor read/64, error -71
<6>[ 397.956848,0] usb 1-1: new full-speed USB device number 4 using msm_hsusb_host
<3>[ 398.436832,0] usb 1-1: device not accepting address 4, error -71
<6>[ 398.556844,0] usb 1-1: new full-speed USB device number 5 using msm_hsusb_host
<3>[ 399.036691,0] usb 1-1: device not accepting address 5, error -71
<3>[ 399.036908,0] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[ 401.038723,0] msm_otg f9a55000.usb: USB in low power mode
<6>[ 421.141393,0] wlan: [1595:E :HDD] wlan_hdd_tdls_check_bmps: 1755: pHddCtx or pHddTdlsCtx points to NULL
<6>[ 481.407016,1] wlan: [1595:E :HDD] wlan_hdd_tdls_check_bmps: 1755: pHddCtx or pHddTdlsCtx points to NULL
<6>[ 489.646823,0] wlan: [1595:E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
<6>[ 541.088392,0] wlan: [1595:E :HDD] wlan_hdd_tdls_check_bmps: 1755: pHddCtx or pHddTdlsCtx points to NULL
<6>[ 602.071540,1] wlan: [1595:E :HDD] wlan_hdd_tdls_check_bmps: 1755: pHddCtx or pHddTdlsCtx points to NULL
<6>[ 662.130080,0] wlan: [1595:E :HDD] wlan_hdd_tdls_check_bmps: 1755: pHddCtx or pHddTdlsCtx points to NULL
<6>[ 676.210880,0] msm_otg f9a55000.usb: USB exited from low power mode
<6>[ 676.216806,0] msm_hsusb_host msm_hsusb_host: remove, state 84
<6>[ 676.356920,0] usb usb1: USB disconnect, device number 1
<6>[ 676.359954,0] msm_hsusb_host msm_hsusb_host: USB bus 1 deregistered
<6>[ 676.867350,0] msm_otg f9a55000.usb: USB in low power mode
<6>[ 678.581483,0] msm_otg f9a55000.usb: USB exited from low power mode
<6>[ 678.796950,0] msm_hsusb_host msm_hsusb_host: Qualcomm On-Chip EHCI Host Controller
<6>[ 678.797570,0] msm_hsusb_host msm_hsusb_host: new USB bus registered, assigned bus number 1
<6>[ 678.826732,0] msm_hsusb_host msm_hsusb_host: irq 166, io mem 0xf9a55000
<6>[ 678.846582,0] msm_hsusb_host msm_hsusb_host: USB 2.0 started, EHCI 1.00
<6>[ 678.846906,0] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 678.847148,0] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 678.847374,0] usb usb1: Product: Qualcomm On-Chip EHCI Host Controller
<6>[ 678.847502,0] usb usb1: Manufacturer: Linux 3.4.42-AeroKernel-g63fb0d2 ehci_hcd
<6>[ 678.847728,0] usb usb1: SerialNumber: msm_hsusb_host
<6>[ 678.848817,0] hub 1-0:1.0: USB hub found
<6>[ 678.849065,0] hub 1-0:1.0: 1 port detected
<6>[ 679.166721,0] usb 1-1: new full-speed USB device number 2 using msm_hsusb_host
<3>[ 679.376783,0] usb 1-1: device descriptor read/64, error -71
<3>[ 679.696879,0] usb 1-1: device descriptor read/64, error -71
<6>[ 679.926679,0] usb 1-1: new full-speed USB device number 3 using msm_hsusb_host
<3>[ 680.136851,0] usb 1-1: device descriptor read/64, error -71
<3>[ 680.456683,0] usb 1-1: device descriptor read/64, error -71
<6>[ 680.686725,1] usb 1-1: new full-speed USB device number 4 using msm_hsusb_host
<3>[ 681.166605,0] usb 1-1: device not accepting address 4, error -71
<6>[ 681.286774,0] usb 1-1: new full-speed USB device number 5 using msm_hsusb_host
<3>[ 681.766590,1] usb 1-1: device not accepting address 5, error -71
<3>[ 681.766860,1] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[ 683.989181,1] msm_otg f9a55000.usb: USB in low power mode
<6>[ 722.101336,1] wlan: [1595:E :HDD] wlan_hdd_tdls_check_bmps: 1755: pHddCtx or pHddTdlsCtx points to NULL
<6>[ 783.182826,0] wlan: [1595:E :HDD] wlan_hdd_tdls_check_bmps: 1755: pHddCtx or pHddTdlsCtx points to NULL
<6>[ 843.167467,1] wlan: [1595:E :HDD] wlan_hdd_tdls_check_bmps: 1755: pHddCtx or pHddTdlsCtx points to NULL
<6>[ 869.535005,1] wlan: [1750:E :SME] sme_FTUpdateKey: Unhandled state=0
<4>[ 885.327543,2] IRQ40 no longer affine to CPU2
<4>[ 888.582235,2] IRQ40 no longer affine to CPU2
<4>[ 890.598683,3] IRQ40 no longer affine to CPU3
<6>[ 903.098191,0] wlan: [1595:E :HDD] wlan_hdd_tdls_check_bmps: 1755: pHddCtx or pHddTdlsCtx points to NULL
<6>[ 960.586653,1] wlan: [1595:E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
[/spoiler]


Sent from my Moto G using XDA Free mobile app
28th December 2014, 02:04 PM   |  #503  
Junior Member
Thanks Meter: 1
 
4 posts
Join Date:Joined: Jan 2010
Hi, everyone. Mr. Quarx your build is so nice and workable... Thank's for your talent... I got a question: Should we wait for your own build of Lollipop for our devices? CM12 already released a beta, but after their experiments with CM 11 for Moto G 1gen, i got no desire to choose their build...
The Following User Says Thank You to dizaar For This Useful Post: [ View ]
28th December 2014, 02:29 PM   |  #504  
Senior Member
Thanks Meter: 92
 
509 posts
Join Date:Joined: Jan 2011
Question
Quote:
Originally Posted by dizaar

Hi, everyone. Mr. Quarx your build is so nice and workable... Thank's for your talent... I got a question: Should we wait for your own build of Lollipop for our devices? CM12 already released a beta, but after their experiments with CM 11 for Moto G 1gen, i got no desire to choose their build...

This is not unique to this rom but I get soo much better battery life running stock with stock kernel (even when I add xposed framework, gravitybox and xprivacy). This with all the same apps restored to either rom. Especially apparent if I standby. For example, with this rom, I can probably pull 3-4 Screentime with no standby, or 3 hours and 1 day standby. With stock, I can do 2 days and 4 hours screen time with 2-3 hours of music to boot. This is the same for both mine and my friends' Moto Gs. I wonder if there is a certain app that doesn't play well with the non stock code. I have used battery stats and such and could not find a particular anomaly.
16th January 2015, 05:05 PM   |  #505  
Junior Member
Thanks Meter: 1
 
15 posts
Join Date:Joined: Feb 2013
More
@Quarx, @Blechd0se

Thanks a lot for your contribution and building this specific CM11. It is running smoothly and without an issue. I just wanted to ask whether you are still open to a few improvements/additions in the ROM. Just that on default KitKat rom running on XT1033 (Dual-Sim); it remembers the SIM card to use for calling or SMS on individual contact basis. If this is possible then please add in future nightly as it saves a lot of time.
25th January 2015, 03:07 PM   |  #506  
m0nn3's Avatar
Senior Member
Thanks Meter: 21
 
224 posts
Join Date:Joined: Jan 2009
Hello, I have flashed this ROM on my moto g and sometimes my device reboots automatically..
How can I solve this problem?

All the rest runs very good and smooth!

Thanks for your work!

Sent from my One S using XDA Free mobile app
25th January 2015, 11:17 PM   |  #507  
Senior Member
Flag Salerno
Thanks Meter: 32
 
136 posts
Join Date:Joined: Jul 2013
More
I use 01-23 without random reboots, you use any kernels? Or special applications? A suggest you to use Aerokernel for check random reboots.

Sent from my Moto G using XDA Free mobile app
26th January 2015, 09:49 AM   |  #508  
Junior Member
Thanks Meter: 5
 
16 posts
Join Date:Joined: Jul 2014
hey quarx,
in 2 latest build l can't go to recovery using option reboot recovery from power button,
but I can go to recovery using terminal emulator, is this only me or the other had the same problem

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes