[android-developers] Digest for android-developers@googlegroups.com - 1 update in 1 topic

Comments: (0)
andrew_esh <andrew.c.esh@gmail.com>: Aug 31 11:26AM -0700

I took a look at android::Region::createTJunctionFreeRegion here:
 
http://androidxref.com/4.4.4_r1/xref/frameworks/native/libs/ui/Region.cpp#185
 
I would look at the region being passed in to there. I wonder if some of
the arrows you're rendering are not valid regions by the time they reach
this function.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 1 update in 1 topic

Comments: (0)
Avetik Kazhoyan <kazhoyan@gmail.com>: Aug 30 04:33PM -0700

Hi!
 
I'm having this strange crash somewhere in native code. It happens much
more frequently when drawing very small Path objects (I'm drawing little
arrows). My app runs on Android 4+, so can't tell about previous OS
versions.
 
Couldn't find anything about it, so please have a look, at a backtrace:
#00 pc 00007354 /system/lib/libui.so
#01 pc 00007485 /system/lib/libui.so
(android::Region::createTJunctionFreeRegion(android::Region const&)+90)
#02 pc 0001bb13 /system/lib/libhwui.so
#03 pc 0001b2d1 /system/lib/libhwui.so
#04 pc 0001df1b /system/lib/libhwui.so
#05 pc 0001e079 /system/lib/libhwui.so
#06 pc 0006c299 /system/lib/libandroid_runtime.so
#07 pc 00020bcc /system/lib/libdvm.so (dvmPlatformInvoke+112)
#08 pc 00051927 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int
const*, JValue*, Method const*, Thread*)+398)
#09 pc 0002a060 /system/lib/libdvm.so
#10 pc 00031510 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#11 pc 0002eba8 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*,
JValue*)+184)
#12 pc 00064159 /system/lib/libdvm.so (dvmInvokeMethod(Object*, Method
const*, ArrayObject*, ArrayObject*, ClassObject*, bool)+392)
#13 pc 0006c18f /system/lib/libdvm.so
#14 pc 0002a060 /system/lib/libdvm.so
#15 pc 00031510 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#16 pc 0002eba8 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*,
JValue*)+184)
#17 pc 00063e75 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method
const*, Object*, bool, JValue*, std::__va_list)+336)
#18 pc 0004d457 /system/lib/libdvm.so
#19 pc 00051f0f /system/lib/libandroid_runtime.so
#20 pc 000534a3 /system/lib/libandroid_runtime.so
(android::AndroidRuntime::start(char const*, char const*)+354)
#21 pc 0000105b /system/bin/app_process
#22 pc 0000e4f3 /system/lib/libc.so (__libc_init+50)
#23 pc 00000d7c /system/bin/app_process
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

[android-developers] Digest for android-developers@googlegroups.com - 6 updates in 4 topics

Comments: (0)
Justin Anderson <magouyaware@gmail.com>: Aug 29 12:25AM -0600


> If i launch Inner main fragment 2 and i tap on anther next tab. when i
> came back to the Home Tab, the Inner main fragment 2 is not visible and
> it goes to the Home Tab automatically.
 
It sounds like you have a bug. To fix it, you should probably put some
breakpoints in your fragment's lifecycle callbacks and figure out why you
are getting unexpected bhavior.
 
Finally i fixed that issue using this code,
> android:label="@string/title_activity_operation" >
> </activity>
 
> This is a very common approach to "fixing" errors, but it is generally a
very very very bad idea. Unless you know what you are doing, you do not
want to be using the configChanges attribute.
 
But the problem is, i want to set deference layout with orientation change
> (portrait/landscape) for a inner fragment in the main fragment. But It's
> not working and orientation listener is not working in an inner fragment.
 
I'm not sure I fully understand what you are trying to say here... But
what I think you are saying is that you have two layout files (one in
res/layout and one in res/layout-land) but when you rotate the device the
layout doesn't get reloaded. Is that correct? If so, I refer to my comment
above... specifying configChanges for an activity is generally a very very
very bad thing to do, unless you really know what you are doing.
 
Your configChanges line above tells Android to ignore orientation events...
So naturally, when you rotate the device, it ignores the fact that the
orienation changed and the layout doesn't get reloaded. Remove that line,
and then your layouts should magically work on device rotation. But...
that will then bring back the other but you mentioned... so you will need
to start doing some debugging to figure out why you are getting unexpected
behavior.
 
Already I've created two deference XML layouts (layout-large-land and
> layout-land)for a single inner fragment. But the device when rotate UI not
> change. How can i solve this issue.
 
See above... Also, as an FYI, if you provide some code of how you are
loading the fragments, you might get some better info on how to solve your
problem.
 
 
Thanks,
Justin Anderson
MagouyaWare Developer
http://sites.google.com/site/magouyaware
 
 
On Thu, Aug 28, 2014 at 10:45 PM, askl <amalskr@gmail.com> wrote:
 
askl <amalskr@gmail.com>: Aug 29 12:23AM -0700

Thanks Justin for your reply.
 
Yes you got my issue. But not totally. As you said that, in fragment layout
is not change when device rotation. I had to add
 
android:configChanges
 
 
line in manifest file. Mainly in my application has 3 tabs and first tab
has two inner fragment. So please help me to get orientation event in inner
fragment in First tab. If i remove that manifest code line, when device
rotation inner fragment will be goes back, That mean automatically reload
main fragment when rotation.
 
Thnx
 
 
 
 
On Friday, 29 August 2014 11:59:52 UTC+5:30, MagouyaWare wrote:
Justin Anderson <magouyaware@gmail.com>: Aug 29 11:42PM -0600

As I said before...
 
Also, as an FYI, if you provide some code of how you are loading the
> fragments, you might get some better info on how to solve your problem.
 
You are not going to get any help without showing us some code for how you
are managing your fragments...
 
Thanks,
Justin Anderson
MagouyaWare Developer
http://sites.google.com/site/magouyaware
 
 
On Fri, Aug 29, 2014 at 1:23 AM, askl <amalskr@gmail.com> wrote:
 
Eddie <branchweb74@gmail.com>: Aug 29 06:47AM -0700

Hi,
 
I have recently included android wear support in my app but when I went to
publish it today I was made aware my earlier version would be archived. My
earlier version was targeting api 16 to include as many devices as
possible.
 
I was hoping if a user doesn't have the latest devices capable of running
my updated android wear version then they would get the earlier version I
have published.
 
What is the correct procedure to enable this to happen please?
 
Regards
Hiko <hikosaisoku@gmail.com>: Aug 29 04:21AM -0700

Hello,
 
I have been searched for this solution on the web for a half day.
but, i could not find the way to solve it.
 
I could find the way to convert FROM DSA.
but, to know for me is opposite than this.
 
could you please let me know if you find out this.
 
i appreciate that you can paste the sample code, or the website URL that
code is described.
 
 
Thank you,
 
Regards,
Hiko
Patrick <patrick.godeau@gmail.com>: Aug 29 02:31AM -0700

Hello Madison,
Thanks for the suggestion. I've already tried this project, but most of the
time, the video doesn't play and I have an error...
Still looking for a working solution.
 
Le jeudi 28 août 2014 19:16:57 UTC+2, Madison Koenig a écrit :
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.