Related
Hello!
I bring to your attention a small script to change the size of PagePool directly on the device.
The script allows to replace the size PagePool From 2.00 to 16.00th mbyte without a reflash of the device and loss of data.
After work of a script it is enough to make a soft reset to the device.
In a script is implemented the algorithm of automatic search of the address of offset and check result of search with use of check value on algorithm MD5 . In this mode every possible checks are made so much what kill the device practically not possible.
Also there is a possibility of instructions of own displacement of value of the size PagePool In a case when automatic search cannot find out it. In this mode value to the specified address is checked only. And if it not in the range of values of the size PagePool from 2 to 16, script also refuses to make changes to a device insertion.
The script is checked up with several firmwares and devices.
If program can't autodetect offset value of PagePool, generate "dev info"
and provide it to me. Im add your device in autodetection feature.
Thankful in advance for responses about work of a script and the help in perfection of this.
Screenshots and script are applied
P.S. Sorry for bad english
latest version available at ftp://intruder.spb.ru/PPSmartChanger.exe
First of all thank you for your hard work!
I read everywhere about this "PagePool". Can i ask what's this? And which PagePool is more wise to use?
TIA
If I correctly have understood you, I answer
PagePool it is area which it is used by system for caching various information. The size of accessible RAM depends on the size of this area for. As a rule this value selects everyone under itself individually. Someone uses the big programs which is necessary a lot of memory, and someone a much small programms.
As the program allows to change this value without loss of data, it is possible to experiment.
If has worked address autodetection that all it should be good.
If has not worked, I need info about your device and firmware to try add your device to autodetection.
Thanks for this sweet app....
Now I can change the pagepool on the fly... even though I wonder how many times I will actually change it...
You can change the size of PagePool as many times as you need without any limits.
Version updated:
1. Improved method of info retrival from device.
2. Added multidevices support.
3. EXPERIMENTAL: Added support of WM6 on FS LOOX C550 (can't test on device, my device HTC Touch)
So, what would be the best size for the Touch? I know it should be smaller, I've read 4MB somewhere but is that best or at least better than original?
I'm using BatteryStatus with enabled CPUScaler and I noticed when I change the PagePool size to 4 Mb, TCPMP player works on higher frequency (299 MHz, Boost) instead of 247 MHz (Max) with 8 Mb PagePool size.
So if PagePool size is 4 Mb and less we have low productivity.
I found that 6 Mb is good size. The productivity is the same as with 8 Mb and free memory bigger for 2 Mb.
Version updated.
Hi shark... It's not working on my Touch. Firmware using is 1.11707.1B WWE.
Swiftblade said:
Hi shark... It's not working on my Touch. Firmware using is 1.11707.1B WWE.
Click to expand...
Click to collapse
Hi! Please use new version and if it not work, build info for me (option in menu) and attach to reply
Latest version can be accessed at ftp://intruder.spb.ru/PPSmartChanger.exe
the link of your app doesn't work anymore...
can you upload it to a different server please.
thanks
It did work on mind.
It said Dump size mis-matched.
Try built Development Information.
It also failed and sais Some **** happened!
Don't know what is next. ROM I used is the 55Meg Big Storage ROM without Extended ROM found in this forum.
jychan28 said:
It did work on mind.
It said Dump size mis-matched.
Try built Development Information.
It also failed and sais Some **** happened!
Don't know what is next. ROM I used is the 55Meg Big Storage ROM without Extended ROM found in this forum.
Click to expand...
Click to collapse
Same to me
Please wait while tool locate PagePool setting offset
_______________________________________________________
Started at 10:50:08.39
> Initializing... done
> Reading ROM info... done
> Dumping part of ROM.. ERROR
> Locating PagePool setting. skipped
> Checking MD5. skipped
Finished at 10:50:41.82
_______________________________________________________
Size of dump is mismatch
Press any key to continue . . .
Click to expand...
Click to collapse
But building of debug info worked.
Don't know how to contact you at 4PDA.ru since my russian is very rusty (cannot even read any of these words).
So I post the log here
My ROM is1.11.407.1B.GER (original german HTC Touch)
I have the same problem with jychan28
ROM: 1.11.721.2B WWE
Radio Ver: 02.93.90
Hi,
I was wondering how i can change the pagepool size when i'm cooking a rom?
I've been searching and searching but didn't find anything to change the touch's pagepool.
Gr. bram
New version at ftp://intruder.spb.ru/PPSmartChanger.exe
bram_smulders said:
Hi,
I was wondering how i can change the pagepool size when i'm cooking a rom?
I've been searching and searching but didn't find anything to change the touch's pagepool.
Gr. bram
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=323269
If any **** happens, download new version
It buil development info in C:\PPSCDev.
sorry...
_________________________________
> Checking........7z.exe: No such
file or directory
.. ERROR
Tool might be broken
Execution aborted
Press any key to continue . . .
Click to expand...
Click to collapse
the file I downloaded is also only 229kB instead of 295kB of 0.37a
Sorry, it's my fault. Script updated, try again.
Here it is:
This utility runs on your computer (PC/Laptop) not on your PPC Phone!
You will be Patching the nbh file before you flash your device.
Requires you have Dot NET Framework 2.0.0x or better installed.
This simple tool will easily change:
The Rom Version Displayed during the Boot Process.
The Initial Rom Date
The PagePool Setting (supports Dynamic, 6mb, 12mb, 16mb, 18mb, 24mb & 32mb).
Easy to use:
1. Click [Browse] and find your NBH File
2. Click [Analyze], it will find the Rom Version, Rom Date and PagePool Settings and tell you what they are.
3. Make the desired changes.
4. Click [Modify]
5. If you click [Analyze] again it will verify that your changes were made to the image (imemory).
6. Click [Save]
You have changed your PagePool and/or Update the Rom Date!
I have tested this and successfully flashed the following modified Rom Images:
AT&T WM6.0 Rom 1.62.502
Dopod WM6.1 Rom 3.10
AT&T WM6.1 Rom 3.51
Use at your own risk.
I will be keeping it in my 4shared Public Folder: Kyphur.4shared.com. There is now a folder for the PagePool Patcher, go there for the orignal & latest Versions.
Special thanks to duttythroy, Tayton & Sleuth255 it was their info that got this started.
If you want to support development of this (and possibly other Rom Cooking Tools) click on the [About] button to find a [Donate!] button.
Also, it has been reported to work on Touch dual Rom Files.
Enjoy....
Can you add 10mb PagePool Size ?
Is-it possible to modify the first number in ROM version ?
Thanks for your hard work !
thanks alot for your hard work kyphur. Will this work on slueth's 1.2 or schap's? What is it supposed to say if it don't work? TIA..
No it is not possible to modify the first number, even if I actually overwrite it in the Rom file it will have no effect.
As for adding new PP Sizes, I think I've got it pretty well covered. I mean is there really that much of a difference between 10 & 12mb? Yeah, I know I have 16 & 18 but that's because 16/18mb seems to be a sweet spot with the Kaiser.
Tell you what, if I find other reasons to make a new compile then I'll add a few more PP Sizes.
MickyMax said:
Can you add 10mb PagePool Size ?
Is-it possible to modify the first number in ROM version ?
Thanks for your hard work !
Click to expand...
Click to collapse
It should work on all of them.
If it reports any strange data (like Rom Version or Date contains something out of place) or an unusual PagePool Number then let me know.
Knumb said:
thanks alot for your hard work kyphur. Will this work on slueth's 1.2 or schap's? What is it supposed to say if it don't work? TIA..
Click to expand...
Click to collapse
thanks again! I'll try it out and let you know if I get some weird info...
Very good to have a patcher for all ROMS
But, when I hv used it on your own ROM (XDA live 3.0) and set the PP to dynamic (which I believe is the best), it failed to analyze the ROM again.
So, I was afraid to flash the ROM with wrong parameters
I'm looking into it right now, found a minor coding issue related to adding the "Classic Rom" support that only affected setting the PP back to Dynamic.
msharaf said:
Very good to have a patcher for all ROMS
But, when I hv used it on your own ROM (XDA live 3.0) and set the PP to dynamic (which I believe is the best), it failed to analyze the ROM again.
So, I was afraid to flash the ROM with wrong parameters
Click to expand...
Click to collapse
Fixed & Uploaded, get the latest from my rapidshare folder.
msharaf said:
Very good to have a patcher for all ROMS
But, when I hv used it on your own ROM (XDA live 3.0) and set the PP to dynamic (which I believe is the best), it failed to analyze the ROM again.
So, I was afraid to flash the ROM with wrong parameters
Click to expand...
Click to collapse
kyphur said:
Fixed & Uploaded, get the latest from my rapidshare folder.
Click to expand...
Click to collapse
That was quick will test and give feedback
Thanks
Great Great Great
Works flawlessly (tested on many versions)
One last question, can we do it on the phone memory without need to re-flash after modification.
Thanks
Nope, you got to modify the image file before flashing.
msharaf said:
Great Great Great
Works flawlessly (tested on many versions)
One last question, can we do it on the phone memory without need to re-flash after modification.
Thanks
Click to expand...
Click to collapse
kyphur said:
Nope, you got to modify the image file before flashing.
Click to expand...
Click to collapse
Thanks again for your prompt response
Cheers
Last update:
I did change the PP in your ROM to Dynamic
After flashing the phone freezes at windows welcome screen and never prompt to touch the screen to continue preliminary setup.
I changed the PP of the same NBH file from Dynamic to 32MB, reflashed, and worked.
Couldn't get my favor dynamic PP
Wow, that is really odd, for Dynamic I simply set the values back to their default.
I'm busy with work right now and might not get a chance for in depth testing for a few days but by this weekend I'll give my development kaiser a workout and see if I can duplicate your results.
msharaf said:
Last update:
I did change the PP in your ROM to Dynamic
After flashing the phone freezes at windows welcome screen and never prompt to touch the screen to continue preliminary setup.
I changed the PP of the same NBH file from Dynamic to 32MB, reflashed, and worked.
Couldn't get my favor dynamic PP
Click to expand...
Click to collapse
maybe n00b but...What does dynamic actually do??
Dust2Dust said:
maybe n00b but...What does dynamic actually do??
Click to expand...
Click to collapse
No fixed size, grows as much as needed.
thanks for one more time for your work kyphur
if i change pagepool and flash again the new rom,can i use a backup for restore (from the same rom but with different pagepool) or it's worthless??
and i have to build again all my apps from beginning....
In theory you should be fine.
zaharakis said:
thanks for one more time for your work kyphur
if i change pagepool and flash again the new rom,can i use a backup for restore (from the same rom but with different pagepool) or it's worthless??
and i have to build again all my apps from beginning....
Click to expand...
Click to collapse
kyphur said:
In theory you should be fine.
Click to expand...
Click to collapse
i'll try it and i'll give report
thanks for your support my friend
Dimitris
I successfully got Cyanogen's 2.6.29-cm [email protected]) kernel up and running on Hero.
Link http://www.demarcatedmedia.com/rom/jacHEROski_Experimental.zip
This is a very, very experimental build (I rough cut the new boot.img). Please, anyone who volunteers to experiment please have DDMS up and running so you can send me logs.
As you can see from the pictures, I loaded Drizzy's optimized apps and framework because I had never seen the Ophone graphics and wanted to see what they are all about. If drizzy doesn't mind I'll drop the graphics but keep the optimized apps
Preqs:
New SPL
New Radio
Recommended:
FAT32
EXT3
linux-swap (32 MB)
Cyanogen Recovery 1.3 or greater.
Old Features:
linux-swap supprt
optimized rosie
New Features:
Kernel From Cyanogen
optimized widgets courtesy of Drizzy
Ophone Graphics (maybe)
appstosd from Nismo
TO DO / Known Issues
Change default boot config (let's widgets etc on first boot)
IF GOD LOVED ME HE WOULD LET ME FIGURE OUT HOW TO DO FOUR HOMESCREENS
other little surprises
1) wifi won't start
2) gps still a no go
--------------------------------- THE OLD ROM DOWNLOAD LINK AND INFO BELOW ------------------------------
ALL OF THE THANKS GO to JAC, Denkai, coolbho3000 and everyone else who makes this possible.
This is a slightly modified JACHero2.3.3 release.
This ROM is for those who prefer a 3rd linux-swap partition. The modified a2sd.sh will start swap on every boot (http://forum.xda-developers.com/showthread.php?t=531988).
THREE PARTITIONS
FAT32
EXT2 OR EXT3
linux-swap
Included in this ROM is the Super Optimized Rosie from http://forum.xda-developers.com/showthread.php?t=532822
Next up, 4 Home screens on Rosie for the win! <---- probably should have been more specific, I'm working on this (it's more difficult than I anticipated)
Enjoy your ROMen noodles!
http://demarcatedmedia.com/rom/jacHEROski2.zip <----- slightly smaller Rosie, still working on fewer Home Screens
The file should be roughly 79.43MB - I used MEGAUPLOAD so who knows.
Please Note: This is my FIRST ROM, so use at your own risk. It does, however, work flawlessly on mine.
As always, I would recommend freshly formatting you sd card (at least the ext3 and linux-swap partitions) and wiping data before applying.
Awesome! Been looking for something like this. Gratz on your first ROM and props to everyone who made this possible. Downloading right now
could you plzzz upload to other site coz megaupload is not available in my area...
Question. If I am using a ext2, do I still need to do the 3rd? If so, how do I do that? Can I use partition manager?
would be cool if we could choose how many home screens it had.
Breakthecycle2 said:
Question. If I am using a ext2, do I still need to do the 3rd? If so, how do I do that? Can I use partition manager?
Click to expand...
Click to collapse
Yea, I don't know I haven't tested it on two partitions. This ROM is mainly for those who have three partitions set up on their SD card.
FAT32
EXT3 or EXT2
linux-swap
The best part is you don't have to worry about your SD card getting corrupted when you mount.
You can use whatever to partition your SD card so long as it partitions it!
Lieu10ant said:
would be cool if we could choose how many home screens it had.
Click to expand...
Click to collapse
Working on this now. At least, trying to reduce the number of screens.
leomak said:
could you plzzz upload to other site coz megaupload is not available in my area...
Click to expand...
Click to collapse
where can you download from?
ccyrowski said:
where can you download from?
Click to expand...
Click to collapse
anything else please... the site blocked my area (HK)
leomak said:
anything else please... the site blocked my area (HK)
Click to expand...
Click to collapse
I'm uploading now, gonna be about 30 mins.
swappines
what is swappiness set at and can we change it? also what size should swapp portion be
bizz3d said:
what is swappiness set at and can we change it? also what size should swapp portion be
Click to expand...
Click to collapse
the linux-swap partition should be 32MB
swappiness is set at 20
you can edit the "echo 20 >" command in the a2sd.sh to change the swappiness.
ccyrowski said:
the linux-swap partition should be 32MB
swappiness is set at 20
you can edit the "echo 20 >" command in the a2sd.sh to change the swappiness.
Click to expand...
Click to collapse
thanks for such a quick reply. I was reading the link you provided about the size. Flashing now
bizz3d said:
thanks for such a quick reply. I was reading the link you provided about the size. Flashing now
Click to expand...
Click to collapse
Cool, let me know how it goes. I flashed without a problem.
thanks so much for the second link~~
ccyrowski said:
Cool, let me know how it goes. I flashed without a problem.
Click to expand...
Click to collapse
It flashed just fine but, am i suppose to see all "0" in terminal after
su
free
i have a my sdcard setup with Fat32 first Ext3 second and Linux Swap last with 31mb.
not sure what i did wrong. i used Paragon to setup my sdcard if that helps
will this work if you only have a ext 2 or will it boot loop?
peary27 said:
will this work if you only have a ext 2 or will it boot loop?
Click to expand...
Click to collapse
it should be fine. When in doubt, flash!
thanks downloading now
bizz3d said:
It flashed just fine but, am i suppose to see all "0" in terminal after
su
free
i have a my sdcard setup with Fat32 first Ext3 second and Linux Swap last with 31mb.
not sure what i did wrong. i used Paragon to setup my sdcard if that helps
Click to expand...
Click to collapse
It should be fine. You should see numbers where there are zero's.
unpack the udpate.zip on your computer and go to /system/bin/a2sd.sh and post the contents here so I can see what it says.
Please Read
This will not change anything on your phone that would prevent you from ever flashing a new rom or nandroiding back to a working one. Everything this update will do can completely be erased with a wipe or nandroid. Also flashing any rom, clean install or not, will preplace the boot.img this update.zip puts on your phone. So dont blame these downloads for your simple user errors of not being able to flash a new rom or nandroiding.
This is an overclocked kernel from toastcfh godmode .29 source. The kernel was actually pulled from Fresh Toast
This works on DamageControl and roms based off of his, it will not effect any of DC mods, including the Dconig app.
UPDATE
6/6/10- This should be working on the newest damagecontrol 2.09. Please report (if overclocking has worked in the past for you) if you have a problem on the newest release.
Click to expand...
Click to collapse
I made an attempt to get compcache to work, so it might or it might not. Someone with more experience might want to double check it.
Both include setcpu.txt for Setcpu OC app.. Select "custom" at the very bottom for device. Do not select hero. Or you can select "Auto Detect" at the top, this does not need the setcpu.txt.
*View attachment damage710v2.zip* THIS IS A TEST KERNEL FOR THE NEWEST DAMAGECONTROL 2.09.. It is the exact same as damage710 but with a newer ramdisk, this is in hope of fixing any problems anyone is having with 2.09 and OC kernel. There might not even be a difference in the new ramdisk between the old one. I didnt have time to check. Sooo ya.
*View attachment damage537.zip* 537mhz is the default.. scalable to 768 if you use an OC'ing app
*View attachment damage768.zip* 768mhz default clock speed -read below
*View attachment damage710.zip* 710mhz default clock speed -read below
Both can be scaled from 19.2 to 768mhz..
DAMAGE710--The damage710 will default 710mhz, you must use an OC app to scale it to 768. Use damage710 if your phone can not boot the 768mhz. And dont scale any higher then 710mhz or your phone might reboot.
DAMAGE768--If your phone can boot the 768mhz then either download will work. But if you dont want to use an OC'ing app then the damage768 will scale to 768mhz.
This IS a flashable update.zip.. This will only replace your boot.img of your phone. So it is not a full rom. This is applied on top of your rom.
ALWAYS MAKE A NANDROID BEFORE FLASHING.
You Do Not Need A Partition On Your Sdcard For Overclocking
THIS IS A MUST FOR SWAP/compcache
To get swap working, you must have an ext partition on your sdcard. This will format you sdcard erasing everything, so do the following. Back up everything from your sdcard to your computer(exp- In a folder on your desktop named Sdcard). In recovery, select partition sdcard, use all default values, 32mb swap, 512mb ext partition, the rest fat32. Then when its finished change ext2 to ext3. Then reboot the phone. And then move all the files you backed up to the computer back to your sdcard.
If thanking me for putting this together. You should also give an even bigger thanks to Toastcfh for this kernel.
Thanks also goes to flipzmode, cuz i pulled the kernel from his boot.img in fresh toast.
Also darchstar for the defaulting clock speed tip.
So does this mean we can get the real AOSP dialer on Damaged's ROM?
mattshaver said:
So does this mean we can get the real AOSP dialer on Damaged's ROM?
Click to expand...
Click to collapse
No.. this just adds overclocking and the few extra things that come along with it in the kernel. Has nothing to do with AOSP.
you rock
10 char
Excuse my ignorance on this topic.
But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) , so what is the difference?
My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.
If anyone wants to know how to do this, follow this guide starting at Step 8.
Essentially just extract the kernel you want from the right boot.img, extract the ramdisk from the other boot.img, then use mkbootfs and makebootimg to put them back together.
PM me if you need help.
mattshaver said:
Excuse my ignorance on this topic.
But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) , so what is the difference?
My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.
Click to expand...
Click to collapse
I dont mind, ask anything here. Its how we learn
But that was the issue with all 2.1 roms. Toastchf cracked the code (in a way, not literally). And was able to give us a working source for .29 kernel. That kernel can then be used to work on any cdma hero 2.1 rom. But there are different things you have to do to get it to work on Darchdroid AOSP rom, he has already done that and its in his newest release. This one I posted above is just to work with damagecontrol roms or ones based off of it.
To get the AOSP dialer working you would have to have a rom based on AOSP, which darchdroid is the only rom so far. All the other roms are based on htc framework or just something different then AOSP. But im pretty sure theres AOSP dialers for damagecontrol. Go check the apps and themes section.
EDIT: the dialers are also completely separate from the kernel. Its based on what the rom is.
i'm running ic3rom and in the process testing it out
jeremysterling said:
i'm running ic3rom and in the process testing it out
Click to expand...
Click to collapse
If you downloaded the compcache one, can you go into terminal and type
adb shell
free
Tell me if it says "swap" in what comes up and that it doesnt have all 0's.
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)
schmooo said:
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
Click to expand...
Click to collapse
It doesnt effect jit at all. It only adds a few files and changes your boot.img.
schmooo said:
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
Click to expand...
Click to collapse
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.
Jus10o said:
If you downloaded the compcache one, can you go into terminal and type
adb shell
free
Tell me if it says "swap" in what comes up and that it doesnt have all 0's.
Click to expand...
Click to collapse
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#
Re: [KERNEL] Toast-godmode .29 source for DamageControl
So I can flash this and oc icerom? Etc....
-------------------------------------
Sent via the XDA Tapatalk App
mattshaver said:
I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)
Click to expand...
Click to collapse
Haha well you are right sorta on what the kernel does, but all cdma htc heros use the same kernels but it depends on what android version you are using. 1.5 uses .27 kernel, and 2.1 can use a edited .27 kernel but something things wont work, like camera. What toast did was made his own .29 kernel based on other sources and what we already have then we use for our 2.1 roms. The 2.1 roms that come from sprint use a .29 kernel that work, but we cant edited anything within the kernel until they release the source to the kernel. You must have source to the kernel to be able to change anything with in it. You cant download a rom from xda and take the kernel out and change the files and put them back. You have to already have the files to the kernel, change what you want, make your own kernel and then put it on the rom. Cuz once you compile the kernel its not able to be opened back up.
In a boot.img there are 2 parts, the kernel and a ramdisk. The ramdisk CAN be opened back up and changed. But if its trying to call something within the kernel it has to already be there, since you cant add anything to it. If you start with all the kernel files and compile your own like what toast did, then you can add the special things like overclocking frequencies.
I know I really suck at explaining things. I only know the basics of how it all works.
jeremysterling said:
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#
Click to expand...
Click to collapse
And you have the compcache.. or the newer one i posted?
Jus10o said:
It doesnt effect jit at all. It only adds a few files and changes your boot.img.
Click to expand...
Click to collapse
Decad3nce said:
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.
Click to expand...
Click to collapse
sweet im gonna give it a try
Jus10o said:
And you have the compcache.. or the newer one i posted?
Click to expand...
Click to collapse
i downloaded and flashed damage1.zip with compcache
jeremysterling said:
i downloaded and flashed damage1.zip with compcache
Click to expand...
Click to collapse
Ok thanks.. yea compcache and swap arent working. Ill work on it.
But overclocking and everything else is. So its not gunna make a noticeable difference.
Progress update and INT2SD implementation request form!
With holidays starting, and more free time on my hands, I've decided to revive this project. Having my hard drive fail on me recently, and losing the request log, it has become obvious that I need a new system of handling requests, and it is here. If you have requested a ROM before, please send a request again, via this form.
Please submit all further requests via this form!
---
This is the INT2SD thread for Sense ROMs and their developers and users.
INT2SD thread for AOSP ROMs
What is INT2SD?
INT2SD doesn't use symlinks. It mounts ext partition on your SD to /data, thus eliminating the need for the mtd5 userdata partition. This makes the mtd5 userdata partition unneeded. It is used in conjunction with the fatsys HBOOT (more info later on), allowing most of the vital parts of a ROM to stay on the system partition without the need to symlink half of it to the SD due to memory shortage.
For now, there is only one ROM here, but more will come! If you wish to see INT2SD in your favorite ROM or in your own ROM, please post here!
INT2SD-S - "Speed" (default as of 29th Jun)
Main characteristics:
/data on SD ext, /data/data on internal
/data/data limited to 280 MB (probably enough for more than 100 user apps)
noticeably faster on slower cards
for use with CM7r2 HBOOT
Description:
The new "speed" flavour mounts ext to /data and userdata to /data/data, achieving great speed while still retaining excellent storage capabilities. It's used with the CM7r2 HBOOT. This is now the default flavour, offering great speed while still being able to hold a hefty amount of apps.
INT2SD-M - "Mass" (discontinued)
Main characteristics:
/data on SD ext
number of apps is only limited by ext size
requires a faster card
for use with fatsys HBOOT
Description:
The classic "mass" flavour mounts ext to /data, thus eliminating the need for the mtd5 userdata partition. It has proven to be slow even on some of the faster cards. Due to INT2SD-S being able to hold a very high number of applications, and still being much faster, this flavour is discontinued.
FAQ
For users: How to get this in your favorite ROM
For ROM developers: How to get this implemented in your ROM
Please fill out this form.
Cross-device implementations
For now, no. You may submit requests, but I won't be able to fulfill them for a while. I have quite a lot of real life work on my plate, not to mention a list of Desire ROMs I have to tend to. After that's done, I'll be happy to try blind-porting it to whichever device you wish, but my priority are Desire ROMs, primarily because it's a lot easier to implement INT2SD into ROMs for a phone I already have.
Universal update zips
Also, no. Each ROM is different, and due to the nature of INT2SD, it is simply not possible to make a one-for-all universal update zip. Every ROM requires tending to its peculiarities, especially Sense ROMs, and I would rather not take the change of trying to make one and end up with a flashable bootloop zip.
Why don't you just publish instructions on how to implement INT2SD for devs to use?
Proz0r said:
You can take a look at the modified ROM and you will find 3 new files in /system/etc, dalchk, fsck and sleep. These files are executed by init.rc because of my modifications to it. You can also decompile the boot.img and use a tool such as diff or diffuse (a GUI for diff) and check the differences between it and the unmodified init.rc from Alex's standard, D2EXT ROM. However, his ROM required another init.d script to move weather animations to /data, and modifications to the updater-script to flash everything that would normally be flashed to /data, to be flashed to /sd-ext. Sounds simple enough, right? Well, it's actually not quite as simple. When I have first implemented INT2SD to CyanogenMod 7, all I had to do was edit a few lines and add those three scripts. There was not a single ROM (and there are a few unreleased ones which I've worked on) to which I could apply a "standard" procedure. Each ROM required further modifications on its own and being the one who devised INT2SD, I know what I should look out for in order to avoid catastrophical bugs. ROM developers do not. This is why I do NOT offer support for "homemade" INT2SD implementations. Every ROM has its own peculiarities that need tending to and INT2SD implementations need to be very flexible to allow the ROM to work in conjunction with it. Sure, everything could go great, but INT2SD is extremely easy to implement horribly wrong and have huge bugs and even unbootable systems, and without knowing what the dev did to put it in their ROM, it is next to impossible for me to troubleshoot and fix. It would probably end up with me having to implement it myself either way in most cases and having angry developers and possibly users on my hands being pissed at me for doing a bad job and releasing a ****ty product, when the problem was just a typo in init.rc. That's why I have not nor will I release instructions for devs on how to implement it themselves.
Click to expand...
Click to collapse
Before you download!
Although it is for the best part bug free, INT2SD is still a fairly fresh project so I'm looking for as much input as I can get to fix possible bugs I haven't yet uncovered. If you try a ROM featuring INT2SD, please be sure to comment in this thread on your experience, even if it works great or doesn't work at all. If you wish to further support the project, there is a donate button in my signature. Although a nice sign of support and appreciation, donations are not obligatory!
Due to /data/data being on the SD, a high-class card is recommended.
Another thing is the HBOOT, fatsys. You must flash it before flashing any of the INT2SD Sense ROMs.
fatsys HBOOT
bravo_alphaspl-fatsys.img
MD5: 2272c1cb06f8eb743aa1c0ad4c3fa36b
PB99IMG-fatsys.zip
MD5: 4d6b2e74c241361237df047bfed5ff08
INT2SD Sense ROMs require a special HBOOT, fatsys. This special HBOOT has 427 MB dedicated for /system, 5 MB for /cache and 5 MB for /data and there is probably no ROM without INT2SD that would work on it properly. It was made so that the largest part of Desire's internal memory can be used for quick access to vital system files by storing them in /system instead of symlinking them to /sd-ext, therefore slowing the entire system down. There is still plenty of space for your apps if you make a large enough SD ext partition, since SD ext gets mounted to /data and the real, 5 MB mtd5 userdata partition goes unused. So, /data on SD ext, huge /system and no symlinks! Before flashing a Sense INT2SD ROM, make sure you have flashed the fatsys HBOOT!
Download
Thanks to Ante0 for hosting the files!
INT2SD implemented in:
Alex-V1.8 GB Sense HD INT2SD-M fatsys (Thread | Download)
Alex-V1.8 GB Sense HD INT2SD-S CM7r2 (Thread | Download in a minute)
Runnymede AIO 6.1.1 Beta (Thread)
Current bugs:
-
To do list for the next version:
-
Credits (alphabetically):
Alex-V - providing me with the first Sense ROM to implement INT2SD in
Ante0 - providing proper hosting for the zips
brabo, GShellz admin - huge help with bash scripts implemented in the ROMs
CM - a base ROM for implementing the method in
Droidzone - suggestions, help with HBOOTs
Hacre - massive assistance as well, kicking me to try and realise the main idea and for coming up with names "INT2SD" and "fatsys"
JieeHD - help with compiling/decompiling the boot.img files and his excellent guides on FYA
Pulser_g2 - massive assistance, ideas on the reboot bug and hosting
Richard Trip - making GingerVillain which now has a version featuring INT2SD
snq- - pointing out a huge typo and saving me multiple hours of pointless work
ubuntubhoy - a kick in the arse I needed
... and everyone else in the #villainrom IRC channel for help and mental support! Thank you all, and everyone I forgot to mention (PM!).
Disclamer: I'm not responsible if something goes wrong and wreaks havoc upon you, your phone, your card, any part of your phone, your friends, your family, your close or distant relatives and/or your pet, but I will gladly provide assistance if it does.
I'm not a dev at all, but I think this tool can help you: a too for making coustoms hboot by _thalamus
http://thalamus-hacking.blogspot.com/2011/07/custom-hbootsupdate.html
I have been using for months without any problem
Well, if you manage to learn how to reverse engineer and manipulate hboot, do share.. You might want to ask thalamus. I read that he'd done it.
Edit: Ah blackhawk_LA has already posted that.
@blackhawk_LA, is there an open source version of this tool?
blackhawk_LA said:
I'm not a dev at all, but I think this tool can help you: a too for making coustoms hboot by _thalamus
http://thalamus-hacking.blogspot.com/2011/07/custom-hbootsupdate.html
I have been using for months without any problem
Click to expand...
Click to collapse
Awesome, thanks! Wish there was a Linux version of it, luckily, I have Windows in dual-boot so I'll whip something up in a minute!
Droidzone said:
Well, if you manage to learn how to reverse engineer and manipulate hboot, do share.. You might want to ask thalamus. I read that he'd done it.
Edit: Ah blackhawk_LA has already posted that.
@blackhawk_LA, is there an open source version of this tool?
Click to expand...
Click to collapse
Yeah, I'm interested in how this works too.
Droidzone said:
@blackhawk_LA, is there an open source version of this tool?
Click to expand...
Click to collapse
I don't know, I just found that tool and start using it, I can't do anything more
@blackhawk_LA
Have you ever had any issues with the application? It's making a very important part of the system and if any errors would occur, it would be a catastrophe, which is why I am a bit apprehensive towards this program.
Make HBOOTS with it which have the same sizes as the HBOOTs from Alpharev, compare MD5, if they match, it's probably safe. Then you should be good to go to make a custom HBOOT with it
Never had any issue, I have used it very carefully to make at least 10 different custom hboots, and my phone is still alive
More statistics are needed to say it's completely safe but I think thalamus did a perfect job
I can say the program is very safe... have a dozen of custom hboots with it... no problem at all.
And looking forward to your INT2SD for sense..
here you go..
http://www.multiupload.com/N0B1RHYFPW
I'm very interested too!!! Thanks and keep up the awesome work!
When it'll be available I'll try it into my rom.
msandeep said:
here you go..
http://www.multiupload.com/N0B1RHYFPW
Click to expand...
Click to collapse
Thanks man, have you tested it?
You're not telling me everyone is too afraid to flash it, so everyone hopes someone else tries it to take the risk... -.-
Proz0r said:
Thanks man, have you tested it?
Click to expand...
Click to collapse
yes...its the one i use in my roms...and 40mb real data is really good to add apps like maps (that can updated) to the rom
with kind regards
Chaosz-X said:
You're not telling me everyone is too afraid to flash it, so everyone hopes someone else tries it to take the risk... -.-
Click to expand...
Click to collapse
I need my phone for the next couple of days and therefore cannot try it myself.
Alex-V said:
yes...its the one i use in my roms...and 40mb real data is really good to add apps like maps (that can updated) to the rom
with kind regards
Click to expand...
Click to collapse
Nice. Should real data be reduced to 5 MB or be left at 40 MB then, in INT2SD? Since it won't be needed for symlinks with it, I only see the point in having the 5 MB for the fsck log.
Word of advice.. Before flashing new hboot, use the alpharev downgrader. Otherwise you're screwed if the hboot turns out to be a corrupt file
Sent from my HTC Desire using Tapatalk
Thanks man, could you briefly describe what would happen if I would flash a corrupted HBOOT with and without flashing the downgrader prior?
Proz0r said:
Thanks man, could you briefly describe what would happen if I would flash a corrupted HBOOT with and without flashing the downgrader prior?
Click to expand...
Click to collapse
Well, AFAIK the HBOOT is also the white screen you get when you press Vol Down+Power, and it probably also involves the bootprocess normally, so I would say: broken HBOOT = a very nice brick.
Though I don't know what the downgrader is..
Yup, I know about that, I'm wondering about the downgrader too.
Proz0r said:
Yup, I know about that, I'm wondering about the downgrader too.
Click to expand...
Click to collapse
I'm always use the hboot-downgrade whenever I change hboot no matter whether the previous hboot is a lock hboot or an unlock hboot. It is always best to unlock the hboot before flashing a new one to be on a safe side.
Here is hboot with 427mb/system, 5mb/cache & 5mb/data as you mentioned here
Proz0r said:
Now, we need a volunteer to make the said zero-data HBOOT for 5 MB for /cache, 5 MB for /data and the rest for /system.
Click to expand...
Click to collapse
I tested the hboot by flashing it to my phone.. no problem to go to recovery, no problem to boot to bootloader. but I don't have any ROM which can fit a 5mb data partition to test. The lowest I ever go is 30mb/data.
Note: to change to another hboot.. use the hboot_downgrade first as this is a lock hboot.
Edit : Manage to squeeze the ROM to fit a 5mb/data ... so confirm the hboot works.