eReader Pro+ v2 and Google Play books

[lazyt]

Hi all,

After some wonderful help here, I was able to get my pro+ up and running again, including installing v2. However, my sole reason for getting this device - Google Play Books - is not working correctly as it was with v1. Basically, it's paging (pagination) is totally off, with parts of the text being rendered off the page and weirdly places page breaks.

I'm really disappointed because, as I mentioned, this app is the sole reason I purchased this device (and I had confirmed before purchasing that GPB works fine). Is anyone else experiencing this? Does anyone have any solution?

p.s. I can post screenshots if the description of the issue isn't clear, if someone can tell me how.

[lazyt]

Here is a photo of the screen. Notice the lack of margins on top and on bottom? This is because there is still text there! (I.e. the margins extend to part of the screen that is non-existent).

http://i.imgur.com/bHooKaX.png

p.s. MODS: if you can insert [img] tags with scaling to a decent size, thanks!

[nhedgehog]

Don't know about Google Play Books but the picture looks like the App is not working in fullscreen. That can be solved be installing full!screen (more here).

[lazyt]

Thank - really loving the full screen mode. Unfortunately, it didn't help. Here is another image from the page preview mode showing the page break right down the middle: http://imgur.com/zQU43fO

[nhedgehog]

Looks like an error in the Google Play books app. Only the developer can repair that. You should contact them. Don't know if they are producing an eInk friendly version of this. I wouldn't use it but rather stick to working reading apps.

Edit:

After some wonderful help here, I was able to get my pro+ up and running again, including installing v2. However, my sole reason for getting this device - Google Play Books - is not working correctly as it was with v1. Basically, it's paging (pagination) is totally off, with parts of the text being rendered off the page and weirdly places page breaks.

Actually I don't believe that this is a problem which came out after updating the firmware. I guess it has more to do with updating Google Play books.

[lazyt]

Actually, Google Play Books was working just fine with v1. I'm not sure how, but it seems the firmware managed to screw it up.

[nhedgehog]

If so, have you tried to reset (delete all data of) Google Play Books?
BTW: Its easy to switch between two versions of the firmware.
You just need to flash the system.img. How to backup and flash it is described in theRK3026 E-Readers Kitchen thread.

[lazyt]

Yes, I have tried clearing the data. I also reset my device since (factory reset). Neither helped.

[V3t]

I have that issue on my note3, I have been wondering if the DPI has been causing this. Perhaps something similar here?

I don't really use it so never looked into it, was just comparing a sample to a kindle book.

[lazyt]

DPI sounds like a very likely culprit. Did the DPI change between versions? Now that I'm rooted, how can I change the DPI?

[nhedgehog]

Originally Posted by lazyt

DPI sounds like a very likely culprit. Did the DPI change between versions? Now that I'm rooted, how can I change the DPI?

I guess thats the "ro.sf.lcd_density=" value in the system\build.prop

Boyue T62D firmware from 03/2015 has the value:
ro.sf.lcd_density=212

But you can verify this by yourself while comparing build.prop of v1&v2 of the ES ROMs.

[V3t]

Yeah changing the DPI on phone worked. 480 it didn't like, 320 worked fine.

You just need to edit the build.prop file or there are probably a few apps on Google Play Store that would do it. I am not sure how it will effect Energy's launcher though so your mileage may vary. As for the value I think 240 is a "standard" value as well as 320 and 480.

Another thought would be to check V1 dpi and compare, I would for you but I don't use my Energy ereader anymore so don't have the tools about unfortunately.

Another alternative would be the xposed framework with per app dpi setting, might be safest route!

An alternative would be to find a multi dpi version of the APK... Google play store can also be finicky about DPI and there are some multi dpi ones of it around.

[Purple Lady]

Originally Posted by nhedgehog

I guess thats the "ro.sf.lcd_density=" value in the system\build.prop

Boyue T62D firmware from 03/2015 has the value:
ro.sf.lcd_density=212

But you can verify this by yourself while comparing build.prop of v1&v2 of the ES ROMs.

If you change the dpi in the build.prop, it won't work properly and you'll have to put the original back using adb. Been there done that.

Originally Posted by V3t

Yeah changing the DPI on phone worked. 480 it didn't like, 320 worked fine.

You just need to edit the build.prop file or there are probably a few apps on Google Play Store that would do it. I am not sure how it will effect Energy's launcher though so your mileage may vary. As for the value I think 240 is a "standard" value as well as 320 and 480.

Another thought would be to check V1 dpi and compare, I would for you but I don't use my Energy ereader anymore so don't have the tools about unfortunately.

Another alternative would be the xposed framework with per app dpi setting, might be safest route!

An alternative would be to find a multi dpi version of the APK... Google play store can also be finicky about DPI and there are some multi dpi ones of it around.

Xposed App Settings module should fix the problem. I had a similar issue with Overdrive and changing the dpi using App Settings fixed it. It took a few tries to find a dpi that worked.

[lazyt]

I tried playing with the DPI but it got me nowhere. What DPI are you guys using?

[V3t]

Originally Posted by lazyt

I tried playing with the DPI but it got me nowhere. What DPI are you guys using?

I will wipe the dust off mine and try tonight, did you try 240 & 320?