yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Yet I and several others have/had no problem with headphones. Me up to a nightly in middle of July. I personally went back to a TW based Rom because I need the Bluetooth working and need my square card reader to work. Battery life is obviously shorter but I've optimized a little and is better than true stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zoser42:
Yes that's what I mean. But the post after mine said that some don't have the issue so my info may not mean anything at all. My guess is a bug was introduced upstream in cm in the last few months since that is when all of the reports started. I didn't install the gold build or and recent cm 13 nightlies to find out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
Alright.. Thanks anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] osk4rin:
Hello guys!

I have a issue with my s3 sgh i747 At&t. I could not flash any Gapps just the ROM.

Does anyone have this same problem?

Any specific Gapps?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GoughGhan:
Which version of Gapps did you try?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amanvishnani:
What are the flashing instructions?

Factory Reset, format system and Catche wipe?

Which recovery should I use?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] osk4rin:
I tried many gapps like nano, Pico, micro, mini, stock. Any of them work

Any solution for this?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therock3181:
You should use TWRP 3.0.2-0. Flash this first.

Advanced wipe and check everything. Make a backup of your internal/SD card memory for important things.

Copy your custom ROM, Gapps and SuperSU on your phone.

Flash Custom ROM, SuperSU and Gapps.

Enjoy !

---------- Post added at 01:24 PM ---------- Previous post was at 01:23 PM ----------

Have you done an advanced wipe and check everything including Internal/SD card memory ?

Have you flash your custom ROM and Gapps at the same time ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] osk4rin:
Yes,I flashed the Costum ROM and Gapps at the same time,even with wipe SD card.don't know what is the problem

I'm gonna try to Install another Recovery mode.

---------- Post added at 07:05 PM ---------- Previous post was at 06:50 PM ----------

I just Flashed TWRP 3.0.2 it was the problem,I have an old TWRP

NOw I'm flashing the ROM is working like A Champ.

Many thanks:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tguadagno:
hi, i just noticed that i (accidentally) upgraded from 13.0 nightly's to a 13.0.1 nightly (13.0.1-2016-08-05-nightly-d2att). i was not paying attention. everything seems ok, but all the subsequent 13.0 nightly's are looking like older versions. In addition, i do not see a 13.0.1 update.....so, whats the deal with 13.0.1...will there be more nightly's? can i go back to the current 13.0 nightly without issue?

thanks for your help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
That is weeiiirrd! I never heard anything about 13.0.1 except on official devices (oneplus one etc).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tguadagno:
proof
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Thevenine:
I was also on that nightly for a few days. According to the changelog, 13.0.1 only signified a new security update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pyro00:
Hey guys, I was just wondering what the likely-hood of adding USB keyboard capabilities to the kernal are? I love Keepass, and this plugin allows you to use your phone as a keyboard so it obfuscates your password and you dont have to use a keyboard to enter it on a computer.

I can't post links but on the Google Play Store:

Keepass2 USB Keyboard Plugin

USB Keyboard

I'll mess with my phone a bit, but the kernal is not something I'd touch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
You should honestly just go with a the OFFICIAL Cm13 as nightlies have been out for the d2att and others for a long time.

Sent from my SAMSUNG-SGH-I747 Running CyanogenMod 13
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pyro00:
I am using the CM13 ROM. Android seems to support using the phone as a USB keyboard, but they don't seem to have code in the kernal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pierre2324:
Nothing nougat for i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PaulG2000:
+1 ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
invisiblek has posted some unofficial CM 14.1 builds for d2vzw on his site. Keep your fingers crossed. There's still some development going for the old S3. Hopefully it will make its way to the other d2 variants.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yosmokinman:
^If anyone want's to give N a spin the vzw rom works on our d2att if you remove the asserts. But it's no dd (see edit, may be a dd already). Make a nandroid first!

The rom works quite nice I'd say snappier than M but while data, sms, outgoing calls work (after changing to gsm auto and letting gapps install googlephone and giving it permissions), incoming calls do not work for me (t-mo sim if it matters).

Just shows N could work well on the d2att if calls can be fixed.

[MENTION=5806583]canodroid15[/MENTION] Did Incoming calls work when you flashed it on the att phone?

