Database Info

Help On Porting An Ai Prog

how hard is it to port windows progs to run on ppc (wm5) there is a great product for the pc called ulta hal heres a link to see what it is
http://www.zabaware.com/
now if this could be ported to ppc it would turn si-fi to si-fact it would open up a whole new world to the ppc
any info you guys could give me would be a great help or any guides on porting software
please guys id love to see this software running on ppc
for now its a dream but please help me make it reallity
thank in advanced

Ok here goes:
1) As this is a commercial product and there for getting its source code is not an option porting it would really mean just writing the whole thing from scratch. Not really feasible.
2) From just reading the intro on the site it seems that PDA type device don't really need this kind of app. After all all that 'secretary' like functionality is already exposed for one click use and there is no shortage of various reminders (built in and 3rd party apps).
4) Microsoft Voice Command and Cyberon Voice Commander (full version, not the built in voice dial crap) can launch apps and do other stuff as well as dial the phone so there goes that functionality.
5) For most devices having 2D / 3D animation constantly taking up part of the screen and all that other functionality running in the background may just be to much of a drain on resources.
Sorry. I didn't mean to pummel your idea in to the dirt, but I just can't see something like this happening with the current abilities of our devices.
Perhaps in a few more years as the phones / PDAs get more powerful, but not now.

thank you for you reply well iguess ill just have to wait but it would be nice to have it on ppc as all the app out for ppc at the min dont learn as hal does if i was running hal i could say for eg becky it my hair dresser her phone number is 00000000 and if later on i wanted to ring her i could say ring the hair dressers of i could say who cuts my her and hal would reply becky cuts your hair
its not a nessasery prog but it would make a great protable personal assistant

could i use this to do it http://en.wikipedia.org/wiki/Bochs
it allows you to run x86 code on a ppc
i know i should probable drop this idea but i cant i really want to see it running on a ppc

Close but no cigar, as they say.
This thing will emulate the PC but not the OS which means you somehow need to stick (what is the minimal version HAL runs on?) desktop windows on you device, and get it to run under the emulator.
Do I need to continue?
It might be possible to create something like this for the newer high powered devices (certainly not my Jamin or your k-jam). Perhaps you could peach the idea to the manufacturer.

i have already got intouch with the makers of hal and am still waiting for a relpy
yer i think i may have to give up on this one as hal uses the ms assistantce so id have to get them working before i could even mske a start on the speach system and that would take up most of my mem but yer there is a but i dug out my old pc the other day its has a 350 cpu and 64mb of ram which is way below my ppc and hal was running fine and i was also able to have enough mem to run ms media player and ie exploerer and my ppc has a 400mhz cpu and 128 mem so there is still hope

You can't really compare PPC CPU and computer CPU speeds like that - they're different types of chips off the bat, and also they run different operating systems, which almost always means the computer ends up doing more things and doing them faster. Take the difference between Intel XScale chips and Texas OMAP chips for example - both are PPC CPUs, but the OMAP's 200MHz can almost match the Intel's 416MHz, despite the former being less than half the speed of the latter.
It's not to say that running this software isn't possible, but you might need a lot more grunt than you expect. Remember, the Playstation 1 had a 33MHz chip, yet if anyone wants to emulate a PSOne on the PC it'll take >400MHz for good performance (though note that this is emulation. Obviously if someone was able to recompile the PSOne's software to run natively on PC hardware, then it would be significantly more efficient.).

yet another "wm6.5 vs Android" post !

