Root [All Carriers][ROM][4.4.4] ViperOneM8 | Android 4.4.4 Sense 6.0 - HTC One M8

cool enjoy - ive been on it a few months now and not felt the need to change it at all ..... apart from the included tweaks obviously

dan55 said:

cool enjoy - ive been on it a few months now and not felt the need to change it at all ..... apart from the included tweaks obviously

Click to expand...

I've ran Viper since i had my EVOLTE on Sprint...never switched!

dan55 said:

cool enjoy - ive been on it a few months now and not felt the need to change it at all ..... apart from the included tweaks obviously

Click to expand...

You updated to the latest build? I held off because Early pointed out some hiccups a while back.

hi Tre.
no I'm still on a 4.4.2 build as i couldn't face the pain of updating the firm ware being s on :-\ :-D

Tre Lawrence said:

You updated to the latest build? I held off because Early pointed out some hiccups a while back.

Click to expand...

I haven't because I've been swamped - but I think that they probably have them sorted, so I will sometime this week. Meanwhile, there's always nandroid.

Tre Lawrence said:

You updated to the latest build? I held off because Early pointed out some hiccups a while back.

Click to expand...

I'm on Viper 2.4.0 and all seems fine at this very moment. The only I would say is under heavy load there's a bit of lag now and again but considering the options and customising available it is expected :thumb:

I want Sprint Wi-Fi calling!

Dan, we need to update firmware? Did I also see we need to update TWRP?

hi Tre,
yes pretty sure ive seen in the viper thread on xda that it needs a firmware update before flashing viper - not so sure about twrp - but i guess that is the case there too
cheers

Tre Lawrence said:

I want Sprint Wi-Fi calling!

Dan, we need to update firmware? Did I also see we need to update TWRP?

Click to expand...

Yes to both, check out Captain Throwback's posts at themikmik.com - you don't need superCID and so forth to update Sprint firmware, just s-off.

International / GSM needs 2.22 firmware, Sprint equivalent is 2.16.

Also - beware Sprint wifi calling. Your GPS will evidently go into a coma if you use it, and there's some very specific steps to bring it back to life.

If I find them first, I'll link to what to do.

And again, expect a link to something from the Captain on that, one of his posts alerted me first. (Frankly I think that a lot of us Sprint users would be lost without the Cap'n, so, big thanks if you see this.)

As I recall, that's a Sprint bug, nothing to do with any one rom.

Yes Cap'n is an icon!

Guys... thanks for the pointers. I'm lost without you.

good luck Tre

Does anyone know how to get the little "X in the circle" the clear recent notifications on the pull down notification bar? I changed a setting somewhere and cant figure out how to get it back.

EarlyMon said:

Yes to both, check out Captain Throwback's posts at themikmik.com - you don't need superCID and so forth to update Sprint firmware, just s-off.

International / GSM needs 2.22 firmware, Sprint equivalent is 2.16.

Also - beware Sprint wifi calling. Your GPS will evidently go into a coma if you use it, and there's some very specific steps to bring it back to life.

If I find them first, I'll link to what to do.

And again, expect a link to something from the Captain on that, one of his posts alerted me first. (Frankly I think that a lot of us Sprint users would be lost without the Cap'n, so, big thanks if you see this.)

As I recall, that's a Sprint bug, nothing to do with any one rom.

Click to expand...

EM: is this the thread you were referring to? [SPRINT][ROM]M8WHL Stock Rooted - Base: 2.16.651.4 (Android 4.4.3) - theMikMik)

Tre Lawrence said:

EM: is this the thread you were referring to? [SPRINT][ROM]M8WHL Stock Rooted - Base: 2.16.651.4 (Android 4.4.3) - theMikMik)

Click to expand...

I'll have to check and get back to you.

Cap's signature there has the firmware and TWRP updates you'll need.

Seems easy enough.

- Nandroid
- Update firmware via Cap's Sig.
- Update TWRP via Cap's Sig
- Dirty flash new Venom build.

Early, any more info on the Wi-Fi calling bug? Couldn't find anything at MikMik.

awesome stuff Tre - congrats

dan55 said:

awesome stuff Tre - congrats

Click to expand...

Haven't done it just yet. Working on it now.

Thoughts on Super CID?

Tre Lawrence said:

Thoughts on Super CID?

Click to expand...

Not if you're on Sprint.

EarlyMon said:

I haven't because I've been swamped - but I think that they probably have them sorted, so I will sometime this week. Meanwhile, there's always nandroid.

Click to expand...

I'm still sitting on the same version of Android that was on the phone when I switched to Verizon and got the M8 in mid-June. I was waiting until 4.4.3 came out and all the bugs were ironed out, but I admit that I'm still confused. It seems like things are still buggy or at least quite complex. In a nutshell, what's the story? The more I read on XDA, the more confused I get.

