Responses to “[CM10.1][Vowney V5] CyanogenMod 10.1 Sto”

1. 

   10/01/2013
   

    

   jamesbomb on 10/02/2013 @ 8:27 am

   I'm using cm 10.1 v3.0 but I can't to record video greater 640×480. I need help to record FullHD. 

   Log in to reply.
   • 

     08/26/2013
     

      

     alex66gor on 10/03/2013 @ 10:03 pm

     Gallerygoogle.apk I replaced the Gallery2.apk (from firmware Official Vowney V5 Version: S5009_0626), is in the system> app.
     Now the camera stock.
   • 

     09/26/2014
     

      

     dilnix on 01/22/2015 @ 11:20 am

     Yes, it's a problem.

     But i don't want to replace this nice camera with stock one. May be anybody knows how to fix this? Please, just turn me in right way to find a fixing method.
2. 

   07/16/2013
   

    

   furyo on 10/02/2013 @ 2:32 pm

   On my Vowney does not work

   Log in to reply.
   • 

     07/16/2013
     

      

     furyo on 10/03/2013 @ 3:25 am

     (compas with accel_nvm )
3. 

   09/26/2013
   

    

   pLin_io on 10/04/2013 @ 6:54 pm

   Thanks Caber for your job with compass.

   I've installed several rom from here trying to set up properly the compass. Finally I get back to the original rom flashed with SP_Flash_Tool, check the /data/misc/sensors/accel_nvm file and nothing to do with compass, it seems died.

   Well, I've opened a console-terminal and

   $su

   #cd /system/bin

   #memsicd

   Voilà, compass working, Marine Compass, CPU-Z and Spirt Level Plus shows working.

   I'm still working because compass points the north always with 45 degrees to the west, and you can't stop or kill the process, only shutdown the phone, with the battery down quickly (i figure)

   I think the chip is ok, and just we need a programmer to do the correct job.

    

   Log in to reply.
   • 

     07/16/2013
     

      

     furyo on 10/04/2013 @ 7:46 pm

     LEGENDARY!! For the first time after 3 months I see the compass really work!

      
   • 

     07/16/2013
     

      

     furyo on 10/04/2013 @ 8:33 pm

     To me it works only pitch and roll, not Azimut
4. 

   08/22/2013
   

    

   george_sh on 10/04/2013 @ 10:03 pm

   Exactly, Furio. Again, azimuth here is tied to g-sensor, only this time it is not North arrow pointing to down, but South with about 45 degree shift.
   I think it is still too early to make conclusions about chip since data is being read from another sensor, not magnetic.

   Log in to reply.
5. 

   07/16/2013
   

    

   furyo on 10/08/2013 @ 12:50 am

   COMPASS: if it does not work with the ROM 626 stock, for now there is nothing to do: data files are updated directly by the kernel, if you do not update any ROM can do something.
   For those who does not work, there are two possibilities:
   A) hardware problem unsolvable – that would also explain the silence and the lack of resolution by Vowney.
   B) Hope that there is a different sensor in some phones and Vowney decides to settle down with a new kernel, after months of figures.

   Sorry for my English translated.

    

   Log in to reply.
   • 

     09/26/2013
     

      

     pLin_io on 10/09/2013 @ 8:09 pm

     Hmmm,, this is what the kernel says about sensors, type this on your terminal

     $su
     #dmesg  | grep sensor

     and you would read

     > 0) hwmsensor hwmsensor: bus resume
     > 0) image_sensor image_sensor: bus resume
     > 0) image_sensor_bus2 image_sensor_bus2: bus resume
     > 0) gsensor gsensor: bus resume

     I guess or kernel issue or bus issue. As there are lot of phones with compass working with 626 Rom, there is not a kernel issue but an I2C bus defect. Nothing to do. Enjoy your phone and forget the compass.

     Someday will be a developper patching your phone 
