yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] devilman30:
AlohaJ to the N,

I'm on VZW and I flashed 2.00 and got stuck at installing apps. I waited for about 20 minutes and it wouldn't go any further. Will 2.1 fix the VZW issues?

Mahalo
[One (M9) Android Development] bschram:
Check the zip you downloaded to see if the files I mentioned here are still present. If they are, follow the directions below and try to reflash.
[One (M9) Android Development] devilman30:
Aloha Bschram,

Will give it a shot!

Mahalo Brother
[One (M9) Android Development] croaten:
I'm on Sprint and it works the same as before. Works fine over 3g...doesn't work over 4g.

---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------

Still only works with 3g in 2.0.0 with Sprint.
[One (M9) Android Development] deepsouth06:
Would this be true for At&t users as well? That is if one does not update the firmware.
[One (M9) Android Development] bschram:
Those directions are for Verizon.

On AT&T, follow the directions on the website:
[One (M9) Android Development] deepsouth06:
Ok thanks for the reply. O and flashing the international Firmware on ATT phone should be ok correct?
[One (M9) Android Development] j38mike:
Is there anyway to remove the persistent Wifi calling icon? I tried in Tweaks>StatusBar>Hide Icons>Wificalling, but didn't seem to work- might be something specific to Tmobile wifi calling that doesnt hide the icon?
[One (M9) Android Development] bschram:
Yes. Also covered if you read the website.
[One (M9) Android Development] racrickey:
Same on sprint.
[One (M9) Android Development] deepsouth06:
must have missed that. thanks again.
[One (M9) Android Development] PlatinumNick:
right now i have a tmobile htc one m9 from here in the US. Im tired of us always get delayed updates compared to other parts of the world. So i plan on doing s-off supercid and change my firmware to .401, is that ok with a tmobile us phone because i know its a gsm phone?
[One (M9) Android Development] frankcck:
No problem I can think about.

S-off then SuperCID and changed WWE firmware, and enjoy ViperOne =)

Just note, you will need to select default instead of T-mobile during Aroma installer and you will lose WiFi calling.
[One (M9) Android Development] sdamark:
There is a special download on VenomRoms.com for Verizon. That's all you need. Works great. Enjoy.
[One (M9) Android Development] ksword23:
Why is it that we need to select default instead of T-Mobile? I'm on att and installed it using att instead of default on the new firmware and Viper 2.0.0. Should I have done differently? :0
[One (M9) Android Development] Behold_this:
Because selecting the T-Mobile option will flash a kernel that is incompatible with the new firmware but the AT&T option does not, that's why.
[One (M9) Android Development] frankcck:
If you are talking about ViperOne 2.0.0, then I can tell you that there's no big deal whether you select default or at&t if you are on AT&T, because AT&T carrier tweak doesn't contain carrier specific kernel(unlike sprint, verizon, and Tmo).

FYI, some of T-mobile features such as WiFi calling need proper kernel, therefore, new kernel from 1.40 base won't work with t-mobile features.
[One (M9) Android Development] PlatinumNick:
The only problem that I for see is signal strength? Any info on using wwe firmware on US phones cause any signal problems?
[One (M9) Android Development] aka120:
I flashed the 1.40 firmware on my AT&T M9, and at first the network signal was very poor, however, after maybe 10 minutes it went to the normal strength. I think it was at first hovering around -116 dBm or so, then it went to -78 dBm. So, I would so it appears to be running fine so far with the international fw on us phones.
[One (M9) Android Development] frankcck:
Not that I can see.

Although my M9 stay on DevEd firmware for testing purpose, I have not experienced any signal issue on my AT&T M8 running WWE firmware. I wouldn't say the signal is better than AT&T firmware, but I didn't notice any weaker signal.

If you really worried about the signal strength, you can set new AT&T APN.

Just note, I didn't talk about Carrier aggregation because even AT&T didn't talk about that clearly.

Thanks for report. ;)
[One (M9) Android Development] user602:
You'll get over it. I did it to benefit the community. :silly:

And I get called by that term daily, but this is the first time in German. Only on XDA. :D
[One (M9) Android Development] xunholyx:
The build number in settings is the ROM base/the firmware the ROM is based on. What it says in your getvar under version-main, or in bootloader next to OS, is your firmware version.

That's why you are seeing two different numbers. If you've updated the ROM now, the build number should match. That should cure your OCD. :D
[One (M9) Android Development] tx_jaycee:
I've also found that a good stiff whiskey or shot (name your poison) also does wonders for OCD. :highfive: :victory:
[One (M9) Android Development] PlatinumNick:
you guys are talking about at&t im talking about tmobile? are they the same?
[One (M9) Android Development] frankcck:
Sorry, I was confused. There was another guy asked similar things on at&t.

