Related
i read something in the net while i was surfing yesterday, you can look here: http://www.androidcentral.com/motorola-atrix-hd-gets-official-cyanogenmod-support
and then reading these lines made me surprised(maybe getting official cyanogenmod support for ancora is impossible after this moment but who kowns?)
If an Android device has enough of a following, and there are developer(s) willing to commit (no pun intended) to maintaining the device in the official CyanogenMod source tree, this device becomes officially supported -- and receives official builds of the CyanogenMod ROM.
if someone be maintainer for our device can we get official support from CyanogenMod?
is this really possible?
ı mean our device source code are available in github(kernel source device source and vendor files)
maybe forking our device source into CyanogenMod source tree can make this possible or am ı wrong??
maybe this is a bulsh*it after this moment but just wondering
for example galaxy s is getting official support from Cyanogenmod still if im not mistaken mr. pawit is their maintainer and developer
ım waiting your answers brothers what do you think about that? @arco68 @arsradu @LeroViten @honeyx and all ancora devs
with my best regards :good:
The SGW was for more than 3 years without official CM support and we didn´t miss anything, so I don´t think this is that much important for the rest of it´s counted days.
honeyx said:
The SGW was for more than 3 years without official CM support and we didn´t miss anything, so I don´t think this is that much important for the rest of it´s counted days.
Click to expand...
Click to collapse
ı understood bro but is there any hope for galaxy w? return of ancora :good: and also ı understood that from your comment : technically this is possible,galaxy w can get official support from CM Team but this is unnecessary for this dead device isnt it?
I simply don´t think this will happen because you have to look from their point of view.
1. this device is a low activity device in Amercian terms. 2. So never was that popular to get their attention. 3. is already old and not up to date. 4. It´s hype time is almost over and many earlier SGW users are going to replace it. 5. CM is going a different route now and will be focusing on their "device" they are going to launch soon. And finally 6. Why should they change this now after already 3 years?
So if I were CM I would look for the future not looking back to the past with it´s outdated devices and not even waste a single tought about devices like the SGW.
Is this bad for the SGW owners? As long we are having Devs like Radu who are porting the latest ROMs to this device it really doesn´t matter CM is supporting it officially or not supporting it.
So what do you expect from being supported by CM? You only would be able to install the latest nightlys launched by the CM team with all the bugs in the CM code included and maybe some day fixed. A Dev who is porting their CM sources of course has to fight with these bugs too, but also cares to fix the most important ones.
I asked arco68 a while ago, and he said it's because of legacy camera drivers that we are unsupported.
Sent from my Nexus 5 using Tapatalk
SGWUser said:
I asked arco68 a while ago, and he said it's because of legacy camera drivers that we are unsupported.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
auhh thats true sir arne is right as always anyway thanx man for informing us
regards :good:
I don't think so...anyway, we already have the stable n smooth ROM so far. Without Officail, it's does not matter at all.
Hello sir @arco68
First of all huge thanx for your great work on our Wonders
And secondly i wonder something
We are using s5k4ecgx sensor for back camera
And if we add the following patches and if we use v4l2 for camera driver, Can we use CAF based qcom cameraHAL?
-http://www.spinics.net/lists/linux-media/msg50380.html
And probably if we use new qcom cameraHAL, then we wont need legacy stuff the CM doesnt like(MemoryHeapBase,Overlay)
Then maybe we can get cm nightlies
Maybe porting new camera Hal to our phone can be hard but we must not give up. We are so close to official CM after ION i think. We can do it and we can success :good:
Thanx
Regards
hack4er said:
Hello sir @arco68
First of all huge thanx for your great work on our Wonders
And secondly i wonder something
We are using s5k4ecgx sensor for back camera
And if we add the following patches and if we use v4l2 for camera driver, Can we use CAF based qcom cameraHAL?
-http://www.spinics.net/lists/linux-media/msg50380.html
And probably if we use new qcom cameraHAL, then we wont need legacy stuff the CM doesnt like(MemoryHeapBase,Overlay)
Then maybe we can get cm nightlies
Maybe porting new camera Hal to our phone can be hard but we must not give up. We are so close to official CM after ION i think. We can do it and we can success :good:
Thanx
Regards
Click to expand...
Click to collapse
That would be so f... Awesome *-*
Please we need someone who knows how to do this
I heard at devcon that a few guys are working on Sailfish ports for a few phones, including ours. So I decided to get them together with the devs here on the forum to get the port done. The place where the developers and porters of Sailfish OS are talking to each other is on freenode, so if you want to help them... just go there and join the channel #sailfishos-porters.
Warning: This is a developement project. So please only join the channel if you really want to help. Just going there to ask for ETAs or stuff like that won' t be tolerated. Also this thread should be a place for developers to collect ideas and fix bugs, not for the purpose of asking for ETAs. Please keep that in mind.
For the initial port I would like to thank @vgrade; information on how to install the port are in second post!
XDA:DevDB Information
Sailfish OS, ROM for the ONEPLUS ONE
Contributors
dansou901, vgrade
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CM 11
Version Information
Status: Alpha
Created 2015-03-20
Last Updated 2015-03-29
This is a community port of Jolla's Sailfish OS for the OnePlus One.
It features a gesture-based user interface with a unique design and ease-of-use in mind.
For more information about SailfishOS please head over to sailfishos.org.
This is not an Android ROM, this is a different base of an operating system called Linux, running glibc library.
It only uses parts of Android for hardware enabling (drivers).
Release Notes:
The port is considered to be of alpha quality and released as a first step to the same levels of functionality as the Nexus 5 .
Download Location
http://images.devaamo.fi/sfa/bacon/
Kernel Source at http://images.devaamo.fi/sfa/bacon/...1.1.27-alpha1-201503192017-kernel-src.tar.bz2
Make sure you have a compatible cm11 version installed http://78.47.45.43/owncloud/public.php?service=files&t=9725fbb3b3c8d9706a2bb29388b3de83
Zip install tested with TWRP and MultiROM versions later than 20 March from http://forum.xda-developers.com/oneplus-one/development/mod-multirom-v26-t2835738
HW Support status:
(Look for OnePlus 5 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Bug reports, if internet search refuses to help:
First search XDA for keywords. Things like libsailfishapp have already been worked out by this amazing community
Software-related bugs (Sailfish OS): first search http://together.jolla.com . Tag your questions with "community-build"
Hardware-related problems: at the Nemo Project Bugzilla under Hybris-ing component
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
oneplus forum thread at https://forums.oneplus.net/threads/sailfish-os-for-oneplus-one.279537/
Known issues:
OTA Updates do not work
The camera does not work
Android app support is not available (unlike in Jolla phone): please ask about the status for open-source Dalvik runtime framework on #sailfishos-porters on irc.freenode.net and also check this XDA Thread
All remaining: In Bugzilla
ROM Kernel: Linux 3.4.0
Changelog:
Alpha2 - 29 March 2015
WLAN fixed up - vgrade/yacuken
Alpha1 - 20 March 2015
Initial release
This is a new video of SailfishOS running on the oneplus one with wlan working . http://youtu.be/Vm4m_dlUYRw
Install Video at https://www.youtube.com/watch?v=iphzmCVofbk
Details of port can be found at http://piratepad.net/gVqPXuEGW4
Please join the porting efforts at IRC channel #sailfishos-porters.
Thanks to all the Jolla sailors and SailfishOS community members for all their help, especially @stskeeps for the QCOM_BSP catch.
BREAKING NEWS - SailfishOS 2.0 version WIP at https://plus.google.com/+TomaszSternaSMK/posts/DyQHm82v2b5
vgrade
Just a little status update that you see the project isn't abandoned: @vgrade is waiting for updated AOSP sources from Oneplus. Once they're live, he can cook something for us.
Is the project still alive?
CountDooku said:
Is the project still alive?
Click to expand...
Click to collapse
Ask @vgrade if it is still alive. I didn't hear anything the last weeks, but I hope that he's still working on it...
dansou901 said:
Ask @vgrade if it is still alive. I didn't hear anything the last weeks, but I hope that he's still working on it...
Click to expand...
Click to collapse
@vgrade, is the project still alive?
msri3here said:
@vgrade, is the project still alive?
Click to expand...
Click to collapse
Hey,
I've not been able to spend much time on this since xdadev:con due to day job commitments, fingers crossed I'll get some time over the holidays to progress some more.
BR
vgrade
vgrade said:
Hey,
I've not been able to spend much time on this since xdadev:con due to day job commitments, fingers crossed I'll get some time over the holidays to progress some more.
BR
vgrade
Click to expand...
Click to collapse
thanks for the quick reply
Take you time
vgrade said:
Hey,
I've not been able to spend much time on this since xdadev:con due to day job commitments, fingers crossed I'll get some time over the holidays to progress some more.
BR
vgrade
Click to expand...
Click to collapse
Let me know if you need any help, I'm new to porting, but I'd be willing to lend a hand and do some of the grunt work - if you need it.
I'm very interested by getting Sailfish OS on my One Plus.
I don't know how to install the build you'll provide but I suppose that you will give a litte tutorial with it.
I'm now following this thread !
Looking forward to this
@dansou901 might be of interest.
Edit: might be your work. [emoji5]
https://twitter.com/vgrade/status/573375605640695808
gsmyth said:
@dansou901 might be of interest.
Edit: might be your work. [emoji5]
https://twitter.com/vgrade/status/573375605640695808
Click to expand...
Click to collapse
Good find! I don't have twitter so I wouldn't see this... @vgrade, will you come here again when you're back from Barcelona? @KINGbabasula, is MultiROM ready to go for Sailfish OS?
Edit: It isn't my work, I'm not in Barcelona on MWC this year (but planning to go there someday...). So it's vgrades work together with the other Sailfish porters (see the IRC channel I linked in OP).
Have you guys seem this?
http://www.thejollablog.com/sailfish-os-oneplus-one/
topfreitas said:
Have you guys seem this?
http://www.thejollablog.com/sailfish-os-oneplus-one/
Click to expand...
Click to collapse
That's just a followup from vgrades tweet, so nothing new. The information that he will share the build after MWC is down in the comments...
Guys Hi
As you see great progress made during MWC week on the port. Stskeeps from Jolla identified the bug stoppng UI coming up so we are go now.
Good to see the chase up on Multirom as this makes it easier for folks to test. I think it just needs to have a build which includes the sailfish patches included so any recent upstream build should suffice. On the add room page you should see a SailfishOs radio button.
Stay tuned for more details and drop into #sailfishos-poters channel on freenode IRC and say hello.
BR
vgrade
For those wanting to build their own images I've put my porting notes at http://piratepad.net/gVqPXuEGW4 , join us at #sailfishos-porters channel on IRC .
vgrade
vgrade said:
Guys Hi
As you see great progress made during MWC week on the port. Stskeeps from Jolla identified the bug stoppng UI coming up so we are go now.
Good to see the chase up on Multirom as this makes it easier for folks to test. I think it just needs to have a build which includes the sailfish patches included so any recent upstream build should suffice. On the add room page you should see a SailfishOs radio button.
Stay tuned for more details and drop into #sailfishos-poters channel on freenode IRC and say hello.
BR
vgrade
Click to expand...
Click to collapse
vgrade said:
For those wanting to build their own images I've put my porting notes at http://piratepad.net/gVqPXuEGW4 , join us at #sailfishos-porters channel on IRC .
vgrade
Click to expand...
Click to collapse
Zip Image link now in second post in thread.
vgrade
vgrade said:
Zip Image link now in second post in thread.
vgrade
Click to expand...
Click to collapse
phone does not boot
i am using philz recovery to flash the rom can that be a problem
MasalaMan said:
phone does not boot
i am using philz recovery to flash the rom can that be a problem
Click to expand...
Click to collapse
Yes, this recovery does not have a version of tar which supports the -j option so the sailfishOs rootfs is not extracted, please use the recommended recovery
vgrade
Hey guys its devut again informing you that HOX's Device tree is nearlyready!!!
UPDATE: DEVICE TREE IS NOW COMPLETE
Nearly
Yes Nearly because libdgv1 is still taking time
libdgv1
http://dmitry.gr/index.php?r=06. Thoughts&proj=04. Android M on Grouper
Here it states that we get a lot of problem because
Code:
dlopen()
is a POSIX COMPLAINT:crying::crying:
So here it is nearly perfect Marshmallow device tree
https://github.com/DevUt/android_device_htc_endeavoru/tree/Marshmallow-begins-part-1
I also have not tested it for new layout
If you are a developer then please check it
[ Do not go for storage_list.xml (as it is deleted , go for fsatb)]
Another issue (damn it)
Proprietary-files.txt has a problem ! Will fix it soon
DevUt said:
Another issue (damn it)
Proprietary-files.txt has a problem ! Will fix it soon
Click to expand...
Click to collapse
*finger crossed*
bopung said:
*finger crossed*
Click to expand...
Click to collapse
I think it will take alot of time cause it is verrryyyy confusing
Added issue section in my github repo
1 issue added
you guys also help me by telling me the issues in code
Should i add wiki to my repo to guide other developer?
Or should leave them on their own to figure out how to make libnvos and other thing works ( cause just looking at the tree you wont be able to understand because the patches are also in proprietary files )?
And another great news the device tree wil be ready till Monday!! :laugh: :good: ????????????
Device tree complete now no monday
DevUt said:
And another great news the device tree wil be ready till Monday!! :laugh: :good:
Click to expand...
Click to collapse
(After this many ppl)
Critic : Monday ? What! You are so slow DevUt!
DevUt : Sorry , Thats the way im!
DevUt : But for other HOX DEVS
DEVICE TREE IS NOW COMPLETE
NOW NO MONDAY
DEV GET THEIR HANDS ON!
Awesome!I was planning to get an s4 but since the hox will actually get mm I will stick to it.Great work,you are awesome dude
MaRtYy01 said:
Awesome!I was planning to get an s4 but since the hox will actually get mm I will stick to it.Great work,you are awesome dude
Click to expand...
Click to collapse
My pleasure dude
I predict you will see mm till mid may cause my net is slow
Thanks for Patience and all your support
But if you wanna try to make a rom from this tree you can (please check the issue section if there are none then please proceed to building if there is even 1 Stop ; I will fix it )
Guys i just found out that we need to have a newer version of twrp to flash marshmallow on our hox. So here's my thought
First i will Fix the device tree ( yes i will be adding some more. Patch files which are on my local pc)
Then as we already have the kernel available for marshmallow.
And then i will build the new twrp and it all in a post
Guys fact of the matter : HOX doesn't runs well on newer roms! And yes thats the bitter truth for every Phone once its old it losses its powet
But why
Here's a logical answer : It is in the way the developer makes the newer roms!
What !
Yes ! Actually the devs just patch some existing files and add some new ones and release it !
And i dont blame the devs for it cause nobody will waste his/her time in writing everything from kernel , Device tree ,proprietary files they sum upto millions and millions of files
Thats causes the problem.
So whats the solution
The solution is nothing! But as a HOX lover i would love to take this whole summer for HOX
So whats your plan
My plan is after releasing marshmallow i would work to write the whole thing scratch (not exactly scratch) but i will make it the most stable rom for HOX
I know im making many promises but believe me i would make them true :highfive:
Thank you for your work, I'm looking forward to marshmallows for HOX.
I'm out of the station for 10 days will come and back to work ASAP
Is this a rom?
sagor1 said:
Is this a rom?
Click to expand...
Click to collapse
The ROM is nearly ready ! Source code has been downloaded tweaks have been made to the device tree ( necessary for ROM ) so you will see the ROM soon . This thread was made to keep updated my fellow friends with my status
Guys bad news my laptop screen has disturbed it is showing vertical lines I will send to soon for repairs and continue until then see my github progress ! You have surprise in both the kernel and my own profile
DevUt said:
The ROM is nearly ready ! Source code has been downloaded tweaks have been made to the device tree ( necessary for ROM ) so you will see the ROM soon . This thread was made to keep updated my fellow friends with my status
Click to expand...
Click to collapse
With sense or without sense?
sagor1 said:
With sense or without sense?
Click to expand...
Click to collapse
Without, its based on cm13
Sent from my Nexus 7 using XDA-Developers mobile app
Hello everyone,
the question and disscussion is:
Do we get Lineage OS support in the Future? it does not matter if unofficial or official, but what do you think?
I saw the LeEco le Max 2 get some unofficial support, so it could be that some Devs will try it.
It would be awesome *_*
I think the problem is, that the community isn't that big like for the le Max 2, but maybe it will get bigger in the future.
What do you think? :good:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
I think, it's not discussion, but it is a question. So, it should be in "QUESTIONS & ANSWERS". Le Max 2 have bigger community, because this phone is cheaper and cheapest Le Max 2 was for 180-200$. This mobile is older. Our Le Pro 3 have few months and in future it could have more community and ROMs like this.
corvus said:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
Click to expand...
Click to collapse
Wooow! Someone interested?
It would be awesome!
:fingers-crossed:
Who could we talk to in order to get official support?
I dont know, but to get official support there should be at first a stable unofficial lineage OS Version. I do not know much about creating ROMs but i hope someone does and will create a masterpiece for le pro 3
I hope so
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
corvus said:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
Click to expand...
Click to collapse
Hi Corvus,
I've been trying to build slim from the repo you forked, but it keeps telling me I have no recovery, and ends up erroring out. I tried on ubuntu 16.04 lts though, could be my issue. Gonna try your lineage 13 version.
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
Would be awesome. I will try your build!
Good project looking forward to
manuelbvb said:
Would be awesome. I will try your build!
Good project looking forward to
Click to expand...
Click to collapse
I'll edit a link to the thread I make with to-dos based off the source code I can see.
Here's where I'll post progress!: https://forum.xda-developers.com/le-pro3/development/progress-lineage-os-13-t3546126
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
Hi @jts2111,
No problem from my side. TS team shared with me the sources, I modified them for Lineage, and try to do some tweaks (already uploades) and have some more in local, but causes some problems, so I didn't upload them.
With this image I get more than 3 days of batt time and a sot of 8 hours, so it's good for me. My only concern is that I was not able to make Camera2 HAL working to get manual settings. But I have little time to test, so any help from this side is welcome.
Only one thing, please, share the code in a public repo so TS, me or any other developer can see it and work together.
Thanks
---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
robertzas said:
Hi Corvus,
I've been trying to build slim from the repo you forked, but it keeps telling me I have no recovery, and ends up erroring out. I tried on ubuntu 16.04 lts though, could be my issue. Gonna try your lineage 13 version.
Click to expand...
Click to collapse
For Slim, please use the fork from where I get the code. See it in github. It's TS source, so it should work.
corvus said:
Hi @jts2111,
No problem from my side. TS team shared with me the sources, I modified them for Lineage, and try to do some tweaks (already uploades) and have some more in local, but causes some problems, so I didn't upload them.
With this image I get more than 3 days of batt time and a sot of 8 hours, so it's good for me. My only concern is that I was not able to make Camera2 HAL working to get manual settings. But I have little time to test, so any help from this side is welcome.
Only one thing, please, share the code in a public repo so TS, me or any other developer can see it and work together.
Thanks
Click to expand...
Click to collapse
I forked your repo and shared it in my post. I'll work on what you mentioned. One of my top (long term) goals is complete CTS compatibility. With safetynet passed, there'd be nothing that would really pull you back to stock.
Definitely, I'm preparing the Kernel code after code to ensure we get a very clean and functional Kernel for the future, instead of just merging the one from LeEco with more than 80% of unneeded bits due to their other devices being at the same place (shameful).
This will get a ~30MB Kernel reduced to around 12MB and thus make custom ROMs perform a lot better and boot immensely faster after all.
I'd only need one sense of common attitude which is asking LeTV to keep the Kernel source up-to-date when they launch OTAs as well, I've seen some comments regarding their image stabilization fix at latest release (OTA) which is only possible at Kernel/blob level and thus if we want to have this feature working (at least partially) we need the source code "right off the bat" to get those fixes. Please, make pressure on their forums for 5.9 x720 Kernel source code and for nougat preview builds, I'd appreciate to even help with their own EUI for that matter, I'll see if I can get in touch with them concerning those points.
Do we have someone from China or someone with experience with Chinese so we can attach our discussions there?
I do hope they keep the open source up to date, but it seems they are doing the bare minimum to apply to Google's open source policy. I'm in the US, so I have the x727 with 1 SIM. We would need someone to test with a x720 as well.
@GalaticStryder, Leeco only will post the sources needed to avoid license problems with GPL, so dont wait much help from them. But we can ask...
@jts2111, I have a 720, so I can test your builds.
@jts2111
I received my X720 this week and I could also test your experimental build.
It would be nice to already start with a LineageOS custom ROM as first ROM to avoid a lot of reinstallation / reconfiguration of apps with other kind of custom ROMs.
Hello,
As some people heard, i really try to get Android Wear 2.0 for our beloved SmartWatch 3.
And it's possible, sources, device trees, all exist to build a working own compiled Android Wear 2.0.
So this thread tells about the current process of the port
PROGRESS
Code:
Repo synced
First build finished (not buildable yet due no blobs included
GAPPS Porting in progress
Fixed to 99% the device tree
Updating Blobs to M1D64T in progress
Using own Device tree
SOURCES
Device Tree for tetra:
https://github.com/Sony-SmartWatch-3-OSS/android_device_tree_tetra_eng_prerelease
Device Kernel for tetra (unmodified):
https://android.googlesource.com/kernel/bcm/+/android-wear-6.0.1_r0.99
(we can use MM kernel on Nougat too, maybe some patches needed but that's okay)
Prebuilts/Blobs for tetra:
https://github.com/Sony-SmartWatch-3-OSS/vendor_prebuilts_tetra
For Discussions go to this thread please: https://forum.xda-developers.com/smartwatch-3/general/companion-thread-android-wear-2-0-t3565693
If you want to help me on this project, write to me via telegram: https://t.me/PDesire
I need that so much any ETA ?
By the way keep up the good work !
Nice to see someone is working on this :victory:
Sent from my Sony Xperia Z5 using XDA Labs
Thanks for your job.
Enviado desde mi Redmi Note 3 mediante Tapatalk
great!!! thanks
Dear PDesire,,
My support can be only moral..... :crying:
And I hoping good news soon from you
Thx again for your great hard work :good:
thankx you great hard work and good luck my friend
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Certain components of Android (and therefore Wear) come from third parties and have licenses which require the source code to be made available (e.g. the Linux kernel). The components made available via the AOSP repositories for releases like Wear are, afaik, the components which have that type of license.
Wear is a release which has taken the same path as Honeycomb. I can understand that for open source fans and people looking to tinker with a working system it’s somewhat disappointing to see, but those are the choices Google has made.
Click to expand...
Click to collapse
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
drakonizer said:
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
Click to expand...
Click to collapse
Yeah I've seen these, and already fixed. Patch comes soon.
Things for WLAN and BT for example are on google repo too and if a library or something is missing we can use it from M1D64T
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
Click to expand...
Click to collapse
Lel then I can't understand why the build is working xD at least I am building in time and already 14% finished
I know some libs we have to grab from the Marshmallow FW but that shouldn't be a big deal
At least we also need some things from Preview 2 so we can get our AW 2.0 Preview 2 working
So I try my best to grab much from source and if required also from FW, but all in all its possible for our SmartWatch 3 to get Android Wear 2.0
Your PDesire
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
xpatze85x said:
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
Click to expand...
Click to collapse
Because there aren't any sources of the final version.
@PDesire :
You're the man...keep up a good work ???
Hey @PDesire , any news? I'm sooooo hyped!!!
Thank bro I hope
Thanks for this!
So current status is:
Code:
Repo synced
First Test build stopped to fix things on device tree
Expected in future:
Code:
Blobs dump
Fully fixed Device tree
Creating vendor for tetra
Adding overlays for framework to device tree
Some mix with armv7-a-neon generic
Gapps Dump
Expected in far future:
Code:
Creating an OSS project for tetra (like sonyxperiadev but for tetra)
So guys I will do more tomorrow as I am awake already from Friday 7AM - 3AM Saturday (right now GMT +1) and working on it and I need my sleep xD
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Your PDesire
PDesire said:
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Click to expand...
Click to collapse
And I can confirm my donation is coming when a working build is ready, and I suppose others are coming, isn't it guys? ???
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Neo Cortex said:
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. That'll only work on an official firmware, unfortunately...
Thank you very much, hope you will finish it without problems~!