yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] crybert:
Same for me! clean install and wifi is still not working. This is the case since 18th january nightly. Before it worked without any problems.

EDIT: Just created a guest network in my FRITZ!Box with WPA-Encryption (TKIP). I can connect to this guest network but not to my normal network which uses WPA2-Encryption. Maybe someone can test this.
[Nexus 7 (2013) Android Development] adamcullen:
black screen

I've flashed the last 3 nightlys and gotten the same result on my nexus 7. Flashed nightly, gapps and wiped cache and dalvic. Device boots, updates apps, goes to run setup and the screen goes black. Top status bar is visible with battery, WiFi, a key and hash (#). That's all that I can see on the screen.

Any clues how to fix?
[Nexus 7 (2013) Android Development] klaust58:
I'm using a FritzBox too!

Curious: After deleting the Nexus-Entry in the FritzBox, it works. But then my 4.4.4-ROM did not connect. Deleting entry, 4.4.4 works, CM12 not.....What's that?

Now, with CM12 i set up static ip and with 4.4.4 i use DHCP. Not a nice solution.

:confused:
[Nexus 7 (2013) Android Development] JGeZau:
This worked. Thanks!
[Nexus 7 (2013) Android Development] boxcar8028:
Just flashed 1.21 smooth and stable. Got center clock back ^^
[Nexus 7 (2013) Android Development] marsaltito:
Try to delete wififorget) connection and try again !?

:)
[Nexus 7 (2013) Android Development] Ellobo24:
We still got issue with the keyboard selection on Nexus 7fhd..i hope it get fix soon!!!! ?
[Nexus 7 (2013) Android Development] boxcar8028:
SwiftKey working for me with nightly 1.21 :cyclops:
[Nexus 7 (2013) Android Development] 78Staff:
1.23 nothing but SystemUI errors :( Anyone else?

Tried both Cyandelta flash and standard wipe and flash, no joy.
[Nexus 7 (2013) Android Development] boxcar8028:
Yeah, same here.
[Nexus 7 (2013) Android Development] klaust58:
Same here. Just flashed back the 21th nightly.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Android Development] Fivesack622:
Same... I also use Cyandelta to update and that was a no go. I tried all kinds of stuff including clean install and nothing worked. It's really cool we got skipped on the last nightly too, but apparently there was a reason and we should have been skipped again. I'm also REALLY impressed that GPS STILL doesn't work without flashing a custom kernel. It's also pretty cool that the guy that started this thread hasn't been back here since his first couple posts. Is this actually an OFFICIAL thread???

But most of all, I am glad to see that CM can handle properly supporting a 1 and a half year old Nexus device. :good:
[Nexus 7 (2013) Android Development] 78Staff:
I'm taking the opportunity to try a few differ roms, Dirty Unicorns for one. I've been a CM10/11 user for quite a while on the S4, but CM12 on Flo is lacking... I realize it's a very new rom but I find myself missing all kinds of things that aren't there yet. I'll give it a while to mature and try again later...

Heck I may even go back to CM11/4.4.4 so I can get my Good 4E running again.
[Nexus 7 (2013) Android Development] Fivesack622:
I'm just frustrated after spending 3 hours trying to make sure I wasn't doing something wrong, not to mention all the hours I spent the last 2 weeks trying to figure out the GPS problem. At least a custom kernel fixed that... I still have my backup of CM11 if I need to roll back and I actually had to use it tonight so I could use my USB OTG (not working in CM12 as well) to get some files I needed while I was in the process of restoring everything. I watch the commits everyday and I watch all the open commits as well. I just don't see a whole lot being done to even attempt to fix the issues on flo and I guess it bothers me and also worries me a little as well. I'm sure it will all get sorted out in the end, but I feel like it should be getting a lot more attention being a Nexus and with the code originally coming straight from Google.

Time will tell I guess....
[Nexus 7 (2013) Android Development] php5_developer:
Is it me or you have battery drain issue too?

