Apparently I didn't wait long enough! I manually flashed the update and all is normal but it does boot up faster than before.
It happens, just always turn on your TV to make sure your device is not updating before unplugging it from power.
Apparently I didn't wait long enough! I manually flashed the update and all is normal but it does boot up faster than before.
Hey guys - great work!
A few suggestions...
Some sort of reference to the thread ROM version number (e.g, 1.1), along with the Build version number (eg 14975.002) on the chromecast web panel would be cool.
Do you have any plans to make the home screen more interesting? Eg, maybe the ability to set a custom home screen (rather than those photos), or some sort of portal type page where maybe we could see things like the weather, calendar invites, stock prices - like Google Now, but for Chromecast! (obviously I realise this would be done via baby steps at first!
I just rebooted 14975.001 - and it rebooted back in to the home screen and didn't seem to pick up an update to 14975.002...?
Thanks for all your work!
James
My CC is powered by the TV so it doesn't matter but this time I removed it and used the wall wart to get the update but this does bring up a question. Do we always have to select the CC as our input to see if it's updating before turning the TV OFF? I assume it will show that it's in the middle of a update?? Powering OFF during an update isn't good as I just have found out!It happens, just always turn on your TV to make sure your device is not updating before unplugging it from power.
My CC is powered by the TV so it doesn't matter but this time I removed it and used the wall wart to get the update but this does bring up a question. Do we always have to select the CC as our input to see if it's updating before turning the TV OFF? I assume it will show that it's in the middle of a update?? Powering OFF during an update isn't good as I just have found out!
Or just disable OTA from the panel? What's the "Apply Updates" for? Does "Disable OTA" download but not apply?You don't always have to, but its good to check during a OTA rollout. Also, this is probably one of the reasons why the official user manual for the device says to use the external power brick instead of the TV for power. That way you cant interrupt the update process.
It happens, just always turn on your TV to make sure your device is not updating before unplugging it from power.
Can I make a future request for OTA updates? Could we make it so that it could be a manual process? Mine is powered on and plugged in 24/7 but I would like to be in control for when the update applies. I would hate to be fiddling with my system and accidently power it down while it was doing a update. Just something to consider .
Thats why you can disable OTA updates. Just disable them and watch this thread, so if theres ever a update you just do it by using a flashcast jumpdrive.
In a future update, is it possible to add the option to disable automatic updates, which would then display a "Check for an update" button in the Web Configuration Panel? This would allow the option of updating without the inconvenience of flashing manually with a FlashCast drive, and would make it safer for those who are powering their Chromecast via the TV's USB port instead of the power brick. No chance of accidentally corrupting the installation of a new update, if it's happening while on a different input and turning the TV off. Make sense?
Sent from my HTC One using Tapatalk
What's the "Apply Update" option for? Something in the future?No it does, and a force update check button was one of the ideas we were toying around with adding, which would pretty much do exactly what you are talking about.
I thought maybe an OTA Update maybe downloaded but not applied. Might be better if it was "Apply Changes"?you click that when you make changes in the settings panel to apply those changes.
How do you check the temperature of chromecast?
Sent from my SM-N900T using XDA Premium App
For the version thing, in the future on the home page under status we will have the panel check and tell the user if its the lastest build or not.
As for plans, yes we have more stuff in the works no worries and the custom wallpapers is definitely on the list of things to work on.
Reading recovery parameters
Looking for mods on /dev/sda1
Resetting crash counter and boot mode
Clearing OTAs
Copying /usr/share/flasher/remove-ota to /tmp/tmp.aRGbEu
Flashing mod at /tmp/tmp.aRGbEu
Mounting cache (mtd4) at /tmp/tmp.uvfrKt
Removing temp-ota.zip and ota.zip from cache partition (/tmp/tmp.uvfrKt)
Unmounting /tmp/tmp.uvfrKt
Removing temporary mod directory /tmp/tmp.aRGbEu
Mounting /dev/sda1 to /tmp/tmp.P1UmeJ
Using runtime directory /tmp/tmp.P1UmeJ/flashcast-data/1
Opened log file /tmp/tmp.P1UmeJ/flashcast-data/1/log.txt
Created large temp directory /tmp/tmp.P1UmeJ/flashcast-data/1/tmp
SETUP FAILED: No images found on /dev/sda1
Removing large temp directory
Unmounting and removing /tmp/tmp.P1UmeJ
I believe this has been posted before and happens when you haven't renamed the file to "eureka_image.zip".I had Flashcast and Pwndcast working fine on my Chromcast. I updated my flash drive to Flashcast 1.1.1 and tried to manually update to Eureka-ROM. However, after the Flashcast screen comes up the white light turns red after a few seconds. This is the log:
Code:Reading recovery parameters Looking for mods on /dev/sda1 Resetting crash counter and boot mode Clearing OTAs Copying /usr/share/flasher/remove-ota to /tmp/tmp.aRGbEu Flashing mod at /tmp/tmp.aRGbEu Mounting cache (mtd4) at /tmp/tmp.uvfrKt Removing temp-ota.zip and ota.zip from cache partition (/tmp/tmp.uvfrKt) Unmounting /tmp/tmp.uvfrKt Removing temporary mod directory /tmp/tmp.aRGbEu Mounting /dev/sda1 to /tmp/tmp.P1UmeJ Using runtime directory /tmp/tmp.P1UmeJ/flashcast-data/1 Opened log file /tmp/tmp.P1UmeJ/flashcast-data/1/log.txt Created large temp directory /tmp/tmp.P1UmeJ/flashcast-data/1/tmp SETUP FAILED: No images found on /dev/sda1 Removing large temp directory Unmounting and removing /tmp/tmp.P1UmeJ