Related
First question does Osprey's hardware support Android O ?
Prob does but we'll prob not be able to have some features
Osprey's hardware didn't supported android N too but we got it with custom rom... I think this will happened with android O too
Our device is in list to get los 15 ie. android O
androidbaba said:
Our device is in list to get los 15 ie. android O
Click to expand...
Click to collapse
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
adityak1303 said:
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
Click to expand...
Click to collapse
Just for fyi, lineageosdownloads.com is not the official site (download links are redirected to actual linageos.org (org, not com)). So information they give cannot be verified unless the official linageos blog posts something about it.
It's still a long way. Source code hasn't been out yet. After AOSP code is pushed, linageos team will work on it, but considering the limited resources (unlike CyanogenMod), it can take a while. After the base is ready, then devs will focus on building device specific images and fix bugs. Only then android o will be roaster ready. Other derivative ROMs will take more time obviously.
We can't be sure if 8.0 will be fully compatible with our device. We don't have official Nougat kernel sources and proprietary blobs (AFAIK), also from what I've observed so far, the farther apart the last official firmware and target firmware are, the harder it is to keep a ROM unmodified and yet stable & functional.
Our device shouldn't die that easy though, as newer Moto devices with similar hardware as osprey and Merlin have been released.
Broadcasted from Zeta Reticuli
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Hopefully we get O, and hopefully O comes default with the pixel nav because redacting that would take effort thats not worth it now that nexus is dead .
Nikos dima said:
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Click to expand...
Click to collapse
Our device does support Nougat, it is evident by the presence of custom ROMs (and even a stock port). The only reason we didn't get a OTA was because the company didn't provide us. The Moto ROM and these custom ROMs all are based on AOSP code.( Technically, if the company released the full source of their ROM and features, then we could build stock ROMs too)
And yes, you are right, it may take a little while but eventually we should see the ROMs coming
But the absence of latest device specific proprietary stuff and official kernel sources forces devs to look for other branches to fill the gaps and get newer thingies working. In some places it's not possible to implement a certain feature and an older feature is modded to make it work, for example before the official marshmallow OTA was out, we already got marshmallow ROMs but it had some hacky workarounds for radio (I don't know if it was updated after that), same goes for early Nougat when camera was becoming a problem. The camera is still not perfect (check linageos thread), working correctly on some apps and glitching on others. Newer software, newer challenges.
But codes are not exactly like food though, mixture of old and new ones is not always bad. But the blobs and drivers sometime give headache
Broadcasted from Zeta Reticuli
Have faith on our awsome developer we will surely have android O
Well, Android Oreo is out. I really hope that Osprey will get it soon.
https://source.android.com/devices/architecture/treble
according to this website,
"With Treble, a new stable vendor interface provides access to the hardware-specific parts of Android, enabling device makers to deliver new Android releases simply by updating the Android OS framework—without any additional work required from the silicon manufacturers"
Does this mean if someone gets Lineage OS 15 or OTA of Stock Android 8.0, they will receive all the updates from google from security patch to new Android versions (If the hardware is capable of running that version obviously!)?
---------- Post added at 09:47 AM ---------- Previous post was at 09:46 AM ----------
If that so, Manufacturers can just update all the devices which theoretically can run android O , it will be a onetime work, after that it'll be easy to update the devices
That would be amazing. Let's wait for a developer opinion.
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
android1111 said:
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
Click to expand...
Click to collapse
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
adityak1303 said:
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
Click to expand...
Click to collapse
Wow.. nice to hear this.. dude how do you know about this
rahul9999 said:
Wow.. nice to hear this.. dude how do you know about this
Click to expand...
Click to collapse
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
adityak1303 said:
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
Click to expand...
Click to collapse
Thanks For the information
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Abhishek17599 said:
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Click to expand...
Click to collapse
Hello,
There is no confirmation yet about this from official maintainer
Yes it should be get as Osprey already successfully booted it.. but don't ask for ETA
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
https://developer.sony.com/develop/open-devices/
Unified 4.4 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Bug tracker
https://github.com/sonyxperiadev/bug_tracker/issues
Now you can build the latest Android with the latest 4.4 kernel
jerpelea said:
Now you can build the latest Android with the latest 4.4 kernel
Click to expand...
Click to collapse
Does it also mean that the official firmware from Sony will be updated with this new kernel?
I am not a developer but built it following the guide using the sources since a few months back. Boots and runs. Even used it for a time. But couldn't get fingerprint sensor to work properly. When I used 8.0 branch it was working but very slow and roughly. (Nowhere near the sensitivity of the stock rom) now with 8.1 branch can't get it register fingerprints. Sensor works, starts enrollment and progresses, but at the last step it gives error. However seems like more sensitive and faster than before. Another problem is the battery drain when idle. When using the phone daily routine not that bad, slightly less screen on time compared to stock but the real problem idle battery drain. %15-20 in 6-7 hours. According to battery starts appears to be related to Google play services which is always a serious battery killer for custom roms for years. Other than these did not notice any serious problems. And all this without any changes or tweaks. Straight from the source. Good job Sony imo.
@maluus Don't know if this also applies to compiling roms, but Sony just (march 8) released a new version (v11) of the odm image, which solves fingerprint enrollment issues you seem to describe for the omnirom 8.1 build:
https://developer.sony.com/file/dow...es-for-aosp-oreo-android-8-1-kernel-4-4-loire
Yeah heard of it. I was using v10 oem image last time. When i get back to home I'll try with v11 and will see if fingerprint issue is solved. If it's ok i can use it as daily as it is. If battery drain problem is solved too it will be pretty much everything i expect.
Vendor v11 is out
https://developer.sony.com/develop/open-devices/latest-updates
battery drain is fixed and new kernel binary will be released today
FM-radio will work someday on kugo in custom roms?
Anyone tried a recent aosp build with v11 binaries yet? Does fingerprint works correctly and accurately? How is the battery life compared to the stock? What is screen on time?
Just installed an AOSP build from March 15th together with v11 binaries and Micro GApps. Fingerprint is working.
And the battery life? I'm home though. I'll be building soon ?
droncheg said:
FM-radio will work someday on kugo in custom roms?
Click to expand...
Click to collapse
for the Open Devices project
in Android 7.x the FM Radio is enabled
in Android 8.x the FM Radio is disabled
Regards
J
For user security dm-verity and File Based Encryption are enabled by default
Please disable them only if you are developing new features
Regards
J
@jerpelea
Will the Sony Xperia XZ2 be added?
MartinX3 said:
@jerpelea
Will the Sony Xperia XZ2 be added?
Click to expand...
Click to collapse
we are finalizing the last steps before adding it
Regards
J
All build guides are updated with the Security updates
https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
Here is the list of all known bugs. If you find bugs you can always open a ticket in the bug tracker and we will check it ASAP.
https://github.com/sonyxperiadev/bug_tracker/issues
@jerpelea, do you know if there is a modem binary file for this phone that's compatible with T-Mobile VoLTE in the US? The XZ1C has a compatible file (amss_fsg_lilac_tmobile_us_ims_tar.mbn). The stock ROM doesn't, but I'm trying to get VoLTE working and this file would certainly help (if it exists).
Last night I built again. First thing I noticed is how well fingerprint reader works. It's like stock. Congrats to the devs for good job. Camera including video recording and Bluetooth works. But camera seems 1-2 mm smal from sides. Charging issue persists. As Harry pointed 3 amp chargers doesn't work. I tried 2 other chargers. 2.1 amp charger work normally. But 1 amp charger starts do disconnect and connect again after 43-44%. (I'll share the logs with devs) Another problem I noticed is that I can't root with magisk. Tried ver 16, 17 and 18. I can flash from twrp without error but when the device boot up neither Magisk manager is installed nor device is rooted. I did not try with supersu. Another thing to mention is that device boots up pretty slow. Boot crash still happens sporadically.
PS: Supersu works. Sometimes device lags heavily. I noticed especially on chrome and some banking apps.
PS 2: Sharing logs. (Includes 3 amp charging attempt and 2.1 amp charging)
little off, very very basic question, and I could not seem to find the answer.
I understand how to set up a build environment and build an image to the phone, but how about the developer.sony.com latest section binaries?
are they already built images? how will it be different if I build mine following the instructions?
Cheers,
You'll build rom first then you still need to flash that binaries too. They are not alternatives to your home build rom. They are part of the os which you won't be able to homebrew, for your device to work properly.
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
GuyInDogSuit said:
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
Click to expand...
Click to collapse
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
I wouldn't mind even if the best ROM available is a 6.0 Marshmallow one. Anything that gives AOSP on a stable base for the Fire HD10 is going to be awesome.
DragonFire1024 said:
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Click to expand...
Click to collapse
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
They will likely need some patches to work with newer versions, but it's a good start I'd say.
It's the most recent version amazon has published.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Sent from my MotoG3 using XDA Labs
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
The one I have and provided is a source to 7.0. looks nicely stocked.
Sent from my MotoG3 using XDA Labs
bibikalka said:
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
Click to expand...
Click to collapse
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
I have fixed the upload, please use amonet-suez-v1.1.1.zip
DragonFire1024 said:
The one I have and provided is a source to 7.0. looks nicely stocked.
Click to expand...
Click to collapse
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
k4y0z said:
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
I have fixed the upload, please use amonet-suez-v1.1.1.zip
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
Click to expand...
Click to collapse
I'll provide a link in a few. Trying your fix now.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Rortiz2 said:
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
Click to expand...
Click to collapse
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
bibikalka said:
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
Click to expand...
Click to collapse
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
This is great news! I am eagerly awaiting more info about this AOSP ROM
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
ffstudios said:
This is great news! I am eagerly awaiting more info about this AOSP ROM
Click to expand...
Click to collapse
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
bibikalka said:
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
Click to expand...
Click to collapse
If my testing on ROMs caused my brick, we have to be careful. I've been testing and flashing test ROMs for months now and never bricked like this. I think I may know what happened and if I'm right, I'm not sure what effect if any this will have on flashing a rom. According to the fstab.mt8173 file in the root directory, the partitions we flash for a rom, aren't part of the EMMC: data, system, cache are all ext4. All other partitions are however EMMC. So if I recall correctly, I did list the system as EMMC in the build script, but did intend to remove it. I made a last minute adjustment to the script and didn't change that part though.
https://forum.xda-developers.com/showpost.php?p=78542898&postcount=618
Sent from my MotoG3 using XDA Labs
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
I too am willing to test. Just let me know and I'll be sure to wear my best testing pants. [emoji41]
Sent from my SM-G9650/DS running stang5litre Pie ROM
AOSP ROM TEST 1 (suez)
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: Removed
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Click to expand...
Click to collapse
Sounds good to me. Won't have a chance till later this afternoon/evening to give it a whirl, but when I do I'll definitely share my results and any information that may be useful. Thank you!
Sent from my SM-G9650/DS running stang5litre Pie ROM
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
...
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Click to expand...
Click to collapse
Which AOSP version is this? Could you try that Oreo Lineage stuff from @wangyiling at some point as well?
One of these days we'll have a ROM developer and a tester within the same person Too bad we've lost @DragonFire1024 since his tablet got bricked
Support for the official LineageOS ROM has ended, so I sync'd the latest tree and built an update. Since I went through the effort of building, I figured I'd share in case anybody else still found it useful.
Build utilizes current, official LineageOS tree.
Tested SAT on a US model with b12 firmware with OpenGapps arm64 7.1 mini & Magisk.
Download:
ROM - https://www.androidfilehost.com/?w=files&flid=296768 dtd 2020MAR18
Follow install instructions in the official thread. Also, you should use Bigfoot29's build in the official thread. I'm not a developer and am just doing this for fun.
Sources
ROM - https://github.com/LineageOS/android.git -b cm-14.1
Device Tree
Kernel
I posted an update dtd 2020AUG31.
https://www.androidfilehost.com/?fid=8889791610682926612
I posted an update dtd 2020AUG31.
https://www.androidfilehost.com/?fid=8889791610682926612
Nice
Enviado desde mi HTC U11 life mediante Tapatalk
Hi! It's nice to have more ppl who build themselves.
I am still using the official thread. I am doing this for a couple of months now as you can see there: https://forum.xda-developers.com/showpost.php?p=80328317&postcount=644
Regards, Bigfoot29
After trying out endless stock roms to try and cure the WiFi dropouts on this phone, i decided to root my phone to see if that would cure the problem. Indeed it did!! No problems or glitches with this ROM at all, thanks for sharing. I have used the APKs from the stock launcher and camera. So i have the same feel as before but everything seems a lot smoother. I nearly gave up on this phone, i even put Marshmallow back on there thinking the wifi was a nougat problem, no the problem was ZTE!!!! THANKS !!
If you ever need an update, just holler. I still have my build environment intact.
Thanks very much!!
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano/pico gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
Almost all
Known Issues
If you have wifi issues with latest release, please after install firmware apply patch:
SM-T320: https://drive.google.com/file/d/1E79Gcn7rNox2vP3OUd5FcVm2-a0aE12n/view?usp=sharing
SM-T325: https://drive.google.com/file/d/1fn1zJLL8dTJJJyoMEqph3DPH50YJp_gO/view?usp=sharing
Links
SM-T320
7. 20200411: march security patch, kernel update: https://drive.google.com/file/d/1I3QGfAEo55MKoEpBHBoZwj9a6EWzFBzA/view?usp=sharing
6. 20191211: december security patch, video recording, kernel from q with new wlan driver: https://drive.google.com/file/d/1YsniqI2RPwPKN9dB_7fKBAo9QkzxSFs_/view?usp=sharing
5. 20191130: latest sources, update kernel (autobrightness, some cleanup): https://drive.google.com/file/d/1swloB3vCfNsVzr9qsCmgpP8FpdrbXaJ2/view?usp=sharing
4. 20191112: november security patch: https://drive.google.com/file/d/1KQUcfna2rbeq8TLZfu44e63la59-rmzY/view?usp=sharing
3. 20191102: https://drive.google.com/file/d/1qJstVdMuPOM5ihsWqNvQeO4NyzsaVVIF/view?usp=sharing
2. 20191029: rollback dtb blocks to old stock: https://drive.google.com/file/d/1bY-vCQj57Gfgco1HeGbkkyjJEdOYOG2D/view?usp=sharing
1. 20191026: initial build: https://drive.google.com/file/d/1H3X036Qe9MJwEkE2zMPH5gQ05DLTkCzc/view?usp=sharing
SM-T325
4. 20200411: march security patch, kernel update: https://drive.google.com/file/d/13W9kC8RXK9CkqhDt5X9SQ7k9GISHbI5w/view?usp=sharing
3. 20191214: fix audio issues from last release: https://drive.google.com/file/d/1Mo3tPRTXtik2kBVNLJ8kw_bA6NJAgMuW/view?usp=sharing
2. 20191211: december security patch, ril + mobile data, internal speaker, kernel from q with new wlan driver: https://drive.google.com/file/d/13ARo1qiUh9MrNh9DHNlwxdo028cGpAjI/view?usp=sharing
1. 20191130: latest sources, update kernel (autobrightness, some cleanup), november security patch: https://drive.google.com/file/d/1Y4w1enXmMmDmLCvgzQSf5V6w-6wiPqLA/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official version from:
SM-T320: https://twrp.me/samsung/samsunggalaxytabpro8.4wifi.html
SM-T325: https://twrp.me/samsung/samsunggalaxytabpro8.4lte.html
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_mondrianwifi and https://github.com/Valera1978/android_device_samsung_mondrianlte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_mondrianwifi and https://github.com/Valera1978/android_vendor_samsung_mondrianlte
Thanks
Thanks to LineageOS team
Hello. 2 weeks ago with a big discount, I bought used a tab pro 8.4 wifi tablet.
I develop firmware for several tablets - note 12.2 on the same qcom 800, tab a 2016 on exynos 7870 (wifi<e) and a tab s3 on qcom 820 (wifi<e).
Initially, I thought, since the note pro is almost then same, as the tab pro series (actually, the note pro was develop based on the tab pro series), it turned out that these are huge differences, and I spent a huge amount of time to launch the tablet.
There were literally problems with everything - I spent almost a week launching just a panel and correctly turning it on/off. Then a huge amount of time to launch wifi and bt. Well, at the end, the sensors and cleanup the sources.
A bit later I'll build sm-t325 version and may be 10.1 sm-t525 (but I don't have this tablets, please send me to pm if you ready to help with test)
All my tablets already has android q. Of course after cleanups sm-t320 will get android q too.
Working for me only with pico gapps
del
Valera1978 said:
Hello. 2 weeks ago with a big discount, I bought used a tab pro 8.4 wifi tablet.
I develop firmware for several tablets - note 12.2 on the same qcom 800, tab a 2016 on exynos 7870 (wifi<e) and a tab s3 on qcom 820 (wifi<e).
Initially, I thought, since the note pro is almost then same, as the tab pro series (actually, the note pro was develop based on the tab pro series), it turned out that these are huge differences, and I spent a huge amount of time to launch the tablet.
There were literally problems with everything - I spent almost a week launching just a panel and correctly turning it on/off. Then a huge amount of time to launch wifi and bt. Well, at the end, the sensors and cleanup the sources.
A bit later I'll build sm-t325 version and may be 10.1 sm-t525 (but I don't have this tablets, please send me to pm if you ready to help with test)
All my tablets already has android q. Of course after cleanups sm-t320 will get android q too.
Click to expand...
Click to collapse
everything seems to work. thank you for this huge job
Thanks a lot! For me it works too!!! I used TWRP 3.2.3.0 and gapps mini (arm)! Dont forget a full wipe after installation.
Sent from my [device_name] using XDA-Developers Legacy app
@Valera1978
THX, you have done a great job, alot of us have waiting for this Version 16, camera works fine.
@Valera1978
Which Security Date has got this ROM.
Wound you like to update this ROM monthly with newest Patch level ?
bierma32 said:
@Valera1978
Which Security Date has got this ROM.
Wound you like to update this ROM monthly with newest Patch level ?
Click to expand...
Click to collapse
Current security update is october 2019.
You can monitor new update in: https://github.com/LineageOS/android_build/blob/lineage-16.0/core/version_defaults.mk , PLATFORM_SECURITY_PATCH define
Usually a new update appears on the 5-10th of the month (in lineage code) and after it I'm building new version.
Thank you for your working. I really expect the version of SM-T325
And what about SM-T520?
TechDriver said:
And what about SM-T520?
Click to expand...
Click to collapse
sm-t520 has differ platform. this is exynos5420 like t900\p900\901.
Thanks much! You brought a new life into my favorite tablet! It's hard to find a premium 8.4 tablet these days and hardware in this 5 year old one is running strong with your ROM.
Спасибо Валера!
Incredible to find developers still going strong in creating latest android version builds for this tablet after 5 years. Kudos to OP!
Works flawless and surely has added couple of more years life to the tablet now.
new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.
Valera1978 said:
new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.
Click to expand...
Click to collapse
I've tried test version on my SM-T325. There was repetitive rebooting problem initially and I cannot set anymore
However, thank you for your effort and I believe you can fix this problem.
How do i install this?
sorry to be a noob but this is my first time rooting an android device in about 8 years.
I have rooted by T320 and have super user.
I have installed the TWRP app.
I have odin.
I have all the downloads suggested on both my PC and my Samsung SD card.
WTF am i supposed to do from there? Do i install the mondrianwifi i find in the TWRP app if, so to boot or recovery? Or am i supposed to install the version the author linked. I hav read multiple articles but they don't explain what i am doing, why, how i should choose my options and they are all seriously out of date (given the age of the tablet)
Help!? Can someone give me a breadcrumb trail?
---------- Post added at 03:13 PM ---------- Previous post was at 02:51 PM ----------
scyto said:
sorry to be a noob but this is my first time rooting an android device in about 8 years.
Help!? Can someone give me a breadcrumb trail?
Click to expand...
Click to collapse
Ok i figured it out by a lot of poke and hope and got lucky.
I have the new firmware on with micro apps.
Was non intuitive how long the tablet takes after first reboot to get everything ready and WTF is that slider / circle animation - i thought it was telling me to slide my finger from right to left (that was up for like 2.5 mins the first time) luckily i just waited.
On first use lots of apps reported crashing most stopped but BT app was in infinite reboot.
Did hard reboot and the BT app is still infinitely rebooting along with android.process.media
Trying a factory reset, use TWRP to wipe device (all but SD card) and reinstall to fix....
---------- Post added at 03:32 PM ---------- Previous post was at 03:13 PM ----------
now its hung at the strange animation for more than 10 mins and power button does nothing? What next?
Another wipe and re-install not connected to USB seemed to fix it.
nrpia said:
I've tried test version on my SM-T325. There was repetitive rebooting problem initially and I cannot set anymore
However, thank you for your effort and I believe you can fix this problem.
Click to expand...
Click to collapse
Please post logs,
SM-T325 builds appreciated
Valera1978 said:
new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.
Click to expand...
Click to collapse
WOW just WOW
@Valera1978 Thank you for all your efforts and bringing this device back to life! I'm happily looking forward to test builds for the SM-T325 and provide logs if needed.
Valera, What is new in release from 11/02 (lineage-16.0-20191102-UNOFFICIAL-mondrianwifi)? Or it is targeted to owners of SM-T325 and you just misplaced it in SM-T320 section?