yashsingh1/xdaforums huggingface dataset:
[Wing, P4350 ROM development] ivanmmj:
Depending on how your XIP is set up from that other kitchen: Does it have a MSXIPKernel folder?

If not, we can get around that.

Don't replace SYS folders, just dump out the old ones and use the new ones only. There might be DSM's that change names and that will cause a problem. Did you convert those modules to files that I mentioned?
[Wing, P4350 ROM development] ace10134:
The 23016 kitchen doesn't have a MSXIPKernal folder. Neither does Holly's kitchen.

When replacing SYS folders, I delete the entire SYS folders and then copy in the other new folders. I don't just tell it to "replace", since I don't trust what it's doing, so that's all good.

And I couldn't find those "nk.exe" folders or whatever you told me to convert from modules to files. So I'm not sure about that. You can download the kitchen that I linked to in the last post and look around, see if you can find those.
[Wing, P4350 ROM development] ivanmmj:
1. I should say, keep your original ROM's VM folder in the SYS but everything else throw away and replace.

Don't touch the nk.exe. Look around for platformrebuilder. It comes with a tool that will let you use the DSM's in the XIP to organize the XIP files. Use that and the copy all the files/modules in the MSXIPKernel into your XIP, leaving all the other older files there.

The files that I want you to convert are all the files in the adobeflash folder and the browsingie folder.
[Wing, P4350 ROM development] ace10134:
I always do that, Ivan. That's straight from your guide. Also, there's no need to keep shell32 and shellres, since my SYS folder is the same resolution? And I don't need to keep the WinCLES folder either? Just keep VM? Ok.

I'll find PlatformRebuilder. And I'll look at those files->modules.
[Wing, P4350 ROM development] ivanmmj:
Correct. My guide is a little on the older side. Don't keep the older shell stuff or it will cause problems with the newer builds. Especially the 6.5 builds.

Same with the Wincles folder. JUST the VM.

And remember, modules to files. Check to see if there are even any modules on it right now. They might have already been converted by someone.
[Wing, P4350 ROM development] ace10134:
What do modules look like, anyways?? I haven't looked up those, yet. Looking at the Platformbuilder thing right now.

And here's what the AdobeFlash and broswingie folders look like: (There's no AdobeFlash_0409, seems like it's all in one folder) (sry about small resolution, fixing it...)
[Wing, P4350 ROM development] ivanmmj:
Those folders within the packages that have file names are modules. (Also, the 0409 folders are just the language files for wwe (English).)
[Wing, P4350 ROM development] ace10134:
So then those DO need to be changed? I'll look into it tonight. Hopefully I'll get 6.5 working today, that'd be cool.
[Wing, P4350 ROM development] ivanmmj:
Yes. They need to be converted into files. If not, they'll throw off random errors that will cause the ROM not to boot for seemingly random reasons. (My SuperJustKitchen also has the feature to turn modules directly into files and viceversa. (Built-in feature of ervius's visual kitchen which is the base to my kitchen.)
[Wing, P4350 ROM development] ace10134:
K cool. Yea I tried making a kitchen off of Ervius's, but just got too tired. I'll tell you when I start working on 6.5 tonight.
[Wing, P4350 ROM development] ace10134:
Ivan, one more question...

When you're porting the XIP, do you also need to use the "xip.bin" or "out.bin" or whatever you call it? I know that it's used to dump the XIP, but do you still need it after that? Or just leave the old one and it won't make a difference?

And I think I'm about to try 6.5 again, once I get home.
[Wing, P4350 ROM development] bigdee:
is this rdy for use ? where is downlod link ?looking good keep up good work
[Wing, P4350 ROM development] ivanmmj:
You don't need the new one. Some kitchens keep a copy of the original one in the ROM folder, but it's not really needed, either.
[Wing, P4350 ROM development] ace10134:
NO.

It's NOT a ROM. It's for discussion. I'm making a 6.5 ROM as we speak.

IVAN!!!!!!!!!!!!!

Thank you soooo much dude, I got 6.5 working!!! Made my own ROM!! Ivan, I'm gonna donate to you soon. that PackageBuilder worked, got it working in about 30 minutes, easiest thing I've ever done! I should probably dontate to Bepe, too, for the awesome tool. But we'll see. I know you, Ivan, so I wanna donate to you. And you're the one that inspired me, youre the one that stuck with the Wings, you're the one that's the boss.

Ok. I'm just so freakin happy I cooked 6.5!!!!!!!!!!!!!!1 Ok. I think I'm done. Thanks again Ivan, I'll donate some time this week or so. If I donated now, I'd end up giving you $100. I'm just in the moment right now.

