Develop Bugs

[ROM][5.1.1_r26][UNOFFICIAL]Temasek 5.1.1[BETA]

Introduction
Temasek is based on Cyanogen Mod rom ,and added more feature than Cyanogen Mod
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, or dead SD cards,
* nuclear war, penguin invasions or that you are getting fired because the alarm app failed.
* before flashing it! YOU are choosing to make these modifications, and
* If you point your finger at me for messing up your device, I will laugh at you. Hard
*/
Samsung Galaxy Fame device-specific source code :
Devicehttps://github.com/wulsic/android_device_samsung_nevisp
Kernel: Vendor: [/COLOR][URL="https://github.com/wulsic/android_vendor_samsung_nevisp"]https://github.com/wulsic/android_vendor_samsung_nevisp
Patches :
Most patches by pawitp: https://gist.github.com/pawitp/88a1d4514a0734c866c7(replace each time it says CAPRI with RHEA)
Icu4c compat for working rhea EGL driver: https://gist.github.com/Flex1911/47a9515fc482d5551a85
audioflinger patch for support old API https://gist.github.com/Flex1911/79969e4bfe06cf91b647, https://gist.github.com/Alonso1398/9eede1c631c2a88ec2fc and https://gist.github.com/Alonso1398/5d9dbb0f0eb5cc9cf25a
Not Working:
Same like CM12.1
Working:
everything is working except at Not Working list
Installation instructions
first,u need CWMR 6.0.4.9(by corsicanu or wuilsic) / TWRP 2.8.7.0
Download the zip
WIPE DATA/FACTORY RESET
Format/System
flash the rom zip from recovery
Flash gapps package or light gapps.
Reboot
Connect your phone to your pc and use adb to logcat and report it here.
Downloads
Please don't mirror to any site ,cuz everyone must see this thread and read the discussion
Please give a proper credit and thread link if you are publishing any article, video or anything related to this ROM
don't use adfly or shorten link to made money from our hard works
ROM
Android File Host
Gapps
you can use Open Gapps or any gapps ,choose PICO <because it's just include Play Store and Google Framework
How do I logcat?
See this thread how to logcat it's very easy, I suggest to be also newb friendly to use the logcat apps.
http://forum.xda-developers.com/showthread.php?t=1726238
How do I enable Dual SIM?
To enable or disable, run the following command from adb or terminal emulator and then reboot. SIM Settings can then be found in Settings -> Multi Sim Settings
Option 2 which is the fastest one is to check out this app made by @xenon92 it also has a nice UI, I hope it works on the fame else I will remove the link again:
https://github.com/xenon92/multisim-toggle/releases
Enable:
Code:
su
setprop persist.radio.multisim.config dsds
Disable:
Code:
su
setprop persist.radio.multisim.config none
Note that Dual SIM mode currently has the following limitations:
Both SIMs are always enabled (no way to disable one SIM)
"Receive incoming call while data is enabled" is always enabled
The QuickSettings tile will display the status for the currently selected SIM for data
There is no arrow activity indicator in the status bar.
Changing 2G/3G network mode using the QuickSettings toggle is not supported, only do it from Settings.
Changing 2G/3G mode in Settings may show too many options if the language used is not English. If more than 3 options is shown, only use the 3 top options (which will be WCDMA only/GSM only/WCDMA preferred regardless of the actual label shown).
3G may not work properly if Dual SIM mode is enabled with only 1 SIM inserted
Cannot set different ringtone for each SIM
Baseband version not displayed in Settings
Credits:
Google for Android before Cyanogenmod will slice them off.
The Android community for their contributions
Cyanogenmod for their Branch
@wulsic for his works! for this device to make a good device tree based on
@dhinesh77 for his Corsica source which I use as base.
@pawitp for Patches
@xenon92 for collection and patch apply script
karthick mostwanted for some kernel tweaks/other stuff.
@corsicanu
Ramsudharsan
@happyhere :*
@Alonso1398 for the patches
@flex1911 for the patches
@citrusb for fixing build kernel problem
@temasek who make temasek rom
@arter97 of course,he help temasek to made the best one
And all the betatesters and the fame community peope which are just too many to mention.
XDA:DevDB Information
Temasek 5.1.1, ROM for the Samsung Galaxy Fame
Contributors
faizauthar12, Wulsic, Karthick Mostwanted
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: latest firmware
Based On: Temasek
Version Information
Status: Beta
Current Beta Version: 20151207
Beta Release Date: 2015-12-07
Created 2015-12-07
Last Updated 2015-12-07

reserved

I'm trying to flash now, but it seems to be going much slower than usual (tried on cwm and twrp latest versions). Stuck at "detected filesystem ext4 for dev/block/mmcblk0p9". Any solutions? (same issue with both recoveries)
Update: It takes really really long, but suddenly it boots Its really smooth, thank you @faizauthar12

It has more applications is nice and soft
it does not work
the browser goes black
The camera records but the videos come in green
Sound Recorder does not work
the gapps take a long the phone
It's a great job thank you very much for your effort