Hi all,
I have been testing android for the last couple of months and I wanted to share with those of you who did not dare or bother to try android or did so but some time ago. I do not pretend to discover anything, simply give some info to those curious as I was a few months ago...The post has not much to do with wm6.5 development so maybe should be moved elsewhere, I post here because it is where in the past I read questiosn and answers about this question.
Android Pros:
Wonderful interface and navigation concept: graphics, scrolling, effects, overall resolution and touch experience I think it is much much better, Multitasking but the UI acts more as an iPhone or Treo, when you leave an application you are exiting it, from a navigation point of view. Another thing I like is the fresh concept of the phone: the notification bar and slide-down courtain, the lock screen, the keyboard are much better. On the side of the sotware is a cloud2.0 phone, since lots of applications tend to connect to the itnernet to fetch contents, context or whatever. this means you do not need to configure or copy so many things each time you flash. It has changed a lot since the first time I tried it: wifi works perfectly, GPS and car kit works perfecly, music, etc. It is very thumb friendly, You can install it as the only OS of the phone ("nand" install) or to run it from wm ("haret") install. They work pretty well both. You can even find dual bootloaders so you can choose which OS to load each time
Android Cons:
Our beloved Polaris are old for this trip !! Android seems to have a high consumption of RAM compared to wm6.5. Regarding storage it has been solved using the sdcard as internal storage but it is not perfect since the sd card can become corrupt much more easily than in Windows. The kernels are ported from Vogue (dzo) and this means no front camera, as Vogue does not have it. BT files transfer to PC & music transfers to headsets have limitations also. Another limitation is for people like me, wanting to have installed dozens and dozens of programs, ready to use: in my experience it seems this takes a lot more of RAM and transit to the cache or sd than in Windows so this means with a 100 programs the device is almost ununsable (on the other hand, with 15 apps is 1.000 times more fluid than windows). Another con (or pro) is the learning curve of the lynux/android new environment. Seems quite easy to modify a rom, simply adding apks (cabs) to the tar file and signing it but scripting, customization, registry, programming seems to me much more complex (to make an analogy, wm6.5 is visual basic and android is java). Another big con is the shorter battery (it is shorter and the phone is more oriented to wireless connections) and the need to have a data plan. With the radio I have used for the last years, the signal is worst.
Not pros or cons but differences:
Android is great for you if you use google (I do): gmail and contact integration is great. Of course, the same goes for WM6.5 with Outlook. Android is great if you have a data plan. If you don't (I don't) you can still use it but you better be sure you now how to cut traffic to the internet. Android stock of apps are oriented to localitzation services (Gps, camera recognition of whatever is focusing, social networks, etc) while wm seems to have still a larger stock of apps, more oriented to productivity, PIM, etc. For example, wm has much better off-line navigation programs since android are all connected to gmaps or whatver.
From the point of view of people enjoying cooking roms, customizing, etc. Android+Polaris seems a step hill to climb but Polaris+wm6.5 has not a long horizon ahead. Well, I hope this helps some of you to decide it it is worth to test android or not and stik or not to the Polaris.
enjoy your devices !

Good but not a replacement POLA200
Hey cruzza i tried out near on all of the android NBHs and yes they are a joy to use on the polaris.. But and heres a big BUT it is not very stable to use as a day to day op system for phone. The cameras weird to use. After working nice for one day it started to force close with everything - there was always a surprise waiting for me when i woke my phone up. You are right bro very very nice to look at and use i cried when i had to go back to windows.. I am curious to know how does your android perform - day in day out..

I've been using Android for six month first on haret then on nand and what i can say is that a lot of concession has to be made, and some are very important regarding stability, battery life and phone functionality
You have a great ease of use and a better feeling on android but general performance and memory management are not as good as on windows mobile
I was a flashing addict and i missed a lot of phone call, gps data due to bugs, flashing time, bad battery life so i decided to turn back to windows mobile (3LIT3 VIII) and i'm very pleased with it

