Related
These are entirely unchanged from the ROMs on the thread over in Dream land below (apart from one small fix for Exchange in version 1.0)
http://forum.xda-developers.com/showthread.php?t=534479
These are JAC and Drizzy's ROMs, not mine - all I've done is unpack the ROM, change one file in boot.img to make it work on a Magic, and then repack it all and sign it. So we'll forego the sigfile saying "if you like my work please buy me a Ferrari". However, this whole thing is a bit of a faffy operation and not something that's simple to set up (although is easy enough once you have everything you need in place) so I thought I'd share and save others the grief rather than hogging all the fun for myself.
These have come about because I wanted a Hero ROM, but wasn't entirely satisfied with the best one available for the Magic (Qtek's, IMO). It worked well, but the swap version dropped SMS messages sometimes, and the Compcache version was buggy, sluggish, and wifi didn't work.
JACxHERO seems to have a number of the same issues that Qtek has - dropped SMS messages (it seems that the lack of memory on the device causes the SMS/MMS process to die), and the Compcache version has broken Wifi. I said earlier on that I thought this version was oddly sluggish, but after setting up Compcache with backing swap I am loving it. By far the best Hero ROM on my own setup so far. No Wifi is a drag but I can live with it for now.
JACHeroSki 2.7.4.r2 in contrast is an older build, and one suspects they're using an older kernel; it has a working Compcache setup, but no conventional swap at all, and no multitouch. A good call if you have a slow SD card, can live without multitouch, and positively have to have wifi.
Bottom line as I see it:
Fast SD card? Use JACxHero v1.2. But you might lose SMSes (that said, no-one's reported any yet - I just worry about lack of memory issues)
Slow SD card but need wifi, and can live without multitouch? Use JacHeroSki 2.7.4 r2.
Slow SD card and want multitouch, or you insist on Compcache for other reasons, and not interested in wifi? Use JACxHero v1.0.
I personally am running 1.0 and after not being keen initially, it is growing on me and turning into a keeper. I only ever use wifi when at home and can do without it there, so it's not a problem for me.
----
JACxHero Version 1.2 - seems fast, but no Compcache
http://www.4shared.com/file/123726235/aa3ee695/jacxhero12-pn-magic.html
JACxHero Version 1.0 - Compcache, WiFi doesn't work properly. Works well if you enable backing swap and up the swappiness. See my user.conf on page 3 of the thread.
http://www.4shared.com/file/123729537/191c816a/jacxhero10-pn-magic.html
http://www.4shared.com/file/123821706/7250ac6b/jacxhero10-exfix.html (version with Exchange fix - I haven't tested this but it should be fine)
(version 1.1 didn't seem to be enormously different than 1.2; I did try it and have a working .zip but don't see much point uploading it)
JACHeroSki v2.7.4r3 - Compcache works by default, as does wifi. Note, though, there's no multitouch in the browser, which is a bit fail.
http://www.4shared.com/file/123798395/c61c220a/jacheroski274r2-pn-magic.html
NOTE THAT ALL OF THESE NEED THE USUAL THREE PARTITIONED SD CARD! i.e. fat32/ext2/swap
why have the v1.2 no compcache?
eljuego
As a note remember that JACxHero Roms dont have Compcache enabled by default.
The first post in the Dream Forum JacxHero thread tells you how to enable it - you need to edit the user.conf file, which i think is in /system/bin, can't remember right now.
It tells you which settings to change to get each combination of linux-swap and compcache
(BTW I know as it's working for me...)
Is it for 32A or 32B?
The rom for 32a or 32b ?
dazcox5181 said:
As a note remember that JACxHero Roms dont have Compcache enabled by default.
The first post in the Dream Forum JacxHero thread tells you how to enable it - you need to edit the user.conf file, which i think is in /system/bin, can't remember right now.
It tells you which settings to change to get each combination of linux-swap and compcache
(BTW I know as it's working for me...)
Click to expand...
Click to collapse
Good spot, I should have pointed this out.
gdskp said:
Is it for 32A or 32B?
Click to expand...
Click to collapse
32B - sorry, have now edited the thread title.
eljuego said:
why have the v1.2 no compcache?
eljuego
Click to expand...
Click to collapse
No idea mate. I suspect it was because of the issues with WiFi that they removed it until they could fix it.
One oddity I've noticed - the weather widget doesn't work. i select London as a city, it has a bit of a churn saying "loading weather", and no weather ever turns up. Clicking into the weather app workable fine.
Snap judgement - it's not as fast as Qtek's Rom. Just feels a bit "off". Maybe it's just me.
Loccy, the widget are buggy you sure you have ported the version 1.2 not the version 1.1 ? In version 1.2 the widget are fixed
edit : The widget have no border, but the rom is really fast probably the fastest rom i have tested !!!!
setenza01 said:
Loccy, the widget are buggy you sure you have ported the version 1.2 not the version 1.1 ? In version 1.2 the widget are fixed
edit : The widget have no border
Click to expand...
Click to collapse
Am pretty sure I called 1.2 the right filename but I was drowning in roms by the end so it is possible I got them mixed up. Can't check until I get home now though.
Either way I'm not too impressed - more bugs than Qtek and it is eating battery (although I have been hammerring the phone more or less constantly over the few hours I've been out). I think when I get home I'm going to build the final JacHeroski Rom and see how that goes, I believe that has Compcache running.
Dazcox, how are you finding this Rom? You've been running it longer than me.
Actually I've been using QTek today... but about to install this one will let you know
setenza01 said:
edit : The widget have no border, but the rom is really fast probably the fastest rom i have tested !!!!
Click to expand...
Click to collapse
Really? It's not a patch on Qtek for me. How fast's your SD card?
Am just downloading the final release of JacHeroSki - v2.7.4r2 - and will give that a try. I wonder if some of these new releases are a little too bleeding edge to be useful. If a worthwhile update.zip for the 32B emerges I'll post it here.
dazcox5181 said:
Actually I've been using QTek today... but about to install this one will let you know
Click to expand...
Click to collapse
I thought you'd done your own boot.img hacking and were running this already..?
I have a 8Gb class 6 sdcard and it's really fast more than the qtek rom
The 2.7.4r2 good idea, you make the port today ?
Loccy said:
Really? It's not a patch on Qtek for me. How fast's your SD card?
Am just downloading the final release of JacHeroSki - v2.7.4r2 - and will give that a try. I wonder if some of these new releases are a little too bleeding edge to be useful. If a worthwhile update.zip for the 32B emerges I'll post it here.
I thought you'd done your own boot.img hacking and were running this already..?
Click to expand...
Click to collapse
now I am, tried all the other builds myself
setenza01 said:
I have a 8Gb class 6 sdcard and it's really fast more than the qtek rom
Click to expand...
Click to collapse
Ah. I have the stock 2Gb Vodafone pile of ****e (plus an "8Gb class 6" that I bought from ebay that causes a reboot loop on my Magic ). That'd probably be the problem for me.
Right chaps, here's another one for you. This is JacHeroSki version 2.7.4 r2. Someone else here has done JacHeroSki previously*, but I don't think they ever updated to the final release. It's a little behind the curve in that JAC seems to have gone on to work with Dizzy, and in a different direction, and it won't see any more development. It has working Compcache, but lacks the fancy config scripts of later builds. If you want to play with your Compcache settings, you need to edit the a2sd script in /system/bin. No conventional swap or facility for one. I'd say this is pretty much where Qtek was trying to go with his Compcache ROM though:
http://www.4shared.com/file/123729537/191c816a/jacxhero10-pn-magic.html
Am not sure I'm going to stick with this, however. I've just seen in the thread on the Dream forum that you can get Compcache working in JacXHero 1.2 by nabbing the boot.img from 1.0, so I'll give that a go too. What I'd really like is a working ROM with Compcache and swap as a backup.
edit: * speak of the devil, it's just turned up on the front page of the threads, they did do the final release, but it was for 32A not 32B. Oh, and am very disappointed to find no multitouch in the browser.
Does texting work fine on this ROM?
bhav007 said:
Does texting work fine on this ROM?
Click to expand...
Click to collapse
Honest answer? I don't know. I got a couple of text earlier when running JACxHERO 1.2, and I was hammering the browser at the time (if icanhascheezburger.com isn't going to run you out of available memory, I don't know what is). But I think a definitive answer will have to come from people who text more than I. Unfortunately texts seem to be an issue on all Hero ROMs on the G1 and the Magic 32B, because of memory - hence why my goal is to get a build with as much "memory" as possible, even if most of it is swap and compcache sleight of hand.
Loccy said:
Honest answer? I don't know. I got a couple of text earlier when running JACxHERO 1.2, and I was hammering the browser at the time (if icanhascheezburger.com isn't going to run you out of available memory, I don't know what is). But I think a definitive answer will have to come from people who text more than I. Unfortunately texts seem to be an issue on all Hero ROMs on the G1 and the Magic 32B, because of memory - hence why my goal is to get a build with as much "memory" as possible, even if most of it is swap and compcache sleight of hand.
Click to expand...
Click to collapse
Am getting a boot loop after clean flashing this rom, any ideas why?
bhav007 said:
Am getting a boot loop after clean flashing this rom, any ideas why?
Click to expand...
Click to collapse
Which one? I found I had to completely clean off my ext2 partition before it'd run (coming from the Qtek ROM). Well, actually what I did was go into the recovery console and shift everything the Qtek had left in ext2 into another directory so that this ROM didn't get confused by it
bhav007 said:
Am getting a boot loop after clean flashing this rom, any ideas why?
Click to expand...
Click to collapse
If you were coming from Qtek's Rom, like I did, It does boot loop unless you clean your ext partition first, then wipe and reinstall the rom. It runs like a champ.
to erase the ext: boot into recovery
then from adb shell : run
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -rf /system/sd/*
then do whats stated above and no boot loop anymore.
PS: Loccy thx for the port.
PPS: to get this working with compcache instructions are in the first post of the dream rom
r1tman said:
If you were coming from Qtek's Rom, like I did, It does boot loop unless you clean your ext partition first, then wipe and reinstall the rom. It runs like a champ.
to erase the ext: boot into recovery
then from adb shell : run
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -rf /system/sd/*
then do whats stated above and no boot loop anymore.
PS: Loccy thx for the port.
PPS: to get this working with compcache instructions are in the first post of the dream rom
Click to expand...
Click to collapse
Am abit new with the terminologies here . Is there a guide I can follow to do the clean wipe. If i reformat my SD card to the necesarry partitions, it should work?
bhav007 said:
Am abit new with the terminologies here . Is there a guide I can follow to do the clean wipe. If i reformat my SD card to the necesarry partitions, it should work?
Click to expand...
Click to collapse
Should do, if you use the partitioning option on the recovery image, that'll wipe everything.
r1tman said:
PS: Loccy thx for the port.
Click to expand...
Click to collapse
De nada. All I did was just change a few files.
I'm done for the night now people. I did try to get 1.2 running with 1.0's boot.img, but ended up with a ROM that had no working wifi and no apparent Compcache. I figured that wasn't any better than 1.0 proper (which I'm going to give another crack and see if I can tidy up the Compcache settings to my satisfaction - I can live without wifi for now).
Hey Everyone,
I was just wondering that if we have a build to which we have BOTH RamHack kernels and the non-ramhack kernel, would there be a way to write a quick app or script to switch between them.
I guess we could store both kernels on the /sdcard and use a .sh script to flash_image between them, and reboot. I dont believe we can "hot-swap" between kernels, but if anyone knows a method, please respond here
If anyone can think of a better or more efficient method of doing this, I believe the whole community would benefit. Lets see if we can get something like this going....
zimphishmonger said:
Hey Everyone,
I was just wondering that if we have a build to which we have BOTH RamHack kernels and the non-ramhack kernel, would there be a way to write a quick app or script to switch between them.
I guess we could store both kernels on the /sdcard and use a .sh script to flash_image between them, and reboot. I dont believe we can "hot-swap" between kernels, but if anyone knows a method, please respond here
If anyone can think of a better or more efficient method of doing this, I believe the whole community would benefit. Lets see if we can get something like this going....
Click to expand...
Click to collapse
is it really that hard to boot into recovery and flash an update.zip?
I guess this is what you're looking for:
http://wootroot.com/blog/?page_id=1463
Ive seen it implemented on one other rom on xda, but can't remember which one ..
I am trying to make it easier and more efficient to switch between them. The uneek switch seems exactly what im looking for
I put together a version of uneeks script that can be flashed over SuperD or FastTest3.1.
ISSUE THOUGH, I cant get it to flash correctly, as I get the "update-script not found" error, even though I signed it and created the appropriate META-INF directories.
Here is the file, if anyone thinks they can fix it
Uneek Script (needs to be fixed\signed) : http://www.4shared.com/file/257220832/8b6c2940/uneek.html
Alpha release
Here is a very alpha release of a working port of uneek's RamHack/NonRamHack Toggle script ported to SuperD 1.10.2 by myself.
http://www.4shared.com/file/257253893/a61182a2/Uneek_Script.html
Instructions
extract zip file to /sdcard/uneek
Launch terminal
type 'su'
type 'sh /sdcard/uneek/install-uneek.sh' -should see no errors/messages
execute 'uneek' from /system/bin
Chose Ram option or JIT (not tested) options, all others prob dont work as I didnt modify them
reboot (you must do so to see effects take place, the kernel doesn't "hot-swap" :-( )
WiFi still works, CC & Swap work.
Issues
Switch breaks boot screen - not sure why as its stored in framework-res.apk, but still a bug
Leave me feedback\ improvements\whatever......
You still have to boot into recovery so you might as well flash a zip containing a rhack or noram-hack kernel.
I did some scripts based off Kings,
get gscript from the market ( donate if you like it )
and drop script into the gscript folder
with a little uname query you could have just one script, which switches based on the current running kernel
Edit: , actually if your kernel needs different kernel modules, then you will have to build in a copy ( which I suspect is where king got his rwsystem bit from , he copied from a script which updates the kernel modules )
Firerat said:
...<snip>...
my faster, much safer script
Code:
#!/system/bin/sh
if [ -e /data/kernels/full3d.img ];
then
if [ "`md5sum /data/kernels/full3d.img|cut -d " " -f1`" != "061284119d4ce46cbe0b585e0a8b2d0b" ];
then
echo "/data/kernels/full3d.img isn't the version I was expecting"
echo "I'm not going to flash it, as it may have become corupt"
exit 1
else
flash_image boot /data/kernels/full3d.img
echo "full3d Kernel Flashed..."
echo "Rebooting now"
sleep 1
shutdown -r now
fi
else
echo "Sorry, /data/kernels/full3d.img"
echo "seems to be missing....."
exit 1
fi
and yeah, I could never spell corrupt , is it one or two 'r's?
PS , the md5sums in the scripts are for the power off fix boot.img's I did for you guys
if you are wanting to switch to different boot.imgs then update the md5sum its checking for ( or remove the check )
Click to expand...
Click to collapse
If you have an engineering SPL installed, there isn't any need for the recovery partition, so might as well install your second kernel to the recovery partition. Boot normal = normal, boot recovery = ramhack.
lbcoder said:
If you have an engineering SPL installed, there isn't any need for the recovery partition, so might as well install your second kernel to the recovery partition. Boot normal = normal, boot recovery = ramhack.
Click to expand...
Click to collapse
and then have a script switch wlan.ko if incompatible
might as well switch with script and keep recovery for the odd times when you just want to quickly flash some zips from a list and not at your pc.
yeap, I've downloaded and flashed a rom while 'out and about' before.
Firerat said:
and then have a script switch wlan.ko if incompatible
might as well switch with script and keep recovery for the odd times when you just want to quickly flash some zips from a list and not at your pc.
yeap, I've downloaded and flashed a rom while 'out and about' before.
Click to expand...
Click to collapse
If the only difference is ramhack on one but not the other, then the wlan module will be fine -- there is NO REASON to be switching modules around with your kernel unless you use a kernel that is binary incompatible -- which means DIFFERENT VERSION.
lbcoder said:
If the only difference is ramhack on one but not the other, then the wlan module will be fine -- there is NO REASON to be switching modules around with your kernel unless you use a kernel that is binary incompatible -- which means DIFFERENT VERSION.
Click to expand...
Click to collapse
yeap, true but why not keep options open?
What if they decide they want to switch between binary incompatible kernels?
They would need to switch kernel modules anyway.
so get a script that works, and is simple to 'generate'.
I know you are trying to keep it simple, but you are actually needlessly setting up restrictions, which would then require a script to get around.
So why not use a script from the start, keeping the added convenience of a recovery image?
Firerat said:
yeap, true but why not keep options open?
What if they decide they want to switch between binary incompatible kernels?
They would need to switch kernel modules anyway.
so get a script that works, and is simple to 'generate'.
I know you are trying to keep it simple, but you are actually needlessly setting up restrictions, which would then require a script to get around.
So why not use a script from the start, keeping the added convenience of a recovery image?
Click to expand...
Click to collapse
If the only objective is to be able to easily toggle between ramhack and noramhack, then the recovery solution is (1) more reliable, (2) doesn't require reflashing NAND, (3) just easier to activate. With the reflashing approach, you have to either go into recovery and flash something, or pause-and-wait-and-autoreboot.
lbcoder said:
If the only objective is to be able to easily toggle between ramhack and noramhack, then the recovery solution is (1) more reliable, (2) doesn't require reflashing NAND, (3) just easier to activate. With the reflashing approach, you have to either go into recovery and flash something, or pause-and-wait-and-autoreboot.
Click to expand...
Click to collapse
did you ever read anything?
the script is as easy as a couple of taps, maybe home button, swipe tap tap.
( the key app here is gscript )
the flash is over very quickly, it checks md5sum first, it reboots.
you have to reboot with the recovery method anyway
recovery method restricts to binary compatible kernels, or require a script to switch kernel modules.
It is a no brainer imo, keep it flexible and keep the convenience of a true recovery.img
ok, so nand only gets what, on average 10,000 writes, is it really going to reduce its life in practice?
I like your idea, it will work but it just isn't as flexible as a script.
It is however more suited to an mt3g, offering duel ROM
I'm thinking mtdblock3 for one ROM, block4 for the other
errm, data , yeah might need to section that up somehow
any reason why a loopback can't sit on yaffs?
oh, and the ramdisk will need tweaking, obviously.
Sorry back on topic
Guys,
Either will work, if you do have incompatible kernels, and are having problems with scripts just let me know, I can probably make a script to generate a script for you.
1) Booting into recovery to change out your kernel image is totally unnecessary. You can do it via CLI with the flash_image command -- most every modded ROM already includes it.
2) Removing the recovery image just to put up a second install also seems somewhat overkill for devices as heavily limited on storage as most Android phones -- especially the G1.
3) I don't know about loopback on yaffs2 -- but I don't see any reason why it couldn't work.
4) It really seems to me that what we need is some kernel hacker who's familiar with hotswapping patched files -- a la ksplice ( http://www.ksplice.com/ ) -- to hack together a genuine, non-rebooting, RAMhack switch.
5) In all seriousness; what makes gscript superior to ASE ( http://code.google.com/p/android-scripting )?
IConrad01 said:
5) In all seriousness; what makes gscript superior to ASE ( http://code.google.com/android-scripting )?
Click to expand...
Click to collapse
Nothing, apart from its easy, it works and I haven't looked at ase yet
btw , you missed a p/ in that link
http://code.google.com/p/android-scripting/
btw , you missed a p/ in that link
http://code.google.com/p/android-scripting/
Click to expand...
Click to collapse
>_<
Pesky perniciously persistently phantasmagoric P!!!
I just keep on seeing people referring to gScript when ASE is a vastly more robust offering. It can run its scripts as daemons, run in background, run in terminal, it offers the same desktop shortcut option -- and more importantly, it can run Python, Perl, JRuby, Lua, BeanShell, JavaScript, Tcl, and shell scripts. (It loads the interpreters onto your /sdcard.) I've asked this question more than once before and I've never gotten an answer. It really seems like people just aren't aware of ASE -- which is kinda sad, considering the fact that ASE is still seeing continuing development whereas development ended on gScript sometime at the end of last year.
IConrad01 said:
>_<
Pesky perniciously persistently phantasmagoric P!!!
I just keep on seeing people referring to gScript when ASE is a vastly more robust offering. It can run its scripts as daemons, run in background, run in terminal, it offers the same desktop shortcut option -- and more importantly, it can run Python, Perl, JRuby, Lua, BeanShell, JavaScript, Tcl, and shell scripts. (It loads the interpreters onto your /sdcard.)
Click to expand...
Click to collapse
no, I am very interested in it,
I have been meaning to have a proper look at it for sometime
, I think I first saw it on @google
gscript is just handy,
unzip this, gscript from market,add, load, tick su, save , tap
But I promise , I will look at ASE
Firerat said:
and then have a script switch wlan.ko if incompatible
might as well switch with script and keep recovery for the odd times when you just want to quickly flash some zips from a list and not at your pc.
yeap, I've downloaded and flashed a rom while 'out and about' before.
Click to expand...
Click to collapse
Glad this is getting your attention....My script was pretty dirty anyways.
Anyway you can package it up in signed-zip format for easy access and modification of boot.imgs. Im having some issues with the update-script portion during the signing process tos keeping me from getting mine to be "flashable"
zimphishmonger said:
Glad this is getting your attention....My script was pretty dirty anyways.
Anyway you can package it up in signed-zip format for easy access and modification of boot.imgs. Im having some issues with the update-script portion during the signing process tos keeping me from getting mine to be "flashable"
Click to expand...
Click to collapse
still having update-script issues?
if you post it, I'll be happy to take a look for you
Oh, I've started a kernel switch script
I'll do some testing when its done and post it here for you
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.
Downloads here: http://www.neopeek.com/viewtopic.php?f=14&t=6507
Pretty much as stock as you can get it, if you want to create your own line of roms based off this.. Doesn't seem like that google supports these old roms anymore for the sake of server space (the sources seem to be deleted)
e334 said:
-Wipe everything (except dalvik-cache), data, rotate-settings, cache, and battery-stats! Wipe is very important! Superwipe V1 & V2 is fine to use.
Click to expand...
Click to collapse
since dalvik-cache is stored on /data , how do you go about not wiping dalvik-cache but still wiping data ?
wiping data will wipe
dalvik-cache
rotate-settings
battery-stats
since they are all stored on data
See: http://forum.xda-developers.com/showthread.php?t=637419
I understand what you mean, but the recovery "wipe dalvik-cache" function wipes more than it needs to (the dex files), and causes the rom to crash. This often occurs on 1.6 roms, but not in 2.1+.
can it be run on 2708? just no 3d?
For use with 2708 RADIO
See this post: http://forum.xda-developers.com/show...3&postcount=43
the link can not be opened
yes, it can run 2708, just flash kernel after install and it will work.
Link here: http://droidbasement.com/db-blog/?p=1563
e334 said:
See: http://forum.xda-developers.com/showthread.php?t=637419
I understand what you mean, but the recovery "wipe dalvik-cache" function wipes more than it needs to (the dex files), and causes the rom to crash. This often occurs on 1.6 roms, but not in 2.1+.
Click to expand...
Click to collapse
ahh I see
it is not a problem at install time, and is only a problem if lame symlink hacks have been used to redirect the dalvik-cache from cache to some other place, instead of using the dex to data only prop
you don't link any of your source as per http://forum.xda-developers.com/showthread.php?t=755506
well, dex never goes to /cache, so symlink hacks are not required, so wiping dalvik-cache with RA will not be an issue
problem doesn't exist
e334 said:
3D and/or camera WILL NOT WORK WITH 10 MB RAM HACK KERNELS!!!
Click to expand...
Click to collapse
Why is hw3d broken I know not.. least if you use a 2708 kernel.. you can use the original 10mb hack on the 2708 kernel with broken 3d but working camera but that seems silly.
You can go back to my 2708+ kernel thread and look up the old builds kernel.. in theory hw3d+camera will work unless you are having other issues with newer kernels and hw3d on the older rom.
FYI the old builds kernel has an alternative memory map that correctly maps hw3d for 2708, and maps 8mb for camera rather than the 5mb in froyo. (This is needed for the older libcamera's.. if you are re-building from source you may want to see if you can shim in the froyo libcamera)
ezterry said:
Why is hw3d broken I know not.. least if you use a 2708 kernel.. you can use the original 10mb hack on the 2708 kernel with broken 3d but working camera but that seems silly.
You can go back to my 2708+ kernel thread and look up the old builds kernel.. in theory hw3d+camera will work unless you are having other issues with newer kernels and hw3d on the older rom.
FYI the old builds kernel has an alternative memory map that correctly maps hw3d for 2708, and maps 8mb for camera rather than the 5mb in froyo. (This is needed for the older libcamera's.. if you are re-building from source you may want to see if you can shim in the froyo libcamera)
Click to expand...
Click to collapse
I think he is just getting things confused, like with the dalvik-cache wipe thing.
saying that problems exist when they don't
to clarify I'm reffering to this
Bugs so far:
-no 3d with 2708+ kernels because of the 10mb hack
Click to expand...
Click to collapse
unless I missed something and there are 2708 kernels which give extra 21mb ram?
from what I understood your 2708 kernels for older 1.6 builds gains 11mb instead of 14 with 2.2+ ( due to the required cam mem,as explained above )
and the 10 mb ramhack is completely different where memory allocated to the gpu is mapped to system instead, so it makes sense that 3d would not function (the gpu has no memory )
Effdee said:
unless I missed something and there are 2708 kernels which give extra 21mb ram?
Click to expand...
Click to collapse
I've been a bit too lazy to create/release it .. but in theory I could make a build with
15 + 5 + 8 =28mb on top of a regular 1.6 stock kernel by breaking both hw3d and camera
15 = 2708 ram changes (I say 14 elsewhere because newer froyo kernels have another ram hack to regain 1mb on all ebi0 radios/spls..
5 = camera ram
8 = EBI video region (hw3d)
This may need 1.6 but be interesting for the ram.. or those wanting more of just a embeded linux device
ezterry said:
5 = camera ram
Click to expand...
Click to collapse
the camera is interesting, the cam on the g1 is awful anyway so this ram might be put to better use as system ram.
I'm just wondering how much ram the cam would need for barcode (QR) scanning, as I would miss that ability.
might have a poke around myself and see what I find
ezterry said:
I've been a bit too lazy to create/release it .. but in theory I could make a build with
15 + 5 + 8 =28mb on top of a regular 1.6 stock kernel by breaking both hw3d and camera
15 = 2708 ram changes (I say 14 elsewhere because newer froyo kernels have another ram hack to regain 1mb on all ebi0 radios/spls..
5 = camera ram
8 = EBI video region (hw3d)
This may need 1.6 but be interesting for the ram.. or those wanting more of just a embeded linux device
Click to expand...
Click to collapse
omg ive been asking for this for a while now.. but nobody answered... would love to see this get done ) i wish i know how though.. :/
A good think would be 15 + 8 = 23mb with camera working and 3D broken
apps2ext seems to be broken in R1. Update soon.
Effdee said:
ahh I see
it is not a problem at install time, and is only a problem if lame symlink hacks have been used to redirect the dalvik-cache from cache to some other place, instead of using the dex to data only prop
you don't link any of your source as per http://forum.xda-developers.com/showthread.php?t=755506
well, dex never goes to /cache, so symlink hacks are not required, so wiping dalvik-cache with RA will not be an issue
problem doesn't exist
Click to expand...
Click to collapse
Hmm.. I see, although it has proved problematic for me to wipe dalvik-cache via recovery, so let's just leave it at that..
The source is obviously from google, as it is "AOSP" Android Open Source Project, which is from google.
e334 said:
Hmm.. I see, although it has proved problematic for me to wipe dalvik-cache via recovery, so let's just leave it at that..
The source is obviously from google, as it is "AOSP" Android Open Source Project, which is from google.
Click to expand...
Click to collapse
so you made no changes?
guess we are better off using an established 1.6 in the rom bible then
Some people prefer "pure" AOSP.
Sent from my HTC Stallion using XDA App
when it comes to donut it seems most prefer cm4 or superd
Whats great about this is that it gives users more options to choose from when selecting a ROM.
Sent from my HTC Stallion using XDA App
Effdee said:
when it comes to donut it seems most prefer cm4 or superd
Click to expand...
Click to collapse
Its the community's choice, I won't get butt-hurt if no one downloads my rom. I *know* that there are CM4 or SuperD roms out there, and I have tried them all, and they are good and fast, and I'm not ashamed to say that my rom is rather basic/buggy. If you want to continue trolling this thread to make yourself feel better, and make me look like an idiot, you are more than welcome to...
e334 said:
Its the community's choice, I won't get butt-hurt if no one downloads my rom. I *know* that there are CM4 or SuperD roms out there, and I have tried them all, and they are good and fast, and I'm not ashamed to say that my rom is rather basic/buggy. If you want to continue trolling this thread to make yourself feel better, and make me look like an idiot, you are more than welcome to...
Click to expand...
Click to collapse
trolling?
I just pointed out that your advice on not wiping dalvik-cache was contradictory as you said you *must* wipe data which will also wipe dalvik-cache.
I wasn't trying to make you look like an idiot. That would be a waste of time as you are doing that all on your own.
and if I *really* wanted to troll I would sign up to the competing forum you advertise in the op
I note you have asked for the thread to be deleted, which is probably a good idea as you violated the rules regarding source code and gpl
but would be a little unfair as the thread evolved, as a result of more miss information from yourself, into a think tank regards memory in the different kernels.
Hello,
I just try this on my Asus Transformer and it seem to make a big different on the tablet smoothness.
Before when I either wake up the TF or running allot of program, it would lag allot. After the ram tweak, I can said it does make a different. Even after I had almost fill my memory up to 90%, opening new programs and swapping screen is fast. Android does a decent amount of work and return my memory back to 150 (and up) with the OOM Kill task. It did not cure my SOD problem.
I am current running the ram optimization with no other ram optimizer or task killer.
Here my TF configuration:
Prime 1.5, Netformer 1.5 @ 1.5GHZ, SD Boost, and Script Ram Optimization. The link is below. Check it out and let me know how it goes on your transformer. As always, make a nano backup before the tweak.
Credit goes to Juwe11
http://forum.xda-developers.com/showthread.php?t=1111145&highlight=ram
Hi, if you're running prime 1.5 it has support for sysctl changes built in. By using /system/etc/sysctl.conf_default as a guide, simply put the desired settings into the /system/etc/sysctl.conf file and these will be applied on reboot by the 04sysctl init.d script that's already in the rom.
Or just use the script for the post above, it should work fine too.
nice work !
By the way, what is SD Boost?
can i use this tweak with the netformer kernel and stock rom?
amerikian said:
By the way, what is SD Boost?
Click to expand...
Click to collapse
The default settings for I/O is really slow when it comes to SD r/w. With SD Boost app on market, it'll tweak the I/O parameters on boot. If you're running Prime, then it is already tweaked for you and is permanent.
frosty5689 said:
The default settings for I/O is really slow when it comes to SD r/w. With SD Boost app on market, it'll tweak the I/O parameters on boot. If you're running Prime, then it is already tweaked for you and is permanent.
Click to expand...
Click to collapse
But those files can be applied on stock rom with root and Kernel netformer 1.5 or i can fall in some issue if i don't have prime 1.5 installed into TF?
devilpera64 said:
But those files can be applied on stock rom with root and Kernel netformer 1.5 or i can fall in some issue if i don't have prime 1.5 installed into TF?
Click to expand...
Click to collapse
Apps like that or SD Speed Increase should be fine with just a rooted device at minimum.
jonitfcfan said:
Apps like that or SD Speed Increase should be fine with just a rooted device at minimum.
Click to expand...
Click to collapse
and the RAM tweak? if i apply it with CWM on the stock rom (as i have done with wpa_supplicant to turn on Ad-Hoc connections) it's ok or i can have issues?
Here is what Roach2010 already has in the kernel by default:
[taken from the /system/etc/sysctl.conf_default file in PRIME v1.5]
NOTE: only the values that relate to what is in the script that the OP links to
Code:
vm.dirty_background_ratio = 5
vm.dirty_ratio = 20
vm.dirty_writeback_centisecs = 500
vm.dirty_expire_centisecs = 200
vm.swappiness = 60
vm.vfs_cache_pressure = 100
Here are the values to place into the /system/etc/sysctl.conf file that Roach2010 mentions above:
NOTE: these are the replaced values that relate to the script the OP links to
Code:
vm.dirty_background_ratio = 5
vm.dirty_ratio = 90
vm.dirty_writeback_centisecs = 1000
vm.dirty_expire_centisecs = 500
vm.swappiness = 50
vm.vfs_cache_pressure = 10
Looks to be similar to this app => https://market.android.com/details?id=com.rs.autokiller&feature=search_result
Roach2010 said:
Hi, if you're running prime 1.5 it has support for sysctl changes built in. By using /system/etc/sysctl.conf_default as a guide, simply put the desired settings into the /system/etc/sysctl.conf file and these will be applied on reboot by the 04sysctl init.d script that's already in the rom.
Or just use the script for the post above, it should work fine too.
Click to expand...
Click to collapse
Canny figure oot if yer sayin this is gonny help oor no?
I'm running Prime 1.5 and clemsys kernel v14b.
Globespy said:
Canny figure oot if yer sayin this is gonny help oor no?
I'm running Prime 1.5 and clemsys kernel v14b.
Click to expand...
Click to collapse
Everything about how much "snappier" it becomes is subjective.
frosty5689 said:
Everything about how much "snappier" it becomes is subjective.
Click to expand...
Click to collapse
Cheers. I guess it falls in the same basket as autokiller etc. Highly debatable subjects.
Just from my experience. When I have using the TF for 4 hours, I would have use over 10 programs. opening the android market up would take at least ten seconds or more. With the ram tweak, it open up in two seconds.
Opening all other programs there after are just as quick, as if you first start up the Transformer. Switching from screen to screen is very smooth. Where with out the tweak it would lag for a few seconds if I have allot of programs running.
My experience with the tweak vastly improve the usability of the tablet. Then again, it is subjective.
Did not know Prime 1.5 already have the SD Boost tweak? Can anyone recommend me a SD Card benchmark tools that can work on the microsd, SD, and internal storage? Been looking on the market, but not that work for all the storage slots in one tools.
Thanks
I am using the Clemsyn version 16 kernel. Can I use the CWM RAM Script?
Thanks a lot
I don't see why not. OC does help with loading up the program faster and durning usage. The ram tweak help with the multitasking part. It use subjective though.
Do a backup before tweaking it.
minhgi said:
I don't see why not. OC does help with loading up the program faster and durning usage. The ram tweak help with the multitasking part. It use subjective though.
Do a backup before tweaking it.
Click to expand...
Click to collapse
would a complete nandroid be necessary or could we just backup the files it alters?
adiliyo said:
would a complete nandroid be necessary or could we just backup the files it alters?
Click to expand...
Click to collapse
A complete nandroid backup would a safer bet in this instance, or any other instance for that matter, in case you can't boot into your TF for whatever reason. It'll also be more convenient than having to find out which exact files are being modified and to use a root file manager to manually copy and paste the current versions before flashing.
It seemed to help me on my tf. Surprisingly I didn't have anything in my sysctl.conf before I added this in.
brando56894 said:
It seemed tohelp me on my tf. Surprisingly I didn't have anything in my sysctl.conference before I added this in.
Click to expand...
Click to collapse
Same here...I don't have any sysctl.conf on my Asus..
I have asus eee transformer with kernel netformer 1.5 @1,5 ghz and prime 1.4 but after a succesfull flash wirh cwm i don't see the file in the folder and with the other metod i can't change permissions with root explorer, what have to do?*