yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] RebelScum75:
Well, it didn't look like some of the other posts in here, mine had a lot of stuff the others didn't, and I just wanted to be sure, that's all. Thanks for the verification that it is all good.

Can someone answer my other question: it was implied earlier by FR that this patch can be undone by flashing a new ROM and just not flashing this patch. Ok, but the "recovery" patch, I would assume, does not get reversed, since that is patching your recovery (right?). If you wanted to completely revoke this, you'd have to re-flash recovery, and then re-flash your ROM, right?
[G1 Android Development] AndDiSa:
It was already discussed here: It's obvious, because otherwise you would have two different partition tables when you are running recovery and when you are running the rom. Both should always have the same partitioning.
[G1 Android Development] lbcoder:
Sanity check = failed.

You really need to read up on the difference between VOLATILE and NON-VOLATILE memory. RAM is VOLATILE.

So when you turn the power off, does it come back totally blank? If not, then it MUST be NON-VOLATILE memory! Remember that I just finished saying that RAM is VOLATILE.

According to above, you have 69276 total free including both RAM (1804) and SWAP (the rest). So what's the problem?

Note: Android has a special process killer that kills things when the RAM gets eaten up too much, hence it tends to balance out with about 2 MB free. As for the fact that it isn't loading up your swap... well that's because swap isn't compatible with android. It can do some REALLY weird things.

It must be just too simple for you to comprehend. I think you're getting messed up with all the idiotically insane difficult stuff that you can't see what is right there and obvious...... lets provide you with an easy analogy.... if you paint your walls green and then you don't want them green any more, you paint over it with something else, like blue. Easy?
[G1 Android Development] RebelScum75:
Ok, actually, I did know this. What I was saying was that "free" shows you volatile RAM.

My question is, what kind of non-volatile memory is in the system? It's not the same thing as an SD card; it's faster, right? Or is it just the access speed is better?

So... yes?

Listen, I realize how frustrating it must be dealing with people like me who are totally new to this stuff, but I don't think you realize how hard it is coming in to the scene at this point, when everyone else already seems to be up-to-speed. I'm trying to learn, I really am, but it's hard to find good starting points; a lot of the posts/wikis are very out-of-date, and following them just doesn't work. I come in here and it's like everyone's talking a different language. Maybe you've forgotten what it was like being totally new. Talking down to me just isn't productive.

But thanks for the help.
[G1 Android Development] asb123:
Whats the genral rule for system sizes? In general how much bigger than the zip file should I have the system partition?
[G1 Android Development] Firerat:
unzip rom

look at size of system, add a bit

but as most ROMs set themselves a max of 90, stick with 90

wait for Devs and Modders to do the more complicated conversions

but you might find some tips in

http://xdaforums.com/showthread.php?t=727386

If I get bored I might 'covert' the Slide Port I did ( after fixing the browser issue, *without resorting to replacing the Slide Framwork with some old espreso framework )
[G1 Android Development] techjosh:
Help with Rogers Dream

Is there any trick to getting this to work properly with a Rogers Dream? I didn't think there was but I'm having the hardest time with a new Rogers Dream I just got while I've had no problems at all with the G1 I've been using. My SPL is 1.33.2005, my radio baseband is 3.22.20.17.

My mtdpartmap.txt file is set to "110 2". After I install the latest Amon Ra recovery image (1.7.0R) I boot into recovery and flash the FR-MTD-PartHack-recovery-v1-3_S.zip, wipe data + cache, and reboot into recovery again...

... except I don't. I'm stuck staring at the Rogers logo until I remove the battery. I CAN get back into recovery using fastboot boot with the same recovery image but using the -c flag along with appending the correct "mtdparts=" value to the command line (I took the value from my working G1's /proc/cmdline). Once booted I can even install ROMs (being sure to flash a Rogers compatible kernel on top afterwards) and flash the FR-MTD-PartHack-boot-v1-1_S.zip updater, but rebooting still lands me at the same Rogers screen.

The Rogers Dream does work when I don't try to change the partition layout, though... so I know that the ROM/Kernel I'm using work. I've tried everything I could find in the thread and a few other things too but still can't get this to work on my Rogers Dream. Any suggestions for what to try next? Has anybody been able to do this on a Rogers Dream? Thanks!
[G1 Android Development] yohshua:
thank you very much that seamed to fix it and all seams well again thank you :)
[G1 Android Development] Firerat:
hmm,

you have me stumped

at the moment, the only thing I can think of is that the kernel is slightly different in the way it handles the cmdline... but I have to admit this is just a guess at the moment, I'll grab 1.7.0R and see how different it is