Sent from N7 2013
[Nexus 7 (2013) Android Development] jk8260:
Yep same here even tried full clean wipe and still fc circus, bad build :( that's two hours I'll never get back.
[Nexus 7 (2013) Android Development] boxcar8028:
Just flashed 1.24 so far so good. Nice new boot animation.
[Nexus 7 (2013) Android Development] oxplot:
Not so random reboots

I'm getting reboots. It happens after the device boots, goes into lockscreen and the phone sleeps. Less than a minute later, the device reboots. I noticed that if I use the device (ie unlock, open apps), the reboot doesn't happen but as soon as it goes to sleep, the device reboots again. Also, when connected to PC using USB, the device doesn't reboot. The ROM is vanilla 20150124 nightly with no gapps or anything else flashed on top.

Here is the last lines of the /proc/last_kmsg saved after the reboot (full content attached):

[ 16.021118] bq27541_get_psp status: Not charging ret= 0x0181
[ 16.023132] bq27541_get_psp current = -637 mA
[ 16.023254] healthd: battery l=94 v=4111 t=32.6 h=2 st=4 c=0 chg=
[ 16.421630] bcm2079x-i2c 0-0077: 10,91
[ 17.129882] gpio 25 VCM_PD(1)
[ 17.130035] gpio 31 XSHUTDN(1)
[ 17.160736] msm_sensor_config:1422 sensor state 1
[ 17.291717] msm_actuator_config:887 msm_actuator_power_down failed -14
[ 17.325958] msm_sensor_config:1445 sensor state 0
[ 17.510131] gpio 43 CAM_RST(1)
[ 17.569946] mi1040_sensor_match_id +++
[ 17.570678] Sensor id: 0x2481
[ 17.570831] PMIC gpio 11 CAM_VENDOR_1(0)
[ 17.570922] PMIC gpio 10 CAM_VENDOR_0(0)
[ 17.571014] PMIC gpio 24 CAM_LENS(0)
[ 17.571136] Vendor is B
[ 17.571197] mi1040_sensor_match_id ---
[ 18.230163] NOHZ: local_softirq_pending 200
[ 18.230438] NOHZ: local_softirq_pending 200
[ 18.230590] NOHZ: local_softirq_pending 200
[ 18.594024] gpio 25 VCM_PD(1)
[ 18.594482] gpio 31 XSHUTDN(1)
[ 18.621246] msm_sensor_config:1422 sensor state 1
[ 18.867095] msm_actuator_config:887 msm_actuator_power_down failed -14
[ 18.901245] msm_sensor_config:1445 sensor state 0
[ 19.200134] gpio 43 CAM_RST(1)
[ 19.260009] mi1040_sensor_match_id +++
[ 19.260894] Sensor id: 0x2481
[ 19.261077] PMIC gpio 11 CAM_VENDOR_1(0)
[ 19.261199] PMIC gpio 10 CAM_VENDOR_0(0)
[ 19.261383] PMIC gpio 24 CAM_LENS(0)
[ 19.261505] Vendor is B
[ 19.261627] mi1040_sensor_match_id ---
[ 32.846374] dsps_wdog_bite_irq
[ 32.846710] dsps_log_sfr: DSPS failure: SFR Init: wdog or kernel error suspected.
[ 32.846740] Resetting DSPS
[ 32.847442] subsys-restart: subsystem_restart_dev(): Restart sequence requested for dsps, restart_level = 3.
[ 32.848236] subsys-restart: subsystem_shutdown(): [eab60440]: Shutting down dsps

No errors detected
Boot info:
Last boot reason: Watchdog

Looking at the last line, it's obvious that the watchdog timer is timing out, causing a reset. I didn't know watchdogs are enabled on a mobile device whose CPU goes into sleep for extended length of time and this seems to be what's happening.

I've found a bug report and a patch that is a workaround for CM11. The patch is however already in CM12 and it's obviously not helping.
[Nexus 7 (2013) Android Development] TheAvngrZ:
Check in performance settings with lwest rate you have set... it is the same probem for me too its set at 1 GHz
[Nexus 7 (2013) Android Development] klaust58:
Yes. 0124 works fine.

You have a nice boot animation? Where did you get them? Mine is extremely ugly! :eek:
[Nexus 7 (2013) Android Development] TheAvngrZ:
Think so? :D its a bit boring :(

---------- Post added at 10:42 AM ---------- Previous post was at 10:42 AM ----------

Oh yes!

Its not on the compleat screen... on each side are missing 0,5 cm :D
[Nexus 7 (2013) Android Development] php5_developer:
You know this kernel is somehow wired. Go to performance and do not touch your phone fora few seconds and it drops to 384mhz. Once you touch the screen it goes to 1ghz. Other kernel handle this very differently.

Sometimes it becomes constantly awake and I have to restart. It's not suitable for daily use yet. I'm going back to CleanRom for now.

Sent from N7 2013
[Nexus 7 (2013) Android Development] jk8260:
Same here much better than yesterday, CM nightlies are auto built so can get a rotten apple every once in awhile especially this early in the game.
[Nexus 7 (2013) Android Development] TheAvngrZ:
Haha what can be more worse than the built yesterday?! :D

So far so good now... Im very surprised how cm will inject all the other features... :)

Waiting for the slide up from home button gestures... Them was in cm 11 a very good method to make the screen black.
[Nexus 7 (2013) Android Development] boxcar8028:
yeah, it’s too bright :cyclops:
[Nexus 7 (2013) Android Development] jk8260:
I'm sorry but imho the new CM12 boot loader animation is a hideous mess, our cat will not come out from under the couch now... :eek:

...check it out here...

https://www.youtube.com/watch?v=3zOLt21ndeA

or here

http://gfycat.com/FinishedDentalIslandwhistler
[Nexus 7 (2013) Android Development] khaytsus:
..............so?
[Nexus 7 (2013) Android Development] jk8260:
It's the AT&T boot animation with the cyanogen face, at that brightness will burn a few % battery just to boot.
[Nexus 7 (2013) Android Development] 78Staff:
yeah I like the older one much better, so reverted to it instead of the white blizzard version...
[Nexus 7 (2013) Android Development] Fivesack622:
"White Blizzard" literally made me laugh out loud. Thank you.

On a side note, I'm just curious. Has anyone who thinks they have GPS working actually tested it with GPS Test Plus or something similar and are you using strictly CM12 nightlies with no custom kernels, hacks or anything that could possibly alter a system file to make it work?

I have tried a clean flash with full data wipe and still have no GPS. I didn't even install a GApps package in that test, which shouldn't make a difference anyways because GPS should be working without any Google app of any sort installed..

Just trying to see if we can pinpoint something causing the problem since the 10-15 of us in this thread are apparently our own support. I really suspect it's kernel related as both Sabermod and Glitch kernel fixed the problem instantly, but who knows, I am not a developer...

If GPS is truly working for someone who has a pure CM12 installed with no mods of any kind and it can be physically proven, please speak up. I really want to know what I am doing wrong.

Thank you.
[Nexus 7 (2013) Android Development] TheAvngrZ:
I think android 5.0 not very good with the colors... something is grey, something withe, some letters are green and so on... with JB and KK there where the same colors and letters everywhere! I liked this very very much :D
[Nexus 7 (2013) Android Development] klaust58:
Stock-CM12 GPS: no Chance

CM12 with Franco/Sabermod Kernel: GPS-fix after a few seconds.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Android Development] TheAvngrZ:
for me is gps working with no mods installed.... works well also with smart lock and maps...
[Nexus 7 (2013) Android Development] gatebil:
Same here, GPS Test App cant get any GPS Fix but Maps working fine.
[Nexus 7 (2013) Android Development] khaytsus:
GPS is not working then. Maps is just showing wifi location.
[Nexus 7 (2013) Android Development] mslatter:
I had the same issue... No GPS on a clean stock install. Had to go back to another ROM quickly as I thought maybe it was a bad install and GPS is crucial for what I use the N7 for. Wasn't even going to mention it until I saw your post...
[Nexus 7 (2013) Android Development] TheAvngrZ:
sure?
[Nexus 7 (2013) Android Development] khaytsus:
If GPS apps are showing no fix, but Maps is showing a "fix", yes, I'm quite sure.
[Nexus 7 (2013) Android Development] :
If you would like to test it, you could change the Location Mode to "Device only". If Maps is still working, you're GPS is working.
[Nexus 7 (2013) Android Development] 78Staff:
Same, fine with Franco/SaberMod - but that doesn't help you much I suppose. On the next nightly I'll test on cm kernel b4 flashing sabermod...but I suspect I'll be the same as you and [MENTION=4478505]klaust58[/MENTION]
[Nexus 7 (2013) Android Development] boxcar8028:
It looks like we got pasted up tonight.

