yashsingh1/xdaforums huggingface dataset:
[HTC One X+] ace_viknesh:
Hey Beladus, I just wanna ask, is it possible to overclock the processor since its and NVIDIA CPU?
[HTC One X+] reaper90:
Why would you do that? I only use the phone in Power saver mode (1.3GHz) and it's more than fast enough. also on the other side, it gets very hot when there's heavy load on all cores and GPU (for example gaming) even on 1.3 GHz. So OC is just unnecessary, may damage your phone and also helps draining your battery faster...
[HTC One X+] ace_viknesh:
I asked cos I want to know up to what limit the processor can reach. Its fast yes, but i'm sure it can get even faster. Heat and battery life is an issue, agreed.
[HTC One X+] :
Yeah, I've had a look at the OC code, and it's a lot more complex than the nexus s, so at this point I don't really understand it. I think I would if I was confident I could do it correctly, but only as an experiment. The device just gets too hot even at 1.3GHz.
[HTC One X+] ace_viknesh:
Do you have a copy of the OC code, and if you have could I have a look at it? Thanks!
[HTC One X+] :
morfic has done some work on it for tegra (nexus 7 though) here: https://bitbucket.org/morfic/seven/commits/all

e.g https://bitbucket.org/morfic/seven/commits/6f9d8d4c672b6724d28464323e59fdeba3c55ebf
[HTC One X+] :
v3.4 is here: http://d-h.st/BH2

CoreManager.apk is here: http://d-h.st/R5l

-after rebooting, remember to open/save+exit to restore your preferences

-Please grant super-user permissions

Version 3.4 Notes

Firstly, Core Manager has been tidied up a bit, and now has the GPU coupling toggle.

In the kernel, the touch boost frequency has been brought down to 1.15GHz with no apparent impact on GUI smoothness, and will nudge the power-saving up a little.

Also, with respect to saving power, I accidentally seem to have fixed some kind of config mistake that I didn't realise was in there. I got my kernel config from nik3r, and assumed it was correct. However, while building the AT&T test builds, I investigated the default config, and found some differences. So I've merged these differences into my config, and it certainly seems to me that the heat coming out of the back seems substantially reduced! I've played asphalt 7 continuously for about an hour, and it feels warm, but not burning! Yay! :D

EDIT: Also forgot to mention, the S2W [slide to wake] code has been updated (thanks maxwen) and the max frequency has been allowed up to 1.7GHz (frequencies between the ideal 1.15GHz and 1.7GHz are skipped to avoid pointless reclocking)

My kernel config

-Slide to Wake [S2W]

-Hotplugging with a user defined limit (using the above app)

-The low power core is prevented when awake, and the high-power quad-core is forbidden when the screen is off. This is to ensure performance when the screen is on, and power-saving when it is off (+ there is a two core minimum when device is awake)

-smartmax governor by maxwen

-added fast-charge to kernel (thanks maxwen)

-added BLX (thanks ezekeel)

-Available IO Schedulers: BFQ, CFQ (as default), Deadline, NOOP, SIO, ROW, and V(R).

-Miscelaneous tweaks: ticket based rwsem algorithm; Google's tcp proportion rate reduction algorithm; cifs; zcache with latest LZO; SLUB
[HTC One X+] reaper90:
Thanks, sounds great, hope this applies to other Games as well! Will try Iron Man 3 to see if it still burns my phone^^

edit: ok just tried and it still gets very hot, but at least not that hot as before. CPU-Z reported a battery temperature (i don't have any app installed read cpu temperature) of 49°C after playing, with kernel 3.3 it was almost 60°C.
[HTC One X+] pradeepvizz:
Thanks [MENTION=4128576]bedalus[/MENTION].. are the tweaks to the IO parameters from the test version inside too?
[HTC One X+] :
Yeah, but they're so trivial I didn't think to mention them :)
[HTC One X+] :
Ah, that's good. That's a huge improvement!
[HTC One X+] pradeepvizz:
the only thing which may require improvement is the IO on my phone .. all others conquered by your kernel.
[HTC One X+] :
What's up with the IO?
[HTC One X+] reaper90:
Maybe i have to add that i limited my phone to 2x 1.3GHz and decoupled GPU. Smoothness seems the same as with 4 cores, so i think it is limited by Tegra 3 GPU. Maybe it could run even cooler with lower CPU frequency.

But I'm happy with how it runs now (temperature and smoothness).

I'm now waiting for more kernel customization features :P (no hurry though)

