Hi,
First post, feels like I'm a little late to the party. I have a gio which initially had gingerbread 2.3.3. The phone is unlocked, and rooted, and has the clock work mod recovery patch on it. I have tried a couple of different versions of gingerbread, and am now running ice cream sandwich: kernel 2.6.35-7-galaxyics, CyanogenMod version build 9-20120610-UNOFFICIAL-gio, build number IMM76L.
Firmware-wise, it's mostly good, but I'm having a couple of weird issues:
1. The screen goes black on me periodically, and won't come back without pushing the on/off button. This is happening every 30 to 60 seconds of use.
2. The wifi crashes, a lot. With the older gingerbread I would get the word "error" under wifi in settings, and couldn't turn it back on. I would enter *#*#526#*#* to bring it back, but every 5 minutes seems a little excessive.
With the newer ICS, I've noticed I can play on a wifi link all day long without issue, but as soon as I set the phone down for a couple of minutes, wifi stops working. If I go into settings, wifi is on, but there's no connection. If I turn wifi off and back on, it comes back to life.
I guess, I'm wondering if these indicate more of a hardware issue than a software issue. It's hard to ask for support from my carrier, given I'm using an unlocked phone bought from a 3rd party, and have no contract.
zapstrap said:
With the newer ICS, I've noticed I can play on a wifi link all day long without issue, but as soon as I set the phone down for a couple of minutes, wifi stops working. If I go into settings, wifi is on, but there's no connection. If I turn wifi off and back on, it's comes back to life
Click to expand...
Click to collapse
I got that problem to sometime ,
And welcome !
send from my galaxy gio with paranoidAndroid Rom
Errors that you describe has a lot of people
The team is now working on ICS AOSP so be patient wait a little meringue as soon
And yet you propose to install something else that any CM
In total there is this quite a bit
update
A couple of things I've noticed:
1. The resetting wifi problem does not happen when the phone is plugged into USB.
2. The screen turning off happens frequently, but about 1/2 of the time, the screen will turn off for 1-2 seconds, then come back on at full brightness; the rest of the time, it will not come back on at all, but still responds to being tapped. The only way to get it back is to push the on/off button on the side twice, but then the screen is locked, and has to be swiped to unlock.
I have picked up a second phone, a 5660M running stock gingerbread 2.3.4, unlocked and rooted; not experiencing either of the two above issues (and the camera preview works). If I could take the 5660 back to stock at this point, I would prefer that, as the phone is not usable with these problems. Is there a stock rom available for this phone somewhere?
update part II
Hmm, after the phone showed up with 2.3.3 claiming to be a gt-s5660, and was sold as such, I finally put 1 & 1 together. I checked under the battery, it's a gt-s5660m. That explains probably all of the problems I've been having. Pity there's no ICS build for the M version of the phone.
You can use cm9 ics on your M model, it only changes your device id to gt-s5660, just dont flash roms with ODIN except roms for the M model.
Flashing from recovery wont install a baseband, with ODIN it mostly does, so the only roms you cant flash are old roms that still need odin like gioprio.
Flashable .zips are fine, all of them
Sent from my GT-S5660 using xda premium
The wifi problem might be hardware, m8
I don't know, as my gio has some strange problems as well and I've had ICS, Adrenaline ROMs, everything, and the problems still persist. At least they're not really bad to handle in everyday use but still, they're annoying.
Go to wifi settings - advanced - sleep policy- never
Sent from my GT-S5660 using xda premium
update part III
Since going back to GINGERBREAD.MUGKG3 / 2.3.4 for the GT-S5660M, the wifi crashing and screen blanking behaviours have completely stopped. After two days of running, wifi has not shut-off unexpectedly even once, and the screen does not blank any more at all.
The gps works now; it was not before. It used to sit for up to an hour under a clear open sky, day or night, and never acquire a single satellite. Now it picks them up within 30-60 seconds, though a full lock does take a couple of minutes.
The phone previously always indicated it was roaming, and would frequently refuse to send texts or make calls. I would get full bars for signal strength, but no connectivity.
I even got hold of the fm radio app, which was not included with the M version of the 5660, and manually installed it (phone must be rooted, and file system must be mounted read/write). It works too; a nice bonus.
The camera works, but is a bit flaky, requiring an occasional restart to get it going.
Probably the biggest headache, after flashing back to the 5660M version, was that the phone locked itself again, and wouldn't work on my network. I dumped bml5 page and searched out the unlock code. I had some trouble with this. The search string to get close to the code is supposed to be a sequence of twenty 0x00 bytes, one 0x05 byte, and fourteen 0xff bytes. The 0xff bytes weren't there, and it took a while for me to clue in that if I searched on the twenty 0x00, and single 0x05 byte sequence, I could still pull it out. I got it, and wrote it down in case this happens again.
sms issue
Still ticking along with the GT-S5660M; mostly it's all working nicely. I have one question though: I recently ran out of memory for storing SMS messages. It looks like the texting app in the phone wants to put everything on the SIM card rather than on the SD card, but there's no option for moving the default storage location for messages. Is there a simple way to do this? The phone is unlocked & rooted, but does not have the ext2 file system on it.
What's the IC? I checked under the battery to confirm mine is a Canada model, and it is.
But my IC is GT-S5660L
Model: GT-S5660M
IC: GT-S5660L
buremily You
Peteragent5 said:
What's the IC? I checked under the battery to confirm mine is a Canada model, and it is.
But my IC is GT-S5660L
Model: GT-S5660M
IC: GT-S5660L
Click to expand...
Click to collapse
Same, GTS5660L ... why do you ask?
Related
HI all, I am new to android
Followed the excellent tutorials in this forum and upgraded to 2.2 using a file downloaded directly from a HTC link (sorry cant find right now)
Everything is superb but the gps cant get a fix. It has been a few days and I tried various things like restarts, remove battery, clear sky, leave google maps running for long, checked it is enabled in settings etc.
What to do?
What should be the correct version information after the 2.2 update? (in case i installed a beta/incomplete version)
Please help this new droid get back on its feet
I am sorry I have no solution, but I have the same issue. This has nothing to do with 2.2 I think, because it happened all of a sudden. At least it felt like it happened jus like that. I have been using 2.2 for a long time and used GPS. Only recently I noticed the issue.
from my post here http://forum.xda-developers.com/showpost.php?p=7773080&postcount=9
It worked for me! I went to the roof as today is a bright day and used Tricorder app's Geo tab. Touched on it to show satellite.
It kept trying to connect to satellite. The tricorder app shows some satellites as green. Presumably as they are chosen to calculate location. It didn't finally lock-on till it was showing 12 satellites and 4 of them were green. I noticed that I had to remove the jelly cover and :
1. Stand still, she how many satellites it shows signals. In a few seconds it will stop detecting new ones.
2. It it hasn't locked on then move around a bit and change some orientation then step 2 again
3. Repeat above till it latches to atleast 4 green or 12 total signals (dont know which one works the 12 signals or 4 green)
and after that it easily updates even indoors for me.
I usually get a fix in the first minute, usually under 30 seconds. But this time no satellites were showing, not even after 15 minutes. I switched roms and it's working fine again.
I think I must have messed up something by reflashing multiple times. (I was trying to get the bios boot image to work, but sadly no avail )
I've just updated to voda standard 2.2 rom OTA this morning
1st thing I've noticed is the gps is a no go, no sats in view at all.
(using gps test the 'on button' only stays yellow too)
I've not 'messed' with my phone at all other than the standard updates
I must admit I've not tried a hard reset yet but I think that's going to be the last hopeful resort otherwise it's going back for a replacement
Hi,
I just got a new HTC Desire Z Bell Branded (A7275) for my AT&T service. I "debrand" it using the debrand guide. I just noticed twice yesterday that when I put it in standby mode, I try to press the power button to turn off standby mode so I can get the screen to slide down to unlock the screen for usage. Well, it did not....no matter what I do...I cannot get the screen to get unlock. The screen is black as if it isn't on. I hold the power button, still nothing. Only way is for me to pull the battery out, put it back in and power it up. Is this common? What is the problem that causes this? Any help would be nice. Thank you in advance.
have you oc your phone at all? have you flashed a kernel? custom rom? and what guide did you use?
I used this guide to debrand my phone.
have you oc your phone at all?
Not a single bit, everything is bone stock regarding CPU.
have you flashed a kernel? custom rom?
I only flashed the one from the guide.
[ROM] RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M
what guide did you use?
http://forum.xda-developers.com/showthread.php?t=835777
Thanks for the fast reply and help, bahmanxda.
Tbh I am not sure what is the problem I got nothing ,the only thing that I can think of is if you are already rooted and s/off do a full wipe and flash the Rom again or try different roms if u like sense try virtuous 9.0 its really good.
Sent from my HTC Vision using XDA App
There are some others with this issue. Unfortunately, the cause has not been found, or whether it is hardware or software related:
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
I've had this crop up myself a few times. I can say this:
Several times my Desire Z has powered off and could only be powered on after pulling the battery and re-installing. It did this twice within the first few days I owned it. Then it didn't happen anymore.
Maybe a week later I tried the Godspeed kernal (1 GHz) and SetCPU. No issues for about 2 weeks.
Then I tried CPU Tuner based on claims made by some users here that it is easier on battery life. Used a screen-off profile to underclock. The phone had the power off problem, 3 times in 2 days. Every time when the screen was off. But the random poweroffs did not start immediately after installing CPU Tuner, maybe 2 days later.
I uninstalled CPU Tuner to see if it would help (and it didn't seem to be improving battery life). Went back to Set CPU (have messed around with and without screen-off profiles). Its been more than 2 weeks, and no random power-offs.
None of this is conclusive, of course. Maybe the problem in my case was CPU Tuner, or a combination of the kernal and CPU Tuner. Maybe the things I've described are complete coincidence, and its some other factor altogether. But just thought I'd throw my experiences out there. Some claim Google Maps is the problem, but I have not found this to be the case. Or possibly some issue with the battery contacts, or the battery itself. Who knows?
Same thing happens to my Bell Desire Z. Every now and then it just decides to freeze and Only solution seems to be to take out the battery and then put it back.
Very frustrating.
Thanks for the reply, everyone. Strange it has not happen for the past 2 days now. I've read the other thread and still no exact detail on the cause of this. This is not good...especially it is my first Android phone and first HTC (bought it due to their reputation of quality made phones).
It happened twice within the first week of using the phone. Decided NOT to return the phone to observe it for a full month. During that month it happened every 3-4 days, always happens when the phone is not charging, and at the hour mark. Decided enough is enough and returned for a warranty claim 2 days ago.
During the one month, I rooted the phone after 2 weeks and flashed a custom ROM, but the problem did not go away.
There're people who aren't affected by this problem though.
I've the exact same problem here. CM 6.1.1 will just randomly black screen on standby. No response to charge when plugged in. The only way to reset is to pull the battery.
I don't think it happened on stock firmware. I'm now highly debating switching ROMs. It's getting annoying to remove the back cover every time I need to do a hard reset.
I think there is a thread in regards to CM and overclocking causing a screen on issue. But I think in those cases, the phone has power (LED and front buttons light up), just the screen can't power on. But adjusting any overclocking/underclocking profiles is worth a try.
Do you have SetCPU or CPU Tuner setup, and any profiles under those, such as underclock when the screen is off? I tried CPU Tuner for a few days, due to claims by XDA users of better battery life than SetCPU. I got 3 instances in 3 days of the phone not being able to power on (had to pull battery). I un-installed CPU Tuner, switched back to SetCPU, and haven't had the power on issue crop back up for almost a month now.
Given, I had the power on issue 2 times before using CPU Tuner, so it can't be the sole culprit. My only theory is that some combination of switching the kernel and SetCPU has solved the issue. Or it has nothing to do with those at all, just a coincidence, and is something else completely. Who knows.
It happened to me many time already. I still use stock htc desire rom and never rooted..
I've had it happen about 6 times, always requiring a battery pull. Totally stock other than being unlocked, not-rooted. But it hasn't happened for the last 3 weeks or ever since I stopped using juicedefender. Coincidence?
Desire Z freezes
Hi,
I also have some random freezes of my Stock Desire Z, I didn't do a thing on software or hardware side.
I run Android 2.2.1 Build 1.72.405.2 CL296256, provider KPN (Rabo Mobiel)
I got rid of the hangs after the upgrade from 2.2.0 then after several weeks it came back, only solvable by removing the battery.
I tried to figure out what's wrong and I think I have several clues:
- mostly some time after using Google Maps
- mostly when Wifi was on (it might be that the Wifi has limited connection and it screws up the data)
- after the reset I allways have updates from Market available
I can't remeber the Memory widget I ran, which I felt was having a good influence on the hangs.
I'm not happy with this behavioure, but cannot determine if it is hardware or software, it's not helping much that the phone just stalls , a reboot is irritating but less then a complete hangup when you don't know how long it has been in that status.
P.S. I don't run juicedefender
Cheers, Edward
I have STOCK G2 ROM.
S-off, CID, unlock via http://forum.xda-developers.com/showthread.php?t=855764
NO Cputuner or SetCpu (well I uninstalled them before these problems cropped up)
Used G2 for about a month and a bit no problems. Installed launcher pro then started to experience this problem. Coincidence? Not sure. Uninstalled and it did not help. Uninstalled several more apps that I recently loaded (skype, minimalistic text, Gtab Simi clock...) didn't help.
Wiped phone, nandroid backup to original ROM, restored using TB. Worked for a few days then just started happening again.
I also was using 2 chinese batteries I bought from eBay. Not sure if this has anything to do with it either.
// Just reflashed, HTC stock battery. Froze up within an hour. Too bad I bought this off of ebay, no warranty
// Factory Reset, restored apps and data with TB, still freezing
Hi all
I'm new to this forum (sorry, a newbie about to make a whole load of gaffs, no doubt), but I am at least fairly tech-savvy. I've had HTCs for years, right from the days of the 2000 vintage Compaq Ipaq!!
My wife & I bought two Desire Zs at Christmas, and it was therefore 50:50 which box was opened by whom. It appears I picked the dud, as I'm suffering from the issue described by all you guys, and in the other thread:
http://forum.xda-developers.com/showthread.php?t=857584
For the sake of adding more evidence to this otherwise confusing issue, I thought I'd join the forum:
So:
1) The device is not modded in any way. Standard ROM from HTC, being used on the UK T-mobile network. Currently at Android 2.2.1, Kernel 2.6.32.21-g540976a, Build 1.72.405.2 CL296256 "release-keys". This was installed on Christmas day, over the air.
2) There has been no playing with processor speeds or memory management.
3) The first crash of this nature was either on Christmas Day or Boxing day (ie the day-after-christmas-in-England); can't quite remember now, but certainly after the ROM update.
4) I have had this occur irregularly, but in increasing frequency, since that date. I think I'm probably into double figures by now, but I've only started to log them recently.
5) I was starting to think that there was some correllation with GPS applications. The phone would die after using Google Earth, for example, but not immediately. It may be after two or three standby's that it would fail to respond on the fourth, for example.
6) I had a very bad day a few weekends ago where the phone died four times in a single day. I had been using geotagging-photos (in the standard HTC camera app)... plus location-based services such as Yell and Google maps.
7) I tried keeping GPS disabled, and to be fair, there was no evidence of it crashing at that point. But I use GPS too much to make this plausible for a long time.
8) I wondered if it was due to the motion of keeping my phone in my pocket, but it died over night on the bed-side table on Monday-Tuesday, where my last usage had been the Friend-Stream widget/app. GPS was on...
During all of this, my wife's phone has not shown any of these symptoms. Whilst she uses Google Maps, Google Navigator & HTC Navigator a bit, she generally keeps the GPS turned off except for specific odd occasions. Hers has not crashed in this manner...
About to contact HTC to see what their response is...
This has occurred for me regardless of app usage.
It can occur right after a fresh reboot after being fully charged.
// Wow, I was in the middle of sending a txt and it just shut off on me...
I really wish I had a warranty on this
Hey there.
I can clearly pinpoint the problem with my desire z to the GPS. In the first view weeks I used it regularly and my phone froze, but only when the gps sensor was not active anymore (and the phone had gone to standby once or more). It didn't matter which app I used. For a while now I haven't been using GPS and my phone runs smooth as hell.
@lost800: I suppose your problem has a different kind of nature.
I already contacted HTC (very good support) and they told me to send it in to repair. I need my phone for work at the moment and I haven't found time to do this.
Due to the very small amount of ppl having that problem, I suppose it's an hardware error.
Greetz
Edit: Just out of curiosity, is there any meaning to the kernel version? Or has every mobile phone the same one?
Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).
dwardo said:
Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).
Click to expand...
Click to collapse
I called HTC support to see about getting the phone replaced. After explaining to the guy that it was freezing and then not rebooting when I pulled the battery out, the first thing he said was: "Did you install apps from the market ?"
Given that I replied by the affirmative he wanted me to test rebooting in safe mode and seeing if the freezes still occured before moving on to a replacement. He claimed that some market apps are not "properly coded and can mess up the phone"
I asked for and got the instructions how to reboot into "safe mode" (hit keyboard S key at HTC logo and stay on it while it boots)
In "safe mode" you can still install apps but they won't appear in the app drawer so you won't be able to start them (you can start them if they are on your home pages though ). No backgroud apps will run though (bbc, task killer ...)
Well I ran in safemode for 6 days and used the phone as I always do (work email, leisure email, web, video, camera, games, GPS, bluetooth etc...) and the darned thing ran perfectly. No freeze during those 6 days (the last few times it took less than 2 days to get a freeze).
I therefore decided it was time to test it again in "normal mode". Before rebooting I removed my task killer as for me this was "THE APP" that "safe mode" was really blocking from running on my phone...
Well It has been 2 days now and still no freeze. If it stays that way for another week I think I will have a rather good idea of who was the culprit...
Will keep you all updated and keep my fingers crossed.
Hi guys
An update:
HTC over the web-support were very helpful. Immediately they suggested that the device needed to be taken in for repair. In subsequent stages of the dialogue, they stated that the mainboard would be replaced.
A couple of weeks ago, I cleared down my device, packaged it up and waved goodbye to it (sniff...). HTC took it and...
!!DID NOTHING!!
It came back on Monday with an *old* ROM installed (1.35... If I remember correctly), and a statement saying 'no fault found'.
I've built the phone back up to where it used to be, including installing the over-the-air update to 1.72.405.2 (I need this as there's an activesync exchange bug in the old ROM) and within 24 hours, the device was unresponsive again
I have just written back to HTC to find out what the next steps are. I'd be interested to see if they suggest some debugging actions, like the safe-mode option, for example.
I've also asked them directly if their engineers have any clue what is causing this? Fundamentally, I don't see how any app should have the power to kill the device, however badly written it might be. That suggests insufficient controls/barriers in the OS.
Throughout this period, my wife's phone has continued to operate perfectly, even with some extra GPS playing to try to force a failure. So, we are now looking for any differences that could help to pin this down further. One difference is that she has never enabled the HTCSENSE.COM account on her phone, whereas I had. Perhaps there's some problem with the Phone Location functionality (in addition to the fact that I have to be in a yacht off the West coast of Africa for it to accurately show the phone's location). To test this, I've removed my HTCSENSE.COM account this morning.
Dwardo: I think your issue is slightly different, but the safe-mode info is useful.
Thanks
Andy
Hey guys, i need some advise here!
For weeks, i anxiously waited for the mailman to bring my my GNex and for a few days im very happy with it. Unfortunatly, the major plus of android, it never freezes, isnt true for my brand spanking new Gnex!
Seeming randomly, the phone freezes, refusing all input from the screen and the On/Off button. This happens about every 20 hrs.
Ususally i advise people with this problem to exchange their phone with a different one, but im afraid i wont get a stock 'yakju' build back in return, so want to try to fix (or at least determine) the problem first.
Can you guys give me some tips on how to get to the bottom of this?
Thanks in advance!
Info:
Model: Galaxy Nexus (GSM)
Android version: 4.0.1
Smalbandversion: I9250XXKK1
Kernel: [email protected] #1
Build: ITL41F (yakju)
And again, it's all stock
...
i had a lot of problems with the 4.0.1 fw, have you tried updating the phone to 4.0.2 it solves a lot of bugs!
I tried to update the phone through the system update menu in the settings, but it listed my phone as 'up to date'. I find this is odd, since i have a Nexus ánd the Google build
Is there a way of updating the phone without a lot of hassle?
I looked into it, in the Netherlands the 4.0.2 update should roll out in a few days. If it isn't, I'm going to flash it myself! Were your problems with 4.0.1 similar to mine e.g. crashes and freezes?
Sent from my Galaxy Nexus using XDA App
In my experience most of the time when that happened was caused by 3rd party apps that weren't ics optimized.
Sent from my Galaxy Nexus using XDA App
Well freezes and crashes maybe, but the whole phone unresponsive? Isn't there a try/catch somewhere which prevents this kind of 'dirty code' to crash the whole OS, anyway there should be.
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Sent from my Galaxy Nexus using XDA App
Same problem
Panatella said:
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Click to expand...
Click to collapse
That exact thing happened to me yesterday as well (running 4.0.1). I pulled down the notification bar, clicked on the email notification, and when the notifybar started collapsing again, the animation stopped, sound was caught in a loop, and two seconds later my phone rebootet with a clicking sound (I hope that it was just the speaker reacting strangely to the sudden signal loss...!)
The same day, the Nexus kind of crashed while I was streaming internet radio to my bluetooth speaker. The music kept on playing fine, but I wasn't able to turn on the screen. Even holding the vol+/- and power buttons only shut the phone down, but I couldn't restart before I removed the battery.
I really hope this is gonna be fixed with the 4.0.2 / 4.0.3 firmwares. This thing is crashing a little too often right now, for my taste
I'm getting the same problems as noted above. I've just picked up the nexus to move away from Apple's iPhones, but I'm left wondering I've made a serious mistake in doing so. An added problem is that the crash has also occurred when I've been recharging the battery while asleep- so the alarm I set did wake me.
Honestly, it's an unreliable product. I'm a customer, not a Samsung lab rat.
Got the same issue. 2 crashes in 4 days. Not a huge problem for me yet, but 4.0.3 better fix it.
Well most of my problems went away when i updated my phone. You should definitely try to update. Personalty I went straight for 4.0.3. The best ROM i've tested is definitely Android Open Kang Project :http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-build-13/
Everything just went so smooth and bugfree as far as i can tell. And i love the quick setting he put in notification bar.
You can see how to unlock your phone here using the gn toolkit :
http://forum.xda-developers.com/showthread.php?t=1392310
I had those kinds of crashes, too. My phone would crash maybe once every 3-4 hours on 4.0.1... doing anything. Whether it be idle, with no extra services (factory reset), or while composing messages. Anything would do it.
Anyway, I rooted the phone and I've been on Bigxie's ROM since V1 (AOSP 4.0.3) and the issue stopped, for the most part, except for an idle reboot every 18-28hrs. Suspecting it was kernel related, I swapped out the Apex kernel and threw on Franco's... since then, my phone can run for almost two days (of moderate usage) without a charge.
Any of you guys enabled 'force 2d hardware acceleration'? I don't know how relevant it is, but all my problems went away when I stopped to use this function.
Sent from my Galaxy Nexus using XDA App
Uv'ing too low can crashes also.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???
dhruvraj said:
Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???
Click to expand...
Click to collapse
U sure it's not a software u installed recently? For me changing back to the stock music player fixed the random crashing.
In general, I can say some apps are not stable at all.
I experience random crashes too, although they coincide with the sudden loss of signal, as described in these threads:
http://forum.xda-developers.com/showthread.php?t=1390816
http://forum.xda-developers.com/showthread.php?t=1387943
http://forum.xda-developers.com/showthread.php?p=20816554
I have started to make some logs to try to identify the cause of this problem. I use Log Collector for making a log and No Signal Alert to obtain a time stamp when the signal drops. What I see in the logs is that just before the signal drops I notice an entry in the log something like "process:com.lookout has died". Could this have something to do with the Lookout app I have installed or is it just coincidence that the app and a certain Android process have the same name?
By the way, does anybody know if there are websites or people who can analyze the logs I have created? Most of the content is mumbo jumbo to me and a knowledgeable person might be able to shed some more light on what happens inside the phone and what might trigger this problem.
I just upgraded to 4.0.2 on Thursday, but the problem persists.
Android version 4.0.2
Baseband Version: I9250XXKK6
Kernel Version: 3.0.8-gaaa2611
[email protected]#1
Build Number: ICL53F
ICS stock; non-rooted
Well i guess you tried already to remove the lookout app right?
My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.
b4cksl4sh said:
My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.
Click to expand...
Click to collapse
Are you sure it's the OS not some buggy/incompatible apps? I've had the phone since launch and it never froze even once. Stock 4.02 too.
And you should try out different OS. Then you will know what suits you.
I've been running the only official lt28 JB firmware for over a month now on an LT28at with AT&T as the carrier. Overall pretty happy with it, haven't noticed any 'day 1' bugs accept for the video recording lag (which for whatever reason is phone playback only? on my pc, through vlc, all the video's look great.)
However, only July 22nd, Google released the updated maps app....and things have kind of gone south for literally anything gps related ever since...
The issue is tricky. After i installed the updated maps app, my phone froze on the map screen while searching for a gps signal. After about 5 seconds, the phone rebooted...but it wasn't a full reboot it seemed...it only took another 5 seconds or so before i was back at the lock screen. If i hadn't been physically looking at the phone, i never would've noticed it happened. Before this update; i had never encountered this problem.
After the kind of 'mini' reboot thing...no matter what, any gps related app (my tracks, gps status, Torque Pro, etc.) would do exactly the same thing. If i turned the gps off or never used a gps related app, the phone would function normal as ever...after manually rebooting the phone by either a full reset, or just turning the phone on and off...the gps would function normally again...I could get a lock, could use any of the apps, etc...
after a few hours, though...it would freeze up on gps stuff again, and get into the same boot loop issue with any time the gps sensor was used.
I've tried rolling back maps, but the problem remains...and i'm kind of stuck now...I'm positive this showed up with the newest maps update, as i had been using JB for a while before it and never had any gps problem of any kind...
what i've tried so far:
flashed an AT&T ICS firmware back...gps functioned properly for 2 days without a single problem. because this is an LT28at, pc companion cannot do a repair for this firmware. I get a 'we couldn't find any software for this device' or something of that nature. I've wiped everything through flashtool, and reflashed multiple times, without any form of back up data. I'm not rooted anymore, as i wasn't crazy about the rooting method for JB to begin with. figured i'd just wait for the time being.
tried 2 different .ftf files of the same JB firmware...both have the problem.
clearing cache of any gps related app i have doesn't seem to effect anything.
the only thing that seems consistent is that the problem only starts happening after the phone has been on for a few hours. If it try gps after a fresh boot, it works perfectly. If i try again a few hours later, most of the time it freezes and quickly resets, but keeps doing it non-stop until i shut the phone off.
is anyone having anything like this? Any help would be greatly appreciated...
EDIT: this can be marked as solved i guess...found info on other phones with 4.1.2 having similar problems...something to do with memory allocation and the adreno 220 gpu...rooting and running a memory tweaker/task killer (greenify or autokiller memory optimizer both worked) has been a good enough work around for the time being...hasn't happened once since i switched autokiller to 'aggressive' memory management...no gps problems, and not one redraw...phone is actually running better than new now haha...
I got a freezing problem with my note2. It's quite a strange behavior, got worse pretty fast since yesterday (tried to reflect the situation exactly below).
The freeze behaves like: system freezes, apps freeze, buttons stop working, sometimes the notification bar pull-down still works for 1-2 seconds, BUT: animated icons in the notification bar are sometimes (not always) still animating up to 2-3 minutes. Can also happen with display off, can't turn on anymore.
Since I'm using a ROM that's safe from the SDS problem, it cant be that. Still I mention that I do have that insane chip (Type: VTU00M, FwRev: 0xf1).
My guess is its a hardware related problem, maybe the internal flash memory(?).
Still, it will be hard to restore back to stock for warranty with the usb not working to use Odin.
Original Baseband: XXALJ2
History of this phone (maybe not 100% accurate, it's hard to recall everything exactly):
Bought on release
rooted some weeks later
flashed CM ~spring, regularly updated
July: stopped showing modem signal strength
July: switched to Asylum CM10.x, updated on new version releases
September: USB stopped working correctly when connecting to computer (charging but no data, different cables, ports, computers)
October: started freezing randomly, approx every second day, getting slighly more often
Since Yesterday:
-did a full wipe/factory reset, reflashed rom. more and faster freezes
-as i was messing around, decided to do a modem update: from XXALJ2 to XXDMF1: radio signal strength working again. Freezing increased.
-reverted to backup, also restored old modem: Crazy fast freezings, withing 30sek after every boot.
-again some full wipes/clean install with different but still recent asylum roms: freezings a little better than with a backup, but still crazy fast.
-full wipe with format internal storage: freezes got better, occur after minutes instead of seconds. They still occur faster when using a backup instead of a new install. Same with CM 10.1.3.
No custom kernels used. Default governors. No TB restores or something that I could think of messing with stuff.
Any help or ideas are very appreciated
I could manage to restore stock via Odin (1 in 100 times it detects the usb connection on my laptop), with 4.1.1 Had a freeze, made the OTR update to 4.1.2. Had another freeze. After that 2 more updates. It also changed the Baseband every time, its now DMF1 (same as i upgraded). No freezes anymore. I mean, what the heck? This makes no sense for me at all. If someone can lighten me up, please, go ahead.
It all sounds like SDS. Don't forget that SDS happens if there is a memory block corrupted. If you were in an insane rom before (and you said you bought it in release so almost sure you did) the memory blocks got corrupted. that happened "a lot" of people in the SDS thread(between commas taking in account that here in xda there is not the whole group of people who bought it and percentatge is low).
I recommend you to use emmc brickbug check app and check the memory blocks(if you are rooted)
then if it is SDS the only thing that we can do is pray or wait to samsung not to give free repairs only to China.
hoping that you'll pass the blocks test and it was only a normal problem..
Sent from my GT-N7100 using xda premium
Thanks for your reply.
SDS was the first thing I thought could be the issue. But it run for months without a single freeze on a SDS-safe rom before it started.
The last thing I have done before reverting to stock was a memory check with emmc brickbug app, and it passed. I forgot to mention it, even it's very interesting: while the memory check was running I had the longest runtime without a freeze.
I'm thinking now of returning the phone for warranty because of the USB problem. It's probably too risky to get back to stock once again. If I even could manage to root it again. But tell them too I had freezes? hmm, it's really not happening now anymore
I have the same problem... no idea what should I do
well... Yesterday I took a try and swtiched the CWM. I had TWRP and I've switch to Phliz Touch, so far... 16 hours without freeze
Amit BL said:
well... Yesterday I took a try and swtiched the CWM. I had TWRP and I've switch to Phliz Touch, so far... 16 hours without freeze
Click to expand...
Click to collapse
hmm, I also switched back to CWM recovery (from TWRP) for the last boot (to restore the nandroid stock backup I did, but could manage to flash with Odin before I had to do it that way), that was the point where I was surprised that the emmc memory check did go through without a freeze. I didn't saw any relation to the problem here, but who knows?
So far 34 hours without a freeze
Sent from my Galaxy Note II using Tapatalk
dedors said:
I got a freezing problem with my note2. It's quite a strange behavior, got worse pretty fast since yesterday (tried to reflect the situation exactly below).
The freeze behaves like: system freezes, apps freeze, buttons stop working, sometimes the notification bar pull-down still works for 1-2 seconds, BUT: animated icons in the notification bar are sometimes (not always) still animating up to 2-3 minutes. Can also happen with display off, can't turn on anymore.
Click to expand...
Click to collapse
Same problem, been suffering with freezes for the last 3 weeks and the last 2 days have been 400% worse, found out about this emmc bug but cannot find any information as to how to fix it, some mention kernals, vodafone will not replace the phone unless their software update does not fix it, Running 3.99 RC2 Paranoid android. Anybody got any ideas?
Seems my phone is one of the effect chips with the emmc issue. Funny thing is i just flashed back to stock in order to take my phone back to the shop and its working fine.... not a single issue all day.
Is there something custom roms are doing that party causes this issue?
Sent from my GT-N7100 using xda app-developers app
Madnessx9 said:
Seems my phone is one of the effect chips with the emmc issue. Funny thing is i just flashed back to stock in order to take my phone back to the shop and its working fine.... not a single issue all day.
Is there something custom roms are doing that party causes this issue?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I was having different issues including freezes and WiFi/BT loss when kernels with undervolt installed. Usually from custom ROMs. The effect is prolonged sometimes till hardware reset done.
The only working solution (for me) is to use a kernel with controlled voltages and set all the voltages about 1000mV for frequencies below 800MHz. 100% stable,