yashsingh1/xdaforums huggingface dataset:
[One (M9) General] Ramsey:
Yes it is, if you're talking about raw pictures.

---------- Post added at 12:57 PM ---------- Previous post was at 12:48 PM ----------

Pics of flowers in JPG (with denoise tweak in build.prop): https://drive.google.com/open?id=0B3vmznAFra6gZF9wdXQwMUZ0cjg

Same pic in a raw to jpg file: https://drive.google.com/open?id=0B3vmznAFra6gS0lzb3RDOVFSWFE

Download for full resolution.

Raw is super nice with excellent accurate colors. Look at how much brighter it is! way better in my opinion.

I wish we could shoot like that, I wish HTC would remove almost all the processing (lol). This camera doesn't have very good white balance, it tends to go towards green and red, depending on the situation.

My settings for the 2.10 camera now with denoise tweak, contrast -0.5, saturation 0 (I brought it back to 0 from -0.5), sharpness 0 (I'll be turning this to -0.5).

Btw, the JPGs that come out with the Raw file have the denoise tweak active (no noise reduction :) ) so that's awesome!

Edit: Sorry, I didn't share the pics properly, it should be fine now.
[One (M9) General] defcomg:
[MENTION=535051]RSK01[/MENTION]

M9 cam not so bad i digg it:p

Snaps from XDA by RSK01 by defcomk, on Flickr

Snaps from XDA by RSK01 by defcomk, on Flickr
[One (M9) General] peca_slo:
Hdr

View attachment 3438535

View attachment 3438537

RAW + PSX

View attachment 3438538

View attachment 3438539
[One (M9) General] defcomg:
whats the iso and exposure time of second hdr image ?
[One (M9) General] peca_slo:
Iso bouth max, exposure normal (didnt touch)
[One (M9) General] defcomg:
I meant to say what does the exif info say on those parameters. I like the way the second hdr came out in the shadow areas I usually end up with a green discolouration
[One (M9) General] peca_slo:
Hope this helpView attachment 3438653
[One (M9) General] Aleki:
How are you guys managing such nice photos? I went back to my M7 after a few frustrating weeks of shenanigans with the M9. Does SW 2.8 really impact the camera that much? My Sprint phone only updated to 2.6.6(cant remember the correct number) Some photos come out really nice; but most are either mediocre or disasterous.

PS: The sensor has a strong tendency to smear photos in low light while in viewfinder(compared to the M7 camera), is this inherent of the hardware, or software?
[One (M9) General] Ramsey:
If you're rooted, add the following lines to the end of build.prop (found under System):

persist.camera.qcwnr.enabled=0

camera.eis.enable=0

The first line removes most noise reduction in the HTC camera app.

The second line disables the EIS.

Also, limit ISO to 800 so it has more effect. You shouldn't get smeared pictures after that.

If you're not rooted, download Snap Camera or Freedcam and remove the Denoise checkmark. That'll also disable noise reduction but then you're forced to use those apps to remove noise reduction as it will only work inside those.
[One (M9) General] Aleki:
Thanks, I actually have a replacement; don't want to open the box, as I was thinking about selling it and just sticking with the M7, but still curious about the difference in ease of use. Would you say the changes are significant enough to make the camera comparable to the G4/S6? What I like about those cameras is how you don't have to fiddle with the settings to get a good shot. Unlike the M9, theyre primed as a point-shoot(which is why I liked the M7). Also, does the camera still get overwhelmed with intense lights? For example, the LED's on my washer/dryer are so bright, that it bleeds into the entire photo

I want to really like this phone, as it is much smoother than my M7; but the camera was a serious letdown for me
[One (M9) General] muayyadf1:
[MENTION=994565]Ramsey[/MENTION] why would you disable EIS? Wouldn't this make video worse ?
[One (M9) General] Ramsey:
My wife had the M7 actually and we despised its camera, it was bad and worse than a cheap digital camera. The phone was awesome though. The camera on the M9 is way better and I find it better than on the S6. I am not a fan of the Samsung's post processing, even in their mirrorless line up. When you modify the M9 a bit the quality is really good. You can just use one the apps I mentioned and then you won't have to root or tweak the phone.

You could also shoot raw and get quality that surpasses the G4.

The G4 has the best overall camera for point and shoot, including manual mode but the overall software of the phone is very very buggy (The M9 is very stable in that area, even more than the S6). Don't listen to those saying the bugs have been fixed, it's not true. You may get lucky and get a good one but more than half of them are experiencing so many issues, touchscreen issues, wifi dropping, phone restarting/failing, major lagging, phone charging/discharging weirdly, just to name a few, go check the forum. LG is slow to release updates just like Samsung. I prefer HTC in this field, they release quite a lot of updates.

