Related
coming from cm10 nightlies, i want stock back. i miss some of the cool features that came with the phone.
what am i going to be missing from going from asop to stock?
what rom seems to be the most stable with decent battery life?
I have the exact opposite question, oddly enough. I see that CM10 nightlies are in a somewhat unstable state, as they are nightlies. I cant complain about their instabilities because of this, and that is fine. Some people say they are stable, Others tell me that since they are nightlies I shouldnt be using them as daily driver, and yet others (those posting in the thread) are having bugs and issues of the exact sort that I dont want to be encountering (like not being able to get wifi working, or google account sync issues).
So how did you figure out which nightly to put on your phone, especially when the preferred install method is full wipe/clean install?
I am also interested in the jellybean stock rom question. I dont really care for updates all the time but I'm growing tired of the random quirks and shortcomings of the tmobile stock firmware very quickly. For example, how the screen doesnt automatically turn on when you move the phone away from your face during a call, even though it does automatically turn off.
Xquisite rom by wicked. Look the the development section. He updates when he finds fixes and improvement. Plus a lot of good tweaks
Sent from my SGH-T999 using xda app-developers app
Does Xquizit include debloating? From reading the description, it looked like the goal was to remain as close to 100% stock as possible. I didnt see any mention of removal of the bloat that came with the phone.
shrimants said:
I have the exact opposite question, oddly enough. I see that CM10 nightlies are in a somewhat unstable state, as they are nightlies. I cant complain about their instabilities because of this, and that is fine. Some people say they are stable, Others tell me that since they are nightlies I shouldnt be using them as daily driver, and yet others (those posting in the thread) are having bugs and issues of the exact sort that I dont want to be encountering (like not being able to get wifi working, or google account sync issues).
So how did you figure out which nightly to put on your phone, especially when the preferred install method is full wipe/clean install?
I am also interested in the jellybean stock rom question. I dont really care for updates all the time but I'm growing tired of the random quirks and shortcomings of the tmobile stock firmware very quickly. For example, how the screen doesnt automatically turn on when you move the phone away from your face during a call, even though it does automatically turn off.
Click to expand...
Click to collapse
The latest nightly
Sent from my SGH-T999 using xda premium
I'm using liquidsmooth its fast, looks very good and amazing battery life
Sent from my SGH-T999 using xda app-developers app
Flashed latest CM10 nightly, must have been a corrupt download or something because now it flashes the "samsung" logo for a split second and then I get a black screen. I can get back into recovery, but I cant mount external SD card or internal storage. All it says is "usb device not recognized". All drivers are installed correctly, so I dont know wtf is going on. This requires further research, preferably after dinner.
I've been using the nightly CM10 for the past 3 weeks and I've had little to no issues. (And yes, I update daily.) The only reason I've considered going back to stock is for *possibly* better battery life. WiFi, camera, Google accounts sync, and everything have worked for me from the start.
Sent from my SGH-T999 using xda premium
I've done loads of searching here, heard about the *#0011# and switching Power Saving mode off, which doesn't apply to AOSP/CM based ROMs, and tons of beating my head against the wall for the past few weeks. I have "keep WiFi awake when screen off" set to "Always." I tried setting my frequency to both 2.4ghz and 5ghz only with no luck. I have tried the stock CM kernel, ktoonsez's Kernel, Lean Kernel with none of them changing anything. I have tried an array of ROMs, including CM10 stable, CM10 nightlies, Task's AOKP, Slim, LiquidSmooth, ... the list goes on.
Long story short: my WiFi will occasionally drop connection to the network and not come back up until I turn off and turn on the WiFi again. If it drops and I go into the list of signals I get, it seems to pick up the network and have decent strength, but it will not reconnect and just says "Saved" underneath the record. How long it takes before it drops ranges anywhere from a few hours to a few seconds. It does seem to happen more often than not with low signals to the router, but I've been in the same room as a router with full bars and it will still happen. I've tried different routers, different router configurations, and different networks entirely, same deal. It does not affect my cell data, just my WiFi.
I am currently trying a stock ROM to see if it happens on stock, and so far it has not occurred. I have done full wipes of all data and clean installing a new ROM, I have tried installing stock and then dirty installing to a new ROM. Nothing seems to solve the problem. I ran a logcat when the problem occurred (lost the log, sorry) and the entry from wpa_supplicant was "AP scan failed". I am at my wits end here. Has anyone had the same problem and found a solution? None of the solutions I've found so far have seemed to work.
Edit:
Stock ROM seemed to have stable WiFi.
Completely formatted phone back to virgin stock, rerooted, installed CWM instead of TWRP (really don't think this would have a difference), factory reset, wiped data, wiped system AGAIN, wiped cache, wiped davlik, installed Task650's AOKP. WiFi seems stable again. Maybe his kernel? Maybe something during wipe? Maybe CWM vs TWRP (unlikely)? I'm unsure if the problem is even solved, honestly, but so far it seems stable. Will keep this updated. I'm going to start installing apps (not from Titanium backup this time) one at a time...
oscooter said:
I've done loads of searching here, heard about the *#0011# and switching Power Saving mode off, which doesn't apply to AOSP/CM based ROMs, and tons of beating my head against the wall for the past few weeks. I have "keep WiFi awake when screen off" set to "Always." I tried setting my frequency to both 2.4ghz and 5ghz only with no luck. I have tried the stock CM kernel, ktoonsez's Kernel, Lean Kernel with none of them changing anything. I have tried an array of ROMs, including CM10 stable, CM10 nightlies, Task's AOKP, Slim, LiquidSmooth, ... the list goes on.
Long story short: my WiFi will occasionally drop connection to the network and not come back up until I turn off and turn on the WiFi again. If it drops and I go into the list of signals I get, it seems to pick up the network and have decent strength, but it will not reconnect and just says "Saved" underneath the record. How long it takes before it drops ranges anywhere from a few hours to a few seconds. It does seem to happen more often than not with low signals to the router, but I've been in the same room as a router with full bars and it will still happen. I've tried different routers, different router configurations, and different networks entirely, same deal. It does not affect my cell data, just my WiFi.
I am currently trying a stock ROM to see if it happens on stock, and so far it has not occurred. I have done full wipes of all data and clean installing a new ROM, I have tried installing stock and then dirty installing to a new ROM. Nothing seems to solve the problem. I ran a logcat when the problem occurred (lost the log, sorry) and the entry from wpa_supplicant was "AP scan failed". I am at my wits end here. Has anyone had the same problem and found a solution? None of the solutions I've found so far have seemed to work.
Edit:
Stock ROM seemed to have stable WiFi.
Completely formatted phone back to virgin stock, rerooted, installed CWM instead of TWRP (really don't think this would have a difference), factory reset, wiped data, wiped system AGAIN, wiped cache, wiped davlik, installed Task650's AOKP. WiFi seems stable again. Maybe his kernel? Maybe something during wipe? Maybe CWM vs TWRP (unlikely)? I'm unsure if the problem is even solved, honestly, but so far it seems stable. Will keep this updated. I'm going to start installing apps (not from Titanium backup this time) one at a time...
Click to expand...
Click to collapse
I've had the same issue with all AOSP based roms. There seems to be an issue with cm 10 which is the base for all AOSP and aokp roms. The touch wiz roms I've tried have no issues and you can go into settings and disable wifi sleep with them.
ak29 said:
I've had the same issue with all AOSP based roms. There seems to be an issue with cm 10 which is the base for all AOSP and aokp roms. The touch wiz roms I've tried have no issues and you can go into settings and disable wifi sleep with them.
Click to expand...
Click to collapse
That's a shame, but I suppose at least I'm not an isolated case. I didn't figure I was considering I could find other people posting about it, but all the posts seem old and never got much attention. So far task650's AOKP seems fairly stable. I haven't had it drop out on me at home yet, though the WiFi does seem to have difficulty coming up after a boot. I suppose worst case scenario I could switch to a TW ROM, but I really like the AOSP experience better :\ (minus TW's camera)
oscooter said:
That's a shame, but I suppose at least I'm not an isolated case. I didn't figure I was considering I could find other people posting about it, but all the posts seem old and never got much attention. So far task650's AOKP seems fairly stable. I haven't had it drop out on me at home yet, though the WiFi does seem to have difficulty coming up after a boot. I suppose worst case scenario I could switch to a TW ROM, but I really like the AOSP experience better :\ (minus TW's camera)
Click to expand...
Click to collapse
In addition to having wifi issues I found all the AOSP/AOKP based roms to have screen wake issues. The camera on non touch wiz based roms is also considerably slower. For now I'm sticking with the stock virgin rom - rooted with toggle mod installed. Wifi on the AOSP/AOKP based roms seems to disable when I go to bed. Then I have disable and enable for it to reconnect. I've tried 10+ roms still haven't found that was stable with the features I want. The only I didn't try was flashing a new kernel. Maybe that will solve both the wifi and screen wake issues. I would rather the rom be stable than have tons of features and being buggy.
ak29 said:
In addition to having wifi issues I found all the AOSP/AOKP based roms to have screen wake issues. The camera on non touch wiz based roms is also considerably slower. For now I'm sticking with the stock virgin rom - rooted with toggle mod installed. Wifi on the AOSP/AOKP based roms seems to disable when I go to bed. Then I have disable and enable for it to reconnect. I've tried 10+ roms still haven't found that was stable with the features I want. The only I didn't try was flashing a new kernel. Maybe that will solve both the wifi and screen wake issues. I would rather the rom be stable than have tons of features and being buggy.
Click to expand...
Click to collapse
If you are interested in running an AOSP/AOKP ROM still, give Task650's AOKP a try. After a fresh wipe, to virgin stock, to rooted stock, wipe, and then to his ROM, it seems stable. I haven't had a WiFi drop for about 24 hrs, and it seems stable. I did have some WiFi problems on the first boot or two (WiFi wouldn't be on at boot and a tad stubborn to come on, stable after it came on), but that seems to have solved itself now... I say seem though, because like I said in my OP it can sometimes take hours to drop WiFi. He does use a kernel that isn't the CM10 kernel, so maybe that has something to do with it?
I'm loading my apps back on in waves to try and see if maybe it's an app. So far it's still stable.. I'm about to start downloading all my Spotify playlists which it typically would **** out on, so we'll see. If it starts again I'll be going back to stock.
oscooter said:
If you are interested in running an AOSP/AOKP ROM still, give Task650's AOKP a try. After a fresh wipe, to virgin stock, to rooted stock, wipe, and then to his ROM, it seems stable. I haven't had a WiFi drop for about 24 hrs, and it seems stable. I did have some WiFi problems on the first boot or two (WiFi wouldn't be on at boot and a tad stubborn to come on, stable after it came on), but that seems to have solved itself now... I say seem though, because like I said in my OP it can sometimes take hours to drop WiFi. He does use a kernel that isn't the CM10 kernel, so maybe that has something to do with it?
I'm loading my apps back on in waves to try and see if maybe it's an app. So far it's still stable.. I'm about to start downloading all my Spotify playlists which it typically would **** out on, so we'll see. If it starts again I'll be going back to stock.
Click to expand...
Click to collapse
I did give that rom a try. I had the same wifi issue when I went to bed. It also happens after the phone is rebooted. In addition I was getting the screen wake issue. Task's rom is still based on cm 10 so will have the same bugs. Maybe changing the kernel to task's own kernel or the other AOSP kernel. I'll give a try one of these days. Let me know how that works out for you.
Do you guys having this problem have "Avoid poor connections" checked in the Wifi advanced settings? I don't remember if CM10 has this, but AOKP does. I expected that this setting would cause the phone to switch to a better AP if the signal was low but it seems like it just stops Wifi data completely. After disabling this setting I haven't had any issues.
I've been running CM10 nightlies with the CM10 kernel since late November and haven't had any issues with WiFi. I am on my 2nd GS3, first one returned due to phone speaker (not the speakerphone on the back) and on that one my WiFi was sketchy. Not sure if it was a hardware problem, or CM10 merged a fix close to when I swapped out devices. Either way, I use the latest twrp recovery flashed from GooManager and Formula84 10/12 Gapps. I update daily with the CM Updater, and haven't had any issues other than what is already reported to be a bug on CM (which in all reality is, nothing, since I NEVER use Bluetooth)
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I'm only asking for reference, this happened to me somewhat on CM10, and my roommate on his Stock GS3. Anyone with these issues using a Netgear router? We dumped ours for an Asus and haven't seen a problem since. I hate netgear so much...
goodtimes50 said:
Do you guys having this problem have "Avoid poor connections" checked in the Wifi advanced settings? I don't remember if CM10 has this, but AOKP does. I expected that this setting would cause the phone to switch to a better AP if the signal was low but it seems like it just stops Wifi data completely. After disabling this setting I haven't had any issues.
Click to expand...
Click to collapse
Avoid poor connections is always unchecked for me. I also make sure wifi is set to never sleep.
---------- Post added at 11:35 PM ---------- Previous post was at 11:33 PM ----------
thacounty said:
I'm only asking for reference, this happened to me somewhat on CM10, and my roommate on his Stock GS3. Anyone with these issues using a Netgear router? We dumped ours for an Asus and haven't seen a problem since. I hate netgear so much...
Click to expand...
Click to collapse
I'm using the linksys e4200v2 router. Never had any issues with any of my devices except after I flash AOSP/AOKP based roms. I have 8 devices connected wirelessly with no issues.
My router at home is a Netgear. Not sure about work. The weird part for me is that I didn't use to have these problems with AOSP ROMs, not that I remember anyways. It seems like a recent development in the past few weeks.
Still having decent luck with task650's ROM. It did happen to me once last night at home but it's been stable as a rock otherwise. If it starts happening more I'm gonna flash stock. If it continues to happen from there I'll consider it a hardware defect and go ***** to AT&T.
Sent from my SGH-I747 using xda app-developers app
oscooter said:
My router at home is a Netgear. Not sure about work. The weird part for me is that I didn't use to have these problems with AOSP ROMs, not that I remember anyways. It seems like a recent development in the past few weeks.
Still having decent luck with task650's ROM. It did happen to me once last night at home but it's been stable as a rock otherwise. If it starts happening more I'm gonna flash stock. If it continues to happen from there I'll consider it a hardware defect and go ***** to AT&T.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I just tried two roms (liquid smooth and tasks aokp). Had wifi issues with both of them after reboot. I decided to try two custom kernels (underwear and ktoonsez). Still experienced wifi saying not in range. The issue seems to be with the latest cm base which is used in all AOSP and AOKP roms. I hope this issue is fixed with the new cm 10.1 base. I guess I'll be stuck using only touch wiz roms now.
Found a great app that solves the wifi issue. It's called smart wifi toggler. Wifi reconnects after reboot now and remains connected when I go to sleep.
ak29 said:
I did give that rom a try. I had the same wifi issue when I went to bed. It also happens after the phone is rebooted. In addition I was getting the screen wake issue. Task's rom is still based on cm 10 so will have the same bugs. Maybe changing the kernel to task's own kernel or the other AOSP kernel. I'll give a try one of these days. Let me know how that works out for you.
Click to expand...
Click to collapse
It sounds like something is going wrong when you flashed the ROM. Task's AOKP isn't CM based (he cherry-picks from it, but builds from source), and I've never had a Wi-Fi issue with it.
Sent from my SGH-I747 using xda app-developers app
ak29 said:
Found a great app that solves the wifi issue. It's called smart wifi toggler. Wifi reconnects after reboot now and remains connected when I go to sleep.
Click to expand...
Click to collapse
Thanks for the heads up! I still have been having good luck with task650's ROM, but I will try this out on other ROMs!
guitarpunk8403 said:
It sounds like something is going wrong when you flashed the ROM. Task's AOKP isn't CM based (he cherry-picks from it, but builds from source), and I've never had a Wi-Fi issue with it.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I've been having good luck as well with tasks, but I don't know what could be going wrong when flashing a CM based ROM that is so consistent, unless it's either a hardware issue or something in their code base.
Sent from my SGH-I747 using xda app-developers app
oscooter said:
Thanks for the heads up! I still have been having good luck with task650's ROM, but I will try this out on other ROMs!
I've been having good luck as well with tasks, but I don't know what could be going wrong when flashing a CM based ROM that is so consistent, unless it's either a hardware issue or something in their code base.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
No prob. I'm finally able to enjoy tasks aokp now that I got the wifi issue solved with using smart wifi toggler. It's a great rom, with tons of features and customizations.
I still haven't rooted my note 2. I want to root and get custom roms but scared the roms might not have good battery like stock. I'm not sure what's you guys opinion?
Sent from my SGH-T889V using xda app-developers app
Everything gets better with custom roms
Sent from my SGH-T889 using xda app-developers app
Stock.
Sent from my SGH-T889 using Tapatalk 2
I have rooted every Android I ever owned including ny Note 2... This is the only phone I have unrooted and went back to fully stock. I am very happy with the way this phone runs stock.
Sent from my SGH-T889 using xda premium
I absolutely had in my mind I wasn't going to root etc. but im running the latest jedi rom and it is phenomenal!
Sent from my SGH-T889 using xda app-developers app
There are some cool features tied in with touch wizard specific to our pen capability. If you go custom you may lose that. So I would look more at rooting like such. Do I want root to bypass tethering lockdown from the vendor or to make backups with Titainium? Do I really need to overclock or undervolt? Do a new ROM's features negate the potential loss of pen related features
Sent from my GT-N7105
Im rooted running stock, tried jedirom 10 and had to pull the battery after every phone call. Still havent gotten an answer as to why this was happening. Went back to stock rooted and done with custom roms until this gets ironed out.....on a positive note, that jedi 10 with that kernel was flying and im very disappointed that I couldnt stick with it as it has awsome features.
zellroot said:
Im rooted running stock, tried jedirom 10 and had to pull the battery after every phone call. Still havent gotten an answer as to why this was happening. Went back to stock rooted and done with custom roms until this gets ironed out.....on a positive note, that jedi 10 with that kernel was flying and im very disappointed that I couldnt stick with it as it has awsome features.
Click to expand...
Click to collapse
I was running stock rooted since I got my phone late last December. But today I finally decided to run a custom rom and jedi 10 was it. Flashed with no problems and do not see the problem you have. The rom is really nice. Here are some features I would suggest rooting for:
1. Free wifi tethering (it's a must for me since T-mobile charges $15 for me to use data that I'm already paying for).
2. Wifi calling (good option to have in case I do not have signals) - the jedi 10 rom offers this.
3. Multi-windown (any app) - a cool feature. I don't think I will use it much though. But it's good to use to show off.
4. Samsung keyboard with auto-correct. I wanted to keep the samsung keyboard so that I can use the s-pen sometimes. But the jedi rom has the auto-keyboard switcher embedded.
??????
I rooted my phone I think but now I dont know what to do next! How do I pick a rom and where do I go to pick a rom or download one? Also what are kernals and overclicking?
SAMOANBK47 said:
I rooted my phone I think but now I dont know what to do next! How do I pick a rom and where do I go to pick a rom or download one? Also what are kernals and overclicking?
Click to expand...
Click to collapse
Before you do anything else, search "nandroid" learn all about it, and make one.
Sent from my SGH-T889 using xda premium
I was stock until about 3 days ago. I moved into the Jedi ROM. I used CWM, the non-touch version. I don't know if I'm old school or worried about a non responsive screen but eh.
Originally I'd just thought to stay stock and not rooted so I could get OTA'S. Though with a ROM, I'm already miles ahead of the game.
As another person stated, using the tethering has really been good for me. I'm paying $70 a month, $15 more for the hot spot would of been ridiculously overkill.
Also, I've never seen or witnessed a phone become so buttery smooth and perform so well. I'm happy. ^_^
Just make sure you do back ups through TiBu and do nandroids.
Sent from my SGH-T889 using Xparent Green Tapatalk 2
I rooted, went to Jedi ROM, but had issues, like screen tearing, slow response (probably aggressive underclocking) and some other weirdness. Went to Tweaked ROM, and had to pull battery after using CNN app for 5 minutes. Also phone is very slow to wake. Turning screen off makes music player unusable. I think I should go to stock, but I would love to have TSM Parts thing on it. Wonder if there's a way to install it.
Meanee said:
...Went to Tweaked ROM, and had to pull battery after using CNN app for 5 minutes. Also phone is very slow to wake. Turning screen off makes music player unusable. I think I should go to stock, but I would love to have TSM Parts thing on it. Wonder if there's a way to install it.
Click to expand...
Click to collapse
This would likely be better off reported in the Tweaked thread...
But, w/ the CNN freeze up (was this an app or website? Reading text or watching video/listening to audio?) was there any FC at all? What kernel were you using? What version of Tweaked were you running, and what sort of options did you have installed? A logcat of such an issue would be immensely helpful Also - were you charging the phone and have the MIUI battery bar active? On other phones I've experienced issues w/ video playback and that combo.
Turning screen off makes music player unusable - what do you mean? The long-press volume controls weren't working? The music stops? What app were you using to listen to music?
Very slow to wake - is there anything more specific you can offer here? Like an amount of time it takes to wake? That really shouldn't differ from stock at all - and there will always be a bit of lag there (though I never have anything more than a second or so).
And fwiw TSMParts is regrettably not an independently functional sort of apk. It requires a bunch of other edits throughout aspects of /system to actually work. But man that would be nifty
Fyi...noting what I said before, I am currently running one of Tesh's rooted stock ROMs for the international version. I can run backups, do tethering (no carrier lockdown for international), and run another kernel if I wish. It also allows me to use some of the Exposed installer tweaks to keep the Note2 touchwiz benefits and still use things like per app resultions and all apps in multiwindow.
Sent from my GT-N7105
dwitherell said:
This would likely be better off reported in the Tweaked thread...
But, w/ the CNN freeze up (was this an app or website? Reading text or watching video/listening to audio?) was there any FC at all? What kernel were you using? What version of Tweaked were you running, and what sort of options did you have installed? A logcat of such an issue would be immensely helpful Also - were you charging the phone and have the MIUI battery bar active? On other phones I've experienced issues w/ video playback and that combo.
Turning screen off makes music player unusable - what do you mean? The long-press volume controls weren't working? The music stops? What app were you using to listen to music?
Very slow to wake - is there anything more specific you can offer here? Like an amount of time it takes to wake? That really shouldn't differ from stock at all - and there will always be a bit of lag there (though I never have anything more than a second or so).
And fwiw TSMParts is regrettably not an independently functional sort of apk. It requires a bunch of other edits throughout aspects of /system to actually work. But man that would be nifty
Click to expand...
Click to collapse
I didn't really so a lot of troubleshooting. It was a CNN app. I pushed Back button from an article and got a black screen only with top bar active. Pushed power button, screen turned off. Then it stayed off. Had to do a battery pull. Not charging, no MIUI battery bar.
As for music, turning off the screen makes it stutter and slow down. Turning screen back on fixed the issue. I am guessing with screen off, clock rate is way too low to support music playback.
Very slow to wake could mean 2-3 seconds after I push the power or home button. Same thing with phonecalls. I can hear the phone ring but screen would stay black. 2-3 seconds later I can finally see who's calling.
I guess I can resolve most of these issues by tweaking clock rates, just wish I had time to read up on it.
Edit: Forgot to mention, I am on 1.4. Downloaded and flashed yesterday.
Meanee said:
I didn't really so a lot of troubleshooting. It was a CNN app. I pushed Back button from an article and got a black screen only with top bar active. Pushed power button, screen turned off. Then it stayed off. Had to do a battery pull. Not charging, no MIUI battery bar.
As for music, turning off the screen makes it stutter and slow down. Turning screen back on fixed the issue. I am guessing with screen off, clock rate is way too low to support music playback.
Very slow to wake could mean 2-3 seconds after I push the power or home button. Same thing with phonecalls. I can hear the phone ring but screen would stay black. 2-3 seconds later I can finally see who's calling.
I guess I can resolve most of these issues by tweaking clock rates, just wish I had time to read up on it.
Edit: Forgot to mention, I am on 1.4. Downloaded and flashed yesterday.
Click to expand...
Click to collapse
Hmm... my thoughts:
- That may have just been wonkiness in the CNN app - not sure if anything I did could impact something in the way you described (but of course I could be wrong).
- Yeah that is way slow - and uncharacteristic from my experiences at least
- That plus the music issue makes me wonder - are you just using the stock kernel? If so you can't do much in the way of clock rate tweaking, but I also find it curious as I've heard little in the way of issues regarding the stock kernel.
- Did you do a full data wipe before installing?
Regardless - I am sorry to hear about the poor outcome - feel free to PM me if you want any suggestions/help troubleshooting. I'm not the best at it (especially remotely), but I'll try
Sorry for the off-topic stuff OP!
The question doesn't make sense.
Rooting just means you unlock the root account on the phone to have superuser access. This is required by some useful apps (ProxyDroid, Paragon NTFS & HFS+ which lets you mount any USB stick or hard drive using an OTG cable, backup programs...). You can very well keep the stock firmware and just root it, which is what I ended up doing on the Note II.
On my previous Galaxy S2 CM10 was working like a champ, so I figured I would try it on the Note II... I think at this point it's a total disaster and completely unusable, just not ready for prime time. Bluetooth is completely broken, the camera doesn't work, the video driver has problems, and most of all you lose a lot of the cool things you get with the stock firmware (multi-windows, stylus-specific features, etc...). Good enough if you're contributing to the ROM development and testing for bugs and missing features, but painfully not ready for prime time. The big problem is that you just don't know what feature will break next and will let you down right when you need it.
So for me, it's stock until CM10.1 goes RC. But of course I rooted it because I want to be able to use some apps that require rooting.
Note that some Samsung apps (Readers Hub) detect SuperSU and refuse to run. Uninstall SuperSU and use Superuser instead, and use Voodoo OTA Rootkeeper to temporarily unroot the phone if you need to use them.
Rooted on Stock Rom is the way to go.
I stay on stock ROM for Wi-Fi calling, but I had it rooted in order to transfer application data.
Backup your efs as well, because there has been several people that have lost their imei.
So there's been a lot buzz lately about the bugs that are present in the latest build. Therefore, I'm going to maintain the thread to keep track of it all.
RULES:
-This is not a thread for feature requests. It's a thread for bugs, issues, and problems only!
-Before posting, you must swear under oath and punishable by law, that you are referring to a fresh installation and not a dirty flash (a fresh flash can alleviate a lot of the intermittent problems you may be having)
-In order to be a bug, it has to be confirmed by other users under same conditions
Please make sure to actually test bugs instead of saying yes yes yes. I will try to test each bug, but I'm relying on people's integrity as well. We don't want devs wasting time trying to fix something that isn't properly broken. So ensure that your bugs are legit and reproducible. Also, logcats where possible would be an amazing help too. I'm only adding bugs OP that are confirmed by at least a couple users. If it's not in the OP, it's not official.
Current bug list in no particular order:
Lock screen takes a while to draw
GPS works but reports 0-2 satellites only, NMEA data stream seems to be incorrect, so parsing this data may be touchy in some apps
Face unlock doesn't work
Autobrightness is choppy and slow
Pictures from camera show up in the wrong orientation from how they were taken
Bluetooth for headsets does not work, but may work connecting to GPS, etc.
Audio in skype is messed up
Gallery picture editing
Sound delay in calls
Work in progress...
FIXED (latest build)
Music skip/stutter when screen is off
Tethering is broken - M3 Build - thanks budor
No audio in video recording
Data usage/tracking does not work in the settings menu
Keyboard crashes
Current news...
Bluetooth is still broken
New build has an updated kernel with ota support
They are closing in on the audio issues
Stay tuned for a fresh build when the new monthly is released
For the record: this is on CM10.1, on the Samsung Captivate Glide, using the recent 4.2.2 update dated 2/17/2013
- Bluetooth Headset profile doent work
- Audio in video recording not working
- Photosphere unavailable
- audio stutters if screen is turned off (seems to be a CPU sleeping issue)
- Something (i am suspecting Google+, even though i am not actively using it) is filling up my SD card with gigabytes of thumbnails, which i have to delete manually
- lockscreen takes too long to appear
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts). Not a bug per se, but a symlink would've been nice?
- auto-brightness is choppy and slow
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
- face unlock doesnt work (hangs when opening the camera)
- orientation issues when taking photos: if i take a photo in landscape mode, it ends up in portrait mode in the gallery, and vice versa
Since i guess and hope many people will report bugs, and some of them will be not reproducable by others, we should have some mechanism to 'vote' or 'confirm' bugs, i guess?
All of the above...
Connecting to PC with USB, MTP mode does NOT work (it did work in Adam77root's last CM10.1 build ...)
Email - Any mail delivered into sub folders (Using Push MS Exchange) doesn't create a notification.... I miss a lot of email when sorting via rules on delivery. This is new in JB.
Some apps are deleted after reboot. (temporary fix is manually move to sdcard)
The phone connection will drop randomly and not come back until I reboot the phone. Note that I am using a Rogers (Canadian) model, if it has any relevance. Let me know how I can help you diagnose this bug.
mschweini said:
For the record: this is on CM10.1, on the Samsung Captivate Glide, using the recent 4.2.2 update dated 2/17/2013
- Audio in video recording not working
Click to expand...
Click to collapse
+1
- lockscreen takes too long to appear
Click to expand...
Click to collapse
+1
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts). Not a bug per se, but a symlink would've been nice?
Click to expand...
Click to collapse
+1, using Directory Bind as a replacement
- auto-brightness is choppy and slow
Click to expand...
Click to collapse
+1
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
Click to expand...
Click to collapse
GPS lock timeframe +1, not sure about the report
- face unlock doesnt work (hangs when opening the camera)
Click to expand...
Click to collapse
+1
- orientation issues when taking photos: if i take a photo in landscape mode, it ends up in portrait mode in the gallery, and vice versa
Click to expand...
Click to collapse
+1
yohan4ws said:
Some apps are deleted after reboot. (temporary fix is manually move to sdcard)
Click to expand...
Click to collapse
For me, some apps are weird and are missing icons: http://i.imgur.com/CNZ5Nwq.png
face unlock does not work, but it's not that important, just to mention it.
OP updated. Please make sure to actually test bugs instead of saying yes yes yes. I will try to test each bug, but I'm relying on people's integrity as well. We don't want devs wasting time trying to fix something that isn't properly broken. So ensure that your bugs are legit and reproducible. Also, logcats where possible would be an amazing help too. I'm only adding bugs OP that are confirmed by at least a couple users. If it's not in the OP, it's not official.
Sent from my SGH-I927 using Tapatalk 2
Just thought that I would mention that I've noticed that the audio stutter is even more noticeable when the phone is plugged into something using a line in instead of headphones. I'm not sure if this is a issue specific to my device, but if I use a patch cord (audio cable, but w/o the extra contact for a remote) the music sometimes stops altogether, and rarely resumes. This happens whether the screen is on or off. Bluetooth audio stream however is completely fine. No stutter even if screen is off.
Devian50 said:
Just thought that I would mention that I've noticed that the audio stutter is even more noticeable when the phone is plugged into something using a line in instead of headphones. I'm not sure if this is a issue specific to my device, but if I use a patch cord (audio cable, but w/o the extra contact for a remote) the music sometimes stops altogether, and rarely resumes. This happens whether the screen is on or off. Bluetooth audio stream however is completely fine. No stutter even if screen is off.
Click to expand...
Click to collapse
I've never had it stop on me all together.
I feel like this thread should be in the dev section, no? Flag this thread to move it if you think so
Sent from my SGH-I927 using Tapatalk 2
Please don´t throw stones, but bluetooth is or isn´t working? I´d like to try CM 10.1 but I need bluetooth working to use the phone while driving.
brunobbarcelos said:
Please don´t throw stones, but bluetooth is or isn´t working? I´d like to try CM 10.1 but I need bluetooth working to use the phone while driving.
Click to expand...
Click to collapse
2nd post ... says Bluetooth headset profile doesn't work .. this means you can stream Audio to your car's stereo, but you can NOT use your headset... I'm going to assume it's the same accross all ROMs that you can HEAR the other person talk, but the microphone via bluetooth isn't enabled.... my other assumption is that it has to do with the sound driver issues of using skype etc. where when the microphone is activated, all other sound output becomes sloooow motion. -
These are assumptions based on an under educated hypothesis .. a guess.. a shot in the dark ... based on no fact .. and hence, could be completely entirely wrong
Here's a thought, though, why don't you do a nandroid backup in CWM one evening, download the CM10.1 and install it and play with it test bluetooth and some other things, report your findings and if bluetooth deosn't work, revert back to your backup... nothing lost and everything to gain PLUS you'll be helping out the community.
gtmaster303 said:
I've never had it stop on me all together.
I feel like this thread should be in the dev section, no? Flag this thread to move it if you think so
Sent from my SGH-I927 using Tapatalk 2
Click to expand...
Click to collapse
The reason it isn't in the dev section is because it isn't actually a dev thread. The dev section is more for an actual product, whereas this is more documentation for a product, meant to answer questions people might otherwise ask in the general section.
Any of you guys use Whatsapp? It will tell you that tablets are not supported.. :/
And the main Google search app (where you can't type more than one letter from the homescreen) always closes.
Great work BTW. I just got this this afternoon. I'm loving how smooth it is
Sent from my SGH-I927 using xda app-developers app
chrisyjwai said:
Any of you guys use Whatsapp? It will tell you that tablets are not supported.. :/
And the main Google search app (where you can't type more than one letter from the homescreen) always closes.
Great work BTW. I just got this this afternoon. I'm loving how smooth it is
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Whatsapp works for me.
You can fix the google search app by disabling the hotword feature.
Snuuuuupy said:
Whatsapp works for me.
You can fix the google search app by disabling the hotword feature.
Click to expand...
Click to collapse
Yea. Sorry my bad. I had no service at that point. The app could not verify a network and assumed it was a tablet.
Thanks.
Okay. So basically I flash this firmware and before I proceed to use any of the apps I decide to update them. So while the outdated search app still had the hotwords feature on, I updated it. Thereafter, the app will close even before I could get to the setting menu. So the only way is to either use the older version or use the older version to turn off the hotwords feature and update. I know this is minor. Just thought I'd add this to a bugs thread.
And there are some speaker/microphone issues with google hangouts.
Anyone second this?
Sent from my SGH-I927 using xda app-developers app
chrisyjwai said:
Okay. So basically I flash this firmware and before I proceed to use any of the apps I decide to update them. So while the outdated search app still had the hotwords feature on, I updated it. Thereafter, the app will close even before I could get to the setting menu. So the only way is to either use the older version or use the older version to turn off the hotwords feature and update. I know this is minor. Just thought I'd add this to a bugs thread.
And there are some speaker/microphone issues with google hangouts.
Anyone second this?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Open up the older one. Don't update, disable hotwords and that new google feature (cards?). Update, should work fine.
Tethering
Tethering is broken, I didn't see it in the list. Even FoxFi doesn't work.
BACKUP YOUR EFS THROUGH FREEGEE AND/OR TWRP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a preview of CM-12.0 built entirely from CM sources. There are few modifications (listed below in features).
Features
- Settings->About Phone->CyanogenMod updates uses wfhome.net servers (my builds)
Latest Build
I have started Nightly's
Downloads
Latest Builds
http://goo.gl/kQP3f8 - Private Hosting (no ads, no waiting, enjoy)
Old Builds
http://goo.gl/Sz2K7a - Android File Host
Google Apps
http://forum.xda-developers.com/android/software/gapps-google-apps-flashable-package-t2930266
TWRP - 2.8.3.0
http://teamw.in/project/twrp2/155
Known Issues
- "No SIM Card" message on lock screen (CM12 issue)
- Built in Messenger App doesn't work right (CM12 issue)
- Nothing else that I have noticed
All changes can be viewed on the CyanogenMod gerrit.
Thanks to all who have developed CyanogenMod and the device and kernel trees for the Optimus G.
I'm using a modified version of @JulianXhokaxhiu CyanogenModOTA tools on my web server.
https://github.com/julianxhokaxhiu/CyanogenModOTA
Source
http://github.com/CyanogenMod
http://github.com/rjwil1086
The E970 and LS970 are slightly different, have you used the LS970 sources to build? The LS970 has minor differences in the camera as well as it being CDMA and not requiring a SIM card. Are these taken into affect? I am going to test because this is actually based on US hardware so I am hoping for most things to work that do not because other builds are based from international versions.
dopy25 said:
The E970 and LS970 are slightly different, have you used the LS970 sources to build? The LS970 has minor differences in the camera as well as it being CDMA and not requiring a SIM card. Are these taken into affect? I am going to test because this is actually based on US hardware so I am hoping for most things to work that do not because other builds are based from international versions.
Click to expand...
Click to collapse
I did use the LS970 sources. I have AT&T and Sprint phones (just not an LS970) so I am aware of the network differences. I am also aware of the 13MP camera the LS970 has. This is built entirely with CM sources (I'm using a fork of http://github.com/TheMuppets for vendor blobs; I added some gps blobs to get gps working). The device tree for these two phones share a lot of stuff as they are broken into 3 repositories (gproj-common, ls970-common, and ls970). The e970 also uses gproj-common and ls970-common which are about 95% of the device tree code for both phones. There is already a CM-12.0 branch on github for the ls970 so I'm assuming it was updated just like the e970. Just need someone with hardware to check it out.
rjwil1086 said:
I did use the LS970 sources. I have AT&T and Sprint phones (just not an LS970) so I am aware of the network differences. I am also aware of the 13MP camera the LS970 has. This is built entirely with CM sources (I'm using a fork of http://github.com/TheMuppets for vendor blobs; I added some gps blobs to get gps working). The device tree for these two phones share a lot of stuff as they are broken into 3 repositories (gproj-common, ls970-common, and ls970). The e970 also uses gproj-common and ls970-common which are about 95% of the device tree code for both phones. There is already a CM-12.0 branch on github for the ls970 so I'm assuming it was updated just like the e970. Just need someone with hardware to check it out.
Click to expand...
Click to collapse
Great! Sounds like you know what you are doing. I am downloading it right now and am at 20%. I will flash when done and absolutely report back.
EDIT FOR FINDINGS
@rjwil1086 GREAT JOB! The ROM is working great on my device (LS970) so I will send some feedback
PROS
1) Everything seems to work for the most part except items listed under CONS.
2) Calls and data are working from flashing, no extra steps needed to achieve calls or data. 4G coverage included.
3) Superuser is integrated (THANK YOU)
4) Camera works superb, even quality is amazing. (see cons)
5) Voicemail by long pressing one works and on other CM12 does not.
6) You can turn on "flash" while video recording so you have overhead light. Maybe I've missed that in every other ROM but that's great! (Does not cause phone to power down, see #6 cons)
CONS
1) Messaging app does not send a text from within the built in app (Quick reply works fine) I think this is CM issue and not device because it is in all CM based roms currently.
2) Swipe texting does not work with built in keyboard.
3) No SIM card appears in notification bar on lock screen (once again in other CM12 ROMS).
4) Data usage is not tracked at all, it says no apps used data right after I used the browser and the Play Store to download something.
5) NEW FINDINGS:: Phone calls will not end, pressing the end icon only makes the end option go away but the phone call is still in progress. I tried using a bluetooth headset and only the device. My work around is to enable Airplane Mode then disable it, that shuts the phone call off.
6) using flash in any camera app causes device to power off, overhead light during video recording is fine though.
7) Volume control on screen lock is not possible. You must unlock the screen to alter the volume (notable in music playing)
8) Very important!! While making a call, the phone immediately disconnects. When I call back, the other caller is still connected so it goes to voicemail. I have to ask them to ignore the first call so I can make it again. This happens every time and is very difficult to manage since I have to enable airplane mode to end the call.
On another note, I am using the Multiboot method and have this installed as primary, I haven't tested any secondary ROMs but I do not expect them to boot and that is due to a specific patch being required for the kernel that is not compatible with gproj. Also, it will not install as secondary, it fails upon flashing. The only thing I noticed is that it takes awhile longer at the boot screen to get past it than other roms. No issues though since it works to my expectations.
I will continue to use this to see if anything else comes up, but over all this is awesome. I look forward to CM fixing things upstream. Please keep those builds coming, they work.
Looks good. Once those CM bugs get worked out, this ROM will be fantastic! Thank you for this ROM! Willing to test any new updates. Seems like dopy did a pretty solid review so far.
This ROM running Android Lollipop 5.0?
RegKilla said:
This ROM running Android Lollipop 5.0?
Click to expand...
Click to collapse
Yes, CM12 is 5.0 (in this case 5.0.1)
EDIT: @rjwil1086 ...
GREAT JOB ON THAT UPDATE. I'm not sure if it was you that fixed it or CM fixes, but some of the previous issues are gone. Now this is extremely stable. I definitely recommend it to anyone with an LS970.
Fixed issues: (calls are main thing fixed)
1) Calls end perfectly fine
2) Phone no longer shuts off at flash of the camera.
3) no issues with music. (I didn't mention it before but when I would try to play music from any app, it would say it was playing but the song would not progress and there was no sound. I also attributed it to my bluetooth headset, but now the issue is gone)
4) Adaptive brightness and notification bar brightness adjustment has always worked with this ROM. (basically all aspects of brightness work)
still existing issues
1) Volume control on inactive lock screen. (still have to turn on screen)
2) Data usage still not tracked by settings/data usage.
3) messaging app will not show active send, pressable icon (cannot send text from within the app but quick reply still works) (I'm certain CM issue)
4) Swipe texting with built in keyboard (most likely CM issue)
5) Not really an issue but lock screen still says "No SIM card" (CM issue?)
Great update, more than half of the major issues have been fixed, now it seems like mostly CM issues , and not even major problems.
dopy25 said:
Yes, CM12 is 5.0 (in this case 5.0.1)
EDIT: @rjwil1086 ...
GREAT JOB ON THAT UPDATE. I'm not sure if it was you that fixed it or CM fixes, but some of the previous issues are gone. Now this is extremely stable. I definitely recommend it to anyone with an LS970.
Fixed issues: (calls are main thing fixed)
1) Calls end perfectly fine
2) Phone no longer shuts off at flash of the camera.
3) no issues with music. (I didn't mention it before but when I would try to play music from any app, it would say it was playing but the song would not progress and there was no sound. I also attributed it to my bluetooth headset, but now the issue is gone)
4) Adaptive brightness and notification bar brightness adjustment has always worked with this ROM. (basically all aspects of brightness work)
still existing issues
1) Volume control on inactive lock screen. (still have to turn on screen)
2) Data usage still not tracked by settings/data usage.
3) messaging app will not show active send, pressable icon (cannot send text from within the app but quick reply still works) (I'm certain CM issue)
4) Swipe texting with built in keyboard (most likely CM issue)
5) Not really an issue but lock screen still says "No SIM card" (CM issue?)
Great update, more than half of the major issues have been fixed, no it seems like mostly CM issues , and not even major problems.
Click to expand...
Click to collapse
Yup all those were fixed by CM developers. I saw several CDMA fixes in the ril code. I'm sure there were more elsewhere in the code. Swipe on the keyboard is disabled in CM because it doesn't work on any of my devices.
rjwil1086 said:
Yup all those were fixed by CM developers. I saw several CDMA fixes in the ril code. I'm sure there were more elsewhere in the code. Swipe on the keyboard is disabled in CM because it doesn't work on any of my devices.
Click to expand...
Click to collapse
So the 12/20/14 build fixes those bugs?
Downloading now. Thank you for this again! Breathes some life into this old phone lol.
Edit; I would just like to add; you sir, have made me love cyanogenmod once again.
I use to use CM 10.2 all the time, but honestly, when the official CM11 came out with LS970 sources, it always felt, not laggy, but not responsive. As in just sluggish. Gee Roms always ran fast on my optimus, but always over heated easily too.
I absolutely love this ROM. It is extremely fast and uses LS970 sources. I can finally leave stock confidently. Is there anyway I can repay you? I am on mobile, so I can't see much, but do you have a donation link? I'd pay to keep this going.
Fantastic job. It works great!
Never had this much responsiveness on a LS970 cm ROM before.
Edit 2: Does anyone know how to disable mobile data? I like to turn it off so it doesn't suck battery in low service areas. Thanks again.
Whiplashh said:
Edit; I would just like to add; you sir, have made me love cyanogenmod once again.
I use to use CM 10.2 all the time, but honestly, when the official CM11 came out with LS970 sources, it always felt, not laggy, but not responsive. As in just sluggish. Gee Roms always ran fast on my optimus, but always over heated easily too.
I absolutely love this ROM. It is extremely fast and uses LS970 sources. I can finally leave stock confidently. Is there anyway I can repay you? I am on mobile, so I can't see much, but do you have a donation link? I'd pay to keep this going.
Fantastic job. It works great!
Never had this much responsiveness on a LS970 cm ROM before.
Edit 2: Does anyone know how to disable mobile data? I like to turn it off so it doesn't suck battery in low service areas. Thanks again.
Click to expand...
Click to collapse
I agree, it is definitely snappier than any ROM I've ever used on this phone.
As far as data, I don't know. I tried a few widgets and shortcuts to no avail. I'm sure it's a matter of time before it's enabled in settings from CM.
I did have some partial success with quick shortcut maker. Run a search for "data" and try to use the shortcut to data roaming under "phone." What it did was say settings has force closed, but it shut off my mobile data. It caught me off guard but a reboot turned it back on.
On the plus side, battery life is pretty wicked already.
dopy25 said:
I agree, it is definitely snappier than any ROM I've ever used on this phone.
As far as data, I don't know. I tried a few widgets and shortcuts to no avail. I'm sure it's a matter of time before it's enabled in settings from CM.
I did have some partial success with quick shortcut maker. Run a search for "data" and try to use the shortcut to data roaming under "phone." What it did was say settings has force closed, but it shut off my mobile data. It caught me off guard but a reboot turned it back on.
On the plus side, battery life is pretty wicked already.
Click to expand...
Click to collapse
Even with data on the battery is good? That's awesome!
Just a heads up, the build does still have some phone issues. Can't call on first try and hangup without hitting airplane mode. Calls coming in work perfectly, but out can be a hassle.
Whiplashh said:
Even with data on the battery is good? That's awesome!
Just a heads up, the build does still have some phone issues. Can't call on first try and hangup without hitting airplane mode. Calls coming in work perfectly, but out can be a hassle.
Click to expand...
Click to collapse
From what I've noticed, it is absolutely great on battery. I'll post some screen shots. I was in and out of 3/4G. Downloaded a few files, probably 500mb worth. Played tapped out, which is a freaking battery hog. And still lasted a whole day. I did just notice that the total hours don't seem to be tracked, that's odd.
On the phone thing, I am so sorry you're still having that issue, it is gone for me. Are you sure you're on the 12/20 build? Maybe we did something different.
I flashed the 12/18 and GApps since I tried it first (then restored the backup of it because I had since flashed another ROM and neither would work as secondary on my multi boot setup) then I flashed the 12/20 build to update (dirty flash over 12/18) cleared cache's twice because I like to. And it seemed to work. That's a real bummer that it doesn't work for you. Incoming or outgoing work fine for me, for now anyway.
screen shots I'll have to post later, I always have issues doing that on my phone
dopy25 said:
From what I've noticed, it is absolutely great on battery. I'll post some screen shots. I was in and out of 3/4G. Downloaded a few files, probably 500mb worth. Played tapped out, which is a freaking battery hog. And still lasted a whole day. I did just notice that the total hours don't seem to be tracked, that's odd.
On the phone thing, I am so sorry you're still having that issue, it is gone for me. Are you sure you're on the 12/20 build? Maybe we did something different.
I flashed the 12/18 and GApps since I tried it first (then restored the backup of it because I had since flashed another ROM and neither would work as secondary on my multi boot setup) then I flashed the 12/20 build to update (dirty flash over 12/18) cleared cache's twice because I like to. And it seemed to work. That's a real bummer that it doesn't work for you. Incoming or outgoing work fine for me, for now anyway.
screen shots I'll have to post later, I always have issues doing that on my phone
Click to expand...
Click to collapse
I clean flashed the 12/20 build. Wiped everything twice because thats how I do. Had to go back to stock so I could make calls and organize a friends bday party. Hopefully this flash will be better.
Whiplashh said:
I clean flashed the 12/20 build. Wiped everything twice because thats how I do. Had to go back to stock so I could make calls and organize a friends bday party. Hopefully this flash will be better.
Click to expand...
Click to collapse
The weird thing is, it's happening intermittently for me as well. But it seems more like making calls from the first call screen. Selecting recents seems to not do it. Also seems like it happens more when LTE is on. I haven't tried switching to 3G only but it dedi definitely didn't do it when I only have 3G.
dopy25 said:
The weird thing is, it's happening intermittently for me as well. But it seems more like making calls from the first call screen. Selecting recents seems to not do it. Also seems like it happens more when LTE is on. I haven't tried switching to 3G only but it dedi definitely didn't do it when I only have 3G.
Click to expand...
Click to collapse
It just happens all the time. I'm using CWM recovery so I don't know if that effects it. Hopefully it will work out soon. That and the messaging bug. Loving the ROM so far. Once those 3 things are fixed, this phone won't see stock again lol.
(Data toggle, messaging send which IS a cm thing, and the phone issue).
Whiplashh said:
It just happens all the time. I'm using CWM recovery so I don't know if that effects it. Hopefully it will work out soon. That and the messaging bug. Loving the ROM so far. Once those 3 things are fixed, this phone won't see stock again lol.
(Data toggle, messaging send which IS a cm thing, and the phone issue).
Click to expand...
Click to collapse
I can only assume that recovery shouldn't be an issue as long as it's semi up to date. But some people are having sensor issues on all other builds and it very well could be related, I don't know enough on the subject. I will keep up on this because this ROM really is slick. I use textra for messaging but I really like the built in messenger. Google messenger is almost identical but has MMS issues. Nothing on textra, it works perfectly. So I'm still using this daily. I'm sure data toggle will go in soon. I see an APN update in the change log so I'm sure it's coming soon. I'll keep you updated.
dopy25 said:
I can only assume that recovery shouldn't be an issue as long as it's semi up to date. But some people are having sensor issues on all other builds and it very well could be related, I don't know enough on the subject. I will keep up on this because this ROM really is slick. I use textra for messaging but I really like the built in messenger. Google messenger is almost identical but has MMS issues. Nothing on textra, it works perfectly. So I'm still using this daily. I'm sure data toggle will go in soon. I see an APN update in the change log so I'm sure it's coming soon. I'll keep you updated.
Click to expand...
Click to collapse
Thank you!
Whiplashh said:
Thank you!
Click to expand...
Click to collapse
Give today's build a shot. I just made about 10 phone calls to various numbers from various locations within the dialer and all connected the first time, and disconnected fine.
There is still no data toggle, but data is now being tracked (or at least showing that it was previously tracked) I also do not see any apn settings but that might not have been an update for our device that I saw.
Messaging still does not send from within the app but quick reply is fine (I use Textra SMS and everything works in it)
If there's anything else you want me to check just say the word. I wonder if it's a cache issue with the dialer or something causing the phone to misbehave, but it seems to be working fine now.
dopy25 said:
Give today's build a shot. I just made about 10 phone calls to various numbers from various locations within the dialer and all connected the first time, and disconnected fine.
There is still no data toggle, but data is now being tracked (or at least showing that it was previously tracked) I also do not see any apn settings but that might not have been an update for our device that I saw.
Messaging still does not send from within the app but quick reply is fine (I use Textra SMS and everything works in it)
If there's anything else you want me to check just say the word. I wonder if it's a cache issue with the dialer or something causing the phone to misbehave, but it seems to be working fine now.
Click to expand...
Click to collapse
That's one down. Like I said, I love this ROM. The camera is AMAZING. I'll test it and see what happens.