Edit:

nope, only difference in the config is

CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1=y

and I imagine they are the same src
[G1 Android Development] lbcoder:
Internal is nand-flash. Your sdcard is *probably* also, but not necessarily.

What do you think?

I wasn't talking down on you. Read that again and try to find out where I said something like "you're stupid". All I said is that **you are expecting something complicated when it is actually very simple**.
[G1 Android Development] lbcoder:
@Firerat:

He's running an EBI1 radio.....

http://wiki.cyanogenmod.com/index.php?title=How_to_build_a_kernel_port_for_CM5

the unpack/repack commands you're using won't work!

@techjosh:

You can safely flash a 2.x EBI0 radio, then you won't be crippled to EBI1 kernel/boot images. There is NO advantage for you to have an EBI1 radio. I suggest flashing it via FASTBOOT since your SPL is capable of it.
[G1 Android Development] whywhy1:
can this be undone?
[G1 Android Development] lbcoder:
Possibly, but it may require that you use one of these: http://tiny.cc/5h0au
[G1 Android Development] techjosh:
Thanks lbcoder, I'm glad to hear theres a reason and I'm not going insane. But there is a slight advantage to the EBI1 radio... I get an extra meg of RAM. And lets face it, the Dream can use all the RAM it can get! If I can avoid switching to EBI0 to get this working I will...

Rogers Dream w/EBI1:

# free
free
total
Mem: 98664

TMobile G1 w/EBI0:

# free
free
total
Mem: 97640

I was able to get this going though thanks to your tip about different base offsets... I changed the mkbootimg line to look like this:

/tmp/mkbootimg --kernel /tmp/${boot}.img-zImage --ramdisk /tmp/${boot}.img-ramdisk.gz --base $(cat /tmp/${boot}.img-base) --cmdline "$KCMDline" --output /tmp/${boot}.img

that

should

work with whatever kernel image is already there and preserve its base offset.
[G1 Android Development] Firerat:
ahhh,

I really should read about other phones

ok kewl

thats almost too easy :)
[G1 Android Development] superbart007:
Question?

do I have to reflash any of this when flash a new or updated rom. i.e. the cm6 nightlies.
[G1 Android Development] RebelScum75:
Yes, you have to re-flash just the 2nd part, the "boot" part. The 1st part you would only have to re-flash if you were flashing a new recovery as well.
[G1 Android Development] Necrobutcher:
Stuck on T-Mo Screen with the newest nightly
[G1 Android Development] techjosh:
OK, so I tested this on one of my EBI0 G1's and it worked perfectly there as well so I thought I'd throw it up here so that others can make use of it...

I can't wait for somebody to throw together a recovery image that has the mtd driver compiled as a module... that would be so cool to be able to repartition on the fly. After that we'll need to automate the application of these scripts if the recovery or boot partitions are flashed. Then there wouldn't be anything extra to do when flashing a ROM, unless you wanted to repartition first and even that would be mostly painless.
[G1 Android Development] Firerat:
:)

Nice one, I'll link these in the OP

,

yeah, MTD as modules, just this min been thinking about that again.

I've already compiled a Kernel, not tried it yet.

as POC I'm thinking of packing the extra AnyKernel bins into recovery, along with a script

the script doing something along the lines of

updater-script copies MTD config to /tmp/

updater-script runs the script reads config file in /tmp/

erase_image system,data,cache

reload MTD Modules with new partition layout

erase_image system,data,cache

reflash recovery with new layout

updater-script completes ( i.e. rom is flashed )

Boot Patcher reflashes boot

but as I said, not tried the kernel yet, I think as long as I unmount anything MTD related the kmod reload should work ok

I will probably have something next week
[G1 Android Development] Firerat:
which is probably an issue with the nightly

it could be a space thing, either

'grow' system

remove bootanimation from zip and re-sign

squashfs xbin and re-sign

but it could easily be something else

if you can't fix a nightly, either forget about using nightlies or wait for someone who can fix it to fix it.

There is little point in crying a nightly doesn't boot, especially in a thread which has little to do with CM6 nightlies

go here for your nightly chatter

http://forum.cyanogenmod.com/topic/2697-nightlies-discussion-of-nightlies/

I have posted at least one 'fixed' nightly in that thread ( 0723 )
[G1 Android Development] alongenemylines:
woo! 127.8 mb for data on cm5.0.8! thank you firerat!
[G1 Android Development] srivers33:
need some help