Well, I do agree with most of what you replied. The current release and setup I am using is quite stable for a "light" use: no front camera, no videocall (never used in wm6.5 btw), no native T9 dialer, no native birthdays notifications, limited bt file transfer are a pain but you can live with it. The rest works pretty well: bt car kit, wifi, GPS, UI navigation, phone...In terms of apps I miss lots of things: an app to filter contacts to be sync'd with bt car kit, not so good nav programs (igo, compemaps have no equivalent...). However, you can live without it and the UI is so nice to handle, that it is difficult to go back to the blurry 6.5 or 6.1 screen and I love sync with google calendar and mail. I also love the navigation and buttons concept, the courtain with the notifications and many other things. I also love the open concept behind linux and android. Remember Da_G being warned by lawyers for posting the 6.5 releases? that can not happen in Android. Some brands even support officially roms made by users !!!
The problem is that we certainly have a device old to cope with it all since Android seems to eat more RAM: this means the RAM is eaten only by having installed let's say 100 programs (in wm6.5 It performs better in my experience with so many programs). The performance of the device drops exponentially as you eat resources. Then you may want to try some more advanced setup like installing the NAND to the SD card either to a separate partition or to an enlarged data file, but then my experience so far is that the SD Card becomes unreliable (you may loose all) so yo need to transfer the backup to the pc...and that is difficult to live with for me. Another thing that wm6.5 beats android is about scripting: with mortscript it is so easy in wm6.5 !! but with Android you need a heavy pc platform and you need to learn new languages and tools, far more complex and advanced than windows equivalents.
How do I look at it? I have stopped working on my wm6.5 roms since I do not think I will last much more time on wm6.5; I will probably gift me a data plan (I never had one) and a super android terminal with a good battery, screen, accelerometer and ROM (+ all I have in the Polaris). Until then I have decided to be again a (almost) end user.
The other reason, probably the most important, to change device is that the Polaris forums (both android and polaris) have little posts, new ideas, knowledge sharing... since most people already upgraded the device, and xda developers was in my case the driver to get curious about how these devices work.
So I think wm6.5 works better in our Polaris for a heavy use thanks (thanks to all who made it posible) but Android works pretty well in our Polaris for a basic use and for evaluating wich one you like more. The easiest thing to do is test a haret installation (this means you load wm6.5 as OS, and then run haret = linux as a program that executes android) and if you like it, test nand installation with a different sd card.

pinkstuff said:
Hey cruzza i tried out near on all of the android NBHs and yes they are a joy to use on the polaris.. But and heres a big BUT it is not very stable to use as a day to day op system for phone. The cameras weird to use. After working nice for one day it started to force close with everything - there was always a surprise waiting for me when i woke my phone up. You are right bro very very nice to look at and use i cried when i had to go back to windows.. I am curious to know how does your android perform - day in day out..
Click to expand...
Click to collapse
Well, the difficult part with Android is to now what to flash: if the camera or wifi do not work well these means your android kernel does not like your "rom" release. In wm6.5 we only had two kernels the old kernel and recently a "native" wm6.5 kernel.
In Android you have more kernels basically programmed by a few expert cookers and developers, mostly DZO. You have a good post by l1q1d listing setups that should work on all devices. Try and ask for help. the newest kernel is 2.6.32 I think but has no good camera drivers. The previous kernel 2.6.25 supports camera but it is quite useless in my opinion (yes, the "horrible" camera we have can perform even worse than in wm!!). These are the kernels I have been testing but probably there are others. These kernels can not be combined with any release, the cooker must adapt the rom release to the kernel. So you need to locate a working combination so you must use the combinations tested by others (or experiment yourself). You also need to become familiar with modding the NBH to suit your device screen (the way to is atools again by l1q1d) Android has several major releases (eclair, froyo, ...) froyo 2.1 is like wm6.5 more experimental so many peopple stick to android 1.5, not so nice, but they say it works in a more stable way in the Polaris. Hope this helps.

