yashsingh1/xdaforums huggingface dataset:
[G1 General] bunu:
Hope this helps

for a Android 1.5- MLIGN 3.2B (not 3.3) or KingKlick Hero-Sense Hybrid 2.3. VERY FAST Hero ROMs and GREAT for everyday usage. I even had MLIGN 3.2B on my phone for about a month...then cyangoen released 4.2.14.1 and I wanted to try that out but right now I'm restoring MLGIN 3.2B.

for Android 1.6- I will say the latest Cyanogen with the RAM hack or the latest Super D.

Cyanogen- He lets you actually choose if you want the RAM hack or not. If you want the RAM hack then flash the right file via terminal. He has a Nexus One now so he is deving for the g1/mt3g and the Nexus One but he will still dev for the g1/mt3g.

Super D- Pretty good ROM. It is a mixture of Dwang and Cyanogen so it is pretty fast but I found that you can't really run more than 4 apps before it slows down A LOT. But this already has the RAM hack already installed so it is bad for 3D gamers but good for those lazy people that don't know simple terminal commands.

I DO NOT RECOMMEND DWANG RIGHT NOW. He never updated his ROM in like 3 months. I flashed Dwang 1.17.1 (the latest) and I found it way worse than Cyanogen and Super D.

Hope my lengthy advice helped.
[G1 General] Seksay:
Super D

I'm interested in putting the Super D version of 1.6 on my G1 but I'm having trouble finding it. Does anyone have a link?

Thanks
[G1 General] ldrifta:
http://xdaforums.com/showthread.php?t=613809
[G1 Android Development] Macrophage001:
I wanna try his new kernel out but im having some difficulties.

the link to it is:

http://thedroidsector.com/roms?id=42

First difficulty is when I type in:

rwsystem

it says:

rwsystem: not found.

how can I fix this?

sorry if I posted this in wrong section. still kinda new to this =/

Some Extra Just in Case info:

REQUIREMENTS:

His New AOSP 2.1 v1.3 ROM

1. Might need to make the directories to put the ramzswap.ko and xvmalloc.ko files in.

2. If rwsystem and rosystem doesnt work try:

rwsystem alternative: mount -o rw,remount /dev/block/mtdblock3 /system

rosystem alternative: mount -o r,remount /dev/block/mtdblock3 /system

**Thanks for the Help guys**
[G1 Android Development] yokonunz:
do you runned it by root?
[G1 Android Development] Macrophage001:
Did I run it in root?

yes

first thing I did.

I am currently trying it on the recovery console and it doesnt work either.
[G1 Android Development] JAguirre1231:
Not all roms have rwsystem, the default way would be

mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
[G1 Android Development] SarDroid:
Is possible flash this kernel with adb?
[G1 Android Development] Macrophage001:
Ahh ok thanks man so that does the same as rwsystem?
[G1 Android Development] JAguirre1231:
Yep, and then when you do the rosystem just make that

[cod]mount -o r,remount -t yaffs2 /dev/block/mtdblock3 /system[/code]
[G1 Android Development] Macrophage001:
Thanks dude that helps a lot.

Hmm I hope he posts that up for other people that dont know like me lol.
[G1 Android Development] ciwrl:
Wouldn't the following work the same?

su

mount -o rw,remount /system

and then

mount -o ro,remount /system
[G1 Android Development] JAguirre1231:
It should, but the longer way is always more fun ;)
[G1 Android Development] s0mep00p:
are the instructions kind of wrong on the droid sector site...
[G1 Android Development] ciwrl:
No certain roms support the rwsystem and rosystem commands...its a truncated way of doing what me and jag posted
[G1 Android Development] s0mep00p:
no i mean with these two commands:

# cp -f /sdcard/ramzswap.ko /system/modules/lib/modules/2.6.29.6-king/compcache

# cp f /sdcard/xvmalloc.ko /system/modules/lib/modules/2.6.29.6-king/compcache

