Theoretically with the new low mem support of android kitkat you could...
however you might run into issues.
eg, for me, I run hardware with older gpu, and while the gpu is supposed to
support opengles 2+, the drivers had issues, and the company doesnt seem to
be maintaining them any longer.
So
Gentleman,
Again I'm porting a new version of android 4.3.1 to a piece of hardware
I've already got older roms on.
I've noticed that running reboot as super user at command line doesnt
reboot most of the time, it just does emergency remounts and then hangs.
I've run kernels/uboot from older bu
Ends up it was just the touchslop calibration... after playing with it, I
was able to get it a lot better...
On Wednesday, January 8, 2014 9:36:02 PM UTC-8, kamal kumar wrote:
>
> Hi Wetson,
> Enabling/Disabling of the built in zoom control logic is part of Browser
> app.
>
> However enabling
Hi,
Has anybody seen that FLAC decoder/Parser in Android Kitkat is taking up
too much CPU.
For example to get 4096 frames it can take anywhere from 90 to 150 msec on
our platform.
Only change between JB and KK seems to be in Android.mk. KK Android.mk adds
LOCAL_CLANG := true
LOCAL_CFLAGS += -
See https://code.google.com/p/android/issues/detail?id=62562
comment #23 Nov 25, 2013
and the AOSP CL that it links to:
https://android-review.googlesource.com/#/c/70749/
On Thursday, January 9, 2014 2:43:38 PM UTC-8, Uday Gupta wrote:
>
> Hi,
>
> Has anybody seen that FLAC decoder/Parser in Andro
Thanks.
I actually made the same change after I posted the query and the stutters
went away. Looks like the clang compiler is was inefficient compared to gcc
or is it that compiler options are not getting passed to clang?
On Thursday, January 9, 2014 3:06:08 PM UTC-8, Glenn Kasten wrote:
>
> Se
The clang -ftrapv option is not currently implemented efficiently for the
type of integer computation-intensive code used in FLAC inner loops.
The code generated for -ftrapv option doesn't yet take advantage of the ARM
architecture's "V" (overflow) condition code bit.
On Thursday, January 9, 201
Hi Reena,
Check the Kernel layer whether it supports Bluetooth HID or not.
If it is enabled & you still observe the problem exists, then try applying
android InputSubsystem patches to make it working.
It is available on net.
Regards,
Ramya
On Wed, Jan 8, 2014 at 11:28 PM, Reena Bains wrote:
>
