yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) LTE Android Development] smakme7757:
As far as i know it should already be available in the latest nightly. But I havn't tested it as I built my own.

If you want you can try my own build. It's a fresh compile with the latest code as of 7 hours ago.

ROM

http://sourcenix.com/downloads/CM-20150613-NIGHTLY-SOURCENIX-deb.zip

SHA256 Hash of ROM

http://sourcenix.com/downloads/CM-20150613-NIGHTLY-SOURCENIX-deb.zip-SHA256.txt
[Nexus 7 (2013) LTE Android Development] Tahvok:
I saw that the fix was commited to the latest nightly, so I flashed it.

Data is working fine now!

Thanks for the great work again!
[Nexus 7 (2013) LTE Android Development] smakme7757:
That's great. Glad you're up and running with data again.

It was really nice getting is all working again. There was also a few other small bugs that were ironed out too.

ciwrl was the brains behind the fix, so most of the credit goes to him :)
[Nexus 7 (2013) LTE Android Development] michael.schefczyk:
Encryption

Dear All,

It is great that LTE now works without tricks (i.e., without changing selinux settings). The only isssue I can find with the June 17 CM12.1 nightly is after encrypting the device. While it is possible to update the encrypted device with tricks (adb shell, mount -t tmpfs none /data, mkdir media, exit shell, adb push to path /data/media/update.zip, flash update.zip), unlocking the encrypted device after a reboot is more difficult. There is only a window of a few seconds for entering the password. After that time has elapsed, the password field is covered by a transparent overlay showing the home screen / clock. While the password field remains visible then, it is not possible to type characters there anymore. The only escape seems to be to reboot and type more quickly next time.

Does someone know how to work around that issue other than typing quickly?

Regards,

Michael
[Nexus 7 (2013) LTE Android Development] smakme7757:
I experienced the same thing last night. Indeed a reboot and typing more quickly is the answer.

I have no better work around as of now unfortunately.
[Nexus 7 (2013) LTE Android Development] jeffsrawr:
Tried 5.1 when it first was available and kept having system memory errors and google services issues. I decided to just go back to 5.0.2. Today i decided to try out the newest nightly (7-13-2015) and it works perfectly. No system memory problems and data lte works without reboot trick finally. Great job everyone who has put their time into working out the issues with this rom. Hopefully android M is a smoother transition.

I dirty flashed from 5.0.2 no problems just installed gapps lp 511
[Nexus 7 (2013) LTE Android Development] Methisfaction:
Can i use this rom for my In Car Dash installation?

Does it support USB OTG with charging Option?
[Nexus 7 (2013) LTE Android Development] Intruder_a6:
The newest version (and the others too) have a bug with APP Android Assistant. This application isn't working properly, because when I use it to clean the applications and memory, it can't clean nothing.
[Nexus 7 (2013) LTE Android Development] nemeblist:
Compatible with elementalX ??
[Nexus 7 (2013) LTE Android Development] pepez05:
I have a question. I'm one CM 12.1 (last build of 13/09) and i'm wondering if i want return back to official Android Lollipop it's posssible to just flash the factory image (avaible on https://developers.google.com/android/nexus/images) in CMW no ?

Thanks and sorry for my english
[Nexus 7 (2013) LTE Android Development] nemeblist:
Nope, flash it with toolkit or with flash-all.bat inserted in factory image
[Nexus 7 (2013) LTE Android Development] pepez05:
Ok thanks ;)
[Nexus 7 (2013) LTE Android Development] NoN1979:
Maybe usefull for anyone unofficial CM13 nightly https://yadi.sk/d/_C9zctngk7CZi
[Nexus 7 (2013) LTE Android Development] kamistral:
Official CM13 - seems now everything working

As I don't find a CM13 thread I post this information here, could be helpful for some:

I dirty flashed yesterday cm-13.0-20151126-NIGHTLY-deb.zip on my encrypted device which was running cm-12.1-20151114-NIGHTLY-deb.zip before - and since today's update (cm-13.0-20151127-NIGHTLY-deb.zip) even LTE is working :) (also both cameras, Wifi, BT)

