yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
are the people with random reboots running viperxl? i have experienced random reboots running stock kernel on viper ever since 2.0 was released (actually had one today) . flar, will this command work even on stock kernel? would be nice to run this after a reboot and find out why the hell its happening (especially since i get reboots no matter what kernel im running)

edit: btw, every reboot i have experienced has been while NOT using the phone. the phone would be sitting there doing nothing and randomly reboot. its so weird, i wish i could find out why the hell this happens. im hoping jellybean would somehow fix it (new base, new software, etc etc)
[AT&T, Rogers HTC One X, Telstra One XL] Red5:
I'm on LE from Xs. I was on 3.1 and had two random reboots today. The last one I had my phone in my hand texting someone and it rebooted. So I d/l 3.2beta2 and chose the 850 option.
[AT&T, Rogers HTC One X, Telstra One XL] fadetoblack2104:
I've noticed that my phone is running at the max pretty much every time the screen is on. Is this normal. Running 3.1 with 2.0 oc and gpu oc as well. Intillidemand s2w off and zram on.
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
I haven't had any reboots since going to "slight undervolt" on 3.2b1.
[AT&T, Rogers HTC One X, Telstra One XL] CB620:
Do you undervolt every time? I never did it. Any advantages?
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
I'm on CleanROM 5.1 about 80% of the time, and latest Viper the other 20%. Never had a random reboot, and I use my phone quite a bit.

Reboots can definitely be caused by apps or ROMs, especially if they're heavily modified. There are always bound to be some bugs. But just to be sure, anyone having reboots should up their voltage by 50mV. You can up your voltage either with an app like Kernel Tuner or Venom Tweaks, or by installing 3.2beta2 with a higher voltage option.

That command will work with any kernel.

However, I'm not sure if it will work on Viper if "disable logging" is checked in venom tweaks.

Nope, that's not normal, it could be an app running wild.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
is this something that can only be run right after you have a random reboot? i had one about 3/4 hours ago, worth running? lol
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Yes, it shows the kernel messages from before the last boot. So unless you rebooted again after the random reboot, it will have the messages fromt the time it randomly rebooted.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
damn. i rest it again when i flashed a new radio (thinking the radio could be the cause of the reboot, because im out of ideas tbh) . ill try it next reboot :D

edit: btw flar, i ran the cmd just to test. was able to open that txt file and saw the ACPU PVS line in there. just another way of finding what kind of chip you have (maybe without having to restart and run the command right at boot?)
[AT&T, Rogers HTC One X, Telstra One XL] carl1961:
install Lumberjack and you can email any logs to yourself or maybe flar2 can come up with a email address that every one can sent these logs instantly
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
I just did it the last time I flashed. It stopped the reboots.
[AT&T, Rogers HTC One X, Telstra One XL] katdog75:
Hi Flar,

I have been very stables for ages now. However, I have been having random reboots with 3.2. running my previous voltage settings. I increased my voltages and the reboots have stopped - however at a cost of increasing my voltages by 50 more than with 3.1

If I get a crash again I will send you the log. :)
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Thanks Carl, I didn't know about that app

If you install Lumberjack, email the logs to bertona.tab(at)gmail.com

************************************************************************************

Anyway, I think I'm going to delay release of 3.2 until we test this a bit more. Not sure what's wrong with it but it can't be too bad because it's hardly different than 3.0 and 3.1, which have been downloaded 1500+ times, plus a bunch of people probably downloaded it from Venom Hub, and not too many reports of problems.

I would definitely appreciate log files from anyone experiencing problems
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
Will do, but like I said, I haven't had a single reboot since upvolting.

BTW, there's a beer in your inbox. :cool:
[AT&T, Rogers HTC One X, Telstra One XL] chinchillachubby:
flar2

I am extremely not happy with this kernel !!!!! 3.2 beta 2

For some reason my battery won't die ...

My phone is super snappy

And I've had it up since 6 this morning 14hrs

Have about 3 hrs 51 min of screen time and still at 66%

All joking aside I thank you for all that you do

I know you do this for our phones to optimize their functionality

Come payday I'll send something your way

Again thank you and happy holidays!!!!
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Reboot bug just got me too, surfing pics in fb app this time. Here's a log. Got me twice yesterday surfing tapatalk app.