U know ,the size of temasek ,500 mb : v ,so yeah it will take longer than usual

Please do something for dual sim

bhkparmar said:
Please do something for dual sim
Click to expand...
Click to collapse
give me ur RILD from stock
system/bin

faizauthar12 said:
give me ur RILD from stock
system/bin
Click to expand...
Click to collapse
I have already uploaded System/Bin from my stock rom in Cm12.1 threads, link: http://forum.xda-developers.com/showpost.php?p=63851534&postcount=123

deepakpop said:
I have already uploaded System/Bin from my stock rom in Cm12.1 threads, link: http://forum.xda-developers.com/showpost.php?p=63851534&postcount=123
Click to expand...
Click to collapse
lol xD
forget that

SIM is not working what to do???

torgashkin said:
SIM is not working what to do???
Click to expand...
Click to collapse
Not sure what model you have, but on my phone (s6810), I simply changed to single sim and voila, it works

there is a possibility of
Slim ROM 5.1.1
CARBON ROM
as has the Pocket Neo?

can't flash this rom
I try to flash this on my fame with cwmr 6.0.4.9, but while i flash this rom, i always got "error at extsdcard/rom.zip
instalation aborted
(Status 7)"
Can you help me.
Sorry for my bad english

YDroid521 said:
I try to flash this on my fame with cwmr 6.0.4.9, but while i flash this rom, i always got "error at extsdcard/rom.zip
instalation aborted
(Status 7)"
Can you help me.
Sorry for my bad english
Click to expand...
Click to collapse
Already tried CWMR 6.0.5.1 / TWRP?
Sent from my ferrari using XDA Labs

faizauthar12 said:
Already tried CWMR 6.0.5.1 / TWRP?
Sent from my ferrari using XDA Labs
Click to expand...
Click to collapse
I also use TWRP 2.8.7.0 but after I flash this rom and reboot, my phone do not want to boot, then i open twrp again and flash another rom Then reboot, its fine.
Can you tell me whats wrong with this, because i really want use this rom or tell me correct way flash with twrp.

YDroid521 said:
I also use TWRP 2.8.7.0 but after I flash this rom and reboot, my phone do not want to boot, then i open twrp again and flash another rom Then reboot, its fine.
Can you tell me whats wrong with this, because i really want use this rom or tell me correct way flash with twrp.
Click to expand...
Click to collapse
how long u wait it ??
it takes more than 30 minutes

faizauthar12 said:
how long u wait it ??
it takes more than 30 minutes
Click to expand...
Click to collapse
I wait 30 minutes or more. Can you tell me step by step flash this rom with twrp because this is first im using twrp

YDroid521 said:
I wait 30 minutes or more. Can you tell me step by step flash this rom with twrp because this is first im using twrp
Click to expand...
Click to collapse
i think
u already read the first post bro
wipe>advance wipe

ROM download page says :
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access

waheka said:
ROM download page says :
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=65918888&postcount=345

[ROM] [6.0.x] [BETA] Unofficial CyanogenMod 13.0 Nightly Builds (KIW-L24 / L22 / L21)

CyanogenMod 13.0 is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
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.
*
*/
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.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Note: This thread is not about:
- Other devices!
- General Honor 5X stuff (Unlocking, Emui, going back to Stock, Updating Stock...)
- Aliens, UFOs, ...
-> Generally: ANYTHING not specifically about CyanogenMod 13.0 for Honor 5X
Important Notice:
Code:
As of July 19, an upgrade of the firmware to MM-Firmware is required ([URL="http://forum.xda-developers.com/showpost.php?p=67840582&postcount=1813"]Link to instructions[/URL],
possibly find your firmware update here: [URL="http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288"]LINK[/URL] - note: not related to us, thanks @clsA).
If you run a device below the required firmware,
flashing will fail due to checks in the upgrade package! (No, you shouldn't remove the checks!)
In that case please use a build of July 18 or below. (Link: [URL="https://www.androidfilehost.com/?w=files&flid=72880"]clsA's repo[/URL])
Please DO NOT complain about this, we are not responsible for non-released firmwares
and other things not directly under our control. Please also DO NOT ask for any support
of firmware update in this thread! Go to Q&A section and create or use an existing thread there!
Preparation
To make sure you can run the builds from July 20 and up, please do the following
(For all commands please copy everything between the quotes not including them! All commands require to press [ENTER] to execute)
1) Open the terminal app or connect via computer and type "adb shell"
2) Type "su"
3) Type (or copy)
strings /dev/block/platform/soc.0/7824900.sdhci/by-name/tz | sed 's/QC_IMAGE_VERSION_STRING=//p;d'
4) Compare the output to:
TZ.BF.3.0.C3-00025
5) Are they equal? Go on with the instructions and use a newer build
They are different? -> Go with build of July 18
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
1) Read this post completely! Make sure you are aware of the issues!
2) Download the zip(s).
3) Install a compatible Recovery (e.g. TWRP (Link))
4) Perform a NANDroid backup of your current ROM (Optional)
5) Wipe data & cache partitions of your device (required when coming from stock!).
6) Flash CyanogenMod.
7) Optional: Install the Google Apps addon package. (Pay attention to the note in "Download links"!)
Changelog
Device tree
Kernel tree
Generic CM tree
Broken Features / Known Issues
camera does not support HDR photos - no need to try other camera apps, it's disabled completely!
dt2wake doesn't use the proximity sensor to filter bogus d2twake triggers and therefore can turn on too easily in your pocket,
but it DOES work without proximity sensor
Builds older than July 20: fingerprint sensor not implemented! (Do not even ask for it, search the thread!)
smart view case support
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
If you have a hard reboot (to the vendor boot logo, not the CM boot logo), use adb or any other file explorer tool to pull a copy of
/sys/fs/postore/console-ramoops
after the reboot and provide that.
Note: We will not support any kind of modification on the ROM not done by our sources. If you are running XPosed, Kernel Booster or whatever occurs to you, we won't support you in any way. The problem will in every case be treated as the additional softwares' fault (because often it is!)
Download Links
CyanogenMod: ROM @ http://download.crpalmer.org/nightlies/kiwi-cm-13.0
Google apps addon:
(Note: Not required to run the ROM)
We are using Open GApps (Link) Arm64 version. (make sure to use 64bit when using other packages), others might also be working
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
Note: If you install a package which replaces the default dialer (mostly "Stock Gapps") you have to go to Settings->Apps->Gear-Icon and set the new dialer as a default telephony app to prevent force closing of apps
XDA:DevDB Information
CyanogenMod 13.0 Builds, ROM for the Honor 5X
Contributors
crpalmer, BadDaemon
Source Code: https://github.com/CyanogenMod/android_kernel_huawei_kiwi
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Created 2016-03-25
Last Updated 2016-07-27