Edit: Flashing the gsm ril blobs zip seems to have fixed incoming calls. Didn't work for me on the 11/25 rom now it does on 11/28, cool.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Yeah as long as you flash the d2gsm ril blobs you're good to go. Also, in preferred network settings I choose GSM/WCDMA/preferred (all the way at the bottom) ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yosmokinman:
^Yup :D Those two things have the official d2vzw 14.1 working nicely here.

If thats all we need where's Dave at for the att official :p

Edit: I was just thinking, if I could get a sprint splash screen.. I'd have a vzw rom on an att phone with a tmo sim and a sprint startup? May cause a Resonance Cascade.. Hmm...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majorkid:
Where can I find d2gsm ril blobs i searched for it but couldn't find it..? I didn't find on invisblek site
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yosmokinman:
^ Here: http://xdaforums.com/galaxy-s3-verizon/orig-development/rom-cyanogenmod-12-1-nightlies-verizon-t3113037 it's in the "d2vzw ROM Extras" link in the op.

Make sure to change preferred network type to gsm as canodroid said. I have it on gsm/wcdma auto. Otherwise outgoing calls don't work.

I'm thinking of flashing the d2vzw twrp so I don't have to remove the assert for each update. Anyone see any problem with that? I'm not sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Don't flash Verizon twrp, not recommended
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=4551784]matrixzone[/MENTION], has returned from the matrix Lol :) Long time no see man. Hope you're doing OK these days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majorkid:
Official CM 14.1 Nightly is up for d2att can't wait to try out ..

d2att Official CM Page
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tjensen:
Hopefully a CM 14.1 nightly thread will get created by the person in charge and we can all start helping out :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Compxpert:
Wow 14.1 rocks. Other than occasional BT hiccups with streaming to my pioneer headunit its flawless. Can even make calls on it. I have yet to have an issue with it.

Edit: One small bug is the pull down tray live tiles do not update the BT info

EX im using headset but it shows my radio as connected,

Icon in tray does not update either so it still shows the battery indicator from my headset when connected to my radio.

Going into BT settings however yields correct info
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
I only played around with it for a few minutes, but 14.1 send to have breathed new life into this old phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
CM14.1 is sucking for me [emoji20] Whenever I flash Gapps Pico the wifi connectivity always fails and play store doesnt work. This has forced me to revert to CM13 until I can find some help with this [emoji20]

And when I tried it I clean flashed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Compxpert:
I used the Micro package
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
I guess I'll at least try that. What date was your Gapps package from?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majorkid:
Am having a problem in CM 14.1, some sim cards are detected while others are not detected.. So i decided to upgrade my BL to Latest, Now my baseband is unknown and imei is null.. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
OTA updated from CM13.1 to CM14.1 and it won't stop popping up with a "com.android.phone has stopped" error. Clean flash with this one, don't be stupid and lazy like me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Compxpert:
Additional bug, there is no battery menu in settings, more settings in pull down does not go to it either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anil2653:
Same issues I am having on my d2tmo as play store not connecting and showing no internet connection, contacts and Gmail not syncing but calendar is syncing and inbox is working
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoshkapundrick:
I installed cm14 12/15 nightly as a "dirty" install over my cm13 official. I used the latest open gapps mini. The only problem i am getting is the error "com.android.phone has stopped". I am lucky that i am using freedompop on this device because calls and texts work with no problem since they use a separate app to make calls and to text.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EriksR:
Does anyone know where to download the last CM13 nightly? Must've been 20161212 or something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chill4279:
The last CM13 d2att nightly I had seen was 20161204....I made sure to make a copy of it before it disappeared from the get.cm site. If interested, I can make it available for download...

---------- Post added at 09:45 AM ---------- Previous post was at 09:29 AM ----------

went ahead and shared the link to the last CM13 d2att nightly build:

https://drive.google.com/file/d/0Bwr-IFp5NTJKY28xSXMyZHh2Q3M/view?usp=sharing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
A few posts above your's:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EriksR:
Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] proza:
Is this Android 6.0.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
yup

"err on the side of kindness"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iamn1ck:
I reverted back to stock rom, from this rom, this summer to play pokemon go, but now I'm trying to update back to this rom so I can play newer games. I did wipe/factory reset and now I get stuck on a black screen at boot. When the phone boots it flashes the 'Samsung' logo, then shows the samsung galaxy s III screen with the blue guy on it, and after a second it just goes black.

How can I get this to load on my device, I dont have a backup on this computer and wont have access to my main pc with my backup for another week or two and I need access to my phone

any help is greatly appreciated

