I'm having a few issues with my G2 and was thinking about doing a "Factory Reset". I'm currently running Stock G2 rooted with S-off. Will I have to Re-Root after the Rest?
*I'm currently having issues with:
1. not being able to change my wallpaper at all, thru built in wallpapers or thru gallery selection.
2. Recently, since the forced upgrade to the "New Market", the overall performance of my phone is "Jittery" at times. (the jitter is really noticeable in menu scrolling and games like angry birds, very frustrating!!!)
I reloaded the "Old Market" via Titanium and it seem to fix the problem for about 10 minutes before the "New Market" loaded up again. I can't seem to nail down this jitter issue and has prompted my factory reset decision. Is there any way to keep the new market from auto loading? Any input would be greatly appreciated!
xblue95 said:
1. not being able to change my wallpaper at all, thru built in wallpapers or thru gallery selection.
Click to expand...
Click to collapse
What steps are you performing when trying to change your wallpaper?
- via Gallery > Set As > Wallpaper
- via Home Screen > Wallpapers
This happens to me on occasion, and often I have to perform the process more than once to get it to stick. Sometimes I've had to reboot the phone to make it stick. I don't recall experiencing this problem on my previous MT4G or MT3G, just on the G2 and I'm running CyanogenMod 6.1.1 Stable.
xblue95 said:
2. Recently, since the forced upgrade to the "New Market", the overall performance of my phone is "Jittery" at times. (the jitter is really noticeable in menu scrolling and games like angry birds, very frustrating!!!)
I reloaded the "Old Market" via Titanium and it seem to fix the problem for about 10 minutes before the "New Market" loaded up again. I can't seem to nail down this jitter issue and has prompted my factory reset decision. Is there any way to keep the new market from auto loading? Any input would be greatly appreciated!
Click to expand...
Click to collapse
I don't believe you can prevent the Market from auto-updating if you're still running with a stock ROM. Have you thought about flashing a different ROM, seeing as you've already rooted your phone? Performing a factory reset may help but it means you have to install/download everything to your phone again. You could try clearing the cache on the apps you're having issues with, and you can do this by going into Menu > Settings > Applications > Manage Applications.
no you will not have to re-root after a factory reset.
Thanks for the input guys! I usually use the (Home Screen > Wallpapers) way to change my wallpaper. I haven't tried any ROMs yet because I like the Stock Rom minus the blotware just fine, If this "jitter" problem persists after the "Factory Rest" maybe I'll try one. I don't relish the thought of reloading everything, but with Titanium it's not to bad, plus this jitter thing might be a conflict between the New Market and some other program I'm running. This might help weed it out....we'll see!
The "Factory Reset" has worked wonders so far, no jitters and I'm able to set wallpapers again. I did have a problem with the New Market automatically downloading all the apps that where previously installed. (after the reset, the old market came up the first time I selected market, then the new market loaded and started downloading every app) I had to go in and stop downloading on each app. I run with "auto updating" deselected on all of my apps, I found this very frustrating, I like to keep track of my updates. Anyway I've been slowly adding back in my apps to see if any jitter pops up, so far so good!
My questions is as my title explains.
I just used the shiny new root tool to root my phone, so of course the first thing I did was boot up Titanium Backup and restore all of my apps and some of my settings.
I made sure that I was pretty careful not to override any system apps/settings, or at least so I thought.
Everything is working fine, except that now all of my toggles are completely gone.
Notification drawer: Missing
Quick Settings Panel: Missing
Settings -> Display -> Notification Drawer: Missing
Was just wondering if anyone had any ideas, or if I'm forced to do a reset and restore again :/
Nevermind I fixed it. I used Titanum Backup to wipe my two Settings Storages and that worked.
Just thought I'd post that in case someone else does the same thing.
I generally only do restore of apps, then afterwards certain ones I will restore the data, like games Angry Birds etc. You may have restored some mod app or something that overwrote those items? not sure. But going from one device to another its a bit risky restoring app and data in my expereince.
*ah, glad you got it
highaltitude said:
I generally only do restore of apps, then afterwards certain ones I will restore the data, like games Angry Birds etc. You may have restored some mod app or something that overwrote those items? not sure. But going from one device to another its a bit risky restoring app and data in my expereince.
*ah, glad you got it
Click to expand...
Click to collapse
Agreed. Never a good idea to try to restore Settings (or really ANYTHING other than user apps) when going cross-ROM, and especially cross-Device. Sometimes you can get away with it if the roms are based on the same origin (i.e. a modified stock rom from stock), but if there's ever any changes to the available settings (nearly always the case), there's a huge risk.
Glad to see you fixed it.
Hello good Samaritans,
So my issue is that since I tried moving via SmartSwitch my conversation history from my iphone 4s back up to my new Samsung Galaxy s5, there are issues with the stock messaging app. At first it would not let me scroll properly the list of conversations (jumping back up), and the history of those conversations (jumping back down). I don't know if it's because I already had new messages on that phone beforehand. Rebooting would make the problem go away temporarily, but then it'd be back. After I deleted the "SmartSwitch" folder from the phone manually, the jumping hasn't happened again (so far) but I think the stock messaging app is still much more laggy than it was before I started using that infernal NotSoSmartSwitch. Also, strangely, most of the conversation history I transferred from the old phone disappeared, but not all.
Has anyone had similar experience? How can I restore my phone's lost innocence (that is, how do I get rid of any leftover harmful effect of PrettyDumbSwitch, such as the lagging), preferably without resetting the whole phone?
Thanks!!
- Jenny
Jenny666 said:
Hello good Samaritans,
So my issue is that since I tried moving via SmartSwitch my conversation history from my iphone 4s back up to my new Samsung Galaxy s5, there are issues with the stock messaging app. At first it would not let me scroll properly the list of conversations (jumping back up), and the history of those conversations (jumping back down). I don't know if it's because I already had new messages on that phone beforehand. Rebooting would make the problem go away temporarily, but then it'd be back. After I deleted the "SmartSwitch" folder from the phone manually, the jumping hasn't happened again (so far) but I think the stock messaging app is still much more laggy than it was before I started using that infernal NotSoSmartSwitch. Also, strangely, most of the conversation history I transferred from the old phone disappeared, but not all.
Has anyone had similar experience? How can I restore my phone's lost innocence (that is, how do I get rid of any leftover harmful effect of PrettyDumbSwitch, such as the lagging), preferably without resetting the whole phone?
Thanks!!
- Jenny
Click to expand...
Click to collapse
Well, I didn't read everything that you wrote because you're not using paragrahs for some reason. Which made your post too hard to read. But if I got the gist of it, you don't like the effect of smart switch on your SMS app. And you want to know if you can completely revert the smart switch settings.
The best way to revert settings is to restore a backup. If you didn't make a backup, that is something that you should take time to organize.
Simply turning off smart switch should stop it. But some apps also require that you clear the app and system caches. So go to Settings > Applications > Application manager > all > smart switch. Assuming that you can find it (sometimes apps show up under somewhat different names), choose clear cache. Then clear data. The latter step is basically setting the app's user settings back to default.
Then go to recovery mode (ensure that your phone is powered off, then press and hold volume up + home + power) and choose wipe (system) cache from the on screen menu.
Should you have ongoing problems and no backup to restore.. then the last resort would be to do a factory reset and /or reinstall the stock firmware with Odin or Kies. The former erases user files and defaults settings. And the latter will replace all system files.
.
That was bloody difficult to read
Sent from my SM-G900F using XDA Free mobile app
Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!
DrPhant0m said:
Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!
Click to expand...
Click to collapse
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..
TheAfroSamurai said:
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..
Click to expand...
Click to collapse
I do run some (several) xposed mods and wanam/gravity box mods, and have been for quite some time on several devices. A string of bizarre events like that hasn't happened though.
It is strange, though, that I did install XToast just last night. This is an xposed mod that gives you more control over the toast messages received under different circumstances. Could be the culprit... not sure. I think I'll disable it and go back to BurntToast, a mod that does similar stuff.
Maybe switching from one to the other borked something?
Thanks for the input.
I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.
armadiljo said:
I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.
Click to expand...
Click to collapse
Thank you for the information. I kind of suspect that Titanium Backup had something to do with my problems, as well, since it happened right around the time that a scheduled action was to take place. I think that TB was still in the middle of the previous operation at 2am when it tried to start the next one at 2:30. This has never caused a problem before, but maybe it was at the wrong place at the wrong time, as odd as that may sound.
Your problems seem to be a more constant hassle. Especially the parts about granting SU access several times. I'm leaning toward the fact that your external SD card might interfere a little. External memory is handled a lot differently in kitkat builds, which CM11 is. In newer custom ROMs, there are attempts made to "fix" it... but in your case, maybe it was counter-intuitive.
The issue is that, to paraphrase... Kit-Kat imposes a lot of data access restrictions on external media. So... if you create a file in one app... you can't modify that file in another. That's a bastardization of the whole thing, I'm sure... so look up the particulars from someone more qualified than I. haha
If I were you (and I had a few hours to burn)... I'd back up everything on your external card and your internal memory (a good idea in any case),
clear EVERYTHING and reinstall the latest versions of everything without the external card in your phone. See if you still have issues. If you don't, then the card might be a problem. Then, wipe the card and put it back in your phone, and let your phone reformat it. At that point, copy your backed-up card data to your external card in whatever way is best to keep KitKat from messing it all up again.
Luckily, I don't have issues with my external card, except for the fact that, say, if I want to put a picture of my son as my wallpaper or notification shade background... if I pick a file from the card, it won't load after I restart my phone. For stuff like this... make sure that you put the pic ON YOUR PHONE STORAGE. Consider it like this... you wouldn't have a lot of luck if your PC's desktop background or screensaver ran from the CD drive, as opposed to your hard drive.
@DrPhant0m
I already went to that process of backing up, wiping and so on. Actually, I already did it twice.
The first time, I cleaned my device, installed latest versions of everything, went through the restoring process. But most of my mentioned issues still existed.
The second time, I cleaned my device again, did about exactly what you mentioned, but I restored some older versions of the ROM, SuperSU and Titanium Backup Pro. And right now, my issues are gone!
Actually, I didn't realise there are so many KitKat-related issues with SD. Maybe my pictures indeed are/where stored on a faulty SD. But it's reformatted now, and it works. And I actually don't know if that picture is stored internally or externally, I selected the picture with/by Google Photo. No idea how it handles is
I'm not saying Titanium certainly will be the bad guy, but I'm quite sure it plays it's part in it. Other issues are caused by the custom ROM. In the last few months, developers of that ROM don't give a **** about solving issues, and introduce one new feature after the other, most of them still highly experimental. Maybe that's another problem I can't control at all
I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6
Michele31415 said:
I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6
Click to expand...
Click to collapse
Every time you do a backup it does this? That's bizarre. Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund.
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.
DrPhant0m said:
Every time you do a backup it does this? That's bizarre.
Click to expand...
Click to collapse
Yes. It is.
DrPhant0m said:
Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund..
Click to expand...
Click to collapse
No, I don't mean upon restoration. I mean I take a full backup (user apps + system apps), go off for a cup of coffee, come back, see that it completed OK, exit TI, and then I see that my background is back to the Samsung default and it I open something that needs keyboard, the keyboard is also back to Samsung default. I guess it was never enough of a bother for me to go to the trouble of buying it and then complaining. I figure that for free, I can put up with a minor annoyance.
DrPhant0m said:
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
Click to expand...
Click to collapse
I can see where you're thinking, but it happens right after *doing* the backup. I haven't even had the need to do a full restore yet, so I don't know what that would do.
DrPhant0m said:
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.
Click to expand...
Click to collapse
It's very odd, that's for sure.