http://db.tt/Pn7iz8tP
[AT&T, Rogers HTC One X, Telstra One XL] ECEXCURSION:
sh-3.2# dmesg | grep ACPU
<6>[ACPU] select_freq_plan: ACPU PVS: Fast
<6>[ACPU] select_freq_plan: Applying min 1.15v fix for Krait Errata 26
<6>[ACPU] select_freq_plan: Max ACPU freq: 1512000 KHz
<6>[ACPU] cpufreq_table_init: CPU0: 13 scaling frequencies supported.
<6>[ACPU] cpufreq_table_init: CPU1: 13 scaling frequencies supported.
sh-3.2#

Yay, I've got a "Fast" phone apparently. I guess this means I want 850mv to maintain my stock voltages. I'll test out your beta 2 this weekend.
[AT&T, Rogers HTC One X, Telstra One XL] Red5:
I've got a fast phone too... 850 has been good for me for the last 4 hours.
[AT&T, Rogers HTC One X, Telstra One XL] wdkingery:
Hey I'm on 3.1 here, and in my area we just got LTE. well what a heat LTE causes! I was busily searching for movie tickets on my phone when it started getting hot, then slow.

So I tried to turn the ghz down in kernel tuner, but it wouldn't stick! Nothing I did slowed it down. I had to put it on the a/c in the car for 5 minutes to bring it back down, and reboot it. I turned down the voltage over a whole volt, from 1300 to 1200.. Didn't help.

I was at 1890 mhz, went back and flashed 1.7ghz later that day.. Hasn't happened since, altho I haven't dint any LTE searching since.

Thoughts?
[AT&T, Rogers HTC One X, Telstra One XL] paulk_:
What core settings are recommended for ElementalX? Noticed that it seems to default to both cores after rebooting, and if I set it to 1 core (in Venom Tweaks) it seems to completely shut down the second core. Settings 1 core in Venom Tweaks is supposed to set dynamic core usage and not completely shut it down

p.s. Forcing both cores is extremely smooth, even with power saving bias at 60 (max speed 1512). Choosing 1 core is a bit laggy even with power saving bias at 0 as the second core never seems to come on. Either way seems to be chomping at my battery like crazy though
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
I know it's a long thread, but flar has addressed this several times. He recommends not tweaking the cores at all and letting them do their thing.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
just to add to this: ive had nothing but issues messing with the core settings. as elvis stated, id leave it alone. i set powersave bias to 40 (runs at 1.35ghz in browsing mode) and i ont have any lag. in 3.2 flar tweaked intellidemand a little to have the CPU ramp up / ramp down quicker. will probably make the kernel faster than it already is.
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Hopefully that was an isolated incident. I'm on LTE for about 10 hours a day and it will get warm if you're web browsing, but it shouldn't get hot or slow down. LTE will definitely use more battery, but I still get 20 hours on a charge easily.

@iElvis: thanks man :cheers:
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Anyone who wants to test, please use this latest beta

ElementalX-v3.2beta3:

http://goo.gl/8qPQK

(If you tried downloading this before 12:44, download again)

I reverted the intellidemand tweaks, it's the only thing I can think of that changed from 3.1 to 3.2 that would affect stability.

I also tweaked the voltages a slight bit, giving an extra 25mV to 2.0GHz on three of the voltage options.

