Related
Ok noob alert..just a prelude I've done alot of searching and reading, and *think I have some answers, but if some kind soul were to take a quick look and maybe verify what I've found, I'd be eternally grateful. I used to have a LG Optimus and easily rooted/upgraded to CM7 by reading this forum and didn't have to ask any questions.
Now I've gone and signed up for WIND (Canada) and picked up an XT720. It's my budget and I'm not overly concerned about whether or not I have ICS immediately. I'd rather have something stable and $$ saving.
OK so I'm noticing a serious difference in the way the XT720 handles the WIFI/mobile data situation compared to the LG: it doesn't. First off, there's no easy way to turn off mobile data. Secondly, enabling WIFI gets me a connection to my router, yes, but browsers and apps that require a connection just refuse to use the WIFI unless: 1. there is 3G data connection - in other words, it ain't using WIFI 2. I put the phone in Airplane Mode, and turn WIFI back on. Great, but now no phone calls or SMS. Not a viable workaround. Option 3 involves hard resetting the phone with a battery pull which sometimes works and sometimes doesn't.
From scouring around various sites, this seems to have been a common problem with 2.1 and this model of phone. And thus the workarounds I tried were also employed by others.
From what I know of all versions custom ROMs etc from 2.2 onward for other models of phones, though, this wasn't an issue, and also in 2.2 and onward you can switch off Mobile Data which will force the WIFI connection if turned on.
So is this something that I will see an improvement on if I install say CM 6.3 onward or whatever? I'll get the ability to turn off mobile data, right? And then there theoretically shouldn't be a conflict, right?
That's my biggest issue. I don't get enough 3G signal in my house to just use the mobile data connection, I absolutely have to be able to use WIFI and receive phone calls/texts at the same time, so if custom roms aren't going to help me, I'd best return the phone.
Some other things I'm curious about:
- do most of the normal functions of the phone work with CM 6.3? HD recording, camera, HDMI out etc? Anything I've missed?
- I see quite a bit of talk about people running out of RAM and using sd swapping etc is this a common problem? Even with about 20 or so apps and CM7 on my LG Optimus I was still able to maintain about 110 mb RAM free at all times by judicious use of installing apps on SD card...will I be ok?
- Probably the biggest question before I root/install...most of the guides I'm reading talk about installing various stock sbfs etc etc...I'm coming in from a WIND stock rom so I don't *THINK* I need to do this, right? I should be nandroid'ing, Open Recovery, flash custom rom....right?
Here's my specs
Xt720 Wind Canada
s/w STR_U2_05.1F.2
f/w 2.1-update1
f/w config GAS_NA_NAWIND_P012
Baseband 3GSMEPU91A_U_91.075EI
kernel 2.6.29-omap1
I realize that some of this is covered in other threads. To be honest tho some respondents/contributors aren't English first language and I just want to make sure I haven't misunderstood anything. Anyone who has done similar to what I'm trying to do, especially coming from a WIND perspective, lemme know your thoughts, please and thanks alot!
acrobat69 said:
Now I've gone and signed up for WIND (Canada) and picked up an XT720. It's my budget and I'm not overly concerned about whether or not I have ICS immediately. I'd rather have something stable and $$ saving.
Click to expand...
Click to collapse
I've picked up the XT720 myself from Wind a few days ago at the clearance price ($150 outright, no plan). They even told me there are no guarantees with the phone with its stock ROM and seemed glad to hear that I was gonna use it with a custom ROM. I knew what I was getting into and the only reason I still bought the phone is this:
http://forum.xda-developers.com/showthread.php?t=1300246
We are extremely lucky to get Gingearbread on our phones, so don't even think of ICS at this moment. As you noticed already the stock 2.1 is useless and I flashed mine the 1st day.
acrobat69 said:
That's my biggest issue. I don't get enough 3G signal in my house to just use the mobile data connection, I absolutely have to be able to use WIFI and receive phone calls/texts at the same time, so if custom roms aren't going to help me, I'd best return the phone.
Click to expand...
Click to collapse
The ROM I linked above (the only 2.3, actually CM 7.1 available for XT720) works as you'd expect with wifi and 3g, that is it uses wifi when connected to both. Any decent ROM will do that.
acrobat69 said:
- do most of the normal functions of the phone work with CM 6.3? HD recording, camera, HDMI out etc? Anything I've missed?
Click to expand...
Click to collapse
HD recording - not yet (you don't lose much anyway, the camcorder quality would be crappy, check reviews with the stock OS)
camera - yes (pretty good quality)
HDMI - not yet (I'm guessing it will be fixed very soon, the devs are working on exactly this)
everything else - yes
acrobat69 said:
- I see quite a bit of talk about people running out of RAM and using sd swapping etc is this a common problem? Even with about 20 or so apps and CM7 on my LG Optimus I was still able to maintain about 110 mb RAM free at all times by judicious use of installing apps on SD card...will I be ok?
Click to expand...
Click to collapse
This one is tricky, the phone only has about 225mb usable RAM, there's not much multi-tasking you can do with that amount but it's workable. There are some performance tweaks you can do (overclocking, CM settings, V6 SuperCharger, etc.) to make it decent. Moving apps on sd card is a good idea in order to save storage space on the phone (another limited resource at only 174mb) but has nothing to do with RAM.
acrobat69 said:
- Probably the biggest question before I root/install...most of the guides I'm reading talk about installing various stock sbfs etc etc...I'm coming in from a WIND stock rom so I don't *THINK* I need to do this, right? I should be nandroid'ing, Open Recovery, flash custom rom....right?
Click to expand...
Click to collapse
I've been wondering the same thing, what's up with all the SBFs people are talking about left and right? The answer is don't worry about them, you don't need any SBF. They are just that, stock ROMs, all 2.1. You would only need one (the Wind version) if you wanted to take the phone back for servicing and wanted to return to the original non-rooted state. Apparently even if you take a full nandroid backup with your stock ROM now and restore it later, the phone will still be rooted and this is where a stock SBF would help. I'm not gonna bother, even if I do take it back (highly doubt it, with the custom ROM it's a very good phone for $150 outright), I'm just gonna restore my stock nandroid backup.
So what you need is:
1. root the phone (personally I used SuperOneClick, google for the latest version)
2. install OpenRecovery: http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
I can send you the file you need if you pm your email address. I HATE it when I have to register on some forum just to get 1 stupid file. And you absolutely CANNOT get that stupid file anywhere else on the face of the Earth/internet.
3. install this mod for OpenRecovery: http://forum.xda-developers.com/showthread.php?t=1242259
4. go to the ROM's thread, dl the latest build linked in the 1st post, copy the zip file to your sdcard\openrecovery\updates, reboot into recovery mode, apply update, format data&cache, reboot. Done. Enjoy!
BuddyBud said:
2. install OpenRecovery: http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
I can send you the file you need if you pm your email address. I HATE it when I have to register on some forum just to get 1 stupid file. And you absolutely CANNOT get that stupid file anywhere else on the face of the Earth/internet.
Click to expand...
Click to collapse
There's an OpenRecovery apk floating around here to install ther OR bootstrap, no need to register at ModMyMobile.
:Edit:
Woodrube has it attached to this thread. Install the apk from the sdcard, reboot, then run the apk & install OR. (Now you can switch out the OR files with Mioze's modded OR)
here you go
I knew that thread would come in handy one of these days. Plus Buddy and Acro there are other handy APKs in there too.
Mioze actually have all the necessary Open Recovery files linked in his CM6.3 topic
that's the most updated version
THANK YOU THANK YOU THANK YOU to James and everyone who has responded so far - even going so far as to direct link me to files I'll need? You guys are the best!!.
I really appreciate the encouragement. I think tonight's the night.
I'll try and log my procedures and steps and make note of anything I run into for future noobs like me I might be able to help..that's how community works, right?
Wish me luck!
Good luck
One more tip: If you find that Market keeps crashing after you flash fjfalcon's ROM, flash this updated Google Apps package - gapps-gb-20111216 (dl link here).
It worked for me. Put the zip file on the sdcard right next to the ROM file and flash it just like the ROM file.
PS: Who's James?
Ah BuddyBud sorry, there is another Canadian Wind guy named Biker Bob (real name James) who was posting about his experiences in another thread, and I mixed the two of you up..
About to try this...couple questions
Has anyone watched/used Reverend's tutorial video? Results?
I don't need to unlock the phone first, right? Please tell me no, I just got it! lol
The Revs videos are a good reference & if you are talking about a sim unlock that's not necessary.
Yes Revs videos are good to show.a visual of what you should do. Don't worry about it. I know it is scary the first time but once you do it, it will become second nature. Don't forget to wipe cache, dalvik and factory reset. If you bootloop, that is probably why.
No you don't need to be unlocked. That just deals with carriers and not ROMs.
Im on the edge of the decision precipice..am not too nervous about doing this, as in fact I'm pretty technically proficient..it just seemed that this process was a bit more convoluted than the one I picked up on easily for the LG.
Decisions decisions...6.3 or go all the way to 7.1
I think I need stability...and I'm not sure I want to get into a whole bunch of swapping locations etc. I noticed The Reverend mentioned he didn't bother with swaps. Mind you, I don't even think he made an ext partition either, which boggles my mind, I was almost sure you had to make at least one for any custom ROM. I might be showing just how little I know here! lol
Is it just that 7.1 is more of an ongoing thing, or by now are most of the +/- s of both pretty much on par? I know, I should be reading all 78 pages of the damn thread, right??
Oh boy, I just read through the Bravo thread...and the LED notification sounds SOOO tempting. No LED notification bugged the hell outta me on the LG. Hmmmm...
Ok...have settled on the ROM in this thread (Bravo):
http://forum.xda-developers.com/showthread.php?t=1332410
I just want to make sure of one thing...the VERY helpful steps that you all have outlined ie BuddyBuds...they stay the same up to step 4 (ROM + update) no matter what ROM I choose, pretty much.
Brians instructions are just a slight bit confusing in that Im not sure if I have to apply just the most recent update for LED ie v1.6...or if I have to install ALL the updates from the start on up (I think there are 4 of them). To me it would seem logical that each new version would be cumulative ie include the stuff from previous versions...but I just want to make sure!
One more thing..I didnt notice any mention of gapps in the download in that thread (nor did I see a gapps apk in the files I unzipped, but might have missed it..)...if not, Ill need to apply that too, right..any special version to useÉ
Ok so...
I went with Brian's BRAVO. I followed some of the steps provided in this thread, coupled with Reverand's video. I used his OpenRecovery install method (ie original from the Dexter build, copy new over top that) because I've never installed OpenRecovery before and it just seemed confusing on other threads.
To root, I used UltimateAndroot, in order to have the ability to unroot the machine (you'll see why...)
The first thing I checked, of course, was the pull down power/status bar to see about turning off various connections (ie Wifi, Bluetooth, Refresh, Mobile Data, etc). Unlike other 2.2 Froyo's I've used, specifically..LG..there is no pull down/status bar. Damn. Went thru every Setting imaginable, but won't work. This isn't looking great.
Next thing I tested was my 3G/Wifi issue. To my dismay...the issue remains. Browser and apps are still trying to use 3G first and foremost, as far as I can see. How do I know? Because if I leave Data Network Settting to "Allowed", browser/apps work, and *seem to be using the WiFi, but the second the 3G signal fades or is dropped, I get connection issues, and WiFi is still on. If I turn Data Network Setting to "Not Allowed", it might/might not use the WiFi for a bit and then pretty consistently stop. When I mean "stop", I mean the phone is still showing connected to WiFi yet there are data connection errors on all browsers/apps that need data etc. Sometimes, if the 3G signal returns, I get the pop-up asking me to Allow the data, and if I say yes it works for a bit (but then, because of the 3G signal issue, it cuts out again).
The fix - again - turn on Airplane mode, which disconnects all connections, turn on WiFi, then go back into Call Settings and search for the Home Network again. This is crazy, I can't do this every time, and eventually it craps out again and I have to do it all over.
The other really frustrating thing is I powered it down to do a full recharge overnight...when I booted back up it didn't find my Home Network at all and I had to rescan for it. Testing that out, sure enough, rebooting the phone I have to reselect the Network. Argh.
Any thoughts? The whole necessity of being able to turn 3G data off is so I can avoid this very problem. Basically, I walk in my front door, turn off data over the mobile network, and let my WiFi do it all while I'm home. I wish I could do this as effectively as with my LG on 2.2 (and later, CM7)
acrobat69 said:
Ok...have settled on the ROM in this thread (Bravo):
http://forum.xda-developers.com/showthread.php?t=1332410
I just want to make sure of one thing...the VERY helpful steps that you all have outlined ie BuddyBuds...they stay the same up to step 4 (ROM + update) no matter what ROM I choose, pretty much.
Click to expand...
Click to collapse
Once you get to step 4 inn Buddy's list check out this. It will explain it a little bit better. Brought someone back from the brink on this thread. Where is says Dexter, just replace that with Bravo.
Brians instructions are just a slight bit confusing in that Im not sure if I have to apply just the most recent update for LED ie v1.6...or if I have to install ALL the updates from the start on up (I think there are 4 of them). To me it would seem logical that each new version would be cumulative ie include the stuff from previous versions...but I just want to make sure!
Click to expand...
Click to collapse
Per Brian's OP the v1.9 has all the patches.
v1.9,A new Nandroid IMG backup,All patches included(20111217).
Click to expand...
Click to collapse
One more thing..I didnt notice any mention of gapps in the download in that thread (nor did I see a gapps apk in the files I unzipped, but might have missed it..)...if not, Ill need to apply that too, right..any special version to useÉ
Click to expand...
Click to collapse
Gapps is for CM builds. Bravo is a 2.2 build.
Side note: If you are going to partition it is up to you. I and a few other don't but it is really a personal preference. When I did, I used MiniTool Partition Wizard and it worked like a charm.
A few things though:
1: Your partitions must be set up this way---> Fat then EXT2/3 then Swap (if you choose-I don't and never did-requires you to fastboot a custom kernel and since this is your first experience, I would not suggest it)
2: Sizes. Many noobs will set their EXT2/3 partition to 1gb. That is way too big and you are just wasting space. I find that somewhere between 350-400mb is more than enough.
3: Do not convert your Ext partition to EXT4 unless the ROM you choose supports it. If/when the time comes, use MZ's open recovery utility to do it and not GPArted or MiniTool. The creat a Hugefile that has to be deleted and is a PITA.
4: If you do decide to partition, you will have to boot up fully, then go into your root explorer and in the SD-ext, you will need to create a folder called App (not apps-no S) so it will look like this sdcard/sdext/app. Then reboot and your apps will auto-install there.
Sorry for the long post and good luck.
---------- Post added at 11:30 AM ---------- Previous post was at 10:42 AM ----------
acrobat69 said:
Any thoughts? The whole necessity of being able to turn 3G data off is so I can avoid this very problem. Basically, I walk in my front door, turn off data over the mobile network, and let my WiFi do it all while I'm home. I wish I could do this as effectively as with my LG on 2.2 (and later, CM7)
Click to expand...
Click to collapse
Once you click on WIFI it should take over as your primary source of data. Not sure why unless I think I might have figured it out. Go into settings>wireless>tick your WIFI and once your router pops up leave it alone and hit your menu button. Set your WIFI sleep policy to NEVER and I bet that takes care of it. Pretty sure that is toggling off your WIFI when 3g is present.
Other solution is Widgetsoid and Elixir both have a widget to toggle off data (so does Beautiful widgets too for that matter). You can use those but I really think the above solution should work for you.
Woodrube said:
Per Brian's OP the v1.9 has all the patches.
Click to expand...
Click to collapse
Ah, figured..however when I go into LED Notification, it says "revision 1.6" (or some wording to that effect) at the bottom. Maybe that's just an error, but I just used that to gauge whether or not I had installed the latest revisions etc.
LED Notification works for text messages. I haven't seen it work for calls yet, but maybe I'm doing something wrong. I call the phone, the screen lights up that there's a call, and then ultimately closes when noone answers it. It was at this point that I'd assume the LED notification would come on. Screen is out, so LED, right?
Woodrube said:
Gapps is for CM builds. Bravo is a 2.2 build.
Click to expand...
Click to collapse
Ok I guess I goofed then, because I tried to update with Gapps after I installed Bravo. One thing I noticed is that I wasn't prompted to sign up/into my Google accounts or set up the phone when I rebooted following the Bravo ROM + Gapps install..that had always happened on my LG when I did CM installs...your explanation makes sense!
But...isn't CM6 basically 2.2 and Bravo basically 2.2? Or maybe I misread that.
At any rate, the real reason I updated Gapps is because I wanted the "new" Market look. I don't like the old one very much, really like the My Apps function. Is there way I can just patch this in to Bravo?
Woodrube said:
Side note: If you are going to partition it is up to you. I and a few other don't but it is really a personal preference.
Click to expand...
Click to collapse
Why do people partition? I did it on my LG, but never used it. Partitioning has nothing to do with installing user apps to the SD card, right? I can do that anyways, true?
Speaking of which..in CM there is the ability to set the default install location. I searched to find something similar in Bravo, to no avail. Is there a way to do this?
Wait...I think you just gave me the answer to both these questions...duh me..
Woodrube said:
4: If you do decide to partition, you will have to boot up fully, then go into your root explorer and in the SD-ext, you will need to create a folder called App (not apps-no S) so it will look like this sdcard/sdext/app. Then reboot and your apps will auto-install there.
Click to expand...
Click to collapse
I guess I do in fact want to partition, then. I can't imagine how one wouldn't want to, I mean you don't want apps clogging up internal memory, right?
Woodrube said:
Sorry for the long post and good luck.
Click to expand...
Click to collapse
Never apologize for long posts...I'm the worst at it and I love pouring over every single last detail. I'm sure there are lurkers who appreciate also, I know I really did when learning on my LG. Thanks a million!!
Woodrube said:
Once you click on WIFI it should take over as your primary source of data. Not sure why unless I think I might have figured it out. Go into settings>wireless>tick your WIFI and once your router pops up leave it alone and hit your menu button. Set your WIFI sleep policy to NEVER and I bet that takes care of it. Pretty sure that is toggling off your WIFI when 3g is present.
Other solution is Widgetsoid and Elixir both have a widget to toggle off data (so does Beautiful widgets too for that matter). You can use those but I really think the above solution should work for you.
Click to expand...
Click to collapse
DOHHHHH!!!! I knew I had forgotten something about past settings that made my LG work so well.. I have modified the Wi-Fi sleep policy and hopefully it will work better now! One constant in all the issues I was having, now that you've mentioned this, is that the screen was sleeping/timing out while things were going on. I'd bring it back up, and be all "like, wtf" when my browser wouldn't work or apps that were downloading hung, etc. Mind you, it probably should have reconnected by itself, but whatever, if it doesn't, there's no harm in using Never Sleep for WiFi. I'm not that much of a stickler for battery usage. I go to bed, I charge the phone, I wake up, repeat. I don't need 4 days battery life and if I ever am in a situation where I do, I'm camping or somewhere remote ie no WiFi hence this doesn't apply as I'd just toggle WiFi off completely anyways.
You're right, I could use a Widget to manage my connections and I managed to grab Beautiful when it was 10 cents..but those reside on the screen and I would love to get that pull-down bar back, just so handy to drag down no matter what app/screen you're in...I know, I'm picky
You know what? I got a Notification Toggle app on my PC at home that I'll upload here tonight. I just remembered it while I was at lunch. It is from an older ROM so not sure it will work but worth a try. Usual directions. Push it to /system/apps reboot. It should be just what you are looking for if it works. Might not though so you'll just have to see.
CM6 is 2.2 and so is Bravo only Bravo was made from the official Korean update that was handed down and Mioze has created the CM6 from source. So yes they are both 2.2 but very different.
Edit: I have the latest Market.apk too. It is floating around here somewhere but I can't find in for some reason. I'll upload them tonight.
acrobat69 said:
Decisions decisions...6.3 or go all the way to 7.1
Click to expand...
Click to collapse
try them both first, then see which one you want to use as your daily driver.
i personally like the 6.3 better because it runs the fastest even on stock speed 720 Mhz
you can use Open Recovery to do a full backup, and switch back and forth between 7.1 and 6.3 until you decide which one you like best
7.1 has more themes to choose from and is more up to date, but... less free resources vs. 6.3 which is indirectly related to why it feels less quick than 6.3
7.1 feels similar to the speed you get on the stock ROM from Wind, 6.3 feels like a brand new device
Hello,
NOTE: Please see new thread with ROMs for Amplifier, HDMI and S/PDIF:
http://forum.xda-developers.com/showthread.php?t=2596910
Here is a build of Android 4.4 KitKat based on CM11 from repo sync on 12/14/2013 for TAS5713 (Amplifier) outputs. See the end of this post for details on issues and potential workarounds.
Please go easy on the downloads or mirror these files if desired. They are on my private server so bandwidth is limited.
TAS5713 (Audio Amplifier):
Download: http://www.magicandroidapps.com/download/cm-11-20131214-UNOFFICIAL-steelhead_TAS5713.zip (171MB)
MD5SUM: 422c9a863b9292dd0f2db60f105b4fd1 *cm-11-20131214-UNOFFICIAL-steelhead_TAS5713.zip
SPDIF/HDMI: Sorry, no build available yet.
Recovery: http://www.magicandroidapps.com/download/cm-11.0-recovery.img
MD5SUM: 21ef5dffca97cc803ed2351e3b34068d *cm-11.0-recovery.img
To install:
Boot into recovery mode:
Code:
fastboot boot cm-11.0-recovery.img
When Q has reached recovery mode:
1. choose "install zip"
2. choose "install zip from sideload"
From PC:
Code:
adb sideload cm-11-20131214-UNOFFICIAL-steelhead_TAS5713.zip
It is a good idea to wipe data and cache. If coming from my previous cm-10.2 image, it may be possible to avoid wiping data/cache.
Sideload gapps if desired:
pa_gapps-full-4.4-20131119-signed.zip http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.4-20131119-signed.zip (257MB)
MD5SUM: fa40f00fbdee7332bde93f51ee68218b
From within recovery, "install zip from sideload" and:
Code:
adb sideload pa_gapps-full-4.4-20131119-signed.zip
If cm11 gets stuck in a boot loop, then you probably need to wipe. Reboot the Q back into fastboot as follows:
Unplug power for Nexus Q and wait about 10 seconds.
Plug Q back in. Do not put your hand on top of the Q until the small LED on top lights up.
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.
If you keep your hand on the Q while plugging it in, or if you put your hand on it too quickly, it will not enter the bootloader.
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 CM 11 seems to be work, but there are some functional and stability issues.
FUNCTIONAL AND STABILITY ISSUES:
I have seen stuttering occasionally in audio playback in Google Music.
Chrome Browser in Google Play Store says it's not compatible with this device for some reason. Pulling the .apk off a phone and "adb install" to Nexus Q seems to work fine. Make sure you are using the latest Google Chrome update with KitKat support. The previous version will crash on KitKat.
If you find any other issues, please let me know.
Do you know if this point is fixed in the newest 4.4 builds?
"2. I have seen stuttering occasionally in audio playback in Google Music."
Thanks anyway, great work hharte !
Nice work. Any progress on WLAN? I have no wired ethernet near any of my Q's. Do you need any help moving forward with this?
Thank you sir, love to see development for this device!
Sent from my CM powered Nexus Q
I got WLAN working over the weekend, will post an updated ROM tomorrow.
Can we add packages from the factory images? I was thinking of the tungstenLEDService.apk. I guess its responsible for indicating the volume on the led ring and so on. I really miss that feature on CM. Maybe the visualizer package too, I don't know what that does but it would be great if we could get the led music visualization back, because it looks really cool
Here is the apk's location in the extracted system image
com.google.tungsten.ledservice
/app/TungstenLEDService.apk
/lib/libtungsten_led.so
I think the packages is installed here on stock Q's
package name=com.google.tungsten.ledservice
codePath=/system/app/TungstenLEDService.apk
nativeLibraryPath=/data/data/com.google.tungsten.ledservice/lib
package name=com.google.android.tungsten.visualizer
codePath=/system/app/Visualizer.apk
nativeLibraryPath=/data/data/com.google.android.tungsten.visualizer/lib
Do we have the source for these packages? I checked the android source but could not find any TungstenLEDService, but Im not completly sure were to look.
My biggest thing is getting the led ring and visualizer working on it again those are the 2 biggest things that I miss
Sent from my Nexus 7 using xda app-developers app
"SPDIF/HDMI: Sorry, no build available yet."
If you want SPDIF/HDMI audio output, you could flash the normal cm11 builds, don`t you?
I updated the build with working WLAN in the first post. Again, this is for the audio amplifier only.
Basari said:
"SPDIF/HDMI: Sorry, no build available yet."
If you want SPDIF/HDMI audio output, you could flash the normal cm11 builds, don`t you?
Click to expand...
Click to collapse
In theory yes, but not sure that standard cm11 has support for Q yet.
hharte said:
I updated the build with working WLAN in the first post. Again, this is for the audio amplifier only.
In theory yes, but not sure that standard cm11 has support for Q yet.
Click to expand...
Click to collapse
You're a god, please stay at this. After I install this where do I send Bitcoins?
Can SPDIF used as the audio input source?
Hello
Is uvcvideo.ko kernel part is included in the kernel ?
Thanks,
TT
Nice, I will try the new build as soon as possible. I'm waiting for my third Q bought on eBay. My girlfriend would kill me if I started tinkering with the existing ones, working perfect with CM 10.2 running spotify. The main reason I want KitKat on these are the improvements in performance. I use the Q's as my primary sound system with Spotify using the "Spotify Connect" feature. Amazing piece of hardware, I love the sound from the built in receiver but I'm not an audiophile.
Merry X-mas and a happy new year!
Extra Nexus Q
mannberg said:
Nice, I will try the new build as soon as possible. I'm waiting for my third Q bought on eBay. My girlfriend would kill me if I started tinkering with the existing ones, working perfect with CM 10.2 running spotify. The main reason I want KitKat on these are the improvements in performance. I use the Q's as my primary sound system with Spotify using the "Spotify Connect" feature. Amazing piece of hardware, I love the sound from the built in receiver but I'm not an audiophile.
Merry X-mas and a happy new year!
Click to expand...
Click to collapse
First of all, THANK YOU!, secondly, Merry Christmas & Happy New Year! Lastly, I happen to have a factory sealed Nexus Q just sitting here waiting to be put to good use. The opened but never used Q I have is getting this build as we speak. Just couldn't sit back without saying thank you!
Has anyone done this yet? How was the install? I've never rooted anything so I'm a little nervous it looks difficult. Could someone make a youtube how to?
Unsafe volyme warning
hharte can you dissable the "Unsafe volyme warning" in this rom?
How do I get video out put from my nexus
Ok so I have everything installed but you said the hdmi doesn't work so what am I supposed to use to see anything?
DavidLattimerii said:
Ok so I have everything installed but you said the hdmi doesn't work so what am I supposed to use to see anything?
Click to expand...
Click to collapse
Don't worry, video signal still goes through the HDMI cable, you'll see everything if you connect your Q to a display. However this is a build that supports the built-in audio amplifier. It means you won't hear anything through HDMI, you'll have connect your device to speakers (with banana plugs) in order to enjoy its sound.
Thank you for your efforts hharte!
Sent from my Nexus S using Tapatalk
yes you should be able to use the standard CM 4.4 builds, for HDMI sound. As far as i'm aware CM does support the Nexus Q..?
Sent from my Nexus Q using Tapatalk 2
OK sorry for my confusion however I was confused because currently when I plug my Q in to the tv (i've tried 2) it shows nothing not even a black screen the tv registers it as nothing so I am wondering if I installed something wrong or am I booting to it wrong?
I have a Sony bluetooth head unit in my car which supports handfree and audio streaming profiles. I can play my music through the head unit just fine via bluetooth. I can also make and receive calls without problem when I am listening to the radio (ie when I am not listening to my own music). However, when I am playing my own tunes and I either make or receive a call, the head unit indicates I am on a call, it mutes the music but I just get silence through the speakers.
I used to have a Galaxy S Advance and it all worked just fine without too much configuration on the phone or head unit; basically just pair them up, make sure the right boxes are ticked in the bluetooth options and thats it.
Any idea what the problem could be? I've tried an upgrade to 4.2.2 but it didn't help...
Hi,
I have a similar problem. I can pair my s2 plus with cm11 from this thread to my car kit (Parrot MKi 9200). Playing music via phone on the car speakers works fine but when I place a call the receiving phone just gets loud static (and my voice very very silent).
I wanted to ask the developer of the cm11 I am using if he sees a way to exchange the bluetooth module (or what androis equivalent is) to the one of e.g. Android 4.1.2 because I know that one works perfectly. I am posting here because I havent reached 10 posts yet.
Of course I am open to other workarounds and ideas.
Thanks,
Kiesel
Bluetooth
Same issue here,
everything (music etc.) is okay, but the phone connection.
I'm connecting to my Ford Sync.
I can connect, but then the quality of the voice is very very bad, I can hardly understand anything...
I thing there's a configuration file in the etc/ folder, maybe that need some upgrade?!?
Hope someone can help, because I really like to keep CM11 on my phone...
Dan
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
safariking said:
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
Click to expand...
Click to collapse
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
DeKiesel said:
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
Click to expand...
Click to collapse
I know what you mean but i think the best method now is to wait until cooldev find a solution to this
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Hmm, interesting. I will try this out as well. Might probably be a week though, I am leaving for holidays tonight and cant risk making my phone unusable. Maybe somebody else is willing to give it a try?
kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Thanks now i know where to search the problem.
Hi,
here is a logcat of a bluetooth connection during a call on stock rom/stock kernel.
What I did:
-start logcat
-start bluetooth
-chose a contact
-call contact-
-talk for a minute
-hang up
-stop logcat
I then wanted to flash the mosh kernel and do the same again but the last time I checked there wasnt this huge plethora of different kernels to choose from. Very impressive work!
Could you tell me which one you would like me to flash and I would then redo everything?
Hi,
I tried installing mosh kernel 1.8 and 1.85 (for stock, init.d enabled) on sazy rom but it didnt boot. It stayed at the very first screen you get when you turn the phone on. I then installed your cm11 build8, connected via bluetooth to my car and had someone call me.
Attached is the logcat.
Do I need the samsung stock rom for mosh kernel? I thought sazy rom was a stock rom?
Sorry I'm very to new all this stuff. I barely managed to root my Note Pro 12.2 a month or 2 ago, even then I did manage lose all my data.
But anyways, I recently got an OTG cable to plug my Xbox One controller into my Note Pro, and it seems to work fine when I pair it up with JoystickCenter (https://play.google.com/store/apps/details?id=com.poke64738.usbjoygolddemo&hl=en)
However some apps don't support controllers, but JoystickCenter has a Touch Emulation feature. When I try to enable it I get an error Can't access dev/uinput
I looked into this and found some info on it - https://groups.google.com/forum/#!msg/pokes-android-apps/sME_vV9pPcE/K-eTQFY_TpMJ
Which led me to this post - http://forum.xda-developers.com/showpost.php?p=53343683
I tried everything there, but I still believe SELinux is in Enforce mode :\
So I was wondering about the third fix listed, about installing a custom kernal.
I do see this post http://forum.xda-developers.com/showthread.php?t=2772908
I would be willing to attempt (It does say Knoxless, so I would assume it would fix my issue I'm having?) however I have no idea how to flash ROMs.
I looked up some guides about recovery mode and bootloaders, but I still have no idea what I'm doing.
I have seen some recent posts about not enough development for the NP 12.2, but I did find this http://teamw.in/project/twrp2/224
Maybe some people who know what they are talking about could set me straight on all this, and if it's possible for me to get around my issue?
Thanks in advance
The ROM you link to contains the stock kernel & won't get you any further forward. http://graemehill.ca/turning-a-galaxy-note-pro-into-a-linux-laptop/ seems to be the most promising source of advice I've found so far. If you have the same device as the author you can use the kernel he compiled. Unfortunately I don't think I do & am wary of trying to set up my own build environment being fairly comprehensively clueless, so I'm hoping someone with at least some experience will pick this up.
Do post back here if you find a solution. I'm after a permissive kernel for the same reason you describe.
jns20 said:
I tried everything there, but I still believe SELinux is in Enforce mode :\
Click to expand...
Click to collapse
maybe this could help:
http://forum.xda-developers.com/showthread.php?t=2765353
?
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Termuellinator said:
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Click to expand...
Click to collapse
*push* nobody got any ideas? i would post it in the appropriate thread (especially since this rom is still only nightly) as a potential bug report, but as a new user i'm not able to :/
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Termuellinator said:
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Click to expand...
Click to collapse
The WiFi bug is a known issue since early August. It affects almost every Moto device (G, G 4G, X and defy?) it's reported several times to CM-s bug tracking system, but nobody cares... You can use custom kernels. Maybe they aren't affected.
I don't know anything about the BT bug.
i found some posts about people having the same kind of wifi-issue, but it is good to know, that the devs are aware and - kind of - working on it
the BT-thingy is driving me insane though...fiddled around a bit, stopping BT-Related processes etc...this somehow did something...my phone now connects and stays connected, i can make phone calls...but the contact list is incomplete - only 3 random contacts are displayed on the car system
haven't rebooted since then, i kind of fear that rebooting will bring back the issue :/
BT still working after reboot, so it seems my "fix" is permanent...must have something to do with deleting the BT-data/cache while process was killed i would think - in case someone else also encounters this problem
still can't acces all my contacts from Car-system though :/
Most nights roms have a lot of issues and it is pretty hard to stay aware all of bugs. Why don't you try something more stable like Pac Man RC or some. Sometimes a different kernel will help sometimes it's the opposite.
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Termuellinator said:
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Click to expand...
Click to collapse
All AOSP rom uses the CM device tree and kernel as a base, so the low level kernel bugs are the same.. Also the last "stable" CM for falcon is dated back to April, so you didn't lose anything with peregrine...
Just in case anyone encounters the same Issues:
with CARBON-KK-NIGHTLY-20140922-0414-peregrine the BT-Problems seem to be resolved, connection works and the contacts are accessible from the car.
WiFi still has problems with dhcp, but as stated, devs are aware of that :good:
bad news: flashed to CARBON-KK-NIGHTLY-20141103-0939-peregrine and the BT-issue is back as in the beginning - com.andoird.bluetooth stops working - but only following the first connect -.-
interestingly going back to my pre-flash-backup didn't resolve the issue (doesn't matter if i just restore or wipe prior to that...but after flashing/restoring the first connect works perfectly)...perhaps that leads to some ideas about the cause?
was just trying to get it to work like the other time by stopping/deleting data of com.andoird.bluetooth, but didn't work this time
ok, figured it out again, this time i'll post my steps in case anyone ever encounters similar issues (and for my future reference in case i encounter them again, too )
1) unpair
2)switch off bluetooth
3) stop com.android.bluetooth in "apps"
4) delete data of com.android.bluetooth
5) reboot
6) pair
7) unpair
8) delete data of com.android.bluetooth
9) pair
10) reboot
at least these are the steps i did and it seems to be working now, again