Related
READ FIRST - I am no longer updating my ROMs - details.
If you're following the Hero scene, you'll know that I have published a custom ROM based on the 1.73.405.5 shipping ROM. I have a Vodafone Magic (32B) and a T-Mobile G1 kicking around (and HTC want my PR review unit Hero back!), so figured it would be cool to firstly build a really simple way for me to package my ROMs for all 3 devices, and secondly try and produce an update.zip that runs on all 3!
Well, the first step is here, I have the MoDaCo Custom ROM ready to install on your Sapphire 32B device (and a 32A version is available to test).
Things you should know...
- Contents are IDENTICAL to the MoDaCo Custom ROM versions detailed here.
- I have used cyanogen's kernel from 4.0.4 (big respect to cyanogen, he's doing awesome work!)
- Now compcache ready - use this script for a big performance boost!
It has room for improvement, but it runs really sweet already IMHO!
The download link (in update.zip format for flashing in the usual way via recovery image) is at: http://android.modaco.com/content/h...-modaco-custom-rom-hero-to-sapphire-32b-port/
I've packaged Cyanogen's 4.1.11.1 BFS enabled Kernel and wlan.ko as an update.zip too (see above thread) - nandroid backup before applying!
I've quoted some of my original Hero post here, so you know what you're getting. Enjoy!
P
Changelog
2.2.1 [32A only]
32A - fixed boot.img
2.2
Fixed SU and SD card bugs.
2.1.2
Updated busybox
Now compcache ready - use this script for a big performance boost!
2.1.1
Switch to Cyanogen's kernel
Fixed G-Sensor / Compass
Fixed sound
Unified Dream / Sapphire 32B download
2.1
Initial Release
me said:
This ROM is based on the Generic 2.73.405.5 release version of the 'new update' (together with my own optimisations) for the best possible performance! The ROM is now available in 2 versions - 'core' and 'enhanced' by popular request.
Included in both 'core' and 'enhanced' versions
- Rooted with 'adb remount' permission and superuser APK
- A2SD included (fully automatic - thanks cyanogen!) - create a EXT3 partition as your second partition to use. dalvik-cache remains on device. EXT4 is NOT supported.
- Added Jbed Java
- Added Spare Parts (run it and switch the 2 animation types to 'fast' for an even better experience!)
- Added Custom Locale for setting non english Locales
- Added android-wifi-tether 1.52 (props to the developer, this is a great app!)
- Added WMSM
- Added busybox 1.15 - tweaked such that 'get information' in Swapper now works as desired
- Added nano 2.09 - text editor for use in shell mode
- Added terminfo and settings to boot.img to allow nano etc. use
- Added tun.ko file (untested, please report on whether this is useful)
- Added files required for Debian linux
- Moved Quickoffice to data partition to allow easy uninstall
- Deleted 'Learn More' application
- Deleted Maps application - install from the Android Market to always stay up to date
- ROM now includes touch focus in Camera app
- ROM now supports shortcuts using BetterCut (and therefore I assume anycut!) in Rosie
- Silenced boot sound (it's still there and can be reactivated with a file edit)
- You can now check your MoDaCo Custom ROM (MCR) version from the about menu. It will display MCR2.0 (core) or MCR2.0e (enhanced).
- Fix for HTC Peep on Vodafone now available here!
Included in 'enhanced' version only
- Added Business Card Scanner
- Added 'Plurk' client
- Added WAP browser
- Added Chinese IME
- Restored Maps app (for users who cannot install it from the Market)
Click to expand...
Click to collapse
Is this ready to go as far as elimintating the blurry screen AND wifi ??
Just asking as the 1.5 and 1.51 both gave me fuzzys, and applying the update eliminated the fuzzys but took away wifi !
Either way. Thank You SOOO much I knew if I waited you'd give us something nice for the holiday !
You think a wipe would be needed going from 1.51 to 2.1?
Gimpeh said:
You think a wipe would be needed going from 1.51 to 2.1?
Click to expand...
Click to collapse
to avoid any possible issues, I'd suggest a fresh wipe. I didnt add to much after the last rom I flashed so im gonna start over with my sdcard as well
A wipe is always wise, but SHOULDN'T be necessary...
P
Going to try this one now. How is the bluetooth support? Can paired headsets now actually work when calling?
re: support for ANYTHING other than WiFi and Camera (which both work), I don't know!
Let me know stuff that doesn't work, and i'll try to fix it in the next version.
Consider this a starting point...
P
For 32A I recommend the 2.6.29 kernel that redglasses uses on his Hero ROM:
http://www.2shared.com/file/7555649/5881ee4a/myhero-110.html
Might be stuck, d'oh!
So far, did a nandroid, wiped, etc. Updated, rebooted, and after asking for the language and network settings it's sat at a blank screen for some time. Status bar at the top, if left alone and hit the call button the dialer will appear and afterwards you'll see the unlock screen. But it just unlocks back to a blank screen. :/
So far this is the first ROM I've run into that's done this interesting bit. Will maybe reformat SD Card and rewipe, or something.
Nevermind. Rebooted, and it somehow proceeded this time around. Strange, though :/
dont really care for blutooth sound, but will it work for wireless tether ?? thats what I miss from using non hero roms.. having wifi back is also nice !!
Success!
Only noticeable thing is that when you go to far away from the home screen (going into settings, the dialer, etc), and return, it has to reload again for about 10 seconds. But once it's there it's fairly snappy.
Bluetooth pairs and works like it should! I might just hold onto this version of the ROM and tinker with it for a while.
ZiBop said:
Success!
Only noticeable thing is that when you go to far away from the home screen (going into settings, the dialer, etc), and return, it has to reload again for about 10 seconds. But once it's there it's fairly snappy.
Bluetooth pairs and works like it should! I might just hold onto this version of the ROM and tinker with it for a while.
Click to expand...
Click to collapse
have u messed with the swap yet ? 64/60 should help with that or 96/60 perhaps
i just flashed this and still am getting the fuzzys !! grr,, guess i have to flash the update over the rom and loose wifi ??
Modaco if you could shed some light it'd be much appreciated !
WiFi, etc works. Other problem : G Sensors aren't working D'oh
BRAND1SH said:
have u messed with the swap yet ? 64/60 should help with that or 96/60 perhaps
Click to expand...
Click to collapse
My swap's a bit rediculously larger. It's not that bad a lag, but only really noticeable when going back "home" from an application.
No swap or compcache etc. out of the box yet, let's fathom out the best settings together!
P
I'll upload a 32A version for someone to test...
P
modaco said:
No swap or compcache etc. out of the box yet, let's fathom out the best settings together!
P
Click to expand...
Click to collapse
modaco,
I am having all kinds of problems with this rom im still getting a blurry screen, it froze on me 3 times, im stuck in portrait and i keep getting the htc loading screen. I downloaded the file twice to eliminate possiblity of a faulty download as well.
mytouch...amonra 1.2.1, ext3. might have to go back to 1.51 that one worked great
I can confirm that this is running beautifully on my 32A device using redglasses/myhero boot.img and wlan.ko.
Seems to be significantly faster than the 1.73 builds, thank you modaco! Now you just need the 2.84+ build as well
READ FIRST - I am no longer updating my ROMs - details.
If you're following the Hero scene, you'll know that I have published a custom ROM based on the 1.73.405.5 shipping ROM. I have a Vodafone Magic (32B) and a T-Mobile G1 kicking around (and HTC want my PR review unit Hero back!), so figured it would be cool to firstly build a really simple way for me to package my ROMs for all 3 devices, and secondly try and produce an update.zip that runs on all 3!
Well, the first step is here, I have the MoDaCo Custom ROM ready to install on your Sapphire 32B device (if anyone can point me at a boot.img / kernel that runs this on 32A, i'll include that in the package (I can't test 32A)).
Things you should know...
- Contents are IDENTICAL to the MoDaCo Custom ROM core version detailed here.
- I have used cyanogen's kernel from 4.0.4 (big respect to cyanogen, he's doing awesome work!)
- Now compcache ready - use this script for a big performance boost!
It has room for improvement, and given the serious lack of ROM on the G1, I think optimising is a priority. Hopefully it will also provide a useful base for some other chefs. All that said and done tho, I don't think in it's current state it's unusable!
The download link (in update.zip format for flashing in the usual way via recovery image) is at: http://android.modaco.com/content/h...-09-2-1-modaco-custom-rom-hero-to-dream-port/
I've packaged Cyanogen's 4.1.6 BFS enabled Kernel and wlan.ko as an update.zip too (see above thread) - nandroid backup before applying!
I've quoted some of my original Hero post here, so you know what you're getting. Enjoy!
P
Changelog
2.2
Fixed SU and SD card bugs.
2.1.2
Updated busybox
Now compcache ready - use this script for a big performance boost!
2.1.1
Switch to Cyanogen's kernel
Fixed G-Sensor / Compass
Fixed sound
Unified Dream / Sapphire 32B download
2.1
Initial Release
me said:
This ROM is based on the Generic 2.73.405.5 release version of the 'new update' (together with my own optimisations) for the best possible performance! The ROM is now available in 2 versions - 'core' and 'enhanced' by popular request.
Included in both 'core' and 'enhanced' versions
- Rooted with 'adb remount' permission and superuser APK
- A2SD included (fully automatic - thanks cyanogen!) - create a EXT3 partition as your second partition to use. dalvik-cache remains on device. EXT4 is NOT supported.
- Added Jbed Java
- Added Spare Parts (run it and switch the 2 animation types to 'fast' for an even better experience!)
- Added Custom Locale for setting non english Locales
- Added android-wifi-tether 1.52 (props to the developer, this is a great app!)
- Added WMSM
- Added busybox 1.15 - tweaked such that 'get information' in Swapper now works as desired
- Added nano 2.09 - text editor for use in shell mode
- Added terminfo and settings to boot.img to allow nano etc. use
- Added tun.ko file (untested, please report on whether this is useful)
- Added files required for Debian linux
- Moved Quickoffice to data partition to allow easy uninstall
- Deleted 'Learn More' application
- Deleted Maps application - install from the Android Market to always stay up to date
- ROM now includes touch focus in Camera app
- ROM now supports shortcuts using BetterCut (and therefore I assume anycut!) in Rosie
- Silenced boot sound (it's still there and can be reactivated with a file edit)
- You can now check your MoDaCo Custom ROM (MCR) version from the about menu. It will display MCR2.0 (core) or MCR2.0e (enhanced).
- Fix for HTC Peep on Vodafone now available here!
Click to expand...
Click to collapse
Yes
Fire up the stoves chefs and let the cook-off begin!!! lol
Awesomeness Just out of interest then, is this the same build as in this thread
http://forum.xda-developers.com/showthread.php?t=555624
or newer/older?
Jonno12345 said:
Awesomeness Just out of interest then, is this the same build as in this thread
http://forum.xda-developers.com/showthread.php?t=555624
or newer/older?
Click to expand...
Click to collapse
It is based on a newer build of Hero. So it should technically be better. May need some optimization for the G1 though.
I'm running CM v4.1.4 right now, I can just flash this without any other modification? Would a wipe be advisable?
modaco said:
If you're following the Hero scene, you'll know that I have published a custom ROM based on the 1.73.405.5 shipping ROM. I have a Vodafone Magic (32B) and a T-Mobile G1 kicking around (and HTC want my PR review unit Hero back!), so figured it would be cool to firstly build a really simple way for me to package my ROMs for all 3 devices, and secondly try and produce an update.zip that runs on all 3!
Well, the first step is here, I have the MoDaCo Custom ROM ready to install on your Sapphire 32B device (if anyone can point me at a boot.img / kernel that runs this on 32A, i'll include that in the package (I can't test 32A)).
Things you should know...
- Contents are IDENTICAL to the MoDaCo Custom ROM core version detailed here.
- I have used the awesome 2.6.29 jac kernel (serious respect - these guys are the real heroes (pun intended)!)
- None of the 2.6.29 kernel tricks are used (yet)
- No real optimisation has been done (yet)
So, it has room for improvement, and given the serious lack of ROM on the G1, I think optimising is a priority. Hopefully it will also provide a useful base for some other chefs. All that said and done tho, I don't think in it's current state it's unusable!
The download link (in update.zip format for flashing in the usual way via recovery image) is at: http://android.modaco.com/content/h...-09-2-1-modaco-custom-rom-hero-to-dream-port/
I've quoted some of my original Hero post here, so you know what you're getting. Enjoy!
P
Click to expand...
Click to collapse
thanks!!! 10 chars
B3astofthe3ast said:
I'm running CM v4.1.4 right now, I can just flash this without any other modification? Would a wipe be advisable?
Click to expand...
Click to collapse
just make sure u have the latest Radio and SPL and make a nand backup Just In Case
Anyone else having trouble flashing? Get an error, going to redownload incase it's just a bad download.
Redownloaded, still can't flash, get
Code:
E:failure at line 361:
copy_dir PACKAGE:data DATA:
Installation aborted.
EDIT: Wiped dalvik-cache and it flashed .
Jonno12345 said:
Redownloaded, still can't flash, get
Code:
E:failure at line 361:
copy_dir PACKAGE:data DATA:
Installation aborted.
Click to expand...
Click to collapse
You have to wipe your ext 3 and do a alt+w
Yeeeahhh.
The blaze is about to be set!
Got a question....
Are there any devs out there that can build a ROM from the ground up? Maybe a Hero clone that doesn't require so much space and resource? I've noticed (not being anything close to a dev) that you guys take a ROM developed by some techie at HTC and cook it to bring the rest of us enjoyment and peace with our phones, but does any dev have the know-how to develope a "Hero" ROM designed for the G1?
If this is retarded, just ignore the post and tell me to go brick my G1. Word...
jugg2000 said:
Yeeeahhh.
The blaze is about to be set!
Got a question....
Are there any devs out there that can build a ROM from the ground up? Maybe a Hero clone that doesn't require so much space and resource? I've noticed (not being anything close to a dev) that you guys take a ROM developed by some techie at HTC and cook it to bring the rest of us enjoyment and peace with our phones, but does any dev have the know-how to develope a "Hero" ROM designed for the G1?
If this is retarded, just ignore the post and tell me to go brick my G1. Word...
Click to expand...
Click to collapse
Um first off that would be painstainkinly annoying to do and second if it was possible someone probably would have done it and third these roms are a HERO rom designed for a g1 they were once for hero now there for a g1
r_dub said:
You have to wipe your ext 3 and do a alt+w
Click to expand...
Click to collapse
Ahh okay, didn't wipe my ext 3 Hoped I'd get away with it Will try again.
Jonno12345 said:
Ahh okay, didn't wipe my ext 3 Hoped I'd get away with it Will try again.
Click to expand...
Click to collapse
Yeah for 1.5.1 its an absolute must
jugg2000 said:
Yeeeahhh.
The blaze is about to be set!
Got a question....
Are there any devs out there that can build a ROM from the ground up? Maybe a Hero clone that doesn't require so much space and resource? I've noticed (not being anything close to a dev) that you guys take a ROM developed by some techie at HTC and cook it to bring the rest of us enjoyment and peace with our phones, but does any dev have the know-how to develope a "Hero" ROM designed for the G1?
If this is retarded, just ignore the post and tell me to go brick my G1. Word...
Click to expand...
Click to collapse
if you have the money to pay my bills whilst I quit my day job and can wait several months. Then yes.
It takes TEAMS of people that get paid a **** ton of money MONTHS to develop a ROM from the ground up.
ccyrowski said:
if you have the money to pay my bills whilst I quit my day job and can wait several months. Then yes.
It takes TEAMS of people that get paid a **** ton of money MONTHS to develop a ROM from the ground up.
Click to expand...
Click to collapse
Scratch that. If you have the money to pay every cooker here for several months then yes it could be done.
EDIT: I'm only talking for myself and JAC, but a lot of the stuff JAC or I include in our builds we built from the source at http://android.git.kernel.org/
ccyrowski said:
Scratch that. If you have the money to pay every cooker here for several months then yes it could be done.
Click to expand...
Click to collapse
Not a bad idea we could all pitch in and have all the hero devs work togeather on a fully functional G1 Hero build LOL just kidding
im gonna nandroid backup and flash... will post results
It looks like we have some known issues for me to fix tomorrow... no G-Sensor, Compass or (worringly) sound! biggrin.gif
If any chefs have come across these before and have any hints, let me know! wink.gif
P
hey i have bricked my phone i trieed to update my radio to install this rom after completing it when i rebooted my phone now i onli see a photo of a box and a arrrow cuming out of it indicating to phone i cant even power on my phone cant even go to recovery mode..............please help...
Hi,
i'm trying to build my own kernel for the G1 to forward port the msm_camera working in cm-4.2.15.1 kernel 2.6.29.6 to a 2.6.33.2 kernel. So far I've got everything working:
wifi, bt etc. But after several days and attempts I'm not able to get the camera
working in the 2.6.29.6 kernel so no forward porting is possible. I've tried all possible cm-kernel branches and android-git branches,
so I'm starting to suspect that I'm overlooking something stupid and obvious.
I've got the best results so far by porting the msm_camera form android-2.6.29-donut kernel to the cm-* sources in the sense that the camera and camcorder apps start and seem to work but no previews are displayed and pictures or videos could be taken.
Any hints in the right direction are appreciated as this is driving me mad.
Attached there are dmesg and logcat.
Method used is:
1) download the sources (e.g. form cyanogen github)
2) take config.gz form working 4.2.15.1 rom
3) build the kernel
4) generate a new boot image
5) boot the new boot image on the the fly:
fastboot boot new_boot.img
6) camera does not work [email protected]@@
Thanks in advance for your help.
You haven't told us if this is eclair or donut, I suspect eclair as there are some hoops to jump through to get the camera working? Btw camcorder is a different story entirely and doesn't work at all on 2.x
Before anyone goes into one explaining it, are you working on android 1.6 or 2.x?
I'm working on "donut with some eclair bits" cyanogenmod 4.2.15.1.
At this point I've tried all source branches form cyanogen's git:
android-2.6.29-donut
android-2.6.29-eclair
android-2.6.33-msm
and from android's git:
android-msm-2.6.29
android-msm-2.6.29-donut
android-msm-2.6.32
and various permutations of them 8-/
The result is basically the same:
1) the camera app doesn't start
2) the camera app starts but no preview is shown and no photos
can be taken.
You're using CM sources, have you also got the binaries from HTC for Android 1.6 on the G1?
signed-google_ion-ota-14721.zip
from here:
http://developer.htc.com/google-io-device.html
Reference here (the bit about unzip-files.sh): http://source.android.com/documentation/building-for-dream
Shoot me down if I am getting this completely wrong.
Here is the post that helped me get the camera working on eclair, I don't think its relevant to you but may help.
http://forum.xda-developers.com/showthread.php?t=624993&highlight=pershoot
Eureka!!! Got it working!!! thanks st0kes for the hints.
Just to share the info with others, the correct source revision
to get the camera working on cyanogemod 4.2.15.1 is the one tagged
as android-msm-26.6.29-donut:
http://android.git.kernel.org/?p=ke...089eb4931cbf63877963ecb09e6330c5888cdb;sf=tgz
Now happy forward and backporting time starts
More to come in the next days.....
Here is a flash image for the dream of the MT3G ASOP (T-mobile OTA) 2.2 release. Including the most recent security update!!!
[SIZE=+2]MT3G-test3_S.zip[/SIZE]
(MD5: efff33db482ea3b6da3b247516be6a7f .. last updated 11/21/2010)
Please note this includes my 20101106 - 2708 ported kernel, for those requiring other kernels see addons
Requires:
* [Size=+2]1.33.0013d or 1.33.0013 SPLs with recommend 2.22.28.25 radio[/size]
(32b devices only) details on this post..
If you refuse to upgrade or can't upgrade because you have a 32a (1.2 or classic) device: you will need an alternative kernel as described in step 4.b 4.c or the phone will not boot
Note: 2.22.27.08 will also work but is not how the ota was shipped
* Uesrs of other SPLs can either use Danger (dream only), any sapphire SPL on the magic/sapphire/MT3G or alternatively Custom MTD I recommend "87 2" (system/cache) {as of test3 06bindcache will work if you install the parts package, thus if you use CustomMTD parts is mandatory to avoid market issues}
To install:
1) Wipe with 'fastboot erase system -w' (A no-wipe upgrade from test-2 will probably work)
2) flash MT3G-test3_S.zip
3) You will be prompted if you wish to install AmazonMP3 (answer yes/no)
4) You will be prompted if you want to set gprsclass set to 12 (you probably wish to answer yes)
4.b) If you have a 32a or 32a 1.2 magic install the ebi1, ebi0 kernel respectively from here: http://goo.gl/qFJO
4.c) If you have a 32b dream/sapphire without the new 2708 spl/radio install the ebi0 kernel if your radio starts with 2.22, or the ebi1 radio if it starts with 3.22 here: http://goo.gl/qFJO
5) Optional flash "DroidX keyboard" add-on
6) Optional flash "parts" add-on
Alternatively the rom is now available in RomManager; and will install the rom and correct version of the 20110222 kernel; also will allow you to choose between the components parts, droidX keyboard, and language packs.
Whats included:
1) su/superuser from CM6
2) my cm6 optimized pershoot based kernel described here
3) wifi working
4) bluetooth working (fixed inv2)
5) keyboard working (fixed in v2)
6) Rom contains English/Spanish only (Other languages available as language pack addons)
7) No sim card required (fixed with v2 market fix)
Many additional packages included in the parts addon.
To see information on the original Test2 release vist This Post
What not working:
* CM6 potential USB power issue (its not horrible on 2.6.34.7 but if you notice it reboot, or plug in a wall adapter)
* Sound Recorder shortcut missing, this looks like a bug in the OTA not the port a workaround
What to do if it bootloops
Before posting that the rom will not boot; please verify the following:
1) Check that if you don't have the newest radio SPLs *OR* don't have a 32B phone; that you install the correct kernel as mentioned in step 4b/4c in the installation instructions
2) Please use Super Wipe immediately before installing (ie. flash super wipe; restart back to recovery; then install the rom)
3) If you did not install it; install partsB; this will fix some date related bootloops that happens after flashing some of the radios. (after you can login and set the date correctly feel free to re-install without parts if you really don't want it)
4) If your phone is still bootlooping; after a clean install make sure you run 'adb logcat > logcat.txt' on your computer just after rebooting into the rom. Then paste the logcat contents into pastebin copying the link to this thread.
This may sound overkill but its the easiest way to make sure its not your error during install.
Addons
A|| Kernels:
The set of kernels used with this rom can be found: http://goo.gl/qFJO
> MT3G 1.2 (fender users) please use the EBI0 kernel
> 32A magic users (and rogers dreams who have not updated to a 2708 radio) please use the EBI1 port
> Dream/Sapphire users with older EBI0 radios may also use the EBI0 kernel with this rom.
B|| Parts Add On:
MT3G-test3-partsB_S.zip
MD5: 58b80345db33c95a92f9be77ee67cc43 (update 12/01/2010)
What is it you ask.. It adds support for many things on top of the base rom
(note if you are upgrading from the original Test3-parts this is a no-wipe update)
1) Add support for init.d scripts
2) Add support for 'adb remount'
3) Add support for live wallpapers (apk kanged from CM nightly 238, and odex by myself)
4) Add busybox in a squashfs (binaries kanged form CM nightly 238; and repacked since I didn't want all of them) Note test3-partsB restores the toolbox netstat link to correctly display netstat information again.
5) Add LWP fix (fixes various 3D) via init.rc permissions (based on firerats work) updated in test3-partsB to fix slow performance in many games.
6) Added fix_permissions script (this one kanged from biffmod 2.1)
7) Load ipv6 on boot
8) apn list from CM238 nightly (new for test3)
9) flash_image from CM238 nightly (new for test3)
10) date verification; if year is < 2010 set the date to a more recent date (prevents initial boot boot loops for some users) added in test3-partsB
11) And Last but not least:
Added "Froyo Parts" apk custom menu interface to (this is my work k, thanks.. but certainty has ideas from pre-eclair apps2sd and firerats scripts):
internal -> /sd-ext
a. dex2sd (/data/dalvik-cache)
b. data2sd (/data/data)
c. apps2sd (/data/app & /data/app-private)
d. Keep Home in Ram (thanks to raven_raven's idea) [new test3]
e. Compcache 18MB (based of CM's script) [new test3]
f. Restrict /dev/hw3dc most games run better with this disabled; however some work better with it enabled (no reboot required) added in test3-partsB
Check the one or more to gain additional space; allow the app root permissions and reboot; the files will be moved accordingly.
All options only apply on next reboot, so if you make a mistake just revert​
Previous 11/21/2010 version
MT3G-test3-parts_S.zip
MD5: 199475ba609396114049adbe196d571a
C|| DroidX Multi Touch Keyboard:
A new addon for those that like the DroidX Multi Touch Keyboard.
Thanks to RoyalKnight6190 for the biffmod port this is based on and in turn punk.kaos for the version that works on your phones
This is odexed to save data space and WILL replace the default keyboard
MT3G-test3-DroidX-kaosfix-v3_S.zip
MD5: 5f7f7cf54f8224976be173dca9543c57 .. last updated 11/21/2010
D|| Themes:
* See shadowch31's True Blue Theme:
http://forum.xda-developers.com/showthread.php?t=856165
* Also roalex's OTA Gingerbread (for froyo):
http://forum.xda-developers.com/showpost.php?p=9686189&postcount=1440
(enough work it could be its own rom so do check it out)
* sisterchick's Themes for OTA
http://forum.xda-developers.com/showpost.php?p=9894072&postcount=1567 - Blue Revo Theme
http://forum.xda-developers.com/showpost.php?p=9944245&postcount=1586 - Peppermint Twist
http://forum.xda-developers.com/showpost.php?p=9955951&postcount=1590 - Orange Slice/Green Revo/Grape Jelly
* Simple Black Bar
http://forum.xda-developers.com/showpost.php?p=9771131&postcount=1493
A simple black status bar mostly intended to aid others in porting dark status bar themes; but can of course be used on its own.
* castaway1 x10 bar style
http://forum.xda-developers.com/showpost.php?p=10328491&postcount=1647
Note: The clock will be black on black unless you flash the "Simple Black Bar" theme with white clock followed by this themed status bar.
E|| Lang Packs:
Non-supported language starter packs
see this post (update 12/11/2010)
These are for test3 only and provide the options to add [fr,pl,de] or [ja,zh] or [it,ru,nb] or [cs,ko,tr] to the existing en,es rom.
F|| Disable Menu Unlock:
No this is not a bug fix; the Rom has a feature coded in to allow the menu key to unlock the screen as could be done on the phone before the update.
However for those that don't like this feature here is a hacked version of the framework to disable the menu unlock, and enable the "H" notification.
MT3G-test3-disabelMenuUnlock_S.zip
MD5 SUM: 897bf28ee97db05395935f0e29b20967
Please note this will not work with the language packs or themes (of course a theme or custom language pack may include this functionality)
G|| Kernel Updates:
An update to the included 20101106 (and related 20101031) kernels can be found:
http://forum.xda-developers.com/showpost.php?p=11565574&postcount=670
Simply flash the kernel update.zip matching your configuration
FAQ:
* Installing Titanium + Root Fails: You require BusyBox for Titanium to work; this can be installed via You can either install the parts package or install via titanium its self
* I need ipv6 loaded on boot to run goggles or other app: This is included in the parts package; if you wish not to use the parts package see this trick
* adb remount doesn't work and this rom doesn't have root.. yes 'adb remount' fails because this is a stock rom.. however NO just because that fails doesn't mean there is no root. see this post in short modify /system in recovery its safer than adb remount anyway. Also ADB remount has been added to the parts package
* I want to revert from the DroidX keyboard to stock: re-flash test-3 followed by parts if you flashed parts. (do not wipe)
(In short if you are having issues with advanced features try out the parts package )
Note:
This is only a quick hack of the official MT3G rom; please don't expect me to make major changes to it (If I'm doing that I'll build from ASOP source)
(Changes: version 2 fixes bluetooth and the keyboard + audio levels for dream + removes OTA key so it won't ask for any future updates)
(Changes: Market-fix; applies the updated files from the OTA fix; in addition to allowing you to signon [or skip signon] without a simcard)
(Changes: Test-3 parts improvements + security update included)
thanks for this fast port. i will give feedback =)
EDIT: wo mtd its working smooth. just one faves fc and otherwise no issues. maybe you could say that gapps are included and working ^^
Currently flashing too, many thanks! Was gonna have an early night, cant see that happening now!
Update: Flash went well, booted up nice and quick. Upon setup screen I left it sit for a few mins after the screen turned off. I then proceded to set up passed the initial screens but it failed to connect and stated "you dont have a network connection". It found my router fine, carried on with the set up and synced. So for me so far I have no mobile data connection. Overall it seems nippy and responsive, will keep testing it out...
What did you do!?!?!?!? this is perfect!!!!
Browser, Gallery, Search, Calculator, Phone, Messages, etc ALL OPEN AT THE SAME TIME, no swap, no compcache (i think, free/busybox is broken) SUPERFAST FROYO
Thanks man.
Quick question... is this insane speed due to that i haven't logged in to google yet? or is it due to your awesome kernel? or neither? What's different between the EXACT kernel used in here and the pershoot ones?
Thanks.
James Carr
I desperately want to flash this, but I'm slightly nervous because my MyTouch3G (or HT-03A, in my case) was bought in Japan and subsequently unlocked for use in another country. I see that SU was implemented, so I'm not worried about losing root. Basically, besides the normal risks of flashing custom roms, is this going to create a danger zone for me?
Update: gave it a shot. Installs and boots like a race horse, but sadly it's not a phone. I keep getting the phone itself FCing (com.android.phone) and thus it kind of loses it's functionality. Going to give it another wipe and flash, see if that helps.
Second edit: no love. I know this is going to be huge, and I already can feel/see the amazing speeds present here. BUt if I can't make phone calls, it really can't help me right now. Good luck man, I'll be rooting for you!
jcarrz1 said:
What did you do!?!?!?!? this is perfect!!!!
Browser, Gallery, Search, Calculator, Phone, Messages, etc ALL OPEN AT THE SAME TIME, no swap, no compcache (i think, free/busybox is broken) SUPERFAST FROYO
Click to expand...
Click to collapse
I kept it stock; stock has no busybox but you can push it from somewhere else if you wish
The compcache module is included if desired; also setcpu will allow upto a 595oc with this kernel; (a safe 576 max by default)
Very little injected my kernel+modules; and su/superuser.apk from a cm6 build so you keep root.. and copied init.sapphire.rc to init.trout.rc (removed the radio+recovery components of course since I assume you wish to keep the custom recovery)
Without bluetooth this is like a one engine jet plane .
No PAN , no can.
i have a funny feeling t-mobile, google and htc are dicking us around, yawn.
http://imboredatwork.org/boredbaby.jpg
This is absolutely amazing, the speed is as fast as donut, unbelievable!! What is needed to get root access? Im in no position to be ale to help unfortunately as I lack the tech-knowledge! Also any ideas on the bluetooth issue?
May many many thanks!!!
How does this compare to Biffmod for you? I remember the original stock Donut was typically faster than AOSP based Donut roms, does it apply to this case?
Downloaded and flashing right now...
thelamacmdr said:
How does this compare to Biffmod for you? I remember the original stock Donut was typically faster than AOSP based Donut roms, does it apply to this case?
Click to expand...
Click to collapse
For me my friend, this is probably the best rom ever! My reasons, theres been no lag, installation was smooth and fast, not a single force close. Bluetooth and mobile data isnt working for me (is it because I am in the UK, perhaps I just need to sort out my APN.....) nor is there root yet but theyll come in time. Ive installed LauncherPro and it runs smooth as anything, I am VERY VERY pleased that I have a super fast Froyo on my G1, I am never going back!!!
PS: I personally experienced random reboots on Biffmod and other Froyo roms, none on this rom so far!
cd993 said:
For me my friend, this is probably the best rom ever! My reasons, theres been no lag, installation was smooth and fast, not a single force close. Bluetooth isnt working nor is there root yet but theyll come in time. Ive installed LauncherPro and it runs smooth as anything, I am VERY VERY pleased that I have a super fast Froyo on my G1, I am never going back!!!
Click to expand...
Click to collapse
Um.. root is working for me.. I added that to the zip (if you are in adb you will need to run 'su' then accept it on the phone.. so make sure the phone is unlocked the first time)
Sorry to be stupid, will this work with Magic 32B version? I dont care for Bluetooth at all, I care for wifi, 3g and gps.
Heading home right now to go and flash this on my G1.
feronovak said:
Sorry to be stupid, will this work with Magic 32B version? I dont care for Bluetooth at all, I care for wifi, 3g and gps.
Click to expand...
Click to collapse
Obviously, read the first post...
If I wanted to how would I go about updating to new Radio/SPL etc and use this lol ~ noob question but just making sure
XxKOLOHExX said:
If I wanted to how would I go about updating to new Radio/SPL etc and use this lol ~ noob question but just making sure
Click to expand...
Click to collapse
No new spl/radio, actually it will probably fail with the new radio.
ezterry said:
Um.. root is working for me.. I added that to the zip (if you are in adb you will need to run 'su' then accept it on the phone.. so make sure the phone is unlocked the first time)
Click to expand...
Click to collapse
Sorry yes my fault there. The problem I faced was I tried Titanium Backup but it complained of not having root and/or BusyBox. I went in to Terminal, typed SU, allowed it, downloaded BusyBox through Titanium and all is well!
Your. Are. A. Genius!!
PS: Keys arent mapped correctly e.g. the 'M' key which should give me a '>' gives me a '!'
ezterry said:
No new spl/radio, actually it will probably fail with the new radio.
Click to expand...
Click to collapse
Okie dokes thanks was just making sure
Flashed! Nice and fast, adding spanish APN...!
I'm trying to get a functional config for the 1.2 mytouch but I'm having trouble tracking down the exact source to the MT3G-Fender-1.2-2.6.35.12-10M-test4.zip kernel but it's proving rather tricky. I can't seem to determine what the source to this kernel is and where to pull it.
If anyone can point me in the correct direction i can start on some work.
I pulled some pre-packaged git repo from ezterry's github. ezterry-kernel-biff-testing-5fba47e
I pulled my config from the running kernel from the zip i mentioned above running on my phone.
I built the kernel produced from using that config and the wlan.ko module.
Using this guide : http://forum.androidcentral.com/htc...how-build-your-own-kernel-package-source.html
I just want to be sure the kernel source i'm starting out with doesn't need extra patches that weren't included in the github pull in order to get it to work on the 1.2.
thanks for any help.
I'm also looking at cyanogenmod's github and will probably build a kernel against that pull this week as well.
Still, would like to know what sets the kernel i mentioned above apart from just straight pulls of these repos. That's the only part really confusing me.
Hey I was wondering if you could make this kernel your building an OverClock kernel too. No one has built one for our MyTouchs 1.2 that is truly for this device.
The Max OC I've been able to pull of is 725 without the phone freezing and rebooting.
Idk just thought it would be a good idea for your kernel!
Sent from my Fender using XDA Premium App
overclocking stability is less about the kernel and more about your particular hardware. Some phones just by manufacturing luck can achieve faster clocks than stock to varying degrees. 710 is considered to be the average max i believe. Anything faster is in the far minority of units. People who hack the cpufreq table to get these higher clocks limit to what they consider safe to stop people from actually destroying their hardware (which is possible).
Though, these "oc kernels" should have their patches posted somewhere. It's difficult to track down where exactly these kernel zips are coming from and thus to find out what their source is. Legally they need to either be shipped with the source or shipped with files pointing to the source or have the source available from the same place the binary was downloaded from. thus far I'm just guessing as to what the actual source is to the kernel i'm currently using and hoping all the necessary changes and patches are committed to the github that I believe the kernel is ultimately based from.
cellsafemode said:
I'm trying to get a functional config for the 1.2 mytouch but I'm having trouble tracking down the exact source to the MT3G-Fender-1.2-2.6.35.12-10M-test4.zip kernel but it's proving rather tricky. I can't seem to determine what the source to this kernel is and where to pull it.
If anyone can point me in the correct direction i can start on some work.
Click to expand...
Click to collapse
Hi I built this kernel.. later versions have a SOURCES file with the url's to the source I used. I added that after I started seeing it posted outside of the rom thread I originally posted it to
This is a build off of Pershoots github source
https://github.com/pershoot/kernel-2635
including Ezterry's 10Meg patch to the 32a mem map (Fender/1.2 is 32a/b hi-bred)
https://github.com/ezterry/kernel-b...9fca2404a4fa24384d11f8422ced65920bf06#L0R1355
and Farmatito's usb drain patches 001 - 022 excluding bfs
http://forum.xda-developers.com/showthread.php?t=1010932
and wlan.ko from Cyanogen's sources
the .config can be obtained using kernel-sources/scripts/extract-ikconfig
or adb pull /proc/config.gz config.gz
and as for Overclocking have a look at Dumfuq's githib
https://github.com/dumfuq/cm-kernel/commit/9f113c9e0acf19f57a35acbb85bd6f5cc2e76bb2
I get reboots at anything over 595
edit: I build these kernels because usb mount does not work with 2.6.34 on Gingerbread roms and more recent Cyanogen kernels had the green tint issue. Since the green tint issue is fixed and I think 2.6.34.8 works better on Froyo I haven't been working with 2.6.35 at all lately
cellsafemode said:
I'm trying to get a functional config for the 1.2 mytouch but I'm having trouble tracking down the exact source to the MT3G-Fender-1.2-2.6.35.12-10M-test4.zip kernel but it's proving rather tricky. I can't seem to determine what the source to this kernel is and where to pull it.
....
I just want to be sure the kernel source i'm starting out with doesn't need extra patches that weren't included in the github pull in order to get it to work on the 1.2.
Click to expand...
Click to collapse
you need to ask the person that build 2.6.35.12 based kernels.. [see ratkings comment]
My github has sources for 2.6.34.7/8 and 2.6.36.4 tags match my public builds (I think they are all tagged if not check the notes with my release of the kernel for the correct commit)
I also had some 2.6.35.9-11 builds from cm-kernel sources (exact commits and patches if needed mentions on the posts with the kernels) but the last one off those was in January.. and besides the january one the builds were 32b/2708+ only since that was the reason to re-build cm. sources with little modification.
I too get issues over 595. Wifi will not work etc. at 595 everything is happy.
I pulled the .config, and you cleared everything up. I was just wondering if those extra patches or anything that made booting to the 1.2 correctly were missing from the standard github kernels that I've found.
I have two jobs so time is very limited but I'm hopeful to boot my own compiled kernel this weekend and then work on modifying the accelerometer driver, specifically the parts that handle determining orientation in order to create a sysfs file that controls orientation locking. Write a 1 to the file and it always reports the same orientation that it's currently in, tricking the entire android system into thinking you are never changing your orientation... write a 0 and it reports the real orientation.. and so on. Then write a little app that can be used as a widget or kept in notification bar so you can easily tap lock the orientation whenever needed. Allowing true landscape and portrait locking on any mytouch 3g.
Uhh yeah I trimmed that way down.. no debugging at all (I like to live dangerously)
later tests were less insane
http://www.mediafire.com/file/eqgv0sbb7t4c57s/config-test7
the only other thing to note is that kernel/mkbootimg.sh was edited to force the base address to 10000000 instead of copying the address of the previous kernel.. thats really why I posted it as for Fender/1.2 only. I didn't want anyone messing that up and blaming me when re-flashing Pershoots kernel didn't correct it
It looks like the 1.2 patch is something that basically changes the 32A so if you patch your kernel source to support 1.2, you break building 32A kernels (you have to then have two trees or continually apply and remove the patch between builds). Is that the case, does the patch make your tree a 1.2 only tree when building for the 32A ?
If so I can edit the patch to introduce a kernel config under the saphire board selection to choose if you want to build for the mytouch 1.2 or 32A or 32B directly. So there is no confusion. Then instead of replacing values in the source like the patch does, wrap them in IFdef macros based on the kernel config options.
Then it should be easy to roll out 3 kernel compiles and do something similar to an auto kernel package and utilize a little logic to determine which to use. A rev board with 2.22 radio == 1.2 (i forget if there is another locale where the radio is different for the 1.2). Others can be chosen based on board rev only.
cellsafemode said:
It looks like the 1.2 patch is something that basically changes the 32A so if you patch your kernel source to support 1.2, you break building 32A kernels (you have to then have two trees or continually apply and remove the patch between builds). Is that the case, does the patch make your tree a 1.2 only tree when building for the 32A ?
If so I can edit the patch to introduce a kernel config under the saphire board selection to choose if you want to build for the mytouch 1.2 or 32A or 32B directly. So there is no confusion. Then instead of replacing values in the source like the patch does, wrap them in IFdef macros based on the kernel config options.
Then it should be easy to roll out 3 kernel compiles and do something similar to an auto kernel package and utilize a little logic to determine which to use. A rev board with 2.22 radio == 1.2 (i forget if there is another locale where the radio is different for the 1.2). Others can be chosen based on board rev only.
Click to expand...
Click to collapse
Um... all my kernels to my knowledge work on 32a old radio, 1.2/32b old radio and 2708+ 32b new radios..
Just 3 config files and #ifs for the changes.. ebi1=3.22 radio, ebi0=2.22 radio, and 2708+ = 32b with 2.22.27.08+ radios. (And thus 3 binaries in the auto kernels)
Note the ebi1/ebi0 have both 32a and 32b versions that is what you see with the smi size logic in the kernel
ok. I read the description of the 10M patch above wrong and thought it was also enabling 1.2 support ...
Also, I'm wondering why exactly we use an initrd/initramfs setup. Our rootfs drivers are all compiled in so what's the real reason we bother with initrd ? Seems like we could speed up loading time if we avoid having to decompress and use an initramfs image and just get right into mounting root
OK, sweet. I have 2.6.36.4-s2 working 100% on my mytouch 1.2. Now i can move forward with some actual development.
cellsafemode said:
Also, I'm wondering why exactly we use an initrd/initramfs setup. Our rootfs drivers are all compiled in so what's the real reason we bother with initrd ? Seems like we could speed up loading time if we avoid having to decompress and use an initramfs image and just get right into mounting root
Click to expand...
Click to collapse
i might be wrong but i think android mounts the partitions directly to places in the initrd. never does a switch root out of it like most linux distros.
but im a noob and might be wrong lol
tvall said:
i might be wrong but i think android mounts the partitions directly to places in the initrd. never does a switch root out of it like most linux distros.
but im a noob and might be wrong lol
Click to expand...
Click to collapse
The normal configuration is:
/ = ramdisk and contains init and adbd on the rom (and all of recovery)
/system = system partition
/cache = cache partition
/data = is userdata partition or internal MMC card depending on the device's design
/data/data = userdata if the device has an internal MMC card
** dream/sapphire only has /data on the MTD partition .. no internal MMC card.. just the external one (sd-card)
Can it be changed .. well that is more of a rom design than a kernel question.. just set the bootimage's command line to match if needed... but the above is aosp's expectation.
OK,
2.6.36.4-s2 ezterry kernel for mytouch 1.2
http://signal-lost.homeip.net/files/2.6.36.4-s2-cellsafe.zip.torrent
Source code at
http://signal-lost.homeip.net/files/ezterry_2.6.36.4-s2.torrent
Seed if you download. tTorrent app is a full torrent app for your phone. Or you can just load it on your computer (ideal) and then move it over usb while in recovery.
This is basically rattking's kernel install package with some minor asthetic edits to the install script and layout. The kernel is based off an older rattking .config with necessary changes to match configuration changes in the newer kernel as well as changes to certain schedulers and included drivers and features.
edit:
If you have trouble connecting to the torrent, make sure encryption is on.
IF you still have problems.. the direct link is http://signal-lost.homeip.net/files/2.6.36.4-s2-cellsafe.zip But it would be nice if the torrent was used.
edit2:
Some info about the latest kernel for those who haven't checked it out...
the 10M patch is already applied in the upstream source, so you'll have that. I also turned on all the unsafe frequencies, but default you move around between 122 and 595. You can override that however with user apps.
NOTE: Swap is not enabled with this kernel. .. that's about all the important stuff for now. I just wanted to get a good stable starting point before i start diving in and breaking stuff.
New version with some bugfixes.
I forgot to add in scsi support so the mass storage feature can function... some other minor changes too.
http://signal-lost.homeip.net/files/2.6.36.4-s2-cellsafe2.zip.torrent
7 hours of constant audio playback with the regular music player, on and off texting and web browsing over 3g (3g enabled entire time) and still got 50% power. I gotta compare to other kernels but that sounds pretty decent considering by now i'd be plugging the phone in.
my next half day off when i'm not 2 jobbing it i'll patch up the sensors so that I can enable and disable updating the orientation sensor via sysfs. Should be trivial then to have real orientation locking that's application independent. Should be sweet !
Is your kernel mainly for gingerbread, or froyo? If I understand right, ezTerry's 2.6.36.4 kernels are for gingerbread...
I've only tested it against gingeryoshi so I would say gingerbread or newer