first off thank u firerat. the opportunities are so much more vast now w this hack.

i do have an issue tho and wud really appreciate some help. ive read the thread and cant really figure it out.

ive been running a few dif froyo's all w ur patch in the past week. last night i tried wiping data cache & dalvik & using ur patch on a 2.1 sense rom. it wouldn't boot, so i gave up that wiped all again and tried a nand backup of another 2.1 sense rom this time w/o using the patch . it booted but with a froyo/eclair lockscreen. tried another nand and again nothing after the boot screen. got back to froyo ok but how do i get back to my old stuff. it almost seems like its not wiping completely . plz help.

im still on r.a. 1.5.2 btw
[G1 Android Development] Firerat:
when ever you resize you must clear everything

fastboot erase system -w

or for best results use the partition formats in clockwork recovery, before and after rebooting recovery .
[G1 Android Development] srivers33:
so boot into fastboot (camera and power) then what? im not seeing a wipe option. or do i need to go into the console and use that command "fastboot erase system -w"
[G1 Android Development] sunzoje:
on g1 with danger spl, flashed FR-MTD-PartHack-recovery-v1-1_S, cm nightly build, gapp addon and FR-MTD-PartHack-boot-v1-2_S_S. getting duplicate listings on df

Filesystem Size Used Available Use% Mounted on

tmpfs 47.7M 0 47.7M 0% /dev

tmpfs 47.7M 0 47.7M 0% /mnt/asec

/dev/block/mtdblock3 90.0M 87.8M 2.2M 98% /system

/dev/block/mtdblock5 117.8M 39.2M 78.6M 33% /data

/dev/block/loop0 4.0M 4.0M 0 100% /system/xbin

/dev/block/mtdblock4 117.8M 39.2M 78.6M 33% /cache

/dev/block/mtdblock5 117.8M 39.2M 78.6M 33% /cache
[G1 Android Development] Firerat:
yes, you type

fastboot erase system -w

if your stuck stick "fastboot" in the box in the upper right of this page ( the one with the magnifying glass icon
[G1 Android Development] Firerat:
:eek:

that must mean the bind mount is working
[G1 Android Development] sunzoje:
cache of 117 MB. am confused ..
[G1 Android Development] Firerat:
http://xdaforums.com/showpost.php?p=7226113&postcount=168

will hopefully explain it
[G1 Android Development] sunzoje:
thnx ... that explained ... btw wonderful work around ...one question, do we need to flash both files everytime i do wipe and install roms?
[G1 Android Development] z28james:
Please correct me if I am wrong..

I was wondering this myself. In attempt to try and see if I understand this, the first file patches recovery. I would imagine this needs to be done once? The second file, this actually patches the rom. Id think this needs to be done every time unless the ROM includes this (SpeedTeam 3.0 does, apparently)?
[G1 Android Development] Firerat:
you only need to flash the recovery patcher

once ( each time you want a new size )

or if you have upgraded/switched recovery

Edit: odd that got totally messed up

you only need to flash the recovery Patcher once ( unless you want to resize or have installed a new recovery )

you *must* flash the boot patcher if you flash a new ROM/Kernel

( unless its an AutoMTD zip, but if your not sure just flash the boot patcher )
[G1 Android Development] Firerat:
I was wondering if anyone was using the AutoMTD :)

it just makes things a little more convenient :)
[G1 Android Development] srivers33:
Yea I did man, just couldn't get a clear enough answer and ofcourse its not somethin I should be guessing on. From what I've read it looks like I boot into fastboot (camera + home) then connect to my pc via usb and the pc will somehow allow me to type in a command of "fastboot erase system -w" enter. But from what u told me I should be able to boot into recovery mode on my G1, choose "console" and type the same command and it will do its thing w/o ever connecting to a pc. So which is it? The fastboot way or the G1 recovery way?

I understand ur frustration man, just tryin to learn from the best person to learn from ya kno.

Thanks again

Sent from my HTC G1
[G1 Android Development] Firerat:
you do that command on your PC

I'm guessing you are a windows user

http://xdaforums.com/showthread.php?t=463627
[G1 Android Development] bbutlerau:
bah i tried applying this for like 4 hrs last night. Im using the latest cm6 nightly. I:

nandroid

wipe everything through clockwork partition menu

applied first patch (recovery)

reboot into recovery

restore nandroid

apply boot patch

reboot

This didnt work. Im on dangerSPL and still have a 30mb chache according to root explorer
[G1 Android Development] Firerat:
and when you reboot to recovery, what is the size of cache?

