Related
first and foremost, if I've posted in the wrong place, I ask that a MOD kindly move it for me please...and you have my sincerest apology now, if its in the right place then disregard these words. Notice I said MOD, i don't need a bunch of people posting all the known comments like "this is in the wrong place" .."somebody ban this waste of space"..."learn how to read the forum rules"..."I'm tired of people posting here"...etc, etc. All that is not necessary, when a MOD can simply come right along and move it. If you insist on being a MOD "wanna be"..or a "tattle tell" (some refer to as snitch) Then just PM the CEO of XDA that Klyentel posted in the wrong place, who cares...as long as it gets corrected
EDITDONT WORRY ABOUT YOUR SWAP PARTITIONS,COMPCACHE,3RD PARTY SWAP APPS, AND YOUR FANCY LITTLE USER CONFIG'S.....THEY WON'T WORK ON THIS ROM--AND YOU DON'T NEED EM-
I highly recommend anyone who hasn't played with the overclocking hack recently brought to everyones attention, credit and thanks to Eugene, or anyone who has tried it and didn't like it, to make their first time experience or redeem their failed experience with KnK's version of the super-d 1.8 rom, seriously, it will shut down any doubts in mind that the hack makes a difference, trust me.
(Some of you may or may have not already tried this, if so feel free to comment your experience, as it will give others a better idea what to expect, similar settings don't count, you can sit here & argue this forum a thousand pages long about how you already tried this and that...how you turned swap on and off got the same results....benchmarked this, benchmarked that....well Daproy said this and Shadowich said that....[those are just random names of high posting users by the way, I'm not pointing anyone out, by all means those are two well respected, knowledgeable senior members for those who don't know] but I will not engage into a paragraph after paragraph argument with you, nothing stands as a valid opinion until you flashed this rom, not your own tweaked version, with your own tweaked settings, THIS ROM>FOLLOWING THESE STEPS are the only valid comments that will be made redeemable to any type of response from me, period. If another random member wants to post back and forth with ya than fine, but I will continue to ignore irrelevance)
And it would be greatly appreciated if off topic, sarcastic humor, LOL buddy chat, and pointless picture posting be taken over to a PM for private conversation...as it has nothing to do with this thread
BY THE WAY THIS IS NOT MY ROM, I AM NOT A DEV. I'M A HAPPY SUPER D USER WHO STUMBLED ACROSS A PIECE OF GREATNESS AND DECIDED TO SHARE. IF YOU HAVE PROBLEMS, ISSUES, CONCERNS, OR QUESTIONS...I SUGGEST YOU CONTACT THE PERSON RESPONSIBLE FOR THIS TWEAKED VERSION OF SUPER D, HERE IS HIS INFO-- [email protected], XDA MEMBER NAME-KNK, TWITTER-DIGITALKNK
THANK YOU
Backup what ya got, Do a clean full wipe, download this zip:
http://www.megaupload.com/?d=3J6RP7GN
extract it to ya pc, grab the setcpu.txt file and the setcpu apk- he forgot to put it back in the rom, so you will need this unless you have a copy of the apk on your sdcard already, place it on the root of ya sd,
transfer the KnK's custom Super D rom to your sdcard,
boot into recovery and flash,
after it fully loads, don't do anything, reboot again,
when it loads back up, go to your setcpu app and choose Custom settings
tweak your high/min the way ya want, I recommend 628/245
after setting it, reboot again,
when it loads back up, you will be completely amazed, I promise you.
Whats special about his version? Theres no swap/compcache, a few system apps are removed (so if you like the stock email, calculator, IM and all that, you'll have to port it back yourself)
Maps Nexus Multi-Touch enhancement already applied, cpu hack boot img already compiled and packaged
and probably more but IDK, maybe he tweaked the kernel or something, needless to say this is still Super D-1.8, and you all know how great that is anyway, credit due to the Dev-Ben Buchacher
but truth be told this is the fastest I've seen guys, really, It defeats the purpose of swap and compcache
just try it on ya spare time, and if ya follow the steps above I promise you wont be disappointed
I welcome all your opinions, negative, positive, flame me, blame me, hate me and be angry, I don't care....this is worth my time to post for others to try because my experience was that good, call it crazy, "placebo", imaginative, whatever....bet ya can't call me a lie flash and you'll see why.
Downloading this now can't wait to try it out
Thanks, I'll try this out too
The different fonts and colors hurt my eyes. I'll download it though...
And someone had to say something negative:
"The rom cooker app isn't even out yet and it's already happening."
That should rid the negative for a few posts
Wooo downloading now. Thank you for sharing.
i feel u on that some ppl just plain out rude lol!!! applying this now i will update as i go!!!! good look on this !!!
JAguirre1231 said:
The different fonts and colors hurt my eyes. I'll download it though...
And someone had to say something negative:
"The rom cooker app isn't even out yet and it's already happening."
That should rid the negative for a few posts
Click to expand...
Click to collapse
LOL, agreed, but I'm not and will not be one of the "Rom Cooking" posters, this is someone elses.
fail...lol
please read eugenes official statement on the overclock not actually working. Any speed increase you see is fictional.
http://forum.xda-developers.com/showpost.php?p=5584571&postcount=164
d33dvb said:
fail...lol
please read eugenes official statement on the overclock not actually working. Any speed increase you see is fictional.
http://forum.xda-developers.com/showpost.php?p=5584571&postcount=164
Click to expand...
Click to collapse
Please flash this rom, and follow these steps, then post your fiction theory along with its link again. that is my one and only reply to you. Thanks.
Whether or not the overclocking really works, this is pretty much the ROM combo I've been after for awhile
What are the required partitions and SPL?
I installed setCPU, but I'm not getting the option to increase the clockspeed beyond 528 ...
Where exactly do I copy the setcpu.txt file to get the additional clock rates?
Do I choose a different hardware platform (g1, magic, nexus, etc.) for the setCPU app?
chilln73 said:
I installed setCPU, but I'm not getting the option to increase the clockspeed beyond 528 ...
Where exactly do I copy the setcpu.txt file to get the additional clock rates?
Do I choose a different hardware platform (g1, magic, nexus, etc.) for the setCPU app?
Click to expand...
Click to collapse
put the file on the root of your sd---meaning just drop it on the card, not inside a folder
you will not choose a handset- such as g1, magic,nexus,etc...
you will choose the very last option which is Custom settings
please do not forget two reboots are required!! Follow all steps carefully.
I spent some time with the ROM and I wasn't noticing a huge difference in performance... Went back to Super D.
Johnny5401 said:
What are the required partitions and SPL?
Click to expand...
Click to collapse
Same as the original rom (Ben) stated...please see the main thread labeled (rom) SuperD1.8-"Fried Donut" for any change logs or special install requirements.
CaptainShanks said:
I spent some time with the ROM and I wasn't noticing a huge difference in performance... Went back to Super D.
Click to expand...
Click to collapse
please do tell in detail....did you reboot after first flash? and again after setting overclock? How long did you play? Were there any decreases in performance? Such as lags, freeze ups? what did you clock? high/min?
People, dont get carried away, you cant just flash, boot up, spin clock speed up to highest your heart feels, then turn off and nandroid back to your old set-up, you have to do the steps above exactly as stated, and if you did indeed do so...i want to know more about what your experience and clock tweaks were, because one minor adjustment can make a difference.
CaptainShanks said:
I spent some time with the ROM and I wasn't noticing a huge difference in performance... Went back to Super D.
Click to expand...
Click to collapse
Couldn't really tell either. I replaced Home++ with Advanced Launcher to make a better judgement, but as far as I can tell it's just the typical Super D speeds... which is of course, amazingly fast.
Tried at your rec setting of 628.
bigdbag said:
Couldn't really tell either. I replaced Home++ with Advanced Launcher to make a better judgement, but as far as I can tell it's just the typical Super D speeds... which is of course, amazingly fast.
Tried at your rec setting of 628.
Click to expand...
Click to collapse
cool,
alright thanks for the input!
Here's an idea, if you're up for it...wipe and go back to the stock super D 1.8 with no cpu hack, and see if the speed feels the same....it'll be fast, cus like you said super d is fast, but I can almost guarantee it wont be the same
Umm wow ... I didn't think Klyentel would have made a post about this hahaha. In any case thanks .
I don't run it at 780 in fact My max is 580mhz since overclocking it to anything above that is a battery eater and doesn't jump much in performance.
Be sure to use profiles on setcpu that is the most useful feature on there.
I have these settings.
Charging
- 780max
- 384min
Sleep/Standby
- 245max
- 128min
Power < 90%
- 580max
- 245min
Battery Temp > 37.9
- 245max
- 245min
I have the profile set @ 780 when charging because I have the failsafe enabled which drops the cpu down if the battery is to heat up. So that's the only time I have it enabled at 780mhz.
Well I hope you enjoy the rom I didn't do much but just tweak it a bit like Klyentel said Ben did most of the work with SuperD which is an awesome rom all I did was tweak it to my liking
For those not seeing a difference you won't really at standard tasks, I have setcpu to on demand on the normal Super D 1.8 and set at 384 or 528 max you see no real difference... that is until you start multi tasking. Having 10 browsers windows open, snes emulator, last fm and documents to go the speed increase is greatly noticed as its at its heaviest usage that the cpu finally decideds to crank up due to workload.
If your gonna test then do so properly rather than a quick look and deciding nothing has changed. Gonna flash this myself later and do some proper more constructive testing and report back.
Hi All Mighty Developers!
You all work hard to satisfy our needs on ROM and App developent but from our point of view (end user) there is no objective and comparable results of developed ROMs for HTC devices.
My idea is to develop a software that is capable of measuring device:
- MTBF (Mean time between failures) or between soft/hard reset
- Average and low high levels of RAM usage
- Average CPU levels, Net usage, etc.
- Device Manufacturer, Type,
- Device OS, ROM, ROM version
This is a small footprint of data which can be uploaded to a site. At server side data could be analysed and integrated into a structural view to hellp users decide to install ROM or not.
ROM developers should be allowed to register their ROM and decide weather to include the client software or not. They can maintain their ROM versions and follow its data.
Regards,
cina.
you are right. these is no objective way to measure performance of roms. the systematic benchmarks are totally usless
i think its much more useful to develop a simple application that does a messure of how long it takes to complete a set of well known tasks.
the application would for example run a script to visually start mail appication then run file explorer then create a tcalender item then change the time then copy a file to the SD card and read from it. the output would be the time it takes to do this. this should be extremely useful for rom cookers to really help them optimise their roms
anybody willing to give this a shot. it shouldnt be that complicated
That is a one shot execution of measuring performance of a software which is influenced by many factors - currently running applications, memory usage, etc.
If execution of a software needs to be measured (objectively and comparable) I think it needs to run several times - so a monitoring application should be developed which records timing of every execution and then averages results.
MTBF and the other parameters I've mentioned in post #1 also needs a monitoring method to develop. Small footprint as a service separated from the GUI which is only running during configuration, uploading result, etc.
I have a lot of ideas with this. But I'm not a PPC developer. I have some experience in desktop application development so I might help some desperate programmers with a basic specification and design if needed.
Idea is absolutely useless, imho.
Too many variables.
I am using soft i've added to rom to FEEL difference between roms, checking:
- overall speed in real life conditions,
- doc file reading test(ebook reader and word),
- emulators test(cpu and gfx speed test),
- overall GUI speed,
- cam performance differencies,
- vid playback differencies,
- battery behaviour in similar conditions,
- mem drain after launching/using exactly same set of soft(interesting - mem drain is always related to phone subsystem),
- some synthetic tests related to gapi, gdi etc(BUT NEVER SPB bench, that program is ridiculous!),
- filetypes read check(to test associations/codecs).
And you know what..i haven't had single wm crash, batt drain or weak performance(cpu,batt) for 4 years, always used best base available(funny thing is TO FIND such base...many builds are needed..), tweaked to the max, these tests always worked for me, all weak/problematic builds ALWAYS showed potential problems/weaknesses after such test set.
First thing is to know your device, feel it(let's say).
I think that ONE program to measure these:
MTBF (Mean time between failures) or between soft/hard reset
- Average and low high levels of RAM usage
- Average CPU levels, Net usage, etc.
- Device Manufacturer, Type,
- Device OS, ROM, ROM version
Click to expand...
Click to collapse
is just not good idea - vide spb benchmark - results ARE NOT reliable at all(to be honest - that soft is BULL****).
I assume it is just because it is ONE program(and it serves salary, not REAL benching), such thing has nothing to reallife usage schema.
sry for my 2 cents.
upd:
MTBF (Mean time between failures) or between soft/hard reset
Click to expand...
Click to collapse
this is seriously ridiculous - HOW can one test something like that, LOL?
pupakota said:
this is seriously ridiculous - HOW can one test something like that, LOL?
Click to expand...
Click to collapse
Well not that much ridiculous I think! In server world one important measure is availability which is primary based on MTBF. Supposing that an ideal PPC never needs to be soft/hard reseted an average measure of uptime of your ROM is an approximate of stability. Statistics I mean.
Averaging thousands of results of all previously cooked ROMS stability of device is measured which can be a valuable feedback to the manufacturer.
(I think I think in wide usually and open as well. Probably my nickname is producing a lot of negative feedback to my ideas. Maybe I should test this more. )
cina said:
(I think I think in wide usually and open as well. Probably my nickname is producing a lot of negative feedback to my ideas. Maybe I should test this more. )
Click to expand...
Click to collapse
Ohh, do not take it personally, please...
Averaging thousands of results of all previously cooked ROMS stability of device is measured which can be a valuable feedback to the manufacturer.
Click to expand...
Click to collapse
Do You think they WOULD CARE? It's all about salary, nothing more.
---
Notice, that NOBODY is using stock roms, too(and it is quite clear, there's reason for that ).
It may be interesting - reporting cooked roms performance to...stock rom manufacturer
pupakota said:
Ohh, do not take it personally, please...
Click to expand...
Click to collapse
Paranoid a bit I am. Anyway thx for the encouragement.
pupakota said:
Do You think they WOULD CARE? It's all about salary, nothing more.
---
Notice, that NOBODY is using stock roms, too(and it is quite clear, there's reason for that ).
It may be interesting - reporting cooked roms performance to...stock rom manufacturer
Click to expand...
Click to collapse
I know everything is driven by money. Even in healthcare where I currently work.
I don't want to repeat myself. But the basic idea was to help end users choose the ROM that best suits their needs. And to help chefs with feedback on their jobs.
Parallel with medical work all doctors need feedback about their patients to achieve better level of practice. A chef should learn from data collected from end-users and enhance their ROM development.
I understand that a lot of you cook for themselves and publish the result (one time cookers or beginners). But there are big names of cookers with huge experience working hard reading the posts about their ROMS and trying to debug based on that. Wouldn't it be easier to get collected data on ROM performance/stability, bug reports, SW incompatiblity, etc. in an organized way?
Anyway you said that
pupakota said:
And you know what..i haven't had single wm crash, batt drain or weak performance(cpu,batt) for 4 years, always used best base available
Click to expand...
Click to collapse
How do you know? Probably you are a lucky one that got an exceptional stable hardware, a battery with no weak cells and a wireless chip with no misaligned molecule in its layers. Others probably have weak hardware, SW from other source that you have never tested. Are you quite sure that your ROM is prepared for "all" situation? Probably not and no one can be sure about that. (And do not take it personal). "Perfection cannot be reached but we should try it hard." - source unknown.
So literally I propose a software that measure some performance/stability/compatiblity issues of cooked ROMs and I've just listed my ideas. Anyone who will develop a software like this will add its own ideas and probably suppress/emphasize some of mine. I intended just to inspire developers for such a solution. I didn't want to give a clear solution anyway but I offered some help with a work like that.
Best regards,
Cina.
Allright, good luck, really...
Paranoid a bit I am.
Click to expand...
Click to collapse
Me too, mate, me too
I understand that a lot of you cook for themselves and publish the result (one time cookers or beginners).
Click to expand...
Click to collapse
btw i am not beginner. i stopped making public roms 2 yrs ago.
How do you know?
Click to expand...
Click to collapse
..because i can see it.
my softpack was tuned for almost 2 yrs, practically every single apps' oem is made by me, every single app is reconfed by me.
my methods for getting optimal os base were tuned for almost 5 yrs(and regardless of base, builds are always made with same, OLD methods).
zero HTC soft inside. zero useless soft inside. zero useless dlls, zero useless reg entries. bases with ANY kind of problem are thrown out and not used by me.
i do not need any external info from anyone to get optimal results. strict methods have very important feature: elimination of sudden misbehaviours, unknown problems, so only problems with any of: performance, batt,whatever, may come from base then.
That's all.
i do not know anything about others' point of view on external performance/etc. data ideas, but it may be hard to believe that good cooks are not having similar ways. You know, i see that someone tells: "That base is good", allright, 20 minutes later i have ready rom, so it's quite fast way to check, if it is good base, then practical subsystems tests in reallife verificate REAL usability. btw hard to imagine such build list, if we cannot have EVEN clear com 2,3,5 builds list, lol.
sorry for LQ english(or engrish..).
"Perfection cannot be reached but we should try it hard."
Click to expand...
Click to collapse
So true...
Thanx. And I appreciate your posts. Really.
pupakota said:
btw i am not beginner.
Click to expand...
Click to collapse
I've already got that.
I got an EVO myself and managed to overclock it to 1.267GHz. We could probably go even higher, but that requires more extensive changes. Here are the changed source files: http://dl.dropbox.com/u/36553/supersonic_oc-uv.tar.gz
It also includes an undervolt courtesy of pershoot (a whole 0.1V lower when idle, which should help battery drain a lot!). Here is a test update.zip: http://dl.dropbox.com/u/36553/supersonic_oc-uv_signed.zip (working WiFi). Make sure to do a nandroid backup first!
Sensors/camera do not currently work in this kernel because the source is not yet complete.
There is an overvolt on the highest frequencies. It should not cause any issues. Thanks to toastcfh for his source, Herver for creating the first booting overclocked kernel on the EVO, all the kernel devs in the N1 community, especially pershoot and kmobs, richardtrip from the Desire community, koush for anykernel updater, and all who helped to root the EVO. Enjoy!
Update 6/15: Fixed 950mV undervolt. Raised voltages from 1228800 above to improve stability. Source files updated and update.zip uploaded.
old said:
I posted these in an earlier thread, but I think I should bring this to everyone's attention. Here are some simple patches that will overclock the Evo up to 1.267GHz (though by any means it's not guaranteed to get that high!):
Edit: please don't flash the below update.zip, as it doesn't seem to boot. Devs, the patches are still below, and a zimage is in the anykernel update zip.
Update: I compiled it myself. Here is an update.zip: http://dl.dropbox.com/u/36553/update-oc_signed.zip. This uses toastcfh's sources, Koush's excellent anykernel updater and a config.gz pulled from a stock Supersonic. If this doesn't boot, no damage will be done to your phone. Just reboot into recovery and reinstall your ROM. You can test overclocking by grabbing SetCPU from my sig or changing the cpufreq values if you know how. Once we get this working, I will create an undervolted version for battery savings. I'd get an Evo, but it's sold out everywhere T_T
http://dl.dropbox.com/u/36553/supersonic_oc.zip
cpufreq.c and acpuclock-scorpion.c are in arch/arm/mach-msm, and supersonic_defconfig is just the config. I don't have an Evo, so I can't test these out, but these should work with the source files toastcfh posted earlier: http://forum.xda-developers.com/showthread.php?t=686240.
Undervolting can be achieved simply by adjusting the voltages (in mV) in the acpu_freq_tbl table in acpuclock-scorpoion.c. For those not familiar with his work, you can see pershoot's safe (but lower) voltages for the N1 here: http://github.com/pershoot/nexus-kernel/blob/master/acpuclock-scorpion.c. If you want to overvolt or go under 1000mV, you have to make one further adjustment to the voltage regulator in board-supersonic.c.
Note that the N1 and the Evo are completely different devices (with similar processors), so what may work for the N1 may not work for the Evo.
Click to expand...
Click to collapse
Awesome... until I am sure this is stable, I will wait, but I must have overclock
jigglywiggly said:
Awesome... until I am sure this is stable, I will wait, but I must have overclock
Click to expand...
Click to collapse
I don't recommend overclocking, the devices already can run warm at current settings.
But then again, you are entitled to do as you wish.
Options better than overclocking are to remove the Sprint bloatware and strip down parts of Sense, this speeds things up alot by removing excess background applications.
Well it ain't too bad, my Droid at 1 ghz(550 stock) runs great.
So this should be good too.
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
phinnaeus said:
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
Click to expand...
Click to collapse
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Well, I agree with the benchmarking comments but on the subject of Froyo... Froyo is designed to be even faster on equivalent hardware than 2.1... and 2.1 on my Evo is smooth as silk. And the Evo handles most Flash I can throw at it, so I'm not sure. I have however noticed a small performance difference with live wallpaper running, so maybe OCing will clear that up a bit.
Jus10o said:
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Click to expand...
Click to collapse
You know, this is an excellent point and I feel like I failed the developer community in some small way when you had to bring it up. You shouldn't have to provide a reason for wanting progress, it should happen for its own sake.
Proceed.
Jus10o said:
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Click to expand...
Click to collapse
Agree with everything you just said, and I am less than excited about the benchmarks with the EVO thus far
Roman G said:
Agree with everything you just said, and I am less than excited about the benchmarks with the EVO thus far
Click to expand...
Click to collapse
HAHAHA.. im sorry but i had to laugh at your sig.
Jus10o said:
HAHAHA.. im sorry but i had to laugh at your sig.
Click to expand...
Click to collapse
Ya I sold my hero a couple weeks before the EVO dropped, and had to use my wife's old phone.
phinnaeus said:
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
Click to expand...
Click to collapse
I'm not trying to start an argument at all but you have to think broader mathematically. If the processor runs at 1000Mhz or 999mhz (In the case of my N1) a .267 increase is 267mhz, a 26.7% increase in computational performance... That's pretty raw especially in cellphone terms, that have no way to vent or displace that kind of heat.
Has anyone noticed how much hotter the kickstand gets? I bet you that it's attached to something the cpu is connected to. $5 bucks says we will see KICKSTAND HEATSINK + FAN MOD 2GHZ OC! LOL
thebluecoat said:
I'm not trying to start an argument at all but you have to think broader mathematically. If the processor runs at 1000Mhz or 999mhz (In the case of my N1) a .267 increase is 267mhz, a 26.7% increase in computational performance... That's pretty raw especially in cellphone terms, that have no way to vent or displace that kind of heat.
Has anyone noticed how much hotter the kickstand gets? I bet you that it's attached to something the cpu is connected to. $5 bucks says we will see KICKSTAND HEATSINK + FAN MOD 2GHZ OC! LOL
Click to expand...
Click to collapse
This is a patch for developers, not a discussion thread for the merits (or lack thereof) of overclocking.
If you don't want to overclock your phone, nobody is making you.
It has worked out fine in the Desire and Nexus One community.
coolbho3000 said:
This is a patch for developers, not a discussion thread for the merits (or lack thereof) of overclocking.
If you don't want to overclock your phone, nobody is making you.
It has worked out fine in the Desire and Nexus One community.
Click to expand...
Click to collapse
how do i apply this ???????
can u make it flashable?
mccurt29 said:
how do i apply this ???????
can u make it flashable?
Click to expand...
Click to collapse
need to follow the directions in the first post. the .c files need to be loaded into the kernel source (right now just have toast's soruce) and the kernel has to be compiled with them.
if somebody wants to compile up a kernel with these, we could start testing. if i get some free time i'll help out here and compile a kernel but somebody else will prob beat me to it!
please someone let us know how this works out for your evo 4g... benchmark, test results... anything to show better/worse performance, whether your got ALOT warmer, or just a lil, etc.. ne information would be greatly appreciated it, i'm not a 100% noob, i just know how to follow instructions very well, doesn't mean i understand everything that's going on, just the basic concept of what i want. thank you in advance.
madunix said:
please someone let us know how this works out for your evo 4g... benchmark, test results... anything to show better/worse performance, whether your got ALOT warmer, or just a lil, etc.. ne information would be greatly appreciated it, i'm not a 100% noob, i just know how to follow instructions very well, doesn't mean i understand everything that's going on, just the basic concept of what i want. thank you in advance.
Click to expand...
Click to collapse
I'm waiting for someone to compile this first.
If nobody steps forward, I'll make my own attempt, but I'll be working blind with no test hardware.
I'm pretty sure most devs are waiting on the htc source kernal before playing with this. I can't wait but I understand them being hesitant to do too much with this for now. Still awesome of you to post it and have it rdy for when that time comes!
sounds good.
madunix said:
sounds good.
Click to expand...
Click to collapse
Your signature says you have a radio of 1.32.651.6, just to let you know that is not a radio, that is an HTC software OTA update. My radio is 1.39.00.05.31 for example
So I keep hearing complaints about "lag" with the Galaxy S4. Some of you have it and some don't.
Well, debloating your ROM (removing junk apps that you don't use) will typically reduce lag since these extra apps aren't fighting for system resources. But that doesn't work for everyone.
Another thing to do is to flash an AOSP (android open source project) ROM. These ROM's (including gapps) are usually less than 300MB in total size, while a stock or even debloated stock TouchWiz ROM are almost always 800MB to 1.3+GB in size.
Another thing you can try is to install "Seeder". Some folks will suggest it doesn't really do anything for you. Some others will say it uses up a lot of battery. So I guess every application is different. Because for me, even with an AOSP ROM, I seem to get slightly faster system response time when I click on something. And I've left my phone alone over eight+hours and checked battery useage and don't see Seeder anywhere taking up any battery.
Here is the Seeder main application thread. There, you can "thank" the developer (lambgx02) and also ask questions about the app. You can also download Seeder from that thread for free.
http://forum.xda-developers.com/showthread.php?t=1987032
Or, you can be a nice person and "buy" the app from the Play Store. At less than $2, it's not very expensive.
https://play.google.com/store/apps/details?id=com.lcis.seeder&hl=en
You can either read about how/why the app works or doesn't. Or you can try it for yourself.
For me, it's a must-have on the S4 since even AOSP ROM's still have a small amount of lag when compared with the smoothed-out ROM's on the S3.\
REQUIREMENTS:
-Rooted ROM
-Canadian or USA or Euro S4's, it works for all of them.
-TouchWiz or AOSP, it doesn't matter which.
So, here's how to install it:
1) Download Seeder to your internal or external SD card. It doesn't matter where.
2) Using Root Explorer (or your file browser of choice), locate and click on the seeder.apk.
3) Select "Install".
4) Select "Install" again.
5) Click "open".
6) Read the disclaimer and click "OK".
7) Grant root permissions:
8) Make your settings identical to mine (to start with). I've actually since changed mine from "Moderate" to "Aggressive" because I noticed no change in battery life. So, why not.
9) Now reboot.
10) Wait two minutes after the phone comes back up (to allow background start-up processes to finish) and start using phone normally.
Good luck, hope it works for you as well as it works for me. This is not a "cure-all" for lag, but it should help speed up an otherwise healthy system.
Don't expect miracles either. Only a really fubard'd ROM might show HUGE differences. But this app will probably help a little bit.
I had tried this program on my ATT GNOTE after the new JB update that seemed to slow everyone's phones to a crawl. It did help somewhat, but not enough for it to become bearable.. Caved and bought the S4. Seems like the app DOES work.
This app is a myth that has been busted even by the xda portal.
http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Try this instead
plwalsh88 said:
This app is a myth that has been busted even by the xda portal.
http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/
Click to expand...
Click to collapse
I endorse the posting of this link. I actually intended to do so in the OP when I was typing up the original post (and lost it all to a BSOD).
The article refers more to the theory behind the "fix".
But end results are end results, and the app works for some people. It also does not work for some other folks.
Like I said in the OP, try it and see how it works for you.
CZ Eddie said:
I endorse the posting of this link. I actually intended to do so in the OP when I was typing up the original post (and lost it all to a BSOD).
The article refers more to the theory behind the "fix".
But end results are end results, and the app works for some people. It also does not work for some other folks.
Like I said in the OP, try it and see how it works for you.
Click to expand...
Click to collapse
Right, and it shows that the theory behind the "fix" is flawed, having no effect on app execution. The only positive performance you're seeing is a result of boosting CPU speeds. It's not saying you're not seeing results. It's just that you're seeing them for the wrong reason; the same of which can be achieved by changing your CPU governor.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
plwalsh88 said:
the same of which can be achieved by changing your CPU governor.
Click to expand...
Click to collapse
Negative. Because I've seen results on top of overlocking and governor changes.
CZ Eddie said:
Negative. Because I've seen results on top of overlocking and governor changes.
Click to expand...
Click to collapse
I highly, highly doubt any other positive effects can be discernible on top of overclocking.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
The system lags because touchwiz has many many features beyond those that you can just simply remove with titanium backup and such, there are a lot of features;what they seem to call them. That adjust color and lighting beyond ambient at all times no matter what. Samsung needs to release an update which I know they're cooking up, that optimizes these resource hog and debugs that are constantly running in the background... Let's just hope we get it soon and not have to wait till 4.3 to get it. The only way to get rid of all of the lag is to switch to also otherwise there will always be a tad amount of it, until samsung fixes it themselves; there's only so much developers can conjure up
The only way to get rid of the lag is by installing a custom ROM, either AOSP/AOKP or a TW based ROM like Omega or Winam. Then installing a custom, polished kernel like KT's kernel. Then disabling the scroll cache.
That makes this thing run like it should have in the first place.
Yeah seeder sucks sorry to say its not actually doing much.
I want to work with someone, anyone and get a kernel going again for this phone. I have experience helping make roms and kernels a long time ago (in a time far far away) and really want to get something going. I am willing to collaborate with many people to get this going. I have the "PC" capable enough to do this with the storage. I was thinking possibly revitalizing the resurrection kernel that has already been done for Oreo (no sense in recreating the wheel). /shrug Lets do this!
meatwad0222 said:
I want to work with someone, anyone and get a kernel going again for this phone. I have experience helping make roms and kernels a long time ago (in a time far far away) and really want to get something going. I am willing to collaborate with many people to get this going. I have the "PC" capable enough to do this with the storage. I was thinking possibly revitalizing the resurrection kernel that has already been done for Oreo (no sense in recreating the wheel). /shrug Lets do this!
Click to expand...
Click to collapse
Hi, we'll be happy to see you in the group on the telegram. Here are some great devs who work on this phone. https://t.me/MotorolaG6
I am very happy to know that someone is interested in improving this device, but I would ask you a favor.
if possible, could remove the underclock of the 1.8 ghz cpu (which is no big deal), for 1.4 ghz (which is impossible to use the device without being angry with lags and crashes
when it reaches 40 degrees
I know this is a protection to prevent it from frying, but I had a g4 that reached 44º, and I never had any problem and it never happened.
I play a lot of PUBG, when it reaches that temperature, it drops the clock to 1.4 ghz and I lose about 30fps, not to mention the lags.
I believe that removing this limitation or even increasing the tolerance of the underclock to 45 ° will not make my device explode
I think this would greatly improve the performance of this device, since 1.4 ghz is practically a G4
Indeed, and more.
There is an absolute tonne of roms, kernels and other modifications for devices like the g5 and g4. no one seems to be keeping things up to date on the g6. i'm more than happy to have my phone used as a guinea pig (as long as it doesn't break). My skills in roms and kernels are very limited but i'm sure there are guys out there with much better skills.
I'd hugely appreciate if someone put in the effort to build a kernel and preferably a rom to go with that can be kept up to date with bug fixes like every fortnight (like on the g5) with something like arrowos.
Anything i can help with, let me know!
We are working on the kernel! If you want, join us!
Now we already overclocked the moto to 2,6GHz cpu, and 700Mhz GPU.
petya230 said:
We are working on the kernel! If you want, join us!
Now we already overclocked the moto to 2,6GHz cpu, and 700Mhz GPU.
Click to expand...
Click to collapse
jesus christ this is my dream <3
If you want, I can test on my xt1925-3.
I do not mind killing my device
Wow
petya230 said:
We are working on the kernel! If you want, join us!
Now we already overclocked the moto to 2,6GHz cpu, and 700Mhz GPU.
Click to expand...
Click to collapse
Thats brilliant, give me a shout if theres anything i can do or test stuff