yashsingh1/xdaforums huggingface dataset:
[Greenify] hyborian:
I really don't understand why you are using Greenify to go to an app and click force stop ... Why not just go directly to the MIUI settings and force stop it there ?

Anyway, on all my 4 Xiaomis, with the latest and greatest MIUI 10 8.9.2 Developer ROM as at this date, Greenify works perfectly.

Apps under Hibernation are as expected when viewed from the MIUI Settings, they are already Force Closed (Force Close button greyed out), with the Uninstall button available (not greyed out).

Under MIUI Settings, apps under Shallow Hibernation are not Force Closed, and clicking on the button Force Close will force close it and the button becomes greyed out, and after that, the Uninstall button will be ungreyed and available. When you go back to Greenify, the previously shallow hibernated app that was force closed is now under the section of the normal hibernation, no longer under shallow hibernation.

All fine on my side, MM and Nougat Xiaomis, I don't know about Oreo. I think Greenify is still needed for Xiaomi with Oreo, since Xiaomi seems to walk a different path than the others.
[Greenify] akhu5:
I have over 200 apps in my phone. So there are a lot of apps that need to be 'greenified'. And I've noticed that if you go into developer settings and disable 'miui optimisations', then greenify works perfectly. But for the rest, even if the app is open in the background and you select the option to hibernate it, the force close button is greyed out and nothing happens
[Greenify] hyborian:
Oh, yes, I forgot, of course I have MIUI OPtimizations disabled, always, less problems for me. All rooted too, with Greenify4Magisk, and some module to allow Play Services to be dozed.

Well, if an app cannot be force closed in the MIUI settings, then it is something else preventing it from being closed, and Greenify cannot override it. Gboard (Google Keyboard if used) I think is an example, if I remember. Only a few, and system apps which I would not touch anyway. I don't greenify important user message apps like Messenger or Whatsapp, though, I also Whitelist them from deep doze, just playing safe.

Excluding system apps, I have only a few user apps, less than 40 for sure. All greenified except a few I don't want greenified. As for system apps,

I froze many of them that I will never use and safe to freeze of course, surely stronger than doze or hibernate.
[Greenify] DB126:
Ridiculous and counterproductive greenifying a huge app suite. Focus on those that demonstrate bad behaviors; ignore the rest.
[Greenify] Sophia.xda:
Not Hibernating Automatically Apps on Greenify phone is rooted SU, android 7.0.1 but why the apps are not auto hibernate only few that comes on that tabs Not Hibernating Automatically and how to fix all appps will automatically hibernate... please help...

---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------

https://u.cubeupload.com/2017/Screenshot2018122820.jpg
[Greenify] TNSMANI:
Not one or two but four identical posts in four different threads is really taking it too far.
[Greenify] Anonymous110:
Solution

Just turn of MIUI Optimisation in Developer Options.
[8125, K-JAM, P4300, MDA Vario General] ihabdawood:
Dear all,

I have imate k-jam with Black diamond 3.1 software.

I was inquiring about GPS software, i have GPRS connection.

I have google maps but it seems it locates me in the wrong location.

Thank you
[8125, K-JAM, P4300, MDA Vario General] sariel2413:
Well, get yourself any sirfstar III bluetooth GPS toy. It'll get your position without any problems. Also, don't use google maps to find your location unless you just LOVE paying through the nose for the GPRS traffic. I used it for a few minutes on WLAN and it already ate up several megabytes of data for the satpics...and megabytes over GPRS is really expensive...
[LeEco Le Pro3 Questions & Answers] kielpogi28:
.i flash a chinese stock rom thru twrp and got stuck in bootlogo cant access the twrp now,i can access the fastboot but the bootloader is lock i cant flash twrp

what will i do?
[LeEco Le Pro3 Questions & Answers] mchlbenner:
Their is not fix for this you have read and study for doing this.
[LeEco Le Pro3 Questions & Answers] sk8223:
I don't know where you came from, but you should have read this sticky in this forum before attempting anything: https://xdaforums.com/le-pro3/help/x722-owners-read-flashing-device-t3736091

You most likely flashed stock 26s or the WIXCNFN5802005041S firmware ROM through TWRP, both of which permanently lock the bootloader.