http://download.cyanogenmod.org/
[Nexus 7 (2013) Android Development] Madawcisrich:
hi does anyone know where to enable advance reboot in the ROM please?

It is annoying to reboot manually to recovery each time. Thank you very much
[Nexus 7 (2013) Android Development] :
Developer Option->Advanced Reboot and in FN you can customise it.
[Nexus 7 (2013) Android Development] mslatter:
Or install Quick Boot - you can set widgets on your screen so one tap takes you there.... I used to use the widgets but got tired of 'accidentally' touching one of them.... so it's a two tap process for me now.
[Nexus 7 (2013) Android Development] ianjojo:
updates

since the 24th, my CM isn't seeing any new updates.. i installed 25 by hand, any idea how to fix this?
[Nexus 7 (2013) Android Development] mslatter:
That has happened to me too. Not sure how to ensure it doesn't happen again, but I backed up my device after manually flashing the new ROM, and then went back into CyanDelta and selected the newly installed ROM as the one to flash, and flashed it again....so it would take note of the current one and look for new. Again, it's not really a fix, but at least got the process working again for me.....
[Nexus 7 (2013) Android Development] lapocompris:
I got a reboot during sleep yesterday, but not today after flashing elementalx kernel.
[Nexus 7 (2013) Android Development] RobbieL811:
Can someone in here tell me what vendor repos are needed to build CM 12 for Flo and Deb? I have vendor_asus & vendor_broadcom, but I don't see any vendor_qcom. I come from background of SlimRoms, and those are the three vendor repos that are needed to build Slim. Just curious if it is different than Slim? Do I need vendor_qcom?
[Nexus 7 (2013) Android Development] chrisluffy25:
Theres an error when you try to update into latest nightly.
[Nexus 7 (2013) Android Development] klaust58:
No. No problems here ☺

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Android Development] webyrd:
I could not download the 1/27 nightly, no unusual problems with 1/26
[Nexus 7 (2013) Android Development] Madawcisrich:
Hi guys, is there any solution to update the rom via some Cyangenmod software instead of going to their siteweb and update manually? It seems that I saw it once in the device, but I cannot find it again.