Ok. now done. Thanks again Ivan. I'm gonna optimize this 6.5 babby.
[Wing, P4350 ROM development] ace10134:
So, Ivan, you probably know why ExtROM freezes in WM6.5, right?

Right after you flash your phone, calibrate the screen, the initial setup tries to run, and then it freezes the phone. Soft reseting makes it work.

I know it's a problem with the ExtROM, because when you remove Config.txt, it all works fine.

Did you ever find a fix for it, Ivan? Or did you just do what I did?
[Wing, P4350 ROM development] ace10134:
And THIS is how I got Windows Mobile 6.5 ported.

The PackageBuilder worked perfectly Ivan, I didn't even have to do the modules to files thing.

The guide took longer to write up than it did to originally figure out!
[Wing, P4350 ROM development] ivanmmj:
haha. Awesome to hear that it worked! ^_^

As far as it freezing, mine doesn't freeze so it must be something that your ExtROM or your local config.txt file is calling. Show me what's in your config.txt.
[Wing, P4350 ROM development] ace10134:
Well it's basically an empty Config.txt I think it goes something like this...

LOCK:Disabled

XML:/ExtROM/Wing.Dev.01.xml

RST:Reset

LOCK:Enabled

I know thats not formatted right, wrote it from mmy phone. But thats the only thing it has in it, the XML..
[Wing, P4350 ROM development] ivanmmj:
Strange.... it might be having a hard time accessing your ExtROM.

