I have a HTC Touch/Vogue on US Cellular. The phone is not active and I am just playing around with it for right now. I want to just try to use it as an MP3 player right now. Not sure what WM version is on there, but it makes a difference I could check. I loaded Android 1.5 Build (dated 8-8-09). I had to switch the board selection to 3 in the default.txt to boot up. I have media in the media folder and in a different folder which adroid sees and will play in the media player. I have no sound what so ever though.
1. Hard reset from Android
2. Adjusted Volume in WM
3. Played same MP3 in WM
4. Adjusted volume in android
5. Tried to hear a ring tone in android.
All of these yielded no results. I can't seem to get the phone to make a sound. Weird thing was after a hard reset from android the vibrate started to work.
I have been searching for a while here and on other forums and can't find any solutions.
I am new to this whole thing and not sure what radio I have or how to find out. Any help is appreciated. There are more problems, but I can't even get this to work at all.
E/AudioHardwareMSM72XX( 115): Cannot open /dev/msm_pcm_out errno: 22
D/AudioHardwareMSM72XX( 115): AudioStreamOutMSM72xx::write(0xb618, 4096)
Thats what my logcat says when I hit play in the media player.
I/ActivityManager( 132): Starting activity: Intent { comp={com.android.music/co
m.android.music.MusicBrowserActivity} }
W/ActivityManager( 132): startActivity called from non-Activity context; forcin
g Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { comp={com.android.music/com.androi
d.music.MusicBrowserActivity} }
D/AudioHardwareMSM72XX( 115): AudioStreamOutMSM72xx::write(0xb618, 4096)
V/AudioHardwareMSM72XX( 115): open driver
E/AudioHardwareMSM72XX( 115): Cannot open /dev/msm_pcm_out errno: 22
D/AudioHardwareMSM72XX( 115): AudioStreamOutMSM72xx::write(0xb618, 4096)
V/AudioHardwareMSM72XX( 115): open driver
E/AudioHardwareMSM72XX( 115): Cannot open /dev/msm_pcm_out errno: 22
D/AudioHardwareMSM72XX( 115): AudioStreamOutMSM72xx::write(0xb618, 4096)
V/AudioHardwareMSM72XX( 115): open driver
E/AudioHardwareMSM72XX( 115): Cannot open /dev/msm_pcm_out errno: 22
D/AudioHardwareMSM72XX( 115): AudioStreamOutMSM72xx::write(0xb618, 4096)
V/AudioHardwareMSM72XX( 115): open driver
E/AudioHardwareMSM72XX( 115): Cannot open /dev/msm_pcm_out errno: 22
I/ActivityManager( 132): Displayed activity com.android.music/.MusicBrowserActi
vity: 607 ms
D/pppd ( 1232): sent P
I/ActivityManager( 132): Starting activity: Intent { action=com.android.music.P
LAYBACK_VIEWER comp={com.android.music/com.android.music.MediaPlaybackActivity}
}
D/AudioHardwareMSM72XX( 115): AudioStreamOutMSM72xx::write(0xb618, 4096)
V/AudioHardwareMSM72XX( 115): open driver
E/AudioHardwareMSM72XX( 115): Cannot open /dev/msm_pcm_out errno: 22
D/AudioHardwareMSM72XX( 115): AudioStreamOutMSM72xx::write(0xb618, 4096)
V/AudioHardwareMSM72XX( 115): open driver
E/AudioHardwareMSM72XX( 115): Cannot open /dev/msm_pcm_out errno: 22
D/AudioHardwareMSM72XX( 115): AudioStreamOutMSM72xx::write(0xb618, 4096)
V/AudioHardwareMSM72XX( 115): open driver
E/AudioHardwareMSM72XX( 115): Cannot open /dev/msm_pcm_out errno: 22
D/AudioHardwareMSM72XX( 115): AudioStreamOutMSM72xx::write(0xb618, 4096)
V/AudioHardwareMSM72XX( 115): open driver
E/AudioHardwareMSM72XX( 115): Cannot open /dev/msm_pcm_out errno: 22
I/ActivityManager( 132): Displayed activity com.android.music/.MediaPlaybackAct
Thats what it says before When i laungh the media player
try my mssmisonthemed build from the google code page. Let me know if it does that same thing.
i replaced system.img with the mssmisonsystem.img i downloaded at google code.
it proceed to linux, then after it hit rootfs successfully, then it goes to look for the system.img file, It said
dev/block/loop0 unmounted
Checking for Hero...
Hero/Rogers builds not found Assuming Ion variant
(Thats about all I could catch)
then
[ 39.377253] android_power: wakeup (0->0) at 206761
[ xx.xxxxxx] android_power: wakeup (0->0) at xxxxxx
Where the x's change digits, and it hits line after line of that for about 5 mins.
It never got out of linux
umm that's odd. That totally should happen. Try and clear your sd card and start again..
I tried your hero build from hero.zip at google code, that booted past linux but just goes to the Hero and HTC logos. I left it for 5 mins once it got past linux and nothing except the HERO and HTC logos cycling every min or so.
in the past formatting the card and starting over over hasn't done anything, but its worth a try.
socalracer said:
I tried your hero build from hero.zip at google code, that booted past linux but just goes to the Hero and HTC logos. I left it for 5 mins once it got past linux and nothing except the HERO and HTC logos cycling every min or so.
in the past formatting the card and starting over over hasn't done anything, but its worth a try.
Click to expand...
Click to collapse
did you set your res to 320x480?
i did hard reset, didnt do anything. i had w=320, h=428 in default.txt i will change it to w=320 h=480 and reboot.
Confirmed WM 6 Pro
CE OS 5.2.1620 (Build 18125.0.4.2)
Radio 2.32.00
ROM 1.21.573.1
ROM Date 7/03/08
after reboot and changing default.txt, same thing.
still getting this and have been since using your imgs
dev/block/loop0 FILE SYSTEM MODIFIED, even though it gets to HERO/HTC splash startup.
also to note, before starting all this android stuff, the device was master reset to defaults. Powered up and went through all the lil tutorials and setup everything, nothing has been done since then.
bumping for any more ideas?
After resolution on default.txt. set lcd.density=160
tried the lcd density, seemed to work the same maybe a little better. it boots(using hero build) to android for the first time and does the setup wizard, then when i hit finish, it looks like it reboots, goes back to hero/htc splash, then eventually it just stops at the htc screen and you can't see the animation any more, tried hard reset from there and it boots up, linux says the file system was modified and same thing stops at HTC spalsh screen with no animation after about the 5th time
EDIT: same results with lcd density not in the default txt. It responds very slow to the selections in the wizard. It has a problem usually getting to the wizard and sometime will say system process failed, wait or force quit, i say wait and then soon the wizard will open. tested this with a clean wipe of the card.
tried the zimage 8-14-09 said it resolved sound problems, still nothing. only difference was i had files in a folder that were mp3s, before it would recognize them, but now it won't, still couldnt get any of the ringers to play or the volume changing didnt emit any sound
socalracer said:
tried the zimage 8-14-09 said it resolved sound problems, still nothing. only difference was i had files in a folder that were mp3s, before it would recognize them, but now it won't, still couldnt get any of the ringers to play or the volume changing didnt emit any sound
Click to expand...
Click to collapse
The sound issues that it fixed were something else entirely.
What your error log states is that android cannot access your sound hardware.
What I might recommend is downloading ALL the files again. It's not unprecedented for a file to be slightly corrupted on download, and then some weird error like this occurs. Also, run SHA checksums on all the files you download. On the google-code site, you can find out what the SHA checksums should be by clicking on the description of the file (rather than the filename itself.) You should be able to find a free SHA checker on the internet... I haven't had the need for one lately, so I can't think of what you might wanna use.
i used fciv to check the checksums, 3 out of 3 files had completely different checksums using sha1. i downloaded the bundle android 1.5 8-8-09. guess i can try downloading the bundle again. hope this works
EDIT: the checksum for the zip file bundle i downloaded was right. then reextracted the files and the checksums matched up. then wiped the card and booted original 8-8-09 image. same thing no sound. i put a mp3 file in the media folder, it sees the file and plays it, not no volume. i readjusted the media volume while the player was open camera+volume button, that didnt do anything. When android boots up from linux this is on of the things it displays [ 12.134009] 7500 Audio : Speakerphone Off
still haven't been able to get this thing to work. this is frustrating
have you tried upgrading the rom? It should be 3.01.573.4. Go to device information under settings to check
socalracer said:
still haven't been able to get this thing to work. this is frustrating
Click to expand...
Click to collapse
You probably have an old radio, update to the latest rom for your carrier and audio will work.
Just downloaded the latest (system-haykuro.img) Hero build.
Now I only have problems with:
- Importing my SIM accounts
- The weather clock (don't know how else to name it, flipclock I think) is not displaying the weather
- My location on Google maps is not working. (Can't find my location)
Related
when i run the program i am getting
App: SLIDE.EXE
File:SLIDE.EXE
Proc: WINMAIN
Opcode: LOADSPRITE
Char/Line/Offset: 0, 0,
0x005391e0
Error loading image
\Program
Files\Slide2Unlock\GFX\Res\Wallpaper.bmp
I Followed to Extension and the file is there and opens fine..any suggestions?
For some reason I am getting the same error in mine I have tried doing this like 4 times already. If some one knows what’s wrong please help.
mackthepattywack said:
when i run the program i am getting
App: SLIDE.EXE
File:SLIDE.EXE
Proc: WINMAIN
Opcode: LOADSPRITE
Char/Line/Offset: 0, 0,
0x005391e0
Error loading image
\Program
Files\Slide2Unlock\GFX\Res\Wallpaper.bmp
I Followed to Extension and the file is there and opens fine..any suggestions?
Click to expand...
Click to collapse
have you tried S2U2 rather than Slide to unlock
Is there a picture file at the end of that path?
"\Program Files\Slide2Unlock\GFX\Res\Wallpaper.bmp"
Is it possible to emulate an android ROM on a computer?
If you grab the SDK, you can run any version of Android in the emulator. If you want to run an actual ROM you will need to create an image of /system (as system.img) and replace that with those in the SDK folder.
thanks alot! that helped me alot
and yes, i want to run an actual ROM. what filesystem does it have to be?
was thinking about something like...
(cd PATH)
dd if=/dev/zero of=system bs=1024 count=#KB_needed
losetup /dev/loop0 system
mkfs -f FS /dev/loop0
(mkdir /mnt/system)
mount /dev/loop0 /mnt/system/
cp -a system /mnt/system/
umount /mnt/system/
losetup -d /dev/loop0
do you know any good tools for this exept for dd?
Never tried so I honestly don't know, you sound like you know a lot more than me about creating/mounting images than me, so it's probably best to use your judement. The easiest way is just to make a nadroid back backup, flash the ROM you want to test, nadroid that and grab system.img, revert to your old nandroid backup. It's tedious, and it doesn't help if you want to test a ROM before flashing, but that's the only method I've heard people use.
okay. thanks
HTC Sense UI system.img
Does anybody know where I can download a system.img for a HTC with Sense UI (Hero for example)? I have been looking for ages with no luck.
My app is not working on a customers Hero and I am trying to find a Hero system.img to run in the emulator so I can work out why it fails on this phone.
I dont own a Hero, so am unable to extract my own system.img.
You can get HTC official ROMs here:
http://forum.xda-developers.com/showthread.php?t=559622
if you've got a windows computer you probably could extract the content of this exe file and then try to follow my previous instructions to make the system.img.
And if you don't have an unix/linux box.. You could send the content of the exe file to me, if you are able to extract the data in it. (I'm in China with a netbook atm and not able to extract the exe file with my limited tools). Then I could try to make you a system.img
I tried that, but without an HTC phone connected to the PC USB the exe wont extract.
I take that back. I found the files in my temp folder. I have extracted ROM.zip including the system.img into the avd folder, but the emulator is failing to bring it up.
could you upload that zip file here or on rapidshare? then i could have a look at it
Here is the rom.zip file from RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_NoDriver.exe:
rom.zip
Other people must be doing this kindof thing to test their apps?
Here is the logcat. It looks like the sytem process is starting to come up, then fails. This repeats over and over.
12-16 18:34:20.945: INFO/SystemServer(113): Starting telephony registry
12-16 18:34:20.975: INFO/SystemServer(113): Starting Package Manager.
12-16 18:34:21.056: INFO/Installer(113): connecting...
12-16 18:34:21.075: INFO/installd(33): new connection
12-16 18:34:21.205: INFO/PackageManager(113): Got library com.google.android.maps in /system/framework/com.google.android.maps.jar
12-16 18:34:21.225: INFO/PackageManager(113): Got library com.google.android.gtalkservice in /system/framework/com.google.android.gtalkservice.jar
12-16 18:34:21.265: INFO/PackageManager(113): Got library com.htc.framework in /system/framework/com.htc.framework.jar
12-16 18:34:21.515: INFO/PackageManager(113): Got library android.awt in /system/framework/android.awt.jar
12-16 18:34:21.535: INFO/PackageManager(113): Got library android.test.runner in /system/framework/android.test.runner.jar
12-16 18:34:21.535: INFO/PackageManager(113): Got library com.android.im.plugin in /system/framework/com.android.im.plugin.jar
12-16 18:34:21.545: INFO/PackageManager(113): Got library com.htc.android.pimlib in /system/framework/com.htc.android.pimlib.jar
12-16 18:34:21.565: INFO/PackageManager(113): Got library com.htc.android.easopen in /system/framework/com.htc.android.easopen.jar
12-16 18:34:21.565: INFO/PackageManager(113): Got library com.scalado.util.ScaladoUtil in /system/framework/com.scalado.util.ScaladoUtil.jar
12-16 18:34:22.596: DEBUG/dalvikvm(113): GC freed 4273 objects / 216216 bytes in 302ms
12-16 18:34:23.476: ERROR/PackageManager(113): Adding duplicate shared user, keeping first: android.uid.shared
12-16 18:34:23.526: ERROR/PackageManager(113): Occurred while parsing settings at line -1, column -1
12-16 18:34:23.546: ERROR/PackageManager(113): Adding duplicate shared user, keeping first: com.htc.rosie.uid.shared
12-16 18:34:23.596: ERROR/PackageManager(113): Occurred while parsing settings at line -1, column -1
12-16 18:34:23.746: ERROR/PackageManager(113): Bad package setting: package com.android.providers.contacts has shared uid 10008 that is not defined
12-16 18:34:23.746: ERROR/PackageManager(113): Bad package setting: package com.android.launcher has shared uid 10008 that is not defined
12-16 18:34:23.756: ERROR/PackageManager(113): Bad package setting: package com.android.googlesearch has shared uid 10008 that is not defined
12-16 18:34:23.766: ERROR/PackageManager(113): Bad package setting: package com.android.inputmethod.latin has shared uid 10008 that is not defined
12-16 18:34:23.786: ERROR/PackageManager(113): Bad package setting: package com.htc.MusicWidget has shared uid 10047 that is not defined
12-16 18:34:23.816: ERROR/PackageManager(113): Bad package setting: package com.android.contacts has shared uid 10008 that is not defined
12-16 18:34:23.836: ERROR/PackageManager(113): Bad package setting: package com.android.providers.userdictionary has shared uid 10008 that is not defined
12-16 18:34:23.846: ERROR/PackageManager(113): Bad package setting: package com.android.providers.im has shared uid 10008 that is not defined
12-16 18:34:23.896: INFO/dalvikvm(113): DexOpt: Some deps went away
12-16 18:34:23.926: ERROR/dalvikvm(113): /system/framework/com.scalado.util.ScaladoUtil.jar odex has stale dependencies
12-16 18:34:23.926: ERROR/dalvikvm(113): odex source not available -- failing
12-16 18:34:23.926: WARN/dalvikvm(113): threadid=15: thread exiting with uncaught exception (group=0x40013140)
12-16 18:34:23.936: ERROR/AndroidRuntime(113): Uncaught handler: thread android.server.ServerThread exiting due to uncaught exception
12-16 18:34:23.956: ERROR/AndroidRuntime(113): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
12-16 18:34:23.966: ERROR/AndroidRuntime(113): dalvik.system.StaleDexCacheError: /system/framework/com.scalado.util.ScaladoUtil.jar
12-16 18:34:23.966: ERROR/AndroidRuntime(113): at dalvik.system.DexFile.isDexOptNeeded(Native Method)
12-16 18:34:23.966: ERROR/AndroidRuntime(113): at com.android.server.PackageManagerService.<init>(PackageManagerService.java:419)
12-16 18:34:23.966: ERROR/AndroidRuntime(113): at com.android.server.PackageManagerService.main(PackageManagerService.java:261)
12-16 18:34:23.966: ERROR/AndroidRuntime(113): at com.android.server.ServerThread.run(SystemServer.java:126)
12-16 18:34:24.006: ERROR/AndroidRuntime(113): Crash logging skipped, no checkin service
12-16 18:34:24.006: ERROR/AndroidRuntime(113): Crash logging skipped, no htc checkin service
12-16 18:34:24.036: INFO/Process(113): Sending signal. PID: 113 SIG: 9
12-16 18:34:24.066: INFO/Zygote(102): Exit zygote because system server (113) has terminated
12-16 18:34:24.086: INFO/ServiceManager(26): service 'usagestats' died
12-16 18:34:24.086: INFO/ServiceManager(26): service 'SurfaceFlinger' died
12-16 18:34:24.086: INFO/ServiceManager(26): service 'power' died
12-16 18:34:24.086: INFO/ServiceManager(26): service 'batteryinfo' died
12-16 18:34:24.086: INFO/ServiceManager(26): service 'telephony.registry' died
12-16 18:34:24.106: ERROR/installd(33): eof
12-16 18:34:24.106: ERROR/installd(33): failed to read size
12-16 18:34:24.106: INFO/installd(33): closing connection
12-16 18:34:24.146: INFO/ServiceManager(26): service 'media.audio_flinger' died
12-16 18:34:24.146: INFO/ServiceManager(26): service 'media.player' died
12-16 18:34:24.146: INFO/ServiceManager(26): service 'media.camera' died
12-16 18:34:25.096: DEBUG/AndroidRuntime(130): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
12-16 18:34:25.116: DEBUG/AndroidRuntime(130): CheckJNI is ON
12-16 18:34:25.686: DEBUG/AndroidRuntime(130): --- registering native functions ---
12-16 18:34:25.956: INFO/(129): ServiceManager: 0xac38
12-16 18:34:25.956: DEBUG/AudioHardwareInterface(129): Running in emulation - using generic audio driver
12-16 18:34:25.956: INFO/AudioFlinger(129): Create BTIPSA2dpInterface
12-16 18:34:25.966: DEBUG/BTIPSA2dpInterface(129): BTIPSA2dpInterface 1.0.0.0.
12-16 18:34:25.966: DEBUG/BTIPSA2dpInterface(129): BTIPSA2dpInterface:penOutputStream 1, 0, 0
12-16 18:34:25.966: INFO/(129): Creating ashmem region names /data/btips/btips_mm_shm size 20480
12-16 18:34:25.966: INFO/AudioFlinger(129): AudioFlinger's thread ready to run for output 0
12-16 18:34:25.986: DEBUG/BTIPSA2dpInterface(129): BTIPSA2dpStreamOut::set 1, 0, 0
12-16 18:34:25.986: DEBUG/AudioFlinger(129): setRouting 0 2 -1, tid 129, calling tid 129
12-16 18:34:25.986: DEBUG/AudioFlinger(129): setRouting 1 2 -1, tid 129, calling tid 129
12-16 18:34:25.986: DEBUG/AudioFlinger(129): setRouting 2 1 -1, tid 129, calling tid 129
12-16 18:34:25.986: DEBUG/AudioFlinger(129): setMode to mode 0
12-16 18:34:25.996: INFO/AudioFlinger(129): AudioFlinger's thread ready to run for output 1
12-16 18:34:26.006: INFO/CameraService(129): CameraService started: pid=129
12-16 18:34:26.086: DEBUG/(130): ======================== register_android_graphics_Canvas, g_haveProfilerFile=0
12-16 18:34:26.476: INFO/Zygote(130): Preloading classes...
12-16 18:34:26.486: DEBUG/dalvikvm(130): GC freed 786 objects / 43096 bytes in 9ms
12-16 18:34:26.746: DEBUG/dalvikvm(130): GC freed 275 objects / 17264 bytes in 6ms
12-16 18:34:26.956: DEBUG/dalvikvm(130): GC freed 200 objects / 12200 bytes in 8ms
12-16 18:34:27.096: DEBUG/dalvikvm(130): Trying to load lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.346: DEBUG/dalvikvm(130): Added shared lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.356: DEBUG/dalvikvm(130): Trying to load lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.356: DEBUG/dalvikvm(130): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
12-16 18:34:27.366: DEBUG/dalvikvm(130): Trying to load lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.366: DEBUG/dalvikvm(130): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
12-16 18:34:27.386: DEBUG/dalvikvm(130): Trying to load lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.386: DEBUG/dalvikvm(130): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
12-16 18:34:27.396: DEBUG/dalvikvm(130): Trying to load lib /system/lib/libmedia_jni.so 0x0
12-16 18:34:27.396: DEBUG/dalvikvm(130): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
12-16 18:34:27.426: DEBUG/dalvikvm(130): GC freed 467 objects / 29272 bytes in 10ms
Click to expand...
Click to collapse
Anybody?
Someone must have emulated HTC Touch / Sense UI?!
Okay... After unzipping and manipulating a 2.1 ROM to my liking; I have now resigned it...
Can someone please explain to me how I would go about testing it with the Android SDK Emulator?
I have already created a 2.1 AVD and the emulator loads to the "ANDROID" screen...
What must I do to test out this newly packaged ROM file?
Hi,
I intensively searched for my problem, but found always other non-related stuff.
Recently (last 1, 2 days) my WiFi didn't connect to any APs any more. I was using CN nightlies and franco kernel, so today I did update CN without franco. Afterwards I downgraded CN and did a radio update and now I tried the stock 4.2.2 image with the flash-all script, which also seemed to reflash my radio.
The default wifi dialog always displayed the saved wifis only. And after installing stock, the initial wifi dialog displayed "searching" only for a very long time. Sometimes I see some networks and I even managed to connect to mine, but it dropped immediately.
I know, this is very undetailed, but do you have any recommendations / logs to look out / smth which could point me in the right direction? Or is my hardware just broken?
logcat outputs this when turning wi-fi on (on stock 4.2.2, unrooted):
D/WifiService( 499): setWifiEnabled: true pid=1942, uid=1000
D/BluetoothAdapter( 1942): 1110956336: getState() : mService = null. Returning STATE_OFF
W/Netd ( 156): No subsystem found in netlink event
D/NetlinkEvent( 156): Unexpected netlink message. type=0x11
W/Netd ( 156): No subsystem found in netlink event
D/NetlinkEvent( 156): Unexpected netlink message. type=0x11
D/Tethering( 499): sendTetherStateChangedBroadcast 1, 0, 0
D/Tethering( 499): InitialState.processMessage what=4
D/Tethering( 499): sendTetherStateChangedBroadcast 0, 0, 0
D/SoftapController( 156): Softap fwReload - Ok
D/CommandListener( 156): Setting iface cfg
D/CommandListener( 156): Trying to bring down wlan0
E/NetdConnector( 499): NDC Command {219 softap fwreload wlan0 STA} took too long (739ms)
I/wpa_supplicant( 9715): Successfully initialized wpa_supplicant
I/wpa_supplicant( 9715): rfkill: Cannot open RFKILL control device
I/wpa_supplicant( 9715): rfkill: Cannot open RFKILL control device
D/CommandListener( 156): Setting iface cfg
D/CommandListener( 156): Trying to bring up p2p0
D/BluetoothAdapter( 1942): 1110956336: getState() : mService = null. Returning STATE_OFF
Click to expand...
Click to collapse
when flashing stock (via the official google flash scripts), stock firmware files (qualcom, ..) are also flashed, right? or could I do something useful with the official google binaries?
Stupid post.... Ignore
Hi!
I have a problem with my phone that it randomly vibrates with no notification what so ever, even after doing a full wipe and flashing new ROM.
Lets start with some info:
GT-i9505
Danvdh Google Play ROM 4.4.4 (Pure nexus version)
GoogyMax3_GE 1.1.6 Kernel
I have Xposed Framwork installed
I have "Show all app that don't respond" in Developer options, still no errors have popped up.
No app which i've seen send vibration without notification when an update occurs.
I've tried to trace the source with logcat but havent really gotten any far.
Using the app aLogcat ROOT i often get the message:
Code:
E/AndroidRuntime(xxxxx): cannot open customer xml file
E/memtrack(same numbers): couldn't load memtrack module (no such file or directory)
E/Android.os.Debug(same numbers): failed to load memtrack module: -2
If i have the logging up and running in the app and then press Home button (Which takes me to Apex Launcher) i often get 2 quick vibrations
If i then start aLogcat ROOT again, i sometimes get another vibration followed by either
Code:
I/DEBUG (26414): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys
or
Code:
E/LightSensor ( 1010): Light old sensor_state 1, new sensor_state : 1 en : 0
However, it seems most often related to I/DEBUG (26414): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys
It's kinda getting frustrating and nothing i've Googled have seem to have provided the answer, most answers are something in line of Facebook messenger, repeat notification functions (For example vibration every 5 mins for sms, etc).
It happened more often before i wiped phone, which i then had Danvdh GPE rom, but 4.4.2 version instead, and ktoonez kernel. Apps were mostly same.
Following caused 2 vibrations 2 times:
Code:
I/DEBUG (26830): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys'
I/DEBUG (26830): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys'
E/LocSvc_eng( 1010): D/void loc_eng_deferred_action_thread(void*):1627] received msg_id = LOC_ENG_MSG_INJECT_LOCATION context = 0x8012add0
E/LocSvc_adapter( 1010): I/<--- void globalRespCb(locClientHandleType, uint32_t, locClientRespIndUnionType, void*) line 115 QMI_LOC_INJECT_POSITION_REQ_V02
E/LocSvc_api_v02( 1010): D/loc_free_slot:298]: freeing slot 0
E/Watchdog( 1010): [email protected] 194
E/AndroidRuntime(27295): cannot open customer xml file
E/memtrack(27295): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug(27295): failed to load memtrack module: -2
I/DEBUG (26830): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys'
I/DEBUG (26830): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys'
E/AndroidRuntime(27396): cannot open customer xml file
E/memtrack(27396): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug(27396): failed to load memtrack module: -2
Does anyone have ANY clue on how to fix this, or what might be causing it.
Anyone have any similar findings?
Thanks in advance
I have same problem!
If I remove Xposed Framework the random vibrations no longer appear, but it is very useful for me!
I opened a thread in Xposed Framework General -> here
Hi, ive got the same problem, random vibration 1 to 3 time, im running on the same
Rom with xposed installed. Anyone know any fix for that? Thank you
After a dealing with selling my house and moving into a new one, I've finally got my build system back together and connected to the Internet. This Ubuntu machine has been successfully building OmniROM 4.x for a couple devices and 5.1 for Nexus 5 for some time, but now I have a puzzle.
The "nightly" version of OmniROM boots and runs fine on the hardware. However, when I try to boot the "homemade" version of 5.1, it fails to get very far in the process. I've already pulled down a fresh repo, installed the factory drivers from https://developers.google.com/android/nexus/drivers (originally 5.1 LMY48B, but now have also tried fresh copies of 5.1 LMY48M) and everything appears to build properly.
Looking at the two logcat outputs, the earliest hints of error seem to be the inability to load a key library
NIGHTLY:
Code:
03-31 16:27:29.726 D/QSEECOMD: ( 179): qseecom listener services process entry PPID = 1
03-31 16:27:29.726 E/QSEECOMD: ( 179): Listener: index = 0, hierarchy = 0
03-31 16:27:29.733 D/QSEECOMD: ( 179): Init dlopen(librpmb.so, RTLD_NOW) succeeds
03-31 16:27:29.733 D/QSEECOMD: ( 179): Init::Init dlsym(g_FSHandle rpmb_init_service) succeeds
HOMEMADE:
Code:
03-31 15:07:02.586 E/QSEECOMD: ( 176): Listener: index = 0, hierarchy = 0
03-31 15:07:02.586 E/QSEECOMD: ( 176): Init dlopen(librpmb.so, RLTD_NOW) is failed....
03-31 15:07:02.586 E/QSEECOMD: ( 176): ERROR: RPMB_INIT failed, shall not start listener services
That stanza, or one very similar is spattered throughout the homemade logcat.
Looking at the homemade version, "find / -name librpmb.so" returns nothing.
For the nightly version, it is found at /system/lib/librpmb.so
I don't see it in the output directory, but it is in the vendor source directory
Code:
[email protected]:~/devel/build/hammerhead-5.1/out/target/product/hammerhead$ find . -name librpmb.so
[email protected]:~/devel/build/hammerhead-5.1/out/target/product/hammerhead$ find $ANDROID_BUILD_TOP/vendor -name librpmb.so
/home/jeff/devel/build/hammerhead-5.1/vendor/qcom/hammerhead/proprietary/librpmb.so
Digging further, vendor/qcom/hammerhead/device-partial.mk does not include librpbm.so (but does, for example, include qseecomd)
I don't see anything in vendor/qcom/hammerhead/ that would copy over librpmb.so
Looking at the installed nightly rom, /system/lib/librpmb.so is there (and has the same md5 as that from the qcom driver distributions)
Has anyone seen this before? Any suggestions on resolution? (other than the obvious, "Well, just edit the qcom device-partial.mk")
I'm sort of stuffed on doing any dev work until I can get a working baseline build again...
Thanks,
Jeff
jeffsf said:
After a dealing with selling my house and moving into a new one, I've finally got my build system back together and connected to the Internet. This Ubuntu machine has been successfully building OmniROM 4.x for a couple devices and 5.1 for Nexus 5 for some time, but now I have a puzzle.
The "nightly" version of OmniROM boots and runs fine on the hardware. However, when I try to boot the "homemade" version of 5.1, it fails to get very far in the process. I've already pulled down a fresh repo, installed the factory drivers from https://developers.google.com/android/nexus/drivers (originally 5.1 LMY48B, but now have also tried fresh copies of 5.1 LMY48M) and everything appears to build properly.
Looking at the two logcat outputs, the earliest hints of error seem to be the inability to load a key library
NIGHTLY:
Code:
03-31 16:27:29.726 D/QSEECOMD: ( 179): qseecom listener services process entry PPID = 1
03-31 16:27:29.726 E/QSEECOMD: ( 179): Listener: index = 0, hierarchy = 0
03-31 16:27:29.733 D/QSEECOMD: ( 179): Init dlopen(librpmb.so, RTLD_NOW) succeeds
03-31 16:27:29.733 D/QSEECOMD: ( 179): Init::Init dlsym(g_FSHandle rpmb_init_service) succeeds
HOMEMADE:
Code:
03-31 15:07:02.586 E/QSEECOMD: ( 176): Listener: index = 0, hierarchy = 0
03-31 15:07:02.586 E/QSEECOMD: ( 176): Init dlopen(librpmb.so, RLTD_NOW) is failed....
03-31 15:07:02.586 E/QSEECOMD: ( 176): ERROR: RPMB_INIT failed, shall not start listener services
That stanza, or one very similar is spattered throughout the homemade logcat.
Looking at the homemade version, "find / -name librpmb.so" returns nothing.
For the nightly version, it is found at /system/lib/librpmb.so
I don't see it in the output directory, but it is in the vendor source directory
Code:
[email protected]:~/devel/build/hammerhead-5.1/out/target/product/hammerhead$ find . -name librpmb.so
[email protected]:~/devel/build/hammerhead-5.1/out/target/product/hammerhead$ find $ANDROID_BUILD_TOP/vendor -name librpmb.so
/home/jeff/devel/build/hammerhead-5.1/vendor/qcom/hammerhead/proprietary/librpmb.so
Digging further, vendor/qcom/hammerhead/device-partial.mk does not include librpbm.so (but does, for example, include qseecomd)
I don't see anything in vendor/qcom/hammerhead/ that would copy over librpmb.so
Looking at the installed nightly rom, /system/lib/librpmb.so is there (and has the same md5 as that from the qcom driver distributions)
Has anyone seen this before? Any suggestions on resolution? (other than the obvious, "Well, just edit the qcom device-partial.mk")
I'm sort of stuffed on doing any dev work until I can get a working baseline build again...
Thanks,
Jeff
Click to expand...
Click to collapse
Weird. I still haven't gotten completely back from vacation (have a friend visiting now) so I haven't built Omni in a while...
I'll try to build it when they leave, not sure when that will be though.
@XpLoDWilD and @maxwen - Could this potentially be one of those weird messes where our source trees have an issue but the build server hasn't properly synced? This wouldn't be the first time we've had a "why the hell didn't this break months ago" issues like some issues @Jakew02 had last winter.
More digging reveals that between 5.0 (LRX21O) and 5.1.1 (LMY48M) the following files appear to be added (all in 5.1.0 LMY47D aka 1743759):
vendor/qcom/hammerhead/proprietary/librpmb.so
vendor/qcom/hammerhead/proprietary/libssd.so
vendor/qcom/hammerhead/proprietary/qmi_fw.conf
On the other hand, vendor/qcom/hammerhead/device-partial.mk has apparently not changed since at least LRX21O
fgrep suggests that libssd.so is referenced in qseecomd (as is librpmb.so)
jeffsf said:
More digging reveals that between 5.0 (LRX21O) and 5.1.1 (LMY48M) the following files appear to be added (all in 5.1.0 LMY47D aka 1743759):
vendor/qcom/hammerhead/proprietary/librpmb.so
vendor/qcom/hammerhead/proprietary/libssd.so
vendor/qcom/hammerhead/proprietary/qmi_fw.conf
On the other hand, vendor/qcom/hammerhead/device-partial.mk has apparently not changed since at least LRX21O
fgrep suggests that libssd.so is referenced in qseecomd (as is librpmb.so)
Click to expand...
Click to collapse
Better use the DonkeyCoyote repo, at least this is what Jenkins does afaik: https://github.com/DonkeyCoyote/proprietary_vendor_lge/tree/android-5.1/hammerhead
golden-guy said:
Better use the DonkeyCoyote repo, at least this is what Jenkins does afaik: https://github.com/DonkeyCoyote/proprietary_vendor_lge/tree/android-5.1/hammerhead
Click to expand...
Click to collapse
Didn't realize he wasn't... librpmb was added with https://github.com/DonkeyCoyote/pro...mmit/1a71e5c4d257c4883e1dea461fd893df13e0413c
AOSP's official binary blob distros often are missing stuff that is necessary for some capabilities and CAN be found in the factory images.
We don't mention DC in any official documentation for legal liability reasons... We probably need to update the extract-files scripts for ALL of our devices...