yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] cityeyes:
I'm sorry ahead of time if this has been asked, but FireRat is mentioned so much in this thread it's difficult to search out an answer without manually going through the whole thing.

That, and while I have a direct link to the thread explaining exactly what the patch does, I'm too stupid to understand exactly what happens.

So, I'll ask and hope that I don't get too much abuse for this:

In simple terms, I understand that FireRat's patch was the thing that made DangerSPL obsolete - that said - is the patch required to use on MT3G since we have more system space than the G1 by default?

What would happen if I DIDN'T install the Firerat patch before installing CM6? I installed the latest test without using Firerat's patch last night on my MT3G and almost everything seemed to be fine except for the known bugs.

Final question (and it could be related), but what happens to root when I install the experimental versions/defcon versions? I attempted a Titanium backup to no avail and then after that I attempted to install busybox through Titanium and got an error. It seems that even though Superuser permissions is working fine, nothing is getting root. Is there any way to fix this?

Thanks ahead of time!
[G1 Android Development] Firerat:
good question, technically no, you don't need it as most if not all roms target a max of 90mb on system ( well, just under )

But, if your not currently keeping a close eye on the size of system, then its handy as you can increase the size of your system partition and be able to install a bloated ROM ( for the moment I'm on 95mb system size )

This is not to say that we shouldn't be lazy and eventually trim things back down to ~90mb or less ( less is good as we can give it to data ), but its nice not to be stressing about the size.
[G1 Android Development] Krician:
Wait, whats the difference between Test9 and Latest Nightly? And please, if you have the time, Give me noobie instructions on how to flash it on a 32B. I mean, I flashed Test 5 On my 32B Dream, but the new tests that came out requires MTD patch? Please help me. I have read the instructions on Firerat's post

So is the patch already configured for a 32B Dream? And am I supposed to flash the ROM first, THEN patch? Or Patch, reboot into recovery, THEN flash ROM?

Thanks for your time.
[G1 Android Development] mr2t32:
First I want to say great job on getting maps to work. Installed the latest nightly, gapps w/o firerat patch on mytouch 32b. So far it seems like everything is working. I'll test out wifi later when i get home from work. Market seems to be the only thing that still FC. I'll try to get a logcat later on. It FC everytime after an installation of a downloaded app. I'm sure the cooks are already aware of this, so i'm just pointing this out for other people that haven't tried out the rom yet. Anyways, that's not a big deal since i don't download much from the market. This will now be my daily until the official release of froyo.
[G1 Android Development] PhreekMini:
I'm running a Mytouch 3g 1.2 and everything seems to work. Having the same issues with the market crashing though. Wifi turns on but never seems to obtain an IP address from any networks. Other than those 2 things everything is working great thus far.
[G1 Android Development] defconoi:
ok Cyanogen is updating the changelogs, usually this is around when he releases an official, I believe we are now stable enough, im building a fresh sync'd CM6 rom right now

CyanogenMod-6 CHANGELOG and Features..

Visit http://github.com/CyanogenMod for full changelogs and git access.

6.0.0-pre
---------
* ANDROID: Google, HTC, Qualcomm, and everybody else. We <3 U
* Common: Deskclock extra settings - cyanogen, mtwebster
* Common: ADWLauncher 0.9 - Ander Webbs
* Common: Music app enhancements - Eliot Stocker
* Common: Phone mod V.30.1 - cytown
* Common: WyContacts 1.2 - Wysie (port to Froyo by Sileht)
* Common: Superuser 2.2.2 - Adam Shanks (ChainsDD)
* Common: MMS enhancements from Ruqqq, Takuo Kitame, Jef Oliver
* Common: Improved RTL text rendering - David Kohen, Omri Baumer
* Common: Themable user interface elements - Wysie, bcrook, jeagoss
* Common: FLAC playback support - Kenny Root, Cyanogen, Glenn Maynard
* Common: Lockscreen enhancements - Wysie
* Common: Long-press home options - Wysie, bcrook
* Common: OpenVPN support - James Bottomley, Takuo Kitame
* Common: Br0tips - Kmobs
* Common: Browser incognito mode - Optedoblivion
* Common: Zipalign on install (if needed) + system dex cache to /cache - Cyanogen/Chris Soyars
* Common: Customizable Nexus LWP - Chris Soyars/Cyanogen
* Common: JIT toggle, configurable heapsize, compcache supprt - Cyanogen
* Common: Adjustable haptic feedback - Michael Webster
* Common: Custom wallpapers - jairomeo, prash, SatanR1
* Common: Battery percentage display - canadiancow, jeagoss
* Common: Trackball wake, trackball unlock, menu unlock - Jon Boekenoogen/Kmobs
* Common: Surfaceflinger night mode and effects - Jeff Sharkey
* Common: Reflow webviews on pinch option - Jonas Larsson
* Common: Enhanced accelerometer settings - Jonas Larsson
* Common: A2DP bugfixes - Glenn Maynard
* Common: Browser fullscreen mode and other enhancements - Wysie
* Common: Translations: Takuo Kitame, Matthias Büchner, Eug89
* Common: Major build system enhancements by Chris Soyars & Koush
* Common: Long press volume buttons to skip songs - Jon Boekenoogen
* Common: Accelerated ARMv7 JPEG decoding - Qualcomm
* Common: Patch wrangling - Cyanogen, Chris Soyars, Koush
* Common: Bluetooth HID support - Erin Yueh @ 0xlabs
* Common: Mouse pointer support - Chih-Wei Huang (android-x86)
* N1: Maintainer: Cyanogen
* D/S: Maintainer: Cyanogen
* D/S: Camera reverse engineering by NCommander & Cyanogen
* D/S: Kernel patches for stability from Zinx Verituse
* D/S: MT3G Fender/1.2 support from Zinx Verituse
* Droid: Maintainer: Koush
* Hero: Lox (GSM), Darchstar (CDMA)
* Bravo (Desire): Maintainers: behnaam, Kali-
* Incredible: Maintiner: Koush
* Espresso (Slide): Maintainers: Wes Garner, Chris Soyars
[G1 Android Development] rsfaze:
anyone else notice Rom Manager is gone from the latest build?
[G1 Android Development] Blackman778g:
Another Job well done by Great people.

Damn this project was amazing.... to many bootloops and force closings to this wonderfully finished project.... all of you developers and modders never cease to amaze me. :)

