OFW 2.1.7: Custom launcher won't set as default.

[Mount81]

Hello!

So I have installed this ATV launcher and everything works till the next reboot, than the launcher is set back to HiMedia's default. How can I make the custom launcher permanent?

There was no trouble with this in OFW 2.1.1, so is there some magic trick I must do on 2.1.7?

Thank you!

[pcristi]

Try copy OvLauncher.apk from Lite-CFW-HMD-2.1.4 to your box via adb or root on /system/app/OvLauncher/OvLauncher.apk.

[Mount81]

Thanks!
So it must be:

Code: [Select]

adb connect <ip_player>
adb root
adb connect <ip_player>
adb remount
adb push OvLauncher.apk /system/app/OvLauncher/OvLauncher.apk
adb reboot

And do I need to save/backup the original launcher first from the Box via adb, in case it doesn't work well? Or how  can I revert to the original 2.1.7 launcher if I want to?

Code: [Select]

adb connect <ip_player>
adb root
adb connect <ip_player>
adb remount
adb pull /system/app/OvLauncher/OvLauncher.apk
adb reboot
Can the code above work for this? Or any other steps?

Edit: I have managed to do the swap, now the launcher can be changed.

[Mount81]

Another issue with 2.1.7 (I just don't wanted to open a new thread) is that the wallpaper constantly resets to blank black sometimes by itself. It was somewhat the same even with OFW 2.1.1, but I guess with 2.1.7 it happens more often, mostly after reboot. Is there anything I can do to stop this happening? A patch maybe, or a third party app?

TY!

[pcristi]

I don't use OFW but back wallpaper is come from /system/framework-res.apk/res/drawable-sw720dp-nodpi-v13/default_wallpaper.png
Can you try to over set on build.prop
ro.config.wallpaper=/system/etc/default_wallpaper.png
and push from adb your favorite wallpaper on /system/etc/default_wallpaper.png

Code: [Select]

adb connect <ip_player>
adb root
adb connect <ip_player>
adb remount
adb pull /system/build.prop
add with notepad++ on end of build.prop ro.config.wallpaper=/system/etc/default_wallpaper.png

Code: [Select]

adb connect <ip_player>
adb root
adb connect <ip_player>
adb remount
adb push build.prop /system/build.prop
adb push default_wallpaper.png /system/etc/default_wallpaper.png
adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/etc/default_wallpaper.png
adb reboot
If like this not solve then try edit on framework-res.apk, resign with platform key and push back via adb.
Don't forget to make backup, backup, backup because touch build.prop/framework-res.apk can end on loop, then OFW need to reinstall with paper clip.
Enjoy moding of OFW.

[Mount81]

Well thanks, but it takes a lot of consideration to do such a in-depth modification. Can only the first method also cause system errors?

BTW, back to the previous: After this modification (quoted under) the first video playback ended in freeze of HiMedia player, than I have to reboot and the second time it played normally. I didn't tested much exhaustingly, it was only one video, and hope this is not some kind of result of either the launcher, nor the power menu mod i have just installed.

 

Thanks!
So it must be:

Code: [Select]

adb connect <ip_player>
adb root
adb connect <ip_player>
adb remount
adb push OvLauncher.apk /system/app/OvLauncher/OvLauncher.apk
adb reboot

And do I need to save/backup the original launcher first from the Box via adb, in case it doesn't work well? Or how  can I revert to the original 2.1.7 launcher if I want to?

Code: [Select]

adb connect <ip_player>
adb root
adb connect <ip_player>
adb remount
adb pull /system/app/OvLauncher/OvLauncher.apk
adb reboot
Can the code above work for this? Or any other steps?

Edit: I have managed to do the swap, now the launcher can be changed.

[saltino]

Hi at all,
some problem with offical firmware 2.1..7 and external launcher
for now I have resoved (poor and dirty) with automatic execution of installed launcher at startup with MENU setup key

but isn't clean solution

I'm on rooted 2.1.7, will try to investigate on /system/app/XXXLauncher/XXXLauncher.apk (XXX I don't know righr name of default official firmware launcher APK)

I presume that is:  com.hitv.launcher

Code: [Select]