edit: nevermind guys, it turns out my power button was stuck down, so when it booted it would immediately turn itself off again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] proza:
What is the different between this nightly build and the unofficial build that is on thread 1. I mean what is new after the unofficial build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martiroskg:
guys sim card doesnt work. it doesnt see my sim cards. what should i do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EriksR:
I had the same when I first went from original rom to CM11, you need to update your modem/bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CajunDreDog:
The newest nightly is posted today. lineage-14.1-20170213-nightly-d2att-signed.zip

https://download.lineageos.org/d2att

Noob question: If I update OTA, will it wipe my phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d00m178:
latest lineage os lineage-14.1-20170911-nightly-d2att-signed.zip doesn't boot on my sgs3 (d2att) with latest twrp 3.1.1

just shows boot animation in loop.

can't find any info about fixing this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechGuyAnthony:
I suggest you try running Resurrection Remix. Its another ROM derived from Lineage and is officially supported by the S3 (d2att)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] asdf2345:
Could you fix the link?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arana1:
do i risk anything if trying on a i747?

have not been able to get any custom romworking on it, all of them give me problems with no service/no sim card messages
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
I didn't understand? What do you mean... By this comment?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
All these team inherit from CM source.. Until we have strong device maintainers from these team for d2att, they will stop the support. At the moment Omni does not support our device not even for kitkat. And slim for d2att is based on CM tree. I check the device tree of all the custom rom regularly. You won't find much difference in anyone, except some nIce add-on
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheGeekyNimrod:
Device trees are almost always based on CM yes, but base code is not. That's what I was trying to say. I'm sure both teams have people capable of bringing those trees up, whether they actually do or not is a different story. I know devs o here who have brought other ones up for Lollipop.

I have a feeling we'll see something from CM, but it will be a while. Lollipop is such a different thing that it's going to take some time. I have no fear that d2att will make it there. Just not in the timing we would like to see.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I know of some exceptional cases like the International S3 where the Namesless has taken lead the development. But on large scale CM maintains the device tree.

On good news, we now have official device maintainer for our device. Nardholio
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheGeekyNimrod:
All that worrying for nothing ;) lol. I knew it would happen somehow. Too many people use this device.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I will purchase new mobile once we loose official CM support. Don't want to use obsolete technology :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheGeekyNimrod:
I'm with ya there.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mickiemas:
Does that mean we will have official cm12 for our device?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheGeekyNimrod:
In time, yes. But I would expect it to be just a little while longer.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mpjohnsn:
Home button issues...

Has anyone's home button experience actually degraded over time? It was working for me on one of the early builds but it hasn't worked since around 12/20. I have to enable the onscreen controls to have any sort of normal navigation.

Any ideas on how to fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mickiemas:
Doesn't really matter how long just wanna know it will be supported. I tried installing the cyanidel v3.0 but it just stayed there saying installing and nothing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tazmanian200:
flashed the 01/04/15 rom and the only camera app that works is the FX. only the camera works, no video. any fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Go to settings/buttons/home button, & tick the wake device switch in the newer builds
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mpjohnsn:
Thanks, but I've tried this and it doesn't enable the single-click to go home. Also, the long-click function doesn't work. Strangely, the double-click function works and I just set it to App Switcher to get by. However, the single-click will wake the device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Oscargl15:
you guys know how to disable noise supression in the phone with this rom? because it reduces the sound when i talk, i need help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BottleB:
[MENTION=4551784]matrixzone[/MENTION] and [MENTION=5315289]TheGeekyNimrod[/MENTION]nimrod - will you guys merge projects? I'm always torn between both builds....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jondroid2:
I had a similar problem not to long ago. I had to get a fresh download of the ROM and clean flash it. Home button problems fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Lol! Agreed, if they did I'd bet whatever they released would be the ROM to end all ROMs! 2 amazing minds behind one build? Scary good!!??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RayEdmondson:
:good::good::good::cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Still no fix on video. It's been beat to death
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbrian27:
That's the understatement of the year thus far :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] philhouse:
I know that the camera doesn't work, but for learning purposes I'm wondering if anyone can explain why? I believe I read that it wasn't working that great with CM11 either. Is it something unique to our devices or unique to Samsung? Just curious. Thanks and amazing work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ruger94:
The short answer is...this OS is not designed for our phone, there is no code except for the phones it was released for... That's why each time a new OS is released there are problems with certain aspects of adapting for other and older models of hardware.

