yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
I don't know what it does, so I'm not responsible for any further problem, but maybe try the camera fix in the BeastMode thread: http://xdaforums.com/showpost.php?p=33623274&postcount=3
[AT&T, Rogers HTC One X, Telstra One XL] joho5:
So nobody is actually able to underclock:

The low side and the high side of the second core?
[AT&T, Rogers HTC One X, Telstra One XL] caviera:
It works!!! thanks!!.
[AT&T, Rogers HTC One X, Telstra One XL] FreddieP:
What problem did the cam fix fix? Sorry going off topic a bit... i'm on CRVfinal with clean kernel and the sense 4.5 camera. Sometimes the camera starts with a black screen and nothing i do short of rebooting gets the camera working again. Is this what you were experiencing? Thanks!
[AT&T, Rogers HTC One X, Telstra One XL] caviera:
In viper 2.1.2 rom, otg kernel freezes camera and any other camera app when you launch that app. With this fix, issue is no more

Enviado desde mi HTC One XL usando Tapatalk 2
[AT&T, Rogers HTC One X, Telstra One XL] FreddieP:
I'm trying this app... Were you able to get usb memory to Auto mount? I still get the 'unable to charge message'. However, I launch the app, manually mount and OI explorer will launch displaying the sdcard/usb_card folder

---------- Post added at 10:48 PM ---------- Previous post was at 10:35 PM ----------

Also trying NTFS Mounter. But it wont Auto mount even though App description says it will.

Is there something I need to do to get auto mount to work?
[AT&T, Rogers HTC One X, Telstra One XL] FreddieP:
Ran Chainfire's USB host diagnostics attaching USB OTG cable with card reader & SD card attached.

Why are claims support and devices detected indicating no?
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
^^that kind of stuff and things like automounting depend on the ROM and apps. The kernel only enables the underlying stuff that allows OTG to work. I suspect some of the apps available simply don't recognize our device because it doesn't have full OTG enabled in stock.

I really haven't checked out a lot of software or tried to have things automount. I recommend googling for the StickMount apk, I use it to mount and unmount my USB sticks and camera cards and it works well. All I have to do is plug in the usb and click "mount"
[AT&T, Rogers HTC One X, Telstra One XL] FreddieP:
I haven't changed the ElementalX settings from default and have been watching System Tuner display of cpu times for both cores.

CPU 0 is in use most of the time and CPU 1 is used very little. Is the second core only used when absolutely needed to save battery? I was kinda surprised to see it almost not used at all.

Also, should undervolt settings for ElementalX be accessible from an app like Kernel Tuner?

ElementaX has been really stable and psyched to have USB OTG! Thanks!
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Correct, CPU1 only comes online when it's needed.

Voltage settings aren't available now, but will be in v2.0, which will be ready sometime this weekend.
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Elemental-v2.0 released!

CHANGELOG:

-made 1.7 and 2 GHz versions

-add sweep to wake

-add gamepad and joystick support (but not sure how

well Android supports these)

-add voltage control via sysfs

-add zram support (disabled by default)

-disabled fsync

ENJOY and please report any problems
[AT&T, Rogers HTC One X, Telstra One XL] Myrder:
Camfix just fixes the camera.... That's it. Had camera problems on mine until I flashed the cam fix. But before that I tried flashing the leaked 4.2 cam. Didn't fix, so I flashed cam fix and all is well.

Sent from my HTC One XL cellular device over clocked to 1.9Ghz
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
Ramping up quicker = require higher voltages to be stable?
[AT&T, Rogers HTC One X, Telstra One XL] currydude:
Exactly :)
[AT&T, Rogers HTC One X, Telstra One XL] CB620:
View attachment 1568011

View attachment 1568012
[AT&T, Rogers HTC One X, Telstra One XL] CB620:
Probably gonna end up with 4hrs and some change of on screen time. And I'm running the latest beta. No reboots no screen flickering no butt dialing lol no hiccups. I haven't touched voltages I have both cores enabled. I'm running 1.7 with 192. Intellidemand with full brightness. Synching 5 email addresses and GSM/WCDMA on auto. Background sync on.

Don't know what else to say. Don't see why others are having problems if you haven't tweaked voltages. I flashed on top of my previous kernel which was 2.1 not 3.1 but 2.1 and than wiped cache even though aroma did and I'm getting awesome battery life.

