Today I got a small update presumably to fix some minor bugs and stability issues, but now my Tab is hanging on a screen with a process bar and it won't get past the 28%.
Is there something I can do about this or do I have to wait for the battery to die and then hope it still works?
I looked through the manual but can't find anything about resetting it.
This happened to me and I restarted the download. Worked fine the 2nd time. It did stand on a couple percentages for what felt like a couple minutes though. Good luck.
Unfortunately it's not the download but the installation. So I can't just restart something.
Installing via Kies worked for me, however I had to re-root and CWM.
Related
here are some observations:
Every so often the hardware keys stop working. (soft keys seem fine) Quick fix is put unit into standby then unlock and keys work again.
Lookout Mobile: while doing a backup the system shuts down for some reason.
I just upgraded my wife's g-tab yesterday to G-Harmony. She hasn't had any of the issues that you mentioned.
From what I can tell from the main thread, you need to completely wipe the gtab before flashing the rom. Here's (Basically) what I did.
Formatted each and every mount point
Cleared each and every cache
Connected to my computer via USB
Flashed the Rom in.
Booted and let it sit about 20 minutes before I did anything.
Downloaded a Term emulator and ran V6.
Everything pretty much seems to be ok. Every once and a while she experiences an issue with an app or two after it sits running for a long period of time but a reboot seems to fix it.
Hope this helps.
Other issue observations...
After loading G-Harmony on my wife's tablet this weekend, I've noticed a few things (complaints from her).
* After running for about 1 1/2 - 2 hours, system will get very slow and eventually just locks.
* Browser simply goes to a white screen
* Audio stops running (I found a thread that said to turn off GPS and reboot. I've tried that, but I don't know if it has made a difference yet.).
That's all for now. Is anyone else seeing anything like this?
There is a new ics rom by jamcar. Try it out. I did and it runs very good.
Thanks.
I'll take a look at it. Not sure if my wife will give up her tablet or high scores (again) but I'll see how she reacts. ;o)
Hi;
I apologies in advance for the long thread, but I want other users to notice the symptoms I faced maybe someone else will benefit from it.important parts are marked in blue
MY galaxy s3 is only 4 months old....I got tempted by rooting and getting all -other- features such as fast recharging, sound hack, trying new roms before they are officially released...etc
anyhow, my phone's troubles showed strange symptoms quite shortly after the second rom being installed....
at first I was not fully aware of the required rooting steps, until I use the galaxy toolbox that rooted my phone easily for me...
then I started noticing the phone would start and everything but noticed (root user notices) take time to show up after boot, it would take approx. 1min then they will show very fast...after that everything is normal so i figured the processor is a little bit loaded...
few weeks later I started using CWM's backup &restore feature , noticed that when I go back to the official Rom, it lags, a lot! , I have to restart the phone at some points because it will stop responding...I started checking processor load and was surprised to see normal non harmful rates...so I forced apps to be closed once I exit them.
few roms and flashings later, the phone started restarting it self randomly,like an old car heating up, it would restart few times then get back to normal state....this would happen whenever i try to change anything in the rom (CM10+nightlies build)
few days ago, whenever the phone received or made a notification sound, I would pick it up and find it turned off! I turned on again and use it normally , no issues....after this happening for 2 times, the phone just died ...PIT partition is non-readable/writable anymore :crying:
I noticed the night this thing happened that, when I restored the rom, it took a longer time, and something was not found but the rom booted normally....
now my phone is in service and they are overloaded with service-warranty requests, so they haven't checked it yet (it has been there for 3-4 days)..I used traingle away on the current rom, no flash counter appears and the binary is official, but the rom appears as custom
notes:
*from the beginning, every step I made was a trial and error to me, I tried rooting once (manually) and I didn't figure it out,until i saw the toolbox that made it easy,,,the first root was amazing, but I rooted again after rom crashed and seems I used a different root that started all that trouble.
*All the mentioned above I believe were symptoms, that I didn't care about since the phone was acting normally after those occurring..I think I should've spotted them earlier.
*There have been 2 overheating incidents, one happened when I forgot the phone in my pants and by mistake i ticked "load new videos from subscriptions in youtube and the phone sucked up around 3gbs that day...it was really really hot when I got back to it.....the other one was when I went to sleep few days ago, I put it under my pillow, woke up with the phone overheated and restarting continuously "might've been doing this all overnight!"
*I insisted -although it was clearly troublesome to my phone- on installing Siyah kernal on every rom "always the latest one", sometimes the phone would keep restarting and I would have to restore a previous rom, sometimes it would go without issues, this happened more oftentimes during the last few weeks and CM10 nightlies offers dialy updates and I had to flash siyah back after every update...now I'm writing it and feeling stupid!
*Official JB roms caused the phone to hang a lot, so I kept using CM10+siyah kernel till the last moment.
now, what I would like to know is:
1- why does that chip get affected?? I never flashed a 3/4 part rom, just using CWM....
2- I decided (if) the phone gets fixed on warranty, to not to root again, I'm having a million guesses as the reason why this happened, including the fast recharging, the continuous flashings and testing (although all are stable roms, only official and CM10 roms), the overheating incidents....etc....I would like to know what you guys think.
If you had read the faqs and guides first you would not have the trouble .
Like
at first I was not fully aware of the required rooting steps
from the beginning, every step I made was a trial and error to me
I tried rooting once (manually) and I didn't figure it out,
>> basic CF Root is simple as it gets .
jje
Hi Everyone,
Recently my phone got crazy!
I used it as stock for a long time, until 3 weeks ago when it started being slow (a few weeks after updating from 4.0.4 to 4.1.2), crashing and getting stuck a lot.
I did a factory reset, not before I rooted it and backed it up with Titanium Backup. That's where things took a turn for the worse.
The factory reset didn't solve anything. Phone kept on crashing.
Next I tried to install a custom ROM (Samsung JB based) and a custom kernel. UI responsiveness got much better, of course, but it didn't prevent the phone from crashing. Tried different kernels and still, nothing.
Yesterday I did a full NAND wipe using ODIN and reinstalled everything using HydRx-D ROM. Things actually got a little better, and the phone UI gets stuck much less frequently.
Still, this is very frustrating, and I can't find a solution anywhere.
I'm attaching a logcat from this morning. The phone worked perfectly for 2 hours straight. Read a few articles, made a few phone call - nothing out of the ordinary. Then it got stuck right after a phone call ended.
Now you probably ask why do I always say that the UI stucks. Well, it always starts with being very laggy for a few seconds and then the foreground app gets stuck, but then I can still swipe down from above to see the notification panel and it always gets stuck on the way down. Also, it mostly gets stuck after a phone call. There was this funny case where I had a phone call using my bluetooth headset, and the phone actually got to BOOT SCREEN while I was still talking. When I finished talking, I had to hard reset the phone to get it work.
I'm really lost about this. If it was my PC I'd definitely know what to do about it, but my experience with Android ends with this phone, my TF101 and a couple of other phones/tablets I got to play with.
Thanks in advance for everyone who's willing to help.
Re: GT-I9300 IU stucks randomly
This unfortunately sounds like the kind of thing that happens before the sds strikes.
Will have a look at the log but I'm no expert in these matters,I suggest you read the sds thread and compare symptoms
Stock Samsung galaxy note i717.
First thing I noticed was that it crashed at 40% battery. I restarted it and it said 0%. I thought maybe I was mistaken but it has crashed at various battery levels between 30-50%.each time when it restarts it says critical battery level and is at 0%.
I don't think it is the battery. (mainly because of the upgrade issues listed below) it charges pretty quickly. I have had the phone about 18 months and never really had any issues. I went through and deleted a bunch of apps (specially the "power" hog apps). I have a lot of free memory (internal and external). I did order a new battery but wont be here till next Friday or Saturday.
ALSO, at startup it says there is an update that cant continue. I read some posts and tried to check for apps that are upgrading couldn't find any... in app manager (in settings) the at&t software update is running and I cant stop it.
if I connect to keis and try to update or upgrade firmware it will download the package and then CRASH.
I am really trying to avoid a hard reset.
Please help, any suggestions are appreciated.
Randall
[email protected]
more info
also, after the first time it crashed... I charged it. and the date had changed to Dec 31, 2011. 11am.
I got the phone Sep. 2012.
this is also a reason I don't think it is the battery.
Thanks for looking.
Randall
Just curious why you don't want to do a reset?
You can save your apps and data with a nandroid BU to your external SD card.
Although, restoring a back up from a corrupted system might be a bad idea.
Why not root the phone, and install something better?
done.
Update.
I ended up doing the hard reset and still had the updating issue and the crashing problems.
I installed the new battery and have discharged it and fully charged it 4 times without any crashes.
the Samsung update continues to run and gives me the "failed" warning every restart.
But at this point I am happy that it isn't crashing.
Thanks to all who suggested battery!
Randall
After waiting for a couple of months updating to A12 we have done this yesterday.
We received first a update to A12, later the C13 update.
Now I'm facing the current problems:
When rebooting the phone, the first 15 minutes everything works flawless, but after that:
Phone becomes laggy
Camera app stops working
Video's are not playing normally, green screen on video display, or even not loading/playing at all
In-app video's not playing normally
If we restart the phone, everything works well again for some random minutes, and then the problem comes back again.
I have tried to figure out which service/app could cause these problems but no luck so far.
Do you have any idea what could cause these problems?
Bummer cant help u but.......ive done update from oos11 to 12 last week and all working well.
Maybe do facory reset and start new over ?
Ive done dirty flash with ota and it works well.
Thanks all for the reply, excuse for my late response.
After one night not using the phone it works flawless again. I guess there were some update background processing issues.
Give it a day is my advice if someone runs into the same problem.