there are no folders that exist as "2.6.29.6-king", i looked inside the zip for 1.3 and its "2.6.29.6-jac"
[G1 Android Development] Macrophage001:
crap -.- now my fone is stuck at the g1 screen. I think its cuz I flashed the boot.img.

any suggestions?
[G1 Android Development] JAguirre1231:
How did you flash it?
[G1 Android Development] Macrophage001:
He probably made a mistake on the instructions. try it with -jac instead of -king
[G1 Android Development] Macrophage001:
Through terminal emulator
[G1 Android Development] JAguirre1231:
Then you should be having no problems. He did say it could take a while to boot
[G1 Android Development] Macrophage001:
yeah true i guess im just impatient.

ima post again after about 20 minutes to say whether it worked or not...

...although I was only able to flash the boot img nothing else then I turned off and wiped everything but I dont think thats gunna affect anything...is it?
[G1 Android Development] olearyp:
EDIT: Huh, apparently my blind guessing is wrong. Go about your business.

THE FOLLOWING STATEMENTS ARE DEPRECATED BY THE EXPERIENCES OF OTHERS:

I'm going out on a limb and guessing that if you were to boot the new kernel, `uname -r` would expand to "2.6.29.6-king". Follow the directions, creating the folders if needed. That's where the kernel is going to go looking for its modules. Best to keep your kernels separate. If you boot the new kernel with the modules in the wrong folder, you won't have anything that's built as a module (wifi, compcache, etc.)
[G1 Android Development] Macrophage001:
hey umm jic this doesnt work do I just need to flash the old boot img and if so does anyone have it? idt I have it anymore but ima check.
[G1 Android Development] JAguirre1231:
It will be in the rom you had before (in the update.zip) if you need it
[G1 Android Development] Ace42:
So this is the kernel he plans on putting in all of his 2.1 roms.Hope this means they will see a update in the near future.
[G1 Android Development] wwwhershcom:
you are right, its is "2.6.29.6-jac". King made a mistake is the instructions. I just tried "-jac" and is worked fine.
[G1 Android Development] Macrophage001:
k thxx again. damn i must be getting annoying huh? sorry.
[G1 Android Development] olearyp:
My earlier guess updated. Thanks. Since you've booted the new kernel, though, do you mind posting the results of a `uname -a'? Just curious.
[G1 Android Development] pepe6934:
Booted the new kernel...

# uname -a

Linux localhost 2.6.29.6-king #1 PREEMPT Sun Jan 31 01:00:02 PST 2010 armv6l GNU/Linux
[G1 Android Development] Firerat:
lol, I was going to question the -jac -king thing myself

do you have the '-king' in modules now?
[G1 Android Development] wwwhershcom:
Linux localhost 2.6.29.6-king #1 PREEMPT Sun Jan 31 01:00:02 PST 2010 armv6l GNU/Linux
[G1 Android Development] pepe6934:
nope still 2.6.29.6-jac
[G1 Android Development] Macrophage001:
Am I like the only one having problems here?

I type in:

mount -o rw, remount -t yaffs2 /dev/block/mtdblock3 /system

and then it says;

Usage: mount [-r] [-w] [-o options] [-t type] device directory

???
[G1 Android Development] wwwhershcom:
for me this isn't running well at all. serious lag after I switched.

Can some one else pst there experience so far?
[G1 Android Development] Firerat:
ok kewl, going to have a stab myself, because tbh I would have thought it would fall over without modules, but my Linux is a little rusty
[G1 Android Development] ultma75:
try this code

su

mount -o rw,remount /dev/block/mtdblock3 /system
[G1 Android Development] Macrophage001:
Thank you man soooo much =)

but damn its like one problem after the other.

now its saying that the path does not exist when i type in:

# cp -f /sdcard/ramzswap.ko /system/modules/lib/modules/2.6.29.6-king/compcache
[G1 Android Development] ultma75:
no problem..
[G1 Android Development] JAguirre1231:
Try

