xdpi and ydpi, resulting in
(among others) a messed up LatinIME.
Solution: replace 96.0 with 160.0 (note, IEEE 754 32-bit floating point format).
Binary search: c042 Replace: 2043
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Hi,
On Tue, May 24, 2011 at 2:13 PM, Ajay Kalavakunta wrote:
> what is the data passed in the request
> "RIL_REQUEST_SEND_SMS_EXPECT_MORE".
This is documented in ril.h, see [1].
Joerie
[1]:
http://android.git.kernel.org/?p=platform/hardware/ril.git;a=blob;f=include/t
e Mms.apk, which is included in
AOSP. The Android market on the other hand is only available to
'official' Google partners.
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
board. Have a
look at libsensors for crespo [1]. Once implemented correctly, it
should be automatically loaded by the sensors daemon (as
/system/lib/hw/sensors.boardname.so).
Joerie
[1]:
http://android.git.kernel.org/?p=device/samsung/crespo.git;a=tree;f=libsensors;h=735a4b272dfa82c536cbf957f3
Hi,
On Tue, May 3, 2011 at 6:55 PM, Douglas Selph wrote:
> Does anybody have any clues here?
Tried logcat -b radio?
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
lse in the 'hw' directory) are tied to your
device's board/kernel interface.
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Hi,
On Tue, Apr 19, 2011 at 10:19 PM, József Márk Király wrote:
> Well yea, I'm using Ubuntu right now, any idea for that?
You could always check out the relevant source code for your input
device. Alternatively, if xev doesn't work (huh?) perhaps [1] is of
use.
Joeri
Hi,
On Tue, Apr 19, 2011 at 9:58 PM, József Márk Király wrote:
> Any idea?
In Android, 'getevent' should show the keycodes as returned by the
kernel. You should be able to use those to map them to Android
scancodes.
(Disclaimer: might be confusing keycodes and scancodes in the ab
t's slightly outdated, in
which case you should take a careful look at eg. the herring
defconfig.
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Hi,
On Tue, Apr 12, 2011 at 10:32 PM, Dudero wrote:
> Does anybody now if there are handset manufactors, who are releasing
> their complete source code?
Probably the Nexus phones are as good as it gets (AOSP is maintained,
any blobs are redistributable under a reasonable license).
output would probably point out the culprit.
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Hi,
On Sun, Mar 13, 2011 at 12:58 PM, arindam wrote:
> Kernel panic - not syncing: Attempted to kill init!
>
> Now my question is for android anything I have to change in kernel
> side?
Are you passing init=/init on the kernel command line?
Joerie
--
unsubscribe: android-port
r is android::createOMXPlugin().
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Hi Daniele,
On Mon, Mar 7, 2011 at 12:15 PM, paldan wrote:
> Is it possible to build only the RIL related part of the platform?
Try 'mmm hardware/ril/reference-ril/' or simply 'mm' from the
reference-ril directory itself.
Joerie
--
unsubscribe: android-porting+unsub
Hi,
On Tue, Mar 1, 2011 at 2:39 AM, Sunil Jha wrote:
> Can i get a reference RIL so that i can modify it as per my GSM
> module?
The AT reference RIL is included in the AOSP Android repositories. See
http://android.git.kernel.org/?p=platform/hardware/ril.git;a=tree
Joerie
--
unsub
Practically, forget it, especially if you have never ported a similar device.
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
a /dev/ttyGPS0 (iirc). Yes, it would be the
file to 'edit', but as it contains compiled code, doing so is
non-trivial.
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
mething completely different from what it's expecting to
see. At best the function will simply fail, probably it will lead to a
crash.
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
boardname is the kernel supplied board
name, lowercase (and if it contains spaces, up to the first space).
> If yes, what shall I write into this file?
Anything to be performed at init, specific to your board.
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://grou
Hi,
One of the kernel.org mirrors appears to be having issues. Try
temporarily setting android.git.kernel.org to 199.6.1.176
(android3.git.kernel.org) or 130.239.17.12 (android4.git.kernel.org)
in your resolv.conf.
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website
Hi,
Try running the binary/script using /system/bin/logwrapper and then
check the logs using logcat.
Joerie
On Wed, Feb 2, 2011 at 11:59 AM, extrapedestrian
wrote:
> how can I get echo messages from various scripts started from init.rc
> printed to console?
>
> for example, dhcpcd
see debug_verbosity in
linker.c/linker_debug.h).
Joerie
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
alsa_sound.
- Missing libasound reference in alsa-utils.
- Format type modifier incompatibility with bionic in alsa-lib (I'm
not sure why this hasn't surfaced before).
Joerie
On Wed, Dec 29, 2010 at 12:39 PM, hedwin wrote:
> Joerie,
>
> See some big difference between w
ther
portait or landscape mode.
- The Japanese IME displays fine, which - I suppose - isolates the
issue to being somewhere in the LatinIME
- My screen size is 480x800, and I've set ro.sf.lcd_density
accordingly (240).
Has anyone got an idea where I should start looking?
Joerie
--
unsubscr
Hi,
> I've built the android-2.6.37-rc7 kernel already, but android-2.2
> platform manifest crashes at the init process.
Are you sure you're running into a kernel issue? Assuming you've got
the kernel config right, have you tried increasing the debug verbosit
Hi Deepak,
Both ALSA and /hardware/ti/omap3 require some patching to build on
Gingerbread. In addition to the patches posted already, have a look at
my Github repositories [1], which should have all necessary OMAP-
related patches.
Joerie
[1]: https://github.com/ius
--
unsubscribe: android
l tree were applied for Eclair to run).
Apart from that, there's still plenty of work to do. If you happen to
have the phone and you're not afraid of the kernel, pleae /do/ hop
along at #h1 on freenode, I could use a hand.
Obligatory proof of concept: http://i44.tinypic.com/331in0x.jpg
leased bySamsungyet?
>
> On Jan 16, 7:22 am, Joerie wrote:
>
> > While there are currently two phones on the market running the 360
> > LiMo OS (SamsungM1 andH1), they fundamentally differ in hardware
> > design, and thus should be considered different porting targets (H1
>
While there are currently two phones on the market running the 360
LiMo OS (Samsung M1 and H1), they fundamentally differ in hardware
design, and thus should be considered different porting targets (H1
runs on top of a OMAP3430, whereas the M1 is powered by a S3C6410).
I do think both have great p
29 matches
Mail list logo