Seriously... you guys should make your own phone and show Google and the cell phone carriers (ex. T-Mobile) how it's done. No phone shall ever die here! ;)
[G1 Android Development] defconoi:
be sure to let http://twitter.com/cyanogen know as well, dont know if he is reading this thread (he put the work into it)
[G1 Android Development] Firerat:
the ROM is AutoMTD Patched

its just for convenience, since you don't have to flash the boot patch

an AutoMTD Patched rom will use the partition layout of the running recovery

if its stock Danger layout it will use that, if its customised it will use that

I have compiled a 2.6.29 kernel with mtd as kernel modules,

not got round to playing with it yet, but the idea is ( lbcoder's) that the ROM can dictate the partition sizes to use, providing the recovery is compatible..

if I can get a proof of concept working, I would hope that it would be adopted

but for now its not needed.

ROM dev can instruct what partition size are optimum if they are NoneStandard
[G1 Android Development] ttabbal:
Working great, excellent work guys. The only "bug" I've seen so far is that BT with my car (06 Prius) doesn't send/receive audio. Pairing works, making and receiving calls works, status data works, but no audio. Weird. Anyone else with a BT headset notice a problem?

Latest defconoi posted ROM currently. It's amazingly fast, scary fast. I think it put a Nexus in my G1. :D
[G1 Android Development] BuddhaTeh1337:
can somebody upload the actual ROM to a different site like m/u or r/s? i cant seem to download it....
[G1 Android Development] bert269:
Root access

I have tried since around test5 and the Root seems to have a problem.....is this rom not rooted?

I just installed test9 (downloaded from the OP). Titanium backup cannot load since it needs Root and terminal SU - gives permission denied.....

Did I miss something?

Thanks for all the effort guys/gals!
[G1 Android Development] defconoi:
Install the latest nightly with gapps and mtd patcher, all bugs are fixed minus BT audio, and adhoc
[G1 Android Development] ttabbal:
heh.. well, at least I have a known bug. :) Anything I can do to help get BT working?
[G1 Android Development] joseangel.alv:
Well... I've edited the boot.img of this latest nightly to support the autorun of init.d

Here it is! :)

I'm very happy with this last build... after a bit of customization everything is working for me.

