[mcschweg]

darkrickpr, on 12 February 2013 - 07:16 AM, said:

That's the problem cuz it new hack playstore won't be affected from the buildprop and I see everyapp showing up. I will get and old version and see how it goes.

Sent from my HTC Holiday using Tapatalk 2

Test3 after installing and executing LCD DENSITY MODDER PRO.app:

It downloaded and installs some Playstore mod3_a_240.apk (because i chosed, that Playstore should think, i am on 240DPI-dont know, why this is important to the app). It is a Playstore Version 3.5.15.
AND it downloaded and installs GSF.mod1_16a_240.apk.
After reboot, incompatibilities are gone AND switching is still possible.

Can you mimic that and build it in?

Edit:
Tried executing LCD DENSITY MODDER PRO.app on test4 to get the "good" hacked Playstore,
BUT IT ALSO GET THE SWITCH STUCK.

SO it is not the hacked Playstore. Sorry.

Again:
Test3 with LCD DENSITY MODDER PRO.app hack ---> working switch.
Test4 with or without LCD DENSITY MODDER PRO.app hack ---> not working switch

This post has been edited by mcschweg: 12 February 2013 - 08:01 AM

[darkrickpr]

mcschweg, on 12 February 2013 - 07:47 AM, said:

Test3 after installing and executing LCD DENSITY MODDER PRO.app:

It downloaded and installs some Playstore mod3_a_240.apk (because i chosed, that Playstore should think, i am on 240DPI-dont know, why this is important to the app). It is a Playstore Version 3.5.15.
AND it downloaded and installs GSF.mod1_16a_240.apk.
After reboot, incompatibilities are gone AND switching is still possible.

Can you mimic that and build it in?

I will give a test and if work I will try to integrate test4 fixed thanks mc

Sent from my HTC Holiday using Tapatalk 2

This post has been edited by darkrickpr: 12 February 2013 - 07:59 AM

[mcschweg]

darkrickpr, on 12 February 2013 - 07:57 AM, said:

I will give a test and if work I will try to integrate test4 fixed thanks mc

Test went wrong. See Edit above.

It is, as you said, the attempt to change thhe build.prop by the skript, that lets the boot go wrong afterwards.
So one solution is, to leave the build.prop untouched by taking out 2 lines of the skript like this:

#!/system/bin/sh
#

#
# v 0.2 by Rara Avis 20130204, modded
#

# lcd_density for 'Normal' mode
NORMAL=160;

# lcd_density for 'HD' mode
HD=203;

CURRENT=$(cat /sys/devices/platform/rk-fb/graphics/fb0/resolution | grep current | sed -e 's/^.*://');
mount -o remount,rw /system;
case $CURRENT in
  0)
    echo "Normal->HD";
    flash_store 1;;
#sed -i s/ro.sf.lcd_density=.../ro.sf.lcd_density=$HD/g /system/build.prop;;

# uncomment the next line to use in native "retina" ROM 
# not wise due to existing appropriate "Settings" item
#    setprop persist.sys.lcd_density $HD;;

  1)
    echo "HD->Normal";
    flash_store 0;;
#sed -i s/ro.sf.lcd_density=.../ro.sf.lcd_density=$NORMAL/g /system/build.prop;;

# uncomment the next line to use in native "retina" ROM 
# not wise due to existing appropriate "Settings" item
#    setprop persist.sys.lcd_density $NORMAL;;

esac
mount -o remount,ro /system;
sync;
sleep 1;
reboot resolution;

The only downside of this simple solution is, that you have to alter the
ro.sf.lcd_density manually in build.prop, before you switch res (i.e. 203).

But maybe you can find out, how the skript can be go through even with the dpi changing, because that is so much cooler

Maybe the sleep=1 is too short, and it should wait for a few seconds longer?

This post has been edited by mcschweg: 12 February 2013 - 09:43 AM

[Rara Avis]

mcschweg, on 12 February 2013 - 08:02 AM, said:

Test went wrong. See Edit above.

