yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] FadeFx:
Oc can only freze but not brick a CPU, over volting is the dangerous thing...

For redbend you'd have to loock in /sbin if the binary is there... i have also read of some open source alternative that can do the same...
[Galaxy 3 Android Development] FadeFx:
Info on redbend for sgs: http://xdaforums.com/showthread.php?t=765724
[Galaxy 3 Android Development] FadeFx:
The unobtainable sourcecode should be in the initramfs as binary, its mostly driver stuff.
[Galaxy 3 Android Development] precurse:
Do we have an initramfs anywhere? I only thought there was a zImage..

Is this the open source alternative you're speaking about?

http://www.glassechidna.com.au/products/heimdall/

And there is a redbend_ua file there. However, it doesn't obey any type of command line arguments. That was the thread I was reading about redbend before actually. According to it: "redbend_ua working binary. (some firmware ship a new binary that does not accept command line parameters)"

Perhaps JPA doesn't accept them?
[Galaxy 3 Android Development] precurse:
I'm just looking at the /fota.rc file... Like, there are lines commented out for yaffs2.

mount rfs /dev/block/stl6 /system check=no

# mount yaffs2 /dev/bml6 /data nosuid nodev
mount rfs /dev/block/stl7 /data nosuid nodev check=no

There HAS to be a way to convert from rfs to yaffs2 with the G3
[Galaxy 3 Android Development] FadeFx:
The initramfs is inside the zimage, i think it should be provided along with the sources also. If not, there is a howto for extracting the initramfs from a zimage in the i9000 section.

Heimdall is an alternative to Odin that is platform independent. However it'd have to be adapted to the g3. I already asked Benjamin Dobell to do it, but he wouldn't for some reason.

Maybe we should ask someone using older firmwares to extract a redbend.ua for testing
[Galaxy 3 Android Development] FadeFx:
I think yaffs2 wont be an option as it isn't for the i9000, since the devices are built using onenand that takes care of wearleveling by itself and wont accept a pure band filesystem since it emulates a block device to the system if i am not mistaken.
[Galaxy 3 Android Development] precurse:
Good call.. I assumed that was it if there was actually one..

http://xdaforums.com/wiki/index.php?title=Extract_initramfs_from_zImage

I believe the /sbin directory is in the initramfs, since there is no /sbin in the factory.rfs file (this file is ONLY /system). I'll see if I can extract it from an older firmware to see how it works. It does look like the samsung bootup scripts for OTA updates is in fact calling:

service redbend_ua /sbin/redbend_ua all

oneshot

Yeah, I was thinking there is more to it. However, I'm thinking it's just a kernel thing... So if a kernel gets built that doesn't require that, and the filesystem matches that - I don't see how that wouldn't work.

I'm just brainstorming. There might really be a technical limitation though.
[Galaxy 3 Android Development] FadeFx:
There in fact is a hardware limitation, since the onenand controller does this on hardware, its not a driver issue at all. That's why the sgs guys use ext filesystems for this... ext4 would be the way to go.

Btw, sorry that i can't help experimenting, but i never have written one line of code in c or c++ nor have i ever compiled a kernel by myself, i am just a Guy reading to much in forums, that's why i know all that for me useless **** and am just happy to share my knowledge to keep others from having to go a way that has already been gone...
[Galaxy 3 Android Development] precurse:
All good. Maybe you will start =)

I got the initramfs extracted now.. I'm tempted to make some customizations to it (like the default.prop, etc). I'll grab the redbend from the older ECLAIR firmwares and see how it works.
[Galaxy 3 Android Development] FadeFx:
Btw, you should rename the thread since this has nothing to do with i9000 anymore :-)
[Galaxy 3 Android Development] FadeFx:
Maybe we could also use some older GPS files in jpb to test if the bug is caused by those files or if it is a kernel issue.

Btw, can you examine the content of datafs.rfs also, or give advice how to mount rfs images?
[Galaxy 3 Android Development] precurse:
I'll have to play around with that.

For unpacking and repacking the zImage file, we have z4 to thank for his scripts: http://z4ziggy.wordpress.com/2010/10/02/z4mod-updated/
[Galaxy 3 Android Development] FadeFx:
I know about that, but i thought you mounted factoryfs.rfs and saw there is only /system folder inside
[Galaxy 3 Android Development] FadeFx:
Found something, it is pretty obvious actually, just mount it on the phone...

http://forum.samdroid.net/f28/howto-extract-files-samsung-rfs-1693/
[Galaxy 3 Android Development] precurse:
You can open the .rfs files with magic iso.. File > Open > (all files).