I wanted to get a G4 because of its camera but the amount of people returning that phone for issues led me to forget about it, especially in the US and Canada.

Also it's too big for my hand. I had an Oppo Find 7a and had to sell it as it was too big to use with one hand. The real test is when you're outside of your house on the go, then you'll know if a phone is good for you or not.

The M9 doesn't get overwhelmed with lights, mine was fine. Make sure that you wipe the glass on the rear camera, always keep it clean when you're about to take pictures. I point it and let it focus on its own for better metering. If I notice a scene is dark, I focus on where I want and the metering will help increase the light in that area. If I want more light in a darker scene, I lower shutter speed. The M9 has a great camera. Its software is great but needs to be optimized in some areas, I find the scrolling is bad and not like the S5 (I have the Galaxy S5 also as my main phone) or the iPhone. It scrolls for a long distance without that quick stop that Google implemented a while ago. It also has slow pinch to zoom, my S5 is faster and more responsible with touching, scrolling, and pinch zooming. The M9 is really slippery also and I don't like that.. With a case it's too thick.

---------- Post added at 10:27 AM ---------- Previous post was at 10:25 AM ----------

No idea its effect on videos but I disabled it as per the suggestion of this thread.

I find this phone has really good stabilization, once I disabled EIS, and I'm not joking but I feel like it has OIS. I am able to use slow shutter at 1 second without blurring, which is really great!

I don't like digital stabilization as it crops videos, not sure what it does in this phone, I haven't tested.
[One (M9) General] fmedrano1977:
What tripod, if any, are some of you using?

HTC One (M9)
[One (M9) General] hamdir:
2.10.401.1 camera samples:

Auto mode, auto focus, sharpness -0.5

Full digital zoom

HDR

Auto mode, auto focus, sharpness -0.5

HDR

RAW, processed in Photoshop

Tips for the 2.10.401.1 base:
[One (M9) General] Ramsey:
I'm running latest AT&T stock, firmware 2.6 (Android 5.1).

Should I pay for S-off and update to firmware 2.10? or it's the same thing?

I'd rather stay stock as much as possible.

Do you feel any difference with the camera with that firmware?
[One (M9) General] fmedrano1977:
So 1.40 still remains the firmware to run for best pics?

HTC One (M9)
[Moto X Q&A] Mexickano:
I'm on lollipop by AICP team, my issue is that some 3 days ago I saw how my device is locked and it awake in clock, it doesn't turn off/lock again, just black screen and the white digital clock, any idea? Any of you are suffering the same?

Thanks in advance, excuse my english, isn't my nat lang.
[Moto X Q&A] fury683:
Sounds like Daydream or screen saver to me.
[Moto X Q&A] Mexickano:
What is DayDream?
[Moto X Q&A] fury683:
It's a setting to show the clock when the phone is charging or docked. In the stock 4.4.4 ROM on my XT1060 it is in Settings > Display > Daydream.

You can change what is shown (clock, Pandora and photos appear for me. You may have more or less), and change when daydream is activated at the bottom. The options are Docked, Charging or Either (both).
[LG Optimus G Pro] t3chwizard:
***OP UPDATED***

I have the necessary APKs and other files to make a flashable zip, however whenever I try to flash it it succeeds but when I click on quickremote, the app force closes on me and will not load. How can we successfully get this to work on lollipop? I have posted several times in the forums but nobody seems to care about helping get this done.

Please see my other thread with a logcat I have pasted in pastebin related to the issue I am experiencing if anyone cares. http://xdaforums.com/showthread.php?t=3044306
[LG Optimus G Pro] t3chwizard:
I updated the OP
[Xposed General] Mikanoshi:
com.android.server.*

I know that these classes have to be hooked in handleLoadPackage for lpparam.packageName == "android", but sometimes there are several processes ("system:ui" for example) that contain this package and hooks fail even from handleLoadPackage.

Now I'm using this code, is it correct?

if (lpparam.packageName.equals("android") && lpparam.processName.equals("android")) { ... }

Resource hooks

They are just not working. Well, most of them. Using fwd or DrawableLoader doesn't matter. No errors shown in log. It's not just a problem with some packages. Status bar icons, action bar icons, etc, etc - I can't replace 90% of them, exact same hooks were working on Kit Kat.

For example, png drawable is used only in manifest and in actionbar ( actionbar.setIcon(iconResId) ). With a hook this icon is replaced in launcher, but not in actionbar.