As the way wasn't very easy I describe my steps to get it running - 3 notes before:

1. Could be that now, since cm-13.0-20151127-NIGHTLY-deb.zip, LTE works right out of the box.

2. It could be that the step wiping the app data could also be done earlier so you don't need 2 reboots.

3. You need to know how to use adb as there is currently a bug which causes phone FC's. I'm not responsible if you damage your Nexus or whatever.

Steps:

- Download Cyanogenmod 13.0 from https://download.cyanogenmod.org/?device=deb

- Download GApps (ARM/6.0/nano - you can try other versions surely too) from http://opengapps.org/

- Reboot into Recovery, Wipe->Advanced Wipe-> select system, data, dalvik-cache, wipe these three partitions.

- Still in recovery install the downloaded CM and GApps.

- Reboot

- In case of "com.android.phone has stopped"-messages use adb to remove two data directories including content: http://android.stackexchange.com/a/129946

As mentioned after that I had yesterday everything working except LTE/3G/2G, today I dirty flashed cm-13.0-20151127-NIGHTLY-deb.zip (wipe cache/dalvik-cache) and now LTE/3G/2G works too :)
[Nexus 7 (2013) LTE Android Development] Intruder_a6:
I had problems with the automatic update for CM 13.0 and after ...

I made an big mistake. In recorvery mode I wiped system, data and dalvik-cache, but before reboot I forgot to install CM and GApps. And now my Nexus 7 stay frozen in screen "Google" with padlock. Is it possible to fix this BIG mistake ?
[Nexus 7 (2013) LTE Android Development] kamistral:
Boot to recovery with key combination (not sure, just google it, I guess volume down+power) and flash with "adb sideload CM-....zip" with USB connection from a laptop/computer.

You could also copy the Rom file to the tablet and flash it then.
[Nexus 7 (2013) LTE Android Development] Intruder_a6:
Thank you! I was in panic. My Nexus 7 is alive again.
[Nexus 7 (2013) LTE Android Development] nFiniti:
All 5.1.1 Roms deleted from CM's Servers? Was looking for LMY48X since its what I need for my build but now cannot download any CM12.1 Roms. Luckilly Euphoria is avail. I have the newest CM12.1, but its LMY48Y
[Nexus 7 (2013) LTE Android Development] rmkilc:
From the flo factory image.
[Nexus 7 (2013) LTE Android Development] bongster:
After I installed the newest twrp my baseband is gone again. :(

I don't get it...
[Nexus 7 (2013) LTE Android Development] pompatello:
Posted by mistake

But since I'm here, anybody had any luck installing the gapps stock package? It always tells me there's not enough ROM space left. The other packages aren't as good, lots of apps I don't want on a nexus
[Nexus 7 (2013) LTE Android Development] clonato:
Same To Me
[Nexus 7 (2013) LTE Android Development] clonato:
Hi

does someone have tested if GPS work?
[Nexus 7 (2013) LTE Android Development] stgeorge88:
like a charm.

attached result is from inside a condo by the window
[Nexus 7 (2013) LTE Android Development] Hikikomorikruge:
I had the same issue but a full device wipe (including sdcard) fixed it. I used the latest gapps package - BETA12
[Nexus 7 (2013) LTE Android Development] djeddieone:
Where can I find the 4.4.4 stock radio?
[Nexus 7 (2013) LTE Android Development] pompatello:
Tried that but nothing changed. Really weird as the system partition as shown on titanium backup is around 1GB, which should be more than enough for all the stock gapps.
[Nexus 7 (2013) LTE Android Development] jffonseca10:
I had the same problem, some how the stock gapps are too big for the partition (?). What i did i pasted this gapps-config.txt (read below) file in the same gapps directory, so the installation would skip install those apps listed and still remove all the AOSP apps. Later on you can download the skipped apps from play store.

File Name: gapps-config.txt

Content:

Docs

Drive

Earth

Keep

Movies

NewsStand

NewsWidget

Sheets

Slides

Sunbeam

---------- Post added at 09:12 PM ---------- Previous post was at 08:57 PM ----------

in the stock image, or download it from here:

http://goo.gl/tykbM4
[Nexus 7 (2013) LTE Android Development] pompatello:
Yeah I figured it out in the end reading the gapps thread properly.

Anyone having issues activating cellular service? It gets stuck there forever upon booting the rom the first time so I ended up skipping it. Is the a way to bring it back?
[Nexus 7 (2013) LTE Android Development] kamistral:
bootloader unknown / SIM card not working solution

My baseband version was also for 2 days "unknown", tried everything in this thread and some more, and the only way I got LTE/SIM card working was:

flash 4.4.4 stock (razorg-ktu84p flash-all.sh/bat) - this wipes the device - all data lost!

boot stock until network works (no need to setup)

reboot into bootloader and flash trwp 2.8.2.2 (fastboot flash recovery ...)

transfer CM and GApps in recovery over MTP, flash both then dalvik-cache&data-wipe

done - right after boot I already got a signal :)