The directory structure is that of the /system folder. The factoryfs partition gets mounted at boot-time onto /system and the rest of the root structure is contained in the read-only initramfs:

[root@zone initramfs-JPA]# ls
data dev init init.goldfish.rc lib recovery.rc sbin system
default.prop fota.rc init.apollo.rc init.rc proc res sys

So if I can pull apart the initramfs, make changes to the default.prop, etc, and put it back together into a zImage file.. that will be great. That means I can permanently turn on certain things that otherwise weren't accessible (since every reboot they get reverted).
[Galaxy 3 Android Development] precurse:
Yeah I read about that one.. RFS is supposedly backwards compatible with FAT32.. So you should be able to mount it on any linux box easily. I haven't tested this though.

The Magic ISO way is a lot easier.

I wonder how much effort it would take to get Gingerbread on this thing ;-)
[Galaxy 3 Android Development] FadeFx:
Just tried redbend_ua --help on my gf's i5800 running jk1 and it seems like there was some output on the console before the device just rebooted... what effect did you get using newer redbend binary?
[Galaxy 3 Android Development] FadeFx:
I don't think we have much a chance atm since there is nothing to start from, nexus s sources wont be to much help i guess
[Galaxy 3 Android Development] precurse:
I keep getting the following.. no matter what parameters I pass it. No reboot, nothing.. Strange yours rebooted though. No problems though?

# redbend_ua
redbend_ua
log_init
UA/ RedBend Update Agent main
UA/(MakeBMLNodes):
FOTA : Make Block Device Nodes
UA/(MakeBMLNodes): mknod path=/dev/block/bml4, dev_no=35076
UA/(MakeBMLNodes): mknod path=/dev/block/bml5, dev_no=35077
UA/(MakeBMLNodes): mknod path=/dev/block/bml7, dev_no=35079
UA/(MakeBMLNodes): mknod path=/dev/block/bml8, dev_no=35080
UA/(MakeBMLNodes): mknod path=/dev/block/bml11, dev_no=35083
UA/ERROR(get_fota_status) Open /data/fota/fota.status
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
lcd_init(524): Error: failed to map framebuffer device to memory.
: Invalid argument
#

I wouldn't mind trying it, but the onenand and rfs modules probably wouldn't work.. It appears to run .35 instead of .32 that our FROYO runs.
[Galaxy 3 Android Development] FadeFx:
I did a su before... so maybe i just got the same output plus a reboot. I guess it tries to read fota.status to get instructions.
[Galaxy 3 Android Development] FadeFx:
That's the command used inside the update.zip of a hardcore speedmod kernel:

run_program /tmp/updates/redbend_ua restore /tmp/updates/zImage /dev/block/bml7

I guess this does not work on runing system ...
[Galaxy 3 Android Development] precurse:
I've been looking at the source code of eclair and it appears that the code for Onenand is in: drivers/mtd/onenand ..

Confirmed by this guy too: http://xdaforums.com/archive/index.php/t-801223.html

It might be hard to upgrade to the Gingerbread kernel on this phone as long as we're using RFS for it. There's no RFS module beyond the kernel 2.6.32.9 (Froyo), and we can't use the RFS .ko files from the Galaxy S - since it's compiled for a different processor. The initramfs from the Nexus S doesn't even appear to have ANY modules included after I extracted it.

