Related
I had the Nexus S from the day it was launched but decided to return it within the 14 day cooling off period as I just didn't think it was worth the money and in its state at the time I didn't feel it was finished / polished as it should be.
Problems reported about the screen coating and the lack of responsiveness of the capacitive buttons also led me to the decision to return. I then started to hear stories of the phone not being able to hold a conversation for more than a few mins and the phone randomly powering off.
That was then and this is now. After the disappointment of MWC 2011 I am considering picking up the Nexus S again but I am interested to know what has improved since launch. I'm assuming the o/s has gone through a few updates and am hoping that the problems above are all now resolved.
Anything else anyone can add into the mix I would be interested to hear.
Never had a problem with it on phone #1. Didn't even have to return it.
CM7 on Nexus S is amazing.
The problems you listed have not been resolved.
Even with CM7 there are random reboots and lost of signal. Thes are gingerbread/google problems, not necessarily ROM related. Although I love the phone, it's not very stable.at least not compared to my ns1.
</signature>
This is worrying for a phone that's supposed to be at the bleeding edge as far as Google is concerned - a pthone that's meant to get all the updates as soon as they are available.
If Google know of these problems and have a fix in place (which I have read they do) then why not release it?
xspyda said:
This is worrying for a phone that's supposed to be at the bleeding edge as far as Google is concerned - a pthone that's meant to get all the updates as soon as they are available.
If Google know of these problems and have a fix in place (which I have read they do) then why not release it?
Click to expand...
Click to collapse
face it, gingerbread was not/is not ready for mainstream. yet so why would you want them to push out another update to fix a problem if that update just isnt ready yet?
Are you kidding me? I could live with a few niggling bugs, sure I'd even expect them but if I owned a Nexus S and it was dropping calls left right and centre I'd be looking for a fix pronto!
Fixes are due this week, supposedly (According to a video posted here). Engadget had a story on it here
http://www.engadget.com/2011/02/15/nexus-s-suffering-from-random-data-loss-reboots/
Who cares about Gingerbread? Awaiting Ice Cream where it combines Gingerbread & Honeycomb
but seriously, i haven't encountered ONE bug that has been mentioned. No reboots, smooth as hell, no browser lag. The only bugs I encounter are from CM7 nightlies [when they occur]
zephiK said:
Who cares about Gingerbread? Awaiting Ice Cream where it combines Gingerbread & Honeycomb
but seriously, i haven't encountered ONE bug that has been mentioned. No reboots, smooth as hell, no browser lag. The only bugs I encounter are from CM7 nightlies [when they occur]
Click to expand...
Click to collapse
Goto g4tv.com and let's see how smooth your browser is lol!
Sent from my Nexus S
princeasi said:
Goto g4tv.com and let's see how smooth your browser is lol!
Sent from my Nexus S
Click to expand...
Click to collapse
That's probably not Gingerbread though, that's probably just flash in general.
And there is a G4 app on the market.
Ill admit that it is laggy at the beginning when its still loading, but after its done loading.. its fine, but sluggish and not 100% smooth.
Uninstall flash and try it......just as laggy!.......thanks for upping me on the app tho!
Sent from my Nexus S
Am I the only one whose phone is just generally unstable? Running CM7 Stable right now, though I've gone through Weapon, Eaglesblood, and Miui (whitehawkx) and no matter what I'm running this omnipresent cloud of fail just seems to follow me. Applications will hang/force close, webpages will encounter errors, bits of UI will lag or not respond, the lockscreen will fail to turn on, the entire system feels like it was programmed by howler monkeys throwing keyboards at each other.
I wipe /system. I fix permissions. I disable SetCPU and don't use custom kernels. But still the phone just feels wrong. And it seems like it's been getting worse as time's gone on. Back in May/June the only reoccurring problems were GPS locks.
LOL, howler monkeys. I can't say I've experienced this. What roms were you running back before all this started?
96traxx said:
LOL, howler monkeys. I can't say I've experienced this. What roms were you running back before all this started?
Click to expand...
Click to collapse
It's just slowly gotten worse and worse. I can't point to a single moment when things "started".
LordButtersI said:
Am I the only one whose phone is just generally unstable? Running CM7 Stable right now, though I've gone through Weapon, Eaglesblood, and Miui (whitehawkx) and no matter what I'm running this omnipresent cloud of fail just seems to follow me. Applications will hang/force close, webpages will encounter errors, bits of UI will lag or not respond, the lockscreen will fail to turn on, the entire system feels like it was programmed by howler monkeys throwing keyboards at each other.
I wipe /system. I fix permissions. I disable SetCPU and don't use custom kernels. But still the phone just feels wrong. And it seems like it's been getting worse as time's gone on. Back in May/June the only reoccurring problems were GPS locks.
Click to expand...
Click to collapse
Not using a custom kernel well there's ur problem
Sent from my LG-P999 using XDA App
Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Stock JB was very laggy on my NS for some reason. Even swipping pages in the home screen was laggy. Some apps would instantly crash, too.
I've been running custom JB roms on my Nexus S, and its been running really well. The only thing is im experiencing the same lag that you do with Google Now. It has caused me to open my browser to do a search, which is disappointing, because in GB and ICS, the Google Search bar was so quick and convenient.
shyguyhighfive said:
Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Click to expand...
Click to collapse
The cards could be taking longer to load because of your flaky connectivity. Can't expect them to load instantly if your data/signal is dying all the time, can you?
Definitely an inferior experience here on stock JB compared to ICS. Really hope Google fix this in an incremental update, as it's a bit silly their second-best phone can't run JB properly.
polobunny said:
The cards could be taking longer to load because of your flaky connectivity. Can't expect them to load instantly if your data/signal is dying all the time, can you?
Click to expand...
Click to collapse
heh, that's a fair point. I'm not so upset with the cards taking a long time to load as I am that, while they are loading, the OS is very unstable. It's difficult for me to bring up the keyboard and search google while it's trying to load those cards. I can't believe it's not butter
Nothijngrad said:
Definitely an inferior experience here on stock JB compared to ICS. Really hope Google fix this in an incremental update, as it's a bit silly their second-best phone can't run JB properly.
Click to expand...
Click to collapse
My thoughts exactly . I was excited to get back on stock so I could have a functional phone without any added bells and whistles. New features are nice, but not at this price.
Try running a custom kernel.. Try the thalamus kernel its very stockish and it's SUPER smooth..
Sent from my Nexus S 4G using xda premium
I'm running stock on [email protected] with a matrix kernel everything smooth for me
Sent from my Nexus S using xda premium
I had problems with JB too. There were a few lags, especially with Google Now. Some apps would crash every time I tried to open them, and the launcher crashed every time I tried to change wall paper.
shyguyhighfive said:
Howdy hello,
I've been on my Nexus S since GB. Ever since I've rooted and been running custom ROMs. I've had some awesome experiences but some crappy ones at the same time, all of which I attributed to my phone running a custom ROM.
Now I've finally got the new, new stock JB on my device, and after running it for a few weeks, I'm a bit disappointed. The features are nice and all, but there are so many issues I face that make it near unusable. To name a few:
Google Now takes way too long to pull up. At least 5 seconds and even while it's loading the cards, it's very laggy. The search button used to be a quick way for me to search for something, but the is effectively ruined with this lag.
Constantly losing data / connectivity. I know this may be at the carrier level, but I've never had this much trouble. ALSO, in these cases, the phone will often be reporting that it has full bars / full 3g connectivity, so either way the phone is acting screwy. I mean seriously, the one thing I need my phone to do is make a damn phone call, yet it semi-frequently fails to do so.
Apps fail left and right. Today my youtube app crashed in the middle of the first video I pulled up on it. I know this isn't really the OS, but it's part of the stock experience, and I think android should be held responsible.
Just a few minor gripes. I'm just wondering: has anyone else experienced this? I did a full wipe before installing the stock JB rom, and I don't think it could just be root permissions making things go wacky. I may consider re-wiping and only installing a few apps, but I really don't have that much crap installed, so I'm not sure if that's the issue as well.
I saw another post recommending to get a new SIM card from AT&T. I have had mine for a few years, so that could be a possible fix for issue #2, but I don't think that's the entire reason.
Any feedback is welcome. Thanks a lot all.
Click to expand...
Click to collapse
Hmm I can say that AOSP JB is WAYYYY better than ICS. Soon I can port my ROM from the NS4G to the NS.
I have to agree with this. I've used stock JB when it was released, I was wowed by it's smoothness and cool animations. But everything felt a little slow and sluggish coming from ICS custom rom. After switching to Jellybro, JB feels both very fast and smooth. If you feel disappointed with JB, try using custom rom.
Sent from my Nexus S using Tapatalk 2
I don't know if you guys with problem tried that yet, but it might be a good idea to do a factory reset. You will lose all your data if not backed up but I'm getting a feeling it could help. JB has only been smoother than ICS for most.
Looking to get an NS soon, but it may help, as others have mentioned to run a custom kernel and bump up the clock speeds a bit.
My N1 is almost perfectly smooth (very little lag and often times none) with JB installed and overclocked.
My GNEX is smooth as butter. (As to be expected). But I guess what I'm saying is, if the N1 can run JB smooth, then the NS should not have any problems.
And while I know AOSP is technically designed to run on multiple devices, only two were in mind when JB was released....the N7 and the GNEX. Everything else is an afterthought in which AOSP may not be fully optimized for the hardware that is pushing it. (Just my opinion).
And another opinion while I'm on my soap box. JB is what ICS should have been.
In my opinion 512 MB of RAM are a tight fit for Jelly Bean. I can just run 3-4 background apps without kill-restart-kill-restart-kill-restart and a constant lag.
I remember some kernels used to have compcache support. Maybe I could try to enable compcache/zram.
got556 said:
Looking to get an NS soon, but it may help, as others have mentioned to run a custom kernel and bump up the clock speeds a bit.
My N1 is almost perfectly smooth (very little lag and often times none) with JB installed and overclocked.
My GNEX is smooth as butter. (As to be expected). But I guess what I'm saying is, if the N1 can run JB smooth, then the NS should not have any problems.
And while I know AOSP is technically designed to run on multiple devices, only two were in mind when JB was released....the N7 and the GNEX. Everything else is an afterthought in which AOSP may not be fully optimized for the hardware that is pushing it. (Just my opinion).
And another opinion while I'm on my soap box. JB is what ICS should have been.
Click to expand...
Click to collapse
I just got my GNex and the difference with JB on this phone is night and day. I didn't think it would be but I'm pleasantly surprised. But yeah. The RAM issue seems to be my biggest gripe with it on the NS. And for some reason, it just dominated my battery. I went through my first cycle on stock with Trinity and managed 3.5 hours of screen time over the course of almost 17 hours and still had a little under 50% remaining. My NS would've been dead long before that with the same usage pattern.....
I run stock JB with Matr1x. It works very very well.
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
ekerazha said:
In my opinion 512 MB of RAM are a tight fit for Jelly Bean. I can just run 3-4 background apps without kill-restart-kill-restart-kill-restart and a constant lag.
I remember some kernels used to have compcache support. Maybe I could try to enable compcache/zram.
Click to expand...
Click to collapse
Not to mention it only uses 368 mb of them. If it used the full 512, it would be pretty nice
I'm running Androxide 3.1 and used to run AdamG's custom ROM. Both ran great, no hiccups what so ever, Google now loads very fast, I guess it depends on your GPS and internet connection. My experience with JB is far better than the fastest ICS ROM out there, I believe given enough time, performance will become exceptional.
Logomotph said:
I run stock JB with Matr1x. It works very very well.
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
Not to mention it only uses 368 mb of them. If it used the full 512, it would be pretty nice
Click to expand...
Click to collapse
That can be tweaked a bit with different kernels.
I am running XenonHD 9 + marmite 4.2 kernel. It's stable and smooth. Worth a try.
Hello,
I have the following problem:
I experience visual artifacts when using two-finger rotate in Google Maps, also Photoshpere is really acting up... the images flicker...
Not all devices have it, as a matter of fact there are few of them (reported). Let's try to collect as much data as we can in order to find the cause of this and maybe a fix. I'll start.
HTC One S
Color: Gradient Blue
HBOOT:1.14.0002
Radio:1.06es.50.02.31
Jun 11 2012, 14:36:28
It's recommended to attach a logcat with the problem.
The problem allways happen when try to rotate Gmaps with two fingers, and photoshpere gets crazy especially after taking 1st photo.
It seems like an accelerometer problem, but accelerometer utilities seems to report the sensors working fine, so maybe a GPU driver problem.
C'mon guys, let's get this fixed
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Darknites said:
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Click to expand...
Click to collapse
I've tried many packs... i will try those and report back. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
adi4motion said:
I've tried many packs... i will try those and report bach. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
Click to expand...
Click to collapse
What you get both issues on Virtuous? that can't be good.
Darknites said:
What you get both issues on Virtuous? that can't be good.
Click to expand...
Click to collapse
yes... that's also what i'm afraid of...
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
PcFish said:
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
Click to expand...
Click to collapse
ok, that's not a problem, i can live without photoshpere, but the fact is Google Maps also have this problem and I need GMaps...
I know that at least 3 others reported this problem (and i'm sure that are many others who didn't test for it) I wonder where are they now...
I started this thread hoping that if other users reported it, the devs would try to solve this, but i think i'll just have to wait for HTC to give us JB and see if i still have the problem (but I am really concerned that I might have it). What's wrong with this One series? so many bugs (and not minor): cases chipping, helicoptering bug, sound issues, performance issues (one x), this problem....
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
wheeliemonster said:
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
Click to expand...
Click to collapse
when i rotate the map with two fingers i get visual artifacts
I have the same problem on photospere, on maps I have no graphical problems, but the magnet sensor seams to change it's direction sometimes. Had this on CM10, and now on 4.1 Sense+.
Edit: I mean I have the orientation problem on photosphere. My screen does not flicker.
I have this same exact problem with an HTC One XL. I have not found a fix for it.
I've tried flashing every flavor of jellybean there is. It oddly seems to not happen if I use a sense version of jellybean. But I hate sense and want vanilla android.
AOKP, AOSP, modded, unmodded, doesn't matter. I get this annoying graphics glitch when I try to scroll around using maps or photosphere.
I hope it's not purely hardware related, and that there's an easy software fix for it.
Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
LlirasChosen said:
Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
Click to expand...
Click to collapse
is the show screen updates or something similar on in developer settings?
dragon1357 said:
is the show screen updates or something similar on in developer settings?
Click to expand...
Click to collapse
Nope, I don't run that stuff because all of the rendering updates and stuff can get annoying to look at while working. I'm able to get the same issues on a fully stock rom, and a pure flashed rom, with a few programs installed. But the fact that the hardware render seems to be the issue to me is just very odd on a non-AOSP rom.
I have been having screen flickering issues ever since I flashed the latest AOKP build (AOSP) I originally thought that it was because of the kernal and the under voting that I applied but even with a different governor and normal volt settings the screen still flickeres. After some poking around I figured you that it is only happening while I am trying to type and by uninstalling the Swype beta keyboard the screen flicker had been reduced to almost nothing. I do not know why the keyboard would amplify the effect but if I use the system keyboard the flickering becomes almost non existent.
Also, the screen flickers anytime a pop up menu is on screen, such as in the tapatalk app, the menu that pops up to allow you to quote someone..
Sent from my SCH-I535 using Tapatalk 2
Had been having the same issue on Baked Bean 6, flashed BB7 last night and it seems the problem is gone. BB7 being 4.2.1 I'm guessing whether intentional or not somewhere along the process of updating the "bug" if it indeed was as it appeared was squashed.
I'd be curious to know what was causing this, if by chance you find a definitive answer please post it.
Thanks
Lk
I had a very similar issue for a while, i flashed LEAN KERNEL
Rebooted twice, and problem went away.
For an update, I flashed kt's latest kernal and the flashing has ceased.
Sent from my SCH-I535 using Tapatalk 2