Is there any way too disable the hall sensor ?
I work in a high magnetic field environment and it constantly turns the screen on/off as i move around.
Can you make a Faraday case or do you want to retain mobile phone signal?
I want to retain phone signal
Anyone?
Could it be done by editing the build.prop? Just a thought.
Actually this thread has a few solutions. It mentions building the on off into the kernel, but page two has a link to an exposed module that might work better.
http://forum.xda-developers.com/showthread.php?t=2086959
There is an xposed module that will prevent screen from turning on if proximity sensor is covered. Need root of course.
-------------------------------------------------------------------------
[ DEVICE : N5 ] [ ROM : L DEV PREVIEW ] [ KERNEL : ELEMENTALX ]
dEris said:
There is an xposed module that will prevent screen from turning on if proximity sensor is covered. Need root of course.
-------------------------------------------------------------------------
[ DEVICE : N5 ] [ ROM : L DEV PREVIEW ] [ KERNEL : ELEMENTALX ]
Click to expand...
Click to collapse
There is any way to disable it in the recovery over adb? cause I cant use the cellphone after bootscreen, it turns off screen everytime.
I search in build.prob, not
I know if I install xposed and magnetoff will solve, but i cant use the phone after boot screen, any ideas?
Hertz23 said:
There is any way to disable it in the recovery over adb? cause I cant use the cellphone after bootscreen, it turns off screen everytime.
I search in build.prob, not
I know if I install xposed and magnetoff will solve, but i cant use the phone after boot screen, any ideas?
Click to expand...
Click to collapse
i dont know if this problem persists but you can install the module via adb (don't know actually how to enable this). but you helped me finding a module that disables the sensor because it interacts badly with my car mount
Related
Hi everybody!
This thread is dedicated to containing all the kernel (and some other kernel-related) patches I create/port for our device. So I think it could help our kernel developers to focus on actual SGR-related work without worrying about examining and implementing everything that already have been created for other devices from scratch. I'll update this thread with all information whenever I do something related to the goal. I plan to make this a huge thread so please help us to keep it organized and ask common questions in the Q&A thread (in General section) or in PM (if nobody can answer your question). Thanks in advance!
BLN mod
What is BLN?
- Refer this article for more information.
What do I need to try it out on my device?
- Download my CWM-flashable zip from the following link (This installs my kernel plus my modified liblights (of course it makes a backup of the original one first)):
http://www.mediafire.com/?1cnua9uw3ckoiqk
What features does this kernel have?
version 3.1.10 (for ICS stock firmwares)
eMMC_ERASE_CAP disabled (totally safe to use)
it includes AOSP vibrator fix (it works with my pre-alpha CM10 build too) -> Hybrid kernel
Wi-Fi MAC address changing implemented
Keychord support enabled (start services using hardware keys -> revert to original MAC address by pushing 'volume down', 'volume up' and 'power' buttons simultaneously)
BLN support
- Download 'BLN Control - Free' or 'BLN Control - Pro' app from the Play Store. The pro version has some really nice additional features all of which are supported in my mod.
What do I need to enable it in my kernel?
- Apply my attached patch ('bln.patch') in your kernel source dir with 'patch -p1 < bln.patch'. This patch includes the BLN mod port from SiyahKernel3 (SGSII kernel). I removed its wakelock and earlysuspend dependency, our touchscreen driver has a different structure from that of SGSII touchscreen driver and it works without those quite well. I also added some cleanups regarding the original key led sysfs entries.
- Find 'Device Drivers->Input device support->Touchscreens->Atmel MXT224E Touchscreen Interface' in menuconfig and enable 'BLN Support' under it.
What do I need to enable it in my rom?
- Use a kernel that supports BLN.
- Extract 'system/lib/hw/lights.n1.so' from the CWM-flashable zip (in the link I previously attached) and put it into the appropriate folder.
- Optionally include BLN Control app.
Why do I need a special liblights?
- The original liblights doesn't support notifications since we don't have a led for that purpose. Epsylon3 uploaded the open source version of liblights he uses for CM7.2 to his GitHub. However, that unfortunately doesn't support stock Samsung roms (Button backlight doesn't work.), so I had to hack it a little to make it work. By default, the stock rom can set the brightness of the button backlight according to light conditions. I tried several options but didn't notice any difference in brightness, so my modified version returns 255 (0xFF) as brightness whenever it's set to some non-zero value (zero means turning it off). I also added support for BLN through the common Android notification way.
I uploaded its sources to GitHub:
https://github.com/Adam77Root/liblights_bln
Keychord support
What is it?
- If it is enabled in the kernel, init can start services triggered by hardware keys.
Why should I use it?
- I made a simple yet quite reasonable use of it. I created a service in my init.rc, which runs a script ('/system/xbin/resetmac.sh') that turns Wi-Fi off and resets the original MAC address by writing an invalid one ('13:37:13:37:13:37') into the '/efs/wifi/.mac.info' file. This runs whenever I push 'volume down' (114), 'volume up' (115) and 'power' (116) buttons simultaneously. (I had to disable bugmailer first.) You can find keycodes in '/system/usr/Generic.kl'.
- Example code ('init.rc'):
Code:
service resetmac /system/bin/sh /system/xbin/resetmac.sh
class main
disabled
oneshot
keycodes 114 115 116
- Example code ('/system/xbin/resetmac.sh') (chmod it to 700):
Code:
svc wifi disable
echo 13:37:13:37:13:37 > /efs/wifi/.mac.info
What do I need to enable it in my kernel?
- Simply enable 'Device Drivers->Input device support->Miscellaneous devices->Key chord input driver support' in menuconfig.
- Of course it has advantages only if you enable something in your init files too.
Wi-Fi MAC address changing
Please refer my previous thread for more information and on how to use/implement it.
Every custom modification to devices have risks. Use these at your own risk!
Have fun and enjoy!
---reserved---
---another one---
I'm on Frankenstein ROM 4.0.2 and ardatdat 4.2b4 right now, is it safe to flash your kernel plus bln mod directly,and do I need to mount/system before flashing and clear cache and dalvik cache after???
Sent from my GT-I9103 using Tapatalk 2
khpatel4991 said:
I'm on Frankenstein ROM 4.0.2 and ardatdat 4.2b4 right now, is it safe to flash your kernel plus bln mod directly,and do I need to mount/system before flashing and clear cache and dalvik cache after???
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
I'm on that rom too. It is safe.
Sent from my GT-I9103
I flashed the kernel,wiped cache and dalvik cache, downloaded bln mod pro but not able to understand the patch part,can you explain the procedure in detail,about how to apply the patch
Sent from my GT-I9103 using Tapatalk 2
khpatel4991 said:
I flashed the kernel,wiped cache and dalvik cache, downloaded bln mod pro but not able to understand the patch part,can you explain the procedure in detail,about how to apply the patch
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
You don't have to patch anything. That part id for kernel devs. My kernel already contains it.
Sent from my GT-I9103
This is awesome bud !
I'm yet to try cause I have to use NTFS pen drives during the next few days, will flash it after that. I had a small request if possible look into it.
I was going through dev sicopat's threads & I found that he had enabled BLN for the stock SMS app by modding it. The link to the MOD is currently down as it was uploaded on multiupload which had shut down for some time. But I'm searching for an alternate link, will notify you if I find one.
Here's the link to the ROM's thread: http://forum.xda-developers.com/showthread.php?t=1164516 (Check Post no. 2, Updates: v3.0).
If possible can you MOD the stock ICS SMS, stock ICS Samsung Email app(not Gmail) / Social Hub for enabling BLN in them ? As per Sicopat's thread as of now this can't be enabled even if we download the BLN Control Pro app & we've to use 3rd party apps. Maybe you can get in touch with him to enable the same.
Hope it'll be possible for you to do so. Cheers !
First of all thanks Adam. This is a long awaited MOD; I have been missing notification LEDs since my change from HTC to SGR.
I have installed your zip through CWM, wiped cache and dalvik cache and bought BLN control app.
The test looks fine, but I have yet to get it to work with an SMS application. I still just use the stock application which doesn't give LED notification.
But I experienced an issue with the modded kernel related to touch. It however disappeared after having the screen off for a few minutes.
When I held icons and try to move them to another position, it lost my touch after 1-1½ second. Similarly I couldn't flick halfway to a new page and hold it there for more than 1½ second.
I'll give an update if it comes back, but this is the first time I have experienced such an issue, and therefore I expected it to be related to this modification.
BR, MHCA
mhca said:
But I experienced an issue with the modded kernel related to touch. It however disappeared after having the screen off for a few minutes.
When I held icons and try to move them to another position, it lost my touch after 1-1½ second. Similarly I couldn't flick halfway to a new page and hold it there for more than 1½ second.
Click to expand...
Click to collapse
Hm, I haven't experenced such problem yet. Pls update me on this when it happens one more time and I'll investigate on it.
Sent from my GT-I9103
I'm really happy with BLN. Thanks!
It would be great if merged to a voodoo kernel.
Sent from my GT-I9103 using xda app-developers app
Thanks Adam, you are the one!
May I ask for your permission to add the BLN modification to my kernel? Thanks very much.
---------- Post added at 02:29 AM ---------- Previous post was at 01:53 AM ----------
I will try to implement it in my kernel. Thx.
Sent from my GT-I9103 using xda premium
ardatdat said:
May I ask for your permission to add the BLN modification to my kernel? Thanks very much.
Click to expand...
Click to collapse
Of course! I'm happy that you find them useful.
Sent from my GT-I9103
Adam77Root said:
Hm, I haven't experenced such problem yet. Pls update me on this when it happens one more time and I'll investigate on it.
Sent from my GT-I9103
Click to expand...
Click to collapse
I just experienced issues again. It is quite annoying when trying to hold down a key on the keyboard to type a number instead of a letter. Failed multiple times.
I then tried holding home screen icons and most of the times it just opened the application as if I had clicked them.
I don't know how you will be able to investigate it, such things can probably be hard to replicate.
Hello guys, as the title I have problems dynamic backlight display, if I disable all ok, but after a while 'time, or if I restart the phone it is as if you forget that the dynamic backlight is disabled, in fact if I go into settings as soon as I click power management system without touch anything it's alright, but after a while 'the problem recurs, it also happens to you as well? I tried searching around but nothing, can someone help me?
Thanks
P.S.: Sorry for my bad english
Up
Hi, I resolve whit an init.d script that disable permanently dynamic backlight, first of all u enable init.d, there are a lot of guides on xda and other forums, after this download script and put it in system/etc/init.d. Reboot and enjoy
Download:
https://www.dropbox.com/s/735jtz812hw3cxs/01dimmer?dl=0
Have u resolved it?
The purpose of this kernel is to provide the new features of the community to an older version of android.
To see this old version of android in its maximum splendor, trust on me, its better use kk on your smartphone than another version of android
FEATURES
for now (i am working on add some features but something gone wrong, and i think re-made everything, so keep calm)
-Fix wifi issue on dual sim version thanks to @kaminari
-Reclaim ram from loggers
-Fixed some memory leaks
-Xperience Governor WIP
-OC/UC Bus
-OC/UC GPU 600 mhz-100mhz
-OC/UC/UV CPU up to 1.6ghz-96mhz
-Compiled With Sabermod 4.7
-Fix Screen Flickering and added ULPS
Click to expand...
Click to collapse
INSTALLATION
-Install a CM-AOSP KK rom (no works on GPE and Stock)
-Flash via TWRP or CWM.
-Enjoy
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------
| If something gone wrong.... you can follow a video tutorial from How-To Basic in YT to fix your device |
| Nah just a joke, give me a logs to see what can i do for you |
--------------------------------------------------------------------------------------------------------------------------------
DOWNLOADS
-----LINK----
FOLDER ON DRIVE
https://drive.google.com/folderview?id=0Bzhj4Q-XtM6RMkJjM19uT3hvQmc
Click to expand...
Click to collapse
BUGS
None for now
Click to expand...
Click to collapse
SOURCES
https://github.com/STR4NG3R/android_kernel_motorola_msm8226-1
Click to expand...
Click to collapse
Thanks to...
@hurtsky @BryanByteZ @TeamMex @h2o64 @kaminari @Slate21&MOTOG
-And all the real developers in this community.
Recomendations for best perfomance:
ROMS:
https://forum.xda-developers.com/moto-g/development/rom-cyanogenmod-11-4-4-kernel-fixed-t3431146
https://forum.xda-developers.com/moto-g/development/rom-speedmod-slimkat-based-lollipop-t3430480
TIPS:
Since the moto g have a partition thats isnt used for nothing(/cache partittion 600mb), , you can made a swapp file into it (with the apps ram expander from google play).
Click to expand...
Click to collapse
Wifi issue
Very nice Kernel. Better than others in all respect but one. Wifi cannot be turned on. I tried wiping cache, copying CM11 wifi module, persistence, etc... None worked. Any idea?
XT1033 dual sim here. Your kernel did fix the flickering issue and stopped random rebooting. But I am reluctant to use it due to the lack of wifi.
stonelight said:
Very nice Kernel. Better than others in all respect but one. Wifi cannot be turned on. I tried wiping cache, copying CM11 wifi module, persistence, etc... None worked. Any idea?
XT1033 dual sim here. Your kernel did fix the flickering issue and stopped random rebooting. But I am reluctant to use it due to the lack of wifi.
Click to expand...
Click to collapse
So weird ://// i dont know why
Is this rom based on Render? I checked the Render kernel website http://forum.xda-developers.com/showthread.php?t=2724016 and people were complaining about wifi not enabled on KK 4.4.4 and XT1033, which is exactly my phone. Unforetunately Render stopped developping in 2014.
Now I have an ugly workaround. Two kernels work to some extent:
Render or Culcalkin: I flash boot with pre_render_boot.img, all good except wifi.
Pink: I flash recovery with pre_pink_boot.img, has wifi, but suffers from random reboot, not able to wake up sometimes, and flickering screen at boot up.
So most of time I use boot image into Culcalkin. When I really need wifi, I reboot into recovery which is indeed pink kernel.
STR4NG3R-GUY said:
So weird ://// i dont know why
Click to expand...
Click to collapse
Does it work on gpe 5.1 bootloader?
stonelight said:
Is this rom based on Render? I checked the Render kernel website http://forum.xda-developers.com/showthread.php?t=2724016 and people were complaining about wifi not enabled on KK 4.4.4 and XT1033, which is exactly my phone. Unforetunately Render stopped developping in 2014.
Now I have an ugly workaround. Two kernels work to some extent:
Render or Culcalkin: I flash boot with pre_render_boot.img, all good except wifi.
Pink: I flash recovery with pre_pink_boot.img, has wifi, but suffers from random reboot, not able to wake up sometimes, and flickering screen at boot up.
So most of time I use boot image into Culcalkin. When I really need wifi, I reboot into recovery which is indeed pink kernel.
Click to expand...
Click to collapse
maybe are based in the same sources, tell me with which kernel's you dont have thats issues to make a EXP build for you
XMoDuLeSx said:
Does it work on gpe 5.1 bootloader?
Click to expand...
Click to collapse
yes it does.
im dead right now, never drink a lot X_X
I tried too many kernels and forgot where I got that boot image . The ROM that I used is http://forum.xda-developers.com/moto-g/development/4-4-4-rom-t2826944 and its buildin kernel works with wifi (but with the flickering issue etc.). And somehow I have a boot image called pre_pink_boot.img which also works with wifi.
Your kernel is the only CM11 kernel that does not have the flickering issue on my phone. All others suffer from a moving flickering line at bootup, until I turn off screen and turn it back on again.
I heard that CM12 and above does not have those issues but I like the compactness of CM11. And Xposed is much easier on CM11.
STR4NG3R-GUY said:
maybe are based in the same sources, tell me with which kernel's you dont have thats issues to make a EXP build for you
yes it does.
im dead right now, never drink a lot X_X
Click to expand...
Click to collapse
Next update will be in december i need to dedicate all my time to my college, i learn how to add a lot of features so its a promise... Next version version will be really featured
STR4NG3R-GUY said:
So weird ://// i dont know why
Click to expand...
Click to collapse
You need to put this in your Makefile:
Code:
LDFLAGS_MODULE = --strip-debug
Otherwise the wi-fi module will be over 30 MiB in size and it'll definitely not load (the proper size for the module is no more than 4 MiB). Both your defconfig and updater-script are fine, no need to change anything inside them.
*MiB: mebibyte or binary megabyte (1024² bytes).
Edit: This line is already present in the Makefile, but it's empty.
Code:
LDFLAGS_MODULE =
You need only replace this line with mine.
wifi issue
Kamin4ri, thanks. do you have a compiled working CM11 kernel that is stable and with WIFI? Mine suffers from random reboot on XT1033.
Kamin4ri said:
You need to put this in your Makefile:
Code:
LDFLAGS_MODULE = --strip-debug
Otherwise the wi-fi module will be over 30 MiB in size and it'll definitely not load (the proper size for the module is no more than 4 MiB). Both your defconfig and updater-script are fine, no need to change anything inside them.
*MiB: mebibyte or binary megabyte (1024² bytes).
Edit: This line is already present in the Makefile, but it's empty.
Code:
LDFLAGS_MODULE =
You need only replace this line with mine.
Click to expand...
Click to collapse
Updated
what is the decryption key?
stonelight said:
what is the decryption key?
Click to expand...
Click to collapse
Moved to G-Drive
Thank you!
Not sure if you guys are seeing this over on androidforums so im posting it here too
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
************************************* Start of dev info***************************************************
kernel sources based off of v20k: https://github.com/touchpro/android_kernel_lge_stock-v20k
all the device and vendor trees are based off of teamregular's work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos13
g4stylus-common: https://github.com/touchpro/android_device_lge_g4stylus-common
vendor: https://github.com/touchpro/android_vendor_lge
also you need a few modded hardware/qcom folders, until the kernel gets updated to play nice with caf sources:
audio-caf: https://github.com/touchpro/android_hardware_qcom_audio-caf
display-caf: https://github.com/touchpro/android_hardware_qcom_display-caf
******************************************End of dev info***************************************************
I would recommend using my TWRP here to flash it: http://androidforums.com/threads/update-twrp-3-0-3-0-built-from-source-2-18-17.1103219/
what I know works:
display
touchscreen
vibration
ril (calling and texting. i cant test data since i dont have a data plan atm)
wifi
buttons
adb
mtp
panel backlight brightness adjustment
camera
video recording
internal storage
external_SD
sound
bluetooth (file transfer, audio)
youtube/netflix (any others i didnt test but i bet they work)
wired headset sound and microphone
microphone
gps/location services
compass
rotation
flashlight and camera flash
nfc (dunno what works and what doesnt, dont have another nfc device or android pay)
notification led
what doesnt work:
double tap to wake
data (manual network selection now works, im getting closer)
maybe some other things
The rom zip:
https://www.androidfilehost.com/?fid=673368273298938085
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 6.0)
THIS DOESNT COME WITH SU AND THE ONLY WORKING SU I FOUND IS SUPERSU!
Download it here: http://www.supersu.com/download
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Also,
Lineage OS 14.1 for the h631/ms631
twrp 3.1.0-0 for the h631/ms631
Hey. I flashed this rom on my friends phone. Its a metro stylo. Everything works but cellular data. Any fix for this?
Support for H635?
This is just for the US model, right? Not for the international H635?
LOS 14.1
Stonkers said:
Hey. I flashed this rom on my friends phone. Its a metro stylo. Everything works but cellular data. Any fix for this?
Click to expand...
Click to collapse
Please elaborate, did you flash this with TWRP and it's all good? I'm still running KATANA and would like to get a little more current.
Thanks!
barguybrady said:
Please elaborate, did you flash this with TWRP and it's all good? I'm still running KATANA and would like to get a little more current.
Thanks!
Click to expand...
Click to collapse
I flashed los 14 with twrp 3.1. cellular data would not work so i restored a backup. Now bluetooth, netflix and youtube wont work in katana rom. Trying to downgrade twrp and flash metro partitions to see if i can get it working.
Any updates on this rom?
Stonkers said:
I flashed los 14 with twrp 3.1. cellular data would not work so i restored a backup. Now bluetooth, netflix and youtube wont work in katana rom. Trying to downgrade twrp and flash metro partitions to see if i can get it working.
Click to expand...
Click to collapse
any updates on this ROM?
whoshotjr2006 said:
Not sure if you guys are seeing this over on androidforums so im posting it here too
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
************************************* Start of dev info***************************************************
kernel sources based off of v20k: https://github.com/touchpro/android_kernel_lge_stock-v20k
all the device and vendor trees are based off of teamregular's work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos13
g4stylus-common: https://github.com/touchpro/android_device_lge_g4stylus-common
vendor: https://github.com/touchpro/android_vendor_lge
also you need a few modded hardware/qcom folders, until the kernel gets updated to play nice with caf sources:
audio-caf: https://github.com/touchpro/android_hardware_qcom_audio-caf
display-caf: https://github.com/touchpro/android_hardware_qcom_display-caf
******************************************End of dev info***************************************************
I would recommend using my TWRP here to flash it: http://androidforums.com/threads/update-twrp-3-0-3-0-built-from-source-2-18-17.1103219/
what I know works:
display
touchscreen
vibration
ril (calling and texting. i cant test data since i dont have a data plan atm)
wifi
buttons
adb
mtp
panel backlight brightness adjustment
camera
video recording
internal storage
external_SD
sound
bluetooth (file transfer, audio)
youtube/netflix (any others i didnt test but i bet they work)
wired headset sound and microphone
microphone
gps/location services
compass
rotation
flashlight and camera flash
nfc (dunno what works and what doesnt, dont have another nfc device or android pay)
notification led
what doesnt work:
double tap to wake
data (manual network selection now works, im getting closer)
maybe some other things
The rom zip:
https://www.androidfilehost.com/?fid=673368273298938085
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 6.0)
THIS DOESNT COME WITH SU AND THE ONLY WORKING SU I FOUND IS SUPERSU!
Download it here: http://www.supersu.com/download
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hey! Why was the "android_device_lge_g4stylus-common" included to build the ROM for h631?
Rotation doesn't work, after flash the rom it work but after a few minutes the rotation not work anymore, is there any fix?
whoshotjr2006 said:
what doesnt work:
double tap to wake
data (manual network selection now works, im getting closer)
maybe some other things
Click to expand...
Click to collapse
Hey, thanks for working on this. I'm trying to get away from Metro stock ROM, but the phone is my entire Internet connection so of course I need data Does that mean it's working for you in your local kit but not in what you uploaded? Either way, I tried manual network selection and it said "registering on MetroPCS" (or equivalent, that was last night so I don't recall precisely) for about 20-30 seconds, then it very briefly flashed a scarcely-readable error message, then bumped it with a message indicating it successfully joined. But I never get a 4G or any similar symbol in the status bar, or any data, so I wondered if there's something I can do, either to force it into submission or to help you out. Thanks again
LineageOS 13 for Life One X2
This Rom was ported from the Unofficial LineageOS 13 for the Yureka Black. First I need to give credit for all the hard work the developers put into their Rom, I only modified it to work on the Blu Life One X2.
Note: Please remember I'm doing this on my own time and using my own money to cover expenses.
What Works:
Boots
Calls
SMS
Data
GPS
Wifi
Bluetooth
Audio
Video Playback
Sensors
Led
Not Working Yet:
(Please let me know if you find anything else)
Camera
Flash (works but reversed front to back)
Fingerprint
Downloads:
Builds: https://drive.google.com/drive/folders/0BzMHnGbQH3bhVnppRTdHbjZyZEk?usp=sharing (list view recommended)
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhRGhuQVNsWUFsa0k/view?usp=sharing
Kernel: https://github.com/meganukebmp/android_kernel_blu_life-one-x2
Gapps: http://opengapps.org
Special thanks to Ieatgravity and Tydraco for all their support.
Screenshots:
(screenshots taken with the PitchBlack | DarkRed CM13/12 theme)
Theme: https://apkpure.com/pitchblack-darkred-cm13-12/com.resurrectionremix.pitchblack
Changelog
Lineage-13.0-08282017-2012-UNOFFICIAL-Life_One_X2:
fixed gapps (fixed "there was a problem communicating with google servers" error)
Lineage-13.0-09042017-2137-UNOFFICIAL-Life_One_X2:
Fixed theme manager crashing
Cleaned up some of my code
Troubleshooting
Encryption Unsuccessful Screen:
Boot into TWRP and format Data (not wipe)
Reserved
Great work! I look forward to testing this.
I was using drax rom, flashed your LOS and i keep getting the encryption unsuccessful. how do i go about this?
Daisuke1988 said:
I was using drax rom, flashed your LOS and i keep getting the encryption unsuccessful. how do i go about this?
Click to expand...
Click to collapse
Go into TWRP and format Data. That fixed it for me.
srgrusso said:
Go into TWRP and format Data. That fixed it for me.
Click to expand...
Click to collapse
Thanks! now one last thing, which gapps did you use? ive tried 3 and they all fail. would it be because of the encryption thing?
Daisuke1988 said:
Thanks! now one last thing, which gapps did you use? ive tried 3 and they all fail. would it be because of the encryption thing?
Click to expand...
Click to collapse
Sorry unfortunately I haven't been able to get them working either. I've been getting "there was a problem communicating with google servers" error. I'm currently trying to fix this. I think it is related to this error from dmesg:
Code:
[ 1398.055688] type=1400 audit(1503798238.823:50): avc: denied { search } for pid=7470 comm="IntentService[P" name="com.google.android.gsf" dev="mmcblk0p46" ino=803248 scontext=u:r:untrusted_app:s0:c522,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=dir permissive=1
I have been using other apk resources for now. I'll add opengapps to the list.
Ok I think I figured out the gapps problem. I hope to have a fix tomorrow.
Here is a quick fix. Download build.prop
https://drive.google.com/file/d/0BzMHnGbQH3bhLWdIQmd4cVl6LWs/view?usp=sharing
Boot into TWRP and mount system partition rw then:
adb push build.prop system/
adb shell
chmod 644 system/build.prop
reboot
now opengapps should work.
The problem for now will be to operate the cameras correctly, in addition to the fingerprint reader ... But little by little and with this is a breakthrough
srgrusso said:
Ok I think I figured out the gapps problem. I hope to have a fix tomorrow.
Here is a quick fix. Download build.prop
https://drive.google.com/file/d/0BzMHnGbQH3bhLWdIQmd4cVl6LWs/view?usp=sharing
Boot into TWRP and mount system partition rw then:
adb push build.prop system/
adb shell
chmod 644 system/build.prop
reboot
now opengapps should work.
Click to expand...
Click to collapse
man youre awesome!
kiomet said:
The problem for now will be to operate the cameras correctly, in addition to the fingerprint reader ... But little by little and with this is a breakthrough
Click to expand...
Click to collapse
im assuming once the finger print sensor is working we can use it as gesture navigations right?
Daisuke1988 said:
im assuming once the finger print sensor is working we can use it as gesture navigations right?
Click to expand...
Click to collapse
I could be wrong, but I don't think this phone supports that. Hopefully someone will correct me if I am wrong.
New build uploaded with gapps fixed.
Lineage-13.0-08282017-2012-UNOFFICIAL-Life_One_X2.zip
srgrusso said:
I could be wrong, but I don't think this phone supports that. Hopefully someone will correct me if I am wrong.
Click to expand...
Click to collapse
Not natively. Probably will work with an additional app. But the rom itself doesn't have this built in. (not even swipe for back option from stock X2 )
ieatgravity said:
Not natively. Probably will work with an additional app. But the rom itself doesn't have this built in. (not even swipe for back option from stock X2 )
Click to expand...
Click to collapse
on the stock rom it has the option to use it as a agivation option under the finger print settings
Daisuke1988 said:
on the stock rom it has the option to use it as a agivation option under the finger print settings
Click to expand...
Click to collapse
Yes but the lineage os for this rom was ported from another phone. It wasn't compiled for our phon so the option for navigation isn't included. Now with that said. If someone would like to experiment and see if they can extract that from the stock settings and merging it with the lineage settings then maybe we can add that functionality. Either way it will be useless without a working fingerprint scanner.
ieatgravity said:
Yes but the lineage os for this rom was ported from another phone. It wasn't compiled for our phon so the option for navigation isn't included. Now with that said. If someone would like to experiment and see if they can extract that from the stock settings and merging it with the lineage settings then maybe we can add that functionality. Either way it will be useless without a working fingerprint scanner.
Click to expand...
Click to collapse
well it will come. over all, the rom is working great.