04-08-2016, 11:26 AM
Just wondered how many of you see 'blocky' or 'patchy' pixels when viewing google earth in streetview: 18 months later I still have this problem.
Bugfree: you had the same problem - were you able to resolve it? You said the problem didn't exist when you ran google earth in an LL live environment, but the problem returned following an LL install to disk.
Mike
Bugfree: you had the same problem - were you able to resolve it? You said the problem didn't exist when you ran google earth in an LL live environment, but the problem returned following an LL install to disk.
Mike
64bit OS (32-bit on Samsung[i] netbook) installed in [i]Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ Arm710@1.2GHz - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ i3-3110M@2.4GHz - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom N455@1.66GHz - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel T3200@2.0GHz - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel T7100@1.8GHz - LL4.6, works well with kernel 4.4; 4.15 doesn't work
2017 - Raspberry pi 3B (4cores) ~ Arm710@1.2GHz - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ i3-3110M@2.4GHz - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom N455@1.66GHz - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel T3200@2.0GHz - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel T7100@1.8GHz - LL4.6, works well with kernel 4.4; 4.15 doesn't work