The only way to fix your phone now is to get the x722's QFIL file, which is not available anywhere, even China. The x720's QFIL file does not work for the x722. Join the thread here: https://xdaforums.com/le-pro3/leeco...velopment--and-mods/try-unbrick-x722-t3686191
[FYT Android Head Units] gtxaspec:
Reserved for TWRP instructions.
[FYT Android Head Units] gtxaspec:
Issues:

-Unable to send text message via google voice app using Pulse SMS, error is "Message couldn't be sent" // If anyone has a fix for this, please let us know

-Google Assistant doesn't work, launching activity manually results in "The Google Assistant doesn't work on this device" / You can fix this by changing the resolution to at least 720. use the command wm size to change the screen resolution or another tool that can change DPI

Release History:

custom helper:

V4_1: Fixed installation issue from micro sd cards.

V4_2: Check OS build fingerprint, will deny install unless you are on 20171215 or later.

V4_3: Updated text on installation screen for easier reading, Updated build detection logic

V4_4: Fixed bug in build detection logic

V4_5: Added no_data_wipe, translations included.

V4_6: fixed reboot to twrp not extracting recovery ota.

V4_7: lbug fixed

V4_8: script improvements

V4_9: prepare for re-write, added performance mode

ROM:

V4: Replaced opengapps with nano version

V5: Updated to 01-10 AOSP Base, Added bluetooth build property from [MENTION=2550900]surfer63[/MENTION], more optimizations.

V6: Added Navi APK, more optimizations, CANBUS firmware included, various stability fixes, ability to "dirty flash", mcud included to prevent bootloops during app optimization, works with 800x600 units now, fixed overlay bug, faster first boot, added ViPER4ANDROID, added USB audio policy modifications.

V7: Fixed LED issues and AMP Options. Updated GAPPS base to 20180226, might need to optimize apps on first boot if you are dirty flashing. Added fyt.prop to /system/app fix various issues.

V8: Changes in the way the installer handles re-installation of stock recovery for disaster recovery situations in which the installation fails and custom recovery remains installed, changed installation logic to to compensate for faulty installation media, twrp bug fixes, fixed twrp restart loop, clear FYT flags on twrp start.

V9 alpha 1:

updated recovery busybox to 1.27

fixed SYU file manager not found in CM Settings

fixed right camera not displaying

updated MCUd build to co-exist with sofia server

eliminate audio pops during rebooting

updated gtx_installer

updated dalvik cache

fixed recovery_maintenance.sh in system and recovery envrionments

recovery maintenance.sh is now functional from recovery console

updated clean_rom.sh

permissions overlay fixed

fixed script logic in install-recovery on 6021 units

include terminal app APK

added nano x86 editor

added network_up.sh to ensure debug network access and SU daemon is always run

v9_alpha_2:

fixed drm video black screen issue

added rom version information to fyt_build.prop

sofiaserver runs audio through all channels during call

v9_alpha_3:

xposed module to prevent xposed from updating framework causing bootloops

added remount command to path

added display calibration app to launcher

include both 5_25 and 9_20 versions of McuUpdateAll.bin in /system/mcu/ (copy the corresponding version to /system/mcu)

keep JET and other apps as user to ease upgrade
[FYT Android Head Units] surfer63:
V3 Rom link not working?
[FYT Android Head Units] gtxaspec:
Just finished upload, Try now.
[FYT Android Head Units] surfer63:
Yes, works fine. Sorry for clicking the links too early :)

I can't do anything with it now, but a link is so easily clicked.
[FYT Android Head Units] usa911g:
my joying head units have an internal amp, can I use this ROM?
[FYT Android Head Units] surfer63:
Yes, no problem at all. If there are bugs we will share them all. Nothing specific for amp or no-amp models.
[FYT Android Head Units] usa911g:
because the EQ app for amp or non-amp models is different, so I concern that
[FYT Android Head Units] surfer63:
Actually it is one and the same app with different screen-layouts and functionality depending on the hardware.
[FYT Android Head Units] gtxaspec:
The digital amp software is included.
[FYT Android Head Units] sanangel:
Reserved.

As soon as I have time I will try this rom
[FYT Android Head Units] gtxaspec:
the russian hackers at 4pda are using the following build.prop mods, anyone care to chime in? if they actually do something, I will include them.

ro.rk.install_non_market_apps=true
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
persist.telephony.support.ipv4=1
persist.telephony.support.ipv6=1
persist.sys.purgeable_assets=1
ro.wifi.channels=14

