Related
I am having anissue...sch-1535...d2vzw....whatever it needs to be called...running du_d2vzw_2013-10-14
Was attempting to backup everything with TiBu...... (was sooo pumped to flash KitKang, been running Dirty Unicorn 4.3.1 for about a week; loved it, just relatively new to all of this, only had a gs3 since September... so proverbial noob, although not naive...)..... upgraded to TiBu Pro when it said I did not have enough free storage available to batch backup apps/system data... which of course was bogus. Checked the forums and tried to update SuperSU permissions, was redirected to Playstore for some sort of update; next thing I know, this bad boy is briefly rebooted into recovery and now.....alas, I evidently no longer have root permissions............?????....!!!????asdfasf asfgawo asfasgh
I would really appreciate some help; I have already tried to flash SuperSU update or whatever; I have also even tried to (re?)root with Casual (which is what I used the first and only other time I rooted my phone to flash JellyBeans b_19 a few weeks after I got the phone for $0.97 at wally world) and that did not work...
I am completely cool at this point with doing a factory wipe and flashing from scratch, I just don't want to do that yet because I lack the confidence in myself. I feel like I have learned about as much as I could have in the past couple months, and while this site is incredible, there seems to be a lot of cooks in the kitchen telling me 9 ways to skin a cat (to no fault of their own... if anything it's on me for being ill-equip to decipher and filter the signals through the noise...) and I could realllly use a helping hand here.
I'd like to end this saga with first an apology; my rambling is probably adding unneeded information and leaving out more vital details that would better help my future hero, and for that I am sorry and appreciate your patience.... and secondly, I would like to thank everyone who is involved with the development, maintenance, and everything else Android... you fellas are brilliant, and it is not enough to thank you for facilitating me with a hobby/passion, however new and freshly planted this obsession of mine may be; THANK YOU!!!!!!!!!!
sammymcalaxy said:
I am having anissue...sch-1535...d2vzw....whatever it needs to be called...running du_d2vzw_2013-10-14
Was attempdecipher and filter the signals through the noise...) and I could realllly use a helping hand here.
I'd like to end this saga with first an apology; my rambling is probably adding unneeded information and leaving out more vital details that would better help my future hero, and for that I am sorry and appreciate your patience.... and secondly, I would like to thank everyone who is involved with the development, maintenance, and everything else Android... you fellas are brilliant, and it is not enough to thank you for facilitating me with a hobby/passion, however new and freshly planted this obsession of mine may be; THANK YOU!!!!!!!!!!
Click to expand...
Click to collapse
Not sure what all you have done.
Proper way to fix in this case is probably to flash your same ROM again , just dirty flash it. If that doesn't work then try to settle a bit and explain in English clearly what you have done so far step by step. Or you can just go into recovery, wipe everything and flash your chosen ROM fresh.
Thanks for answering, Doc, and sorry for the inane illustration of immediately inept, irritatingly irrational, illusion-ed illiteracy I illustrated inside the earlier invoice.... I was flipping out because the last thing I want is a to deal with some bootloop.
It's the little things, evidently; I had thought I was flashing the most recent version of SuperSU: Wrong. Reflashed the newest update, cleared cache/dalvik... and now I am golden. Thank you sir.
While I am typing, would you or anyone have an opinion on the most "solid/functional/reliable/dependable" 4.3(+) ROM available? Like I said, I have been using Dirty Unicorns 4.3.1 and while it was almost excellent, I prefer to be able to utilize xposed or something similar for functions such as LMT, etc... thanks!
Try the instructions on this link.
http://forum.xda-developers.com/showthread.php?t=2525831&page=25
sammymcalaxy said:
Thanks for answering, Doc, and sorry for the inane illustration of immediately inept, irritatingly irrational, illusion-ed illiteracy I illustrated inside the earlier invoice.... I was flipping out because the last thing I want is a to deal with some bootloop.
It's the little things, evidently; I had thought I was flashing the most recent version of SuperSU: Wrong. Reflashed the newest update, cleared cache/dalvik... and now I am golden. Thank you sir.
While I am typing, would you or anyone have an opinion on the most "solid/functional/reliable/dependable" 4.3(+) ROM available? Like I said, I have been using Dirty Unicorns 4.3.1 and while it was almost excellent, I prefer to be able to utilize xposed or something similar for functions such as LMT, etc... thanks!
Click to expand...
Click to collapse
The most functional , stable , fully features ROMs for the Verizon S3 are the custom TW ROMs. . Lots of good ones, I have personally used Hyperdrive,, Synergy and Jelly "Beans" They are all great, each with a different mix of features and custom settings. "beans" release 20 is new this week and has the xposed framework.
Thanks! I got flash antsy and while I was looking at liquidsmooth 2.10, I noticed that 2.37 had just been posted no sooner than 3 hours before...to which I declared it fate and have been happily running that ever since. Very seldomly, it procures minor hiccups...but I love it. I have been reading a few things about beans_20 that have made me think I need to wait just a bit for all the kinks/fixes to be registered before diving in. I'd imagine that within a few weeks there will be some sort of 4.4 that can be a DD with enough customizable options to keep me busy...I'm hopefull anyway.
Seems like twrp, rooms etc are not really being developed. Anyone have any ideas on this?
Sent from my Nexus 5X using Tapatalk
stackz07 said:
Seems like twrp, rooms etc are not really being developed. Anyone have any ideas on this?
Click to expand...
Click to collapse
There are a few and the performance is good.
In terms of price, the pixel is pretty damn expensive compared to other android phones with similar specs. Add to that the fact that, in the USA, at least, it was nearly impossible to get one for the longest time and finally, the way the partitioning is set up is quite different that any previous android phones. All these make for some slow development.
It's expensive plus Google's security features are becoming more problematic. The newest bootloader is causing issues with root now.
The real dev device now is OnePlus not googles product anymore.
stackz07 said:
Seems like twrp, rooms etc are not really being developed. Anyone have any ideas on this?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Was actually my thinking also...
I came to the conclusion, that nobody has this device, and also google is making it hard to develop for the pixel. Working against the dev community with each update.
I am not worried though, because I only need root for my ARISE sound mod ,and backup/restore via Titanium Backup. I'm running completely stock, because that is the fastest, smoothest, most battery friendly setup I could find. Now that (even with a lot of hacking and manual adjustments) both TWRP and root works somehow, I am enjoying my pixel as it is... All these new things, like slots, loosing the recovery partition etc. make this device terrible for flashing. I was used to flashing my phones without a PC for 6-7 years now. I didn't even had to hook them up to the PC, only once, at first recovery flashing.... This is not the case with the pixel..
Maybe if the new partition layout gets picked up by other manufacturers, the problems will be solved quickly. Or even google drops this nonsense with the new pixels, and then we are really doooooomed
mikeprius said:
It's expensive plus Google's security features are becoming more problematic. The newest bootloader is causing issues with root now.
The real dev device now is OnePlus not googles product anymore.
Click to expand...
Click to collapse
Lol...OnePlus are unavailable to release nougat for the OnePlus 2 (SD810+4Gb Ram)
I don't really agree. The development took some time because of all the new features.
We are not really missing any roms, root, twrp or anything I want to be able to do. I see PN, DU, Lineage, OctOS, PixelDust, RR. I mean what other ones you want?
I'll get an OP when they decide to support their devices at least 2 years. They burned enough people with OP2.
milan187 said:
I don't really agree. The development took some time because of all the new features.
We are not really missing any roms, root, twrp or anything I want to be able to do. I see PN, DU, Lineage, OctOS, PixelDust, RR. I mean what other ones you want?
I'll get an OP when they decide to support their devices at least 2 years. They burned enough people with OP2.
Click to expand...
Click to collapse
Twrp seems abandoned, and the mix and match instructions for getting things to boot and run with magisk etc just seem odd, that's all. I'm sure everything will be figured out with time, but was just honestly curious.
stackz07 said:
Twrp seems abandoned, and the mix and match instructions for getting things to boot and run with magisk etc just seem odd, that's all. I'm sure everything will be figured out with time, but was just honestly curious.
Click to expand...
Click to collapse
Well the developer works on it when he can. It works fine so we do have it. Will need a new one that can sign the boot image.
Magisk isn't officially support it since developer does not have the device.
New boot signing procedure had a fix in a day or two after Google release. That's not bad. Things are not perfect I agree. Multiple slots are making things the hardest I think.
Sent from my Pixel using Tapatalk
Probably security more than anything. Don't expect it to pick up anytime soon.
Is there a technical reason that we have not seen any Custom Oreo roms released yet. I figured between all the RC releases of oreo leading up to the final build that the most popular roms (Pure Nexus, Resurrection Rom.. etc...) would have released 8.0 versions by now. Is it just too soon and unrealistic to expect that yet.. or an actual limitation in Oreo that is preventing builds? fyi.. im not like demanding one .. just curious on a technical level.
revdirty said:
Is there a technical reason that we have not seen any Custom Oreo roms released yet. I figured between all the RC releases of oreo leading up to the final build that the most popular roms (Pure Nexus, Resurrection Rom.. etc...) would have released 8.0 versions by now. Is it just too soon and unrealistic to expect that yet.. or an actual limitation in Oreo that is preventing builds? fyi.. im not like demanding one .. just curious on a technical level.
Click to expand...
Click to collapse
From my understanding, most devs don't work on betas but wait until a final build is published and this was supposedly a significant update to Android. Perhaps there's a lot to do to handle the project treble changes. XDA published an interesting article about it just today.
The pixel doesn't seem to be the super popular development device many expected it to be but I'm sure the Oreo builds will come soon enough.
Just from my point of view, finding the various aspects for my themes was a pain in the butt from N to O. Somethings that were once png are now vector images and that is just from a themers aspect,,,rom building is a whole other thing. I am sure there will be some soon.
I was thinking the exact same thing as OP. I hope this isn't the case for the Pixel 2 XL. My Nexus 6 is running a custom Oreo ROM and it's great so far. It's like a ghost town.
Hey guys, im currently using Pure nexus, i thought of waiting for the oreo version of pure nexus. But it seems like its gonna take a while.. So, shall i switch to official oreo or to wait for any custom rom?
How is battery life and performance in Oreo?.
Thanks in advance
Oreo appears buggy...
I will wait for Pure Nexus Oreo
udahy.manna said:
Hey guys, im currently using Pure nexus, i thought of waiting for the oreo version of pure nexus. But it seems like its gonna take a while.. So, shall i switch to official oreo or to wait for any custom rom?
How is battery life and performance in Oreo?.
Thanks in advance
Click to expand...
Click to collapse
I'm not going to say switch to Oreo, but for me it's been pretty stable. It's no RR or PA by a long shot. Battery life seems ok, and comparable to
other nougot roms I've ran. Performance is comparable as well. I'm no gamer, so can't report on heavy usage, but I've had no issues with
my standard apps, youtube, slack, twitter etc..
I guess the only thing I'm real annoyed at is if you want to get into TWRP, you have to reboot to bootloader, and fastboot boot twrp.img. I don't know the
status of flashing twrp, but the fastboot method works well.
Rooted with SuperSU, and substratum working nicely. I can't stand the default navbar height, so installed the mod from "[MODS] Pixel OREO Aroma Mods Installer" and lowed my navbar to 42dpi, and am now content.
Now, once a Oreo custom mod like RR/PA is released (Haven't tried Pure Nexus) I'm switching.
cntryby429 said:
From my understanding, most devs don't work on betas but wait until a final build is published and this was supposedly a significant update to Android. Perhaps there's a lot to do to handle the project treble changes. XDA published an interesting article about it just today.
The pixel doesn't seem to be the super popular development device many expected it to be but I'm sure the Oreo builds will come soon enough.
Click to expand...
Click to collapse
I was just about to ask about the "State of Development" on the Pixel because I have been curious as to the lack of active development for Mods and ROMs. Hell my Wife's old Samsung Galaxy S4 still gets more development.
Could the A\B partitioning be a big factor in this?
I thought the Pixel would receive the same reaction like th Galaxy line and Google is a recognizable just like Samsung
Why is custom ROM development on Pixel is very low?
hp13 said:
Why is custom ROM development on Pixel is very low?
Click to expand...
Click to collapse
Because it's an expensive device and it has this new crappy A/B partitions system
lorax70 said:
I'm not going to say switch to Oreo, but for me it's been pretty stable. It's no RR or PA by a long shot. Battery life seems ok, and comparable to
other nougot roms I've ran. Performance is comparable as well. I'm no gamer, so can't report on heavy usage, but I've had no issues with
my standard apps, youtube, slack, twitter etc..
I guess the only thing I'm real annoyed at is if you want to get into TWRP, you have to reboot to bootloader, and fastboot boot twrp.img. I don't know the
status of flashing twrp, but the fastboot method works well.
Rooted with SuperSU, and substratum working nicely. I can't stand the default navbar height, so installed the mod from "[MODS] Pixel OREO Aroma Mods Installer" and lowed my navbar to 42dpi, and am now content.
Now, once a Oreo custom mod like RR/PA is released (Haven't tried Pure Nexus) I'm switching.
Click to expand...
Click to collapse
The new official flashable TWRP is out and compatible with pixel Oreo.
yeah, I would give "O" a little time. It appears that some are starting to have a few issues with phones being bricked. It's possible that one of the 3 is not related, but certainly my advice would be to wait folks. This could be related directly to branded phones, but not exactly sure and would only be speculation at this point. It's possible the DEV's are waiting on a few areas...
https://forum.xda-developers.com/pixel/help/pixel-bricked-overnight-t3681377
https://forum.xda-developers.com/pixel/help/google-pixel-bricked-oreo-twice-ideas-t3671302
dantexaiver said:
I was just about to ask about the "State of Development" on the Pixel because I have been curious as to the lack of active development for Mods and ROMs. Hell my Wife's old Samsung Galaxy S4 still gets more development.
Could the A\B partitioning be a big factor in this?
I thought the Pixel would receive the same reaction like th Galaxy line and Google is a recognizable just like Samsung
Click to expand...
Click to collapse
The dual partition s is the reason. It makes developing roms a real pain. Developers have now added a dual partition setup to the list of things to avoid when getting devices.
I am usually a real patient guy, but I have to tell you, I am so over stock. I would never be rude enough to ask for an ETA, but cmon gentleman, I'm dieing here. Lol
Golf c said:
I am usually a real patient guy, but I have to tell you, I am so over stock. I would never be rude enough to ask for an ETA, but cmon gentleman, I'm dieing here. Lol
Click to expand...
Click to collapse
Flash back to a nougat custom rom. Problem solved.
mitchdickson said:
Flash back to a nougat custom rom. Problem solved.
Click to expand...
Click to collapse
Haha, not quite.
Recently got a pixel after years of sony phones and am awaiting some Oreo custom roms. It's great I'm getting the latest OS updates straight away but the downside I guess is the newness means custom roms take longer. Now there's a working TWRP I'm hopeful we'll start to see custom Oreo roms appearing.
zelendel said:
The dual partition s is the reason. It makes developing roms a real pain. Developers have now added a dual partition setup to the list of things to avoid when getting devices.
Click to expand...
Click to collapse
citation, please?
that seems a bit silly, because A/B partitions are the new standard. it won't just be Google phones using it... plus, there are non stock ROMs that have made the jump to A/B.... lots of app devs have too....
Frankly, while it may add some complexity, it is far better for upgrades over OTA and makes total sense that it would be the next iteration for rolling out upgrades.
nine7nine said:
citation, please?
that seems a bit silly, because A/B partitions are the new standard. it won't just be Google phones using it... plus, there are non stock ROMs that have made the jump to A/B.... lots of app devs have too....
Frankly, while it may add some complexity, it is far better for upgrades over OTA and makes total sense that it would be the next iteration for rolling out upgrades.
Click to expand...
Click to collapse
It is the standard for Google device. Notice how only Google devices use it?
They are great if you stay stock. But not for rom development. As for your citation, you would have to talk to developers about it.
It is coming to the point that people will have to choice. Ota updates from Google or custom roms. Not gonna get both
A/b partition will be like many things gs that Google added that oem remove. Like adaptable storage.
zelendel said:
It is the standard for Google device. Notice how only Google devices use it?
Click to expand...
Click to collapse
Motorola has been testing it, including a device that utilizes it now. Same goes with Xaoimi... Furthermore, a/b partition is a part of AOSP... Oreo devices going forward will be making use of Project Treble and I suspect in the next year, you are going to see more vendors adopting the new partition scheme.
On top of that, all new mediatek and Qualcomm SOCs will support A/b partition schemes.
https://www.xda-developers.com/xiaomi-mi-a1-android-ab-partition/
https://www.xda-developers.com/moto-z2-force-ab-seamless-updates/
https://review.lineageos.org/#/c/156378/
https://source.android.com/devices/tech/ota/ab_updates
zelendel said:
They are great if you stay stock. But not for rom development. As for your citation, you would have to talk to developers about it.
Click to expand...
Click to collapse
Um, no. it's perfectly reasonable for an end use running a custom ROM to want/expect OTA upgrades that uses seamless updating, where supported.... I've been involved in ROM development, in the past. thanks.... for someone developing a ROM; ya, you will be flashing your custom builds, but for an end user not building from AOSP, lineageOS repositories; OTA is far bore reasonable...
zelendel said:
It is coming to the point that people will have to choice. Ota updates from Google or custom roms. Not gonna get both
Click to expand...
Click to collapse
lol. that comment makes zero sense, given the context... It's always been the case (for stock vs. custom roms) that you will be getting updates from one or the other, not both...
zelendel said:
IA/b partition will be like many things gs that Google added that oem remove. Like adaptable storage.
Click to expand...
Click to collapse
We will see, but given that Qualcomm and mediatek will be supporting it going forward and the revelations and direction of Project treble && VTS; I suspect that a/b partitions will become the norm...
the only question is what will Samsung do for future devices, since they unlike most vendors produce their own SOCs/Exynos boards.... I guess we will see when the next galaxy line is released.
Hello everybody!
I'm Martin and looking for a helping hand with my OnePlus One. Which is actually my first smartphone ever. That should tell you how experienced I am in flashing ROMs. I got it early 2015 and as big brother was bothering me I rooted it instantly to have AFWall+ and AdAway installed. Rooting my phone really made me sweat because I feared I might brick the thing. So when an CyanogenMod update killed my root a few days later and I had to redo the whole procedure, I decided to stay away from future updates so as not to take any further risk of losing my root again. Which means I'm still running on CM 11.0-XNPH05Q.
This worked fine for me for years but with 2020 rolling in I can't deny anymore that there's hardly an app left that I can install in its most recent version. There's also a rising number of apps I can't even install at all. So unfortunately I cannot ignore the situation no more. As CM is dead I considered buying a new phone. But I'd really like to avoid that as long as possible because my OPO is of great non-material value to me. On the net I learned about the successor Lineage OS which I tried to flash last weekend. Well, I failed miserably. Furthermore I have no idea what "error 7" should tell me. This is what I did:
1. Updated the Recovery successfully to TWRP 3.3.1-0 => reboot
2. Created a backup of my existing CM Boot, System & Data
3. Wiped Dalvik, System, Data & Cache => reboot
4. Attempted to install the ROM but got an error 7 instead; I tried several times but to no avail
I doubt that I have accidently downloaded a wrong ROM or wrong Recovery. All of them are marked as suitable for bacon. But then again who am I to rule that out. So if error 7 means exactly that just let me know.
To make my OPO operate again I restored the backup. It did work but for now I'm stuck. I'm aware of the fact that I'm probably the wrong guy in the wrong place here as I'm neither a developer nor a flashaholic. But I really don't know anybody else I could ask. So if you have any idea at what point I messed things up I kindly ask you to drop me a line. Any help is appreciated!
If you don't mind I'd also like to use the opportunity to address another question. I'm wondering what the best ROM for my OPO might be. I understand the overall attitude on this platform that there really is no best ROM for all of us. Probably true, but there is certainly one for me. I'm worried that I might experience problems with LOS 16 as the team is still banging out nightly builds almost every day. What I am looking for is a ROM for daily use. So it needs to be
- absolutely stable
- responsive
- battery-friendly
I also expect all the built-in technology like camera, flashlight, bluetooth, WLAN etc. to work properly. Nothing fancy, just something that turns my OPO back into a sturdy tool I can rely on. If that means to flash a ROM with an outdated version of android then so be it. I can't afford to miss the call to pick up my baby girl from kindergarten or lose a precious moment with her because the signal isn't stable or the camera doesn't work. So should I stick with LOS 16 or do you have better recommendations?
Did you did a manual wipe of /system before installing the ROM? Maybe your data was encrypted? Then you'll have to format full data.
Or maybe you don't have the least of free space in your data partition? Maybe?
Anyway, all roms are good, some people has LOS with more battery useage than other AOSP ROMs, other peoples don't.
Just try, there's a lot & lot more of ROMs out there.
Hi all,
i own a Tab S6 T860 (non-lte) for quite a while now, about 6 months.
There are some downsides like the horrible unbuffered screen tearing that you'll get with fast-scrolling, but the overall device is pretty premium-sided, and it's got a decent processor, a great display (color/resolution wise) although im missing 2160p in youtube.
Question is as i (until now) didnt bothered developing for a new device, since i had my hands full with the MiPad4, some alcatel devices and are Maintaining official LineageOS for three legacy devices, should i develop for this one if the community still wants it.
The lead-dev of the MiPad left it so im thinking about developing for the Tab S6 now.
I would only develop LineageOS, starting with 16.0 then doing 17.1 and then 18 but idk how long it would take, since ive no real knowledge of the newest platforms and how they are built, so i'd be reading/trying out stuff a LOT before some release nightlies. The "latest" i developed for was the MiPad4 with a sdm660 btw but i mainly do legacy (e.g 8953/8952/8926).
So please leave your feedback or any other opinions/questions, if we reach a decent amount of people who still want it i'll start right away when im back home from my vacations on 18th.
Best Regards!
Edit: Since theres no real telegram group, and i MAINLY talk via telegram i made one so you can contact me quickly.
https://t.me/joinchat/Bn6f-VKeQfZfiKXo69h3Mw
#reserved 1
I would LOVE to have LOS on my Tab S6 (SM-T860) WiFi-only tablet!
Don't even care about stuff like fingerprint, external keyboard, Widevine, Bluetooth, any 'functionality' similar to what Samsung 'provides' like, you name it.
I've spent sooo much time, and a few dollars, trying to get preinstalled stuff to *not* work! but still be able to boot—Knox bull****, anyone?
And having telephony **** on my WiFi-only tablet, either. Something that has baffled me for years is why a 'custom' ROM for a Wifi-only device has software that trys to interact with nonexistent hardware, using up cpu as it continually tries...on a bit of a rant, there.
So yeah, I'm all in. FWIW, I helped write the instructions, and did a *lot* of testing for rooting the Tab S5e, so I ain't scared to test out stuff; check it out, here:
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
TiTiB said:
I would LOVE to have LOS on my Tab S6 (SM-T860) WiFi-only tablet!
Don't even care about stuff like fingerprint, external keyboard, Widevine, Bluetooth, any 'functionality' similar to what Samsung 'provides' like, you name it.
I've spent sooo much time, and a few dollars, trying to get preinstalled stuff to *not* work! but still be able to boot—Knox bull****, anyone?
And having telephony **** on my WiFi-only tablet, either. Something that has baffled me for years is why a 'custom' ROM for a Wifi-only device has software that trys to interact with nonexistent hardware, using up cpu as it continually tries...on a bit of a rant, there.
So yeah, I'm all in. FWIW, I helped write the instructions, and did a *lot* of testing for rooting the Tab S5e, so I ain't scared to test out stuff; check it out, here:
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
Click to expand...
Click to collapse
Thanks for the info about the S5e, i was unaware of how well it is supported.
I would definitely do stuff like fingerprint, widevine, Bluetooth (PEN) and stuff.
But idk about those keyboards samsung offers and how they function since i cant test it on my own.
Same goes for the LTE but im pretty sure i can just use the same blobs.
BTW anyone has a firehose package for the tab s6 by chance???
I too would love LOS in this device. Samsung UI is cluttery, lagging (on mine), and an absolute mess. My PocoF1 gives me better Honkai Impact 3 (a gatcha action fighting game) performance than this tablet, and the poco is an SD845, with lite LOS. So yeah, I'd love to have this. My warranty is void anyways (because samsung decided so I haven't done a thing to void it), so it'd be great to have a reason to take advantage of that.
Chiming in for a plea to get a Lineage build for the Tab S6.
Such a gorgeous piece of hardware beset by such a ****ty software implementation. Why does Samsung insist on abusing its customers? I'd gladly pay for a Lineage or AOSP rom for our device.
Alright, a little update:
Kernel is done -> link found below
It has to be handled with care as of now. Installing it on my running rom resulted in a crash when unlocking the device. A quick factory reset fixed the problem but keep that in mind when installing this on your device.
Rom will follow up hopefully till next month - but i cant promise anything.
T-860:
https://dl.keksla.wtf/boot_t860.img
T-865:
(uploading)
Thargorsson said:
Alright, a little update:
Kernel is done -> link found below
It has to be handled with care as of now. Installing it on my running rom resulted in a crash when unlocking the device. A quick factory reset fixed the problem but keep that in mind when installing this on your device.
Rom will follow up hopefully till next month - but i cant promise anything.
T-860:
https://dl.keksla.wtf/boot_t860.img
T-865:
(uploading)
Click to expand...
Click to collapse
i would love to have custom kernel for samsung rom, but i don mind if you can make enhancements to the kernel like under volt or to solve the graphics lagging issues. it was just tiny changes involved in the past to make it work for both stock and LineageOS but for android 10, i have no idea
i have long inactive in both rom and kernel developments and i doubt how long should it take to get familiar with changes from android 7 to 10
ps i am still on pie, too lazy to upgrade due to my csc is tgy, which lacks updates as usual, and i dont wanna reinstall everything as to switch to dbt and to re-enter all my passwords
btw, may i ask if the stock android 10 fixed the problem with fast scrolling? i have experiences lags and graphics distortions with the samsung browser which was way toooooo unacceptable for a top device like tab s6
ykkfive said:
i would love to have custom kernel for samsung rom, but i don mind if you can make enhancements to the kernel like under volt or to solve the graphics lagging issues. it was just tiny changes involved in the past to make it work for both stock and LineageOS but for android 10, i have no idea
i have long inactive in both rom and kernel developments and i doubt how long should it take to get familiar with changes from android 7 to 10
ps i am still on pie, too lazy to upgrade due to my csc is tgy, which lacks updates as usual, and i dont wanna reinstall everything as to switch to dbt and to re-enter all my passwords
btw, may i ask if the stock android 10 fixed the problem with fast scrolling? i have experiences lags and graphics distortions with the samsung browser which was way toooooo unacceptable for a top device like tab s6
Click to expand...
Click to collapse
nope, sadly we still suffer from those issues on Q .
I dont have any good knowledge of how to apply those undervolts as i never done it before (lineageos requires stock govenors for official) but if you can point me to the correct commits i can look at it
Thargorsson said:
nope, sadly we still suffer from those issues on Q .
I dont have any good knowledge of how to apply those undervolts as i never done it before (lineageos requires stock govenors for official) but if you can point me to the correct commits i can look at it
Click to expand...
Click to collapse
oh...
there were some cpu/voltage tweaks for the same cpu before for my old devices. and for our tab s 6 there are a few devices with the same cpu like one plus. you can search the cpu model in github and then you can find the code name of it and those devices which use the same cpu. i used to get those tweaks for modifying kernels for my previous devices. however for our 855, sadly there's no port for the samsung devices afaik, so you may need to make some more changes in order to port them
---------- Post added at 05:54 ---------- Previous post was at 05:35 ----------
just found this one https://github.com/kdrag0n/proton_bluecross/releases
it should be a 855 with some oc according to the change log, but unfortunately i couldnt load the changes with my browser so i couldnt find the relevant commits
may be you can take a look at that
Thargorsson said:
Hi all,
i own a Tab S6 T860 (non-lte) for quite a while now, about 6 months.
There are some downsides like the horrible unbuffered screen tearing that you'll get with fast-scrolling, but the overall device is pretty premium-sided, and it's got a decent processor, a great display (color/resolution wise) although im missing 2160p in youtube.
Question is as i (until now) didnt bothered developing for a new device, since i had my hands full with the MiPad4, some alcatel devices and are Maintaining official LineageOS for three legacy devices, should i develop for this one if the community still wants it.
The lead-dev of the MiPad left it so im thinking about developing for the Tab S6 now.
I would only develop LineageOS, starting with 16.0 then doing 17.1 and then 18 but idk how long it would take, since ive no real knowledge of the newest platforms and how they are built, so i'd be reading/trying out stuff a LOT before some release nightlies. The "latest" i developed for was the MiPad4 with a sdm660 btw but i mainly do legacy (e.g 8953/8952/8926).
So please leave your feedback or any other opinions/questions, if we reach a decent amount of people who still want it i'll start right away when im back home from my vacations on 18th.
Best Regards!
Edit: Since theres no real telegram group, and i MAINLY talk via telegram i made one so you can contact me quickly.
https://t.me/joinchat/Bn6f-VKeQfZfiKXo69h3Mw
Click to expand...
Click to collapse
I'm in at 17.1 level and up. Don't want to go back...
YES! Yes please please please! I have been dreaming and hoping LOS would come to the Tab S6 for SO long now. So yes, please make a rom for it. Please.
I would love to have LOS rom support on the Tab S6! The lack of Lineage OS support was the one thing holding me back from purchasing the Tab S6, compared to the Tab S5E, but I wanted the faster processor, storage, and larger memory capacity.
That said, if you develop a working LOS rom, that would be a huge win for all Tab S6 users!
I don't think there is a person on XDA with the tab S6 that would not want to see a custom lineage Rom built. I do want a working Spen though. Im on stock 10 One UI 2.5 and samsung is extremely slow at releasing the kernel source code for the 860. Its definitely worth it to use to build one if you can. Thanks for developing on the tab S6.
LOS for T-865 ?! Yes, absolutely
P.S: Working pen would be great of course.
Still On The Fence.
lucgardos said:
LOS for T-865 ?! Yes, absolutely
P.S: Working pen would be great of course.
Click to expand...
Click to collapse
I would support a ROM for this device, but I am leery about past issues and previous devices. I had 3 smp600 units, and all three were beaten to the edge with constant testing of all the ROMS I could grab. But, only ONE of those tabs choked on something from a pure LOS build. Then it hit a brick wall. I could never find a way past a Nov 18 build. So, now with two smt870 units, I will tread lightly. And, big question: WHY are we STILL stuck with ODIN for this process? I know nothing of the process of coding and writing these great ROMS, but having to drag out a WINDOWS laptop to update my android device seems like many steps backwards. I have no NEED for a laptop save for praying for Odin to even run properly. Wish there were better ways for us old farts who've forgotten more tricks than new ones have been taught. But, I am on board to get the Sammy off of my tab. Thanks for your errors.
;-DeanoD
DeanoD said:
I would support a ROM for this device, but I am leery about past issues and previous devices. I had 3 smp600 units, and all three were beaten to the edge with constant testing of all the ROMS I could grab. But, only ONE of those tabs choked on something from a pure LOS build. Then it hit a brick wall. I could never find a way past a Nov 18 build. So, now with two smt870 units, I will tread lightly. And, big question: WHY are we STILL stuck with ODIN for this process? I know nothing of the process of coding and writing these great ROMS, but having to drag out a WINDOWS laptop to update my android device seems like many steps backwards. I have no NEED for a laptop save for praying for Odin to even run properly. Wish there were better ways for us old farts who've forgotten more tricks than new ones have been taught. But, I am on board to get the Sammy off of my tab. Thanks for your errors.
;-DeanoD
Click to expand...
Click to collapse
Well if your not rooted you dont need odin you can install official release update. If you mean to install custom rom like lineage you again dont need odin after you install TWRP.
Actually, on debloated rooted stock ROM I don't see any problems so far..Device is holding it solid and sound.
Flavour of Lineage is absolutely welcome, but personaly I wouldn't use it because a lot of bugs and non functional addons.
Personally...this tablet without pen is like Ferrari without fuel.
Rooted debloated stock is miles ahead of Samsung's incompetent shadow apps. But even as stripped down as I can make it, the ROM still lags and burns battery in the background. I've tried everything and can't get this beautiful expensive piece of hardware to perform to its specs. I respect others who love it as is, but I've never gotten comfortable with the pen and just want a light, fast tablet with a beautiful screen that doesn't overtax its battery.
I'd switch to Lineage on this device in a heartbeat.
this project still alive? seems dead for me.