Starting Xposed binary version 60, compiled for SDK 21
Phone: HTC One (HTC), Android version 5.0.2 (SDK 21)
ROM: LRX22G release-keys
Build fingerprint: htc/htc_europe/m7:5.0.2/LRX22G/482424.2:user/release-keys
Platform: armeabi-v7a, 32-bit binary, system server: yes
SELinux enabled: yes, enforcing: no
[Xposed General] agentdr8:
Noticed that as well. Some resources can be replaced, others it's like they're just silently ignored. I'm guessing maybe the ART optimizations are the culprit?

There's a thread about it here. I'm sure [MENTION=4419114]rovo89[/MENTION] will chime in when he's had time to take a look. As a workaround, you could always find the method that's setting the original drawable and replace it there; that seems to work for me in most cases.
[Xposed General] rovo89:
So you're saying that there are situations with lpparam.packageName == "android" and lpparam.processName <> "android"? That would explain a couple of other issues. If you could find out a good way to reproduce this, it could be quite helpful.

Depending on the situation, I will have to see how to handle it. Checking for package name "android" is a pretty common pattern to ensure you're in the system server (which I even recommend myself!), so ideally it should stay correct even without the additional checks you suggested.
[Xposed General] C3C076:
Yes, I can confirm this seems to be the case. Haven't got a chance to debug which process comes with packageName == "android" apart from "android" process itself, but when that happens, classLoader cannot find classes that are typically available within "android" package, which is logical. The other process that has packageName "android" is something else with no access to those classes.
[Xposed General] Mikanoshi:
Oh, and rarely soft reboot after module activation ends like this :eek:

E/Xposed(10834): Error -32 while adding app service user.xposed.app
E/Xposed(10822): Zygote service is not running, Xposed cannot work without it
[Xposed General] rovo89:
I would like to concentrate on the bigger issues first. Yours can probably be solved by another reboot. ;)

So after some research, grepping the AOSP code and so on, it seems that the "system:ui" process is only used by the PackageManagerService. Maybe more will follow in the future. For some reason, the process seems to be called "android:ui" though once it has been started. It's running with UID 1000, but in the system_app SELinux context.

I would like to understand some more things about this before making a decision. It seems that there can now indeed be processes with package name "android" that aren't the system_server. Without breaking existing modules, I think I could only block handleLoadPackage() for these. Maybe it would also make sense to add a new handleLoadSystemServer() method. That would avoid the need for checks, especially if only system services are hooked. For backward-compatiblity, handleLoadPackage() could still be called for package "android", but modules would produce error messaages if they don't check the process name. Or there could be a compatiblity break at this point, requiring all modules that hook system services to adopt the new API.
[Xposed General] Mikanoshi:
I don't mind checks :) Almost every module that hooks system classes requires an update for 5.0 anyway.

Huge issues for me now are broken resource hooks and problems with installing apks (sometimes it takes 3-5 tries to install and then soft reboot just to test interface changes).
[Xposed General] rovo89:
Most likely, this is the reason why the ChooserActivity runs in the "android:ui" process now:

https://github.com/android/platform...40#diff-30afe08a44bf548c7cc9116a473f8bdfL2798

It used to declare multiprocess=true, which meant that the activity was started in the caller's process. Now it's started in a separate process, where ":ui" is relative to the package name, not the applications's default process name (that would be "system").

There are also other activities with similar attributes defined, even in KitKat. If someone has a bit of time at their hands, they could try to check whether handleLoadPackage() is also called for package == "android" and process != "android" on KitKat ROMs for those other activities. It wouldn't be as noticable as it is on Lollipop because the system services that most modules hook there were available with the boot class path.

Anyway, now we know that there are legitimate usages of the "android" package for other things than the system_server. These usages are very limited though. The activities use the boot classloader, so hooking methods from initZygote() would (still) work for them. What if I set the packageName for these apps to "system" instead? So modules checking for "android" as package name could be sure it's the system_server then. Modules which need to do something for the android:ui process could simply check for "system" as package name. Any complaints?
[Xposed General] pyler:
Good solution... Ship it :)

But I believe majority of actively developed modules are already fixed for this specific case.
[Xposed General] wanam:
Great idea, no complaints here.
[Xposed General] pyler:
Whike fixing this, maybe you can try to look why appInfo is null for "android" package.
[Xposed General] rovo89:
That's very simple to answer: https://github.com/rovo89/XposedBri...de/robv/android/xposed/XposedBridge.java#L245

There's simply no ApplicationInfo object (yet), it's constructed later when the PackageManagerService is running. I could construct a fake object, but there are hardly any fields that could be filled with proper values.
[Xposed General] pyler:
atleast flags field could be filled, or not? just do copy of real object for android, which any normal app can get.

