Database Develop

[ROM Feedback] CM 6.0.2 (09/05/10)

To my knowledge, there is no thread dedicated to the new numerical releases of CM. Let us start with the newest, CM 6.0.2.
Please post your anecdotal data, including benchmarking scores, bugs, and glowing experiences. Perhaps this will serve as an unofficial repository for issues that prove consistent.
Note: After modifying my WiFi settings, specifically disabling sleep mode while the screen is off, I've encountered no related instability.
Mail FC Fix: http://forum.xda-developers.com/attachment.php?attachmentid=394316&d=1283500340
Systemic issues yet to be addressed:
-LEDs do not work save for charging
-Outgoing calls initially drop before reconnecting
-Lockups or reboots, likely stemming from SetCPU
-OS does not recognize internal storage

Does this version fix the wifi not staying on?

Did you change your settings to Never sleep for wifi and just left the wifi on? Thanks...I want to try different settings and see if I can eliminate reboots/shut downs.

are we waiting for the nightly for the newest fixes like LEDs or is there gonna be a new release like .3?

OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.

not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.

seanmcd72 said:
OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.
Click to expand...
Click to collapse
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.

Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I would have to second the issue with SetCPU. As soon as I overclocked it and began using the rom I noticed the phone would get hot abnormally fast and would reboot a few times within the first few hours. Not sure what is going on here as it worked fine on the RC.

Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I didn't even notice setcpu till you said that. Phone was back to 998mhz
Sent from my INCREDIBLE using XDA app

My phone doesn't vibrate when I receive an incoming call when the phone is set to vibrate.

Has anyone else noticed the keyboard lag when using the Messaging app? Browser and this xda app seem to work fine with no lag..
Other than that, smooth.

dnoyeb said:
not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.
Click to expand...
Click to collapse
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.

Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).

I get random reboots and freezes every thirty minutes if so on a fresh wipe of 6.0.3 I tried with setcpu and without but always with the built in hotspot running. Same issue since RC3

LED notifications dont work. LauncherPro Plus FCs on every reboot, other then those things im good with it, great wallpapers , great rom

Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...

Panda Fuzz said:
Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...
Click to expand...
Click to collapse
And you know the issue is the kernel because...?

mp3sum said:
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.
Click to expand...
Click to collapse
actually if you read the thread, you'll see koush himself is in there dealing with 6.0.2, offering up kernels and fixes...
he just hasn't updated the topic title.

Okay this may be a stupid question but how do I apply the mail fix?

mp3sum said:
Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).
Click to expand...
Click to collapse
Battery life was down to 81% 11 hours later, and the phone had been placed in Airplane mode while running Gentle Alarm and a few widgets (no auto task killer).
Breakdown:
System 0.6%
System Processes 0.3%
System Panel 0.3%
android.process.acore 0.1%
Plus several honorable mentions with 0.0%. I have yet to perform this experiment with Ruby or ID.

FIXED: [Q] Cyanogenmod bluetooth

Hi All,
Sorry if this has been covered anywhere else but I can't find the same issue.
I have cyanogen 7 stable on my NC now and it works fantastically (even with overclock to 1GHz) There is an option to enable bluetooth but it just says "enabling bluetooth" for a few seconds and then goes back to being disabled.. I know some people have bt working with CM7 on the NC so what can the problem be?
/mrintegrity

Same problem with mine.

I fixed it, holding down power button untill it does a hard shutdown (instead of just a soft reboot) and then the next boot i was able to enable it. This has worked for other people too.
/mr

mrintegrity said:
Hi All,
Sorry if this has been covered anywhere else but I can't find the same issue.
I have cyanogen 7 stable on my NC now and it works fantastically (even with overclock to 1GHz) There is an option to enable bluetooth but it just says "enabling bluetooth" for a few seconds and then goes back to being disabled.. I know some people have bt working with CM7 on the NC so what can the problem be?
/mrintegrity
Click to expand...
Click to collapse
CM7 "stable"? Did I miss something?

brad0383 said:
CM7 "stable"? Did I miss something?
Click to expand...
Click to collapse
He means the Nightly is running stable, not that there is a Stable version.