@jrior001: thanks for the last_kmsg, unfortunately I forgot I had "quiet" on the command line, we should get useful kmsg with beta3
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
Maybe just a coincidence and it's voltage issues?
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Possible. I don't think the voltage selection method I've used should cause issues but you never know. Luckily I didn't change that much from 3.1 to 3.2 betas so we should be able to isolate the problem. First step is to revert the intellidemand change and see if that helps.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
How about adding governor settings to the elementalconf file? Allow people to change it to there preference? (If you find that's what is causing stability issues).
[AT&T, Rogers HTC One X, Telstra One XL] paulk_:
3.2 beta 2 running rock solid for me (only 12 hours in though)

192 - 1512

850mV

sweep2wake

no GPU OC
[AT&T, Rogers HTC One X, Telstra One XL] ECEXCURSION:
I think it's just people setting the wrong voltage for their phone in beta2. I'm gonna stay with beta2 since I have found the correct stock voltage for my phone.

Sent from my HTC One XL
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
I've also run into strange issues when upgrading between versions of kernels. I say the real test should be a full wipe (for all kernels)
[AT&T, Rogers HTC One X, Telstra One XL] bimmernut318:
People are reporting that they have fast cpus and running at 850mv the device is stable, I have a nomimal cpu and I have just wiped and flashed viper fresh with the stock kernal and want to come back to elemental. Is there a good starting point voltage wise for me, I was stable on elemental 2. and 3. until I started going back and forth and trying betas then the reboots started.

---------- Post added at 10:23 AM ---------- Previous post was at 10:22 AM ----------

I am thinking this too!
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
e

That's why I think there's something wrong with the betas. Before the 3.2 betas, everybody was running undervolted (at 800). I'd suggest 850 for you.

Everyone on the earlier betas should move to beta3 and see if it's stable.
[AT&T, Rogers HTC One X, Telstra One XL] ECEXCURSION:
I couldn't use your default of undervolted in 3.1, it simply wasn't stable for me until I selected the "stock" voltage. Unless your stock voltage in 3.1 was actually undervolted at 800mv. Is that what you were saying?

Sent from my HTC One XL
[AT&T, Rogers HTC One X, Telstra One XL] slippers67:
All you guys with problems...stop undervolting, stop overclocking, and use a standard governor, like ondemand. At least do this to verify everything is working.

It'll give you a baseline (and a reliable device). Then when you start tweaking things, you'll know what caused the problem, rather than just guessing and hoping your phone will boot or remain stable.

This thread seriously makes me cringe sometimes, with all the conjecture and problems. Flar, perhaps the default settings on the kernel should be fully stock? Might reduce your tech support workload. :)
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
^^That's excellent advice. But I do think something's up with 3.2 beta because there have been about 3000 downloads of this kernel and its only been since the beta that there have been a lot of problems reported, including by my trusted beta testers .
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
id say 99% of peoples issues come from voltages/overclocking. whether thats not setting voltages high enough for overclocking speeds, undervolting too much, not selecting the right voltage option for your type of chip, etc. no reason to switch the governor to ondemand though, intellidemand works just fine. my opinion of course

as i posted before, the best way to test each version is after a full wipe. the issues could even come from the rom and may have nothing to do with the kernel.
[AT&T, Rogers HTC One X, Telstra One XL] thedauntlessone:
I seriously suggest people not to undervolt. Unless you undervolt aggressively, you won't see much battery difference. If you undervolt aggressively, your phone might random reboot which uses more battery than the undervolt saves.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
some would be surprised how little undervolting or overvolting effects battery life.
[AT&T, Rogers HTC One X, Telstra One XL] CB620:
Running the beta untouched and I'm getting good life. Also trying to burn the battery but it takes some work.

Awesome job.
[AT&T, Rogers HTC One X, Telstra One XL] bimmernut318:
Which beta are you running?
[AT&T, Rogers HTC One X, Telstra One XL] CB620:
v2 beta
[AT&T, Rogers HTC One X, Telstra One XL] ECEXCURSION:
Atta-boy, v2 is where it's at.

Sent from my HTC One XL
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
notice any performance improvements with the intellidemand governor (ramp up/ramp down quicker)? havent tried 3.2 yet.
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
Flashed this morning, same settings as before (850), and I've been stable so far.
[AT&T, Rogers HTC One X, Telstra One XL] CB620:
For me I was on v2.1 for the longest. I notice transition speeds are way quicker. After 4 hours standby my battery was 96%. That's real good. I'm on 11hrs with 2 1/2 hours on screen time and battery is at 60%. Just been browsing and opening numerous apps trying to kill my battery. Haven't uv/ov I left everything untouched and just themed it that's about it.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
V2 or 3? We're you stable on v2?

Just to make sure, you meant you noticed a speed increase from 2.1 > 3.2? Or were you running 3.1?

And that's good you didn't touch voltages. After seeing all of these issues id recommend only undervolting the lowest frequency if you really wanted to, and no more than 25mV if stable
[AT&T, Rogers HTC One X, Telstra One XL] CB620:
I was running 2.1 but after noticing random vibrations and reboots with the latest Venom Rom I tried the beta and its performing better than ever.