Thank you very much
[Nexus 7 (2013) Android Development] mindmajick:
Try cyandelta in the play store.
[Nexus 7 (2013) Android Development] lapocompris:
Wait a little bit before jumping on the latest build. I just downloaded 28 without any problem.
[Nexus 7 (2013) Android Development] soccermon15:
Settings > About Tablet > CyanogenMod Updates
[Nexus 7 (2013) Android Development] Krayvon:
cyandelta is the way to go.

it only downloads the updates and not the whole freaking rom. and its free. give it a try.

on another note, i know no one wants to mention it because "misc" drain is not a drain nor a bug, but what the flip is it? lol

to add to that, ever since LP, standby time is no where close to KK. i would leave my tablet untouched and it would last for a week. now i get 2-3 days tops.

anyone got a way to improve deep sleep? and don't say greenify :P
[Nexus 7 (2013) Android Development] boxcar8028:
Not so sure about nightly 1.30 it should be 245mb. but when I'm downloading its only 125mb. I think I'll wait for the next one.

edit: just rechecked and now the download is a full 245mb. so i downloaded, flashed and all seems okay. bluetooth is better but still no GPS.
[Nexus 7 (2013) Android Development] xbs:
In 01/30 nightly the nav buttons are off center in landscape and don't work.

Anynone seeing this?
[Nexus 7 (2013) Android Development] kamistral:
Yes, I'm on deb (with LTE ) and have the same problem since -20150130:

