Is it possible to create a special thread about the element tablets from Archos?
Otherwise its difficult to keep track of them.
Amadeus01 said:
Is it possible to create a special thread about the element tablets from Archos?
Otherwise its difficult to keep track of them.
Click to expand...
Click to collapse
I second your request. Archos has introduced a new line of Element tablets in March which do not use the OMAP processor and are in need of their own section. I have a rooting guide that I want to post for the Archos 80 Titanium that doesn't belong with any of the Gen 8, 9, or 10 sections.
+1
Related
http://www.pcmag.com/article2/0,2817,2380756,00.asp
Google on Tuesday announced that the full SDK for Android 3.0 is now available to developers.
"The APIs are final, and you can now develop apps targeting this new platform and publish them to Android Market," Xavier Ducrohet, Android SDK tech lead, wrote in a blog post.
Along with the new platform, Google said it is releasing updates to its SDK Tools (r10) and ADT Plugin for Eclipse (10.0.0).
In the ADT Plugin, Google had added: new palette with categories and rendering previews; more accurate rendering of layouts that will more faithfully reflect how layouts look on devices; selection-sensitive action bars to manipulate View properties; zoom improvements, including fit to view, persistent scale, and keyboard access; and improved support for "merge" layouts and layouts with gesture overlays.
Google also added Traceview integration for easier profiling from ADT and tools for using the Renderscript graphics engine.
More details are available on the Android 3.0 Platform Highlights page.
Google released a preview of the Android 3.0 "Honeycomb" SDK in late January to allow developers to start testing their apps on tablets. Earlier this month, Google also held an event in San Francisco to more formally unveil Honeycomb. It also unveiled the Android Market Web Store, a Web-based version of the Android app store.
The first tablet running Android 3.0 Honeycomb, the Motorola Xoom, hits stores on Thursday.
uff
noooooo now that i need to send my folio to the assistance for the soundboard problem.... please you can wait sometime for build a release 3.0 for the folio??? ahahahahhaha
i confirm that on the android sdk is now accessible the platform 3.0 api 11, my best notice of the 2011 for now!
moved to general as not android development
Yeah! I've just readen this good news too on a news website!! So, does this mean dev's can start working on a 3.0 update for our folio's?
How long to get honeycomb on Folio?
I'm starting the count down right now
Now for serious, 2.2 is fine for me as long compatible apps keep coming to it. It will be needed a few months before We see honeycomb in full glory. I guess that there's a huge pression to get it right this time.
need this!
I realy need this for my Folio!
please...port it!
tomasino.blaha said:
I realy need this for my Folio!
please...port it!
Click to expand...
Click to collapse
theres only one person who can do that at the moment and that is dext3r
What google has released is SDK, software development kit.
This is tools to build Honeycomb application, not Honeycomb itself.
For the Folio to get Honeycomb we will need a rom from a machine similar enough.
No such thing exists (yet).
Yes of course! SDK is only for software development, but is one first step toward a possible mod. Some tegra 2 tablets with similiar hardware specs will be launched this week, I don't think Xoom from motorola is that similiar.
One other option is to have source code and a set of compile options, and them try to build it from scratch.
I guess the main obstacle could be the drivers and hardware support. Must of these will have to be built from ground up and will take a considerable amount of time. I guess that it's feasible but to get a rom as polished as 1.4 we will still have to wait...
It's still good news though !
Thanks for explanation,now i'm so sedder but i believe somebody can do it
but how said "bastospn",this is first step to build new rom
well guys...
but any chance to have honeycomb working on folio?
whats the problem to port it to our deveces?
i got nexus one also and im trying the honeycomb release roight now....
davidebeatrice said:
well guys...
but any chance to have honeycomb working on folio?
whats the problem to port it to our deveces?
i got nexus one also and im trying the honeycomb release roight now....
Click to expand...
Click to collapse
1st, you need a full source from Google, not just a SDK like someone has already pointed out. 2nd, porting is not an easy job...especially when the target device has a bunch of difference hardware components than the reference device. If there's no compatible drivers, sometimes you need to spend days/weeks of writing drivers/ debugging...
What you have on your Nexus one I believe is just an emulator port and thus extremely slow
xitrumch said:
1st, you need a full source from Google, not just a SDK like someone has already pointed out. 2nd, porting is not an easy job...especially when the target device has a bunch of difference hardware components than the reference device. If there's no compatible drivers, sometimes you need to spend days/weeks of writing drivers/ debugging...
What you have on your Nexus one I believe is just an emulator port and thus extremely slow
Click to expand...
Click to collapse
no,
on my n1 ive a full sdk porting really fast and stable, obviously with no phone connection at all...
resolution is the native one, so characters are really small on n1...but folio screen is wider...
look here: http://forum.xda-developers.com/showthread.php?t=961994
so guys...how does it look?
i'm so excited and waiting for it!
is possilbe to do it?
now i installed FolioMod but.that isn't Honeycomb!
Before starting a new thread, I used the search function and looked through the "check these threads before starting a new one" listed threads but didn't find an answer. If this has already been addressed, my apoiogies.
My company uses Excel spreadsheets with custom Visual Basic macros that I have written when we test medical imaging equipment. I would love to use a Tablet for this but Dataviz states "that code type is not supported by handheld platforms, so Documents To Go cannot execute the VB code necessary to use those features. "
Is this an accurate statement? I don't know enough about Android yet to know whether it is correct or if this is perhaps outdated information. The statement was made in June of 2010.
Is Visual Basic totally imcompatible with Android or is there hope that custom macro enabled Excel spreadsheets may work in the semi-near future?
Thank you in advance for any information you give me.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Hello,
I am (finally) getting around to developing my first android app. It's nothing exciting, starting off as a catalogue and some other things.
I have set up the main activity with four tabs within the first tab I have three spinners. The first spinner is meant to let the user select a car manufacturer, the second spinner is meant to show models of that manufacturer and the third spinner shows editions. An example would be:
Manufacturer:
Vauxhall
Model:
Corsa
Edition:
2000+
I was wondering what the easiest way to dynamically change the contents would be? Right now I have one adapter created for each manufacturer with a setOnItemSelectedListener that changes the adapter based on which manufacturer was selected. I don't think this is the most efficient or tidy method though. Also, for a list of 60 odd manufacturers it's a pain to write.
Thanks guys! (and girls)
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Now that framework modifications are no longer working in newer Android versions, a lot of the research I have over the past few months may be of use in maintaining touchpad support.
The Sony example apps use NativeActivity and the event ID from the native side separates the event (since touchscreen events use the same handler). The trick for an app dev getting it to work was just a matter of returning a false motion event to Java and handling the input natively with a second interface set up for touchpad events. This did not change in later versions of Android. The only real change was the key layouts. In later versions of Android, they added a separate key layout for the gamepad instead of appending the default one. That is why the circle button is no longer alt + back. Instead, you have to check the device name for zeus-gamepad and then handle it as the standard back KeyCode.
You can see the code to handle touchpads in a standalone library I put together to add to reicast. This library is built independent of the emulator and allows handling the touchpads through a secondary NativeActivity that has the methods OnNativeMotion and OnNativeKeyPress handling input identified as coming from an Xperia Play.
https://github.com/reicast/reicast-emulator/blob/master/shell/android/jni/src/XperiaPlay.c
The touchpads no longer dispatch a TouchEvent because a TouchEvent was the catch all for touchscreen, touchpad, mouse interaction. When GenericMotionEvent was added, it allowed better classification of touch and move without all the extra checks and conditions.
Trying to find a workaround from the user end instead of getting the developers to use the proper code is why older apps end up broken in newer versions of Android. A lot of the developers have since moved on to other things and left the app with the hack code. Now that it is no longer possible, it may be too late to get an update with the code that works.
GameKeyboard uses the touchpad support methods and acts as a middleman to convert the interaction into something the app can handle using standard methods. A system modification would be something like that merged with something like tasker to detect when the gamepad was opened. Until that modification exists, GameKeyboard and Tasker are a fully-functional alternative.
https://play.google.com/store/apps/details?id=com.locnet.gamekeyboard2&hl=en
Here is the full source on the various supported ways to handle the touchpads in Android:
https://github.com/AbandonedCart/XperiaPlayNative
And for Unity developers, here is an extension to support touchpads from within a game:
https://www.assetstore.unity3d.com/en/#!/content/18853
And here is a demonstration of an Android app with touchpad support from within Unity:
https://www.dropbox.com/s/lw7lebx4piizw4v/SwordArtUnity.apk?dl=0
hi,thank you for starting this thread, it's nice to se that someone is still interested in the xplay, it's still perfect for my use. i do heavy retrogaming with retroarch, plus all the new game, the walking dead,gta sa nova modern combat ecc. i'm on super jelly bean 8 with lupus 13, oc to1.4ghz for gaming with the touchpad fix,and touch pads lag as hell and make any game unplayable..
unfortunately i'm not a developer, but i will be testing of corse if you need..
This isn't really one of the threads where there will be a build or mod to download and then post error reports about. This is one of those threads (like xda used to be flooded with) meant to show people how to do things so they can add them to something or gather all the parts and build something else. It's source, instructions, and good ol' fashioned information. It's a little late, but it's all the stuff that should have been here when the games were being developed to prevent the support situation currently being faced.
Sent from my iPad using Tapatalk
twistedumbrella said:
This isn't really one of the threads where there will be a build or mod to download and then post error reports about. This is one of those threads (like xda used to be flooded with) meant to show people how to do things so they can add them to something or gather all the parts and build something else. It's source, instructions, and good ol' fashioned information. It's a little late, but it's all the stuff that should have been here when the games were being developed to prevent the support situation currently being faced.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Thank you as soon as I get another Xperia play I'll definitely be trying this
Sent from my VS980 4G using XDA Free mobile app
twistedumbrella said:
This isn't really one of the threads where there will be a build or mod to download and then post error reports about. This is one of those threads (like xda used to be flooded with) meant to show people how to do things so they can add them to something or gather all the parts and build something else. It's source, instructions, and good ol' fashioned information. It's a little late, but it's all the stuff that should have been here when the games were being developed to prevent the support situation currently being faced.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
thank you again for your support, by not being a developer i've no idea on how to use your files, not understandable for me. i'm shure it will be useful to developers for eventual new projects
Not sure if this is the right place to post, but I am trying to extend the functionality of my Joying 2gb head unit (5.1.1).
I have made changes to the apk that accepts the key presses and translates them into commands. For example, start the google voice search activity from the steering wheel buttons. I also modified the applications that are cycled through with the 'Source' key.
I have made all the modifications to the smali code and rebuilt the apk (Sofia-1-C9-Server-V1.0.apk). The problem comes when I try to use it the system will not recgonize it. From the error I get, it needs to be signed with the same signature as the other apps that share this user ID 1000 (android.uid.system). It looks like there are 22 other programs using this ID.
Is there anyway to have the HU accept this modified package? I was thinking about re-signing all 22 of the apk files that use this shared id, but thought I would ask to see if anyone has any experience with this issue. Any suggestions?
Thanks
gustden said:
Not sure if this is the right place to post, but I am trying to extend the functionality of my Joying 2gb head unit (5.1.1).
I have made changes to the apk that accepts the key presses and translates them into commands. For example, start the google voice search activity from the steering wheel buttons. I also modified the applications that are cycled through with the 'Source' key.
I have made all the modifications to the smali code and rebuilt the apk (Sofia-1-C9-Server-V1.0.apk). The problem comes when I try to use it the system will not recgonize it. From the error I get, it needs to be signed with the same signature as the other apps that share this user ID 1000 (android.uid.system). It looks like there are 22 other programs using this ID.
Is there anyway to have the HU accept this modified package? I was thinking about re-signing all 22 of the apk files that use this shared id, but thought I would ask to see if anyone has any experience with this issue. Any suggestions?
Thanks
Click to expand...
Click to collapse
No, its not the right section - you have a Joyous Sofia unit and these are not MTCB, C or D units, there is a thread in the Android Auto General forum, I would post in that.
Thanks for the clarification. I wasn't sure but this is about the closest *development* forum I could find anywhere on xda.
I was hoping that someone who has done development with any MCU related android code running at the system level. had run across this issue, and able to provide advice.
gustden said:
Thanks for the clarification. I wasn't sure but this is about the closest *development* forum I could find anywhere on xda.
I was hoping that someone who has done development with any MCU related android code running at the system level. had run across this issue, and able to provide advice.
Click to expand...
Click to collapse
Someone has indeed written an app for it, its called MTCservice, or MTCKeys or something, using Xposed, but it will only work on MTC MCUs and your unit uses an entirely different MCU to MTC MCUs. MTCB and D units got their own forums due to the sheer number of them sold, other units dont I m afraid so your ll have to trawl the General Forum to find threads relevant to your unit. There are some MTCD units with the Sofia chipset, but Joyous chose to go another MCU route with their Sofia devices.