• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CyanogenMOD 13 UNOFFICIAL Beta 2

Furik said:
I too am having the sensor error. When I try to flash the sensor fix zip, TWRP restarts. When I checked the verification box and try flashing, I get this. Am I doing something wrong?
Click to expand...
You need to turn off zip file signature verification in twrp.
 
Furik said:
I've tried that but when I do and attempt to flash, TWRP restarts.
Click to expand...
The fact is that this problem is caused by something on your phone not being set up right. With that said you might try updating twrp to 3.0 ad see if the issue goes away...just make sure you leave twrp with the default settings
 
Can't get device to be recognized even with system r/w. Gps probs. Battery percentage jumps to 100 after a few reboots. Team blackout YouTube installs but shows Google service error when trying to use it. Volte and wifi calling don't work. Other than that. Pretty flawless
 
Explain then, in laymen's for us newbies. I know the battery jumping to 100 isn't user error. Everything else. Maybe. But can you please explain
 
Blackout didn't have anything to do with my phone showing up as unknown on root checker after changing the build prop. Nothing to do with battery percentage, nor wifi calling and volte. Issues before I even installed the app. Still waiting on that answer
 
crealah said:
Blackout didn't have anything to do with my phone showing up as unknown on root checker after changing the build prop. Nothing to do with battery percentage, nor wifi calling and volte. Issues before I even installed the app. Still waiting on that answer
Click to expand...
WiFi calling and volte doesn't work with these roms ,only stock. You probably flash the wrong gapps. The device model showing unknown has nothing to do with any of your issues and the battery ,well I have no idea. I don't use cm.
 
I use team blackout apps all the time and I've never had any issues with any of their blacked out google apps other than google play music and messenger. All the rest have worked flawlessly.

Just in case you flashed the wrong gapps, you need 6.0 arm gapps. Banks gapps, slim gapps, and open gapps will all work fine as long as they are 6.0 arm.

WiFi calling and volte aren't bugs they are features that don't come in custom ROMs. Cm13 doesn't let you put the date in your status bar but that isn't a bug or an issue...same applies to WiFi calling and volte.
 
This build is running smoothly my only problem is that at random times the signal goes completely down then thr phone states there is no signal. I have to reboot for the phone to have signal again.
 
I flashed open gapps nano 6.0. Maybe it was the superuser app I was using. But wifi calling does come on cm13. The new Nexus models have it. And if you type it in the search in settings it takes you to a page to turn it on. It just doesn't stay on
 
Volte and wifi calling don't work on anything but stock, that you can search for it I'm settings and that there's a setting doesn't mean anything, it's not supported.
 
Blu8 said:
Volte and wifi calling don't work on anything but stock, that you can search for it I'm settings and that there's a setting doesn't mean anything, it's not supported.
Click to expand...
So cm just put it in there for the **** of it? I highly doubt that.. It's fot T-Mobile phones. Whether or not it's implemented on all T-Mobile phones idk but it's working on some
 
You realize this is an unofficial port and not everything is working 100% right? You also realize you can go ahead and fix it yourself as well?
 
Blu8 said:
You realize this is an unofficial port and not everything is working 100% right? You also realize you can go ahead and fix it yourself as well?
Click to expand...
Yes I do realize that and I thought when asked to test devs would accept feedback instead of dismissing what's said. Don't be a smart ass. I'm a very grown man. If I knew how to fix it i wouldn't be asking about it
 
Feedback isn't saying "this doesn't work but it should, do something about it" in order to give feedback to a dev a logcat for starters is nice, and when you bring up third party mods like blacked out apps crashing, that's nothing to do with the ROM and if it were, again, a log would say that.

I couldn't care less how "grown" or "man" you are, I'm not sure why you felt the need to bring that up but all the more power to you.
 
Loving CM 13! Thanks to @hroark13 and all contributors. No problems to report yet with Beta 2, just a couple of questions and suggestions re: install...
Q: under preferred cellular network in settings, 2G and 3G are the only options, and I'm not seeing LTE?
Q: Location is turned on, but even after allowing apps access to location, some can't find me?
S: in TWRP, do a clear cache/delvik after install of cm13 and again after gapps... All other instructions worked perfectly. P.S. - no sensor issues so far, but saw that sensor fix was included in Beta 2, so I guess that is resolved.

Cheers,

-sdt1
 
Last edited by a moderator:
Okay, so a couple of things to note so far in my experience with CM 13 B2...LTE only seems to activate when WiFi is turned off (also to note that even when LTE is indicated, it is not an option in wireless carriers settings... Only 2G or 3G). I tried resetting network settings, but as soon as I make a WiFi connection. LTE reverts to 3G (no LTE indicator). The other issue is that the system randomly will go into a SIM lock. I can unlock it, and then it locks again. The only way I've found to stop it, is to reboot. Lastly, when powered off and charging, the display backlight stays on.
 
Today, I tried reflashing B22.zip to see if it would make any difference in LTE working, but still the same.. No LTE option in Cellular Networks > Preferred Network Type, and LTE only shows in status bar if WiFi is turned off, or for a brief minute at startup. Side note.. I flashed SuperSU with TWRP, and no issues there.
 
You must log in or register to reply here.
Back
Top Bottom