yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Guides, News, & Discussion] basem_ym:
I know quoting large posts is not a good idea, but this really worth quote, sorry.

I read this post nearly 10 times a day, so exciting, seems like nothing is impossible for you.

I am following your posts closely, your ideas and the way you understand basics is very impressive.

what you say is very promising, maybe we will have a vendor repo someday :D

all the best bro, Merry Christmas and happy building ;)
[Treble-Enabled Device Guides, News, & Discussion] tripLr:
You can quote me any time

I broke my arm as a kid so I had lots of puzzle books from my grandma's

The first TRS80 came to our school with Basic,

The first ibm PC came to our school with Pascal programming, ( c prequel)

And my assignment in computer science was building a 4 bit computer

I worked at Microsoft and learned what crap cut and paste OS is while apple was slowly building and the Linux Unix revolution went kaboom

So for the next decade everything was patchware upgrades while Linux and FreeBSD became the backbone of the internet.

So as search engines and browsers battled, and your cell phone providers became rich selling ringtones , a outfit named Google buys a little Linux based cell phone operating system called Android.

We are using a Linux kernel (open source )

with a touch screen Graphic user interface.

On a hardware motherboard ( open architecture by chipset manufacturer

With a proprietary bootloader

And a propietary desktop ( like TouchWiz )

With propietary add on hardware ( S Pen )

And propietary cell phone company apps. ( Verizon )

And unremovable pre loaded bloatware ( Facebook NFL etc)

Running on propietary drivers.

Which totally goes against the open platform of Linux in my opinion.

So by forcing the chipset and handset to make standard driver hooks, the open platform of Linux and open source Android desktop in trebel brings a little more control back to the user , and allows Google to innovate Android faster,

Google is wanting the customer that owns the phone to be theirs, not the handset maker or cell phone provider.
[Treble-Enabled Device Guides, News, & Discussion] tripLr:
Ok another thought

Someone ported Lineageos to X86 laptops

https://xdaforums.com/lineage/general/unofficial-linage-os-pc-based-android-t3531145/page2

Could Trebel be ported to laptops? Most hardware drivers have open source version for Linux .

Oreo Trebel on your HP laptop anyone?
[Treble-Enabled Device Guides, News, & Discussion] tripLr:
Open GL will support any device that has open GL hardware and it's in Android Linux keenel
[Treble-Enabled Device Guides, News, & Discussion] Haxk20:
Treble onX86 ?

Its impossible. X86 doesn't work the same as ARM.

They don't use separate partition.

Also as I said 100000x times here. Its impossible for you to port treble to non-treble device.

You need opensource vendor files which I doubt any SOC will just give away.

Also the note 5 will have treble drivers only for note 5.

You must take into count that every phone have different WiFi BT etc those drivers won't work with any other phone.
[Treble-Enabled Device Guides, News, & Discussion] basem_ym:
maybe it worth a try?
[Treble-Enabled Device Guides, News, & Discussion] Haxk20:
Sure let him try but im 99.999999% sure that it wont work.
[Treble-Enabled Device Guides, News, & Discussion] revjamescarver:
Just wasting time even talking about "porting" treble to older devices that aren't already treble enabled, especially older devices. I mean really, what SoC manufacturers are going to waste their time rewriting code for older chipsets to make them treble capable? Guy's talking about how treble isolates the kernel from the hardware and other bs, he needs to read up a little on what treble does and does not do. Treble isolates the Android system (framework) from the hardware and enables device manufacturers to provide updates easier. With treble they can provide updates kernels and drivers without having to rewrite a lot of the Android framework every time, and they don't have to change any low level stuff to update the Android system, that's all it is. Kernels and device blobs are always going to be device specific, and since all those blobs are CLOSED source it ain't gonna happen.
[Treble-Enabled Device Guides, News, & Discussion] basem_ym:
come on guys...

do you think that we really don't know treble can't be ported??

anybody on xda can recognize that, I've seen that million times.

the purpose of this thread is clear:

I believe OP is not strictly talking about "porting" treble itself, but finding or developing something makes old devices act as a treble enabled device, thus they can benefit from an android go build hopefully.

maybe by building device blobs from scratch (by community)

or by doing alot of copy-past work.

or maybe by doing some hardware hacks.

maybe every thing we discuss is impossible, but we all have seen impossible things come true.
[Treble-Enabled Device Guides, News, & Discussion] Haxk20:
Sure but where do you get vendor sources ?

Do you create your own ?

AlsoTWRP uses one 2 generic drivers for touch.

No matter the device touch is 95% sure that it will work.

So the question is are you going to create your vendor files ?

Or idk how you get them.

And if so you decide to make them then good luck with that.

If it was that easy ROM devs would make vendor files too to make the process sooooo much easier.
[Treble-Enabled Device Guides, News, & Discussion] 2390:
And what "no hardware acceleration" means is that the operating system "Android Linux Kernel" cannot see the OpenGL capable hardware because it needs code that belongs to the OEMs and GPU manufacturers that cannot, will not, ever, be made available to the public. The only, and I mean ONLY possible device I can think of that has a chance in hell of a community Treble port is the HTC HD2, because they've reverse engineered everything, and that's only because 1: HTC used to open source almost everything back in the day, and 2: they've had 8 years to work on it

---------- Post added at 12:35 AM ---------- Previous post was at 12:28 AM ----------

Think of it like this: imagine somebody paralyzed from the waist down due to a spinal injury. Do their legs work? Yes, in theory, but the body cannot access them. Could the body grow the spine? Sure, they grew one in utero but the cells lack the blueprints to do it again (look up how scar tissue works if you're interested). Porting Treble to older devices would be like that. Is the hardware there? Yes. Can the OS see or use them? No, because they (and we, the devs) lack the blueprints to rebuild things, which would be required. I know that analogy kinda went a bit off the rails, but I think it gets the general point across
[Treble-Enabled Device Guides, News, & Discussion] tripLr:
Ok, we have a new trebel article.

https://www.xda-developers.com/project-treble-aosp-android-oreo-huawei-mate-10-pro/

So in here is a chipset mention in different devices.

One of them is the Qualcomm snapdragon chip

Now I know most programmers ate mostly cut paste, tweak, library links, and scripting

Hardware driver however coders dread new families of hardware, but they all start with CPU architecture, buss addresses, memory IO addresses which represent physical connections.

So here we have a trebel snapdragon device.

By running the compiled drivers of trebel, through a code comparison with a non trebel driver should be able to identify

I/O address --->software code----> Trebel handle

Or visaversa

Trebel requirement ----->code------>device

Hardware development also follows lines.

Witness Intel CPUs and AMD, and the chipset to make them work on the motherboard.

So figure the easy stuff first

Buttons

Screen input sensor

GPS

Memory controller

Then harder stuff

GPU

CPU

Sensors

Camera

When a chipset maker makes x

Does the handset maker say, I want x and then adds the camera controller it wants, is there a standard IO for a camera in the chipset?

Is there a driver guru out there that understands the hardware itself ?

When u look at the comments for the kernel, you can see email addresss for contributors for things like the scsi controller etc for Linux. All these comments are in almost all the kernel.sources.

Anyway still figuring things out..
[Treble-Enabled Device Guides, News, & Discussion] tripLr:
As for not being open source drivers, who cares, the hardware has published specs.

Bluetooth is a spec

Arm is a spec. The patent owner in England licenses the arm tech to builders

So Arm has an instruction set

Arm 64 has an instruction set

Open GL is a open video spec

And Android is an open spec.

A compiled lineage os is about 334 megabytes

In there the Kernel is compiled about what , 3 megabytes?

The modem partition is what 15 megabytes?

What's this all compiled in C++ or what. Just askin
[Treble-Enabled Device Guides, News, & Discussion] revjamescarver:
Do you even bother to read?

Do you even bother to read? There is no "backporting" to older non treble devices. First off you're not going to get closed source driver code from the SoC manufacturer, it just isn't going to happen. You also make a wrong assumption about twrp, there is nothing universal about it, as of oreo twrp no longer contains a kernel of any kind. There can never be a universal bootloader as those have and always be particular to the specific SoC, you can talk about code all you want and hope you haven't done it sonce pascal, but there are some simple facts that you refuse to grasp no matter how many people try to tell you. First off, treble REQUIRES driver and kernels that have been written to support it, second you are NEVER going to get the source code for the drivers from the SoC manufacturer, third you are comparing the android device to a pc and the two are as different as night and day, on a pc some of the low level functions are handled by the bios, whereas on any android device there is no bios, everything between the hardware is handled by the kernel, it's modules, the CLOSED SOURCE drivers, and then the android os. You trying to port treble to your device would be just like me getting to port it to my retired s5, a ton of time wasted on a futile effort. If you want to waste your time go for it, but realize that forest your going to have to port a complete kernel, write ALL your own drivers, rewrite a s***load of the android os, compile it all, repartition your device, at very minimum you're going to have a recovery, ram disk, kernel, vendor, system, and data partitions (kernel and ram disk because with oreo there is no boot partition anymore, it is /kernel and /ramdisk). So if you want to chase windmills get to coding. As some additional information, the phone manufacturer does not write their own drivers for the hardware on the SoC, those are provided in binary form from the SoC vendor, the carrier has nothing to do with drivers or low level software at all.
[Treble-Enabled Device Guides, News, & Discussion] mhedoc:
Hi,

why should the SoC/module vendor change the way on how a driver is writen for linux kernel?

Are the SoCs/modules only used for Android devices or also for other devices that maybe are also linux kernel driven?

If their SoCs/modules are used for other than android devices, are they really implementing different drivers for the same kernelversion?

I don't know, but maybe somebody, who knows how vendors create drivers for their SoCs, can tell us? Or maybe somebody can explain this picture mentioned in early post?

https://xdaforums.com/showpost.php?p=74993403&postcount=550

[IMG="Changes between Project Treble to old android way"]https://cdn57.androidauthority.net/wp-content/uploads/2017/07/Old-vs-new-HAL-process-840x338.jpg[/IMG]

These are seriously meant questions!!!!! And i will appreciate somebody competent will answer them!!!
[Treble-Enabled Device Guides, News, & Discussion] revjamescarver:
Your questions

I can understand your questions, I suppose the best way to look at it that the kernel (and it's modules) live in one space, Android lives in another space, and the Hal occupies the space in-between, the SoC drivers are specific to Android devices. There are distributions of Linux that run on arm core devices (raspberry pi for example) but they generally rely on the kernel and it's own built in drivers to support hardware. The last Linux build I did for arm used broadcom for Wi-Fi, realtec for the sound, etc., All off the shelf chips, SoC's for phones are a different animal. As far as the how any why the SoC vendors do things the way they do, you are probably not going to find the answer you are looking for on XDA, you'll really have to talk to a software development person at the SoC you are looking to find out the answers about.
[Treble-Enabled Device Guides, News, & Discussion] o-l-a-v:
Can a Treble compatible driver for a SoC used by multiple devices, across OEMs, be used by another device with the same SOC?

Lets say a OEM ported Treble to a device using the same SOC as my OP3T, could my phone benefit from it later on?
[Treble-Enabled Device Guides, News, & Discussion] Haxk20:
NOOO

The treble files are device specific and thats it.

There is no way to backport treble for older devices.
[Treble-Enabled Device Guides, News, & Discussion] tripLr:
The answer is kinda maybe, it's gonna be hard.

As hard as making a driver from scratch from code like the original Linux.

1. You need to start by hoping your device has a list of all drivers

Here is a clue

All SOC makers have a standard they licence from the source of the ARM platform, the parents are owned by a company in England.

The next standards are all the IO standards. So far I am talking the actual hardware no software yet

Most SOC manufacturers like Qualcomm will sell a chip for hardware developers like watches, medical devices, display manufacturers, case manufacturers etc. These chips are then sold to a mother board maker that makes a ”phone" that sits on a open motherboard.

Qualcomm releases build able somewhat open source kernels and drivers for these hardware testers.

Older drivers are released as open source on the Qualcomm website, and some Samsung.

In a phone unlike a computer, there is only 1or 2 chips that have everything built together.

So these testbeds, just plug in screens with touch input and cameras .

These developers play around with the drivers to get their configuration to work

https://developer.qualcomm.com/hardware/snapdragon-835-hdk
[Treble-Enabled Device Guides, News, & Discussion] afridi.shahriar:
Hey!! I developed trebel for my phone, Xiaomi Mi max (hydrogen).

But, there are many limitations.

1: trebel is only for the same android SDK version.

Like, the trebel won't boot sdk27 roms, as it's only SDK26 supported.

2: t

With trebel, other ROMs booted, bur, baseband was showing error, and, many wireless related apps showed force close, like: com.android.phone.

Btw, i think, vendor/trebel also need to be upgraded in these trebel devices, which will bu automatically updated from Google services. So, it will be automatically supported to new android SDK versions.

Which won't be available in our custom trebel ports.

Or, we need to have a developer's site, who will upgrade trebel files like Google do, for unofficially trebel enabled phones.

As, now, we have lineageos, which provides custom roms, when we don't get official updates
[Treble-Enabled Device Guides, News, & Discussion] tripLr:
That's awesome.

Thanks for sharing.

Can you post a thread in this zone on how you did it with your sources?

Please share this wonderful accomplishment

General steps are ok, post your steps.

I have been digging into building ROMs. To catch up on getting into building Oreo.

So for my progress which I will update in the OP

Learning Linux from scratch on an 6 year old dual hard drive 4 gb HP dual 64 gb laptop

Which further reinforces my ideas on Trebel and or oreo

https://www.xda-developers.com/android-go-old-android-8-1-oreo/
[Treble-Enabled Device Guides, News, & Discussion] tripLr:
I will be closing this thread.

Many Aosp and lineageos Oreo builds are up for almost all note 4 devices.

GitHub.com/tripLr-dev

Thanks

Come visit out telegram group.

https://t.me/triplr_dev_users
[Google Pixel XL Questions & Answers] ggpxl555:
Hey guy and girls,

Just wondering if its possible on the pixel xl to have a custom live wallpaper that daily updates with all your photos on google drive? it only lets me select one.

Cheers!
[Xiaomi Mi A1 Questions & Answers] aks_pk:
Hi all,

Basically I want to root my mobile without loosing access to my corporate mail and banking app (which doesnt work on rooted mobiles - and which I assume will work with magisk). I have below queries if anyone can answer will be grateful

1) I want to use adaway, font changer, build.prop hack for api2, all mods in this thread https://goo.gl/PZYFZH & https://goo.gl/fgDMWu (Some of them req twrp). Will I still be able to access corporate mail ?

2) can I just unroot and re-lock bootloader to get and install OTA

3) Will I lose data after point 2
[Xiaomi Mi A1 Questions & Answers] _mysiak_:
1. as long as you enable Magisk hide + specify your email/banking apps in the menu, you should be able to use them. You might be out of luck if you use Xposed though (it breaks Safetynet).

