yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] GrandAdmiral:
Haven't updated to 4.2.0 yet (still on 4.1.0), but I have been having this wifi issue since moving to 4.X.X. i saw earlier in the ROM's history (pre-Sense 5) someone mentioning that they've been getting an authentication error on certain hotspots. I've since started getting the same errors after moving to Viper 4.0. There was a link to a possible solution that was provided {http://code.google.com/p/android/issues/detail?id=34212). Does anyone know if this fix is compatible with this version of Android? It only seems to happen on my home network.
[AT&T, Rogers HTC One X, Telstra One XL] danix180:
I fixed my issue!!

It was probably some corrupted files under DCIM\100MEDIA

So I just had to rename that folder to 100MEDIAold, cleaned up Gallery app and re launched it. That way a new 100MEDIA folder was created and all my pictures showed up again...
[AT&T, Rogers HTC One X, Telstra One XL] nrap:
what is the command to flash the firmware update? is it "fastboot flash zip 2.15.0000_5...zip" if im already in teh folder where the zip file is?

and will it hurt anything if i rename that stupid zip file? its a pita to type out all those numbers underscores and whatnot
[AT&T, Rogers HTC One X, Telstra One XL] anarchychris:
Follow Turge's instructions

http://xdaforums.com/showthread.php?p=45072132
[AT&T, Rogers HTC One X, Telstra One XL] nrap:
been trying.

error cannot load file

or

error: cannot determine image filename for "2.15.000..."

is what it tells me.
[AT&T, Rogers HTC One X, Telstra One XL] thedailyl3af:
Copy the exact file path to the folder (c:/user/Fred/download/fastboot/firmware.zip) for example. Paste after Fastboot flash zip (pathtofirmware.zip) hit enter and do it again for the final flash. Finish commands and done.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] anarchychris:
If you follow the instructions in Turge's thread you'll be fine. Make sure you follow the instructions word for word. I have followed these same instructions without issue. Take your time and make sure you read and understand all the steps
[AT&T, Rogers HTC One X, Telstra One XL] nrap:
done.

apparantly i was fat fingering the long filename. and i forget to use right click. tried to ctrlV with no luck. then realized after your posts i could right clikc paste!

thanks guys

i should add this rom is killer. the only issue i have had in teh week since i got it was the data/wireless dropping off.

no wakelocks, no crashes nothing. if this fixes the connectivity, this'll be my rom till... well the next update. but such a solid rom
[AT&T, Rogers HTC One X, Telstra One XL] 53l3c7a:
If you start typing a long filename and then hit Tab, most terminal emulators should auto complete it for you. Just be careful it completes the right filename.
[AT&T, Rogers HTC One X, Telstra One XL] maxpower2078:
Is it required to update the firmware to move to 4.2.0?

I am on 3.2.8 but want to update and I don't have S-OFF as of now.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Yes it's required if you don't want signal drops or reboots. I think it's time for you to get s-off, it's really simple. If you can read and type you can get s-off.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] maxpower2078:
hmm... well I think I can handle at least one of those I guess. Does the HBOOT version matter to get S-OFF or is it just super CID and root the only requirements?

Also, so after I get S-OFF should I update the firmware first and then the install the rom or does that order really matter?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Root and SuperCID are the only requirements. The order doesn't really matter but you'll already be in fastboot so I'd suggest updating your firmware first and then flashing the ROM.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] mac20dnangel:
I always get random reboots.

Don't know why.

I am on S-OFF and HAve a Super CID.

I have installed it correctly but still getting random reboots specially when my HOXL is on standby mode.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Have you updated your firmware or flashed the Beastmode kernel as suggested?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] mac20dnangel:
yeah. but still nothing happens that resolves my problem.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
What kernel settings are you using?

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Xak:
I use Elemental X 8.2.0+ for Sense 5 and have stock voltages and stock clocking at 1.5 GHz and Sweep to wake and BLN get kernel from forum search red point compilation roll up. Hope helped use set CPU app to make profiles and save battery.

Sent from my Viperfied AT&T HTC One X 4.2.0 along with Elemental X 8.2.0+!

