( 72): JNI_OnLoad functions registered
So I don't understand why, when java requires fir21 from
ResampleInputStream JNI, it can't find it.
Naming should be correct, I guess... (this is all OOB AOSP code).
On Monday, 25 November 2013 05:27:28 UTC-8, ffxx68 wrote:
I built my AOSP JB for a tablet
I built my AOSP JB for a tablet, including all necessary customizations
(project details discussed over here:
https://groups.google.com/forum/#!forum/renesas-emev-osp).
I'm now in the clean-up stage, with a list of minor issues being debugged
and hopefully removed. One of these is the use of
i can suggest to start from the examples found in the AOSP-supported
device, e.g.
$ cd device/moto/stingray/sensors
$ ls -l
total 84
-rw-r--r-- 1 ffxx68 ffxx68 4795 2012-12-21 19:45 AccelerationSensor.cpp
-rw-r--r-- 1 ffxx68 ffxx68 1595 2012-12-21 19:45 AccelerationSensor.h
-rw-r--r-- 1 ffxx68
Hi,
while recompiling a binary using the 4.4.3 Android NDK toolchain and
linking it to an ASOP JB build, I get the warnings Unknown EABI object
attribute 44, as below:
[...]
CC test/srvctl.c
test/srvctl.c: In function 'main':
test/srvctl.c:161: warning: ISO C90 forbids mixed
Nothing was really missing, apart from calibration.
Since parameters for low-pass filtering (to extract gravity; hardcoded in
AOSP in *WindowOrientationListener.java*) are based on real m/s^2
acceleration values, having sensor returning values too far from reality
made some check functions
Hi,
I have ported the BMA220 accelerometer too, as part of this JB porting
project:
https://groups.google.com/forum/?fromgroups=#!forum/renesas-emev-osp
our sensor HAL source code is here:
https://github.com/Renesas-EMEV2/Renesas-device_emev/tree/emev-4.1/sensors
All seems working well,
Same issue with the logo, for another 4.1 porting project:
https://groups.google.com/forum/?fromgroups=#!forum/renesas-emev-osp
Any help appreciated.
On Monday, 10 June 2013 22:30:48 UTC+2, Dave Smith wrote:
Hi all -
We are running 4.1.2 on an OMAP4460 platform made by Variscite:
what does the logcat say, while booting up? most probably it's looping
over, after some crash.
watch carefully and check for the portion of log that is repeating itself
(it could be very large).
On Thursday, 6 June 2013 06:42:33 UTC+2, ddy wrote:
hi all
I'm porting an ics device to Jb,it
= wpa_driver_signal_poll,
solved the problem, as WiFi signal level is shown on notification bar icon!
On Tuesday, 14 May 2013 11:11:16 UTC+2, ffxx68 wrote:
Hi,
maybe a bit late here... but I'm facing exactly the same issue on my JB
porting.
I'd like to understand what has been done to solve
Hi,
maybe a bit late here... but I'm facing exactly the same issue on my JB
porting.
I'd like to understand what has been done to solve it.
What do you mean by driver ioctls are failing?
What have you debugged/fixed?
thanks
Fabio
On Friday, 27 August 2010 11:05:27 UTC+2, guru wrote:
HI All,
this page on TI wiki:
http://processors.wiki.ti.com/index.php/Android-USB-3G-Modem-Integration
-Vishveshwar
On Thursday, May 9, 2013 9:40:24 PM UTC+5:30, ffxx68 wrote:
Hi,
I’m porting a GB tablet firmware to JB (
https://groups.google.com/forum/#!forum/renesas-emev-osp) and I’m now
stuck
, Vishveshwar wrote:
On JB 3G-modem integration seems to have become easier.
Refer this page on TI wiki:
http://processors.wiki.ti.com/index.php/Android-USB-3G-Modem-Integration
-Vishveshwar
On Thursday, May 9, 2013 9:40:24 PM UTC+5:30, ffxx68 wrote:
Hi,
I’m porting a GB tablet firmware
Hi,
I’m porting a GB tablet firmware to JB (
https://groups.google.com/forum/#!forum/renesas-emev-osp) and I’m now stuck
at the 3G modem integration. I missed what has been customized in GB
(though I can access code), so I have to redo the work myself.
I found Adrien's tutorial
, ffxx68 wrote:
Seeking video integration expert's help.
Porting OMX HW codecs to JB for our platform:
https://groups.google.com/forum/#!topic/renesas-emev-osp/NpJj163nEQ8[1-25-false]
I get the error below, on video playback. When a video it's started from
from the Gallery app, screen gets
- is there a debugger available for Android, which can communicate over
ADB?
thanks
Fabio
On Friday, 8 March 2013 16:56:35 UTC+1, ffxx68 wrote:
Seeking video integration expert's help.
Porting OMX HW codecs to JB for our platform:
https://groups.google.com/forum/#!topic/renesas-emev-osp
540 212 169776 30792 40033a40 S android.process.media
media 732 1 21932 5444 40083b64 S
/system/bin/mediaserver
u0_a27349 212 181864 42360 40033a40 S com.android.systemui
On Friday, 8 March 2013 16:56:35 UTC+1, ffxx68 wrote:
Seeking video
Seeking video integration expert's help.
Porting OMX HW codecs to JB for our platform:
https://groups.google.com/forum/#!topic/renesas-emev-osp/NpJj163nEQ8[1-25-false]
I get the error below, on video playback. When a video it's started from
from the Gallery app, screen gets black and a
.
But I can't see what's wrong!
On Thursday, 8 November 2012 14:42:21 UTC+1, ffxx68 wrote:
Hi
I'm trying to port a ICS implementation of ALSA audio to JB, or a tablet
device, under this project:
Mainly, I have the following to integrate (which I have the patch for ICS):
external/alsa-lib
audio_route.c to force power first and now everything goes fine... looks
like.
Thanks all for the contributions!
On Thursday, 8 November 2012 14:42:21 UTC+1, ffxx68 wrote:
Hi
I'm trying to port a ICS implementation of ALSA audio to JB, or a tablet
device, under this project:
Mainly, I have
I found out that I was missing a file that is mandatory for JB,
media_codecs.xml, and after adding it mp3 and mp4 are reproduced as expected.
Now I'm debugging the hal to see why it doesn't set mixer controls. I hope I
can figure it out soon...
--
--
unsubscribe:
exactly the same as the PCM that was decoded by Stagefright.
However, it's still PCM, and is typically 44.1 or 48 kHz 16-bit signed
interleaved stereo for hardwired speakers/headphone out.
On Thursday, November 8, 2012 5:42:21 AM UTC-8, ffxx68 wrote:
Hi
I'm trying to port a ICS
is produced by the Android
MediaPlayer. Does it depend on the origin file being decoded (e.g. an
.mp3)?
If it's not producing exactly what the PCM expects, I may get an error from
the player.
On Thursday, 8 November 2012 14:42:21 UTC+1, ffxx68 wrote:
Hi
I'm trying to port a ICS
Thanks. So the actual blocker must be the criptic E/MediaPlayer( 633): error
(1, -2147483648) .
Any clue about this?
--
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
---
You received this message because you are
:36 sdcard1
d- system system1970-01-02 00:36 usbdisk0
root@android:/ # ls -la
/mnt/sdcard/
d- root root 1970-01-02 00:00 .android_secure
...
On Monday, 11 February 2013 17:52:47 UTC+1, ffxx68 wrote
I'm porting AOSP JB to a tablet and getting this error, which I don't
understnad the reason of:
*W/MediaScanner( 487): Error opening directory
'/mnt/sdcard/.android_secure/', skipping: Permission denied.
*
Here's my mount list:
root@android:/ # mount
rootfs / rootfs rw 0 0
/dev/root / ext3
I've put also my init.rc (all in one) in the same DropBox folder.
On Monday, 11 February 2013 16:49:37 UTC+1, ffxx68 wrote:
I'm porting AOSP JB to a tablet and getting this error, which I don't
understnad the reason of:
*W/MediaScanner( 487): Error opening directory
'/mnt/sdcard
also audio_policy.conf, but it's not directly related to this.
2. I'm not aware of such a restriction.
3. That's the hardware volume, which is mostly unused currently.
AudioFlinger applies a software attenuation instead.
On Tuesday, January 29, 2013 1:26:40 AM UTC-8, ffxx68 wrote:
I think
,
float right)
{
return -ENOSYS;
}
On Monday, 28 January 2013 17:23:33 UTC+1, ffxx68 wrote:
Hi Glenn, thanks a lot for answering.
I hope you don't mind if I ask you to guide me through these steps. I have
both the kernel driver code, the datasheet and device
not really sure how to use these controls, in audio/audio_hw.c or
audio/audio_route.c code...
On Monday, 28 January 2013 11:59:52 UTC+1, ffxx68 wrote:
I'm now pretty sure I made a mistake when I thought I solved: I simply
used a different Android file system (of which I don't have source
for
the grouper' example, for just one control, I could try to map to my device
and eventually extend to all controls.
On Thursday, 8 November 2012 14:42:21 UTC+1, ffxx68 wrote:
Hi
I'm trying to port a ICS implementation of ALSA audio to JB, or a tablet
device, under this project:
Mainly, I
audible: 8000: 11,
Audio routes:
mMainType=0x0
mBluetoothName=null
On Friday, 25 January 2013 18:10:24 UTC+1, ffxx68 wrote:
Ok. I think I solved. Thanks again for the suggestions!
I just compiled the audio/ as is (adapting only my .mk files), and it goes
just fine on my device:
https
that use tinyalsa, such as device/samsung/tuna/audio
and device/asus/grouper/audio. When JB-MR1 is open-sourced [I don't have
the date],
there will updated audio HALs there.
On Thursday, November 8, 2012 5:42:21 AM UTC-8, ffxx68 wrote:
Hi
I'm trying to port a ICS implementation of ALSA audio
names, etc, but looks like that's
not necessary...
On Friday, 25 January 2013 17:21:21 UTC+1, ffxx68 wrote:
Hi Glenn,
I'm back on this after some time.. Thanks for the useful suggestion, to
start from one such examples. I think tinyalsa it's much easier than going
for the full ALSA-lib
root
group root
oneshot
And, I had to fix file privileges to make it finally go:
chown system:system init.rc
chown system:system init.emxx.rc
chmod 644 init.rc
chmod 644 init.emxx.rc
On Friday, 7 December 2012 11:41:46 UTC+1, ffxx68 wrote:
Hi,
I'm struggling to find a solution
Hi,
I'm struggling to find a solution to this problem.
I have a device with the following definitions:
emev.mk:PRODUCT_NAME := renesas_emev
emev.mk:PRODUCT_DEVICE := emev
emev.mk:PRODUCT_BOARD := emev
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/init.rc:root/init.rc \
system system /sys/class/leds/led2/brightness
service emev-setup /system/etc/init.emev.sh
oneshot
-
On Friday, 7 December 2012 11:41:46 UTC+1, ffxx68 wrote:
Hi,
I'm struggling to find a solution to this problem.
I have a device with the following definitions
... and the complete set of product names (in my emev.mk) is:
PRODUCT_NAME := renesas_emev
PRODUCT_DEVICE := emev
PRODUCT_BOARD := emev
PRODUCT_BRAND := emxx
PRODUCT_MANUFACTURER := renesas
On Friday, 7 December 2012 11:43:43 UTC+1, ffxx68 wrote:
Sorry, forgot to mention that the content
something must have changed...
On Friday, 7 December 2012 12:31:05 UTC+1, Vishveshwar wrote:
On Friday, December 7, 2012 4:11:46 PM UTC+5:30, ffxx68 wrote:
Hi,
I'm struggling to find a solution to this problem.
I have a device with the following definitions:
emev.mk:PRODUCT_NAME
btw - thanks Vishveshwar!
On Friday, 7 December 2012 16:29:34 UTC+1, ffxx68 wrote:
the machine name from kernel is
cd arch/arm/mach-emxx
grep MACHINE_START *.c
emev_board.c:MACHINE_START(EMXX, EMXX)
So, looks like I need an init.EMXX.rc file... Does lower/upper case
count?
I'm
to check?
On Friday, 7 December 2012 12:31:05 UTC+1, Vishveshwar wrote:
On Friday, December 7, 2012 4:11:46 PM UTC+5:30, ffxx68 wrote:
Hi,
I'm struggling to find a solution to this problem.
I have a device with the following definitions:
emev.mk:PRODUCT_NAME := renesas_emev
I was looking for the same kind of info too.
What are the contact points?
Do you need to get in touch with a Google sales rep?
On Wednesday, 5 December 2012 07:51:31 UTC+1, Jacob wrote:
Your company needs business agreement in place with Google Android team.
On Tue, Dec 4, 2012 at 10:00 AM,
Thanks Shree. I will check that, but could you please elaborate about the
initrd? How could I verify that?
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Hi
I'm trying to port a ICS implementation of ALSA audio to JB, or a tablet
device, under this project:
Mainly, I have the following to integrate (which I have the patch for ICS):
external/alsa-lib
hardware/alsa_sound
plus some other smaller fix around, but I want to understand first of all
Forgot to link my project's discussion board:
https://groups.google.com/forum/?fromgroups=#!forum/renesas-emev-osp
On Thursday, 8 November 2012 14:42:21 UTC+1, ffxx68 wrote:
Hi
I'm trying to port a ICS implementation of ALSA audio to JB, or a tablet
device, under this project:
Mainly, I
Hi sarika, have a look at the diffs here:
https://github.com/Renesas-EMEV2/RenesasEV2-BSPGB-Kernel/commit/910c76b7bbd631ba8e4384b57cb1c201fbdd2f05
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
info on that here:
http://source.android.com/tech/input/getevent.html
Weston
On Friday, September 21, 2012 5:39:41 AM UTC-7, ffxx68 wrote:
Hi cnet,
yes, that's what I've also done. Indeed looks like the kernel driver
isn't the main problem, I think...
Here's what I've achieved so far
Hi cnet,
yes, that's what I've also done. Indeed looks like the kernel driver isn't
the main problem, I think...
Here's what I've achieved so far. I've introduced the .idc file for the
touch device, so it gets recognized as an actual touch screen, not as a
pointer pad. Then I've set the
Porting to JB an Open Source Renesas-based tablet
(https://groups.google.com/forum/?hl=enfromgroups=#!forum/renesas-emev-osp)
and having troubles with the touch screen.
While GB implementation perfectly supported the touch panels (PixCir or
Goodix mdels, depending of hardware revision), with
.
On Wednesday, 13 June 2012 09:55:59 UTC-7, ffxx68 wrote:
After upgrading my host to Ubuntu 12 and successfully rebuilding android,
after isntallation on device, the system boot loops into this error:
I/Zygote ( 147): Preloading classes...
D/dalvikvm( 147
After upgrading my host to Ubuntu 12 and successfully rebuilding android,
after isntallation on device, the system boot loops into this error:
I/Zygote ( 147): Preloading classes...
D/dalvikvm( 147): GC_EXPLICIT freed 47K, 78% free 232K/1024K, external
0K/0K,
/MediaProfiles( 1437): could not find media config xml file
D/dalvikvm( 1437): GC_EXPLICIT freed 99K, 47% free 545K/1024K, external
0K/0K, paused 16ms
...
On Friday, 13 April 2012 11:10:52 UTC+2, ffxx68 wrote:
Hi experts.
I've started a new project about porting AOSP (2.3.6
/system/lib/hw/overlay.emxx.so
./symbols/system/lib/hw/lights.emxx.so
On Friday, 13 April 2012 11:10:52 UTC+2, ffxx68 wrote:
Hi experts.
I've started a new project about porting AOSP (2.3.6 for the time being)
to a tablet which I own. I have created the git repositories and a
discussion group
Hi experts.
I've started a new project about porting AOSP (2.3.6 for the time being) to
a tablet which I own. I have created the git repositories and a discussion
group as well for this project:
https://github.com/ffxx68
https://groups.google.com/forum/?fromgroups#!forum/renesas-emev-osp
I
Hi koba, all. This is juat to report that the solution is to look for
the hdaders in the Renesa kernel sources.
On 21 Mar, 20:03, ffxx68 ffum...@googlemail.com wrote:
Infact, I'm missing the directory where to ger the fbcommon.h. and
proably much more...
On Mar 21, 6:37 pm, ffxx68 ffum
Hi Koba,
I’m also trying to build Android for a tabelt based on the Renesas EMMA EV2
and followoing the useful suggestions found here. I know many HW
peripherals may differ from the KZM-A9 board, but I have the kernel source
code and the Renesas BSP RC2 (someone has posted it, a while ago, in
I'm afraid the BSP I have is incomplete...
On Mar 21, 3:05 pm, ffxx68 ffum...@googlemail.com wrote:
Hi Koba,
I’m also trying to build Android for a tabelt based on the Renesas EMMA EV2
and followoing the useful suggestions found here. I know many HW
peripherals may differ from the KZM-A9
Infact, I'm missing the directory where to ger the fbcommon.h. and
proably much more...
On Mar 21, 6:37 pm, ffxx68 ffum...@googlemail.com wrote:
I'm afraid the BSP I have is incomplete...
On Mar 21, 3:05 pm, ffxx68 ffum...@googlemail.com wrote:
Hi Koba,
I’m also trying to build
57 matches
Mail list logo
