Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (6)
to General by Kalatti - 4 days, 16 hrs ago - more...
| The Following User Says Thank You to oenone For This Useful Post: | ||
|
2016-04-29
, 18:58
|
|
Posts: 602 |
Thanked: 735 times |
Joined on Mar 2011
@ Nantes, France
|
#652
|
Because you've set the good release in the OTA process and the "version dup" command didn't receive any error. Plus, if there is some changes in the SFOS GUI, you see them.
|
|
2016-04-29
, 20:54
|
|
Posts: 76 |
Thanked: 377 times |
Joined on Feb 2016
|
#653
|
I removed the builds from mediafire since those were outdated and filled with issues.
Status update on hybris-12.1:
- Phone and GPS patterns/packages are back and GPS now works.
- 2.0.0.10 builds have opaque cards on the launcher (home screen). 2.0.1.7+ builds have this issue fixed. I'm not sure if an OTA will fix the issue from a 2.0.0.10 build. Currently, I think the fix might be: "[qtdeclarative] Fix missing images when alpha and shader effects are involved. Fixes ."
- Sensors fixed: Per the suggestion of BluesLee, I tried the sensors hal (sensors.msm8974.so) from cm11.0, and it got us functional sensors. Onyx -- another cm12.1 based device -- has functional sensors with a more recent sensors hal. Testing the sensors hal and configs from onyx, all sensors work except for the proximity sensor.
Current plan:
- Work on getting transparent covers back in the 2.0.0.10 build.
- See if we can get proximity working with a more recent sensors/configs.
- Release
- Pick a repo and help on porting sfdroid changes.
Edit: If the cm11.0 sensor issue really was blob related, romu's modified llelectronics script and service can be integrated into the builds.
Edit2: I was able to get transparent cards on 2.0.0.10 by upgrading 12 qt5 packages. These upgrades are going to get bundled.
Last edited by RealJohnGalt; 2016-04-29 at 21:44.
Status update on hybris-12.1:
- Phone and GPS patterns/packages are back and GPS now works.
- 2.0.0.10 builds have opaque cards on the launcher (home screen). 2.0.1.7+ builds have this issue fixed. I'm not sure if an OTA will fix the issue from a 2.0.0.10 build. Currently, I think the fix might be: "[qtdeclarative] Fix missing images when alpha and shader effects are involved. Fixes ."
- Sensors fixed: Per the suggestion of BluesLee, I tried the sensors hal (sensors.msm8974.so) from cm11.0, and it got us functional sensors. Onyx -- another cm12.1 based device -- has functional sensors with a more recent sensors hal. Testing the sensors hal and configs from onyx, all sensors work except for the proximity sensor.
Current plan:
- Work on getting transparent covers back in the 2.0.0.10 build.
- See if we can get proximity working with a more recent sensors/configs.
- Release
- Pick a repo and help on porting sfdroid changes.
Edit: If the cm11.0 sensor issue really was blob related, romu's modified llelectronics script and service can be integrated into the builds.
Edit2: I was able to get transparent cards on 2.0.0.10 by upgrading 12 qt5 packages. These upgrades are going to get bundled
.
Last edited by RealJohnGalt; 2016-04-29 at 21:44.
| The Following 4 Users Say Thank You to RealJohnGalt For This Useful Post: | ||
|
|
2016-04-30
, 01:03
|
|
Posts: 84 |
Thanked: 146 times |
Joined on Feb 2015
|
#654
|
Originally Posted by romu
Thanks. It took either after the last try or after several reboots:
Because you've set the good release in the OTA process and the "version dup" command didn't receive any error. Plus, if there is some changes in the SFOS GUI, you see them.
The ambiance is AllBlack from Markkyboy.
| The Following User Says Thank You to oenone For This Useful Post: | ||
|
|
2016-04-30
, 07:20
|
|
Posts: 69 |
Thanked: 85 times |
Joined on Mar 2013
|
#655
|
about that sensors thing: i hope we dont have to use scripts to check errors in sensors.qcom and sensorfwd, because it's a fix that doenst work for every n5 model ...
| The Following User Says Thank You to frullewulle For This Useful Post: | ||
|
|
2016-04-30
, 16:25
|
|
Posts: 602 |
Thanked: 735 times |
Joined on Mar 2011
@ Nantes, France
|
#656
|
The problem with sensors is the following: the sensors driver may crash while the sensorfwd and sensors.qcom processes stay alive and don't eat too much CPU (it's even nearly 0%). I experienced this many times. And that's impossible to detect with a simple script. If there is a real fix, great!
| The Following 2 Users Say Thank You to romu For This Useful Post: | ||
|
|
2016-05-01
, 01:21
|
|
Posts: 84 |
Thanked: 146 times |
Joined on Feb 2015
|
#657
|
After some use I have noticed that on 2.0.1.11 the screen will turn on when the proximity sensor detects that proximal objects are no longer proximal, such as when the device is taken out of the pocket or purse.
Perhaps I am mistaken, but I do not recall this behaviour before this update.
Perhaps I am mistaken, but I do not recall this behaviour before this update.
| The Following 3 Users Say Thank You to oenone For This Useful Post: | ||
|
|
2016-05-01
, 05:53
|
|
Posts: 76 |
Thanked: 377 times |
Joined on Feb 2016
|
#658
|
Yet another sfos 2.0.0.10/hybris-12.1/cm12.1 test build:
Notes:
- Must flash sensorsfix.zip after flashing cm + sfos zips. This will be integrated into the build soon.
- Do not flash sfdroid.
- Treat it as a pure test build until more feedback is generated.
Improvements over cm-11.0 base:
- Bluetooth can stay connected, can be toggled without crashing, and can play music continuously without disconnecting or crashing.
- Camcorder and some video playback has been fixed.
Regressions:
- You might need to disable adaptation0 repo and refresh to get store working.
- Tell me.
Download:
cm12.1 snapshot: https://download.cyanogenmod.org/get...hammerhead.zip
sfos: https://www.mediafire.com/?34xk0a41lbb7x9b
sensor fix (flashable zip): http://www.mediafire.com/download/h5.../sensorfix.zip
Sources:
Kernel: https://github.com/RealJohnGalt/andr...ts/hybris-12.1
Device:
https://github.com/RealJohnGalt/andr...ts/hybris-12.1
mer-hybris stuff:
https://github.com/RealJohnGalt/droid-hal-hammerhead
https://github.com/RealJohnGalt/droid-config-hammerhead
https://github.com/RealJohnGalt/droi...ion-hammerhead
TODO
- Integrate sensors blob into build.
- Add screen gestures support to kernel using MSC_GESTURE events (DT2W, camera, etc). Looking to onyx for guidance.
- OBS!
- Work on selinux policies for enforcement.
- Add settings for device specific options such as mac address randomization.
Last edited by RealJohnGalt; 2016-05-01 at 07:54.
Notes:
- Must flash sensorsfix.zip after flashing cm + sfos zips. This will be integrated into the build soon.
- Do not flash sfdroid.
- Treat it as a pure test build until more feedback is generated.
Improvements over cm-11.0 base:
- Bluetooth can stay connected, can be toggled without crashing, and can play music continuously without disconnecting or crashing.
- Camcorder and some video playback has been fixed.
Regressions:
- You might need to disable adaptation0 repo and refresh to get store working.
- Tell me.
Download:
cm12.1 snapshot: https://download.cyanogenmod.org/get...hammerhead.zip
sfos: https://www.mediafire.com/?34xk0a41lbb7x9b
sensor fix (flashable zip): http://www.mediafire.com/download/h5.../sensorfix.zip
Sources:
Kernel: https://github.com/RealJohnGalt/andr...ts/hybris-12.1
Device:
https://github.com/RealJohnGalt/andr...ts/hybris-12.1
mer-hybris stuff:
https://github.com/RealJohnGalt/droid-hal-hammerhead
https://github.com/RealJohnGalt/droid-config-hammerhead
https://github.com/RealJohnGalt/droi...ion-hammerhead
TODO
- Integrate sensors blob into build.
- Add screen gestures support to kernel using MSC_GESTURE events (DT2W, camera, etc). Looking to onyx for guidance
.- OBS!
- Work on selinux policies for enforcement.
- Add settings for device specific options such as mac address randomization.
Last edited by RealJohnGalt; 2016-05-01 at 07:54.
|
|
2016-05-01
, 10:10
|
|
Posts: 288 |
Thanked: 1,103 times |
Joined on Jul 2014
|
#659
|
I wouldn't suggest to enable double tap to wake, it drains the battery on the nexus 5. As well as swipe to wake etc. Due to the way the touchscreen panel was made on the nexus 5 the screen has to be on to use the touchscreen as far as I know.
What you could do is use a custom kernel with a custom CPU governor.
What you could do is use a custom kernel with a custom CPU governor.
| The Following 4 Users Say Thank You to nh1402 For This Useful Post: | ||
|
|
2016-05-01
, 15:54
|
|
Posts: 76 |
Thanked: 377 times |
Joined on Feb 2016
|
#660
|
Originally Posted by nh1402
I was going to do it the way outlined in the HADK, which disables the touchscreen if the proximity sensor is in use. An alternative to DT2W could be using a sneak peak patch.
I wouldn't suggest to enable double tap to wake, it drains the battery on the nexus 5. As well as swipe to wake etc. Due to the way the touchscreen panel was made on the nexus 5 the screen has to be on to use the touchscreen as far as I know.
What you could do is use a custom kernel with a custom CPU governor.
EDIT: Here are the results for 2.0.1.11:
Last edited by oenone; 2016-04-29 at 18:52.