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
Related
Hey all good morning, what a messed up way to start the morning. So I was on my phone paying some bills, reading some manga when it powered off on me, I thought this was the known random reboot you get when flashing CM10 sometimes so I paid it no mind, however the phone has still not turned back on. I've done battery pulls, tried to boot into recovery or download and nothing is working it's just dead. I definitely didn't do anything this morning, flashed no roms nada and it had full charge shoot it was plugged in to my work computer when it happened. Someone, anyone please help me, I have the toolkit on this computer and can download anything all I need is instruction. Please help and also I've wanted the CM10 rom because I like it but it doesn't seem ready to be my daily driver as I'm having issues and have flashed different versions with it seeming to get worst while getting better. What does anyone recommend for a safe daily driver, stable, no reboots, crashes and still can be played with like CM10 for features somewhat?
Shels said:
Hey all good morning, what a messed up way to start the morning. So I was on my phone paying some bills, reading some manga when it powered off on me, I thought this was the known random reboot you get when flashing CM10 sometimes so I paid it no mind, however the phone has still not turned back on. I've done battery pulls, tried to boot into recovery or download and nothing is working it's just dead. I definitely didn't do anything this morning, flashed no roms nada and it had full charge shoot it was plugged in to my work computer when it happened. Someone, anyone please help me, I have the toolkit on this computer and can download anything all I need is instruction. Please help and also I've wanted the CM10 rom because I like it but it doesn't seem ready to be my daily driver as I'm having issues and have flashed different versions with it seeming to get worst while getting better. What does anyone recommend for a safe daily driver, stable, no reboots, crashes and still can be played with like CM10 for features somewhat?
Click to expand...
Click to collapse
I've been using ths 08/14 CM10 rom on a full wipe without much issues, but have come accross your issue on an old CM9 build last month.
For me to get the phone to boot, I removed the battery and powered it on by AC only, and then poped in the battery, and haven't had issues since.
Do you do any overclocking or undervolting? You say CM10, what release? What kernel?
Hopefully we can get your phone working once more
jeb101 said:
I've been using ths 08/14 CM10 rom on a full wipe without much issues, but have come accross your issue on an old CM9 build last month.
For me to get the phone to boot, I removed the battery and powered it on by AC only, and then poped in the battery, and haven't had issues since.
Do you do any overclocking or undervolting? You say CM10, what release? What kernel?
Hopefully we can get your phone working once more
Click to expand...
Click to collapse
Thanks for the support, I'm not sure what happened but I just saw the samsung logo and it's booted up, so now it's up and running but that kinda scared me lol. I know what you mean jellybro hasn't given me much problem before which is why I've picked it over others but this now scares me lol especially since I actually formatted my phone last friday and had to start from scratch, so was worried it was a repeat without me doing anything lol. I'm using the 20120813 release and the kernel that comes with it, I haven't played with kernels at all, is there a kernel I should look at? And I don't overclock per say I may switch the cpu performance to "performance" from time to time but that's it and no undervolting I try not to play with things I don't understand too much lol
I'd recommend you to hop on the new 08-14 official CM10, now that cm9 is released, i would imagine seeing many more frequent updates from Cyanogen himself.
I was using Jellybro and got random crashes, but so far no issues with 0814 cm10. Just do a full wipe, dalvik wipes and dirty flash cause more issues than its worth, especially with Titanium Backup you do a one click restore, and get a sms backup tool. Simple clean switch. Just make sure not to copy system data with TI, which would give you the same results as a dirty flash.
Sent from my SAMSUNG-SGH-I747 using xda premium
I know CM10 has been made "stable" on this device but I just have a few questions regarding it. My wife has been using the nightlies since the first previews were available and I'm not sure if our issues are common or something I am doing wrong.
She is currently on a nightly from a few days ago but these issues have persisted for about a month. I have done a full wipe and flash multiple times and we still have the same issues.
Skype: She can't barely here the other user and the other user hears nothing but static. I have tested with multiple other users. I have wiped data for Skype and reinstalled it, still has the same issue.
Force Close - Many apps. Happens randomly and it's not the same apps every time. I feel it is an OS issue and not an app issue.
Speakerphone is randomly activated by default. She usually has to tap the mic button a few times (deactivate, reactivate, deactivate) in order to get it switched to the handset.
Depending on what nightly she flashes the caller on the other end gets echo. It hasn't been happening with recent flashes but every couple weeks it pops up again for a nightly and then disappears.
I understand there are many issues due to Samsung not releasing sources, etc, just want to verify I am not alone. I have looked through the forums and see some people have some of the issues from time to time but I am hoping for some verification.
Thanks for everything.
I noticed the same thing a few days ago on Skype but didn't think much of it at the time.
Just checked again and sure enough I'm having the same experience you are with static.
Flashed back to stock and the problem disappears.
Must be a problem with CM10.
Ever try flashing the Stable version? Or a different rom for that matter? Maybe AOKP?
The issue existed before Stable and it exists in Stable. I just tried [ROM] AOKP(Jellybean 4.1.2)Task & Ktoonsez (11/18) and the issue with Skype exists there as well. If anybody knows of a AOKP or CM build that doesn't have any issues I would swap over. I have been wiping and flashing roms like crazy lately and I we really can't stand stock samsung rom. I may end up selling the phone and picking up something different, it's quite frustrating. Last time I buy a Samsung phone, that's for sure. They basically **** on devs.
DarthDerron said:
Ever try flashing the Stable version? Or a different rom for that matter? Maybe AOKP?
Click to expand...
Click to collapse
I see you have the same phone as my wife. Any chance you have time to test Skype on your current rom? If so thanks in advance, I appreciate it.
Sent from my LG-E973 using xda app-developers app
Thanks guys. Just going to return her to stock and sell it. Going to find a device with better support from manufacturer.
Sent from my LG-E973 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.
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
heartspains88 said:
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
Click to expand...
Click to collapse
If this has just started recently in would say it is indeed apart of the cm base, and related to kernel issue. Since the kernel devs are using cm and their kernel base most ROMs kernels have the same base, which means in a round about way they may react the same way on your device. To me, you said graphic glitch, then reboot. I would bump up your voltage little by little and see if it stops, I also would change govs in the kernel.. I'm assuming it happens on any cm kernels you've tried? Yank555 has an awesome cm kernel I would highly recommend, or even imoseyon always has a solid stable cm kernel as well.
How are you transferring the firmware? The heavy cable with the heavy plug? If so, it might have damaged your device's USB port and is causing intermittent disconnections which are corrupting the data as it is transferred. Try a lightweight cable and make sure it is firmly seated, then don't let it move during the transfer.
If this solves it then maybe look into replacement due to faulty design.
Frank
It is happening on all roms, however the only custom roms I've tried are CM based. I'll take a look at these other kernels and see if that resolves. Thanks for the help and idea's so far guys.
I've been having the same issues. Hellish reboots though. 10+ a day... Keep me posted. Thanks
Sent from my SM-N900T using XDA Premium 4 mobile app