Hello guys,
I am an Yota 3 user.
I just got the phone and am very disappointed that there is no Camera2 API support in this phone.
I know this phone has very great camera sensor on the back, yet has very poor quality camera app.
With Camera2 API, we can use the greatest Google Camera app to take a picture and even get RAW files.
That would be a tremendous software upgrade.
Is there any developer who would implement the API?
If there is none, please, would anyone who knows implementation of the API give me a clue to implement the API to the phone?
I would like to try the implementation myself.
Thank you.
Try adding "persist.camera.HAL3.enabled=1" to your build.prop file:
Temporarily boot into recovery
Code:
fastboot boot recovery.img
Mount system and then using adb, pull the build.prop file
Code:
adb pull /system/build.prop <path to save file>
Edit the file you just extracted and save it. Push it back to your phone via adb
Code:
adb push <path to your file> /system/build.prop
Set permissions:
Code:
adb shell
chmod 644 /system/build.prop
vevgeniev said:
Try adding "persist.camera.HAL3.enabled=1" to your build.prop file:
Temporarily boot into recovery
Code:
fastboot boot recovery.img
Mount system and then using adb, pull the build.prop file
Code:
adb pull /system/build.prop <path to save file>
Edit the file you just extracted and save it. Push it back to your phone via adb
Code:
adb push <path to your file> /system/build.prop
Set permissions:
Code:
adb shell
chmod 644 /system/build.prop
Click to expand...
Click to collapse
I tried that by directly editing build.prop (rooted).
But I see no difference. And open camera still does not work (even when you change the settings to use the camera api).
Did anyone successfully activate this with his yota3+ ?
Related
If you are using ADB Shell on a Windows machine and try to LS with busybox on your phone it will add color coding along with directory and file names.
To get rid of this you need only need to type [1] in the command prompt.
If you would like an LL type function added you can also put in [2].
[1] alias ls='ls --color=never'
[2] alias ll='ls -la --color=never'
Is there any way to get these aliases to stick?
The aliases go away every time I open a new ADB Shell. :\
##########edit1
I found that you can use PuTTYcyg to properly display the colors if you have Cygwin installed on your machine.
I just selected "Cygterm" for "Connection type" and put "adb shell" in "Command (use - for login shell)".
I would still like to have an alias for LL at least if we can figure out a way to get the aliases to stick.
Thanks!
##########edit2
In case people have no idea what I'm talking about.
Busybox LS output with color in Windows CMD:
Code:
# ls
ls
←[1;34mcache←[0m ←[1;36metc←[0m ←[1;34mroot←[0m
←[1;34mconfig←[0m ←[1;32minit←[0m ←[1;34msbin←[0m
←[1;36md←[0m ←[1;32minit.desirec.rc←[0m ←[1;34msdcard←[0m
←[1;34mdata←[0m ←[1;32minit.goldfish.rc←[0m ←[1;34msqlite_stmt_journals←[0m
←[0;0mdefault.prop←[0m ←[1;32minit.rc←[0m ←[1;34msys←[0m
←[1;34mdev←[0m ←[0;0mlogo.rle←[0m ←[1;34msystem←[0m
←[1;34memmc←[0m ←[1;34mproc←[0m
Busybox LS output without color in Windows CMD:
Code:
# ls --color=never
ls --color=never
cache etc root
config init sbin
d init.desirec.rc sdcard
data init.goldfish.rc sqlite_stmt_journals
default.prop init.rc sys
dev logo.rle system
emmc proc
And now color just looks like one of the weirdest words to me after looking at it for so long....
COLOR.
I got an LL going if anyone is interested. Basically using this guys instructions but making it for ll instead of dir.
1) Create a file named ll in /system/xbin
With this in it [NO COLOR]:
Code:
#!/system/xbin/sh
ll(){
ls -la --color=never [email protected]
}
ll [email protected]
OR
With this in it [COLOR]:
Code:
#!/system/xbin/sh
ll(){
ls -la [email protected]
}
ll [email protected]
2) Set file ownership/permissions
Get an ADB Shell:
Code:
cd /system/xbin
chown 0 ll
chmod 755 ll
The LL command will work immediately after setting ownership/permissions on the LL file. It's a workaround for now but works great.
Updated first post.
Not at all
The shortest way to do it is:
Code:
# alias ls="ls --color=never"
What I wonder is how to get rid of the annoying ECHO..
Long term fix?
Any better ways to fix this? I never used to have this problem, but all of a sudden, after messing with ADB over WiFi, now I do have this problem
http://forum.xda-developers.com/showthread.php?p=14564633
The alias only works for a single cmd session
update
ScottHW said:
Any better ways to fix this? I never used to have this problem, but all of a sudden, after messing with ADB over WiFi, now I do have this problem
Click to expand...
Click to collapse
Small update: I noticed that I actually only have the problems with ls -al when the phone is fully booted. When I use adb booted in Recovery (CWM) the file listings are fine.
It's possible that I have never used adb while the phone is fully booted before, and just assumed that the Recovery behavior was universal and when I got the funky behavior, it wasn't messing around with ADB, it was just because I didn't know what "normal" was.
Short term fix is still just to use an alias for ls
But you have to redo it every time you restart adb
1. Prepare a short mp3 and name it android_audio.mp3
2. Put the mp3 under the adb folder
3. Save the following code as !bootaudio.bat (I use this name)
4. Turn your phone into ADB debugging mode
5. run !bootaudio.bat
6. Reboot your phone and have fun!
This should work on almost all G7
Tips: During the boot animation, the volume would change twice. So I suggest insert 1 second before the audio for escaping from the volume changing side-effect.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb shell rm /data/local/android_audio.mp3
adb push android_audio.mp3 /data/local/
adb shell rm /system/customize/resource/android_audio.mp3
adb shell ln -s /data/local/android_audio.mp3 /system/customize/resource/android_audio.mp3
adb shell ls -l --color=never /data/local
adb shell ls -l --color=never /system/customize/resource/
adb pull /system/customize/CID/default.xml
pause
Script description:
Mount the system path to enable writing access.
Remove the original boot sound if it exists.
Push your mp3 into the data/local, where the bootanimation.zip is.
Make a link to data/local/android_audio.mp3
List the two affected pathes for you to confirm the result
Pull the default.xml out from the phone, if you find it not work after reboot, you can check the xml to see what the actural fullpath it is using. And manually change the script to try again.
My current boot sound is attached to the thread.
Hi there, I have an error when trying to link beacause the folder does not exist... may I create it manually?!
I couldn't run scripts in init.d, and it took me a while to figure this out, so I'm sharing. There is more than one way to do this.
Step 1. Install chulri's rw root.
Step 2. Create a script directory and a runall script to run all the scripts in a given directory. To do that, you can type the following in an adb shell:
Code:
su
mkdir /data/local/bootscript
chmod 755 /data/local/bootscript
cd /data/local/bootscript
cat > runall
#!/bin/sh
for x in /data/local/bootscript/*.sh ; do /bin/sh $x ; done
(You can copy and paste that into a DOS window running adb.) Now press ctrl-d, enter. Then continue:
Code:
chmod 755 runall
Step 3. Edit /init.rc. You can do that on-device with vi and ssh, or you can install an editor that preserves Linux line-endings on your desktop (I use CONTEXT). I'll assume you're doing this with adb. So on the desktop do:
Code:
adb pull /init.rc init.rc
Now, edit init.rc on the PC, and to the section listing all the services, add:
Code:
service bootscript /data/local/bootscript/runall
enabled
oneshot
Then put it back on the device:
Code:
adb push init.rc /tmp
adb shell
su
mv /tmp/init.rc /
Step 4. Now you can put whatever scripts you want to run in /data/local/bootscript. Just make sure you they have a .sh extension. All scripts will be run with /bin/sh and there is no need to specify #!/bin/sh . Also, there is no need to chmod the scripts to render them executable. You can just copy scripts in.
To disable a script, just change its .sh extension to .disabled.
There are, of course, other ways of doing this.
great tutorial!
Download THIS file.
Extract the things inside it and put them in your adb folder.
push it.
Code:
adb push be_photo /system/etc
adb push be_movie /system/etc
now pull the build.prop file
Code:
adb pull /system/build.prop
go to adb folder and open the buid.prop file with notepad. add this to the end of it:
Code:
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
save and push it back in:
Code:
adb push build.prop /system
now go to terminal emulator on your phone and type this in:
Code:
su
busybox chmod 0755 /system/etc/be_photo
busybox chmod 0755 /system/etc/be_movie
busybox chown 0.0 /system/etc/be_photo
busybox chown 0.0 /system/etc/be_movie
reboot the phone and have happy times with the bravia engine >
i got this information from Kabir Saini on facebook. I didnt do any of this work myself
i tried it on my phone and i think there is a slight improvement...
PersianSphinx said:
Download THIS file.
Extract the things inside it and put them in your adb folder.
push it.
Code:
adb push be_photo /system/etc
adb push be_movie /system/etc
now pull the build.prop file
Code:
adb pull /system/build.prop
go to adb folder and open the buid.prop file with notepad. add this to the end of it:
Code:
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
save and push it back in:
Code:
adb push build.prop /system
now go to terminal emulator on your phone and type this in:
Code:
su
busybox chmod 0755 /system/etc/be_photo
busybox chmod 0755 /system/etc/be_movie
busybox chown 0.0 /system/etc/be_photo
busybox chown 0.0 /system/etc/be_movie
reboot the phone and have happy times with the bravia engine >
i got this information from Kabir Saini on facebook. I didnt do any of this work myself
i tried it on my phone and i think there is a slight improvement...
Click to expand...
Click to collapse
Are you sure that it work buddy? I want mean, not necessary other files like framework or libraries?
How system knows that are 2 new files in /system only editing build.prop?
there's already an another thread about it.. :/
-tapatalked by RnB
i_rnb said:
there's already an another thread about it.. :/
-tapatalked by RnB
Click to expand...
Click to collapse
sorry, but i searched for it and couldnt find anything!
denzel09 said:
Are you sure that it work buddy? I want mean, not necessary other files like framework or libraries?
How system knows that are 2 new files in /system only editing build.prop?
Click to expand...
Click to collapse
apparently it will work. im not 100% but i think it will.
anyways, its only 2KB your adding, so big deal right?
PersianSphinx said:
sorry, but i searched for it and couldnt find anything!
Click to expand...
Click to collapse
u had to search a lil bit longer ..
http://forum.xda-developers.com/showthread.php?p=19597041
-tapatalked by RnB
Until there are ad blocking apps for FFOS it needs a DIY method.
I'll assume you know how to use adb and have it set up on your machine. I'll also assume you have rooted your phone following the instructions here.
I use Linux so my commands may be a bit off in places.
1. Collect a suitable hosts file. I used the one on my Android phone but this one seems to update regularly http://winhelp2002.mvps.org/hosts.txt
2. Save the file as 'hosts' to a known location on your PC.
3. Open a shell window (command window) on your PC and check adb works.
Code:
adb devices
should return roamer2. If not, on your phone, go to settings > More Information > Developer - and check Remote Debugging.
4. In the shell window - change directory to where you have saved the hosts file. then type:-
Code:
adb push hosts /sdcard/
5. When that completes type:-
Code:
adb shell
you'll see $ prompt
Code:
su
If you are rooted correctly you'll see # prompt
Code:
mount -o remount,rw /system
Mounts the system folder for read / write permissions.
Code:
cat /system/etc/hosts
Should show just '127.0.0.1 localhost'
Save this if you want as hosts.old
Code:
busybox mv /system/etc/hosts /system/etc/hosts.old
Now replace the hosts file with the new one:-
Code:
busybox mv /sdcard/hosts /system/etc/hosts
To check your hosts file has been replaced type
Code:
cat /system/etc/hosts
And lots of domain names will whiz past.
All done.