What's in that Wing.Dev.01.xml? If it's your file, just move it to the ROM and call it from /Windows/Wing.Dev.01.xml instead and see what happens. (I never use the ExtROM (since everything is already cooked in my ROMs, so I've never noticed whether it freezes 6.5 or not.)
[Wing, P4350 ROM development] ace10134:
Well it's actually called WingDev_Config.xml, and it looks like this...

<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\OEM" translation="filesystem" >
<parm name="ExtROMVersion" datatype="string" value="WingDev.01" translation="filesystem" />
</characteristic>
</characteristic>
</wap-provisioningdoc>

So what does that do, then? You have any ideas on what to do about it?
[Wing, P4350 ROM development] ivanmmj:
It just sets the ExtROMVersion in the registry. Not needed. (But strange... that means that you have a Dev ExtROM from Tmobile...)
[G1 Q&A, Help & Troubleshooting] darkphoenix2012:
I could have sworn that when I first used the sms widget it prompted me what application I wanted to use for the buttons, compose msg mainly. I can't seem to make it work with handcent sms, even after clearing default programs in application manager. Anyone have any ideas?
[G1 Q&A, Help & Troubleshooting] h.nocturna:
Its never asked me what application I wanted to use it with... sorry I'm of no help...
[JASJAR, XDA Exec, MDA Pro General] kazparov:
Is it possible to flash my uni via SD card?

i would like to install a lite rom, but i cant do the traditional method with windows 7, dont know why
[JASJAR, XDA Exec, MDA Pro General] orb3000:
It would be nice if you do a search before creating a new thread:eek:

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

And there are more threads regarding this...
[JASJAR, XDA Exec, MDA Pro General] kazparov:
i saw that, but my phone is G4 :(
[G1 Q&A, Help & Troubleshooting] esmith972:
I have the Hero build and I've found it necessary (along with everyone else) to reboot the phone daily. I was wondering if there was some kind of cron-esque script made so it would reboot the phone daily.
[G1 Q&A, Help & Troubleshooting] alritewhadeva:
cron-esque? Well how hard is it to press three buttons?
[G1 Q&A, Help & Troubleshooting] BrooklynAvi:
Provide solution, not comments

@alritewhadeva, while many of your posts are quite useful, and you have personally assisted me in the past, I don't think your response is at all productive for this forum. While it may not be difficult to "press three buttons," the question is certainly a valid one and deserves to be treated as such. Perhaps he would like his phone to auto-reboot at 6am so it's ready to go when he wakes up. Either way, don't waste time by mocking the question. It is not productive and wastes everybody's time.

While on the subject of cron, I too was wondering what cron-esque solution(s) may be available to Android. I will look into it myself and post my findings, if any, here.
[G1 Q&A, Help & Troubleshooting] dumfuq:
The cron daemon is available in busybox. Haven't tried it but you should be able to start it on boot in userinit.sh or whatnot and make an actual cron job for reboot.
[G1 Q&A, Help & Troubleshooting] B-man007:
There is a script in the development section that has scheduled reboots. it was recently posted and should be on somewhere on the first 3 pages (probably the first)
[G1 Q&A, Help & Troubleshooting] BrooklynAvi:
Scheduler Location

Here is the post that has the scheduler app. Truth be told I am about to try it out for myself so at the time of this post I know nothing about it. I'm just posting its location for anyone who comes across this thread via searching for "cron."

http://xdaforums.com/showthread.php?t=558822
[G1 Android Development] alritewhadeva:
*applaudes* awesome. Should be added to helpful threads.
[G1 Android Development] phantasm714:
very nice! perhaps add a "(How-To)" prefix to thread??
[G1 Android Development] nicholasbithell:
Everything was going great in setting this up until I got to this part "gedit /etc/udev/rules.d/51-android.rules"

I cannot find "51-android.rules" inside of "rules.d"

Any thoughts>?
[G1 Android Development] wddglr:
it does not exist, you will make it.

do the command as stated above.

gksu gedit /etc/udev/rules.d/51-android.rules
[G1 Android Development] cynofox:
Damn you beat me to it!

I was just thinking earlier about doing this same "How-To" guide, I was surprise to see it posted just now.

Anyways, great job!
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
Can someone sticky this thread. Now I have ADB & fastboot on my Win7, Ubuntu, and OS X Partition. Thank you wddglr. :D
[G1 Android Development] jay22are:
bravo...linux rocks even better now!...
[G1 Android Development] savethechicken:
Awesome tutorial for setting this up. Have been using adb/sdk on ubuntu since oct. but this would have saved me some headaches back in the first couple of weeks.

The onlything that is not clear and/or confuses me is

Setting up the udev to recognize the device.

SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"

Have never used this (will now to see if it will do anything) and the only problem i have is that sometimes i have to kill-server to get it to connect correctly but i have seen this happen to almost everyone on many forums since the 9.04 came out. And even after putting this file on the computer i have had the problem.
[G1 Android Development] wddglr:
It happens to me also from time to time. especially when i reboot and want to go into adb while the device is rebooting. although that file, 51-adndroid.rules, is what helped me get adb to recognize the device. the guide on developer.android.com talked about 50-android.rules but after a few deep searches i found this: http://groups.google.com/group/android-developers/browse_thread/thread/1d3488c601243686
[G1 Android Development] nicholasbithell:
Okay A few questions for you....

First I fixed the whole "couldnt find the (51-android.rules) file now I am having issues with executing ADB!

When in terminal this is what I get...

"root@ubuntu:/home/nick# /AndroidSDK/tools/adb

bash: /AndroidSDK/tools/adb: cannot execute binary file

root@ubuntu:/home/nick#"

and I also noticed something different from when I start terminal the first lines now state

"bash: ﻿: command not found

nick@ubuntu:~$"

I dont remember the first line ever being there, but I could be mistaken!

Any help would be greatly appreciated!:)

Edit: You state creating "Mount point: /AndroidSDK" During Installation, and what I did was Just place my AndroidSDK at root so it is at "/AndroidSDK". I dont know if this makes a difference.

I am actually running ubuntu 8.10 ha! I just tried to update But I keep getting errors! is there anything I can change to get this to work on ubuntu 8.10?
[G1 Android Development] wddglr:
okay, a few things -

seems like your .bashrc file isn't setup right (?)

make sure that the two lines you inserted into it are on separate line

#AndroidDev PATH
export PATH=${PATH}:/AndroidSDK/tools

because maybe export PATH=${PATH}:/AndroidSDK/tools got commented on accident if you copy pasted.

When copying your SDK to the root of your filesystem, did you copy it as your own user or as root? you can use:

gksu nautilus

to copy system files with complete root privileges.

What exactly are you trying to update, Ubuntu or ... ? There shouldn't be a difference to get this working on 8.10, the only thing that seemed to change was the 51-android.rules file. Maybe this can help -

renaming it to 50-android.rules with

gksu nautilus

and deleting any backups (use CTRL+H to view hidden files).

restarting udev using:

sudo /etc/init.d/udev restart

Remember this is for 9.04, not 8.10. I hope this helps.
[G1 Android Development] nicholasbithell:
Okay this is how I moved my "AndroidSDK" Folder to root....

nick@ubuntu:~$ su

Password:

root@ubuntu:/home/nick# mv /home/nick/Desktop/AndroidSDK /

root@ubuntu:/home/nick#"

And I went to the bashrc file and it is entered in there correctly.

This is still what I get even after restarting Udev...

" bash: ﻿: command not found

nick@ubuntu:~$ adb

bash: /AndroidSDK/tools/adb: cannot execute binary file

nick@ubuntu:~$ su

Password:

root@ubuntu:/home/nick# adb

bash: adb: command not found"

Edit: This is what my .bashrc file looks like, well the top part of it anyways....

#AndroidDev PATH

export PATH=${PATH}:/AndroidSDK/tools

# ~/.bashrc: executed by bash(1) for non-login shells.

# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)

# for examples
[G1 Android Development] wddglr:
Okay your .bashrc is setup right and it's recognizing adb and its directory.

I would say it's something to do with permissions. since you moved it under su, you are not the owner so i would say that you'd have to change the permissions of /AndroidSDK

you can do that with -

gksu nautilus

Navigate to /

Right click on /AndroidSDK and select Properties

Click on Permissions tab

Select your user account as the owner

hopefully now it will function correctly
[G1 Android Development] nicholasbithell:
I dont understand what this line does...

"gksu nautilus"

when i type it in it asks me for my administrative password and then after i put it in it hangs for a sec and then back to...

bash: ﻿: command not found

nick@ubuntu:~$ gksu nautilus

nick@ubuntu:~$
[G1 Android Development] wddglr:
nautilus is the file browser, while using gksu nautilus you can use the file browser under root privileges
[G1 Android Development] nicholasbithell:
I dont have Nautilus as a file browser I have Thunar I believe.
[G1 Android Development] wddglr:
Then gksu thunar
[G1 Android Development] nicholasbithell:
For permissions it says that I am the owner and the group (I=Nick) for Others it says Read and Write, Access says Read and write. So it seems it has all the right permissions. Any other Ideas?
[G1 Android Development] BlackElvis79:
Partitioning HD

First off, thank you for this thread, it's most excellent. I have a question that is slightly off topic, but not so much. I have Ubuntu 9.04 installed on my recovery partition. This partition is only 10 GB, while I have Vista on my main. I have almost 100 GB free on my main drive, and what I want to know is, if I resized my partitions to give more space to Ubuntu, how would it affect my comp? (if at all). And which OS should I be on while resizing, Ubuntu or Vista?
[G1 Android Development] wddglr:
Great, atleast you didnt jump in right away without any guidance. :)

First, make sure you defragment your disk in Windows, do it twice just in case.

After that, you can go straight to installing ubuntu, or partitioning with gparted.

How exactly is your harddrive set up?

[______VISTA + 100 GB______][__UBUNTU__][SWAP]?

if so you can make the following partition table -

[___VISTA + 60 GB___][_UBUNTU + 10 GB_][_/home(25GB)_][_/AndroidSDK(5GB)_][SWAP]

or you can ditch the /home partition and go with -

[___VISTA + 60 GB___][_UBUNTU + 35 GB_][_/AndroidSDK(5GB)_][SWAP]

or what suits you best. you get the idea
[G1 Android Development] wddglr:
I am not sure how i can help you my friend, I will try to look for something.
[G1 Android Development] nicholasbithell:
Okay I think I figured out the problem! I just upgraded from 8.10 to 9.04 so I could start fresh (Which also means I have nautilus as well) So when I move my "AndroidSDK" folder to "/" using "gksu nautilus" It works just fine but when I go to permissions it gives me a bunch of options that "Thunar" didnt have like giving the file "Permission to execute as a program" so I go in and give every program in there the same permissions (all on my user account) and then I exit out, But when I go back in to check the permissions right after i set them all the little check boxes giving me the option to "execute as a program" have gone blank again along with changing some other permissions from "Read and Write" to "---------". Any Ideas I am feeling pretty close to getting this done! (hopefully) :) Thanks for your help!

