Search the Community
Showing results for tags 'freezing'.
Found 3 results
My Pastel Meets arrived yesterday complete with its packaging and while I was happy about, lingering in the back of my mind was why would someone want to part with such a recent Tamagotchi? Well, I have unfortunately found the answer: it freezes everytime the screen turns on after it's reset. When the screen turns on, the tamagotchi stands frozen in place during its idle animation and while pressing the buttons does cause the accompanying sound effect, eventually they stop responding altogether. And the screen stays frozen like that probably forever since mine never turned off. Reseting the device causes it to act normal till, once again, the screen goes off and then turning it back on causes it to return frozen. Interestingly, it always remains frozen on the last screen that was open - such as the clock screen or outside - rather than returning to inside the house where the standard idle animaton would resume. If the screen does turn off, then the device will act normally which I've discovered is triggered by pressing the reset button. Taking this together with further observation of my M!Xes - the previous Tamagotchi version - I conclude the malfunction with my Pastel Meets is that the device is missing the programming that tells it what to do when the screen resumes. On both my Spacy and 20th Anniversary M!X, I discovered that the idle animation is not programmed to completely restart when the device is activated - as is the case with my On - but rather to resume from the last frame the animation was at when the device turned off. This was no doubt added for immersion to give the allusion that the tamagotchi continued moving off-screen instead of truly turning off. It is, of course, weak immersion since I never noticed it all this time but it does give a more immersive feel if you pay attention and turn the screen on immediately after it goes off, where the animation thus appears seemless. This explains why when I turn my Pastel Meets on, the screen is frozen on the last frame of the idle animation my tamagotchi did instead of being frozen at the start of the animation. It also explains why it freezes on both the clock screen and outside the tama's house rather than returning to inside the house and starting the idle animation. I already mentioned the solution to the freezing problem but, since I mentioned it as a detail, it is worth restating again: pressing the reset button causes the screen to turn off and turning it on again with the buttons causes the device to act normally. I theorize that the reason this happens is because the reset button overrides all other commands the device is being given by the programming inside of it and it always tells it to turn off the screen and then reboot which, of course, takes it to the download and clear data screen. For some reason, mine doesn't reboot but instead just turns off which I wonder may be because the programming is stalled and maybe when it recieves the command to turn off, that leads to it then being able to follow the other commands that direct it on how to behave when the screen is turned on again. If I had more programming knowledge, I could probably give a more educated guess if not answer that altogether, since all electronics are essentially machines following scripted directions written in a language the machine can understand. It might be worth noting that the solution I had created before I discovered the "reset trick" was simply to connect my Pastel Meets to one of M!Xes or On as I thought this might create a save point so that I wouldn't lose so much progress if I reset my Pastel Meets. I imagine this is actually true as after every connection on the Meets/On, it says that it's "updating" which of course means that it's saving data. This probably is not a good longterm solution as I would only have control during the narrow window where the device first reboots and I'd maybe have to leave it for a long time in sleepmode to reach its natural save points and then I'd have to reset it again. Or perhaps by that time I would have found out where it made all of it's natural save points and planned accordingly - whereupon it might make more sense to get a refund. I did buy it from Japan You Want and I can totally understand why they thought it was functioning fine because, oddly, none of these freezing problems happened in the baby stage - possibly because the baby stage has so much going on.
Hi, I'm fairly new to Tamagotchi, and I just got my first P's. I've been trying to install the VDAs onto the P's using a USB to IrDA dongle on my computer. I'm following the steps, setting up the connection on the P's, going to downloads, facing it at the infrared while keeping the device an inch away and level... and it gets to the Connecting screen and freezes. It's done this several times and I've had to pop open the back of the Tamagotchi to get it to work again. My computer downloaded the necessary drives for Windows 8 64bit (the device is a SigmaTel USB-IrDA), Device Manager says the dongle is working, so the problem doesn't seem to be on that end. I honestly don't know what else I can do. Is the problem on the P's, the IrDA, or the computer? At this rate, I don't know if it would be wise to consider purchasing an IrDA phone if there is something wrong with the P's. IDK if it's relevant, but the P's was purchased used and already has an english patch applied to it. I've not had any issue linking it to the pierce that came with it, and it seems to be running perfectly. I doubt that makes a difference, but I really cannot figure this out. So is there any advice on what to do, something I missed, something different to try, any other suggestions? I haven't a clue what I'm doing with this thing, but the picture guide I found seemed straight forward enough, just can't figure out why it's freezing, or if that's a known issue.
I've had my tamagotchi id l for a little over a year now and today I took it out after I had gotten to school and it was frozen. My heart sunk because this was my 9th generation and I was not about to start over. Anyone have any information regarding this issue?