Awesome job OP I was stuck on 2.1 thinking it was the best but you outdid yourself :cool::cool::cool:
[AT&T, Rogers HTC One X, Telstra One XL] stoopid2001:
Can someone recommend settings (OC, zram, governor, IO and voltage)for the best stability? Battery life isn't a priority for me, but I need OTG so I don't want to go back to stock. I'm running viper 2.40. Thanks!
[AT&T, Rogers HTC One X, Telstra One XL] CB620:
Install the latest beta kernel with default everything in aroma. And WIPE WIPE WIPE afterwards
[AT&T, Rogers HTC One X, Telstra One XL] carl1961:
the default settings in aroma installer I think is meant to be the stable settings
[AT&T, Rogers HTC One X, Telstra One XL] katdog75:
Hey Guys!

I love Flar's work! This kernel has been amazing for me!

But PLEASE stop with the - "I don't know why other people are having problems" comments unless you have are absolutely sure you have a solution that is going to work for them. When your phone isn't working properly and you are trying all the tricks - increasing your voltages, wiping caches, doing full wipes, increasing your min settings, lowering your max settings, fixing permissions, completely re-installing your rom etc... and your phone is still crashing it is frustrating that you have someone who isn't having issues saying "Mine is fine - I don't know why you are having issues" The whole purpose of the thread is to share information so that development is improved and also for those who are having problems to find answers.

The issues some of us are encountering MAY be issues with uv'ing. Genetics will tell you that when I first came on the thread I was always encouraging people to increase their voltages.

But something seems to have happened last week - because there have been a lot of discussions about stability pop up again. I know ViperXL just upgraded too - so maybe it's not even a kernel issues.. but let's figure it out instead of just saying stating that everything is fine(because yours is) when there are people who might have some legitimate issues.

I know many of you are just trying to give due credit to Flar (and I encourage that - hey maybe a donation too if you have it?) But just try to be respectful of those who are having issues. They aren't all complete noobs. :laugh:

Kate
[AT&T, Rogers HTC One X, Telstra One XL] CB620:
The people that are having problems are overdoing the voltage and the people that aren't having problems are leaving everything default or slightly touching the voltage. If people READ than people wouldn't have to keep repeating the same steps. We already had a couple people in this thread say the cause of their crashing/rebooting/lag/screen flickering came from overdoing settings and when they took advice to leave default or slightly ov they were stable afterwards.

Another example from a problem I was having which was random vibration and screen flickers from me running 2.1 no one else had it and OP told me to update to beta with default settings and report back. I did such and now I have no issues. It was probably a compatibility issue with viper xl being updated.
[AT&T, Rogers HTC One X, Telstra One XL] ECEXCURSION:
The default settings in aroma are undervolted, underclocked, and overclocked - and not stable at all on my "fast" device. This is where most people are having trouble I believe - specifically with the undervolted part. I don't know why flar2 opted to underclock the device by default... I guess the defaults are his settings, but still, it would make more sense to keep them completely stock.

@ stoopid2001, install using the aroma installer, voltage level (850mv most likely), but you can check this if you know what you're doing and read the post the last couple of pages back... then set the max clock speed to 1.5Ghz, and min clock to 192 is probably fine, otherwise you could use 386mhz which is completely stock.

---------- Post added at 11:57 AM ---------- Previous post was at 11:49 AM ----------

I'd be willing to bet that every single stability issue on this kernel could be fixed by doing two things.

Figure out what CPU you have in your phone (to determine what the stock voltage should be). Set that in the Aroma installer and don't overclock

Flash a ROM that doesn't have stability problems... Like the stock ROM or CleanROM.

If that's not the way you like to run your phone.. well... that's a risk you're going to have to take.
[AT&T, Rogers HTC One X, Telstra One XL] katdog75:
I agree! And people should definitely read the threads before posting.

By the same token if there are issues with stability that can be addressed it is good to try to weed them out rather than assume that every issue is an end user issue. (Although we know MANY of then are)

:)
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
I've got a couple log files, and it doesn't look like the reboots with 3.2betas are due to undervolting or overclocking

What I need is the output of /proc/last_kmsg from anyone who experiences a reboot using 3.2beta3 (It has to be beta3 because I enabled some extra logging in that version)

To do this, immediately after crash, use Lumberjack and send output of /proc/last_kmsg to bertona.tab(at)gmail.com

*or*

In the terminal, type:

cat /proc/last_kmsg > /sdcard/last_kmsg

