Search results

I tried LSpeed calibration and it, like everything else didn't help. I can't post my problematic battery version, since I swapped for a working ZF2, but the new one is 1517.

I had the issue (battery monitor jumping to 100% and phone shutting off @20%). Nothing I tried fixed it (calibration, going back to early stock builds, running CM12.1, nor SuperZen ROM with this kernel). I exchanged the phone and the problem is solved. If you look at the Asus forum, you will see...

Running CM12.1 did not solve the battery reporting problems I was having with my phone that exhibited this behavior. In fact, this was the determining factor in my decision to return that handset for a replacement.

I'm having the same issue.

To follow up, it seems the wake problem occurs with intellidemand, but not smartmax. I haven't tried the other governors to see if the issue exists with others.

Tried 1.05, screen wouldn't come back on after sleep. 1.04 works great.

Try uninstalling the YouTube app and installing it again. This fixed that problem for me recently.

Works! Thanks. Make sure you set permissions and reboot. Sent from my TouchPad using Tapatalk

Active display is fixed. Woo-hoo!

Same thing happens to me.

Not sure if this is already a known issue, but when using Active Display, the status bar is missing when I unlock from pocket mode. Interestingly, bringing up the shut down menu restores it. Don't need to actually restart, just bring up the menu. Sent from my One using Tapatalk

I'm running FTL with this kernel and I don't have any such problems.

This is true, but my previously remapped buttons continue to operate correctly. So, not a big problem for me.

Hard reboot solves start up problems for me. Sent from my One X using Tapatalk 4

Well, I just heard back from Zarboz and he said he has run into the same problem mobiletechvideo reports. So, I guess that answers the question. How depressing. Sent from my MB860 using Tapatalk 4

No, I didn't mean that sarcastically. I really don't know if their diagnosis is accurate or not. Out of curiosity, how do you know Zarboz has been successful? Sent from my TouchPad using Tapatalk 4 Beta

You could be right. What do I know? I would like to find out if anyone else has been able to revive their phone, or if the bug is terminal. Sent from my TouchPad using Tapatalk 4 Beta

I guess I will respond to my own post, again. Apparently, mobiletechvideo can't fix it. They claim it is a bad power management chip. I am not sure that makes sense, given the circumstances. I guess I will try and pm Zarboz and see if he has had any better luck with these. Sent from my...

Anyone whose phone was damaged running cm 10.2? Sent from my MB860 using Tapatalk 4

Has anyone whose phone was bricked by the pre-nightly cm 10.2 builds actually gotten their phone fixed via jtag? I sent mine to mobiletechvideo on the 11th and I am still waiting for the phone. They contacted me yesterday to say that there was a problem with the repair and to ask for more...

Mine was not charging at the time, but it had been idle for some time in my pocket when I tried to wake it up, and discovered it was bricked. So, it could have been running trim. I was also on TWRP 2.6 and had been running cm10.2 for about a day. No daydream.

Mine was declared "sane," so caution with relying on this may be warranted.

Sorry to hear about your two phones, but at least this confirms what happened to me. I am sending mine off to Mobiletechvideos for revival. Fingers crossed...

Upgraded. Sent from my MB860 using Tapatalk 4 ---------- Post added at 03:05 PM ---------- Previous post was at 02:59 PM ---------- I wish it were that easy to revive, but alas... I have also tried holding power and volume down for forever, in case anyone is wondering this as well. Sent...

Bad news for me and a heads-up. My phone is bricked. This happened while running the 8/9 build and after a brick bug check declared my memory "sane." It was not charging at the time, unlike some others. Computer sees it as QHSUSB_DLOAD like the others though. Please let me know if there is...

Odd. Superuser and Titanium Backup are both working here.

Great work. Any chance we'll see a return of usb host in the future?

Well, that is undoubtedly dust in the speaker holes on your phone. :rolleyes:

I still got a fc taking a portrait on the front camera.

This. It is definitely lower than before the 3.4 kernel.

How about low call volume? Is this connected to the other audio issues? I recall it was a problem before, but don't remember what it fix was.

Odd. I haven't had the audio only on one side since I turned off lpa. I should add that this is on headphone out. I don't have bluetooth audio to test if it fixes that also.

That's right. Depending on how you edit it, you may have to reset it after.

Did you set the build.prop permissions before rebooting? ---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ---------- Whoops forgot to quote what I was replying to.

Setting lpa.decode to false in the build prop, seems to have fixed the one-sided audio bug. Can anyone else confirm.

Yes, there is something wrong with the 6/4 build. I double checked the md5, so it's not a bad download.

Looks good. LTE come up just fine after flashing. Thanks.

That doesn't work in my case. In fact, I had to run *#*#4636#*#* again after trying to toggle that to re-enable LTE.

Yes, this is a good workaround. Thanks.

LTE default is not sticking for me on the latest. Reverts to WCDMA preferred. This is on a clean install. Anyone else?

Re: [ROM][4.1.2][WEEKLY] CyanogenMod 10 for HTC One XL I'm pretty sure CM10 is not reporting lte signal properly. Have you looked at the actual signal strength number in the settings to compare?

Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL I can confirm the freezes while using Play Music. Also coming from a full wipe. Re-flashed the previous build for now.

Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL Sorry, my lame attempt at humor in response to a question about timelines.

Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL bi-monthly.

Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL How did that work out? :)

Re: [ROM][4.2.1] UNOFFICIAL CyanogenMod 10.1 for HTC One XL Yeah, it's low.

No, the gps issue is still there.

What does a Samsung phone have to do with us?

Same here, and reflashing the radio has not helped on my phone.

I flashed the 12/1 cm10 nightly and thought the GPS signal drop was gone, but alas a reboot brought it back. So, no not fixed yet.