I've noticed with the new update that there is a haptic pulse after the phone finally shuts down. I have gotten in the habit of ripping out the battery to exchange it for a fully charged one before the phone does the final power down feedback.
So I guess my question is, what is happening from the point where the screen turns off until it actually powers down fully? Are there any negative consequences for pulling the battery prior to the phone fully shutting down?
If you shut down in the dark you will see that the screen is not actually off. In fact if you touch the screen before the vibration, the capacitive buttons will light up again. I would wait for the vibration before taking out the battery, but some people do a battery pull just to pre-odin shutdown... for what its worth.
Sent from my SPH-D700 using XDA App
I've noticed the haptic feedback at the end of shutdown.
I mean I would personally wait. Don't think it has ever been good to yank a battery on any device while it's shutting down.
Its been like that since dk28...I think its a froyo thing...
I've never pulled the battery while it was shutting down...that's like unplugging your computer while its shutting down..
Sent from my SPH-D700 using XDA App
uh oh. i have never shut down prior to removing the battery. when my batt gets low, i just flip it over and yank the battery while its still on. i would never do that to my computers, but i never gave it a second thought until i read the analogy above. crap.....
If you set your keyboard timeout to same as screen timeout then the capacative lights will stay on till it vibrates.
FROZEN EPIC
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pulling the battery during shutdown shouldn't effect anything major as long as you still have journaling enabled. Those running ext4 with the no-journal mod are the only ones that really have to worry about problems occuring because of pulling the battery.
DiGi760 said:
Pulling the battery during shutdown shouldn't effect anything major as long as you still have journaling enabled. Those running ext4 with the no-journal mod are the only ones that really have to worry about problems occuring because of pulling the battery.
Click to expand...
Click to collapse
I'm no developer/hacker, but I'm pretty sure DiGi is on the right track here. The only reason to worry about pulling the battery rather than "properly" shutting down would be if you have apps/utilities/settings that aren't saved yet. If you always ensure that your apps, games, etc. have saved anything "important"--or simply closed--then you shouldn't have to worry.
Conversely, if you pull the battery in the middle of an epic Angry Birds session, you'll probably lose that progress!
Comparing our smartphones--and most solid-state devices--to a computer is somewhat misleading anyway, because PCs often have data stored in caches on magnetic HDs that require some time to write the cached info to disk because of the moving parts (platters and read/write heads). Our Epics and the vast majority of handheld devices use only solid-state (i.e., no moving parts) electronics.
As for RFS versus EXT4, that's over my head. Thanks for the input, DiGi.
If anyone else can correct me or explain anything better or in more detail, please throw down! I'm all ears when it comes to geek knowledge...
DO NOT PULL THE BATTERY DURING SHUTDOWN AND BEFORE THE VIBRATION. Learned this the hard way as on three occasions I had to restore because of FC's of all of my apps. After finally retracing my steps, I realized that I was pulling the battery before the final vibration in the shutdown process. Haven't had the problem since I put two and two together.
Agreed, I've had significant data corruption (apps force closing, files that won't open) after accidental battery pulls on the dk28 roms w/ the no-journaling mod. It makes me wonder if the no-journaling mod is worth the slight increase in performance/less write usage. Speaking of which, does anybody know if cwm3 automatically removes journalling, o just specific roms?
Sent from my SPH-D700 using XDA App
Related
a lot of people are reporting this problem when the phone is off
http://androidforums.com/htc-evo-4g/106893-i-just-notied-my-evo-glows-dark.html
JoshHuman said:
Here is the problem on a 002 15 second exposure in complete darkness.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
The way I see ut is that the button panel has its own backlight and is meant to turn on in complete darkness, but some evo's do it when the phone is off given enough power since the panel's software run a separate lower powered chip, but I'm no engineer. It can be fixed with a firmware update, probably.
Mine did this once. I turned it back on and killed a bunch of apps with advanced task killer, and then it quit. Think it was just a fluke because it hasn't happened since.. and that was about a week ago. If it's happening constantly even after reboots, I'd assume you have installed something that is acting retarded in the background.
actually it's not a software problem... I hard reseted and kepted the phone clean and checked at night. still LED problem being lit. I took it to a store and they are willing to replace the phone
Yes this happens to me alot and i have to remove the battery and put it back in i left the phone like that for 10 minutes and i click every button but does not come back on so have to remove the battery
My wife's has been doing that and it will not stop. Ive rebooted cleaned all apps and nothing. I'm trying to return it but am waiting for bestbuy to call me when they get more phones. Any one have a solution?
Sent from my PC36100 using XDA App
I have the opposite problem. Mine never seem to turn on in complete darkness. >_<
I just noticed this for the first time last night. Haven't seen it before or since.
Sent from my PC36100 using XDA App
TheBiles said:
I have the opposite problem. Mine never seem to turn on in complete darkness. >_<
Click to expand...
Click to collapse
wish i had that problem. i really have no need for back lights on the menu. the bleed they cause is terrible when looking at dark movies.
on the droid, in froyo at least, the menu buttons dim when watching a movie or you can use LEDsHack to turn off the lights.
I posted this issue a couple days ago and got no replies. I have noticed this issue on my phone. Sometimes pressing volume up/down will cause the lights to come on too.
I wonder if this is the cause of poor battery life. It's almost as if the light sensor is still functioning when the phone is supposed to be sleeping.
I noticed this also on both mine and my girls 0002 models... You can see it during the day too if you cup your hands around the bottom of the screen just over the buttons and look under. Wasn't sure what that was all about. Looks like just another glitch to me.
Is this good enough reason to request exchange? Does this drain battery faster in any way?
apexi350z said:
Is this good enough reason to request exchange? Does this drain battery faster in any way?
Click to expand...
Click to collapse
yes it is a good reason. kills battery
delete please.. double post
I thought the whole time that the "glow in the dark" was a feature. Its something I certainly don't mind, as I have found it rather useful.
But since its not a feature... then... defect? Haha. Well, this EVO is going back to the store anyway.
I figured I'd make a thread about some of the weirdest stuff you've had happen to your SGS. Only a few minutes ago I had a little incident which made me wonder, what kind of weird stuff do other people deal with?
I'll start.
A few seconds ago I tried playing Angry Birds. After it loaded I clicked play and the screen didn't change. Instead random dark lines started to appear horizontally across the screen. At first there was one and then slowly many, many more started to appear. None of the capacitive buttons worked, nor did the home button. Eventually it got really bad and I lost all hope so I held the power button and it reset. All seems fine now.
The time before that I was flipping through some menus fast and I started getting mass FC's. I decided to restart the phone. Upon booting up ALL info that I downloaded or came from Bell was gone. The Remote PVR app and everything, was gone. The factory reset button in the settings menu didn't even work. After doing a reset via the 3BC everything worked again.
Now, what kind of crap have you had to deal with?
hmm... how about a double weird even of the same magnitude?
So, here i was doing stuff happily with the SGS on me, suddenly i hear the phone have restarted on its own i was like OMG!!!!! WTF!!!!
it was just once, and i was doing stuff, so i disregarded it and continued with my life.
then shortly after (30min ~ hour) the same thing happened so i was left pondering and started to investigate, only to find out that the belt letter case that i use have an exact opening to activate the buttons (never paid attention to it before) and when i sit down the rugged parts of the Jeans will press exactly right into the spot where the On/Off button is located mystery solved
solution move the belt case a little bit more to the front to avoid the hard edge of the jeans plies
But!!!.... that's not over... the SAGA continues!!!....
not long after at around the same time (a day or 2 later) the phone did it again, it rebooted on its own IN FRONT OF MY EYES (i was texting in the toilet), so i said it aloud WTF!!! this definitely was not a Jeans/Belt combo issue, it was not the SMS / XDA App program causing it.
so i started to investigate, i installed a new app recently that i was testing (superpower), it worked really good for the first roughly 12~24 hrs i was using, made some options changes
then it worked even better, however the reboot was caused by the app that i installed it.
removed the app and now the phone is back to normal ever since.
How's that for excitement?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Every now and then, when using it to play music in the car, it will turn itself off. Not a graceful shutdown though. It will be playing one minute, then BAM, it's turned off.
Holding down the power button for 5 seconds won't turn it back on. Even multiple tries.
But holding the power button down for a solid 10-12 seconds will turn it back on. Then after it boots up, everything seems normal again....
well, I was showing the phone to a friend, he has an iPhone 4, he saw the Angry Bird icon, he said, ok let's compare the game between ur SGS and my iPhone4
I won the battle, size of screen depth of colors were my weapons but
when I pressed the home key it went back to home, then suddenly screen started getting brighter, more and more, I wasn't able to see anything after few seconds, and I was so shocked casue I read some topics about Super Amoled going brighter and then dying for ever I immediately restarted it using the power key, and never played angrey birds again this was before a month, my screen is still fine
This started yesterday out of the blue.
When i press the power button to wake up the phone, It wakes to a black screen. The Home,back, menu and search icon light up. I can even slide to unlock. It all works but the screen remands black. Now if i press the power button on/off a few times everything works and the screen will awake.
Once the screen is woke everything runs fines. The only other problem i ever had was the launcher force closing.
Running "Vision_Gingerbread_S_TMOUS_2.13.531.8"
I reflash the rom when this problem first started. I really need to fix this. IDK if it is software or hardware. Has anyone had this problem before? I wasnt planing on buying another phone till income tax time which is about 7-8months from now.
also tried adjusting the brightness, and disabling the animations.
I had the same problem on Vision roms. Now I'm on CM stable, and get it once in a blue moon.
Yea i flashed that rom along with some others. I am thinking its hardware problem.
I took the phone apart and the ribbon cable that runs from the phone to the screen casing has a little dot on it( a rip in the insulation). Im guessing something in my pocketed one day kinda cut into it or just wear and tear.
Im going to try to find that cable and replace it and see if it fixes my problem.
For now i just put a little tape on it to stop the hole from getting bigger. and shorting out with the metal casing.
Anyone know where to start looking for this cable
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found screens and keyboard stuff but havent found this cable yet
your black screen problem is a known issue for your phonehaving trouble catching up (speed wise) and it does that until you turn the screen on and off again. I suggest upping your minimum clock speed to something like 475mhz. apart from that if you're using something like Virtuous 2.0, then the OC daemon will eliminate that issue. I haven't seen the issue on my phone for the past few months after i switched to using the OC daemon provided by rmk and the virtuous team.
mputtr said:
your black screen problem is a known issue for your phonehaving trouble catching up (speed wise) and it does that until you turn the screen on and off again. I suggest upping your minimum clock speed to something like 475mhz. apart from that if you're using something like Virtuous 2.0, then the OC daemon will eliminate that issue. I haven't seen the issue on my phone for the past few months after i switched to using the OC daemon provided by rmk and the virtuous team.
Click to expand...
Click to collapse
That doesnt explaine y it just started doimg this tho. I unhooked the ribbon and plugwd it back. Also havnet openwd the the phone since and all has been good. So I bwlieve its just hardware. Maybe the cable came lose.
unless you screwed something up hardware wise, it is the minimum speed trying to catch up with the turn on and failing.
I had this problem before and switching to the OC daemon solved it. It's a known fact.
those ribbons usually come with the screen, so search ebay for the screen component, you'll have better luck there.
mputtr said:
unless you screwed something up hardware wise, it is the minimum speed trying to catch up with the turn on and failing.
I had this problem before and switching to the OC daemon solved it. It's a known fact.
those ribbons usually come with the screen, so search ebay for the screen component, you'll have better luck there.
Click to expand...
Click to collapse
Son and wife have knocked it off the desk I put it. Fallen about 2ft onto the carpet. So im welling to bet the cable was just lose. Will give it a week and ser if the problem comes back. Thanx for the help.
It also did the blank screen doing boot up and recovery which has to be hardware since the os hasnt booted yet.
sure. good luck with it then.
I think the minimum clock speed is a good theory. I have mine on 245MHz, will make it higher and see if it helps. Now that I think about it I started having the problem since rooting and playing with SetCPU.
Yep, having it higher there is an increase in how long it takes for the screen to turn on after pressing the button (Yes, I do see in milliseconds ) Now i'm on 768 min and 1516 max.
I had a trackpad wake to black screen on CM 7.1RC1. Upgraded to the latest nightly and it's fine
Well so far problem seems to be gone since I took the phone apart. I didnt change any settimgs or anything.
I have a weird problem with my Wildfire's screen after I did an OTA upgrade to Froyo.
First, the top of the screen stopped working. The taskbar wouldn't work and I the top wasn't responding. All of a sudden, after approximately a month or so, it started working again.
It worked fine for a few weeks and then the right side of the screen has a problem. All of a sudden it started automatically hitting the spot on the screen where the letter "P" would appear on the keyboard. When I was trying to type out a message, the letter "P" would get hit on its own over and over again. When the keyboard was not open, it would still happen.
I felt it might be a virus, so I did a hard reset. This still didn't stop. So I switched off my phone and kept it in a desk for 48 hours. When I switched it on again, this problem stopped, but the right side of my phone was not responsive (approximately 4 milimeters of it).
I can see that this is clearly not a hardware problem and has something to do with the firmware/OS. I'm not too sure what to do. I've tried flashing new ROMs on to my phone, but it remains the same way.
Incidently, when I tried flashing "TheNextSense" ROM on to my phone, the phone started hitting the portion of the screen where the "P" key would appear. When I switched back to CM7, it stopped, but the right side was unresponsive.
Is this something to do with the memory? Or is this a known issue with upgrades/certain ROMs?
Any help will be appreciated. This is driving me crazy
why do you think its not a harware problem ?
for me it sounds like it is one. (temperature or short circuit problem)
IANAHRM (I Am Not An HTC Repair Man) but I think the touch screen connector has just slightly worn loose, perhaps due to temperatures. It sits on the right side of the main board (left side of the phone itself). I know the Wildfire can survive quite a motion shock so that shouldn't be it (I hope).
Nandroid backup and restore jobs heat up my phone quite a bit, did this occur on your device as well while you were installing roms? That might explain the change in behaviour.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
henkdv said:
IANAHRM (I Am Not An HTC Repair Man) but I think the touch screen connector has just slightly worn loose, perhaps due to temperatures. It sits on the right side of the main board (left side of the phone itself). I know the Wildfire can survive quite a motion shock so that shouldn't be it (I hope).
Nandroid backup and restore jobs heat up my phone quite a bit, did this occur on your device as well while you were installing roms? That might explain the change in behaviour.
Click to expand...
Click to collapse
Nope. It's never heated up till now. This happened all of a sudden, and it gets worse with upgrades. It's like, for some reason, the phone isn't able to function properly with any ROM other than the stock ROM. I'm going to try to put back eclair on it today and see whether it works. Will keep you posted.
stavro said:
why do you think its not a harware problem ?
for me it sounds like it is one. (temperature or short circuit problem)
Click to expand...
Click to collapse
Because it doesn't always occur. It kind of gets fixed on its own after a few days. It's like my phone has a ghost in it
I put back the stock Froyo ROM and now the problem is 50% better - much of the portion of the screen that was dead earlier is now responding. But the rest still isn't. Any ideas? :-(
Hello guys , i would like to know whether anyone else has experienced any type of graphical glitches on their 6p.
the thing is , i had a Nexust 6 (Moto) last year, and during cold temperature it would get a split screen bug few times every few hours and it was very annoying.
the only fix for it was to use a custom kernel with 'interactive' governors.
the kernel that worked best for me to get rid of that graphical glitch was Lean Kernel.
but my 6p thankfully is not getting the splitting screen graphical glitch, but instead it just looks like the picture of whatever app i am in just gets smashed into each other (sorry i dont know how to explain!).
it basically glitches for a second and is back to normal , and it happens like a couple of times per day, happened only recently after the weather here got cold.
is this a common thing with the 6p? i am now wondering whether i should try lean kernel with it ,as i am currently using flash kernel.
hm, at first i thought it was because of a profile i used on my 6p so i disabled profiles, then i thought it could be caused by the theme (cm13) so i reverted theme to stock.
but the random occasional graphic glitch was still there.
hope someone can shed some light on this for me.
Only if you could explain it a lil more maybe a screenshot or something
What kind of temperatures?
Phones usually last fine till about -15 celsius, beyond that intense screen ghostings (maybe this is what you meant?) start appearing, phone turns slow in general and battery dies very fast also causing permanent damage to the battery.
If it is the screen ghosting then that is perfectly normal and usually dissapears when it gets warm again, but I can not confirm as I have no 6P nor have had any amoled phones.
Does the glitch show up on screenshots? Or is it only visible physically?
tauio111 said:
What kind of temperatures?
Phones usually last fine till about -15 celsius, beyond that intense screen ghostings (maybe this is what you meant?) start appearing, phone turns slow in general and battery dies very fast also causing permanent damage to the battery.
If it is the screen ghosting then that is perfectly normal and usually dissapears when it gets warm again, but I can not confirm as I have no 6P nor have had any amoled phones.
Does the glitch show up on screenshots? Or is it only visible physically?
Click to expand...
Click to collapse
its only physically visible, i think it is because of the app Twitter..
when i open it up ,that graphical glitch appears for a split second, it looks like the app itself makes the screen shimmery? i dont know how to explain it, but yes i think it was twitter.
but then again, i think it is what you stated, screen ghosting.
and that stuff is normal ? if so then all is good, thanks!
@Prattham and @tauio111 sorry guys ,pretty late on providing screenshot.
i happen to have one where it took place, the graphic glitch.
it ocassionaly still does happen..
turned out it is not at all because of cold temp.
it is stupidly hot right now, haha.
and btw. it also happens more often when i go switching too fast between apps with the recents button.
and also at times when i scroll.(with scrolling happens way more rarely though).
here is the picture , look at how the picture in the youtube app (official one) mashes into each other.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}