Reserved
Known Issues:
Moved to first post (above).
Other Issues:
If I don't list it as a known issue, it means I do not think it's a problem because I have never encountered whatever you think is broken.
If you post "_____ is broken", I will ignore it unless you:
* Provide appropriate logs
* Provide clear instructions to reproduce the problem or a statement that it just randomly happens
* Have the problem on a "clean" install (see below).
Getting Logs:
You can use SysLog by Tortel from the play store to get logcats (Main Log), dmesg (Kernel log) and Radio Logs. These will capture the log after the fact. You can also get the logs via adb:
PHP:
adb logcat -v time -d > logcat.txt
adb logcat -v time -b radio -d > radio.txt
adb shell dmesg > dmesg.txt
You can use either a file explorer app that allows root access or adb to get the last kernel log. Via adb you would plug your phone into a computer that has adb access to it and run
PHP:
adb root
adb pull /sys/fs/postore/console-ramoops
Appropriate Logs:
If you have a hard reboot (to the vendor boot logo, not the CM boot logo), the only log that will contain useful information if the last kernel log. All other logs are cleared on a reboot and will be useless.
If you have any issue with telephony, wifi, bluetooth or anything related to externally communicating via your phone, please provide all 3 logs (logcat, radio log and kernel log).
If you submit radio logs, please do so via a PM as the logs may contain phone numbers and other information such as your IMEI.
Clean Install:
If you have a reproducible problem:
* Backup your current install in twrp (so you can go back to it, if you want, when you're done)
* Factory reset
* Wipe system
* Install CM, install GApps (and not one that replaces system apps like the camera, especially if you think the camera is broken!)
* Do not install anything else, do not restore anything else via Google, Titanium Backup, etc.
* DO NOT INSTALL Xposed
* Install the apps that you need to reproduce the problem
* Collect logs
* Restore your backup
If the problem is not reproducible, you still need to run on a clean install and wait for it to happen. In this case do:
* Backup your current install in twrp (so you can go back to it, if you want, when you're done)
* Factory reset
* Wipe system
* Install CM, install GApps (and not one that replaces system apps like the camera, especially if you think the camera is broken!)
* Do not install anything else, do not restore anything else via Google, Titanium Backup, etc.
* Install the apps that you need on your phone via Play Store and do not restore data from anywhere or install any other tweaks, scripts.
* DO NOT INSTALL Xposed
* Wait for it to happen
* Collect logs
* Restore your backup
Note: We will not support any kind of modification on the ROM not done by our sources. If you are running XPosed, Kernel Booster or whatever occurs to you, we won't support you in any way. The problem will in every case be treated as the additional softwares' fault (because often it is!)

Reserved

So happy to see marshmallow come to this amazing device. Many thanks to all contributing

crpalmer said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Click to expand...
Click to collapse
Thanks @crpalmer. You might want to change above to 6.0.x
Sent from my A0001 using Tapatalk

Keep getting "App not responding" every few minutes. Not sure if I'm the only one.

Going to flash it right now; fingers crossed.
Thanks for your work @crpalmer

InfamousGam3r said:
Keep getting "App not responding" every few minutes. Not sure if I'm the only one.
Click to expand...
Click to collapse
Same Issue, Facebook and Messenger.

Damn bro... You're amazing.... I would love to taste marshmallow on this device but i think I'll refrain until some important bugs are fixed.... Thnx a lot for your hard work
Sent from my KIW-L21 using Tapatalk

Elmerdus said:
Same Issue, Facebook and Messenger.
Click to expand...
Click to collapse
Yep, exact same problem[emoji14]Facebook and Messenger seem to be giving that error on cm13 3/24/16
Sent from my KIW-L24 using Tapatalk

Amazing work this is the first time I'm actually using marshmallow . The rom feels a bit slower than the lolipop version, but hey having shower in the acid feels better than using the stock rom.
right now the battery indication seem to be stuck at 100%, need to reboot to check if it is actually valid.
Battery works now I have to allow all this user permissions
---------- Post added at 09:31 AM ---------- Previous post was at 09:23 AM ----------
InfamousGam3r said:
Yep, exact same problem[emoji14]Facebook and Messenger seem to be giving that error on cm13 3/24/16
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
mine works pretty well for messenger and.... restoring facebook..... yup works perfectly; I'm using custom booster so maybe?

nemexs said:
Amazing work this is the first time I'm actually using marshmallow . The rom feels a bit slower than the lolipop version, but hey having shower in the acid feels better than using the stock rom.
right now the battery indication seem to be stuck at 100%, need to reboot to check if it is actually valid.
Battery works now I have to allow all this user permissions
---------- Post added at 09:31 AM ---------- Previous post was at 09:23 AM ----------
mine works pretty well for messenger and.... restoring facebook..... yup works perfectly; I'm using custom booster so maybe?
Click to expand...
Click to collapse
What do you mean "custom booster"? I was coming from CM12.1 with GApps Arm64 5.1 Minimal, updated to CM13 (3/24/16) and GApps Arm64 6.0 Micro

InfamousGam3r said:
What do you mean "custom booster"? I was coming from CM12.1 with GApps Arm64 5.1 Minimal, updated to CM13 (3/24/16) and GApps Arm64 6.0 Micro
Click to expand...
Click to collapse
skynet project
http://forum.xda-developers.com/android/software-hacking/android-l-booster-1-soon-t3030796
The apps that didn't run properly from the titanium I reinstalled them.
For developer: Battery indicator is bugging out again, rebooting........ same problem, removed the gravity box [MM]; busybox has a problem too. Ok Google seems to crash every time I reboot.
Workaround the batter indicator bug: if you are plugged to a power charger the indicator works perfectly.
Update: busybox works with graphics just crashing, but app working well.

nemexs said:
skynet project
http://forum.xda-developers.com/android/software-hacking/android-l-booster-1-soon-t3030796
The apps that didn't run properly from the titanium I reinstalled them.
For developer: Battery indicator is bugging out again, rebooting........ same problem, removed the gravity box [MM]; busybox has a problem too. Ok Google seems to crash every time I reboot.
Workaround the batter indicator bug: if you are plugged to a power charger the indicator works perfectly.
Click to expand...
Click to collapse
Going to try and use that custom booster you linked me to, reinstalling CM13 again (reverted back to CM12 earlier because of a few issues). Doing it all fresh this time, just hate having to re-arrange my stuff haha.
Thanks,

@crpalmer , call recording works on cm13 .
Doze is working fine .
Major bugs are battery status and all CPUs online .
If you could fix this , cm13 comes to use as a daily drive .

Still getting "Unfortunately, *APP* has stopped." on CM13 3/24/16. Clean install. CM13 > GApps Arm64 6.0 nano

InfamousGam3r said:
Still getting "Unfortunately, *APP* has stopped." on CM13 3/24/16. Clean install. CM13 > GApps Arm64 6.0 nano
Click to expand...
Click to collapse
Are you l24 or l21? :/
http://opengapps.org/ This one? arm64 6.0 nano works fine for me

nemexs said:
Are you l24 or l21? :/
http://opengapps.org/ This one? arm64 6.0 nano works fine for me
Click to expand...
Click to collapse
KIW-L24
and... OpenGapps ARM64 6.0 nano.

InfamousGam3r said:
KIW-L24
and... OpenGapps ARM64 6.0 nano.
Click to expand...
Click to collapse
Maybe l24 problem? I'm using it on l21 and the only thing that's bugging is "OK Google." Have you tried redownloading it?

[ROM][6.0.1] Android 6 - Marshmallow (March 1, 2016) [WINGRAY]

Android 6.0 Marshmallow coming to a Motorola Xoom!
This ROM is for Wingray (MZ604).
It is directly based on vanilla Google Android sources. Real AOSP.
This ROM is in early alpha stage.
Download
Motorola Xoom MZ604 (Wingray) - aosp-6.0.0-latest-wingray.zip (md5sum)
Download TWRP recovery
TWRP 3.0.2
Download SuperSU
SuperSu 2.50
Download GApps
OpenGApps
Prerequisites
TWRP 3.0.2-0 or higher
Instructions
Flash TWRP 3.0.2-0 or higher.
Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
Dalvik Cache
System
Cache
Data
and wipe them. Don't reboot just yet.
Go into install.
Flash aosp-XXX.zip
Optional: Flash GAPPS.zip (Recommended) (Note: This rom is not yet gapps compatible. Skip this step for now)
Optional: Flash SuperSU.zip (Recommended)
Reboot to System
Check Settings->System Updates (Creates /sdcard/OpenDelta/FlashAfterUpdate)
Copy SuperSu and Gapps zip to /sdcard/OpenDelta/FlashAfterUpdate so that they are automatically applied after OTA update. Else your system will be unusable after an OTA!
Issues
Camera not working
HW Videodecoding not working
HDMI output not working
BT audio not working
Headphones not working
Missing GApps support
...
Tips'N'Tricks
Decrease Window/Transition animation scale and Animator duration scale to Animation off (Developer options menu)
If you install Gapps after the ROM has been booted for the first time you either need to wipe data or manually delete /data/system/users/0/runtime-permissions.xml and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
Building the source
Start here
Code:
/*
* Your warranty is now void.
*
* I will not accept responsibility for any adverse effects to your device,
* including, but not limited to: bricking, dead SD card, bootloops etc.
*
* You mod your device at your own risk.
*/
Please Donate
If you like my ROMs please donate by pressing the "Donate to Me" button below my name on the left side. It takes a lot of my spare time developing these ROMs for the community and every penny is greatly appreciated .
Donate to Me
XDA:DevDB Information
Marshmallow, ROM for the Motorola Xoom
Contributors
Schischu
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 2.6.x
ROM Firmware Required: TWRP 3.0
Based On: AOSP
Version Information
Status: Testing
Created 2016-05-11
Last Updated 2016-05-11

Just Amazing! downloading now! - Thank you.

Update online 20160511.212724
OTA support
Added microphone support
Added sdcard support
Fixed reboot to recovery
Force use of legacy dhcpclient as recommended by @Manuellama to fix wifi connectivity issues

you recomend change your 5.1 rom for this one?

thanks a lot again @Shishu
moving superfast now!
p.s. maybe how to flash the recovery from the other thread should be in the first post
unpack twrp.tar
fastboot flash recovery recovery.img
fastboot reboot
keep system partition read only can be put to YES in twrp
the last step is confusing put gapps into opendelta folder even though they dont work?
p.s. i wonder whats with the gapps since it worked for me on the old rom for 2 days with banks gapps
but when flashing supersu i would get google services have stopped errors
before that i could download apps and update them - oh well will work with es explorer backups
of my apps for now (if only the rom would have a filemanager so one could install apps right away
without adb)
p.s.s is superfun to have marshmallow on a tablet from 2011 that came out with android 3.0 back then
this is fighting obsolescence at its best!

This sounds awesome, but I might hold off until the headphones and HW Video Decoding are functional.
Thanks!

i dont wanna get on shishus nerves all the time so he can do his work quitely
but maybe someone else can help?
after adb installing es explorer and installing backed up apks
it crashed when installing dolphin
it rebooted and then it got can't start android phone services
permanently
will try to adb install the the sideloaded apks and report back

ok now i got it working
via adb install:
es file explorer
vlc
trickster mod (overclocking to 1400 mhz)
sandmann (german app old xoom version)
quick boot (booting into recovery now works)
netflix (woow drm already working)
via es file explorer install apk:
busybox on rails (trickster mod needs a busybox)
ard mediathek (german app)
nova launcher
dolphin (turn jetpack off in settings)
p.s. tip take twrp backups often when installing stuff as its really fragile right now

This is just nuts! There's hardly any people left with a working Xoom, it's just really cool to see a 6.0 build for this device. I'm totally going to flash this, haven't turned my Xoom in a few months but I'd never get rid of it

Fastboot flashed TWRP 3.0, however the Xoom hangs on Entering Android Recovery Mode. Flashing back to TWRP 2.8.6.0-bigpart, and the device boots into TWRP as expected. Running CM 11.
Did I miss a step?
Ta!

i was upgrading from TWRP 2.7.1.0 touch recovery [2014-7-4] BigPart F2FS support sucessfully
dont know what could cause it - maybe try again?

I have gapps working on @Schischu Android 6.0.
You have to add this to build.prop.
ro.setupwizard.mode = disabled
If you want to avoid endless error notifications of setupwizard has stopped. and google play services has stopped.

i tried this following this guide
http://forum.xda-developers.com/showthread.php?t=1948558
setting it to the last line of build.prop then saving rebooting into recovery
and installing mentioned opengoggleapps from the thread i get
setup wizard and google play services has stopped and setup wizard has stopped errors
p.s. i can see it with adb shell and cd system less build.prop
at the end of the file yet it doesnt seem to work

You will add suport for 3g?

Whaaat??! SERIOUSLY? You are a genius man. Thank you @Schischu

lfpeacemaker said:
You will add suport for 3g?
Click to expand...
Click to collapse
If it's a wingray ROM, then no. Because the wingray doesn't have 3g.

Hi, why are you using elementalx-xoom kernel 2.0 if has 2.1? @Schischu
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
briandotcom0 said:
If it's a wingray ROM, then no. Because the wingray doesn't have 3g.
Click to expand...
Click to collapse
Thank you

....and why do you propose SuperSu 2.50 and not 2.71?

lfpeacemaker said:
You will add suport for 3g?
Click to expand...
Click to collapse
Maybe, but it way down the list.
lfpeacemaker said:
Hi, why are you using elementalx-xoom kernel 2.0 if has 2.1? @Schischu
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
Thank you
Click to expand...
Click to collapse
It's based on 2.1, the version number is just wrong.
Peterpaulmarie said:
....and why do you propose SuperSu 2.50 and not 2.71?
Click to expand...
Click to collapse
Copy / Paste. Actually I have no idea up to which version works on xoom.

Schischu said:
Maybe, but it way down the list.
It's based on 2.1, the version number is just wrong.
Copy / Paste. Actually I have no idea up to which version works on xoom.
Click to expand...
Click to collapse
2.72 super su works on Xoom fine
Sent from my SM-G935F using Tapatalk

[DISCONTINED] [ROM] [7.1.x] Official LineageOS 14.1 Weekly Builds (Z00A/Z008)

SUPPORT FOR THIS HAS BEEN DISCONTINUED
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Unlock Bootloader!
Download the zip(s).
Install Appropriate FW base (STOCK MM 4.21.40.xx base is required) simple FW update package is available at my download link
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash LineageOS.
Optional: Install the Google Apps addon package. Open Gapps x86 7.1
Optional: Install the addon SU zip (x86 version)
Broken Features / Known Issues
VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
[*] Snapchat: thin greeen line tends to appear on recorded videos for snapchat
Asus Pixelmaster Camera App: Super resolution mode does not work. Turning off "Optimizations" from settings clears up any green line issues.
Some video formats do not play as expected
FM Radio is unsupported.
sim 2 cannot be disabled (this is true for all CM builds on non qualcomm hardware)
Other than Fugu (Nexus Player TV box) there are no Vendor released M x86/x86_64 builds in existance. You may experience some issues with GAPPS and some known apps not loading or working correctly. Below is a list of KNOWN apps that do not currently run on CM13 based x86 Zenfone 2 builds :
Polaris Office, Chase Mobile, Showbox...
[*] Screen recording not working Works now.
Chromecast screen mirroring not working, native casting works though.
[*] factory reset from setting menu has been reported to cause recovery boot loops. Works now.
CM14 (not device specific issues)
No CMTE yet
CM file manager has trouble accessing external sdcard
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
DOWNLOADS.LINEAGEOS.ORG
Recovery Links
Z00A
MM BL compatible TWRP: TWRP
Z008
MM BL compatible TWRP: TWRP
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps.
SU addon:
Flashable SU addon/removal
FOR INFO ON MM BOOTLOADER BASED BUILDS SEE THIS POST
XDA:DevDB Information
LineageOS 14.1 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
jrior001, crpalmer, say99
Source Code: https://github.com/LineageOS/android_kernel_asus_moorefield
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 4.21.40.xxx stock base
Version Information
Status: Nightly
Beta Release Date: 2016-11-09
Created 2017-01-27
Last Updated 2018-01-28

Reserved
DATA MIGRATION BUILDS
"THESE BUILDS WILL TAKE A LONG TIME (~30 mins) TO BOOT"
LineageOS has moved to private key signed builds. This is something that typically requires a full data wipe to transition too. To ease this burden for users who are not accustomed to that , the initial release builds are designed "MIGRATION" to help users who do not want to clean flash from an existing CM/Lineage build. Use the data migration builds as a one time "Flash this first, and then the officials" to migrate to private key signed builds. Follow the below instructions using the admiration builds to preserve app data if so desired, Otherwise feel free to clean flash directly to the weekly release builds
Official CM-13.0 -> CM14.1 Upgrade Guide
As seen with my previous unofficial CM-13.0 builds based on the MM Stock roms, An upgrade to the MM Firmware and bootloader is required going forward.
This guide is here to assist.
1) Download ROM and 7.1 GAPPS
2) Download my Firmware Update package for Z00A or Z008 . FASTBOOT AND ADB ARE REQUIRED!
3) Follow the included instructions to update Firmware and flash the new compatible TWRP. If for some reason the new TWRP is not flashed automatically flash it manually via fastboot. "fastboot flash recovery recoverimagename.img
4) Reboot to recovery and flash CM 14 and Gapps, reboot and enjoy. Data Wipe on upgrade is not required
CM 14.1 from Stock MM
1) Unlock Bootloader
2) Flash compatible TWRP
3) Perform desired backups
4) From recovery, factory reset & install ROM & 7.1 GAPPS
5) Enjoy!
CM 14.1 from CM13 Mm based beta builds
1) Reboot to TWRP( should already have good version)
2) Flash CM14.1 and 7.1 GAPPS
3) Reboot and enjoy!!