Yes, they are basically same as long as you don't need WiFi calling.

As [MENTION=4174733]Behold_this[/MENTION] and I replied earlier, you are good to use WWE firmware on Tmo M9.
[One (M9) Android Development] guiltyundertaker:
Battery life appears to be incredible, first charge and I'm on 43% after 15 and a half hours!
[One (M9) Android Development] calebcabob:
So, the Verizon folks who have had bad luck (bricked devices?) here, have they had s-off? Is there any info on this? Or should Verizon users just avoid Viper for now?
[One (M9) Android Development] Behold_this:
Well since Verizon does not allow for unlocking the bootloader by definition anyone running ViperOneM9 on Verizon has s off.
[One (M9) Android Development] Aldo101t:
I haven't heard about any bricked phones?? on the venom site is a fix for you guys, check it out.
[One (M9) Android Development] calebcabob:
Well, I see that it says there's a Fixed version...but I see that warning saying what kinds of issues Verizon people have had...they had to send their phones to Verizon. Yikes.

So, I guess my question is...since the fix, has there been any of these same reports of unworking devices?
[One (M9) Android Development] xavierxxx2p:
+1 on ? I'm still on 1.9.1 don't see the need for 2.0 since there might be a risk
[One (M9) Android Development] bschram:
There have not been any bricked devices on Verizon from flashing the ROM.

We have had two users that experienced an issue with voLTE.

We're not really sure if it is related to viper, root, s-off, or something else. It could also have just been a coincidence and not related to any of these things.

If you have a previous version of Viper running without issue, you shouldn't really need worry about any of this.

The fixed version on the site is a fixed version of 2.0.0 that boots on Verizon. Unrelated to the other voTE issue.

The fixed version may still require a clean install, so make sure you have a recent backup before installing.

Also, related to your question about S-Off, in order to get any custom ROM or anything installed on VZW, you need S-Off. The current method for Verizon is to use a javacard to get S-Off. If you need more info about this, you can send me a PM.
[One (M9) Android Development] sdamark:
There were two, that I'm aware of, that lost VoLTE after installing ViperOne.

There was no way to get it working again, and the hardware had to be replaced.

Restoring backups, RUU, factory reset, nothing worked.

I, however, have been running ViperOne since 1.3.0 on my VZW device, and have had zero issues.

All Verizon M9s including mine are S-Off by Java card. In fact one of the devices that went bad was the guy's that helped me with S-Off on mine.

So, if you are paranoid about damaging your phone???? I don't know what to tell you.

I'm having a great time with Venom ROMs, and, I accept the risk that something I do may permanently damage my phone. Personally my feeling is it was a big coincidence, or maybe I'm just telling myself that to keep from worrying about it.

Either way the choice is, and always will be, yours.

Enjoy :good:

Well [MENTION=5618158]bschram[/MENTION] beat me to it... lol
[One (M9) Android Development] Behold_this:
Well said by both you gents!
[One (M9) Android Development] bschram:
We managed two tl;dr posts in a couple minutes. That takes skill. [emoji12]

Another note, is that both people that had the issue were able to get a free replacement device from Verizon after returning to stock, locked, S-on.
[One (M9) Android Development] sdamark:
That's a fact, jack... :p
[One (M9) Android Development] PlatinumNick:
ok so im on tmobile us and i just supercid and changed my firmware to wwe edition and now im getting ready to flash the new viper so im in twrp recovery trying to wipe my dalvik cache, cache, system, and data but it says unable to mount and failed to wipe four times, what does this mean?

edit:nevermind
[One (M9) Android Development] xavierxxx2p:
Thanks guys! Bscharm and u....I need to buy u guys a beer
[One (M9) Android Development] HTCuser90:
How to add button like here ? :D
[One (M9) Android Development] croaten:
Venom Tweaks > Status Bar > Header > Widgets > Quick Settings
[One (M9) Android Development] Boostjunky:
This happened to me, as well. I ignored it and installed the ROM, anyways.

After booting into the ROM, I had google play services errors. As I had noticed the oddity in recovery with not being able to mount cache, I rebooted into recovery and started over , wiping /data, /system, /cache, and /dalvik-cache. This time it did not show the error, and upon booting into Android after the 2nd wipe/install attempt, everything was fine.