and send me the file /sdcard/last_kmsg
[AT&T, Rogers HTC One X, Telstra One XL] gilmerd:
Hi..i used elementalx 3.0 and 3.1..great kernels..but i was just wondering if anyone else experienced the same little hiccups that i did on these kernels while sending sms or text messages? Sometime during the message sending process the screen would just randomly flicker a few times causing the keyboard to vanish..then i have to press within the message box again to bring keyboard back up and finish message...thanks! It did it with completely clean installs, setting undervolted, overvolted and stock voltages...
[AT&T, Rogers HTC One X, Telstra One XL] dafunk60:
v3.2 Beta 3 has been running well for me, superb battery life, even in an area with marginal cell reception. The phone was pretty much used non stop. Stock voltages, CPU Max 1.7, No GPU Overclock, zRam enabled, Sweep2Wake Disabled, Intellidemand governor.

I did have a 1 reboot around 1am this morning but I didn't grab the last_kmsg until about 3pm this afternoon. If I am reading the log correctly it looks like it goes back to yesterday afternoon, well before the reboot. I've emailed the log you requested in case it may still be of value.
[AT&T, Rogers HTC One X, Telstra One XL] harry655:
@gilmerd

If not already, try using the stock keyboard & completely disable or remove any others. I did & almost all that stuff was eliminated.

Sent from my ViperXL 2.4.0
[AT&T, Rogers HTC One X, Telstra One XL] hyun18:
I did wipe. I stopped getting the FCs, which I now figured must've had nothing to do with the kernel. That's why I was asking if those things can be caused by kernels.

I don't know about the messages though, but Its really annoying when you lose your messages, unless you don't have messages to worry about. So my bad if I sounded so whiny loll.
[AT&T, Rogers HTC One X, Telstra One XL] bimmernut318:
sms backup+
[AT&T, Rogers HTC One X, Telstra One XL] hyun18:
Lmao.I bought go SMS pro, but I've been using the HTC application. I backed up recently, but lost about 2 says of messages after the backup...
[AT&T, Rogers HTC One X, Telstra One XL] c5satellite2:
It has happened to me and others. Crash, reboot, all messages gone. Crash happens at just the right time, text db goes bye bye. Yes it SUCKS! I feel for you. It's not the kernel, just a crash at the right moment.

There is a way to back them up with gmail, but I have never tried it out.
[AT&T, Rogers HTC One X, Telstra One XL] ECEXCURSION:
Happens on the stock One S as well.

Sent from my HTC One XL
[AT&T, Rogers HTC One X, Telstra One XL] =JKT=:
Best performance on my phone yet (on latest viperxl, 1.7 GHz). This kernel got everything right, I think.

In terms of battery, I even watched like an hour of streaming video! I would leave it discharging overnight to see how long it would last, but I need a fully charged phone for work.

Thanks!
[AT&T, Rogers HTC One X, Telstra One XL] paulk_:
SMS Backup + will backup to your Gmail, can take a really long time though (IIRC 3,000 texts took half an hour). Never tried restoring from it.

Used SMS Backup & Restore for a while which I used to automatically backup all my texts to my SD card every night. Worked like a charm but took around 20 minutes to half an hour to restore 7,000 texts.

Got too lazy to keep everything backup up after switching to my HOXL and trying different ROMs so I only keep a small backup using TiBu nowadays

[EDIT] Got them mixed up! Haven't used SMS Backup + in over a year so I have no idea if performance has improved though
[AT&T, Rogers HTC One X, Telstra One XL] bimmernut318:
Sms backup+ backs up to gmail

Sent from a slithery smooth phone!
[AT&T, Rogers HTC One X, Telstra One XL] hyun18:
I use the stock HTC app and I can back up and restore from there quite easily...

And restoring don't overwrite your current data like it does with my back up pro.
[AT&T, Rogers HTC One X, Telstra One XL] bimmernut318:
Never used it, do you have to do it manually? SMS backup+ is automatic and when I restore it doesn't overwrite my data. I like the fact that it backs up automatically, one more thing I don't have to remember.
[AT&T, Rogers HTC One X, Telstra One XL] hyun18:
Ohhhh. Really? That's neat. Gon go and download that.

Edit: omfg, I went into the SMS back up + app. And it said I had nothing to back up.

Turns out, my messages got deleted, AGAIN.
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
And your messages getting deleted has absolutely nothing to do with the kernel.

