yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] Aldo101t:
yeah mine won't change either, but they all stayed the same for me cuz I dirty flashed, everything seems ok except for that, so far
[One (M9) Android Development] aooga:
[MENTION=1102297]Sneakyghost[/MENTION] - I just flashed everything over again (firmware and rom) with a full data wipe and I still get the same message. I even tried picking "default" instead of Tmobile US in the aroma installer. I still get the same message.

Any other TMO users on 2.0.0?
[One (M9) Android Development] Tecardo:
Uncheck the old firmware option in aroma, after that your kernel version is

3.10.49-g4ee4c46

Gesendet von meinem HTC One M9 mit Hilfe von XDA Forums Pro.
[One (M9) Android Development] Sneakyghost:
The problem withe the HTC One M9 is, that its using newer Android security measures, which have the side-effect of a simple restore of a stock NANDROID not being enough to be able to get HTC OTA's.

If you want to update via stock NANDROID, you need to have one which was taken before /system was mounted R/W for the first time. If you got such a NANDROID, you have to flash back the system.win.emmc file from that backup (rename it to system.img if you want) using fastboot (fastboot flash system system.img), or else HTC OTA's will fail for you.

This is because TWRP would, upon restore completion, automatically mount /system as R/W and thus break system integrity again, which in consequence disables HTC OTA.

Sounds complicated? It is. A little.
[One (M9) Android Development] Behold_this:
Yes it is, but what I said was if they're on old firmware they need to select the old kernel.
[One (M9) Android Development] xunholyx:
No. You can't flash firmware in recovery.
[One (M9) Android Development] Behold_this:
Yes there are T-Mobile users as well as T-Mobile testers. Also if you flash the updated firmware you should have never been choosing the T-Mobile option in the first place as that gives you a mismatch with the kernel.
[One (M9) Android Development] Tecardo:
Have you tried to go to service app, don't know if it's existing in tmous. But otherwise no idea.

Gesendet von meinem HTC One M9 mit Hilfe von XDA Forums Pro.
[One (M9) Android Development] aooga:
So here's what I have right now.

1.40 firmware

Default setting for carrier. NOT Tmobile US

NOT checked 1.32 kernel.
[One (M9) Android Development] xunholyx:
Sorry, I didn't mean to contradict you. I was just letting the AT&T users know that there is that option as well.
[One (M9) Android Development] Sneakyghost:
Yeah well if you have 1.40 firmware and 2.0.0 ROM with "default" selection everything should be working, even on TmUS (except their Wi-Fi calling). Dunno whats going on. Might want to report in a ticket with a log of "fastboot getvar all", that screenshot and a brief description of the issue, then the supporter who picks it up can assign it to the developers to look at.

He just said he did that and also chose default in Aroma and it wouldnt work.
[One (M9) Android Development] aooga:
I don't care about wifi calling :)

I'll wipe one last time and maybe re download the rom. I'll report it if it still doesn't work. Thanks.
[One (M9) Android Development] Behold_this:
Try toggling SELinux off and on again a couple times then reboot and see if the error still pops up. We did have the similar problems with motion gestures in testing and that was the common fix and I see another user posting it fixed it for them.
[One (M9) Android Development] aooga:
I tried toggling it multiple times, but the same error still pops up. Weird...
[One (M9) Android Development] Behold_this:
Are you restoring anything, out of curiosity? I know you said you did a clean install but did you restore stuff afterwards?
[One (M9) Android Development] zorantoma:
it did fix it ,but now i got masive lag again on gesture wake up. before i toggled SELnux and rebooted the gestures were instant.
[One (M9) Android Development] aooga:
The aroma settings were automatically restored, but other than that, no. No HTC backup/restore or Google.

I just realized that I've been using the "no red text" 1.40 firmware. I'm going to try the standard 1.40 one and see if it helps.

EDIT: Nope, even with the stock 1.40 firmware listed in the google sheet, it still has the same problem. I'm going to try another 1,40 based rom and see if I get the same issue.
[One (M9) Android Development] Behold_this:
Sounds good, let us know.
[One (M9) Android Development] aooga:
Just edited my post...still the same thing. I'm going to try another 1.40 based ROM and see if I have the same problem. I'll report back whenever ART finishes...it takes a LONG time (as you know).

[MENTION=1249599]zorantoma[/MENTION] seems to be having issues with lag as well. Not sure if related...
[One (M9) Android Development] xunholyx:
Just when you are about to take a week off. Thanks. :mad:

