Los 19.1 question - Galaxy Tab S Q&A, Help & Troubleshooting

Hi @retiredtab, I'm trying to bring up los 19.1 for the tab S 10.5 LTE, i'm using your build guide with the current los 18.1 trees for the device, What changes did you need to make to get it to boot? I assume it would be similar seeing as they're both on kernel 3.4
Update: I used the trees and patches from ur github and from universalexynos5420 and i got it to the bootanimation, it hangs on bootanim tho
I'd appreciate if you could help out as i'm not familiar with reading logcat and kmsg's
Logs at: https://realmeme.realmemecloud.workers.dev/0:/
logs1 is logcat
kmsg2 is last_kmsg

Related

[ROM][6.0.1] LineageOS 13.0

LineageOS 13.0
Marshmallow - Android 6.0
​
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Additional Information:
maguro wiki page
toro wiki page
toroplus wiki page
Download:
The latest builds & changelogs are available at
https://download.lineageos.org/maguro
https://download.lineageos.org/toro
https://download.lineageos.org/toroplus
Extras:
su (arm)
su removal (arm)
Google Apps can be found at http://opengapps.org/?api=6.0&variant=pico - beware that only the pico version will fit, unless you change your partition sizes! Also, starting from M, it's recommended to install gapps before the initial boot so the permissions are properly set up.
Bugs:
- Sometimes, quiet speaker pop sounds can be heard at the beginning and/or end of some audio streams (ie. touch sounds - the workaround is to disable them). For some reason, this isn't affecting everyone.
- Report back anything else you find which isn't listed here
FAQ:
Does this ROM supports F2FS?
- Yes, on /data and /cache - although /cache F2FS support might get removed in the future, as it's worthless.
Does this ROM uses DDK 1.9?
- Yes, with all the camera issues (ie. pink lines, rare crashes) resolved.
Why does the initial boot take so long, and where are my live wallpapers?!
- To make room on the system partition for the (bigger) M gapps packages, I had to sacrifice dexpreopt and the live wallpapers. This can result in pretty long initial boots or upgrade boots, and dexpreopt might run during the first time setup wizard as well, slowing down the system for an additional couple minutes.
Will you release newer ZMoD builds or something?
- Yes, as soon as the memory optimizations are finalized and I find enough time...
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
LineageOS 13.0, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan, MWisBest, Android-Andi, Everyone else who helped me: AOSP, Hashcode, ...
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Version Information
Status: Nightly
Created 2016-02-11
Last Updated 2018-12-30
Does it have more ram 802 like the kernel used in cyanogenmod 12.1 you posted? Thank you!!!
Awesome!
Enviado desde mi GT-I9300 mediante Tapatalk
Thank you!!
AOSP Keyboard keeps crashing.. Apart from that everything seems to be working. Will check for more bugs in the meantime
Extraordinary work!!
PD: Device doesn't receive Internet connection. My ISP is Oceans Network from Spain.
You are a king!
Running on it for 1 hour, and already impressed... WOW !!!
Works perfectly
Works great! No problems at all and have been running it for 3hrs. Have xposed also installed. Great work!
I will continue to use and report any bugs i encounter.
great...Testing this rom right now. I had to rewipe,since installing gapps after the rom boot cause google play service to crash. I really wish there will be an official cm13 for galaxy nexus.I have a nexus 5 but I like galaxy nexus design and amoled screen...
Edit: this ROM runs very well,maybe a little better than other ones based on marshmallow
How much free ram? Is it 802mbytes or 762?in cn 12.1 there was a kernel boot img by zuyan that gave 802 mbytes of ram
Good job @Ziyan
Please guys, can anyone link me that kernel? I can't find it
Need suggestion, rootexplorer shown no root on this rom, how do i.
I try to flash ROM with TWRP, then fix root permission. @Ziyan could you please create this ROM support CWM.
Having random reboots now, is this happening to anyone else?
Reboots? Not yet
Gesendet von meinem Galaxy Nexus mit Tapatalk
@Ziyan can i flash kernels for lollipop like the one you posted on cm 12.1 recently?
NightWolf1396 said:
Having random reboots now, is this happening to anyone else?
Click to expand...
Click to collapse
Logs?
nikodr said:
@Ziyan can i flash kernels for lollipop like the one you posted on cm 12.1 recently?
Click to expand...
Click to collapse
No, but I attached a new kernel which has 811 mb userspace ram available (instead of the usual 756 mb). I think the crashes and tiler out of memory problems are gone, but report back if there's one single camera/camcorder crash happening
EDIT: the transition from the bootloader logo (google logo) to the boot animation won't be.. uhm... smooth, but it's nothing to worry about, I forgot to work it around this time
Ziyan said:
Logs?
No, but I attached a new kernel which has 811 mb userspace ram available (instead of the usual 756 mb). I think the crashes and tiler out of memory problems are gone, but report back if there's one single camera/camcorder crash happening
EDIT: the transition from the bootloader logo (google logo) to the boot animation won't be.. uhm... smooth, but it's nothing to worry about, I forgot to work it around this time
Click to expand...
Click to collapse
Will get them as soon as I get home
Ziyan said:
Logs?
No, but I attached a new kernel which has 811 mb userspace ram available (instead of the usual 756 mb). I think the crashes and tiler out of memory problems are gone, but report back if there's one single camera/camcorder crash happening
EDIT: the transition from the bootloader logo (google logo) to the boot animation won't be.. uhm... smooth, but it's nothing to worry about, I forgot to work it around this time
Click to expand...
Click to collapse
I will try zImage in my AOSP rom thanks can i use it no ?
Also there is no git commit for this extra RAM netither in OMAP4-AOSP or Ziyann github
werty100 said:
I will try zImage in my AOSP rom thanks can i use it no ?
Also there is no git commit for this extra RAM netither in OMAP4-AOSP or Ziyann github
Click to expand...
Click to collapse
Using the zImage on any DDK 1.9 / Android 6.0.1 ROM should be fine.
There is no git commit because I didn't push it yet (the values aren't final), but to get the same kernel I uploaded:
Clone https://github.com/CyanogenMod/android_kernel_samsung_tuna/tree/cm-13.0, and apply this, but with the following values:
CONFIG_ION_OMAP_TILER2D_SIZE=72
CONFIG_ION_OMAP_IPU_MEM_IOBUFS_SIZE=32
uji_sine said:
Need suggestion, rootexplorer shown no root on this rom, how do i.
I try to flash ROM with TWRP, then fix root permission. @Ziyan could you please create this ROM support CWM.
Click to expand...
Click to collapse
Enable root the same way you did it on CM12.1: enable developer settings, then you'll find the root option there. And just forget about CWM... don't use fix permissions and friends, as it might cause problems.
Ziyan said:
Using the zImage on any DDK 1.9 / Android 6.0.1 ROM should be fine.
There is no git commit because I didn't push it yet (the values aren't final), but to get the same kernel I uploaded:
Clone https://github.com/CyanogenMod/android_kernel_samsung_tuna/tree/cm-13.0, and apply this, but with the following values:
CONFIG_ION_OMAP_TILER2D_SIZE=72
CONFIG_ION_OMAP_IPU_MEM_IOBUFS_SIZE=32
Click to expand...
Click to collapse
I try before with zImage but rom was no booting i will try alter with commits thanks and kernel source

