Related
Trying to solve audio stuttering...
I'm currently running the Eclair build from Kenia from
http://forum.xda-developers.com/showthread.php?t=827537
Like the speed, most things working fine.
... but playing media results in audio stutter.
Problem is apparently well known and affects more devices, see also
http://forum.xda-developers.com/showthread.php?t=711692&page=364
Indeed, killing battery service solves stuttering, but I'd like to keep it running, of course
Any build/kernel out there that does not suffer from this?
I'd like to find out what's different, since in the past it seemed to have worked, but with pushing more accurate battery readout in the latest kernels, this problem was introduced...
Maybe just putting an old battery service in a current kernel could work?
Cheers,
Robbert
I can confirm that audio shuttering is a common problem, but I wasn't aware it can be related to the battery code. Can anyone check if killing battery service helps with shuttering audio (youtube maybe?) on other build (e.g. FRX03)?
TBH battery code is unfinished since Camro (the guy who did most of it) bricked his phone. If it's really a kernel issue maybe I'd could build test kernel w/o battery code sometime next week.
g3rm0 said:
I can confirm that audio shuttering is a common problem, but I wasn't aware it can be related to the battery code. Can anyone check if killing battery service helps with shuttering audio (youtube maybe?) on other build (e.g. FRX03)?
TBH battery code is unfinished since Camro (the guy who did most of it) bricked his phone. If it's really a kernel issue maybe I'd could build test kernel w/o battery code sometime next week.
Click to expand...
Click to collapse
Hi, g3rm0,
Always happy to do some more testing!
Took me some time to get a FRX03 build back working (not my daily build, Froyo is just too slow on blackstone, I'm afraid)
Anyway: Using the FRX03 build from
http://forum.xda-developers.com/showthread.php?t=711692
(full package, so using the included rootfs, zimage and modules.)
I can *confirm* that audio still stutters, and also on this build stuttering immediately disappears when battery service is killed!
Hope it helps?
If there's need to test different rootfs/zimage/modules/startup/..., just let me know!
Actually, for me, I just want to disable battery service so I can listen to music on my 15min bike ride to work!
But I am a linux Noob, so although "kill -9" is in my power to stop the service, actually restarting a service is momentarily out of reach...
Any help with restarting the [battery] service would be greatly appreciated!
Cheers,
Robbert
You don't need to compile a kernel tbh, why don't you just create an init script which includes the "kill -9 28" command? The init script will get launched on startup therefore killing the battery service as desired.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
You don't need to compile a kernel tbh, why don't you just create an init script which includes the "kill -9 28" command? The init script will get launched on startup therefore killing the battery service as desired.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
Hi, Stickman89,
Yes, I read this also somewhere, thanks for reminding me!
My bigger wish is to be able to restart the battery service after finishing listening to music, not having to restart Android (and first WinMo) because that takes way too much time.
How do I restart the service, any idea?
Cheers,
Robbert
well to do that you would need to install a mobile terminal app from the market and create two scripts, one to disable the service and the other to enable it. Only problem is this would not be automated and you would need to execute the script via the terminal app installed.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
well to do that you would need to install a mobile terminal app from the market and create two scripts, one to disable the service and the other to enable it. Only problem is this would not be automated and you would need to execute the script via the terminal app installed.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
I could live with that (still hoping for a proper fix, of course!)
Most builds come with a terminal app (Busybox is popular, if I remember correctly) that's what you mean?
But still I need the command line / script lines to execute, and that's where I'm stuck, since I know how to kill the service from the prompt of my terminal in the phone, but not how to "unkill" it!
"Disable/enable" sounds much better than "kill/unkill", but how???
As a side note, I also get the impression that the android terminal does not give me full access to a shell environment, since, for example, the "ps" command is severely limited! (wanted to find out more information on process "[battery]", but no chance with the crippled "ps" command...)
Maybe there are better (more functional) terminals out there?
Or do we actaully have access to "enable/disable service" commands in this "busybox" and I just don't know the proper command?
(just for reference: I'm running Kenia's eclair build that includes busybox 1.5 as terminal)
Cheers, Robbert
Even better, look what I just found for you: http://forum.xda-developers.com/showthread.php?t=486486
Basically you can create a homescreen icon and assign a shell command to it, simply create an icon and assign the "kill -9 28" command to it which will kill the battery service, I would have to check out the process name to be able to start it again. Let me take a look for you (I don't think "start -9 28" will work as we have only issued the process ID and since it is no longer running will be useless)
Best Regards,
ST1Cl<^^aN
If you have a working adb setup then type: "adb shell ps -w"
or download a mobile terminal and type: "ps -w"
Ok here are the processes running, PID 28 is krpcserversd in our case which is incorrect so we need to look for the battery service which is PID 29 for me.
Code:
# ps
ps
PID USER VSZ STAT COMMAND
1 0 312 S /init.android
2 0 0 SW [kthreadd]
3 0 0 SW [ksoftirqd/0]
4 0 0 SW [watchdog/0]
5 0 0 SW [events/0]
6 0 0 SW [khelper]
7 0 0 SW [suspend]
8 0 0 SW [kblockd/0]
9 0 0 SW [cqueue]
10 0 0 SW [kmmcd]
11 0 0 SW [btaddconn]
12 0 0 SW [btdelconn]
13 0 0 SW [kondemand/0]
14 0 0 SW [smd_tty]
15 0 0 DW [rpcrouter]
16 0 0 SW [kadspd]
17 0 0 SW [detection/0]
18 0 0 SW [button/0]
21 0 0 SW [kswapd0]
22 0 0 SW [aio/0]
23 0 0 SW [panel_on/0]
24 0 0 SW [tty_wq/0]
25 0 0 SW [usb_mass_storag]
26 0 0 SW [kstriped]
27 0 0 SW< [krfcommd]
28 0 0 SW [krpcserversd]
29 0 0 DW [battery]
54 0 0 SW [mmcqd]
71 0 0 SW< [loop2]
90 0 0 SW< [loop0]
94 0 0 SW< [loop1]
133 0 1736 S busybox telnetd -b 192.168.20.1 -l /bin/sh
1168 0 1740 S /bin/sh /bin/userinit.sh -c /sdcard/conf/froyo.user.
1226 0 1740 S /bin/sh
1227 1000 812 S /system/bin/servicemanager
1228 0 3728 S /system/bin/vold
1229 0 1736 S /bin/sh /bin/netd
1231 0 668 S /system/bin/debuggerd
1232 1001 5464 S /system/bin/rild -l /lib/froyo/libhtcgeneric-ril.so
1233 0 87964 S zygote /bin/app_process -Xzygote /system/bin --zygot
1234 1013 26664 S < /system/bin/mediaserver
1238 1002 1260 S /system/bin/dbus-daemon --system --nofork
1239 0 824 S /system/bin/installd
1240 1017 1612 S /system/bin/keystore /data/misc/keystore
1241 0 3340 R /sbin/adbd
1243 0 3720 S /system/bin/netd
1258 1000 246m S system_server
1330 10054 124m S com.swype.android.inputmethod
1345 10011 129m S N com.google.process.gapps
1434 1001 134m S < com.android.phone
1685 1000 123m S com.android.settings
2847 0 0 DW [audmgr_rpc]
3391 0 0 DW [ksdiorqd]
3392 0 0 SW [tiwlan_wifi_wq]
3400 1010 3004 S /system/bin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/da
3588 10007 107m S com.android.quicksearchbox
4937 10053 159m S android.process.acore
5076 10058 108m S com.appspot.swisscodemonkeys.apps
5083 10023 105m S com.android.voicedialer
5095 10004 110m S com.android.vending
5106 10026 114m S com.google.android.googlequicksearchbox
5113 10002 126m S android.process.acore
5233 10037 105m S com.android.defcontainer
5243 10030 112m S com.google.android.apps.genie.geniewidget
5273 10010 111m S < android.process.media
5284 10014 114m S com.google.android.gm
5338 0 0 SW [pdflush]
5462 10064 106m S mobi.infolife.taskmanager
5524 0 0 SW [pdflush]
5532 10070 123m S stericson.busybox
5584 10061 115m S com.facebook.katana
5631 0 1736 S sleep 500
5635 10059 114m S cn.miren.browser
5662 0 740 S /system/bin/sh -
5665 10060 122m S com.voxmobili.phonebook2
5691 10056 108m S com.miui.player
5697 10028 108m S com.google.android.apps.uploader
5705 0 1740 R ps
Once the battery service has been located so in my case PID 29 then to kill that PID via adb simply issue "adb shell kill 29" (PID number may vary so please check) and to start the PID issue "command-removed".
So if you want to use the application i linked you to over at the G1 thread then simply assign the commands "kill 29" to kill the service and "command-removed" (remember that the PID number may vary so please check) to start the service again.
FYI charging will stop at this point and battery stats will freeze at there current percentage.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
Ok here are the processes running, PID 28 is krpcserversd, interestingly we also have the PID 29 which is battery.
Click to expand...
Click to collapse
Same here for me: PID is 29 (it may different in some builds) but... when I killed battery service (kill -9 29) audio shuttering stopped. It also solved "audpp: DMA missed" messages in dmesg so maybe we're on the right track.
IMHO killing battery service every time is not a solution. Maybe code just needs to be cleaned up a little.
Anyway, for now kill -9 is the only (known) way to achieve smooth playback.
Ok then all we need to do is adjust the scheduling priority until we find the sweet spot via renice
That way we wouldn't need to kill anything and that can be added to init fairly easy, we would have to test some values first.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
Ok then all we need to do is adjust the scheduling priority until we find the sweet spot via renice
That way we wouldn't need to kill anything and that can be added to init fairly easy, we would have to test some values first.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
Tried that already, afraid it might not be so easy...
Gave the audiomanager -20 or so, and the battery service +20 or so, no effect, still stuttering...
But maybe your mileage may vary, did you try this on your build?
Cheers,
Robbert
Stickman89 said:
If you have a working adb setup then type: "adb shell ps -w"
or download a mobile terminal and type: "ps -w"
Ok here are the processes running, PID 28 is krpcserversd in our case which is incorrect so we need to look for the battery service which is PID 29 for me.
Click to expand...
Click to collapse
Also for me, number 29 it is.
Stickman89 said:
Once the battery service has been located so in my case PID 29 then to kill that PID via adb simply issue "adb shell kill 29" (PID number may vary so please check) and to start the PID issue "--locating-process--".
So if you want to use the application i linked you to over at the G1 thread then simply assign the commands "kill 29" to kill the service and "--locating-process--" (remember that the PID number may vary so please check) to start the service again.
Click to expand...
Click to collapse
Huh?
Something must have gotten "lost in translation" here, I have really no idea what is meant by the command "--locating-process--", I guess it's not literally typing in this phrase, what am I missing?
Ah, just noticed your statement in an earlier post "I would have to check out the process name to be able to start it again", I guess that's what you meant by "--locating-process--" in the next post...?
Well, to be continued...
Cheers,
Robbert
The service isn't successfully starting after being killed, I initially thought it had but it appears it failed to kill on first try therefore it was still running. I will keep looking into this though, stuttering isn't that bad on my build. I will upload it soon, it is there but isn't too bad.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
The service isn't successfully starting after being killed, I initially though it had but it appears it failed to kill on first try therefore it was still running. I will keep looking into this though, stuttering isn't that bad on my build. I will upload it soon, it is there but isn't too bad.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
Yeah, noticed that too, sometimes the service takes a few seconds to unload (or at least "ps" still shows it.)
Maybe someone else has some bright ideas, posted it also at Neopeek, some good guys over there, too
I just hoped someone had a quick solution, but we may have to wait for some more kernel development. I'll keep my eyes open, if something pops up I'll update.
Cheers,
Robbert
May I ask what application you guys are using to kill the process? I downloaded the terminal emulator app, however when I type "kill 29" it says operation not allowed.
I'm assuming this is because of a rights issue. I am using Android 2.2 (FroYo) by the Brilliant Mistake [03 Sep 2010] (V1.6) with the latest kernel, zimage, rootfs along with FRX03 update.
I'm a bit confuse as to how I can "root" my device in order kill the battery process so I too can listen to my music without the annoying stuttering.
Any info would be appreciated. Thanks
Just type "su" first
g3rm0 said:
Just type "su" first
Click to expand...
Click to collapse
Thank you for your reply.
I type "su" then enter...
I get a "#" prompt
then I type "kill 29" enter
I don't get any type of confirmation just another "#" prompt
I try listening to my music, stuttering is still there... What am I doing wrong?
James62370 said:
Thank you for your reply.
I type "su" then enter...
I get a "#" prompt
then I type "kill 29" enter
I don't get any type of confirmation just another "#" prompt
I try listening to my music, stuttering is still there... What am I doing wrong?
Click to expand...
Click to collapse
"kill -9 29" has a better chance
Did you check before killing it, that [battery] is process 29 for you? (use "ps" command in shell)
Did you check afterwards that process 29 [battery] is indeed gone?
Just wait for viruscrazy submit the patch to phh to be merge in the main tree.It already in Jerome tree HERE
Code:
/* Patch to fix "audpp DMA missed" messages on AMSS version 52.62.25.34 */
1423 if ( machine_is_htcdiamond() || machine_is_htcblackstone() ) {
1424 if( !(snd_state & SND_STATE_PLAYBACK) ) {
1425 dex.cmd = PCOM_GET_BATTERY_DATA;
1426 msm_proc_comm_wince(&dex, 0);
1427 } /* else {
1428 printk("Skipping battery pcom call to avoid audppp DMA miss\n");
1429 } */
1430 }
Working now. Check my rom
You mean you want to try if you can activate the 3G module?
I flashed it but it doesn't work. There isn't even the mobile data option. You know where you can change APNs etc.
I couldn't grab the adb output though. Adb doesn't see my TF I'll try again in the evening.
Sent from my Galaxy Nexus using XDA
Nebucatnetzer said:
I flashed it but it doesn't work. There isn't even the mobile data option. You know where you can change APNs etc.
I couldn't grab the adb output though. Adb doesn't see my TF I'll try again in the evening.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
You can also put "ls /dev" in Terminal Emulator and give me the output
Nebucatnetzer said:
I flashed it but it doesn't work. There isn't even the mobile data option. You know where you can change APNs etc.
I couldn't grab the adb output though. Adb doesn't see my TF I'll try again in the evening.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
1. Make sure you have usb debugging enabled on the transformer (this is often not the case on new installs)
2. try the naked drivers
Naked drivers: http://forum.xda-developers.com/showthread.php?t=1379875
You can also put "ls /dev" in Terminal Emulator and give me the output
Click to expand...
Click to collapse
Here you go.
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ ls /dev
accelirq
alarm
android_adb
ashmem
asusec
battery
binder
block
bus
compassirq
console
cpu_dma_latency
cpuctl
device-mapper
dsp_fm34
full
fuse
graphics
i2c-0
i2c-1
i2c-2
i2c-3
i2c-4
input
kmsg
knvmap
lightsensor
log
maXTouch
maXTouch_messages
max_online_cpus
mem
mi1040
mpu
mpuirq
mtp_usb
nct1008
network_latency
network_throughput
null
nvhdcp1
nvhost-ctrl
nvhost-display
nvhost-dsi
nvhost-gr2d
nvhost-gr3d
nvhost-isp
nvhost-mpe
nvhost-vi
nvmap
ov5640
port
ppp
ptmx
pts
random
rfkill
rtc0
snd
socket
tegra-crypto
tegra_avp
tegra_camera
tegra_dc0
tegra_dc1
tegra_mediaserver
tegra_rpc
tegra_sema
timerirq
touch_debug
touchpanel
tps6586x
tty
ttyHS1
ttyHS2
ttyHS3
ttyS0
ttyS1
ttyS2
ttyS3
ttyUSB0
ttyUSB1
ttyUSB2
ttyUSB3
ttyUSB4
ttyUSB5
tun
uinput
urandom
usb
usb_accessory
vga_arbiter
wm8903
xt_qtaguid
zero
[email protected]:/ $
do you have a public source tree for your work ?
Nebucatnetzer said:
Here you go.
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ ls /dev
accelirq
alarm
android_adb
ashmem
asusec
battery
binder
block
bus
compassirq
console
cpu_dma_latency
cpuctl
device-mapper
dsp_fm34
full
fuse
graphics
i2c-0
i2c-1
i2c-2
i2c-3
i2c-4
input
kmsg
knvmap
lightsensor
log
maXTouch
maXTouch_messages
max_online_cpus
mem
mi1040
mpu
mpuirq
mtp_usb
nct1008
network_latency
network_throughput
null
nvhdcp1
nvhost-ctrl
nvhost-display
nvhost-dsi
nvhost-gr2d
nvhost-gr3d
nvhost-isp
nvhost-mpe
nvhost-vi
nvmap
ov5640
port
ppp
ptmx
pts
random
rfkill
rtc0
snd
socket
tegra-crypto
tegra_avp
tegra_camera
tegra_dc0
tegra_dc1
tegra_mediaserver
tegra_rpc
tegra_sema
timerirq
touch_debug
touchpanel
tps6586x
tty
ttyHS1
ttyHS2
ttyHS3
ttyS0
ttyS1
ttyS2
ttyS3
ttyUSB0
ttyUSB1
ttyUSB2
ttyUSB3
ttyUSB4
ttyUSB5
tun
uinput
urandom
usb
usb_accessory
vga_arbiter
wm8903
xt_qtaguid
zero
[email protected]:/ $
Click to expand...
Click to collapse
Many thanks for that, now I can see kernel supports it, so it should be possible to integrate 3G
I'll fix the build later
Cool looking forward to this. Maybe it stops my TF from rebooting when it's unconnected to a power source.
Sent from my Galaxy Nexus using XDA
new build on the first post
still no public source ?
rhaaa said:
still no public source ?
Click to expand...
Click to collapse
I'll provide it when everything is working
It doesn't work. I can't save any APNs because there is no save button.
And if I want to choose the network operator it fails at the search.
Do you need any specific logs?
Nebucatnetzer said:
It doesn't work. I can't save any APNs because there is no save button.
And if I want to choose the network operator it fails at the search.
Do you need any specific logs?
Click to expand...
Click to collapse
A logcat would be nice, when you try to search for networks
ricardopvz said:
A logcat would be nice, when you try to search for networks
Click to expand...
Click to collapse
Et voilà
10 char
Hey everyone. I hope I posted in right section.
I'm trying to port Stock 4.2 Asus ROM from TF300T device. I tried 4 different port method, and last I tried AutoPorter tool, that's the only one that gave me a Almost bootable ROM ( All other method gave me a bootloop on EEPAD Logo )
In fact, now I'm trying to get ride of Bootloop of my ported ROM but I need help, I'm afraid there's something wrong with kernel, and I'm not really good in kernel things.
Anyway, here's the logcat that loop on :
18:26:48.286 Info Netd 32464 Netd 1.0 starting
18:26:48.286 Warning InterfaceController 32464 Warning (Cannot load library: load_library(linker.cpp:771): library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
18:26:48.397 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -N bw_INPUT
18:26:48.397 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -A INPUT -j bw_INPUT
18:26:48.397 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -N fw_INPUT
18:26:48.397 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -A INPUT -j fw_INPUT
18:26:48.397 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -N oem_fwd
18:26:48.397 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -A FORWARD -j oem_fwd
18:26:48.506 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -N fw_FORWARD
18:26:48.506 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -A FORWARD -j fw_FORWARD
18:26:48.506 Info mediaserver 32463 ServiceManager: 0x40a235a0
18:26:48.506 Info AudioFlinger 32463 Using default 3000 mSec as standby time.
18:26:48.506 Info CameraService 32463 CameraService started (pid=32463)
18:26:48.506 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -N bw_FORWARD
18:26:48.506 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -A FORWARD -j bw_FORWARD
18:26:48.506 Error HAL 32463 load: module=/system/lib/hw/camera.tegra.so
18:26:48.506 Error HAL 32463 Cannot load library: soinfo_link_image(linker.cpp:1673): could not load library "libandroid_runtime.so" needed by "camera.tegra.so"; caused by soinfo_relocate(linker.cpp:1013): cannot locate symbol "_ZN7android12AssetManager12addAssetPathERKNS_7String8EPPv" referenced by "libandroid_runtime.so"...
18:26:48.506 Error CameraService 32463 Could not load camera HAL module
18:26:48.506 Info AudioPolicyManagerBase 32463 loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
18:26:48.506 Info AudioFlinger 32463 loadHwModule() Loaded primary audio interface from tf101 audio HW HAL (audio) handle 1
18:26:48.506 Info AudioFlinger 32463 HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
18:26:48.506 Info AudioMixer 32463 found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
18:26:48.506 Info AudioFlinger 32463 Using module 1 has the primary audio interface
18:26:48.506 Info AudioFlinger 32463 AudioFlinger's thread 0x40a3e010 ready to run
18:26:48.507 Warning AudioFlinger 32463 Thread AudioOut_2 cannot connect to the power manager service
18:26:48.507 Debug audio_hw_primary 32463 out_set_parameters:routing=2
18:26:48.507 Debug audio_hw_primary 32463 select_devices+ in=0, out=1
18:26:48.507 Verbose audio_hw_primary 32463 devices=2 active_out=n active_in=n
18:26:48.507 Verbose audio_hw_primary 32463 headphone=0 speaker=2 hdmi=0 isRecording=0
18:26:48.507 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -N natctrl_FORWARD
18:26:48.507 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -A FORWARD -j natctrl_FORWARD
18:26:48.507 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -N oem_out
18:26:48.507 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -A OUTPUT -j oem_out
18:26:48.507 Debug audio_hw_primary 32463 playback
18:26:48.507 Verbose audio_hw_primary 32463 audio_route_apply_path:speaker
18:26:48.507 Debug audio_hw_primary 32463 select_devices-
18:26:48.507 Verbose audio_hw_primary 32463 do_out_standby+
18:26:48.507 Verbose audio_hw_primary 32463 do_out_standby-
18:26:48.507 Info audio_a2dp_hw 32463 adev_open: adev_open in A2dp_hw module
18:26:48.507 Info AudioFlinger 32463 loadHwModule() Loaded a2dp audio interface from A2DP Audio HW HAL (audio) handle 3
18:26:48.507 Error AudioFlinger 32463 int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.usb (No such file or directory)
18:26:48.507 Info AudioFlinger 32463 loadHwModule() error -2 loading module usb
18:26:48.507 Warning AudioPolicyManagerBase 32463 could not open HW module usb
18:26:48.613 Info AudioPolicyService 32463 Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)
18:26:48.613 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -N fw_OUTPUT
18:26:48.613 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -A OUTPUT -j fw_OUTPUT
18:26:48.613 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -N bw_OUTPUT
18:26:48.613 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t filter -A OUTPUT -j bw_OUTPUT
18:26:48.613 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t raw -N bw_raw_PREROUTING
18:26:48.613 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t raw -A PREROUTING -j bw_raw_PREROUTING
18:26:48.613 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t raw -N idletimer_raw_PREROUTING
18:26:48.613 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t raw -A PREROUTING -j idletimer_raw_PREROUTING
18:26:48.722 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t mangle -N bw_mangle_POSTROUTING
18:26:48.722 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t mangle -A POSTROUTING -j bw_mangle_POSTROUTING
18:26:48.722 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t mangle -N idletimer_mangle_POSTROUTING
18:26:48.722 Error Netd 32464 exec() res=768 for /system/bin/ip6tables -t mangle -A POSTROUTING -j idletimer_mangle_POSTROUTING
18:26:48.832 Error BandwidthController 32464 runIptablesCmd(): failed /system/bin/ip6tables -N costly_shared res=768
18:26:48.832 Error BandwidthController 32464 runIptablesCmd(): failed /system/bin/ip6tables -A bw_INPUT -i lo --jump RETURN res=768
18:26:48.832 Error Netd 32464 Unable to create netlink socket: Protocol not supported
18:26:48.832 Error Netd 32464 Unable to open quota2 logging socket
18:26:48.832 Debug MDnsDS 32464 MDnsSdListener::Hander starting up
18:26:48.832 Debug MDnsDS 32464 MDnsSdListener starting to monitor
18:26:48.832 Debug MDnsDS 32464 Going to poll with pollCount 1
18:26:53.420 Info ServiceManager 101 service 'media.audio_policy' died
18:26:53.420 Info ServiceManager 101 service 'media.audio_flinger' died
18:26:53.420 Info ServiceManager 101 service 'media.player' died
18:26:53.420 Info ServiceManager 101 service 'media.camera' died
18:26:53.420 Info Netd 851 Netd 1.0 starting
Click to expand...
Click to collapse
Maybe someone may know what's wrong, I saw this error on many port try, but didnt find any answer yet.
FYI
Here's the ROM I used for port : http://forum.xda-developers.com/showthread.php?t=2252329
And I used josteink CM10 nighlty as base.
I can upload my current port if someone request it.
.
Thanks in advance for further answer
Hmm, I am just going to ask WHY?
Not sure what the stock TF300T ROM has that the other (non-stock) TF101 4.2 ROMs lack. Maybe you could enlighten me.
I am running KatKiss and the only things lacking is that my front camera locks up, and I do not have Face Unlock (which I could care less about). I can get the front camera working if I flash a different GAPPs that does not have photosphere in it.
frederuco said:
Hmm, I am just going to ask WHY?
Not sure what the stock TF300T ROM has that the other (non-stock) TF101 4.2 ROMs lack. Maybe you could enlighten me.
I am running KatKiss and the only things lacking is that my front camera locks up, and I do not have Face Unlock (which I could care less about). I can get the front camera working if I flash a different GAPPs that does not have photosphere in it.
Click to expand...
Click to collapse
The answer is simple as that : I like Asus stock style and apps, and I would love see it on a 4.2 ROM.
Kingzak34 said:
The answer is simple as that : I like Asus stock style and apps, and I would love see it on a 4.2 ROM.
Click to expand...
Click to collapse
read the logcat carefully you are missing libandroid_runtime.so and some other libs for tegra you can pull from CM ( I have done this on the S3 poring Sense 5)
zachf714 said:
read the logcat carefully you are missing libandroid_runtime.so and some other libs for tegra you can pull from CM ( I have done this on the S3 poring Sense 5)
Click to expand...
Click to collapse
The problem is that this lib is present and pulled from CM others too
Kingzak34 said:
The problem is that this lib is present and pulled from CM others too
Click to expand...
Click to collapse
What kernel are you using then, might I ask
Sent from my SCH-I535 using Tapatalk 4
zachf714 said:
What kernel are you using then, might I ask
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
The CM one
Kingzak34 said:
The CM one
Click to expand...
Click to collapse
Have you done any modifications to it
Sent from my SCH-I535 using Tapatalk 4
zachf714 said:
Have you done any modifications to it
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Nope bootclasspath were the same but maybe I made a mistake
Envoyé depuis mon Nexus 4 MIUI !
Kingzak34 said:
Nope bootclasspath were the same but maybe I made a mistake
Envoyé depuis mon Nexus 4 MIUI !
Click to expand...
Click to collapse
Maybe check the init.rc files .. My biggest fear would be you or both of us having to hex edit the h*ll out off all the libs because they are for a different board spec
Sent from my SCH-I535 using Tapatalk 4
zachf714 said:
Maybe check the init.rc files .. My biggest fear would be you or both of us having to hex edit the h*ll out off all the libs because they are for a different board spec
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
When i got time I'll check again for bootclasspath
Maybe I missed something
Envoyé depuis mon Nexus 4 MIUI !
I can upload my work if you are interested
Kingzak34 said:
The answer is simple as that : I like Asus stock style and apps, and I would love see it on a 4.2 ROM.
Click to expand...
Click to collapse
I like Asus stock style too that's the reason I'm still running 4.0.3. Are there any Asus stock 4.0.4 rom out there currently? I can't find it.
Wish you good luck on JB rom.
Kingzak34 said:
I can upload my work if you are interested
Click to expand...
Click to collapse
Yes man
Sent from my SCH-I535 using Tapatalk 4
TheEndHK said:
I like Asus stock style too that's the reason I'm still running 4.0.3. Are there any Asus stock 4.0.4 rom out there currently? I can't find it.
Wish you good luck on JB rom.
Click to expand...
Click to collapse
I dont think there is one.
zachf714 said:
Yes man
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I'll do ASAP, anyway, thanks for trying to help
zachf714 said:
Yes man
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Note : You may have to re partitionate you device, ROM size is bigger than our system partition if you want to use it ( I made my system partition 800MB )
Kingzak34 said:
Note : You may have to re partitionate you device, ROM size is bigger than our system partition if you want to use it ( I made my system partition 800MB )
Click to expand...
Click to collapse
I think that may be part of the problem, try symlinking some of it to /data
Sent from my SCH-I535 using Tapatalk 4
zachf714 said:
I think that may be part of the problem, try symlinking some of it to /data
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I dont need I repartitionated my tab with Tubuntu app, editing default.cfg
Everything works well and I've a 800MB /system partition
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It shouldnt be a problem now ?
Kingzak34 said:
I dont need I repartitionated my tab with Tubuntu app, editing default.cfg
Everything works well and I've a 800MB /system partition
It shouldnt be a problem now ?
Click to expand...
Click to collapse
It has to do with the kernel and how the tegra 2 loads the system ( I have ported sense 4 to the droid inc and sense 5 to the S3)
Sent from my SCH-I535 using Tapatalk 4
zachf714 said:
It has to do with the kernel and how the tegra 2 loads the system ( I have ported sense 4 to the droid inc and sense 5 to the S3)
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
WHat does it mean ?
( Every ROM works as it should )
I'm wanting to add a borescope to my Nexus and realize that not all of them are compatible. I've purchased a USB model that is not compatible even after a jailbreak so I was hoping someone has had the opportunity to test any that are compatible?
I purchased the following:
ebay item: 141214106067
and was looking at the following since it appears to have a USB2.0 UVC interface
ebay item: 111107144638
Any help or guidance would be appreciated..
VB,
I managed to pry out the following information from the command line
#dmesg | grep video
Linux Video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
uvcvideo: Found UVC 1.00 device USB camera (0bda:5801)
I believe this means the my USB camera is already using the UVC driver in attempt to work properly..
Anyone have any suggestions on how to possibly get this to work?
Actually looks like its supported at Linux UVC
0bda:5801 Realtek 2SF022 (HP Pavillon DV7 4151SG notebooks) Realtek
Continuing to dig and finding this in dmesg- firewalled???
130|[email protected]:/ # dmesg | grep video
<6>[ 7539.970855] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<6>[ 8885.732574] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<5>[ 8917.306060] type=1400 audit(1398128520.701:44): avc: denied { getattr } for pid=5504 comm="ra.simplewebcam" path="/dev/video0" dev="tmpfs" ino=7536 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:video_device:s0 tclass=chr_file
<6>[ 9269.163787] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<6>[ 9537.000366] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<5>[ 9575.854766] type=1400 audit(1398129235.463:47): avc: denied { getattr } for pid=6112 comm="ra.simplewebcam" path="/dev/video0" dev="tmpfs" ino=7536 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:video_device:s0 tclass=chr_file
<6>[ 9686.335266] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<6>[ 9902.219024] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<5>[ 9994.940917] type=1400 audit(1398129654.551:48): avc: denied { read write } for pid=6406 comm="ra.simplewebcam" name="video0" dev="tmpfs" ino=7536 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:video_device:s0 tclass=chr_file
<5>[ 9994.941192] type=1400 audit(1398129654.551:49): avc: denied { open } for pid=6406 comm="ra.simplewebcam" name="video0" dev="tmpfs" ino=7536 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:video_device:s0 tclass=chr_file
<6>[10049.950195] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
I've temporarily disabled SELinux.. still no luck but the avc: denied errors are gone.
It looks like there is a device conflict as it seems to not be able to open the /dev/video0?
Anyone have any thoughts?
D/dalvikvm( 2962): Trying to load lib /data/app-lib/com.camera.simplewebcam-1/libImageProc.so 0x41ea2f78
D/dalvikvm( 2962): Added shared lib /data/app-lib/com.camera.simplewebcam-1/libImageProc.so 0x41ea2f78
D/dalvikvm( 2962): No JNI_OnLoad found in /data/app-lib/com.camera.simplewebcam-1/libImageProc.so 0x41ea2f78, skipping init
D/dalvikvm( 2962): GC_FOR_ALLOC freed 71K, 2% free 9181K/9284K, paused 17ms, total 17ms
I/dalvikvm-heap( 2962): Grow heap (frag case) to 10.166MB for 1228816-byte allocation
D/dalvikvm( 2962): GC_FOR_ALLOC freed 1K, 2% free 10380K/10488K, paused 14ms, total 14ms
E/TEST ( 2962): Cannot open '/dev/video0': 16, Device or resource busy
D/dalvikvm( 2962): GC_CONCURRENT freed <1K, 2% free 10381K/10488K, paused 3ms+2ms, total 18ms
I/ActivityManager( 590): Displayed com.camera.simplewebcam/.Main: +211ms
I'm guessing this has something to do with the 2 built in camera's... not sure if they can be temporarily disabled or somehow mount the USB camera on another /dev maybe like /dev/video3?
making very little progress but I think I know what's going on.. the USB device is being loaded as /dev/video3 and not as /dev/video0 which I assume is what most applications are looking for.
This was me plugging and unplugging the camera. I believe this also tells me that the kernel already is set for the camera.
[email protected]:/ # ls -l /dev/v*
crw-rw---- system camera 81, 1 2014-04-22 21:54 v4l-subdev0
crw-rw---- system camera 81, 2 2014-04-22 21:54 v4l-subdev1
crw-rw---- system camera 81, 3 2014-04-22 21:54 v4l-subdev2
crw-rw---- system camera 81, 4 2014-04-22 21:54 v4l-subdev3
crw-rw---- system camera 81, 5 2014-04-22 21:54 v4l-subdev4
crw-rw---- system camera 81, 7 2014-04-22 21:54 v4l-subdev5
crw-rw---- system camera 81, 9 2014-04-22 21:54 v4l-subdev6
crw-rw---- system camera 81, 10 2014-04-22 21:54 v4l-subdev7
crw-rw---- system camera 81, 11 2014-04-22 21:54 v4l-subdev8
crw-rw---- system camera 81, 12 2014-04-22 21:54 v4l-subdev9
crw------- root root 7, 0 2014-04-22 21:54 vcs
crw------- root root 7, 1 2014-04-22 21:54 vcs1
crw------- root root 7, 128 2014-04-22 21:54 vcsa
crw------- root root 7, 129 2014-04-22 21:54 vcsa1
crw------- root root 10, 127 2014-04-22 21:54 vga_arbiter
crw-rw---- system camera 81, 0 2014-04-22 21:54 video0
crw-rw---- system camera 81, 6 2014-04-22 21:54 video1
crw-rw---- system camera 81, 8 2014-04-22 21:54 video2
[email protected]:/ # ls -l /dev/v*
crw-rw---- system camera 81, 1 2014-04-22 21:54 v4l-subdev0
crw-rw---- system camera 81, 2 2014-04-22 21:54 v4l-subdev1
crw-rw---- system camera 81, 3 2014-04-22 21:54 v4l-subdev2
crw-rw---- system camera 81, 4 2014-04-22 21:54 v4l-subdev3
crw-rw---- system camera 81, 5 2014-04-22 21:54 v4l-subdev4
crw-rw---- system camera 81, 7 2014-04-22 21:54 v4l-subdev5
crw-rw---- system camera 81, 9 2014-04-22 21:54 v4l-subdev6
crw-rw---- system camera 81, 10 2014-04-22 21:54 v4l-subdev7
crw-rw---- system camera 81, 11 2014-04-22 21:54 v4l-subdev8
crw-rw---- system camera 81, 12 2014-04-22 21:54 v4l-subdev9
crw------- root root 7, 0 2014-04-22 21:54 vcs
crw------- root root 7, 1 2014-04-22 21:54 vcs1
crw------- root root 7, 128 2014-04-22 21:54 vcsa
crw------- root root 7, 129 2014-04-22 21:54 vcsa1
crw------- root root 10, 127 2014-04-22 21:54 vga_arbiter
crw-rw---- system camera 81, 0 2014-04-22 21:54 video0
crw-rw---- system camera 81, 6 2014-04-22 21:54 video1
crw-rw---- system camera 81, 8 2014-04-22 21:54 video2
crw-rw---- system camera 81, 14 2014-04-22 21:56 video3
[email protected]:/ # ls -l /dev/v*
crw-rw---- system camera 81, 1 2014-04-22 21:54 v4l-subdev0
crw-rw---- system camera 81, 2 2014-04-22 21:54 v4l-subdev1
crw-rw---- system camera 81, 3 2014-04-22 21:54 v4l-subdev2
crw-rw---- system camera 81, 4 2014-04-22 21:54 v4l-subdev3
crw-rw---- system camera 81, 5 2014-04-22 21:54 v4l-subdev4
crw-rw---- system camera 81, 7 2014-04-22 21:54 v4l-subdev5
crw-rw---- system camera 81, 9 2014-04-22 21:54 v4l-subdev6
crw-rw---- system camera 81, 10 2014-04-22 21:54 v4l-subdev7
crw-rw---- system camera 81, 11 2014-04-22 21:54 v4l-subdev8
crw-rw---- system camera 81, 12 2014-04-22 21:54 v4l-subdev9
crw------- root root 7, 0 2014-04-22 21:54 vcs
crw------- root root 7, 1 2014-04-22 21:54 vcs1
crw------- root root 7, 128 2014-04-22 21:54 vcsa
crw------- root root 7, 129 2014-04-22 21:54 vcsa1
crw------- root root 10, 127 2014-04-22 21:54 vga_arbiter
crw-rw---- system camera 81, 0 2014-04-22 21:54 video0
crw-rw---- system camera 81, 6 2014-04-22 21:54 video1
crw-rw---- system camera 81, 8 2014-04-22 21:54 video2
[email protected]:/ #
Found an interesting thread where I believe the developer is trying to make the USB camera /dev/video0... I'd post the URL but I've only posted 7 times to the forum.
sorry... gonna post a few more time to meet the 10 post limit to post URL's... and I have to wait 5 minutes between posts.. a bit on the paranoid side around here..
Gonna try flashing a zip file.. of a potential fix?
Backing up my device.. post #9
Device done backing up..
Here is the URL:
http://forum.xda-developers.com/showthread.php?t=2100452&page=4
Anyone know if this is still a working solution?
Wow.. no suggestions or reply's to this thread. Huge bummer..
Still digging around and seeing some noise about using the /system/etc/nvcamera.conf file however that file is not on my Nexus 7? I trieed creating one but not sure its being read.. maybe it is. Anyway, it didn't work..
Need to make /system directory read/write:
# mount -o rw,remount /system
# vi /etc/nvcamera.conf# format, cameraName=device,direction,orientation,type
This is the file before mods
# type can be 'stereo' for stereo capable, 'mono' for not stereo capable,
# 'usb' to enable searching for a usb device and where to put it in the list
# if found. Lines must be shorter then 256 characters
version=1
camera0=/dev/ov5640,back,0,mono
#camera1=/dev/ov5650,back,0,mono // 2nd camera for stereo once supported
camera1=/dev/mi1040,front,0,mono
#camera4=/dev/ov5650,back,0,stereo // virtual stereo device once supported
Change this line:
camera0=/dev/ov5640,back,0,mono
to:
camera0=/dev/ov5640,front,0,mono
And this line:
camera1=/dev/mi1040,front,0,mono
to:
camera1=/dev/mi1040,back,0,mono
Click to expand...
Click to collapse
I could really use some help with this.. anyone?
Just wanted to close the loop and let the forum know that I got my generic borescope working on my Nexus via the USB port, I did have to root it but might not have had to assuming I could give permissions of /ueventd.xxxx.rc set to 0666. SInce its rooted its a moot point..
I also modified the source code for simplewebcam (https://bitbucket.org/droidperception/simplewebcam/overview)
VB,
Maybe you've thought, "Oh, if only I had GPS on me ereader I could have it log locations so that it could tell me exactly where I read the last page of Jane Eyre".
Or you could use it for hiking/mapping applications.
I presume that this thread will be more for amusement than actual instruction.
I have a Glow3. I prefer Glow2's for normal reading.
I have a GPS module, the GP-2106.
It's small, not being sold anymore.
The lower corner of the Glow3 PCB is only ground plane with no traces.
You can cut out a bunch of it, then you have about 1/4" depth to put stuff.
The only accessible UART is UART4 (/dev/ttymxc3) since we want to keep the original console in place.
That UART is not already configured or existing as a /dev/
The GP-2106 uses 1.8V interfaces and supply.
I modified the kernel (not rebuilt, just hex modified) to initialize UART4.
I stole 1.8V power supply off a bus.
Currently I am using this directly in an application and not implemented as a LocationProvider (yet).
I have a JNI NDK thread that reads the NMEA data and parses it.
Shown is my own little hiking app that uses my own KML maps.
(On other devices I use this with the standard built-in LocationProvider.)
Yes, the grab is in color, although the Nook is obviously black & white.
That's a bit of a con, but the visibility in bright sunlight is a plus.
So, I took a look at how the whole Android GPS worked.
In the Secure settings you have:
location_providers_allowed = gps
location_mode = 3 (3 = high accuracy, 0 = off)
In /system/framework/framework.jar is android.location.LocationManager
In /system/framework/services.jar is com.android.server.location.GpsLocationProvider
This tries to read /etc/gps.conf (which gives you network resources like NTP and is not strictly required, it's not present)
This uses native code like "native_agps_..." in:
/system/lib/libandroid_servers.so
This uses hw_get_module() in:
/system/lib/libhardware.so
Which uses a search for hardware HAL modules to load, like
/system/lib/hw/gps.default.so
Which does not exist on our Glows
I made a junk file and libhardware.so does try to load it (and fails)
Code:
E/HAL ( 2461): load: module=/system/lib/hw/gps.default.so
E/HAL ( 2461): dlopen failed: "/system/lib/hw/gps.default.so" is too small to be an ELF executable
There are some projects out there for building a generic gps.default.so
FWIW, the whole meat of GPS is in this file, i.e. NMEA decoders, callbacks...
I'll be trying to do that later.
Edit: Well, I built a gps.default.so and it seems to work fine, but somewhere along the way I misplaced my serial port.
In any case:
Code:
GPS: [email protected]
Renate NST said:
So, I took a look at how the whole Android GPS worked.
In the Secure settings you have:
location_providers_allowed = gps
location_mode = 3 (3 = high accuracy, 0 = off)
In /system/framework/framework.jar is android.location.LocationManager
In /system/framework/services.jar is com.android.server.location.GpsLocationProvider
This tries to read /etc/gps.conf (which gives you network resources like NTP and is not strictly required, it's not present)
This uses native code like "native_agps_..." in:
/system/lib/libandroid_servers.so
This uses hw_get_module() in:
/system/lib/libhardware.so
Which uses a search for hardware HAL modules to load, like
/system/lib/hw/gps.default.so
Which does not exist on our Glows
I made a junk file and libhardware.so does try to load it (and fails)
Code:
E/HAL ( 2461): load: module=/system/lib/hw/gps.default.so
E/HAL ( 2461): dlopen failed: "/system/lib/hw/gps.default.so" is too small to be an ELF executable
There are some projects out there for building a generic gps.default.so
FWIW, the whole meat of GPS is in this file, i.e. NMEA decoders, callbacks...
I'll be trying to do that later.
Edit: Well, I built a gps.default.so and it seems to work fine, but somewhere along the way I misplaced my serial port.
In any case:
Code:
GPS: [email protected]
Click to expand...
Click to collapse
Hi Renate !
I was off grid for some time, so i 'm just taking known of your work. Quite impressive, again.
It's look like a very good news, so you made a custom gps.default.so from scratch ?
not sure to undersand perfectly what you mean about misplaced the seral port, but existing projects about generic serial driver seem use directive based from build.prop like this :
Code:
# Custom GPS driver
ro.kernel.android.gps=ttyS1
ro.kernel.android.gps.speed=9600
ro.kernel.android.gps.max_rate=1
BTW you have make a great improvement of GPS support on the NST !
let us know when you will able to release your work
See you later !
liptonthe said:
misplaced the seral port...
Click to expand...
Click to collapse
Oh, I lost track of where the patches for ttymxc3 were.
I found them, tried the built gps.default.so and it was eating all the CPU.
I'll have to do some debugging.
(The GPS module is pretty crappy, slowest fix that I've ever seen.)
Renate NST said:
Oh, I lost track of where the patches for ttymxc3 were.
I found them, tried the built gps.default.so and it was eating all the CPU.
I'll have to do some debugging.
(The GPS module is pretty crappy, slowest fix that I've ever seen.)
Click to expand...
Click to collapse
All right, i guess it would be too easy that work at the first attempt.
But at least it's a progress, i can relate, UsbGps4Droid is not really a fast fix solution too !
Hi @Renate NST, what's up
Did you fix your issue about CPU comsumtion ?
i'm still interessted to try it on my BNRV300 if you want.
See you later.
liptonthe said:
I'm still interested to try it on my BNRV300 if you want.
Click to expand...
Click to collapse
Yeah, the NST gives you a choice of 1.8V or 3.3V also.
I've been busy on other stuff, but I should get back to this.
Renate NST said:
Yeah, the NST gives you a choice of 1.8V or 3.3V also.
I've been busy on other stuff, but I should get back to this.
Click to expand...
Click to collapse
Hi, Okay thats a good news
i'm availble for trying binary's and confs. Let me know when you are ready.
I realized what the problem was with the lost /dev/ttymxc3
I had bodged it into where the Bluetooth goes and it only worked if you had the WiFi on.
I knew this, but I forgot it.
I've got that working a different way now (but I managed to disable the console accidentally).
So now I'm back to something eating all my CPU.
And the stupid GPS module still hasn't gotten a fix after 15 minutes.
Renate NST said:
I realized what the problem was with the lost /dev/ttymxc3
I had bodged it into where the Bluetooth goes and it only worked if you had the WiFi on.
I knew this, but I forgot it.
I've got that working a different way now (but I managed to disable the console accidentally).
So now I'm back to something eating all my CPU.
And the stupid GPS module still hasn't gotten a fix after 15 minutes.
Click to expand...
Click to collapse
Hi Renate !
It look like i have missed the notification of your last response the 10/03..
I'm working myself on the implementation of the gps.default.so from this project : https://github.com/dipcore/gps-glonass-android-driver
i have pushed + chmod the gps.default.so lib in /system/lib/hw/ and edited the /system/build.prop to add :
Code:
# Custom GPS driver
ro.kernel.android.gps=ttyS1
ro.kernel.android.gps.speed=9600
ro.kernel.android.gps.max_rate=1
But actually i'm not able to see anything loading in logcat or dmesg for the moment.
Maybe you could try yourself with this lib ?
---------- Post added at 11:12 PM ---------- Previous post was at 10:35 PM ----------
Actually i set this value but it's not better.
Code:
sqlite> update secure set value=3 where name='location_mode';
sqlite> update secure set value=0 where name='mock_location';
sqlite> update secure set value='gps' where name='location_providers_allowed';
gps.default.so should be natively loaded by HAL scanner as described in the /system/lib/libhardware.so but i don't see it in logs.
Perhaps
Code:
ls /sys/module
seem show the loading of a "garmin_gps" module
Still loaded when gps.default.so is no present in the system, that's strange !
Code:
# ls /sys/module
kernel
printk
wakelock
userwakelock
earlysuspend
spurious
omap3epfb
keyboard
vt
bridgedriver
scsi_mod
sg
usbcore
usb_storage
usbserial
aircable
ark3116
belkin_sa
ch341
cp2101
cyberjack
cypress_m8
digi_acceleport
io_edgeport
io_ti
empeg
ftdi_sio
funsoft
[B]garmin_gps[/B] <---------------
ipaq
ipw
ir_usb
iuu_phoenix
keyspan
keyspan_pda
kl5kusb105
kobil_sct
mct_u232
mos7720
mos7840
navman
omninet
opticon
option
oti6858
pl2303
safe_serial
sierra
spcp8x5
ti_usb_3410_5052
visor
whiteheat
adutux
berry_charge
iowarrior
ldusb
legousbtower
usbtest
musb_hdrc
mousedev
psmouse
omap_hdq
w1_bq27000
usbhid
binder
lowmemorykiller
snd
snd_timer
snd_pcm
snd_dummy
snd_usb_audio
oprofile
rfkill
pvrsrvkm
omaplfb
bc_example
tiwlan_drv
It loads and correctly accesses the GPS module and decodes the NMEA correctly.
You can see that if you edit gps.h and rebuild it.
Code:
#define GPS_DEBUG 1
//#undef GPS_DEBUG
(You get lots more messages.)
My stupid GPS module was being so annoying. It would take 20 minutes to capture.
I've been looking for a new module, but all the small ones use a stupid scheme where pulsing a pin cycles it through various modes.
You can never tell what mode you're in.
In any case, I was still left with the Android world not getting GPS updates and "top" was showing 99% CPU.
Does yours react this way?
Renate NST said:
It loads and correctly accesses the GPS module and decodes the NMEA correctly.
You can see that if you edit gps.h and rebuild it.
Code:
#define GPS_DEBUG 1
//#undef GPS_DEBUG
(You get lots more messages.)
Click to expand...
Click to collapse
Hum great tips ! I've been able to find and edit the .h file but i'm not common with the rebuilt / compile process of C programs.
did you use GCC, make and stuff to do that ?
In any case, I was still left with the Android world not getting GPS updates and "top" was showing 99% CPU.
Does yours react this way?
Click to expand...
Click to collapse
A quick look on "top" was not showing an overstimulated CPU, maybe it's due to the debug params.
---------- Post added at 02:03 AM ---------- Previous post was at 01:55 AM ----------
I'm using a little app to get somes indicatives values about GPS data.
--> https://apkpure.com/just-gps/net.thenumber42.android.justgps
When i launch it i get a pop-up about "The GPS is not enabled" however i have set the settings.db properly.
This app is running like charm when i use the moc location trick.
Maybe i missed something, when this app is launched the result in logcat is :
Code:
E/LocationManagerService( 1026): requestUpdates got exception:
E/LocationManagerService( 1026): java.lang.IllegalArgumentException: provider=gps
E/LocationManagerService( 1026): at com.android.server.LocationManagerService.requestLocationUpdatesLocked(LocationManagerService.java:863)
E/LocationManagerService( 1026): at com.android.server.LocationManagerService.requestLocationUpdates(LocationManagerService.java:833)
E/LocationManagerService( 1026): at android.location.ILocationManager$Stub.onTransact(ILocationManager.java:79)
E/LocationManagerService( 1026): at android.os.Binder.execTransact(Binder.java:287)
E/LocationManagerService( 1026): at com.android.server.SystemServer.init1(Native Method)
E/LocationManagerService( 1026): at com.android.server.SystemServer.main(SystemServer.java:514)
E/LocationManagerService( 1026): at java.lang.reflect.Method.invokeNative(Native Method)
E/LocationManagerService( 1026): at java.lang.reflect.Method.invoke(Method.java:521)
E/LocationManagerService( 1026): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/LocationManagerService( 1026): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/LocationManagerService( 1026): at dalvik.system.NativeStart.main(Native Method)
I/PowerManagerService( 1026): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=2
E/LocationManagerService( 1026): isProviderEnabled got exception:
E/LocationManagerService( 1026): java.lang.IllegalArgumentException: provider=gps
E/LocationManagerService( 1026): at com.android.server.LocationManagerService._isProviderEnabledLocked(LocationManagerService.java:1387)
E/LocationManagerService( 1026): at com.android.server.LocationManagerService.isProviderEnabled(LocationManagerService.java:1361)
E/LocationManagerService( 1026): at android.location.ILocationManager$Stub.onTransact(ILocationManager.java:237)
E/LocationManagerService( 1026): at android.os.Binder.execTransact(Binder.java:287)
E/LocationManagerService( 1026): at dalvik.system.NativeStart.run(Native Method)
---------- Post added at 02:31 AM ---------- Previous post was at 02:03 AM ----------
Also i just found this project dedicated to generic serial GPS driver : https://tinkerboarding.co.uk/forum/thread-671.html && https://github.com/joerg65/libGPS_TinkerBoard
Hmm, do you have secure / location_providers_allowed=gps
My GPS is working (when the GPS module finally captures).
The CPU being eaten is possibly unrelated.
It's the Alarm Manager spamming on an alarm set for the year 2000!
It may be trying to set the time constantly.
If I delete gps.default.so it stops.
But, in any case, the clock is not even syncing to the NMEA.
I tried the beaglebone one, it builds fine and does about the same. Oops, I was rebuilding the first one.
Renate NST said:
Hmm, do you have secure / location_providers_allowed=gps
Click to expand...
Click to collapse
I think it should be good, there is my setup sequence :
Code:
adb connect xxx.xxx.x.x:5555
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push gps.default.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/gps.default.so
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update secure set value=3 where name='location_mode';
update secure set value=0 where name='mock_location';
update secure set value='gps' where name='location_providers_allowed';
.q
reboot
But my apps (Oruxmaps or Just GPS) still saying GPS is disabled :/
My GPS is working (when the GPS module finally captures).
Click to expand...
Click to collapse
I'm happy to ear that ! A great improvement I hope reproducing it too.
The CPU being eaten is possibly unrelated.
It's the Alarm Manager spamming on an alarm set for the year 2000!
It may be trying to set the time constantly.
If I delete gps.default.so it stops.
Click to expand...
Click to collapse
A really strange glitch..
But yes it's could be the time updating system, but the alarm.. this is really strange.
But, in any case, the clock is not even syncing to the NMEA.
Click to expand...
Click to collapse
That's strange because that should be updated ! maybe this is a linked to the high power consumtion (infinite retry of time setup after failed attempt ?)
I tried the beaglebone one, it builds fine and does about the same. Oops, I was rebuilding the first one.
Click to expand...
Click to collapse
I'm not sure to understand, do you try the other GPS project's lib ?
---------- Post added at 12:26 AM ---------- Previous post was at 12:24 AM ----------
Maybe you could share me the lib you recompile with log enabled ?
---------- Post added at 12:50 AM ---------- Previous post was at 12:26 AM ----------
It seem this command has no effect in my case :
Code:
sqlite> update secure set value=3 where name='location_mode';
I can't see it in the DB
Code:
sqlite> select * from secure;
1|android_id|1e70509c-cb20-4b12-8ce2-2a3fce741da9
2|bluetooth_on|0
3|data_roaming|1
4|install_non_market_apps|1
5|location_providers_allowed|gps
6|assisted_gps_enabled|1
7|network_preference|1
8|usb_mass_storage_enabled|1
11|wifi_networks_available_notification_on|0
12|preferred_network_mode|0
13|cdma_cell_broadcast_sms|1
14|preferred_cdma_subscription|1
15|mock_location|0
16|backup_enabled|0
17|backup_transport|
18|demo_mode|off
19|wifi_max_restart_supplicant_attempts|3
20|enabled_input_methods|com.android.inputmethod.latin/.LatinIME
26|device_provisioned|1
274|wifi_on|1
277|default_input_method|com.android.inputmethod.latin/.LatinIME
278|adb_enabled|0
sqlite>
---------- Post added at 01:17 AM ---------- Previous post was at 12:50 AM ----------
I just create a row mannualy in the DB.
But i still gett "GPS disabled in apps"
Code:
insert into secure (name) VALUES('location_mode');
Code:
select * from secure;
...
279|location_mode|3
...
Hello @Renate NST
I've retry to setup the gps library on a brand new NST BNRV300 from ebay this week to create an second topographic eReader like mine.
The result is the same i'm stuck with the gps.default.so, i don't know how to rebuilt it to integrate debug and check if it's loaded correctly. On the other hand it seem the OS has not GPS settings enabled. (But my params has been pushed successfully by sqlite). i'm really confused about that point.
I'm still getting thoses errors in logcat when i'm launching an app with GPS location needs :
Code:
E/LocationManagerService( 822): requestUpdates got exception:
E/LocationManagerService( 822): java.lang.IllegalArgumentException: provider=gps
E/LocationManagerService( 822): at com.android.server.LocationManagerService.requestLocationUpdatesLocked(LocationManagerService.java:863)
E/LocationManagerService( 822): at com.android.server.LocationManagerService.requestLocationUpdates(LocationManagerService.java:833)
E/LocationManagerService( 822): at android.location.ILocationManager$Stub.onTransact(ILocationManager.java:79)
E/LocationManagerService( 822): at android.os.Binder.execTransact(Binder.java:287)
E/LocationManagerService( 822): at dalvik.system.NativeStart.run(Native Method)
I/PowerManagerService( 822): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=2
E/LocationManagerService( 822): isProviderEnabled got exception:
E/LocationManagerService( 822): java.lang.IllegalArgumentException: provider=gps
E/LocationManagerService( 822): at com.android.server.LocationManagerService._isProviderEnabledLocked(LocationManagerService.java:1387)
E/LocationManagerService( 822): at com.android.server.LocationManagerService.isProviderEnabled(LocationManagerService.java:1361)
E/LocationManagerService( 822): at android.location.ILocationManager$Stub.onTransact(ILocationManager.java:237)
E/LocationManagerService( 822): at android.os.Binder.execTransact(Binder.java:287)
E/LocationManagerService( 822): at dalvik.system.NativeStart.run(Native Method)
I guess the glowlight 3 you are using has some differences about that in the firmware.
Do you have an opinion on that ?
##### Other Subject #####
I just read your thread about the SD card soldering perfomed on Glows 2/3/4 and it's very interesting
I will maybe buy a BNRV510 (Glow2) and try to reproduce the SD card mod but also soldering a GPS on the UART. I'm not totally sure but i guess it will be easier to make it work natively with a 4.4 Android OS.
The BNRV510 is waterproof, has SD card (after mod) and an UART serial input so it's a good setup for me but i'm not aware about what expect.
Advices ?
By the way, thank's for your time !
Yeah, I've got to get back on this.
I had tried the two different sources for gps.default.so, the one with a bunch of files, the one with one big source file.
I'm just building them using the stock Android NDK toolchain.
The bunch-of build is detected as GPS but it does weird stuff like using NaN for no fix and I think it's reporting erroneous time which drives the AlarmManager crazy and eats CPU.
The big-file build is not recognized as GPS. I haven't really looked at it, but it doesn't touch the serial port at all.
When troubleshooting it helps to look at the serial port and see if the driver has set baud rate and characteristics.
Code:
# busybox stty -F /dev/ttymxc3
(Or whichever your device is.)
You should be able to cat it and see NMEA sentences. (Although it "steals" the text while you are doing this.)
Code:
# cat /dev/ttymxc3
Are you sure that your serial port is accessible?
I added this to ueventd.rc
Code:
/dev/ttymxc3 0666 root root
Adding an SD card on the Glow2 & Glow4 is easy.
The Glow3 needs a kernel mod and/or NTX hwcfg mod.
Oh! I see a problem with my build of the single-source gps.default.so:
Code:
E/HAL ( 2454): dlopen failed: cannot locate symbol "floor" referenced by "gps.default.so"...
Interesting, the other one didn't use math.
Also, I had to patch the source to understand 4800 baud, slow, but the official baud for NMEA-0183.
So, here's gps.default.txt, just rename it gps.default.so (it's not zipped or anything).
MD5=4c3eb7408a1ef94ec90ea44d045b7df2
The setup goes in /system/etc/gps.conf (not in build.prop like the other one).
Code:
GPSPORT /dev/ttymxc3
GPSSPEED 4800
Renate NST said:
When troubleshooting it helps to look at the serial port and see if the driver has set baud rate and characteristics.
Code:
# busybox stty -F /dev/ttymxc3
(Or whichever your device is.)
Click to expand...
Click to collapse
Yes, the GP-735 is running well at 9600 baud on ttyS1 in my case :
Code:
# busybox stty -F /dev/ttyS1
speed 9600 baud;
Renate NST said:
You should be able to cat it and see NMEA sentences. (Although it "steals" the text while you are doing this.)
Code:
# cat /dev/ttymxc3
Click to expand...
Click to collapse
Yeap this is work perfectly too, i'm able to see NMEA sentences :
Code:
# cat /dev/ttyS1
$GPRMC,224350.00,V,,,,,,,271120,,,N*78
$GPVTG,,,,,,,,,N*30
$GPGGA,224350.00,,,,,0,00,99.99,,,,,,*64
$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
$GPGSV,1,1,02,26,,,33,30,,,24*7A
$GPGLL,,,,,224350.00,V,N*48
Renate NST said:
Are you sure that your serial port is accessible?
I added this to ueventd.rc
Code:
/dev/ttymxc3 0666 root root
Click to expand...
Click to collapse
Yes it was 0660, but worked perfectly with the UsbGps app.
But i changed it to try with 0666, it seem not changing the matter.
Renate NST said:
Adding an SD card on the Glow2 & Glow4 is easy.
The Glow3 needs a kernel mod and/or NTX hwcfg mod.
Click to expand...
Click to collapse
This is a very good news, do you think the UART serial port is also ready to use on the Glow2 ?
Renate NST said:
Oh! I see a problem with my build of the single-source gps.default.so:
Code:
E/HAL ( 2454): dlopen failed: cannot locate symbol "floor" referenced by "gps.default.so"...
Interesting, the other one didn't use math.
Also, I had to patch the source to understand 4800 baud, slow, but the official baud for NMEA-0183.
So, here's gps.default.txt, just rename it gps.default.so (it's not zipped or anything).
MD5=4c3eb7408a1ef94ec90ea44d045b7df2
The setup goes in /system/etc/gps.conf (not in build.prop like the other one).
Code:
GPSPORT /dev/ttymxc3
GPSSPEED 4800
Click to expand...
Click to collapse
Thank's you, i have tried with the gps.default.so an gps.conf you provide (but with adapted params).
I'm not able to see anything in logcat or dmesg at this time. But the error about GPS not enabled in Android still present.
This last error is not a problem with the lib for sure but with the android system itself about his settings parameters. I will continue to try things with the settings.db
Since you're using the default of 9600 that won't tell you anything.
If stty says "echo" then the driver hasn't touched it.
It should show "-echo".
Check to see if it even tried to load.
I'll get you the debug version in a bit.
Edit: Charging up my old Nook NST to check what the scoop with that is...
Edit^2: What I posted above is actually the verbose one (that spams logcat) but works fine on the Glows.
The NST needs a different build.
I'll post a non-logcat-spamming versions for the Glows in a bit.
Renate NST said:
Since you're using the default of 9600 that won't tell you anything.
If stty says "echo" then the driver hasn't touched it.
It should show "-echo".
Check to see if it even tried to load.
I'll get you the debug version in a bit.
Click to expand...
Click to collapse
I guess i have understand what you want mean. It's about using the "GPSSPEED" value to check with stty if the lib module is correctly loaded by alterating the link speed ?
So to test it i have changed the value to 4800 has you recommanded. But the stty stil give back the 9600 default value.
Code:
# busybox stty -F /dev/ttyS1
speed 9600 baud; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-brkint -imaxbel
#
nothing revelent about :
Code:
/ # dmesg | grep gps
/ # logcat | grep gps
Renate NST said:
Edit: Charging up my old Nook NST to check what the scoop with that is...
Edit^2: What I posted above is actually the verbose one (that spams logcat) but works fine on the Glows.
The NST needs a different build.
I'll post a non-logcat-spamming versions for the Glows in a bit.
Click to expand...
Click to collapse
Alright !
[If I can only figure out how this forum works now...]
Ok, so the problem was getting this to run on the NST, which is still running Android 2.1, API 7.
Android forced us to Clang for builds, there's an incompatibility with libdl.so, dladdr() is too modern.
So, here's a version that should work on both old and new.
I haven't double-checked it on the Glow3 yet.
It loads on the NST but I don't have any hardware check of it yet.
This is called gps.default.txt, rename it gps.default.so
MD5 188477c37d86b7a3ae43573e7174238b