2. when OTA arrives, restore stock boot image from Magisk, apply OTA and when the phone asks for a reboot, install Magisk to the second, updated partition. After reboot you'll have updated and rooted system.

3. there is no need to relock the bootloader, so no risk of data loss.
[Xiaomi Mi A1 Questions & Answers] aks_pk:
Thanks a lot. I installed magisk. Everything is good so far. Any good modules/mod/hacks can you suggest please

Also Reg 2nd point, i dont mind losing all the data. Just in case anything happens, can I flash stock rom, and get the phone back in mint condition?
[Xiaomi Mi A1 Questions & Answers] _mysiak_:
You can relock the bootloader as long as you have stock kernel, recovery and system. Lazy way is to uninstall magisk ("restor stock boot image"), the safest way is to download stock rom and flash it (with or without data wipe). Btw. Xiaomi is the first phone which did not perform factory reset while unlocking the bootloader, so it's possible that you will lose nothing during relocking.

Personally I'm using these modules/mods from repository:

1. Google framework - to be able to install Google phone dialer from play store

2. Google lens enabler - to be able to use..Google lens :)

3. Greenify4Magisk

4. Xposed

+

5. Custom made module with these build.prop fixes - enable EIS, camera2api, add more volume steps, fix voice recording noise (there is similar module available at XDA with additional mods which I wasn't interested in)
[Xiaomi Mi A1 Questions & Answers] aks_pk:
Thanks a lot.

Thanks for sharing.

Well, I was using this mod for google dialer before rooting. - https://goo.gl/iSxS45. Have to say its awesome.

Also using google lens, mi A1 module by [MENTION=4460995]sooti[/MENTION], iYTB magisk, greenify, ifont, adaway, GCAM mod with hdr+ and zsl. Still exploring :cowboy::cowboy:
[Xiaomi Mi A1 Questions & Answers] _mysiak_:
If I'm not mistaken, it doesn't support nearby places search and caller ID, the only two features which are missing in stock Mi A1 dialer :) But with Google framework + unmodded Google dialer, everything works fine. There is only one disadvantage - if you install Google dialer and then boot phone without Google framework module enabled, it will disappear from installed apps and mess up dialer permissions and settings and you'll need to reinstall it later. But IMHO it's worth the risk :)
[OnePlus 5T  Themes, Apps, and Mods] saraohyland:
As some of you know the Google Camera app with HDR On is great to shot low light pictures. However OP5 users as myself aren’t as lucky when using the modded Google Camera app as as users from other devices.