mkdir /system/modules/lib/modules/2.6.29.6-king/compcache
[G1 Android Development] Macrophage001:
lol I feel like the only dunce in this forum.

I wish he posted that with the instructions -.-
[G1 Android Development] ultma75:
lol it would help
[G1 Android Development] Macrophage001:
Last question cuz im getting annoyed of myself lol.

How do you check to see if you have the kernel?
[G1 Android Development] Firerat:
type

uname -a

in terminal
[G1 Android Development] Macrophage001:
yeah...that doesnt work for me

tried but it says:

uname: not found
[G1 Android Development] Firerat:
ok, go settings --> About Phone

near the bottom you will have kernel version.

but I'm not sure why uname isn't working, maybe you don't have symlinks to busybox,

try

busybox uname -a
[G1 Android Development] ultma75:
i think the kernels meant for people with kingklick rom already.. so my advice wait till his new release to try the kernel
[G1 Android Development] Macrophage001:
lol too late..

I already got it but now I rebooted my phone alittle while ago again and its still at the g1 screen =/

hope it works..dont want to have to repart my sd again.

and thanks firerat

btw, do you guys know of a way to see if the g1 is actually doing something while its in the g1 boot up screen? cuz I saw something about that but I forgot where
[G1 Android Development] Ace42:
You would have to wipe not repartition your sd. You only repatition if you want to make something bigger or smaller or want to add swap.
[G1 Android Development] Firerat:
same here, I did read 15min somewhere, but your SD should fine, I pulled the battery earlier and did a nandrestore, everything back as it was ;)

you did do a backup?

if not don't worry, all you need to do is re-flash your current ROM, you shouldn't need a wipe as you are not really changing anything.

anyway, made myself a .sh script to do all the boring stuff

on G1 screen atm, will leave it 20min or so :)
[G1 Android Development] Macrophage001:
yeah I tried doing it that way but didnt work so I just repart.

I backed up my stuff up anyways so im good =)

idk y but it makes me feel better if I just do a re-partition.
[G1 Android Development] shafty023:
Ladies and Gentlemen, a kernel can be used by any ROM for the most part. It's the init.rc (ramdisk) in King's kernel that will cause your phone to sit at a G1 screen if you're not using his ROM. If you want to use his kernel on a different ROM just unpack the boot.img and grab out the boot.img-kernel and repack the boot.img with the ramdisk from your current ROM you're running. Then push over wlan.ko and the compcache modules to your phone. I don't believe his kernel supports squashfs (as most are starting to not use) so if you have /system/modules/modules.sqf then this kernel is not for you. To check if that file exists do:

adb shell mount | grep modules.sqf

To unpack/repack a boot.img

http://xdaforums.com/showthread.php?t=443994&highlight=unpack+boot.img

To copy wlan.ko and CC modules to your phone. Do this from RECOVERY

adb shell mount /system
adb push wlan.ko /system/lib/modules/
adb shell mkdir /system/modules/lib
adb shell mkdir /system/modules/lib/modules
adb shell mkdir /system/modules/lib/modules/`uname -r`
adb shell mkdir /system/modules/lib/modules/`uname -r`/compcache
adb push xvmalloc.ko /system/modules/lib/modules/`uname -r`/compcache
adb push ramzswap.ko /system/modules/lib/modules/`uname -r`/compcache
adb shell umount /system
adb shell reboot bootloader

Then when it enters the bootloader

PATH_TO_YOUR_SDK/tools/fastboot flash boot boot.img

Where PATH_TO_YOUR_SDK is literally the path to your sdk,

that is not a command

,

it is not an environment variable

, you need to fill it in with the path to the android sdk on your pc. I know no matter how clear I make that someone will literally type it into their command prompt.

