UPDATE
Due to unforeseen issues with this build and a plethora of people incapable of reading even simple notes, this release is being pulled while we work out some issues with our own internal testers.
Thank you.
Kernels. The final pain in the arse. These are the voyages of the dev team Ninphetamine. Our continuing mission, to break strange new code. To seek out new bugs and strange implementations. To boldly go where no phone has gone...before.
*cue musical score*
It's been some time since I last graced the Android community. Draped in the success of FroydVillain 1.5, empowered from my victories over Froyo's poor (and non existent) AOSP implementation for the HTC Hero, onward I charged into the task of dragging the ancient kernel of the Hero into the 21st century. However, after seeing how HTC are as likely to stick to recommended kernel practices as I am likely to win a Miss Universe contest, (This is highly unlikely and the least significant reason is that I am not female.) I buckled like a jet fighter made from tin foil and surrendered faster than an agoraphobic Frenchman. There has been some advances into more modern kernels for the Hero but as I predicted they're still plagued with issues, all of which can be blamed squarely on HTC.
It took some major rehabilitation to get me back into the Android development scene, a key factor in that rehab being the ownership of a Samsung Galaxy S. A delightful phone, still in my opinion the best single core Android phone that money can buy. Beautiful screen, fast, elegant and excellent on battery. It nursed me through those dark days of waking up in cold sweats with github commits circling through my head, kernel debug symbols blinking in the dark of the night like Vietnam flashbacks, breaking down into incoherent rants on IRC development channels ending eventually with "YOU WEREN'T THERE MAN, YOU JUST DON'T UNDERSTAND, HTC WILL COME AND GET YOU EVENTUALLY, THEN YOU'LL KNOW". Oh how I longed to find a high up HTC developer in a bathroom to blow them away before ending my own bitter misery. Alas, it was not to be.
After a successful tour of duty as a regular non developing user on the Samsung Galaxy S, I treated myself to a brand new and shiny Samsung Galaxy S II. As soon as I used the device and checked out the available source code for it, I knew I was ready, I knew I was fully recovered to be able to break free from the oppression of HTC, I knew that I was capable to step once more unto the breach and step back into Android development. The stage set, the orchestra struck...all that remained was to see if the Samsung Galaxy II could dance.
And dance it can. Accompanied by my trusty partner in crime netarchy (because this time if I go down in a gibbering wreck I'm damn sure taking someone with me) there is at last another phone with the magic, capabilities and horsepower to endure the test of time and upgrades, that like the Hero has carved out a niche of not only being the good of its generation but being the very best of its generation. Such hardware deserves only the best development efforts and here we are.
The best kernel for a phone that any human hand is capable of producing at this very moment in time. This will of course be rendered moot with the next release BUT RIGHT NOW, this is it boys and girls. Download it, flash it, use it with whatever ROM you wish (VillainROM of course for those with an IQ north of my shoe size) and enjoy the liberated freedom, speed and stability that those whoever owned a HTC Hero became accustomed to.
After much arguing with Samsung's inane practices, lack of logic, bizarre design decisions and enough harrassment via their support interface that I confidently expect a restraining order any day now, I bring you...
Ninphetamine version 1.0, the beginning.
Features:
Overclocking up to 1.6GHz. The phone is blisteringly fast at stock 1.2GHz so be happy you can push it to 1.6GHz. We will not provide higher, if you want higher then make your own.
Full voltage control interface. Via SetCPU you can set voltage as low as 800mV or as high as 1500mV for each speed in the database. If you're possessed with the intelligence of a baboon and destroy your phone as a result, do not come crying to us. All you'll get is a quote in this thread with much mocking from myself and your peers.
Patches and bug fixes up to and including 2.6.35.11. We're working on going up to 2.6.35.13 however the important fixes are in already. As well as some that never made it to 2.6.35.y -at all-.
Fully tested performance optimisations. This kernel comes with BFQv2-r1 IO scheduler enabled as default along with some tweaked parameters for this scheduler. These were painstakingly tested over many many many many many MANY different benchmark tests. These are the best. Anyone who claims otherwise or says that noop or deadline or CFQ is better, they're wrong. Why? Because I say so and I'm right.
A customised and trimmed down initramfs, including Clockworkmod. Many thanks to ogdobber for this who kindly gave me the template including ClockWorkMod that I took and further improved upon. All storage mounts are optimised for performance and data throughput, busybox is included as well as a much improved shell that by default provides tab completion even via adb shell. Please note that by default, adb is insecure, this means that adb shell, adb remount etc all work and give root access immediately.
So there you have it. Please download, flash, test and report any issues/bugs in this thread. I'll then either completely ignore the dumb posts or take on board constructive ones and use those reports/suggestions, incorporate them into the next version and then take all the credit.
Thanks to:
This release would not have been possible without the awesome and tireless work of netarchy, of Nexus S and Asus Transformer fame. Thanks also to ogdobber and supercurio for their assistance. Also thanks to mattgirv, Lenny, Rawat, Obihoernchen, geko95gek and Ante0 for being my guinea pigs for the many many test builds that were made before this final release, no doubt without them there would be a lot more bugs in this release than there already are. Also not forgetting of course, the everlasting patience of my wonderful wife, without which I never would have bothered picking Android up again at all.
Bugs/Issues:
Please of course report them in this thread, however before doing so, please:
Wipe dalvik.
Ensure you have no other OC software installed such as Tegrak. The only OC software supported by this kernel is SetCPU (or setting manually via command line of course).
Are you using a custom ROM? See if you still get issues with stock Samsung firmware or VillainROM. I cannot test with every single custom ROM out there, so I test with stock Samsung (naturally) and my ROM of choice.
If you're still having issues such as random hangs/crashes/reboots and if these issues still occur at stock speeds/voltages then please do the following:
Install the Android SDK if you have not already done so.
In a command window, do the following:
Code:
adb logcat > USERNAME-logcat.log
Then in another window:
Code:
adb shell cat /proc/kmsg > USERNAME-kmsg.log
Naturally replacing USERNAME with your name and make these logs available either via attachment or pastebin or whatever. Please do not paste them directly into posts as these logs can become quite large quite quickly.
Known Issues:
adb install <package> currently does not work.
Version 1.1
Changelog:
Some minor edits to the initramfs to fix adb install <application>.apk and a few other path issues. Loses the nice adb shell with tab completion, but fixes some issues. Download links updated.
Version 1.2
Changelog:
More initramfs changes to fix an issue with nandroid backups.
Making nandroid backups work again may have broken the "adb install" package install method, but I figure working nandroid and needing to push the apk to the phone to then install with Application Manager beats broken nandroids. I'll look further into the adb install issue later today.
Version 1.4
Changelog:
Some configuration changes to try and track down the random hangs/reboots people are experiencing.
Support for startup scripts in /system/etc/init.d added should ROM makers wish to use them.
Added debugging code, which prevents deep sleep in version 1.4, but makes crashes easier to diagnose.
FAQ/General Points
I hate Odin. It is a giant buggy piece of ****. Things can inexplicably go wrong for no other reason than Odin is a big heap of proprietary fail. Before reporting issues with the kernel, please either flash it with CWM or Heimdall. I highly recommend Heimdall, it will flash a jpeg to your kernel filesystem if you tell it to and somehow it'll boot anyway. I do all my testing with Heimdall so it's safe to assume that if I'm posting it, Heimdall will flash it. Heimdall also has the advantage of being open source and completely cross platform. Please take the time to download it and get used to using it, it will save you a lot of pain in the future.
This kernel has been tested with 2.3.3 KF2 and 2.3.4 KG1. There is no reason it shouldn't work with any ROM revision.
Somewhat amazing that I need to point this out, but you MUST FLASH THE KERNEL FOR THE VOLTAGE TAB TO APPEAR IN SETCPU.
Don't use tegrak with this kernel. DO. NOT. USE. TEGRAK. WITH. THIS. KERNEL.
The voltage that's adjusted is the CPU core voltage.
Major_Sarcasm said:
Just a FYI for those people that can't make logical connections; if you have Tegrak OC installed when you flash this kernel, you might end up with a boot loop. Go back to default settings in the app, then uninstall it before flashing.
Click to expand...
Click to collapse
More will be added to this post as the need arises.
pulled for now
SUPER !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Thank you !!!
netarchy said:
Use the voltage interface in SetCPU.
Click to expand...
Click to collapse
OOOO who is here!!! famous netarchy
Hacre said:
Reserved
Click to expand...
Click to collapse
Welcome. Will give it a try.
2.3.3, 2.3.4 ... all ok w this universal kernel?
EDIT: Great... I see you edited Post #2, and the answer is yes.
Thanks for the kernel. Does this have the multi-touch fix included?
jlevy73 said:
Thanks for the kernel. Does this have the multi-touch fix included?
Click to expand...
Click to collapse
I've not noticed an issue with multi-touch, of what do you speak?
*subscribes to thread*
netarchy said:
Use the voltage interface in SetCPU.
Click to expand...
Click to collapse
Okay maybe this is a dumb question, how do you undervolt using setcpu? I know I use it to underclock, and AFAIK it's different from undervolting. I've check the interface of setcpu just now trying to find undervolting options
mach0boi said:
Okay maybe this is a dumb question, how do you undervolt using setcpu? I know I use it to underclock, and AFAIK it's different from undervolting. I've check the interface of setcpu just now trying to find undervolting options
Click to expand...
Click to collapse
Make sure you're using the latest version, and use the voltages tab.
mach0boi said:
Nice! So how will you do the undervolting here?
Click to expand...
Click to collapse
Ummm...
Hacre said:
Full voltage control interface. Via SetCPU you can set voltage as low as 800mV
Click to expand...
Click to collapse
If only I'd mentioned it in the OP...
netarchy said:
Make sure you're using the latest version, and use the voltages tab.
Click to expand...
Click to collapse
Ooh okay i didn't knew there was such feature! thank you!
Hacre said:
Ummm...
If only I'd mentioned it in the OP...
Click to expand...
Click to collapse
I'm sorry maybe I'm just using an outdated version and never knew you could actually do that. Forgive my ignorance
sorry i am new to android so i do not know about undervolt or overclock, can anyone please tell me best combination of voltages on 1.6ghz that does not effect battery life?
ravian29 said:
sorry i am new to android so i do not know about undervolt or overclock, can anyone please tell me best combination of voltages on 1.6ghz that does not effect battery life?
Click to expand...
Click to collapse
The stock max voltage of the CPU is 1275-1300mV. Anything under this improves battery life, anything over this harms battery life from the standard "stock" expectations. Just like with a PC, not all processors are created equal. There is no setting for 1.6GHz that will not affect battery life as at best you'll need to increase voltage from the standard max setting. If you're not sure, use our defaults, these have been tested on two different handsets. There isn't even a guarantee that 1.6GHz will even work on your handset.
If you're not sure or are not confident, don't touch it. Any settings you set past 1.2GHz/1300mV are at your own risk, may damage your handset or even rip a hole in the space-time continuum, then you'll not only look an idiot with a broken handset but Stephen Hawking will be really pissed and you really don't want him trying to crush your toes in that tank he calls a wheelchair.
Best case scenario, try our defaults and only increase voltage in 25mV steps. If you find yourself a 1450mV and your phone still isn't stable then 1.6GHz isn't going to work for you. If battery life is your concern, then consider undervolting in 25mV increments at 1.2GHz or even 1GHz or 800KHz.
mach0boi said:
Ooh okay i didn't knew there was such feature! thank you!
Click to expand...
Click to collapse
I am using the latest version 2.24, i don't see a voltage tab there..I only see Main, Profiles, Advanced, Info, About
@hacre cheers mate
umair9001 said:
I am using the latest version 2.24, i don't see a voltage tab there..I only see Main, Profiles, Advanced, Info, About
Click to expand...
Click to collapse
In Settings -> About Phone what does the Kernel version show?
umair9001 said:
I am using the latest version 2.24, i don't see a voltage tab there..I only see Main, Profiles, Advanced, Info, About
Click to expand...
Click to collapse
Yeah also checked it and I'm also using the latest version. Was about to ask this. Another question, is that voltage tab option kernel related? I'm using cfroot kernel and cannot find that damn voltage tab I'm using tegrak to undervolt. If I knew there's a feature like this in SetCPU, I should've not bought tegrak
Related
I just recently rooted my thunderbolt, and I have a few questions about overclocking. I'm not as familiar with the thunderbolt as I am with the moto droid, so I'm not sure what an average speed is to overclock to. On my old droid, I overclocked up to 1.2ghz without any problems. On my thunderbolt, however, when I overclock past 1.267ghz, it freezes and then reboots. I'm not sure if that's normal or if my phone just isn't capable of handling anything more than that, but i feel like most people can get at least to 1.4ghz. Will a different kernel work better with my phone? And what are all of you overclocked to?
edit: forgot to mention i'm running synergy rom in case that makes a difference
Which kernel are you running? The stock synergy one? I don't know if it will make a difference changing them or not, but it could be a voltage problem with that specific kernel and your phone. I think all well at least I thought all Tbolts could handle 1.4ghz.
I personally don't have a problem even if I'm overclocked to 1.92 and extremely undervolted.
Yes, I'm running the kernel that came with synergy rom. So you think if I change the kernel it should work better? Is there a specific one you recommend?
I can't say for sure it will make a difference but it's worth a shot. I really like Imoseyon's kernels.
I've run that kernel. Ziggy tends to be pretty conservative regarding his voltages. You've got several options with a Ziggy kernel. You can write a script to change them. He explains how at ziggy471.com. You can use ScriptFusion, though I'd suggest using the terminal install as the app had some issues when I used it. Or, You could switch up to Imoseyon or dreamkernel, both of which I've found to be a bit more stable at higher clock speeds. 1.41GHz should be the least you should be able to over clock, with most able to do 1.6 and some able to pull off 1.8 or 1.9. Synergy and Ziggy kernels are NOT for the novice. Ziggy kernels aren't really meant to be toyed with my amateurs that aren't comfortable with ADB and basic script writing. ScriptFusion does work well on it though. Some ideas for voltage settings to get you to 1.6GHz: 1.024 should be somewhere around 1050 to 1100, 1.22 around 1150, 1.4 around 1275, 1.6 around 1375. I run my 1.6 at 1400 for stability, but some may be stable as low as 1325 at that speed. It's trial and error. How to test, using the ziggy kernel? Very easy. Open the terminal and enter "echo "xxxxxxx yyyy" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels" where xxxxxxx represents the clock setting and yyyy represents the voltage setting you wish to apply to the clock setting. Omit the quotes. This is useful if the setting is unstable. If it locks up, the phone will restart using original settings. Definitely check Ziggy's site if you're interested in learning how to work with his kernels the right way.
Thanks for taking the time to explain all that. I really don't want to mess around with any scripts, as i'm really not an expert with this stuff. I think I'm going to flash a new kernel and see if it helps. I was thinking of using dreamkernel, but there are three different files and I'm not sure which one to pick...?
http://www.nerozehl.net/dreamkernel_sense_2_3_6.zip - MD5:
15985306c69cf659c96abc085b9fa3a2
http://www.nerozehl.net/dreamkernel_sense_2_3_0.zip - MD5: 9f2e3f78d5d11b18508b141f715224fc
http://www.nerozehl.net/dreamkernel_sense_2_2_4.zip - MD5: ce5bd02540cbba9e687d5dbaae56931b
Those are the choices. Could you explain to me what the difference is between the three?
Also do you know if jdlfg's kernels are any good? I used to use them on my old droid and I really liked them, but they're not listed under the xda kernel list (http://forum.xda-developers.com/showthread.php?t=1081930) so I don't know if they're compatible with my phone. Again, thanks for your help.
xoluvsdance12 said:
Thanks for taking the time to explain all that. I really don't want to mess around with any scripts, as i'm really not an expert with this stuff. I think I'm going to flash a new kernel and see if it helps. I was thinking of using dreamkernel, but there are three different files and I'm not sure which one to pick...?
http://www.nerozehl.net/dreamkernel_sense_2_3_6.zip - MD5:
15985306c69cf659c96abc085b9fa3a2
http://www.nerozehl.net/dreamkernel_sense_2_3_0.zip - MD5: 9f2e3f78d5d11b18508b141f715224fc
http://www.nerozehl.net/dreamkernel_sense_2_2_4.zip - MD5: ce5bd02540cbba9e687d5dbaae56931b
Those are the choices. Could you explain to me what the difference is between the three?
Also do you know if jdlfg's kernels are any good? I used to use them on my old droid and I really liked them, but they're not listed under the xda kernel list (http://forum.xda-developers.com/showthread.php?t=1081930) so I don't know if they're compatible with my phone. Again, thanks for your help.
Click to expand...
Click to collapse
Those are merely different revisions of the same kernel. Use the newest one, 2.2.6,... that is, if your synergy build isn't on the newer gingerbread base. If it is, you're stuck with Ziggy's unless a working front facing camera and WiFi are features you couldn't care less about. On the newer gingerbread builds, Imoseyon's have proven faster than dreamkernel. Can't tell you why. From what I've seen of the latest Ziggy's, it simply cannot be clocked fast enough to keep up with Imoseyon or dreamkernel. Can't tell you much about the jdlfg. I thought that was an AOSP kernel. Never used it in any case.
loonatik78 said:
Those are merely different revisions of the same kernel. Use the newest one, 2.2.6,... that is, if your synergy build isn't on the newer gingerbread base. If it is, you're stuck with Ziggy's unless a working front facing camera and WiFi are features you couldn't care less about. On the newer gingerbread builds, Imoseyon's have proven faster than dreamkernel. Can't tell you why. From what I've seen of the latest Ziggy's, it simply cannot be clocked fast enough to keep up with Imoseyon or dreamkernel. Can't tell you much about the jdlfg. I thought that was an AOSP kernel. Never used it in any case.
Click to expand...
Click to collapse
So if I'm on a newer gingerbread build I can't flash any other kernel? How do I know if I'm on a newer gingerbread build? I just flashed synergy rom I believe on July 20th or so, so I guess I am running the newer build.
If I do run lean kernel, my options are GB SENSE DOWNLOADS:
1) lean test, 1) 184Mhz test, 3) Stock kernel, 4) USBfix, 5) 2.5.3test7 kernel, 6) dreamKernel
Which of these would I want? Stock?
Also, it says the GB sense kernel is a test version and has bugs. Should I worry about that?
xoluvsdance12 said:
So if I'm on a newer gingerbread build I can't flash any other kernel? How do I know if I'm on a newer gingerbread build? I just flashed synergy rom I believe on July 20th or so, so I guess I am running the newer build.
If I do run lean kernel, my options are GB SENSE DOWNLOADS:
1) lean test, 1) 184Mhz test, 3) Stock kernel, 4) USBfix, 5) 2.5.3test7 kernel, 6) dreamKernel
Which of these would I want? Stock?
Also, it says the GB sense kernel is a test version and has bugs. Should I worry about that?
Click to expand...
Click to collapse
1 through 5 are all good. Dreamkernel is a bit different, but not bad. I'm using the test to write this on, so its quick and solid. If the nightly is that new, its probably the new base so using one of these will likely mess up your front facing camera and WiFi. Before you flash one of these, try Twistedumbrella's scriptfusion on that Ziggy kernel. That might be the best way to go at this point. If you have any question, hit me up.
I went on ziggy471.com, but I'm a little confused about which article to read about writing scripts. Is it this one? http://www.ziggy471.com/2011/04/07/vdd-smartass-and-cpufreq-sysfs-interfaces-and-how-to-use-them/
I'm kind of hesitant to use script fusion, as I don't want to mess anything up, so I was wondering if you could walk me through it? Or at least point me in the right direction on finding instructions? I looked at the page for scriptfusion, but I didn't understand what a lot of the things meant. I really don't know much about this stuff. If you think it will be too difficult for me, I will just accept not overclocking and hope the wifi issues will be fixed on the other kernels soon.
I alternated between leanKernel & dreamKernel on Gingeritis. Too bad imoseyon hasn't updated Sense leanKernel in almost 4 weeks. I guess he's sticking with cm7
Sent from my ADR6400L using XDA App
I am running chingys lastest 3d beta 5 and I have always used dreams sense kernals but this one came with ziggys and I have decided to try it out. Is it a bad idea to just use setcpu with ziggys kernal? I know your not supposed to use setcpu with speedtweak.sh but this kernal doesn't use that
Sent from my ADR6400L using XDA App
MarkMyShark said:
I am running chingys lastest 3d beta 5 and I have always used dreams sense kernals but this one came with ziggys and I have decided to try it out. Is it a bad idea to just use setcpu with ziggys kernal? I know your not supposed to use setcpu with speedtweak.sh but this kernal doesn't use that
Click to expand...
Click to collapse
SetCPU works with ziggy's kernel. For the record, SetCPU works with speedtweak as long as you instruct speedtweak to ignore max/min freqs
Sent from my ADR6400L using XDA App
SetCPU works just fine for any kernel. The reason you don't want to use SetCPU with ScriptFusion is they both attempt to do the same thing using the same method; create a script that will alter your settings. The disadvantage of SetCPU is that it's an app that takes up resources. Not a whole lot, but it does. ScriptFusion takes up nothing because it executes the script at boot and it's done. ScriptFusion simply makes writing a fairly complex script fast and easy, but the end result is a script that is written to /system/etc/init.d. Ziggy's kernels allow you more options in scripting than ScriptFusion provides for, if you know how to write the script. Stuff like manipulating the behavior of the governors and the like. That link is correct, and he has answered questions regarding that script on the Synergy Development thread at infectedrom.com. I'd like to help more, but I couldn't even write a script for one of his kernels because his settings are subject to change with every kernel revision. You'd have to know the stepping for the the clock and voltages before you could do anything. That's easy enough to get using the "cat" command, but if you don't know much about linux commands, doing the stuff you need to do can be a little daunting. I would suggest using ScriptFusion, and do a nandroid first. Also, download the GuiltyVirdict which will remove all setting if something goes wrong. If you want to try a speed or voltage setting before applying it through speedtweak.sh, follow what's in that guide. You can do it either through the terminal on your phone or through ADB. I've tried all of it and it does work.
If you'd like to hit me up while you're messing with it, you can hit me up on yahoo messenger at [email protected]
I'm using imyosons gb test kernel on gingeritis 3d and its smooth as butter at 1.4
Sent from my ADR6400L using XDA App
I've been running Synergy Rom/Ziggy's Kernel for about 1.5 months now, minimum I've ran it at is 1.2, max is 1.6. I haven't tried to go above that, but I've never had any issues with it going south on me. I set up a few different profiles, and drop it to about 768 overnight (3am to 7am for me). It's worked like a champ.
sonami said:
I'm using imyosons gb test kernel on gingeritis 3d and its smooth as butter at 1.4
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
@sonami: battery life been just as good or better on his rom than Ziggy's?
Sent from my ADR6400L using XDA Premium App
xoluvsdance12 said:
I went on ziggy471.com, but I'm a little confused about which article to read about writing scripts. Is it this one? http://www.ziggy471.com/2011/04/07/vdd-smartass-and-cpufreq-sysfs-interfaces-and-how-to-use-them/
I'm kind of hesitant to use script fusion, as I don't want to mess anything up, so I was wondering if you could walk me through it? Or at least point me in the right direction on finding instructions? I looked at the page for scriptfusion, but I didn't understand what a lot of the things meant. I really don't know much about this stuff. If you think it will be too difficult for me, I will just accept not overclocking and hope the wifi issues will be fixed on the other kernels soon.
Click to expand...
Click to collapse
That's the right link. If you're reluctant to use scriptfusion, I'm not going to suggest doing a manual script, as that all scriptfusion does in a much easier way. Scripts are the only way to adjust a voltage to make a less than stable clock speed become stable. I get the strong impression virtually ever Tbolt can do 1.41GHz, if not 1.6GHz. Is you're on Gingeritus3D beta5 I'd suggest moving to 6 since Ziggy made noticeable changes to the kernel that improve speed and overclocking. The voltage scale on Ziggy's in beta6 shouldn't require voltage changes to achieve 1.41GHz. ScriptFusion isn't that scary. Give it a try. And if things go real sour, use guilty verdict.
Alright - I'm not the type to ask questions if I haven't done hours of research already. Please do not tell me to google it, look harder, etc. Some of this stuff has frustrated me to no end, and some of you may be able to answer the question off the top of your head. So why not help out, right? ^^.
I did take a lot of time writing these questions out, and I know that it is quote a long read. If you only want to answer one here and there, that is fine. I GREATLY appreciate all help. If I sound mad at all during the read, please excuse that. If anything I'm a little frustrated, but definitely not mad at anyone or anything. I just want answers.
My Device:
3D with Silverlight/Netarchy-5 as the Kernel, and Synergy Rev. 316 2.3.3 as my Rom. So far, I have only been able to get a max quadrant score of 2600. Sort of disappointing compared to my last kernel/rom build, especially when I saw all the good Quadrant scores on Synergy's thread (and yes, I tested Ziggy's Stock Kernel too that came with it, but with no change in Quadrant scores).
I want to stick to 2.3.3 until they have overclocking for 2.3.4.
My old Kernel + Rom build was the RCMIX Kernel that could OC to 2050, and the Shooter Rewind 3D ROM. With this set-up, I was able to get a Quadrant score of 3,660.
Unanswered Questions (Or Questions I am still confused on):
2) In the Kernel threads, I always try to find which one will provide the best performance. I have a 4500 mah battery, so I usually can make almost anything last 2+ days for me. However, I'm not sure how to compare Kernels and determine what is better. This is what is listed under RCMIX:
V(R) I/O
SLQB
WIFI FIX
CIFS
TUN
NLS
WIMAX SUPPORT
Wifi Tweak to connect a weaker signal -108db over stock -88db
Under Silverneedle, the other one I think of using, it says:
- CIFS
- TUN
- Overclock up to 1.7ghz (this will likely be expanded in future builds)
- JHash3
- The usual assortment of build tweaks that those familiar with my previous work have come to expect
- Base updated to 2.6.35.14
HOW am I supposed to compare those two performance wise? Also, what does "TUN," "NLS," "V(R) I/O," and "SLQB," "JHash3," "CIFS," etc, mean? I'm assuming WIMAX is for 4g, but I'm not even entirely sure of that.
3) EXT4. I read the thread here, but a lot isn't explained. It says "You should only need to convert to ext4 optimized if you wipe data/nandroid" - is this just system data? I'm assuming it wouldn't wipe SD Card Data, correct? So basically it is like a Factory Reset? But then it says to flash "svn rev 450 or higher" after. Where would I get the Synergy's revised 450 version when I can only get the rev 316 version myself?
5) Virtuous OC MOD. Oh yes - this has probably given me the most trouble than anything. I used to use SetCPU. When I saw that Mod, I uninstalled it, installed virtuous, and it didn't work. I couldn't edit my files via terminal emulator given su permissions, via root explorer, anything. So I thought there was a conflict through some file left by setcpu and virtuous. SO I did a factory reset.
I then installed rev 316 synergy and RCMIX 4.2 with a 1.8ghz allowable OC on it, and also flashed the virtuous oc + dual core mod. First off, I have no clue what the difference is between DualCore VOC and DualCore 1.1 besides the fact that he said 1.1 solved some lag issue some were experiencing. So I installed that, naturally. Saw nothing change whatsoever. I then tried to edit my Virtuous OC files, which was a success! However, when I ran the command "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" - which is in his thread to determine if it is working, it showed the unedited number.
So I then did a normal reboot, in hopes it needed init.d to trigger, and I got stuck in an infinite reboot.
Lastly, I installed rev 316 by synergy again with silverneedle/netarchy 5 kernel. And that's where I am now. What did I do wrong?
6) Chainfire 3D / Turbo 3D (can't find link atm, but each are from the same creator). Will this help quadrant scores? What is this used for? Is it helpful?
8) What's the point of the V6 Supercharger for Android? How does it improve memory? Does it do the same thing as far as EXT4 is concerned? Is it already implemented in the current roms/kernels?
9) Besides my questions, is there a kernel or rom that you suggest for the best speed/performance, and why?
10) As far as Dual Core goes, as it been more bad than good? I've seen a lot of posts about people lagging with it on. Does it actually help?
11) Without any Dual Core mod on, what does the second CPU normally do anyways? Why would anyone make a dual-core phone without utilizing both dual cores? Or did we lose the dual core availability when we rooted our phones, and we are just now getting some beta beginnings of it back?
Thanks for anyone's time who reads any part of this, and thanks in advance to those who can answer some of them too.
Questions Answered (Thanks for those that helped!!):
If you believe there is more that could have been said in an answer, or that an answer is wrong feel free to add-on! Otherwise, I'm satisfied with the answers I have received and believe them to be right.
1) I've read through the Synergy thread, mostly the beginning and ending pages, and people talk about Revisions that are better than other (obviously). I just hooked up my SVN File Updater for the Nightly Updates, so would I not have access to anything later than Rev 316, but older than the current 2.3.4 version? I really would like to have access to the latest 2.3.3 build that works the best, which would probably include the EXT4.
1-Answer by life64x) 318 is the latest 2.3.3 and the last 2.3.3. Since they upgraded to 2.3.4
4) Let's say I backup my entire system apps + data using Titanium. Does that mean after I Wipe/Reset and go to a different rom/kern, or sense to aosp, that if I restored EVERYTHING, it would still work? Or should I only restore the things I "essentially" need?
4-Answer by life64x) Not all your system apps will be restored...sense...sense widgets etc. Data yes.. user apps will be restored. | I then asked "So titanium won't restore things incompatible with the ROM I am on, even if I hit restore all?" | Answer by life64x: That's correct becuase sometimes it won't let you...say different versions of rosie.apk or framework stuff that deals with sense UI.
7) What is "Cyanogen?" I don't understand if that is a type of software, group of people, or what the purpose of whatever that word is.
7-Answer by life64x and phatmanxxl)Cyanogen is the handle of a person that created a alternate android OS..away from manufacture stock software that is smaller and faster...bloateware removed, basic android is there. Cyanogen is also the name of the product from them. I forgot his name, but he developed a alternate source open source I might add for our phones and now tablets. Many phones have it and each phone has developers for it also. ASOP ROMs such as CM7 and MIUI are not available for the EVO3d yet, they are still in development.
Q. 4. Not all your system apps will be restored...sense...sense widgets etc. Data yes.. user apps will be restored.
Q. 7. Cyanogen is the handle of a person that created a alternate android OS..away from manufacture stock software that is smaller and faster...bloateware removed, basic android is there. Cyanogen is also the name of the product from them. I forgot his name, but he developed a alternate source open source I might add for our phones and now tablets. Many phones have it and each phone has developers for it also.
I am at lunch at work now and possibly later others will give the rest or when I get home from work I will try to do more. You have quite a bit and this thread will also help others.
life64x said:
Q. 4. Not all your system apps will be restored...sense...sense widgets etc. Data yes.. user apps will be restored.
Q. 7. Cyanogen is the handle of a person that created a alternate android OS..away from manufacture stock software that is smaller and faster...bloateware removed, basic android is there. Cyanogen is also the name of the product from them. I forgot his name, but he developed a alternate source open source I might add for our phones and now tablets. Many phones have it and each phone has developers for it also.
I am at lunch at work now and possibly later others will give the rest or when I get home from work I will try to do more. You have quite a bit and this thread will also help others.
Click to expand...
Click to collapse
Thanks for the information, I appreciate it a lot. So titanium won't restore things incompatible with the ROM I am on, even if I hit restore all?
That's correct becuase sometimes it won't let you...say different versions of rosie.apk or framework stuff that deals with sense UI.
life64x said:
That's correct becuase sometimes it won't let you...say different versions of rosie.apk or framework stuff that deals with sense UI.
Click to expand...
Click to collapse
Awesome. That answers that. Going back to cm7, is it mostly used for tablets? I don't see it for the 3d.
Diabetic said:
Awesome. That answers that. Going back to cm7, is it mostly used for tablets? I don't see it for the 3d.
Click to expand...
Click to collapse
ASOP ROMs such as CM7 and MIUI are not available for the EVO3d yet, they are still in development.
Q. 1. 318 is the latest 2.3.3 and the last 2.3.3. Since they upgraded to 2.3.4
Q.6. Don't worry about chain fire, unless you are a gamer. Regarding quadrant, it is crap. If you insist on going by it, take it with a grain off salt. Try other testing methods.
phatmanxxl said:
ASOP ROMs such as CM7 and MIUI are not available for the EVO3d yet, they are still in development.
Click to expand...
Click to collapse
Try VirusROM. It's a pretty good little AOSP ROM with some of those CM7 features like changeable desktop size, drawer size, custom rosie/launcher, custom animations.
phatmanxxl said:
ASOP ROMs such as CM7 and MIUI are not available for the EVO3d yet, they are still in development.
Click to expand...
Click to collapse
Ah - got it. So CM7 and MIUI are for original AOSP then? According to some threads, it is getting close. Should be interesting to watch. Thanks ^^.
life64x said:
Q. 1. 318 is the latest 2.3.3 and the last 2.3.3. Since they upgraded to 2.3.4
Q.6. Don't worry about chain fire, unless you are a gamer. Regarding quadrant, it is crap. If you insist on going by it, take it with a grain off salt. Try other testing methods.
Click to expand...
Click to collapse
Ah, I suppose I just read those posts wrong in that thread. I assumed that the 2.3.4 version started near revision 500. Definitely a bummer. I tried their latest 2.3.4 version just to see what it was like and it is much cleaner than the 2.3.3 rev 318 version. Guess I'll wait for an OC on 2.3.4 to go back to Synergy Sense.
As for "other testing methods" - what would you recommend? Anything in specific?
And what do you mean by "gamer." What would qualify as a "gamer" for HTC 3D? For example, I do play Legend of Zelda: Orcarina of Time on my phone ^^. It ran fine on RCMIX 2.2.3 and Rewind Shooter as long as I used SetCPU to 1728 max and 1080 min (or higher min, depending on if I had any problems). Haven't tried on my latest setup though.
Thanks again for your help!
chillfancy said:
Try VirusROM. It's a pretty good little AOSP ROM with some of those CM7 features like changeable desktop size, drawer size, custom rosie/launcher, custom animations.
Click to expand...
Click to collapse
I actually just flashed that yesterday night and am loving how much free RAM space I have. Currently have 305MB used and 497MB free. I love having extra space. I have a few problems with it, but nothing worth complaining over really. Stock Kernel that comes with it is probably best, right? Thanks for helping =-).
http://forum.xda-developers.com/showthread.php?t=1224659&page=33
Use the dual core kernel less heat=save battery with performance increase by taking off the load on a single processor
Hi there,
This is a development thread.
Don't ask for ETAs. Don't ask what's working. Don't ask how to use.
It is not yet in an usable state.​
INFORMATION
Click to expand...
Click to collapse
This is an attempt to make a homemade 3.x kernel for our beloved Galaxy S II. I'm targetting the GT-I9100 only for now, if you wish to get it running on other variants (I9100G for instance), feel free to port it to your device and do a pull request.
I started it off Origenboard 3.0.4 kernel patched to 3.0.24, so that we get the most up-to-date opensource drivers, removing the need of porting Samsung drivers from 2.6 (gingerbread) kernel.
We'll be able to merge proprietary stuff from Samsung when they release it (audio and modem mainly), but thanks to what we'll already have we'll have a proper 3.x kernel without any Samsung crap (such as their MTP implementation that is borked it seems).
GIT REPOSITORY
Click to expand...
Click to collapse
http://github.com/xplodwild/android_kernel_samsung_galaxys2
WHAT'S WORKING
Click to expand...
Click to collapse
Keys GPIOs
Regulator and battery (it loads well but Android doesn't show it's charging)
Screen/framebuffer
Touchscreen
MFC (untested but should work from Origen)
RTC Clock
Touchkeys
MAJOR ISSUES
Click to expand...
Click to collapse
Phone never wakes from deep sleep (<== We definitely need experts on this one)
ADB works only after unplugging and replugging USB cable (issue almost located)
HOW TO HELP
Click to expand...
Click to collapse
Well, start forking, do stuff and make pull requests so I merge it and everyone enjoys. I'd need some help for the major issues above (especially the deepsleep issue).
If you're not a developer, well, buy me a coffee, there's a donation button on the left of this post
I'll keep you informed when it'll be ready for "public" use.
Phone never wakes from deep sleep
cpufreq is stuck at 200Mhz in ondemand governor
My guess is that these might be connected - or does conservative work?
Our device becomes very unhappy if it enters suspend when the regulators aren't set high enough to support 200 MHz.
As an experiment - if you set the default voltages for 200/500 to match 800 and it fixes things, that's the problem. If it still breaks - it's something else and I have no clue what.
Entropy512 said:
[*]Phone never wakes from deep sleep
[*] cpufreq is stuck at 200Mhz in ondemand governor
My guess is that these might be connected - or does conservative work?
Our device becomes very unhappy if it enters suspend when the regulators aren't set high enough to support 200 MHz.
As an experiment - if you set the default voltages for 200/500 to match 800 and it fixes things, that's the problem. If it still breaks - it's something else and I have no clue what.
Click to expand...
Click to collapse
I was just thinking that Iirc it puts the device into 800 when waking, or something like that...
Entropy512 said:
Our device becomes very unhappy if it enters suspend when the regulators aren't set high enough to support 200 MHz.
As an experiment - if you set the default voltages for 200/500 to match 800 and it fixes things, that's the problem. If it still breaks - it's something else and I have no clue what.
Click to expand...
Click to collapse
I had the same issue when I haven't enabled the governors, so the CPU was stuck at 1200MHz but won't wake up either from a deep sleep.
I'll have a try with the voltage, but my guess is more that there's some steps missing (the default 2.6 kernel seems to have a "low power mode" in which the board gets before waking up, if I understood it correctly).
At the same time, I'm giving a try with the 3.3 branch at Linaro (check android-3.3 branch at my github). It's harder than 3.0 because there's no more s3c framebuffer, it seems to go directly to FIMD, and the LCD panel has to be setup through SPI.
Some update:
- Touchkeys, clock and various things added/fixed
- Patched to 3.0.24
Edit:
- Added sdcard mounting
Cool stuff should come very quickly
Good work...
---deleted some post----
Sorry u can delete this post as it making thread very ugly..
_____________________
Sent From My Phone
just buy u a expensive coffee! Work hard!
Yeah do you smell sources?
Sent from my GT-I9100 using XDA
boba23 said:
Does this mean you are smelling Samsung source code somewhere? ;-)
boba
Click to expand...
Click to collapse
We'll do our best without them.
True enough.
This kernel is the most exciting thing I'm watching lately.
Really excited about the outcome. Samsung Kernel is just not the way to go if you get an alternative like this, which is far more promising.
Here comes your coffee:
33P346290U8160844
Keep it up!
Before your release ... Samsung Released their open source kernel.. guys Congo.. will wait patiently for your kernel... Thank you.. love u Dev
Sent from my GT-I9100 using Tapatalk
sam razzy said:
Before your release ... Samsung Released their open source kernel.. guys Congo.. will wait patiently for your kernel... Thank you.. love u Dev
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
he already know it...pretty sure xplod and codeworkx will bring some state of art kernel to us
Samsung kernel is really dirty : A lot of hacks, outdated drivers, ... The Samsung way, just the same they do with Android (adapt mainline code to their stuff, instead of doing it the other way...)
But we're going to bring everything to a clean 3.0 or 3.3 base soon
Isn't 3.3 bleeding edge?
Sent from my GT-I9100 using XDA
awesome, man
despite not owning a sgs2 I like your work! Samsung should definitely review their way of development, way cook your. own soup, when it. Is. already done by someone else
they should just stay compatible and release the damn hardware drivers ;-)
Sent from my Nexus S using XDA Premium HD app
XpLoDWilD said:
Samsung kernel is really dirty : A lot of hacks, outdated drivers, ... The Samsung way, just the same they do with Android (adapt mainline code to their stuff, instead of doing it the other way...)
But we're going to bring everything to a clean 3.0 or 3.3 base soon
Click to expand...
Click to collapse
What is your definition of "clean"? - since a "clean" 3.0 mainline can't run Android at all, and a "clean" 3.3 can barely run it.
I'm still wondering why you renamed mach-exynos back to mach-exynos4 - you complain about outdated drivers, but you revert progress in the CM codebase? https://github.com/torvalds/linux/commit/830145796a5c8f1ca3f87ea619063c1d99a57df5 (The aforementioned commit was part of the transition from 3.1 to 3.2 in mainline.)
Edit: Some of Samsung's drivers are clearly full of ugly hacks and need major work. However, an automatic judgement of "it's different, therefore it must be old" is clearly not appropriate - it has already led you to make the mistake of "fighting the future" and taking the mach-exynos codebase backwards, when all of the evidence says that in the case of mach-exynos, "different" means "much newer", not "older".
Entropy512 said:
What is your definition of "clean"? - since a "clean" 3.0 mainline can't run Android at all, and a "clean" 3.3 can barely run it.
Click to expand...
Click to collapse
Clean, meaning a clean 3.0 with Android additions in it.
If you take Samsung 3.0.15, there's not much files (if you exclude mach and specific drivers) that looks like "clean" 3.0.15, which causes a LOT of troubles if you want to patch it up.
Entropy512 said:
I'm still wondering why you renamed mach-exynos back to mach-exynos4 - you complain about outdated drivers, but you revert progress in the CM codebase?
Click to expand...
Click to collapse
In mainline 3.0, it's mach-exynos4. It's renamed mach-exynos afterwards. Samsung had BOTH, with duplicated files which could lead to thousands of headaches when patching and doing stuff too.
Entropy512 said:
https://github.com/torvalds/linux/commit/830145796a5c8f1ca3f87ea619063c1d99a57df5 (The aforementioned commit was part of the transition from 3.1 to 3.2 in mainline.)
Edit: Some of Samsung's drivers are clearly full of ugly hacks and need major work. However, an automatic judgement of "it's different, therefore it must be old" is clearly not appropriate - it has already led you to make the mistake of "fighting the future" and taking the mach-exynos codebase backwards, when all of the evidence says that in the case of mach-exynos, "different" means "much newer", not "older".
Click to expand...
Click to collapse
Take Samsung max8997 driver, it's clearly 2.6 one. Mainline got a different implementation, not much complete as of 3.0 unfortunately (MUIC missing for instance).
XpLoDWilD said:
Clean, meaning a clean 3.0 with Android additions in it.
If you take Samsung 3.0.15, there's not much files (if you exclude mach and specific drivers) that looks like "clean" 3.0.15, which causes a LOT of troubles if you want to patch it up.
Click to expand...
Click to collapse
Makes sense, although unfortunately, some things are clearly backports of newer code, see below.
In mainline 3.0, it's mach-exynos4. It's renamed mach-exynos afterwards. Samsung had BOTH, with duplicated files which could lead to thousands of headaches when patching and doing stuff too.
Click to expand...
Click to collapse
Not sure what codebase you're looking at, but in the I9100 source drop I've been working with, there was only mach-exynos, not mach-exynos4, and definitely not both.
No matter what you name it, you're not going to be able to track mainline with this unless you sacrifice MASSIVE amounts of functionality (such as ditching support for any idle state deeper than WFI), because at least in this particular instance, mach-exynos in the Samsung drop is simply lightyears ahead of mainline.
You're going to have to either forget about bringing in mainline patches that touch mach-exynos for a long time, or accept a major reduction in functionality - no matter how you do it, mach-exynos needs to differ significantly from mainline to be even remotely useful.
Take Samsung max8997 driver, it's clearly 2.6 one. Mainline got a different implementation, not much complete as of 3.0 unfortunately (MUIC missing for instance).
Click to expand...
Click to collapse
This one is, of course, a tough one - Is the different implementation in mainline actually newer or older? Determining new vs. old in Samsung drops can be difficult - it may just be taking forever to mainline the additional stuff in Samsung's driver, just like the features just mainlined in 3.3 have been in Android kernels for well over a year.
Entropy512 said:
Not sure what codebase you're looking at, but in the I9100 source drop I've been working with, there was only mach-exynos, not mach-exynos4, and definitely not both.
Click to expand...
Click to collapse
My bad, after checking it must be codeworkx that merged it wrong (he put samsung on top of "stock" 3.0.15 to check the differences), I guess files weren't deleted.
Entropy512 said:
No matter what you name it, you're not going to be able to track mainline with this unless you sacrifice MASSIVE amounts of functionality (such as ditching support for any idle state deeper than WFI), because at least in this particular instance, mach-exynos in the Samsung drop is simply lightyears ahead of mainline.
You're going to have to either forget about bringing in mainline patches that touch mach-exynos for a long time, or accept a major reduction in functionality - no matter how you do it, mach-exynos needs to differ significantly from mainline to be even remotely useful.
Click to expand...
Click to collapse
I'm not talking specifically about mach-exynos implementation, but more all the other things that got touched around it.
Entropy512 said:
This one is, of course, a tough one - Is the different implementation in mainline actually newer or older? Determining new vs. old in Samsung drops can be difficult - it may just be taking forever to mainline the additional stuff in Samsung's driver, just like the features just mainlined in 3.3 have been in Android kernels for well over a year.
Click to expand...
Click to collapse
If copyright header is right, Samsung's one is 2009-2010 whereas 3.3 is from 2011. One example is that the Samsung driver uses mutexes and locks, which are not needed anymore and are not present anymore in mainline. This causes deadlocks everywhere when trying to use them in a "clean" kernel.
Posting this in the hope that it might help people who are rooted, but don't want to unlock and install a custom ROM due to the warranty issues, get the most out of their Primes. Also because this info is spread about around the forum and may not otherwise be that easy to find.
These are the 4 steps I took that made my Prime perform like I expected it should. Obviously all credit here remains with the people who did did the work to make these fixes. Thanks guys.
This is for the .21 firmware, but only step 3 should be firmware dependant, the first two should work regardless I think (tell me if I'm wrong).
1. Install this (thanks to TheOnionKnight):
http://forum.xda-developers.com/showpost.php?p=25286407&postcount=61
2. Install this (thanks to saturn_de) and select the cfq scheduler:
http://forum.xda-developers.com/showthread.php?t=1473520
3. Install this (thanks demandarin):
http://forum.xda-developers.com/showthread.php?t=1647357
4. Cold boot
After these steps everything runs smoothly, even when installing Apps from the Market, I never get a browser hang with the stock browser, all games work nearly flawlessly and I have yet to have a random reboot.
It goes without saying that YMMV, but hopefully this helps someone.
I have had my prime for about a month and have not heard anything about atp tweaks. Can you tell me why I need it?
I have all them on my Prime which help my Prime flying. There is a thread that MCCANDY started for limiting numbers of background process at most 1 to help your prime more stable.
Sent from my Desire HD using xda premium
whycali said:
I have had my prime for about a month and have not heard anything about atp tweaks. Can you tell me why I need it?
Click to expand...
Click to collapse
its a great app. its not necessarily needed but can improve your prime. first it allows you to change the I/O scheduler on prime. You can change it to Cfq, which will improve i/o performance on prime. In other words improve the lag seen from playstore apps installing from market while you doing other things on prime. The scheduler on prime is noop by default. there are other schedulers you can test out also.
then atp tweaks also adds modules/drivers for devices not supported by prime, out the box. other things it adds support for also.
best way to make it work like it should is take it out of the box and turn it on. No root needed.
everything else done like rom flashing, kernel flashing, atp tweaks, changing schedules, build.prop tweaks is all extra to make it work better.
demandarin said:
its a great app. its not necessarily needed but can improve your prime. first it allows you to change the I/O scheduler on prime. You can change it to Cfq, which will improve i/o performance on prime. In other words improve the lag seen from playstore apps installing from market while you doing other things on prime. The scheduler on prime is noop by default. there are other schedulers you can test out also.
then atp tweaks also adds modules/drivers for devices not supported by prime, out the box. other things it adds support for also.
Click to expand...
Click to collapse
Thanks, I am surprised nobody seems to talk about it. Even nobody in the sqlite thread has mentioned it. I was watching these boards for a couple of months before I got my prime. I knew there were problems but the solutions are the interesting part. If I wanted a tablet my 3 year old could use I would have kept my Ipad. I got a little burnt when I switched from my HD2 to an LG thrill just based on the specs. Great piece of hardware with no dev support and low interest from most people makes for a very dull device.
whycali said:
Thanks, I am surprised nobody seems to talk about it. Even nobody in the sqlite thread has mentioned it. I was watching these boards for a couple of months before I got my prime. I knew there were problems but the solutions are the interesting part. If I wanted a tablet my 3 year old could use I would have kept my Ipad. I got a little burnt when I switched from my HD2 to an LG thrill just based on the specs. Great piece of hardware with no dev support and low interest from most people makes for a very dull device.
Click to expand...
Click to collapse
Yeah, even though some on the other thread have said that the default noop scheduler is in theory better for these kinds of devices I find that the cfq scheduler does actually give a decent boost to responsiveness when the prime is trying to do background io.
whycali said:
Thanks, I am surprised nobody seems to talk about it. Even nobody in the sqlite thread has mentioned it. I was watching these boards for a couple of months before I got my prime. I knew there were problems but the solutions are the interesting part. If I wanted a tablet my 3 year old could use I would have kept my Ipad. I got a little burnt when I switched from my HD2 to an LG thrill just based on the specs. Great piece of hardware with no dev support and low interest from most people makes for a very dull device.
Click to expand...
Click to collapse
well the cfq sheduler improves the lag, but not 100%. maybe a combination of everything the OP stated does. its worth looking into but the new build is supposed to drop sometime this week, according to gary new update.
Yeah it's not completely flawless even with the cfq scheduler, but I do believe it is better.
The one I'm surprised that isn't more discussed is browser2ram. As far as I can see it's just buried on page 5 of a thread or something and for me it completely resolved the most annoying issue I had, which was the stock browser hangs.
just installed and did a quick test using cfq (after a reboot) installed 7 updates in record time. Hmm
---------- Post added at 07:27 PM ---------- Previous post was at 07:23 PM ----------
fatski said:
Yeah it's not completely flawless even with the cfq scheduler, but I do believe it is better.
The one I'm surprised that isn't more discussed is browser2ram. As far as I can see it's just buried on page 5 of a thread or something and for me it completely resolved the most annoying issue I had, which was the stock browser hangs.
Click to expand...
Click to collapse
It does make the other browsers usable, that's for sure. I hate the tiny font on the best browser (opera mobile) my corneas are hardening.
When the .28 update arrives, should we replace the modded build.prop with the stock one before updating? Or will we be okay to update with it?
whycali said:
Thanks, I am surprised nobody seems to talk about it. Even nobody in the sqlite thread has mentioned it. I was watching these boards for a couple of months before I got my prime. I knew there were problems but the solutions are the interesting part. If I wanted a tablet my 3 year old could use I would have kept my Ipad. I got a little burnt when I switched from my HD2 to an LG thrill just based on the specs. Great piece of hardware with no dev support and low interest from most people makes for a very dull device.
Click to expand...
Click to collapse
CFQ was actually noticed, however this has nothing to do with Sqlite.
In fact CFQ does not improve sqlite performance nor does it improve IO performance in terms of speed. OK it removes part of the lag when installing stuff an browsing the web. But at the end operations will take just as long since it just priorizes stuff differently.
what of step #3...? which build prop do i download. tried downloaded one directly onto the prime & it wouldn't allow me to unzip it. first two steps went great though. lol
Sent from my Transformer Prime TF201 using XDA
xTRICKYxx said:
When the .28 update arrives, should we replace the modded build.prop with the stock one before updating? Or will we be okay to update with it?
Click to expand...
Click to collapse
it should be fine but you can put back the original one to be on the safe side.
jussumguy88 said:
what of step #3...? which build prop do i download. tried downloaded one directly onto the prime & it wouldn't allow me to unzip it. first two steps went great though. lol
Sent from my Transformer Prime TF201 using XDA
Click to expand...
Click to collapse
if you running the stock rom, you download whatever version matches your prime. for example if your version is U.S., you download the first one. yes it is a zip file. you download it. then unzip it and the modded build.prop file should be inside. then make sure you put it in /system. But you do need root to use this mod and make sure to set permissions of new build.prop correctly. then make sure to rename old build.prop(by it looking like this"build.prop.bak") & backing it up to somewhere safe(just in case it needs to get pushed back in). then reboot and the modded build.prop should take effect. just make sure to read instructions in first post of my thread thoroughly.
but you might as well wait for update to drop. I will be updating that thread eventually with a build.prop that reflects the new update coming. if you don't plan on updating, feel free to try it out then.
Hello all, I am looking for a way to enable all cores on the Honor 5x. If you use Kernel Adiutor (and I'm sure you do) you'll notice that 99% of the time (save for a reboot) your little cluster is offline when using any AOSP ROM, now the only way I've found to enable them is to edit the value in the active file located in /sys/module/cluster_plug directory. The issue with this method is that it just enables them, 95% of the workload is still handled by the big cluster, even when it's straining itself the little cluster fails to pick up any of the workload. I have done clean installs of the Blaze kernel and the issue is still not resolved. Any incite into this issue will be greatly appreciated. Thanks.
You'll need to mess with:
/sys/devices/system/cpu/cpu0/core_ctl/min_cpus
/sys/devices/system/cpu/cpu0/core_ctl/max_cpus
/sys/devices/system/cpu/cpu4/core_ctl/min_cpus
/sys/devices/system/cpu/cpu4/core_ctl/max_cpus
It takes integer value ranging from 0-4. 0-4 meaning how many cores you want online per cluster.
The only issue is that I don't have /core_ctl directory that you've specified, I don't recall ever having it on this ROM, though I could be wrong. I'm using the krexus ROM in case I hadn't specified before.
I know, reading the stock ROM forums I got very excited to see the before mentioned information that was posted only to see that said (/core_ctl) directory was missing from any AOSP ROM I had used. This is the one thing that is holding me up from giving up my Windows phone as my business phone (the lag as a result of only being able to use 4 cores is intolerable in my line of work) even giving a link to what all these directory files mean would be very helpful. Thanks.
You could google what those directory means and that would give you that answer.
I have done this (and I consider myself well versed in the ways of the interwebs and I rarely come up with anything useful but I've been working on a solution for my original question and feel I am close to achieving it. I will post once I do.....though if anyone has ANY suggestions at all I'm open to try, all of my discoveries have been made through trial and error.
tboned82 said:
I have done this (and I consider myself well versed in the ways of the interwebs and I rarely come up with anything useful but I've been working on a solution for my original question and feel I am close to achieving it. I will post once I do.....though if anyone has ANY suggestions at all I'm open to try, all of my discoveries have been made through trial and error.
Click to expand...
Click to collapse
You may be needing a custom kernel to achieve this successfully.
Sent from my honor 5X using XDA Labs
adriansticoid said:
You may be needing a custom kernel to achieve this successfully
Click to expand...
Click to collapse
I can't recall if I mentioned it or not but I'm using the blaze kernel at the moment (as far as I know it's the only custom one available for this phone?) Also the CPU control I desire is available inside the stock KIWI ROM, just wish I knew of a way to "port" that hotplug to a AOSP ROM.... thinking SELinux policy is prohibiting me from achieving the CPU control I'm after, but not sure if it's the only thing at play when it comes to this issue.
tboned82 said:
I can't recall if I mentioned it or not but I'm using the blaze kernel at the moment (as far as I know it's the only custom one available for this phone?) Also the CPU control I desire is available inside the stock KIWI ROM, just wish I knew of a way to "port" that hotplug to a AOSP ROM.... thinking SELinux policy is prohibiting me from doing this, but not sure if it's the only thing at play when it comes to this issue.
Click to expand...
Click to collapse
Have you joined the beta channel of Blaze in Telegram?
adriansticoid said:
Have you joined the beta channel of Blaze in Telegram?
Click to expand...
Click to collapse
I have not, but would be very interested, what is Telegram?
tboned82 said:
I have not, but would be very interested, what is Telegram?
Click to expand...
Click to collapse
It's a messaging app. Just like Whatsapp, but with some diferences. You can check it in the Play Store. Telegram group link is in the Blaze kernel thread.
Wow thank you, I dirty flashed it (since version 2 dirty flashed fine) and didn't have pleasing results, going to do a clean flash AOSP, but those hotplug features are exactly what our phones need! Who's ready to hunt down some flagships?
tboned82 said:
Wow thank you, I dirty flashed it (since version 2 dirty flashed fine) and didn't have pleasing results, going to do a clean flash AOSP, but those hotplug features are exactly what our phones need! Who's ready to hunt down some flagships?
Click to expand...
Click to collapse
You didn't have screens of death?
Sent from my honor 5X using XDA Labs
tboned82 said:
didn't have pleasing results
Click to expand...
Click to collapse
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
alpinista82 said:
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
Click to expand...
Click to collapse
Yeah the developer have not seen action the past few weeks.
adriansticoid said:
You didn't have screens of death?
Click to expand...
Click to collapse
I apologize for my absence, I really hate being that "guy" but all my free time has been devoted to tracking down a nasty electrical gremlin in my sister in laws car, but no I have never had any adverse effects from dirty flashing anything really
alpinista82 said:
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
Click to expand...
Click to collapse
I currently have blaze kernel installed and using the method I've mentioned before am able to enable all cores, but with very poor load balancing, and the beta version is far from RTM at the moment so guess I'm stuck with version 2 for the time being.
adriansticoid said:
Yeah the developer have not seen action the past few weeks.
Click to expand...
Click to collapse
I have noticed this as well, which is unfortunate because the dev seems like a very talented coder who is quite capable of the task at hand, sometimes life gets in the way of the things we would like to do so I'm just going to be patient and hope he picks back up on the project.
tboned82 said:
I apologize for my absence, I really hate being that "guy" but all my free time has been devoted to tracking down a nasty electrical gremlin in my sister in laws car, but no I have never had any adverse effects from dirty flashing anything really
I currently have blaze kernel installed and using the method I've mentioned before am able to enable all cores, but with very poor load balancing, and the beta version is far from RTM at the moment so guess I'm stuck with version 2 for the time being.
I have noticed this as well, which is unfortunate because the dev seems like a very talented coder who is quite capable of the task at hand, sometimes life gets in the way of the things we would like to do so I'm just going to be patient and hope he picks back up on the project.
Click to expand...
Click to collapse
It's been that story for many developers man. A great project paused because life hit hard again. I believe he'll come back to it soon.
tboned82 said:
Hello all, I am looking for a way to enable all cores on the Honor 5x. If you use Kernel Adiutor (and I'm sure you do) you'll notice that 99% of the time (save for a reboot) your little cluster is offline when using any AOSP ROM, now the only way I've found to enable them is to edit the value in the active file located in /sys/module/cluster_plug directory. The issue with this method is that it just enables them, 95% of the workload is still handled by the big cluster, even when it's straining itself the little cluster fails to pick up any of the workload. I have done clean installs of the Blaze kernel and the issue is still not resolved. Any incite into this issue will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
methuselah said:
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
Click to expand...
Click to collapse
Drains battery like hell. Lol.
Sent from my Galaxy Tab 3 using XDA Labs
methuselah said:
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
Click to expand...
Click to collapse
I had thought of doing this, though I don't see any cm 12.1 links in the Honor 5x thread, just 13, (though I'm at work at the moment and have to be stealthy about my research...errgghh Damn kids and their Snapchat) and I have to admit I've kind of fallen in love with the Krexus ROM and am apprehensive to flash another. Just need that hotplug support (and OTA updates would be nice as well