People who are running the Nexus S kernel on the Galaxy S are using EXT4 now (they need to reformat their data partition I think to use that kernel). It shouldn't be too difficult to do that on the i5800 either - since the partition files we flash are just raw files that include partition info. If you hex edit any .rfs file, you'll see "FAT16" headers (since it's just a fat-style filesystem with added POSIX permissions, etc). This is the reason why we can mount these files as regular raw FAT (msdos) block devices easily in Linux or BSD.

As long as we're just playing around with the factoryfs and datafs partitions, there shouldn't be any trouble with bricking our phones. We could then remove the rfs modules from the initramfs completely, and use EXT4 or yaffs2.. This could allow us to build kernels closer to the vanilla android branch.

Oh, and this looks interesting: http://android.git.kernel.org/?p=kernel/samsung.git;a=summary

Looking at the init.rc file from the JPB initramfs:

# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
# mount yaffs2 mtd@system /system
# mount yaffs2 mtd@system /system ro remount
mount rfs /dev/block/stl6 /system ro check=no

# We chown/chmod /data again so because mount is run as root + defaults
# mount yaffs2 mtd@userdata /data nosuid nodev
# mount yaffs2 /dev/bml6 /data nosuid nodev
mount rfs /dev/block/stl7 /data nosuid nodev check=no
chown system system /data
chmod 0771 /data
mkdir /data/system
chown system system /data/system
chmod 0775 /data/system

If we simply changed the init files from the initramfs (and possibly from the factoryfs files), we could easily mount these partitions as any partition type we'd want. This is, of course, assuming that our kernel has built in support for that specific filesystem.
[Galaxy 3 Android Development] FadeFx:
Yaffs2 is a nand filesystem and thus will not work on onenand, sgs guys were discussing that up and down. We have to go for ext4 as i told you already, yaffs2 is a waste of time.
[Galaxy 3 Android Development] precurse:
Gotcha.. I'm thinking of ext4 anyways - as it would be the same effort - was just brainstorming. I've been trying to build a kernel from the source of SGS Froyo, but was getting some errors. The modules are in a separate directory in the source for the G3, but it appears Samsung included most of it inside the tree now rather than out of it.

I'm going to continue to try to build a kernel from it - at least comparable to the kernel we're running in JPA/JPB.

I also emailed Samsung asking if they could send me the source code for the G3 - but I don't think there's a chance of that happening.. But it's wishful thinking =)
[Galaxy 3 Android Development] Benjamin_L:
Isn't ext4 unsuited for flash memory. I read something like that over at phoronix. Can ext4 implement wearlevelling?
[Galaxy 3 Android Development] precurse:
Wear leveling is typically handled by hardware/firmware. SSDs, SD cards, CF cards ,etc. usually have wear leveling built into the firmware.

I'm not sure how Samsung handles it with this phone, but I'd assume it's handled at a lower level than the filesystem.. But someone feel free to correct me on that.

... Update

You can read about it here: http://www.samsung.com/global/busin...y/downloads/LinuStoreII_GPL Compliance_10.pdf Under the "Samsung Block Device Driver" section.
[Galaxy 3 Android Development] Techie87:
precurse, i have to say : you are doing some nice research on this phone :-)
[Galaxy 3 Android Development] precurse:
Interesting...

http://patchwork.ozlabs.org/patch/71734/

