Database Info

[OFFICIAL]CM10 Official Nightlies for D2VZW GSIII

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
See the 9-11-12 Cyanogenmod Announcement at bottom of post! There are now regular Nightlies you are used to and now the M-Series Roms, I will let the CM Team speak for it themselves as to what it is, see quote and link at bottom of post.
As of 8-18-12, the Verizon Galaxy S III, yes the one with the formerly locked bootloader that everyone loved to hate, has now been accepted into the Official CM10 Jelly Bean Nightly builds. Bookmark THIS PAGE to check for the latest nightlies. Many thanks to everyone involved in getting the d2vzw this far including you, African Canadian Sock Monkey!
Official Announcement from Cyanogenmod 8-18-12
Today we kick off the nightly builds of the CM10 JellyBean code branch, builds will show up later this evening.
CM9 nightly builds for devices that don't receive a CM10 nightly will continue (for the meantime) but we are changing the timing on them to be once a week instead (aka weeklies). This will allow a means for us to test bug fixes and the like as they get merged into the ICS branch - as stated before, the CM9 branch is in an otherwise perpetual code-freeze.
The devices receiving CM10 nightlies this evening include (but aren't limited to):
# The US SGS3 variants
# The Galaxy Nexus variants
# The Nexus S varaints
# The Nexus 7
# The Transformer and Transformer Prime
# The SGS1 variants (Vibrant, Captivate, International, and i9000b)
# The SGS2 i9100g
# P3 and P5 tablets
Other devices will join the roster as they become ready and gain their maintainers blessing for nightlies.
Edit d2vzw nightlies will require the insecure bootloader. See http://goo.gl/CST0K
Click to expand...
Click to collapse
Source
I didn't see a thread for this so I figured I would go ahead and create this thread for the discussion and following of the d2vzw Official CM10 Jelly Bean Nightlies. Our maintainer cvpcs has stated that the initial official nightlies may not have all of the fixes such as MMS fix in them until those fixes are merged into the official tree.
YOU MUST BE ROOTED:
I recommend using the Casual app from Adam in THIS THREAD.
YOU MUST BE UNLOCKED:
As stated the official version of CM10 nightlies for d2vzw requires you be on an unlocked Verizon GSIII. As an alternative to the Casual method Adam posted up, you can now unlock your device using a simple one-click app made by fellow dev mmmeff called VZW GS3 EZ-Unlock on the play store.
YOU MUST BE RUNNING A CUSTOM RECOVERY:
Also see his EZ-Recovery for VZW Galaxy S3 app for the easiest way to load any custom recovery you want. Please note the Touch CWM 5.8.4.9 available in the app doesn't play nice with CM10. Don't use it. I personally recommend using the CWM (non-touch) versions such as 6.0.1.2. If you prefer 6.0.1.2 Touch and want to flash it using the EZ-Recovery app using the "custom" option, simply flash this file using the app.
If you would rather not use that app, see THIS THREAD for CWM 6.0.1.2 files and install instructions.
blade7840 said:
Can I use TWRP recovery to flash this Rom?
Click to expand...
Click to collapse
Don't see why not. As usual, make sure you have a nandroid just in case. I previously stated TWRP Data Wipe was broken. Which is only partially true, because it FAILS for a REASON. If it worked it would format our internal sdcard! Proper use of TWRP would be to use the Factory Reset option which should take care of things. The Format Data option would be rather dangerous if it worked. So there you go.. It should work as well as CWM. More of a preference thing. You can find TWRP 2.2.2.0 in THIS THREAD. If you like using mmmeff's EZ-Recovery app and want to flash TWRP 2.2.2.0 using the custom option, use this file.
BECAUSE WE ARE NOW UNLOCKED, WE NO LONGER REQUIRE OR USE ANYTHING KEXEC
* In case anyone is still running CWM 6.0.1.0 from the kexec kernel days it is fine to use still. It functions as a standard custom recovery but had the additional ability to run kexec enabled kernels. So you can continue to use it or upgrade to another version. Because we are unlocked you are free to use any recovery now and Kexec is no longer applied.
So now all you need to do is root your phone, load up those two apps, load the recovery (i recommend the newest TWRP 2.2.2.0), unlock the device, and download and install the latest nightly in recovery.
GOOGLE APPS (including Play Store) ARE NOT INCLUDED IN OFFICIAL CM:
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Google Apps by default.
If you do a complete wipe and install an official CM10 build clean and you still have gapps remaining without having ever installed a gapps package, you likely didn't get a clean wipe. Recommend rebooting and wiping again and re-install.
WILL I LOSE MY IMEI IF I FLASH THIS?:
WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Click to expand...
Click to collapse
There is a chance you will lose your IMEI on these devices any time you flash anything. If you are not willing to accept the risk inherent in flashing your device, regardless of what you are flashing or what you are worried about, then DONT FLASH ANYTHING, remain stock, and locked. If you want to read more on the "how to" for IMEI backup and restore, see THIS THREAD for latest IMEI discussions and detailed methods for backup and restore.
CM OFFICIAL NIGHTLIES DO INCLUDE A KERNEL:
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Click to expand...
Click to collapse
Yes. If you want to try custom kernels on CM10, it is of course at your own risk.
Flash, MMS, NFC or Native Tethering work on these builds?
Let's put it this way. They have all worked at some point or another. Then you have the fact that so many people posting here are contaminating the results with comments about unofficial builds and people that are flashing using different methods, etc......There's no good way for me to track and update this portion accurately. If you rely on any single feature to work properly, you are using the wrong ROM. Go back to stock. If you are flashing Nightlies of anykind you should expect things that have worked all along, some days will be broken. So the best thing to do is try it yourself and report here for others to see. These might be official nightlies but it's still very BETA and WIP (Work In Progress) and should be treated as such.
MMS WORKS
I can confirm personally as of the 8-20 build MMS is working and persistent after a reboot!
NFC WORKS
NFC fix found here.
WPA/WPA2 Native Tethering WORKS
You can flash the file in THIS POST to fix native tethering with WPA/WPA2 security intact.
FLASH WORKS
Sideload the newest Adobe Flash app found in THIS THREAD to get Flash on Jelly Bean. Of course you must have "Unknown Sources" enabled in Settings->Security to sideload any apk
If things change, let me know via PM, I'll try to update the OP.
UNOFFICIAL ALPHA BUILD THREAD IS OVER HERE.
In that thread you can find discussion and info on the unofficial alpha builds by people such as cvpcs, invisiblek, dhacker and others who have been part of the efforts to get us to where we are today. Their contributions are invaluable. Those builds right now may actually run smoother and have less bugs because they are UNOFFICIAL which means they can do what's called "cherry picking" and include code that has not been committed into the OFFICIAL builds yet. The official build may or may not have all those features. They are sometimes different ROMs functionally.
Now that we have an Official Nightly build in order to not confuse people please take Alpha Unofficial talk to that thread. Please keep posts here on topic and relevant to the Official Nightly builds. Things that work on those doesn't work on these and vice-versa.
CHANGELOG IS HERE and UnOfficial CM10 Bugtracker is HERE
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
UPDATE, Official Announcement from Cyanogen Mod, M-Series Roms Announcement 9-11-12
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
Tonight’s M1 build is available for these devices:
Galaxy Nexus GSM (maguro)
Galaxy Nexus VZW (toro)
Galaxy Nexus Sprint (toroplus)
Galaxy S2 GT-I9100G (i9100g)
Galaxy S (galaxysmtd)
Galaxy S B (galaxysbmtd)
Captivate (captivatemtd)
Galaxy S3 Sprint (d2spr)
Galaxy S3 VZW (d2vzw)
Galaxy S3 AT&T (d2att)
Galaxy S3 TMO (d2tmo)
Galaxy S3 US Cellular (d2usc)
Nexus S (crespo)
Nexus S 4G (crespo4g)
Galaxy Note AT&T (quincyatt)
Google Nexus 7 (grouper)
Sony Xperia Acro S (hikari)
Sony Xperia S (nozomi)
In standard CM style, we will continue to add devices as time goes on up until our stable release.
Head over to Get.CM to grab the latest build for your device. Installation instructions and other documentation can always be found at the CM Wiki and help is always close at hand over on our official forums.
Happy flashing!
Click to expand...
Click to collapse
Source
If you need a more general "all things GSIII guide" to bail out of a problem, or to do other things that aren't necessarily CM10 specific, I highly recommend THIS THREAD

So to start it off I'd like to know if anyone is running the cm-10-20120818-NIGHTLY-d2vzw.zip build from early this morning? Does it have the MMS fix? Is it significantly different from the alpha builds we have been running for a couple weeks?

Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've unlocked your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.

Do these include google now, if not where can I get it?

ilogik said:
Do these include google now, if not where can I get it?
Click to expand...
Click to collapse
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Play Store by default.
Click to expand...
Click to collapse

Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium

Immolate said:
Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've disabled your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.
Click to expand...
Click to collapse
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies

WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
YES. Op updated.

Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2

Schaweet said:
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
Yeah yeah, acknowledged. I'm sure if you can disable your bootloader, I'll figure out a way.

ive had one random reboot hopefully it was just a once time thing cause im loving this rom..much better than touchwiz
hopefully that flickering thing when texting gets fixed soon cause it gets a bit annoying..(ive also noticed that my widgets flicker)

neyenlives said:
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Click to expand...
Click to collapse
I think he's talking about Google now(voice search assistant), Not Google apps. It should be built into the ROM but you should still flash gapps anyways
Sent from my SCH-I535 using Tapatalk

Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The ROM comes with a kernel, but you can flash any non-kexec kernel for AOSP ROMs that you want. I'm currently running an AT&T kernel.
Sent from my Galaxy S III

TheBiles said:
Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
Click to expand...
Click to collapse
mms is working for me with the latest build:good:

XTRoRDiNAiRE said:
mms is working for me with the latest build:good:
Click to expand...
Click to collapse
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III

Can I use TWRP recovery to flash this Rom?

TheBiles said:
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III
Click to expand...
Click to collapse
Phone number and MIN are blank for me (after a few reboots). Also, the LTE toggle doesn't seem to function properly. Everything else is working flawlessly; this ROM is definitely a daily-driver. Enjoy!
EDIT: I just realized that MMS isn't working for me....I can live without it for now but those that need it, may want to wait for another build.

neyenlives said:
YES. Op updated.
Click to expand...
Click to collapse
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium

Nice. I was just thinking about flashing this
Sent from my Verizon Samsung Galaxy S 3 running SynergyROM v1.6

WizeGuyDezignz said:
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The IMEI issue from my personal standpoint and based off of the opinions of the smart guys in IRC, is that it is very possibly a hardware design issue. Samsung could have put the EFS data which contains the IMEI in a non-volatile un-changable part of the memory but it looks as though they left it writable. This means we can try to write it back if we lose it but it also means bad data could be written to it thus erasing it.......that's what I have gotten out of it so far. So every time you flash you take the risk. I seriously doubt any fix will ever officially come because as long as you buy the phone and use it in stock form, you would never see the issue. It's an issue that only affects custom flashers, so don't expect to see a fix.

No location services in JB ROMS

I'm having a strange problem with every 4.1.X ROM i try. All apps that use location data seem to think it still needs to be enabled - even though it is. Gps on, Wifi and cell data share on, but I'm still reminded to enable them for better performance.
This isn't much of a problem with anything except Google Now. Maps still gets a gps fix despite telling me gps is disabled, but Now only shows the "enable location data" card. Any idea how to fix it? I've tried 5 different roms, fixed permissions, did several data and cache wipes, nothing works.
My sister has a stock S 4G with the OTA update and hers works flawlessly.

Have you tried flashing a custom kernel? Did you wipe data/cache/dalvik/boot/system before each ROM install? JB doesn't seem to play nice with some people's phones. Maybe 4.1.2 might fix your problem once someone gets it running on our 4G variant. Also, I believe this belongs in the NS general forum?
Sent from my Nexus S 4G using Tapatalk 2

I've used matr1x 22.5-23.5 along with stock kernel or included kernel variant packed with each rom and no luck.
And I AM running a 4.1.2 ROM right now, that's why I said 4.1.X because the issue is with both versions
Sent from my Nexus S 4G using xda app-developers app

Well that's interesting because I've never had such an issue with jelly bean but future reference don't post in android development section unless your releasing a ROM or kernel or even a recovery... I'm reporting this thread so it can be moved
Sent from my Nexus S 4G using Tapatalk 2

[Q] WiFi flaky with Sky-Jelly-Bean ROM from seanzscreams

I am posting it for first time but have tried many ROMs since GB ROMs on my skyrocket. I am not yet allowed to post this question on dev's ROM page. Recently I flashed Sky-Jelly-Bean ROM from Sean T11 beta. While the WiFi worked fine before flashing the 11.2 update, it became flaky after I flashed the update. Every 10 minutes or so it would switch to cell network and back to WiFi. This seriously impacts any downloads or streaming. Same happened with T10 base as well. I didn't notice it on T7.1 though.
I noticed this issue at home and at work. I had full WiFi signal when I had it. But still it switches to cell network about every 10 mins.
I did wipe cache and dalvik 5X before flashing the update. Fixed permissions too. Using TWRP open recovery for flashing the ROMs. Is anyone else noticing the same issue? Any help would be much appreciated.
Thanks Sean for another wonderful ROM. I have been flashing all your ROMs and updates since GB ROMs on my skyrocket. None of them failed to impress me.

wait continues...
I have to wait for 9 more posts to start posting the questions directly in dev's ROM pages.

It's a beta. He stated if you want a flawless Rom go back to 7.1
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Yeah, I took the risk with the beta. But I had the same issues with T10 as well. I wanted to know if anyone is facing similar issues or is it only me. Are you on T11? Do you see any similar issues?
Sent from my skyrocket

I have no issues with wifi with T11.2

I don't have WiFi issues using T11.3
Sent from my SAMSUNG-SGH-I727 using xda premium

raj3366 said:
Yeah, I took the risk with the beta. But I had the same issues with T10 as well. I wanted to know if anyone is facing similar issues or is it only me. Are you on T11? Do you see any similar issues?
Sent from my skyrocket
Click to expand...
Click to collapse
No I don't use that Rom, sorry man.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I went and fixed permissions for few times and now the frequency of the problem has reduced, but not completely. I guess I have to live with that for now. Hoping future updates or ROMs from sean might fix it.
Thanks all for responding.
Sent from sky

Dose anyone know where I can get a different boot animation for the sky jelly bean? To like the nexus one or the original jelly bean animation?

Try a different radio or reflash the current one.
Sent from my SAMSUNG-SGH-I727 using xda premium

I had that issue on UCLF6 and tried UCLI3. But both had the same issue.
As I mentioned before, it got much better after fixing permissions for few times. I can live with it until 4.2 updates come.
Sent from Milky way

CaLLm3LAzY- said:
Dose anyone know where I can get a different boot animation for the sky jelly bean? To like the nexus one or the original jelly bean animation?
Click to expand...
Click to collapse
You might want to post this directly under Sean's SkyJelly bean thread if you are using his ROMs.
Btw, someone in that thread mentioned that the ROM stopped working after flashing a new boot animation. You might want to search around a bit before playing with flashing boot animations.
<<<<<
Originally Posted by kamui957 View Post
Really liked this rom, then after flashing a new boot animation it stopped working completely, and now even when I wipe it completely it still will not boot. Formated cache, system, data, etc 5x and then flashed just the base 5.0 rom, Nothing. Flashed back to Sky ICS just fine. Flashed to other JB based roms fine, but this one just won't flash. Kinda sad really.
>>>>>

4G never going above 1 bar...

Hey guys
I recently got into the s3 (I know, I'm late to the game...)
I am using the latest elemental X from Nitro...and I love the ROM!
The one thing I noticed is that I can never get above 1 or 2 bars on 4g. Speedtests never go above 4 or 5 Mbps. However, My Bionic will do 25+ in same area.
Any suggestions where I should start investigating?
Thanks!

About the only thing I could suggest is to try another modem and rpm

docluv01 said:
Hey guys
I recently got into the s3 (I know, I'm late to the game...)
I am using the latest elemental X from Nitro...and I love the ROM!
The one thing I noticed is that I can never get above 1 or 2 bars on 4g. Speedtests never go above 4 or 5 Mbps. However, My Bionic will do 25+ in same area.
Any suggestions where I should start investigating?
Thanks!
Click to expand...
Click to collapse
How was your signal on stock ? ROMs don;t change the radio, so should be the same. Did you make any other changes?

DigitalMD said:
How was your signal on stock ? ROMs don;t change the radio, so should be the same. Did you make any other changes?
Click to expand...
Click to collapse
Hmm, to be honest, it seemed ok...
Here is what I did when I got the phone...
I ODIN's back to stock 4.1.2, rooted and unlocked bootloader.
Went into clockwordmod...wiped etc, installed elemental X, and gapps.
Should I have done the OTA update 1st?

I just checked the baseband version..., it says "I535VRBLK3"
Could that be it?

Elemental is aosp right ? If it is then that's you're answer . try a touchwiz ROM and you'll see the bars falling off your screen . tyres ROMs have to do with your signal . touch wiz ril will always be superior to aosp's ril.

docluv01 said:
I just checked the baseband version..., it says "I535VRBLK3"
Could that be it?
Click to expand...
Click to collapse
Your modem should be VRBMB1 , you are on an older modem/radio version
You should install the latest OEM verizon 4.1.2 full.
Then root and install the ROM you want.
The radio is the radio and custom ROMs shouldn't mess with your actual signal if you install via recovery, but GUI changes to the status bar may cause the display to be different.

Thanks....Thats exactly what I just did....
Stock ROM still giving lousy signal....speeds aren't that much better...
Ill try a touchwiz rom also...

docluv01 said:
Thanks....Thats exactly what I just did....
Stock ROM still giving lousy signal....speeds aren't that much better...
Ill try a touchwiz rom also...
Click to expand...
Click to collapse
And your modem version is? Data rates might get a little boost from some tweaked ROMs, but actual signal strength won;t, it simply doesn't because custom ROMs still run the stock modem and radio. And the stock ROM IS TW . when I run stock , I get 25+ mbs down in a 4g area, same as on Synergy custom, even when I have only 1 bar I get 10 mbs down

DigitalMD said:
And your modem version is? Data rates might get a little boost from some tweaked ROMs, but actual signal strength won;t, it simply doesn't because custom ROMs still run the stock modem and radio. And the stock ROM IS TW . when I run stock , I get 25+ mbs down in a 4g area, same as on Synergy custom, even when I have only 1 bar I get 10 mbs down
Click to expand...
Click to collapse
Hmm, forgive me, but which would be the modem version?
I put everything back to stock, rooted for now....
Thanks again my friend!

ive read that hte AOSP roms show less bars but get similar signla.
ive seen it in practice when with my mother.
check the signal strength on TW, then on AOSP and see if theyre equal. my moms stock S3 gets the same signal as my aosp phone does in our location.

Go here. Download the latest. It is an all in one. With the latest trust zone. It may alleviate your problems.
Or not.
I am running the PACMan ROM. And it shows less bars. Yes, it annoys the living daylights out of me. But, the speed is there when I use it and do speed tests. Any way, good luck.
http://rootzwiki.com/topic/34053-modemrpmtz-vrbmb1-verizon-sgs3-sch-i535-recovery-flashable/
Sent from my SCH-I535 using xda app-developers app

Jaytronics said:
Go here. Download the latest. It is an all in one. With the latest trust zone. It may alleviate your problems.
Or not.
I am running the PACMan ROM. And it shows less bars. Yes, it annoys the living daylights out of me. But, the speed is there when I use it and do speed tests. Any way, good luck.
http://rootzwiki.com/topic/34053-modemrpmtz-vrbmb1-verizon-sgs3-sch-i535-recovery-flashable/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks ! ill give it a try tonight....apprecviate the help!

Wifi not working with custom roms on n8013

A few days ago I got my new Galaxy Note 10.1 wifi edition (the n8013 I believe). I rooted it then flash the latest CM 10.1 nightly only to find wifi does not work... I subsequently tried a few other custom roms (I think they were all based on cm10.1 which may be the problem). Wifi will turn on and recognize my network but when I try to connect it simply says "connecting" and then a few second later goes back to "saved, secured with WPA2". I'm relatively sure it is not my router since my laptop and phone are constantly connected and my tablet could connect on TouchWiz.
I've looked all around XDA and other forums to see if anyone has this issue and I could only find one topic but it had no resolution. I figure this must no be too common since Wifi, at least for the n8013, is the only way of connecting to the internet.
Any one have a similar problem or know how to fix it? Should I try flashing a rom that isn't based on CM10.1? I could just go back to stock TouchWiz but I'd rather not...

There's some good roms that are based on stock. I never used cm 10.1 so I don't have an answer for that. I am on an experimental build of 10.2 and wifi works just fine.
Sent from my EVO using xda premium

fluffy312 said:
A few days ago I got my new Galaxy Note 10.1 wifi edition (the n8013 I believe). I rooted it then flash the latest CM 10.1 nightly only to find wifi does not work... I subsequently tried a few other custom roms (I think they were all based on cm10.1 which may be the problem). Wifi will turn on and recognize my network but when I try to connect it simply says "connecting" and then a few second later goes back to "saved, secured with WPA2". I'm relatively sure it is not my router since my laptop and phone are constantly connected and my tablet could connect on TouchWiz.
I've looked all around XDA and other forums to see if anyone has this issue and I could only find one topic but it had no resolution. I figure this must no be too common since Wifi, at least for the n8013, is the only way of connecting to the internet.
Any one have a similar problem or know how to fix it? Should I try flashing a rom that isn't based on CM10.1? I could just go back to stock TouchWiz but I'd rather not...
Click to expand...
Click to collapse
U have mistake when flash rom not for 8013. Now U only 1 way is flash stock rom and factory reset after the first boot.
If U wanna CM rom, u have to reconized what rom affordable for 8013 first.
Sent from my GT-N8013 using Tapatalk 2

having same issue
Tried a few roms and wifi doesn't work. Any suggestions?

*ZeuS* said:
Tried a few roms and wifi doesn't work. Any suggestions?
Click to expand...
Click to collapse
What rom which you had tried? I think you back to stock rom to fix wifi driver first
Sent from my C6802 using Tapatalk

Cm10.2, paranoid android
Sent from my GT-N8013 using XDA Premium HD app

WiFi is a function of the kernel .