since we talk about this, is this doable or Xposed starts too soon for these values?
[Xposed General] defim:
Old modules which use "android" are incompatible...

To be compatible i have then to check "system" and "android" - this is not better than check for package& process name
[Xposed General] pyler:
system is for *:ui processes and we mostly care about android only.
[Xposed General] defim:
Who is "we" and whats the source of "mostly" :D

I have to say that i'm using "android" for <21 and so it seems i have to use different package names depending on Xposed version
[Xposed General] rovo89:
"real object for android" => you mean the one that I said doesn't exist at the time the system_server is starting up, as the PackageManagerService is not running yet? ;)

No idea about your other suggestion, I'm currently looking mainly into crashes etc., API extensions have to wait...

I was talking about "other things than the system_server", i.e. the process for ChooserActivity etc. This process is hardly used, I'm not even sure if it existed in previous versions. Only for this process, the package name is faked to be "system". The system_server, which is way more widely used, will keep package name "android". So I don't expect a single module to break.
[Xposed General] defim:
If no update for older modules is needed its great :good:
[Xposed General] nirmal0721:
can i use it on samsung device running cm 12

can i use it on samsung device running cm 12
[Xposed General] Mikanoshi:
It's totally different, this method is parsePackageLite(File, int) on 5.0, but Xposed has parsePackageLite(String, int)

Is it the last alpha?
[Xposed General] tonyp:
API 62, so I think it is, yes.
[Xposed General] pyler:
Can we since API 62 remove check for processName without any worries? :)
[Xposed General] tonyp:
Btw, the reason I wrote my problem is similar is that my module fully works and the hook does what it's supposed to do - but it still shows the error message in the log, so at some point it doesn't find the method but at another it does.
[Xposed General] Mikanoshi:
This is the point))

https://github.com/rovo89/XposedBridge/blob/master/src/android/content/res/XResources.java#L148
[Xposed General] tonyp:
I see, but then there's no possible workaround currently, correct? I could catch the error and suppress it, but I guess I prefer not to do that in order to see actual errors for people who use different ROMs.

I've seen quite similar errors in my log from Gravitybox, maybe [MENTION=4419114]rovo89[/MENTION] can do something about it in the next alpha.
[Xposed General] Mikanoshi:
I've seen this error too, but my mods are working fine, so no idea))
[Xposed General] tonyp:
Yes, it certainly works fine here, too.

I guess it's just another alpha version issue. Anyways, thanks for the help and feedback!
[Xposed General] Mikanoshi:
initZygote:

findAndHookMethod("android.media.MediaPlayer", null, "pause", new XC_MethodHook() {
@Override
protected void beforeHookedMethod(final MethodHookParam param) throws Throwable {
XposedBridge.log("MP paused!");
Context mContext = (Context)XposedHelpers.callMethod(param.thisObject, "getContext");
}
});

04-02 19:27:05.014: I/Xposed(11413): MP paused!
04-02 19:27:05.024: E/Xposed(11413): java.lang.NoSuchMethodError: com.sonymobile.music.a.p#getContext()#bestmatch
04-02 19:27:05.024: E/Xposed(11413):	at de.robv.android.xposed.XposedHelpers.findMethodBestMatch(XposedHelpers.java:271)
04-02 19:27:05.024: E/Xposed(11413):	at de.robv.android.xposed.XposedHelpers.findMethodBestMatch(XposedHelpers.java:284)
04-02 19:27:05.024: E/Xposed(11413):	at de.robv.android.xposed.XposedHelpers.callMethod(XposedHelpers.java:947)
04-02 19:27:05.024: E/Xposed(11413):	at com.sensetoolbox.six.mods.ControlsMods$12.beforeHookedMethod(ControlsMods.java:420)
04-02 19:27:05.024: E/Xposed(11413):	at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:636)
04-02 19:27:05.024: E/Xposed(11413):	at android.media.MediaPlayer.pause(Unknown Source)
04-02 19:27:05.024: E/Xposed(11413):	at com.sonymobile.music.a.p.pause(WatchedMediaPlayer.java:44)
04-02 19:27:05.024: E/Xposed(11413):	at com.sonymobile.music.a.a.f(AudioPlayer.java:410)
04-02 19:27:05.024: E/Xposed(11413):	at com.sonyericsson.music.localplayer.a.b(LocalPlayer.java:1046)
04-02 19:27:05.024: E/Xposed(11413):	at com.sonyericsson.music.localplayer.a.pause(LocalPlayer.java:1026)
04-02 19:27:05.024: E/Xposed(11413):	at com.sonyericsson.mediaproxy.playerservice.manager.PlayerService.pause(PlayerService.java:209)
04-02 19:27:05.024: E/Xposed(11413):	at com.sonyericsson.music.proxyservice.worker.aa.l(Worker.java:1170)
04-02 19:27:05.024: E/Xposed(11413):	at com.sonyericsson.music.proxyservice.worker.aa.handleMessage(Worker.java:389)
04-02 19:27:05.024: E/Xposed(11413):	at android.os.Handler.dispatchMessage(Handler.java:102)
04-02 19:27:05.024: E/Xposed(11413):	at android.os.Looper.loop(Looper.java:155)
04-02 19:27:05.024: E/Xposed(11413):	at android.os.HandlerThread.run(HandlerThread.java:61)

