Hi,
Is there any mod for increasing maximum sound volume?
Im looking for the exact same thing. Have tried suggestions of using Viper but to be fair I dont find it does alot. Need a proper solution like they had on the S4 and on my HTC One.
viperFX 10.1(2014) working solution KK 4.4.3
Viper is amazing. I've been using it for about 1 year under 4.3 .. i consider it one of the essential apps for my 10.1 (2014).. But when i upgraded to 4.4.2 I could not install.. I tried all the basic comobinatios (install busy-box first..then SU, flash SU then install buxybox install driver, ok install SU then flash viper, then blah blah ) the error message was always the same.. "you don't have a full-root, or your busy-box is not correct/complete" or some such.... I'm sure the developer is not trying to be deceptive, but these error messages were not that helpful, indeed this is just a symptom of many possible issues. SO I decided to dig in and sort it, took awhile , but I'm posting my very long winded howto..In case others might have this specific issuue you will know if ou read this..and (hopefully) you can fix your viper too.
(0) My kit: samsung/lt033g:4.4.2/KOT49H/P601XXUCNJ5:hanspampel Linux version 3.4.39-3098518 xkat-3.0 ROOTED . Cool ROM, but I at first since I had no cluse, I wondered if this inability to install V was due to this R..I tried antoher hydronium-ROM same prob, scratch that.Next I started reading, and I discovered to my horror this symptom has been reported many places, I found countless solutions in various posts not very helpful but entertaining something like "flash this file, then flash this, then dude enable this and then DUDE ITs AWESOME sounds KILLER BRO.." .. The rpint is that this one symptom has many different underlying causes, no one has explained (or I have not seen a post) yet that does that. so that is what you are geting here.
(1) installing viper (standard way the way you have done it) app store, or click on apk never worked..What is partial root anyway? doesn't matter.. So my stragety here is , when I"m lost in this situation, I have two things to look at..
debug (logcat -vv time ) or
specifc level of debug logitE='logcat -v time process tag *:E' (i put this under /system/etc/mksh after remountin /system RW so I can have a decent working environment.. And or figure out what the apk was having trouble with..So get a copy of the apk . first you might see a zip file ViPER4Android_FX_v2340.zip. this contains two files
ViPER4Android_FX_A2.3.apk (XHiFi)
ViPER4Android_FX_A4.x.apk (effects)
I've always used the FX_A4 version before, I don't really know what the A2.3 is.. anad have a look.
(2) Looking at the APK. Apk's are just zip files. change the .apk extension to .zip and unzip it on your PC (by the way it helps to have adb working, but it is not required).. In the apk for viper I saw directories.. an assets, lib and res dir to be exact I haven't developed anythig on android yet mostly xcoder person. so I was clueless.. but you can work out by the directory's what its trying to do..The top level dirs were res, lib, assets and META-INF, I don't care about the UI stuff in META or res, that was working, in otherwords when we installed the apk, you see the VIPER user interface installs and launches..Its at that point you are asked to install the drivers to get viper to work, so we know the UI is OK and the SU thing make me suspect permissons.. BY the way there was conversation about SE_Linux regarding this install..(permissive / enforcing). I tried that too, so since KK 4.4.3 , SE_Linux was made to be in enforcing mode, before it was just permissive (sending warnings but did not deny any thing)..Now SE_Linux is for real,, If you look at the app-permissions, not file permissions but app permission of VIper there was one funny permissions issue.. "PERMISSION_ACCESS_SUPERUSER" " was unknown. I thoguht maybe this was it! I got "SELiuxModeChanger" (this needs root but apparently can change SE_LIN back to permissive.. its not clear if it really wokred) but I tried it..switched my phone back to permissive mode but i still got the same error.Even after rebooting.. and I set the notificagion "You are In PERMISSSIVE mode" but you open the app and it's in enforcing.. (smell some cheese here..?) .
Sorry for the side traack.. back to the APK, So the apk had a lib directory, an assett directory, are what we are intereseted in.. also I saw on the web there were two system files that needed modifying:
/system/etc/audio_policy.conf /vendor/etc/audio_effects.conf
So know I knew I have to manually place some lib (librarys) and modify some system files.. After rebooting at this point (with this totally broken install) "logcat -v time | grep -i viper
4111): Jni library status = false..
if you look on the apk:
lib/armeabi/libV4AJniUtils.so*
so the system is complaiing about a JNL lib is missing, which means the system files or a system file was modified so the sysem knows to look for the jnl file, and this jnl file is pert of the install which failed..... So plop libV4AJniUtils.so* /system/lib. (via any means you choose) FiLE permissions to 644 "chmod 644 libV4AJniUtils.so* reboot and clean cleared cache(s) in recovery , then rebooted and volla one small step:
I/ViPER4Android( 4111): Jni library status = true
So YOU must see the message as part of the criterial for successful install.
but I still had probelms..
0I/ViPER4Android( 4111): Starting service, reason
I/ViPER4Android( 4111): Check driver
I/ViPER4Android( 4111): Found 13 effects
I/ViPER4Android( 3744): ViPER4Android engine not found, create empty service
04-12 19:57:55.374 I/ViPER4Android( 3744): Service:nStartCommand [Begin check driver]
04-12 19:57:55.374 E/ViPER4Android( 3744): Service:nStartCommand [V4A Engine not found]
I/ViPER4Android( 4111): could not find ViPER4Android engine at 13..
So we are still missing a lib, the viperEngine.. that probably one of the files located in the assets dir..
[email protected] 10 mikel staff - 340B 11 Apr 06:42 ../
[email protected] 1 mikel staff - 926K 12 Feb 11:15 libv4a_fx_ics_X86.so*
[email protected] 1 mikel staff - 810K 12 Feb 11:15 libv4a_fx_jb_NEON.so*
[email protected] 1 mikel staff - 814K 12 Feb 11:15 libv4a_fx_jb_NEON_HQ.so*
[email protected] 1 mikel staff - 810K 12 Feb 11:15 libv4a_fx_jb_NEON_SQ.so*
[email protected] 1 mikel staff - 554K 12 Feb 11:15 libv4a_fx_jb_NOVFP.so*
[email protected] 1 mikel staff - 818K 12 Feb 11:15 libv4a_fx_jb_VFP.so*
[email protected] 1 mikel staff - 926K 12 Feb 11:15 libv4a_fx_jb_X86.so*
[email protected] 1 mikel staff - 923K 12 Feb 11:15 ViPERDDC.db*
[email protected] 1 mikel staff - 810K 12 Feb 11:15 libv4a_fx_ics_NEON.so*
[email protected] 1 mikel staff - 814K 12 Feb 11:15 libv4a_fx_ics_NEON_HQ.so*
[email protected] 1 mikel staff - 810K 12 Feb 11:15 libv4a_fx_ics_NEON_SQ.so*
[email protected] 1 mikel staff - 554K 12 Feb 11:15 libv4a_fx_ics_NOVFP.so*
[email protected] 1 mikel staff - 818K 12 Feb 11:15 libv4a_fx_ics_VFP.so*
[email protected] 1 mikel staff - 16B 10 Feb 15:37 ver.txt*
(3) finish intsall
I don't know what to do with any of those files.. and I don't know what chanegs need gto be made to the .conf files.. this version of the driver I can't find anything that looks like a script.. it must be hidden in the install stuff somewhreer.. stuck..so where do you go when you are stuck?
xda-developers of course..and usually someone will have said something..Many people had alot of posts (because viperFX is so kick ass everyone wanted to get it to work). Yes all the posts about my problem were so last year.. well what I say I'm slow.. and none of them could explain to me exactly how to get it to work... I saw one post that had some zip files:
http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
This is the lollipop viper for nexus.. not my phone, but it had lots of conversation. Remember I am on Kit Kat so my story differs, regardless I read along and found 3 zip files:
Viper4A-_Build.Prop-Tweaks_-CWM.zip
Viper4A-_Soundfix-LibFiles_-CWM.zip
viper_v2.3.3.0.zip
I did not put a link to the files because you don't need these files, I just used them to understand how to get 2.3.4.0 to work. So if you want to down load these files, you have to find them, because if you install them on anytying but the proper device it will bric your phone (hang it..)
However they were useful, because they showed me:
audio_effects.conf.txt*
audio_policy.conf.txt*
/system/lib/soundfx/libv4a_fx_ics.so*
how the install was supposed to look like.
The fact that I had files designed for CM mod, means I am at rrisk for BRIC-OLA.. but I had no intention of using any of the binaries, I just used the conf files to modify my sysem comf files.. If you do a diff you can see the changes..the big for me was the engine location:
/system/vendor/etc/audio_effects.conf
ibraries {
v4a_fx {
path /system/lib/soundfx/libv4a_fx_ics.so
}
bundle {
path /system/lib/soundfx/libbundlewrapper.so
}
...
I knew where to put the enginelib. However none of my lib in the apk/asset dir were of the name libv4a_fx_ics.so Well looking back at the logs I saw an message (I did not save it) that said from the viper install something like "CPU IS NEON xxx, CHoosing Driver libxxx" so I was able to see what lib the viper install would have chosen.. what about HQ/SQ naming? I remembered that we have 3 choices to install the driver, basic or low battery drain, high, and super..we have 3 ibs nohting HQ (highQuality) andSQ (SuperDuperQuality).. so thats how that works..I went ahead and pushed the ibv4a_fx_jb_NEON_HQ.so* /system/lib/soundfx dir..renamed the lib to libv4A_fx_ics.so changed file permissions to 644.. and rebooted. It worked sorta..
I saw this:
Check driver
04-11 10:31:09.970 I/ViPER4Android( 4111): Main activity onResume()
04-11 10:31:09.970 I/ViPER4Android( 4111): onResume(), Binding service ...
04-11 10:31:10.005 I/ViPER4Android( 4111): Query ViPER4Android engine ...
04-11 10:31:10.010 I/ViPER4Android( 4111): Found 13 effects
04-11 10:31:10.010 I/ViPER4Android( 4111): [1], SoundAlive, Samsung
....
04-11 10:31:10.015 I/ViPER4Android( 4111): Android System this driver not supported
found ViPER4Android engine at 13
Service:nStartCommand [V4A Engine not found]
I/ViPER4Android( 4111): could not find ViPER4Android engine at 13..
So.. viper driver was being rejected? I tried a few others.. same message.. then I rememberd that I was not clearing the cache .. so I tried again after claering the cache and I got this:
I/ViPER4Android( 4111): Perfect, found ViPER4Android engine at 13
I/ViPER4Android( 4111): The version of ViPER4Android engine is 2.3.4.0
I/ViPER4Android_v2( 2291): Welcome to ViPER4Android driver [Happy new year!]
I/ViPER4Android_v2( 2291): ViPER4Android is normal audio quality mode
I/ViPER4Android_v2( 2291): Use 24bit fixed point calculating arch, round res
THis is the second message YOU must have for VIPER to work on your phone.
OK everything is great! I rebooted turned on my favorite music (RUSH 2112) and what do you know.. it didn't work. Opening Viper and checking the driver status, it said "not enabled" but it was installed.. WTF.?.It did have power, but still nothing..So I remembered reading that someone their bluetooth worked, but going through speaker mode did not. I switched to a bluetooth speaker.. and this time I had:
NEON enabled: yes
enabled: yes
process NO
Process NO? but eerything else yes.. How hard are we today..man.. I knew I was close, so i looked in the logs..
AudioPolicyManagerBase( 2291): selectOutputForEffects outputOffloaded 0 outputDeepBuffer 0
04-12 14:33:00.784 V/AudioPolicyManagerBase( 2291): selectOutputForEffects outputOffloaded 0 outputDeepBuffer 0
W/BufferQueue( 2285).ViPER4Android] cancelBuffer: BufferQueue has been abandoned!
Seems like somehow a buffer is not happening.. this is getting alittle deep for me, but there are many different combinations to try (turn on viper first, then music, then bluethooth.. or BT first, music viper..etc) Also happily I have a "music effects" in my settings where I can choose MUSICFX (samsun's binary) or Viper. SO I found that did not do much, but if I killed Viper, then started it (go to the UI) and powered it up) it had processing set to yes) at that point viper works perfectly. I'm not exaclty sure what the buffer issue is, and I have not made changes to my audio_policy file.. I want understand that first.. but good enoght for now.. Finally Hats off to VIperDevelopers.. its hands one of the most amazing music enhancements I have ever heard.. Don't quite know why its such a pill to install.. sorta feels like no one is taking care of the baby.. well this baby rocks.. someone aught to.. (I'll do it!) anyway all I can say is you are genius and Brilliant software / hareware developers.. when i grow up I wanna be just like you guys.. thanks again hope this post help.. Hope I am not posting anything I shouldn't I have never posted to xda before..
Related
GST
(Galaxy S Tweaker)
This post is not about your Tax! (lol)
Before anything this application is not par of any other project.
This application is a new version of this one : http://forum.xda-developers.com/showthread.php?t=808555
I create a new thread because the application has changed a lot, and in the first version, there was a very very very very annoying bug which has formated their SD-CARD (I'm really sorry for them!).
The bug has been fixed, but may be their are others more dangerous, I've not installed all firmware available, so I've not test all the options.
To avoid some strange bugs, turn on USB debugger in your preference menu (in section application, sub section development).
Disclaimer: I will not be able to test each and every version of the MOD included, so I will not be held responsible if the mod doesn't work, or if your phone doesn't boot. Though the max you will have to do is to reflash firmware using odin.
Please keep a current backup of you apps/data and the original framework-res.apk before flashing
The best thing you can do is a nandroid backup before applying any modification to your phone !!!!!!!
Please, I read most of the comments here and in the market. Most phones broke run a firmware not supported by the app. The name of firmware supported for each function is always indicated.
Don't try a file not made for your phone. Particularly, don't use JP6 file for JI6 firmware (15 phones broke for this firmware only) !!!!!!!!
Technic to repair your phone when it's broken : flash it by using Heimdall with the same firmware that the one installed. If you use lagfix, don't forget to reinstall it. You should recover your data.
Now, about functions of this application:
help to root your phone (Eclair, and just JP1/JP2 for Froyo)
help to install voodoo lagfix (version beta 4, the beta 5 does not exist yet in update.zip, and is not yet totally finish)
help to disable voodoo lagfix (needed to update your ROM)
help to change your screen lock
help to change your fingerprint to access protected applications on the market (at the moment I use the fingerprint of droid eris phone, may be it's a better idea to use Nexus one / Desire fingerprint to access to only froyo app, like flash, if you have one of these fingerprint, can you give me it?)
I've other ideas to include, but for the moment I must be sure what I've ever done is Ok. So let me know if their is a bug.
Before using this application, make a backup of your data.
It's really possible that this application break your phone (I don't hope, but I know now that all is possible). You will have to flash your phone again. So, MAKE a BACKUP.
Most of the things included in this application is from another thread of this forum. Thanks to the authors of these tips/tools...
In particular, I want to thanks : supercurio (voodoo lagfix), Ateisti / Project01.exe (Screen Locker).
If you are interested in these project :
voodoo lagfix : http://project-voodoo.org/
screen lock : http://forum.xda-developers.com/showthread.php?t=784992 and http://forum.xda-developers.com/showthread.php?t=779803
battery : http://forum.xda-developers.com/showthread.php?t=765419
Updates (I forgot what I've done in other updates..., but now, I'll update here!) :
Error in downloading JP6 deodexed stock screen locker and vibrant voodoo lagfix are fixed!
version 2.93 : Add JPO/JPA support
version 2.92 : fix bug in fingerprint function
version 2.91 : Before this update, the app was not able to get write rights on system directory when voodoo lagfix was activated. Now, it's Ok!
version 2.90 : add a new backup/restore your kernel function
version 2.85 : display bug fix
version 2.84 : bug fix
version 2.83 : now use thread to execute the script generated. Should improve things.
version 2.82 : another another another bug fix... I will fix it!
version 2.81 : another bug fix (now ask su rights at the launching of the app, I think that it's a source of some of bricked phones)
version 2.8 : bug fix (add a sync command at the end of script to change battery icon, should improve things)
version 2.70 : new function - change icon battery [experimental]
version 2.60 : support now voodoo lagfix v5 for screenlock changer !!!
version 2.50 : add some security checks
version 2.40 : remove use of busybox in change screen lock
version 2.30 : another big bug corrected... and some text modifications thanks to Darkstriker
version 2.2 : some messages updated
version 2.1 : correct a bug in screen locker changer (about rights to write in system folder)
version 1.5 : bug fixes
To come (make some propositions):
APN file
Stop media scanner
Change battery icon
reboot buttons
But to make improvement, I must be sure that the actual version works well, so don't hesitate to write here the function XXX works well
And don't hesitate to rate 5 stars the app in the market!!!!!!!
Screenshots are not up to date... but I will do it... but I don't when
hope battery mod will be included. looks good!
download link?
link? where can i dl it`?
thx for effort dude! ..I will check it out....
bigp90 said:
link? where can i dl it`?
Click to expand...
Click to collapse
Euuhhh ... Market ?
snoopy33 said:
Euuhhh ... Market ?
Click to expand...
Click to collapse
i dont find it there
bigp90 said:
i dont find it there
Click to expand...
Click to collapse
Ok, first thing repaired !
Now published on market.
Thanks
There is a small bug I can spot from the screens: "Change your printfinger"
Haha, I love that term.
Rosa Elefant said:
Haha, I love that term.
Click to expand...
Click to collapse
Now Fixed!
mike.sw said:
hope battery mod will be included. looks good!
Click to expand...
Click to collapse
yeah, it's for the next version!
good work snoopy
plz upload somewhere an put dl link here
i dont can install on other lockscreen
or iam just to stupid^^
snoopy33 said:
Now Fixed!
Click to expand...
Click to collapse
I havent tried the app yet but looking at the screen a lot of the text has errors or sounds clumsy.
If you want to, you can send me all text from the app and I will look over it for you.
another idea for you, add an apn file download button. can help so many ppl setting their apn setting right with a click of a button
I can't seem to apply the root on Froyo. When I try it says
E:signature verification failed
Istallation aborted.
How does it install the Voodoo lagfix for Froyo?
kazim said:
I can't seem to apply the root on Froyo. When I try it says
E:signature verification failed
Istallation aborted.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/showthread.php?t=788108
Haha Looks intersting.. HOWEVER in my country GST means Government Service Tax >.< I hope there is no Tax for this thing haha
GST means Goods and Services Tax in New Zealand, it's a 15% Tax on all Goods and Services.
With a lack of Custom ROM support for this device, I took it upon myself to modify the stock ROM a bit. Since this is the first time I have done anything like this, please do not expect much. As of now - the mods are as follows:
Baked in SU/Busybox
Added Google Play (actually uses the phonesky.apk and will update automatically to latest version after signing in)
A few Build.prop tweaks
Zip aligned
So far my tablet seems a little more responsive but the main advantage is to those who are having trouble rooting or installing Google Play. Now that CWM recovery is available for this device, flash that recovery image first. Directions for this can be found here: http://forum.xda-developers.com/show....php?t=2189640
Once CMW is installed, wipe data/cache/dalvik and then flash the ROM!
Remember that when you first sign into the "Market" app it will take about 10 minutes for the app to auto-update to the newest version of the Play Store.
Like I said, not much here but I welcome any suggestions for improvement.
DOWNLOAD
I've been meaning to try this as I have 5 of these tablets in my house and I'm sick of everyone bugging me to put games on them since they don't have the play store. One of these days I will set up an assembly line of tablets and root and flash this rom.
Sent from my SPH-D710 using Tapatalk 2
Thanks for this. Now installing CWM & rooting can both be achieved straight from the tablet!
More specific directions for installing CWM here: http://forum.xda-developers.com/showthread.php?p=42882562#post42882562
As for suggestions... deodex? more tweaks?
Thanks for this, I've been waiting for a while, downloaded and about to flash, thanks again will let you know if I find any fc's.
so i tried this it rebooted but no touch screen controls. i dont know what i did wrong. i did delete everything in cwm as said
Didn't work for me.
I tried to flash this from the recovery and the tablet couldn't verify the signature (?) and refused the update. I think I need a livesuite image of this tablet to fix it.
Good luck with that, I've ended up returning my tablet, there is one livesuite image but it was corrupted and it never worked...
Sent from my SPH-L710 using Tapatalk 4
Yeah I tried that one too.
jocarog said:
Good luck with that, I've ended up returning my tablet, there is one livesuite image but it was corrupted and it never worked...
Sent from my SPH-L710 using Tapatalk 4
Click to expand...
Click to collapse
I tried the supposedly 9.7 image, now the tablet has no video. Don't have the hdmi cable so I can't check if there's video.
anybody else have issues.
I wanted to update my Trio with this ROM but was not sure if i should after reading the posts here. Has anybody been sucess with this ROM?
Don't do it if your model is 9.7c
Good night bro please nedd help with the rom
stevenj05 said:
Don't do it if your model is 9.7c
Click to expand...
Click to collapse
GOOD NIGHT BRO PLEASE NEDD HELP WITH THE ROM IM CARLOS AND I DAMAGE THE ROM OF MY TABLET AND NOW I DO NOT GET THE ORIGNAL FACTORY INSTALLED OTHER BUT HE WILL NOT GET THE TRUE PLEASE HELP ME IF YOU CAN great maid
Great!
Works as advertised, though not a lot of noticeable speed improvements. Thanks.
Mach Speed Trio Stealth Pro 9.7 Bricked. Help Me Please!!!
Hello. First of all, this is the first time i'm posting here. I have a Mach Speed Trio Stealth Pro 9.7 Tablet, and I tried to install a custom rom using clockworkod recovery. I made a huge mistake because the screen doesn't work. When I press the power button it starts, but there is nothing on the screen. It just stays gray colored. I have looked around so many websites for a solution regarding this tablet, and It seems the only possible solution is to flash an image rom using Livesuit. The problem is that I need the specific image rom for this Tablet, and I haven't been able to find it nowhere. Does anyone here has a possible solution to fix this tablet? I would really apretiate any kind of help. THank you very much.
Mach speed 9.7
bwilde83 said:
With a lack of Custom ROM support for this device, I took it upon myself to modify the stock ROM a bit. Since this is the first time I have done anything like this, please do not expect much. As of now - the mods are as follows:
Baked in SU/Busybox
Added Google Play (actually uses the phonesky.apk and will update automatically to latest version after signing in)
A few Build.prop tweaks
Zip aligned
So far my tablet seems a little more responsive but the main advantage is to those who are having trouble rooting or installing Google Play. Now that CWM recovery is available for this device, flash that recovery image first. Directions for this can be found here: http://forum.xda-developers.com/show....php?t=2189640
Once CMW is installed, wipe data/cache/dalvik and then flash the ROM!
Remember that when you first sign into the "Market" app it will take about 10 minutes for the app to auto-update to the newest version of the Play Store.
Like I said, not much here but I welcome any suggestions for improvement.
DOWNLOAD
Click to expand...
Click to collapse
Hello, I have this same tablet and I tried it and I have no touch and wifi. I have followed every step and it does boot up. I have a back up of all drivers and information is there anyone who can help me?
Mach speed 9.7c
bwilde83 said:
With a lack of Custom ROM support for this device, I took it upon myself to modify the stock ROM a bit. Since this is the first time I have done anything like this, please do not expect much. As of now - the mods are as follows:
Baked in SU/Busybox
Added Google Play (actually uses the phonesky.apk and will update automatically to latest version after signing in)
A few Build.prop tweaks
Zip aligned
So far my tablet seems a little more responsive but the main advantage is to those who are having trouble rooting or installing Google Play. Now that CWM recovery is available for this device, flash that recovery image first. Directions for this can be found here: http://forum.xda-developers.com/show....php?t=2189640
Once CMW is installed, wipe data/cache/dalvik and then flash the ROM!
Remember that when you first sign into the "Market" app it will take about 10 minutes for the app to auto-update to the newest version of the Play Store.
Like I said, not much here but I welcome any suggestions for improvement.
DOWNLOAD
Click to expand...
Click to collapse
I have tried your firmware and I was wondering if you can help me out with the wifi. I do have a backup of my firmware but My data won't restore. Please help.
Darice
factory img
I have posted in other threads that I have the original img for the 9.7 I flashed it on my 9.7c and everything seems to be fine. Find it here:
h t t p s : / / d o c s.google.com/file/d/0B0ErylDjXdUxMU1FTFBKQ1RnNWM/edit
If it works for you please let other members know that a factory img is here. Use livesuit to flash. Use at own risk. Is there a moderator that can upload this to the roms section? Thanks
So messing around it's still black screen with backlight but HDMI works. Touch screen is way off but I was able to get to settings and still a 9.7 that doesn't work for me at least.
Sent from my Nexus 7 using XDA Free mobile app
diddley813 said:
I have posted in other threads that I have the original img for the 9.7 I flashed it on my 9.7c and everything seems to be fine. Find it here:
h t t p s : / / d o c s.google.com/file/d/0B0ErylDjXdUxMU1FTFBKQ1RnNWM/edit
If it works for you please let other members know that a factory img is here. Use livesuit to flash. Use at own risk. Is there a moderator that can upload this to the roms section? Thanks
Click to expand...
Click to collapse
ive flashed mine with this , and still not seeing anything on screen except the backlight, anyone kknow how to fix that?
HAHA.... Better late than Never!
I reserved this spot. Not thinking of the minimum post count! Now that I'm able to post pics/links, I'm here to make this spot productive!
TABLE OF CONTENTS!
1. [ZIP]CWM6028-A10-RECOVERY-v2
2. [MODDED BACKUP] build.prop
CHANGES AND REASONING!
---- 1. I changed the dalvik.vm.heapstartsizes (Minimum for 4.0.4? 512...)
---- 2. Set wifi.supplicant_scan to 240 (I get 3 Days battery with light browsing)
---- 3. Windowsmgr.max_events_per_sec set to 90.
---- 4. Changed some settings to make it not be from china anymore.
---- 5. Fixed a typo in net.tcp.buffersize.default and net.tcp.buffersize.wifi
---- 6. STAGEFRIGHT ENABLED! Security risk, I have not checked this vulnerability yet...
---- 7. I kept it to HW rendering because the sun4i is a powerhouse when it comes to graphics and fast I/O.
---- 8. There are some things you can play around with, but; not many of them will make a benefit! DO YOUR RESEARCH!
3. [POST #22] RTL_WIFI_SDK.TAR.GZ (LINUX/UBUNTU/VM)
4th. Coming....
Beginning of the logcat.txt - Kernel Init
Now, this would not be fun if I posted the whole logcat.txt... Here are the first identifiers and architecture dialogsl!
-- FIELDS IN RED = MUST BE IDENTICAL TO YOUR OWN RESULTS || ENTRIES IN GREEN = MAY VARY BASED ON SEVERITY OF THE INCONSISTENCIES! OTHERWISE --
--- HERE IT IS (JUST TO HELP THOSE HAVING TROUBLE IDENTIFYING THEIRS) ---
Linux version 3.0.8+ -- ICS Minimum Kernel v3.0.4 --
([email protected]) -- 'inet' and/or 'crane' indicate correct board config, 'cube' is the same Board Family but it IS A DIFFERENT DEVICE!
(gcc version 4.5.1 (Sourcery G++ Lite 2010.09-50) ) #3 PREEMPT
D/Kernel ( 0 ): CPU: ARMv7 Processor 413fc082 revision 2 (ARMv7); cr=10c53c7f
-- THESE VALUES WILL (ALMOST) NEVER CHANGE ONCE SET, BUT; THEY WILL NOT BE THE SAME AS MINE!
D/Kernel ( 0): <7>[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
D/Kernel ( 0): <7>[ 0.000000] Machine: sun4i
D/Kernel ( 0): <6>[ 0.000000] Total Detected Memory: 1024MB with 2 banks
I/Kernel ( 0): <6>[ 0.000000] Memory Reserved(in bytes):
I/Kernel ( 0): <6>[ 0.000000] LCD: 0x5a000000, 0x0200000 -- if this changes, you don't have the same display as I do.
I/Kernel ( 0): 0
I/Kernel ( 0): <6>[ 0.000000] SYS: 0x43000000, 0x00010000 -- if this changes, You froze @ boot!
I/Kernel ( 0): <6>[ 0.000000] G2D: 0x58000000, 0x01000000 -- if this changes, you don't have the same GFX Hardware as I do.
I/Kernel ( 0): <6>[ 0.000000] VE : 0x44000000, 0x05000000 -- You might not boot...
I/Kernel ( 0): <6>[ 0.000000] VE : 0x49000000, 0x01000000 -- ... Or, you might only lose storage!
-- IF YOU HAVE A SPECIFIC VALUE OR DEVICE TO LOOK UP, TELL ME IN THIS POST --
I'LL BE BACH! To edit and clean up!
........ G2H ~
Code:
[COLOR="gray"]
/*
* 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 features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
Introduction
- Safestrap provides TWRP like recovery capabilities for locked devices.
- This is based on the original work of Hashcode.
Prerequisites for Installation
- You must be on stock firmware:
update-fire-phone-33.4.6.1_user_461013320.bin OR ...461013820.bin <- Please confirm this before proceeding <-
- You must have root access
Known Issues
- Secondary slots do not work at all. Any attempt to flash a secondary slot will result in you having to re-sideload stock 4.6.1
Compatible ROMS
- CM-11 coming soon
Installation
- If not already rooted, use Kingroot from here to obtain root access.
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery
- You should eventually end up in safestrap recovery.
Download
*** Please do NOT create any mirrors ***
- Safestrap for Amazon Fire Phone (Kodiak)
XDA:DevDB Information
Safestrap KK, Device Specific App for the Amazon Fire Phone
Contributors
ggow
Version Information
Status: Beta
Current Beta Version: 4.0.1
Created 2015-07-04
Last Updated 2016-08-17
Reserved
---
- Link is now up
CM-11 progress so far
- Attached is a couple of photos of CM-11 running on Fire phone
Things that are not yet working:
(1) Audio through the speakers
- Music and system sounds through the headphones seems to be working
- This phone uses a TFA9887 audio amplifier chip. Need to figure out a way to enable it. The stock kernel sources don't seem to make any references to it so... must be controlled in userspace.
- In the amazon stock ROM it looks be controlled by two shared libs: libaudio-ExternalSpeakerAmps.so and libaudio-NxpTfa9887.so which are loaded by audio.primary.msm8974.so
- When trying to use the stock audio.primary.msm8974.so I see this in the logs:
Code:
[INDENT]D/audio_hw_primary( 496): select_devices: out_snd_device(2: speaker) in_snd_device(0: )
D/hardware_info( 496): hw_info_append_hw_type : device_name = speaker
D/ACDB-LOADER( 496): ACDB -> send_audio_cal, acdb_id = 53, path = 0
E/ExternalSpeakerAmpControl( 496): Failed to open the speaker amp control (0) at address = 0x34. Error = 108
E/ExternalSpeakerAmpControl( 496): Failed to open the speaker amp control (1) at address = 0x35. Error = 108
D/audio_speaker_platform( 496): Loading speaker use case "music"[/INDENT]
oooooo going to be keeping a very close eye on this thread now.
Update
Progress for today.
- WiFi is working
- Sensors are working
- Baseband seems to be detected correctly - put my sim card in and got a SIM network unlock screen - screenshot attached. I got the phone for nearly next to nothing. But looks like I need it unlocked to use my SIM.
- Bluetooth is working - paired with a keyboard and works good.
- Gapps working
- Front and rear camera not working yet
- Sound, need to figure this out - this is a show stopper at the moment. No Ringing of phone etc
On the amplifier issue did a little digging and other devices like the HTC M7 tend to have a kernel driver which implements an IOCTL interface to userspace but this doesn't seem to the case in the Fire Phone's stock kernel in which I couldn't find any reference to the TFA9887.
I'll have to research a bit more.
I'll do an early preview release at a good point.
Thanks for your hard work.
wonderful ! I just bought fire phone
Thanks for your. Hard.working,I just get my fire phone
Great work! Congrats!
Great work will this also work on the US 4.6.1 software version 461013820.bin. thanks
tintin1892 said:
Great work will this also work on the US 4.6.1 software version 461013820.bin. thanks
Click to expand...
Click to collapse
Should work. If it doesn't, you should be able to boot into the amazon recovery and sideload your stock firmware.
Let me know your results. Once you confirm its working I'll update the OP.
Sent from my Nexus 6 using Tapatalk
Thank you very much, i already installed it and it works fine with the us version 35.4.6.1...461013820, too.
D/audio_hw_primary( 496): select_devices: out_snd_device(2: speaker) in_snd_device(0: )
D/hardware_info( 496): hw_info_append_hw_type : device_name = speaker
D/ACDB-LOADER( 496): ACDB -> send_audio_cal, acdb_id = 53, path = 0
E/ExternalSpeakerAmpControl( 496): Failed to open the speaker amp control (0) at address = 0x34. Error = 108
E/ExternalSpeakerAmpControl( 496): Failed to open the speaker amp control (1) at address = 0x35. Error = 108
D/audio_speaker_platform( 496): Loading speaker use case "music"
Click to expand...
Click to collapse
@ggow
Just making an observation, the external speakers do not depend individually on the stock audio libs (libaudio-ExternalSpeakerAmps.so ; libaudio-NxpTfa9887.so etc..) but might also depend on Dolby frameworks that the stock rom calls.
I want to test it out but i'm having problems with hyper-v atm.
v6ser said:
@ggow
Just making an observation, the external speakers do not depend individually on the stock audio libs (libaudio-ExternalSpeakerAmps.so ; libaudio-NxpTfa9887.so etc..) but might also depend on Dolby frameworks that the stock rom calls.
I want to test it out but i'm having problems with hyper-v atm.
Click to expand...
Click to collapse
Thanks.
I had a brief look at the chain of dependencies. This is all I could find. However I will take a look tomorrow. And let you know what I find
CM-11 Progress update
- Front and rear cameras are now working.
- Google camera and OpenCamera are perfectly fine
- Stock camera app is displaying the preview image upside down.
- Google camera seems to give significantly better photo quality than the stock camera app.
- I will probably remove stock camera app from the build.
Good News
- I have audio on the the speakers... Exactly as I thought- the Tfa9887 is controlled only from the two shared libs I previously mentioned. The fix was to set the correct permissions on /dev/i2c-8 and set a property which indicates audio has been initialized correctly.
- I have a few things to tidy up - like a couple of force closes etc
- Need to do a bit of testing, test video, a couple games etc
- After all of that it should be ready to go.
- I won't have tested make calls, sms and mobile data - so the first release will be a BETA.
EDIT: I should start a [DEV] thread for this so I don't clog up this thread anymore.
ggow said:
- I have audio on the the speakers... Exactly as I thought- the Tfa9887 is controlled only from the two shared libs I previously mentioned. The fix was to set the correct permissions on /dev/i2c-8 and set a property which indicates audio has been initialized correctly.
- I have a few things to tidy up - like a couple of force closes etc
- Need to do a bit of testing, test video, a couple games etc
- After all of that it should be ready to go.
- I won't have tested make calls, sms and mobile data - so the first release will be a BETA.
EDIT: I should start a [DEV] thread for this so I don't clog up this thread anymore.
Click to expand...
Click to collapse
great work as i have a fire phone been hoping something would come out. i have installed safetrap which is working going to install the stock firmware through safestrap. also my fire phone is unlocked to all networks and maybes be able to test it just a thought.
fantastic work
can cm11 be downloaded yet as most my android apps wont work with fire os
wjamie30 said:
great work as i have a fire phone been hoping something would come out. i have installed safetrap which is working going to install the stock firmware through safestrap. also my fire phone is unlocked to all networks and maybes be able to test it just a thought.
Click to expand...
Click to collapse
m4nik10 said:
fantastic work
can cm11 be downloaded yet as most my android apps wont work with fire os
Click to expand...
Click to collapse
- I will be doing a release today
- Netflix and youtube are not working ATM it seems but I can fix that up later.
- Keen to now get it out there to find out if telephony, sms etc is working.
Based on Demetris' LOS 14.1, with :
Android security patch level updates, currently 2020-02-05
tracking LA.BR.1.2.9 from CAF, currently 1.2.9_rb1.44
WIP upstream with linux-stable, currently upgraded from 3.10.49 to 3.10.68 3.10.75
SELinux enabled (better security, SafetyNet & PlayStore should be ok, if not check @tess1 clear caches post )
2018 fixes : MTP, battery consumption, camrecorder crash, wifi, OpenGL ES version, dualsim 6045K (update to MM first), lid & proximity sensor
known problems :
camrecording low brightness
mobile internet connectivity loss and battery drain after a while (days) : toggle airplane mode and back, or reboot
new problems : none known at the moment, but the ROM is not so thoroughly tested before publication
How to investigate and report problems :
sudo adb shell dmesg > dmesg.txt
sudo adb logcat > logcat.txt
sudo adb logcat -b radio > radio.txt
Credits : @FireLord, @Demetris, @Unjustified Dev and all the giants whose shoulders we stand upon !
Source code : Kernel | Device | Vendor trees | Local manifest : View attachment idol3.xml
Changes since previous build : see the build release post
Downloads : lineage-14.1-20200226-UNOFFICIAL-idol3.zip | other releases
Kernel alternative (cam might not work since 20190619 build) : overclocked kernel by @DepressedHedgehog
Reserved
Thanks a lot for sharing this build. Now that the method for restoring our phones to stock has been taken away from us, I'm hoping that more people will jump in and try to solve some of the few remaining issues with this ROM.
Personally I'd like to figure out why the Play Store is installing old versions of certain apps and listing other apps as being incompatible while they can be still sideloaded without any problem. I've found many threads on XDA with people complaining about the same issue but no solution that worked so far. Is this an issue with opengapps, or bad entries in the build.prop? I've compared with the original build.prop from stock 6.0.1 and tried changing values around but no success.
Also battery life seems a lot shorter with Nougat, and there is no way to find out which apps/processes are being power hungry as you have already pointed out.
Issues aside this ROM still makes this phone quite usable and stable compared with other ROM's I have tried so good job and I'm looking forward to testing out new builds.
new thread - we're open for business!
@vknecht once again, thanks for your continued efforts... I tried your Sept 12 release with opengapps Sept. 12 as well - the Play store continues to thwart our efforts in the same manner.
@upyisfar I found that the battery drain during sleep could be reduced to almost nil with the following settings:
- turn off WIFI during sleep - Settings-> WIFI -> Gear Icon -> Keep WIFI on during sleep -> change to....
- turn off Emergency Broadcasts - Settings -> ...More ->Emergency Broadcasts -> Uncheck all
20180918 build : add ptt_socket_app for better wifi and battery
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Code:
09-19 15:14:35.466 1192 1344 E BatteryStatsService: no controller energy info supplied
09-19 15:14:35.748 1192 1212 E BatteryStatsService: power: Missing API
09-19 15:14:35.762 1192 1344 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
Thanks @upyisfar @tess1 for the feedback, keep us posted with your findings...
@vknecht
1. Just tried something... reinstalled 7/18 build where all of the play store program installations were working and then overlayed it with OTA 9/18 which then led to PLay Store blocking installation of many apps ("device isn't compatable" error) - I recall that the build after 7/18 included 25 fixes/commits. Not easy to track it down but could the problem be from one of those fixes/commits?
2. The proximity sensor (tsl2772-ps) error was earlier reported as either missing a driver or needing a shim. Is this a file that can be pulled from Marshmallow and put into this ROM?
Battery updates to follow
vknecht said:
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Click to expand...
Click to collapse
Interesting. How do we know if those changes were merged into the LineageOS's code repo?
vknecht said:
[*]SELinux enabled (helps with safetynet basicIntegrity test ; also better security, but some glitches here and there)
[*]new problems : probably due to SELinux now in "enforce" mode, like battery stats
Click to expand...
Click to collapse
I've installed your new build last night and I've set my kernel to run in permissive mode (Magisk SELinux Manager module) and safetynet basicIntegrity test still passes just so you know. Battery life now feels more comparable to what I get in stock MM. Not sure if this due to SELinux being switched to permissive or the the changes that you have made.
What build environment are you using to build your ROM's, I'm trying to build on Debian stable following your instructions here and keep getting compilation errors.
tess1 said:
@vknecht
1. Just tried something... reinstalled 7/18 build where all of the play store program installations were working and then overlayed it with OTA 9/18 which then led to PLay Store blocking installation of many apps ("device isn't compatable" error) - I recall that the build after 7/18 included 25 fixes/commits. Not easy to track it down but could the problem be from one of those fixes/commits?
Click to expand...
Click to collapse
I thought the 20180905 build ruled out the august kernel updates as the breaker but in fact I should and will retry kernel from july with SELinux enabled ; if it's still not OK then I guess the cause is LOS august update...
tess1 said:
2. The proximity sensor (tsl2772-ps) error was earlier reported as either missing a driver or needing a shim. Is this a file that can be pulled from Marshmallow and put into this ROM?
Click to expand...
Click to collapse
iiuc the hint is that we need either a HAL/framework wrapper OR reuse stock Lollipop driver+shim.
I'm sorry I don't know much about this low-level androidy stuff yet and don't have much time atm to focus on it.
upyisfar said:
Interesting. How do we know if those changes were merged into the LineageOS's code repo?
Click to expand...
Click to collapse
I think if it was in LOS it should appear here : https://github.com/LineageOS/android_system_extras/commits/cm-14.1/ext4_utils
upyisfar said:
I've installed your new build last night and I've set my kernel to run in permissive mode (Magisk SELinux Manager module) and safetynet basicIntegrity test still passes just so you know. Battery life now feels more comparable to what I get in stock MM. Not sure if this due to SELinux being switched to permissive or the the changes that you have made.
What build environment are you using to build your ROM's, I'm trying to build on Debian stable following your instructions here and keep getting compilation errors.
Click to expand...
Click to collapse
I'm using Fedora 28 ; note that you'd have to update the local manifest ($ANDROID_ROOT/.repo/local_manifests/idol3.xml) using given kernel/device/vendor trees as linked in OP, so at the moment it should look like :
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="vknecht/android_device_alcatel_idol3" path="device/alcatel/idol3" remote="github" revision="fix-ptt_socket_app" />
<project name="vknecht/android_kernel_alcatel_msm8916" path="kernel/alcatel/msm8916" remote="github" revision="upstream-lxstable-cafrb144" />
<project name="vknecht/proprietary_vendor_alcatel" path="vendor/alcatel" remote="github" revision="fix-ptt_socket_app" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
</manifest>
(to use july kernel change revision to "upstream-lxstable").
For idol3 build environment setup help, feel free to send me private messages or join #idol3 on Freenode, or maybe even create a thread, for the more we are able to build, the better...
vknecht said:
I thought the 20180905 build ruled out the august kernel updates as the breaker but in fact I should and will retry kernel from july with SELinux enabled ; if it's still not OK then I guess the cause is LOS august update...
iiuc the hint is that we need either a HAL/framework wrapper OR reuse stock Lollipop driver+shim.
I'm sorry I don't know much about this low-level androidy stuff yet and don't have much time atm to focus on it.
Click to expand...
Click to collapse
1 Just tried the 9/05 build --> same play store issue --> August updates maybe problematic
2 Fair enough... I don't know enough but am willing to beta test along the way
It is all in progress...
tess1 said:
1 Just tried the 9/05 build --> same play store issue --> August updates maybe problematic
2 Fair enough... I don't know enough but am willing to beta test along the way
It is all in progress...
Click to expand...
Click to collapse
I've tried the july 3.10.68 kernel (used in 20180718 and 20180905 builds) with current device/vendor trees, and still G compat problems, so it leaves the Android/LineageOS diffs from 2018-06-05 to 2018-08-05 patch levels (afaik there was no 2018-07-05 for LOS 14.1 and there's no 2018-09-05 yet).
20180924 build : 2018-09-05 android security patch level
Only change is Android/LineageOS framework (repo sync) for 2018-09-05 update
Too sad, it doesn't seem to solve the some-apps-in-proeminent-vendor-store incompatibility problem...
@upyisfar : I've wondered about "the method for restoring our phones to stock has been taken away from us", what did you mean ?
While, too bad, the Sugar utility (which had my preference) now fails on a "site not found" error (maybe should try a fresh install, why not in Wine), I still could reset by using the "Panasonic Eluga Switch" utility then the "Mobile Q upgrade" (~1 hour total, with 100Mbs connection) to go back to stock.
lineage-14.1-20180924-UNOFFICIAL-idol3.zip | or OTA zip
Q
vknecht said:
I've wondered about "the method for restoring our phones to stock has been taken away from us", what did you mean ?
While, too bad, the Sugar utility (which had my preference) now fails on a "site not found" error (maybe should try a fresh install, why not in Wine), I still could reset by using the "Panasonic Eluga Switch" utility then the "Mobile Q upgrade" (~1 hour total, with 100Mbs connection) to go back to stock.
Click to expand...
Click to collapse
The Sugar utility was what I was referring to. Haven't had any success with the Mobile Q though, I always get a "check your internet connection" message or something like that. The MM 6.0.1 ROM posted by The Marionette is close enough though. I don't expect Alcatel to push more OTA updates for this device anyway.
I'm sticking with your build of Nougat now that the battery drain issue has gone away. I don't mind manually transfering the APK's from another device to my phone, for now at least. I have managed to set up my build environment (was missing a dependency) and will be producing a test build soon to see if I can fix a thing or two. In the mean time I will happily upgrade to the new build that you have just posted. Thanks!
upyisfar said:
The Sugar utility was what I was referring to. Haven't had any success with the Mobile Q though, I always get a "check your internet connection" message or something like that. The MM 6.0.1 ROM posted by The Marionette is close enough though. I don't expect Alcatel to push more OTA updates for this device anyway.
I'm sticking with your build of Nougat now that the battery drain issue has gone away. I don't mind manually transfering the APK's from another device to my phone, for now at least. I have managed to set up my build environment (was missing a dependency) and will be producing a test build soon to see if I can fix a thing or two. In the mean time I will happily upgrade to the new build that you have just posted. Thanks!
Click to expand...
Click to collapse
@upyisfar
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is an upload link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM987quN6bTYRNWnZuNQSBnCjANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v7MEGSI5-uWsr_t4MZCX3qh1fmCtHzhHptI
I put the phone into download mode and it took about 30 minutes.
---------- Post added at 10:45 PM ---------- Previous post was at 10:39 PM ----------
@vknecht
vknecht said:
This was a complain in the logs, so added it from MM.
There are still batterystats related problems but there's a lead...:
Code:
09-19 15:14:35.466 1192 1344 E BatteryStatsService: no controller energy info supplied
09-19 15:14:35.748 1192 1212 E BatteryStatsService: power: Missing API
09-19 15:14:35.762 1192 1344 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
Thanks @upyisfar @tess1 for the feedback, keep us posted with your findings...
Click to expand...
Click to collapse
re: add ptt_socket_app for better wifi and battery
Would it be possible for you to list the (hopefully few) files and any edited files that you put into this build and the corresponding locations so that I can graft them onto my 7/18 build?
tess1 said:
Just 3 weeks ago, I was able to restore (in Canada) my Idol 3 to stock MM using Mobile Upgrade (I think it was version 5.1.7 as 5.1.8 would not do anything).
Here is an upload link:
5.1.7:
https://mega.nz/#!KmogkYAa!e5y6ZSM987quN6bTYRNWnZuNQSBnCjANMglrhB4rtHo
5.1.8:
https://mega.nz/#!OuhEGaaQ!g6mH6RE7v7MEGSI5-uWsr_t4MZCX3qh1fmCtHzhHptI
I put the phone into download mode and it took about 30 minutes.
Click to expand...
Click to collapse
OK. I was wondering if Alcatel was geo-blocking some countries seeing how some people have success and others don't. I'm in Canada too so I guess that isn't the issue. For now I'm more interested in trying to find a solution to the opengapps compatibility problem.
---------- Post added at 11:04 PM ---------- Previous post was at 10:51 PM ----------
tess1 said:
[MENTION=9435528]
re: add ptt_socket_app for better wifi and battery
Would it be possible for you to list the (hopefully few) files and any edited files that you put into this build and the corresponding locations so that I can graft them onto my 7/18 build?
Click to expand...
Click to collapse
See these commits https://github.com/vknecht/propriet...mmit/f84888778905c179e0d49d7587bc5467248e4b01 and https://github.com/vknecht/android_...mmit/dc64e2c79616e33640a2680451e2fe5ab0152d89
... and the workaround for disabling the bogus 3rd camera mode
https://github.com/vknecht/propriet...mmit/b57afd7960943e0dc8f0c593ae25cb74b5351a3f
6045K / dualsim / multisim
Code:
idol3:/ # setprop ctl.start ril-daemon1
Does it make it better for you too ? (dunno if there's a non-root or GUI equivalent...)
Good news!
I have found the fix for the opengapps store compatibility issue.
I noticed in CPU-z that the reported OpenGL ES version was 1.0 so I added a line to my build.prop:
Code:
ro.opengles.version=196609
And now CPU-z reports version OpenGL ES version 3.1 and all my apps are available for download in the G store.
the value "196609" is decimal for hexadecimal 30001 (OpenGL ES 3.1). Ive seen a commit on github that says support for 3.2 was added but when I change the value to "196610", CPU-z still reports 3.1 not sure why..
vknecht said:
new problems : probablymaybe due to SELinux now in "enforce" mode, like battery stats
Click to expand...
Click to collapse
Appears to be working since the 2 latest builds, with SELinux set to enforce:
[/COLOR]
upyisfar said:
Good news!
I have found the fix for the opengapps store compatibility issue.
I noticed in CPU-z that the reported OpenGL ES version was 1.0 so I added a line to my build.prop:
Code:
ro.opengles.version=196609
And now CPU-z reports version OpenGL ES version 3.1 and all my apps are available for download in the G store.
the value "196609" is decimal for hexadecimal 30001 (OpenGL ES 3.1). Ive seen a commit on github that says support for 3.2 was added but when I change the value to "196610", CPU-z still reports 3.1 not sure why..
Click to expand...
Click to collapse
SECONDED - Confirmed fixed! and the Play Store also reports that my Device is Certified under Play Protect Certification.
Thank you upyisfar
vknecht said:
Code:
idol3:/ # setprop ctl.start ril-daemon1
Does it make it better for you too ? (dunno if there's a non-root or GUI equivalent...)
Click to expand...
Click to collapse
6045I single-sim here, can't test this, sorry.
BTW can you add "low brightness in camera video capture mode" to list of known issues in the op? thx
I have been trying to install v4a presets on my Oneplus but I cant seem to get them to work. I tried a method from another post on here which said to just make a presets folder (/internalstorage/viper4android/presets) and to copy the xml files into there, but then v4a didn't recognize them.
I also installed a folder of like 1600 presets from here too and looking through them I noticed they all have similar names like "headset.xml" or "bt_a2dp.xml" so I was wondering if that has a meaning or if I can change them since I want multiple files from the collection.
I am running lineage o and I am rooted on my oneplus 7t.
Needs to be selinux permissive for V4A to work
HueyT said:
Needs to be selinux permissive for V4A to work
Click to expand...
Click to collapse
Uhm can you elaborate
Use selinuxchanger.apk to switch to permissive and then V4A will work
Releases · MrBIMC/SELinuxModeChanger
Simple android app that sets SELinux into desired mode on each boot. I opensourced it because google banned such apps from Google Play. Licence is GPLv3. Enjoy! - MrBIMC/SELinuxModeChanger
github.com
HueyT said:
Use selinuxchanger.apk to switch to permissive and then V4A will work
Click to expand...
Click to collapse
Thanks for the suggestion, but I looked into it and apparently the version I'm using works with enforcing mode on. Also my problem was just with the presets which I managed to fix by just reinstalling the magisk module while keeping my presets folder in the v4a folder.
I still have not figured out what the filenames mean but I think it's just the type of output device while the folder gives it the name.
Still don't really know what SELinux is so I'm going to keep that on default for now. Seems to be a security protocol so I don't know if I want to turn that of.
Anyway thanks again for your help
Hey man maybe you can help me
I need a magisk flashable batch script for changing / replacing a value in many xml files per batch i wont to help the guys from viper4android maybe you know the tool following operations : open file - jump to row / string - read value - calculate new value - write value - save file - jump to next xml and so on.
Description : The values for surround section changed from 120 - 0 130 - 1 140 - 2 150 -3 160 - 4 170 -5 and so on until 8 old values : 120- 200 new values 0- 8
Maybe you can help me with this many people would be happy to solve the wrong conversion issue of viper4 Android presets or maybevyou know somebody