Jump to content


Photo

G sensor Error :(


  • Please log in to reply
30 replies to this topic

#21 miguelkorn87

miguelkorn87

    Newbie

  • Jr. Member
  • Pip
  • 2 posts

Posted 18 January 2013 - 01:15 PM

We make it easy. Enough to have the soldering station and straight arms. This can easily make professional who repairs mobile phones.


But you dont have access to the pins as they are under the chip,how did u desolder and solder them? Did u use this kind of solder station? http://www.eclipseto...gs/900-066N.JPG

How did u solve the problem of not having accede to the pins? Did u apply heat to the chip itself with the soldering pen until everything got soldered? Or did you use wires?

Sorry I ask so much, but I want to be 100% sure of the procedure not to destroy the board.

Thanks!

#22 bajie23

bajie23

    Member

  • Jr. Member
  • PipPip
  • 27 posts

Posted 27 January 2013 - 03:19 AM

Has this been resolved? Is this really hardware issue? Any software fix?

I just got this back from service warranty repair because of the battery problem, they said they replaced the board, but it looks like they installed a board with a faulty accelerometer..

Looks like im going to take this to service warranty again.. another week of wait..

Edited by bajie23, 27 January 2013 - 03:24 AM.


#23 lemiks

lemiks

    Newbie

  • Jr. Member
  • Pip
  • 7 posts

Posted 28 January 2013 - 06:57 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

#24 bajie23

bajie23

    Member

  • Jr. Member
  • PipPip
  • 27 posts

Posted 28 January 2013 - 11:49 PM

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

Voila the touch screen work great.


so this fixed touch screen problems or the g sensor issue?

i have accelerometer rotation issue, want to play with build.prop but don't know what fields to change, and what values to set..
is there anyone out there who have a Hero without rotation problems that can post or send a copy of their build.prop??

#25 lemiks

lemiks

    Newbie

  • Jr. Member
  • Pip
  • 7 posts

Posted 29 January 2013 - 02:51 AM

Fix them both, as you see in my earlier post there is 2 g sensor for hero, and the value either 0 or 5

#26 bajie23

bajie23

    Member

  • Jr. Member
  • PipPip
  • 27 posts

Posted 29 January 2013 - 11:11 PM

Fix them both, as you see in my earlier post there is 2 g sensor for hero, and the value either 0 or 5


i dont think we have the same symptoms..

i dont have touch screen problem, just that the g sensor is not working. on an app called accelerometer log, it shows that only my x axis is moving, on the graph y and z is a flatline dead.
imagine temple run 2, runner is stuck on the left side.
only way i can rotate screen is to use 3rd party app for orientation.

i tried once to edit build.prop, ro.sf.hwrotation=0 ; ro.sf.gsensorposition=2; and touch screen got messed up,
but on v1219 values, touch = ok, but still no g sensor.

im starting to think this is a hardware issue now..
ill do some more reading on build.prop and the BMA sensor and see if i can figure it out

#27 lemiks

lemiks

    Newbie

  • Jr. Member
  • Pip
  • 7 posts

Posted 30 January 2013 - 05:07 AM

The value ether 0 or 5 I saw someone posting with value of 2 but from ainol build.prop is clear the value is 0 or 5
BTW have you try the 1219 firmware? If the g sensor n work with that firmware mostly you have hardware problem. I have the hardware problem with the other ainol hero also

Edited by lemiks, 30 January 2013 - 05:10 AM.


#28 bajie23

bajie23

    Member

  • Jr. Member
  • PipPip
  • 27 posts

Posted 30 January 2013 - 10:48 AM

Thanks lemiks! Already tried v1219, same issue, good thing i have warranty.
Last time i took it there, they said they replaced the whole board for the battery issue, 3 days repair.
Good thing we have ainol service here in the Philippines.
Plus i have 1 year service warranty!
3 days without this toy again..

#29 Ahsan Khawaja

Ahsan Khawaja

    Member

  • Jr. Member
  • PipPip
  • 16 posts

Posted 31 January 2013 - 10:27 AM

Gsensor is fine in 1219

Sent from my Novo10 Hero using Tapatalk HD

#30 bajie23

bajie23

    Member

  • Jr. Member
  • PipPip
  • 27 posts

Posted 31 January 2013 - 04:47 PM

It is hardware problem for me. I dont know about other hero's, but ive switched on all official roms, and its not working.

Its safe to say that there are 2 kinds of gsensor issue.
1. Those who have switched roms (software)
2. Those who have to resolder their bma sensor. (Hardware)

too bad, luckily i have warranty. Will have my hero back in a few days.

So if anyone is having rotation problems, try 2-3 roms, pref 1219, or cm10, doing multiple wipes, and its still not fixing it, then just give up, unless you have service warranty.

Edited by bajie23, 31 January 2013 - 04:49 PM.


#31 Ahsan Khawaja

Ahsan Khawaja

    Member

  • Jr. Member
  • PipPip
  • 16 posts

Posted 31 January 2013 - 09:58 PM

It is hardware problem for me. I dont know about other hero's, but ive switched on all official roms, and its not working.

Its safe to say that there are 2 kinds of gsensor issue.
1. Those who have switched roms (software)
2. Those who have to resolder their bma sensor. (Hardware)

too bad, luckily i have warranty. Will have my hero back in a few days.

So if anyone is having rotation problems, try 2-3 roms, pref 1219, or cm10, doing multiple wipes, and its still not fixing it, then just give up, unless you have service warranty.

I personally dont like cm10 and prefer most updated stock fw.

Sent from my Novo10 Hero using Tapatalk HD




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users