[Q] Sailfish OS port for Droid 4 - Motorola Droid 4

Since the N9 (OMAP3360) got a port for Sailfish OS I believe that a port for the Droid 4 is also possible. In fact I like the Droid 4 very much (Except of the accentuated Power-button, the buggy Headphonejack and the non pop up slider) and I would love to see Sailfish OS on this phone to have a real successor of the N900 and N950 in my Hands.
I would like to know, are im alone with that, or is someone else is also Interested in Sailfish OS on the Droid 4, or even already working on it.

Me Too
doener said:
Since the N9 (OMAP3360) got a port for Sailfish OS I believe that a port for the Droid 4 is also possible. In fact I like the Droid 4 very much (Except of the accentuated Power-button, the buggy Headphonejack and the non pop up slider) and I would love to see Sailfish OS on this phone to have a real successor of the N900 and N950 in my Hands.
I would like to know, are im alone with that, or is someone else is also Interested in Sailfish OS on the Droid 4, or even already working on it.
Click to expand...
Click to collapse
I have been looking for others interested in this! I have a Droid 4 with CyanogenMod 11, and I am totally interested in running SailfishOS! I'm not competent in porting yet--especially since my CM11 build failed (that's another story). Once again, I really want this!

The SailfishOS HADK is finally released! I have read through it, and it's a little over my head. I understood a lot of it though. I may try porting it in a couple weeks, maybe not. The only issue I am concerned about is the fact that we should have a stock Android version of 4.2.x. I'm super busy now.

Currently building, but stopped by an issue.
I've been following the guide in the HADK but when I run the breakfast command, make says "hardware/ti/omap4xxx/security/Android.mk" does not exist. Maybe I'm doing something wrong (I have little, but some, experience with building), but I'm not sure.

Very interesting. Is the folder there at all? I bet that the repo which has the TI stuff isn't downloaded.

No, it wasn't there at all. I ran an extract-files.sh script while connecting the Droid 4 to USB, and now make isn't spitting out any errors in breakfast maserati. When I run
Code:
make -j4 hybris-hal
make outputs
Code:
build/core/product_config.mk:253: *** No matches for product "full". Stop.
I also reproduced the files that make said were missing from searches on the internet (might not have been the best idea), so that's probably why it's not complaining.

Use this repo to get the files:
https://github.com/CyanogenMod/android_hardware_ti_omap4xxx
The next error doesn't make sense to me yet.

Any news on this?
Hey there! I am also highly interested in this. Any progress on the build? Would actually be willing to spend some money for this. So if anyone is up for setting up a goal, I'd pledge 20$, too.