Thanks to Firerat ;) (he is the author of the ramdisk I'm using)

EDIT:

It is not flashable... You have to:

Option 1:

extract boot.img to the root of your SD card

enter adb shell or terminal in recovery

flash_image boot /sdcard/boot.img

run again the MTD patch (if you're using it)

Option 2:

unzip

substitute the ROM boot.img by this one

resign

flash the modified ROM

Changes:

autorun init.d scripts

bind mount for cache

/sd-ext directory (mount point)
[G1 Android Development] rsfaze:
I've experienced the same issue.

I was on test2 and everything was working great, TI Backup was functioning but since flashing test5 or higher, now only some apps get root, and now when opening super user on the latest build it just sits with a black screen.

After another clean wipe, this time including the dalvik-cache wipe in the advanced part of ClockWork and it's working. TI Backup is installed and working.

The dalvik-cache wipe under advanced is the only thing I can say I did different from the other couple of times.

Give that a try and see what happens.

Question...

Anyone know why Rom Manager has been removed from the latest build?
[G1 Android Development] ttabbal:
Or use adb/terminal in recovery "flash_image boot <file>". Then don't forget to run the MTD patch again if you're using it, or you get to use fastboot erase like me! :D

However, the bind mount for cache is working, so FR's init.d script is working. Now to get the ext mounted and my userinit working. Then restore all my settings and apps. I wanted to re-do my phone again today, really I did. :D

Thanks man. :)

ohhh... and the /sd-ext directory is there now. Thanks again! :)
[G1 Android Development] lightninbug:
so what if im on g1? what does Then use FireRat's boot patcher:

http://xdaforums.com/show...71#post7061471....WHAT DOES THAT DO? do I **HAVE** to install using that? im on armonra recovery 1.7.0
[G1 Android Development] joseangel.alv:
In:

cm_dream_sapphire-07092010-013513

or:

test 9

Rom Manager has NOT been removed

I suppose you have a system space related problem
[G1 Android Development] Firerat:
no no no

I just patched a bit of cm5's init.rc into the cm6 one

;)
[G1 Android Development] lightninbug:
do i have to install using yout custom MTD layout? b/c i have never done that..and dont really wish to..can i just flash rom then gapps..then boot?
[G1 Android Development] Firerat:
you only have to use that if you want controll over the MTD partition sizes

e.g

change

system 90

cache 30

data 89

into

system 90

cache 2

data 117

or

system 95*

cache 2

data 112

system 95 will give you a little room to play with cm6 until its gets trimmed down to a respectable size
[G1 Android Development] joseangel.alv:
You are completely right... and your way is the easiest by far... ;)
[G1 Android Development] Firerat:
not sure what the current system footprint is

you could manually remove bootanimation.zip to give you an extra 3,5 mb space on system ( before flashing gapps )

nb, to dodge the auto backup/restore of gapps remove /system/build.prop *before* flashing main rom
[G1 Android Development] ttabbal:
From df -h, as I just got done installing.. again. :D

/dev/block/mtdblock3 105.0M 83.0M 22.0M 79% /system
[G1 Android Development] defconoi:
Test10

Download Test10 (83mb system)

Latest Github Sync: (including finalgapps)

http://www.mediafire.com/?vyl2monyygr

if your running the latest nightly as of this post (no need to upgrade)
[G1 Android Development] ttabbal:
After installing the modified boot.img to run init.d scripts, I pushed the 05mountsd script over to /system/etc/init.d/ and made is executable (chmod 750 05mountsd) and rebooted. /sd-ext is now mounted properly, and my userinit.sh runs as it should.

I how no idea how I managed to mess it up when I tried to do it myself, but it works now. :D
[G1 Android Development] Firerat:
nice

if your going to shrink system to 85 mb ( for 122 data ) then make sure you format system, else cache will have junk in it next time you boot to repatched recovery

fastboot erase system -w

is your friend

( or partition options in clockwork )

if on RA,

flash_image recovery /sdcard/recovery-clockwork-2.0.2.0.img

the flash pacther ( with you current part map )

then once you reboot into clockwork

you can repatch ( shrinking system )

and use the partition options to format system, cache and data

save messing with fastboot ( but not an excuse to not have an SPL that can fastboot )
[G1 Android Development] Firerat:
:)

from what I've seen with cm6 you don't really need the cache bind

it seems FroYo has made cache redundant

( market downloads are now 'temping' on sdcard )
[G1 Android Development] ttabbal:
so, something like this?

boot recovery

nandroid backup

edit /sdcard/mtdpartmap.txt

flash recovery MTD patcher

boot fastboot

fastboot erase system -w

boot recovery

nandroid restore

flash boot MTD patcher

reboot
[G1 Android Development] crr127:
anyone have any idea why audio hack doesn't work anymore? worked on test 5 and 6. did they change where the audio files go?
[G1 Android Development] axllent:
As someone pointed out earlier, a wipe seems to be needed to avoid all the issues and segfaults. Thanks for the Test10 file though - appreciated!
[G1 Android Development] Firerat:
yeap

clockwork lets you skip the fastboot bit

actually with RA you could probably do it

