yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] anykill:
I got a problem with CM, I have a DJI Phantom and I need to select wich app I will use with, but when I connect to the Nexus the option to select wich app will open, just closes and I cant select, then I cant fly my drone, with stock I can select normally, with my moto G with CM13 I can too...

what's wrong?

Thank you
[Nexus 7 (2013) Android Development] alfick3:
Hey, anyone that updated to 8/15 nightly; have you had issues with the touchscreen? I've been pretty happy so far, with the nighties, but after I updated (from 8/13 by the way) the touch screen was really buggy. It would take multiple presses just to select something. I was trying to play a game (Civilisation Revolutions) and it was very frustrating. I had to go back to the 8/13 nightly Bavaria's it was so unusable.
[Nexus 7 (2013) Android Development] NoN1979:
got some bugs due to new generic-extract utils in CM , need to to be fixed by CM team
[Nexus 7 (2013) Android Development] zwliew:
Does anyone else face a similar issue?

I highly doubt it. The makefiles change doesn't affect anything. Furthermore, that change happened before 20160815
[Nexus 7 (2013) Android Development] SoulSmasher:
How's the battery life comparing to the stock ? I'm planning to install and was just wondering.. Thanks in advance!
[Nexus 7 (2013) Android Development] sushi247:
clock and weather across device still not working since first mm release. was looking for a replacement for pure nexus since substratum is the crap of the earth. any work around not being able to select a weather provider?
[Nexus 7 (2013) Android Development] avatarx1:
I updated my Nexus 7 2013 (flo) to CM 13 snapshot. I was using Android 4.3 and it was working great but it started to randomly reboot while in sleep about a month ago. It had the same issue in safe mode also so I don't think it was app issue.

I like CM 13 interface and options and things like that but I found two issues so far.

1. Battery drains faster compared to Android 4.3 while using the tablet. With 4.3 I could use my tablet all day long but with CM 13, I have to charge my tablet midday.

2. Hangout crashss when I try to send a SMS. It crashes immediately as soon as I type a word. Also, if I click SMS icon from my contact list, hangout loads but exits immediately and gives me "To send an SMS with hangouts, turn on SMS in settings". I already did turn on the SMS.

Anyone found fix for the hangout?
[Nexus 7 (2013) Android Development] shuvabrata:
Blank screen after Google Logo

Hi All,

I was running my Nexus 7 (2013) on Cyanogenmod 13 Snapshot. After i received notifications of the new snapshot builds, i tried to upgrade. It won't reboot into recovery. So i headed to developer options and switched on "Advanced Reboot" and "Update Recovery". The device is now blank after the Google logo appeared. Please help.

regards,

Shuvo

Update: It started working after i tried to reboot into recovery after some time. Flashed the updates from the recovery and its working smoothly.
[Nexus 7 (2013) Android Development] Wannabedeveloper:
Looking forward for CM 14
[Nexus 7 (2013) Android Development] dcdave63:
I have the same issue with Hangouts. I even did a clean install, and it is still happening. It's very odd. Guess it's time to try something else, since there seems to be no fix for this on Cyanogenmod.
[Nexus 7 (2013) Android Development] Thebear j koss:
SMS doesn't work with flo nexus 7. SMS requires data, which we do not have. Nothing you can do about that...

Thebe?r'$ NeXu$
[Nexus 7 (2013) Android Development] dcdave63:
Hangouts hasn't needed it for the past year or so,why would it have changed? Also, just installer PureNexus and it works just fine.
[Nexus 7 (2013) Android Development] Thebear j koss:
SMS works fine? It requires data to send SMS. I am on Pure Nexus and it doesn't work. I can't send any message through SMS.

