Problem with reading

[MenkOrd]

Steps to reproduce

Nothing, I just updated the app

Expected behavior

Can read as usual

Actual behavior

When I open a chapter, the pages are black, there are no connection errors, and I can download the page as an image and see it in my phone gallery perfect. It happens with downloaded chapters and not downloaded ones

Crash logs

App version: 1.7.13 (standard, 4714970, 122, 2024-02-09T11:06Z)
Android version: 13 (SDK 33)
Android build ID: DN2103_11_F.50
Device brand: OnePlus
Device manufacturer: OnePlus
Device name: OP515BL1
Device model: DN2103
Device product name: DN2103EEA

Extensions that are outdated, obsolete, or unofficial
Extension Name: Manhwa18.org
Installed Version: 1.4.34
Available Version: 1.4.35
Obsolete: false

Extension Name: Pornwha
Installed Version: 1.4.33
Available Version: 1.4.34
Obsolete: false

Extension Name: Pururin
Installed Version: 1.4.6
Available Version: N/A
Obsolete: true

Extension Name: Manhwahentai.me
Installed Version: 1.4.35
Available Version: 1.4.36
Obsolete: false

Extension Name: MangaMiso
Installed Version: 1.4.4
Available Version: N/A
Obsolete: true

Extension Name: ManhuaDex
Installed Version: 1.4.32
Available Version: 1.4.33
Obsolete: false

--------- beginning of main
02-09 16:04:08.423 15123 15123 E IPCThreadState: attemptIncStrongHandle(91): Not supported
02-09 16:04:08.423 15123 15123 E IPCThreadState: attemptIncStrongHandle(76): Not supported
02-09 16:04:13.793 15123 15123 E IPCThreadState: attemptIncStrongHandle(67): Not supported
02-09 16:04:15.083 15123 15123 E IPCThreadState: attemptIncStrongHandle(92): Not supported
02-09 16:04:26.624 15123 15123 E IPCThreadState: attemptIncStrongHandle(93): Not supported
02-09 16:04:26.624 15123 15123 E IPCThreadState: attemptIncStrongHandle(86): Not supported

Yōkai version

1.7.13

Android version

Android 13

Device

Onep

Other details

No response

Acknowledgements

• I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• If this is an issue with an extension, or a request for an extension, I should be contacting the extensions repository's maintainer/support for help.
• I am reporting an issue exclusive to this fork. I have also checked that is not an issue on the main version of Mihon
• I have tried the troubleshooting guide.
• I have updated the app to version 1.7.13.
• I have updated all installed extensions.
• I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
• I have filled out all of the requested information in this form.

[Th3N3rdyGam3r]

I'm facing the same issue.
Android 11, OnePlus 7T
Crash logs: https://pastebin.com/s0RQB4sF

[vorteex]

same problem. changing reading mode to LONG STRIP works.

[null2264]

Well that's annoying, I couldn't replicate it, might be a OnePlus thing?

[RahmanRagib]

Well that's annoying, I couldn't replicate it, might be a OnePlus thing?

No it's happening in my realme too

[vorteex]

i have it on Samsung.

[null2264]

Can you try this for me? Go to settings, reader, find section "Paged", find Cutout behavior, set it to Ignore.

[MenkOrd]

Can you try this for me? Go to settings, reader, find section "Paged", find Cutout behavior, set it to Ignore.

Didn't work. Still black pages

[vorteex]

I think I found the issue. when you uncheck the "Show content in cutout area" setting and check and uncheck "Crop borders" everything works fine.

…

On Sat, Feb 10, 2024, 11:13 MenkOrd ***@***.***> wrote: Can you try this for me? Go to settings, reader, find section "Paged", find Cutout behavior, set it to Ignore. Didn't work. Still black pages — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVMOFEH2TJSLLU4THH34ZTLYS5B35AVCNFSM6AAAAABDBTT5TKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWHE3DEMRQGE> . You are receiving this because you commented.Message ID: ***@***.***>

[MenkOrd]

I tried again, and it works. Finally, thanks

[KW1J]

I think I found the issue. when you uncheck the "Show content in cutout area" setting and check and uncheck "Crop borders" everything works fine.

man you are the best 👍

[MrDfour]

I think I found the issue. when you uncheck the "Show content in cutout area" setting and check and uncheck "Crop borders" everything works fine.
…
On Sat, Feb 10, 2024, 11:13 MenkOrd @.> wrote: Can you try this for me? Go to settings, reader, find section "Paged", find Cutout behavior, set it to Ignore. Didn't work. Still black pages — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVMOFEH2TJSLLU4THH34ZTLYS5B35AVCNFSM6AAAAABDBTT5TKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWHE3DEMRQGE . You are receiving this because you commented.Message ID: @.>

Came to repot that this worked indeed, Poco X3 Pro. It seems to be a problem with how the image renders with the cutout option since I was able to open the cbz manually with other viewer and also able to see the Manga in another fork. Reactivating the show content in cutout area option makes the image black again and just deactivating it solves the issue

[MrDfour]

I did a bit more testing. Using landscape mode shows the Manga with no issues having the cutout option activated unless the "cutout area behavior" for landscape is set to "ignore cutout areas" . Then it just shows black image like portrait mode

[null2264]

Thanks for effort everyone, it helps narrow things down, I'll look into it and try to fix it when I have free time.

[null2264]

Can anyone test the latest nightly to check if the issue still there?

[MrDfour]

Can anyone test the latest nightly to check if the issue still there?

Can't even open the nightly in any build