Hi there,
I'm using a different device but I thought I'd comment anyways I cannot agree more to the statement of our devices being old. I think Android is a truly magnificent OS chained to our limited resources, however it is an amazing performer.
I am still on Donut (1.6) exactly because of the same reasons, battery life, reliability and speed. I have tried and messed with a lot of Android builds ported to our devices and I couldn't get the feeling off me that with Eclair and Froyo my poor Kaiser was struggling to operate.
I chose Android because no matter what I did to Winmo I was never completely satisfied. The closest I got to it was when I got PointUI and made myself a few custom things for it. In the end the performance with video and games was not so good due to the graphics driver issue from long ago. Once I got Android I had all that I needed, a good graphics performer, didn't need to find too many extra apps to satisfy my needs, and a GUI that I truly enjoy. I am also a very heavy gmail user and I do not even have outlook installed in my computer.
I love linux and terminal, another point for Android at least in my case.
On the development side of things my heart is with C++ and C# so I still prefer the .NET side of things. Java which thankfully is similar enough to C# as to grab it and start working on it for the first time is a very interesting experience, still getting used to a new environment though.
I use this as my everyday phone and after months of continued use I can't complain. I messed with Winmo so much that it was sluggish and needed to do a hard reset every now and then anyways.
Thanks for your info. I am sure it will help other users decide to give this a try. This is the only way to know for sure what your next device will be. As for me, I don't think I can live without Android anymore.

PC emulation on Android - OS XDA project links.

So in this thread it tells you how to install pc operating systems like windows and linux on the Evo 3D.
http://forum.xda-developers.com/showthread.php?t=1459153
This, is freaking awesome. This one is a big breakthrough.
----
Here is the thread in the Nook Color forums for ubuntu on the device:
http://forum.xda-developers.com/showthread.php?t=1055954
----
These two threads are native installs, not using some client to access the installation, the device itself is the client as it should be.
This is not some chrooted virtual OS simulation, but the real deal installed to the device.
----
In the back of my mind i've wanted to play with ubuntu installed on the MT4GS, but not a virtual installation I want it installed and running on the device natively.
I definitely don't have the time to do this and a lot i'm trying to do around here even if I wasn't in my busy season for work.
Dropping this information so I can find it later when I do get to trying to get ubuntu (and now windows XP looks like a possibility) installed on this device.
If anyone else feels like looking into this, here's a good place to start. If anyone comes across any other projects that are the real deal and not virtual installs please post links here.
Have fun!

Blue6IX said:
So in this thread it tells you how to install pc operating systems like windows and linux on the Evo 3D.
http://forum.xda-developers.com/showthread.php?t=1459153
This, is freaking awesome. This one is a big breakthrough.
----
Here is the thread in the Nook Color forums for ubuntu on the device:
http://forum.xda-developers.com/showthread.php?t=1055954
----
These two threads are native installs, not using some client to access the installation, the device itself is the client as it should be.
This is not some chrooted virtual OS simulation, but the real deal installed to the device.
----
In the back of my mind i've wanted to play with ubuntu installed on the MT4GS, but not a virtual installation I want it installed and running on the device natively.
I definitely don't have the time to do this and a lot i'm trying to do around here even if I wasn't in my busy season for work.
Dropping this information so I can find it later when I do get to trying to get ubuntu (and now windows XP looks like a possibility) installed on this device.
If anyone else feels like looking into this, here's a good place to start. If anyone comes across any other projects that are the real deal and not virtual installs please post links here.
Have fun!
Click to expand...
Click to collapse
Regardless of what impression you may have, it is ABSOLUTELY IMPOSSIBLE to run MSWin on ARM hardware natively. The reason for this is that MSWin is x86 and ARM is... ARM. The approach used in the first link is to use BOCHS (pronounced "Box"), which is a VIRTUAL HARDWARE EMULATOR. It requires a host operating system to be functioning in the background, in this case Linux.
As for Ubuntu... well sure. No problem. Its Linux and the phone runs Linux. Not that big of a stretch to replace the Android parts with GNU.
Note that NONE of this is any kind of "great breakthrough". Bochs has been around for a VERY long time. First OPEN SOURCED in early 2000. Yeah, 12 years ago. As for Ubuntu... well I suppose that the main reason that most people aren't making a native android replacement out of ubuntu, is that not many people are all that interested in it. Cute in theory, but not practical.
What would be a more worthy project would be to upgrade android to GNU libraries and utilities. This would afford us an actually USEFUL balance between the two. Also the ability to run X *through* android without having to do stupid things like VNC. Have the proper interface ***AS AN ANDROID APPLICATION***, leaving Android to work (i.e., phone calls, etc.) while simultaneously offering the standard Linux applications.
My thought though, is that this is becoming less and less important. Firefox is on Android now, the Document foundation has announced LibreOffice for Android -- supposed to be by late 2012 to early 2013... GIMP has no place on Android... That certainly covers the basics.