[Kernel][7.1.1] SunKernel Pedigree Z5 for LineageOS [sumire]

A custom Kernel for LineageOS 7.1.1 based on the ideas and experiences of SunKernel corona (StockKernel) for Xperia Z5 series
XDA:DevDB Information
SunKernel Pedigree Z5 for LineageOS, Kernel for the Sony Xperia Z5
Contributors
zacharias.maladroit
Kernel Special Features: FauxSound, KCAL, reworked thermal engine, fast camera, etc.
Version Information
Status: Beta
Current Beta Version: 1.3
Beta Release Date: 2017-03-14
Created 2017-03-14
Last Updated 2017-08-30
Reserved
Changelogs:
14.1_I
initial release - Features:
Click to expand...
Click to collapse
14.1_I.2
changes ...
Click to expand...
Click to collapse
14.1_I.3
add throttling for orientation sensor input events (most likely NOT needed) to cut idle cpu high load of 15-20%
Click to expand...
Click to collapse
14.1_I.4
removed lots of sources for log-spam (dmesg/kernel-log)
BCL<-->KTM interface for BCL (battery_current_limit) driver is now used, faster, more reliable (less overlapping) and better hotplug during thermal events, etc.
more reliable bcl mitigation due to fresh SoC value, allowing frequency-based mitigation even with BCL set to off
MUCH improved sound output
more reliable sound playback
Click to expand...
Click to collapse
Reserved
Kernel Releases (Betas for now):
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
From now on
both LineageOS and Resurrection Remix are unified builds that work on Single SIM and Dual SIM devices - no separate kernel or ROM needed !
Resurrection Remix: already IS the unified build (thread is currently parked at the General Subforum: Resurrection Remix 5.8.2 for Xperia Z5 (unified build) )
LineageOS: please download the unified LineageOS builds from olivier: lineageOS ROM (as mentioned at: LineageOS thread )
those are NOT boot-tested but should work (need testing + feedback)
Reserved (3)
Notes:
The preamp of FauxSound or the actual sound/soc driver state seems to be a bit "mushy",
thus the white noise (swoosh-ing, hiss-ing) is a bit high - reduce headphone amp by 10 or 15 (-10 or -15) so that you get a clear and well-defined output,
it really depends on your headphones - with in-ear it is most likely more noticable.
This was with unmodified "stock"/"upstream" lineageOS kernel source and with a bit patched up - so nothing I can and will change
Kernel source:
https://github.com/zachariasmaladro...kami_r2/commits/Sun-Kernel_Pedigree_cm-14.1_I
Thanks, I hope you don't forget dsds variant.
It is a pleasure to have SunKernel in LineageOS.
Thanks @zacharias.maladroit
I will try after released stable LineageOS for dsds and SunKernel.
Flashing lineage and kernel, looking forward to try it
Thanks for upload
s.hossein said:
Thanks, I hope you don't forget dsds variant.
Click to expand...
Click to collapse
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Thx! But After flashing this Kernel i couldnt Boot up. Stuck ar Boot Animation. But the Animation did not stopped.
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
zacharias.maladroit said:
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Click to expand...
Click to collapse
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
stipi69 said:
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
Click to expand...
Click to collapse
please update to the lineageOS builds from Olivier,
unless he has uncommitted changes locally in his repos - there are no changes,
my lineageOS build is at patchlevel March 5th 2017,
so with recent changes the kernel (more precisely the ramdisk) might be incompatible with the old builds from @Myself5
balrajs99 said:
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
Click to expand...
Click to collapse
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
In this minute i downloaded fresh update, flashed in this order:
1. lineage-14.1-20170316-UNOFFICIAL-sumire
2. open_gapps-arm64-7.1-nano-20161104
3. UPDATE-SuperSU-v2.78-20160905010000
4. Z5_SK_Enf_v14.1_I.3_sum
lineage from olivier from below link:
https://dl.olivierk.at/sumire/lineage-14.1/
lineage-14.1-20170316-UNOFFICIAL-sumire
i still get bootloop, scren is dimed, lineage animation keeps going for couple of secs, screen goes bright and bootloop from there on, waiting 10+ minutes now... maybe old superuser zipfile for this task? dont know realy, will make clean install
zacharias.maladroit said:
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
Click to expand...
Click to collapse
Yes, on latest build by oliver it ran into bootloop.
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
@zacharias.maladroit: Thank you a lot for your work. We should be very thankful to every developer on the Z5!
Just gave your Kernel a try on latest olivier's lineageos (0316). Got a bootloop. After 20 minutes, I did a power reset and dirty reflashed latest olivier's lineageos (0316) via TWRP. Telephone was functional again.
L33Tgod said:
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
Click to expand...
Click to collapse
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
Click to expand...
Click to collapse
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks
zacharias.maladroit said:
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks[/QUOTE]
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
L33Tgod said:
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
yeah, that's why I wrote:
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)[/QUOTE]
might be that upstream changed the content of updater-script,
that's why I ask for a working variant ;)
Click to expand...
Click to collapse

