I just found a way to overclock the GPU on all xperias. Need some testers, but remember, it might damage your device!
I will releasing here test kernels for X8, but these MIGHT DAMAGE your devices, so you flashing on your own.
XDA:DevDB Information
Pepejson-Kernel, a Kernel for the Sony Ericsson XPERIA X8
Contributors
mamutos
Kernel Special Features:
Version Information
Status: Testing
Created 2013-11-05
Last Updated 2013-11-05
I compiled the first version, but have probably a bad ramdisk, not even the logo shows up and gets into bootloop.
I need nAa-jb-06 ramdisk. @nobodyAtall Can you share it with me ?
Thanks.
1. We need a "little bit" more information about this project
2. The kernel is GPL protected, need the source (to identify what is your work and who worked with the kernel earlier)
3. The "original development" section need at least one idea what not exists on this device.
4. The "GPU overclock": with the msm7x27 SoC, the GPU clock is LOCKED, always run on the axi bus speed, you can't set it separately. You can set the GPU speed if you play with the axi bus speed in the acpuclock.c, but this is not a new idea.
5. The overclock of the GPU in our msm7227 SoC is theoretically unusable, because our adreno200 is cpu limited in most case. Just check the same gpu in the qsd8250, and you can see, with more powerful cpu this gpu can perform much better (on same clock)
This is NOT an offense, I just point to some thing before tons of idiot questions arrived about the project.
So, better if you correct the opening post and give the required informations, and folloew the forum rules (before you get a warning from a moderator, for example: due the missing sources)
PS.: you can cut the ramdisk from the precompiled nAa-06 kernel. I you have the knowledge to make new gpu overclock method, this is easy work...
PS.2.: Okay, just find the lz4 header in the kernel.sin, and delete everything before this and you can get the original nAa-06 ramdisk
Last note: maybe I wrote incorrect informations, the more experienced members/developers can correct it.
EDIT: the to overclock the gpu on all xperias is nonsence, because the xperia family have different gpus. (the most is adreno powered, but the phones with novathor SoC have Mali 400MP, or the xperia C have PowerVRSGX544)
I don't understand this kind of thread , first test then post it and do a favor for all do not create it in original DEV section this is not belong here .
Thanks whore?
Sent from my E15i using Tapatalk 2
pilu1978 said:
4. The "GPU overclock": with the msm7x27 SoC, the GPU clock is LOCKED, always run on the axi bus speed, you can't set it separately. You can set the GPU speed if you play with the axi bus speed in the acpuclock.c, but this is not a new idea.
Click to expand...
Click to collapse
I don't knew that. Sorry
Topic to remove.
Yet again this highlights the fragmentation of development here.
@op - I you had performed a search or even browsed here a little you would seen active kernel development.
You unwillingness to ask to join such a group of guys or even just post in their threads to contribute leads me to thinking you're a glory hunter.
And then when you ask nAa to just send you his ramdisk I honestly nearly wet myself.
Thanks for the laugh chap - I'm even gonna thank you for it
Related
Hi all,
So far, I am able to build a kernel from source for working on Dell Venue. As I notice, the JW rom has performed some overclocking tricks to reach a CPU frequency greater than 998MHz.
I would like to ask, how would we overclock for Dell Venue in our kernel? I tried to set min/max frequency for CPU manually, but no effect (the kernel documentation also shows that, Sysfs can override such change).
Please help!
OK, now I got the answer and know where to patch.
BTW, my topic was moved to General, it might not a suitable place since I am asking about kernel tweaks for performance, not using apps.
So r u building a new rom? might be ics 4??
TUTORIAL
How to overclock my device?
What do we need?
-Android device
-Kernel wich supports OC or UC (Stock kernel can be used for UC)
-App to manage CPU speeds
I have all of these what do i do now?
http://www.youtube.com/watch?v=CxNFz_ad3Us&feature=youtu.be
Follow that tutorial i made for you guys it shows some of the OC.
Kernels i reccomend.
XSX kernel(Stable and fast has some things others don't have.)
SSspeed kernel(Made for pure speed is most of the time stable and gives good benchmark scores!)
Pure ics kernel-for cm9/cm10(this kernel is the same as SSspeed but it's for CM.)
FAQ
Q-can this damage my device?
A-yes if you use too high speeds
Q-do i need root acces?
A-yes
Q-how to get those govenors?
A-if your kernel does not have them ask your kernel maker to put them in
Q-my device keeps rebooting when overclocking to high speeds
A-this means it is not stable try a bit lower
Q-my device gets hot!
A-turn it off before you damage your hardware
If you have questions ask them bellow or PM me
I AM NOT RESPONSIBLE FOR YOUR DEVICE IF YOU DAMAGE IT IT IS YOUR PROBLEM
Click to expand...
Click to collapse
post 1 for kernels upto 1.728
post 2 for kernels upto 1.836post 3 for kernels upto 1.512post 4 updates & requests
This is originally Leedroids work
ive just made slight changes and edited the script/code, with governors and frequencies etc, below in downloads, for both cores (more to add by request).
if you find that any of these changes are not working
delete .placeholder folder in system/etc/init.d/ , you will need a rooted explorer with the file system mounted rw. And/or remove/disable mpdecision (if your kernel supports it)
please go thank leedroid on this thread but dont post bug reports or errors to Leedroid, as this was edited by me, any faults in the code is my fault
this basically, is a bit of code, which pre sets dual core as locked/forced aswell as which governor, and at what frequencies your phone is set to be at, as standard. please decide on your "ideal" governor and frequency, as you will have trouble changing these inside android (as a noob) ,
if your desired governor or frequency isnt listed, again , give me a holler and il sort it for ya.
1, back up your rom (advised)
2, download chosen zip
3, in recovery, install chosen zip
4, reboot
5, no step 5, thats it, youve done it
to check, confirm and change settings, i recommend using (click me) <<< this here, very lightweight, easy to use, and changes are instantanious, aslong as they are not been conflicted by previous init.d files
if you would like alternate settings, or governors, give me a holler with kernel info and and il see what i can do
downloads beloware for kernels that support upto (atleast)1.728
For kernels upto 1.836 ghz
downloads beloware for kernels that support upto (atleast)1.836
For upto 1.512 ghz
downloads beloware for kernels that support upto (atleast)1.512
currently editing
16/8
performance for upto 1.836 ghz kernels added
interactive for upto 1.728 ghz kernels added
savagedzen for upto 1.836 ghz kernels added
.................................................................................................................
requests[
ok to start and ask a stupid question
ICS & GB ?
ICS only ?
GB only ?
doesnt matter ?
jcsy said:
ok to start and ask a stupid question
ICS & GB ?
ICS only ?
GB only ?
doesnt matter ?
Click to expand...
Click to collapse
It doesn't make a difference mate, works on jb, gb and ics
OP - might wanna make note..since a lot of people here use the "other" kernel.. may wanna inform them not to use these scripts w/ that kernel...and to select the settings they want in aroma
if people want to use these scripts, they should disable mpdecision via sysfs (directions posted on that other site in post 2 of the kernel thread)
this info will prevent a lot of issues with external processes attempting to control cpu1 on/offline
cyndi.branam said:
OP - might wanna make note..since a lot of people here use the "other" kernel.. may wanna inform them not to use these scripts w/ that kernel...and to select the settings they want in aroma
if people want to use these scripts, they should disable mpdecision via sysfs (directions posted on that other site in post 2 of the kernel thread)
this info will prevent a lot of issues with external processes attempting to control cpu1 on/offline
Click to expand...
Click to collapse
Removing the .placeholder from init.d allows the CPU to be controlled manually, as opposed to chads preset settings
I'll be a little more specific in op later, thanks
Also mpdeciaion has been disabled in 3.1.8 , if I remember correctly
Q&A for Kobo Arc Development
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Kobo Arc Development. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Kobo Arc 7HD OTG
ginco95 said:
Does somebody know how to enable usb otg on rooted Arc 7 HD?
Click to expand...
Click to collapse
DoPa made a patch to give OTG to the Sero 7 PRO (sero7pro-usbotg-dopa-v1.1.zip)
(See http://forum.xda-developers.com/showthread.php?t=2470998)
Could this be used to give OTG to the Kobo Arc 7HD or could it be modified to do so?
If this can be done, please give instructions about how to install patch to the Kobo Arc 7HD.
Thanks
stock rom
can someone please provide a download link for the original kobo arc 7 android 4.2.2 jellybean firmware zip cause I was such an idiot and I didn't back up data and I try to make a custom rom and the device is now bricked with boot loop adb doesn't work and fastboot doesn't work either please provide a download link
Kobo Arc (OLD), status?
Hi guys,
I've just read through the whole thread and frankly it just gave me a headache. I'm a software developer and I'd like to help, but I have zero experience with android or Cyanogenmod so I need some help. I have the OLD Kobo Arc and I'd love to be able to install something more recent than the latest official ancient Android 4.1.1 system update. So, let me fire a few questions:
1. Can anyone quickly summarize where we are with the OLD Kobo Arc? Do I understand correctly that you guys have so far managed to root it but unfortunately all attempts to go any further have failed?
2. Considering that the Kobo Arc has the same SoC (omap 4470) as the Nook HD+, what are the chances of cm-10.2.1-ovation.zip working (as far as I can see this is the latest for the Nook HD+ - sorry I can't post the link)? Of course there can be all kinds of different drivers required for the two devices, but chances are that they could be both based on the same or similar OEM designs. At least could this be used as basis to create a Kobo Arc variant?
3. Has anyone tried the Nook HD+ image?
4. All things considered, what is the next step towards a working rom?
Kobo arc 7 rom needed
my kobo arc 7 crashed cause i install chainfire 3d and now it is bricked and stuck in boot logo i need the stock rom cause i don't have any backup. can someone please give a link to download the kobo arc 7 stock android 4.2.2 rom
RC Files and thoughts on Custom Kernel
Hi, I am a new user here and in my attempt to give a reply to this user in this development thread , I got some weird restriction.
Anyway I have attached the .rc files that exist on my device. The init.carrier.rc and init.environ.rc did not exist on my device. This device is a KOBO ARC 10HD.
In addition, I have also been playing around with the kernel sources for the 10HD in particular, and as you can see from the screen shot below I am currently running my own custom kernel build.
Frankly I do not know how useful a custom kernel is since many of the special features are so heavily coded. Take the cpu governors for example, the way in which the cpufreq features are implemented make adding governors somewhat useless. There is a tegra cpufreq driver that parks the device in userspace, and decides based on the user interaction which governor is used. I suspect this has to do with the power saving features built into the stock ROM as well. In essence if I add let us say, a new governor, even if I select it as my preference the tegra cpufreq driver still has control, and defaults back into userspace once again.
Releasing userspace control of the CPU, GPU, and Cpuquiet parameters [Kobo Arc 10HD]
As some of you may have realized, it is impossible to successfully change some cpu, gpu, and cpuquiet related settings (ie. governors). This is due to a unified user daemon running in the background that constantly monitors and regulates the cpu, gpu, and cpuquiet (hot plugging) components. This means that you cannot change any of these options without them being immediately changed by this unified user daemon in userspace.
I had initially thought that this restriction was the result of a userspace kernel implementation, but it is simply a really annoying daemon messing with the kernel parameters.
To disable this functionality cleanly rename "/system/bin/ussrd" to "/system/bin/ussrd.bak" so that nvusd cannot initialize it.
This gives you complete userspace control over all cpu, gpu, and cpuquiet parameters! Do not touch the ussr_setup.sh, or you will lose important permissions to certain parameters. Do not do anything crazy like set the min and max frequencies to 51 MHz! The power saving features still work!
Good luck! Tell me if this solves your governor problems . . .
After maybe a month of working in the kernel.
I guess it's about time to release the kernel for testing.
Downloads in the second post are only there for easy follow ups.
Please read all the sections below before trying out this kernel first.
This kernel comes with absolutely no warranties whatsoever, period.
XDA:DevDB Information
This field is required., Kernel for the Samsung Galaxy Star
Contributors
psych.half
Kernel Special Features:
Version Information
Status: Testing
Created 2016-02-15
Last Updated 2017-10-12
Downloads
Latest : kernel-mint2g-trilogy-stable-r10.zip
The latest version is tested to be booting on :
Stock JB4.1 with CWM 6.0.5.3 by @dabakale
CM-10.1 with Philiz recovery by @medved197938
CM-11 with TWRP 3.0 by me
If you are getting status 7 errors, while flashing.
Try with a different recovery, and if that doesnt help upload the /sdcard/liverepack.log along with recovery.log from your recovery.
Changelog:
Code:
==================================
r10 : Apr 7, 2016
- Added and fixed custom voltage control, It could be errornessly set lesser than 650mV.
- Added underclocking. Needs to be enabled manually, see post #
- Removed 1400Mhz and 1500Mhz frequencies, as it causes crashes on many devices.
- MTP should now work on both Stock/CM rom (needs testing )
- Fixed battery level getting stuck issue.
- Fixed brightness/constrast bug in stock ROM.
- Initial stable* release of trilogy version.
Extra downloads
camctl : script to enable/disable camera for RAM
How this thread is organized.
The OP has been broken down into sections. The first 20 posts reserved for info/wiki sort of.
So when things get updated/added it'll all be in the first few pages for everyone to see.
Each section will be short and to the point so you're having problem with one section.
And you're the type who just has to quote posts you might do so without getting on other people nerves.
And normally I just just ignore the forum's usual craptalks, but at this early stage of development, try to keep the noise minimal
Let's make some things clear first.
This kernel is not for you if you want a stable kernel.
CM11 should already include the stable version of this kernel, so you should just stick to that.
This kernel is only for CM11. No other roms will be supported or even considered.
This kernel is higly experimental. Freshly made, straight from the lab.
So expect some breakage of functionality, random reboots, bootloops and explosions (unlikely, but I gotta cover myself).
Flashing
The zip makes no backup of your current kernel as of now.
So if you wanna go back to shipped CM11 kernel you have two options.
i) Manually move the original modules to system and restore just the boot image from TWRP.
ii) Restore/flash the entire ROM.
As for flashing the zip, you should burn it on a CD, and choose boot from CD in your PC by keep pressing F10/F12 at BIOS screen.
Well no but, you should at least be familiar with flashing and backups.
Breakages
Camera:
Well, it's due to updated ION drivers, which are not compatible.
In the meant time I have disabled memory allocation for camera.
Which should give some extra free memory.
If there's any other stuff broken here but not while using CM11 kernel.
Post it here instead of there. But not the stuff broken in shipped CM11 too.
What are not bugs.
24mb of less RAM:
Linux ate the RAM, no really.. linux eats RAM http://www.linuxatemyram.com
Well it's due to enabling memory cgroups.
Android says keep it enabled for low ram devices.
As per https://source.android.com/devices/tech/config/low-ram.html
Also, see the below sections for frequency scaling
Bug reporting
You know you won't get help the next time from a kernel dev if you give them a logcat.
So get the dmesg or no help for you.
And /proc/last_kmsg is not working due to ram console issues.
So if you're gonna be reporting random reboot issues, make it reproduceable.
And make it precise. If the issue is caused because you have installed, some 10 or 20 other mods.
Good luck solving it.
What are in the kernel.
You get your usual stack of IO schedulers, governors, dynamics and mods. They won't be included in the change log below.
I don't even know what half of those are.
So don't ask me what/which one to use. See them for yourself.
You also get some usual tweaks, which can be changed with any kernel control app you like.
Same don't ask what/how to tweak.
If you want something to be added that you don't find. Let me know, and I'll see what I can do.
Frequency scaling
Frequency scaling is already included from r3 onwards. So the previous instructions no longer applies.
The default min and max frequency is 1Ghz and default governor performance. ie. same as stock.
Any change to that is your own choice.
And your own loss if something goes wrong.
There are some limits to it.
i) It can be only changed 10 times a second, so it might cause lag sometimes.
So choose your governor and scaling wisely. Battery or performance. You decide.
Underclocking has been removed.
Going below 1000Mhz makes no sense, as the core voltage is the same.
There is no point in reducing frequency, if the power consumption is constant.
Overclocking has it's own section. See below
Overclocking
First if you were using the older broken cpufreq driver and were in the impression that you were at 1.6Ghz you're gonna damage your device.
The driver written by me, really overclocks the cpu and the whole system, yeah mines fractured too. Nothing I can do about it.
So use at your own risk. And don't discuss about the safe overclocking frequency. There isn't any.
Issues caused by overclocking are not issues. or bugs.
I won't give you any overclocking advice. But here's one anyway.
Overclock only when necessary and do not keep the values persistent at boot, "Set at boot" in apps.
Changes from stock:
A lot of thing has been updated, changed, modified. I will have to go through source again.
A short list of changes I can think right now will be posted soon.
- The you know, built with some GCC-5 Linaro toolchain and O2.
- Cherry picked upgrades from various kernel sources.
- Disabled a whole lot of Samsung debugging.
But there's more... see the Github repo.
reserved
#Reserved
#Reserved
#Reserved
Source
kernel:
https://github.com/halfpsych/kernel_mint2g
cpufreq-driver: https://github.com/mint2g/kernel_module_cpufreq-driver
Contributing.
Any contributions to both source and wiki are always welcome.
You can help fix typos or better clarify some sections or even help to write new ones.
Credits
For bringing CM11 to this device
- corphish
- Dreamstar
- TeamButter
- All others involved in CM11 mint2g project
Initial testers and bug reports:
- Dark Knight Begins