Perhaps there is a easier way, but as said the other posted solutions didn't work for me.

Edit/update: With that recovery version decrypting data in recovery is possible when setting PIN or password encryption. Didn't try it since these steps, but will do later today or tomorrow and report back if there are problems with encryption ;)

Background why the baseband problem could happened: I was directly coming from unlocking bootloader, flashing recovery, data/cache wipe, flashing CM/GApps - perhaps its needed to flash one time a stock image or something?

Was completely wrong - with right GApps it works encrypted too, had the wrong installed :( Sorry for the confusion.
[Nexus 7 (2013) LTE Android Development] rmkilc:
So no system wipe?
[Nexus 7 (2013) LTE Android Development] kamistral:
Yes, I didn't wipe system manually. Surely during flashing Stock it got wiped...

Just looked a few seconds into the CM updater-script, seems it backups some files and needs mounted /data-partition, which wasn't working for me during the first tries - that's more alike to be the problem :) (as I'm no Android coder please correct me if I'm wrong)
[Nexus 7 (2013) LTE Android Development] bongster:
I have found another workaround I guess.

Rebooting into the bootloader and restart it works. After that my baseband is back. I will wait with a full wipe till Google decide to release a factory image for our device.
[Nexus 7 (2013) LTE Android Development] kamistral:
Yes thats one of the things I've tried for 2 days (including waiting for hours as some said it takes some time), but didn't work for me :/ Guess my mistake was flashing CM when /data wasn't mounted in recovery, as it seems a working /system-partion and rw-mounted data-partition is needed for flashing CM. Still don't know how that happened exactly.
[Nexus 7 (2013) LTE Android Development] koron393:
Hello.

I thought unknown baseband issue and no gps issue are same problem. Perhaps I'ts related to SELinux permisson probrem.

See dmesg and logcat.

Kickstart and sensors are denied by SELinux permisson.

Set SELinux to Permissive

or

Correct SEPolicy and rebuilt the CM

will fix it.

<4>[ 9.992706] type=1400 audit(1421575969.665:21): avc: denied { dac_override } for pid=329 comm="chmod" capability=1 scontext=u:r:kickstart:s0 tcontext=u:r:kickstart:s0 tclass=capability permissive=0

<4>[ 9.996704] type=1400 audit(1421575969.665:22): avc: denied { dac_read_search } for pid=329 comm="chmod" capability=2 scontext=u:r:kickstart:s0 tcontext=u:r:kickstart:s0 tclass=capability permissive=0

<4>[ 9.997131] type=1400 audit(1421575969.665:23): avc: denied { dac_override } for pid=329 comm="chmod" capability=1 scontext=u:r:kickstart:s0 tcontext=u:r:kickstart:s0 tclass=capability permissive=0