Thebe?r'$ NeXu$
[Nexus 7 (2013) Android Development] dcdave63:
I am using it on 2 phones, one with Google Voice and one with Google Project Fi. Both accounts are using Hangouts, and my Nexus 7 s both accounts tied to it and I can get and send messages through Hangouts and others are receiving my responses from both phone numbers. It has worked for me through Google Voice for 3 years, and for Project Fi for over a year.
[Nexus 7 (2013) Android Development] Thebear j koss:
Ok, but you are linked to some other number that can recieve SMS, if you don't have a # to verify, it won't work. You need data for SMS to work. The nexus 7 Flo does not have data.

You can send messages (not SMS) to your google contacts and g+ contacts. I haven't been able to connect with anyone outside of that on the nexus 7 since i do not have a android device with data. My other device is an iphone, completely google free.

Thebe?r'$ NeXu$
[Nexus 7 (2013) Android Development] dcdave63:
No the Flo does not have data, yet my original statement, that Hangouts is not working on the Flo, when it Hangouts clearly can and does work without data. So, Hangouts works just fine, it always has, just not on CyanogenMod 13. It works on PureNexus now. Clearly there is an issue with Hangouts on CyanogenMod 13, and no issue with others.
[Nexus 7 (2013) Android Development] mindmajick:
For all those having hardware issues... Try the official gapps I posted earlier in the thread.
[Nexus 7 (2013) Android Development] 78Staff:
Updated to 0115, update the file again, and boom it's now working. Very cool. Amazing how such a minor thing can be such a major factor in how usable a device is.

EDiT: and after a reboot, it;s gone. File is getting reset to 0 somehow. Oh well I'm almost there...

Nevermind, re-read the kernel thread and found the offender... for those having issues check out http://xdaforums.com/showpost.php?p=54012812&postcount=3...

---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------

I agree, while a bit older, I have zero issues with these gapps. I use PA gapps most of the time, but with the issues being reported with PA's I tried these and everything just works. You do have to do a few app updates but they stick through nighties so it's a one time deal really unless you do a full wipe.
[Nexus 7 (2013) Android Development] dadeo1111:
Glad you figured it out - not sure why I didn't have this problem myself - could be that I use MultiRom..?
[Nexus 7 (2013) Android Development] boxcar8028:
Anyone else having issues with Bluetooth and GPS? Bluetooth is working but with lots of skipping. its not my player or my music stream. Same song plays fine with headphone and N7 speakers. And I have totally lost my GPS, didn’t even notice until I checked with GPS Checker.
[Nexus 7 (2013) Android Development] mindmajick:
I'm not. GPS locking quickly and no Bluetooth issues with Pandora or mp3 etc audio. What gapps are you using?
[Nexus 7 (2013) Android Development] boxcar8028:
On my N7 I used the gapps from here:

https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip

But on my N5 it’s totally stock factory image. On both N7 and N5 was a full clean install.

No GPS issues on my N5 Just N7 but bluetooth skipping on both.
[Nexus 7 (2013) Android Development] mindmajick:
Is it always connected to the same device with the same network/internet connection? I don't have the n4, but I have the n7 on cm12 and the HTC m8 on GPE lollipop- have streamed to my car, home stereo and PC without any issues.

I would try the question in a more general lollipop thread for the Bluetooth issues and keep the GPS issue here. Although I haven't had an issue myself.
[Nexus 7 (2013) Android Development] boxcar8028:
It’s interesting that you ask about my network/internet connection because I read somewhere that the bluetooth skipping issues are only on wifi network and not cell network. I need to test this tonight. Now that I think about it the skipping only seem to be when I’m at home on my wifi network but not at work when I’m streaming from google music to my other bluetooth headphone.

Good call on the postings. :cyclops:
[Nexus 7 (2013) Android Development] tungdil:
[MENTION=4819666]drharder[/MENTION] [MENTION=4650021]Cm9aphla[/MENTION]

Same as with other Lollipop builds so far... it will install as secondaryROM with MultiROM after modifying the updaterscript. Just checked this with the build cm-12-20150115-NIGHTLY-flo and it is booting right now.

