Toshiba TV29C90 problem; Image fades to black...

On 30/9/2017 12:25 AM, Mr. Man-wai Chang wrote:
> Start Your Engines – Firefox Quantum Lands in .....

Kamen Rider Drive OP theme song
<https://www.youtube.com/watch?v=ToWdmzTEHK0>


--
@~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!!
/ v \ Simplicity is Beauty!
/( _ )\ May the Force and farces be with you!
^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
不借貸! 不詐騙! 不援交! 不打交! 不打劫! 不自殺! 請考慮綜援 (CSSA):
http://www.swd.gov.hk/tc/index/site_pubsvc/page_socsecu/sub_addressesa
 
Roy Tremblay <rmblayrrroy@nlnet.nl> actually wrote:

However, even these two relatively weak 14dBi and 18dBi antennas can still
go for miles line of sight under the right conditions on the other side.
https://s26.postimg.org/jbamhcg6h/00eradio.jpg
Click to expand...

Update for Jeff and Rod:

Using that bullet and planar antenna above, I finally got around to
physically mounting the Ubiquiti Bullet M2HP connected to a 14dBi planar
antenna outside on a pole stuck into the leftover hole from an ancient
15-foot wide satellite dish which was removed long ago.
<https://s26.postimg.org/jbamhcg6h/00eradio.jpg>

Here are some LOS Android-based received-signal-strength measurements for
Jeff Liebermann and Rod Speed where I set up *exactly* what Rod Speed wants
to accomplish.
<https://s1.postimg.org/7za88bam6n/wifi.jpg>

Those measurements are roughly at about 300 feet LOS (-50dBm to -60dBm) and
at about 100 feet LOS (-35dBm to -40dBm) distance from the radio which is
wired to the SOHO router and set up as an "access point" (which is what Rod
wants to do).
 
On Monday, May 29, 2000 at 3:00:00 AM UTC-4, Matt wrote:
Hello,

I have two Heathkit 10MHz scopes and they both have failed at the same
spot. So I am wondering if anyone else has had this problem.

The problem is on the left vertical board and its down on the lower left
side of the board (when you look at the component side of the board). The
10 Ohm resistor gets really hot, and eventually burns up. The display is
majorly out of wack (for lack of a better term). Most controls have no
effect, but it is displaying something.

The model number for the scopes is: IO-4550.

Thanks to anyone that is willing to help me out. If you need more info
I have it. Thanks

- Matt Rizzo
Oakland University
School of Engineering and Computer Science (SECS)
Click to expand...
 
On Monday, May 29, 2000 at 3:00:00 AM UTC-4, Matt wrote:
Hello,

I have two Heathkit 10MHz scopes and they both have failed at the same
spot. So I am wondering if anyone else has had this problem.

The problem is on the left vertica
Click to expand...

On Monday, May 29, 2000 at 3:00:00 AM UTC-4, Matt wrote:
Hello,

I have two Heathkit 10MHz scopes and they both have failed at the same
spot. So I am wondering if anyone else has had this problem.

The problem is on the left vertical board and its down on the lower left
side of the board (when you look at the component side of the board). The
10 Ohm resistor gets really hot, and eventually burns up. The display is
majorly out of wack (for lack of a better term). Most controls have no
effect, but it is displaying something.

The model number for the scopes is: IO-4550.

Thanks to anyone that is willing to help me out. If you need more info
I have it. Thanks

- Matt Rizzo
Oakland University
School of Engineering and Computer Science (SECS)
Click to expand...

Hi,

I have the same scope, I put it a way working years ago and just turned it on today and it smoked. There is a burnt 10uf cap and 10ohm resistor on the vertical board in the minus 15 volt circuit. I believe the burnt components on my scope are C123 and R163-1, the cap is shorted. I will eventually try to replace the resistor and cap.

D. marino
 
On 10/15/2017 09:58 PM, dmarino2494@gmail.com wrote:
On Monday, May 29, 2000 at 3:00:00 AM UTC-4, Matt wrote:
Hello,

I have two Heathkit 10MHz scopes and they both have failed at the same
spot. So I am wondering if anyone else has had this problem.

The problem is on the left vertica

On Monday, May 29, 2000 at 3:00:00 AM UTC-4, Matt wrote:
Hello,

I have two Heathkit 10MHz scopes and they both have failed at the same
spot. So I am wondering if anyone else has had this problem.

The problem is on the left vertical board and its down on the lower left
side of the board (when you look at the component side of the board). The
10 Ohm resistor gets really hot, and eventually burns up. The display is
majorly out of wack (for lack of a better term). Most controls have no
effect, but it is displaying something.

The model number for the scopes is: IO-4550.

Thanks to anyone that is willing to help me out. If you need more info
I have it. Thanks

- Matt Rizzo
Oakland University
School of Engineering and Computer Science (SECS)

Hi,

I have the same scope, I put it a way working years ago and just turned it on today and it smoked. There is a burnt 10uf cap and 10ohm resistor on the vertical board in the minus 15 volt circuit. I believe the burnt components on my scope are C123 and R163-1, the cap is shorted. I will eventually try to replace the resistor and cap.

