So I've been having a bit of trouble with my t989 lately, when I try unlocking the phone I will either get a black screen (the lock screen will appear for a split second before going blank if I hit the lock button again) or it won't track my finger movements on the screen. If I manage to unlock the device I end up seeing numerous graphic glitches ranging from the bar at the top w/ the clock/battery meter just gone and the keyboard not working.
I'm runing CM9.0.0 because I had issues with 10.2 (battery wouldn't charge) and 10.1.3 (similar to my lock screen issues but not as severe, still agitating) and also 9.1 which had the same exact issues as I'm having now. I've tried installing with different gapps but the same thing happens. The phone will work for a day or two, then the glitches come. After resetting, everything is normal for a day or so, then it's normal a few hours, etc. The time is getting narrower between reboots and it's a bit frustrating.
Does anyone know what I could be doing wrong, if anything? I flash via twrp and wipe, then install the rom, then install gapps, then reboot, wait 20min, reboot, and go about my business w/ the setup and such. I would be fine going back to 10.1.3 but jellybean roms and snapchat don't really like to work together on this phone for some reason. It's really the only app I use because it seems like the only way my friends want to communicate nowadays, so I'd prefer to stay on ics if possible...
If anyone can give any insight I'd really appreciate it
greenghoul said:
If anyone can give any insight I'd really appreciate it
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
meekrawb said:
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
Click to expand...
Click to collapse
I'll give that a try. Odin is just the program used to root originally, correct? Also, I want to stay on ICS if possible. So after doing that I'm going to try CM9 again and see how that works.
Anyway, the past few days I've been using AOKP mr2 milestone 1 and it's been okay. For some reason the battery life is bad even with juice defender and a task killer taking care of things. In a matter of minutes after clearing tasks I'm down from ~350mb of ram free to 60. Is that normal with that rom?
I'm not sure what to do at this point. I'm not the best with technology but i figured i was smart enough to figure this out...
bump.
I still haven't tried flashing w/ odin yet. Does anyone know where I can find a gingerbread stock rom? I've been looking for a while and can only find the jellybean one. Since I want to stay on ICS what I want to do is go from gingerbread and up to that rather than downgrading from the jellybean stock rom if that makes sense.
Related
Alright so not even a week ago got my Nexus coming from a Charge so don't know if maybe there's something I'm missing or overlooking, but when running stock then Liquid Smooth 1.4 I have a signal and data (even though I have poor signal strength, don't know if that might be part of the problem.) So when trying to flash any other rom/kernel combination I won't have a signal and I'll start roaming and won't connect to data. I've looked and couldn't find anyone else with the same problem. I've tried AOKP, MIUI.us, Black Ice with Franco, IMO Lean, Popcorn etc. I did a clean install and have the newest radios (even tried the leaked 404 radios) but to no avail. I'm hoping there's something I overlooked but I dunno. ANY help would be MUCH appreciated as I would definitely like to try out some of these awesome roms (not that there's anything wrong with LS) because that's the whole reason for getting rid of my Charge (lack of development) And no, none of the roms I flashed were GSM versions. Thanks in advanced to anyone who can help!
Well that's interesting... my first thought would have been that the activating screen at the beginning after every flash takes a little more "juice" or power to get a reliable signal, but if you're going back to LS and it connects fine every time, then it couldn't be that... have you tried going back to stock and seeing how your phone reacts to that?
anton2009 said:
Well that's interesting... my first thought would have been that the activating screen at the beginning after every flash takes a little more "juice" or power to get a reliable signal, but if you're going back to LS and it connects fine every time, then it couldn't be that... have you tried going back to stock and seeing how your phone reacts to that?
Click to expand...
Click to collapse
I know that before I flashed LS there were no signal/roaming issues. That's actually a thought I had today at work and was going to use my nandroid from before LS when I was still stock. Also I am going to try flashing from stock. Didn't think it would be an issue coming from LS as long as I wiped everything but we'll see. Got my fingers crossed and if anyone else can think of something it might be please feel free to let me know. It's frustrating to want to try out some new rom goodness and can't get service/roaming... Thank god for nandroids
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
So here's what I've discovered.
As of now, on stock 4.1.1, the phone runs smooth when audio is screwed up. The moment touch sounds work again (or the moment I install SoundAbout to fix it) it starts lagging like crazy. Is this a hardware thing? After switching roms, kernels, versions of Android, flashing stock and locking the bootloader nothing has worked.
_________________________________________________________________________________________________________
So I'm having this strange issue that I don't really see mentioned previously (based on my multiple searches)
My phone was running fine until I flashed Paranoid Android (The last Jellybean 4.1 Release). On this ROM i was getting some insane lag, sluggish performance. I'd swipe on the home screen and get a huge delay or the phone would read it as a long touch and bring up the wallpapers option. Opening folders and the app drawer had some serious slow downs. It was a real mess.
I assumed the phone just didn't play well with the ROM so I flashed over to Bugless Beast. The odd thing is that the problems persisted. I would get just as horrible performance and the same sluggish visual effects and stuff. Specifically I remember even the audio slowing down and being choppy (touch sounds) until they automatically disabled themselves and the ROM ran smooth for a bit but returned to the sluggishness again.
So last night I restored to stock flashing the stock image and relocking the bootloader. Rooted, unlocked, flashed recovery again and loaded up Bugless Beast and the issue is still happening. Even got my first random reboot on Bugless Beast today after it slowed down really bad. Now I've noticed that when touch sounds disable themselves so does media audio (while the ringer and notification sounds still work). This is pretty much why I'm convinced it's a software problem and not a hardware one.
Basically I just wanted to know if anyone's experienced something similar and found a way to fix it? Probably going to reflash to stock tonight
EDIT: Well it seems like the audio thing might be a hardware issue. SoundAbout fixed that but I don't see how my audio jack could have been damaged in between flashes.
EDIT 2: Current State:
- I tried flashing just the system img (multiple times) and the lag returned
- I just flashed a 4.2.1 ROM just to see what happened. Touch sounds are back which means my headphone jack fixed itself. Still EXTREMELY slow.
- And just like that headphone jack screwed AGAIN but no more lag? Any reason for these two things to be related?
Bump. Any help? Still happening, though not as common, when I flashed stock
Could it be a hardware problem? Though it would be odd for a hardware issue to show up after flashing a rom. How long have you had the phone before the issues started?
Have you tried the official 4.1.1 image?
If so, do problems go away?
If you are using ports you have to expect bugs.
Let us know
Sent from my Galaxy Nexus using xda premium
Try flashing just the system.img a few times in fast boot with a reboot boot loader between. I was having slow boot up and random performance issues on full stock until I flashed that partition with the stock image (3 Times to be precise). I no longer have the 5 minute wait for the Google logo to disappear, and overall much snappier. Apparently something was leftover from previous restores/downloaded OTA updates.
Sent from my Galaxy Nexus using xda premium
I'd suggest you stop messing around with multiple ROMs and start trying different kernels. Kernels will impact performance much more than any specific ROM will. Try either an updated version of leanKernel (assuming your sig is accurate) or a different kernel all together. Others have had luck with franco, trinity, etc, etc.
Had the same problem on my GSM GNex yesterday. Flashed a ROM combination (Xylon 4.2.1 + Lean Kernel 5.0) and had this lag.. everything would lag and FC.. tried a full wipe as well but didnt work..
Changed to another AOSP Rom (UDK 4.2.1 with linaro kernel) and its fine now..
Oh and i also changed recovery from 6.0.1.5 non-touch(that i flashed yesterday) to CWM 6.0.1.9 touch..
Not sure if this helps but thats what worked for me.. I suggest going back to a ROM that worked for you in the past.. and also try formatting your SD card and run the phone without putting back your data for a while..
@rlb81 - Starting to think it might be a hardware one but at this point I'm not sure of anything. Only had the device 3 months.
@tincbtrar - Yeah I flashed the official 4.1.1 image and the problems are still there. Ridiculously sluggish and the audio problems. In fact, on stock 4.1.1 I just had this issue where I'd turn the screen off, the animation would be really slow, and then I'd get a black screen and wouldn't be able to wake it up. Did a battery pull to boot it again and the same exact issue the second time it turned on.
@Winesnob - I'll be sure to give this a try. Thanks so much! This is a really odd issue and I've never experienced it on any of my previous android devices (Fascinate, Incredible, Thunderbolt, even the old HTC Vogue)
@Cilraaz - Currently just trying to get stock running properly so everything is locked right now. Can't remember but I'm pretty sure I tried the newer lean kernel when I flashed back to bugless.
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
Thanks so much to all of you guys. If you have any other input it'd be greatly appreciated.
+1 on try different kernels, my phone seems to love lean kernel. I switched to tiny kernel for a few days and every so often, a simple task like opening tapatalk would take up to 30 seconds, and everything would become unresponsive. Nothing but smoothness on lean, give some different kernels a try.
Sent from my Galaxy Nexus using Tapatalk 2
I tried Winesnob's method and I THOUGHT it worked. Was running smooth for a good amount of time and just now back to the really choppy mess it was before. In fact it just got frozen on the lock screen and went to a black screen again.
This is killing me. The headphone jack thing seems to be a hardware issue anyway so I emailed Wirefly about getting a replacement. I feel like they'll avoid that though and I'll be left with this.
Gonna try some other things tonight. Wish me luck
EDIT: The thing gets so choppy that notification sound get choppy and crackle. This is insane. I'm fully stock minus the unlocked bootloader right now
EDIT2: Flashed stock image and touch sounds came back. This is getting really weird. Lag is still here though. Really bad lag
Bumping again now that I've sort of pinpointed the issue. Lags with touch sounds enabled and headphone jack works / soundabout installed with touch sounds on.
Currently the phone's headphone jack is screwed up, I installed soundabout, disabled touch sound and no lag.
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Ahh thanks for the heads up
Would it be wise for me to try going back to the ROM that started the problem? Maybe that'll do *something?
Again, from what I saw, everyone had some luck going back to the rom that caused the problem.
There's a tool in the developer thread called "super duper wipe" that seems to have fixed the lag for ones having the issue. I'm not sure how it works, but If you can take it apart and look at the zip, it may point someone in the right direction.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
The dev thread in the DROID incredible 2 forums.
Sent from my Incredible 2 using xda app-developers app
SkinnyT said:
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I took a look at that super duper wipe script...looks interesting but not necessary on our phone.
Im starting to think you may have a hardware issue if you cant flash stock images and get everything back to normal. Maybe a relock and then unlock?
i just did this cause I had a SIM card issue...and naturally it wiped my data completely.
solarpolitiks said:
...
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
...
Click to expand...
Click to collapse
turns out my lag problems weren't gone completely until i wiped /System before flash.. Alot of ROM's out there have a /system wipe script, but the one causing my FC's and lag didn't, so it was installing the new system files on top of the old ones and possibly causing a conflict.
it could the same for you
Yeah I've recently tried unlocking again, formatting system before a ROM flash and I still get lag. Now it's more that it will last a day without the lag and just magically come back the next day. Headphone/speaker issues still exist. Wirefly completely ignored my first email so I sent them another one. Hoping for the best.
Completely lost on what this could be
anyone see this thread?
http://forum.xda-developers.com/showthread.php?t=2029246
I have random lag on my vzw nexus and i think its io related and nothing to do with the kernel.
Sent from my Galaxy Nexus using Tapatalk 2
I'll check out that app but like I've mentioned. Lag seems to be coming from sound. After installing soundabout to get the speaker working again I get some nasty lag. Disable touch sounds and I have no lag. Disable the sound effects on twitter - no issues with the app. WireFly said I'm still under manufacturer warranty through my carrier and it sounds like I should be covered. If Verizon tries anything to get around that they'll be willing to do a three way call to make sure I get the replacement. I'll probably end up with a refurb but hopefully it'll beat this stupid issue.
Just stopping in to say thanks to everyone that tried to fix the issue but Verizon is sending out my replacement device today and I'll be sending this one with the faulty headphone jack back.
Problem solved!
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.
Well ATM its working.. But lately the lag on my device makes it stutter so bad it freezes up then slowly comes back. Then sometimes the screen goes black and my device won't do anything.. The screen doesn't come back on. I have to hold the power button and sometimes volume buttons together to get it to restart to be usable.
I have only experienced this on 5.0.x roms 4.4.4 never did this
Ideas? Suggestions? Thanks
Sent from my Nexus 7 using XDA Free mobile app
I've never had those issues on any lollipop ROMs (at least not for this device).
Personally I'm not a big fan of CM, have you tried any other ROMs and/or kernels? Have you flashed a custom kernel or adjusted any kernel settings that could be causing this? Are you using any mods (like Xposed)?
I'd suggest trying out some other ROMs (possibly even just rooted stock) and starting out with a clean flash, with no mods/kernel changes initially, and see if you still have the issue.
PrizmaticSmoke said:
I've never had those issues on any lollipop ROMs (at least not for this device).
Personally I'm not a big fan of CM, have you tried any other ROMs and/or kernels? Have you flashed a custom kernel or adjusted any kernel settings that could be causing this? Are you using any mods (like Xposed)?
I'd suggest trying out some other ROMs (possibly even just rooted stock) and starting out with a clean flash, with no mods/kernel changes initially, and see if you still have the issue.
Click to expand...
Click to collapse
I'll give that a try.. I haven't done anything to it because upgraded the bootloader to like 4.04 and installed CM12 on it. It ran so good till like a week or so ago and now its just trash. A case with a magnet for sleep mode wouldn't have anything to do with this would it? But first things first, I'll try a simple 5.0.2 rom and see what happens.
Thanks