The hard reboot has worked for me as well. On one update flash, I also had to run the Fix Permissions process in ROM Manager and then do a hard reboot. After that, bluetooth was working as advertised.

Just remember this is STILL a work in progress, BT range ij the majority of cases is restricted to a foot or less and reading the various threads still a bit picky about what it will pair and connect with.

TP CM9 changelog and known issues?

Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.

StoneRyno said:
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
Click to expand...
Click to collapse
Known issues are basically the camera and mic don't work, some folks have wifi issues and some don't... and some have issues with the audio acting up when waking from sleep... I myself am happy to say I don't have wifi or audio issues... but camera and mic are driver issues that may never get to work. All in all very stable though
Sent from my cm_tenderloin using Tapatalk 2

If camera and mic are the only problems then I see no reason not to give it a shot. I don't know if I would ever use them.I was concerned that it was missing core functionality making it something one wouldn't use as a daily OS and only switch over to it for test scenarios and then switch back. I have cm9 on my Samsung epic (the one with hw kb). Would the current latest nightly be the one to go with?

Just curious, why are the camera and mic drivers so difficult? I would have thought having them running on WebOS was at least some of the work. I guess porting said work to Android is a completely different ballgame.

I wonder if the wifi/audio issues are still being worked on tho? Or are those of us with those stuck with em forever?

The big thing for me was hardware video decoding. Alpha 1 fixed that for YouTube, and alpha 2 finished the fix for Netflix and others.
If you haven't already, check out the thread at rootzwiki.
I was using webOS by choice until CM9 came out. I switched to CM9, and have been using it as my daily driver since the very first Alpha. I never video chat, but if I wanted to I know I can just boot webOS.
Don't let people here tell you CM9 (or the Kangs thereof) are unstable. Some people continue to spew that we don't have a stable version of android purely because its called an alpha. I don't think it will graduate past alpha without camera/mic support, and that may never happen. Right now, without trying, I am sitting at 587 hours of up time on my TouchPad. I can't think of a better word to use than "stable."
Sent from my Galaxy S II (i777)

Known Issues that I can think of. I know some were mentioned above, but all in one place is good.
Broken, NO FIX:
1) No Microphone
2) No Camera
Partial Workarounds:
1) Audio gets noisy with screen off. Kinda workaround: Turn volume down, only happens at higher volume levels. Or set screen timeout longer/always on while playing audio. No complete fix.
2) Wi-Fi dies or doesn't reconnect. Some people never have a problem, others do. Workarounds: First, set WiFi to always on so it doesn't turn off with the screen. Second, try changing the channel on your router, or if you have 2.4ghz/5ghz switchable, try using the other. If Wi-Fi still dies, toggle it off and back on.
3) Some people report that if the TouchPad fully discharges to 0% they have trouble getting Android to charge properly. Others report that if you reboot the device with it plugged in, sometimes it won't charge. I've experienced neither problem, but the best advice is, charge before the device shuts off fully, and unplug the charger/usb while booting.
Broken, but Completely Fixable:
1) Random crashes. Install CPU Master and raise minimum CPU speed to 384 or 416 depending on which works for you, and crashes go away. Also, don't overclock too much.
Setup Issues:
1) DPI is at 160dpi stock. This works for most things, except a few tablet apps and games will not work properly. Setting DPI to 120dpi fixes everything, but the display quality is not ideal. 132dpi is ideal, but breaks the market after a day or two. Most people use 160dpi or 120dpi.
2) The default launcher, Trebuchet, is NOT compatible with the 4:3 aspect ratio of the TouchPad's screen if you use any DPI other than 160. Why something so easily fixable has not been fixed escapes me, but you will quickly find you need a new launcher. Go Launcher HD is one of a few that are very friendly to the TouchPad.
App Issues (not really issues but you probably want to know)
1) A few apps really, really, really are picky about the screen size and just won't scale right. (see Trebuchet notes above). One example is Politico HD - it forces 16:9 aspect ratio and thus gets cut off. Some apps simply refuse to run. Contacting the developers rarely works. This is probably less than 1% of the apps on the market, however.
2) Some developers simply are too strict on app compatibility on the market, and whitelist only select devices. Getting compatibility from these guys is a longshot. Best option is to install on another device, grab the APK or use Titanium Backup to move the app to the TouchPad.
3) Some games (notably Gameloft is the worst) enforce device compatibility checks within the program itself and it will refuse to run unless you masquerade as an approved device by hacking your build.prop... which is not normally recommended.
Did I miss anything anyone?

