Your experiences with MyRemote v2.1 for iOS (iPhone/iPad)

[Cheese]

Dear all,

The fix is almost complete, we're finetuning on the last parts and aim to get it out very soon!

Kind regards,
JuAn

Hi Juan,

What is very soon? we're almost 2 weeks further by now..

Another additional 5 weeks?!?!!!

I'm afraid I'm running out of patience!

[Muccie]

Hi Juan,

What is very soon? we're almost 2 weeks further by now..

Another additional 5 weeks?!?!!!

I'm afraid I'm running out of patience!

Well... This evening a new version of the app for both iPad and a seperate one for iPhone became availble through the Apple app store. I deleted first the old version, then installed the new versions, that have the remark that there is NO fix for the memory-leak.... And on both my iPad3 and iPhone 4s, the apps don't even start!! They immediately afer a split second quit... Well done Philips!!!! Why oh wy..... There is a Dutch saying: als je het niet kan, moet je het niet doen. Think of that before trowing things on the marketet that only frustrate your customers...

[bluevoice]

Well... This evening a new version of the app for both iPad annd a seperate one for iPhone became availble through the Apple app store. I deleted first the old version, then installed the new versions, that have the remark that there is NO fix for the memory-leak....l.l And on both my iPad3 and iPhone 4s, the apps don't even start!! They immediately afer a split second quit... Well done Philips!!!! Why oh wy..... There is a Dutch saying: als je het niet kan, moet je het niet doen. Think of that before trowing things on the marketet that only frustrate your customers...

Same thing here on an iPad 2, app crashes and goes back to springboard. However the new version works ok on my iPhone 4S.

[Muccie]

After a full restart of my iPhone 4s the app now starts but didn't find my 47 PFL 9705 UNTILL I powered it off and on. Resetting iPad3 does not fix things, app still quits immediatelly.

[Toengel]

Hi,

in my blog I also got some comments, that users have massive problems with this new 2.2.1 release.

Toengel@Alex

[Philips]

Hi,

in my blog I also got some comments, that users have massive problems with this new 2.2.1 release.

Toengel@Alex

Hi all,

Please help us in getting some crash logs: see here. You can send them to nettv.forum@philips.com. Thanks for your cooperation.


Regards,
JuAn

[Muccie]

Hi all,

Please help us in getting some crash logs: see here. You can send them to nettv.forum@philips.com. Thanks for your cooperation.


Regards,
JuAn

Don't mind me saying, but are "we" now really your testing-audience ? You really want US to send these "difficult to find" or least deep to dig for crashlogs to Philips ?? Why ?? Don't you guys have a iPad (3) yourself for testing purposes ? Look at the "comments" in the Apple app-store: at the moment already 10 other users report the same problem !!

I am always happy to help, will later this evening if I am in a good mood search for the crash-log and send it but it is rather a shame that Philips needs to ask for this ! And I still have in memory that Philips despite my many, many, many complaints on all kind of levels and platforms NEVER EVER has reacted with a single letter on the annoying HTS5590 firmware problems (TV does "see" the first time after connection the HTS and displays all kind of "widgets", with one to switch to FM radio. If you power off the TV and on again, all these "widgets" are gone and it is NOT possible anymore to switch with the TV remote and HDMI-CEC to FM radio...).

[Philips]

Don't mind me saying, but are "we" now really your testing-audience ? You really want US to send these "difficult to find" or least deep to dig for crashlogs to Philips ?? Why ?? Don't you guys have a iPad (3) yourself for testing purposes ? Look at the "comments" in the Apple app-store: at the moment already 10 other users report the same problem....

Hi Muccie,

To be quite honest here, we have verified everything before the update publication and also double checked after the update yesterday in Appstore, and are (unfortunately) not seeing the issues as described. So something is wrong here and we need to ask this favor to you to be able to fix it as fast as possible.

Grtz.,
JuAn

[Muccie]

http://itunes.apple.com/de/app/phili...501031744?mt=8

You may have read these (German) replies already yourselves. After VERY annoying problems with 3 Philips TV's on the specific DynGop32 problem that Philips denied for many, many months, I had some mail (not email) conversations with your former Mr. Kleisterlee. He had one of his "Presidents Delegates" sent out to clear that matter. She keept me posted on all her steps by phone and at some point she told me: we better hire you as "tester" because we do not seem to do a good job there". The most ridiculous thing was, that Philips Germany kept on telling: we did test it, we do not "see" the problems. But: tons of "complaints" on the internet. It took me 3 months to understand what the problem was: Philips Hamburg did (at time) NOT have a cable-TV connection: they where "testing" with sat-signal, althought every deaf-horse could have understoond that the problem came from DVB-C (c=cable) reception. I had to tell Philips Hamburg that they could never have propperly tested BECAUSE it is not possible on their streetaddress to get a cable-TV connection at all ! And then all of a sudden things began to move. So please: testing and double-testing is nice, but DO NOT do it in a "lab", do it "in the field" under real conditions. Anyway, I will dig later this eveing for this log-files, but it'll cost you........

[Toengel]

Hi all,

Please help us in getting some crash logs: see here. You can send them to nettv.forum@philips.com. Thanks for your cooperation.


Regards,
JuAn

Hi,

just updated my blog entry with your request...

Toengel@Alex

[Muccie]

Hi Muccie,

To be quite honest here, we have verified everything before the update publication and also double checked after the update yesterday in Appstore, and are (unfortunately) not seeing the issues as described. So something is wrong here and we need to ask this favor to you to be able to fix it as fast as possible.

Grtz.,
JuAn

Well, I just tried it again: deleted the app, restarted the iPad3, loaded the app. And now it works..... Looking at the at least 10 others who reported the problem: could you guys have a time/date thing in the app, that it only works from a given date ? The "Programmführer" (I have as language German installed on my iPad) logo is now shown correctly. I digged for the .crash and .plist files: not to be found: could it be that they are only "made" if an app crashes and are deleted when the app (finally..) starts ?

It would be very interesting to find out WHY the app YESTERDAY did not work but works TODAY....

[valder]

I just bought my Philips SmartTV, and I was not able to download the MyRemote in both my iPhone or my Android phone. I leave in Canada, is that available for Canada?

Hi,

Please share your experiences with this new App version here in this topic. Channeling your input will make it easier for users to search and find relevant info.

Discuss here all your experiences when upgraded to the new App: new, old, positive, negative.....

I did not find a thread for that, although it is available for a while.

[smart]

Hello, I also updated as usually to the newest version on the iPhone4.
It worked without any Problems. So it is not completely untested and is working without problems at least for some people like me.

Greets

[Toengel]

Hi,

@Philips
Can you please update the changelog: http://www.supportforum.philips.com/...-for-Apple-iOS

Toengel@Alex

[DoubleYou]

For me, the app (2.2.1) behaves differently on iPad2 and iPhone4:

- iPhone4: after deinstall of the old version and installing the new version, it immediately started consuming hundreds of MB of memory, just like previous versions; therefore, I had to deinstall it to prevent all memory being consumed

- iPad2: even after an upgrade from the previous version (without deinstalling), the app starts and works normally and stays at 12.6 MB of memory consumption

(@Philips: maybe it's better to start a new thread with the correct version number in the title? This thread now says 2.1, while we're now discussing 2.2.x)