Does anyone know an eta or will it be even possible to make Nougat for the Galaxy S2 Plus?
there will be nougat versions.
Just wait
Nougat on S2p
No WiFi, BT, Audio, etc.
Carlos_Manuel said:
Nougat on S2p
No WiFi, BT, Audio, etc.
Click to expand...
Click to collapse
Where can I find the download link and can I flash this on GT-I9105P? Probably the thing that won't work is NFC but I don't use it anyways
Dinkec27 said:
Where can I find the download link and can I flash this on GT-I9105P? Probably the thing that won't work is NFC but I don't use it anyways
Click to expand...
Click to collapse
I haven't uploaded my nougat builds to anywhere yet. I've made several test builds and fixed some SELinux denials,etc. but there's still a lot to do.
Carlos_Manuel said:
I haven't uploaded my nougat builds to anywhere yet. I've made several test builds and fixed some SELinux denials,etc. but there's still a lot to do.
Click to expand...
Click to collapse
I will happily be your tester,if you want I can try to look for more issues,also great work on even making it bootable for the S2 Plus!
Dinkec27 said:
I will happily be your tester,if you want I can try to look for more issues,also great work on even making it bootable for the S2 Plus!
Click to expand...
Click to collapse
Here's a Nougat build for i9105:
https://drive.google.com/file/d/0B4Z8DsxsJxQqTmFrc0FSNm9ZamM/view?usp=sharing
I couldn't get BT,, Camera and WiFi working (just yet?).
in-earpiece speaker, microphone and sounds are working.
To fix RIL, flash the supersu,
http://techxat.com/download-supersu-android-7-0-nougat-root-package/
install root file manager (i.e. ES File Manager) (adb install, MTP, micro SD card or by some another method...)
Navigate to the system "/system/" and open build.prop.
Add these lines
Code:
rild.libpath=/system/lib/libbrcm_ril.so
ro.telephony.ril_class=SamsungBCMRIL
ro.telephony.call_ring.multiple=0
ro.telephony.call_ring=0
mobiledata.interfaces=rmnet0
to the build.prop below
"#
# ADDITIONAL_BUILD-PROPERTIES
#"
I am too lazy to make an another build with those props included
My next build will have those included in the build.prop.
Sources:
Device trees, vendor and kernel
https://github.com/manumanfred/android_device_samsung_galaxys2plus-common
https://github.com/manumanfred/android_device_samsung_i9105p
https://github.com/manumanfred/android_kernel_samsung_galaxys2plus-common
https://github.com/manumanfred/proprietary_vendor_samsung_galaxys2plus-common
ROM
https://github.com/Dreams-N
Carlos_Manuel said:
Here's a Nougat build for i9105:
https://drive.google.com/file/d/0B4Z8DsxsJxQqTmFrc0FSNm9ZamM/view?usp=sharing
I couldn't get BT,, Camera and WiFi working (just yet?).
in-earpiece speaker, microphone and sounds are working.
To fix RIL, flash the supersu,
http://techxat.com/download-supersu-android-7-0-nougat-root-package/
install root file manager (i.e. ES File Manager) (adb install, MTP, micro SD card or by some another method...)
Navigate to the system "/system/" and open build.prop.
Add these lines
Code:
rild.libpath=/system/lib/libbrcm_ril.so
ro.telephony.ril_class=SamsungBCMRIL
ro.telephony.call_ring.multiple=0
ro.telephony.call_ring=0
mobiledata.interfaces=rmnet0
to the build.prop below
"#
# ADDITIONAL_BUILD-PROPERTIES
#"
I am too lazy to make an another build with those props included
My next build will have those included in the build.prop.
Sources:
Device trees, vendor and kernel
https://github.com/manumanfred/android_device_samsung_galaxys2plus-common
https://github.com/manumanfred/android_device_samsung_i9105p
https://github.com/manumanfred/android_kernel_samsung_galaxys2plus-common
https://github.com/manumanfred/proprietary_vendor_samsung_galaxys2plus-common
ROM
https://github.com/Dreams-N
Click to expand...
Click to collapse
Thank you will test when I get home,great work!
Works very well except those features not working but who cares,I also noticed that the recent apps looks a bit weird,I wanted to take a screenshot but it doesn't work as well,anyways great work!
Dinkec27 said:
Works very well except those features not working but who cares,I also noticed that the recent apps looks a bit weird,I wanted to take a screenshot but it doesn't work as well,anyways great work!
Click to expand...
Click to collapse
Those looks weird, because I have not applied all the workarounds to fix rotation, screenshot, etc.
Can I somehow put Google Play on it because when I flash Gapps it bootloops?
Dinkec27 said:
Can I somehow put Google Play on it because when I flash Gapps it bootloops?
Click to expand...
Click to collapse
i tested the rom more opengapps pico and was booting fine
cracker12 said:
i tested the rom more opengapps pico and was booting fine
Click to expand...
Click to collapse
It was probably a bad download
Dinkec27 said:
Can I somehow put Google Play on it because when I flash Gapps it bootloops?
Click to expand...
Click to collapse
Sure, if you find correct gapps for it (use odexed ones), but most of the apps probably will fail to open. I'm working on the SElinux denials, but I'm not good at fixing denials... What I think, most of the SELinux rules should be made from scratch....
NFC and Bluetooth seems to be fworking now. :good:
But no sound, probably because of lib_Samsung_Resampler.so gets denied by audioserver, but in permissive SELinux mode audio should work (at least it worked and I am lazy to read my dumped logs)?
Now, also camera works (at least worked before witching to video recording and re-opening camera) and typo in hex-edited libwvn.so is fixed (symbol error).
Help from other more skilled/experienced users would be great.
Here's my new build:
https://drive.google.com/file/d/0B4Z8DsxsJxQqTHBJYlRYeEF2VVE/view?usp=sharing
Carlos_Manuel said:
Sure, if you find correct gapps for it (use odexed ones), but most of the apps probably will fail to open. I'm working on the SElinux denials, but I'm not good at fixing denials... What I think, most of the SELinux rules should be made from scratch....
NFC and Bluetooth seems to be fworking now. :good:
But no sound, probably because of lib_Samsung_Resampler.so gets denied by audioserver, but in permissive SELinux mode audio should work (at least it worked and I am lazy to read my dumped logs)?
Now, also camera works (at least worked before witching to video recording and re-opening camera) and typo in hex-edited libwvn.so is fixed (symbol error).
Help from other more skilled/experienced users would be great.
Here's my new build:
https://drive.google.com/file/d/0B4Z8DsxsJxQqTHBJYlRYeEF2VVE/view?usp=sharing
Click to expand...
Click to collapse
Great! I am not really skilled all that I've done is ported a lot of MTK ROMs and modified boot images,and ported recovery images,I tried maybe grabbing some libs from a Marshmallow ROM for S2 Plus and putting them in a flashable zip,but that ended up being a fail,the only thing that changed was it said that Wi-Fi is disabled,usually it would be blank lol
Btw did you add those lines for RIL to work to build.prop?
Yes, I did. I had screwed up one of my commits, that's why those lines didn't get included in my previous build.
Related
This development has come to a stop!
But further development is taken here.
Many thanks.
Hello everyone,
I start this thread to get some more development going on for the ZTE Blade S6.
It should encouraged others to join in or describing their own rom development for this device.
To start with I will show you my first alpha build, which means that most basic function should work now, of Cyanogenmod 12.1 for the Blade S6 (P839F30). I have the AS-Version of the device so be careful, if you have a EU Blade S6 or some other similar device. But at always be careful with your device, because I'm not responsible what you do with it, make a backup with TWRP before flashing the rom.
Things I tried:
called my phone
mobile Internet
wifi shows access Points
sound
button lights
camera working
breathing notification
Not Working:
Flash don't work when taking pictures.
UMS is not working correct
Preparation:
download unofficial CM12.1 and put it on your external sd Card
make a twrp backup
factory reset your device
optional - install this mod
install CM12.1
optional - install other region kernel - AU, EU
optional - install gapps
Credits:
Whole team of CyanogenMod https://github.com/CyanogenMod/android
lonespeaker for helping getting things started
KonstaT for TWRP
repos from piccolo-dev team, at which my work is based on.
Kernel Sources my own kernel repo
Kernel Sources ZTE
Please note this is the first time I do this, I'm still learning while doing and also some things I don't know.
Download Google drive
Updated Version 16.11.2016 using data/media as internal storage
Download links for the different kernels:
EU Version
AU Version
Previous Version 20.06.2016
10.02.2016
Concerning the wifi issue you could try the wifi zip file from fortek..see https://mega.nz/#F!c9AyURra!H4Oew0HB6JmqfPpmQ4SJqA
Something new here ??
slawoko said:
Concerning the wifi issue you could try the wifi zip file from fortek..see https://mega.nz/#F!c9AyURra!H4Oew0HB6JmqfPpmQ4SJqA
Click to expand...
Click to collapse
Hey, yes this should work. I think in the official kernel source from zte the config for wifi is missing.
Maybe they have done it any other way. Will cherry pick some commits and hope wifi will be alright then.
lightwars said:
Hey, yes this should work. I think in the official kernel source from zte the config for wifi is missing.
Maybe they have done it any other way. Will cherry pick some commits and hope wifi will be alright then.
Click to expand...
Click to collapse
If the blade is the same as the SU6, copy the pronto_wlan.ko module from stock to vendor/vodafone/p839v55/proprietary/lib/modules (or whatever you've named the directory structure) and in the BoardConfig.mk in the device tree put
BOARD_HAS_QCOM_WLAN := true
BOARD_WLAN_DEVICE := qcwcn
BOARD_HOSTAPD_DRIVER := NL80211
BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_qcwcn
BOARD_WPA_SUPPLICANT_DRIVER := NL80211
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_qcwcn
WIFI_DRIVER_MODULE_PATH := "/system/lib/modules/pronto/pronto_wlan.ko"
WIFI_DRIVER_MODULE_NAME := "wlan"
WPA_SUPPLICANT_VERSION := VER_0_8_X
That worked for the SU6.
(you might need something in the device.mk file I can't remember, give me a shout if this doesn't work).
in my cyanogenmode 12.1 for zte blade worked all. release version will be the end of the month
New Version with synced cm sources uploaded, wifi should know work.
Next step to get internal sdcard function properly and Sound working is very important.
Changes could effect that EU variant could work too, but I don't own one to test it. Please be careful.
So I think the button backlights will work in next version and I trying to get the sdcard working.
Why the sound is not working properly, I don't know at this time...
Check fortek's version may be, sound works fine there
So I got a newer build working, which has working audio. What is wired that sim card isn't detected, which seems as a problem.
Internal sdcard is accessible through file manager. And unfortunately button illumination do not work, which should be okay, I had done some tests before... So another build is needed which hopefully combine all things that work.
So.. Sim Card isnt working in this build?
And does it work properly on EU / DEU (german) Version?
DStyl3 said:
So.. Sim Card isnt working in this build?
And does it work properly on EU / DEU (german) Version?
Click to expand...
Click to collapse
Apparently yes, my sim card wasn't detected. A little bit strange, cause I didn't change so much, but anyway the other build is able of it.
I must admit that I don't own a EU or DEU version of this device, only the AS version. So I couldn't test the compatibility.
We need someone to test it to know for sure...
Update: New version is uploaded with sim working and sound... I apologize, cause I changed some vendor blobs and yes also some radio related ones, that's why it stopped working.
Great progress! Now just need the camera
eremini said:
Great progress! Now just need the camera
Click to expand...
Click to collapse
Back camera is working now, though I ran out of time getting all libs for the front camera. This will be next.
And to add it the builds only uses data/media and saddly not internal storage.
Storage issue is fixable?
eremini said:
Storage issue is fixable?
Click to expand...
Click to collapse
I think it is just a matter of mounting things right and playing with the init file.zte has just made some changes to their init files which differ from aosp.
In my opinion the better way is also to get one huge partition for userdata and data.Then what it is now,with two partitions...
lightwars said:
I think it is just a matter oft mounting rings right and playing with the init file.zte has just made some changes to their init files which differ from aosp.
In my opinion the better way is also to get one huge partition for userdata and data.Then what it is now,with two partitions...
Click to expand...
Click to collapse
Yeah I think that makes more sense. BTW serveral Russian users that tested ur firmware reported very weak wifi signal, up to the point where they couldn't connect to their wifi. May be something you want to look into.
eremini said:
Yeah I think that makes more sense. BTW serveral Russian users that tested ur firmware reported very weak wifi signal, up to the point where they couldn't connect to their wifi. May be something you want to look into.
Click to expand...
Click to collapse
Thanks for your information.That is not good. I used zte's driver...
This doesn't seem to work on the AU version... goes into a boot loop. Can anyone help?
Thanks a lot.
@lightwars , it is possible that the rom work for EU version ???, and if not, can you make it compatible ??
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
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.
ROMs with Bluetooth Fix!
For several years I have been frustrated with CM and LOS being unable to connect to my car. To compound this, most custom ROMs are based on these ROMs and use the same BT stack making it nearly impossible to find a custom ROM that works with my vehicle. I had assumed that it was hardware driver related until I found that it happened with the Oneplus 3T as well. I was beginning to lose hope.
But thankfully, it turns out that AOSPA uses a different BT stack that actually works with my car, so I spent several weeks researching ROM building and was finally able to build my favorite ROMs with AOSPA's BT stack! I have made a flashable zip using a bluetooth file found in the stock ROM to fix the issues I've been having. The zip is below. If you have a different device and would like this fix feel free to pm me to make a zip or just follow the instructions in post 2 for how to apply the fix in TWRP without a zip.
Disclaimers:
-I only have a Oneplus 3T, not a 3. This zip should work on both, but keep this in mind.
-This will only fix the issues you're having if the ROM you're taking the file from has Bluetooth that works.
BT Fix v1.2
XDA:DevDB Information
[LOS][RR][GZR] Bluetooth Fix for Existing ROMs, ROM for the OnePlus 3
Contributors
shadeau, TheCrazyLex, Thecrazyskull, arter97, xboxfanj, chrislahaye, carlosavignano, arzbhatia, scoobyjenkins, martinusbe, otisman, akhilnarang, varund7726, westcrip
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: OOS 4.1.6 or later
Based On: AOSP, LineageOS
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2017-09-20
Created 2017-06-21
Last Updated 2017-11-21
Manual Bluetooth File Replacement Instructions
1) Install the ROM with working bluetooth on your device in TWRP
2) While in TWRP (no need to boot) mount the /system folder
3) Using the file manager navigate to /system/lib/hw, select the bluetooth.default.so file, and tap copy
4) Paste this file somewhere in the base /sdcard directory where it won't be deleted when you factory reset
5) Install your favorite ROM with everything like you normally would/restore it from a backup
6) Mount /system in TWRP again (if it became unchecked or you rebooted)
7) Use the file manager to locate the bluetooth.default.so file that you just placed in your internal memory
8) Copy the file and paste it in /system/lib/hw
9) Reboot and test by connecting to device
10) Enjoy!
Troubleshooting
The flashable zip basically does three things:
1) mounts system partition
2) copies modified bluetooth file to system partition
3) unmounts system partition
4) performs update script like all zips
The zip assumes that your system partition is in the normal location (for a 3T) and formatted in ext4 for my script to work. If you have issues then try manually mounting the system partition with TWRP before flashing the zip.
Reserved2
Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Edit: Nevermind. I misunderstood what this was. Still, thank you very much! I cannot wait to try it still!
jbw716 said:
Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Click to expand...
Click to collapse
I've built full ROM zips, so you'll need to do a clean install of the ROM that you prefer and you should be good to go. Hope that helps.
Superbbbbbb Thanks, waiting for this fixing for a long time. BT with gear s.3 WORK. Please be keep update.
BTW RR Roms from your file why option in notification slider in additional buttons are difference from the link thread
Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!
plepew said:
Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!
Click to expand...
Click to collapse
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
shadeau said:
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Yes, a flashable zip would be the way to go if possible.
I will try Validus on the weekend and report back if I have success... I've installed in in the past and it's nice. But prefer Tesla due to some features.
Thanks for the quick response!
Cheers!!
shadeau said:
I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Should be doable unless framework is involved.
silentvisitor said:
Should be doable unless framework is involved.
Click to expand...
Click to collapse
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!
Would you be open to posting your sources for these builds?
Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.
Excellent job brother! I too have the same issue with my 2015 Nissan Altima. I honestly have no idea why the makers of these roms don't just use this BT stack...... OOS has no issues with my car, so why don't they all use OOS BT? Just makes no sense to me lol
jbw716 said:
Would you be open to posting your sources for these builds?
Click to expand...
Click to collapse
I'm totally open to that. But I need to figure it how to post to git first .
jbw716 said:
Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.
Click to expand...
Click to collapse
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.
shadeau said:
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!
Click to expand...
Click to collapse
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).
shadeau said:
I'm totally open to that. But I need to figure it how to post to git first .
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.
Click to expand...
Click to collapse
Here you go. I hope it helps!
https://drive.google.com/file/d/0B22KzlQ3gJRaMHhNbGVDd29JMXM/view?usp=drivesdk
silentvisitor said:
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).
Click to expand...
Click to collapse
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.
shadeau said:
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.
Click to expand...
Click to collapse
Search for "bt" and "bluetooth" in both folders and you'll get list of files. Now extract those files, make a flashable zip and test with some other ROM
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.