Related
I wish to turn off continous autofocus when i take videos, the only thing this continously does is - it continoutly ruin my videos with excessive amout of blur that makes it impossible to use in many cases.
Interior videos, even outside it tends to totally mess up any attempts to make a decent video.
I saw some custom roms have a option to disable it in options, but i would like to keep the original rom - Root it and change whatever magic inaccesible settings i need to change (like the silent camera shutter ro.camera.sound.forced=0 setting).
I saw Potatoman's camera.apk mod but that does not have any options regarding video autofocus.
totally useless
i am with you on that problem, i don't even film anymore. all movies with moving objects or even if i move my camera are useless. i don't know why they made it this way. hope for a quick and reliable solution.
Its annoying as hell. I also dont bother recording! . Sad really.
Sent from my porn shoot using GT-I9100.
+1 for this problem.
I saw some custom roms have a option to disable it in options
Click to expand...
Click to collapse
Can you provide a link to a such rom?
It is miui for galaxy s2, i saw this in action and it has a option to disable auto-bluring of videos but i dislike the rest of gui. Plus i lose stuff like usb otg if i put that rom on so i'm searching for another solution:
http://forum.xda-developers.com/showthread.php?t=1130951
No luck Tried the camera apk from miui and it doesn't work on my kf3 stock rom.
I think our best hope is that Potatoman fixes this, i cannot reply in his topic (10 posts limit), but i sent him a private message about this and i hope he reads it.
I looked into disassembly tools for apk files and so far had no success taking apart the camera app myself, otherwise if i had a working way to disassemble and reassemble it i would do this myself (baksmali fails on me with a "Could not find the main class: R:\Internet\baksmali-1.2.7.jar. Program will exit." message).
JernejL said:
I looked into disassembly tools for apk files and so far had no success taking apart the camera app myself, otherwise if i had a working way to disassemble and reassemble it i would do this myself (baksmali fails on me with a "Could not find the main class: R:\Internet\baksmali-1.2.7.jar. Program will exit." message).
Click to expand...
Click to collapse
You should extract the classes.dex file from the Camera.apk (using WinRar) and put it to the same folder with baksmali-1.2.7.jar.
I managed to do that, and found the magic command line parameters for running it, i have the smali files but this looks like one big mess.
I found startTimer in onVideoRecordingStart
and .method public handleMessage(Landroid/os/MessageV in camera main handler, this contains text such as "AF_WAIT_TIMER_EXPIRED" and calls to restartTouchAutoFocus, it could be the timer which continously calls autofocus, but it's not in camcorder classes but the camera class - i am not sure how the classes are interconnected and if this is really what i was looking for, i wish potatoman can help better with this.
I found something else, it looks like continous focus is a camera property - focusing mode:
.method public static getFocusModeString(I)Ljava/lang/String;
it has modes: "auto, fixed, macro, facedetect, continuous-video" and is saved to preferences as "pref_camera_focus_key" (this is my guess based on what i am seeing)
It seems that android api confirms this:
developer.android.com/reference/android/hardware/Camera.Parameters.html#FOCUS_MODE_CONTINUOUS_VIDEO
called with:
developer.android.com/reference/android/hardware/Camera.Parameters.html#setFocusMode%28java.lang.String%29
camcorderengine:
.method public doPrepareVideoRecordingAsync()V
const-string v3, "continuous_af"
this goes into..
const-string v1, "continuous_af"
const/4 v1, 0x0
invoke-virtual {v0, v3, v1}, Lcom/sec/android/seccamera/SecCamera$Parameters;->set(Ljava/lang/String;I)V
useful info here too:
pastebin.com/V94HYCnk
Code:
// Parse continuous autofoucs into a format the driver understands
conAf = pars.get("enable-caf");
if (conAf != 0 && strcmp(conAf, "on") == 0) {
mContinuousAf = true;
}
else {
mContinuousAf = false;
}
pars.set("continuous_af", mContinuousAf ? 1 : 0);
I hope this research opens up the possibility that potatoman fixes this for us, i can barely read this .smali assembly and i'm afraid i'll break everything if i change anything.
note: i had to cripple all the http links because i have too few posts to link to things externally.. :/
Hey guys, just a heads up that I'm working on v2 of my mod now, so while I'm doing that I'll take a look at this too. I don't usually film video though, so just to be clear, do you guys want it to just stop adjusting the focus entirely, or adjust the focus faster so that it isnt blurry for so long (since atm it takes like 5s before refocusing.) Personally I think the best solution would be to refocus on tapping the screen like the camera does, but I'm not sure if that's possible during capture, so I'd have to look into it.
Please post telling me which, so I know what I'm trying to implement here. I don't want to make it worse!
Refocus when tapping the screen will be the best way i think...
Sent from my GT-I9100 using XDA App
Based on the code and documentation that i saw, it's not even possible to adjust the focusing speed.
I would prefer that any automatic focusing is simply disabled during video recording / camcorder mode.
If tap to focus works can be done that would be brilliant, but no automatic adjustments as this ruined every video i took so far.
The phone simply starts refocusing / enters blur mode for no reason while the picture is already totally crisp and then ruins 3-5 seconds of video with blur while it tries to find "focus".
we need touch to focus
is the best solution
today i read online that choosing for a lower resolution then the full had filming wil fix the problem, i havent got any time yet to test it ........
Tap2Focus would be awesome! BUT simple disabling continuous af would be enough for start
I wish the operation is as following:
1, The focus start and lock when I touch the Record icon.
2, The focus is disable and start to record when I release my finger from the Record icon
mrky said:
today i read online that choosing for a lower resolution then the full had filming wil fix the problem, i havent got any time yet to test it ........
Click to expand...
Click to collapse
I tried this - one of first things i tried, it doesn't really help at all in my case (tested this outside in a clear well sun lit scene)
stev2010 said:
I wish the operation is as following:
1, The focus start and lock when I touch the Record icon.
2, The focus is disable and start to record when I release my finger from the Record icon
Click to expand...
Click to collapse
+1 Yes please!
But I would settle for ANYTHING to disable auto-focus because it make videos totally useless.
I actually have no problem with autofocus itself... but my issue is that auto focus does not work at ALL on any resolution lower than 1080... Anyone else have this issue?
In this thread we should share our own little tweaks to this amazing ROM.
I'll add to this first post any stuff that is proven to increase speed or makes using the ROM easier or more enjoyable
Note, this isn't intended to include mods and addons, as there is already a great thread for that
IMPORTANT:
Always backup stuff! And reboot after teaking!
Please note that, the ones I've found more useful, I add a USEFUL tag in front of them
____________________________________
BUILD.PROP tweaks
With root explorer or any other method of your liking, go to /system/ and edit the file build.prop.
- To increase max fps limit possible, add:
Code:
windowsmgr.max_events_per_sec=150
I'm not sure this one is really useful, I think android already sets this already to around 1.5x screen refresh rate. The gains could be negligible.
- Disable error checking, add:
Code:
ro.kernel.android.checkjni=0
- USEFUL Stop debugging icon from appearing in status bar (doesn't disable adb), add:
Code:
persist.adb.notify=0
- USEFUL Force home launcher into memory, add:
Code:
ro.HOME_APP_ADJ=1
_______________________________________________
OTHER TWEAKS AND TRICKS
- VERY, Extremely, Mega-USEFUL - Go to:
Code:
/system/lib/elg
Open egl.cfg and delete the 1st line (0 0 android), reboot the phone.
Everything should be much smoother, I notice this especially opening folders with a lot of icons in Apex Launcher. I think this disables the default android software rendering method and uses only GPU. Don't ask me if this is different than setting composition mode to gpu in build.prop, I don't know, I just know everything is much faster
USEFUL - Only works with Aurora 2.07+ and synaptics screen - Tweak your screen duplicate filter, like in x5settings for .32 kernels.
Go to:
sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity
Open the file "sensitivity" and tweak the value. Default is 4. Higher values reduce screen flickering/jitter but screen can become less sensitive, lower values, the contrary. Personally I use 8, works very good for my fingers, adjust you value accordingly. Note, this takes effect immediately, but doesn't stick after a reboot. To make it stick after a reboot, go to "/system/etc/", open one of the scripts, I recommend "ini.qcom.post_boot.sh", and add this at the end:
Code:
echo 8 > sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity
where 8 is the value you want. Save, reboot and check is the value is there, in the "sensitivity" file.
- USEFUL - Great tips on how to save battery without turning everything off (bonus, doesn't use BS calibration myth):
http://www.androidcentral.com/keeping-your-charge-how-improve-battery-life-your-android-phone
Works AMAZINGLY thank you
Edit1: Also may i ask what CPU settings do you use? any overclocks/governor?
Edit2: I got that funny text glitch just before, i decided to wipe cache and dalvik and i haven't had it again yet. Ill get a screen shot if it happens again but im pretty sure you know what i mean, all the text for apps look like squiggly lines/really odd ive seen this happen normally in previous versions of aurora but oh well ill come back with more info if anything else happens thanks again!
thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium
spirosbond said:
thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Regarding the logcat, yes, probably disables that functionality, I've read in other sites, it just disables checking for errors, thus performance improvements. When I have time, I'll check if logcat is still there... the composition thing I think it tells the OS to always use GPU no matter what, I see a great improvement with that one, don't know if anything is affected, but so far, everything is great
EDIT: these tweaks were from here:
http://forum.xda-developers.com/showthread.php?t=1578065
Sent from my U8800
Here are some more:
http://www.freeyourandroid.com/guide/build-prop-modifications
If you try some, please post results, to add to first post.
spirosbond said:
thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Logcat still works
Added synaptics TS setting like there was in X5settings app (Touchscreen Filter).
fjsferreira said:
Added synaptics TS setting like there was in X5settings app (Touchscreen Filter).
Click to expand...
Click to collapse
hi there, i have changed it right now to value 10 and its the same, its trembling...
i have kernel v3 from Dzo 2.0.5 rom.
and have restart the phone too
r1c4rd0 said:
hi there, i have changed it right now to value 10 and its the same, its trembling...
i have kernel v3 from Dzo 2.0.5 rom.
and have restart the phone too
Click to expand...
Click to collapse
Yes, I think so, maybe it was just placebo... also, it doesn't stick after a reboot, the ROM would need init.d startup script support and a script to change the value everytime... try change it to 40 or something, and report, it it still trembles, I'll remove from the first post...
fjsferreira said:
Yes, I think so, maybe it was just placebo... also, it doesn't stick after a reboot, the ROM would need init.d startup script support and a script to change the value everytime... try change it to 40 or something, and report, it it still trembles, I'll remove from the first post...
Click to expand...
Click to collapse
will try it right now
edit: changed the value and no diference... then i restart and no diference too...
I think it doesn't work... I've changed it to 1 and notice no difference... I'll remove that thing from front post and post here if anyone wants to study it...
- Something to try, it seems not to work... - Improve synaptics screen sensitivity!
Do you miss x5Settings setting about touchscreen filter? I've been studying x5settings source code and found out what file needs to be changed to achieve the same result in Aurora. Go to:
- sys/module/synaptics_i2c_rmi_1564/parameters/
Edit the file "sensitivity" and set a value appropriate for you. I've set it to 8 and touchscreen seems better now. Maximum value I think is 64, and that works great too. I think this isn't placebo Pinch to zoom in pics doesn't "tremble" when holding the fingers on the screen as it did before, here.
EDIT: it doesn't stick after a reboot! And values change by itself, don't know why, maybe it doesn't even work... Try it for your self
fjsferreira said:
- Something to try, it seems not to work... - Improve synaptics screen sensitivity!
Do you miss x5Settings setting about touchscreen filter? I've been studying x5settings source code and found out what file needs to be changed to achieve the same result in Aurora. Go to:
- sys/module/synaptics_i2c_rmi_1564/parameters/
Edit the file "sensitivity" and set a value appropriate for you. I've set it to 8 and touchscreen seems better now. Maximum value I think is 64, and that works great too. I think this isn't placebo Pinch to zoom in pics doesn't "tremble" when holding the fingers on the screen as it did before, here.
EDIT: it doesn't stick after a reboot! And values change by itself, don't know why, maybe it doesn't even work... Try it for your self
Click to expand...
Click to collapse
hey fjsferreira if you want stick after a reboot, you must to paste this command "echo 8 > /sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity" (without the quotes) into 1 of the files in /etc/init.d
number 8 is choise by us... but make 8 for this example
r1c4rd0 said:
hey fjsferreira if you want stick after a reboot, you must to paste this command "echo 8 > /sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity" (without the quotes) into 1 of the files in /etc/init.d
number 8 is choise by us... but make 8 for this example
Click to expand...
Click to collapse
The problem is, there isn't an /etc/init.d :S maybe it can be added to one of the scripts in /etc/
fjsferreira said:
The problem is, there isn't an /etc/init.d :S maybe it can be added to one of the scripts in /etc/
Click to expand...
Click to collapse
yes it can...
r1c4rd0 said:
yes it can...
Click to expand...
Click to collapse
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!
fjsferreira said:
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!
Click to expand...
Click to collapse
yes it works, but i think its related to his new v3.0 kernel...
in .35 kernel, if i´m not worng, we can change that value.
i think placebo dont work with me lol
fjsferreira said:
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!
Click to expand...
Click to collapse
I tried 8 and 10 but the flickering didn't reduce. Thanks for the tip though. I hope you get it working...
Question:
What is the difference between the mod:" get rid of cpu composition" and setting the line
debug.composition.type=gpu
at build.prop?
By making the above change doolde jump graphics where improved
Cheers
You have ro.HOME_APP_ADJ=0 to force the launcher into the memory, but wouldn't the right value be 1?
FlashTH said:
You have ro.HOME_APP_ADJ=0 to force the launcher into the memory, but wouldn't the right value be 1?
Click to expand...
Click to collapse
Correct. I've fixed it, thank you!
Sent from my U8800
i dont know if you notice, but wen the phone is charging touchscreen feels more jumpy...
can anyone confirm this?
maybe this will interest dzo in the ics port? in this site there are the amtel and synaptics drivers:
port ics input drivers
drivers from HTC Legend touch the same as desire:
drivers synaptics from htc
thanks
So I have an idea for a ticker mod, but since I have zero programming knowledge I thought I'd see if any of you smart people could help. The stock ticker has the icons for messages, vvm, email, missed calls and im. Trailblazers mod allows us to use the icons to display the apps even if there are no missed messages, calls,etc. I don't use the vvm, email or im, so I'm wondering if it would be possible to change those three to different apps... Like Google Voice, Gmail, and contacts? I wouldn't mind trying myself, but have no idea where to even start looking. Not worried about changing the icons, just what app is launched when pressed. Anyone have any idea if this is possible...or if it's already been done/tried?
Sent from my SCH-I400
roaddog665 said:
So I have an idea for a ticker mod, but since I have zero programming knowledge I thought I'd see if any of you smart people could help. The stock ticker has the icons for messages, vvm, email, missed calls and im. Trailblazers mod allows us to use the icons to display the apps even if there are no missed messages, calls,etc. I don't use the vvm, email or im, so I'm wondering if it would be possible to change those three to different apps... Like Google Voice, Gmail, and contacts? I wouldn't mind trying myself, but have no idea where to even start looking. Not worried about changing the icons, just what app is launched when pressed. Anyone have any idea if this is possible...or if it's already been done/tried?
Sent from my SCH-I400
Click to expand...
Click to collapse
That actually doesn't sound like a bad idea.
trailblazer101 is the ticker guru, if you do want to attempt a ticker mod you can start here: http://forum.xda-developers.com/showpost.php?p=19758250&postcount=1
trailblazer let us in on some of his sources to patch, it has to do with ticker. then you can take apart his currrent mod and see that there are already actions for those icons. mow it will go deep so decompile the apks and look around, they will start to make some sense.
he may just tell you/us where the mods are once you can grasp what you will be doin
roaddog665 said:
So I have an idea for a ticker mod, but since I have zero programming knowledge I thought I'd see if any of you smart people could help. The stock ticker has the icons for messages, vvm, email, missed calls and im. Trailblazers mod allows us to use the icons to display the apps even if there are no missed messages, calls,etc. I don't use the vvm, email or im, so I'm wondering if it would be possible to change those three to different apps... Like Google Voice, Gmail, and contacts? I wouldn't mind trying myself, but have no idea where to even start looking. Not worried about changing the icons, just what app is launched when pressed. Anyone have any idea if this is possible...or if it's already been done/tried?
Sent from my SCH-I400
Click to expand...
Click to collapse
It would be really, really easy... hahahaha... Voice Mail already sends you to Google Voice in my Gingerbread Mods, so we are already a fifth done, haha... But to be honest with you, why don't you just set the shortcuts you want in the quick launch screen, now that is is customizable and all (and soon will be rotation aware also )
But yea, it wouldn't be hard at all... Changing from VVM to Google Voice was a matter of changing two lines of code.... Changing the others will be a little more involved, because you have to delete a lot of previous code (there's some code that goes into launching the email screen, other than just calling the program... It has to get/send the ID for the email, etc etc etc... same thing for messaging...) But that's just a matter of deleting code...
trailblazer101 said:
It would be really, really easy... hahahaha... Voice Mail already sends you to Google Voice in my Gingerbread Mods, so we are already a fifth done, haha... But to be honest with you, why don't you just set the shortcuts you want in the quick launch screen, now that is is customizable and all (and soon will be rotation aware also )
But yea, it wouldn't be hard at all... Changing from VVM to Google Voice was a matter of changing two lines of code.... Changing the others will be a little more involved, because you have to delete a lot of previous code (there's some code that goes into launching the email screen, other than just calling the program... It has to get/send the ID for the email, etc etc etc... same thing for messaging...) But that's just a matter of deleting code...
Click to expand...
Click to collapse
Lol... Didn't even know about the Google Voice...see, your way ahead of me!
And I've already set the others, just figured that since these are there not being used might as well try to make them useful. My problem is that all this code is exactly that to me... Code! As in super secret, undecipherable code! Lol. Now, if somewhere it says "push this icon to launch app x" and I can change x to whatever app I need, I could probably figure it out... Maybe I'm looking at the Services.jar smali now, and it's giving me a headache. Haha.
Sent from my SCH-I400
Alright, here's if I was you how to start out... First, figure out where the actions you want to change are coming from... You can change something in the area that you want changed (like push a button or anything like that), then look in logcat/DDMS to see where it is coming from! That will lead you to the smali file..... In your case, because you want to modify something in the Ticker Missed Notification View screen, you can use a little bit of luck and assume its coming from TickerMissedNotificationView.smali within the services file, haha... Now, you limited it down a lot... From here, you need to narrow it down more... Think about what exactly is happening; so, you are clicking a button, and it does some action... Well, why don't we find the button first, then that can lead us elsewhere... *HINT: A good place to start looking for things, no matter where you are, is within onFinishInflate()V*... So, let's look for something that looks like the button... First thing I see is: "mNewEmailImage:Landroid/widget/ImageButton;." alright, so let's follow that, and see where it goes! Later on within that function, you see something along the lines of:
Code:
iget-object v0, p0, Lcom/android/server/ticker/TickerMissNotificationView;->mNewEmailImage:Landroid/widget/ImageButton;
new-instance v1, Lcom/android/server/ticker/TickerMissNotificationView$4;
invoke-direct {v1, p0}, Lcom/android/server/ticker/TickerMissNotificationView$4;-><init>(Lcom/android/server/ticker/TickerMissNotificationView;)V
invoke-virtual {v0, v1}, Landroid/widget/ImageButton;->setOnClickListener(Landroid/view/View$OnClickListener;)V
We are getting warmer! We know that this is right, because it has "OnClickListener"... Its just common sense that this code does whatever is within TickerMissNotificationView$4 when clicked! Now, open up the specified file, TickerMissNotificationView$4, and see what that does!
This is where it gets tricky.. You don't see anything that says: HEY, I JUST GOT CLICKED, SO LET'S DO THIS!!!"
Instead, you often see code that sends a "message" to somewhere else, just for funsies But, let's continue... Since we don't see anything within that file itself about opening the email screen (HINT: you know a program is being opened when you see: com.blah.blah.SOMETHINGEMAIL"), find what the message is, and where it is being sent to!
So, at the end of the file, you see:
Code:
const/16 v1, 0x69
iput v1, v0, Landroid/os/Message;->arg1:I
.line 220
iget-object v1, p0, Lcom/android/server/ticker/TickerMissNotificationView$4;->this$0:Lcom/android/server/ticker/TickerMissNotificationView;
iget-object v1, v1, Lcom/android/server/ticker/TickerMissNotificationView;->mHandler:Lcom/android/server/ticker/TickerMissNotificationView$H;
invoke-virtual {v1, v0}, Lcom/android/server/ticker/TickerMissNotificationView$H;->sendMessage(Landroid/os/Message;)Z
This looks promising! So now let's open up TickerMissNotificationView$H, and try and do a search for const/16 v1, 0x69... Oh uh, no results! But you do see that this is the right place, because you see that it is launching other apps from here! From here, you can do two things... A) you can just search through the file, find code that looks like it is opening the email program, and move to the start of the section (right after pswitch)... or my favorite, b) you know that each section of this file is doing different things, and you see that they are divied up by "pswitch"s... so, let's find out how it knows where to go! After looking around, you will find your answer at the bottom: ".packed-switch 0x65"... This code starts with 65, and goes up to whatever the last message is so, for example: 65 would be pswitch_0, 66 would be pswitch_1, etc etc... So, by using this method, we can go exactly where we need to go! find where pswitch_4 happens again, and that's your start... Now, select all the code within the two pswitchs, copy it into another file, then delete it... you should now have "pswitch_4, then right after, pswitch_5"...
Here's the part that makes you always feel guilty, cheat! Find code that is close to what you want, and make it your own So, look through the other "pswitch"s and find which one has code that is ONLY launching an application, not anything else... CLUES: look for the indicator I gave you before: "com.blah.blah.whatever"... So for this case, you find something like this:
Code:
new-instance v8, Landroid/content/Intent;
invoke-direct {v8}, Landroid/content/Intent;-><init>()V
.line 547
.restart local v8 #intent:Landroid/content/Intent;
const/high16 v18, 0x1480
move-object v0, v8
move/from16 v1, v18
invoke-virtual {v0, v1}, Landroid/content/Intent;->setFlags(I)Landroid/content/Intent;
.line 548
const-string v18, "com.android.mms"
const-string v19, "com.android.mms.ui.ConversationList"
move-object v0, v8
move-object/from16 v1, v18
move-object/from16 v2, v19
invoke-virtual {v0, v1, v2}, Landroid/content/Intent;->setClassName(Ljava/lang/String;Ljava/lang/String;)Landroid/content/Intent;
.line 549
move-object/from16 v0, p0
iget-object v0, v0, Lcom/android/server/ticker/TickerMissNotificationView$H;->this$0:Lcom/android/server/ticker/TickerMissNotificationView;
move-object/from16 v18, v0
move-object/from16 v0, v18
iget-object v0, v0, Lcom/android/server/ticker/TickerMissNotificationView;->mTickerService:Lcom/android/server/ticker/TickerTapeService;
move-object/from16 v18, v0
move-object/from16 v0, p0
iget-object v0, v0, Lcom/android/server/ticker/TickerMissNotificationView$H;->this$0:Lcom/android/server/ticker/TickerMissNotificationView;
move-object/from16 v19, v0
invoke-virtual/range {v19 .. v19}, Lcom/android/server/ticker/TickerMissNotificationView;->getContext()Landroid/content/Context;
move-result-object v19
move-object/from16 v0, v18
move-object/from16 v1, v19
move-object v2, v8
invoke-virtual {v0, v1, v2}, Lcom/android/server/ticker/TickerTapeService;->launchActivity(Landroid/content/Context;Landroid/content/Intent;)V
goto/16 :goto_0
.line 555
.end local v8 #intent:Landroid/content/Intent;
This is short and sweet, so let's use this!
copy and paste that code into the emptiness, and pray Now, i would compile, and make sure that the button you are trying to modify does the same thing that the button you copied from does... If yes, yay!
Now you have to find what is the "call" that is being done when you launch the application of your choice... So, go into logcat/DDMS, again, and open up the program you want to set as your button... look for the hint I gave you before; you should see code code code, and within some of that code: "com.1.2" ".1.2.3"
For example, this is what you see when you open up facebook:
Code:
starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.facebook.katana/.LoginActivity }
So, replace the
Code:
const-string v18, "com.android.mms"
const-string v19, "com.android.mms.ui.ConversationList"
with
Code:
const-string v18, "com.facebook.katana"
const-string v19, "com.facebook.katana.LoginActivity"
You should now be done
awesome! we need a super or thanks+ button for you!
ill be moving this weekend and into next week, finally after 9 mos got our house! something always comes out when im busy thats life but to say the least i will be back in action soon.
and this method will help with customization for individual users, like me with no real need for phone, mms, ect since its more of a mini game device. btw minecraft pe 040 and FFIII are time killers! love them.
Ok, I've made my changes and compiled the new Services.jar. The new one only has a classes.dex file, the original pulled from the phone has a classes.dex file and a META-INF folder. Should I replace the classes.dex file in the original with my modified new one and then push it back to the phone, or am I thinking wrong.
Sent from my SCH-I400 using xda app-developers app
roaddog665 said:
Ok, I've made my changes and compiled the new Services.jar. The new one only has a classes.dex file, the original pulled from the phone has a classes.dex file and a META-INF folder. Should I replace the classes.dex file in the original with my modified new one and then push it back to the phone, or am I thinking wrong.
Sent from my SCH-I400 using xda app-developers app
Click to expand...
Click to collapse
Yes, that should work! Good thinking Now, don't be worried if it force closes, trust me, there's a good chance haha... You could also use my program, which would do that for you automatically... (choose 11, y, n)...
EDIT: Like right now, I'm bored... I just finished adding rotation to the quick launch and the missed notification screen, so I'm working on something a little more.. adventurous I'm trying to see if I can make it so if you hit the grip pad three times in a row fast, it'll automatically skip to the next/previous song... But i keep getting FCs, hahaha...
Good luck with that! Lol
I'm just happy that I was looking in the right place... Even if I didn't know what I was looking for! Well, getting ready to push it back to the phone... Fingers crossed
Sent from my SCH-I400 using xda app-developers app
roaddog665 said:
Good luck with that! Lol
I'm just happy that I was looking in the right place... Even if I didn't know what I was looking for! Well, getting ready to push it back to the phone... Fingers crossed
Sent from my SCH-I400 using xda app-developers app
Click to expand...
Click to collapse
If it doesn't work, you are moving into the fun debugging stage of things This page will become your life:
http://webcache.googleusercontent.c...alvik-bytecode.html+&cd=1&hl=en&ct=clnk&gl=us
That's because DDMS/Logcat doesn't give you nice outputs sometimes when something goes wrong... It does give you the bytecode equivalent of the function that is the problem child, though! I'll show you how to do that if it doesn't work
oh, and I managed to get it work, haha... Now you can go to the previous/next song by tapping the grip sensor on the left/right side accordingly
You, sir, are a scholar and a gentleman!! Works perfectly so far! Did get a little worried at first, when I pushed the jar back nothing really happened... Until I pushed the email icon! Then it did this really cool crash where the screen goes black and it plays my boot sound. Pulled battery and restarted, and it sat on the boot ani forever... Like after a delvik wipe. Was getting ready to pull the battery again, but it came up and is working! Thanks for the education! I'm learning a little bit at a time!
And that's an awesome idea with the grip sensor and the music player! Glad to hear you got it going!
Sent from my SCH-I400 using xda app-developers app
ive gathered some things and did a few tests on my MotoActv since ive gotten it and did some tweaks here and there and i added the following features to mine and put them into a flashable zip for u all
-init.d support (plus some scripts to make it faster then ever) (tested and working (makes two files in sdcard on boot to show it) (picks and chooses when to work now for some reason, so i put an app i made that loads scripts when onCreate()'d and sometimes on-boot)
-Viper4Android sound system (only works for bluetooth headsets if enabled, but its sounds better with good settings)(see credits)
-OpenVPN (idk if theres a use for us but i added the required files (no GUI)
-UsbEnabler.apk (see credits)
-Adblock host (hopefully it works i havent been able to test yet)
-lag-free entropy (so far seems to work, as im not lagging switching launchers anymore)
-MotoActv DPI (my own personall app i made for Changing dpi from 90,100, and stock(120)
-Sqlite3 + init.d sqlite3 optimizer
-Busybox Run-parts (for init.d, still picks and chooses when to work)
-100 Dpi When-Flashed (can be changed back to stock with the MotoActv DPI app i made)
-minor-to-major tweaks from init.d scripts and other methods
-DalvikCache2Sd (not sure if it truly tested working, but i do have a tiny bit more space+no lag like other 2SD methods
soon to be added:
I take bare minimum credit for these, i mostly used this personal zip for when i update my MotoActv's rom, this can be universal for other androids, but it was initially made to the MotoActv watch running custom roms
Credits to give:
(will edit when i get forum post urls and OP's names)
Viper4Android:
OP = @zhuhang
Thread = http://forum.xda-developers.com/showthread.php?t=2191223
UsbEnabler:
OP = @fagalto
Thread = http://forum.xda-developers.com/showthread.php?t=2396138
init.d scripts, OpenVpn, Entropy:
i extracted from the rom on my phone so idk where they originally came from
Init.d App(unreleased w/o mod_pack)+MotoActv DPI:
OP:me @jkok for developing and publishing
Thread (MotoActv DPI):
http://forum.xda-developers.com/showthread.php?t=2435370
Gallery+Live Wallapapers:
Google, But @ClearD for giving me the zip with the script+apks
the zip:
i put together, made the script, signed+released for general use for others:
future credits will be made when i add more things.
Download:
Reusable Download Link
Awesome!
Here's a zip (with changed mounting, again; this time using the exact same one that I use for the rom) of the Live Wallpapers + Gallery apks. Hopefully, this one will work fine.
ClearD said:
Awesome!
Here's a zip (with changed mounting, again; this time using the exact same one that I use for the rom) of the Live Wallpapers + Gallery apks. Hopefully, this one will work fine.
Click to expand...
Click to collapse
well thanks ClearD i can do the script just fine, some of the mountpoints are universal like what i use
umount("/system");
or
run_program("xbin/mount", "/system"); (might be wrong on the xbin part, just going by memory
run_program("xbin/umount", "/system");
but the resolution on the galery on your motoactv rom is too big for it, it resizes dont get me wrong, but it needs to do a single horizontal row cause if u overscroll to the farest right u see there is second or more rows going down, imma fine the sourcecode for the galery2.apk, and make a single-row version when i find it =)
jkok said:
well thanks ClearD i can do the script just fine, some of the mountpoints are universal like what i use
umount("/system");
or
run_program("xbin/mount", "/system"); (might be wrong on the xbin part, just going by memory
run_program("xbin/umount", "/system");
but the resolution on the galery on your motoactv rom is too big for it, it resizes dont get me wrong, but it needs to do a single horizontal row cause if u overscroll to the farest right u see there is second or more rows going down, imma fine the sourcecode for the galery2.apk, and make a single-row version when i find it =)
Click to expand...
Click to collapse
Ah, sweet! That sounds good. I couldn't get it to mount properly any other way so far, but it could have been something as simple as a typo. If it does actually work, then I might use that in the future. That's the one I tried with the last iteration.
ClearD said:
Ah, sweet! That sounds good. I couldn't get it to mount properly any other way so far, but it could have been something as simple as a typo. If it does actually work, then I might use that in the future.
Click to expand...
Click to collapse
the universal way i do my scripts is
mount("ext3", "MTD", "system", "/system");
unmount("/system");
and it always seemed to work for me, so thats why i call it universal anyways
but the other ways i posted seemed to work for me when i tried em, i just used this way cause it was in a zip for a motoactv rom (i think it was yours or the battery mod)
Opps! i was wrong, its not
run_program("xbin/mount", "system");
its
run_program("sbin/mount", "system");
lol i had to check my other mod zips lol
jkok said:
the universal way i do my scripts is
mount("ext3", "MTD", "system", "/system");
unmount("/system");
and it always seemed to work for me, so thats why i call it universal anyways
but the other ways i posted seemed to work for me when i tried em, i just used this way cause it was in a zip for a motoactv rom (i think it was yours or the battery mod)
Click to expand...
Click to collapse
Lol no doubt, I went through the same thing with the battery mod, looking over and over for one that worked better. I'd prefer the xbin/mount method, but for some reason, it was hit and miss on my end with end users. Not sure why, unless busybox wasn't set up right somehow.
Just updated the mod_pack with more features!
Sorry but the only thing i havent really been able to fix that well way the init.d it seemed to workwhen i first released this mod_pack, but it seems to pick+choose when to work, so i added 2 other methods for init.d (one of which is an app i made, yet to release that loads the scripts when the app is onCreate()'d and sometimes on-boot when SuperUser allows it)
but there are some great new features that WILL work, along with some of my own personall apps, tweaks, and clock faces =)
Again: this mod_pack is meant for MotoActv's running a custom rom, and Not meant for AOSP based MotoActv Roms
Tested and confirmed working (except init.d that picks and chooses) on @ClearD 's ClearRom 1.2.0 T2 (and my own personal (un)Official 1.2.1 T1 i made for him)
For some reason all of the mods are being denied superuser, any ideas? I am setup to automatically allow all requests
Edit: Installed SuperSU and my problem has been resolved
Has there been anything definitive about the entropy thing? The last consensus I saw by anyone not potentially making money from a fix is that at best it's just forcing the processor to stay awake, decreasing battery life.
Saeviomage said:
Has there been anything definitive about the entropy thing? The last consensus I saw by anyone not potentially making money from a fix is that at best it's just forcing the processor to stay awake, decreasing battery life.
Click to expand...
Click to collapse
well by my testing before my motoactv went kaput it didnt affect the battery any noticeable amount, but it did solve some-to-all of the lag from switching launchers on the ClearDroid 1.2.0_T2 rom, i cannot make or update this mod-pack anymore because i dont like submitting a mod-pack that is untested, and since my motoactv went kaput i cannot test it anymore but if u have any questions feel free to ask and ill try to answer the best i can for now =)
not sure what is the right place to ask this... How does DPI change work? Does it mean the "system" screen resolution is changed? Let say, what is the "Full Screen" resolutions in 90/100/stock(120?) dpi's??? Where to read about it if it is not so simple???
yuiop0 said:
not sure what is the right place to ask this... How does DPI change work? Does it mean the "system" screen resolution is changed? Let say, what is the "Full Screen" resolutions in 90/100/stock(120?) dpi's??? Where to read about it if it is not so simple???
Click to expand...
Click to collapse
Dont worry its ok to ask here, since i made this app after all , i might as well answer how this works =)
well to make it shorter and more understandable to alot more people:
Yes, it is the overall resolution of the screen:
DPI (dots-per-inch) is more like the size range to view images/displays/graphics on ANY of your LCD/LED Screened devices including androids, I-craps(iPhones/ipods )(sorry i dont like apple too much, bad excperiences, dont get offended if u like it as its just my personal preferences), blackberries, windows phones, TV's, computer Monitors, etc:
the stock setting for HDPI phones (the more common screened ones now) is 240, say if u lower it, the images get smaller, if u raise it it gets bigger (maybe even too big for the screen to handle correctly);
but since the MOTOACTV has a smaller screen as u can obviously see (if u have one that is, as i dont know others posesions =P), its default for the stock rom is 120 (1/2 of HDPI if u notice the math) and 120 is as big as it should go cause say for example 130 dpi, it makes the images slightly too big for the screen, but slightly smaller values (100 is usually smallest for alot of peoples eyes for the watch, but for some people like me that like them a tad smaller for sharp small details, i put 90), but literally the smaller the amounts go, the smaller the images(and possible errors, i.e ES File Explorer crashes below 120 DPI untill u restore to 120+) , and for the smaller screen we have u cant go too big (121+), or too small (>=90-100), so i put those details of 90,100,and 120 (no 110 as it doesnt make too much of a difference by what i saw)
but there is (a) way(s) to check what DPI u are at currently:
METHOD1.check your build.prop file under /system/build.prop by doin these ADB commands (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb pull /system/build.prop
<EOC>
check somewhere using notepad for this line (NOTE: if u want to edit to push to your device use notepad++, search for it on google if u dont already have it, as regular notepad corrupts it)
ro.sf.lcd_density=(your current DPI is displayed here)
if u decide to change it that way and want to apply it MAKE A BACKUP!!!, then change it in notepad++ and save it, then goto the directory it is in in the terminal/command prompt and do (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb push build.prop /system/build.prop
adb shell chmod 644 /system/app/build.prop
adb reboot
<EOC>
METHOD 2: Any DPI Checking/changer app (there might be some good free ones, i.e. pimpmyrom has a density changer (DPI changer) that works the same as mine i think, it changes the DPI value in the Build.prop and it WILL stick over reboots, just not rom flashes (as it overwrites it and my change)
if u want to see how i did this(if u understand java/android applications) u can check This app on my github, its acually fairly easy and lightweight compared to others
https://github.com/kittleapps/MotoActvDPI
and the exact class that does this (using a library), is this
https://github.com/kittleapps/MotoA...om/KittleApps/app/motoactvdpi/MainScreen.java
as u can see it changes it to 90,100, and 120 quite simply (with root access of course)
and sorry for this long message but it explains not only your question, but possible future questions on how this app works =)
jkok said:
but there is (a) way(s) to check what DPI u are at currently:
METHOD1.check your build.prop file under /system/build.prop by doin these ADB commands (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb pull /system/build.prop
<EOC>
check somewhere using notepad for this line (NOTE: if u want to edit to push to your device use notepad++, search for it on google if u dont already have it, as regular notepad corrupts it)
ro.sf.lcd_density=(your current DPI is displayed here)
if u decide to change it that way and want to apply it MAKE A BACKUP!!!, then change it in notepad++ and save it, then goto the directory it is in in the terminal/command prompt and do (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb push build.prop /system/build.prop
adb shell chmod 644 /system/app/build.prop
adb reboot
<EOC>
METHOD 2: Any DPI Checking/changer app (there might be some good free ones, i.e. pimpmyrom has a density changer (DPI changer) that works the same as mine i think, it changes the DPI value in the Build.prop and it WILL stick over reboots, just not rom flashes (as it overwrites it and my change)
if u want to see how i did this(if u understand java/android applications) u can check This app on my github, its acually fairly easy and lightweight compared to others
https://github.com/kittleapps/MotoActvDPI
and the exact class that does this (using a library), is this
https://github.com/kittleapps/MotoA...om/KittleApps/app/motoactvdpi/MainScreen.java
as u can see it changes it to 90,100, and 120 quite simply (with root access of course)
and sorry for this long message but it explains not only your question, but possible future questions on how this app works =)
Click to expand...
Click to collapse
There is a 3rd method as well.
Method 3 = Install the Xposed framework and app settings apk found here: http://forum.xda-developers.com/showpost.php?p=44034334&postcount=2315
This will allow per app DPI settings rather than one global setting.
In order for this to work correctly, make sure you move both the Xposed Installer and App Settings apks to the phone after installation and reboot as well.
I like running some apps at 120, others at 100, 90, and even 70 w/ modded font sizes and this allows for all those combinations.
Artimis said:
There is a 3rd method as well.
Method 3 = Install the Xposed framework and app settings apk found here: http://forum.xda-developers.com/showpost.php?p=44034334&postcount=2315
This will allow per app DPI settings rather than one global setting.
In order for this to work correctly, make sure you move both the Xposed Installer and App Settings apks to the phone after installation and reboot as well.
I like running some apps at 120, others at 100, 90, and even 70 w/ modded font sizes and this allows for all those combinations.
Click to expand...
Click to collapse
that is true, but i didnt include that cause i was seeing people having issues with xposed-framework on the MOTOACTV on a few threads, and tbh i made this app+inlcuded in modpack before that method was usable for MOTOACTV (or gingerbread in general), thats kinda why i havent updated the modpack in a while (including the fact mine is damaged for some time now), i managed to fix mine up somewhat but it only turns on the backlight and no button combos work but to turn on backlight XD, so no fastboot recovery, boot-to-system, or quickboot :S and since the device is discontinued i cant get a real fix XD, so unless i personally test the things i put in this modpack, i cant make new versions to distribute for device stability reasons (e.g. in case it is corrupted and breaks someone elses device, as it is un-tested, since i dont have a device to test it on)
jkok said:
that is true, but i didnt include that cause i was seeing people having issues with xposed-framework on the MOTOACTV on a few threads, and tbh i made this app+inlcuded in modpack before that method was usable for MOTOACTV (or gingerbread in general), thats kinda why i havent updated the modpack in a while (including the fact mine is damaged for some time now), i managed to fix mine up somewhat but it only turns on the backlight and no button combos work but to turn on backlight XD, so no fastboot recovery, boot-to-system, or quickboot :S and since the device is discontinued i cant get a real fix XD, so unless i personally test the things i put in this modpack, i cant make new versions to distribute for device stability reasons (e.g. in case it is corrupted and breaks someone elses device, as it is un-tested, since i dont have a device to test it on)
Click to expand...
Click to collapse
Sorry to hear that. I personally haven't loaded the mod pack yet. Was looking into cherry picking parts of it when I saw the question on DPI. I thought it was a general question.
In any case, I personally have not had any issues with Xposed on my actv. What issues have you heard about?
jkok - thank you so much for the explanations. It's become more clear for me but I'm not so experienced in android/development so I have some more questions related to dpi on actv.
My practical interest in this is - to investigate the possibility to run igo primo on this device (for route planning/voice navigation) because I'm not happy with Motorola map application (walk/run outdoor mode). I have some ideas how to modify igo's data.zip for specific screen resolutions (at least I managed to make "custom 640x480" data.zip for primo 2.4.0 WM for htc DIAM100) but I need to know what is the "Full Screen" resoluton (for igo and other applications) in different dpi modes on actv (ClearD 1.2.0 rom currently, just in case). Is it the same - 176x220 for all dpi's (I don't think so as the size of icons/fonts/etc are different). So, the real question is - what is the screen resolution I need to set up in data.zip to try to run igo primo on motoactv. To know that I need to understand if dpi change affects the "full screen resolution" in motoactv/android. And, once more, sorry if the question looks stupid (already explained etc) as I'm not developer...
yuiop0 said:
jkok - thank you so much for the explanations. It's become more clear for me but I'm not so experienced in android/development so I have some more questions related to dpi on actv.
My practical interest in this is - to investigate the possibility to run igo primo on this device (for route planning/voice navigation) because I'm not happy with Motorola map application (walk/run outdoor mode). I have some ideas how to modify igo's data.zip for specific screen resolutions (at least I managed to make "custom 640x480" data.zip for primo 2.4.0 WM for htc DIAM100) but I need to know what is the "Full Screen" resoluton (for igo and other applications) in different dpi modes on actv (ClearD 1.2.0 rom currently, just in case). Is it the same - 176x220 for all dpi's (I don't think so as the size of icons/fonts/etc are different). So, the real question is - what is the screen resolution I need to set up in data.zip to try to run igo primo on motoactv. To know that I need to understand if dpi change affects the "full screen resolution" in motoactv/android. And, once more, sorry if the question looks stupid (already explained etc) as I'm not developer...
Click to expand...
Click to collapse
well im not familiar with those apps, as for the resolutions/dpi im not sure of that :S it could possible be found on google, as basic hdpi (240 dpi), usually is around 480*800, and 120 dpi is like the motoactv 220*176, so i guess there isnt a ratio it follows, just sizing of images maybee :S, but i also just became a developer more resently withing the last 2 years so im still learning
I based my work on MGC_3.2.045_RazerPhone2_V1 by BSG.
It's a working Modded Google Camera for stock rom (works on custom too) heavily improved.
• Requirements:
Camera2 API enabled.
Click to expand...
Click to collapse
Set: persist.camera.HAL3.enabled 1 into your build.prop or use this Magisk Module.
• Installation:
Install as normal apk, open it, enter to 'resolution & quality' and disable video stabilization. Restart the app (force close it or restart your phone).
Click to expand...
Click to collapse
• Changelog:
Based on MGC_3.2.045_RazerPhone2_V1 by BSG.
Changes by developer (BSG):
- Added custom saturation settings.
- Added custom denoise settings.
- Added option to restrict exposure time.
- Removed flash option due to constants sync issues.
Changes by me (v2F):
- Set default custom denoise parameters for Albus/Potter.
- Tweaked GcammoduleJNI (combined with BSG 6.1.021).
- Took Hot Pixels parameters from BSG 6.1.021.
- Took Spatial Gain Map from BSG 6.1.0.21.
- Fixed gray shutter issue.
- Fixed AF and TF for Albus/Potter.
- Added new round icon.
- Package name changed to avoid conflicts with other GCams.
* When you launch the app for first time,
enter to settings and forceclose the app.
If you don't do it firts shots will have a pixelated process.
Click to expand...
Click to collapse
• Important tips:
- Recommended settings for LOW LIGHT scenes (like night shots):
- Correction of auto-exposure HDR+: Increase exp. to 8 or Min. ISO.
- Restrict correction exposure: 1/4s.
- HDR+ parameters: Super High.
- Recommended settings for GOOD LIGHT scenes:
- Correction of auto-exposure HDR+: Off 8 or Increase exp. to 2.
- Restrict correction exposure: 1/4s.
- HDR+ parameters: Medium/High.
• Download link:
3.2(HDR+)Albus_v2F-Moonlightdrive
Thanks to:
BSG
Credits:
BSG, Moonlightdrive.
Reserved.
Is it for moto z2 play stock ROM ?
thx... first try: only slowmo doenst work...as far as i can see
@C4mine: yes, stock is 32bit!
:cyclops:
Installed on my z2 play but when I open, after swipe left on the "tutorial", it crashes, giving the message "cannot connect to camera". I tried reinstall, force closing, restart the phone, nothing works.
evandromon said:
Installed on my z2 play but when I open, after swipe left on the "tutorial", it crashes, giving the message "cannot connect to camera". I tried reinstall, force closing, restart the phone, nothing works.
Click to expand...
Click to collapse
You need to enable Camera2 API first, and when in the 'tutorial": rapidly change to photo mode. Don't stand more than a second in video mode cause it will crash/hang because video stabilization is not disabled.
can somebody post examples from this app and stock app, rooting this device is a pure mess, i would like to see is it worth it... thanks in advance
moonlightdrive said:
You need to enable Camera2 API first, and when in the 'tutorial": rapidly change to photo mode. Don't stand more than a second in video mode cause it will crash/hang because video stabilization is not disabled.
Click to expand...
Click to collapse
sorry for the dumb question, but how do I do this?
tried this on my redmi go force close upon clicking settings
samsungics1200 said:
tried this on my redmi go force close upon clicking settings
Click to expand...
Click to collapse
Go cry in the Redmi forum
I just tried it on Potter and focus isn't working on pictures, works on video. Also noticed that since bsg 3.2.045 v3.2 focus isn't working, in previous versions it works.
Fedray said:
I just tried it on Potter and focus isn't working on pictures, works on video. Also noticed that since bsg 3.2.045 v3.2 focus isn't working, in previous versions it works.
Click to expand...
Click to collapse
Can confirm AF and TF do work on Moto G5+ (Potter), my work is shared on Moto G5+ Camera development Telegram group (since Albus and potter shares same camera sensor: IMX362RS), this app was heavily tested by G5+ users (custom and stock users).
Be sure that your device is properly named (inside build.prop and default.prop) as a 'potter', it's needed due to Pixel phones uses different focus parameters, unlike Lenovo which uses ZAF, and modded gcams for these devices (a few others like Xiaomis too) needs to be modified/patched in order to focus.
In this case:
Code:
.method public BadTF()I
.locals 3
const-string v1, "[B]potter[/B]"
invoke-virtual {v1, v0}, Ljava/lang/String;->equals(Ljava/lang/Object;)Z
move-result v2
if-nez v2, :cond_0
const-string v1, "[B]albus[/B]"
invoke-virtual {v1, v0}, Ljava/lang/String;->equals(Ljava/lang/Object;)Z
move-result v2
if-nez v2, :cond_0
const/4 v2, -0x1
:goto_0
return v2
:cond_0
const/4 v2, 0x0
goto :goto_0
.end method
Long story short: if your device is named as 'potter' this must work. Hope it helps.:good:
moonlightdrive said:
Can confirm AF and TF do work on Moto G5+ (Potter), my work is shared on Moto G5+ Camera development Telegram group (since Albus and potter shares same camera sensor: IMX362RS), this app was heavily tested by G5+ users (custom and stock users).
Be sure that your device is properly named (inside build.prop and default.prop) as a 'potter', it's needed due to Pixel phones uses different focus parameters, unlike Lenovo which uses ZAF, and modded gcams for these devices (a few others like Xiaomis too) needs to be modified/patched in order to focus.
In this case:
Long story short: if your device is named as 'potter' this must work. Hope it helps.:good:
Click to expand...
Click to collapse
Can you help me with what lines need to tell potter? I'm on stock 7.0 and like I said it doesn't focus at all, only in videos.
This is what I have found in build.prop
ro.product.model=Moto G (5) Plus
ro.product.brand=motorola
ro.product.name=potter_retail
ro.product.device=potter
Nothing like that in default.prop
Edit: noticed that with hdr off focus works, when I enable it or set to auto then focus stops working
my hdr+ photos turn out purple.
moonlightdrive said:
Reserved.
Click to expand...
Click to collapse
my hdr photos turn out purple. And sometimes it does not work. I use J7 prime, i tested the app to see if my camera2api is enable or not, and this is enabled. You can help me? (Sorry for my bad english)
Abilrifor said:
my hdr photos turn out purple. And sometimes it does not work. I use J7 prime, i tested the app to see if my camera2api is enable or not, and this is enabled. You can help me? (Sorry for my bad english)
Click to expand...
Click to collapse
Go to you J7 prime forum and cry.
Link is down. Any chance we can get a mirror or something?
Confirmed not working properly on US Retail XT1710-01 Android Pie 9.0. Imahe has artifacts, settings crashes app, and video freezes up.
Knuxyl said:
Confirmed not working properly on US Retail XT1710-01 Android Pie 9.0. Imahe has artifacts, settings crashes app, and video freezes up.
Click to expand...
Click to collapse
Installation:
Quote:
Install as normal apk, open it, enter to 'resolution & quality' and disable video stabilization. Restart the app (force close it or restart your phone).
Click to expand...
Click to collapse
Read OP installation instructions first. You must do that (it's mandatory), otherwise you will face those issue you described. This app is widely tested on this device.
Edit: do not forget to enable API2.
Knuxyl said:
Confirmed not working properly on US Retail XT1710-01 Android Pie 9.0. Imahe has artifacts, settings crashes app, and video freezes up.
Click to expand...
Click to collapse
Neither BR Retail Pie, has the same problems as mentioned.
I'm on US retail Pie as well and I get artifacts in the preview and on photographs. Stabilization was disabled from before the upgrade (which was when it worked just fine). I cleared app data, but the artifacts persist and the app crashes when I try to go to settings. Please excuse the fact that I'm uploading screenshots of the photographs; I haven't found a quick way to erase the location metadata from the originals and I figured the screenshots wouldn't have that in the first place. The windowsill photograph was taken before clearing data (i.e. with stabilization disabled) and the one of wood afterwards (i.e. with stabilization enabled).