lulz
[One (M9) Android Development] billyho7993:
Yeah same here I dirty flashed too and that's the only one that won't work so far
[One (M9) Android Development] Aldo101t:
yep, same here.
[One (M9) Android Development] aooga:
I just flashed a different 1.40 rom and the gestures work on that. When I switched back to viper, it worked again. Not sure what exactly I did, but it works now. :good:
[One (M9) Android Development] shokouhi:
I have read through the thread a bit. It would seem that some Tmous users are having a hard time with the new base? I have downloaded the 1.40 base firmware (No Red Text) and 1.40 base (2.0 Viper Rom). Any Tmous users get this running okay? Thanks in advance!

Shokouhi
[One (M9) Android Development] xunholyx:
The base? Like the WWE firmware package? I don't think you can flash that.
[One (M9) Android Development] PlatinumNick:
if i jump to 1.40 firmware can i flash 1.9.1 since its based off an old base?
[One (M9) Android Development] vizzy:
Having a very odd issue. I installed the latest firmware, and when I install ver2 it goes through the Android is updating and then it goes to a white HTC screen , then the screen just goes blank with the LED flashing. When this is when the setup screen normally appears. I have full wiped, will no apps selected to uninstall , and yet still no luck. I'm not sure what I'm doing wrong ?
[One (M9) Android Development] shokouhi:
I am S-off, Super CID, and running WWE 1.32 rom and firmware now. I am asking if anyone running S-off and Super CID have gotten the new firmware package and Viper Rom 2.0 working together on a TMOUS M9 without compatibility issues?

Shokouhi

---------- Post added at 06:04 PM ---------- Previous post was at 06:00 PM ----------

You may get bootloops. There are not compatible. Run 1.32 firmware with 1.9.1

Shokouhi
[One (M9) Android Development] xunholyx:
Yea, I've never understood T-Mo.

I've heard both WWE doesn't work proper, and also that it does.

If you are already running WWE, I don't see why it wouldn't work now.

Make a backup, and flash the new ROM. Report back on your experience. You won't break your phone, and your input will be valuable to others. XDA 101
[One (M9) Android Development] Behold_this:
Its pretty simple to understand and it works either way on T Mobile devices and network. If you want to run the new firmware, you have to select default install option NOT T-Mobile. If you want to keep T-Mobile features like wifi calling, you will need to have the old firmware and select the T-Mobile option. Either way the rom works perfectly on T Mobile devices.
[One (M9) Android Development] shokouhi:
Thanks for the input. I have been running Viper Rom on TMOUS for a while just fine. I was just wondering if 1.40 was causing anyone issues. I will flash to see.

Shokouhi
[One (M9) Android Development] Behold_this:
The only issue is exactly what I explain to you above. If you want the new firmware, you cannot use the T-Mobile install option. If you want to use the T-Mobile install option, you cannot use the new firmware. Whichever option you want the ROM will work for you.
[One (M9) Android Development] sdamark:
Okay, so... I'm a Verizon user, I apologize. It's the best carrier in my remote area. I am s-off, I am on Verizon firmware. I have been using ViperOne 1.9.1 with no issues. I have tried installing with, 1) no wipe, selecting 1.32 kernel.... everything crashes, restored nandroid 2) no wipe, unselecting 1.32 kernel, everything crashes 3) full wipe, clean install... will not get past "Android is upgrading, starting apps" I allowed it to sit for 20 minutes.

Jan mentioned he was not sure it was tested on Verizon.... I have offered to test....

My recovery is TWRP 2.8.6.4 - S-Off - Verizon - USA

So, my question is "Has anyone on Verizon got ViperOne 2.0.0 to work?, and if so, how?"
[One (M9) Android Development] Aldo101t:
don't select the 1.32 kernel your default kernel will be installed with rom.
[One (M9) Android Development] frankcck:
For any T-mobile US users,

There's only two scenarios that like what [MENTION=4174733]Behold_this[/MENTION] said earlier.

First, you are s-off, wanna use 1.40 WWE firmware without Tmo features such as WiFi calling.

=> update your firmware to 1.40 WWE firmware and unselect "old kernel" in Aroma and select "Default" in carrier option in Aroma instead of T-mobile.

Second, you need WiFi calling feature

=> DO NOT update firmware, stay on 1.32 firmware. And select "old kernel" in Aroma as well as "T-mobile" in carrier option.
[One (M9) Android Development] sdamark:
Yeah, like I said, I've tried both ways. One more time "Has anyone on VERIZON got ViperOne 2.0 to work? and if so, how?" Tried dirty and "Full wipe, clean install" with no success.
[One (M9) Android Development] bschram:
We haven't successfully gotten it to work yet on Verizon as far as I know.
[One (M9) Android Development] 123421342:
So for T mobile users, will 2.0 still function normally without flashing the new firmware?
[One (M9) Android Development] Behold_this:
This has been addressed several times now including once at the top of this very page. Have a look.
[One (M9) Android Development] sdamark:
That would have been good to know on release.