Note: the updater script may look a bit different than the one which the link leads to. However, it is the same principle when modifying: Just delete the if, ifelse and endif; statements and anything in between.
[Nexus 7 (2013) Android Development] Zinshin:
I have the same error, with the same setup, but with latest version of TWRP recovery.
[Nexus 7 (2013) Android Development] boxcar8028:
I also have lost my GPS. CM12 nightly 1.15.2015 after a clean install. :(
[Nexus 7 (2013) Android Development] Fivesack622:
I originally started off using Ajfink's unofficial CM12 build located here http://xdaforums.com/nexus-7-2013/development/rom-unofficial-cm12-preview-builds-flo-t2943784 around the beginning of December and then switched to the official nightlies once they came out. GPS has never worked for me no matter what I did. Tried wipes, clean installs, modifying the gps.conf file and nothing worked. If you look at Ajfink's thread, the issue has been present for some time.

Anyways, I decided to try flashing a custom kernel a few days ago to see if that made a difference and sure enough it did. GPS works great now and tested with GPS Test Plus, The kernel is the SaberMod Franco Kernal which is based off Franco's kernel and is at the present time the only kernel I could find compatible with CM12. It is located here http://xdaforums.com/nexus-7-2013/development/kernel-sabermod-franco-r17-t2809979. Give it a shot, it worked for me. Just download it and flash it directly after you flash the nightly zip.
[Nexus 7 (2013) Android Development] boxcar8028:
Thanks man. I’ll give it a try later tonight. I really wanted to stay stock CM but hopefully CM will fix this soon. :good:
[Nexus 7 (2013) Android Development] tungdil:
Hi! As of today Glitch Kernel (16/01/2015 - r307) is also available in a CAF version. I just checked it and GPS is working well.

Note: I also tried your recommendation and can confirm GPS is working.
[Nexus 7 (2013) Android Development] lieuliau:
I'm using latest nightly but when I use Max Volume, I hear a lot of distortion. I come back to 4.4.4 and I didn't have audio distortion when max volume.
[Nexus 7 (2013) Android Development] mindmajick:
Anyone know why there have been no nighties since the 15th?

According to the change log there will be themes in the next version!

-> Sent from my mind to your screen
[Nexus 7 (2013) Android Development] VannMann:
It's a task getting the theming integrated, I'm sure. There probably cleaning it up before the next nightly is released.
[Nexus 7 (2013) Android Development] mindmajick:
Oh, I'm sure it's a whole lotta fun for the dev with that task. [emoji12]

I'm just trying to fit in and be an inpatient user lol.
[Nexus 7 (2013) Android Development] klaust58:
The 18th nightly does not work with my Nexus 7². WLAN does not connect and google app stops constantly. I tried first with dirty and then clean flash.

MultiROM, CM12 as second rom.

:confused:
[Nexus 7 (2013) Android Development] lieuliau:
Anyone has this issue or only mine? Thanks!
[Nexus 7 (2013) Android Development] Thebear j koss:
Didn't say hangouts isn't working. SMS is not working, because there is no data. No issue with hangouts, only when attempting SMS.

Thebe?r'$ NeXu$
[Nexus 7 (2013) Android Development] dcdave63:
No, but I did say that Hangouts isn't working.
[Nexus 7 (2013) Android Development] Thebear j koss:
Nope. Better go back and read your original comment. You said you had the same issue as the other user... SMS is not working which is because we don't have data. If hangouts doesn't work for you, i am presuming it is because you are restoring data that is saying ylu have data, when you don't. Best bet is to install Matlog or catlog, open it. Give it SU permissions. Close it. Open hangouts, when it f/c's open matlog or catlog immediately after. Pause it as soon as it starts showing logs. Filter for "babel" save and post the log or send via email to dev.

Thebe?r'$ NeXu$
[Nexus 7 (2013) Android Development] dcdave63:
Done.
[Nexus 7 (2013) Android Development] OhioYJ:
Since the problem is just with SMS, could you not just use Google Voice to send texts? I have not switched to Hangouts yet so maybe Im missing something can you not switch back and forth between Hangouts / Voice?

Serious question too, as Ive been hesitant to try hangouts as I don't want to be trapped if I dont like it. Of course since it apparently it wont work on my tablet that sounds like a deal breaker already.
[Nexus 7 (2013) Android Development] hliew88:
SMS on Hangouts broke on me starting from version 10 (I believe, whichever was released in late July). I switched my SMS back to Google Voice, and it all works fine. I miss MMS capability from Hangouts though, so I would also greatly appreciate if the cause for this could be identified. I basically use my Google Voice number as my primary number now.
[Nexus 7 (2013) Android Development] Thebear j koss:
You can use both. And messenger. And Duo. And spaces. And ally. Google is outta control with their bloated nonsense. But you can have voice and hangouts. Hangouts is a better group messenger than voice, plus it has video chat if that is your thing. It's a newer version of google Talk and is already being replaced by their newer stuff...

Thebe?r'$ NeXu$
[Nexus 7 (2013) Android Development] hliew88:
Yes, that's why it would be great if this SMS in Hangouts bug can be fixed. Having to resort to Google Voice which was last updated in 2013 leaves a ton of features missing (MMS, group SMS, etc.). You can't send SMS/MMS using your GVoice number in Allo or Duo and there appears to be no desire to support that in the future. Google Messenger isn't supported on our Nexus 7's either.

All signs seem to point to Google trying to kill off Google Voice numbers along with Hangouts in a few months...
[Nexus 7 (2013) Android Development] Thebear j koss:
It isn't a bug, you need data to send sms. The nexus 7 flo doesn't have data. You can send messages and videochat, but you can't send sms or mms over wifi. You need a phone # to use sms and mms.

Thebe?r'$ NeXu$
[Nexus 7 (2013) Android Development] hliew88:
You are still misunderstanding the bug we are reporting. The point of having a Google Voice phone number (not a regular cell # as you are talking about) is so that you can call/SMS/MMS with no cell data plan. Since 2013, you could merge Google Voice with Hangouts. SMS and MMS in Hangouts worked before version 10 on this ROM, and continues to work on desktop and other wifi-only devices. So clearly, Hangouts is still supporting Google Voice SMS/MMS on any device, even if it has no regular cell # or data subscription.

So what is it about this ROM that causes Hangouts to crash the moment you start typing an SMS? Is this ROM denying Hangouts a certain permission or something?
[Nexus 7 (2013) Android Development] Thebear j koss:
Not misunderstanding at all. Google needs to verify the # by sending a message to your device, it can't because you have no data on the 7. Verify the # from a different device and try to use it again on the 7. When you installed the ROM all data was cleared, so google it looks like a new device to google. It needs to send a message over data to the device through hangouts. Once the # is verified again, you should be able to send messages from the 7.

Thebe?r'$ NeXu$

---------- Post added at 04:08 PM ---------- Previous post was at 04:06 PM ----------

May also want to check a different gapps package and/or flash a themed hangouts to see if it works... Maybe you are correct, maybe there is just a lib missing.....

Thebe?r'$ NeXu$
[Nexus 7 (2013) Android Development] daman261:
Does anyone have a way to run Pokémon Go?
[Nexus 7 (2013) Android Development] quickdraw86:
Search "magisk", "phh SU", and "suhide".
[Nexus 7 (2013) Android Development] zwliew:
flo will have an official CM 14.1 build soon, courtesy of Simon Shields (forkbomb) :). He took the rebased trees and brought them up to 7.1.
[Nexus 7 (2013) Android Development] htb2050:
That's awesome to hear. I just hope someone will step up to get deb up to speed soon too because all the work is already done. docHD used to but he is busy with angler these days.
[Nexus 7 (2013) Android Development] bbernardini:
Anybody had trouble booting after installing Xposed on today's nightly? Flashed the ROM and GAPPS, rebooted fine. Went back into recovery, flashed Xposed 86 as always, but it just hangs on the opening animation when I reboot.
[Nexus 7 (2013) Android Development] Locke_G:
Did you wipe cache and davlek?
[Nexus 7 (2013) Android Development] TUN_SD:
Me too. Stuck in a loop.

Gesendet von meinem E6653 mit Tapatalk
[Nexus 7 (2013) Android Development] Viggen66:
Can anyone please give me a link to latest cm 13 nightly build? The snapshot of 20 August I receive some pop-ups ads from nothing I guess there's some security flaw somewhere.
[Nexus 7 (2013) Android Development] mochi579:
Do anyone has the idea to re-orient the nav bar in landscape position?
[Nexus 7 (2013) Android Development] Azrael959:
Netflix

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Android Development] skyler13:
is anyone able to watch 1080p or 1080p60 on the youtube app? as i was able to on stock but since moving to custom roms i have been unable to watch 1080p60 on my nexus 7
[Nexus 7 (2013) Android Development] Link_of_Hyrule:
Does it stop the video and but still play the audio on YouTube 60fps videos? Do you use magisk?
[Nexus 7 (2013) Android Development] machbret01:
It happens to me too. I'm on slimrom 6.0 but I can't find a solution.
[Nexus 7 (2013) Android Development] purplepenguin:
Is there a mirror for the last CM13 for flo somewhere? Trying to downgrade from 14.1 if possible
[Nexus 7 (2013) Android Development] quickdraw86:
https://archive.org/download/cmarchive_nighlies
[Nexus 7 (2013) Android Development] bombermanCC:
Hi, could someone confirm which file I should get for CM13 for nexus 7 FLO ? Thank you.
[Nexus 7 (2013) Android Development] quickdraw86:
The last nightly or stable cm13 build, if you can find it around. It's not in the archive I linked earlier, as cm14.1 is the last nightly built for flo by CM. I may have the last cm13s I mentioned, if anyone is interested, I can look when I get home from work.
[Nexus 7 (2013) Android Development] bombermanCC:
If u could link it, i would really appreciate it. Do you know if your version of the CM13 for Nexus 7 FLO supports F2FS?