http://xdaforums.com/showthread.php?p=58532372
[Nexus 7 (2013) Android Development] TheAvngrZ:
http://review.cyanogenmod.org/#/c/87240/

boot animation gets dark flavour in next nightly
[Nexus 7 (2013) Android Development] fluther:
Yup, me too.

There were lots of navbar merges in 01/30 (including navbar left/right text navigation!), and they work great in portrait, but landscape is busted.
[Nexus 7 (2013) Android Development] jk8260:
God I hope so !!!
[Nexus 7 (2013) Android Development] jasonftfw:
Tried flashing 130 and it goes through, but then the boot animation is slow at start and then when the setup comes up, constant force close windows for all sorts of google apps etc.

I even tried without flashing gapps too and it still did this. Any ideas whats going on?

I'm pretty sure I'm doing this right considering I've put CM12 on my other devices with no issue.

using TWRP, wipe (factory reset) and then I flash CM. thats it. FYI this is my first install of CM on this device.

Reverting back to rooted stock via backup for now.
[Nexus 7 (2013) Android Development] TheAvngrZ:
You had bad luck...

The nightly you flashed is a corrupt zip!

Try to flash a other nightly :) tomorrow or from yesterday :)
[Nexus 7 (2013) Android Development] jk8260:
I'd wait until the new version tonight the last few days have been garbage.
[Nexus 7 (2013) Android Development] klaust58:
Everything was OK with the last zips.

The landscape-navbar-problem has been fixed with 0131.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Android Development] lapocompris:
When I dirty flash a new nightly my Nexus 7 is always wiped out of everything including Gapps, whereas my LG G3 keeps everything as intended. What's happening with my Nexus?
[Nexus 7 (2013) Android Development] TheAvngrZ:
Nope.

And about the little: The Multitasking Bug is fixed!in next nighly :)
[Nexus 7 (2013) Android Development] xbs:
Nav bar landscape issue fixed in 01/31 nightly.
[Nexus 7 (2013) Android Development] fluther:
Very strange issue here.

My flo is encrypted, and I'm using the latest TWRP, which has borked encryption support on flo, so I use adb sideload from my laptop to flash cm12 nightlies, which works fine. However, now the tablet boots, even from cold, directly to the ordinary lock screen, without going through the pin-entry decryption screen.

The device still reports itself as encrypted, and TWRP still can't read the encrypted partitions, but it now boots straight into a usable state. Anyone any ideas what gives?
[Nexus 7 (2013) Android Development] TheAvngrZ:
make a factory reset, flash it via twrp and then do your PIN stuff :D I think there went just something wrong :)
[Nexus 7 (2013) Android Development] fluther:
Thanks, but don't want to fix it just yet, what I want to know is how it has happened. Am I right in thinking that devices that come encrypted out of the box like the n6 and n9 don't have the decryption screen during boot? I'm wondering if having setup my install using adb sideload rather than flashing from recovery it was set up to encrypt using a default password on first boot like those later devices.

Anyone know how I could check?

Update: well that's interesting. I downloaded Cryptfs Password from the play store, and flashed supersu so I could use it. It worked perfectly, and I didn't need to put in my current pin to change the encryption password, which indicates to me that yes, installing these cm12 nightlies via sideload streaming from a mac rather than by flashing a zip on the sdcard automatically enabled the same kind of encryption settings as one finds on the N6 and N9.

I've changed the pwd now, so I have the decryption screen at boot.
[Nexus 7 (2013) Android Development] jasonftfw:
1/28 went in with no issue. Up to 1/30 now, no nav bar issues for me, but my old nexus 7 had the issue.
[Nexus 7 (2013) Android Development] fluther:
Are sounds-on-screen-touch broken for anyone else on 02/02? I can hear a tiny, sad little noise, but not the proper tapping noise.
[Nexus 7 (2013) Android Development] caolfin:
deep sleep = turned off ??