adb shell df -h
[G1 Android Development] acidwashg1:
your patch works flawlessly firerat, thanks for the great work. i think i misunderstood what this patch does, but i figure i'll ask. is there any way you can increase the amount of working memory for the phone with these kernel tweaks? if so, what partition would i have to increase to give the phone more memory? devfs? system? im only currently using about 40% of my data partition, and that is with all of my apps installed. i would like to repurpose the remaining ~60% to increase the working memory for the phone, in such a way that i would be increasing the total memory when listed using the free command. would this be possible? *crosses fingers*
[G1 Android Development] bbutlerau:
Filesystem Size Used Available Use% Mounted on

tmpfs 47.8M 0 47.8M 0% /dev

/dev/block/mtdblock4 30.0M 1.3M 28.7M 4% /cache

thats all it says.. so 30mb.. not sure what im doing wrong here
[G1 Android Development] Firerat:
afraid not, you are confusing nand and RAM into the same thing

I think its about time we changed the label in the settings to internal storage instead of memory, because that is what seems to confuse people.

RAM is very different to nand flash, they are incompatible.
[G1 Android Development] Firerat:
well, it looks like recovery is not patched
[G1 Android Development] bbutlerau:
how do i get it to patch.. it looks like it works fine... very confused here

for soem reason logat is not working either i get adb logcat ./sbin/sh: exec: line 1: logcat: not found
[G1 Android Development] Firerat:
recovery doesn't have logcat

and I haven't a clue why its not working

boot to clockwork recovery

format system data and cache

flash recovery patcher

reboot to clockwork recovery

format system data and cache

flash/restore rom

flash boot patcher

thats it, it is suppose to be simple
[G1 Android Development] bbutlerau:
is there another method to try?

should i maybe try a diff recovery, im using clockwork 2.5xx.. a beta one. (im a sucker for trying betas)

also off topic but it rc2 much diff from the latest nightly?
[G1 Android Development] haunter1982:
Perhaps....

Could it be that CM6 has a recovery inside? I didn't have a clean CM6 here so i could not look into it. But i think i heard something like this before.

That would make it impossible because when flashing the CM6 then you overwrite the patched recovery....

So just unpack the Zip and search for recovery.img.

Ok, forget my idea, you wouldn't have longer the Clockwork-Recovery if another one would be inside CM6...

Have you tried another ROM? I use the one from Studjuice. It has the Auto-MTD Patch inside...
[G1 Android Development] Firerat:
space is very tight with cm6, a recovery wouldn't fit
[G1 Android Development] Firerat:
you are using the same recovery as me
[G1 Android Development] TmobileDash12:
Hello, excuse me if I'm allowed to ask this question, but what sizes do you recommend for this ROM.

http://xdaforums.com/showthread.php?t=679135

Again, pardon me if you are tired of these kinds of questions.

Sorry and thank you in advance :]
[G1 Android Development] ERamseth:
Any issues popping up with this and CM6-RC2?
[G1 Android Development] Ace42:
On HardSPL it says buildprop and different spl #'s like a 1000 times.
[G1 Android Development] Firerat:
see post #2, you will also need a different kernel which is also in post 2

( I can do a working x0.95.xxxx kernel with the rc2 src later today )
[G1 Android Development] Firerat:
nope, and there is no reason there would be any issues
[G1 Android Development] Firerat:
start with 90 2

once installed have a look at df -h

you can reduce the size of system by the amount of free space on system ( rounded down )

e.g. if free space was 2.7 mb , then 88 2
[G1 Android Development] mr.incredible:
I've read through a lot of the thread. (not all) Sorry if it's been asked. The partitioning on the SD, what does it modify? Does it mess with the FAT part? I don't want to chance losing anything there. I know I should be backing it up if it's that important. As a matter of fact I will. In that case I'm just curious.
[G1 Android Development] lbcoder:
Wrong thread. This has NOTHING to do with the SDCARD.
[G1 Android Development] ZailCZ:
I have lots od free /data now. Is this free space usable to speed up my mobile? Can it be used for swapper? If yes, is it better than swapp on sd card?

If not, I can move all my apps from sd to internal memory without slowing down my mobile ?
[G1 Android Development] mr.incredible:
Not the wrong thread. The custom partitions are on the sdcard. My question is which partition is the script modifying? the ext partition or the fat partition.

Edit:Where else could the partitions be placed? School me if I'm wrong.
[G1 Android Development] Firerat:
no, don't use your internal storage for swap, you will ultimately limit the life of your phone for very little gain

and yes, you can move your apps from FroYoFat to internal storage

