WebOS 2.2.3 is already there for Veer

[Herrie]

It's "PmA6Updater"! Please make sure to use the right capitals!

[kryptonite_2448]

Herrie,

Is it possible CreateMirror.com is down now? I can't seem to find any good links with the 2.2.3/.4 file.

Thanks.

[mefm247]

For anyone using either Herrie's scripts or the doctor from John Steffes and are having the reboot problem. I seem to think that it's actually coming from the distance sensor (when you put the phone close to your ear). In my experience I get tons of reboots if I put the phone to my ear, but haven't had a single reboot if I'm using bluetooth headset or the speaker phone. One thing to try out, but I haven't tried it yet, is to lock the phone before putting it to your ear, which is not ideal but which might not trigger the reboot.

Do let me know if this helps anyone as it will help us find a solution to the problem. Thanks!

[mefm247]

Originally Posted by kryptonite_2448

Herrie,

Is it possible CreateMirror.com is down now? I can't seem to find any good links with the 2.2.3/.4 file.

Thanks.

Tried downloading it yesterday and it was ok. Are you still having issues? PM me and I can send you the correct links.

[mgiammarco]

Hello,
I have a problem, I have followed herrie82 procedure to update my Veer.

Probably I have made a mistake: I have finished upgrade (without modem) but I have done an hard reset and now I have no data connection. So I am stuck in option1, how can I go in option2 considering that phone is not in debug mode?
Thanks!!

Mario

[devil.insulted]

Originally Posted by mefm247

For anyone using either Herrie's scripts or the doctor from John Steffes and are having the reboot problem. I seem to think that it's actually coming from the distance sensor (when you put the phone close to your ear). In my experience I get tons of reboots if I put the phone to my ear, but haven't had a single reboot if I'm using bluetooth headset or the speaker phone. One thing to try out, but I haven't tried it yet, is to lock the phone before putting it to your ear, which is not ideal but which might not trigger the reboot.

Do let me know if this helps anyone as it will help us find a solution to the problem. Thanks!

I had 2.2.4 running on my veer perfectly for sometime but then i had to redoctor it to 2.1.2 due to some reasons.
Recently I redoctored my veer almost 4 times with 2.2.4 in last month and it works for a few days, all of a sudden it will reboot and then erase everything.

Has anyone else seen this issue?

[Herrie]

I have been running 2.2.4 since December last year without these issues.

[John Steffes]

Originally Posted by devil.insulted

I had 2.2.4 running on my veer perfectly for sometime but then i had to redoctor it to 2.1.2 due to some reasons.
Recently I redoctored my veer almost 4 times with 2.2.4 in last month and it works for a few days, all of a sudden it will reboot and then erase everything.

Has anyone else seen this issue?

My Veer has been on webOS 2.2.4, sense the testing on the Doctor process with the included A6, TouchPanel, and Modem firmware (about three months), never had a reboot with erase, although I am WiFi only (no SIM), is connect to a profile... Grab the messages log and post...

[devil.insulted]

Thanks for the update, Even i had it working for a few months before i redoctered it to 2.1.2 and since then no luck.
I love my veer, but I think its time to say adios.

[TheOneill]

Originally Posted by mefm247

For anyone using either Herrie's scripts or the doctor from John Steffes and are having the reboot problem. I seem to think that it's actually coming from the distance sensor (when you put the phone close to your ear). In my experience I get tons of reboots if I put the phone to my ear, but haven't had a single reboot if I'm using bluetooth headset or the speaker phone. One thing to try out, but I haven't tried it yet, is to lock the phone before putting it to your ear, which is not ideal but which might not trigger the reboot.

Do let me know if this helps anyone as it will help us find a solution to the problem. Thanks!

Did someone else notice that ? It seems to be interesting, if the proximity sensor causes the reboots, we can try and patch the phone application.

[dbmgreen]

Originally Posted by TheOneill

Did someone else notice that ? It seems to be interesting, if the proximity sensor causes the reboots, we can try and patch the phone application.

Yep had that problem, removed my screen protector, and it went away?? Go figure

