Related
Hey guys,
this is still no kernel, it will only optimize your values for touchscreen using The most important thing in this script is the following line:
touch.pressure.scale = 0.001
Click to expand...
Click to collapse
On my SGS this is the best one. Maybe you can try whats working for you as the best and tell it to me so that i can share the best result.
Files attached to this post:
stock_kpq_file.zip (If you want to go back to the default values)
the_modified_file.zip (THE mod, RootExplorer method)
the_flashable_modified_file.zip (THE mod, CWM method)
Files are usable for:
- Only for Stock or Custom KPQ/KPM Roms! Other will follow if needed
How to install:
- RootExplorer method; download the attached the_modified_file.zip, unpack it and replace the file in /system/usr/idc/mxt224_ts_input.idc with the included one using RootExplorer. Aaaand Reboot.
- CWM method; download the attached the_flashable_modified_file.zip, put it to your sd-card and flash it through CWM. Aaaand Reboot.
Source:
# Copyright (C) 2010 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Input Device Calibration File for the Crespo touch screen.
#
# These calibration values are derived from empirical measurements
# and may not be appropriate for use with other touch screens.
# Refer to the input device calibration documentation for more details.
#
# All edited parts by fuss132 licensed under GPL
# Visit my profile on xda http://forum.xda-developers.com/member.php?u=3264556
# Thanks for using...
touch.pressure.calibration = amplitude
touch.pressure.source = default
touch.pressure.scale = 0.001
MODULE_DESCRIPTION("Touchscreen Driver");
MODULE_LICENSE("GPL");
# Touch Size
touch.touchSize.calibration = pressure
# Tool Size
# Driver reports tool size as an area measurement.
#
# Based on empirical measurements, we estimate the size of the tool
# using size = sqrt(22 * rawToolArea + 0) * 9.2 + 0.
touch.toolSize.calibration = area
touch.toolSize.areaScale = 22
touch.toolSize.areaBias = 0
touch.toolSize.linearScale = 9.2
touch.toolSize.linearBias = 0
touch.toolSize.isSummed = 0
# Pressure
# Driver reports signal strength as pressure.
#
# A normal thumb touch typically registers about 100 signal strength
# units although we don't expect these values to be accurate.
touch.pressure.calibration = amplitude
touch.pressure.source = default
touch.pressure.scale = 0.001
# Size
touch.size.calibration = normalized
# Orientation
touch.orientation.calibration = none
Click to expand...
Click to collapse
And why a new Thread?
Very easy. This mod is completely different to my other script. I don´t want to confuse the users ^^
I m gonna test it!!! Thanks Fuss!!
mihkohuy said:
I m gonna test it!!! Thanks Fuss!!
Click to expand...
Click to collapse
Ok, but please re-download the flashable.zip cause there was something missing in it. Fixed it now
Alright, re-download it and test it right now
---------- Post added at 12:50 AM ---------- Previous post was at 12:42 AM ----------
Flashed. Seems much smoother now, the touchscreen. Thx!!
fuss132 said:
Ok, but please re-download the flashable.zip cause there was something missing in it. Fixed it now
Click to expand...
Click to collapse
working on KPM too
Thanks fuss!!!! Great job, you're great even if you don't have the device yet!!!
Great dude, seems to be working
can't imagine wt will u bring once u have the device itself
I can feel changes thanks for tweak dude.
I'm on kpq.
Sent from my GT-I9003 using Tapatalk
hehe... good inspiration from ICS tweaking
DooMLoRD said:
hehe... good inspiration from ICS tweaking
Click to expand...
Click to collapse
Nope google´s idea
But why ICS Tweaking?
Works fine on XWKPG, good finding. Just make the changes directly on file using text editor in Root explorer/ applicable to most of the ROMs i think.
how to flash this using CWM??
do we have to use flash Update option in CWM??
deepanshu sharma said:
how to flash this using CWM??
do we have to use flash Update option in CWM??
Click to expand...
Click to collapse
- Enter CWM
- Select "install zip from sd-card"
- Select the downloaded flashable zip
- Select Yes
- Reboot
just did it!
waitin to boot
EDIT:
works great!!
thanks dominik
works good..
Thanks fuss, I am using your Ramscritp and this mod and both work perfect in KPQ. The next step ... videocalls please ... (you know, I have tested everything and I know the issues of each app) or else when you have your i9003, thanks for everything you are doing.
Dear,
Can you make it for ZHKPD?
May be it can make the handing writing better..^_^
Sent from my GT-I9003 using XDA App
Requesting for DXKP9 version please. Would live to try this.
skchattha said:
Works fine on XWKPG, good finding. Just make the changes directly on file using text editor in Root explorer/ applicable to most of the ROMs i think.
Click to expand...
Click to collapse
lee82gx said:
Requesting for DXKP9 version please. Would live to try this.
Click to expand...
Click to collapse
ckm814 said:
Dear,
Can you make it for ZHKPD?
May be it can make the handing writing better..^_^
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
read the posts above mates IT WORKS ON ALL THE FIRMWARES...its not related to regions or different firmwares!!!!!!!!!!
We need your help.
We are using yp-g50.
I am sure that a lot of people donno g50.
One or two yrs ago
Samsung released a mp3 named
Yp-g50.(galaxy player)
Yp-g50's spec is almost same as galaxy3/apollo.
It was released in some Europe countries and s.korea.
So oneday i wanted to edit build prop and when i opened it i saw a name apollo. I knew that g50 is based on i5801.
So yesterday.. I went to xda and downloaded i5801 firmware n i flashed it by odin.
Of course it did not work.
So i opened the tar file and i deleted logo.png and modem.bin and i flashed it again.
It did not worked.
Then i changed zimage or zlimage(i dont remember the name well) which is in g50's firmware.
Again,i flashed it.
Then!!!! It worked!!!
However,the status bar did not move and it seemed that the system is not stable(it kills its system for every 3or4minute.
So i downloaded kyora rom and one gingerbread rom which is themed in blue razr?(for got the name sorry)
N did the same work and it failed.
I can give you everything so could anyone help us to port custom roms to g50??
Sorry for bad english..i am korean...
We really need your help because we only have 1official firmware and that is eclair...
Sent from my YP-G50 using XDA
People who dont believe it this is the screenshot.
Sent from my YP-G50 using XDA
You'll need to ask someone who has both, galaxy 3 and g50. Anyways, this is very interesting flashing a different phone's firmware......really cool!!
Of course I tried, but samsung doesn't sell galaxy 3 in korea and malaysia(I'm studying in malaysia for a while)
As I said in the previous post, yp-g50 is based on galaxy3. So I was able to port galaxy3's firmware to yp-g50 without big edit.
HOWEVER, the difference is that there is no logo.png and modem.bin. Moreover, kernel(zimage) is bit different. So I think we need a person who can edit the kernel for yp-g50. That's all.
I wanna donate my yp-g50 to dev, but as I'm student, I cannot. So I'll give our kernel to dev and edit it and I will test it. I'll report the result. I am sure that it will be easy to edit kernel becuz both devices are similar...
I WILL NOT BLAME THE DEVELOPER EVEN THOUGH MY MP3 BRICKS OR BREAKS.
Sent from my Desire HD using xda premium
a961009 said:
Of course I tried, but samsung doesn't sell galaxy 3 in korea and malaysia(I'm studying in malaysia for a while)
As I said in the previous post, yp-g50 is based on galaxy3. So I was able to port galaxy3's firmware to yp-g50 without big edit.
HOWEVER, the difference is that there is no logo.png and modem.bin. Moreover, kernel(zimage) is bit different. So I think we need a person who can edit the kernel for yp-g50. That's all.
I wanna donate my yp-g50 to dev, but as I'm student, I cannot. So I'll give our kernel to dev and edit it and I will test it. I'll report the result. I am sure that it will be easy to edit kernel becuz both devices are similar...
I WILL NOT BLAME THE DEVELOPER EVEN THOUGH MY MP3 BRICKS OR BREAKS.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Also if you help us, we can give our firmware to you. Yp-g50 is a mp3 player so it is focused on music. In our firmware, we have "soundalive"(upgrade version of dnse) sound enhancer. In my opinion itis better than dsp. To flash the firmware you just need to change the kernel I think.
So both get benefit.
Sent from my Desire HD using xda premium
ok, but anyways, why do you want g3 firmwares?
J.Purungrit said:
ok, but anyways, why do you want g3 firmwares?
Click to expand...
Click to collapse
because they have only eclair's firmware for their phone...and specs are very simmilar..so they wan't at least froyo build....
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.0
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rkoby13 said:
because they have only eclair's firmware for their phone...and specs are very simmilar..so they wan't at least froyo build....
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.0
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Yes.. So is there any developer can help us?? If no,please spread this.. Will i upload yp-g50's firmware in galaxy3 development?? So that anyone can see??
By using this,may be you can port soundalive instead of dnse.
Sent from my YP-G50 using XDA
a961009 said:
Yes.. So is there any developer can help us?? If no,please spread this.. Will i upload yp-g50's firmware in galaxy3 development?? So that anyone can see??
By using this,may be you can port soundalive instead of dnse.
Sent from my YP-G50 using XDA
Click to expand...
Click to collapse
first of all, we need the source!
EDIT: Can anyone flash g50 firmware in g3???
Samsung's firmware aren't open source
J.Purungrit said:
first of all, we need the source!
EDIT: Can anyone flash g50 firmware in g3???
Click to expand...
Click to collapse
So it means that if there is a source released from samsung, we have hope right?? I will try to find it.
To flash the g50 firmware. I think you change zimage and delete modem... I am not sure since i dont have galaxy3
Sent from my YP-G50 using XDA
a961009 said:
So it means that if there is a source released from samsung, we have hope right?? I will try to find it.
To flash the g50 firmware. I think you change zimage and delete modem... I am not sure since i dont have galaxy3
Sent from my YP-G50 using XDA
Click to expand...
Click to collapse
don't worry, I know what to do, just upload the .tar file......and btw, you don't have hope, cause samsung is close source.....
J.Purungrit said:
don't worry, I know what to do, just upload the .tar file......and btw, you don't have hope, cause samsung is close source.....
Click to expand...
Click to collapse
HURRAY there is!!!
I love u samsung!!
opensource.samsung.com
Go to mp3 part.
My g50 refuses to enter becuz of protection. Sorry
Just find yp-g50.
And i will upload tar file today .(for me today is 17.april now it is 1.49)
Sent from my YP-G50 using XDA
This more sounds like a guy a few months ago that claimed he installed a Galaxy 5 ROM on the Galaxy 3 and went around harping on about how he reckons everyone should do it, but what actually happened was all the files in the TAR did not actually match what was in the OPS so nothing was flashed and he was actually just using the Galaxy 3 ROM still.
By renaming zImage to ZlImage, you're making it not flash anything.
But anyway to show us what hardware is in the phone, give me all the files produced by these commands (from Terminal Emulator or ADB shell) (they will be in the sdcard):
ls /sys/devices/platform/ > /sdcard/platform.txt
cat /proc/cpuinfo > /sdcard/cpuinfo.txt
cat /proc/meminfo > /sdcard/meminfo.txt
lsmod > /sdcard/lsmod.txt
If any of these match the Galaxy 3 then you're in luck, but I am more placing bets that it is SIMILAR hardware, but not the same.
hillbeast said:
This more sounds like a guy a few months ago that claimed he installed a Galaxy 5 ROM on the Galaxy 3 and went around harping on about how he reckons everyone should do it, but what actually happened was all the files in the TAR did not actually match what was in the OPS so nothing was flashed and he was actually just using the Galaxy 3 ROM still.
By renaming zImage to ZlImage, you're making it not flash anything.
But anyway to show us what hardware is in the phone, give me all the files produced by these commands (from Terminal Emulator or ADB shell) (they will be in the sdcard):
ls /sys/devices/platform/ > /sdcard/platform.txt
cat /proc/cpuinfo > /sdcard/cpuinfo.txt
cat /proc/meminfo > /sdcard/meminfo.txt
lsmod > /sdcard/lsmod.txt
If any of these match the Galaxy 3 then you're in luck, but I am more placing bets that it is SIMILAR hardware, but not the same.
Click to expand...
Click to collapse
I didnt change the name kk. I just forgot the name.. ofcourse without changing the zimage it canot pass. I tried everything i will prove that galaxy 3 and yp-g50 is almost same wait for awhile kk
EDIT: i did not know that xda app cannot upload files so i will copy the text from the files
Sent from my YP-G50 using XDA
hillbeast said:
This more sounds like a guy a few months ago that claimed he installed a Galaxy 5 ROM on the Galaxy 3 and went around harping on about how he reckons everyone should do it, but what actually happened was all the files in the TAR did not actually match what was in the OPS so nothing was flashed and he was actually just using the Galaxy 3 ROM still.
By renaming zImage to ZlImage, you're making it not flash anything.
But anyway to show us what hardware is in the phone, give me all the files produced by these commands (from Terminal Emulator or ADB shell) (they will be in the sdcard):
ls /sys/devices/platform/ > /sdcard/platform.txt
cat /proc/cpuinfo > /sdcard/cpuinfo.txt
cat /proc/meminfo > /sdcard/meminfo.txt
lsmod > /sdcard/lsmod.txt
If any of these match the Galaxy 3 then you're in luck, but I am more placing bets that it is SIMILAR hardware, but not the same.
Click to expand...
Click to collapse
From platform.txt
uevent
power
power.0
s3c-keypad
s3cfb.0
s3c2410-wdt
s3c2410-rtc
s3c2440-i2c.0
s3c2440-i2c.2
i2c-gpio.3
i2c-gpio.4
i2c-gpio.7
i2c-gpio.8
s3c-sdhci.0
s3c-sdhci.1
s3c-sdhci.2
s3c-fimc.0
s3c-fimc.1
s3c-fimc.2
s3c-jpg
s3c-mfc
s3c-adcts
s6d04d1-backlight
apollo-battery
qt602240-ts
sec_headset
s3c-usbgadget
s3c-g3d
s3c-g2d.0
dpram-device
bcm4329_rfkill
virtual_rtc
proximity_cm3607
android_pmem.0
android_pmem.2
android_pmem.5
android_pmem.6
android_pmem.7
s5pc100-uart.0
s5pc100-uart.1
s5pc100-uart.2
alarm
bma020-acceleromete
soc-audio.0
From cpuinfo.txt
Processor : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS : 664.38
Features : swp half thumb fastmult vfp edsp java
CPU implementer : 0x41
CPU architecture: 6TEJ
CPU variant : 0x0
CPU part : 0xb76
CPU revision : 7
Hardware : YP-G50
Revision : 0000
Serial : 479061a1c4107e00
From meminfo.txt
MemTotal: 215652 kB
MemFree: 9136 kB
Buffers: 5980 kB
Cached: 57028 kB
SwapCached: 0 kB
Active: 87560 kB
Inactive: 88900 kB
Active(anon): 56340 kB
Inactive(anon): 62376 kB
Active(file): 31220 kB
Inactive(file): 26524 kB
Unevictable: 3416 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 48 kB
Writeback: 0 kB
AnonPages: 116880 kB
Mapped: 35656 kB
Slab: 10580 kB
SReclaimable: 4136 kB
SUnreclaim: 6444 kB
PageTables: 10276 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 107824 kB
Committed_AS: 4747688 kB
VmallocTotal: 606208 kB
VmallocUsed: 83424 kB
VmallocChunk: 480260 kB
From build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ECLAIR
ro.build.display.id=ECLAIR.KD2
ro.build.version.incremental=KD2
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Wed Apr 6 19:19:14 KST 2011
ro.build.date.utc=1302085154
ro.build.type=user
ro.build.user=slim
ro.build.host=midsys
ro.build.tags=test-keys
ro.product.model=YP-G50
ro.product.brand=samsung
ro.product.name=YP-G50
ro.product.device=YP-G50
ro.product.board=YP-G50
ro.product.cpu.abi=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=ko
ro.product.locale.region=KR
ro.wifi.channels=
ro.board.platform=s5p6442
# ro.build.product is obsolete; use ro.product.device
ro.build.product=YP-G50
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=YP-G50-user 2.1-update1 ECLAIR KD2 release-keys
ro.build.fingerprint=samsung/YP-G50/YP-G50/YP-G50:2.1-update1/ECLAIR/KD2:user/release-keys
# Samsung Specific Properties
ro.build.PDA=G50KD2
ro.build.hidden_ver=G50KD2
ro.build.changelist=SR2
# end build properties
#
# system.prop for apollo
#
#ROSSI Project by sam.lim (2010.07.03)
rild.libpath=/system/lib/libsec-ril-apalone.so
#ROSSI Project by sam.lim End
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=120
# wifi
wifi.interface=eth0
#
# ADDITIONAL_BUILD_PROPERTIES
#
dalvik.vm.heapsize=32m
windowsmgr.support_rotation_270=true
dalvik.vm.heapsize=32m
windowsmgr.support_rotation_270=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.1_r12
ro.config.ringtone=Samsungtune.ogg
ro.config.notification_sound=TaDa.ogg
ro.config.alarm_alert=Alarm.ogg
ro.opengles.version=131072
ro.com.google.clientidbase=android-samsung
net.bt.name=Android
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
I am sure that we have so many rams is because we don't have modem inside the devices(of course. It is mp3.) actual size is 256mb.
Sorry that it is very long.
Sent from my YP-G50 using XDA
Darius_AWS said:
Samsung's firmware aren't open source
Click to expand...
Click to collapse
U know what? Samsung released sources almost every devices.. even i5800 n i5801 is there! Of course yp-g50 is also there kk
Just go
opensource.samsung.com
Visit mobile-mobile phones
Sent from my Desire HD using xda premium
Kernel sources not firmware
Sent from my GT-I5800 using xda premium
Darius_AWS said:
Kernel sources not firmware
Sent from my GT-I5800 using xda premium
Click to expand...
Click to collapse
Oh my god we also need that?
Sent from my YP-G50 using XDA
a961009 said:
ro.board.platform=s5p6442
Click to expand...
Click to collapse
Indeed you do have the same chipset in your device, and looking at the sys platform devices, it would appear you have the same guts as our phone, albeit without a modem.
One last thing, can you give me the output of this:
cat /proc/partitions > /sdcard/partitions.txt
dmesg > /sdcard/dmesg.txt
The dmesg will be huge so put it in a code box (do that by typing [ CODE ] and [ /CODE ], but without the spaces).
EDIT: I am downloading the source code for your kernel. Will see what's in there.
!!!FIRST READ THEN POST!!!
I am not a programmer so do not shout at me , I try to help you gather as much information as possible. Of course, I trying port kernel by myself but is going very slowly.
I decided to start this thread and share with you information that I managed to collect. Topic applies to porting the kernel 3.0.8 for i9001.
I found a phone that has the same motherboard, CPU and GPU as the i9001 and already got an official kernel 3.0.8.
Why this kernel is good for us? - because has already almost all drivers needed by i9001 so porting will be easier.
Why we need it - better battery life, better cooperation with ICS/JB, better speed, new possibilities? And why not?
- What needs to be done?
- include and port file from 2.6.35.X - arch/arm/mach-msm/board-ariesve.c
- include/find missing drivers for i9001
- Links:
i9001 spec - Samsung Galaxy S Plus
U8860 spec - Huawei Honor
Kernel sources
Thread - Huawei U8860 Honor / Honour / Glory - Index
How to build kernel:
This howto is working only with 2.6.35.X kernel, when this project will be finished will add HOWTO for 3.0.8
You need linux machine, i don't know it is possible on Windows and if so i don't help you with that!!!
1. Download toolchain.
Download toolchain and extract it to /opt/ directory.
Should looks like:
Code:
/opt/arm-eabi-4.4.3/
2. Set up evn.
Edit your:
Code:
~/.bashrc
file and add at the end of file this two rows:
export CROSS_COMPILE=/opt/arm-eabi-4.4.3/bin/arm-eabi-
export CCOMPILE=/opt/arm-eabi-4.4.3/bin/arm-eabi-
Click to expand...
Click to collapse
3. Download kernel - 2.6.35.14.
You can download kernel sources from Arco, Skywalker01 or Vitaliy_y repo, and extract to ~/kernel/, this kernels has already needed drivers etc.
4. Compile kernel:
When i'm compiling kernel i'm doing it in this way:
make ARCH=arm mrproper -j3
make ARCH=arm clean -j3
adb pull /proc/config.gz ./
gzip -d ./config.gz
mv ./config ./.config
make ARCH=arm oldconfig -j3
make ARCH=arm menuconfig -j3
make ARCH=arm -j3
Click to expand...
Click to collapse
5. Output files.
mkdir -p ../kernel-out/modules
cp arch/arm/boot/zImage ../
find ./ -name "*.ko" -exec cp {} ../kernel-out/modules \;
Click to expand...
Click to collapse
6. Create boot.img
split_bootimg.pl boot.img
mkdir ramdisk
cd ramdisk
gzip -dc ../boot.img-ramdisk.gz | cpio -i
Click to expand...
Click to collapse
- Swap kernel and modules and then:
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
Click to expand...
Click to collapse
- Creat boot.img
mkbootimg --kernel zImage --ramdisk newramdisk.cpio.gz --base 0x00400000 -o boot.img
Click to expand...
Click to collapse
Download: split_bootimg, mkbootimg
Extract files here /usr/local/bin and set permissions to 755.
What i have done:
1. Added board-ariesve.c here:
arch/arm/mach-msm/board-ariesve.c
2. Included Ariesve board to Kconfig and Makefile.
3. Added missing files:
include/linux/fsa9480.h
arch/arm/mach-msm/include/mach/msm_reqs.h
Compilation error:
arch/arm/mach-msm/board-ariesve.c: In function 'pm8058_gpios_init':
arch/arm/mach-msm/board-ariesve.c:329: error: variable 'sdcc_det' has initializer but incomplete type
arch/arm/mach-msm/board-ariesve.c:330: error: unknown field 'direction' specified in initializer
arch/arm/mach-msm/board-ariesve.c:330: warning: excess elements in struct initializer
error, forbidden warning: board-ariesve.c:330
make[1]: *** [arch/arm/mach-msm/board-ariesve.o] Error 1
Click to expand...
Click to collapse
Cool ! Thank you !
oisis said:
I am not a programmer so do not shout at me , I try to help you gather as much information as possible. Of course, I trying port kernel by myself but is going very slowly.
I decided to start this thread and share with you information that I managed to collect. Topic applies to porting the kernel 3.0.8 for i9001.
I found a phone that has the same motherboard, CPU and GPU as the i9001 and already got an official upgrade to ICS.
Why this kernel is good for us? - because has already almost all drivers needed by i9001 so porting will be easier.
What needs to be done?
- include board-ariesve.c - Board spec.
- include missing drivers for i9001
Links:
i9001 spec - Samsung Galaxy S Plus
U8860 spec - Huawei Honor
Kernel sources
Thread - Huawei U8860 Honor / Honour / Glory - Index
Click to expand...
Click to collapse
page not found - Huawei U8860 Honor / Honour / Glory - Index
What advantages will kernel 3.x have for us?
Sent from my GT-I9001 using XDA
chasemyass said:
page not found - Huawei U8860 Honor / Honour / Glory - Index
Click to expand...
Click to collapse
Fixed.
EternalFame said:
What advantages will kernel 3.x have for us?
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
New drivers, better cooperation with ICS?
Awesome project!
What's the current status? How far does your current compile boot?
oisis said:
Fixed.
New drivers, better cooperation with ICS?
Click to expand...
Click to collapse
Kay
Just asked out of interest
Does it also bring some speed?
Sent from my GT-I9001 using XDA
EternalFame said:
Kay
Just asked out of interest
Does it also bring some speed?
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
Not to much but can bring some. Also maybe bring better battery life, new possibilities.
hey about the jelly bean thing,i sent you the nexus boot.img with modified init.rc and init.traces .rc. did you try comparing them with some tool? like winmerge.
Doomsday94 said:
hey about the jelly bean thing,i sent you the nexus boot.img with modified init.rc and init.traces .rc. did you try comparing them with some tool? like winmerge.
Click to expand...
Click to collapse
First we need kernel then boot.img and init.rc scripts.
oisis said:
First we need kernel then boot.img and init.rc scripts.
Click to expand...
Click to collapse
you mean the 3.0 kernel?
Good luck, oisis. I do not know if this will help with something, but the dev tom3q, wrote kernel 3.0 for i5700 spica. Maybe he has some tips .....
Doomsday94 said:
you mean the 3.0 kernel?
Click to expand...
Click to collapse
Yes.
drummer1839 said:
Good luck, oisis. I do not know if this will help with something, but the dev tom3q, wrote kernel 3.0 for i5700 spica. Maybe he has some tips .....
Click to expand...
Click to collapse
Thanks for link.
PDK
Good to see progress.. By the way, you guys might already know this, but Google release a "Platform development Kit" in Google IO 2012, to help developers and manufacturers port new Android OSs (like Jelly Bean) to their devices.
I found the link below, maybe it can help bringing Jelly Bean to our device in the future :silly:
http://www.kandroid.org/online-pdk/guide/index.html
Thanks
So guys a quick review.
Oisis and me are both working on kernel now.
We are using parts of the Huawei honor kernel to make ICS camera work. But please be patient that it will take a while till we finish. and we dont give guarantee that ALL will work CORRECTLY then.
But for you guys, to see the status of developement and we are not bluffing ^^
Here you see the drivers which we'll use in new kernel.
https://github.com/dzo/kernel_huawei/tree/master/drivers
****Update Status****
Will be new in kernel:
- Changing drivers for radio (maybe will work then) -> https://github.com/dzo/kernel_huawei/tree/master/drivers/media
- Changing wifi drivers for better wifi thetering performance
- Changing Audio/Video drivers for ICS Camera -> https://github.com/dzo/kernel_huawei/tree/master/drivers/video
- And other little things will be changed (better battery usage -> new drivers/ better performance ... )
- Will change GPU drivers too -> https://github.com/dzo/kernel_huawei/tree/master/drivers/gpu
As i see those drivers of huwai are the same as Samsung galaxy s plus?
Sent from my GT-I9001 using xda app-developers app
Raimon93 said:
As i see those drivers of huwai are the same as Samsung galaxy s plus?
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
Its mostly the same Hardware, so we can use many things of that device, because it got official ICS with everything working!
Keinbockwurst said:
Its mostly the same Hardware, so we can use many things of that device, because it got official ICS with everything working!
Click to expand...
Click to collapse
That's true, because that device got a official ICS update and the hardware Is nearly the same we can use its drivers and we think it will work.
Kernel will be finished to try in this week I think...
Sent from my GT-I9001 using xda app-developers app
This great rom is build from source. I just compiled it while the PSX team did all the work. A little about the rom:
Welcome to Pure Speed X
PSX is a fast, built from AOSP source (4.4.2) Rom with an emphasis on speed and performance. Our goal is to provide unrivaled performance, stability, and a lightweight Rom with a handful of valuable features. We are not, nor ever will be focused on adding every feature out there. We will always be searching for ways to make it faster, more stable, more secure, and feature rich, but never at the cost of performance.
PSX V3
This version has all the features listed below. It is complete and not much work is being done on it. The new project will be called PSX Fat Lady.
PSX Light
This is the newest branch. Everything is being built from ground up. This is purely for performance and speed. No added features just pure optimizations. PSX Fat Lady will be based on this version. PSX Light is more up to date, but lacks features.
Team PSX Consists of:
ctfrommn
rustyjay
Martin_Ro
Banks
dully79
All the thanks goes out to those developers mentioned above for coming up with such a fantastic rom.
Directions
Download Rom, GApps, and SuperSu
Reboot into recovery
Make nandroid
Factory reset or wipe dalvik/cache/system/data
Flash Rom, GApps, and SuperSu
If ROM fails to flash, reboot into recovery and try again
Enjoy the Best Rom
Features/Changelog
Active Display
Quick Settings customization
Double Tap to Sleep
Quiet Hours
Immersive Mode/Tile
Lock Screen Targets
Status Bar tweaks
Navigation Bar tweaks
Optimizations
Much much more
PLSX FINAL
PSX_GROUPER_LIGHT 2014-02-20
PSX_FatLady Feb 24, 2014
psx_grouper_2014_02_23
Downloads PSX V3
PSX Grouper 30-01-14 MIRROR
PSX GApps
PA GApps
SuperSu
Source Code
Team Slim
Team Omni
Team CM
Vanir AOSP
Team Codefire
Team PA
@rascarlo
Source
PSX Github
Screenshots
Settings
Interface
About Tablet
Downloading now. Just can't resist the promise of something unique.
Sent from my Nexus 7 using Tapatalk
TardyKilla said:
Downloading now. Just can't resist the promise of something unique.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Hopefully you won't be disappointed. I've always used CM since CM5. Since I was introduced to this rom for my phone about a month ago, there's no looking back to any other rom for me.
This is the stable build with no other additions. The team is working on a psx-light (speed and performance with very few features). Once that's done, they'll add a psx-fat lady version with the usual customizations.
Anyway, this rom is stable with many features. Hope you all enjoy it or at least give it a shot.
this is one of the best on hammerhead (for me) i'm trying plsx and i love it because it has useful features... and is very stable & fast
is great to see a psx build on Nexus 7 too!
why don't You ask to the team (on their forum) to become official mantainer..?
thanks for the build
enricocid said:
this is one of the best on hammerhead (for me) i'm trying plsx and i love it because it has useful features... and is very stable & fast
is great to see a psx build on Nexus 7 too!
why don't You ask to the team (on their forum) to become official mantainer..?
thanks for the build
Click to expand...
Click to collapse
I'm using PSX on the LG Optimus G. It's pretty amazing. I build PLSX for Grouper and the Optimus G, but I need Active Display at the minimum. Gotten so used to active display, can't do without it. Is there an xposed module that does that?
I don't want to become an official maintainer. Don't want the responsibility of building in a timely manner. This way, I can build and release whenever. This PSX build is pretty complete and I doubt any changes will be made to it since they started re-basing everything off PSX-Light. Once PSX-Fat Lady is up, I'll build and post.
jblazea50 said:
I'm using PSX on the LG Optimus G. It's pretty amazing. I build PLSX for Grouper and the Optimus G, but I need Active Display at the minimum. Gotten so used to active display, can't do without it. Is there an xposed module that does that?
I don't want to become an official maintainer. Don't want the responsibility of building in a timely manner. This way, I can build and release whenever. This PSX build is pretty complete and I doubt any changes will be made to it since they started re-basing everything off PSX-Light. Once PSX-Fat Lady is up, I'll build and post.
Click to expand...
Click to collapse
Pick this commits for active display
http://forum.xda-developers.com/showpost.php?p=45736797&postcount=2
Please add Screenshot
matqow said:
Please add Screenshot
Click to expand...
Click to collapse
It's an AOSP rom. Screenshots will look similar to any other AOSP rom. I did put some dropbox link for Settings, Interface, and About Tablet screens.
Great to see @enricocid on the boards! I'm still using little bro's Advanced Stock Rom, but I feel the urge to upgrade to a rom build on KK. This looks like it might do the trick! (and thanks again to you and Ivn88 for your previous contributions!)
And thanks to OP for bringing this to us! Will flash later tonight and report back. BTW; is there a requirement to flash using a specific recovery?
orlzzt said:
Great to see @enricocid on the boards! I'm still using little bro's Advanced Stock Rom, but I feel the urge to upgrade to a rom build on KK. This looks like it might do the trick! (and thanks again to you and Ivn88 for your previous contributions!)
And thanks to OP for bringing this to us! Will flash later tonight and report back. BTW; is there a requirement to flash using a specific recovery?
Click to expand...
Click to collapse
I doubt it as long as you are using the latest recovery. I think I'm on 2.6.3.0 TWRP. If after you make nandroid and do factory reset, then the rom fail to flash, you reboot into recovery and try again.
jblazea50 said:
I doubt it as long as you are using the latest recovery. I think I'm on 2.6.3.0 TWRP. If after you make nandroid and do factory reset, then the rom fail to flash, you reboot into recovery and try again.
Click to expand...
Click to collapse
I had the same problem using TWRP 2.6.3.1. When I rebooted into recovery had to root again. Then installed ROM, Capps and SU. All good now. Thank you.
Sent from my VS980 4G using Tapatalk
55Pegasus said:
I had the same problem using TWRP 2.6.3.1. When I rebooted into recovery had to root again. Then installed ROM, Capps and SU. All good now. Thank you.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Yup, on first attempt the PSX zip failed; I rebooted recovery and then everything worked like a charm. Restoring my apps now; first impression is that this rom rocks! Very nice work, and thanks to all of you for your help and advice on installing. I'll report back if anything borks.
This is my first attempt at a KK rom (my GS3 is still on 4.1.2 JB), so I'm really excited about test driving this! Thanks!
enricocid said:
Pick this commits for active display
http://forum.xda-developers.com/showpost.php?p=45736797&postcount=2
Click to expand...
Click to collapse
I tried to cherry pick the commits. I got this:
Code:
error: could not apply 0657865... active display settings
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
Recorded preimage for 'src/com/android/settings/Settings.java'
jblazea50 said:
I tried to cherry pick the commits. I got this:
Code:
error: could not apply 0657865... active display settings
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
Recorded preimage for 'src/com/android/settings/Settings.java'
Click to expand...
Click to collapse
try
Code:
git status
what is the output?
First 12 hours, and I can say this thing is a BEAST! Very fast; easy install; everything working! JBlaze did not lie when he said this thing had some legs on her. Speed is nice, but I have to say, never having been one to toy around with CM builds (I'm a TouchWiz guy from the GS3 forums) this has features on it that are really amazing! Thanks again to the team and to the OP for bringing this to us. @TexasLTE, can a brother get a Nexus 7 (2012) banner with some PSX graphics, and a big "Amen"?!
I've build PLSX (PSX-light). This is the new project and it mostly bare bones with just speed enhancements. You can install Xposed Framework and Gravity Box to get majority of the features that pleases you. If anyone wants to test it out, here are the links:
psx-light grouper 2014-02-01
Mirror
orlzzt said:
@TexasLTE, can a brother get a Nexus 7 (2012) banner with some PSX graphics...
Click to expand...
Click to collapse
:fingers-crossed: ...see if this looks OK... :fingers-crossed:
http://i1202.photobucket.com/albums/bb374/TexasEpic/Requested%20Banners/orlzzt-Nexus7_zps315f682e.png
TexasLTE said:
:fingers-crossed: ...see if this looks OK... :fingers-crossed:
http://i1202.photobucket.com/albums/bb374/TexasEpic/Requested%20Banners/orlzzt-Nexus7_zps315f682e.png
Click to expand...
Click to collapse
Llloovvvee it!! Love it love it love it! Thanks! Check your Red Bull account!
enricocid said:
try
Code:
git status
what is the output?
Click to expand...
Click to collapse
Code:
[email protected]:~/psx-light/frameworks/base$ git status
# HEAD detached at 0324d29
# You are currently cherry-picking.
# (fix conflicts and run "git commit")
#
# Changes to be committed:
#
# modified: core/java/android/app/INotificationManager.aidl
# new file: packages/SystemUI/res/drawable-hdpi/ic_ad_dismiss_notification_activated.png
# new file: packages/SystemUI/res/drawable-hdpi/ic_ad_dismiss_notification_normal.png
# new file: packages/SystemUI/res/drawable-hdpi/ic_ad_lock_pressed.png
# new file: packages/SystemUI/res/drawable-hdpi/ic_ad_morenotifications.png
# new file: packages/SystemUI/res/drawable-hdpi/ic_ad_target_unlock_activated.png
# new file: packages/SystemUI/res/drawable-hdpi/ic_ad_target_unlock_normal.png
# new file: packages/SystemUI/res/drawable-hdpi/ic_ad_unknown_icon.png
# new file: packages/SystemUI/res/drawable-hdpi/ic_ad_unlock.png
# new file: packages/SystemUI/res/drawable-hdpi/ic_handle_notification_normal.png
# new file: packages/SystemUI/res/drawable-mdpi/ic_ad_dismiss_notification_activated.png
# new file: packages/SystemUI/res/drawable-mdpi/ic_ad_dismiss_notification_normal.png
# new file: packages/SystemUI/res/drawable-mdpi/ic_ad_lock_pressed.png
# new file: packages/SystemUI/res/drawable-mdpi/ic_ad_morenotifications.png
# new file: packages/SystemUI/res/drawable-mdpi/ic_ad_target_unlock_activated.png
# new file: packages/SystemUI/res/drawable-mdpi/ic_ad_target_unlock_normal.png
# new file: packages/SystemUI/res/drawable-mdpi/ic_ad_unknown_icon.png
# new file: packages/SystemUI/res/drawable-mdpi/ic_ad_unlock.png
# new file: packages/SystemUI/res/drawable-mdpi/ic_handle_notification_normal.png
# new file: packages/SystemUI/res/drawable-xhdpi/ic_ad_dismiss_notification_activated.png
# new file: packages/SystemUI/res/drawable-xhdpi/ic_ad_dismiss_notification_normal.png
# new file: packages/SystemUI/res/drawable-xhdpi/ic_ad_lock_pressed.png
# new file: packages/SystemUI/res/drawable-xhdpi/ic_ad_morenotifications.png
# new file: packages/SystemUI/res/drawable-xhdpi/ic_ad_target_unlock_activated.png
# new file: packages/SystemUI/res/drawable-xhdpi/ic_ad_target_unlock_normal.png
# new file: packages/SystemUI/res/drawable-xhdpi/ic_ad_unknown_icon.png
# new file: packages/SystemUI/res/drawable-xhdpi/ic_ad_unlock.png
# new file: packages/SystemUI/res/drawable-xhdpi/ic_handle_notification_normal.png
# new file: packages/SystemUI/res/drawable/ad_active_notification_background.xml
# new file: packages/SystemUI/res/drawable/ic_ad_dismiss_notification.xml
# new file: packages/SystemUI/res/drawable/ic_ad_target_unlock.xml
# new file: packages/SystemUI/res/layout-land/active_display_content.xml
# new file: packages/SystemUI/res/layout/active_display.xml
# new file: packages/SystemUI/res/layout/active_display_content.xml
# new file: packages/SystemUI/res/layout/glow_pad_container.xml
# new file: packages/SystemUI/res/layout/glow_pad_view.xml
# new file: packages/SystemUI/res/values/vendor_arrays.xml
# new file: packages/SystemUI/res/values/vendor_dimens.xml
# new file: packages/SystemUI/res/values/vendor_donottranslate.xml
# new file: packages/SystemUI/res/values/vendor_styles.xml
# modified: packages/SystemUI/src/com/android/systemui/statusbar/BaseStatusBar.java
# modified: packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java
# new file: packages/SystemUI/src/com/android/systemui/statusbar/policy/activedisplay/ActiveDisplayView.java
# new file: packages/SystemUI/src/com/android/systemui/statusbar/policy/activedisplay/ClockView.java
# new file: packages/SystemUI/src/com/android/systemui/statusbar/policy/activedisplay/DummyActivity.java
# modified: services/java/com/android/server/NotificationManagerService.java
#
# Unmerged paths:
# (use "git add <file>..." to mark resolution)
#
# both modified: core/res/AndroidManifest.xml
# both modified: packages/SystemUI/AndroidManifest.xml
#
i'm assuming i have to type following commands:
git add core/res/AndroidManifest.xml
git add packages/SystemUI/AndroidManifest.xml
Here's what I get for one of the packages_apps_Settings cherry-pick:
Code:
[email protected]:~/psx-light/packages/apps/Settings$ git cherry-pick 0e508d62622c403ab99655a1eb7e14b3fcaa18d8
error: could not apply 0e508d6... Add active display to ChameleonOS [2/2]
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
Recorded preimage for 'res/values/arrays.xml'
Recorded preimage for 'res/values/strings.xml'
[email protected]:~/psx-light/packages/apps/Settings$ git status
# HEAD detached at 311aaf6
# You are currently cherry-picking.
# (fix conflicts and run "git commit")
#
# Changes to be committed:
#
# new file: res/xml/active_display_settings.xml
# new file: src/com/android/settings/chameleonos/ActiveDisplaySettings.java
#
# Unmerged paths:
# (use "git add/rm <file>..." as appropriate to mark resolution)
#
# both modified: res/values/arrays.xml
# both modified: res/values/strings.xml
# deleted by us: res/xml/system_settings.xml
#
Do I also need to "git add" both modified files as well as the one deleted (res/xml/system_settings.xml)?
orlzzt said:
Llloovvvee it!! Love it love it love it! Thanks! Check your Red Bull account!
Click to expand...
Click to collapse
Glad U liked it and THX !
Hi,
i'm testing my own KK ROM for a while now and i'm using AGNi PureStock kernel.
It's quite a nice combination but because i'm still using old bootloader on my device, i was annoyed by this offline charging bug.
You might have read about it or may have noticed it as well, if you use old bootloader and installed some of the KK stock ROM's.
Finally i did some research myself and thought about a permanent solution done at kernel level.
The idea was to hack the bootlader params given by old bootloader to match the requirements of the KK init and lpm binary.
Because it is done at very early stage, it is not required and not recommended to apply the JB patch for the battery driver anymore.
So as a prerequisite, please remove this part from samsung_battery.c if it still exists in your kernel:
Code:
/* For JB bootloader compatibility */
static int bootloader_get_lpm_state(char *str)
{
if (strncmp(str, "1", 1) == 0)
lpcharge = 1;
pr_info("%s: Low power charging mode: %d\n", __func__, lpcharge);
return lpcharge;
}
__setup("lpcharge=", bootloader_get_lpm_state);
Here's my patch...
Add this to the platform config file:
Code:
...
CONFIG_CMDLINE="console=ttySAC2,115200"
# CONFIG_CMDLINE_FROM_BOOTLOADER is not set
# CONFIG_CMDLINE_EXTEND is not set
# CONFIG_CMDLINE_FORCE is not set
[B]CONFIG_CMDLINE_FIXUP=y[/B]
...
Kconfig needs this modification,
/arch/arm/Kconfig:
Code:
config CMDLINE_FIXUP
bool "Append missing parameter to bootloader kernel arguments"
help
The missing parameter will be appended to the
command-line arguments provided by the boot loader.
The fix itself is located in the function parse_tag_cmdline,
/arch/arm/kernel/setup.c:
Code:
static int __init parse_tag_cmdline(const struct tag *tag)
{
#if defined(CONFIG_CMDLINE_EXTEND)
strlcat(default_command_line, " ", COMMAND_LINE_SIZE);
strlcat(default_command_line, tag->u.cmdline.cmdline, COMMAND_LINE_SIZE);
#elif defined(CONFIG_CMDLINE_FORCE)
pr_warning("Ignoring tag cmdline (using the default kernel command line)\n");
[B]#elif defined(CONFIG_CMDLINE_FIXUP)
strlcpy(default_command_line, tag->u.cmdline.cmdline, COMMAND_LINE_SIZE);
if (strstr(default_command_line, "lpcharge=1") != 0) {
strlcat(default_command_line, " ", COMMAND_LINE_SIZE);
strlcat(default_command_line, "androidboot.mode=charger", COMMAND_LINE_SIZE);
}[/B]
#else
strlcpy(default_command_line, tag->u.cmdline.cmdline, COMMAND_LINE_SIZE);
#endif
return 0;
}
As you see this it is quite simple and straight forward.
... but right now you'll need to compile your own kernel or ask the developers to integrate it for you.
It works very nice with my own test kernel compiled from AGNi pureSTOCK sources.
The patch will have no effect, if you're on new bootloader already... so it fits well
Though some kernel hardliner may not like it, because we touch general arch specific code...
Anyway, hope you like it and good luck for your kernel compilation!
Enjoy offline charging in the end :laugh:
P.S.: Some technical notes about the background:
http://forum.xda-developers.com/showpost.php?p=58760241&postcount=9
P.P.S.:
I may create a simple patch file as well... for now grab the txt file to copy'n'paste.
@psndna88 & @Hbohd:
This patch could be re-worked a little bit to be even more modular.
E.g. replace the fixed strings by user defined placeholders to be defined in the config file.
Some caution is required then of course...
Have fun!
scholbert
AOSP fix?
Hello,
I have been struggling with this bug on AOSP roms since I rooted my phone, will this fix work with Cyanogenmod roms?
Thanks,
Jortu
Hi Jortu!
Jortu said:
I have been struggling with this bug on AOSP roms since I rooted my phone, will this fix work with Cyanogenmod roms?
Click to expand...
Click to collapse
To be honest it is not that easy to answer this question in general, as there are several versions in use.
It depends on the proprietary files used for the specific CM version, if this patch would be helpful or not.
CM10.2 uses JB proprietary files:
system/bin/lpmkey
system/bin/playlpm
These binaries should match old bootloader (don't know about init binary used in initrd).
No issues here i guess... no patch required.
Though i never used this version and can't tell about the state.
As CM11 uses system/bin/lpm only, which seems to be the proprietary file from the stock KK,
it would require the new bootloader to work properly, from the first view.
It seems there'd been some confusion about the correct initialisation for offline charging and maybe it never got fixed. Don't know if it had ever been solved in the ramdisk somehow (changes in the init process or init binary itself).
This release might be still affected from the bug, if you're on old bootloader.
I once used a version of Omnirom (based on CM11) and if i remember correctly, there'd been no issues...
So if you like to check it out, apply the patch and build your own kernel and boot.img.
CM12 then switched to opensource healthd-charger.
So in fact this is the best solution and it should be independent from bootloaders.
To sum up... if CM11 is still affected by offline charging bug, the patch may help as well.
I hope this helps!
Cheers,
scholbert
Hi again,
for thoose who like to test...
I created my own kernel based on psndna88 source branch pureSTOCK-I9305-4.4.4:
- applied offline charging patch
- removed f2fs support in config
- support for FTDI USB serial adaptors
- cleaned/shrinked down initrd
See link to the attachment in my ROM thread below!
Clean and mean... works very nice
http://forum.xda-developers.com/attachment.php?attachmentid=3203351&d=1425985426
This is a test kernel to be considered as a proof of concept.
It may work on other stock based ROMs as well, as it is mainly based on psndna88 config for V55.
As i don't wanted to steal any of psndna88 great work i removed all init.d stuff and other things.
So my initrd is more back to stock in this case, some of the systems tweaks are in use though.
Please give huge thanks and credits to @psndna88 for his incredible hacking skills :good:
P.S.: I will immediately remove the zip file if it's violating any official rules or personal feelings :angel:
Have fun!
scholbert
scholbert said:
Hi again,
for thoose who like to test...
I created my own kernel based on psndna88 source branch pureSTOCK-I9305-4.4.4:
- applied offline charging patch
- removed f2fs support in config
- support for FTDI USB serial adaptors
- cleaned/shrinked down initrd
See link to the attachment in my ROM thread below!
Clean and mean... works very nice
http://forum.xda-developers.com/attachment.php?attachmentid=3203351&d=1425985426
This is a test kernel to be considered as a proof of concept.
It may work on other stock based ROMs as well, as it is mainly based on psndna88 config for V55.
As i don't wanted to steal any of psndna88 great work i removed all init.d stuff and other things.
So my initrd is more back to stock in this case, some of the systems tweaks are in use though.
Please give huge thanks and credits to @psndna88 for his incredible hacking skills :good:
P.S.: I will immediately remove the zip file if it's violating any official rules or personal feelings :angel:
Have fun!
scholbert
Click to expand...
Click to collapse
flashed.
seems it work fine on old bootloader.
thanks a lot for this kernel.
i'll test it for few days...if it will works well, can i add it to Amcha rom?
Hey LeoDeos,
thanks for appreciation.
Use this kernel for whatever you like, you're welcome
Though it was meant for testing, should be all o.k. with it.
If you need some more info, don't hesitate...
Cheers,
scholbert
scholbert said:
Hey LeoDeos,
thanks for appreciation.
Use this kernel for whatever you like, you're welcome
Though it was meant for testing, should be all o.k. with it.
If you need some more info, don't hesitate...
Cheers,
scholbert
Click to expand...
Click to collapse
after one day of use i found a little issue.
it doesnt run the scripts in init.d.
i changed the busybox in it and now is ok
Hi LeoDeos,
thanks for your feedback!
LeoDeos said:
after one day of use i found a little issue.
it doesnt run the scripts in init.d.
i changed the busybox in it and now is ok
Click to expand...
Click to collapse
I did not use the init.d feature yet, so this was untested.
Though busybox is the same used in psndna88 initrd, which is Stericsons BusyBox v1.23.0.
I guess for complete init.d support, it would be best to place all symbolic links to initrd busybox in /sbin as well.
Could you be more specific, which script refused to start or was it a general issue?
Which one do you use now?
Thanks again!
scholbert
scholbert said:
Hi LeoDeos,
thanks for your feedback!
I did not use the init.d feature yet, so this was untested.
Though busybox is the same used in psndna88 initrd, which is Stericsons BusyBox v1.23.0.
I guess for complete init.d support, it would be best to place all symbolic links to initrd busybox in /sbin as well.
Could you be more specific, which script refused to start or was it a general issue?
Which one do you use now?
Thanks again!
scholbert
Click to expand...
Click to collapse
Hi scholbert
the problem was with all scripts in init.d...it doesnt run anyone.
i always had problems with Stericsons BusyBox...in past i changed it in Amcha Rom (for example, doest works reboot command in shell) and changed also in Agni Kernel in Amcha Rom.
i use busybox 1.22.1 bionic.
Hi LeoDeos,
thanks for your immediate reply!
LeoDeos said:
Hi scholbert
the problem was with all scripts in init.d...it doesnt run anyone.
i always had problems with Stericsons BusyBox...in past i changed it in Amcha Rom (for example, doest works reboot command in shell) and changed also in Agni Kernel in Amcha Rom.
i use busybox 1.22.1 bionic.
Click to expand...
Click to collapse
AFAIK reboot command is not implemented in Stericsons BB.
I use the stock reboot binary in DLite ROM and it works as it should.
In the beginning there where some dead links created during install... but i fixed that in my ROM.
Sometimes things got lost while creating updater scripts
Anyway, luckily there are several choices and i know this bionic version of busybox as well.
Maybe i'll check it out.
Thought about creating my own BB as well :fingers-crossed:
BTW, thanks for your great work and helping people out in the Amcha thread!!
EDIT:
Just as a side-note...
Please be aware which version of bionic busybox you use, some are linked dynamically.
It could be dangerous to use dynamically linked binaries in initrd!
busybox-bionic: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped
This is linusyang version (standard libc):
busybox-linusyang: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
It got the reboot command implemented as well!
Cheers,
scholbert
@scholbert
Many thanks to you for fixing this issue. I have a couple of questions.
- I know you said it's the 4.4.4 version of AGNi, but is it the stock AGNi or one with modified sound?
- May I have your permission to use the zImage from your kernel to create multiple versions (No sound mod, Boeffla Mod, Wolfson Mod)
I've played around with AGNi myself a little bit too, enabling the insecure ADB and updating BusyBox, so I would be able to make this custom versions without a problem. These custom versions would be used for my ROM (TGP)
---------- Post added at 11:13 AM ---------- Previous post was at 10:47 AM ----------
UPDATE: Just done a test to put together my modded AGNi Kernels with the zImage from this kernel, and it worked.
So if I have permission I can include this in TGP where users will have the option to select either of the 3 variants of AGNi
scholbert said:
Hi LeoDeos,
thanks for your immediate reply!
AFAIK reboot command is not implemented in Stericsons BB.
I use the stock reboot binary in DLite ROM and it works as it should.
In the beginning there where some dead links created during install... but i fixed that in my ROM.
Sometimes things got lost while creating updater scripts
Anyway, luckily there are several choices and i know this bionic version of busybox as well.
Maybe i'll check it out.
Thought about creating my own BB as well :fingers-crossed:
BTW, thanks for your great work and helping people out in the Amcha thread!!
EDIT:
Just as a side-note...
Please be aware which version of bionic busybox you use, some are linked dynamically.
It could be dangerous to use dynamically linked binaries in initrd!
busybox-bionic: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped
This is linusyang version (standard libc):
busybox-linusyang: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
It got the reboot command implemented as well!
Cheers,
scholbert
Click to expand...
Click to collapse
thanks for this informations.
i never tried linus yang version...i'll try it and let you know
Hi guys!
To be honest, i did not expect this resonance for my custom kernel and it's an honour to help out if i can
djb77 said:
@scholbert
Many thanks to you for fixing this issue. I have a couple of questions.
- I know you said it's the 4.4.4 version of AGNi, but is it the stock AGNi or one with modified sound?
- May I have your permission to use the zImage from your kernel to create multiple versions (No sound mod, Boeffla Mod, Wolfson Mod)
I've played around with AGNi myself a little bit too, enabling the insecure ADB and updating BusyBox, so I would be able to make this custom versions without a problem. These custom versions would be used for my ROM (TGP)
---------- Post added at 11:13 AM ---------- Previous post was at 10:47 AM ----------
UPDATE: Just done a test to put together my modded AGNi Kernels with the zImage from this kernel, and it worked.
So if I have permission I can include this in TGP where users will have the option to select either of the 3 variants of AGNi
Click to expand...
Click to collapse
@djb77:
Sure you can use it, but take the modules from /lib/modules as well as they should match the kernel.
So maybe i'm repeating, but give some credits to psndna88 again, because i really think he has build up an excellent kernel code base, which is in good shape.
I reviewed many parts of code in the meantime and i really like that he pushed it up to final release which is 3.0.101 :good:
LeoDeos said:
thanks for this informations.
i never tried linus yang version...i'll try it and let you know
Click to expand...
Click to collapse
@LeoDeos:
You're welcome!
I once used linus yang's BB back in these days, when i pimped up my xperia, and never got trouble.
There's also a version with all symlinks included... might be useful as well :highfive:
Have a nice day!
scholbert
scholbert said:
Hi guys!
To be honest, i did not expect this resonance for my custom kernel and it's an honour to help out if i can
@djb77:
Sure you can use it, but take the modules from /lib/modules as well as they should match the kernel.
So maybe i'm repeating, but give some credits to psndna88 again, because i really think he has build up an excellent kernel code base, which is in good shape.
I reviewed many parts of code in the meantime and i really like that he pushed it up to final release which is 3.0.101 :good:
@LeoDeos:
You're welcome!
I once used linus yang's BB back in these days, when i pimped up my xperia, and never got trouble.
There's also a version with all symlinks included... might be useful as well :highfive:
Have a nice day!
scholbert
Click to expand...
Click to collapse
flashed just now your kernel with linus yang busybox and seems it works well, at least as regard to the run of the scripts in init.d
about your wonderment, i have to say that this kernel is usefull for me that i have old bootloader...
and dont know if is a placebo, but it seems more battery friendly than agni...with pegasusq governor
scholbert said:
@djb77:
Sure you can use it, but take the modules from /lib/modules as well as they should match the kernel.
So maybe i'm repeating, but give some credits to psndna88 again, because i really think he has build up an excellent kernel code base, which is in good shape.
I reviewed many parts of code in the meantime and i really like that he pushed it up to final release which is 3.0.101 :good:
Click to expand...
Click to collapse
I was more thinking about mainly crediting psndna88 for the kernel (as from what I read it's pretty much the AGNi Kernel modified), and give you credit for the mods you've done.
The tests went well on my I9305 with a new bootloader, I'll have to give my 2nd I9305 with the old bootloader a test soon
Hi!
LeoDeos said:
flashed just now your kernel with linus yang busybox and seems it works well, at least as regard to the run of the scripts in init.d
about your wonderment, i have to say that this kernel is usefull for me that i have old bootloader...
and dont know if is a placebo, but it seems more battery friendly than agni...with pegasusq governor
Click to expand...
Click to collapse
Nice that it works now... guess i'll switch to this BB too. Thanks for reporting!
As for the battery friendlyness, guess it's placebo.
Did not realize any significant change.
I used an older toolchain to compile though.
BTW, i realized no negative effect on performance here (Seems even to perform a little better, if you refer to AnTuTu, which is sometimes little missleading)
djb77 said:
I was more thinking about mainly crediting psndna88 for the kernel (as from what I read it's pretty much the AGNi Kernel modified), and give you credit for the mods you've done.
The tests went well on my I9305 with a new bootloader, I'll have to give my 2nd I9305 with the old bootloader a test soon
Click to expand...
Click to collapse
Yeah sure, this was my intent at this point
To refer to your tests... nice that we got a confirmation for new bootloader!
Did you realize my tiny tweaks in initrd concerning KNOX, should have effect if someone aims to use crypto features i guess.
AFAIK using KNOX features on custom ROMs is impossible though
Thanks again for your comments and happy hacking!
scholbert
scholbert said:
Hi!
Nice that it works now... guess i'll switch to this BB too. Thanks for reporting!
As for the battery friendlyness, guess it's placebo.
Did not realize any significant change.
I used an older toolchain to compile though.
BTW, i realized no negative effect on performance here (Seems even to perform a little better, if you refer to AnTuTu, which is sometimes little missleading)
Yeah sure, this was my intent at this point
To refer to your tests... nice that we got a confirmation for new bootloader!
Did you realize my tiny tweaks in initrd concerning KNOX, should have effect if someone aims to use crypto features i guess.
AFAIK using KNOX features on custom ROMs is impossible though
Thanks again for your comments and happy hacking!
scholbert
Click to expand...
Click to collapse
All I basically did was decompile your version with Android Image Kitchen, and grabbed all the files in the split_files folder. Once I had them, I just decompiled the original versions of AGNi and used it's ramdisk along with the other split_files.
All I can say is the phone boots, it doesn't seem laggy as such, but real extensive testing.
I'm experiencing an issue (not specific to this kernel) where my I9305 runs out of vmalloc space due to the old bootloader passing "vmalloc=144m" (new one would do "vmalloc=176m", but I would rather not install it - besides, it's just 32M extra, so just as likely to fill up), resulting in a never-ending stream of FCs. Would it be possible to make a kernel that overrides the vmalloc parameter in a similar way?
EDIT: The I9300 (with just 1GB RAM) also uses vmalloc=144m, so it's obviously undersized; other 2GB RAM devices tend to have vmalloc spaces around 400M (there is even a kernel for the S5 that bumps vmalloc to 512M from the original 400M). I would say let's get brave and replace vmalloc=144m (or vmalloc=176m if present) with vmalloc=400m (512m is probably an overkill for a 720p device).
EDIT 2: Here is a modded AGNi kernel with that fix (as well as the LPM fix): https://mega.co.nz/#!zYp0XS7D!6ZimeSRCnczqArRBtZwAdqHT01Y832ZtPfaopSHDfuA
BUG in this kernel: phone locks up trying to play video. I'm investigating it. Fixed version uploaded.
This is just AGNi I9305-4.4.4 compiled from Github using Linaro 2015-03, with this patch:
Code:
[PATCH] Implement scholbert's offline charging fix and add vmalloc fix
Signed-off-by: Gábor Stefanik <[email protected]>
---
arch/arm/Kconfig | 12 ++++++++++
arch/arm/configs/psn_i9305_new_defconfig | 1 +
arch/arm/configs/psn_i9305_new_wolf_defconfig | 1 +
arch/arm/kernel/setup.c | 29 +++++++++++++++++++++++++
4 files changed, 43 insertions(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 1dc4875..e0c2854 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -1901,6 +1901,18 @@ config CMDLINE_FORCE
command-line options your boot loader passes to the kernel.
endchoice
+config CMDLINE_FIXUP
+bool "Correct broken Samsung bootloader kernel arguments"
+depends on CMDLINE_FROM_BOOTLOADER || CMDLINE_EXTEND
+help
+ Some Samsung smartphone bootloaders send invalid kernel command
+ strings. This can cause failure to detect that the device is in
+ charging mode, or insufficient vmalloc space; leading to OOM
+ errors and potentially preventing boot.
+
+ Say Y here if you have a broken bootloader and experience any of
+ these symptoms.
+
config XIP_KERNEL
bool "Kernel Execute-In-Place from ROM"
depends on !ZBOOT_ROM
diff --git a/arch/arm/configs/psn_i9305_new_defconfig b/arch/arm/configs/psn_i9305_new_defconfig
index 2a6c88a..6036bf2 100644
--- a/arch/arm/configs/psn_i9305_new_defconfig
+++ b/arch/arm/configs/psn_i9305_new_defconfig
@@ -784,6 +784,7 @@ CONFIG_CMDLINE="console=ttySAC2,115200"
CONFIG_CMDLINE_FROM_BOOTLOADER=y
# CONFIG_CMDLINE_EXTEND is not set
# CONFIG_CMDLINE_FORCE is not set
+CONFIG_CMDLINE_FIXUP=y
# CONFIG_XIP_KERNEL is not set
CONFIG_KEXEC=y
CONFIG_ATAGS_PROC=y
diff --git a/arch/arm/configs/psn_i9305_new_wolf_defconfig b/arch/arm/configs/psn_i9305_new_wolf_defconfig
index 05d5cb8..2f1dada 100644
--- a/arch/arm/configs/psn_i9305_new_wolf_defconfig
+++ b/arch/arm/configs/psn_i9305_new_wolf_defconfig
@@ -784,6 +784,7 @@ CONFIG_CMDLINE="console=ttySAC2,115200"
CONFIG_CMDLINE_FROM_BOOTLOADER=y
# CONFIG_CMDLINE_EXTEND is not set
# CONFIG_CMDLINE_FORCE is not set
+CONFIG_CMDLINE_FIXUP=y
# CONFIG_XIP_KERNEL is not set
CONFIG_KEXEC=y
CONFIG_ATAGS_PROC=y
diff --git a/arch/arm/kernel/setup.c b/arch/arm/kernel/setup.c
index a9ead89..111b78b 100644
--- a/arch/arm/kernel/setup.c
+++ b/arch/arm/kernel/setup.c
@@ -671,6 +671,9 @@ __tagtable(ATAG_REVISION, parse_tag_revision);
static int __init parse_tag_cmdline(const struct tag *tag)
{
+#if defined(CONFIG_CMDLINE_FIXUP)
+size_t cmdline_len = strlen(default_command_line);
+#endif
#if defined(CONFIG_CMDLINE_EXTEND)
strlcat(default_command_line, " ", COMMAND_LINE_SIZE);
strlcat(default_command_line, tag->u.cmdline.cmdline,
@@ -680,6 +683,32 @@ static int __init parse_tag_cmdline(const struct tag *tag)
#else
strlcpy(default_command_line, tag->u.cmdline.cmdline,
COMMAND_LINE_SIZE);
+#if defined(CONFIG_CMDLINE_FIXUP)
+cmdline_len = 0;
+#endif
+#endif
+#if defined(CONFIG_CMDLINE_FIXUP)
+/*
+ * check for the proprietary parameter "lpcharge=1 and add the corresponding
+ * standard parameter "androidboot.mode=charger"
+ */
+if (strstr(default_command_line + cmdline_len, "lpcharge=1")) {
+strlcat(default_command_line, " ", COMMAND_LINE_SIZE);
+strlcat(default_command_line, "androidboot.mode=charger",
+COMMAND_LINE_SIZE);
+}
+
+/* increase vmalloc space from 144m or 176m to 224m */
+char *vma_param = strstr(default_command_line + cmdline_len, "vmalloc=144m");
+if (!vma_param) {
+vma_param = strstr(default_command_line + cmdline_len, "vmalloc=176m");
+}
+
+if (vma_param) {
+vma_param[8] = '2';
+vma_param[9] = '2';
+vma_param[10] = '4';
+}
#endif
return 0;
}
Full source available @ https://github.com/gstefanik/AGNI-pureSTOCK
nice work. Does he work with a 5.1 AICP ROM ?
And witch tool I need to fix my offline charging plz ?
can you tell me how to remove Offline charging. I am using a chinese device. No source code. But I have experience with boot.img unpack repack