First custom kernel for Defy Mini XT320/XT321 is here!
Featured on XDA Portal: http://www.xda-developers.com/android/first-custom-kernel-for-the-motorola-defy-mini-mini-xt320xt32/
@MauroSZ @Bernd.Defy @junk031
Despite us having a locked bootloader, we can boot a custom kernel via fastboot.
Technical Details:
Fastboot is stored as a secondary bootloader in Defy Mini. On older firmwares, the secondary bootloader had fastboot enabled but newer firmwares don't. This is why Motorola left a vulnerability in fastboot which allowed us to fastboot boot img files.
Kernel Source: https://github.com/rootdefyxt320/android_kernel_motorola_tinboost
This kernel is made for Defy Mini stock ROM's.
Details:
Linux Kernel version 2.6.38.6
Features:
-Swap
-Insecure
To Do:
-Add overclock
-Add custom governors
Limitations:
-You must use fastboot everytime you want to boot a custom kernel so it requires a computer.
Instructions:
1. Download boot.img from attachments
2. Download modules.zip from attachments.
3. Make sure you have CWM Recovery, if not download it from Post #41
4. Now boot into CWM Recovery using the batch script or typing the command in cmd
Code:
fastboot boot name-of-recovery.img
4. Now type these commands in cmd:
Code:
adb shell mount -a
Code:
adb push modules.zip /sdcard
Code:
adb shell
Code:
cd /system/lib/modules
Code:
busybox unzip /sdcard/modules.zip
Then it will ask you to overwrite the files, press A on the keyboard.
Now type the next commands in cmd:
Code:
cd /system/lib
Code:
chmod 755 modules/*
Code:
exit
Code:
adb reboot-bootloader
Code:
fastboot boot boot.img
Updated to v2 in Post 8: http://forum.xda-developers.com/showpost.php?p=51104120&postcount=8
Same installation instructions as v1.
Lol, I compiled one for XT530 with OC and undervolt, but never released as thought it would be tough to boot it everytime
Well, nice start. I'm currently working on kexec, would possibly release it when kexec would be ready.
rootdefyxt320 said:
Limitations:
-You must use fastboot everytime you want to boot a custom kernel so it requires a computer.
Click to expand...
Click to collapse
it's possible make it permanent?
sfoot13 said:
it's possible make it permanent?
Click to expand...
Click to collapse
Locked bootloader prevents this. Until I can conpile kexec, I can make it permanent.
rootdefyxt320 said:
Locked bootloader prevents this. Until I can conpile kexec, I can make it permanent.
Click to expand...
Click to collapse
You're a genius! i hope you can have success with the kexec!
You know if swap will make any difference in the performance?
sfoot13 said:
You're a genius! i hope you can have success with the kexec!
You know if swap will make any difference in the performance?
Click to expand...
Click to collapse
I built an 800MHz overclock kernel but beware you can burn your NAND but we can now use @cute_prince method to have a 878 MHz PLL2 overclock without burning NAND It's not modded numbers
rootdefyxt320 said:
I built an 800MHz overclock kernel but beware you can burn your NAND but we can now use @cute_prince method to have a 878 MHz PLL2 overclock without burning NAND It's not modded numbers
Click to expand...
Click to collapse
are you working on it? (878 MHZ overclocking)... thanks for your work bro! :good:
sfoot13 said:
are you working on it? (878 MHZ overclocking)... thanks for your work bro! :good:
Click to expand...
Click to collapse
Hey, I managed to improve the performance of the kernel also by using LZMA compression instead of GZIP, switching to SLUB allocator and deadline I/O scheduler and overclock also.
Kernel v2 Update:
-Uses LZMA compression
-Enabled OTG Support
-Switched to SLUB Allocator
-Added Deadline I/O Scheduler
-Default VDD=7 for better overclocking with Bernd.Defy's overclock module.
-Enable zRAM.
You must install the new modules otherwise device will bootloop!
Thank you so much! OTG support *-* is a great gift!
bro, can you do it permanent? is something uncomfortable always connect the phone to pc, anyway thanks for your work!
sfoot13 said:
Thank you so much! OTG support *-* is a great gift!
bro, can you do it permanent? is something uncomfortable always connect the phone to pc, anyway thanks for your work!
Click to expand...
Click to collapse
I'm busy studying for exams these days. Kexec requires a lot of hard work before we can even boot the kexec custom kernel. Remember, I'm just a 16 year old dev, so got to have priorities in school work first
rootdefyxt320 said:
I'm busy studying for exams these days. Kexec requires a lot of hard work before we can even boot the kexec custom kernel. Remember, I'm just a 16 year old dev, so got to have priorities in school work first
Click to expand...
Click to collapse
Oh sorry, i don't knew! 16 years old dev.? really? you're doing a great work :good:
Well, success on your studies! God bless u
sfoot13 said:
Oh sorry, i don't knew! 16 years old dev.? really? you're doing a great work :good:
Well, success on your studies! God bless u
Click to expand...
Click to collapse
Is USB OTG working for you? Please test it as I don't have any USB OTG equipment and give me feedback on the performance of the kernel
rootdefyxt320 said:
Is USB OTG working for you? Please test it as I don't have any USB OTG equipment and give me feedback on the performance of the kernel
Click to expand...
Click to collapse
i need search my OTG cable, i don't know where is... about the overclock.. it's possible increase it?
sfoot13 said:
i need search my OTG cable, i don't know where is... about the overclock.. it's possible increase it?
Click to expand...
Click to collapse
Use Bernd.Defy's overclock module for now. I have overclocked my Defy Mini to 720MHz using his overclock module.
Go to the thread:http://forum.xda-developers.com/showthread.php?t=2210799
Then extract the defymini_oc.ko out of the zip folder.
Then use adb to push the file:
Code:
adb push defymini_oc.ko /system/lib/modules
Then use these commands in cmd:
Code:
adb shell
Code:
su
Code:
busybox insmod /system/lib/modules/defymini_oc.ko pll2_l_val=75 acpu_freq_tbl_addr=0xc0775b5c cpufreq_stats_tbl_addr=0xc07a971c
rootdefyxt320 said:
Use Bernd.Defy's overclock module for now. I have overclocked my Defy Mini to 720MHz using his overclock module.
Click to expand...
Click to collapse
me only 700MHZ, 720 reboot my phone, i'm using smartassV2 and I/O deadline and the performance is good, a bit better than noop (I/O) and smartassv2 together
Framework-res, Phone and SystemUI modded!
Hi, i edited the framework.res.apk, Phone.apk and SystemUI.apk, i just changed some icons and images, and the color of divisors
Just download the zip files and put it on your SD, boot into CWM recovery, select install update.zip and install the modded files
Make sure you have a backup of your original files.
rootdefyxt320 said:
Is USB OTG working for you? Please test it as I don't have any USB OTG equipment and give me feedback on the performance of the kernel
Click to expand...
Click to collapse
OTG not working, and with the new modules (V2), i have a WIFI "error" using the stock kernel, but i fixed it with the first version of your modules.
sfoot13 said:
OTG not working, and with the new modules (V2), i have a WIFI "error" using the stock kernel, but i fixed it with the first version of your modules.
Click to expand...
Click to collapse
The V2 modules are for the V2 custom kernel as there is substantial changes to the features. The new modules are made for SLUB Allocator instead of the SLAB allocator in the stock kernel. Try using an app to see if OTG is present.
sorry i am geting unzip write: no space left on device ,
i have no experience in this, please help
feline2611 said:
sorry i am geting unzip write: no space left on device ,
i have no experience in this, please help
Click to expand...
Click to collapse
You will have to delete stuff in /system.
Related
Here is my Unvolted kernel for the Desire HD. This will give u a bit more speed with no overvolt and every speed bar the max 1.2ghz is undervolted if u want faster check out my 1.4ghz kernel that uses the exact same voltages as this kernel up to 1.24ghz
I AM NOT RESPONSABLE FOR ANY DAMAGE CAUSED BY THIS ALTHOUGH
TESTED YOU UNDERTAKING THIS MEANS U UNDERSTAND AND TAKE THE RISKS
All Speeds up to 1209Mhz are undevolted from stock and 1209Mhz is the highest value of stock.
This Kernel Should be safe and stable for all Desire HD
[Change Log]
1.3.8.3
-- patched to .35
FULL CHANGE-LOG LIVES HERE
[INSTALL]
via Clockwork Recovery
Needed :-
-- ClocworkMod Recovery installed
-- SENSE This .zip
1) copy the .zip (From Above) to your sdcard
2) boot into recovery
3) flash .zip from sdcard
4) select requierd .zip
4) FLASH
5) reboot
OR Fastboot
Needed
-- Fastboot Set Up
-- SENSE This .zip
-- ADB set up
-- Set CPU
1) boot into bootloader (fatboot mode)
2) put the zImage from the .rar file in the fastboot directoy
3) run
fastboot flash zimage zImage
Click to expand...
Click to collapse
5) run
fastboot reboot
Click to expand...
Click to collapse
6) wait for android to boot
///// Make shure you have the .ko from the .zip / .rar where the zImage came from ///////
7) put the .ko frile from the .rar file in your adb director
8)run
adb push bcm4329.ko /sdcard/
Click to expand...
Click to collapse
9) in adb shell run these commands in order
su
mount -o remount,rw /dev/block/mmcblk0p25 /system
rm /system/lib/modules/bcm4329.ko
busybox cp /sdcard/bcm4329.ko /system/lib/modules/bcm4329.ko
rm /sdcard/bcm4329.ko
Click to expand...
Click to collapse
10) reboot
11) use SetCPU to gain the extra speed
Here is the zip to flash in clockwork too ... when its out :-D
[MIRROR]
http://is.gd/3KknOZ
Thanks To zantekk for the mirroring
[ALL VERSIONS]
1.3.8.3 SENSE
1.3.8.2 SENSE
1.3.8 SENSE
1.3.7 SENSE
1.3.6 SENSE
1.3.5 SENSE
1.3.4 SENSE
1.3.3 SENSE
1.3.0 SENSE
1.2.5 SENSE
1.2.3r2 SENSE
1.2.2 SENSE
1.2.1 SENSE
1.2.0 SENSE
1.1.4 CM ---- SENSE
1.1.3 CM ---- SENSE
1.1.2 CM ---- SENSE
1.1.1 CM ---- SENSE
1.1.0 CM ---- SENSE
1.0.8 CM SENSE
1.0.7
1.0.6
1.0.5
1.0.4
1.0.2
1.0.1
1.0.0(GOLD)
0.0.9-CM ---- 0.0.9-SENSE
Source
https://github.com/BuzzBumbleBee/HTC_ACE_KERNEL
Credits
Cyanogen team for info on edition speed tables
-Mr. X- For helping me fix the source
Lee For His gov + CPU table
CK2 [BFS Patch]
erasmux [SmartAss CPU governor]
Aplharev ppl for help
Hi, many thanks for a prompt kernel release!
Just to clarify, by undervolting does this in theory/pratice produce better battery life given less voltages are being used?
Some say it does but there are a lot of factors but in some intances the voltage can afferct the power use :-D
i know that neither a yes/no but its how these thigs are :-D
Apache14 said:
Some say it does but there are a lot of factors but in some intances the voltage can afferct the power use :-D
i know that neither a yes/no but its how these thigs are :-D
Click to expand...
Click to collapse
lol no worries thats fair doos, cant make my mind up whether to flash the 1.2ghz or 1.49ghz........decisions decisions!!
fastboot.zip for the people
xmoo said:
fastboot.zip for the people
Click to expand...
Click to collapse
Thanks , but this compatible with WIN7 64bits ?
Thanks , and for adb ? how is it ? i can use rootexplorer for copy file in system ?
brolee93 said:
Thanks , but this compatible with WIN7 64bits ?
Thanks , and for adb ? how is it ? i can use rootexplorer for copy file in system ?
Click to expand...
Click to collapse
I used it on WIN7 64bits, so gues it should be compatible.
ADB I did not use. I used gscript addedthe commands there.
ok and how use fast boot please help me
brolee93 said:
ok and how use fast boot please help me
Click to expand...
Click to collapse
Put your phone in bootloader / Fastboot
Plugin usb cable / Fastboot USB
Extract the zip and run fastboot.cmd on your computer
xmoo said:
Put your phone in bootloader / Fastboot
Plugin usb cable / Fastboot USB
Extract the zip and run fastboot.cmd on your computer
Click to expand...
Click to collapse
Ok i test now thanks
EDIT: when i clic fastboot.exe i have this bug :
Uploaded with ImageShack.us
Works perfectly, thanks Xmoo and Apache14!
Don't run the exe but the cmd.
brolee93 said:
Ok i test now thanks
EDIT: when i clic fastboot.exe i have this bug :
Uploaded with ImageShack.us
Click to expand...
Click to collapse
Sent from my Desire HD using XDA App
Mine hasn't worked Can I check please -
I boot into recovery.
I select Fastboot.
I plug in to my PC via USB and wait for drivers to install.
I 'cmd' and browse to my ADB/fastboot folder
I type 'fastboot flash zimage zImage'
It reports -
Code:
sending 'zimage' (2744 KB)... OKAY [ 0.469s]
writing 'zimage'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.012s
What have I done wrong?
S-off, rooted??
Sent from my Desire HD using XDA App
Not S-Off (is this done simply yet?) but rooted (should be perm rooted via VISIONary r12)
O BTW: I can OC tot 1,49Ghz, that's a bit weird as the Topictitle says 1,2Ghz...
AndyCr15 said:
Not S-Off (is this done simply yet?) but rooted (should be perm rooted via VISIONary r12)
Click to expand...
Click to collapse
It is relatively simple as long as you can read and follow instructions well, if you feel uncomfortable flashing the ENG Hboot image, then don't do it.
AndyCr15 said:
Not S-Off (is this done simply yet?) but rooted (should be perm rooted via VISIONary r12)
Click to expand...
Click to collapse
S-OFF it, so it stays perm.....
Do you have guide for copy bcm4359.ko for WiFi . Because I don't have permission for this file. With rootexplorer or terminal help me.
Thanks for zimage it work perfectly
: screen of my pb :
Uploaded with ImageShack.us
Edit : sorry i win lol thanks thanks my desire hd roxxx
Doktaphex said:
It is relatively simple as long as you can read and follow instructions well
Click to expand...
Click to collapse
Are there any English instructions yet? I think the translation of the German ones, while pretty good, probably weren't perfect and you need to be spot on with something like this.
[UPDATE 02/03/2011]
Here is my OverClocked kernel for the Desire HD. This kernel is undervolted all the way up to 1.1ghz and uses a maximum overvolt of 150mV at 1.51ghz
I AM NOT RESPONSABLE FOR ANY DAMAGE CAUSED BY THIS ALTHOUGH
TESTED YOU UNDERTAKING THIS MEANS U UNDERSTAND AND TAKE THE RISKS
like my undervolted kernel clock speeds under 1209MHz are undervolted in comparison with stock and 1209Mhz is at the same voltage as stock. Above the system is at a hight voltage than stock slighly.
This KERNEL is for people woh dont mind going highet voltage than stock. If this isnt you check out my UV kernel
As the DesireHD has a slightly better quiality CPU than the Z/G2 this over volt can be slightly less on this.
I cannot guarrentee that this kernel will be stable on all DesireHD's if you get freezing/crashing limit the CPU speed in setCPU or install my UV kernel.
[CHANGELOG]
1.3.8.3
-- Patched to .35
----- NO more CM support as the stock CM kernel is very good -----
THE FULL CHANGE LOG LIVES HERE
[INSTALL]
via Clockwork Recovery
Needed :-
-- ClocworkMod Recovery installed
-- SENSE This .zip
1) copy the .zip to your sdcard
2) boot into recovery
3) flash .zip from sdcard
4) select requierd .zip
4) FLASH
5) reboot
OR Fastboot (Builds Before 0.0.9)
Needed
-- Fastboot Set Up
-- SENSE This .zip
-- ADB set up
-- Set CPU
1) boot into bootloader (fatboot mode)
2) put the zImage from the .rar file in the fastboot directoy
3) run
fastboot flash zimage zImage
Click to expand...
Click to collapse
5) run
fastboot reboot
Click to expand...
Click to collapse
6) wait for android to boot
///// Make shure you have the .ko from the .zip / .rar where the zImage came from ///////
7) put the .ko frile from the .rar file in your adb director
8)run
adb push bcm4329.ko /sdcard/
Click to expand...
Click to collapse
9) in adb shell run these commands in order
su
mount -o remount,rw /dev/block/mmcblk0p25 /system
rm /system/lib/modules/bcm4329.ko
busybox cp /sdcard/bcm4329.ko /system/lib/modules/bcm4329.ko
rm /sdcard/bcm4329.ko
Click to expand...
Click to collapse
10) reboot
11) use SetCPU to gain the extra speed
****Due to the init bug (100% CPU usage use SetCPU to limit speed when screen off to save your battery I recommend 256 to 768*****
Here is the zip to flash in clockwork too ... when its out :-D
[ALL VERSIONS]
1.3.8.3SENSE
1.3.8.2SENSE
1.3.8SENSE
1.3.7SENSE
1.3.6SENSE
1.3.5SENSE
1.3.4SENSE
1.3.3SENSE
1.3.0SENSE
1.2.5SENSE
1.2.3r2SENSE
1.2.2SENSE
1.2.1SENSE
1.2.0 SENSE
1.1.4 CM ---- SENSE
1.1.3 CM ---- SENSE
1.1.2 CM ---- SENSE
1.1.1 CM ---- SENSE
1.1.0 CM ---- SENSE
1.0.8 CM SENSE
1.0.7
1.0.6
1.0.5
1.0.4
1.0.2
1.0.1 fixed please reflash
1.0.0(GOLD)
0.0.9-CM ---- 0.0.9-SENSE
Source
https://github.com/BuzzBumbleBee/HTC_ACE_KERNEL
Credits
Cyanogen team for info on edition speed tables
-Mr. X- For helping me fix the source
Ziggy471 for LZMA compression source
Lee For gis Gov and CPU table fixes
CK2 [BFS Patch]
erasmux [SmartAss CPU governor]
Aplharev ppl for help
thanks for this!
for 5) its just fastboot reboot
Edit:
oh and also adb won't push so you have to use these commands instead in the terminal
adb push bcm4329.ko /sdcard/bcm4329.ko
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p25 /system
cat /sdcard/bcm4329.ko > /system/lib/modules/bcm4329.ko
oops cheers for the heads up
teihoata said:
oh and also adb won't push so you have to use these commands instead in the terminal
Click to expand...
Click to collapse
Thanks for the kernel Apache14!
Also, thanks teihoata for the above tip, i complete forgot we have to remount system as rw for now
fastboot.zip for the people
So what is the stock volt, and what is the volt you using??
And you guys use any profiles??
WiFi doesn't seem to work. I get "error".
Sent from my Desire HD using XDA App
phunkycow said:
WiFi doesn't seem to work. I get "error".
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'm on WIFI here. No Issue...
Pushed BCM4329.ko again and rebooted, still nothing
My bad luck. Do you think it could have anything to do with the custom boot.img of the other thread? Also just noticed that my max freq is 1GHz now, seems like stock... Was working fine when i first flashed.
Sent from my Desire HD using XDA App
You will have overwitten the zImage, just reflash the zImage out of the rar with fastboot
Thanks a lot, you were right; works fine again.
Sorry about the fuss. :]
Sent from my Desire HD using XDA App
hi, sorry for a very noob question but how do you enter bootloader mode and setup fastboot.
thanks
Either using adb (plugin your phone via usb first): adb reboot bootloader
or: turn of your phone -> hold volume down + power until you see the bootloader screen.
Apache14 said:
You will have overwitten the zImage, just reflash the zImage out of the rar with fastboot
Click to expand...
Click to collapse
What is the stock volt and the volt ur using here??
Sent from my Desire HD using XDA App
xmoo said:
What is the stock volt and the volt ur using here??
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I believe that stock is 1100mV I could be wrong but I remember that when using the previous OC method I was undervolting to 1000mV at 1440MHz via Apache14's instructions. I would guess he's gone for a 50-100mV overvolt, but hey I'm just pulling this from the top of my head, so don't quote me.
Very Good :-D anything under 1.2Ghz is a 50mV under clock and over is either 50mV 100mV or 150mV and I may be able to get more out of it yet
It looks a though this fellow and his G2 are going crazy:
http://forum.xda-developers.com/showthread.php?t=834219
1.7GHz at 1400mV
Those voltages could be unsafe after long use (heat + ware on CPU) i would only go for a 150mV over volt MAX for every day use.
Apache14 said:
Those voltages could be unsafe after long use (heat + ware on CPU) i would only go for a 150mV over volt MAX for every day use.
Click to expand...
Click to collapse
Yeah I was thinking it's probably pretty unsafe, hence why he hasn't released that in his kernel, too many folks would just think it was plausible to keep the phone at that level.
Apache14 said:
Very Good :-D anything under 1.2Ghz is a 50mV under clock and over is either 50mV 100mV or 150mV and I may be able to get more out of it yet
Click to expand...
Click to collapse
so how much is this 1.49 50/100 or 150
xmoo said:
so how much is this 1.49 50/100 or 150
Click to expand...
Click to collapse
1305=50, 1401=100, 1497=150
Froyo 2.2.2 port for Huawei U8120.
Maybe it will work on Huawei U8100/U8110 series, but for now it is focused on U8120.
So I dont know what behavior has on U8100 etc.
I must say a big thanks to Tom_G for his awesome work, especially for his froyo port on pulse.Without his work and his posts
on modaco forum, I will not be able to accomplish this.
kalt kaffe's 2.6.29 kernel.
Android 2.2.2 from aosp with some codeaurora changes.
JIT enabled.
Working:
RIL
Audio
GPS
Bluetooth
Wifi
SD card
Sensors
TSCalibration from codeaurora(still the app needs some improvements.For now use a stick or pen when you calibrate the screen)
Not working/bugs:
camera
broken layout on dialer
sdcard cannot be mounted in pc
Its still under development.This is not a finished rom and its not fully tested.
Probably it has problems that I have not yet encountered.So I would not suggest you to try it,
except if you have some experience and you want to help.
I have tried to make it as plain and simple as it gets.No google apps, no bootanimation etc.When all bugs are fixed then I will include them or I will post
my rom.But there are guys that are more expert in rom cooking than me.
Here is a zip with already compiled image files if someone wants to try it and post any bugs/fixes that have found.I have also uploaded here gapps if someone wants them(gmail,market etc)
Code: https://github.com/tas0s
Device tree: https://github.com/tas0s/android_device_huawei_u8120
Try it at your own risk.
Im not responsible for any damage that this may cause.
v.1 initial build
How to build it:
- Install git and gpg (gnupg).
- Download repo - http://source.android.com/source/git-repo.html
$ mkdir android
$ cd android
$ repo init -u https://github.com/tas0s/platform_manifest.git
$ repo sync
- Extract necessary binaries
Some compiled code from the official eclair roms is re-used in froyo. Because some of this code is not opensources I cannot included in the git repository.
The files can be extracted from any u8120 eclair rom.
Place the rom zip in the android directory an rename it to u8120_update.zip
navigate to /device/huawei/u8120:
cd device/huawei/u8120
Then execute from the android directory
$sh device/huawei/u8120/unzip_files.sh
else you can extract them from a working u8120 phone with an eclair rom (check that adb is enabled)
$device/huawei/u8120/extract_files.sh
- Building the system
Once thats done you can start compiling.
Follow the aosp instructions on setting up the build environment. - http://source.android.com/source/download.html
After the environment is setup.
$ cd android
$ source build/envsetup.sh
$ lunch
Select the device u8120.
$ make
I recommend using multiple threads for make if you have a multi core/processor system. By default make will use
1 thread (-j1), set it to use 2*NumberOfCPUsAvailable (so on my dual core -j4). Reducing the number of threads used will reduce the impact on
system performance while the build is running.
The output will be image files in {buildroot}/out/target/product/u8120/. Flash with fastboot.
$ fastboot flash boot out/target/product/u8120/boot.img
$ fastboot flash system out/target/product/u8120/system.img
$ fastboot flash userdata out/target/product/u8120/userdata.img
$ fastboot reboot
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
for the future
thnx for the gifts up to it tomorrow
A question about camera problem, only video or all features?
bitye said:
A question about camera problem, only video or all features?
Click to expand...
Click to collapse
The camera fails after a few secs.When an image appears in the preview window.
I have read that the the way that android handles camera has changed in froyo.In cyanogen they are using a libcamera2 (just libcamera with a few changes I think so it can work with the new framework).
As you can see in the BoardConfig.mk I have already include the libcamera2 statements but not the lib
When I manage to get some free time I would try the libcamera2.Maybe until the end of the week or sooner.
Ρε πατριδα αξιζει η rom ή οχι;
tas0s said:
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
Click to expand...
Click to collapse
There's a little fix using bootbuilder for U8120, see this post:
http://android.modaco.com/content/t...l-r1-bootbuilder-for-pulsemini-alpha-release/
In the 6th reply you can find the info you could need it
Good luck!
Hi can you tell me on wich kernel it runs?
the 2.6.32 or2.6.29?
and if wiifi is completly fixed no crashes sleep works mac adress?
thanks
calibration fixed at this repo?
larissamafia said:
Ρε πατριδα αξιζει η rom ή οχι;
Click to expand...
Click to collapse
Πατριωτάκι δεν είναι για καθημερινή χρήση ακόμα.Γιαυτό δεν έχω βγάλει και έτοιμη rom.
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
tas0s said:
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
Click to expand...
Click to collapse
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
cedric123 said:
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
Click to expand...
Click to collapse
The kernel Im using is kalt kaffe's kernel.So I think that if you just replace the kernel and the kernel modules in /system/lib/modules you will be fine.
Im uploading now a zip with the compiled images.
It has the problems I mention in the first post etc.
Just an observation.If the calibration isnt correct the screen is always on landscape mode Propably because it gets wrong screen dimensions.So if you see something like that, calibrate your screen with the TSCalibration app.
When im done with the camera, I will fix the calibration bugs.
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
joilaroi said:
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
Click to expand...
Click to collapse
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
tas0s said:
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
Click to expand...
Click to collapse
thanks. its what i am doing. if i find anything i will give feedback
EDIT - Cant install superuser and have permissions. it downloads su-2.3.1-bin-signed.zip to sdcard but its corrupted. maybe its better if its already on .img
Im getting more MFLOPS with 633Mhz in this rom than with 691Mhz with the other kernel. its now with 4.45 MFLOPS vs 4.1MFLOPS. Nice
Do you know where i can find su-2.3.1-bin-signed.zip?
Ubuntu 10.10 x64 under W7 VMWare will be enought for compile?
PC: C2D [email protected],2GHZ 8GB RAM
Laptop: Lenovo T410 i5 vPro 2,4GHz Quad Core 4GB RAM
I think yes
Hei there.
The idea of this thread is to develop a better kernel for the I9001 in the community. I have compiled my own one for using it in the cwm recovery mod. I've only changed the following so far:
Patched pm2.c file in the samsung kernel sources, see here for the patch:
https://github.com/PabloPL/android_...mmit/46e96915a7e0459dc6b3aec04aa47329371fff44
through menuconfig I've changed the default cpu governor from performance to ondemand.
What we should implement first is init.d support.
I've uploaded my boot.img file for further use here:
http://www.mediafire.com/?6p91s5knka0e0py
It also contains the CWM Recovery
This is great idea bro. Its great to have you here.
Thanks again!!!
Sent from my GT-I9001 using Tapatalk
I would love to see a overclock able kernel! Great idea!
Joost
Sent from my GT-I9001 using XDA App
overclocking module
Hi guys,
coolbho3000 posted source of an overclocking module for HTC Vision. As far I know, it can be used with the SetCPU App together.
http://forum.xda-developers.com/showthread.php?t=813681
Since S+ has a similar Qualcomm chip, it should work as well.
I compiled the overclocking module with the S+ Kernel and packed it into the zImage. The device doesn't boot. Maybe it would be better to follow what coolbho3000 says and adapt the settings
ädu
PS: it needs definitively some adaptions.
Shouldn't we create our own github/bitbucket repositories for kernel and CWM? I'm trying to get my feet wet in generic Android kernel development now, it would be cool to have repository to sync with.
YardE said:
Shouldn't we create our own github/bitbucket repositories for kernel and CWM? I'm trying to get my feet wet in generic Android kernel development now, it would be cool to have repository to sync with.
Click to expand...
Click to collapse
yep of course. I've already opened an account on github. But right now I ain't got time to read the instructions on how to upload repos because I'm busy with applying some changes to FeaMod Recovery and testing them.
I would be happy if a lot of kernel developers would join us!
Edit: The sources for FeaMod recovery 1.1 are on github:
https://github.com/manveru0/FeaMod-Recovery--based-on-CWM-Recovery-
Samsung kernel sources with patched pm2.c:
https://github.com/manveru0/kernel_I9001_samsung
Later I'll try to add "run-parts /system/etc/init.d/" to init.rc, but I'm highly confused from examining ramdisk, because I couldn't find any bash-scripts interpreter (possibly embedded into init executable?) and don't have enough time to continue examining init.rc now. I think, we can add busybox to system image and call it from there. Also, please, modify these lines in default.prop in your future builds:
Code:
ro.secure=0
ro.debuggable=1
As far as I understood, these allow us to use "adb root".
Also, thanks for your awesome work!
YardE said:
Later I'll try to add "run-parts /system/etc/init.d/" to init.rc, but I'm highly confused from examining ramdisk, because I couldn't find any bash-scripts interpreter (possibly embedded into init executable?) and don't have enough time to continue examining init.rc now. I think, we can add busybox to system image and call it from there. Also, please, modify these lines in default.prop in your future builds:
Code:
ro.secure=0
ro.debuggable=1
As far as I understood, these allow us to use "adb root".
Also, thanks for your awesome work!
Click to expand...
Click to collapse
sounds good. I haven't seen a script interpreter either and I'm not quite sure if there is one included in the init. I think it's better we include busybox. Take a look at this thread by the way:
http://forum.xda-developers.com/showthread.php?t=1152740
I'll try to do that testwise.
Here's the adress for my uploaded boot.img-ramdisk without the samsung pictures (we can easily add them again when building a new boot.img):
https://github.com/manveru0/bootimage_ramdisk_I9001
I've already included the changes in default.prop
EDIT: some useful links
http://www.kandroid.org/online-pdk/guide/bring_up.html
http://www.androidenea.com/2009/08/init-process-and-initrc.html
After some init.rd learning I've inserted a service here which should get the job's done, but I have no idea how to test it. Anyway, here is the diff from the normal one:
Code:
[[email protected] boot]$ diff -u3 init.rc ../boot_mod/init.rc
--- init.rc 2011-11-05 22:35:33.194680288 +0400
+++ ../boot_mod/init.rc 2011-11-05 22:24:40.000000000 +0400
@@ -566,7 +566,7 @@
# ihryu 2010.07.19
setprop ro.rfkilldisabled 0
- class_start default
+ #class_start default
# +++++++++++++++++++++++++++++++++++++++++++
# for silent reset
@@ -714,6 +714,10 @@
onrestart restart netd
onrestart restart sensor-daemon
+service initd /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
+ oneshot
+
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin net_raw radio qcom_oncrpc
[[email protected] boot]$
Have also commented "class_start default" which runs twice for some reason. To have this working in theory, you should have busybox installed in /system/xbin with run-parts support. For me, it boots at least ^_^
P.S. It also works if I call command line from adb. Also, adb root works after changing default.prop, good.
P.P.S. You can also remove "charging.rle" from repo, as it is image, too, but why not just keep all the files in repo? git is loyal to binary files as long as you don't try to create a patch. ~_^ Also, you can use .gitignore to exclude some files from git's view at all.
Found excellent reference on init.rd:
http://www.kandroid.org/online-pdk/guide/bring_up.html
Fixed previous post (removed "disabled"), so it should really work now. Going to test it, but not really sure if my test are correct (I'll try to write something to sdcard, but is it mounted r/w at the moment of script running?)
Test failed, thinking of some other, more accurate tests now.
Tried to create file in /cache, and it worked! Here is boot.img with working init.rd and adb root. Flash it via dd (dd if=boot.img of=/dev/block/mmcblk0p8). You should have busybox installed into /system/xbin for this to work.
YardE said:
Found excellent reference on init.rd:
http://www.kandroid.org/online-pdk/guide/bring_up.html
Fixed previous post (removed "disabled"), so it should really work now. Going to test it, but not really sure if my test are correct (I'll try to write something to sdcard, but is it mounted r/w at the moment of script running?)
Test failed, thinking of some other, more accurate tests now.
Click to expand...
Click to collapse
thx for your commit, I'm testing it as well with the adrenaline shot. If init.d support works you should see the changed values.
I do have a working busybox in /system/xbin with run-parts support, so that shouldn't be the issue as my tests didn't work so far.
Okay, gonna delete disable as well.
concerning the images i wasn't so sure about law problems since they include original samsung stuff.
update:
success You did it! Init support works. Though I have to retest it since I've also added user root to the init.rc. Honestly I'm not quite sure if that entry is needed
"user root" is not needed since user is root by default, already tested without it (edited my posts above).
YardE said:
"user root" is not needed since user is root by default, already tested without it (edited my posts above).
Click to expand...
Click to collapse
okay then, i will change the init.rc file and commit it to github. I will name you in the comment to the change. Which name should I use? Is that okay for you?
Oh, you can use either "abbradar" or "YardE", I don't mind. ^_^ Thank you for credits and again for your work. Gonna experiment a bit with CWM now since init.d is working.
YardE said:
Oh, you can use either "abbradar" or "YardE", I don't mind. ^_^ Thank you for credits and again for your work. Gonna experiment a bit with CWM now since init.d is working.
Click to expand...
Click to collapse
I have to thank you for your work as well, mate It's cool working as a team since we are better, faster and should see more bugs than working alone
Edit:
Hmm, we should include busybox in the boot ramdisk, since not every user has busybox installed.
P.S: funny thing is, I've installed adrenaline shotv13 but only part of it works. For example the sdcard tweak works, the sysctl tweaks don't.
P.P.S: i've installed bash on my device, it's much more easier with it to navigate in the adb shell
manveru0 said:
Hmm, we should include busybox in the boot ramdisk, since not every user has busybox installed.
Click to expand...
Click to collapse
What is the max size limit in our device for ramdisk? Also, should we really do so? It will be hard to update in comparison and maybe will be stripped due to size limit, and users basically'll have two versions of busybox - our embedded into boot.img and their own - in /system. (I'm looking on CM and other init.d implementations as an example) But on the other hand, it is really nearly critical level app (although sh is not in boot.img, for example)
P.S: funny thing is, I've installed adrenaline shotv13 but only part of it works. For example the sdcard tweak works, the sysctl tweaks don
Click to expand...
Click to collapse
They also trying to write some values into non-existent /sys nodes, looks like they are meant for other kernel scheduler, like BFQ (should we also try it?)
---------- Post added at 01:25 AM ---------- Previous post was at 01:25 AM ----------
P.P.S: i've installed bash on my device, it's much more easier with it to navigate in the adb shell
Click to expand...
Click to collapse
Good advice, thank you ^_^.
YardE said:
What is the max size limit in our device for ramdisk? Also, should we really do so? It will be hard to update in comparison and maybe will be stripped due to size limit, and users basically'll have two versions of busybox - our embedded into boot.img and their own - in /system. (I'm looking on CM and other init.d implementations as an example) But on the other hand, it is really nearly critical level app (although sh is not in boot.img, for example)
They also trying to write some values into non-existent /sys nodes, looks like they are meant for other kernel scheduler, like BFQ (should we also try it?)
---------- Post added at 01:25 AM ---------- Previous post was at 01:25 AM ----------
Good advice, thank you ^_^.
Click to expand...
Click to collapse
the maximum size of both recovery and boot.img is 7864320 Bytes. Riversource once found that out. It's also in the BoardConfig.mk So we would have enough space for including busybox. But you're right, it would only lead to 2 busyboxes on the device which is not the best idea.
CM uses the BFQ scheduler as far as I know so yeah, we should give it a try
AFAIK, BFS patch nearly fully removes original kernel schedulers, so some work of comparing with original Linux kernel will be needed to do. Although, it may not be true for Android kernel sources or my experience may be wrong, so we should just try it as is before continuing.
Sent from my GT-I9001 using XDA App
YardE said:
AFAIK, BFS patch nearly fully removes original kernel schedulers, so some work of comparing with original Linux kernel will be needed to do. Although, it may not be true for Android kernel sources or my experience may be wrong, so we should just try it as is before continuing.
Sent from my GT-I9001 using XDA App
Click to expand...
Click to collapse
yep, I've looked at the changes the patches make and they remove alot of the CFQ related functions. Fortunately the makefile is patched as well so no work here.
I've have downloaded the patches for kernel 2.6.35 here:
http://algo.ing.unimo.it/people/paolo/disk_sched/sources.php
I applied them to my sources, compiled em and flashed my FeaMod pack with the new kernel and your changes to the boot ramdisk.
So far everything is working on my device I'm gonna upload the patches to github.
Edit: Had to change the .config as well since bfq is not the default I/O scheduler. It is now, I've also activated the hierarchical scheduler support.
Concerning ramdisk git repo: maybe we should move all the code into some folder, for example, "ramdisk", and move README out from there to avoid it being placed into final image? Also, we should point which files are missing from ramdisk in README.
ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
This mod was originally created for the Axon 7, but due to several requests, I've modified a version for the G5, please see below, and post questions or comments in the original thread above. Please state you are a G5 user if you have feedback in that thread, to consolidate user feedback and speed up response time.
Custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the G5 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
3. Must have write protection disabled. If the G5 requires write protection to be disabled, see the code and instruction below:
Using adb shell:
Code:
adb reboot disemmcwp
Using Linux terminal (from your phone, for example):
Code:
reboot disemmcwp
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio, dirty_background_ratio, swappiness, and other parameters of the virtual machine.)
- disabled zRAM for 6 GB variants (RAM compression, again, not needed on this device really, this mod will save you CPU cycles and power) this will not apply to G5 users, you will still have zRAM enabled.
- remapped minfree parameters for LMK (low memory killer) again only for 6 GB variants
- Tuned CFQ scheduler for flash storage devices
- Tuned "core_ctl" module (needs kernel support, I recommend freeza's latest version of BeastMode. For those wondering, yes, you can still use this mod with the stock kernel. It won't break anything.) again this will only apply to devices that support core_ctl at the kernel.
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the file to your device, open up a file explorer (must have root capability), navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
DOWNLOAD:
Is this a new kernel?
Regards
Nathan
Sent from my LG-H850 using XDA Premium HD app
@warBeard_actual
Here :good: :fingers-crossed:
onestyle007 said:
@warBeard_actual
Here :good: :fingers-crossed:
Click to expand...
Click to collapse
Got it man, working on it now. I should have it up soon.
OP updated... Enjoy guys!
Instructions on how to install are in the OP, post your results here
warBeard_actual said:
OP updated... Enjoy guys!
Instructions on how to install are in the OP, post your results here
Click to expand...
Click to collapse
Question,does that matter for your results if I'm using an other governor,cause I'm currently on alucard?? Stock rom but a custom kernel (Asgard for g5 to be exact)
onestyle007 said:
Questions,does that matter for your results if I'm using an other governor,cause I'm currently on alucard?? Stock rom but a custom kernel (Asgard for g5 to be exact)
Click to expand...
Click to collapse
You will notice minimal to no difference if you are using another governor.
Any pro can do a flashable zip?
Any n00b can copy and paste
Will it work on Android 6?
I don't know it's placebo or not but after replacing the file I have now a better GPS fix and accuracy I am on the H850 so thanks on the OP
yes accurancy gps, not lag boot, very smooth. thanks!!!!!!!!!!!
warBeard_actual said:
OP updated... Enjoy guys!
Instructions on how to install are in the OP, post your results here
Click to expand...
Click to collapse
Okay,last night after I've replaced the file, changed to interactive gov,0.2% lost during the night with wifi and mobile data off here is my current stats. Was a bit surprised though and I'm not sure if it's a bug in reading . But hey that's what it shows.
Rhadamanthis said:
yes accurancy gps, not lag boot, very smooth. thanks!!!!!!!!!!!
Click to expand...
Click to collapse
Same for me, let see if the battery will be better too...
Does this only work on LG Stock?
Hi,thanks for mod,great mod running in Nougat Fulmix rom?
OTOGY2002 said:
Hi,thanks for mod,great mod running in Nougat Fulmix rom?
Click to expand...
Click to collapse
Ues
How to mount System as R/W? When I set permission I get error evice is busy
Worked like a charm using Fulmics Rom 2.0.
Hint for some who have issues with mounting RW: Use FX file explorer for this. Works just fine.
Will monitor and report how it works.
My Problem. I go to /system/etc and I can´t find this file. I´m on Root with FX file Manager. What am I doing wrong?