S3 running someone else's ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mpjohnsn:
Sadly, I did a clean install with no changes. Thanks though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] korrectmethod:
Tried clean install of the 1/4 build. Main problem I had was the music player would pause and crash when a notification tone would play either via text or email. Also had a very difficult time maintaining LTE. Otherwise smooth performance and decent battery life.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tscollins2002:
Fixing the camera

First I would like to thank you for giving us an early peak at CM12 but because of the camera, time shifting and other issues I've encountered with this ROM I decided I have to go back to CM11-M12 and just wait for the official CM12. So last night I did a 'wipe data/factory reset', 'wipe cache partition' and 'wipe dalvik cache'. Once all that was done I then did 'install zip' and selected cm-11-20141112-SNAPSHOT-M12-d2lte.zip. It was all up and running I then tried to use the stock camera app and got 'Can't connect to the camera' or if I do get into the camera app it will just stop while I'm accessing the settings. My question is there a more thorough wipe I can do on the device or with adb that will get things all running nicely again? Anyone, anyone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheGeekyNimrod:
In my recent experience, going back to KK from LP, I've had to do the wipe you mentioned and wipe internal as well (make sure anything you need is backed up). I don't know if it's just me having to do this, but the times I have gone back to KK, all sorts of weird things happened if I didn't wipe it all.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fezzy102:
Going back to kk is a must full wipe of everything and internal memory. Its because things are accessed differently in lp than kk and cause weird issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AddictedToB3er:
Hmm strange I had no issue installing cyanide L coming from I think it was slimkat. Clean install of course and pa 5 beta gaps. Definitely hung up at boot animation first time and with my impatience I forced it to restart and it booted up without a problem.

Sorry to be off topic, though I've noticed a ridiculous hang time on every device I've updated to lollipop. I just assume that's normal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Uploading new build on the server, will update the OP once the file is uploaded

I am running this build for the last 24 hours without any issues. One of the most stable release.

Change log:

CM Catch-up

Stability and battery fixes

More CM features ported

We are getting closer to official CM nightlies.

Additionally, I have made the CM team aware of the Camera bug. They are already aware of the issue and are working for getting this fixed properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
OP updated with today's build. Go get it while its hot!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anil2653:
Downloading now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mickiemas:
It was just a bad download there was nothing wrong with the ROM. Got a new copy and it worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jk8260:
Get yourself an MD5 checker program and never flash anything to your phone that does not first match the MD5 verification. It will alert you to bad downloads and virus injections. These are free apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Nice work! Thanks for communicating your issues with the CM team and letting us know of the status of the official builds! You are a very informative developer and I appreciate it a lot!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I've been unable to upload photos to instagram for the past few builds. I've tried everything. Any help would be appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheGeekyNimrod:
Only way I've been able to do it on any LP build is from the gallery. Choose the photo, then click the share button up top and choose Instagram. That's what's been working for me at least. Mileage may vary.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjgrenke:
This is what I've been doing for sending pics over text too. Anything in an app that has to load up the camera seems to crash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Where can I find the changelog?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheGeekyNimrod:
Some apps will let you choose which camera app to use. Mms does that for me as long as I don't freeze the stock camera first.

But apps like Instagram call on the stock camera and will definitely just crash out.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jk8260:
I've been texting images fine on this ROM from 1-9 ,just saying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjgrenke:
I'm using messenger for texting, which pulls up the stock camera and crashes as soon as I hit the attach button. It does seem to work fine through the stock SMS app, but going through gallery to send pics via messenger isn't too much of a hassle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] leon77banga:
Working Camera

The Kitkat Camera is working just fine.

Use any root browser (root browser, es file manager)

Delete lib files and GoogleCamera.apk from system/app/GoogleCamera/

Push/Copy the attached GoogleCamera.apk to system/app/GoogleCamera/

Set permissions rw rw rw.

Or Flash the Camera.Zip from recovery

Dont forget to untick the auto update Gooogle Camera from Play Store or it will again update to the new one.

If accidentally update , Repeat the Procedure again :p :p

If this seems tough, Goto Play store Download Cymera App , Its just Working Fine... :good: :good:

If you want old Gallery just copy the attached GalleryGoogle.apk to system/app/GalleryGoogle/

Set permissions rw rw rw.

:good: :good:

Sorry for my bad english :p :p