Search results

Does this kernel work well with stock roms? I'm using the 7.x SL!m rom - just curious if I can safely install this with that.

16.6 didn't quite work for me in this case. Battery life on the other hand... I was getting down to 30% within 5 hours of unplugging. Maybe 1-2 hours of SoT in that time span. Never had gmail crashes though. That's a new one for me.

So after a few weeks with the beta, I've gone back to the Android 7 SL!M rom. There's a lot to like about ZTE's work on this Oreo build but it's too buggy for daily driving. The main issues stopping me from daily driving this: Battery life is awful - even with the jojoc fix Magisk and modules...

Abysmal if I forget about the magisk issue and my phone has rebooted recently - 5-6 hours before I get down to 30% battery with maybe an hour of SOT. If i reinstall Magisk, I'll get about 2-3 hours of SOT and closer to 12 hours before reaching 30% battery.

Magisk crashes any time I reboot the phone. I then have to reboot into recovery, uninstall it and then reinstall Magisk and my modules. I noticed this was mentioned in the other thread as well. Is there a fix? This rom seems prone to random reboots so I end up finding out it's broken...

So I've noticed that enabling encryption after I sign into Android locks me out of TWRP. TWRP wants a password to decrypt but when I enter the one I use for Android, it fails. Encrypting for some reason also seems to break the camera entirely. Not sure why. Edit: NFound has posted that AEX...

I just switched last night and I like how the rom looks and feels. The stock camera app included with it crashes every time I load it for some reason. Other camera apps have no problems running - including for example, the built in camera in Textra. I tried GCAM 4.0 that's been floating...

With a standard 0.4mm nozzle, the model with all the holes will not be printable on an FDM machine. Maybe with an 0.2mm nozzle but I think the holes will still cause problems.

Soft reboots while I'm doing something. Sometimes the screen goes black for an extended period and then it becomes a hard reboot. Last stable build was at least 3 builds back. Most recent one from 9/26 still has issues. I've done a clean flash with the 9/26 build and still experience it.

Is anyone else getting random reboots on CM since the last few updates?

Is your phone bootloader unlocked and do you have a custom recovery like TWRP already? You'll need to do that whether you install CM14 or 15. If you install CM14, you probably won't have a clean upgrade path. Dirty flashing generally isn't recommended for major updates like that. You will...

bluetooth audio has been skipping a lot in the last 3 weekly builds. Any ideas on what could be causing it?

According to that thread, Lineage OS already supports AptX. Does the device support aptx-hd?

You have to use Magisk for root. SuperSU and LineageOS's versions of root will not pass safetynet from my experience. I don't know if it helps but I also have the Play Store and Nintendo's games enabled on Magisk Hide.

Your post touches on some of my bluetooth audio "issues" on LOS. The volume curve is not even at the lower registers and on low impedence headphones, can easily get to the point of causing clipping and hearing damage at just 50% volume. There's a huge jump in volume from a volume of 3-4 over...

Some minor differences between the two, but nothing huge. I've swapped the files and restarted my phone. I have the same issue with volume controls. The LineageOS file has no defined curve for music. All devices call a "Default_media_volume_curve". Not knowing what that is, I defined a...

The curves seem easy enough to figure out, however, i'm not sure WHICH stream types I should be editing for this specifically. The headphones I tested with are actually low-impedence wired in-ear headphones and connected to a bluetooth amplifier/headset combination. Looking at this chart...

I have noticed that the volume control on my device has never been a consistent/gradual increase/decrease since switching to Lineage OS. Specifically, if the volume almost doubles when I go from 3 clicks up from 0 to the 4th click. I have very sensitive headphones and 3 clicks is too low, 4 is...

You have the latest. I've used the alarm every morning to wake up for the last few weeks without issues. Sound is perfect through headphones/bluetooth. I don't use twitch so I can't comment there. I use chrome - it works like a dream. The in-built android browser is not advisable. In fact...

Got it! One of the other EDL guides said to reboot recovery. I found a guide elsewhere. Follow these steps. The full guide with screenshots has some very out of date instructions for bootloader unlocking. but you can see it here: here. Enable USB Debugging and the OEM Unlock Feature In...

Yep!

I've flashed the B15-New_TWRP_EDL file using the xiaomi tool and when I boot to recovery, I see a black screen now instead of TWRP or the stock recovery. Trying to run the fastboot command from here, I just see a "Waiting for Device" message. How do I work past this?

I got mine a few weeks ago... great case. Feels way nicer than the stock one. I didn't like the rubber texture at first but its grown on me. What I've noticed: The indentation for the fingerprint scanner is a bit deep and I'm using the tip of my finger more than I was before. As a result...