If my settings don't work keep messing around reflecting kernel till it works like a champ. Stock GHz for longer battery life plus profiled. Click thanks if I helped.
[AT&T, Rogers HTC One X, Telstra One XL] mac20dnangel:
Im using the latest Elemental X right now with fiops and intelldemand and just the stock voltage and cpu speed.
[AT&T, Rogers HTC One X, Telstra One XL] Xak:
8.2.0 works keep re flashing untill you find right setting I use stock and changed to stock GHz 1.51 or something like that and it worked no reboots and use intellidemand and fiops took me 15 different combos of flashes untill no reboots check extra voltage on kernel install. Change to ultimate minefield settings in Viper XL tweaks

Sent from my Viperfied AT&T HTC One X 4.2.0 along with Elemental X 8.2.0+!
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
If you can't get Elemental to play nice, try using the stock kernel.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Bob in Northern NJ:
Really Strange Sense Widget Anomaly

Earlier today, I tried to install a viper animated background from the hub for the App Drawer and Notification Pulldown backgrounds. It didn't work, so I uninstalled it. Everything on the phone continued to work fine, as I inadvertently moved some widgets across screens, and had to move them back.

Then tonight, after I charged the phone up on my car charger for 3 hours while I was in a meeting:

I can no longer move the widgets or folders around on my screens. When I long press an open area of the screen, nothing happens, it doesn't open the widgets screen to install widgets. If I tap an existing widget on any of my screens, it opens the app normally as it should. I just can't move existing widgets, or install new widgets on any of my screens. If I tap a folder on my screen it opens the folder, and I can move the app icons within the folder around, and the apps start and run fine.

So what ever I did, appears to be limited to just the widgets.

I have rebooted. No Change.

I have wiped cache and dalvik cache. No Change.

I have done a fix widgets in venom tweaks. No Change.

I have done a fix permissions in venom tweaks. No Change.

I am thinking I may have inadvertently changed a setting, but I can't for the life of me figure out what!

Any suggestions would be humbly appreciated!
[AT&T, Rogers HTC One X, Telstra One XL] silverburst11:
Maybe, on the home screen hit the menu, is lock workspaces checked?
[AT&T, Rogers HTC One X, Telstra One XL] Bob in Northern NJ:
Great suggestion, but no that isn't it. I can move apps around inside of their folders, but I can't move the folders around, nor can I move the widgets around. Long pressing on a blank space of the screen doesn't open the widget menu either.
[AT&T, Rogers HTC One X, Telstra One XL] Xak:
RE flash rom for a fasty. Probabalbly a bug. No need to wipe data.

Click thanks if I helped. :D
[AT&T, Rogers HTC One X, Telstra One XL] gr8lats:
Pretty sure that Turge suggested to not use the animated backgrounds for now.
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
Yeah he told me that, make sure you turn off notification background and app drawer backgrounds that might help
[AT&T, Rogers HTC One X, Telstra One XL] Bob in Northern NJ:
Thanks guys. Pretty sure you're both correct. Lesson learned!

Late last night, (Very early this morning?), I did a Titanium Restore of HTC Sense Desktop which, after reboot, eliminated the problem. I was going to dirty flash the full 4.2.0 ROM as Techinstein suggested if it hadn't worked. After reading 696Kris's post a few minutes ago, went into Tweaks>Sense and turned Use Background Image to OFF.

Thanks everyone who had suggestions!
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
No bother bob. happy to help.
[AT&T, Rogers HTC One X, Telstra One XL] xxcaptcrunchxx:
Thanks guys! I didn't hear about the background issue. I'm still using them, have been since I flashed, but now I'll know if anything goes wrong. Or I may just stop...probably the smart thing.

Just want to say I love this Rom and this forum! There's a bunch of stand up guys in here. Did my research, used all the tips and guides from everyone to update firmware, kernel..etc. Didn't run into one problem!

I'll never go stock again :D

Thank you thank you thank you!
[AT&T, Rogers HTC One X, Telstra One XL] eoraptor:
OMG someone PLEASE help me before I murder someone.

I updated from 3.8 to 4.2 of Venom XL today.

ever since installing, play store is not working for me, I either get Error 927 or error retrieving server information RPC:S-5:AEC-0

