Related
MghtyMax 1.9.1 "What a Feeling"
SIGNED VERSION NOW LIVE!!!!
THIS IS A CUPCAKE HERO ROM. AT PRESENT 1.9.1 IS STILL THE LATEST VERSION OF MGHTYMAX. IN MY OPINION, STILL THE FASTEST, MOST STABLE HERO ROM ON THE PLANET.
***NEWS***
I may be developing a "Legacy Edition" of MghtyMax, considering we are reaching the end of the road for the G1. It would essentially be 1.9.1 with minor tweeks, some graphical improvements, and some special goodies to celebrate life of a great phone. Kind of in the "feeling out interest" phase right now, so if this is something you would like to see, please respond. I'd also like to talk to some folks who are good with custom desktop wallpapers. Please contact me on Twitter if interested in working on this project.
Changelog:
1.9.1 - Added Flash support
1.9 Altered user.conf. Turned off Compache and went to straight linux-swap. Swappiness set at 60. This may be the FASTEST HERO ROM EVER.
Recommended linux-swap partition sizes:
G1: 128 MB Linux Swap
MT3G: 96 MB Linux Swap* (Not tested. If running laggy after rom settles try 128MB as well)
If you get the blurries on MT3G, use the blurries fix:
http://twistedumbrella.slackdev.com/Deport-1.0.zip
After the system settles, and everything is running nice and smoothly, shut down, reboot into recovery and flash this as a ROM. Don't wipe, don't remove partitions. Just flash the zip. Reboot, and no more blurries!
1.8:
*This IS Maxisma 1.8 with the following changes:
Brought back PEEP due to popular demand (as is in Maxisma's roms)
Include Backup for Root & Missed Calls apps, and a few added sounds.
Modded build.prop to allow use of T-Mo apps (My Account, My Faves)
1.7.1a:
Removed HeroLED. All LED's will work natively on MT3G, and on G1 all will work except *missed call notifications. Thanks to Maxisma's build.prop
*Included Anon's Missed Call. Allows for custom LED color and frequency for incoming/missed call notification, and missed call notification sounds. This app will be in your app draw, and it must be run and set up for missed call notification LEDs to work. MT3G users do not need to use this app.
Included Blackgin's "Backup for Root Users" (This version works with HERO rom's)
Added lots of sound files for Ringtones, Notifications, and Alarm.
This version has an edited build.prop so that the phone's model number displays as T-Mobile G1 for apps like T-Mobile's "My Account" Although this has not been tested on MT3G it should not cause any issues. Please report if there are and I will release a MT3G version of this rom.
Replaced boot sound and image files.
Removed HTC PEEP. (was causing problems for me, lots of FC)
Thanks go out to Maxisma of course for compiling the rom that I basically just tweeked a bit, and for allowing me to share it with all of you. Anon for his Missed Call app, Blackgin for "Backup for Root Users", HTCPedia and Rapidshare for hosting, everyone at XDA and the T-Mobile forums, JackCrackerMan for pointing me to the blurry fix, and of course all of you, the Android community at large.
***BEFORE INSTALLING PLEASE***
***THESE INSTRUCTIONS MUST BE FOLLOWED TO THE LETTER OR MGHTYMAX WILL NOT WORK!!!***
-If using "Backup for Root" uninstall any heroled app you may be currently running before backing up.
-Before flashing this rom, WIPE PHONE/FACTORY DATA RESET, WIPE/REPARTITION EXT AND LINUX-SWAP in parted.(I recommend ext4 for best performance, 128MB Linux Swap for G1, 96 MB Linux Swap for MT3G)
-After repartition and upgrade of ext partition, exit parted and PULL BATTERY. Make sure device is not charging or hooked up to USB and put battery back in and boot to recovery.
-WIPE/FDR Phone AGAIN FOR SAFETY. Too many people having issues with remnants of old roms interfering with new ones. PLEASE follow this procedure exactly.
- Flash Rom.
-When the new rom boots and you get to the homescreen, allow some time for the apps2sd to catch up.
- IMPORTANT!!! Run Market. Accept the ToS. Exit Market.
- Run "Backup for root users" (also in app tray) if you ran it prior to flashing this rom, and restore your files.
- Wait. Wait. Wait. Sit and watch the apps pop up in the tray. Wait some more. Look, they're dancing! They keep moving! Wait. Wait. Wait. Grass growing? Wait. Wait Wait. Wait some more and when they finally stop moving around for good, close the app tray and reopen it. If it scrolls like butter, it's done. If it's laggy, wait, wait, wait. DO NOT RUN **ANYTHING** During this process!!! You may get FC's, load screens, and just may end up doing a wipe and reflash. Give it time. It will take a while, but you'll be glad when it's done.
- Run "Missed Calls" app in the app tray and set up your led notifications for missed/incoming calls.
Feedback/suggestions appreciated!
*As with any rom, you flash this at your own risk, neither I, Maxisma, these forums, your wireless carrier, or any being, living or dead in the known universe (except for you) will be held responsible should your damage or destroy your device in an attempt to flash/use this rom in any way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MghtyMax 1.9.1 "What a Feeling!" ---> http://htcpedia.com/forum/showthread.php?t=918
Just in case folks prefer the RAMHack for some reason, 1.7.1a is still available for download.
MghtyMax 1.7.1a --->http://htcpedia.com/forum/showthread.php?t=918
"Just when I thought I was out... THEY PULL ME BACK IN!!!"
I just couldn't let 1.8 be it, with the problems I was seeing with lag. I am very proud of 1.9, and think it just may be the fastest Hero Rom setup yet. I hope you think so too. Thank you again for your support!
Please share your thoughts/comments on this topic here, or to my twitter at http://twitter.com/mghtyred
Thank you all again for enjoying this ROM!
Finally My First Post!!!!
This Seems Amazing, I'll Try This Out
anybody try it out yet? how is it?
going to give this a try brb
Since its a hero rom im guessing we will need a class 6 sd card right?
[email protected]@ said:
Since its a hero rom im guessing we will need a class 6 sd card right?
Click to expand...
Click to collapse
Because of the memhack Maxisma is using in the rom, no it's not required since linux-swap isn't really used, but recommended for faster app loading in apps2sd.
Working Great for me so far!
No FC's at all on the Mytouch.
Only one FC i got so far was the one when you search for a Contact, but mighty is already aware of that.
Other than that no problems so far.
Using it on the G1 and it blazing fast and holy sh** the LEDS work amazing!
Way to go Maxisma and Mighty!
If I'm coming from Max 1.7.1 do I need to wipe before flashing on my mt3g?
i followed directions and it boots up to mighty max screen and keeps booting to that same page. what next?
rizoh66 said:
If I'm coming from Max 1.7.1 do I need to wipe before flashing on my mt3g?
Click to expand...
Click to collapse
Absolutely. Follow the instructions to the T.
badaphooko01 said:
i followed directions and it boots up to mighty max screen and keeps booting to that same page. what next?
Click to expand...
Click to collapse
Clarification needed:
Are you getting a boot loop? Hero->HTC->MghtyMax->Hero->HTC->MghtyMax- etc,etc?
Or are you stuck on the MghtyMax screen?
mghtyred said:
Clarification needed:
Are you getting a boot loop? Hero->HTC->MghtyMax->Hero->HTC->MghtyMax- etc,etc?
Or are you stuck on the MghtyMax screen?
Click to expand...
Click to collapse
im sorry yes, its a boot loop
im wiping again and reflashing
Make all of this fit in 90 MB (death spl system) and I'll be impressed. I'll give it a try, though, maybe this one's worth my while, but the back of my mind is saying "Meh, another hero...)...
ok, let me tell you what steps i took before i flashed.
1.using Ra recovery. I wiped ext2 part
2. wiped/reset
3.repartioned fat/ext2/linux swap
4.upgraded to ext3
5.rebooted to g1 screen
6.pulled battery and removed sd card
7.copied rom to sd card
8.booted into recovery
9.wiped again
10.flashed rom
11.stuck in "might max" boot loop
mghtyred said:
Absolutely. Follow the instructions to the T.
Click to expand...
Click to collapse
Im sorry, I have one more question. Do I still need to partition my sd if im on the mt3g?
badaphooko01 said:
ok, let me tell you what steps i took before i flashed.
1.using Ra recovery. I wiped ext2 part
2. wiped/reset
3.repartioned fat/ext2/linux swap
4.upgraded to ext3
5.rebooted to g1 screen
6.pulled battery and removed sd card
7.copied rom to sd card
8.booted into recovery
9.wiped again
10.flashed rom
11.stuck in "might max" boot loop
Click to expand...
Click to collapse
Wow. That's your problem. Try it again using my EXACT process. I mean EXACT. If you do it EXACTLY as I posted it, you will have no problems. Start from the beginning and do it again.
rizoh66 said:
Im sorry, I have one more question. Do I still need to partition my sd if im on the mt3g?
Click to expand...
Click to collapse
As mentioned previously in the first post, in order for this rom to work on your phone, you need to follow the instructions I posted TO THE LETTER.
Yes you still need to partition your SD.
Read above to see what happens when you don't do exactly what is posted.
I have an extra 1GB class 2 or 4? SD card that I can use for this. And I want
to try it but I'm wondering.. is it good to be used as a daily driver? Is it as fast
or almost as fast as CM?
hey guys...
Congrats on Hero_over on the retirement, but you didnt have to mention my name in your post. I dont even consider myself a ROM developer, I just made a nice rom thats fast and stable for me, and I wanted to share. I dont want nor expect donations. I just love this community and I figure maybe someone out there would like this ROM. Its all love though.
i have this rom that i've made and have been using for the past two-three weeks. as i've been going along i've been tweaking it to my liking, and its very fast for me and i have no force closes. i wasn't even going to post this rom, but i thought maybe somebody out there would like it.
First off: G1 (HTC Dream) ONLY!!!! They say it works for mt3g, so you can try but I made it for the G1.
its based on dwangs 1.17.1 rom.
i edited the boot.img to include cyanogen's 4.2.12.2 kernel ( NO ramhack, so you can enjoy 3D games and apps)
i added the black statusbar
added nano so you can edit scripts in terminal on-the-fly
ext 2 through 4 supported
automatic a2sd!
added meltus audio hack v2r2
edited alot of pngs.. themed STOCK launcher with nexus tray
eclair contacts.apk
youtube 1.5.08
eclair calculator
compcache working...
userinit.sh support in /system/sd/
updated market
like i said i wasnt going to post it, but i thought maybe somone would like it...so if u flash it. let me know how it works for you.
REQUIREMENTS
DANGER SPL and UPDATED RADIO (THE NORM)
ext 2-4 partition
swap partition if you want.
PLEASE WIPE DATA BEFORE YOU FLASH!!!
Sidenote:I never usually wipe my entire ext partition before I flash any ROM. If you have access to a linux box and sd card reader I usually just delete the DALVIK-CACHE folder and APP-PRIVATE... although my APP-PRIVATE is always empty. I think what causes the crashing at boot when you don't erase the ext is the dalvik-cache. I leave my APP folder and my userinit.sh there, and when I reboot and it dexopts all of my apps and when it finally starts up all my apps are there from the beginning. NOW! You might have to reinstall some apps which might FC when you try to run it, but you can easily with a file manager and browsing to /system/sd/app/ and reinstalling.
But that's just me, I find that more convenient that reinstalling 111 apps one-by-one. If thats too much...
WIPE EXT PARTITION BEFORE FLASH.
ChangeLog-
Boogiedonut.5
Davilk-cache on sd card
Added latest WiredTether and WirelessTether, and the newer Terminal
Added transparent notification drop down
Fixed A2SD script to correctly run e2fsck
/system/sd/userinit.sh support, if not, then linux-swap if you have swap partition, or compcache if you don't
Reverted to stock Android bootsplash
boogiedonut.2
changed boot.img to use /etc/init.d as custom_init
turned on compcache by default ( 32mb disklimit ), if no /system/sd/userinit.sh present
changed status bar battery icon with default hero one
reverted back to nexus themed launcher, changed launcher background to darker png
edited phone.apk to replace all in-call screens with stock 1.6, (still eclair dialer)
added WIRED tether. works great, trust!
keep dalvik-cache on internal memory... ( i have over 100 applications on my sd, and have 29.50 mb free internal) - apps still on sd
BOOGIEDONUT.1
Added LatinIME.apk and reverted to working alarm clock
http://www.sendspace.com/file/ifr7oa
mirror: http://www.mediafire.com/?madu0lqmuyw
I'll also add the userinit.sh that I use for me it's makes it pretty fast, it just sets cpu max to 528, min to 384 Mhz. Compcache with 24 MB dize size, without swap partition. Backing swap with 16 MB mem limit, with swap partition, 30 swappiness. Just unzip then, adb push to /system/sd/.
Eclair STOCK theme'd launcher... I dont use advanced launcher, I'm pretty sure you can just "rm -r /system/app/Launcher" and then adb push advanced launcher to /system/app/ if you want to use that.
http://www.mediafire.com/?xkxmhmjytzy
cool, ill be trying this, im always open to new roms
Nice
Very Cool. I had done something similar myself when I got tired of 3d apps not working cuz of the ramhack except mine was too buggy for my liking. I will try it out and see how the speed compares with dwangs/cyan's (came from dwang to cyan and not diggin it ). I'll post back with some results!
EDIT: Just installed and started playing around with it. Everything seems good so far. One thing is that i got FC on installation. I figured out that eventually when i got past the FC and activated that either there was a problem during setup that the keyboard IME did not get installed or you forgot to include them. No worries. I just pulled them from another rom and installed and all is dandy. Gonna restore some apps and see how that goes and give another update when I can.
i just got this error
E: failure at line 50:
symlink toolbox SYSTEM:bin/start
Installation aborted
thephantom007 said:
i just got this error
E: failure at line 50:
symlink toolbox SYSTEM:bin/start
Installation aborted
Click to expand...
Click to collapse
Which SPL do you have...?
ups i cant see know cuz my phone wont boot im gonna look and try to install the SPl and the radio i didnt do that long time ago and what about the 1.6 android version
thephantom007 said:
ups i cant see know cuz my phone wont boot im gonna look and try to install the SPl and the radio i didnt do that long time ago and what about the 1.6 android version
Click to expand...
Click to collapse
If you had a backup, just restore from that and then you can check your radio version. Aside from that just make sure you wiped before installing.
It hangs on G1 screen, I have the latest radio and SPL installed.
songoku119 said:
Very Cool. I had done something similar myself when I got tired of 3d apps not working cuz of the ramhack except mine was too buggy for my liking. I will try it out and see how the speed compares with dwangs/cyan's (came from dwang to cyan and not diggin it ). I'll post back with some results!
EDIT: Just installed and started playing around with it. Everything seems good so far. One thing is that i got FC on installation. I figured out that eventually when i got past the FC and activated that either there was a problem during setup that the keyboard IME did not get installed or you forgot to include them. No worries. I just pulled them from another rom and installed and all is dandy. Gonna restore some apps and see how that goes and give another update when I can.
Click to expand...
Click to collapse
you are right i did not include a keyboard IME. Myself I perfer the HTC_IME and it can only be adb installed to the phone, instead of being build into the ROM. If you want I can include a new version with LatinIME.apk included.
yes i have a backup im gonna try to reinstall everything from the begining and i wipe everything
lethal said:
It hangs on G1 screen, I have the latest radio and SPL installed.
Click to expand...
Click to collapse
did you wipe before you tried to install. also is you ext partition empty?
i just got it running my friend im gonna see how it works and how fast it is and if im satisfied well u can have a six pack o maybe a 12 lol thank you
I want to try this but absolutely need the alarm to work, lol. Can you post an update fixing the alarm?
Perfect ROM!Just what i needed.thank you!
feedback
Can anybody tell me if its faster than dwangs 1.17.1. Also any fc and is everything working on this build. Thanks. Oh and hows the battery life on this build cuz dwangs draining alot.
Gerson2407 said:
I want to try this but absolutely need the alarm to work, lol. Can you post an update fixing the alarm?
Click to expand...
Click to collapse
i fixed it in the boogiedonut.1 update as well as missing keyboard
Extremely fast.
But... I have a couple of problems
My Pro's and Con's
Pros:
1.Extremely fast, no lag on the launcher at all.
2. It even speeds up dolphin broswer for some reason.
3. Fast, fast, fast.
Cons:
1. Did notice only three homescreens, had gotten used to 5 but no biggie. Maybe an update if demanded by enough members?
2. Some of my widgets (Including Paid:Weather Flip clock) get stuck on updating. All Mippin mobile widgets get stuck on updating too. Edit: fixed with a reboot, sorry about that mate.
3. Missing spare parts, can I just add that in myself?
I'm running on 96mb swap, did a full wipe, came from Latest Cyan .12 I think.
Gerson2407 said:
But... I have a couple of problems
1. Did notice only three homescreens, had gotten used to 5 but no biggie. Maybe an update if demanded by enough members?
Click to expand...
Click to collapse
Would like to see a 5-screens-launcher too.
Maybe you could integrate the Advanced Launcher (user can select the number of screens)
I'm for 5 screens, but against AdvancedLauncher. It has not been updated for a long time and seems to be slowing down the phone quite a bit.
I want to try this Rom but I cant download from sendspace. Plz upload it in mediafire.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After I have tried a lot of ROMs for the HTC Desire, and each one of them was perfect in another way, there was one kind of ROM I couldn't find: a ROM which is as small as possible, with Sense, and Gingerbread, and as clean as possible.
First of all: I am not an experienced developer, such as LeeDroid, or Coolexe (by the way, thanks a lot guys, loved your ROMs, and used each one of them without any issues, so kudos for your hard work!).
I'm just a 15-year old boy, who wanted to create a ROM which is as small as possible, but keeping Sense. If you have things to say like 'Loser, why would I flash this ROM, there are dozens of other ROMs', don't say anything at all.
However, if you have tips, questions, or think you can help me with this ROM, don't hesitate, and feel free to post!
About this ROM:
-Based on Gingerbread RUU from HTC for HTC Desire (Bravo)
-Bananacakes awesome new kernel (0.4), build by Sibere (0.4a), running on 1GHz, OC'able to 1.2.
-Su + Superuser + Busybox included
-Optional A2SD
-Removed a lot of stuff, resulting this ROM to be less than 120MB in size!
-Kept Sense, but some apps are removed (such as Stocks, Footprints, and Facebook, which you can download from the market anyway)
-Works on Stock HBOOT, and it should also work on Data++ or Bravo Sense (please post your experience with these 2 HBOOTs)
So, if you are looking for a lightweight version of Sense and Gingerbread, this is the ROM you're looking for. It may contain bugs, and I can not be held responsible for any damage. If you tell me about the bugs, I could try to fix them, but don't think I'm an expert with Android development, but I'll see what I can do.
To do:
-TrackballWake
-Perhaps create a special update.zip for some popular apps (filemanager, terminal, DSPManager)
-Fix the bootanimation (just a black screen at the moment, trying to find out how to fix it), the ROM boots just fine though
Removed:
-Apps you can install from the market (Facebook, Gmail, Flash, Flickr)
-Apps which have better alternatives (HTC Twitter)
-Apps which bugs a lot of users, even when they're not being used (HTC Stocks)
-Apps I simply don't like or use (Friendstream, Footprints)
-Apps of which I can't even come up with a reason why they would be installed by default (Polaris Office, if I'm right about the name)
-Live wallpapers which are pretty useless in my opinion (Smoke Wallpaper, Music Visualizations)
-HTC Sense Live Wallpaper, and the normal wallpaper is replaced
-Almost all ringtone/notification sounds, except for one in each category (the default ones)
Without further ado, here are the downloads:
Click here for the Non-A2SD build (version 1.5)
HBOOTs with 5MB cache won't work! Stock HBOOT or Bravo Sense HBOOTs will work fine, since they have a bigger cache (thanks Ronijs19!) For cMTD users: /system is 163MB in this build.
Click here for the A2SD build (version 1.5)
After you have installed the A2SD build, download a terminal emulator from the market and execute the following commands:
su
a2sd cachesd
Click to expand...
Click to collapse
Your apps and the Dalvik Cache will be stored on EXT from now on.
Changelog:
1.5
-Updated kernel to 0.5 by Bananacakes
-Restored original framework (= original skin)
-Restored fonts (Ubuntu fonts took more space...)
1.4
New build of Bananacakes kernel, by Sibere, running on 1GHz, OC'able to 1,2.
Bootanimation is either ANDROID now, or still a black screen, bit confused about that due to a lot of builds..
New font, Ubuntu.
Also removed alarm and notifications tones except the default ones.
1.3
-Removed LiveWallpapers (every LWP except HTC Sense)
-Removed Mode10Wallpapers (the HTC Sense LWP)
-Replaced dock (used the one from the Slate theme for Sense 2.1)
-Replaced the default Sense wallpaper for a custom one
-ROMs will be uploaded onto our own server from now on, which means: no waiting, and direct links (thanks DonUber!)
1.2
-Removed FriendStream (Twitter and Facebook were removed anyway, so Friendstream was unusable)
-Removed all ringtones except for 1 (saved about 2MB)
-Swapped the ucsh00d_c.ttf font for DroidSans.ttf, saving about 3.5MB
-Swapped the gcsh00d-hkscs.ttf font for DroidSans.ttf, saving about 1MB
-Removed some images in /media/resources, saved about 500KB, since the images are never used in Android anyway, AFAIK
-Modified updater-script with some ui_prints to inform about the progress
-Bananacakes new kernel (0.4) implemented
-Two versions from now on: with A2SD, and without A2SD. In the version without A2SD, you can insert any A2SD script you would like (both versions have init.d support). Recommended HBOOTs are Stock or Data++ or Bravo Sense. I have only tested Stock though, so if you use another HBOOT, please post your results.
1.1
-Init.d Script Support
-A2SD (Darktremor Script) installed by default, should be working
Click to expand...
Click to collapse
Thanks to:
-DonUber, a good friend IRL, who always gives me tips and ideas for improving the ROM, thanks a lot mate!
-Koush, for his Anykernel Updater!
-Bananacakes, for his awesome kernel!
-Ronijs19, for tips and testing different HBOOTs.
-You, and every other user who uses this ROM!
Enjoy, and don't hesitate to ask questions or report bugs!
If you like my ROM, and you don't have a DropBox account yet, consider creating one by using my referral link, giving both of us an additional 250MB: Click here!
This is the theme that is being used in Flux 1.3 and higher. If you download Flux 1.2, you won't have this skin!
Thx dude, gonna try it.
Which base did you use? Stock Sense GB Rom?
(what? I'm the first one? Yupiiiii)
Yes, this ROM is based on the RUU, released by HTC on HTCdev.com. It is an official Gingerbread, which was a bit slimmed down by HTC, and I removed even more bloatware.
EDIT: I'm trying another way to get A2SD working, give me half an hour
EDIT2: A2SD working, get 1.1 now from the first post! Wipe recommended.
Chaosz-X said:
Yes, this ROM is based on the RUU, released by HTC on HTCdev.com. It is an official Gingerbread, which was a bit slimmed down by HTC, and I removed even more bloatware.
EDIT: I'm trying another way to get A2SD working, give me half an hour
EDIT2: A2SD working, get 1.1 now from the first post! Wipe recommended.
Click to expand...
Click to collapse
Nice, i have removed friend stream widget (hate it).
If more people want to see other widgets/apps removed, I could make a list, and also remove that apps if there are enough people who would like to remove it. Aside from that, I'll also make a script soon which allows you to remove even more apps.
Thanks for your response!
Hello.
Always nice to see both new developers in here, and continued ROM development for the Desire.
May I ask, are there any benefits to this ROM for someone like me who hasn't S-Off'd and just has the stock partition?
Chaosz-X said:
If more people want to see other widgets/apps removed, I could make a list, and also remove that apps if there are enough people who would like to remove it. Aside from that, I'll also make a script soon which allows you to remove even more apps.
Thanks for your response!
Click to expand...
Click to collapse
Dude, can you upload some screen-shots of this ROM? how about performance and battery consumption?
williamj1 said:
Hello.
Always nice to see both new developers in here, and continued ROM development for the Desire.
May I ask, are there any benefits to this ROM for someone like me who hasn't S-Off'd and just has the stock partition?
Click to expand...
Click to collapse
If you don't have S-OFF, this ROM is perfect for you, if you want your phone to be as clean as possible, and need space for apps. This ROM uses A2SD by default, and in combination with a 512MB/1024MB EXT-partition, you don't have to worry anymore about the space for apps (a Desire without A2SD has only 137MB on NAND for apps).
Aside from that, this ROM is smaller than an original one. The GingerBread RUU by HTC was already slimmed down, and was 150MB. I removed even more bloatware, or unnecessary apps (such as HTC Stocks, which keeps running and bugs a lot of users), resulting in a ROM which is only 120MB. Even CyanogenMod is 90MB, so this ROM is really lightweight, since it has only approx. 30MB difference with an AOSP ROM.
In other words: no tweaks and modifications, just a ROM meant to be as stable and fast as possible, and without the bunch of apps most of the users won't use anyway, or they have alternative apps.
kmaq said:
Dude, can you upload some screen-shots of this ROM? how about performance and battery consumption?
Click to expand...
Click to collapse
The skin is the same as a normal Sense ROM for the Desire (so it's just as the stock ROM). The performance is really good, I haven't noticed any lag or anything like that yet, and it is running pretty stable until now.
I'll post tomorrow evening about the battery consumption, as the most recent build I made was about 2 hours ago, so I couldn't really test it yet.
I will make a skin though, and I hope to finish it in about a week.
Ok thanks....
So after boot and A2SD+ initiates, how much memory would I have free?
After you have installed the ROM, and have an EXT-partition, all your apps which you install will be placed on the EXT-partition. This means the available space is the same as the size of the EXT-partition.
My Desire said I had 80MB free after a flash, because the Dalvik Cache is still on the NAND of the phone. I also moved that to the EXT by installing a Terminal Emulator, and executing the commands:
su
a2sd cachesd
Click to expand...
Click to collapse
After which your phone will reboot. No matter how much apps you install now, your phone will always say you have 137MB available, because everything is being stored on the EXT-partition on your SD-card.
To use A2SD:
Boot in recovery, and partition your SD-card with an EXT-partition (512MB or 1024MB should be enough). Keep in mind partitioning removes all your data and formats your SD-card. Then copy the ROM ZIP to the root of the SD by using the USB Storage Function in recovery, and install it by using recovery. Then reboot, and A2SD will be enabled and your phone will boot in less than 5 minutes (only the first time, after the first boot it will startup much faster). During boot you'll get a black screen, it is completely normal. To use the EXT-partition for Dalvik Cache also, use the 2 commands I mentioned earlier in this post, and you should be ready
Chaosz-X said:
After you have installed the ROM, and have an EXT-partition, all your apps which you install will be placed on the EXT-partition. This means the available space is the same as the size of the EXT-partition.
My Desire said I had 80MB free after a flash, because the Dalvik Cache is still on the NAND of the phone. I also moved that to the EXT by installing a Terminal Emulator, and executing the commands:
After which your phone will reboot. No matter how much apps you install now, your phone will always say you have 137MB available, because everything is being stored on the EXT-partition on your SD-card.
To use A2SD:
Boot in recovery, and partition your SD-card with an EXT-partition (512MB or 1024MB should be enough). Keep in mind partitioning removes all your data and formats your SD-card. Then copy the ROM ZIP to the root of the SD by using the USB Storage Function in recovery, and install it by using recovery. Then reboot, and A2SD will be enabled and your phone will boot in less than 5 minutes (only the first time, after the first boot it will startup much faster). During boot you'll get a black screen, it is completely normal. To use the EXT-partition for Dalvik Cache also, use the 2 commands I mentioned earlier in this post, and you should be ready
Click to expand...
Click to collapse
I appreciate the efforts, but I am actually very experienced in that sense. I know perfectly well the A2SD commands and how it works All I wanted to know was the 137mb figure
PS: It isn't correct to say "No matter how much apps you install now, your phone will always say you have 137MB available". The memory will still go down even with A2SD+ installed and davlik cache to sd. It just doesn't go down as much.
Hi Chaos,
Why not just use a2sd script from Oxygen rom? I'm using it on all roms including CM7, MIUI. Leaving dalvik cache on nand with cm7r2 hboot. Much smaller then dt version.
Is your rom deodexed or odexed?
Some proposals:
-add new kernel from bananacakes (modified original GB Sense kernel, sources also available in post).
-Please add trackpad2wake also.
And kind request, what is removed or what is left inside?
Thanks!
Sent from my HTC Desire
williamj1 said:
I appreciate the efforts, but I am actually very experienced in that sense. I know perfectly well the A2SD commands and how it works All I wanted to know was the 137mb figure
PS: It isn't correct to say "No matter how much apps you install now, your phone will always say you have 137MB available". The memory will still go down even with A2SD+ installed and davlik cache to sd. It just doesn't go down as much.
Click to expand...
Click to collapse
You're right, it does go down, but since your apps, the dalvik cache and the cache are being stored on the EXT-partition, the NAND is almost untouched by apps I think. Not sure though, I don't know a lot about the A2SD scripts.
vr5411 said:
Hi Chaos,
Why not just use a2sd script from Oxygen rom? I'm using it on all roms including CM7, MIUI. Leaving dalvik cache on nand with cm7r2 hboot. Much smaller then dt version.
Is your rom deodexed or odexed?
Some proposals:
-add new kernel from bananacakes (modified original GB Sense kernel, sources also available in post).
-Please add trackpad2wake also.
And kind request, what is removed or what is left inside?
Thanks!
Sent from my HTC Desire
Click to expand...
Click to collapse
Removed:
-Apps you can install from the market (Facebook, Gmail, Flash)
-Apps which have better alternatives (HTC Twitter)
-Apps which bugs a lot of users, even when they're not being used (HTC Stocks)
-Apps of which I can't even come up with a reason why they would be installed by default (Polaris Office, if I'm right about the name)
-Live wallpapers which are pretty useless in my opinion (Smoke Wallpaper, Music Visualizations)
Trackpad2Wake is a function I also used a lot myself, so I will implement it soon
The new kernel by Bananacakes: if I see positive results by other users, and people like it, I will build it in.
And the ROM is deodexed
About the Oxygen A2SD script: I'll see what I can do, and maybe implement a feature to choose the desired script for A2SD.
Thanks a lot for your interest guys, I really appreciate it!
your rom is a perfect! dsp manger?
I'll see how much space it takes, and I'll either make a flashable ZIP to install it automatically, or if there are lots of people interested in it, I'll implement it in the ROM itself
Chaosz-X said:
You're right, it does go down, but since your apps, the dalvik cache and the cache are being stored on the EXT-partition, the NAND is almost untouched by apps I think. Not sure though, I don't know a lot about the A2SD scripts.
Thanks a lot for your interest guys, I really appreciate it!
Click to expand...
Click to collapse
You are very welcome. I will be sure to try this at some point in the next few days, thanks
Just one thing.... if you are really wanting to attract people in and get them downloading, I'm certain having a screenshot would help with that. And maybe update the OP with some of the information like the above ^, about what is removed etc etc.
Good luck Thanks
iltore said:
your rom is a perfect! dsp manger?
Click to expand...
Click to collapse
I don't think its implemented in the ROM itself, but now its possible just to install the CM7 mod as an apk file.....
(attached)
I have some work to do for school, which should be finished in about 15 minutes, and then I'll update the OP and add screenshots of the current interface.
In about 1 week I'll release an update with a really nice skin (in my opinion), and I think that will make the ROM a bit more unique
williamj1 said:
you are very welcome. I will be sure to try this at some point in the next few days, thanks
just one thing.... If you are really wanting to attract people in and get them downloading, i'm certain having a screenshot would help with that. And maybe update the op with some of the information like the above ^, about what is removed etc etc.
Good luck thanks
i don't think its implemented in the rom itself, but now its possible just to install the cm7 mod as an apk file.....
(attached)
Click to expand...
Click to collapse
everything works thanks thanks thanks to both!
Chaosz-X said:
N/A
Click to expand...
Click to collapse
Feel free to stick the APK of the DSP manager I attached in the OP if you wish ?
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 AOSP ROMs and their developers and users.
INT2SD thread for Sense ROMs
-
This is INT2SD, a new method of achieving D2EXT. It is meant for developers who wish to implement this functionality in their ROMs, since, due to the nature of the method, there is no way of making a flashable .zip which would be universal and work on most ROMs (yet?).
What differs this method from the old ways is that it uses no symlinks whatsoever.
INT2SD mounts an SD ext partition directly to /data, and this requires making changes to the boot.img, hence why universal flashable zips are not an option. The real userdata partition is mounted on /realdata and used for the e2fsck log.
Sorry for the link downtime, there were some critical bugs which I did not have time to fix. Therefore I took my time and added symlink checks, fixed fsck and more.
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
Instructions:
Pick your ROM featuring INT2SD, download it and flash it. You only need 1 ext2/3/4 partition. Due to /data/data being on the SD, a high-class card is recommended. Due to Gingerbread AOSP ROMs generally being pretty small, there's still quite a lot of unused space left on /realdata, to which I plan symlinking the /data/data directory so that INT2SD plays nice with lower-class cards too.
Remember to flash Google Apps, available here, if you opt for CyanogenMod.
All zips are signed for your convenience.
Flashing other kernels on top of these ROMs should work, though it hasn't been tested. If you try it, please let me know how it went.
EDIT: Seems there are people spreading false information on how this should be installed due to their own misunderstanding of my post. While I thought the instructions are simple enough, it seems they are too simple and do not describe the process. So, let me clear this up once and for all:
THE ROMS HERE ARE FULL ROMS THAT ALREADY HAVE INT2SD IN THEM.
THESE ARE NOT ADD-ON ZIPS.
Meaning, if you wish to use CM7 with INT2SD, just download CM7 from here. It is actually full CM7, along with INT2SD. So, the process is as follows:
Make a backup of all your apps
Download the full CyanogenMod 7 Stable ROM with INT2SD here
Do a full wipe
Flash it
Flash gapps
Restore your apps
Download:
Thanks to Ante0 for hosting the files!
INT2SD implemented in:
CyanogenMod 7.1.0 Stable INT2SD-M (Download)
CyanogenMod 7.1.0 Stable INT2SD-S (Download)
CyanogenMod 7.2.0.1 Stable INT2SD-S (Download)
GingerVillain 3.3 INT2SD-M (Thread | Download)
GingerVillain 3.3 INT2SD-S (Thread | Download)
Google Apps (not included in CyanogenMod)
It's compatible with Titanium Backup, here's how TB sees it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Current bugs:
-
Credits (alphabetically):
Alex-V - providing me with the first Sense ROM to implement INT2SD in
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.
Changelog:
v2.0.1
Small bugfix
v2.0
Dalvik cache is now by default on /realdata (the actual userdata partition) EDIT: Nope, not a good idea, thanks Droidzone!
Fixed fsck
Implemented lots of failsafes and small fixes
v1.0
First stable version
One version for ext2, ext3 and ext4 partitions
Implemented e2fsck (cheers Hacre!)
Reboot bug fixed (cheers Pulser!)
Real data partition is now mounted on /realdata (used only for e2fsck log)
v0.1
First beta version
Sretno!
nice work, I will try it !
This is very nice in theory and I hope devs notice your initiative. Just one question though, if ext is mounted as a /data partition, what happens to the real /data partition then? Is it merged with the ext or something else? Don't see an explanation in the first post. Thanks mate and keep up the good work. With no symlinks this could be somewhat of a speed booster for our roms for people that use higher class sd cards.
Cheers rayiskon and TomWan!
PlayPetepp, nothing happens, it simply isn't used, or even mounted. I wish I could merge it with the ext partition, but due to several issues this isn't possible.
Can /data then be mounted as /sdext? Just so there's no losses.
It can, but I intentionally avoided doing that so there was no confusion among users. Besides, I don't see what it could be used for anyway.
I could do a special version which does that, though
PlayPetepp said:
This is very nice in theory and I hope devs notice your initiative. Just one question though, if ext is mounted as a /data partition, what happens to the real /data partition then? Is it merged with the ext or something else? Don't see an explanation in the first post. Thanks mate and keep up the good work. With no symlinks this could be somewhat of a speed booster for our roms for people that use higher class sd cards.
Click to expand...
Click to collapse
Proz0r said:
Cheers rayiskon and TomWan!
PlayPetepp, nothing happens, it simply isn't used, or even mounted. I wish I could merge it with the ext partition, but due to several issues this isn't possible.
Click to expand...
Click to collapse
PlayPetepp said:
Can /data then be mounted as /sdext? Just so there's no losses.
Click to expand...
Click to collapse
Proz0r said:
It can, but I intentionally avoided doing that so there was no confusion among users. Besides, I don't see what it could be used for anyway.
I could do a special version which does that, though
Click to expand...
Click to collapse
you can change the hboot and make system partition bigger and data smaller..so you dont need to symlink system apps or libs....
Symlinking system apps or libs? There's no need of doing that in the first place
Proz0r said:
It can, but I intentionally avoided doing that so there was no confusion among users. Besides, I don't see what it could be used for anyway.
I could do a special version which does that, though
Click to expand...
Click to collapse
Devs would probably find a use for it since it's additional space on the phone. Imagine having all your apps and other stuff like boot/downanimation on /data and only dalvik, and I mean only dalvik, on /sdext (using your partitioning method ofcourse). That's my understanding of it so far.
-. typewrited .-
Alex-V said:
you can change the hboot and make system partition bigger and data smaller..so you dont need to symlink system apps or libs....
Click to expand...
Click to collapse
That's one of the uses I also had in mind. Could lead to a better responce of the rom in general.
-. typewrited .-
Proz0r said:
Symlinking system apps or libs? There's no need of doing that in the first place
Click to expand...
Click to collapse
I guess he was thinking of bypassing symlinking alltogether. Just like you.
-. typewrited .-
Yeah, I think putting just Dalvik on the real userdata partition could be done, that's a great idea, thanks!
Ah, you mean for the Sense ROMs which symlink stuff to the sd-ext! Yeah, the /system partition could be enlarged, even to the point where userdata is only a few megabytes in size since it doesn't even get mounted as is. I'll leave those things to someone else though, since I'm not great editing partition tables
PlayPetepp said:
That's one of the uses I also had in mind. Could lead to a better responce of the rom in general.
-. typewrited .-
Click to expand...
Click to collapse
PlayPetepp said:
I guess he was thinking of bypassing symlinking alltogether. Just like you.
-. typewrited .-
Click to expand...
Click to collapse
Proz0r said:
Yeah, I think putting just Dalvik on the real userdata partition could be done, that's a great idea, thanks!
Ah, you mean for the Sense ROMs which symlink stuff to the sd-ext! Yeah, the /system partition could be enlarged, even to the point where userdata is only a few megabytes in size since it doesn't even get mounted as is. I'll leave those things to someone else though, since I'm not great editing partition tables
Click to expand...
Click to collapse
Thats what i make since a half year or so...withthe 387mb system hboot and take the sd-ext with data2xxxx scripts as data partition.... lol to make the system faster without symlinks...
using nands data partition (internal) for dalvik is a bad idea...because it can be that you cant install apps but you still have free sd-ext because of data is full with dalvik because of internal
instead its better to move dalvik to sd-ext and use a odexed rom...so the dalvik (odex) from system apps and framework is internal...and only third party apps dalvik is extern...
this make system fly also whith data2xxxx scripts
anyway...good idea...i will try the script also
with kind regards
Alex-V said:
instead its better to move dalvik to sd-ext and use a odexed rom...so the dalvik (odex) from system apps and framework is internal...and only third party apps dalvik is extern...
this make system fly also whith data2xxxx scripts
Click to expand...
Click to collapse
PlayPetepp is one of the supporters of the odexed roms idea, i remember he mentioned it a while ago through pm i am too in a way, although it makes it a lil harder to customize stuff, i don't feel like using smali and baksmali everytime i want to do a battery mod or stuff like that despite it's advantages regarding speed.
nways, i think this script can be very helpful for future plans.
This is my idea for deodexed roms: /system as it is (cm7r2 hboot preferably), ext mounted as /data and data as /sdext. Now, all apps and other rom stuff that can't go to /system go to /data and only dalvik goes to /sdext. That way, there's still enough space for all apps and for dalvik because, let's face it, you'll hardly fill up 287mb with just dalvik. I have like 100+ apps on my phone and after moving dalvik to ext I got 160mb more space on /data so that's the size of dalvik.
Odexed roms are different but actually the same could be applied. Since /data gets bigger we can still use /sdext as a place for dalvik since it will be occupied with only installed apps dalvik and no framework/system dalvik (since it's odexed and everything goes to either /system or /data). Then free space would be evened out with apps going to /data where some odexed apps are stored. The only downside would be symlinking but there would be no need to change hboots. Am I making any sense here?
rayiskon said:
PlayPetepp is one of the supporters of the odexed roms idea, i remember he mentioned it a while ago through pm i am too in a way, although it makes it a lil harder to customize stuff, i don't feel like using smali and baksmali everytime i want to do a battery mod or stuff like that despite it's advantages regarding speed.
nways, i think this script can be very helpful for future plans.
Click to expand...
Click to collapse
i dont say anything bad...i know that he is a good man ..lol..i only say that this way of rom..speed things..is the way i do for around a half year..but he or michael..never ask me...maybe for tips or soo..
you dont need to deodex if you want change battery or so...first: UOT have a odex support...second: framework-res.apk and com htc resources apk is never odexed (also not in original htc roms
PlayPetepp said:
This is my idea for deodexed roms: /system as it is (cm7r2 hboot preferably), ext mounted as /data and data as /sdext. Now, all apps and other rom stuff that can't go to /system go to /data and only dalvik goes to /sdext. That way, there's still enough space for all apps and for dalvik because, let's face it, you'll hardly fill up 287mb with just dalvik. I have like 100+ apps on my phone and after moving dalvik to ext I got 160mb more space on /data so that's the size of dalvik.
Odexed roms are different but actually the same could be applied. Since /data gets bigger we can still use /sdext as a place for dalvik since it will be occupied with only installed apps dalvik and no framework/system dalvik (since it's odexed and everything goes to either /system or /data). Then free space would be evened out with apps going to /data where some odexed apps are stored. The only downside would be symlinking but there would be no need to change hboots. Am I making any sense here?
Click to expand...
Click to collapse
i was full with dalvik on data (internal) in the past...with older data2ext and whatever scripts...and also other people (i had the same thinking as you...once a day a person say..he cant install apps but he have free memory...it was a full data partition because of dalvik)...
but idea is nice...anyway dalvik is on sd-ext if i understand it right..so no limit of 2xx mb..or..?
yes symlink some files and you dont change hboot...but if you use data2xxx scripts with dalvik to sd-ext you dont need the data partition because sd-ext is data...so you can make the system partition bigger and dont need symlinks...so rom will be faster...mmmhh but this is maybe only my personal feeling...?!?
with kind regards...Alex
@Alex-V & other People here:
Hi guys,
I'm from the Nexus One forum, and I'm looking for a better script for my HyperSense ROM, based on the AceSMod007-v41 by michael.
I was trying to understand how can I modify my ROM having only dalvik-cache into an sd-ext folder... I have succesfully transferred all the stuff into /system with a modified HBOOT and so I have only a /data folder with some apps.
Obviously /data partition will have only around 70mb remaining for apps. So it's a must that I can transfer dalvik-cache to sd-ext.
How can I do?
Thanks!
Iperzampem0 said:
@Alex-V & other People here:
Hi guys,
I'm from the Nexus One forum, and I'm looking for a better script for my HyperSense ROM, based on the AceSMod007-v41 by michael.
I was trying to understand how can I modify my ROM having only dalvik-cache into an sd-ext folder... I have succesfully transferred all the stuff into /system with a modified HBOOT and so I have only a /data folder with some apps.
Obviously /data partition will have only around 70mb remaining for apps. So it's a must that I can transfer dalvik-cache to sd-ext.
How can I do?
Thanks!
Click to expand...
Click to collapse
what script you use at the moment...?
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4