Back on topic, sometime today I'm going to call on my trusty beta testers to try out v3.2beta4.
[AT&T, Rogers HTC One X, Telstra One XL] currydude:
Ready to test! Also, I'm just wondering, why are there so many frequency steps? Wouldn't it improve stability and responsiveness if we had fewer steps? (Total nob with this so its just coming out of my butt)
[AT&T, Rogers HTC One X, Telstra One XL] ziroxs:
I´m using 3.1 with Viper ROM 2.40 and got sometimes reboots during browsing or opening market place and so on. I raised up the global voltag +25 mV and now since 3 days no issues :good: Only for your information
[AT&T, Rogers HTC One X, Telstra One XL] hyun18:
Like someone mentioned, it is because of the reboots,which is caused by the kernel..

So it kinda is..lol. not complaining tho.
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Unless you're using the beta, your reboots are probably caused by something else. Thousands of downloads up to version 3.1 with very few issues reported.
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
You mean in the installer, or with frequency scaling?

For the installer, it just pics the maximum to use. Unless you pick one that is too much for your phone to handle, it doesn't make any difference in stability. I want to keep the options up to 2.0GHz in there bevcause a lot of people run at 2.0GHz.

For frequency scaling, I use the same frequency steps as stock, except the additional frequencies above 1.5GHz, if you selected them in aroma.
[AT&T, Rogers HTC One X, Telstra One XL] alx1880:
Hello, I've installed Elemental stock, so far so good, only downside is that camera doesn't work. How do I fix this issue?
[AT&T, Rogers HTC One X, Telstra One XL] pauley:
By clicking the "search this thread" button at the top... It's been answered so many times here.
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
I will answer this because I'm not sure if it's come up for elemental-stock (this is the stock kernel with OTG support). For elemental-stock, use the cam fix zip from the Beastmode thread.

Just so everyone knows the difference, this only applies to the stock kernel with OTG support. ElementalX-v3.1 installs the correct camera files automatically (and they're not the ones from Beastmode).
[AT&T, Rogers HTC One X, Telstra One XL] hapticxchaos:
hello all, getting a reboot at the end of EVERY call.....very stock cleanROM at 1.8ghz. will try reflashing at 1.7 to see what happens. please find my printk statement dump attatched also wondering how you've utilized aroma to flash a kernel for people on 2.20?? doesnt viper rom do this as well?? what is your secret lol??
[AT&T, Rogers HTC One X, Telstra One XL] alx1880:
Thanks a lot flar2, that solved the problem.
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
pm or email that to flar :D
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
Bump
[AT&T, Rogers HTC One X, Telstra One XL] slippers67:
The reboots are mostly from people trying to overclock too much while also running the voltages too low. So technically it's not the kernel's fault, other than the fact that it allows people to overclock and undervolt. :)

Seems like most people have no more issues after they stop undervolting so much, based on all the recent "success" posts.
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
This is a given.

The OP has always said to do a full wipe and clean install, lower max frequency or increase voltage before reporting problems.

It would be very helpful to me if people stuck to that.

So, if you have a problem:

1. factory reset

2. clean install of a stable ROM

3. reinstall kernel with max freq 1.5, S2W disabled, no GPU OC

4. bump your voltages up by 50mV with kernel tuner, venom tweaks, etc.

If you do this, you shouldn't have problems.
[AT&T, Rogers HTC One X, Telstra One XL] slippers67:
May I suggest you make the default voltage on the kernel 50 mV higher on the next release? :)
[AT&T, Rogers HTC One X, Telstra One XL] currydude:
Yes, I'm talking about the frequency scaling/steps, but yeah ... ignore what I said, I gave it more thought and reducing the number of frequencies avaliable for scaling will reduce stability.

The latest private beta is working a treat, have no problems at the moment (only been a frew hours though)
[AT&T, Rogers HTC One X, Telstra One XL] dave-:
I had v2.1 (1.5Ghz) going for ages with +25mV in Venom Tweaks. After upgrading to v3.1 the same voltage was highly unstable, causing a number of screen lockups. Currently at +75mV now to see if it stops the screen lockups and random reboots.

Will probably go back to v2.1 if it doesn't improve. Haven't changed anything else since either.
[AT&T, Rogers HTC One X, Telstra One XL] ECEXCURSION:
I agree. Regular voltage should be the default. Then if users want to undervolted they can select it in the installer - knowing that they are selecting something for which this phone was not designed. Just my opinion.