> This patch is for onenand support of s5p6442 SoC.
>
> Cc: Minkyu Kang <mk7.kang@samsung.com>
> Cc: Kyungmin Park <kyungmin.park@samsung.com>
> Signed-off-by: Joonyoung Shim <jy0922.shim@samsung.com>
>
> ---
> drivers/mtd/onenand/samsung.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mtd/onenand/samsung.c b/drivers/mtd/onenand/samsung.c
> index f2be687..cbcf83b 100644
> --- a/drivers/mtd/onenand/samsung.c
> +++ b/drivers/mtd/onenand/samsung.c
> @@ -67,7 +67,7 @@ do {	\
> #define MAP_01	(0x1 << 24)
> #define MAP_10	(0x2 << 24)
> #define MAP_11	(0x3 << 24)
> -#elif defined(CONFIG_S5PC1XX)
> +#elif defined(CONFIG_S5PC1XX) || defined(CONFIG_S5P64XX)

Same CPU as the G3 (S5P6442)

Samsung talks about u-boot in their block device pdf I listed previously.. Looks like the G3 could be using U-Boot as its bootloader.
[Galaxy 3 Android Development] precurse:
I'm just hoping I can plant the seed for someone (or myself) to take off with it and do something awesome...

We're pretty fortunate to have a tool like ODIN to work with. However, if Samsung simply was more open with their hardware, we wouldn't have to sidestep the way we are.

I really hope Google's push to have vendors open up their hardware (the reason Android was originally intended to be) will have some pull here. We need more phones like the Nexus series - the complete opposite end of the spectrum to the way the iPhone operates.
[Galaxy 3 Android Development] god_md5:
is the way add onenand driver to old Eclair kernel?

other libs is not open source
[Galaxy 3 Android Development] precurse:
Not sure if I understand entirely. The onenand driver is under the drivers/mtd/onenand folder in the eclair source tree right from Samsung.
[Galaxy 3 Android Development] Gsam101:
Readonly for RFS. If you change some files (add) it will do nothing good.
[Galaxy 3 Android Development] god_md5:
how to change /system file format to ext2?

if the initramfs only in /system ,system how to know /system is which format?

is the initramfs have in bml4 "bin" like zimage+initramfs ?
[Galaxy 3 Android Development] precurse:
Not sure if I understand. zImage contains the kernel and initramfs in 1 file.

initramfs is root, so " / ". It contains everything not in /efs, /cache, /data, or /system.

It's a read-only ramdisk that gets reset every time the phone gets rebooted.
[Galaxy 3 Android Development] god_md5:
so if need /system mount to ext2

need to rebuild a new Kernel with ext2 and edit the initramfs is mount it

in bml4 one bin,than the /system is ext2

look very hard to change the /system to ext2...
[Galaxy 3 Android Development] precurse:
Well in order to mount /system as ext2, initramfs's init.rd file will need to be changed. It's currently set to mount /system as rfs.

We could have a universal init.rd that will mount it either rfs or ext2 depending on partition type - that's not hard at all, and only requires a simple change and a kernel/zImage rebuild

If you choose ext2, then the factoryfs.rfs file will need to be recreated as an ext2 file instead of rfs to flash with ODIN. The factoryfs is a raw partition image that gets flashed on /dev/block/stl6.

This is still all theory, but I have a strong belief this would work.
[Galaxy 3 Android Development] FadeFx:
If its that easy, it should not be to hard to change all partitions to ext2. This would give major performance boost, but also is somewhat dangerous to suffer data loss when not shut down propperly
[Galaxy 3 Android Development] precurse:
For the /system partition, ext2 is more than adequate since it's read only by default..

For the /data partition, JFS or ext3/4 are better options I think since they are journaled and can sustain power loss better.

We need someone to test those modules though ... even if they don't play on using ext2.

I REALLY want the sources for Froyo so I can mess around with it more easily. I don't have the time to try to hack the source code of the i9000 together to get it to work on the i5800. I hope Samsung hurries up.
[Galaxy 3 Android Development] precurse:
Nice.. So they use your sdcard as the /data partition? That actually would make it SUPER easy to do - no worrying about creating a datafs.ext4 file.. just simply format the SD card.

It's too bad your girlfriend has the i5800.. otherwise you could help test stuff out =)
[Galaxy 3 Android Development] FadeFx:
The data partition is on the built in 8gig internal memory, it is kind of SD card but not removable, and it is like this by default, the partition layout is unchanged here
[Galaxy 3 Android Development] FadeFx:
Btw, eventually it makes sense to port the cwm recovery that hardcore is using to the g3 so we have a base for true lagfixing without loop device i think it actually runs, but crashes when you try to do something in it. So eventually there is only minimal adaption work to do.
[Galaxy 3 Android Development] unreal3000:
http://xdaforums.com/showthread.php?t=895164

with this be of help??
[Galaxy 3 Android Development] precurse:
We would need to go to eclair for native mounting of /system with ext4. For Froyo (at this time), the initramfs needs to be changed and the ext4 module would need to be added to that as well. Personally I'd rather stick with Froyo.

The initramfs is not fun to pull out and put back into zImage - I've tried it. The only repackager I've found are for the SGS, and there are some messed up options that I don't have the time to figure out the G3 version of.

So either we need to use the loopback method, or stick with rfs for everything.

If someone wants to look into it, the thread for the initramfs repacker is here: http://xdaforums.com/showthread.php?t=789712

This could allow us to at least use ext2 natively on our /data partition.
[HD2 General] wasaiisno:
it is good news,the dft has been released the android rom's video

it is cool

i am new ,so i can not put the url out ,sigh
[HD2 General] wasaiisno:
Everybody may go to look at the video frequency

it is name “tudou” in china
[HD2 General] Seven Goals:
I'm a Chinese,this is true
[HD2 General] H3ALY:
I think this is the video:

http://www.tudou.com/programs/view/59xxkXhh8Ck/
[HD2 General] Seven Goals:
Right，that's it
[HD2 General] rlydiard:
Just to give you guys a head's up on all this, if you do a search, you can find where all three links were already posted on this HD2 forum.
[HD2 General] H3ALY:
I've upload a copy onto YouTube incase anyone has a problem buffering from the website.

http://www.youtube.com/watch?v=MJugZtIZVwc
[Droid Incredible Q&A, Help & Troubleshooting] MondoMcNubb:
I am using an HTC Incredible w/CM6.1 and LauncherPro. I'd like to know if there is a way to hide the text under the icons in the app drawer to leave just the icons. I found a few mods for "Rosie" that do this, but I don't know what Rosie is, much less how to make those work for my setup.

Anyone think they could help?
[Droid Incredible Q&A, Help & Troubleshooting] jtcarnes:
Rosie is the Sense launcher, so it won't help you with LauncherPro.

I'm not a LP guy, but I do know that ADW can do what you're looking for. I don't see why LP wouldn't have the option too...
[Epic 4G General] ksweat2292:
i flashed the stock mms apk and the return key got replaced by the smiley face button

is there a way to change this?
[G Tablet General] muerteman:
Hey guys,

I found this while reading the comments for engadgets very poor review of the new archos tablets, and I was wondering if it would be helpful. I know nothing about what our problem actually is, but maybe this can help.

http://forum.archosfans.com/viewtopic.php?t=44084&p=302959

Muerte
[G Tablet General] roebeet:
Thanks for this - trying it out, now. I still get the long "scanning for media", so I'm not sure if this will have any effect.

The "dot", btw, means that it's a hidden file (at least in the *nix world).

EDIT: My music app is no longer seeing any of the music on SDCARD2. This might actually be a good thing as that means it's not adding the files to the local DB. To be honest, if I had a choice between not having them scan versus scanning and erasing my stuff, I'd take the former.
[G Tablet General] gotwillk:
i'm still getting the super long scan on bootup, even after putting a .nomedia file in the root of sdcard2. i have a feeling its not even scanning the sdcard2 because i unmounted and popped the card out and i still have that scanning message. or maybe its just stuck? i have no idea.
[General Topics] YoungBloodz:
I have the chance to get a new phone, and I have decided its going to be between the G2 and the Samsung Captivate. I'm on the AT&T network, and I'm probably not gonna have data, so the speeds of data and 2G/3G network speeds shouldn't be that much of a factor. I did research on them and both of them seem pretty good but I'm not sure which of the two I should actually get.

I do text a lot so the keyboard on the G2 would be a little helpful, but the Captivate has that nice Super AMOLED screen. I do however plan to be doing a lot with the phone, like rooting it, so please keep that in mind as well.

What would some of you suggest? Any help would be great. Thanks.
[General Topics] Shammyh:
Captivate.
[General Topics] Tchem:
Don't know much about the g2 but I do currently own a captivate and its a great phone very easy too root and install roms. I would start from there research which one is easier too root and which ones have the best roms and what not.

Never was a big fan of a physical keyboard. so I can tell you that the typing on the captivate is pretty accurate. Also the screen is bigger! Lol but enough about my bias opinion just find out the hacking capabilities of both as well and go from there

But to make a long story short like the guy ahead of me.

Captivate FTW

Sent from my phone exuse the typos(if any)
[General Topics] nbs11:
If you plan to stick with the stock ROM then get the G2. Otherwise, get the Captivate. With a custom ROM the Galaxy S phones blow all the others away.
[General Topics] OGCF:
Both are great phones, but I think all of the people recommending the Captivate are forgetting that the G2 is sort of 'future-proof' in that it has HSDPA+ built in for T-Mobile's kinda-sorta 4G network. It's really up to you if you think you'd need that.

Another question to ask yourself is do you need a physical keyboard or not. And finally, which phone do you prefer as of right now?
[General Topics] YoungBloodz:
Well I'm not really sure about the physical keyboard, if the touch keyboard thats on the Captivate is good, then I guess I wouldn't really need the physical keyboard. I also remember hearing that it has Swype on it as well, so I dunno if Swype is actually faster than a physical keyboard or not. The 4G connectivity would be good, but I don't have T-Mobile so it doesn't really apply to me all that much :D
[General Topics] Pickx:
Do you require a keyboard or have a lot to gain from having one? If so, htc Vision is your best bet in the market right now.

Otherwise, save your money because single core processors will be phased out in a matter of months.
[General Topics] Tchem:
Its funny you say that they are coming out with dual core processors but still using the same battery as single core. So imagine how fast the battery will fade on you. On top of that the price of the phone will almost double. So I give em late 4th quarter 2011 before these phone will actually blow up.

Sent from my phone exuse the typos(if any)
[General Topics] eleazar6:
The G2 is the fastest (other than games... its close tho) with a little overclocking, and has a clearer, smaller but less bright screen. I wish I had that extra .3" sometimes. Physical keyboard is sweet, but I can type near as well with the on screen keyboard on the galaxy s'. They also have a better vibrate-on-keypress. Did I mention that this phone is fast? Stuff just does what you tell it.

Also, I know this is just the general forum but the dual core info... I wouldn't believe much of it
[General Topics] shanghei:
If you plan on using GPS at all, stay away from the Captivate.
[General Topics] Tchem:
well said I forgot all about gps

Sent from my phone exuse the typos(if any)
[General Topics] T.C.P:
+1 also if u dont want to be wait for official roms get the Vision [i have a vibrant too so just saying]