2.1 was stable for me for the longest up until the 2.4.0 update of Venom. Everything before that was great. I got almost 26hrs and 5hrs on screen time. I posted a screenshot in the venom thread

---------- Post added at 05:36 PM ---------- Previous post was at 05:35 PM ----------

I just flashed v3 too early to call any hiccups but will post if I notice any.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
And the only thing that was touched was the intellidemand governor? How could changing ramp up/down settings cause reboots? Doesn't make sense to me. Has to be the voltages that some are running.

Bottom line, nobody should be messing with voltages . Maybe the 192mhZ settings, but that's it. You want it 10000% stable? Leave the voltages alone.
[AT&T, Rogers HTC One X, Telstra One XL] hyun18:
Reboot reboot annoying reboot. ... And getting FCs and just lost my messages.

Annoying. Can this be caused by an unstabler kernel?
[AT&T, Rogers HTC One X, Telstra One XL] slippers67:
Another thing to keep in mind is that with android devices everyone seems intent to undervolt AND overclock at the same time. Talk about a recipe for disaster.

Sure there are some devices where you get a top-binned cpu that can handle this, but in general the engineers that designed it have a better idea than you or I about what voltage and speed will work best, without causing problems.

I've been overclocking CPUs since before the days of the Abit BP6 and dual Celerons, and generally you don't try to decrease the cpu voltage at the same time that you overclock. In fact, you would normally increase the voltage when you overclock, or otherwise sacrifice stability. Yes, this isn't an ancient motherboard from a defunct company, but the fact remains: a higher clock speed almost always requires more power to maintain the same level of stability.
[AT&T, Rogers HTC One X, Telstra One XL] wdkingery:
i'm thinkin it was the ZRAM that got me cooking, if you'll remember my previous incident (not the one before that lol)

all seems well without it
[AT&T, Rogers HTC One X, Telstra One XL] CB620:
Honestly if you do a flash of a kernel and wipe after you shouldnt have any issues.
[AT&T, Rogers HTC One X, Telstra One XL] harry655:
flickering & distorting icons. Just thought I'd mention, I disabled 3rd party keyboards & using the sense kb, it's made a huge improvement, no distortion & flickering is almost disappeared!

Question, how to overclock gpu? Kernel tuner doesn't seem to work.

Sent from my ViperXL 2.4.0
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
b3.

I was stable on b2; I bumped the voltage up to 850 when I first flashed it, and I've been fine ever since.

To be honest, I was never that unstable to start with. At worst, I was getting 1-2 reboots a day on 3.1 after I decided to overclock to 2.0.

Battery life seems better on b3.

---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------

Are you on this kernel? What settings?
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Could be caused by all kinds of things.

I hope you're not using the beta. You should be using 2.1 or 3.1, which are stable.

Of course, you need to use sane settings. Custom kernels have a lot of options and allow you to select settings that may not work with your hardware.
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Read the OP, it has all the answers. I'm just going to quote what the OP has said for weeks:

And it's true. This kernel is barely different than stock. I don't modify all kinds of things, I just add a few features. Hundreds of people use it as a daily driver. But it also enables you to push your hardware to the limit. If you're having problems, that's the reason. If you constantly flash and modify stuff, you will have problems. I keep my phone clean and organized, use settings my phone can handle, and I've never had a single reboot, but I enjoy extra features, enhanced performance and great battery life.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
if you find out that tweaking the governor was the cause of everyones reboots, would you consider an aroma option? i definitely like the idea. but again, i just dont see how changing that would cause reboots. :confused:

you should add in gigantic bold/underlined letters in the OP "undervolt at your own risk" lol
[AT&T, Rogers HTC One X, Telstra One XL] thedauntlessone:
Your post is also annoying. You give no info on your install, and just whine.

Hint: No one else is having similar problems, so it's probably error on your end. FULL WIPE and reflash.
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
I don't know if the governor tweaks were the culprit yet, they were only changed in beta 1 and 2, reverted in beta3. Governors are notoriously finicky.

Anyone having troubles on the releases definitely needs to increase their voltage, because they are tested and stable.

