LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
There are lineage os builds for only tab s2 8.0 2015 models.
this version is stable without any known issues.
Root is not included here. For root install magisk or su-addon ( https://mirrorbits.lineageos.org/su/addonsu-14.1-arm-signed.zip )
install:
flash with twrp
don't forget to flash gapps ( opengapps.org ) you need version for android 7.1 arm
download:
20180102
t710: https://drive.google.com/open?id=1tkzdpZdGXNouu0ig-NHGErWfmUP_CICP
t715: https://drive.google.com/open?id=1cLX-gWvUM9miJ3JTmcnWeXrNxI0F3II5
test build 20180303 for t710 is here: https://forum.xda-developers.com/showpost.php?p=75756582&postcount=147
sources:
https://github.com/bonuzzz/android_kernel_samsung_gts2
https://github.com/bonuzzz/android_device_samsung_gts2-common
https://github.com/bonuzzz/android_device_samsung_gts28wifi
https://github.com/bonuzzz/android_device_samsung_gts28ltexx
https://github.com/bonuzzz/android_vendor_samsung_gts2-common
https://github.com/bonuzzz/android_vendor_samsung_gts28wifi
https://github.com/bonuzzz/android_vendor_samsung_gts28ltexx
WOW! This is the first build of Lineage that works great on my tab! Didn't test fingerprint but autobrightness and camera is working great. Thank a lot. On T710 by the way.
See my signature for twrp 3.1.1-0 for both gts28wifi and gts28ltexx.
Please note that twrp 3.2.0-0 has just been released! I'll be working on bringing it up to the Galaxy Tab S2 2015 tablets as soon as possible
On a related matter, I own a 9.7 wifi variant and I build for it daily. Netflix doesn't work with the official gts2-common repo, but if you use mine it will. I kept a long since abandoned fix which has worked very well in my builds.
Do we need gapps, thank you sooooooo much for this!!!!
Sent from my SM-T710 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:45 AM ----------
ripee said:
See my signature for twrp 3.1.1-0 for both gts28wifi and gts28ltexx.
Please note that twrp 3.2.0-0 has just been released! I'll be working on bringing it up to the Galaxy Tab S2 2015 tablets as soon as possible
On a related matter, I own a 9.7 wifi variant and I build for it daily. Netflix doesn't work with the official gts2-common repo, but if you use mine it will. I kept a long since abandoned fix which has worked very well in my builds.
Click to expand...
Click to collapse
You sir, are a good among men, which gapps do you recommend? And we can install su manually whithout messing up the fixes you got to make this bad boy run? Once again thank you.
Sent from my SM-T710 using Tapatalk
lahegry said:
Do we need gapps, thank you sooooooo much for this!!!!
Sent from my SM-T710 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:45 AM ----------
You sir, are a good among men, which gapps do you recommend? And we can install su manually whithout messing up the fixes you got to make this bad boy run? Once again thank you.
Click to expand...
Click to collapse
I flash pico on my phone and tablet, but even stock or higher should work if the builds are from official sources. I also recommend Magisk if you wish to root. If these builds have su root, Magisk simply uninstalls it before installing itself.
bonuzzz, you did what most (self proclaimed) devs failed to achieve and deliver for the T710/715 in the last months! i just installed the ROM and tried it out the last few hours. finally got a clean and reliable android for my T710.
it's working really smooth, no issues so far. everything - including bluetooth and fingerprint - is working perfectly [edit: haven't tried it, since not needed: according to some posts in this thread stock camera doesn't seem to be working properly]. i am really anstonished and amazed by this great initial release, thanks a lot. i hope you keep on delivering such a good work.
many thanks and best regards from germany
For me on my T710 the microphone did not work. So it isn't in perfect working order yet and the battery drains quite fast, but it's miles better than the previously shared builds here on XDA, and most certainly usable.
I also had issues with certain apps not working properly, so I ended up going back to stock for now. (more precisely: the Antutu 3D part and the Focus gallery application).
TWRP 3.2.0-0 for gts28wifi and gts28ltexx!
twrp-3.2.0-0-gts28wifi.img
twrp-3.2.0-0-gts28wifi.tar
twrp-3.2.0-0-gts28ltexx.img
twrp-3.2.0-0-gts28ltexx.tar
@ripee,
create your own topic please. dont spam here. thank you
bonuzzz said:
@ripee,
create your own topic please. dont spam here. thank you
Click to expand...
Click to collapse
Sorry if twrp is spam. Best of luck fiddling around with lineage recovery. For everyone's sake, I hope that Netflix works on your builds.
Thanks a lot for this build. An important progress for the T710/T715.
And also thx for the current TWRP link @ripee, missed that one.
Camera app force closed. Dont save any pictures
If you use a third party app like open camera, it actually works really well.
Either way, the microphone doesn't work at all, as in all roms for this device, and sadly it is a deal breaker for me since I use my tablet for video calls all the time.
azenyr said:
If you use a third party app like open camera, it actually works really well.
Either way, the microphone doesn't work at all, as in all roms for this device, and sadly it is a deal breaker for me since I use my tablet for video calls all the time.
Click to expand...
Click to collapse
open camera same problem.
My twrp recovery is old. I update this and I will try again
Having used this ROM for the last few days on a T710, I experienced a very stable system. UI was always smooth, no serious issues so far. :good:
However, I observed some strange behaviours/minor issues:
Fingerprint unlock isn't always working reliably. Sometimes, when trying to unlock the lockscreen, the finger on the fingerprint sensor doesn't seem to be detected and the PIN has to be entered manually.
LiveDisplay is not always active when the device comes from sleep and has to be unlocked. Upon the next sleep/active via short press on the power button iteration, the LiveDisplay mostly works as expected.
Once, presumably a wakelock drained the battery throughout the day until it was empty and the device turned itself off. I don't know why this happened and can't reproduce it.
Altogether a very successful start for this ROM, I will keep it on my device and hope the dev keeps on working on it to further improve it or even update to Lineage 15.x...
Thanks, @bonuzzz!
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img.tar
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img.tar
ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img.tar
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img.tar
Click to expand...
Click to collapse
Hi! I tested gts28wifi for my SM-T700 but touch sensor is wrong. The interface is unusable for now. Best of luck. But you should start your own thread...
powerade001 said:
Hi! I tested gts28wifi for my SM-T700 but touch sensor is wrong. The interface is unusable for now. Best of luck. But you should start your own thread...
Click to expand...
Click to collapse
ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
What would be the point of a dedicated thread if it doesn't work? Anyway, thanks for your feedback.
Click to expand...
Click to collapse
ripee said:
ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
What would be the point of a dedicated thread if it doesn't work? Anyway, thanks for your feedback.
Click to expand...
Click to collapse
The point is,..
If your building it, wouldn't you want it all together so you could track it easier? Now you'll need to read all the threads that you've posted this into to find the results.
I know we all appreciate you doing this. But please make your own thread for it so we can all see what's going on. Without having to read through the 4+ threads this is in.
Keep it up. It's nice to see our tabs still getting some love. Thank you. ?
Click to expand...
Click to collapse
engine95 said:
ripee said:
The point is,..
If your building it, wouldn't you want it all together so you could track it easier? Now you'll need to read all the threads that you've posted this into to find the results.
I know we all appreciate you doing this. But please make your own thread for it so we can all see what's going on. Without having to read through the 4+ threads this is in.
Keep it up. It's nice to see our tabs still getting some love. Thank you.
Click to expand...
Click to collapse
Is it possible to make android oreo??
What are the basic requirements for it??
Click to expand...
Click to collapse
Related
Hi guys,
I've updated my Nexus 7 FLO to version 4.4.4-20140704-flo-NIGHTLY
After reboot the WLAN dies not work.
Is there an Kernel/driver issue?
Kind regards
Chris
Read commit comments here.
Problem is we're in the process of getting a new maintainer fully spooled up. There are various techniques device maintainers have available to them that need to be used for certain device maintenance tasks (like a full upstream merge) which aren't normally available to gerrit users.
Andre hasn't quite yet learned how to properly wield his newly-given powers. Specifically, the kernel tree really shouldn't be a fully squashed merge, but individual commits. He reverted the squash but the push of the individual commits failed last time he tried it. He went away for a few days around the same time pulser sorted his access, so the kernel is still backleveled.
I could fix this myself, but I want Andre to do this on his own so he knows how to do it going forward.
?
Sorry but I didn't understand this in detail. Only that some merges die not work.
Workaround for me was to install Franco Kernel.
Now WLAN works again.
May there are some more quality tests required before merge into nightlies?
Kind regards,
Chris
cnexus4 said:
?
Sorry but I didn't understand this in detail. Only that some merges die not work.
Workaround for me was to install Franco Kernel.
Now WLAN works again.
May there are some more quality tests required before merge into nightlies?
Kind regards,
Chris
Click to expand...
Click to collapse
No, the issue is that we have a new maintainer that needs to learn some new maintenance techniques. Rather than push the fixes ourselves, we want him to do it, but he's on vacation for a few days.
Thanks for your answer. OK, wie all have to learn new technologies.
Kind regards,
Chris
cnexus4 said:
Thanks for your answer. OK, wie all have to learn new technologies.
Kind regards,
Chris
Click to expand...
Click to collapse
I just tried to install OmniRom on my Nexus 7 2013 (flo)
Once installed, it is not able to do wireless internet, which is a fatal error.
Will it be posted in this thread, or where should I look to know when this is corrected?
Thanks in advance, and sorry about the prior attitude. (long day)
- Gary
When I last tried this about the 20th July wifi was still not working can anyone confirm its safe to update - I had to fall back to a month old image as I wasn't sure when the issue appeared..
Tia
---------- Post added at 02:58 PM ---------- Previous post was at 02:39 PM ----------
codifies said:
When I last tried this about the 20th July wifi was still not working can anyone confirm its safe to update - I had to fall back to a month old image as I wasn't sure when the issue appeared..
Tia
Click to expand...
Click to collapse
Answering my own question I downloaded a Franco kernal as a precaution and tested it, happy to say the new maintainer has it well in hand by the looks as its all working OK
Okay there's something else going on, quite an odd one this...
After playing with some kernels WiFi stopped working - no great surprise, so I reinstalled the latest nightly that *was* working and now it doesn't ! Even after wipe of data / system install of month old (or latest) and I can't get anything from WiFi...
I've had to restort to using CyanogenMod as I can't seem to work out what's going on here !!!
Any ideas and I'm up for investigating - the only wrinkle is I'm currently using a multirom version of twrp but I'm not injecting it, so that shouldn't matter ?
Any ideas folks?
There's a fixed_wifi_boot.img that needs to be downloaded and flashed in the bootloader. If you've flashed a recovery before, it's similar. Just do "fastboot flash boot fixed_wifi_boot.img" in the right directory.
[QUOTEr;54470792]There's a fixed_wifi_boot.img that needs to be downloaded and flashed in the bootloader. If you've flashed a recovery before, it's similar. Just do "fastboot flash boot fixed_wifi_boot.img" in the right directory.[/QUOTE]
What does this file actually do?
Will it prevent other ROMs such as CyanogenMod or kernels using googles official binary blobs from working?
Can it be undone ?
Where is the file?
Tia
The file is in the same location where you downloaded the OmniROM nightly. As for conflicts between other ROMs/kernels, I'm not sure. I imagine there's an official boot image somewhere that can be flashed, maybe Google's stock images install it.
Sent from my Nexus 7 (2013) using Tapatalk
thevypr said:
The file is in the same location where you downloaded the OmniROM nightly.
Click to expand...
Click to collapse
Code:
fastboot flash boot fixed_wifi_boot.img
You can find the file on dl.omnirom.org/flo/ at the bottom (I can't post external link)
I will try soon.
I'm reluctant to try this if it means I wouldn't be able to use stock ROMs or say cyananogen mod or some other such...
I'd love to hear an explanation of what its doing too....
codifies said:
I'd love to hear an explanation of what its doing too....
Click to expand...
Click to collapse
You should look at this thread http://forum.xda-developers.com/showthread.php?t=2626831&page=12
I can't write into above mentioned thread!?
But I'm happy that WLAN is working again.
Hi,
I don't want to waste your time, but I think this is a proper time to ask a question.
This tablet(s) are 9 months on the market. Tons of ROMs came to see the daylight, every less important variant of this device got AOSP or CM builds for them, and that's awesome! And everybody enjoy their cool tablets, except ... the owners of the best and most important variant - 10.5 LTE. And there is even official T705 CM12 build! Why not for T805?
I feel sorry I don't have any knowledge in programming or porting, neither I have any pleasure in doing it. But there are a lot of great and talented chiefs who love to port and build good ROMs who make a good TW stuff, and a lot of guys who make AOSP for ... WiFi version. Noone is interested in LTE model, and there is a lot of T805 users out there waiting for AOSP release and asking on every Tx00 threads for builds for their devices.
I have a lot of respect for hard work everyone do here, and we all understand everyone of you - talented chiefs here - have limited time and possibilities. I am personally very grateful for your effort. And don't get my post wrong. All it is about is to ask: Why? Why there are CMs, AOSPs for T800, which I think is not so much different from LTE model,and there is NOTHING AOSP for T805....
I think there will be more than only me to greatly ask for attention from great developers of xda, to ask them for xda miracle for us. Please, make something AOSP for T805... please please please! Let us see this:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
We all would be so grateful for your help, to let us feel the Google Experience..
Thank you!
HUGE UPDATE
It looks like we got it! Finally, good working Lollipop with LTE on our amazing devices. Now the Tab S got a new life, with pure Google Experience! For everyone interested, check out our great developer who made a HUGE effort to make this happen (big cudos to AndyT12) and his website with updates and downloads:
http://goo.gl/ODCQ94
AAAND HERE WE GO!
Another AOSP from cool developer deadman96385:
http://forum.xda-developers.com/gal...m-liquidsmooth-v4-1-lollipop-sm-t700-t3092696
Unfortunately LTE still does not work here but they have just the initial build se let's be patient! Thank you!
UPDATE ON NEXT GREAT BUILDS
We are happy to see yet another great build with working LTE! This time it's amazing work from developer Nexorr who managed available sources from NVertigo and AndyT to build this ROM! Check the links below to download the stuff:
http://forum.xda-developers.com/showpost.php?p=61934130&postcount=78
http://forum.xda-developers.com/showpost.php?p=61940915&postcount=84
Thank you Nexorr for your huge effort!
Yes.. I'm interested this project... Available for Betatester on my Sm-t805.... Happy to see Android v5.1.1 full working on this device
T805 is alot different than T800. Nvertigo explained why a while back. One simply cannot build without having the device. In my guessing, more people probably have wifi ones vs lte models in which most devs have Idk. Nvertigo made a thread also on how to build/port. http://forum.xda-developers.com/showthread.php?t=3031278
It requires a ton of work so... yeah.
So there is no hope, I guess...
Btw I thought there are much more interested people in the AOSP. I was wrong, it seems. 248 visitors came across this thread without even a word, so let's say it: buy N9 or eat TW rubbish.
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
callum_88 said:
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
Click to expand...
Click to collapse
Bring him in.
callum_88 said:
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
Click to expand...
Click to collapse
Whoever read the cm12.1 for t800 thread knows about how much time I can spend on development untill November: it's hardly enough to keep up the development for t800.
So: no, I will not develop for a different device for now.
I said MANY times: there is a cm11 development for chagalllte and cm12.1 for klimtlte. Thats a good starting point.
nvertigo67 said:
Whoever read the cm12.1 for t800 thread knows about how much time I can spend on development untill November: it's hardly enough to keep up the development for t800.
So: no, I will not develop for a different device for now.
I said MANY times: there is a cm11 development for chagalllte and cm12.1 for klimtlte. Thats a good starting point.
Click to expand...
Click to collapse
And the questions from the first post still apply.
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
andyt12 said:
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
Click to expand...
Click to collapse
Hi Andrew! It is so great to hear! This is so cool! Thanks for the information. Are you willing to make xda thread also? Thanks!
PS. Is this build working or it is relatively experimental one? I am worried to lose my data or backups etc..
Hi, i have problems with download, it is so slow and then breaks the download fail. Any oher options to download ?
It was so great CM12.1 for the tab T805 LTE...... and great Job Thanks
One question, must i use your twrp or is it ok with the Original twrp i have 5.0.2 on my tab Iron Rom lollipop
Same here, download fail. But anyway, thank you for your effort! Would really like to try it.
Btw backing up efs, in twrp?
I could use a quick HOW-TO, @andyt12:
with both your provided Odin3.07, and my own Odin3.10, I could not graphically locate either your .md5sum file, nor the .zip ROM archive. At least I *could* enter the file/archive names at the Odin text-entry-box...
but that produced another pair of issues:
-although the suffix ".md5sum" isn't recognized, direct-entry of the filename indicates "binary corrupted" or similar
-entering the .zip archive directly results in Odin message-box saying "success 0/failed 1"
I am really, really excited at the prospect of CM12.1 for my tablet (matching my phone). But I seem to be sort of stuck at some basic point. BTW, I already had TWRP-2.8.6.0 installed on my T805, so I left that and did not try your provided version...
Thank-you for you efforts! I deeply appreciate the work you've put into this!
GordP
is this for t-805y or just t-805 ? since u seem from OZ the version i have is from telstra.
This is awesome. I'm so grateful someone is making a CM12 for t805. Will be trying it soon. Do we have a list of known issues/things that still need work?
andyt12 said:
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
Click to expand...
Click to collapse
Please put it in Xda it will be helpful to test and to make solutions to help you in this project
I've downloaded the latest build (as of May 30) and re-uploaded it to Mega (with an md5 file): https://mega.nz/#F!JhsSTahA!sEf03jOCUWHFbQXizOX_lA
DarkDvr said:
I've downloaded the latest build (as of May 30) and re-uploaded it to Mega (with an md5 file): https://mega.nz/#F!JhsSTahA!sEf03jOCUWHFbQXizOX_lA
Click to expand...
Click to collapse
There is any issue or bugs in this rom ?
Cuz there is no info about rom
So, here's what I did/got:
To repeat dev's words:
Make sure you use EFS backup tools (for example, there's one in Play store) to backup your EFS/IMEI partitions somewhere in a safe place (not just on a tablet).
1. Was not able to install Andrew's TWRP (Odin claims it's broken, redownloading the tar.md5 didn't help).
2. Used my own TWRP (latest, from XDA) to wipe system/data/caches, then install the CM12 zip Andrew has created.
3. Installed latest 5.1.x gapps (micro) from here: http://www.androidrootz.com/2015/03/download-android-51x-lollipop-pa-gapps.html
4. Rebooted
ROM booted just fine, no errors or issues so far.
Bluetooth tested and works.
Wifi tested and works.
Mobile network and data tested and works.
Root, ADB work
USB works - able to see both device storage & SDcard
CPU: usage seems normal, with cores ranging from 200MHz to 1.9GHz. Although I don't see any cores disabling during no load. Not sure if this is normal.
Performance: subjective. To me, device seems a hell of a lot snappier. Transitions, scrolling, app switching - noticeably smoother than on Lollipop TW.
GPU test: tested in a game (hearthstone), performace is the same as on stock ROM, didn't see any difference.
Temperature: max 43C so far, seems the same.
Camera: both front and back cameras work
Battery: device is sleeping fine, no wakelocks. Battery usage completely flattens when it's sleeping, so, in a few days, I'm expecting a good battery life.
Charging: I think it's the same as on stock: around +500mA when device is ON and on a wall charger.
Bug: Samsung's stock docking keyboard: everything works, expect the app switch button.
Bug: In app switcher - there's an error loading the search widget. No big deal, but it's a thing.
Device info screen
Continuing to test other features, but so far, no issues encountered. Getting really freaking excited.
DarkDvr said:
So, here's what I did/got:
1. Was not able to install Andrew's TWRP (Odin claims it's broken, redownloading the tar.md5 didn't help).
2. Used my own TWRP (latest, from XDA) to wipe system/data/caches, then install the CM12 zip Andrew has created.
3. Installed latest 5.1.x gapps (micro) from here: http://www.androidrootz.com/2015/03/download-android-51x-lollipop-pa-gapps.html
4. Rebooted
ROM booted just fine, no errors or issues so far.
Bluetooth tested and works.
Wifi tested and works.
Mobile network and data tested and works.
Continuing to test other features, but so far, no issues encountered. Getting really freaking excited.
Click to expand...
Click to collapse
Thank you for this info
What about battery and temperature of device ?
And if he used default kernel speed for cpu
Sorry for long questions
Finally what about speed and what is better TW or CM12.1 ?
All the answers before my post ? ??
Hey guys
In memory of a very dear friend who passed away yesterday, I am starting this thread and a new era for our x3.
CM has pushed their CM13 branches yesterday, which means it's time for a new project. This time, though, I will be all by myself.
Please do not expect any miracles soon, as the M sources still need to settle a bit before we can even hope for a halfway working build.
Once again, you have several ways to get in touch with me/us:
You can use this thread (but keep it development related)
We have our own IRC channel on freenode, called #p880-dev
Use our github site
PM (even though the other ways are preferable)
We are of course still open source, and you can find the repos on our github:
Device tree
Kernel
Blobs
Any help is greatly appreciated, be it pre-alpha testing, or helping with actual development and fixing bugs. Feel free to make a pull request on github, which we will most likely merge happily. If you're not that experienced in git, feel free to contact me about it.
If you want to use this sources/ROM as your base, you sure are allowed to, but please let me/us know about it before you release it and give proper credits.
That's all we're asking for.
I know you want to know the actual Status, so I try to always keep it updated in this OP:
Not working:
Most likely everything
Working:
Most likely nothing
Now, the most important part:
If you like our work and all the time we spent in order to get it working, feel free to buy us a coke/beer/whatever by donating a litte bit
Special thanks go to: (names in no particular order)
@Daniel Kng
@fritzcola
@sunsettrack4
@thegrim11
@LGaljo
@alfsamsung
@Adam77Root
kingf1 from IRC
And last but not least, please keep this thread on topic! All OT posts will be deleted without further warnings!
XDA:DevDB Information
[DEV] [WIP] Unofficial CM13 for the p880, ROM for the LG Optimus 4X HD
Contributors
laufersteppenwolf
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-10-06
Last Updated 2015-10-06
Reserved
A quick update, CM's sources are still not compilable as they are still working on the initial bringup.
I will stay on it and see what I can do
I will pay you, just please make final ROM for 4X, with everything working as it shoud be! That would be awesome!
Wysłane z mojego LG-P880 przy użyciu Tapatalka
I will pay you too. I would like when I will be to have the final ROM fo 4x. Thanks
Make it working relibly and responsively, and I will pay you too. You deserve it!
I don't mind if it takes months to achieve it. Just make it at some point, and I'll be happy!
Can't wait !!!
ps. i'm sorry for your friend
laufersteppenwolf said:
A quick update, CM's sources are still not compilable as they are still working on the initial bringup.
I will stay on it and see what I can do
Click to expand...
Click to collapse
I'm also waiting for complete bringup tried for daily driver... failed. If you need help just send me message on hangouts/mail
@laufersteppenwolf, I was hoping you could give insight regarding this current dilemma seen with CM13. http://pastebin.com/vHMRMS0E
Feel free to PM me or reach out on here. Wanting to know if you were successful getting past the problem and if so what was your solution. Your time and consideration is appreciated.
SHM said:
@laufersteppenwolf, I was hoping you could give insight regarding this current dilemma seen with CM13. http://pastebin.com/vHMRMS0E
Feel free to PM me or reach out on here. Wanting to know if you were successful getting past the problem and if so what was your solution. Your time and consideration is appreciated.
Click to expand...
Click to collapse
that's a CM issue and needs their fixing. Hence I did not look into it, because if I go on do my "fix" it will most likely differ from CM's fix and may then cause some later issues.
So I'm currently waiting for CM to fix it
Some days ago is builded a cm13 ZIP, but it doesnt even pass bootloader.
Here are my commits for device tree. I disabled most likely everthong what causes building errors like Audio and CameraWrapper.
Here are my commits https://github.com/lenzwagner/android_device_lge_p880/commits/cm-13.0
@laufersteppenwolf will be on IRC the next evenings. Hope you'll be there too.
---------- Post added at 07:45 PM ---------- Previous post was at 07:40 PM ----------
laufersteppenwolf said:
that's a CM issue and needs their fixing. Hence I did not look into it, because if I go on do my "fix" it will most likely differ from CM's fix and may then cause some later issues.
So I'm currently waiting for CM to fix it
Click to expand...
Click to collapse
They fixed it some days ago.
Look here:
1. http://review.cyanogenmod.org/114239
2. http://review.cyanogenmod.org/114277
3. http://review.cyanogenmod.org/112338
I already fixed the device tree quite some time ago without disabling it, will have to look into it another time as I have to fix my mom's lappy first...
laufersteppenwolf said:
I already fixed the device tree quite some time ago without disabling it, will have to look into it another time as I have to fix my mom's lappy first...
Click to expand...
Click to collapse
If you find time, i'm on IRC atm
@fritzcola, just got home from work, gonna check out those commits now. Thanks for posting them. ffmpeg has been a pain for me this past week trying to compile CM13 :-/. Gotta love a fresh brunch out the kitchen lol.
edit: eh, those commits have already been merged so problem still persists.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
@fritzcola, just got home from work, gonna check out those commits now. Thanks for posting them. ffmpeg has been a pain for me this past week trying to compile CM13 :-/. Gotta love a fresh brunch out the kitchen lol.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Just run "make clean" and "repo sync". Commits are already merged in source apart from one.
@laufersteppenwolf Can you upload the fixes to a " cm-13.0" branch?
And do you already go further than BL?
fritzcola said:
Just run "make clean" and "repo sync". Commits are already merged in source apart from one.
@laufersteppenwolf Can you upload the fixes to a " cm-13.0" branch?
And do you already go further than BL?
Click to expand...
Click to collapse
Yea, just verified I already have them in the source. Stagefright still being an issue. Need to look at gerrit and see if there is a commit on standby that may resolve my problem. codecs_utils.cpp fails to compile over at external/stagefright-plugins/utils/.
SHM said:
Yea, just verified I already have them in the source. Stagefright still being an issue. Need to look at gerrit and see if there is a commit on standby that may resolve my problem. codecs_utils.cpp fails to compile over at external/stagefright-plugins/utils/.
Click to expand...
Click to collapse
Weird cause i just compiled a build with no errors.
fritzcola said:
Weird cause i just compiled a build with no errors.
Click to expand...
Click to collapse
I got passed it finally. Seemed it was just a fluke with no explanation. Got to deal with this problem now. Take note of line 232 specifically. Haven't had time to mess with it yet.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
I got passed it finally. Seemed it was just a fluke with no explanation. Got to deal with this problem now. Take note of line 232 specifically. Haven't had time to mess with it yet.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Are you sure you're building for P880!? MSM8974 is Snapdragon stuff
fritzcola said:
Are you sure you're building for P880!? MSM8974 is Snapdragon stuff
Click to expand...
Click to collapse
No sir I am not. For another device, forgive me if that caused any confusion. My initial post on here was with regards to ffmpeg. A hunt for an unofficial build on xda brought up a few links and so wanted to make contact with the dev(s) to see if they had the same problem and/or fix so I may compare and possibly adapt if applicable my previous outcome. As for my current issue I do not expect any answer or results from here since its completely off topic from this device. I merely shared it in response with no intention or expectations for a solution. . I did take a look at your repo and saw ffmpeg is obsolete so I removed it from my tree as well since it was most definitely causing my builds to break.
--FOR MORE INFO AND NEWS ALWAYS CHECK MY LAST REPLY!--
Thanks for understanding!
PROJECT IS ABANDONED.
Regards,
Holy ****, finally. I cant try it out for my self cause i need to leave to malta tomorrow but i can try it later
MIUI Rom, finally!!!!
I hope they fix the bug as soon as possible
Again, the ROM is NOT bootable, I need logcats from you to fix the problem, hopefully.
So don't expect this to boot.
Thanks for understanding!
Try to take a look here Logcats
I hope to have helped
Giuseppe300715 said:
Try to take a look here http://https://forum.xda-developers.com/showthread.php?t=1726238
Click to expand...
Click to collapse
I cannot open the link. It gives me an error.
XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
He meant this link https://forum.xda-developers.com/showthread.php?t=1726238
XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
I just fix the connection
---------- Post added at 09:04 AM ---------- Previous post was at 08:50 AM ----------
[Universal] [Flashable] [Logcat] [Guide] So your test ROM build didn't boot
[UNIVERSAL][LOGCAT]How to get & read a logcat/ Troubleshoot your own issues!
That's all I've found and that can be useful for both this Rom and others that you will develop.
Thank you, but I know how to dump logcats. I asked you if you could provide me some logcats of the rom not booting from your device and send me.
Thank you.
XTutorials said:
The ROM is compiled, but it doesn't boot and me and @AymenDe7 need logcats.
I will provide a download link, but just in google drive so not much downloads will be allowed. Bootable version (if) will be released on androidfilehost.
https://drive.google.com/open?id=0Bx9qplihpe8YVUNZRTNnSFY1bkk
Full no reject source code:
https://github.com/aymende7/XTutorials_Miui8
For now I need logcats from you.
Thanks for understanding!
Click to expand...
Click to collapse
Here's my logcat. http://www117.zippyshare.com/v/WcWK3ksX/file.html
I think there's problem with OpenGL
06-13 10:04:20.297 2468 2468 E libEGL : load_driver(/system/lib64/egl/libGLES_mali.so): dlopen failed: library "/system/lib64/egl/libGLES_mali.so" not found
06-13 10:04:20.297 2468 2468 F libEGL : couldn't find an OpenGL ES implementation
--------- beginning of crash
Click to expand...
Click to collapse
And if you would copy libGLES_mali.so to /system/lib64/egl?
Would it work?
Thank you for your logcats. I will see what I can do.
How does it go with progress?
Should boot if you use custom kernel and copy&replace blobs
I am giving up on trying to fix that error message. I am trying to build AOSP 6 and then try again patchtom, hopefully I won't get that error.
I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.
haky 86 said:
I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.
Click to expand...
Click to collapse
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
Yeah. We have like 2 developers(one is a team) On this device. Haky and OpenKirin. And 6 "different" ROMs that all work the same, with the exception off the nougat FOMs, which have even more bugs.
lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
I don't think that...I'm a kid...I make my own roms with my tree...:angel:
haky 86 said:
I don't think that...I'm a kid...I make my own roms with my tree...:angel:
Click to expand...
Click to collapse
I know man, I wasn't talking about you. I was talking in general. I know you're doing god work, despite I'm not developing anything since a long time I still read forum and follow what's happening.
Like @Vinnipinni said, 2 guys and 6 "different" roms. But all working the same.
Back in times people were more likely waiting for stable CM/AOSP before compiling bunch of other distros. Now it's just mess.
I really wish I could go back to developing for android devices, especially now when I have programming knowledge and experience.
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
androiddev - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
CessnaBroon said:
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
klimtwifi - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
Click to expand...
Click to collapse
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
prkfsz said:
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
Click to expand...
Click to collapse
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
CessnaBroon said:
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
Click to expand...
Click to collapse
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
prkfsz said:
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
Click to expand...
Click to collapse
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
CessnaBroon said:
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
Click to expand...
Click to collapse
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
prkfsz said:
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
Click to expand...
Click to collapse
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
CessnaBroon said:
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
Click to expand...
Click to collapse
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
prkfsz said:
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
Click to expand...
Click to collapse
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
CessnaBroon said:
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
Click to expand...
Click to collapse
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
prkfsz said:
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
Click to expand...
Click to collapse
This should work on stock marshmallow too. I will give it a go and get back to you.
Thank you kindly!
lafinjack said:
Thank you kindly!
Click to expand...
Click to collapse
You're very welcome!
CessnaBroon said:
This should work on stock marshmallow too. I will give it a go and get back to you.
Click to expand...
Click to collapse
Sorry for delay in answering..
Unfortunatelly the error is still present. Like i said, probably a software issue.
Bit thanx anuway!
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey there! I'll take a closer look once I'm home. Speak to you then
darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
CessnaBroon said:
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
Click to expand...
Click to collapse
Just an FYI...I was reluctant to start everything over again with Odin and latest Samsung firmware, so I opted to take a chance and merely 'adb push' the LineageOS and GApps that you have on your Google drive (along with some cache erasures as you suggested) and everything seemed to upgrade properly from Resurrection Remix to LineageOS 17.1
A few minor problems so far: camera doesn't work, and initial signon to the tablet with a PIN doesn't work so well (seems to take multiple attempts). In any case, now running Android 10!
These were issues that I faced too - I never found a way to fix them. Neither did the original Dev, but apparently updating to the latest webview fixes chrome crashes. PIN you need to wait 30seconds after boot. Camera works only with clean install and even then sometimes doesn't work.
Hope this helps,
Cessna
I was trying to install TWRP but after reboot when I go to the Recovery mode there is no TWRP. I installed the LOS on my Tab Pro 8.4 and wanted to install LOS on Tab S 8.4 but can't flash the TWRP. Any ideas what I'm doing wrong?
Thanks