xnopasaranx said:
Hey there! I am also highly interested in this. Any progress on the build? Would actually be willing to spend some money for this. So if anyone is up for setting up a goal, I'd pledge 20$, too.
Click to expand...
Click to collapse
We've (or I have, rather) run into a roadblock. I need to get the right repos, and I'm not sure I have the SDKs set up properly. Like I said, I have little experience in building, just did this as a weekend project (yeah, thought it'd be that easy).

dmon633 said:
We've (or I have, rather) run into a roadblock. I need to get the right repos, and I'm not sure I have the SDKs set up properly. Like I said, I have little experience in building, just did this as a weekend project (yeah, thought it'd be that easy).
Click to expand...
Click to collapse
Haha. I thought it would be easy, but then I read the HADK. I don't have much experience with building either, but I have a good understanding of tech so I have some sort of advantage.

dmon633 said:
No, it wasn't there at all. I ran an extract-files.sh script while connecting the Droid 4 to USB, and now make isn't spitting out any errors in breakfast maserati. When I run
Code:
make -j4 hybris-hal
make outputs
Code:
build/core/product_config.mk:253: *** No matches for product "full". Stop.
I also reproduced the files that make said were missing from searches on the internet (might not have been the best idea), so that's probably why it's not complaining.
Click to expand...
Click to collapse
The error makes more sense to me now. It means that it can't find anything to build by the name of "hybris-hal".
I think I will try to port Sailfish myself really soon. I had a pretty good experience building CM 11. I also tried to make a vanilla AOSP KitKat ROM using a few CM files. So far I have fixed a few build errors but then ran into another one. I haven't been able to fix that one yet. I learned a lot about how to build Android, so now I want to try my hand at porting Sailfish.

dmon633 said:
I've been following the guide in the HADK but when I run the breakfast command, make says "hardware/ti/omap4xxx/security/Android.mk" does not exist. Maybe I'm doing something wrong (I have little, but some, experience with building), but I'm not sure.
Click to expand...
Click to collapse
OK, go ahead and delete the "omap4xxx" folder if you have one then add it to your local manifest.
Here is what mine looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="prebuilt" name="CyanogenMod/android_prebuilt"/>
<project name="CyanogenMod/android_device_motorola_maserati" path="device/motorola/maserati" revision="cm-10.1"/>
<project name="CyanogenMod/android_device_motorola_omap4-common" path="device/motorola/omap4-common" revision="cm-10.1"/>
<project name="CyanogenMod/android_kernel_motorola_omap4-common" path="kernel/motorola/omap4-common" revision="cm-10.1"/>
<project name="CyanogenMod/android_hardware_ti_omap4xxx" path="hardware/ti/omap4xxx"/>
<project name="CyanogenMod/android_hardware_ti_wlan" revision="cm-10.1" path="hardware/ti/wlan"/>
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" revision="cm-10.1"/>
</manifest>
Using this manifest, I successfully built hybris-hal!!! That's not everything that needs to be done, but it's a start.
Oh yeah, you also need to edit "$ANDROID_ROOT/hybris/hybris-boot/fixup-mountpoints" and "$ANDROID_ROOT/device/motorola/maserati/recovery.fstab"
Maybe I will learn how to put it on GitHub...

Nice! Good progress. Keep us updated. I would like to test this if it works.

mo0n_sniper said:
Nice! Good progress. Keep us updated. I would like to test this if it works.
Click to expand...
Click to collapse
I'm trying to port CyanogenMod 12.0 right now. I will go back to work on Sailfish soon.

theprogramguy said:
I'm trying to port CyanogenMod 12.0 right now. I go back to work on Sailfish later.
Click to expand...
Click to collapse
I am very interested in the possibility of running Sailfish OS on Droid 4 or Photon Q. Keep me up to date!

Last time I worked on it, I was trying to fix some issues with the kernel configuration. Sailfish doesn't support some of the original values. I made changes but I have no idea what it will do if I ever get to run this on my phone!

I've been trying to work on it for a few days. For some reason I can't get it to build hybris-hal, which is strange since I've done it before.

Just spreading the word (link):
TheKit said:
I'm currently doing Droid 4 port. Plan to post it once the basic things are fixed (currently missing sound input and camera at least).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse

Flash-A-Holic said:
Just spreading the word (link):
Click to expand...
Click to collapse
Thanks Flash-A-Holic. Can't wait for this either. Please let us know if spot any more updates.

Flash-A-Holic said:
(link):
Click to expand...
Click to collapse
ultra :good:
plz send me your mail address via PM you earn half the bounty for bringing up a wayland OS on droid 4. way to go.
EDIT: Oh. It's TheKit's work. Well. Anyway. Good to have a keyboard wayland debian phone in sight

Related

Congrats to CM

Cyanogen goes from from Android mod to legit startup with $7M from Benchmark
http://venturebeat.com/2013/09/18/c...-mod-to-legit-startup-with-7m-from-benchmark/
Hopefully we see good things in the foreseeable future, gotta love what CM has done for all of us :thumbup:
Sent from my One using Tapatalk 4
This guy is a legend.
Good luck to Steve... I would be willing to at least try out a Cyanogen OS phone.
Sent from my beige box using xda premium
Even though I do not use CM.
I wish them the BEST!!!
I hope they become 2nd. Not 3rd
Because....
"Apples are meant for eating...period."
sent from my HTC ONE using Aftermath + Elemental X and XDA-Developers app.
Cyanogenmod was the first rom i ever flashed. Seeing it grow up kinda brings a tear to my eye :crying: . Best of luck Steve im sure it will be popular!
Does anyone else realize how nuts this is? I mean, from a back door, unlicensed, hackers, weekend project to a full fledged entity that directly competes against big name software. All for free. This is amazing and can only get better congrats to them and the whole android hacker community!
Sent from my HTCONE using xda app-developers app
Did anybody actually read the article?
Am I the only one confused about the CM installer off Google Play? Wut
Can anybody explain how non rooted users can switch to CM via an app from the Play Store?
Here is the full blog by the guy himself.
http://www.cyanogenmod.org/blog/a_new_chapter
Sent from my Desire HD using xda app-developers app
sauprankul said:
Did anybody actually read the article?
Am I the only one confused about the CM installer off Google Play? Wut
Can anybody explain how non rooted users can switch to CM via an app from the Play Store?
Click to expand...
Click to collapse
I'm pretty sure the CM installer will require root, I mean there are plenty of apps that requires root on the PlayStore.
I'm curious of how they will eventually monetize this. $7mil is no small investment, the invester will expect a return? I'm pretty sure if cm came shipped with a phone it might be without root. If you followed Steve K on plus he posted a question about the reasons why users want root and he said it was possible to achieve most of it without root with coding and thus will provide a more secure environment.
I thought this was funny
https://plus.google.com/100275307499530023476/posts/Y1NNyPMMVfN
im0rtalz said:
I'm pretty sure the CM installer will require root, I mean there are plenty of apps that requires root on the PlayStore.
I'm curious of how they will eventually monetize this. $7mil is no small investment, the invester will expect a return? I'm pretty sure if cm came shipped with a phone it might be without root. If you followed Steve K on plus he posted a question about the reasons why users want root and he said it was possible to achieve most of it without root with coding and thus will provide a more secure environment.
Click to expand...
Click to collapse
If it does require root, what exactly is the point? I'm sure most people who go through the trouble of rooting their devices have at least heard of CM, if not used it. This really won't "expand the user base" or whatever unless it can painlessly root your phone from stock. Which I'm pretty sure it can't do. Plus, He also writes about how the rooting process is "gruesome" and he thinks it is unnecessary. Maybe he has/will figure out a way to get CM on our phones without root? He said next few weeks, so... let's see.
sauprankul said:
If it does require root, what exactly is the point? I'm sure most people who go through the trouble of rooting their devices have at least heard of CM, if not used it. This really won't "expand the user base" or whatever unless it can painlessly root your phone from stock. Which I'm pretty sure it can't do. Plus, He also writes about how the rooting process is "gruesome" and he thinks it is unnecessary. Maybe he has/will figure out a way to get CM on our phones without root? He said next few weeks, so... let's see.
Click to expand...
Click to collapse
I meant that their goal would be to have a partnership with oems and have devices that comes with cm pre-installed so there would be no need for root it might just update thru the stock recovery just the same as a regular ota would be. Well everything is just speculation but from the looks of focal then voice+ there is going to be so many good things to come. A revamp theme engine that rivals miui maybe.
Sent from my SPH-D710 using Tapatalk 2
im0rtalz said:
I meant that their goal would be to have a partnership with oems and have devices that comes with cm pre-installed so there would be no need for root it might just update thru the stock recovery just the same as a regular ota would be. Well everything is just speculation but from the looks of focal then voice+ there is going to be so many good things to come. A revamp theme engine that rivals miui maybe.
Click to expand...
Click to collapse
If I were a multi billion dollar company, I wouldn't exactly want to outsource my OS development to a small hacking startup.
It would be cool, but I think it's not possible right now, at least, not with mainstream OEMs.
Oppo? Probably. Samsung HTC Sony etc? Prolly not.
And he specifically mentioned the installer right after the "rooting is gruesome" thing. I think that's a good clue.
EDIT: Maybe something like a "CM edition" will work, just like GPe?
Also, did anyone notice the iPhones in
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Although I don't typically use it as a stand-alone ROM, most of the ROMs I build and like best are based in CM. They have a great team and embody everything about open-source that users, devs and aspiring devs want to emulate. I think it's high time they receive the recognition they deserve and a top spot in the Android and mobile OS forum. Best of luck, guys!
Started from the bottom now he here! Congrats to Steve and the whole CM team. Reminiscing about the CM6 days to where CM is now always brings a tear to my eyes. Lol.
Sent from my HTCONE using Tapatalk 4
sauprankul said:
If I were a multi billion dollar company, I wouldn't exactly want to outsource my OS development to a small hacking startup.
It would be cool, but I think it's not possible right now, at least, not with mainstream OEMs.
Oppo? Probably. Samsung HTC Sony etc? Prolly not.
And he specifically mentioned the installer right after the "rooting is gruesome" thing. I think that's a good clue.
EDIT: Maybe something like a "CM edition" will work, just like GPe?
Also, did anyone notice the iPhones in
Click to expand...
Click to collapse
I noticed all the iDevices and was very intrigued by it. CM on iOS devices? That's something I can get excited about.
Sent from my One using xda app-developers app
"The firm's first announced step is to improve the process of installing the software on owner's devices, which Kondik described as "hideous". A new installer app is planned to be released "in the coming weeks" on Google Play. The installer app will not require rooting the device, instead installing by simply clicking a button."
http://en.m.wikinews.org/wiki/CyanogenMod:_Open-source_smartphone_OS_goes_commercial?dpl_id=785316
If that's true, the CM will be an instant hit.
I wonder if this will void warranty since you basically just installed an app. Also, I know I'll be laughed at, but will not having root fix the frequency lock issue?
my main question when i install CM in the future will it be a close to stock android experience that we all know and love or are they looking to do something like amazon(just not terrible) and use android as a base
turtleman2008 said:
my main question when i install CM in the future will it be a close to stock android experience that we all know and love or are they looking to do something like amazon(just not terrible) and use android as a base
Click to expand...
Click to collapse
dude. C'mon.
Really?
C'mon.
The whole point of CM is to get closer to the stock experience. It's just that now, overlays like TW and Sense don't suck. CM is upping their ante to compete with these guys (Hence the project name Nemesis). They are introducing features like CM accounts and focal, which don't detract from the experience.
It would be suicide for CM to completely run away with Android like that.
sauprankul said:
If that's true, the CM will be an instant hit.
I wonder if this will void warranty since you basically just installed an app. Also, I know I'll be laughed at, but will not having root fix the frequency lock issue?
Click to expand...
Click to collapse
Looks like the installer will only work on unlocked *bootloader unlocked* and developer editions, they are hoping more manufacturers will eventually offer offical unlock, similar to HTC dev unlock I am thinking. So it isn't going to magically install CM on any device.
CyanogenMod will have its own installer app “in the coming weeks” which will be available in the Play Store. Initially the app will not install CyanogenMod on devices for which unofficial exploits were used to unlock their bootloaders. Steve Kondik (cyanogen himself if you didn’t already know) had this to say about the installer app:
The first release of the installer won’t support devices that require exploits. The long-term goal is to open up OEMs to the possibility of supporting us officially- there’s zero technical reason for these measures and the best way to fix it is to not buy these devices and speak your mind.
…
It’s more important to me to work with OEMs on changing policy than developing exploits, though. And we’ll do that by creating great stuff that people want to use.
The app should work seamlessly on your Nexus device, your Developer Edition device or your device for which an official bootloader unlock is available.
Also some interesting read on focal https://plus.google.com/106978520009932034644/posts/L8FJkrcahPs

[ANSWERS] All the answers

Hey there,
xplodwild here, I did the announcement session at BABBQ, it was awesome. Thanks for everyone who were there.
So yeah, we didn't prepare a lot of YouTube demo videos yet, but all the information about the philosophy of Omni are available on Omni website: http://omnirom.org/why-omni/.
We are a ROM different than others: we are focused on performance, cohesion, stability, innovation, code quality, community and open source. And the community more than anything else. You are using the ROM, you should be choosing what you want to have.
When we're taking a patch from another ROM, we're trying as much as possible to enhance it before merging it. When we're getting new features, we give you a way to give early feedback, early access to prototypes, early access to mockups, etc, so that we know immediately early on if we're doing it right.
All the contributions will be GPL licensed (at least we'll be pushing for it). People will be able to vote up and down on patches,
Some of the key features of Omni:
Flippable Quick Settings
Roadrunner mode
Multi-window(!)
Daydream enhancements
Integrated Performance Control
Multi-workspace
Color-changeable, 3D depth Phase Beam
And a bunch more
We're also pushing non-Android stuff, such as OmniInstaller (an all-in-one, multi-platform, open source, installer that anyone can plug in), as well as a Qt library to give Qt Android apps a native Android look, and have gorgeous and super-fast Android apps. We're helping users, and helping developers.
Everything is free, free as in money, and free as in liberty. And transparent.
Edit #1: Regarding device support, we currently support all the Nexus devices, as well as the Oppo Find 5, Xperia Z, Xperia Tablet Z. We have preliminary support for the i9300 as well as the Oppo R819.
Edit #2: We'll have a bunch of developer resouces up soon, giving a head start to newcomers in the Android development world.
I probably didn't cover much things but I'll add more things as they come to my mind. We're having beers here and I'm probably not fully able to do a comprehensive post right now.
Have some screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NIce! Does that "multiwindow" works flawlessly?without breaking apps?
I'm overjoyed to see you guys bounce back after the Inc debacle.
Looking forward to compiling, testing and enjoying Omni.
Are you guys going to kang features from other ROMs (Halo and Pie from PA for example) or will all features be developed in-house?
Also, on which Android-version are the first builds based? I guess 4.3.1?
Since the annoucement of Cyanogen to be a corporation, I was searching for a new AOSP-based ROM for my daily needs, and I think I found it. Good luck guys!
I m dying to try this rom.
Would it be possible to port it using cyanogenmod or aosp as base?
chasmodo said:
I'm overjoyed to see you guys bounce back after the Inc debacle.
Looking forward to compiling, testing and enjoying Omni.
Click to expand...
Click to collapse
Me, two©. Joli coup @XpLoDWilD @Entropy512 and everyone else involved, wishing you all the best with Omni. Nice to see espenfjo back on track as well.
#free^3
They say all nexuses are supported , then where is galaxy nexus support huh ? If there will be not official support , how can I develop a unofficial version of OMNIr for gnex ?
sakindia123 said:
NIce! Does that "multiwindow" works flawlessly?without breaking apps?
Click to expand...
Click to collapse
It will do pretty much. We'll get sources up very very soon (ie. minutes), and gerrit is already live where you can see the MultiWindow patch being reviewed and improved.
SGWUser said:
Are you guys going to kang features from other ROMs (Halo and Pie from PA for example) or will all features be developed in-house?
Also, on which Android-version are the first builds based? I guess 4.3.1?
Since the annoucement of Cyanogen to be a corporation, I was searching for a new AOSP-based ROM for my daily needs, and I think I found it. Good luck guys!
Click to expand...
Click to collapse
In the spirit of open source, if there's something that gives positive improvement on the user experience, and it can be introduced, and people want it, it will be included. There's a balance between "settings inception" (ie. a toggle for your toggle, to toggle text alignment of the clock) and something that isn't customisable, but that will be open to much wider discussion and consultation.
4.3.1 is the current version in use, yes.
Halo and Pie are 2 specific examples, but this is where the community comes in - porting these features should be fairly straightforward. We like to try improve things too where possible
AndroidAddiction said:
I m dying to try this rom.
Would it be possible to port it using cyanogenmod or aosp as base?
Click to expand...
Click to collapse
The ROM is based on AOSP, and full sources will be posted today, meaning you can try to build it for yourself. Be aware though, not all chipsets are currently supported - nexus devices will have more luck than other devices for now, but that will obviously change in the coming days and weeks.
Ashutos1997 said:
They say all nexuses are supported , then where is galaxy nexus support huh ?
Click to expand...
Click to collapse
I don't believe anyone has one here for testing, hence it has not been listed yet. it WILL be supported, but until it's been tested, it won't go onto the list
Have the additional selinux commits CM started picking a few months ago been picked here also? If so, would make getting a build up for the Sprint and Verizon GNote 2 much easier Now it's just a waiting game for source to drop.
Sent from my Nexus 7 using Tapatalk 4
slick_rick said:
Have the additional selinux commits CM picked a few months ago been picked here also? By that I mean the 2nd commit from the top to the next page https://github.com/CyanogenMod/android_frameworks_base/commits/cm-10.2?page=15 If so, would make getting a build up for the Sprint and Verizon GNote 2 much easier Now it's a waiting game for source to drop.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
We've not focused yet that much on SELinux, as generally we believe that features like this should be introduced once the tree is stable enough.
There's still work needing done for SoCs (like Exynos!), but once we have the ground work covered, make no mistake, SELinux will be in and securing. Until then though, it will not be a number 1 priority (not to say nobody can go fix it!) - that's the glory of open source
Hurray!
a small query,do you plan to include support for legacy devices?(for example, the video encoding/decoding patches for msm7x27/7x27a)?
Currently,no roms support this by default.
Great News.
pulser_g2 said:
We've not focused yet that much on SELinux, as generally we believe that features like this should be introduced once the tree is stable enough.
There's still work needing done for SoCs (like Exynos!), but once we have the ground work covered, make no mistake, SELinux will be in and securing. Until then though, it will not be a number 1 priority (not to say nobody can go fix it!) - that's the glory of open source
Click to expand...
Click to collapse
Makes sense. I use modified CM trees to build for PA which doesnt have that extra selinux stuff so building should still be pretty painless I hope. Last question, let's say I wanted to add PA Pie support in an aio patch or so, would I just push to gerrit and from there the core team and users vote on it? Considering its stable and working fine. How will that work? Thanks!
Sent from my Nexus 7 using Tapatalk 4
sakindia123 said:
NIce! Does that "multiwindow" works flawlessly?without breaking apps?
Click to expand...
Click to collapse
Still work to be done. I just barely got it working on flo and pollux_windy before flying out to BABBQ.
What's the Roadrunner feature?
sakindia123 said:
a small query,do you plan to include support for legacy devices?(for example, the video encoding/decoding patches for msm7x27/7x27a)?
Currently,no roms support this by default.
Click to expand...
Click to collapse
Yes, we intend to include legacy device support as a key feature. I'll go into this in more detail later, but this was one of our founding "aims".
Provided compatibility for legacy devices can be implemented "neatly" without impacting other devices, it's actively encouraged
Custom ROMs were meant to extend the useful lives of phones, not leave phones dangling without support
hikarugo said:
What's the Roadrunner feature?
Click to expand...
Click to collapse
Roadrunner was the "speculated" feature name for a previous version of Android where some people suggested that it would improve battery life, and add better power profiles and management.
Roadrunner was something Xplod is working on, but it aims to make it possible to easily and quickly bias your device's configuration for performance, or battery, or a balance between the two.
On a modern device with 4 cores, and 2.2 GHz CPU (or whatever), this is frankly excessive for simple tasks. OEMs usually excessively prioritise performance so their device feels "snappy", leaving battery performance poor.
Roadrunner lets you reduce "raw" speed, but gain better battery life.
pulser_g2 said:
Yes, we intend to include legacy device support as a key feature. I'll go into this in more detail later, but this was one of our founding "aims".
Provided compatibility for legacy devices can be implemented "neatly" without impacting other devices, it's actively encouraged
Custom ROMs were meant to extend the useful lives of phones, not leave phones dangling without support
Click to expand...
Click to collapse
I will try to get @PecanCM involved, as well as the members from androidarmv6. They'll have a few patches to push up
Because we use different sets of qcom hardware sources, can I ask for them to be able to be fetched from different github users/organisations, just to keep the source code tidier?
Sent from my Nexus 7 using Tapatalk now Free

100$ challenge for first OnePlus 7 pro custom ROM developer

Hi guys I am conducting small program to motivate developers .
I will donate 100$ to first custom ROM for OnePlus 7 pro developer.
Conditions:
All basic functionality working.
I'm honestly surprised that we don't have any custom roms yet
chandra1.jd said:
Hi guys I am conducting small program to motivate developers .
I will donate 100$ to first custom ROM for OnePlus 7 pro developer.
Conditions:
All basic functionality working.
Click to expand...
Click to collapse
How about donating to @phhusson because the AOSP GSI he works on pretty much has all basic features working with the exception of finger print sensor but giving how long it took to get an under-screen sensor working for OP6T that might be a long way off yet.
Regards,
Ravi
rav101 said:
How about donating to @phhusson because the AOSP GSI he works on pretty much has all basic features working with the exception of finger print sensor but giving how long it took to get an under-screen sensor working for OP6T that might be a long way off yet.
Click to expand...
Click to collapse
(I didn't check the thread or anything, I'm just answering to this post)
FWIW, on Mi9, I fixed under-display fingerprint less than three days after getting it. (more precisely, after I got bootloader unlock because of stupid Xiaomi 2 weeks bootloader lock).
Also I've been told that pop-up camera doesn't work well on OP7Pro too. Though this should be quite easy to fix.
(I'm currently working on K20 rather than OP7Pro for the moment though)
Then I'm supposedly getting an OP7 from OP, but I haven't got much news.
Someone say AOSP?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Exathi said:
I'm honestly surprised that we don't have any custom roms yet
Click to expand...
Click to collapse
I think the devs are waiting until all the OnePlus 7/7 Pro models are out and all the sources are available so they're not starting again and again.
phhusson said:
(I didn't check the thread or anything, I'm just answering to this post)
FWIW, on Mi9, I fixed under-display fingerprint less than three days after getting it. (more precisely, after I got bootloader unlock because of stupid Xiaomi 2 weeks bootloader lock).
Also I've been told that pop-up camera doesn't work well on OP7Pro too. Though this should be quite easy to fix.
(I'm currently working on K20 rather than OP7Pro for the moment though)
Then I'm supposedly getting an OP7 from OP, but I haven't got much news.
Click to expand...
Click to collapse
I used your 9phh treble build and it actually works really well. But yes, camera pops up and wont come down, have to give it a manual tap and it closes. FP, yep, non existent. But other than that, its pretty stable and useable. Glad to hear you are getting one. If you need logs etc, let me know and ill get them to you. Or ill just wait till you get yours.
---------- Post added at 07:15 AM ---------- Previous post was at 07:13 AM ----------
liam_davenport said:
Someone say AOSP?
View attachment 4774680
Click to expand...
Click to collapse
Gimme Gimme
Exathi said:
I'm honestly surprised that we don't have any custom roms yet
Click to expand...
Click to collapse
I'm not. "CUSTOM" ROMs are getting more and more obsolete, especially as long as smartphone OEMs churn out decent stock ROMS, like Oneplus.. Or if certain OEM rom features can't work nice on a custom rom. Even so, it's a lot easier to just improve OOS as is; hard to compete since at heart, OOS is a ROM everyone helped to develop somehow. The only things that seem to matter is - DARK THEMES and themeability, which don't need a custom rom. - Magisk root modules -[ed]Xposed modules -kernels.. If a custom ROM could pack all stock rom features with actual additional features (maybe dual audio, 4k HDR recording, idk)..
Not meaning to talk garbage to all custom rom makers, but it's no longer as essential as it was. There's "better" things to work on, as people have less time to do stuff, or as android just gets better.
miffymiffy said:
I used your 9phh treble build and it actually works really well. But yes, camera pops up and wont come down, have to give it a manual tap and it closes. FP, yep, non existent. But other than that, its pretty stable and useable. Glad to hear you are getting one. If you need logs etc, let me know and ill get them to you. Or ill just wait till you get yours.
---------- Post added at 07:15 AM ---------- Previous post was at 07:13 AM ----------
Gimme Gimme
Click to expand...
Click to collapse
Fixing up a few things then will post it!
To Do list:
USB, Front Cam, NFC.
Il happy donate some to for an AOSP ROM
liam_davenport said:
Someone say AOSP?
View attachment 4774680
Click to expand...
Click to collapse
Need developer info ..if u have please share it ...
rav101 said:
How about donating to @phhusson because the AOSP GSI he works on pretty much has all basic features working with the exception of finger print sensor but giving how long it took to get an under-screen sensor working for OP6T that might be a long way off yet.
Regards,
Ravi
Click to expand...
Click to collapse
For sure I will donate by this month end ...
(FWIW I started reverse-engineering popup camera support in https://github.com/phhusson/treble_experimentations/issues/558 )
Just watching this thread, hoping @Eliminater picked up an OP7 or 7 Pro
djsubterrain said:
Just watching this thread, hoping @Eliminater picked up an OP7 or 7 Pro
Click to expand...
Click to collapse
He did
djsubterrain said:
Just watching this thread, hoping Eliminater picked up an OP7 or 7 Pro
Click to expand...
Click to collapse
As soon someone post source, he'll build 100%
So one of the devs on Carbon ROM team are awaiting to get OP7 Pro. So we should see Carbon on here too!
miffymiffy said:
I used your 9phh treble build and it actually works really well. But yes, camera pops up and wont come down, have to give it a manual tap and it closes. FP, yep, non existent. But other than that, its pretty stable and useable. Glad to hear you are getting one. If you need logs etc, let me know and ill get them to you. Or ill just wait till you get yours.
---------- Post added at 07:15 AM ---------- Previous post was at 07:13 AM ----------
Gimme Gimme
Click to expand...
Click to collapse
What were your steps to get a GSI to work on our device? I couldn't get it to boot
I vooted it easily. Follow Google's method. For flashing Android 10 gsi then fastboot -w and flash everything needed. Should boot fine. Ran Omni the other day
Not sure if anyone has tried, but im guessing the 6t fp fix does not work on the 7/pro so it will need rebuilt from scratch again?

Several questions for the current state of the phone

Hey all,
So I just got the new June 1 update (OPSS28.65-36-11-4).
Been thinking that since the whole thing with newer stuff needing to comply soon on Play Store if memory serves right, it was about time I evaluated if I should be considering updating my phone with one of the other roms. Just been curious given that I believe there is still no official download to force the phone from 32-bit to 64-bit.
So even if it is, I've been lovin the Fingerprint sensor for several things and personally, been liking the whole time/weather widget which I believe is tied to the launcher and I would lose if I changed so I'd guess I'd have to replace that, but at the same time, I just don't feel the need for root so its not something I am worried about having. Last time I did any of the rom patches, it was with the Nexus 7 so not quite sure how much has changed in that regard.
Should I be looking into the 64-bit roms available and if so, what ones would fit based on the no real need for root while still maintaining some of the things I enjoy of the Moto phone (including moto Gestures)?
For the record, I don't do Pie but as far as Oreo custom ROMs go, almost all of them have Moto Gestures/Actions which is quite cool. Compared to stock they offer a lot more gesture choices.
5 gestures with some 14 screen-on fingerprint actions and 8 screen-off. Not bad.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Other items like the Moto clock/weather widget and other Moto items are available for flashing. Take a look at this thread (mostly inactive) but its related Telegram channel has all the activity and later downloads.
https://forum.xda-developers.com/showthread.php?t=3746457
[MOD][Pixel-MODS]for any ROM[9.0][20190110][Moto G5s Plus]
Moto G5S Plus XT1806, AOSiP 8.1 ROM, microG (NoGapps), MultiROM, XDA Legacy
zapoqx said:
Hey all,
So I just got the new June 1 update (OPSS28.65-36-11-4).
Been thinking that since the whole thing with newer stuff needing to comply soon on Play Store if memory serves right, it was about time I evaluated if I should be considering updating my phone with one of the other roms. Just been curious given that I believe there is still no official download to force the phone from 32-bit to 64-bit.
So even if it is, I've been lovin the Fingerprint sensor for several things and personally, been liking the whole time/weather widget which I believe is tied to the launcher and I would lose if I changed so I'd guess I'd have to replace that, but at the same time, I just don't feel the need for root so its not something I am worried about having. Last time I did any of the rom patches, it was with the Nexus 7 so not quite sure how much has changed in that regard.
Should I be looking into the 64-bit roms available and if so, what ones would fit based on the no real need for root while still maintaining some of the things I enjoy of the Moto phone (including moto Gestures)?
Click to expand...
Click to collapse
There's no real advantage to 64 bit on this device. I've run both (32 and 64) and decided to stick with 32 bit as everything works, and works well. Couldn't find a 64 bit in which everything actually worked. May just be cuz I have the US version and all the "devs" are not from the US, but there's always something that doesn't work, or doesn't work as well.
marcdw said:
For the record, I don't do Pie but as far Oteo custom ROMs go, almost all of them have Moto Gestures/Actions which is quite cool. Compared to stock they offer a lot more gesture choices.
5 geatures with some 14 screen-on fingerprint actions and 8 screen-off. Not bad.
Other items like the Moto clock/weather widget and other Moto items atee available for flashing. Take a look at this thread (mostly inactive) but its related Telegram channel has all the activity and later downloads.
https://forum.xda-developers.com/showthread.php?t=3746457
Click to expand...
Click to collapse
Thanks for this info.
Phazmos said:
There's no real advantage to 64 bit on this device. I've run both (32 and 64) and decided to stick with 32 bit as everything works, and works well. Couldn't find a 64 bit in which everything actually worked. May just be cuz I have the US version and all the "devs" are not from the US, but there's always something that doesn't work, or doesn't work as well.
Click to expand...
Click to collapse
The other thing is if the compliance is supposed to be about 64-bit, I may have an issue of an app that I need to not work. But I do have the US version (XT1806). Been on it since last year just as the G6 series was coming out (and my unfortunate disdain for them not giving the Plus models to the state side) so I figure at least, it should last me until a later one comes out that is actually more powerful than what I have. Also, I sometimes like to have some games on the go very quick. Not the Fortnite or PUBG variety, but I figure that if the games have to add compliance as well, I may lose out on some. So I get what you're saying. But I am kinda trying to figure my options too from all perspectives.
But would you mind explaining some examples of things that didn't work? Maybe if its something that wouldn't bother me, I can figure from there.
[Ugh. Sorry for all the typos in my last post.]
If I'm not mistaken, the OEM stock ROMs are 32-bit but the custom ROMs are all 64-bit. So I guess there's not really a choice between architectures.
On the user end of things I haven't experienced anything that runs on one but not the other. I still have the stock Nougat (32-bit) installed along with several Oreo ROMs (64-bit). If anything I may see an issue with an app that runs fine on Nougat but not so well on Oreo but that's rare.
Moto G5S Plus XT1806, AOSiP 8.1 ROM, microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
[Ugh. Sorry for all the typos in my last post.]
If I'm not mistaken, the OEM stock ROMs are 32-bit but the custom ROMs are all 64-bit. So I guess there's not really a choice between architectures.
On the user end of things I haven't experienced anything that runs on one but not the other. I still have the stock Nougat (32-bit) installed along with several Oreo ROMs (64-bit). If anything I may see an issue with an app that runs fine on Nougat but not so well on Oreo but that's rare.
Moto G5S Plus XT1806, AOSiP 8.1 ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
Ya I get it, just one of those precautions. I am still more or less baffled that the OEM is 32-bit even after the story and how almost any other phone, I can find the stock rom so easy to deal with, but this one, I can't even get it unless I look at someone else pulling their own.

ZTE Axon 10 Pro US bootloader unlock request

It looks like ZTE is back again with another flagship killer with an unbelievable price! With 8+256 for $549 and 12+256 for $599 this will be the device to beat the rest of 2019 and well into 2020. However, one thing will separate the Axon 10 Pro from the OnePlus 7/7T going forward and that is an official bootloader unlock from ZTE. The inclusion of microSD support has me wanting this phone more than any out currently. Hopefully the bootloader is unlockable out of box, but if not, please, ZTE, if you happen to read this, PLEASE include an official bootloader unlock, preferably one that doesn't affect widevine L1 so we can enjoy a flourishing development community as well as high quality video on this display.
XDA, let's show ZTE how great this device can be with your support in backing an official bootloader unlock for the Axon 10 Pro!
Join the discussion on Z-community and make your voices heard:
https://community.zteusa.com/discussion/54800/axon-10-pro-bootloader-unlock-request
Unlock Bootloader will be awesome, and having You as well as @Unjustified Dev as developers will rock this device even more like Axon 7 did.
If ZTE is watching, I just want to say thanks.
I remember receiving a PM from @DrakenFX 3 years ago about this new phone THE ZTE AXON 7! Doesn't that sound cool? It wasn't the first time we crossed paths or second here on XDA.
At the time, ZTE was known for stripping devices of fastboot mode. Regardless of my novice skills, I still took on the challenge.
Shortly after coming into the community and learning about this device and meeting some great people, I received another PM! A guy asked for my address to send me a device! Yes, that's correct, my first device was actually bought by one member of XDA.
The joy of that day can never be explained or replicated again. I received my device a bit later which was good because ZTE had just released the OTA file that allowed B20 to be unlocked and brought back fastboot which is stripped on all of their devices that I've ever worked with.
In less than a week we had CM-13.0 running, but there were so many things we couldn't figure out.
Before I knew it, ZTE reached out to me and a few other CyanogenInc developers. They helped us fix Audio, fingerprint, sensors, VR, Camera, and I'm betting even more. I am considering getting the Axon 10 Pro myself if I don't receive one from ZTE or anyone else
I think we're all asking for you to be the same ZTE that left us with the Axon 7 one of the most influential devices in your history.
Already prepared for this amazing device http://files.nwwn.com/~unjust/Axon 10 Pro/LineageOS/
I went from my axon 7 to onplus my daughter now has my axon 7 and she loves it
If bootloader unlock is there I am definitely jumping back to ZTE from OnePlus
Lineage 16.0
@Unjustified Dev What base firmware did you use to build Lineage 16.0?
Thanks
Bill
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How did you do that?
I hope that it does not take long until we can all unlock the BL
and we get TWRP for axon 10
Chris axon 7 said:
How did you do that?
I hope that it does not take long until we can all unlock the BL
and we get TWRP for axon 10
Click to expand...
Click to collapse
Unlock Bootloader is possible at the moment (thanks to @Unjustified Dev and if not mistaken is or will work on TWRP, but will see....:good::good:
I know that we shouldn't ask about timelines but hey what's the status on this?
marcusah123 said:
I know that we shouldn't ask about timelines but hey what's the status on this?
Click to expand...
Click to collapse
Timeline on what? If you mean bootloader unlock read xda news
Sent from my G8142 using Tapatalk
Unjustified Dev said:
Timeline on what? If you mean bootloader unlock read xda news
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
Hello,
Timeline on any of the above except bootloader, aka TWRP, Lineage, I mean is it being worked on or what? Sorry I should have quoted the text above.
Quote:
Originally Posted by Chris axon 7
How did you do that?
I hope that it does not take long until we can all unlock the BL
and we get TWRP for axon 10
Unlock Bootloader is possible at the moment (thanks to @Unjustified Dev and if not mistaken is or will work on TWRP, but will see....
marcusah123 said:
Hello,
Timeline on any of the above except bootloader, aka TWRP, Lineage, I mean is it being worked on or what? Sorry I should have quoted the text above.
Quote:
Originally Posted by Chris axon 7
How did you do that?
I hope that it does not take long until we can all unlock the BL
and we get TWRP for axon 10
Unlock Bootloader is possible at the moment (thanks to @Unjustified Dev and if not mistaken is or will work on TWRP, but will see....
Click to expand...
Click to collapse
TWRP isn't ready due to decryption with a pin set. And lineage isn't ready either but you can install GSI. Only difference is GSI don't take full advantage of the Qualcomm enhancements like gps and ims but everything else *should* work
Sent from my G8142 using Tapatalk
DrakenFX said:
Unlock Bootloader is possible at the moment (thanks to @Unjustified Dev and if not mistaken is or will work on TWRP, but will see....:good::good:
Click to expand...
Click to collapse
marcusah123 said:
Hello,
Timeline on any of the above except bootloader, aka TWRP, Lineage, I mean is it being worked on or what? Sorry I should have quoted the text above.
Quote:
Originally Posted by Chris axon 7
How did you do that?
I hope that it does not take long until we can all unlock the BL
and we get TWRP for axon 10
Unlock Bootloader is possible at the moment (thanks to @Unjustified Dev and if not mistaken is or will work on TWRP, but will see....
Click to expand...
Click to collapse
Unjustified Dev said:
TWRP isn't ready due to decryption with a pin set. And lineage isn't ready either but you can install GSI. Only difference is GSI don't take full advantage of the Qualcomm enhancements like gps and ims but everything else *should* work
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
If I'm going to run this phone, I would love LineageOS as that's what I am on currently. Why Android has to be a pain to get everything migrated from an old phone to a new phone and hasn't been fixed is beyond frustrating too. I don't upgrade often due to the fact that phone hardware sucks or the boot-loader is encrypted. If that wasn't an issue that would be one less hassle but the fact that it's so much trouble to change from an old device to a new device while taking all your stuff with you and not losing or having stuff get missed in the transfer that's the biggest reason I keep my phones so long.
I'll need all the regular features like GPS so I can't really do without full support and I wouldn't want to run anything but LineageOS anyway because when LineageOS is ready I want to just get my stuff to it and not have to do the move of my data multiple times.
Thanks
marcusah123 said:
If I'm going to run this phone, I would love LineageOS as that's what I am on currently. Why Android has to be a pain to get everything migrated from an old phone to a new phone and hasn't been fixed is beyond frustrating too. I don't upgrade often due to the fact that phone hardware sucks or the boot-loader is encrypted. If that wasn't an issue that would be one less hassle but the fact that it's so much trouble to change from an old device to a new device while taking all your stuff with you and not losing or having stuff get missed in the transfer that's the biggest reason I keep my phones so long.
I'll need all the regular features like GPS so I can't really do without full support and I wouldn't want to run anything but LineageOS anyway because when LineageOS is ready I want to just get my stuff to it and not have to do the move of my data multiple times.
Thanks
Click to expand...
Click to collapse
The phone hasn't been out very long. It took a whole team to get most of the issues worked out the Axon 7. There's no way we could just get it working that fast. Keep in mind I don't own the device either. It's going to take time regardless due to so much changing with Android I'm behind on all the new stuff like encryption.
Sent from my G8142 using Tapatalk
marcusah123 said:
If I'm going to run this phone, I would love LineageOS as that's what I am on currently. Why Android has to be a pain to get everything migrated from an old phone to a new phone and hasn't been fixed is beyond frustrating too. I don't upgrade often due to the fact that phone hardware sucks or the boot-loader is encrypted. If that wasn't an issue that would be one less hassle but the fact that it's so much trouble to change from an old device to a new device while taking all your stuff with you and not losing or having stuff get missed in the transfer that's the biggest reason I keep my phones so long.
I'll need all the regular features like GPS so I can't really do without full support and I wouldn't want to run anything but LineageOS anyway because when LineageOS is ready I want to just get my stuff to it and not have to do the move of my data multiple times.
Thanks
Click to expand...
Click to collapse
For starters, @Unjustified Dev DOES NOT have this Device, he is doing every blind and if you want to get any custom software together, jump in and help him get the Axon 10 Pro, so he can debug and get faster fixes for this device.
Other than that You Have To Wait like everyone else
Unjustified Dev said:
The phone hasn't been out very long. It took a whole team to get most of the issues worked out the Axon 7. There's no way we could just get it working that fast. Keep in mind I don't own the device either. It's going to take time regardless due to so much changing with Android I'm behind on all the new stuff like encryption.
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
Hello,
Thanks for taking time to respond to my message. I understand what you mean about the encryption. Can I justify buying the phone at the double cost from what the Axon 7 cost? Not sure however I am highly interested in this.
Thanks
---------- Post added at 08:14 PM ---------- Previous post was at 08:09 PM ----------
DrakenFX said:
For starters, @Unjustified Dev DOES NOT have this Device, he is doing every blind and if you want to get any custom software together, jump in and help him get the Axon 10 Pro, so he can debug and get faster fixes for this device.
Other than that You Have To Wait like everyone else
Click to expand...
Click to collapse
Can we start or set something up here to donate so he can get a device?
I am not sure how that works here.
marcusah123 said:
Can we start or set something up here to donate so he can get a device?
I am not sure how that works here.
Click to expand...
Click to collapse
If you want you can start a thread using his "PayPal.me" or just donate to him here :
https://www.paypal.me/unjustifieddev
Every little thing counts and the faster he get the device the faster WE will see things moving.
thanks,but it used AXON10Pro 5G ?

Categories

Resources