I won't be doing the open beta again, lol. Way too many people downloaded it.
[AT&T, Rogers HTC One X, Telstra One XL] bimmernut318:
Thanks, I can see the truth in this, I am not a flash junkie and have only flashed updates to this kernel and viper. I did not have ANY reboots until I started screwing around with flashing add-ons and whatnot. I started playing around with voltages and flashing mods and got some reboots. I have just wiped and installed viper and ran it for a day on the stock kernel and all was good and flashed this b3 a few hours ago and all is still good. I will keep an eye on it and see how it goes. Thanks to everyone in this thread that has lots of good input, you know who you are! And thanks again flat for all your hard work.

Sent from a slithery smooth phone!
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
This:

Just like you can't slap an aftermarket turbo on your car and expect it to work reliably without some tuning, you've got to find the optimal settings for your CPU if you're going to start overclocking.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
stick to your trusty beta team, 3.1 came out perfect :silly:
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
Beta3 running solid all day. On lowest undeevolt like always.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
were you on beta 2 previously WITH reboot issues? id suggest for everyone to post which version they were running previously and if they had issues or not. itll probably help flar out, and in turn getting out a stable release :D
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Learned my lesson :)
[AT&T, Rogers HTC One X, Telstra One XL] bimmernut318:
Come on, you have to feel really good about answering all these really jacked up questions, it has got to keep you on top of your game:p

Sent from a slithery smooth phone!
[AT&T, Rogers HTC One X, Telstra One XL] jrior001:
I had posted it before in the discussions about beta2. Had just a couple of reboots on b2.
[AT&T, Rogers HTC One X, Telstra One XL] ECEXCURSION:
Beta 2 here reporting in, running solid since it came out (sane voltage levels) and zram enabled.

Sent from my HTC One XL
[AT&T, Rogers HTC One X, Telstra One XL] currydude:
All 3.2betas have been solid, I reckon it's just people using the incorrect voltage with the more aggressive intellidemand governor
[AT&T, Rogers HTC One X, Telstra One XL] joho5:
With kernel tuner is it normal for cpu1 to stay at 1.9...even if i slide it down to 1728...it immediately reverts to 1.9
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
^^The more I look at this cpu frequency stuff, the more strange things I notice. There is a lot of stuff going on with cpu frequencies on this device. Now I'm not so sure Kernel Tuner is best thing to use either.

Btw, this kernel uses the exact same overclocking modifications as the other kernels for this device (except Beastmode, which has an extra step to 2.1 and some different options in setup)

I have a proper fix for this, but I need to do more testing.
[AT&T, Rogers HTC One X, Telstra One XL] joho5:
Your fine....mine seems to have stuck with no frillz with the box ticked to not allow any apps to change CPU.
[AT&T, Rogers HTC One X, Telstra One XL] Skizzy034:
Can the sleep to wake from beastmode be added to this?

---------- Post added at 06:17 AM ---------- Previous post was at 06:15 AM ----------

The same thing is happening to me with beastmode.
[AT&T, Rogers HTC One X, Telstra One XL] ki11bert:
This is a really cool kernel. Thank you dev.
[AT&T, Rogers HTC One X, Telstra One XL] caviera:
Is there anybody else that have the camera issue at viper 2.1.2?

Whatever sense otg kernel I flash, with this rom, camera doesn't work.
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
A couple of the weird things about cpu frequencies I discovered:

I was wrong, it's not the thermal daemon that's changing min freq to 384. It's actually HTC WebCore. Whenever you use the network it changes the min frequency to 384. The way to stop this is to ensure that permissions are set to read only on /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_frequency. Elemental v1.3 sets this permission automatically, but some of the overclocking apps change it back to read/write, which allows webcore to set it back to 384.

The other thing is that most of the overclocking apps only set the frequencies on CPU0. So if you use NoFrills, for example, your second CPU is left running fult tilt at 1998MHz no matter what you set. Kernel Tuner seems unable to make the max frequency stick, and it reverts to 1998, as some of you have noted.

These observations apply to all kernels, not just ElementalX

All the kernels basically use the same code to overclock.

I'll consider adding sweep to wake after I figure out the cpu frequency stuff (which is probably not that important, since everyone's been living with it so far, but it bothers me).
[AT&T, Rogers HTC One X, Telstra One XL] yaooitsbrett:
I'm having the same camera issues as well