I have a really odd problem. I purchased 3 EU version WiFi only Streak 7. Only one of them, when updating to HoneyStreak or the new offical 3.2 HC, one of them have visible refresh rate problem (it is like less than 50 Hz so that i can see the screen image light vibrates, it flickers).
The weird thing is all off the are OK with Android 2.2.2. But after the update, only one of them shows this strange behavior. Any idea about what the hell is going on? I can't return it since it is OK with Froyo.
The workaround is to increase the screen brightness more than %60 and it becomes OK.
crime_of_heart said:
I have a really odd problem. I purchased 3 EU version WiFi only Streak 7. Only one of them, when updating to HoneyStreak or the new offical 3.2 HC, one of them have visible refresh rate problem (it is like less than 50 Hz so that i can see the screen image light vibrates).
The weird thing is all off the are OK with Android 2.2.2. But after the update, only one of them shows this strange behavior. Any idea about what the hell is going on? I can't return it since it is OK with Froyo.
The workaround is to increase the screen brightness more than %60 and it becomes OK.
Click to expand...
Click to collapse
It have this on 2.2.2 and honeycomb but I only see it on a white screen
well, I have same problem - did anyone find any solution already (i read that ICS have support for gpu) - did someone with EU version already do update to ICS and how is there with flickering?
Thank you.
i had the same problem with Honeystreak r8. So i reverted back to using Honeystreak r6, i found r6 to be totally stable and reliable build without any visible bugs.
Now im using the ics beta4 build, but its not stable yet and camera/radio/brightness dont work in that build. WIP for ics build.
Related
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk
Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.
angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!
angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.
I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.
queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!
anyone know how to fix the wifi Authenticating --> disconnecting --> loop on honeystreak? I had the same problem with my NC and an older version of CM7 but i am now getting it with honeystreak 2.0.
I am having the exact same issue, or also Im getting error when it trys to connect. I have looked everywhere and cant find a solution. Any help? This rom would be great if I could get the wifi working and if I was able to tether my phone to it. Its a Tmo dell.
Our best shot is waiting for dell to roll out hc and have the proper kernel
I just went back to the 3.1 RC3 because of the issues I have had with the 3.2 R2. The touchscreen isn't as responsive, the battery life is a bit worse than the 3.1 RC3, the wifi issues - I can't get better than 3 bars on wifi 5 feet from my router on 3.2 R2.
I may be the only one, but mine (wifi only - using the wifi build for 3.2) has another unusual bug. When the screen shuts off on it's own (to sleep) it vibrates just for a split second about every 15-30 seconds. I started talking to someone and it was in my hand and started to do this... when I pressed the power button to turn it back on I saw the "HoneyStreak by DJ Steve" screen very briefly... then the homescreen. Yeah, 3.2 R2 wasn't for me. Hopefully this month an official release for 3.2 will be here!
Hello,
Joined the forum recently,unable to post in any of the existing threads due to the 10 posting rule (yawn!)...hence started a new thread, Apologies if this has been already reported, cd not find the related thread.
I have tried all ROMs (barring MIUI) and observed the following
On 2.3 Stock ROM & Andro - The phone gets hot while using 3G (the lower part) and sometimes while on charge (not the battery). Is this normal and expected of a Huawei product ? I use a Huawei 3g dongle and have observed it to get hot on usage. Occasionally have also seen the phone to heat up while on EDGE. Not sure if this is my handset problem or something else (due to overclocking ???). Open to advice suggestions.
GPS is not working on Andro, it hooked on to the satellite only once post searching for 15 mins.
2.3 Stock ROM & Andro - I have seen other members report of Screen lag - is this the lag in screen display appearing post pressing the on/off button post screen lock or the delayed response while moving between screens ? I have not seen any delays while pressing ON/OFF in Froyo, India 2.3 Update, Good ROM 318D update or Andro update. And in all, i have seen delayed response while swiping to the next screen.
Is there Wifi Problem in Good ROM 318D ? I experienced WIFI issues;did not lock onto my home WIFI despite multiple attempts. No issues observed on other ROMs
Noticed Bluetooth headset (I use a Nokia) volume is very low in Official Stock ROM (2.2, India 2.3 and Good ROm 318D) but excellant and loud in Andro ?
Couple of more points/queries (pardon me if these are elementary !)
On 2.3 the EDGE/3G/WIFI notifications sometime goes White, what does this signify ?
Saw a thread on 1500mah battery, Anyone's used it ? Appreciate a review. My battery experience is just ok.
I rooted the phone on Official 2.3 ROM, installed ROM Toolbox, it asked for Busybox while trying to change system font. Installed that from market, however the phone restarted suddenly and hanged at Android Logo at start up. Where did I go wrong ?
Phone occasionally restarts, have read this in other CSL MI410 reviews, noticed this happen when there is an FC or the phone is busy !
Thanks
Couple of observations
Hi everyone,
I was up to ICS Rom yesterday, but everytime i unlock screen, i cant touch in the bottom of the screen, cant typing with h, g, j and somewhere around it, but on the right, left or top screen i can still use normal. Does anyone know what happen and how to fix it?
When im in CM7 Rom is was fine and has no problem
PS: Sr for my bad english i really not good in grammar.
Same problem but different area
I have the same issue.
On Apex i had no issues but when i upgraded to SlimICS 3.2. The right side of the screen ocasionally becomes unresponsive.
That is, on any keyboard from approximately the 'i' to backspace horizontally, and from enter to the top of the screen.
This whole zone randomly decides not to work. the only fix is to turn the screen off and then turn the screen on again, or backing out of the application and reloading it. The application can be anything, chrome browser, swiftkey, messages, whatsapp.
Does anyone know what the issue could be?
I'm running slimics3.2 with semaphore ics 1.0
I'm also running slim 3.2 and had the same issue with the sephamore kernal. I just reflashec the essentials and everything worked perfectly for me.
Sent from my SGH-I897 using XDA
I used the essentials kernel first and experienced the issue, i thought it was a kernel issue so I flashed semaphore afterwards. But I still have the issue...
arse87zx said:
I'm also running slim 3.2 and had the same issue with the sephamore kernal. I just reflashec the essentials and everything worked perfectly for me.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
I tryed AOKP 3.0 and didn't modify anything, also some another ROM but it still have a problem with the touchscreen
KunNuK said:
Hi everyone,
I was up to ICS Rom yesterday, but everytime i unlock screen, i cant touch in the bottom of the screen, cant typing with h, g, j and somewhere around it, but on the right, left or top screen i can still use normal. Does anyone know what happen and how to fix it?
When im in CM7 Rom is was fine and has no problem
PS: Sr for my bad english i really not good in grammar.
Click to expand...
Click to collapse
I hate to say this, but its probably the fact the phone does not like ICS, it is more than likely some sort of hardware incompatibility issue.
I went through this exact same thing, it was on a 1009 or so build number captivate, no matter what flavor of ICS, none of them would work properly with the touchscreen hardware, there was always a spot of the screen, at the lower center 1/4 portion of the screen, that was unresponsive. Flashing a Froyo or Gingerbread rom, the touchscreen was perfect.
So.. I sold that Captivate, purchaced a refurb Captivate off Ebay, and touchscreen is perfect with ICS (CM9 is what I run).
Wish I had something more helpful, but that's my experience. Good luck with it.
Curious about experiences. Right now I'm on the M3 Experimental.
It's really stable.. By far the most stable cm10.1 build I've ever used. Only thing Is the instagram videos come out fuzzed out and you can't see anything. That Sux
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Only one bluescreen in 24 hours so far. Using its boot image in the newest Slimbean, hope it continues to hold up.
I was just coming to post this exact same question. I had to go back to M3 because there were too many bugs in the subsequent nightlies.
But I think i'll try RC-5 and see what it's about.
I did flash it. Since that time I've had some issued with bluetooth where I've had to reboot the phone to get it to work. Also some "blue screen" and random reboots. Someone suggested I should probably reflash and clear everything (data, cashe, dalvik etc...)
jdekoven said:
I did flash it. Since that time I've had some issued with bluetooth where I've had to reboot the phone to get it to work. Also some "blue screen" and random reboots. Someone suggested I should probably reflash and clear everything (data, cashe, dalvik etc...)
Click to expand...
Click to collapse
The bluetooth issue seems inherent in any of the 4.2.2 roms. I've done clean installs , wiped with Darkside, etc. It doesn't really seem to matter.
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Installed 10.1.0 using the updater and had lots of problems. Audio bad, Bluetooth not working. Installed clean with a factory reset and it is very stable. Only issue is still some camera apps (Google drive scan, latest evernote) require setting Disable HW Overlays. But other than that, seems good
jdekoven said:
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Click to expand...
Click to collapse
Lots of random reboots followed by a blue screen, I have noticed that it happens a lot during or after viewing a video and certain games, it even has happened while texting. No where near stable, battery life is horrible and like I said the reboots are random but often.
I'm using the CM 10.1 stable release as the boot image for PAC-Man rom. So far, no blue screens, reboots or anything. I've messed around with it, adding the Google edition camera and other goodies I found in i717 forum. Flashed in the S-4 launcher and everything is still holding together. Battery life is okay, considering I'm using livewall paper and wifi also. 60% remaining after four hours.
I'll give it a few days to settle in.
10.1.0 (4.2.2), good so far
jdekoven said:
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Click to expand...
Click to collapse
I've been running the 'stable' version for a couple days and only one b.s.o.d. Runs smooth and battery is about the same at RC5. Camera is good as well. Don't use Blu-tooth so can't testify for that. I reboot every morning and that seems to make a world of difference.
Wish stock JB would come to us.
Anyone know how to get stock screen resolution back?
20130804-Nightly stable
Hey all, just thought that since I complained about how buggy the nigthlies were, I should come back and say that I am now on the 20130804 and it is very stable. I have been using it since Monday and i've only have one reboot. I initially had some screen flickering when I had a solid green background (from an MIUI theme), but I switched to another wallpaper and don't have that problem anymore.
Just FYI.