Aside from the usual risks that come with rooting, does this method work reliably? I use my phone as a daily driver and I was worried that this approach would cause a conflict somewhere

Better battery life, got rid of the stupid notification bell, and lost my ability to root because I hadn't rooted before the upgrade. Hopefully Tenfar or someone will provide a solution soon, but it's not the end of the world.

It's not ZTE's job to block ads for you. Most vendor-specific flavors of android don't offer built-in ad blocking. If you want to complain to anyone, complain to Google for not allowing extensions in Chrome. They're lagging behind IOS there. Use adguard like others have suggested, or root...

Some quirks in UI decisions that ZTE made which make no sense, but generally speaking, it'm pretty happy

My understanding is that the HIFI chip doesn't work with apps that don't support it. Is that wrong? I never notice it and Atmos doing much for Google Play Music

This worked on my old Sony and it seems to work here as well: Go to your phone dialer and enter this: *#*#4636*#*#

I've been running 3.1 since it came out and last night was the first time I used GPS for navigating in my car. Google maps for directions and the phone plugged in to the charger with the screen on. I was losing GPS every few minutes. It would grab the signal again after several minutes...

The task switcher seems to find random moments to clear itself of all running tasks in the background. They're there and still running but the switcher behaves as though nothing is there... This goes away with a reboot, but it happens at least once a day. I also saw this with the last 2.x...

This worked for me.. First several attempts to root on 575 failed because of a "CHMOD /path/to/file/ Not Found" error that left me stumbling and barking up the wrong tree - every solution I saw in other threads didn't work. What worked was updating my Android drivers. Once I got that, I was...

I've lost root and recovery since installing 3.0. I haven't needed to root my phone since... Slimm 2.0, probably. It seems a lot has changed and the 291 firmware has made it harder to root. I'm a bit out of the loop on how to re-root at this point. Locked bootloader, no access to TWRP for...

I experienced it while driving over the weekend. It resolved itself after a reboot. The timing just sucked because I was in the middle of downtown during a festival, driving to a neighborhood I normally never visit. It made me realise how much I rely on bluetooth and GPS as a navigational crutch.

Bluetooth audio has been cutting in and out a lot (kinda like a skipping CD) since 2.1 . How would I go about checking if it's the rom or something else?

Try a factory reset. I had a similar issue when I did an OTA update from 1.7 to 1.8. Chances are something went wrong during the upgrade.

Can I upgrade from Concept? Or do I need to wipe my device first?

It's a wireless protocol used for connecting sports sensors - heart rate monitor, speed/cadence (for cycling), etc. The Z3 line of phones come with the ability to handle it. I've got a Garmin bike computer I can also use, but having access on the phone would be really useful for going on runs.

Is ANT+ working on the beta? Spring is coming and I'd love to hook up my heart rate monitor and bicycle sensors to the phone. The concept rom doesn't support it.

Upgrading got me stuck at the pink boot screen so I reverted back. I'll have to try again tonight. Maybe it needs a clean install?

I finally decided to go from the last stable to the nightlies. Is there any way to reduce the frequency at which the Active Display shows up? I have it set to never repeat notifications, yet I still see my phone's screen blink on every 3 seconds even though I have it set to never redisplay...

Google Now is broken I'm no longer able to run Google Now after the most recent update. I'm on the latest Task650, GAPPS, and Ktoonsez kernel. So far, I've done a cache/dalvik wipe and a fix permissions. I have also tried clearing app data for Google Search. So far, no luck. Before I go...

Swagger Activated!

Damnit. You guys have convinced me. Backup in progress. Factory reset in... 5 minutes

I haven't tried Task's rom since I got my phone back in August. Maybe it's time to give it another whirl

Re-Flashing CM wasn't doing it. It'd still black-screen on me. Stock kernel is a good idea. I should dig it up. As for the Nandroid. I was quite dumb not to. On the flip-side, I had a Carbon backup and now I have a fresh OS install. Back to the issue. I just realized the 3.0 is actually...

I'm on CM10 M3 right now. I've tried both the 3.0 and 3.4 versions of the kernel and I get a black screen on boot. I've had to do a full reformat to get my phone working again. Simply doing a factory reset wasn't doing it. I had to wipe my internal storage entirely in order to get the phone...

After some mucking around, this appears to have worked (so far). I also did a clear data on the download manager and play store.

On a Rogers/AT&T S3 with CM10. I'm seeing the same bug. I've tried uninstalling facebook, reboot, and a clear data on the play store. No luck getting it to go away yet.

I have the same issue as you for item 1. I'd love to see that fixed. I just realized this is in the wrong forum - there might be better luck in the D2att forum... I found this thread on google