Hello all
I installed cm12 nightly and I'm stuck with a setup screen where I have to choose language and WiFi, I select them and then I have a 2nd select WiFi screen
How can I solve this ?
Thanks
I'm glad someone started a thread like this for issues with CM12 nightlies. Hopefully it gets used and noticed.
I also had your problem, I just skipped through it until I got to the next part of the setup process.
But overall, CM12 nightly was disappointing compared to the NamelessROM I'm using. Mobile data would be on for only a few seconds then it would disconnect for ages, only occasionally coming back for a few seconds. Makes it unusable for me, and I'd still classify it as an experimental build rather than a nightly because of that. This issue was fixed ages ago in the unofficial 5.0.x ROMs, so I can't understand why CM hasn't fixed it.
Well I can't skip through it because it gets stuck at the 2nd network detection, probably provider selection but I never get there.
It's the Cm account app, why they need an app for that is beyond me but if it is not solved soon I'll move along to another rom....
In the meantime i'm still looking for a fix
Thanks
apuntigam said:
I'm glad someone started a thread like this for issues with CM12 nightlies. Hopefully it gets used and noticed.
I also had your problem, I just skipped through it until I got to the next part of the setup process.
But overall, CM12 nightly was disappointing compared to the NamelessROM I'm using. Mobile data would be on for only a few seconds then it would disconnect for ages, only occasionally coming back for a few seconds. Makes it unusable for me, and I'd still classify it as an experimental build rather than a nightly because of that. This issue was fixed ages ago in the unofficial 5.0.x ROMs, so I can't understand why CM hasn't fixed it.
Click to expand...
Click to collapse
CyanogenMod 12.1 is a free, community built distribution of Android 5.1.x (Lollipop) which greatly extends the capabilities of your phone.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is the support thread for CM12.1 on the AT&T Galaxy S3. All bug reports must be submitted with a log. Feature requests will be ignored, I only work to make the ROM stable on this phone, I do not work on major enhancements to the ROM itself.
Known issues:
Front camera does not work in some apps like Retrica and Instagram.
Install instructions:
1. Install TWRP Recovery for "d2att".
2. Download your correct, updated bootloader/modem. For the US variant you should be on NJ1.. Note that you must do MJB -> NE4 -> NJ1 in order. After MJB you can no longer downgrade your bootloader! Be warned if you are coming from earlier versions. See here and here for the files for the US d2att. I will add links for SGH-i747m if someone sends them to me.
3. Get the nightly build here.
4. Reboot into recovery and install both.
Follow the changelog!
http://www.cmxlog.com/12.1/d2att/
I stole the nice colors above from a post by @InfiniteCaffeine
XDA:DevDB Information
CyanogenMod for d2att, ROM for the AT&T Samsung Galaxy S III
Contributors
Nardholio, invisiblek
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: NJ1 bootloader/modem
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-05-05
Last Updated 2015-05-04
Reserved
Yahoo! First!!
Thanks for this! I hope this fixes the issue I have with Lollipop where when I hit the home button my device goes black except for the status bar!
Thanks!
I installed this and kept having issues with the keyboard not working at all. When I restored via nandroid to my stock setup, nothing worked. It was super whacky. I had to factory reset and restore everything via TiBu. Gonna try a newer nightly and see what happens.
slicetwo said:
I installed this and kept having issues with the keyboard not working at all. When I restored via nandroid to my stock setup, nothing worked. It was super whacky. I had to factory reset and restore everything via TiBu. Gonna try a newer nightly and see what happens.
Click to expand...
Click to collapse
In my side all working good except mobile network the slide all time off..see pic
bluetooth
ok so i dont know if im able to ask this or not but are all the features in this in the unofficial one my amf66
also is bluetooth working
just wondering
thanks
again sorry
So I got it working on my phone, but honestly, I kinda hate Lollipop. I don't like the notifications on my lockscreen instead of at the top in the status bar. I don't like the new animations (I turn all that **** off anyway). I'm not feeling the whole way the sound/alarms/notifications thing is going, either.
Guess I'll downgrade back to my 4.4.2 and be happy with how well things worked on there.
Works great
Installed the 20150504-NIGHTLY last night (dirty flash) and had no issues. No reboots. no signal drop. no camera problems. Thank you!
Hi,
Dirty flashed it over amf66's 4/28 version. It seems very stable, I had one reboot, but I'm sure it was because the phone was overheating (GPS + stuck in traffic + sunroof + warm sunny day).
The only concern I have is regarding bluetooth. It works very well, but the autoconnect fuction does not seem to work. I have to manually connect it (not pair, connect) every time. Once connected, it's smooooth.
This said, I tried to redo de pairing, with multiple devices, screen on / off, cleared "bluetooth sharing" data, etc.
Basically, I have two ways of using it:
Either I keep bluetooth off and turn it on when i'm near a device, it will connect right after turning it on. I can also leave it on and simply select my device when it is in range, and it will connect flawlessly. BUT, if for any reason, the device is turned off, the phone won't reconnect unless I do it manually.
Any thoughts? Anyone else? If i'm the only one with this problem, i'm probably good for a clean flash.
On the 05/05 build I had Dialer force close this morning that required a reboot before it would function again. Haven't gotten it to repeat since the reboot, although it did happen once just now when swiping in Dialer from the lockscreen. Also wanted to note that long press media controls are working again. It's been nonfunctional the past 3 or 4 builds and it's great to have them back!:good:
Aw, yeah. Official thread is a go!
Thanks for maintaining our trusty ol' S3, nardholio. This ROM runs even better than CM11 did on my phone.
I'll throw in a quick bug report, though. In all of these builds (including the unofficial ones) YouTube videos tend to freeze briefly about 8-10 seconds in. This happens with every video when viewed in the YouTube app, regardless of resolution or quality. I haven't noticed it happening with videos using the YouTube API in other apps such as Relay for Reddit.
That's pretty much the only issue I've ever had with these builds. They're pretty fantastic.
Hello guys,
Just a little update regarding the bluetooth issues. I did a clean flash, and it made it somehow better but not perfect. Now, as long as the screen is on or if there is something streaming, everything works well. But, if the phone screen is off, the bluetooth commands stop working (play, next...)...and they work fine if I turn the screen back on. Same goes for the auto connect, it does work when the screen is on, but won't connect if it isn't.
What I think is that the way lollipop acts when the phone is standby simply prevents the bluetooth app from updating it's status or recieving inbound commands. Now, the thing is that it used to work fine in previous builds (amf66 before 4/28 if I remember correctly), and that would mean that some setting was changed, probably in the CM source.
Once again, good job on maintaining our old devices, it really is appreciated.
And..no pressure here, just something I think would be worth looking into.
Dom
Try turning off ambient display for your Bluetooth issues. I'm thinking of permanently disabling it for the S3 anyway as it eats battery.
Nardholio said:
Try turning off ambient display for your Bluetooth issues. I'm thinking of permanently disabling it for the S3 anyway as it eats battery.
Click to expand...
Click to collapse
Tried it this morning, you are on the right track. Once connected, commands now work (phone, play/payse, next etc) even if the screen is off. But, I still have to connect it from the phone, and if the bluetooth device is turned off, it won't reconnect.
Thanks for the support! Are there any other functions that might prevent the phone from scanning for bluetooth devices?
Running the 5/4 nightly. Did the cleanest install possible - formatted through TWRP everthing on the phone, installed the ROM and gApps, then let the play store install all my apps. Everyting is running well for almost 4 hours now. Not a single reboot. Bluetooth has worked for several calls.
Issues I have noticed are -
1. Audio throug the car dock is broken. Once again, as has happened numerous times in the past on Cyanogen, the audio is not being routed through the dock with the phone is docked. I really hope this one gets fixed. Much of my phones use is inthe dock in the car.
2. Although the phone initially bootted with LTE working, it eventiually lost it. As has been noted elsewhere, removing all the other APNs and only leaving the one required for your particular provider fixes this.
3. Was getting pretty bad battery drain about 5-7% per hour at idle. Turned out that fixing the LTE issue as noted in #2 also fixed this issue. Somewhat surprising since the phone is almost always on Wi-Fi anyway. FWIW, I did not have wakelocks from Google Play. Battery concumption over the last hour of idle is only .9% per hour as reported by BBS.
So now, really only issue #1 remains!
jswclw said:
3. Was getting pretty bad battery drain about 5-7% per hour at idle. Turned out that fixing the LTE issue as noted in #2 also fixed this issue. Somewhat surprising since the phone is almost always on Wi-Fi anyway. FWIW, I did not have wakelocks from Google Play. Battery concumption over the last hour of idle is only .9% per hour as reported by BBS.
Click to expand...
Click to collapse
Which BBS version do you have working with android 5.1.1? I've tried a few of the betas with mixed results, but mostly FC's.
jason2678 said:
Which BBS version do you have working with android 5.1.1? I've tried a few of the betas with mixed results, but mostly FC's.
Click to expand...
Click to collapse
I used the latest BBS, 2.1b3 I believe. Also had to flash the helper app, then install BBS again. In the end, it does work.
Is it still recommended that we deny Google Play Services' Wake Up and Keep Awake permissions in Privacy Guard? I had them denied when I was rocking the earlier unofficial builds, but I have had them unblocked as of late. I didn't notice any difference at first, but not Google Play Services is my top battery drainer again.
I notice that I had the contacts repeated. Only one of the contacts had information.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
does it works on the sgh-i747m ?
Hello everybody,
Been a SM-T311 user for 3 years and still going strong :good:
I'm just try to find the best stable and especially WORKING rom for this device.
During the last 3 years i've changed at least 4 rom, without finding out one that actually works completely.
One rom with bluetooth problems, another with youtube videos problem, another with incoming call problems...
Before reverting back to stock rom, which will be a shame (I'm actually very happy and satisfied with the options introduced in the new android version) I will like to know your opinion.
Actually I'm using unofficial LineageOS 13.0 (Android 6.0.1) which has some little frustrating problems, like ram usage, random reboot, app installation through playstore required extensive time and eventually reboot the device, and calling problem (if I have an incoming call i can't listen the other person, but if I close the call and re-answer a second time everything works as normal)
I'm ready to completely format and lose everything in my tablet, to start again with a freshly working ROM.
As I understand, AICP (Nougat) 6.0.x seems a good candidate and I will eventually live without bluetooth audio (99% of the time I use another phone in my car with bluetooth)
Thank you in advance for everyone who would like to contribuite.
Just curious to see what people use this tablet for these days. I'm trying to find a good use for mine and am coming to the conclusion that if you want what has features its going to come with issues. But Lineage is quite fast just no features.
Curious on others opinions!
Having installed a12 I was disappointed with its work (compared to stock a6). The rom works fine (except for quick settings, the curtain always lags) until additional programs are installed
Then disappointed in the A12, I decided to switch to the A11, namely the OFFICIAL latest CRDROID. It also started to work worse when a bunch of programs I needed appeared, but not so, it could be in use. However, when I tried to listen to music all night because of him, he was unloading Spotify (he seems to have serious problems with working with RAM. Of course, another reason is 2 GB of RAM)
I also had a strange bug that the tablet completely hung, and after restarting the ROM broke. The blind did not want to open completely, there were problems with the software.
As a result, I returned to a12, put fewer programs, tried to configure the kernel, the system to be more or less comfortable to use it. Of course, this is not the level of a6 or a9, but if you want Something new, cool design, why not.
In my opinion, it is better to use the 9-11 android, as well as install the kernel with overclocking, it is very necessary here.
I'm still new to using this device, so I haven't used much ROM, but it's probably in the future
From here ... > ... The best
No need to look at a high Android!
erdar said:
Having installed a12 I was disappointed with its work (compared to stock a6). The rom works fine (except for quick settings, the curtain always lags) until additional programs are installed
Then disappointed in the A12, I decided to switch to the A11, namely the OFFICIAL latest CRDROID. It also started to work worse when a bunch of programs I needed appeared, but not so, it could be in use. However, when I tried to listen to music all night because of him, he was unloading Spotify (he seems to have serious problems with working with RAM. Of course, another reason is 2 GB of RAM)
I also had a strange bug that the tablet completely hung, and after restarting the ROM broke. The blind did not want to open completely, there were problems with the software.
As a result, I returned to a12, put fewer programs, tried to configure the kernel, the system to be more or less comfortable to use it. Of course, this is not the level of a6 or a9, but if you want Something new, cool design, why not.
In my opinion, it is better to use the 9-11 android, as well as install the kernel with overclocking, it is very necessary here.
I'm still new to using this device, so I haven't used much ROM, but it's probably in the future
Click to expand...
Click to collapse
CrDroid isn't broken but it does have an odd systemUi bug likely to the system partition and other things being so outdated. Whenever restarting the tablet it will continue to respring until it decides to boot the best way to handle this is just to leave it be I've found that more often then not it will eventually start up, other times it refuses to start at all and I will have to reboot again most times I try to refrain from turning it off. Unfortunately this seems like the only way to get good features for this tablet. Wishing someone would take interest like forkLineage or EvoX perhaps
Mr.Conkel said:
"CrDroid isn't broken but it does have an odd systemUi bug ....."
Click to expand...
Click to collapse
I agree, although I prefer pixel experience (and the like).
As for the CRDROID ... My problem was that the curtain does not open, and many programs were not launched, and there was an arrow in the bar, which is displayed only when the navigation bar is two Buttons, and I had gestures enabled) Very strange, actually. It's funny that it all started after the ROM crashed .. I still wanted to try at least lineage 18.1, but after reinstalling a12 I'm too lazy
Running unofficial LineageOS 17.1. I don't really use the tablet or anything really. My touch screen doesn't really work, along with the tilt sensor. It's really slow which is to be expected. I use my Fire 7 since it's faster and less frustrating to use.
I pulled my old nexus out from the cupboard a few weeks ago and was amazed that the battery still had decent life after yrs not being used. I managed to unlock bootloader and install twrp before the micro USB charging port stopped working. I now have DotOS android 9 installed and am using the nexus as my eReader, charging via Qi wireless
Can anyone explain to me and a possible solution for this. When using Oxygen OS 13 it's fine, no issues. Issues arise with AOSP ROMs such as Nameless and Pixel Extended ROM.
So I first noticed it with my Ring doorbell.
Whenever the doorbell is pressed my gf's Pixel 6 will notify her instantly and my phone will notify me about 30 seconds later, although the "lag" is different every time.
My dad would call me on Google Meet or Whatsapp Video and say his phone rang about 5 times before I answered, even though I answered the phone immediately.
So I definitely experience a delay in being notified on AOSP roms.
I love the Vanilla Android experience and want to stay with AOSP roms but unless I can get this fixed then I don't see how until I get new phone.
Oh and i've tried turning off Battery Optimization, but that only had minimal impact. And my phone is not rooted. Can't have root as I use some apps for my job that wont work with root.
Any ideas?
I have same problem as you. Tried crDroid and Nameless. Notifications are delayed on both ROMs. One thing that helped a little was running Eva kernel GCC, rooting phone and using KTweak app but notifications are still delayed. I think that problem is with Google Play Services which should handle push notifications.
I hope that someone come here with solution.
I too have the same issue on custom ROMs. I am on OnePlus 9. I tried Unrestricted settings from app's Battery Usage. Still no help.
No ideas then?
Shame. Regardless I am sticking with AOSP. Currently on Pixel Extended trying a few settings to see if it helps.
I don't like what Oxygen OS has become. And I cannot stand the way folders work on Oxygen OS. My next phone will definitely be the Pixel series.