[MENTION=4905624]j to the 4n[/MENTION]

I am still willing to test for you, since your Verizon testers aren't keeping up ;)

PM me, again... Got no response from Sneakyghost last time, I E-Mailed him (couldn't start a hangout).
[One (M9) Android Development] Archangel:
Sorry for all your trouble,,I was about to try this as I am on Verizon too, now I will wait.
[One (M9) Android Development] darkenedpath:
So..... I'm I'm good to flash this on my iPhone6 correct? Lol sorry, couldn't help it
[One (M9) Android Development] Archangel:
LOL good one. :laugh::laugh:
[One (M9) Android Development] sdamark:
Yeah, [MENTION=2744223]Archangel[/MENTION] I would wait until we get this straightened out.
[One (M9) Android Development] brittoking:
So I noticed there's no small apps in the sidebar apk? Were they removed cuz I LOVED THEM!? I even added back the old apk from 1.9.1 but the small app section of the sidebar is just blank now :(
[One (M9) Android Development] Archangel:
Damn, I wanted to get started on Blue VenoM9. Oh well, all good things come to those who wait.
[One (M9) Android Development] ReppinFlorida:
Small apps were FC on new firmware... To many bigger issues were on the priority list for initial release.. they will be reimplamented in update.
[One (M9) Android Development] kaosb0x:
Has anyone noticed you cant get into Motion Gesture Options? Is it just me? i flashed a few times clean flashing, tried with couple kernels also same concept..im s-off with sprint, any help is appreciated :D
[One (M9) Android Development] brittoking:
Same here.

Edit: but with Att
[One (M9) Android Development] hackmania:
if i flash 1.40.201.15 firmware,can i still revert back to tmo 1.32.531.33 firmware?
[One (M9) Android Development] Michaelmansour1997:
Quick question, what are the settings for the best battery life? or is there some type of guide, Thanks!!
[One (M9) Android Development] dmc2359:
If your s-off you can flash whatever you want
[One (M9) Android Development] croaten:
Same for me on Sprint. Swipe up and double tab to wake work fine, but I can't get into the "Motion Launch gestures" in settings to make any changes.
[One (M9) Android Development] Aldo101t:
are you talking the settings in phone or in venom tweaks, the ones on the phone settings are working fine for me ( Sprint )
[One (M9) Android Development] j to the 4n:
Venomtweaks-Advanced-SeLinux: enable permissive

Don't ask why that is required, we don't know either.
[One (M9) Android Development] j to the 4n:
Tried a couple of hours to get them working, without success, [MENTION=1016148]m0narx[/MENTION] and me will try to get them back in one of the next update.
[One (M9) Android Development] j to the 4n:
Blame [MENTION=5618158]bschram[/MENTION] he was drinking beer the last two days and couldn't get it tested :D

Sry for the issues guys, but the last three days were really nerve wrecking and very exhausting.

We were just happy to get all running finally and totally forgot about Verizon.
[One (M9) Android Development] croaten:
I'm talking about the settings on the phone. What Motion Guesture Options are you talking about in Venom Tweaks?
[One (M9) Android Development] j to the 4n:
Mate it has been discussed a few times already, try setting se Linux to permissive in VenomTweaks
[One (M9) Android Development] bschram:
More work than beer, but I'll take the blame. [emoji6]
[One (M9) Android Development] Aldo101t:
the tweak in venom tweaks for changing data icons doesn't work, don't know how to screen shot that??lol

also in settings there is no system update option used to update prl and profile, although you still can with sprint zone app
[One (M9) Android Development] sdamark:
No problem at all. Will wait patiently on the sidelines. :fingers-crossed:

ViperOne 1.9.1 is running just fine, in the mean time. :good:
[One (M9) Android Development] j to the 4n:
Ah, thought statusbar theming doesn't work. Will take a look.
[One (M9) Android Development] Black-FR:
@ charging issues:

Unplug the charger.

Switch the device off, then charge it for a while.

(approximate 5 minutes)

Unplug the charger again.

Now reboot and charge again.

It should now charge with normal speed.

@ motion launch gesture settings menu:

Set SELinux to permissive

(venom tweaks -> advanced)

Afterwards reboot the device.

Now you should be able, to access the menu.

Gesendet von meinem HTC One M9
[One (M9) Android Development] j to the 4n:
They have no "charging" but "changing" issues :D

Signal icons tweaks doesn't work.
[One (M9) Android Development] Aldo101t:
damn, was trying to figure that one out haha.
[One (M9) Android Development] brittoking:
That would be amazing and thanks for the effort regardless of the outcome
[One (M9) Android Development] Black-FR:
OK... Seems as I quoted the wrong one... Or tapatalk did it.[emoji16] [emoji12]

Gesendet von meinem HTC One M9
[One (M9) Android Development] croaten:
Didn't work for me, but I really don't care because I just use double tap and swipe up to wake and those seem to work fine even if I can't access the settings.
[One (M9) Android Development] aka120:
Is it just me, or is anyone else experiencing odd behavior with their preferred network? I'm on AT&T and after every reboot the preferred network is automatically switching to WCDMA preferred. So I have to manually switch it back to GSM/WCDMA/LTE auto in phone info after every restart.

It just started occurring after a dirty flash of 2.0.0 over 1.9.1 (which is probably my entire problem), I just didn't have time for a full wipe and clean install. I'll be doing that tomorrow. I was just curious if anyone else was having the issue.
[One (M9) Android Development] j to the 4n:
Rebooted min 30 times yesterday, still on lte auto for me. Shouldn't behave different on att, but you can try choosing the default carrier option in the aroma installer, instead of att.

Also I assume you are on old firmware and choosed the old kernel to install? Could be a culprit too.
[One (M9) Android Development] aka120:
Yep, still on old firmware. I'll try default carrier as you suggested, if its no go well say it's At&t's old firmware running a muck lol

*Edit* Selecting default carrier resolved the issue. Thanks so much!
[One (M9) Android Development] Michaelmansour1997:
Does anyone have anything on maximizing battery life
[One (M9) Android Development] j to the 4n:
With sofff and supercid you could flash int fw. Not sure how long it will take on att to release the new fw. Could be a week, several or months...or they even skip it and go straight to 5.1
[One (M9) Android Development] j to the 4n:
Use powersaver all the time (I do) turns off the 3-7 cores
[One (M9) Android Development] aka120:
Probably going to be in the range of 2 months if ever is usually how it goes lol. I might flash the international fw in a few days.

I edited my post after trying the default carrier, that got it working ;) thanks!
[One (M9) Android Development] Michaelmansour1997:
i always have that on, are they any other tweaks that will help make the battery last longer?
[One (M9) Android Development] ivicask:
You can tweak up Autobrightness to lower in misc tab of tweaks.
[One (M9) Android Development] qriozum:
I would like to ask whether the "Extended NavBar" displays only five switches, or all selected?