Edit: I just went in and checked the permissions on "adb" and not just on the "AndroidSDK" folder and found that it has all the correct permissions including the little check box that say "make program executable". But there is one other thing in the section where it says "open with" there are no programs selected, it also gives the option to use a custom command line?!? any ideas?
[G1 Android Development] wddglr:
re-download the SDK and follow the procedure from the OP

it should work now that your machine is fresh.

:)
[G1 Android Development] savethechicken:
This is the way that I have my .bashrc file setup. For those having problems with it not recognizing the adb as a command try this...

export PATH=$PATH:~/SDK/tools

I removed the {} around ${PATH} and it is working if I had them on it would say that it didn't recognize the command. Removed them and all works well.
[G1 Android Development] wddglr:
Updated OP.
[G1 Android Development] BlackElvis79:
Sweet!! Thanks a mil for ya help.
[G1 Android Development] wddglr:
It's always good to help out.

:)
[G1 Android Development] acids7n:
Jaunty 64

Can this but done on Ubuntu 64bit? (jaunty 9.04)

I'm currently looking into Eclipse to see if that can help

did some googling and got it to work with Eclipse....

Infact i followed this guide here

http://www.howtoforge.com/installing-google-android-sdk1.0-on-ubuntu8.04-desktop

works for jaunty 64bit

