Hello everyone, I am now using this Android build fusion and it works well to me:
1. system.img from xdandroid FRX05 (Android 2.2.2)
2. XDAndroid latest Kernel,initrd and rootfs
3. Latest 11.29 3D drivers with Gralloc
4. Phone overclock to 614.4Mhz
INSTRUCTIONS:
1. Get the latest kernel,initrd and rootfs from the Attached Files below (XDAndroid Latest Set)
EDITED- OUTDATED AND REMOVED
2. Get the Latest 11.29 3D drivers with Gralloc from the Attached Files below (3D Driver)
3. Extract 3D Driver and you have the following:
i) gralloc.msm7k.so and libGLES_qcom.so
ii) libGLESv2_adreno200.so and libq3dtools_adreno200.so
iii) bootanimation.zip, build.prop, froyo.user.conf
4. Extract XDAndroid Latest Set and you have the following:
i) zImage
ii) initrd.gz
iii) modules-2.6.27.46-01231-gfca2168.tar.gz
iv) rootfs.img
5. Put everything above on root sd card, STARTUP.TXT and ts-calibration use the one that you use for your device
7. To overclock your phone, just add acpuclock.oc_freq_khz=X to your cmdline on ur STARTUP, where X is the desired frequency in KHz, I overclock it to 614400KHz
8. Sometimes the Wifi will show an error, just delete the module and zimage in SD card and then recopy it from your PC
9. To prevent Wifi error, my suggestion is NEVER TURN OFF your Wifi
Results:
1. Wifi, Bluetooth, GPS, Market works
2. Speaker works and no more 'hizzing' sound
3. 3D graphic little bit slow but the good news is no flickering
4. Charging works in Android
5. Mic works
6. Camera still not working (Preview only)
7. Fps2D: 28
8. Neocore with sound: 19.1 FPS
9. Neocore without sound: 21.0 FPS
10. Good battery life
11. USB works
Good luck for testing and sorry for my English
EDITED: FRX04 IS OUT..IMPROVED 3D PERFORMANCE
1/3/2011-FRX05 OUT
1. Download the latest Rootfs and replace it with the older one
I don't think libGLESv2_adreno200.so, and libq3dtools_adreno200.so will be loaded for msm7k devices.Why did you need to load adreno library for Nexus or armv7 devices
works
works, but with custom kernel and startup file, sometimes wireless fails but the rest works good
run's better then gindebread (alpha release)
testing the charging mode...
ok thx, i'm testing it...
To prevent wifi error, my suggestion is NEVER turn off wifi..if the wifi show error after turn off, you have to delete the module and zimage in your SD card and then recopy it from your PC
Can't answer in Development-Thread (yet) ...
... so opened this.
ok, just to clearify:
1. the kernel with keypad drivers as modules is not to be take because the drivers are more stable, it is to be taken because you can unload and reload the drivers when the hung up (that's not posible with static driver in the kernel binary).
2. the kernel with keypad drivers as modules needs the autostart.sh script to load the driver modules on system boot. Without them, you have no keypad ;-).
keypad drivers as modules repeated twice, did you mean keypad drivers not as modules?
Kurt Krummbein said:
ok, just to clearify:
2. the kernel with keypad drivers as modules needs the autostart.sh script to load the driver modules on system boot. Without them, you have no keypad ;-).
Click to expand...
Click to collapse
How to load file autostart.sh scrip to load the driver modules on system boot ??? Not only no keypad also no keyboard except Power button and Camera button
Hi,
@jerrytan93: yes, both times 'keypad-driver-as-modules' ... the code is in both cases the same, it is not more stable when compiled as modules, it's just reloadable when it failes.
@h_pro9x: the best guide to set this all up is <http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2>. Only caveat is, you need the 'Terminal Emulator', either as app or as part of DevTools, to be able to run the commands with a 'su-shell'.
Ciao
Kurt
Pls have someone of you tried the supercharger v6 script? What was the result? Was it easy to install?
Sent from my LG-P990 using Tapatalk
its great. i installed it when still in stock and still using it with neoblaze kernel.
its already fast even without the oc kernel. you wont see higher number on benchmark apps. but you will feel the difference.
this is from the supercharger thread
http://forum.xda-developers.com/showthread.php?t=991276
Requirements:
1. Rooted Phone....
2. Script Manager or Terminal Emulator to run the script. Stock ROMs can also use SM to load up boot scripts!
3. Busybox 1.18.2 OR LOWER - 1.18.3 or newer are VERY much a hassle with errors that should NOT be errors!
4. AutoStart Script by me - Enables Stock ROMS (Milestone) to utilize etc/init.d for boot scripts.
Installing/Using:
1. Download the attached V6_SuperCharger_for_Android*.txt script and save to your sdcard.
... Do NOT run the V6 SuperCharger install script at boot!
2. Load the script (V6_SuperCharger_for_Android*.txt) into Script Manager and select "Run as Root."
3. Touch the screen for the soft keyboard or slide out the keyboard and get SuperCharged! Just pick an option!
4. READ the script's output!
5. Afterwards, READ the html HELP FILE in the root of your SD Card!
6. Disable "Lock Home in Memory" if your ROM has this option.
7. Optional: For a quick status check, you can put a Script Manager widget for V6 SuperCharger on you desktop
for me, i use the 11th option (oom grouping fixes + hard to kill launcher) then reboot.
cyanogen doesent need the autostarter script ore does it?
Ok,thanks. I am running it now too and it feels really faster
Sent from my LG-P990 using Tapatalk
Hi, may i know which option did you choose? I chose the 8th one(the MAX one) but i don't feel such many differences...
If my memory is correct, i used the option 7, max RAM 512 and hard to kill launcher
It is also for CyanogenMod 7?
Hi, I tried to apply ext4 lagfix via CF ext4 Manager (CF-Root-ext4-v1.3-Addon.apk) , data was converted successfuly, system was not converted due not enough free space, which is normal as Chainfire said.
Please note that when first using the tool to convert, you will probably notice /system is not converted. If this happens, it is because /system does not have enough free space for the extra space overhead of ext4. You will need to free up some space on /system before the conversion will succeed.
Click to expand...
Click to collapse
Running 2.3.4 JVQ stock firmware with CF root.
But after reboot ext4 app have all choices grayed, so I cannot convert system or any other partion to ext4 or back.
It show "No rfs/ext4 partions found" and "unknow ,0.0MB, 0.0MB total"
Any tips appreciated. Thanks in advance
Roman
Which kernel are you running? Try changing kernel eg: Semaphore or galaxian. Then do a wipe cache and dalvik cache
Runnig CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS on stock JVQ without other changes.
Thanks for advice
Problem is, that many kernels have logging disabled, I need logcat, ddms for developing
EDIT: Flashed semaphore, there is greenscreen while lock/unlock screen(minor issue),but other things seems fine, thanks!
semaphore has logging enable script
Quote :
"In order to control voodoo sound and BLN you have to download Voodoo Control and BLN control applications respectively from android market.
The max CPU frequency is by default 1Ghz.
You may use applications like Voltage Control or Pimp my CPU to control OC/UV.
In order to load various modules of the kernel copy the respective script from /res/scripts to /system/etc/init.d directory and give the script executable permissions. This is optional. It is needed only if you want to use this functionality. The scripts:
- enable_conservative (load conservative governor module)
- enable_cifs (load cifs module)
- enable_netfilter (load netfilter modules for firewall or WiFi, USB tethering)
- enable_tun (load tun module)
- enable_deadline (load the deadline I/O scheduler module)
- enable_binfmt_misc
- S05_enable_oc replaces enable_ocuv since 1.6.0 (enable overclocking)
Other scripts:
- enable_sm_cold script for SpeedMod cold preset
- enable_sm_warm script for SpeedMod warm preset
- enable_sm_neutral script for SpeedMod neutral preset (please note that this is enabled by default)
To enable logcat run the enable_logger script in res/scritps and reboot your phone."
Here is the link
Hope this helps.
The Ultimate kernel for the HTC Desire 500, both one sim and dual sim!
Software version 1.32/1.26 only! It probably won't work on earlier versions, but it might work on later versions (1.34), I haven't tested that.
Use at your own risk!
Features:
/system write protection removed
two new frequencies added: 1300 and 1400 mhz
init.d support
intelli_plug
sweep2sleep
sweep2wake and doubletap2wake, both with pocket detection
ntfs read/write support
Governors added: SmartassV2 and Lulzactive
ioschedulers added: sio and fiops Default: sio
Fastcharge
Unsecure (ro.secure=0)
Click to expand...
Click to collapse
If you don't want to overclock your device, then simply choose the download link with no overclocking.
Requirements:
Unlocked bootloader
Custom recovery (cwm or twrp)
Fastboot installed
Click to expand...
Click to collapse
Installation instructions:
Download the latest boot.img
Boot your phone into fastboot mode
Open up your commandline
cd to the directory containing the boot.img
In the command line type: fastboot flash boot boot5.img
Boot into cwm/twrp
Wipe cache and dalvik-cache
If you don't have it yet (your phone is not rooted), flash SuperSU or superuser
Click to expand...
Click to collapse
Downloads:
Version 8: Not overclocked: boot8_no_oc.img, Overclocked: boot8_oc.img
Version 7: Not overclocked: boot7_no_oc.img, Overclocked: boot7_oc.img
Version 6: boot6.img
Version 5: boot5.img
Version 4: boot4.img
SuperSU: SuperSU
Click to expand...
Click to collapse
If your phone does not boot after installing an overclocked kernel, then try installing the not overclocked kernel.
Changelog:
Version 8:
Removed the underclocking, it was way too low, and caused wakeup issues
Added 1300 mhz frequency
Updated intelli plug from faux123's github
Updated to 1.34, many thanks to @0lvin
Little fixups on sweep2wake/doubletap2wake
Version 7:
Added overclocking up to 1400 mhz
Underclocking down to 19 mhz
Added sweep2wake and doubletap2wake
Added intelli plug, a replacement for Qualcomm's closed source mpdecision
Enabled perflock again
Version 6:
Add fastcharge
Version 5:
Disabled -O3 optimization
Version 4:
-O3 optimization
ntfs read/write support
Governors added: SmartassV2 and Lulzactive
ioschedulers added: sio and fiops Default: sio
Version 3 and below:
Check the Ultimate Thread
Click to expand...
Click to collapse
Kernel source:
https://github.com/dummie999/android_kernel_htc_z4u
Click to expand...
Click to collapse
Credits:
@flar2 for sweep2sleep
@xpirt for helping me with Smartass
@GreatEmerald for helping me with kernels in general
@eexter for testing for 1.26
@0lvin for updating to 1.34
To the devs:
Feel free to include this kernel in your rom/rooting tool. Just give proper credits and put a link to this thread in your rom thread (Required for GPL).
XDA:DevDB Information
The Ultimate Kernel, Kernel for the HTC Desire 500
Contributors
dummie999, 0lvin
Kernel Special Features: dt2w | s2w | intelli_plug | fastcharge | oc | init.d
Version Information
Status: Stable
Created 2014-10-14
Last Updated 2014-10-14
Reserved
Reserved
Upcoming features
* Intellidemand (implemented - needs tweaking)
* F2FS
Tips
How to change sleep/wake options:
The options for sweep2sleep, sweep2wake and doubletap2wake:
sweep2sleep: 0 - disabled, 1 - enabled, both directions, 2 - enabled, left->right only, 3 - enabled, right->left only
sweep2wake: 0 - disabled, 1 - enabled, both directions, 2 - enabled, left->right only, 3 - enabled, right->left only
doubletap2wake: 0 - disabled, 1 - enabled, full screen, 2 - enabled, bottom half screen, 3 - enabled, center down of the screen (hope you get it)
To change the options, put a script in /system/etc/init.d:
Code:
#!/bin/sh
echo "0" > /sys/android_touch/sweep2sleep
echo "0" > /sys/android_touch/sweep2wake
echo "0" > /sys/android_touch/doubletap2wake
This setting disables all the sweep/wake options
Code:
#!/bin/sh
echo "1" > /sys/android_touch/sweep2sleep
echo "1" > /sys/android_touch/sweep2wake
echo "2" > /sys/android_touch/doubletap2wake
This setting enables sweep2sleep and sweep2wake, and enables doubletap2wake bottom half of the screen
Click to expand...
Click to collapse
How to use fastcharge:
If you charge your phone via usb (from your computer) then it will only charge at 500mA even while most usb ports are capable of supplying 1000mA. Enabling fastcharge will allow your phone to charge at 1000mA via usb.
!!! Warning: you must be sure your usb can supply 1000mA !!!
Fastcharge is disabled by default. You can enable it in 2 different ways:
1. Writing a 1 to /sys/kernel/fast_charge/force_fast_charge. You can do this with a text editor, or with a script in init.d (see above)
2. Or you can simply install an app. I tested Fast Charge by Mathew Winters and Fast Charge by Chris Conley, both worked.
Click to expand...
Click to collapse
To hard? Use this app by Ufonek: Kernel Settings
A word about governors:
Some governors lower the frequencies to fast. For example, when I play angry birds when using lulzactive, the phone laggs a lot. This is, however, not the fault of the kernel, but the fault of the way the governor is tweaked. It is the price you pay for the better battery life you have. If you want to do something about it, tweak your governor, there are a lot of tutorials about this.
Don't come here complaining the phone laggs, and that I should fix it, I won't, because I can't. Everyone has his own preferences, and if you can't live with this, then I recommend you use the ondemand governor.
Compilation instructions
Instructions for compiling the kernel yourself.
Prerequisites:
1. A linux computer
2. Basic bash knowledge
3. ~120 MB free space
4. The android-eabi toolchain:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6 for 4.6
(use darwin-x86 instead of linux-x86 for mac)
And then add it to your $PATH (You need to have the arm-eabi-4.6/bin folder in your path)
Instructions:
1. Download the kernel source
2. Open the cmdline and cd to the directory with all the files (Documentation, arch, block etc.)
3. type: make dummie_z4u_defconfig
4. type: make menuconfig
........A menu will open, and you can change some settings. If you want everything to be the way I built it, then skip this step.
5. type: make
The actual building will begin.
Troubleshoot:
If you run into a python problem, you might want to change, in android_kernel_htc_z4u/scripts/gcc-wrapper.py this:
"#! /usr/bin/env python" into "#! /usr/bin/env python2", credits @svalo
If the building succeeds, then you will find the file zImage in arch/arm/boot.
Next step: turn the zImage into a boot.img
1. Download imgtools, and add it to you $PATH
2. Download my boot.img
3. Open cmdline, cd to the directory containing boot.img and type: unpack boot.img
........You will end up with: ramdisk.cpio.gz, ramdisk and zImage (and the boot.img that was already there)
4. Replace the zImage with the zImage you build earlier (arch/arm/boot)
5. Rebuild the kernel:
Code:
repack_ramdisk ramdisk initramfs.cpio.gz
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x3b00000 --cmdline 'no_console_suspend=1 console=null' -o new_boot.img
You will now see a file called new_boot.img, containing your own kernel, which you can install the very same way
Good luck:good:
Note that -O3 does not work for the kernel, at all, and never has. You can set it but it won't do anything. The compiler will still use -O2, because all the parts where performance matters are written in assembly or through GCC-specific extensions already. There is nothing that automatic code optimisation would improve. Meanwhile -O3 enables non-safe options that can result in imprecise calculations, which can lead to disasters in things that are as important as the kernel. So you should disable that.
GreatEmerald said:
Note that -O3 does not work for the kernel, at all, and never has. You can set it but it won't do anything. The compiler will still use -O2, because all the parts where performance matters are written in assembly or through GCC-specific extensions already. There is nothing that automatic code optimisation would improve. Meanwhile -O3 enables non-safe options that can result in imprecise calculations, which can lead to disasters in things that are as important as the kernel. So you should disable that.
Click to expand...
Click to collapse
Then why do people use it?
dummie999 said:
Then why do people use it?
Click to expand...
Click to collapse
Placebo. It makes them think they're gaining something, even though in truth they aren't (but are not certain).
so i need to flash the boot image than flash the kangbang kernel????
joe-khalil said:
so i need to flash the boot image than flash the kangbang kernel????
Click to expand...
Click to collapse
No, you don't need to flash the kangbang kernel. This is a replacement of the kangbang kernel, for 1.32
Replacement?? That means if i flash the boot image i'll have the kernel installed?
Dual SIM doesn't have the 1.32 update, so i don't think this kernel would work on the dual sim version.
joe-khalil said:
Replacement?? That means if i flash the boot image i'll have the kernel installed?
Click to expand...
Click to collapse
yes, lol
I have installed.. It works fine. Thanks !!!
gayTony said:
Dual SIM doesn't have the 1.32 update, so i don't think this kernel would work on the dual sim version.
Click to expand...
Click to collapse
1.32 for Single SIM = 1.26 for Dual SIM (kernel is the same)
dummie999 said:
Fastcharge
Overclocking?
If you have any requests, post them!
Click to expand...
Click to collapse
Overclocking would be nice!
And don't forget to add a link to your kernel sources, to prevent unfortunate things from happening to this thread
GreatEmerald said:
And don't forget to add a link to your kernel sources, to prevent unfortunate things from happening to this thread
Click to expand...
Click to collapse
lol, I knew I had forgotten sth
dummie999 said:
lol, I knew I had forgotten sth
Click to expand...
Click to collapse
any news about CM @dummie999