media.stagefright.enable-http=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
[FYT Android Head Units] surfer63:
I have no idea about the build props.

The custom V3 app did install the recovery image in one go. I do not know whether you improved something or the previous time was a glitch on my system when it gave that verification error.

I installed the V3 ROM. It works fine. It seems indeed faster than the original joying stock rom.

From what date are the GAPPS? The unit is trying to update all gapps. It is not really useful to have everything pre-odexed for a quick start (and it really is a quick start), when it immediately starts updating once you have finished the Google account setup.

(I myself also prefer the GAPPS micro package. I don't need and want google photos, youtube, google fit, etc. on my head unit.)

My JET apk is only partly working. At this moment I do not know why.

Replacing apps with mods (radio, BT, sofiaserver) works again now the apps are installed in /system/app

Copying the launcher.sh to /data does work. The launcher.sh works with the SofiaServer keymod as well as with the Xposed module sofiaservercustomkeymod (the one that uses the launcher.sh).

Installing a newer version ór installing one of the xposed modules currently doesn't work as it requires the package installer. The default package installer has been replaced by the googlepackageinstallers from the gapps. As such I can easily work around it by simply writing the apps to their folder in /system/apps. As soon as I upload my modules to the global xposed repository it is no problem anymore anyway as the Xposed installer can install it. I will still looking into why that one can install and my app not. I will also uninstall the google installer and replace it with the default package installer and see what happens.

And with regard to the customkeymod xposed module with settings screen: The settings screen itself works fine, but I still can't use the settings from my app. They stay empty.
[FYT Android Head Units] gtxaspec:
Ok, if you think the microgapps is lighter I can cook that in.
[FYT Android Head Units] joshnat:
You might even consider nano or pico gapps and let users just install whatever else they need manually.
[FYT Android Head Units] gtxaspec:
I'll do nano on v4 release which will be out tonight.
[FYT Android Head Units] edit:
Is Viper4Android working on this ROM?

Some time ago you said that you will investigate why is not working on the stock Joying but you never returned with an answer, can you please share your findings if you have any?

Thank you !

---------- Post added at 07:05 AM ---------- Previous post was at 07:03 AM ----------

I second this .... I also prefer things kept extremely simple !
[FYT Android Head Units] gtxaspec:
haven't tested viper. I will install it tonight and test it tomorrow morning on my drive.
[FYT Android Head Units] yuvalmesika:
The lights of the buttons?

It happens to me too, but it turns off eventually.

I found out that if I turn of the lights before the car switch it will turn off the head unit lights.

Turn the switch on, then turn the car lights off then turn the switch off.
[FYT Android Head Units] ptolomeo:
Yes, the lights of the buttons.

I was going to go to the car again to check the lights... thank you for the trick!
[FYT Android Head Units] surfer63:
This sometimes happens when a program could notbe stopped immediately. Check again after 4-5 minutes. If they have switched off, you do not need to worry.
[FYT Android Head Units] ptolomeo:
Confirmed, everything was off after some minutes... Thank you!!
[FYT Android Head Units] skurtov:
Is there USB DAC support? Or is it really not worth the extra effort?
[FYT Android Head Units] joshnat:
Still working on getting this set up, but a couple observations:

1. I had the same overlay warning on first boot. Unticking and ticking the overlay module and rebooting solved it.

2. When trying to change the canbus setting in car settings, the unit reports that it can't find the canbus files to update. I'm trying to change to a VW setting.

3. I rebooted into TWRP at one point after the install (and after reflashing TWRP from the custom app). When trying to reboot to System, it rebooted into TWRP. I had to push the reset button with a toothpick and let it fail to reboot 3 times before it successfully rebooted to Android.

Otherwise fantastic job! We all really appreciate your enthusiasm and your hard work!
[FYT Android Head Units] gtxaspec:
i have control of the sound processor without removing sofia server via command line...!
[FYT Android Head Units] edit:
It sounds great but can you please explain the benefits of having that?
[FYT Android Head Units] gtxaspec:
If you would like to mix android audio, WHILE listening to AMFM radio ( like for navigation ) then:

i2cset -f -y 4 0x40 0x30 0x8A

this sets mixer volume (register 30) to -10db. you get all android audio as well as FM RADIO. Is this information useful? Hmm...maybe, we need to make an Xposed module to do the mixing. Sofia server SHOULDN'T do any mixing aside from radio. Sofia server should always enable RADIO mixing, and RADIO should be killed by exiting the radio app using the back key.

When you use that command, google maps automatically lowers the volume of the AMFM, was this always happening?

Also, another thing I always thought was annoying, yet was available in the lbdroid custom rom, phone call audio was only audible on the front speakers, no more!

#enable rear left speakers for phone

i2cset -f -y 4 0x40 0x2b 0x84

#enable rear right speaker for phone

i2cset -f -y 4 0x40 0x2a 0x84
[FYT Android Head Units] gtxaspec:
[MENTION=2550900]surfer63[/MENTION] how do you repack and sign the sofiaserver apk's? i want to make a build script that could replace the built-in strings file for translations and corrections out of all the syu/fyt apk's, recompile the APK, and resign them automatically.
[FYT Android Head Units] petro_ionut:
Great ROM, blazing fast, but keys light doesn't react to switching on/off cars interior illuminating! Car model it is set to RZC XP(L), cannot change it as well!
[FYT Android Head Units] gtxaspec:
Do you have can bus? Did you try setting the lantern setting to small light control?

You are unable to change the canbus vehicle in settings?
[FYT Android Head Units] dyabolikarl:
I get a similar thing. Lights stay on for approx 2-3 minute after switch off.

The light control works for dimming though.

Small light control enabled.

Not a huge issue though as long as it does not kill the battery.
[FYT Android Head Units] petro_ionut:
Yes, Yes and when trying to change car model i got an error, i have been set car model before installing GTX rom!
[FYT Android Head Units] dyabolikarl:
I never got how to do the canbus thing... I have standard canbus and a custom swc box for the kia forte (cerato) but no idea how the canbus thing works or what is needed for it.
[FYT Android Head Units] ptolomeo:
I'm trying to install "Car Web Guru" Launcher (my favorite one), but when it's analyzing permissions, it says something like "Screen overlay detected: to change this permission setting you first have to turn off the screen overlay from Settings -> Apps".

How ever, I don't find any "Screen" item... what do I have to disable exactly?
[FYT Android Head Units] IG_Vasilich:
Have you disabled Android Assistant, coming with Joying units? It is that "half-transparent square with rounded corner-thing" on stock ROM.
[FYT Android Head Units] ptolomeo:
On this GTX ROM, the anoying circle doesn't appear. There is nothing like 'Android Assistant'.

In the 'Draw over other apps" section, I see:

Aux

Bluetooth

Car Info

Car settings

CarMark Settings

Cellular data

Google Play services

Launcher

Launcher3

Launcher3

MainServer

PlatformServer

Radardroid

Radio

Right Camera

Subserver

System UI

Touch Screen Study

UI Server
[FYT Android Head Units] derschnelle:
We discussed this issue a few pages back. Try de- and reactivating the overlay module in xposed.
[FYT Android Head Units] surfer63:
You cannot and must not resign the sofiaserver apk. It is a system apk.

When working on the sofiaserver apk you should use the correct framework for that firmware version.

So from your V5 ROM (for example), extract the framework-res.apk (/system/framework/framework-res.apk)

Then do a:

apktool if <path/to/>framework-res.apk

This will overwrite the default android framework that will be good for almost anything (including the radio apk for example), but not for the real joying system apks.

then do with the SofiaServer from that same firmware:

apktool d Sofia-1-C9-Server-V1.0.apk

make the modifications and do the

apktool -c b Sofia-1-C9-Server-V1.0.apk

Done!
[FYT Android Head Units] Haegar333:
Problems Flashing

Hello,

did anybody test this ROM on a 1G/16G version?

I have a 6" 1G Ram single DIN version of the joying radios.

I tried to install this ROM but didnt have luck.

I started with the newest joying ROM installed.

First try:

- tried to flash the custom recovery with custom app. At first i got an error that it didnt install, at second try it installed, a verify said good.

After flashing the rom it wasnt right... it started, but all the integrated apps were missing. Did a reboot (or 2, dont remember), that changed nothing.

Second try:

- Flashed the Joying rom again.

This time TWRP installed flawless.

Flashing GTX rom succeeded, but at Boot after the new android animation i get a grey screen for a few second and then it loops and boots again.

Did anybody encounter this?

I am back to stock Rom now, but want to use the GTX of course.
[FYT Android Head Units] luismiguelmimi:
Hello, how are you? I need some help, I followed the installation as it comes in the forum, and I have also followed the video but in one of the steps I have lost. Step 1 ok, step 2 ok, step 3 on the video can automatically install, but ami shows me a TWRP window and I see a menu. I do not know what I have to do next. I do not know why it is not installed automatically as it appears in the video or as the forum says. What am I missing? Can you help me? Thank you all, and sorry for my English.

Enviado desde mi Redmi Note 3 mediante Tapatalk
[FYT Android Head Units] henrysinn:
Hi

I've just been through this with the same problem...

Step 1 should read: "Unzip ALL the contents OF ALL THE ZIP FILES to the root of your USB flash drive on your computer, then plug the flash drive into the Joying unit via USB. "

etc..

It will then reboot to TWRP - AND - continue

:)
[FYT Android Head Units] luismiguelmimi:
hello henrysinn, thanks for your help. After step 3 it restarts and I see the image that I have put, and that's where I do not know what to do. The video in step 3 takes almost 10 minutes, and ami in step 3 takes 2 minutes. Something I'm doing wrong.