Appreciate the post. I didn't have time to dig into it too deeply, so took it at face value for the impression I got. Happened to come across it in passing and didn't want to lose track of something vital to the future dev of a project like this on the doubleshot. (but definitely this doesn't belong in the dev section at this time - just clutter there.)
I was hoping people would add to it, especially the way you have, who had more of an understanding of what's going on there - I didn't realize that it was a virtual environment for the windows stuff, but it did seem to good to be true.
Even if no one responded I figured the thread would get pushed down out of the way, but still be here when I got the time to come back to it.
----
My reason for running native linux on the device itself is to be able to use the Android SDK and tools without needing a computer to do so. I have 2 of these phones and a Nook Color. The NC has USB host support, so I could plug the doubleshot into it without frying either device. (yes, i'm blending android and linux concepts here - but usb host support in android shows that it's capable of doing it)
Even from one doubleshot to the other I could use wifi adb for a lot of stuff without plugging them into each other through USB and frying the phones. So that would be a victory as well.
The lack of a hardware charging circuit in the doubleshot makes the worry of frying the phones a big deal, power transfer through USB is a big hurdle to jump in management.
Beyond that - the doubleshot is powerful enough on hardware specs to be able to compile a kernel, but that's not gonna happen through a virtual linux install because the overhead is too much. A native install might just be able to do it though. Won't know until I try, but it's worth the work to get to the point of trying, even if it doesn't work out.
The Nook Color probably won't be able to compile a kernel - it's asking too much from a device not really able to handle that.
Getting what I mentioned above to work would mean I could do all my dev work with what fits in my pocket, and let me keep working wherever I am.
I do like the idea of an app to work with this through Android itself - but I don't see how I could use the SDk and variety of user-created tools without a native linux install. Worth pursuing either way though.
If anyone has anything to add, i'd be welcome to hear it. Just understand this is not a project i'm working on or actively pursuing right now - but fully intend to down the line.

Actually blue. There is a thread somewhere that has a step by step on installing ubuntu on gingerbread. I meant to add it when I added the backtrack link. For some reason I didn't, I probably forgot, I actually think the link for it is in the backtrack thread in the sticky.
If I do find it ill let you know.
Sent from my ICS Splashed using Tapatalk

[Dev] Who wants to port ZGrom or GMenu2x?

Here's a link to the project:
http://code.google.com/p/zgrom/
A cut&paste from the page:
ZGrom is a gaming oriented distribution for Sharp Zaurus PDA devices. It's a console based distribution built around the Gmenu2X SDL GUI. ZGrom has a wide selection of quality emulators, game engines and apps. Currently, ZGrom only supports the following Zaurus models:
•C-1000 - Akita
•C-3000 - Spitz
•C-3100 - Borzoi
•C-3200 - Terrier
ZGrom comes with GINGE. In a nutshell, GINGE enables ZGrom users to run unmodified GP2X binaries. Some of the emulators and game engines that come with ZGrom are plain, unmodified GP2X binaries that execute on Zaurus devices via the GINGE static loader.
A link to the gmenu2x page:
http://mtorromeo.github.com/gmenu2x/
A cut&paste from the page:
GMenu2X is a frontend application targeted at embedded devices, originally developed for the GP2X and successively ported to other devices.
GMenu2X provides an easy to use interface with quick access to the games and applications of the device trough links similar to those found on PC's desktops.
Its interface is fully customizable with skins.
Other features include: built-in selector for emulators, manuals and readmes integration, built-in overclocker, gamma and volume configuration, ram timings tweaker.
I started working with these but like with other projects... i'm short on time these days. The last of my efforts had a working kernel for these, only a keymap was needed to give to the zgrom developer to build a rootfs, and for someone to text and debug.

IMO the better way would be focusing on developing Android distro, because probably most people are still waiting for working Android on our beloving UNI! Anyway, your efforts are great and mainly because of you UNI developing is still alive!!! Good luck!!

l2tp said:
IMO the better way would be focusing on developing Android distro, because probably most people are still waiting for working Android on our beloving UNI! Anyway, your efforts are great and mainly because of you UNI developing is still alive!!! Good luck!!
Click to expand...
Click to collapse
Lol, I know, I’m taking a break waiting for another project to finish up:
http://forum.xda-developers.com/showthread.php?t=1948803
I’m working on shrinking android now; deleting unneeded library’s and functions to lower memory/processor requirements and running processes. This OS is better suited for people who don’t use their universal as a phone and only have 64mb of ram. I don’t have time to work on this either, the question “Who wants to port ZGrom?” wasn’t rhetorical; I really want someone to pick up where I left off porting it. And android for universals is mostly done all hardware except the cams work. Power saving, gprs, sound on both ends of the call all work… I just need to trim and speed it up….and learn some arm assembly to add in iwmmxt optimizations.

I understand that 64 MB of RAM is too little to run any recent Android version (and by recent I mean higher than 2.2), so it'd be good if there was some alternative OS to bring life to old Universals with the standard RAM - even if that new 'life' doesn't including phone abilities. I don't think the PXA 27x CPUs aren't really that optimized to run Android either (Android can be slow on ARMv6, let alone ARMv5). I'm not telling you to give up on the Android thing; just trying to make people realize notime can't focus forever on something that can't be further optimized... but if it can, then just go ahead
In that sense, I support any development efforts towards something that's not Android.
Also, the work done in porting recent Linux kernel versions can be used not only in Android but in any other Linux-powered OS porting. I may have a go at it... once I format my computer with a bigger ext4 partition (currently out of space to install any kind of cross-compiling tools or SDK) - and this can get delayed for several months.

I was playing around with my Universal (with a dead battery), running old Linux distros on it (with things like Qtopia and Opie), when I started thinking if there wasn't a more recent thing to run other than Android. Then I remembered I had promised to try to port this thing once I got my computer formatted...
Actually I have already formatted my computer and now I have a mostly free >250 GB ext4 partition. I'll only be able to start working on this in the beginning of July, however.
This seems like the perfect use for a Uni that doesn't survive when it isn't charging.

[Firefly] [ROCKCHIP] [ITX-3588J] ITX-3588J ARM Android/Linux Dual "Deskphone" Progress

First off, I wanted to say I posted a few threads about this thing here asking questions about stuff I needed to get it working in the way I'd like and I'd want to thank you because I have made a lot of progress in getting it to be what I'd like it to be. I also don't know if this is the best forum to post this report because it's neither a question nor necessarily a tutorial but rather a summary and description of work already done so far, and especially because this device, while it sure runs Android (very well!) does not fit into any of the categories on this site neatly.
The story so far
This post concerns my experience working with the ITX-3588J, a board released just a few months ago by the Chinese manufacturer Firefly (or T-Chip Intelligent Technology Co. Ltd, based in Zhongshan) that is in the coveted mini-ITX form factor which means it can actually fit into a small-size desktop computer case and indeed has enough compute power to theoretically - and perhaps not so theoretically! - function as an honest desktop system with an ARM processor: namely the - also very new - Rockchip RK3588 system-on-a-chip.
About two months ago, I was looking into acquiring a new kind of computer to replace my somewhat longer on the tooth x86 machine that would be compact, low-power, and easy to transport while also being a fully capable desktop. And I certainly didn't want Apple. I had seen some very small form x86 desktops before, but I also knew there were many boards - like Raspberry Pi - that featured the ARM processor. Not content with the Pi, which is still very weak for this application at least when compared against modern software, I wanted to see if there was something else by now in a similar vein, and when I saw this board I thought it was an amazing option, esp. given I have not yet found a peer. Many ARM single-board devices exist but this is the only one I've found so far that looks to be in a proper desktop form factor and sporting a processor powerful enough to work at that level.
So I got the board, a case, and - noting it had SATA ports - a cheap 250 GB SSD, and put it all together ... and fired it up! And to my surprise, it booted up Android! Which was a real shocker because I generally thought this'd be like another PC board, not having had much experience with this ecosystem beyond phones, so that it would just give the usual "OS not found" stuff. Nope - pre-loaded on the board. Very minimal, very bare-bones though, not even the Google Play and similar essentials required for a usable Android experience. Yet with the little bit I had, I couldn't help but notice it was extremely fluid, responsive, and snappy, moreso than my aging 2018 era x86 box. Moreover, it was very, very interesting (and exciting!) to see Android booted onto a full-size monitor screen like Linux or Microsoft Windows - and actually and surprisingly, to see that it didn't look and feel all that bad!
However, of course, I wanted more. First, I wanted a fully-featured installation of Android. Second, I wanted to run Linux on it - especially given that, a short while later, I found that the board manufacturers were offering a stock Ubuntu 20.04 to be installable to it. Although, in the early stages, I didn't know how to do this at all, and then soon after learned how to reflash the embedded MMC chip to change the OS. And I did so, trying the Ubuntu and finding it also very performant, but not liking either that it was not quite the newest version but also more that it was mutually exclusive with Android - so far.
And that would begin a long - and at many times frustrating, especially given how much information out there is not at all tuned to a device like this being pressed into this application - learning journey toward exploring topics as diverse as how ARM processors and SoCs work under the hood, U-Boot, kernel features, the Firefly-Rockchip developer kit - and having to essentially single-handedly discover many of that kit's ins and outs given there was pretty much no documentation - and more, ultimately leading to where I've got it to now.
What it can do at this point
And that is, right now, I have it sitting here, loaded up with the stock Android 12 and Ubuntu 20.04 - with the former on the eMMC and the latter on the SSD hard drive. On the Android side, Google Play is now loaded and functional, though Google Chrome is not (it crashes with a "Telephony is null" exception for some reason, which seems to suggest for some reason it's trying to act like it's on a phone but isn't). Zoom - an app that I really, really wanted to have (and why I wanted to keep Android around on it) - works and works smoother and cleaner than my 2018 x86 Linux clunker. On the Ubuntu side, though, things are not yet coming - mostly because of seeming inability to use U-Boot to boot from the SSD. I managed to install GRUB, and given that Firefly's generous board SDK provides the full U-Boot source code was able to recompile it with the necessary "bootefi" command enabled which is not present in stock, but nonetheless alas this U-Boot seems to have its SATA support bugged or incomplete, because it would crash immediately upon trying to initialize that subsystem.
Where I'd like to go with it
Obviously, full dual boot of Android and Ubuntu, so getting U-Boot to boot the GRUB resident on the hard drive, is the biggest issue so far, and that means investigating whatever is the problem (or not?) in its SATA subsystem. Getting Google Chrome working on Android is another important step. Moreover - though it would cost extra money that I do not have right now - there's the very interesting possibility, owing to the fact that it has a built in M.2 slot on the board, and alluded to in the title - that the device could be made to act as a cell phone. And finally, the possibility of upgrading to a newer version of Ubuntu (ideally 22.04) - however from what I know so far, it looks like this will have to wait because the stock Linux kernels do not currently support the RK3588 fully - though I'd suggest the Linux kernel developers really should take a look at the SDK that came with this thing because it has lots of code in it including for the kernel, all under GPL.
Final note
One of the most interesting things I've learned from this project, and mentioned earlier, is just how well Android seems to work as a desktop OS. While there have apparently been some attempts to port it to x86, this is perhaps one of the first devices that is desktop-workable and which runs it natively. And one of the things I find that's nice about it is that ironically, because all the apps are designed for small screens, when they are run on a very big screen (and this monitor is not "very big" even by today's monitor standards, being a used and earlier LCD type), they are extremely easy on the eyes and have minimal UI clutter when compared to a typical desktop app on most Linux WMs and on MS Windows.
If you want to know more about the details, or anything else, feel free to ask any questions you might have!

UPDATE:
I believe I may have found an easier way to dual-boot Linux with Android, and that consists of configuring a custom ROM that will put both kernels, and GRUB, on the board's eMMC, while the rootfs for both OSes is placed on the hard disk. Will be seeing how it works.

UPDATE:
I have almost completed the custom ROM! I have now both Android and at least the base system for Ubuntu 20.04 (Kernel 5.10.66) bootable with Android now storing user data on the hard drive; though I'm still running into some hardware initialization issues in the latter that are keeping me from actually installing the desktop system. With regard to the Ubuntu system, there is some interesting issue in that for some reason the provided SDK kernel, which I had to rebuild, seems to build more Android-like because it wants to look in "/vendor" for some things related seemingly to the networking facilities, and it is possible this is preventing me from bringing up wifi, which I need in order to download the rest of the system.
But lots of progress overall - it seems that a full-fledged ARM desktop running simultaneously Android and Ubuntu is within reach to be wrung from this board!

Ignore my request for an update in another post. Seems you like you moving along. I don't need dual boot, just a working Android 12 with GPlay and Chrome. Did you get Chrome to work?

mebalzer said:
Ignore my request for an update in another post. Seems you like you moving along. I don't need dual boot, just a working Android 12 with GPlay and Chrome. Did you get Chrome to work?
Click to expand...
Click to collapse
Thanks. Yeah, I want to say that I have pretty successfully gotten Android 12 working on it for sure, but Ubuntu is proving much more difficult due to graphics support issues, and I'm not sure if it will be possible until RK3588 is supported in the mainline Linux kernel tree which is still something under development. And yes! I got Chrome to work Everything works, actually - it's great as an Android system, though obviously Android is kinda funny to use as a desktop OS. I am wondering if I can't get a "pseudo" Linux using something like Linux Deploy in lieu of running it natively, at least until the kernel development catches up with this new processor.
(FWIW, I'm posting this post from that machine while it is running A12. )
Good to see someone else is interested in it, though. What are you planning on using yours for?

Insofar as getting Android 12 to work w/GApps - it depends on if you want to do it purely on the eMMC or you want to also put user data on an attached hard drive like I did. In either case, the best option, I feel, is to create a custom ROM - I could provide custom ROMs for it for download, but don't know because of Google's licensing conditions around the GApps and have heard of people getting in trouble with Google for distributing custom ROMs for phones that have GApps in them. You basically need to unpack the stock Android image, unpack the "super.img", then load the apps from a package like NikGApps into the "product" partition (NOT "oem" - that was a big mistake), then repack everything and flash to the eMMC again. You will need the board SDK from Firefly for all this as it has the custom ROM-packing and flashing tools.
Alternatively, it is possible to manually install the NikGApps GApps using the Android console - as it's a fully unlocked system, obtaining root access is trivial: just put it into Developer mode and you will find the root access in the "Developer options..." menu under "System".

Shimmy99 said:
Insofar as getting Android 12 to work w/GApps - it depends on if you want to do it purely on the eMMC or you want to also put user data on an attached hard drive like I did. In either case, the best option, I feel, is to create a custom ROM - I could provide custom ROMs for it for download, but don't know because of Google's licensing conditions around the GApps and have heard of people getting in trouble with Google for distributing custom ROMs for phones that have GApps in them. You basically need to unpack the stock Android image, unpack the "super.img", then load the apps from a package like NikGApps into the "product" partition (NOT "oem" - that was a big mistake), then repack everything and flash to the eMMC again. You will need the board SDK from Firefly for all this as it has the custom ROM-packing and flashing tools.
Alternatively, it is possible to manually install the NikGApps GApps using the Android console - as it's a fully unlocked system, obtaining root access is trivial: just put it into Developer mode and you will find the root access in the "Developer options..." menu under "System".
Click to expand...
Click to collapse
Thanks I will keep this in mind. See my reply to you other reply on another post as well.

I would to run gplay as well please send me instruction the nikapps github doesnt say nothing