This is all I'll explain on this matter as flashing custom kernels is for experienced people. It's not something that can be taught in a quick tutorial as you need to understand what makes up a boot.img, what modules pertain to a kernel, supported filesystems (squashfs), etc etc.
[G1 Android Development] Macrophage001:
I tried to unpack it using:

gunzip -c ../boot.img | cpio -i

Yeah there must be something wrong there. was wondering if you could explain it a little better than the instructions in link?
[G1 Android Development] Firerat:
Nothing wrong with the instuctions, basically the one big boot.img file is in 4 sections your only interested in the first 3, first part is the header and is 2k long, the next is the kernel this as long as the kernel is big. its end is where the third section starts

this third section is the ramdisk its beginning is indicated by hex value 1F 8B (proceeded by the kernels bunch of zeros tail ;)

you need to delete the first 2k and the '1F 8B' onwards and save as kernel ( use hex editor )

then you need to delete upto the 1F 8B and save as ramdisk.gz (again with hex editor), you can then gunzip/cpio it, mess about files, and follow the packing instructions

but for now just try the new ROM :)

PS

http://www.linuxfromscratch.org/

is step by step, will take a while but its all good fun ;)
[Touch Pro, Fuze ROM Development] JesusFreak316:
I have been following the Android scene here pretty regularly but the os I have always really wanted is a full fledged Linux. I heard about, and wanted a N900 because of Maemo but I'm too poor to buy one ;). I then heard about the Mer project https://wiki.maemo.org/Mer to port Maemo to other devices and saw it booted on the kaiser http://xdaforums.com/showthread.php?t=565480. On page two of that thread it is stated that someone (Mdrobnak) got it up and running pretty well on his Fuze with a couple tweaks to Xorg.conf, the kernel, and to the splash screen (resized to 640x480). I've been working over the past few days on getting it to start on my fuze but haret keeps giving errors about pc_clk_disable. I resized the splash, changed Xorg.conf to be 640x480 and did the rest of the directions on the Kaiser thread, but no luck. I would love to get a port of this going, as being able to use ~95% of Ubuntu packages working on my phone would be awesome. I wasn't quite sure how to patch the kernel; that would be the zImage, right? Any suggestions?

I'm going to be on #mer and #htc-linux irc on freenode quite a bit until we get this working well if anyone wants to discuss things, not that I can contribute much. :p

Would it be possible to create a rootfs.img file similar to how XDANDROID does it for people too lazy to partition their card or just plain suck like me? :p
[Touch Pro, Fuze ROM Development] TheDeadCPU:
Sounds interesting! Keep us updated!
[Touch Pro, Fuze ROM Development] needmoney:
Oh god! Ill be in 7th heaven if it's going to be done!

I think you can use the zImage of xdandroid, maybe it'll work
[Touch Pro, Fuze ROM Development] JesusFreak316:
I tried the xdandroid zImage but it didn't work. This is really a call for help. I really don't know what I am doing, lol. I'm not even close to being a dev.:p Try out the steps on the Kaiser thread but use the stable 0.16 distribution as the testing links don't work. See if you can figure anything out.
[Touch Pro, Fuze ROM Development] Mr_stickz:
Maemo on the Raph ? that would be great!:D:D:D maybe we could run it in dual boot with android and abandon WM for ever !:D
[Touch Pro, Fuze ROM Development] phhusson:
To get X working, use glemsom's kernel, and add msm_fb.fix_x=1 to cmdline.

For touchscreen, you might want to add msm_ts.raw=1 (but it can also work without it)
[Touch Pro, Fuze ROM Development] JesusFreak316:
Thanks, phh. Will try it when I get home.
[Touch Pro, Fuze ROM Development] dcordes:
that's the old and ugly msm_fb refresh hack.

I will update here once I have xorg working on kovsky and kaiser.
[Touch Pro, Fuze ROM Development] JesusFreak316:
Man, I actually feel like this is getting places. :D Got Phhusson from XDANDROID and dcordes from the original Android on Diamond thread. Quite the star power. :)

