i had random data disconnects so i updated the e971 modem seems better so far
modems:
http://downloads.codefi.re/houstonn/lgog/modem
Thanks, I will check out the new Bell modem and see how it works.
i had random data disconnects so i updated the e971 modem seems better so far
modems:
http://downloads.codefi.re/houstonn/lgog/modem
For all you guys that are KDZ'ing back to stock .. please note that is it better to KDZ to the newest official jelly bean kdz and then root then unlock.. then install all these aosp roms in recovery.. since the jelly bean official there's a lot of hardware firmware changes including new modems etc that would most likely be more compatible with a lot of code changes as we are moving forward..this way it insures that you are update to date if any is updated..
---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------
can you provide us with a log cat .. or more info would help..
Holy battery killer batman!! These are my results this morning with the 21/3 build. NFC doesn't seem to want to turn off either. Every time I check, its toggled back on.
Sent from my Nexus 4 using Tapatalk 2
i had random data disconnects so i updated the e971 modem seems better so far
modems:
http://downloads.codefi.re/houstonn/lgog/modem
Question about the modems. If I'm using a Rogers E971 on Bell network, should I flash a bell modem or rogers modem. I flashed the new bell modem. It works, but seems worse then before. I'm going to tee trial and error flash the rogers one too see. But figured I'd ask incase someone has more info.
Sent from my Nexus 4 using Tapatalk 2
Hi Chad, my post got buried under a flurry of posts so its gotten lost...
So far everything still going great.
I have a question for you, I've been watching the cpufreq settings and I can't quite figure out whats going on.
Upon initial boot, I check the max freq with this command:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
It seems to be all over the place, sometimes its overclocking to 1836, sometimes its max is 1296 and sometimes its right where it should be at 1510.
Just randomly checking with the cat command and the max is changing...with nothing seemingly causing it.
From my understanding max is max, it shouldn't be jumping around once set by either the kernel or by userspace command...
Can you explain whats going on??
I'd just like for it to stick at 1512 but I can't seem to get it to stick.
Thank you very much for taking the time to answer my question!
Not one reboot or sod yet, with lots of notifications coming in and led on.
Cheers and keep up the fantastic work!
I may have a small contribution to the forums soon as I'm getting my feet wet in the android ROM world.
Sent from my Optimus G using xda app-developers app
only issue so far is when i make a call it says call ended right away but then the calls goes through
No idea of what is wrong. Right now i'm restoring with KDZ file.
Sorry I meant what happened to your phone when you ran it?
I ran benchmark earlier today without issue...
---------- Post added at 09:25 PM ---------- Previous post was at 09:19 PM ----------
First SOD just happened.
Im not a kernel programmer, I took a guess at what might help from dmesg?
<3>[ 51.186523] BUG: scheduling while atomic: kworker/2:0/2797/0x00000103
<4>[ 51.186614] Modules linked in:
<4>[ 51.186767] [<c00145fc>] (unwind_backtrace+0x0/0xf8) from [<c08cdd5c>] (__schedule+0x53c/0x738)
<4>[ 51.186889] [<c08cdd5c>] (__schedule+0x53c/0x738) from [<c08ce36c>] (schedule_preempt_disabled+0x24/0x34)
<4>[ 51.187042] [<c08ce36c>] (schedule_preempt_disabled+0x24/0x34) from [<c08ccfa4>] (__mutex_lock_slowpath+0x11c/0x1a4)
<4>[ 51.187194] [<c08ccfa4>] (__mutex_lock_slowpath+0x11c/0x1a4) from [<c08cd068>] (mutex_lock+0x3c/0x40)
<4>[ 51.187316] [<c08cd068>] (mutex_lock+0x3c/0x40) from [<c03da344>] (pm8xxx_pwm_lut_config+0x94/0x478)
<4>[ 51.187469] [<c03da344>] (pm8xxx_pwm_lut_config+0x94/0x478) from [<c054955c>] (pm8xxx_led_set+0x78/0xec)
<4>[ 51.187561] [<c054955c>] (pm8xxx_led_set+0x78/0xec) from [<c0548b9c>] (led_timer_function+0xe4/0xf4)
<4>[ 51.187683] [<c0548b9c>] (led_timer_function+0xe4/0xf4) from [<c007c860>](run_timer_softirq+0x140/0x39c)
<4>[ 51.187835] [<c007c860>] (run_timer_softirq+0x140/0x39c) from [<c0075784>] (__do_softirq+0xc8/0x22c)
<4>[ 51.187957] [<c0075784>] (__do_softirq+0xc8/0x22c) from [<c0075d7c>] (irq_exit+0x90/0x98)
<4>[ 51.188110] [<c0075d7c>] (irq_exit+0x90/0x98) from [<c000eea0>] (handle_IRQ+0x54/0xb8)
<4>[ 51.188201] [<c000eea0>] (handle_IRQ+0x54/0xb8) from [<c00085e8>] (gic_handle_irq+0x3c/0xe4)
<4>[ 51.188323] [<c00085e8>] (gic_handle_irq+0x3c/0xe4) from [<c08cfc40>] (__irq_svc+0x40/0x70)
<4>[ 51.188476] Exception stack(0xe81c3ec0 to 0xe81c3f08)
<4>[ 51.188568] 3ec0: cf724990 60000013 16191619 00010000 cf724980 00000000 00000001 e81c3f2f
<4>[ 51.188690] 3ee0: 00000143 60000013 cf724990 cf793498 00000000 e81c3f08 c06a6630 c08cf580
<4>[ 51.188812] 3f00: 60000013 ffffffff
<4>[ 51.188903] [<c08cfc40>] (__irq_svc+0x40/0x70) from [<c08cf580>] (_raw_spin_unlock_irqrestore+0x28/0x50)
<4>[ 51.189025] [<c08cf580>] (_raw_spin_unlock_irqrestore+0x28/0x50) from [<c06a6630>] (msm_ssbi_write+0xdc/0xe4)
<4>[ 51.189178] [<c06a6630>] (msm_ssbi_write+0xdc/0xe4) from [<c03d7dec>] (pm8921_writeb+0x34/0x3c)
<4>[ 51.189300] [<c03d7dec>] (pm8921_writeb+0x34/0x3c) from [<c03d9400>] (pm8xxx_pwm_bank_sel+0x38/0x68)
<4>[ 51.189392] [<c03d9400>] (pm8xxx_pwm_bank_sel+0x38/0x68) from [<c03d99a4>] (pm8xxx_pwm_lut_enable+0xa0/0x120)
<4>[ 51.189514] [<c03d99a4>] (pm8xxx_pwm_lut_enable+0xa0/0x120) from [<c0549be0>] (pm8xxx_led_work+0x6c/0x14c)
<4>[ 51.189666] [<c0549be0>] (pm8xxx_led_work+0x6c/0x14c) from [<c008805c>] (process_one_work+0x124/0x468)
<4>[ 51.189819] [<c008805c>] (process_one_work+0x124/0x468) from [<c0088684>](worker_thread+0x138/0x2e8)
<4>[ 51.189971] [<c0088684>] (worker_thread+0x138/0x2e8) from [<c008d318>] (kthread+0x88/0x94)
<4>[ 51.190032] [<c008d318>] (kthread+0x88/0x94) from [<c000f114>] (kernel_thread_exit+0x0/0x8)
Phone is still in sod and I have adb access if there's something else you'd like to see?
Is there ANY WAY you can add to this the changes in faux123's Nexus 4 kernel (see here http://rootzwiki.com/topic/36722-kernellinux-340-makojbuvoctuncifsv001-nov-30/#entry1032460) to reduce the horrible msm_hsic_host wakelock battery drain?