Search results

Yes. It looks like the build got stuck.

LOS provides a "Vibrator Intensity" setting, which can be found under the Sound -> Other Sounds menu. Have you tried adjusting this?

I too have noticed that the 4/27 build is much more responsive than the previous builds. However, yesterday I experienced much faster battery drain than usual. Have you noticed this yet? If not, please keep an eye out for it.

The arm64 version.

LineageOS images are carrier-agnostic. However, if your phone is not carrier-unlocked, you will only be able to authenticate on the network the phone is locked to. This is not a limitation of LOS.

I can confirm this issue exists with the 4/13 build. Is anyone else having trouble connecting to their cellular network with the 4/13 build?

I assume that is a screenshot of the AOSP Clock app. If so, the answer is no. The interface is slightly different than mine, so I checked the package and was surprised to learn that I had installed the Google Clock app. I guess I never realized it was part of the "mini" GApps package. I thought...

I wake up to these alarms 5+ days each week and have not had any problems to date.

While I have noticed issues after deleting files as I mentioned previously, I have had no problem getting the phone to show up in Windows Explorer. It sounds like your device isn't enabling MTP. Just to confirm, are you choosing "Transfer files" in the "Use USB to..." menu after connecting your...

I've noticed recently that deleting files via MTP hasn't been working properly. If you try to delete over MTP, the files appear to get deleted, but they will reappear if disconnected and reconnected. I'm not sure if this is what you're seeing. If not, you should share some more detail of your...

I can attest to frame drops and general lagginess on the 4/7 nightly. I posted about similar lagginess in the 3/3 nightly here: https://forum.xda-developers.com/showpost.php?p=71360074&postcount=1019. It seemed to improve on builds since then until this new 4/7 build, in which it seems to have...

Sounds exactly like this user's issue from a month ago: https://forum.xda-developers.com/showpost.php?p=71295013&postcount=975. I don't think a cause or solution was ever posted, though.

1.) crpalmer has built an experimental kernel to cut down on wifi battery drain. It's a few pages back; just search the thread. 2.) Did you install a gapps version with the Google Phone app? If so, you must flash the gapps package after flashing the system image before you boot into the system...

The order with which you flash su and gapps shouldn't matter. Did you enable the developer options menu and enable root in there? This still needs to be done like in CM.

That's currently a "feature" of the LOS Updater app. It will report your currently installed version as an available update. crpalmer didn't upload a new version, all builds are automated now.

Has anyone else noticed the 3/3 build being much more laggy/choppy than all previous builds? Very noticable in Chrome, especially with keyboard input.

You must have had a bad flash. I dirty-flashed 3/3 over 2/27 without issue.

It's the former. From the LineageOS website:

I don't think so. It looks like pme will be the first build tomorrow.

While it may not be a bug, it's certainly a regression. The old CMUpdater would mark the available download for your current version as "installed" instead of showing the download as an available update.

The location has changed in Android N. In settings, you need to select "Apps," then press the gear in the upper-right corner.

I was one of the people to report this, and I provided an excerpt from dmesg with the stack traces in post #352. Glad to see I'm not the only person still experiencing this. It seems to be occurring less frequently in more recent builds, but I still encounter it occasionally.

I've been using the "stock" Gapps package. Everything seems to work just fine, including the Google Dialer. Dirty flashing a new nightly won't wipe your Gapps; you don't need to reinstall them after a dirty flash.

If you haven't formatted your SD card since flashing from stock, you might have the same issue I did. I reported my fix in post #231. Try this and see if it fixes your SD card permissions issues.

It's already available. You just need to enable it under Developer options > Advanced restart.

I believe that option should be re-titled "Remove Encryption Password."

This is the same sporadic issue I've been having with WiFi. I posted an excerpt from dmesg in post #352. Once the device gets into this state, that log excerpt gets spammed repeatedly until the device is restarted.

The dmesg output is attached to my earlier post #352. I am using your kernel.