I just want to go back to marshmallow (preferably not stock) until xposed is out for Nougat. I hate not having control of my hardware.
[Nexus 7 (2013) Android Development] quickdraw86:
Actually, the link I DL from a while back is still live in this thread:

https://xdaforums.com/nexus-7-2013/general/rom-cyanogenmod-14-1-official-nightlies-t3527243

The 12-20-2016 final cm13 snapshot build can be DL from there. I always thought switching roms after f2fs conversion to be a PITA, and never used it much, but, IIRC, CM didn't natively support it, but a custom kernel (glitch, EX) and some changes to fstab are all it would take to get it working.
[Nexus 7 (2013) Android Development] bombermanCC:
Thanks for the link quickdraw86, got the cm-13.0-20161220-SNAPSHOT-ZNH5YAO3XL-flo.zip file.

A thanks for mentioning Glitch kernel, didn't know it existed.. I will readup and try it out. Seems interesting indeed.
[Nexus 7 (2013) Android Development] xtra0581:
No such problem here with 15th nightly...
[Nexus 7 (2013) Android Development] joelalmeidaptg:
I confirm that this issue is happening with the TF300T here in my home. I'm going to try and see if it is a gapps problem.

---------- Post added at 02:40 PM ---------- Previous post was at 01:51 PM ----------

