• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Geniatech Enjoy TV

I've managed to upgrade 2 ATV2000s from a June version of Froyo to the January version of 2.3.4, however am proving unable to get the full market working, it just won't show the likes of Facebook and Youtube. I updated to the latest vending.apk as described in this thread, tried the whole clear cache, services framework, etc trick and also tried different alterations to build.prop, all to no avail... Any further suggestions would be much appreciated!

BTW: do other ATV1000/2000 users have actual access to these apps in the original market?
 
retspan said:
I've managed to upgrade 2 ATV2000s from a June version of Froyo to the January version of 2.3.4, however am proving unable to get the full market working, it just won't show the likes of Facebook and Youtube. I updated to the latest vending.apk as described in this thread, tried the whole clear cache, services framework, etc trick and also tried different alterations to build.prop, all to no avail... Any further suggestions would be much appreciated!

BTW: do other ATV1000/2000 users have actual access to these apps in the original market?
Click to expand...

I think when you are in froyo (june version) you have to install the version of november before the january version ;)
 
I'll test the range with my setup when it arrives as i have an lcd.
Plasma gives off an awful lot of infrared so this maybe interfering?
 
Microcessus said:
I think when you are in froyo (june version) you have to install the version of november before the january version ;)
Click to expand...

Surely I only had to make sure that the SPI was updated to 20111102? I did this (from original June version of Froyo):
-updated SPI to 20110907
-updated SPI to 20111102
-installed update20120111 (179MB)

Everything else seems ok...just that the market is incomplete...
 
retspan said:
Surely I only had to make sure that the SPI was updated to 20111102? I did this (from original June version of Froyo):
-updated SPI to 20110907
-updated SPI to 20111102
-installed update20120111 (179MB)

Everything else seems ok...just that the market is incomplete...
Click to expand...

On my ATV1000, I have the same SPI and update and Facebook loaded as part of the update20120111.

As for Youtube, the Market version that loads with the 20120111 update has Youtube (and I recall Youtube is loaded with the update). However I am using the 198MB version from MyGica. I also have a 184 MB version from Geniatech but no 20120111 178 MB.

Your problems may arise from the contents of the various updates.

Further, I have 2 other Android devices and they all appear to have different versions of the Market on them. However I do not know if the range and scope of apps available is significantly different. The 3 versions all appear to have most of the apps that am looking for.

Have you tried other markets such as AppBrain App Market, 1 Mobile Market, ******** Market, SlideME Market, etc.
 
Video porting Debian 6.0.2 (squeeze) to ATV1000:
MVI 1051 - YouTube

It is real the slow start on the X-xfce, lxde and gnome on more slowly, because of a long chain running loop file-> chroot-> vnc server-> vnc client-> X
 
schit said:
Video porting Debian 6.0.2 (squeeze) to ATV1000:
MVI 1051 - YouTube

It is real the slow start on the X-xfce, lxde and gnome on more slowly, because of a long chain running loop file-> chroot-> vnc server-> vnc client-> X
Click to expand...
I suspect I am seeing the same reason for a slowdown of Ubuntu. Do you know how big the Debian disk image is??
If anything the Ubuntu load on the ATV1000 is quicker than this (which is not saying much btw), but you do end up opening up multiple browsers as you think its not doing anything.

EDIT, Well I may have found the app - Is this it.
https://market.android.com/details?...sMSwxLDEsImNvbS5nYWxvdWxhLkxpbnV4SW5zdGFsbCJd

Footprint of 180MB. which is a fraction of either of the Ubuntu loads. If so I won't bother, as it also looks dog slow.
 
meggiedude step by step
- Debian is tried different sizes from 1 GB to 3.5 GB (3.5 GB maximum in the video, but the speed is the same)
- Of course I tried linux installer only for generation loop file.

This makes the porting of Debian Toucan W in the NAS - Network Attached Storage.
What was missing in android is present here:
- Servers - samba, nfs, ftp, I think you can raise all the necessary services and servers in the debian repositories are present.
- All loaders: torrent, http, etc. (in the debian repositories huge selection of clients)
- Writing/reading all types of files systems, ntfs, ext2/3/4 fat16/32, exfat and other exotic (in the debian repositories modules available)
- You can create software raid disks
- You can run a web server.

