Hey guys,
We are working on InstaReloader - the development tool that reloads class and resource changes on the fly while developing the Android application.
Its purpose is to minimize the time consumed by the application rebuilds and reinstalls during development.
Right now supported features are:
Adding and reloading regular and inner classes.
Refreshing changes in method bodies, adding and removing methods.
Adding and removing variables, constants.
Reloading changes in layouts, menus and other stuff in res directory.
Here is a short demo of InstaReloader:
Prototype android layouts on the fly demo:
What features are also needed? How many times per day do you rebuild & restart the app? We would like to add some reloading functionality to the popular frameworks and it would be great to hear your feedback
You can download InstaReloader form here: Android hotswap tool
Pre configured Eclipse sample project
Pre configured Android Studio - Gradle sample project
Looks quite awesome, it would save me a lot of time every day.
When do you plan to publish? Will it be opensource?
Archimano said:
Looks quite awesome, it would save me a lot of time every day.
When do you plan to publish? Will it be opensource?
Click to expand...
Click to collapse
It is too early to think about the final, though alpha will be released soon. Right now class reloading is pretty stable but layouts reloading is a pain in the [email protected] Would you like to participate?
The good news:
We improved layout reloading. Now you can add onClickListeners in the Java code for newly added elements and be able to interact with changes almost instanlty!
Planning to add support for Intellij IDEA soon.
and Intellij IDEA is supported now
This app can be used for all android roms? Or it has some requirements and support only some android devices?
Sent from my HTC Desire using xda app-developers app
siavash2death said:
This app can be used for all android roms? Or it has some requirements and support only some android devices?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I think should work almost an all ROMs, depends how significant it changes from the original android's one. So far I've successfully tested class reloading on LG, Samsung, HTC, ASUS devices with original ROMs.
With Layout reloading it's a bit harder because usually this part is "fragmented" so need to create a separate plugin for each brand.
new features demo video is added
Just uploaded another awesome demo video to YouTube! Android layouts can be prototyped on the fly:
http://www.youtube.com/watch?v=ogatWLZA4yQ
We've sent closed beta release to first participants today! It will be available on the XDA soon!
Made the configuration doc. It's quite big so posting link only: http://www.instareloader.com/instalation-configuration/. We will drop some steps in the next version.
ART
I wonder is dynamic class loading possible in ART aka dalvik 2.0 We will check and try to find a solution after receiving the new nexus with the 4.4
InstaReloader 1.5.1 is ready. It contains better logging and bug fixes.
InstaReloader 1.5.1 is now public. Here is a direct download link to this Android code hotswap utility
Implemented cool new feature. InstaReloader can be started from the test-project. Only one entry should be added to the manifest file. Will release 1.6.0 after documentation is ready.
InstaReloader works on KitKat with ART!
InstaReloader 1.6.0 is released!
Download it here: http://www.instareloader.com/download
InstaRelaoder 1.6.1 is released! Now it has support for Android Studio and Gradle.
Check the new demo app: AS-Gradle sample app
Someone have the source of this Tool?
All links are gone.
onolox said:
Someone have the source of this Tool?
All links are gone.
Click to expand...
Click to collapse
I was wondering the same thing. Very quietly this project just disappeared. I wonder if there is anything on github from it?
I think the developer has been contracted by jrebel.
But i'm working in a open source project that does the same thing:
http://forum.xda-developers.com/and...ap-res-src-t3243653/post63713718#post63713718
Related
This thread is for discussion on how to implement omnipatcher for android.
Project site => http://android-omnipatcher.googlecode.com
Project owner is brut.all
An Android app that can automatically download and apply patches/fixes for installed apps. It makes possible to add features to closed source apps without distributing proprietary code.
Planned features (in more or less chronological order):
* apks patching
o res files adding, deleting, replacing - especially useful for themes designers
o applying smali patches
o bsdiff patching
o xml assets patching
o resources.arsc patching
* signing and zipaligning apks after patching
* automatic app version matching
* automatic downloading to SD card some dependencies like smali, baksmali, zipalign, etc.
* patching system apps
o with root permissions
o without root - by changing package name and installing it beside original app
* possibility to generate update.zip file to reinstall some critical apps
* online repository of users fixes
* tool that simplify or maybe fully automate generating of patches
[Reserved for future use]
[Reserved for future use]
Brut.all said:
I though Java has native zip support?
Click to expand...
Click to collapse
Ok, Metamorph is run from console, so it hasn't got access to Java's zip lib. We wouldn't have this problem.
Brut.all said:
Big, but not huge And so far it was evolving very rapidly
Beside of that it will be iterating project. First we need patcher with some of basic features. Minimalistic UI and configuration, libs and patches will be downloaded manually to SD. Then we will add some automation, new features and so on.
Click to expand...
Click to collapse
Yes, I think an iterative project is the best for this
Brut.all said:
I did it already, this was really esay And file is significantly smaller, because smali/baksmali are built with Maven and hence have doubled deps.
I don't understand... You mean (bak)smaling only needed files? It is possible, I checked it
Click to expand...
Click to collapse
I don't know how exactly baksmali work but I have some idea in mind that I have to check... will tell after reasearching some stuff ;-)
Brut.all said:
I though Java has native zip support?
Click to expand...
Click to collapse
Yes, java has built in support (at least on desktop)
It's very interesting!
I made majority of work needed to release the first version of Omnipatcher with basic functionality and then I took to all Android stuff: UI, etc. 2 days passed and I'm almost at the starting point :-/ I got -10 to Android enthusiasm :-/
Android Layouting is not always that easy :-/
I don't have too much time now because I have to finish my pre bachelor thesis (have final design review on Wednesday) but...
How can I help with it?
Hey -- looking this over, as a non-developer/programmer; I am curious: is there any chance that this program could work to apply patches to *.img files? (Specifically, I'm thinking about hot-swapping the kernel.)
IConrad01 said:
Hey -- looking this over, as a non-developer/programmer; I am curious: is there any chance that this program could work to apply patches to *.img files? (Specifically, I'm thinking about hot-swapping the kernel.)
Click to expand...
Click to collapse
Nope, because the intent of this app is decompiling apk's, patch it and compiling again to make the patching app itself legal because no proprietary content will be distributed... the user has to provide the proprietary app to the patching util.
What you want to do could be easily done with just a binary patcher like bsdiff.
rac2030 said:
Android Layouting is not always that easy :-/
I don't have too much time now because I have to finish my pre bachelor thesis (have final design review on Wednesday) but...
How can I help with it?
Click to expand...
Click to collapse
@brut.all If you want, we could open a wave for Brainstorming on the app and I can help you with the Android app stuff your having problems with?
I'm working on it alone because I write much faster in languages like Java, than in English ;-)
I want to get first basic (root only, sorry), but working version, clean up code, release it, update googlecode site a bit (TODOs in form of issues, some usage docs, etc.) and then I will open to community development. In a few days, I think
Nice, MetaMorph pretty much does alot of this, at least in regards to apk and jar patching. MetaMorph is in the market now. the only problem we have had so far is that market apps require them to be resigned when you edit their contents, so that is problematic.
Yep, someone told me about MetaMorph already, so I checked it out, cause I prefer team work than many parallel projects on the same topic.
However I concluded that MetaMorh has different assumptions: it was created as a theme designers tool mainly, so it emphasizes speed and simplicity.
I want to create all-in-one framework with many methods of patching (simple file replacement, bsdiff, smali, XML patching) and installation (in-place replacement, uninstall & install by package manager, generating update.zip), apk version control and possibility to distribute patches without containing proprietary stuff in them. And hence I have chosen Java in contrast to MetaMorph, which is a shell script.
And you have surprised me by info that MM is in the market. You wrote about MM app here, but you didn't write that you finished it... Is it just a front-end to shell script?
too bad this thread's dead
ROM modders/developers!
I'm the developer behind ROM Updater. It's meant to be an universal ROM updater (which means, it doesn't really care if you're on CyanogenMod or you're on the "whitelist"-free of ROM Manager). There is even a PHP script (on the website) which will automatically create incremental updates, cool feature of my app which lets both you and users save a lot of bandwidth. Please consider "adopting" it, it's free ^^
elegos said:
ROM modders/developers!
I'm the developer behind ROM Updater. It's meant to be an universal ROM updater (which means, it doesn't really care if you're on CyanogenMod or you're on the "whitelist"-free of ROM Manager). There is even a PHP script (on the website) which will automatically create incremental updates, cool feature of my app which lets both you and users save a lot of bandwidth. Please consider "adopting" it, it's free ^^
Click to expand...
Click to collapse
Nice work Elegos
Fantastic, consider me a supporter.
I think u have delivered it pretty well
Update: I've released incremental.jar and relative sources. Go to the website and check
New in version 1.8 (from version 1.7):
- Tried to fix a Null exception error, received via Market (thanks for reporting!) (please test)
- Added incremental.php and incremental.jar (plus sources) in the git repository to easily create incremental updates
- Moved common variables in a singleton (SharedData class) and more comments for easier understanding of the code and less variables around
PLEASE NOTE:
You don't have to mess up with the ROM name anymore, the program will check for the ro.build.display.id (MOD name) and ro.build.version.incremental (!!!INTEGER!!! version number), as well as ro.product.model (for future releases, in our case be sure is "Nexus One"). The repository main.json file has a new variable, "model" which is, indeed, the same of ro.product.model. Future versions of the app will make impossible to download updates not for your phone.
DEVELOPERS:
You have no excuses now ! I've talked with some other modders who say, for example, their updates are changing rather all the files, and I say you it's not true. Making some tests I saw that using incremental updates make the update 50~75% smaller, even with MIUI weekly releases. This means "bye bye" to the bandwidth problems, both for hosters and users.
Just added your page as my favorite. Will study and use it later, hehe ,need some time to know about it~~~~
So how do I set up repository for. CM7 nightlies? Do I have to enter it manually?
Sent from my Nexus One using XDA App
I'll give it a go. I have been using ROM Manager and it works very well but I was getting concerned with the bandwidth used for the CM7 nighties.
This does support CM7 nighties right?
Also, what about getting notifications when there is a new build for ClockworkMod Recovery and backup/restore options for ROMs that I keep on my phone?
Wow, as a themer, I would have to say that the idea behind this is amazing. I would love to see it adopted by everyone. I would like to be able to see what exactly has changed between updates, it would save me a lot of time personally. I commend you for your work on this. Woot
@apratomo: you need someone who sets up a CM7 nightly repo. I can't, as it would mean I should support every ROM out there, and my bandwidth is limited (I can host one ROM if you want, not 1000 ). By the way you should edit the build.prop file in order to edit the incremental value and make sure the ROM name is allways the same (display.id).
@pfran42: it supports any ROM you want, this is why I made it
It actually don't check for new recovery images, as it relies on external repositories only, I may create a different application for that though. As of backup/restore, it currently has an option to backup the current ROM wherever you want (see options). When I discover how to restore a nandroid backup via command line, I'll add that feature too.
This is a great idea, however adoption may be slow. Even though its an AWESOME idea, it may be a good idea for you host a popular ROM elegos to get the ball rolling. I'd hate to see this die...
Ok so I have to launch a poll. Problem is that:
1. In the generic Android Development forums (where this really thread should stay) is overcrowed with posts, most of them are just publicity for apps on the market.
2. I'd love to have the attention of all the android people to partecipate to the poll. Of course I MAY create a CM7 nightly repo, but it would mean daily work for me (and a lot of space on my host).
I'm working on a system that should keep a list of repositories automatically updated every time you download a ROM with the app (accepting to send anonymous data). It's ready in the git repository, I'm waiting to push it live 'cause I want to create an interface to grab that data too (a sort of list ordered by phone model).
I think that just for starting I'd love to host a Nexus One Gingerbread AOSP, just like MicroMod777's one (TBH I already have that repo online, but it's frozen at version 20 as MicroMod is focusing on CM 7 custom builds, which I dislike for its too many customizations (both CM itself and MicroMod's)). Alternatively an AOSP 2.3 with no apparent changes (i.e. maybe CM with standard launcher). Any idea?
Sometimes you just have to prove how good your ideas are, because people are lazy... good luck my friend.
Sounds interesting.
I'm going to release a "major" update: all the times a user downloads a ROM and accepted to send anonymous data, the repository, ROM name & version and phone model will be sent to a database, which will return back a list of repositories directly in the settings menu!
I've released version 1.9 and made a Enomther Nexus One repository. Enjoy!
Version 1.9.1
- Fixed an untranslated italian string
- Fixed the import of a repository URL via the repositories list (new line at end of repository)
- Made the application more solid when there are connectivity problems / no internet available (no crash anymore)
awesome work!!
have tagged the link shall go thru it...gr8 job elegos ..!! ..PeacE
Awesome ^-^
IMPORTANT
Virtuous Ten Studio is now the official successor to the M10Tools.
Find it here: http://forum.xda-developers.com/showthread.php?t=1619473
No more support for this tool!
Hi guys !
DiamondBack2010 and me are proud to release new tools for modding Sense !
Since Sense 3.0, people wondered about these m10 files, and there you go !
m10Tools allows you to decompile/edit/recompile these m10 files.
The use of the M10 Editor is recommended !
Remember: THIS IS A BETA !
As pictures speaks better than words, here are some screenshots of what you can do with the tools:
Here screenshots of an upcoping Flyer port for DHD/DZ
And then .. the thing you all are waiting for:
The download link
Hehe no, it's in the second post !
PS: For those who have downloaded alpha tools, please, DON'T USE VERSIONS THAT AREN'T RELEASED BY DiamondBack2010 or me !
Thanks !
Feedback
You can give feedback on M10Tools here:
https://docs.google.com/spreadsheet/viewform?formkey=dHVkbkZSdUZwVVZYLTZnNEFFSnlHelE6MQ
System-Requirements
You need a working .NET 4 Framework installation to run the M10Editor.
m10decoder and m10encoder should run in console-version without anything special.
Reminder
Dear people, please keep in mind, that this software is our own work and that we are spending hours and hours of our freetime to create this essential piece of software.
So, please consider a little donation to keep the development alive.
Every donation is much appreciated, no matter which amount.
If you want to get mentioned as a donator, just write me a PM with you confirmation code or put your xda nick in the donation.
Download-Section:
Current Version:
0.5.26.387
Changelog
0.5.26.387
fixed another decoder bug
added possibility to check whether a file can be safely de/recompiled
do NOT edit files which fail in this test, this could lead to unexpected behaiviour
0.5.25.321
fixed bug with decoding images
fixed a bug where changes were reverted back to normal
0.5.22.313
image-files now de/encodable (!!!)
needs to be activated under "m10-files"
please keep in mind, that the m10-image compression is NOT lossless,
so please do only decode the images if you want to change them.
Otherwise the quality may decrease after a certain amount of decompile/recompile-turns
please DO NOT resize images yet. This WILL screw your apk.
Editing the image is no problem.
this feature is beta at the moment. So please be careful with it.
It is likely you will screw your apk if used without care.
added possibility to work with the program without using ADB & zipalign
added generic ADB-Window
divided property view into "Known Properties" and "Unknown Properties"
got rid of de/encoder.exe, now done via native library (you can use them via commandline nevertheless)
properties are now completely sorted
some other bugs fixed (mainly cosmetic)
0.5.14.208
removed zip.exe/unzip.exe, now done natively
fixed lots of bugs
fixed really bad bug with zipalign (not my fault actually xD zipalign behaves a little strange...)
huge code cleanups
added some usability improvements
0.5.10.170
added possibility to zipalign apk
added possibility to "adb push"
added possibility to reboot phone
added "Quick-Save"-Feature (STRG + S)
added "Quick-Load"-Feature (STRG + L)
added "Quick-Push"-Feature (STRG + P) (keep in mind you have to save the apk first. Otherwise, pushed apk contains no changes)
added "Quick-Save&Push"-Feature (STRG + Q) (first saves current changes and then pushes the apk)
added "Quick-Reboot"-Feature (STRG + R)
added kind of sorting to properties view (known properties first)
added better log output from de/encoder
some gui enhancements
cleaned up editor-view
Clarified errormessage after decompiling m10-less apks
fixed some minor bugs
0.5.2.94a - Fixed dependencies for VC++ 2010
0.5.2.94 - Initial release
reserved for later use.
Time to get my M10 editing on!
Finaly! congrats!!
Amazing job guys. it's our turn to work hard. I still have headaches that I have followed you on irc. French people thank-you.
Sent from my Desire HD using XDA App
Bravo guys! You are the pride and glory of this community!
two thumbs up
Excellent job guys. Very well done
Huray, great job!
Du bon travail, félicitation!
Good job!
Followed you on IRC from the beginning, you have done a great job guys!
Thank you for your hard work !!!
Well done on the tool guys!
Just had a look at a rosie and all I can say is good luck porters!!
Look forward to the rom in op too
Great job guys!
Flemmard said:
Here screenshots of an upcoping Flyer port for DHD/DZ
Click to expand...
Click to collapse
That's all I needed, I can stop holding my breath now
Thank u SO MUCH guys for YOUR HARD WORK!!! Thanks button is not enough U are definitelly "aliens" To understand that 0x00fdg4333 lanugage
Awesome guys!
I wonder is there anything that xda developers cant do on their device!?
i can have another link of multiupload?.. whyt i can't see multiupload.. i get a error and page blank..
i see this address after i copy this link in my address bar:
http://67.210.14.254/after.php?type=www.multiupload.com:
is that no normal...
http://www.multiupload.com/170BHM3M0F
This says Flyer port, will there be a sensation port after?
l.m.prowse said:
This says Flyer port, will there be a sensation port after?
Click to expand...
Click to collapse
Since both have the incorrect resolution, the current thinking is that it makes more sense to port the Flyer ROM than it does the Sensation ROM, being that the former is complete/final.
rmk40 said:
Since both have the incorrect resolution, the current thinking is that it makes more sense to port the Flyer ROM than it does the Sensation ROM, being that the former is complete/final.
Click to expand...
Click to collapse
Makes Sense
Presenting: Fast AAPT - aka FAAPT
Lately Android development has been getting me down. Slow builds all over the place in many of my app projects, and my PC is blazing fast - it shouldn't all be that slow, even if you're running Eclipse!
Working on DSLR Controller has been driving me mad - testing a minor change in the underlying communications library, then building and launching the app - ugh! So I set out to fix this. I had done all the usual tricks, even gave Eclipse loads more memory (helped with regular performance, but not building) but nothing major seemed to change. Then I figured out most of the time building was spent in AAPT. So I synced my AOSP repo (2012.09.26, took a few minutes), tried to get the Windows SDK to build on my Linux box (took several hours) and finally got to actually mucking with the source.
Found the bottleneck (for my long-build-time projects at least, related to XML file compilation) and fixed it (by introducing a simple cache). "DLSR Controller" build time has gone down from 35 seconds minimum, to 2-3 seconds ( >10 times faster). Hell, I can even turn "Build Automatically" back on without getting constant delays!
Note that my build times quoted only apply to incremental internal builds. If your images still need to be "crushed" (optimized), or you're "exporting" an APK (final build for publication), build time will still be significantly longer. However, during normal development and testing (by far most builds if you're making an app in Eclipse) those stages are not performed, and builds should be lightning fast.
"Fixed" is a big word though, right now it's more of a "hack", and it needs some pollish, so the patch can be submitted to AOSP. I don't want to keep it from you for that long, so my first test build is attached - don't use it in production builds..
Patch code has been submitted to:
AOSP - #1 Cancelled, #2 Review in Progress ... superseded by ctate rewrite
AOKP - #1 Merged, #2 Merged
CM - #1 Cancelled, #2 Merged
Attached ZIP includes Linux, Windows and Mac OS X versions.
The files are drop-in replacement, but I would certainly advise you to backup the originals for your production builds! Also, don't forget to chmod/chown on Linux or it won't work.
Enjoy and leave some feedback
Will this help your project build ?
A quick way to spot if this will have effect on your slow build is as follows:
- In Eclipse, set Build output to Verbose under Window -> Preferences -> Android -> Build.
- Clean and build your project.
- If the build pauses on lines in the "(new resource id <filename> from <filename>)" format, you have the problem FAAPT fixes
(of course, you can also run aapt manually if you know how, you'll get the same output)
In a full framework build the optimizations only affect a very small portion of the actions done during the build, so you won't see any spectaculair speed increases there.
Update (#2)
I have updated the patch code to fix problems with Mac OS X compatibility, I've also included a Mac OS X binary in the new zip file.
-----
( v1: 557 )
So that's what's been killing the speed of my eclipse then. It froze so often I had to switch to AIDE on my phone. Hopefully this'll speed it up a little
Sent from my Galaxy Nexus using Tapatalk 2
Awesome work Chainfire, will play around with this in a few
Thanks brother, gonna give it a try right now on Linux
EDIT:
It works. Gave it three tries. Went consistently around 19.1 sec with FAAPT and 33.9 sec with regular AAPT. This is on the Linux version. Good job
Amazing work. Handles large resources like framework-res a lot faster.
wildstang83 said:
Thanks brother, gonna give it a try right now on Linux
EDIT:
It works. Gave it three tries. Went consistently around 19.1 sec with FAAPT and 33.9 sec with regular AAPT. This is on the Linux version. Good job
Click to expand...
Click to collapse
Glad to hear the Linux version also works! Too bad your increase is not as much as mine, but I guess it depends heavily on the amount and type of assets in your project.
Chainfire said:
Glad to hear the Linux version also works! Too bad your increase is not as much as mine, but I guess it depends heavily on the amount and type of assets in your project.
Click to expand...
Click to collapse
I tested on a theme project of mine, so its heavy in img files. Thats probably why. I'm not complaining one bit. Absolutely love it and can't wait to try it out on my other apps
Chainfire said:
Glad to hear the Linux version also works! Too bad your increase is not as much as mine, but I guess it depends heavily on the amount and type of assets in your project.
Click to expand...
Click to collapse
Indeed, tested the Windows version and yes it gives a very good result with a amount of assets, i got 7 time faster than the normal one on Eclipse, too bad we can't use it for production, we need one for Apktool .
wanam said:
Indeed, tested the Windows version and yes it gives a very good result with a amount of assets, i got 7 time faster than the normal one on Eclipse, too bad we can't use it for production, we need one for Apktool .
Click to expand...
Click to collapse
Actually, I was using it with APKTool.
Thanks CF.
Decompiling recompiling now is so fast
apktool and Maps.apk on Linux.
aapt - 29.2s to compile
faapt - 2.2s to compile
Amazing job, Chainfire!
Tested both in linux and winz....
It works great!
Untested time but noticeble faster.
What's the next step after elite rec dev for chainfire?
Thanks for the great work!
Could you post your tweaked source file(s)?
Would like to compile from source for OS X..
On my projects I see anywhere from 5 to 20x speed increase on build. Thank you for this magic.
I don't get how the google android SDK team did not optimize this (I know they done some crazy optimizations for different stuff).
Yeah, could you post your patch?
berdon said:
Yeah, could you post your patch?
Click to expand...
Click to collapse
He did say in the OP. He had to clean it up for AOSP inclusion, so just wait till you see it on Gerrit
Sent from MIUIAndroid Phone.
That is good stuff. It's gonna save me a whole lot of time. The thanks button was just not enough to thank you!
Thanks for the great work Chainfire.
Whoa! Now I will surely stop cursing while waiting for xenoAmp tu build (just not enough time to say "kurwa!")! Thank you!
I'am using ArchLinux x64 as my normal desktop OS. (Yes, I don't have Windows.) and tried it with Eclipse, but it don't work.
Hello,
I have released a very ugly, hacked up dump of my work from July when I attempted to port CyanogenMod 9 to the Nexus Q. It is incomplete, but compiles still, and functional. Developers might find this of use.
There was a large amount of interest in this work when I released a video of 'proof of concept' that went viral in July, before the consumer launch. This work was all created before Google pulled the launch (July), and many weeks before AOSP or OMAP repos had the source for device/vendor.
I call it "Tuna balls" due to the fact it's a raw rip off of the Tuna/Maguro base from CM9, dated July 2012, when I forked and modified it.
The codenames of the branches may be wrong. A lot of the 'bugs' may be easy to fix. Unfortunately, I never came back to this project after July.
As someone who strives for complete, QA process builds, I kept this private for months. I know it's not complete, please understand things don't work flawlessly. No audio (possibly hard to fix) and crashing System UI (probably easy to fix) can ruin your experience, but this can be hacked into shape
* GIT SOURCE *
https://github.com/kornyone/android_device_google_steelhead
https://github.com/kornyone/android_device_tuna_balls
https://github.com/kornyone/vendor_google_steelhead
https://github.com/kornyone/google-kernel-steelhead
Here are my notes/bug list from Github:
"Operation Tuna Balls"
This is a partially complete attempt at porting CyanogenMod 9 (Android 4.0.4) to the Nexus Q.
At the time of original creation (July), there was no other source available. As such, I used the Tuna/Maguro bases to port to the Steelhead, as there were so many common pieces.
This combination worked well for the majority of things. Known bugs never resolved since this project was orphaned in July include:
* No working audio. Mixers fail to load with tuna audio_hw.c. The OMAP "Steelhead" and AOSP "Phantasm" repositiories online have a -very- hacked up version of this file, but intended for Jellybean (as of writing). Also, OMAP has the audio listed as a known issue in their source releases.
* No working NFC. This could be easy to solve, I did not spend much time on it.
* System UI crashes. This should be a simple matter of finding this conflicting Tablet/Phone System UI layouts being requested (should be an overlay setting, likely).
Most everything else works. This includes:
* Bluetooth pair all the things, no hacks needed.
* Wifi works.
* XHDPI resolution works (when System UI doesn't crash).
* HW Acceleration in games work.
* Google Play Market is open for use.
--------------
While I am a maintainer for CyanogenMod, this work is not official in any way. It is incomplete, and I am more or less abandoning it at this point due to a broken Nexus Q and lack of free time. Please hit me up on Freenode (kornyone) for questions, ##nexusq is still open.
Thanks!
Proof of concept (so people don't have to dig this stuff up):
Video concept -- (Very rough) --
Photo gallery on G+ with screenshots -- https://plus.google.com/100539377198423911977/posts/GRxhSLRnNss
very nice mate
Sent from my Xperia T using tapatalk 2
kornyone. I was wondering where you put this. Thanks for the source release, it will come in use. I have a big move coming up but plan to pick up where you left off and maybe get some other devs in on this. Again, thanks for the xmas present!
how hard would this be to run cm 10 on it?
kornyone,
I was able to build and install your cm9!
Of course I have the same issues as you (systemui crashes, no sound) but hey it's something!
Thanks for everything and I hope there is still some progession on this!