WebOS Internals - User contributions [en]

Patch WebOS Bypassing Lock Screen

2011-12-26T01:33:06Z

Lingfish:

{{template:patch}}
== webOS 2.2 and newer ==

(I think this changed from 2.2 onwards?)

=== About ===

Since the 1.1 update (see [[#About_2|About]]), upon connecting an e-mail account to Exchange (EAS), if a policy enforcement exists on that server, it will be enforced on the webOS device as well.

=== Modification ===

The place to bypass the PIN in the codebase has changed quite a bit -- the patch is now done to <tt>com.palm.app.phone/phoneAppPinCode/source/PhonePinCard.js</tt>.

Conveniently, the webOS team left a nice, simple way to bypass it all around line 66:

<pre>
// DEFAULT: just handle known launch mode
} else {
//always unlock - for testing
//this.$.updatePinAppState.call({state: 'unlock'}); return;

this.handleLaunchLockMode();
}
</pre>

== webOS 2.1 and older ==

=== About ===
The 1.1 update allowed me to connect to Exchange (EAS) with a policy enforced. Of course, having my screen lock every single time I turn off the screen seems a little harsh. The policy asks for a 10-minute timeout, but the way it's implemented in WebOS, the screen locks whenever the screen turns off.

=== Modification ===

Below is a modification to automatically unlock the screen. This method seems to still work with the 1.3.5 update.

Edit <pre>/usr/palm/applications/com.palm.app.phone/app/controllers/pin-assistant.js</pre>

Immediately after " setup: function() { " (line 32 in 1.1, line 33 in 1.3.1 and 1.3.5, line number may vary in other versions)

add the line:
<pre>
this.unlock(); return;
</pre>

What you've done is edit the "setup" function to immediately call the unlock function and return (skipping anything else it would normally do).

Reboot, and your screen should automatically unlock as soon as you slide it open.

Should work like a charm!

Patch WebOS Bypassing Lock Screen

2011-12-26T01:32:22Z

Lingfish:

{{template:patch}}
== webOS 2.2 and newer ==

(I think this changed from 2.2 onwards?)

=== About ===

Since the 1.1 update (see [[#About_2|About]]), upon connecting an e-mail account to Exchange (EAS), if a policy enforcement exists on that server, it will be enforced on the webOS device as well.

=== Modification ===

The place to bypass the PIN in the codebase has changed quite a bit -- the patch is now done to <pre>com.palm.app.phone/phoneAppPinCode/source/PhonePinCard.js</pre>.

Conveniently, the webOS team left a nice, simple way to bypass it all around line 66:

<pre>
// DEFAULT: just handle known launch mode
} else {
//always unlock - for testing
//this.$.updatePinAppState.call({state: 'unlock'}); return;

this.handleLaunchLockMode();
}
</pre>

== webOS 2.1 and older ==

=== About ===
The 1.1 update allowed me to connect to Exchange (EAS) with a policy enforced. Of course, having my screen lock every single time I turn off the screen seems a little harsh. The policy asks for a 10-minute timeout, but the way it's implemented in WebOS, the screen locks whenever the screen turns off.

=== Modification ===

Below is a modification to automatically unlock the screen. This method seems to still work with the 1.3.5 update.

Edit <pre>/usr/palm/applications/com.palm.app.phone/app/controllers/pin-assistant.js</pre>

Immediately after " setup: function() { " (line 32 in 1.1, line 33 in 1.3.1 and 1.3.5, line number may vary in other versions)

add the line:
<pre>
this.unlock(); return;
</pre>

What you've done is edit the "setup" function to immediately call the unlock function and return (skipping anything else it would normally do).

Reboot, and your screen should automatically unlock as soon as you slide it open.

Should work like a charm!

Facebook timezone issue

2010-01-30T08:32:45Z

Lingfish:

This article has been moved to my blog.

http://geeklog.lucid.net.au/article.php?story=20091211084306281

Facebook timezone issue

2010-01-30T08:32:26Z

Lingfish: Replacing page with '== Introduction == This article has been moved to my blog. http://geeklog.lucid.net.au/article.php?story=20091211084306281'

== Introduction ==

This article has been moved to my blog.

http://geeklog.lucid.net.au/article.php?story=20091211084306281

Facebook timezone issue

2009-12-03T12:29:42Z

Lingfish:

== Introduction ==

As at version 1.3.1, Synergy and the Pre doesn't display Facebook event times right. This is, in my opinion, due to an error on both the part of Facebook, and Palm.

Mostly Facebook.

== The definition of Unix epoch time ==

Wikipedia rightly defines [http://en.wikipedia.org/wiki/Unix_time Unix epoch time] as:

:'''''Unix time''', or '''POSIX time''', is a system for describing points in time, defined as the number of seconds elapsed since midnight Proleptic Coordinated Universal Time (UTC) of January 1, 1970, not counting leap seconds.''

The key point here is that an epoch timestamp is in ''UTC time''.

== How Facebook does event times ==

As per http://wiki.developers.facebook.com/index.php/Events.get:

:''Note that the <tt>start_time</tt> and <tt>end_time</tt> returned are the times which were input by the event creator, converted to UTC after assuming that they were in Pacific time (Daylight Savings or Standard, depending on the date of the event), then converted into Unix epoch time.''

... Pacific time being GMT-8.

Why they assume this PST timezone, who knows... their backend seems to be smart enough to work out what timezone a typical browser session is in (I'm assuming via +/- offsets in <tt>Date:</tt> HTTP requests), so why not use that when an event is submitted, convert down to UTC at ''that'' time, and all is well!

Instead, they do it this way, and do some crazy magic when others view the event. This is where I say Palm is partly at fault -- because they haven't put this same magic in. They shouldn't ''have'' to though.

== What WebOS does ==

It would seem the Pre assumes that the <tt><start_time></tt> and <tt><end_time></tt> are in UTC via a Unix epoch timestamp -- very fair logic in my opinion, as this is what Facebook ''should'' be returning via its API. Instead, it seems to return <tt>local_time_of_event</tt>+8. Bizarre.

Firstly, some definitions:

;fb_stored_time
:The time as stored internally on Facebook servers
;epoch
:Function to convert to Unix epoch time
;UTC
:Function to convert to UTC time
;assumed_Pacific_time
:Facebook being stupid and assuming the local time the creator entered is in Los Angeles -- ''yes America, we all live there''. This time can be affected by daylight saving, too

So the math loosely looks like this:

:<pre>fb_stored_time = epoch(UTC(assumed_Pacific_time))</pre>

''(To be continued, not finished.)''

Facebook timezone issue

2009-12-03T11:00:00Z

Lingfish: New page: == Introduction == As at version 1.3.1, Synergy and the Pre doesn't display Facebook event times right. This is, in my opinion, due to an error on both the part of Facebook, and Palm. M...

== Introduction ==

As at version 1.3.1, Synergy and the Pre doesn't display Facebook event times right. This is, in my opinion, due to an error on both the part of Facebook, and Palm.

Mostly Facebook.

== How Facebook does event times ==

As per http://wiki.developers.facebook.com/index.php/Events.get:

:''Note that the <tt>start_time</tt> and <tt>end_time</tt> returned are the times which were input by the event creator, converted to UTC after assuming that they were in Pacific time (Daylight Savings or Standard, depending on the date of the event), then converted into Unix epoch time.''

... Pacific time being GMT-8.

Why they assume this PST timezone, who knows... their backend seems to be smart enough to work out what timezone a typical browser session is in (I'm assuming via +/- offsets in HTTP requests), so why not use that when an event is submitted, convert down to UTC at ''that'' time, and all is well!

Instead, they do it this way, and do some crazy magic when others view the event. This is where I say Palm is partly at fault -- because they haven't put this same magic in. They shouldn't ''have'' to though.

== What WebOS does ==

It would seem the Pre assumes that the <tt><start_time></tt> and <tt><end_time></tt> are in UTC via a Unix epoch timestamp -- very fair logic in my opinion, as this is what Facebook ''should'' be returning via its API. Instead, it seems to return <tt>local_time_of_event</tt>+8. Bizarre.

''(To be continued, not finished.)''

Portal:Research

2009-12-03T10:33:59Z

Lingfish: Added Facebook timezone issue

__notoc__
{{portal-header|
The Research Portal is for bleeding edge things being done with the device.

Title all pages: '''Research [description]''' or '''Reference [description]'''
}}
{{portal-two-columns
|column1=
===Research:===

* [[Applications Bundled on the Pre]]
* [[Application_Framework|Application Framework]]
* [[Blocking Updates]]
* [[New Bluetooth|BlueZ (Replacing Palm Bluetooth)]]
* [[Boot_Chain|Boot Chain]]
* [[Bootie]]
* [[ClassicFilesystem]]
* [[Decrypt SSL (trusted man-in-the-middle technique)|Decrypt SSL (trusted man-in-the-middle technique)]]
* [[FirstUse Application Functionality]]
* [[Fonts available on board the Pre]]
* [[Gstreamer]]
* [[Hidd]]
* [[Introspecting_Dbus|Introspecting Dbus]]
* [[Key Codes|Key Codes]]
* [[Pre Specific Hash Codes|Pre Specific Hash Codes]]
* [[Pictures from Self-Test|Pictures from Self-Test]]
* [[Restore Debug Log|Restore Debug Log]]
* [[Reverse_Engineering_WebOS_Doctor|Reverse Engineering WebOS Doctor]]
* [[Rooted Pre Issues|Rooted Pre Issues]]
* [[Research_Securing_Pre|Securing your Pre]]
* [[Running Processes|Running Processes]]
* [[Symlink Applications|Symlink Applications]]
* [[System Sounds|System Sounds]]
* [[TestApps|TestApps]]
* [[Facebook timezone issue|The annoying Facebook timezone issue]]
* [[Update Service Trace|Update Service Trace]]
* [[Tidbits|Tidbits]]
* [[VideoRecording]]
* [[WebOS Exploration - Various Information|WebOS Exploration - Various Information]]
* [[Research_Pre_GSM_Modem | Pre GSM modem device informations]]
* [[Research_Pre_GSM_Modem_Protocol | Pre GSM modem protocol informations]]
* [[Research_Pre_Audio | Audio routing and setup on the Pre]]
* [[Research_mpt | MSM modem passthru mode ]]
* [[Research_Pre_Boot_Process | Boot process]]

|column2=
===Reference===
* [[Packaging Standards|Packaging Standards]]
* [[webkit_transform|Webkit Transform]]- a powerful set of commands for manipulating elements.
}}