If something is missed will add later.
 
hi! please can enybody help me. my keyboard/remote stopped working. device is notonlytv lv2gbox. it arrived with old 2.2.5 soft. CC send me a update files, SPI and "mid-spi" for 512 model. after updating that "mid-spi", my keyboard stopped working. blue led on device is on, on keypress blinking in short blinks, but no cursor, no keypress respond. i know about that KB doesn't work in recovery console, but mine died 100%?!
pls, if someone know how to revert it to previous state or re-synchronize it with device.
THX!
 
vikidroid said:
hi! please can enybody help me. my keyboard/remote stopped working. device is notonlytv lv2gbox. it arrived with old 2.2.5 soft. CC send me a update files, SPI and "mid-spi" for 512 model. after updating that "mid-spi", my keyboard stopped working. blue led on device is on, on keypress blinking in short blinks, but no cursor, no keypress respond. i know about that KB doesn't work in recovery console, but mine died 100%?!
pls, if someone know how to revert it to previous state or re-synchronize it with device.
THX!
Click to expand...
Hi vikidroid, surely your problem with keyboard/remote is only temporary,
in the meantime you can connect an usb keyboard to the second usb port,
and work with it (up/down arrows, enter)
 
gio965 said:
Hi vikidroid, surely your problem with keyboard/remote is only temporary,
in the meantime you can connect an usb keyboard to the second usb port,
and work with it (up/down arrows, enter)
Click to expand...

gio, your words are music to my ears. but, it seems to me that all is dead. i know for usb solution, but, that in some way is better than this KB, but...

i'm looking for similar problem, no success. the most similar is when KB doesn't work in recovery console, but in system, i'm unique! (at least in something!) :D
 
vikidroid said:
gio, your words are music to my ears. but, it seems to me that all is dead. i know for usb solution, but, that in some way is better than this KB, but...

i'm looking for similar problem, no success. the most similar is when KB doesn't work in recovery console, but in system, i'm unique! (at least in something!) :D
Click to expand...
vikidroid, I take it you know that the keypad goes into "suspend" mode if you have double klicked the centre droid button. It comes out of this by clicking it again.
When its in this mode the blue light is constantly on.
Is there a chance you have done this, walked away and battery has drained.
 
vikidroid said:
gio, your words are music to my ears. but, it seems to me that all is dead. i know for usb solution, but, that in some way is better than this KB, but...

i'm looking for similar problem, no success. the most similar is when KB doesn't work in recovery console, but in system, i'm unique! (at least in something!) :D
Click to expand...
If your usb keyboard works in recovery mode :confused:, you could try this:

-4 wipe data/factory reset
-5 wipe cache partition

then reboot....
 
meggiedude said:
vikidroid, I take it you know that the keypad goes into "suspend" mode if you have double klicked the centre droid button. It comes out of this by clicking it again.
When its in this mode the blue light is constantly on.
Is there a chance you have done this, walked away and battery has drained.
Click to expand...

of course that first was to change batteries. no good. i know about suspend mode, and i done that also. not only twice pressed - ten times double! :D
i think i wrote (or maybe not), led on player light steady, but on KB only when i press button, but even then, on keypress, only short, quick blinks. i even find some re-connect procedure, "esc"+"g" then "y"+"quotes". i left it for some time to rest but nothing changes.

gio965 said:
If your usb keyboard works in recovery mode :confused:, you could try this:

-4 wipe data/factory reset
-5 wipe cache partition

then reboot....
Click to expand...
no, no, in recovery mode works only usb KB, and i done that also. i wiped everything what can be wiped.

is it possible that customer care of notonly tv sended me some false SPI file? because that happened after _first_ update.

first, they sended me "update20111102.zip", and "update_spi20111102.zip". that first went wrong. instalation was aborted.
i reported that, they said that i have too old uboot&recovery and that i MUST use some "mid-update" SPI file. and they sended me "updateSPI_512.zip". and NOW keyboard was killed. so, only logical is that THAAT file was wrong. after hours and hours of trying, posting to customer care, i founded that there are three souch SPI files. 256, 512 and 512F. they sended me plain 512. but what about 512F? somewhere stands it is for 512mb internal memory V2? which V2? v2 of what?