Enviado desde mi Redmi Note 3 mediante Tapatalk
[FYT Android Head Units] henrysinn:
I might be wrong but you need to:

Download the INSTALLER and the FIRMWARE and the CUSTOM

Unzip the INSTALLER and the FIRMWARE to a USB Stick

Copy the CUSTOM to the USB Stick

Install CUSTOM

Install TWRP via CUSTOM

Install ROM via CUSTOM

Bingo (quite some time)

Re-boot 25 thousand times give-or-take (As I have / did) and you're more-or less off and running

It sounds like you have not unzipped FIRMWARE to the USB stick
[FYT Android Head Units] luismiguelmimi:
Thank you! I unzip the 2 Zip in the root of the USB as it puts in it forum should make me the installation automatically right? How can I know if everything went well and I have the custom ROM installed?

Enviado desde mi Redmi Note 3 mediante Tapatalk
[FYT Android Head Units] henrysinn:
You'll know..

VERY different

:)
[FYT Android Head Units] henrysinn:
Boot Problems

As attached, does anyone know how to address the boot problems I'm seeing?

Happening at the end of boot just before the launcher starts

"Android is Starting - Starting Apps" - Happening every cold boot

EDIT:

Tried a Wipe Data, Cache and Dalvik from TWRP with no result except a lengthy set up again

