Q&A for [KERNEL] Project T - Custom Kernel for ZenFone 2
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 [KERNEL] Project T - Custom Kernel for ZenFone 2 . 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!
TheSSJ said:
and I packed it into a boot.img.
)
Click to expand...
Click to collapse
Hi. Tell me, please, how right pack bzImage with ramdisk into boot.img. I without problem compiling bzImage from Asus source code, than unpack stock boot.img with utility "zenfone 2 boot repack " by sorg, delete stock zImage from "boot" folder, put custom bzImage in "boot" folder, rename it to "zImage" and packwith utility "zenfone 2 boot repack " into boot.img, then flash this boot.img into phone with command fastboot flash boot boot.img, but device not start, white screen with logo Asus- and all. What I doing wrong?
BORETS24 said:
What I doing wrong?
Click to expand...
Click to collapse
The command line parameters screw up the information about the image data, as the boot command line parameters use double quotes ( " ).
So open img_info and delete the part in the command line parameters with the " signs. Also you need to enter the second addr and size params:
kernel : $kernel
ramdisk : $ramdisk
page_size : $page_size
base_addr : $base_addr
kernel size : $kernel_size
kernel_addr : $kernel_addr
ramdisk_size : $ramdisk_size
ramdisk_addr : $ramdisk_addr
below entries should be missing (or at least one of the two):
second_size : $second_size
second_addr : $second_addr
You need to enter that info into img_info file. If I have the time I will upload the img_info how itshould look like
Sorry, I don't understand a little, need make so?
BORETS24 said:
Sorry, I don't understand a little, need make so?
Click to expand...
Click to collapse
Nope, take the img_info in the attachment and replace yours with mine
With Your img_info my boot.img also don't working , zf2 didn't start,but i try singed modules off in menuconfig. Need disable all modules, right? in menuconfig all points "M" switch to "*" ?
Signed modules check only if the modules are fitting to the kernel by their signature.
Which kernel src version did you download?
I'm using source 2.19.40, AOSP 5.0.0_r7, KenelMakeFile from Asus, build kernel by command make -j4 -f KernelMakeFile TARGET_DEVICE=fhd modules_install
BORETS24 said:
I'm using source 2.19.40, AOSP 5.0.0_r7, KenelMakeFile from Asus, build kernel by command make -j4 -f KernelMakeFile TARGET_DEVICE=fhd modules_install
Click to expand...
Click to collapse
You need to issue 2 commands:
make -j4 -f KernelMakeFile TARGET_DEVICE=fhd build_kernel
make -j4 -f KernelMakeFile TARGET_DEVICE=fhd modules_install
Also make sure you first unpack source 2.12.40 and then copy 2.19.40 over it, then it should work
Yes, I know, what in source 2.19.40 lost IPU module. I'm unpacked 2.12.40 in working directory and unpacked 2.19.40 over with replacements. bzImage compiling without errors, in command prompt write "bzImage ready 6776Kb"
I'm install your kernel - device can't see MicroSD . I think this, because your ramdisk for firmware 2.19.40.18 or 20, and I have 2.19.40.22, I'm right?
BORETS24 said:
I'm install your kernel - device can't see MicroSD . I think this, because your ramdisk for firmware 2.19.40.18 or 20, and I have 2.19.40.22, I'm right?
Click to expand...
Click to collapse
You need update fw 2.19.40.22
Gửi từ ASUS_Z00AD của tôi bằng cách sử dụng Tapatalk
I have exactly 2.19.40.22, I'm wrire about this in previous post ! MicroSD don't working
Gửi từ ASUS_Z00AD của tôi bằng cách sử dụng Tapatalk
raynan said:
I am unable to see my external SD card in root browsers or when connected to my PC.
Click to expand...
Click to collapse
You have SDcard with exFat format? Custom kenlel not support exFAT, in source code of ASUS no exFAT drivers... While only use FAT32. I'm wrote to Asus support yesterday, that add exFAT in source
Fat32 sd cards work just fine on my custom kernel. Will see to add exfat support natively by the kernel config though (maybe it's turned off, but then ASUS did this by default already)
@TheSSJ do you have any idea of what is ospm_wake_lock is? is it related to screen on because the kernel wake lock only running on when the screen is on.
cangcan said:
@TheSSJ do you have any idea of what is ospm_wake_lock is? is it related to screen on because the kernel wake lock only running on when the screen is on.
Click to expand...
Click to collapse
This explains it really well: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=13469
Could you check the partial wakelocks please? Maybe ospm is taking up so much because an app doesn't release its wakelocks...
If change stock governor Interactive to any others and back to Interactive - all 4 cores works on max freq always. Required reboot that Interactive work right. Cat log write this:
07-14 22:14:43.925 E/Intel PowerHAL(628): Error opening /sys/devices/system/cpu/cpufreq/interactive/touchboostpulse: Permission denied
07-14 22:14:43.925 E/Intel PowerHAL(628): Error opening /sys/devices/system/cpu/cpufreq/interactive/touchboostpulse: Permission denied
07-14 22:14:43.934 E/Intel PowerHAL(628): Error opening /sys/devices/system/cpu/cpufreq/interactive/touchboostpulse: Permission denied
Hi @taylor.fowler,
Here is the L Speed mod flashable zip originally found here by Paget96: http://forum.xda-developers.com/android/software-hacking/tweak-l-speed-v1-0-02-02-2015-t3020138
Its shows this message with TWRP 2.8.7.0 ZE551ML: Error executing updater binary in zip
Edit: I am not able to see the upload option.
Related
i have pushed the board files to my github to compile a fully working kernel for the GSM Hero. i dont own the device, but Behnaam has been working with me testing and such. anyhow everything works. the link to my source can be found below:
GoDmOdE-KeRnEl-SoUrCe
anyhow enjoy i do this for the community and ask for nothing but in return. Devs have at it!!!
Behnaam already beat you to the punch, link.
gu1dry said:
Behnaam already beat you to the punch, link.
Click to expand...
Click to collapse
i seen but i can update this one plus i guess i forgot to add two files . btw they are there now and it will compile for sure. (i just did it) enjoy
will it say no more huge battery drain ?
Quick and dirty compile by me in boot.img format (too tired to hack an update.zip together)
Credit to: Benocharm, and well everyone else who worked on this project... i just compiled it lol
EDIT: Had a lapse and forgot to compile a new wlan module... will reupload after school today
Cant post links yet sooo h**p://w w w .mega upload. c o m/ ? d = 724NZ7Q1
** = tt
remove spaces
Method One Flash: (For those with unlocked SPL)
fastboot flash boot newBoot.img
fastboot reboot
Method Two Flash:
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
- write: No space left on device [this is ok, you can ignore]
flash_image boot /sdcard/boot.img
reboot your phone
zjr8 said:
Quick and dirty compile by me in boot.img format (too tired to hack an update.zip together)
Credit to: Benocharm, and well everyone else who worked on this project... i just compiled it lol
Cant post links yet sooo h**p://w w w .mega upload. c o m/ ? d = 724NZ7Q1
** = tt
remove spaces
Method One Flash: (For those with unlocked SPL)
fastboot flash boot newBoot.img
fastboot reboot
Method Two Flash:
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
- write: No space left on device [this is ok, you can ignore]
flash_image boot /sdcard/boot.img
reboot your phone
Click to expand...
Click to collapse
Here ya go mate
http://www.megaupload.com/?d=724NZ7Q1
Are the video drivers included?
MerXury13 said:
Are the video drivers included?
Click to expand...
Click to collapse
I think that's very basic that they check it .
I'm more curious about other things that are not so obvious while testing:
volume keys while sleeping, battery usage, g-sensor, correct behavior of the audio jack (audio switches to jack instead of speaker), etc...
'gsm long text > 160 chars' issues can't have anything to do with the kernel used as I see it. That's something of the messaging app and / or the radio RIL used.
Hmm, new kernel to play with... might be the push I needed to try building my own android stuff to learn
Am I missing something with regards to the wlan module sources? Didn't see them so far...
Or am I being stupid (highly likely)
Are the video drivers included?
Click to expand...
Click to collapse
I think that's very basic that they check it .
I'm more curious about other things that are not so obvious while testing:
volume keys while sleeping, battery usage, g-sensor, correct behavior of the audio jack (audio switches to jack instead of speaker), etc...
'gsm long text > 160 chars' issues can't have anything to do with the kernel used as I see it. That's something of the messaging app and / or the radio RIL used.
Hmm, new kernel to play with... might be the push I needed to try building my own android stuff to learn
Click to expand...
Click to collapse
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
MerXury13 said:
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
Click to expand...
Click to collapse
It's too early for me^^ sorry
dipje said:
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
Click to expand...
Click to collapse
The normal 'stable' version of his ROM is built on the same test kernal that every other 2.1 ROM is built on.
MerXury13 said:
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
Again... getting boring
Can someone please compile this one with overclock patch?I have no idea how to compile from source else I would do it
l0st.prophet said:
The normal 'stable' version of his ROM is built on the same test kernal that every other 2.1 ROM is built on.
Click to expand...
Click to collapse
Hence it got video drivers
Can anyone point me in the direction of a good write up on how to build a boot.img from this git repo please?im using ubuntu 10.4
so can we use this kernel on the vanilla roms?
anon2122 said:
Am I missing something with regards to the wlan module sources? Didn't see them so far...
Or am I being stupid (highly likely)
Click to expand...
Click to collapse
Do you have the latest commit? I believe initially there were some missing files. I know when I grabbed the source the first time i had wlan drive compile issues
I applied this to both cronos rom and to superhero rom and both got really sluggish after installing it (I used the boot.img posted among the first posts).
Android Development How-To: Compiling the Android/Linux kernel for the Epic Touch 4G.
NOW INCLUDES ROOT!!!
Introduction: This guide is meant for people who want to get started with android development and don't know where to start. This thread can also be used as a reference place for android development on the et4g. This guide well first be on compiling the android kernel and flashing it to your phone and, I well update it on a regular basis for more complex mods and such to get you familiar with the android platform. If at anytime anyone would like to add more to this, pm me with what you would like to add or fix. Android is an open-source wonderland and I feel like more people should experience the fun of android development. Just remember I am not responsible if you do something stupid and break your phone!
First, we are going to get familiar with the android kernel by compiling a stock build and flashing it with Odin to your et4g.
What you need to download to compile the kernel:
Samsung open-source kernel and platform files. Available at: Samsung Open Source
Type in: Sph-d710 in the search bar in the link and download latest source.
initramfs files (More on this later) (includes cwm, busy box, and of course root! Thanks to chris41g for his help.) Files available at: Initramfs Files
Tool chain for compiling: Available at: Arm-toolchain
Preferably Ubuntu or another Distro. Of Linux running on a partition or Virtual machine.
Step 1: Were going to unzip the source you got from Samsung and take a short look around.
unzip the source and unzip the file that says, “SPH-D710_GB_Kernel.tar.gz” and, open it up. You are now looking at the kernel source for the Epic touch 4g! Okay I well not go over to much whats is here but, I well add a more in depth look in the kernel soon.
Scroll to the bottom of the source and you should see a document that says, "makefile". We are just going to add a name for your stock compile of the kernel, to make it a little more special. Open it and go to where it says Extra version and add your last name ,just make it all lower case letters or it wont compile correctly. When you flash it to your phone, the about phone panel in setting well say: Kernel version: 2.6 [last name you chose] now.
Step 2: Lets get started!
Open terminal in Linux and change your directory to the kernel. You do this by putting,
“cd” and then typing where your kernel source is then hit enter. My terminal looked like this:
cd /home/shane/Desktop/SPH-D710_GB_Kernel
Click to expand...
Click to collapse
Step 3: Tell terminal where your tool chains you downloaded are located.
The kernel is compiled using a tool chain, and the terminal needs to know where the tool chain is to compile. (The tool chain is the folder called “arm-2009q3” )Start by typing this in the terminal:
export CROSS_COMPILE=
Click to expand...
Click to collapse
Then after that put where your tool chain is located. Also when you are entering where it is at, you need to put a “/bin/arm-none-eabi-” at the end of the directory. This shows the terminal that the compiling tools are under the folder bin and starts with arm-none-eabi- and the android compilation adds the last word for the compiler program it needs. (you can see this if you go into the bin folder under the “arm-2009q3 folder.) For adding the tool chain I entered this:
export CROSS_COMPILE=/home/shane/Desktop/arm-2009q3/bin/arm-none-eabi-
Click to expand...
Click to collapse
Then hit enter.
Step 4: Clean the kernel, enter configuration files and make the modules.
Enter this command:
sudo make clean
Click to expand...
Click to collapse
Then enter password and hit enter.
Then it well say something like:
make: /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-gcc: Command not found
Click to expand...
Click to collapse
IGNORE THIS! It is just a fragment in a configuration file that says the toolchain is not in the default location. But, we changed the tool chain location in step 3 so it well compile correctly.
This cleans up and organizes the kernel for compilation.
Now enter this command in terminal:
make c1_rev05_na_spr_defconfig
Click to expand...
Click to collapse
This is the configuration files for the epic touch 4g and well compile the kernel based off what is in these files.
Now were going to compile all the modules so wifi,vibration... work.
Enter this in terminal:
make modules
Click to expand...
Click to collapse
Step 5: Moving the newly compiled modules to the initramfs/lib/modules folder.
We are now going to move the modules from the newly compiled modules to the initramfs files. So that wifi and vibration well be working in our kernel.
*Initramfs files are the root filesystem of the kernel and does processes the kernel can't do itself while its booting.
You can do this by terminal or by hand. We are just moving the modules to the initramfs to be used when compiling the kernel.
You can type this into terminal (Where it says “Path to initramfs” you need to replace with your own path to the initramfs folder + /lib/modules) :
cp drivers/samsung/j4fs/j4fs.ko Path to initramfs/lib/modules
cp drivers/scsi/scsi_wait_scan.ko Path to initramfs/lib/modules
cp drivers/bluetooth/bthid/bthid.ko Path to initramfs/lib/modules
cp drivers/net/wireless/bcm4330/dhd.ko Path to initramfs/lib/modules
cp drivers/samsung/vibetonz/vibrator.ko Path to initramfs/lib/modules
cp drivers/staging/westbridge/astoria/switch/cyasswitch.ko Path to initramfs/lib/modules
Click to expand...
Click to collapse
This copies the new modules out of the kernel source and puts them in the initramfs/lib/modules folder to be used later.
Now once you enter that press enter.
Step 7: Compiling the android kernel with initramfs.
Type this in terminal:
make -j5 CONFIG_INITRAMFS_SOURCE=Path to initramfs file
Click to expand...
Click to collapse
*Remember to replace the “path to initramfs file” with the path to the initramfs file.
Okay this well take anywhere from 5-15 mins. to compile depending on your system.
Step 8: Were done compiling, lets make something flashable for Odin!
Just type in terminal:
cd arch/arm/boot/
Click to expand...
Click to collapse
Then type:
tar cvf MyKernel.tar zImage
Click to expand...
Click to collapse
This well zip up the zimage (the kernel) you just compiled to something flashable in odin.
If you open up the kernel source file and go to arch/arm/boot you well see the zimage you compiled and, the Mykernel.tar file for Odin. Double check and right click on the zimage and make sure it is around 5-6 MB before flashing.
Step 9: Flashing to your phone.
Go to a windows computer and download Odin.(if you have rooted your phone using zedomax's method you should have it installed already)
Okay now open it up and place the Mykernel.tar file in the PDA section of Odin. Now download the drivers for your phone if you haven't.(I assume you already have.) Then put your phone in download mode (hold volume down button and power button on start up and push volume up button when the warning pops up) Now plug your phone into the computer and make sure “auto-reboot” is the only box checked in Odin. Hit start and your phone well be flashed with a kernel you compiled yourself! If you did this right your phone should start up. If it is stuck in a boot loop, immediately put back in download mode and flash to stock. Link available here to stock files:
http://forum.xda-developers.com/showthread.php?t=1409634
and, try to figure out what you did wrong while compiling and try again!
Good job you have finished!
Step 10: The future and your new phone!
I would like to include more android kernel mods and stuff in the future but, wanted to get this out there to get people familiar with the android compiling process. I want this guide to be something people reference as they start to develop, by using the methods here along with kernel and U.I mods on the platform being implemented in the future. My ultimate goal is to at least know I helped at least one person get into android development so, if I helped you please leave a reply or say thanks. If anyone has ideas to add to the post, please pm me.
Have fun developing!
I'll take this...
and this...
One more...
Awesome!!!! I have been patiently awaiting this. THANK YOU SOOO MUCH!!!!
Sent from my SPH-D710 using xda premium
Thank you! Definitely will be referring to this during my free time. Can't wait to see what else gets added
Sent from my SPH-D710 using xda premium
Awesome!! tyvm!!
Wow... How awesome is this? I have been looking for something like this for a long time. I will be watching for updates. Thank you very much.
all u need now is a video tutorial
My man!!! Thank you for this!!
Sent from this phone
Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?
dtm_stretch said:
Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?
Click to expand...
Click to collapse
It all depends if you wanted to flash a already made custom recovery (cwm) then we would just haved to root the kernel then build and flash the recovery. If you were to make a fully custom recovery with custom functions made by you then it could get a little more tricky but, I am guessing you just mean flashing a custom recovery like cwm. Which is not terribly hard but, not neccesary easy eather depending on how hard it is to obtain root.
I might update the guide in the future. Showing how to do something like this but, I have a few more ideas for the guide before I include this.
You nailed it, I was curious about adding root and CWM(or a variation of it). I am more than content with figuring out what you have posted so far.
Thank you so much. This is absolutely great!
Sent from my SPH-D710 using XDA App
Awesome guide. Thank u so much for this. Hope for many more.
Sent from my Nexus S 4G using xda premium
Very awesome thanks for the share!!
Sent from my SPH-D710 using XDA App
Great Guide!
Very informative and well put, Thank You.
thank you very much for this! Gives me something new to try out. Thanks again!!!
Sent from my SPH-D710 using Tapatalk
Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!
obelisk79 said:
Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!
Click to expand...
Click to collapse
I hope it helps!
InformationThis kernel is forked from the CyanogenMod Kernel and i have added a few additional changes of my own and more to come. My builds of AOKP and Gummy have this kernel pre-installed with the Kanged Gummy Kernel but when i release 1.0 it will have a few more tweaks so you would need to upgrade.
There will be 4 files you can download. The boot.img and zImage can both be flashed using Heimdall. The Flashable zip and Odin tar.
Bugs
Deep Sleep works but when using LiveOC it does not so i recommend only using this when playing games or maybe make a script to disable this when you device locks in the time being.
Differences
LiveOC
More Frequencies (100MHz, 200MHz, 400MHz, 600MHz, 700MHz, 800MHz, 900MHz, 1000MHz, 1100MHz, 1200MHz, 1300MHz, 1400MHz)
Lulzactive v2 Governor (My preferred choice)
Tiny shmem
Working on more!
Using Features In The KernelLiveOCHere is information on it This is configurable using a tool known as NSTools on the PlayStore. When using this 100% means the bus frequency is at 100% try not to get confused. So 100% of 100MHz would be 100MHz so if you increase it to 120% so it would be 120% of 100MHz would be 120MHz and this value applies to all CPU frequencies, GPU ect.
LulactiveThis is like other governors for the CPU and can be configured using applications like Voltage Control, SetCPU, NSToolsand built-in tools from CM9/10 and AOKP ect.
Downloads
All Devices - http://goo.im/devs/henryedwardrose/Kernel/ICS
P1 - zImage - Boot.img - Flashable.zip - Odin.tar
P1L - zImage - Boot.img - Flashable.zip - Odin.tar
P1N - zImage - Boot.img - Flashable.zip - Odin.tar
Installation
zImage or boot.img
Use command line tool known as 'heimdall' (for people comfortable with the command-line)
Flashable.zip
Installed using CWM (the easiest methord)
Odin.tar
Put this file in the PDA section on Odin (Windows only)
Special ThanksThe TE4M - Nice work on developing the kernel and getting our device officially supported by CyanogenMod!
Dizgustipated - Nice Guy, Excellent Roms and Kernel!
Technomancer - The Guy who originally ported CM7 to our tab
SourcesMy Github
BuildingYou can build this kernel yourself in two ways
The First MethordIs by adding it into your manifest in your android build environment which supports integrated kernel building like CM9/10 and AOKP.
If you want it in your own Rom then simply just perform the regular build commands
If you just want to build a boot.img then apply the following commands
source build/envsetup.sh
lunch cm_p1-userdebug (change this depending on what device you would like to build)
make out/target/product/p1/boot.img
Click to expand...
Click to collapse
The Second MethordBefore the integrated kernel building system you used to build a kernel outside of this in it own separate environment so i have made it possible without have to download the android build environment to build any kernel for this device and you just have to run a build script and tell it what device you want to make.
Firstly you want to use the following commands
mkdir Kernel
cd Kernel
repo init -u https://github.com/henryedwardrose/Kernel_Manifest.git -b master
repo sync
Click to expand...
Click to collapse
Ok when synced you will see that there are three directories. Two of which are what you need. The 'Files' directory
is where all of the other files go that are necessary to build the kernel. The build.sh is a nice bash script which
you can open and easily understand what commands are being executed and how the files are being used.
Anyways here's how you build:
Firstly in the terminal go to the Files directory
cd Files
Click to expand...
Click to collapse
Now run this following command to extract the ramdisks (you only have to do this when i have uploaded a new ramdisk)
./RUNAFTERSYNC.sh
Click to expand...
Click to collapse
Then you want to build the kernel and at the end you will end up with the following flashable files 'zImage,
boot.img, .tar, .zip'
Now you need to initiate the building process
./build.sh
Click to expand...
Click to collapse
Now follow the commands on screen and you will end up with the kernel located in the out directory and you can flash
via Heimdall (zImage and Boot.img), Odin (.tar) and CWM (.zip)
Enjoy!
Thanks for you work...
Please build for all model (P1,P1l,P1N, P1C)..
a-vista said:
Thanks for you work...
Please build for all model (P1,P1l,P1N, P1C)..
Click to expand...
Click to collapse
oops! forgot this information lol :silly: Of course, well except for P1C atm
thanks for kernel. love your work bro.
i flashed on my p1. im trying and write back here for bugs etc.
can someone post some screen shots..???? PLEASEEE...
[email protected] said:
can someone post some screen shots..???? PLEASEEE...
Click to expand...
Click to collapse
ScreenShots from what???
This is a kernel, nothing changes visually...
Just performace, battery..etc..
hi
thanks again your work.
i tried kernel but it doesnt going into DEEP SLEEPtab working always 1200.
my options is smartassv2 and sio.
Used this kernel can be used camera 360 ?
It feels smooth indeed. Quadrant score at 1300 MHz with Cm9 is around 2600-2700.
Kernels includes CWM right? I wonder if I can have this on my P1000N stock GB 2.3.3.
Sent from my HTC Desire S
Hi henry.
My tab is p1000 and im on your aokp milestone 6 (not the rebuild 1). I decided to update my kanged gummy kernel to 1.0 as suggested in the op. I tried the zip for p1 using cwm recovery, and my tab was stucked to the samsung logo. Cant go to recovery too. So i decided to use the .tar in odin, and its now perfectly.
Just a heads up that there maybe something wrong with the zip version. But neverrtheless, thanks for this wonderful kernel!
I have a p1 too and i have download cwm file i have instal it with no issue.
Maybe a wrong download ?
@Henry,
with rebuild 1 kernel is the latest kernel or i have to redownload and install ?
Thank's
Hope someone can upload it to other sites. Rapishare really sucks.
Sent from my GT-N7000 using xda premium
MarlX said:
Kernels includes CWM right? I wonder if I can have this on my P1000N stock GB 2.3.3.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Yes it does, yer you can and will install but it will NOT boot unless you have ICS on your device.
vince_junior said:
Hi henry.
My tab is p1000 and im on your aokp milestone 6 (not the rebuild 1). I decided to update my kanged gummy kernel to 1.0 as suggested in the op. I tried the zip for p1 using cwm recovery, and my tab was stucked to the samsung logo. Cant go to recovery too. So i decided to use the .tar in odin, and its now perfectly.
Just a heads up that there maybe something wrong with the zip version. But neverrtheless, thanks for this wonderful kernel!
Click to expand...
Click to collapse
Thank you for your report its always appreciated It has worked for me and i have a p1 but i will test it soon again to see if i have any issues
chickygamon said:
I have a p1 too and i have download cwm file i have instal it with no issue.
Maybe a wrong download ?
@Henry,
with rebuild 1 kernel is the latest kernel or i have to redownload and install ?
Thank's
Click to expand...
Click to collapse
There is no need to install it but if you install this one it won't hurt its the same.
Gpsrisk said:
Hope someone can upload it to other sites. Rapishare really sucks.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I will upload it to goo.im soon but working on jb atm
henryedwardrose said:
I will upload it to goo.im soon but working on jb atm
Click to expand...
Click to collapse
Wow!
New Link
Hey, Uploaded All files to Here now;
http://goo.im/devs/henryedwardrose
Click to expand...
Click to collapse
enjoy!
henryedwardrose said:
Hey, Uploaded All files to Here now;
enjoy!
Click to expand...
Click to collapse
Something wrong with goo.I'm server. ?
Sent from my GT-P1000 using Xparent ICS Tapatalk 2
well this sucks all links are broken
tohno said:
well this sucks all links are broken
Click to expand...
Click to collapse
Goo.im are down atm i am going to upload them again when they are back up. In the mean time i am working on a few things and i may rebuild the kernel with gcc 4.6 check the op are the links still working on rapidahare?
Sent from my GT-P1000 using xda app-developers app
Today was released the source of the China version kernel
Can be downloaded here: http://consumer.huawei.com/cn/mobil...pport/downloads/detail/p6-u06-cn.htm?id=16381
Great new, but we need to support to unlock the bootloader
S34Qu4K3 said:
Today was released the source of the China version kernel
Can be downloaded here: http://consumer.huawei.com/cn/mobil...pport/downloads/detail/p6-u06-cn.htm?id=16381
Great new, but we need to support to unlock the bootloader
Click to expand...
Click to collapse
This is good, hopefully we can get some underclocking and some kernel governors on this beast of a phone
And most important, battery and wifi tweaks. There are the weakeness of this phone (i think)
Sent from my HUAWEI P6-U06 using xda app-developers app
S34Qu4K3 said:
Today was released the source of the China version kernel
Can be downloaded here: http://consumer.huawei.com/cn/mobil...pport/downloads/detail/p6-u06-cn.htm?id=16381
Great new, but we need to support to unlock the bootloader
Click to expand...
Click to collapse
Link is Dead
GuneetAtwal said:
Link is Dead
Click to expand...
Click to collapse
Here you got it, in my git repo: https://github.com/S34Qu4K3/P6-U06-JellyBean-Kernel-3.0.8---China-Version
S34Qu4K3 said:
Here you got it, in my git repo: https://github.com/S34Qu4K3/P6-U06-JellyBean-Kernel-3.0.8---China-Version
Click to expand...
Click to collapse
are you able to compile it ...?, how to get default device config file, adb pull /proc/config.gz gives file does not exists.
Latest Download Path : http://download-c.huawei.com/download/downloadCenter?downloadId=16381&siteCode=cn
Edit:
i am able to find default config for this kernel in this path :
/kernel/arch/arm/configs/hisi_k3v2oem1_defconfig
New modules CIFS/USB Ethernet
sreeramu said:
are you able to compile it ...?, how to get default device config file, adb pull /proc/config.gz gives file does not exists.
Latest Download Path : http://download-c.huawei.com/download/downloadCenter?downloadId=16381&siteCode=cn
Edit:
i am able to find default config for this kernel in this path :
/kernel/arch/arm/configs/hisi_k3v2oem1_defconfig
Click to expand...
Click to collapse
Thanks, got my Trendnet TU2-ET100 USB ethernet adapter working (modules attached)
And, CIFS support
oh, and ext3 filesystem also
Modules to be placed in /system/lib/modules are attached for kernel version 3.0.8-00788-g5d19ba2
build.prop
Nees to recompile for ext3 journaled
Hi, here is tool for making flashable zip in few commands! No need root! In few commands your rom is ready for sharing or flashing with CMW ! You can dump any rom! NOTE: all your rom changes which is in your phone will be included in rom.zip (for example busybox, su...etc)! Tool will be usefull for dumping next Sony stock rom, but allso all rom is supported! Enjoy!
For no rooted devices:
adb push romgen /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 romgen
Code:
./romgen C6903 honami /dev/block/platform/msm_sdcc.1/by-name/system /dev/block/platform/msm_sdcc.1/byname/userdata /dev/block/platform/msm_sdcc.1/by-name/cache [COLOR="Red"]/dev/null[/COLOR] /storage/removable/sdcard1/rom.zip
/dev/null must be used as a boot partition since no rooted devices have no access to these device!
For rooted devices:
adb push romgen /data/local/tmp/
adb shell
su
cd /data/local/tmp
chmod 755 romgen
Code:
./romgen C6903 honami /dev/block/platform/msm_sdcc.1/by-name/system /dev/block/platform/msm_sdcc.1/byname/userdata /dev/block/platform/msm_sdcc.1/by-name/cache [COLOR="Red"]/dev/block/platform/msm_sdcc.1/by-name/boot[/COLOR] /storage/removable/sdcard1/rom.zip
Download tool:
http://forum.xda-developers.com/showthread.php?t=2533585
munjeni said:
Hi, here is tool for making flashable zip
Click to expand...
Click to collapse
is it stable already?
I mean the Meta-INF generated completely?
thanks gonna try this if the tool complete
nelikp said:
is it stable already?
I mean the Meta-INF generated completely?
thanks gonna try this if the tool complete
Click to expand...
Click to collapse
Yesterday I noticed bug There is bug when folder is empty or when symlink is inside folder but there no other files! So when tool generate zip these folder is missing in zip but updater-script have line "set perm to folder" which not exist, so installation aborting because a missing folder Will try to solve them soon! Do not flash generated zip since you will get boot loop (you can only if you add missing folders to zip)! I will make new version soon, hope clean!
New version is out! Hope all bugs solved! Bug is solved by creating empty file .placeholder to all existing folders so zip for sure now have all mised folders, than placeholders is auto removed at finish of the installation
I am hope eerything is right now, but I will test and let you know if generated zip is installable with sucess!
New working version finaly, sorry! Now I tested tool and found another 2 bugs, first one was "zip fail to store file which contain special characters like *()...etc", and seccond one was wrong format of the permssions in updater-scrip. Now all things is solved, I have tested tool, tried to install generated zip, installed zip, and bum. Everything is ok now, enjoy!
Hi mate...nice to see you here
If I'm correct, you have some great work and kernels in your biography
Sent from my C6903 using Tapatalk
funky0308 said:
Hi mate...nice to see you here
If I'm correct, you have some great work and kernels in your biography
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
No space left in my signature :laugh: One oftopic question, anyone have info when Sony will anounce 4.4.2 ?
munjeni said:
No space left in my signature :laugh: One oftopic question, anyone have info when Sony will anounce 4.4.2 ?
Click to expand...
Click to collapse
Yeah...I'm using Tapatalk so can't see...but, as I said, I know who you are and we will be very happy if you join Z1 development :thumbup:
It should be out (most likely) in a first few days on april (let just hope it won't be first April and we.won't be April's fools )
Some of Z2 apk files are already out and if that guy who already post few things managed to post Z2 system dump - we could have something even earlier
Sent from my C6903 using Tapatalk
I am allready in development on Z1 Compact but curently I have problem in semc_colorizable (going to start working in MIUI), so first of all I need to solve all things related to the recompiling framework-res and full removal of the semc_generic_uxp... by now have no luck Did you have luck on framework-res on Z1 using apktool ? I have managed to recompile/compile them by now, but boot loop on colorizable things since my modificaions on framework / framework-res is not complete .
munjeni said:
I am allready in development on Z1 Compact but curently I have problem in semc_colorizable (going to start working in MIUI), so first of all I need to solve all things related to the recompiling framework-res and full removal of the semc_generic_uxp... by now have no luck Did you have luck on framework-res on Z1 using apktool ? I have managed to recompile/compile them by now, but boot loop on colorizable things since my modificaions on framework / framework-res is not complete .
Click to expand...
Click to collapse
@munjeni bro, you can try out the Advanced APKtool by @BDFreak bro for the framework-res issues. It's compatible with z1 Compact.
http://forum.xda-developers.com/showthread.php?t=2639400
@munjeni, nice tool, but I need help. I get this error in CWM log every time I try to install my zip; "l:Can't partition non mmcblk device: /devices/msm_sdcc.2/mmc_host
What do I need to do to the updater script? I tried replacing the mount system bit with;
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("system", "/system");
but I had no luck.
Probably you pased bad command to the romgen since you say /devices/msm_sdcc.2/mmc_host !!! Double check first post before you going to generate zip! Or probably you using an bad cwm which have bad fstab! If no of these 2 simptoms is true than for sure you have modified updater-script by your own way which probably is not ok! Hope this help.
munjeni said:
Probably you pased bad command to the romgen since you say /devices/msm_sdcc.2/mmc_host !!! Double check first post before you going to generate zip! Or probably you using an bad cwm which have bad fstab! If no of these 2 simptoms is true than for sure you have modified updater-script by your own way which probably is not ok! Hope this help.
Click to expand...
Click to collapse
Okay so it's the bad fstab, thanks man
Can anyone make rom for my karbon a39 HD