My recommendation before going through the same steps I went through would be to simply reboot from recovery back into recovery and try the same wipe/install steps you tried upon your first attempt and see if the error returns or not.
[One (M9) Android Development] PlatinumNick:
Thanks for the response I got impatient and flashed the rom anyways but i made sure to use the wipe feature in the aroma, and right now the apps are optimizing, I will come back for an update to let you know what happens.
[One (M9) Android Development] devilman30:
Mahalo sdamark... Smooth as butter.
[One (M9) Android Development] PlatinumNick:
T-mobile US users that has switched their firmware to wwe .401 is there anyway to get LTE? i just realized theres no LTE option under preferred network mode?:(
[One (M9) Android Development] angelky:
Anyways, should i do a full wipe to update from 1.9.1 after i updated the firmware?
[One (M9) Android Development] Boostjunky:
Check in [Venom Tweaks] [Misc] [Phone Info].

Scroll down to just above where it says "Turn off radio" where you'll find a drop-down menu with several different options.

Make sure that "GSM/WCDMA/LTE auto" is selected.
[One (M9) Android Development] PlatinumNick:
oh ok good thanks, i guess that overrides whats on the regular stock phone settings network?
[One (M9) Android Development] TheAvatar:
Hi All, I just dirty flashed from 1.9.1 to 2.0.0 after updating firmware and I am randomly getting SystemUI crashes, it will try to restart SystemUI constantly then is ok for a while after a restart. I haven't been able to replicate the circumstance that causes this crash so I am not too sure what to try, I would like to avoid a wipe if possible.

Any ideas?
[One (M9) Android Development] Boostjunky:
It's actually just a hunch. I'm hoping it leads to some answers or a solution for you. I don't have a TMOUS device, so I'm just going out in a limb, here.

Also, did you select T Mobile as your carrier during setup after Android booted up?
[One (M9) Android Development] j to the 4n:
It's a bug, will be fixed in 2.1.0. Happens just on LTE. Will release it within 2-3 hours I hope.

Pm me, if you need it quicker
[One (M9) Android Development] PlatinumNick:
yes i did pick t mobile on the boot up screen. Ill let you know the results later im not in a LTE zone right now
[One (M9) Android Development] TheAvatar:
Ah cool, I can wait :) Thanks.
[One (M9) Android Development] dominikano1:
Everything works fine for me I'm on t-mobile USA, LTE works fine, etc..... The only thing is when I long press the Do Not Disturb setting on the Esq, it actually says "can't start activity! application not found". Is there supposed to be an application for that?
[One (M9) Android Development] oblivianz:
I'm glad you found the problem and managed to fix it. Always quick and on top of things with outstanding support. Looking forward to the new release :good:
[One (M9) Android Development] j to the 4n:
FYI: Currently the OTA Funtion is unfortnately broken.

I put a hotfix in the hub.

Bad thing about it is, that it will cause a reoptimization of all apps.

So it's your choice if you flash it and use the OTA function later...or install the update manually in recovery.

BUT: If you don't install the hotfix and then the update manually it will cause a reoptimization too, because the OTA Fix needs to be in the OTA too for the next update.
[One (M9) Android Development] droidphile:
Anybody able to get neon working on Viper4Android app on ViperRom 2.0 (and 1.40 firmware)? Neon worked for me until Viper 1.9.1 (and 1.32 firmware). Without neon, we can't install SuperAudioQuality driver.
[One (M9) Android Development] Toumbski:
I'm also having the motion launch not available error. Update hasn't finished, fill in sim code to finish it.

Did the selinux method no fix, dirty flashed again no fix, I have latest firmware. And on default network, no T-mous or other stuff. Any one who knows what the culprit could be?
[One (M9) Android Development] j to the 4n:
on 2.1.0 the stock motion launcher app will be installed again hope it fixes it. what firmware you are on?
[One (M9) Android Development] Toumbski:
It's no biggie, just to lazy to push the button.

firmware version is 1.40.401.5, from sneakyghosts thread. Flashed it yesterday evening. Had my phone rebooting all night because I was still running 1.9.1 with the new firmware. So flashed 2.0.0 this morning, no more problems with rebooting. Just the motion launch bug.

Thanks for the amazing work Jan and crew.
[One (M9) Android Development] TheMegosh:
Just woke up after s-off, updating to 1.40 base and flashing 2.0.0. Fully wiped, restoring non system apps with titanium backup. After roughly 5 hours, battery only charged exactly 50%. From 22% to 72%. GSam reports it should be charging about 70%/hour. Did a restart, unplugged and plugged back in and after 5ish mins, the battery is stationary at 72% and GSam reports 1289%/hour charge.

