Asus does not care at all

24

Comments

  • Which 100 dollar phone takes better pictures, or a 200 dollar phone for that matter? I understand that you want a better camera and it's ok. Who doesn't? But you're trying to insult our camera performance to make your point by saying that basically all other phones are better. This is is not true from an objective point. If you were to make some real comparisons with other manufacturers, then you would notice that our camera is a lot better than you think. Just watch all those comparisons that are already available from medias and youtubers.

  • Ohhhhhhh????? taught him a lesson.

  • Seems like you got the device gifted and did not buy. That you are such a fan boy. Let me do the talking with the dev. Do not need your expert opinion.

  • This isn't the place as you expect it to be kid.... Do people in here talk to devs alone, it's a forum for discussion dude don't be soo mean.

  • @Anders_ASUS here is the problem with the device.

    Confirm by micky387

    strings com.qti.chi.override.so | grep "system"

    system/lib/DataSet/ispDB/ASUS_UNDI_ZOOM.bin


    there is desperately a treble violation

  • Yeah because i am not here to please him a earn a rog 2 phone like you. So i am good. Keep trying hard may be you will get a rog 2 someday. Youtubers are the last people to belive as they do paid promotions. But thats for sensible people. You can keep trying for the rog 2.

  • Oh god seriously u freakin kids have these intention to do so, and that's why you got that thought so please, enough of our conversation. Why would i even think of that fool.????

  • S4tS4t Level 2

    @Anders_ASUS GCam was working on Pie. It was broken with the upgrade to Android 10. Modders already have it working on Android 10 on OnePlus and Xiaomi phones, but on ASUS Android 10, something is stopping the background processing of the image.

    tl;dr: Something is wrong and it's only affecting ASUS users running Android 10.

    I own and directed users to this device via my GCam repo and telegram channel, created and maintain the XDA threads for both the ZF6 and ROG2, and do my best to help by being an admin on the telegram group for this phone and a moderator on a (unofficial) sub-reddit. I'm probably biased, but since ASUS can't match Google's quality, I think GCam is important.

    I understand that you can't directly work on this, but if the attitude is "everything is fine with our camera" and "we don't even know what GCam is", then I guess current and possible new owners should be warned.

    But maybe I'm jumping into conclusions too quickly, maybe this Android 10 update was rushed due to some deadline and we should give ASUS some time to fix the issues. I still have hope that my Christmas/new year photos won't lack detail and be blurry, after all that's why I bought a new phone.

    ---

    Edit: Some comments were posted while I was writing this one.

    I hope ASUS and their employees don't go the "OnePlus way". For years they insisted they had a good camera and all criticism was an "attack" from hatters, not an opportunity to improve. Eventually they "saw the light", understood that they camera wasn't the best and started improving it.

    To fix a problem, we must first admit there's a problem. The quality of ASUS camera app isn't the best. It doesn't retain as much detail, performance in low light is bad, and things like HDR Enhanced are even close to what brands like Google offer. It records 4K video, but it's limited to... 5 minutes (maybe because of the heat? I'm freezing with 4ºC, so I hope there's another reason for this limit).

    Some of these problems could be bypassed if 3rd party cameras were better supported (not even talking about GCam). For example, not exposing 48MP to other apps is a mistake in my opinion. Forcing users to use another app to record 4k video for more than 5 minutes is another mistake.

  • @gunmanrishi Sorry to say, but your tone and attitude is a bit harsh. If you do some proper research you'll find a Gcam for Android 10, check this threat - post from 2019-09-29, 10:32PM. It's not perfect, but not too bad: https://forum.xda-developers.com/zenfone-6-2019/themes/asus-zenfone-6-google-camera-apk-gcam-t3932748/page23

    I hope it helps.

  • Buddy that's a old gcam we have all used. We are talking about the gcam 7.2 which works for all the devices on android 10. And i am sorry for being harsh but asus has been a bag full of excuses for a long time. I have also shared the exact problem on this post read that. And people like nishant 005 who are trying to be super nice and don't understand 5% of this device are the reason why i became harsh. I created this thread with a reason i am myslef a dev for custom roms so i have a good idea of this device. Thank you for sharing link. I am a admin for the 6z official group on telegram.

  • U were harsh before my conversation. That's the one he meant, better you understand things properly and stop getting me into trouble.

  • VS-KRVS-KR Level 4
    edited November 2019

    What the hell is happening here, since 2-3 days there are some nervousness on this forum, keep calm and relax !

  • @Anders_ASUS this might help you.

    micky387, [20/11/19, 11:03 pm]

    [In reply to Deborshi Bhattacharya]

    actually, all blobs are stored in both system/lib(lib64) and vendor/li(lib64) but the camera FW (.bin) stored in system. Their need to store their FW into Vendor for treble


    micky387, [20/11/19, 11:05 pm]

    [In reply to Deborshi Bhattacharya]

    i dont know but in all case, treble/apex dislike 

    11-20 14:33:13.071 10623 10623 F DEBUG  : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

    11-20 14:33:13.071 10623 10623 F DEBUG  : Build fingerprint: 'asus/WW_I01WD/ASUS_I01WD:10/QP1A.190711.005/17.1810.1910.68-0:user/release-keys'

    11-20 14:33:13.071 10623 10623 F DEBUG  : Revision: '0'

    11-20 14:33:13.071 10623 10623 F DEBUG  : ABI: 'arm64'

    11-20 14:33:13.071 10623 10623 F DEBUG  : Timestamp: 2019-11-20 14:33:13+0100

    11-20 14:33:13.071 10623 10623 F DEBUG  : pid: 915, tid: 929, name: HwBinder:915_2 >>> /vendor/bin/hw/[email protected]_64 <<<

    11-20 14:33:13.071 10623 10623 F DEBUG  : uid: 1047

    11-20 14:33:13.071 10623 10623 F DEBUG  : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------

    11-20 14:33:13.071 10623 10623 F DEBUG  :   x0 0000000000000000 x1 00000000000003a1 x2 0000000000000006 x3 0000000000800000

    11-20 14:33:13.071 10623 10623 F DEBUG  :   x4 07203d3635000000 x5 07203d3635000000 x6 07203d3635000000 x7 00008035363d2007

    11-20 14:33:13.071 10623 10623 F DEBUG  :   x8 0000000000000083 x9 7e8d367c5d89e854 x10 0000007e029fab50 x11 000000000000005b

    11-20 14:33:13.071 10623 10623 F DEBUG  :   x12 0000000000000010 x13 0000000000000003 x14 0000000000000008 x15 0000ade0bc698dc9

    11-20 14:33:13.071 10623 10623 F DEBUG  :   x16 0000007e0530ae68 x17 0000007e052e8cc0 x18 ffffffffffffffff x19 0000007df8d18bb8

    11-20 14:33:13.071 10623 10623 F DEBUG  :   x20 0000007e00f863b1 x21 0000007e029fc020 x22 00000000ffffffff x23 0000007e05762068

    11-20 14:33:13.071 10623 10623 F DEBUG  :   x24 0000007e0575f010 x25 0000007e029fbaa8 x26 0000000000000000 x27 0000000000000001

    11-20 14:33:13.071 10623 10623 F DEBUG  :   x28 0000000000000000 x29 0000007e029fb0e0

    11-20 14:33:13.071 10623 10623 F DEBUG  :   sp 0000007e029fb0c0 lr 0000007df8b90658 pc 0000007e052e8cc8

    11-20 14:33:13.093 10623 10623 F DEBUG  : 

    11-20 14:33:13.093 10623 10623 F DEBUG  : backtrace:

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #00 pc 00000000000cdcc8 /apex/com.android.runtime/lib64/bionic/libc.so (tgkill+8) (BuildId: be077ff7dde73cd4a2c582cf1140485f)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #01 pc 000000000007c654 /vendor/lib64/hw/com.qti.chi.override.so (ExtensionModule::Flush(void*)+212)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #02 pc 00000000000db6ac /vendor/lib64/hw/com.qti.chi.override.so (Usecase::FlushAllSessions(Session* const*)+204)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #03 pc 0000000000067e2c /vendor/lib64/hw/com.qti.chi.override.so (CameraUsecaseBase::ExecuteFlush()+124)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #04 pc 000000000006fa20 /vendor/lib64/hw/com.qti.chi.override.so (AdvancedCameraUsecase::ExecuteFlush()+32)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #05 pc 00000000000db2f4 /vendor/lib64/hw/com.qti.chi.override.so (Usecase::Flush()+356)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #06 pc 000000000007c348 /vendor/lib64/hw/com.qti.chi.override.so (ExtensionModule::OverrideFlush(camera3_device const*)+368)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #07 pc 0000000000074070 /vendor/lib64/hw/com.qti.chi.override.so (chi_override_flush(camera3_device const*)+40)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #08 pc 0000000000110cc0 /vendor/lib64/hw/camera.qcom.so (CamX::flush(camera3_device const*)+296)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #09 pc 0000000000024d04 /vendor/lib64/[email protected] (android::hardware::camera::device::V3_2::implementation::CameraDeviceSession::flush()+140) (BuildId: f22417a0d3d88ab58c6b20e7fb3bfd18)


    micky387, [20/11/19, 11:05 pm]

    [In reply to Deborshi Bhattacharya]

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #10 pc 0000000000025ff8 /system/lib64/vndk-29/[email protected] (android::hardware::camera::device::V3_2::BnHwCameraDeviceSession::_hidl_flush(android::hidl::base::V1_0::BnHwBase*, android::hardware::Parcel const&, android::hardware::Parcel*, std::__1::function<void (android::hardware::Parcel&)>)+152) (BuildId: 72e587fb8029881cfaf267ea0c622f7b)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #11 pc 000000000002dcec /system/lib64/vndk-29/[email protected] (android::hardware::camera::device::V3_5::BnHwCameraDeviceSession::onTransact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+1444) (BuildId: 5766c3b0abfaf6f457a479045f4c4144)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #12 pc 00000000000825f4 /system/lib64/vndk-sp-29/libhidlbase.so (android::hardware::BHwBinder::transact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+68) (BuildId: a97cf35da82e6d0531f993d9f4b53c49)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #13 pc 0000000000085ecc /system/lib64/vndk-sp-29/libhidlbase.so (android::hardware::IPCThreadState::getAndExecuteCommand()+1036) (BuildId: a97cf35da82e6d0531f993d9f4b53c49)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #14 pc 00000000000870d4 /system/lib64/vndk-sp-29/libhidlbase.so (android::hardware::IPCThreadState::joinThreadPool(bool)+96) (BuildId: a97cf35da82e6d0531f993d9f4b53c49)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #15 pc 0000000000095a54 /system/lib64/vndk-sp-29/libhidlbase.so (android::hardware::PoolThread::threadLoop()+24) (BuildId: a97cf35da82e6d0531f993d9f4b53c49)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #16 pc 0000000000013600 /system/lib64/vndk-sp-29/libutils.so (android::Thread::_threadLoop(void*)+288) (BuildId: df1cb265136d101bd3885cc21684f5cf)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #17 pc 00000000000e1100 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36) (BuildId: be077ff7dde73cd4a2c582cf1140485f)

    11-20 14:33:13.093 10623 10623 F DEBUG  :    #18 pc 0000000000083ab0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: be077ff7dde73cd4a2c582cf1140485f)

    11-20 14:33:13.166 1372 1372 E /system/bin/tombstoned: Tombstone written to: /data/tombstones/tombstone_00

  • Yeah, right. You're telling them they're bunch of kids and they didn't bought their phones because they don't agree with you? Good thinking. You are admin of some Telegram group... So? Go seek attention in there and spare us the trouble dealing with you. A mod made everything clear for you. I find camera performance good enough. I knew what I buy however it seems it doesn't apply to all of us.

    Something's wrong with Treble support? Create a proper bug-reporting thread and act accordingly.

  • S4tS4t Level 2

    Good enough compared to what?

    Here's a hand held test from the stock camera app on Android 10 (night mode) and a broken, unoptimized GCam (night sight):

    Stock:

    Google Camera (again, noisy and full of problems due to the Android 10 update):

    Let's zoom in a bit. Stock:

    Google Camera:

    Let's look at the small tree. Stock:

    GCam:

    ---

    I don't expect ASUS to compete with Google, but Android 10 broke GCam and now we have a problem.

    Something on Android 10 is stopping GCam's background image processing. It works on Android 10 from brands like OnePlus and Xiaomi.

  • Yah even i don't have any idea abt the issue but when i used gcam in A9 it was same as the stock cam. But now i can see a difference in yours, that's why i didn't even care about gcam ??

  • Thats the whole point here. Since there was tons of vendor issues in android 10 beta we understood why certain things were not working but now when they claim that the vendor issues are resolved how is the camera gone from a flagship to bad. There is a whole comparison we have of zf 5z and 6z and zf 5z on auto has more dynamic range in a night shot than the 6z night mode.

    https://us.v-cdn.net/6031231/uploads/530/HC4NR3W0YQRD.jpg There was an error displaying this embed. https://us.v-cdn.net/6031231/uploads/274/XAMTK7TACHB7.jpg There was an error displaying this embed.

    Check this images and you will get it why we are trying to make a point here.

  • 5 had ai camera, which would focused for a good final image, did u try taking pic on 6z by focusing on a dim place.

  • Maybe auto focus issue

  • I wish but that's not the case. I have 100 more of such pics.

This discussion has been closed.