Reserve !
---------- Post added at 09:28 AM ---------- Previous post was at 09:14 AM ----------
I've just want to verify
to flash lineageOs
Its required Mm bootloader.
Is it required to flash also the firmware of Mm or just the bootloader and twrp !

Flashed migration build just fine. Didn't take too long. Flashing nightly now!

Thanks for big work. We love this rom, LinOS ???

Finally here!!!! Great job guys I'm glad you didn't give up through everything <3

jrior001 said:
Broken Features / Known Issues
VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
Snapchat: thin greeen line tends to appear on recorded videos for snapchat
Asus Pixelmaster Camera App: Super resolution mode does not work. Turning off "Optimizations" from settings clears up any green line issues.
Some video formats do not play as expected
FM Radio is unsupported.
audio is a little weird in Real Racing 3.
sim 2 cannot be disabled (this is true for all CM builds on non qualcomm hardware)
Other than Fugu (Nexus Player TV box) there are no Vendor released M x86/x86_64 builds in existance. You may experience some issues with GAPPS and some known apps not loading or working correctly. Below is a list of KNOWN apps that do not currently run on CM13 based x86 Zenfone 2 builds :
Polaris Office, Chase Mobile, Showbox...
DRM content is currently broken
Live Display (color calibration) not working yet
Screen recording not working
Chromecast screen mirroring not working, native casting works though.
factory reset from setting menu has been reported to cause recovery boot loops.
Battery life is horrible, numerous display wakelock issues
CM14 (not device specific issues)
No CMTE yet
Status bar icon changing broken
CM file manager has trouble accessing external sdcard
Battery profile is non functional/string errors
Click to expand...
Click to collapse
Damn that's a lot of issues! Is this from the Lineage OS official build or from the unofficial ? Some of them issues must have had been fixed, right ?