Folks

On 28/01 and 03/02 my flo is going to sleep properly but then can only be turned on by (very) long press of power button !

It then goes through the whole boot sequence

Does anyone know why ?
[Nexus 7 (2013) Android Development] poondog:
I was on 27/1 and I didn't have this issue at all

Updated to 4/2 now, anyone else got sysui FC on boot?
[Nexus 7 (2013) Android Development] mindmajick:
No idea why it's going into the "sleep of death". It's been doing that to me since the first release. Elementalx kernel fixed it for me.
[Nexus 7 (2013) Android Development] jasonftfw:
Just updated to 2/4 build and lock screen isn't very responsive. If I swipe a few times it'll finally unlock and then everything is good and responding. Anyone else getting that?
[Galaxy S III Q&A, Help & Troubleshooting] Zordak7:
Is there a way to save the settings of an specific app (Google Play Services for example, I've disabled a lot of services and receivers and stuff, or Go Locker themes, etc.), and even better, save the settings of several apps?

Thanks!
[Galaxy S III Q&A, Help & Troubleshooting] Zordak7:
Plz
[Galaxy S III Q&A, Help & Troubleshooting] Zordak7:
Pliz :)
[Galaxy S III Q&A, Help & Troubleshooting] Zordak7:
Plz somebody give me some help here. pls pls.

Saludos!
[Samsung Gear S] destro005:
can't pair with note edge gear Manger just keeps loading pairing comes up the says gear couldn't connect see manual but,the manual says nothing about fixing the problem anyone have any suggestions or help thanks if so
[JASJAR, XDA Exec, MDA Pro General] manu407:
Even when I untick 'On Battery power Turn off baclight if device is not used for ... Time', my Jasjar baclight goes off in 2 minutes. And, if I set this to 5 minutes still my Jasjar backlight goes off in 2 minutes. Also, when I choose to 'turn on backlight when a button is pressed or the screen is tapped, it doesnot turn on any button or screen tap. I can turn it on by power button or Call reject red button. Any registry hacks/ Am I missing something? I would like my backlight always on untill I press power button. Also is there any hack to turn on power/ backlight automatically when I open the lid?
[JASJAR, XDA Exec, MDA Pro General] gibhenry:
Maybe a soft reset (fixes lots of weird problems like this). Cheers,
[JASJAR, XDA Exec, MDA Pro General] starik:
yeah and if soft reset doesnt help, do backup, sync with PC and do hard reset.
[Note Edge Q&A, Help & Troubleshooting] cvaria:
Does anyone have full mirror link working on their edge/ note 4?
[Note Edge Q&A, Help & Troubleshooting] iondokk:
I have full mirror link on my jvc head unit

Galaxy Edge!
[Note Edge Q&A, Help & Troubleshooting] troycarpenter:
How did you get it to work? I have tried it on my Pioneer model, but I don't get anything on the HU. The phone says it's in Mirrorlink mode, but I guess I don't have any apps that support it. The Pioneer version called AppRadio One works, which I now think piggybacks Mirrorlink, but it only works with one app currently (AppRadio Live).

Are there any special apps needed on the Edge beyond the built-in MirrorLink support? Is there a special launcher that gets mirrored on the HU?
[Note Edge Q&A, Help & Troubleshooting] iondokk:
This is my head unit http://mobile.jvc.com/product.jsp?modelId=MODL029337&pathId=133&page=1

And this is the only app required to run it. https://play.google.com/store/apps/details?id=com.jvckenwood.HID_ThinClient.JVC

On the Samsung phones you also have to have the following MHL adapter with the Samsung adapter for it to work correctly http://www.bestbuy.com/site/rocketfish-mhl-hdtv-adapter-black/6295102.p?id=1218726390911

One or all of these could be your issue....:cool:
[Note Edge Q&A, Help & Troubleshooting] troycarpenter:
Ok, I see. Your HU has HDMI input. I'm trying to figure out how this works over USB only, not MHL/HDMI.