There is a project, which devs are reverse engineering proprietary Samsung binaries to make free analogues. It probably can give some profits, if you integrate their work in the ROM.
KOLANICH said:
There is a project, which devs are reverse engineering proprietary Samsung binaries to make free analogues. It probably can give some profits, if you integrate their work in the ROM.
Click to expand...
Click to collapse
We've already integrated pretty much anything of use that they have. Among other things, the opensource camera HAL and the Yamaha audio HAL on Exynos 4210 devices originate from Replicant.
For the most part though, the Exynos 4210 family are dead (unlikely to be supported by Omni when L goes live) and 4412 support is questionable. (Most of the Exynos guys have long since moved to less painful platforms.)
Related
Look at this:
http://gizmodo.com/360514/htc-says-software-fix-is-coming-for-lousy-video-drivers
An official HTC statement about the drivers looks promising. Again, keep your hopes up and guard up!
Not only is this old and posted to death, but
However this fix is not a new video driver to utilize hardware acceleration
Click to expand...
Click to collapse
There is nothing promising about this, please read carefully next time, it just misleads people who read your post
Damn. . . I thought that was a new and updated statement. Look if you only read a little bit of it then you probably missed out on this.
Some of our top engineers have investigated video performance on our devices and have discovered a fix that they claim will dramatically improve performance for common on-screen tasks like scrolling and the like. Their fix would help most of our recent touch-screen products including the Touch family of devices and TYTN II / Tilt, Mogul / XV6900. The update is in testing and we hope to release it soon. However this fix is not a new video driver to utilize hardware acceleration; it is a software optimization. Video drivers are a much more complicated issue that involves companies and engineers beyond HTC alone. We do not want to lead anyone to believe they should expect these. To explain why we are not releasing video acceleration instead of the optimization
I offer you our official statement... "HTC DOES plan to offer software upgrades that will increase feature functionality, over the air wireless speeds and other enhancements for some of the phones being criticized, but we do not anticipate including any additional support for the video acceleration issues cited in customer complaints. It is important for customers to understand that bringing this functionality to market is not a trivial driver update and requires extensive software development and time. HTC will utilize hardware video acceleration like the ATI Imageon in many upcoming products. Our users have made it clear that they expect our products to offer an improved visual experience, and we have included this feedback into planning and development of future products. To address lingering questions about HTC's current MSM 7xxx devices, it is important to establish that a chipset like an MSM7xxx is a platform with a vast multitude of features that enable a wide range of devices with varied functionality. It is common that devices built on platforms like Qualcomm's will not enable every feature or function. In addition to making sure the required hardware is present, unlocking extended capabilities of chipsets like the MSM 7xxx requires in-depth and time consuming software development, complicated licensing negotiations, potential intellectual property negotiations, added licensing fees, and in the case of devices that are sold through operators, the desire of the operator to include the additional functionality. To make an informed decision about which handset suits them best, consumers should look at the product specification itself instead of using the underlying chipset specifications to define what the product could potentially become."
Click to expand...
Click to collapse
~~Tito~~ said:
Damn. . . I thought that was a new and updated statement. Look if you only read a little bit of it then you probably missed out on this.
Click to expand...
Click to collapse
Sorry Tito,
Nothing new to that, just the same old company line that they've been spouting for weeks.
Meeing!! I thought I saw something new. Well Law Suit it is then since they don't want to make a small amount of effort to fix some devices problems that they shouldn't have. I wonder if they use their own devices or do they have drivers made for them and not us?
http://www.change.org/petitions/nvidia-useful-driver-for-tegra-2-chipset#
just thought id share it in here guys. even if you dont think its relevant to you, since you dont flash roms (which is unlikely, because you would not be in xda..lol ), still sign it ! its important stuff, especially if we want a good ics rom.
cheers
xilw3r said:
http://www.change.org/petitions/nvidia-useful-driver-for-tegra-2-chipset#
just thought id share it in here guys. even if you dont think its relevant to you, since you dont flash roms (which is unlikely, because you would not be in xda..lol ), still sign it ! its important stuff, especially if we want a good ics rom.
cheers
Click to expand...
Click to collapse
Note from Nvidia about drivers
Hello Android Development Community
We appreciate all the interest and passion surrounding the NVIDIA Tegra Platform and we take our support for the development community seriously. NVIDIA has been working with Google and Motorola to provide the open source community with the required drivers and other binary code to build full Android OS images for the Tegra 2 powered "Motorola Xoom". We expect Google to make those components available as part of the Android Open Source Project soon.
In addition, NVIDIA is working on a full release of Ice Cream Sandwich (ICS) for our Tegra 2 Dual Core and Tegra 3 Quad Core reference devices to be made available early next year. This release package will comprise of binary code, drivers developed on our reference platforms and any patches necessary to ensure stability & performance with ICS. We hope the open source community can leverage this release for their work on all Tegra devices.
Andrew Edelsten
Source: http://forum.xda-developers.com/showthread.php?t=1309620
These petitions are of no use. The only option we have is to wait.
i know i know... online petitions dont accomplish anything.. but i guess im just a bit desperate.
ive seen that statement and what troubles me is that it mainly concerns xoom which is actually using a different kind of tegra2, ventenara or sth like that whereas 2x has harmony tegra 2, so if nvidia releases drivers for xoom, we wont have much use of them
Anyone got a clue on why either of these are not compatible with the note 3? Is the version android we are on? If so I am starting to think Samsung hates the note 3 buyers.
Because Samsung doesn't want repeat customers? :silly:
This might explain it a bit:
http://forum.xda-developers.com/showpost.php?p=59951925&postcount=163
http://forums.androidcentral.com/ve...3/512346-mobile-payment-options-note-3-a.html
My understanding is that currently there are 2 different NXP chips which use two different stacks.
pn544 used libnfc-nxp stack binary patched by NXP to add HCE support (no support in AOSP for HCE)
pn547 uses libnfc-nci, which is from broadcom but uses standard NCI command sets, with HCE support already in-place in AOSP code.
There has been investigations to establish if pn544 could be made NCI-compliant through firmware upgrade, but it seems like it is not working, thus no HCE support for pn544, binary patched images excluded.
pn547 have HCE support, but it seems like Ttp capabilities are still missing for some Google choice
Sorry to resurrect the thread with a new question: how does all of this relates to the HCI based infrastructure in Linux kernel (drivers/nfc) ?
Android support, afaik, is completely userspace, using a trivial i2c-dev kernel driver as interface. Is this correct? Where is the i2c-dev driver for pn544/547? It shouldn't be in drivers/nfc/ tree right?
cherokee140 said:
This might explain it a bit:
http://forum.xda-developers.com/showpost.php?p=59951925&postcount=163
http://forums.androidcentral.com/ve...3/512346-mobile-payment-options-note-3-a.html
My understanding is that currently there are 2 different NXP chips which use two different stacks.
pn544 used libnfc-nxp stack binary patched by NXP to add HCE support (no support in AOSP for HCE)
pn547 uses libnfc-nci, which is from broadcom but uses standard NCI command sets, with HCE support already in-place in AOSP code.
There has been investigations to establish if pn544 could be made NCI-compliant through firmware upgrade, but it seems like it is not working, thus no HCE support for pn544, binary patched images excluded.
pn547 have HCE support, but it seems like Ttp capabilities are still missing for some Google choice
Sorry to resurrect the thread with a new question: how does all of this relates to the HCI based infrastructure in Linux kernel (drivers/nfc) ?
Android support, afaik, is completely userspace, using a trivial i2c-dev kernel driver as interface. Is this correct? Where is the i2c-dev driver for pn544/547? It shouldn't be in drivers/nfc/ tree right?
Click to expand...
Click to collapse
Thanks for this.
Samsung just lost me as a customer. First the GPS never works, then the whole storm about Knox, then android/samsung pay, now no updates post 5.0?
This phone was dropped by them for getting updates in May way before the 2 years commitment they said they would keep.
tnerb123 said:
Thanks for this.
Samsung just lost me as a customer. First the GPS never works, then the whole storm about Knox, then android/samsung pay, now no updates post 5.0?
This phone was dropped by them for getting updates in May way before the 2 years commitment they said they would keep.
Click to expand...
Click to collapse
This.
It's not exactly flattering when a flagship phone is mostly forgotten the next year. Especially when your biggest 2 competitors still support older/cheaper/slower products
Sent from my SM-n900A using Tapatalk
Today it has been announced in the XDA that redmi Note 4 got its project treble compatibility and it is a full project treble compatibility.
So when is Moto G5 s going to receive any kind of project treble compatibility but I think that it is relative the easier than the Xiaomi devices because it has all the resources available and I don't think there is any kind of heavy modification from the Motorola side as Xiaomi
But motorola does not offer enough sources to enable trebel i think..
What is project treble anyway, care to explain?
Sent from my XT1805 using Tapatalk
jdesignz said:
What is project treble anyway, care to explain?
Sent from my XT1805 using Tapatalk
Click to expand...
Click to collapse
Google can explain, but don't expect anything for this device. It's good for the future, but this device is in the past.
jdesignz said:
What is project treble anyway, care to explain?
Sent from my XT1805 using Tapatalk
Click to expand...
Click to collapse
There's an additional abstraction layer / API between the OS and the hardware drivers,
that make it easier to update the Android OS across different vendors with the same chipset (SoC) and hardware features (and long-term probably also across newer Android and Kernel versions, not sure though)
In essence you should be able to run an AOSP build from e.g. Huawei on Sony phones, LG, etc. as long as the components are the same,
meaning: e.g. phone calling, WiFi, etc. all should be working out of the box after installing that, camera and specific features (e.g. dedicated sound DAC) might be a different story though and require adjustments (not sure how that is realized in detail with Treble)
The thing with Project Treble is that it has to be considered right from the start, meaning there need to be (2 ?) additional partitions for updates available:
Partition A (current),
Partition B (new)
So that means for existing device it would involve re-partitioning and/or adding additional partitions to make a device Project Treble "ready",
which is practically impossible since this cannot be achieved with OTA updates.
I've read that older Huawei (or other vendor, Xiaomi ?) has this experimentally added (community ?) but this would require TWRP and/or custom manual intervention through recovery
and most people aren't able to do this - so it's unrealistic that existing device without Project Trouble could be "upgraded", retrofitted through that means
that's at least the superficial level that I got to understand from the discussion from other Sony devs
Hope that helps
Anything that can be developed for this phone have to be figured out very fast because Moto is going to release the G6 family very soon and as you know that once a new family gets released the older family gets less attention and gradually dies over the time and sadly I can see that there are no dedicated developers for this phone so the community has to take the responsibility to do anything possible for this phone as soon as possible.
Hey, i was just wondering why hasnt there been any stock android roms for the note 8 yet? I saw the s9 getting a resurrection remix. Is there any technical limitations thats holding back the development or do people just not care?
Because this phone has a pen ana that pen won't work without source code from Samfail
silveraero said:
Because this phone has a pen ana that pen won't work without source code from Samfail
Click to expand...
Click to collapse
Stock Android - and especically things like RR actually have pretty solid stylus support. And there's plenty of apps that add features like pen-gestures and replicate the proprietary Samsung stuff.
The problem is likely more to do with the lack of treble support that the S9 has - which drastically simplifies the issue of dealing with proprietary firmware and API's.
And the fact that a large portion of Note 8 users have models with locked bootloaders, which prevent the usage of non-Samsung ROMS. There have been several threads detailing attempts at making AOSP or similar ROM's, but all have fallen silent without much to show in the way of progress:
https://forum.xda-developers.com/galaxy-note-8/how-to/unofficial-lineageos-t3686026
https://forum.xda-developers.com/galaxy-note-8/how-to/bounty-aosp-roms-note8-t3686083
https://forum.xda-developers.com/galaxy-note-8/how-to/resurrection-remix-official-note-8-t3756351
Decoding and dealing with proprietary API's and firmware takes a lot of time and luck without sources which Samsung refuse to provide. And the pool of developers that seem interested in such a huge effort for the Note 8 seems to be shrinking.
Aaren11 said:
Stock Android - and especically things like RR actually have pretty solid stylus support. And there's plenty of apps that add features like pen-gestures and replicate the proprietary Samsung stuff.
The problem is likely more to do with the lack of treble support that the S9 has - which drastically simplifies the issue of dealing with proprietary firmware and API's.
And the fact that a large portion of Note 8 users have models with locked bootloaders, which prevent the usage of non-Samsung ROMS. There have been several threads detailing attempts at making AOSP or similar ROM's, but all have fallen silent without much to show in the way of progress:
https://forum.xda-developers.com/galaxy-note-8/how-to/unofficial-lineageos-t3686026
https://forum.xda-developers.com/galaxy-note-8/how-to/bounty-aosp-roms-note8-t3686083
https://forum.xda-developers.com/galaxy-note-8/how-to/resurrection-remix-official-note-8-t3756351
Decoding and dealing with proprietary API's and firmware takes a lot of time and luck without sources which Samsung refuse to provide. And the pool of developers that seem interested in such a huge effort for the Note 8 seems to be shrinking.
Click to expand...
Click to collapse
SO basically no hope for the future? this thing wouldve been a beast with an aosp rom. Thats really dissapointing i was looking forward to android p (
2000ftt said:
SO basically no hope for the future? this thing wouldve been a beast with an aosp rom. Thats really dissapointing i was looking forward to android p (
Click to expand...
Click to collapse
I wouldn't say the situation is hopeless. Just pretty silent at the moment. Some of the groundwork seems to have been done particularly by @SaschaNes and the teams they're a part of. But they've been silent on actual progress of bootable builds for several months now. No clue if they're still working at it or not.
I would say AOSP or Lineage for the Note 8 is achievable it would just take reasons for developers to dedicate their time and effort. And currently, there aren't many for most. Few dev's actually have the device, and even fewer are interested in AOSP for it. Perhaps a bounty might lure one or two - but it would have to be sizeable, and considering the amount of people that seem to have bought this device for the Samsung features - that's going to be hard to organize.
considering the amount of people that seem to have bought this device for the Samsung features - that's going to be hard to organize.
Click to expand...
Click to collapse
This, is the reason the note line, for a while now, has not had the development other Samsung phones have. Add to that , snapdragon and its lockdown , makes it difficult to see the note series as a custom powerhouse.
Sent from my Galaxy Note8 using XDA Labs
Which is a shame, considering the legacy of the Note 3,4 and 5 which continue to have AOSP roms built for them to this day - which has drastically extended the lifespan beyond Samsungs woeful EOL. Sadly devs simply don't seem to have the motivation or time to deal with jumping through the increasingly convoluted hoops constantly being errected by google and OEMs.
Because the note 8 is so locked down