<4>[ 84.998596] type=1400 audit(1421576044.668:125): avc: denied { getattr } for pid=1101 comm="vold" path="/persist" dev="mmcblk0p4" ino=2 scontext=u:r:vold:s0 tcontext=u:object_r:persist_file:s0 tclass=dir permissive=0

<6>[ 4.914459] SELinux: Context u:object_r:sensors_persist_file:s0 is not valid (left unmapped).
[Nexus 7 (2013) LTE Android Development] clonato:
i did it and, for me, it works

now i can use GPS and Mobile Data.
[Nexus 7 (2013) LTE Android Development] donb1:
I flashed stock radio and simple gaps to get it working,all sweet now.
[Nexus 7 (2013) LTE Android Development] kamistral:
Was completely wrong - with right GApps it works encrypted too, had the wrong installed :( Sorry for the confusion.

I guess I found why I had to reset my N7 this hard way to get LTE working: seems that when using encryption, baseband version gets back to "unknown" and the SIM card is not detected :(

Tried all your methods (rebooting to bootloader, rebooting, waiting, flashing baseband and everything fresh, wiping dalvik&cache, ...) - none worked. Anybody else using encryption on these nightlies with working LTE? Btw, I use a single SIM card which is locked to 3G, but I guess thats not the problem as it works perfectly when not using encryption.
[Nexus 7 (2013) LTE Android Development] niko1983:
Got mobile data!!!

For me was a mind trip, going crazy but today FINALLY I got it working... :D

What I've done to get it working for me:

1) Flashed CM11 (I didn't care what version) + Gapps KK

2) complitely booted, set it up and checked for the update

3) installed the update through CM Updater and no gapps but still LTE connectivity

4) rebooted to recovery, sideloaded the stock android gapps for Lollipop and... yes! Got it!

Hope to help...
[Nexus 7 (2013) LTE Android Development] devarshi:
On 1/13 mobile data worked after I rebooted in airplane mode. I'm not updating to a new nightly until this problem is fixed, don't want it getting screwed up again!
[Nexus 7 (2013) LTE Android Development] derekedw:
Boot loader reboot works for me now but damn... That was annoying... Hopefully fixed soon. Anyone know if it's reported?
[Nexus 7 (2013) LTE Android Development] kamistral:
After updateing to 2015-01-19 i had no LTE/networking and "bootloader: unknown" again, a few reboots (also to bootloader) and waiting helped.

Updating to 2015-01-20 didn't work, as System UI is crashing during entering the decryption password :( Back to 2015-01-19...
[Nexus 7 (2013) LTE Android Development] ddaniel51:
Bad 20

Updating to -20 causes UI crash. Back to -19.
[Nexus 7 (2013) LTE Android Development] vArrow:
No problems so far with todays nightly (20/01/2015).
[Nexus 7 (2013) LTE Android Development] kamistral:
Do you encrypt your device?

And did you update from 19/01/2015 or earlier, or wipe?
[Nexus 7 (2013) LTE Android Development] vArrow:
No encryption, just updated from 18/01.
[Nexus 7 (2013) LTE Android Development] unicorn.mod:
After the upgrade to - 20, first got the error UI. Pressed close. Sent a bug report and Android booted ... until everything is working properly. It was possible to connect a keyboard SwiftKey, falling out before the upgrade error. No encryption. Sorry for my English.
[Nexus 7 (2013) LTE Android Development] McNizi:
Just flashed 20 nightly and then reflashed supersu and official lollipop gapps

Cellular is now here, baseband visible, gps working !
[Nexus 7 (2013) LTE Android Development] smartchip:
My local LTE network (Singapore) is 1,800MHz. LTE is not connecting for me, getting only 3G. It seems the CM12 ROM is using baseband G00_2.37.0_1024 ... Will anyone be able to update the baseband to the latest H00_2.42.0_1204?
[Nexus 7 (2013) LTE Android Development] TheBKBurger:
Anyone have issues on AT&T with data slow to enable? If I toggle between WiFi and Mobile Data, mobile data take about 5 min to start working.
[Nexus 7 (2013) LTE Android Development] rmkilc:
I am still not able to get working data. It appears everyone's method is different. Does anyone know a reliable method that works every time?
[Nexus 7 (2013) LTE Android Development] rockingondrums:
You and me both. It seems there's not one absolute way, but that may be because not everyone had the same fault prior to getting it working. I'll just keep updating the nightlies until it works.
[Nexus 7 (2013) LTE Android Development] Sardus87:
After updating to new nightly (20150123), i have continues System UI fc problems (every second). Anyone get same problem?