Great work on this one!
[HTC One X+] pradeepvizz:
i may be wrong... but i think my phone struggles when more than 1 program starts accessing data - say downloading an app update in the background and then opening a different app / changing to a different app. so i think IO is the problem.
[HTC One X+] :
Is it the same problem for all IO schedulers?
[HTC One X+] Notechis:
Flashed it and everything seems to be smooth.

Rgds Mr. Floppy
[HTC One X+] pradeepvizz:
i have tried with noop and cfq - both struggle when downloading on background in mobile data. i use the phone most of the time in mobile data, not sure if it happens at WiFi back home.
[HTC One X+] :
If it's an IO issue, it won't matter if you're on wifi or 3G. You could try BFQ, it is probably the best choice if you've got multiple activities making demands on storage.
[HTC One X+] towelboy:
Will test it out after I get home! Good stuff bedalus
[HTC One X+] snakebiteex:
3.4 is super awesome!

everything is butter smooth, the way it was supposed to be from the beginning, *cough* HTC *cough*

anyways, keep up the super awesome work!

----------------

edit:

for some reason charging is super slow with 3.4.. even with fastcharge on and an 2.1 amp charger (i know it wont charge at 2 amps, just saying the power adapter has plenty of juice)..
[HTC One X+] Rapscallion16:
It's saying File Not Found for me. Is that the right link?
[HTC One X+] DannyAb:
very very Slow charging (2% in 30minutes slow) . But buttery smooth, good job Bed.

Notice the difference between elite kernel(charging) in the first phase, then hxore v3.4 in the second :/
[HTC One X+] haighpaul:
Also having serious charging issues on 3.4. Battery dropped to zero while plugged in to computer USB during a long HTC sync! Will try to recharge from mains adapter.
[HTC One X+] pradeepvizz:
no charging problems here
[HTC One X+] reaper90:
USB charging (from computer) does not deliver as much current as DC charging. The phone can easily drain more current than your USB port provides when SoC is busy and display is on. Also battery level drops very fast when under 15% or sometimes even shuts down before reaching 0%. I don't know if Bedalus changed anything regarding this, but i don't think so, DC charging works fine for me.
[HTC One X+] Notechis:
No charging issues here

Rgds Mr. Floppy
[HTC One X+] :
No charging issues for me either, but I'll double check my recent changes
[HTC One X+] laurab4369:
In first my phone is very hot when i use it in charge: cpu 80 c° and my battery 55 c°.

In second the charge is very very slow with ac adapter.

I haven't problem in screen of.
[HTC One X+] ace_viknesh:
For those who are having battery problems, did you re-flash the kernel to see if it solved the problem? Do reply if you have done so and if the problem still exists.

Edit: [MENTION=4128576]bedalus[/MENTION] could you check if the kernel codes for the battery are correct, cos too many users are reporting the problem. Because when you fixed the heat issue, you could have also changed codes for the battery. I'm no expert like you but its possible right?
[HTC One X+] sffmandrake:
Hi,

Same here ;)
[HTC One X+] yourguitarist:
Gonna try flashing the new test kernel after dinner. Will report back later!

Sent from my HTC One X+
[HTC One X+] :
Yeah, I'm pretty sure I modified some battery code, but I can't remember why. I'll take a look after work
[HTC One X+] reaper90:
Charging speed and temperature were normal, but somthing was wrong with BLX. I used to set the maximum charge to 95% lately, yesterday before going to bed i set it to 100%, but the phone still was on 95% this morning. Now after rebooting the phone and again applying 100% as charging maximum, it works...
[HTC One X+] :
IIRC the blx code might not work until you unplug and plug in again
[HTC One X+] reaper90:
I also did this yesterday, i changed limit to maximum and when i saw it did not work i unplugged and plugged the phone in again.But after another 30min, not a single % increase in battery... But i will try again later, just to be sure.

edit: just tested again, when limited to 95% and also charged to this value, i have set to 100% but it won't charge again. I tried:

set value -> unplug -> plug in again

and also

unplug -> set value -> plug in again

in both cases it did not charge further than 95%... i know this isn't the battery issue, some people are having, but i noticed that this does not work flawlessly...
[HTC One X+] ace_viknesh:
I think for the mean time for those who are having problems, roll back to v3.3 and let Bedalus find out the problem.
[HTC One X+] pradeepvizz:
does someone have a issue with performance or is it only me? i have a feeling that the previous version 3.3 showed better performance.