WTF? :eek:
[Xposed General] Falseclock:
come on man!

android.media.MediaPlayer does not extend any activity or view :o
[Xposed General] Mikanoshi:
So? Why Xposed hooks extended class and not the base one? getContext() is a private method in MediaPlayer class.
[Xposed General] Falseclock:
are you sure?

http://grepcode.com/file/repository...r1/android/media/MediaPlayer.java#MediaPlayer

---------- Post added at 12:50 AM ---------- Previous post was at 12:37 AM ----------

what if hook "create" method and store context from there?
[Xposed General] Mikanoshi:
Yes, it's HTC :) I just want to call this method... It returns context that was saved in create()/setDataSource() and gets it if it's null (using very questionable async code :D).

param.thisObject.getClass() returns the wrong class and Xposed searches method there.

View attachment framework.jar

This works perfectly:

Context mContext = (Context)XposedHelpers.findMethodExact(findClass("android.media.MediaPlayer", null), "getContext").invoke(param.thisObject);
[Xposed General] C3C076:
Xposed considers private methods of actual class. Private methods of super classes are skipped in search loop.

https://github.com/rovo89/XposedBri...e/robv/android/xposed/XposedHelpers.java#L249
[Xposed General] Mikanoshi:
So callMethod() cannot be used for any private method, because it may fail if hooked class is extended? You learn something new every day)
[Xposed General] Falseclock:
hahaha.... that is why I was unable to hook private method of android.telephony package several month ago and had to find another way to get object's data
[Xposed General] Mikanoshi:
I never considered types of methods/vars and this is the first time I encounter such error...
[Xposed General] rovo89:
There was a lengthy discussion about whether it should also look for private methods in super-classes: https://github.com/liudongmiao/XposedBridge/issues/1

My decision was not to include them, as there could be even weirder issues otherwise.
[Xposed General] Mikanoshi:
Xposed Framework 3.0 alpha 4, cannot replace holo gradient background. Hooked background_holo_dark color and drawable in android package using setSystemWideReplacement() - no changes. Can anyone confirm?

Android 5.0.2 on HTC.
[Xposed General] Mikanoshi:
Ok, found the problem. It was like that in previous Xposed versions too. If you replace a drawable and app uses that drawable directly - everything is ok, but if it's a part of some other resource, e.g. a layered drawable, then replacement will not work, you'll have to replace a layered drawable.
[Xperia SP Q&A, Help & Troubleshooting] bhrajishna:
MODEL: Sony xperia SP(C 5302)

I tried flashing CM12 by huashan on xperia sp. I forgot to wipe data and davlik cache before flashing custom kernel.

Now i am able reboot my phone but unable to go though initial setup completely and is getting crashed.

i tried going to CWM mode on booting phone again but unable to do that. i cant use my phone noe

please help me

Thanks in advance
[Xperia SP Q&A, Help & Troubleshooting] Razvan:
Sir,

Please wait until mods will move this thread to the device specific forum for more relevant answers.

Stand by

Good luck
[Xperia SP Q&A, Help & Troubleshooting] Xa7adu:
If you want to flash back to CM11 immediately, enter fastboot mode by pressing volume up+power botton and in the meantime, connecting the phone to your computer when power off. Then use your fastboot to flash in a kernel with a kitkat recovery.
[G3 Q&A, Help & Troubleshooting] mps42:
Hi all i want to know if my lg g3 d855 support 4g lte or not ?

D855 is international version of lg g3

thanks :)
[G3 Q&A, Help & Troubleshooting] joooe:
What the hell?

Google it.

LG website has a page for the D855 with its technical specs, for god sake!
[G3 Q&A, Help & Troubleshooting] fire6water:
Yes it does. Use it on atf and T-Mobile with 4g.