Help building Lineageos kernel from source

I'm no expert and just wanted to try and build Mi5s lineageos kernel with just a few minor changes, not the whole rom, but after flashing it doesn't boot.
This is more or less what I've done:
Downloaded lineageos Mi5s source:
https://github.com/LineageOS/android_kernel_xiaomi_msm8996
Downloaded Gooogle's prebuilt toolchain:
https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/
Setup a build system following guides/tutorials from here and there.
Got it to successfully build after a few fixes to source but it doesn't pass the Mi logo.
The 3 images in the output folder are, Image, Image.gz and Image.gz-dtb, from what I've read in various tutorials was to use the Image.gz-dtb image.
So initially I unpacked stock lineageos boot.img and repacked it with my compiled Image.gz-dtb, also I've tried Anykernel2, but it just results in a non booting kernel.
I'm not sure what I'm missing and any help is really appreciated.

device tree

Does anyone have the klte device tree? Or can I just use the lineage one while compiling Roms that aren't los? Its a lot of work to build it from scratch.
Of course you can, you just need to have the correct files, get the repos of lineageOS and put them in another rom, send me a PM and I will gladly help you
Thx

A300FU Lineage 16.0 Selfbuild Bootproblem [SOLVED]

hi all
my story:
i got my hands on a samsung galaxy a300fu (aka. a3ulte) 2015 and successfully installed twrp3.2.3 and a custom lineage build version 14.1. my goal however is to build, install and boot lineage 15.1 or lineage 16.0. the building is not the problem! i can build both versions (with help of the lineage wiki and the local manifest from the github user "Galaxy-MSM8916"). i can also install them however i'm unable to boot them.
what i tried so far:
- the mentioned github user offers multiple lineage 15.1 downloads for the device but none of them seem to boot (it crushed my PIT or something i needed to reflash the recovery image)
- since android 8.0 the debug mode is off so i needed to build an engineering version (another 4h) to get some kernel messages but i'm kind of overwhelmed with 11000 lines of debug (not counting the loops)
- on androidfilehost there is a lineage 16 build from the user vlw (also present here on xda) which strangely seems to be working! after checking its system properties file however it seems this build is kind of a hybrid (part a3lte, part a3ulte). also i'm unable to contact him that's why i'm writing here.
i'm pretty much out of ideas and would like to know if any of you has an idea how to proceed.
regards
edit:
related to github.com/Galaxy-MSM8916/android_device_samsung_gprimeltezt/issues/1
able to boot after renaming hardware/qcom/keymaster/Androir.mk to hardware/qcom/keymaster/Android.mk.nobuild

Categories

Resources