Related
AniDroid-Hardened-TF101 Kernel
Short Kernel information:
AniDroid-Hardened Kernel is the first Hardened kernel for Android that uses GRSecurity subsystem to provide different useful Security functionality.
AniDroid-Hardened Kernel now is in early stage of developing but it's almost ready for using and testing on Asus Transformer TF101 and Google (Samsung) Nexus S devices
Provided Features:
Linux Kernel version 2.6.39.4
GRSecurity version 2.2.2 with different security features enabled by default (see GRSecurity Feature List for details)
EXT4, NTFS, CIFS support
init.d support
Compatible with any OTA-based and AOSP ICS Roms
1024 Kb ReadAhead support
Automatic Process Group Scheduling
-fstack-protector buffer overflow detection
GRSecurity Feature List:
Kernel Memory Protection (restrict read/write access to /dev/kmem, /dev/mem, and /dev/port)
Active Exploits Protection (deter exploit bruteforcing, active kernel exploit response)
Role Based Access Control (RBAC)
Filesystem Advanced Protection (including advanced security for applications running in CHROOT environment)
Full Kernel Auditing (event logging for many kernel events)
Executable Protection (deter ptrace-based process snooping)
Network Protection (TCP/UDP blackhole and LAST_ACK DoS prevention)
Managing support via Sysctl Interface
CPU Frequence Scaling Governors:
Ondemand (Default)
Interactive
Conservative
Powersave
Performance
IO Schedulers:
CFQ (Default)
Noop
Deadline (tweaked for flash devices)
Simple IO (SIO)
Links:
Current Kernel Binaries:
AniDroid-Hardened-TF101-Alpha1.zip
Other Kernel Binaries:
Old binaries on SourceForge
Kernel Source:
Will be available on GitHub soon..
Changelogs and issues info:
Alpha 1 known issues:
BCM4329 WiFi kernel module temporarely doesn't work
SU is temporarely cause "Permission denied"
WARNING!!!
AniDroid-Hardened-TF101 Kernel is still need testing!
So, you can flash and use this kernel at your oun risk!
Thanks to msticninja, guevor, eugene373, koush, ezekeel, supercurio, morfic, franciscofranco, sztupy, reddv1, byeonggonlee!!!
Great to see another kernel option. Awesome work, mate!
I'll give it a try.
hi!great to see new kernelz every week!after reading all the features in the nexus 3ad,i wonder if you'll put some of them un future in this tf's build...some of them i use every day on smartphones and are very Usefull..like touchwake,liveOC,BLX , fast charge and others..(fast charge especially)glad to test this kernel now,hoping that wifi works,anyway thanks for the hard work and keep it up in future release!i'll report how it goes...
sert00 said:
hi!great to see new kernelz every week!after reading all the features in the nexus 3ad,i wonder if you'll put some of them un future in this tf's build...some of them i use every day on smartphones and are very Usefull..like touchwake,liveOC,BLX , fast charge and others..(fast charge especially)glad to test this kernel now,hoping that wifi works,anyway thanks for the hard work and keep it up in future release!i'll report how it goes...
Click to expand...
Click to collapse
As far as I know, fast charge from a computer USB port isn't possible on the tf101 because it requires 12v to go into fast charge mode where a normal USB port only provides 5v.
Congrats on getting the kernel compiled with your changes. I'll post some fixes tomorrow that you might want to pull to your git. I have to be honest though, I don't really see the point of grsecurity on android. Do people actually get hacked?
noted but will flash when somebody got the balls to try...
Sent from my Transformer TF101 using xda premium
j3tt3 said:
noted but will flash when somebody got the balls to try...
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Never mind the balls, I don't see the point of flashing a kernel where wifi and SU (both quite critical in my opinion) don't work.
Basically, su won't work with GRSec because of the RBAC model. Another way needs to be found
Sent from my LT26i using XDA
K900 said:
Basically, su won't work with GRSec because of the RBAC model. Another way needs to be found
Sent from my LT26i using XDA
Click to expand...
Click to collapse
SU will work as privileged user can be allowed to run privileged operations useful for such apps as Titanium Backup and so on ..it's not GRSec issue - vanilla asus source have tha same issue for me.. it's either compiler or ramdisk problem..
novic_dev said:
SU will work as privileged user can be allowed to run privileged operations useful for such apps as Titanium Backup and so on ..it's not GRSec issue - vanilla asus source have tha same issue for me.. it's either compiler or ramdisk problem..
Click to expand...
Click to collapse
I meant that you need to either allow switching to root, which defeats the whole purpose of GRSec or use its own access controls, which needs to be done in apps.
Sent from my LT26i using XDA
K900 said:
I meant that you need to either allow switching to root, which defeats the whole purpose of GRSec or use its own access controls, which needs to be done in apps.
Sent from my LT26i using XDA
Click to expand...
Click to collapse
It will be an App
Sent from my Nexus S using xda premium
PROJECT: Backport essential OMAP drivers from OMAPZOOM 3.0.y Kernel into our 2.6.35 Source
Firstly, I would like to thank dhiru1602 for his CM9/CM10 builds in which he fixed up a lot of bugs single-handedly.
Also, thanks to rocker529 who helped me in this Project.
Me, and rocker529 have been working on this project for the last few weeks, and we have made some progress.
Since backporting Kernel 3.0 wasn't possible on our GT-i9003, I contacted dhiru1602 regarding what could be done in order to have a fully working CM9/CM10 port. Since, the OMAPZOOM Kernels would refuse to boot and no news about the LG Optimus Black Kernel Sources I decided to work on this.
According to my study/research and after a talk with dhiru.
The following would be needed to fix up all Video decoding/recording , camera, lag, HW Composer issues with our present CM9/CM10 builds.
We need-
Implementation of ION Memory Allocator.
What is ION?
ION is a generalized memory manager that Google introduced in the Android 4.0 ICS (Ice Cream Sandwich) release to address the issue of fragmented memory management interfaces across different Android devices. There are at least three, probably more, PMEM-like interfaces. On Android devices using NVIDIA Tegra, there is "NVMAP"; on Android devices using TI OMAP, there is "CMEM"; and on Android devices using Qualcomm MSM, there is "PMEM" . All three SoC vendors are in the process of switching to ION.
You can read more documentation here: http://lwn.net/Articles/480055/
Our progress:
We managed to backport all the ION drivers including our OMAP Specific ION Allocator driver. Fixed up all the errors. It will compile, even managed to get it to boot. However, the required sysfs enteries seem to be missing at /dev/ion . All that I get is some enteries in /debug/ion .
This could possibly be due to improper changes made to our board-latona. We need to initialize ion properly when our board initializes(omap_ion_init() and omap_register_ion() ) which I have failed to do due to no possibility of getting logs on splash screen when the Kernel is loaded.This port also required to new memblock drivers from Linux 3.0 which I have backported.
You can take a look at the changes at my github, please point out if I have missed out anything
Implementation of DSSCOMP-
A: DSSCOMP is needed to make our OMAP HW Composer to work. I have merged all the possible necessary drivers needed for dsscomp. Firstly, dsscomp needs implementation of OMAP ION. Despite of this, we have managed to fix up all the compile errors encountered in our Kernel Source. The driver will compile, but will not boot since ION is not working. Also, it does not go past the boot screen so there are no chances of getting a log.
Again, you can look at my github to see what I have done.
Besides this, we had to backport a LOT of stuff from the OMAPZOOM 3.0 Kernel ! You can take a look at the changes I have made in detail at my github repo..
If I have missed out something, or if I am doing something wrong please help. If we can manage to fix this we could possibly have a stable CM9/CM10 in future.
Please keep this thread [DEV-ONLY] and avoid posting noob questions.
Thanks.
Current progress: Backporting all dependencies for ion and memblock to work.Not sure it would boot though.
Compile from my sources
If you wish to help us I have made a small guide on how to compile your Kernel from my Sources-
Please do not ask me stupid questions like how to copy modules, toolchain error, etc. Proceed only if you have basic knowledge about Linux Kernel Compiling.
Toolchain I use and reccomend: arm-eabi-4.4.3 from CyanogenMod repo. You can find it here.
I would recommend making a github account since it is free and will make it easy for us to track changes, again don't ask me on how to use git, there is plenty of information over the Internet. Take time and search,read etc.
Clone my github repo
Download these boot.img tools.
I will be using directory /home/aditya/i9003 for my reference, you may use any.
Assuming our Kernel is in i9003/Kernel.
Unpack your boot.img tools into tools folder at i9003/tools.
Follow the README in the tools, and unpack CM9/CM10 boot.img.
In the tools/unpack folder make sure you have boot.img-ramdisk.gz (Thats the ramdisk, do not unpack it)
Download this and extract it in i9003/tools folder such that you get i9003/tools/out (This folder will have files needed for CWM zip and compiled modules will go here)
Change your toolchain path in Makefile, add your name to i9003/Kernel/scripts/mkcompile.h if you wish.
Thats done. Your build environment is set up.
Now just,
Code:
cd i9003/Kernel
./build.sh
Sit back and relax, the resulting Kernel will be automatically packed into a flashable zip in i9003/BETA_KERNEL#.zip.
Simply copy to sdcard and flash.
Hoping more people can contribute to development for i9003.
rocker529 said:
Current progress: Backporting all dependencies for ion and memblock to work.Not sure it would boot though.
Click to expand...
Click to collapse
The functions needed for omap_reserve() need to be backported, can you commit your changes? They are not booting as per the ones in the omapzoom 3.0 Kernel.
good luck u guys. have u missed to write "wifi fix" on the topic or,
fix up all Video decoding/recording , camera, lag, HW Composer
Click to expand...
Click to collapse
does it not depend on kernel?
all the best bro with your project and thx you to try it for our phone !:laugh:
i think it is an good idea to make our phone stable before porting kernel 3.x
Good luck in developing, looking forward to this project. :thumbup:
Happy sl user
Sent from my GT-I9003 using xda app-developers app
you should add battery solution cuz battery drain is huge compared by ginger kernel ... the old kernels like amits and vurrut so much better compared to cm kernels
thanks 4 ur effort and waiting 4 ur custom cm10 rom if allah want
Sent from my GT-I9003 using xda app-developers app
Dude like seriously,
I have so much of expectation from u guyzz (Y)
Good Luck !!
Sent from my Galaxy SL using XDA Premium App !!
dorukc said:
good luck u guys. have u missed to write "wifi fix" on the topic or, does it not depend on kernel?
Click to expand...
Click to collapse
From what I know, the wifi module is not compiled from the kernel source and the TI SDK is used to compile it. But ION and DSSCOMP will not help with wifi. For that we will need to seperately debug the wifi drivers (ti_wlan) .
Sent from my GT-I9003 using xda premium
Stuck up at the moment. The backported omap_reserve() functions aren't booting, getting stuck at splash screen. I'll wait, since hillbeast is busy now.. once he is free I will ask him for uart logs.. thinking of posting my kernel(cm10) for testing here , what say people?
Sent from my GT-I9003 using xda premium
^^ Go ahead and post it, but not on this thread. Leave this for development only.
I hope the kernel could be released soon AS possible
Sent from my GT-I9003 using xda app-developers app
Current progress and To-Dos:
The current progress is we are already having the board reserve memory for ion on startup. But since the reserve functions for vram, dsp, ipu and omapfb are not working, we need to backport all the functions and its dependancies from the omapzoom 3.0.y kernel.
To-Dos:
1.Have another brief look at omap_ion_init and omap_ion_register functions.
2.Try to backport the four functions from omapzoom 3.0.y kernel.
3.Have a check at memblock and mm drivers of our current kernel to check for dependancies.
4.If it doesn't boot, get UART logs from hillbeast for debug.
rocker529 said:
Current progress and To-Dos:
The current progress is we are already having the board reserve memory for ion on startup. But since the reserve functions for vram, dsp, ipu and omapfb are not working, we need to backport all the functions and its dependancies from the omapzoom 3.0.y kernel.
To-Dos:
1.Have another brief look at omap_ion_init and omap_ion_register functions.
2.Try to backport the four functions from omapzoom 3.0.y kernel.
3.Have a check at memblock and mm drivers of our current kernel to check for dependancies.
4.If it doesn't boot, get UART logs from hillbeast for debug.
Click to expand...
Click to collapse
Do you want me to edit the Kernel 3.x discussion thread to a backporting project (this) ?
Or simply create another independent one.
I think this topic is very well for questions and information and monitor progress
if there are no spam we get to the good times to follow.
Create a topic and put the other links on the first post when compared with the release obliged for calm languages lamp.
This is the topic of CM10 should have done as the section between dev and overall it is not clear
^^ Wait till Adi_Pat or rocker529 decide to post their test kernel here or maybe give it a unique name and make another thread. Then it would be time to have a q&a or discussion thread. Hopefully this thread wont attract much crowd till there's stuff to download.
Adi_Pat said:
Stuck up at the moment. The backported omap_reserve() functions aren't booting, getting stuck at splash screen. I'll wait, since hillbeast is busy now.. once he is free I will ask him for uart logs.. thinking of posting my kernel(cm10) for testing here , what say people?
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
it will be another kernel or the kernel with omap drivers frim linux 3.0 into your 2.6?
Skander1998 said:
Do you want me to edit the Kernel 3.x discussion thread to a backporting project (this) ?
Or simply create another independent one.
Click to expand...
Click to collapse
No need editing it, as the 3.0.y kernel work is mainly done by hillbeast, and our's is just a backport of parts of the 3.0 kernel to the current 2.6.35.7 kernel, which is separate and non related.
Mamica said:
it will be another kernel or the kernel with omap drivers frim linux 3.0 into your 2.6?
Click to expand...
Click to collapse
Just the old 2.6.35.7 kernel, with DSSCOMP, ION and other dependancies backported from omapzoom 3.0 kernel.
ooikaisheng529 said:
No need editing it, as the 3.0.y kernel work is mainly done by hillbeast, and our's is just a backport of parts of the 3.0 kernel to the current 2.6.35.7 kernel, which is separate and non related.
Just the old 2.6.35.7 kernel, with DSSCOMP, ION and other dependancies backported from omapzoom 3.0 kernel.
Click to expand...
Click to collapse
with this kernel the rom might works much better than with an old kernel?
Hi gents,
I'm looking for the way to read and write data on an usb pen drive using the OTG. Is there any apps the works on our nexus in oder to do that??
Any suggestion on this issue??
Thanks for your help
kernel
coluichepensa said:
Hi gents,
I'm looking for the way to read and write data on an usb pen drive using the OTG. Is there any apps the works on our nexus in oder to do that??
Any suggestion on this issue??
Thanks for your help
Click to expand...
Click to collapse
You must have a kernel that support OTG (like matr1x) and use a specific usb cable with external power like this one (ebay 140978662818).
----------------------------------------------------------------------------
Nexus S i9023 : 4.2.2 rooted stock ROM with Matr1x kernel
Archos 80G9 : cm10.1 with stock kernel
Will an OTG cable connected to a powered hub work also?
[email protected]
acro49 said:
You must have a kernel that support OTG (like matr1x) and use a specific usb cable with external power like this one (ebay 140978662818).
----------------------------------------------------------------------------
Nexus S i9023 : 4.2.2 rooted stock ROM with Matr1x kernel
Archos 80G9 : cm10.1 with stock kernel
Click to expand...
Click to collapse
Boeffla Samsung Kernel by AndiP
Ported and compiled by Hbohd and P$T
For i9305
Introduction
Note: The 4.x kernels are only for Samsung based 4.1.x roms!!! Do not install it on CM or AOSP based roms!!!
The 5.x kernels are only for Samsung based 4.3 roms!!! Also do not install it on CM or AOSP based roms!!!
After ausdim's contribution to porting variety of kernels to our phone, I am here to continue his work (he won't maintain it any longer because he simply doesn't own this phone now). Updates will be made as soon as Andi will push them to github.
Here is original thread of i9300 boeffla kernel - CLICK
Here is thread with boeffla ported by ausdim - CLICK
Info
Kernel is compiled using Linaro 4.9.1 with some required changes for our i9305:
No FM radio
No CMA_DMA
No flash and load in Boeffla App
New 'Hbohd preset' and 'PST preset' which are just our everyday use settings.
New 'Hbohd' and 'PST' equalizer preset - just our favorite.
Apart from that, everything is same as in i9300 version.
Please for any questions problems or anything else ask here and not on I9300 thread.
Credits
P$T (for helping hand with compiling and endless patience and time)
Ausdim (basing on his work and he always gives helping hand)
Yank (his endless patience and knowledge to help with any issue)
AndiP (for kernel base and another kind help)
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in CWM recovery and safely store your personal data before you flash a new kernel.
Source:
Here it is, github link! - CLICK
5.2 STABLE compiled with linaro 4.8.3 toolchain -->HERE
Newest version 5.3-beta7 compiled with linaro 4.9.1 toolchain (new ramdisk NE4) --> HERE
Camera bug info:
It appears that some people (like me) have problem with camera. In exactly THIS situation: do full wipe, flash sammy rom+boeffla kernel, reboot and launch camera. Effect? Camera closes with "camera failed" popup.
Possible solution:
1. Read this thread and follow steps --> click
2. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, then reboot to recovery and flash my ported kernel
3. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, grab file (SlimISP_XX.bin, where XX differs between phones) from /data/cfw/ and backup it where you want. Then if you can always copy it to /data/cfw if your camera doesn't work with my ported kernel. (ATTENTION: Unfortunately this file does not always appear - still don't know why )
Possible explanation, my own research:
I found out that people with ZD and GD will have camera working always. Why? Because these (SlimISP_XX.bin, where XX differs between phones) files are packed within kernel (zImage exactly) and ONLY THESE two are provided by Samsung in their opensource release... Interesting, isn't it? For example, I have GH version, which I may add to zImage manually, however adding more of them breaks the size limit for boot partition, so it's impossible to have all these versions together. However, stock kernel somehow has them, don't know how because zImages aren't extractable.
And just to confirm my theory, I've compiled a kernel with mine version of camera firmware, made full wipe, installed sammy rom+my kernel, rebooted, launched camera and voila - it worked
Thus, we has to live with this bug unless Samsung do something about it or someone else proves me that I'm wrong
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Installed let see how it goes...
Good work
Tank's
Sent from my GT-I9305 using Tapatalk 2
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Thanks.
Do you have any link or something where we can read about zzmoove governor tunables? I was searching, and searching and nowhere have I found a good explanation of all parameters.
I should probably look into sources you just gave a link for, but I am too tired atm.
Edit:
Oh that wasn't link to sources, but it doesn't matter, there has to be one somewhere in Boeffla thread.
Sent from my GT-I9305 using Tapatalk 2
My 'sources' are only one file - defconfig. The rest is completely same as Andi's sources
And for any explanation of zzmoove configurables - there is some documentation, quite well explained: https://github.com/andip71/boeffla-...48257af1b13/drivers/cpufreq/cpufreq_zzmoove.c
Cheers
Thanks for the port.
Over night I find this one better on battery than the last port. See how it goes with a bit of heavy usage today.
Sent from my GT-I9305 using Tapatalk 2
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
kazoum said:
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
Click to expand...
Click to collapse
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Hbohd it will continue the port of the boeffla kernel since i moved to the i9505.
Also i see Andip make some changes to the boeffla sound driver so it will work better.
Thank's
After 1 day with new kernel I can say the battery improve are the best an till now. Great job
Sent from my GT-I9305 using Tapatalk 4 Beta
Nice.. good job man..
Sent from my GT-I9305
Hbohd said:
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Click to expand...
Click to collapse
Well, I'm sad that a developer leaves this phone, but it is awesome to know that Boeffla will continue to be ported to I9305! The best part is the frequent updates Thumbs up!
I'm gonna try your port and will say something later.
beta6
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
dyy said:
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
Click to expand...
Click to collapse
What if I told you...
Beta7 is better than beta6
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
kazoum said:
What if I told you...
Beta7 is better than beta6
Click to expand...
Click to collapse
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Sincerely, I haven't experienced any random distortions of sound, everything works great. Obviously, if you raise headphone or speaker volume too high, it may be distorted, but it is understandable.
Or did you want to mention the problem with distorted/freezing/stuttering audio on screen-off? That was discussed and it might be caused due to too low screen-off frequency or too high sampling_rate and sampling_rate_sleep_multiplier. If it's the problem, try to change to zzmoove-optimised as it has this values changed a little bit.
About Perseus' screen calibration settings... As for now, introducing such thing would require adding multiple scripts to support variety of configurations for it (in boeffla app), change app to stweaks (which is quite tough task) or wait for new app which will come in some time, made by Andi (and in my opinion, will let us easily configure what we want).
What's more, personally I liked these calibrated colours, however, original colours also seem good to me So nowadays, I do not need it, although I might look at it in my free time and see what can I achieve
dyy said:
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
The fact is, that ausdim released beta4 or 5, I don't remember exactly, and then was my release beta7. And we somehow skipped beta6, you are right! However if I were you, I wouldn't take zzmoove 0.5 as 'unstable'. It introduces a great deal of new configurables that, I suppose will be really beneficiant in the future (when we all will learn what they mean ).
Version 0.5 is ONLY unstable when you are changing governors frequently. Otherwise, it is really efficient and bettery-friendly one (same as 0.3). In addition, it's my beloved governor since its start
Furthermore, new betas always consist of other updates (like Linux kernel upstream to 3.0.82, fixes, optimizations) so it is always worth to use the newest one!
As for now, you may stay with your actual beta version or wait for next update. Andi is testing comparison between zzmoove 0.3 and 0.5 right now, so he haven't pushed any sources, therefore I can't release any new update We are all impatiently waiting for the results i think!
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
inzomnia said:
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Have the same problem, no matter the governor i choose.
I try zzmove battery and pegasusq boeffla battery saving
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
I had this issue with boeffla but only when i used rxtreme rom, i never have it with ripper rom!
I am running the Blue Halo theme for M.O.A.R. 6.2. I have USB OTG Helper installed and can read NTFS formatted flash drives. But I cannot write. Is this a kernel limitation? Is there a kernel I can use with 6.2? Will MOAR 7 write to NTFS via OTG?
Please help,
Bob
I use chainfires stickmount app and don't have any issues at all.
Sent from my SM-G900P using Tapatalk