Lord Vader said:

I'm still sitting on the same version of Android that was on the phone when I switched to Verizon and got the M8 in mid-June. I was waiting until 4.4.3 came out and all the bugs were ironed out, but I admit that I'm still confused. It seems like things are still buggy or at least quite complex. In a nutshell, what's the story? The more I read on XDA, the more confused I get.

Click to expand...

LOL Ditto. Which is why I let the fine folks here decipher it for me!

Lord Vader said:

I'm still sitting on the same version of Android that was on the phone when I switched to Verizon and got the M8 in mid-June. I was waiting until 4.4.3 came out and all the bugs were ironed out, but I admit that I'm still confused. It seems like things are still buggy or at least quite complex. In a nutshell, what's the story? The more I read on XDA, the more confused I get.

Click to expand...

Engineers actually have an equation for risk.

It's really simple.

Risk = ( complexity / maturity )

Iow - if it's new, there's a higher chance of bugs as you go up in complexity.

ViperOneM8 is complex - and I mean that as a compliment.

Personally, I saw a big improvement going from 1.6 to 1.8 - it didn't lose complexity, it gained maturity. Risk of bugs and failure went down.

When revision 2 hit we saw -

A. Some people perfectly happy.

B. Some people with install errors that were misdiagnosed (j4n even recanted his original installation advice).

C. Some people with errors that got traced to mismatches on some existing theme elements. (Those needed time to catch up for example.)

D. Some people with errors traced to new incompatibilities with their favorite Xposed modules. (And of course, some Xposed features replicate Viper features, so that class of bugs doesn't surprise me, fwiw.)

E. Some weird install error that tags you as trying to pirate the rom - so you have to contact the devs right away to clear that. (Don't ask, I don't know, and if I did I wouldn't say because that would probably help the actual pirates lol.)

F. And etc etc that I don't remember.

Iow - it was new. The risk (of bugs) equation never likes anything complex that's new.

Usually, I adopt updates right away. If something doesn't work out for me, I'm a nandroid restore away from where I started.

No big deal.

I didn't adopt early this time because my job has changed and (as evidenced by me not being as chatty as usual lol!) I'm just shy of my usual time for reconfiguring and exploring.

For all I know, I might have ended up in group A (or maybe B, but who knows about hindsight).

So when asked by anyone, any time - should I take the major new update? I tend to always say no, because it signals that the person asking isn't typically an early adopter. (And btw, there's absolutely nothing wrong with that!)

It's not advice based on the rom quality - it's just based on the risk equation.

New = higher chance of bugs or something you won't like (not a guarantee of it, just a higher chance ok).

So - personally, I'd say that so long as you're good on your firmware, and you do a clean install, your risk ought to be pretty low now. It's had time to mature.

If it turns upside down, just do a nandroid restore. No big deal.

It's more likely that it won't.

And as far as bugs - unless you installed the Xposed Fake ID security fix, you're living with a huge bug in 1.8 that you do NOT want to be with anyway.

I still owe a wrap up on the Sprint wifi calling thing but honestly, I've been on travel and don't know the current state of that. Anyway, it was a Sprint bug that Viper inherited, not a Viper bug. If in doubt and you're on Sprint, go ahead and don't use that feature until we're all clear on that.

Helpful or not? Please let me know, I'll be happy to clarify as best I can.

I understand what you're saying. It looks like I can easily wait a bit before trying to install the latest firmware.

I agree with EM. I've been slowing down a bit on early adoption as well for the same reasons. I do not have the time to be a tester, so I'll let the thing mature and let the others be the guinea pigs for me, lol.

Besides, I was also waiting for the VZW firmware only update RUU to be worked up.

But I'll have to say, I've been on 2.5 for about a week now and don't have any problems. I updated by firmware via RUU, did a nandroid backup, and then (believe it or not) just flashed the 2.5 over my 1.8 without even a data wipe. Now I always recommend a data wipe especially coming from one version of Android to another. So I'll just say I got lucky.

good luck

So Sprint WiFi Calling -

If you have an app that initializes and locks hardware GPS prior to WiFi Calling connecting, everything will work properly.

What I've been doing is rebooting the phone and opening Maps as soon as possible, letting it get a lock, and leaving it open until I see the WiFi Calling notification. Then you can close Maps and everything will work as it should (until the next reboot).

I have noticed that my phone won't go into deep sleep while WiFi Calling is connected, which reduces battery life. I'm not sure if this is related to the GPS issue or not. I'm going to try disabling the "Locate Me" feature of WiFi Calling and see if that makes a difference.

Hopefully this issue is addressed with the 4.4.4 OTA (though somehow I don't think it will be).