beibyboy06 said:
Reserve !
---------- Post added at 09:28 AM ---------- Previous post was at 09:14 AM ----------
I've just want to verify
to flash lineageOs
Its required Mm bootloader.
Is it required to flash also the firmware of Mm or just the bootloader and twrp !
Click to expand...
Click to collapse
no... just upgrade your bootloader to MM, download and flash
---------- Post added at 03:15 AM ---------- Previous post was at 03:12 AM ----------
PedroCaseiro said:
Damn that's a lot of issues! Is this from the Lineage OS official build or from the unofficial ? Some of them issues must have had been fixed, right ?
Click to expand...
Click to collapse
give them time bro.... First nightly is up just now... chill

Why the zip on the lineageOS download page are not signed ? I need to disable the verification to install it in TWRP...

PedroCaseiro said:
Damn that's a lot of issues! Is this from the Lineage OS official build or from the unofficial ? Some of them issues must have had been fixed, right ?
Click to expand...
Click to collapse
Provably a few of those I can clean up, was just quick copy/pasta from the other thread
Sent from my ASUS_Z008 using Tapatalk

persieghini said:
no... just upgrade your bootloader to MM, download and flash
---------- Post added at 03:15 AM ---------- Previous post was at 03:12 AM ----------
give them time bro.... First nightly is up just now... chill
Click to expand...
Click to collapse
Ok btw can I upgrade my lollipop bootloader to MM via twrp
And also should I unroot and uninstall xposed?