[MENTION=4128576]bedalus[/MENTION] what was the decision made in context to no of cores usage vs frequency? i am seeing that the fourth core does not get activated easily while the frequency scales up pretty fast.

---------- Post added at 02:41 PM ---------- Previous post was at 02:27 PM ----------

tried BFQ with the new kernel and i think BFQ performs bad compared to CFQ/Noop so back to Noop at the moment.

Does download need cpu cycles? i don't know, i was under the impression that it probably does not need much of CPU for it and when i tested it it was confusing me :(

i turned off the screen timeout, kept the phone on the floor started downloading asphalt 7 to test IO and noticed that the frequency was actually jumping heavily from 320MHz to 1.3 GHz..
[HTC One X+] Vixa:
Today i had 2 random reboots and something strange with the back button it locks the screen sometimes when i press it , and also i have lag like before v3.3 was perfect. Ill reflash the kernel as soon as i can to see if it solves the problems...
[HTC One X+] :
Obviously I've done something wrong. I'll have to issue a v3.4b asap when I've worked out what went wrong!
[HTC One X+] pradeepvizz:
Thanks a lot!
[HTC One X+] adamkx7xdesire:
Unfortunately I've SOD

here is logcat

back to 3.3 ;(
[HTC One X+] lbaquerizo:
Are you using the original charger :confused: because I have noticed with generic chargers take a long time and with the original (HTC short really short cable) it charges OK

HTC one X+ InsertCoin 4.0.0
[HTC One X+] :
I did reduce the default ideal frequency. Is it that noticeable?

Yep, smartass scales up to the ideal freq immediately, then down slowly. Or are you talking about time spent at 1.7GHz

It's supposed to be better for desktop users compared to cfq. But trust your own observations. It may not translate to our device.

Yeah, it's normal for the frequency to jump around. I'm still at a loss on how to demonstrate what IO scheduler would work best. I'll have to do some more testing soon
[HTC One X+] :
You're not alone, 3.4 seems to be buggy! I should have done more testing. :p

Is anyone else having any issues with the back button?
[HTC One X+] DannyAb:
Yeah man. Original Charger, you can notice how slow it was charging in the picture i posted..
[HTC One X+] :
It might work if you unplug and let it discharge one percent then plug in again. I can't remember exactly, but when I built it in I definitely remember there was a quirk to workaround
[HTC One X+] :
That sounds very bad. This is on v3.3 or 3.4?
[HTC One X+] reaper90:
It's not a big deal, I don't change the value that often, just wanted mention in case it's a bug or so.
[HTC One X+] Notechis:
You see how different the kernels work for each user.

For me the last 2 or 4 releases run like hell , with less drain. No reboots , lags or charging issues.

Scaling e.g. is perfect... For me there is less difference between noob / bfq / cfq , all are pretty good ;)
[HTC One X+] pradeepvizz:
i observed once that the phone did not turn on for a few seconds with swipe to on/power button too.

My phone has been really strange from day 1 on custom kernels - Elite kernel lags like mad on my phone - To me the the only versions i have noticed smoothness are with the version 3.3 / 3.0 (the last performance version without any battery saving) During the pre 3.0 era when others used to be happy with 2 cores, i thought there is a room for improvement and i think 3.3 nailed it.

i may most probably be having a very bad app.

i would not say that the last change of reducing the default ideal frequency is bad - because it shows on the battery for sure. Can this default ideal frequency be changed using a script?

its the smartass scaling i was talking about - it is really good - i noticed 3 cores were on 1.7 GHz and the fourth one was inactive. i think this is the expected behavior and it is done so considering battery usage.

yupp, thats why i am sticking to cfq/noop

yeah right - too many scenarios and probably there is no one size fits all IO scheduler

Thanks a lot for your efforts, we will wait for 3.4b
[HTC One X+] laurab4369:
Version 3.4
[HTC One X+] reaper90:
Bedalus set a hotplugging maximum of 3 cores on boot, you have to change the number in core manager after every boot if you want something else.
[HTC One X+] Notechis:
That is pretty amazing

Rgds Mr. Floppy
[HTC One X+] lbaquerizo:
Then my advice is rollback to previous version. I am on 3.3 and don't feel that it's necessary to update yet

HTC one X+

ROM ELEGANCIA 6.1.0
[HTC One X+] :
http://xdaforums.com/showthread.php?p=42862222#post42862222

I've updated (and hopefully fixed) v3.4