@dcordes: What needs to be edited to use VGA; just the first screen resolution dimensions in Xorg.conf?
[Touch Pro, Fuze ROM Development] dcordes:
what image are you using?
[Touch Pro, Fuze ROM Development] JesusFreak316:
I'm using the Smartq5 from here: http://wiki.maemo.org/Mer/Releases/0.16. My main problem is with the kernel though I think; haret hangs after about 15 seconds; I'm gonna create a log of it.
[Touch Pro, Fuze ROM Development] LordKiwi:
On my Raph300 I can login on the terminal using the Q5 image. I was using the latest zimage from gelmsom. But kernel is screaming some stuff a bout a clock not having an ena bit and something about an rpcrouter being blocked. When I try to start X, I get an error loading libpicacces.so.0
[Touch Pro, Fuze ROM Development] JesusFreak316:
I get that same error, but Haret hangs when I get it. Please share what you did: e.g. editing xorg, exact zImage used, what you used to partition, your default.txt, whether you edited the splash screen image etc. I'd like to get a database of sorts of people's configurations. Good to know though. Did you add Phhusson's tip to default.txt?

"To get X working, use glemsom's kernel, and add msm_fb.fix_x=1 to cmdline.

For touchscreen, you might want to add msm_ts.raw=1 (but it can also work without it)"
[Touch Pro, Fuze ROM Development] LordKiwi:
Yes i added the msm_fb.fix_x=1 to the cmdline. Unfortunatly it is not the solution for this problem. We have got some trouble with the libraries. Maybe something is missing.
[Touch Pro, Fuze ROM Development] phhusson:
Last time I tried it worked automatically (I mean for X video output.) with msm_fb.fix_x=1
[Touch Pro, Fuze ROM Development] LordKiwi:
Sorry it works. JesusFreak and I extracted the tar file the wrong way.

I should have type tar -pxvf. I forgot the p which is very important.

Now it stops with a different error.