[Q] Nook HD+ CM10.1 Issues

I am opening this thread for people to discuss issues with the CM10.1 and share solution and fixes that they have found to solve these issues.
I have noted that the auto brightness does not work for me. I do not notice any change in brightness in different light settings and it seems to be frozen. Does HD+ comes with a light sensor and is it supported by CM10.1.
Another thing I wanted to ask. Can we use MHL adapters to connect a Nook to a tv through HDMI. I was looking for an alternative to Nook branded adapter.
Thanks

excalibar001 said:
I am opening this thread for people to discuss issues with the CM10.1 and share solution and fixes that they have found to solve these issues.
I have noted that the auto brightness does not work for me. I do not notice any change in brightness in different light settings and it seems to be frozen. Does HD+ comes with a light sensor and is it supported by CM10.1.
Another thing I wanted to ask. Can we use MHL adapters to connect a Nook to a tv through HDMI. I was looking for an alternative to Nook branded adapter.
Thanks
Click to expand...
Click to collapse
I'm pretty sure there is no light sensor on a tablet that has no camera.

Overall CM 10.1 is a whole lot better than stock 2.1. Some games do not work that did with stock (Buggy Blitz, Moonshiners and NBA 2013), but all the Zen Pinball Star Wars games work (they did not with 2.1).
With CM 10.1, you can not get any more less intrusive with Android, especially compared to stock on the Nook HD+. The good news is there is no more stutter with apps and a lot of apps load faster. The bad news is some apps still load slow and there is intermittent lag when pressing to start apps or navigate. Tapatalk is an example. There can sometimes be a 5 to 10 second delay from the time the app is activated to the time there is an action. Same with navigating and with other apps as far as lag such as browsers and games. The weird thing is when games play, there is no lag or signs of touch response problems. Games play well and so do virtual pads for game emulators. The issue is not touch sensitivity, since the press registers, but sometimes takes a while before an action happens.
For whatever reason, the Nook HD+ has an intermittent lag problem that also existed with stock 2.1, though the app stutter has thankfully gone away. The lag really stands out when comparing to my S3 and Excite 7.7. Those both are stock, but respond instantly when activating and navigating apps and only have slight issues if updating apps in the background.
My Razr had a 4430 and was not laggy. The higher display res should not be a factor for such dramatic lag issue with the HD+. The lag seems to happen about 30% of the time, if I were to guess. For what I want it for, the lag is not a big issue, but seems to make no sense. Both HD+ I have used have the issue, but was hoping CM 10.1 would be the answer to fix it.
Bad memory management, perhaps? Added: Nope, if so, games in action would be laggy as well.

channeledbymodem said:
I'm pretty sure there is no light sensor on a tablet that has no camera.
Click to expand...
Click to collapse
You are right, there is no light sensor so autobrightness does not work.
Sent from my Nook HD+ running CM10.1 on emmc.

rushless said:
My Razr had a 4430 and was not laggy. The higher display res should not be a factor for such dramatic lag issue with the HD+. The lag seems to happen about 30% of the time, if I were to guess. For what I want it for, the lag is not a big issue, but seems to make no sense. Both HD+ I have used have the issue, but was hoping CM 10.1 would be the answer to fix it.
Click to expand...
Click to collapse
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.

verygreen said:
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.
Click to expand...
Click to collapse
Tapatalk seems to be a poster child app for the issue. It does seem like a wait state issue. Added: That said, it does not do it all the time, so probably not app specific. I just use Taptalk a lot. The lag seems to happen with most apps, but not all the time. 30% of the time seems about right. The good news is the stutter issue that was them main problem IMO with stock 2.1 is gone. No sign yet, in spite of the intermittent app start and navigation lag.
What app can I install to log the issue?
Thanks

