Related
im running stock rom with no mods yet (im usally a heavy softmodder but its not worth it yet)
and today epistle rom gripper and ninjump wanted to update so me not carrying updated them and for the rest of my day my phone has been rendered useless it wouldnt send text calls or go on the internet via wifi or 3g and it stopped getting a radio signal all together when i usally have full bars
so it turns out the new update to one of these programs nocked my whole phone unstable and i want to know how and why because as soon as i uninstalled them i was able to connect to the net instantly and i got my missed calls emails and text in as soon as they where gone so.
can someone shed some light on this?
have never heard of anything like that ;(
You might have to check with the respective developers of those apps. Maybe the apps you updated are not optimized for Gingerbread yet. I'm usually the first to criticize Gingerbread for its slew of glitches, but in this case, it sounds like the issue lies with the applications themselves; especially considering once you uninstall them, your phone is back to normal.
onthecouchagain said:
You might have to check with the respective developers of those apps. Maybe the apps you updated are not optimized for Gingerbread yet. I'm usually the first to criticize Gingerbread for its slew of glitches, but in this case, it sounds like the issue lies with the applications themselves; especially considering once you uninstall them, your phone is back to normal.
Click to expand...
Click to collapse
it wasn't a big loss to me because i wasnt really using the apps. but what should i email them saying hey im running 2.3 on nexus s and your app almost bricked my phone? i dont know how to get the logcat without rooting it.
dudekiller said:
it wasn't a big loss to me because i wasnt really using the apps. but what should i email them saying hey im running 2.3 on nexus s and your app almost bricked my phone? i dont know how to get the logcat without rooting it.
Click to expand...
Click to collapse
Yes, more or less. Just reach out to them (there should be an "Email the Developer" option in the Market place of every app to find their email) and tell them briefly but precisely the problems you're having. Mention you're running Gingerbread 2.3 (2.3.1 if you want to be specific) on a Nexus S. If they're good about replies, you should hear from them. Then see what happens from there.
Anybody had this issue? all of a sudden keys stop working (or parts of the screen) - Default keyboard in the default and Handsent SMS the K and L have stopped working...
GiZiM said:
Anybody had this issue? all of a sudden keys stop working (or parts of the screen) - Default keyboard in the default and Handsent SMS the K and L have stopped working...
Click to expand...
Click to collapse
My touch screen stop working when I turn the phone upside down.. Not sure if this is the same problem.
Haven't had this happen. I've only had the auto rotate stop working.
Sent from my HTC Inspire 4G using XDA app
RayYung said:
My touch screen stop working when I turn the phone upside down.. Not sure if this is the same problem.
Click to expand...
Click to collapse
Honestly that's a really great idea if it was a feature. Think about it no more accidental answer/deny when pulling it out of your pocket if you put it in upside down. And how often if ever is the phone used upside down. I'm calling for a patent on this one!
I have this issue.
I have this issue and it goes far beyond the keyboard. I will be playing fruit ninja and half the screen will be unresponsive. Its happening quite a bit and I am thinking about exchanging my phone.
Same here
I've been having the same problems but I think it has only happened to me when I use custom ROMs such as Cyanogenmod or Coredroid. When I went back to stock I don't remember it happening.
I was running Coredroid V8.1 a few weeks ago and didn't like it because the font looked terrible but I think the keyboard didn't give that problem, it was with an older version of CD. Right now I am using Cyanogenmod 7.0 and it happens a lot and gets annoying. I now for a fact that is not hardware since the keyboard will work normally on landscape and other stuff will respond to the touchscreen.
Still trying to see if there is some sort of fix or to use a new keyboard. Installed GO keyboard and same thing happened, now using Swiftkey X and it happened also but now I took the protective case to see if that has something to do with it LOL.
edit: disregard.
ive had this problem also for awhile. i dont remember having it on the factory rom, but that was awhile back also. ive had it on every custom rom that i can think of. i used coredroid and cm7 for awhile. right now im using miui. ive tried 3-4 different keyboard at least, and had this problem with all of them. the keyboards accuracy also seems to decline. when switching to a new keyboard the problem initially goes away, but it eventually starts doing it again with the different keyboard.
I would try come non CM based roms as I have seen this come up a few times and the omr thing most have in common is that it shows up on CM based roms like MIUI. I have never had this issue on any sense based rom so that would lead me to think like wifi and Bluetooth that it is due to the non OEM drivers CM uses.
Coreddroid is a sense rom, and I had it back then. I've been using absolution, which is cm7 based, and have not since had the problem. The problem has also been reported to occur on non rooted, stock phones.
Sent from my Inspire 4G using XDA App
Nevermind that, I still have it.
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
Hi guys,
I'm an Android poweruser, but definitely no guru, so I decided to share this problem with you guys. Although less urgent, it's still bothering me.
I've recently (a few months ago) purchased my TF300t. For me, it's the perfect device. However, with all it's quad core magic, the browser frequently hangs on me. Sometimes, it just works perfectly, but other times it freezes for about 5 seconds after which I receive the force close image. Would I press wait, I could continue browsing. Until, of course, the next pageload. This might seem like something minor, but it completely ruins the experience of having a great quad core tablet.
Here's some facts:
It happens all around the web, although some websites seem to trigger it the most. An example of this is the website foodgawker.com, which is a responsive website. However, this website never gives problems on my S2 with CM9.
It happens randomly. At one moment it may happen each pageload, or it may not happen at all for about 15 pageloads. Feels random.
Other browsers either give the same problem, or a terrible browsing experience.
Yes, the problem occurs after a factory reset
Yes, I've upgraded to the latest available firmware.
After a lot of dialoque with Asus, I sent it off for repairs. But as expected, all they did was wipe everything on it, and the problem still exists.
In the meantime, Chrome for Android seems to have been updated, and the problem is less apparent.
My questions:
Does anyone else experience these kind of problems with their TF300t?
Would unlocking it and installing CM help?
The reason I'm asking is because I want to determine whether or not this issue is hardware related. I don't want to be messing with custom software when I'm not totally sure the hardware's fine.
Thanks in advance
Duveaux said:
Hi guys,
I'm an Android poweruser, but definitely no guru, so I decided to share this problem with you guys. Although less urgent, it's still bothering me.
I've recently (a few months ago) purchased my TF300t. For me, it's the perfect device. However, with all it's quad core magic, the browser frequently hangs on me. Sometimes, it just works perfectly, but other times it freezes for about 5 seconds after which I receive the force close image. Would I press wait, I could continue browsing. Until, of course, the next pageload. This might seem like something minor, but it completely ruins the experience of having a great quad core tablet.
Here's some facts:
It happens all around the web, although some websites seem to trigger it the most. An example of this is the website foodgawker.com, which is a responsive website. However, this website never gives problems on my S2 with CM9.
It happens randomly. At one moment it may happen each pageload, or it may not happen at all for about 15 pageloads. Feels random.
Other browsers either give the same problem, or a terrible browsing experience.
Yes, the problem occurs after a factory reset
Yes, I've upgraded to the latest available firmware.
After a lot of dialoque with Asus, I sent it off for repairs. But as expected, all they did was wipe everything on it, and the problem still exists.
In the meantime, Chrome for Android seems to have been updated, and the problem is less apparent.
My questions:
Does anyone else experience these kind of problems with their TF300t?
Would unlocking it and installing CM help?
The reason I'm asking is because I want to determine whether or not this issue is hardware related. I don't want to be messing with custom software when I'm not totally sure the hardware's fine.
Thanks in advance
Click to expand...
Click to collapse
Yes, exactly so in the stock browser or clones. Hitting "Wait" often seems to fix it. Just shifted to Chrome and haven't seen it happen. Got to say not impressed by the browsing experience with any browser - slowwwwwwwwer than I expected.
al89nut said:
Yes, exactly so in the stock browser or clones. Hitting "Wait" often seems to fix it. Just shifted to Chrome and haven't seen it happen. Got to say not impressed by the browsing experience with any browser - slowwwwwwwwer than I expected.
Click to expand...
Click to collapse
So you have exactly the same problem? That kinda saddens me, since exchanging it won't have any use then. Are custom roms known to fix this?
I also have this issue....however after using the "brows2ram" app and root access, it seems to have 90% disappeared.
search XDA for the brows2ram app, install, reboot, and grant superuser permission and it seems to help a lot.
after a lot of reading here and the TF201 (prime) forum it is a fairly common issue and most of the users believe the 5th companion core is to blame.
basically downloading/scrolling (two main things in browser) are both handled by the companion core...so when this is done, it boggs down the processor.
i have yet to hear if someone experiencing this on stock OS also experiences is on a custom ROM....would love to hear this.
but if you can wait, Jelly Bean should be here pretty soon....and since jellybean was built around the nexus 7 which has almost identical specs, all lag should be gone. i expect JB to be here by september....hopefully.
in the mean time, brows2RAM has helped tremendously and makes me not even have a desire to unlock and ROM this thing.
turdbogls said:
I also have this issue....however after using the "brows2ram" app and root access, it seems to have 90% disappeared.
search XDA for the brows2ram app, install, reboot, and grant superuser permission and it seems to help a lot.
after a lot of reading here and the TF201 (prime) forum it is a fairly common issue and most of the users believe the 5th companion core is to blame.
basically downloading/scrolling (two main things in browser) are both handled by the companion core...so when this is done, it boggs down the processor.
i have yet to hear if someone experiencing this on stock OS also experiences is on a custom ROM....would love to hear this.
but if you can wait, Jelly Bean should be here pretty soon....and since jellybean was built around the nexus 7 which has almost identical specs, all lag should be gone. i expect JB to be here by september....hopefully.
in the mean time, brows2RAM has helped tremendously and makes me not even have a desire to unlock and ROM this thing.
Click to expand...
Click to collapse
This helps me out so much! It would explain why browsing is the only thing lagging, and games like Dead Trigger work flawlessly. I also forgot the Nexus 7 also has Tegra 3. I'm guessing Jelly Bean will work flawlessly on this tablet.
Thanks to your post I'm going to stop trying to solve this with Asus, as they'll probably won't admit this. I'll keep using chrome until the official update is here. I don't even think I'm going to root, because Chrome works acceptably!
Thanks!
Edit -> Also; September? Asus is that quick? I guess being used to Samsung, anything is quick.
I'm running hydro on tf300 with the stock web browser
the pause and wait option does still happen, but very infrequently
when I was on a stock rom, it happened all the time
now with hydro it rarely happens
And how is fluidity of web browsing? Because for me, even on Chrome, the experience isn't what I'd expect from a high-end tablet.
Try Ics Browser + and enjoy.
Duveaux said:
And how is fluidity of web browsing? Because for me, even on Chrome, the experience isn't what I'd expect from a high-end tablet.
Click to expand...
Click to collapse
web browsing seems fine on hydro
there are still the normal hick ups from time to time
the difference in speed and fuidity between hydro and stock is night and day
after being on hydro for about the last month
I really don't know how I could even stand the stock rom
on hydro everything is super charged, super fast, super smooth
I've noticed the same problem on the stock rom, for that reason I switched to a early version of cm10 with jellybean. Haven't seen it happen again ever since
Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.
Of course you can. Head over to the thread Nardholio started in the Development section.
http://forum.xda-developers.com/showthread.php?t=2405310
The first post has links to: the official CM site and to the Apex Github. The CM site has a changelog for nightlies. On the Apex Github, they maintain a list of known issues.
It's all there.
I caution you on expectations here. Android 4.4 was just announced with a very unfortunate name. I think Jelly Bean 4.3 has about 60 days to live. It would be silly to expect 10.2 to be stable by then. After 4.4 hits Nexus devices, I bet the Apex guys will shift their focus to 4.4 and we will repeat some of this process...
NavarroCol said:
Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.
Click to expand...
Click to collapse
it will probably never happen.
android 4.4 is just around the corner, so i guess the focus will be swapped on that, as it was for 4.3 and 4.2 before
CyanogenMod will do a final "release" build when 10.2 is EOL which will be the most stable we can make it. We also have a last 10.1 build we consider mostly stable, although it is unofficial. Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)
Nardholio said:
Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)
Click to expand...
Click to collapse
I have random freezes/reboots all the time on the official nightlies -- even the ones people claim are stable. The lockscreen freezes quite often too. Are these known issues or am I just a lucky one? I am running CWM and followed the installation instructions on the Cyanogenmod wiki.
I just installed alogerec and hopefully something will show up to troubleshoot my issue.
Problem with 10.2 nightly as well
I have a problem with the 10.2 nightlies I have tried (all from this week) that I emailed Narholio as he requested.
But since I am a n00b and cannot post to development threads yet I could not post details there. I have not done extensive testing because the screen stays black even though the buttons light up when I try to unlock the phone. I can usually get it to display by pressing the lock button again to lock it, then pressing it again to unlock it right away. This also seems to happen only after the phone has been locked for greater than 20 seconds. If the screen timeout happens, or if press the lock button to lock it, the display almost always works if I unlock it again before 20 seconds is up.
I have not noticed any reboots or other problems, but have not used it extensively because of the black screen problem.
Try http://ls.infernix.net/jenkins/job/apexq-staging/ build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app
I flashed build 336 last night and still have my phone lock up when trying to unlock it. This doesn't happen every time but when it does it either shows the back and menu buttons illuminated with a black screen or an unresponsive lock screen. In either case it will eventually reboot.
Sent from my SGH-T699 using xda app-developers app
Same problem
Nardholio said:
Try build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it
I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.
Good idea
DOMF said:
I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.
Click to expand...
Click to collapse
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?
computerinfo21 said:
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it
Click to expand...
Click to collapse
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1
computerinfo21 said:
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?
Click to expand...
Click to collapse
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running
Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.
Plenty of free memory
croogrog said:
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1
Click to expand...
Click to collapse
Yep, did wipe each time I tried multiple recent nightly versions which all do the same thing. The only one I've tried that works correctly is the 20130309 version.
DOMF said:
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running
Click to expand...
Click to collapse
I generally keep a tab open to this Relay forum so I can watch what's happening, but not many tabs. Also happens immediately after flashing, without even running any apps, much less installing any.
orange808 said:
Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.
Click to expand...
Click to collapse
I really haven't installed any. And when testing different nightlies I just flashed and it happens right away, didn't install a thing on them.
I decided to stay on a version for a while, so have had 20130920 since Friday, and I've used it long enough to know it is consistent. I have found another way to make it happen: incoming phone calls. When phone wakes that way it almost always happens as well. Today it finally showed the screen when I received a call, but 3 or 4 other calls the screen has just been black so I can't tell who's calling.
I discovered another thing since using this ROM for 6 days. Sometimes I get lines/bars/tearing on screen that won't go away until I lock and unlock the phone again.
I have some other phones that are broken, if I can fix one of them I might consider sending this one to a dev to temporarily play with since it seems to be the perfect test case for this problem. The screen is cracked (I got it used in this condition), which I would normally suspect to be the cause of the problem, however since it does not have either problem with stock ICS, stock JB, or the 20130309 CM I'm pretty sure it's related to something in CM10.2. Just new enough to Android I'm not sure how to track it down.
Thank you all for your help!
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
I also have a rev0 cpu phone, and I had a few lockup/reboots since I finally dove in last Monday (9/30) with Staging build 341. However, without me changing anything (still on the same build), they seem to have stopped. Last one I got was 10/2.
Edit: until just now. *facepalm*
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
I got sick of stock so I tried CM again. After flashing the 10.2-20131014-NIGHTLY-apexqtmo nightly I have not had one reboot or lockup in days. YMMV
Edit: Still haven't had a lockup on wake or reboot.
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
Hmm... I'll have to try again
Hmm... Sounds like I need to try again then. I tried one released after that and still had issues, but I will try to make some time later to try it. It is fantastic other than that problem.
newer nightlies
Anyone else having issues with the newer nightlies? I have been flashing one a week for a while now and I'm coming from the 14th. tried flashing the 21,22,and 23 all of them are giving me a boot loop at the samsung screen. I have dirty flashed, cleared cache and dalvik, updated recovery. none of them are working for me. Am I missing something? they don't work so i reflash the 14th and everything is good again.
tried in
CWM 6.0.3.7
CWM 6.0.3.8
CWM Touch 6.0.3.8
all with the same errors any help would be appreciated