D. marino
Click to expand...

You're responding to a post made over 17 years ago.
 
On Sun, 15 Oct 2017 23:24:41 -0400, bitrex
<bitrex@de.lete.earthlink.net> wrote:

shorted. I will eventually try to replace the resistor and cap.

D. marino


You're responding to a post made over 17 years ago.
Click to expand...

Holy crap Batman..........
17 years ago, they hadn't even invented the electron yet!
 
I also have a BT 501MW, which was manufactured back in 1987 and sold in the Netherlands.
 
On Sun, 22 Oct 2017 06:43:48 -0700 (PDT), ameesdotme@gmail.com wrote:
> I also have a BT 501MW, which was manufactured back in 1987 and sold in the Netherlands.

heh.. How cute!
A google grooper's "Me Too" followup to a 3-year-old followup --
which, itself, was yet another google grooper doing a followup
on a 13-year-old post from Sept. 2, 2001.
 
On Sunday, 22 October 2017 17:39:41 UTC+1, Allodoxaphobia wrote:
On Sun, 22 Oct 2017 06:43:48 -0700 (PDT), ameesdotme@gmail.com wrote:
I also have a BT 501MW, which was manufactured back in 1987 and sold in the Netherlands.

heh.. How cute!
A google grooper's "Me Too" followup to a 3-year-old followup --
which, itself, was yet another google grooper doing a followup
on a 13-year-old post from Sept. 2, 2001.
Click to expand...

fwliw, the first domestic nuke was the 1967 Radarange. It had a door that opened downwards and an unsafely basic interlock. A rather different animal to any 1987 thing.
 
On Sun, 22 Oct 2017 13:53:26 -0700 (PDT), tabbypurr@gmail.com wrote:

On Sunday, 22 October 2017 17:39:41 UTC+1, Allodoxaphobia wrote:
On Sun, 22 Oct 2017 06:43:48 -0700 (PDT), ameesdotme@gmail.com wrote:
I also have a BT 501MW, which was manufactured back in 1987 and sold in the Netherlands.

heh.. How cute!
A google grooper's "Me Too" followup to a 3-year-old followup --
which, itself, was yet another google grooper doing a followup
on a 13-year-old post from Sept. 2, 2001.

fwliw, the first domestic nuke was the 1967 Radarange. It had a door that opened downwards and an unsafely basic interlock. A rather different animal to any 1987 thing.
Click to expand...
In 1972 or thereabouts when I was 15 or 16 a friend of mine had me
over for lunch in the new house his family had just moved into. It had
a Radarange/conventional oven combo in the kitchen. We nuked hotdogs
in the bun in the thing. I was duly impressed until about half way
through the hot dog when the bun got pretty tough as it cooled. But we
loved the thing so we nuked several more naked hot dogs and had them
on un-nuked buns. I remember wondering why there was a thing that
looked kinda like an antenna in the oven. We watched it rotate through
the oven window and figured it probably bounced the microwaves inside
the oven, kinda like stirring. And the oven window was weird too
because it wasn't plain glass but had a screen in it. It took us a few
days to realize why it had a screen. That thing was cool.
Eric
 
On 11/7/2017 8:29 PM, Xeno wrote:
FWIW, the original mini did not have chronic understeer and I could bat
my 850 around hairpins leaving my friend with his RWD 327 GM POS
swinging sideways all over the road behind me. He had the wherewithall
on the straightaways, the V8 engine saw to that, but on the hairpins the
mini was king. Power into the hairpins whether facing downhill or uphill
and let the car pull itself around the corners in a way the RWD POS
could never do.
Click to expand...

I remember the original Minis running at Lime Rock. A Corvette could run
away on the straight but somehow after the twisty stuff the Mini would
be stuck to its bumper again.

That's not a fair test because the 'Vettes handled for shit anyway
speaking of understeer, They did love straight lines.
 
On Monday, November 13, 2017 at 9:38:26 PM UTC-5, warge...@gmail.com wrote:
I have a repair box full of 1000a parts
Click to expand...


Then list them on ebay and don't reply to 17 year old posts. I doubt the OP even owns that toilet any longer.
 
He who is harry newton said on Tue, 21 Nov 2017 22:32:53 +-0000 (UTC):

Google admits it tracked user location data even when the setting was
turned off. It did so via cell tower data.
https://www.theverge.com/2017/11/21/16684818/google-location-tracking-cell-tower-data-android-os-firebase-privacy
Click to expand...

Does anyone know more about disabling "Firebase Cloud Messaging" services?
For example, what if you're on Android 4.3 (like I am) with all location
services disabled?

Here's another article...

Google collects Android users+IBk- locations even when location services are
disabled

<https://qz.com/1131515/google-collects-android-users-locations-even-when-location-services-are-disabled/>
Since the beginning of 2017, Android phones have been collecting the
addresses of nearby cellular towers+IBQ-even when location services are
disabled+IBQ-and sending that data back to Google.