With OP5 we have bugs that seem to be applicable only to our case: touch to focus not working along HDR & dots pattern issue visible when you zoom in certain pictures shot with the modded camera.
[OnePlus 5T  Themes, Apps, and Mods] Stephen:
Moderator Information,

Thread closed, Please see existing thread: Google Camera ported app on OP5T
[Shift General] hbendavid:
Everyone,

This is one of my first posts. I have been reading the threads on this and cannot make heads or tails of what's going on. I have a Shift for eval purposes and after playing around with it, I think it's a pretty amazing device. HTC has crippled the phone capability in the US versions because they haven't certified it for voice use with the FCC yet. If we can access "file explorer" and some of the other features of WM6, I think a lot can be done to modify it or even to use it for voice. Has anybody made any headway as far as a new ROM that enables all of this functionality?
[Shift General] greatestkelvin:
No

nobody has yet developed the crack. The reason is because nobody has the machine yet. Can u comment a bit about the battery life. Is it very disappointing?
[Shift General] citivolus:
well, now that several people actually have the device in-hand, could somebody please confirm that the ability to expose full WM6 exists as described by Pawel062:

This is the only thing holding me back from ordering one myself!
[Shift General] Pfeffa-rah:
Me too!

So Any luck running/installing any other programs on SnapVue?

