Related
youAdb is a very convenient tool for you android device which allows you to do various actions by just a couple of clicks.
Some features:
- SD-Partition-Manager (FAT32, EXT2/3/5, Linux Swap etc.!)
- App Manager (FULL BACKUP function!)
- File Manager (Push, Pull, Delete folders/files...)
- Reboot, Reboot Recovery, Adb Remount...
- View and automatically SAVE LOGS
- custom adb commands (like a shell)
- Install recovery images!
- Shows device's state and Serial Number
In contrast to most other android tools this tool is stable, leightweight (less than 1MB!) and easy to set up!
Watch a video tour: http://www.screentoaster.com/watch/stU0xUQ0VLQ1tZQl9UWVtf (ya, i know, my mic sucks.)
Screenshots:
DOWNLOAD: youadb.4shared.com
Nicely done.
It works great on my G1. I've not tested the partitioning section yet, but everything else works fine!
good job!
I keep getting ADB server is out of date
idbl_fanatic said:
I keep getting ADB server is out of date
Click to expand...
Click to collapse
..but you don't get this if you manually use adb via cmd?
try using sdk 1.6 and android 1.6
Works great on my G1.
A few suggestions:
Apps window, make the sections scalable because some app names are larger than the widow size.
Push/Pull window, allow double click to open the folder instad of having to go to enter to open it.
Reorder list by name
evilkorn said:
Apps window, make the sections scalable because some app names are larger than the widow size.
Click to expand...
Click to collapse
actually i'm reworking the whole gui right now to be fully scalable!
Push/Pull window, allow double click to open the folder instad of having to go to enter to open it.
Reorder list by name
Click to expand...
Click to collapse
ok i'm gonna do that too. good ideas.
fabsn said:
..but you don't get this if you manually use adb via cmd?
try using sdk 1.6 and android 1.6
Click to expand...
Click to collapse
I am such a noob for android, where would I get this?
Pretty cool, man. Good job on this!
idbl_fanatic said:
I am such a noob for android, where would I get this?
Click to expand...
Click to collapse
Get the sdk here:
http://developer.android.com/sdk/1.6_r1/index.html
(the adb file your looking for is in the tools directory)
i also recommend using the latest version of android (have a look at the development secion of the board) because i'm developing the software using a android 1.6 (donut) phone.
Pretty cool, man. Good job on this!
Click to expand...
Click to collapse
Thanks.
fabsn said:
Get the sdk here:
http://developer.android.com/sdk/1.6_r1/index.html
(the adb file your looking for is in the tools directory)
i also recommend using the latest version of android (have a look at the development secion of the board) because i'm developing the software using a android 1.6 (donut) phone.
Thanks.
Click to expand...
Click to collapse
My bad, I didn't have my phone in debugger mode.
New release. Build 01711.
Changelog:
-Scalable gui. you can adjust the fileviewers size to the size you want. very useful, especially if there are many long filenames.
as requested by evilkron.
get it here:
youadb.4shared.com
Nice changes
But one problem: The push/pull tab gets stuck and won't go back in folders after going a few folders deep and won't go back with the ...
I noticed that too. I'm gonna fix that right away...
---
fixed.
build 01711b
changelog: fixed filebrowser's "..." (go back) button.
download: youadb.4shared.com
Its working great on my G1, at least the first version, just dl'ed the new edition. Great job on this...keep up the awesome work.
Any feature requests?
I need something to work on
Question. I ran Google app backup.
Where does it backup too?
kizer said:
Where does it backup too?
Click to expand...
Click to collapse
I have no idea (i dont use it) and i dont understand how this question is connected with this thread.
great app clean and simple to use, keep up the great work
Joe333x said:
great app clean and simple to use
Click to expand...
Click to collapse
i really appreciate this comment as thats exactly what this app is supposed to be: fast, easy and functional.
there might be some other tools which have more functions (which i'm going to implement too) but they're not as fast and stable as mine is / will be!
NEW RELEASE: build 02111
changelog:
-push/pull file function updated
-MAJOR speed and stability improvements: app starts in less than 1sec and uses multitasking so that it will stay stable and is faster (especially when pushing files or searching fo .apks on ur computer!)
Download: youadb.4shared.com
________________________
NEW release: build 02211
changelog:
- added remount button
- slight ui changes
- fixed assemblyinformation
- improved "custom adb command" dialog
edit: fixed 1 more bug (you dont have to manually refresh the device stat to use the partitioning tool anymore)
=> build 02211b
Download: youadb.4shared.com
Hi All
Today I found a combination (which might have been out there for a while) how the Camera actually is working for Topaz Android
1. Download the FRX04 version
2. http://forum.xda-developers.com/showthread.php?t=883966 check there for section "Topaz Users"
3. Don't forget the post "[23/01/2011] :" to dissable 2 rows in froyo.conf file
The Camera was able to startup and I took one Picture
The speed of the Cam.. well.. don't be to happy.. but it is working anyway
/olme
Yeah,works fine, but only 3 MP and without auto-focus,but it works more quick than im windows mobile.
Oh,but programm(name forgotten) in FRX04 for Rhodium(23.01.11) is more usable,you can make photo by pressing on volume keys
yes indeed WinMo is quicker.. but one step at the time This is the first time I ever on my Topaz and Android was able to even see that it was "connected" and that I could take a picture.
The next development will be that the rest of the goodies will appear such as speed and autofocus etc etc..
GOOD job Android Devs!
/olme
Please, keep in mind that it's in debug state, a branch of XDAndroid code made by viruscrazy.
If you want to help test it, follow the instructions in the first post and leave your logs there.
Thanks.
Somebody tested camera on FRX04(23.01.11)?
saneksem said:
Somebody tested camera on FRX04(23.01.11)?
Click to expand...
Click to collapse
yes with provided topaz test kernel it's working till 3mp pictures
@5mp camera crashed... but this is allready known and developer asked for dmesg log files to finetune the driver...
-bl4ckb1rd
p.s. camera driver did not work with latest 01253 kernel
can any1 pls upload the conf file? because i couldn't find the 2 rows......
[23/01/2011] :
Updated Lib_package to fix the froyo.user.conf file (thanks to arrrghhh again, you're the "conf file" specialist) and the Blackstone picture crash (I hope...). If you are using latest FRX04 build and rootfs, you may have to disable the two following lines (add a "#" at the begginnning of the line) :
Code:
mount --bind /sdcard/lib_camera/libGLES_qcom.so /system/lib/egl/libGLES_qcom.so
mount --bind /sdcard/lib_camera/gralloc.msm7k.so /system/lib/hw/gralloc.msm7k.so
Could DEVs add camera to Gingerbread?
There is a new fix for 5MP. It works. You need the Kernel from 28.01.11 and the new attached Haret Version. Do not use the attached kernels and don't forget to write the line:
set INITRD_OFFSET 0x608000
under "set initrd initrd.gz" (Startup.txt)
http://forum.xda-developers.com/showthread.php?t=883966
CameraWorks
Erikson89 said:
There is a new fix for 5MP. It works. You need the Kernel from 28.01.11 and the new attached Haret Version. Do not use the attached kernels and don't forget to write the line:
set INITRD_OFFSET 0x608000
under "set initrd initrd.gz" (Startup.txt)
http://forum.xda-developers.com/showthread.php?t=883966
Click to expand...
Click to collapse
I also confirm it works
Here it doesn't. New haret makes the topaz reboot in winmo...
Well, it doesn't seem to work with Froyo X...
What doesn't seems to work?
The Camera is working but as the forum said.. only stable up to 3Mpixels...
olme said:
Hi All
Today I found a combination (which might have been out there for a while) how the Camera actually is working for Topaz Android
1. Download the FRX04 version
2. http://forum.xda-developers.com/showthread.php?t=883966 check there for section "Topaz Users"
3. Don't forget the post "[23/01/2011] :" to dissable 2 rows in froyo.conf file
The Camera was able to startup and I took one Picture
The speed of the Cam.. well.. don't be to happy.. but it is working anyway
/olme
Click to expand...
Click to collapse
Place a files hire!
Brain-brick with your link
sorry I don't understand what you want me to do..
Do you want me to place a link to my files I used to get the Camera running or what?
cheers
/Olme
olme said:
sorry I don't understand what you want me to do..
Do you want me to place a link to my files I used to get the Camera running or what?
cheers
/Olme
Click to expand...
Click to collapse
Yes! Yes and Yes!
check this link where I have uploaded my andboot.
1. Download it and extraxt it anywhere
2. put the 2 folders on the root of your SD Card.
3. Start Haret.exe
hotfile .com /dl/101065742/b00ae64/andboot.rar.html
Thanks for you effort uploading the file
I think someone needs to thank you also , but i think he's "cooking" right now
olme said:
check this link where I have uploaded my andboot.
1. Download it and extraxt it anywhere
2. put the 2 folders on the root of your SD Card.
3. Start Haret.exe
hotfile .com /dl/101065742/b00ae64/andboot.rar.html
Click to expand...
Click to collapse
wow
thx, cam is working for me, but only up to 2 Mpix,
but in this version wifi error after reconnect... :-(
yes i think cooking can be started ;-)
Ok, so I brought this up as a comment in the epic ROM by the good people at Einherjar, Trigger Redux, but it should also work for any version of CM7 and since I figured a lot of people might want CM7 to be compatible with the FFC mod for the Vibrant, I decided to make a brand new thread for it.
I owe this fix to the good people who worked on the various Q&A and FAQs for Vibrant CM7. The issue regarding the fact that some versions of CM7 do not support the Vibrant FFC Mod lies in the /system/lib/libcamera.so file. Since the Vibrant does not have a FFC normally, it will present only the 4 options on the camera app that should pertain to your phone, and consequently even if you do have a FFC, neither the camera nor any mirror or video calling app will work right out of the box.
The fix? Using Root explorer (or something similar), replace the current /system/lib/libcamera.so file with the one provided here, change the permissions on the libcamera.so file so they match all the other .so files in the same folder, and reboot. Problem solved.
NOTE: Due to a very helpful favor from scrizz, this tweak is now available as a CwM flashable .zip! However, the .zip only contains the libcamera.so file. If you want to change out ALL the .so files regarding the camera, they have been uploaded. (changing out all the .so files is recommended, since they may prevent unknown bugs from occurring in the future).
This tweak will allow the camera to have 5 of the 6 options (the only one missing will be for flash). Video calls and all mirror apps should now work.
This tweak does not harm any other functions of the phone, it just enables FFC support should someone happen to have an FFC on your Vibrant.
BUGS:
~When you use the FFC in the main camera app for some reason, it will make you look fat when rotated horizontally and will make you look skinny when rotated vertically. Pictures and video will look normal, however.
~This fix does have the old "image is rotated 90 degrees" bug . However, while YOU will see yourself rotated 90 degrees, the PERSON YOU ARE CALLING will see you normally, and all pictures and videos you view will look normal. The image in the main camera app, however, is mirrored, but not rotated .
I tried changing every "SGH-T959" and "vibrantmtd" in the build.prop to "GT-I9000" but that didn't work. Turns out this time, the bug is back with a vengeance. Either way, while it is mildly annoying, it causes no practical malfunction.
~When in video mode for the FFC, you will not be able to zoom in the normal camera app.
P.S. The complete set of all .so files pertaining to the camera do NOT come as a CwM flashable .zip. You have to extract the file on your computer and then manually replace the file. I'm just throwing my two cents in here so that people wont have to dig thru Q&A sections. However, if anyone wouldn't mind giving me a crash course in how to make this a flashable .zip for everyone, do not hesitate to PM me. I would be happy to help and the lesson would be much appreciated.
Additionally, be aware that if you use this tweak and you do NOT have an FFC, the camera will still work under normal circumstances, but if you switch to the "Front" function, the camera will freak out and force close every time you try to open it.
To fix this problem should you encounter it, simply go to Settings>Applications>Manage Applications>Camera and click "clear data."
IDK if this works with MIUI. If you'd like to be a tester for it, do not hesitate to PM me with the results!
If the rotation thing every got fixed I would flash cm7/miui in a heartbeat
Follow me on twitter @Hometowns_Hero
Is this any different than the i9000 lib file? I currently have 4 libcam files pulled directly from an i9000 rom, but the only difference for me is that on Tango vchat I see myself rotated 90 degrees, but so does the other person. You're insisting that they'll see me normally?
yea were are these lib files from? i pulled a libcamera.so and miuicamera.apk from the latest I9000 rom and got the FFC to work on my vibrant with the same bugs as the ones listed
ultrav.icious said:
yea were are these lib files from? i pulled a libcamera.so and miuicamera.apk from the latest I9000 rom and got the FFC to work on my vibrant with the same bugs as the ones listed
Click to expand...
Click to collapse
They're from the AOSP i9000 2.3 ROM (the i9000 CM7). Also, an alternative method of pushing this libcamera.so is by doing this in terminal (or, I assume, adb).
Code:
su
mount -o rw,remount /system
cp /sdcard/libcamera.so /system/lib/
reboot
made it into CWM flashable zip.
LMK if it works.
Jus tested the flashable .zip and everything works as expected.
dglowen23 said:
Jus tested the flashable .zip and everything works as expected.
Click to expand...
Click to collapse
So the rotation problem is fixed?
Follow me on twitter @Hometowns_Hero
dglowen23 said:
Jus tested the flashable .zip and everything works as expected.
Click to expand...
Click to collapse
thanks!
10char
Joy2DaWurld said:
Is this any different than the i9000 lib file? I currently have 4 libcam files pulled directly from an i9000 rom, but the only difference for me is that on Tango vchat I see myself rotated 90 degrees, but so does the other person. You're insisting that they'll see me normally?
Click to expand...
Click to collapse
Exactly! This lib file is the same one from the i9000 version of CM7.
Regarding the vchat 90 degrees bug, yes, I am INSISTING that the other person should see you normally, but I did test it only on Qik as Tango wouldn't work for me for some reason. If you use Qik the other person WILL see you normally.
Try replacing all 4 of the lib files that pertain to the camera with the ones that you have from the i9000 version of CM7. I did, but it didn't make any difference to me. However, since I was unable to try Tango, Vignette or ooVoo, I would recommend you try it.
Anyone else who wants the remaining 3 lib files can get them here.
scrizz said:
made it into CWM flashable zip.
LMK if it works.
Click to expand...
Click to collapse
I'll add it in the OP. LMK if you want it removed for some reason. Thanks man! For future reference, where can I learn how to make a CwM flashable .zip like that?
Will that zip work for miui?
Edit:I confirm it works for miui =]
follow me on twitter @Hometowns_Hero
ChoctawT said:
Will that zip work for miui?
Edit:I confirm it works for miui =]
follow me on twitter @Hometowns_Hero
Click to expand...
Click to collapse
Did it work the camera.apk or with miuicamera.apk?
rbtady said:
Did it work the camera.apk or with miuicamera.apk?
Click to expand...
Click to collapse
Miuicamera
Sent from my T959 using XDA Premium App
On Skype the person sees me rotated
Is banding still present on v1 cameras?
Is banding still present on v1 cameras on CM7?
d33dvb said:
Is banding still present on v1 cameras on CM7?
Click to expand...
Click to collapse
doesn't matter what rom you use, V1 cams will have banding.
i figured out the rotated FFC video chat problem with vibrants. we need an i9000 build.prop for our cameras not to show rotated, tested with tango works perfectly now!
Respect!
I don't think you get the credit you deserve for being so awesome!
scrizz said:
made it into CWM flashable zip.
LMK if it works.
Click to expand...
Click to collapse
lookitzjohnny said:
i figured out the rotated FFC video chat problem with vibrants. we need an i9000 build.prop for our cameras not to show rotated, tested with tango works perfectly now!
Click to expand...
Click to collapse
im also using tango and i have the rotated view, can i ask you what is the exact (looking at this thread) file to flash?
Use everything here on your own risk and hit THANKS BUTTON if you like my work!
General Information:
As you propably know, till now there is no CRT-off MOD out for the S3. This is because only changing the value of config_animateScreenLights from true to false in framework-res.apk is not working anymore!
Together with Tungstwenty and rovo89 we faced out, that the problem are some missing commands in the /system/framework/services.jar
After comparing files from S2 and S3 Tungstwenty could help me to find the right position to edit files and with a litte bit of testing we found the right commands to enable the CRT-off-effect!
Click to expand...
Click to collapse
Tungstwenty said:
Let me clarify what is required in order to have the CRT effects working:
A patched library that properly (i.e. no flicker, etc.) provides the effects --> see attached flashable zip's or use Tweakbox
Code changes on the ROM in order to properly trigger the effect(s), which the library will then respond to those triggers --> look at the how-to or use Tweakbox
Item no. 1 is the one that I worked on and for which a fully working library was now provided.
The 2nd part can be done in 2 different ways - either patching the S3's ROM to properly enable the CRT-On and/or CRT-Off effects, OR do some hooking on the existing methods in the ROM and without changing that code, override the flags (i.e., the way Tweakbox does it).
It's this 2nd aspect that you guys need to address somehow. I worked with rovo89 on Tweakbox and not only does it bundle with the library, it also does the code changes in memory to make it work (topic no. 2).
But sphinx02 had already provided that, initially, after some discussion on what needed to be patched on the S3 ROM.
So, in order to have it working you have 2 ways:
Either use Tweakbox and make use of its configuration options to enable only CRT-Off, only CRT-On, or whatever you fancy.
Ask for someone (such as sphinx02) that has an S3, to keep up with existing ROMs (it will need to be changed separately for every one), and provide patched apk's on top of the existing ones so that it enables the effect triggers I mentioned. This will also need to take into account whether you prefer both effects on, only CRT-Off, etc.
I hope this is a bit more clear now, if not just let me know.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
HOW-TO make the Code Changes:
This is what have to be done:
First of all decompile classes of services.jar (I won't provide any information to this, there are many tutorials out there how to use the smali tools!)
Than in com/android/server/PowerManagerService.smali we have to make the method nativeStartSurfaceFlingerAnimation(I)V callable from inner classes. To do that, we have to add the following after the last access$XXXX method:
Code:
.method static synthetic access$9000(Lcom/android/server/PowerManagerService;I)V
.registers 2
.parameter "x0"
.parameter "x1"
.prologue
.line 110
invoke-direct {p0, p1}, Lcom/android/server/PowerManagerService;->nativeStartSurfaceFlingerAnimation(I)V
return-void
.end method
Than we have to add some commands to the file com/android/server/PowerManagerService$BrightnessState.smali to trigger the CRT-off-effect. For that add the red part between :cond_38 and iget-object v4, p0, Lcom/a.... like this (its around line 400 in code):
Code:
.line 2679
.restart local v3 #turningOff:Z
:cond_38
[COLOR="Red"] iget-object v4, p0, Lcom/android/server/PowerManagerService$BrightnessState;->this$0:Lcom/android/server/PowerManagerService;
const/16 v3, 0x11 # CRT-On and CRT-Off
#calls: Lcom/android/server/PowerManagerService;->nativeStartSurfaceFlingerAnimation(I)
invoke-static {v4, v3}, Lcom/android/server/PowerManagerService;->access$9000(Lcom/android/server/PowerManagerService;I)V[/COLOR]
iget-object v4, p0, Lcom/android/server/PowerManagerService$BrightnessState;->this$0:Lcom/android/server/PowerManagerService;
#getter for: Lcom/android/server/PowerManagerService;->mScreenBrightness:Lcom/android/server/PowerManagerService$BrightnessState;
invoke-static {v4}, Lcom/android/server/PowerManagerService;->access$6000(Lcom/android/server/PowerManagerService;)Lcom/android/server/PowerManagerService$BrightnessState;
move-result-object v4
If you want to have only CRT-OFF, you can replace
Code:
const/16 v3, 0x11 # CRT-On and CRT-Off
with this:
Code:
const/16 v3, 0x10 # CRT-Off only
Finally recompile the file, put it on your phone and you can see the CRT-Off effect on your S3!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Avoid flickers, enable CRT-ON in lib-file:
Tungstwenty said:
Hi,
I worked on the porting of the patch to S3 and despite not having one myself, I'm pretty confident that the binary rovo89 and myself included in the latest Tweakbox should work on an S3.
Could any of you guys try it out?
What to do:
Install the newest Xposed framework from here. Open the Installer app, press Install/Update and reboot.
Install the Tweakbox mod from here. Open it and enable the CRT effects in the appropriate section. You can also enable any other tweaks you like, to check if they also work for the S3 (most of them should)
Go back to the Xposed Installer app, activate the Tweakbox mod (2nd tab), then in the libraries section select "libsurfaceflinger.so" and use the I9300 version. Tick the "Replace in test-mode only" option and back in the 1st tab do a soft / test reboot.
If everything goes well and the effects work as expected, you can go back to the installer app and untick "test-mode only" so the lib is overridden on every boot.
Note that except for the app_process system file which is installed by the framework (creating a backup file, and which should have no practical effects until any mods are enabled later), all other replacements such as the surfaceflinger lib do not change anything in /system but are rather performed by loading the files from an alternate path.
I'd appreciate your feed back especially for the CRT effect, but also the other existing Tweakbox options.
Thanks!
Click to expand...
Click to collapse
Or use in addition to the changes in services.jar the attached flashable zip's to overwrite libsurfaceflinger.so with the corrected one by Tungstwenty or me, XXAL for (XXALE8,XXALF2,XXALF6) and XXBL for (XXBLFB,XXBLG1,...)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Notes:
- This is a development thread so please discuss only things that interest for further development
- First part of the development has been discussed in this Thread of S2-forums
- As on the S2 after the CRT-off-effect sometimes the screen flickers --> fixed by Tungstwenty
- For some reason, it works without setting config_animateScreenLights from true to false in framework-res.apk
- I hope Tungstwenty and rovo89 can help us again to edit the libsurfaceflinger.so to avoid that it flickers after the CRT-off-effect
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Testing the effect:
I have made the changes for ODEXED and DEODEXED XXALF2 ROM, if you want to test it have a look at my thread in the themeing/modding forums:
[MOD][ALF2/ALF6/BLFB][ODEX/DEODEX] 1% BatMod + ExtPowMen + CRT-OFF-ON or CRT-OFF-ONLY
Please post development-unrelated stuff there!!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Credits:
Credits are going out to Tungstwenty and rovo89 for their excellent work on the S2 and for their help/advice on the S3! Excellent developers!
I hope you guys will help us again to fix the libs and perhaps enabling CRT-on-effect aswell!!!
Thank you for helping us again!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
reserved for future use, just in case..
Nice one!
Sent from my GT-I9300 using xda premium
sphinx02 said:
- I hope Tungstwenty and rovo89 can help us again to edit the libsurfaceflinger.so to avoid that it flickers after the CRT-off-effect
Click to expand...
Click to collapse
The flicker issue and the lack of CRT-On effect are *exactly* the same issues that are present on the S2 lib as well.
It has been fixed there, but changing ARM code without the sources is a very tedious process and that requires a fair amount of testing till it eventually works.
Without having access to an S3 it's very hard to do this or even explain what needs to be done
On top of that, I have other pending stuff I need to work on so you shouldn't expect a fix very soon, sorry.
Tungstwenty said:
The flicker issue and the lack of CRT-On effect are *exactly* the same issues that are present on the S2 lib as well.
It has been fixed there, but changing ARM code without the sources is a very tedious process and that requires a fair amount of testing till it eventually works.
Without having access to an S3 it's very hard to do this or even explain what needs to be done
On top of that, I have other pending stuff I need to work on so you shouldn't expect a fix very soon, sorry.
Click to expand...
Click to collapse
Ok, I see the problematic.. But perhaps you can give me the original and the modified files from the s2 so I can compare the 2 files and perhaps see by myself what is changed! And as I never changed anything in .so files perhaps you can tell me additionally how you have edited them!
I'm willing to try around again and to play with bytecode or so on, but I think I need a little input from you!
You mentioned the tool objdump, so I think I have to become familiar with this tool, am I right?
sphinx02 said:
Ok, I see the problematic.. But perhaps you can give me the original and the modified files from the s2 so I can compare the 2 files and perhaps see by myself what is changed! And as I never changed anything in .so files perhaps you can tell me additionally how you have edited them!
I'm willing to try around again and to play with bytecode or so on, but I think I need a little input from you!
Click to expand...
Click to collapse
Ok then, I'll give you the starting pointers so you can have a look at what lies ahead
The S2 patched file with ON and OFF both working correctly, with no flickers, is in this post.
The S2 original file is attached here.
Do a binary compare to see the changed bytes and their offsets.
To have a look at the code, you need to have the NDK installed.
Run "objdump -x libsurfaceflinger.so" to see the decompiled ARM code.
And have fun trying to understand that
Tungstwenty said:
Ok then, I'll give you the starting pointers so you can have a look at what lies ahead
The S2 patched file with ON and OFF both working correctly, with no flickers, is in this post.
The S2 original file is attached here.
Do a binary compare to see the changed bytes and their offsets.
To have a look at the code, you need to have the NDK installed.
Run "objdump -x libsurfaceflinger.so" to see the decompiled ARM code.
And have fun trying to understand that
Click to expand...
Click to collapse
Ok, thank you for that.. I dont know at this point if I ever will have success with it but I will give it a try as I have the time to! Thank you very much again Tungstwenty for your tips/advice!
While trying around a little bit and thinking about the problem, I had the following idea:
Is it not possible to build an own, additional library file with the crt-off functions? Sources for that are out there! Just copy together and build an .so file. Than in the Java-Code we are including this new native code and simply calling the function from this new / additional lib-file? What do you think about that?
Looks like someone needs to do this again...
http://forum.xda-developers.com/showthread.php?t=1676378
The flicker bug is just a bit annoying
Edits
Lol sorry just seen the post a couple above mine. Hope you guys can fix it. Good luck.
Sent from my GT-I9300 using XDA Premium HD app
sphinx02 said:
While trying around a little bit and thinking about the problem, I had the following idea:
Is it not possible to build an own, additional library file with the crt-off functions? Sources for that are out there! Just copy together and build an .so file. Than in the Java-Code we are including this new native code and simply calling the function from this new / additional lib-file? What do you think about that?
Click to expand...
Click to collapse
I don't think that's a viable option. rovo already tried that with existing sources, I think, and the resulting library did not work on sammy's rom.
As for creating a separate library with only those functions, I also don't think that's possible as everything related with screen rendering (state, buffers, etc.) is on this lib and therefore a separate one would not have any of that info.
Hi,
I worked on the porting of the patch to S3 and despite not having one myself, I'm pretty confident that the binary rovo89 and myself included in the latest Tweakbox should work on an S3.
Could any of you guys try it out?
What to do:
Install the newest Xposed framework from here. Open the Installer app, press Install/Update and reboot.
Install the Tweakbox mod from here. Open it and enable the CRT effects in the appropriate section. You can also enable any other tweaks you like, to check if they also work for the S3 (most of them should)
Go back to the Xposed Installer app, activate the Tweakbox mod (2nd tab), then in the libraries section select "libsurfaceflinger.so" and use the I9300 version. Tick the "Replace in test-mode only" option and back in the 1st tab do a soft / test reboot.
If everything goes well and the effects work as expected, you can go back to the installer app and untick "test-mode only" so the lib is overridden on every boot.
Note that except for the app_process system file which is installed by the framework (creating a backup file, and which should have no practical effects until any mods are enabled later), all other replacements such as the surfaceflinger lib do not change anything in /system but are rather performed by loading the files from an alternate path.
I'd appreciate your feed back especially for the CRT effect, but also the other existing Tweakbox options.
Thanks!
Now I try, thank you..
And CRT on is possible?
failax said:
Now I try, thank you..
And CRT on is possible?
Click to expand...
Click to collapse
Yes. If everything is working as I expect, the new things vs your current situation are:
- No more flickering issues when CRT-Off
- Now also includes CRT-On
- Can detect device orientation and do a "vertical" CRT effect instead of horizontal
All these are optional and can be turned on/off in the Tweakbox preferences.
I tried.
CRT OFF has the same problem, CRT On is not visible, but I had to place also a jar file?
---------- Post added at 12:01 PM ---------- Previous post was at 11:50 AM ----------
I must add that I'm on checkromevo hd and I've already inserted a mod to see crt off, I don't know if this can help.
Other mods in tweakbox work.
failax said:
CRT OFF has the same problem, CRT On is not visible, but I had to place also a jar file?
Click to expand...
Click to collapse
Mmm, did you follow the steps I mentioned before, i.e. enabling the lib replacement in test mode and doing a soft reboot?
You should end up with a library on /vendor/lib (ramfs) and it should get loaded on startup instead of the one in /system/lib. Can you check with a file browser if the file under /vendor/lib does exist?
Also, could you open a terminal, run "set" and check if LD_LIBRARY_PATH is "/vendor/lib:/system/lib", as in S2?
Tungstwenty said:
Mmm, did you follow the steps I mentioned before, i.e. enabling the lib replacement in test mode and doing a soft reboot?
You should end up with a library on /vendor/lib (ramfs) and it should get loaded on startup instead of the one in /system/lib. Can you check with a file browser if the file under /vendor/lib does exist?
Also, could you open a terminal, run "set" and check if LD_LIBRARY_PATH is "/vendor/lib:/system/lib", as in S2?
Click to expand...
Click to collapse
I've rebooted totally, what do you mean for soft reboot?
Now I try to see those files..
EDIT:
under vendor/lib I see 2 things, I see a folder called DRM and inside libdrmwvplugin.so, and single file called libwvm.so.
Also, could you open a terminal, run "set" and check if LD_LIBRARY_PATH ?
Yes it's there.
failax said:
I've rebooted totally, what do you mean for soft reboot?
Now I try to see those files..
EDIT:
under vendor/lib I see 2 things, I see a folder called DRM and inside libdrmwvplugin.so, and single file called libwvm.so.
Click to expand...
Click to collapse
Can you open the Xposed Installer app and post a screenshot of each of the 3 tabs? "Framework", "Modules" and "Libraries" (in this last one, scroll to the bottom to display the "libsurfaceflinger.so" entry so it's visible in the picture)
Can you send me the modded libsurfaceflinger.so so I can test it directly?
Maybe a downloadlink via pm...
I have sphinx mod for CRT, so If I deselect CRT off on tweakbox, it is shown the same.
sphinx02 said:
Can you send me the modded libsurfaceflinger.so so I can test it directly?
Maybe a downloadlink via pm...
Click to expand...
Click to collapse
Would you mind just taking it from the Tweakbox package, and in the process also checking if the on-the-fly replacement is working for you?
---------- Post added at 12:03 PM ---------- Previous post was at 12:01 PM ----------
failax said:
I have sphinx mod for CRT, so If I deselect CRT off on tweakbox, it is shown the same.
Click to expand...
Click to collapse
Your lib settings are ok, so if you do a soft reboot (pressing the button on the app), it should come back with a libsurfaceflinger.so file in /vendor/lib. It's won't happen, though, if you do a "normal" reboot.
It isn't happening to you? Could it be that the soft reboot tries to load the new lib, fails, and immediately does a hard/normal reboot - did you notice anything that could point to this?
Disclaimer :
Code:
I am not responsible for any damage to your device!
Use this mod at your own risk!
What's this?
This mod increases the audio bitrate on video recording from a disgraceful 96kbps to a respectable 320kbps. Thus, giving a richer, more pleasing audio quality.
Still confused? Click here for a better explanation
Requirements :
- A rooted phone with magisk installed
- An opened mind (important!)
Contributors :
@Jt380p
@Slim K
* NOTES * (READ) :
- Not all ROMs are compatible with this mod, you might end up in a bootloop. YOU HAVE BEEN WARNED!
Download :
https://drive.google.com/file/d/1wr-p7puOL8nYb1wj1AyVbh9XmMp5kRKI/view?usp=sharing (Flash with magisk manager)
Source :
https://forum.xda-developers.com/Mi-9/themes/magisk-audio-bitrate-increase-t3927810
Audio files provided by @Slim K
Thanks to :
@Slim K
@topjohnwu for Magisk
Created : 7/11/2020
Last updated : 7/11/2020
reserved
Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:
Slim K said:
Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:
Click to expand...
Click to collapse
For me it works on Stock, but not on Urnyx05 GCam. Thanks Dev.
Lineage android 11 will benefit from it, or that is already implemented in them?
So which ROMs are not compatible?
Aki-to said:
So which ROMs are not compatible?
Click to expand...
Click to collapse
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.
Slim K said:
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.
Click to expand...
Click to collapse
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
This mod is also so extremely tiny, you could pretty much make these changes manually. Just take care of permissions and replace the file, that's it. It's even less complicated than working with /etc/fstab, it seems.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.
Aki-to said:
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
Click to expand...
Click to collapse
You assume correctly. The path to the functions can be usually found in /data/adb/magisk/util_functions.sh on your device.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.
Click to expand...
Click to collapse
Why write code twice when it already exists and works for everyone.
Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.
nike1973 said:
Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.
Click to expand...
Click to collapse
Yes it works
Thank you. Works on MIUI EU 12.0.6.
Eu 12.0.6, super stabilization (on stock camera) crashes when module is active.
I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!
Anyone tried on Xiaomi.eu rom?
Running 12.0.8.
Hi!
gkhnkaanyrtc said:
I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!
View attachment 5272691View attachment 5272693
Click to expand...
Click to collapse
Hi! I have the same problem ... Did you fix it? I use Miui 12.0.1 with Android 11
320kbps should be the default, I wonder why the f**k Xiaomi gives us 96kbps.
Does it work in Pixel Experience rom on Surya?