Try this:
adb shell sqlite3
/data/data/com.android.providers.settings/databases/settings.db
"INSERT INTO system (name,value) VALUES ('device_provisioned','1');"
I'm pretty sure that will do the trick, but I'm not 100% certain.
-Jeff
On Fri, Nov 14, 2008 at 11:53 AM, Jean-Baptiste Queru <[EMAIL PROTECTED]> wrote:
>
> I think that it's driven by one or more system properties. I don't
> know the details at all (I don't even know where to look in the source
> tree), so I hope that someone who knows this area better can chime in.
>
> JBQ
>
> On Fri, Nov 14, 2008 at 10:32 AM, Maxime Petazzoni
> <[EMAIL PROTECTED]> wrote:
>>
>> Is there a way to re-enable it by hand? Is it driven by a system
>> property or does it require additional code? If so, is there any plans
>> for this piece of code to be released as well?
>>
>> Thanks,
>> - Maxime
>>
>> On Nov 14, 10:22 am, Jean-Baptiste Queru <[EMAIL PROTECTED]> wrote:
>>> The open-source build currently lacks the code that enables it (on the
>>> G1, it's disabled until the device has run through the setup wizard,
>>> and the SDK has some replacement code that notifies the system that
>>> setup has completed, but the open-source build doesn't have either of
>>> those).
>>>
>>> JBQ
>>>
>>> On Fri, Nov 14, 2008 at 10:13 AM, Maxime Petazzoni
>>>
>>> <[EMAIL PROTECTED]> wrote:
>>>
>>> > Hi,
>>>
>>> > This may appear as a very dumb question, but does the Home button
>>> > works on your Android builds? In the packaged SDK, it has the expected
>>> > behavior (return to the Home screen), but in the open source build, it
>>> > does nothing -- and the keycode is correct and mapped to HOME is the
>>> > layouts.
>>>
>>> > Any ideas?
>>> > - Maxime
>> >
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