Trying other gapps did not work. Also, it's impossible to go back to 15th release since it makes the tablet enter an apparently infinite bootloop. So ensure you make a backup!
[Nexus 7 (2013) Android Development] xtra0581:
You can surely go back. But have to wipe system partition as well...
[Nexus 7 (2013) Android Development] joelalmeidaptg:
I did. It's no good. It won't boot after its data "touched" the new nightly, in both my tablets.
[Nexus 7 (2013) Android Development] mindmajick:
Is this update working for anyone?

Edit: the January eighteenth update, to be exact.

-> Sent from my mind to your screen
[Nexus 7 (2013) Android Development] Jhall8:
Yes, it's working for me.
[Nexus 7 (2013) Android Development] mindmajick:
+1. I hate when they put the fear to update in me lol. Cleanly upgrade with no issues.

-> Sent from my mind to your screen
[Nexus 7 (2013) Android Development] php5_developer:
I'm on 0115 nightly, I monitored my cpu freqs and my low freq stucks at 1ghz instead of 384 mhz. Even if I restore it to what it was it keeps coming back to 1ghz

Sent from N7 2013
[Nexus 7 (2013) Android Development] boxcar8028:
Flashed nightly January 18th with no problems, smooth and stable. but when trying to install swiftkey keyboard force quit. Cyanogen knows about the problem and should be fixed in next nightly.
[Nexus 7 (2013) Android Development] 78Staff:
0118 dirty flash installed and working here as well... no issues. Well, no new issues :).
[Nexus 7 (2013) Android Development] joelalmeidaptg:
Which gapps are you using?
[Nexus 7 (2013) Android Development] 78Staff:
This one mentioned earlier in the thread... http://xdaforums.com/showpost.php?p=58065806&postcount=32
[Nexus 7 (2013) Android Development] joelalmeidaptg:
I just tried updating my tablet after a data wipe (since it wouldn't boot before) with those same gapps and it did update smoothly. I believe PA gapps messed up something in my data that was somehow preventing Google services to work with the new nightly, stuff that wouldn't go away even if I switched gapps. Oh well, now it's working fine ;)
[Nexus 7 (2013) Android Development] 78Staff:
yeah I normally use pagapps in the past, but lots of reports with issues with 5.0 PA Gapps apparently, so I tried these as [MENTION=3234739]mindmajick[/MENTION] suggested and have not had any issue..
[Nexus 7 (2013) Android Development] php5_developer:
Don't install gapps from play store or apk. Flash pa gapps for lollipop and you should be fine

Sent from N7 2013
[Nexus 7 (2013) Android Development] klaust58:
I tried without gapps - clean install to a second-(multi)rom. WLAN did not work.
[Nexus 7 (2013) Android Development] Badger51:
Where does one send bug reports?
[Nexus 7 (2013) Android Development] dean_fx:
I would say:

https://www.cyanogenmod.org/bugs

When you search for Nexus 7 you are directed to the project page:

https://jira.cyanogenmod.org/browse/CYAN-150?jql=text ~ "nexus 7"
[Nexus 7 (2013) Android Development] JGeZau:
I updated to CM12 from CM11 thru Settings -> About Tablet -> CM Updates (in fact I didn't notice I was updating to CM12, I just selected the latest update).

GAPPS stopped working but that was an easy fix, I just flashed the new Lollipop GAPPS. The real 'problem' I am facing now is that I lost root access :( I tried flashing SuperSU, and also installing from Play Store and is telling me "There is no SU binary installed, and SuperSU cannot install it. There is a problem"

What do I have to do to solve this issue?

Thanks!
[Nexus 7 (2013) Android Development] Hybridnoob:
Root is already there. Just enable developer options and it's in those settings.
[Nexus 7 (2013) Android Development] JGeZau:
So I enabled that option and chose Root Access -> Apps and ADB, rebooted the tablet and Root Checker still says I do not have root. BusyBox also tells me i do not have root access and still getting the same message from SuperSU
[Nexus 7 (2013) Android Development] Hybridnoob:
I can only imagine imagine SuperSU messed something up. I would uninstall that app, then reboot into recovery, wipe system, cache and dalvik (shouldn't affect your data). Then install ROM and gapps. Make a backup first just in case.