6. 

   08/22/2013
   

    

   george_sh on 10/10/2013 @ 9:30 am

   Strange… Mine says the following:

   u0_a135@android:/ $ su
   root@android:/ # dmesg  | grep sensor
   <4>[59414.949686] (0)[787:Binder_9]<HWMSEN> set old fastest sensor delay as workqueue base time=66
   <4>[59414.950849] (0)[753:Binder_6]<HWMSEN> set old fastest sensor delay as workqueue base time=10
   <4>[59418.699042] (0)[4074:Binder_B]<HWMSEN> set old fastest sensor delay as workqueue base time=66
   <4>[59423.827551] (0)[9080:Binder_F]<HWMSEN> set old fastest sensor delay as workqueue base time=66
   <4>[59423.828921] (0)[753:Binder_6]<HWMSEN> set old fastest sensor delay as workqueue base time=10
   <4>[59427.578495] (0)[520:Binder_3]<HWMSEN> set old fastest sensor delay as workqueue base time=66
   <4>[59432.769299] (0)[754:Binder_7]<HWMSEN> set old fastest sensor delay as workqueue base time=66
   <4>[59432.770460] (0)[1456:Binder_A]<HWMSEN> set old fastest sensor delay as workqueue base time=10
   <4>[59436.518062] (0)[747:Binder_4]<HWMSEN> set old fastest sensor delay as workqueue base time=66

   u0_a135@android:/ $ su

   root@android:/ # dmesg  | grep sensor

   <4>[59414.949686] (0)[787:Binder_9]<HWMSEN> set old fastest sensor delay as workqueue base time=66

   <4>[59414.950849] (0)[753:Binder_6]<HWMSEN> set old fastest sensor delay as workqueue base time=10

   <4>[59418.699042] (0)[4074:Binder_B]<HWMSEN> set old fastest sensor delay as workqueue base time=66

   <4>[59423.827551] (0)[9080:Binder_F]<HWMSEN> set old fastest sensor delay as workqueue base time=66

   <4>[59423.828921] (0)[753:Binder_6]<HWMSEN> set old fastest sensor delay as workqueue base time=10

   <4>[59427.578495] (0)[520:Binder_3]<HWMSEN> set old fastest sensor delay as workqueue base time=66

   <4>[59432.769299] (0)[754:Binder_7]<HWMSEN> set old fastest sensor delay as workqueue base time=66

   <4>[59432.770460] (0)[1456:Binder_A]<HWMSEN> set old fastest sensor delay as workqueue base time=10

   <4>[59436.518062] (0)[747:Binder_4]<HWMSEN> set old fastest sensor delay as workqueue base time=66

   Log in to reply.
7. 

   09/26/2013
   

    

   jltoro on 10/12/2013 @ 12:37 am

   Bluetooth no working forma me. Everything el se is fine, amazing battery life.

   Log in to reply.
8. 

   10/13/2013
   

    

   CKY1978 on 10/13/2013 @ 10:10 pm

   Installed  it, but SIM cards are not recognised.

   Baseband is "unknown", IMEI also not present and product code has become 0123456789ABCDEFG.

    

   Tried to restoreoriginal ROM , but SIM cards are not detected anymore.

    

   HELP !!!

   Log in to reply.
   • 

     09/26/2013
     

      

     pLin_io on 10/14/2013 @ 8:12 am

     Be patient, Cky. Unplug the sim, plug it and try again. Sometimes it happens, just wait a few minutes with phone on, then it ask you for pin.     
9. 

   09/08/2013
   

    

   wr400 on 10/17/2013 @ 4:41 am

   hello, have a very big bug when the phone is locked, and I click the Power button, appears to unlock, if I swipe up and down the notifications bar appears and lets get on the phone, even if you have code, solve this is  and is the best rom for this mobile phone 

   Log in to reply.
10. 

    09/22/2013
    

     

    soulfirst on 10/23/2013 @ 10:13 am

    new design is suck

    Log in to reply.