(**) FBDEV(0): using shadow framebuffer
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"
(II) Loading /usr/lib/xorg/modules//libshadow.so
(II) Module shadow: vendor="X.Org Foundation"
compiled for 1.6.0, module version = 1.1.0
ABI class: X.Org ANSI C Emulation, version 0.4
(EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument
(EE) FBDEV(0): mode initialization failed

Fatal server error:
AddScreen/ScreenInit failed for driver 0
[Touch Pro, Fuze ROM Development] JesusFreak316:
Dang it; I just can't get it to work. I'm the thread starter and I can't do it, lol. Here's what I did:

1. Downloaded 0.16 stable smartq5 rootfs.

2. Extracted the tar to my home folder. (Now that I think of it; I did it with archive manager not the command line, so no -p setting or anything. That could be the problem.)

3. Edited the xorg.conf file to change the resolution to 640x480.

4. Changed the splash screen size to 640x480.

5. Formatted my sd card to ext2 for 1.5 gb and fat32 for .5 gb using command line following these directions for ext2: http://wiki.maemo.org/Mer/Documentation/SmartQ_Installation_for_the_Windows_user and gparted for fat32.

6. I then used the directions on the same pagee as before to copy the file, except using cp instead of mv.

7. I copied haret, a zImage, and the startup.txt that I renamed to default.txt and edited to the fat32 partition.

8. I started Haret.

I attached my default.txt.
[Touch Pro, Fuze ROM Development] LordKiwi:
The formatting is done correct. You should try to use the tar command line wich you can find on the same page. It should solve the problem of loading the library.

•Type sudo tar -pxzvf *.gz and press return. This will now untar the entire 'rootfs' to the card. (Install Mer).
[Touch Pro, Fuze ROM Development] LordKiwi:
I'm an idiot....... I saved my startup.txt as startup.doc. That's why X didn't start.
[Touch Pro, Fuze ROM Development] xdeaTHHhx:
0.17 release

Is possible run the 0.17 realease in raphael more fast than in N810?
[Touch Pro, Fuze ROM Development] JesusFreak316:
Tried it. Didn't work, lol. Well I give up for now; I'm just clogging up the thread. If anyone really wants to help me pm me or get on #htc-linux or #mer to chat. What would be really nice is a .img file of your sd card with mer workingthat I could flash to my card. hint hint. :) Usb image tool is a great program for creating and restoring img files from a memory card.

I have one request that I'm adding to the original post: a rootfs .img file similar to how XDANDROID does it for people too lazy to partition their card or just plain suck like me. :p How hard would that be? If someone could point me to a tutorial I'll try it myself. I'll google it anyways.
[Touch Pro, Fuze ROM Development] gamikzone:
I would really like 2 see symbian s60v5 i miss my nokia 5800 lol, but gd job trying 2 port linux maybe if this device was 480x800 it would be easier cuz maemo and some android devices use that resolution.
[Touch Pro, Fuze ROM Development] JesusFreak316:
Thanks. I wish the screen was 800x480 too for several reasons. However, I thought that the open source symbian didn't support touchscreens though. I just heard about it on Engadget so I don't know that much.
[Touch Pro, Fuze ROM Development] gamikzone:
yea i also saw it there yesterday i checked the symbian site they said all of symbian is open source now, so i dont know also and if it was only 3rd u could possibly do a port but its a good thing that the tp has a keypad but that would be a wast of time :D.
[Touch Pro, Fuze ROM Development] Kangal:
Dear fellow internet geeks

Please focus on getting Mer to work on HTC Touch Pro.

That would be a decent N900 alternative, and much cheaper.

And it would mean I wont have to wait another 5months for the N900 to become available (Aust)

Where the hell is mdrobnak with his tutorial & mer ROM?!!?!

Sorry for offending you geeks, its just my sense of humour, as I once were a humble geek

The only MAJOR improvements to Touch Pro i wish was made:

1) could have increased screen size + pixels to 800x480!!!!

2) could have used A8 instead of old A11, but i can get over it if OS is sexy.

3) they used WinMo: wtf i NEED Maemo5!!!

Seen the evolution of WinMo over many years, now own iPhone + playing with N97.

Wow Symbian has come a long way, longer than WinMo.

OSX is a beast except no multi-tasking = fail!

Why am I posting: I just gotta have a smartphone with slide qwerty, and a really good one without paying AU$900 (ie N900)!

PS: I haven't come back to this site since owning my iPaq h2210 and imate PPC !
[Touch Pro, Fuze ROM Development] JesusFreak316:
Nice necropost. jk ;) But seriously, I'm waiting for fatsal, the developer of android and ubuntu on x1. He said he'll probably make a mer build sometime. I'll then try to get his build working on tp. Until then, I can't do much.
[Touch Pro, Fuze ROM Development] Kangal:
Thank you Jesus (no pun intended).

People so underestimate the power of having a full distro running on these pocket rockets. It would mean backward compatability to an explosion/library of programs.

I liked WinMo back in the days, but now it really isn't appealing.

BTW, I was so hyped about MeeGo, not anymore as it came to my attention that it will differentiate into different versions and wont support cross-compatability like Android.

Dang!

I thought, here is the time for a user-friendly widespread Linux distro to bridge the gap between ARM-and-x86 but it may not be.

Hi-powered ARM processors have never been so admirable!
[Touch Pro, Fuze ROM Development] JesusFreak316:
For some reason people like to abbreviate my name. ;) But yeah, I agree completely. There are certaing desktop apps with no mobile equivalent, such as midi sequencers or Guitar Pro tablature software (important to me). As of right now I'm trying to talk to fatsal about fixing the Ubuntu build but he lives exactly across the globe from me so it's hard to find time. Mer would probably be better anyways as the interface is more mobile friendly but it just hasn't gotten anywhere.