cedric1997 said:
Why the zip on the lineageOS download page are not signed ? I need to disable the verification to install it in TWRP...
Click to expand...
Click to collapse
The builds are signed, its your twrp that's not signed with the same private key(and never will be) that keeps you from using that sig verification.
Sent from my ASUS_Z008 using Tapatalk

jrior001 said:
Provably a few of those I can clean up, was just quick copy/pasta from the other thread
Sent from my ASUS_Z008 using Tapatalk
Click to expand...
Click to collapse
Is the battery life really horrible? Is it worse than the MM blobs CM 13? Anyways, thanks for continuing to develop this great ROM.

How can I enable also G-Assistant and G-Now on LinOS

crisvincent said:
Is the battery life really horrible? Is it worse than the MM blobs CM 13? Anyways, thanks for continuing to develop this great ROM.
Click to expand...
Click to collapse
No, it's actually been much better recently. I cleaned up a couple of the issues that were causing inconsistent wakelock issues a week or so ago.
Sent from my ASUS_Z008 using Tapatalk

jrior001 said:
No, it's actually been much better recently. I cleaned up a couple of the issues that were causing inconsistent wakelock issues a week or so ago.
Sent from my ASUS_Z008 using Tapatalk
Click to expand...
Click to collapse
Can confirm, I noticed my battery get much better recently before realizing you had updated that. I still have an issue with losing fast/quick charge, but I haven't seen others mention this so it's likely an issue on my end.

