Howdy,
Is there currently a patch or fix for the Lag on wake issue for TNT Stock? I would prefer if the only modification to the kernel (if its a kernel side issue) was for this specific issue.
Thanks!
Hi,
When TNT 3452 was found on a link (not via OTA), I thought that roebeet had said that he thought that the lag fix was in there, but I don't know if anyone has actually confirmed that.
Jim
Related
I know this works on vegan 5.1.1. Tried other kernels and had the problem with the wifi not working or frozen after wake-up. Turn off or on doesn't work and the only solution was a reboot. Perehoots 3/27 kernel seems to fix it whereas his latest 4/01 version seeks to bring the problem back.
Not sure which forum this info should be posted in.
http://droidbasement.com/db-blog/
Sent from my VEGAn-TAB-v1.0.0b5.1.1 using Tapatalk
lgkahn said:
I know this works on vegan 5.1.1. Tried other kernels and had the problem with the wifi not working or frozen after wake-up. Turn off or on doesn't work and the only solution was a reboot. Perehoots 3/27 kernel seems to fix it whereas his latest 4/01 version seeks to bring the problem back.
Not sure which forum this info should be posted in.
http://droidbasement.com/db-blog/
Sent from my VEGAn-TAB-v1.0.0b5.1.1 using Tapatalk
Click to expand...
Click to collapse
Hey this seems promising. i just got a new gTab and I flashed CM7. I don't get notifications when my screen is off and also my WiFi keeps losing connection. I need to toggle the wifi icon to get it back. this post of yours seems to address it. Can you give a noob guide to what I need to do? Does pershoot's kernel replace CM7 or add to it? Do I do the same - download zip, boot to clockwork, flash from sd card thing?
Wi-Fi
Who knows how to set up Wi-Fi on Linux.
Shall describe the step by step please.
I updated my stock Rogers Nexus 9020A via the manual update to 2.3.4 update went fine but now my search button randomly flashes and executes on it's own...is this a bug in stock 2.3.4? Also did a factory reset still problem exists.
Anyone else experience the same?
Im on Rogers as well. Had no problems at all...certainly not like this. Then i ended up switching to custom ROM's and what not just to add some enhancements. Try re-flashing? Did you create a backup first?
I had this problem prior to updating to 2.3.4. It has been 12 hours and I have not seen it occur. I am crossing my fingers on this one. Google claims they are investigating the issue. There were a lot of complaints on the Google Mobile forum. It seems random and occurs maybe once or twice a day, sometimes it skips a day.
So I was able to figure out the cause for the search button bug was the Baseband switching to KD1....I reverted back to 2.3.3 with baseband KD1 but problem still occured...once I switched the radio back to KB2 problem was gone....so any ideas on what I should do to get the Stock 2.3.4 update to function on my rogers device without the search button bug? I have not received any OTA notice on my phone yet. Anyone on Rogers receive the OTA?
So after trying to flash 2.3.4 many ways it is evident the baseband of KD1 is causing my Nexus S this search button bug. So now I am using 2.3.4 with the KB2 radio and it is rock solid. Anyone have an idea why only a select few nexus s 9020A phones are doing this after the 2.3.4 update?
Looks like a lot of people with the Canadian version Nexus S 9020A are experiencing the same problem once they upgrade OTA to 2.3.4 .....google is trying to narrow down the problem.
http://www.google.la/support/forum/p/Google+Mobile/thread?hl=en&tid=49e8ca84071d51a4&start=80
I cleared Dalvik cache, did not resolve the issue.
I know downgrading to kb2 would solve a lot of the issues, but then i still have issues with the search bug during navigation.
Let's see if we can figure this out.
Matridom said:
I cleared Dalvik cache, did not resolve the issue.
I know downgrading to kb2 would solve a lot of the issues, but then i still have issues with the search bug during navigation.
Let's see if we can figure this out.
Click to expand...
Click to collapse
Looks to be a confirmed bug in KD1 baseband:
http://mobilesyrup.com/2011/05/23/canadian-nexus-s-experiencing-voice-search-bug/
So your saying since you bought your nexus s with the stock 2.3.3 you have had this issue?....and is the issue worse once you update to 2.3.4 like I have?
Rob
richerob said:
Looks to be a confirmed bug in KD1 baseband:
http://mobilesyrup.com/2011/05/23/canadian-nexus-s-experiencing-voice-search-bug/
So your saying since you bought your nexus s with the stock 2.3.3 you have had this issue?....and is the issue worse once you update to 2.3.4 like I have?
Rob
Click to expand...
Click to collapse
Yup. I need to do more testing but with kb2 I would only get it in gps mode.
Sent from my Nexus S
I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?
qaaqq said:
I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?
Click to expand...
Click to collapse
I have the same issue, only the position is different. Have you worked out a solution? Or still waiting for it? Anyone?
Im on Miui with matrix cfs 5.5 (9023)
huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine
bucimaci said:
huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine
Click to expand...
Click to collapse
I have this problem also, im on CM7 nightly. cant unlock the screen. Phones barely 3 days old
Had that same problem, and it's gone now. Don't know what did fix it, but I flashed new radio and Trinity kernel, and the problem is gone now...
I thought with the 2.3.5 the problem was solved, but its back now... dunno what it is, my phone is 2 weeks old.
I'm experiencing the same issue on a stock, not rooted or in any way modified Nexus S I9023 (SCLCD version) with Android 2.3.6
Also the settings button is right under the line (so the location is different from the video) and it is unresponsive as well.
Does anybody have any idea what to do about this???
Another issue I've encountered with stock 4.2.1 from ASUS is that I can't even attempt to turn on Bluetooth. I know there are many issues with the Broadcom stack, but not even being able to turn on the stack?
Really?
Is this something others have experienced? If not, are there any suggestions to allow me to turn the stack on and have a fiddle about with some BT keyboards?
Look in general for the fix. Asus forgot to set the permissions on a file. You can only fix if you are rooted though. Or install CROMI or Energy if you want a stock based 4.2.1 rom
sbdags said:
Look in general for the fix. Asus forgot to set the permissions on a file. You can only fix if you are rooted though. Or install CROMI or Energy if you want a stock based 4.2.1 rom
Click to expand...
Click to collapse
Thanks for the tip, sdbags.
I did do a search in this forum, but was definitely looking in the wrong place.
http://forum.xda-developers.com/showthread.php?p=38885348. This link even has a method to change the permissions using root explorer.
I'm surprised ASUS hasn't pushed an OTA fix for this simple issue, so folks don't have to root their device to fixed a shipped issue.
Has anyone received any information as to why a recovery image for 2.2.2 was released but no OTAs have been uploaded?
I've tested out the image and it seems legit. The build number (29979_541.7190) seems to support my assumption that this build was legitimately made before 3.0, but the lack of an OTA seems very odd.
Hm, I can't seem to flash it. The error I get is always that system.img exceeds free space or something like that. Did you also encounter this problem? If you've successfully installed it, how does performance compare to 2.2.1 as well as the pulled 3.0? Thanks in advance.
amartolos said:
Hm, I can't seem to flash it. The error I get is always that system.img exceeds free space or something like that. Did you also encounter this problem? If you've successfully installed it, how does performance compare to 2.2.1 as well as the pulled 3.0? Thanks in advance.
Click to expand...
Click to collapse
I was able to flash it although it seems to be worse than 3.0. Haven't had 2.2.1 in awhile so I won't try to compare it.
Someone in my DB thread mentioned that an NVidia rep said that 2.2.2 is the image that new tablets are shipping with. It seems to be pretty similar to 2.2.1 as it does contain Android 5.0.1. 2.2.2 does seem to be noticeably laggier than 3.0. Although your issue is interesting, I wouldn't bother with finding a solution as 2.2.2 isn't worth it IMO.
Yeah, I flashed the 3.0 again because it worked well enough for me.