crpalmer: Just wanted to let you know I'm still experiencing this WiFi issue running your 1/15 build. dmesg output is exactly the same as what I posted previously. I can't say for certain, but it appears to be occurring less frequently. Please let me know if there's any way I can help debug this.

Whoa, whoa, whoa ... what's with the tone? I have read up the thread, and I have used the search function, thank you very much. I could only find one mention of this (the post I quoted from yesterday) and it contained a screenshot of the log messages. I thought I'd contribute a textual version...

I'm having the same problem. A couple times now I've woken my phone to find WiFi turned off and dmesg is chock full of these. Attaching a textual dmesg excerpt.

OK. I've had some time to get to the bottom of this once and for all. When you performed your "clean reinstall," did you also happen to format your external SD card? I believe you must have. I just found that FileManager had proper permissions to access the external SD card. However, there was...

I was curious which nightly ROM you installed. Just trying to get a sense of what's different between our clean installs. I just completely removed the FileManager app and dirty flashed crpalmer's 20170108 build and yet the problem persists. I'm curious how many other people are having this...

Thanks for the info. It's even more strange because I'm having the problem even though I'm also running a clean install (@crpalmer's 20170104 nightly). Just curious - which ROM did you perform your clean reinstall with?

Have you managed to fix this? I have the same issue. File Manager can't access the external SD card, even though the "Storage" permission (which is the only permission listed) is enabled and root access mode is also enabled. I've tried disabling/re-enabling the permission, disabling/re-enabling...

Actually, the stock HTC ROM provides at least 3 methods of waking the phone (and I did not configure fingerprint authentication): 1.) Power button 2.) Home button 3.) Double-tap screen If I may add my two cents: having alternative methods of waking the phone can be lifesavers. The physical...

Thanks! That did the trick (size-wise, at least - I'll see if the image boots and works later). I wasn't aware that the pme blobs were up on TheMuppets repo already. crpalmer has apparently been moving right along! :good:

I was going to take a look into the MTP issues in my spare time, so I decided to pull down source and start a build. However, the zip I just built was only 412MB, whereas the nightlies hosted by crpalmer are ~507MB. I haven't worked on CM since CM11, so I feel like I'm missing something new in...

Thanks for putting this together, Rahulrulez! I just made a bunch of updates to the spreadsheet with regards to the T-Mobile Galaxy S4 (SGH-M919). I also found a few entries that were vandalized by people who apparently have nothing better to do with their lives, so I fixed them up as I went...

Unfortunately, Wi-Fi calling requires a working radio because T-Mobile uses info from the SIM card to authenticate the phone. Also, the GB and JB kernels have a large number of differences. Getting the GB kernel to work work properly with CM10.1 would require a tremendous amount of work, and I...

Thanks, Adam. You're correct - in the end I did not need to modify any scripts. FYI, I was able to fix my adb / USB issue with a simple solution: Perform a full wipe before flashing a CM10.1 ROM. :p However, I also discovered a workaround just in case anyone encounters a similar problem where...

Looks like it was simply an issue with the proprietary files. I incorrectly assumed augmenting the proprietary files in Adam's p999 repo with the files in the CM p990 repo would do the trick. I pulled the proprietary files off my phone and used them in the build, and sure enough, the build works...

Thanks for the response, Mazout360. I removed the p990 line from my local manifest as you recommended. I tried another clean sync and build so that I could post clean results here. Once again the build errored out because it couldn't find a number of symbols referenced in LGEInfineon.java. After...

This actually belongs in the dev thread, but I don't have enough posts under my belt to do so. I have tried building CM10.1 for the p999 for a few days, to no avail. I understand that the build is currently a modded p990 build, and after sifting through the makefiles and diffing my ROM against...

Can't believe I haven't stopped by to say hello before. Hi, everyone.

Logs generated, PM sent!

Thanks for the tutorial, loganmc10! I have built many CM7 KANG's for the G2x without issue, but I seem to be having some problems with CM9. I figured out what I assumed was the proper way to build CM9 for the G2x a few weeks ago, and your tutorial matches what I did, so I know I'm on the right...