Introduction
If you own a Chuwi tablet then you might of heard that you can install a modifed boot.img to improve the font rendering. This is not only risky as it may not work for your version of the tablet, but the results aren't that great either. Enter Chuwi Tweaks, the Xposed module that fixes the problem while also giving you some new options too.
Click to expand...
Click to collapse
Features
Font options so you that can customize the appearance
An option to restore multi-user support (Chuwi removed it)
An option to keep notifications with action buttons expanded
More to come?
Click to expand...
Click to collapse
Comparison
Before:
{
"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"
}
After:
Click to expand...
Click to collapse
Download
Xposed Repo (APK)
Click to expand...
Click to collapse
XDA:DevDB Information
Chuwi Tweaks, Xposed for Chuwi tablets
Contributors
ImADev
Xposed Package Name: com.imadev.chuwitweaks
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2016-02-16
Created 2016-02-16
Last Updated 2016-02-16
If you use Nova Launcher then I recommend going into it's settings and setting the font to condensed, increasing the text size up a notch and also setting the color to #666666 (skip setting the color for the desktop).
Personally I like the way the condensed font looks, so that's what I have Chuwi Tweaks set to use on my Vi10.
Can you add a brightness fix to the tweak, or would that require a modified kernel? I switched back to stock from RemixOS, everything works except brightness and the screen flickers a lot.
@ZeroTheSavior
What's your Chuwi model number?
Most of the people with brightness issues are using older Vi10's that still have a light sensor. The solution that people like to suggest is that you disable automatic brightness.
My model is Vi10PQ64G22150901XXX
There's no option to turn on automatic brightness in the first place.
Brightness worked in RemixOS, but I hated the lack of adb and Xposed so I flashed the first rom I could find.
I guess your build is new enough that it doesn't have the light sensor. What's odd though is that I can adjust the brightness and there's no flickering on my 221511 build.
If you've flashed the BIOS then I'd suspect that that's caused the problem, but it could easily be a mismatched kernel too. I guess it depends on how you restored Android or if it's been an issue since you bought the tablet and used Android.
Yeah, I did flash the BIOS at one point... BIOS lists InsydeH20 Version as J1D_S165C_206, which I think is 2.06. What's yours?
BIOS: J1D_S165C_206 (used in the 221511 revision)
BIOS date: 10/30/2015
MD5: d1138265c8e2825ddcf70b2e7dae2487
BIOS: J1D_S165C_206 (used in the 221509 revision?)
BIOS date: 09/21/2015
MD5: e1f93389808e45ae375be9f9d0b8030f
BIOS: G1D_S165_206 (an update for users with G1D_S165_205)
MD5: 3fbb11ac7d77fd81305bc65c88ad414a
BIOS: G1D_S165_205 (old)
MD5: 8706eb20323936956fd9932bf238b5b6
d1138265c8e2825ddcf70b2e7dae2487 might also apply to the 221510 revision.
If I were to install e1f93389808e45ae375be9f9d0b8030f onto my 221511 revision then it breaks the front facing webcam. If I then reinstall d1138265c8e2825ddcf70b2e7dae2487 everything will be back to normal and there will be no “STATUS_DEVICE_POWER_FAILURE” error in Windows.
If your BIOS is already a J1D_ version then you shouldn't ever need to update it. Only the old G1D_ builds require an update to fix some issues.
My BIOS is 09/21/15, so I guess that means I have a mismatched ROM. Guess I gotta look for another one. (Turns out there's a lot more broken things than just brightness... No sound in headphones, no Bluetooth)
More related to Chuwi software: There's no rotation options in Android settings. Is there a fix? Even Ultimate Rotation Control doesn't work.
ZeroTheSavior said:
My BIOS is 09/21/15, so I guess that means I have a mismatched ROM. Guess I gotta look for another one. (Turns out there's a lot more broken things than just brightness... No sound in headphones, no Bluetooth)
More related to Chuwi software: There's no rotation options in Android settings. Is there a fix? Even Ultimate Rotation Control doesn't work.
Click to expand...
Click to collapse
That definitely sounds like you've installed the wrong ROM. I've heard about them issues happening and I actually just linked someone to the 221509 backup images over on techtablets.
Once you've got the correct ROM installed you'll get rotation options and everything should work as you'd expect it to.
chuwi hibook here...
I cant install xposed, it seems to be arm but i get "Error executing updater binary in zip" in both arm and arm64 versions
In addition, i tried flashing the x83 version and it got flashed, but the tablet doesnt boot... how do i know what android im running?
Droid hardware info shows: ARMv7, armeabi
Yakandu said:
chuwi hibook here...
Click to expand...
Click to collapse
Hey, sorry for the wait.
Have you posted your issue to the Xposed support page as it seems your issue is with Xposed rather than this module?
I don't know if this will work, but download and install the Xposed Installer, open the app and look at the logs page. Does it say the platform is armeabi-v7a? If it does then download xposed-v84-sdk22-arm.zip and install it from recovery.
You'll need to use the sdk22 framework and you might need to adjust the jit_reset_offset if it's anything like KitKat.
ImADev said:
Hey, sorry for the wait.
Have you posted your issue to the Xposed support page as it seems your issue is with Xposed rather than this module?
I don't know if this will work, but download and install the Xposed Installer, open the app and look at the logs page. Does it say the platform is armeabi-v7a? If it does then download xposed-v84-sdk22-arm.zip and install it from recovery.
You'll need to use the sdk22 framework and you might need to adjust the jit_reset_offset if it's anything like KitKat.
Click to expand...
Click to collapse
Yeah, I tried on the support page but nothing so i came here since you own a Chuwi tablet. I didnt get a bootloop after isntalling xposed.apk, but my logs page is empty but I downloaded Hardware info and i got: ARMv7 processor rev 1
When installing xposed-v84-sdk22-arm.zip I get "Error executing updater binary in zip ..."
Yakandu said:
When installing xposed-v84-sdk22-arm.zip I get "Error executing updater binary in zip ..."
Click to expand...
Click to collapse
Are you using the Intel temp recovery solution and have you tried both TWRP and CWM? You'll normally get that error either when you're using an outdated version of TWRP or if the /system partition doesn't have enough free space, in which case uninstall any non-essential system apps that you can reinstall via the Play Store.
I guess you've already made a complete backup of the ROM? I wouldn't suggest doing any of this otherwise.
ImADev said:
Are you using the Intel temp recovery solution and have you tried both TWRP and CWM? You'll normally get that error either when you're using an outdated version of TWRP or if the /system partition doesn't have enough free space, in which case uninstall any non-essential system apps that you can reinstall via the Play Store.
I guess you've already made a complete backup of the ROM? I wouldn't suggest doing any of this otherwise.
Click to expand...
Click to collapse
Im using a TWRP version that some russians made for the HiBook, the version is 2.8.7.0...
I have 1,8gb free on /system
I tried installing x86 version of the Xposed zip and it got installed but it doesnt boot..
this is very weird
Is there any other way to install xposed?
Yakandu said:
Is there any other way to install xposed?
Click to expand...
Click to collapse
There's no other way to install newer versions of Xposed, but you could try the following.
1. Install the Xposed Installer app
2. Open it and then exit
3. Open Terminal Emulator and enter the following
Code:
su
echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
4. Boot to TWRP and install the framework
For the Chuwi Vi10 I created a custom version of the Xposed Installer so that jit_reset_offset doesn't need to be set. That wouldn't work for you though as it's built for KitKat.
I just looked into your tablet as well as similar tablets that use the Z8300. So far none of them have got Xposed to work.
ImADev said:
There's no other way to install newer versions of Xposed, but you could try the following.
1. Install the Xposed Installer app
2. Open it and then exit
3. Open Terminal Emulator and enter the following
Code:
su
echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
4. Boot to TWRP and install the framework
For the Chuwi Vi10 I created a custom version of the Xposed Installer so that jit_reset_offset doesn't need to be set. That wouldn't work for you though as it's built for KitKat.
I just looked into your tablet as well as similar tablets that use the Z8300. So far none of them have got Xposed to work.
Click to expand...
Click to collapse
Anyway, thankyou so much for your time
Related
Hello!!
The #HYPE is correct.
OPT devs are on the job for creating the best base of CM12.1
Meanwhile here is my guide to install the Xposed Framework on Stock Oxygen OS after Root.
1) YOU NEED PERFECT ROOT WITH SU. Follow THIS awesome simple guide.Before Starting to Unlock Your Boot Loader
Backup Every Bit of Your Data
Perform fill wipe op your mobile
Don't use encrypted mobile. REMOVE Encryption
Have patience, After OEM Unlock, Don't Reboot.
(Hold Volume Down + Power) to open the TWRP else you will end up in STOCK Recovery.
2) Make a NANDROID
Click to expand...
Click to collapse
Since OPT is based on ARM64, Get the following from Official Xposed Thread Here
You should get these two files
1)
{
"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"
}
xposed-v73-sdk22-arm64.zip - (5.62 MB)
2)
XposedInstaller_3.0_alpha4.apk - (611.8 KB)
Once You are ready with all the above quoted prerequisites, start
Step 1:
Download the above said two files in a folder of your OPT Internal Memory
Step 2:
Boot to recovery
Step 3:
Flash 1st file which is a Zip File
Step 4:
Reboot your Mobile after flashing normally.
Step 5:
Open the Second File (.apk) from your file browser and install.
Step 6:
Open the Exposed Installer from you app Menu.
Step7:
If everything goes well, You should find this..
Hope From this you can take off downloading the modules you would like to and enjoy tweaking the Stock ROM...
This is Youtube PopUp Module (Second one from the list) Working on my OPT
This is the Lockscreen Mod
Enjoy Guzy.. Hit Like if this guide Helped
are there any bugs? will we get OTA if we install this? can we uninstall this ? will warranty be affected? please confirm
---------- Post added at 10:10 PM ---------- Previous post was at 09:35 PM ----------
Can you tell us which are the modules that are safe and working here? so that we can test and confirm ?
Hi Bharat
OTA have no issues so far.
See my screens below running Latest of Oxygen OS
Will be certain if any more updates are out. As of now, no issues.
All modules which are for lollipop are working absolutely fine. No issues if you go through the description of each module before installing. However device specific modules which are developed for Xperia.. Samsung.. HTC.. Etc.. Can't work.
Hope this helps.
No SU for Xposed Installer
I installed the framework on my rooted OPT as per your instructions (great guide btw) but the xposed installer doesn't get SU permissions. I set it up with the same options checked as in my OPO with CM 12.1.1 . Any ideas why ?
Thanks for your time.
fpavoncelli said:
I installed the framework on my rooted OPT as per your instructions (great guide btw) but the xposed installer doesn't get SU permissions. I set it up with the same options checked as in my OPO with CM 12.1.1 . Any ideas why ?
Thanks for your time.
Click to expand...
Click to collapse
Open Xposed Installer->Framework->Reboot Grant SU permission.
Tapped from my ①+②=❸
vaisakh7 said:
Open Xposed Installer->Framework->Reboot Grant SU permission.
Tapped from my ①+②=❸
Click to expand...
Click to collapse
That didn't work, that's why I posted the question.
With only Greenfy and Bootmanager modules installed, I rebooted a dozen times but it didn't get SU permissions.
The problem was solved later on when I installed the "true silent mode" module (it doesn't work in case you want to know), wich I guess needed the permission.
Anyway, problem solved, now it has SU permissions. Thank for the help anyway.
fpavoncelli said:
I installed the framework on my rooted OPT as per your instructions (great guide btw) but the xposed installer doesn't get SU permissions. I set it up with the same options checked as in my OPO with CM 12.1.1 . Any ideas why ?
Thanks for your time.
Click to expand...
Click to collapse
Hi there..
Its because of improper rooting.
I Suggest you to re-start the rooting process from the guide above.
After OEM Unlock and recovery flashing.. DO NOT REBOOT
Then Reboot to recovery and then Don't forget to slide (RECOVERY IMAGE STABILIZING)
Then after rebooting to system..
Reset your Phone (Prefer to take a NANDROID after this)
Then Flash SU and check with Rootaccess Checker
If everything Goes well
Then Flash the Xposed Framework given above an then Install and REBOOT before opening.
Then when you open the Xposed application, then SU should popup for permission..
Hope this helps...
Did you suggest some interesting modules for Xposed on OPT ?
ps000000 said:
Did you suggest some interesting modules for Xposed on OPT ?
Click to expand...
Click to collapse
No, I just got it, and I'm trying to figure out Oxygen OS lack of funcions compared with Cyanogen wich is what sold me on the OPO.
Maybe in the next few days I will.
Just my 2 cents:
Download xposed-uninstaller-20150831-arm64.zip and keep it on your internal sd card!
In case of a bootloop caused of a trouble making Xposed mod you just flash the uninstaller to get rid of the bootloop.
Then uninstall or deactivate the mod in Xposed Installer app and reinstall Xposed again.
So when i checked the official thread for xposed it showed a newer file version than what is mentioned here. However in that v74 there are 2 versions again
xposed-v74-sdk21-arm64.zip -
xposed-v74-sdk22-arm64.zip -
not sure which one to use with my Oxygen OS 2.1
Anyone has any information on the above.
Edit : Never mind mound it.
Dude_Virus said:
So when i checked the official thread for xposed it showed a newer file version than what is mentioned here. However in that v74 there are 2 versions again
xposed-v74-sdk21-arm64.zip -
xposed-v74-sdk22-arm64.zip -
not sure which one to use with my Oxygen OS 2.1
Anyone has any information on the above.
Edit : Never mind mound it.
Click to expand...
Click to collapse
so which did you use? the 22?
I used v74sdk22
Sdk 22 is the right one.
Sdk 21 was for Android 5.0
Oxygen OS 2 is based on Android 5.1
Full list of SDK versions and corresponding Android version:
http://developer.android.com/reference/android/os/Build.VERSION_CODES.html
does whole xposed module work well on OPT? any bugs or app that isn't working or so?
22vlaja said:
does whole xposed module work well on OPT? any bugs or app that isn't working or so?
Click to expand...
Click to collapse
No issues so far!I'm running Amplify, Gravitybox,Greenify,Powernap,Notification Counter,AppOpsXposed.
Tapped from my ❶+❷
vaisakh7 said:
No issues so far!I'm running Amplify, Gravitybox,Greenify,Powernap,Notification Counter,AppOpsXposed.
Tapped from my ❶+❷
Click to expand...
Click to collapse
Did u notice some strange behavior after installing Xposed? and did u follow tutorial flash from first site?
22vlaja said:
Did u notice some strange behavior after installing Xposed? and did u follow tutorial flash from first site?
Click to expand...
Click to collapse
1.Flash the Xposed V74-arm64-SDK22 from here.
2.Wipe cache and dalvik cache after flashing.
3.Reboot and install the XposedInstaller-alpha4.apk
4.Open the app->Framework->Reboot.
5.Grand SuperSU access.
Done!
You might have missed the second step.That's not mentioned in the OP.
Tapped from my ❶+❷
allready installed Xposed, just wanted to be sure that this steps is ok!
one more thing, why did you installed AppOpsXposed? its implemented in Oxygene.
22vlaja said:
allready installed Xposed, just wanted to be sure that this steps is ok!
one more thing, why did you installed AppOpsXposed? its implemented in Oxygene.
Click to expand...
Click to collapse
AppOpsXposed is needed to handle GooglePlayServices.
Tapped from my ❶+❷
Download:
The module is available in the Xposed Repo.
Compatible Apps
Gallery3D (Cyanogenmod 11+)
Google Photos
QuickPik (4.5.2)
Description:
Ever hate when you show a friend a single photo/video and they start swiping away through your photos and videos? This module aims to help solve this issue by allowing you to lock an image. If the user attempts to swipe to another image/video they can be greeted by the application crashing, returning to the home screen, or a custom message.
Example Usage:
Example Video
Instructions:
- Enable Module
- Open Don't Swipe Module (App Drawer or Xposed -> Modules -> Don't Swipe)
- Update Hooks (Gallery3D and QuickPic excluded)
- Choose Desired Swipe Action (Optional)
- Open Desired Gallery App
- Find Desired Image/Video
- Click Three Dot Icon and Click Lock
Please make to do the step detailed above before posting for help.
To Do List (Request/Bugs):
None At The Moment
Screenshots:
{
"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"
}
Source Code:
GitHub - Link
Looks nice. I'll download it and try it.
Very buggy, needs work.
grawkiller73 said:
Very buggy, needs work.
Click to expand...
Click to collapse
Can you explain the issues you are facing? Thank you.
just what I've been looking for for ages, but causes bootloop on my nexus 5 running 5.1.1 Dirty Unicorns
DrRuckingFetard said:
just what I've been looking for for ages, but causes bootloop on my nexus 5 running 5.1.1 Dirty Unicorns
Click to expand...
Click to collapse
That is rather strange. I have a Nexus 5, so I will look into this issue immediately. I apologize for this issue you have encountered.
DrRuckingFetard said:
just what I've been looking for for ages, but causes bootloop on my nexus 5 running 5.1.1 Dirty Unicorns
Click to expand...
Click to collapse
I just tested Dirty Unicorn's Weekly 9.6 on my Nexus 5. I didn't experience any bootloop. Is you signature still current about you using version 9.5 or are you currently using another version? I want to see if I can replicate this issue.
Edit:
Tested Weekly 9.6, Official 9.6, and Official 9.5 with no issues. All done with full wipes, re-installation of Xposed, and installation of module.
iHelp101 said:
I just tested Dirty Unicorn's Weekly 9.6 on my Nexus 5. I didn't experience any bootloop. Is you signature still current about you using version 9.5 or are you currently using another version? I want to see if I can replicate this issue.
Edit:
Tested Weekly 9.6, Official 9.6, and Official 9.5 with no issues. All done with full wipes, re-installation of Xposed, and installation of module.
Click to expand...
Click to collapse
signature is outdated, I'm running weekly 9.6 (Aug 18th build i think). Had to boot into twrp and delete the app manually to get the phone to boot again
Excellent. Works with quick pic but can you make it work with stock samsung gallery app? Quickpic was sold to cm and dont want to use it now ?.
DrRuckingFetard said:
signature is outdated, I'm running weekly 9.6 (Aug 18th build i think). Had to boot into twrp and delete the app manually to get the phone to boot again
Click to expand...
Click to collapse
I can confirm this, phone was stuck at boot animation for nearly 20 mins then went to recovery and deleted apk and it booted fine, running AICP on Note 4, latest build.
I'm guessing this module doesn't work on Touchwiz ROMs either. I am using a TW 5.0.0 ROM and it bootloops when I enable this module too.
Doesn't work on my Oneplus running Blisspop 4.0 using Quickpik 4.5.2. The lock option doesn't appear inside the 3 dot menu.
Same as above but with the stock LG G3 rom.
Quickpic v4.5.2 doesn't shows the option to lock.
I apologize for the issues users are facing. I have set the module as experimental at the moment since individuals are reporting bootloops. I have tested four personal devices (Moto G, Nexus 5, Blaze 4G, and OPO) to have no issues. I am trying to nail down what may be causing issues for some, but sadly have been unable to reproduce the bootloops some are facing.
Nexus 5 latest Cataclysm. Bootloop. Does it matter if FIRST I started and configured the module (updated hooks) and THEN restart the device?
@iHelp101 Idk if I should call myself a idiot or whatever, but after failing on 1st attempt and reading your post that you tested it on 4 devices, I just out of curiosity thought to give it another try, this time reading the instructions properly. I realized that I updated hooks for Cyanogen gallery before (thinking the default gallery on my CM ROM would be Cyanogen gallery though it was Gallery3D upon checking my nick does tell that ) and maybe that caused me to stuck in a bootloop. This time tho I just installed the module and activated (read that hooks ain't required for Gallery3D n Quickpik so dint do anything other than activating) and it works like a charm now! :good: Thank you very much for this awesome module! :highfive::highfive:
AndroidNoob22 said:
@iHelp101 Idk if I should call myself a idiot or whatever, but after failing on 1st attempt and reading your post that you tested it on 4 devices, I just out of curiosity thought to give it another try, this time reading the instructions properly. I realized that I updated hooks for Cyanogen gallery before (thinking the default gallery on my CM ROM would be Cyanogen gallery though it was Gallery3D upon checking my nick does tell that ) and maybe that caused me to stuck in a bootloop. This time tho I just installed the module and activated (read that hooks ain't required for Gallery3D n Quickpik so dint do anything other than activating) and it works like a charm now! :good: Thank you very much for this awesome module! :highfive::highfive:
Click to expand...
Click to collapse
Thank you for the positive message. I will try to reproduce these steps to see if the module causes a bootloop for me. If you are able to, once again updating your hooks for Cyanogen Gallery. Reboot and see if you get a boot loop again. If so I can nail it down to the way the hooks are stored (Via SharedPreferences).
dniwe1337 said:
Nexus 5 latest Cataclysm. Bootloop. Does it matter if FIRST I started and configured the module (updated hooks) and THEN restart the device?
Click to expand...
Click to collapse
I am trying to find the correlation currently. I apologize about this and promise I will find a resolution. If you are still in a bootloop use TWRP to delete the module located under /data/app/com.ihelp101.dontswipe.apk.
iHelp101 said:
Thank you for the positive message. I will try to reproduce these steps to see if the module causes a bootloop for me. If you are able to, once again updating your hooks for Cyanogen Gallery. Reboot and see if you get a boot loop again. If so I can nail it down to the way the hooks are stored (Via SharedPreferences).
Click to expand...
Click to collapse
Bootloops.
AndroidNoob22 said:
Bootloops.
Click to expand...
Click to collapse
Found the issue. The fix should be pushed out soon.
So recently I've rooted my galaxy s5 tmobile sm-g900t and install viper4andriod. I have Busybox installed through google play and installed on both my xu and system folder. I also made sure there was enough space. Around 30mb of space. I then installed SeLinuxMode Changer and Universal init.d so that i can force the SeLinixmode changer to stay on permissive. There is a bug where restarting and exiting out the app would reset SeLinux mode you have selected. Now that that SeLinusMode restarts on permissive, i was able to install Viper4Andriod. I then continued and installed the driver, but after installation, i checked to see if anything changed in the sound. Nothing changed so i checked the driver status. It turns out to be Abnormal and unsupported. I'm running 2.3.40, and have also tried the latest version of Viper4Andriod, but both doesn't seem to work. I have stock touchwiz rom and completely disabled and removed Knox. I checked my root with Root Checker, and it passed. But for some reason going into recovery mode, it asks me to install supersu because it was missing. But at the same time, i am running PhilzTouch, which is outdated. I have tried other methods, but it doesn't seem to work. I just need to get pass the driver status problem.
If anyone know the solution to this, I'd very much appreciate it if you help us all out.
Same for me : with 6.0.1 rooted, the driver was unsupported.
What worked for me was to install viper4android from the play store, as the 2.3.4.0 version has better sound (in my own opinion) than the 2.4.0.1 that can be found elsewhere. After installing the driver in high quality, it showed as unsupported.
I had to flash two additional files that you can find here http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609 : Viper4A-[Build.Prop-Tweaks]-CWM.zip and Viper4A-[Soundfix-LibFiles]-CWM.zip. I am no expert, and probably only the second file is required but I flashed both and it just worked.
Also, you don't need a SElinux permissive kernel. You can simply flash the file linked here http://forum.xda-developers.com/showthread.php?p=61242973#post61242973, and it will patch your system. As long as you have supersu installed, you will be able to use viper4android in enforcing.
For full steps, you can also have a look at maximumentropy post here :
maximumentropy said:
...
Install the APK in the standard way (not in priv-app or most convolvers won't work).
Install the highest quality drivers and reboot to recovery
Flash the update here from recovery to allow V4A execution with SELinux Enforcing: http://forum.xda-developers.com/showthread.php?p=61242973#post61242973
Flash the Viper4A-[Soundfix-LibFiles]-CWM.zip from this message (but not the others) to replace the system sound libraries in /system/lib/soundfx with V4A-compatible versions: http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609
Reboot
In Viper settings, use Normal mode, not Compatible.
Enable V4A-FX in the desired profile (it is not necessary to use Force Enable V4A)
...
Click to expand...
Click to collapse
alexbelgium said:
Same for me : with 6.0.1 rooted, the driver was unsupported.
What worked for me was to install viper4android from the play store, as the 2.3.4.0 version has better sound (in my own opinion) than the 2.4.0.1 that can be found elsewhere. After installing the driver in high quality, it showed as unsupported.
I had to flash two additional files that you can find here http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609 : Viper4A-[Build.Prop-Tweaks]-CWM.zip and Viper4A-[Soundfix-LibFiles]-CWM.zip. I am no expert, and probably only the second file is required but I flashed both and it just worked.
Also, you don't need a SElinux permissive kernel. You can simply flash the file linked here http://forum.xda-developers.com/showthread.php?p=61242973#post61242973, and it will patch your system. As long as you have supersu installed, you will be able to use viper4android in enforcing.
For full steps, you can also have a look at maximumentropy post here :
Click to expand...
Click to collapse
It says its only for kitkat rom? Do you knw if it works for gs5 sm-g900t?
Frankie_Xenon said:
It says its only for kitkat rom? Do you knw if it works for gs5 sm-g900t?
Click to expand...
Click to collapse
Well I am sure that it works both for SM-G900F on 5.0 and 6.0.1 roms. The best for you is to make a backup of your system before trying. As it only impacts the system and not the kernel, it should work whether it is g900f or g900t...
alexbelgium said:
Same for me : with 6.0.1 rooted, the driver was unsupported.
What worked for me was to install viper4android from the play store, as the 2.3.4.0 version has better sound (in my own opinion) than the 2.4.0.1 that can be found elsewhere. After installing the driver in high quality, it showed as unsupported.
I had to flash two additional files that you can find here http://forum.xda-developers.com/showpost.php?p=52106530&postcount=609 : Viper4A-[Build.Prop-Tweaks]-CWM.zip and Viper4A-[Soundfix-LibFiles]-CWM.zip. I am no expert, and probably only the second file is required but I flashed both and it just worked.
Also, you don't need a SElinux permissive kernel. You can simply flash the file linked here http://forum.xda-developers.com/showthread.php?p=61242973#post61242973, and it will patch your system. As long as you have supersu installed, you will be able to use viper4android in enforcing.
For full steps, you can also have a look at maximumentropy post here :
Click to expand...
Click to collapse
Do you know if this works for lollipop 5.1.1? It said for kitkat rom?
Frankie_Xenon said:
Do you know if this works for lollipop 5.1.1? It said for kitkat rom?
Click to expand...
Click to collapse
Mmh I answered just above to that question? I tested it both on touchwiz with android 5 (lollipop) and 6 (marshmallow) and it works! It said "only kitkat" because at that time lollipop wasn't out you can see that the original post was dated from early 2014.
alexbelgium said:
Mmh I answered just above to that question? I tested it both on touchwiz with android 5 (lollipop) and 6 (marshmallow) and it works! It said "only kitkat" because at that time lollipop wasn't out you can see that the original post was dated from early 2014.
Click to expand...
Click to collapse
My apologies lol. My phone lagged and i ended up replying twice. Thanks ill give it a shot!
alexbelgium said:
Mmh I answered just above to that question? I tested it both on touchwiz with android 5 (lollipop) and 6 (marshmallow) and it works! It said "only kitkat" because at that time lollipop wasn't out you can see that the original post was dated from early 2014.
Click to expand...
Click to collapse
For some reason the driver keeps asking me to install it after flashing 2 the zips.
Guys, can you check this ROM(lollipop 5.1.1) for geiti94 which have all ready included this app. Very stable and battery friendly.
https://mega.nz/#!HdggTITL!C9bVqBlPwh8Kg8R7eeJQ_NokENEBwqmhkXBMNjwOZUs
Frankie_Xenon said:
For some reason the driver keeps asking me to install it after flashing 2 the zips.
Click to expand...
Click to collapse
Is your kernel still permissive? If not you can also try to flash the supolicy fix.
You can also try to remove completly the viper4android app and reinstall it.
Lastly there are some identified issues with some supersu versions. I am sure that the driver installation works with supersu 2.52 (my main one when I was on lollipop) and 2.68 (the one I use on marshmallow). Changing your supersu to 2.52 could perhaps help you. This is identified in the main viper4android thread here "If you see V4A installation pop-up loop, its probably due to incomplete root."
Hi. I have a G900H with stock rom, just rooted and Selinux enforcing and Viper works just fine. I just installed it and also installed busybox and flashed a file I got somewhere on xda to permit Viper on enforcing. I also had to verify my settings on supersu to uncheck the entry for namespaces. Hope it helps
Enviado desde mi SM-G900H mediante Tapatalk
So op, did you manage to make viper4android work?
alexbelgium said:
So op, did you manage to make viper4android work?
Click to expand...
Click to collapse
read the reply above you it gives you the solution
---------- Post added at 12:09 AM ---------- Previous post was at 12:04 AM ----------
alexbelgium said:
So op, did you manage to make viper4android work?
Click to expand...
Click to collapse
mannyvzla said:
Hi. I have a G900H with stock rom, just rooted and Selinux enforcing and Viper works just fine. I just installed it and also installed busybox and flashed a file I got somewhere on xda to permit Viper on enforcing. I also had to verify my settings on supersu to uncheck the entry for namespaces. Hope it helps
Enviado desde mi SM-G900H mediante Tapatalk
Click to expand...
Click to collapse
works like a charm thank you! lets spread this so more people will enjoy it
Also make sure "Mount Namespace Separation" is off in SuperSU.
{
"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"
}
*** Disclaimer
Code:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about the instructions or the linked things before doing anything!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you and I promise, I will!
Introduction
I decided I wanted a more up-to-date CM11 build, so here it is, a new build of LineageOS 11, for D605!
Images
{
"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"
}
Features
* Quite default LineageOS 11 but with USB OTG and offline charging
Installation instructions
* Under construction
Changelog
* Creating once finished
Downloads
Checksums:
* Uploading once finished
Download
* Uploading once finished
Sources
* https://github.com/Avamander/android_device_lge_d605
* https://github.com/Avamander/android_kernel_lge_d605
FAQ
* Under construction
Thanks To/Credits
Code:
* Varcain
* Puresoul_CZ
So, let me know if you're even interested.
XDA:DevDB Information
LineageOS 11 for D605, ROM for all devices (see above for details)
Contributors
Avamander, Varcain, Puresoul_CZ
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Abandoned
Created 2017-09-25
Last Updated 2020-07-04
Planned:
* Fix to reallow XPosed
Thanks Avamander! I'll test your ROM asap! Thank you again for your efforts!
ps: is the new build including the WiFi CRAK fix?
ps2: do you have any resource where to find any guide to compile it?
thePanz said:
Thanks Avamander! I'll test your ROM asap! Thank you again for your efforts!
ps: is the new build including the WiFi CRAK fix?
ps2: do you have any resource where to find any guide to compile it?
Click to expand...
Click to collapse
About CRACK, haven't checked, not sure a patch has been released for LOS11, if it has after the build date, let me know and I'll rebuild it.
I used the this https://wiki.lineageos.org/devices/d855/build but replaced d855 in commands with d605 and manually downloaded the sources to the according folders.
@Avamander: I tried to install your LineageOS ROM on top of a CM11 (by Varchain, the v11 release), but I get a "Status 7" error.
The error reports "set_metadata_recursive: some changes failed"
Checked the MD5 of the ZIP file and it is correct, both on my PC and on the SD.
Can you help me with the installation?
thePanz said:
@Avamander: I tried to install your LineageOS ROM on top of a CM11 (by Varchain, the v11 release), but I get a "Status 7" error.
The error reports "set_metadata_recursive: some changes failed"
Checked the MD5 of the ZIP file and it is correct, both on my PC and on the SD.
Can you help me with the installation?
Click to expand...
Click to collapse
Did you wipe /system (and /cache) and are you using TWRP v2.6.3.0 (that's what I use)?
Avamander said:
Did you wipe /system (and /cache) and are you using TWRP v2.6.3.0 (that's what I use)?
Click to expand...
Click to collapse
I was using a CWM version 2, and I had to update to the latest v3 (from Varchain, :
https://mega.nz/#!QXZUnbwQ!BRI3ENa-53StAjr2Tq1R-hmyIJ9ZDERWIAxXpx9Hye4) and it is now installing. Or do you suggest to update to TWRP?
I'll test it now.
thePanz said:
I was using a CWM version 2, and I had to update to the latest v3 (from Varchain, :
https://mega.nz/#!QXZUnbwQ!BRI3ENa-53StAjr2Tq1R-hmyIJ9ZDERWIAxXpx9Hye4) and it is now installing. Or do you suggest to update to TWRP?
I'll test it now.
Click to expand...
Click to collapse
Let me know if the latest works. If it doesn't, let me know if TWRP works
Avamander said:
Let me know if the latest works. If it doesn't, let me know if TWRP works
Click to expand...
Click to collapse
Ok, CWM v3 installed and Lineage-v11 installed, too.
The install went OK. Few issues encountered so far:
1. looks like the phone WiFi is configured for US area (thus, only channels 1-11 are working, but not mine, as it was configured on channel 13. I had to use https://forum.xda-developers.com/showthread.php?t=1982149 to properly fix it. Would be great if the ROM comes with the 1-13 set of channels.
2. Installing TitaniumBackup: install ok, but it did not run, ADB reported "libtitanium.so not found". Looks like the v8.1.0 is not able to extract the ARM library. I had to extract it from the APK (found here https://www.androidapksfree.com/apk/titanium-backup-apk-latest-version-download/download/) and manually push the library with "adb push libtitanium.so /data/data/com.keramidas.TitaniumBackup/files/"
Couldn't find anywhere else why those errors are caused. Do you have the same behaviour?
btw: thanks for your effort in keeping the D605 alive
thePanz said:
Ok, CWM v3 installed and Lineage-v11 installed, too.
The install went OK. Few issues encountered so far:
1. looks like the phone WiFi is configured for US area (thus, only channels 1-11 are working, but not mine, as it was configured on channel 13. I had to use https://forum.xda-developers.com/showthread.php?t=1982149 to properly fix it. Would be great if the ROM comes with the 1-13 set of channels.
2. Installing TitaniumBackup: install ok, but it did not run, ADB reported "libtitanium.so not found". Looks like the v8.1.0 is not able to extract the ARM library. I had to extract it from the APK (found here https://www.androidapksfree.com/apk/titanium-backup-apk-latest-version-download/download/) and manually push the library with "adb push libtitanium.so /data/data/com.keramidas.TitaniumBackup/files/"
Couldn't find anywhere else why those errors are caused. Do you have the same behaviour?
btw: thanks for your effort in keeping the D605 alive
Click to expand...
Click to collapse
I will investigate the WiFi issue... The TiBu issue, sounds weird, though a lot of old exploits have been patched and some apps might be expecting they exist. Though in my case I could install TiBu without issues from Google Play. I updated the planned task list.
Avamander said:
I will investigate the WiFi issue... The TiBu issue, sounds weird, though a lot of old exploits have been patched and some apps might be expecting they exist. Though in my case I could install TiBu without issues from Google Play. I updated the planned task list.
Click to expand...
Click to collapse
Thank you!
As a side note: CWM v3 is also able to lokify the ROM after flashing Varchain added it "because I am lazy" (cit.)
thePanz said:
Thank you!
As a side note: CWM v3 is also able to lokify the ROM after flashing Varchain added it "because I am lazy" (cit.)
Click to expand...
Click to collapse
That means it would still break the signature if I would release a signed image.
Quick update: the offline-charging is not working.
Switching off the phone and connecting the charger will boot up the phone in the default mode, not "only charging".
I know this might be a minor bug but auto brightness doesn't work.
DJ-SMOKE_300 said:
I know this might be a minor bug but auto brightness doesn't work.
Click to expand...
Click to collapse
Never has, never will, there's no brightness sensor hardware.
Avamander said:
Never has, never will, there's no brightness sensor hardware.
Click to expand...
Click to collapse
Oh. Thanks for clearing that up. All in all its mostly stable. :good:
Another thing i noticed is that some system processes crash at random times. And if I have my own wallpaper set if that happens and I reboot the device it resets.
DJ-SMOKE_300 said:
Another thing i noticed is that some system processes crash at random times. And if I have my own wallpaper set if that happens and I reboot the device it resets.
Click to expand...
Click to collapse
Seen that happen a few times, but without logs of the crash I can't help you.
1. Please remove the space character from the link to md5 for ROM.zip. I think it is easier to place a checksum instead of a link.
2. Last edited by Avamander; 26-12-2017 at 23:23. Reason: New build revert.
Has the file changed on the server, has it been refreshed or something else?
---------- Post added at 23:26 ---------- Previous post was at 23:11 ----------
Avamander said:
(...)
Installation instructions
* Use TWRP, wipe everything, (...)
Click to expand...
Click to collapse
Is there really a reason to clean Internal storage and sdcard?
> 1. Please remove the space character from the link to md5 for ROM.zip. I think it is easier to place a checksum instead of a link.
It's more work to create the file for the recovery to verify it. The space is part of the link.
> 2. Last edited by Avamander; 26-12-2017 at 23:23. Reason: New build revert.
Has the file changed on the server, has it been refreshed or something else?[
Nope
> Is there really a reason to clean Internal storage and sdcard?
Internal storage? If you mean /data, yes, but /sdcard doesn't need to be wiped.
As a sidenote, I've been rebuilding the entire system today, will see if that brings back the WiFi.
(7.1) Flyme7. Fingerprint infrared V3 For the Leeco X720 and X727 ( Updated on 9/5/2018 )
AKA: The newest version of Flyme Original Chinese Name : 7to-X720.flyme7.指纹红外V3.zip
Developer: Cold and Ruthless
Original Link: http://rom.7to.cn/romdetail/1030273
Link: https://mega.nz/#F!xYJgXYxK
Key: !QNUTt-aMXA-Kvl39hOMp9A
{
"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"
}
Flyme:
LeTV pro3 transplant Flyme7.8.21R V3
Redesigned interface, better overall experience
Advanced settings root card brush package
Optimized sound
Author: Cold ruthless
Release Date: 2018-09-04
Android version: 7.1.x
UI type: Flyme ROM
Size: 1270.00MB
Experience the new interface, with advanced settings, high speed, theming options, and excellent call and sound quality, all are hallmarks of the Meizu Official Experience
Applicable models: LeEco LEX720, LEX727
Optimization of the optimized
volume of the bottom package update sound.
Temperature control based on port from: Charm Blue Note 6 Build
Double Wipe> reboot to Recovery, if you have an error you may need to format storage
The first boot is very slow, please wait for the Meizu official latest experience version transplant
Past Bluetooth issue resolved.
Optimization scheduling
New interface new experience, advanced settings and optimization
Installation Notes:
First Boot may be slow, so if it takes a while for the first system boot, the solution is just to wait longer.
Flyme Account http://forum.flymeos.com/
Create an Official Flyme account if you want to gain access to tons of addons.
Meizu is Port friendly and Flyme Account Provides:
Forum advice
Plugins,
Apps,
3rd party themes etc.
Download Flyme 7 Launcher, Stock Wallpapers, and Apps (Flyme 7 stock APK)
https://www.androidsage.com/2018/05/15/download-flyme-7-launcher-stock-wallpapers-apps-apk/
As always, flash anything under your own discretion
Root
This Rom comes with Magisk root, You can easily flash Magisk 17.1 overtop after setting up the system and then rebooting to recovery.
Gapps: I am using BeansGapps-Mini-7.1.x-20170725.zip
Helpful files:
https://mega.nz/#F!JMYSSCLQ
Key: !xgQFTB69PE-hL8RTUbpUIw
Firmware
https://mega.nz/#F!oAZ3yC4b!
Key: MDwbHXNTRdrpgMvQ42yviw
If you have safetynet issues, follow the steps below
Extract the boot.img file from the rom, and placed the boot image into storage.
Open Magisk and use install to Patch Magisk to the boot.img.
Reboot to recovery, install the patched boot.img to boot
Flash addonsu-15.1-arm-signed.zip, and then reflash Magisk again, from storage then use advanced options to clear cache, and then reboot to system.
With these steps you will always Pass Safetynet and be playstore certified
https://forum.xda-developers.com/showpost.php?p=77367331&postcount=4790
Build Prop Recommendations
After the installation and initial testing period,. you may decide to continuing using Flyme for a while:
If so you can further optimise the ROM with these build prop and edits posted below.
First backup your existing buildprop
* ro.product.locale.language = en ( or your language)
* ro.product.locale.region = IN or your country
* persist.sys.timezone = your country ( see proper entry here: https://gist.github.com/arpit/1035596)
* persist.sys.meizu.region =
or use persist.sys.oem.region= your country google correct acronym for your country
Reserved for future hints
Thanks I will try and feedback
i get error code 3 when i try to flash
rob_z11 said:
i get error code 3 when i try to flash
Click to expand...
Click to collapse
Me Too!
Yes, I tried it and the same thing happened to me, it must be a corrupt download because people are giving the release a 8.3/10. I found a slightly older but highly rated rogue pig version. ( see same link above)
I installed it successfully and must say, it's actually extremely good.
Corruption
The original newer file is probably just corrupted so I am going to try redownloading it. Until then, check out the other version that I placed in the same megadrive folder see the link above. Yes, it's a little older but its actually awesome!
I just attempted to find the newer rom by cold ruthless on the BBS website, has he been banned. I had a bookmark saved and when I click I get this message " Authors are banned or deleted automatically blocked" Not sure if its the same person or not, if this next download is corrupt. I would still recommend flyme_LEX720_rogue_6.8.3.17R-beta, I am testing it right now and like it alot.
Does Android Pay work with this ROM?
I flashed the ROM after the boot I face a black screen and a bar with Chinese written and I can't do anything only control the volume...I only flash the ROM with wipe the data,system and delvic cach
3llawi said:
I flashed the ROM after the boot I face a black screen and a bar with Chinese written and I can't do anything only control the volume...I only flash the ROM with wipe the data,system and delvic cach
Click to expand...
Click to collapse
No issue like this. Everything worked. It booted fine. You may have to use the recovery version from earlier in the month of Jan.
Everything worked for me except volte which is no big deal. Really impressive build. Thanks for downloading @tsongming..
3llawi said:
I flashed the ROM after the boot I face a black screen and a bar with Chinese written and I can't do anything only control the volume...I only flash the ROM with wipe the data,system and delvic cach
Click to expand...
Click to collapse
It looks like what happened to me when going from an Oreo rom to Nougat, you have to format data not only wipe data. Format data, write "yes" and then install the rom. Always have a backup of your data before.
flyme is one of the best system , the official one is good but it's old , be sure to have eui firmware before flashing flyme .
rob_z11 said:
No issue like this. Everything worked. It booted fine. You may have to use the recovery version from earlier in the month of Jan.
Everything worked for me except volte which is no big deal. Really impressive build. Thanks for downloading @tsongming..
Click to expand...
Click to collapse
Please can you put the link of old recovery version
rob_z11 said:
No issue like this. Everything worked. It booted fine. You may have to use the recovery version from earlier in the month of Jan.
Everything worked for me except volte which is no big deal. Really impressive build. Thanks for downloading @tsongming..
Click to expand...
Click to collapse
Did you format internal storage?
3llawi said:
Did you format internal storage?
Click to expand...
Click to collapse
No because I have always been on miui10
can some1 link me the gapps?
collisiion said:
can some1 link me the gapps?
Click to expand...
Click to collapse
Look at the post #1
Thanks to troubleshooting from @ rob_z11, I plan to post a working version of the Cold Ruthless file late tonight EST.
andrew2401 said:
Does Android Pay work with this ROM?
Click to expand...
Click to collapse
I believe so, though I haven't tried it yet. I will let you know late tonight
tsongming said:
I believe so, though I haven't tried it yet. I will let you know late tonight
Click to expand...
Click to collapse
Okay thank you how's the battery so far?; I've owned Meizu phones and there is was always good for battery optimization
tsongming said:
Thanks to troubleshooting from @ rob_z11, I plan to post a working version of the Cold Ruthless file late tonight EST.
Click to expand...
Click to collapse
Ok, this is what I have found. Your original latest flyme seems to be working ok. Here is what I have done. Using RAR apk, I unzipped it, and it complained about one apk in mizu-apk folder, and I ended up removing that folder completely, and zipped the ROM again. It flashed without any issue, but I can't seem to get Data to turn-on. It turns on briefly during the boot, but it goes away. I think if I compare the build.prop from older version with newer version, I may be able to find the fix.
andrew2401 said:
Okay thank you how's the battery so far?; I've owned Meizu phones and there is was always good for battery optimization
Click to expand...
Click to collapse
Extremely good, at the moment my phone has no OS at all..
I only glanced at battery life briefly yesterday with Gsam battery tool. Plus, I installed BlackScreen 5.3 r2 which worked fine, I would rather wait for a real answer. Otherwise it would just be a guess.