i'm loosing patience little by little. i'll wait for some more time for customer care and then i'll simply put that keyboard aside and use plain mouse.

if only i could find 2.2.x android and matching uboot&recovery. and do flash from begining.
 
vikidroid said:
of course that first was to change batteries. no good. i know about suspend mode, and i done that also. not only twice pressed - ten times double! :D
i think i wrote (or maybe not), led on player light steady, but on KB only when i press button, but even then, on keypress, only short, quick blinks. i even find some re-connect procedure, "esc"+"g" then "y"+"quotes". i left it for some time to rest but nothing changes.


no, no, in recovery mode works only usb KB, and i done that also. i wiped everything what can be wiped.

is it possible that customer care of notonly tv sended me some false SPI file? because that happened after _first_ update.

first, they sended me "update20111102.zip", and "update_spi20111102.zip". that first went wrong. instalation was aborted.
i reported that, they said that i have too old uboot&recovery and that i MUST use some "mid-update" SPI file. and they sended me "updateSPI_512.zip". and NOW keyboard was killed. so, only logical is that THAAT file was wrong. after hours and hours of trying, posting to customer care, i founded that there are three souch SPI files. 256, 512 and 512F. they sended me plain 512. but what about 512F? somewhere stands it is for 512mb internal memory V2? which V2? v2 of what?

i'm loosing patience little by little. i'll wait for some more time for customer care and then i'll simply put that keyboard aside and use plain mouse.

if only i could find 2.2.x android and matching uboot&recovery. and do flash from begining.
Click to expand...
WRT 512 vs 512F I guess you are refering to the instructions here:
http://www.nikingstore.com/support/20110907-SPI-update.pdf
Which form part of the instructions here:
Android OS 2.3 Upgrade Guide for Geniatech Enjoy TV BOX – ATV300/ATV1000/ATV3000 - NIKINGSTORE OFFICIAL BLOG | NIKINGSTORE OFFICIAL BLOG
I can only go with what I installed - which was the 512F file as my 512MB ATV1000 was running Android 2.2.5 originally, and this was the correct file for it.

I am unsure what the spec is of your box, but I suggest you go through these URL/PDFs and see if you can retrack and resolve your issue.

Good luck

MD
 
@meggiedude yes, those instructions are one of many i readed. as yours, mine was also 2.2.5, and guys from notonlytv sended me plain 512, and few mails later i asked about that "f" and "no-f", they said "if we sended you wrong file, your's device will be dead".
so, i presume that they know what are they doing.
 
vikidroid said:
@meggiedude yes, those instructions are one of many i readed. as yours, mine was also 2.2.5, and guys from notonlytv sended me plain 512, and few mails later i asked about that "f" and "no-f", they said "if we sended you wrong file, your's device will be dead".
so, i presume that they know what are they doing.
Click to expand...
lol, maybe.
Just for clarity, are they saying that the file they sent is correct otherwise your box would be dead, or are they saying you have bricked the machine by loading something that they sent to you?
 
their answer:
"we send you the correct file otherwise you didn't even switch on the device.

Regards
LIFEVIEW SRL"
 
vikidroid said:
no, no, in recovery mode works only usb KB, and i done that also. i wiped everything what can be wiped.

is it possible that customer care of notonly tv sended me some false SPI file? because that happened after _first_ update.

first, they sended me "update20111102.zip", and "update_spi20111102.zip". that first went wrong. instalation was aborted.
i reported that, they said that i have too old uboot&recovery and that i MUST use some "mid-update" SPI file. and they sended me "updateSPI_512.zip". and NOW keyboard was killed. so, only logical is that THAAT file was wrong. after hours and hours of trying, posting to customer care, i founded that there are three souch SPI files. 256, 512 and 512F. they sended me plain 512. but what about 512F? somewhere stands it is for 512mb internal memory V2? which V2? v2 of what?

i'm loosing patience little by little. i'll wait for some more time for customer care and then i'll simply put that keyboard aside and use plain mouse.

if only i could find 2.2.x android and matching uboot&recovery. and do flash from begining.
Click to expand...
You can try the downgrade to android 2.2 using update_spi_all_2.2.zip

The file can be found inside this post made by enviro8:

http://androidforums.com/3741327-post643.html
 
You must log in or register to reply here.
Back
Top Bottom