It is, as you said, the attempt to change thhe build.prop by the skript, that lets the boot go wrong afterwards.
So one solution is, to leave the build.prop untouched by taking out 2 lines of the skript like this:
(skipped

May be it is easier for danerick to remove extra space in "ro.sf.lcd_density= 220" (before "220")?

[mcschweg]

Rara Avis, on 12 February 2013 - 09:54 AM, said:

May be it is easier for danerick to remove extra space in "ro.sf.lcd_density= 220" (before "220")?

Rara, are you saying, that the space in the build-prop is the only error causing element¿?
Let's try again...

EDIT!

AAAAAAAaaaarghh! That has cost me one night, finding out, that darkrick messed up the build.prop by ONE SPACE HIT!

Rara is right: just fix your build.prop, and the skript will be fine the way it is.

Test4 is HEALED. Waht is left to accomplish are:

- HD Mode Wallpaper-misplacement until another restart.
- The WiFi Icon is fine in the "unconnected" state (when it is grey), but gets bad, when it turns blue (connected).
- Battery-Icon is a bit blurry and needs to be tuned, i guess, because it can only count in 10% steps.
- Battery stats missing.
- what else?

BTW.: What is the best free screenshot-app to be integrated?

This post has been edited by mcschweg: 12 February 2013 - 11:23 AM

[pixellegolas]

Just a small pointer, I would really like to have the n90fhd stock wallpaper back, the yellow and blue lines thingy Have lost it on the way on all the updates

[darkrickpr]

mcschweg, on 12 February 2013 - 10:56 AM, said:

Rara, are you saying, that the space in the build-prop is the only error causing element¿?
Let's try again...

EDIT!

AAAAAAAaaaarghh! That has cost me one night, finding out, that darkrick messed up the build.prop by ONE SPACE HIT!

Rara is right: just fix your build.prop, and the skript will be fine the way it is.

Test4 is HEALED. Waht is left to accomplish are:

- HD Mode Wallpaper-misplacement until another restart.
- The WiFi Icon is fine in the "unconnected" state (when it is grey), but gets bad, when it turns blue (connected).
- Battery-Icon is a bit blurry and needs to be tuned, i guess, because it can only count in 10% steps.
- Battery stats missing.
- what else?

BTW.: What is the best free screenshot-app to be integrated?

Really the problem was the the build prop having an space on the dpi jajajaj

Sent from my HTC Holiday using Tapatalk 2

[vdings]

I have to say the tablet is pretty good in its current form.

[mcschweg]

vdings, on 12 February 2013 - 03:40 PM, said:

I have to say the tablet is pretty good in its current form.

...and you are still on test3. But i can now recommend test4 for everybody, that try to decide, where to turn from stock or danerick.

So a hint for everyone else:
Until gv7t5 is released, install gv7t4 and just erase the space in front of the 220 in the dpi-line inside the build.prop file - and everything is perfect so far.
Maybe, rick can reupload a fixed t4 for starters.

This post has been edited by mcschweg: 12 February 2013 - 03:57 PM

[darkrickpr]

mcschweg, on 12 February 2013 - 03:55 PM, said:

...and you are still on test3. But i can now recommend test4 for everybody, that try to decide, where to turn from stock or danerick.

So a hint for everyone else:
Until gv7t5 is released, install gv7t4 and just erase the space in front of the 220 in the dpi-line inside the build.prop file - and everything is perfect so far.
Maybe, rick can reupload a fixed t4 for starters.

Yes I will upload the fix

Sent from my HTC Holiday using Tapatalk 2

[vdings]

Does test 4 have a performance adavantage over test 3?

Google magazines is still pretty slow in test 3.

Also can we leave out taskman, and other apps like Rom toolbox. I know that I can delete them, but its a hassle.

[mcschweg]

vdings, on 12 February 2013 - 04:04 PM, said:

Also can we leave out taskman, and other apps like Rom toolbox. I know that I can delete them, but its a hassle.

I am singing this song since test1... see my reviews above. It is not very reasonable to delete mostbof the chinware and leave these in.
We want it clean from the start, please.

Performance wise, i can not tell. And rick never mention any change, that lead to more performance....

This post has been edited by mcschweg: 12 February 2013 - 04:14 PM

[vdings]

Danke. Ich will nicht, um die ROM ändern, wenn es keine Performance-Vorteile.

[mcschweg]

vdings, on 12 February 2013 - 04:20 PM, said:

Danke. Ich will nicht, um die ROM ändern, wenn es keine Performance-Vorteile.

Not bad for a google translation Or did you learn German?

And you are right.
You do not have to update the rom, because all the changes, Rick implemented from 3 to 4, you did on foot on your own

[Mazitch]

Hi all,

Just wanted to provide my feedback after 2 days using test 3 (after using only stock Visture).

I must say it is day and night. It is my first tablet, so I don't know if tablet should run smoother, but for me it is good enough in HD, and finally good to use. I really advise people to move to it. No major issues for me, just little things that are not that annoying:
+ works fine in HD, fast enouigh and no decrease of performance over time
+ free of unwanted applications (for me the few things that are there like Super SU are goodO
+ most of google play apps work, I only had issues with quadrant and facebook so far. For facebook, was able to install through the alternative app store.
- screen orientation is sometimes changing when an application is launched (was happening with stock rom as well). Not a big deal, enough to turn the tablet around.
- battery indication is a bit weird, it went to 33% before getting over 40% without charging then down again. All in all, I have the feeling battery life might have been reduced very slightly compared to stock visture, but I may be wrong.

All in all, good job!

[mcschweg]

Mazitch, on 12 February 2013 - 04:29 PM, said:

- screen orientation is sometimes changing when an application is launched (was happening with stock rom as well). Not a big deal, enough to turn the tablet around.
- battery indication is a bit weird, it went to 33% before getting over 40% without charging then down again. All in all, I have the feeling battery life might have been reduced very slightly compared to stock visture, but I may be wrong.

First batterie: indication has to be trained. All devices have to learn, befor they are precise. So give it time.
Also, the percentage left is depending sometimes on the workload in the moment of prediction. If there is a higher workload on CPU, Screen, etc.,
the algorythm will predict a smaller percentage left, because it expect a more rapid consumption from that moment on.
So ups and downs may occur, that are not linear.

Now to the rotating screen. I also find the forced turnings of some games and apps annoying. Use rotate.apk from playstore and force the screen to keep it's rotation or even change it, when ever you like.

[vdings]

mcschweg, on 12 February 2013 - 04:28 PM, said:

Not bad for a google translation Or did you learn German?

And you are right.
You do not have to update the rom, because all the changes, Rick implemented from 3 to 4, you did on foot on your own

Yup Google translation it is. Its actually really good. I have been using it for spanish, which I am actually learning.

Could you tell the difference between google translate and a real person speaking german fluently from what I wrote?

This post has been edited by vdings: 12 February 2013 - 05:09 PM

[darkrickpr]

fixed Gv7test 4 uploaded

[mcschweg]

vdings, on 12 February 2013 - 05:06 PM, said:

Yup Google translation it is. Its actually really good. I have been using it for spanish, which I am actually learning.

Could you tell the difference between google translate and a real person speaking german fluently from what I wrote?

actually, the translation was not far from crap, but I could understand, what you wanted to say.I just wanted to be polite in case you learned it that way in school... ;-)
you / Google wrote:
Danke. Ich will nicht, um die ROM ändern, wenn es keine Performance-Vorteile.
correct sentence would be:
Danke, ich will das Rom nicht ändern, wenn es keine Performance-Vorteile gibt.
that means:
"Thanks, I do not want to change the Rom, if there are no performance advantages."


so Google or a bad German lesson was obvious :-) but nice try!

what s your native tongue?

This post has been edited by mcschweg: 13 February 2013 - 09:19 AM

[hotroderinn]

darkrickpr, on 12 February 2013 - 10:55 PM, said:

fixed Gv7test 4 uploaded

Great. Thank you very much.