regards

q.

--

wysłane z HTCOne (m9) przez Tapatalk v4.15.1
[One (M9) Android Development] j to the 4n:
Max are 5 atm. Go to VenomTweaks-Buttons-(extended navbar section): Quicksettings to reorder, change them
[One (M9) Android Development] qriozum:
Thanks for your reply :)

I know where there is a panel with a choice of elements "Extended NavBar".

Could do with a separation after the fifth element - then it would be all Defaults legible;)

I noticed some of irregularities related to the "Extended NavBar" and the section "Music Control View '.

Well, scrolling works by "swipe" correctly only when there is no active button "Search".

When it is displayed ("Search"), then he or she during a "swipe" there is no display "Extended NavBar" - whether it be intentional or rather tiny error for correction?

If "Music Control View" is off - then he or she "Search" in no way interferes and "Extended NavBar" is displayed correctly.

regards

q.
[One (M9) Android Development] Michaelmansour1997:
im getting a large battery drain from android system, does anyone know what causes this, and if there are any fixes
[One (M9) Android Development] j to the 4n:
With search it still works its just harder to swipe, since there is no free area to do so. Just use the right side of the navbar and swipe two times to get there (use infinitive scrolling)
[One (M9) Android Development] j to the 4n:
Unusual battery drain is to 99% an user side issue and not rom side. You don't see any other users complaining, currently its just you.. clean flash the rim without installing any 3rd party apps and you will see it will be okay.

Also some more info will help, like screenshots of battery history/stats, and maybe gsam wakelocks. You even didn't say what kind of battery life you got.

Additionally its absolutely normal for android system draining the most battery, if it would be not the case I would be worried.
[One (M9) Android Development] ivicask:
Your not getting large drain, all rest is draining so little that android system is now on top, I also have it at top "battery drain", but by current usage I'm gona go over 6 hours of screen on on this rom.
[One (M9) Android Development] qriozum:
[MENTION=4905624]j to the 4n[/MENTION]