I have tried deleting and recreating my Google Account, tried wiping the cache's both in android and in TW, tried deleting my Google account, force-stopping and then wiping Google Play Services and Google Device Framework, and tried Factory Reset.

Nothing is working, and the symptoms are the same on Wifi and on Data.:eek:

HALP!
[AT&T, Rogers HTC One X, Telstra One XL] zeroth:
I'm having the same issue, it was working fine this morning I think. so I don't know, maybe is the play store server?
[AT&T, Rogers HTC One X, Telstra One XL] eoraptor:
Okay, I feel mrginally less insane right now... y upgrade was coincidental. it is a thing. since at least 3:30 pm EDT today http://www.androidcentral.com/google-play-experiencing-issues-most-everyone
[AT&T, Rogers HTC One X, Telstra One XL] Pdj7969:
Did anyone receive a System Update notification that said Illegal Copy and then didn't do anything? I canceled it and then checked the System Update option in Settings and it shows nothing is available. Weird as hell.
[AT&T, Rogers HTC One X, Telstra One XL] Turge:
Looks like the ViperOne rom is getting the same thing. Must be a problem on the server causing this. We're looking into.

Just ignore it for now and sorry for the inconvenience.
[AT&T, Rogers HTC One X, Telstra One XL] Turge:
Please let us know if you guys are still having the issue.
[AT&T, Rogers HTC One X, Telstra One XL] zounduser:
U guys should b pretty happy on this rom huh?!!!! Im using my one x for the first time in months, and this rom, its exactly the same as what is on the ONE! im amazed! Good job viper!
[AT&T, Rogers HTC One X, Telstra One XL] Madridista7:
Not sure if this issue has happened and has been answered, but I searched and didnt find anything. Anyways, heres my case. I've been using this rom for a while now. I recently updated to 4.2.2 and also updated the firmware of the phone. Yesterday my phone simply decided to eat the battery. The phone battery (complete charge) lasted like, 7 hours without me even using the phone. I decided to charge it completly again. While charging the phone was really hot. I disconected it after charging it completly and went to sleep. Today when I woke up the phone was off and for some reason it wont charge. Its been connected to the charger for more than 5 hours and not even the red light will come on. I've changed it to different power outlets and nothing.

Anyone know anything? Maybe the battery fried somehow?
[AT&T, Rogers HTC One X, Telstra One XL] oranget:
With your phone not coming on and not even the led showing while plugged in it sounds like your phone is bricked. Have you plugged it into a computer with a usb cord, see if it recognizes it?
[AT&T, Rogers HTC One X, Telstra One XL] Madridista7:
It doesnt come on in the computer, so i dont think its bricked. Havent flashed anything to it either other than the viper rom and updates.
[AT&T, Rogers HTC One X, Telstra One XL] oranget:
If it shows qsusb download on ur computer or not registering on ur computer at all when u plug it in, it is bricked. Mine did same thing 4 months ago.

---------- Post added at 12:16 PM ---------- Previous post was at 12:14 PM ----------

I was just flashing a kernel on mine and it died.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It isn't necessarily bricked, this sounds to me like it could be the power management bug that we see on this device from time to time. Keep it plugged in for about eight hours then try to power it on (leave it plugged in while trying). If standard power on doesn't work, try holding power for a couple of minutes, if that doesn't work try holding volume down plus power for a couple of minutes. If that doesn't work, disconnect it from the outlet and try those methods again. I'm not saying this will definitely work but I've seen a few phones that looked like they were bricked come back to life from this bug.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Madridista7:
Hopefully its that. Its been plugged in for about 5 hours now. I really dont want to buy a new phone v_v. But still no led turning on or any signs of it doing anything.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
If it is the power management bug you're experiencing, I believe the led won't activate again until you successfully zombify that thing (bring it back from the dead).

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] Bob in Northern NJ:
You didn't mention anything about flashing a custom kernel. Is the phone significantly overclocked in the kernel settings? Voltage settings?

Presently, there are only 3 kernels I've seen discussed that work well for this ROM, stock, Beastmode 3.5, and ElementalX 8.1.

