Related
Until Vilord get's back and can post it in his other thread. Here is a kernel for ECLAIR ONLY that will help with open gl performance it's not setting permission properly on boot yet, but when the system's booted chmod a+rw /dev/msm_hw3d* than stop/start. Again I'm sure if I don't Vilord will get the permissions fixed up when he's back.
Big thanks to DZO again for applying all of the needed changes
The google live wallpapers do not work properly, however the visualization papers do, as well as the wallpapers from the market because they are written in just open gl, not lite.
This brings neocore results from 01.6 to 15.6 fps!
Results may vary.. (I like that phraze )
Download
http://www.mediafire.com/?sharekey=f6ec00ed7ed721a8d0d290dca69ceb5cf8913d4b9300395c16f8cf40558950b4
If you like my work and would like to donate me a beer you can by clicking here Beer Me
where's it located?
posted them to media fire. When Vilords back we'll put them on sourceforge.
FREAKING SWEET!!!!
You Da Man!!!
Is there a zImage version available for haret? thanks.
If you had to remove libGLES_qcom.so I'm not quite sure how you're actually getting hardware graphics, since it's the driver...
Is this only for 3D animation on home screen or are we likely to see any performance upgrades during day-to-day use of Eclair (as in screen scrolling or switching between apps).
Pl clarify.
bri3d said:
If you had to remove libGLES_qcom.so I'm not quite sure how you're actually getting hardware graphics, since it's the driver...
Click to expand...
Click to collapse
bri3d. hit me up on gtalk.
After realizing the permissions weren't being set properly still I set them with the commands in the first post.
There is a definite increase in some of the live wallpapers however some do not work properly at all now. I believe it is because of opengl es lite not being supported. As example the grass wallpaper now only has a white background, although the grass looks alot better. lol. Wallpapers off the market are much smoother now.
however this is a huge step in the right direction
Seeing the same issues - it's a shame the current Q3Dimension driver for this chipset doesn't support everything Live Wallpapers want. On the other hand, the couple games I've tested thus far work, along with Street View.
"Grass," "Spectrum," and "Polar Clock" (after changing the colors in the options, thanks mssmison!) seem to be the only live wallpapers that work for me (Cube does too, but it's not GL) - Magic Smoke crashes on 320x240 due to a bug in the wallpaper itself (mssmison confirms it works fine on bigger resolutions), Galaxy uses an unimplemented GLES call, Nexus just doesn't work (this is the one that confuses me most - no unimplemented call errors and the GPU allocates just fine, just doesn't display anything), Water's got some unimplemented calls too.
We'll see if a newer Q3Dimension version ever surfaces or downport wallpapers - until then, I think this is parity with official MSM7500 devices so it's about the best we can do.
bri3d said:
"Grass," "Spectrum," and "Polar Clock" (after changing the colors in the options, thanks mssmison!) seem to be the only live wallpapers that work for me (Cube does too, but it's not GL)
Click to expand...
Click to collapse
Interesting about changing colours - I'm running into an issue where the bootanimation on heroblend on the nomorootfs nand (or nand 2.0) completely whites out - I've replaced with a different bootanimation and it works fine.
Are there some colours out of limits?
When I ran this on my Vogue it made everything super huge...what did I do wrong?
plemen said:
Interesting about changing colours - I'm running into an issue where the bootanimation on heroblend on the nomorootfs nand (or nand 2.0) completely whites out - I've replaced with a different bootanimation and it works fine.
Are there some colours out of limits?
Click to expand...
Click to collapse
yes there are, I havent had time to go through and define them as of yet.
mssmison said:
Until Vilord get's back and can post it in his other thread. Here is a kernel for ECLAIR ONLY that will help with open gl performance it's not setting permission properly on boot yet, but when the system's booted chmod a+rw /dev/msm_hw3d* than stop/start.
If you like my work and would like to donate me a beer you can by clicking here Beer Me
Click to expand...
Click to collapse
A little help please- is it one line in terminal:
chmod a+rw /dev/msm_hw3d*
or is there another line? What do you mean by "than stop/start"?
So if I already flashed to mssmison's 2.1 build using the 480 nbh then changed the density to 120 and flashed to 320 nbh, what exactly do I do with this .nbh? Do I have to start from scratch or can I use the volume up menu to update?
hexto said:
So if I already flashed to mssmison's 2.1 build using the 480 nbh then changed the density to 120 and flashed to 320 nbh, what exactly do I do with this .nbh? Do I have to start from scratch or can I use the volume up menu to update?
Click to expand...
Click to collapse
What are you trying to do? If you are trying to get the dialer to fit correctly download the qgva update tar file. Open it using 7 zip after download and open the build.prop file change the density to 110 save it and run the update tar file via the new installer.
Reddog80p said:
What are you trying to do? If you are trying to get the dialer to fit correctly download the qgva update tar file. Open it using 7 zip after download and open the build.prop file change the density to 110 save it and run the update tar file via the new installer.
Click to expand...
Click to collapse
Trying to get HW3D working
hexto said:
Trying to get HW3D working
Click to expand...
Click to collapse
Flash the nbh from the first post in this thread then run the app from this post under opengl support..
http://forum.xda-developers.com/showpost.php?p=5486428&postcount=1
I've been searching, and have seen lots of threads about similar problems with the Evo and it's fairly low-color screen, but I was under the impression that the Droid X has a 24bit color screen so this shouldn't be an issue.
Anyway, I've got some wallpapers (cropped and resized for the Droix X from the originals at Ultralinx)
They look fantastic on the computer. They're the right dimensions. Tried saving as JPG and 24 bit PNG, but the outcome is the same. When I copy them to the phone and set them as wallpaper, the gradients don't look smooth; there is color banding all over the place.
I've got screenshots and originals up on the web, but can't link to them until my account is approved by a mod.
EDIT: Added attachments instead, but the forum super-compressing the images doesn't help their clarity at all.
Hey,
i've got the same problem.
That's not funny at all, I really don't know how to save it, that it looks like on my desktop pc!
4tticuz said:
Hey,
i've got the same problem.
That's not funny at all, I really don't know how to save it, that it looks like on my desktop pc!
Click to expand...
Click to collapse
Sorry to be off topic but I cant help but stare at your notification bar. What theme is it?
It's my own notificationbar.
Have to search the files first
It doesn't seem to be the screen. I dropped those images into my dropbox, and opened them in whatever viewer dropbox opened by default. The image was smooth as I zoomed in, until I zoomed in far enough to see a moire pattern. I also opened it in Astra's built in viewer; again there was no banding. However, when I set the image to be my wallpaper, I see the same banding you are seeing.
Bad news is, I don't know what the problem is; good news is it doesn't seem to be a screen limitation.
Thanks so far!
But what's the problem than?
I really have no idea :/
Ah ha! Google turned up this app: "Wallpaper Set and Save" (Sorry, can't post a link because I'm new, apparently. I attached an image of the QR code instead.)
It says it hasn't been updated for 2.x, but it worked fine on my droid x (running the stock rom with launcher pro.) Using it to set the exact same wallpaper, I now see no banding (although I did in the preview screen.) It's worth a try, although I'd still like to know what is causing this issue (since it obviously isn't a hardware issue.)
I attached a screen capture so you can see for yourself.
Edit: The forum's image compression adds some artifacts; it looks even smoother on my screen capture. Even here it's a big improvement over the others though!
Its probably the gallery app that is re-compressing the wallpaper and creating the bands
Weeds2000 fixed the orientation on our Folio100 to work with games like Asphalt5 and now its possible to play, although graphics are still kinda messed up. but other games like the 3d tilt works nearly perfect now too.
you might find it useful, and VEGAn mod might be able to include this as my FolioTntMod is based of the TNT framework...
Find the download patch i made for our folio in this thread.
it also include a full 360 rotation fix, if you need it
As we all share the same Tegra2 platform and can nearly swap experience here, im posting this to share the fixes weeds2000 made for us...
Hope you find it useful..
Note:
The patch i made might actually work fine as update.zip on your tablet as well, or might need minor adjust to install, but let g tablet modders fix this if needed.
at least now you know its available.
Thank you! One question - do you know what file(s) were altered for the 360 rotation fix? Was it a lib file, for example?
EDIT: Also, to any other modders looking at this, the system.img is a ext2 filesystem image, NOT a yaffs2 image.
roebeet said:
Thank you! One question - do you know what file(s) were altered for the 360 rotation fix? Was it a lib file, for example?
EDIT: Also, to any other modders looking at this, the system.img is a ext2 filesystem image, NOT a yaffs2 image.
Click to expand...
Click to collapse
Roeby wan Kanobi, is this something that could work and be added to TnT Lite? My Clockwork back up just completed
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
Click to expand...
Click to collapse
This could be another watershed update Also- with the accelerometer corrected, folks will be getting exercise by holding up the G while playing games
added:
Perhaps the one extra update that would be nice is a DSP manager so dB level or gain increases can be made. Modders released a DSP manager on the Incredible that allows increases to 3.5mm and speaker output. Hardware based EQ too.
Perhaps being too picky, but louder speakers would be nice.
Did you see.. they provided the SOURCE!!!!! This is what we need!
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
Click to expand...
Click to collapse
What does the patch change? Would is break things when the application developer fixes the orientation code in their game.
We saw this problem fixed in the application in the Gallery 3D application by google, not in framework. http://android-developers.blogspot.com/2010/09/one-screen-turn-deserves-another.html
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Click to expand...
Click to collapse
okay here are some details.
the framework.jar modified comes from this file: update-smb_a1002-3338-user.zip
the library should be generic, but is required for the gsensor/rotation/orientation fix as part of the new framework.jar changes.
the 2 primary folders in the framework.jar changed are /android/hardware /android/view
you should be able to easily spot the differences in filesizes..
do note: there is another change android\os\Environment.smali as i modified it to work with /mnt/sdcard and /mnt/sdcard/sdcard-disk0 and /mnt/usbdisk-disk0 for compatibility with folio mount functionality.
here is the "vold" also different but works fine with the tap'n'tap framework.
remember that /etc/vold.fstab needs changed to support the more new mount devices if you wish to use that one too.
360 rotation fix is in android\view\WindowOrientationListener$SensorEventListenerImpl.smali
orientation fix is
android\hardware\SensorManager*.smali
but again, the framework.jar is Tap'n'Tap based, so works directly on top of r3338 edition.. and i made a patch in my section with just framework + lib files included.
rothnic said:
We saw this problem fixed in the application in the Gallery 3D application by google, not in framework. http://android-developers.blogspot.com/2010/09/one-screen-turn-deserves-another.html
Click to expand...
Click to collapse
No, as far as i understand, weeds2000 only made the hardware swap sensor reading, so now it acts like a portrait mobile phone, where our Tegra2 has the chip rotated once 90degree.
Dexter_nlb said:
No, as far as i understand, weeds2000 only made the hardware swap sensor reading, so now it acts like a portrait mobile phone, where our Tegra2 has the chip rotated once 90degree.
Click to expand...
Click to collapse
Hmm, so it does a 90 degree rotation. And the device is still a default landscape device. We definitely need to make sure there are no negative effects on games that utilize the acceleromether and worked fine before.
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Thanks for the explanation - this is something I suspected would fix it, but it's good to see that someone had pushed the idea all the way through to an actual fix.
So, I suspect that when the device boots up, it should be in portrait mode initially (until the sensor kicks in).
roebeet said:
So, I suspect that when the device boots up, it should be in portrait mode initially (until the sensor kicks in).
Click to expand...
Click to collapse
That makes more sense to me if that is true.
I read through the code ... Prior to the code change they were performing the rotation either for Acceleration minus Gy on the y-axis
or Acceleration minus Gz on the z-axis and NOT Acceleration minus Gx on the x-axis. Now the axis swap is always occurring... under all 3 conditions irregardless of sensor.
Dont know why there was an exclusion in the first place for Acceleration minus Gx on the x-axis...
When I get back I will look through the code some more...
rothnic said:
Hmm, so it does a 90 degree rotation. And the device is still a default landscape device. We definitely need to make sure there are no negative effects on games that utilize the acceleromether and worked fine before.
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Click to expand...
Click to collapse
rothnic said:
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Click to expand...
Click to collapse
if Google didn't "invent" the different way of reading sensors, there would only be one way of doing it, so developers would not be able to see it, so an update to like 2.2 or higher is now an requirement, right? but if older games do not check, it would work with them, so this fix solves it as i see it.
putting back androidos orientation handling to its original state, as many developers should be reading it.
I have ported the fix for both TnT stock and lite. As well as Vegan beta 4.
http://forum.xda-developers.com/showthread.php?t=892345
gojimi said:
I have ported the fix for both TnT stock and lite. As well as Vegan beta 4.
http://forum.xda-developers.com/showthread.php?t=892345
Click to expand...
Click to collapse
remember its all done by weeds2000 , i cannot/will not take credits for his effort here, i am just sharing the good work done on this fix.
I have released a new version of the fix, this should clean up all the remaining issues with the accelerometer/compass. Code is also much cleaner now. Some weird hacks you may have seen were caused by the legacy API which was used by my test game.
Only known issue up to now is that the mouse coordinates are also rotated.
The source can be found in the zip file attached to the original post, I hope that all changes are prefixed with // XXX:
The source files are based on the nvidia-froyo tree.
Link:
http://forum.xda-developers.com/showpost.php?p=10209624&postcount=38
Doodle jump doesn't work. Game loads upside-down with home buttons on top. If you tilt left you go right...Any fix for this?
Does this work for the VegaN Ginger Edition, or is that fix built into the ROM, I think I am having issues with some games on that ROM.
bmw4aaron said:
Doodle jump doesn't work. Game loads upside-down with home buttons on top. If you tilt left you go right...Any fix for this?
Click to expand...
Click to collapse
I think you can write the developer and tell , that the games is not working normally.. all other games work fine, so why would one game stand out, only reason, bad programming, or misunderstanding of androidOS and orientation. maybe developer thought he should fix the "orientation" in his game on tablet, and forgot other trying to make it reverse.. so: bad programming and choice of developer..he should follow guidelines and not his ideas.
After some poking and prodding at my A7+, I was surprised by some of it's short comings. A couple in particular are easily rectified. The following changes require root access and some means of editing your /system/build.prop file (Root Explorer is real nice).
The first problem was that the screen was not as sharp and crisp as I would have expected for a 7 inch tablet running at 1024x600. As someone on these forums pointed out the LCD density is set incorrectly for the display, and that causes some problems with position/size of things in various apps. To fix this you need to change a line in /system/build.prop.
Code:
Default: ro.sf.lcd_density=200
Correct: ro.sf.lcd_density=160
The next problem is that the device reports OpenGL ES 1.1 when queried through the Android APIs, but when queried through the OpenGL APIs it reports OpenGL ES 2.0. This is a kinda big problem if you like playing indie games because few programmers will bother with low level calls when there is a decent framework to take care of that for them (let's them focus on their product instead of the boilerplate under it). To change this so that it reports correctly in the Android APIs you must add the following to the bottom of /system/build.prop.
Code:
ro.opengles.version=131072
The last problem I've not found an elegant solution for. The tablet doesn't seem to want to engage the second processing core unless a program explicitly demands it. The workaround for this is to install System Tuner, go to CPU, and slide the second CPU (left slider) all the way up, it will not keep this setting upon reset, it does keep it through sleep though. It is much more battery intensive with the CPU full engaged like that, so you'll want to kick it back down when you don't need it. One example where this made a huge difference: I was trying to watch a video encoded in x264 hi10p, without the second CPU engaged the video played slowly while the audio played full speed, with the second CPU engaged it played full speed without so much as a stutter.
I'm going to dig into the tablet a bit more now that I have a terminal emulator and ssh server set up on it. If there are power profiles like the stuff I've had to tweak on my laptop, can likely squeeze out a lot more performance with some fine tuning.
eideticex said:
After some poking and prodding at my A7+, I was surprised by some of it's short comings. A couple in particular are easily rectified. The following changes require root access and some means of editing your /system/build.prop file (Root Explorer is real nice).
The first problem was that the screen was not as sharp and crisp as I would have expected for a 7 inch tablet running at 1024x600. As someone on these forums pointed out the LCD density is set incorrectly for the display, and that causes some problems with position/size of things in various apps. To fix this you need to change a line in /system/build.prop.
Code:
Default: ro.sf.lcd_density=200
Correct: ro.sf.lcd_density=160
The next problem is that the device reports OpenGL ES 1.1 when queried through the Android APIs, but when queried through the OpenGL APIs it reports OpenGL ES 2.0. This is a kinda big problem if you like playing indie games because few programmers will bother with low level calls when there is a decent framework to take care of that for them (let's them focus on their product instead of the boilerplate under it). To change this so that it reports correctly in the Android APIs you must add the following to the bottom of /system/build.prop.
Code:
ro.opengles.version=131072
Click to expand...
Click to collapse
Wow. The lcd change is really nice- everything is much smaller but fits and looks sharper and cleaner. I saw that same post awhile ago but didn't pay much attention to it. Videos also look better.
I'm going to dig into the tablet a bit more now that I have a terminal emulator and ssh server set up on it. If there are power profiles like the stuff I've had to tweak on my laptop, can likely squeeze out a lot more performance with some fine tuning.
Click to expand...
Click to collapse
I really hope you continue to work on this tablet- it definatly needs some work. You should talk to Jam4 over at TR about this. He is making a HC ROM, and I bet he could bake the CPU changes right into the ROM.
I'm new to this stuff but where does the density come from? when I did my own math it seemed closer to 170.
Naidosh said:
I'm new to this stuff but where does the density come from? when I did my own math it seemed closer to 170.
Click to expand...
Click to collapse
Sorry been busy with my coding projects, so haven't popped into the forums in awhile. If I'm right in assuming you calculated that based on the visible screen space and resolution, you have to consider that screens have a metal trim around the edge which covers a few pixels of width and height on each border. If you dig through the source code that eLocity released, there are padding values in place to compensate for those when rendering to the screen. Almost every display out there does this, LCDs are pretty good about minimal over size, but old CRTs would have as much as 20% of the screen tucked behind the bezel for a nice border.
So Marshmallow uses this new format for configuration files for apps on the EPD. Maybe we can start collecting recommended configurations for various apps? I noticed that the default files it comes with don't include the Kindle app this time, tho it had a default config in the old LP settings.
So, if you've found good settings for a particular app, please post them here! And I might go look on the Russian site to see if there are any there already - tho if one of the Russian-speaking users here wants to do that first I wouldn't complain
edit: I just found an app for editing the new configuration files, it's by x2009xxx on this hi-pda thread. Attaching for convenience. The button at the bottom to save the configuration and the toast that pops up when you do so aren't in English, but all the options are, so I'm pretty sure you can figure it out. (Don't forget to reboot to activate your changes)
I am wondering is there possibility to set epd to full refresh after 5 pages or every page. There is no sign in readme file. I tried adding ""slowmode" : true" in the configuration cfg but notting happens.
I'm not sure, but I have gathered that you have to reboot for changes to take effect.
Sent from my YD201 using Tapatalk
I know, when I change something (ex. dithering, sharpening etc.) there is effect but problem is that i don't see command which can set full refresh of epd screen after some interval (previously it was slowmode). I'm using moon+ reader (white letters on black background) and without full refreshing after some pages ghosting is terrific and reading seems to be nearly impossible.
Remove the Android GUI transitions/effects on Developers Menu, not only makes your phone faster but it also helps EPD to have less ghost when using the other Android Apps, and folders...
I just edited the first post to add a tool I found for editing the config files.
ahigienix said:
I know, when I change something (ex. dithering, sharpening etc.) there is effect but problem is that i don't see command which can set full refresh of epd screen after some interval (previously it was slowmode). I'm using moon+ reader (white letters on black background) and without full refreshing after some pages ghosting is terrific and reading seems to be nearly impossible.
Click to expand...
Click to collapse
I'm looking at the readme.txt that lives in the epd_optimizer directory, and the option that sounds related to what you're talking about is "update_timeout - timeout of fullscreen update after content change. Use -1 to disable."
Tried to change update_timeout value. There are some changes in update mode but EPD still not doing full refresh (like in Yotareader for example). Still after flipping some pages black background is full of gray shades from previously viewed pages. Tested on CoolReader, Moon+ FBreader, Allreader.
Is there anyone who figured out how to set full refresh of EPD in any book reader?
Nice thread, I had in mind creating one like this. I haven't played with the configuration file yet, but I can post here what I found from other xda posts and a file from Russian Telegram group.
For Whatsapp (but I think it should work also on other similar apps) a configuration found here is the following:
Code:
{
"name": "com.whatsapp",
"description": "WhatsApp",
"dithering": "ATKINSON_BINARY",
"update_timeout": -1,
"sharpening": 2,
"contrast": 0,
"brightness": -5,
"stretch_black": 50,
"stretch_white": 220,
"regional_update": false
}
For Vkontakte (VK - Russian social network) I found this one:
Code:
{
"name": "com.vkontakte.android",
"description": "VKontakte",
"update_type": "GRAYSCALE",
"dithering": "ATKINSON_BINARY",
"update_timeout": 0,
"sharpening": 1.0,
"contrast": 50,
"brightness": 10,
"stretch_black": 50,
"stretch_white": 200,
"regional_update": true
}
Maybe we could develop some configurations for groups of apps: chat, social, e-book readers, office, browser, etc. and post them here!
Don't know if I'm missing something but I've tried all sorts of different values for dithering, update type, contrast, brightness, stretch_black, and stretch_white but after restarting nothing seems to have any effect. No matter what I do, everything just looks way too bright/low contrast and washed out. On the other hand, the Yotahub looks fine--deep blacks and easy to read.
This is on a YD206. Everything looked fine on lollipop. I submitted bug reports to yotadevices but they told me that the YD206 isn't supported. Anyone else having this issue? And if so, are you on YD206?
EDIT: Anyone know how to query what epd_optimizer settings an application is using? The backscreen is the only thing that looks good and AFAIK its package name is com.yotadevices.yotaphone2.launcherbs . Unfortunately there's no corresponding entry in the epd_optimizer directory.
Here is a stock EPD_optimizer folder after OTA upgrade from 5.0. Try replacing your files and reboot.
I figured out that changing values via application make a mess in cfg files. Better to check package name using app, copy some stock cfg, rename it to package name and edit via Total Commander it works fine.
I have yd206 and changing values take effect but i can't set full EPD refresh.
EDIT: Anyone know how to query what epd_optimizer settings an application is using? The backscreen is the only thing that looks good and AFAIK its package name is com.yotadevices.yotaphone2.launcherbs . Unfortunately there's no corresponding entry in the epd_optimizer directory.
Click to expand...
Click to collapse
From readme.txt
If these parameters are missing in app's configuration as well, the system will use parameters which defined in master.cfg configuration file. If this file is deleted, the system will use parameters that are stored within Android framework.
ahigienix said:
Here is a stock EPD_optimizer folder after OTA upgrade from 5.0. Try replacing your files and reboot.
I figured out that changing values via application make a mess in cfg files. Better to check package name using app, copy some stock cfg, rename it to package name and edit via Total Commander it works fine.
I have yd206 and changing values take effect but i can't set full EPD refresh.
From readme.txt
If these parameters are missing in app's configuration as well, the system will use parameters which defined in master.cfg configuration file. If this file is deleted, the system will use parameters that are stored within Android framework.
Click to expand...
Click to collapse
Thanks, I'm no longer using the app to modify the values as you suggested and changing settings has an effect now. (using vim in an arch chroot environment) Using your stock values for a separate firefox config seems to have improved things. Still not nearly as good as 5.0 but I can actually read text now.
However, there is this issue where from moment to moment the screen brightness seems to switch back and forth between two settings: a config with deeper blacks (clear) and a config that's too bright. It's almost as if there are two configs fighting for control. If I let the phone sit (so there are no screen updates), it will eventually settle on one of those configs but not reliably on any particular one--it almost seems random. I spent several hours trying a variety of different settings but I can't seem to get rid of this problem or manage a config that's comparable to 5.0.
At this point I think I'm just going back to 5.0 as I can't really put any more time into this. Maybe the problem will sort itself out in future releases but I'm not hopeful given the lack of support for the YD206.
I have three yd206, one which firmware was sideloaded from 1.1.31 had simmilar to your EPD glitchs, try to delete your epd_optimizer folder, create new one and copy files from attachment, then do a hard reset. It helped me and now this yd206 runs flawlessly.
I found the file /root/sdcard/TitaniumManager/mirror.cfg has some information similar to files in .../android/epd_optimizer and create a configuration for FBReader, but makins some test it seems nothing change.
Follow the last solution for my file org.geometerplus.zlibrary.ui.android.cfg
{
"name": "org.geometerplus.zlibrary.ui.android",
"description": "FBReader",
"dithering": "ATKINSON_BINARY",
"update_timeout": -1,
"sharpening": 1.0,
"contrast": 70,
"brightness": -10,
"stretch_black": 50,
"stretch_white": 220,
"regional_update": false
}
Have you any suggestion?
ahigienix said:
I have three yd206, one which firmware was sideloaded from 1.1.31 had simmilar to your EPD glitchs, try to delete your epd_optimizer folder, create new one and copy files from attachment, then do a hard reset. It helped me and now this yd206 runs flawlessly.
Click to expand...
Click to collapse
Hi, couldn't get this off of my mind so I took another stab at it. I've tried everything you've suggested but haven't been able to get things to an acceptable level. I've put together a couple images comparing 5.0 and 6.0 image quality (attached to this post) with the epd_optimizer .cfgs you've provided.
The two images have a few different icons on the home screen but demonstrate the difference in both brightness and clarity pretty well. I'm not saying those .cfgs didn't improve things--they definitely did (yes, it originally looked even worse than the 6.0.jpg image prior to using the .cfgs you provided) but it still doesn't look nearly as good. Looking at the 6.0.jpg image, you can probably imagine how difficult it would be to read an ebook or browse the web.
I think there's more to this than the .cfg files. Note that I upgraded to 6.0 by restoring the "MMB29M.6.0.1-RU1.1.147" backup provided in this thread via TWRP. I was coming from LRX21M.5.0.0-HK1.1.124d (I always clear the cache and dalvik between firmware changes of course).
EDIT: Whoops, I've mixed up the image names. Fixed the images.
Excuse me i do not know about changing that values for the epd
but as a person who works and edits photos the difference between the pics is remarkable in my eyes
beacuse it seems to be that there are different grey scales that are produced, especially the black value.
You can edit every photo you made into greyscale (8bit or 16bit) and it normally looks fine.
but you can also convert it into a black/white (1bit) picture with a filter like diffusion and it is more grainy.
so for me it looks that the 6.0jpg is too grainy and is not the correct grayscale. It can be washed out but the black part seems not that fine as it is in the 5.0jpg pic.
maybe this isn't that important but i want to point on that.
GetSAS said:
Excuse me i do not know about changing that values for the epd
but as a person who works and edits photos the difference between the pics is remarkable in my eyes
beacuse it seems to be that there are different grey scales that are produced, especially the black value.
You can edit every photo you made into greyscale (8bit or 16bit) and it normally looks fine.
but you can also convert it into a black/white (1bit) picture with a filter like diffusion and it is more grainy.
so for me it looks that the 6.0jpg is too grainy and is not the correct grayscale. It can be washed out but the black part seems not that fine as it is in the 5.0jpg pic.
maybe this isn't that important but i want to point on that.
Click to expand...
Click to collapse
I see, thanks for the insight. Maybe this will help with determining what's causing this.
I changed contrast in the master to 40, and I'm pretty happy with the results.
Full master file:
Code:
{
"name": "master",
"description": "This is default epd update setting. Please modify with caution.",
"update_type": "MONOCHROME",
"dithering": "STUCKI_BINARY",
"update_timeout": -1,
"sharpening": 1,
"contrast": 40,
"brightness": 10,
"stretch_black": 30,
"stretch_white": 220,
"regional_update": false,
"color_inversion": false
}
epd refresh problem
after i upgrade official stock 6.0.1 my epd stop refreshing. am i in the right place? i dont know how to change the values mentioned above. can someone help me please? thanks
lgk350tr said:
after i upgrade official stock 6.0.1 my epd stop refreshing.
Click to expand...
Click to collapse
My navigation program has the same probem. Too much ghosting. Is there a possibility, to set a refresh time? (Maybe a background program with timer and torch screen?) I can do it with developer options (show surface updates). Is it possible, to make a shortcut or start and stop it automatically?
If the yotaphone is in standby, the epd screen is constantly flashing (after 2 minutes) and I don't know, why.
I am experiencing the same. I own a YD206 converted to 201 and running lates MM OTA update.
EPD screen was fine for couple of days, but know ghosting is terrible specially when navigating thru full Android. Also black color on widgets is totally grayed out.
Right now I am trying the full discharge and leave it for couple of hours before I fully charge it.
Any other solution/suggestion on what to try? This is definetly a refresh problem which is not eliminating previous images.
Thanks