Related
I know this will sound stupid, but is there a way to install WM (.cabs) on an android phone? (or port a program somehow)
Basically, nope!
Probably, same phone, same hardware, but the difference is, different operating system.
The only way to port stuff over, as yet, is to get hold of the source code and re-engineer it into the other OS. Not for the faint hearted, although it can be done.
The question to ask is, 'Is your App worth that amount of effort?'
'Where is the source code?', for starters.
If the App was written in .NET then a MONO CF for Android could be a solution. Anyone written it yet?
Hi to all fellow Athena owners.
It's been a while since i did any custom work for our phones, as I lost hope on the WM6x and the lack of support for our Athena400 models.
But now that Google Linux Android 2.1 is picking up steam in all other platforms, and seeing all the new HTC devices out and coming out with Android 2.1 there it seems to be light at the end of the tunnel, specially now with the addition of Gen.Y DualBOOT for WM6x phones.
after reading a few post in the forum i found new movements all round this front, so I felt inspired to try this project out and see how it turns out.
Here are our "ingredients"
http://forum.xda-developers.com/showthread.php?p=5420781#post5420781
Android 2.1 (Eclair) On HTC [09 Jun 2010] (V2.4) Improved GPS and Speed
http://forum.xda-developers.com/showthread.php?t=623792&highlight=x7510
[APP][25MAR10]Gen.Y DualBOOT v1.0.6.0[W|Q|VGA][CAB|EXT]
http://forum.xda-developers.com/showthread.php?t=402654
Ultra Vanilla for SPL 1.2 and SPL 3.5 (we'll need to first re-cook it to work for the x7510)
1. So the idea is simple, to start we'll try to make the Gen.Y DualBOOT on our phone. If that works we'll...
2. Install Android 2.1 first on SD card, if it runs properly...
3. we'll move it to the internal Flash Drive of the X7510, this will let you run both WM6, 6.5 or 7.0... and Android 2.1x whenever you want.
4. Then start cooking a good build of Android 2.1 with all the must have basic applications related to our phone, once we can confirm it can receive and make calls, get the GPS, 3G, WiFi, and smooth video/audio play back (hopefully with support for our ATI chip)...
5. Then we can cook a vanilla WM6x ROM to include Gen.Y DualBOOT and default it to Android 2.1
Android 2.1 is great, but not that great, there are still lots of applications missing in the Android platform, by that I mean software that are only available on WM6x and not on Android, StyleTap has not yet created a WM6x emulator for Android yet.
So the only way to use any application that you need in WM6x is to boot back to WM6x and use it, then boot back to Android.
Currently I've a lot of old Palm OS software that i can continue to run comfortably in WM6x using StyleTap, so until then it's all about hunting a replacement software for Android or waiting for StyleTap to release their WM6x emulator.
I noticed a lot of interest around Android an our WM HTC phones.
If anyone has spare time, please feel free to pitch in.
I'll keep you guys updated with my progress
Nice.
I am on for som testing when you are ready for that.
This manual might help with the hunt for drivers.
Gen.Y Dual boot, works great.
I got as far as loading the Kernel.... when running Android 2.1 but after that, it just hangs.
I tried installing it as all the available supported models without over clock, and it wont get pass that way.
I think we'll need to spend some time hacking and repacking Android 2.1 to support Athena
The the only thing Auto-Setup.exe seems to be doing is copying startup.txt from the models directory to the root of your memorycard.
containing:
set ramsize 0x6000000
set ramaddr 0x10000000
set mtype 2039
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3"
boot
Click to expand...
Click to collapse
This file is used by haret.exe in the booting process.
Time to edit that to something usefull.
I have played a little with the 'set mtype xxxx', but it did not get me any further. It needs to point out to some usefulness in the kernel that is made for the Athena or is common to it.
On my search to a way to decompile zImage, I came upon a site that has various linux kernels for HTC smartphones.
Athena is in the list but has nothing yet.
http://htc-linux.org/wiki/index.php?title=Main_Page
I have tried to search for Mtype, and found that i could be mtype = 182 !?!
set MTYPE 182
set FBDURINGBOOT 0
set KERNEL "zImage"
set RAMADDR 0x30008000
set CMDLINE "root=/dev/mmcblk0p2 mem=64M rootdelay=5 panic=30"
set kernelcrc 1
http://blog.gmane.org/gmane.comp.handhelds.haret/month=20090201
http://ibot.rikers.org/#htc-linux/20081002.html.gz
and on this page they are using mtype = 1289
They are all probably using different kernels with different mtype adressings.
We probably need a kernel for intel PXA based devices with a Athena x7510 mtype in it.
There are some Athena related recources over here.
And some basic info about booting linux on a deveice over here.
It's been more than 10 years ago that I compiled a linux kernel and that was just for a 486 PC.
Hey, i'm making good progress on the Universal that has similar hardware you can check the status. So far i've gotten every version of android to boot on it so far.
http://forum.xda-developers.com/showthread.php?t=658664
If anybody already knows how to build a kernel i can provide some help/tips and files.
the Linux page is not all that bad, i see they have collected several relevant information already but they are still missing the CPU type, GPS, keyboard, and many other items.
http://htc-linux.org/wiki/index.php?title=Athena
also thanks notime2d8, your input is very helpful, we'll give that a shot.
can y describe, how y compile kernel for univerzal? We can use the recept for x7510
Android on X7510
AllGamer,
I too am waiting for this major improvement to my X7510 device. Looking forward to testing for you anytime. Just let me know when you're ready! Keep up the good work!
Cheers,
Van
AllGamer said:
the Linux page is not all that bad, i see they have collected several relevant information already but they are still missing the CPU type, GPS, keyboard, and many other items.
http://htc-linux.org/wiki/index.php?title=Athena
also thanks notime2d8, your input is very helpful, we'll give that a shot.
Click to expand...
Click to collapse
The keyboard is there actually. http://htc-linux.org/wiki/index.php?title=Keyboard
And a technical info document of the processor:
www.phytec.com/pdf/datasheets/PXA270_DS.pdf
And you probably want this one too:
Porting Linux 2.6.9 to the PXA270 based development platform
Hello, you'd better go on a dell streak.
Maybe i will buy one but i don't know android and i wait for windows phone 7.
Yes, I am probably going to buy the Dell Streak or the Motorola Driod X.
But even then, I am curious if the X7510 can be made into something useful.
this is going to be a slow process to re-vitalize our Athena phones with Android OS.
in the meantime i'm getting myself a Samsung Galaxy S i9000, with more insight and hands on into a working phone, this'll make it easier to figure how to make it work with Athena, obviously the main challenge are the drivers for Athena, i can then use a dump of the phone and hopefully be able to find and replace all the drivers to make it work with the Athena.
Having 2 phones will allow me to test stuff on my Athena without having to worry about bricking the phone and getting myself stranted with no smart-phone to use for my daiy business.
Quite a few of the drivers are already available here link
This athena device file seems to include gpio keys, keyboard, bluetooth and gps power, backlight and video, and touchscreen for the 2.6.32-rc5 kernel. If anyone knows how to build a linux kernel, they can simply download any android kernel 2.6.32+, and add this plus related files and build a android kernel for the athena and only have the remaining drivers to work on or improve.
i was scavenging the forum for files that we could use, and this proves to be rather interesting although abeit modified.
http://rapidshare.com/files/116019051/Android-Athena.zip.html
i'll see if i can make it dual boot
came from this other topic
http://forum.xda-developers.com/showthread.php?t=387654&page=4
i'm still inspired by this very old video of the first android running on the Athena
http://www.youtube.com/watch?v=HtlcCQSRmiA
AvengerPenguin was working on getting android working on the x7501, which is pretty much the same as the x7510. Not sure what progress he made, or if he's still working on it, but you should look into teaming up with him. I know he has put a lot of hours into research and working on it. There are a couple android threads in the x7500 sections you should look at that he has posted in. I would love to see android on our athenas.
I have also been looking at the Streak, but I don't think anything comes close to the hardware suite we have on the 7510 -- processor speed aside. i am one of those rare birds who LOVES the magnet-attached keyboard, but then I use my 7510 as a palmtop PDA, not a phone. I would beg, borrow, steal or bribe for a working version of Android on this device!
Avi on 7510
Sorry for posting a whole new thread for this. I poked around with the search, however I figure the developers that are doing stuff for the Infuse have a lot on their plates to be able to write out a tutorial for this individual phone forum.
But, I have absolutely 0 experience in making a rom for anything. I have flashed Infused on my Infuse. This is my first Android device and I really love the customizability over the iOS software (previous phone). I know Gingerbread is just around the corner but I would love to take my first few steps towards developing with a rom thats been out already. This way by the time I get a better grip of things I can maybe transfer these skills to the new version.
If anyone can be so kind, Ide appreciate it if the helpful devs could maybe point me to some links with the necessary files and programs/files that are needed to build a custom rom. As well as maybe some tutorial threads or videos.
Anybody feel free to shoot me some useful links if possible. Thanks so much in advance! Cant wait to contribute.
Mikeymike had something you're looking for in the Captivate forum. Can't find the thread on my phone but it was basically a how to thread. Good stuff if ur interested
This should be in Q&A. But yeah, MikeyMike has a tutorial somewhere.
In my opinion - start off small. Get familiar with making customizations to a ROM (theming, app replacement, etc) and then grow from there. Don't bite off more than you can chew.
tazbo28 said:
Sorry for posting a whole new thread for this. I poked around with the search, however I figure the developers that are doing stuff for the Infuse have a lot on their plates to be able to write out a tutorial for this individual phone forum.
But, I have absolutely 0 experience in making a rom for anything. I have flashed Infused on my Infuse. This is my first Android device and I really love the customizability over the iOS software (previous phone). I know Gingerbread is just around the corner but I would love to take my first few steps towards developing with a rom thats been out already. This way by the time I get a better grip of things I can maybe transfer these skills to the new version.
If anyone can be so kind, Ide appreciate it if the helpful devs could maybe point me to some links with the necessary files and programs/files that are needed to build a custom rom. As well as maybe some tutorial threads or videos.
Anybody feel free to shoot me some useful links if possible. Thanks so much in advance! Cant wait to contribute.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=928955
remember to post in the right section next time bud.
Thanks so much guys. Sorry I was totally debating on whether to post this there but I thought that maybe the devs dont frequent that section.
Please do move this thread if possible.
Sent from my SAMSUNG-SGH-I997 using XDA App
Ok so I have one last question.
Is it better/easier to build the rom using an ubuntu virtual machine, dual boot ubuntu, or a Mac OSX Lion virtual machine in Windows 7?
I have the option to run any one of these types of systems. Unfortunately I do not have a Mac available, so Im wondering if it is even possible to build the source using a Mac VM seeing as how there are certain types of partitions necessary.
Thanks in advance.
tazbo28 said:
Ok so I have one last question.
Is it better/easier to build the rom using an ubuntu virtual machine, dual boot ubuntu, or a Mac OSX Lion virtual machine in Windows 7?
I have the option to run any one of these types of systems. Unfortunately I do not have a Mac available, so Im wondering if it is even possible to build the source using a Mac VM seeing as how there are certain types of partitions necessary.
Thanks in advance.
Click to expand...
Click to collapse
I'd dual boot windows and Linux
Samsung infuse running gingerbread!
Dual-booting Linux is your best bet. VMs mean that if you eventually get as far as doing kernel or AOSP/Cyanogenmod compiles, you'll have less RAM available, and also sometimes accessing USB devices (such as to use ADB or Heimdall) is a bit of a pain with VMs.
Awesome thanks a bunch guys i just got my ubuntu dual boot set up but i don't seem to have a working Linus driver for my trendnet wifi adapter.
But i have downloaded the infuse 4g source and im about to start setting up the build components from the android website.
Sent from my SAMSUNG-SGH-I997 using XDA App
tazbo28 said:
Awesome thanks a bunch guys i just got my ubuntu dual boot set up but i don't seem to have a working Linus driver for my trendnet wifi adapter.
But i have downloaded the infuse 4g source and im about to start setting up the build components from the android website.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Well, there are two routes to building ROMs right now:
1) Start from a Samsung ROM - there is source to the kernel and a few small parts of the userland stack available, but most of it is lacking source. Most custom ROMs available here are created by taking the stock Samsung ROM and tweaking them - removing apps, adding others, or attempting to bring apps from other devices to ours.
2) Cyanogenmod 7 - this is a source build, HOWEVER - it is not complete, open-source reimplementations of some Samsung stuff is not complete, so some features (like Bluetooth) are broken
A lot of ROM devs (those that work on Samsung-derived ROMs) don't even have a copy of Samsung's source code release as it's not useful to them. (Exception are those of us who do kernel work.)
It's not something you can just jump into. To do it properly, you need patience and a willingness to spend a lot of time researching a lot of different things.
1) Some things are easier to do in Linux and other things are best done in Windows due to some tools only being available for Windows. It's best to have both.
2) Learn how to dump the system partition (using the dd command) and mount/extract the resulting factoryfs.rfs on your computer.
3) Learn the /system folder structure. Explorer the files in each folder and try to figure out what those files are.
4) Find and learn how to use a script or program that can deodex the apps and framework from the extracted system image.
5) Learn the structure of flashable zips and what all of the commands in updater-scripts do. Easiest way to do this is to download a bunch of roms and look at their folder structure and updater-scripts. Google commands in them that you do not understand.
6) Learn which apps can be removed and replaced without consequence. If you can't figure out exactly what a particular apk does, best to leave it alone.
7) Experiment with changing build prop entries to see what some of them do.
8) Learn how to manually decompile and compile the dex portion of apk and jar files. Use smali and baksmali for this. This lets you modify app and framework code, but the decompiled smali can be a bit confusing. Try to learn how to read it. Try this AOSP lockscreen mod tutorial.
9) Learn how to use a program that can decompile and compile entire apps, including resources. Apktool is a good program and APK Manager is a good front end for it. Look through all of the folders in the resources (res) directory of a decompiled app. Learn which images and types of files are in each folder. There are a ton of xml files that do various things in the resource folders. Open a bunch of them up and learn some basic xml structure so you can see what all that xml is doing. Most visual app mods are done via xml. Here's a slightly more advanced mod tutorial than the AOSP lockscreen was: http://forum.xda-developers.com/showthread.php?t=811532
10) Learn proper apk compression techniques. Though it works, just dropping images into apks via 7zip and calling it a day isn't really the right way to theme. The default Android Asset Packaging Tool (used by the Android SDK to package apps) does not compress certain file types, including images. This is because images, especially pngs, typically do not compress a great deal anyways and the added cpu time it takes to decompress those images at app launch makes the total app loading time longer than if the images were uncompressed, even if they are slightly larger. Also, compressing some file types, like oggs and system objects, too much can even cause the app to not be able to load them. See here for a handy script to repack apks with proper compression: http://forum.xda-developers.com/showthread.php?t=1123463
I could go on forever, but that should point you in the right direction. At least you know some of the basics you need to learn now even if I didn't tell you exactly how to do each thing. Remember, Google will be your best friend. Use it. A lot.
Man I really appreciate this so much gtg. Its exactly the kind of encouragement i was hoping for. I just get a general sense of excitement when thinking of all the different possibilities in both Rom and app development. And seeing as how im and artist first, its awesome to know that ill down be able to be a double threat in both designing the look of, and building the Rom myself.
I can't thank you enough for pointing me in the right direction. Maybe one day someone will put together a kitchen for the Infuse. Until then ill be happy to dive into all the nitty gritty.
Sent from my SAMSUNG-SGH-I997 using XDA App
Hey, XDA. This is a copy and paste of a post to '/r/wp7dev' on Reddit I made a few minutes ago, and I'm not yet able to post links sadly.
I took out my Toshiba Gigabeat S the other day, which I've pretty much abandoned when I got my Focus. I kind of missed the amazingness of Rockbox.
The short time that I had a loaner iPhone 3G, I had installed iDroid on it and the Rockbox for Android port too, and it worked well. (I was the first person to get Rockbox working on an iPhone, [kind of!])
So now, I'm thinking about how cool it'd be to have Rockbox on my shiny Windows Phone 7.5 Samsung Focus...
I'm not a programmer by any stretch of the term, aside from dabbling here and there, but I do have the whole VS2010 for WP7 and an official student dev unlocked phone and all that, and got to tinkering with the source from Rockbox's Android port (I had this linked, search for Rockbox Android port). (I figure it'd be the most sensible to try with their Android port than any of their device specific variants.)
Obviously, I have no idea what I'm doing. I was able to find a porting guide for Android to WP7 APIs (I had this linked, search for Windows Phone Android mapping) and it looks like a lot of the objects translate well, plus Java and C# are fairly similar to each other, and are translatable (also linked, search for Java C# comparison).
I'm aware of some of the limitations with file system access and native applications, etc. with WP7, so I know the whole porting process won't be a 1-2-3-done kind of deal. But it definitely looks doable.
It seems that something like this might need an Interop-unlocked device for it to fully run, but I figure anyone who'd even want Rockbox would already have that done.
Rockbox would be great for WP7 because:
- it supports gapless playback
- it supports a gigantic variety of file formats
- crossfading is lovely
- EQ controls are superb, as are compression controls and balance and whatnot
- it has an excellent set of plugins like oscilloscope, vu meter, etc.
- plus, it'll look really cool Metro-fied.
If anyone with interest is able to help out with this, let me know. Then who knows, support for streaming gapless from a media server could even be done down the line.
tl;dr: a Mango/Metro-fied WP7 Rockbox using the source code from the Android port could be a super amazing thing for the audio playback options for the platform. Any assistance in doing this would be spectacular!
Rockbox for Android is not something I'm familiar with; the last time I looked at RockBox it was a full ROM replacement. You could technically do that with an HTC phone, I guess, but it would be very difficult to create the ROM and a complete waste of the hardware's other capabilities.
Integrating Rockbox functionality into a WP7 ROM is probably closer to what you're thinging of, but it still won't be easy. WP7 doesn't allow apps to replace core functionality built into the OS, so you'd need to create a custom ROM that uses Rockbox in place of the built-in media player.
I don't know how hard this woul be, but don't assume it would be easy. Android is pretty much nothing like WP7 internally. Android uses a Linux core, and apps for it are written using a Java variant or various native programming languages available for Linux. WP7 uses a Windows CE core, and apps for it are written using managed code or Windows native C++. Typically speaking, to port an app between the two system you must completely re-write it.
I do know that Windows Phone 7 uses C#, which is structurally similar to java. At that point it'd be a matter of porting over the java to C#, then figuring out the API equivalents. Still though, I don't know how possible this'd all be without native access to the device.
I've been using crDroid for a few years now -- it's my preferred ROM.
Someone recently ported it to work on the Pixel 2 XL, which is honestly the only reason I bought the phone. Well that and its bootloader was easily unlockable and is CDMA capable (Verizon.. sigh.)
However, regardless of how one goes about doing it, the wallpaper won't change. It's a bug within the ROM and I'm wondering how I might be able to fix it myself without having to wait for the original poster to release an update -- I've got a lot of free time and this kind of stuff genuinely interests me.
I've got (albeit basic) experience with python, perl, batch and shell scripting, pretty limited knowledge with C++ but am familiar with system architectures and such though have no knowledge of using java or porting apps, that kind of thing. I'm thinking this issue is just a problem with how the wallpaper's linked when selected.. or just a simple permission issue.
I've gone through the process of extracting the payload.bin and the image files within, looked through a few files and their contents (specifically for *wall*) but don't see anything promising. Anyone have any ideas who might be able to help a newbie with this stuff? I see a lot of posts on how to extract apk contents and recompile, that sort of thing. But I'm .. honestly not sure what I'm looking for, or whether it's an app-specific issue or a system issue, you know?
Kudos in advance.