[ROM][5.1.1][OFFICIAL] CyanogenMod 12.1 for S3 Neo[LEGACY]
{
"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"
}
NOTE: PLEASE ALSO READ ALL OF THE FAQ IN THE SECOND POST. IT COVERS MANY OF THE COMMON PROBLEMS AND QUESTIONS!
CyanogenMod 12.1 is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lolipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Changelog:
https://www.cmxlog.com/12.1/s3ve3g/
Requirements:
Custom recovery (either TWRP or CyanogenMod)
Soon other things will be added
Known Bugs/Issues: (fixed nightly date)
NFC
If camera not working flash this: LINK
Offline charging(02.09.2016)
(Please don't ask ETA for any bug fixes)
Bug reports for this ROM should be officially submitted via CyanogenMod's Jira bug tracking sytstem. Please fully read the FAQ entry on bugs and bug submission before submitting any tickets.
FAQ, other information:
Soon
Download:
https://download.cyanogenmod.org/?device=s3ve3g
Note to users: I'm not responsible if you brick your phone. See the disclaimer above.
Note to admins/moderators: I'm not a developer / contributor of CyanogenMod and not associated with Cyanogen, Inc. in any way. If this thread is inappropriate, please move/delete it.
Thanks to These People:
Zola
@rox
Abhisek Devkota
Samsung Devs
CyanogenMod Devs
XDA:DevDB Information
Cyanogenmod12.1, ROM for the Samsung Galaxy S3 Neo
Contributors
n1kolaa, Zola III
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: No Longer Updated
Stable Release Date: 2016-08-22
Beta Release Date: 2015-10-19
Created 2015-09-23
Last Updated 2018-05-14
How to report problem with new kerel or rom?
tonyp said:
We're on a development site - at least in theory.
To help out development without actually having some knowledge it's really important to know how and when to get logs.
Lately more and more people in this section do grab appropriate logs, which is a good thing and has already helped in fixing a bunch of bugs.
To stop (especially new) people from constantly asking how to get logcats I decided to hand out a quick reference on how to grab logs efficiently via adb / terminal / app.
There is an app which can export apps (see the end of this post), but you should learn how to get logs via adb anyways, as a dmesg is often crucial in case of debugging bsods.
I won't post instructions in how to get adb working - you can use Google or take this CM wiki entry as a starting point.
The three most important log types are:
logcat: the logoutput of the Android system
radio logcat: the log outpur ot your System / BB / RIL communication
kernel log (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
Normal Logcat:
Code:
adb logcat -v time -d > logcat.log
Radio Logcat:
Code:
adb logcat -b radio -v time -d > logcat_radio.log
Note: Cyanogenmod (based) ROMs require the following setting to export kernel logs via adb:
Settings - Developer Options - Root access - choose: "Apps and ADB"
Kernel Log:
Code:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
For getting the logs via the Terminal Emulator app the commands differ a little:
Get logs via Terminal Emulator:
Normal Logcat:
Code:
logcat -v time -d > /sdcard/logcat.log
Radio Logcat:
Code:
logcat -b radio -v time -d > /sdcard/logcat_radio.log
Kernel Log:
Code:
su -c dmesg > /sdcard/dmesg.log
Last_kmsg:
Code:
su -c "cat /proc/last_kmsg" > /sdcard/last_kmsg.log
Notes:
-v time will include timestamps in the logcats
-d will export the complete log.
If you want to save a continuous log you can remove the -d parameter - then you need to cancel the logging process via CTRL+C.
To export a continuous kernel log use adb shell su -c "cat /proc/kmsg" > dmesg.log (and cancel it via CTRL+C again).
Exporting logs with an app:
I used to recommend Lumberjack for grabbing logs, but it doesn't work with Jellybean properly anymore and fails to export the dmesg.
I googled for a while and found a great (and fully open sourced) alternative to export logs: SysLog
With this great app there are no more excuses - at least open the app, export all 4 log types and attach the zip file from /sdcard/SysLog to your bug report.
Before anyone asks (duh!), Kernel log = dmesg, Last kernel log= last_kmsg, main log = logcat, modem log = radio log.
Lumberjack still is great to have a look at logs on the phone, but for exporting you probably should use SysLog as it does it quickly and reliable
SysLog (source):
Click to expand...
Click to collapse
#o#
tonyp said:
When to post which kind of logs:
If you got any kind of ROM problems - especially problems with Apps like force closes, attach a logcat.
If there are problems while calling or with your signal attach a radio logcat to the normal logcat.
In kernel threads or on issues which might be kernel related (from A as auto brightness to Z as ZRAM) you need a kernel log
If you had a sudden reboot attach a last_kmsg, then we can check if it's been kernel related
As our phone has always been on the edge of bsod's and freezes, some special notes about them as well:
If you had a bsod and/or freeze a logcat dmesg after rebooting is useless, as it doesn't show anything from before the reboot
There are two things you can do:
While the phone's screen is black connect the cable to your computer and check if the device is accessable via adb (check e.g. with "adb devices").
If it is export the dmesg like explained above. If not go on to step 2:
Note that two of the bsod problems of the ICS/CM kernel have been fixed by pengus by the logs I managed to get while the phone has been in a bsod - which means this is crucial!
Pull the battery and insert it again as quickly as possible. Why? The phone does hold a so called last_kmsg in RAM.
It's non-permanent memory, which means it doesn't survive a loss of power - sometimes we're in luck by a quick pull though.
If we're not in luck the file will be empty or contain scrambled characters.
Last but not least some general remarks:
If you don't provide useful logs we can not help you in 95% of the cases in case we can't reproduce it.
Buf even if we could reproduce it - let's assume one of YOUR apps is force closing. Why should we install the app to reproduce the problem and get the logs ourselves.
YOU want help, so YOU should provide the log.
Every real dev with some coding knowledge will need logs to fix the bugs.
This site is called xda-developers - which means that the initial intention of this forum is the actual development itself - and not "making your phone cool".
The least you can (and must) do is to provide useful help with a clear problem description and attached logs when you run into some issues
Click to expand...
Click to collapse
Donations for s3 dual sim
Use "Send payment" option on paypal
@Ahmad Tawfik: 1,62 USD; 1,18 USD
@S3-Neo 5 USD
@naik2902 6.00 USD
@aelfinn 5.51 USD
@St.Ungulant 5.49 USD
Ulrich 10.99 USD!
@Droidaner 13.49 US
I need about 50 euros for used dual sim phone
FAQ POST
Q: When you will realse CM13.0?
A: DON'T ASK FOR ETA(ETA = Estimated Time of Arrival)
Reserved #2
Is offline charge working with this kernel?
Edit:
sorry but I did not read the 1st post
Everything is fine
Installed and booted without issue. Kernel seems to be changed. :good: :highfive:
Is that working on Resurection Remix 5.5.6 ?
Removed
Ahmad Tawfik said:
Offline charge isn't working for me
Click to expand...
Click to collapse
Read OP...
" ##Bugs:##
no bugs so far(offline charging like cm12.1) "
Btw thanks n1kolaa!
Zokhii said:
Read OP...
" ##Bugs:##
no bugs so far(offline charging like cm12.1) "
Btw thanks n1kolaa!
Click to expand...
Click to collapse
I hope you like it
Np It will be assome to rate it 5 starts and make review.
ahmo67 said:
Is that working on Resurection Remix 5.5.6 ?
Click to expand...
Click to collapse
if its based on cm12.1 it shoud.
Take a backup if you not shure.
Mediafire folder is empty for me
jad88 said:
Mediafire folder is empty for me
Click to expand...
Click to collapse
https://www.mediafire.com/folder/3c3y68hehuv9t/n1kernel
MediaFire links not working...
n1kolaa said:
https://www.mediafire.com/folder/3c3y68hehuv9t/n1kernel
Click to expand...
Click to collapse
It's the same... Maybe it's my browser
Is this kernel base on Rox kernel?
And can you add this future for color calibration --> http://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
We need this futures.
---------- Post added at 01:48 PM ---------- Previous post was at 01:34 PM ----------
jad88 said:
It's the same... Maybe it's my browser
Click to expand...
Click to collapse
Download one buy one !
Sectorian said:
Is this kernel base on Rox kernel?
And can you add this future for color calibration --> http://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
We need this futures.
---------- Post added at 01:48 PM ---------- Previous post was at 01:34 PM ----------
Download one buy one !
Click to expand...
Click to collapse
I wont add it. Its based on Rox kernel
I had to login to my mediafire account. It works on latest RR. (Flashed with flashify)
Sorry, one question. If i flash your kernel, did i lose my data?
Related
| CyanogenMod 10.2 - Android 4.3.1 - Jellybean |
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include
/*
* Your warranty is now likely void.
*
* I am not responsible for bricked devices, dead SD cards,
* spontaneous combustion, or any other host of cosmic penalties
* which may befall you, your family, or your phone.
*
*/
If you ask any questions that are answered in the first two posts your question will be ignored. If you don't search prior to posting you will be ignored. If you don't read you will be ignored. If you've done all that and still don't have an answer then feel free to ask your question. Ambiguity doesn't help anymore. Elaborate. It's that simple.
Click to expand...
Click to collapse
Built from CM source
Service
Text
Call
Audio
WiFi
Google Now
Bluetooth
GPS
MMS
Video playback
Audio playback
Camera
Camcorder
UMS
You tell me
Do NOT use superwipes
Wipe everything except sdcards
** (if you are simply applying an update to this rom base this might not always be required)
*** ((but do not report bugs if you didn't full wipe))
Flash ROM
Flash GAPPS
Reboot
???
Profit
To enable Developer Options and Performance go to Settings, About Phone and repeatedly press Build Number.
If you use ADB read this: PSA by CM
If you use reboot to recovery read this: PSA by CM
Regarding new Superuser: PSA by CM
android1234567 for figuring out initial boot. if it wasnt for his stubberness we probably still would be rebooting to recovery
Evervolv for their wonderful kernel which my kernel is 98% based on
elginsk8r for his work on the glacier device tree and kernel. These repos were the base of my build
And any and all users in this thread who contirbuted or will contribute to making this ROM as stable as possible
NineInchNails for being an awesome dev partner, moral support and friend!
dastin1015 for being an awesome dev partner and friend!
android1234567 for being an awesome dev partner and friend!
android1234567 for all the help with the kernel, without you we wouldn't have new kernel
A bunch of thanks to arco, for all his updates to our kernel, our display libs, our media libs, and for fixing the video playback glitching, and for being a good friend and dev mentor.
All my supporters!
I really didn't want to do this but people keep asking so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means
Note: The name on the paypal account may say patricia, this is because it's a family paypal account.
Thanks and happy flashing!
Download link is in 2nd post
Oct-11
* Fixed Torch not staying on when screen off
* Lots of camera fixes
* Fixed mic with some VoIP apps (Tango, Viber
* ramdisk init script cleanup (evervolv)
* A whole bunch of kernel updates including headset and display code re-writen (Evervolv)
* Kernel updated to Linux 3.0.99
* Build tagged 4.3.1_r1
* A lot of other updates I'm probably forgettting, plus all upstream changes
Sep-17
* Fixed SD card mount
* Fixed brightness/sensors
* Added CMAccount
* Upstream: Android tagged "Android 4.3_r3"
* Any upstream changes at time of compile
* Note; sorry for the delay
Sep-6
* Fixed front facing camera
* General cleanup
* Any upstream changes at time of compile
Aug-24
* Fixed Torch FC
* Attempt to fix data drops for some people
* Any upstream changes at time of compile
Aug-22
* Fixed front facing camera
* Any upstream changes at time of compile
Aug-19
* Fixed mounting SDcard over USB
* No longer using prebuilt audio libs from 10.1
* Couple overlooks to the media libs compiling (weren't grabbing correct headers)
* Bugfix: Root access will now be enabled by default without having to do the "trick"
* Any upstream changes at time of compile
** Note: please use the updated gapps (8/13) linked below or you will most likely have issues
Aug-13
* Initial release everything seems to be working well
ChronicKernel
Kernel now based on Evervolv's kernel with a few changes by me, including:
* Compiled with linaro
* Removed/Disabled KSM
* Removed ZRAM
* Optimized and compiled with with the "Optimize a lot, or -o3 option)
* Added more I/O schedulers
* Tweaked voltages a bit
* PMEM memory mapping tweak to remedy soft-reboots with AOSP 4.2/4.3/CM-10.1/10.2
These settings were changed by me to help make the kernel more stable with our ROM, observed with tests by me. if you want to use another kernel please feel free. but support will not be provided unless you are running the kernel included with the ROM
Other Features of the kernel include:
* OC to 1900Mhtz (default 1024Mhtz, Recomended: 1200Mhtz)
* Undervolted
* Added CPU Governors: Smartassv2, lazy, lagfree, interactiveX
* User-configurable CPU OC
* User-configurable CPU default governor (ondemand = default)
* User-configurable I/O scheduler (default = DEADLINE)
Team Hydra Github (main): https://github.com/Team-Hydra
CyanogenMod Github: https://github.com/CyanogenMod
ROM : cm-10.2-20131011-Albinoman887-glacier.zip
GAPPS: : HERE or HERE (Mirror)
Goo.im Repo : CLICK HERE
* This ROM can also be downloaded directly with GooManager *
first create the folder structure for your source. I suggest creating android/system n your home directory.
Now cd into this directory enter this command
Code:
repo init -u git://github.com/Team-Hydra/android.git -b cm-10.2
repo sync
( if you have a pretty decent /internet connection (10-20mbps+) you can add -j and then a number ater repo sync i recomend something like repo sync -j10 )
Once you have done that your ready to go. simply run:
Code:
. build/envsetup.sh
./vendor/cm/get-prebuilts
lunch cm_glacier-userdebug
mka bacon
make sure before you start a new build to always run make clobber
If anyone would like to help bug bash with me feel free. if you make any progress send me a pull request
P.S. I HIGHLY recomend setting up ccache if you are going to compile a lot you can read more about ccache here: Initializing a Build Environment and scroll down to the "set up ccache" section
Happy Developing,
Albinoman887
1st
First!
Lol yes! 4.3 let the porting begin! thanks so much for this man.
Sent from my HTC Glacier using xda app-developers app
oouuu yeaah nice work man:good:
bug: everytime I reboot my notification light is on and says my battery its charging - I just plug in and unplug from charger and its ok...just want to report, no big deal
update: I have this bug still even I flash other rom, maybe its hardware problem...sry if I am wrong but never encountered this problem until now
Thank you!
Thank you for taking the time and effort to build cm 10.2! I've spent a few minutes poking around, and discovered that su doesn't function for me. TB tells me that /system/bin/su fails, terminal shows it doesn't work but no error message is produced. Logcat says:
Code:
D/su ( 4659): starting daemon client 10041 10041
E/su ( 4660): connect failed with 2: No such file or directory
I also am with the same issue. I've flashed superuser and it didn't stick
Sent from my myTouch 4G using xda premium
Try flashing Koush's experimental 4.3 root
Sent from my HTC Glacier using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:32 PM ----------
I'd like to say that with this release of 4.3, everyone should really try and help out with the headset issue.
Older kernels won't work anymore so you cannot flash .62 or .64s anymore, meaning we are all stuck with the issue unless we all try fixing it.
I dont know much but I will say that we should try and get dmesg and last_Procs (or whatever it is) as we can.
I'm not saying it wasnt important before, but now we are really left with the issue. The devs have tried a lot and now the users gotta help even more.
I think Elgin tells you the commands in his evervolv thread. Hopefully we can all fix this issue
Sent from my HTC Glacier using xda app-developers app
jggimi said:
Thank you for taking the time and effort to build cm 10.2! I've spent a few minutes poking around, and discovered that su doesn't function for me. TB tells me that /system/bin/su fails, terminal shows it doesn't work but no error message is produced. Logcat says:
Code:
D/su ( 4659): starting daemon client 10041 10041
E/su ( 4660): connect failed with 2: No such file or directory
Click to expand...
Click to collapse
Hi Albionman,
I tried few different superusers, even the new experimental 4.3 but no luck.
also couldnt see "users" the new feature in 4.3
batterywise & performance wise its silky smooth so far...thank you for this
JukiCro said:
oouuu yeaah nice work man:good:
bug: everytime I reboot my notification light is on and says my battery its charging - I just plug in and unplug from charger and its ok...just want to report, no big deal
Click to expand...
Click to collapse
I don't have this issue just camera didn't work until reboot. Also camera jb+ fixes the green line but flash is better timed in the stock camera. So far very nice rom. Thanks
Sent from my GT-P3113 using xda premium
not as stable as the 4.2 rom unfortunately
USB Mass Storage doesn't work for me AT ALL. Tells me I can safely remove the SD card when I try to turn it on. I did a full wipe and everything too...
got an "error retrieving information from server" when I try downloading from the play store
and camera force closes
Just got one random reboot too. Guess I'll be reverting back to 4.2 for now :'(
jggimi said:
Thank you for taking the time and effort to build cm 10.2! I've spent a few minutes poking around, and discovered that su doesn't function for me. TB tells me that /system/bin/su fails, terminal shows it doesn't work but no error message is produced. Logcat says:
Code:
D/su ( 4659): starting daemon client 10041 10041
E/su ( 4660): connect failed with 2: No such file or directory
Click to expand...
Click to collapse
usb mas storage works. i just tested it.... unless i forgot to apply the fix to your build or something
and the SU isssue. i need to put this in the OP its a bug with 10.2. enable developer options by going to about phone and tapping build number repeatedly. then go to developer options and switch root access to apps and adb and back to apps. then it will work
OK i updated the op with the superuser trick. its in bold towrds the bottom of the first post. please point any questions to that. thanks
SU Works
Thank you for showing us the SU trick, works like a charm. However, the USB storage issue is present. It first says safe to remove then resets, after a second attempt the process initiates and goes nowhere.
Doogitronix said:
Thank you for showing us the SU trick, works like a charm. However, the USB storage issue is present. It first says safe to remove then resets, after a second attempt the process initiates and goes nowhere.
Click to expand...
Click to collapse
You are right SU working and USB storage have issue also when open gallery phone goes to reboot and FFC unfortunately gallery crashed.
Sent from my myTouch 4G using xda app-developers app
Doogitronix said:
Thank you for showing us the SU trick, works like a charm. However, the USB storage issue is present. It first says safe to remove then resets, after a second attempt the process initiates and goes nowhere.
Click to expand...
Click to collapse
hview said:
You are right SU working and USB storage have issue also when open gallery phone goes to reboot and FFC unfortunately gallery crashed.
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Logcats would help a lot from these errors. Get a logcat app from the store, run it and try to do the things that are going wrong for you. Get last-ksmg if you are having reboots. Use paste bin to post your results. Look up cnote74's paceman he has link to instructions on how to log errors. The more info you can give the devs, from different phones would help them a lot.
Sent from my HTC myTouch 4g using xda app-developers app
camera is fine for me,
have screen flickering more often then before,
SU problem, yeah I had bug when I run titanium backup but I went to settings - superuser - closed it, and its fine
and about USB storage...I just pull out my sd card and stick it in computer, becouse since I flashed my first jb 4.2.2 I have that bug with every rom and it sucks, but I can live without it
anyway great job keep it up:good:
GronHog said:
Logcats would help a lot from these errors. Get a logcat app from the store, run it and try to do the things that are going wrong for you. Get last-ksmg if you are having reboots. Use paste bin to post your results. Look up cnote74's paceman he has link to instructions on how to log errors. The more info you can give the devs, from different phones would help them a lot.
Sent from my HTC myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
Logcat app: http://forum.xda-developers.com/showthread.php?t=1123129
Enjoy!
logcat for camera issues
This is a logcat for my camera issue
Not sure if I've done it right
[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project
CyanogenMod is a free, community built distribution of Android 5.1 which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
XDA:DevDB Information
[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project, ROM for the Sony Xperia Z3
Contributors
jerpelea
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-12-02
Last Updated 2015-04-13
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
ENJOY AN UNOFFICIAL CM RELEASE BROUGHT TO YOU BY FreeXperia Team
PLEASE DONT MIRROR OUR ROMS
Homepage
www.freexperiaproject.net
thanks to all who made this possible supporting us
contributing with code, donations or even trusting us
thanks to SONY that made all this possible !
jerpelea said:
thanks to all who made this possible supporting us
contributing with code, donations or even trusting us
thanks to SONY that made all this possible !
Click to expand...
Click to collapse
Repo link? download link? Whats working?
Thread cleaned.
Lets try and keep this one on the right tracks.
Bug reports with LOGCATS are OK, off topic chatting is not!
???Where is the rom
Where is the rom ?? is everything working?
adidouh113 said:
Where is the rom ?? is everything working?
Click to expand...
Click to collapse
http://fxpblog.co/cyanogenmod/cyanogenmod-12/
The build for Z3 isn't listed yet though, I hope OP will add it soon
we have enabled daily builds
if your device is not yet in the list will appear soon (1 day,1 week, 1 month) no ETA please
but you have to remember that is an early alpha build
Please do not ask for what is working or not
It is an early Alpha build. If you do not know what that is then DO NOT FLASH IT.
The point of this is for you to flash it, test what is working or not and provide feedback WITH LOGCATS so others can try and fix it.
Thread cleaned (Again)
Thread closed until there is a build available
Thread cleaned
@jerpelea, please PM a mod or report this post to get the thread re-opened immediately.
Thread opened, build is now available
WiFi is working. But systemui crashes as soon as you lock the phone. After a restart it crashes instantly. Looking forward to the next build.
---------- Post added at 01:42 AM ---------- Previous post was at 01:39 AM ----------
nimrodity said:
sorry but care to give any more info on what works and what doesn´t. Also where is the link, I am to dumb to find it
Click to expand...
Click to collapse
Link is http://fxpblog.co/cyanogenmod/cyanogenmod-12/
SystemUI - crashes can be fixed by adb pushing SystemUI from AOSP lollipop. All crashes now gone (including screen off). I'd suggest only those who know their way around adb try this (you need to r/w mount through adb shell) - here's the replacement SystemUI apk (it's from my latest 5.0.1 r2 build hehe) https://drive.google.com/open?id=0B0uD0ZLDjONjRW0xWS12MGF4OWc&authuser=0
Wifi - all good, nice to be able to access google drive, mail, play store etc
Camera - installed google camera - fc's as expected
SU permissions all good
Modem - cellular connected after pushing modem files and ril libs
Pleasantly surprised by first build - will test more stuff and report back..
{
"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"
}
iBuzman said:
SystemUI - crashes can be fixed by adb pushing SystemUI from AOSP lollipop. All crashes now gone (including screen off). I'd suggest only those who know their way around adb try this (you need to r/w mount through adb shell) - here's the replacement SystemUI apk (it's from my latest 5.0.1 r2 build hehe) https://drive.google.com/open?id=0B0uD0ZLDjONjRW0xWS12MGF4OWc&authuser=0
Wifi - all good, nice to be able to access google drive, mail, play store etc
Camera - installed google camera - fc's as expected
SU permissions all good
Modem - cellular connected after pushing modem files and ril libs
Click to expand...
Click to collapse
Did you need to manually push modem files and ril libs? Or are they in the build from the fxpblog.co site ?
^^ manually, I had them on hand (my 4.4.4 kitkat files) after grabbing them when trying to get lollipop aosp working.
iBuzman said:
^^ manually, I had them on hand (my 4.4.4 kitkat files) after grabbing them when trying to get lollipop aosp working.
Click to expand...
Click to collapse
Is that possible for you to share those files? I'd really like to use the build if modem is working Thanks!
^^ I'm away from pc for rest of night.
modem:
mba.b00 & mba.mbt plus all modem.b00 thru modem.b25 & modem.mbt ~ all from stock kitkat. abd push into /etc/firmware/
ril libs:
libril.so and librilutils.so from stock kitkit. adb push into /system/lib/
cant remember if I remembered (if that makes sense..) to abd push rild into system/bin hehe ~ I think I forgot to do it but worked anyway
you should be able to get away with doing in root explorer instead of stuffing around with adb pushing. you have r/w mount system via root adb root shell first (took me ages to get permissions to push system files.. plus what I do is very hit and miss.. n00b hacking away blindly lol).
---------- Post added at 07:46 PM ---------- Previous post was at 06:53 PM ----------
of course a flashable zip with systemui, modem and ril patches would be best - I'll see if I can learn how to make one (seeing we'll probably need it for a while yet).
probably try to put all the patches into the gapps flashable I think (why reinvent the wheel and I have to flash it already anyway)
thread cleaned again.
The build is in the download section for cm12 on the link given by the op.
Do not ask what us working, flash it and provide the feedback via a logcat. This is an alpha rom.
Do not flash it if you do not want to test it.
mobile seems to be somewhat working... goes in and out on me. was the file modem/mba dot MBT or MDT ?
mms - seemed to receive a few , but couldn't reply
calls - received one but it dropped. when i tried to call out i received an error with phone.ui (or similar)
iBuzman said:
^^ I'm away from pc for rest of night.
modem:
mba.b00 & mba.mbt plus all modem.b00 thru modem.b25 & modem.mbt ~ all from stock kitkat. abd push into /etc/firmware/
ril libs:
libril.so and librilutils.so from stock kitkit. adb push into /system/lib/
cant remember if I remembered (if that makes sense..) to abd push rild into system/bin hehe ~ I think I forgot to do it but worked anyway
you should be able to get away with doing in root explorer instead of stuffing around with adb pushing. you have r/w mount system via root adb root shell first (took me ages to get permissions to push system files.. plus what I do is very hit and miss.. n00b hacking away blindly lol).
---------- Post added at 07:46 PM ---------- Previous post was at 06:53 PM ----------
of course a flashable zip with systemui, modem and ril patches would be best - I'll see if I can learn how to make one (seeing we'll probably need it for a while yet).
probably try to put all the patches into the gapps flashable I think (why reinvent the wheel and I have to flash it already anyway)
Click to expand...
Click to collapse
if you have the zip ill be happy to test the rom and the zip. Needing my Phone "on the road" so without calls and mobile-data i cant test the rom
{
"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"
}
Brought to you by @nailyk!
Notice: Thread missing information/ credits/ mentions/ stuff etc etc. Work in progress.
All credit for this ROM must go to Nailyk as the main developer of Omni for Leo devices. I am just a tester / thread maintainer for Leo (Z3).
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Who can use it?:
This ROM is only for Xperia Z3 users with UNLOCKED and (preferably) UPGRADED bootloaders!
How to install:
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash this TWRP (version 3.1.x)
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen / wait for purple LED on boot and press volume up key
% Wipe system, cache and data
Install rom zip (+ % gapps if you need it)
Reboot
(After first boot if you have initial issues try a second reboot and see if it stops. If not, clean install)
Rolling back to stock:
- Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
TWRP:
See Nailyk's TWRP build here for best compatibility (based on Omni sources):
TWRP 3.1.x-x
GAPPS:
Flash any 7.1.2 compatible Gapps package. I suggest OpenGapps.
Alternatively Microg and fdroid will serve you well as an alternative to Google Play Services.
Releases:
Latest:
2017-12-13: Android File Host Download
Mirror: releases.nailyk.fr/omnirom
Change Log: CVE Patches
TWRP 2017-11-21: Android File Host Download
Previous:
2017-12-02: Android File Host Download
Change Log: Fixed scripts for modem files at first boot. No issues with SIM detection, manual script running etc now.
2017-11-21: Android File Host Download
Change Log: Updated Security Patches to latest. No change to ROM.
2017-10-17: Android File Host Download
Change Log:
Code:
Lot of important changes here,
- Device was renamed z3 instead of leo,
- This release ""should"" support all leo variants. However, the script is on early stages: expect troubles.
In case of problem with RIL process the following:
Reboot into recovery,
connect to shell then:
Code:
mount /system
ln -s /system/vendor/etc /vendor/etc
sh /system/etc/init.blobs.sh
This build is patched against wpasupplicant attack (krackattack)
Some improvements about external sdcard & charging.
2017-09-28: Android File Host Download
MD5 Sum: b431c2c720be4a4dfd365a8343ca8115462a3393
Root etc:
For root it is suggested that you see phhSuperUser here: phhSuperUser Thread
Flash options such as Magisk or SuperSU if you wish, but there is not guarantee of support. Magisk 14.0 was tested by myself and working at first release.
Contributors:
@nailyk,
@xkeita, @tomascus, @derf elot, @TheavenginTitan
@tomgus1, @gr8st, @mcgi5sr2, @doriandiaconu, @Robot76, @panzerox123
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information:
Status: Beta
Logs:
This post will describe how to take logs.
If you are using the ROM and want to make development faster/ easier please simply take a log and post it here in the thread for us to check out.
Take logs when you notice bugs etc and try to reproduce them when taking the log and give us some description of the problem.
First you will need ADB:
Set up any adb environment on you PC (showing windows here for eg.- Linux/ Mac differs):
- For windows a minimal installation will be enough to take logs and takes 15 seconds.
15 second ADB Installer
Then open the folder it is installed to so you see "adb.exe" (obviously different on Linux/Mac).
Open and CMD window in the folder with adb and you can connect your phone.
Enable USB Debugging on the phone!:
Go to Settings - About Phone - Build Number (tap this until Developer options unlocks)
Go to Developer Options and enable "USB Debugging".
Now take the actual logs running adb logcat:
- Back to the PC CMD window.
- When you run the command a window will pop up on the phone asking for access. Say yes.
- Run the command - " adb logcat > logcat.txt "
- This will give you a text file with the log to post to us.
If possible take a dmseg /kmsg:
This is most useful for bootloops etc
You may need root on the device to access these:
- " adb shell su -c dmesg > dmesg.log "
- " adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log "
Screenshots
Screenshots thanks to @Tux111. Find some of his comments and hit thanks for him!
Full showcase of screenshots here: MEGA
What working?
@Dobsgw When you will update missing informations, could you please share informations about changelogs, what works, whats not, special features and some screenshots?
All the users (me too) will appreciate a lot.
I'm gonna get the info on the changes and features etc at some point later this week.
For now all I know is the build is beta but working very well. You all know Nailyk has a very high standard of work.
The current version I have installed is working as normal and since this morning (when I installed) I've seen no issues.
If you have some time it's worth checking out.
For features etc see the Omni ROM website
Dobsgw said:
I'm gonna get the info on the changes and features etc at some point later this week.
For now all I know is the build is beta but working very well. You all know Nailyk has a very high standard of work.
The current version I have installed is working as normal and since this morning (when I installed) I've seen no issues.
If you have some time it's worth checking out.
For features etc see the Omni ROM website
Click to expand...
Click to collapse
Mobile Data don't work. Every time i try to set APN, it automatically disappear. No way to make SIM data work.
The rest of the ROM is kinda awesome, some little bugs but really nicely done. Ah, message app miss. Add it please.
You probably know already but there is no link to TWRP 3.1.x for Z3 and Z3 dual (can be found in xkeita thread of Lineage 14)
Tux111 said:
Mobile Data don't work. Every time i try to set APN, it automatically disappear. No way to make SIM data work.
The rest of the ROM is kinda awesome, some little bugs but really nicely done. Ah, message app miss. Add it please.
Click to expand...
Click to collapse
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
tiliarou said:
You probably know already but there is no link to TWRP 3.1.x for Z3 and Z3 dual (can be found in xkeita thread of Lineage 14)
Click to expand...
Click to collapse
Xkeita TWRP is fine.
Nailyk also has a brilliant TWRP version found here in the forum.
It is updated to latest just ignore the title. 3.1.1-3
nailyk said:
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
Click to expand...
Click to collapse
D6603 single SIM.
Can't provide right now, sorry.
EDIT: I'll provide it soon as possible!
How i have to make radio log?
nailyk said:
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
Click to expand...
Click to collapse
I figured out mobile data work. But there is a bug, inside APN configuration, that automatically delete the APN created if you modify a string inside and after save it.
This time i simply used default APN settings, without modifying anything a part APN "Name" and "APN" and it works.
Here there is the logcat of the bug (over 1 mb can't upload here).
https://mega.nz/#!YAUXUSaA!3w6IWURIGvsHU-Cm9IkFStOsmyj67Sxvt9tbqqD2mG8
Tux111 said:
I figured out mobile data work. But there is a bug, inside APN configuration, that automatically delete the APN created if you modify a string inside and after save it.
This time i simply used default APN settings, without modifying anything a part APN "Name" and "APN" and it works.
Here there is the logcat of the bug (over 1 mb can't uploader here).
https://mega.nz/#!YAUXUSaA!3w6IWURIGvsHU-Cm9IkFStOsmyj67Sxvt9tbqqD2mG8
Click to expand...
Click to collapse
Thank you for taking the time to look into this.
Hopefully not a big issue
Mobile data D6603 german working LTE
Sent from my unknown using XDA-Developers Legacy app
edit
New twrp works fine and omnirom build too! Thx for hard work! ? Greets from German
Sent from my unknown using XDA-Developers Legacy app
App not using SD card photo ecc
Inviato dal mio unknown utilizzando Tapatalk
my BL is unable to get unlocked. but im now on .291 rom and rooted and twrp installed. is there nothing i can do to taste the full working nougat?
what will happen if i flash it onto my device (in this case, the BL is still locked. bootloader unlock allowed : no )
thanks.
leo31 said:
my BL is unable to get unlocked. but im now on .291 rom and rooted and twrp installed. is there nothing i can do to taste the full working nougat?
what will happen if i flash it onto my device (in this case, the BL is still locked. bootloader unlock allowed : no )
thanks.
Click to expand...
Click to collapse
You will have a brick.
Nothing you can do when unlock allowed:no.
The only thing is to contact sony, it is illegal (in some countries) to have an unlockable bootloader.
The images and most of the files do not use the sd card and when you want to pass applications to the system it does not allow attachment screenshot.
You could also add the option to expand the desktop and resize the navigation bar.
{
"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 is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), 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.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Working
Boot
Mobile data
Cam (pics only)
flashlight
fingerprint
sdcard is recognized/mounted
Unknown/Untested
GPS
NFC
calls/sms (should work i guess, because data works)
audio (cant test that in class )
Issues
USB
Wifi
Bluetooth
Recording
Brightness change
Everything i forgot probably
As you can see on the "Working" list, this is a highly experimental build, flash at your own risk, and don't come crying to me if it should brick anything (it didn't for me, but seeing from the TWRP Thread the V30 can be picky).
Dont forget to make a backup!!!
If you want to report any bugs, NEVER do it without providing logs. I can't try to fix things without logs.
Helpful log commands:
logcat (usage: e.g. logcat > /sdcard/logcat.txt )
dumpsys (usage: e.g. dumpsys SurfaceFlinger > /sdcard/dump_sf.txt)
dmesg (usage: e.g. dmesg > /sdcard/dmesg.txt , might need root)
for more examples on how to use the commands, either google (do that first) or ask (only do this if you already googled how to use those commands).
FAQ
USB isn't working. How do I get logs?
In the ramdisk theres a nice little script which will print the logcat to /data/ramoops/cm14.1_<number>_logcat_<date/time>.txt
The logcat is many many hundreds of MB in size, why?
Its currently spammed with something like this:
Code:
E/QMI_FW ( 674): xport_reg Failed for service_id=0x35 version=0x1001 on 15
Replace
Code:
[0-9][0-9]-[0-9][0-9] [0-9][0-9]:[0-9][0-9]:[0-9][0-9].[0-9][0-9][0-9] E/QMI_FW ( [0-9][0-9][0-9]): xport_reg Failed for service_id=0x35 version=0x1001 on [0-9]*[0-9]
in the log with your favorite editor which can use regex with nothing (or delete all those lines if you have that option)
Is there another way to get some logs?
In Developer Options, turn on "Local Terminal", and get a logcat or other logs with that.
The screen glitches, is there a way to fix this?
I hope so, working on this too.
After restoring my backup with TWRP, my phone won't recognize my PIN (not SIM PIN). What todo now?
Just follow the guide on here. Afterwards you have to setup your PIN again (also Fingerprints, and enable Trusted Agents in Settings -> Fingerprints & Security)
Download
Version 0.0.2: https://www.androidfilehost.com/?fid=962187416754470110
Version 0.0.1: https://www.androidfilehost.com/?fid=818070582850487924
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the LG V30
Contributors
SGCMarkus
Source Code: https://github.com/SGCMarkus
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2018-01-25
Last Updated 2018-01-25
Changelog
v 0.0.1 Initial build
it boots
v 0.0.2
Mobile data works
Cam works (pictures only)
fixed graphics glitches
Fingerprint works
flashlight works
SDCard is recognized
If you are interested to contribute/help out/test, hit me up in PM, or join my Discord Server: https://discord.gg/DJRnTRC
I set it up to be a general server for all kinds of LG V30 things, but also for Developers to meet and talk to each other, and help each other out.
Downloading...
I'll try to flash it. I'm new on LG devices (come from Samsung...)
It BOOTS
Mike.YT said:
It BOOTS
Click to expand...
Click to collapse
I agree... FC everywhere
But I hope it's a first step...
Exam time here though, so i couldnt really work on this more :/
But i have hope now for actual Treble support (we have a partition called OP, idk how important the stuff in there is though, 344MB if im not wrong, gathered all the Oreo blobs from the V300S kdz (i hope i have all needed ones), and those take up 324MB xD)
But atleast already a working recovery (TWRP 3.2.1) which would recognize the /OP as /vendor
Will work on each project a bit more when exams are over
i don't know if can help someone to build lineage or aosp based rom, btw here are the link to source and kernel for v30:
h930: http://opensource.lge.com/osSch/list?types=ALL&search=h930
us998: http://opensource.lge.com/osSch/list?types=ALL&search=us998
v300: http://opensource.lge.com/osSch/list?types=ALL&search=v300
Here the content of readme:
1. Android build
- Download original android source code ( android-7.1.2_r4 ) from http://source.android.com
( $repo init -u https://android.googlesource.com/platform/manifest -b android-7.1.2_r4
$repo sync -cdq -j12 --no-tags
$repo start android-7.1.2_r4 --all
)
- Untar opensource packages of LGH930_Nougat_Android.tar.gz into downloaded android source directory
a) tar -xvzf LGH930_Nougat_Android.tar.gz
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) lunch 1
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain) into the android directory.
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Uncompress using following command at the android directory
a) tar -xvzf LGH930_Nougat_Kernel.tar.gz
- When you compile the kernel source code, you have to add google original "prebuilt" source(toolchain) into the android directory.
- Run following scripts to build kernel
a) cd kernel/msm-4.4
b) mkdir -p out
c) make ARCH=arm64 O=./out joan_global_com_defconfig
d) make ARCH=arm64 O=./out CROSS_COMPILE=$(pwd)/../../prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android- KERNEL_COMPRESSION_SUFFIX=gz -j4
* "-j4" : The number, 4, is the number of multiple jobs to be invoked simultaneously.
- After build, you can find the build image(Image.gz) at out/arch/arm64/boot
Click to expand...
Click to collapse
I always loved to know how to build Kernel or ROM.
I'm not a dev so i cannot solve any FC or any other problem, so I need to know where to get the sources.
Little update here, decided to fix LOS14.1 first as 15.1 didnt wanna work at all ?
SGCMarkus said:
Little update here, decided to fix LOS14.1 first as 15.1 didnt wanna work at all
Click to expand...
Click to collapse
heheh don't give up my little dev... We believe in your skill :good:
Also could someone with a US998 test this?
And check what works (and doesnt)? And then send me the logcat (from /data/ramoops) after copying to the sdcard in twrp or whereever before restoring a backup xD
SGCMarkus said:
Also could someone with a US998 test this?
And check what works (and doesnt)? And then send me the logcat (from /data/ramoops) after copying to the sdcard in twrp or whereever before restoring a backup xD
Click to expand...
Click to collapse
I was just getting ready to ask if this will work on US998. If I get a chance I will try it out but I'm not sure how to do the logcat thing sorry.
foamerman said:
I was just getting ready to ask if this will work on US998. If I get a chance I will try it out but I'm not sure how to do the logcat thing sorry.
Click to expand...
Click to collapse
The logcat is taken automatically, as for idk why it wont be recognized via USB... (same kernel as the TWRP, ramdisk and so should also work), just boot into recovery after you used it a bit (if it even boots, otherwise do the button dance), and there, before you wipe/restore a backup, go to advanced -> file manager, browse to /data/ramoops and copy the log in there to the sdcard or whatever else is safe
SGCMarkus said:
The logcat is taken automatically, as for idk why it wont be recognized via USB... (same kernel as the TWRP, ramdisk and so should also work), just boot into recovery after you used it a bit (if it even boots, otherwise do the button dance), and there, before you wipe/restore a backup, go to advanced -> file manager, browse to /data/ramoops and copy the log in there to the sdcard or whatever else is safe
Click to expand...
Click to collapse
OK but now I have another problem TWRP backup failed on me. So if I do install 14.1 and it doesn't boot I have WETA 1.5 I can do the button dance and go twrp and reinstall weta as soon as I get some time I'll will try it.
---------- Post added at 02:45 PM ---------- Previous post was at 02:26 PM ----------
Sorry one more question I'm guessing we need to download our own gapps too yes? so arm64 7.1 pico would be fine that's the least one
foamerman said:
OK but now I have another problem TWRP backup failed on me. So if I do install 14.1 and it doesn't boot I have WETA 1.5 I can do the button dance and go twrp and reinstall weta as soon as I get some time I'll will try it.
---------- Post added at 02:45 PM ---------- Previous post was at 02:26 PM ----------
Sorry one more question I'm guessing we need to download our own gapps too yes? so arm64 7.1 pico would be fine that's the least one
Click to expand...
Click to collapse
Try it without gapps, its not worth to setup all that, it isnt daily driver ready... and gapps would just add more (unneccessary) stuff to the log ^^
--snip--
Well I tryred it but I got error 7 thats all I got
foamerman said:
Well I tryred it but I got error 7 thats all I got
Click to expand...
Click to collapse
Probably because of wrong device, remove the assert line in the updater-script in side the .zip file
(.zip/META-INF/com/google/android/updater-script)
SGCMarkus said:
Probably because of wrong device, remove the assert line in the updater-script in side the .zip file
(.zip/META-INF/com/google/android/updater-script)
Click to expand...
Click to collapse
OK I unzipped the file and deleted the (.zip/META-INF/com/google/android/updater-script) OK now I need a little help I'm a little slow I'm not sure how to zip it back up
{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS:
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), 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.
All the source code for LineageOS is available in the Suicide Squirrel and LineageOS Github repos.
If you would like to contribute to do not hesitate to submit patches
**** These builds are for UsU'd devices only ****
UsU? http://bit.do/unlockg4
Requirements
Your device need to be unlocked by UsU
Your bootloader stack should be on MM 20p or higher! (see FAQ #20 for how to upgrade your bootloader stack)
Latest TWRP - PREVIEW build: click
Clean modem partition (so no UsU baseband flashed) - see Installation topic for details
Installation
If you have ever flashed the UsU baseband package: Clean flash the modem partition in TWRP:
- TWRP flashable N modem (recommended)
Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash LOS
Flash GApps (8.1 - ARM64) if you like to use google apps
Flash SuperSU / Magisk if you want root
Boot (will take long on first boot!)
Enjoy
Download
Get your builds from my leech server
http://leech.binbash.it:8008/lineage/oreo/h815-UsU/
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Known issues:
Check the current issues at the github tracker (feel free to help, provide logs etc!)
Credits
LineageOS
ThePiGuy
kessaras
steadfasterX
and more..
Sources
LineageOS
Kernel
device tree
build manifest
XDA:DevDB Information
lineage-usu-h815, ROM for the LG G4
Contributors
steadfasterX, ThePiGuy, kessaras
Source Code: https://github.com/Suicide-Squirrel/local_manifests/tree/los-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 20p or higher firmware
Based On: pure LineageOS
Version Information
Status: Beta
Created 2018-06-20
Last Updated 2019-07-10
Reserved
Hey! I'm using it and it works flawlessly except 1 thing for me. I use bt calls much but now it has background noise as mentioned in known issues section. I can live without it but I hope you to solve this problem. Is there anything I can do for help? Thanks again @steadfasterX
emrtnl said:
Hey! I'm using it and it works flawlessly except 1 thing for me. I use bt calls much but now it has background noise as mentioned in known issues section. I can live without it but I hope you to solve this problem. Is there anything I can do for help? Thanks again @steadfasterX
Click to expand...
Click to collapse
Thanks for offering your help but unfortunately you can't do anything at the moment. I'm working on it at highest priority because I need it by myself but this issue is absolutely a nightmare and not easy to fix
Sent from my LG-H815 using XDA Labs
Thank You!
First of all, THANK YOU @steadfasterX for your work. I'm so happy there are still active developers for the G4, i'm finally free from the LG's claws.
I'm currently running the latest version of LOS available and here's a list of bugs/errors I found:
- I can't find/connect to 5GHz Wireless networks;
- The torch tile isn't working;
- Feels like even 2.4Ghz wi-fi connections are slowed down;
- SeLinux is permissive;
- Not an error, but I coudn't get Floatify to work on my lockscreen, guess it is not compatible with Oreo yet.
I didn't have issues with bluetooth media as some people had, though. There's no background noise
I hope this feedback help you somehow
igorgpsouza said:
First of all, THANK YOU @steadfasterX for your work. I'm so happy there are still active developers for the G4, i'm finally free from the LG's claws.
I'm currently running the latest version of LOS available and here's a list of bugs/errors I found:
- I can't find/connect to 5GHz Wireless networks;
- The torch tile isn't working;
- Feels like even 2.4Ghz wi-fi connections are slowed down;
- SeLinux is permissive;
- Not an error, but I coudn't get Floatify to work on my lockscreen, guess it is not compatible with Oreo yet.
I didn't have issues with bluetooth media as some people had, though. There's no background noise
I hope this feedback help you somehow
Click to expand...
Click to collapse
BT music is ok but calls has that bad noise.
Thanks for building this. Think I prefer Lineage to AOSCP.
Just a couple of issues that I have noticed so far.
I have the same problem on this ROM that I had using AOSCP. I tried to change the lockscreen to pattern during the initial setup wizard but it crashed and next time round I just skipped that step. Now when I try and set my lockscreen it just crashes the settings app.
Also torch tile doesn't work in the quick settings panel.
Rich Rich said:
Thanks for building this. Think I prefer Lineage to AOSCP.
Just a couple of issues that I have noticed so far.
I have the same problem on this ROM that I had using AOSCP. I tried to change the lockscreen to pattern during the initial setup wizard but it crashed and next time round I just skipped that step. Now when I try and set my lockscreen it just crashes the settings app.
Also torch tile doesn't work in the quick settings panel.
Click to expand...
Click to collapse
torch tile --> check the Known Issues in the OP for a workaround
regarding the settings crash: without logs no one can help you
adb shell
su
logcat -b all -c
logcat -b all
(now immediately reproduce the crash)
ctrl+c to cancel
Click to expand...
Click to collapse
copy the whole console output and paste it at http://bpaste.net (ensure you set the dropdown there to never)
steadfasterX said:
torch tile --> check the Known Issues in the OP for a workaround
regarding the settings crash: without logs no one can help you
copy the whole console output and paste it at http://bpaste.net (ensure you set the dropdown there to never)
Click to expand...
Click to collapse
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?
Rich Rich said:
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?
Click to expand...
Click to collapse
no. all good.
Rich Rich said:
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?
Click to expand...
Click to collapse
please do a backup in TWRP
then flash this TEST kernel in TWRP: http://leech.binbash.it:8008/kernel...ental/h815_usu_los_boot_TEST-build-1-oreo.zip
try again to access the settings screen
steadfasterX said:
please do a backup in TWRP
then flash this TEST kernel in TWRP: http://leech.binbash.it:8008/kernel...ental/h815_usu_los_boot_TEST-build-1-oreo.zip
try again to access the settings screen
Click to expand...
Click to collapse
Same error again. Here's log;
https://bpaste.net/show/2290419a8aee
Rich Rich said:
Same error again. Here's log;
https://bpaste.net/show/2290419a8aee
Click to expand...
Click to collapse
ok I have my h815 UsU'd as well and I cannot reproduce your issue.
Do you have tried to do a clean flash (means format system! --> FORMAT data! --> flash ROM) ?
Hint: obviously this will delete ALL your internal storage so take care of that and I recommend to use the app FlashFire for the backup of your internal storage before doing the above
.
steadfasterX said:
ok I have my h815 UsU'd as well and I cannot reproduce your issue.
Do you have tried to do a clean flash (means format system! --> FORMAT data! --> flash ROM) ?
Hint: obviously this will delete ALL your internal storage so take care of that and I recommend to use the app FlashFire for the backup of your internal storage before doing the above
.
Click to expand...
Click to collapse
Just tried that. Still the same.
Tried it twice, once as you said then again by picking all the wipe options. If I try set a password or code it will crash then ask me to re-enter the password which always fails.
Think I'll just use it without a lockscreen.
New build up
Happy leeching
@Rich Rich try that one too. Its really strange that it does work here and for you not. what firmware version is your bootloader stack?
Sent from my LG-H815 using XDA Labs
steadfasterX said:
New build up
Happy leeching
@Rich Rich try that one too. Its really strange that it does work here and for you not. what firmware version is your bootloader stack?
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Just flashed that and it's the same. My device is an import from Taiwan, so originally on the TWN firmware is that makes a difference.
How do I check the bootloader stack? I used the UsU guide and flashed the files given there.
Rich Rich said:
Just flashed that and it's the same. My device is an import from Taiwan, so originally on the TWN firmware is that makes a difference.
How do I check the bootloader stack? I used the UsU guide and flashed the files given there.
Click to expand...
Click to collapse
and what was the exact firmware version you were on before flashing UsU?
you can use SALT and check "Firmware (system)" in the main screen. its not 100% but we will see.
if you have followed the unlock guide you would have a backup of that. Then its enough to do this (requires Linux/FWUL):
Open a terminal in the directory where you have your SALT backup before UsU'd.
Then:
Code:
strings misc.bin | grep LG
and paste the whole output
steadfasterX said:
and what was the exact firmware version you were on before flashing UsU?
you can use SALT and check "Firmware (system)" in the main screen. its not 100% but we will see.
if you have followed the unlock guide you would have a backup of that. Then its enough to do this (requires Linux/FWUL):
Open a terminal in the directory where you have your SALT backup before UsU'd.
Then:
Code:
strings misc.bin | grep LG
and paste the whole output
Click to expand...
Click to collapse
I've attached a screenshot of my SALT window. Hope this shows the info needed.
Rich Rich said:
I've attached a screenshot of my SALT window. Hope this shows the info needed.
Click to expand...
Click to collapse
you know that you are using an outdated version of SALT? current is 3.16 atm.
now check the backup files as mentioned.
.
steadfasterX said:
you know that you are using an outdated version of SALT? current is 3.16 atm.
now check the backup files as mentioned.
.
Click to expand...
Click to collapse
Don't know where the backup files are stored. I just have SALT installed in a standalone VMWare Linux machine, I'm not Linux literate so not sure where to start looking for the files. What's the default backup location?