This is AOKP with some extra "flavour"
Kernel:
4.2 roms require a different kernel then 4.1
So you MUST use the correct kernel (and dont forget to switch back
if you go back to a 4.1 rom).
Important:
With 4.2 google added the "user account" feature
That means your "home" folder is NO LONGER /data/media
but /data/media/ (0 by default)
All apps only "see" this folder so if you want to access data
already stored in /data/media you must copy those into that folder
That includes TWRP which will create its backups then also in that folder
If you switch back to a 4.1 rom you must of course to this in
the opposite direction
Downloads:
ROM - goo manager app support is included
Mirror (thanks to Lloir)
Kernel - ALWAYS use kernel in the rom until told otherwise
gapps http://goo.im/gapps/gapps-jb-20130301-signed.zip (20130301)
Different to 4.1 DONT mix and match those to between 4.2 and 4.1 roms
Whats not working:
-... you tell me
Known issues:
-HDMI MHL broken
-SpiritFM broken
-Still pictures are sometimes grey
-phone encryption doesnt work
FAQ:
Q: music lags - how to solve it
A: read this
http://forum.xda-developers.com/showpost.php?p=41311260&postcount=1322
http://forum.xda-developers.com/showpost.php?p=41331878&postcount=1323
http://forum.xda-developers.com/showpost.php?p=41333844&postcount=1324
Again big thanks to the IceColdJelly team
http://forum.xda-developers.com/showthread.php?t=2052610
Using their base for HOX made it much easier to start
maxwen said:
...
Click to expand...
Click to collapse
I have to try this, thank you very much!!!:good:
Downloading!!!!!!!!!
Sent from my HTC One X+ using Tapatalk 2
Just installed it. I will report on how it handles!
I'm not sure what the problem is, but I can't install Swiftkey or Thumb Keyboard. The error message is "couldn't install on usb storage or sd card".
Works great few things i found:
- Google now voice, when you press the mic it crashes.
- The 360 camera mode isn't there.
- No google now button in the unlock circle (?)
- Torch Toggle (widget) does WORK for me.
- Can't install swiftkey just like saibz
cornedor said:
- Can't install swiftkey just like saibz
Click to expand...
Click to collapse
keymonk keyboard works fine
so I would assume this to be an app issue
but anyway - logcat please
cornedor said:
Works great few things i found:
- Google now voice, when you press the mic it crashes.
Click to expand...
Click to collapse
dont see this here - please explain in more detail what you have done
also provide a logcat
maxwen said:
keymonk keyboard works fine
so I would assume this to be an app issue
but anyway - logcat please
Click to expand...
Click to collapse
maxwen said:
dont see this here - please explain in more detail what you have done
also provide a logcat
Click to expand...
Click to collapse
Weird, I have swiftkey working fine here and the mic on Google now as well, it has not crashed.
Seems like it is not only in the search. If I press the mic in the browser it crashes too. Logcat (http://pastebin.com/QBrwHY7y) says that it can't open res/raw/open.wav.
Also a logcat for the installation error: http://pastebin.com/nGNs9p2f
I use the non-free version. Also if I try to install Root Browser (payed) it gives the same error.
In my case the camera is not working at all, as soon as I open it, it crashes with the Gallery error.
Any idea?
Sent from my HTC One X+ using Tapatalk 2
cornedor said:
Seems like it is not only in the search. If I press the mic in the browser it crashes too. Logcat (http://pastebin.com/QBrwHY7y) says that it can't open res/raw/open.wav.
Click to expand...
Click to collapse
weired - have you flashed the right gapps?
the 201212 version?
work without problems for me
maxwen said:
weired - have you flashed the right gapps?
the 201212 version?
work without problems for me
Click to expand...
Click to collapse
I think I did, will retry it.
EDIT: retried, and did not help, flashed gapps-jb-20121212-signed.zip
There are a few apps that I believe are not compatible with the ROM. Could that be? For example,Waze, there is no way to make it work. It does not catch the signal.
Sent from my HTC One X+ using Tapatalk 2
Adolfopacheco said:
There are a few apps that I believe are not compatible with the ROM. Could that be? For example,Waze, there is no way to make it work. It does not catch the signal.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
probably not 4.2.* compatible yet
Spam
Workaround for installation problems
I can confirm:
- No Sphere Cam in camera app
- Video recording doesn't work
- Mic causes crash
- Torch causes crash
- Some apps won't install due to the "Can't install on USB storage or SD card" error.
I figured out a workaround for the installation problem, but it's pretty annoying. The Play Store app is downloading the apps onto your phone, but it's failing to install (I dunno why; I suspect it's a permissions issue). Interesting note - this seems to ONLY affect paid apps. All of my free apps install fine but none of my paid apps do, including when Play Store was restoring from my account.
Anyway, here's how to get those apps installed:
1. First you need to get a hold of the temp file downloaded by Play Store. You can find them in /data/app-private/
2. All of the files have generic names in the form "vmdl-[lotsofnumbers].tmp" so you have to figure out which file corresponds to the app you tried to install. NOTE: you should do this immediately after attempting to install, if you're concerned about accidentally taking the wrong file. How you find that file is up to you, whatever floats your boat, really:
- If you use a file explorer like Total Commander, you can open the directory and eyeball the modification date.
- OR you can open a terminal emulator and find the last modified file with:
Code:
$ su -c 'busybox ls -lt /data/app-private/'
- OR you can use a shell with adb from your computer with:
Code:
$ adb shell busybox ls -lt /data/app-private/
- OR you can logcat WHILE you install, until you see the error message pop up. Then, kill the logcat and check it for some lines similar to:
Code:
I/DefContainer(10169): Created container for smdl2tmp1 at path : /mnt/asec/smdl2tmp1
E/DefContainer(10169): Failed to copy /data/app-private/vmdl-876030916.tmp to /mnt/asec/smdl2tmp1/pkg.apk
W/ActivityManager( 736): No content provider found for permission revoke: file:///data/app-private/vmdl-876030916.tmp
3. Once you've found the file, copy it to your SD card or some directory you'll remember. Then rename it to [something].apk. It doesn't really matter what you rename it as, you should be able to see what app it is from the icon after you rename it with the .apk extension (depending on whether you use a file manager supporting apk icons like Total Commander).
I know it's a bit tedious, but it'll let you install your apps until the bug can be fixed.
maxwen, top work on this mate, it's already stable enough to be my main OS.
here are some logcats for the various crashes:
Installation error: http://pastie.org/pastes/5563789/text
Torch crash: http://pastie.org/pastes/5563793/text
Mic crash: http://pastie.org/pastes/5563795/text
Video recording: http://pastie.org/pastes/5563798/text
For all with install issues for paid apps please try this boot.img
So reflash kernel and try again
EDIT: deleted for now
Not sure if this is actually relevant, but in my case, the data was automatically copied to data/media/0. I didnt have to move anything...
I can confirm the voice & video not working though. Flashlight only works through CM10 app, statusbar toggle and TeslaLED won't work.
Sent from my HTC One X+ using xda app-developers app
s3nsation said:
Not sure if this is actually relevant, but in my case, the data was automatically copied to data/media/0. I didnt have to move anything...
I can confirm the voice & video not working though. Flashlight only works through CM10 app, statusbar toggle and TeslaLED won't work.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
/0 is the new user thing in 4.2 you are user 0
Sent from my HTC One X+ using XDA Premium HD app
Related
This script is not compatible with NookColor software 1.01. I will probably not be updating it. All of my work on Gmail, the Market, GTalk, and this script has been rolled into GabrialDestruir's AutoNooter sdcard image. I recommend using AutoNooter as it provides everything my script does with one less step and fewer requirements (like Linux).
UPDATE 12/15/10 - Version 1.2
ADDITIONS
* Modified Droid X Multitouch Keyboard
* Working Google Talk
UPDATE 12/13/10 - Version 1.1
BUG FIXES
* YouTube would sometimes fail to install because the package manager was not running
* Device might reboot in the middle of the script leaving the process incomplete
I wrote a linux script that will automatically do the following:
* Enable APK installs directly on the device
* Enable Live Wallpapers
* Enable Multitouch for certain apps (Google Maps, etc)
* Download and extract the Google Apps (Market, Gmail, etc) to the proper place on your NC and set permissions
* Download and install Youtube
* Edit build.prop and packages.xml to enable Gmail and Market, and Talk
* Generate an AndroidId for the Market. The Android emulator is no longer required.
* Modify the fingerprint of your device to emulate a Verizon Droid Eris running Android 2.1. This will let you access protected apps in the Market that would be otherwise hidden. (SlingPlayer is one)
Requirements:
* Already nootered and have Superuser
This script is intended automate much of the process after the first two requirements are met. I recommend a complete wipe, followed by nooter and z4root and then my script last.
If you are using a version of the SDK older than r08 (Android 2.3) make sure to open the script in a text editor and follow the instructions at the top.
You will need to connect the NookColor via USB. Be sure to eject both the 4gb internal partition (/media) and the sdcard from your OS before running my script!
From a terminal, cd to your adb directory and run these commands:
wget http://muffinworld.net/android/nookcolor/NookColor-Config
chmod +x NookColor-Config
sudo ./NookColor-Config
Click to expand...
Click to collapse
Press the Home button on your device. If you get the Google Setup Wizard, skip the sign in. Run the YouTube app and hit menu->My Channel. Log in with your Gmail account and press the Home button. Reboot device.
Gmail and the Android Market should work.
Awesome. Thank you!
I'll try before restore mi NC...
Edit:
can anyone help with the terminal stuff?
What terminal application is recomended and what settings are neccesary to input those lines?
thanks!
king conan said:
Awesome. Thank you!
I'll try before restore mi NC...
Edit:
can anyone help with the terminal stuff?
What terminal application is recomended and what settings are neccesary to input those lines?
thanks!
Click to expand...
Click to collapse
Are you running windows or linux? The commands listed here will likely only run under linux... and maybe cygwin?
I'm running windows...
Sent from my Nexus One using Tapatalk
Need a linux partition set up then methinks
idk if Cygwin would work properly with adb, too much stuff to go wrong imo.
I am assuming since it will think it is a Verizon Droid Eris then the NFL app will work also? This will be awesome since I watched part of the eagles game last night on the way home from my hockey game.
Awesome job...
I'm going to work on a Windows version of this script.
ZeroSX said:
Need a linux partition set up then methinks
idk if Cygwin would work properly with adb, too much stuff to go wrong imo.
Click to expand...
Click to collapse
Adb push in cygwin may work if you use nt paths, but I have yet to try. It fails using posix paths for the source.
Sent from my NOOKcolor using XDA app
xboxexpert said:
I'm going to work on a Windows version of this script.
Click to expand...
Click to collapse
Ditto - I'm working on one sans su and root, just sideload (more secure imo)
Sent from my NOOKcolor using XDA app
I modified the script to work on mac os - just remove the .txt extension.
You need to have the path to the sdk in your bash_profile.
Humm, OP I am not seeing the link to your script.
-CC
clockcycle said:
Humm, OP I am not seeing the link to your script.
-CC
Click to expand...
Click to collapse
You pull the script using wget.
Thanks for the effort. Does it work on Win7?
It seemed to work fine other than the live wallpapers bit, but nothing happens when I hit the home button.
Mistar Muffin said:
Gmail and the Android Market should work.
Click to expand...
Click to collapse
Mistar Muffin FTMFW!!!
GMail works! Market works! (Had to reboot once to get past the server unavailable message.)
And I was able to install FlightStats (which I purchased long ago and HIGHLY recommend for anyone who flys at all!)
Thanks a ton!
Patchthehippie said:
It seemed to work fine other than the live wallpapers bit, but nothing happens when I hit the home button.
Click to expand...
Click to collapse
My experience is once the settings.db change is applied for the App Install mod, the home button no longer works to return you to the home screen. I haven't figured out why yet unless it is a permissions issue on the settings.db file
EDIT: This is for the native NC Launcher. If you choose a Launcher replacement I don't think this is an issue.
windows version. Version 5 still buggy. Please hold off until I get a really universally working version
WOW,
thank you. I'll try it ASAP.
Got it! Thanks
Google Maps 5.0 Fix - Two Finger Rotation for Cm 6.1.1 - distinct multitouch for passion + CM 7 nightlies
- [As CM 6.1.1 did not get the latest commits and #cm_nightly_296 failed here´s it]
- [you can use this for CM 7 nightlies till they get it by default ]
Now, there are 3 ways to install this select yours, according your experience! (...as surprisingly still, some got probs to copy/paste...)
1.)
How to:
- in ../system/etc/permissions/..
- exchange "android.hardware.touchscreen.multitouch.xml" with "android.hardware.touchscreen.multitouch.distinct.xml"
- set permissions:
Code:
adb shell chmod 644 /system/etc/permissions/android.hardware.touchscreen.multitouch.distinct.xml
- reboot
2.)
How-to:
1. - connect your device via usb
2. - put "android.hardware.touchscreen.multitouch.distinct.xml" into C:\AndroidSDK\tools\
3. - put "distinct_multitouch.bat" into C:\AndroidSDK\tools\
4. - run (doubleclick) "distinct_multitouch.bat"
5. - wait tills reboots, done
3.)
How-to:
1. - put "distinct-multitouch-signed.zip" on sdcard
2. - flash from recovery (if you have probs, toggle signature verification)
.
..more than 300 downloads here..so I had to do a new thread. So it does not get lost.
Trying it!
Sounds great!
Works* on rooted stock
*As well as the CP2K will let it, at least.
Awesome, works! But I can see why google disabled it by default.. not exactly the smoothest experience.
daisun said:
Awesome, works! But I can see why google disabled it by default.. not exactly the smoothest experience.
Click to expand...
Click to collapse
But Google could of kept the functionality for the N1 by using the trackball for rotation. (I can pan with the screen in the same way the Nx S does and use the trackball for rotation when in the 'perspective' mode).
It is weird that it works on Evil's Desire HD rom.
daisun said:
Awesome, works! But I can see why google disabled it by default.. not exactly the smoothest experience.
Click to expand...
Click to collapse
I think it's something to do with the crazy screen rather than smoothness.
When I installed Maps 5 on my phone I knew that I wouldn't get rotation due to HTC's superb choice of touch screen sensor (sarcasm). But what is weird to is that my girlfriend didn't get rotation either on her captivate. That's not normal is it? I though Samsung hardware was supposed to have great touch support. Or maybe the rotation is just in froyo? She running Eclair still...
Anyhow, I`ll try that fix for sure! Is that gonna work with CM 6.1.1 Stable?
vk2bea said:
But Google could of kept the functionality for the N1 by using the trackball for rotation. (I can pan with the screen in the same way the Nx S does and use the trackball for rotation when in the 'perspective' mode).
Click to expand...
Click to collapse
Can you, or would you like to?
Thanks Rori! It may not be the smoothest, but I am glad that there is an option to use it.
Getting permission error when trying to copy file to Permissions folder.
Any easier way to fix this?
BrumBrum74 said:
Getting permission error when trying to copy file to Permissions folder.
Any easier way to fix this?
Click to expand...
Click to collapse
adb remount
is this for MIUI Rom, too? has anyone tried yet?
Thanks rori. It works! It is not smooth, but at least I have an option to use when needed.
Works for me, great thanks!
Yep, works here.
Used Root explorer, moved over the file to the dir, deleted old file, set permissions.
Well it "works," but its really hard to get it working, and its not as accurate as my friend's evo or incredible
why is this necessary for CM6.1.1 again ?
i dont seem to have a problem with map5.0 rotation / 3d function
Great work! Works fine on my N1 with CM 6.1.1. Thanks!
lsxrx7 said:
why is this necessary for CM6.1.1 again ?
i dont seem to have a problem with map5.0 rotation / 3d function
Click to expand...
Click to collapse
3D? How did you get it work?
Hi,
When I go to gPlay on the Q and click on "Apps" I only get like 150,000 results available for download, only a small fraction of the total apps available. When I go there on my computer browser to try to download an app to the Q it says "This app is not compatible with this device" for 90% of the apps. So, no dice with either method.
I have been sideloading apps and most of them work just fine. So I want to get around this gPlay restriction on the Q so I can just download apps directly from gPlay rather than having to sideload them.
(I am fully aware that the reason why gPlay keeps track of which devices are compatible is to avoid more "broken" apps than necessary, but in the case of the Q their own system appears to be broken itself, so I want to get around it.)
So, I bought the Device Spoofer app for $1.50USD
https://play.google.com/store/apps/details?id=com.scheffsblend.devicespoof&hl=en
which, despite the reviews worked just fine for me on both the Nexus 7 and on Nexus Q. It changes your build.prop file to spoof Google Play into thinking you are a different device of your choosing. Note that, as it says in the instructions, you need to spoof the device using the app, reboot, go to gPlay, *download an app* (any app), and from then on gPlay will register your device as a different one.
That works for me -- I select for example "Galaxy Nexus", go thru the steps above, and voila, gPlay in my computer's browser has now replace "Nexus Q" with "Galaxy Nexus". Pretty cool.
HOWEVER, and I am now getting to the point, this doesn't allow me to download any more apps than I had access to before! It still says "This app is not compatible with this device ["Galaxy Nexus"]" for the same apps that were incompatible before. Browsing gPlay on the Q also doesn't yield any new opportunities for downloading apps.
I think what is happening is that even though the build.prop file is being changed, the Q is still reporting to gPlay that it doesn't have, for instance: GPS, phone functionality, etc etc, long list of items. And that means that any apps that require any one of those functionalities is "not compatible" (despite the fact that sideloading many of them means they work just fine).
So, my point is, does anyone know how to spoof gPlay so that the Q reports to gPlay that it has all of the bells and whistles? (GPS, phone functionality, etc etc)
Thanks
I downloaded all the .xml files from my Q's /system/etc/permissions folder and compared them to those downloaded from my Nexus 7. There are about half the number of files and indeed many things are not supported, no surprise.
Is it safe to just copy all the .xml files from my Nexus7 to my NexusQ? (plus a few .jar files that are linked to in the .xml files).
And perhaps then gPlay will show more apps?
OK sorry for multiple posts, but what the heck I just tried it. And can't see any more apps on gPlay. Tried downloading one that was visible as I thought it might only report its permissions at download-time, but nothing changed after the download. Drawing blanks here.
FIGURED IT OUT!
That's right folks, you can now download any app directly onto the Q! No sideloading, no adb.
Followed these instructions for a different device. Basically I was on the right track but needed to change the .xml's file permissions back to rw-r-r and then clear gPlay cache, reboot, etc, then it worked.
Pasting the steps from this page http://www.slatedroid.com/topic/34849-guide-to-fix-market-to-get-more-apps-compatible/ below, with the small modification that I got my .xml files from my Nexus 7, not from his/her link, and I only loaded the tablet_core_hardware.xml so far (I have not attempted loading on any of the Nexus 7's other .xmls but most of them don't seem useful). Thanks go out to bosondehiggs of slatedroid.com. I have made a note in square brackets at which point my Nexus Q gPlay started suddenly showing all apps.
A. Backup /system/etc/permissions (just take a copy with ES file explorer or root explorer.recommended just in case)
B. copy the xmlfiles files into /system/etc/permissions (android.hardware.location.gps.xml, android.hardware.location.xml, com.android.location.provider.xml, tablet_core_hardware.xml) agree to over write all of them
C. Make sure the file permission are rw-r-r (with ES file explorer, long tap then change properties on each file..to help you out all files in that directory need to be rw-r-r)
D. Go to settings->apps->all and tap Google Play Store
E. Click on Clear data
F. REBOOT tablet
market still not working
Go to settings->apps->all Go to “Google Play Store” again
‘Clear Cache’ if it lets you then ‘Force Stop’ — DO NOT Clear data
back and Go to “Google Services Framework”
‘Clear data’ then ‘Force Stop’
REBOOT your machine. [After rebooting, the Nexus Q worked with gPlay just fine!]
Then after reboot market is still not working.. then go into..
settings->apps->all google play store again open it but this time clear data if it lets you..
thats it exit open market up, login and you should now have full market access....Youtube...Facebook....
Click to expand...
Click to collapse
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
sonikot said:
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
Click to expand...
Click to collapse
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
Click to expand...
Click to collapse
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
davidnhutch said:
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
Click to expand...
Click to collapse
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
sonikot said:
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
Click to expand...
Click to collapse
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
UKROB86 said:
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
Click to expand...
Click to collapse
Sorry, I assume you have already followed the instructions by kornyone here to root and install a launcher:
http://forum.xda-developers.com/showthread.php?p=28484300
There are other ways of doing this too. Some folks have gotten CM9 working on it.
I just made this quick video which shows Trebuchet and the Google Play showing most apps available, near the middle of this video.
What Can You Do with the Nexus Q? : http://youtu.be/6rb4iQDBom0
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Click to expand...
Click to collapse
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
mrjaymillz said:
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
Click to expand...
Click to collapse
Sorry, I mean the keyboard page on my website: davidnhutch.com/nexusq, click on Keyboard > Special Keys.
Basically, the "menu" button on android is mapped to the same keycode as the "menu" button on Windows keyboards, which usually has an icon that looks like a drop-down menu with a pointer hovering over it. (http://en.wikipedia.org/wiki/Menu_key)
You also can do all this from the command line without ES File Explorer, I'm just trying to make it a bit more visual, plus, ES is useful.
I am very interested in what you described you are working on, as I am hoping to try the same thing when I get some time. Please post your results and steps!
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
Click to expand...
Click to collapse
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
xMemphisx said:
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
Click to expand...
Click to collapse
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
mrjaymillz said:
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
Click to expand...
Click to collapse
I didn't get a chance to play with it too much yesterday, I would imagine that if you install a 3rd party keyboard and set it to your primary input method it (might) work. I'm going to have a better chance to really look at the Q tonight here in a few hours, so I'll report back with what I can figure out.
[Edit]
I still have had no time to test this yet. The company I work for is at deadline with new software and we have been working 65+ hour weeks here recently, so my Q has just been sitting there. I'm still anxious to test it, but it might still be a few days before work slows back down and I can really get after it again.
mrjaymillz said:
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Click to expand...
Click to collapse
Hm, weird that two people have said the .xml file is not downloadable -- I tried today and yesterday and it was available both times. Maybe the hosting site was down or something. Anyway it looks like someone else offered the same .xml file at another link so we're all set. I'll leave the .xml file there for a year or so though.
Steps 6-15: Yes, enter everything as quoted. No extra "adb" or "su" or anything is needed, other than what I wrote there. Just follow one step at a time, typing each one and then hitting enter. Shouldn't need a command prompt code entry as it is already, just without the code tags and with extra double-quotation marks. Please let me know if there are any errors though.
As for your last paragraph, it seems there are two issues. 1) Not being able to open gPlay on the launcher. Can you please provide more info? What happens? Does it try to open then crash? Is the gPlay app missing? 2) Can't get a keyboard to show up on the screen. -- You will never have an on-screen keyboard on the Q. You need an external keyboard, plugged into the USB port. If you want mouse + keyboard simultaneously, you need a "unifying mouse and keyboard wireless receiver" -- just search amazon for that -- what it is is a mouse+keyboard with just one USB dongle that serves both.
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
300k said:
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You're right, you technically don't need Trebuchet. It just makes life easier than launching everything (e.g. gPlay) via "adb shell am start ..." commands from your computer.
Regarding Google updating to JB, perfectly possible. Possible that everything will be standard in the next Q hardware release. However the real questions are, why was this functionality not included in the first place? Why was the hardware so very limited by the software? And the bigger question, why was the public release of the first Nexus Q sales indefinitely postponed? Presumably they are coming out with something better than what they showed at IO. Whether it's much better or just marginally better remains to be seen.
The best app/function in the video is being able to use OnLive (3D streamed games) in my opinion. Now, OnLive is expensive and I did have a few problems with the keyboard mapping, the mouse not working while OnLive was playing, etc, but it works and shows the potential for streamed games. The Q doesn't have to be the core device either, presumably a tablet would work too. I just think they should have done the hardware differently and made an Xbox competitor (Xsphere?) instead of a competitor to precisely no-one.
On steps 8 and 9 I get
sh: cannot create /sdcard/permissionsbackup: Is a directory
I don't think that I am typing it in wrong and I have copied and pasted as well just in case...The directory is made correctly... Thanks for your help.
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
I have tried following these directions to temporarily get the Advanced menu back for the CM10.2 nightlies so I can enable dock audio. I keep getting the following error:
Error type 3
Error: Activity class {com.cyanogenmod.device/com.cyanogenmod.device.DeviceSettings} does not exist
It seems to work on other VZW Note 2 Android 4.3 based roms, but I cannot get it to work on our nightlies.
Is there an additional file or entry missing somewhere?
Thank you for any assistance.
Hopper8 said:
Ok, for anyone who is missing the 'Device settings' or 'Advanced Settings' menu (since it was left out of CM10.2. See here for more details.) These settings include mDNIE screen settings and backlight control. I for one use them.
Anyway: To get these settings back, follow these steps.
1. Download attached apk (I took it from Rootbox 4.2.2, but it works just the same on 4.3).
2. Paste it into /system/app, set permissions to rw-r--r-- and reboot.
3. Enter terminal Emulator, and type:
Code:
su [enter]
am start -n com.cyanogenmod.settings.device/.DeviceSettings [enter]
(obviously don't type [enter], press the enter key....)
4. Device Settings will open up, set whatever you desire
Note: to re-open the app, you will have to do it throught Terminal Emulator again. There's no other way of launching it that I could find, even Titanium Backup doesn't recognise it as able to run.
Big thanks to Unisexist6969 and Markox89 for helping figure this out
Edit: most users of a launcher such as nova or similar should be able to add a homescreen shortcut using nova activities shortcut. Personally this doesn't work for me, I'm not sure why. The method above will work regardless of using a different launcher, or if someone (like myself) doesn't have the option to add a shortcut, or if they plain don't want a homescreen shortcut (also like myself).
Click to expand...
Click to collapse
mising said:
I have tried following these directions to temporarily get the Advanced menu back for the CM10.2 nightlies so I can enable dock audio. I keep getting the following error:
Error type 3
Error: Activity class {com.cyanogenmod.device/com.cyanogenmod.device.DeviceSettings} does not exist
It seems to work on other VZW Note 2 Android 4.3 based roms, but I cannot get it to work on our nightlies.
Is there an additional file or entry missing somewhere?
Thank you for any assistance.
Click to expand...
Click to collapse
I'm running the Eclipse ROM (which I believe is based off of CM 10.2), and I had this issue before I restarted the phone. After restarting, it fixed the problem. If this issue persists after restarting your phone, maybe someone else can chime in?
Sorry I couldn't be of more assistance.
SonOfUncleSam said:
I'm running the Eclipse ROM (which I believe is based off of CM 10.2), and I had this issue before I restarted the phone. After restarting, it fixed the problem. If this issue persists after restarting your phone, maybe someone else can chime in?
Sorry I couldn't be of more assistance.
Click to expand...
Click to collapse
Rebooting didn't help, I am back on a TW ROM for the moment since I use my dock everyday, but plan on trying Eclipse or PAC this weekend.
Sbrissen said he is going to put the option back in the settings once they figure out where they want to put it, so I just keep flashing the nightlies every few days to check.
Thank you for your input though.
Over at the Chromecast forum they're building a compatibility list for mirroring with Chromecast. DNA isn't officially supported (yet), but I aim to build a list of ROMS that mirror successfully with the MirrorEnabler app.
TESTED WORKING:
Google Play Edition
Nusense Six
Cyanogen (all music players force close
LiquidSmooth (audio only)
NOT WORKING:
AOKP
Carbon
Paranoid
Dirty Unicorns
Viper
Anyone willing to report on tested and working ROM's please chime in....
Credit goes to r3pwn for his original thread HERE (
r3pwn and I got things rolling on cm-11 so that is confirmed. In the case of DNA ROMs any aosp and cm based should work without issue with v3. It seems the only folks having problems right now is because their ROMs did not compile in r_submix support.
Sent from my HTC6435LVW using XDA Free mobile app
mattgyver83 said:
r3pwn and I got things rolling on cm-11 so that is confirmed. In the case of DNA ROMs any aosp and cm based should work without issue with v3. It seems the only folks having problems right now is because their ROMs did not compile in r_submix support.
Sent from my HTC6435LVW using XDA Free mobile app
Click to expand...
Click to collapse
I noticed the headway made over there with v3 and v4. v4 seems to cast without gps fc but only a black screen. Going to try v3 if i can find it now that the app has been updated.
xlxcrossing said:
I noticed the headway made over there with v3 and v4. v4 seems to cast without gps fc but only a black screen. Going to try v3 if i can find it now that the app has been updated.
Click to expand...
Click to collapse
Here is how mine got working, mind you post these instructions I never had to flash past v2. If you already flashed v3 or greater then you probably don't need to do steps 1 and 2 because Mirror enabler handles that part.
Install and enable mirror enabler v2
execute the following commands in a root terminal
Code:
su
/data/data/com.r3pwn.mirrorenabler/lib/libhackyworkaround.so /data/data/com.google.android.gsf/databases/gservices.db
insert into overrides (name, value) values ('gms:cast:media:use_tdls', 'true');
.exit
exit
Code:
su
/data/data/com.r3pwn.mirrorenabler/lib/libhackyworkaround.so /data/data/com.google.android.gsf/databases/gservices.db
insert into overrides (name, value) values ('gms:cast:remote_display_enabled ', 'true');
.exit
exit
Update /etc/audio_policy.conf and in the global_configuration append to the end of the "attached_input_devices" line
Code:
|AUDIO_DEVICE_IN_REMOTE_SUBMIX
Now, this is something to ask r3pwn but I believe hes pushing a rather generic version of audio_policy.conf and not the device specific policy which means there could be an error related to the generic version. I am not sure if Mirror Enabler is backing up the original audio_policy.conf and putting it back in place after its "disabled" and then uninstalled. What I suggest if you are post v3 is to extract the specific audio_policy.conf from the original ROM and follow step 3 only then reboot. That may be worth attempting to see if it fix.
OK so extracted default audiopolicy, added the submix edit and pushed to system/etc. I am able to receive sound while casting but TV screen is black.
xlxcrossing said:
OK so extracted default audiopolicy, added the submix edit and pushed to system/etc. I am able to receive sound while casting but TV screen is black.
Click to expand...
Click to collapse
Two questions;
What rom are you using?
Did you place the file in /etc/ or /system/etc ? It goes in /etc/
Also make sure the file is owned by root and has 644 perms
I can confirm, NusenseSIX RC 6.4 works as well.
mattgyver83 said:
Two questions;
What rom are you using?
Did you place the file in /etc/ or /system/etc ? It goes in /etc/
Also make sure the file is owned by root and has 644 perms
Click to expand...
Click to collapse
Liquid Smooth. The paths are the same. The permissions are set as they should be. My issue with liquid is no video so tinkering with the audio policy file doesn't seem like a remedy. Ive rebooted Chromecast and the phone to no avail. Can anyone else confirm only audio on LiquidSmooth?
xlxcrossing said:
Liquid Smooth. The paths are the same. The permissions are set as they should be. My issue with liquid is no video so tinkering with the audio policy file doesn't seem like a remedy. Ive rebooted Chromecast and the phone to no avail. Can anyone else confirm only audio on LiquidSmooth?
Click to expand...
Click to collapse
Sorry, I cant directly confirm this for Liquid Smooth but like I said if it can be confirmed by the ROM developer that REMOTE SUBMIX support is compiled into the ROM then using mirror enabler _should_ work. I would suggest contacting the developer to see if this is the case. I can confirm that on my DNA using CM11 m8 snapshot all audio and video works flawless across all applications (including apollo, etc). I would suggest for anyone having issues running that ROM (or possibly others) to attempt the steps I noted earlier to see if using a more "pure" audio_policy.conf. Based on what we learned by testing with my device somehow the audio_policy.conf does in fact have something to do (were not entirely sure what) with ensuring that all the data gets across to the chromecast, he saw a few logcats of users who had audio and no video which were corrected after implementing the "force close fix" that pushes the updated audio_policy.conf. Now while a one size fits all audio_policy.conf is the best method and not causing other issues is hard to say.
Sorry I couldn't be of more help, Good luck!
Edit: I did a few more tests when i got home to make sure I'm not completely full of it and it turns out yeah i am. Apollo is in fact not working for me and does cause a fc then causing mirroring FC's but it appears the force closes settled down after a reboot also plex decided to give me a fit while also while mirroring but otherwise i didn't get any other grief.