When using a kernel that has cpu1 enabled, the cpu1 scaling_governor will be reset to userspace at random intervals. I haven't been able to figure out a pattern for it, but has anyone else noticed this behavior, or have an idea of how to prevent it?
On a related note, the permissions for cpu1/cpufreq on startup are really weird too (440 for scaling_max_freq and scaling_governor), but I can manually fix those after a reboot...
hboot: 1.40
root: revolutionary
ROM: stock 2.08.651.2
kernel: freeza 4a or bcblend 0.03
If any other info would help please let me know. Thanks in advance.
penguinicus said:
When using a kernel that has cpu1 enabled, the cpu1 scaling_governor will be reset to userspace at random intervals. I haven't been able to figure out a pattern for it, but has anyone else noticed this behavior, or have an idea of how to prevent it?
On a related note, the permissions for cpu1/cpufreq on startup are really weird too (440 for scaling_max_freq and scaling_governor), but I can manually fix those after a reboot...
hboot: 1.40
root: revolutionary
ROM: stock 2.08.651.2
kernel: freeza 4a or bcblend 0.03
If any other info would help please let me know. Thanks in advance.
Click to expand...
Click to collapse
very interesting issue...
cpu1 scaling governor reset to userspace at random intervals .. the first guess i'd have would be some 3rd party android app following a predefined profile. of course, this app should need root access to echo out to the sysfs file and if you have superuser installed the app would have had to prompt at least once for permission.
if you don't have any 3rd party app installed echo'n values then the only other common tool i've seen is the settings in CM7, but you stated you're on a stock ROM.
if you're on a rooted stock ROM with custom kernel, sometimes the devs setup support for startup scripts and might be making some type of tweak in a startup script which could also be set to loop and apply some predefined setting.
my guess would be the perms on sysfs files are setup in the kernel config files when its compiled. would be something the kernel dev should be able to change easily. 440 could be intentional as they're trying to limit access .. don't want any random app/binary messing around with the settings
hope some of those thoughts are helpful!
joeykrim said:
very interesting issue...
cpu1 scaling governor reset to userspace at random intervals .. the first guess i'd have would be some 3rd party android app following a predefined profile. of course, this app should need root access to echo out to the sysfs file and if you have superuser installed the app would have had to prompt at least once for permission.
Click to expand...
Click to collapse
Here are the programs with superuser permission:
BusyBox installer
ConnectBot
Kernel Manager Lite
Quick Boot
ROM Manager
Superuser
Titanium Backup
All of these are pretty common, and I doubt any of them would be poking around the governor, but that's why I'm asking after all.
joeykrim said:
if you're on a rooted stock ROM with custom kernel, sometimes the devs setup support for startup scripts and might be making some type of tweak in a startup script which could also be set to loop and apply some predefined setting.
Click to expand...
Click to collapse
Do you know how I could check this? I don't think the kernel has init.d support.
joeykrim said:
my guess would be the perms on sysfs files are setup in the kernel config files when its compiled. would be something the kernel dev should be able to change easily. 440 could be intentional as they're trying to limit access .. don't want any random app/binary messing around with the settings
Click to expand...
Click to collapse
Yeah, definitely makes sense. It was just odd to me that the CPUs were mismatched (cpu0 had 640 permissions for all of those).
joeykrim said:
hope some of those thoughts are helpful!
Click to expand...
Click to collapse
Definitely, thank you.
I've worked around it for now by modifying Virtuous OC to set the perms to 640 before doing its thing, then resetting them to 440 when done. I've also written a daemon that will report when it's changed to userspace in hopes that I can track down some sort of pattern.
penguinicus said:
Here are the programs with superuser permission:
BusyBox installer
ConnectBot
Kernel Manager Lite
Quick Boot
ROM Manager
Superuser
Titanium Backup
All of these are pretty common, and I doubt any of them would be poking around the governor, but that's why I'm asking after all.
Do you know how I could check this? I don't think the kernel has init.d support.
Yeah, definitely makes sense. It was just odd to me that the CPUs were mismatched (cpu0 had 640 permissions for all of those).
Definitely, thank you.
I've worked around it for now by modifying Virtuous OC to set the perms to 640 before doing its thing, then resetting them to 440 when done. I've also written a daemon that will report when it's changed to userspace in hopes that I can track down some sort of pattern.
Click to expand...
Click to collapse
Okay, well given some of your responses I'm going to assume you're a bit more of a technical/advanced user.
All the Android applications you posted with superuser access are very common as you stated. An easy way to check might be, rename /system/bin/su to something else so no scripts or apps can gain superuser access and see if your sysfs cpu1 files are still changed?
If I were you, I'd want to get to the bottom of the perms on the cpu1 sysfs files. Especially since you're saying cpu0 and cpu1 have diff perms set on the sysfs files. Since Linux kernel code is GPL, the kernel dev should have a public link to their kernel files. I'd go look thru their source to find where they're implementing cpu1 sysfs files and check the perms they're setting up sysfs files with. I want to say, the cpu1 sysfs files are something added/modified by the kernel devs so there is definitely potential somebody missed a proper setting.
I'd rather take this approach than have to patch over some poor coding by using another app to adjust the perms on the file.
Can you post the log produced by your daemon on the changes to the sysfs cpu1 file?
Hope that helps!
EDIT: noticed I missed a question, how to check for init.d type support in the kernel. Generally, they're going to have to make a change to the init.rc file in order to add in anything to the start up sequence. I'd grab the stock init.rc file and diff against the currently loaded init.rc file in the kernel being used.
As an FYI, init.rc is stored in the ramdisk part of the boot.img.
Whew, ok. After a lot of observation, I noticed that the reset to userspace corresponded with me putting the device to sleep.
I then tried disconnecting my device from USB and the daemon started crashing, being unable to read the sysfs files for cpu1, which never happened while connected over USB. I switched adb to TCP mode and found that the files were indeed gone, because cpu1 was offline. Apparently being connected over USB kept cpu1 online more often than it would be otherwise. This was causing some weird permission resets too, as the permissions would reset when the core was brought offline and back online.
When cpu1 is automatically taken offline then back online, it seems to be randomly restored with the userspace governor instead of whatever governor it had when it was taken offline. It sometimes gets stuck online, too, even when the phone has been asleep for a long period of time. I still can't get either to happen consistently, however, and I don't know if nobody else is experiencing it, or if it's just gone unnoticed by others.
Enabling and disabling SetCPU seemed to have no effect on the consistency or frequency of the weirdness either. I may mess with my daemon to have it duplicate cpu0's governor to cpu1 when cpu1 comes online but doesn't match, but I have to assume this is just weirdness due to the whole "async cores are new" thing.
Thanks very much for your help, and if anyone else observes anything similar please let me know! D:
penguinicus said:
Whew, ok. After a lot of observation, I noticed that the reset to userspace corresponded with me putting the device to sleep.
I then tried disconnecting my device from USB and the daemon started crashing, being unable to read the sysfs files for cpu1, which never happened while connected over USB. I switched adb to TCP mode and found that the files were indeed gone, because cpu1 was offline. Apparently being connected over USB kept cpu1 online more often than it would be otherwise. This was causing some weird permission resets too, as the permissions would reset when the core was brought offline and back online.
When cpu1 is automatically taken offline then back online, it seems to be randomly restored with the userspace governor instead of whatever governor it had when it was taken offline. It sometimes gets stuck online, too, even when the phone has been asleep for a long period of time. I still can't get either to happen consistently, however, and I don't know if nobody else is experiencing it, or if it's just gone unnoticed by others.
Enabling and disabling SetCPU seemed to have no effect on the consistency or frequency of the weirdness either. I may mess with my daemon to have it duplicate cpu0's governor to cpu1 when cpu1 comes online but doesn't match, but I have to assume this is just weirdness due to the whole "async cores are new" thing.
Thanks very much for your help, and if anyone else observes anything similar please let me know! D:
Click to expand...
Click to collapse
I've noticed the exact same thing on my E3D. I'm running a "clean" custom ROM (CleanROM DE) with a famous third-party kernel (Tiamat Sense 1.1.0). I've also noticed that there is a lot of work in the Sensation forum trying to get the "Dual-Core" mode "unlocked" and that some ROMs have managed to pull it off. I think having a talk with any of these developers (or anyone who boasts "Dual Core" or "dual core patch") would help you get to the bottom of this.
It's extremely frustrating. Even using apps like System Tuner Pro, which have a special option to "force all CPUs active", does not seem to correct the sporadic governor switching back to userspace on the second core.
---------- Post added at 04:33 PM ---------- Previous post was at 04:12 PM ----------
curiousGeorge said:
I've noticed the exact same thing on my E3D. I'm running a "clean" custom ROM (CleanROM DE) with a famous third-party kernel (Tiamat Sense 1.1.0). I've also noticed that there is a lot of work in the Sensation forum trying to get the "Dual-Core" mode "unlocked" and that some ROMs have managed to pull it off. I think having a talk with any of these developers (or anyone who boasts "Dual Core" or "dual core patch") would help you get to the bottom of this.
It's extremely frustrating. Even using apps like System Tuner Pro, which have a special option to "force all CPUs active", does not seem to correct the sporadic governor switching back to userspace on the second core.
Click to expand...
Click to collapse
Oh. HTC's doing. My bad.
http://forum.xda-developers.com/showpost.php?p=17456447&postcount=7630
Of course, flashing this sucker could cause you to wind up with a bricked phone. Beggers can't be choosers. Now I'm off to flash Synergy. *sigh*
WOW, thanks for this info. That makes a lot of sense actually, I notice blazing performance for the most part on tiamat 1.1.0, and then out of nowhere it's slow as balls. Reboot *seems* to fix. I guess it's stock for me with a modified ramdisk, no OC, but that's cool. The shooter is pretty damn quick.
If any of you folks come up with something that corrects the userspace gov issue and perms, please post, I would like to use it. Thanks again.
Was having the same issue, looked all over and found a solution
http://forum.xda-developers.com/showpost.php?p=17456447&postcount=7630
Keep in mind these are flashable solutions as long as you stick with the same scaling_governor. Its been said to have both cpu's running same one.
Related
About a month ago some of you may remember my posts that I was working on a kernel. Here is my first public release. The whole thing works at about 95% or so.
==============
The advantages I notice while using it besides the normal issues associated with Eclair are as follows:
1. Memory management has changed (has good and bad effects) Good: when you fly through 45 websites the browser does not crash as it eats memory. Bad: when you blow through 45 websites the browser will hang (easy fix hit home, and use app killer to free memory from apps you are not using) (Personally I like not losing my place as I get lost in the web, it also will prevent apps from dieing in the background when you are using multiple apps at the same time, if memory gets low enough the OS WILL KILL the offending apps). I personally found Eclair for Fascinate to handle memory available worse than this kernel, and I find this kernel handles memory more like Eclair on the Moto Droid did, and the Moto Droid had far less memory to work with.
2. UI has a faster response vs stock kernels, the kernel is also running AS scheduling vs BFQ but I updated BFQ to run as well if you want to revert.
3. Internet Connectivity appears to be faster with those apps that properly use the API. Web browsing, CheezeBurger, youtube etc all load content faster (efficiently? / Maybe related to memory management?)
Want something added to this list? Post your requests, just please be reasonable If I like the idea I will try to implement it. Remember this is for kernel features not system ROM modifications.
==============
Issues to fix (ToDo List, I am working to fix these issues / Updated 01/30/11):
1. Investigate and address bluetooth connection issues [ Confirmed that this issue does not affect everyone / or all bluetooth devices ]
2. Investigate and address remaining data connection issues (Orbot activates and test show as using tor on normal websites, tor addresses fail to connect to servers, also Orbot is unable to de-activate [Confirmed]
3. Investigate and address remaining camera crash issues [ Please zip and send in logs from /proc/kmsg, specify if you used the volume control zoom or pinch to zoom ]
4. Improve on touchscreen timing for quick flicks on the first attempt without burning up processor time.
5. Investigate and fix stutter/crash on camera zoom followed by attempt to take photo.
Notice something that should be in this list? Please make a post describing your issue, remember to include the kernel version/rom and the steps you performed to reproduce the issue.
==============
For those doubting, this IS 2.6.29.6, I personally merged the code myself, IT IS NOT 100% COMPLETE. Some drivers still need merging, and the V4L2 code is not completely converted because Fascinate uses different (updated?) V4L code (compare Fascinate's Eclair to Eclair on AOSP)
If anyone wants to help bug hunt I will forever be grateful. I would like to finish squashing bugs in this in the next 2 weeks as I really want to attempt to work on a Froyo for Fascinate. Even if it uses Eclair code to run the only RIL code we have.
I also semi-blindly fixed about 50-100 coding problems in the Eclair Kernel, varied from not returning data from a function that should have, simple void definitions that were returning when they had no data to return and no function collected it. Correcting order of operations in if statements. Declaring data types that were vague (unsigned vs signed). You will notice it compiles a lot cleaner...attempting to fix the camera code nearly kills the camera completely, I am thinking the broken code dumps variables by accident that the corrected code does not.
Edit: I wanted to share a few things every dev (some of it specific to kernels) should remember when nights are long and sleep is a half world away.
1) Keep a backup of your most recent WORKING work safe, because it is too easy to....uh oh *[email protected]$
2) If you edit the config file, remember to make clean and make mrproper before you make, otherwise your still on your original config file (a copy of the one you actually edit .config)
3) Do not put comments to the right of options in the kernel config file...apparently they will be discarded (the entire option line, not the comment, you'll see it in your compile error message logs).
4) Automate the mundane, I have a nice build environment setup, I type one line and it will make a brand new kernel from scratch (I'll be sharing that later, keep an eye on this post)
5) Work with what you have, don't wait for someone else too. Somewhere, someone is working on something better, and tomorrow it will be out.
6) Laugh...at something...anything because lets face it, you make better decisions in a good mood, in a bad mood...entire trees (code) die, either from rm -Rf /work/crap//* or a sledgehammer to the motherboard. Which brings us back to the first thing to remember, where did you put that backup...different drive I hope?
Attached is a working kernel, it will have issues using DI01 (such as no vibrations), it works great with DJ05 ROMS and maybe DL09 system roms. At this time I can not recommend a DL09 system rom with this kernel, during my initial tests it appears to drop GPS and cell data connectivity frequently resulting in having to relock on GPS satillites, and losing data connections in networked applications.
I highly recommend the setup I am running, DL09 Radio, Son Of Skywalker Blackhole v2.4 and this kernel (if you can handle the few bugs that is, it is beta).
Please feel free to post bug reports please include detailed information about the issues, I AM NOT FIXING APP PROBLEMS. Please remember to only report kernel issues and information specific to the kernel crash. If an app crashes on other kernels and not just this one please do not submit a report. This kernel is NOT setup for debug info, I will post one setup with debug turned on later. Right now, play around with it and report your results! Enjoy and have a great time :-D
GITHUB: https://github.com/sirgatez/
Edit 1: I thought I would mention that I originally started with the JT1134 kernel source from late Nov. - mid Dec. and the Samsung Fascinate stock source (from Samsung's Opensource website) then I merged in source from 2.6.29.6 from www.kernel.org and from Cyanogen's 2.6.29.6 Eclair kernel. I stopped on 2.6.29.6 instead of moving higher because of 1 reason, once you step in to 2.6.30 there are major driver changes requiring a lot of double verification and back trekking....In a few words, it is lots and lots of work, and I think that jumping from 2.6.29 to 2.6.29.6 will help transition to the 2.6.30 (Froyo?) series of kernels because then the majority of the work is in restructuring the driver code (which would likely best be done backwards, from the system .h files, to the .c handlers, down to the device drivers) from Samsung to match that in the stock 2.6.30 set. Complexity will be reduced by a measurable amount
Notes 1: Samsung's Android code has some significant differences under the hood from AOSP Android code, I have not sorted it all out yet, but it is possible that without an AOSP stock system that a full kernel update to the current AOSP code may not be possible. There is a built in virtual CD driver for what appears to be hosting the ISO built into the base Samsung system image, I have not opened the image yet but it appears to perhaps be drivers? Also it does not sleep the SD card like standard AOSP does, attempts to do so will disable the SD card from use with no ability to remount without a battery pull. (This is in 3 of 4 lines of code that AOSP had that must be commented out from the Samsung kernel for this SD issue to be prevented). For those wanting it, CIFS and NFS are compiled modules in this kernel. The current kernel is not over-clocked, and does not have voodoo. It does support both with a kernel configuration edit required for voodoo with the proper init scripts, and over-clocking requires changing just a few files and recompiling, I did neither as I wanted a true comparison to compare changes against the original stock kernel. The kernel does have the BLN notification code built in. BLN, Voodoo, and Over-clocking code are not my own creation they are pulled from their respective creators.
REMOVED ALL OLDER KERNEL INFORMATION
Update RC3 v2.2.4-VooDoo/NoVooDoo: This is a minor/major (depending who you ask) bug fix to adjust the processor throttles. Think I've got it too set to a good sweet spot now, the peaks are steep and a little harder to climb but the falls are also quicker. After turning it my phone on with it last night and about 2 hours of use I went to sleep, wake up a couple times to silence various alarms (I wake to wake up, but I want to sleep a little more, can't I do both?), and these are the numbers that setcpu reports for time in state:
1.2Ghz = 0 (Had the phone thottled to 1.0Ghz for this test, but with 1.2 on it only uses it when it needs it, might could leave it on?
1.0Ghz = 164978 (Not such a big a number as before)
0.8Ghz = 292008 (much more reasonable than before, could be a little lower)
0.6Ghz = 117672
0.4Ghz = 114250
0.2Ghz = 104715
0.1Ghz = 2965562 (This is what I was aiming for proportionally for 0.1Ghz)
Remember these times are mostly from idling, the idea was to reduce clockspeed when not in use to save some juice. The phone might take a moment to wake up from idle, but once it is going you shouldn't feel hardly any difference between this and RC2. Bootup clockspeeds from your first 3-4 minutes will almost always remain in the top tier due to applications still loading, media scanner running, etc.
Update v2.2.4-VooDoo/NoVooDoo: This is a major fix kicking us out of RC status and into actual release. Now for the menu, prepare your appetite, for the appetizer we'll be serving a much demanded voodoo color fix, and voodoo sound fixes. Followed by a main coarse of throttle tweaks, throttle shift updates (these are new they decide what the next cpu speed will be when a throttle is exceeded up or down, every kernel to my knowledge including my last used the default for a 5 slot kernel, here is a true 8 slot), and for desert a reduction in logged touch screen data from the touch screen, and an additional surprise to everyone, a reduced cpu load when using the touch screen!
Apparently the touch screen had authority to force the cpu into any slot it wants, it defaulted to slot 1 (which was 1.0Ghz for Blazed, now it's 1.2Ghz). The result of which meant that if you pressed the touch screen your cpu load catapulted up to 1Ghz for as long as you touched it even if you only held your finger in one place with no apps open. I have changed that to only go to 400Mhz, we'll see how this goes, if anything we might bump it to 600Mhz, so far besides a slightly slower response when first touch my touchscreen after leaving it alone for a long period it doesn't effect normal use from one app to another. If your processor is already at 400Mhz or higher it will not up it further. You will find this kernel will likely end up being the most battery conscious you have ever seen, once you get things moving the speed follows. If you find this kernel has a slower response than you feel it needs let me know, because when I fixed the touch screen from blasting the cpu load through the roof, it through off my throttle settings some, now they may be too conservative, report back and we'll fix them if it is a problem. Ah yes, please don't forget to tip your waiter if you enjoyed the service... [ REMOVED - Aggressive throttles not configured for use without aggressive touchscreen driver ]
Update v2.2.4R2-VooDoo/NoVooDoo: This is a minor fix to correct the choppy feeling that v2.2.4 had, the choppiness was due to aggressive throttles to fight off the excessive high speeds the touch screen forced on. This should correct those issues. Unless I have another bugfix for 2.2.4, I will be adding 1.1Ghz in the next release making it a total of 9 slots. The higher speeds still need some tweaking, if your looking to hit benchmarks please set min and max to the speed you are testing, otherwise the throttle is trying to save you power that doesn't need to be used. But for everyday use, these settings should be good
Update v2.2.5-VooDoo/NoVooDoo: Voodoo sound is still broken, anyone have the patched files I could compare to? The screen should be about 15% dimmer than it usually is on the lowest setting (and scaled up from there to 100% at max), I found the dimmest setting just too bright in the dark for my self, and hopefully it will help me save a little extra juice because I usually use my phone on the lowest brightness setting anyway. Major fix to throttles, now they are better tailored to this many slots. Slots updated to 9, 100Mhz, 200Mhz, 400Mhz, 600Mhz, 800Mhz, 1.0Ghz, 1.1Ghz, 1.2Ghz, and 1.3Ghz. Increased processor voltages (my ultra low voltage was about 25uv lower in most slots than everyone else who has a uv kernel...I was a little too aggressive on that one). Update bluetooth driver, it should remain connected now, could someone please verify this? Stability has improved alot with the higher voltages and better handling of throttling for different situations. Several other pieces of hardware discover that have authority to play with processor. I capped highest touch screen processor forced at 600Mhz (the higher I set it the faster your battery goes, default stock is 1Ghz), and all other hardware at 1Ghz (not very many requests, but this is where rouge 1.2 use came from). If you had issues before except for camera zoom or data connectivity in apps give Blazed another try. The slightly higher voltages should improve a lot of the random issues people were having. You may see an improvement in cellular signal now, 1.3Ghz is also stable, but I wouldn't run it all day either due to heat generated etc...Well I hope everyone enjoys, this should be the best release of Blazed Yet!
Update v2.2.6-VooDoo/NoVooDoo: This is a major fix for cellular signal issues many people have been having, the issue again was related to timing and the kernel modules not waiting long enough for the modem to respond before proceeding with action resulting in errors that caused a disconnect or forced a modem reset (requiring a phone reset to regain signal). I found waiting too long only slowed the entire phone down, so I opted to go with nanosecond wait times, waits that short however are active and will warm the phone up some, please report back if it becomes an issue as I am looking for a better wait device than udelay, preferable more like sleep that doesn't keep the processor busy. There is some performance stutter in the phone on the high end of internet connectivity speeds, but your not going to be losing your connection either, I'll continue to attempt to improve on this issue later on. [ REMOVED - Timing further improved in v2.2.7 ]
Update v2.2.7-VooDoo/NoVooDoo: This is a minor for that makes a major difference. Improved timing for communication with GPIO/modem this should be the end of the majority of network connection issues. It was entirely a mailman problem, put package in box, check for package, package still there? no=do other stuff/yes=...wait,repeat at package still there?, etc. The fix is put package in mailbox, wait long, check is package still there? no=do other stuff,yes=short wait and check again...Hope this helps alot of you out, I am aware the touch screen is a little slow to respond and I will be looking into that issue. This little fix should also improve usable speed over v2.2.6 because the waits are better timed.
Update v2.2.8-VooDoo/NoVooDoo: Timing is everything with electronics and this post...as promised today before 11:59pm is v2.2.8. Working Voodoo Sound v4, updates to the dpram/dpio communications again improving connection stability, if you lose your connections please report back (permanent loss requiring a restart only, fluctuations are different issue). Throttles set a little more aggressive about 5% so (helps ease on light loads), stepped up the first throttle jump from 100mhz to 400mhz (touch screen snaps back now). Dropped the 1Ghz permission for misc hardware to 400mhz if you have issues let me know, touch screen retains it's 600mhz permissions. Also screen brightness is reducible to gamma 1 brightness 10, typically reserved for battery about to fail status (I found the lowest setting just too dang bright). Enjoy everyone! I've been hammering away on this since 7am this morning and only had voodoo sound working about 9am. Thanks to JT1134 for his prebuilt kernel containing voodoo sound v2 working, adding v3 & v4 was a snap after that. Please report if you have any issues with it and remember you MUST be using the new voodoo sound app from the market.
Update v2.2.8R2-VooDoo/NoVooDoo: Another dpram timing adjustment (will lower your upload speed a little but will be more stable in operation, down speeds should be around 200KB down 44KB up on a good connection). Adjusted 1.1Ghz dividers per nemesis (not sure that it looks right, appears to get better benchmarks than 1.2 now will follow up on it). Made throttles a little more aggressive, 2.2.8 looked all over the place and having difficulty controlling processor use.
Update v2.3.0-VooDoo/NoVooDoo: Alot of work went into fixing dpram.c and multipdp.c it seems they were incompatible from the very beginning resulting in alot of ril issues and stability problems not just on my kernel but others as well, especially with nonstandard clocks and multiple slot kernel. I also added a fix to the framebuffer courtesy of JT1134 that has long since been overdue but a rare bug most probably have never seen. I fixed all the timing in dpram.c I also fixed the non-matching buffer sizes for multipdp and dpram (they talked to each other using different sized buffers...come on?!) There are still some bluetooth compatibility problems and the camera may still crash on zoomed photo, but I'd say it's 100% out of Beta! Enjoy! :-D I will be working on a Froyo kernel so stay tuned folks!
Update v2.3.0R2-VooDoo/NoVooDoo: Minor fix to help prevent dpram crash by handling and disposing of invalid commands sent to dpram, should fix seeming random lockup. [ Edit: corrected incorrect version numbers in original v2.3.0 series xda posts, thanks to s44 who caught the error, this does not affect kernel downloads, this were named correctly ]
Update v2.3.1-VooDoo/NoVooDoo: I reduced the delays in the ce147 camera driver, repairing the dpram driver resolve many of the seemingly random issues that had once plagued Blazed. Also a special treat for all you Blazed users, a new voodoo sound option that I have named "HEADPHONE_STICK" essentially the option when enabled (per boot) will force all audio directed to the external speaker to be instead directed to the headphone jack if the headphone jack has a plug in it. I find it excellent for not disturbing others around me with notifications when I would rather the phone be silent but I have headphones plugged in. Also excellent for using that awesome amp you have in combination withr you fascinate to wake you up in the morning. I will be contacting the maker of the Voodoo sound app in the market to get this option added to his application for quick and easy access. Also a major rework in the way kernel modules are loaded, all modules non-essential to booting are now stored in /system/kmodules. So if you reflash your system folder reflash your kernel or it may not boot, a quick browse will reveal what modules are kept there, I have more readily compiled and will release a separate "modules only" update.zip for those interested. By moving the modules it will allow for more options that are only available for including in the kernel boot image.
Update v2.3.1R2-VooDoo/NoVooDoo: Reverted some of the CE147 delay changes, reducing all of them caused some minor camera instabilities. EXT3/EXT4 moved back into the kernel, for some reason even with it's depends loaded ext4 doesn't load correctly as a module (resulted in broken boot on voodoo, now fixed). Also You MUST USE RED CLOCKWORKMOD TO FLASH IF USING VOODOO, you may use green clockwork only if Voodoo is NOT enabled due to the fact that some modules required for bootup are now stored on the system partition and if your using Voodoo only red clockworkmod has access to it. Also if you flash a different system or restore a backup you must reflash the kernel to ensure your modules are up to date. Also is a new file KMODULES-FULL contains all of the modules I have been compiling for Blazed thus far, several nifty ones but I have not setup any of the configs to use them, anyone versed in Linux command line can utilize them or setup scripts to use them, have a look inside the zip too see what there is to play with, request and I will add more if the module could prove useful to others. Several of the modules in FULL are also in the Kernel due to being required for startup redundancy (such as the 3D video/LCD drivers etc, which without a Android system folder, Android won't boot, nor will it boot without these modules so system seemed like a reasonable place to store them. The kernel/initramfs file is less than 6MB with Voodoo due to moving these modules to the system folder. I plan to add ClockworkMOD as soon as I have time to test it, then Blazed will also work for Recovery.
The Great Voodoo Debate: I have also been benchmarking Blazed against stock, to determine the difference Voodoo has on the kernel, so far it would appear Blazed has modifications either in the file system handling or the manipulation layers that are nearly equal to negating the speed lost to RFS's use before Voodoo or EXT4 is even brought into the equation. Just compare Stock vs Blazed (novoodoo) using 'RL Benchmarks SQLite Performance" from the market. A difference of 33.246 seconds in favor of Blazed, my preliminary results are (124.944 Seconds Blazed-NoVoodoo) (158.19 Seconds Stock) using the same exact system install less than 20 minutes apart between boots, with over 300 applications installed and several running like any other day. Based on this alone I find Quadrant is at least partially flawed at measuring proper I/O transfer timing, and I would NOT rely on it for an accurate benchmark in regards to I/O at this time until the issue is resolved by the Quadrant team. Voodoo does not produce the outlandish high scores that Quadrant makes out that it does, and Blazed is plenty fast in I/O even with RFS in use as shown by these preliminary results that any one of you can verify on your own using the "RL Benchmarks SQLite Performance" application, Voodoo does improve transfer compared to RFS in my tests but I am still putting together the results on Blazed NoVoodoo vs Blazed Voodoo. But as far as a 1800+ or 2000 score, so far my results say it just doesn't look realistic...sorry guys. On the flip side, if there is an error in my kernel causing a misread on the score you guys are welcome to help me find it and I will push the correction, but right now it looks like the issue is in how Quadrant measures I/O time, and I think non-atomic disk writes are the reason for the high scores, theoretically they would return claiming data is written to disk almost immediately when in reality it is still in memory and the kernel will write it to the disk at later time without the write time being considered as part of the benchmark (Google: write-caching, also known for providing significant performance improvements over atomic-writes).
If you appreciate Blazed and enjoy using it, please consider making a donation. Thank you for trying it out and have fun!
My initial impression after playing around with it for 15 minutes:
Seems to have given my phone new life/snappiness back that it had when I first installed super dark rom and stupidfast 1.54. My phone seemed to be bogging down lately. The internet definitely feels quicker too.
So far so good!
will try, thank you for the release.
Great work!
Sent from my Galaxy-S Fascinate
I don't want to turn you away from your work, but have you considered heading over to IRC and joining the guys working on Gingerbread? I'd assume that the more competent people working on it, the better.
Great work, the kernel seems to have given new life to my test fascinate! ADB does however appear to be dead (I got error device not found every time I tried to connect) Other than that I have no complaints, keep up the good work
That is very odd, as I have not had any issues using adb. Please reload your drivers to be safe and double check debug mode has not accidently become disabled. I wired up my fascinate just now and confirmed that ADB is working. (It was invaluable in working with the camera crashes). Also it maybe related to a conflict in the system rom vs the kernel. I personally have not have any issues with DI01 Fascinate stock, and everything worked great using DL09 radio, DJ05 system from SonOfSkywalker (BlackHole 2.4). Right now I am running DL09 Radio, DL09 System Rom from SonOfSkywalker v3, and my kernel from this post, thus far no issues. I am using Ubuntu v9.04 to test right now, and not windows to confirm that ADB is working. I will check on windows later today when I have a chance.
anyone else having an issue with bluetooth? It says "Turning On" but does not turn it on just reverts back to "off" status.
I still have DJ05 modem and on blackhole 2.3 something but updated market and swype maunally.
Camera force closes when you go to zoom in.
Sent from my SCH-I500 using XDA App
I assume disabling voodoo would be a prerequisite to installing this kernel? Though I'm curious what partition scheme are you using for this? Is it using samsung's default filesystems for /system /data etc?
EDIT: Forgot to say, this is re-gosh-darn-diculously awesome, thanks for your hard work.
wizang said:
I assume disabling voodoo would be a prerequisite to installing this kernel? Though I'm curious what partition scheme are you using for this? Is it using samsung's default filesystems for /system /data etc?
EDIT: Forgot to say, this is re-gosh-darn-diculously awesome, thanks for your hard work.
Click to expand...
Click to collapse
Yes, you MUST disable voodoo before using this kernel. I will put together a voodoo and OC flavor of this for those interested later. As of now I have only been working with non-OC and non-Voodoo in this kernel to gauge how the work changed the experience.
Edit: Oh yes, it uses the default partition scheme. It is a goal of mine to eventually change the formats of partitions (similar to voodoo) but keep the layout, it is my thought that doing so provides the largest window of compatibility between stock Samsung/VZW Roms and custom Roms. With a proper recovery, the change could be performed and backups and restores would work no matter the format of the internal media as the layout remains the same.
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
bwheelies said:
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yea my phone is not recognized by the computer either, even after a restart.
Naturally I double checked usb debugging and the drivers (adb connected to my white fascinate just fine and I made a jump back to Geeknik's test kernel to double check that something hadn't died in ole blacky and it registered there as well) I wonder if its just this fascinate (as it has had a laundry list of its own issues). This phone is running Superclean DJ05 completely stock and was fresh off a complete wipe and restore
bwheelies said:
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I can confirm that I am unable to access the phone via Samsung's drivers using Windows XP. [Added this too my list]
Wireless tether does work in case you need it, that is why I hadn't noticed this issue. Good catch!
I really like the transparency of your work. It's refreshing to actually read about the process you're working on and the way you explain it definitely makes seems like you have a good grasp of what's going on. I can never quite tell with the other devs. Anyway good luck!
FDro said:
I don't want to turn you away from your work, but have you considered heading over to IRC and joining the guys working on Gingerbread? I'd assume that the more competent people working on it, the better.
Click to expand...
Click to collapse
Agreed! If they can get GB running nobody is going to be interested in Eclair or Froyo.
I like the sound of this kernel. Imma flash it when i get home. Looking forward to seeing the OC version
SCH I500 Super Clean v.9 DJ05 Revolution 3.6 OTB oc'd lv1200 Voodoo5
2 SirGatez.
It sounds like you are pushing towards performance optimizations. Have you checked supidfast sources? I tried it before geeknik left and it was significantly faster then stock. May be you can get something from him.
I really appreciate what devs do here, cool stuff! However I do not understand why that much talent spend in vain... Every developer has his own build, mods and bug fixes. Is this real open source spirit to have so many versions? Looks like brownian motion to me.
Now, you can say that I'm free to do it on my own etc, as other devs pointed here. But, full fledged development it not for everybody by various reasons. I hope it is obvious. Would be nice to see some consolidated development! Then it will be much more easy for mere mortal to contribute to that product. We all have same phone!
Once again I do not want to upset anybody.
bendbowden said:
Great work!
Sent from my Galaxy-S Fascinate
Click to expand...
Click to collapse
Also, great write up! I will report back if I notice any bugs not mentioned above.
Just got my gtab the other day. After some XDA upgrades and flashing cm7, I'm not showing any governor selection under cpu settings? I also use Temp+Cpu app to monitor my clock speed and its showing -1mhz constantly with no changes. Everything runs ok, boots no problem, but I'm pretty sure this shouldn't be showing like this.
These are exactly the steps I took-
out of the box booted up, Installed the OTA, checked my info was TNT 1.1 3588, Rooted via z4root, installed clockwork v08, wiped data/factory, cache and dalvik cache, installed cm7n86, booted up.
I'm not new to android but obviously new to the gtab. I'm assuming I did something wrong but not sure what I skipped over if any steps? Any suggestions before nvflashing? Thanks!
If you're running CyanogenMod 7.0.x, then you have pershoot's kernel, which has the correct cpu governor -- ondemand -- already pre-configured. You don't need another governor.
Simply change the MIN and MAX CPU frequencies as needed. The kernel will take care of everything else.
Thanks, but I guess I should have specified more. Not having the governors was a concern as far as them not showing but not for wanting to use the others. I use ondemand for all my devices so that is good to know that it is using that.
For me it's more that it is not showing me what the current cpu frequency / clock speed is. That was one of my ways of telling when an app or something was not acting right. i.e. When I'm sitting on my home screen not doing anything and my cpu is maxed out, then I know something is running when it shouldn't. I still have the cpu % so I can live without the frequency, just not used to seeing my cpu speeds in the negative lol.
btw, is this normal for the gtab/cm7?
The negative CPU frequency is most likely an application bug. Report it to the app author.
Check the correct CPU speed (in kHz) by getting it directly from the kernel:
Code:
$ cat /sys/devices/system/cpu/cpu?/cpufreq/cpuinfo_cur_freq
216000 [I]# system's idle, so the second CPU's been offlined[/I].
[I]
Load the CPU; then,[/I]
$ cat /sys/devices/system/cpu/cpu?/cpufreq/cpuinfo_cur_freq
1000000
1000000 [I]# Both CPUs now operating at 1 GHz[/I].
Instead of the command line, you can also use Michael Huang's SetCPU from Market to check (and set) CPU speed.
Edited
Figured out the answer
Trickster MOD app is a tweaking tool to change various settings included in your kernel and other tweaks to your phone. It was made by me and my friend.
Screenshots and more information at links below.
Links
Google Play Store
AndroidPIT
Donate
Website​If you like the app please rate it 5 stars and if you can, please donate.
Feature requests
Please post & vote features on our feedback site. So we can keep track of them
Bug Report
Please read the FAQ at our website before reporting any problem
If the FAQ does not help, use the Bug Report feature in our app & reference your ID here (the number in the mail subject).
Credits:
- Google
- Our great kernel devs
- grilledbacon for your beautiful icon
- Beta testers and translators for your contributions
- Anyone that helped us in some way
Disclaimer: This is provided with NO GUARANTY whatsoever. Use your common sense.
Initial version has been pushed to Google Play https://plus.google.com/u/0/116709542966452959662/posts/NZBEEJcuY5d, still pretty basic ATM moment. More stuffs will be added in later versions.
Thanks for adding support for the Nexus 10!
New version uploaded to market, should be available to you shortly
https://plus.google.com/u/0/116709542966452959662/posts/796By1dhjso
New version has been uploaded to Play Store, more info https://plus.google.com/116709542966452959662/posts/KDqLwP8gMH7
I had backed up my stock kernel using trickster mod, then flashed franco.kernel r-4. I confirmed everything on my phone was working properly, then paid for the donate version of the app so I could restore my stock kernel back to my nexus 10 4.2.1. All was well until I started using my device,
- OTG support was intermittent and my applications were running abnormally slow.
- Most of the folders that had write privileges could not be written to anymore when I tried making a new TWRP backup and ended up corrupting some of my existing application backups (combination of program not being able to write properly and OTG fading in and out).
I had to go into TWRP and restore from a nandroid after the fact and run Titanium to restore all my apps - OTG and worked fine after that. Any ideas, or a possible fix? I'd like to get the most out of the restore kernel function of the app.
bigdog2k7 said:
I had backed up my stock kernel using trickster mod, then flashed franco.kernel r-4. I confirmed everything on my phone was working properly, then paid for the donate version of the app so I could restore my stock kernel back to my nexus 10 4.2.1. All was well until I started using my device,
- OTG support was intermittent and my applications were running abnormally slow.
- Most of the folders that had write privileges could not be written to anymore when I tried making a new TWRP backup and ended up corrupting some of my existing application backups (combination of program not being able to write properly and OTG fading in and out).
I had to go into TWRP and restore from a nandroid after the fact and run Titanium to restore all my apps - OTG and worked fine after that. Any ideas, or a possible fix? I'd like to get the most out of the restore kernel function of the app.
Click to expand...
Click to collapse
Hi there,
The code to do the backup/restore couldn't possibility do that (e.g. it does not contain anything to change permissions). As I don't have the device, previous tests were done by my testers and I had positive results, so I will ask them to check again. For now, can you provide more information:
- ROM: I guess stocks?
- busybox: which app did you use to install it? busybox version?
- If possible do a new nandroid backup and do two bug report (Trickster MOD menu): once before you do a new backup and another when you restore kernel so I can check if there's anything goes wrong. Also send me the list of contents in /sdcard/kernel_backups
bigeyes0x0 said:
Hi there,
The code to do the backup/restore couldn't possibility do that (e.g. it does not contain anything to change permissions). As I don't have the device, previous tests were done by my testers and I had positive results, so I will ask them to check again. For now, can you provide more information:
- ROM: I guess stocks?
- busybox: which app did you use to install it? busybox version?
- If possible do a new nandroid backup and do two bug report (Trickster MOD menu): once before you do a new backup and another when you restore kernel so I can check if there's anything goes wrong. Also send me the list of contents in /sdcard/kernel_backups
Click to expand...
Click to collapse
Thanks for the quick response! I can do that later today. Yes, Rom is stock Jellybean rooted 4.2.1, busybox was installed using the stericson tool from the play store. Ill pm you later with extra info.
heya, loving the app. got one question if anyone can answer. does anyone have a list of kernels that support s2w? I'm using kmanta but it doesn't show CPU temp.
also on a side not, where would the options show up if its able?
edit: stock kernel from paranoid android for n10 and franco kernel doesnt show temperature either
Big eyes, I'm running trickster for the first time on the gnex and have a question. If I change the max freq from 1700 to 1600 and hit save. Then exit and go back in, its back to 1700. I then tried the freq lock option and that seems to work and it stays at 1600.
What's odd, is on the main screen (device status, core 0/1) it only goes to 1000mhz max. In realtime I mean....if I put my finger on the screen and move around it gets to 1000 but nothing higher. I'm wondering maybe if locking it down by checking that option basically locked it down to 1000 rather than 1600?
Confused..... Any thoughts? Thanks, great app
chugger93 said:
Big eyes, I'm running trickster for the first time on the gnex and have a question. If I change the max freq from 1700 to 1600 and hit save. Then exit and go back in, its back to 1700. I then tried the freq lock option and that seems to work and it stays at 1600.
What's odd, is on the main screen (device status, core 0/1) it only goes to 1000mhz max. In realtime I mean....if I put my finger on the screen and move around it gets to 1000 but nothing higher. I'm wondering maybe if locking it down by checking that option basically locked it down to 1000 rather than 1600?
Confused..... Any thoughts? Thanks, great app
Click to expand...
Click to collapse
Kernel/ROM issue. The app always reads frequency settings from the kernel itself so if it's at something then it's there, if a setting doesn't stick then something else changes it, and if the frequency does not go to the max that is because the set governor and its correspondent tunables, as in load is not high enough for the governor to set it to max.
bigeyes0x0 said:
Kernel/ROM issue. The app always reads frequency settings from the kernel itself so if it's at something then it's there, if a setting doesn't stick then something else changes it, and if the frequency does not go to the max that is because the set governor and its correspondent tunables, as in load is not high enough for the governor to set it to max.
Click to expand...
Click to collapse
Fair enough...I appreciate the quick response. It's Franco's latest R8, so I'm guessing its his kernel. Dam.... good to know. Maybe time to go back to stock kernel on Sentinel ROM...wonder if I can change the freq's in that kernel
chugger93 said:
Fair enough...I appreciate the quick response. It's Franco's latest R8, so I'm guessing its his kernel. Dam.... good to know. Maybe time to go back to stock kernel on Sentinel ROM...wonder if I can change the freq's in that kernel
Click to expand...
Click to collapse
You might wanna read our FAQ as it contains some information of what inside a JB device that might change the set frequencies. This should be patched in the kernel or worked around in the ramdisk. I coded for the N10 without a device so it's hard for me to say more. As for the frequency doesn't go to max, it's likely because of the load as I told you. Touching the screen is a relatively light load so it might not go to max frequency at all. That's normal.
Sounds good...last question, how do u reset the CPU spy like stats? Sorry if this is already covered in the faq
chugger93 said:
Big eyes, I'm running trickster for the first time on the gnex and have a question. If I change the max freq from 1700 to 1600 and hit save. Then exit and go back in, its back to 1700. I then tried the freq lock option and that seems to work and it stays at 1600.
What's odd, is on the main screen (device status, core 0/1) it only goes to 1000mhz max. In realtime I mean....if I put my finger on the screen and move around it gets to 1000 but nothing higher. I'm wondering maybe if locking it down by checking that option basically locked it down to 1000 rather than 1600?
Confused..... Any thoughts? Thanks, great app
Click to expand...
Click to collapse
You can't change the max clock freg because you need a kernel with a patched PowerHAL, which Franco doesn't have.
It only goes to 1000mhz because this is how the interactive governor is tuned. If you put it under increased load it will eventually increase. If you go into the governor parameters on trickster for interactive you will see "hispeed_freq" will most likely be set to 1000000 (1GHZ), which means the CPU will jump to this immediately. You can play around with these parameters for battery/performance but Franco and a few testers tune them significantly, although his N10 kernel is very young compared to his N4 and N7 kernels where the settings have been tuned to a tee, and I think the N10 settings might have just been copied over as a reliable base.
We're going to close individual device thread to consolidate our app thread into one at http://forum.xda-developers.com/showthread.php?p=28659480 , please go there if you need to discuss anything related to our app.
Thread Closed as per OP....
Hello for all! :good:
Sorry my english...:cyclops:
Well, i have a low cost tablet, less of 100 bucks, AOC MID 7y2241. It have Amlogic (mason 6) Dual Processor set in 1.2Ghz and 1 GB RAM, GPU Dual Mali 400, running Jelly Bean 4.1.1 :highfive:
It can run all games in excellet performance if... dont sleep. Take easy, i can explain:
Yeah, i dont know why, but, when tablet turns on, he play everything very well. But, if the screen lock and sleep for 5 min or more, the tablet shows me so much lag and low performance after wake up. Just way to back to good playing is restarting device.
I think the problem is the power saving or a seriuos bug, but i not sure. This tablet is set up in conservative mode, and i cant change it. Really, i cant change nothing relative of CPU. I already rooted device with kongo, it works really good! But any apps of overclock dont works in this device. Give root permission, you set, but nothing happen.
I try change manually sys directory (cpufreq), with adb shell, but is same. I give permissions to rw, but the device return me ALWAYS operation denied.
Well, i like to know if is possible write in sys directory. I try for adb and rooted file explorer, but always is operation failled or denied. If this low performance after sleep is a bug, how to fix or if change the governor can help me in this case?
I cant wait for updates... maybe this tablet never see other android version. I cant change image files and rom, cause i cant do backup in this device. Need a solution for compiled kernel.
Seens it is not a particularity of my device. All AOC MID 7y2241 shows this same problem (but only me realized.). Everyone thinks this tablet is slow, but it can run heavy apps and games easily (before first sleep).
Pls, a really need some help (more than 5 days searching and nothing...)
*********************************************************
News: When device restart, 2 cores are working. After 5 min sleeping (lock screen), just one core work. Nothing do the second core wake up. Just shows stopped in CPU-Z. I think this is the problem. How i can fix?
For god, nobody????
Cmon guys, just 5 min of a genius can libert me of my insanity!!!
7y2241 said:
Hello for all! :good:
Sorry my english...:cyclops:
Well, i have a low cost tablet, less of 100 bucks, AOC MID 7y2241. It have Amlogic (mason 6) Dual Processor set in 1.2Ghz and 1 GB RAM, GPU Dual Mali 400, running Jelly Bean 4.1.1 :highfive:
It can run all games in excellet performance if... dont sleep. Take easy, i can explain:
Yeah, i dont know why, but, when tablet turns on, he play everything very well. But, if the screen lock and sleep for 5 min or more, the tablet shows me so much lag and low performance after wake up. Just way to back to good playing is restarting device.
I think the problem is the power saving or a seriuos bug, but i not sure. This tablet is set up in conservative mode, and i cant change it. Really, i cant change nothing relative of CPU. I already rooted device with kongo, it works really good! But any apps of overclock dont works in this device. Give root permission, you set, but nothing happen.
I try change manually sys directory (cpufreq), with adb shell, but is same. I give permissions to rw, but the device return me ALWAYS operation denied.
Well, i like to know if is possible write in sys directory. I try for adb and rooted file explorer, but always is operation failled or denied. If this low performance after sleep is a bug, how to fix or if change the governor can help me in this case?
I cant wait for updates... maybe this tablet never see other android version. I cant change image files and rom, cause i cant do backup in this device. Need a solution for compiled kernel.
Seens it is not a particularity of my device. All AOC MID 7y2241 shows this same problem (but only me realized.). Everyone thinks this tablet is slow, but it can run heavy apps and games easily (before first sleep).
Pls, a really need some help (more than 5 days searching and nothing...)
*********************************************************
News: When device restart, 2 cores are working. After 5 min sleeping (lock screen), just one core work. Nothing do the second core wake up. Just shows stopped in CPU-Z. I think this is the problem. How i can fix?
Click to expand...
Click to collapse
uninstall apps you wont use and also
try clearing cache you can do so by finding at play store :angel:
Thanks so much for coop!
Hell_X said:
uninstall apps you wont use and also
try clearing cache you can do so by finding at play store :angel:
Click to expand...
Click to collapse
**********************************************************************************************
Man, i really really apreciatte your iniciative. Thank you so much! I dont give up yet...
I already do a factory reset, cleanning cache, using Power + Up Button. And not work... Maybe you want said other thing, maybe?
I pass last days broken head in this S.O, and seens a bugged kernel. The tablet boot, and 2 cores working. When 5 min pass by (standby), the cpu 1 is setted off line, and dont wake up again until restart. In I9100, the core wake up frequently, according to demand. But in this case, it dont wake anymore...
When the tablet boot, In "cpu1" folder (in sys/devices/system/cpu/), there is a shortcut of folder "cpufreq" contained in "cpu0" folder. When pass 5 min in standby, the cpu1 is setted like offline, and this shortcut (cpufreq folder in cpu0) is deleted, together with folder "topology". When force wakeup cpu1, just folder "topology" backs. In short, the shortcut of "cpufreq" folder in "cpu1" folder no back anymore.
I think that cpu1 stays without freq control, cause system tuner apps shows the cpu1 like online (just when force wake up), but without freq, just shows n/a.
I really really apreciate a solution for this problem. No one apps can do anything usefull.
For hour, this table have a 4000mah battery, so, i dont matter if i can disable hotplug cpu function. I prefer let 2 cores working that let it cpu1 in offline.
All apps that give tweak "all core enable" in boot dont work (rooted). I need a way that prevent the cpu1 to be setted offline permanently when in standby (lock screen), to avoid first offline set in cpu1.
Something to do with your cpu governor not scaling properly on wake up. Download No-frills CPU Control from playstore. You can read about this app in here.
Try setting the cpu governor to interactive (if none, ondemand) and i/o scheduler to sio (if none, noop or deadline). You can also adjust the min/max frequencies of the stock values.
Yet trying!
Hello!!!
Thanks god, somebody reply me! :victory:
So, how i said, noone apps in google play works (rooted) in this tablet. The No Frills was the first that i try. I click apply, but the config dont change (rooted!).
Is a total root. No this problem. I think that cpu Amlogic have some limitations. Maybe the energy controller is very limited, cause i cant change freqs, governors and I/O (any apps). Just have "conservative" (default, i cant change) and "performance2" (i cant set) governors. Exists "performance", but not have config options (is like no exists).
Or, maybe, the kernel of this android version no able this changes (in this case, i have hope).
I think I/O dont go work here (disk scheduler). What i want is prevent cpu1 set offline, maybe disabling hotplug control?
I discover that this cpu set auto offline cpu1 after 40 ~ 50 min playing heavy games (for sure, high temps...). Certainly, the power manager of cpu Amlogic meson6 is very useless.
If somebody know how disable it in kernel options (maybe uninstalling drivers?), it would be amazing :highfive:
Reviving topic...
Reviving topic...
Reviving topico again...
Reviving topic again... :crying:
7y2241 said:
Reviving topic again... :crying:
Click to expand...
Click to collapse
Claim warranty!
It is s SW Problem ... Iam developing a custom kernel for a Ventos 7 HD ( has the same CPU) it has the the same problems. I fixed it by comparing many meson6 kernel sources. You will need a custom kernel.The Original Amlogic Kernel is very buggy .The CPU can reach 1.5ghz without problems but it is not active in most kernels for Amlogic.Also the CPU1 down is a known Problem , this happens often after a suspend.
Try to find the kernelsource for the device.Maybe i can help you then.
Sent from my LG-P990 using XDA Free mobile app
I've tried several apps that could get kernel access, but they either crash or fail to load. I'm rocking android 7.1.2.
Verdinex said:
I've tried several apps that could get kernel access, but they either crash or fail to load. I'm rocking android 7.1.2.
Click to expand...
Click to collapse
Don't have that problem; suggests a possible problem with bootloader unlock. Any issues securing root?
This is what I see after installing su14.zip arm non-64:
https://imgur.com/a/jnnOc03
Strangely enough, I can't see the root option in the developers panel and it should've been under 'demo mode'.
Can you run Kernel Adiutor? Could give me the name of the app you're using so I can check if it works.
Verdinex said:
This is what I see after installing su14.zip arm non-64:
https://imgur.com/a/jnnOc03
Strangely enough, I can't see the root option in the developers panel and it should've been under 'demo mode'.
Can you run Kernel Adiutor? Could give me the name of the app you're using so I can check if it works.
Click to expand...
Click to collapse
- "su14.zip"? Looks like run-of-the-mill "Advanced Root Checker" app which yields unreliable results IME
- "I'm rocking android 7.1.2" - based on your post history assume that means AEX customized for HDX??
- if AEX there is no integrated "root option"; however, it will expose all installed/working tools in "UI &UX" section
- I use multiple kernel apps including EX Kernel Manager and Kernel Adiutor to name a couple of popular ones; no issues
Davey126 said:
- "su14.zip"? Looks like run-of-the-mill "Advanced Root Checker" app which yields unreliable results IME
- "I'm rocking android 7.1.2" - based on your post history assume that means AEX customized for HDX??
- if AEX there is no integrated "root option"; however, it will expose all installed/working tools in "UI &UX" section
- I use multiple kernel apps including EX Kernel Manager and Kernel Adiutor to name a couple of popular ones; no issues
Click to expand...
Click to collapse
So which rom would you recommend instead? It seems this one has some issues regarding the root access. I've rooted my device with the file that can be found on official lineage website:
https://download.lineageos.org/extras
Verdinex said:
So which rom would you recommend instead? It seems this one has some issues regarding the root access. I've rooted my device with the file that can be found on official lineage website:
https://download.lineageos.org/extras
Click to expand...
Click to collapse
None of the popular HDX ROMs have "root access" issues. Your device, more accurately your firmware/software configuration, is the problem. Suggest a full wipe (all partitions) followed by a complete reinstall using the ROM of your choice. If issues persist it is likely the bootloader has not been fully/properly unlocked.
Davey126 said:
None of the popular HDX ROMs have "root access" issues. Your device, more accurately your firmware/software configuration, is the problem. Suggest a full wipe (all partitions) followed by a complete reinstall using the ROM of your choice. If issues persist it is likely the bootloader has not been fully/properly unlocked.
Click to expand...
Click to collapse
I've used magisk to root my device and everything's working fine now. I can run any kernel manager without much problem. Strangely enough, on demand cpu governor keeps my clocks at 300MHz. Interactive works a lot better. Is there any way to overclock my cpu without changing the kernel itself? I'd like to set single core at 2.2-2.3GHz and the rest at 1.9GHz to lower the temperature. 2.15 GHz is the maximum now.
Verdinex said:
I've used magisk to root my device and everything's working fine now. I can run any kernel manager without much problem. Strangely enough, on demand cpu governor keeps my clocks at 300MHz. Interactive works a lot better. Is there any way to overclock my cpu without changing the kernel itself? I'd like to set single core at 2.2-2.3GHz and the rest at 1.9GHz to lower the temperature. 2.15 GHz is the maximum now.
Click to expand...
Click to collapse
No way to overclock on stock kernel; there are no alternatives. Let interactive governor set the clocks and walk away. Twiddling CPU frequencies and other gov parameters on a handheld device of this type/vintage is a fools errand. Heat dissipation is not an problem unless you make it an issue with a thick/unventilated case after messing with CPU tunings. Just don't ...
Davey126 said:
No way to overclock on stock kernel; there are no alternatives. Let interactive governor set the clocks and walk away. Twiddling CPU frequencies and other gov parameters on a handheld device of this type/vintage is a fools errand. Heat dissipation is not an problem unless you make it an issue with a thick/unventilated case after messing with CPU tunings. Just don't ...
Click to expand...
Click to collapse
After playing around with different cpu governors, I discovered that the conservative mode is quite good when it comes demanding apps. Do you know an app that could allow me to set a particular cpu governors for different apps?
Verdinex said:
After playing around with different cpu governors, I discovered that the conservative mode is quite good when it comes demanding apps. Do you know an app that could allow me to set a particular cpu governors for different apps?
Click to expand...
Click to collapse
You'd have to roll your own script using a tool like Tasker or Xposed Edge.
Davey126 said:
You'd have to roll your own script using a tool like Tasker or Xposed Edge.
Click to expand...
Click to collapse
Thx, I'll stick to Kernel Adiutor it works really well and I can switch between governors on all core with a single button.