Release notes
Android TV is very limited at the moment, you can see it, for example. opening Play Store. Because of this I've decided for an "hybrid build" (see it like Windows 8 with Metro/Modern and Desktop parts.)
From ATV's launcher you will be able to run only a limited set of apps (only those built with support for the Android TV SDK), for all the other apps I've included Chainfire's Sideload launcher.
Using this launcher you can access to all apps installed on the system, included regular Android settings (I left if there because it's way more complete, from there you can even change resolution and/or overscan for your WeTek like in CM12).
Since the Play Store is really empty, if you wanna install apps without sideloading the APK, you can launch the browser (from Sideload Launcher), search for the app that you wanna install straight from the address bar (ex. "mx player"), click install and open the resulting link in Play Store; it's easier said than done.
If the device seems sluggish it might be caused by a background install process (an app is updating), the dex2oat process (aka ART compiles the apk) is very resource hungry, so just let it finish
Remember that as a consequence of the switch to art from dalvik: first boot, updates and apps installation will take longer; this happens because art compiles the apk and does not work like dalvik that was using a just-in-time approach (so expect almost 10 minutes for the first boot and future upgrades)
First install instructions
* As really first thing install one of the available customs recoveries (CWM or TWRP)
* Power off your device and unplug the AC power cord.
* Get the latest available ROM and GAPPS version from the links below and copy them to a MicroSD card.
* Now insert the MicroSD card in your STB.
* Plug the AC power cord while you keep pressed the little reset pinhole (located on the bottom of the device) for 10 seconds (just count slowly to ten and it will be good).
* Once the device has booted to recovery perform a factory reset and flash the ROM's zip for first followed by the GAPPS zip.
* Reboot and enjoy Android TV.
Update instructions
* Get the latest available ROM and GAPPS version from the links below and copy them to a MicroSD card.
* Now insert the MicroSD card in your STB.
* Enable "Developer options" following this tutorial and from it enable the "Reboot to recovery" option.
* Bring up power menu by keeping pressed the power button on the STB for a couple of seconds (or pushing F4 if you have a keyboard plugged in) and select "Reboot -> recovery".
* Once the device has booted to recovery flash the ROM's zip for first followed by the GAPPS zip.
* Reboot and enjoy your updated Android TV.
Downloads
* ROM 2015-01-15
* GAPPS 2014-12-31 (ATV)
* Kernel sources
Screenshots
Older builds
* ROM 2015-01-13
* ROM 2015-01-12
* ROM 2015-01-11
* ROM 2015-01-10
* ROM 2015-01-05
* ROM 2015-01-02
* ROM 2015-01-01
* ROM 2014-12-31
* ROM 2014-12-28
* ROM 2014-12-27
I was able to deodex the apks of the Nexus Play rom, I need a break tomorrow I will give it a look
New build with new gapps, read carefully the release notes in the OP
* ROM 2014-12-27
* GAPPS 2014-12-27 (ATV)
New build with new gapps
* ROM 2014-12-28
* GAPPS 2014-12-28 (ATV)
Some work under the hood and some cosmetic changes, I'm liking this Android TV interface, specially because with this build you can install other apps and you're not limited like the nexus player (that doesn't even have a web browser right now)
Video of WeTek Play running Android TV: https://www.youtube.com/watch?v=yrH_Ccdm52c
Next build (in the late afternoon probably) will have WeTek Theater's icon in Android TV's launcher
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WeTek Play ATV
Hi Christian Troy,
looks really nice what you have created.
I'm currently searching for an android box for my tv and got really interrested on the WeTek Play.
One question though for your Android TV Build, is it able, like the Nexus Player to act like an Chromecast?
That would make this thing really awesome!
Keep up your good work!
~ApO
I haven't tried but I would be very surprised if it would. Since I never tried it do you have a video to show it how it should work to test it out?
Google Cast
In this video 1:20 you can see for a short time there is a app called Google Cast.
http://www.theverge.com/2014/11/3/7149505/google-nexus-player-review
It should work like you have connected a Chromecast to your TV,
apps from this list https://www.google.de/chrome/devices/chromecast/apps.html#?view=featured
should find the Chromecast running on WeTek with Android TV build.
To test it you could try to install Chromecast app for Android/iOS on your phone/tablet.
https://play.google.com/store/apps/details?id=com.google.android.apps.chromecast.app&hl=
Edit: I rewatched your video and saw in the settings Google Cast and while Daydeam was showing "Google Cast ready"
could be possible that the abbility like Chromecast works.
it doesn't work, and the logs are not helpful (they dont' say anything), what you see is there because I included AndroidMediaShell app in my gapps package but probably it works only with nexus player and chromecast
Christian Troy said:
it doesn't work, and the logs are not helpful (they dont' say anything), what you see is there because I included AndroidMediaShell app in my gapps package but probably it works only with nexus player and chromecast
Click to expand...
Click to collapse
Ok thanks for testing, maybe time will find a way to get it .
Edit: Did a google search and found something interresting:
http://forum.xda-developers.com/hardware-hacking/chromecast/app-cast-receiver-app-android-t2900726
* ROM 2014-12-31
* GAPPS 2014-12-31 (ATV)
New Year Release
* ROM 2015-01-01
* ROM 2015-01-02
like today's CM12 build, it has the volume control perfectly working now
* ROM 2015-01-05
Some minor changes and three relevant:
- replaced CM's Superuser with SuperSU (the new superuser that has recently been committed doesn't work with this kernel that doesn't have SELinux enabled), the first time you will run supersu app (if ever...) a notification will tell you to update su binary, all the files are updated but, again, because of the lack of SELinux it will drive SuperSU a little bit crazy, just let it update the su binary in the normal way and it won't bother anymore
- added an exception to not detect the airmouse as an hw keyboard so the aosp ime will popup (if you have an hw keyboard it won't show unless you force it from language & input settings, leanback keyboard will always popup btw)
- remapped the key layout of the airmouse so now you will be able to select letters using leanback keyboard
* ROM 2015-01-10
This build includes a kernel that I've built from sources, disabling an option that was hogging the cpu when a network service was binding on the localhost interface (hopefully all the other things will keep working, I don't know how far it is respect the kernel used by latest WeTek OS roms, in case I'll ask for updated sources).
Acestream, for example, was unusable because of this, now it works like a charm (tested under Kodi 14.1 RC and latest P2P-Streams, right now SopCast shipped with that addon doesn't work with Lollipop)
Included CEC settings under Settings -> WeTek Settings, untested because I have any cec capable device. It should work because it's just a matter about writing some stuff to the proper sysfs file and let the kernel handle it.
Fixed a problem that might happen when quitting from daydream (the screensaver) that was sending the device to sleep (I don't know why it happened, it wasn't doing it when I tested daydream in early builds but some upstream changes might have changed something)
* ROM 2015-01-11
Final fix for the zoom in issue on WeTek Theater. I tried to be nice, but I had to do it the hard way... now it won't happen anymore, it's practically impossible (I hope!!)
* ROM 2015-01-12
Workaround for the last frame of the last channel played on WeTek Theater that was visible when launching some apps (like Kodi), it's just cosmetic and will be handled better when the new WeTek Theater will be released (I told them to put the modification straight in the Theater's code, when quitting the app)
Added support for link2sd, if you wanna use it prepare a microsd card using the new cwm (be careful, all data on it will be destroyed) and install link2sd from play store (or sideload it, whatever you prefer)
* ROM 2015-01-13
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Release notes
* This is not a bug, but a consequence of the switch to art from dalvik: first boot, updates and apps installation will take longer; this happens because art compiles the apk and does not work like dalvik that was using a just-in-time approach (so expect almost 10 minutes for the first boot and future upgrades)
* Probably few minor things might not be as stable as the stock ROM, in case report it and I will try to fix it.
First install instructions
* As really first thing install one of the available customs recoveries (CWM or TWRP)
* Power off your device and unplug the AC power cord.
* Get the latest available ROM and GAPPS version from the links below and copy them to a MicroSD card.
* Now insert the MicroSD card in your STB.
* Plug the AC power cord while you keep pressed the little reset pinhole (located on the bottom of the device) for 10 seconds (just count slowly to ten and it will be good).
* Once the device has booted to recovery perform a factory reset and flash the ROM's zip for first followed by the GAPPS zip.
* Reboot and enjoy CyanogenMOD.
Update instructions
* Get the latest available ROM and GAPPS version from the links below and copy them to a MicroSD card.
* Now insert the MicroSD card in your STB.
* Enable "Developer options" following this tutorial and from it enable the "Reboot to recovery" option.
* Bring up power menu by keeping pressed the power button on the STB for a couple of seconds (or pushing F4 if you have a keyboard plugged in) and select "Reboot -> recovery".
* Once the device has booted to recovery flash the ROM's zip for first followed by the GAPPS zip.
* Reboot and enjoy your updated CyanogenMOD.
Downloads
* ROM 2015-01-20
* GAPPS 2015-01-07 (LITE)
* GAPPS 2014-11-09 (FULL)
* Kernel sources
Screenshots
Videos
* https://www.youtube.com/watch?v=ZESm4wjU_kA
Misc Stuff
* When an app forces the portrait orientation, the default behavior is to simulate a portrait / phone-like UI adding black bars to the sides (an example is Antutu when it runs the benchmark, or Box.com). If you prefer to have a landscape stretched UI flash this zip. To revert to the default behavior flash this one instead.
Note that the setting will persist even if you upgrade the ROM so you have to flash that zip only once.
* When you press power button on the TV box or the AirMouse, the default behavior of the device is to perform a shutdown and enter a suspension state (the status LED will turn red) and when you will power it on again, it will have to boot from scratch.
If you find it annoying you can flash this zip (it will have to be flashed after each rom upgrade) that will turn off box's video output but it will mantain it active for background tasks (the LED will stay, in fact, blue) and powering it on will take just a second (the same as it happens on an Android phone or tablet for example)
Older builds
* ROM 2015-01-15
* ROM 2015-01-13
* ROM 2015-01-12
* ROM 2015-01-11
* ROM 2015-01-10
* ROM 2015-01-05
* ROM 2015-01-02
* ROM 2014-12-30
* ROM 2014-12-25
* ROM 2014-12-23
* ROM 2014-12-22
* ROM 2014-12-19
Removing the "beta" tag since it's working very very nicely, enjoy this Christmas build on your first TV Box having a really working Lollipop
* ROM 2014-12-23
Any chance at all that this will work with the Minix X8 as it runs an Amlogic S802 chip?
I'm sorry but I'm offering support only for WeTek products
Ryan 619 said:
Any chance at all that this will work with the Minix X8 as it runs an Amlogic S802 chip?
Click to expand...
Click to collapse
I would give donations do have this for my Minix x8-h Plus, hope it gets more attention soon
Fixed official YouTube playback in today's build (actually I've done a much better job under the hood integrating into amplayer the new Lollipop way to handle network streams, instead of keep using some old routines that I had forward ported)
Now it's practically a daily driver.
* ROM 2014-12-25
Android TV
Your work is fantastic. I really appreciate what you do.
I want to ask, will it be possible to make a Android TV build like on the Nexus Player
Thank you in advance.
Is there any source code for Android TV available? Anyway right now the review about the Nexus Player are really meh, it's something a little bit more than a chromecast
Android TV
Christian Troy said:
Is there any source code for Android TV available? Anyway right now the review about the Nexus Player are really meh, it's something a little bit more than a chromecast
Click to expand...
Click to collapse
I hope this will help:
url --> android.googlesource.com/device/google/atv/+/android-5.0.2_r1
url nexus player --> android.googlesource.com/device/asus/fugu/+refs
As I understand the ATV is just a customized lollipop with some added and removed services.
Thank you for your hard work.
I will give it a look in the future
Android TV
Christian Troy said:
I will give it a look in the future
Click to expand...
Click to collapse
Thank you for this:
url--> wetekforums.com/viewtopic.php?f=13&t=97&sid=cf9b59c44e999dc30c7cee61704ce0c0
until I won't find a way to use the gapps from Nexus Player it won't run properly
Android TV
Christian Troy said:
until I won't find a way to use the gapps from Nexus Player it won't run properly
Click to expand...
Click to collapse
I'll have a look at that.
I think the device has to be recognized by the google play store as the Nexus player to get the proper gapps. I'll try to find the proper version of Google Play Store and Play Services.
The device is already fetching apps for Android TV, in fact the store is very restricted (and you can download Youyube for Android TV like shown in the screenshot), the problem is in the default play store, it will update only with the phone/tablet version, I have to ship it with the one from the Nexus Player but right now it's odexed and baksmali fails with Lollipop odex files.
New build, and a new GAPPS zip for those of you that wanna a minimal install without most of G's bloatware
* ROM 2014-12-30
* GAPPS 2014-11-09 (LITE)
* ROM 2015-01-02
Fixed volume +/- handling, now it will default to modify the "media" stream volume and it will actually work (despite big G's effort to output always at max volume the media stream using digital connections); improved mute button handling (it uses a native function to mute the stream instead of doing weird workarounds like amlogic was doing), if you mute it you can unmute pressing mute again or pressing vol+, if the stream is muted and you press vol- nothing will happen.
btw, this was Lollipop's handling of mute button before my modification
Code:
case KeyEvent.KEYCODE_VOLUME_MUTE:
[...]
// TODO: Actually handle MUTE.
.... "Actually handle MUTE"... they didn't rush out L release, do they?
* ROM 2015-01-05
Some minor changes and two relevant:
- replaced CM's Superuser with SuperSU (the new superuser that has recently been committed doesn't work with this kernel that doesn't have SELinux enabled), at first boot a notification will tell you to update su binary, all the files are updated but, again, because of the lack of SELinux it will drive SuperSU a little bit crazy, just let it update the su binary in the normal way and it won't bother anymore
- added an exception to not detect the airmouse as an hw keyboard so the aosp ime will popup (if you have an hw keyboard it won't show unless you force it from language & input settings)
* ROM 2015-01-10
This build includes a kernel that I've built from sources, disabling an option that was hogging the cpu when a network service was binding on the localhost interface (hopefully all the other things will keep working, I don't know how far it is respect the kernel used by latest WeTek OS roms, in case I'll ask for updated sources).
Acestream, for example, was unusable because of this, now it works like a charm (tested under Kodi 14.1 RC and latest P2P-Streams, right now SopCast shipped with that addon doesn't work with Lollipop)
Included CEC settings under Settings -> WeTek Settings, untested because I have any cec capable device. It should work because it's just a matter about writing some stuff to the proper sysfs file and let the kernel handle it.
Re-introduced the display sleep timeout, setting it to a value different than "Never timeout" will trigger daydream (the screensaver), that you can customized from its settings.
* ROM 2015-01-11
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
General:
CyanogenMod 11 for Samsung Galaxy Trend 2. (SM-G313HN) This is not 100% completed, so bugs can be expected. There are some bugs listed on this post and if you find more, report them to me. (Either to this thread or via private messages) It will help alot to fix them.
Note: Google apps are not included. Get them here. I recommend using Mini or smaller, because when installing a OTA update, the bigger packages don't fit on RAM if the internal storage is full. You can install the rest from Play store. It is also kinda pointless to have for example, Youtube and Google Maps on /system, because when they are updated, the updated versions go to /data anyway.
Screenshots:
Downloads:
* Latest build
* All builds
Installation:
* Install a custom recovery. (Get CWM here)
* Download the latest version to your SD-card.
* Boot into the recovery mode by pressing <Vol. Up> + <Home> + <Power>
* You can navigate on the recovery mode with the volume keys. <Power> opens the selection and <Back> goes to the previous menu.
* Backup your stock ROM by going to the SD card by going to "backup and restore" -> "backup to /storage/extSdCard". You need about 3-4 gigabytes of free space on the card, depending how full your internal storage is. You can go back to stock if you don't like this ROM, by going to "backup and restore" -> "restore from /storage/extSdCard".
* You need to do a factory reset before installing this. You can do this by selecting "wipe data/factory reset". The installation won't let you install the ROM without doing this.
* Select "install zip" -> "install from /storage/extSdCard" and then select the zip you downloaded.
* Optionally install the OpenGApps-package while you are in the recovery the same way. (Doesn't need a data wipe)
* When it is done installing, go back to the main menu and select "reboot system now" and that should be pretty much it. The first startup takes a while.
Updating:
CyanogenMod checks for updates weekly by default. You can update the phone manually by going to Settings -> About phone -> CyanogenMod-updates, tapping the refresh button and selecting the latest one. After it is downloaded, you can install it.
What works?
* Audio
* Bluetooth (At least file transfer between 2 devices is confirmed, no other devices tested. (For example. headsets, keyboards, etc.)
* Calls
* Camera
* Data connection
* DSP Manager
* GPS
* NFC
* Offline-charging
* OTA updates
* Text messages
* USB (Adb, MTP, PTP, UMS, Tethering, etc)
* Video playback/recording (Mostly.. Front camera video recording doesn't work and some codecs don't work.)
* WiFi
* Wired headsets (Audio, microphone, button)
Bugs:
* First startup might is laggy. The best way is to just skip everything, change the language and set up the accounts, etc. from the Settings app.
* Some videos don't play, because there are some codec issues. (For example on Facebook. YouTube seems to work fine.)
* Some have reported about higher battery drain when using WiFi compared to stock ROM.
* Reported that when calling or sending messages, the phone causes more interference to TV/radio signals than stock. (Excessive transmitting power?) Not too noticeable unless you are very close to the antenna, so it shouldn't cause too much problems. Possibly uses more battery.
* When USB debugging enabled and the phone is restarted, turning USB tethering on too quickly doesn't turn it on completely and removing the USB cable the phone causes the phone to freeze. (This happens when using Linux, the computer shows that it is trying to connect to the internet but the phone shows that USB tethering is not enabled) When this happens, it can be fixed (When the cable is not removed) by going to the settings -> developer settings and disabling ADB, then re-enabling it and finally then turning on USB tethering. Yes, Linux + ADB + turning on USB tethering within 10-20 seconds after rebooting. I know this doesn't affect many people, but happens to me frequently.
* Front camera video recording doesn't work.
Changelog:
Code:
===================================
Build 20151214
===================================
* Fix libskia. (Updated sources)
* Remove unused or otherwise useless binary blobs. List of blobs:
/system/bin/at_distributor
/system/bin/atx
/system/bin/atxd
/system/bin/usb_portd
/system/bin/usbdev_mode
/system/etc/apanic_rename.sh
/system/etc/copy_cp_imgs.sh
/system/etc/show_navi.sh
/system/etc/usb_portd.conf
/system/lib/lib_SA_GoogleFX_ver124b.so
/system/lib/libatlog.so
/system/lib/libatparser.so
/system/lib/libaudiosa.so
* Rework /system/etc/media_profiles.xml. (Doesn't seem to fix or break anything..)
* Change kernel compression from XZ to GZip. (Speeds up booting by few seconds)
* Disable CONFIG_KSWAPD_NOSWAP from kernel. (Enable better swapping)
* Remove unused services from /init.hawaii_ss_vivaltonfc3g_base.rc.
===================================
Build 20151209
===================================
* Android security patch December 1, 2015.
* Removed the a2dp_audio_hw patch, because it did not do anything.
===================================
Build 20151207
===================================
* Fixed libstagefrighthw. (Caused some app crashes, for example YouTube and Facebook)
* Enabled zRam. (This should speed up the phone nicely, when there are alot of apps running in the background.)
* Patched a2dp_audio_hw. I don't know if it changed anything.
* Cleaned the init scripts a bit.
===================================
Build 20151128
===================================
* Fixed bluetooth
* Fixed NFC
* This build now uses CyanogenMod /init instead of the stock one
* Now uses OTA updates (yay!)
===================================
Build 20151119
===================================
* Fixed the "WiFi amnesia" bug
* Fixed offline charger
===================================
Build 20151118
===================================
* Fixed the codec issues
* Built with newer sources, now shows "Android security patch level"
===================================
Build 20150829
===================================
* First release.
Source code:
* Device tree
* Kernel
Thanks to itigr for helping me alot in this project!
Thanks a lot!
Best wishes with very first custom rom for Trend 2! Keep going!
I prefer pico or nano GApp build. This one should works on CM-11.
update:
I've found that this is very stable and fast ROM, not bugged as I had experience with CM11 on Huawei.
It even works with microG (GApp replacement) very nice! I only use Play Store and YouTube app.
New Pipe (Youtube replacement) have problem only for WebM format video is blue/pink filtered, but smooth playing. For MPEG-4 format, play normal.
Samsung S6 CM11 theme and S Launcher 6 made Trend 2 looks similar to stock touchwiz environment
I found more bugs. Bluetooth isn't working and device forgets wifi password with every reboot.
New build coming soon! Changes:
- Most of the hardware codecs work now. (Tested: video recording/playback, Youtube, DSP Manager)
- When I updated the CM sources, there was "Android security patch level" in "About phone". Not sure if these will update automatically or what.
EDIT: New build is available!
EDIT2: Fixed the "WiFi amnesia". Quick patch: https://www.androidfilehost.com/?fid=24269982086999294.
EDIT3: New build uploaded. Fixed the WiFi bug and the offline charger now works.
EDIT4: Accidentally uploaded the eng-build. (Red flashes around the screen and insecure ADB) >.< Rebuilding..
EDIT5: Re-uploaded the build.
Small teaser:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nikiz said:
Small teaser:
Click to expand...
Click to collapse
G313HN got CM12.1 now )
G313HU got CM11 )
and now G313HZ is the worst of all (
Most of all: G313HZ use Spreadtrum chip instead of Broadcom
doesntexits said:
G313HN got CM12.1 now )
G313HU got CM11 )
and now G313HZ is the worst of all (
Click to expand...
Click to collapse
Well, er, it is CM12.0 for G313HN
And Galaxy V (G313HZ) got whole thread with CM11.0 also.
adeii said:
Well, er, it is CM12.0 for G313HN
And Galaxy V (G313HZ) got whole thread with CM11.0 also.
Click to expand...
Click to collapse
But it has lots of bugs
Well, the CM12.0 is not usable yet. The base system works pretty well, but RIL/WiFi/Bluetooth are not working yet. Well, it is the first build that actually boots. Also logcat shows alot errors. It is strange, the RIL and WiFi works for about 30 seconds after the first boot, then suddently stops working.. Also, I found out why the stock /init works and CM one doesn't. ueventd tries to load < 32 characters long ueventd.{hardware}.rc and "ueventd.hawaii_ss_vivaltonfc3g.rc" is too long. It needs to be renamed (or patch the init) "ueventd.hawaii_ss_vivaltonfc3g.r" or sometimes "ueventd.hawaii_ss_vivaltonfc3g". (I have absolutely no idea why it varies..)
Nikiz said:
Well, the CM12.0 is not usable yet. The base system works pretty well, but RIL/WiFi/Bluetooth are not working yet. Well, it is the first build that actually boots. Also logcat shows alot errors. It is strange, the RIL and WiFi works for about 30 seconds after the first boot, then suddently stops working.. Also, I found out why the stock /init works and CM one doesn't. ueventd tries to load < 32 characters long ueventd.{hardware}.rc and "ueventd.hawaii_ss_vivaltonfc3g.rc" is too long. It needs to be renamed (or patch the init) "ueventd.hawaii_ss_vivaltonfc3g.r" or sometimes "ueventd.hawaii_ss_vivaltonfc3g". (I have absolutely no idea why it varies..)
Click to expand...
Click to collapse
Great job anyway.
Btw bluetooth should work if you'll use the stock libs (on cm11).
and thanks for pushing patches .
itigr said:
Great job anyway.
Btw bluetooth should work if you'll use the stock libs (on cm11).
and thanks for pushing patches .
Click to expand...
Click to collapse
Thanks. Btw, here are the DS-versions of the patches: https://github.com/ZIM555/android_device_logands/tree/master/patch Just add the external/tinyalsa to it. Btw, could you try to boot HU with HN kernel and show what "cat /proc/cpuinfo" and "cat /proc/simslot_count" shows with it? It might be possible to make one ROM for both devices. Just need to change "ro.telephony.ril" on init. I just need a way to detect which device it is regardless of what kernel/ROM it is running.
EDIT: Well, I need to figure out a way to disable NFC, preferably without deleting files.
Nikiz said:
Thanks. Btw, here are the DS-versions of the patches: https://github.com/ZIM555/android_device_logands/tree/master/patch Just add the external/tinyalsa to it.
Click to expand...
Click to collapse
Ok, i'll check it out.
Well, the Cyanogenmod Updater is not working.. The OTA server seems to be working though.
EDIT: Oh, it works. Had to add "/api" to the url.
Nikiz said:
Well, the Cyanogenmod Updater is not working.. The OTA server seems to be working though.
EDIT: Oh, it works. Had to add "/api" to the url.
Click to expand...
Click to collapse
What server do you use btw? xdarklight's one?
itigr said:
What server do you use btw? xdarklight's one?
Click to expand...
Click to collapse
I use this: https://github.com/julianxhokaxhiu/CyanogenModOTA It is simple and easy to set up. Doesn't require mysql-databases, etc. Just download it and boom, it works. Or at least should work. I had to do some small modifications to it.
itigr said:
Btw bluetooth should work if you'll use the stock libs (on cm11).
Click to expand...
Click to collapse
Got Bluetooth working on CM libs! Well, atleast file transfer works between two devices. I have no headsets to test though. Just add bt_vendor.conf to /system/etc/bluetooth-
Code:
# UART device port where Bluetooth controller is attached
UartPort = /dev/ttyS0
# Firmware patch file location
FwPatchFilePath=/system/vendor/firmware/
#Firmware Patchfile name
FwPatchFileName=BCM4343A0_001.001.034.0044.0127_ORC_Vivalto-3G_5MC.hcd
(SM-G313HU seems to use a newer patch file, just rename it)
Also made some changes regarding NFC, but I have no way to test it.
The OTA server seems to just dump all builds, regardless of what version is in use so the phone will show older builds as updates as well..
New build! Changes:
* Bluetooth is now working. (At least file stransfer)
* Small changes to NFC, might not work though. I have no way to test this.
* Uses now the Cyanogenmod /init, no longer using the stock one.
* OTA updates enabled!
Great. One more question, does your kernel compile while building CM? I can only compile it by going to kernel dir and running make here, then defining TARGET_KERNEL_PREBUILT, eitherway it ****s about "zconf.hash.c" .
UPD0: Just started compiling and sata connection died -_-, dammit.
UPD1: one guy reported couple months ago that headset (bluetooth or wired, no idea) button doesn't work
itigr said:
Great. One more question, does your kernel compile while building CM? I can only compile it by going to kernel dir and running make here, then defining TARGET_KERNEL_PREBUILT, eitherway it ****s about "zconf.hash.c" .
UPD0: Just started compiling and sata connection died -_-, dammit.
UPD1: one guy reported couple months ago that headset (bluetooth or wired, no idea) button doesn't work
Click to expand...
Click to collapse
I am compiling the kernel while building CM. It just works for me. I use ArchLinux. Try to use my kernel sources. One thing though, the build might fail, because the new glib. Use "export LANG=C" before building, or add it to "~/.bashrc". For some reason linking libwebviewchromium.so takes for me about 12-48 hours when I reinstalled Arch, normally it took about 6 hours for the whole build..
I just tested the wired headset with the "Okay Google"-thingamajig and it is working perfectly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
About LD
Years after the death of LiquidSmooth, Sean Hoyt, (the LiquidSmooth lead dev) has returned to the ROM game, along with the Exynos5420 team, to bring greatness to our beloved Exynos5420 tablets (and note 3), out of the ashes of the fallen LiquidSmooth ROM. LiquidDeathOS is super optimized for the Exynos5420.
In fact right now it is so optimized that it won't even boot on non-exynos devices
LDO is AOSP based , and is only for Exynos devices
(it's even more optimized than cm).
Important info
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
What works:
Display/Brightness
Touchscreen
Audio
Wifi
S-Pen
Buttons/Lights
SDCard
USB Storage
GPS
Bluetooth
IR Blaster
Camera
OMS/substratum theme engine
What doesn't work:
The default wallpaper is from DU, it will be changed in time
Not in the list? Report below
How to install
1. Download ROM and Gapps and transfer to device
2. Boot into recovery (TWRP recommended)
3. Wipe the system, cache, data, and dalvik cache
4. Install ROM
5. Install Gapps
6. Install SuperSU
7. Reboot to system
Downloads
official releases
test Builds
Note: n1awifi is the same device as lt03wifi - the SM-P600
Contributors
@deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin @javelinanddart@tincho5588 @ShevT
Device Maintainers
@mosimchah @ZakooZ @Orion116
Source code
Kernel
Device Repos
Rom Source
XDA:DevDB Information
SM-P600 LiquidDeathOS Official, ROM for the Samsung Galaxy Note 10.1 (2014 Edition)
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: LP bootloader
Based On: AOSP
Version Information
Status: Beta
Created 12-30-2016
Last Updated 3-23-2017
Deathly Adiutor App
Deathly Adiutor is an open-source, modified version of Kernel Adiutor made specifically for Exynos 5420 devices.
Features
Power Saving:
S-Pen Power Saving - Same as in Touchwiz, disables S-Pen detection if it's inserted in the slot
S-Pen Input Booster - Instantly increase CPU frequency when the S-Pen touches the screen
Touchscreen Input Booster - Instantly increase CPU frequency when you touch the screen
Touchkey Input Booster - Instantly increase CPU frequency when you touch the capacitive buttons
Touchscreen Glove Mode (Not all screens support this)
CPU Control:
CPU Settings reworked - Deathly adiutor back-end was cleaned up to work specifically with our CPU
CPU Thermal - Control all thermal throttling points for the CPU (make your device run colder... or even hotter)
GPU Control:
GPU Time in States - Same as CPU Time in States (Times in each frequency)
GPU Frequency Control (not yet supported on Nougat)
GPU Voltage Control (not yet supported on Nougat)
GPU Governor Control (not yet supported on Nougat)
Battery control:
Full power statistics - See current and maximum charging currents and current source of power
Unstable power source detection - Lowers current until the power source is stable
Customize charger current limits - Make your device charge faster (safe, if the charger can not supply enough current, the board will dynamically decrease the current)
Screen-On current limiter - Limit charging if screen is on (to avoid overheating)
Speakers:
Privacy mode - Disable main speaker if headphones are plugged in
Earpiece volume
Left/Right speaker volume
Speaker equalizer
Headphones:
Left/Right channel volume
Mono output mode
Headphone equalizer
App Themes:
Light theme - White and Red
Dark theme - Grey and Red
Credits
This post was written by @ZakooZ
This app is brought you by the exynos5420 developer team: @deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin, @javelinanddart, @tincho5588, @ShevT
Translators:
@ShevT - Russian
The following people deserve distinction for their major contribution:
@tincho5588, responsible for 80%+ of the code for the new features
@deadman96385, the main maintainer of the Deathly kernel and most of the remaining code
Downloads
The app can be found in the Play Store:
Free version (with ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.ads
Donator version (no ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.adfree
Helping the developers
You may have noticed there's 2 versions of this app, one ad-free for donators and one with ads.
You can help us by clicking ads you're interested in for the free version, or purchasing the donator version!
We will use the money generated by this app as common money for the developers of the team. It will be used to pay for our web-hosting (we own a gerrit server and a domain name, exynos5420.com). It will also be used to buy a new device if one of ours breaks.
Translating the App
You can also help us by translating the app to your language:
1. You can start by looking at the full english language file: Link
2. Then compare it to your unfinished language file. You can find it here, under values-xx/strings.xml, xx being your language abbreviation.
3. You can then fill-in the missing strings in your language file. Here's an example of what a proper update looks like.
4. Then you can submit your translation by using our gerrit. If you don't know how to use gerrit, just PM the translation to your favorite developer and he'll get it merged!
FAQ:]
Q Does this ROM support custom kernels?
A No.
Q Why doesn't this ROM support Xposed?
A Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports while using it as Xposed can cause a lot of bugs.
Q Alright, but I still want to flash Xposed, so which version do I need to install?
A Xposed is not yet available for nougat, however when it is ready you will need to use the version arm sdk 25.
Q Can I have an ETA for the next build?
A Yes, the next build will be Thursday evening (eastern time), unless if something goes wrong of course...
Q Do I need to provide a log if I'm reporting a bug?
A If you want it to be fixed faster (or at all) then yes, you should definitely provide a log.
Q I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A In TWRP, flash the substratum rescue zip in the substratum folder in the internal storage.
Q Can the builds be dirty flashed over each other?
A Yes, however make a nandroid first as there is a chance of getting a bootloop or encountering bugs, also bugs may only be reported on a clean flash.
Q How do I get a logcat, and what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog
just in case
mosimchah said:
just in case
Click to expand...
Click to collapse
Whow!
Another great rom for our device and the file is really sssmmaaaaall this time!
No unwanted stuff, debloated right out of the box. Just the way I like it..!
I like to see new liquidness coming back...
Will test it tonight and report later...
I'm really curious to the optimizations done in this rom/kernel.
I am really glad with what dedication you all write new code for this nevertheless a few years old device.
If only we had a few good guys like you from the beginning ...
But finaly I'm really happy not to sold my device to replace it with a buggy pixel tab, Lol!
2 things so far, The wifi is set to recongize 5ghz in GB rather then all( don't remember the code for 'all', I switched mine to US). And some apps will have outstretched videos after a couple of seconds ( one such app is watchESPN). but other then, very nice ROM. Smooth and no troubling installing.
This ROM looks like a real killer. I like the fact that it is optimized for our specific chip, and the configurabilitylooks sweet. What gapps package is recommended for this build? I usully go with open gapps nano, but I might try the aroma package once more. I like the "pick & play" aspect and the install ui. Anybody have input with the gapps. I think I am going to really like this ROM. Thanks again, guys! ;-DeanoD
This looks awesome, i will be waiting for an stable version
Right, just clean flashed and I chose Nano GApps.
There's a problem that's solvable. It appears that the built-in AOSP WebView might not be working properly. For instance:
Feynman Lectures app opens but does not load its main page
Lightning Browser opens, but gets stuck once the UI is visible.
GetTube opens, but crashes once the YouTube link is clicked
Lithium eReader catalog crashes
SwiftKey is usable, but accessing its main menu (likely the one where it uses WebView to go online) crashes the app
"Crashes", as in the app is frozen and stops responding and Android offers the app-kill popup.
After installing Android WebView from the Play Store, everything works perfectly again. Checked the IR, camera, played some games (Machinarium, Deus Ex GO, TWoM) and all appears working. And yes, this is a real minimal install, so no music player, no browser etc from the get go.
And thus, those moving in from that CM14 build, might not be able to wake up from home key, hide software buttons and be rooted from a default install. I don't mind the former two, so to get root, download and flash the zip from here:
https://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip
I'll do some further testing, will report with more findings or logs in a week or so.
ROM won't boot after 15 minutes. Stuck at Android boot screen. Suggestions?
hipocrazy said:
ROM won't boot after 15 minutes. Stuck at Android boot screen. Suggestions?
Click to expand...
Click to collapse
Did you flash any mods with the ROM? Make sure you wiped the system, cache, and dalvik cache before flashing
Pact said:
Right, just clean flashed and I chose Nano GApps.
There's a problem that's solvable. It appears that the built-in AOSP WebView might not be working properly. For instance:
Feynman Lectures app opens but does not load its main page
Lightning Browser opens, but gets stuck once the UI is visible.
GetTube opens, but crashes once the YouTube link is clicked
Lithium eReader catalog crashes
SwiftKey is usable, but accessing its main menu (likely the one where it uses WebView to go online) crashes the app
"Crashes", as in the app is frozen and stops responding and Android offers the app-kill popup.
After installing Android WebView from the Play Store, everything works perfectly again. Checked the IR, camera, played some games (Machinarium, Deus Ex GO, TWoM) and all appears working. And yes, this is a real minimal install, so no music player, no browser etc from the get go.
And thus, those moving in from that CM14 build, might not be able to wake up from home key, hide software buttons and be rooted from a default install. I don't mind the former two, so to get root, download and flash the zip from here:
https://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip
I'll do some further testing, will report with more findings or logs in a week or so.
Click to expand...
Click to collapse
Thanks for the feedback, I'll include webview with the next build
DeanoD said:
This ROM looks like a real killer. I like the fact that it is optimized for our specific chip, and the configurabilitylooks sweet. What gapps package is recommended for this build? I usully go with open gapps nano, but I might try the aroma package once more. I like the "pick & play" aspect and the install ui. Anybody have input with the gapps. I think I am going to really like this ROM. Thanks again, guys! ;-DeanoD
Click to expand...
Click to collapse
Aroma should work, I don't think anyone on the team has tested it though
mosimchah said:
Did you flash any mods with the ROM? Make sure you wiped the system, cache, and dalvik cache before flashing
Click to expand...
Click to collapse
No mods, not even gapps. I performed a factory reset prior to flashing. I did receive the e: unknown command error after flash.
Edit: followed the instructions in OP to the letter. ROM boots fine now!
First Impressions
For a first draft ROM, this looks solid, and runs very clean. Still trying to tweak the install but system settings refuses to open so far. Will re-install tomorrow. ;-Deano
DeanoD said:
For a first draft ROM, this looks solid, and runs very clean. Still trying to tweak the install but system settings refuses to open so far. Will re-install tomorrow. ;-Deano
Click to expand...
Click to collapse
Currently there are none of the usual customisation options that you would expect in custom ROMs, absolutely nothing, being able to wake the tablet by pushing the physical home button would be a nice start. I'm also finding that like some other ROMs I've had on this and other devices Titanium backup will fail to restore some backups, just doing the animation it does while restoring but never actually finishing (having to install the occasional app from the play store while TB was doing its thing to make it progress), I had no sign of that problem with the CM14.1 ROM.
Once they hit their stride with development things should progress nicely, LiquidSmooth was probably the best ROM I've used (at least on this device).
It has navbar customizations in the system UI tuner, app ops in the security settings, and one of the main features is the substratum theme engine, more features will be added soon, can you get a logcat for the titanium backup issue
Right now the plan is to iron out the reported bugs, and then focus on a lot more features, keep in mind, this is this literally our first release ever, don't expect it to have a ton of features on the very first release
Really impressed by this ROM. Amazing work guys!
mosimchah said:
It has navbar customizations in the system UI tuner, app ops in the security settings, and one of the main features is the substratum theme engine, more features will be added soon, can you get a logcat for the titanium backup issue
Click to expand...
Click to collapse
My first go at capturing something using Catlog is attached, TB trying to restore Adaway app & data for a while.
I have looked through pretty much the entire Settings interface and found no "system UI tuner" anywhere and no app that looks as though it would do any such thing, I have not removed a thing via TB or any other means.
WELCOME TO THE SNAPPATCH[ Featured by DroidViews and XDA ]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SOME THINGS ARE DIFFERENT TO THE AOSP SNAPPATCH
PLEASE MAKE SURE YOU ARE USING THE RIGHT VERSION FOR YOUR DEVICE / ANDROID OS VERSION AND VARIANT
ABOUT THE PROJECTStarted on the Nexus 6, Years ago is the Patch the Result of evolving custom ROMs to something more. Instead of uploading My Changes combined with a OS, is the POM just delivering the wanted Edits. It can be applied on top of any OS, and makes Android Updates independently from My Work. The latest and already 5th Revision of the POM is called Snappatch, and made for Snapdragon Xperia Devices running the very latest AOSP Systems. Coming with a huge amount of exclusive Configs and Optimizations is the Patch unleashing Your Device on a unexpected Way. You will raise the Performance, Efficiency, and Quality of the whole System, besides adding Features and Services which are not available on unpatched AOSP ROMs. The POM comes also with a Rooting Solution, Busybox and the full set of needed GApps to provide a great Pixel like Experience with the barely minimum of needed Apps out of the Box. Based on 8 Years of research and testing, made with Passion! The Snappatch sets Quality over Quantity...
Already adapted by Others for Stock Firmwares is the Snappatch still the first and Original Patch System. You will face it all over XDA in the next Years! Be Part of the Patch Revolution, get Patched!
FEATURES
Xperia DRM Fix and Kernels included
Xperia Apps cleaned out and replaced
Night Light and Ambient Display Settings
Latest Busybox with 400+ Applets (Excluded on Stock)
Magisk Stable Root included
SafetyNet Passing Changes
Pixel Bootanimation / Apps
Xperia and Pixel UI Sounds
Added advanced VR Capabilities
Added Features and Services
Optimized Google Apps Set
Optimized Camera Handling
Optimized Display Handling
Optimized Rendering Handling
Optimized Storage Handling
Optimized Services Handling
Optimized Multitasking Handling
Optimized Audio Handling
Optimized Microphone Handling
Optimized 4K & HDR Handling
Optimized Hardware Handling
Optimized Software Handling
(Features are summarized to keep the overview)
(Don't trust Lists, try it out by Yourself)
SUMMARY OF THE DEVELOPMENT
-Camera Configs can be still improved (Implented not all Configs right yet)
-Some Camera Apps may not Work. Recommended are:
--Snap Camera HDR (Play Store)
--Open Camera (Included / Play Store)
--Google Camera Mods (Some are working, others don't)
-Some Equalizers don't Process (Audio is routed different)
SUPPORTED AOSP DEVICES (BLUE)
SPECIAL THANKS TO
@D daydream for buying Me the Daydream View 2017! No VR Development with You!
XDA:DevDB Information
SNAPPATCH, ROM for the Sony Xperia XZ1
Contributors
Miustone, Miustone, Miustone, Miustone
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: ANDROID 8.0 / SDK 26
Version Information
Status: Snapshot
Current Stable Version: 101
Stable Release Date: 2018-04-27
Created 2018-04-28
Last Updated 2018-04-28
Fundamental:
Feedback:
-Which Device are You using?
-Which Patch Version are You using?
-Which Android Version are You using?
Before posting:
-Read, read, read! Make sure You've seen the whole Thread
-Make sure You've followed the Instructions from Post 3
-Make sure You're using the right Patch for Your OS (STOCK / AOSP)
-Make sure You've not used other Mods which could cause Bugs
Infos:
Instructions:
-Download the latest Firmware for Your Model (XperiFirm)
-Download and place "NewFlasher" in Your Firmware Folder
-Connect Your Device in Flash Mode (Volume Down + USB)
-Execute the NewFlasher Firmware flash
-Disconnect Your Device (Let it powered Off)
-Connect Your Device in Fastboot Mode (Volume Up + USB)
-Flash the latest Recovery from TWRP.me
-Boot the Firmware until You see the Setup Wizard
-Power Off the Device again
-Hold Volume Down and the Power Button to enter TWRP
-Format Data (Not just wipe, FORMAT)
-Reboot to Recovery
-Format Data again (Don't do any Wipes)
-Your Device is prepared, now go over to the Patch Instructions on the Website
-You can also use custom ROMs, but untouched Android is always the best Base for a Patch...
Download:
Snappatch Website
Please consider a Donation if You like My Work! [PayPal.Me] [Gift Code]
Thanks to @janjan for his awesome Kernels and the DRM Fix!
Really appreciate Your Work, and would be glad to use Your Kernel on MY XZP too :highfive:
(Files are uploading)
EDIT: UPLOADED
Let Me know how it goes! I just own the XZ Premium
Hello,
I have tried it in the XZ1, i flashed the latest firmware, ending in 145, formated data twice, mounted the storage in recovery, copied the 2 files, tried flashing the zip, it failed with error 7, i have modifed the updater script, because the model was maple, and not poplar, flashed ok, booted ok, with the pixel notification, when i tried setting it up, there was no keyboard to input the password to my wifi network, removed the password, tried again but the setup fails, it says google play services stopped, and does not go forward. I ve tried flashing open gapps, but still no luck.
Thank you for your efforts.
Help as please.....
I'm giving it error 7, the idea is that I found on youtube several things that were about to unpack the zip to look for a script and delete something from the script, all those videos in the script show something else to be deleted from the script, I tried to I delete something, the first row with "assert" but gave me error6 .... maybe I did not delete what need to work, maybe not have all the row deleted ... Thanks
Replace maple with poplar in the first row. It appears 3 times.
have it need unlock！
THANKS...
emyjojo said:
Replace maple with poplar in the first row. It appears 3 times.
Click to expand...
Click to collapse
It works, but there are 4 "maple" and there is ("This package is for" maple \ "devices car needs to be replaced ... Unfortunately, she tells me he can not sync with Google and the black screen remains
Sounds like the included GApps are not flashing right. Since Chrome is removed am i forcing a WebView install besides the Google Keyboard, Pixel Launcher and so on. It should all be there and working without further Edits or Tricks. I checked also the Updater Script and i really missed to remove the Device Checks before uploading. I will upload fixed Versions as soon as i can. Until that please check out if something was wrong while flashing and provide Logs from TWRP if possible (Got to Advanced, Copy Log after flashing).
Looking forward to give You a working Stock Patch! Think we can handle that
Nice...
Miustone said:
Sounds like the included GApps are not flashing right. Since Chrome is removed am i forcing a WebView install besides the Google Keyboard, Pixel Launcher and so on. It should all be there and working without further Edits or Tricks. I checked also the Updater Script and i really missed to remove the Device Checks before uploading. I will upload fixed Versions as soon as i can. Until that please check out if something was wrong while flashing and provide Logs from TWRP if possible (Got to Advanced, Copy Log after flashing).
Looking forward to give You a working Stock Patch! Think we can handle that
Click to expand...
Click to collapse
I'm looking forward to solving the next update, these are the problems, the problem with the error7 which is solved by zip unpacking and "maple" with "popolar" and this problem can not be done because you can not synchronize with google and it remains in black screen after trying to search for updates, I tried to flash Pico Package for Google Package Installer and Google Play services but it does not work,same problem and the stockpackage is got bootloap probably because google installed Ventor, I'm waiting for you to solve these problems, is overtake me ... thank you
Could u add dt2w and dt2s?
Araa01 said:
Could u add dt2w and dt2s?
Click to expand...
Click to collapse
That is at kernel level..
This is an awesome idea. I hope it pans out.
When you make the next update? I told you I can not setup process because she can not connect with google account and it remains in black screen, only status bar and navbar appears ... thanks
Wairing for new update
NEWS: https://plus.google.com/communities/...57640557144575
Miustone said:
NEWS: https://plus.google.com/communities/...57640557144575
Click to expand...
Click to collapse
Link doesn't work
snake218 said:
Link doesn't work
Click to expand...
Click to collapse
Search for the SNAPPATCH Community on Google+ or try this Link: https://plus.google.com/communities/101868357640557144575
Updates coming in the next Hours after fixing some last Stuff!
Hi,
I am downloading the patch for my 8342 version (stock) but I cannot see the snap.prop file within this folder.
I have checked the other XZ1 variant and all are having it.
Could you please confirm that I also need this file to proceed ?
If yes, could you please upload it ?
Many thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Features:
RIL: LTE, Calling + recording, SMS and MMS
Wi-Fi: Connection to 2.4 and 5 GHz, Wi-Fi Display with audio
Bluetooth pairing, sharing and audio
Audio & video playback, streaming and recording
NFC
GPS and sensors
Camera
Powered on/off and wireless charging
USB file transfer/MTP and charging
USB, Bluetooth and Wi-Fi tethering (hotspot)
Google services and SafetyNet compliant (banking apps and Google Wallet work out of the box)
Storage encryption and SDCard
LineageOS Recovery with encryption support (not required, but endorsed )
Slimport HDMI
LG Quick Circle case support with FlipFlap
Known issues:
DRM/Widevine L3: Amazon Prime and Play Now (Polish TV stream) are working and streaming, but the quality is 540p.
YouTube doesn't show 1440p in video quality options.
Slimport HDMI connection creates screen flickering, but it's not visible on an external display.
Won't work:
VoLTE
Check out the changelog in the post below.
Make sure you're on the correct firmware for your variant.
1. If you're coming from another ROM or performing a clean flash:
Reboot to Recovery
Backup any important data
Format Data partition
Wipe Dalvik, Cache and System
Flash the ROM
Flash GApps (optional, can't be flashed after the first boot)
Reboot to System
2. If you're updating the ROM or performing a dirty flash:
Reboot to Recovery
Flash the ROM
Wipe Cache
Reboot to System
Download LineageOS 18.1 ROM and Recovery
Alternative download for LineageOS 18.1
TWRP for LG G3
Google apps (MindTheGapps recommended)
Rooting your phone by Linus Tech Tips
Stock ROM by @MESA
3__HacerPermisivo.zip - this switches your selinux to permissive
bootimage_adb_unsecure by @AdrianDC - debugging, disables adb auth
Mr_Bump.zip by @dadi11 - fix for Secure booting error (boot certification verify)
Join G3 development channel on Telegram to get more info about my projects.
LineageOS GitHub repo
github.com/itsHardStyl3r
device and kernel sources
18.1, 23.04.2023
Code:
* Kernel: Updated prima driver (Wi-Fi)
* Kernel: Updated sdFAT driver from 2.3.0 to 2.4.5
* Kernel: Fixed race condition for TCP listens (https://gitlab.com/LineageOS/issues/android/-/issues/3916#note_669493796)
* Enabled DRM Clearkey 1.3 plugin
* Reimplemented ZRAM
* Fixed geotagging in photos
* Disabled wallpaper zooming effect to increase performance of app drawer
* Fixed Wi-Fi settings not being applied, including LG G3 default hotspot name
* Fixed Wi-Fi WPA3 networks
* Fixed turning off DiscoveryService and NearbyMessagesService
* Adjusted sepolicy settings
* G3 should now appear as a phone in File Managers via USB
* d85x, f400, vs985: Declared support for Mifare NFC tags
- ls990 does not have pn547 NFC chip, so I can't confirm it works.
* Reverted "Disable wifi AP MAC randomization" to fix 5 Ghz hotspot
- It works now: https://imgur.com/a/6JgSynU.
* Enabled XZ compression
* Fixed HIDL power stats, TetherController and TelephonyManager errors
* Updated screenshots
18.1, 14.04.2021
Code:
* April 2021 Android Security Bulletin: r34
* Promotion to Official 18.1 #306996 #306997
* Sanitized sources so I could push to LineageOS (mostly vendor stuff) - not really worth mentioning
* Fixed TimeKeep implementation
* Fixed "Switched to AOSP RenderScript" from 31.03.2021 update
18.1, 31.03.2021
Code:
* March 2021 Android Security Bulletin: r32
* Fixed encryption
* DRM protected now works (e.g. Netflix)
* Switched to AOSP RenderScript
* Builds now come with smaller font footprint
18.1, 14.02.2021
Code:
* Updated source (LineageOS/lineage-18.1)
* sepolicy additions
* device tree updates (Trust VINTF)
* CameraServiceProxy error fix
* more bringup
18.1, 20.12.2020
Code:
* Initial release
https://imgur.com/a/j98w3ko
Reserved #3
Reserved #4
You are great, thank you..
The second beta release is awesome. Everything seems as it should be. Animations are very smooth. I wonder what is next.
Horrah! just downloading...
thank you for your hard work!
turquoise.ht said:
You are great, thank you..
i wanna submit my very first impression after a few hours of use. i had no problem during installation and in general everything is ok. animations were laggy at the beginning but they are smoother now after a while. i am sure things will get better soon. thank you very much again for your efforts.
-google drive crashing, google chrome cannot see the google account so cannot start sync.
-magisk 20.4 does not work but 21.1 beta works.
Click to expand...
Click to collapse
These bugs are related to the GApps, these are very shady but the basics work. I am waiting for @walter79 to respond and I'll build our own GApps.
Thanks for the feedback.
D855 32gig: came from 17.1, flaweless install, all works perfect, no lags or hassles. Nice work, will be my LOS from now on! Thank you HardStyl3r for this ROM.
and what Gapps can I install for LG g3 D855?
fefe128 said:
and what Gapps can I install for LG g3 D855?
Click to expand...
Click to collapse
you will find it in the download folder ==> first post here....
fefe128 said:
you will find it in the download folder ==> first post here....
Click to expand...
Click to collapse
yes. I have it. I apologise
I installed and want to switch instead of Lineage recovery sleep on TWRP recovery. How ?
fefe128 said:
I installed and want to switch instead of Lineage recovery sleep on TWRP recovery. How ?
Click to expand...
Click to collapse
same here: it seems root + TWRP is gone...
fefe128 said:
I installed and want to switch instead of Lineage recovery sleep on TWRP recovery. How ?
Click to expand...
Click to collapse
LZ_ said:
same here: it seems root + TWRP is gone...
Click to expand...
Click to collapse
The setup wizard is tricky this time. It automatically replaces TWRP with LineageOS Recovery unless you uncheck the option. To bring back TWRP, use flashable ZIP in my TWRP thread, flash it (either adb sideload or sdcard is fine) and skip the signature check failure.
HardStyl3r said:
The setup wizard is tricky this time. It automatically replaces TWRP with LineageOS Recovery unless you uncheck the option. To bring back TWRP, use flashable ZIP in my TWRP thread, flash it (either adb sideload or sdcard is fine) and skip the signature check failure.
Click to expand...
Click to collapse
Good news on the LS990. installed and booted up fine. Data and telephony both working. Rom seems just fine. Still have my twrp . No fc and no reboots. Can't get magisk 20.4 to flash so no root yet but as smoothly as it's running so far we're looking good. Thank's for the LS990 build.
Update !! Found Magisk 21 and installed root. Works fine now. One question about setup manager related to installing lineage recovery. Is it a onetime setup question or will it ask this on future updates and or resets ? Just wondering if it's something we need to be on guard against . Possible to disable the feature ? Fortunantly I happen to catch it and uncheck it so I'm good. Thanks
LS990 users you can install this . The old reboot problem we had with lineage 17 is gone. This runs good enough I'm going to continue with it as daily driver for now.
Max Frost said:
Good news on the LS990. installed and booted up fine. Data and telephony both working. Rom seems just fine. Still have my twrp . No fc and no reboots. Can't get magisk 20.4 to flash so no root yet but as smoothly as it's running so far we're looking good. Thank's for the LS990 build.
Update !! Found Magisk 21 and installed root. Works fine now. One question about setup manager related to installing lineage recovery. Is it a onetime setup question or will it ask this on future updates and or resets ? Just wondering if it's something we need to be on guard against . Possible to disable the feature ? Fortunantly I happen to catch it and uncheck it so I'm good. Thanks
LS990 users you can install this . The old reboot problem we had with lineage 17 is gone. This runs good enough I'm going to continue with it as daily driver for now.
Click to expand...
Click to collapse
This should only pop up when you clean /data. As far as I know, Setup Wizard only appears on first boots, which includes clean /data. If you've unchecked this, I think you are safe. Enjoy. And yeah, the latest Magisk beta works.
Fixed: took the latest Magisk-v21.1.zip, then run the TWRP-App and installed .bin file. Enable Advanced restart and all works fine again!
Why can't I find Advanced Reboot option? Someone enliten me!