android
android.ext.services
android.ext.shared
com.android.CaSettings
com.android.PreBurning
com.android.backupconfirm
com.android.bluetooth
com.android.bookmarkprovider
com.android.certinstaller
com.android.cts.ctsshim
com.android.cts.priv.ctsshim
com.android.defcontainer
com.android.diagtest
com.android.documentsui
com.android.egg
com.android.emergency
com.android.externalstorage
com.android.htmlviewer
com.android.inputdevices
com.android.keychain
com.android.location.fused
com.android.packageinstaller
com.android.pacprocessor
com.android.phone
com.android.printspooler
com.android.providers.blockednumber
com.android.providers.calendar
com.android.providers.contacts
com.android.providers.downloads
com.android.providers.downloads.ui
com.android.providers.media
com.android.providers.settings
com.android.providers.userdictionary
com.android.proxyhandler
com.android.settings
com.android.sharedstoragebackup
com.android.shell
com.android.smart.terminal.iptv.aidl
com.android.statementservice
com.android.systemui
com.android.vending
com.android.vpndialogs
com.android.wallpaperbackup
com.android.wallpapercropper
com.android.webview
com.explorer
com.google.android.backuptransport
com.google.android.configupdater
com.google.android.ext.services
com.google.android.ext.shared
com.google.android.feedback
com.google.android.gms
com.google.android.gsf
com.google.android.gsf.login
com.google.android.onetimeinitializer
com.google.android.partnersetup
com.google.android.syncadapters.calendar
com.google.android.syncadapters.contacts
com.google.android.tts
com.himedia.android.videoplayer
com.himedia.channeltv
com.himedia.hmdupgrade
com.himedia.imageslideshow
com.himedia.lan
com.himedia.mediacenterentrance
com.himedia.music
com.himedia.nfs
com.himedia.packinstall
com.himedia.usb
com.himedia.wallposter
com.hisilicon.android.gallery3d
com.hisilicon.android.hiRMService
com.hisilicon.android.inputmethod.latin
com.hisilicon.android.pqsetting
com.hisilicon.android.videoplayer
com.hisilicon.dlna.dmp
com.hisilicon.dlna.dmr
com.hisilicon.dlna.dms
com.hisilicon.miracast
com.hisilicon.multiscreen.server
com.hisilicon.multiscreen.vime
com.hitv.explorer
com.hitv.launcher
com.hitv.lib
com.hitv.locker
com.hitv.newappmanager
com.hitv.process
com.hitv.statistics.service
com.hitv.tv.settings
com.svox.pico
eu.chainfire.supersu
eu.chainfire.supersu.pro



Thx & bye

[pcristi]

Well thanks, but it takes a lot of consideration to do such a in-depth modification. Can only the first method also cause system errors?

Always editing/change/update/OFW/CFW/etc are risk to get end in boot loop then request to reinstall FW with paper clip. But to answer to your question first method have less chance to end on boot loop.
Enjoy HiMedia players.

[saltino]

Great! Thx.
I'm resolve with root and root explorer

substitution my *.apk lancher from /app/myLauncher/app.apk with /system/app/OvLauncher/OvLauncher.apk
That's all

boot perfect from 24h

[pcristi]

Corect copy OvLauncher.apk with Root explorer over original /system/app/OvLauncher/OvLauncher.apk are also good option on rooted box  .
Nice to hear your box is stable, enjoy.
 

[Mount81]

I don't use OFW but back wallpaper is come from /system/framework-res.apk/res/drawable-sw720dp-nodpi-v13/default_wallpaper.png
Can you try to over set on build.prop
ro.config.wallpaper=/system/etc/default_wallpaper.png
and push from adb your favorite wallpaper on /system/etc/default_wallpaper.png

Code: [Select]

adb connect <ip_player>
adb root
adb connect <ip_player>
adb remount
adb pull /system/build.prop
add with notepad++ on end of build.prop ro.config.wallpaper=/system/etc/default_wallpaper.png

Code: [Select]

adb connect <ip_player>
adb root
adb connect <ip_player>
adb remount
adb push build.prop /system/build.prop
adb push default_wallpaper.png /system/etc/default_wallpaper.png
adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/etc/default_wallpaper.png
adb reboot
If like this not solve then try edit on framework-res.apk, resign with platform key and push back via adb.
Don't forget to make backup, backup, backup because touch build.prop/framework-res.apk can end on loop, then OFW need to reinstall with paper clip.
Enjoy moding of OFW.

So I have now finally done it and confirm, that this method is working. Once the "pull" part is done, one should only do to change the wallpaper is make batch file for the "push" part and place and rename any custom wallpaper he wants in that folder where bat file is launched from.