{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
REMEMBER TO MAKE A NANDROID BACKUP OF YOUR WORKING PHONE.
REMEMBER THAT THIS IS A TESTING VERSION.
Instructions For Flashing First time
Reboot to recovery.
Factory Reset. (wipe data,cache and dalvik cache)
You should also wipe system.
Flash the zip and reboot.
Instructions For Upgrading from Previous Nightly/RC/Stable/Milestone
Reboot to recovery.
wipe cache and dalvik cache only .
Flash the zip and reboot.
Current work process
We are working with @percy_g2 in order to bring CM12.1 up.
I'm working on the XT1524 and the following status as only been tested on this device.
Percy_g2 is working on the xt1521
This build works on XT1514, XT1521, XT1523, XT1524, XT1526, XT1527
CAUTION Flashing build from 20150503 Seems to cause problem on the CDMA version
XT1524 Status
Working
* Speaker OK
* RIL (voice OK, sms OK, Data OK)
* Camera (front OK, back OK)
* Video Recorder OK both
* Playing video recorded with the camera OK
* Auto rotation OK
* Airplane mode
* Bluetooth (detected another phone, but not tested completely)
* Wifi
* GPS
* FM
* Led notifications
Not working
* None
XT1526 Status
Working
Some issues with VM phones
Not Working
Same as above
Reporting Bugs
Tell which version you are on
Tell which phone you are on
Provide logcat
Provide DMESG
Provide a way to reproduce the issue
Binaries
Builds can be found Here
I'll be saving some particular version
here
Sources
https://github.com/CyanogenMod/android_device_motorola_surnia
Credits
CyanogenMod
cybojenix
Motorola
percy_g2
android_device_yu_tomato guys
@JoshTheAndroidUser for testing the XT1526
@sparkly_raving for the work he does on the xt1526 and boost users
XDA:DevDB Information
CM12.1 for moto E 2015, ROM for the Moto E 2015
Contributors
scritch007, jelixis, percy_g2, JoshTheAndroidUser
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP Recovery
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-04-14
Last Updated 2015-10-05
Changelog
cm-12.1-20150929-UNOFFICIAL-surnia-57.zip
Changed configuration by default to RUIM instead of NV for the CDMA. Should be all good
cm-12.1-20150927-UNOFFICIAL-surnia-54.zip
Big thanks to @StarK_raving for the CDMA tests and fixes
cm-12.1-20150921-UNOFFICIAL-surnia-53.zip
Fix USB configuration issues for mtp when adb was not activated - Thx @yelupic for the bug
Fix charger only mode when in ROM
Updated audio configuration taken from osprey
Squid2 post wifi binary blob
cm-12.1-20150917-UNOFFICIAL-52.zip
Re Add leds
Updated lights lib for batterie and notification
Batterie notification settings should be available in the settings menu
cm-12.1-20150916-UNOFFICIAL-surnia-osprey-kernel-50.zip
Use the same kernel as osprey
cm-12.1-20150913-UNOFFICIAL-surnia-ramdisk-rework-48.zip
Cleanup rootdir to match as much as possible osprey ramdisk
Removed a few services that don't bring anything.
cm-12.1-20150908-UNOFFICIAL-surnia-44.zip
CM update
Add CMActions. Now we can make the double twist to open camera app.
cm-12.1-20150906-UNOFFICIAL-surnia-43.zip
CM updates
Tried something with the ERI.xml files
cm-12.1-20150827-UNOFFICIAL-surnia-42.zip
Update of the SEPolicy all should be fine now
reverted to older prima drivers from qcom master branch
cm-12.1-20150817-UNOFFICIAL-surnia-38.zip
Fixed sensors.
CM 12.1 updates (This has the stagefright fixes)
cm-12.1-20150731-UNOFFICIAL-surnia.zip
Enable SEPolicy (This breaks sensors but all the rest works) thanks to @buzz for pull request
cm-12.1-20150716-UNOFFICIAL-surnia.zip
CM update
cm-12.1-20150705-UNOFFICIAL-surnia.zip
Fix boot on xt1526
cm-12.1-20150704-UNOFFICIAL-surnia.zip
Special @squid2 delivery. You should thanks him for finding the kernel drivers update and the error in the product name...
Fixed version in script using now xt1526 instead of xt1527
Re updated sensor to 5.1 sensor
Updated kernel stml0xx driver
cm-12.1-20150701-UNOFFICIAL-surnia.zip
Downgrade script for the sensors
Downgraded sensors to 5.0.2 version + downgraded kernel
First try to integrate the xt1527 Boost lte fix
cm-12.1-20150624-UNOFFICIAL-surnia.zip
Updated the sensors and firmware blobs so that it matches the AOSP version. Not everything is updated.
Updated kernel for matching sensors lib. This fixes the headset/speaker issue
Updated f2fs to latest motorola sources, this fixes the video recording issue
cm-12.1-20150612-UNOFFICIAL-surnia.zip
MotoDoze
Headphones fix
Added some CDMA configuration...
cm-12.1-20150523-UNOFFICIAL-surnia.zip
Update wifi drivers which used to create some reboots when unloading driver.
cm-12.1-20150518-UNOFFICIAL-surnia.zip
Add support of the xt1514
Start second daemon for dual sim devices
Modified APN configuration for CDMA to 310120 like most phones outthere
Restore the ro.telephony.default_cdma_sub=0 value
Add some eri.xml extracted from stock rom
cm-12.1-20150512-UNOFFICIAL-surnia.zip
Updated wifi firmware and kernel drivers
Removed system.prop things
Added some configuration for CDMA
cm-12.1-20150506-UNOFFICIAL-surnia.zip
BoardConfig cleanup
Added some parameters to the DHCP for the wifi (let's hope it will work for everybody) at least it fixed my broken version from the 0503
Removed the CDMA stuff I added on the 0429 because it seems it was broken starting from this version
FIxed skype microphone issue
Fixed SEPolicy it seems ok now.
cm-12.1-20150503-UNOFFICIAL-surnia.zip
Added OMX libraries. This fixes video recording on long(more then a few seconds) videos
XT1523 is a multiple sim product so set correctly information
Added properties for XT1521 factorized with the XT1523
XT1526 remove the default_sub value and added new properties... (Not tested)
Added missing Sepolicy domains
cm-12.1-20150430-UNOFFICIAL-surnia.zip
Enable FM. There is a message saying that radio is off, but it goes off after a while
Added Boost Mobile specific config in the ramdisk for CDMA
cm-12.1-20150429-UNOFFICIAL-surnia.zip
Add xt1523 initial support
Add ambient display
Add led notification when charger is plugged
Renable Sepolicy but set to permissive for NOW.
4 Cpu enabled after boot
Added some changes for CDMA but don't know the result.
Updated blobs to xt1521 version
cm-12.1-20150425-UNOFFICIAL-surnia.zip
CM12.1 bringup
Fixed GPS but meteo application says it doesn't work Installing Gapps fixes the meteo application behavior
XT1521 support started, not tested for now.
cm-12-20150418-UNOFFICIAL-surnia.zip
Updated system.prop (This fixes installing Chrome)
cm-12-20150417-UNOFFICIAL-surnia.zip
Fixed RIL Data
Small code rework
Added CDMA entries for XT1526 in the init._surnia.c still probably have to add some more things to make it work
cm-12-20150414-UNOFFICIAL-surnia.zip
Removed some error messages in the dmesg
Wifi fixed
cm-12-20150413-UNOFFICIAL-surnia.zip
Initial Version
first, yesss! great move that someone finally builds cm 12. really big thanks for that :good::victory:
CM12 already here, so cool :good::good::good:
edit: i try it, this rom is much pleasant than stock rom no doubt.
i think to keept it even if data/wifi not working.
i'm able to connect internet via bluetooth internet.
but RIL not stable sometime's loose signal
Works with Gapps 5.0 and also works with XT1526
New build is up cm-12-20150414-UNOFFICIAL-surnia.zip
Wifi is fixed and a little bit of error message cleanup.
hi
how to install?
matteo 06 said:
hi
how to install?
Click to expand...
Click to collapse
Instructions are in the "first post".
I have A bug when Changing themes
View attachment 3265303
RIL Fixed new version for XT1524 and probably XT1527
cm-12-20150417-UNOFFICIAL-surnia.zip
Fixed RIL Data
Small code rework
Added CDMA entries for XT1526 in the init._surnia.c still probably have to add some more things to make it work
Working Hard
Were working on getting CDMA Model Working with Data as fast as we can
JoshTheAndroidUser said:
Were working on getting CDMA Model Working with Data as fast as we can
Click to expand...
Click to collapse
Just a suggestion, no idea if it'd be helpful, but would looking at the CM commit that fixed data on the CDMA variants of the 1st gen Moto G be helpful?
Actually...now that im thinking more about it....i'm not sure it would be since the moto g is 3g only and the new moto e has 4g?
Hi
i have xt1524 surnia which recovery should be used? twrp 2.8.5 or 2.8.6 ?
thanks advanced
2.8
matteo 06 said:
Hi
i have xt1524 surnia which recovery should be used? twrp 2.8.5 or 2.8.6 ?
thanks advanced
Click to expand...
Click to collapse
2.8.5
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
itslels said:
Just a suggestion, no idea if it'd be helpful, but would looking at the CM commit that fixed data on the CDMA variants of the 1st gen Moto G be helpful?
Actually...now that im thinking more about it....i'm not sure it would be since the moto g is 3g only and the new moto e has 4g?
Click to expand...
Click to collapse
I don't think so since it was 3g
Loving the work scritch. Thank you thank you!
matteo 06 said:
Hi
i have xt1524 surnia which recovery should be used? twrp 2.8.5 or 2.8.6 ?
thanks advanced
Click to expand...
Click to collapse
Either use my LTE recovery (2.8.6) or use cybojenix's recovery (2.8.5).
Both will work, but mine is newer, smaller, and uses a source-built kernel.
Testing build 04/17/2015 everything seems to be working on boost mobile variant except lte. I do have 3g doe and its fastest than it used to be
bzo22 said:
Testing build 04/17/2015 everything seems to be working on boost mobile variant except lte. I do have 3g doe and its fastest than it used to be
Click to expand...
Click to collapse
Thanks For Letting Us Know New Build Coming Out Soon
Wait, what model has which code?
4G S410?
3G S200 ?
Techguy18 said:
Wait, what model has which code?
4G S410?
3G S200 ?
Click to expand...
Click to collapse
What do you mean? Are you sure this is the correct forum for your question? Must models are: xt1526, xt1527, etc...
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include
/*
* Your warranty is now void.
*
* 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.
*/
REMEMBER TO MAKE A NANDROID BACKUP OF YOUR WORKING PHONE.
REMEMBER THAT THIS IS A TESTING VERSION.
Instructions For Flashing First time
Reboot to recovery.
Factory Reset. (wipe data,cache and dalvik cache)
You should also wipe system.
Flash the zip and reboot.
Instructions For Upgrading from Previous Nightly/RC/Stable/Milestone
Reboot to recovery.
wipe cache and dalvik cache only .
Flash the zip and reboot.
Current work process
I'm working on the XT1524 and the following status as only been tested on this device.
This build works on XT1514, XT1521, XT1523, XT1524, XT1526, XT1527
This build is based on F-AOSP.
XT1524 Status
Working
* Speaker OK
* RIL (voice OK, sms OK, Data OK, 4G OK)
* Camera (front OK, back OK)
* Video Recorder OK both
* Playing video recorded with the camera OK
* Auto rotation OK
* Airplane mode
* Bluetooth (detected another phone, but not tested completely)
* Wifi
* GPS
* FM
* Led notifications (Only when plugged)
Not working
* Videos of more then 46 seconds sometimes make the camera app crash and video is not complete.
* Some issue in WiFi with DHCP but it depends of unknown (yet) parameters
* SEPolicy set to permissive
* Probably other stuffs
CDMA devices
* LTE not working
Dual sim devices
* SMS/CALL/DATA will probably not work
Reporting Bugs
Tell which version you are on
Tell which phone you are on
Provide logcat
Provide DMESG
adb shell getprop
Provide a way to reproduce the issue
Binaries
Builds can be found here
or Here
Sources
https://github.com/F-AOSP
https://github.com/Motorola-CyanogenMod/android_device_motorola_surnia
https://github.com/Motorola-CyanogenMod/android_kernel_motorola_surnia
https://github.com/Motorola-CyanogenMod/android_vendor_motorola_surnia
Check for the aosp-5.1 branch
Credits
Google
Alberto97
cybojenix
Motorola
percy_g2
XDA:DevDB Information
AOSP 5.1 for moto E 2015, ROM for the Moto E 2015
Contributors
scritch007, percy_g2
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP Recovery
Based On: AOSP
Version Information
Status: Alpha
Created 2015-05-27
Last Updated 2015-06-08
Changelog
AOSP-5.1.1-20150921-surnia-jenkins-dual-28.zip
Updated device tree with latest CM changes
Actions (Thanks to alberto97) Chop Chop is displayed but obviously not working
Using osprey kernel like cm12.1
Updated wifi binary (From squid2 post)
Latest F-AOSP changes
AOSP-5.1.1-20150721-surnia-jenkins-dual-20.zip
Same as AOSP-5.1.1-20150720-surnia-jenkins-single-18.zip
Dual sim support
AOSP-5.1.1-20150720-surnia-jenkins-single-18.zip
Updated stml0xx drivers with peregrine version
Integrate patch for the xt1526 version
Update to latest version of android
AOSP-5.1.1-20150616-surnia-jenkins.zip
The update of the sensor binary to the 5.1 was not correct regarding the 5.0.2 kernel driver. I updated the kernel to fix some of the values and now they do work, but some stuff might be broken. I have to figure out how to force flash a 5.0.2 sensor binary.
Fixed Headset
Fixed speaker
Fixed Proximity sensor
Fixed camera recording
AOSP-5.1.1-20150612-surnia-jenkins.zip
Headset Fixed
AOSP-5.1.1-20150609-surnia-jenkins.zip
This is a test build do not flash it, it has some heating issues. And eleven player doesn't work.
Updated 5.1 blobs
Added Eleven music player
AOSP-5.1.1-20150604-surnia-jenkins.zip
64Gb exfat sdcard support.
latest aosp update.
AOSP-5.1.1-20150527-surnia-benjamin.zip
Initial version
Very nice! Thx bro
xt1524
hya!
i flashed this on my rooted xt1524 with the custom squid r5 kernel (followed the xda video guide for rooting).
...immediately noticed huge improvements in performance!
then i went ahead and flashed gapps 5.1 (for google play store) as well, (i always cleared cache&dalvik after flashing) which resulted in heavy slowdowns and error messages at first, luckily now it's running smooth again! (i did however deactivate everything, except for play store, which is the only google thing i use)
next, i installed the latest alpha for xposed 5.1 , and the modules i use seem to work as they should (greenify, viper4android).
so yeah, i'm very happy now thank you big time!!
great job scritch007 , flashed this and this is my favorite rom better than cm and maybe more compatible with xposed framework. thank you
edit: drop network problem
Deleted
Sent from my Moto E 2015 LTE
I use this Rom now for a few days. Conclusion: no lags, no boot loops, camera works.
Sent from my XT1524 using XDA Free mobile app
xukashi said:
I use this Rom now for a few days. Conclusion: no lags, no boot loops, camera works.
Sent from my XT1524 using XDA Free mobile app
Click to expand...
Click to collapse
I'm using it too as my everyday rom, but I'm having some issues with the video recording, this issue I also have it on CM12.1.
If I try to record some video of more then 46 secs (I usually test with 1minute), one time out of 2 or 3 the camera app will force close. I'm still investigating on this issue but do you face it?
Hi, I have now tested the video function several times. With me everything is working. I've made several videos over 5-6 minutes. Goes without problems. But I also do not the stock app but "open Camera". Can it be that the stock App is broken?
Sent from my XT1524 using XDA Free mobile app
Earphones not working?
On the XT1527, I tested a couple of earphones and none is working. That's the biggest bummer so far for me.
Does 4g work on this ROM or no? According to another post the 4g is working but if it's built off @scritch007 build then, in my experience, 4g CDMA doesr not work.
http://www.htcmania.com/showthread.php?t=1021303
crazynapkinman said:
Does 4g work on this ROM or no? According to another post the 4g is working but if it's built off @scritch007 build then, in my experience, 4g CDMA doesr not work.
http://www.htcmania.com/showthread.php?t=1021303
Click to expand...
Click to collapse
From OP:
CDMA devices
* LTE not working
AOSP-5.1.1-20150604-surnia-jenkins.zip
64Gb exfat sdcard support.
latest aosp update.
scritch007 said:
AOSP-5.1.1-20150604-surnia-jenkins.zip
64Gb exfat sdcard support.
latest aosp update.
Click to expand...
Click to collapse
Where can I find this build? In GDrive is nothing
Sent from my XT1524 using XDA Free mobile app
xukashi said:
Where can I find this build? In GDrive is nothing
Sent from my XT1524 using XDA Free mobile app
Click to expand...
Click to collapse
I was just wondering that??
Sent from my XT1524 using XDA Free mobile app
xukashi said:
Where can I find this build? In GDrive is nothing
Sent from my XT1524 using XDA Free mobile app
Click to expand...
Click to collapse
cheffy11 said:
I was just wondering that??
Sent from my XT1524 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry forgot to update first page. Builds are available now on:
http://builds.hubdroid.com/AOSP/
hi
is MMS working?
Amazing ROM just installed latest update and wow so much smoother than your cm build
Sent from my XT1524 using XDA Free mobile app
scritch007 said:
Sorry forgot to update first page. Builds are available now on:
http://builds.hubdroid.com/AOSP/
Click to expand...
Click to collapse
Nice work
Sent from my XT1524 using XDA Free mobile app
I hope the noob question can be forgiven, but does F-AOSP include the modifications that remove the carrier-signaling when tethering?
With the stock ROM, T-Mobile can tell when I'm tethering because the stock build uses a different device to send out the tethered traffic.
CM12 normally removes this such that one can tether without strings attached. Does F-AOSP include this, or no?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This ROM is in testing stage and not ready for daily use at the moment
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@ashwin007
@Shreps
@elandoido
@vache
I used the sources from @ashwin007 as a starting point and combined them with Motorola's stock kernel sources to base this cm 13.0 build on.
Before you start
THIS ROM IS TESTED ON XT1622 UNTESTED BY DEVELOPER ON ANY OTHER MOTO G4
Code:
*
* Your warranty will be voided !
*
* 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.
*
About the ROM
Current state of ROM : BETA
What works/is Fixed
Boots
Sound (excl ringtones)
Mic
GSM (ril)
Dualsim detection XT1622
Wifi
Camera
GPS
Ringtones (no wav/mp3 support)
What is not working
Important
Single sim support not working.
Minor
Flashing red border around screen. (seems sound related)
Instructions
How to install CM13.0
If you don't have TWRP yet, get it from here : TWRP by bender1987 (Use the flash option, not just boot)
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot (Needs to be tested)
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 13.0 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
29/08/2016 - Extra prop settings in init for non dualsim XT1622 models, based on work from [user=68428475]@vache[/user].
**********
26/08/2016 - Slight prop changes in single/dual sim support. Maybe enough to get it to work on single sim. (dual works)
**********
25/08/2016 - Rild and libril build from source.
**********
24/08/2016 - Recompile, camera works again.
**********
23/08/2016 - Single sim settings (prop only) taken from XT1622 single sim and included. Build with detection. (Dual sim mode tested)
- Camera not working (something broke it)
**********
21/08/2016 - Disabled single/dual sim detection, limited 1 build to single sim for those who want to test if this could work. (20160821 build)
**********
20/08/2016 - Switched single/dual back to sim detection. (20160820 build)
- Changed default CPU governor from performance to Interactive to limit heat buildup.
**********
19/08/2016 - Switched single/dual sim check to hwrev based. Needs to be tested. (dualsim XT1622 works)
**********
18/08/2016 - Single sim needs to be tested, 2 'method' builds uploaded to test
- Enabled several decoding codecs, including aac and flac. (ringtones work better now)
- Did something not nice with sound, flashing red border around screen.
**********
17/08/2016 - Dual sim detection works (single sim detection working, sim not working)
- Memory option detection added. Settings split up between low mem (2G) and high mem (>2G) devices.
- Full cm phone support included
**********
15/08/2016 - [user=5426059]@ashwin007[/user] git a working build, cloned his device and vendor tree to learn where I went wrong and to see if I had some minor changes done correctly.
**********
05/08/2016 - First bootable image using Motorola kernel (permissive)
**********
06/07/2016 - First compile (I hope)
**********
Downloads
Latest CM 13.0 build : https://www.androidfilehost.com/?fid=24591000424960822
All CM 13.0 releases can be found here :
All CM 13.0 testing releases can be found here : https://www.androidfilehost.com/?w=files&flid=90423
All CM 13.0 beta releases can be found here :
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
All our sources can be found here : https://github.com/Moto-G4
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
CyanogenMod 13.0 for Moto G4, ROM for the Moto G4
Contributors
T_I, ashwin007, shreps, elandroido
Source Code: https://github.com/Moto-G4
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-07-06
Last Updated 2016-08-29
Ok, build failed. Used osprey (Moro G 2015) as starting point, maybe not the wisest choice. Merlin (Moto G 2015 Turbo) looks more similar. However, both based on msm8916 board. The only msm8952 basesd image I can find in cm sources is htc One A9 (hiaue), but that device is arm64, the Moto G4 (at least the one I have) only has the 32 bit libs. Uploaded current state to the git location in OP. I've build with android_device_motorola_athene, android_device_motorola_mcm8952-common and kernel-msm. (All cm-13.0 branch)
When someone has the time and experience to help, that would be nice. I'll try again day after tomorrow.
Edit: missing headers for f2fs in motorola kernel tree... those are split off in another git repo... joined them with the msm kernel and compiling again.
I find this device interesting but only if a working CM ROM exists (possibly also for Moto G4 Plus), so I plan to follow this thread. I hope in a growing community for G4/XT1622 and G4 Plus/XT1642. Interesting that I just searched for this when the ROM is not even a day old
Thanks @T_I
Waiting for beta version, so we can try it
Will this will work well on Indian Moto g4 plus variant (XT1643)
Moto G3 (?) lel is Moto G4 , any screenshots?
XT1641?
Enviado desde mi Moto G (4) mediante Tapatalk
Haven't got a clue, I've almost got the sources in a state that it'll build, we will have to wait and see if it'll boot after the build. (and after that if anything works)
can someone post a direct link to the cm13 rom i cant find it thanks
Just out of interest: how does compiling a build usually take, the way you say it, it seems like it takes quite a while (1+ hours).
[ROM][6.0.1][XT1622][UNOFFICIAL] CyanogenMod 13.0 for Moto G3 [building]
Florensie said:
Just out of interest: how does compiling a build usually take, the way you say it, it seems like it takes quite a while (1+ hours).
Click to expand...
Click to collapse
On this computer, it'll take about 2-3 hours, when it's done. I'm at the point where the kernel builds without errors, but the image itself gives some issues. Switched from osprey (Moto G3) to merlin (Moto G3 turbo) as starting point. Mainly because the turbo version is dual sim. It also has some thermal settings that re included in the tree, so I can take a peak and see how to include the thermal settings from the athene in the build. (and later how to correct them, the device is getting a bit warmer then I expected while using)
xtermmin said:
[ROM][6.0.1][XT1622][UNOFFICIAL] CyanogenMod 13.0 for Moto G3 [building]
Click to expand...
Click to collapse
1 typo found, corrected. Wouldn't be to surprised if there are more in OP.
Drat, almost there, but the build fails on the install-recovery.sh script.
Code:
Installing recovery patch to system partition
Warning: could not find SYSTEM/build.prop in <built-in function zip>
using prebuilt recovery.img from BOOTABLE_IMAGES...
using prebuilt boot.img from BOOTABLE_IMAGES...
cp: cannot stat '/usr/local/src/cm/android/system/out/target/product/athene/ota_temp/SYSTEM/bin/install-recovery.sh': No such file or directory
build/core/Makefile:1074: recipe for target '/usr/local/src/cm/android/system/out/target/product/athene/system/bin/install-recovery.sh' failed
make: *** [/usr/local/src/cm/android/system/out/target/product/athene/system/bin/install-recovery.sh] Error 1
make: Leaving directory '/usr/local/src/cm/android/system'
I'm currently look into the sources to see what should provide this script, as I can't find any references for this in my other builds. (which don't have this issue)
Edit: drat, stupid error in my sources. When you include build tree, it's nice the Android.mk will accept the device to include it... Rebuilding. With some luck this was the issue.
If that didn't work, try wih the moto x play sources...
waiting,will try it on Moto G4 plus XT1643(Indian)....
dhk.- said:
If that didn't work, try wih the moto x play sources...
Click to expand...
Click to collapse
Good one, as the merlin tree is a fork of lux, maybe a clean start is better. Last attempt for merlin, will try lux tomorrow.
Ok, switched angle of approach. Instead of rewriting an existing device, started with the twrp sources as starting point and working my way up to a setup similar to the osprey/lux/merlin setup. (separate board and device setup) First try will be compiling with the twrp sources for athene in the cm source tree. Pre build kernel and dt, nothing else.
Edit: Yes, this is the way to go. Just build the first bootable recovery from CM source. With both pre-build kernel and dt. Trying a build with kernel from sources, then dt from sources as well.
Edit 2: And broke it again. but I pin-pointed the section that breaks the build. The kernel and partitioning at least are OK, it's one of the extra modules/settings that make the mess. Will try again Thursday.
Any news?
My CM 13 - https://yadi.sk/d/-WvJyaqqtNJ2P
much does not work
is this works for g4 plus also?
is kernel 64-bit?
thx a lot
I have a G4 plus - x32 firmware
wizard-dima said:
Any news?
My CM 13 - https://yadi.sk/d/-WvJyaqqtNJ2P
much does not work
Click to expand...
Click to collapse
bugs??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a Official Build of madOS ( based on AOSP Oreo ) for Coolpad Note 3 with MTK 6753 SoC
madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.
Code:
#include
/*
* Your warranty is now void.
*
* 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.
*/
Installation Instructions:
Download ROM from M.A.D. Facebook
OR from download section
Download OpenGapps nano or pico from download section
Backup
Flash new mandatory new Oreo TWRP (available on downloads)
Boot to the new TWRP recovery
full Wipes (dont come crying if you didn't .. ;p )
Install rom (optionally following by GAPPS if you use them)
Optional: go to: wipe --> Advanced Wipe, tick 'cache' and klick 'repair or change File System' --> change File System --> F2FS --> swipe to the right (hit back several times, and proceed the same way with 'data').
Reboot System
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors (including fingerprint)
Lights; HW Keys
Both storages & MTP
HW de/encoding
Camera (photos and video)
GPS & aGPS
Audio
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Not working:
VoLTE
XDA:DevDB Information
madOS_O_CPN3, ROM for the CoolPad Note 3
Contributors
DerTeufel1980, fire855
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: twrp
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 2.1
Stable Release Date: 2017-12-31
Created 2017-12-31
Last Updated 2017-12-31
Reserved
General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP 3.2.1-0 recovery for OREO 8.1.0
http://www.mediafire.com/file/11350taybhaxbcl/twrp_coolpad_n3_oreo.img
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select Oreo TWRP> Select "Recovery" as partition to flash.
Reboot to recovery to use new one
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Update: On Oreo 8.1.0:
- We have extended Theme support even further ( madLauncher, messaging, etc)
- As well as many fixs
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: I want to report a bug(s) do you have an issue tracker?
A: Yeah... madOS issue tracker
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with :
1: Magisk ( v14 onwards.)
2: Super SU ( v2.82 onwards)
IF there are problems in rooting, you need to report it to the root-threads...There's nothing we can do
Q: Should i root together with rom ?
A: Not advised.. mainly the Magisk that gives some weird issues...
Flash ROM and GAPPS (if you use gapps), after first boot get back to recovery and flash your desire rooting method
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
A: Pretty awesome
Q: Does this build support Vulcan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A: openGapps arm64 nano/pico
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
Pure Nexus
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...
Reserved
Changelog 26h March 2018:
madOS version: 2.1.2
Build number: OPM1.171019.021 - March 2018 Security Patch Level
fixed video playback issues
improved camera quality
improved overall smoothness
tons of new options added
https://www.facebook.com/notes/mad/rom-810-official-mados-coolpad-note3-mt6753/1647790581971375/
Changelog 4th January 2018:
madOS version: 2.1.1
Improved GSM/LTE signal handling
Fixed GSM/LTE signal with GPS enabled
Added option to set QuickSettings background transparency
Fixed alarms
Fixed wallpaper scrolling setting in madLauncher
Improvements in bluetooth for A2DP
Updated included APNs list
That's what a new year gift is called.
Coolpad users happy now.....
You deserve a Thumbs up guys!!
Good work @m.a.d team
Thanks Team M.A.D, time and again you have proved that your ROMs are the best for Coolpad devices. I'm stoned to see how you release ROMs without major bugs. Hats off!! A big fan of yours. Didn't even flash a single custom ROM ever since you released Mad os Nougat back in August.
Thank you so much M.A.D. Team for all your efforts.
Happy New Year guys.
I have a made a quick video on How to install this ROM.
https://www.youtube.com/watch?v=P8GytCuFWLQ
Bugs and it's probable solutions
I am going to compile all the bugs I will encounter.
Code:
Try these on your own. These worked for me it may or may not work for you.
1. Screen Recorder is not able to save the video. (DU is saving but most of the time black and white and some yellowish lines) AZ and ScreenCam are not even saving anything.
probable solution: NONE:crying:
2. Performance lag is there. probable solution: flash magisk 15.2 and then after rebooting install latest magisk manager.:good:
e.g. Typed whole word then it shows up suddenly.
When on call it takes time to reach Home after clicking Home button
3. Network drops when GPS is on (Airtel 4G SIM).
probable solution: delete system/vendor/bin/mtk_agpsd:fingers-crossed:
I will add others when encounter.
Very Much thanks for the rom..
But facing too much network drops
Xieyt said:
Very Much thanks for the rom..
But facing too much network drops
Click to expand...
Click to collapse
I believe that network drop is due to low LTE signals of Jio and in mados we have fatser network switching when the signals are below specified limits. As Jio doesn't have any fallback networks(3g or 2g) it causes the network to entirely drop and it comes back when signals are good enough @DerTeufel1980
Gps fix ..? While using gps mobile network goes off every time
Jio 4g voice not working on cpn3 please volte pach update
Thanks!
Thanks for the ROM.....
But why is LTE Only, WCDMA Only or GSM Only modes are not working...
And zero brightness bug is also there (i mean when you move the slider to left most then the screen becomes fully dark).
RIL crash is there when an app try to access FINE_LOCATION or COURSE_LOCATION.
BKhandual said:
Thanks for the ROM.....
But why is LTE Only, WCDMA Only or GSM Only modes are not working...
And zero brightness bug is also there (i mean when you move the slider to left most then the screen becomes fully dark).
RIL crash is there when an app try to access FINE_LOCATION or COURSE_LOCATION.
Click to expand...
Click to collapse
To avoid the ril crash with GPS, you/one needs to delete system/vendor/bin/mtk_agpsd.
You need to be rooted for this...
Sent from my uhans h5000, running Android 8.0.0
DerTeufel1980 said:
To avoid the ril crash with GPS, you/one needs to delete system/vendor/bin/mtk_agpsd.
You need to be rooted for this...
Click to expand...
Click to collapse
After this will do GPS works ?
Ui is not smooth their is noticeable lag in the ui..
lovepreetsg said:
After this will do GPS works ?
Click to expand...
Click to collapse
Nope......only Agps will work like before but gps won't...
And at this time RIL is more important than gps
niks143 said:
Jio 4g voice not working on cpn3 please volte pach update
Click to expand...
Click to collapse
I am able to use Jio4gVoice on this ROM with some tweaks on my CPN3
lovepreetsg said:
After this will do GPS works ?
Click to expand...
Click to collapse
Yes. GPS is still working afterwards.
Just the agps solution from mediatek is not working then... But I don't know if it was ever working (good).
Sent from my uhans h5000, running Android 8.0.0
The ui crashes frequently.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This ROM is not actively maintained anymore! Please use LineageOS 17.1 instead: https://forum.xda-developers.com/t/...-for-the-galaxy-j7-2015-j7elte-j7e3g.4057503/
LineageOS 16.0 is a free, community built, aftermarket firmware distribution of Android 9, which is designed to increase performance and reliability over stock Android for your device. This is a port by me for the Samsung Galaxy J7 2015 and is based on the great work of @danwood76 and @Stricted.
All the source code for LineageOS is available in the LineageOS GitHub repository. And if you would like to contribute to LineageOS, please visit the project's Gerrit page. You can also view the Changelog for a full list of changes & features.
Code:
/*
* Your warranty is now void.
*
* 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.
*
*/
Working
RIL (Calls, SMS etc.)
Camera
WiFi
Bluetooth
Hotspot
GNSS
Hardware Composer
Audio
Not working
VoLTE, VoWiFi (not possible)
Supported variants
SM-J700F
SM-J700H
SM-J700M
Installation instructions
Install TWRP
Make a full phone backup if you don't want to loose your data
Wipe Cache, Dalvik Cache, Data, System partitions
Download LineageOS 16.0 and optionally GApps flashables and transfer them to the phone
Flash the zip(s). If you are choosing to use GApps, install them after the ROM.
Downloads
LineageOS 16.0 for J7 2015 (new builds): Download
LineageOS 16.0 for J7 2015 (old builds): MEGA
Google Apps: OpenGApps
Recovery: Team Win Recovery Project (TWRP)
Root: Magisk
Special thanks
@danwood76 for fixing a reboot issue that appeared when waking up the device from standby and providing me a server to build on after my Google Cloud Computing trial ended.
XDA:DevDB Information
LineageOS 16.0 for J7 2015, ROM for the Samsung Galaxy J7
Contributors
dariotr, danwood76, Stricted, alexax66, Sekilsgs2, l-0-w and all other Exynos 7580 contributors
Source Code: https://github.com/dariotrombello
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest baseband and bootloader
Version Information
Status: Stable
Stable Release Date: 2020-02-16
Created 2020-02-16
Last Updated 2020-08-10
Code:
2020-12-10
- LineageOS updates
Code:
2020-11-09
- LineageOS updates
Code:
2020-09-12
- LineageOS updates
Code:
2020-08-12
- August security patch
Code:
2020-06-06
- May security patch
- Include the AudioFX app
- Use audio configuration from A3 2016 (might improve speaker loudness and microphone gain)
Code:
2020-04-28
- Clean up and update the Ramdisk from stock
- Improve performance when using the phone while charging by disabling setting the cores to powersave
- Resolve an error in the logs by declaring only one cpu interactive path in the power HAL
Code:
2020-04-12
- April security patch
- Use new slsi source to resolve LineageOS licensing issues (thanks to danwood76 and Stricted)
- Disable mDNIe in the kernel as the J7 does not support it
- Correct AAPT screen configuration from xlarge to normal
- Increase speaker gain
Code:
2020-03-20
- Fix SIM issues by addressing rild SELinux denials
- Clean up the overlays
- Show 4G instead of LTE in the status bar to adapt to the behaviour from stock
- Add missing TS25 database binaries needed for RIL
- Set config_bluetooth_operating_voltage_mv to improve battery forecast
- March security patch
Code:
2020-02-26
- Update build fingerprints from stock
- Fix bugged battery percentage while charging by reverting a fix for A3
Code:
2020-02-20
- Fix accelerometer (rotation) by downgrading STMicroelectronics K2HH kernel driver using J700F Android 6.0 sources
Code:
2020-02-19
- Enable CONFIG_DECON_DEVFREQ in kernel
- Fix video recording using SM-J700T Android 7.1.1 camera libs
- Fix samsung lib permissions (644 => 755)
- Clean up mixer_paths.xml and increase speaker volume
- Fix mobile data by using SM-A310F libsec-ril.so and libsec-ril-dsds.so libs
- Uprevision Audio HAL from 2.0 to 4.0
- Clean up wifi configs
- Enable wifi batched scan to allow the system so scan for wifi information without waking up the device in standby
- Update display driver colour correction tables from Exynos 7870 kernel source
- Improve estimated battery life prediction
- Remove unsupported MDNIE and light sensor stuff in the overlays
- LineageOS updates
Telegram and Discord
Telegram group
@lineageosforj72015
Discord server
https://discord.gg/TBNR8Sq
error 7 TWRP
j700M ( J7elte ) any solutions ?
DarkEvinho said:
error 7 TWRP
j700M ( J7elte ) any solutions ?
Click to expand...
Click to collapse
Try to update your recovery.
Germoon said:
Try to update your recovery.
Click to expand...
Click to collapse
lastest TWRP 3.3.1-0 from twrp.me
i try downgrade for now and install again
RIL doesn't working on J700H. UI is lagging too. But video recording works.
---------- Post added at 02:33 AM ---------- Previous post was at 02:09 AM ----------
DarkEvinho said:
lastest TWRP 3.3.1-0 from twrp.me
i try downgrade for now and install again
Click to expand...
Click to collapse
I dunno. On my J700H it has successfully installed.
For those who are facing error 7 on j7
Error 7 is due to the port rom you have installed previously like (any tw-nougat based rom)
Try flashing stock rom if it is possibal
Or
Try re flashing the twrp(dosent know if this works)
Or
Remove the assert section from the updater script(this one always work)
HimanshuRaj said:
Error 7 is due to the port rom you have installed previously like (any tw-nougat based rom)
Try flashing stock rom if it is possibal
Or
Try re flashing the twrp(dosent know if this works)
Or
Remove the assert section from the updater script(this one always work)
Click to expand...
Click to collapse
I have enigmaux rom installed on my phone. I just made nandroid backup, erased all partitions and installed
Germoon said:
RIL doesn't working on J700H. UI is lagging too. But video recording works.
---------- Post added at 02:33 AM ---------- Previous post was at 02:09 AM ----------
I dunno. On my J700H it has successfully installed.
Click to expand...
Click to collapse
Calling and sending SMS should be fine. Only mobile data is currently not working. I'm not sure why UI is lagging for you. I would be happy if you could send me a logcat.
dariotr said:
Calling and sending SMS should be fine. Only mobile data is currently not working. I'm not sure why UI is lagging for you. I would be happy if you could send me a logcat.
Click to expand...
Click to collapse
Okay.
UPD: Maybe I know why RIL doesn't work. I have J700H.
This phone isn't support LTE. But, when i check connection settings, there's automatically configured LTE. How i can switch to 3G without settings??
Germoon said:
Okay.
UPD: Maybe I know why RIL doesn't work. I have J700H.
This phone isn't support LTE. But, when i check connection settings, there's automatically configured LTE. How i can switch to 3G without settings??
Click to expand...
Click to collapse
It's because I use the same device tree on J700H and J700F/J700M. Also the non-LTE variant gets the option to enable LTE but it shouldn't do anything, just ignore it. It will fall back to 3G.
Okay. So i just need to send logcat of my android??
Im sorry)) I had install wrong rom It was Los 16 too, but 2019 build test. RIL is working.
By the way, do you have any purposes, how to make mobile data work??
UI now isnt lagging too
Phone shows that mobile internet is working in tray, but the internet isnt working
Glad to see finally a Android 9 development and active post for our beloved J7's, thanks very much for that, still today I'm using my J700M for working, wish this come to stable in order to try it!
LightSpectrum said:
Glad to see finally a Android 9 development and active post for our beloved J7's, thanks very much for that, still today I'm using my J700M for working, wish this come to stable in order to try it!
Click to expand...
Click to collapse
You're right ))
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
Germoon said:
Im sorry)) I had install wrong rom It was Los 16 too, but 2019 build test. RIL is working.
By the way, do you have any purposes, how to make mobile data work??
UI now isnt lagging too
Phone shows that mobile internet is working in tray, but the internet isnt working
Click to expand...
Click to collapse
Any purposes??
Hi @dariotr
Thanks for your efforts.
The Samsung S5 Neo has the same chipset as our beloved, ageing J7 2015, aaaaand it has OFFICIAL LOS 16.
Maybe that can help?
Anyways here's the link ...... S5 Neo Official LOS16 page
dodo2244 said:
Hi @dariotr
Thanks for your efforts.
The Samsung S5 Neo has the same chipset as our beloved, ageing J7 2015, aaaaand it has OFFICIAL LOS 16.
Maybe that can help?
Anyways here's the link ...... S5 Neo Official LOS16 page
Click to expand...
Click to collapse
No. That doesn't help me. Take a guess which devices I used as base for the j7 tree...
DarkEvinho said:
error 7 TWRP
j700M ( J7elte ) any solutions ?
Click to expand...
Click to collapse
hello friends I managed to solve the problem of error 7 in twrp when installing rom lineage pie from @dariotr
I did the following:
analyzing the zip file of the lineage 8.1 compilation of @ messi2050 I noticed that there was a file called file_contexts.bin that was missing from the lineage 9.0 zip file
I copied the file and it worked, I was able to install it without problems on the j7elte (j700m port / br)
did a dirty installation of lineage 8.1 to 9.0
I haven't tested much but.
cam ok
bluetooth ok
mtp ok
flashlight ok
chips ok
mobile data ( works !)
wifi ok
incoming calls ok
autorotation does not work
autobright does not work
sorry for the bad english
Code:
[COLOR="teal"]2020-02-19[/COLOR]
- Enable CONFIG_DECON_DEVFREQ in kernel
- Fix video recording using SM-J700T Android 7.1.1 camera libs
- Fix samsung lib permissions (644 => 755)
- Clean up mixer_paths.xml and increase speaker volume
- Fix mobile data by using SM-A310F libsec-ril.so and libsec-ril-dsds.so libs
- Uprevision Audio HAL from 2.0 to 4.0
- Clean up wifi configs
- Enable wifi batched scan to allow the system so scan for wifi information without waking up the device in standby
- Update display driver colour correction tables from Exynos 7870 kernel source
- Improve estimated battery life prediction
- Remove unsupported MDNIE and light sensor stuff in the overlays
- LineageOS updates
https://drive.google.com/open?id=15myoAp1eczZE1ehFUYxndA6aEE_4Ypww
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Instructions:
Download the latest build, official TWRP (3.3.1 and newer) and GApps (if you need them)
Flash the downloaded TWRP via fastboot
Boot to recovery
Format system, vendor, data, cache, and dalvik cache
Reboot to recovery
Flash the latest build
Flash GApps and any other necessary add-ons
What's working:
WiFi
Camera and Camcorder
Bluetooth
NFC
Fingerprint - Oreo firmware required
GPS
OTG
Video Playback
Audio
RIL
VoLTE/VoWiFi
USB tethering/audio
SELinux: Enforcing
Known issues:
You tell me
Downloads:
Official builds: Download
Recovery: Official TWRP
Google Apps: OpenGApps (nano package is advisable, but you definitely should avoid using stock/super packages)
Reporting Bugs
All bugs should be reported here: Issue Tracker
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks to:
@GivFNZ for testing my builds
@wiktorek140, @karthick mostwanted, @wh0dat, @KalilDev, @AsD Monio, @GoldeneyeS2, @Steve Mathew Joy and @rajatgupta1998 for their hard work on our device sources
LineageOS team
Changelogs:
Code:
2020-11-19:
Updated kernel based on Moto's Moto One (deen) QPKS30.54-12-23 tag and CAF's LA.UM.8.6.r1-05300-89xx.0 tag
Updated Moto Actions UI
Improved boot animation speed and smoothness
Partially resolved perf HAL spam in logs
2020-11-15:
Added support for montana_retcn (XT1799-2)
Fixed a bug where the back flash wouldn't work properly when taking a photo using Snap
Fixed a bug where loudspeakers would crackle on some VoIP calls
Improved RIL stability
Improved Wi-Fi stability
Increased ZRAM to 1.33GB
Updated kernel based on Moto's Moto One (deen) QPKS30.54-12-22 tag and CAF's LA.UM.8.6.r1-04700-89xx.0 tag
Updated Moto Actions UI
November security patch
2020-10-11:
Added customizable vibration intensity in Settings > Accessibility
New FM radio app
Added support for factory reset protection (only partially effective)
Fixed boot with SELinux: Enforcing on GSIs
October security patch
2020-09-23:
Minor improvements and under the hood changes (check technical changes for more details)
2020-09-20:
Improved GPS stability
Fixed an issue where there would be random UI lag
2020-09-17:
Fixed an issue where you couldn't exit from offline charging mode
2020-09-16:
Fixed offline charging
2020-09-15:
Actually fixed random color inversion that could occur (Note: Color calibration in LiveDisplay is no longer available as a result of fixing the bug)
Fixed bootloop when enabling secure startup
Fixed manual network selection
Fixed dual SIM menu not appearing - needs testing
Mobile data settings now only displays 3 modes (LTE, 3G and 2G)
September security patch
2020-09-11:
Fixed random color inversion that could occur
2020-09-10:
Fixed Wi-Fi Display
Updated listen blobs to Q
Added support for Color profiles (Settings > Display > Colors)
Fixed an issue where you couldn't connect to certain Wi-Fi networks
2020-09-08:
Initial release.
Source code:
Common device tree: https://github.com/LineageOS/android_device_motorola_msm8937-common
Device tree: https://github.com/LineageOS/android_device_motorola_montana
Kernel: https://github.com/LineageOS/android_kernel_motorola_msm8953
Reserved
Reserved
Nice job, thanks a lot for your working on it
Thanks Jarl for keeping montana alive!
:good:
New build is up. Check OP for changelog. Downloads as always are in the OP, but you may update via the Updater app if you wish. Happy flashing! :fingers-crossed:
Just flashed it, working very fine, thanks a lot.
A minor bug I can't explain : some of the menus stay in English even if I select another language.
Will moto actions be add?
Everything else working fine
Random color inversion. Flashed last build
does this and lineage os 16 need something apart from oreo firmware? because i tried both with all twrp versions available and when rebooting after flashing zip it just always send me to the bootloader.
i have model xt1790
before i was on carbon rom and was working fine so i dont know what is wrong here, also tried lineage os from AsD Monio and works fine just the initial setup a bit buggy
recovery log: https://pastebin.com/Y0GjaHtZ
logcat right after reboting to recovery after wiping all then flashing this rom: https://pastebin.com/mvVQ12Zb
janinetavs said:
Will moto actions be add?
Everything else working fine
Click to expand...
Click to collapse
Settings > System > Advanced
janinetavs said:
Random color inversion. Flashed last build
Click to expand...
Click to collapse
v1.2? Nobody has experienced random color inversion for that one.
rakion99 said:
does this and lineage os 16 need something apart from oreo firmware? because i tried both with all twrp versions available and when rebooting after flashing zip it just always send me to the bootloader.
i have model xt1790
before i was on carbon rom and was working fine so i dont know what is wrong here, also tried lineage os from AsD Monio and works fine just the initial setup a bit buggy
recovery log: https://pastebin.com/Y0GjaHtZ
logcat right after reboting to recovery after wiping all then flashing this rom: https://pastebin.com/mvVQ12Zb
Click to expand...
Click to collapse
No, but please make sure to use the latest TWRP version. You must also format data (not wipe). Also, recovery logs won't help due to them only showing what's happening in the recovery.
Just flashed v1.2 working also fine
One question though : on the Moto Camera v6.2 app the HDR option is no more visible (it was on latest Pie builds).
Edit : persistent even when installing via the Moto Camera Thread tutorial
JarlPenguin said:
No, but please make sure to use the latest TWRP version. You must also format data (not wipe). Also, recovery logs won't help due to them only showing what's happening in the recovery.
Click to expand...
Click to collapse
rn im on latest 3.4.0-1 and i tried both format and wipe, dirty flashing from the other los 17.1 and other rom just to test but all end in always booting to bootloader menu its weird never happened something similar and only happen with your lineageos 16 and 17.1 roms
rakion99 said:
rn im on latest 3.4.0-1 and i tried both format and wipe, dirty flashing from the other los 17.1 and other rom just to test but all end in always booting to bootloader menu its weird never happened something similar and only happen with your lineageos 16 and 17.1 roms
Click to expand...
Click to collapse
Do you have full Oreo firmware installed? Also can't do anything without logs
Dan Mornill said:
Just flashed v1.2 working also fine
One question though : on the Moto Camera v6.2 app the HDR option is no more visible (it was on latest Pie builds).
Edit : persistent even when installing via the Moto Camera Thread tutorial
Click to expand...
Click to collapse
It's because we use HAL3 now. Certain functions won't work because we use deen blobs instead of stock camera blobs
janinetavs said:
Will moto actions be add?
Everything else working fine
Click to expand...
Click to collapse
They already are?
Yes they are, you have to look in the right menu
JarlPenguin said:
Do you have full Oreo firmware installed? Also can't do anything without logs
Click to expand...
Click to collapse
i didn't remember but looks like i got a old one or a fix fingerprint zip most probably, took me a day to find a working link to full 8.1 and after 2 updates from ota i got M8937_37.13.03.75R baseband and now worked perfectly your rom thank you for keeping alive our moto g5s