I present you my private slim builds.
It's pure stock slim with full -O3 support.
Features:
Rom - linaro 4.8
Kernel - linaro 4.8
JustArchi optimizations
Official changelog:
SLIMROM
My changelog:
10-01-2015 Slim5.02: Latest source, used GCC 4.8 for rom and kernel.
14-12-2014 Slim5.0: Latest source: alpha 9, changed a lil bit flags, rom should be flawless now
09-12-2014 Slim5.0: Latest source: alpha 8
01-12-2014 Slim5.0: Latest source: alpha 6
27-11-2014 Slim5.0: Latest source: alpha 5, fixed playstore.
24-11-2014 Slim5.0: Latest source: alpha 4, full -O3 included, some icons in google play are glitchy. Linaro 4.8
22-11-2014 Slimpop: Latest source: alpha 3
13-11-2014 Slimpop: Latest source: alpha 2
Bugs:
You tell me (it's alpha)
Gapps force close = reflash gapps without wipes (u wont lose accounts etc).
Installation:
moving from another rom? do full wipe before flashing
moving from previous versions of slim5.0 (built by me/official/sb else)? Just install, no wipes required.
having system crashes etc. - full wipe
gapps force close - reflash gapps
for root access, flash SuperSU
Download:
Slim 5.0
Slim5.02 10-01-2015
Credits:
Slimroms.net
JustArchi optimizations
Linaro
@TheLoonyBin
Source:
Slim5.0
How to build:
You need 64bit linux, I use Manjaro based on Arch
Follow this turorial (Ubuntu based): Ubuntu
Follow this turorial (Arch based): Arch
Sync source: repo init -u git://github.com/SlimRoms/platform_manifest.git -b lp5.0 && repo sync
Initialize building environment to bash: . build/envsetup.sh
Try to build, it should download device source: time brunch slim_hammerhead-userdebug
After downloading device tree u can stop compilation process
Go to slim_folder/.repo/local_manifests and replace it with following code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Removals -->
<remove-project name="platform/external/webp" />
<remove-project name="SlimRoms/android_build" />
<!-- Slim device and kernel source -->
<project name="SlimRoms/device_lge_hammerhead" path="device/lge/hammerhead" remote="github" revision="lp5.0" />
<project name="SlimRoms/kernel_lge_hammerhead" path="kernel/lge/hammerhead" remote="github" revision="lp5.0" />
<!-- My choice, usually these repos are ahead of default ones -->
<project name="JustArchi/android_external_webp" path="external/webp" remote="github" revision="cm-11.0" />
<project name="TheLoonyBin/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="lp5.0" />
<project name="TheLoonyBin/proprietary_vendor_qcom" path="vendor/qcom" remote="github" revision="lp5.0" />
<project name="TheLoonyBin/proprietary_vendor_broadcom" path="vendor/broadcom" remote="github" revision="lp5.0" />
<project name="ArchiDroid/Toolchain" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideab-4.8Li" remote="github" revision="linaro-4.8-arm-linux-androideabi" />
<!-- My repos, fixes, patches etc -->
<project name="xenuPL/android_build" path="build" remote="github" revision="lp5.0" />
</manifest>
Clean all stuff: make clean
Wipe ccache: rm -rf ~/.ccache
Build rom: brunch hammerhead -jx (x-number of cores)
Awesome ~ will give it a flash later on here goes my weekend :victory:
Hellz yah !! Thank you Brother for dropping some fresh new dope !!
Time to whip out the ye ole' TWRP syringe and slam this potent goodness in my phone-arm!!
Thanks again brother for the f¡x !!
��
This is awesome - super stable too. Thanks man!
I'd love to see someone do some AOSPA builds in the future.
Oh I will try both of them downloading.....:silly:
Got aospa sources, but i need to fix some stuff. Will try to build it this week.
Omni build running smooth with Linaro r59. I'd love to see the CarbonROM with the Archi optimizations too if you can.
New slim
satyr007, great work!
These optimizations, are really great, I updated Omni to latest official and now i see how your build was faaast.
I wish these were the daily Omni builds
Cheers!
Great job feels snappier slim
new omni
This Omni rom works fine.
I'm testing the Kernel Big-Bum CM.and I think the results are positive.Sorry,I can not upload screenshots.
Tested Omni rom and it's blazing fast. Went back to PA stock because I need it's features. Hope that OP will manage to do a PA version. Thank you for bringing forth these tweaks for our hammerhead.
Please post a mirror.. mega is blocked in my country. thanx in advance
Any Chance for an optimized Mahdi Rom? Tested your Slim Version and was impressed. But Mahdi gives me more options..
Sent from my LG-V500 using XDA Free mobile app
Slim download not available
peluillo said:
Slim download not available
Click to expand...
Click to collapse
Working now :good:
@satyr007 check pm.
latest slim 7.2.1
First AOSPA build. I will build only these 3 roms from time to time (once a week or two)
Related
hi,
im having trouble building a kernel that actually boots liquidsmooth (https://github.com/LiquidSmooth)
I tried using https://github.com/CyanogenMod/android_kernel_sony_msm8974/tree/cm-12.0 and https://github.com/Tommy-Geenexus/android_kernel_sony_msm8974.
Kernel compiles fine but when i flash the kernel the device is stuck at sony bootlogo. also i cant enter recovery. if i press volume up when the led is pink it turns yellow.
its no difference if i use cwm or twrp recovery
Also applied ramdisk size fix for twrp with no difference.
If i flash http://forum.xda-developers.com/xperia-z-ultra/development/anykernel2-zombie-t2926584 my rom (liquidsmooth lp self compiled) boots witout problem. but if i compile the same kernel its about 3mb bigger.
Im using google arm-eabi toolchain 4.8
also tried linaro and sabermod with no difference.
Anyone had the same problem?
How do i get logs at this stage?
Any suggestions?
Didnt have any problems with kitkat.
Manifest:
<project path="device/sony/togari" name="CyanogenMod/android_device_sony_togari" remote="gh" revision="cm-12.0"/>
<project path="device/sony/rhine-common" name="CyanogenMod/android_device_sony_rhine-common" remote="gh" revision="cm-12.0"/>
<project path="device/sony/msm8974-common" name="CyanogenMod/android_device_sony_msm8974-common" remote="gh" revision="cm-12.0"/>
<project path="device/sony/common" name="CyanogenMod/android_device_sony_common" remote="gh" revision="cm-12.0"/>
<project path="device/sony/qcom-common" name="CyanogenMod/android_device_sony_qcom-common" remote="gh" revision="cm-12.0"/>
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" remote="gh" revision="cm-12.0" />
<project path="hardware/sony/DASH" name="CyanogenMod/android_hardware_sony_DASH" remote="gh" revision="cm-12.0" />
<project path="vendor/sony" name="TheMuppets/proprietary_vendor_sony" remote="gh" revision="cm-12.0"/>
<project path="vendor/extra" name="VanirAOSP/vendor_qcom_opt" remote="gh" revision="L5" />
<project path="bootable/recovery" name="CyanogenMod/android_bootable_recovery" groups="pdk" />
<project path="kernel/sony/msm8974" name="CyanogenMod/android_kernel_sony_msm8974" remote="github" revision="cm-12.0" />
<!--project path="bootable/recovery" name="omnirom/android_bootable_recovery" remote="gh" revision="android-5.0" />
<project path="kernel/sony/msm8974" name="Tommy-Geenexus/android_kernel_sony_msm8974" remote="gh" revision="master" /-->
edit:
fixed, problem was using sabermod androideabi toolchain instead of googles.
According to Alx31TLse you cant use sabermod toolchain for xperia z line.
It seems its messing up the busybox or cpio executable for the target. I would guess the problem is with cpio because the leds for entering recovery where working which are controlled by busybox.
If i change https://github.com/CyanogenMod/android_device_sony_msm8974-common/blob/cm-12.0/boot/custombootimg.mk line 36 to
$(hide) $(MKBOOTIMG) --kernel $(PRODUCT_OUT)/kernel --ramdisk $(PRODUCT_OUT)/ramdisk.img --cmdline "$(BOARD_KERNEL_CMDLINE)" --base $(BOARD_KERNEL_BASE) --pagesize $(BOARD_KERNEL_PAGESIZE) --dt $(INSTALLED_DTIMAGE_TARGET) $(BOARD_MKBOOTIMG_ARGS) -o $(INSTALLED_BOOTIMAGE_TARGET)
kernel finally boots but no recovery of course.
if i look at the combinedroot folder everything looks ok.
i dont get whats going wrong. im guessing it fails at extracting the ramdisk when using the init script from combinedroot. i also tried to compress the kernel with gzip and also tried using a compressed ramdisk but that didnt change a thing.
any ideas?
@OmarEinea @Saatvik Shukla @Alx31TLse
you did compile successfully do you have any suggestions?
1st of all at least specify u wanna make it with twrp wich needs change to your rhine-common
u can take omni's or slim rhine-common as its already twrp-ified. or else if u take cm one, u need twrp's fstab, tagets in board config and and indeed twrp flags. to make it easier take omni's u will save time and headaches.
and main question is...why are u taking msm8974 kernel from tommy wich is for stock rom, u really like things complicated bro. if u take mine from team validus repos or Omar's one it will surely works, and on top of that, kexec patched for multi rom...
If u absolutely wanna keep working with Tommy's one, good luck but imo if u wanna make a good custom kernel change ur base and cherry-pick his stuff for gamma control and everything if its the reason why u looking for his kernel source.
Alx31TLse said:
1st of all at least specify u wanna make it with twrp wich needs change to your rhine-common
u can take omni's or slim rhine-common as its already twrp-ified. or else if u take cm one, u need twrp's fstab, tagets in board config and and indeed twrp flags. to make it easier take omni's u will save time and headaches.
and main question is...why are u taking msm8974 kernel from tommy wich is for stock rom, u really like things complicated bro. if u take mine from team validus repos or Omar's one it will surely works, and on top of that, kexec patched for multi rom...
If u absolutely wanna keep working with Tommy's one, good luck but imo if u wanna make a good custom kernel change ur base and cherry-pick his stuff for gamma control and everything if its the reason why u looking for his kernel source.
Click to expand...
Click to collapse
thanks for reply,
im sorry i thought i made it clear that i tried usind cwm and twrp.
already made all the changes to rhine, ramdisk and stuff... set all the flags and made changes to recovery rhine-common/rootdir/init.recovery.qcom.rc like described here:
http://forum.xda-developers.com/showthread.php?t=1943625
was never a problem with kitkat.
https://github.com/Tommy-Geenexus/android_kernel_sony_msm8974 which im using is lollipop cm kernel forked from cm. which is booting if altering "combinedroot.fs" to ramdisk.img like written in post #2 but of course without recovery!
if i dont alter "costumbootimg.mk" device is stuck at sony logo.
no difference if i change to cwm recovery either. its also the same if use cm kernel instead of tommys. i could try validus but as it is a forked cm kernel im guessing i will have the same result.
there is no kernel at github from omareinea which would be compatible with lollipop.
Cuz his kernel is not in his account, its in greatdevs organisation.
Well sorry but me, i don't know then...it works on my roms and cuz fota kernel is less complicated...im no more crushing my head on recoveries xD
update
i made a clean/fresh linux install ubuntu (14.10)
i reseted the device with flashtool to sony stockfirmware .108 and installed from fresh.
used different sources (cm, validus, greatdevs).
problem still persists. :crying:
if i check the uncompress combinedroot.cpio with cpio -tv combinedroot.cpio everything looks good.
and as stated if i use ramdisk.img instead of combinedroot.fs kernel/rom boots but no recovery... FOTAKernel is installed with twrp. If i flash a kernel i didnt build there is no problem booting recovery or rom.
problem was the android-eabi toolchain.
changed to default google toolchain and now its working.
i feel stupid now
before i only tried different arm-eabi toolchains.
now it all make sense.
i guess it must be problem in compiled cpio.
MusterMaxMueller said:
problem was the android-eabi toolchain.
changed to default google toolchain and now its working.
i feel stupid now
before i only tried different arm-eabi toolchains.
now it all make sense.
i guess it must be problem in compiled cpio.
Click to expand...
Click to collapse
don't feel stupid, cuz i did same error and took me a month to find out.
Hey guys, so I finally got my hands on S3 and the Stock ROM on this is 4.3 and so out-dated now and it lags when I install many apps. I was planning on installing CM 11 official but it has got some bugs. Can someone please suggest a stable ROM without any bugs and good battery life? Lollipop or Kit-Kat whatever ROM you think is great.
<b><font color="Red">Questions? Use Q&A!</font></b><br />
<br />
<b><font color="RoyalBlue">Build 12 Download: MEGA | XDA</font></b><br />
<br />
<b><font color="DarkBlue">Suggested GAPPS</font></b><br />
<b><font color="DarkBlue">Other GAPPS</font></b><br />
<br />
<font color="Blue">Changelog:</font><br />
<br />
Build 12<br />
- Went back to closed-source sensors, as open-source ones aren't working completely perfect yet<br />
- Fixed netflix, it should work properly now<br />
- Updated sources<br />
Build 11<br />
- Increased earpiece volume slightly, as it was barely heard outdoor<br />
- Fixed SELinux derps introduced in B10 (sysfs denials)<br />
- Fixed more SELinux denials related to recently changed parts (open-source sensors & bluetooth)<br />
- KERNEL: Fixed dm-crypt not accepting discard requests which resulted in failed encryption (CM10.2 regression)<br />
- Updated sources<br />
Build 10<br />
- Fixed (compass) and reintroduced open-source sensors<br />
- Misc SELinux updates<br />
- Misc hwcomposer fixes and improvements<br />
- Updated sources<br />
- Android 5.1.1 revision 6 (LMY48G)<br />
- Probably other things that I forgot already<br />
Build 9<br />
- Our CM sources have been rebased and resynced to fix derps and other misc issues<br />
- Fixed most (if not all) hardware encoder/decoder issues<br />
- Improved stability, compatibility, battery life and performance drastically while encoding/decoding movies<br />
- hwcomposer improvements and fixes<br />
- Wi-Fi firmware updates & cleanup<br />
- Updated sources<br />
Build 7<br />
- Fixed mobile networks search (for good this time)<br />
- Various kernel cleanups & stability improvements<br />
- Added proper touchkey backlight support. They don't light up on screen touch anymore (stock behaviour)<br />
- Hopefully fixed Wi-Fi dropouts during night<br />
- Updated sources<br />
Build 6<br />
- Fixed mobile networks search<br />
- Various kernel cleanups & stability improvements<br />
- Updated sources<br />
Build 5<br />
- Kernel: Various improvements, zRAM should be more responsive now.<br />
- RIL: Fixed & Updated Exynos4RIL java class, long shutdown issue resolved<br />
- Updated sources<br />
Build 4<br />
- Android 5.1.1<br />
- Kernel: Changed version type to -CM-ArchiKernel-base, hope you won't mix it up with AK now<br />
- Kernel: Does not include BFQ anymore, CFQ is default.<br />
- Updated sources<br />
Build 3<br />
- Major updates to RIL (again)<br />
- ArchiKernel: Haptic: Made get() and store() consistent<br />
- Updated sources<br />
Build 2<br />
- Major updates to RIL client (V11)<br />
- Updated i9300 RIL header (V11)<br />
- Major updates to RIL blobs (XXUGOA2)<br />
- Network settings FC fixed<br />
- MMSes fixed<br />
- Sensors fixes<br />
- Added vibration intensity to stock kernel<br />
- Updated sources<br />
Build 1<br />
- Initial release<br />
- Everything what worked in CM12.0 should work, too<br />
- Fast overview: HWC, RIL, Wi-FI, RIL, Sensors, Camera are fine, rest is untested<br />
- MMSes not yet fixed (known bug from CM12.0)<br />
<br />
<br />
<b>Background:</b><br />
Due to lack of official maintainer for i9300 device for CyanogenMod. I, together with @Moster2 decided that we will work unofficially on i9300 device tree for CM12, to bring Lollipop goodness to our beloved Galaxy S3.<br />
All builds provided in this thread are <b>UNOFFICIAL</b>, which means that:<br />
- There is no official support for i9300<br />
- There are no OTAs available<br />
- There are no automated "nightglies"<br />
<br />
At some point, we definitely will try to make proper pull requests, and maybe even support CM12 officially, but at the moment this project is in WIP - Work-In-Progress state, and many things are still broken/unusable. Until we finish, all builds are unofficial, and proper device support is not finished yet.<br />
<br />
At the moment, this project is considered: <b><font color="green">BETA</font></b>. All core functions <b>should work</b>, ROM <b>shouldn't have any critical issues</b>, but it's <b>still not ready to mark as stable</b>. However, it <b>should work properly as daily driver</b>.<br />
<br />
<b><font color="red">Please refrain from talking about other kernels than stock. We can't track every kernel and it's problems, hence, you're using other kernels at your own risk. Please don't report bugs while you're using custom kernels.</font></b><br />
<br />
Main developers:<br />
<b>- JustArchi<br />
- Moster2</b><br />
<br />
Thanks to:<br />
<b>- dhiru1602<br />
- arter97<br />
</b><br />
<br />
<b>Current issues</b><br />
<b>Manifest / Sources</b><br />
<br />
We work on this project for <b><font color="green">FREE</font></b>. While not mandatory, donations encourage us to continue to do so, and we'd deeply appreciate them, if you feel generous.<br />
<br />
<b>Donate to JustArchi</b><br />
<br />
Build instructions:<br />
Follow <b>CM build instructions for i9300</b>. When doing <b>repo init</b>, don't forget to <b>declare CM-12.1</b> branch (-b cm-12.1) instead of the default one. <br />
<br />
Before "breakfast i9300", you must include our manifest and resync the sources:<br />
<br />
croot<br />
cd .repo<br />
mkdir -p local_manifests<br />
cd local_manifests<br />
wget https://raw.githubusercontent.com/ArchiDroid/manifest/cm-12.1/roomservice.xml<br />
croot<br />
repo sync<br />
Click to expand...
Click to collapse
<br />
<br />
<b>Notice:</b> Our manifest already includes proprietary_vendor_samsung, so <b>don't execute ./extract-files.sh</b>. Just repo sync.<br />
<br />
Then follow "breakfast i9300" and the rest of the commands in original instructions, while keeping in mind above notice.<br />
<br />
<b><u>XDAevDB Information</u></b><br />
<b>[5.1.1] [Build 12] [BETA] [2015-07-18] CyanogenMod 12.1 for i9300, ROM for the Samsung Galaxy S III I9300</b><br />
<br />
<b><u>Contributors</u></b><br />
JustArchi, Moster2, arter97 <br />
<b>Source Code:</b> https://github.com/ArchiDroid<br />
<br />
<b>ROM OS Version:</b> 5.1.x Lollipop<br />
<b>ROM Kernel:</b> Linux 3.0.x<br />
<b>Based On:</b> CyanogenMod 12.1<br />
<br />
<b><u>Version Information</u></b><br />
<b>Status:</b> Beta<br />
<br />
<b>Created</b> 2015-03-29<br />
<b>Last Updated</b> 2015-07-17
Gesendet von meinem GT-I9300 mit Tapatalk
heartbrake said:
Hey guys, so I finally got my hands on S3 and the Stock ROM on this is 4.3 and so out-dated now and it lags when I install many apps. I was planning on installing CM 11 official but it has got some bugs. Can someone please suggest a stable ROM without any bugs and good battery life? Lollipop or Kit-Kat whatever ROM you think is great.
Click to expand...
Click to collapse
I think that every ROM including factory stock will have one or two bugs.
However, the three ROMs that I like most ATM are:
DN4 KK 4.4.4 based (do make sure to upgrade to Boeffla 7.6 kernel) - no very recent updates but Lollipop UI mod is available in the Themes section (IMO the ROM performs better without it) For me this has been the most solid KK 4.4.4 ROM
Amcha v6.10 - KK4.4.4 - a great ROM all round IMO based on S3 LTE firmware
Blekota Note 4 lite also KK 4.4.4 based - very good ROM with Lollipop UI, hints of S6 and pretty frequent updates
Try this one -
[ROM][GT-I9300][KK 4.4.4]?S5 Sensation ROM™ v11.0?[AROMA][OTA][MAY05,2015] - excellent rom
or qaraqumus ROMs (4.3 or 4.4)
You won't regret...
Try ArchiDroid...
heartbrake said:
Hey guys, so I finally got my hands on S3 and the Stock ROM on this is 4.3 and so out-dated now and it lags when I install many apps. I was planning on installing CM 11 official but it has got some bugs. Can someone please suggest a stable ROM without any bugs and good battery life? Lollipop or Kit-Kat whatever ROM you think is great.
Click to expand...
Click to collapse
Hi,
After 15 month of experience, what I can higly recommend to you is ArchiDroid. This soft has two versions: AD 1.X (based on stock Android 4.3) and AD 2.X (3.X actually, based on pure CM 12 with magnificent speed & fluidity optimizations). Today a STABLE version of the former one is going to be released, however experimental version which has beeing developed for a few months is far more stable than most LP based ROMs. So you can choose between Android 4.3 and 5.1.1. Want KitKat CM 11 ? You can also have it - you need to download STABLE version of ArchDroid 3.0.2 from the end of 2014. It is not updated any more and got an annoying bug from google (constant FC of Google Play Services app) nowdays, but you can easily find a solution within following links.
Why ArchiDroid ? It's developer put utmost pressure on reliability and quality. No compromises. This is the reason of creation of two version of his soft. Version 1.X is best when your highest priority is compatibility (for example BT headsets), stability and battery. Version 2.X is demon of speed. Beleve me - I used version 1.X quite a long time, being accustomed to stock interface and not so keen on big experiments. When I finally flashed version 2.X, the difference with fluidity and smoothness was so great... I use this version till this moment and prepare to switch to Lollipop (AD 3.1 STABLE). This version is claimed by his creator to be even faster and smoother than KK version (3.0.2). This soft is really stable, fast and battery friendly. Many optimizations means for example, that you can forgot about ads - ad blocking is just implemented in ArchiDroid. What else - using my mobile with some tuning (tasker, greenify, lux) and not gaming - just internet, mail, chat, music - I have everage SOT between 3,5 and 5 h. With great speed of this soft (no lags and difference in speed after half a year w/o reflashing)...
Aha, more than year before, hesitating which ROM will be the best choice for me, I tested as far as I remember 3 or 4 best ranked ROMs. And decided to choose AD - with no doubts.
Here you have the link to AD 2.X (3.X) thread. In a few post at the beginning you will find FAQ Q/A post - read it, it's worth it.
http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
good luck !
The best one is Archidroid 3.X . It's fast,light and has many optimizations and far more stable than many LP roms.
http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
HeartBrake, Did you try any of the ROM's mentioned here or other. I am also in a similar situation and landed upon this thread. I have recently rooted my Galaxy S3 I9300, and currently have 4.3. I am also looking for a ROM which will give me good battery life and better connectivity. I am facing mobile connectivity issues frequently nowadays.
What's the main bug with Archidroid 2.x? I'm using Archidroi 1.x at the moment but fancy a play with an AOSP rom. Can it be used on an unrooted phone? I have one phone rooted, but need an unrooted phone for Barclays mobile banking app.
Hey i am new here and i am searching for a good custom rom currently iam running on android revolution with boeffla kernel runs very well but i would like something slimmer and without aroma stable and bugless would be nice too hope someone can help me
Device GT-I9300
For those that don't know what Evervolv is, Evervolv is an AOSP (Android Open Source Project) rom aimed at Snapdragon powered devices. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
If you would like to contribute to Evervolv, please visit our Gerrit Code Review.
Current version: Based off 6.0.1 Marshmallow)
Features:
Extended PowerMenu
Battery %,
Volume button music control.
Trackball Wake (Available on devices with a trackball/pad)
CM Theme manager
ability to turn all customization off with one switch in the toolbox, giving you 100% aosp look and feel.
eng builds (instead of userdebug like everyone else) providing more open experience (ie adb root by default)
full complement of commandline tools (busybox, vim, ssh, curl/wet with ssl support!)
custom updater written from scratch by Preludedrew and Texasice, featuring automatic update checks,
support for downloading gapps, and advanced automatic install (TWRP and CWM supported but TWRP preferred)
Bug Reporting:
Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use EVPaste to post your logs.
Downloads:
7-4 Build
Source:
Evervolv Github
Device Tree
Tab A common tree
MSM8916-common tree
Kernel Source
Changelog:
View the recent changes at Evervolv Gerrit
Donations:
If you wish to donate please do so here (Paypal)
What's working:
Touchscreen
Power, Home, Recents, Back buttons
Wifi
Bluetooth
Camera
Sensors
GPS
Storage's (internal, external, adoptable storage)
Bugs/Not Working:
Initial setup takes a while to initialize
Audio
Video/DRM
Offline charging
Playstore downloads old app versions
How to flash a Rom properly?
Make sure you are using Lollipop Firmware or your touch will be flipped we are activily working on supporting the Marshmallow firmware
Copy the rom and gapps to your tablet
Boot into your custom recovery
OPTIONAL make a backup of your current running rom and store it on your MicroSD-Card or on your PC/Laptop
Wipe dalvik cache
Wipe/format system
Wipe/format data
Flash rom
Flash gapps
Reboot and give your device some time to do it's first boot!
In case someone likes to compile on their own:
You need to setup Linux first, good tutorial here:
Ubuntu / Xubuntu:
- https://nathanpfry.com/how-to-prepar...-android-roms/
- https://nathanpfry.com/how-to-setup-...-android-roms/
- https://nathanpfry.com/how-to-set-up...-android-roms/
- https://nathanpfry.com/how-to-setup-...-android-roms/
Arch based Linux ready to go:
- BBQLinux by @codeworkx http://bbqlinux.org/
Once you have synced Evervolv source run the following in terminal:
Code:
mkdir -p .repo/local_manifests
nano .repo/local_manifests/local_manifest.xml
Add the following to your local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
-<manifest>
<project revision="mm-6.0" remote="github" path="vendor/samsung" name="Evervolv/android_vendor_samsung"/>
<project revision="mm-6.0" remote="github" path="hardware/samsung" name="Evervolv/android_hardware_samsung"/>
<project revision="mm-6.0" remote="github" path="kernel/samsung/msm8916" name="Evervolv/android_kernel_samsung_msm8916"/>
<project revision="mm-6.0" remote="github" path="device/samsung/qcom-common" name="Evervolv/android_device_samsung_qcom-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/msm8916-common" name="Evervolv/android_device_samsung_msm8916-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt5-common" name="Evervolv/android_device_samsung_gt5-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt510wifixx" name="Evervolv/android_device_samsung_gt510wifixx"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt58wifixx" name="Evervolv/android_device_samsung_gt58wifixx"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/audio-caf/msm8916" name="Evervolv/android_hardware_qcom_audio-caf"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/display-caf/msm8916" name="Evervolv/android_hardware_qcom_display-caf"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/media-caf/msm8916" name="Evervolv/android_hardware_qcom_media-caf"/>
<project revision="mm-6.0-caf" remote="github" path="hardware/qcom/bt-caf" name="Evervolv/android_hardware_qcom_bt"/>
<project revision="mm-6.0-caf" remote="github" path="hardware/qcom/wlan-caf" name="Evervolv/android_hardware_qcom_wlan"/>
</manifest>
Save the file.
Back in terminal:
Code:
repo sync
. build/envsetup.sh
lunch gt510wifixx
make otapackage
(you can replace gt510wifixx with gt58wifixx if you like to build for the Galaxy Tab A 8.0 WIFI (SM-T350)
Great work man, happily waiting for lte support to get this great cheap tab bloadware-free:highfive:
Hello, this ROM is also compatible with the version Galaxy Tab A SM-T550? Thank y
pickmod said:
Hello, this ROM is also compatible with the version Galaxy Tab A SM-T550? Thank y
Click to expand...
Click to collapse
Umm not trying to sound like a jerk here but doesn't the title of the thread say it's for the Samsung Tab SM-T550?
---------- Post added at 18:02 ---------- Previous post was at 18:00 ----------
What about the Samsung Tab A 8.0 (SM-T350)? Will it work? Would love to flash it. ?
alias4ever said:
Umm not trying to sound like a jerk here but doesn't the title of the thread say it's for the Samsung Tab SM-T550?
---------- Post added at 18:02 ---------- Previous post was at 18:00 ----------
What about the Samsung Tab A 8.0 (SM-T350)? Will it work? Would love to flash it.
Click to expand...
Click to collapse
have a look here
http://forum.xda-developers.com/andr...-t350-t3411150
@deadman96385:
First of all many apreciate for your hard work, you didn`t give up just like me^^
Will it be possible to compile pure cm with your repos?
Just saw that you updated the branches...
Will both Galaxy-Tab-A and Evervolv repos be updated?
Maybe you can add a how-to of flash for some new users just like that: https://andi34.github.io/faq.html
And some additional informations later like here :http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
Thanks @Android-Andi
This is not meant to be some kind of criticism, just wanna support this device thread
alias4ever said:
What about the Samsung Tab A 8.0 (SM-T350)? Will it work? Would love to flash it.
Click to expand...
Click to collapse
Here is Evervolv for the T350
http://forum.xda-developers.com/android/development/rom-evervolv-galaxy-tab-sm-t350-t3411150
Chemnitzer said:
have a look here
http://forum.xda-developers.com/andr...-t350-t3411150
@deadman96385:
First of all many apreciate for your hard work, you didn`t give up just like me^^
Will it be possible to compile pure cm with your repos?
Just saw that you updated the branches...
Will both Galaxy-Tab-A and Evervolv repos be updated?
Maybe you can add a how-to of flash for some new users just like that: https://andi34.github.io/faq.html
And some additional informations later like here :http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
Thanks @Android-Andi
This is not meant to be some kind of criticism, just wanna support this device thread
Click to expand...
Click to collapse
It should be possible to build cm with the repos but i have not tried it yet, the Galaxy-Tab-A org will be were i test things out and once its stable it will be merged on to the Evervolv repos. I will add some of the info you mentioned
Edit: 3rd post now has install instructions and a compile guide
deadman96385 said:
Here is Evervolv for the T350
http://forum.xda-developers.com/android/development/rom-evervolv-galaxy-tab-sm-t350-t3411150
It should be possible to build cm with the repos but i have not tried it yet, the Galaxy-Tab-A org will be were i test things out and once its stable it will be merged on to the Evervolv repos. I will add some of the info you mentioned
Click to expand...
Click to collapse
Just figured that some of your source links are not working
Chemnitzer said:
Just figured that some of your source links are not working
Click to expand...
Click to collapse
Fixed there was an extra " on a couple of them
Very cool, hope you support tgphe LTE version soon.
Gesendet von meinem SM-T555 mit Tapatalk
Blindie said:
Very cool, hope you support tgphe LTE version soon.
Gesendet von meinem SM-T555 mit Tapatalk
Click to expand...
Click to collapse
Will be added by deadman in time, have Seen it in beta repo already so work is in progress:victory:
omfg finally someone did it! thank you so much!
---------- Post added at 10:42 PM ---------- Previous post was at 10:10 PM ----------
Just found a bug: the touch is upside down. i think it is due to the new marshmallow bootloader, because ashyx had the same problem with the twrp recovery
hellcat50 said:
omfg finally someone did it! thank you so much!
---------- Post added at 10:42 PM ---------- Previous post was at 10:10 PM ----------
Just found a bug: the touch is upside down. i think it is due to the new marshmallow bootloader, because ashyx had the same problem with the twrp recovery
Click to expand...
Click to collapse
Is it reversed in twrp/system/Both?
What twrp are you Using?
Made a clean Flash?
alias4ever said:
Umm not trying to sound like a jerk here but doesn't the title of the thread say it's for the Samsung Tab SM-T550?
---------- Post added at 18:02 ---------- Previous post was at 18:00 ----------
What about the Samsung Tab A 8.0 (SM-T350)? Will it work? Would love to flash it.
Click to expand...
Click to collapse
I'm so sorry! I meant if it is compatible with the version Tab A SM-P500 ?!?! Thank you!
pickmod said:
I'm so sorry! I meant if it is compatible with the version Tab A SM-P500 ?!?! Thank you!
Click to expand...
Click to collapse
I doubt it is compatible with P500 but it is worth a shot
Chemnitzer said:
Is it reversed in twrp/system/Both?
What twrp are you Using?
Made a clean Flash?
Click to expand...
Click to collapse
No, ashyx fixed it in the recovery. Before the fix the same was present in the twrp
I'm using twrp 3.0.2.1
hellcat50 said:
No, ashyx fixed it in the recovery. Before the fix the same was present in the twrp
I'm using twrp 3.0.2.1
Click to expand...
Click to collapse
Chemnitzer said:
Is it reversed in twrp/system/Both?
What twrp are you Using?
Made a clean Flash?
Click to expand...
Click to collapse
You are correct currently you need to have lollipop firmware installed we our actively working on the kernel to support the M firmware. I have also added a note in the install instructions about it.
deadman96385 said:
You are correct currently you need to have lollipop firmware installed we our actively working on the kernel to support the M firmware. I have also added a note in the install instructions about it.
Click to expand...
Click to collapse
Can I downgrade the firmware without bricking the device?
And what about the bootloader?
nevermind, downgraded and now the touch works. hopefully the other existing issues will be fixed soon
Just found another issue: the rotation doesn't work after sometime using the tablet. After a reboot it's working again until it stops working again.
For those that don't know what Evervolv is, Evervolv is an AOSP (Android Open Source Project) rom aimed at Snapdragon powered devices. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
If you would like to contribute to Evervolv, please visit our Gerrit Code Review.
Current version: Based off 6.0.1 Marshmallow)
Features:
Extended PowerMenu
Battery %,
Volume button music control.
Trackball Wake (Available on devices with a trackball/pad)
CM Theme manager
ability to turn all customization off with one switch in the toolbox, giving you 100% aosp look and feel.
eng builds (instead of userdebug like everyone else) providing more open experience (ie adb root by default)
full complement of commandline tools (busybox, vim, ssh, curl/wet with ssl support!)
custom updater written from scratch by Preludedrew and Texasice, featuring automatic update checks,
support for downloading gapps, and advanced automatic install (TWRP and CWM supported but TWRP preferred)
Bug Reporting:
Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use EVPaste to post your logs.
Downloads:
7-9 Build
Source:
Evervolv Github
Device Tree
Tab A common tree
MSM8916-common tree
Kernel Source
Changelog:
View the recent changes at Evervolv Gerrit
What's working:
Touchscreen
Power, Home, Recents, Back buttons
Wifi
Bluetooth
Sensors
GPS
Storage's (internal, external, adoptable storage)
Bugs/Not Working:
Mobile Data/Calling/Messagaing
Initial setup takes a while to initialize
Audio
Video/DRM
Camera
Offline charging
Playstore downloads old app versions
How to flash a Rom properly?
Make sure you are using Lollipop Firmware or your touch will be flipped we are activily working on supporting the Marshmallow firmware
Copy the rom and gapps to your tablet
Boot into your custom recovery
OPTIONAL make a backup of your current running rom and store it on your MicroSD-Card or on your PC/Laptop
Wipe dalvik cache
Wipe/format system
Wipe/format data
Flash rom
Flash gapps
Reboot and give your device some time to do it's first boot!
In case someone likes to compile on their own:
You need to setup Linux first, good tutorial here:
Ubuntu / Xubuntu:
- https://nathanpfry.com/how-to-prepar...-android-roms/
- https://nathanpfry.com/how-to-setup-...-android-roms/
- https://nathanpfry.com/how-to-set-up...-android-roms/
- https://nathanpfry.com/how-to-setup-...-android-roms/
Arch based Linux ready to go:
- BBQLinux by @codeworkx http://bbqlinux.org/
Once you have synced Evervolv source run the following in terminal:
Code:
mkdir -p .repo/local_manifests
nano .repo/local_manifests/local_manifest.xml
Add the following to your local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
-<manifest>
<project revision="mm-6.0" remote="github" path="vendor/samsung" name="Evervolv/android_vendor_samsung"/>
<project revision="mm-6.0" remote="github" path="hardware/samsung" name="Evervolv/android_hardware_samsung"/>
<project revision="mm-6.0" remote="github" path="kernel/samsung/msm8916" name="Evervolv/android_kernel_samsung_msm8916"/>
<project revision="mm-6.0" remote="github" path="device/samsung/qcom-common" name="Evervolv/android_device_samsung_qcom-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/msm8916-common" name="Evervolv/android_device_samsung_msm8916-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt5-common" name="Evervolv/android_device_samsung_gt5-common"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt510ltexx" name="Galaxy-Tab-A/android_device_samsung_gt510ltexx"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt510wifixx" name="Evervolv/android_device_samsung_gt510wifixx"/>
<project revision="mm-6.0" remote="github" path="device/samsung/gt58wifixx" name="Evervolv/android_device_samsung_gt58wifixx"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/audio-caf/msm8916" name="Evervolv/android_hardware_qcom_audio-caf"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/display-caf/msm8916" name="Evervolv/android_hardware_qcom_display-caf"/>
<project revision="mm-6.0-8916" remote="github" path="hardware/qcom/media-caf/msm8916" name="Evervolv/android_hardware_qcom_media-caf"/>
<project revision="mm-6.0-caf" remote="github" path="hardware/qcom/bt-caf" name="Evervolv/android_hardware_qcom_bt"/>
<project revision="mm-6.0-caf" remote="github" path="hardware/qcom/wlan-caf" name="Evervolv/android_hardware_qcom_wlan"/>
</manifest>
Save the file.
Back in terminal:
Code:
repo sync
. build/envsetup.sh
lunch gt510ltexx
make otapackage
Great Work for this!
Any plans for CM-13.0?
Chemnitzer said:
Great Work for this!
Any plans for CM-13.0?
Click to expand...
Click to collapse
Once the bugs are worked out i will work on cm-13.0
deadman96385 said:
Once the bugs are worked out i will work on cm-13.0
Click to expand...
Click to collapse
"Evervolv/android_device_samsung_gt510ltexx" is missing on github
Chemnitzer said:
"Evervolv/android_device_samsung_gt510ltexx" is missing on github
Click to expand...
Click to collapse
Fixed sorry about that its currently on my Galaxy Tab A org for now https://github.com/Galaxy-Tab-A/android_device_samsung_gt510ltexx
Auto standby is not working. In stock Rom, display goes of when LiD of cover is closed and goes back on when LiD is lifted.
Good job!
Thanks for this!:highfive:
Chemnitzer said:
Auto standby is not working. In stock Rom, display goes of when LiD of cover is closed and goes back on when LiD is lifted.
Click to expand...
Click to collapse
It is on the to-do list i will add a few potential fixes that might fix it, but i do not currently have a smart cover yet.
Hello! First I want to thank you for your work! I just installed the Rom, but not just opened, it stays hanging around with the sign Evervolv, screen saying that you are loading applications and then again Evervolv and so I get an hour without change. That may be, as I fix it? Thank you!
dodka said:
Hello! First I want to thank you for your work! I just installed the Rom, but not just opened, it stays hanging around with the sign Evervolv, screen saying that you are loading applications and then again Evervolv and so I get an hour without change. That may be, as I fix it? Thank you!
Click to expand...
Click to collapse
You made a clean flash?
Are you running latest twrp?
Sorry for Late reply
Chemnitzer said:
You made a clean flash?
Are you running latest twrp?
Sorry for Late reply
Click to expand...
Click to collapse
Yes, i made clean flash and i have instaled latest TWRP.
dodka said:
Yes, i made clean flash and i have instaled latest TWRP.
Click to expand...
Click to collapse
Which Version?
I use latest from ashyx and no issue like that
https://www.androidfilehost.com/?fid=24499762635999217
Also make an advanced wipe, not only factory reset
After wipe, you shouldt directly reboot into recovery and allow modifications.
Last, install Both ROM and Recovery WITHOUT Reboot
You surely own a sm-t555/ GT510LTE? (only to be sure)
I managed to install the Rom, but can not find the gapps. From where I have to download? Thank you!
dodka said:
I managed to install the Rom, but can not find the gapps. From where I have to download? Thank you!
Click to expand...
Click to collapse
http://opengapps.org/
You need arm version for android 6.0 in whatever variant you prefer.
Remember to install gapps together with rom BEFORE Reboot and First Boot of ROM
@deadman96385
Hows the progress on Rom?
Best let people work in peace, I'm sure they are progressing and will soon have another update of this interesting Rom.
I have managed to fork deadmans device tree to cm-13.0 for gt510lte.
If somebody is interrested in just pm me.
I will not start an own thread for this until it is proper booting.
Any support is welcome
any members interested in cm development may check my forum: http://forum.xda-developers.com/and...-t550-t555-t3449597/post68407172#post68407172
New members (those with few posts) are not permitted to post to development-related forums
Click to expand...
Click to collapse
Since I am not allowed to reply on the [UNOFFICIAL] [DEV] CyanogenMod 13.0 For LG G5 (H830 & H850) thread, it seems that I have to start a new thread here...
I have found a workaround to support the rear camera (imx234) on CM 13.
The required changes are on github, and pull requests to lg-devs have been issued:
msm camera: force power up/down settings for imx234/imx268 from h850 stock logs: https://github.com/ChristianFrisson/android_kernel_lge_msm8996/commits/cm-13.0-camera
g5: add libflash_pmic.so necessary for imx234/268 camera probing + restore stock camera xmlhttps://github.com/ChristianFrisson/proprietary_vendor_lge/commits/cm-13.0-camera
Snap: debug switching cameras beyond 2 (dual rear cameras) https://github.com/ChristianFrisson/android_packages_apps_Snap/commits/cm-13.0-dual-rear-camera
Here is how your local_manifest.xml should look like if you want to apply these changes on a cm-13.0 distribution:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="lg-devs/android_device_lge_h850" path="device/lge/h850" remote="github" revision="cm-13.0" />
<project name="ChristianFrisson/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-13.0-camera" />
<project name="lg-devs/android_device_lge_g5-common" path="device/lge/g5-common" remote="github" revision="cm-13.0" />
<project name="ChristianFrisson/android_kernel_lge_msm8996" path="kernel/lge/msm8996" remote="github" revision="cm-13.0-camera" />
<remove-project name="CyanogenMod/android_packages_apps_Snap"/>
<project name="ChristianFrisson/android_packages_apps_Snap" path="packages/apps/Snap" remote="github" revision="cm-13.0-dual-rear-camera" />
</manifest>
ChristianFrisson said:
Since I am not allowed to reply on the [UNOFFICIAL] [DEV] CyanogenMod 13.0 For LG G5 (H830 & H850) thread, it seems that I have to start a new thread here...
I have found a workaround to support the rear camera (imx234) on CM 13.
The required changes are on github, and pull requests to lg-devs have been issued:
msm camera: force power up/down settings for imx234/imx268 from h850 stock logs: https://github.com/ChristianFrisson/android_kernel_lge_msm8996/commits/cm-13.0-camera
g5: add libflash_pmic.so necessary for imx234/268 camera probing + restore stock camera xmlhttps://github.com/ChristianFrisson/proprietary_vendor_lge/commits/cm-13.0-camera
Snap: debug switching cameras beyond 2 (dual rear cameras) https://github.com/ChristianFrisson/android_packages_apps_Snap/commits/cm-13.0-dual-rear-camera
Here is how your local_manifest.xml should look like if you want to apply these changes on a cm-13.0 distribution:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="lg-devs/android_device_lge_h850" path="device/lge/h850" remote="github" revision="cm-13.0" />
<project name="ChristianFrisson/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-13.0-camera" />
<project name="lg-devs/android_device_lge_g5-common" path="device/lge/g5-common" remote="github" revision="cm-13.0" />
<project name="ChristianFrisson/android_kernel_lge_msm8996" path="kernel/lge/msm8996" remote="github" revision="cm-13.0-camera" />
<remove-project name="CyanogenMod/android_packages_apps_Snap"/>
<project name="ChristianFrisson/android_packages_apps_Snap" path="packages/apps/Snap" remote="github" revision="cm-13.0-dual-rear-camera" />
</manifest>
Click to expand...
Click to collapse
Beautiful! Great work. We'll test this over in the dev forums
Sent from my Pixel XL using Tapatalk
ChristianFrisson said:
Since I am not allowed to reply on the [UNOFFICIAL] [DEV] CyanogenMod 13.0 For LG G5 (H830 & H850) thread, it seems that I have to start a new thread here...
I have found a workaround to support the rear camera (imx234) on CM 13.
The required changes are on github, and pull requests to lg-devs have been issued:
msm camera: force power up/down settings for imx234/imx268 from h850 stock logs: https://github.com/ChristianFrisson/android_kernel_lge_msm8996/commits/cm-13.0-camera
g5: add libflash_pmic.so necessary for imx234/268 camera probing + restore stock camera xmlhttps://github.com/ChristianFrisson/proprietary_vendor_lge/commits/cm-13.0-camera
Snap: debug switching cameras beyond 2 (dual rear cameras) https://github.com/ChristianFrisson/android_packages_apps_Snap/commits/cm-13.0-dual-rear-camera
Here is how your local_manifest.xml should look like if you want to apply these changes on a cm-13.0 distribution:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="lg-devs/android_device_lge_h850" path="device/lge/h850" remote="github" revision="cm-13.0" />
<project name="ChristianFrisson/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-13.0-camera" />
<project name="lg-devs/android_device_lge_g5-common" path="device/lge/g5-common" remote="github" revision="cm-13.0" />
<project name="ChristianFrisson/android_kernel_lge_msm8996" path="kernel/lge/msm8996" remote="github" revision="cm-13.0-camera" />
<remove-project name="CyanogenMod/android_packages_apps_Snap"/>
<project name="ChristianFrisson/android_packages_apps_Snap" path="packages/apps/Snap" remote="github" revision="cm-13.0-dual-rear-camera" />
</manifest>
Click to expand...
Click to collapse
Great work!
ChristianFrisson!! Thank you very much. That was i missed!
You are awesome!
You can add the Snap changes to g5-common overlay i think
here: android_device_lge_g5-common/overlay/packages/apps/Snap
gesendet von meinem LG G5 H850 V10E
MetaIIica said:
You can add the Snap changes to g5-common overlay i think
here: android_device_lge_g5-common/overlay/packages/apps/Snap
gesendet von meinem LG G5 H850 V10E
Click to expand...
Click to collapse
Thanks for the suggestion. I'm trying to have the changes merged upstream, since these solve java.lang.ArrayIndexOutOfBoundsException that are thrown, what may happen with other devices with dual rear cameras.
for the officially Repo is this change important.
MetaIIica said:
for the officially Repo is this change important.
Click to expand...
Click to collapse
Rashed97 from lg-devs kindly opened a ticket on cyanogenmod code review (number 166128, I am not yet allowed to post links here...).
have seen. But i dont know why only cm 14 and not cm 13
and lg-devs stop support for cm13 too, no changes sience a long time. See only changes for cm14 -.-
please add all changes in cm 13 on lg-devs too... cm13 is not dead...
Thanks for the great work!
There are still some proprietary libraries reported to be missing by logcat. These may add more features to the cameras:
libmmcamera_llvd.so
libmmcamera_dcrf_lib.so
libmmcamera_chromaflash_lib.so
libmmcamera_optizoom_lib.so
libmmcamera_ubifocus_lib.so
libmmcamera_trueportrait_lib.so
libmmcamera_stillmore_lib.so
I could not trace these on autoprime's stock roms (10C or 10E). One reason might be I am mounting system.img on OSX with ext4fuse which provides non-native support.
There are as well other proprietary libraries reported to be missing by logcat, but not related to cameras I assume:
libwvm.so
libn2pm.so (found in stocks' lib/lib64)
qfp.wakeup.so
/system/lib/soundfx/libvolumelistener.so (found in stocks' lib/lib64, found listed in lg-devs/android_device_lge_g5-common – audio_effects.conf, should be built by android_hardware_qcom_audio it seems)
May somebody with a stock ROM installed or running linux check?
Ohhh, you're the one I need to hug for fixing the cam issue in CM13 for our G5? Well consider yourself hugged until you turn blue @ChristianFrisson :highfive:
I bought my G5 in early May and had just about given up on getting a fully working CM rom, you saved me and a ton of other G5 users.
THANK YOU :victory:
ChristianFrisson said:
There are still some proprietary libraries reported to be missing by logcat. These may add more features to the cameras:
libmmcamera_llvd.so
libmmcamera_dcrf_lib.so
libmmcamera_chromaflash_lib.so
libmmcamera_optizoom_lib.so
libmmcamera_ubifocus_lib.so
libmmcamera_trueportrait_lib.so
libmmcamera_stillmore_lib.so
I could not trace these on autoprime's stock roms (10C or 10E). One reason might be I am mounting system.img on OSX with ext4fuse which provides non-native support.
There are as well other proprietary libraries reported to be missing by logcat, but not related to cameras I assume:
libwvm.so
libn2pm.so (found in stocks' lib/lib64)
qfp.wakeup.so
/system/lib/soundfx/libvolumelistener.so (found in stocks' lib/lib64, found listed in lg-devs/android_device_lge_g5-common – audio_effects.conf, should be built by android_hardware_qcom_audio it seems)
May somebody with a stock ROM installed or running linux check?
Click to expand...
Click to collapse
I'm using 10d and only found the 2 libs you specified. (Though it is the base ROM for MIUI stone rom without the patch so probably also based on autoprime's)
I guess optizoom (optical zoom) and chroma flash (3 colored LEDs) wouldn't make too much sense on this phone anyway as our hardware doesn't support it.
lolmensch said:
I'm using 10d and only found the 2 libs you specified. (Though it is the base ROM for MIUI stone rom without the patch so probably also based on autoprime's)
I guess optizoom (optical zoom) and chroma flash (3 colored LEDs) wouldn't make too much sense on this phone anyway as our hardware doesn't support it.
Click to expand...
Click to collapse
Does the G5 not support chroma flash?
Sent from my Nexus 5X using Tapatalk
drsn0w said:
Does the G5 not support chroma flash?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
My bad. I thought it is the new take 3 different color LEDs to get a white flash but it actually is some kind of hdr where a picture with and without flash is merged. I guess our phone does support that even though it seems that this functionality wasn't built in the stock camera. At least I couldn't find it. Here a quick explanation of chroma flash: https://youtu.be/ZGfEQnhaBoo
ChristianFrisson said:
May somebody with a stock ROM installed or running linux check?
Click to expand...
Click to collapse
I've tried to find those so files in 10E ,and failed,but there are tons of other libmmcamera so files. Are you sure those files are really needed for the LG G5? Because it seems to me that they are specific for the camera app,so maybe using them from some other source could solve the missing issue?
Thanks for having checked lolmensch and onestyle007. These libraries might not be necessary, since the os boots and runs, but I guess that these may bring more features, or at least, unclutter the logs.
I have opened an issue on github: https://github.com/lg-devs/android_device_lge_g5-common/issues/9
Hey! I'm pretty new to Android development, but I've been flashing ROMs and rooting for a couple years now. How would I actually put this into action? I have a build of CM13 that wasn't made by lilrowrow, so the Snap.apk is still broken even without flashing gapps.