very similar to this guide.

thanks again for all the help
[G1 Android Development] ccyrowski:
It should be noted that if you ever plan on compiling kernels and/or cupcake ROM's you will NEED ubuntu8.04. You'll also need at least 10GB. :)
[G1 Android Development] ChrisBuchholz:
remount failed: Operation not permitted

I have followed this guide, and also the one at http://www.swedroid.se/forum/showthread.php?t=158 before I found this, but none works for me.

When I do "adb devices" it does list my phone, but I can't get neither "adb remount" or "adb push" to work at all. I've tried to format my sd-card, but that didn't work either. When doing "adb remount", it just replies remount failed: Operation not permitted, and with "adb push xxx xxx' I get failed to copy 'xxx' to 'xxx': Read-only file system

What have I've done wrong?
[G1 Android Development] alapapa:
did you turn on usb debugging in the settings on your phone?
[G1 Android Development] dancerobot:
Needed extra rules

I am running Ubuntu Jaunty 64-bit and I have an HTC Magic. I could get fastboot to work but I could not get adb to ever detect the device.

Finally, last night I found some additional rules that needed to be added to the android-rules files that did the trick! Also, in the time I was fiddling with it, I renamed my file 90-anroid-rules on someone's advice, I don't know if that is necessary but it is working for me so I am leaving it alone :)

So, the contents of my /etc/udev/rules.d/90-android-rules files is:

SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c02",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c01",SYMLINK+="android_fastboot"

I hope this helps some get adb to detect your device!
[G1 Android Development] temporizer:
I am using ubuntu jaunty jackalope. i realize this is a tutorial for 8.10, but what about 9.04 (which is what i have) How can i get it to recognize my device? i type

adb

and it gives me the help menu

when i type

adb devices
or
adb remount

it sayd

error: device not found

can someone help?
[G1 Android Development] Fernanernie:
Great forum all, and an awesome thread.

Here's a question for though, would this work under a Virtual OS setting such as VMWare or Virtual Box?
[G1 Android Development] dixxa:
try to use those command as root

I had this problem long time ago.

If it works as root,

do this in a terminal chown your_username:your_username -R /path/to/tools/folder.
[G1 Android Development] temporizer:
It works fine with root, so I did this

chown temporizer:temporizer -R /home/temporizer/android/tools

and upon fresh boot, I still can't use adb without root
[G1 Android Development] ravens0ng:
Thanks for the awesome tut! Worked like a charm for me! Could never get this working in Vista, but it fired right up in Ubuntu JJ.
[G1 Android Development] Breakthecycle2:
Ok , I need some quick help. I know this is for 9.04, but I am trying to get 9.10 installed. I already had it installed side by side with Vista, but couldn't get adb to work in Ubuntu. So I tried to follow this tutorial. The problem I am having is when I go to set up the partition, and clock forward, I get "no root file system detected". Can someone please point me in the right direction?
[G1 Android Development] Breakthecycle2:
Anyone?? lol.
[G1 Android Development] BombaMyte:
@BreakingTheCycle: I've already set up my SDK and whatnot, but I can reinstall Ubuntu 9.10, and try this method. TBH, I used bits and pieces of several SDK installation tutorials to get it up and running. Hopefully this method will work. I'll try it after the game, about 30 mins...

EDIT: Okay, I followed the directions listed. Once you get to setting up the partition, I get that same error. So instead of naming the partition /AndroidSDK, I just selected "/" from the drop-down menu. Installation continues, yada-yada-yada, open Terminal, adb shell, success.
[G1 Android Development] Breakthecycle2:
Hey man. OK, so I was able to delete the partition and install a fresh copy of 9.10. I followed the OP, installed rule 51 and did everything else. Now it still is saying adb is not a recognized command. My question is, does the sdk folder have to be in your filesystem folder or can it be be on the desk top? I would assume it's similar to windows and has to be on the root of your hard drive?
[G1 Android Development] BombaMyte:
I moved mine from /home/bombamyte/ to the filesystem. Did you also edit your .bashrc for ADB access? I did this in stride with the OP, then changed it when I moved the SDK to the filesystem.
[G1 Android Development] chrisharang:
Thank you for this! I was having trouble getting a VM with Karmic (9.10) to recognize it with the usual settings, but this fixed it.

- Chris