Related
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium
Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!
I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?
I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.
Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.
He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O
@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves
Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!
Hi there, I hope you guys can help me out on this.
I just got my HOS a few days ago and it was all good.
Rooted it after 1 day, everything was fine.. at first.
Played a few games, installed themes and so on. After a few hours, my HOS began to vibrate out of nowhere and apps started here and there, menu opens on its own and all that stuff. It was out of control xD
I then saw that theres an update available. Flashed stock recovery and unrooted it. Afterwards, I installed 1.78. Still unrooted, downloading most of my Apps again, works flawless. Gaming(specially Temple Run xD) is smooth.
Yesterday, I decided to root it again. At first no problems at all.
Just now on the train, playing Temple Run again, my HOS started going crazy, vibrating all the time as if it is pressing buttons on its own and I see the phone doing all kinda stuff(opening new apps, browsing thru home screen etc xD).
Has anyone else expierenced something similar? I have no idea where its coming from and it really annoys the hell out of me.
Right now I'm on TrickDroid v3.1 (wiped system/data/dalvik/cache before flashing)
Kernel: 3.0.8-01136-g9d2ad32
Baseband: 0.16.31501S.17_2_10.23.31501S.10L
Build: 1.70.666.1 CL52668
That really is strange !!! Its as if root contains some sort of poltergeist
I would have imagined a factory reset would have cleared it up, But in your case it didnt....
Have you tried an alternative rooting method ?
Nope, I did not. Always used the All-In-One Toolkit, except for when I flashed Trickdroid, since it comes rooted.
Is it ok if I unroot the HOS with Rootkeeper(is this just temp. unroot?) and then root it again with Superboot?
Unbranded HOS bought in Germany, if that matters. Also, no other recovery works for me except Intermin, CWM just won't boot for me.
that is weird...
Unlocking the bootloader was successful right ?
I dont understand why your phone is rejecting software lol.. Oh and I didnt know root keeper can unroot ive never used it..
how i got root was by flashing paul obriens recovery and then the root package zip file.. I did this on day one and have never had any issues at all.. Ive tested every single ROM and every single recovery lol..
Make a nandroid in recovery and just test out different methods and try get this issue fixed. If you have any issues just restore the nandroid..
Check your phone for remote access apps, maybe you got hacked. Most of those require root to function. Also check your google account for which IPs logged in and check the password recovery options for weird emailadresses and phonenumbers...
Ars has a writeup on hardening your android device, not very technical but some good stuff there. http://arstechnica.com/security/201...-smartphone-against-stalkers-android-edition/
Forget whatever i wrote.
My HOS registers my thumb, even tho I'm not touching it at all. If I'm like 5mm away from the screen, it registers it as if I'd touched it. My gf also has a HOS and it acts only if I touch the screen.
I also noticed that the hotter my HOS gets, the distance increases at which it recognized my "touch".
The distant screen touch has happened on my uprooted tmo us HOS. I've also experienced some craziness out of the device. I've kept it stock, no unrooting/rooting going on.
I was thinking an exchange with HTC cause I also have excessive battery drain and wavy lines in the screen but now I also have an awesome cracked screen too :-\
Sent from my HTC VLE_U using XDA
i also dont need to touch my screen to select something
I just hover my finger over the app, real close to the screen and it selects it...
I guess we have special powers
i also dont need to touch my screen to select something
Click to expand...
Click to collapse
Same here.
lets keep this quiet, We dont want people to know we are superhuman...
I cant be arsed with the fan mail from the CIA,,, Nor do i have the time to fight crime and save the world....
Id rather just continue to flash a ROM.
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
What firmware are you running?
Is it the same firmware on both phones?
What is the launcher?
Have you tried a different modem?
Are you using a battery saver like juice defender?
Are you using an ad blocker?
Are you using a specific kernel? Oc? Uv?
Need for specific info
ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
You know, for the rather lengthy post, you really have not explained any detail about your issue.. You have a generic 'I have an issue, the Infuse sucks' post and its not going to help anyone resolve your issue. I find it EXTREMELY hard to believe that you have 2 infuses having the SAME EXACT ISSUE. Yes, there will be times when you get a defective phone or it isnt working up to your standards, but to have 2 defective phones with the same defect? You need to play the lottery. Also, i suggest you send the phones back. It sounds like youve already made your mind up and have pretty much bashed the samsung infuse in that entire post. The same samsung infuse that myself, and plenty of other people live with day to day and have absolutely 0 complaints.
I will give you $20.00 a piece for them!!!!
ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
Simple . Hack it and put cm7 on it if you really need speed. Maybe its your screen protecter. Wipe the screen off. Cm9 can be sluggish, for speed go to miui on gingerbread or cm7
Id be willing to buy one of the infuses
Trust me...sounds like you got two defective units...which like Scott, I find hard to believe...but hey its possible-idk when you got hem.but if it hasn't been a year then put them back to stock with gtgs unbrick and file a warranty claim with Samsung...the infuse is a great phone and I never had the problem you described...I do have a question though...did you get them both at the same time? Cause I don't see why you would get a second if your first was having problems
Anyways...if you wanna sell one hmu...I may buy one depending on the price and if I can get the money (I think I already may have one lined up for $170 just need to get the money)
Sent from my HTC PH39100 using xda app-developers app
Never really had any problems with samsungs beside the only issue I have ever had with ALL Samsung phones .. They have the worst RF signal/strength out of any company! I miss the days of my old Nokia RF ..
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Android Law #1: Costum ROMs are ALWAYS 10x better than stock.
Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium
Prometh1216 said:
Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Hehehe, what ROM u running?
Sent from my SAMSUNG-SGH-I997 using xda premium
qkster said:
What firmware are you running?
Click to expand...
Click to collapse
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
qkster said:
Is it the same firmware on both phones?
Click to expand...
Click to collapse
No
qkster said:
What is the launcher?
Click to expand...
Click to collapse
Both stock
qkster said:
Have you tried a different modem?
Click to expand...
Click to collapse
No, thought never occurred to me that I should look at this as a solution.
qkster said:
Are you using a battery saver like juice defender?
Click to expand...
Click to collapse
Neither.
qkster said:
Are you using an ad blocker?
Click to expand...
Click to collapse
Nope
qkster said:
Are you using a specific kernel? Oc? Uv?
Click to expand...
Click to collapse
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
qkster said:
Need for specific info
Click to expand...
Click to collapse
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).
are you completely wiping before every flash youve done? have you tried a complete wipe and start from fresh?
ssa2204 said:
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
No
Both stock
No, thought never occurred to me that I should look at this as a solution.
Neither.
Nope
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).
Click to expand...
Click to collapse
Task manager is NOT the best app to tell you what is running in the background.
Maps and other location apps may not be listed but will consume resourse that can be the cause of your lag.
The fact that stopping wallpaper or live wall paper off alleviate the condition may suggest that the phone is running at max capacity. Steps to reduce the load improves it. Live wp, facebook, maps, stock email and other device manager from stock att was one of the first @#$% I took out on any rom I run.
Having a large amount of apps installed can also cause this lag. The OS may only be able to handle so many.
Have a poor signal at the time of the call may also be an issue, especially if both of your phones have this issue occasionally but not consistently.
Lock screen can also be a factor. Some sleep setting may also cause the phone to wake up poorly. I get around this by turning off my lock screen. On the call settings, you can also change the answering options so that it will override others and make it easy to answer.
On any firmware - stock or modded, after you have the phone running for an extended period of time without a reboot, you may start to see some lags. This may be across all devices. You may need to reboot it occasionally or boot into recovery and wipe the cache.
These issues may or not go away once you have a device with more power or resources..ex: dual or quad core, 1gb or 2gb ram etc..my guess is when a device has more power, programmers will come up with more resourse intensive apps that may hinder the phone as well.
Lastly, pay attention to your battery meter. As the power dips below 30%, there are steps taken by the OS to conserve the battery. This may give you lags as well..possibly one of the reason why it seems random also.
If you wanted to test out the lag issue due to background apps, go to settings/account and sync. turn off background data. You will retain the (radio) phone and text but there will be no email/facebook, weather, widgets/market/amazon etc updates unless you manually update them. If this runs smoothly but lags when you turn it back on, you can start the process of narrowing down your culprit.
gl
Hey XDA Forums. So I am having a problem with my Galaxy S2 Skyrocket (i727). I will have it in my pocket, not using it, and when I take it out to try and use it, it will not wake up. I do not know if it is off or what, but I cannot turn it on without pulling out the battery and putting it back in. And it isn't dead, once it comes back on it will have anywhere from %20-100 of battery left. No where near being dead. This isn't just when it is off in my pocket tho, it happens some of the times when I try and restart it, but only sometimes. This was happening before I put a Rom on it but after I had Rooted it. I am running the Slim Bean Rom and I have made sure that it is completely updated and I have returned the device to factory state and reinstalled the Rom following the directions given with the same thing happening. Any help would be greatly appreciated!! Thanks!!
Random freezes and lockups have been an issue with jelly bean from the start. They are much more infrequent now, but they still occur. Be sure your minimum CPU speed is atleast 384. Many have found this to help quite a bit on cutting down on the lockups.
A battery pull shouldn't be necessary by the way. Simply hold the power button for 10 seconds and that should do the trick.
I have only had freezes when rebooting way back in July when I flashed my first ROM Sky ICS. It happened constantly after the initial flash though while yours seems random. I was told to backup the rom, wipe and immediately restore it. Worked like a charm. Can't hurt to try it.
Edit: It could also be a stuck power button. Check the stickies and you should find info on correcting it.
-------------------------------------------------
Sent from my Skyrocket i727 running Slim Bean
-----------Nexus 7 running AOKP M1-----------
http://forum.xda-developers.com/showthread.php?p=31606955
Sent from my SGH-I727 using Tapatalk 2
can u clarify, when you are on stock rom does it do it, or only on custom rom, on stock rom its more important if its doing it as it could be some hardware issue, if its a custom rom, read the devs thread for possible fixes or try another rom
Moved to Q&A
tjc1029 said:
Hey XDA Forums. So I am having a problem with my Galaxy S2 Skyrocket (i727). I will have it in my pocket, not using it, and when I take it out to try and use it, it will not wake up. I do not know if it is off or what, but I cannot turn it on without pulling out the battery and putting it back in. And it isn't dead, once it comes back on it will have anywhere from %20-100 of battery left. No where near being dead. This isn't just when it is off in my pocket tho, it happens some of the times when I try and restart it, but only sometimes. This was happening before I put a Rom on it but after I had Rooted it. I am running the Slim Bean Rom and I have made sure that it is completely updated and I have returned the device to factory state and reinstalled the Rom following the directions given with the same thing happening. Any help would be greatly appreciated!! Thanks!!
Click to expand...
Click to collapse
I had this same issue with my Skyrocket. Granted mine was just rooted and on stock rom. But it still did it, random reboots usually during a call. I got tired of it happening so I contacted AT&T international support (that part was by accidentaly dialing the wrong number), and then a few days later I had a brand new Galaxy S III. Now granted in my case it was that I was on the 3'rd Skyrocket and was not about to go through all that again.
So, I don't know what happened. I didn't touch a thing on this phone, haven't changed any settings or installed any apps for weeks. However, just now, my phone has decided to start acting up in a bad way.
I'm on Paranoid Android 2.52, and I have been for many months now, with no stability issues of any kind. However, without any warning or cause on my part, something got reset. The first thing I noticed was that all of my settings reset to the default Android settings. I had to go through and change all my settings back to how I want them. Then I discovered that there's nothing I can do to get my lockscreen to work again. I have it enabled, I've tried every variation of lockscreen on this ROM, with delay, without delay, but the lockscreen just won't show.
Then I noticed that my notification bar won't display any notifications. It'll show the time, battery, Wi-Fi and other small logos. But the alarm, timer, text, e-mail, etc. notifications will not show on the bar at all. My phone will vibrate when receiving and e-mail or text, but no notification will appear.
Then I noticed that in SMS Popup, which I use, I can't un-hide the message on the popup. I have the privacy set such that I have to tap the little eye logo to display the message. But now that logo no longer responds. It will change color on press, but will not un-hide the message. All I can do is close the popup with the message unseen.
Then I noticed that my home button doesn't work. Either short- or long-press. Short-press should take me to my home screen, long-press should take me to recent apps. It does neither. My phone will vibrate when I touch the home button, but it does nothing. I've checked my settings, and they are as they should be. The button just won't do anything.
I'm sure there's many, many more issues I'm yet to discover. What on Earth happened to my phone and how do I fix this?
Sent from my SGH-I997 using xda app-developers app
I've tried rebooting, turning it off, pulling the battery for a few minutes. Had no effect. And I have no idea what else to do.
Sent from my SGH-I997 using xda app-developers app
Titanium just reported to me that my phone's ID somehow changed. This indicates a factory reset, but I certainly didn't do that.
dstarr3 said:
I've tried rebooting, turning it off, pulling the battery for a few minutes. Had no effect. And I have no idea what else to do.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
When all else fails I personally start completely over using this thread http://forum.xda-developers.com/showthread.php?t=1524081 ,boot into completely stock GB go through setup,reboot into stock GB,then reboot into download mode, flash Zen's A16 kerrnel with recovery,reboot,then follow directions for installing whatever ROM you desire.My two personal favorites(YMMV)are 2.3.6 GB deodexed,zip-aligned,debloated and BeanStalk
elbscorp said:
When all else fails I personally start completely over using this thread http://forum.xda-developers.com/showthread.php?t=1524081 ,boot into completely stock GB go through setup,reboot into stock GB,then reboot into download mode, flash Zen's A16 kerrnel with recovery,reboot,then follow directions for installing whatever ROM you desire.My two personal favorites(YMMV)are 2.3.6 GB deodexed,zip-aligned,debloated and BeanStalk
Click to expand...
Click to collapse
Yeah, I ultimately decided that the only thing I could do is just go back to stock and work my way up to BeanStalk. I enjoyed PA for a while, but all the BeanStalk discussion piqued my interest.
Anyway, I just wish I knew what happened to cause my phone to spontaneously fail so completely. It's seriously of a case of it working before I put it in my pocket, and it being completely ruined when it came out.
dstarr3 said:
Yeah, I ultimately decided that the only thing I could do is just go back to stock and work my way up to BeanStalk. I enjoyed PA for a while, but all the BeanStalk discussion piqued my interest.
Anyway, I just wish I knew what happened to cause my phone to spontaneously fail so completely. It's seriously of a case of it working before I put it in my pocket, and it being completely ruined when it came out.
Click to expand...
Click to collapse
If you go back stock and run it for a day or two should let you know if it is a hardware issue.
elbscorp said:
If you go back stock and run it for a day or two should let you know if it is a hardware issue.
Click to expand...
Click to collapse
Yeah. As soon as I went back to stock, everything was immediately back to normal. But, my past three phones have all lasted anywhere between 21-24 months without any problem, and then suddenly falling apart like the Blues Brothers car and becoming completely unusable overnight, just in time for me to upgrade to new phone with a discount. And, since my contract is up in a couple months, I wouldn't be shocked if my phone's about to have its end-of-term breakdown.
I'd really like to avoid the introductory prices on the S4, though... If I could keep this phone going until about June, I'd love that.
dstarr3 said:
Yeah. As soon as I went back to stock, everything was immediately back to normal. But, my past three phones have all lasted anywhere between 21-24 months without any problem, and then suddenly falling apart like the Blues Brothers car and becoming completely unusable overnight, just in time for me to upgrade to new phone with a discount. And, since my contract is up in a couple months, I wouldn't be shocked if my phone's about to have its end-of-term breakdown.
I'd really like to avoid the introductory prices on the S4, though... If I could keep this phone going until about June, I'd love that.
Click to expand...
Click to collapse
I don't have contracts and I've had phones with faster,newer,better hardware and I come back to and enjoy my Infuse more. As long as there is this kind of active development for it I will keep picking up cheap Infuse.
elbscorp said:
I don't have contracts and I've had phones with faster,newer,better hardware and I come back to and enjoy my Infuse more. As long as there is this kind of active development for it I will keep picking up cheap Infuse.
Click to expand...
Click to collapse
Yeah, I'll admit Scott's solely responsible for keeping my interest in this phone. A year ago, I was still on Froyo and I was getting bored with it and wanting a new phone, but I stumbled across PA somehow and thought I'd give it a shot. Three PA roms and Bean Stalk later, I'm still loving my Infuse.
The problem is that the hardware's just not holding up anymore. I'm having the famous power button issue. I'm going to try to gut my phone and clean the button myself, but beyond that, there's not a lot that can be done about it. I'd really love to dedicate the Infuse to an alarm clock/media player when I get my new phone, so I can still have something to mod. But I just don't know how I'm going to adjust to the sudden lack of customizability when I get the S4 with a stock release of Android.