---------- Post added at 11:26 ---------- Previous post was at 10:46 ----------

Even a new flash with device full wiped present a system ui problem.

With the 20150121 nightly all seems to be ok
[Nexus 7 (2013) LTE Android Development] Fablito83:
Same problem here.
[Nexus 7 (2013) LTE Android Development] logitechor:
Me too. Used back up to restore. Could not figure out why. So restore.
[Nexus 7 (2013) LTE Android Development] vodopadek:
i have the same problem :( im back to early version
[Nexus 7 (2013) LTE Android Development] rockingondrums:
Come on CM, let's get that data working!
[Nexus 7 (2013) LTE Android Development] koron393:
http://xdaforums.com/showpost.php?p=58387570&postcount=17
[Nexus 7 (2013) LTE Android Development] felixjai:
My mobile data is working again! Yay! thanks for the fix!
[Nexus 7 (2013) LTE Android Development] LP6:
Got my mobile data working with this, thanks. But I'm missing WiFi. It hangs on "Turning Wi-Fi on...".
[Nexus 7 (2013) LTE Android Development] kamistral:
New 20150125 works for me again, no systemui fc's (neither during entering decryption password, nor later when CM is fully booted) :)

Coming from 20150121, I updated flashing 20150125, latest PA Gapps beta and the mod_bootcmd_selinux_permissive.zip everything works for me (Wifi and LTE) :) Great work!

(tried without the selinux_permissive also, but then LTE was missing)
[Nexus 7 (2013) LTE Android Development] HowardZ:
The following works for me with the" Turning Wi-Fi on... " problem :

Make sure data and Bluetooth are both enabled.