rushless said:
What app can I install to log the issue?
Click to expand...
Click to collapse
I don't think there is a good one for logging.
I just need to be able to reproduce myself so I can poke at it from multiple angles.

It does seem to be an app start/stop and navigation lag. No lag when using touch or virtual controls in games.
Not having the stutter in the GTA games is nice. It was GTA Stutter City with stock 2.1. as in many other games. Smooth now, while playing a game.

channeledbymodem said:
I'm pretty sure there is no light sensor on a tablet that has no camera.
Click to expand...
Click to collapse
While I agree that HD+ may not have a light sensors, however, a light sensor has nothing to do with camera and primarily used to control the screen brightness. A camera can detect brightness through its image sensors which is separate from a light sensor.

Does stock firmware have auto brightness setting? Can not remember, but I thought it did.... I tend to not use it.

verygreen said:
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.
Click to expand...
Click to collapse
I would like to thank you first verygreen for your efforts. You have made the HD+ such a useful tablet.
I have noticed that sometimes my screen would turn off momentarily for no reason. This happen more frequently when I am using and charging he tablet at the same time. I believe that it is due to the magnetic cover flap sensors which goes awry for some reason. Is there a way to turn this sensor off for those of us who are not using a cover with magnetic flap?

rushless said:
Does stock firmware have auto brightness setting? Can not remember, but I thought it did.... I tend to not use it.
Click to expand...
Click to collapse
No, as many have said here, including me, there is NO hardware sensor, so auto brightness cannot work.
Sent from my Nook HD+ running CM10.1 on emmc.

As mentioned, I do not use it, but would not be the first time for a phantom setting. Look at stock 2.1 and the slow app loading, stuttering state that it is. Not exactly a model for strict user experience QA.

Getting about 4 or 5 random reboots per day but everything else seems fine. Using greenify to hibernate apps
Sent from my BN NookHD+ using Tapatalk 4 Beta

Not had a random reboot yet.

Must be some misbehaving apps since I have never had random reboots. However, my screen flicker once in a while if I charge and use it at the same time.

mrpunk2u said:
Getting about 4 or 5 random reboots per day but everything else seems fine. Using greenify to hibernate apps
Sent from my BN NookHD+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
You might want to check to see if you have GPS checked in location services. If you have that checked and an app like Google Maps runs in the background, that sometimes causes reboots.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
You might want to check to see if you have GPS checked in location services. If you have that checked and an app like Google Maps runs in the background, that sometimes causes reboots.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
GPS is off - not sure what's causing it - Also, i keep getting Google Sign in errors and asks for my password at least 2x daily

Intermittent lag aside, I use the Nook now more than the iPad 4. Same nice display clarity and not locked down.
Wild how an OS mod can change perspective on a device so much.

My biggest problem has been with touch, it's not that responsive sometimes and sometimes I have my finger hovering over a button and it clicks it (is that phantom clicking?).. Overall it's MUCH better than stock and mad props to all the developers. My girlfriends tablet has been getting random reboots as well, i'll check to see if GPS is on.

[Q] Screen becoming unresponsive.