New nightly rom is amazing.... Thanks a lot guys @jrior001
---------- Post added at 04:11 AM ---------- Previous post was at 04:07 AM ----------
beibyboy06 said:
Ok btw can I upgrade my lollipop bootloader to MM via twrp
And also should I unroot and uninstall xposed?
Click to expand...
Click to collapse
No you can't do it with twrp... You need adb(comp) and unrooting is not necessary... Uninstalling xposed is also not necessary... It won't work in nougat.. It'll just be there

Can i use SuperSU instead of the official root?

Wow , I know I've just done a clean install of the nightly ....but , is it just me or is this a lot faster , more fluent browsing the web pages than anything built in the past ? Or am I slightly delirious thru watching all that blue building up coff ?
Hats off to the new age lineage and the master dev

Just moved to the official branch. Migration tool worked perfectly, and SU optional package did its job as well.
The whole process was absolutely painless, so let's enjoy OTA updates from now on!

[TWRP][OFFICIAL][3.2.2-0] TeamWin Recovery For Moto E4(woods)

TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.​
​
What's new in 3.2.2-0:
</> CHANGELOG : ? </>
Code:
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
</> DOWNLOAD ? </>
https://twrp.me
​
$ TIP $
You can update it from previous TWRP recovery if you already have it installed, else install it as fresh by using adb or Official TWRP Installer app from google play store or similar
​
To flash with Fastboot/Adb:
Code:
Code:
make sure OEM-Unlocking is ON
$ adb reboot bootloader
$ fastboot flash recovery twrp-3.2.2-0-woods.img
To contribute:
TWRP Code Review
TeamWin
XDAevDB Information
Moto E4 ROMs, Kernels, Recoveries, & Other Development
Contributors
iykeDROID™ {dumbDevpr*}
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created: 2018-07-12
Last Updated: 2018-07-13

Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.

