Related
How is Android actually ported to work on the Vogue?
Are you guys literally taking the source code, changing things, compiling & releasing it?
How have you guys learned how to do it?
I'm really interested in helping out and would like to learn more, so any info is great!
Still interested. If any developers could chime in I'd really appreciate it.
Even if you just post a link to some resources I could read.
I googled...I found..
http://www.kandroid.org/android_pdk/index.html
It may be old IDK....Have fun
Thanks!
If anyone has anything else.. please post!
http://cs-alb-pc3.massey.ac.nz/vogue/
^A bit of info about how the project came to be and progressed
Thank you for the reply!
So, when it comes to myn and plemen releasing their builds, what exactly are they doing? Are they getting the source code from Google and completely customizing it, or are they customizing a source that has already been ported for the Vogue? Or... what?
To summarize:
The brunt of the porting effort is in the kernel (the heart of Linux) - a kernel which supports the Vogue hardware needed to be constructed, and the Android-specific extensions added and made to support the hardware. Martin (dzo) did most of the work on that.
Then, there are some core user-space libraries in Android which interface with the hardware and kernel (audio and radio being the big two, with lights, GPS, camera, etc. following). These also needed to be created and updated to support the Vogue hardware. Each time a new Android version comes out, these libraries tend to change and parts need to be rewritten to keep up with Android. A lot of people were and are instrumental in this process.
Then comes the questions you're asking, the "userland" pieces of the build: porters can start from an AOSP (Android Open Source Project) build, which is built ground-up from the released Android sources, a build from another phone (Tattoo, Hero, Droid, etc.), or an SDK emulator build (which is usually not preferred because SDK builds have extra debugging and are missing features for real hardware). To "port" a build, the Vogue libraries are copied in and init scripts and build properties are updated to support the Vogue's screen resolution and hardware initialization. Some porters go an extra mile and unpack, modify, and repack application data to support 320x240 better or to add new themes. For the most part, this is what people like myn and plemen do.
Builds can also be "zipaligned" (package files are aligned to match cache and block boundaries, so they're loaded faster), and image files downsized or removed to enhance speed.
Hi,
I would like to offer SVN hosting for ROM developers and their ROMs. This service is for HD2 ROM chefs totally free, without any charge in the future.
The only reason for this is that downloading from many web-based multiloads is very slow.
If you're interested, please, contact me through personal message.
I will write there SVN address, when first person upload his work: )
Note: If your ISP blocks SVN port (3690), it's okay, there is a choice of port redirection through port 80.
/* How to checkout repository */
Address of repository is svn://svn.dacesilianas.cz/xda-roms.
(If you have troubles with default port, you can use svn://212.80.85.51:80/xda-roms.)
If you're using Windows, you can download TortoiseSVN.
Great
Dacesilian said:
Hi,
I would like to offer SVN hosting for ROM developers and their ROMs. This service is for HD2 ROM chefs totally free, without any charge in the future.
The only reason for this is that downloading from many web-based multiloads is very slow.
If you're interested, please, contact me through personal message.
I will write there SVN address, when first person upload his work: )
Click to expand...
Click to collapse
Great idea! thanks for that
Great idea - i would love it - BUT - i think we already tried this with zzattack's mirror and I think there was difficulty in keeping it updates with all the latest releases.
You're right, but this can be caused only by ROMs authors.
Me, as ROM author, I would release my new ROM, so I upload it to SVN and everyone can download it, because our ROM repository is global for all ROMs.
Versions of ROMs will be written in SVN log and "by folder" I can show only versions of "my favourite" rom.
I think, this should work.
chris_ah1 said:
Great idea - i would love it - BUT - i think we already tried this with zzattack's mirror and I think there was difficulty in keeping it updates with all the latest releases.
Click to expand...
Click to collapse
I would love a collaboration of sort to get a mirror interface setup (much like cloud) with nodes in US, EU and APAC. So Chefs upload to mirror nearest to them and the other nodes replicate automatically. And of course people download from node nearest to them.
Seems doable and makes more sense to me
I only want to make some possibility for ROM downloading. I hope, this should work and it's up to you, if you use it. If not, nothing is wrong.
Since ROMs are downloaded by only few people at once, this is okay. Try it and we see.
PSFreedom's recent port to various Android devices using the msm72k chipset got me thinking. Has anyone taken a look at building it for the HD?
I currently use an X10 which unfortunately isn't supported but I have a Blackstone lying around that would be perfect. The hardware *should* be able to handle it but I have no clue how to even begin.
I can cross-compile modules for my X10 and so on but that's about it. I have no experience building a working kernel, the external module and finally making boot images for use with haret.
Anyone working on it?
ddewbofh said:
PSFreedom's recent port to various Android devices using the msm72k chipset got me thinking. Has anyone taken a look at building it for the HD?
I currently use an X10 which unfortunately isn't supported but I have a Blackstone lying around that would be perfect. The hardware *should* be able to handle it but I have no clue how to even begin.
I can cross-compile modules for my X10 and so on but that's about it. I have no experience building a working kernel, the external module and finally making boot images for use with haret.
Anyone working on it?
Click to expand...
Click to collapse
for educational purposes only..
oNNoZeLe said:
for educational purposes only..
Click to expand...
Click to collapse
Naturally.
So after some intense googling I've worked out a plan but I have some questions on compiling and assembling images. The plan goes like this:
Since I don't use the device as an actual phone I'm not bothered about losing things like making phone-calls or things like that. So I'll probably used a stripped down version of Donut or Eclair depending on whichever's the easiest.
Any recommendations on guides for compiling custom kernels, building external modules and preparing the kernel for use with haret?
I've set up toolchains for building Donut modules in the past and earlier I got a Blackstone toolchain set up from a guide over at www.androidonhtc.com but then I got stuck. Any help would be much appreciated, I've been at this way too long now.
Thanks
This would rock..
Sent from my MSM using XDA App
I would also love to see this happen.
I maybe wrong, but currently the Android releases are setup on the Blackstone it doesnt give you access to the card (for files) or USB connection (for transfer) yet as it's still in an unstable state...?
the battery issue is keeping me away from android.
usb connection is not there and access to card is not there from pc .
but access to card is there... using terminal emulator.
to check the usb config , i copied config.gz from /proc folder to /sdcard and copied it back while using windows..
so if the activsync type of connection is not there to put or get the files... that can still be done thru winmo... unless it is also hindering some other functionality that i'm not aware of
edit:
i'm using Android 2.2 (FroYo) On HTC [03 Sep 2010] (V1.6)
sunish said:
the battery issue is keeping me away from android.
usb connection is not there and access to card is not there from pc .
but access to card is there... using terminal emulator.
to check the usb config , i copied config.gz from /proc folder to /sdcard and copied it back while using windows..
so if the activsync type of connection is not there to put or get the files... that can still be done thru winmo... unless it is also hindering some other functionality that i'm not aware of
edit:
i'm using Android 2.2 (FroYo) On HTC [03 Sep 2010] (V1.6)
Click to expand...
Click to collapse
I have atleast ADB working over USB but it requires that I boot with the cable plugged in. So USB works, but I don't know to what extent.
ddewbofh said:
I have atleast ADB working over USB but it requires that I boot with the cable plugged in. So USB works, but I don't know to what extent.
Click to expand...
Click to collapse
did you try droid explorer? several things work with ADB enabled..
I have a lot of time on my hands, but no knowledge of what needs to be done in order to work out how to get this working.
Is there any system already ported that we can look at that has similar devices to the Blackstone - perhaps the HD2?
If not, if someone can advise on what needs to be worked out, I dont mind putting the time in.
DejaVu1977 said:
I have a lot of time on my hands, but no knowledge of what needs to be done in order to work out how to get this working.
Is there any system already ported that we can look at that has similar devices to the Blackstone - perhaps the HD2?
If not, if someone can advise on what needs to be worked out, I dont mind putting the time in.
Click to expand...
Click to collapse
did you check one of the other threads on "getting this to work on XDA?"
I've been on checking XDA-Dev (as well as other sites) since the release of psgroove/psfreedom for updates.
I've been watching all the other devices getting ported too (Nexus One, Bravo, Dream, Desire, Sapphire, TI-84+ (CALCULATOR!), Dingoo), but really dont know where to start for the Blackstone - which has been dishearting as the Teensy++ boards are sold out worldwide!
But surely, if a calculator can do it...!!
Supposedly, the USB Device is the same as the others (MSM72K) that have already been ported. It just needs to be written into the psfreedom code I guess and run a certain way depending on the system the Blackstone would use.
I dont think Windows Mobile has 'root access' so hence the use of Android via Haret. Although it's not stable as such, I think it should be sufficient to run this (if possible through Haret?)
Some of this may seem like complete crap - but I will be the first to admit, I dont know what I'm talking about. It's just the gist I'm getting from surfing the internet over the last few days.
From what I gather, all the (hardest?) work has been accomplished (it's proven it can work with Android!) and I'm sure the Dev's that have completed it will share their findings to help other devices to work?
Also, looking through most the forums on here, Blackstone being THE most popular, I think the port would be appreciated by a lot more people.
The reason that Blackstone is the most popular IMHO is that Windows Mobile running on it is terrible. When I got mine originally from O2, the ROM was sooo slow. The great work the Chef's do on here are appreciated by thousands as they are making the phone usable again. Bring on Adroid for this phone... IT NEEDS IT!!!
If it's pointed out what needs doing. I'll happily do it - I've flashed my phone sooo many times lately, a few more wont hurt!
It'll be Awesome!!!!
I was under the impression that Blackstone has MSM72K (reference to which I found in a very old thread.
following is the text form config.gz which uses MSM_HSUSB
so only a ROM chef can tell us which driver is used in blackstone.
We can only request all the developers on this site to look into this and guide us.
Code:
# USB Function Support
#
CONFIG_USB_FUNCTION=y
CONFIG_USB_FUNCTION_MSM_HSUSB=y
# CONFIG_USB_FUNCTION_NULL is not set
# CONFIG_USB_FUNCTION_ZERO is not set
# CONFIG_USB_FUNCTION_LOOPBACK is not set
CONFIG_USB_FUNCTION_ADB=y
# CONFIG_USB_FUNCTION_UMS is not set
CONFIG_USB_FUNCTION_MASS_STORAGE=y
# CONFIG_USB_FUNCTION_DIAG is not set
CONFIG_USB_FUNCTION_ETHER=y
CONFIG_USB_FUNCTION_RNDIS=y
# CONFIG_USB_FUNCTION_FSYNC is not set
# CONFIG_USB_FUNCTION_SERIAL is not set
# CONFIG_USB_FUNCTION_PROJECTOR is not set
# CONFIG_USB_FUNCTION_MTP_TUNNEL is not set
http://forum.xda-developers.com/showthread.php?t=777120 The HD2 get a haret Port
It doesn't work on a HTC Touch HD T8282, Won't boot. I think, as a WM6.1 phone it can't be rooted.
HD1
sunish said:
I was under the impression that Blackstone has MSM72K (reference to which I found in a very old thread.
following is the text form config.gz which uses MSM_HSUSB
so only a ROM chef can tell us which driver is used in blackstone.
We can only request all the developers on this site to look into this and guide us.
Code:
# USB Function Support
#
CONFIG_USB_FUNCTION=y
CONFIG_USB_FUNCTION_MSM_HSUSB=y
# CONFIG_USB_FUNCTION_NULL is not set
# CONFIG_USB_FUNCTION_ZERO is not set
# CONFIG_USB_FUNCTION_LOOPBACK is not set
CONFIG_USB_FUNCTION_ADB=y
# CONFIG_USB_FUNCTION_UMS is not set
CONFIG_USB_FUNCTION_MASS_STORAGE=y
# CONFIG_USB_FUNCTION_DIAG is not set
CONFIG_USB_FUNCTION_ETHER=y
CONFIG_USB_FUNCTION_RNDIS=y
# CONFIG_USB_FUNCTION_FSYNC is not set
# CONFIG_USB_FUNCTION_SERIAL is not set
# CONFIG_USB_FUNCTION_PROJECTOR is not set
# CONFIG_USB_FUNCTION_MTP_TUNNEL is not set
Click to expand...
Click to collapse
Afaik msm72k and msm_hsusb are different drivers for the same hardware. The kernel in use for the Blackstone port is 2.6.27 and it uses msm_hsusb. Newer kernels are probably different.
psfreedom-for-htc-touch-pro1-2diamond-1-2
Look at this site, you got to copy 3 things and you must have Xandroid 2.2
h**p://howtohackps3.com/psfreedom-for-htc-touch-pro1-2diamond-1-2-is-now-available/
^^ will try it once i get home
It Works !!!!
Yeah Yeah Yeah !!
good temp solution.
as u need to connect the phone to pc when android is booted.
will wait for dongle's price to fall down
Description:
AndroidLib is a .NET assembly written in C# (C-Sharp) that easily handles communication between a connected Android device and your program. Currently, there is a large amount of automated controls, eliminating thousands of lines of code the programmer has to write themselves. The class AndroidController is a semi-wrapper of the ADB (Android Debug Bridge) binary. The other class you will be working with the most is the Device class. This class contains useful information about the device (for example: software/hardware info, memory info, battery stats, mount points for partitions, root status, busybox information, and much more), as well as exposes many instance methods to control your phone such as Rebooting, Mounting Filesystems, Push/Pull/Install Files, and much more to come. AndroidLib contains all of the Android binaries necessary to work properly. AndroidLib also assumes that the phone's USB drivers are already installed correctly on the target machine, or that your program will take care of it on it's own.
This is perfect for any developer who would like to create, for example, an auto-rooter or any other application that needs to connect with Android devices through a .NET application. AndroidLib provides all the methods needed to communicate with the Android device. This will cut back on the code you have to come up with and write yourself by a HUGE amount!
What it does:
Provides easy-to-use code for communicating with Android devices in .NET
Provides easy access to information about the connected Android devices
Has a large list (and growing...!) of methods that control connected Android devices
Please credit the work here by me in your own projects; not only to give thanks to me and the many hours I am putting in to this project, but so others know where to find it if they need to!
Usage:
Add a reference to AndroidLib.dll in your .NET project and begin using this great API. Please refer to the "Getting Started.txt" guide and full documentation included in the zip.
Requirements:
.NET 3.5 or Higher
Changelog (Only most recent version displayed, full Changelog in download)
Version 1.5.1.0 | 01.21.13
Fixed Device.InstallApk() bug
Download Latest Release
GitHub
Online Documentation
Sample Solutions Using AndroidLib:
C# (C Sharp)
Visual Basic (VB)
AndroidLib Featured Projects by XDA Users:
RegawMOD Evo 4G LTE Rooter - XDA
RegawMOD CDMA Hero Rooter - XDA
RegawMOD Rebooter - XDA
Droid Manager by DeepUnknown - XDA - Google
Android SMS - XDA - Home Page
Quick ADB Pusher by Goatshocker - XDA
reserved just in case
It's very useful, thank you very much, im planning to code a Filemanager like qtadb, because qtadb is sucking too often
In the process of completely redesigning the library (due to coding stupidity), basically from the base class up. I should have a beta1 out by this weekend for testing. All that are interested in beta testing this library for their Android .NET projects, post here and I'll add you to the list of testers!
It would be great!
Can you add something like adb forward? So we can connect to an android service without using ADB, that as we all know sucks!
Mrc527 said:
It would be great!
Can you add something like adb forward? So we can connect to an android service without using ADB, that as we all know sucks!
Click to expand...
Click to collapse
Yeah, I'll throw in a method to create a port forward. What I have now uses the bridge, which is included in the assembly, but handles all of it silently and very well. I should have a build out soon (most likely this weekend). As long as you don't dispose the AndroidController object, that port forward will be good, so you can use your own Socket code
regaw_leinad said:
Yeah, I'll throw in a method to create a port forward. What I have now uses the bridge, which is included in the assembly, but handles all of it silently and very well. I should have a build out soon (most likely this weekend). As long as you don't dispose the AndroidController object, that port forward will be good, so you can use your own Socket code
Click to expand...
Click to collapse
Great work! really, great idea!
You can change the .NET to 3.5? I too code in .NET, and I try to keep the .NEt version as low as possible!
SimranSingh said:
You can change the .NET to 3.5? I too code in .NET, and I try to keep the .NEt version as low as possible!
Click to expand...
Click to collapse
Yeah, I actually did that a few days ago, forgot to update the OP.
Where is it possible to download?
Mrc527 said:
Where is it possible to download?
Click to expand...
Click to collapse
I'm just writing the documentation for this. I'm pretty sure I'll have it done today.
Yeah! Just a joke. When finished I'm sure will be a success!
Inviato dal mio Galaxy Nexus usando Tapatalk
Making some last minute changes to the Device class, then I'm going to finish the documentation and release it. Just keeping you updated.
Ok everyone, the new documentation is up (Online) (Offline). For the beginning of this product, I would like developers to pm me, or reply here in the thread if they would like to try the library out for their project, and I'll send it to them. It's still under development, and there will be updates coming out regularly. Shoot me a pm or post here and I'll send you a link right away.
regaw_leinad said:
Ok everyone, the new documentation is up (Online) (Offline). For the beginning of this product, I would like developers to pm me, or reply here in the thread if they would like to try the library out for their project, and I'll send it to them. It's still under development, and there will be updates coming out regularly. Shoot me a pm or post here and I'll send you a link right away.
Click to expand...
Click to collapse
Meeeeeeeeeeeeeeeeeeeeee!!
Hi,
I'm C# developer and i would like to try your lib, can you send it please?
Thanks in advance, and great work.
Hey guys, check the first post to download the library. It is in a zip which includes the dll, "Getting Started.txt" and the documentation. Please read the getting started guide before diving into it! And please give me feedback on it. That would be much appreciated in order for me to deliver a better product.
Dan
Great work!
It works without any problem to me!
Next update will have these features internally implemented:
Package Manager (inside the phone's shell)
Ability to install/uninstall apks
Ability to freeze/unfreeze apks
Ability to backup/restore apks
A class that will handle signing of update zips
More internal information about connected device (cpu, environment, etc)
Possible wrapper of AAPT
That seems like a good amount for the next update. Please post anything you wish to share about the library after using it for these few days.
Hi All,
I'm a software developer, reasonably comfortable with compiling apps in Linux, though still got more to learn on inner workings of the full system.
I've been thinking about following the Linux from Scratch book for a while - and also about converting my Nook e-reader into a useful device for developing on when out im the sun.
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot (I'm familiar with these problems, but not solutions or good workarounds).
What I'd really like is a good understanding of:
- what tool chain I need to setup
- What has been tried already and what the problems were
- any further help/datasheets that can get me going
I'd have posted this in the 'android development' area as the closest forum for what l'm trying to do, but apparently I'm not allowed until I've got my post count up - so I'm being forced to post in 'general'. If someone agrees and can move it, that would be great.
P.s. I have searched the xda site, but I'm not finding what I'm looking for. I'm sure it must be here somewhere, so any pointers/links on where it is would be appreciated.
SimonSimpson said:
Hi All,
I'm a software developer, reasonably comfortable with compiling apps in Linux, though still got more to learn on inner workings of the full system.
I've been thinking about following the Linux from Scratch book for a while - and also about converting my Nook e-reader into a useful device for developing on when out im the sun.
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot (I'm familiar with these problems, but not solutions or good workarounds).
What I'd really like is a good understanding of:
- what tool chain I need to setup
- What has been tried already and what the problems were
- any further help/datasheets that can get me going
I'd have posted this in the 'android development' area as the closest forum for what l'm trying to do, but apparently I'm not allowed until I've got my post count up - so I'm being forced to post in 'general'. If someone agrees and can move it, that would be great.
P.s. I have searched the xda site, but I'm not finding what I'm looking for. I'm sure it must be here somewhere, so any pointers/links on where it is would be appreciated.
Click to expand...
Click to collapse
I have tried to get info on such things three times over 2 years for different devices, no one every seems to point me in the right direction, the most i have been able to find out is how to make compile cm and a little bit of how to customize roms, not to be a downer but i think the process is often so different for ever device and difficulties usually happen that the only people that build roms are people that have either have experience I n some form from their job, just edit existing source for cm(updating to a new version, customizing roms ect...) or have screwed with the stuff for years till the point that they just figured out alot of problems themselves. Wish a could find a good guide myself to atleast get the basic dependencies required for a device to boot together, if i could get something to boot the rest of the issues could be worked out with trial and error, boot noone on xda, Android authority, Reddit or cm's own forums goes into enough depth to make that possible.
Hi jaykoerner,
Thanks for your reply - good to know I'm not alone with my echo!
I've discovered some useful links if anyone wants to begin getting to grips with all this...
1. XDA Devs has a wiki (not sure how to find from the forum links...?)
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch
2. There's a (atleast one) customized kernel (and probably a dev-tool chain) available on GitHub:
https://github.com/javifo/NST/tree/master/kernel -- including kernel compilation instructions
https://github.com/javifo/NST -- root of the repository.
3. Parallel to Raspberry Pi kernel compilation (so you may want to learn from that as it probably has more articles)
https://www.raspberrypi.org/documentation/linux/kernel/building.md
I'll post more when I next do something with the information (Still want to understand more on the android HAL)
Hope that helps someone!
SS.
SimonSimpson said:
Hi jaykoerner,
Thanks for your reply - good to know I'm not alone with my echo!
I've discovered some useful links if anyone wants to begin getting to grips with all this...
1. XDA Devs has a wiki (not sure how to find from the forum links...?)
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch
2. There's a (atleast one) customized kernel (and probably a dev-tool chain) available on GitHub:
https://github.com/javifo/NST/tree/master/kernel -- including kernel compilation instructions
https://github.com/javifo/NST -- root of the repository.
3. Parallel to Raspberry Pi kernel compilation (so you may want to learn from that as it probably has more articles)
https://www.raspberrypi.org/documentation/linux/kernel/building.md
I'll post more when I next do something with the information (Still want to understand more on the android HAL)
Hope that helps someone!
SS.
Click to expand...
Click to collapse
My initial thought was that toolchain should match the underlay Linux kernel of Eclair (2.6.x.y) for us to be sure it could be run on NST. This info that I still have to search through is certainly helpful. Thanks!
SimonSimpson said:
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot...
Click to expand...
Click to collapse
Neither the NST or the newer glows use device trees.
In the Glows this is all handled by the custom ntxconfig which allows simple configuration.
For building Android apps, you use the straight Android SDK, possibly also the Android NDK (for native code).
You'd also use the NDK for building command line utilities.
I've never built a kernel from scratch, but I have binary modified/patched them.
There is the simpler bit of patching system image ramdisks which can be conviently handled by my imgutil.exe in the signature.
If you want to do audio, you really are better off with the Glow4 (7.8") which actually supports it.