it will take forever to do via settings

this script will try and move everything to internal

for apk in `find /mnt/asec/ -type d|grep -v asec/\$`;do
echo "moving `basename ${apk}.apk` to internal ( temp )"
pm install -f -r ${apk}/pkg.apk
done

should be fine as long as /mnt/asec/ is smaller than free space on data

du -hcs /mnt/asec/
[G1 Android Development] lbcoder:
As I said, WRONG THREAD. Clearly you HAVE NOT READ ANYTHING. Either DO SO, or go away.

Edit: I suggest you start with the OP: http://xdaforums.com/showpost.php?p=7061471&postcount=1
[G1 Android Development] Firerat:
gawd..............................................

you just don't understand,

please please do not use this

infact just unroot , or buy an iphone
[G1 Android Development] Firerat:
uploaded a cm6rc2 kernel compatible with NoneDanger

see post #2 for more details

2010-07-27

NoneDanger compatible Kernel for RC2

FR-CM6RC2-bootimg4NoneD-AutoMTD.zip (MD5: 88aeabb075c1b3a23cfa61726d790e24)

http://rapidshare.com/files/409421937/FR-CM6RC2-bootimg4NoneD-AutoMTD.zip.html

http://www.mediafire.com/file/52ajiqdmi45idy7/FR-CM6RC2-bootimg4NoneD-AutoMTD.zip
[G1 Android Development] mr.incredible:
Dude, that was harsh... Forgive my ignorance. I did read like the first 5 or 6 pages and the last 5 or 6 pages. I guess I just had a mental block against where the extra room was coming from. I did go back and reread some of the key explanations and it is a little clearer now. Basically you are just rearranging the use of the internal storage? Couldn't some of this be pushed to the ext? Back in my SGI UNIX days (IRIX if I remember correctly) we would bind system folders across drives. Drives weren't big enough back then to handle the graphics for color copiers and wide format plotters. Would that be advantageous in anyway?

Anyway I assumed that is what you were doing. I got a little carried away. with the possibilities.
[G1 Android Development] Firerat:
Its a cruel world....

No bind mounts are not used like you describe ( but I do use one to get around the limited size of cache )

If you want to know how it works look! Nothing is hidden.
[G1 Android Development] asb123:
I have been told conflicting info with the mtd patcher.

Originally I was told that I do not need to reflash the recovery patch after the first time.

Now in see in the op that it says I need to flash it when I change sizes...

I think that I may be needing to flash it everytime i change the txt file values because I am having hude problems with every rom I have tried since installing, so I must be doing something wrong.
[G1 Android Development] Firerat:
if you want to resize you need to resize recovery, so yes you must flash the recovery.

the logic is very very very simple
[G1 Android Development] lbcoder:
Harsh? Yep. But note that this harshness prompted you to do what you should have done to start with.... read and understand.

As for pushing data to partitions on the sdcard... sure you could do that if you want, BUT it WILL get to be a real nightmare trying to support people doing this.

If you want to move things to the SDCARD, you can certainly do so, BUT, this procedure would be best reserved for CUSTOM installs. Can you imagine the newb support issues when they pull out their sdcards? Or can't figure out how to flash their ROM because they don't have any compatible filesystems on their sdcard?

The stock internal layout makes a slight bit of sense from the vendor's perspective, but from our perspective (i.e. anyone not interested in OTA updates), it is insanely wasteful. You know that in the stock layout, a whole 67.5 MB is wasted on the /cache partition that remains perpetually EMPTY? Even the deathSPL layout leaves, I think, about 30 MB in there. With a custom layout, you get to make FULL use of the internal storage.

I.e., you've got 210 MB there. Why limit yourself to 142?

So here we have a way of making proper use of the full internal storage withOUT having to resort to messy hacks like bind mounts and symlinks. All we do is hand the kernel a better partition table and we can fit any size of system image we like.
[G1 Android Development] frankencat:
This has made my phone run much better with Super E. Thanks Firerat for your hard work!

P.S. I just set it up stock. Are there any changes or tweaks recommended?
[G1 Android Development] bylokk:
Hi@all,

I have applied this Custom MTD partitions patch to my phone with CM6RC2 ROM. I'm sure I followed the instructions completely.

Data is up to 117MB, so no problem with that. But Cache directory is kinda messed up (not the 2MB in size it should have), or is this OK anyway?
[G1 Android Development] lbcoder:
.... go back to the first post of this thread. Read the section labelled "FAQ".
[G1 Android Development] bylokk:
thx, shame on me :o