Hey guys,
Long time lurker and follower of the site but my first post and I need some advice-
The screen on the kindle fire HD sometimes becomes unresponsive. The buttons like power and volume still work fine, just the touch screen itself seems to be the issue. It only seems to occur when memory/processor load starts to climb (like it's being dumped for space or something) and I can sometimes, SOMETIMES, hit the power button to lock it and unlock it to gain control again then I have to immediately close out of what ever app I'm in and close all running tasks.
While watching the memory available the lowest I've seen it drop to is around 125mbs and still not have an issue, or maybe it's spotty. Not fully out, but getting there.
This is also unrelated to the power issue I've seen posted, that when it's plugged in it can occur as well. Doesn't seem to care too much if plugged in or not.
This started on stock rom so I flashed it and installed cm11 which has definately improved the problem but not solved it.
So, just polling the minds of people here to see if anyone has a suggestion.

Latonya1 said:
i had same problem and what i did is i opened battery from the device and inserted its again and did a factory reset on my device
Click to expand...
Click to collapse
Removing the battery on the kindle isn't an easy feat. Are we talking about the same device, or did you attempt this on a phone? Because if this worked with the kindle, I am more than happy to put the time into trying but I want to make sure.
Thanks for the reply.

dlenoxx said:
Hey guys,
Long time lurker and follower of the site but my first post and I need some advice-
The screen on the kindle fire HD sometimes becomes unresponsive. The buttons like power and volume still work fine, just the touch screen itself seems to be the issue. It only seems to occur when memory/processor load starts to climb (like it's being dumped for space or something) and I can sometimes, SOMETIMES, hit the power button to lock it and unlock it to gain control again then I have to immediately close out of what ever app I'm in and close all running tasks.
While watching the memory available the lowest I've seen it drop to is around 125mbs and still not have an issue, or maybe it's spotty. Not fully out, but getting there.
This is also unrelated to the power issue I've seen posted, that when it's plugged in it can occur as well. Doesn't seem to care too much if plugged in or not.
This started on stock rom so I flashed it and installed cm11 which has definately improved the problem but not solved it.
So, just polling the minds of people here to see if anyone has a suggestion.
Click to expand...
Click to collapse
This happened to me once...however it was solved with me wiping the whole kindle in recovery(dalvick etc) and flashing the kindology rom.....good luck man :thumbup:
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed

Seems like I have had that problem before, was because I had to many background processes running. I try to keep my ram so only about 60-70% of it is in use when using it, and I also stopped using dolphin web browser, that is a nice browser but man does it use up a lot of resources. On another note I noticed one time my kindle had around a GB left on the internal storage it started getting sluggish so that's another thing to look out for, but I doubt it's the root of your problems. Kinda find it annoying that android uses as much ram as it does, its based on Linux but on a desktop is on my PC with 2gb of ram, it idles at 20% on Ubuntu(which would be like 40% on a kindle because it has half as much ram), whereas android idles at around 60%.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

itouchables said:
This happened to me once...however it was solved with me wiping the whole kindle in recovery(dalvick etc) and flashing the kindology rom.....good luck man :thumbup:
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Click to expand...
Click to collapse
I should have read over what kinology was before flashing it.. I'm sure it's a great rom, but I'm wanting something more android-e. Went great though, as far as the install- and thanks for the tip. Worse case I'll have that file to fall back on.

stunts513 said:
Seems like I have had that problem before, was because I had to many background processes running. I try to keep my ram so only about 60-70% of it is in use when using it, and I also stopped using dolphin web browser, that is a nice browser but man does it use up a lot of resources. On another note I noticed one time my kindle had around a GB left on the internal storage it started getting sluggish so that's another thing to look out for, but I doubt it's the root of your problems. Kinda find it annoying that android uses as much ram as it does, its based on Linux but on a desktop is on my PC with 2gb of ram, it idles at 20% on Ubuntu(which would be like 40% on a kindle because it has half as much ram), whereas android idles at around 60%.
Click to expand...
Click to collapse
As I've been doing a bit more testing trying to figure out what is going on, it does seem to happen more often when under 100~75mg of memory available. Idling now at 550 memory available now, thanks to a few tweaks here and there which has almost erased the problem when doing things like browsing the internet, youtube, netflix, etc. It's just happening now during games. Not as much- but still, in the middle of a game of Kingdom Rush it's a little frustrating to all of sudden have no control. And currently I've still got almost 7 gigs of space available as far as harddrive goes so that doesn't seem to effect it by much (at least for me).
Setting the I/O to noop, overclocking to 1500 (leaving the minimum to 350), and setting the zram compression to 28% were the tweaks. Also having Task Killer by rechild set to kill tasks when screen off has been a great fix when I do lose the touch pad controls as it'll free up some memory when I turn it off, leave it off for a minute, then turn it back on without really interrupting progress in several apps.
Still searching for a true, 100% fix so tips are still welcome and I'll keep everyone posted if I run across anything myself.