Now getting boot loops resulting in disaster

Hard reset seems to bring it back to life.

See attached

Thoughts?

EDIT 2

Tried https://xdaforums.com/showpost.php?p=76718952&postcount=1574

Still stuck on bootloops and "Android is Starting - Starting Apps"

Thoughts?
[FYT Android Head Units] xxcelloxx:
where i can download the androidhelper apk?
[FYT Android Head Units] surfer63:
Which Androidhelper apk?

You mean the FYT apk with the help screens and documentation?

Or ..?
[FYT Android Head Units] Aaaron16:
Is this ROM still available? Would be great to fix the loud popping noise.
[FYT Android Head Units] lotte67890:
Hello again, I have the problem that my unit running this ROM sometimes stays somehow awake when ac is turned off. The screen goes black, music stops but sometimes if I come back to the car I hear funny noises through the speakers powered by two external amps. This means to me that the external amp 12v signal is not switched off by the unit. The setup has not been changed since 3 months, the issue started two weeks ago. It once drained my battery low to 4 volt... Might this be SW related which could be fixed by reinstalling or is it more related by a hardware bug? Would activating nokill be an option? It happened 3 times over the past two weeks...

Thx

Lotte
[FYT Android Head Units] the converted:
Is anyone able to give me some direction on this PLEASE. I'm desperate to make this headunit more user friendly...
[FYT Android Head Units] surfer63:
NoKill wouldn't fix that. It would even make it worse. Download a wakelock app from the play store and see if some app holds a wakelock.

---------- Post added at 10:17 PM ---------- Previous post was at 10:13 PM ----------

Share your /system/build.prop. Check and see if there is a fyt.prop and/or a fyt_build.prop in /system/app. If there is/are, also share those. Then we can give more info. Having one of the latter two makes your unit almost completely compatible with this custom ROM, but don't flash it before we know more.

The About screen is not enough.
[FYT Android Head Units] the converted:
Thank you SO much for your reply.

Build.prop as follows
[FYT Android Head Units] the converted:
fyt.prop as follows