- very precisely written.

"Extended NavBar" displays when it is enabled "Search".

"Extended NavBar" not displayed when it is enabled the" Search "and" Music Control View '.

These three elements must be met together.

If the option "Search" does not affect the display of the "QuickSettings View" that means well and properly get in the box to move and scrolling :)

regards

q.
[One (M9) Android Development] j to the 4n:
really no idea what you mean. I have music view enabled and search button and I'm able to swipe to the music view.
[One (M9) Android Development] qriozum:
Approx.

This by the way, I will make myself Viper with a full wipe :)

regards

q.
[One (M9) Android Development] bschram:
To get the 2.0.0 ROM to boot, remove /additions/carriers/Verizon/system/lib64/libc.so and /additions/carriers/Verizon/system/lib/libc.so from the ViperOneM9_2.0.0.zip and reflash.

Then manually flash the boot.img from /additions/carriers/Verizon/tmp/boot.img using 'fastboot flash boot boot.img' and then clear dalvik cache.
[One (M9) Android Development] j to the 4n:
If you got an issue with the extended navbar a fullwipe definitely wont help. I just dont't understand what you are saying (language barrier)
[One (M9) Android Development] angelky:
i installed 2.0 and when the phone sleep it couldn't awake anymore, but then reboot itself. i dirty flash from 1.91, what should i do now?
[One (M9) Android Development] HTCuser90:
Hi dev

After flash rom,everything boot normal but when im add google account

My phone request update gg play serivce then updated,my imei lost :crying:
[One (M9) Android Development] Archangel:
Okay zipping it all back then I assume flash the 1.4.0 firmware, then the rom then fastboot flash the boot.img all in the same session correct?
[One (M9) Android Development] HTCuser90:
Rom is okay but when sign in google account got a notification update google play service

After updated and lost my imei :D something went wrong :confused:
[One (M9) Android Development] bschram:
Don't flash the 1.4.0 firmware if you have a vzw device
[One (M9) Android Development] Archangel:
Okay cool, so flash the rom and then fastboot flash the boot.img,,,by the way leave the boot.img in the zip dont delete it out?
[One (M9) Android Development] j to the 4n:
its because you didnt read the instructions.

Either flash the new 1.40 firmware. If you don't, your device will reboot when you turn your screen off.

Flashing that firmware requires s-off. Or you need to return device back to stock and take the HTC OTA to update your firmware, assumed that OTA is pushed in your area already, because it isn't in Europe yet.

If you can't update your firmware, you need to choose "flash old 1.32 kernel in aroma" and you wont get reboots anymore.
[One (M9) Android Development] Adam182:
Exact same issue here although its happening after updating the Firmware to 1.40 and BEFORE flashing Viper 2.0. Im guessing this means the FW is causing the issue, phone no longer wakes from sleep and just reboots itself - Adam

EDIT: OK from Jans reply above im guessing flashing 2.0 will fix the problem
[One (M9) Android Development] j to the 4n:
just flash it, not 100% confirmed yet though if manually flashing is actually required.
[One (M9) Android Development] j to the 4n:
read my answer above.

1.4x firmware is incompatible with 1.32 based roms.

Also 1.3x firmware is incompatible with 1.4x based roms.

Firmware and rom base version (kernel) have to match.
[One (M9) Android Development] Archangel:
Okay backing up first and flashing. I assume click the option for the old 1.3.2 kernel in aroma?

Edit- upgrading all apps be back in a few minutes but, so far so good.

After boot and set up noticed gestures doesnt work so far when you click it it just grey's out and doesnt go to the second screen. Gonna see if a reboot helps
[One (M9) Android Development] Cabanne:
Many thank you to all the team, you made a great job.

thank you again ;)
[One (M9) Android Development] j to the 4n:
Fixed Vzw build is on venomroms.com, you might clear your browsers cache for that page (ctrl+f5)

Enable SELinux permissive in VenomTweaks->Advanced, then it should open. Trying to figure out why that is required.
[One (M9) Android Development] Archangel:
LOL that worked thanks,,,putting the rom through the paces and so far it is smooth as ever and super fast, great job!
[One (M9) Android Development] vizzy:
No matter what I did I could not solve this issue, even installing the 1.32 kern. However, for some odd reason other roms will boot up fine and straight away. I even installed IC and then tried to re-install venom but for some reason it's just not having it......very odd......