Edit: unplugged, turned phone completely off, charged for a few mins in that state until 75%, unplugged again, started it back up, then plugged it back in. Will report if any change.

Edit 2: another 5 mins after boot, charging, battery won't budge past 75%. http://imgur.com/g4W5dmV

Edit 3: Things are normal again.
[One (M9) Android Development] calebcabob:
OK, that's exactly the info I was looking for. I'm aware of the risk with doing anything related to altering the stock software on your phone...it was just when I saw an additional warning to Verizon users, well I grew curious. After all, I am a Verizon user. Haha. Thanks for explaining what made you add that extra note:good:
[One (M9) Android Development] xavierxxx2p:
I went ahead n flash 2.0 on vzw..everything when great no problem @ all.make sure u download 2.0 vzw one
[One (M9) Android Development] j to the 4n:
​

ViperOneM9 2.1.0 (2nd June)

Additions & Updates

Added coloring of extended navbar music controls

Added coloring of extended navbar quicksettings buttons

Added custom navbar color on homescreen

Added Back custom statusbar clock and header clock color for html noobs, html deniers, lazy buggers, my mom

Added kcal Color Control - Compatible wth 1.40 and 1.32 kernel!

Added custom navbar background

- choose from collection (nearly 200 backgrounds)

- choose from gallery

Fixes & Cleanups

Fixed Sprint Signal Icons not working

Fixed Motion Launch Gestures not opening in Settings->Display & Gestures (hopefully)

Fixed a SystemUI FC some people had

​

ViperOneM9 2.1.0 is available as OTA. (Settings->About->Software Update / VenomTweaks->Advanced->OTA Update)

Unfortunately the OTA Function is broken in 2.0.0. If you want to use the OTA funtionality you need to flash the OTA Fix in VenomHub first.

Else you can just install the OTA also manually.

OTA for manual flashing:

ViperOneM9 2.0.0 > 2.1.0

Fullroms:

Main Link: AFH US

NL/EU Mirrors will follow by [MENTION=2632943]Whiskey103[/MENTION]
[One (M9) Android Development] C.H.T.J.:
Thank you guys for this :)..
[One (M9) Android Development] j to the 4n:
You are not the only one experiencing that, seems a bug with the fw/kernel. Happens also for some on maximus hd. temp solution is to reboot or turn off the device and charge a bit and turn it back on.

thats what works for our beta testers.

Workaround is to flash back 1.32 firmware and check to use old 1.32 kernel in aroma.
[One (M9) Android Development] MagicMan3311:
extended navbar doesnt change view on swype as long i have quicksettings view enabled.

when its disabled, i can swype to music control.
[One (M9) Android Development] j to the 4n:
fat fingers alarm (-:

Not sure why you got the issue, works well here and it was also well tested by our beta testers.

Please make a screenshot of your settings and your navbar.
[One (M9) Android Development] MagicMan3311:
see attached images.

maybe i can record my screen. will try that
[One (M9) Android Development] j to the 4n:
You got a minswipe distance of > 300 and got vertical swipe enabled.

Now the navbar has a size of about 150...you see the issue?

Either decrease your minswipe distance or disable vertical swipe.
[One (M9) Android Development] MagicMan3311:
yeah. havent set it to this value. this got set while i tested the swypes. but even with 0 it doesnt work.

and even with disabled vertical swype it maybe works one time. After that one time it makes a swype animation but after that it shows only normal back, home, recent ... buttons.

How can i record my screen?
[One (M9) Android Development] j to the 4n:
additonally ith search enabled its very hard to swipe from the left side. It really neads an empty area, else it wont work.

it's an user issue (-:, it definitely works as it should.
[One (M9) Android Development] MagicMan3311:
i will share a creen recording with you. PM follows.

EDIT: yeah... you´re right... with search button it doesnt work... thats sad. i used this button to hide the navbar... PM will not follow ;)
[One (M9) Android Development] clever_man:
Doesn't work after OTA 2.1.0. Any idea?
[One (M9) Android Development] MagicMan3311:
This requests a option for hiding the navbar by long-pressing the menu-button. is it possible to add this option to the long-press menu setting?
[One (M9) Android Development] j to the 4n:
Added to my todolist.
[One (M9) Android Development] j to the 4n:
No idea, we had different results with our beta testers. Think [MENTION=4751514]Krocko[/MENTION] had a workaround.

Thing is that I included the stock EasyAccessService without any modification, so it has to work...else its maybe an HTC bug.

Enabling permissive mode should work too for now.