Data enabled is not found in cm12 settings so I use powertoggles app (it's nice for turning on and off WiFi, hotspot, GPS, muting audio, autobrightness, etc in one widget)

Then reboot.

Might have to turn on WiFi after the reboot.

After WiFi works, reboot a few times to make sure WiFi turns on reliably.

This problem happens on my S4 after flashing every single cm12 nightly, but rarely occurs on my nexus 7 lte tablet.

Hope this helps.

P.S. When the mobile radio will not work on the tablet, I do the following

Remove sim card

Insert sim card

Do a full reboot (not the soft reboot)

Go into settings and try to auto select my cell service provider - t-mobile
[Nexus 7 (2013) LTE Android Development] LP6:
Thank you for the tip, but unfortunately this didn't help.
[Nexus 7 (2013) LTE Android Development] HowardZ:
You might want to flash the latest stock Google binary to get the latest radio and other firmware. Maybe it will help.

Remember it will wipe the internal SD card, so copy your latest nandroid backup and other SD card content to a pc before you do this.

I usually flash every new Google binary when it comes out to have the latest bootloader and radio firmware in case they might have changed. Version lte keeps getting faster, but only if one uses the latest radio / modem.

On my s4 phone, which radio and non-hlos is flashed seems to affect the WiFi because cm12 is enforced and not permissive anymore.

PS I'm no expert in this. Just making suggestions.

Regards

Howard
[Nexus 7 (2013) LTE Android Development] LP6:
Thank you. I just got all the apps and data installed on my tablet...

So I would prefer just updating the radio firmware if it is possible and the solution for this problem.
[Nexus 7 (2013) LTE Android Development] Christian72D:
for those people with the "System UI" error:

Link xda
[Nexus 7 (2013) LTE Android Development] sabzake:
This is first time i install costum rom on my nexus. How can i use my google account ? I do not see any option on " Accounts " for adding my google aacount .
[Nexus 7 (2013) LTE Android Development] HowardZ:
Yes, the Google Image is flashed onto the tablet by typing flashall.Bat from a cmd window on the pc,

You can first edit the flashall.Bat file.

For example the "-w" means to wipe data.

I often restore my nandroid backup of the stock system, delete the "-w", run the bat file, and the updated stock system works fine without the data wipe.

In your case, probably delete several lines from the file leaving only the radio?

---------- Post added at 06:54 AM ---------- Previous post was at 06:45 AM ----------

By the way, I found the latest version of "kernel tuner 2014"has a new item in the misc category to change the system from enforcing to permissive.

So immediately after a reboot, I look in system settings and it is enforcing, but within a minute kernel tuner implements it's settings and it changes to permissive.

I am not sure why cyanogenmod changed to enforcing, nor how helpful permissive might be
[Nexus 7 (2013) LTE Android Development] Sardus87:
Yes, now works for me too :good:
[Nexus 7 (2013) LTE Android Development] LP6:
Thank you, I will try this. If only Google had a Lollipop image for Deb/Razorg already...
[Nexus 7 (2013) LTE Android Development] janeka_pt:
How's battery drain? Does location on Maps work?

Thank you in advance
[Nexus 7 (2013) LTE Android Development] LP6:
Unfortunately this didn't help. Bootloader was already the same as on the latest Google image and I installed the modem via bootloader, but I'm still missing WiFi and mobile network requires the permissive fix to work.

Shouldn't correct bootloader and modem etc. come with the CM nightly image?
[Nexus 7 (2013) LTE Android Development] HowardZ:
Sorry it didn't help, but I think it's always best to stay current with the Google bootloader and modem.

Cyanogenmod provide new versions of the kernel partition (also known as boot), and the system partition. I don't think cyanogenmod provides anything more.

I also heard years ago that WiFi support is in the kernel. If the kernel didn't flash right, then no WiFi. I used to have a HTC Rezound phone, and the Internet advice was to always flash a new kernel 3 times because it wouldn't always reliably flash - but that supposedly was a unique HTC problem.

I hope you did the basic md5 check that your cyanogenmod zip file downloaded correctly without error?

I don't know everything, and maybe others have better advice. To me, a tablet without WiFi is useless - I'd make a nandroid backup and go back to cyanogenmod 11 or stock Google 4.4
[Nexus 7 (2013) LTE Android Development] LP6:
Yep, I always check what I'm about to flash on my devices, you can't be too cautious (paranoid ;)).

I'll hang with the mobile data for a while and test with kernels, but eventually I may have to fall back to an older ROM with working WiFi.

Thanks for your help.

Edit: ElementalX kernel doesn't seem to work with the permissive "fix" and without it both WiFi and mobile data are missing...
[Nexus 7 (2013) LTE Android Development] koron393:
You have to apply ElementalX zip first, next permissive zip.

Do not reverse.

Because ElementalX re-writes boot command parameters completely.
[Nexus 7 (2013) LTE Android Development] LP6:
Thanks. I think it was stuck on the Google logo after doing just that, after which I had to restore boot and system from a backup. I will test it again to be sure.

Edit: It won't boot with ElementalX and permissive zip (flashed in that order).
[Nexus 7 (2013) LTE Android Development] Sardus87:
I noticed that after every rom update, at the first boot my nexus does not require the pin sim to unlock, meanwhile at second one, it does correctly. :confused:

sorry for bad english :)
[Nexus 7 (2013) LTE Android Development] edy.xda:
Any one able to make normal phone calls over GSM/UMTS

Has anyone tried making phone calling work over GDM/3G ? If YES. How do you it on CM 12?

One more question I can see that nighlies are available as OTA, if I do that, will it format all user data or is like other OTA updates which are not a pain in the a$$ ?

Cheers

Edy
[Nexus 7 (2013) LTE Android Development] aristofeles:
2 things that I still dream for my Nexus: phone calls, and to change my LTE band, from whatever US uses to my country 2,5 GHz.