Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (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.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=clark&type=nightly
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM64 platform, Android version 6.0)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Misc Links
Unoffical changelog:
Link: http://www.cmxlog.com/13/clark/
Learn to build yourself:
Link: https://wiki.cyanogenmod.org/w/Build_for_clark
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 13.0 Nightlies for the Moto X Pure 2015 (clark), ROM for the Moto X Style (Pure)
Contributors
invisiblek, Hashbang173, gmillz, neph81
Source Code: http://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2016-06-03
Last Updated 2016-06-03
I can't flash this build (clean flash). Twrp 3.0.2.0, stuck at "Patching system image unconditionally" forever.
Still able to flash unofficial build normally though.
Device: XT1572 Asia Single Sim.
tanpro260196 said:
I can't flash this build (clean flash). Twrp 3.0.2.0, stuck at "Patching system image unconditionally" forever.
Still able to flash unofficial build normally though.
Device: XT1572 Asia Single Sim.
Click to expand...
Click to collapse
Log? Check dmesg and /tmp/recovery.log
invisiblek said:
Log? Check dmesg and /tmp/recovery.log
Click to expand...
Click to collapse
dmesg:
Code:
Installing zip file '/external_sd/Downloads/cm-13.0-20160603-NIGHTLY-clark.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 1464916728
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Patching system image unconditionally...
That's it, it stop there forever.
Log uploading...
Update: Log link
tanpro260196 said:
dmesg:
Code:
Installing zip file '/external_sd/Downloads/cm-13.0-20160603-NIGHTLY-clark.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 1464916728
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Patching system image unconditionally...
That's it, it stop there forever.
Log uploading...
Update: Log link
Click to expand...
Click to collapse
Wow, so much going on here. Its trying to do a data wipe, failing pretty hard at doing that starting here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L531
I see su.img, which leads me to believe you're using that systemless root thing for whatever reason (CM includes root already...not sure what you're trying to achieve here other than complicating things).
I see xposed in there, another strike at attempting to get any official support for something that's broken.
However, it appears to get past all that and is blowing up here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L7740
I'm not sure what zip its trying to open there, seems odd to me that it would be trying to open another zip AFTER the install has already taken place.
End result: I don't have a good answer for you. The above snippet is not a dmesg. Not sure if it would provide any more information, but you got a lot of hacks going on here already. My guess is that xposed or that systemless root thing are attempting to re-install themselves after your CM zip is installed and is hanging/failing.
You could wipe /system (use the advanced format option under wipe) as well as /data (but it looks like that fails, so a full format of internal storage would probably be recommended) and try again.
invisiblek said:
Wow, so much going on here. Its trying to do a data wipe, failing pretty hard at doing that starting here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L531
I see su.img, which leads me to believe you're using that systemless root thing for whatever reason (CM includes root already...not sure what you're trying to achieve here other than complicating things).
I see xposed in there, another strike at attempting to get any official support for something that's broken.
However, it appears to get past all that and is blowing up here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L7740
I'm not sure what zip its trying to open there, seems odd to me that it would be trying to open another zip AFTER the install has already taken place.
End result: I don't have a good answer for you. The above snippet is not a dmesg. Not sure if it would provide any more information, but you got a lot of hacks going on here already. My guess is that xposed or that systemless root thing are attempting to re-install themselves after your CM zip is installed and is hanging/failing.
Click to expand...
Click to collapse
I already performed a full wipe (checked every box except SD card) before flash, it should removed everything right?
Beside, those things are installed on unoffcial builds, not this build.
The other zip file could be the gapps package?
tanpro260196 said:
I already performed a full wipe (checked every box except SD card) before flash, it should removed everything right?
Beside, those things are installed on unoffcial builds, not this build.
The other zip file could be the gapps package?
Click to expand...
Click to collapse
Doubt its the gapps package. One other thing you could try is to change the filesystem of /data to ext4, then back to f2fs, that would wipe it out for sure. Make sure you have a way to get your cm zip back on to the device though afterwards, because it won't be there after you do that.
Something is really hosed with your /data partition when I see it failing to delete (unlink) all those files. That's not good at all...
invisiblek said:
Doubt its the gapps package. One other thing you could try is to change the filesystem of /data to ext4, then back to f2fs, that would wipe it out for sure. Make sure you have a way to get your cm zip back on to the device though afterwards, because it won't be there after you do that.
Something is really hosed with your /data partition when I see it failing to delete (unlink) all those files. That's not good at all...
Click to expand...
Click to collapse
I noticed that only /data is f2fs, the rest is ext4, is it normal?
Could be a hardware defect?
tanpro260196 said:
I noticed that only /data is f2fs, the rest is ext4, is it normal?
Could be a hardware defect?
Click to expand...
Click to collapse
That's normal.
No, pretty unlikely.
invisiblek said:
That's normal.
No, pretty unlikely.
Click to expand...
Click to collapse
One more thing, when I plug the phone to my pc in twrp, it shown "xt1575" instead of "xt1572". Could it be the problem?
tanpro260196 said:
One more thing, when I plug the phone to my pc in twrp, it shown "xt1575" instead of "xt1572". Could it be the problem?
Click to expand...
Click to collapse
No, that's a TWRP thing and its purely cosmetic.
invisiblek said:
No, that's a TWRP thing and its purely cosmetic.
Click to expand...
Click to collapse
Tried your suggestion and failed again.
dmesg is the same.
Log attached. I see some errors in there but I don't understand any of them.
I just installed CM13, booting now... Never unlocked the device, so full stock unmodiffied system 'till now. I flashed CM Recovery but fails to install the .zip it says its for clarck and my device is . (none) so I flashed TWR Recovery and it flashed w/o error at all. First full wipe, including system, then cm.zip and then gapps stock, all fine. Now starting Android for first time optimizations... I'll let you know if something goes wrong.
At last...
Sent from my XT1572 using XDA-Developers mobile app
Clark booted fine no issues accept having issues updating binaries in SuperSU
---------- Post added at 04:31 PM ---------- Previous post was at 04:30 PM ----------
ARUN B said:
At last...
Sent from my XT1572 using XDA-Developers mobile app
Click to expand...
Click to collapse
+1
Haven't flashed anything in weeks, guess I'll finally give cm a shot.
Just noticed cm recovery. Any benefit to flashing this? I'll find out soon enough I suppose.
Weird, I can't flash this rom but I can flash everything else normally (unoffcial cm13, RR, Dirty Unicorn)....
Wow cm recovery is pretty lacking feature wise... Now i have to flash twrp again.
---------- Post added at 09:40 PM ---------- Previous post was at 09:11 PM ----------
Flashed fine here. Loading apps now.
Been running well for me most of the day. Thanks to everyone who has been a part of the ROM.
Hi, can you share battery life?
This is a beta test for MIUI 8 MM base for the Nexus 6P.
This version is based off patchrom, and is an unofficial build.
Up to date tutorial of how to build using patchrom - Here
WARNING: Your warranty is now void. I take no responsibility in the well-being of your device. Follow the instructions, and post detailed information if you face any issues.
Full install instructions can be found - Here
It is a long process, unfortunately
Ok, this should be the current install method that people are following. As of Oct/13/16
Download the necessary apk files and place them on your sdcard/emulated storage. (Keyboard of choice, rom manager/smanager, titanium backup, and working theme manager)
Wipe Dalvik, system, data, and cache
Flash fullota, vendor, gapps, superuser
Allow the rom to boot. Takes roughly 10 minutes for the first boot. You will experience some force closes
Pull the notification shade down, hit the gear icon to get into options. Go to about phone. Tap MIUI version until you have developer options.
Go back to settings, then find additional options. Scroll down to "Allow USB debugging". Check the box next to this option
Open permissions, application found on your homescreen select bottom option for root. Check the box and accept the prompt
It will say that it failed
Go to the homescreen and delete the supersu application (drag the icon to the top of the screen)
Open the file manager application and install Titanium backup. (This will help you determine if you're rooted)
Open script manger(browse as root). Navigate to /data/local/ and run userinit.sh as root.
Your gapps should now be functioning without force closing.
Now delete the themes application. (use a root file explorer, I use solid explorer. Theme manager is located in /system/apps/)(Must restart your phone after deleting the apk)
Install the theme manager from your sdcard
(You can download themes from Here (place them in the /miui/theme/ folder
Finally, fix file sharing issues by enabling Documents in the installed apps settings. (It is disabled by default. You'll have to enable it after every reboot)
To download off of Wi-Fi, go to downloads app, settings, change limit to your liking.
To keep documents enabled after reboots, follow theses instructions:
Enable Documents in "installed apps" settings
Go to developer options
Disable MIUI optimizations
Accept and reboot
Download links:
MIUI ROM - FullOta
Vendor - Vendor
GAPPS - GAPPS
GAPPS Mirror - GAPPS
Apps to place on sdcard - APPS
Superuser - SU Warning Won't prompt for super user permissions
Tested and working:
Data
Wi-Fi
Touch
Camera
Gyroscope
Fingerprint reader
NFC
Bluetooth
Gapps
Su
Themes
File sharing
BUGS/TODO:
Package everything into an all in one package/less packages
Enable themes by default
Enable "Documents" by default
Find a better solution for gapps
Add su handling application
Add fully English keyboard to initial package
Old install method, courtesy of @Andromjb
Changelog:
Oct - 7 - 2016
Fixed MIUI kernel (no longer need to flash franco kernel)
Thanks where they are deserved!
mcming1989 on github for supporting Patchrom for angler
@thoiloidainhan for being super helpful with a TON of things
The fans for keeping me motivated
MIUI devs and port team for info
Superr for his tools
Google for the ease of access to info
Those of you who have donated. You rock!
@MidnightDevil for writing a helpful How-To
@skw5115 for figuring out the "share" bug
@Andromjb for the great installation video
@pacods61 for getting themes situated
@pacods61 for finding the download limit setting
XDA:DevDB Information
MIUI 8, ROM for the Huawei Nexus 6P
Contributors
tr4nqui1i7y
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP, Patchrom, MIUI 8
Version Information
Status: Testing
Created 2016-08-18
Last Updated 2016-10-04
I'm in, standing by to flash..
mbl1979 said:
I'm in, standing by to flash..
Click to expand...
Click to collapse
eta 6 min
Be aware. Not sure if this will boot. Or soft/hard brick a device.
By flashing, you agree that you are at fault if any errors occur.
I will help as much as possible in the process.
Please upload your logcats to pastebin. This way I can view them, as long as others.
OK, do you have a 6p as well? Or are you building blind?
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
Also what do we need to flash with it? 1st time flashing MIUI ROM.
mbl1979 said:
OK, do you have a 6p as well? Or are you building blind?
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
Also what do we need to flash with it? 1st time flashing MIUI ROM.
Click to expand...
Click to collapse
I have a 6p as well. OP updated with download link.
Good deal.
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
Flash super su ?
Can i flash It by Twrp? Does It need gapps?
Enviado desde mi Nexus 6P mediante Tapatalk
OP updated with further instructions
Downloading ?
Backup updated, flashing now.
xXPegashusXx said:
Can i flash It by Twrp? Does It need gapps?
Enviado desde mi Nexus 6P mediante Tapatalk
Click to expand...
Click to collapse
Flash through latest TWRP. No gapps or additions for now.
1st attempt, error 7 failed to install in TWRP.
mbl1979 said:
1st attempt, error 7 failed to install in TWRP.
Click to expand...
Click to collapse
Me too, it says same error
error 7 faild in the first attempt
mbl1979 said:
1st attempt, error 7 failed to install in TWRP.
Click to expand...
Click to collapse
Got it. Updating asserts then I'll repost. Flashing will not succeed until I post an update. Sit tight everyone.
Sounds good bud.
mbl1979 said:
Sounds good bud.
Click to expand...
Click to collapse
ETA 8 minutes
Downloading new version
OP updated with test 2
Will be back tonight with more builds...
Again. ONLY FLASH IF YOU ARE COMFORTABLE WITH FASTBOOT/SOFT BRICK/HARD BRICK
Just got this email: "You f****** loser, you test it first. Stupid noob. You want us to brick first? You test it first mother f*****"
Robert Tromp [email protected]
If you don't want to test, don't. This is a development community, let's act like it. This build was never claimed to be safe/stable/usable/bootable.
Asteroid OS Alpha 1.0
Freedom & Privacy
We believe that when it comes to wearable devices, users should have full control over their machines and data. AsteroidOS has been created from the ground-up with modularity and freedom in mind. For this reason, it is a free and open-source project.
Proven building blocks
AsteroidOS is built upon a rock-solid base system. Qt 5.6 and QML are used for fast and easy app development. OpenEmbedded provides a full GNU/Linux distribution and libhybris allows easy porting to most Android and Android Wear watches.
Community-friendly
Since its creation in 2015, AsteroidOS has been led by Florent Revest, but is open towards external contribution and collaboration. The project is still in active development and if you want to help, make sure to check the Get Involved page.
Click to expand...
Click to collapse
This is only for SPARROW, the larger ZenWatch 2.
The way AsteroidOS is implemented it is not meant to be flash to any partitions. It boots an isolated root file system from the sdcard partition using a custom fastboot image.
This is very powerful because it allows a person to switch between AsteroidOS and Android Wear with relative ease.
Status: The Asus Zenwatch 2 hasn’t been supported by AsteroidOS for very long and there is currently a bug with the touchscreen but overall it is good enough to test Asteroid.
The Bluetooth synchronization app for Android is named AsteroidOSSync and is available. Be careful that dory is the only port with Bluetooth capabilities and this app will be of no use with other watches yet.
Click to expand...
Click to collapse
Known Issues:
Touch Screen disabled after resuming from "sleep"
Bluetooth - needs to be implemented.
To Do:
How to get logs
Pictures
AsteroidOS documentation [url]https://asteroidos.org/wiki/documentation/[/URL]
Source:
meta-asteroid: [url]https://github.com/AsteroidOS/meta-asteroid[/URL]
meta-sparrow-hybris: [url]https://github.com/AsteroidOS/meta-sparrow-hybris[/URL]
AsteroidOSSync: [url]https://github.com/AsteroidOS/AsteroidOSSync[/URL]
My test repo: [url]https://gitlab.com/lrs/asteroidos-sparrow[/URL]
Build Changelog:
December 1, 2016:
/dev/.coldboot is created by systemd
btsync fixes
libaccounts fixes
mtp fixes
and much more
September 18, 2016:
Move msm-fb-refresher to meta-asteroid
machine.conf: Remove some MACHINE_FEATURES for more lightweight images
bcrm-patchram-plus: be less verbose
Make layers Machine specific to prevent conflicts with other meta-*-hybris
lipstick, sensorfs: move hybris dependencies to meta-*-hybris layers
lipstick, sensorfs: fix typo
Simplify patchram script
September 11, 2016:
sparrow.conf: provide proper SERIAL_CONSOLE for systemd
misc. meta-astroid patches
August 13, 2016:
sparrow.conf remove some useless config values
linux-sparrow: pack with mkboot
July 28, 2016: Initial Official Bring up
Sparrow Kernel Bring Up
Initialize Sparrow lollipop system
Configure Initd scripts to support Sparrow
Configure Sparrow device flags
Testing Changelogs:
September 10, 2016:
Provide proper serial console to prevent systemd timeouts
Old logs:
Nothing yet
Requirements:
Linux/OSX (Windows if drivers are available)
Unlocked Bootloader
ADB and Fastboot in path - recommended not required
Developer mode
ADB enabled
Not Needed:
DOES NOT NEED TWRP
A backup, though it is recommened
Before Installing (only if the bootloader is locked):
Install the Android developer tools: adb and fastboot, on your computer.
Enable ADB in the Android Wear settings under Developer options/Android Debugging. (Developer options appear after tapping the Build number in the About page several times)
Enter the following commands in a terminal:
adb reboot bootloader
fastboot oem unlock
Temporrary Install (Assumes your using Linux):
Go to the AsteroidOS website - link is below
Select Asus ZenWatch 2 (sparrow)
Download the official rootfs and zImage files
Download the AsteroidOSSync app from the bottom of the website
Install on your phone - Useless until bluetooth is implemented
Push the rootfs to the sdcard
adb push -p /home/user/Downloads/asteroid-image-sparrow.ext4 /sdcard/linux/asteroidos.ext4
Reboot to bootloader
adb reboot bootloader
fastboot boot the zImage
fastboot boot /home/user/Downloads/zImage-dtb-sparrow.fastboot
Download:
AsteroidOS Official Downloads
Archives/Mirrors:
To be updated
Old How To "Install":
Extract asteroidos-*-sparrow.tar.xz
cd to extracted files
adb push -p asteroid-image-sparrow.ext2 /sdcard/linux/rootfs.ext2
adb reboot bootloader
fastboot boot zImage-dtb-sparrow.fastboot
enjoy
Getting logs:
While there is no straight forward way to determine which log is needed because there are so many pieces that break regularly. Some common areas are debuging the launcher, and hw issues. I do not remember all the logging commands or what does what, so if you are obtaining logs you will need to run all the commands and capture the outputs.
adb access to Asteroid OS (windows, linux, mac)
adb shell
add strace - if needed
journalctl -u mce --no-pager (requires disabling 1000 user first) - used to debug launcher and other packages.
EGL_PLATFORM=hwcomposer strace lipstick --platform hwcomposer
EGL_PLATFORM=hwcomposer lipstick --platform hwcomposer
more to come
Q: Why doesn't x, y, z, feature work?
A: Probably, because it hasn't been implemented yet.
Q: I have x, y, z, issue.
A: Logs Please
Q: Can I use a custom kernel?
A: Only if you are willing to put forth the effort replace the kernel source in the build process yourself and make your own builds.
Q: I flashed *insert file here* and now it won't boot.
A: Sounds like a personal problem, since you didn't read the instructions properly. Seriously, you will probably need to restore some sort of backup.
Q: Will you port AsteroidOS to my watch?
A: No, but I can, somewhat, help you port it yourself. #asteroid on freenode or [url]https://asteroidos.org/irc-channel/[/URL] is a good place to get help.
Lrs121 said:
Q: Why do I need linux?
A: Because I don't know of any working Windows/OSX(macOS) fastboot drivers.
Q: Why doesn't x, y, z, feature work?
A: Probably, because it hasn't been implemented yet.
Q: Can I use a custom kernel?
A: Only if you are willing to put forth the effort replace the kernel source in the build process yourself and make your own builds.
Q: I flashed *insert file here* and now it won't boot.
A: Sounds like a personal problem, since you didn't read the instructions properly. Seriously, you will probably need to restore some sort of backup.
Q: Will you port AsteroidOS to my watch?
A: No, but I can, somewhat, help you port it yourself. #asteroid on freenode or https://asteroidos.org/irc-channel/ is a good place to get help.
Click to expand...
Click to collapse
after the bootanimation, the display is turning black and it seems to have a bootloop
---------- Post added at 12:09 ---------- Previous post was at 11:42 ----------
Lrs121 said:
Requirements:
Linux
p7zip
Unlocked Bootloader
ADB and Fastboot in path - recommended not required
Developer mode
ADB enabled
Not Needed:
DOES NOT NEED TWRP
A backup, though it is recommened
How To "Install":
Extract asteroidos-*-sparrow.7z
cd to extracted files
adb push -p asteroid-image-sparrow.ext2 /sdcard/linux/rootfs.ext2
adb reboot bootloader
fastboot boot zImage-dtb-sparrow.fastboot
enjoy
Download:
Google Drive Folder
Mirrors:
To come?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24694152805485105
Mirror for your file
matze19999 said:
after the bootanimation, the display is turning black and it seems to have a bootloop
---------- Post added at 12:09 ---------- Previous post was at 11:42 ----------
https://www.androidfilehost.com/?fid=24694152805485105
Mirror for your file
Click to expand...
Click to collapse
Thanks for the mirror.
Have you tried pressing the power button after the boot animation. I can't remember if it defaults to the sleep state after boot. There is no "ambient" mode, the screen is either on or off.
It is also possible that, because it is a dev preview, this particular build is broken and may be so for a while.
Lrs121 said:
Thanks for the mirror.
Have you tried pressing the power button after the boot animation. I can't remember if it defaults to the sleep state after boot. There is no "ambient" mode, the screen is either on or off.
It is also possible that, because it is a dev preview, this particular build is broken and may be so for a while.
Click to expand...
Click to collapse
Will try it, thanks
---------- Post added at 19:59 ---------- Previous post was at 19:55 ----------
matze19999 said:
Will try it, thanks
Click to expand...
Click to collapse
no, doesnt work. I can access the watch via adb shell, but display is black all time..
matze19999 said:
Will try it, thanks
---------- Post added at 19:59 ---------- Previous post was at 19:55 ----------
no, doesnt work. I can access the watch via adb shell, but display is black all time..
Click to expand...
Click to collapse
Ah that's useful. If adb can be access then that means is not the boot image nor is it boot looping. Which narrows it down to the root file system and probably just an unstable build.
I thought you are the developer of this build?
matze19999 said:
I thought you are the developer of this build?
Click to expand...
Click to collapse
I maintain the device tree, beyond that I'm clueless. So if there happens to be bad code or something related to the system I'm clueless. That or I had a bad download during the build process. Anything could be the issue.
If I can remember the some of the logging commands I can have people get me logs from their watches and I can get help decoding what the issue is from Florent Revest or someone on IRC.
Lrs121 said:
I maintain the device tree, beyond that I'm clueless. So if there happens to be bad code or something related to the system I'm clueless. That or I had a bad download during the build process. Anything could be the issue.
If I can remember the some of the logging commands I can have people get me logs from their watches and I can get help decoding what the issue is from Florent Revest or someone on IRC.
Click to expand...
Click to collapse
If you tell me how I can take a log file, I would send it to you...
Update:
There is now a directory for test changes. Use this if you are brave, though in general it should be safe.
It can be found under the Google Drive link. Please read the README file. It will include important information related to the test builds
Edit:
the sync app has been uploaded. it is not signed so any future updates will probably require uninstalling the old app and installing the new
I get parsing Error while installing the apk file.
Android 6.0
Snapdragon 820 64Bit
http://hastebin.com/onuyifedet.md
Code:
sh-4.3# lipstick --platform hwcomposer
EGLFS: Screen Info
- Physical size: QSizeF(29, 29)
- Screen size: QSize(320, 320)
- Screen depth: 32
Segmentation fault
matze19999 said:
http://hastebin.com/onuyifedet.md
Click to expand...
Click to collapse
Make sure you have the EGL_COMPOSER=hwcomposer pre-appended or else it will segfault. I forgot strace had to be built and added to /bin. Also I believe the journalctl command is used to debug the launcher
matze19999 said:
I get parsing Error while installing the apk file.
Android 6.0
Snapdragon 820 64Bit
Click to expand...
Click to collapse
I'll look into the app issue
Lrs121 said:
Q: Why do I need linux?
A: Because I don't know of any working Windows/OSX(macOS) fastboot drivers.
Q: Why doesn't x, y, z, feature work?
A: Probably, because it hasn't been implemented yet.
Q: I have x, y, z, issue.
A: Logs Please
Q: Can I use a custom kernel?
A: Only if you are willing to put forth the effort replace the kernel source in the build process yourself and make your own builds.
Q: I flashed *insert file here* and now it won't boot.
A: Sounds like a personal problem, since you didn't read the instructions properly. Seriously, you will probably need to restore some sort of backup.
Q: Will you port AsteroidOS to my watch?
A: No, but I can, somewhat, help you port it yourself. #asteroid on freenode or https://asteroidos.org/irc-channel/ is a good place to get help.
Click to expand...
Click to collapse
fastboot and adb is working flawlessly on Mac OSX 10.11.6
Update:
Major updates to meta-asteroid (core of the os) - should probably fix launcher issues
Minor update to sparrow device tree
Will be up soon
Major update:
meta-asteroid has had many changes and some rewrites
sparrow device tree has been updated to support changes to meta-asteroid
rootfs is smaller after removing some optional features
bootloader
I was wondering if after executing these two adb commands
will the bootloader remain unlocked even after reboot and
a power down? (my phone has the MM 6.01 updated)
adb reboot bootloader
fastboot oem unlock
Thanks, have a great day everyone!
Misterjunky said:
I was wondering if after executing these two adb commands
will the bootloader remain unlocked even after reboot and
a power down? (my phone has the MM 6.01 updated)
adb reboot bootloader
fastboot oem unlock
Thanks, have a great day everyone!
Click to expand...
Click to collapse
Adb reboot bootloader just reboots the watch into fastboot mode.
Fastboot OEM unlock is what unlocks the watch, this is "permanent" as in it will stay that way until you run the command fastboot oem lock
TWRP FOR SAMSUNG GALAXY J7 PRIME (SM-G610F/M)
*** Disclamer
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* or any other problems u face. 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 aren't to be held reponsible.
Be sure to backup your data,contacts,apps,etc. as the internal storage may need to be wiped
Flashing Instructions
1. Download The Odin flashable Zip
2. Enable OEM unlock in your developer options.
3. Enter Download mode (Vol Down + Home Button + Power Button while switched off)
4. flash the twrp by placing downloaded zip in AP section and flash it while keeping auto reboot off.
5. Once it shows PASS... Press vol down + home + power..
6. when the phone turns off...immediately shift to volume up + home + power.
7. U Will boot to twrp...
8. If you just wanna root... just flash supersu using otg or sideload...
9.if you wanna mount internal ... flash the kernel provided below and Wipe internal... [WARNING : your device will be formatted...make a backup first]
10. Enjoy
FEATURES
1.touch Working
2. f2fs file system support (read, write, format, backup & restore)
3.exFAT file system support (read, write, format, backup & restore)
4.NTFS file system support (read, write, format)
5.ADB root
6.ADB Sideload
7.Full SELinux support
8.OTG support
9. Backup And Restore
10. MTP supported
ISSUES
1. Sdcard Doesnt mount
2. MTP doesnt work
3.Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
DOWNLOADS
TWRP - DOWNLOAD
MODDED KERNEL- HERE
CREDITS:
TWRP team..
Samsung
max35000 (for the kernel)
thank you bro..
gooooooooood job
---------- Post added at 03:02 PM ---------- Previous post was at 02:58 PM ----------
it works!!!!!!!Thank you very much brother
dacochir said:
thank you bro..
gooooooooood job
---------- Post added at 03:02 PM ---------- Previous post was at 02:58 PM ----------
it works!!!!!!!Thank you very much brother
Click to expand...
Click to collapse
np still...cant figure out sdcard mounting... but i think otg compensates for that
Varun hellboy said:
np still...cant figure out sdcard mounting... but i think otg compensates for that
Click to expand...
Click to collapse
Yes that's right. Otg cable was detected. There is no need to ADB. Thank you very much brother:good:
MTP fixed
hello, thanks for this one.
TWRP works well, touch screen works.
Since sdcard not detected, how to flash supersu.zip?
I tried method sideload but it doesn't work well.
Difficult to use cmd on windows xp
backup and restore not working
dafikjunior said:
hello, thanks for this one.
TWRP works well, touch screen works.
Since sdcard not detected, how to flash supersu.zip?
I tried method sideload but it doesn't work well.
Difficult to use cmd on windows xp
Click to expand...
Click to collapse
Use otg....or wipe internal...flash kernel and reboot...put supersu in internal and flash
dacochir said:
backup and restore not working
Click to expand...
Click to collapse
Working for me.... I must be doing something wrong.....see attachment for proof
Varun hellboy said:
Working for me.... I must be doing something wrong.....see attachment for proof
Click to expand...
Click to collapse
Should I use a kernel that you have introduced?
I am currently using the ROM DoomsDay I'm gonna get this ROM backup.
Should I install the kernel that you have introduced?
thank you very much brother...:good:
dacochir said:
Should I use a kernel that you have introduced?
I am currently using the ROM DoomsDay I'm gonna get this ROM backup.
Should I install the kernel that you have introduced?
thank you very much brother...:good:
Click to expand...
Click to collapse
yes....it is highly recommended.. use it
guys i have uploaded a new kernel based off latest stock rom....use that as a wifi lag is seen while using max's kernel on Roms like Doomsday....
Is the modded kernel has some features, or just modded to enable to mount the internal storage?
@Varun hellboy. Base on experience, Can u help me build a twrp recovery for j7109 (china version). I cant find out any twrp really working for it. May be it'snt international version. I can provide things as u need. Thank in advanced!
steviejrdn said:
Is the modded kernel has some features, or just modded to enable to mount the internal storage?
Click to expand...
Click to collapse
only allows mounting....i will make a feature packed kernel later..
kien_vip said:
@Varun hellboy. Base on experience, Can u help me build a twrp recovery for j7109 (china version). I cant find out any twrp really working for it. May be it'snt international version. I can provide things as u need. Thank in advanced!
Click to expand...
Click to collapse
Ask J700 guys..
Oh thanks. May be I'll ask guys with j7xxx series.
Is there anyway to backup without USB OTG? i hate to flash the modded kernel also, because it cause a trouble for my stock rom...
thanks
Not Working
not working for me.
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
/ * Your warranty is now void. Knox 0x1.
/* We are not responsible for bricked devices, dead SD cards, lost data due to failed backups, etc, etc. flash at your own risk
*/
How to flash this ROM:
1. Download the zip file.
2. Make sure this zip file is saved to your device (I prefer transferring to sd card to allow for full wipe of data on tablet).
3. If you want Google Play functionality, download OpenGApps (link below). (optional)
4. Reboot into TWRP (Volume Up + Home + Power or Advanced Restart).
5. Make a backup (optional).
6. Wipe System, Data, Cache, and Dalvik Cache partitions with Advanced Wipe. (I like wiping internal data too, do NOT wipe SD Card!)
7. Flash the ROM you just downloaded.
8. Flash OpenGApps ARM for Android 9.0 if you want Google services (optional).
9. If you want root, flash Magisk.
10. Reboot and proceed normally with installation.
11. ????
12. Profit!
Download links:
SM-T350
OpenGApps ARM 9.0 (I use pico)
Source code:
LineageOS
iesous-kurios (forked from LineageOS, and rest of the developers mentioned in the following Credits) on Github
Galaxy MSM-8916
Credits:
The LineageOS Team (and specifically haggertk )
elginsk8r
VirsysElectron
Nubianprince
And awesome tester : retiredtab (saved me sooo much time and has been huge asset in getting bugs fixed)
And of course the Galaxy MSM-8916 team for all of their hard work on our device specific code.
Version Information:
ROM OS Version: Android 9.0 Pie
Known Bugs:
Static while playing mp3s with stock music player (download vlc player to play mp3 files)
Overwhelming sense to brag that your old tablet has newer version of Android on it than a lot of people's expensive phones.
All other functions seem to be working fine. Please report bugs with logcat. I am just starting out on being able to troubleshoot bugs and make edits to code to fix problems, so a majority of bugs will be fixed by the official devs and maintainers of Lineage but I'm trying to learn how to help out too and you have to start somewhere, right?
1st
2nd
3rd
Looking forward to this, thank you!
Thanks for the nice ROM, older bugs are gone! Runs very smoothly with frequent lock-ups.
Issues:
Some apps from Google Play Store are not available saying "not compatible" when you can install their APKs (i.e. Instagram...etc.)
Lockups are annoying
Jfuginay,
Thanks for compiling this ROM. Your work is appreciated.
On my SM-T350, I get the following message when trying to install the 16.0 ROM
updater process ended with error: 7
error installing zip file /sdcard/Download/lineage-16.0-20190221-UNOFFICIAL-gt58wifi.zip
I will check tomorrow to see if there is a newer TWRP that can work with the updater script. I saw in another thread that the SM-T550 updater script is failing because TWRP can't report the model number.
I do need external audio working. I see that SM-T550 which is the bigger version of this A tablet does have audio working as per
https://forum.xda-developers.com/showpost.php?p=78720468&postcount=22
Perhaps there is something in that SM-T550 code that we can use to help with the SM-T350.
retiredtab said:
On my SM-T350, I get the following message when trying to install the 16.0 ROM
updater process ended with error: 7
error installing zip file /sdcard/Download/lineage-16.0-20190221-UNOFFICIAL-gt58wifi.zip
Click to expand...
Click to collapse
Okay the above error was due to TWRP version 3.1.0. I upgraded to 3.2.1 and now the updater-script installs 16.0 onto my SM-T350.
I found TWRP 3.2.1 at
https://androidfilehost.com/?fid=962339331458992706
TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi.tar
for the Samsung Galaxy Tab A 8.0, by Austcool Walker
MD5 = 6455c0cfa01b9f71cf575c553df18733
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
I also noticed a newer build today (dated 20190223).
External audio still doesn't work. Headphone jack works.
---------- Post added at 12:11 PM ---------- Previous post was at 11:55 AM ----------
Here is the SM-T550 thread where virsys got external audio working.
https://forum.xda-developers.com/showpost.php?p=78972270&postcount=70
I'm looking through the SM-T550 commits, but unsure what might be needed for the SM-T350?
The most obvious difference between
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/tree/lineage-16.0
and
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
is the entire configs folder in the SM-T350 code.
I also found
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
retiredtab said:
Okay the above error was due to TWRP version 3.1.0. I upgraded to 3.2.1 and now the updater-script installs 16.0 onto my SM-T350.
I found TWRP 3.2.1 at
https://androidfilehost.com/?fid=962339331458992706
TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi.tar
for the Samsung Galaxy Tab A 8.0, by Austcool Walker
MD5 = 6455c0cfa01b9f71cf575c553df18733
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
I also noticed a newer build today (dated 20190223).
External audio still doesn't work. Headphone jack works.
---------- Post added at 12:11 PM ---------- Previous post was at 11:55 AM ----------
Here is the SM-T550 thread where virsys got external audio working.
https://forum.xda-developers.com/showpost.php?p=78972270&postcount=70
I'm looking through the SM-T550 commits, but unsure what might be needed for the SM-T350?
The most obvious difference between
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/tree/lineage-16.0
and
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
is the entire configs folder in the SM-T350 code.
I also found
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
Click to expand...
Click to collapse
Glad you got it to boot.
I noticed that missing config folder too, so I just added that to my build directory and am compiling that now to test it out. I didn't add the camera files, since it is only bluetooth and speaker I'm trying to troubleshoot. Don't think the camera is having problems, but honestly haven't tried it out yet.
I noticed the missing config folder when checking out the device.mk file for each device. I added the links to the config folder in the device.mk file and added the bluetooth and sound folders from config file to my build directory, so I'm hoping once that compiles it will fix our problems.
Will do a dirty flash first, then if it still isn't working, I'll do full wipe and test it out. If it boots up and fixes anything I'll upload it for people do download, if the same problems persist I won't bother uploading the new build.
One of my links that I found got messed up.
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi
In the above, virsys does some OSS-audio cleanup for 16.0
---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------
Regarding the stock 16.0 camera, I get the following error message
Camera error
Can't connect to the camera
If I download open camera from play store, the back camera gives an error message
"failed to start camera preview"
However, the front facing camera shows a preview, but can't save the picture/photo
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
Also had a complete reboot while using Clash Royale game. I hit the news tab and the tablet completely rebooted.
I will try to reproduce, if I can, and get a logcat.
Playing Clash Royale seems okay, but I have to use the headphone jack vs external audio to get sound.
My SM-T350 is a completely fresh install with only gapps pico. Nothing else.
---------- Post added at 04:59 PM ---------- Previous post was at 04:29 PM ----------
Looking at the commit history between the SM-T350 and SM-T550, it looks like deadman96385 didn't add the config/audio files for the SM-T350, but did for the SM-T550 on April 18, 2018
SM-T350
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/commits/lineage-16.0
SM-T550
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/commits/lineage-16.0
I wonder if the non working external audio is due to missing config folder?
retiredtab said:
One of my links that I found got messed up.
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi
In the above, virsys does some OSS-audio cleanup for 16.0
---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------
Regarding the stock 16.0 camera, I get the following error message
Camera error
Can't connect to the camera
If I download open camera from play store, the back camera gives an error message
"failed to start camera preview"
However, the front facing camera shows a preview, but can't save the picture/photo
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
Also had a complete reboot while using Clash Royale game. I hit the news tab and the tablet completely rebooted.
I will try to reproduce, if I can, and get a logcat.
Playing Clash Royale seems okay, but I have to use the headphone jack vs external audio to get sound.
My SM-T350 is a completely fresh install with only gapps pico. Nothing else.
---------- Post added at 04:59 PM ---------- Previous post was at 04:29 PM ----------
Looking at the commit history between the SM-T350 and SM-T550, it looks like deadman96385 didn't add the config/audio files for the SM-T350, but did for the SM-T550 on April 18, 2018
SM-T350
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/commits/lineage-16.0
SM-T550
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/commits/lineage-16.0
I wonder if the non working external audio is due to missing config folder?
Click to expand...
Click to collapse
I'm hoping it's those config files. I did a build with them in but I'm not sure they were included because of my ccache being enabled. I'm not 100 percent convinced that ccache can tell the difference between slightly modified files well enough to know to include the changed files in new build, so I cleared out my ccache files and ran make clobber and am building fresh right now with those config files in there.
Will do full wipe and flash this and report back if it made any difference.
Adding those config files didn't fix anything. Found several differences in some proprietary.mk files so attempting to see if any of those do the trick. New build compiling now. Will probably need to disable ccache and do make clobber to clear directory so I'll probably let it build over night while I sleep.
Let's hope I wake up to a fixed ROM !
Jfuginay said:
Adding those config files didn't fix anything.
Click to expand...
Click to collapse
Darn, I was hoping the config would fix it.
I left a message in the SM-T550 thread asking virsys what was done to fix the external audio because it's not obvious to me where the commit is that fixed it.
In this post
https://forum.xda-developers.com/showpost.php?p=78170903&postcount=9
dated Nov 15, 2018 virsys says "Audio is working now".
At github
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi/commits/lineage-16.0
there is a commit for Nov 16, 2018 entitled
Cleanup for OSS-audio and improved lineage-16.0 compatibility
I wonder if this commit fixed the external audio?
Just out of curiousity, how are you building this ROM? Locally or on some clould computer?
Another idea/suggestion?
At
https://github.com/Galaxy-MSM8916/a...8wifi/blob/lineage-16.0/proprietary-files.txt
it says the proprietary files are from (line 1)
# Samsung Package Version T550XXU1CQL5_T550OJV1CQK3_TUR (unless otherwise specified and/or tagged)
The SM-T550 has 2 external speakers while the SM-T350 only has 1. I wonder if we have to grab the proprietary files from a SM-T350. Maybe the drivers from the SM-T350 know how to work with just 1 speaker?
retiredtab said:
Another idea/suggestion?
At
https://github.com/Galaxy-MSM8916/a...8wifi/blob/lineage-16.0/proprietary-files.txt
it says the proprietary files are from (line 1)
# Samsung Package Version T550XXU1CQL5_T550OJV1CQK3_TUR (unless otherwise specified and/or tagged)
The SM-T550 has 2 external speakers while the SM-T350 only has 1. I wonder if we have to grab the proprietary files from a SM-T350. Maybe the drivers from the SM-T350 know how to work with just 1 speaker?
Click to expand...
Click to collapse
I'll check out a working 14.1 ROM and see if it has specific proprietary files there which differ from what we are using now.
Virsys responded back on how he/she got the SM-T550 external audio working. See
https://forum.xda-developers.com/showpost.php?p=78978788&postcount=74
"I've fixed the whole audio framework by editing and importing my own mixer_paths.xml to /system/etc"
I wonder if we can download his SM-T550 ROM image, extract that mixer_paths.xml file to see what changed?
So I downloaded the SM-T550 code and looked at the
/system/vendor/etc
directory.
There are 28 files there. In the SM-T350 /system/vendor/etc, there are only 27 files.
The additional file in SM-T550 is called audio_platform_info.xml.
It has definitions for speaker out. I'm not sure of all the definitions or how it's linked yet? I don't know if this file has to be part of the actual rom compilation process or it gets read at boot/runtime.
In addition, there have been additional entries put into the mixer_paths.xml file in the 550 that virsys referred to.
In the SM-T550 /system/etc directory, there 3 additional XML files named
A05QF_sr544_module_info.xml, B05QF_sr544_module_info.xml and C05QF_sr544_module_info.xml.
Not sure if these files are needed or not?
retiredtab said:
So I downloaded the SM-T550 code and looked at the
/system/vendor/etc
directory.
There are 28 files there. In the SM-T350 /system/vendor/etc, there are only 27 files.
The additional file in SM-T550 is called audio_platform_info.xml.
It has definitions for speaker out. I'm not sure of all the definitions or how it's linked yet? I don't know if this file has to be part of the actual rom compilation process or it gets read at boot/runtime.
In addition, there have been additional entries put into the mixer_paths.xml file in the 550 that virsys referred to.
In the SM-T550 /system/etc directory, there 3 additional XML files named
A05QF_sr544_module_info.xml, B05QF_sr544_module_info.xml and C05QF_sr544_module_info.xml.
Not sure if these files are needed or not?
Click to expand...
Click to collapse
Thanks for all the ground work, gives me a good place to look into tonight when I get home from a meeting and have some time to tinker with the code.
K, I looked through a lot of proprietary code for both the gt58 and 511, and hopefully found all the discrepancies. Added over 20 files and lines of code to gt58 proprietary folders and renamed one file to match the dependency in another file.
Compiling now, so cross your fingers that it fixes our sound!
Are your changes up on github?
https://github.com/jfuginay
I'm newish to github and just learning how to navigate and look around.
What I find confusing is the seemingly incredible amount of layers of abstraction in defining the speakers. That is, A->B, B->C, C->D, D->E, E->F, F->G. Anything missing is enough to break it.
I understand why the layers are required, but without a flow chart or visualization of how these things work, it's difficult to follow all the necessary definitions and files needed.
I also have noticed some of the people using github have no documentation on why the code change was required. The changes are there, but why? Was it because something was broken? Was it because it wasn't defined properly in the first place? Was it because there was a potential security problem?
If you have any URL resources that would help explain some of this, I would appreciate some pointers.