This is one of those questions that may or may not be best asked in -
platform so if there's a better place to ask please let me know.
I was asked a question by an OEM that had me scratching my head. What
they want to do is have a single firmware image and on the initial
boot silently install a s
Alan,
Any chance you could try the AndAppStore installer by downloading it
to your PC, adb installing it, then running it on the device? ( The
download URL is http://download.funkyandroid.net/AndAppStore-Installer.apk
)
This should isolate whether the problem is with downloading via a
browser or
;>>> with the details there.
>
> >>>> On Sun, Aug 23, 2009 at 2:22 PM, Alan Cramer wrote:
>
> >>>>> Hi Dianne,
> >>>>> It was the message on screen. Where can I go to find the logs? Is it
> >>>>> the same as a Linu
AndAppStore, it comes up with an Out of Space
> error.
>
> "Software Directory could now be viewed. Free up some space on your phone
> and try again."
>
> Attached is the new log. The Android-x86 has been installed to an ext2
> partition, if that helps.
>
>
I'm looking for feedback from anyone who has a QVGA or WVGA device in the works
on how well the latest release of our client works on those size screens. We've
tested it on the open source repo donut emulator and it seems to work well, but
I'd still be grateful for feedback on how well the UI s
A few people are getting together to port Android to the "old" non-
Android Archos 5 which is based on the a TI OMAP 3 processor, so I was
wondering if anyone has any pointers to get a build environment for
Android up and running so we can avoid any setup snags.
Thanks,
Al.
P.S. If you're inter
Does anyone have a pointer for how to best handle devices without Home, Menu,
and back physical keys?
I'm ideally looking for something which will be on-screen (e.g. in the status
bar).
Al.
--
* Looking for Android Apps? - Try http://andappstore.com/ *
==
Funky Android Limited is register
sily end up stuck without a way to get out.)
>
> It would help to have some more context about what you are trying to
> accomplish.
>
> On Fri, Aug 6, 2010 at 7:24 AM, Al Sutton wrote:
> Does anyone have a pointer for how to best handle devices without Home, Menu,
>
Does anyone know if there is a equivalent for code?
I'm working with some people on a Froyo port to the Archos 5 IT, which,
although it ships with Android, doesn't have the home, menu, and back buttons
so we've had to implement them in the status bar. In order to do this we've
needed some code
a copy of an earlier version of the
> platform's source seems worse.
>
> On Fri, Aug 20, 2010 at 11:43 AM, Jim Ancona wrote:
> On Aug 19, 8:55 am, Al Sutton wrote:
> > Does anyone know if there is a equivalent for code?
>
> AFAIK, the only way to do this is to fork
Limited, it's associates, or it's subsidiaries.
On 21 Aug 2010, at 11:11, Magnus Bäck wrote:
> On Saturday, August 21, 2010 at 09:51 CEST,
> Al Sutton wrote:
>
>> We've ended up with a forked repository at the moment. The main
>> problem with post c
nline and if it gets
> accepted, you can then use a normal resource overlay for config.xml
>
>
>
>
>
> On Sat, Aug 21, 2010 at 5:03 PM, Al Sutton wrote:
> [copied to list]
>
> I'm a fan of the KISS principal, so if I can reduce the number of
> reposit
Have you considered porting Froyo instead? I'm slightly curious as to why
anyone would still be porting Donut (or even Eclair), and I've been working on
Froyo on the ViewPad 10 so I might be able to help.
Al.
==
Funky Android Limited is registered in England & Wales with the company number
Something I'd suggest is a method for one app to address both displays.
This could be as a vendor specific library as opposed to modifications to the
existing framework, but I can see a number of apps being able to make use of
two screens in a nintendo-DS style manner (e.g. city guides with a ma
I was told the straight dpi to density mappings weren't accurate, so a device
with a larger display could get a higher bucked than then SDK documentation
indicated it would due to expected viewing distance being taken into account.
Al.
==
Funky Android Limited is registered in England & Wale
The recommendations depend largely on what your device is intended for. It
might be worth looking at similar devices in order to determine what works well
for your use case.
Al.
==
Funky Android Limited is registered in England & Wales with the company number
6741909.
The views expressed
Please use the android-building group for build questions;
http://groups.google.com/group/android-building
Al.
==
Funky Android Limited is registered in England & Wales with the company number
6741909.
The views expressed in this email are those of the author and not necessarily
those
Build issues should be discussed on
http://groups.google.com/group/android-building
If you search that groups history you should find some helpful tips.
Al.
On 24 Dec 2010, at 05:37, Srinidhi K V wrote:
> Hi All,
>
> Is there a way to build ginger bread on a 32bit machine? Any pointers on thi
Looks like Change-Id If6efd11f5032141dadbfcd0b3215e89b464e5f35 (AOSP commit
aefc28a1b666f3e9b19eb5a8955e70297119f03d) is to blame.
As part of the removal of some performance checking code the conditional which
loaded the page as well as triggering a performance message was removed. The
specif
John,
The android-x86 group have tried switching to chromium, but it appears to have
a dependancy on the v8 engine which in turn requires the ARM platform (see
http://groups.google.com/group/android-x86/msg/f99f379337585667 for details).
Do you have a recommendation for what groups porting to n
Given the recent announcement by Kogan is it worth putting effort into
trying to support QVGA?
From the -developers list it sounds like very few apps will have a
usable UI in QVGA, so maybe it should be dropped as an option?
Al.
Jean-Baptiste Queru wrote:
> That all sounds good, thanks.
>
>
or the
> various densities, which is on the roadmap.
>
> Growing pains are a necessary part of growth, though. Otherwise,
> pushing the reasoning further, we'd all be running Android 1.0 on the
> G1 forever.
>
> JBQ
>
> On Sat, Jan 17, 2009 at 1:23 AM, Al Sutton wrote
Dianne Hackborn wrote:
> On Sat, Jan 17, 2009 at 1:23 AM, Al Sutton <mailto:a...@funkyandroid.com>> wrote:
>
> Given the recent announcement by Kogan is it worth putting effort into
> trying to support QVGA?
>
>
> The work isn't being done for Kogan
expect.
Maybe someone should update the docs and/or remove the skins from the
emulator if they are currently as useless as you say.
Al.
Dianne Hackborn wrote:
> On Sun, Jan 18, 2009 at 2:34 AM, Al Sutton <mailto:a...@funkyandroid.com>> wrote:
>
> > The work isn't bein
24 matches
Mail list logo