Google was apparently collecting cell tower data from all modern Android
devices before being contacted by Quartz. A source familiar with the matter
said the cell tower addresses were being sent to Google after a change in
early 2017 to the Firebase Cloud Messaging service, which is owned by
Google and runs on Android phones by default.

Devices with a cellular data or WiFi connection appear to send the data to
Google each time they come within range of a new cell tower. When Android
devices are connected to a WiFi network, they will send the tower addresses
to Google even if they don+IBk-t have SIM cards installed.

Android devices never offered consumers a way to opt out of the collection
of cell tower data.
 
He who is nospam said on Tue, 21 Nov 2017 17:55:51 -0500:

you were *so* sure you had blocked google's ability to track you, going
to such extreme lengths as changing your google id every few weeks.

many people told you that you were still being tracked, but you blindly
dismissed it.

now you know.
Click to expand...

You would love that to be the case, but, you're jumping to conclusions out
of confirmation bias (i.e., you *wish* it were true).

I looked and I don't think it's the case for me since I don't see (yet)
anything called "Firebase Cloud Messaging" on my Android 4.3 phone.

Time will tell which phones were affected, but this is a good one for
Google to get sued on, as it certainly will take some 'splaining why they
captured unique cell tower IDs when Location Services were disabled.

All we know, so far, is that it started in January of this year, and that
it used "Firebase Cloud Messaging" services - whatever that is. I googled
it, and I don't think it's even on my phone - but it's too early to tell
just yet what's going on.

Google apparently immediately said they'd terminate the practice of
capturing cell tower unique IDs - so, it doesn't appear to be something
they sanctioned (because they wouldn't likely have agreed to terminate the
practice so quickly if they had their legal ducks already lined up).

Time will tell which devices are affected - but I don't even see the app on
my phone - which is rooted - so I can delete it - if I can find it - but it
doesn't seem to exist.

To other android users:
Q: Do you see a process for "Firebase Cloud Messaging" services?
 
On Tue, 21 Nov 2017 23:48:55 +0000 (UTC), harry newton
<harry@is.invalid> wrote:

To other android users:
Q: Do you see a process for "Firebase Cloud Messaging" services?
Click to expand...

It's not an app. It's service:
<https://firebase.google.com/docs/cloud-messaging/>
<https://firebase.google.com/products/cloud-messaging/>
You download the API and link it into your application. It runs on a
variety of platforms including Apple IOS.

More:
<https://www.google.com/search?q=Firebase+Cloud+Messaging>

--
Jeff Liebermann jeffl@cruzio.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
 
He who is Jeff Liebermann said on Tue, 21 Nov 2017 19:26:10 -0800:

It's not an app. It's service:
https://firebase.google.com/docs/cloud-messaging/
https://firebase.google.com/products/cloud-messaging/
You download the API and link it into your application. It runs on a
variety of platforms including Apple IOS.

More:
https://www.google.com/search?q=Firebase+Cloud+Messaging
Click to expand...

It's still early on since the news came out today, but it behooves us to
figure out then which apps incorporated the Firebase service.

BTW, I think this recent "mashable" article is dead wrong in that they
minimize the outrage by saying the unique cell tower ID was encrypted and
discarded.

"Nope, your Android phone's not secretly tracking your location when you
tell it not to"
<http://mashable.com/2017/11/21/google-android-location-tracking-services-turned-off/>

The mere fact the cell tower ID was *transmitted* to Google servers is the
breach of trust, IMHO.
 
harry newton wrote on 11/21/2017 6:48 PM:
He who is nospam said on Tue, 21 Nov 2017 17:55:51 -0500:

you were *so* sure you had blocked google's ability to track you, going
to such extreme lengths as changing your google id every few weeks.

many people told you that you were still being tracked, but you blindly
dismissed it.

now you know.

You would love that to be the case, but, you're jumping to conclusions out
of confirmation bias (i.e., you *wish* it were true).

I looked and I don't think it's the case for me since I don't see (yet)
anything called "Firebase Cloud Messaging" on my Android 4.3 phone.

Time will tell which phones were affected, but this is a good one for
Google to get sued on, as it certainly will take some 'splaining why they
captured unique cell tower IDs when Location Services were disabled.

All we know, so far, is that it started in January of this year, and that
it used "Firebase Cloud Messaging" services - whatever that is. I googled
it, and I don't think it's even on my phone - but it's too early to tell
just yet what's going on.

Google apparently immediately said they'd terminate the practice of
capturing cell tower unique IDs - so, it doesn't appear to be something
they sanctioned (because they wouldn't likely have agreed to terminate the
practice so quickly if they had their legal ducks already lined up).
Click to expand...

You would love for that to be the case, but you're jumping to conclusions
out of confirmation bias (i.e., you *wish* it were true).

There are the legal issues involved, but just as important if not more
important is the public image perception.

--

Rick C

Viewed the eclipse at Wintercrest Farms,
on the centerline of totality since 1998
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top