ka4o_pi4a said:
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
Click to expand...
Click to collapse
from the looks of things on my side, i don't think that will happen in anytime too soon.
let's just hope for a God sent dev to take over the Moto E4(woods) development .

if any bug with the TWRP, create/open an issue regarding such bug on GitHub :
https://github.com/omnirom/android_bootable_recovery
( make sure to see how other issues were created and follow such trend )
thanks

I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.

EstebanxZ said:
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
Click to expand...
Click to collapse
wait for next update or use this at your own risk
https://t.me/motoe4woods/12179

Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.

ka4o_pi4a said:
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
Click to expand...
Click to collapse
i used it to install Both XOSP & Gapps Pico today.

Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).

ka4o_pi4a said:
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
Click to expand...
Click to collapse
please your issues on that specific ROM's thread.
As far as i know, the TWRP recovery works fine even before the unofficial beta... woods has come to it's best so far.
thanks.

Already do that. Also try with two or three different ROMs and get the same error. Doesn't matter, I'LL wait for some more stable version of twrp and some ROM.

Tks
Thanks man!

Laruzzo said:
Hi, this TWRP version to Moto E4 woods is not good.
It does not install GAPPS, and do not install SUPER SU.
With GAPPS the error is about 64 bits version. And with supersu it says that "Bad recovery no Unzip."
I tried with a unnoficial version and worked everything.
Please update in TWRP site to a new version with bug fix.
Look a this thread with the version that worked with Moto E4 woods.
https://forum.xda-developers.com/mo...rp-3-1-1-r1-port-xt1760-t3772249/post76177524
Click to expand...
Click to collapse
Dude,
learn how to read a full post with instructions & proper way of reporting an issue anywhere you find yourself.
Know you device SoC, Architecture, etc ... don't just talk any how.
also, commits has not been merged
see on gerrit.twrp.me :=> https://gerrit.twrp.me/#/c/android_device_motorola_woods/+/63/
Finally, always check to see if no one has report similar issue and been solved before you start writing sh*t into the air
https://postimages.org/
https://forum.xda-developers.com/showpost.php?p=77250466&postcount=6
NOTE : MOTO E4 SERIES IS ARM(32bit) Architecture Device, stop trying to flash/install ARM64 Gapps as you stop being dumb.

OK
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.

Laruzzo said:
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Click to expand...
Click to collapse
Download ⍖ ?
TWRP-323.0-Unofficial-woods.img

iykeDROID™ said:
TWRP is an open source, community project.
..
..iykeDROID™[/URL] {dumbDevpr*}
Source Code: https://github.com/TeamWin
[/SIZE][...his other way cause I doubt about official ¿‽​
Click to expand...
Click to collapse

Abish4 said:
Format Data Partition with F2FS format is not available which is usually available with every Moto Device Kernel
Click to expand...
Click to collapse
please deal with the kernel source here : https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/nougat-7.1.1-release-woods
Abish4 said:
Can you help with this other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
due to negligence, you couldn't check the source code here : https://github.com/TeamWin/android_device_motorola_woods
also check the twrp site : https://twrp.me/motorola/motorolamotoe4.html

I cannot flash gapps arm 7.1.x

Hi. I have one MotoE4 XT1763 Mediatek MT6735 with unlocked bootload.
would you recommend flashing the
twrp-3.2.3-0-woods.img 15.1M
Or the
TWRP-323.0-Unofficial-woods.img 15.5M
for the Lenovo Moto E4(XT1762)
?
Thank you peoples. TWRP unofficial working fine

Hey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?