There was/is an issue with the beastmode 3.5 kernel and phone not waking from deep sleep. It has been covered extensively in this thread. Since you stated that you have been running the ROM for a while now, and only recently upgraded the firmware to 2.15 I am assuming that you are using a custom kernel. In the 4.x.x ROM install instructions, it is stated that you either have to install 2.15 firmware, which you did, or install the Beastmode 3.5 kernel. Either, or, or both. Or else there are issues with the ROM working correctly. Especially if you are coming from the 3.x.x version of the Viper Rom. Also extensively covered in the thread was an issue with Google Play Services constantly running and consuming the battery. It is an issue with Google, and it self corrects via updates from the play store.

First, get your phone booted. You have to hold the power button down and continue to hold it down, until the phone reboots from the "permanent" deep sleep.

Once booted, hook up your charger. Go into Settings>Power> and turn Sleep mode to "OFF". Reboot the phone again. If you are using either the Beastmode or ElementalX kernel, check your Min/Max CPU settings, and voltage settings.

Since you have the 2.15 firmware flashed, you really don't need a custom kernel IMHO. I've used both Beastmode and ElementalX, and had many of the problems discussed in this forum. Since reflashing the 4.2.0 Full Rom, and switching to the stock kernel, I have had no problems at all.

Try reinstalling the 4.2.0 FULL ROM, not the OTA update. After you have the ROM.zip file on your SD card of your phone, go into TWRP 2.6.3 Recovery. On the WIPE menu, wipe cache. Then wipe dalvik Cache, then do Factory Reset, then wipe system (TIMMAAA!!!! LOL!) Then go to the TWRP INSTALL menu and install the ROM. Be sure to select "Full Wipe" on the Aroma Install menu choices. Also, select to let the Viper Install optimize itself. This will give you the stock kernel with optimal CPU min/max settings, voltage settings, and 3D frequency settings that are the best for your hardware.

If you are still having battery issues, then I suggest you try this: http://xdaforums.com/showthread.php?t=712990

You will need to let the ROM, kernel, and firmware "settle in" for a day or two as well.[/QUOTE]
[AT&T, Rogers HTC One X, Telstra One XL] Madridista7:
Phone didnt have any custom kernel. It was using the stock one. I'll go ahead and keep the power button on and see if it wakes up.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Just for the record Bob, this power management bug has absolutely nothing to do with the Beastmode kernel (or any kernel for that matter). It's a bug with the phone itself, it's been happening to dozens of these phones ever since the release. What ROM/kernel you're on has no impact on whether it'll happen to you. I've seen it on multiple ROMs, both Sense and aosp, and on multiple kernels. Just make sure you're 100% on the advice you're giving, this advice would have had the user go through a lot of steps that weren't necessary. The post also points blame at the Beastmode kernel, which is incorrect.

[MENTION=4580700]Madridista7[/MENTION]

You don't need to reflash your ROM or kernel or anything once (if) you bring your phone back to life, it isn't required. Good luck, I hope it wakes up for you.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] zounduser:
Ive been on beastmode with this rom for about a week now.. working fine for me so far. Im noticing one bug, when going back to the homescreen from doing anything like web browsing, youtube, basically anything that is longer than a minute, sense takes about 6-7 seconds to reload.
[AT&T, Rogers HTC One X, Telstra One XL] Bob in Northern NJ:
[MENTION=4153349]timmaaa[/MENTION], I understand what you are saying, however, I had the exact same problem when I first flashed 4.0.0 with 2.15 firmware, and the beastmode kernel. Stayed with it through the 4.1 and 4.2 OTA's. Had a whole host of other problems as well, like the several seconds wait delay that is mentioned in one of the posts above, multiple random reboots through out the day, phone getting hot while charging, etc. I changed to the ElementalX kernel, but only used it for a day, because the 4.2.0 full ROM came out so I've been stock ever since.

After mashing the power button so many times, I had to turn the sleep function off in settings>power to get the phone to not go "dead" when charging over night as was finally suggested as a fix. A couple of times it wouldn't wake from sleep when it had just been sitting for an hour or so. Madridista7 does confirm what you are saying however, that the problem apparently occurs regardless of the kernel used, as he is using the stock kernel.

For the record, I'm not knocking/blaming the Beastmode 3.5 kernel, I am simply stating that

