Related
In this post, I would like to explain what kexec-hardboot patch is.
@kernel developers: I would like to ask you to merge this patch to your kernels, because it is essential part of MultiROM - it allows me to boot any kernel without changing the boot partition. I realize that it is no small request, but the patch is not big, touches relatively stable parts of kernel and should not cause any problems. Thank you.
What is kexec?
It is syscall of Linux kernel, which allows you to boot another Linux kernel without restarting the device - "Linux boots itself". The functionality is equivalent to fastboot -c *cmdline* boot zImage initrd.img, but without PC and fastboot. It is fairly known thing, so more info at wikipedia and man kexec.
Standard kexec call unfortunatelly does not work on Nexus 4. It freezes somewhere, and it is very difficult to find out where - probably some of the drivers are not shut down/re-initialized properly, it is a commong thing among Android devices, which is why kexec-hardboot was made.
What is the difference between normal and hardboot exec?
Kexec-hardboot patch adds a real device restart to that process, so that all the drivers can be properly reinitialized. It stores new kernel to RAM, reboots the device as usual, and kernel from boot partition immediately jumps to the one which was stored to RAM before reboot.
Unlike grouper's kexec-hardboot patch, this one only requires the host kernel to be patched. This is one of the improvements I made, and I think it is pretty significant.
To sumarize the process:
kexec --load-hardboot.... is called and kernel it loaded into RAM.
kexec -e is called. Special info is written to memory (to area which is not overwritten on reboot) and the device is rebooted.
After reboot, very early in the boot process, kernel checks if that special info is present in RAM and if so, it loads new kernel from RAM and jumps to it.
Kexecd' kernel starts and boots.
For more info, read the original thread.
Patches:
Kernel patch: https://gist.github.com/Tasssadar/6766757, 4.3 AOSP kernel repo, cm 10.2 kernel repo
This is the kernel patch. Only the host kernel needs to be patched.
Related CONFIG options:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_ATAGS_PROC=y
All these options must be enabled.
Userspace kexec binary: https://github.com/Tasssadar/kexec-tools
I had to change some things in kexec userspace binary because of some kernel bugs, complete description is in that repository. You can get statically built binary at https://github.com/Tasssadar/multirom/blob/master/install_zip/prebuilt-installer/multirom/kexec
Usage:
Once you have the kernel patches and kexec userspace binary in place, just run following command to boot into new kernel:
Code:
kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0x85000000 --command-line="$(cat /proc/cmdline)"
kexec -e
Note the command line parameter - cmdline from bootloader is not added automatically, you have to put it there by yourself.
Authors:
This patch was made by Mike Kasick for Samsung Epic 4G. Since that, it was ported to several devices, one of them is Asus Transformer TF201 - I used patch from TF201 and modified it a bit (basically just changed few SoC specific constants). People at #ubuntu-arm helped me out with that, thanks.
For flo, I've improved the patch a bit - only the host needs to be patched now and I also fixed a bug with /proc/atags not reading all tags.
Thanks, added.
Actual kexec testing would have to go to kexec users after kernel passes normal use testing.
Also merged, thanks Tassadar!
I will be merging.... Thank you
Sweet..time.
Sent from my Nexus 4 using xda app-developers app
hope my previous port over to mako helped you
@ramgear
Sent from my Nexus 4 using Tapatalk 4
Added to my cm10.2 caf kernel.
thanks a lot
what would be the benefit for end user? Or is it just for devs to try kernels faster?
Sent from teh void
asim0 said:
what would be the benefit for end user? Or is it just for devs to try kernels faster?
Sent from teh void
Click to expand...
Click to collapse
The primary benefit is so that users can run Multi-ROM and have different kernel based ROMs.
Is it possible to find a nice German guy who can request on http://www.android-hilfe.de/custom-...ss15j-jwr66v-hells-core-b38-19-09-2013-a.html to add this patch to hellscore ?
Thanks
-=-=-
hellsgod Pm-ed , let`s hope
Sent from my Nexus 4 using Tapatalk 2
xanthrax said:
Is it possible to find a nice German guy who can request on http://www.android-hilfe.de/custom-...ss15j-jwr66v-hells-core-b38-19-09-2013-a.html to add this patch to hellscore ?
Thanks
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
+1 on that mate
I already asked the dev to implement this Patch. He wants to implement this patch in some later builds, to be sure the patch works correctly.
Hellsgood said that the patch will be implemented on v40 ! :good:
Merged - Thank you Tasssadar
hells
any1 found 4.2.2 kernel that has kexec?
aqsede said:
any1 found 4.2.2 kernel that has kexec?
Click to expand...
Click to collapse
Check multirom thread. Tasssadar posted one there.
http://forum.xda-developers.com/showthread.php?p=46596551
Sent from my Nexus 4 using Tapatalk
@Tasssadar
I don't know if you're around this thread much anymore, but would it be possible to implement this patch alone in another model of phone's kernels?
I have an Optimus G which is almost identical to the N4 and am trying to read as much as I can on this patch but am not finding if it is device specific, and if it is, how much needs to be changed to be used on a different device (even if it is almost the same phone).
I know there are kernels that have this patch enabled but I don't know where it came from if it's not yours. I have been told it is not possible with a stock based kernel for the O.G. but I see you have some stock kernels for the N4.
I know almost is not exact, but I think so much of them are the same that it doesn't normally take much. Thank you for your time and work put into this.
dopy25 said:
@Tasssadar
I don't know if you're around this thread much anymore, but would it be possible to implement this patch alone in another model of phone's kernels?
I have an Optimus G which is almost identical to the N4 and am trying to read as much as I can on this patch but am not finding if it is device specific, and if it is, how much needs to be changed to be used on a different device (even if it is almost the same phone).
I know there are kernels that have this patch enabled but I don't know where it came from if it's not yours. I have been told it is not possible with a stock based kernel for the O.G. but I see you have some stock kernels for the N4.
I know almost is not exact, but I think so much of them are the same that it doesn't normally take much. Thank you for your time and work put into this.
Click to expand...
Click to collapse
the kernel part itself you probably wont need to modify the patch, however you probably will need to change the offssets in multirom itself. if i recall, there is a guide on how to port multirom for other devices
opssemnik said:
the kernel part itself you probably wont need to modify the patch, however you probably will need to change the offssets in multirom itself. if i recall, there is a guide on how to port multirom for other devices
Click to expand...
Click to collapse
Thank you but I am already using multirom on my phone (Lg Optimus G on Sprint). It works like a champ, but I am trying to see if it can be applied to a stock rom. I am having issues with stock roms not using already patched kernels and would like to know if it is possible to use the patch mentioned here on another phone. The N4 and Optimus G are basically the same phone so I thought it might work.
Title says all. Comment with something under here if you have a GP 4.2. I'm making a ROM for it but, due to my network speed (slooooow), I want to know how many users will download it. Thanks in advance!
PS. If you know other users that have this Player tag their names into your reply!
I have one, but I've since replaced with with the 5 inch model. I still use it on occasion to test apps and things.
I have one, so does @SerkTheTurk @lets_zock and @ChaosChris
Sad that this is a very unsupported device (both by Samsung and developers)
No. I have not it. I leaved it to the samsung center with the latest hard brick. For now i only have a note 1 but i want to sell it to buy an iPhone 4 or a SGS 3.
Inviato dal mio GT-N7000 utilizzando Tapatalk
64kb said:
I have one, but I've since replaced with with the 5 inch model. I still use it on occasion to test apps and things.
Click to expand...
Click to collapse
As far as you have a monkey into your brain that needs ROMs to calm down itself...
drakonizer said:
I have one, so does @SerkTheTurk @lets_zock and @ChaosChris
Sad that this is a very unsupported device (both by Samsung and developers)
Click to expand...
Click to collapse
I saw... I will configure a VM with Mint 15 to (try to) develop a CM7/9 version starting from the work made by @SerkTheTurk...
HellPie said:
As far as you have a monkey into your brain that needs ROMs to calm down itself...
I saw... I will configure a VM with Mint 15 to (try to) develop a CM7/9 version starting from the work made by @SerkTheTurk...
Click to expand...
Click to collapse
I have one and I would help you if I could. But it's not that easy. My Player lies in my rom with dust on it..
lets_zock said:
I have one and I would help you if I could. But it's not that easy. My Player lies in my rom with dust on it..
Click to expand...
Click to collapse
I only have some questions:
1) Is it true that I need to have a 64 bit CPU? If yes, I have not, but in a VM is it possible to have it?...
2) What Linux OS is the best to get a fast compilation time? (My VM: 2Core, 1.5GB Ram, HDD USB 2.0 to host it (only used for the VM), 128GB of virtual HDD)
3) With Mint 15 64bit VirtualBox crashes on boot, is this a problem of the "64bit" version or is a problem of the small quantity of RAM?
I have it! It will be really, really, really great to have a new ROM, since we've got a few numbers of developers for this device. A CM7 or CM9 ROM, like u said u're going to try to do, would be really great for future developers and a future Jelly Bean ROM. ( Nowadays, I'm using ChaOS ROM v1 + S3 Modpack made by @ChaosChris )
HellPie said:
I only have some questions:
1) Is it true that I need to have a 64 bit CPU? If yes, I have not, but in a VM is it possible to have it?...
2) What Linux OS is the best to get a fast compilation time? (My VM: 2Core, 1.5GB Ram, HDD USB 2.0 to host it (only used for the VM), 128GB of virtual HDD)
3) With Mint 15 64bit VirtualBox crashes on boot, is this a problem of the "64bit" version or is a problem of the small quantity of RAM?
Click to expand...
Click to collapse
1)I believe you can build CM7 with a 32 bit OS (that requires only a 32bit processor) but for CM9 onwards you need a 64 bit version of Linux (which requires a 64 bit processor)
2)You can use Ubuntu 10.04 (as recommended on the official Android developers website) for maximum compatibility and less compilation errors.
3)Yup, you cant use 64 bit OS'es on 32 bit processors, neither with VMs nor by actually installing it on another partition.
drakonizer said:
1)I believe you can build CM7 with a 32 bit OS (that requires only a 32bit processor) but for CM9 onwards you need a 64 bit version of Linux (which requires a 64 bit processor)
2)You can use Ubuntu 10.04 (as recommended on the official Android developers website) for maximum compatibility and less compilation errors.
3)Yup, you cant use 64 bit OS'es on 32 bit processors, neither with VMs nor by actually installing it on another partition.
Click to expand...
Click to collapse
1) So for 3 or 4 years (I haven't enough money for a new pc and my parents will never buy another one only because "the cpu can work with the double number of bit in the same time" (Yes, my father were born with the "linux inside" signature, but with a 16/32bit brain))
2) Ok, I'll try
3) Damn!
4) With this post I can now post in the dev section! So when I'll fixed all bugs with current rom I will open a thread for it! Thanks!
Android Developers said:
For Gingerbread (2.3.x) and newer versions, including the master branch, a 64-bit environment is required.
Click to expand...
Click to collapse
So I cannot compile it... :'( Nooooooooo... :'( :'( :'(
I think you can compile cm7 with 32 bit Ubuntu because AFAIK, @SerkTheTurk has a 32 bit CPU (intel centrino) but he has compiled CM7 (though not booting ) successfully for our device...so you can try
Sent from my SGH-T499 using xda app-developers app
Ah. I will try. Thanks! For now with my rom I am at the same point of 3 days ago. Bootloop, bootloop and more bootloop. I think that I will restart from 0 adding one feature every flash and then when I will have enough features and stability I will relase it.
I have it, I love it and I heavily use it everyday... I hope this device can get more support, but it's wishful thinking...
HellPie said:
Ah. I will try. Thanks! For now with my rom I am at the same point of 3 days ago. Bootloop, bootloop and more bootloop. I think that I will restart from 0 adding one feature every flash and then when I will have enough features and stability I will relase it.
Click to expand...
Click to collapse
Great idea! Building a ROM in this way would be really useful to have more knowledge about what you're doing. This will help you to, if there is an error, find out exactly where it is, so you can fix it. Good thinking. Good look, maybe we finally got a sucessful CM7.
I am talking about my modded stock based rom... the cm one will wait because i need to fix some errors with the vm.
Inviato dal mio GT-N7000 utilizzando Tapatalk
lol Got it. Will you try to develop themes for your custom ROM?
Yes. But not now. I'll make themes after I have modded all the Rom because if I mod a part of the rom i need to mod all themes so when i end the modding-time i will start with all done and the theming process will be more faster.
Inviato dal mio GT-N7000 utilizzando Tapatalk
HellPie said:
Yes. But not now. I'll make themes after I have modded all the Rom because if I mod a part of the rom i need to mod all themes so when i end the modding-time i will start with all done and the theming process will be more faster.
Inviato dal mio GT-N7000 utilizzando Tapatalk
Click to expand...
Click to collapse
I can make themes for you if you want. I an currently working on a KitKat theme, and I've managed to do some statusbar mods like transparent mod, jb clock etc. I might release it for the stock XXLF1 ROM but I can do it for you too.
Thanks. I talked with [email protected]:-$ and now we are working toghether. But he has not got the player anymore so he only help me saying me what he tested and what not.
Inviato dal mio GT-N7000 utilizzando Tapatalk
I own one and I use it everyday! I rooted it but only have tried the stock rom. I want to try a custom rom. But don't know which one is the most stable or best
Sent from my YP-GI1 using xda app-developers app
So I'm using one of the kitkat roms and I can't seem to get USB OTG and USB charging to work at the same time? Is this just not possible? Or do I need to do something special? I bought one of the OTG Y cables that allows the hookup of a charger and a USB device and it's still no go, it'll show it's charging for a minute or so after a USB device is mounted but then the charging icon goes away?
Someone had mentioned to me that a custom kernel may be needed?
Yep you would need a custom kernel.
ThatFrigginAzn said:
Yep you would need a custom kernel.
Click to expand...
Click to collapse
Any documentation around on how to build this kernel to do what I need?
Hdale85 said:
Any documentation around on how to build this kernel to do what I need?
Click to expand...
Click to collapse
Look in my signature for a guide. For the specifics, you will need to find a kernel on github that has what you are looking for and port it to your build. My roll your own kernel guide will get you started. You will need a partition with Debian Linux to complete the guide. I suggest AntiX.
sleekmason said:
Look in my signature for a guide. For the specifics, you will need to find a kernel on github that has what you are looking for and port it to your build. My roll your own kernel guide will get you started. You will need a partition with Debian Linux to complete the guide. I suggest AntiX.
Click to expand...
Click to collapse
Can it be a kernel from another device? or does it need to be similar?
Also how about Ubuntu? I'm familiar with Ubuntu, but I'll look at AntiX
From what I gather I only need USB host mode so that the USB port is not outputting power.
Hdale85 said:
Can it be a kernel from another device? or does it need to be similar?
Also how about Ubuntu? I'm familiar with Ubuntu, but I'll look at AntiX
From what I gather I only need USB host mode so that the USB port is not outputting power.
Click to expand...
Click to collapse
Ubuntu should work, though the names of the dependencies might be off. Easier to just partition off and install Antix. Damn good distro. I went with stable for the guide, but you can easily switch later to testing or unstable by changing up the sources list.
For what you need, you may find it as an option when adjusting the menuconfig during the make process.
The second post in the thread tells a bit about changes necessary for the 500 device, as I originally made the guide for the 510.
There are currently two other kernels for the 500 that were successfully made using the guide. One of them also has a decent install through recovery script
sleekmason said:
Ubuntu should work, though the names of the dependencies might be off. Easier to just partition off and install Antix. Damn good distro. I went with stable for the guide, but you can easily switch later to testing or unstable by changing up the sources list.
For what you need, you may find it as an option when adjusting the menuconfig during the make process.
The second post in the thread tells a bit about changes necessary for the 500 device, as I originally made the guide for the 510.
There are currently two other kernels for the 500 that were successfully made using the guide. One of them also has a decent install through recovery script
Click to expand...
Click to collapse
What's the difference between the 500 and 510?
Hdale85 said:
What's the difference between the 500 and 510?
Click to expand...
Click to collapse
The 510 is the Google play edition, whereas the 500 is the lg version. If you didn't buy it through the play store, you have the 500.
The best way to learn would be to follow the guide all the way through, copy and paste, and then figure out what you are doing while you are doing it!
Also, this should be posted in the questions thread rather than development if a moderator would be so kind to move this post.
Oh ok the 510 is the google play edition. Either kernel should work right? They are the same device... I'm not running the stock rom as I wanted a basic 4.4 rom as this is eventually going in my car.
Well you posted right before me lol, but I made the post here because I know there are a couple other people looking for the same thing so I was hoping we could develop a kernel for everyone.
Hdale85 said:
Oh ok the 510 is the google play edition. Either kernel should work right? They are the same device... I'm not running the stock rom as I wanted a basic 4.4 rom as this is eventually going in my car.
Click to expand...
Click to collapse
Unfortunately no, there are some differences, mostly with naming, but that can be important.
There are two parts to the boot image for our device, the ramdisk, and the kernel itself. The ramdisk plays a key roll in deciding certain options for the device, while the kernel controls more common options you may find on any device.
Most of the install from recovery scripts, repack the kernel zimage with the existing ramdisk from the device. But this doesn't really matter either.
All of the multi device kernels tend to be larger than necessary and have problems they shouldn't.
Long story short is that each device has it's own kernel source, which has supposedly been optimized for its device. This isn't exactly true, and the list of changes I've made to better the 510 device's kernel is astounding.
If you follow my guide, all of this will become apparent.
Alright thanks I'll look over it.
So what makes the510 different?? Is the firmware different? Obviously they didn't change the hardware so could one somehow convert the 500 to a 510? Only reason I'm interested is because some of that stuff you said doesn't work on the 500 it seems? Such as fastboot?
Hdale85 said:
So what makes the510 different?? Is the firmware different? Obviously they didn't change the hardware so could one somehow convert the 500 to a 510? Only reason I'm interested is because some of that stuff you said doesn't work on the 500 it seems? Such as fastboot?
Click to expand...
Click to collapse
Lg specific drivers mostly. Fastboot requires an unlocked boot loader, which the V500 does not have. An exploit is used to bypass the boot loader on the 500. Loki.
The gpe is pure android, with just a couple of perks thrown in, as it uses an Lg platforms. Our device , that being the V510 most closely resembles the Nexus 4 (Mako) version, and was probably based off that device. The items I have added to the 510 kernel as enhancements, mostly came from a mako kernel with the rest simply being tweak corrections to the existing source code.
Those changes alone made huge improvements in performance and battery.
sleekmason said:
Lg specific drivers mostly. Fastboot requires an unlocked boot loader, which the V500 does not have. An exploit is used to bypass the boot loader on the 500. Loki.
The gpe is pure android, with just a couple of perks thrown in, as it uses an Lg platforms. Our device , that being the V510 most closely resembles the Nexus 4 (Mako) version, and was probably based off that device. The items I have added to the 510 kernel as enhancements, mostly came from a mako kernel with the rest simply being tweak corrections to the existing source code.
Those changes alone made huge improvements in performance and battery.
Click to expand...
Click to collapse
Yea I just found the long thread about converting, its strange they can't seem to get it to work? Quite strange... Well I'll have to research the other bits I guess from others that have made V500 kernels or something.
maybe this commit is what you need
https://github.com/oubeichen/android_kernel_lge_v500/commit/ee86db750adf2bb7b4f7b988ba6937d92551373b
I havent tested yet but this is ported from a nexus4 kernel thread. v500 and nexus4 have the same power management ic
Sent from my LG-V500 using XDA Premium 4 mobile app
oubeichen said:
maybe this commit is what you need
https://github.com/oubeichen/android_kernel_lge_v500/commit/ee86db750adf2bb7b4f7b988ba6937d92551373b
I havent tested yet but this is ported from a nexus4 kernel thread. v500 and nexus4 have the same power management ic
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If anybody wants this, I'll compile it into the V510. Looks pretty straightforward. Thank you for the link.
Hdale85 said:
Well you posted right before me lol, but I made the post here because I know there are a couple other people looking for the same thing so I was hoping we could develop a kernel for everyone.
Click to expand...
Click to collapse
Indeed! :fingers-crossed:
treetop777 said:
Indeed! :fingers-crossed:
Click to expand...
Click to collapse
I'm going to take a stab at a custom kernel, but I have to setup linux on my desktop again so I'm not sure when I'll get around to it lol. Might be able to this week sometime.
If I can't get USB Host mode with charging enabled I'm going to have to look into a wireless HD solution or something, and even then that won't fix the setup I wanted to use for high end sound.
news ????
This kernel is distributed with several overclock modules.
The modules doesn't have GPL in their licenses. The sources for modules are private.
*** The frequencies below are not real. Sorry for that. I know little about detailed architecture for U8500 CPU... ***
available frequencies:
50MHz,100MHz,500MHz,1000MHz,2000MHz(can be set by modules)
Kernel Link: http://pan.baidu.com/s/1gdmXlyN
Module for overclocking to 1.2 GHz(Stable): http://pan.baidu.com/s/1pJz8i6Z
Module for overclocking to 1.5 GHz(Stable): http://pan.baidu.com/s/1jG3giWI
Module for overclocking to 2.0 GHz(Still testing): http://pan.baidu.com/s/1bnfDNBp
If you like the kernel any donations are welcome: alipay account: 15190852698 I will build a kernel for you if you donate me
If you want to use this in your ROM:
1. PM me first
2. Don't touch the kernel(e.g. extract or modify zImage or ramdisk). You will easily get problems e.g. not booting and wifi not working
3. Don't put anything that you can get money from it in your ROM.
Recovery:
Camera button only after vibrate will bring you into TWRP
Power button only after vibrate will enter CWM
If you press both keys after vibrate you will enter kexec bootmenu.
***Read this before you flash the kernel!***
The kernel only supports /data and /cache of f2fs filesystem. You will get a bootloop if you use ext4 for the two partitions. But use ext4 for /system.
mkfs.f2fs_arm link: http://pan.baidu.com/share/link?shareid=855746158&uk=3137347581
Don't ask me for source. It's from internet.
******
Kernel source: https://github.com/FandroidRelease/android_kernel_sony_u8500/tree/overclock
XDA:DevDB Information
Fandroid Kitkat Kernel, Kernel for the Sony Xperia P
Contributors
zhy0919, XperiaSTE, Sony, CM11
Kernel Special Features: based on XperiaSTE's overclock source, with overclocking modules
Version Information
Status: Beta
Created 2014-08-31
Last Updated 2014-08-31
deleted
big-A said:
deleted
Click to expand...
Click to collapse
What do you mean??
Bootloop
I installed your kernel with cm 11 M9 and slimkat 7.6 and everytime i get a bootloop
How to install those modules? How to access recovery, power button?
This kernel looks promising, but could you please provide more information such as the recovery that comes with it, if theres one; or the features besides having the overclock modules that it has etc. Thank you. Good job overall.
big-A said:
I installed your kernel with cm 11 M9 and slimkat 7.6 and everytime i get a bootloop
Click to expand...
Click to collapse
Sorry I didn't mentioned some important information in my post.
Please format /data and /cache to f2fs if you want to use the kernel.
And also, if you flashed another ROM, you will need to mkfs.f2fs again.
mkfs.f2fs_arm link: http://pan.baidu.com/share/link?shareid=855746158&uk=3137347581
macabrocabral said:
How to install those modules? How to access recovery, power button?
Click to expand...
Click to collapse
Post updated
ArtemisRider said:
This kernel looks promising, but could you please provide more information such as the recovery that comes with it, if theres one; or the features besides having the overclock modules that it has etc. Thank you. Good job overall.
Click to expand...
Click to collapse
Thanks. Post updated.
Novathor chips can go up to 1,3ghz. 1.2 ghz is a safest option. Overclocking that much a novathor SoC without changing voltages will only consume severe power leading to overheat. Due too the aluminium design of xperia p you will not notice so much heat but when graphics artifacts start to occur then i hope you have the budget needed to buy several phones to payout the users.
Cheers
nicolassp said:
Novathor chips can go up to 1,3ghz. 1.2 ghz is a safest option. Overclocking that much a novathor SoC without changing voltages will only consume severe power leading to overheat. Due too the aluminium design of xperia p you will not notice so much heat but when graphics artifacts start to occur then i hope you have the budget needed to buy several phones to payout the users.
Cheers
Click to expand...
Click to collapse
Even i have read that 1.2ghz is the safest option for novathor overclocking. thnx for confirming.
Dammit!
I thought that fake overclocks and/or underclocks will die with the real overclock, but as I can sadly see this is not true. First of all, the commit which increases frequency in the repo of the GitHub link provided does NOT change the needed registers to increase frequency. Secondly, if the work of this thread would work at 50Hz the phone would die and at 2GHz everything will crash automatically, this is just placebo effect, a nonsense placebo effect.
Garcia98 said:
Dammit!
I thought that fake overclocks and/or underclocks will die with the real overclock, but as I can sadly see this is not true. First of all, the commit which increases frequency in the repo of the GitHub link provided does NOT change the needed registers to increase frequency. Secondly, if the work of this thread would work at 50Hz the phone would die and at 2GHz everything will crash automatically, this is just placebo effect, a nonsense placebo effect.
Click to expand...
Click to collapse
Thanks and sorry. But can you tell me why the total current of the phone seems to be much higher when at the highest frequency?
zhy0919 said:
Thanks and sorry. But can you tell me why the total current of the phone seems to be much higher when at the highest frequency?
Click to expand...
Click to collapse
What do you mean with "current of the phone"?
Garcia98 said:
What do you mean with "current of the phone"?
Click to expand...
Click to collapse
current_now in ab8500_fg
zhy0919 said:
current_now in ab8500_fg
Click to expand...
Click to collapse
I don't get you, do you mean charge_now?
Garcia98 said:
I don't get you, do you mean charge_now?
Click to expand...
Click to collapse
/sys/class/power_supply/ab8500_fg/current_now
zhy0919 said:
/sys/class/power_supply/ab8500_fg/current_now
Click to expand...
Click to collapse
For me that value is very similar even with real overclock, and it changes a lot from second to second. To check if overclock works the best idea is to make a benchmark and check ARM PLL registers.
I agree with Garcia98. The overclock cannot be done on this motherboard/CPU and the 2GHz overclock will fry the components in no time.
Garcia98 said:
For me that value is very similar even with real overclock, and it changes a lot from second to second. To check if overclock works the best idea is to make a benchmark and check ARM PLL registers.
Click to expand...
Click to collapse
Really thanks... By the way where can I find documentations about novathor CPUs? And how to modify u8500 cpu's pll register(what value can be set and why)? Thanks for your answer!!
༼ つ ◕_◕ ༽つIn the name of our great lord Helix!༼ つ ◕_◕ ༽つ
Welcome to yet another stock kernel for the Z3 Compact!
Kernel12s
It's different this time because there's an S. Trust me.
AMAZING FEATURES:
They happen to change so often that you're better off checking the changelog, but if you're stubborn, here's the core ones:
Additional CPU and GPU steps
Faux123's Intelli_plug and Intelli_thermal
adreno_idler
Memory fixes up the arse
Countless battery life and overall performance optimizations
Obviously there's more so go ahead and check my Github!
DOWNLOADS:
Always read the changelog before downloading and flashing!
Changelog: http://j.mp/changelog12_stock (includes concept and stock branches of this project)
Downloads: http://bit.ly/kernel12s
Quick link to concept downloads: http://bit.ly/kernel12c
Generously hosted by the good guys on Androidfilehost.com
HOW-TO:
* Flash using recovery
* If you're using systemless root, you need to re-flash the supersu zip after updating the boot.img
SERIOUS DISCLAIMER!
Code:
I guarantee nothing except for squids taking over our planet by the year 3027. #squidmasterrace
I'd also like to point out that the kernel developers for this device are different people with different lives, schedules and priorities, which shows in many differences in their work. We are not enemies or competitors but rather friends and colleagues, but we each support what we do as we are able to and as we deem is best.
Kernel sources: https://github.com/someone755/android_kernel_sony_msm8974_stock
༼ つ ◕_◕ ༽つPRAISE HELIX༼ つ ◕_◕ ༽つ
XDA:DevDB Information
kernel12s, Kernel for the Sony Xperia Z3 Compact
Contributors
someone755
Source Code: https://github.com/someone755/android_kernel_sony_msm8974_stock
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2016-09-06
Created 2016-07-25
Last Updated 2016-09-06
A quick FAQ that you'd better read before posting.
1. So what's the naming convention this time?
A: Cutting the bullsh*t this time 'round, all builds are permissive (unless demand for enforcing ones is raised). The number after the "s" tells you which build number this is. The number after the dash tells you what stock version the kernel was designed for (unless otherwise specified in the changelog).
2. How do I flash this?
A: Flash through recovery. If you're using systemless SuperSU and want to update your boot.img, just flash the boot.img, then flash your SuperSU zip over it. Works like a charm.
3. My bootloader is locked, HALP! OR I'm on AOSP/CM7/the Moon.
A: Then you don't get to install this kernel. Pretty simple but still, tough luck.
4.. What app do you recommend for dealing with CPU settings?
A: Kernel Auditor works for me. Go around the internet, try different apps and see what works for you, then keep it.
5. Touch Control doesn't work in rXXX release, you suckas, fix plixe! OR My phone exploded, HALP!
A: Go away. I do not respond to bug reports without a proper description and log.
6. I want to support you and your work!
A: Awesome! Click thanks and/or share the thread with other guinea pigs who would like to participate! The more people we get on this bandwagon, the faster I'm forced to work.
7. OP is arrogant, I'm gonna call the Internet Police? OR Why are you such a derp and asshole
A: Indeed I am. Deal with it.
8. Where may I find the discussion thread?
A: This thread serves as both the development and discussion thread. Please to not litter (GTFO with "thanks" and "+1" posts), and try to keep to the topic. That said, if you're reporting a bug or requesting a new feature, you may use either DevDB or the thread, but please tag me should you opt for the latter. Just remember, reviews go in the "Reviews" tab!
Special shoutouts to (in no particular order, all help is equal help):
AndroPlus, funiewski, Myself5, sm4tik, nelvinchi, franciscofranco, Freexperia and jerpelea, faux123, Google, Sony and HTC, all Nozomi developers, letama, oshmoun, olivieer, and that other guy (his name is tomascus by the way, he's a cool dude).
reserved?
Huge shoutout to my boys @oshmoun and @Myself5 for the help, drop them a thanks if you can be bothered!
i thought i had a reason for a third OP but i guess not, anyone have ideas?
Is it compatible with 23.5.A.1.238?
@someone755:
This was unexpected!
Big thanks to stay with xda communitiy. Thought we lost another dev because of "some" discussions (weeks/month ago)
And of course big thanks for this release...
alenbernardis said:
Is it compatible with 23.5.A.1.238?
Click to expand...
Click to collapse
According to the release notes I believe no, but you could always give it a try:
More testing, this time on Marshmallow. Clean, based off .575, no bugs found as of GMT 00:56, 25 July 2016. Only tested with .575, compatibility with .570 questionable. Further testing and development required.
Click to expand...
Click to collapse
Thanks someone755, I've installed it and so far so good.
I use this kernel with SLIMM v2.2 and is awesome thanks so much!
alenbernardis said:
Is it compatible with 23.5.A.1.238?
Click to expand...
Click to collapse
Oh come on dude please you're the first post.
Granted it's not explicitly stated but if you'd read the FAQ and changelog you'd know that 1) s3-575 is based around .575 and that 2) it's only been tested and reported working with .575.
Also to note is that .575 is the latest tarball available for shinano. I don't know if .238 has a different kernel or ramdisk, and I can't check, so I can't vouch for anything. You're free to test and report back so others don't have to worry though.
fluffi444 said:
@someone755:
This was unexpected!
Big thanks to stay with xda communitiy. Though we lost another dev because of "some" discussions (weeks/month ago)
And of course big thanks for this release...
Click to expand...
Click to collapse
Unexpected to say the least lol. I can't blame anyone but xda's collective hivemind for what has happened and is happening, but I needed this kernel for myself anyways, and honestly any feedback I can get is useful. You're not losing this dev for at least 4 more months!
Also thanks to everyone else for their contributions, if you don't get any errors on .238 (or Slimm 2.2 or whatever) I'll mark it as compatible. Cheers!
Has Sony released sources for the kernel used in Concept?
I'd love to have a few other governor options if this would work on MM Concept.
undervolting?
h4waii said:
Has Sony released sources for the kernel used in Concept?
I'd love to have a few other governor options if this would work on MM Concept.
Click to expand...
Click to collapse
Sadly, no. I don't know whether it works for that as well, and I still think they're breaking the GPL by not releasing them.
Does loading them as kernel modules work? If so you could just try that (though you'll need to compile those modules, if they'll even work with a different kernel).
aceoff27 said:
undervolting?
Click to expand...
Click to collapse
Well it's there, yeah. What you intend to do with it is all up to you though, I could never get anything stable other than the stock voltage table lol.
wow, great work man, I just installed and works perfect with SliMM 2.3. Looking forward for the next updates.
Keep up the great work
someone755 said:
Sadly, no. I don't know whether it works for that as well, and I still think they're breaking the GPL by not releasing them.
Click to expand...
Click to collapse
@someone755 I've asked them about sources on G+, here is my question and the answer(from today):
Q:
"I've asked about it earlier without any answer, so once more.
I've used Sony since Xperia Ray and the concept rom is the best one of any kind (official or custom like CM, omni, AOKP, you name it), but there is a really big flaw. Kernel sources are not published which stops development.As long as I understand the GPL Sony is obligated to publish them, so why are they not?"
A:
"Henrik Baard
+2
+ xxxxx, we are required by licence to upon request provide source code. Usually we put source in a location available so users can download GPL source.
We will look into providing this asap."
Now it's a possibility it will happen......
funiewski said:
@someone755 I've asked them about sources on G+, here is my question and the answer(from today):
Q:
"I've asked about it earlier without any answer, so once more.
I've used Sony since Xperia Ray and the concept rom is the best one of any kind (official or custom like CM, omni, AOKP, you name it), but there is a really big flaw. Kernel sources are not published which stops development.As long as I understand the GPL Sony is obligated to publish them, so why are they not?"
A:
"Henrik Baard
+2
+ xxxxx, we are required by licence to upon request provide source code. Usually we put source in a location available so users can download GPL source.
We will look into providing this asap."
Now it's a possibility it will happen......
Click to expand...
Click to collapse
**** this is some potentially good news. Just hope this doesn't turn out to be the Half-Life 3/Rocket League Linux client/Amiga Walker of kernel sources.
EDIT: Goddammit xda stop censoring my excrement.
Underclock values for psv8
For those who want to do undervolt I use these values are quite stable and save battery
Only for PSV8 bin MSM8974AC
268 Mhz - 650 mv
300 Mhz - 655 mv
422 Mhz - 670 mv
652 Mhz - 675 mv
729 Mhz - 695 mv
883 Mhz - 705 mv
960 Mhz - 715 mv
1036 Mhz - 745 mv
1190 Mhz - 765 mv
1267 Mhz - 775 mv
1497 Mhz - 805 mv
1574 Mhz - 815 mv
1728 Mhz - 840 mv
1958 Mhz - 885 mv
2265 Mhz - 945 mv
2419 Mhz - 975 mv
2457 Mhz - 980 mv
frixed said:
*snip*
Click to expand...
Click to collapse
Please don't before you get somebody's phone fried.
This phone comes in a couple different variations in terms of binning. Use these values on a chip from a different bin and you'll either be unable to boot (not enough power) or fry it (too much power). Not to mention the OnePlus One is a different device in the sense of thermal dissipation -- its larger surface area allows it to conduct heat away from the chip and phone faster than our Z3 Compact can.
That said, I would like to ask you to either remove this or to specify your bin and chip version, and wrap a
tag around the table.
someone755 said:
Please don't before you get somebody's phone fried.
This phone comes in a couple different variations in terms of binning. Use these values on a chip from a different bin and you'll either be unable to boot (not enough power) or fry it (too much power). Not to mention the OnePlus One is a different device in the sense of thermal dissipation -- its larger surface area allows it to conduct heat away from the chip and phone faster than our Z3 Compact can.
That said, I would like to ask you to either remove this or to specify your bin and chip version, and wrap a
tag around the table.
Click to expand...
Click to collapse
Sorry there edit specify what is my version PSV bin
I have saved drm keys, locked bootloader and latest slimm , how can i use with this kernel my keys? Or isnt necessary, becouse drm fix included to the kernel?
fromhungarytolnacounty said:
I have saved drm keys, locked bootloader and latest slimm , how can i use with this kernel my keys? Or isnt necessary, becouse drm fix included to the kernel?
Click to expand...
Click to collapse
If you apply the DRM keys you'll also relock the bootloader. So there's that.
If you want the DRM workaround hack or whatever you'll just have to flash it yourself.
someone755 said:
If you apply the DRM keys you'll also relock the bootloader. So there's that.
If you want the DRM workaround hack or whatever you'll just have to flash it yourself.
Click to expand...
Click to collapse
Ok. Thank you. After the bootloader unlock, what i have to do, for my drm keys working with this kernel?