SlateDroid.com: Hints for a better Ainol Hero 10 - Collection of tweaks and goodies - SlateDroid.com

Jump to content


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Hints for a better Ainol Hero 10 - Collection of tweaks and goodies

#1 User is offline   mcschweg 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 2
  • Posts: 567
  • Joined: 28-November 12
  • LocationGermany, at my WindowN90fhd 32GB

Posted 19 January 2013 - 06:36 PM

I will start this series of usable hints:

"Orientation Normalization" via build.prop

To all of you, using CM10 by Christian Troy like me (might be good for other installs also):

The default orientation of the tab is set to 270° by built.prop without reasonable cause. At least I don't need it like that.
You can see it when you start up and it lies flat on the table: screen is rotated to portrait right.
You can see it also, when you go to settings, and accessibility and disable rotation. Then it goes to default portrait right.

I would change the built.prop as follows:

ro.sf.hwrotation=0 (was 270)
ro.bootanim.hwrotation=270 <--- optional if needed
ro.sf.gsensorposition=2 (was 0)

After these changes, default orientation of the whole system is landscape and gsensor is ok again.

------------------------------------------------------------------------------------------------------
contribution: 2 hints by member "maludroid":

My first hint is regarding flashing original firmware. Do it twice this way:
1. Factory reset, clear cache and media (so called 3 wipes)
2. Flash firmware
3. Flash patch.zip
4. 3 wipes
5. Select 'reboot' in recovery. The good thing about this reboot is that it boots your system as soon as it's ready. Otherwise it reboots to recovery.
6. If Android doesn't boot, you're back in recovery, so repeat steps 1-5

Using this method I was finally able to flash November and December firmware correctly.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

My second hint is obvious but I've seen bunch of people not knowing it. You can always switch off your Hero using something thin and pushing it into micropnone hole. There's physical switch located.
-------------------------------------------------------------------------------

This post has been edited by mcschweg: 24 January 2013 - 10:45 AM

0

#2 User is offline   mzluczak 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 1
  • Joined: 07-January 13

Posted 20 January 2013 - 05:54 AM

Hi, do you know how to change a tablet to be recognized as Samsung Galaxy Tab 2 (just example) instead of Galaxy Nexus as it is set as default in CM10?
0

#3 User is offline   db260179 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 5
  • Posts: 50
  • Joined: 22-January 11

Posted 20 January 2013 - 06:52 AM

ro.bootanim.hwrotation=270 - unfortunately has no effect, bootanim is rotated the wrong way.

The rest is good

View Postmcschweg, on 19 January 2013 - 06:36 PM, said:

I will start this sseries of usable hints:

"Orientation Normalization" via build.prop

To all of you, using CM10 by Christian Troy like me (might be good for other installs also):

The default orientation of the tab is set to 270° by built.prop without reasonable cause. At least I don't need it like that.
You can see it when you start up and it lies flat on the table: screen is rotated to portrait right.
You can see it also, when you go to settings, and accessibility and disable rotation. Then it goes to default portrait right.

I would change the built.prop as follows:

ro.sf.hwrotation=0 (was 270)
ro.bootanim.hwrotation=270 <--- optional if needed
ro.sf.gsensorposition=2 (was 0)

After these changes, default orientation of the whole system is landscape and gsensor is ok again.

Android and Linux marriage made in heaven!
http://www.amazon.co...hops/db_tablets

Passionate about tablets! Love using Android and Linux
http://dbtablets.weebly.com/index.html
0

#4 User is offline   maludroid 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 4
  • Posts: 34
  • Joined: 18-January 13

Posted 20 January 2013 - 04:35 PM

View Postmcschweg, on 19 January 2013 - 06:36 PM, said:

I will start this sseries of usable hints:


I hope you will collect all hints in first post. My first hint is regarding flashing original firmware. Do it twice this way:
1. Factory reset, clear cache and media (so called 3 wipes)
2. Flash firmware
3. Flash patch.zip
4. 3 wipes
5. Select 'reboot' in recovery. The good thing about this reboot is that it boots your system as soon as it's ready. Otherwise it reboots to recovery.
6. If Android doesn't boot, you're back in recovery, so repeat steps 1-5

Using this method I was finally able to flash November and December firmware correctly.

My second hint is obvious but I've seen bunch of people not knowing it. You can always switch off your Hero using something thin and pushing it into micropnone hole. There's physical switch located.
1

#5 User is offline   mcschweg 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 2
  • Posts: 567
  • Joined: 28-November 12
  • LocationGermany, at my WindowN90fhd 32GB

Posted 24 January 2013 - 10:45 AM

View Postdb260179, on 20 January 2013 - 06:52 AM, said:

ro.bootanim.hwrotation=270 - unfortunately has no effect, bootanim is rotated the wrong way.

The rest is good

Maybe try some other values like 90 or 180 to see, if it has any effect at all.
0

#6 User is offline   Tzul 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 4
  • Posts: 385
  • Joined: 28-August 12

Posted 24 January 2013 - 01:04 PM

Or try "debug.default.dimention=1". That's a setting that Feiyu ROMs seem to have at least.
And yes, it's "dimention".
0

#7 User is offline   lemiks 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 7
  • Joined: 24-January 13

Posted 28 January 2013 - 11:47 AM

After having 2 Hero I found there is 2 different sensor they use, one is BMA 250 and newer batch they use MMA 8452

Look at the build.prop newest 1219 firmware :

ro.sf.hwrotation=270
#0~7 You are required to get the correct install direction according the sensor placement on target board
ro.sf.gsensorposition=0
#compatibility of two kind of sensors
bma250.sf.gsensorposition=0
mma8452.sf.gsensorposition=5
#ro.sf.ecompassposition=4
allow_all_orientations=1

I found weird touchscreen & G Sensor behaviour with newer batch after installing CM 10

Finally I edit : ro.sf.gsensorposition=0 Changing the value to 5

Voila the touch screen work great.

Still curious with #ro.sf.ecompassposition=4 what does it mean
1

#8 User is offline   Pantera70 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 2
  • Joined: 31-January 13

Posted 05 February 2013 - 02:12 PM

I'm also finding the camera app is now in the wrong orientation...
0

#9 User is offline   Pantera70 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 2
  • Joined: 31-January 13

Posted 05 February 2013 - 04:40 PM

I've tried setting orientation to 270 and all fine expect boot animation and camera both of which need to be adjusted back somehow but don't know what to add to build.prop. I've searched but can't find anything at the moment....
0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users