Related
Exclusive MODDED ROM EQS-v2.0M
CS968 a RK3188 ChipSet Based TVBoX
AKA: TV01 [GeekBuying] CR11s [CloudNET2GO]
THIS VERSION HAS NATIVE 1080P KERNEL, NOT SAME AS V1.
IMPORTANT INFORMATION:
WE JUST LEARNED THERE ARE A FEW CS968/TV01/CR11s MODELS equipped with different WIFI/BT MODULES.
Thanks to dFenix we figured this out. [More info]
THIS ROM IS FOR AP6210 WIFI CHIP bundled devices, MAINBOARD VERSION 2.
So if you try this rom on other models you may loose your wifi connection.
Click to expand...
Click to collapse
IMPORTANT NOTICE:
THIS IS KIND OF BETA/ALPHA FIRMWARE OR WHATEVER YOU WANT TO CALL IT.
CURRENTLY I HAVE EXPERIENCED NONE PROBLEM AND IT SEEMS EVERYTHING INCLUDING 1080P MODE WORKS FINE.
THIS IS AN EXCLUSIVE ROM BECAUSE THERE ARE A FEW THINGS FACTORY FIRMWARE HAS NOT.
SYSTEM IS SAME AND NOTHING HAS BEEN MODIFIED EXCEPT SUPERUSER and BUILD.PROP, SO IF THERE IS A BUG THEN THAT IS FIRMWARE RELATED THIS ISN'T SUPER DUPER FIRMWARE AND DOESN'T HAVE SPECIAL KERNEL OR RECOVERY, EVERYTHINGS IS STOCK.
NOTE : LIBMEDIA.SO REPLACED, READ BELOW...
Factory Date : 09-12-2013 from CloudNET based CR11/s
Modification Date: 21-12-2013
NOTICE: THIS IS FOR 2 MPX VERSION, NOT FOR 5 MPX
You may harm your device, if you flash this firmware to 5 mpx camera version.
LCD Display density has been set to 240, if you need smaller icons and texts you can easily change by using preinstalled DPI changer program (May need root permission after first start).
Features:
Rooted [ You may notice a bit difference than v1 version, but it is normal ]
Build tweaks
TCP Tweaks (Buffering etc...)
Networking Tweaks
Wifi Tweaks (Signal etc...)
Multimedia Tweaks
Streaming Tweaks
HW Video Acceleration by default
Spoofed as Galaxy S3
Date format set to European
Timezone Europe GMT +1
Renewed bootanimation
Renewed wallpaper
Add: SuperSU.apk (Updated)
Add: LuckyPatcher (Updated)
Add: RootBrowser (NEW)
Add: OGYoutube with downloader [ Original YouTube still can be apartly installed ]
Add: Dolphin Browser 10.1.2
Add: Android Weather
Add: JetAudio
Add: Blueput Droid (NEW)
Add: Texdroider DPI (NEW)
Add: BSPlayer FREE (NEW)
Add: Cifs Manager (NEW)
Add: ESFile Explorer (NEW)
Add: Patched Libmedia.so (Many thanks hillyu from FreakTab, More info)
Updated : AddAway (Update)
Removed : All of useless chinese media stuff
Removed : Chrome
Removed : Search Box
Removed : Google Stuff (Search, maps, gmail, talk)
Removed : Email
Removed : XBMC Installer (Not everyone's taste)
Removed : A few more crap...
Exclusive test modules : Tun, Cifs*, NFS, NTFS and Xpad these modules are not installed by system, must be done manually from console/terminal.
Included CIFS MANAGER can do it for you, you don't need to install from terminal.
Exlusive bootanimation (Renewed)
Good working Remote Control.
Faster Internet browsing, smoother streaming, Very nice playing 1080p media from NAS DRIVE
*: It seems cifs module won't work properly, it is interesting because it was allright with K-R42 device but I'll search for it.
v2.0M CHANGES
NEW*: MultiWindow
*Needs Xposed Framework to be installed completely.
NEW*: Xposed Framework Installer
*Installation must be done via program self, then after reboot you may download modules as much as you want
REPLACED : BSPLAYER-> MX PLAYER FREE - No Codec pre-installed
REMOVED : JETAUDIO
UPDATE : LUCKY PATCHER, ADAWAY
UPDATE : DOLPHIN BROWSER 10.2.1
Re-Add : RKVideo player, RKExplorer
A few fixes that causes problems.
More optimized video playback (about 40 mbps mkv from network drive), more stable system.
LCD Density set to : 160 (Smaller icons and texts by default)
A little bit faster than 2.0 version.
Feel free to test or build new one, no words for future updates or versions etc.
FLASH WITH YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY DAMAGE CAUSED BY FLASHING OR AFTER.
AnTuTu Results
Devhost / Mirror
password : cs968eqs
Firmware flashing guide.
[ HD QUALITY BOOT ANIMATIONS... ]http://forum.xda-developers.com/showthread.php?t=2612221
hi
Hi Equancy,
Is a small community of CS968 users here: freaktab.com/forumdisplay.php?165-CS968-CR11s-amp-similar-sticks
Would you like to share this rom there too?
fakotibor said:
Hi Equancy,
Is a small community of CS968 users here: freaktab.com/forumdisplay.php?165-CS968-CR11s-amp-similar-sticks
Would you like to share this rom there too?
Click to expand...
Click to collapse
Hi,
Yeah, it seems not much users have CS968 here in XDA but, I'm a member of XDA-Dev and I share what I have here, but you may share this thread on freaktab as yours if you wish.
I have no account on FreakTab and I don't think I may able to manage this thread on multiple forums.
So, I can answer questions only here and also publish updates of my rom.
Thanks for your interest.
Hi Equancy, I cant download this file.
(Error no: 1) Connection failure : User 'proxy_iamheman' has exceeded the 'max_user_connections' resource (current value: 10)
What seems to be the issue. please fix the link. Thanks.
resansid said:
Hi Equancy, I cant download this file.
(Error no: 1) Connection failure : User 'proxy_iamheman' has exceeded the 'max_user_connections' resource (current value: 10)
What seems to be the issue. please fix the link. Thanks.
Click to expand...
Click to collapse
Try primary download host (Devhost), its working flawlesly.
I guess mirror host has problem rightnow.
I've uploaded another Mirror-link working well.http://www.filedropper.com/showdownload.php/cs968051213eqsv2m
EQUANCY said:
Try primary download host (Devhost), its working flawlesly.
I guess mirror host has problem rightnow.
I'll make more mirrors soon.
Click to expand...
Click to collapse
OK This worked. Thanks.
resansid said:
OK This worked. Thanks.
Click to expand...
Click to collapse
Your welcome. :good:
Or you may try from here too.
@EQUANCY,
i tried your rom, looks good. few things are not wrking
1. xposed: i installed xposed framework, rebooted, then installed GravityBox, none of the tweaks in it wkrs. like transparent status bar/traffic meter.
after installing the GB and setting it up, i rebooted, but still not wrking.
2. window support is also not wrking. hv added some of the apps to wkr in window mode, but all run in full screen.
Have you tried these on ur rom ???
hanu_blr said:
@EQUANCY,
i tried your rom, looks good. few things are not wrking
1. xposed: i installed xposed framework, rebooted, then installed GravityBox, none of the tweaks in it wkrs. like transparent status bar/traffic meter.
after installing the GB and setting it up, i rebooted, but still not wrking.
2. window support is also not wrking. hv added some of the apps to wkr in window mode, but all run in full screen.
Have you tried these on ur rom ???
Click to expand...
Click to collapse
Yes,
Multi-window not working, but some features of Gravitybox well.
Actually I've put Multi-window by mistake, it was a bit late when I saw
However you may remove this app by following steps below.
1- Deactivate Multi-window app in Xposed modules menu (uncheck)
2- Reboot
3- Open RootBrowser and go to System/app directory
4- Long press on multi_window.apk and select Delete
I didn't tested all of modules and most of them are not working properly because of Tablet UI, I'll remove both application in next firmware mod.
Sorry for inconvenience, thanks for understanding.
Hi Equancy,
I am having issues with wifi direct. I can establish the wifi direct connection with the other device (Samsung Galaxy S3) just fine, I can send files from the box to the SG3, but I absolutely can't receive files sent from the SG3 to the box (I never even get the prompt).
I also tried to use the Superbeam app, and same story: I can send files out but not receive them.
Any clue? I am not sure whether this is specific to your ROM as I haven't tried with any other.
Cheers, Merry Christmas and Happy New Year to you.
daviddema said:
Hi Equancy,
I am having issues with wifi direct. I can establish the wifi direct connection with the other device (Samsung Galaxy S3) just fine, I can send files from the box to the SG3, but I absolutely can't receive files sent from the SG3 to the box (I never even get the prompt).
I also tried to use the Superbeam app, and same story: I can send files out but not receive them.
Any clue? I am not sure whether this is specific to your ROM as I haven't tried with any other.
Cheers, Merry Christmas and Happy New Year to you.
Click to expand...
Click to collapse
hi,
Thanks for your best wishes, hoping same for you.
For the issue,
Possible answer for WiFi Direct function is Firmware related, because I didn't touched any system file except su binary and build.prop.
I also tested by my self, receiving files from TVBox is working but transfering to the device isn't via SuperBeam.
As I said before, I suppose it is a firmware bug and must be reported.
And question is:
To who
However, you may ask other users who is using another firmware versions or custom roms.
Happy new years...
NFS help needed
I tried the rom on my cr11s and i must say its awesome except that its a bit slow.. i also can't get nfs to mount thru adb nor cifsmanager.. does the supplied nfs.ko support nfsv4? Everything else is working with no major issues.. thanks for the rom anyways...
PsychicSaint said:
I tried the rom on my cr11s and i must say its awesome except that its a bit slow.. i also can't get nfs to mount thru adb nor cifsmanager.. does the supplied nfs.ko support nfsv4? Everything else is working with no major issues.. thanks for the rom anyways...
Click to expand...
Click to collapse
It is very little bit slower than v1.1 but its not really noticable on 2D applications, can you specify what have you experienced actually?
I'm using a NTFS formatted NAS drive with no problem, even watching MKV files about 40-50 mbps rate. (NetGear ReadyNAS).
All of thoose modules have been supplied but not loaded by default need manually installed or you must add lines to the init.rc from system.
This can't be automatically because Kernel needs to be modified and I don't want to do that.
NFS module is actual module for RK3188.
If you more specify problem may be I can look it for you.
And for your consideration...
Some issues are FIRMWARE RELATED, because these firmwares aren't fully optimized, just generic RK3xxx roms.
Not good drivers at all...
And not all manyfacturers optimizes their own firmwares.
Produce and forget policy.
EQUANCY said:
hi,
Thanks for your best wishes, hoping same for you.
For the issue,
Possible answer for WiFi Direct function is Firmware related, because I didn't touched any system file except su binary and build.prop.
I also tested by my self, receiving files from TVBox is working but transfering to the device isn't via SuperBeam.
As I said before, I suppose it is a firmware bug and must be reported.
And question is:
To who
However, you may ask other users who is using another firmware versions or custom roms.
Happy new years...
Click to expand...
Click to collapse
I sent a email to cloudnetgo support, let's see what comes out (probably nothing...)
daviddema said:
I sent a email to cloudnetgo support, let's see what comes out (probably nothing...)
Click to expand...
Click to collapse
You've done very well my friend, please let us know if you get an answer from them.
EQUANCY said:
You've done very well my friend, please let us know if you get an answer from them.
Click to expand...
Click to collapse
I also tried to get screen mirroring to work with the wifidisplay app included in the ROM (is this also part of the original image or did you add it?).
Again, I can set up the mirroring connection between a Samsung Note 3 and the wifidisplay app, but then actual mirroring never happens. I suspect that whatever causes wifi direct not to work also causes the mirroring not to work... pity as this is would be a nice feature...
@EQUANCY,
I have a strange issue related to sound settings, its because of the stock firmware issue, hope you give some pointers on this
in the sound devices settings, there is input sound device and o/p sound device. I understand abt the output sound device, but what is the use of input sound device ? and is by default always set. Is there a way to disable the i/p device ?.
I ask this bcasue, my sound bar sony will cutoff the sound to other devices if the cs968 device is switched-off, if in on/standby mode, the sound passthorough (via cs968 )for other devices i hv connected to my soundbar. My guess is that since sound input device is checked(Radio button on), sound bar thinks that it has to pass through cs968. If i unplug the hmdi cable from cs968, the soundbar wrks fine.
My guess is that somewhere in the settings xml file, there shd be a way of disabling the sound input device.
I tried decompiling settings.apk and settingsprovider.apk searched all file with sound as filecontent key, but could not find anything related to disabling of sound input device.
can you help me on this ???
daviddema said:
I also tried to get screen mirroring to work with the wifidisplay app included in the ROM (is this also part of the original image or did you add it?).
Again, I can set up the mirroring connection between a Samsung Note 3 and the wifidisplay app, but then actual mirroring never happens. I suspect that whatever causes wifi direct not to work also causes the mirroring not to work... pity as this is would be a nice feature...
Click to expand...
Click to collapse
Wifi Display part of firmware self, I didn't add by myself and yes it is not working properly, I've read at somewhere this application supports only Nexus devices but I'm not sure.
hanu_blr said:
@EQUANCY,
I have a strange issue related to sound settings, its because of the stock firmware issue, hope you give some pointers on this
in the sound devices settings, there is input sound device and o/p sound device. I understand abt the output sound device, but what is the use of input sound device ? and is by default always set. Is there a way to disable the i/p device ?.
I ask this bcasue, my sound bar sony will cutoff the sound to other devices if the cs968 device is switched-off, if in on/standby mode, the sound passthorough (via cs968 )for other devices i hv connected to my soundbar. My guess is that since sound input device is checked(Radio button on), sound bar thinks that it has to pass through cs968. If i unplug the hmdi cable from cs968, the soundbar wrks fine.
My guess is that somewhere in the settings xml file, there shd be a way of disabling the sound input device.
I tried decompiling settings.apk and settingsprovider.apk searched all file with sound as filecontent key, but could not find anything related to disabling of sound input device.
can you help me on this ???
Click to expand...
Click to collapse
Disabling sound input?
As much as I know, the only sound input is internal microphone.
I real don't know the other sound inputs and als no clue about disabling it.
If you mean sound output such as Analog, Optical and HDMI then may be there is option but for input, I have no idea.
Sorry.
Uninstall Apps
How can I unistall app like bsplayer?
Thanks
Hi,
Open RootBrowser (usually opens in main directory) if not then got to Main Directory first then next to
\System\App
And long press the application which you want to remove and select Delete.
Or download a root uninstaller from market then uninstall what you want.
Hope this helps.
Could someone with knowledge of Russian language please ask for this "Mi4_Disable_Services.zip" on http://4pda.ru/ to be re-uploaded?
IMO this is a very important thing to set up as long as kernel is not available and an OmniRom (personal preference) or a working AOSP ROM is not available yet. Hoping for a FOSS and free of Google/Xiaomi services ROM.
Further reading:
https://thelibreguy.wordpress.com/2016/10/13/xiaomi-has-backdoors/
https://thelibreguy.wordpress.com/2016/10/16/xiaomi-trackers-and-backdoors-update/
No_Signal said:
Could someone with knowledge of Russian language please ask for this "Mi4_Disable_Services.zip" on http://4pda.ru/ to be re-uploaded?
Click to expand...
Click to collapse
http://www.mediafire.com/file/bwmeqo5v6joop4y/Mi4_Disable_Services.zip
Wat does this zip do?
Disable all google and xiaomi services?
Have u tried?
toji12 said:
Wat does this zip do?
Disable all google and xiaomi services?
Have u tried?
Click to expand...
Click to collapse
A ruff translation how to use (read: what I did):
1. install the zip file in TWRP and reboot
2. open a terminal emulator of your choice
3. type in the following in the terminal command line:
Code:
su
to get root privilege, then
Code:
sh /data/local/tmp/miui/services.sh
4. the script will offer several options.
Enter 2 for Google services and/or 3 for Xiaomi services to disable them.
(5. Repeat the the step to enable them again.)
It does disable most of the Xiaomi services but some stay untouched, someone with better knowledge could surely add those to the script or say why they are left out.
I didn't used it on the Google services as disabling them on recent global IMUI ROM leaves the Redmi 3s in a bootloop.
Surely a helper too clean the official ROM, at this point I prefer zwliew's Cyanogenmod 13 ROM, hoping for an OmniROM built when the kernel is released.
{
"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"
}
Welcome to the NitrogenOS Q&A Megathread. Here you can find answers for the most popular problems and questions about NitrogenOS. I started this thread, so that new users don't repeatedly ask the same questions multiple times. While I am fairly new to coding in Java, I can definitely say I know a lot about Android phones and NitrogenOS, but you'll have to trust me on that. If you need any more help, you can even PM me and I'll try to reply as soon as I can.
You can find the original NitrogenOS thread here.
ROM info
Developer: xyyx
Latest Android version: 8.1 Oreo
NOS Download (latest): https://sourceforge.net/projects/nitrogen-project/files/kenzo/kenzo_test/8.1/
Bugs and updates
- A (very) small amount of users reported Google Dialer not working properly while installed through OpenGapps or the Play Store, you can still use stock dialer
1. Test or stable?!?!
Test in this case doesn't mean less stable. xyyx named the two versions a little confusingly.
Test means Oreo (Android 8.0 and 8.1) and Stable means Nougat (Android 7.1.2).
So let's make this a little less confusing:
Oreo (8.0) builds -> Download from here
Oreo (8.1) builds -> Download from here
Nougat (7.1.2) builds -> Download from here
2. Youtube PiP (Picture in Picture mode)
Google has patched PiP a long time ago, so it doesn't work with the latest Youtube releases. The last official release working with PiP is 12.34.55, which you can download from ApkMirror.
My preferred option however is iYTBP (injected YouTube Background Playback), a modified version of Youtube, but it gets a little confusing as there are multiple options.
You can download it from this thread.
Now the tricky part - choosing the right version. I always prefer the Vanced version, which can be found in the 2nd post. Again you have multiple options, but I will not go through all of them since they are explained pretty good in the post itself. While iYTBP enables PiP, it also blocks ads and adds a lot of useful settings and new updates come very frequently. There are multiple installation methods, but I prefer the Magisk one, since it offers options like detaching the Youtube app from Play Store. What this means is, that you don't have to disable auto-updates and it will not bug you to constantly update it.
You can try these methods:
Magisk Module (Easiest):
1. Open Magisk Manager
2. Go to Downloads
3. In the search bar type "Youtube", you should see two results
4. Choose either the normal or the black theme (I personally prefer the black one)
5. Press the download arrow and then "Install"
6. Wait for a while (it's a big package to download and unpack)
7. Reboot
This is by far the easiest option and the module is updated fairly often.
Manual:
1. Delete or uninstall any previous release of Youtube. If you installed it as a system app, disable it or delete the /system/app/YouTube folder. If you had to delete the folder, reboot.
2. Download the Youtube apk
3. Make a folder called YouTube (watch the caps!)
4. Move the apk to this folder and rename it as YouTube (again with the caps)
5. Copy/move the folder to /system/app (The directory should look like this: /system/app/YouTube/YouTube.apk)
6. Reboot
Magisk (manual):
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. Since we're installing from Magisk, you'll need to set MAGINSTALL to YES (MAGINSTALL="YES"). I usually also enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Open Magisk Manager, go to Modules and press the + button. Now select the universal installer zip and flash it in Magisk.
4. Reboot
Recovery method:
Same as for Magisk, but MAGINSTALL is set to NO (MAGINSTALL="NO"). In case you didn't read the Magisk method, here is the recovery method...
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. I usually enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Reboot to recovery, go to Install and choose the universal installer zip, flash it.
4. Reboot
If you open a video in fullscreen mode and press the home button, it should open it in PiP mode. If you want to change some advanced settings, you can go to your Account (the round icon with your profile picture) -> Settings -> iYTBP Settings
3. Goodix & FPC - What are they
Goodix and FPC are two different types of fingerprint sensors (or rather sensor manufacturers). They both work in Android 8.1 builds. Custom kernels or mods may break the fingerprint sensor functionality.
4. Rooting
tl;dr: rooting NitrogenOS is the same as rooting any other custom rom, just flash Magisk, SuperSU, phh's superuser or anything else.
Now for the extended version.
Magisk:
Magisk is a great open-source root manager, developed by topjohnwu. It features a feature rich app, but most people prefer it because of it's "modules", packages which can do a bunch of things, from installing apps like Viper4AndroidFX or Dolby Atmos, to modifying system settings, like the volume steps increase. Magisk also features an option called "Magisk Hide", which can bypass Android's SafetyNet.
Check out the Magisk thread.
You can directly download the latest version of Magisk from https://tiny.cc/latestmagisk
SuperSU:
SuperSU is an alternative root manager. It used to be developed by Chainfire, but has recently been purchased by another company. I still prefer Magisk, but SuperSU is a great alternative for new users. My problem with it though is, that it is not open-source and the new buyer is pretty secretive so I don't really trust them.
Check out the SuperSU website for the download link.
phh's SuperUser:
Another open-source root manager, but the great thing about this one is, that it's very minimalistic and very small in size.
Check out the SuperUser thread and phh's Build Bot.
5. Google Apps (gapps)
Google apps are a vital part of custom roms. You might not know this, but AOSP and CM based roms are made from Google source code. Google actually makes Android open-source, but the Play Store and other Google apps are not. That's why roms like NitrogenOS do not come with the Play Store preinstalled. That is where Open Gapps come in. They are prepackaged apps, updated almost daily. They come in various sizes and versions, but they can all be flashed in TWRP like a normal zip file.
Platform: arm/arm64/x86/x86_64 - RN3 has an arm64 processor (Think of it as a 64-bit CPU for phones)
Android: 8.0/7.1/7.0... - This is the android version, NOS is Oreo based so choose 8.0 (Or 7.1 for Nougat) [Check below for OpenGapps 8.1]
Variant: This is where it gets complicated. There are a LOT of versions to choose from. For more in-depth resources check the OpenGapps' package comparison.
But OpenGapps are a lot more customisable, to the level where you can choose individual apps you want installed. The easiest way to do this, is to flash the Aroma package, which enables you to choose exactly which packages you want installed. Another option is to configure any of the selected packages using a gapps-config.txt file. You can learn more about that in the Advanced Features and Options section.
You can download daily builds for any Android version from https://opengapps.org/
6. TWRP (Recovery)
A recovery is a partition, used to flash files like ROMs, gapps and any other modifications. You do (in most cases) need an unlocked bootloader to use it. Unlocking your bootloader will not be described on this thread, as there are a lot of resources for our device.
Official TWRP - This is the official TWRP (Team Win Recovery Project) for our device
You can find the latest updates for TWRP on their website.
Red Wolf - This is a modified version of TWRP, my absolute favourite because of it's custom features.
Flashing TWRP:
If you don't have a custom recovery installed and you have unlocked your bootloader, then download the latest version of your preferred recovery and follow these steps:
1. Download Minimal ADB and Fastboot on Windows, or use sudo apt install android-tools-adb android-tools-fastboot if you're on Linux.
2. Enable USB Debugging (Settings -> About phone -> Press "Build number" 7 times to enable Developer options). You should find the Developer options in settings above "About Device". Find USB Debugging and enable it.
3. Connect your PC to the phone via a cable. Open Minimal ADB and Fastboot (which will open CMD) or Terminal on Linux and type this (same for both OSs): adb devices. Select "Always allow on this computer" and confirm access on your phone.
4. Reboot your phone to fastboot/bootloader (By holding Power and Vol-, releasing the power button after a vibration and holding the Vol- button until you see the Xiaomi mascot).
5. Type (In CMD/Terminal): fastboot devices, to confirm if the phone has been recognised, then fastboot flash recovery /path/to/recovery.img
6. After it has succesfully finished, remove the cable and reboot directly to recovery (Power and Vol+, release power after vibration, but keep holding the Vol+ button until you see the TWRP or RedWolf logo).
If you do already have a custom recovery installed and just want to update it, flash the .img or .zip file in your already installed recovery and select "Reboot to recovery".
7. NOS asks me for a password after flashing?!!?!?
This is actually not NitrogenOS's fault, it's a byproduct of your previous rom, most often MIUI. What this means is, that your internal storage is encrypted and the only way to fix this, is to backup everything on your internal storage, which you can do by connecting your phone to your pc while in recovery. You should be able to access the phone's storage and move the files from there. If you for some reason can't do that, you can still put in an sdcard and copy the files to it in TWRP. Bottom line, backup the files and then go to "Wipe" and find the "Format data" button. You might see a "wipe data" button, but this is not the same. When you "wipe data" you are wiping your system, cache, dalvik cache and data partitions, but formatting data will format your internal partition as well and thus remove the encryption.
You can finally reflash NOS and gapps or whatever other modification you want.
8. Firmwares
Check out this link to download the latest firmware for our device.
What is firmware? - It's what connects hardware to software (don't confuse it with a kernel). It's what, for example, makes the camera work.
Do I really need firmware - Yes (but it's already installed, even after completely wiping the stock rom, since it's on separate partitions).
Do I need the most up-to-date firmware - Actually no, the only difference you will notice is in the signal and WiFi strength. If yours are good enough, you don't need to update, otherwise feel free to download the newest version from the link above.
What is emmc_appsboot.mbn? - It's a bootloader update. Bootloader or fastboot is the partition in which you have unlocked your bootloader and flashed the recovery. If you have officially unlocked your bootloader, then you can flash firmware with emmc_appsboot.mbn, but if you have unofficially unlocked your bootloader, do not flash these files as they will re-lock it. But you can still flash the version without emmc_appsboot.mbn.
Kenzo? Kate? - Kate devices are the same as kenzo ones but are a little bigger.
Some comparisons:
Kenzo
Size: 150 * 76 * 6.85 mm
Weight: 164g
Kate
Size: 152 * 76 * 6.85 mm
Weight: 167g
Model numbers:
Kenzo: 2015116
Kate: 2015161
Kate devices are 32/3 GB, and some kenzo devices are as well (some are 16/2 GB), not really sure about this part.
Global stable or developer? - Most people use developer roms, but again, this is not the actual ROM, just the firmware extracted from the rom, it doesn't really matter which one you choose.
When do I need to flash firmware? - If you're coming from MIUI8 (or 9), then you probably have the newest firmware. In this case you don't need to flash it, because MIUI roms already have firmware included in the update. If you're coming from a CM or AOSP based rom you also probably don't have to flash it, but I suggest you update it just in case. If your signal is good enough though, there really is no need.
9. How to flash the rom
Flashing is pretty straight forward. Just go to the Install section of TWRP and flash it like any normal zip, nothing special.
If you're coming from MIUI, then the full procedure is this:
1. Unlock your bootloader (google it, useless explaining it here)
2. Flash TWRP
3. Make a full device backup (Nandroid backup)
4. Copy or move all important files from the internal storage to an sdcard or your pc
5. Format data, or in other words, wipe EVERYTHING (excluding external storage) - This will delete all your photos and anything else in internal storage
6. Flash the latest NOS "test" build (Oreo)
7. Flash gapps (I recommend opengapps.org, check above)
8. Reboot to system
10. OTA?
What is OTA? - OTA means Over The Air (Update)
Does NOS have OTA? - Actually yes and no, newer updates (from March 2018 on) do have partial OTA (it does check for updates and notify you, while also giving a direct download link to SourceForge, but you will have to manually flash every update in your recovery.
What about incremental updates? - Sorry, but no. You'll have to download full packages every time. If you have a bandwidth cap then just download an update every week or two, you can check the changelog to see if you think it's worth updating to.
11. Google Camera
If you're having problems with the official Google Camera or just want some added features then look no further than modded camera apps. Check out this thread by emime12, it's very frequently updated and features a lot of different camera mods, including Google Camera, MIUI Camera, MOTO Camera and many more.
Recommended settings:
3x3 Grid - For better photos
I usually disable "Save location" and "Camera sounds"
Model: Pixel XL (corr) - default
Config camera HDR+: NEXUS 6
HDR+ parameters: Default
Panorama resolution: High
Advanced: Enable both
Experimental: I usually leave this disabled but it's your choice.
Back camera video resolution: UHD 4K (30 fps)
In case your camera doesn't work check if you have these two files and delete them:
/System/framework/com.google.android.camera.experimental2016.jar
and
/System/etc/permissions/com.google.android.camera.experimental2016.xml
Credits go to: @emime12 and Njaiker.
You can find more info about problems and updates on emime12's thread.
Settings may differ a lot, so check emime12's recommended or just test until you find ones that work for you
12. RAM Management - Low free RAM
Android's RAM (Read Only Memory) management doesn't work like Windows'. Android manages RAM very well, "Free RAM is wasted RAM" is a very common expression on XDA. Android loads the first couple of apps into the RAM and priorities the open one. More used ram means more apps loaded in ram which means faster load times. Don't worry about it too much and just enjoy the fast loading speeds.
13. VoLTE?
VoLTE should work on Android 8.1. Magisk, Viper or any other mods may break it.
14. Custom kernels
While there are a lot of custom kernels, I suggest you stick with the stock one, as it is made specifically for NOS and thus it is the most stable. If you still want a custom kernel, you can try Radon or Agni but they might break VoLTE or your fingerprint sensor.
Agni XDA Thread - By psndna88
Radon XDA Thread - By Umang96
15. Daily driver or not?
Yes, NitrogenOS Oreo is very stable, definitely enough for a daily driver. It is the best Oreo rom for our device (in my opinion), as it offers just the right amount of customization and stability.
15. GPS
Some users have reported low accuracy, but you should be fine if you turn on High Accuracy mode and/or install Faster GPS.
Update: In recent updates GPS shouldn't be a problem anymore as xyyx has fixed it, but some users have still reported low accuracy.
16. Viper4Android FX
(There may be other ways, but I haven't tested them yet so I can't confirm if they work) By far the easiest way to install Viper4Android FX is using Magisk. There is Magisk module called ViPER4Android FX Materialized. Download and install that module from the Magisk repo, choose your preferred installation option (By pressing Vol+ or Vol- to select which version you want installed and if you want it materialized - for newest materialized version press Vol+ 2 times) and finally reboot. Try playing some music and open the Viper app. Turn on the "Master Power" switch and the "Playback Gain Control" (the easiest way to tell if it worked). If after a little time the volume increases, it means that Viper4Android FX works. If not, press the three dots and choose "Exit" (without turning off the master power or gain control). Now open the app again and it should work. You can also check that in the side menu under "Driver status", if it's enabled and processing, then everything works.
You may or may not have to exit and re-enter the app after reboot to enable processing (in my case I had to).
I would show you my recommended settings (as requested), but to be honest I only use:
Headset
Viper Bass (Natural bass, 40 HZ frequency, 8 dB)
Viper Clarity (Natural, 6 dB)
Sometimes I use Field surround with default settings
Phone speakers
eXtra loud (Slight, 4x max gain, -1.9 dB max output)
Bluetooth device
Playback gain control (Moderate, 6x max gain, -1.9 dB max output)
If I'm at a party with my bluetooth speaker I pump it up to Extreme and 8x max gain
Viper Bass (Natural, 40 HZ frequency, 8 dB), 17 dB for parties
Viper Clarity (Natural, 3.5 dB)
I don't use equalizers or if I do, they are song-specific. I also don't USB/Dock, so I can't recommend anything there.
Of course these settings can vary depending on the song, so choose those, which you like the most and don't stick with just those I chose, try all the functions to see which you prefer.
17. AdAway (Root)
AdAway is a great open-source root ad blocker, which can automatically download and update sources and works by adding those to the hosts file. It work well on the internet, but also inside apps (most of the time).
Check out the official AdAway website. You can also download it from F-Droid.
Adaway v3.2 (60) (direct download link)
Adding custom host sources:
Go to "Host sources" and add your own sources or check out these: AdAway's host sources
Be careful when adding all of them, since some can block legitimate links like goo.gl.
AdAway also offers an option to scan for Adware, which can be found under "Scan for adware". This will bring up a new window, press "Start scanning". If you don't need/want the mentioned apps you can uninstall them, but AdAway can't block their ads.
You can also check out my recommended settings:
wow,really appreciated that sir., it is very helpful specially for those who wanted to try, flashing rom or any mods on their device like me. thanks and keep up the good work sir God bless!
i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.
saifuk said:
i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.
Click to expand...
Click to collapse
Thanks for the tip, will update the thread.
@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks?
@saifuk what kind of nougat port u are expecting of ?
Aditya1011 said:
@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks
Click to expand...
Click to collapse
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.
AtomR said:
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.
Click to expand...
Click to collapse
Flash latest firmware of developer rom. And volte is sure shot working.
Aditya1011 said:
Flash latest firmware of developer rom. And volte is sure shot working.
Click to expand...
Click to collapse
Mate, I'm already on 7.9.22 firmware. Lots of people are reporting it. Yours is working, must be some kind of random.
@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.
how to install via dualboot patcher as secondary rom?
AtomR said:
@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.
Click to expand...
Click to collapse
Idk bro y that happening to u. Flash miui EU rom n thn the nos rom. Mayb that should work.... Bcuz I had done that for the 1st time whn my volte wasn't working at any cost. Best of luck.
smjhh said:
how to install via dualboot patcher as secondary rom?
Click to expand...
Click to collapse
I don't think dual boot patcher supports oreo roms. Try asking on their thread to see if it does.
Google HDR camera 5 or 5.1 work with this ROM??
sagar13190 said:
Google HDR camera 5 or 5.1 work with this ROM??
Click to expand...
Click to collapse
Read op!
I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great
sagar13190 said:
I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great
Click to expand...
Click to collapse
It works for many users. Did you flash my zip or install an apk?
Sim card detection issue
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.
dhavalmehta said:
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.
Click to expand...
Click to collapse
Dude, it's really not a big problem, it detects it like 95% of the time. Just reboot and you're done. Or wait about 2 min and it should detect it. You could also just remove the sim and reinsert it. But since the latest few updates for me it gets detected 100% of the time. So update to 28/10/2017 build and you should be fine.
@JustMeErazem You're giving flase info. to others saying that VoLTE works on both sim. Actually, it works only on first sim. Tried, tested on 3 different Kenzo's. Clean flashed.
Conclusion: VoLTE doesn't work on 2nd sim.
Introduction
Few weeks ago, I got a Pixel 1 as my backup phone, when I try to connect it to the Microsoft Wireless Display Adapter, it couldn't find the Adapter.
I haven't used Android phones for a long time. In my mind, Android natively supports Miracast. After some searching, I was frightened to find that Google has removed Miracast from Android.
I was really disappointed because I often cast my Windows devices easily by using Miracast. My Projector has only two HDMI ports, one for HDMI cable, and one for Wireless Display Adapter. I can't add a Chromecast unless a HDMI switch is used.
One possible solution is to add a line "persist.debug.wfd.enable=1" in "build.prop" to enable WiFi-Display, but many people say that it doesn't work since Android N, the phone can discover WiFi-Displays but unable to cast.
Since Android framework is open source, I did some searching and found that some WiFi-Display related code still exists. Android 9 still keeps the WifiDisplayAdapter in DisplayManagerService, but removed WifiDisplay from MediaPlayerService, that's why we can discover WiFi-Displays but can't cast.
I recovered some code from AOSP history commits, fixed the build errors, and debugged on my Pixel, finally the Miracast can work on my Pixel.
If you also want Miracast to work on your Google phones, you can follow my steps, but first make sure your ROM is open source so that you can change and rebuild it.
If you have a Pixel 1 running the same version of system, you can simply replace some files in your system with the files I built.
If you have other Google phones or running different versions, you can apply my patch to AOSP, and build it by yourself. I have built the latest version for all Google Pixel phones, but I haven't tested except Pixel 1.
If your ROM is not open source, I will no longer be able to help, since MediaPlayerService may have been changed by your ROM, you may can't replace it with the AOSP version.
Prerequisites
Pixel running Android 9.0.0 build number PQ1A.181205.002.A1 or PQ1A.190105.004.
Bootloader unlocked.
adb and fastboot tools and drivers are working for your device.
Note & Disclaimer
These steps will change files in your system, your Pixel should run the exact same version of system. Pushing files to different versions of system may cause unknown problems.
Please check carefully before running each command, a mistaken operation may result in unable to boot up, or destroy your data, or even damage your phone.
If you are not sure about what these steps are doing, but still want to go ahead, please backup your phone firstly, you may not be able to recover your phone to its original state.
I have only tested on Pixel 1 with build number PQ1A.181205.002.A1 and PQ1A.190105.004, for other phones or versions, you should build and test on your own.
Basic Steps
Flash the same version of factory image for your phone.
Download the prebuilt files from https://github.com/sbjbs/android-wfd-patch
Add this line into "build.prop", without it, we will not be able to enable WiFi-Display:
Code:
persist.debug.wfd.enable=1
Replace some files in system:
Code:
system/lib/libaudioflinger.so
system/lib64/libaudioflinger.so
system/lib/libserviceutility.so
system/lib64/libserviceutility.so
system/lib/libmedia.so
system/lib64/libmedia.so
system/lib/libwilhelm.so
system/lib64/libwilhelm.so
system/lib/libandroid_runtime.so
system/lib64/libandroid_runtime.so
system/lib/libstagefright.so
system/lib64/libstagefright.so
system/lib/libstagefright_wfd.so
system/lib64/libstagefright_wfd.so
system/lib/libmediaplayerservice.so
If you have magisk installed, you can refer to Phoenix Wright's post:
Phoenix Wright said:
using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent.
using magisk to overlay them on /system
Click to expand...
Click to collapse
Some extra steps that you may need
Remove dm-verity metadata of system.img
The dm-verity can prevent us from changing the system, and what's more it has a forward-error-correction(FEC) feature, which can detect and correct some corrupted data.
I spend a lot of time on attempting to change the build.prop but fail again and again, it just always correct the file, and I can't enable wifi-display.
I don't know how to disable it. Since the error-correcting info should be stored in the dm-verity metadata, I just removed the dm-verity metadata from the stock system.img, and flash the system.img.
I will list the steps to remove dm-verity metadata, but if you can disable dm-verity entirely, that should work too.
For phones that have a vbmeta partition (like Pixel 2), seems you can flash an special vbmeta.img to disable AVB. You can build the empty vbmeta image by this command, but I don't have a device to test if it works:
Code:
avbtool make_vbmeta_image --flag 2 --padding_size 4096 --output vbmeta.img
For Pixel 1, we need to remove dm-verity metadata that attached to system.img, first convert the sparse system.img to an ext4 image:
Code:
simg2img system.img system.ext4.img
read the block count to calculate the system size:
Code:
od -j 1028 -An -N4 -tu system.ext4.img
for Pixel 1, it should be 516099. You also can read it by a Hex Editor, e.g., WinHEX in Windows, read 4 bytes starting from 1028 bytes, as a little-endian hex value.
so the real system partition size is 516099 * 4096 = 2113941504 bytes.
we need to set the data to zero after that position. It's important to do this, since we need to overwrite the metadata in that area, rather than just truncate the size of system.img.
next get the ext4 image size, for Pixel PQ1A.181205.002.A1, it should be 2147483648.
so we need to write 2147483648 - 2113941504 = 33542144 bytes：
Code:
dd if=/dev/zero of=system.ext4.img seek=2113941504 count=33542144 oflag=seek_bytes iflag=count_bytes
we also can use some other tools to do this, e.g., WinHEX in Windows. Open the file in in-place mode, and jump to 2113941504, and select it as the begin, and jump to the end, and select as the end, and fill the selection with all zero.
after that, flash the changed system.ext4.img to Pixel:
Code:
fastboot flash system system.ext4.img
Test that you can boot up normally. If not, check what's wrong and fix it.
Temporary boot up by TWRP image
We don't have to install TWRP, but just use it to temporary boot up, so that we can mount the system partition for writing. If you have TWRP installed, you can just boot to TWRP.
Download TWRP image for pixel, just need the twrp.img, we won't install the zip file.
boot your device to bootloader:
Code:
adb reboot bootloader
and boot by the twrp.img
Code:
fastboot boot twrp.img
after TWRP booted up, just leave it there, no need to unlock or input password, we will change the system by adb.
Mount system partition for writing.
In the current version of TWRP for Pixel (twrp-3.2.3-1-sailfish.img), its fstab has an entry for system partition, we can directly mount it.
Code:
adb shell mount /system
run mount to check if successfully mounted:
Code:
adb shell mount
you should see an entry like this:
Code:
/dev/block/sda34 on /system type ext4 (rw,seclabel,relatime)
If not, you should stop now, and check the above steps.
after mount, we can use adb to push files into system.
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
jean_michmich said:
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
Click to expand...
Click to collapse
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
sbjbs said:
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
Click to expand...
Click to collapse
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
jean_michmich said:
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
Click to expand...
Click to collapse
I used to be a ‘latest official ROM’ user
For custom ROMs, since they may have changed the framework, we can't replace files with AOSP version, but as long as they're open source, we can try to contribute to it.
Adding Miracast support in Android is not difficult, and many manufactures have their own support.
I hope your custom ROM will support Miracast for Pie in the near future.
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
spezi77 said:
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
Click to expand...
Click to collapse
There's a link in the OP: https://github.com/sbjbs/android-wfd-patch/tree/master/patches/android-9.0.0
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Great to hear that!
You method is simpler and more elegant, that's awesome!
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Phoenix Wright said:
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
Click to expand...
Click to collapse
Thanks!
sbjbs said:
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Click to expand...
Click to collapse
I tried building with my ROM but I got build errors related to OMX.h, I need to find a solution for them. Thanks anyways!
Nitin
Someone tries on Pixel 3? Thanks
It works perfectly ! I used the prebuilt files on the march build.
Do you know if we can force the 16/9 ratio ?
Thanks
edit : I will try with second screens !
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
marshyrob said:
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
Click to expand...
Click to collapse
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
EMJI79 said:
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
Click to expand...
Click to collapse
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
marshyrob said:
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
Click to expand...
Click to collapse
It did work today with my Sony television.
Thanks!
OMG!!! You made my week. Few hiccups tho....
Can anyone else confirm that Hulu and HBO go and Amazon prime . YouTube works.
Hulu and amazon I can log on but when it plays all you get is audio. Haven't tried Netflix I don't sub them.
HBO go as soon as I try to play a video it says this video cannot be played. If I disable the mirror it plays perfectly. Same thing with Hulu and prime. Disable the mirror an it works perfectly on my phone.
This tutorial was made by Craftingmod
Thanks so much for helping us.
Original Post: HERE
--------------------------
Note:tested only on GSI ROMs 9.0
1. Bluetooth audio connection fix
Backup the file /vendor/overlay/BluetoothResCommon.apk
Simply remove /vendor/overlay/BluetoothResCommon.apk via root explorer
2. aptX HD
Install "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" from Download of Magisk Manager or Download Here (APTX for Android Oreo & Pie NOT WORK)
3. build.prop
Open /vendor/build.prop and find "persist.vendor.bt.a2dp_offload_cap=sbc-aac" and replace "sbc-aac" to "sbc-aac-aptx-aptXHD" (Add -aptx-aptXHD)
Note: if you don't find the add "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD"
4. Restart device and test
Note: if it doesn't work undo everything you did thanks for trying
Hello my magisk cannot seem to find the module you were referring to. Do you have another link where i can download the module?
Hi There, and many thanks for you guides https://forum.xda-developers.com/member.php?u=9792389
This guide made bluetooth audio and connectio work, but bluetooth calling is not working. Can call but no sound is transmitted, so i cant use it. Any suggestions as how to proceed?
thorvall said:
Hi There, and many thanks for you guides https://forum.xda-developers.com/member.php?u=9792389
This guide made bluetooth audio and connectio work, but bluetooth calling is not working. Can call but no sound is transmitted, so i cant use it. Any suggestions as how to proceed?
Click to expand...
Click to collapse
try this , hopefully it will do the trick:
https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5
I worked.
Fillint said:
try this , hopefully it will do the trick:
https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5
Click to expand...
Click to collapse
Thanks :good: . I actually did look at the thread before, but had the impression that the GSI Treble roms were of the ASOP variant, contrary to the note: 'NOTE: This works only on CAF based custom roms. It doesn't work on AOSP.'
Am I wrong, or is it the note that does not apply in this case?
it looks like not both ways aren't working for 9.0 Havoc.
we need better solutions.
I tried these solutions on the Lenovo Z5 pro GT, but the Phone won't recognise any bluetooth IEM's. The sound keeps playing over the speaker. Does anyone have a solution?
When I change vendor to r/w it goes back to file system read only and I can't save the build.prop file afterwards
If someone was able to make it work can you please show me the build.prop permissions!!
this ROM is awesome. but there's a problem. my BT headphone no sound.
in developer options, "disable bluetooth A2DP hardware" can't be turned off. any solution?
And for xiaomi devices?
What is the apk that I have to delete if my device had miui?
in all the GSI images i installed audio BT is not working.
And BluetoothResCommon.apk is not in that path, why ?
build.prop is there but there is no "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD" entry
Any help to fix bluetooth for this case ? I can pair, to headphones connect, for a moment seems to work, but finally audio get played in the phone itself.
kidronvalley said:
in all the GSI images i installed audio BT is not working.
And BluetoothResCommon.apk is not in that path, why ?
build.prop is there but there is no "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD" entry
Any help to fix bluetooth for this case ? I can pair, to headphones connect, for a moment seems to work, but finally audio get played in the phone itself.
Click to expand...
Click to collapse
Overcame the lack of sound in BT headphones on android 10 by replacing system / lib / libbluetooth.so and system / lib64 / libbluetooth.so with stock firmware
AllexBast said:
Overcame the lack of sound in BT headphones on android 10 by replacing system / lib / libbluetooth.so and system / lib64 / libbluetooth.so with stock firmware
Click to expand...
Click to collapse
im gonna try this too because my Maxpad i10 plus as this issue
blaze2051 said:
im gonna try this too because my Maxpad i10 plus as this issue
Click to expand...
Click to collapse
Teclast M40 How to unlock bootloader?
I have found a method of Teclast P20HD to unlock bootloader which can be found in "https://forum.xda-developers.com/android/help/teclast-p20hd-android-10-tablet-4g-t4141997" and "https://forum.hovatek.com/thread-32287.html", but I'm not sure if...
forum.xda-developers.com
@AllexBast
by any chance have you experianced slow command response with ADB? I just install win10 1803 pro and its so so slow to even run adb devices command. does it make a difference if my device is running GSI Phh A11?
Did the trick for me! Thank you
SrCDA said:
This tutorial was made by Craftingmod
Thanks so much for helping us.
Original Post: HERE
--------------------------
Note:tested only on GSI ROMs 9.0
1. Bluetooth audio connection fix
Backup the file /vendor/overlay/BluetoothResCommon.apk
Simply remove /vendor/overlay/BluetoothResCommon.apk via root explorer
2. aptX HD
Install "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" from Download of Magisk Manager or Download Here (APTX for Android Oreo & Pie NOT WORK)
3. build.prop
Open /vendor/build.prop and find "persist.vendor.bt.a2dp_offload_cap=sbc-aac" and replace "sbc-aac" to "sbc-aac-aptx-aptXHD" (Add -aptx-aptXHD)
Note: if you don't find the add "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD"
4. Restart device and test
Note: if it doesn't work undo everything you did thanks for trying
Click to expand...
Click to collapse
Thanks, but editing /vendor/build.prop reaquires writing onto /vendor, so what are the apps to offer rw for /vendor?
hd_scania said:
Thanks, but editing /vendor/build.prop reaquires writing onto /vendor, so what are the apps to offer rw for /vendor?
Click to expand...
Click to collapse
It can be done with root or in TWRP.
But now most phones have aptx-aptXHD support in original firmware, so there's a high possibility you don't need this step. By the way, it is not worth it to fix A2DP though, cause for now it's almost not possible (at lease I didn't solution) to fix bluetooth in call and A2DP offload at the same time. For me bluetooth in call is more important, and there's actually no side effect to turn off A2DP offload as far as I understand.
Anyways, to make bluetooth in call and Aptx (of course others like LDAC) both work, you'll need to:
1. remove /vendor/overlay/BluetoothResCommon.apk (if presented) (if presented and deleted, do a factory reset)
2. remove /vendor/etc/a2dp_audio_policy_configuration.xml
3. Enable "Force-disable A2DP offload" in phh settings
4. Enable "use alternate audio policy" in phh settings if your volume adjustment have any problems (if you got multi ones in different feature category, try different combination until it behave normally)(may require reboot)
5. flash Magisk module "aptx-HD-magisk-10_arm.arm64.zip" to fix aptx support
Now both sbc-aac-aptx-aptXHD-LDAC and bluetooth in call should work. Tested on 2 Qualcomm setups recently with phh android 12 based rom.
Hope this could help you and others having same issues.
XT19443 said:
And for xiaomi devices?
What is the apk that I have to delete if my device had miui?
Click to expand...
Click to collapse
Tho Xiaomi's MIUI really modified the whole aosp crazyly,but the device itself is still treble-compactible
the file is called MIUIbluetoothres.apk(probably,on miui 12.5's vendor)
BUT you dont need to del it.
To Fix: TURN ON "force disable a2dp offload" in phh treble settings.
that's it.(worked on redmi 10a.(MTK))
(ps: actually aptx is a qcom thing so it probably wont work on mtk devices.)