Any one had same experience? It may be something missing or HTC problem?
warnings in and of itself are not problematic
but does it compile ?
does the example actually run in the emulator ?
see this thread i initiated:
http://forum.xda-developers.com/showthread.php?t=1210770
i can't get the sdk examples to run
i really wonder if anybody can ?
Many warnings in "Official Demos" are unacceptable. I tested and only one demo can complied and worked - it is "PenEventCompatibiilityDemo". The demo solve compatibility issues for Android 2.3 and 3.1. IMHO, they wanted to push all developer to develop Android 3.1 (Honeycomb) but their source mixed with Android 2.3 (Gingerbread).
I think they must upgrade flyer to Honeycomb first, because even I make the apps but I can't test it in actual device....
Included is the PenEventCompatibilty jar library to be packaged with your application should you want to write a low level PenEvent application that supports both Android 3.1 and Android 2.3.
Click to expand...
Click to collapse
sc3sc3 said:
warnings in and of itself are not problematic
but does it compile ?
does the example actually run in the emulator ?
see this thread i initiated:
http://forum.xda-developers.com/showthread.php?t=1210770
i can't get the sdk examples to run
i really wonder if anybody can ?
Click to expand...
Click to collapse
so you are actually saying:
it is a mess
Related
Ok so I have the Full xoom dump. When I try to install any of the apk's in it i get "Their is a problem parsing the package". Is their any way I can get them to install? Would the system dump help port honeycomb to the Archos 101?
I'm pretty sure the problem is you are coming from an entirely different android build. Sort of like trying to open a froyo app on android 1.6.
For half a second I had the same thought as you - "hey, we could have tablet optimized apps on the Archos by using the xoom apks!" but then I realized the problem. I couldn't even begin to know how to get them to work.
Yeah, there is no way to make those work. They have a minimum version of 3.0 in the bindary, so you would need the source code and some major programming to make it work under 2.2 as I am sure they utilize API's specific to Honeycomb.
Moved to general as not android development
I'm NOT EXPERT, I'm ONLY TRING TO HELP and SORRY IF I MADE SOME MISTAKES!
I have some ideas for porting android 3.2 to Folio 100 but I can't do all myself - I need some help.
My first idea is:
To add changes made in android 3.2 system(framework, apps etc.) to our Honeycomb from SDK or Xoom and decompile zlmage inside HC kernel(if that tool existe or find it's kernel source, add changes from android 3.2 kernel and recompile it).
---------------------------------------------------------------------------------------------------------
1. This idea is really hard to realise because kernel(I don't think that tool existe) but it's convinient(we'll finish it in short period with little work).
2. For this idea first we need to add changes from android 3.1 and after that from android 3.2.
3. I NEED YOUR HELP to find WHAT ARE CHANGES and TO DOWNLOAD
THEM for adding them to OUR build(First android 3.1 changes and after android 3.2).
For system that isn't problem but for kernel it is. The most detiled list of changes can
be find at Android SDK site but I think that we can't download them.
4. I think that mblaster know a lot of kernels and compiling it won't be problem for him.
----------------------------------------------------------------------------------------------------------
My second idea is similar to first one:
To add changes made in android 3.2 system(framework, apps etc.) to our Honeycomb from SDK or Xoom and compile android 3.2 tegra kernel from
Android Git or from other sources.
----------------------------------------------------------------------------------------------------------
1. I think that this idea is the best if mblaster help us or some one else that know a lot
of kernels.
2. Google won't relise full source of android 3.2 before pushing up android 4.0 aka
Ice Cream Sandwich to shops.
----------------------------------------------------------------------------------------------------------
I can port system itself(it will be faster if someone make a list of changes) but kernel is
a problem. I don't know much about kernels and because it I post first idea.
If you have new ideas or you don't agree with me or want to help me, please, post here!
EDIT: Android 3.2 might work with our HC kernel.
Sent from my Folio3x using Tapatalk
good idea +1
Thanks.
Sent from my Folio3x using Tapatalk
Not interested?
Sent from my Folio3x using Tapatalk
nice idea..
if u write drivers and kernel change, some other developer can use your work alot.
anyone writing all the drivers for folio will make toshiba happy, as they did not do it..
so if you make all this happen and write the drivers , i am sure folio will once again be a good tablet.
the development is something that takes companies 3-6 months to do, so you will be back in december 2011 or maybe early 2012 with your release?
Can someone compile Tegra 3.2 kernel from here? I tried but without success. I'm porting system now.
I tried to unyaffs FolioComb 3xx v2.0 image bu I got 'Segmentation fault'???
I succefully unyaffsed Android 3.1 and 3.1 SDK images.
I'll try to backup it from my tablet(I have FolioComb on it)
Nice to see someone trying to update folio 100, thanks to you and people in CM7 thead.
I don´t know about compiling so I cant help. But i keep an eye in this post.
Do you know anything about system?
EDIT:Nothing
Hello all!!
I'm new to Android and i'm interested in learning a bit and maybe get involved with it but there are some things that i don't get about android and can't find the answers.
My main question is why Android which is based on Linux is so hard to get updates for all devices at once?
For example we got ICS lately why it's only available for Nexus S and not for all devices that support android?
In pcs if there is a new Ubuntu version every pc can get it no matter the hardware it uses as there are drivers for it.
Is it so hard to have drivers for all the android devices?
Why do we need to wait forever for the X company that makes the phone to build a new kernel?
Is it about the libaries?The drivers?
Say i got a device that is not supported by ICS what would i need to make it supported? I got my libs from 2.3.5 can i toss them to overlay compile and works? If not y not?
Thanks in advance for your answers and sorry if my questions are too noobish, everyone has to start from somewhere
Serafym said:
Hello all!!
I'm new to Android and i'm interested in learning a bit and maybe get involved with it but there are some things that i don't get about android and can't find the answers.
1. My main question is why Android which is based on Linux is so hard to get updates for all devices at once?
2. For example we got ICS lately why it's only available for Nexus S and not for all devices that support android?
- In pcs if there is a new Ubuntu version every pc can get it no matter the hardware it uses as there are drivers for it.
3. Is it so hard to have drivers for all the android devices?
4. Why do we need to wait forever for the X company that makes the phone to build a new kernel?
5. Is it about the libaries?The drivers?
6. Say i got a device that is not supported by ICS what would i need to make it supported? I got my libs from 2.3.5 can i toss them to overlay compile and works? If not y not?
Thanks in advance for your answers and sorry if my questions are too noobish, everyone has to start from somewhere
Click to expand...
Click to collapse
1. Manufacturers don't release updates for all their devices all at once (some not at all).
2. It's ready (most stable so far) for that device (SDK ports; (almost) official update)
- Not true. If you tried to place Ubuntu 12.04 LTS on a PC with a 368 MHz and 32mb ram, it would not run .
3. Yes. Android is on devices from many different manufacturers with many different designs and hardware.
4. See here: http://en.wikipedia.org/wiki/Linux_kernel (to know what it is). Different hardware will require different commands, etc. If the manufacturer doesn't release the kernel source, development cannot be done on that device (properly).
5. Yes and yes (much more too).
6. Create a working port from some other device (with similar hardware) which is supported. Sometimes. Some versions of android have backward compatibility of those files but ICS isn't really backward compatible which is why many ports of ICS (for various devices) don't have a working camera, etc. See the 2nd paragraph here: http://www.cyanogenmod.com/blog/cm9-progress-update.
I would like to start developing for Android and I was curious if its possible to take a custom ROM and import it into the SDK Tools Android Emulator and use it in there?
I see there is something called the ROM kitchen for playing with and familiarizing oneself with the ROM structure and environment, but it seems like my device (the Droid Charge) is not supported.
Maybe I am going about this all wrong to attempt to try to emulate someone's ROM on emulator, I just wanted to start from where I know...my current ROM and work from a known standpoint. I have little java experience.
LockheedX said:
I would like to start developing for Android and I was curious if its possible to take a custom ROM and import it into the SDK Tools Android Emulator and use it in there?
Click to expand...
Click to collapse
For this there's a particular method to install the ROM on the Android Emulator (Google is your friend) I wanted to post the website but I cannot
LockheedX said:
I have little java experience.
Click to expand...
Click to collapse
I'm sorry. To develop, you need to know all the java language otherwise you don't do nothing.
So i've been digging into android development hoping to do some work in porting to an LG Optimus C, and i feel like I'm getting conflicting information from Google:
from source.android.com/source/building-devices.html:
Starting with IceCreamSandwich, the Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Click to expand...
Click to collapse
and from en.wikipedia.org/wiki/Android_version_history
Google's Gabe Cohen stated that Android 4.0 was "theoretically compatible" with any Android 2.3.x device in production at that time.
Click to expand...
Click to collapse
Does this mean that i need ICS specific, proprietary drivers from LG if I want to port it to my Opt C?
or do I simply (./sarcasm.sh) need to learn to write hardware drivers without any idea of specifications?
Thanks!