Related
Hello XDA,
Well, after about 3 months of hacking away, the newest version of DroidCam is available. More specifically, a new app: DroidCamX. What's Droidcam? {Mod edit: Link removed}
Now, I'm positive there are probably a few bugs hiding - I'm working with a Nexus One and phone specific issues tend to always come up.
Also give the new PC Client(s) a go and see if you have any issues
DroidCamX Features:
- Various video formats - capable of high-resolutions. (640x480 is my phone's max, I also added 800x600 and 1280x720 - but never tested these)
- Audio support (experimental)
- Connect via ADB (over USB)
- "IP Camera" feature - I created a small Java applet to act as a mini video-only client
- Front Camera support for Android 2.3 - Nexus S users: please check this out and let me know if it works! I have no clue..
- and more..
Cheers!
You may consider trying the free version first to make sure everything works.
Click to expand...
Click to collapse
from {Mod edit: Link removed}
but I can't see any free version (unless you mean the old droidcam?) and your website seems to be down
So its using ur phone as a webcam for ur computer, and not having skype with video on phone?
etched with my mT4g
XlAfbk said:
from ...
but I can't see any free version (unless you mean the old droidcam?) and your website seems to be down
Click to expand...
Click to collapse
Yea, the free version still goes under the same name/package. It's been updated tough (Client + Server roles have been switched)
{Mod edit: Link removed}
The website is on the west coast - it was night here there might have been some maintenance. I don't know tbh. All good now
So its using ur phone as a webcam for ur computer, and not having skype with video on phone?
Click to expand...
Click to collapse
The computer client I wrote registers as a webcam, so you get to stream your Phone's camera to the computer and into Skype/etc.
You basically get an actual webcam (like if you bought one for $20+) + it's WiFi so you can walk around
for some silly reason
the paid version can be found on the market on my phone
however the free version it says "could not be found", and it will not come up when searched
{Mod edit: Link removed}
anyone have the apk file?
I've been trying this app but I get no video with droidcamX after installing the client droidcam 3.1 in win7 I can the droidcam audio driver is listed and I can stream audio. However there is no video, no video driver which means droidcam is not detected as a webcam in any chat programs.
There is no video driver, it's just a DLL. You should be able to pick it up in the video/webcam settings of your chat applications.
Just a month ago I tried every single app like this, including the previous version of this one, because I wanted to get a live stream setup from my Droid X for my sister's wedding, come this summer. They all sucked something fierce.
This new version, which I ended up buying, is a huge step up. Works very well, though I couldn't get ADB mode working. This works surprisingly well, and it has NO competition on the market, lol. (the other 'supposed' competition is like McDonald's competing against a ground Kobe filet mignon burger)
Good job, dude. Keep up the improvements! You've already got my money as of last night.
P.S., a hack to get around the x64 audio driver signature issue would be nice, (without having to permanently disable it in Windows or boot into it via F8 every time) and also a quicker & easier way to change the resolution on the Windows app would be great. Just future suggestions!
Just purchased the Droidcam software. Works just like you said. I am using it on the new HTC Thunderbolt. The Thunderbolt has a front cam but running 2.21 OS. Rear cam works great, but front cam ignores your front cam option. Could you add support for the Thunderbolt frontcam? Thanks.
Found some SDK discussion about using frontcam under Froyo 2.1
Would be great just to have a script to make frontcam as main cam so Droidcam would work. Here is the link.
HTML:
http://stackoverflow.com/questions/2...droid-platform
Thanks guys
@Roland: There are ways to permanently disable driver signing (which may or may not be a good thing. You have to be careful with what you install). Just Google around .. lot's of info, even video instructions. PS. I'm gonna quote your McDonalds remark on the market
@houseboatwayne: Yep, as mentioned I used the new Front Cam SDK that was released with Gingerbread (2.3) - since this is the only method to work across all devices. Before that you had to use special libraries from Sprint and whatnot to get it working specifically for Sprint devices. I'm sure there were hacks to get it working in general but I didn't look into it. The link you posted seems to be cut off
i can't make it work over usb... do you have a tutorial? i can't get my HD2 to get an IP over usb... thanks
New version is crashing on my phone. Can i get the previous version? I had the paid version. New free version does not crash but lacks zoom. New paid version is crashing, previous version worked.
not working on my phone and pc I use usb connection try different port but not working
@dev47
How can we uninstall Windows client completely? If I simply uninstall from control panel, the remnants are still there. Zoom application shows more than three camera drivers, audio sources as droidcam client 1-2-3 etc. Why doesn't the uninstaller remove them completely?
It would be nice if it didn't break Audacity on Windows.
@dev47 Thread closed! Please advise the moderators team to re-open the thread when ready to provide a free version to the XDA community in accordance with rule no. 11 of the XDA Forum Rules.
Regards
Oswald Boelcke
Senior Moderator
The adaption of the released VegaComb / honeycomb 3.0 for our tegra2 brothers (advent vega and Adam) and is getting to a state where its usable and the latest release for Vega is working quite well on Folio100 as well. with modifications of course...
What is Honeycomb 3.0?
Its the operating system upgrade that Toshiba will never delivet to our folio100, since its no longer supported by toshiba.. But the community gives you what the company did not! At least to a point where its possible within reasonable effort.. as not all source is available for rewriting drivers.
Credits for the intensive work done on this honeycomb 3.0 , is primarily done by NotionInk Adam and Advent Vega
developers , which are: MrGuy , newbe5 , corvus , HomerSp
I have just made the required changes to make it run on our Folio100.
Download Folio3x v0.3a here
Wipe should not be required for existing 0.1 - 0.3 users. if nothing seems unstable.
but NEW USERS always do a factory reset, or even "fastboot -w" to fix possible apps problems.
v0.3a
- rebuild from 0.2 and adding changes from 0.3.
- fixed 3G usb dongle problem
- usb share to pc fix fix
- apns conf now ok, apn location should be updated automatically.
- core.android FC fix
- dalvikcache update
- compatibility mode disabled by default (FolioWidget settings is fullscreen now)
- FakeGPS included (enable mock locations in Settings ->development) , so you use compass apps
our tablet has no real GPS, but the device think so but does not find it and it crash apps requesting gps.
- Sensors working.. (Thanks to newbe5 for the help)
- Included the new graphics drivers (quadrant= 2D=130/3D=820)
- adhoc support (use folio hc widget to enable, reboot after enabling)
- PolarisOffice fix
- included a fixed FolioWidget, for disabling folio100 softbuttons.
to use foliowidget:
- add widget to desktop.
- click widget once.
- in menu enable Softbuttons once, to disable the softbuttons below the power led (normally)
PATCHES
install patches below like you would install a full rom in recovery (Not ClockWorkMod), except this zip needs renaming directly to update.zip .
do NOT unpack it first.
any version: Download sensor patch attached to this post, if you want to continue with earlier version and not upgrade.. this does not require a wipe at all, its one single file added to your system.
0.3a : Download bootanimation and copy to /system/media folder read more here , this will fix the "remember language and timezone issue"
0.3a : Download bootanimation as patch, for those not able to copy file, here
0.3a : Download rollback to regular kernel here
0.3a : Download Overclockable kernel upto 1.5Ghz here
OC Kernel might not enable 3G automatically so go into mobile network and disable/enable if it happens.
ALWAYS READ ME BEFORE POSTING Questions - FAQ and Status on folio100 edition of VegaComb.
- Flash works with Opera 11.10 release.
-
- Before you report any issues, you might check that other ports of this Honeycomb (which all pre-3.0 tablets use) already confirms not fixed.
Do check VegaComb xda thread
-
- SOD problem: Others have used the OC kernel, and set the minimum speed to 456, and it solved the problem. But yes, you need the OC kernel + CPU Master as example.
-
- If you got problems running Any Angry birds game or other applications as example, you might need to use "fastboot -w " to erase userdata & cache . To enter fastboot mode, at bootup press 3 times power and then VOL+ .
-
- USB PORT: stick & 3G dongle must be inserted at bootup if needed. Kernel do not at this point automatically register usb port changes if inserted after boot is complete.
-
- At setup wizard, wifi scanning, reboot once, and setup wizard finds the networks at next boot
-
- Apps fail to start if running from sdcard.
-
- Bluetooth send/receive files is not working
-
- Volume control in Settings, still crash when tried opened..
-
- FakeGPS app is needed to start, if you open compass apps, that also read GPS information.
-
- language and timezone in full image, needs to have a bootanimation, then it remember language and timezone after reboot. See the PATCHES for the bootanimation.zip (copy zip manually to /system/media )
-
- MUSIC: music must be copied to /sdcard/music , and player finds it.
-
- Youtube - not all videos can be played, due to incompatibiliy issue with driver and codecs used. (but many do work)
I will do what is possible to bring it to a better state, but i cannot promise anything and maybe patches from vega/adam might actually work on our folio100 depending on what they change. (if its a patch)
You're the BEST!!!
Dexter_nlb said:
If i'm happy with it, ill post a release of it during tonight.
Click to expand...
Click to collapse
I'm eagerly waiting for this new release, master. Thank you for all your hard work. But please, change the name of this rom: while honeycomb has a special meaning, FolioComb seems to me a strange tool involved in hair hygiene... ;-)
Questions
Hi!
I've two question. The 3.0 port contains olny the honeycomb support?I mean there are a few application for 3.0 android so it is possible to use the older (2.1 and 2.2) aps and games? The secound one (this is my first priority is this support 3G modules?Notion Ink has WWAN - 3G HSPA module so I hope that this can help you a little bit
Thomas7610 said:
Hi!
I've two question. The 3.0 port contains olny the honeycomb support?I mean there are a few application for 3.0 android so it is possible to use the older (2.1 and 2.2) aps and games? The secound one (this is my first priority is this support 3G modules?Notion Ink has WWAN - 3G HSPA module so I hope that this can help you a little bit
Click to expand...
Click to collapse
1. it works fine with old apps.. i already tested angrybirds, and astro filemanager, i would say 100% supported.
2. im using our 1.3 based kernel, so it has 3G usb dongle support, but whether 3x will utilize it i have no focus on for now.. lets first get it out and get more people involved, then lets see what it brings.
Happy Face!
I friggin' knew it!!! I finally can take the Folio back, out of the drawer where I locked it months ago PartyTime!
BTW: I've got no problem at all with media scanner not working. It should be considered a FEATURE, not a cons!!! At least it's not gonna randomly delete ALL of my media files over and over again!
EDIT: if there's anyone wishing to follow the original thread for the ADAM, here we go: http://tabletroms.com/forums/showthread.php?356-Honeycomb-on-the-Adam-(Updated)
Hi!
Of course first the stabil working is the most important
Very nice to see this!
I really would love to try even an early version of honeycomb on my folio...
To bad I use my folio a lot latley (I have some server issues, and I don't want to carry my laptop everywhere I go)... But if I know that apps will work correctly (even if slow, but pretty much usable) I will give it a shot....
Please, post rom!!!
Please dont begg!!!
Sent from my HTC Desire using XDA App
My second Folio is now in standby for testing........
Thank you for your hard work Dexter.
Excellent News!
These are excellent news!
I knew you guys could do it!
Thanks for the hard working of everyone involved.
Cant wait to test.
That's great news!! Then i can take the dust of my Folio
Great work Dexter!!
really thanks
again really TnX to the wonderful DE-NOT-AD trio (Dexter, NotionInk Adam and Advent Vega developers).
mattblack85 said:
That's great news!! Then i can take the dust of my Folio
Great work Dexter!!
Click to expand...
Click to collapse
So am i!! I was soldind it, now i give up.
Thanks Dexter for your work.
Nice
Youre so nice!!!..really!I believe you that you can complete it.
Thanks a lot Dexter
Hi Dexter,
Thank you so much for your really good work. After FolioMod now a good working Honeycomb for Folio? -> Amazing!
So, don't missunderstand me, but I really love you for that!
Thank you
You Dexter and Developers who are working on that are GODs...
We hope rom tonight if its possible... else, we can wait for the great work.
Thank you and thanks to honeycomb developer team !
thanks thanks thanks
thats better than christmas.
thank you for your hard work
i hope it goes on.
Just a quick note.. I do hope it is noted what majors are wrong with this one..
i will look into this, but the first "public" will have more or less what i have written as problems..
Our kernel might need to revising, or DerArtem's 2.6.36.3 kernel might help to solve some issues as well..
So the rom is really a "preview" and not for daily use yet...
Lastly, this rom is of course open to anyone who can help fixing the problems, and we can make an even better rom, so if you got any kind of experience with it, help us make this rom better.
I think the easy one is, for now, to get powerkey fixed. (volume buttons work).
I got my S2 on Tuesday and thought that the default firmware had a few shortcomings. Hence I took the stock English firmware and tweaked it to my needs.
Maybe you will find my ROM useful too.
So, what I changed:
Enlarged the data partition to 2.5GiB. I did this for two reasons. Obviously one is so we can get more space for apps. The other is that inside the /data partition are not only stored apk files, but the application's data files (which get written and read frequently). When a partition on a flash disk gets full, it also gets slow. So hopefully with 2.5GiB you will always have enough free space to keep performance up.
Rooted and the new, open source Superuser included.
Replaced the default launcher with the latest Nova Launcher.
Included Titanium Backup.
Changed the read ahead of the flash memroy to 1024KiB from the default 128KiB. While there isn't an overall best setting, I feel that this helps a lot with Chrome, which had huge delays while trying to load a page from its cache.
Changed the default io_scheduler to deadline. it gives better responsiness.
Default notification ringtone changed to something that won't cause heart attacks.
I added proper OTG support. Our tablet supported usb devices only on the OS level and not on the Android apps' level. So while a hardware keyboard would work, camera tethering with DSLR Controller wouldn't. Maybe Pipo did that because the tablet's usb system isn't solid. USB OTG doesn't work always, but at least it always works after a reboot for me and it is awesome to control my DSLR from the tablet.
Added support for cifs (smb).
Removed some apps and widgets which I think aren't that useful.
You can flash it with RKBatchTool. The first boot will take a bit more time until it gets to the launcher screen.
There may be some S2 tablets with a newer front camera module. If that's your case, your front camera may not work.
Pipo-S2-20121123-DS803H-mrsaccess-v1.40
Part1: http://hotfile.com/dl/197646869/89622a6/Pipo-S2-20121123-DS803H-mrsaccess-v1.40.part1.rar.html
Part2: http://hotfile.com/dl/197645382/049223e/Pipo-S2-20121123-DS803H-mrsaccess-v1.40.part2.rar.html
if you know a better host, please suggest
Disclaimer: If you break it, you keep it. I won't take responsibility for broken tablets.
I got CWM on my Pipo s2. I can install the ROM through there, yes?
Also, think we can see CM 10 on it anytime soon?
This ROM can only be flashed with the official tools, it doesn't support CWM, nor it installs it. If you flash it, you will lose CWM.
As for CM, I don't think we will ever see it. Chinese vendors do not give much information or any source code, so it is practially impossible to do a port.
Some guy started working on a CM port for RK3066 devices, but as far as I know he hadn't much success other than a very alpha rom for his device (not the S2).
Ah I see. Well thank you very much for providing this ROM! Is there any way you can provide a short step by step tutorial? I've downloaded the rkbatchtool but alittle unsure of how to proceed.
Great ROM .....Many Thanks For This Great ROM .... Now Downloading .. Please Check My PM And Please Reply ......
New dl links
hi mrsaccess, still possible to get new links for the custom S2 rom ? thx in advance.
I have been using my Nexus Q for about a year via the audio amplifier outputs. When the last Music update broke Q functionality, I decided to give CM10.1 a try on the Q. After fighting some installation issues, where all audio output except "Alarms" were silenced, I found that audio is only working on the HDMI output.
After digging through the code and doing a bit of analysis of the stock Audio HAL, I figured out how to make an audio HAL that supports the TAS5713 audio amplifier used in the Q. As of now, it only supports one audio output device (either HDMI, S/PDIF, or TAS5713) at a time, and the output can only be changed during compile time.
But with some work, this HAL could eventually support all three outputs (HDMI, S/PDIF, TAS5713.) The issue is that Android only appears to support one output device at a time. In order to overcome this, I believe the audio HAL would have to replicate the PCM data stream and send a separate copy to each device.
Through experimentation, I found that the TAS5713 requires a 48KHz audio stream, and S/PDIF also works well with this rate.
Another challenge is that the TAS5713 amplifier volume is controlled by the kernel driver, so you have to tell Android that the Audio HAL will do the volume control itself (ie, not rely on the mixer in Android.) For this reason, if all three output devices are eventually supported, volume control for S/PDIF and HDMI would have to be done in software. Perhaps it can be done while duplicating the PCM stream by taking each of the 16-bit values and multiplying it by the volume level.
Looking through the Steelhead kernel, you can see that Google put some work into being able to synchronize the three audio output devices. This would also have to be added to the HAL for proper operation.
Anyway, I'm putting the changes out there in GitHub in case someone wants to do some more improvement to this audio HAL.
The fork of CyanogenMod/android_device_google_steelhead is hharte/android_device_google_steelhead:
https://github.com/hharte/android_device_google_steelhead
For binaries that you can flash to your Q (TAS5713 audio amplifier and S/PDIF) please scroll down to post #9 and choose the correct binary. Each binary only supports one audio output.
Please make this a reality.. I'm dying to have the analogue outputs working at the same as HDMI. it was possible on the stock Nexus Q image.
Thank you for the work you've put into making this a reality. I would love to try out a build with the amplifier selected as the output device, but it sounds like you can't control the volume natively?
Sent from my Nexus 4 using Tapatalk 2
Thanks for doing this!
After cloning your repository, I wasn't sure what to modify to have audio output through S/PDIF or TAS5713. Would you mind giving some advice to someone new to building CM?
Thanks in advance.
mahler47 said:
Thanks for doing this!
After cloning your repository, I wasn't sure what to modify to have audio output through S/PDIF or TAS5713. Would you mind giving some advice to someone new to building CM?
Thanks in advance.
Click to expand...
Click to collapse
In device/google/steelhead/audio/audio_hw.c, change the following line in the function adev_open():
adev->card = CARD_STEELHEAD_TAS5713;
Change CARD_STEELHEAD_TAS5713 to one of:
CARD_STEELHEAD_HDMI,
CARD_STEELHEAD_SPDIF,
CARD_STEELHEAD_TAS5713
Volume control should work fine for each of these, based on my last commit:
https://github.com/hharte/android_d...mmit/a15f772b5651e0b14c65f6ff1a6d498d2951e081
Then "brunch steelhead" to re-build CM10.1 for Nexus Q. After it is done building, you can go into out/target/product/steelhead/ and do "fastboot -w flashall" to wipe and flash the new CM image. If you are making minor mods, no need to use "-w" to wipe.
Please let me know if you find any issues. One of the main things I've struggled with when using CM10.1 on Nexus Q is that sometimes after installing gapps, the audio is completely silent. I have not found a good way to fix this other than downloading and installing "Audio Manager" from the Play Store.
-Howard
Howard, YOU ROCK!
This is amazing. My Nexus Q is nearly back to the functionality that I once had with stock firmware, and it's once again a useful device.
Here's my setup:
1) 2013-06-12 nightly build with your changes merged, and as instructed above, audio sent to S/PDIF. My Q is connected to the stereo via optical cable.
2) VNC Server is installed on the Q, and it turns on upon boot. I am using this VNC Server, but I bet others would work.
https://play.google.com/store/apps/details?id=com.schumi.vncs
3) I also have FTP server and ADB Wireless turned on upon booting so I can push files and mess with the Q remotely.
4) VNC Viewer installed on my other devices.
With all of that, I can basically control the Q remotely from my phone, tablet, or computer. VNC is slow, even with a wired connection, but it works.
Prior to your good work, I had to have the TV on to hear anything out of my Nexus Q. However, with the changes you've implemented, I no longer have to do that. My Q lives again!! :victory:
Thanks so much--things can only get better and better from here. This is exactly why the Android community is so amazing.
mahler47 said:
Howard, YOU ROCK!
This is amazing. My Nexus Q is nearly back to the functionality that I once had with stock firmware, and it's once again a useful device.
Here's my setup:
1) 2013-06-12 nightly build with your changes merged, and as instructed above, audio sent to S/PDIF. My Q is connected to the stereo via optical cable.
2) VNC Server is installed on the Q, and it turns on upon boot. I am using this VNC Server, but I bet others would work.
https://play.google.com/store/apps/details?id=com.schumi.vncs
3) I also have FTP server and ADB Wireless turned on upon booting so I can push files and mess with the Q remotely.
4) VNC Viewer installed on my other devices.
With all of that, I can basically control the Q remotely from my phone, tablet, or computer. VNC is slow, even with a wired connection, but it works.
Prior to your good work, I had to have the TV on to hear anything out of my Nexus Q. However, with the changes you've implemented, I no longer have to do that. My Q lives again!! :victory:
Thanks so much--things can only get better and better from here. This is exactly why the Android community is so amazing.
Click to expand...
Click to collapse
Glad to hear that it is working for you. I'm using AirBubble and Bubble uPnP apps on my Q along with "Remote for iTunes" on my phones/tablet. This allows me to actually use my iTunes library on the Q remotely, and DLNA as well.
What needs to be done next (but not sure when I will have time to do it) is to make some changes to the Audio HAL to replicate the audio stream for each output (HDMI, Amplifier, S/PDIF) and implement software volume control for the HDMI and S/PDIF.
Another really cool thing would be to be able to make the Q into a Bluetooth A2DP sink. Then you could pair it to your phone and use it as a set of bluetooth speakers.
Google obviously put a lot more effort into the Q than I have done (making a remote management app that is simple to use, and put a lot of work into making sure that the three audio outputs are synchronized.) So there is a lot more work that needs to be done.
Maybe eventually Cyanogenmod can take my audio HAL. At least it seems to be working as well as the one included in the CM10.1 nightly, and adds the choice of using the other audio outputs, although only as a compile option unfortunately.
I'm embarrassingly uninformed about the inner workings of Android, but is ALSA in Android in any way like it is in Linux? Because I think in Linux when you use ALSA to configure your sound devices and let's say you use Pulse Audio, you have to define in the ALSA config which devices to output sound to and also expose them somehow to the PA mixer. It sounds like what you're doing is only compiling one alsa module whereas a HAL more like the one Google's would be 3 separate modules, right? And then I have no idea how the Android mixer works, but in Linux you'd have a master slider that would control the digital sound and then separate sliders for each output device. Is that sort of behavior replicable in Android?
On a different note, I'm really really sorry to beg because I'm so close to getting a CM build environment set up for the first time, but could either of you gentleman upload a working TAS5713 build? I feel pathetic because it's taken me 2 days just to get a VM image set up on my wife's laptop and most of the CM repo synced and I just *know* that this rom is going to take hours to compile (assuming I was competent enough to set it up right and create a proper manifest). Once/if I get everything set up, I think I'm going to go ahead and commit to merging your amazing work with CM10.1 final when it's out and uploading the zip so that all 5 of us Nexus Q owners out there don't each have compile it from source, but for now, I'd appreciate any help y'all can give me
Malnilion said:
On a different note, I'm really really sorry to beg because I'm so close to getting a CM build environment set up for the first time, but could either of you gentleman upload a working TAS5713 build? I feel pathetic because it's taken me 2 days just to get a VM image set up on my wife's laptop and most of the CM repo synced and I just *know* that this rom is going to take hours to compile (assuming I was competent enough to set it up right and create a proper manifest). Once/if I get everything set up, I think I'm going to go ahead and commit to merging your amazing work with CM10.1 final when it's out and uploading the zip so that all 5 of us Nexus Q owners out there don't each have compile it from source, but for now, I'd appreciate any help y'all can give me
Click to expand...
Click to collapse
Hello,
Here is a build of CM10.1 from repo sync on 6/17/2013 for each of TAS5713 and SPIDF outputs:
These files ar enow being hosted at AndroidFileHost
TAS5713 (Audio Amplifier):
Download: https://www.androidfilehost.com/?fid=95784891001602467 (148MB)
MD5SUM: adc98db7a9905b89c0d2fa9eab601f58 *cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip
SPDIF:
Download: https://www.androidfilehost.com/?fid=95784891001602468 (148MB)
MD5SUM: ec26a86a5011cf480a9efb3cee63e000 *cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip
HDMI: Use stock CM 10.1 nightly build.
Note: If, after installing, you don't have any sound, then install gapps and download "Audio Manager" from the Play Store. Run Audio Manager and select the "Mute" profile, and then select the "Loud" profile.
To install:
Boot into recovery mode:
Code:
fastboot boot recovery.img
When Q has reached recovery mode, push the cm-10.1-....zip to /sdcard using adb, ie:
Code:
adb push cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip /sdcard/
push gapps (if desired) to /sdcard/
gapps-20130301.zip http://goo.im/gapps/gapps-jb-20130301-signed.zip md5: b7e53e96e1c8b1a1c4865bf29418c8e0
From within recovery, "install zip from sdcard" and browse to cm zip file. After this has installed, it is a good idea to wipe data and cache. Then install gapps (if desired) by again choosing "install zip from sdcard" and choosing the gapps .zip file.
If cm10.1 gets stuck in a boot loop, then you probably forgot to wipe. Reboot the Q back into fastboot as follows:
Unplug power for Nexus Q and wait about 10 seconds.
Plug Q back in.
When the LED lights up on the top of the Q, cover it with your hand until the LED ring turns red. This has to be done in less than one second. If you miss it, try again.
As soon as the ring is RED, remove your hand, and the Q should be in fastboot mode.
Now, you can "fastboot -w" to wipe, or "fastboot boot recovery.img" to boot into recovery and wipe using the menu.
Please let me know how these work for you. I'm using these TAS5713 and SPDIF builds now and they are working fine for me.
Thank you so much! My foray into rom building was initially a disaster. I got what I thought was a good virtual image built and configured, but then I found out a fundamental error on my part...I had built a 32bit image. So, I finally just installed Ubuntu on a system partition and finally yesterday built my first stock CM image. I'm going to keep going so I can build for myself, but at least now I can listen to my music on my nexus q speakers while I'm working
Your build is working just great for me. The only times I've had volume issues on stock, I just had to wiggle the nexus q top and tap mute/unmute a couple times. I don't know if your HAL is any different or not yet, but so far, so good! Thanks again!
Edit:
I've mirrored your files and intend for this to be the place I'll put my builds in the future. I'm fairly sure Google Drive doesn't have bandwidth limits, so anybody reading...have at it!
Sent from my Nexus 4 using Tapatalk 2
Make sure you have plenty of RAM in your VM. I'm building on a Mac Pro running Ubuntu (not in a VM) and it takes about 35 minutes to build.
Tried once in a VM running under Windows and killed it after about a day... but the VM only had 1GB of RAM allocated to it.
Thank you so much for the amplifier-build! Just installed it and my Q is better than before. For everybody who wants to re-use the Q as a music player, I can really recommend bubbleupnp. It directly accesses your Google Cloud Music and makes it available via DLNA to other devices
Just install it on the Q and on your tablet / or phone. On the device you want to use as a remote, you can select which media server (Nexus Q) and which media renderer to use (Nexus Q). And - bam - you have your Q back. Browse your media from the phone and play it directly from the Q. Bubbleupnp even has an option for autostart, so once everything is setup, you don't have to use keyboard / mouse / monitor.
The DLNA thingy also has another neat side-effect: The Q now is recognized in Windows 8 as a dlna-device and you can browse you entire Google Music Library with the Windows Explorer and play stuff to your Q...
Guess someone's happy his little gadget is back...
Again. THANK YOU for your awsome work on the Q.
New Life for the Q
[Solved]: was using an HDMI to digital converter cable. Hooked it up to my TV and everything worked great.
First, I would like to say.... this is great! I thought the Q was done.
I'm having some trouble with the install. I was able to push everything to the device, booted into recovery, followed your instructions in flashing CM10.1 and gapps.... and then all I got was the orb sitting there with its blue light and no video. I've messed up flashing roms on other android devices so I thought I would pop back into recovery and try another shot at flashing CM10.1 without gapps. I boot into recovery, the light on the Q keeps spinning (which is what I remember) but there is no video! I know I am in recovery because I can top the Q and it reboots (first option in recovery). What can I do?
thank you,
Tony
Awesome work, thank you !
This is exactly what I was looking for.
Thank you also for the idea of using bubbleupnp, it seems that the new functionality will be better than the original.
I can hardly wait to re-image my Q.
Thanks a million for sharing your work! Works like a charm for me with the SPDIF build.
Bullet91 said:
Thanks a million for sharing your work! Works like a charm for me with the SPDIF build.
Click to expand...
Click to collapse
Op we need ypour help if you would mind updating this to the newest nightly and giving a little support I will kick you some money I emailed you too since you are the only one who has gotten the amp to function.
Thanks for the work you have put in, but every time i try to download the TAS5713 version it is not the 148mb you post says and does not have a matching md5sum.
Can someone host their working TAS5713 build for me?
unknownkwita said:
Thanks for the work you have put in, but every time i try to download the TAS5713 version it is not the 148mb you post says and does not have a matching md5sum.
Can someone host their working TAS5713 build for me?
Click to expand...
Click to collapse
Yes the build I downloaded doesn't work either.
im hosting the rom Anthony uploaded in this g+ post. To the best of my knowledge it is the TAS5713 CM10.1 rom that was originally modified by hharte. Ill keep it up for the foreseeable future. I TAKE NO RESPONSIBILITY FOR ANYTHING.
https://docs.google.com/file/d/0B8a2mhiG243Ja1lqc0xVQzAwdjQ/edit?usp=sharing
ianandamy said:
Yes the build I downloaded doesn't work either.
Click to expand...
Click to collapse
Are you flashing the AMP build provided in this post? http://forum.xda-developers.com/showpost.php?p=42690346&postcount=9
For me it is the SPDIF build which is working, I did not test the AMP one.
Possible issues:
D6000 reboots: 2 users have stated that turning off animations was correlational to D6000 rebooting itself. I have turned off animations since the beginning and not experienced this problem at all on any ROM. Still, it's worth noting here as a possible solution: Turn animations back on if animations are off and you are having reboots
Box states other than official site in regards to frequency support: Gone, info link removed by XDA mods.
Several users experiencing restarts when phone goes into deep sleep
Hard bricked after ROM install: Plug phone into PC via USB and enter recovery (VolDown+Power) then do reboot
v2.4 D6000 dedicated function button not working. Solution: Switch to Chinese language and set by pressing button or through system settings. Switch back to English. Profit.
At least 4 Western users and one China user has experienced "dead battery" syndrome. The internal battery will not charge. Phone boots into Android, after a few seconds phone freezes, then reboots or powers down. Battery charge icons do not show when phone powered down. Solution:
[/hide]
All known ROMS
All known ROMS (contact me if we're missing any): Gone, info link removed by XDA mods
How to upgrade to 5.1 from User 861efdee
Driver Files (Found in 4pda.ru forums):
http://s000.tinyupload.com/?file_id=05936486760178633478 (Just the drivers)
https://yadi.sk/d/LKwZHvUEiosBx (Drivers + QPST/QFIL)
1. Install the drivers. (Accept all default settings)
2. Install QPST/QFIL (Accept all default settings)
3. Unzip the tar.gz to a folder. (Remember this folder)
4. Run QFIL, it should auto detect the port (mine was COM5)
5. Select Flat build.
6. Select Programmer Path from the unzipped tar.gz folder just now and select prog_emmc_firehose_8936.mbn
7. Ensure the Select build path is the path to the unzipped tar.gz folder.
8. Click on Load XML and select rawprogram_unparse
9.. Select patch0.xml
10. Click on Download. Windows will suddenly find and install another new driver and you will receive a "Fail to find QDloader" error
After Windows has installed the driver, go to QFIL and select the new port number for the device Windows have just installed. You should see the number change from 9091 to 9008 and different COM number.
11. Press Download again and cross your fingers.
Root, gapps, TWRP tutorial: Gone, link removed by mods.
Recommended gapps: http://opengapps.org Make sure to DL ARM-64 for 5.1. Pico recommended.
For those concerned about frequencies, we finally had a Canadian answer back and he's connecting to bands as advertised on the site. This means the box is incorrect and the official Innos site is listing the correct frequency support: Gone, link removed by mods.
Wow thanks for sharing :highfive:
Spec are good, but is innos a reliable manufacturer ?
Where can I buy one from 'Canada, and will it be in english????
A 6,000mah battery with octa a53's is exactly what i want.
benxico said:
Spec are good, but is innos a reliable manufacturer ?
Click to expand...
Click to collapse
They're using quality components. If you don't want to bite yet, wait for the review results.
imatts said:
Where can I buy one from 'Canada, and will it be in english????
A 6,000mah battery with octa a53's is exactly what i want.
Click to expand...
Click to collapse
Should be released this week. You'll need to buy from a China shop most likely, Innos D6000 unlikely to be sold retail in anywhere but China or China resellers.
Do somebody know, if it's prerooted? If not can somebody know how to do it?
Can I load there some custom roms?
Will custom roms recognize two batteries, or it's just unique for this innos firmware?
Details of software is necessary to buy, because without root it's useless.
It would be nice to get some more details of its software.
The Innos D6000 has just been received. As far as Innos D6000 root, rooting it shouldn't be a problem. I may delve into that later, but at this point just general testing. So far it's proving to be a very professionally done package. I've put together a quick unboxing. Just slammed it together. Nothing fancy. Uploading to YouTube now. Already up on Facebook.
<MOD EDIT - Link Removed>. First post on the page.
Chinaphonearena said:
The Innos D6000 has just been received. As far as Innos D6000 root, rooting it shouldn't be a problem. I may delve into that later, but at this point just general testing. So far it's proving to be a very professionally done package. I've put together a quick unboxing. Just slammed it together. Nothing fancy. Uploading to YouTube now. Already up on Facebook.
Click to expand...
Click to collapse
Sweet, thanks for the review. I've been looking at this phone for the last couple weeks and really interested in getting it. Really looking forward to the full review on your site!
Also, what exactly do you mean about rooting possibilities?
kuzimoto said:
Sweet, thanks for the review. I've been looking at this phone for the last couple weeks and really interested in getting it. Really looking forward to the full review on your site!
Also, what exactly do you mean about rooting possibilities?
Click to expand...
Click to collapse
It means the phone is rootable, but most likely will need to flash TWRP / CWM.
I'll be doing a running review of the Innos D6000. Piece by piece, then putting it together at Gizbeat with a conclusion. Most likely this week.
That's nice. Can't wait Your movie and my innos it's
Still waiting for dispatch in China...
It was nice if the root methods will work for it.
Hi all.
I bought this phone last week and so far is great.
I found a Chinese forum and install a ROM via native recovery from there but all the Gapps are gone now. The phone have no root and Market.
I install Mi Market and manage to install Play Store and Google Services but the Play Store gives me an error of connection due to the host file in System / etc (root).
I'm not a developer and i'm looking for a Custom recovery or Root access for this device, when you have please post it....
Thanks in advance
Hi All,
I also had problems with an update removing all google services.
You need to use the annoying Qualcomm wire brush method and drivers! As its type C USB, you will also need Qualcomm Ethernet drivers and not standard USB.....
In windows 10 etc you'll also have to disable driver certificate verification to install the drivers.
At the moment there is no root option, but here's the google play 5.1.1 version:-http://bbs.innos.com/forum.php?mod=viewthread&tid=59378&extra=page%3D1&mobile=2
To register on the innos BBS to view links, you'll need a QQ messenger account to use the baidu cloud downloaded.
I would post the entire instructions but I'm currently on holiday in the Ukraine.
Let me know if you need any more help installing the ROM and getting over the great firewall of China!
Thanks!
adojames said:
Hi All,
I also had problems with an update removing all google services.
You need to use the annoying Qualcomm wire brush method and drivers! As its type C USB, you will also need Qualcomm Ethernet drivers and not standard USB.....
In windows 10 etc you'll also have to disable driver certificate verification to install the drivers.
At the moment there is no root option, but here's the google play 5.1.1 version:-http://bbs.innos.com/forum.php?mod=viewthread&tid=59378&extra=page%3D1&mobile=2
To register on the innos BBS to view links, you'll need a QQ messenger account to use the baidu cloud downloaded.
I would post the entire instructions but I'm currently on holiday in the Ukraine.
Let me know if you need any more help installing the ROM and getting over the great firewall of China!
Thanks!
Click to expand...
Click to collapse
Hi Ado James
I have everything you said here except the Qualcomm ethernet drivers.
I will look for this in Google and try to install it and then try to install the ROM....
I will keep you post it
Thanks
This bbs site lookslike fully of helpful informations, but even after translate looks like hard to understand...
Maybe it's time to make space for innos at this forum? Mods?
It could be reason to collect soft or even ingest developers to do done software?
It was nice to install TWRP and some custom roms like slimcat or cm... Is it possible? Will wait, will see...
Zenuno said:
Hi Ado James
I have everything you said here except the Qualcomm ethernet drivers.
I will look for this in Google and try to install it and then try to install the ROM....
I will keep you post it
Thanks
Click to expand...
Click to collapse
Hi Ado
I can't find the right drivers for type-c usb.
If you please, when you arrive from your vacations try to post here all the drivers and programs necessary...
Thanks in advance
I also get the Innos D6000 and are happy with him. By reading your posts it's not an option to upgrade(using wire brush) to a newer version of software due to the play issue(suppose international shipment bring a bit different rom from the Chinese version). On the innos bbs forum i also noticed people not happy with newer software than v1.1 (android 5.0.2), but also noticed people are happy with this rom:
http://bbs.innos.com/thread-59378-1-1.html
it seams it bring play, anyone tried it ?
D6000 frequencies?
According to Gizbeat there is a question about frequencies
<MOD EDIT - Link Removed>
Owners of d6000 If you could, please state your location and what frequencies you are quite sure you're connecting on.
There's also this thread: Where a user is unable to connect to B7 LTE
<MOD EDIT - Link Removed>
Because I'm from USA and it means the phone is completely useless there if box is correct.
damian5000 said:
According to Gizbeat there is a question about frequencies
<MOD EDIT - Link Removed>
Owners of d6000 If you could, please state your location and what frequencies you are quite sure you're connecting on.
There's also this thread: Where a user is unable to connect to B7 LTE
<MOD EDIT - Link Removed>
Because I'm from USA and it means the phone is completely useless there if box is correct.
Click to expand...
Click to collapse
I've communicated with Innos today. According to them the specs are as stated on their official page and through their selling partners. The box only reads the minimal frequencies so as to not confuse Chinese people where the majority of these phones are sold.
Of course, this isn't 100% solid. What we need is reports from people who own the phone, where they live and what kind of connectivity they're getting, especially from anyone in N/C/S Americas, but any reports from any locations are good.
I got my D6000 on saturday. My problem is, that the phone is always reebooting when you turn off the display. This happens in between 1-2 minutes after put the phone in standby. When i turn on flightmode the phone is not reebooting!! Maybe there is a bug with the modem. I use TELEKOM (t-mobile) in Germany.
The rom is version D6000_ROM_COMMON_V1.1 (Android Version 5.0.2).
Any ideas?
Hanz, that's a good guess that it's something with the radio or radio software. If I were you, I'd try the beta 5.1 and see if the problem continues. If it doesn't, then you know it's a software issue. If it does, it still might be a software issue (eg, if it's a driver or baseband issue and these files not changing between ROMs). I'm only recommending it as part of the process of elimination.
First you might want to try setting to WCDMA only, GSM only, LTE only, and see if it's an issue with more specific connectivity. If these options don't exist in mobile network settings, try to use this app https://play.google.com/store/apps/details?id=de.mangelow.network&hl=en