Hey all,
Firstly I'll introduce myself as I'm relatively new around here. My name is Geoff (aka ravenge) and I'm a 22yo, IT Systems Support Manager in South Australia. Things that take up most of my time lately are Work, LANning and tinkering with my G1 that I've had since a few weeks after Optus released them in AU.
Since purchasing my phone, I've thoroughly enjoyed gaining root, and playing with the works of JF, TD, Haykuro and Cyanogen (to name a few). In a nutshell I've tried dozens of excellent ROMs thanks to these guys.
After much experimentation, I decided to move away from the shiny hero as I found it to be rather unreliable and relatively slow. I loved the HTC apps of Hr's Sapphire ports and I loved the speed of ION, then came Rogers, a fully finished, fully packaged rom made by HTC for Rogers in Canada. This meant that the HTC apps were stock and didn't need any porting, and more importantly the rom was designed for the G1 so it ran fantastically on my handset!
I loved the rom but, stock, I found it a little lacking in the features dept. Many people have repacked their own flavours of Rogers, but none fitted my desire for a 'complete' rom.
Since I rebuild my phone consistantly, I wanted a rom that has all the core applications that I use. firstly Apps2SD with ext3 had to be standard. I wanted superuser, terminal, mtt browser, and all the other goodies you've seen floating around the forums. I also wanted to change some options to AU standards so that i wouldn't need to do it later. An example was the Date format from MM-dd-yyyy to dd-MM-yyyy.
After much bug testing, and a LOT of help from awesome xda users such as Haykuro, Cyanogen, MarcusMaximus. I'm happy to have finally reached a stable build.
Starting with the original Rogers rom graciously provided by Haykuro here
History:
This Build is based on the Rogers rom provided by haykuro. I take no ownership for the original files, or any of the
modifications made (except where labelled otherwise).This Build would not be possible without the awesome works of: Haykuro,
JesusFreke, Cyanogen, TheDudeOfLife, and all the developers of the apps included. <3 your work!
To make it significantly easier to differentiate between my rom and other rogers repacks, I am nicknaming mine 'ramjet'.
r7 FEATURES LIST:
Optimisations from Cyanogen's 3.4.4 build:
Cyanogen's 2.6.27.25 kernel (anticipatory iosched, enabled multicast and max cpufreq at 528MHz)
boot.img
a2sd scripts - automatic A2SD using bind mounts
various other file system tools and libraries
AUTO Apps to SD - Standard:
As mentioned above, we're now using bind mounts. This means more stability and flexibility for filesystems. Apps to SD will automatically run for you with next to no setup required (apart from needing a partitioned SD card). If you don't have the partition, it will operate as per any build without a2sd (more or less)
Applications:
-All rogers specific apps removed
/system/app
+amazon mp3
+superuser
+Terminal Emulator
+Browser with multitouch (will possibly replace with HTC browser)
+bugreport.apk
+Google Voice Search
+Latest Google Maps
+spareparts
+updated Quick office to 1.0.1
+HTC Sync
+IM
pre-installed to /data/app
+Backup for root users
+apps2sd
+wifitether 1.51
+Fbook.apk
+Forecast Widget by Koxx
+mymaps 1.1.6
+smspopup 0.9.96
+linda file manager 1.2.10
+NetCounter 0.8
+Locale 0.611 beta
+Astrid 2.8.6
+TwitterRide 1.3.1
Cosmetics:
added images (my own)
in app/launcher.apk
transparent handle for app drawer (just because I prefer it)
in framework/framework-res.apk
battery depletion images with % included (cause I didn't like the battery icon going GREEN GREEN GREEN GREEN RED-FLAT)
NOTE this works off of modifications on the original images. As such, there are only levels at 0% 10% 20% 40% 60% 80% and 100%.
boot animation / audio copied from hero, cause its fancier and modified to include some build details and a picture of roger ramjet (note, Roger Ramjet the cartoon character is copyright of someone else, NOT ME)
3G:
A HTC lib was causing some problems for HQ youtube over 3G. Replacing with the lib from ION seems to fix it.
Audio Mod:
Max Volume mod by Meltus (V5.3+Bluetooth fix)
Dalvicvm:
dalvicvm from ION - cause it's shown speed improvements
Localisations:
Changed date format default to dd-MM-yyyy
Changed build.prop ro.product.locale.region=AU
Added Haykuro's APN List, modified by me to include the AU Carrier 'YES OPTUS' and many other AU carriers (that still need testing) http://forum.xda-developers.com/showthread.php?p=3891703
Added Optus voicemail config.
Changed default languages to en-AU for dialer and ime.
Click to expand...
Click to collapse
WHAT YOU NEED!
rooted g1 (duh)
I've just started using Cyanogen's recovery, it's great!
The Latest RADIO and SPL from Haykuro's here: ** Potential Bricking ** read up properly on this!
Apps2SD needs a Decent SD Card with an ext3 partiton. But a2sd is NOT a requirement to run this rom.
my rom: ravenge-ramjet-r7-signed-update-AU.zip
md5sum: f90b7db7768f6d431af079e97775e288
I recommend wiping, but it may not be necessary.]
The first boot will be very slow if you have lots of apps on your SD.
TODO:
APNS/Voicemail - Read up HERE
Homescreen customisation, such as TD's 5 home screens mod, when I can get my hands on the 'how to' doc.
Investigate ODEX for /system/app
FAQ:
Apps 2 SD: a lot of people have asked "Do I have to use apps to sd?" - you do not.
"if i had apps to sd before?" - thanks to cyanogen's handywork, it will automatically find what you have and set it up for you.
"can you port something from hero?" - probably not, the launchers / framework are different causing problems in most circumstances
"Do I need to wipe?" Probably. You may or may not need to wipe depending on where you've come from. You might be able to get away with just deleting cache (note cache may also be stored on your sd card from apps2sd and will need to be removed manually). If you get lots of force closes, chances are you need a wipe!
Has anyone made any themes? OPhone-V1.0 - ported by barakinflorida
P.S. I added a splash screen for those who know what it is.
If you have any problems, I'll do my best to support them. If you don't like my rom, use someone elses. If you have any useful suggestions, I'd love to hear them!
Regards,
ravenge
CREDITS:
This build was based on Haykuro's rogers.
In the past, Haykuro has been legendary at providing awesome HTC stuff ported from here and there, and a lot of the great roms that are around today are especially thanks to him.
If you would like to support Haykuro, you can buy him some nesquik!
I also got a lot of help, and used a lot of Cyaonogen's optimized android files and kernals from his latest builds. This helped me implement Apps2SD and get the build running nice and fast. For mor information about all of his great work, take a look here
Feel free to Buy Cyanogen a beer!
The AppstoSD2.apk Application comes straight from MarcusMaximus with an updated icon by me.
If you like this App please support Marcus by donating (aka purchasing it) in the Paid market.
MarcusMaximus and his Apps2SD thread is [http://tinyurl.com/n2ah4z]here.[/url]
As mentioned I have used Meltus's audio mod. The one I used is quite loud so you may prefer to check out Meltus' thread here and apply your own. Donate to Meltus here
I also believe that a lot of credit to certain parts of the android development should go to JesusFreke.
Go visit his Blog here and honour his work by donating here
The apks I included were from various sources and in general were extracted from other peoples builds, for example TheDude's 1.2b or Cyanogen or Haykuro's work. If I have forgotton to credit someone somewhere (which is pretty likely - SORRY!) Please PM me so I can give credit where it's due!
Click to expand...
Click to collapse
Previous versions:
r3 AU
r4 AU
r5a AU
r6 AU
Latest Revision Notes
UPDATES
Updated with r7
ravenge-ramjet-r7-signed-update-AU.zip
md5sum: f90b7db7768f6d431af079e97775e288
This patch includes some signifant changes to the guts of the build like the kernel and a2sd. If you experience problems, a wipe may be necessary.
+more useful apps
/data/app
astrid
locale
twitterride
+boot.img/kernel change to Cyanogen's 2.6.27.25 (anticipatory iosched, enabled multicast and max cpufreq at 528MHz)
This should fix a LOT of problems people were having, including the "coma" bug where the phone would run out of memory and wouldn't wake from standby.
a2sd now uses bind mounts (instead of aufs) allowing better stability and compatibility etc.
+replaced default google maps with newer one
+IM app. (let me know if I missed some files)
/system/app/IM.apk
/system/app/TmoImPlugin.apk
+replaced libhtc_ril.so with the one from ion. This should give '3G' and allow HQ youtube over 3G.
+boot.mp3 update
+localisation settings language default to en_AU for locale and dialer \customize\MNS\default.xml
+modified update-script (now closer to cyanogens) and
cleaned out xbin
Updated with r6
linky: ravenge-ramjet-r6-signed-update-AU.zip
md5sum:
a6c7e0eeb0145e5ca18e06e755a10d11
APPS
/system/app
+fix amazon.mp3
+google voice search (yay)
+spareparts
+updated Quick office to 1.0.1
+HTC Sync (W00t) seems to work too, which is a bonus
+IM (hopefully - someone please check)
/data/app
+FBook.apk
+updated Forecast Widget by Koxx - http://forum.xda-developers.com/showthread.php?t=511351
+added the google maps update 3.1.1 & mymaps 1.1.6 (to /data/app) uninstall it if you dont want it
+smspopup 0.9.96
+linda file manager 1.2.10
+NetCounter 0.8
Cosmetic
+new boot animation screen bkg (was bored lol)
Audio Mod
included Meltus' V5.3+bluetooth fix (if you prefer a different one, go see his thread)
default wallpaper switched
Free space:
with pre-installed apps
/data: 91904K total, 34336K used, 57568K available (block size 4096)
Without pre-installed apps
/data: 91904K total, 29760K used, 62144K available (block size 4096)
========================================================
Updated with r5a
ravenge-ramjet-r5a-signed-update-AU.zip
md5sum: 9d294c49d853ac0db67a9571d115898e
r5a: simply fixes a n00b mistake where I didn't upload the rom that included the new lines in the update-script.
r5:
+altered mount auto in a2sd to use busybox to avoid boot loop, allowing potential compatibility for other card types.
(though i'm still fairly certain that e2fsk and tune2fs are meant to convert the partition to ext3 file system anyway)
+Updated Meltus V4 (quality) loud mod. Sounds better than the V3 though not quite as loud.
+moved some apps to /data/app to clear up some system space and make it possible to update/remove them as normal if required. (this required an update to the update-script)
========================================================
Updated with r4
Since I don't have a lot of room left in my initial post at the moment (needs tidying) here is my changelog for r4
the major focus being Default APNs!
(thanks to shellite for having more foresight than me and getting his original files backed up!)
Changelog:
ravenge-rogers-r4-signed-update-AU.zip 09-06-2009
Code:
apns-conf fixed for AU and included more carriers (needs testing)
optus internet -works
optus mms -works
IDEAS -untested
IDEAS MMS -untested
Three -untested
Three MMS -untested
Vodafone Internet -untested
Vodafone MMS -untested
Telstra 3G EDGE GPRS -untested
Telstra GPRS -untested
Telstra 3G Databundle -untested
Telstra 3G Pay by time -untested
Vodafone NZ -untested
Vodafone NZ MMS -untested
voicemail-conf added for Optus AU. If anyone has more carriers to add, let me know
updated build.prop
I could use some help confirming/fixing any of the APNs I used, as I'm with OPTUS I don't have the opportunity to work with the other carriers. I'd love to hear from you.
I'll try this out, sounds good! Its good to see an Australian build pop up, now I won't have to deal with switching date formats every time xP
in case you didn't know.. it's Rogers without the D.. they're a mobile carrier in Canada.
sounds good.. but does this only work with ext3?? i have ext2
yingjai said:
in case you didn't know.. it's Rogers without the D.. they're a mobile carrier in Canada.
Click to expand...
Click to collapse
haha thanks, correcting now
robpet2 said:
sounds good.. but does this only work with ext3?? i have ext2
Click to expand...
Click to collapse
Theoretically, cyanogen's script converts the filesystem to ext3 to make it compatible, I'm yet to try it though. (adding it to my TODO list)
Edit: Apologies for the double post. didn't realise I couldn't delete unwanted posts.
holy moly the HTC start-up sound went through my ear drums~ I am still at the HTC screen but I guess it's gonna take a little longer than ususal due to the extensive inclusion of this and that I think I'm gonna love this thanks Ravenge~ I did a wipe and it works now... hey hold on... omg... My Apps2SD is working too!!... my ext2 was corrupted though I just kept on using the same sd regardless the reduced capacity... (Too busy these days) now it mounts back nicely...
wow... wow... this is insane... btw u have all the goodies working flawlessly.
man i told my slef i was not going to try rogers but...ok you talked me into to it.
Use busybox to mount -t auto
ravenge said:
NOTE: Originally this is supposed to support ext2 however, leaving mount -t auto caused a boot loop in my build. I imagine something is missing.
If anyone could provide some insight, this would be awesome. For the time being ONLY ext3 is supported.
Click to expand...
Click to collapse
The stock 'mount' binary doesn't support an auto mount. If you do a logcat, you'll see it's failing to mount the second partition and therefore can't access the dalvik cache, which is required for a full boot.
The fix is easy, just use 'busybox mount' instead of the regular 'mount'. You can even do this from an adb shell from inside the boot loop and you'll see the system finishes booting and comes online
Kinslayer81 said:
The fix is easy, just use 'busybox mount' instead of the regular 'mount'. You can even do this from an adb shell from inside the boot loop and you'll see the system finishes booting and comes online
Click to expand...
Click to collapse
Great tip, I'll give that a shot for future releases.
As I'm a lazy sod and dont want to mess around flashing my phone again tonight, (hopefully I didnt miss this in your first post) is your AU build based on EU firmware? (eg, no myfaves) ?
just downloaded your rom and about to flash it....hope all goes well............ya it does.....its great as of now will post regular feedback on this.....
thank you....
screenshots plz
sry 4 being a noob,but does anyone have any screenshots ?
looks almost the same as the other original build but anyway the sound is way too loud and the meltus sound thing isnt working can you build the update with the v4 best quality pre-installed thanks really fast I ran a script to odex all system apps and its running really fast love it
5 homescreen launcher.apk
props just flashed your rom, so far so good
Crazy Nice
i just went on ahead and flashed it.. and im lovin this its smooth and fast.. my apps 2 sd worked as a charm..the responsivness is accurate..so far what i notice is a big change in my opinion keep up the good work. would like to see more like a working flash player 10 or having your g1 play any type in movie format..
@ N3xt2N0N3
N3xt2N0N3 said:
5 homescreen launcher.apk
Click to expand...
Click to collapse
Doesnt work dude......says cannot install on this system......
the Rom is very stable and is very good......mixture of all available rom's but the genius has picked up the best among all and given us on one shot....
good work......thank u.....
Sorry to sound ignorant, but I've never used any Apps2SD modification.
Do I need an Apps2SD capable card to run this rom, or will it work fine without it?
Related
Hello XDA! Let's start off with a few thanks. Pof, Jscepi, Kyphur, Bepe, XDA for all the tools and knowledge. Cuboosh, Sirooga, Packetmangler, Tdusen, Drbowden, IDJ and everyone from my 3.02 thread for helping me work out the bugs. Without further ado:
3.53.DK.02 Based on CE OS 5.2.19213 (provided by incognitho)
Storage: 164.66MB Total, about 3MB In Use, about 162MB Free
Program: 85.32MB Total, about 31MB In Use (after soft reset), about 54MB Free
3.53.DK.01 Based on CE OS 5.2.19213 (provided by incognitho)
Storage: 165.79MB Total, about 3MB In Use, about 162MB Free
Program: 85.32MB Total, about 31MB In Use (after soft reset), about 54MB Free
3.51.DK.01 Based on CE OS 5.2.19209 (provided by incognitho)
Storage: 165.29MB Total, about 3MB In Use, about 162MB Free
Program: 85.32MB Total, about 31MB In Use (after soft reset), about 54MB Free
This rom starts where my older roms left off as far as "stripped down-ness" . My roms have AT&T connnection settings by default so no need to install and run HTC Connection Setup if you are an AT&T customer. Keyboard is Tilt layout so install KaiserKeyboard.cab attached below to change to Kaiser layout. Now onto the deets:
3.53.DK.02
- All Tweaks removed (cab included in rar)
- Removed Comm Manager (cab included in rar)
- Put back SIM Manager
- Clear Storage runs after flashing (no need to hard reset, but I still recommend you do)
- Overall more refined (I started from scratch on this one to work out some bugs)
3.53.DK.01
- starts where 3.51.DK.01 left off, nearly identical
- custsat.dll replace with no2chem's dummy file
- AUTD in CommManager replaced with 3G Toggle, cab also available below
3.51.DK.01 (4/24, radio not included)
- starts where 3.02.DK.05 left off
- removed help files from OEM_Lang_0409
- removed bmp's associated with help files
- removed DRM from OEM_Lang_0409 and SYS
- removed several dll's that are a part of Audio Manager and Streaming Player
- replaced NetCF 3.5 and SqlCe 3.5 with NetCF 2.0 and SqlCe 3.0 (for compatibility)
Stuff I noticed in 3.51:
- Addition of disptools.dll in OEMDrivers with new registry settings to go with it! I have no idea what this does and I'd love it if someone could enlighten me.
- AutoShortcut.exe and a shortcut to it that gets place in StartUp. Don't know what this does either.
- HTCCpl.cpl changed to MyCpl.cpl and mxip_HtcApps_translation.provxml reflects those changes. These cpl's control some items under "Settings".
- New bluetooth registry settings! not sure if this is related, but the blue light no longer turns on when you reset.
- What happened to the Program memory? 85.32 down from the usual 101.32.
Issues:
- Microsoft Voice Command versions older than 1.6.19209 will cause lockups.
- Typing area does not show with IM+.
- No video when using CorePlayer in QTv mode.
- I don't use TCPMP, but I'm guessing this still does not work either.
- Using cleartype in landscape mode causes text to disappear.
3.53.DK.02 Download Linkage:
http://rapidshare.com/files/117111999/3.53.DK.02___CABS.rar.html
see here for ringtone size limit fix http://forum.xda-developers.com/showpost.php?p=2227911&postcount=58
3.53.DK.01 Download Linkage:
http://rapidshare.com/files/114733628/3.53.DK.01.rar.html
http://www.4shared.com/file/47558388/89ca384e/KAISIMG_353DK01.html - mirror provided by sirooga
3.53 ROM Base (for cooking, download both parts):
http://rapidshare.com/files/115118417/3.53.DK.01-OEM-ROM.rar.html
http://rapidshare.com/files/115115367/3.53.DK.01-SYS.rar.html
3.51.DK.01 Download Linkage:
http://www.filesend.net/download.php?f=f7a49564aea29389db9d30afa52f22ee
http://www.megaupload.com/?d=5UH62WA2
http://rapidshare.com/files/110092950/3.51.DK.01.rar.html
3.51 ROM Base (for cooking, download both parts):
http://rapidshare.com/files/112782518/3.51.DK.01-OEM-ROM.rar.html
http://rapidshare.com/files/112779560/3.51.DK.01-SYS.rar.html
Radio Thread (1.65.20.29, Thanks to P1Tater):
http://forum.xda-developers.com/showthread.php?t=391714
Radio Linkage (1.65.14.06):
http://www.filesend.net/download.php?f=3ddce0d0b38d500a2108715d20a01677
http://www.megaupload.com/?d=SM6CWVNB
http://rapidshare.com/files/110097140/KAIS_Radio_Only_1.65.14.06_CustomRUU.rar.html
DO NOT INSTALL RADIO 1.65.17.10 IF YOU WANT TO DOWNGRADE IT LATER, I'M NOT EVEN GOING TO PROVIDE A LINK FOR IT, Thanks ATW !
I've started to mod my cabs to install to their own folders under \Program Files instead of \Windows whenever possible to keep the directory as clean as possible. 3.51 has 814 objects in \Windows after flash and opens wicked fast through File Explorer. Voice Command still seems to be in the grey area for posting so PM me for the my new 19209 version that installs to \Program Files\Voice Command. Help files are removed from my new cabs. Cabs attached below with more to come.
Update: There were some issues with 3 of my cabs and I just removed them from my first post. I will re-up them to my second post once I fix. I need to apologize to the 23 members that downloaded HTCQuickGPS 1_00_220821_00, the 17 members that downloaded MSInternetSharing 6.0 and the 15 members that downloaded MSRemoteDesktopMobile 6.1.
click me if you wanna give a me a little somethin'
4/24 - Fixed QuickGPS and InternetSharing cabs attached.
5/13 - Added ArcsoftMMSComposer 5_0_31_19.cab
Great, time to flash again...
Hung on the Windows Mobile 6.1 screen right after the flash. Had to hard reset to get past that point.
Loading up my apps now to see how it works.
akadonny said:
- I don't use TCPMP, but I'm guessing this still does not work either.
Click to expand...
Click to collapse
People might check THIS link to get TCPMP working on your ROM.
Have to admit that I haven't tried it with your ROM. There are at least 3 new ROM's available from the last two days. So I have to check out a lot
Great work btw on your new release! Keep it up!
akadonny, Did you make the APN/RIL changes on this AT&T build for us BBC users?
GSLEON3 said:
akadonny, Did you make the APN/RIL changes on this AT&T build for us BBC users?
Click to expand...
Click to collapse
No. Didn't have any requests for this so never thought to include it. Give me a few minutes and I'll make one for ya.
Edit: I just took a look at your instructions for "Multiple Data Sessions". Was about to make a new rom when I checked my registry. If the only change that needs to be made is:
<parm name="AGPSNVSetting" datatype="integer" value="5" />
then my rom is good to go for BBC. Happy flashing!
I just reflashed to the 3.02 because this one kept locking up on me. I don't me SOD either, I mean total lockup with the backlight on full brightness for 5-6 minutes...
I might try the multi connection ROM shortly.
idj1975 said:
I just reflashed to the 3.02 because this one kept locking up on me. I don't me SOD either, I mean total lockup with the backlight on full brightness for 5-6 minutes...
I might try the multi connection ROM shortly.
Click to expand...
Click to collapse
Did you install Voice Command? Using any version other than 1.6.19209 will cause your phone to lockup. Took me a while to figure this out, but found it installing 1 proggy at a time. Also, radio 1.65.14.06 is required.
akadonny said:
Did you install Voice Command? Using any version other than 1.6.19209 will cause your phone to lockup. Took me a while to figure this out, but found it installing 1 proggy at a time. Also, radio 1.65.14.06 is required.
Click to expand...
Click to collapse
no voice command, had the radio from your first post installed too...
*however* i didn't flash the radio first... i just realized that. i'll flash the radio & then flash the rom to see if it gets any better.
idj1975 said:
no voice command, had the radio from your first post installed too...
*however* i didn't flash the radio first... i just realized that. i'll flash the radio & then flash the rom to see if it gets any better.
Click to expand...
Click to collapse
I didn't know the order of flashing mattered? I flash my phone so much while testing my rom before release that I lose track of these things. I do however always do a master reset after each flash.
Anyways, let me know how it goes. I've been using this rom since yesterday without any issues.
akadonny said:
I didn't know the order of flashing mattered? I flash my phone so much while testing my rom before release that I lose track of these things. I do however always do a master reset after each flash.
Anyways, let me know how it goes. I've been using this rom since yesterday without any issues.
Click to expand...
Click to collapse
i think it might since it hung during startup before i put the radio on.
reflashed the radio & then the rom a little while ago. loading up my apps to see if i get locks again
Right, well I found out what's killing it.
BB Connect seems to be making it die, which makes me wonder if it's the data connection or BB Connect...
EDIT: Loaded Alex's "clean" ROM & it doesn't seem to have the same issue.
EDIT2: Can't get BBC to connect on Alex's ROM, so 3.02 it is for a while longer...
landscape mode - issue with text
akadonny,
Loaded this new ROM on my AT&T Tilt and notice a weird issue (didn't have this with the previous version). In regular mode typing text via the onscreen keyboard is visible. When I switch to landscape mode all text that can be typed disappear or it doesn't appear until you go to a new line. I noticed this when I went to enter my Personal Information.
Otherwise it's working fine for what I use on the device so far.
akadonny said:
DO NOT INSTALL RADIO 1.65.17.10 IF YOU WANT TO DOWNGRADE IT LATER, I'M NOT EVEN GOING TO PROVIDE A LINK FOR IT, Thanks ATW !
Click to expand...
Click to collapse
Hopefully there will be a fix for this soon. If not I will have to revert to plan B.
Mirrors
3.51.DK.01 Mirror
1.65.14.06 Mirror
idj1975 said:
Right, well I found out what's killing it.
BB Connect seems to be making it die, which makes me wonder if it's the data connection or BB Connect...
Click to expand...
Click to collapse
Sorry about that idj. I don't use BBC so I can't really test this for ya.
ecltech said:
Loaded this new ROM on my AT&T Tilt and notice a weird issue (didn't have this with the previous version). In regular mode typing text via the onscreen keyboard is visible. When I switch to landscape mode all text that can be typed disappear or it doesn't appear until you go to a new line. I noticed this when I went to enter my Personal Information.
Click to expand...
Click to collapse
I didn't understand you at first, but I think this may be by design. Just to be clear you are saying that you type using the on screen keyboard entering your Owner Information and when you switch to landscape the on screen keyboard closes until you tap the screen again. Is this right? I tested this and the on screen keyoard seems close under any app where you can type when you switch to landscape. I think I do remember the on screen keyboard staying open in landscape before.
AllTheWay said:
Hopefully there will be a fix for this soon. If not I will have to revert to plan B.
Click to expand...
Click to collapse
ATW, there are a lot of Kaiser/Tilt users out there including myself that owes you many thanks for catching this early.
sirooga said:
3.51.DK.01 Mirror
1.65.14.06 Mirror
Click to expand...
Click to collapse
woohoo! more mirrors!
Thanks much, Sirooga
Ok. So I loaded up the straight bloatware ROM & don't have any of the issues with an immediate lockup when BBC is installed.
Maybe when something was taken out it broke something else in another way that wasn't visible?
At least the ROM is decently speedy for a full on vendor one.
thanks for another release akadonny!
Seems to be running well. Does this have a differently sized pagefile?
Thanks,
PM
idj1975 said:
Ok. So I loaded up the straight bloatware ROM & don't have any of the issues with an immediate lockup when BBC is installed.
Maybe when something was taken out it broke something else in another way that wasn't visible?
At least the ROM is decently speedy for a full on vendor one.
Click to expand...
Click to collapse
At what point does it lock up? Installed the software to my Tilt, ran through the initial setup, soft reset when it told me to and now I have a blackberry tray icon. I click on the tray icon and I have several tabs. I've attached a few screenshots. The cab I used to install it is to big to attach, but I downloaded it from here.
packetmangler said:
thanks for another release akadonny!
Seems to be running well. Does this have a differently sized pagefile?
Thanks,
PM
Click to expand...
Click to collapse
I didn't change the pagepool on this one, but it looks like the 3.51 default it 28MB as opposed to the usual 12MB.
Hi All,
Here is my second contribution to the Android community, android2sd!
I tried to make the installation a bit more straight forward and the readme very verbose.
There is NO going into recovery and wiping of the Android to install this construct. (Of course you can if you want to have a clean slate to build from but it is by your choice only!)
Remove .zip from filename, then unrar (sorry to zip users, zip was too big) the package and copy the android2sd.sh install script to the Android say /data/local and make executable with something like chmod 0750 and copy the android2sd.img install image to the sdcard. (Detailed instructions are in the readme file.) Once the install is complete, you can delete both install files.
Execute the script {where ever you installed it}ie:
/data/local/android2sd.sh and follow the instructions.
Included are several of my scripts (updated from the ones in data2sd) and the rules still apply, adjust or remove as you see fit. The readme explains them all.
I have noticed an improvement in speed based on the install, but you can judge for yourself and tweak as you see fit!
The construct uses Overlay Profiles to overlay the Android system and thus any changes to the Android once loaded, are actually done to the overlay profile thus you have like a safe mode which is the untouched Android under the overlay.
Hope you find it useful!
Darkstrumn
Darkstrumn said:
Hi All,
Here is my second contribution to the Android community, android2sd!
I tried to make the installation a bit more straight forward and the readme very verbose.
There is NO going into recovery and wiping of the Android to install this construct. (Of course you can if you want to have a clean slate to build from but it is by your choice only!)
Remove .zip from filename, then unrar (sorry to zip users, zip was too big) the package and copy the android2sd.sh install script to the Android say /data/local and make executable with something like chmod 0750 and copy the android2sd.img install image to the sdcard. (Detailed instructions are in the readme file.) Once the install is complete, you can delete both install files.
Execute the script {where ever you installed it}ie:
/data/local/android2sd.sh and follow the instructions.
Included are several of my scripts (updated from the ones in data2sd) and the rules still apply, adjust or remove as you see fit. The readme explains them all.
I have noticed an improvement in speed based on the install, but you can judge for yourself and tweak as you see fit!
The construct uses Overlay Profiles to overlay the Android system and thus any changes to the Android once loaded, are actually done to the overlay profile thus you have like a safe mode which is the untouched Android under the overlay.
Hope you find it useful!
Darkstrumn
Click to expand...
Click to collapse
Damn man. Good work.
sounds interesting, what is this all about?
brilliant?!? I think.
So basically, this is a non-destructive method that enables us to run new roms on the G1 without flashing? Am I reading this right? If so... wow.
edit: or, erm... maybe not... i think i've been up too long. Gonna have to watch this thread to get a better grasp on this. interesting nonetheless.
Rename To RAR
Darkstrumn said:
Remove .zip from filename, then unrar (sorry to zip users, zip was too big) the package and copy the android2sd.sh install script to the Android say /data/local and make executable with something like chmod 0750 and copy the android2sd.img install image to the sdcard. (Detailed instructions are in the readme file.) Once the install is complete, you can delete both install files.
Click to expand...
Click to collapse
very interesting .. at first i failed to see this part as i'm sure many pay skip over the whole "rename to rar" thing - LOL - so this loads profiles from the SD to the phone
for anyone having trouble with the whole "rename" process try this:
http://files.lucidrem.us/jf/android2sd.rar
as i know windows with hidden file extensions does not allow a rename easily
So what exactly does this do? I see install instructions, but no description.
Overlay Profiles...
tr.slate said:
So what exactly does this do? I see install instructions, but no description.
Click to expand...
Click to collapse
Well,
I've worked up the natural progression to this XXX2SD business, and have made an Android2SD construct which can expand the Android similarly to the the previous constructs, but puts /system, /data and /cache on sd.
So let me explain the overlay thing:
An overlay profile is a snapshot of the Android file system, namely /system, /data, and /cache.
The initial profile is called 'android2sd' and is a snapshot of your android at the time of install, plus the file system structure as explained in the readme adding the mnt/ dir structure and additional scripts in bin/ (which you can remove or adjust as you need).
Typically I reckon folks would only have the one profile and under it your original Android. But you can create additional profiles and set them up however you like. The overlay is overlayed on top of the Android file system with any changes or edits to the system affecting the profile and not the Android under.
The effective change is that the /system /data/, cache are moved to the sdcard thus expanding them to however large your sdcp2 is; on a class 6 card also improving access time.
A second benefit is that the underlying Android is safe from alteration and can be booted into like a 'safe mode'. (It can also serve as the base for new profiles, or you can make new profiles from active overlays. These snapshots can serve as a form of backup, but that is a fringe benefit.
It cannot protect the Android from update.zip installs exactly, as those will modify the Android directly, but say you try a theme and it gafs your 'droid...you can reapply the firmware update to clean out the theme, then copy the desired profile back to the Android and restore the Android to the state of the profile. (I would recommend having a 'base' profile of the Android but not using that as an active profile which will thus serve as a backup) Note: To restore the Android as described above, you cannot restore using a profile with 250+ apps in /data as the Android doesn't have the space for it!
Originally I used unionfs for the overlays but it was too slow.
Hope that explains things here; the readme has far more detail.
I've gotta go, but if I see that I've been as clear as mud, I'll try to explain better when I have more time.
Hmm just out of curiosity: What are you using now? Bind mounts?
I got a little bit lost in setup, I am not sure if I had problems because I was using Cyanogens latest or something else but either way Im going back to JF to try this.
I installed it using the "-COMMIT" addition
But when I made it to installing/linking apps things wouldnt link
Maybe I will let a few other people try it first.
More info...
[email protected] said:
Hmm just out of curiosity: What are you using now? Bind mounts?
Click to expand...
Click to collapse
Yes. Originally it was to have a multi profile layered system using unionfs: union0 the ro base snapshot and union1 the rw profile containing the copy-on-write data. But as the tests went on, the unionfs was too slow to use for /data; Android is unforgiving of unresponsiveness and was ANR'ing the apps that didn't respond fast enough.
The faster bind mount means that union1 is now not used and union0 is rw.
The reason I wanted the union0,union1 path was that the union0 could serve as base and various profiles could be layered over any part of the file system granting "Lego" like flexibility in how the user could adjust their a2sdLoader.sh script (the android2sd loader which controls the overlay process).
You could have a pristine base and several "change" profiles that you layered to your liking and could change any sub layer to different effect.
While you still can under this paradigm, it is not as compact.
But the unionfs option is not completely done away with. It can still be used for the above layering but shouldn't be used for that apps and package system.
An example of the layering I'm on about:
The Android 0-layer which the base layer is a snapshot of.
The base layer is pristine (fully configured settings, but minimal apps loaded, maybe a particular base launcher layout and wallpaper).
A change profile containing my apps and package system
A change profile containing a version of etc with reconfigured bluetooth settings.
A change profile with a theme (manually installed, or snapshot to profile and restored to pristine)
Now I could take these 4 profiles and arrange several different setups:
'base' with all apps loaded, themed with custom bluetooth
'base' with all apps loaded, themed with normal bluetooth
'base' with all apps loaded with custom bluetooth
'base' with all apps loaded with normal bluetooth
'base' with all apps loaded
'base' themed with with custom bluetooth
'base' themed with normal bluetooth
'base' with custom bluetooth
'base' with normal bluetooth
...
Those would be set to serve as the ro union0 and the rw union1 which will hold the copy-on-write changes to the overlay (which preserves the sub layers)
You could have several more theme profiles and have a script that randomly chooses one at boot...
You could simply use the overlay to protect a favored configuration. Should anything untoward happen such as accidentally damaging the packages.xml file while experimenting with the system, you could simply delete the change profile, make a new blank change profile and the damaged files are undone.
The things one can do with the overlay concept are limited only by your imagination and need (and if they slow down app processing too much causing ANR's)
It vary well could if done correctly allow one to have multiple roms as profiles and switch them based on the selected profile, but I have yet to experiment on that...I reckon that is my next move! (Note that this path would have a high space cost as the roms are about 40MB zipped!)
brandenk said:
I got a little bit lost in setup, I am not sure if I had problems because I was using Cyanogens latest or something else but either way Im going back to JF to try this.
I installed it using the "-COMMIT" addition
But when I made it to installing/linking apps things wouldnt link
Maybe I will let a few other people try it first.
Click to expand...
Click to collapse
Taken from [Rom] CyanogenMod:http://forum.xda-developers.com/showthread.php?t=518851
"DO NOT RUN ANY OTHER APPS2SD APPLICATIONS ON THIS BUILD. YOU WILL BREAK YOUR SYSTEM. THEY ARE NOT NECESSARY BECAUSE THIS ROM WILL DO A2SD AUTOMATICALLY AND BETTER!"
The android2sd construct pretty much falls into the A2SD category and thus is likely the reason you had issues with the install.
My Android is based on JF 1.51... and thus your mileage will vary based on the rom you are using. I reckon with a rom derived from theh JF roms, the install may work as intended.
As I go into the next construct build process, I will see if I can't make it multi-rom compatible (to support multi-rom profiles) I'm sure it will take some time to do as I would have to use my actual Android to test with, but no worries!
Hope that helps a little. Sorry it's not better news though.
An excellent "misuse" of this concept would be to run ion (picking it for its speed and almost stock nature) with a hero overlay (picked due to known instability as we are still developing it) so that ion would serve as a "safe mode" for when you crash hero.
I have a spare phone if i crash this and a secondary sd for if that gets corrupted. Let me know if you need help testing.
twistedumbrella said:
An excellent "misuse" of this concept would be to run ion (picking it for its speed and almost stock nature) with a hero overlay (picked due to known instability as we are still developing it) so that ion would serve as a "safe mode" for when you crash hero.
Click to expand...
Click to collapse
Interesting thought, and if this could be done, I suppose it would be possible to have bluetooth working in ION while using a Hero overlay?
Request for feedback...
Hi All,
Those who've installed android2sd, how is it going?
Can you give some pros and cons of your experience so I may improve things going forward? (Hopefully no cons exists!)
I know that roms that already make use apps2sd will encounter issues as the apps2sd and android2sd function similarly and thus step on each other. I may be able to detect this condition and adjust for it going forward...we'll see.
Thanks in advance for your input!
Darkstrumn
LucidREM said:
very interesting .. at first i failed to see this part as i'm sure many pay skip over the whole "rename to rar" thing - LOL - so this loads profiles from the SD to the phone
for anyone having trouble with the whole "rename" process try this:
http://files.lucidrem.us/jf/android2sd.rar
as i know windows with hidden file extensions does not allow a rename easily
Click to expand...
Click to collapse
Thanks for putting the rar up, XDA wouldn't take the .rar and I didn't want to signup to a file-share site just yet.
And it being seemingly natural to make windows show file extensions, it didn't cross my mind to make a note about that.
Thanks again!
Darkstrumn said:
Thanks for putting the rar up, XDA wouldn't take the .rar and I didn't want to signup to a file-share site just yet.
And it being seemingly natural to make windows show file extensions, it didn't cross my mind to make a note about that.
Thanks again!
Click to expand...
Click to collapse
How come no one is trying this? It seems to me an excellent idea and would be really cool to boot mutipe roms if someone figures that out. I'm not testing this because I'm using appstosd and didn't want conflicts...but no one else with jf1.51 Rom is testing this idea?
Just curious
so wait a second. let me get this straight ... if I have a class 6 8gb card i might be able to install a hero build without rosie or widgets with the original launcher on the sd card that might actually come sorta, kinda, a little close to a speed that might be bearable? at least for like 5 minutes?
Can this be adapted to install bigger roms such as hero without the dangerspl .
XD
Ill try this with ion later tonight
wow this is beautiful work! now to test it!
Im trying so hard to understand this lol.. Correct me on my errors but from what i read this is my hypothesis on what i think this does..
This is like a apps2sd but with data and that type thing from the build we are using? And you Said this takes snapshots So we can create several profiles of the phone? Like for example have a profile with some apps loaded and another profile with all removed and be able to switch between them at will?
Hey everyone,
With the intro of BFS302 and Cyan's almost stable rom, I figured it is time to do some testing w/ user.conf files on CM 4.1.99. I feel this is necessary because I notice that after ~12 hours or so, the phone really starts to lag and I have a suspicion it has something to do w/ compcache.
I WAS using the stock CM 4.1.99 setting (24mb compcache), and now I am trying a user.conf that uses 64mb compcache w/o backing swap.
Anyone have any good settings\configs that have worked well for them AFTER SEVERAL HOURS OF USE?
The phone always seems to be quick after bootup and a taskkill, but after a few hours (possibly when compcache gets full) it starts to act sluggish
EDIT: Now that 4.1.999 is out, what is everyone using for user.conf settings?
EDIT2: Now that 4.1.9999 (and possibly more to come) is out, what is everyone using? I have added the corrected userinit.sh and my current conf file for reference if anyone wants.
zimphishmonger said:
Hey everyone,
With the intro of BFS302 and Cyan's almost stable rom, I figured it is time to do some testing w/ user.conf files on CM 4.1.99. I feel this is necessary because I notice that after ~12 hours or so, the phone really starts to lag and I have a suspicious it has something to do w/ compcache.
Click to expand...
Click to collapse
You are starting this testing thread on a ROM that has broken BFS and Compcache. This has been reportedly fixed by Cyanogen for the next update. Maybe it would be best to wait to try this when compcache is working efficiently again.
Oh, well thats good to hear. Hadnt heard anything about BFS or compcache issues yet. Anyway, guess we can continue testing once the new update comes out today.
Well to answer your question though, miketaylor00's user.def script has been working really well for me since I started using it...
http://forum.xda-developers.com/showthread.php?p=4334135#post4334135
Here's mine (Unix formatted, open in Notepad++). Running great on CM 4.1.99 for almost 2 days now w/o rebooting. Everything's still smooth and responsive.
Here are the highlights:
...
# 32MB cc with 24MB backing swap on Linux-swap partition
compcache_en=1
cc_disksize=32
cc_memlimit=24
cc_backingswap_en=1
cc_backingswap=/dev/block/mmcblk0p3
cc_swappiness=60
...
# swapfile off
swap_file_en=0
...
# swap partition off
linux_swap_en=0
...
# Defaults here
proc_cpu_en=1
scaling_min_freq=245760
scaling_max_freq=528000
sampling_rate=2000000
powersave_bias=200
up_threshold=40
...
I've also had good results with up_threshold set at 32. I'm also running the "extra memory" kernel hack, so that might be a contributing factor.
After messing with user.conf last night and all day yesterday, it seems the best solution is to just disable CC and enable linux swap or nothing at all until the update is released.
Thanks for your opinions and experiences. I have had 2 kernel panics\reboots today using stock settings, switched to a user.conf file I was using before to see if there is any difference. Lookin forward to the new release tonite though
bump because of new update
zimphishmonger said:
bump because of new update
Click to expand...
Click to collapse
Send me the default file and I'll send you my recommendation. I don't have time to load Cyanogen but I've been testing similar ROMs and I am testing the same BFS patch right now. I've found that BFS performs about the same with the same settings whether it is on Hero or Donut or Cupcake. I may not get you the optimal settings but it will be close and you can build from there.
The stock doesnt have a user.conf file, it just enables compcache 24mb by default (I believe). I usually use a slightly modified version of your user.conf file. I changed the cpu to 254760, and the swappiness to 60 (Just changed for testing).
I have a 64mb swap parition on a class 4 SD that is being used as a backing swap. I cant figure out if a backing swap is helping or not, as the lag happens after being booted for 8+ hours (usually overnight)
zimphishmonger said:
The stock doesnt have a user.conf file, it just enables compcache 24mb by default (I believe). I usually use a slightly modified version of your user.conf file. I changed the cpu to 254760, and the swappiness to 60 (Just changed for testing).
I have a 64mb swap parition on a class 4 SD that is being used as a backing swap. I cant figure out if a backing swap is helping or not, as the lag happens after being booted for 8+ hours (usually overnight)
Click to expand...
Click to collapse
Keep the 64MB swap and try the settings from JacHeroSki. See how that runs for a while. What are you using for your CC memlimit? Are you still having problems on the 999 build?
miketaylor00 said:
Keep the 64MB swap and try the settings from JacHeroSki. See how that runs for a while. What are you using for your CC memlimit? Are you still having problems on the 999 build?
Click to expand...
Click to collapse
Havent seen any issues on 999 build yet, but as I said, it happens after a while (when the compcache gets full and uses the backing swap, I assume). Anyway you can post the user.conf for jacherski? Is it different then xROM1.5r4 or r3?
Regarding CC_memlimit, I am currently using 24. Recommended?
zimphishmonger said:
Havent seen any issues on 999 build yet, but as I said, it happens after a while (when the compcache gets full and uses the backing swap, I assume). Anyway you can post the user.conf for jacherski? Is it different then xROM1.5r4 or r3?
Regarding CC_memlimit, I am currently using 24. Recommended?
Click to expand...
Click to collapse
Yes, BFS completely changes the game with the user.conf. Try this one out. The format might not be right so you will probably need to just copy the settings over. That's why I was going to have you send the original. I'm too lazy/busy to download and extract the CM file. But here is my BFS user.conf. I'm betting the upped CC Memlimit will probably help you out quite a bit.
Much appreciated, will 'convert' it and let ya know how it works out over the next day or so. Lookin forward to playing w/ the new xROM whenever that comes out
Zim, did you see my post in the Compcache vs. Linux vs. Stock thread? If not, check it out. It explains it a little better. I should start another thread on tuning BFS ROMs and post what I know. JacHeroSki is so fast that I'm using it as my daily ROM now. We just need to make it more stable and it will be perfect.
miketaylor00 said:
Zim, did you see my post in the Compcache vs. Linux vs. Stock thread? If not, check it out. It explains it a little better. I should start another thread on tuning BFS ROMs and post what I know. JacHeroSki is so fast that I'm using it as my daily ROM now. We just need to make it more stable and it will be perfect.
Click to expand...
Click to collapse
I agree, BFS really has given Android a whole new lease on life. So snappy. I would love to use JacHeroSki full-time, but I rely on a Bluetooth headset occasionally, so thats a deal killer....but I do have a switchrom image that I continually update to see whats new
Will check out that post, but you should start another thread about tweaking specifically w/ BFS. Seems to be gaining universal acceptance in the community, and it def changes the game around.
zimphishmonger said:
I agree, BFS really has given Android a whole new lease on life. So snappy. I would love to use JacHeroSki full-time, but I rely on a Bluetooth headset occasionally, so thats a deal killer....but I do have a switchrom image that I continually update to see what you new
Will check out that post, but you should start another thread about tweaking specifically w/ BFS. Seems to be gaining universal acceptance in the community, and it def changes the game around.
Click to expand...
Click to collapse
I'm really interested to see how those settings run on the latest Cyan. I have been wanting to tune it but I haven't had the time. That ROM is a lower priority for me because only a handful of people seem to want me to offer my suggestions on it. Cyanogen seems to want to stick to compcache only so I've left it alone for the most part.
copied and updated my user.conf file. Seems a lil more snappy right off the bat now. Will report back w/ long term results.
I currently use Cyanogen full-time, but I do occasionally have a habit of switching back and forth to xROM.
zimphishmonger said:
copied and updated my user.conf file. Seems a lil more snappy right off the bat now. Will report back w/ long term results.
I currently use Cyanogen full-time, but I do occasionally have a habit of switching back and forth to xROM.
Click to expand...
Click to collapse
Could you upload your updated user.conf file?
sacredsoul said:
Could you upload your updated user.conf file?
Click to expand...
Click to collapse
I am messing around w/ some Hero stuff at the moment, so I cant access my user.conf. Its pretty easy to modify miketaylor's previously released .conf, however. Ill attach my previous user.conf and you can just take the setting from miketaylor's attached one (above)
NOTE: This is old and has been replaced by Fresh Evo 1.0.1. I decided to start a new thread because this one was just too huge.
http://forum.xda-developers.com/showthread.php?t=726090
Click to expand...
Click to collapse
Geek For Me is proud to release:
Fresh Evo 0.5.3 for your Sprint Evo 4g
NOTE: Fresh Evo now assumes that you have NAND unlocked (part 2 of rooting). This means you are fully rooted and have write access to /system/ even when you are booted up. If you have not unlocked NAND protection then you should do so before flashing this rom!
This release was delayed for way too long due to various things out of my control (school, work, other projects, and a crashed hdd last weekend) so I'm happy to finally get it out!
I have been getting asked a lot when I'll integrate the new OTA update. I don't plan on including it until an RUU for it leaks out because it's a much better way to get files than to copy off patched ones. With that said Sprint pulled the update anyways due to it bricking people's phones. Haha. So just be patient and I'll update once it's out. Here's an analogy for you. You install Windows on a computer and then do all the windows updates. You then hunt down the random files that have changed and pull them off that computer, and just copy them over to another computer that hasn't had windows updates done, in an attempt to update it. While that may end up working, it is not nearly as clean as just getting an updated copy of windows that already has the updates on it and reinstalling it. THAT is why I don't plan on putting the OTA in until I have an RUU for it.
Do a data wipe! This version 100% requires one, even if you are coming from Fresh Evo 0.x. This should however be the last wipe required! It has also been reported that Clockwork Recovery is not wiping sd:ext properly. So if you do a data wipe (data, dalvik, cache, and sd:ext) and are still getting FC's or boot loops then you need to flash Amon's recovery and use it instead. In order to flash this rom you need to be rooted (unrevoked method doesn't count as root) to flash this. How To: Root Your Sprint Evo with NAND unlocked. Always make a nandroid backup, I can't be held responsible if something breaks, etc, etc.
Expect 1 loop at the very first boot! This is a side effect of the fixed vanilla lock. The very first time you boot up the phone it will load the lockscreen and then boot loop one time and then come up.
If it continues to loop then go here.
Go here to see all reported bugs: http://link.geekfor.me/freshevobugs -- if you are having a problem then check that page first, and read these release notes in their entirety!
Base: RUU_Supersonic_1.32.651.6
Changes from 0.3 to 0.5.3 (0.4 never made it to an official release):
Added Fresh Updater! Check the How To for information on setting it up and using it. This project has been on the back burner for months, and I'm happy to finally have brought it back and finished it up. Thanks to cyanogen and firefart as it's based on CMUpdater. It is built off of R657 which is the newest commit.
270 degree auto-rotation (you can turn the phone to the right or the left for landscape) -- Thanks to Optedoblivion for pointing me in the right direction
Fully fixed vanilla lock screen -- see screen shots. Use Fresh Updater to grab one of the vanilla patches to enable it. HTC's lock is enabled by default.
Landscape rosie (disabled by default!) -- see screen shots to see the issues with this. It is functional however it is definitely a hack. You will see some issues with using it. It doesn't look pretty, but it does work! Thanks to jschisurf for pointing me in the right direction on this one. NOTE: I have landscape rosie disabled by default! If you want to try it out then grab one of the patches in Fresh Updater to enable it. See the Fresh Updater How To for help with that.
Landscape settings.apk -- no problems here. Works fine.
12 new Rosie widgets. 7 that are available for our phone and 5 that aren't.
Profiles, ringtone, battery, call mom, coin flip, daily challenge, dice, notes, quick record, tasks, tip calculator, and today in history.
These are made by HTC and will only work in Rosie.
802.11N enabled (2.4 ghz only, not 5ghz) -- thanks to chuckhriczko!
Another brand new boot screen! -- thanks to wrx4memp
Updated DarkTremor apps2sd to 2.7 version 3 version 2. Version 3 was moving dalvik-cache to the sdcard even though it was set to not do so. Will upgrade to v3 when it's fixed. Thanks to tkirton!
Fixed wifi tether force close (still using the newest 2.0.5 pre 2)
Stock files have been resigned. This should prevent the need for any future wipes (not counting any major software changes by HTC/Sprint).
Updated launcher pro to 0.6.3
Updated google maps to 4.3.0
Updated estrongs file explorer to 1.4.2.2
Updated rom manager to 2.0.0.2 -- Note as mentioned above that clockwork recovery is currently having issues wiping sd:ext. So if you are having trouble with bootloops or FC's after flashing this rom then you need to use Amon's recovery instead. Additionally because of Fresh Updater, rom manager may not be needed anymore. VOTE BELOW on if you want me to continue including rom manager or not.
I have still chosen to NOT include adless browsing in my rom. I used adless browsing in all of my Hero Android 1.5 roms because it actually blocked ads from the browser. In Android 2.1 this functionality stopped working so I stopped including it. It was pointed out to me that while it doesn't block them in the browser, it does block them in apps (background data). The reason I am choosing to not include this is because as a developer myself, I feel that the authors deserve to get paid for what they do if you want to use their app. If you are choosing to use their free ad-driven application then I don't want to contribute to people blocking those ads and preventing the dev from getting paid.
Fresh Evo Features:
All APK's have been png optimized and zipalign'd
png optimize goes through every APK and losslessly compresses the png (picture) files without causing any type of visual change. This provides a smaller apk file size that loads faster. Each APK has then been zipalign'd. From Android's developer page: zipalign is an archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
While this does free up space on /system/ (as seen below) it is not done to make free space considering we have more than enough. It is done purely for a performance gain. Every day use of the phone will go smoother and stock applications will respond faster. The reason this works is because it has reduced the application file size as much as 50%, so they load in to memory faster and run smoother.
Additionally all applications in /data/ (even ones you downloaded) will be zipalign'd on boot if they need to be.
Not every apk takes png optimization + zip align well. I've done it on enough roms that I think I know which ones cause issues now, but if you are getting FC's on any apps (I can't test them all) then let me know and I'll get it resolved. Thanks!
Apps2sd enabled! Using Darktremor by tkirton.
Apps2sd takes all applications from /data/app and /data/app-private and moves them to a partition on your sdcard. It was originally created for phones that didn't enough enough space on /data/ to store a large number of applications. This has mostly been resolved on the Evo because we have over 400mb of space allocated to /data/. However for some people this isn't enough. Additionally if your apps are stored on your sdcard then you can do a data wipe and they will still be there (albeit settings will be lost, but you won't need to reinstall them).
You do not have to use apps2sd if you don't want to use it. If you just don't format your sdcard with an ext partition (leave it all as fat32 like it is from the factory) then apps2sd will stay turned off.
How to setup apps2sd on Fresh Evo and warnings about apps2sd
Battery optimizations
The stock mms.apk was possibly causing a wake lock. I have swapped it for a different one while I do some testing.
Raised VM kernel dirty page writeback frequency to 15 seconds. This wakes the phone up less often for background VM activity. Every single application in Android is technically running in a VM (virtual machine) so that's why this helps (as recommended by lesswatts.org).
Compcache 0.6.2 / Ramzswap enabled -- Thanks to toastcfh for compiling the modules! Compcache creates a RAM based block device (named ramzswap) which acts as swap disk. Pages swapped to this disk are compressed and stored in memory itself. Compressing pages and keeping them in RAM virtually increases its capacity. This allows more applications to fit in given amount of memory. This will only kick in when the stock memory (which the Evo has plenty of) gets low.
I have tuned the default to be 100mb ramzswap size with 40% swappiness
You can check compcache's use by opening an adb shell and typing: rzscontrol /dev/block/ramzswap0 --stats
ES File Explorer
ROM Manager -- Fresh Evo does show up as an available download in the free version of ROM Manager, so you can use it to update Fresh Evo right through your phone if you want.
Launcher Pro
Wifi Tether (free 3g and 4g wireless tethering)
Qik
Facebook moved to /data/ so that it can be uninstalled
Custom boot screen thanks to wrx4memp!
Added PowerTOP 1.11. From LessWatts.org: Programs can make your [phone] use more power. PowerTOP is a Linux tool that helps you find those programs that are misbehaving while your [phone] is idle. -- Compiled by cyanogen.
To run PowerTOP just open an adb shell and type: "powertop -d". It will scan for 15 seconds and then print out a report.
The first section will show you what % of time your phone spent running at what Mhz. In the screen shot above my phone was asleep so it was at 245Mhz the whole time.
The next section shows wakeups-from-idle per second. 50-80 would be normal. If you are in that range then you don't have a problem.
The next list is the top causes for wakeups. Compare your list to mine (I only showed the top 3).
All the way at the bottom it will have optimizations that can be made to lower power use. These changes can not be made to the rom itself, they must be made to the kernel. While other roms claim they made changes to the kernel, if they are using the stock kernel (if they aren't over-clockable then they are using the stock kernel) then they didn't. While there is a kernel source available to us, I have chosen to continue using the stock kernel until our official source is released by HTC for stability reasons.
I have chosen to NOT include adless browsing in my rom. I used adless browsing in all of my Hero Android 1.5 roms because it actually blocked ads from the browser. In Android 2.1 this functionality stopped working so I stopped including it. It was pointed out to me that while it doesn't block them in the browser, it does block them in apps (background data). The reason I am choosing to not include this is because as a developer myself, I feel that the authors deserve to get paid for what they do if you want to use their app. If you are choosing to use their free ad-driven application then I don't want to contribute to people blocking those ads and preventing the dev from getting paid.
See the official change log for all previous notes and changes! READ IT. It can answer a lot of questions if you are new to Fresh Evo.
DOWNLOAD: http://geekfor.me/new-release/fresh-evo-053/
RADIO: 1.39.00.05.31 (make sure you are running the newest radio if you are having problems with 4g)
New screen shots:
Older: screen shots:
Thanks to D/\SH at smartphonejunkie.com for the video! This is from the last version of Fresh Evo but he has some nice things to say.
Any plan to get this into ROM Manager? I find that app to be super convenient.
sph33r said:
Any plan to get this into ROM Manager? I find that app to be super convenient.
Click to expand...
Click to collapse
Yup it will be, I was just waiting to release so that the links worked.
Flashing now. The one thing I missed when leaving the Hero was fresh rom's. Thanks Flipz
flipzmode said:
Yup it will be, I was just waiting to release so that the links worked.
Click to expand...
Click to collapse
Awesome! I'm glad to see developers embracing that software.
Can't wait to try it, it sounds great.
Haha mad people must be downloading this your site is having issues establishing a database connection
Nvm seems fine now
Flashed with no problems. My Evo is Fresh!
Thanks Flipz
flipz just made my weekend!
Can we install directly over Fresh 0.1c Beta without a wipe?
Flashing now. Thanks Flipz
TheBiles said:
Can we install directly over Fresh 0.1c Beta without a wipe?
Click to expand...
Click to collapse
Shouldn't be a problem. And yea, the site is getting murdered. I just enabled super cache.
drbgotenks said:
Flashed with no problems. My Evo is Fresh!
Thanks Flipz
Click to expand...
Click to collapse
Hahahaha... I've been dying to say that!!!
Great to see you here flipz!
The beta version was running fine for me but I am excited to see the public version released.
For anyone not familiar with flipzmode's work, just flash this ROM and you'll be a fan!
omg I SO wish my Evo's battery isn't dead right now.
Awesome stuff. Was a huge fan of the hero roms. Now on to bigger and better things
The rom manager wouldn't let me flash. It didn't force close, it just said failed. To fix, I changed the setting in the very bottom panel to an older version, then changed back to the current one and it worked fine.
Flipz,
I love the idea with moving some of them to /data/app... which got me thinking... why not move almost everything there? That way everyone can uninstall whatever they don't like... or at least moving everything you can, over there to allow everything to still work.
Hey Flipz... I noticed that the Hero kitchen worked to push some of the .apk's back to the Evo. But some return an error..and fail.
For example the HTCFMRadio apk;
Can u clarify, when u say: adb shell mount /sdcardadb shell mount /systemadb shellcp /sdcard/fresh-removed-apks/WHATEVERAPP.apk /system/app
Like would "adb shell mount /sdcardadb shell mount /systemadb shellcp /sdcard/fresh-removed-apks/WHATEVERAPP.apk /system/app be all one command line? Or where should that be broken up at? I tried doing adb shell/mount /sdcard and it said "Usage: mount [-r] [-w] [-o options] [-t type] device directory..
drbgotenks said:
The rom manager wouldn't let me flash. It didn't force close, it just said failed. To fix, I changed the setting in the very bottom panel to an older version, then changed back to the current one and it worked fine.
Click to expand...
Click to collapse
Ditto. Did the the fix you suggested, and it's back in action.
Tenny said:
Flipz,
I love the idea with moving some of them to /data/app... which got me thinking... why not move almost everything there? That way everyone can uninstall whatever they don't like... or at least moving everything you can, over there to allow everything to still work.
Click to expand...
Click to collapse
Damn good idea, a second this if it could be done! It would be the most customizable ROM ever!!!!!
I started a new thread for this release because the other one was just too huge. I also want to apologize for how long this release took. Life is crazy.
Geek For Me is proud to release:
Fresh Evo 1.0.1 for your Sprint Evo 4g
NOTE: Fresh Evo now assumes that you have NAND unlocked (part 2 of rooting). This means you are fully rooted and have write access to /system/ even when you are booted up. If you have not unlocked NAND protection then you should do so before flashing this rom!
If you are coming from Fresh Evo 0.5.3 then just as I promised, no wipe is required. However if you are having problems then of course... wipe.
If you are coming from ANY other rom: do a data wipe! This version 100% requires one. This should however be the last wipe required! It has also been reported that Clockwork Recovery is not wiping sd:ext properly. So if you do a data wipe (data, dalvik, cache, and sd:ext) and are still getting FC's or boot loops then you need to flash Amon's recovery and use it instead. In order to flash this rom you need to be rooted (unrevoked method doesn't count as root) to flash this. How To: Root Your Sprint Evo with NAND unlocked. Always make a nandroid backup, I can't be held responsible if something breaks, etc, etc.
Expect 1 loop at the very first boot! This is a side effect of the fixed vanilla lock. The very first time you boot up the phone it will load the lockscreen and then boot loop one time and then come up. If it continues to loop then see above.
Go here to see all reported bugs: http://link.geekfor.me/freshevobugs -- if you are having a problem then check that page first, and read these release notes in their entirety!
Base: RUU_Supersonic_1.47.651.1 -- NEW!
Changes from 0.5.3 to 1.0.1:
Built off of the new 1.47.651.1 base!
Updated apps2sd to DarkTremor 2.7.5-pf4a
Updated Fresh Updater to 1.2
Mostly just visual changes. Turning the "themes" tab in to patches + themes + tweaks tab. More to come on that.
Make sure to Check the How To to setup and use Fresh Updater if you haven't before.
Added back FriendStream and Peep
For the beta versions of 1.0.x I had removed them, but I just found that too many people were having issues related to them not being there, so I've put them back in.
Made new boot.img containing the newest HTC kernel (789bf291)
Updated boot screen thanks to wrx4memp -- the "O" was made solid. While it wasn't wrong in the first place and was the font he used, we agreed it would be better to just make it solid.
Updated Launcher Pro to 0.6.7.2
Updated Rom Manager to 2.0.0.5
Updated Qik to 0.03.54
Check the download links below for an updated radio and wimax image.
If you are currently having problems with 4g then check the wimax.img download page below for links to help. If your 4g worked fine on Fresh 0.5.3 and then stopped working, make sure you are using the newest wimax.img and radio.img, and then do a full wipe and re-flash the rom.
If you are having problems with Google Maps then check the FAQ (linked below)
Click to expand...
Click to collapse
Standard Fresh Evo Features:
Fresh Updater! Check the How To for information on setting it up and using it. Thanks to cyanogen and firefart as it's based on CMUpdater. It is built off of R657 which is the newest commit.
270 degree auto-rotation (you can turn the phone to the right or the left for landscape) -- Thanks to Optedoblivion for pointing me in the right direction
Fully fixed vanilla lock screen -- see screen shots. Use Fresh Updater to grab one of the vanilla patches to enable it. HTC's lock is enabled by default.
Landscape rosie (disabled by default!) -- see screen shots to see the issues with this. It is functional however it is definitely a hack. You will see some issues with using it. It doesn't look pretty, but it does work! Thanks to jschisurf for pointing me in the right direction on this one. NOTE: I have landscape rosie disabled by default! If you want to try it out then grab one of the patches in Fresh Updater to enable it. See the Fresh Updater How To for help with that.
Landscape settings.apk -- no problems here. Works fine.
12 new Rosie widgets. 7 that are available for our phone and 5 that aren't.
Profiles, ringtone, battery, call mom, coin flip, daily challenge, dice, notes, quick record, tasks, tip calculator, and today in history.
These are made by HTC and will only work in Rosie.
Wifi tether (free wireless 3g/4g tether)
Stock files have been resigned. This should prevent the need for any future wipes (not counting any major software changes by HTC/Sprint).
I have still chosen to NOT include adless browsing in my rom. I used adless browsing in all of my Hero Android 1.5 roms because it actually blocked ads from the browser. In Android 2.1 this functionality stopped working so I stopped including it. It was pointed out to me that while it doesn't block them in the browser, it does block them in apps (background data). The reason I am choosing to not include this is because as a developer myself, I feel that the authors deserve to get paid for what they do if you want to use their app. If you are choosing to use their free ad-driven application then I don't want to contribute to people blocking those ads and preventing the dev from getting paid.
All APK's have been png optimized and zipalign'd
png optimize goes through every APK and losslessly compresses the png (picture) files without causing any type of visual change. This provides a smaller apk file size that loads faster. Each APK has then been zipalign'd. From Android's developer page: zipalign is an archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
While this does free up space on /system/ (as seen below) it is not done to make free space considering we have more than enough. It is done purely for a performance gain. Every day use of the phone will go smoother and stock applications will respond faster. The reason this works is because it has reduced the application file size as much as 50%, so they load in to memory faster and run smoother.
Additionally all applications in /data/ (even ones you downloaded) will be zipalign'd on boot if they need to be.
Not every apk takes png optimization + zip align well. I've done it on enough roms that I think I know which ones cause issues now, but if you are getting FC's on any apps (I can't test them all) then let me know and I'll get it resolved. Thanks!
Apps2sd enabled! Using Darktremor by tkirton.
Apps2sd takes all applications from /data/app and /data/app-private and moves them to a partition on your sdcard. It was originally created for phones that didn't enough enough space on /data/ to store a large number of applications. This has mostly been resolved on the Evo because we have over 400mb of space allocated to /data/. However for some people this isn't enough. Additionally if your apps are stored on your sdcard then you can do a data wipe and they will still be there (albeit settings will be lost, but you won't need to reinstall them).
You do not have to use apps2sd if you don't want to use it. If you just don't format your sdcard with an ext partition (leave it all as fat32 like it is from the factory) then apps2sd will stay turned off.
How to setup apps2sd on Fresh Evo and warnings about apps2sd
Battery optimizations
The stock mms.apk was possibly causing a wake lock. I have swapped it for a different one while I do some testing.
Raised VM kernel dirty page writeback frequency to 15 seconds. This wakes the phone up less often for background VM activity. Every single application in Android is technically running in a VM (virtual machine) so that's why this helps (as recommended by lesswatts.org).
Compcache 0.6.2 / Ramzswap enabled -- Thanks to toastcfh for compiling the modules! Compcache creates a RAM based block device (named ramzswap) which acts as swap disk. Pages swapped to this disk are compressed and stored in memory itself. Compressing pages and keeping them in RAM virtually increases its capacity. This allows more applications to fit in given amount of memory. This will only kick in when the stock memory (which the Evo has plenty of) gets low.
I have tuned the default to be 100mb ramzswap size with 40% swappiness
You can check compcache's use by opening an adb shell and typing: rzscontrol /dev/block/ramzswap0 --stats
ES File Explorer
ROM Manager -- Fresh Evo does show up as an available download in the free version of ROM Manager, so you can use it to update Fresh Evo right through your phone if you want.
Launcher Pro
Wifi Tether (free 3g and 4g wireless tethering)
Qik
Facebook moved to /data/ so that it can be uninstalled
Custom boot screen thanks to wrx4memp!
Added PowerTOP 1.11. From LessWatts.org: Programs can make your [phone] use more power. PowerTOP is a Linux tool that helps you find those programs that are misbehaving while your [phone] is idle. -- Compiled by cyanogen.
To run PowerTOP just open an adb shell and type: "powertop -d". It will scan for 15 seconds and then print out a report.
The first section will show you what % of time your phone spent running at what Mhz. In the screen shot above my phone was asleep so it was at 245Mhz the whole time.
The next section shows wakeups-from-idle per second. 50-80 would be normal. If you are in that range then you don't have a problem.
The next list is the top causes for wakeups. Compare your list to mine (I only showed the top 3).
All the way at the bottom it will have optimizations that can be made to lower power use. These changes can not be made to the rom itself, they must be made to the kernel. While other roms claim they made changes to the kernel, if they are using the stock kernel (if they aren't over-clockable then they are using the stock kernel) then they didn't. While there is a kernel source available to us, I have chosen to continue using the stock kernel until our official source is released by HTC for stability reasons.
I have chosen to NOT include adless browsing in my rom. I used adless browsing in all of my Hero Android 1.5 roms because it actually blocked ads from the browser. In Android 2.1 this functionality stopped working so I stopped including it. It was pointed out to me that while it doesn't block them in the browser, it does block them in apps (background data). The reason I am choosing to not include this is because as a developer myself, I feel that the authors deserve to get paid for what they do if you want to use their app. If you are choosing to use their free ad-driven application then I don't want to contribute to people blocking those ads and preventing the dev from getting paid.
See the official change log for all previous notes and changes! READ IT. It can answer a lot of questions if you are new to Fresh Evo.
Check the Fresh Evo FAQ here before you ask questions!
Fresh Evo FAQ: http://geekfor.me/faq/faq-fresh-evo/
Fresh Evo Reported Bugs: http://link.geekfor.me/freshevobugs
Fresh Evo Official Change Log: http://geekfor.me/evo/21/fresh-evo-official-change-log/
DOWNLOAD: http://geekfor.me/new-release/fresh-evo-101/
RADIO: 2.05.00.06.10 (make sure you are running the newest radio)
WiMax Radio: 25641
You must use the new WiMax radio with this rom. First flash the rom, and then the new WiMax radio. Read the release notes with the radio. This will NOT fix your phone if you are having problems with 4g. If you have been a Fresh user all along and haven't flashed any radios and stuff that weren't from me then this will work perfectly for you. If you do have any issues then just do a full data wipe and then reflash the rom. But if your 4g is already broken then follow the link in the release notes for the WiMax radio to get that fixed.
Click to expand...
Click to collapse
New screen shots:
Older: screen shots:
Reserved for once.
I'm gonna test this right now. ;D
Will this be on Rom manager?
downloading and testing now, im excited
I have the Rom manager with the clockworkmod recovery and I keep tryin to flash the recovery RA through the terminal from the market because I'm not to familiar with fastboot. I'm tryin to use the fresh update but it won't work with clockwork recovery. Can someone please help???
Currently downloading via Fresh Updater..
Love your roms Fresh keep up the good work
What he said - thanks man, we really appreciate it!
Issues With Wireless Tether...
Whenever I click the giant green wifi button the app force closes, anyone else experiencing this?
Flipz..... you've outdone yourself man.
This rom is super fast and stable... thanks again for the hard work....
smonme said:
Issues With Wireless Tether...
Whenever I click the giant green wifi button the app force closes, anyone else experiencing this?
Click to expand...
Click to collapse
you will need to remove it, then reinstall it.
dadoc04 said:
you will need to remove it, then reinstall it.
Click to expand...
Click to collapse
could you link me to the apk for reinstall?
smonme said:
Issues With Wireless Tether...
Whenever I click the giant green wifi button the app force closes, anyone else experiencing this?
Click to expand...
Click to collapse
I have had this a couple times on different builds. Go to applications, remove the wireless tether, go here h**p://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q= from your phone and it will reinstall, this has always fixed my issues with force close. You must uninstall first though.
Well that sucks... this rom has been in testing for a week and not a single person mentioned the wireless tether FC. haha. I'm sorry guys.
flipzmode said:
Well that sucks... this rom has been in testing for a week and not a single person mentioned the wireless tether FC. haha. I'm sorry guys.
Click to expand...
Click to collapse
mine wireless tether hasnt FC at all...
Tapatalk has tho... but it seems random. Im using the latest 1.69
Ive only seen it happen twice though.
Perfect!!!!!! On the Tether issue, reload binairies (sp) fixed my just fine.
Jetdr said:
Perfect!!!!!! On the Tether issue, reload binairies (sp) fixed my just fine.
Click to expand...
Click to collapse
For us noobs, how do we reload binaries? Getting fc issue too.
Also, I thought Peep was removed by default (again, I could be mistaken).
Just want to clarify one thing. Do we need to wipe the device if upgrading from Fresh 0.5.3?
In the release notes there you say you have to wipe first, which I did, and stated you wouldn't have to wipe again. Now this has the exact same statement in it. Just want to make sure I do the right thing.
Oh yeah, great ROMs. This is my first Android phone and you make it so much better.
Vivix729 said:
For us noobs, how do we reload binaries? Getting fc issue too.
Also, I thought Peep was removed by default (again, I could be mistaken).
Click to expand...
Click to collapse
Noob version :
Use a program like Uninstaller or Titanium Backup to uninstall Wireless Tether.
Search Market for Wireless Tether for root users. Install. Done.
Crackbone said:
Noob version :
Use a program like Uninstaller or Titanium Backup to uninstall Wireless Tether.
Search Market for Wireless Tether for root users. Install. Done.
Click to expand...
Click to collapse
Oh, so it's literally "reinstall". I thought there was some fancy adb command or something