I recently tried to install Foliomod v1.3d on my Folio, but after installation everything became slow, so slow that the tablet was almost unusable because it almost didn't respond at all, there were moments when it responded but they came and went quite fast and with long periods in between.
One thing that really annoyed me was that I couldn't even get into screen settings to change the brightness of the screen, when I pressed Display under settings it instead went to some simcard phone settings.
And when I tried changing the security settings and apply a Draw Pattern the process just crashed.
I keep hearing that Foliomod is supposed to be so much better then the stock firmware but I'm not seeing it, what am I doing wrong?
try reinstall again
1.factory reset
2.install 1.3d
3.factory reset
4.install testpatch1 and testpatch2
hope this help you.
Testing it now
I can at least set brightness now without a problem
But still when I try changing the security settings and apply a Draw Pattern the process just crashes.
I have just reinstalled and applied the patches after I first did a factory reset
Going to use it like this for the rest of the day and see how it goes, but really annoying that I can't set a Draw Pattern.
Blame Toshiba for this not FolioMod I guess that this could be dued to drivers
issues (not yet updated).
It happens to me too! I just kill everythink and start all over again.
It happens to me sometimes more and more rarely, I kill process and restart too. Everything is find after.
Things seem to be working
It seems that everything is working smoothly now just except for not being able to set a draw pattern, not sure I follow how this i Toshiba's fault when their firmware doesn't have that problem.
But things seems to be working better and I'm getting much longer battery life with FolioMod, which i excellent.
Related
I am experiencing random lock ups and freezes. It happens especially when I receive texts and incoming calls after about 30 minutes of no use. WiFi does not work either. It is very annoying and frustrating as I lose the text or miss the call. I have to reset the phone to get it working again. Sometimes it takes several resets.
EDIT: Other random tidbit...after playing with the phone a bit more, I have found that the phone functions perfectly when plugged into the power outlet-WiFi, texting, incoming calls...Maybe it has something to do with the power settings when not plugged in?
Is anyone else experiencing this?
Does anyone have a guess at what might be the problem?
I am running:
SPL 2.47
2.42.50 radio
DCD Custom 3.2.6
I have never had this problem until about a week ago. I am wondering if it is a hardware issue as I have tried re-flashing several times. It will work well for a few hours then act up again. I am thinking about relocking my phone and taking it in for service, but that is a last resort.
Thanks in advance for any help.
same thing happened to me. It started ever since i switch out for a new battery though. I seriously think it's my battery that causes these random freezes.
hmmm...it does seem to be a battery issue as it works while plugged in. Is there any way to reset the battery somehow?
Freezes here too
I've had my phone freeze twice in the last two days. Yesterday at work, connected via activesync, when I disconnected the screen wouldn't come on. Then today I was connected to the wall charger, disconnected and the screen wouldn't come on again. Had to remove the battery both times to get the phone working again.
My experiences
When the 6800 came out I liked it so much that I hooked my entire family up with one and I have seen more problems than a lot of people. I just thought I would share some of the freezing problems I've seen and what I've dont to replace them. And if the device is not freezing when it is plugged into the wall is the screen off like in idle, or is it real dim and still up? And one great thing you can do to reduce daytime freezes is to leave the device off at night when you charge it (if you can stand to do that), or at least soft reset when you grab it to start the day.
1) The most common reason for lock ups that I've seen is memory drain. It is caused from programs you've installed that continually run in the background. The biggest killer is recieving calls when the phone has been sitting at idle too long or trying to run activesync or an internet browser.
Fix: You can try to go back and remove the programs that you've recently installed till you lack this problem, but the ultimate fix is to hard reset.
2) Some registry edits have poor efects on the way the phone performs and this is when it seems everything is good, you are keeping the memory clear with a task manager, yet it still freezes in the middle of doing something.
Fix: Every titan seems to act a little differently than others. The only time I hack the registry is when one of my family members phone is having an issue, or when I get bored and I want to mess around with my own's performance. The remedy for this is installing the stock carrier rom and then moving to a rom of your choice. Read the posts too. Make sure the radio is compatible with the rom. Trust me in this forum you can find anything.
3) Memory boosting software like memaid or oxios close apps are great, however, with some programs they interfeer with each other and cause problems.
Fix: Forget this memory programs. Find a rom with good memory management.
Animez: That is how mine started...now it does it at least 6 times a day.
Sweeny: Thank you for your detailed response. I do not think it is memory drain as I use x-button and maintain my task manager quite frequently. I have not made any registry edits except for the DCD kitchen (3.2.6), arcsoft, and carrier cab I have installed...
Question: Does the registry get wiped on a reflash or do I need to hard reset to wipe the registry? I don't really trust myself all that much fiddling with the registry unless I know what all the strings do.
bdlane said:
Animez: That is how mine started...now it does it at least 6 times a day.
Sweeny: Thank you for your detailed response. I do not think it is memory drain as I use x-button and maintain my task manager quite frequently. I have not made any registry edits except for the DCD kitchen (3.2.6), arcsoft, and carrier cab I have installed...
Question: Does the registry get wiped on a reflash or do I need to hard reset to wipe the registry? I don't really trust myself all that much fiddling with the registry unless I know what all the strings do.
Click to expand...
Click to collapse
A hard reset or rom flash will wipe your registry since it's included in the new rom and also stored in the hard reset rom. So if you screw it up, worse case you hard reset, or reflash with a new rom/same rom, doesn't matter.
You can also back up your phone prior to making any changes, and if you screw up, hard reset and then restore the backup.
BTC
Ok, so I have a rooted Vibrant on stock firmware and I've been having a problem with my screen becoming unresponsive. It originally happened on a smaller level when the phone was newer and unrooted, however the problem has gotten much worse. I've done a factory reset of the phone along with a nandroid backup of it before the problem was severe, yet it comes back just as strong.
I already went through the problems with the no wake from setcpu, even thought it was my lock screen becoming unresponsive until I disabled it with NoLock. Also, I have the Logcat live wallpaper, and usually when you tap the screen, you can see the system processing the information, however when the problem occurs there is no response on the logcat live wallpaper. The phone doesn't freeze at all though. All the soft keys still work perfect as do the volume and power buttons.
Any ideas, tips, suggestions that might help me narrow down this problem? Could it be from a bad version of busybox? Autokiller maybe? I have it set to strict(was previously on aggressive) but no change. Maybe Autostarts is causing something to freeze up. Thanks for any help. Seams like these phones have alot of wake up issues.
I would reflash back to stock with Odin and see what happens when you don't have task killer, set CPU, etc. Also, be careful with autostarts
So I removed Autostarts and rebooted, same deal. I did a factory reset and still the same. I just unrooted a few minutes ago and the problem seams to have gone away. I'm gonna leave it like this for a bit without installing any apps and see what happens. Is it possoble I have a bad root.zip file or bad version of busybox? Doesn't make sense to happen when I have root, then go away when I don't. Any reason it could cause this? I'm really close to sending the phone back, but don't want to waste my time if it's just a bad root file or user error.
Well I don't know for a fact, hopefully someone more knowledgeable can chime in. Maybe when you are unrooted, changes made by autostarts no longer have the permissions to affect anything. Personally I would use Odin (have done it twice already) and start from scratch. But then you risk accidentally screwing up the phone if something goes wrong.
I removed Autostarts and rebooted just to make sure the changes took effect though. Even did a factory reset. Those removed all apps that required root access and the problem was still so bad it took me an hour to get the screen responsive again. Once I did get into my phone I booted into recover and unrooted. Restared the phone and now the issue seams to have gone away. Touch screen is very responsive now which leads me to believe it was something that had to do with the root file i'm flashing, or possibly busybox. Very very strange.
Hopefully someone much smarter than me could give some insight as to what could potentially cause the touch screens to just stop recieving signal. It's just bizarre that the phone continues to run fine, just not the screen.
Sunday, I started having a problem where my phone (AT&T Galaxy Note 2) would bring itself out of the lock screen without me touching anything. The screen will stay on for 10-15 seconds and then shut off again. It will then stay off anywhere from a few seconds to a few minutes.
Very odd, right? I figured I downloaded a bad app that was causing the issue. I removed practically every app I could (I wasn't going to go through all of them to see which had permissions to bring the phone out of standby). It still kept doing the same thing.
So I did a hard reset on the phone. That should clear everything, right? The problem still kept happening.
I start thinking maybe it's a hardware issue... EXCEPT for it doesn't happen when the phone is in Airplane Mode! Which brings me back around to thinking it's some rogue app, but it still happens even when there's nothing but the default software installed from after a hard reset. It can't be the power button or a bad proximity sensor if it doesn't happen in Airplane Mode, right?
So I took it to the AT&T store and I didn't expect much. The one guy tried to play with my settings and didn't find anything wrong. He took it to the manager in the back room and the manager said I should do a hard reset (ignoring the fact that I told his employee I already had done so twice).
I've looked for answers online. The ones I've found I've tried. I've removed all applications. I've changed the screen time outs. I've even downloaded a Lock Screen replacement program. I've tried using anti-virus to scan for problems. It starts to happen again immediately after I perform the hard reset. I've moved the brightness settings. I've removed the S-Pen thinking it might be causing issues. I've turned on and off motion options. I've turned on and off wi-fi, GPS, screen rotation, multi-window, etc. Power Saving mode doesn't help. Blocking Mode doesn't help. The only thing that works is Airplane Mode.
I have NOT tried rooting my phone. I'm scared to do so, even though I'm a UNIX admin and a techie and shouldn't be scared of something like this.
Has anyone ever experienced this? I'm running whatever the normal, latest AT&T android version (4.1.2) for the Note 2. This is killing my battery and reducing screen life (is that a big deal though? I don't know).
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Macowski said:
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Click to expand...
Click to collapse
Since you've not modified your Sola in any way.
Give this official method a try.
http://xperiafirmware.com/component/content/article/2-uncategorised/29-sony-update-service
OK, this is really weird - after getting the 4.2.2 update, my phone reboots itself every night, not 100% sure it's exactly the same time, but it's been while sitting in my pocket or on the table, not even in use. At first I assumed it was Zooper, which I had installed right after the update, but I disabled it yesterday and got the reboot again tonight.
I even checked my Tasker to make sure some auto-reboot profile hadn't installed itself!
Any hints about how to diagnose this? Do I have no choice but to remove apps one by one? Most of the apps I run are the same ones I run on my TF300 tablet which also has 4.2.2, so don't know if it could be an app.
Did it again tonight and it is the exact same time - 9:19pm It's also interesting is that this is about the time of day I did the update to 4.2.2 It's like some daily thing going on. It must be some new app applied by default by the update, I've disabled some of the obvious new apps.
Does anyone know if I do a factory reset will it go back to 4.1 (which worked fine for me), or will it stay at 4.1?
PhysicalEd said:
Did it again tonight and it is the exact same time - 9:19pm It's also interesting is that this is about the time of day I did the update to 4.2.2 It's like some daily thing going on. It must be some new app applied by default by the update, I've disabled some of the obvious new apps.
Does anyone know if I do a factory reset will it go back to 4.1 (which worked fine for me), or will it stay at 4.1?
Click to expand...
Click to collapse
the Factory reset will erase all ur Apps and will stay in 4.2.2 ......
Looks like this update has really screwed up my phone. After a couple of more nights of trying to disable more apps, and trying to catch the error with logcat (nothing that makes any sense in the log, no error or crashes preceding the reboot) I decided to factory reset.
It rebooted again tonight, about 24 hours after the factory reset.
Also, intermittently now the power button will not suspend the phone, though I can hold it and reboot, I don't know any other way to put it to sleep.
Looking at the log some more, the only thing that gives any hint is that there was Location Services activity before the crash. Googling around about my problem showed there was a bug in Location Services early in 4.2 but the claim was that it was fixed. I guess tomorrow night I'll try turning off Location Services as well.
PhysicalEd said:
Looks like this update has really screwed up my phone. After a couple of more nights of trying to disable more apps, and trying to catch the error with logcat (nothing that makes any sense in the log, no error or crashes preceding the reboot) I decided to factory reset.
It rebooted again tonight, about 24 hours after the factory reset.
Also, intermittently now the power button will not suspend the phone, though I can hold it and reboot, I don't know any other way to put it to sleep.
Looking at the log some more, the only thing that gives any hint is that there was Location Services activity before the crash. Googling around about my problem showed there was a bug in Location Services early in 4.2 but the claim was that it was fixed. I guess tomorrow night I'll try turning off Location Services as well.
Click to expand...
Click to collapse
The update may have screwed up somewhere in the middle, you could try to re-ruu your phone or unlock the bootloader and flash a custom rom, also the thing about the power button not putting the phone to sleep or doing anything than reboot on long press happened to me on each and every custom rom and I never did any OTA, got my phone, unlocked bootloader and flash away from sense, my hboot is still the one that it came with, but for me that thing happens really randomly, like once every 1 or 2 weeks, and when that happens for me the volume buttons stop working also till reboot, I was thinking I was the only one facing it so I kinda decided not to talk about that as I saw no one say anything about it, but I am also one of those for who the phone turns off exactly when my phone goes to 6% battery whatever I do, on whatever rom I am and even in the recovery, so I was thinking that maybe vodafone modified something on it, that's an other reason I didn't say anything about the buttons becoming unresponsive...
So what I would recommend is to re-ruu your phone or go to a custom rom (or if none solves anything the phone may have some kind of hard brick).
Just to help out anyone else who ever has this problem.
It was not location services.
I can see clearly in two logs an HTC process crashing. This seems to cause a cascade that leads to reboot.
I contacted HTC tech support, they suggested I boot up in a recovery mode and try to wipe data cache. They were surprised to find that attempting to do that caused a reboot.
So as Ranomez suggests above, they want me to re-do the update with the RUU when they release it, which they said would be "soon" last weekend.
On the other hand, my battery life after this update is fantastic, so I've decided I can live with this to not have to worry about recharging by mid-afternoon!