I've hopefully solved the charging issues, and I've decided performance was better in v3.3 so the frequency is bumped back to 1.3GHz again
[HTC One X+] towelboy:
[MENTION=4128576]bedalus[/MENTION] can you reupload the file? It seems to not work now that I have free time http://d-h.st/wyHnew
[HTC One X+] pradeepvizz:
That is pretty quick man! i was under the impression that kernel development takes long! you proved it wrong
[HTC One X+] :
I think I pulled it because wifi was confirmed still not working. I'm sure I'll crack it soon!
[HTC One X+] :
here's a new test version: http://d-h.st/gUW

I'm trying a different approach to powersaving. What I'm interested in is whether this one is spending less time at the maximum frequency, but still feels smooth?
[HTC One X+] towelboy:
Okay! May the force be with you
[HTC One X+] yourguitarist:
New test version didn't work that well for me. Im gonna try again after my phone charges a bit. Will report back asap

Edit: Yep, wasn't working for me. :(
[HTC One X+] :
I'm not sure what you mean?
[HTC One X+] yourguitarist:
No wifi on the new ATT test kernel and no vibration

unless that wasn't for att.... ha
[HTC One X+] pradeepvizz:
I think the test version was for international.. guessing you have tried that on your ATT device.
[HTC One X+] :
Yeah that was international!
[HTC One X+] pradeepvizz:
i dont think he would have flashed it ... well in that case the phone wont boot right? or probably he just quoted a wrong post

edit:removed
[HTC One X+] :
There's probably a better place to post about that
[HTC One X+] pradeepvizz:
Sure there is, btw the in latest test version should I keep the cpu power save on or off?
[HTC One X+] :
Keep it off. There's no harm in allowing the higher frequencies. The screen eats the most power, so if you are waiting longer for something to happen, power is being wasted. Might as well make things happen as quick as possible!
[HTC One X+] pradeepvizz:
hmm that's perfectly logical. i have preferred the same for the sake of performance. i have heard it 1000 times that screen eats most of the power - but have a confusion on that.

When i had my HOX, i had run the battery test many times and it ended up using 4 to 5% battery. The test app actually keeps the screen on for one hour and the prerequisites are airplane mode and full brightness (or auto).

so if its just 5 % per hour why worry about it and it does not match the theory of screen eating the battery.

i am definitely missing something :)
[HTC One X+] xdacalvien:
Hotplugging limit:3

GPU Coupling: ON

IO: CFQ

Playing MKV movie heat up. Battery temperature 56.1 CB

It's that normal?
[HTC One X+] :
Dunno. It's not something I do. Have you tried doing that on the stock kernel?
[HTC One X+] reaper90:
Short feedback on latest test version (international):

Very fast and smooth, though i can't feel any difference to 3.3/3.4, is had power saver enabled all the time.

Battery seems good, took it from charger at 6am flashed new kernel and heavily used it in university (only boring lectures today :D) until now and i still have 35% left. Heavy usage in this case means downloading some big files in the background, a lot of browsing websites and texting and some Youtube videos, connected to WiFi most of the time and bad phone signal strenght in university buildings.

---------- Post added at 02:27 PM ---------- Previous post was at 02:19 PM ----------

It's quite some time ago that i played MKV videos on my phone, don't know if i had stock kernel or nik3r's kernel installed, but i also noticed the phone gets pretty hot. I tried some 1080p mp4 movie (12Mbit/s, h.264) shortly and it played fine while SoC was kind of bored, thus phone just a little warm.

Also mp4 is listed as supported video format by HTC and mkv is not (Dunno if this should make a difference)
[HTC One X+] Notechis:
That is a test and not real life usage.

Try to read a book on your hox with less CPU usage and only scroll a bit and change the site and you will find out, the drain of battery compared to screen ;)
[HTC One X+] pradeepvizz:
true that its a test, I will give that a try to understand the behavior.

i was only talking about battery used by the screen only while i think in real life usage the digitizer (touch) is also used which probably uses the power.
[HTC One X+] :
I think the battery reading is also at fault. It can't measure very accurately, so algorithms are at work to help predict the battery level based on usage, estimated drain rate, estimated current charge level, estimated minimum charge level...

I think if you turn your screen brightness on full and use some app to keep the device awake, maybe you get 5 hours. If you actually use the phone, maybe 4.

I did a tonne of battery measurements for the nexus s (although amoled) https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdEY4T3dXWVFDWk9lREdJNGFfU2NwRlE (using an ammeter to measure current)

and came to a bunch of conclusions (featured on the portal :p): http://www.xda-developers.com/andro...ry-study-brings-about-surprising-conclusions/ (although my initial conclusions about deep idle later proved to be wrong)

