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 }
Hi all,
I have a problem with my defy, whitout fall or update the touch screen stop responding.
After some resets & sbf flashing I've noticed that the touch screen is ok only when there is no sdcard.
I've tried over sdcards with no more success.
The sdcard is readable, I can access with adb.
Clockworkmod access the sdcard too.
With sdcard dmesg :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_enq
touch_write: Error while trying to write 2 bytes
qtouch_set_addr: Can't send obp addr 0x 0
qtouch_process_info_block: Cannot read info object block
qtouch_ts_probe:Cannot read info block -121, checking for bootloader mode.
Without sdcard :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_en
qtouch_process_info_block: Build version is 0x10
qtouch_process_info_block: Object 5 @ 0x00f2 (9) insts 1 rep_ids 0
qtouch_process_info_block: Object 6 @ 0x00fb (6) insts 1 rep_ids 1
qtouch_process_info_block: Object 38 @ 0x0101 (8) insts 1 rep_ids 0
(...)
Can it be a HW problem ?
What do you think I can do ?
Questions go in the Q&A section
CharlyBrok said:
Hi all,
I have a problem with my defy, whitout fall or update the touch screen stop responding.
After some resets & sbf flashing I've noticed that the touch screen is ok only when there is no sdcard.
I've tried over sdcards with no more success.
The sdcard is readable, I can access with adb.
Clockworkmod access the sdcard too.
With sdcard dmesg :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_enq
touch_write: Error while trying to write 2 bytes
qtouch_set_addr: Can't send obp addr 0x 0
qtouch_process_info_block: Cannot read info object block
qtouch_ts_probe:Cannot read info block -121, checking for bootloader mode.
Without sdcard :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_en
qtouch_process_info_block: Build version is 0x10
qtouch_process_info_block: Object 5 @ 0x00f2 (9) insts 1 rep_ids 0
qtouch_process_info_block: Object 6 @ 0x00fb (6) insts 1 rep_ids 1
qtouch_process_info_block: Object 38 @ 0x0101 (8) insts 1 rep_ids 0
(...)
Can it be a HW problem ?
What do you think I can do ?
Click to expand...
Click to collapse
AFAIK, it is HW related..
Best choice, get it to the SC..
Maybe I'll try to change the digitizer (20€ on ebay).
Warranty period is finish.
I want more log,
The goal is to enable logging debug in qtouch_obp_ts
I put in /system/etc/init.d/77debug
Echo 0xFF > /sys/module/qtouch_obp_ts/parameters/tsdebug
But no change at all...
What I am doing wrong ?
Envoyé depuis mon A500 avec Tapatalk
Hello, sorry when i post a new Thread i think that many users have the same Problem but my english is not so good that i can find the right Thread ... I have Flash :
I9505_Omega_v2.0_GUEUBMG8_Android_4.3_md5_830353DC5EB14151A017C340C1285E51
Now i have flash a other Rom:
aokp_i9505_unofficial_2013-05-19
and that:
I9505XXUAMDM_I9505OXAAMDM_I9505XXUAMDM_HOME.tar
Now i dont have Sound anymore (micro and Sound are Dissable) Now i have read, that i have make a Bootloader Downgrade and have shoot i up my Bootloader with that :S
What can i doo that Sound works again !? Thanks for Help
wolfsstolz said:
Hello, sorry when i post a new Thread i think that many users have the same Problem but my english is not so good that i can find the right Thread ... I have Flash :
I9505_Omega_v2.0_GUEUBMG8_Android_4.3_md5_830353DC5EB14151A017C340C1285E51
Now i have flash a other Rom:
aokp_i9505_unofficial_2013-05-19
and that:
I9505XXUAMDM_I9505OXAAMDM_I9505XXUAMDM_HOME.tar
Now i dont have Sound anymore (micro and Sound are Dissable) Now i have read, that i have make a Bootloader Downgrade and have shoot i up my Bootloader with that :S
What can i doo that Sound works again !? Thanks for Help
Click to expand...
Click to collapse
wipe data and cache.
if not, reflash your stock firmware, wipe data and cache, reboot
no, that dosnt work, that is a buck in bootloader (4.3 downgrade) i have do flash all roms (wipe too) i have flash a pit rom too but this PRoblem with Bootloader brick is the same. I have Read that many German Users have the same Problem when they flash a higher rom and downgrade it then.I think i must wait for a Developer who have the same Problem :S
When another User Have the same Problem it Please write it here to see that is a big problem for other Users too
Sorry but with Apple i dont have this PRoblem maybe i go back XD
wolfsstolz said:
no, that dosnt work, that is a buck in bootloader (4.3 downgrade) i have do flash all roms (wipe too) i have flash a pit rom too but this PRoblem with Bootloader brick is the same. I have Read that many German Users have the same Problem when they flash a higher rom and downgrade it then.I think i must wait for a Developer who have the same Problem :S
Click to expand...
Click to collapse
why dont you flash MH8 or 5 firmware, it contains the newer bootloader
Edit: please take a look here http://forum.xda-developers.com/showthread.php?t=2436368
when i flash that Sound dont go anymore too. the Problem is a bug in botloader in the newer FW when i have read that correctly
Sorry, i have read that not right .....
Can you give me a link from Rom ?! I only found a rom
forum.xda-developers.com/showthread.php?t=2299087
but this is only without new Bootloader and i think i need that with bootloader or works that too !?
Thansk for Help
Push Thread Too ....
I have Problem with Sound(Downgrade to Stock Rom from Omega Rom)
Now i have Read that i must install fallow Roms:
Factory_Firmware_Full_Wipe_I9505XXUBMGA_I9505OXXBM G3_NEE
and that:
GT-I9505-Factory-Firmware-Full-Wipe-DBT
Basis I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8
This Roms are in Forum but Theme is Close and Files only on **** hoster (Hotfile)
Who can upload that to another hoster (Hotfile is very slow in Germany 30 kb and 1 gb download go of :S ) like upoaded.to or mega.co.nz ?!
Who can help me for Sound come back please help. I have do all what i have read in Forum but nothing works for me.
Thanks for Help.
No People have a Idea !????
I have make a Photo from logger, it was nice when a dev can look ...
Who can tell me from that Folder:
My Android Folder:
1. i have more "mnt" Folder (mnt + mnt_1)
2. On Storage Folder i can see: USBDriveA ,USBDriveB, USBDrive ..... looks folfer i can see: ExtSdCard - sdcard_3
3. I have a folder named: Firmware + Firmware-mdm
4. ALL Files in : sys/fs/selinux are empty, 0kb , Subfolder too
5. In mnt_1 sys/fs/ext4 Folder are too mutch Folders !? looks on mmcblk0p10 + 16+18+26+29 with same Files
and many more .... Please , who can look on his Machine to this Folders, is that the same !?
Here Are Photos from logger that my Sound dosnt work:
{
"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"
}
I cant believe that no People can help me to bring back my Sound ....
Here a logcat answer from Sound .....
D/ALSADevice(10225): No valid input device: 0
V/ALSADevice(10225): switchDevice,rxDev:Speaker, txDevnull), curRxDev:None, curTxDev:None
D/alsa_ucm(10225): snd_use_case_set(): uc_mgr 0x40f97fb0 identifier _enadev value Speaker
E/alsa_ucm(10225): Invalid current verb value: Inactive - -1
E/alsa_ucm(10225): No valid device Speaker found
D/ALSADevice(10225): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice Speaker inCallDevSwitch = 0
V/ALSADevice(10225): switchDevice Done
D/alsa_ucm(10225): snd_use_case_set(): uc_mgr 0x40f97fb0 identifier _verb value HiFi
E/alsa_ucm(10225): Control device not initialized
E/alsa_ucm(10225): Control device not initialized
W/alsa_ucm(10225): error snd_use_case_apply_mixer_controls
D/ALSADevice(10225): close: handle 0x40026d40 h 0x0
D/ALSADevice(10225): open: handle 0x40026d40, format 0x2
V/ALSADevice(10225): Music case
D/ALSADevice(10225): Device value returned is hw:0,0
V/ALSADevice(10225): flags 0, devName hw:0,0
E/alsa_pcm(10225): cannot open device '/dev/snd/pcmC0D0p', errno 2
V/ALSADevice(10225): pcm_open returned fd -1
E/ALSADevice(10225): open: Failed to initialize ALSA device 'hw:0,0'
E/AudioHardwareALSA(10225): Device open failed
I/audio_a2dp_hw(10225): adev_open: adev_open in A2dp_hw module
I/AudioFlinger(10225): loadHwModule() Loaded a2dp audio interface from A2DP Audio HW HAL (audio) handle 3
I/AudioFlinger(10225): loadHwModule() Loaded usb audio interface from SEC USB audio HW HAL (audio) handle 4
D/tms_audio_hw/AudioTmsIpc(10225): adev_open : Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsInitSilenceFrames : Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsInitSilenceFrames : Exit
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerInit :Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerInit: thread started with name =TerminalModeAudioServer and id = 1073900584
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerInit exit
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientSetup : Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen :Enter
D/tms_audio_hw/AudioTmsIpc(10225): initMutex: AudioClientSocketMutex Mutex Created
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientSetup : Exit
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientInit :Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientInit: thread started with name =TerminalModeAudioClient and id = 1073900664
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientInit exit
D/tms_audio_hw/AudioTmsIpc(10225): adev_open : Exit
D/tms_audio_hw/AudioTmsIpc(10225): adev_init_check : Enter
D/tms_audio_hw/AudioTmsIpc(10225): adev_set_master_volume : Enter 1.000000
I/AudioFlinger(10225): loadHwModule() Loaded tms audio interface from TMS Audio HW HAL (audio) handle 5
E/AudioPolicyManagerBase(10225): Not output found for attached devices 00000003
E/AudioPolicyManagerBase(10225): Failed to open primary output
E/AudioPolicyManagerBase(10225): getDeviceForStrategy() speaker device not found
E/AudioPolicyManagerBase(10225): getDeviceForStrategy() speaker device not found
E/AudioPolicyManagerBase(10225): getDeviceForStrategy() speaker device not found
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen Socket Success Name /data/TMAudioSocketServer
E/AudioPolicyService(10225): couldn't init_check the audio policy (No such device)
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen Bind Success gAudioServerLocalSockFd 20
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen Listen Done gAudioServerLocalSockFd 20 ret 0
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen PLATFORM_AUDIO_CMD SIZE 16
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen PLATFORM_AUDIO_DATA SIZE 24
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen PLATFORM_AUDIO_META_DATA SIZE 20
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen SizeInBytes 12288
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen : Givimg Permission 0777 mode , 0 ret
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen accept Start len 110 gAudioServerLocalSockFd 20
V/TranscoderService(10225): TranscoderService created
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen :Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen Socket Success Name /data/TMAudioSocketClient
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen Bind Success gAudioClientLocalSockFd 23
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen Listen Done gAudioClientLocalSockFd 23 ret 0
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen PLATFORM_AUDIO_CMD SIZE 16
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen PLATFORM_AUDIO_DATA SIZE 24
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen PLATFORM_AUDIO_META_DATA SIZE 20
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen accept Start len 110 gAudioClientLocalSockFd 23
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen : Givimg Permission 0777 mode , 0 ret
I/power ( 5291): *** release_dvfs_lock : lockType : 1
D/CustomFrequencyManagerService( 5291): releaseDVFSLockLocked : Getting Lock type frm List : DVFS_MIN_LIMIT frequency : 1566000 uid : 10135 pid : 8603 tag : [email protected]
flash this firmware, wipe data and cache after, reboot http://www.hotfile.com/dl/243289856/5f90db9/I9505XXUDMH8_I9505OXXDMHA_BTU.zip.html
Flash stock kernel again and you would be good.
I had this issue too and found it hard way that it's custom kernel causing this issue.
You can also try this.
Switch off your phone (not restart) and wait for 15-20 secs. And turn it back on. Some users are saying, this will get back your sound.
I have flash that many Times but i will test that again .... Thanks for Help.
Is that the same Rom ? :
I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar.md5
ok, i have Flash now the Rom again, have 3 Times make a Factory Reset + Cache Wipe
Then i have Flash the Kernel only and power of for 20 Seconds my Galaxy then i have Reboot that but no Sound again
Then i have make a LogCat and the Same here: (No Speaker found)
D/ALSADevice( 6355): No valid input device: 0
V/ALSADevice( 6355): switchDevice,rxDev:Speaker, txDevnull), curRxDev:None, curTxDev:None
D/alsa_ucm( 6355): snd_use_case_set(): uc_mgr 0x407ba2f8 identifier _enadev value Speaker
E/alsa_ucm( 6355): Invalid current verb value: Inactive - -1
E/alsa_ucm( 6355): No valid device Speaker found
D/ALSADevice( 6355): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice Speaker inCallDevSwitch = 0
V/ALSADevice( 6355): switchDevice Done
D/alsa_ucm( 6355): snd_use_case_set(): uc_mgr 0x407ba2f8 identifier _verb value HiFi
E/alsa_ucm( 6355): Control device not initialized
E/alsa_ucm( 6355): Control device not initialized
W/alsa_ucm( 6355): error snd_use_case_apply_mixer_controls
D/ALSADevice( 6355): close: handle 0x43d4ad40 h 0x0
D/ALSADevice( 6355): open: handle 0x43d4ad40, format 0x2
V/ALSADevice( 6355): Music case
D/ALSADevice( 6355): Device value returned is hw:0,0
V/ALSADevice( 6355): flags 0, devName hw:0,0
E/alsa_pcm( 6355): cannot open device '/dev/snd/pcmC0D0p', errno 2
V/ALSADevice( 6355): pcm_open returned fd -1
E/ALSADevice( 6355): open: Failed to initialize ALSA device 'hw:0,0'
E/AudioHardwareALSA( 6355): Device open failed
I/audio_a2dp_hw( 6355): adev_open: adev_open in A2dp_hw module
I/AudioFlinger( 6355): loadHwModule() Loaded a2dp audio interface from A2DP Audio HW HAL (audio) handle 3
I/AudioFlinger( 6355): loadHwModule() Loaded usb audio interface from SEC USB audio HW HAL (audio) handle 4
D/tms_audio_hw/AudioTmsIpc( 6355): adev_open : Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsInitSilenceFrames : Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsInitSilenceFrames : Exit
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerInit :Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerInit: thread started with name =TerminalModeAudioServer and id = 1138011176
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerInit exit
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen :Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientSetup : Enter
D/tms_audio_hw/AudioTmsIpc( 6355): initMutex: AudioClientSocketMutex Mutex Created
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientSetup : Exit
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientInit :Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientInit: thread started with name =TerminalModeAudioClient and id = 1138011256
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientInit exit
D/tms_audio_hw/AudioTmsIpc( 6355): adev_open : Exit
D/tms_audio_hw/AudioTmsIpc( 6355): adev_init_check : Enter
D/tms_audio_hw/AudioTmsIpc( 6355): adev_set_master_volume : Enter 1.000000
I/AudioFlinger( 6355): loadHwModule() Loaded tms audio interface from TMS Audio HW HAL (audio) handle 5
E/AudioPolicyManagerBase( 6355): Not output found for attached devices 00000003
E/AudioPolicyManagerBase( 6355): Failed to open primary output
E/AudioPolicyManagerBase( 6355): getDeviceForStrategy() speaker device not found
E/AudioPolicyManagerBase( 6355): getDeviceForStrategy() speaker device not found
E/AudioPolicyManagerBase( 6355): getDeviceForStrategy() speaker device not found
E/AudioPolicyService( 6355): couldn't init_check the audio policy (No such device)
V/TranscoderService( 6355): TranscoderService created
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen :Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen Socket Success Name /data/TMAudioSocketClient
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen Bind Success gAudioClientLocalSockFd 21
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen Listen Done gAudioClientLocalSockFd 21 ret 0
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen Socket Success Name /data/TMAudioSocketServer
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen Bind Success gAudioServerLocalSockFd 22
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen PLATFORM_AUDIO_CMD SIZE 16
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen Listen Done gAudioServerLocalSockFd 22 ret 0
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen PLATFORM_AUDIO_CMD SIZE 16
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen PLATFORM_AUDIO_DATA SIZE 24
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen PLATFORM_AUDIO_META_DATA SIZE 20
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen SizeInBytes 12288
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen : Givimg Permission 0777 mode , 0 ret
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen accept Start len 110 gAudioServerLocalSockFd 22
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen PLATFORM_AUDIO_DATA SIZE 24
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen PLATFORM_AUDIO_META_DATA SIZE 20
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen accept Start len 110 gAudioClientLocalSockFd 21
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen : Givimg Permission 0777 mode , 0 ret
W/ActivityManager( 764): Launch timeout has expired, giving up wake lock!
it maybe a hardware issue.
dial *#7353# and make test
I have a Pit Rom here
Factory_Firmware_Full_Wipe_I9505XXUBMGA_I9505OXXBMG3_NEE
and:
GT-I9505-Factory-Firmware-Full-Wipe-DBT I9505OXABMF8
But when i load that in Odin , i will become a error , invalid .....
Same is with that Rom (one File Rom)
I9505XXUBMEA_I9505OXABMEA_I9505XXUBMEA_HOME.tar.md5 is invalid
I can only flash 1 File Roms
<OSM> MD5 hash value is invalid
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is invalid.
<OSM> End...
no sound here too , here are log Files:
E/Encryption( 187): created DirEncryptionManager
D/Vold ( 187): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Encryption( 187): enable android secure container 'sdcard'
D/Vold ( 187): Volume sda state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdb state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdc state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdd state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sde state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdf state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): '/dev/block/mmcblk0' : disk_size (15758000128)
D/DirectVolume( 187): DirectVolume::readId -> path '/sys/devices/platform/msm_sdcc.2/mmc_host/mmc2/mmc2:e624/block/mmcblk1/device/cid'
D/DirectVolume( 187): DirectVolume::readId -> id '035344535530384780303189d800cab0'
D/DirectVolume( 187): DirectVolume::handleDiskAdded -> mDiskMajor 179, mDiskMinor 32, NPARTS:1
D/Vold ( 187): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/PackageManager( 766): Unknown permission com.sec.android.permission.VIDEOHUB in package com.sec.android.app.videoplayer
W/PackageManager( 766): Unknown permission android.permission.SYSTEM_ALERT in package com.sec.android.app.videoplayer
I have upload the LogFile, when you have time for that, you can look on that. Thanks
http://ul.to/k34sopfp
wolfsstolz said:
I have a Pit Rom here
Factory_Firmware_Full_Wipe_I9505XXUBMGA_I9505OXXBMG3_NEE
and:
GT-I9505-Factory-Firmware-Full-Wipe-DBT I9505OXABMF8
But when i load that in Odin , i will become a error , invalid .....
Same is with that Rom (one File Rom)
I9505XXUBMEA_I9505OXABMEA_I9505XXUBMEA_HOME.tar.md5 is invalid
I can only flash 1 File Roms
<OSM> MD5 hash value is invalid
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is invalid.
<OSM> End...
no sound here too , here are log Files:
E/Encryption( 187): created DirEncryptionManager
D/Vold ( 187): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Encryption( 187): enable android secure container 'sdcard'
D/Vold ( 187): Volume sda state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdb state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdc state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdd state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sde state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdf state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): '/dev/block/mmcblk0' : disk_size (15758000128)
D/DirectVolume( 187): DirectVolume::readId -> path '/sys/devices/platform/msm_sdcc.2/mmc_host/mmc2/mmc2:e624/block/mmcblk1/device/cid'
D/DirectVolume( 187): DirectVolume::readId -> id '035344535530384780303189d800cab0'
D/DirectVolume( 187): DirectVolume::handleDiskAdded -> mDiskMajor 179, mDiskMinor 32, NPARTS:1
D/Vold ( 187): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/PackageManager( 766): Unknown permission com.sec.android.permission.VIDEOHUB in package com.sec.android.app.videoplayer
W/PackageManager( 766): Unknown permission android.permission.SYSTEM_ALERT in package com.sec.android.app.videoplayer
I have upload the LogFile, when you have time for that, you can look on that. Thanks
http://ul.to/k34sopfp
Click to expand...
Click to collapse
sound wont work with older firmware even with the pit. you have to flash official updated firmware hard reset your device.also make sure its your phones official firmware.if that don't work try kies emergency firmware upgrade. hope this helps.
I want to build android-2.3.3_r1 branch from AOSP, to install and Multiboot it with Android 4.4 KK
I synced the repo, but I cannot "lunch".... What could I do to be able to "lunch"'?
EDIT: Tried to port Android 2.3.6 (GRK39F) factory image for Nexus S using PSX as base and PSX kernel but I got a bootloop (logcat said this once and again):
E/Sensors (10921): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors (10921): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors (10921): sns_pwr.c(488):sns_pwr_boot: DSPS device open failed err 19
E/Sensors (10921): sns_init_la.c(301):Error 5 initializing sns_pwr_init
E/Sensors (10921): sns_main.c(1476):Exiting! sensor1_init failed with 5
I/ServiceManager( 154): service 'media.audio_flinger' died
I/ServiceManager( 154): service 'media.player' died
I/ServiceManager( 154): service 'media.camera' died
I/Netd (10925): Netd 1.0 starting
W/InterfaceController(10925): Warning (dlopen failed: library "/system/lib/libne
tcmdiface.so" not found) while opening the net interface command library
I/mediaserver(10924): ServiceManager: 0x2a00b220
I/AudioFlinger(10924): Using default 3000 mSec as standby time.
I/CameraService(10924): CameraService started (pid=10924)
I/CameraService(10924): Loaded "Qcamera" camera module
I/QCameraHAL(10924): Handle base =0x0xb6270064
I/QCameraHAL(10924): getCameraInfo: numOfCameras = 2
I/QCameraHAL(10924): Handle [0]=0x0xb6270064
I/QCameraHAL(10924): Camera sensor 0 info:
I/QCameraHAL(10924): camera_id: 0
I/QCameraHAL(10924): modes_supported: 1
I/QCameraHAL(10924): position: 0
I/QCameraHAL(10924): sensor_mount_angle: 90
I/QCameraHAL(10924): Handle [1]=0x0xb62700a8
I/QCameraHAL(10924): Camera sensor 1 info:
I/QCameraHAL(10924): camera_id: 1
I/QCameraHAL(10924): modes_supported: 1
I/QCameraHAL(10924): position: 1
I/QCameraHAL(10924): sensor_mount_angle: 270
I/AudioPolicyManagerBase(10924): loadAudioPolicyConfig() loaded /system/etc/audi
o_policy.conf
D/audio_hw_primary(10924): adev_open: enter
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_INITIALIZE
E/ (10924): [ACDB RTC]->rtc init done!->result [0]
D/Diag_Lib(10924): actp_diag_init: call diag init function with B6014209
E/Diag_Lib(10924): Diag_LSM_Init: Failed to open handle to diag driver, error =
13
E/Diag_Lib(10924): actp_diag_init: diag init failed
E/ (10924): [ACDB ACPH]->actp diag init done!
D/ACDB-LOADER(10924): No existing ION info in ACDB driver
D/ACDB-LOADER(10924): ACDB -> ION_IOC_ALLOC
D/ACDB-LOADER(10924): ACDB -> ION_IOC_SHARE
D/ACDB-LOADER(10924): ACDB -> MMAP ADDR
D/ACDB-LOADER(10924): ACDB -> register MEM to ACDB driver: 0xb5e1a000
D/ACDB-LOADER(10924): ACDB -> send_asm_topology
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
D/ACDB-LOADER(10924): send mbhc data
D/ACDB-LOADER(10924): send tabla anc data
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 148
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 148
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 148
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 148
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 74
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 74
D/ACDB-LOADER(10924): ACDB -> init done!
D/ (10924): csd_client_init
E/ (10924): csd_client_service_init: Invalid rx device 0, setting to hand
set
E/ (10924): csd_client_service_init: Invalid tx device 0, setting to hand
set
E/QMI_FW (10924): xport_open: socket creation failed - 1
E/Diag_Lib(10924): Diag_LSM_Init: Failed to open handle to diag driver, error =
13
E/QMI_FW (10924): QMUXD: Service_id=20 not found over conn_id=0
E/QMI_FW (10924): QMUXD: Service_id=20 not found over conn_id=0
E/QMI_FW (10924): QMUXD: Service_id=20 not found over conn_id=0
E/QMI_FW (10924): QMUXD: Service_id=20 not found over conn_id=0
E/QMI_FW (10924): QMUXD: Service_id=20 not found over conn_id=0
D/audio_hw_primary(10924): adev_open: exit
I/AudioFlinger(10924): loadHwModule() Loaded primary audio interface from QCOM A
udio HAL (audio) handle 1
D/audio_hw_primary(10924): adev_open_output_stream: enter: sample_rate(44100) ch
annel_mask(0x3) devices(0x2) flags(0x2)
D/audio_hw_primary(10924): adev_open_output_stream: exit
I/AudioFlinger(10924): HAL output buffer size 240 frames, normal mix buffer size
960 frames
I/AudioMixer(10924): found effect "Multichannel Downmix To Stereo" from The Andr
oid Open Source Project
E/MonoPipe(10924): Failed to fetch local time frequency when constructing a Mono
Pipe (res = -32). getNextWriteTimestamp calls will be non-functional
D/MDnsDS (10925): MDnsSdListener::Hander starting up
D/MDnsDS (10925): MDnsSdListener starting to monitor
D/MDnsDS (10925): Going to poll with pollCount 1
Click to expand...
Click to collapse
bamsbamx said:
I want to build android-2.3.3_r1 branch from AOSP, to install and Multiboot it with Android 4.4 KK
I synced the repo, but I cannot "lunch".... What could I do to be able to "lunch"'?
Click to expand...
Click to collapse
It just won't work, don't try.
2.3.3? is that number correct?if so, then just build it will not work.
realfelix said:
It just won't work, don't try.
Click to expand...
Click to collapse
opssemnik said:
2.3.3? is that number correct?if so, then just build it will not work.
Click to expand...
Click to collapse
Ok, but why it wont work? i have tried to port Android 2.3.6 (GRK39F) factory image for Nexus S using PSX as base and PSX kernel... Got a bootloop
Logcat said there was an error with Netd and kept saying "going to poll with pollcount 1" once and again
bamsbamx said:
Ok, but why it wont work? i have tried to port Android 2.3.6 (GRK39F) factory image for Nexus S using PSX as base and PSX kernel... Got a bootloop
Logcat said there was an error with Netd and kept saying "going to poll with pollcount 1" once and again
Click to expand...
Click to collapse
Nexus 4 device tree and proprietary files are for jellybean. It simply isnt compatible with gingerbread.
Why don't you try with cupcake? You might have better luck with it...
Sent from my Nexus 4 using Tapatalk
it will not work without hard work because of s4 pro drivers are for 4.0.3+. since nexus 4 is packed with 4.2.2, u can build 4.1.2 or 4.0.4 or 4.0.3 and use lg og drivers.
BigDig said:
Why don't you try with cupcake? You might have better luck with it...
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I want to try GB because I need to test my apps
bamsbamx said:
I want to try GB because I need to test my apps
Click to expand...
Click to collapse
Then, try to use a virtual machine on your pc
luiseteyo said:
Then, try to use a virtual machine on your pc
Click to expand...
Click to collapse
I have been using Android emulator with AVD, but It seems to be a bit slow.
Also, as we have multiboot why not to try GB in our Nexus??
bamsbamx said:
I have been using Android emulator with AVD, but It seems to be a bit slow.
Also, as we have multiboot why not to try GB in our Nexus??
Click to expand...
Click to collapse
Yes, yes, I am part of the people that say that development is always helpful and appreciated, even if consists in building a previous android version.
Because there aren't drivers for it and Qualcomm isn't going to release them for GB.
sent via tapatalk
That would be like removing a Porsche engine to replace it with a Fiat cinquecento engine.
Sent from my Nexus 4 using xda app-developers app
we can at maxximum have 4.0.3 without any hard work. 2.3 is possible, but u need to "hack" the libs to make them for 2.3.
for 4.0.3 we use lg optimus g drivers(same chipset)
Oxious119 said:
That would be like removing a Porsche engine to replace it with a Fiat cinquecento engine.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Haha, no... It would be like having a Porsche engine and have much lighter car body
opssemnik said:
we can at maxximum have 4.0.3 without any hard work. 2.3 is possible, but u need to "hack" the libs to make them for 2.3.
for 4.0.3 we use lg optimus g drivers(same chipset)
Click to expand...
Click to collapse
Well for having 4.0.3, could we get it working by just flashing a 4.0.3 rom for lg optimus g?
Oxious119 said:
That would be like removing a Porsche engine to replace it with a Fiat cinquecento engine.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It is like having a Porsche and study how to make a Fiat Punto work with its engine. Just study, curiosity, its development, I think it's a great idea.
Anyway, @bamsbamx I would try to build 4.1 or 4.0, which will be much easier.
luiseteyo said:
It is like having a Porsche and study how to make a Fiat Punto work with its engine. Just study, curiosity, its development, I think it's a great idea.
Anyway, @bamsbamx I would try to build 4.1 or 4.0, which will be much easier.
Click to expand...
Click to collapse
Well, but which device should I select to build?
After building, from where can I get those drivers?
I dont know to much about building
I know, I wasn't trying to discredit your effort.
Sent from my Nexus 4 using xda app-developers app
bamsbamx said:
Haha, no... It would be like having a Porsche engine and have much lighter car body
Well for having 4.0.3, could we get it working by just flashing a 4.0.3 rom for lg optimus g?
Click to expand...
Click to collapse
no, we cant use their kernel, we need to use our kernel, but edit ramdisk for ics.and if u porting from their kernels u need to change partition layout.
P.S: we also need to remove libs from their roms. and modify some things. so it would be way easier just to use their s4 pro libs with our builded ics.i tried their stock 4.1.2 it booted,(imodified ramdisk and removed some libs, and little tweaks to vold.fstab and framework). but my hdd failed so i lost everything and my phone is on repair.
opssemnik said:
no, we cant use their kernel, we need to use our kernel, but edit ramdisk for ics.and if u porting from their kernels u need to change partition layout.
P.S: we also need to remove libs from their roms. and modify some things. so it would be way easier just to use their s4 pro libs with our builded ics.i tried their stock 4.1.2 it booted,(imodified ramdisk and removed some libs, and little tweaks to vold.fstab and framework). but my hdd failed so i lost everything and my phone is on repair.
Click to expand...
Click to collapse
ok then, where could I get their S4 pro libs?
EDIT: This has been resolved. Updating vendor blobs and device trees fixed the issue. Thank you for your time.
Greetings Developers,
I would really appreciate some help. By God's grace, in the T-Mobile S4 development thread http://forum.xda-developers.com/galaxy-s4-tmobile/development/rom-pac-rom-mm-t3400111 , I have put together several Marshmallow Roms, namely PAC Rom and AOKP MM, that have the same problem. The camera works to take pictures, but cannot record video. It "appears" to be recording in the built in camera app, but does not actually save the recording. If I use another app, such as OpenCamera, it stops the recording as soon as I try to start. I am relatively new to development, and any help would be greatly appreciated, as well as fully recognized and credited.
Below is the logcat errors/fails when using the CM camera app, and the OpenCamer app. I just really want to get this fixed for the people who are using the roms. I hate to sell them short because I've made some sort of error.
In my inexperienced opinion, this appears to be an audio problem. I have compared the mediarecorder.cpp and similar files between CM13 and my roms, and they are identical. I was wondering if it might be vendor blobs, so I borrowed them from Beanstalk (where the camera video recorder function works), but that did not work either.
I am pretty sure that it is not the app, because using any video recording app fails to actually record the video.
Code:
Here are the fails from the logcat. I am only focusing on the errors, stops, or fails.
Using the built in Camera app:
07-12 06:43:32.459 244 3766 I MediaCodecSource: encoder (audio) stopped
07-12 06:43:32.459 244 652 I MediaCodecSource: puller (audio) stopping
07-12 06:43:32.461 244 3847 E OMXNodeInstance: setConfig(1d:google.vorbis.decoder, ConfigPriority(0x6f800002)) ERROR: Undefined(0x80001001)
07-12 06:43:32.461 244 3847 I ACodec : codec does not support config priority (err -2147483648)
07-12 06:43:32.462 244 3847 I MediaCodec: MediaCodec will operate in async mode
07-12 06:43:32.467 244 3846 I NuPlayerDecoder: [OMX.google.vorbis.decoder] resubmitting CSD
07-12 06:43:32.468 244 3846 I NuPlayerDecoder: [OMX.google.vorbis.decoder] resubmitting CSD
07-12 06:43:32.469 244 3775 D ALSAStreamOps: setParameters(): keyRouting with device 0x0
07-12 06:43:32.469 244 3775 E ALSAStreamOps: must not change mDevices to 0
07-12 06:43:32.470 244 3775 D AudioStreamInALSA: standby
07-12 06:43:32.470 244 3775 D AudioStreamInALSA: standby
07-12 06:43:32.470 244 3775 D ALSADevice: standby: handle 0xb216c1c0 h 0x0
07-12 06:43:32.472 244 3848 W SoftVorbis: vorbis_dsp_synthesis returned -135
07-12 06:43:32.473 244 3848 W SoftVorbis: vorbis_dsp_synthesis returned -135
07-12 06:43:32.500 3612 3612 E MediaRecorder: stop failed: -1007
07-12 06:43:32.502 3612 3612 E CAM_VideoModule: java.lang.RuntimeException: stop failed.
07-12 06:43:33.984 244 3647 W AMessage: failed to post message as target looper for handler 0 is gone.
Using the OpenCamera App for comparison:
07-12 06:50:28.951 244 4439 E ACDB-LOADER: Error: ACDB EC_REF_RX returned = -8
07-12 06:50:28.976 244 4436 E SoftAVCEnc: Error in extractGraphicBuffer
07-12 06:50:28.976 244 4435 E ACodec : [OMX.google.h264.encoder] ERROR(0x80001001)
07-12 06:50:28.976 244 4435 E ACodec : signalError(omxError 0x80001001, internalError -2147483648)
07-12 06:50:28.976 244 4435 E ACodec : [OMX.google.h264.encoder] ERROR(0x80001001)
07-12 06:50:28.976 244 4435 E ACodec : signalError(omxError 0x80001001, internalError -2147483648)
07-12 06:50:28.977 244 4434 E MediaCodec: Codec reported err 0x80001001, actionCode 0, while in state 6
07-12 06:50:28.977 244 4439 D ALSADevice: setHardwareParams: buffer_size 16384, period_size 4096, period_cnt 4
07-12 06:50:28.977 244 4431 E MediaCodecSource: Encoder (video) reported error : 0x80001001
07-12 06:50:29.124 4180 4180 E MediaRecorder: stop failed: -1007
So, the errors or fails that are the same are these:
ACDB-LOADER: Error: ACDB EC_REF_RX returned = -8
MediaRecorder: stop failed: -1007
These are both audio errors. It appears that the audio is creating an error, so the video will not save. Unless someone out there knows better (be sure to correct me, I'm still learning). So I will be looking at MediaRecorder and ACDB-LOADER and audio problems.
Once again, any assistance would be greatly appreciated! Thanks!
Guyz,
I have A PAC ROM in My Lenovo Vibe K5 (GAPPS PICO PACKAGE INSTALLED) and The Rear Camera isn't working....
SPECS- Arm64
Android 6.0
Tell me how to fix this problem???????????????