Related
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
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?
Hi currently im building omnirom for GT-I9205,
Im having some issue with the bluetooth,
i can confirm the bluetooth will work in this device (work on CM11 base source).
here is my logcat, hoping someone will point me to correct direction
Code:
D/BluetoothManagerService( 914): BluetoothServiceConnection: com.android.bluetooth.btservice.AdapterService
D/BluetoothManagerService( 914): Message: 40
D/BluetoothManagerService( 914): MESSAGE_BLUETOOTH_SERVICE_CONNECTED: 1
---
D/BluetoothPanServiceJni( 1650): initializeNative(L110): pan
D/BluetoothTethering( 914): got CMD_CHANNEL_HALF_CONNECTED
E/BluetoothTethering( 914): Trying to set mAsyncChannel twice!
---
I/bluedroid( 1650): enable
I/bt_hci_bdroid( 1650): init
I/bt_vendor( 1650): bt-vendor : init
I/bt_hwcfg( 1650): Starting hciattach daemon
I/bt_hwcfg( 1650): try to set false
I/bt_hwcfg( 1650): Starting hciattach daemon
I/bt_hwcfg( 1650): try to set true
I/bt_hci_bdroid( 1650): bt_hc_worker_thread started
I/qcom-bluetooth( 3318): /system/etc/init.qcom.bt.sh: init.qcom.bt.sh config =
I/qcom-bluetooth( 3324): /system/etc/init.qcom.bt.sh: Transport : smd
I/qcom-bluetooth( 3325): /system/etc/init.qcom.bt.sh: ** Bluedroid stack **
I/qcom-bluetooth( 3332): /system/etc/init.qcom.bt.sh: Power Class: Ignored. Default(1) used (1-CLASS1/2-CLASS2/3-CUSTOM)
I/qcom-bluetooth( 3333): /system/etc/init.qcom.bt.sh: Power Class: To override, Before turning BT ON; setprop qcom.bt.dev_power_class <1 or 2 or 3>
I/qcom-bluetooth( 3334): /system/etc/init.qcom.bt.sh: LE Power Class: Ignored. Default(2) used (1-CLASS1/2-CLASS2/3-CUSTOM)
I/qcom-bluetooth( 3335): /system/etc/init.qcom.bt.sh: LE Power Class: To override, Before turning BT ON; setprop qcom.bt.le_dev_pwr_class <1 or 2 or 3>
I/qcom-bluetooth( 3340): /system/etc/init.qcom.bt.sh: Bluetooth QSoC firmware download succeeded,
I/qcom-bluetooth( 3341): /system/etc/init.qcom.bt.sh: ** Bluedroid stack **
I/bt_hwcfg( 1650): bluetooth satus is on
I/bt_userial_vendor( 1650): Done intiailizing UART
I/bt_userial_vendor( 1650): Done intiailizing UART
E/bt_userial( 1650): userial_open: wrong numbers of open fd in vendor lib [2]!
E/bt_userial( 1650): userial_open: HCI UART expects only one open fd
I/bt_vendor( 1650): Bluetooth Firmware and smd is initialized
I/GKI_LINUX( 1650): gki_task_entry: gki_task_entry task_id=0 [BTU] starting
I/bt-btu ( 1650): btu_task pending for preload complete event
I/bt-btu ( 1650): btu_task received preload complete event
I/ ( 1650): BTE_InitTraceLevels -- TRC_HCI
I/ ( 1650): BTE_InitTraceLevels -- TRC_L2CAP
I/ ( 1650): BTE_InitTraceLevels -- TRC_RFCOMM
I/ ( 1650): BTE_InitTraceLevels -- TRC_AVDT
I/ ( 1650): BTE_InitTraceLevels -- TRC_AVRC
I/ ( 1650): BTE_InitTraceLevels -- TRC_A2D
I/ ( 1650): BTE_InitTraceLevels -- TRC_BNEP
I/ ( 1650): BTE_InitTraceLevels -- TRC_BTM
I/ ( 1650): BTE_InitTraceLevels -- TRC_GAP
I/ ( 1650): BTE_InitTraceLevels -- TRC_PAN
I/ ( 1650): BTE_InitTraceLevels -- TRC_SDP
I/ ( 1650): BTE_InitTraceLevels -- TRC_GATT
I/ ( 1650): BTE_InitTraceLevels -- TRC_SMP
I/ ( 1650): BTE_InitTraceLevels -- TRC_BTAPP
I/ ( 1650): BTE_InitTraceLevels -- TRC_BTIF
W/qdhwcomposer( 215): Excessive delay reading vsync: took 3945 ms vsync_period 33 ms
D/BluetoothAdapterState( 1650): CURRENT_STATE=PENDING, MESSAGE = ENABLE_TIMEOUT, isTurningOn=true, isTurningOff=false
E/BluetoothAdapterState( 1650): Error enabling Bluetooth
i think the problem is most likely due to >> userial_open: wrong numbers of open fd in vendor lib [2]!
what exactly is "fd"?
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...