Related
Hello guys
May i ask if OmniROM will ever make it to the Xperia Z2 (Sirius)?
Been missing it for ages now
Keep up the great work
mariotme said:
Hello guys
May i ask if OmniROM will ever make it to the Xperia Z2 (Sirius)?
Been missing it for ages now
Keep up the great work
Click to expand...
Click to collapse
I normally just report device requests, but since I've done a lot of the Sony bringups:
I wanted a Z2. I really, really wanted one.
However I don't buy greymarket imports, and Sony refused to sell the Z2 in North America until after the Z3 was launched. Even now, the purchasing link is nearly impossible to find (it is not listed for sale anywhere on sonymobile.com)
Z3 is a possibility if it goes on sale unlocked in North America in a timely fashion. (Which is unlikely...) Z2 is a possibility if some maintainer picks it up, of course, but considering the device's successor is out now, that's pretty unlikely.
Entropy512 said:
I normally just report device requests, but since I've done a lot of the Sony bringups:
I wanted a Z2. I really, really wanted one.
However I don't buy greymarket imports, and Sony refused to sell the Z2 in North America until after the Z3 was launched. Even now, the purchasing link is nearly impossible to find (it is not listed for sale anywhere on sonymobile.com)
Z3 is a possibility if it goes on sale unlocked in North America in a timely fashion. (Which is unlikely...) Z2 is a possibility if some maintainer picks it up, of course, but considering the device's successor is out now, that's pretty unlikely.
Click to expand...
Click to collapse
I totally understand Entropy512! Thanks for your input buddy. Appreciate all your efforts man. Keep it up :good:
Entropy512 said:
I wanted a Z2. I really, really wanted one.
Click to expand...
Click to collapse
Thanks for your answer, yes that's the best smartphone I've ever got! Why the hell do they think they don't need to sell their devices in america??
As I know you are a major developer of OmniRom, I really hope you will be able to get an Xperia Z4, and hopefully port the ROM on it..
Thanks for your work!:good:
May I Taste said:
Thanks for your answer, yes that's the best smartphone I've ever got! Why the hell do they think they don't need to sell their devices in america??
As I know you are a major developer of OmniRom, I really hope you will be able to get an Xperia Z4, and hopefully port the ROM on it..
Thanks for your work!:good:
Click to expand...
Click to collapse
I'll probably skip the Z4 thanks to Sony's crazy 6-month product cycle.
I have a Z3 but so far it's stock. This device is holding a record for the longest I've gone without root/unlocking the BL.
Sony did an awesome job with the stock firmware on the SIM-unlocked Z3.
Entropy512 said:
I'll probably skip the Z4 thanks to Sony's crazy 6-month product cycle.
I have a Z3 but so far it's stock. This device is holding a record for the longest I've gone without root/unlocking the BL.
Sony did an awesome job with the stock firmware on the SIM-unlocked Z3.
Click to expand...
Click to collapse
Thanks for your kind answer and I can understand you. It seems however that the Z4 will now last for one year as flagship. Anyway I'll make sure to stay tuned if by chance you work on OmniROM for it.
Have a wonderful year, you and your whole family!
There some unofficial builds for the Sony Sirius floating around...
http://infectedbuilds.net/downloads/sirius/omni_lp/
From my very brief play with it, there's no Cam or NFC but everything else seems pretty useable.
A number of Omni team members are working with the Sony AOSP guys. Short-term it means a lot of things are broken that aren't in CM since Sony AOSP is reworking a bunch of stuff onto a newer unified kernel that will support a large variety of devices. Long-term it'll allow us to support more Sony devices with less effort.
I think one of the guys working this has a sirius... I forget who.
I just synced all the Omnirom repos and compiled for the Z2. It works ok, just no Camera, recovery and there seems to be a bug around internal storage, as it thinks there is no space left.
I'd be interested in helping to fix these things, I'm pretty comfortable using git and gerrit and know some Java and C++ but I have no idea where to start.
Code:
adb logcat | grep camera
- waiting for device -
E/CameraService( 373): Could not load camera HAL module
W/ResourcesManager( 1057): Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
I/CameraManagerGlobal( 1057): getCameraService: Reconnecting to camera service
E/CameraService( 373): getCameraVendorTagDescriptor: camera hardware module doesn't exist
W/CameraManagerGlobal( 1057): Failed to set up vendor tags: The camera device is removable and has been disconnected from the Android device, or the camera service has shut down the connection due to a higher-priority access request for the camera device.
So I'd guess I'd have to find out why the camera HAL module can't be loaded?
mikeysteele said:
I just synced all the Omnirom repos and compiled for the Z2. It works ok, just no Camera, recovery and there seems to be a bug around internal storage, as it thinks there is no space left.
I'd be interested in helping to fix these things, I'm pretty comfortable using git and gerrit and know some Java and C++ but I have no idea where to start.
Code:
adb logcat | grep camera
- waiting for device -
E/CameraService( 373): Could not load camera HAL module
W/ResourcesManager( 1057): Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
I/CameraManagerGlobal( 1057): getCameraService: Reconnecting to camera service
E/CameraService( 373): getCameraVendorTagDescriptor: camera hardware module doesn't exist
W/CameraManagerGlobal( 1057): Failed to set up vendor tags: The camera device is removable and has been disconnected from the Android device, or the camera service has shut down the connection due to a higher-priority access request for the camera device.
So I'd guess I'd have to find out why the camera HAL module can't be loaded?
Click to expand...
Click to collapse
Camera is far away from being supported. The blobs are completely missing, because they simply won't work with our kernel.
There's work being done, however a lot of it has to be done by someone within Sony and that results in stuff having to go through a legal approval process.
In theory it might be possible with some work to get 5.0 camera blobs working with a lot of kernel hacking, but most people are focusing on a cleaner approach that will take longer and unfortunately has dependencies on Sony's lawyers.
Entropy512 said:
Camera is far away from being supported. The blobs are completely missing, because they simply won't work with our kernel.
There's work being done, however a lot of it has to be done by someone within Sony and that results in stuff having to go through a legal approval process.
In theory it might be possible with some work to get 5.0 camera blobs working with a lot of kernel hacking, but most people are focusing on a cleaner approach that will take longer and unfortunately has dependencies on Sony's lawyers.
Click to expand...
Click to collapse
Thanks for the update. I noticed there weren't any camera blobs in the source, so I assumed it wasn't as simple as just adding them in. I see on github the CM guys hacked their kernel to be able to use the old Jellybean camera blobs which looks painful. Hopefully Sony's lawyers aren't too obstructionist. Although to their credit the Sony stock rom isn't actually too bad. Nothing compared to Omni Rom though.
mikeysteele said:
Thanks for the update. I noticed there weren't any camera blobs in the source, so I assumed it wasn't as simple as just adding them in. I see on github the CM guys hacked their kernel to be able to use the old Jellybean camera blobs which looks painful. Hopefully Sony's lawyers aren't too obstructionist. Although to their credit the Sony stock rom isn't actually too bad. Nothing compared to Omni Rom though.
Click to expand...
Click to collapse
Yeah. They used a kernel backcompat hack, and are using old 4.3 rhine blobs because those are the last ones that were completely 100% DRM-free.
DRM issues have caused all sorts of problems with rhine/shinano cameras ever since 4.4 - Workarounds for many of these have been found, but not all. But the kernel backcompat hacks would still be needed (potentially multiple hacks for each device supported by the Sony AOSP kernel) and that gets nasty.
So the current plan is to have a unified set of sensor drivers in the kernel, with blobs provided as part of the Sony AOSP project. However I think this is going to be easier said than done - it's not just Sony lawyers, but Qualcomm lawyers. It really sucks that the entirety of Qualcomm's mm-camera subsystem is proprietary and there's no way for an opensource developer to write modules for it, which prevents any of the community side of the Sony AOSP project from working on some things. Otherwise it would probably be not too difficult to replace Sony's noise reduction algorithm (likely with a better one... Sony's NR algorithm got slammed for being too aggressive and killing sharpness over in a dpreview review... All that DRM protection for something some people actually prefer to have gone.)
Edit: And yes, Sony's stock firmwares are amazing. My Z3 holds the record for longest I've ever owned a device without even bothering to root it.
Another thing, my phone is the China Mobile version (L50t) and OmniRom runs perfectly on it, I just have to change the radio and wlan firmware. I can supply the required files and be a tester if you wanted to add official support for this varient.
Google has made it mandatory for devices launched with Android Oreo to have Linux Kernel 4.4 and Project Treble but
Older Android devices released prior to Android O but that will be upgraded to Android O can continue to use their original base kernel version if desired.
Click to expand...
Click to collapse
From AOSP/Google (I can't yet put links to source as I don't have 10 posts yet)
Which includes our OnePlus 3T. As OnePlus has already said Android Oreo will be the last major update for our device (officially) we might not get Project Treble (like Nexus 5X and 6P) and Linux kernel 4.4 (a major update from our current 3.18) making it very difficult for the developer community to port future updates as Android P and above might only have Treble base unlike Android Oreo.:crying:
That would be a another bummer after there limited support announcement for 3t. For know I keep my fingers crossed for a better message on this front.
Still if images are released for AOSP you still will get development for our phone though. ?
Goku80 said:
Still if images are released for AOSP you still will get development for our phone though. ?
Click to expand...
Click to collapse
Exactly. Honestly I don't see why Project Treble matters to the average ROM user. I just want my phone to work and perform well and have a decent battery life. Besides that I don't really care. Currently I have a Nexus 6 and just replaced the battery in it but I'm perusing the forums for various devices (this was one of them) that I may be interested in. I want to see how the development community is for each one before I decide. Reason I may be considering this over the OP5 is I have heard bad things about the screen and jelly scrolling.
rjmxtech said:
Honestly I don't see why Project Treble matters to the average ROM user.
Click to expand...
Click to collapse
You don't see why?
Let me help you out:
Ars Technica said:
Custom ROMs shouldn't need to be painstakingly hand-crafted for individual devices anymore—a single build should cover multiple Treble devices from multiple manufacturers. Imagine the next time a major new version of Android is released. On Day One of the AOSP code drop, a single build (or a small handful of builds) could cover every Treble device with an unlocked bootloader, with a "download Android 9.0 here" link on XDA or some other technical website.
Click to expand...
Click to collapse
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
I totally agree this !
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
Exactly! Development and porting of Custom ROMs will become easier than ever before and porting of future versions of Android will also become way lot easier (if possible at all as future versions of Android might become completely dependent on Project Treble unlike Android Oreo which is compatible with both)! And porting Project Treble is very very difficult if not impossible (unless you are the Silicon Manufacturer) !
So lets together spread the information about the importance of Project Treble and pressure OnePlus to provide Project Treble with #WeWantTreble
We shall Never Settle!
#WeWantTreble
Sent from my ONEPLUS A3003 using XDA Labs
Lets spam Carl Pei twitter with questions regarding this..
(Well not really spam, that would be rude, more like a lot of people asking him same question in shorts period of time)
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Lyokacanthrope said:
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Click to expand...
Click to collapse
i have red somewhere that pixel devices support treble. Same Soc, should have supported. idk.
From my experience as a Junior Android developer and reading the papers about the project treble, i could say that if there is a little group op3t developers who want this, this can be possible.
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
Interesting. But I assume there would still be issues even if they tried to make a universal solution.
Lyokacanthrope said:
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Click to expand...
Click to collapse
Treble is mostly dependent on the SoC vendor as Project Treble is all about a vendor implementation with a vendor interface layer connecting it to the Android OS Framework unlike before when (parts of) Android OS Framework had to be compiled along with the vendor implementation as there was no interface layer in between them.
But Google Pixel which is also on the Qualcomm Snapdragon 821 as the OnePlus 3T has Project Treble but I also doubt how did they manage to get the silicon specific code required for implementing Project Treble during Developer Previews as generally the source code of Developers Previews is available only to Google and Qualcomm generally doesn't share the uncompiled silicon specific code even with OEMs (I might be wrong and Qualcomm and Google might be having partnership).
As there is already Project Treble for Qualcomm Snapdragon 821 (Google Pixel) I think it might be upto OnePlus to choose if it wants to implement it.:fingers-crossed:
DelicatePanda said:
Treble is mostly dependent on the SoC vendor as Project Treble is all about a vendor implementation with a vendor interface layer connecting it to the Android OS Framework unlike before when (parts of) Android OS Framework had to be compiled along with the vendor implementation as there was no interface layer in between them.
But Google Pixel which is also on the Qualcomm Snapdragon 821 as the OnePlus 3T has Project Treble but I also doubt how did they manage to get the silicon specific code required for implementing Project Treble during Developer Previews as generally the source code of Developers Previews is available only to Google and Qualcomm generally doesn't share the uncompiled silicon specific code even with OEMs (I might be wrong and Qualcomm and Google might be having partnership).
As there is already Project Treble for Qualcomm Snapdragon 821 (Google Pixel) I think it might be upto OnePlus to choose if it wants to implement it.:fingers-crossed:
Click to expand...
Click to collapse
Friggin' derp. How did I forget about the Pixel?
That being said, we'd still need to see how its implemented on the Pixel...As far as I know Treble also relies in a specific type of device partitioning which may be problematic for existing device adaptations. The Pixel phones already used the /vendor partition how it's supposed to be used so adapting Treble is almost a non-issue. I don't think our phone uses the same partition layout.
As of open beta 16 Oxygen OS we didn't get the new v4.4 kernel and also project Treble:crying:
DelicatePanda said:
As of open beta 16 Oxygen OS we didn't get the new v4.4 kernel and also project Treble:crying:
Click to expand...
Click to collapse
That sucks .. even for OnePlus 5?
why the heck Carl is not replying officially on it, anywhere???
As seen here
https://www.reddit.com/r/LineageOS/...ect_trebel_devices/?utm_source=reddit-android
LineageOS team state that project treble is in its baby shoes and completely dependant on google to optimize it even more since as of now gsi rom requires certain adjustments for each device, so will project treble successed?
any1 has an insight please share.
I think it needs more adjustment. The kernel should be universal and updateable along with the OS, it's pretty universal as it is at the moment. Drivers should also be standard and updateable, at least for standard items. There should be a driver model where possible to support other devices, and any phone specific changes could be done through manufacturer supplied drivers. There's really no reason why it can't be done, it would be along the lines of how Windows works. Of course, it can be tailored to suit phones.
System updates should realistically come from Google, it would mean all phones and devices would be up to date with the latest security updates. The phone can also check with the manufacturer for specific updates. If Google keeps them apprised of any changes they can update their specific updates in time. This model would mean individual service testing for a new OS update etc wouldn't be a problem since it should at least be compliant with the base model.
Don't forget Google tracks down security leaks in other OS like Windows, which isn't even a direct competitor, and releases the security leak information if it isn't patched within 30? days. How many Android devices are updated with security patches within 30 days by the manufacturer? It's very much a double standard. Google really needs to think of an even more universal model like I just depicted for Android 10 Quinoa Slice (or whatever they call it).
Will Treble succeed? It's a step in the right direction, but needs more work. Not only should something like I just described be done, it should be made mandatory for all new devices. It doesn't mean custom versions are out, but custom versions would have to have OTA updates and be updated quickly along with the standard OS.
To say whether it succeeded or not, I think you'd first need to define what's its goal.
I still don't even know the answer as of today.
Some people say that the goal is to have a system image controlled and updated by Google.
But I don't see this happening any time soon. Google would need to test their GSIs on many devices, and they didn't even test P GSI over O-MR1 Pixels!
It seems to me that their goal was simply to make updates easier to OEMs. Considering Essential PH-1 getting Pie day-one, this might seem a success.
But we'll need to compare Oreo adoption rate to Pie's to confirm.
Oooh someone made a thread so i can moan cheers
The main problem with treble for me is that it's splintered between a plethora of devices, so one dev will release a treble rom and a multitude of device owners will flash it, each with their own subjective problems and issues, requests and wants.
And there lies the problem, it's difficult even when it's a dedicated rom thread for a particular device to get help at times.
So when you have a bunch of users talking about completely different devices you haven't got a hope in hell.
I think there should be branches to each thread for each specific device, that way help threads can be more linear rather than the chaos that it is at the moment.
Least that's my thoughts
My only rom i've flashed is RR and besides a few missing features, Fingerprint, Stereo and NFC i think it's brilliant.
Hello developers of XDA!
I'm Rox, a Razer Vanguard and i'm here to let you know that the Audio Source is now available for the Razer Phone 2! You can now find the complete source code on the Razer Developers website here
I'm glad you all now have access to the full open source material and we can finally see some movement on the custom development we all know from Android
I would also like to take this opportunity to ask the developers of XDA for some feedback. Is there anything stopping people in particular supporting the device in the community with custom ROM's and Kernels? And is there anything that Razer could do to help?
This is by no means any assurance but I will gather all your feedback and pass it on.
The community is the most important thing to a product and I will continue to raise the communities voice as much as possible.
Thank you so much for the time!
Rox - Razer Vanguard.
Roxas598 said:
Hello developers of XDA!
I'm Rox, a Razer Vanguard and i'm here to let you know that the Audio Source is now available for the Razer Phone 2! You can now find the complete source code on the Razer Developers website here
I'm glad you all now have access to the full open source material and we can finally see some movement on the custom development we all know from Android
I would also like to take this opportunity to ask the developers of XDA for some feedback. Is there anything stopping people in particular supporting the device in the community with custom ROM's and Kernels? And is there anything that Razer could do to help?
This is by no means any assurance but I will gather all your feedback and pass it on.
The community is the most important thing to a product and I will continue to raise the communities voice as much as possible.
Thank you so much for the time!
Rox - Razer Vanguard.
Click to expand...
Click to collapse
Thanks for the info, I'm waiting for my phone to arrive. I hope to start playing with the ROM very soon.
What's a Razer Vanguard?
It's like their tech support reps, except they're a little more involved. Already dealt with one on their site, and he was very helpful and responsive. Most replies were within just a couple hours. Seems like these guys actually use the hardware they support, and don't treat the users like idiots. Nice to see this, especially since they just laid off most of their phone division. Hopefully this is a sign of better things to come. This phone is a beast.
jonchance_84 said:
It's like their tech support reps, except they're a little more involved. Already dealt with one on their site, and he was very helpful and responsive. Most replies were within just a couple hours. Seems like these guys actually use the hardware they support, and don't treat the users like idiots. Nice to see this, especially since they just laid off most of their phone division. Hopefully this is a sign of better things to come. This phone is a beast.
Click to expand...
Click to collapse
That is essentially it! Thank you for the kind words, I'll be sure to pass it on to the team. We definitely do use the hardware we help with and for me personally the Razer Phone is my specialty but we all have experience with most Razer products.
I think there are two main things I would like to see:
1. Earlier factory images and the release of ota updates. It would be nice for those who have yet to get pie, for example.
2. Though I realize it's unlikely, the release of the device tree would really be a big boost to rom and kennel development
I second earlier factory image and source releases.
On another note. The sources we have currently had a lot of header/build issues. As other Devs have pointed out(elsewhere) this was probably due to the sources being built out of the device tree but they still seemed weird as I've never seen that before and can't make out how a device tree would have changed that. Would it be too much to ask that some time be taken to scrub the sources better and maybe even have some basic build scripts or instructions? I realize this is contrary to my first point but it's the next best thing to a device tree.
It would be nice to get full android 9 images the same as android 8.1
I still do not understand - why there is no support for aptx, aptx hd, ldac?!!!
And you can't even install it like on most other phones, maby razer developers know how fix it?
Also, due to a strange signature system, most gsi roms do not work.
How about Razer Phone 1?
Now I'm not a gamer, just got a used RP1 from a moderator on the Swedroid forum quite by accident, as it were.
I really quite like it, the Sharp IGZO screen especially, same as on my Xiaomi Mi Mix1, which was the main reason I got it.
I have had zero problems with it so far.
ROM for Andorid 9
GoomerHD said:
It would be nice to get full android 9 images the same as android 8.1
I still do not understand - why there is no support for aptx, aptx hd, ldac?!!!
And you can't even install it like on most other phones, maby razer developers know how fix it?
Also, due to a strange signature system, most gsi roms do not work.
Click to expand...
Click to collapse
+1 having the full image will save us a lot of time and will expedite the creation of mod ROM.
CurtisMJ said:
I second earlier factory image and source releases.
On another note. The sources we have currently had a lot of header/build issues. As other Devs have pointed out(elsewhere) this was probably due to the sources being built out of the device tree but they still seemed weird as I've never seen that before and can't make out how a device tree would have changed that. Would it be too much to ask that some time be taken to scrub the sources better and maybe even have some basic build scripts or instructions? I realize this is contrary to my first point but it's the next best thing to a device tree.
Click to expand...
Click to collapse
I was informed this is how all new MSM kernels are - they don't build properly out of the AOSP tree (it looks like Android's build system supplies some additional flags to the kernel make system to make it use some prebuilts and AOSP headers over the kernel-provided ones). I don't think this is unique to Razer, since it's a Qualcomm thing.
I've got build instructions for the kernel in my thread too if you need them.
Of course, I could be relaying incorrect information but this does seem like it's typical of Google/Qualcomm to be changing Open Source projects to fit their internal needs...
Rox598 said:
Rox - Razer Vanguard.
Click to expand...
Click to collapse
Can you guys get in contact with CurtisMJ on this forum and see about implementing his amazing Chroma logo alternative app, integrating features of it with the current Chroma logo app, or otherwise allowing us non-root users to systemize it?
https://forum.xda-developers.com/razer-phone-2/themes/beta-logo-oss-implementation-lighting-t3893981
It has a lot of features I want from the Chroma app, but I'm weary of rooting, especially now that Android 9 Pie has come out and no factory images for 9 Pie are on the Razer dev site. If you even wanted to put it in the next update and give users the option of which Chroma app they wanted to use, I'm sure CurtisMJ would think that was pretty neat, though you'd have to ask him. I mean, I'd personally pay to use it if it meant I didn't have to root. Maybe integrate it with the stock Chroma app, and charge $5 to upgrade to CurtisMJ's features, and then split the cash with him. Idk.
AbsoluteContingency said:
Maybe integrate it with the stock Chroma app,.
Click to expand...
Click to collapse
I wonder lol.
Interestingly I did see some code in the Chroma app which can grant use of the service to unprivileged apps. I think it was used to whitelist some other Razer component. Just opening up that functionality to users so they can "grant" Chroma access to apps of their choosing might be enough. Otherwise, if I could get a signed stub in the next OTA that'd be cool (and ridiculously unlikely, just to be clear)
Great comments everyone keep them coming!
GoomerHD said:
It would be nice to get full android 9 images the same as android 8.1
I still do not understand - why there is no support for aptx, aptx hd, ldac?!!!
And you can't even install it like on most other phones, maby razer developers know how fix it?
Also, due to a strange signature system, most gsi roms do not work.
Click to expand...
Click to collapse
Yeah, coming from my Samsung S8+, LDAC is the thing I'm missing the most.
I would just like to say thanks to Razer for listening to their customers and trying to be helpful, so: Thank you! :good: :victory:
I'm not a developer, but whatever these other guys need to get TWRP working, I'm all for
Pete450 said:
I would just like to say thanks to Razer for listening to their customers and trying to be helpful, so: Thank you! :good: :victory:
I'm not a developer, but whatever these other guys need to get TWRP working, I'm all for
Click to expand...
Click to collapse
That's my goal atm to get the developers points of view and requests I'm proud of the community helping each other out so this is my next focus.
So far my feedback list has faster Factory images, and source code, device tree, more Audio Codec (APT-X AND LDAC) and a couple of other things I can't get into.
If anyone else thinks of anything lmk and I'll add it to my list to send on. I hope the right person sees it but again there is zero assurances that any of it will happen but this is where the voices matter.
Thanks again everyone!
Might be a little off topic, but since this is a gaming phone, why can't I pair my old ps3 controller? I even tried an old usb Xbox 360 controller, which a usb host test app successfully found the device. I would have hoped this would have been built in, being a gaming phone and all. I'm on pie and rooted, even when trying multiple previous methods of trying to get something the work, all the phone wants to do is charge the connected device.
jonchance_84 said:
Might be a little off topic, but since this is a gaming phone, why can't I pair my old ps3 controller? I even tried an old usb Xbox 360 controller, which a usb host test app successfully found the device. I would have hoped this would have been built in, being a gaming phone and all. I'm on pie and rooted, even when trying multiple previous methods of trying to get something the work, all the phone wants to do is charge the connected device.
Click to expand...
Click to collapse
Unfortunately the PS3 controller doesn't connect and act like a good Bluetooth or USB device. There is an app called sixaxis controller on the play store that allows you to connect a PS3 controller via Bluetooth, but it needs root and I don't believe it works anymore. There's also an app for wired PS3. It's not a Razer issue, it's a controller issue.
CalebQ42 said:
Unfortunately the PS3 controller doesn't connect and act like a good Bluetooth or USB device. There is an app called sixaxis controller on the play store that allows you to connect a PS3 controller via Bluetooth, but it needs root and I don't believe it works anymore. There's also an app for wired PS3. It's not a Razer issue, it's a controller issue.
Click to expand...
Click to collapse
Right, I tested it all. That app gets to the part where it tries to pull the Mac of the phone's Bluetooth adapter and simply can't. I'm leaning more towards the an Oreo/Pie issue. Seems to be driver related.
GrapheneOS has this nice new feature called Sandboxed Play services which basically allows to run google play services as unprivileged apps. To make this possible, they built a compatibility layer.
For testing purposes I already merged necessary commits and created patches for LOS. As I'm not going to publicly release any builds, I've already posted a guide so that any rom builder can easily integrate the gms compatibility layer in their rom (not necessarily lineageos).
But, I'd love to see this in LineageOS officially. In a comment on reddit it sounds like the main problem is that the feature violates the Android Compatible Device Document. However, after looking at the source code of the compatibility layer, it seems like the layer could easily be implemented without violating anything. In fact, the gmscompat layer was implemented as a compatibility change to reuse the existing compatibility change infrastructure. It is a special implementation though, and automatically get's activated for GMS apps only (see these two patches).
My thinking is, if the compat change isn't activated on its own for GMS apps, but additionally relies on a checkbox (disabled by default) in the system menu, that wouldn't violate anything, because the default behaviour isn't tampered with at all. And as soon as the user enables the compatibility layer with the help of the aforementioned system menu setting, Google play services can be run in a sandbox.
What do you think?
I had inquired with the graphene devs about 2 or 3 weeks ago and they couldn't even tell me all of the repos I had to cherry pick the 100+ commits from....thanks for this. I've been putting off integrating this into my LOS ROM since I started developing it almost a month ago
> I had a with the graphene devs about 2 or 3 weeks ago and they couldn't even tell me all of the repos I had to cherry pick the 100+ commits from....thanks for this. I've been putting off integrating this into my LOS ROM since I started developing it almost a month ago
You can check the commits here: https://gist.github.com/thestinger/ee536cbd1ca674b94dde05831192c348#comments
Wait, that's all the commits needed?
PiXinCreate said:
> I had inquired with the graphene devs about 2 or 3 weeks ago and they couldn't even tell me all of the repos I had to cherry pick the 100+ commits from....thanks for this. I've been putting off integrating this into my LOS ROM since I started developing it almost a month ago
You can check the commits here: https://gist.github.com/thestinger/ee536cbd1ca674b94dde05831192c348#comments
Click to expand...
Click to collapse
Thanks so much for that. Seriously. I FINALLY have Sandboxed Play Services working.
It's a Lineage 19.1 rom
Glad to know about that!
I'm new to all these ROM development stuffs. I'd be helpful if you publish your work on GitHub with a build documentation.. (optional, you can decline my request).
As the dev already has confirmed that former (GMS_Sandbox) is ROM independent, I personally feel like making a Magisk Module for that, which will be systemless and optimal.
Yeah, I surely will upload my sources. It's just so monotonous creating each repo one by one and adding remotes lol I've been putting it off.
Getting it working with that gist was very easy though, most every commit auto-merged.
But yeah, I'll upload those sources and post back here when they are up.
( I am new as well btw, I just got started about a month ago)
EDIT: SOURCES
From what I read the Lineage OS developers don't seem very cooperative, at least on this front (see LineageOS for microG).
A Magisk module would be amazing. It would also make the work I just did to compile Lineage obsolete
Do you already have a technical approach for such a module? Would you just replace the files that have been changed? How concrete are your plans to make it?
Sewdohe said:
Thanks so much for that. Seriously. I FINALLY have Sandboxed Play Services working.
It's a Lineage 19.1 rom
Click to expand...
Click to collapse
u have sandboxed Google's for lineageos 19.1?
can u explain how u got it done?
Thanks