mount /system
rm /system/* -r

but its not as clean as with clockwork

( but looking at Amon's github it looks like erase_image may be built in to next version )
[G1 Android Development] defconoi:
is clockwork really that good? I've been using AmonRa's 1.7, I went to his website which seems super outdated and no information or changelog regarding clockwork recovery
[G1 Android Development] BW91961:
off topic

off topic. but can someone tell me who is working on trying to get flash 10.1 on the g1. Do we need a final stable build before we even try? Didn't know if anyone was testing on these nightly builds. If someone can point me to the right board to get some more info on that. it would be much appreciated.
[G1 Android Development] smjfosho:
flash 10.1 wasnt made for our phones, there is a thread about getting flash lite from sense to work, but no progress as of yet to my knowledge
[G1 Android Development] joseangel.alv:
ummm...

I'm not sure why, but without the cache bind I have something like a bootloop...

I don't have a logcat right now, but I remember something about no place while dexing the framework...

I go to test it and tell you the exact error.

My config (100MB system, 2MB cache, - data)

EDIT:

This is the interesting part of my logcat without the cache bind

W/dalvikvm( 65): partial write in inflate (8152 vs 32768)
E/dalvikvm( 65): Unable to extract+optimize DEX from '/system/framework/core.jar'
D/dalvikvm( 65): Unable to process classpath element '/system/framework/core.jar'
E/dalvikvm( 65): opt header write failed: No space left on device
I/dalvikvm( 65): Unable to open or create cache for /system/framework/ext.jar (/cache/dalvik-cache/system@framework@ext.jar@classes.dex)
D/dalvikvm( 65): Unable to process classpath element '/system/framework/ext.jar'
E/dalvikvm( 65): opt header write failed: No space left on device
I/dalvikvm( 65): Unable to open or create cache for /system/framework/framework.jar (/cache/dalvik-cache/system@framework@framework.jar@classes.dex)
D/dalvikvm( 65): Unable to process classpath element '/system/framework/framework.jar'
E/dalvikvm( 65): opt header write failed: No space left on device
I/dalvikvm( 65): Unable to open or create cache for /system/framework/android.policy.jar (/cache/dalvik-cache/system@framework@android.policy.jar@classes.dex)
D/dalvikvm( 65): Unable to process classpath element '/system/framework/android.policy.jar'
E/dalvikvm( 65): opt header write failed: No space left on device
I/dalvikvm( 65): Unable to open or create cache for /system/framework/services.jar (/cache/dalvik-cache/system@framework@services.jar@classes.dex)
D/dalvikvm( 65): Unable to process classpath element '/system/framework/services.jar'
E/dalvikvm( 65): ERROR: no valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar'
W/dalvikvm( 65): JNI_CreateJavaVM failed
E/AndroidRuntime( 65): JNI_CreateJavaVM failed

and, if I configure the cache bind while seeing that, the system boots normally.
[G1 Android Development] BW91961:
Thanks homie. I will do a thread search if you happen to find it post a link.
[G1 Android Development] Firerat:
Two things I hate

can't get console ( on phone adb fine )

no action confirmation , it will just do a trackball slip

But the partition menu is great, and you can navigate folders for zips

I'l make me a flashable ra to get round the no console bit if I'm without pc

I assume the no console is due to most phones not having keyb
[G1 Android Development] Firerat:
Ahh, cm froyo must be puting dalvik-cache on /cache
[G1 Android Development] domii:
a very simple question, do i really have to go on with the firerat's patch for the custom MTD partitioning or i just can flash the CM 6 test 10 away.
[G1 Android Development] Jigga0o7:
I just went for it and flashed test 10. The only issue I have is that Market will FC every now and then. Everything else seems to be working. Wifi (on Dream) JIT, Maps... etc.
[G1 Android Development] domii:
thanks a million, that was fast....really helped :)
[G1 Android Development] Jigga0o7:
Very welcome. I've been watching these froyo threads like a hawk and I've installed pretty much everything that's been released. This is the best for far.
[G1 Android Development] kboater:
so you only flashed test 10, nothing else? which link did you you go flash from?
[G1 Android Development] Jigga0o7:
http://www.mediafire.com/?vyl2monyygr

It includes Gapps. I have DangerSPL installed. Market only seems to FC while its installing an app which makes it a very tolerable bug.
[G1 Android Development] Daneshm90:
K im not sure but during my process of making frf91 gapps mdpi. I posted 2 links. The first one had issues where the market would force-close on market installs, the second one everything works fine.

Im referring to this. Link
[G1 Android Development] Bzerk1:
so is this the working link or messed up link? and can you direct us to the one that works well if this one is not it.
[G1 Android Development] Daneshm90:
Sorry should've been more clear. Thats the working one, i havent heard complaints / the OP also suggested to use this as the gapps for this build so im assuming everything should be good.
[G1 Android Development] Jigga0o7:
Correct me if I'm wrong but that just might be redundant. OP seems to be advising that this Final GApps package is already combined with Test10.

"FinalGapps Included"
[G1 Android Development] Daneshm90:
Oh, nvm then. I though wht u posted was a custom build. Reading ur issues i came to an assumption. So ur still having force-close on market installs ? Could u post a log ?
[G1 Android Development] :
Question can I just flash this rom on top of test 9 or I have 2 wipe?
[G1 Android Development] Jigga0o7:
Here is the code I get in alogcat when it FC's.

E/DatabaseUtils( 2762): Writing exception to parcel

E/DatabaseUtils( 2762): java.lang.SecurityException: Permission Denial: writing com.google.android.gsf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=2811, uid=10002 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS

E/DatabaseUtils( 2762): at android.content.ContentProvider$Transport.enforceWritePermission(ContentProvider.java:325)

E/DatabaseUtils( 2762): at android.content.ContentProvider$Transport.insert(ContentProvider.java:173)

E/DatabaseUtils( 2762): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:146)

E/DatabaseUtils( 2762): at android.os.Binder.execTransact(Binder.java:288)

E/DatabaseUtils( 2762): at dalvik.system.NativeStart.run(Native Method)
[G1 Android Development] Daneshm90:
Ok did u upgrade w/o wipe from a previous froyo build where u were using frf81-mdpi-gapps perhaps ? Can anyone confirm if u get market-install force-closes if u do a full wipe and then flash ??

Im talking about a FULL wipe as in,

fastboot erase system -w
[G1 Android Development] Royalknight6190:
I am in no way a noob, but between this froyo and firerats patchers, I am a little confused. I want to flash this so can somebody give me a quick run down of the exact steps? Thank you.

What I mean is do I need to part my SDcard? If so what sizes? I saw on the OP that you flash the FireRats Part Hack and then the Rom and then The Boot Hack. I guess I am just stuck on the SD card, probably just stuck in the past with how we used to do things. Thanks for the help.

I hope I make sense. I just got off a very long shift, sorry if I dont.
[G1 Android Development] robuser007:
Isn't this the same as full wipe in ra-recovery ?
[G1 Android Development] rk0:
No. If you wipe through recovery it only wipes /data and /cache. The /system stays intact.
[G1 Android Development] Firerat:
I believe the current is a system of 83mb

so you do no need to "firerat patch" to install

the ,mtd patch will simply increase the amount of space available on data

( by approx 38mb if you opt for 85mb system )

in the past system was a shade over 90 ( for full gapps )

must admit, it is a little confusing as the OP does not detail the recommended system size, but I think that detail has been in the thread.
[G1 Android Development] grennis:
Can somebody help me, why am I getting this building from CM6 repo?

make: *** No rule to make target `vendor/cyanogen/proprietary/RomManager.apk', needed by `out/target/product/dream_sapphire/system/app/RomManager.apk'. Stop.
[G1 Android Development] studjuice:
So the op now says that everything works besides bt audio and something else.

Does the rom auto mount SD-ext correctly now? Is sideways gallery fixed? Voice search? YouTube?

Those are the only old bugs I can think of. If its all working... GREAT! And I have come up with some ideas to make it faster ;)
[G1 Android Development] smjfosho:
Faster?? Yes please! Share
[G1 Android Development] ftruck90:
has anyone else noticed that the JIT on off button isn't working in the latest nightly..well it's either that or they way they implemented JIT is terrible. The SPF rom seems to get a real boost out of jit and and definitely outpaces the nightly. the JIT in the nightly just seems to make everything fall apart.

EDIT: was actually having cache bound to /sd-ext that was causing all the slowness...
[G1 Android Development] grennis:
Nevermind I figured it out myself.
[G1 Android Development] studjuice:
Not actually faster, but feel more responsive. I've been using it for a full day now and been paying attention to what's most annoying. The launcher reloading is annoying (but not as slow as other rom's!) and orientation, maybe a little keyboard speed?
[G1 Android Development] skater4690:
are you using test 10?
[G1 Android Development] studjuice:
No not yet, is there some big difference?
[G1 Android Development] Krician:
Dammit -____- I just flashed latest nightly, then test 10 came out.. Is there any changes?
[G1 Android Development] :
Please can anyone tell me how good is this rom im using extremes froyo but i want to know how good is this 1
[G1 Android Development] rsfaze:
only one way to find out :)