Where do you do this? I have trickster and ROM tool box and don't see a specific setting to enable all 4 cores
[KERNEL] M-Kernel [MOVED]
- Thread starter Metallice
- Start date
- Status
Where do you do this? I have trickster and ROM tool box and don't see a specific setting to enable all 4 cores
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37
Does your rom have kingbeatz? Or do you have the older version installed of the kingbeatz mod?
Sent from my Nexus 7 using Tapatalk HD
Does your rom have kingbeatz? Or do you have the older version installed of the kingbeatz mod?
Sent from my Nexus 7 using Tapatalk HD
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37
He was asking because older versons of king beats mod messes with trickster and wont let you change max active cores
Rootbox/m-kernel
He was asking because older versons of king beats mod messes with trickster and wont let you change max active cores
Rootbox/m-kernel
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37
Should be right under GPU max frequency on SPECIFIC screen.
Nexus 7 | PA 3.00 4.2.2 24Feb | Nova Prime | M-Kernel-a37
Nook Color | PA 2.99 | Nova Prime
Should be right under GPU max frequency on SPECIFIC screen.
Nexus 7 | PA 3.00 4.2.2 24Feb | Nova Prime | M-Kernel-a37
Nook Color | PA 2.99 | Nova Prime
I tried to up the max cores from 2 to 4 for the first time and my system freezes up? Most settings for the kernel are stock.
Any Ideas why?
d
Re: [KERNEL][3G+WIFI][4.2.2] M-Kernel - a37
Look at the screenshots in post #4235. These are working for me.
Nexus 7 | PA 3.00 4.2.2 24Feb | Nova Prime | M-Kernel-a37
Nook Color | PA 2.99 | Nova Prime
Look at the screenshots in post #4235. These are working for me.
Nexus 7 | PA 3.00 4.2.2 24Feb | Nova Prime | M-Kernel-a37
Nook Color | PA 2.99 | Nova Prime
You can find it right above voltages or under gpu frequency.in the last tab in trickster mod
Yes, your screen shots motivated me to change the settings. They are exactly the same....
I have a serious problem with this kernel and prime room. At first I thought that maybe there were some options activated with pimpmyrom, but then I tried to completely format system, data, caches... starting from 0, no way...
The problem is that, till I put my device to sleep, everything is fine, but when I do it, the screen seems splitted into two triangles, the interface shutters all the time and is virtually impossible to continue using it.
I have observed, always without sleeping any time the nexus, that I have strange profiles in gpu and lpu like 1mhz min value in the gpu, but I cannot change or erase this options, only the voltages.
Any idea? Thanks very much
Sent from my Nexus 7 using xda app-developers app
The problem is that, till I put my device to sleep, everything is fine, but when I do it, the screen seems splitted into two triangles, the interface shutters all the time and is virtually impossible to continue using it.
I have observed, always without sleeping any time the nexus, that I have strange profiles in gpu and lpu like 1mhz min value in the gpu, but I cannot change or erase this options, only the voltages.
Any idea? Thanks very much
Sent from my Nexus 7 using xda app-developers app
- Status
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
25650How would you guys feel about me closing this thread and starting a new one in Android Original Development? It technically belongs there anyway, and I wouldn't mind reserving a couple more posts in the beginning for a FAQ and other stuff. Hopefully to stop any more "Why is my min stuck at 340MHz?!?" and others like it
36Working on a new OP for mr1... Finally got a simplified feature list/changelog... Need to clean it up some haha.
Probably forgot a lot of things too.
Basic feature list -
- based on latest google aosp tegra kernel source mr1.1 for android 4.2.2
- optimized compiler flags
- Latest linaro 2013 gcc toolchain
- Dynamic EDP - enable edp cpu maximum frequency limits only above a certain temperature (motley)
- CPU over clock up to 1.7GHz
- GPU over clock up to 700MHz
- Custom user voltage control for CPU and Core components such as EMC, GPU, and LP (faux123)
- Default CPU voltages set to ID 3 levels
- CIFS, NFS, NTFS, HFS, ZRAM, and more built in.
- Runnable threads hot plugging
- FSync control (Ezekeel)
- Glibc memcpy and memmove
- User configurable Wifi power management mode (PMFAST/PMMAX)
- Deadline improvements for solid state drives
- LP core overclock to 666MHz
- Force high current charging over pc USB (imoseyon)
- Proportional Rate Reduction for TCP
- Fixed current_now property for current viewing apps
- Optimized SLUB and use SLUB by default instead of SLAB
- Tegra 3 variant display (faux123)
- Faster LP -> G transitioning
- Optimized swahb32 byteswap helper
- Asynchronous I/O latency improved through removal of plug in do_io_submit()
- Tweaked CFS parameters
- Optimized ARM RWSEM algorithm
- Block: recursive merge requests
- timer: optimize aplpy_slack()
- Disabled GENTLE_FAIR_SLEEPERS to improve performance
- Balanced EDP frequency limits to be same across all cores
- LowMemoryKiller asynchronous compaction and compaction when killing processes
- allow use of a controller native max block size
- optimized crypto algorythms
- Optimized AES and SHA1 routines
- Better hot plugging delays
- Increase boost_up_threshold for AVP clock
- kexec-hardboot support for multirom
- minimum cpu performance loch for audio playback (faux123) with additional fixes
- decreased minimum backlight level for better low light viewing
- switch do_fsync() to fget_light()
- Added latest BFQ I/O scheduler
- Fix crash when unplugging OTG devices (intersectRaven)
- Added Tegra high performance AHB memory driver with additional fixes and improvements
- Input: Send one packet at a time
- support for ROM built-in OTG support
- Added latest ROW scheduler with additional patches and improvements
- Set Core voltage to 0.95V in Low Power mode 1 for significant semi-idle battery savings
- TCP congestion control with Westwood+ set as default
- Disabled speaker dynamic range compression for improved speaker audio quality
- Lock performance governor to all 4 cores
- Many LowMemoryKiller fixes and improvements
- Many, many scheduler improvements and optimizations
- A million other patches, fixes, and improvements that I don't have the time or space to list
23Now, on to my status with this -
As a quick fix, I will revert this patch for the next build. This should hopefully solve all issues with a33 including, but not limited to, SODs, reboots, and increased battery drain in LP1 (too little voltage, but not little enough to cause freezes/reboots, has been shown to actually cause increased battery drain as compensation).
Unfortunately I haven't been able to whip up a quick fix for a couple reasons.
For one, I have other responsibilities. I had a Physics midterm early today and had to spend time reviewing and studying. Also, my father purchased a new HDTV (very nice one, super jealous) and I had to help him go pick it up and transport it, unpack it, remove the old, gigantic, heavy as f---, rear projection DLP HDTV, set up/secure/mount the new one, situate all the cables with the FIOS box/DVD/AV receiver/Surround sound, reprogram the universal remote, set up the new smart tv capabilities with the internet and their internet video services, update the TV software, set up the 3d and 3d glasses, and teach them all how to use the new stuff.
Second, my computer broke. The graphics card started acting up, kept getting messages about it failing and successfully restarting until it no longer would successfully restart. Tried uninstalling/reinstalling drivers and the whole kitchen sink, but the card was dead and there was no way around it. Aren't laptops with their all-fused components wonderful? To be honest four years is a decent run for a cheap 4-yo HP. Anyway, I need a computer for school so I got a new one as an early birthday present.
So I have a new computer now. First of all it's a macbook so I'm going to have to learn how to use OSX for one thing and get everything set up, and I'm going to have to re-make my kernel build environment from scratch which will take some time.
So hang tight please!
New posts
-
-
Question S23 - call recording - possibility of changing CSC ?
- Latest: nguyenlucky
