Related
People that only want to use Android, and have NO clue about Linux or programming PLEASE REFRAIN FROM POSTING HERE
First off credits goto all those working hard and having sleepless nights, people like: dcordes, netripper, druidu and all those I didnt mention!
I have just made this thread to get developers a kickstart, so that they dont have to read hundreds and hundreds of posts.
==========
IRC: #htc-linux @ Freenode
==========
READ: http://linuxtogo.org/~lgorris/kaiser-bootkit/README.txt
Getting the kernel (taken from http://forum.xda-developers.com/showthread.php?p=2269384#post2269384 ... credits to dwaradzyn): (UPDATED, new ARM toolchain and now working)
Code:
mkdir ~/android
cd ~/android
git clone git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git
cd kernel
git checkout -b htc-msm-2.6.25 origin/htc-msm-2.6.25
cd ..
wget http://www.codesourcery.com/gnu_toolchains/arm/portal/package3382/public/arm-none-eabi/arm-2008q3-39-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
tar xvjf arm-2008q3-39-arm-none-eabi-i686-pc-linux-gnu.tar.bz2\?lite\=arm
cd kernel
make htcraphael_defconfig ARCH=arm
export PATH=~/android/arm-2008q3/bin:$PATH
make zImage ARCH=arm CROSS_COMPILE=arm-none-eabi-
Now the file ~/android-kernel/kernel/arch/arm/boot/zImage is ready to be put on your phone and you can boot it with haret's newest version (1.5.2 works fine) ... downloadable from: http://www.handhelds.org/~koconnor/haret/
Open your favourite text editor to create the file "DEFAULT.txt" and put the following in it:
Code:
set MTYPE 1910
set KERNEL zImage
set INITRD android.bin
set RAMSIZE 0x5e
set RAMADDR 0x10000000
set cmdline "root=/dev/ram0 rp init=/init console=tty0 mem=94M"
bootlinux
Get the file android.bin from http://linuxtogo.org/~lgorris/kaiser-bootkit/ and put it in the same directory as haret.exe, default.txt and zImage.
Is the android.bin in http://h3po.de/public/diamond_android_0.8.zip the same? (Havent checked)
=====
Now the new points of attention are:
1. Touchscreen calibration:
I have seen people talking about a red dot in the upper left corner, I have seen it once so far and didnt notice any major miss calibration when using the dev tools > pointer locator ... the only this malfunctioning is the x inversion and that you need to double tab (or is this standard behaviour? It looks like it remembers the last pressed location). Also the onscreen keyboard is very flickery, minor issue should be easy to fix (during loading it looks like it is flickering on the readout of the touchscreen).
2. Hardware support:
Adding various support for hardware, to output sound and all other "required to call" fuctionality.
Also not forgetting to access internal memory, maybe the best workaround to loading a fully fledged Android is to make a minimal initrd to setup internal storage and from there load the rest. Should be much easier when it all gets incorporated into a ROM, instead of loading with haret ... which poses serious problems regarding initrd loading and who wants WM6x/7 on his phone anyway when Android becomes usable. Loading from haret does make working with it for now a little easier. Maybe a GRUB like approach and loading straight from a filesystem (ROM or internal storage)?
==========
Some other request:
Pointers to Android OS sources or atleast a working 1.0 (latest branch?) initrd.
==========
General tips:
Going back to desktop: insert and remove stylus.
Selecting and opening, use double tabbing and mirror x for now.
Using onscreen keyboard: havent figured it out yet sadly.
=========
Ill try to update the post, also PLEASE people refrain yourself from posting in this thread ... let's make a good go at keeping it clean. If you do not intend to be working on getting Linux / Android to work on the Diamond and family please post somewhere else. No harsh feelings, but threads getting cluttered with "Great work!" and "wehn iz android really workn on me phone?" do mess things up by quite a bit.
DO NOT ASK FOR REQUESTS, focus is on the basics first ... input, output and storage.
==========
Dont forget to check: http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
==========
Developers, please post updated links / patches and all that would help us make progression.
//placeholder for useful links
Original thread (very bloated with comments and hard to dig through, dont let it happen here): http://forum.xda-developers.com/showthread.php?t=402002
Complete working Android 0.8, "extract and run" ala Plug 'n Pray: http://h3po.de/public/diamond_android_0.8.zip
Wikipage: http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
Haret: http://www.handhelds.org/~koconnor/haret/
Howto for kernel building: http://forum.xda-developers.com/showthread.php?p=2269384#post2269384 (replace htc-msm with htc-msm-2.6.25)
// placeholder for points that need attention
1. Touchscreen input, calibration and sensitivity.
2. Latest sources to build our own initrd for Android OS.
3. Storage accessibility.
question???
why not put this in the thread that is already running on this ????
why on earth does it need a new thread?
only a question : if I try this Android on my Diamond , the WM6.1 will be delete ? or I can have it also?
P.S.
sorry for my bad english
yuco91 said:
only a question : if I try this Android on my Diamond , the WM6.1 will be delete ? or I can have it also?
P.S.
sorry for my bad english
Click to expand...
Click to collapse
beware.....you can brick your phone if you don't know what you are doing!
liamhere said:
beware.....you can brick your phone if you don't know what you are doing!
Click to expand...
Click to collapse
ok, but you not have aswered at my questions .....
this sounds quite interesting...
Android, is a serious alternative now to Windows o/s, yes?
What are the selling points compared to windows???
Why are there not clear and concise instructions on how to install android???
Does android offer the use of the line 2 facility like 6.1?
I notice the huge Hype with the launch of the G1 phone, can someone offer some screen shots of what it looks like on the diamond please???
cheers
What???? Look I love Mobile phones, Ive bought every high end phone scince the Nokia 8800, but this is way beyond my pay grade, can you ell me how to do this? Im a junkie for utilities and Roms, and etc, but this is really past my skill level. Ive searched and read the thread but I can't get past the first stage. Please help me out, I really want to learn.
liamhere said:
why not put this in the thread that is already running on this ????
why on earth does it need a new thread?
Click to expand...
Click to collapse
cause 581 pages is hard to follow... and OP has sumarized it well...
zmob123 said:
What???? Look I love Mobile phones, Ive bought every high end phone scince the Nokia 8800, but this is way beyond my pay grade, can you ell me how to do this? Im a junkie for utilities and Roms, and etc, but this is really past my skill level. Ive searched and read the thread but I can't get past the first stage. Please help me out, I really want to learn.
Click to expand...
Click to collapse
dont bother usable android version isnt ready for general use (yet)...
not ready?
so how ready currently is it???
and do we have the choice of looking at screen shots???
does it support multi lines?
Was wm6.1 ready? - questionable!
crystal_clear said:
Android, is a serious alternative now to Windows o/s, yes?
What are the selling points compared to windows???
Why are there not clear and concise instructions on how to install android???
Does android offer the use of the line 2 facility like 6.1?
I notice the huge Hype with the launch of the G1 phone, can someone offer some screen shots of what it looks like on the diamond please???
cheers
Click to expand...
Click to collapse
no real screen shots...as it not really running RIGHT on diamond yet...
don't put this on and think your have a new all singing and dancing phone
YOU WON'T....NOT YET ANY HOW
has anyone.....
ok, your point that its not running at moment taken on board...
Has anyone had the idea yet to startup a directory for interested parties to be contacted to take part in trials - once its in the stage of being ready???
I would like to be considered, as i absolutely fully abuse all the facilities i have available to my via orange uk.
And do actively find the wm6.1 platform fails me seriously at times due to usage.
Development is open, just follow the important topic.
All I see is that this topic confuses people.
Bad idea starting this.
Riel said:
Development is open, just follow the important topic.
All I see is that this topic confuses people.
Bad idea starting this.
Click to expand...
Click to collapse
we agree to agree....your my new friend now
Delete this topic.
My cats breath smells like cat food.....
I see that this topic is confusing people already, this is mainly due to the fact 90% of the repliers DID NOT READ MY POST!
As I have stated before:
The basics still need to be worked on; input, output and storage.
People that only want to use Android should refrain from posting in this thread! I made this thread so digging in the old thread can be kept to a minimum, what gets added there I will try to add here too.
I just wanted to encourage people that know what they are doing with a headstart, I myself have been working with Linux since 1998 and reading the "delete this thread" posts really does not support encourage me to help you guys.
As for an example, some random programmer with a Diamond googles for Android and finds hey this might work on my phone (like happened to me) ... the next he will go trough hours of reading useless and outdated posts, not really helping you further.
Then you decide to read from the end back forward, even more useless posts are read and finaly you get a minimum set of files that works ... what now? No sources, no nothing to be found after reading beginning and end of the posts, so you decide to read the WHOLE thread and still NO progression after a full day of endless reading.
So my simple request was to summarize EVERYTHING developers can use to get started and NOT spend one day now or two/three days in the future looking at outdated posts and reinventing the wheel.
I for example did reinvent the wheel and started from the start of the thread, where I spend downloading the git sources from Andriod and started compiling ... same problem, started on output first ... framebuffer ... then I conclude lets start from the end and notice people already gotten something running ... NOT really helpful if you ask me.
So any mod, please delete all the useless posts in this thread. I have no problem with continueing in the old thread, but it will not progress us any further if its not cleaned up.
So people that only want to use Android, and have NO clue about Linux or programming PLEASE REFRAIN FROM POSTING HERE
So here is my summary of posts to be deleted:
4: Original thread is too long, doesnt help new developers start off where they should start.
5: Dont post in this thread, it will not delete WM6x.
6: Answer to post 6, dont post here unless you know what your doing.
7: Please dont formulate such questions here!
8: It does not work correctly, seams you just want to use Android and have no clue what your working with. Please do not post such questions here.
9: Please no learing here, learing can be done on other platforms.
11: It barely works, raw input and working output, some other major and minor functionallity is there but does not work correctly yet. Please dont ask these questions.
13: Trial and testing will be done trough progress, we dont need people that just want to use Android in this thread.
14: Sorry that it seems to confuse people, it is mainly due to people not knowing what this is all about and asking questions that should not be asked in the first place. Let alone they EVEN read every word here!
15: Good luck reinventing the wheel.
16: A webdesigner asking to close this topic ... not really helpful and discouraging.
17: Please remove yourself from this forum!
Thanks in advance.
ouch
...how to make and break friends in one single post
sorry this thread is only for the "special people"
us plebs must not comment in the thread...we have been told
THE END!
PLEASE, FOR THE SAKE OF MY SANITY. READ THE FAQ FIRST FOR QUESTIONS!
F.A.Q.
This in NOT an emulator, nor is it a full ROM! Haret.exe closes down Windows, and boots Linux off of your Storage Card to launch Android. To boot back to WinMo all you need to do is reset your handset!
This thread is more specifically for the Rhodium, as this is the handset that I own, and can troubleshoot and test. So if you have specific questions about a different handset, please find your corresponding thread in post #2, however, this build will support the following devices: Diamond, Raphael, Kovsky, Topaz, Rhodium, & Blackstone by using the corresponding startup.txt found in any of the .rar files.
This package does work for both GSM and CDMA, however, the CDMA troubleshooting thread is at the following link: http://forum.ppcgeeks.com/showthread.php?t=115443
NOT WORKING IN THIS BUILD:
BT
Camera
Headphones
Speakerphone (no mic)
Battery Meter (about 75% fixed now)
--------------------------------------------------------------------------------------------------------------------------------
Change Log:
NEW January 23 NEW FRX04 Android 2.2.1 build added to downloads page!
11/22 FRX03 build added to downloads page! Go HERE for the full change log!!
11/01 FRX02 build added to downloads page! Check out the updates for a more detailed change log!
10/04 Kernel updates! In call mic fix and battery updates!! The new meter should be MUCH closer to actual battery now!! Either use update on the Start Application or head over to the project tracking web page!
9/28 Sovereignty's Startup Utility V1.1 goes live! Fixed BLAZN Gmail app, re-added 3d Gallery. Fixed Reference not having Google Talk.
9/26[/B][/COLOR] NEW KERNEL FIXES NOW WITH WORKING HARDWARE 3D!!!
9/16 System build, FRX01 Final. The product of testing through RC1 and RC2. Lots of fixes, too many to list. Come here for full updates.
8/30 Package with a few updates. This one fixes the garbage noise of the speaker being "on" even when no sounds are being played. Also updated the rootfs file for a few fixes. (Add new gralloc for WVGA devices).
8/26 THE BIG ONE YOU HAVE ALL BEEN WAITING FOR...... SOUND IS WORKING!!! (New Zimage/Modules kernel fixes for sound!)
8/18 Froyo system images added! New rootfs updates = MUCH MORE SPEED!! Lots of BLAZN theme fixes added, Full change log is HERE: http://sites.google.com/site/androidport/updates
CHANGELOG HISTORY CAN BE FOUND HERE!!
--------------------------------------------------------------------
Notes: Read this before you start!
THIS THREAD IS NOT FOR YOU TO COME HERE AND TELL US WHICH OF YOUR FEATURES IS THE MOST WANTED. WE ALL WANT THIS OS COMPLETELY WORKING. PLEASE, BE PATIENT LIKE THE REST OF US.
If you think you need to post a question in this thread: READ THROUGH POST#2, AND USE THE SEARCH TOOL FIRST!!!! Most questions have already been answered in this thread. I don't mind answering GOOD questions, but I really hate people asking the same questions over and over, ESPECIALLY when the answer is only a few pages before your post. DONT BE LAZY, THIS FORUM IS FOR DEVELOPMENT, NOT CUSTOMER SERVICE.Download Section: Project Android Rebuild
Appreciate my work?
ScreenShots
Other Devices:
This package will work on other MSM devices however, you may have some stability and functionality issues. If you are having issues with another device, other than the RHODIUM, check the dedicated forum. Most users on this specific thread only own a Rhodium, so we cannot test/troubleshoot other handsets!!
Dedicated thread For GSM Diamond/Raphael users using xdandroid
http://forum.xda-developers.com/showthread.php?t=601751
Dedicated thread For CDMA Diamond users using xdandroid
http://forum.xda-developers.com/showthread.php?p=5222958
Dedicated thread For Raphael800 users using xdandroid
http://forum.ppcgeeks.com/showthread.php?t=104276
Dedicated thread For Blackstone users using xdandroid
http://forum.xda-developers.com/showthread.php?t=603813
Dedicated thread For Topaz users using xdandroid
http://forum.xda-developers.com/showthread.php?t=509493
-----------------------------------------------------------------
Tips, Tricks, & Fixes
Read the newly updated FAQ Here:
http://sites.google.com/site/androidport/faq
-----------------------------------------------------------------
Project Tracking
Stay up to date with all of the freshest releases here:
http://sites.google.com/site/androidport/project-tracking
-----------------------------------------------------------------
Thanks!
First off, there is an insanely huge list of guys who are responsible for making this possible. Compared to what they do I am just a monkey punching a keyboard. THANKS DEVS
Thanks to phhusson, dzo, zenulator, Chamonix, Stinebd, Makkonen, MrPippy, cr2, Markinus, WisTilt2, Babijoee and anyone else forgotten!
Thanks to scepterr for the free speedy file hosting!!! Need hosting for an XDA project? Ask him!
Donations to XDAndroid team: http://xdandroid.com/w/donate.php
XDAndroid Twitter: http://twitter.com/xdandroid
XDAndroid Facebook: http://www.facebook.com/#!/pages/XDAndroid/394317262428
Thanks to those who have already helped, and to those who will. THANK YOU!
.
reserved for me, just in case
This is much better. AT least noobs like me can clearly follow this thread. Android on my Tilt 2 tonite. Thanx pioneers!!!!!!
Just a quick note that the 'rhod210' keymap (which is default in this build) should be pretty OK for almost all Rhodiums, unless you have an AZERTY layout or an odd European one with lots of accented letters mapped to Fn key combos. You can use Fn+Y to get the 'pipe' symbol | (may seem useless to many of you, but for those of us who poke around at consoles a lot it's invaluable :>). You can use Fn+W to get the UK pound currency symbol and Fn+E to get the Euro currency symbol - these keys are labelled on some Rhodiums so I figured I'd just implement it for all Rhodiums, as it may come in handy sometime.
if you have an odd keyboard layout but just want to use this build, the keys should behave like the layout pictured here:
http://mynokiablog.files.wordpress.com/2009/04/keyboard-2.jpg
so just press the keys as if they looked like that.
One day one day.... we shall have wifi I hope. Thank you for all your hardwork.
I'm trying to do something about wifi ATM with the kernel guys, but it's not simple. The problem is the Rhodium uses a completely different chip than most other phones, for wifi / Bluetooth (it uses a Broadcom BCM4325). No-one's got anything at all out of that chip yet.
Good show.. Thanks for making XDANDROID accessible to everyone.
BTW, Wifi not working at this time creates a good "shutdown/reboot" opportunity for now. The Shutdown option in Android does not seem to be working yet and so was interested in a way to shutdown/reset the phone without a "soft reset" poke after removing the back cover.
Found this by accident:
>>
Settings->Wireless & Network Settings->Wifi (Click to Enable Wifi) and boom in a few seconds, the phone is off like a light.. Hit the power button on top and we have a full reboot..
>>
Edit: The Wifi crash is fixed in the 02/03/10 build mentioned at the top of this thread. So need to open the back cover to reboot..
Man this is really nice. I can't wait to get a Nexus One but this will do for the TP2 for now. Almost there for everything to work. Can't wait for the release with sleep mode fixed and BT working.
Bootup problems
Not sure what/why, but my touch screen doesn't seem to be working as I can't get past the boot screen (touch the android) as the screen location doesn't seem to match up. Any ideas??
[EDIT] My bad, misseed the touch screen calibration...
AdamWill said:
I'm trying to do something about wifi ATM with the kernel guys, but it's not simple. The problem is the Rhodium uses a completely different chip than most other phones, for wifi / Bluetooth (it uses a Broadcom BCM4325). No-one's got anything at all out of that chip yet.
Click to expand...
Click to collapse
Isnt that the same chip as the nexus and the iphone?
sd73ta: yup, indeed. In fact we might need a NAND dump from the n1 to fix it. The kernel guys took the driver from the n1 source, but we can't make it work yet.
edit: not quite the same, in fact - well, same as some iPhones, but the n1 has the BCM4329. The 4325 and 4329 use the same driver, though.
AdamWill said:
sd73ta: yup, indeed. In fact we might need a NAND dump from the n1 to fix it. The kernel guys took the driver from the n1 source, but we can't make it work yet.
edit: not quite the same, in fact - well, same as some iPhones, but the n1 has the BCM4329. The 4325 and 4329 use the same driver, though.
Click to expand...
Click to collapse
have you checked out the dream/nexus one subforums here for a dump or a NAND? i know there are always new dumps and NANDS in the dream forum, if there isnt one, i suggest you get ahold of cyanogen here on XDA. he is the android genius on the dream/mytouch. he might be able to lend a helping hand actually.
When i try to download rar i get message:
Oops! (404)
We can't find the page you're looking for. Check out our FAQ or forums for help. Or maybe you should try heading home.
Any ideas ?
majster-pl said:
When i try to download rar i get message:
Oops! (404)
We can't find the page you're looking for. Check out our FAQ or forums for help. Or maybe you should try heading home.
Any ideas ?
Click to expand...
Click to collapse
FIXED! My Apologies!
Thanks it works now
Nice work!
for the Thread, and for the packages which u create
Hope that this thread will become the MAIN for Porting Android in TP2
Regards!
dont know if this is usefull...nexus1 rom dump
found it on http://db.androidspin.com/android_developer_display.asp?developerid=21
here is the rom http://www.androidspin.com/downloads.php?dir=enomther/ROM/&file=TheOfficial_Nexus1_v1.5.1_update.zip
hope this is somehow usefull
Does anyone know how development on power management is coming along? The most recent builds seem fine for everyday use as far as functionality goes, but battery drain is immense.
It seems like acceptable battery life is the only thing that's keeping this project from offering basic everyday functionality (WiFi, camera and GPS would be nice in the future)
woeds said:
It seems like acceptable battery life is the only thing that's keeping this project from offering basic everyday functionality (WiFi, camera and GPS would be nice in the future)
Click to expand...
Click to collapse
Powermanagement + SOUND... I only miss these two, don't care much for Wifi personally
Hi there!
There are members here who have successfully cooked for the Vogue with each one using the kitchen that he prefers, while there are many others who have researched for hours and still have trouble setting up a kitchen.
Anyone who tried to do this without prior knowledge surely remembers how much effort is needed to learn all the steps, since the cooking process is quite complicated and there are many new things to learn. Even if one managed to setup a kitchen he might still have no idea how to port a new build to the kitchen. I have also found it difficult to learn what exactly do you need to keep from the original ROM that was shipped with the device and which of those old files can we get rid of. And the list goes on and on...
Many would love to enjoy the thrill of building their own custom ROM with the programs that they find useful, and to be able to tweak it the way they prefer.
I'm calling here on all of you who have experience cooking for the Vogue to please share your knowledge here.
If you have a kitchen setup that you would like to share, I'm sure that many members would love to make use of it!
See post #18 for a description of ROM XIP SYS OEM and LANG. Thanks to egzthunder1.
UPDATE 02/18/10
From my own personal experience and as others have mentioned in the first few posts of this thread, the easiest kitchen for a new chef is the PPCKitchen.
STEP 1: You can register at ppckitchen.org and download the latest version of the kitchen. After installing the kitchen you will need to run the updater. It will take a few seconds while it connects to the server. After that you will have an option of downloading different files. In order to cook a working ROM you will need to go to ROM Kitchens\Vogue and download the following Vogue Carrier Kitchen files, Vogue Kitchen Core, Vogue Drivers. (I don't believe you need Generic OEM Kitchen files in the above directory). Of course you will also need at least one of the Windows Mobile builds from the same directory (ROM Kitchens\Vogue).
Although the builds that show up in the updater are pretty new, yet the latest builds will not show up. In the future after having successfully cooked a ROM with one of the more stable builds from the updater, you can go get the latest builds from the PPCK website at Windows Mobile Build Discussions\Test SYS Builds. *Advanced PPCk Users only*. For now I would stick to the builds that show up in the updater.
There are also OEM files that you can download with the updater. These files have different programs that you will be able to add to your ROM. You can download PPCKitchen OEM's, PPCKitchen 240x320 OEM's, Non Freeware OEM's (don't get exited it's only a trial!), and User submitted OEM's. You don't need any of these so you can download them and check if you want the programs that's inside, if not you can delete the whole file from your kitchen folder that's in your PPCK folder.
The kitchen is very easy to use and you can now build a basic ROM.
I hope to add more to this mini tutorial within the next few days.
I agree 100%, I think it would be great if some of the experienced chefs could drop some knowledge on the rest of us, if not only so we can keep pumping out new ROMs for our Vogues.
Head over to PPCKitchen.org they have a tutorial and everything you need to cook roms, its also the easiest to use in my opinion.
As you may have noticed over the past few days, I have been trying to keep the forum a little cleaner by asking people who open new threads with questions to simply ask them in a sticked Q&A thread. This request also falls under that same premise. Please do not open new threads asking questions. Threads should only be opened to contribute to the site (roms, kitchens, skins, guides, apps, etc). Thanks.
Barogi44 said:
Head over to PPCKitchen.org they have a tutorial and everything you need to cook roms, its also the easiest to use in my opinion.
Click to expand...
Click to collapse
I also have been using the PPCkitchen and agree that it's the easiest, but I have found that it's also somewhat limiting and think it would be a good idea if those using the Ervius VK or any other kitchen would be able to help others.
egzthunder1 said:
As you may have noticed over the past few days, I have been trying to keep the forum a little cleaner by asking people who open new threads with questions to simply ask them in a sticked Q&A thread. This request also falls under that same premise. Please do not open new threads asking questions. Threads should only be opened to contribute to the site (roms, kitchens, skins, guides, apps, etc). Thanks.
Click to expand...
Click to collapse
Sorry, didn't mean to make a mess while your trying to clear things up. It must be frustrating, sort of like cleaning up the floor and having somebody walk in tracking dirt on the freshly cleaned floor!
I just thought that this would be a Tutorial type of thread where members could come and add their little bits of knowledge until we would have a lot of info gathered in one spot. Personally I still think that it's not another simple Q&A thread, although your welcome to disagree and to remove this thread if you want. I'm still hoping that this thread will become a guide for all newcomers to cooking.
When I get home tonight, I will give you a heads up on how i use PPCKitchen. I cook for personal use only and don't publish roms. In short, all I do is use is a modified version of Vin's Generic_OEM. By modified, I take out things I don't need and insert things I want. When I used to flash manila roms, this was critical as his MANILA folder has every thing needed. Now that I don't use MANILA (I replaced it it SPB Mobile Shell 3.5.3 (I LUV IT!). When a new WM build comes out, I simply pop them files in the appropriate places and run it. I am currently in love with 23529.
If your interested in what I'm doing, you can start by downloading Vin's Generic_OEM from his 28014 Thread. Just search for Generic_OEM in the thread.
Lewy1 said:
Sorry, didn't mean to make a mess while your trying to clear things up. It must be frustrating, sort of like cleaning up the floor and having somebody walk in tracking dirt on the freshly cleaned floor!
I just thought that this would be a Tutorial type of thread where members could come and add their little bits of knowledge until we would have a lot of info gathered in one spot. Personally I still think that it's not another simple Q&A thread, although your welcome to disagree and to remove this thread if you want. I'm still hoping that this thread will become a guide for all newcomers to cooking.
Click to expand...
Click to collapse
I know what your intentions were and I do not disagree with you. But there are a few things that need to be considered for making a "cooking guide" for this particular section of the site...
*There are only 3 (4 at best) active chefs for this section: Nag, Barogi, vin (if he decides to fully return), and myself. I believe that NFS will not return (personal unfounded belief).
*Most of the above chefs use PPCK. I am not saying that they don't use others like VK, but the info on cooking will be pretty much the same that you can find in the PPCK website.
*There are a slew of tutorials floating around the site (not just the Vogue section, but throughout XDA), which have a lot (and I do mean a lot) of information on how to cook.
*Cooking with other kitchens is far more involved than simply dropping build packages into PPCK. You can even get down to the nitty gritty of hex editing your rom to get more stuff out of it (ie, there is a hex change in the BA roms that allow you to have more ram available).
*Lastly, since the Vogue uses newer style roms (nbh, as opposed to older formats like nbf), learning how to cook from scratch would be kinda a waste of time (believe me, I spent the last month learning how to port a newer rom to the Blue Angel and it isn't as simple as you may think).
One of the mods (I can't remember which one right now) has a series of posts with tools, tutorials, and a bunch of other things needed to cook. What we could do is simply make a one or two post sticky with the links to the different tutorials on xda as well as on other sites (ppcgeeks has a 1100+ pages thread that talks about cooking and porting). I will see if I can get my hands on those and get them in here if that is ok with you.
egzthunder1 said:
One of the mods (I can't remember which one right now) has a series of posts with tools, tutorials, and a bunch of other things needed to cook. What we could do is simply make a one or two post sticky with the links to the different tutorials on xda as well as on other sites (ppcgeeks has a 1100+ pages thread that talks about cooking and porting). I will see if I can get my hands on those and get them in here if that is ok with you.
Click to expand...
Click to collapse
Thanks, that's perfectly fine with me. I have seen most of the stuff that you mentioned and was actually thinking along the same lines as you. If I can I will add my own little bit of knowledge like links to the various kitchens and so on. By the way there is a new kitchen, Oskitchen with new UI by airxtreme (original kitchen by Ondraster). It looks like it will be easy to use and has just been modified for the Vogue, and I'm hoping to give it a try tonight.
Lewy1 said:
Thanks, that's perfectly fine with me. I have seen most of the stuff that you mentioned and was actually thinking along the same lines as you. If I can I will add my own little bit of knowledge like links to the various kitchens and so on. By the way there is a new kitchen, Oskitchen with new GUI by airxtreme (original kitchen by Ondraster). It looks like it will be easy to use and has just been modified for the Vogue, and I'm hoping to give it a try tonight.
Click to expand...
Click to collapse
Yes, I did see that one. I had tried oskitchen before and it isn't too bad (still preferred Ervius though). However, this new UI seems a little more user friendly...
Start out with PPCK. It works well, most users will not notice the limitations.
Biggest thing with making your own ROM's is getting all of the Reg edits that need to be included.
Good Luck! PS Start with build 23529 it seems to be really stable and fast!
First post updated with mini tutorial.
Lmiller1708 said:
Biggest thing with making your own ROM's is getting all of the Reg edits that need to be included.
Click to expand...
Click to collapse
Perhaps we can use this thread to gather up those types of regedits in one place. It would also be good to have guides for new cooks on how to add things like EzInput 2.1 (with working vibration) and Long Press End Key, BT Pan and Alarm functionality (while plugged in). Most of the newer roms have old or incomplete implementations of these features. vin was the last person to get many of these features all together in one place. With the age of the Vogue many of the cooks are trading up to newer devices and much of that knowledge is getting lost.
codf4ther said:
Perhaps we can use this thread to gather up those types of regedits in one place. It would also be good to have guides for new cooks on how to add things like EzInput 2.1 (with working vibration) and Long Press End Key, BT Pan and Alarm functionality (while plugged in). Most of the newer roms have old or incomplete implementations of these features. vin was the last person to get many of these features all together in one place. With the age of the Vogue many of the cooks are trading up to newer devices and much of that knowledge is getting lost.
Click to expand...
Click to collapse
Are you talking bout me ?
egzthunder1 said:
Are you talking bout me ?
Click to expand...
Click to collapse
No sir, not trying to single anyone out. I've tried pretty much every rom released here and on PPCGeeks I haven't tried your latest ones labeled MetroPCS. I'll flash you latest tonight and try it out for a few days.
just uploaded 28230. Try that one and let me know if you like it...
btw, I was joking... don't sweat it. I don't get so easily offended
tharris297 said:
When I get home tonight, I will give you a heads up on how i use PPCKitchen. I cook for personal use only and don't publish roms. In short, all I do is use is a modified version of Vin's Generic_OEM. By modified, I take out things I don't need and insert things I want. When I used to flash manila roms, this was critical as his MANILA folder has every thing needed. Now that I don't use MANILA (I replaced it it SPB Mobile Shell 3.5.3 (I LUV IT!). When a new WM build comes out, I simply pop them files in the appropriate places and run it. I am currently in love with 23529.
If your interested in what I'm doing, you can start by downloading Vin's Generic_OEM from his 28014 Thread. Just search for Generic_OEM in the thread.
Click to expand...
Click to collapse
I don't know if you sent this over via PM but I'd be interested in reading it too. I tried replacing the Generic_OEM.rar in the kitchen folder with the one from vin, but the kitchen won't startup after i do that.
codf4ther said:
I don't know if you sent this over via PM but I'd be interested in reading it too. I tried replacing the Generic_OEM.rar in the kitchen folder with the one from vin, but the kitchen won't startup after i do that.
Click to expand...
Click to collapse
The reason is that Vin's packages are not "kitchen ready". What he posted is in essence a dump of the Mega rom. The packages have to be worked on in a one by one basis to get them to work with PPCK. There is a nice guide on how to do that in the forum at PPCKitchen.org.
Hey Lewy1,
You are off to a good start. I have been giving your idea some thought and if you truly want this to be a "learning resource" for new chefs, you may want to start by describing a few basic concepts as well.
[highlight]ROM[/highlight]
In essence the Operating System with all the necessary files and programs that make up for what you have on your device. This contains things that are general to all devices as well as certain files and folders that are specific to each particular device (hence, the reason why you cannot flash a rom from a Blue Angel into a Vogue and vice-versa). Once a rom is obtained by dumping it, the dump will have a bunch of folders and files, which need to be turned into something "cookable". There exist several applications that can (and must be used) in order to accomplish this.
After all the things in the "dump" are sorted out and manipulated, the rom will essentially turn into 4 main parts: XIP, SYS, OEM, and Lang packages.
[highlight]XIP[/highlight]
The XIP is what holds the core of the OS. This is what holds the Native Kernel of the particular device as well. In order to port a rom to a device, one cannot simply replace the XIP with a new one. The XIP of the new OS must be "implanted" into the XIP of the base rom of the device. The reason for this is that there are many files that can simply be replaced in the XIP, but some must remain untouched as they hold key elements for the proper functioning of the device (Native Kernel).
[highlight]SYS[/highlight]
The SYS folder will have packages with software that the device may or may not need to run properly. This holds things such as the Shell (your UI), Office, core applications, etc. A lot of these packages can be removed from the SYS in order to make space for other apps that the chef maybe interested in having. However, great care must be taken when removing/adding packages since some packages are needed for the device to even be able to boot. Likewise, having too many packages will render the rom un-flashable since most devices have a specific size of rom that they cannot go over. In the case of latter devices, the available space for rom has gone up dramatically. For instance, the Vogue has roughly 90 MB of space for the rom. This is more than plenty to cook a lot of apps without too many issues. There are older devices such as the Blue Angel, where the size of the rom is limited to 32 MB, which forces most cooks to remove packages and compress things as much as possible to even have a bootable rom (keep in mind that most of the time, builds are coming with more and more space requirements).
On top of all this, there are the resolution requirements. Most packages will come with a second folder of a similar name with the resolution added. For example, Base will have another folder called Base_96DPI. The chef will have to be careful on what he/she puts to be cooked as having different resolution packages can make the device either not boot, or look weird (out of scale images) if it does boot
[highlight]OEM[/highlight]
The OEM normally holds fixes and programs that the cook could not fit in the SYS. It also hold drivers, sometimes even Language packs among other things.
[highlight]Lang[/highlight]
These are language and location specific modules. The chefs use the location modules to make roms for different languages and locations. It is usually a four character code that determines which country/language the rom is made for. For instance, 0409 is WWE.
There are many other basic concepts (such as Virtual Memory allocation) that could be discussed, but for now, these basic definitions should help the average person understand what they are dealing with when they see a new set of packages coming out on PPCK,
Hope this helps the cause
egzthunder1 said:
Hey Lewy1,
You are off to a good start. I have been giving your idea some thought and if you truly want this to be a "learning resource" for new chefs, you may want to start by describing a few basic concepts as well.
Click to expand...
Click to collapse
Thanks! Great Info I'll add it to the first post.
I am aware that this has been asked many many times, but i don't see a thread for this issue. I would like to know what attemps have been made to get some sort of support. I am by no means a developer, but i will try my best to get things running. Would it be something as simple as taking a a file out of a current android phone with the same specs and modding for use with a touch pro.
I'm simply curious if there is a thread or website around that discusses this and other issues in more detail.
I'm no kernel hacker, but I am...curious.
That's what i would like to know. facts about how far the development is. Maybe we could start a thread that has such progress stated. Where only the devs would be able to post, so we can have us a look.
The best you can do is read the IRC logs from #htc-linux. I think I recall reading in the logs that klinux had gotten OpenGL working on the Pro2, even with applications like Neocore (thought they're apparently slow).
You have to be a little bit more clear on what you mean by "open gl working".
I'm the developer who was working on the open gl for the klinux build. Bottom line is that open gl is working, but not with hardware acceleration. We used then nexus one drivers (adreno200) to enable things a live wallpapers. But it's so slow its not even worth it.
Now to get hardware 3d working 100%? a lot more work and testing. lol.
Well is hardware 3d working for any of the current android ports in any capacity?
Also, I'm so used to reading hardware specs in Desktop computer form. But with these phones, the only thing I know about them is the CPU manufacturer, model number, and speed.
Is there a separate chipset that handles audio graphics etc, or is it completely SoC.
I read about recent Android ports on the iPhone, and it seems they already have things like external audio working. Is this because the hardware on the iPhone similar to another HTC Android phone, more so than the hardware in the Rhodium?
awesome thread... actually informative and supportive.
i think what the OP is saying is how can us lowerscale highend users be more involved, perhaps in the debugging, data gathering... we could start a -sub group dedicated to each corresponding issues... bill gates didnt invent windows, him and his crew did. the more the merrier eh?
I have a long running reverse engineering thing going on. I have been looking for more info other than IRC. I would like to put my good skills to work w/out starting from scratch. Any info?
EDIT: I did find this, It has some helpful starting info: http://www.androidonhtc.com/wiki/Get_Involved
This is a great thread! I've been wanting to get in on some of this action. Hopefully this will reduce some of the clutter in Reefer's thread.
I meant to get hardware acceleration working. How far has this come along since i posted this??
Only Diamond / Raphael has hardware 3D enabled so far.
Very limited 3D for "low resolution" could be enabled in blackstone or other devices with workaround but that is somehow meaningless.
phh has tried different combinations of memory allocation but in vain.
so am I... given up at the moment.
mcdull said:
Only Diamond / Raphael has hardware 3D enabled so far.
Very limited 3D for "low resolution" could be enabled in blackstone or other devices with workaround but that is somehow meaningless.
phh has tried different combinations of memory allocation but in vain.
so am I... given up at the moment.
Click to expand...
Click to collapse
Phh recommended to trace down mem locations used by wince and that has been done but it still refuses to fire up once pmem.c is modified.
Recently i got the wince dmesg from my rhod in hopes that a cold boot would show as to how the 3d is being activated but that also showed no results. I get this crap when Manila is launched.
[ManilaToday](34156): ### Launching manila ###
23:20:09 [DISP] DrvEscape::HTC_SET_3D_LAUNCHING_FLAG.
I'm not sure what HTC_SET_3D_LAUNCHING_FLAG is.
The next step would be to make an android app and trace down what the hell the libgles_qcom driver is actually doing to see if it is working properly. If you load up ahi2dati.dll on winmo you can actually use the functions to show crap on the screen so i'm hoping the same can be done on android.
Not sure what else can be done at this stage.
[ACL] said:
Phh recommended to trace down mem locations used by wince and that has been done but it still refuses to fire up once pmem.c is modified.
Recently i got the wince dmesg from my rhod in hopes that a cold boot would show as to how the 3d is being activated but that also showed no results. I get this crap when Manila is launched.
[ManilaToday](34156): ### Launching manila ###
23:20:09 [DISP] DrvEscape::HTC_SET_3D_LAUNCHING_FLAG.
I'm not sure what HTC_SET_3D_LAUNCHING_FLAG is.
The next step would be to make an android app and trace down what the hell the libgles_qcom driver is actually doing to see if it is working properly. If you load up ahi2dati.dll on winmo you can actually use the functions to show crap on the screen so i'm hoping the same can be done on android.
Not sure what else can be done at this stage.
Click to expand...
Click to collapse
Ok, i would love to help out as i have never rly done anything like this b4. What exactly are you doing. How do you get HTC_SET_3D_LAUNCHING_FLAG?
How would i open a .dll, i dont think these can just be opened up to see what they are doing. I am on the dark side of the moon here. I know whats going on, but have no clue what to do to help.
garage_man said:
Ok, i would love to help out as i have never rly done anything like this b4. What exactly are you doing. How do you get HTC_SET_3D_LAUNCHING_FLAG?
How would i open a .dll, i dont think these can just be opened up to see what they are doing. I am on the dark side of the moon here. I know whats going on, but have no clue what to do to help.
Click to expand...
Click to collapse
I actually found HTC_SET_3D_LAUNCHING_FLAG on the wince dmesg. You can do this by doing a pwf dump.txt 0x16a00000 0xFFFF0 in haret. I did it after a cold boot to see if anything is done to the gpu once wince boots.
Loading the dll is easy. just make a simple win32 app and do a loadlibrary. This part works but it's not helping on android. I'm interested to see what mcdull thinks since i think he has ventured a lot into this as well. Right now if we can make a simple app in android to load the libgles_qcom.so directly and trace every step, i think that would be helpful to see where we are failing. I'm close to giving up..lol i already took 2 sick days from work to get to where i am now so i could use some help.
Here is what i got out of the chip in wince.
name: ATI HandHeld Interface
versions: 2.07.05110.34681
Revision: 0
ChipID: 1362104322
revisionid: 0
TotalMemory: 15990784
BusInterfacemode: 2
InternalmemSize: 262144
ExternalMemSize: 0
Surface info: 800x480
surface total bytes 768000
dwFrameBufferPhysical=0x14c00780 m_dwFrameBufferVirtual=0x57e00000 dwFrameBufSize=0xbb800
Most people here could probably not help with the hardcore kernel dev stuff, but I guess if you need memory locations or so (be it for opengl/sound etc) I think there a a LOT of people that are willing to run some apps that dump a txt file with debugging info & mem locations to their SD-card and send you that
I would love to help with developing, even if it means that I have to boot into winmo and android all night long and gather certain information, memory-adresses, try different versions of programs with all kinds of parameters etc.
Star-Lite said:
Most people here could probably not help with the hardcore kernel dev stuff, but I guess if you need memory locations or so (be it for opengl/sound etc) I think there a a LOT of people that are willing to run some apps that dump a txt file with debugging info & mem locations to their SD-card and send you that
I would love to help with developing, even if it means that I have to boot into winmo and android all night long and gather certain information, memory-adresses, try different versions of programs with all kinds of parameters etc.
Click to expand...
Click to collapse
We need more devs in general. I ran a trace on a basic app that runs 3d. So there is still a lot of crap to examine.
I'm willing to kill my touch pro 2 and remove the CPU to trace the JTAG locations but I only have the datasheet from the MSM7200/7500, not sure if it will be the same locations. I bet if I hooked up my Segger I could see exactly what is failing on the OpenGL and sound side since alot of hardware debugging is done this way...just sucks I dont know for sure if the pinouts are the same. I'm done it on quite a few different phones and boards over the years so its not a big deal. Omap3430 was simple to trace and the OMAP3530 had the exact pinouts.
BinaryDroid said:
I'm willing to kill my touch pro 2 and remove the CPU to trace the JTAG locations but I only have the datasheet from the MSM7200/7500, not sure if it will be the same locations. I bet if I hooked up my Segger I could see exactly what is failing on the OpenGL and sound side since alot of hardware debugging is done this way...just sucks I dont know for sure if the pinouts are the same. I'm done it on quite a few different phones and boards over the years so its not a big deal. Omap3430 was simple to trace and the OMAP3530 had the exact pinouts.
Click to expand...
Click to collapse
Sounds crazy.. i love it.
I was messing around today and made a small app to load the libgles_qcom.so directly to see if i can replicate my winmo success. Most of the ahi functions are included in the android driver as well except for AhiDispSurfGet which made it impossible for me to draw anything on screen.
The chip did pump out the same info as i posted before and it matches so thats a step in the right direction. Means we can recognize the chip with no problems and all 15.25 memory is reporting as well. If i had more documentation on those functions exported im sure i can get the chip to try to display something directly.
Interesting bit of info I read and perhaps someone can clarify this here. The Sprint Touch Pro 2 uses the Qualcomm MSM7600 processor. The AT&T Tilt2 (GSM phone) uses the MSM7201A processor. The "A" refers to the smaller 65nm die size (I believe).
From what I've read, some changes occurred on the MSM7200 -> MSM7201 due to patent infringements. The next question is, is the MSM7201A and MSM7600 essentially the same chip, just different hardware for CDMA/GSM?
I guess the "libgles_qcom.so" library is used in many other HTC Android phones, but for some reason it's failing on the touchpro2/tilt2, and we're not sure why (although logically it sounds like the library should work as it's used by other android phones with the same chipset)? I'm no kernel dev (I write .NET/c# apps which are much easier than kernel stuff), but am somewhat familiar w/ linux and perhaps can assist in development..
NewbTrader said:
Interesting bit of info I read and perhaps someone can clarify this here. The Sprint Touch Pro 2 uses the Qualcomm MSM7600 processor. The AT&T Tilt2 (GSM phone) uses the MSM7201A processor. The "A" refers to the smaller 65nm die size (I believe).
From what I've read, some changes occurred on the MSM7200 -> MSM7201 due to patent infringements. The next question is, is the MSM7201A and MSM7600 essentially the same chip, just different hardware for CDMA/GSM?
I guess the "libgles_qcom.so" library is used in many other HTC Android phones, but for some reason it's failing on the touchpro2/tilt2, and we're not sure why (although logically it sounds like the library should work as it's used by other android phones with the same chipset)? I'm no kernel dev (I write .NET/c# apps which are much easier than kernel stuff), but am somewhat familiar w/ linux and perhaps can assist in development..
Click to expand...
Click to collapse
learn haret/haretconsole and take a look a the kernel. good place to start. Feel free to come into the irc board if you have any questions
Hello experts on this forum
I`m a total newbie into this technology. I got myself a nice HTC desire HD. After a while, I got aggravated, feeling monitored by Mr. Orwell, whith this Android system. To my great surprise, I believe that I managed to route the phone, and install a Linux firewall. However, I still feel a little paranoid.
I know that people like me, stumbling around on a forum like this, might be a pain in the a. because we don`t "RFTM": However I tried, but there`s so many words that I don`t understand. I`m not a computer expert, and I`m not familiar with DOS programming. However, If I get my hands on a clear list, I know I can do it.
My question is this: I Use a modern iMac, with a card reader. I`ve two separate micro sd cards. Do anyone of you know about a nice, and simple explanation that idiots like me would understand, in order to completely wipe out this Google OS, and install a "clean" Ubuntu? I`m willing to make a real effort to learn, and I have patience. I love my HDHD because of the big nice screen, but I like to keep my personal life only for myself. I can`t stand that Mr. Orwell snap up all my datapackets.
Any help would be greatly appreciated, from you experts. I fear that this might be hard with a Mac, but I do have access to full DOS- utility on my computer. (iMac with i7 processor.
Also, am I pretty safe, with Ubunto on my machine?
Thank you so much in advance.
You do realise that running ubuntu on a device that only has a touchscreen is kinda fail...
Also, i doubt Mr. Orwell - whoever he is ( The only guy i can find on google is some author) would even be able to monitor anything. Android is completely Open source, so it would be kinda suspicious to insert code that sends "Packets" somewhere.
Even if someone is somehow monitoring you through the Android OS, i doubt that they would bother monitoring a single person, out of the tens or hundreds of millions of other android users.
Regardless, following this guide, and doing a full wipe (Download superwipe from android revolution, flash it in CWM) should completely remove android. (And install ubuntu)
314 said:
You do realise that running ubuntu on a device that only has a touchscreen is kinda fail...
Also, i doubt Mr. Orwell - whoever he is ( The only guy i can find on google is some author) would even be able to monitor anything. Android is completely Open source, so it would be kinda suspicious to insert code that sends "Packets" somewhere.
Even if someone is somehow monitoring you through the Android OS, i doubt that they would bother monitoring a single person, out of the tens or hundreds of millions of other android users.
Regardless, following this guide, and doing a full wipe (Download superwipe from android revolution, flash it in CWM) should completely remove android. (And install ubuntu)
Click to expand...
Click to collapse
Hi, and thank you very much for answering my question. Mr. Orwell wrote about 1984, if I`m not wrong. Today, my gut feeling tells me, that all the apps onboard my HTC sends away datapackets that I would like to stop. After installing this Linux firewall, I was amazed to see how many apps that sent away packets with headers, containing mye personalia. Even my camera stopped working properly, when activating the linux firewall.
Nix ok for me. To bad, because I found the Android system very nice and intuitive to use. My great challenge, is that I`m not a nerd. I whish a was, in a technical perspective. Many thanks for your link to the guide. As long as I can type text messages, check the web/mail, and maybe the weather forecast, I`m happy.
What I really fear, is that I will manage to mess up this machine of mine. Well, it`s just a thing, and I `ll survive, if I brake it. My economy isn`t the greatest, but heck, it`s worth a try.
Best regards!
You could always try flashing a clean install of CM7. It doesnt have any HTC Apps, just google.
Also, the packets are either log data, or sync data for HTCSense.com contact/etc backup. You can disable it by flashing ROM Cleaner and only removing the HTC Hub related and HTC "Spyware". This is only required if you want to stay on sense.
Google backup can be disabled by removing your google account, or going Settings>Privacy and untick "Back up my settings" (I think its disabled by default on CM/Miui roms)