time: 1707699382389
msg: android.util.AndroidRuntimeException: requestFeature() must be called before adding content
stacktrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{eu.kanade.tachiyomi.nightlyYokai/eu.kanade.tachiyomi.ui.main.MainActivity}: android.util.AndroidRuntimeException: requestFeature() must be called before adding content
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3655)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3792)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:138)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2308)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7937)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:854)
Caused by: android.util.AndroidRuntimeException: requestFeature() must be called before adding content
at com.android.internal.policy.PhoneWindow.requestFeature(PhoneWindow.java:410)
at eu.kanade.tachiyomi.ui.main.MainActivity.onCreate(Unknown Source:13)
at android.app.Activity.performCreate(Activity.java:8360)
at android.app.Activity.performCreate(Activity.java:8339)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1423)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3636)
... 12 more

[null2264]

Can anyone test the latest nightly to check if the issue still there?

Can't even open the nightly in any build

That should be fixed now... actually nvm, reader broken again ._.

[MrDfour]

Can anyone test the latest nightly to check if the issue still there?

Can't even open the nightly in any build

That should be fixed now... actually nvm, reader broken again ._.

Broken is an understatement haha the app straight away crashes

AN1EiCB6.txt
The log was too extense, I saved it in a txt just in case

[null2264]

Lmao, I already fix that, try updating again

[null2264]

Third time's the charm... hopefully

[MrDfour]

Third time's the charm... hopefully

It's working for me, both vertical and horizontal

[null2264]

Lovely, from my painfully laggy test, it also seems to be working

[null2264]

Alright, should be fixed on 1.7.14. Will release it soon.

[Nanomks1]

Hi I'm having this problem
using App version: 1.8.5.9 (standard, 4b46e9a, 149, 2024-10-06T09:14:12Z)
Android version: 10 (SDK 29)
Android build ID: QQ3A.200805.001
Device brand: Infinix
Device manufacturer: INFINIX MOBILITY LIMITED
Device name: Infinix-X622
Device model: Infinix X622
Device product name: QL1818

Should i open a new issue?
Please help, non of the temporary solution here could fix it.

[null2264]

First you should check if it is an issue with the app or is it an issue with the extension.

If it is an app issue then go ahead, and when you experience the issue you should immediately went to settings > advanced > dump crash log, and attach the dumped log in the gh issue so that I have more context.

[Nanomks1]

I've tried different extension still the same problem i can't read, only after i downloaded the chapter that i can read it...
yokai_crash_logs.txt

[null2264]

The log is pretty much empty, can you screenshot the error you got instead?

[Nanomks1]

Sorry for not being able to respond sooner...

This what i got when i do dump crash logs

App version: 1.8.5.9 (standard, 4b46e9a, 149, 2024-10-06T09:14:12Z)
Android version: 10 (SDK 29)
Android build ID: QQ3A.200805.001
Device brand: Infinix
Device manufacturer: INFINIX MOBILITY LIMITED
Device name: Infinix-X622
Device model: Infinix X622
Device product name: QL1818

--------- beginning of main
10-11 23:16:14.107 5468 10248 E SQLiteLog: (284) automatic index on S(manga_id)
10-11 23:16:14.108 5468 10248 E SQLiteLog: (284) automatic index on C(manga_id)
10-11 23:16:14.108 5468 10248 E SQLiteLog: (284) automatic index on mangas_categories(manga_id)
10-11 23:16:41.984 5468 10264 E BufferQueueProducer: [unnamed-5468-0] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
10-11 23:16:41.984 5468 10264 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
10-11 23:16:52.135 5468 10264 E BufferQueueProducer: [unnamed-5468-1] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
10-11 23:16:52.135 5468 10264 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
10-11 23:21:11.898 5468 10264 E BufferQueueProducer: [unnamed-5468-2] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
10-11 23:21:11.898 5468 10264 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
10-11 23:21:23.639 5468 10264 E BufferQueueProducer: [unnamed-5468-3] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
10-11 23:21:23.639 5468 10264 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
10-11 23:21:33.376 5468 10264 E BufferQueueProducer: [unnamed-5468-4] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
10-11 23:21:33.377 5468 10264 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
--------- beginning of system
10-11 23:21:37.513 5468 10264 E BufferQueueProducer: [unnamed-5468-5] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
10-11 23:21:37.514 5468 10264 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
10-11 23:21:38.481 5468 10248 E SQLiteLog: (284) automatic index on split(_id)
10-11 23:21:41.091 5468 10264 E BufferQueueProducer: [unnamed-5468-6] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
10-11 23:21:41.092 5468 10264 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
10-11 23:21:45.928 5468 10264 E BufferQueueProducer: [unnamed-5468-7] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
10-11 23:21:45.928 5468 10264 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
10-11 23:21:51.521 5468 10264 E BufferQueueProducer: [unnamed-5468-8] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
10-11 23:21:51.521 5468 10264 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
10-11 23:22:00.208 5468 10264 E BufferQueueProducer: [unnamed-5468-9] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
10-11 23:22:00.208 5468 10264 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
10-11 23:22:11.994 5468 10264 E BufferQueueProducer: [unnamed-5468-10] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
10-11 23:22:11.994 5468 10264 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument

This is a screenshot of the black screen.
If this is not helpful can i get the logs some other way to help pinpoint the problem.. sorry I'm not savy in this

[null2264]

Ah, that's already reported here GH-137, maybe you could try nightly version to see if it's already fixed there?

[Nanomks1]

I will try it and get back to you much appreciated.

[Nanomks1]

I've tried it but the problem is unfortunately not fixed in there also..
i will wait for a fix,
This is the best manga reader for me so i will download the chapters for now
Thank you very much for your time and effort.