[android-developers] Digest for android-developers@googlegroups.com - 10 Messages in 7 Topics

Comments: (0)

Group: http://groups.google.com/group/android-developers/topics

    sting <raymond.madigan@gmail.com> Oct 31 10:59PM -0700  

    I am trying to write a Bluetooth android application. I have used many
    ideas from the samples and the bluetooth page in the android developers
    site.
     
    So, I put up a dialog that has the available bluetooth devices available,
    there is only one, and when I pick it the dialog goes to a method to manage
    the results of the dialog.
     
    What I want to do is spawn a thread from this method that sits on a call
    that blocks. I have the Thread and everything seems good, except the
    dialog won't go away until the thread has been cancelled. But I can't
    cancel it because I am stuck in a blocking dialog.
     
    I have tried to create a Broadcast receiver to send myself a message,
    hoping the dialog goes away before I get the message, but that doesn't work
    either, the dialog still blocks until I remove it with a new instance that
    doesn't fork the thread.
     
    The question is, is there a good way to delay the thread running until the
    dialog is down, whenever that is? Or is what I am doing supposed to work
    and I have something else wrong.
     
    //The dialog basically unchanged from the sample

    public Dialog onCreateDialog(Bundle savedInstanceState) {
    String[] deviceNames = getArguments().getStringArray("names");
    int position = getArguments().getInt("position", -1);
    if (position == -1) position = 0;
    return new AlertDialog.Builder(getActivity())
    .setTitle(R.string.select_device)
    .setPositiveButton(R.string.ok,
    new DialogInterface.OnClickListener() {
    public void onClick(DialogInterface dialog, int
    which) {
    ((BrewActivity)
    getActivity()).connectChannel();
    }
    })
    .setSingleChoiceItems(deviceNames, position,
    new DialogInterface.OnClickListener() {
    public void onClick(DialogInterface dialog, int
    which) {
    ((BrewActivity)
    getActivity()).setDevice(which);
    }
    }
    )
    .create();
    }
    }
     
    //The connect channel method where I send myself the message
     
    private void connectChannel() {
    Log.w(TAG, "Connect Channel.");
    mConnectIndicator.setText(mRes.getString(R.string.connected));
    mDataIndicator.setImageLevel(1);
    Intent intent = new Intent();
    intent.setAction("madigan.android.action.CONNECT");
    sendBroadcast(intent);
    }
     
    //The broadcast receiver that gets the message I send myself.
     
    private final BroadcastReceiver mConnector = new BroadcastReceiver() {
    @Override
    public void onReceive(Context context, Intent intent) {
    Log.w(TAG, "Connect Receiver.");
    final String action = intent.getAction();
    if (action.equals("madigan.android.action.CONNECT" ) ){
    connect();
    }
    }
    };
     
    // The method called with the success of the broadcast
     
    private void connect() {
    Log.w(TAG, "Connect.");
    // Starts connection Thread.
    AcceptThread aThread = new AcceptThread();
    aThread.run();
    BluetoothServerSocket socket = connectDevice(mBluetoothAdapter,
    mDevice);
    try {
    socket.accept();
    }
    catch(IOException e){
    Log.w(TAG, "Accept with Exception.");
    }
    Log.w(TAG, "Accept with No Exception.");
    }
     
    // and finally the thread
     
    private class AcceptThread extends Thread {
    private final BluetoothServerSocket mmServerSocket;

    public AcceptThread() {
    // Use a temporary object that is later assigned to
    mmServerSocket,
    // because mmServerSocket is final
    BluetoothServerSocket tmp = null;
    try {
    // MY_UUID is the app's UUID string, also used by the
    client code
    tmp =
    mBluetoothAdapter.listenUsingInsecureRfcommWithServiceRecord(mDevice.getName(),
    UUID.randomUUID());
    } catch (IOException e) { }
    mmServerSocket = tmp;
    }

    public void run() {
    BluetoothSocket socket = null;
    // Keep listening until exception occurs or a socket is returned
    while (true) {
    try {
    socket = mmServerSocket.accept();
    } catch (IOException e) {
    break;
    }
    // If a connection was accepted
    if (socket != null) {
    // Do work to manage the connection (in a separate
    thread)
    manageConnectedSocket(socket);
    try {
    mmServerSocket.close();
    }
    catch (IOException e){
    break;
    }
    break;
    }
    }
    }

    /** Will cancel the listening socket, and cause the thread to
    finish */
    public void cancel() {
    try {
    mmServerSocket.close();
    } catch (IOException e) { }
    }
    }

     

    Dan <dan.schmitt@gmail.com> Oct 31 02:56PM -0700  

    So, I upgraded my SDK today and tried to rebuild all my stuff (command
    line from scons file.) First 2 projects went fine, the 3rd is now failing
    with:
     
    [dex] Converting compiled files and external libraries into
    /....snip.../bin/classes.dex...
    [dx]
    [dx] UNEXPECTED TOP-LEVEL EXCEPTION:
    [dx] java.nio.BufferOverflowException
    [dx] at java.nio.Buffer.nextPutIndex(Buffer.java:499)
    [dx] at java.nio.HeapByteBuffer.putShort(HeapByteBuffer.java:296)
    [dx] at com.android.dex.Dex$Section.writeShort(Dex.java:818)
    [dx] at com.android.dex.Dex$Section.writeTypeList(Dex.java:870)
    [dx] at com.android.dx.merge.DexMerger$3.write(DexMerger.java:437)
    [dx] at com.android.dx.merge.DexMerger$3.write(DexMerger.java:423)
    [dx] at
    com.android.dx.merge.DexMerger$IdMerger.mergeUnsorted(DexMerger.java:317)
    [dx] at com.android.dx.merge.DexMerger.mergeTypeLists(DexMerger.java:423)
    [dx] at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:163)
    [dx] at com.android.dx.merge.DexMerger.merge(DexMerger.java:187)
    [dx] at
    com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:439)
    [dx] at com.android.dx.command.dexer.Main.runMonoDex(Main.java:287)
    [dx] at com.android.dx.command.dexer.Main.run(Main.java:230)
    [dx] at com.android.dx.command.dexer.Main.main(Main.java:199)
    [dx] at com.android.dx.command.Main.main(Main.java:103)
     
    Anybody pointers on how to get it to not fail this way (or more info that
    would help
    folks fix it?)
     
    Dan Schmitt

     

    Bradley O'Hearne <brado@bighillsoftware.com> Oct 31 07:26PM -0700  

    > [dx] at com.android.dx.command.Main.main(Main.java:103)
     
    > Anybody pointers on how to get it to not fail this way (or more info that would help
    > folks fix it?)
     
    Dan,
     
    I literally just worked through this error — mine was caused by adding the Facebook SDK as a module dependency to a project in the latest version of Android Studio. In my case, I saw a stack trace very similar to yours, but the actual exception was further upstream, and the error was due to the fact that the Facebook SDK uses a different version of the android support jar than my primary project. I had to go into the Facebook SDK's build.gradle file and comment out its jar and use the other one that my primary project was using, as follows:
     
    dependencies {
    // compile files('libs/android-support-v4.jar')
    compile 'com.android.support:support-v4:18.0.0'
    }
     
    After fixing that, all problems disappeared. I don't know if this is going to help you even a little, but I've spent the day stumbling around in the spooky Halloween land of undocumented tools and APIs, and thought I'd at least try to lend a hand. Good luck, and let me know if you are able to make it through.
     
    Cheers,
     
    Brad

     

    Nathan <nathan.d.mellor@gmail.com> Oct 31 03:01PM -0700  

    On Monday, October 28, 2013 4:04:19 PM UTC-7, Nathan wrote:
     
    > Nothing in my code ever renames a .db file to a .back file.
     
    > Is there some system process that would do that?
     
    > Could it have anything to do with copying files from one Android device to
    another?

     

    Patrick <patrick.godeau@gmail.com> Oct 31 01:40PM -0700  

    I often get this kind of spam, I reported this to Google support, but I
    don't know what they did with it (if they did something).

     

    JavaSrvcs <jvsrvcs@gmail.com> Oct 30 11:54PM -0700  

    I would like to know or explore ways to simulate tens of thousands of real
    world devices hitting my server.
     
    I am interesting in things like sending GPS data per device (within a
    region) such that device info is coming from geographic parameters I can
    program.
    I am also interested in simulating various battery level strength, wifi
    signal strength and other parameters that can be gathered from an android
    device.
     
    If there is a way to create a very low foot print virtualized android
    device that would send this info, please let me know, I would need the
    ability to run a simulation of a thousand devices per 8 core/64GB box if
    possible, simulating various virtualized devices of a good mix of android
    releases.

     

    Mukesh Srivastav <mukichamps@gmail.com> Oct 31 12:50PM +0530  

    you could easily go with the load and stress test and it need not be on
    only from Mobile devices... :(
     
    any ways, to test the client and server, you could go with the following
    link.
     
    http://jmeter.apache.org/usermanual/jmeter_distributed_testing_step_by_step.pdf
     
     
     
    --
    Warm Regards,
    *Mukesh Kumar*,
    Android Consultant/Freelancer,
    India,Hyderabad.

     

    Kristopher Micinski <krismicinski@gmail.com> Oct 31 11:07AM -0400  

    Mukesh is right on this one.
     
    Stress testing your server won't be any different than testing any
    other sort of server. Just create a dummy that simulates what an
    Android device would do and throw thousands of requests at it.
     
    Ideally, if you're using some sort of service (e.g., Rails) you should
    Google how to test that type of thing and then do whatever it says.
     
    Kris
     
     

     

    Tom <thomas.bruyelle@gmail.com> Oct 31 03:29AM -0700  

    Hi folks,
     
    I noticed that TextUtils and DateUtils are stubbed in the SDK (all theirs
    methods return a RuntimeException with the label "Stub!"). So they can't be
    part of any junit execution which actually makes me really sad...
     
    Is there a good reason for that ??

     

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Digest for android-developers@googlegroups.com - 21 Messages in 10 Topics

Comments: (0)

Group: http://groups.google.com/group/android-developers/topics

    sting <raymond.madigan@gmail.com> Oct 30 10:15PM -0700  

    I am building a device that basically has a UART so I can send and receive
    bytes. I want to be able to control the device, send configuration
    information to the device, using an android phone. Is there a way for such
    a simple device to establish a connection with the BlueToothServer/socket.
    All I think I need is the connection, then its a matter of transmitting
    messages that are just strings.
     
    Any help would be appreciated.

     

    andrew_esh <andrew.c.esh@gmail.com> Oct 30 08:54PM -0700  

    Many of the radio references you are seeing may be related to the Mobile
    Data connection, and the Phone. These use a radio to connect to the cell
    network, and have nothing to do with FM Music Radio.

     

    Michael Palmer <meicpalmer@gmail.com> Oct 30 02:03PM -0700  

    Lately, I've noticed that there are many live wallpapers, by different
    developers, which all contain the following text as part of the description:
     
     
    To use: Home -> Menu -> Wallpapers -> Live Wallpapers
    > device is not supported.
     
    > Note: If your wallpaper resets to default after reboot, you will need put
    > the app on phone instead of SD card.
     
    What's particularly odd is that they all claim to be tested on the same set
    of devices. Furthermore, most of these live wallpapers seem to be static
    images with some objects (most commonly, bubbles) moving in front of them.
    Occasionally, they will have some kind of wave-distortion effect in the
    middle of the screen.
     
    What is going on here? Are these apps being auto-generated by a program?
    Are they attempting to imitate one developer? Are they all made by the
    same developer under multiple aliases?

     

    Palmer Eldritch <the.ubik@gmail.com> Oct 30 03:48AM -0700  

    The preferences are apparently *cleared *when one tries to load them when
    there is a null key which is bad ! Reproducer :
     
    public class XmlExceptionTest extends AndroidTestCase {
    /** Run it twice - on the second run the exception is thrown */
    public void testXmlException() {
    Context ctx = getContext();
    SharedPreferences prefs = PreferenceManager
    .getDefaultSharedPreferences(ctx); // exception thrown here
    (line 18)
    // and apparently it clears the prefs as the condition below is
    false
    if (prefs.contains("run_once")) { // false
    Log.w("XmlExceptionTest",
    "contains null key :" + prefs.contains(null));
    }
    Editor e = prefs.edit();
    e.putBoolean("run_once", true).commit();
    e.putString(null, "I put a sting with null key").commit();
    assertTrue("Contains null", prefs.contains(null));
    PreferenceManager.getDefaultSharedPreferences(ctx); // exception
    // NOT thrown here - why ? - apparently there is a static
    factory
    // returning the instance it already constructed
    // e.clear().commit(); // this eliminates the exception
    }
    }

    exception :
     
    W/ApplicationContext(): getSharedPreferences
    W/ApplicationContext(): org.xmlpull.v1.XmlPullParserException: Map
    value without name attribute: string
    W/ApplicationContext(): at
    com.android.internal.util.XmlUtils.readThisMapXml(XmlUtils.java:521)
    W/ApplicationContext(): at
    com.android.internal.util.XmlUtils.readThisValueXml(XmlUtils.java:733)
    W/ApplicationContext(): at
    com.android.internal.util.XmlUtils.readValueXml(XmlUtils.java:667)
    W/ApplicationContext(): at
    com.android.internal.util.XmlUtils.readMapXml(XmlUtils.java:470)
    W/ApplicationContext(): at
    android.app.ContextImpl.getSharedPreferences(ContextImpl.java:361)
    W/ApplicationContext(): at
    android.preference.PreferenceManager.getDefaultSharedPreferences(PreferenceManager.java:348)
    W/ApplicationContext(): at
    gr.uoa.di.android.helpers.test.XmlExceptionTest.testXmlException(XmlExceptionTest.java:18)
    W/ApplicationContext(): at
    java.lang.reflect.Method.invokeNative(Native Method)
    W/ApplicationContext(): at
    java.lang.reflect.Method.invoke(Method.java:521)
    W/ApplicationContext(): at
    junit.framework.TestCase.runTest(TestCase.java:154)
    W/ApplicationContext(): at
    junit.framework.TestCase.runBare(TestCase.java:127)
    W/ApplicationContext(): at
    junit.framework.TestResult$1.protect(TestResult.java:106)
    W/ApplicationContext(): at
    junit.framework.TestResult.runProtected(TestResult.java:124)
    W/ApplicationContext(): at
    junit.framework.TestResult.run(TestResult.java:109)
    W/ApplicationContext(): at
    junit.framework.TestCase.run(TestCase.java:118)
    W/ApplicationContext(): at
    android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169)
    W/ApplicationContext(): at
    android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154)
    W/ApplicationContext(): at
    android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:520)
    W/ApplicationContext(): at
    android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1447)
     
    Posted in SO here<http://stackoverflow.com/questions/19610569/android-sharedpreferences-null-keys-values-and-sets-corner-cases>and in the relevant thread
    here <http://stackoverflow.com/a/19621603/281545> - but still no answers
     
    Any ideas ?

     

    Nobu Games <dev.nobu.games@gmail.com> Oct 30 10:44AM -0700  

    I quickly peeked into the source code and well, this is the way how it is
    programmed. When an exception occurs while the preferences data file gets
    read, SharedPreferences sets internally an empty map so you start from
    scratch. I even dug a bit deeper. The XML serializer just ignores NULL keys
    and creates XML output that cannot be properly read anymore through the map
    deserialization method which seems to expect an existing key value.
     
    As for why it has been programmed like that... I think the reasoning may be
    that preferences are not deemed to be of so much importance that it should
    make the app crash in case of failure. This error state is silently
    discarded and you start over with the defaults. I think that's a reasonable
    approach since any app should be able to start over with empty preferences.
     
    In this particular case you may have discovered a tiny bug you may want to
    report. But to be honest, using null keys is a pretty unusual thing to do.
     
    On Wednesday, October 30, 2013 5:48:12 AM UTC-5, Palmer Eldritch wrote:

     

    Kristopher Micinski <krismicinski@gmail.com> Oct 30 02:23PM -0400  

    Your question seems more to deal with intention rather than
    complaining. I believe that Nobu's response was merely interpreting
    the implementation and trying to interpret it, so there's no use in
    trying to complain at him for providing a guess at something he didn't
    even write.
     
    kris
     
     

     

    Palmer Eldritch <the.ubik@gmail.com> Oct 30 12:39PM -0700  

    I did not mean to complain at Nobu - sorry if I sounded harsh :)
     
    I just wanted to point out that my question was not so much *what *happens
    but *why *- and also raise awareness to this buggy and unintuitive
    behavior- or maybe have someone explain why this is so.
     
    Should we post a bug report ?
     
    On Wednesday, October 30, 2013 8:23:46 PM UTC+2, Kristopher Micinski wrote:

     

    Kristopher Micinski <krismicinski@gmail.com> Oct 30 04:27PM -0400  

    I would honestly suspect that it's "meant" to be this way, and perhaps
    the documentation is buggy. If you want, posting a bug report might
    get some action by Android devs, if none of them respond here.
     
    Kris
     
     

     

    Palmer Eldritch <the.ubik@gmail.com> Oct 30 01:39PM -0700  

    Why could one permit null keys - actually *one *null key - to have
    afterwards* all the preferences cleared due to an exception *? Given that
    the prefs are a persistence mechanism.
    No it is at least an oversight - except if I am missing something
    NB - I am talking about the default shared preferences - but all shared
    preferences are the same behind the scenes
     
    On Wednesday, October 30, 2013 10:27:03 PM UTC+2, Kristopher Micinski wrote:

     

    Kristopher Micinski <krismicinski@gmail.com> Oct 30 04:45PM -0400  

    I agree it's an oversight, and that at the very least there should be
    something in the documentation to give the semantics in this case.
     
    kris
     
     

     

    Kostya Vasilyev <kmansoft@gmail.com> Oct 31 12:52AM +0400  

    "Starting over" with shared prefs content when something goes wrong --
    looks to me like a feature, and a useful one: sometimes storage goes
    bad, files get corrupted, etc.
     
    Being able to put null keys into shared prefs, and it triggering the
    corruption handing code path later -- looks like a bug to me.
     
    Just my two somethings...
     
    -- K
     

     

    mmj <may.maria10@gmail.com> Oct 30 06:46AM -0700  

    Hi,
     
    I am developing an android app for Google TV Api level 13. I have a
    videoview which plays .mp4 video from raw folder.
    Sometimes the video playes properly.
    But sometimes i can observe lot of frame drops.
    And logcat message shows *:AwesomePlayer(789): we're much too late (0.50
    secs), video skipping ahead*
     
    Here is my code:
     
    VideoView mVideoView = (VideoView) findViewById(R.id.videoView1);
    String path = "android.resource://" + getPackageName() + "/" + R.raw.test;
    mVideoView.setVideoURI(Uri.parse(path));
    mVideoView.start();
     
    MediaController mc = new MediaController(this, true);
    mc.setMediaPlayer(mVideoView);
    mc.setAnchorView(mVideoView);

    mVideoView.setMediaController(mc);
    mVideoView.requestFocus();
     
    I am testing with google tv emulator.
     
    How can i fix this issue?

     

    Jose_GD <jose.gonzalez.d@gmail.com> Oct 30 04:46AM -0700  

    Are you using the same images in all categories?
    For example:
     
    Smartphones: image1.png / image2.png
    Tablet 7": image1.png / image2.png
    Tablet 10": image1.png / image2.png
     
     
     
    El martes, 29 de octubre de 2013 11:45:37 UTC-3, firebreather escribió:

     

    "s.rawat" <imsaurabhrawat@gmail.com> Oct 30 04:52PM +0530  

    Hi,
    I am having a input_event var[arraySize] in the Android HAL.How can I see
    the dump of this using DDMS.Is there any way for this.
     
    Thanks in Advance!
     
    Rgds,
    Rp

     

    Mukesh Srivastav <mukichamps@gmail.com> Oct 30 02:07PM +0530  

    As far as SIP application, I have a good experience in using CSIPSimple
    which is universal accepted and it has all the respective libraries(.so)
    file where you can enable as the default option.
     
     
     
    --
    Warm Regards,
    *Mukesh Kumar*,
    Android Consultant/Freelancer,
    India,Hyderabad.

     

    Juned Khan <jkhan6722@gmail.com> Oct 30 02:36AM -0700  

    I have a broad idea about CSIPsimple application, but this for them who
    want to add g729 in codec in SipDroid
     

     

    Dilip Kumar Chaudhary <androiddilip78@gmail.com> Oct 30 12:32PM +0530  

    Hi Developers,
    I'm getting this abnormal errors in XOLO/T1000 phone only.This is app is
    working fine on other devices.Actually when we click on the Tab for start
    another activity it throws this error.Please suggest me how to solve this
    error.
    *Logcat:
    *W/ActivityManager( 344): Bad activity token:
    android.os.BinderProxy@42aed960
    W/ActivityManager( 344): java.lang.ClassCastException:
    android.os.BinderProxy cannot be cast to
    com.android.server.am.ActivityRecord$Token
    W/ActivityManager( 344): at
    com.android.server.am.ActivityRecord.forToken(ActivityRecord.java:307)
    W/ActivityManager( 344): at
    com.android.server.am.ActivityStack.isInStackLocked(ActivityStack.java:484)
    W/ActivityManager( 344): at
    com.android.server.am.ActivityManagerService.overridePendingTransition(ActivityManagerService.java:2797)
    W/ActivityManager( 344): at
    android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:1338)
    W/ActivityManager( 344): at
    com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:1611)
    W/ActivityManager( 344): at
    android.os.Binder.execTransact(Binder.java:367)
    W/ActivityManager( 344): at dalvik.system.NativeStart.run(Native
    Method)
    D/PullToRefresh(29800): onSizeChanged. W: 720, H: 828
    D/PullToRefresh(29800): Setting Padding. L: 0, T: -496, R: 0, B: -496
    D/PullToRefresh(29800): First Visible: 0. Visible Count: 0. Total Items:0
    D/PullToRefresh(29800): onSizeChanged. W: 720, H: 730
    D/PullToRefresh(29800): Setting Padding. L: 0, T: -438, R: 0, B: -438
    D/PullToRefresh(29800): First Visible: 0. Visible Count: 0. Total Items:0
    F/libc (29800): Fatal signal 11 (SIGSEGV) at 0x00000008 (code=1), thread
    29800 (.zenga.zengatvd)
    I/DEBUG ( 122): *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    *** ***
    I/DEBUG ( 122): Build fingerprint:
    'XOLO/T1000/us9230e1:4.1.1/JRO03C/XOLO_Play_S018_11102013:user/release-keys'
    I/DEBUG ( 122): pid: 29800, tid: 29800, name: .zenga.zengatvd >>>
    com.zenga.zengatvd <<<
    I/DEBUG ( 122): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr
    00000008
    I/DEBUG ( 122): r0 5bfde908 r1 00000008 r2 00000000 r3 00000001
    I/DEBUG ( 122): r4 00000010 r5 00000008 r6 5bfde908 r7 00000004
    I/DEBUG ( 122): r8 00000008 r9 00000008 sl 59f706f4 fp 5bce95a0
    I/DEBUG ( 122): ip 00000010 sp bee98e60 lr 5bc612bc pc 5bc23054
    cpsr 20000010
    I/DEBUG ( 122): d0 00000137442a6000 d1 439bc000439b8000
    I/DEBUG ( 122): d2 43cb8000442a4000 d3 000002a944124000
    I/DEBUG ( 122): d4 0000024900000197 d5 43cb800000000249
    I/DEBUG ( 122): d6 442a400000000197 d7 44a000003f800000
    I/DEBUG ( 122): d8 4000000040000000 d9 44340000437f0000
    I/DEBUG ( 122): d10 0000000044764000 d11 0000000000000000
    I/DEBUG ( 122): d12 0000000000000000 d13 0000000000000000
    I/DEBUG ( 122): d14 0000000000000000 d15 0000000000000000
    I/DEBUG ( 122): d16 4085480000000000 d17 7e37e43c8800759c
    I/DEBUG ( 122): d18 0000000000000000 d19 0000000000000000
    I/DEBUG ( 122): d20 0000000000000000 d21 0000000000000000
    I/DEBUG ( 122): d22 0000000000000000 d23 0000000000000000
    I/DEBUG ( 122): d24 3fc0e5604f000000 d25 4000000006800000
    I/DEBUG ( 122): d26 0000000000000000 d27 0000000000000000
    I/DEBUG ( 122): d28 4060800000000000 d29 0000000000000000
    I/DEBUG ( 122): d30 c000000008000000 d31 0000000000000000
    I/DEBUG ( 122): scr 28000013
    I/DEBUG ( 122):
    I/DEBUG ( 122): backtrace:
    I/DEBUG ( 122): #00 pc 00009054
    /system/lib/egl/libGLESv2_tegra_impl.so
    I/DEBUG ( 122): #01 pc 000472b8
    /system/lib/egl/libGLESv2_tegra_impl.so
    I/DEBUG ( 122):
    I/DEBUG ( 122): stack:
    I/DEBUG ( 122): bee98e20 59f6a3dc
    I/DEBUG ( 122): bee98e24 00000610
    I/DEBUG ( 122): bee98e28 00000048
    I/DEBUG ( 122): bee98e2c 59f37a11
    /system/lib/libardrv_dynamic.so
    I/DEBUG ( 122): bee98e30 00000000
    I/DEBUG ( 122): bee98e34 59f6a3dc
    I/DEBUG ( 122): bee98e38 59f6d7d0
    I/DEBUG ( 122): bee98e3c 59f6b5fc
    I/DEBUG ( 122): bee98e40 59f6b548
    I/DEBUG ( 122): bee98e44 59f05891
    /system/lib/libnvrm_graphics.so (NvRmStreamBegin+80)
    I/DEBUG ( 122): bee98e48 00000000
    I/DEBUG ( 122): bee98e4c 59f6a3dc
    I/DEBUG ( 122): bee98e50 59f6d888
    I/DEBUG ( 122): bee98e54 59f6b5fc
    I/DEBUG ( 122): bee98e58 df0027ad
    I/DEBUG ( 122): bee98e5c 00000000
    I/DEBUG ( 122): #00 bee98e60 00000008
    I/DEBUG ( 122): ........ ........
    I/DEBUG ( 122): #01 bee98e60 00000008
    I/DEBUG ( 122): bee98e64 00000004
    I/DEBUG ( 122): bee98e68 0002c908
    I/DEBUG ( 122): bee98e6c 00000000
    I/DEBUG ( 122): bee98e70 00000002
    I/DEBUG ( 122): bee98e74 5bc612bc
    /system/lib/egl/libGLESv2_tegra_impl.so
    I/DEBUG ( 122): bee98e78 00000004
    I/DEBUG ( 122): bee98e7c 59f3b5c5
    /system/lib/libardrv_dynamic.so (NvArdSetVertexAttribute+110)
    I/DEBUG ( 122): bee98e80 59f6a3d8
    I/DEBUG ( 122): bee98e84 00000001
    I/DEBUG ( 122): bee98e88 c1dfb120
    I/DEBUG ( 122): bee98e8c 5bce95a8
    I/DEBUG ( 122): bee98e90 59f703b8
    I/DEBUG ( 122): bee98e94 00000010
    I/DEBUG ( 122): bee98e98 00000008
    I/DEBUG ( 122): bee98e9c 5bc61484
    /system/lib/egl/libGLESv2_tegra_impl.so
    I/DEBUG ( 122):
    I/DEBUG ( 122): memory near r0:
    I/DEBUG ( 122): 5bfde8e8 ffffffff ffffffff ffffffff ffffffff
    ................
    I/DEBUG ( 122): 5bfde8f8 ffffffff ffffffff ffffffff ffffffff
    ................
    I/DEBUG ( 122): 5bfde908 ffffffff ffffffff ffffffff ffffffff
    ................
    I/DEBUG ( 122): 5bfde918 ffffffff ffffffff ffffffff ffffffff
    ................
    I/DEBUG ( 122): 5bfde928 ffffffff ffffffff ffffffff ffffffff
    ................
    I/DEBUG ( 122):
    I/DEBUG ( 122): memory near r6:
    I/DEBUG ( 122): 5bfde8e8 ffffffff ffffffff ffffffff ffffffff
    ................
    I/DEBUG ( 122): 5bfde8f8 ffffffff ffffffff ffffffff ffffffff
    ................
    I/DEBUG ( 122): 5bfde908 ffffffff ffffffff ffffffff ffffffff
    ................
    I/DEBUG ( 122): 5bfde918 ffffffff ffffffff ffffffff ffffffff
    ................
    I/DEBUG ( 122): 5bfde928 ffffffff ffffffff ffffffff ffffffff
    ................
    I/DEBUG ( 122):
    I/DEBUG ( 122): memory near sl:
    I/DEBUG ( 122): 59f706d4 5c19dc10 00000000 00000010 00000206
    ...\............
    I/DEBUG ( 122): 59f706e4 00000000 00000000 00000000 3f800000
    ...............?
    I/DEBUG ( 122): 59f706f4 00000000 00000008 00000010 00000206
    ................
    I/DEBUG ( 122): 59f70704 00000000 00000000 00000000 3f800000
    ...............?
    I/DEBUG ( 122): 59f70714 00000000 00000000 00000000 00000406
    ................
    I/DEBUG ( 122):
    I/DEBUG ( 122): memory near fp:
    I/DEBUG ( 122): 5bce9580 00000002 00000003 00000000 00000001
    ................
    I/DEBUG ( 122): 5bce9590 00000000 00000001 00dc0001 00ef0002
    ................
    I/DEBUG ( 122): 5bce95a0 00000000 00008b52 00000101 00008b50
    ....R.......P...
    I/DEBUG ( 122): 5bce95b0 0000ffff 00008b52 00000000 0000004b
    ....R.......K...
    I/DEBUG ( 122): 5bce95c0 00000001 00000194 00000047 00000013
    ........G.......
    I/DEBUG ( 122):
    I/DEBUG ( 122): memory near sp:
    I/DEBUG ( 122): bee98e40 59f6b548 59f05891 00000000 59f6a3dc
    H..Y.X.Y.......Y
    I/DEBUG ( 122): bee98e50 59f6d888 59f6b5fc df0027ad 00000000
    ...Y...Y.'......
    I/DEBUG ( 122): bee98e60 00000008 00000004 0002c908 00000000
    ................
    I/DEBUG ( 122): bee98e70 00000002 5bc612bc 00000004 59f3b5c5
    .......[.......Y
    I/DEBUG ( 122): bee98e80 59f6a3d8 00000001 c1dfb120 5bce95a8
    ...Y.... ......[
    I/DEBUG ( 122):
    I/DEBUG ( 122): code around pc:
    I/DEBUG ( 122): 5bc23034 02032001 e3520000 1a00000b e3580008 .
    ....R.......X.
    I/DEBUG ( 122): 5bc23044 13a03000 02033001 e3530000 0a00000d
    .0...0....S.....
    I/DEBUG ( 122): 5bc23054 e8950003 e2577001 e0855004 e8860003
    .....pW..P......
    I/DEBUG ( 122): 5bc23064 e2866008 1afffff9 e8bd81f0 e8950007
    .`..............
    I/DEBUG ( 122): 5bc23074 e2577001 e0855004 e8860007 e286600c
    .pW..P.......`..
    I/DEBUG ( 122):
    I/DEBUG ( 122): code around lr:
    I/DEBUG ( 122): 5bc6129c e3520000 0a000006 e0820001 e1a01003
    ..R.............
    I/DEBUG ( 122): 5bc612ac e1a0200c e1a03004 e58d5000 ebff074f .
    ...0...P..O...
    I/DEBUG ( 122): 5bc612bc eaffffeb e5900000 e1a02004 e58dc000
    ......... ......
    I/DEBUG ( 122): 5bc612cc e98d0030 ebfefbac eaffffe5 e92d4ff0
    0............O-.
    I/DEBUG ( 122): 5bc612dc e24dd03c e5907548 e1a05000 e1a06001
    <.M.Hu...P...`..
    I/BootReceiver( 344): Copying /data/tombstones/tombstone_08 to DropBox
    (SYSTEM_TOMBSTONE)
    I/WindowState( 344): WIN DEATH: Window{4265b850
    com.zenga.zengatvd/com.zenga.zengatv.TabHome paused=false}
    I/ActivityManager( 344): Process com.zenga.zengatvd (pid 29800) has died.
    W/ActivityManager( 344): Scheduling restart of crashed service
    com.zenga.zengatvd/com.zengamedia.service.BackgroundService in 5000ms
    W/ActivityManager( 344): Force removing ActivityRecord{4267c7c0
    com.zenga.zengatvd/com.zenga.zengatv.TabHome}: app died, no saved state
    D/Zygote ( 124): Process 29800 terminated by signal (11)
    W/InputMethodManagerService( 344): Got RemoteException sending
    setActive(false) notification to pid 29800 uid 10105
    I/eFrame (17444): pkgname_before:com.zenga.zengatvd
    D/dalvikvm(30133): Late-enabling CheckJNI
    I/ActivityManager( 344): Start proc com.zenga.zengatvd for service
    com.zenga.zengatvd/com.zengamedia.service.BackgroundService: pid=30133
    uid=10105 gids={30
     
     
    --
    *Thanks & Regards*
    Dilip Kumar Chaudhary
    My Linkedin Profile<http://in.linkedin.com/pub/dilip-kumar-chaudhary/44/64/55b>
    My Development Blog <http://dilipdevelopment.blogspot.com/>

     

    Mukesh Srivastav <mukichamps@gmail.com> Oct 30 02:05PM +0530  

    you could one thing, Delete the bin and Gen directory and do a clean build
    again and try running.
     
     
    On Wed, Oct 30, 2013 at 12:32 PM, Dilip Kumar Chaudhary <
     
    --
    Warm Regards,
    *Mukesh Kumar*,
    Android Consultant/Freelancer,
    India,Hyderabad.

     

    jay <jayavelu.viswanathan@gmail.com> Oct 29 11:10PM -0700  

    Hi Team ,
     
    I needed help how to integrate js in android please explain this !!!!!
     
    On Monday, October 28, 2013 10:42:36 PM UTC+5:30, Laikis Reor wrote:

     

    jay <jayavelu.viswanathan@gmail.com> Oct 29 11:10PM -0700  

    Hi Team ,
     
    I needed help how to integrate js in android please explain this !!!!!
     
    On Monday, October 28, 2013 10:42:36 PM UTC+5:30, Laikis Reor wrote:

     

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Digest for android-developers@googlegroups.com - 22 Messages in 14 Topics

Comments: (0)

Group: http://groups.google.com/group/android-developers/topics

    Dusk Jockeys Android Apps <duskjockeys@gmail.com> Oct 29 09:44PM -0700  

    This entirely depends on what Home Screen Launcher you are using.
    On earlier phones, up to around the Samsung S2, the default installed Home
    Screen indeed provided such callbacks to the Live Wallpaper. Under those
    home screens, a standard static wallpaper would also scroll in response to
    swipes between pages.

    On more recent phones, the default home screens are treating the pages like
    a cylinder rather than a sheet, so as you scroll past the left-most page,
    it jumps to the right-most page. So you can keep swiping pages and end up
    when you started, on the original page. Under that paradigm, scrolling the
    wallpaper (static or otherwise) in response to swipes becomes more
    difficult, because there is an obvious jarring effect as you jump from the
    far left of the background image to the far right. The S2 did it like that,
    and it was noticeably weird. So modern phones homescreens have changed to
    simply not provide the onOffsetChanged callbacks at all to live wallpapers,
    and a static wallpaper doesnt respond to page swipes also. I guess that is
    what is happening on your device, I assume the a static background
    wallpaper isnt scrolling in response to swipes?

    If you try another Home Screen such as Go Launcher, you will see the
    callbacks working, as they havent implemented the cylinder page paradigm.

    But that doesnt solve your problem, because basically as it stands you
    can't guarantree that a particular user has a homescreen that supports
    onOffsetChanged, so you will need to find another UI method to change the
    wallpaper.

    How about shaking? That is independent of the home screen and the vast
    majority of phones these days have motion detection, but is not so useful
    for tablets.

     
    On Tuesday, October 29, 2013 7:31:37 AM UTC+8, Matt Schoen wrote:
     

     

    Michael Palmer <meicpalmer@gmail.com> Oct 29 09:53AM -0700  

    Six days ago, I received an email from someone offering to sell fake
    reviews. I have no interest in this, of course, but I'm having a hard time
    figuring out how to report it to Google. I tried emailing
    googleplay-developer-support, but I received an automated response telling
    me to use the form on their help site. And the form on their help site
    appears to be designed for problems specific to applications.

     

    Michael Banzon <michael@banzon.dk> Oct 29 06:50PM +0100  

    As much as it hurts to give this reply: Let it slide...
     
    I get around 20 of these messages each day from a handful senders. It seems
    they are 'rotating' company/e-mail/name and I seriously doubt it will have
    any impact reporting it as the service they provide is easily
    copied/continued under a different name/brand.
     
    As far as I can tell Google is working hard to limit the possible impact
    the use of these services could cause on the Google Play store (ratings,
    lists etc.) but that might be my own wishful thinking.

     

    Nathan <nathan.d.mellor@gmail.com> Oct 29 11:38AM -0700  

    On Tuesday, October 29, 2013 9:53:27 AM UTC-7, Michael Palmer wrote:
    > googleplay-developer-support, but I received an automated response telling
    > me to use the form on their help site. And the form on their help site
    > appears to be designed for problems specific to applications.
     
    Yeah, the really brazen ones are the ones saying "we've already done this
    for all of your competitors, so don't get left behind." I asked which
    competitors they'd done it for, so I could evaluate their work. No
    response.
     
    Nathan

     

    Michael Palmer <meicpalmer@gmail.com> Oct 29 03:00PM -0700  

    On Tuesday, October 29, 2013 1:50:00 PM UTC-4, mbanzon wrote:
     
    > As far as I can tell Google is working hard to limit the possible impact
    > the use of these services could cause on the Google Play store (ratings,
    > lists etc.) but that might be my own wishful thinking.
     
    I'd still like to submit it to someone as evidence of what they are doing.
    In particular, the email I received says:
     
    "That is the only way you can rank and get noticed, not only in Google's
    > Play store, but also in the Search Engines for your Keywords because each
    > rating and comment is like a backlink!"
     
     
    This may explain why some apps have so many reviews that are simply one
    word, like "Best" or "Nice" or "Cool."

     

    m2k <to.mikekober@gmail.com> Oct 29 01:02PM -0700  

    guys, easier than u think:
     
    if (biggerImageAtPosition == position) {
     
    imageView.setPadding(padding, padding, padding, padding);
     
    } else {
     
    imageView.setPadding(padding, paddingForSmallerImage,
    padding, paddingForSmallerImage);
     
    }
     
     
    so, just apply bigger padding for other images, and currently selected
    image, less padding )
     
    results in bigger image :)
     
     
    public class GalleryOnItemSelectedListener implementsOnItemSelectedListener {
     
     
    @Override
     
    public void onItemSelected(CustomAdapterView<?> parent, View view,
    int position, long id) {
     
    galleryAdapter.setShowImageBiggerAtPosition(position);
     
    galleryAdapter.notifyDataSetChanged();
     
    }
     
     
    @Override
     
    public void onNothingSelected(CustomAdapterView<?> parent) {
     

     
    }
     
     
    }
     
    Am Dienstag, 12. Oktober 2010 07:25:10 UTC+2 schrieb Babita:

     

    Abhilash Baddam <abhilash.androiddeveloper@gmail.com> Oct 29 03:26PM +0530  

     

    TreKing <trekingapp@gmail.com> Oct 29 01:19PM -0500  

    On Tue, Oct 29, 2013 at 4:56 AM, Abhilash Baddam <
     
    > Can we say all the mobiles api level (<=10) have menu key...???
     
    You can't say anything about any device. Manufactures have been known to
    develop devices that are bizarre in all manner of ways. This may be the
    case with 99% of devices, but there is always going to be that *One F*cking
    Device*™ that breaks all expectations.
     
    -------------------------------------------------------------------------------------------------
    TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
    transit tracking app for Android-powered devices

     

    Abhilash Baddam <abhilash.androiddeveloper@gmail.com> Oct 29 03:31PM +0530  

    Hi,
     
    I have referred the below blog,
    http://android-developers.blogspot.in/2012/01/say-goodbye-to-menu-button.html
     
    In my app I want to check the Menu key is present or not.
    For that I have used hasPermanentKey() function which is introduced in API
    level 14 but I cant use it GB.
     
    Can we assume if the api level(<=10) devices has Menu key...?
     
    Please Anybody guide me on this...

     

    Abhilash Baddam <abhilash.androiddeveloper@gmail.com> Oct 29 11:16PM +0530  

    HI,
     
    Is there any possibility to check whether the menu hard key is present or
    not in Gingerbread(2.3)... ?
     
     
    On Tue, Oct 29, 2013 at 3:31 PM, Abhilash Baddam <

     

    firebreather <michaelirvingbrown@gmail.com> Oct 29 05:54AM -0700  

    i'm attempting to draw pixel density and resolution independent controls to
    the screen for my game.

    if I use screenWidth in declaring the size, the control's size will vary
    with resolution. if I just use a certain number of pixels, the control size
    will vary with pixel density.

    assume i need canvas.getDensity(), as there is no action like

     
    canvas.drawCircle(cx,cy,60di,paint). //di: density independent pixel
     
    canvas.getDensity() is returning 0, however. I saw on a different post a
    suggestion of disabling the GPU to fix this. I don't want to disable the
    GPU on my user's phones' though, even if I knew how. how do I get around
    this?

     

    Piren <gpiren@gmail.com> Oct 29 08:03AM -0700  

    Don't use the Canvas' density, use the Display's.
     
    On Tuesday, October 29, 2013 2:54:28 PM UTC+2, firebreather wrote:

     

    firebreather <michaelirvingbrown@gmail.com> Oct 29 10:20AM -0700  

    I found the answer to this on stack overflow here: *getting the screen
    density programmatically in android?*<http://stackoverflow.com/questions/3166501/getting-the-screen-density-programmatically-in-android>
     
    Use getResources().getDisplayMetrics().density or
    context.getResources().getDisplayMetrics().density to get:
     
    0.75 - ldpi
     
    1.0 - mdpi
     
    1.5 - hdpi
     
    2.0 - xhdpi
     
    3.0 - xxhdpi
     
    4.0 - xxxhdp

     
    On Tuesday, October 29, 2013 7:54:28 AM UTC-5, firebreather wrote:
     

     

    firebreather <michaelirvingbrown@gmail.com> Oct 29 07:45AM -0700  

    I added 10" and 7" screenshots as required to tablet optimization, but now
    I have duplicate screen shots that all show on the market. the market first
    shows the two 10" tablet shots, then the two 7" tablet shots, then all the
    phone shots.

    my tablet screenshots are the same as the first 2 phone shots and the 7"
    and 10" tablet shots are the same. since the screenshot window on the
    market goes through all the shots there is a lot of duplication.

    I notice the other apps that optimized for tablets don't have this issue.
    their tablet screenshots don't appear at all for me, i'm assuming because
    i'm not accessing from a tablet.

    how can I keep my tablet screenshots from showing for those accessing from
    phone or laptop, thus avoiding duplication.

     

    Laikis Reor <beaworldchild@gmail.com> Oct 29 07:39AM -0700  

    Hmmm... It is working partially. If I set the target in the
    project.properties to be
    "target=android-17"
    I get the error
    Renderscript support mode requires compilation target API to be 18+.
     
    I should say... I'm rather surprised someone from Google hasn't replied
    here or on the Stackoverflow question here<http://stackoverflow.com/questions/18945058/can-not-run-renderscript-hellocompute-example-on-android-gb-2-3-5>.
    I know this looks like I just haven't updated the libraries or something
    but I guarantee you it's a bug in the Renderscript build tools. I
    recognize that perhaps not many people are having this problem, but just
    because only a few are doesn't mean it isn't important.
     
    The Support Library Features page (here<http://developer.android.com/tools/support-library/features.html#v8>)
    states that 'You should be aware that the steps for including these APIs in
    your application is very different from other support library APIs.' I
    assume this is referring to the build mechanism that allows the
    Renderscript support library to be referenced even though a reference to
    the library isn't explicitly added. Whatever this mechanism might be, it
    is not working in my project.
     
    My project was originally built in Eclipse, then I migrated to Android
    Studio, and then am now back in Eclipse to use the Renderscript support
    library. Perhaps that process has introduced a bug?
     
    Thanks,
    Reor
     
     
    On Monday, October 28, 2013 10:12:36 AM UTC-7, Laikis Reor wrote:

     

    nakvic <nakvic@googlemail.com> Oct 29 01:55AM -0700  

    Thanks Kostya,
     
    I'll give it a try.
     
    Victor
     
    On Monday, October 28, 2013 10:48:10 PM UTC+1, Kostya Vasilyev wrote:

     

    Amit Mangal <forum.amit.mangal@gmail.com> Oct 29 01:30PM +0530  

    Hi there,
     
    I am using ArrayList<HashMap<String,String>> to store my data .
     
    do i need to use call clear method of array list on on destroy method of
    activity or it will automatically clear when my activity is destroying.
     
    i want to avaoid memory leaks in my app.
     
    thanks

     

    TreKing <trekingapp@gmail.com> Oct 29 03:38AM -0500  


    > do i need to use call clear method of array list on on destroy method of
    > activity or it will automatically clear when my activity is destroying.
     
    If you don't have any external references to the array list or activity,
    then it should be cleared with the activity.
     
     
    > i want to avaoid memory leaks in my app.
     
    I would suggest you earn to use the tools at your disposal:
    http://android-developers.blogspot.com/2011/03/memory-analysis-for-android.html
     
    Posting here for every doubt does not seem productive :)
     
    -------------------------------------------------------------------------------------------------
    TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
    transit tracking app for Android-powered devices

     

    Andrew Mackenzie <andrew@mackenzie-serres.net> Oct 29 01:03AM -0700  

    I looked into FM receivers a little. Its not supported in Android itself.
     
    OEMs (e.g. Samsung) add specific hardware and an app that uses a native library of theirs (thats tied to specific radio controller chip).
     
    You can find a radio app project on the web, but it will only work with phones that have the exact chip that matches the native library it includes.

     

    Piren <gpiren@gmail.com> Oct 29 12:44AM -0700  

    Errr... don't know how i missed this - I was talking about targetSdk, not
    minSdk, :-|
     
     
    On Monday, October 28, 2013 6:09:24 PM UTC+2, Piren wrote:

     

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-developers] Digest for android-developers@googlegroups.com - 12 Messages in 7 Topics

Comments: (0)

Group: http://groups.google.com/group/android-developers/topics

    "judemwenda@gmail.com" <judemwenda@gmail.com> Oct 28 04:32PM -0700  

    Hi,
    I have been looking into the android source and surprised there is no FM
    receiver mechanism. Some documents do indicate there is the class
    android.hardware.radio but can not seem to find it. Any pointers on getting
    this or reasons of leaving it out?
     
    Regards

     

    Matt Schoen <mtschoen@gmail.com> Oct 28 04:31PM -0700  

    Hi there,
     
    I'm making a live wallpaper that I would like to change when the user
    swipes the screen. I have a TouchListener set up, but I have had trouble
    precisely matching the behavior of the home screen. In other words,
    sometimes when I swipe the screen, the home screen will change pages but my
    app wallpaper will not, and if I make it more "sensitive", it will flip
    sometimes when the home screen doesn't.
     
    The WallpaperService.Engine.onOffsetsChanged<http://developer.android.com/reference/android/service/wallpaper/WallpaperService.Engine.html#onOffsetsChanged(float,
    float, float, float, int, int)> method seems to be what I'm looking for,
    but I only see it called when the app starts and when you return home from
    an app. It is not called as I swipe or change home screen pages. This StackOverflow
    article<http://stackoverflow.com/questions/6637753/using-onoffsetschanged-to-get-home-screen-swipe-direction>leads me to believe that I should get callbacks on this function every time
    the home screen moves.
     
    Any ideas?

     

    Nathan <nathan.d.mellor@gmail.com> Oct 28 04:04PM -0700  

    Not that I have reproduced it here, but . ..
     
    Customer reports that some large db files were missing from storage and
    were replaced by a .back file of the same approximate size.
     
    Nothing in my code ever renames a .db file to a .back file.
     
    Is there some system process that would do that?
     
    Nathan

     

    firebreather <michaelirvingbrown@gmail.com> Oct 28 02:49PM -0700  

    I've never declared a target sdk, I figure that's safer.
    my android phone is version 10 so I can't increase my minimum or i'd be
    stuck with the increadibly slow emulator.
    it took hours to get a screenshot off it for the tablet google play image.
    it will be some time before I can afford a version 11+ phone or i'd just
    change my minimum to 11 so I wouldn't have to worry about it. testing on
    the emulator takes literally hours for each run so i'll never be able to
    compare different phones:minsdk:targetsdk:development skd permutations.
     
    On Monday, October 28, 2013 4:38:59 PM UTC-5, Kostya Vasilyev wrote:
     

     

    Kostya Vasilyev <kmansoft@gmail.com> Oct 29 02:01AM +0400  

    Re: "testing on the emulator takes literally hours for each run" --
     
    -- do you use the x86 emulator images?
     
    I do, and for me, it's faster than a Galaxy Note 2 (Linux, 64 bit,
    Intel CPU with kvm).
     
    http://developer.android.com/tools/devices/emulator.html#accel-vm
     
    -- K
     

     

    firebreather <michaelirvingbrown@gmail.com> Oct 28 03:03PM -0700  

    also, thanks for pointing out K that this doesn't actually mean I have to
    use minsdk 11 like I assumed. i'll try just targeting for sdk 11 instead of
    not declaring a target at all. if it still works on my android 2.6.35.7
    phone (version 10), i'll upload the target skd 11 declaration code.
     
    On Monday, October 28, 2013 4:38:59 PM UTC-5, Kostya Vasilyev wrote:
     

     

    firebreather <michaelirvingbrown@gmail.com> Oct 28 03:06PM -0700  

    well it won't work on my version 10 phone with a version 11 target (no
    compatible device error), so i'll have to leave it with no target declared.
     
    On Monday, October 28, 2013 4:38:59 PM UTC-5, Kostya Vasilyev wrote:
     

     

    firebreather <michaelirvingbrown@gmail.com> Oct 28 03:20PM -0700  

    it does appear to be working with now with version 11 targeted, so i'll
    upload that. it recommends version 14 targeted. any opinions on whether I
    should target 10 or 14? thanks for the responces. if you answer my
    identical question on stack overflow you'll get star and check attack
    overflow points from me as no one answered there,

     

     

    Kostya Vasilyev <kmansoft@gmail.com> Oct 29 02:12AM +0400  

    > well it won't work on my version 10 phone with a version 11 target (no
    > compatible device error), so i'll have to leave it with no target declared.
     
    It's possible to run a targetSdk >= 11 on an 2.* device. I do it every day :)
     
    A minSdk >= 11 would not run on a 2.* device.
     
    -- K
     
     

     

    heshoots67 Zuber <heshoots67@gmail.com> Oct 28 05:32PM -0400  

    I have the same problem.
     
     

     

    gjs <garyjamessilva@gmail.com> Oct 27 11:31PM -0700  

    Hi,
     
    Its not wrong it only reports being connected (to the LAN) not the internet.
     
    If you really want to check for an active internet connect, send a request
    & examine the response code to some website(s) you know are likely to be up
    & running, google.com perhaps.
     
    Regards
     
    On Monday, October 28, 2013 2:51:00 PM UTC+11, janvi wrote:

     

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.