Sent from my HTC One XL
[AT&T, Rogers HTC One X, Telstra One XL] harry655:
:( finally decided to revert to stock kernel. Too many screen lockups & reboots. Same on both 1.5 & 1.7 GHz with between 0 to +50 mv. On a clean install of viper Rom.

Hopefully a newer version might be better for me.

Performance was nice and same with battery, but...

Sent from my ViperXL 2.4.0
[AT&T, Rogers HTC One X, Telstra One XL] joewong1991:
Sweet new kernel :D

skydragon team
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Alright, it seems a small number of people can't run 3.1 without problems. I'm going to pm a few of you later on to test something and hopefully we can get everyone stable.

In the meantime, anyone with stability problems on 3.0 or higher can use version 2.1.

Also: the latest beta already defaults +50 on voltage, but the option to undervolt is there.
[AT&T, Rogers HTC One X, Telstra One XL] Red5:
I moved back to 2.1 and haven't had any issues. I think ill stay here for the time being. :D
[AT&T, Rogers HTC One X, Telstra One XL] flar2:
Well I know things look dire from the last few pages, but really, there are over a thousand downloads of v3.1, and fewer than 10 people are having problems. I've never had a single reboot or problem of any kind using v3.1 or beta versions of 3.2.

Anyways, I wasn't expecting this many people to start using the kernel and I let the thread get sidetracked. I looked through some other custom kernel threads on here and even the legendary kernel devs get tons of people reporting problems. With phones there are so many variables that come into play it's impossible for everyone to be problem-free.

So, I want to make clear:

1. Before you post problems here, be sure you have read the OP in great detail and that your problems are not caused by the settings you chose or something else specific to your setup.

2. I provide this free of charge to enhance your experience on this phone. If it doesn't work for some reason, don't complain. However, I do welcome constructive posts with details so we can work together to improve the kernel for everyone.
[AT&T, Rogers HTC One X, Telstra One XL] dave-:
Ah the problem of free, people still expect 24/7 support!

Don't bite the hand that feeds you I say. Doing a good job, along with all the Dev's here. :good:
[AT&T, Rogers HTC One X, Telstra One XL] Genetic517:
this. lets not run flar out of town, k? id like to continue to recieve updates with this kernel. :good:
[AT&T, Rogers HTC One X, Telstra One XL] gentzleon:
This is a reason alot of good devs leave....time is volunteered, and ALL the time invested in roms, kernels and themes is great and people complain as if they paid for a service....come on...lets be greatfull and support the devs...
[AT&T, Rogers HTC One X, Telstra One XL] ECEXCURSION:
Is that a bandwagon I see? Let me jump right on..

Removed
[AT&T, Rogers HTC One X, Telstra One XL] paulk_:
We just have to remember that the vast majority of people only start posting when they encounter problems, i.e. there are a handful of people complaining but probably hundreds of lurkers who don't face the same problems.

This thread has over 41,000 views in 64 pages!
[AT&T, Rogers HTC One X, Telstra One XL] cookie29:
Beta 3.2.1 is working flawlessly for me while the previous versions always had a

Little flickering from time to time. Goes to show you that every phone is a little different.

Thanks for all your work flar. Your kernel with clean rom is as smooth and stable as I have ever had a

Phone and substantially better than stock.
[AT&T, Rogers HTC One X, Telstra One XL] mgfjd:
I agree some people should clearly look into the root causes before reporting a problem. Sometimes you have to install a fresh room before reporting a problem.

I am using the latest beta with stock voltage, 1.5ghz, no gpu overclock, no zram, no swipe to wake. It is stable and working great for the last 24hrs.
[AT&T, Rogers HTC One X, Telstra One XL] hyun18:
Yes, because problems need to be known and solved. Thats not complaining lol, unless its an error in the customers part .Otherwise ,that should help the dev better the product.

Unless he/she's willing to ignore the minority that has problems and expect 100% good feedbacks

Think of it more as a problem report rather than complaining.

Unless of course they are actually complaining without even a cause for solving the problem, and just straight out complaining.

Also ,if a dev actually loves what he does, he won't let the minority of negative stuffs get to him and stop him from doing what he wants /like.

They'd just be letting those 'minor negativities ' defeat him.

Anyways,I'm not getting the problems now..

I switched.

Seems like high OVs don't work smoothly.