You could try flashing the fullrom on top or a clean flash, maybe it helps.
[One (M9) Android Development] croaten:
I'm still not able to use KCAL after updating to 2.1.0 on Sprint Variant...anyone else? Get the message "KCAL support not found..."

---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------

Same for me...not working on Sprint Variant after OTA to 2.1.0
[One (M9) Android Development] j to the 4n:
Read above concerning motion launch.

We tested it on 1.32 and 1.40 kernel sucessfully. Didn't on sprint and vzw though, murricanos were asleep when we added and tested it.

[MENTION=1930589]shnizlon[/MENTION] has a fix for sure
[One (M9) Android Development] 030575753:
if i am on .15 base (intenational rom), and i want to flash the Combined, NoWipe ZIP's (Cause i dont know if it touch the "radio" part)

did i need to flash 1.32.401.17 first and to 1.40.401.5.

Or can be directly to flash 1.40.401.5

Thanks
[One (M9) Android Development] trev23sks:
What is KCAL?
[One (M9) Android Development] Joangarc:
[/QUOTE] Same for me...not working on Sprint Variant after OTA to 2.1.0[/QUOTE]

Same for me!! I'm not on Sprint.

---------- Post added at 02:39 PM ---------- Previous post was at 02:35 PM ----------

Same for me!! NOT on Sprint.

---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------

Same for me!! NOT on Sprint, and after OTA to 2.1.0
[One (M9) Android Development] j to the 4n:
Color control: Venomtweaks-misc: adavanced.color.control
[One (M9) Android Development] guiltyundertaker:
I updated via OTA earlier and via downloaded OTA from venom sure just now, but tweaks and settings report that I'm still on 2.0.0. Is this normal?
[One (M9) Android Development] HTCuser90:
Where's screen record tweak?
[One (M9) Android Development] Andrewbud:
Didn't work for me either. Did it reset from twrp on it's own? About to try again with the ota.

Edit: didn't work. Log file attached
[One (M9) Android Development] racrickey:
I just downloaded the ota update posted on here then flashed. Worked great!
[One (M9) Android Development] Andrewbud:
Did you download the actual ota through the system or download and flash manually?
[One (M9) Android Development] nuts77:
Just flashed 2.1, everything working great so far.

Viper is the only 1.40.xxx ROM where I could get hotword voice recognition working (tested Maximus and ARHD this morning, with no success - although I'm sure that issue will be fixed soon!).

Kudos anyway :)
[One (M9) Android Development] HTCuser90:
Where's screen recorder tweak?
[One (M9) Android Development] nitsuj17:
i dont even see that as an option on 2.1.0 on verizon. i had selected 1.32 in ota install since i figured that was more likely to apply set up wise for vzw users
[One (M9) Android Development] Black-FR:
Did you install the hotfix, from the venom hub already?

If not, then the ota update won´t work.

You need to install the hotfix first, else the automatic ota installation won´t work.

It´s not available on the M9.

The version, which is implemented on the M7/M8, didn´t work with the M9.

You could download any screenrecorder app from the playstore and use it.

Did you install the hotfix, from the venom hub already?

If not, then the ota update won´t work.

You need to install the hotfix first, else the automatic ota installation won´t work.
[One (M9) Android Development] Behold_this:
It's an add-on option in aroma now. Perhaps you didn't select to install it, or maybe that option only shows on full rom install.
[One (M9) Android Development] guiltyundertaker:
I applied the OTA fix from the hub this morning, I then OTA'd via the system, then downloaded and flashed manually, the only thing I didn't do was select an option for colour control. But, if I go into tweaks I have all the navbar options, backgrounds, etc, just tweaks says I'm on 2.0.0 pro and so does system settings. And if I check for updates it still tries to get me to download OTA...
[One (M9) Android Development] henengel:
Hi guy's,

I have a question.

How is the screen in the image called, and is there any way to flash something else?

Thanx
[One (M9) Android Development] j to the 4n:
you can flash 1.40.401.5 directly, that the cool things about [MENTION=1102297]Sneakyghost[/MENTION] s Firmwares, they are - as the name already says - combined firmwares, so prev firmware changes are merged to it.
[One (M9) Android Development] j to the 4n:
http://xdaforums.com/one-m9/development/firmware-red-t3097678

read the OP carefully.
[One (M9) Android Development] racrickey:
Download and flash manually.
[One (M9) Android Development] xavierxxx2p:
It's there..im on vzw base 2 .1
[One (M9) Android Development] nitsuj17:
not for me. i reflashed the ota to make sure i didnt not tick the option in aroma. did you select the 1.40 install or the 1.32?