The Fingerprint Scanner SDK (originally posted at http://forum.xda-developers.com/showthread.php?t=1202577) for Android has been released by Authentec. Currently there is only one device(Motorola Atrix) with a fingerprint scanner, but if you release your application with support for the fingerprint scanner (once you get the hang of it it is really not hard to use at all) then users of phones with fingerprint scanners will most likely be happier with your application.
Google has stated that Google Wallet will use fingerprints to unlock the payment system, so clearly more capable devices are on the way (source: http://www.qrcodepress.com/google-unveils-safety-measure-for-their-upcoming-mobile-wallet/853399/). Including fingerprint scanner capability in your application will also future-proof it as AuthenTec will have the same framework in place in other phones that will use their fingerprint scanner (Authentec is a leader in biometric security systems for lots of devices).
MotoDEV Article Guide:
http://developer.motorola.com/docstools/library/writing-fingerprint-enabled-apps
Read and Download the (simple) SDK at their site:
http://developers.authentec.com/
Example of SDK Usage (pulled from the SDK)At the time of this writing, it is my understanding that before you release the application you need to have them review it to meet their security specifications... They don't want you using this fingerprint scanner library and making their work look bad. It's a fair deal to me. I'm not sure if this is how they want it though - maybe that is just for Advanced SDK or maybe I'm just wrong (taken from their site) It appears right now that there is a mismatch between the developers and the makers of the authentec site... apparently there is no requirement for using the fingerprint scanner, so develop away!
I have an Atrix and the fingerprint scanner is amazing, once you use it you will never go back to patterns or pins. As such this guide was written by a user of the Atrix - future devices might not use the exact methodology but it should be nearly identical.
I have the Advanced SDK but I have not used any of the advanced functions yet. After using the code (And getting it to finally work) I have found some things that are not documented or are documented incorrectly in the SDK docs and I have come here to post items that will save you great time. If you find others I hope to hear about them so I can add it to the list - I'll even credit you (maybe with a post number so you can score some thanks points!)
The swipe fingerprint screen won't show up - but I'm getting a result (mine was always 14)
AM2 (Authentec fingerprint framework - there are a lot of unsubscribed terms in the documentation so just go with me here) requires Internet Permission (perhaps to verify the key for the advanced SDK, it might not be done locally - without a key advanced SDK functions will not load). If you don't, all uses of the tsm.jar will not work. Not listed at all in documentation
AM2ClientLibraryLoaded() doesn't work with the code they provide!?
You must Instantiate Authentec.AM2ClientLibraryLoaded() - SDK Docs shows as static but it is not used in the example program they give.
It goes into verification but does not show anything and locks up the fingerprint sensor.
Do not change the 'screen' in the examples of sScreen... I thought that was the title of the window that would appear, but apparently those strings are built into it... it would work better as static fields passed as integers. For values look at the next answer.
What can I use for sScreen (viaGfxScreen(string))?
The documentation says nothing of this but these are different types of verification screens. There is fingerprint scanning only and then there is the unlock style one where you also get the PIN. I'm guessing a modifed version of this is how the lock screen works.
"lap-verify" is fingerprint and PIN
"get-app-secret" is fingerprint only - hit and miss right now... will update when I get it perfected
Why does it lock up?
Only 1 app at a time can access the fingerprint scanner. Motoblur seems to access it occasionally and I think that's why it died on the Atrix's Froyo 1.8.3. It seems mostly fixed but as you develop you will most likely lock it up as you debug. Having a wrong sScreen variable will kill your FP scanner. If it locks in your app you will lose the ability to unlock the device with the FP scanner.
Use DDMS to kill com.authentec.TrueSuiteMobile and the lock will work again. This might work on 1.8.3 but I'm not sure it works that way. If the application exits with the home button, it seems to also lock it up. I'm looking into a way to avoid this..
I can't register my application, it's failing with code 6 - (System Error)
I encountered this one myself when using my Api key for com.mgamerzproductions.gibbertalk - I changed it to com.mgamerzproductions.gibbertalk.testing and it no longer worked. They did tell me this in the email that it is only for one package - so make sure you choose wisely, or bribe the people giving out the API keys to give you another one. I wish it was more specific (API_KEY_NOT_AUTHENTIC or something)
I'm still having problems. What can I do?
You can use these tags for debugging in logcat:
AMJNI (AuthenTec Mobile - permissions - server)
TrueMobileSuite (some gfx log info - swipe fingerprint screen)
AndroidRuntime (will tell you crash related things, as debugging for errors will produce too much to read at once)
Any other things would be greatly appreciated for all of use Developers so speak up if you have something I don't have listed and I'll add it.
If you want to use the encrypted storage provided by the framework you'll need to apply for the Advanced SDK. You have to give them a description of your app, and it has to be security related (obviously that's the whole point of the fingerprint scanner and they don't want you to abuse it).
If you like the guide, and you are on MotoDev, I wouldn't mind a kudos in the contest http://community.developer.motorola...print-Enabled-Apps-quot-article-in/td-p/17206
RESERVED
Reserved for OP at a later date
Pictures of my use right now (more later)
Spoke to OP, moved to main Android development, as this would be of more interest to the development community in general, as I'm sure other phones will be using fingerprint scanning (and this sdk) in the near future.
Originally posted in the source thread:
heilpern said:
I tried to post in the linked thread, but as I'm a new XDA poster the system wouldn't allow me to.
The INTERNET permission is required, however there aren't any connections made off of the device. The system uses sockets internally and INET sockets are used rather than UNIX sockets.
> Why does it lock up?
> Only 1 app at a time can access the fingerprint scanner.
This should not cause the system to lock up; it should cause your app to delay briefly and either continue with your request or return to you with an error. If you can duplicate some other result reliably, please share details.
> If someone also can upload and create an eclipse project it would be must easier to import and view their source code they post. I tried but eventually gave up cause of so many problems.
The eclipse projects for these examples are very simple -- with the exception of the .project you have everything you need in the example directories. Worst case is you can create a new Android project and replace its manifest, sources and resources with those provided by the examples. Then point the build path at your tsm.jar and you'll be ready to go.
Click to expand...
Click to collapse
What I meant was that if an app is asking for the fingerprint reader (not the app entirely, but actively asking for the FP reader scan), and motorola does something in the background with the FP scanner (on atrix), it can lock it up. This was heavily apparent on Atrix 1.8.3 but in the new update it seems to have been mostly fixed.
Errors: If you bring up the window with anything but lap-verify or get-app-secret, the window will lock up (and i think fingerprint reader will lock up as well - if you return to the lockscreen you'll see it never finishes initializing it) I can attempt to reproduce this error but I want to finish some development I am doing now.
heilpern said:
com.authentec.TrueSuiteMobile drives the UI, directly or indirectly depending on exactly what's going on (indirectly in the case of the lock screen, for example). If this package is killed it will restart with the next fingerprint operation however it will disrupt any currently active verification attempt (causing the requesting app to receive an error -- probably the USER_CANCELED error).
Click to expand...
Click to collapse
I never really kill it except if it locks up. Haven't tested what it returns (perhaps null)
heilpern said:
Here's something you can do to experiment if you're using StoreCredential -- swipe one of your existing fingers (the index fingers) and you'll store data to that particular finger. Swipe a different finger (multiple times as prompted) and eventually (after three swipes if all goes well) you'll be asked which finger you just enrolled (and your credential will be stored to that finger). This new finger can be used for subsequent Store Credential requests (without the automatic training session) and to release data stored with Get Secret... but only the index fingers can be used to unlock the Atrix.
Click to expand...
Click to collapse
Yeah, in the original thread I had that image posted... It's in the framework but it never was used... I'm not sure if it was there for this purpose or was just cancelled at the end because it was incredibly confusing... I don't get why you would need all those credentials. It's not like your phone will get passed around that much. You swipe new fingers just like you would if you were registering a finger, then you choose the finger... but the accuracy of the 'pick a finger' one is pretty bad.
Would love to see a test apk where we can try this out...
Nothing available right now?
My application works with the FP scanner... its not done yet though.
These are the included APK's that are the code samples they use:
Download tsm-apk-pack.zip from Host-A
Will it support HTC Desire HD? It won't right?
The fingerprint scanner is a hardware device, just like a laptop fingerprint reader. Its not touchscreen, unfortunately.
Trolling from my ATRIX 4G on probably the crappiest main US carrier
Mgamerz said:
I can't register my application, it's failing with code 6 - (System Error)
I encountered this one myself when using my Api key for com.mgamerzproductions.gibbertalk - I changed it to com.mgamerzproductions.gibbertalk.testing and it no longer worked. They did tell me this in the email that it is only for one package - so make sure you choose wisely, or bribe the people giving out the API keys to give you another one. I wish it was more specific (API_KEY_NOT_AUTHENTIC or something)
Click to expand...
Click to collapse
I agree that a more telling error code would be a better option. Error 6 is eAM_STATUS_ACCESS_ERROR but that value can be returned for other problems as well.
Note that if a generic API key is needed, TSM-0E08085A-1210171A-001A7465-632E7473 can be used if you name your package com.authentec.tsmgetsecret. You cannot post that package to the Market however if you want a means of creating a test APK with a neutral package name that package/key combination will work.
Has AuthenTec claimed that package name on the market...?
they probably should or someone might take that package...
Mgamerz said:
Has AuthenTec claimed that package name on the market...?
they probably should or someone might take that package...
Click to expand...
Click to collapse
Yes, it's already claimed in an unpublished but uploaded entry.
Hi . question: is it possible to use fingerprint senzor as wake up function? My button is very very hard to push, this function would be great....
The following is a direct copy paste from somewhere else Enjoy! The wait is over for Alpha!
___________________________________
CyanogenMod for TouchPad
ALPHA 1
"LOWER YOUR EXPECTATIONS" EDITION
* READ THIS COMPLETELY *
Sweet, sweet Internet,
You waited more-or-less patiently for over a month, so at long last, here it is-- an alpha version of CyanogenMod 7.1.0 (an enhanced version of Google's Android 2.3) for the TouchPad.
Understand, this version is definitely an alpha, with all that implies. Those expecting perfection will be sorely disappointed. Many things won't work as well as they will eventually. But you wanted it ASAP, and hopefully, this version should be somewhat useable and gives a sense of progress.
With that said, let's answer some questions, FAQ style.
WHAT KIND OF WARRANTY DOES THIS SOFTWARE COME WITH, IF ANY?
THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Got it? Good.
WHAT IS CYANOGENMOD FOR TOUCHPAD?
CyanogenMod is a community-developed and supported Android distribution for over 60 tablets and phones. This ported version is for the recently discontinued HP TouchPad tablet.
In truth, this "alpha" version is not intended for the general public. Rather, those technically competent hobbyists and developers who are interested in testing an early development version and fully understand the risks of doing so may find interest in it. But there are many bugs and problems in this alpha version. There will be MANY app compatibility issues as well.
WHAT IS THE "ALPHA 1" VERSION AND HOW DO I INSTALL IT?
*** This early version represents the start of a process, not the end, and as such will not be sufficiently awesome, so take any expectations you have and lower them. Now lower them about five feet below that. ***
To be clear, you are encouraged NOT to install this software, as the alpha is only a test version and as stated above, there is no claim that it is fit for any purpose. You may experience issues ranging from the benign to the very serious, including potential data leakage, and/or permanent loss of data, and even the possible "bricking" or permanent disabling of your device. Or worse. It can't be emphasized enough how risky its use may be. Try it entirely at your own risk and with full understanding of the potential for problems and acceptance of any consequences that may result.
That said, if you do understand, acknowlege, and accept these risks and still want to continue, there are installation instructions (and additional exciting caveats and warnings) bundled with ACME Installer.
DOES INSTALLING CYANOGENMOD VOID MY WARRANTY WITH HP?
While HP has expressed moral support for the project ("For those of you in the development community actively working to port Android to the Touchpad, we applaud your efforts"), other HP representatives have also stated that "anyone who loads Android on their Touchpad voids their warranty."
Therefore, it may be prudent to assume that installing (or attempting to install) Android or any other OS besides the stock WebOS would result in the voiding of your manufacturer's warranty. Generally speaking, you must assume any and all risk when experimenting with this software.
SO WHAT WORKS AND WHAT DOESN'T WORK?
Most hardware features of the Tablet should now be supported, although not 100%. There may be issues with sound, camera, wifi, etc. As stated previously, it is definitely an alpha build.
Here is a helpful list of features that are near-completion. Thanks to DarkRedFlame for compiling this.
* Booting into Android
* ADB commands via ADB
* Power, back/home and volume button layout
* Touchscreen support (Multi-touch, 10 fingers)
* GPU Acceleration (2D Acceleration doesn't work, but not a release blocker)
* Dual core processing
* Bluetooth
* Sound
* Accelerometer
* Power Management
* Battery Reporting
* Camera(only video chat, no recording or snapshots)
* Vibration
* Backlight
* LED
* Multiboot (via moboot)
* ClockworkMod Recovery
* Fast Switch Boot
* Fake SD card Mount
* Light Sensor(need to check "Enable Light Decrease" in cyanogenmod settings->display->automatic backlight
* Accessing webOS files from Android and vice versa
* Touchstone Support
* Softkeys
* Wifi
* And much, much more!
As far as what *doesn't* work, that list is probably too long for a FAQ.
* Many apps will have compatibility issues. Many. Including possibly your favorite app.
* Phone-related items (such as the dialer and text messenger) are left in the build. These apps consume minimal energy and can largely be ignored.
* Speaking of energy-- power management has not been the focus of the port thus far. Battery life is not as good as it might be, and you can probably expect improvement in this area over time.
DOES ROM MANAGER WORK?
Not completely. It can't be used to install or update ClockworkMod Recovery for example. Developer Koush will first need to add TouchPad compatibility to Rom Manager.
ONCE THE ALPHA IS INSTALLED, HOW DO I UPDATE FROM THERE?
Once CM is installed, you can use the original ACME installer to install most (but not all) subsequent "update...zip" files you come across.
Or, if you have installed and are familiar with ClockworkMod Recovery, you can also use it to install "update...zip" files as you would for other CyanogenMod devices.
WHAT IS THIS "CLOCKWORKMOD RECOVERY" EXACTLY?
ClockworkMod Recovery, which you can start into from the boot menu, is a special "Recovery" mode-- often used in emergencies when your regular system doesn't load for some reason. Once you have started ClockWorkMod, you are presented with a series of menus and can chose to reset your installation of CyanogenMod to factory settings or load or format individual areas (called "partitions") of your installation.
Additionally, ClockworkMod can be used to back up or restore your entire Cyanogenmod installation to your SD Card. It can also install updates from special "update files" (which are usually named update-some-name.zip).
Since ClockworkMod Recovery is part of CyanogenMod, it is only "aware" of your Cyanogenmod installation. It can not back up or install updates to WebOS or any other operating system.
THE TOUCHPAD DOESN'T HAVE AN SD CARD SLOT. YET CLOCKWORKMOD RECOVERY AND OTHER APPS IN CYANOGENMOD MAY REQUIRE ME TO USE AN SD CARD. WHAT NOW?
If you've used WebOS, you may be familiar with the user-accessible "media" partition that can be mounted to your computer via USB. Well, that "media" partition is now also shared with ClockworkMod Recovery and CyanogenMod, both of whom now identify it as the SD Card (or /sdcard or /mnt/sdcard). So think of this area as a "fake" SD Card, which can be accessed from WebOS, ClockworkMod Recovery, AND CyanogenMod. You can therefore use it as a common area to share files between different operating systems as well as mount it to your PC (again, from different boots). Neat, huh?
I KEEP SEEING REFERENCES TO "MOBOOT". WHAT'S THAT?
MoBoot is a project separate from CyanogenMod, lead by jcsullins and tmzt and based on the "lk" project, which allows the TouchPad to boot into multiple operating systems or recovery images. Technically speaking, it loads just after the "bootie" bootloader that comes with the TouchPad, and displays a menu for the user to select whether they'd like to boot into the stock WebOS or Cyanogenmod, or something else.
You can install the latest version of moboot using ACME Installer. It can NOT yet be installed from ClockworkMod Recovery.
More information about using moboot can be found on IRC (freenode server) in the #moboot channel.
Or, you can learn more about the project at:
http://code.google.com/p/moboot
SO WHERE DO I REPORT BUGS?
The issue list is currently at http://code.google.com/p/cmtouchpad/issues/list
To avoid duplication, do not submit a new issue until you have thoroughly read the existing issues.
OH NOES! I SCREWED EVERYTHING UP! WHAT DO I DO IF I "BRICK" OR SOMEHOW MY TABLET STOPS WORKING?
After you freak out and regret having tried this, you can attempt to hold down the "home" button and the power button together for about 30 seconds.
DIDN'T WORK
Still nothing? Or maybe you have a dreaded triangle-with-an-exclamation-mark on the screen?
Another "emergency" idea (for advanced folks only) is to boot ClockWorkMod Recovery *directly* from your computer via USB cable rather than from the TouchPad's internal storage. To try this, find an "update...zip" file that contains ClockWorkMod. Inside this zip file is a file called something like "uImage.ClockWorkMod". Extract/unzip that file to your computer, then use novacom (which you used with ACME installer) to "inject" ClockworkMod into your TouchPad.
This process should be familiar to you-- very similar in fact to using ACME Installer. It's done by starting the tablet with the up-volume key held down. When you see the USB icon, connect your computer to the TouchPad via USB, then, in a Terminal, navigate on your computer to where the uImage.ClockWorkmod file is, and type:
novacom boot mem:// < uImage.ClockworkMod
Assuming everything went well and ClockworkMod did start up, you may now use CWM to re-install "update...zip" files, restore from backups, format partitions, or reset everything to factory settings. Or use ADB (search online for "ADB" if you're not familiar with this fantastic Android tool) to figure out what's wrong.
I DON'T UNDERSTAND ANY OF WHAT YOU JUST SAID. CAN'T I JUST START OVER?
Sounds like you should give the "WebOS Doctor" a shot. The WebOS Doctor is a program from HP that is used, effectively, to wipe your TouchPad and reinstall the WebOS software so you can begin anew. Get more info here:
http://ws.hpwebos.com/webosdoctor/sorry.htm
The very helpful homebrew site WebOS-Internals.org also has a page that talks about how to use it:
http://www.webos-internals.org/wiki/How_To_Recover
DO I HAVE ANY OTHER OPTIONS FOR HELP?
If none of the above ideas helped, you'll have to go online for assistance.
Browse to http://webchat.freenode.net/ and fill out the web form. Under "Channels", put #cyanogenmod-touchpad and hopefully someone there will have some helpful advice. It is usually not necessary to preface your question with "Can I ask a question?"-- just go ahead and ask.
You may also try one of the many support forums at www.rootzwiki.com or www.xda-developers.com or another Android site.
To a large extent, the Android community will have to help each other as this is an unofficial, buggy release with no corporate, official, or really *any* support. Now you know the reason for all the caveats and warnings.
WHERE IS THE SOURCE CODE FOR THIS RELEASE?
Some of the Android code licensed under the Apache and other Open Source licenses for this alpha test version is not yet available to the general public. However, all GNU Public Licensed software that comprises CyanogenMod, including the kernel, is available at http://www.github.com/cyanogenmod. The kernel for TouchPad used by this project is available at https://github.com/CyanogenMod/hp-kernel-tenderloin .
When appropriate (hopefully sooner rather than later), CyanogenMod will open the code, and patches/fixes can then be submitted by developers via Gerrit at:
http://review.cyanogenmod.com
IS THIS ALPHA OVERCLOCKED?
Overclocking is optional and can be done with an app like SetCPU. Keep in mind it can cause additional instability!
HOW CAN I DONATE TO THIS PROJECT?
To be clear, the key developers of CyanogenMod for TouchPad are not interested in monetary donations for this effort. This is a project motivated by the challenge and satisfaction of working on the port itself, not by financial reward. The developers have previously announced that any "bounty" won for completing this port to TouchPad will be donated to charity.
That said, there are some who have insisted on making some kind of donation to express their support and gratitude. It should therefore be noted that the official CyanogenMod Web site does have a "donation" area in the bottom right-hand corner of the front page.
http://www.cyanogenmod.com/
Also, the CM for TP developers recommend you learn about the Electronic Frontier Foundation ( http://www.eff.org ), which is an organization fighting to preserve and protect the legal rights of the common citizen in this rapidly changing digital age. As large companies and governments try to limit or narrow your rights, the EFF is on the front lines defending the public interest. A contribution to the EFF is also tax-deductible for United States citizens. As supporters, the developers invite you to visit the EFF web site and learn more about their activities and goals.
http://www.eff.org
I AM A "KANGER" WHO WANTS TO TAKE CYANOGENMOD, MODIFY SOME MINOR FEATURE SUCH AS FONTS OR THEMES, THEN OFFER IT UNDER A NEW NAME AND ASK FOR DONATIONS (OR SELL IT) AS IF THIS IS ALL MY WORK. CAN YOU HELP ME?
Absolutely not. One of the concerns about releasing an early alpha is the sad fact that unscrupulous parasites will creep from the shadows of the Internet, slap their name on this port, then try to sell it for an inflated and unwarranted profit. This has been the case for CM on other devices, and we expect, unfortunately, the same thing will likely happen here.
While the GPL and Apache licenses certainly allow CyanogenMod and Android to be sold, and while there may be legitimate occasions where installation or support expenses may warrant or justify charging money, the CM for Touchpad developers are unified in disgust for those who prey upon the uninformed by simply not telling them that a free version of the software is available or by claiming in their advertisements or to the media (who should know better) that they have created or designed the port themselves.
To be clear now-- mods, themes, remixes, and hacks are great- it's the life blood of open source. And there's nothing at all wrong with asking for donations or even charging for something of value you've contributed. But skimming off the free work of others is plain douchy. And not in a good way.
So the developers ask YOU, beloved Internet, to do your part in keeping an eye out for each other's welfare, and enlighten those, including in the media, who might otherwise be taken in by unscrupulous hucksters.
SO WHAT ABOUT YOU? WHO DO YOU WANT TO THANK?
Shout-outs, yeah! Let's start with Hewlett Packard/Palm -- for creating a wonderful tablet, then making it affordable. We are inspired and encouraged by their commitment to Open Source (and do hope this kernel source kerfuffle is resolved quickly). Generally speaking, we really like WebOS and especially the WebOS community, and wanted to made sure that WebOS would continue to be accessible along with CM7, so that users can have the best of all worlds. While thanking HP, it's appropriate to also thank their technical partner Qualcomm, whose Code Aurora project makes CM7 possible not only on the TouchPad, but many other devices as well.
Thanks to Rootzwiki for hosting a forum where people could have meta-conversations about what was appropriate for the forum, as well as meta-meta-conversations and meta-meta-meta conversations... to degrees extending into meta-oblivion. Similarly, thanks to the residents of the freenode IRC channel #cyanogenmod-touchpad for never, ever asking for an ETA. Again, big ups to the WebOS homebrew community for their participation and willingness to offer all kinds of technical insights into how things worked. Particularly we'd like to recognize http://www.webos-internals.org as a source of enlightenment for anyone who's interested in WebOS. If you haven't installed their excellent Preware by now, you have no excuse. Go do it.
A special moment of recognition goes to the members of Team TouchDroid. Wow, that was some drama, huh?
There are countless others who deserve buku credit-- Google, Github, Kernel.org, the wider CyanogenMod and Android community, the thread-that-never-ended on slickdeals.net, those who contributed TouchPads to developers, our teachers, parents, wives, husbands, children, pets, Newton, Tesla, Turing, etc. But this isn't the Grammys, so we'll stop here. The general point is to recognize that all developers stand on the shoulders of giants.
So thanks, everyone, for your help and support so far. And if anyone was missed, sorry.
WHAT HAPPENS WHEN ICE CREAM SANDWICH COMES OUT?
You mean the next version of Android expected from Google sometime in November '11? Well, if the transition from Froyo (2.2) to Gingerbread (2.3) is a model, it may take several months from the release of the Ice Cream Sandwich source code before a viable port to TouchPad is available.
Or not. Ya never know.
WHERE IS THE SOURCE CODE?
Source code can be found at http://www.github.com/cyanogenmod
As of alpha 1 the kernel source is open. The rest of the source will be opened
as soon as some code can be merged into mainline CM7. This expected to happen
very soon.
DOWNLOADS
Initial install will require multiple files to download. Download the installer README first
and be sure you understand the directions.
Note: Please do not link directly to files. Link only to this thread.
Alpha1:
Note: Alpha1 is an extremely rough build. Expect more crashes than you can count. Many many things do not work yet.
Mirror 1:
REAMDE: http://mirror.dal.tdrevolution.net/kmobs/ACMEInstaller README.txt
Installer: http://mirror.dal.tdrevolution.net/kmobs/ACMEInstaller
CM7: http://mirror.dal.tdrevolution.net/kmobs/update-cm-7.1.0-tenderloin-a1-fullofbugs.zip
Clockwork Recovery: http://goo-inside.me/roms/cmtouchpad/alpha1/update-cwm_tenderloin-1012.zip
Mirror 2:
README and Installer: http://goo-inside.me/roms/cmtouchpad...EInstaller.zip
CM7: http://goo-inside.me/roms/cmtouchpad...fullofbugs.zip
Clockwork Recovery http://goo-inside.me/roms/cmtouchpad...rloin-1012.zip
Please keep the conversations civil!
First video: http://www.youtube.com/watch?v=c20yOVKm5UM
Second video: http://youtu.be/fsZXe-_v9uQ
Third video: http://youtu.be/8IVkj_vdY6s
Fourth video: http://www.youtube.com/watch?v=ApfeSj4Ql6Q
Alpha video: http://tinyurl.com/43gwjlo
Show Your Support
To receive notifications regarding updates -> Click to Mark as Installed.
If you like this modification -> Click to Nominate for Modification of the Month.
If you like to thank the author -> Click Here
This modification may not be copied, reproduced or published elsewhere without author's permission.
CM7 Alpha Released 10/13
CM7 Alpha Released [10/13]
CyanogenMod - (A Project that goal is to be able to dual-boot android and webOS)
What currently works:
COMPLETE Wifi (Fixed 10/9)
COMPLETE Camera (Fixed 10/7)
COMPLETE Touchstone Support (Fixed 10/6)
COMPLETE Power Management (Fixed 10/4)
COMPLETE Clockwork Recovery (Fixed 9/30)
COMPLETE Battery Reporting (Fixed 9/29)
COMPLETE Fake SD card Mount (Fixed 9/26)
COMPLETE Vibration (Fixed 9/26)
COMPLETE Bluetooth (Fixed 9/24)
COMPLETE Dual CPU Processor (Fixed 9/23)
COMPLETE Fast Switch Boot (Appears fixed to me Video Update 9/23)
COMPLETE Booting into Android
COMPLETE ADB commands via ADB
COMPLETE Power, back/home and volume button layout
COMPLETE Touchscreen support (Multi-touch, 10 fingers)
COMPLETE GPU Acceleration (50/50 2D Accel support, just like any other gingerbread device out there)
COMPLETE Sound http://www.youtube.com/watch?v=ApfeSj4Ql6Q
COMPLETE Accelerometer http://www.youtube.com/watch?v=8IVkj_vdY6s
COMPLETE Backlight (Confirmed in IRC)
COMPLETE LED (Confirmed in IRC)
COMPLETE Multiboot (Confirmed in IRC)
COMPLETE Light Sensor (Confirmed in IRC)
COMPLETE Accessing webOS files from Android and vice versa
COMPLETE Softkeys
PARTIALLY Compass (Bugs need to be worked out)
What does not currently work:
See issues below
What's currently being worked on:
Gyroscope
Beating Metal Gear Solid 4 under 5 hours.
Bugs and Issues, see below.
What can possibly work:
HDMI through Micro USB (The System-on-a-Chip has the required hardware, have to find which pin #) (webOS 3.0.4 may have HDMI support, and if so we can reverse engineer the process, stay tuned)
GPS (Does not seem possible to implement because hardware seems to be lacking GPS functionality)
Issues:
High Priority Cannot record sound, unless sound is already playing [Accepted]
High Priority Battery Drains while sleeping and active [Accepted]
High Priority Plugging in headphones does not mute external speakers [Accepted]
Medium Priority Apps in market are being filtered [Accepted]
Medium Priority Battery does not shut down device at critical battery level [Reported]
Medium Priority Camera does not take pictures [Accepted]
Low Priority Reboot and Shutdown can take a long time [Accepted]
Low Priority LED light turns off while sleeping [Accepted]
Low Priority Light Sensor does not work automatically, needs to be turned on manually [Accepted]
Low Priority No audio support for BT headsets [Accepted]
Low Priority Add divx codecs for video support [Started]
Low Priority GPS apps crashes because apps assume for valid GPS [Accepted]
Fixed Reboot to Android from webOS app (Fixed 10/12)
Fixed msm_rotator does not work correctly. Screen may rotate for video, but becomes distorted. (Fixed 10/11)
Fixed Sleep Issues (Fixed 10/11)
Fixed Touchscreen has feedback issues (Fixed 10/11)
Fixed Camera fails to save to disk, does not rotate (Fixed 10/11)
Fixed Airplane mode stays on once turned on, happens because the touchpad doesn't have a real radio interface layer. (Fixed 10/10)
Fixed Screen stays blank for 10 second before boot animation appears (Fixed 10/9) (Confirmed in IRC)
Fixed Wifi Issues (Fixed 10/9)
Fixed Sh exceeds the open file limit (Fixed 10/9)
Fixed Sleep Issues for Wifi (Fixed 10/9)
Fixed CPU stays on max frequency (Fixed 10/8)
Fixed Touchscreen turns off when accelerometer is disabled (Fixed 10/7)
Fixed Touchstone works and charges, but no event is raised to show you it's charging (Fixed 10/6)
Fixed Touchscreen events (touches) are ignored after sleep (Fixed 10/5)
Fixed Protect certain partitions in the kernel (Fixed 10/5)
Fixed Root for bluetooth cmattach (Fixed 10/5)
Fixed Touchscreen stays on at all times, even when screen is turned off (Fixed 10/4)
Fixed Touchscreen has issues with pinch gestures (Fixed 10/3)
Fixed No root access (Fixed 9/30)
Way to double post there ace...man these forums are a joke now. Ill stick to rootz from now on.
Nice... installed perfectly anyone pushed Market.apk to theirs yet....?
Scratch that... Installed "gapps gb 20110815 signed.zip"
Been waiting for this.. Thanks to all the devs working on this project.
Any feedback from the early installers?
At work, so I won't be able to try this for a good 10-11 hours.
Missing G-Apps still trying to find an update that will install them, other than that the device is very snappy touchscreen it so much more responsive a few minor bugs (one of which it wont connect to my work's wireless) other than that i am very impressed.
Just Me said:
Any feedback from the early installers?
At work, so I won't be able to try this for a good 10-11 hours.
Click to expand...
Click to collapse
I watched the install vid. but i need to install from a windows computer. anyone with a walkthrough?
jdmtsx said:
I watched the install vid. but i need to install from a windows computer. anyone with a walkthrough?
Click to expand...
Click to collapse
I've written a "somewhat" easier tutorial here
Question at all: is it normal there is no marketplace?
(I'm not that android-guru ^^ )
so two questions to the early addopters: will it delete/modify the custom kernel in webos and will it **** up the partition layout on the touchpad?
mendel129 said:
I've written a "somewhat" easier tutorial here
Question at all: is it normal there is no marketplace?
(I'm not that android-guru ^^ )
Click to expand...
Click to collapse
Thanks for your tutorial!
However step 5 is vague.
could you please elaborate on:
grab the cmd, browse to the place where you’ve downloaded the acmeinstaller file, and type “C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
How do I "browse to the place I've downloaded the acme installer?
Lets say for example it is in: C:\Users\Zak\Desktop\cm7touchpad\ACMEinstaller
How do I browse there in CMD.exe ?
Thanks!
zgroten said:
Thanks for your tutorial!
However step 5 is vague.
could you please elaborate on:
grab the cmd, browse to the place where you’ve downloaded the acmeinstaller file, and type “C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
How do I "browse to the place I've downloaded the acme installer?
Lets say for example it is in: C:\Users\Zak\Desktop\cm7touchpad\ACMEinstaller
How do I browse there in CMD.exe ?
Thanks!
Click to expand...
Click to collapse
cd \Desktop
cd \cm7touchpad
or just cd C:\Users\Zak\Desktop\cm7touchpad\
(you can autocomplete with tab )
mendel129 said:
cd \Desktop
cd \cm7touchpad
or just cd C:\Users\Zak\Desktop\cm7touchpad\
(you can autocomplete with tab )
Click to expand...
Click to collapse
Thanks!!
Sorry for bugging you, one more question...
I am getting "Access is denied" after typing:
C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
zgroten said:
Thanks!!
Sorry for bugging you, one more question...
I am getting "Access is denied" after typing:
C:\Program Files\Palm, Inc\novacom” boot mem:// < ACMEInstaller
Click to expand...
Click to collapse
1) are you running cmd in elevated permissions?
2) do you have novacom installed in the first place?
mendel129 said:
1) are you running cmd in elevated permissions?
2) do you have novacom installed in the first place?
Click to expand...
Click to collapse
Yes, and Yes.
It shows up in my programs list as "Novacomd"
Well mine installed ok but it seems to wipe your WebOS install (at least it did for me) so I had to restore my palm profile!
Not had much time to play with android yet but im impressed so far!
Loving this! xD
Sent from my HP Touchpad using Tapatalk
Can't imagine why it wasn't released here.
/sarcasm
My problem is actually that I cannot get it to mount.
mendel129 said:
Question at all: is it normal there is no marketplace?
(I'm not that android-guru ^^ )
Click to expand...
Click to collapse
download the google apps package from here: http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps
put in on your touchpad
boot clockwork recovery using novacom (same as for installing cm7, but instead of using "ACMEInstaller" use "uImage.ClockworkMod", go to install, install from zip on sd card, choose the google apps package
done =)
and you have a functional marketplace
Hi everyone. Im one of the developers of SwitchMe, and app that allows multiple secure logins into separate installations of android on a single device. The pr is after the break.
I really need a few people to check into some issues people on the A500 have been experiencing. There are some warnings involved:
- testers must perform a full nandroid backup before using the app, it is not our responsibility if you start getting boot loops
- if you report results or bugs, please use the "Write to us" function in the app whenever possible, and always describe the issue in the header of the logs you send
- if you post here, be sure to include your device type and rom
- if you have apps installed on sd, be sure to mention that as well
--------------------------------------------------------------------
SwitchMe is a unique application for root users that allows you to log in and out of multiple installations of Android just as you would on a desktop computer.
The technology behind SwitchMe saves all of your applications and data, protects it and stores it as a file in memory. You can then log out of an
account and log into a fresh installation of Android or another account with its own unique content.
You may create as many profiles as the memory is capable of holding. Some of these may require very little free memory because they contain few apps,
others will be larger as they contain many applications and lots of cache and data.
Why is this functionality useful?
Privacy - the most obvious benefit is that you can securely share one device among multiple users, which gives you privacy and peace of mind.
Testing - if you are a developer, you can use profiles as clean sandboxes to test your applications and their interaction with the system.
Gaming – with multiple installations of Android on a single device, you can now play online MMOs as different characters.
Speed - the games your kids play slow down your tablet, but with SwitchMe you can easily create profiles without games or instant messengers.
Battery life - when the battery is low but there are important emails or documents to edit later, switch to a profile which only contains these essentials.
These of course are only suggestions - there are plenty of other uses for the functionality SwitchMe offers.
Market link:
https://market.android.com/details?id=fahrbot.apps.switchme
The Lite version allows the creation of two profiles, enough to test on.
Screens:
So far so good. I'm using ezterry's simple stock rom that has root. I've been able to switch between profiles without any problems. The only thing that I've noticed that was strange happened to the app Full Screen Launcher. After the first switch from my original profile to my new profile and then back to original. My folders, shortcuts widgets and anything, other than what was there as default when the app was first launched on the desktop disappeared. This only happened on the first switch. Once I added the shortcuts and stuff back and then tried again the were as they should be. So that's really not an issue. Gameloft games that are moved to sd card via GL to SD from the Market seem to work as well.
Is there anything specific that you want checked? I'd give a few things a shot if you have something in mind. So far, I can't find anything wrong with my setup. And the app is pretty neat. Kinda cool having a fresh tablet to play with. It's even neater that I can just switch back to my profile with all of my junk.
Just what i've been looking for, will test tonight
Device Iconia A500 16gb
ROM Thor's ics v96
have internal and external 32gb swapped
Everything working as should including fast switching.
Takes less than minute to switch.
was also able to clone without issue.
Key has been purchased.
Thanks for this!
Sent from my SGH-T959V using Tapatalk
Thank you! Please rate the app - just press the little star button at the top of the main interface.
Good ratings help us invest more in apps and give users with similar hardware peace of mind.
Thanks in advance!
Why only for the a500?
If you wish for some 501 testing, let me know.
MD
Moscow Desire said:
Why only for the a500?
If you wish for some 501 testing, let me know.
MD
Click to expand...
Click to collapse
Sure, why not.
Are you a programmer? We are hiring in moscow at the moment!
Excellent app. Tested yesterday on honeylicious and purchased key. Keep up the good work
Not found any issues as yet.
Thanks. If you like it, please rate it on the market, that helps a lot.
Any issues to report or is everything working flawlessly as usual?
SwitchMe 1.2 has been rolled out and now includes a lockscreen replacement:
1.2
Added lock screen for logging in and out
More stable Fast switch implementation
Reworked UI colors
Now, its very important that we get some feedback on how this big new feature works, so please read up on it in the help and post your thoughts!
1.2.2 - HOTFIX 2
Reworked widget on qHD+ displays
Fixed widget text on HC and ICS
Fast switch improved on older devices
Hi guys! I would really appreciate some feedback regarding the new lockscreen!
Anything at all?
Its working perfectly here! Thank for this awesome app!
it's working great for me also. sometimes keyboard will lag when needing to put in password from lock screen. once I get my alarmed dismissed in the morning, I'm really awake;-) Also, is there a way to make the key work for all users? I'm unable to access the lock screen settings from other user logins.
edit, fixed the key issue by moving the key apk from /data/apps to /system/apps
doublepost
Somairotevoli said:
it's working great for me also. sometimes keyboard will lag when needing to put in password from lock screen. once I get my alarmed dismissed in the morning, I'm really awake;-) Also, is there a way to make the key work for all users? I'm unable to access the lock screen settings from other user logins.
edit, fixed the key issue by moving the key apk from /data/apps to /system/apps
Click to expand...
Click to collapse
It wont work forever! Not unless you have the same account in the two profiles. In any case, we are working on it, so the switch screen will be accessible to all profiles with one key!
hi,
I've a Liberty Tab, rooted and running Acer Stock Rooted ROM.
I'm installed your app soon after root and it works flawlessly.
How can I setup the replacement lockscreen?
Hello! There will be a new build which gives lockscreen access to everyone very soon!
Any comments on the new switch screen?