greetz,

Pfeffa-rah
[Shift General] rockstar:
what about athena projects rom? that rom is actually from shift right?
[Shift General] Pawel062:
snapvue is actually a today plugin pretty much. it hides the soft keys and start menu of the original wm6. then from the plugin u have access to messaging, settings, and other basic stuff.

this is ment so u use vista but with only 2hrs max battery on vista many people would like to use the less power hungry wm6. i am working with paul from modaco.com on re enabling the full wm6 by putting a modded dll that will unhide the start menu. after that ull be able to get into file explorer and get a reg editor to re enable the soft keys.

heres the challlenge:

--no usb port like regular htc phones to sync the shift and get the dll on their. only usb host

--no bluetooth in snapvue/wm6 side

--no wifi in snapvue/wm6 side

--no ir in wm6 side

--vista device central doesnt see the wm6 side

--cant save files from email to windows folder

and i cant remember now the other blockades. i will continue working on it though.
[Shift General] pusler:
Seems like that there is some kind of file transfer, it uses it when you install a certificate in shift control center, but how to crack it open or replicate the process for other files, and then execute the file on snapvue site ....

Think its time for a "taskforce thred" where all info is posted so everyone can work on it.
[Shift General] Pfeffa-rah:
Sounds a lot more difficult then I first imagined....

(No BT??? OMG! had no idea!)

Sounds like I have to be a bit more patient...

This doesnot sound like it´s gonna be solved in a couple of days....

It´s great that you´re workin on it guys!

greetz,

Pfeffa-rah
[Shift General] citivolus:
thanks Pawel062, I appreciate your efforts in trying to find a way to get this to work!
[Shift General] michael85:
Just saw if you edit a contact and then try to attach a picture, you can browse the WM6 folders.

Unfortunately you can only see the pictures, because it's using the picture manager from HTC..
[Shift General] Wiz:
Silly thought: The miniUSB connector on the dongle formally is only meant to provide additional power to devices that otherwise would not be detected (External Harddrives etc). Would it be a silly thought to assume that the same miniUSB port could somehow allow us to access the SnapVue part? The miniUSB port is located at the back next to the cable leading back to the Shift.
[Shift General] Pantaloonie:
I hadn't even noticed that.

I just plugged mine in for the first time, the only drivers Vista installs are for a Generic USB Hub and a USB to Ethernet Adaptor. There doesn't seem to be anything else hidden in there.
[Shift General] rpawly:
If anyone needs anything tested on a shift dont hesitate to ask. Full WM6 functionality would be greatly appreciated and would turn snapview from a gimick into a usefull tool.