ALL

of my phone's performance problems went away after re-flashing the 4.2.0 full ROM and switching back to the stock kernel. And to that end, there's nothing "wrong" with reflashing a clean install after experiencing multiple issues with an initial install. Sometimes that is what is necessary, and it only takes a total of what, 3 minutes if that? Geeesh! You'd think I was contributing to the Government shut down!:p
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
It's highly possible you just had a bad flash and that flashing again fixed your issues. I've run every version of Beastmode without a single hiccup. I'm saying that though, there is a group of Evitas that can't handle the Beastmode kernel. Anyway, what I'm really saying is that to effectively help people here, and to give good advice, you need to be able to properly identify the problem that someone is complaining about. I mean, the solution to his problem had already been posted, and yet you wrote a reply the length of a sort story which contained a bunch of irrelevant stuff.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] trichrome1:
Yep, this happened to me a few times, not with this ROM in particular, but the phone sometimes just doesn't want to boot into recovery after a bad flash.. Just have to mess with the buttons to get it to charge.. And unplug and replug it into power or sometimes a PC.
[AT&T, Rogers HTC One X, Telstra One XL] Bob in Northern NJ:
Whatever Timmaaa, whatever. You tend to come across as extremely condescending.

Properly Identify the problem

---First thing I said was the wake from deep sleep issue. So problem properly identified.

Second thing I said was problem was related to Beastmode kernel, which was an erroneous statement on my part, which was corrected by you, and acknowledged by me after your correction.

Solution to problem already posted

---That happens all the time on this thread, because most people who give of their time to respond to someone who's posting about a problem experience on here are trying to be helpful to that person. For the record, the only other response prior to mine, posted by you, was incomplete as it only addressed the failure to wake issue, and none of the other issues the OP stated. Even in your response(s), you only addressed how to get the phone turned back on. You never even mentioned the actual solution which was posted by several other users when the ROM was first released and people began reporting about it.

Irrelevant stuff

---That's your opinion, which as previously stated, is quite condescending. The OP stated

multiple

issues...wake from deep sleep (and the related failure to charge when in deep sleep), hot charging, and high battery consumption. Everything I posted addressed ALL of these issues, each of which I also experienced with my Evita upgrade to 4.x.x ROM. The solutions provided were based on my successful experience of resolving these same issues on my device.

What is important in the end, is that we were both trying to help this person.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Alright Bob, I have much to say about that, but I'm not entering into an argument with you.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] mentalityx:
Not the place for this gents. Still need to hear back from Madridista7 if his device ever powered on.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Yeah, hence me not continuing the discussion.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] NY_HAMMER:
Any news on magic jack ap is not working on this rom?
[AT&T, Rogers HTC One X, Telstra One XL] Madridista7:
The device never turned on. :( I tried pressing random buttons and everything. Nothing seems to do the trick. :/ Im thinking the battery must have fried or something somehow.
[AT&T, Rogers HTC One X, Telstra One XL] mentalityx:
My condolences on your loss.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
That's a real shame. It's possible it's bricked, but it's also possible that it's still ok. It can take several attempts (many) to bring it back sometimes. One of the Evitas in my house had this happen, I tried many times to revive it to no avail, then someone else tried the same method and it kicked over first try.

Sent from my Evita
[AT&T, Rogers HTC One X, Telstra One XL] mentalityx:
Given that I would say leave your device alone and try again in 24-48hr time.
[AT&T, Rogers HTC One X, Telstra One XL] 24ky:
I had almost the same issue as you, just I plugged my phone in one day and the LED turned on but every time I look at the battery percentage it kept decreasing and finally it died and wouldn't turn on ( trust me I was [MENTION=865515]***[/MENTION]ing bricks ) but I left in on charge for another 8 hours and it still wouldn't charge so I disassembled the whole device ( Not recommended if you don't know how to do it ) and after an hour I put it together and it still wouldn't charge but I held the power button for 30sec and then plugged the charger back into the device and LED showed it was getting charge.... Just care to share my experience and how I fixed it on my XL. And that's like a week after flashing sense 5 on my device without the new firmware... But ever since I have had the new firmware installed I havent had an issue except for one complete signal drop