Ccurrently trying to get the SkyGO app working on the HD2.
One of the devs has suggested that for the app to work properly we need a Kernel with "ro.secure=1" set in it.
Currently I am bouncing between Typhoon 3.7.6 (which uses tytung's r14 kernel) and NexusHD2-ICS-4.0.3 (tytungs ICSr1 Kernel I believe)
Can anyone tell me how to find out if the kernel has this parameter set. If not how easy would it be for me to add it and recompile the kernel (pointers to kernel de/recompilation threads appreciated!
I'm not to worried about doing it myself if I have to.
TIA
mods - if this is in the wrong forum I apologise in advance, could you move it for me if it is
bobjbain said:
Ccurrently trying to get the SkyGO app working on the HD2.
One of the devs has suggested that for the app to work properly we need a Kernel with "ro.secure=1" set in it.
Currently I am bouncing between Typhoon 3.7.6 (which uses tytung's r14 kernel) and NexusHD2-ICS-4.0.3 (tytungs ICSr1 Kernel I believe)
Can anyone tell me how to find out if the kernel has this parameter set. If not how easy would it be for me to add it and recompile the kernel (pointers to kernel de/recompilation threads appreciated!
I'm not to worried about doing it myself if I have to.
TIA
mods - if this is in the wrong forum I apologise in advance, could you move it for me if it is
Click to expand...
Click to collapse
This is a question. [Q&A]
yz.hd said:
This is a question. [Q&A]
Click to expand...
Click to collapse
Thanks for the useful and insightful response
FYI - I realised that it might be after I submitted it! Which is why I caveated the post at the end.
this parameter is in the initrd.gz in the kernel in the boot folder of the ROM.
You should extract it and inside there is a file called default.prop
extract
mkdir initdir
cd initdir
zcat ../initrd.gz | cpio -i -d
compress
cd initdir
find . | cpio -o -H newc | gzip -9 > ../initrd.gz
Each line in the file default.prop is an attribute assignment. There we need to
Note the two properties: ro.secure, and ro.debuggable. . If ro.secure = 0 is allowed us to run the adb root command.
Usually we put the core ROOT refers to the ro.secure = 0. ROOT permission to refer to the general said on the phone
A license management program (Superuser.apk) procedures for the root user can grant permission.
bobjbain said:
Ccurrently trying to get the SkyGO app working on the HD2.
One of the devs has suggested that for the app to work properly we need a Kernel with "ro.secure=1" set in it.
Currently I am bouncing between Typhoon 3.7.6 (which uses tytung's r14 kernel) and NexusHD2-ICS-4.0.3 (tytungs ICSr1 Kernel I believe)
Can anyone tell me how to find out if the kernel has this parameter set. If not how easy would it be for me to add it and recompile the kernel (pointers to kernel de/recompilation threads appreciated!
I'm not to worried about doing it myself if I have to.
TIA
mods - if this is in the wrong forum I apologise in advance, could you move it for me if it is
Click to expand...
Click to collapse
look here this great kernel should have ro.secure set to 1
Bologna said:
look here this great kernel should have ro.secure set to 1
Click to expand...
Click to collapse
it doesn't, it's based on Tytung's Kernel, Tytung's doesn't so I'm not suprised that dorimnax's "greatest ever" (sic) doesn't teither
big thanks to magnus48, have decompressed the kernel, changed ro.secure to 1, recompressed, copied to /boot
Phone booted (which suprised me) and my SkyGo App now works.
Yay
magnus48 said:
The easy way is use root explorer and edit /default.prop on your device but is not free.
ro. means read only you can't change it's value after rom is loaded
Click to expand...
Click to collapse
So, I can either change the value in my kernel OR I can edit default.prop and reboot??
Won't the values in default.prop get overwritten on boot??
bobjbain said:
it doesn't, it's based on Tytung's Kernel, Tytung's doesn't so I'm not suprised that dorimnax's "greatest ever" (sic) doesn't teither
Click to expand...
Click to collapse
First question : Why of this sarcastic reply?
Second question : Can you please share your skygo working app, telling us what's the kernel you're using to have it working?
Thanks in advance
bobjbain said:
So, I can either change the value in my kernel OR I can edit default.prop and reboot??
Won't the values in default.prop get overwritten on boot??
Click to expand...
Click to collapse
forget this way. It did not work when rebooting the kernel overwrites the deafult.prop file.
The change should be done inside initrd.gz
magnus48 said:
forget this way. It did not work when rebooting the kernel overwrites the deafult.prop file.
The shange should be done inside initrd.gz
Click to expand...
Click to collapse
You should be able to pull it, make changes and push it back to phone via adb. Useful if you don't want to reflash
Sent from my HD2 using XDA
jwchips said:
You should be able to pull it, make changes and push it back to phone via adb. Useful if you don't want to reflash
Sent from my HD2 using XDA
Click to expand...
Click to collapse
default.prop is in the initrd.gz, this is extracted when the phone boots, so any changes you make to default.prop WILL be overwritten when the phone boots.
You have to make the changes inside the initrd.gz file.
Bologna said:
First question : Why of this sarcastic reply?
Click to expand...
Click to collapse
I don't quite hold dorimanx in quite the high esteem that others do, his work is good but it can be rushed as shown by his 5.x series of Kernels.
Bologna said:
Second question : Can you please share your skygo working app, telling us what's the kernel you're using to have it working?
Thanks in advance
Click to expand...
Click to collapse
Here although this is an app for UK Sky only and won't work for non-UK subscribers.
bobjbain said:
default.prop is in the initrd.gz, this is extracted when the phone boots, so any changes you make to default.prop WILL be overwritten when the phone boots.
You have to make the changes inside the initrd.gz file.
Click to expand...
Click to collapse
Any chance you could post the modified kernel? I am running R14 on GB3.2a so it would drop right in
CR5N said:
Any chance you could post the modified kernel? I am running R14 on GB3.2a so it would drop right in
Click to expand...
Click to collapse
yertiz.
Take a backup of your current initrd.gz first though to be on the safe side.
bobjbain said:
yertiz.
Take a backup of your current initrd.gz first though to be on the safe side.
Click to expand...
Click to collapse
Thankyou. This works on Tytung GB3.2a. F1 channel now working on this old HD2
What about SD builds?
magnus48 said:
forget this way. It did not work when rebooting the kernel overwrites the deafult.prop file.
The change should be done inside initrd.gz
Click to expand...
Click to collapse
I can access and edit default.prop on my SD build after the phone has booted. This seems to give me access to Sky News at least. But I still can't get premium channels. Do you think I still need to edit initrd.gz as well or is that now redundant?
johnkst said:
I can access and edit default.prop on my SD build after the phone has booted. This seems to give me access to Sky News at least. But I still can't get premium channels. Do you think I still need to edit initrd.gz as well or is that now redundant?
Click to expand...
Click to collapse
No, you will need to edit your initrd.gz
Before I did I could access Sky News only, afterwards the Sky world was my Oyster!!
bobjbain said:
No, you will need to edit your initrd.gz
Before I did I could access Sky News only, afterwards the Sky world was my Oyster!!
Click to expand...
Click to collapse
Thanks Bob. Is there anything else I should edit while I'm at it?
Currently after booting, my default.prop contains the following attributes:
ro.secure=0 (need to change this to 1)
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
I'm particularly suspicious of the last one!
Also... what should I use to edit default.prop within initrd.gz? I tried unzipping it with 7zip, editing the initrd file with a hex editor and re-zipping but it created a significantly smaller file...
johnkst said:
Thanks Bob. Is there anything else I should edit while I'm at it?
Currently after booting, my default.prop contains the following attributes:
ro.secure=0 (need to change this to 1)
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
I'm particularly suspicious of the last one!
Also... what should I use to edit default.prop within initrd.gz? I tried unzipping it with 7zip, editing the initrd file with a hex editor and re-zipping but it created a significantly smaller file...
Click to expand...
Click to collapse
I only ever changed ro.secure, don't have the phone any more so can't check the other values.
To edit the default.prop you need to uncompress the initrd.gz then recompress it using the following linux commands
Code:
extract
mkdir initdir
cd initdir
zcat ../initrd.gz | cpio -i -d
compress
cd initdir
find . | cpio -o -H newc | gzip -9 > ../initrd.gz
As I run windows I downloaded and installed cygwin and used that to uncompress and recompress the kernel.
I edited the default.prop in windows but you can use vi within cygwin if you want.
If you're uncomfortable doing this then attach your kernel to a post and I can do it for you.
Related
the title says it
after many requests here is the guide
most of this is spread around the vogue
forum here and there, i just wanted to bring it all together
goal-seeing lately we have lost some good developers, this is a shot at getting more involvement in vogue/android development
I.SETTING UP YOUR SYSTEM
1. GETTING LINUX you will need to have Linux installed on your computer(dual-boot, vm, whatever). i recommend Ubuntu karmic (9.10) because its pretty new-user friendly. It can be found at http://www.ubuntu.com/
for you windows lovers here is a guide to setting up a ubuntu VM(virtual machine (if you really didnt know ))
2. THINGS/TOOLS YOU WILL NEED download these:
original 8/8/09 ion 1.5 build HERE(we are gonna use the bin-files and the apns-conf.xml, and a few apps)
the latest rootfs.img (find it)
these android tools (included are genext2fs (android version), split_bootimg.pl, and extract_ramdisk.sh)
after downloading, extract the zip to a folder. open a terminal and cd to the dir of the tools. click applications>accesories>terminal and type:
Code:
cd ~/whatever/
sudo rm -rf /bin/genext2fs
#dont type whats after the pound signs
#type in your password
#if you havent set up a su password yet type:
sudo passwd
#then make one, next
sudo cp -r ./whatever/genext2fs /bin/
squashfs-tools (if you have ubuntu 9.10-karmic first you will have to uninstall squashfs-tools 4.0(4.0 WILL NOT NOT NOT NOT NOT WORK) that is installed during the installation of linux ): go to system>administration>synaptic package manager. type squashfs-tools in the quick search, then right click and click mark for complete removal. then hit apply. then download and install this here http://http://ftp.us.debian.org/debian/pool/main/s/squashfs/squashfs-tools_3.3-7_i386.deb
i also strongly recommend downloading the sdk-tools v1.1(adb is almost essential when porting, for debugging purposes) enatefox has it posted on his media fire. (search for it)
3. ORGANIZATION
now that we have what we need. lets get organized.
a.mount points
we are going to use mount points while porting.
terminal:
Code:
sudo mkdir /mnt/rootfs
sudo mkdir /mnt/system
#i also have one for mounting data files
mkdir /mnt/data
b. directories
terminal:
Code:
mkdir ~/Desktop/android
mkdir ~/Desktop/android/ion
mkdir ~/Desktop/android/donut
#you get the point...
now put the ion 8/8/09 build in the ~/Desktop/android/ion folder and rename it system.sqsh then
terminal:
Code:
cd ~/Desktop/android/ion
unsquashfs ./system.sqsh
you should now have a folder called squashfs-root in the ion directory. it contains all the guts from the ion build. feel free to look around in that folder as you should get familiar with the folders and things in there
II PORTING
1. PORTING A HERO ROM(this was in zens how-to-make-a-hero-rom.txt im just adding on to it)
a. Download a rom from the dream/sapphire development forums.
b. Extract what you downloaded to ~/Desktop/android/hero. It is usually an update.zip.
c. Open the extracted folder. Inside you should see a data directory and a system directory.
d. Open the data directory and look for an app or app_s folder.
e. Open those folders and copy the apks to the system/app/ folder. Leave out what you don't need. feel free to add any custom apps. as long as they are from the same sdk number. ie 1.5, 1.6, 2.0.1, 2.1 most are pretty cross-compatible though.
f. Delete system/xbin from the rom your porting and replace it with the one from Ion.
g. Copy ~/Desktop/android/ion/squashfs-root/etc/apns-conf.xml from Ion to ~/Desktop/android/hero/system/etc/
h. Mount the latest rootfs.img
terminal:
Code:
sudo mount ~/whereever/rootfs.img -o loop /mnt/rootfs
i. Copy libaudio.so libaudioflinger.so libcameraservice.so libgps.so from /lib in the mounted rootfs over to system/lib in the rom you are porting*(donut and eclair really dont need this step because those files are in most of the latest rootfs.img's but be sure to check)
j. Edit the system/build.prop or even use the Ion build.prop.*(for donut/eclair you may want to edit the lcd density to 120 or 110 in the build.prop for qvga and 160 for 320x480)
k. Create a blank file in system/ called hero.build*(for eclair/donut create donut.build or eclair.build or eclairhero.build.....etc)
*l. for hero any systems too big to run on nand, here is a script to make a data file. put this in the ~/Desktop/android/hero directory. cut the app folder from ~/Desktop/android/hero/system and paste it to ~/Desktop/android/hero , and rename it too app_s . next run the mkdataimg.sh it should ask for you password in a terminal. type it in and then it should mount the data.img to data-mnt folder in ~/Desktop/android/hero . keep that terminal open copy the app_s folder in to data-mnt. then type y in the terminal to unmount the data.img. next:
terminal:
Code:
cd ~/Desktop/android/hero
ln -s /data/app_s ./system/app
that should make a broken symlink in system
2. Mount it and squash it
ok now that we are done porting lets put it together
terminal:
Code:
cd ~/Desktop/android/hero
genext2fs -d ./system -b 180000 -a system.ext2
sudo mount -o loop ./system.ext2 /mnt/system
sudo mksquashfs /mnt/system system.sqsh
sudo chown $USER ./system.sqsh
#and if you want
rm -rf ./system.ext2
from zenulator:
There are other little tweaks here and there but thats basically it. Now you can roll your own.
Click to expand...
Click to collapse
im gonna clean this up a bit later just wanted to get this out to you guys
nice thanks jamezelle
zen's manup456-based Eclair build contains different libaudio.so & libaudioflinger.so than the rootfs, and Eclair wouldn't boot if I replaced them with the libs from the rootfs. This might be due to the rootfs libs not being updated for Eclair yet (also why voice search/dial doesn't work) but I'm not sure. I don't know if this will be the case for 2.1, just wanted to add that in.
I really appreciate the guide and look forward to hearing more. I've learned a lot from zen as well but a lot of the work the devs do is so hard to follow because it's undocumented.
Do you know why the xbin has to be from Ion? Is it because of our kernel version or the squashfs ver that our kernel contains? I've been wanting to grab some of the tools from the xbin of other builds but have been unsure about compatibility.
Also, for more advanced Android ROM building, I'd like to add a link to zipalign optimization.
polyrhythmic said:
zen's manup456-based Eclair build contains different libaudio.so & libaudioflinger.so than the rootfs, and Eclair wouldn't boot if I replaced them with the libs from the rootfs. This might be due to the rootfs libs not being updated for Eclair yet (also why voice search/dial doesn't work) but I'm not sure. I don't know if this will be the case for 2.1, just wanted to add that in.
I really appreciate the guide and look forward to hearing more. I've learned a lot from zen as well but a lot of the work the devs do is so hard to follow because it's undocumented.
Do you know why the xbin has to be from Ion? Is it because of our kernel version or the squashfs ver that our kernel contains? I've been wanting to grab some of the tools from the xbin of other builds but have been unsure about compatibility.
Also, for more advanced Android ROM building, I'd like to add a link to zipalign optimization.
Click to expand...
Click to collapse
we need to move back to a more standardized comunity rootfs.img. i'm seeing more and more different rootfs.imgs that vary little by little. it is kind of hard to really document all of the development. but i see your point. the xbin(are just eXtended bin files) doesnt have to come from ion. the xbin in ion is actually empty
yes our kernel doesnt support LZMA compression which is what 4.0 uses. more info on it here http://www.squashfs-lzma.org/ i dont know why out kernel has not been updated to support it(you would have to ask DZO), i just know is isnt supported
thanks for the link to zipalign. i usually zipalign my apps. btw most dream and sapphire devs are already zipaligning there apks so we dont have to
I agree, I don't like forking the rootfs but the latest ones don't contain the correct WiFi files & settings for Kaiser. I know our kernel is way behind, I've asked several questions in the kernel thread about it but then the thread goes OT and I've never gotten an answer to most of the questions. Newbie16 has been compiling kernels but we've had trouble finding all the updated source files.
Oh, the PNG optimization in the zipalign thread is useful also, I easily saved 5 MB in the Eclair build.
The 8/8 file is a .img file, not .sqsh. Terminal tells me it can't find a sqash superblock on the file, or something to that extent.
EDIT: also missing a step that seems crucial... re squashing the files to make a .sqsh file to use?
ln -s help. hero nand porting
When ever I'm trying to port a hero build to nand ln -s gives me "operation not permitted" during boot. I used -a during genext2fs. Also data didn't work, even though I have the right apns-conif.xml. any idea? I was trying to port hero revolution (I think thats it ). Thanx
TheKartus said:
The 8/8 file is a .img file, not .sqsh. Terminal tells me it can't find a sqash superblock on the file, or something to that extent.
EDIT: also missing a step that seems crucial... re squashing the files to make a .sqsh file to use?
Click to expand...
Click to collapse
i fixed(add the missing steps) it but i dont have a copy of 8/8 ion personally. any ion system.sqsh build will work. if anyone has one please post it!
TheKartus said:
The 8/8 file is a .img file, not .sqsh. Terminal tells me it can't find a sqash superblock on the file, or something to that extent.
EDIT: also missing a step that seems crucial... re squashing the files to make a .sqsh file to use?
Click to expand...
Click to collapse
jamezelle said:
i fixed(add the missing steps) it but i dont have a copy of 8/8 ion personally. any ion system.sqsh build will work. if anyone has one please post it!
Click to expand...
Click to collapse
i just mounted the system.img and copied all the files to a new folder....that way then u dont have to mount the system.img everytime u are porting a rom
my steps to do that
[email protected]:~# cd Android
[email protected]:~/Android# dir
hi Inferno sensehero13 SenseHERO-v1.4_NoTheme senshero
signed-Hero_Inferno_Final signed-Hero_Inferno_Final.zip
system-2009-08-08.img system-sensehero-20091009.sqsh
TOOLS
ZipAlign.sh
[email protected]:~/Android# mkdir ion
[email protected]:~/Android# mount -o loop system-2009-08-08.img ion
[email protected]:~/Android#
Could someone please define...
Could someone please define rootfs, zIMage and the other parts that go into an Android build? If you're going from say, donut, to eclair, which ones can you reuse? I think I understand that the system.sqsh is what makes a build donut or eclair and actually is the file that has the customizations in it. But, what do the other parts do? If this is the wrong place to post this, mods, please move this. Thanks.
Sally
Hey guys, don't know if anyone else is having this issue or not.
I'm trying to work with the Topaz kernals...I downloaded the XDAndroid 2.1 system.sqsh and was able to unsquashfs it fine on my Vector Linux box...but I want to do the same to the TopazKernal16 system.sqsh (donut) but when I run unsquashfs it makes it to about 70% (highest I got to was 80% on one try) and then stops saying "killed".
any way to remedy this? also, what is the simplest way to "re"squash it?
Thanks!
iceman198 said:
Hey guys, don't know if anyone else is having this issue or not.
I'm trying to work with the Topaz kernals...I downloaded the XDAndroid 2.1 system.sqsh and was able to unsquashfs it fine on my Vector Linux box...but I want to do the same to the TopazKernal16 system.sqsh (donut) but when I run unsquashfs it makes it to about 70% (highest I got to was 80% on one try) and then stops saying "killed".
any way to remedy this? also, what is the simplest way to "re"squash it?
Thanks!
Click to expand...
Click to collapse
You just posted in the wrong forum altogether. This section is for the Vogue, not for the Topaz. Try to ask there on in one of the xdandroid threads. This project is different from xdandroid. Thanks.
egzthunder1 said:
You just posted in the wrong forum altogether. This section is for the Vogue, not for the Topaz. Try to ask there on in one of the xdandroid threads. This project is different from xdandroid. Thanks.
Click to expand...
Click to collapse
Sorry, thanks...
iceman198 said:
Sorry, thanks...
Click to expand...
Click to collapse
No prob
I would be interested in the Android's filesystem breakdown. Just some guide on what exactly is in the system, and then rootfs.img and then the modules. If someone could point me in the right direction, that would be much appreciated!
Thanks!
iceman198 said:
I would be interested in the Android's filesystem breakdown. Just some guide on what exactly is in the system, and then rootfs.img and then the modules. If someone could point me in the right direction, that would be much appreciated!
Thanks!
Click to expand...
Click to collapse
pm dzo, he will probably be able to help you there.
egzthunder1 said:
pm dzo, he will probably be able to help you there.
Click to expand...
Click to collapse
Thanks egzthunder1!
iceman198 said:
Thanks egzthunder1!
Click to expand...
Click to collapse
Not a problem. Good luck!
Kernel version: 2.6.32.9 [email protected] #1
Base: Cotulla's Source Tree w/ latest drivers enhancements
Instruction:
- Delete zImage
- Unpack/replace my files in your sd
Please refer to this kernel as "michyprima's build" for not making people confused.
Ram Patch from Manus Freedom (http://git.linuxtogo.org/?p=groups/...it;h=65276d5b73d2de9e446cc379c76f03c7e4f8f914)
File up!
I'd appreciate a thanks
EDIT: This is an experimental build. Something maybe will not work for you, or worse this kernel will not be stable on your device. For daily use use a kernel from cotulla's tree
michyprima said:
Kernel version: 2.6.32.9 [email protected] #1
Base: Cotulla's Source Tree w/ latest drivers enhancements
Instruction:
- Delete zImage
- Unpack/replace my files in your sd
Please refer to this kernel as "michyprima's build" for not making people confused.
File up!
I'd appreciate a thanks
Click to expand...
Click to collapse
nevermind ;D
Great, but you forgot to add the modules. I'm not able to enable Wifi.
michyprima said:
Kernel version: 2.6.32.9 [email protected] #1
Base: Cotulla's Source Tree w/ latest drivers enhancements
Instruction:
- Delete zImage
- Unpack/replace my files in your sd
Please refer to this kernel as "michyprima's build" for not making people confused.
File up!
I'd appreciate a thanks
Click to expand...
Click to collapse
wifi is working?
Well, compiled it myself.
It belongs into: /system/lib/modules
Thanks for your kernel. The 384mb patch from manusfreedom works great!
is 384mb max right now? or is there a way to bump it further to 512mb using the same method to bump it to 384mb?
is this only for ubuntu.or i can us for android,too.
ElBartoME said:
Well, compiled it myself.
It belongs into: /system/lib/modules
Thanks for your kernel. The 384mb patch from manusfreedom works great!
Click to expand...
Click to collapse
Thanks for remembering me to give credit...
Wrote the post too fast
ElBartoME said:
Well, compiled it myself.
It belongs into: /system/lib/modules
Thanks for your kernel. The 384mb patch from manusfreedom works great!
Click to expand...
Click to collapse
Great work Michiprama.
By the way how to push this ko file to /system/libs/modules?
If you can tell me a way using the Terminal emulator in the device it would be great.
Thanks
arifqur said:
Great work Michiprama.
By the way how to push this ko file to /system/libs/modules?
If you can tell me a way using the Terminal emulator in the device it would be great.
Thanks
Click to expand...
Click to collapse
Isn't it better to change the file directly in android file system?
On Debian distribution...
Code:
sudo su
mount system.ext2 /MountPoint1 -o loop
rm /MountPoint1/lib/modules/bcm4329.ko
cp bcm4329.ko /MountPoint1/lib/modules
umount /MountPoint1
exit
Otherwise if you have write access directly on the phone you can do the same here.
thx Micy for Kernel
an thx ElBartoME for fix
adb shell mount -o remount,rw /system
adb push "your Path" /system/lib/modules/bcm4329.ko
edit
anyway had sleep of death!! always! for me at least
michyprima said:
Isn't it better to change the file directly in android file system?
On Debian distribution...
Code:
sudo su
mount system.ext2 /MountPoint1 -o loop
rm /MountPoint1/lib/modules/bcm4329.ko
cp bcm4329.ko /MountPoint1/lib/modules
umount /MountPoint1
exit
Otherwise if you have write access directly on the phone you can do the same here.
Click to expand...
Click to collapse
Thanks man
I keep getting errors trying to unpack the .rar file in various ways. Anyone else? Is it corrupted?
michyprima said:
Isn't it better to change the file directly in android file system?
On Debian distribution...
Code:
sudo su
mount system.ext2 /MountPoint1 -o loop
rm /MountPoint1/lib/modules/bcm4329.ko
cp bcm4329.ko /MountPoint1/lib/modules
umount /MountPoint1
exit
Otherwise if you have write access directly on the phone you can do the same here.
Click to expand...
Click to collapse
Can you tell me how to do this for shubCRAFT's build? =)
I got the ram working but I can't overwrite the bcm4329.ko file in module.
3G aint working, wont connect but says connected
RaiderX303 said:
3G aint working, wont connect but says connected
Click to expand...
Click to collapse
Yes, can confirm, no mobile connection possible
Wlan was working fine with the fix, also no SOD within first hour.
tried it, the ram worked but the Wifi didn't work and it gave me SOD
using TMOUS
Downy said:
Yes, can confirm, no mobile connection possible
Wlan was working fine with the fix, also no SOD within first hour.
Click to expand...
Click to collapse
Yes, i confirm this too: Wlan is working with the patch, but mobile connection doesn't works.
Sent from my HTC Desire using XDA App
Well our leo is not ready for more ram right now
Adding on first post an "experimental" warning...
michyprima said:
Well our leo is not ready for more ram right now
Adding on first post an "experimental" warning...
Click to expand...
Click to collapse
unfortunately yes......
A noob question support. Is there a CIFS support in the 2.6.32.21-gbe90714 kernel or a suitalbe cifs.ko file that one could use with the Cifsmanager app?
I am a bit lost here. I downloaded the DHD kernel source released, but had no luck locating the cifs.ko file. And I have no idea how to compile one myself. Can someone pinpoint me in the right direction?
update:
found some instructions here http://forum.xda-developers.com/showthread.php?t=783117 so I will see if I can get it working
update 2:
i have been able to build cifs.o (no cifs.ko was produced ) from the kernel provided by HTC, but it fails with insmod. The problem might be (besides that I have only a vague idea what am I doing) that the downloaded kernel is 2.6.32-g5ed1769 and my phone is running kernel 2.6.32-gbe90714.
Also compiling the kernel ends with this error
make[3]: *** No rule to make target `drivers/input/touchscreen/ntrig.o', needed by `drivers/input/touchscreen/built-in.o'. Stop.
Thats where I got stuck.
I have attached the file cifs.o produced.
Updare 3: Solved - see attachment in post http://forum.xda-developers.com/showthread.php?p=8865419#post8865419
Support/Troubleshooting forum sub section is needed, this Desire HD general is becoming a Desire HD trashcan..
M_T_M said:
Moved to general. Not a DEV thread.
Cheers,
Click to expand...
Click to collapse
I placed in DEV since it deals with kernel compilation. Maybe it should be moved to theme and apps as I am trying to get Cifsmanager app working on DHD.
Small update: I have managed to get a cifs.ko from kernel 2.6.32.17 from G2 partially working. I have HEX edited the file and changed to my kernel version.
I can insmod the file and mount drive without a problem. I can than access the mounted drives a browse the folders, but when I try to open the file I get an error.
I do not seem to be able to find a 2.6.32.21 kernel compiled cifs.ko which I believe might work with HEX updating "-gbe90714".
*push*
looking for the right cifs.ko as well :\ would be really nice to be able to mount cifs shares without custom rom...
anyone got CIFS working on stock ROM?
CIFS working on 2.6.32.21-gf3f553d
here is a working cifs.ko for DHD kernel 2.6.32.21-gf3f553d
Code:
su
insmod slow-work.ko
insmod cifs.ko
insmod nls_utf8.ko
It's a hex edited and --strip-debug cifs to educe file size of the version from MikeMelbourne. http://forum.xda-developers.com/showpost.php?p=9780217&postcount=7
Works fine on my DHD (samba access and video playback with V Player).
nxtwrld said:
here is a working cifs.ko for DHD kernel 2.6.32.21-gf3f553d
Code:
su
insmod slow-work.ko
insmod cifs.ko
insmod nls_utf8.ko
It's a hex edited and --strip-debug cifs to educe file size of the version from MikeMelbourne. http://forum.xda-developers.com/showpost.php?p=9780217&postcount=7
Works fine on my DHD (samba access and video playback with V Player).
Click to expand...
Click to collapse
Thanks for this, it works fine when I insmodded all the .ko's you zipped (that I placed in system/lib/modules/). On reboot though I cannot use cifs manager unless I insmod again. Do I need to insmod everytime i reboot?
Sent from my Desire HD
nxtwrld said:
It's a hex edited and --strip-debug cifs to educe file size of the version from MikeMelbourne. http://forum.xda-developers.com/showpost.php?p=9780217&postcount=7
Click to expand...
Click to collapse
I understand the hex edit - would you mind telling me how you did the --strip-debug - I'd like to do the same.
They were compiled on a headless PII 400 MHz running Ubuntu Edgy Eft server.
-Mike-
You just need to have the android ndk, which I supposed you have since you have bee able to compile the kernel. So just run
Code:
/path/to/android-ndk-r4b/build/prebuilt/linux-x86/arm-eabi-4.4.0/bin/arm-eabi-strip --strip-debug /path/to/cifs.ko
you have to modify the path to cifs.ko a and android-ndk-r4b
I have bee trying to compile the kernel my self on kubuntu, but always finished with an error, so I just ended up hexediting other files.
Thanks for your files. I have been waiting for a working samba mount to stream my videos from NAS!!
keemyb said:
Thanks for this, it works fine when I insmodded all the .ko's you zipped (that I placed in system/lib/modules/). On reboot though I cannot use cifs manager unless I insmod again. Do I need to insmod everytime i reboot?
Sent from my Desire HD
Click to expand...
Click to collapse
I am afraid it has to be insmoded every time on boot. You can automate it with Gscript or Tasker apps.
Thanks @Nxtwrld for the strip-debug advice. The HTC kernel never compiled with my phone's config.gz - after each failed compile I would have to edit .config and disable the item responsible for the build failure. I ended up compiling the module by itself.
Sent from my Desire HD using XDA App
Final compile - optimised versions against NDK R5.
Against the new Android NDK R5 I have just compiled:
* tun.ko - 18 KB
* slow-work.ko - 16 KB
* cifs.ko - 269 KB
* nls_utf8.ko - 4 KB
I have also debug stripped them - resulting in a total module size of 304 KB instead of 3.2 MB.
This time I compiled them on Ubuntu 10.10 instead of the ancient Ubuntu 6.10 I had been compiling on.
Again, these are for 2.6.32.21-g66cfb7a - feel free to hex edit them. I have tested both tun & cifs and they work.
Thanks again nxtwrld for the strip-debug advice.
Can you do the same for kernel 2.6.32.21-g3d0aaf ?
here you go.
thank you! Works very good!
nxtwrld said:
here you go.
Click to expand...
Click to collapse
Sent from my Desire HD using XDA App
I've tried for hours so far to understand more about the android and how to install the files inside 2.6.32.21-gf3f553d.zip.
I have the Desire HD with stock Orange rom and that kernel, i literaly have no idea how to install thease moduals onto the phone.
My desire hd is rooted and is S-on I've tried things like Kernel Update Utility and also just trying to simply copy and paste the files into system/lib/modules didnt work since astro didnt let me paste.
If it wasnt nearly 1am and i wasn't trying for the past 3 hours i would have done more reading. I know its something simple im missing, just can't figure out what the process is to installing thease modules is. First Android phone, first day with it as you can probebly tell.
Any help will be apreciated.
Thanks
arielc said:
I've tried for hours so far to understand more about the android and how to install the files inside 2.6.32.21-gf3f553d.zip.
I have the Desire HD with stock Orange rom and that kernel, i literaly have no idea how to install thease moduals onto the phone.
My desire hd is rooted and is S-on I've tried things like Kernel Update Utility and also just trying to simply copy and paste the files into system/lib/modules didnt work since astro didnt let me paste.
Click to expand...
Click to collapse
There's a free app in the market called "mount /system (rw / ro)" that can make your /system read-write (rw) or read-only (ro). After setting rw - you should be able to copy the *.ko files into /system/lib/modules.
Another alternative is to copy the *.ko files onto your sdcard (/mnt/sdcard).
You can then use an app (i.e. "Terminal Emulator") to enter these commands:
Code:
su
insmod /mnt/sdcard/slow-work.ko
insmod /mnt/sdcard/cifs.ko
insmod /mnt/sdcard/nls_utf8.ko
Alternatively, you can open CifsManager, open the Settings and specify a custom path to your kernel modules (i.e. in /mnt/sdcard). The recent version allows you to specify multiple modules, separated by colons. e.g:
Code:
/mnt/sdcard/slow-work.ko:/mnt/sdcard/cifs.ko:/mnt/sdcard/nls_utf8.ko
Hope this helps.
You should also check you kernel version and verify, that you are really running pin this kernel. I have no idea what the kernel for Orange branding is....
Amazing thanks, i did it with the terminal emulator method. First time i tried it, it wouldnt work. A restart later and i've rentered the comands and my computer drive is mounted. Works like a dream, thanks loads for th hex edited files and the walkthrough with diffrent options was so very helpful.
Things you need:
Base firmware (i'm use Gingerbread S5830SERKPH 2.3.4)
Windows (I'm use windows 7 X64 service pack 1)
Linux (Ubuntu recommended)
And the last thing is, You need enough experience in android world
step-step :
Flash your phone with your desired base firmware.
Make required modifications at your phone.
After that, do hard reset to your phone.
Next back up system.rfs .
put system.rfs with boot.img, data.rfs, recovery.img from PDA base firmware in one folder.
After that, repack your custom rom.
what should we do to modify it :
Remove useless widgets
Add more apps
Change theme
How to back up System.rfs :
Download at market "terminal emulator"
next run this code:
Code:
su
dd if=/dev/stl12 of=/sdcard/system.rfs
How to hard reset your phone :
Move by root explorer your modification apps to system/app then change permission like this :
Code:
User:Read, Write
group:Read
Others:Read
Next change the owner to "root" by root explorer
At least boot into recovery mode "HOME+POWER" and choose "wipe data/factory reset" be sure your contact data already backup
How to repack your custom rom :
PDA by running this code via terminal at linux:
Code:
tar -H ustar -c boot.img recovery.img data.rfs system.rfs >> ROMNAME.tar
md5sum -t ROMNAME.tar >> ROMNAME.tar
mv ROMNAME.tar ROMNAME.tar.md5
change ROMNAME to your desired, of course, ROM name.
If you want to build One-Package ROM, just use 1st and 2nd command and don't forget to include all files on all *.tar.md5 (such as modem, csc, apboot) like this :
Code:
tar -H ustar -c *.* >> ROMNAME.tar
md5sum -t ROMNAME.tar >> ROMNAME.tar
How to change your rom name :
At root explorer you see at folder system "build.prop"
Open it in text editor edit "ro.build.display.id=GINGERBREAD.XXKPH" with your rom name
Another Handy Modification Guide:
How to edit system.rfs on your Pc :
importan : if you want to edit system.rfs at windows, DON'T use Magic Iso, why? because i was use it, then my system.rfs corrupt.
you must have linux (ubuntu recommended)
run it from terminal :
Code:
sudo mount -o loop system.rfs /some_dir
make required modification
then Unmount it
How to Unpacking & repacking the image :
Note: below I give you the details for unpacking and repacking manually, but I have attached two perl scripts that do most of this for you
If you are good with a hex editor, you can open up any of these images and strip off the first 2k of data. Then, look for a bunch of zeroes followed by the hex 1F 8B (which is the magic number of a gzip file). Copy everything from the first line of the file, through the zeroes, and stopping at the 1F 8B. That is the kernel. Everything from the 1F 8B through the end is the ramdisk. You could save each of these files separately. In order to see the contents of the ramdisk, you need to un-gzip it and then un-cpio it. You could use a command like this (ideally after creating a new directory and cd'ing into it):
Code:
gunzip -c ../your-ramdisk-file | cpio -i
That will place all of the files from the ramdisk in your working directory. You can now edit them.
In order to re-create the ramdisk, you need to re-cpio them and re-gzip those files, with a command like the following (remember, cpio will include everything in the current working directory, so you probably want to remove any other cruft you might have in there):
Code:
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
The final step is to combine the kernel and your new ramdisk into the full image, using the mkbootimg program (which you should download and compile from the git repository):
Code:
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel your-kernel-file --ramdisk newramdisk.cpio.gz -o mynewimage.img
Now, there's a lot of hassle in pulling apart files in hex editors and remembering all of these commands, so I wrote unpack and repack perl scripts for you (attached). Hooray.
How to Manually deodex your phone :
What you'll need:
xUltimate v2.2
Unzip xUltimate v2.2, and launch "Main.exe"
If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
Run option 1. After option 1 is done, run option 2.
Now these well take a while. Run option 3.
IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
Now run option 4, and wait.
Exit xUltimate, and put the phone in USB mass storage.
Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
Put the phone in PC mode
Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Your phone should now be deodexed!
You may notice an increase in speed, and you now have the ability to edit certain files with greater effects.
How to change bootanimation :
using a Root explorer goto the /system/media directory.
Copy bootanimation.zip to your SD Card.
Connect your droid to your computer with usb and mount the SD Card
Copy bootanimation.zip to your computer.
extract bootanimation.zip to a folder
Inside you will find 2 folders with all the individual PNG files in them.
With photoshop or paint modify the png files to add your custom graphics, OR make/download your own pictures. (Make sure they are match with your phone device)
Highlight the two folders and the desc file.
Right click the highlighted files.
Select add files to archive.
Select Zip check box
In the compression method drop down box select Store. (this is key if you dont do this it wont play the animation)
save the archive as bootanimation.zip
copy the new bootanimation.zip to your SD Card
Select the bootanimation.zip file from your SD Card and move it... system>media>paste
________________
i'm just 12 years old if i can do it, why you can't
Advantages of this way is :
More efficient
Reduce your internet usage (dont need kitchen, apk manager, etc)
Easy to modification (You can see the direct result)
Reduce your time (only 2 hours i can do this way)
More soon
You steal my IDEAS Univos! No, just kidding, there are incorrect guide on "how to hard reset" lol. Anyway, try to build a ROM before creating this guide, my friend.
Wow Kids!
are doing development now a days
fla.sh said:
You steal my IDEAS Univos! No, just kidding, there are incorrect guide on "how to hard reset" lol. Anyway, try to build a ROM before creating this guide, my friend.
Click to expand...
Click to collapse
im not steal it.
Where is incorrect guide i'm try to fix it?
Sent from my GT-S5830 using XDA App
GadgetCheck said:
Wow Kids!
are doing development now a days
Click to expand...
Click to collapse
Thanks
Sent from my GT-S5830 using XDA App
This guide tested by me, and i have get result from this.
Sent from my GT-S5830 using XDA App
If you have question just ask me!
Sent from my GT-S5830 using XDA App
I think this guide is the same with fla.sh's guide.
devilsking said:
I think this guide is the same with fla.sh's guide.
Click to expand...
Click to collapse
Different, Fla.sh make guide for cooking his rom.
in this thread i tell you how to make your own custom rom.
with Phone device Samsung Galaxy Ace.
Univos said:
Different, Fla.sh make guide for cooking his rom.
in this thread i tell you how to make your own custom rom.
with Phone device Samsung Galaxy Ace.
Click to expand...
Click to collapse
ya ya. I see tks for your guide
devilsking said:
ya ya. I see tks for your guide
Click to expand...
Click to collapse
Please press thanks button, if i helped you
Sent from my GT-S5830 using XDA App
Univos said:
This guide tested by me, and i have get result from this.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Now that you're awesome like fla.sh , I'll be quietly tucking in a corner thinking how young teenagers get their knowledge . XD jkjk
EmoBoiix3 said:
Now that you're awesome like fla.sh , I'll be quietly tucking in a corner thinking how young teenagers get their knowledge . XD jkjk
Click to expand...
Click to collapse
Just kept reading, ask people, don't feel has a lot of knowledge, kept countinue to learn
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
Now that you're awesome like fla.sh , I'll be quietly tucking in a corner thinking how young teenagers get their knowledge . XD jkjk
Click to expand...
Click to collapse
Maybe this holiday i will developt a simple custom rom.
Sent from my GT-S5830 using XDA App
Univos said:
Maybe this holiday i will developt a simple custom rom.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I am thinking about a kid with two or more different XDA ID.
ketut.kumajaya said:
I am thinking about a kid with two or more different XDA ID.
Click to expand...
Click to collapse
No, the real name Fla.sh is "Aver..." my real name is "iz..." we are student of junior high school at surabaya. I'm "Aver..." friend.
Sent from my GT-S5830 using XDA App
Univos said:
No, the real name Fla.sh is "Aver..." my real name is "iz..." we are student of junior high school at surabaya. I'm "Aver..." friend.
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I'm swear.
Sent from my GT-S5830 using XDA App
ketut.kumajaya said:
I am thinking about a kid with two or more different XDA ID.
Click to expand...
Click to collapse
ROFLAMO
Jukirdolly said:
ROFLAMO
Click to expand...
Click to collapse
??????
Sent from my GT-S5830 using XDA App
New!!! -- BETA! BETA! BETA!-- UCKI1 kernel with Voodoo lagfix!
See this thread....
======================================
Mod_Boog_KH3_kernel_V3_V1
Thanks to Boog for a great kernel! I took it apart and tweaked it a bit mainly so that I would have full functionality in ADB and DDMS.
default.prop
Changed the following to allow ADB / DDMS to run as root:
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
init.rc
Modified to execute /system/etc/init.d scripts at boot. Also added sysctl.conf to /system/etc.
more...
Symlinks from Busybox to "ls" and "ps" have been removed from /sbin so that DDMS will work correctly. They now fall back to Toolbox links in /system/bin.
Several scripts have been added to /system/etc/init.d for experimenting. They can be removed, modified and added to as desired. However, the script "S99complete" should remain intact... without it NO scripts will be executed.
Have fun!
DOWNLOAD HERE
> Modified to execute /system/etc/init.d scripts at boot. Also added sysctl.conf to /system/etc.
How did you done that?
If /etc/init.d can be runned - can we have a mount commands changed to ext4?
Yuna said:
> Modified to execute /system/etc/init.d scripts at boot. Also added sysctl.conf to /system/etc.
How did you done that?
If /etc/init.d can be runned - can we have a mount commands changed to ext4?
Click to expand...
Click to collapse
I'll post the relevant parts of init.rc tomorrow... it's 2 am here and I'm going to bed! As for changing the mounts to ext4, there probably is a way but I'm not sure I want to be in the kernel / rom business. I just needed to fix ADB / DDMS and got a bit carried away.
by asking "how did you done that" i mean - how did you managed to change init.rc in pre-compiled kernel?
Yuna said:
by asking "how did you done that" i mean - how did you managed to change init.rc in pre-compiled kernel?
Click to expand...
Click to collapse
I extracted the ram disk with a script... I'll post that tomorrow also.
Yuna said:
by asking "how did you done that" i mean - how did you managed to change init.rc in pre-compiled kernel?
Click to expand...
Click to collapse
Get the extraction scripts here:
http://forum.xda-developers.com/showthread.php?t=901152
repackImage.sh has a bug though...
search for and change:
local at_min=
to
local at_min=0
Thanks.. I will give it a try. Good job and good luck for future work.
mtcarey said:
Mod_Boog_KH3_kernel_V3_V1
Thanks to Boog for a great kernel! I took it apart and tweaked it a bit mainly so that I would have full functionality in ADB and DDMS.
default.prop
Changed the following to allow ADB / DDMS to run as root:
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
init.rc
Modified to execute /system/etc/init.d scripts at boot. Also added sysctl.conf to /system/etc.
more...
Symlinks from Busybox to "ls" and "ps" have been removed from /sbin so that DDMS will work correctly. They now fall back to Toolbox links in /system/bin.
Several scripts have been added to /system/etc/init.d for experimenting. They can be removed, modified and added to as desired. However, the script "S99complete" should remain intact... without it NO scripts will be executed.
Have fun!
DOWNLOAD HERE
Click to expand...
Click to collapse
good job as a dev adbd as root is mandatory
ki2 is out what are you waiting for ?
mtcarey said:
Mod_Boog_KH3_kernel_V3_V1
Thanks to Boog for a great kernel! I took it apart and tweaked it a bit mainly so that I would have full functionality in ADB and DDMS.
default.prop
Changed the following to allow ADB / DDMS to run as root:
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
init.rc
Modified to execute /system/etc/init.d scripts at boot. Also added sysctl.conf to /system/etc.
more...
Symlinks from Busybox to "ls" and "ps" have been removed from /sbin so that DDMS will work correctly. They now fall back to Toolbox links in /system/bin.
Several scripts have been added to /system/etc/init.d for experimenting. They can be removed, modified and added to as desired. However, the script "S99complete" should remain intact... without it NO scripts will be executed.
Have fun!
DOWNLOAD HERE
Click to expand...
Click to collapse
Awesome! This is what I was looking for! Was hoping that someone with a bit more knowledge would chime in on some of this stuff.
I am super new to tweaking all that stuff, I'll look into your changes, and could roll them back over into mine, and future releases. All the fun stuff is coming out while I am at work!
boog said:
Awesome! This is what I was looking for! Was hoping that someone with a bit more knowledge would chime in on some of this stuff.
I am super new to tweaking all that stuff, I'll look into your changes, and could roll them back over into mine, and future releases. All the fun stuff is coming out while I am at work!
Click to expand...
Click to collapse
Have at it boog! I didn't really know these changes off the top of my head... had to dig around a bit. I'll post the change to init.rc soon for the init.d stuff.
DAGr8 said:
good job as a dev adbd as root is mandatory
ki2 is out what are you waiting for ?
Click to expand...
Click to collapse
I'll leave ki2 to boog... got my hands full with app development!
Modification of init.rc to run init.d scripts at boot
# ============================================== MTC
setprop cm.filesystem.ready 0
start sysinit
on property:cm.filesystem.ready=1
### Script S99complete in init.d sets this property to 1 and
### allows processing to continue. Do not remove this script!!!
# ==================================================
class_start default
## Daemon processes to be run by init.
##
# Declaration of service to execute scripts in /etc/init.d ===== MTC
service sysinit /sbin/run-parts /system/etc/init.d
disabled
oneshot
# =================================================
Mtcarey, if you could get EXT4 support on this kernel you would be a God!!!
Sent from my SAMSUNG-SGH-I897 using xda premium
amwbt said:
Mtcarey, if you could get EXT4 support on this kernel you would be a God!!!
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Funny you should mention that.... I was just just looking into it.
mtcarey said:
Funny you should mention that.... I was just just looking into it.
Click to expand...
Click to collapse
Please do! Since designgears left the Captivate, no one cares to keep up the work. In my opinion, the Captivate is useless without it. I just can't bring myself to run a Captivate rom without EXT4 support.
Sent from my SGH-I897 using xda premium
amwbt said:
Please do! Since designgears left the Captivate, no one cares to keep up the work. In my opinion, the Captivate is useless without it. I just can't bring myself to run a Captivate rom without EXT4 support.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
The latest builds fly without ext4. Not sure I would call it useless.
But, I ended up getting into the kernel stuff because it appeared no one else was going to.
boog said:
The latest builds fly without ext4. Not sure I would call it useless.
But, I ended up getting into the kernel stuff because it appeared no one else was going to.
Click to expand...
Click to collapse
I agree with you, ki2 is super fast and stable (with no ext4)
mtcarey said:
Funny you should mention that.... I was just just looking into it.
Click to expand...
Click to collapse
If you do find something, I would be curious to know. Everything I have tried (pulling lagfix out of other kernels) results in initramfs being too large. Even after removing all the voices.
I'm just not sure how much gain would be had for all the work. Getting sources would be cool.
boog said:
If you do find something, I would be curious to know. Everything I have tried (pulling lagfix out of other kernels) results in initramfs being too large. Even after removing all the voices.
I'm just not sure how much gain would be had for all the work. Getting sources would be cool.
Click to expand...
Click to collapse
Yup. Exactly what happened to me. I tried everything to get the size down, but still ended up about 1 mb too big. Oh well, it was a learning experience. I agree that there probably isn't much to gain anyway... rfs now seems as fast as ext4 ever was.
Why don't you make your own lagfix? e.g why need to put all the voodoo stuff, if you (IMHO) need to edit init.rc mount stuff:
mount rfs /dev/block/mmcblk0p2 /data nosuid nodev crypt check=no
mount rfs /dev/block/stl10 /dbdata nosuid nodev crypt check=no
Why not to try this way?
Well, voodoo by itself is good cos it auto-converts partitions - but sometimes it lags
but why not to do this, and after time make a auto-conversion script?