The original thread is still worth a read: http://xdaforums.com/showthread.php?t=1478406
[HTC One X+] pradeepvizz:
OMG this is a research by itself.. you should be hired by the companies - you seem to have some great capabilities!

thanks a lot for your time.

---------- Post added at 06:32 PM ---------- Previous post was at 06:28 PM ----------

i had noticed something like this today on my phone - went from 20% to 8% when it came alive after flashing kernel - that's just in two minutes!

now i probably know
[HTC One X+] xdacalvien:
I'll try tomorrow. But I remember last time not reached 56 temperature.
[HTC One X+] :
new AT&T test kernel: http://d-h.st/Ly5

I've taken a different approach this time. I've gone back to the stock kernel source. So it will probably feel like crap. But does wifi work????? :p
[HTC One X+] Rapscallion16:
Everything is up and running on this version. WiFi works, screen and capacitive buttons respond nicely. It's pretty much the stock kernel if you didn't already change anything in it.
[HTC One X+] Wnsly:
Wow! you shouldn't flash anything when your battery is that low.. make sure it's at least 50%

I would not take the risk. Love my HOX+ too much :)

Sent from my HTC One X+
[HTC One X+] :
The 8% reading was probably just the phone estimating badly. It was probably more than that, but yeah, make sure you've got some charge to spare in case things go wrong
[HTC One X+] :
Ah, finally. Okay. That was the stock kernel, pretty much. Now I've added all the tweaks that are in the international version to it...

So, for any AT&T users: http://d-h.st/7db

Please check that everything works as it should. You should be able to use the Core Manager app for the various settings too.
[HTC One X+] bigdave79:
Is this kernel based on the newest AT&T update from a couple of months ago?
[HTC One X+] pradeepvizz:
Here is my cpu frequency stats from the latest test kernel with cpu power save off. This is from 100 to 20 percent in twelve hours with mobile data on 80 percent of the time and the rest in wifi. No lags perfectly smooth. I would try with power save on tomorrow. View attachment 2069442
[HTC One X+] pradeepvizz:
Thanks never thought about that
[HTC One X+] :
I saw one download for AT&T at htcdev, if you've got a newer link from somewhere can you share it?
[HTC One X+] pradeepvizz:
So i guess 3.4 b is now back to form and stable?
[HTC One X+] :
It seems like it. No complaints so far!
[HTC One X+] Wnsly:
3.4b works like a charm. You did a good job! :thumbup:

S2w responds good even after long deepsleep and Real racing 3 runs smooth without getting extremely hot.

I had some lag while playing music but I don't think it is kernel related. It happens with stock too
[HTC One X+] markwoo:
AT&T kernel best one yet thank you
[HTC One X+] :
Time to make an AT&T thread then
[HTC One X+] Vixa:
In 3.4b everything is good but i still have that strange bug with the back button locking the screen sometimes :D
[HTC One X+] Notechis:
Maybe Rom related.

Rgds Mr. Floppy
[HTC One X+] aliko007:
Me 2 :(
[HTC One X+] Vixa:
I'm on viper 1.0.9 but i think it's not rom related...
[HTC One X+] towelboy:
You're the man!
[HTC One X+] anko184:
Exactly.. I wasn't very sure what hot plugging exactly did, that's why i didn't mention it and tried to explain in it without using any terms:silly:
[HTC One X+] nealkoy:
Re: [KERNEL] hXORe for sense [INTERNATIONAL]

In exchange for no hotplug, Bedalus gave the users control on how many cores to activate. In your case all cores are online while screen is on so you can try to set the kernel to activate 1,2 or 3 cores only as you would have it. Results will vary based on user preference though...

You may wish to try activating 2 cores only and see if performance and battery loss is acceptable to you. ;)

Sent from my Nexus 7
[HTC One X+] anko184:
Yes i know that but i still think it's better to let tegra 3 decide how many cores to enable depending on system load. Why should i have to bother for something that tegra can handle by itself? Also what if i enable 2 cores and then want to play some demanding game? I 'll have to enable 4 cores for the game and then disable the 2 of them when i finish playing, right? Well that's not accepted for me and their is no reason i can think of for forcing user's to act like that..

And because i don't want anyone to think that i'm ungraceful for OP's work i have to say that i really enjoyed testing the kernel but i totally disagree with this decision.. With 2 cores enabled i get excellent battery life but i also have some lags that hot plug would have prevent ;)