Basicly when I reboot or turn on my g1 I have to go through reseting my battery widget and my overclock app. I have tried reinstalling and unistalling. I have even deleted the apps and the dalvik for them off me partition. Anyone run into this? I would like to fix without a wipe. I just spent the last 3.5 hours reflashing, setting up wifi and data, and arraging icons. I really dnt feel like doing that again.
Almost for got the names of the apps. The battery widget is from curvefish and the overclock is from billy chu overclock widget. !MODS PLEASE FORGIVE IF I POSED IN THE WRONG SECTION!
pistol4413 said:
Basicly when I reboot or turn on my g1 I have to go through reseting my battery widget and my overclock app. I have tried reinstalling and unistalling. I have even deleted the apps and the dalvik for them off me partition. Anyone run into this? I would like to fix without a wipe. I just spent the last 3.5 hours reflashing, setting up wifi and data, and arraging icons. I really dnt feel like doing that again.
Click to expand...
Click to collapse
Now that you mention it... I've noticed a problem with Locale. I don't use the ones that you mentioned so I can't comment. But with Locale, I use it to send texts to my girl to make sure she's up for work (three alarm clocks aren't enough but a text from me seems to work just fine). I set it up differently almost every day.
The conditions are based on time, which change depending on what time she wants to wake up by my text. So I make the changes, save twice, hit home and I should be done, right? Not always. Several times the condition didn't save and she ends up getting the text either way too early or way too late. Pretty annoying. So to make sure it saves, I have to reboot and check it on the next start up. Sometimes it saved and works, sometimes I have to try it 3 or 4 times to get it to stick. I do nothing different and I consider myself a pretty loyal user of the app. Let's put it this way... if twofourtyfouram decided to charge $20 for the app, it would suck but I wouldn't hesitate to buy it even if it doesn't always save for me. Anymore then $20 I would probably just remind myself to silence my phone so my custom Saw ringtone for my mother doesn't go off in church... again. Damn Meltus v3 audio mod!
Could be a defect in the programs themselves, OR, if you've been messing around (i.e. with apps2sd), then you could have a PERMISSIONS problem. Look around for the fix permissions script and try that.
fix permisions
lbcoder said:
Could be a defect in the programs themselves, OR, if you've been messing around (i.e. with apps2sd), then you could have a PERMISSIONS problem. Look around for the fix permissions script and try that.
Click to expand...
Click to collapse
How would I go about doing that? And use marcus' apps2sd app
lbcoder said:
Could be a defect in the programs themselves, OR, if you've been messing around (i.e. with apps2sd), then you could have a PERMISSIONS problem. Look around for the fix permissions script and try that.
Click to expand...
Click to collapse
I do fix_permissions from terminal everytime I install/update an app.
It may just be Locale, but I've never read about someone else with the same problem as myself. I've even tried removing the app and browsing to /data/ and /dalvik-cache/ to make sure there was nothing left behind.
I still get the issue but not very frequently.
logcat
I have the logcat if anyone thinks they can help. Email me at [email protected] and I will send it to them.
logcat file
its attached to the message. hopefully someone will read this thread and provide a solution to fix this that doesnt envole the words WIPE AND REFLASH! srry it had to be a zip i didnt feel like breaking up the log
problem solved!
Well after numerous emails back and forth with the devs of the apps I was having issues with I found the solution:
$su
#cd /data/data
#rm -rf (enter app name) ex. Com.xxxxxxxx.xxxxxxxxxx
MODE IS.NEED BE U CAN LOCK/CLOSE THREAD!
Related
I have reflashed the phone about three times with the stock rom and now have moved to custom ones which seem to be working a little better, but I am honestly getting annoyed with how much this phone freezes while in the text window. I have to do a battery pull every time because none of the hard buttons respond either. I have seen many posts and was wondering if anyone has found a fix to this. I might, however, have a bad phone. I did not but it from T-mobile, so if I brought it in to them would they even be able to replace it or how do I go about doing that?
otter5 said:
I have reflashed the phone about three times with the stock rom and now have moved to custom ones which seem to be working a little better, but I am honestly getting annoyed with how much this phone freezes while in the text window. I have to do a battery pull every time because none of the hard buttons respond either. I have seen many posts and was wondering if anyone has found a fix to this. I might, however, have a bad phone. I did not but it from T-mobile, so if I brought it in to them would they even be able to replace it or how do I go about doing that?
Click to expand...
Click to collapse
The SMS freezing issue is widespread in this phone, I honestly don't think you have a bad piece of hardware.
One of the solutions that seems to work most frequently is to keep the number of text messages retained in your phone down to an absolute minimum (like 50 or less) at all times. Clearing them out regularly (and from the deleted folder as well) seems to have eliminated the issue for a bunch of people. If it's critical for you to retain messages longer than that would allow, I'd suggest just backing your messages up with myphone or something similar that allows you to access them off the phone.
I know that's not an ideal solution, but it seems to work. That's the strategy I use all the time, and I've never once had the sms lagging or lockup issues that so many others report.
I've been deleting all my texts as soon as they get over 20 just to minimalize the problem, everything else will start lagging as well if I let this happen. Thanks though. I hope they get a fix for this because I love this phone.
I was haVing the same issues but not as bad as you...you can also try changing the messages too standard not threaded. you can do that by selecting all messages then menu then options...also try running titanium. go to settings/all settings then select windows default I trash mine like that for a while. but what seems to have fixed my problems was just un installing cookies home tab...I mentioned to sirphunkee that in a few days I would install cookies again to see if my problems came back.
I think this MIGHT help you id the problem.
See if removing the memory card helps.
My first unit seemed as bad as yours, if not worse.
Whenever I removed the memory card, it would run SUPER smooth, so I thought to myself, maybe a higher class sdhc would do the trick?
Nope.
There is just something defective about all the TMOUS HD2s...they just fail imho.
toreone said:
I was haVing the same issues but not as bad as you...you can also try changing the messages too standard not threaded. you can do that by selecting all messages then menu then options...also try running titanium. go to settings/all settings then select windows default I trash mine like that for a while. but what seems to have fixed my problems was just un installing cookies home tab...I mentioned to sirphunkee that in a few days I would install cookies again to see if my problems came back.
Click to expand...
Click to collapse
I unthreaded it and have not had a problem all day. Thank you
I'm having some awful slow-down issues with my N1. Like, 3 second delays between clicking widgets and their intended effect, and even longer switching between home screens (if the screens switch at all).
There's no auto task-killer enabled, I've very recently wiped and re-installed CM, and cleaned out my unused apps. I've got around 200MB of RAM free, constantly. SetCPU is keeping my processor at 461MHz or higher. This is obnoxious as balls, and I can't think of much. :s
Any suggestions?
I'm running CM 5.0.6, btw.
i have the same problem
My N1 is not rooted and I am experiencing slowdowns. When opening txt messages now take 3-5 seconds, and typing completely locks sometimes for 20 seconds. Gmail now takes 5+sec to open and other apps are also seeing this. I just had 10+ programs update themselves and all these issues started appearing suddenly. Also when exiting apps my desktop will be blank for 3-5 seconds. This just happened all within the past 2 weeks or so.
reddragon72 said:
This just happened all within the past 2 weeks or so.
Click to expand...
Click to collapse
Yeah, the issue is very recent for me too. Last week.
I am wondering if Google sent out an OTA that is prepping the phone for the 2.2 update??? The reason I say this and not point to an app is the simple fact that I have all my apps stopped completely and the issues still exist.
reddragon72 said:
I am wondering if Google sent out an OTA that is prepping the phone for the 2.2 update??? The reason I say this and not point to an app is the simple fact that I have all my apps stopped completely and the issues still exist.
Click to expand...
Click to collapse
Mmm, I dunno about that. I'm running CyanogenMod. I don't get OTA updates. Do you remember, recently, getting an OTA?
Unless it was pushed inside of a market-updated Google app (uhh.. No.), I wouldn't have got it.
Zak Jones! said:
SetCPU is keeping my processor at 461MHz or higher.
Click to expand...
Click to collapse
You set your CPU at 461Mhz?? Sure it slow down and lagging. What the point buying a 1Ghz processor phone decide let it run at 461Mhz?
Check the profile if you are not set at 461Mhz, maybe accidently make a profile setting and enable.
Or set your setCPU setting from on demand to on performance.
What kernel are you running?
Andrewtst said:
You set your CPU at 461Mhz?? Sure it slow down and lagging. What the point buying a 1Ghz processor phone decide let it run at 461Mhz?
Check the profile if you are not set at 461Mhz, maybe accidently make a profile setting and enable.
Or set your setCPU setting from on demand to on performance.
Click to expand...
Click to collapse
I think he's setting the minimum at 461 hence the "or higher" part.
Well, I can't actually help much except to suggest that perhaps you could try Kang-o-rama (see my sig) and see if that works. It's a stable and fast bundle with no apparent lag. At least I know that setup works.
If you did proceed then posted your results in that thread I might be able to assist. You shouldn't be experiencing lag with this phone... and if you still are after installing Kang-o-rama we could look at logs for you.
No promises but I know Kang-o-rama works...
Success? Sorry for the laggy reply.
JCopernicus said:
I think he's setting the minimum at 461 hence the "or higher" part.
Click to expand...
Click to collapse
Yeah, Copernicus is right, it's at a minimum of 461MHz (now 499MHz.), with a max of 998MHz, running 'on demand'.
antoniouslj said:
What kernel are you running?
Click to expand...
Click to collapse
I'm using whichever kernel comes with CM. (2.6.33.2 is specified in the relevant section of his changelog.)
djmcnz said:
Well, I can't actually help much except to suggest that perhaps you could try Kang-o-rama.
Click to expand...
Click to collapse
Yeah, won't lie, I'm sick of reinstalling all my stuff, so I don't want to do it again. If I keep having issues, I'll look into it though.
Just last night, I wiped both the data partition (factory reset?) and cleared the Dalvik(sp?)-cache. Started from scratch (without Google settings sync.), and reinstalled apps one by one. SO FAR, I haven't had the slowdown, but who knows. All I've got installed yet are the applications that I actually had desktop shortcuts to. (I didn't have very many more, but these are the ones I actually used frequently.)
Anyway, yeah, I'll see how this goes.
K, need a suggestion.
Zak Jones! said:
Anyway, yeah, I'll see how this goes.
Click to expand...
Click to collapse
Sooo, it's not going. Still experiencing the slowdown. I honestly can't think of what's doing this. Advanced Task Manager reports > 190MB free (28 processes running), SetCPU is still running at 499MHz or greater (I can't get 'show CPU to work in Dev Tools?).
Ending everything in the "All Apps" tab does not fix the problem; it's speedy for about 30 seconds, then resumes being slow, with the same problems (so maybe it's a process taking up all my CPU cycles? (But my CPU isn't scaling up like it would in that situation...))
Anything I can try doing before re-flashing and/or wiping? I'd rather avoid that, but, of course, if it's the only solution, whatever. Maybe try flashing a new ROM?
Can't think of what else to do here, gentlemen.
Get rid of SetCPU. I had it installed and it started weirding out on me, would not set the processor higher than 384 and nothing I did in the profiles would set it back to 1 GHz. After I uninstalled, my phone returned to it's normal speeds.
Zak Jones! said:
Sooo, it's not going. Still experiencing the slowdown. I honestly can't think of what's doing this. Advanced Task Manager reports > 190MB free (28 processes running), SetCPU is still running at 499MHz or greater (I can't get 'show CPU to work in Dev Tools?).
Ending everything in the "All Apps" tab does not fix the problem; it's speedy for about 30 seconds, then resumes being slow, with the same problems (so maybe it's a process taking up all my CPU cycles? (But my CPU isn't scaling up like it would in that situation...))
Anything I can try doing before re-flashing and/or wiping? I'd rather avoid that, but, of course, if it's the only solution, whatever. Maybe try flashing a new ROM?
Can't think of what else to do here, gentlemen.
Click to expand...
Click to collapse
You might not like my advice but it's likely to work:
Don't uninstall SetCPU but set your CPU min to 245 and the max to what you want. Disable profiles but select 'Set on Boot' and 'On Demand'. Do nothing else with SetCPU, leave it alone and do not use the active widget. Your current setup is crazy.
Full wipe (as you've done before) data, cache, dalvik-cache, battery, rotate and then install Kang-o-rama 0.7b1 (no, I'm not simply pushing it, I just know it so well that I can assure you it works).
Do not, under any circumstances restore any data or apps for any application with any application. As soon as you set up your Google account go into Settings | Privacy and disable "Back up my settings" and hit Okay.
Install a task manager if you like for monitoring purposes. Install SetCPU as above if you like for OC.
Install no other apps (now that's the painful part) and use your phone for long enough for you to know with certainty whether it's working as you expect.
In all honesty, if it's still broke after that then you've probably got a hardware issue. If it's working after that then slowly add your apps back until you find what's causing the problem.
Good luck, report back.
So far, uninstalling SetCPU is doing wonders for me. Y'know, over the last 15 minutes. I'll use it throughout the day and see if it keeps performing.
Space for future updates:
****ING BALLSACK. <--- First impression of Kang-o-Rama (I decided to just go for it and flash as soon as I saw it included CM.)
^^^^^^^^^^^^ That text is to be read: Kang-o-Rama is amazing. The theme is sexy, I LOVE the Desire camera, and the bundled stuff (kernel, apps, etc) are quite awesome. We'll see if it solves my performance issues.
I was getting the same thing....
Task kill setcpu and reboot it again. If you keep getting the lag then stop using setCPU.
Zak Jones! said:
****ING BALLSACK
Click to expand...
Click to collapse
It takes a twisted mind to interpret that as a complement.
Zak Jones! said:
...Kang-o-Rama is amazing...
Click to expand...
Click to collapse
But thank you!
Delete all widgets that profile your cpu in any way. Stop killing tasks with task killers. Uninstall setcpu. Set exchange email app to "PUSH". Download "Quick System Info Pro" and check what's using up Cpu.
I had the same problem and it turned out to be 2 things: SetCPU widget and exchange email app stuck in a sync cycle.
Maybe theres an ill-performing app that you installed. Since it seems you wiped your phone a couple times including cache. Did you happen to restore apps thru Titanium backup or manually one at a time thru the market.
I always wipe my phone completely and reinstall all apps manually, time consuming, but I have never had a problem.
To further diagnose your problem, see if after installing each app, try the phone to see if there are any slowdowns afterward. Again, I know this is time consuming, but trying to find the problem rather than living with it would be better.
I'm also using 5.0.6 but with no problems or slowdowns.
You can also post a logcat or look thru it yourself if you know how and see if any errors or hangups occur. Logcats are a great way to see the commands being given to your phone and this will most likely reveal your problem.
Same problem, it's annoying.
First off, I cannot take credit for finding this, I was referred to a bug report thread on the Google Android site by XDA user aweaver33, who I thank VERY much for pointing me on the right direction.
So, several of us have had this issue with various custom kernels, where after typically 24-48 hours, the phone would slow to a crawl. If you were to open an app like System Panel, you would see that the CPU load was pegged at 95%+, and speed would be maxed out. You would also see that the process using all the CPU is Android System.
The problem has to do with the file "time_in_state", which literally keeps track of how much time the CPU spends at any given speed in MHz. There is a limit to the size this file is supposed to reach, 256 bytes. Once it exceeds this size, the next time Android tries to access it, it flips out and gets stuck trying, and pegs the CPU. A lot of devs and users blamed SetCPU, and it is true that SetCPU does have an EFFECT on this issue, it does NOT cause it, and indeed the issue can occur whether SetCPU is installed or not.
The issue is brought on by custom kernels that add additional frequency steps for the CPU to choose from, which causes that log file to grow. Which is why older or stock kernels will not cause this. Some ROMS incorporate a workaround so you may not have this issue.
Anyways, the issue is explained better in the link aweaver33 gave me. I will link to the original thread I posted with the conversation we had and the link he gave. I can confirm that, using the info he gave me, the issue has been fixed. I am currently just over 120 hours of uptime with no problems.
Here is the link: http://forum.xda-developers.com/showthread.php?t=1082363&highlight=stock+kernel+gpu+
EDIT: attached the script files for those who want them. You can drop one or the other (NOT BOTH) in /etc/init.d if your rom has this folder already (creating the folder and adding it won't work), or you can download Autostart (root) from the market for free, and drop the file in /data/opt (create the opt folder). This difference between the two is one runs only once at boot, the other runs every five minutes. If you use SetCPU, you need the one that runs every five mins, as every time you open SetCPU it resets permissions on the time_in_state file.
flashable zip? not everyone is comfortable with code and scripts
If I knew how, I would. I wasn't even comfortable with it. But I was so tired of the locking up, I was willing to try anything (after a Nandroid of course). I'm not sure you *could* do this in a flashable zip. I can post the script I'm using. It only runs once after reboot, unlike aweaver's, which runs every five mins (good if you're using SetCPU, as opening SetCPU resets the permissions of the time in state file).
This script should work if dropped into /etc/init.d. *If* your ROM has that folder by default. Mine does not, so I had to download a free app from the market called Autostart which is free and very small. For that app you create a folder in /data/ and drop the script in there.
Sorry guys but I'm no dev so this is the best I can do, maybe someone else can make it flashable?
would it also be fixed by simply deleteing the log file as well rather than setting it to unreadable
It can't be deleted. System instantly replaces it.
bast525 said:
It can't be deleted. System instantly replaces it.
Click to expand...
Click to collapse
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Do you know if it is a problem in gingerbread as well?
mirrin said:
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Click to expand...
Click to collapse
I don't think you can delete it. I can't figure out how to.
mirrin said:
Do you know if it is a problem in gingerbread as well?
Click to expand...
Click to collapse
Issue 9733 is still listed as New, so either Google hasn't fixed it in Gingerbread or they just don't bother statusing their bug reports.
Why do you feel the need to delete it? If you are trying to delete it, you are likely using Root Explorer. Why not just use that to change the permissions of the file? Tap and hold, select permissions, and unchecked all permissions except for the top left one. This will stop the bug, but the permissions will be reset after a reboot, or after opening SetCPU.
I imagine that deleting the file might actually cause FC's or may cause the same bug but I dunno since it wont delete.
dyetheskin said:
flashable zip? not everyone is comfortable with code and scripts
Click to expand...
Click to collapse
I've never created a flashable zip before, but I'd be willing to look into it if the demand is really there. The problem I see is that I'd have to make certain assumptions about how everybody's ROMs are configured. It looks like the most portable approach would be to append a line to the end of /bootcomplete.inc.rc. Do people really find it easier to boot into recovery and flash a zip than to add one line to a file themselves? Personally, I'm always hesitant to flash a zip other than a full ROM because I'd be uncertain how it interacts with other changes I've made to my system.
Inc is
not bad
But. 48hours?
Sent overrow from my Optimized Inc using XDA App
I am not sure what is the problem but every te i format the s5 everything worl great, then i root ,put my cool rom, put my favorite apps. After some days maybe a week i put xposed and greenfy and swicher 3g. After one day or aome time the problem happens. I tried to delete those apps and still the problem dont go it happens even in another rom.
zocex said:
I am not sure what is the problem but every te i format the s5 everything worl great, then i root ,put my cool rom, put my favorite apps. After some days maybe a week i put xposed and greenfy and swicher 3g. After one day or aome time the problem happens. I tried to delete those apps and still the problem dont go it happens even in another rom.
Click to expand...
Click to collapse
Seems like you've started to narrow it down. It doesn't appear to be the phone per se, since the stock firmware works. Likewise you say that it happens on multiple custom ROMs, so probably not them either.
But unless someone has run into the same problem, we can't tell you what it is yet. There are still hundreds of variables. It sounds like it is one of those three apps, even if uninstalling it doesn't resolve the problem. From your description the overwhelming chances are that it's one of those. My bet is 3G switcher having some intermittent conflict.
All you can do is either avoid those apps completely. Or methodically troubleshoot them. Narrow it down from three apps to one. Then look at all of the configuration options for the app, Google search to see if it is a known bug and do a logcat to see if there the system errors help explain what the conflict is.
.
fffft said:
Seems like you've started to narrow it down. It doesn't appear to be the phone per se, since the stock firmware works. Likewise you say that it happens on multiple custom ROMs, so probably not them either.
But unless someone has run into the same problem, we can't tell you what it is yet. There are still hundreds of variables. It sounds like it is one of those three apps, even if uninstalling it doesn't resolve the problem. From your description the overwhelming chances are that it's one of those. My bet is 3G switcher having some intermittent conflict.
All you can do is either avoid those apps completely. Or methodically troubleshoot them. Narrow it down from three apps to one. Then look at all of the configuration options for the app, Google search to see if it is a known bug and do a logcat to see if there the system errors help explain what the conflict is.
.
Click to expand...
Click to collapse
can you help me?
fffft said:
Seems like you've started to narrow it down. It doesn't appear to be the phone per se, since the stock firmware works. Likewise you say that it happens on multiple custom ROMs, so probably not them either.
But unless someone has run into the same problem, we can't tell you what it is yet. There are still hundreds of variables. It sounds like it is one of those three apps, even if uninstalling it doesn't resolve the problem. From your description the overwhelming chances are that it's one of those. My bet is 3G switcher having some intermittent conflict.
All you can do is either avoid those apps completely. Or methodically troubleshoot them. Narrow it down from three apps to one. Then look at all of the configuration options for the app, Google search to see if it is a known bug and do a logcat to see if there the system errors help explain what the conflict is.
.
Click to expand...
Click to collapse
Thank you
I formated my mobile and i wont install the switcher. It might be the problem
I wont use any apps other than greenify and xposed
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.