[Herrie]

Originally Posted by dbmgreen

Yep had that problem, removed my screen protector, and it went away?? Go figure

That's interesting indeed. I must say I have had a lot less reboots lately anyway!

Could be coincidence (maybe network equipment updates around here?), but they seem to get less.

Interesting if it would indeed be caused by the proximity sensor. I should be quite straight forward to patch the phone app so it ignores the proximity sensor

I'll have a look into the phone app source code to see if I can find the proximity sensor code bits somewhere....

[DRS10]

Originally Posted by Herrie

That's interesting indeed. I must say I have had a lot less reboots lately anyway!

Could be coincidence (maybe network equipment updates around here?), but they seem to get less.

Interesting if it would indeed be caused by the proximity sensor. I should be quite straight forward to patch the phone app so it ignores the proximity sensor

I'll have a look into the phone app source code to see if I can find the proximity sensor code bits somewhere....

In my case the reboots stopped for a long while, as in months but then came back eventually. In an different form though. It happens now and then after accepting a call: after some seconds it hangs up by saying 'call from...rejected'!!
It always happen when I place the phone to my ear, so the proximity sensor is indeed very likely to cause that. So no reboots anymore just rejecting a call after answering it.

[Herrie]

OK, any volunteers to try attached patch? I didn't test it yet myself to be honest, but should do the trick

This should disable the proximity sensor completely. Every time it tries to enable it it will actually disable it. When it's enabled already, it will disable it too

[TheOneill]

Thanks for this patch Herrie, I successfully installed it on my 2.2.4 Veer that I had put aside because of reset problems. I will test how it works without proximity sensor and give my feedback here.

Lionel

[Herrie]

Thanks for this patch Herrie, I successfully installed it on my 2.2.4 Veer that I had put aside because of reset problems. I will test how it works without proximity sensor and give my feedback here.

Lionel

Great loking forward to the test results!


-- Sent from my TouchPad using Communities

[TheOneill]

I made a lot of test calls with herrie's patch yesterday and results are quite good. Over about 50 outcoming calls, I had no reset if I let the screen on when I take the phone to my ear. I wanted to try whether turning the screen off before doing so (as the proximity sensor logic would do before patching) had an effect on reboot, and the answer seems to be yes. If I try turning the screen off just after dialing while I'm waiting for the other side to answer, I cannot make 5 successive call : I always have a reset very shortly after the call is answered (5-10 sec max I guess). So maybe the problem does not come from the proximity sensor itself but from the consequence (screen off or maybe something caused by the screen off ?).

I have to confirm that making more tests, trying incoming calls too. Maybe someone else want to try that ?

I noticed that even if you don't turn the screen off manually, it goes off after the regular timeout anyway and I did not have any reboot due to that (though it may not be significant because I did not wait enough at each call to let the screen go off). Maybe the problem comes from the screen being off very early in the call, when the call is answered ?

Lionel

[Herrie]

Thanks for the feedback so far! I'll try and have a look to see if I can find some other bits in the phone app with regards to switching the screen off. Maybe I can patch it so it stays on during call? What are your ideas?

[TheOneill]

I believe that the problem does not come from the screen off itself but from the timing of the screen off. If I try to make longer calls and just let the screen go off by timeout (so, long after the call is answered), there is no reset. So I think we don't have to force the screen ON during all the call, maybe we just have to delay it or try to understand why the screen off cause a problem at this precise time.
I noticed something with the veer when I was running 2.1.1 : when I removed the phone from my ear before ending the call, the "connecting" then call timer white label displayed by the phone app was always briefly displaying "0:00" then one sec later or so displayed the right call duration. I did not notice that behaviour on 2.2.4 as if there was something freezing display updates when the screen was off on 2.1.1 which is no longer present in 2.2.4. It may have nothing to do with the reset problem : there should be no problem to update the HMI while the screen is off but I will take a look at 2.1.1 code to compare.

[michel_ng]

@Herrie

could you please explain that proximity.patch exactly do and which problems it should solve?