Related
I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed
I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.
what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.
Try to flash a custom kernel and see if it the problem is still there
can you tell me or give information what's is 'flash custom kernel' ?
I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.
Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.
Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4
Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...
Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.
Anyone???
Maybe theres another forum that this problem should be posted at??
I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.
hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...
Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).
Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.
hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you
madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.
try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know
my turning off issue went back and it's getting every time more annoying, I don't know what to do...
I have samsung galaxy tab p1000, india.
I am experiencing a problem with touch screen.
Once it starts working, it works perfectly fine with no glitches or any problem but once it goes to sleep mode, it may or may not recover from the sleep mode. When I press the power button, the screen comes but i m not able to unlock it or used.
Initially this problem used to occur rarely but now it is very rare to get my touch working.
I have tried hard reset / soft reset / changing the firmware (approx 20 times) but m not able to make the touchscreen working reliably.
Have also flashed miui ICS, aokp , firmware from samfirmware , tsar300, but no use.
As far as i appreciate this is a software glitch as the touch screen are not able to load everytime the tab wakes up. So, if some body could correct this problem or suggest a solution.... it would mean a lot ..
continue
I was just working out things. When i flashed stock firmware ddjm2, i had a comparatively stable system and improved touch response, although the frequency has reduced but the problem still exists. Any help would be apperciated, i am really frustrated,
thanx in advance
It may be a kernel issue. Have you tried Overcome's kernel/ROM?
tried overcome kernel also, no use.....
It sounds like a software/firmware problem, but if you're still having issues on stock kernel & ROM, it may be a hardware issue...I've never had any issues with touch on my tab...
bigz1981 said:
It sounds like a software/firmware problem, but if you're still having issues on stock kernel & ROM, it may be a hardware issue...I've never had any issues with touch on my tab...
Click to expand...
Click to collapse
thanx bigz1981, one more thing discovered today.
once i flashed fresh froyo 2.2, it works fine but when i connect it to internet, something is updated which results in touchscreen showing above abnormal behaviour. This time after installing the firmware, I switched off the network, lets see if this solves the problem. Nyways thanx for the advice.
Also, i now remember that previously I updated my "tsp update" by dialing that *#____#* number, Which had failed. All this may be result of that. Can you throw some light on TSP,
1. is it touch screen ******,
2. whats wrong in updating it.
3. Was it trying to update through internet, since I was not flashing anything at that time.
4. Is there anything known as touch screen firmware , from where can i update it.
Thanx dear, for all the effort putin by you.....
I also request some senior administrator of the forum to show some way in this darkness...
from the developers, i wanna know,like we have device drivers in case of computers ,
1. we must be having some drivers for thetouch screen ,???.
2. Can this driver be loaded everytime the tab wakes up from sleep.
3. Can we shift loading of this touch screen driver higher in the booting sequence.
I am not a android nerd, but i know some basics of windows. Please guide the correct way. Thanxxxx
Just another input for processing, around 8hrs earlier i had again flashed my tab with ddjm2 foryo2.2, and disconnected from internet. The tab worked fine. I operated it for around 40 times waking up from sleep. It worked perfectly except 4-5 times. I am not able to understand,, what is there that is spoiling the firmware, once it starts updating through internet.
Hello .....
i came up to the forum ....with some expectations .... . ....
moderators , administrators pl listen,....
I saw a similar thread, but try to download ILITEK Touch Utility from the Play Store & see if this helps with your issue.
Dear,
I have the same issue!! very odd. I was a long time without using my tab and then I found out this issue few weeks ago. I've installed 2 applications (angry birds space and juice defender) right before the issue, no new rom updates (I'm still using the euro rom update on my t-mobile tab done 2y ago), however not sure if any automatic update has been performed on the apps. After deleting these 2 apps, issue still persists.
Let me know if someone found a solution.
B. Regards,
Marcel
happened to me when google market is updated to google play
Hi, everyone,
to cut to the chase, here's my problem (video):
They don't allow me to post video since I'm new here, so please check it out on YouTube, it's called Samsung Galaxy S GT-I9000 weird OS problem? (by Getz01)
I used my phone just like any other day, took a few photos while battery was almost done (about 20% left), and then it started breaking all of a sudden in the focus settings menu, and so on.
When I switched to the start screen, this strange occurence from the video appeared.
I tried turning it off, and then turning it on again, I tried taking out the battery, and reducing RAM (I thought it might not have enough of it).
It's Galaxy S I9000 model, I use stock Android that came with it. Phone was bought completely new in a licensed store last year, its OS wasn't meddled with, or anything like that. I like to keep things new, I mean, not to touch its software or hardware unless I have to, like it seems now.
Version: 2.2
I9000XXJPP
Kernel ver. : 2.6.32.9
[email protected] #1
FROYO.XFJP9
Any advice/help is more than welcome!
That is really wierd. I've had an SI for just over 2 years and never seen anything like that. It seems like you have a problem with the digitizer. Have you installed any apps prior to the problem occuring? If yes, uninstall them. If no, then you should maybe back up everything and do a factory reset. If that doesn't work I don't know what to suggest.
Getz01 said:
Hi, everyone,
to cut to the chase, here's my problem (video):
They don't allow me to post video since I'm new here, so please check it out on YouTube, it's called Samsung Galaxy S GT-I9000 weird OS problem? (by Getz01)
I used my phone just like any other day, took a few photos while battery was almost done (about 20% left), and then it started breaking all of a sudden in the focus settings menu, and so on.
When I switched to the start screen, this strange occurence from the video appeared.
I tried turning it off, and then turning it on again, I tried taking out the battery, and reducing RAM (I thought it might not have enough of it).
It's Galaxy S I9000 model, I use stock Android that came with it. Phone was bought completely new in a licensed store last year, its OS wasn't meddled with, or anything like that. I like to keep things new, I mean, not to touch its software or hardware unless I have to, like it seems now.
Version: 2.2
I9000XXJPP
Kernel ver. : 2.6.32.9
[email protected] #1
FROYO.XFJP9
Any advice/help is more than welcome!
Click to expand...
Click to collapse
It seems that you have to reinstall the rom, backup anything with titanium backup app and reinstall, i hope that helps
you can follow this tutorial to reinstall: http://forum.xda-developers.com/showthread.php?t=1583026
I have tried with the factory reset (I've made the backup of the phonebook as the most important thing) and the problem still persists.
I've tried to "squeeze" gently the limits of the screen and it did help a bit, but then it got back to the same.
I recently hard bricked my LG G4 and I was given this phone by someone I know. The phone had a cracked lcd which has since been fixed.
I reformatted to phone back to stock firmware, DOK2. And. I followed the instructions in how to root and install twrp to then ultimately install a custom ROM. Got all that and I have a custom ROM and I am rooted. But the phone lags like crazy. I am trying to type now and I am tapping faster than the keyboard actually acknowledges. Also, if I try to watch Netflix or even an embedded video from the browser, the video "hiccups" every 8 seconds or so.
What I have done.
I wiped the entire phone, including internal SD and external. I did this twice and I Odin stock twice. After I tried the custom rom and experienced the lag. I started from square one again. BTW, the lag happens on stock ROM, too. I have tried Ovrdrv and tek hybrid on both I have SU 2.52 installed and I tried beast and emotion kernels. The lag is real. Maybe this phone is designed to work in this manner when compared to my G4,rip.
On a side note, this phone was given to me in not the best shape. I mentioned I changed the LCD, but the phone's back button and fingerprint scanner don't work. It is also missing the stylus, but that's not a big deal for me. The charging port works fine and so does the recent button and both the back and recent light up. At this point I am thinking it's a hardware issue and it's conflicting with the software somehow. I downloaded different keyboards but they all do the same. I can type maybe 5 short words before it freezes for about a second.
Videos playing directly from device also lag like streaming services, but mp3 and music do not lag.
I can't help with the Note, but did you brick the G4, or did it die because of the known hardware issue? Those phones are dropping like flies. I had one that recently fell into a boot loop out of nowhere. AT&T replaced it, no questions asked. LG has acknowledged a hardware issue. Bad connections on the mobo, I think. I sold the new one to buy the Note. Didn't really like the G4 anyway!
How long did you allow to settle before you wrote this post? The phone needs a couple days to settle before it runs optimally. Did you install any apps or mods such as xposed?
Hi all,
I am completely running out of things to try and do now.
After installing Android 7 on my Note 5 I had the strangest issue that i in general have never seen on a phone. The screen is simply black (which isnt that strange) and the phone is fully functional. Bare with me, after reseting it multiple times so it would finally come on the screen goes crazy and turns goes into so many colours (if it turns on that is). Its either that or jumps all around the phone, quite literally it glitches out completely. Its like one of those virus cut scenes you see in movies, it goes different colours, glitches out, jumps around and completely misformats.
From the beginning i knew this was not a broken screen.
So far i have tried.
1. Factory reseting the phone. That gave me about 5 minutes of normal use until i locked the phone and it wouldnt unlock again.
2. Factrory reseting multiple times... again to no avail, it would work for short periods of time and glitch out again.
3. Reflashing stock Android 7 in Odin. - No avail.
4. Flashing Dr.Kretans Rom... worked for 1 day which made me so happy and think that the problem was solved but then the same problem persisted.
5. Installing Arters Kernel.. (arter97-kernel-n920cig-22.0) Nothing... literally did that today and still NOTHING
6. Re partitioning. Quickest process and no avail.
In more detail, if the phone does sucessfully boot, and bare in mind sometimes it takes more than 2 hours to get ANYTHING on the screen (including recovery which doesnt boot up either until the initial apperance of something on the screen)
I tried taking the phone to a phone shop before doing anything myself and since in England this phone was never released theyre refusing to touch it. I tried calling samsung and they dont want to do anything either cause its not a UK variant.
Could someone please tell me anything else i can try. I feel like im totally running out of options here.
My phone details are as follow
Galaxy Note 5
SM-920I Singapore Singtel Variant
Running on 6.01 (i downgraded from Kretan)
And the kernel is the one previously mentioned v.22.0
I would appreciate anyone's help or suggestions so much at this point. All these problems started since the 7.0 update a few weeks back :/
Oh its also running TWRP recovery (arter97-recovery-n920cig-22.0-twrp_3.0.2-0.tar)