Related
Woke up this morning to my Galaxy Camera 2 claiming it was downloading a new software update (~130mb). Of course, there's no mention anywhere in the update process for what is included in this update, but I can definitely tell you that it's not Kitkat (sadly). Unfortunately, I didn't check version numbers prior to accepting the update (sorry), but here's the version numbers after the update:
Build Number:
JSS15J.GC200XXUCNK4
Kernel version:
3.0.31-2807772
[email protected] #1
Sat Nov 29 15:55:43 KST 2014
That's the same Build Number we've had since like April 2014, but the kernel definitely seems to have been updated. Maybe they finally fixed the loss of Google account settings issue??? I appreciate updates, but I really wish they would inform the customer better on what these updates fixed.
Ironically, for the first time in a long time, my Camera 2 had lost its Google Account settings when I turned it on this morning....haha.
Oh, I reside in Florida, USA. Not sure who else in the world is receiving the update, but according to SamMobile.com the Camera 2 update was hitting other locations around the globe starting 12/18/2014, but there's no mention of it hitting the USA at all.
Need to know if it's root able.
cantenna said:
Need to know if it's root able.
Click to expand...
Click to collapse
As long as this fixes the problem of losing the Google account, I have no reason to root the camera. Plus, I still have this weird hope that Samsung will actually release a Kitkat update for it (haha), and with there basically being ZERO development for this device on XDA, I don't want to be stuck not able to update.
Well, it's been almost a week since this update and it's also been a week of heavy Camera 2 use with the holidays. I haven't lost Google settings even once.
Thus far my camera hasn't lost my Google accounts, and by now it surely would have happened
Sent from my Nexus 9 using Tapatalk
internetpilot said:
As long as this fixes the problem of losing the Google account, I have no reason to root the camera. Plus, I still have this weird hope that Samsung will actually release a Kitkat update for it (haha), and with there basically being ZERO development for this device on XDA, I don't want to be stuck not able to update.
Click to expand...
Click to collapse
Eh...
I didn't waste my time getting the Galaxy Camera 2, just got the One.
I understand your stress though.
Someone needs a swift kick in the butt so we can get development going for both devices.
Sent from my LG-P920 using XDA Free mobile app
hmm am glad to see an uphdate still, though im really really hoping for lollipop which should allow RAW access for the camera.
mark2410 said:
hmm am glad to see an uphdate still, though im really really hoping for lollipop which should allow RAW access for the camera.
Click to expand...
Click to collapse
Assuming you do get it, could we transfer it over to the Galaxy Camera One, Wi-Fi Edition?
I don't like to be the rude one. But at this point, someone has to help root the Wi-Fi Only version, and come up with a Custom Recovery.
Not only this, but we need to see Devs, but we've got people sitting and pointing fingers instead.
I wanna see a ROM putting us all on a better version, or something more come to all the cameras.
Sent from my LG-P920 using XDA Free mobile app
hmm, really wouldnt have thought so, its probably possible given the hardware similarities but i think that given the camera 1 and 2 have been such unpopular devices they havent warranted their own listings here i wouldnt hold me breath. the key to getting a ROM for a device is someone who is techy enough to do wanting to use one. i for one might like the camera but i would have absolutely no clue how to make a rom for it.
hmm surely there must be a dev out there who likes photos.
mark2410 said:
hmm, really wouldnt have thought so, its probably possible given the hardware similarities but i think that given the camera 1 and 2 have been such unpopular devices they havent warranted their own listings here i wouldnt hold me breath. the key to getting a ROM for a device is someone who is techy enough to do wanting to use one. i for one might like the camera but i would have absolutely no clue how to make a rom for it.
hmm surely there must be a dev out there who likes photos.
Click to expand...
Click to collapse
The Camera 2 has gotten support, but not what it needs.
And honestly, Developing ROMs isn't too difficult, I just don't have the time for it.
Sent from my EK-GC110 using XDA Free mobile app
The reason why you would want to root the camera is because you can instal Link2sd and Foldermount, with these two apps you can install theoretically 128G of apps
cantenna said:
The reason why you would want to root the camera is because you can instal Link2sd and Foldermount, with these two apps you can install theoretically 128G of apps
Click to expand...
Click to collapse
Why would anyone want to put 128GB of apps on a camera? I mean, a tablet or phone, okay...but a camera? I just don't really see the practical purpose for that. The biggest storage hog on my tablet/phone is music and movies, and neither of those require the device to be rooted to store them on the external SD card.
Again, with the way Samsung is really clamping down on not allowing OTA's to be delivered to even just rooted devices, and with the basically non-existent development support for this device, I won't be rooting it until I'm 100% certain that there's no OTA update coming for it, and even then I would only root it if someone put out a reliable custom Kitkat or Lollipop ROM for it. Honestly, if Samsung won't update it, then I'm really not holding my breath that some 3rd-party dev ever will.
Ouya-XD said:
The Camera 2 has gotten support, but not what it needs.
And honestly, Developing ROMs isn't too difficult, I just don't have the time for it.
Click to expand...
Click to collapse
It would be a heckuva lot easier to port a Camera 2 ROM over to the Camera 1 (rather than develop a ROM from scratch for either camera model), but even that hasn't been done. I don't think there's ever going to be any original development on these devices (like a CM11 or CM12). Developing ROMs isn't terribly difficult, but it's not easy either, especially not on a device that is so driver dependent like these cameras are. Just about every Android device I've owned (phone or tablet) has problems with the camera not working in some way (if not completely) on any original development project. What good is a camera with the latest Android OS if it causes the camera function not to work or even not work reliably?
I think we need to face it, folks -- these cameras are pretty much as-is. At best we're highly dependent on whatever Samsung gives us.
Nope, I disagree. Rooting this camera is a damn good idea for so many reasons. Most tablet or phone dont have a miro HDMI, My camera, I can install apps without deleting and its not just a camera, its an android device by Samsung that comes with a micro hdmi and with a Bluetooth mouse and keyboard, well if you have ever thought about buying an android TV box, this is a better replacement, it performs much better than majority on the market.
And yes I agree that stock ROMs with stock drivers perform better but asop base ROM do perform much better in terms of speed in gaming and applications. What about a multi ROM solution to allow you multi-boot i.e. boot stock from internal nand and asop lollipop from from external SD, now that would be a sweet setup!
hmmm i get your point but for me, the camera is a camera. ive got a tablet for tablety things, a phone for phoney things so what i want is camera focused and to have dropbox autoupload everything nicely.
thats the anly reasen im so fussed that i want it to get lollipop as it should then get RAW capabilities. while i realise it may not happen i will vote with my wallet. this is my first real samsung device (galaxy nexus doesnt count) and while i love oled screens and removable batteries if samsung abandon the camera, well i will abandon them. its really that simple, if they wont support devices going forward then i wont buy any other android devices from them.
if only google put out a Nexus Camera.
NK4 and rooting
I just finished the upgrade to NK4. I was trying to keep root through survival mode in Superuser Pro, but I ended up having to reroot. The upgrade via kies took about a hour. I attempted to re-establish root via Superuser but was unable to do so. I ODIN'ed the CF-autoroot onto the camera and reinstalled Superuser. I now have a NK4 rooted camera.
Since the discussion seems to have shifted to the rational for rooting, here's my take. First, it should be noted that root <> custom recovery. We do not have custom recovery for the GalCam2, so installing alternative ROM's, if available is not an option. So, why root? For me, it's Xposed modules; specifically pie controls(mmmm, pie). I've had several digital cameras over the years. In fact, when I bought this camera, I had a year old samsung camera. Why this camera? It's android, so I can to many things that would be not be possible on other cameras in this price range, like say using different camera apps.
So, if you're rooted on NC2, fear not. The water's OK over here on NK4.
cantenna said:
Nope, I disagree. Rooting this camera is a damn good idea for so many reasons. Most tablet or phone dont have a miro HDMI, My camera, I can install apps without deleting and its not just a camera, its an android device by Samsung that comes with a micro hdmi and with a Bluetooth mouse and keyboard, well if you have ever thought about buying an android TV box, this is a better replacement, it performs much better than majority on the market.
Click to expand...
Click to collapse
Well, of course you can disagree, but I still think you're stretching your camera well beyond practical purpose. Cameras are quirky enough on their own (especially ones with Android OS) -- it's probably not a good idea to use it so much for non-photography purposes because when you wear it out from overuse with all these extraneous functions you're not just going to be out an Android TV device -- you're going to be out a $400 camera. Android TV boxes can be had for as cheap as US$25 and are practically disposable at that price.
Incidentally, I have a HDMI dongle (that uses a standard, readily available fullsize HDMI plug/cable) that I use on my Galaxy Note 2 phone and/or my Galaxy Note 10.1 2014 tablet all the time (typically when on vacation watching movies on the hotel TV). Not to mention $30 Chromecast can be used wirelessly. All of this without overusing my $400 camera, so that the next time I want to use my camera it won't have a low battery, scratched up screen, or otherwise screwed up or acting quirky from rooting it.
cantenna said:
And yes I agree that stock ROMs with stock drivers perform better but asop base ROM do perform much better in terms of speed in gaming and applications. What about a multi ROM solution to allow you multi-boot i.e. boot stock from internal nand and asop lollipop from from external SD, now that would be a sweet setup!
Click to expand...
Click to collapse
Again, it's all about what's your priority purpose for this device. I bought this device to use as a internet connected camera -- I didn't buy it for playing games or running non-photography related apps. I don't want to have choose which OS I'm booting to....I just want to turn the camera on, take some pics, and be able to immediately upload them somewhere. As long as that's working, then in my world there's really no need to actively look for alternative solutions that are just going to potentially mess that simple process up.
Again, there's a reason why I'm here on XDA -- I've rooted (and usually ROMed) every other Android device I've owned. I'm even currently running CM11 on my Galaxy Note 2 at the expense of losing some of the S-pen features because it runs so much faster that it's like I got a completely new phone. But I just don't see any reason for rooting (or especially ROMing) the Camera 2.
10amla said:
Since the discussion seems to have shifted to the rational for rooting, here's my take. First, it should be noted that root <> custom recovery. We do not have custom recovery for the GalCam2, so installing alternative ROM's, if available is not an option. So, why root? For me, it's Xposed modules; specifically pie controls(mmmm, pie). I've had several digital cameras over the years. In fact, when I bought this camera, I had a year old samsung camera. Why this camera? It's android, so I can to many things that would be not be possible on other cameras in this price range, like say using different camera apps.
Click to expand...
Click to collapse
That's actually very good to know for future reference that NK4 is rootable. That's likely the last update we'll see for this camera knowing Samsung.
I actually don't always use a custom recovery on my Samsung devices. Since most root methods, ROMs, and even the recoveries themselves are flashed via Odin, there's really not a pressing need for a custom recovery. I've even encountered a lot of quirkiness with most custom recoveries (Philz, CWM, TWRP) when it comes to Nandroid backups (especially reliable restores), so I never rely on them and instead just reflash the ROM, allow Google to restore system data, and then restore personal apps/data with TitaniumBackup. Plus, even if you're rooted, as long as you have the stock recovery you can USUALLY take any OTA updates. I emphasize USUALLY because my Note 10.1 2014 Ed tablet is rooted but running stock recovery and the latest bug-fix update will not flash because they claim my tablet has been modified.
I guess I've never felt the need for pie controls because I haven't used the stock launcher on any Android device I've ever owned. The Camera 2 camera app interface is already pretty sweet with the on-screen dial menus. Like I said above, I'm not just globally adverse to rooting (far from it), but I just have yet to find any reason to root this camera, especially now that the latest update seems to have corrected the stupid vanishing Google Account settings issue.
Now, if someone ever comes up with a fully functioning Lollipop ROM for this camera, you'll quickly see me singing a different tune, but until then....
internetpilot said:
Well, of course you can disagree, but I still think you're stretching your camera well beyond practical purpose. Cameras are quirky enough on their own (especially ones with Android OS) -- it's probably not a good idea to use it so much for non-photography purposes because when you wear it out from overuse with all these extraneous functions you're not just going to be out an Android TV device -- you're going to be out a $400 camera. Android TV boxes can be had for as cheap as US$25 and are practically disposable at that price.
Incidentally, I have a HDMI dongle (that uses a standard, readily available fullsize HDMI plug/cable) that I use on my Galaxy Note 2 phone and/or my Galaxy Note 10.1 2014 tablet all the time (typically when on vacation watching movies on the hotel TV). Not to mention $30 Chromecast can be used wirelessly. All of this without overusing my $400 camera, so that the next time I want to use my camera it won't have a low battery, scratched up screen, or otherwise screwed up or acting quirky from rooting it.
Again, it's all about what's your priority purpose for this device. I bought this device to use as a internet connected camera -- I didn't buy it for playing games or running non-photography related apps. I don't want to have choose which OS I'm booting to....I just want to turn the camera on, take some pics, and be able to immediately upload them somewhere. As long as that's working, then in my world there's really no need to actively look for alternative solutions that are just going to potentially mess that simple process up.
Again, there's a reason why I'm here on XDA -- I've rooted (and usually ROMed) every other Android device I've owned. I'm even currently running CM11 on my Galaxy Note 2 at the expense of losing some of the S-pen features because it runs so much faster that it's like I got a completely new phone. But I just don't see any reason for rooting (or especially ROMing) the Camera 2.
That's actually very good to know for future reference that NK4 is rootable. That's likely the last update we'll see for this camera knowing Samsung.
I actually don't always use a custom recovery on my Samsung devices. Since most root methods, ROMs, and even the recoveries themselves are flashed via Odin, there's really not a pressing need for a custom recovery. I've even encountered a lot of quirkiness with most custom recoveries (Philz, CWM, TWRP) when it comes to Nandroid backups (especially reliable restores), so I never rely on them and instead just reflash the ROM, allow Google to restore system data, and then restore personal apps/data with TitaniumBackup. Plus, even if you're rooted, as long as you have the stock recovery you can USUALLY take any OTA updates. I emphasize USUALLY because my Note 10.1 2014 Ed tablet is rooted but running stock recovery and the latest bug-fix update will not flash because they claim my tablet has been modified.
I guess I've never felt the need for pie controls because I haven't used the stock launcher on any Android device I've ever owned. The Camera 2 camera app interface is already pretty sweet with the on-screen dial menus. Like I said above, I'm not just globally adverse to rooting (far from it), but I just have yet to find any reason to root this camera, especially now that the latest update seems to have corrected the stupid vanishing Google Account settings issue.
Now, if someone ever comes up with a fully functioning Lollipop ROM for this camera, you'll quickly see me singing a different tune, but until then....
Click to expand...
Click to collapse
Stretching beyond practice purpose is what makes android, android. Samsung makes good hardware, this camera will never fail from overuse and $25.00 android boxes perform like $25.00 android boxes.
I also do not use the stock launcher on any of my Samsung devices. I use lightning launcher on the camera(as well as my notes). The reason I like pie controls is that you gain extra screen space when you're using the launcher(no nav bar). So far, that's my only use of root, that could change in time; but not having custom recovery makes me very cautious in installing addition items.
cantenna said:
Stretching beyond practice purpose is what makes android, android. Samsung makes good hardware, this camera will never fail from overuse and $25.00 android boxes perform like $25.00 android boxes.
Click to expand...
Click to collapse
If you think a multi element autofocus mechanical extending zoom lens and an electronic shutter are never going to fail, then you better start preparing yourself for disappointment in about 2 years. LOL.
My three $25 AndroidTV boxes have been working great for years, running Netflix and Amazon Prime video since day one that I bought them. They're also running Kitkat even though they started out on Gingerbread.
10amla said:
I also do not use the stock launcher on any of my Samsung devices. I use lightning launcher on the camera(as well as my notes). The reason I like pie controls is that you gain extra screen space when you're using the launcher(no nav bar). So far, that's my only use of root, that could change in time; but not having custom recovery makes me very cautious in installing addition items.
Click to expand...
Click to collapse
I'm pretty sure that all of my Samsung devices have been rooted and ROMed using Odin. My first Android device was a HTC EVO 4G, which solely used custom recoveries (unless you just like going back to the dark years of ADB), so the first couple of times I asked devs for a flashable zip, I was all but excommunicated from the XDA forum for such blasphemy. Everyone here seems to do just about everything via Odin, so I don't really sweat not having a custom recovery. Most things that can go wrong (bootloops, soft-bricks, etc.) when mucking around flashing devices are solved via Odin anyway.
I've read a lot about this phone lacking a good camera. I own a S6 and an S7, so I dumped the camera app from my Samsung phone as well as the frameworks required for the camera app to work.
I'm not sure if this will work because I don't have a OnePlus 3T phone on hand (I am planning on getting one though), so this hasn't been tested. These files are stock files and unmodified. From what I've read as long as the frameworks are available, the APK files should function, so if anyone would like to test these out and report back to let me know how it works I would appreciate it.
Recommendations:
Just to cover all bases, I do recommend everyone to make a backup of their system. This archive won't make any changes to your system outside of installing the stock samsung camera app, but I don't want to be responsible for any issues if something stops working for you.
I don't foresee anything causing any trouble because if this doesn't work, you can just uninstall it like any other app and remove the *jar files and everything should be fine.
Here are the steps:
1. Extract the archive file. (you should see a readme.txt, SamsungCamera4.apk, and a system folder)
2. Install the "SamsungCamera4.apk" file like any other app (Don't open it up yet after you install it)
3. In the system\framework folder of this archive, you will see a bunch of *.jar files. You need to move those into the .\system\framework folder on your phone. (These are required libraries for the APK to work properly)
You can do this using an app like "Root Browser", but you NEED to be rooted for this to work.
4. After you copy the jar files over, reboot your phone.
5. (Optional) When your phone powers back on, try and clear the cache for your camera app.
6. Try and run the Samsung Camera app on your phone.
I hope this will work out on this phone, because I would really like to see a better camera option for such a great phone!
Let me know what you find!
Extracted the apk and doesn't install.
Do you get any errors? If so, what is the error?
m0d hipp¥ said:
Do you get any errors? If so, what is the error?
Click to expand...
Click to collapse
I installed it as a system app because it can't be installed normally (package appears to be corrupted) and installed all frameworks with rw-r-r.
When I open the app, it flashes black for half a second and then closes
Dang, okay. Let me look into this and see what I can do. When you tried installing it as a regular app, did it say it's not compatible or anything came up?
m0d hipp¥ said:
Dang, okay. Let me look into this and see what I can do. When you tried installing it as a regular app, did it say it's not compatible or anything came up?
Click to expand...
Click to collapse
I would like to be optimistic but if it was possible someone would have done it ages ago. You should be able to port from one Samsung to another as the frameworks are similar but you would need to build it from the source (i.e. build the app yourself from scratch) to have it working on Oneplus 3t and the source code is not open I believe.
You would have better chances at tweaking stock camera than porting Samsung's
Yeah, I might need to look into it a bit further. I was being optimistic and hopeful. I mean, I get that the hardware is specific to the device, but I don't see why a camera like Samsung's camera app couldn't be ported for all Android devices. After all Android is built off the same base platform.
Thanks for at least giving it a try. I think I will go and order my OnePlus 3T when I get home from work, then I'll be able to do more trial and error on my own as well!
Thanks for the attempts guys!
m0d hipp¥ said:
Yeah, I might need to look into it a bit further. I was being optimistic and hopeful. I mean, I get that the hardware is specific to the device, but I don't see why a camera like Samsung's camera app couldn't be ported for all Android devices. After all Android is built off the same base platform.
Thanks for at least giving it a try. I think I will go and order my OnePlus 3T when I get home from work, then I'll be able to do more trial and error on my own as well!
Thanks for the attempts guys!
Click to expand...
Click to collapse
Good luck in testing this once you get your phone but I doubt that you'll be able to port Samsung camera to Oneplus 3t. I think better idea would be working on the stock camera and improving the algorithms and post processing there.
If you get stuck and need experts view on your ideas or help with the code ask the greatest camera developer defcomg for help as he with his expertise will be able to assist you where possible
Thanks! I was actually looking at some other apps in the playstore that are considered "high def camera" apps. I know that a lot of the quality in pictures is based on the hardware itself, however I also know that the software is what drives the hardware to work the way it works. I mean, granted the specs of the camera might not be the same as Samsung's, but a 16mp camera should be pretty darn good quality nonetheless.
Has anyone played around with any of the other camera apps?
I know someone here tried the stock android\google camera. What about one of these?
https://play.google.com/store/apps/details?id=com.marginz.snap
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera
https://play.google.com/store/apps/details?id=pl.vipek.camera
https://play.google.com/store/apps/details?id=com.riseupgames.proshot2
I realize some of these are paid apps, and I'll look into it once my phone comes in as well. I definitely think there is opportunity for some optimization to make the camera a little better based off everyone's feedback about it.
This is a good initiative to improve the software side of the camera. I know sultanxda has his own hals in his ROMs but I find stock oxygen ROM to have better images and videos with less distortion.
All the luck for your attempt. If you're able to tidy up the algorithms ,it's gonna improve the camera for sure.
Crossing fingers.
That being said, what camera hal version is the sammy cam? But even if it´s the same, I belive you have to build a wrapper to shim the sammy function calls to the qcom camera hal... Good luck!
Propably logs (logcat and dmesg) from the crashing camera app would be usefull.
Bah, unfortunately it seems like I got ahead of myself. I did a little bit more looking into this, and it looks like the SamsungCamera app is actually using a custom SDK, so it doesn't follow the same practice your other universal apps use. Apparently SamsungCamera uses some more low-level technique that doesn't utilize HAL.
Hey Guy's
Have you tried Google Camera? You can get this on apkmirror.
Cheers
Right, it's like I suggested in one of my previous posts. There seem to be a few high def camera apps available across all android platforms which might be a great alternative. I'm not sure, but it's worth a look and test.
Neo+6210 said:
Hey Guy's
Have you tried Google Camera? You can get this on apkmirror.
Cheers
Click to expand...
Click to collapse
I tried Google camera and it crashes every time I open the app.. Any insight?
jdavis7882 said:
I tried Google camera and it crashes every time I open the app.. Any insight?
Click to expand...
Click to collapse
Use the link from this thread: http://forum.xda-developers.com/one...oogle-camera-4-2-035-141213305-t3531566/page1
Last post I think. First one doesn't work.
NoLunchBox_ said:
Use the link from this thread: http://forum.xda-developers.com/one...oogle-camera-4-2-035-141213305-t3531566/page1
Last post I think. First one doesn't work.
Click to expand...
Click to collapse
Same result
NoLunchBox_ said:
Use the link from this thread: http://forum.xda-developers.com/one...oogle-camera-4-2-035-141213305-t3531566/page1
Last post I think. First one doesn't work.
Click to expand...
Click to collapse
Having tried numerous Google camera versions unfortunately none of them give us the same controls (no HDR+, burst mode which no one uses ) that would give to Nexus line users as this is limited to just Google phones. If HDR+ worked on Oneplus 3T it would give the results that Pixel users get and since Samsung camera app is no-go as expected I think working on Google camera app to unlock HDR+ that Google/Pixel phones get would probably be the only solution to improve the results on OP3T.
@m0d hipp¥ can you port or arrange samsung Gallery app for Oneplus 3T???
It will be a great help bro
Hello all. I haven't poked or prodded, or gone "under the hood" since I picked up the Nexus 6P at launch. I started to have problems with battery life when the Nougat betas started rolling out. So I jumped to the OnePlus 3T. Things are better, but I still miss the actual Google experience. I'm curious if it would be possible to mod the 6P to give me all the things I want. Below is my list. Let me know if it's possible, please, and I'll try to figure it out on my own. A lot has changed since my Nexus 5...
First, I'd like to modify the build prop to where I can get access to the pixel launcher directly from the play store. I know this is easy, but I'm not sure if it will work with the other wishes.
Second, I'd like to be able to run with Franco's kernel. I think this would greatly help my battery life issues.
I'd like to be able to keep Android pay, as I see it as a huge security benefit (plus, I'm trying to get down to just my phone and keys, no wallet).
Lastly, if possible, I'd like to relock the bootloader. I know this one isn't very likely, but like I said, it's a wish list of sorts.
Any and all advice is appreciated!
Based on your needs, sound like keeping your phone running on stock unrooted is the best idea. You can just install the pixel launcher from apkmirror.
Magisk is able to hide root and let you retain the ability to use Android pay, for now. In the future, it may not be able to and you would need to be on stock for it the work. You'll get updates without the headache of having to use a computer or flash different recoveries just to update.
In terms of battery, a 3450mah battery in a nonbloated phone should be yielding you good battery life. If not, check for a rogue app.
Rooting and modding isn't the same as it was in '09, it's gotten to the point where it's just more of a hassle and headache just to get it running as it should/properly. Android has gone a long way in terms of security measures which is a huge plus but it also hurts the modding ability at the same time.
Sent from my Nexus 6P using Tapatalk
You would need to be rooted to use a custom kernel and you can't have a locked bootloader and be rooted on the 6P. If you want to use Android Pay on a rooted phone Magidisc and PhilsSU are the only options that I know of. You will get better battery life with Franco's kernel but it will never be great on this phone. Can't the one plus 3 be modded to give you a more Google experience? I read that the developer activity was very active with that phone.
jhs39 said:
You would need to be rooted to use a custom kernel and you can't have a locked bootloader and be rooted on the 6P. If you want to use Android Pay on a rooted phone Magidisc and PhilsSU are the only options that I know of. You will get better battery life with Franco's kernel but it will never be great on this phone. Can't the one plus 3 be modded to give you a more Google experience? I read that the developer activity was very active with that phone.
Click to expand...
Click to collapse
Totally derped on the custom kernel requiring root. The 3T does have a pretty deep community, but there's a little bit of a disconnect between the 3 and 3T. Another big thing for me is the touch latency. I swipe to type on the Gboard, and I'm always having to manually type words, because the 3T can't keep up. Never had the issue with the 6P though. Thanks for the advice on the 6P though. Might make it a weekend project, before switching my DD.
Seattleite said:
Totally derped on the custom kernel requiring root. The 3T does have a pretty deep community, but there's a little bit of a disconnect between the 3 and 3T. Another big thing for me is the touch latency. I swipe to type on the Gboard, and I'm always having to manually type words, because the 3T can't keep up. Never had the issue with the 6P though. Thanks for the advice on the 6P though. Might make it a weekend project, before switching my DD.
Click to expand...
Click to collapse
That's interesting. I thought the 3T was supposed to be a pretty fast phone. I'm in the market for something to replace my 6p since it probably won't last too far past the end of the warranty. It sounds like the 3T isn't it.
jhs39 said:
That's interesting. I thought the 3T was supposed to be a pretty fast phone. I'm in the market for something to replace my 6p since it probably won't last too far past the end of the warranty. It sounds like the 3T isn't it.
Click to expand...
Click to collapse
Oh, it's definitely a fast phone! Screen latency just isn't up to Nexus level. It's a great phone, no question. I would just like to jump back to "pure" Android sometimes. 3T, IMO, no better phone, for the value. Very customizable for sure, and solid as a rock (yay for 6GB of RAM!). Just feels slightly different from where I've made my home, since the Galaxy Nexus. The updates are even getting regular, to where you shouldn't worry about being left behind. I just miss carrying a little piece of Google with me from time to time.
This is a very unusual post for me but here we go:
I've been rooting, installing custom ROM's etc for about 6/7 years now, no phone has been saved from the rooting process but after the G4 plus I had failed I'm err'ing on the side of caution and after some questions answering with as definite an answer as possible to back up my own research:
I'm looking to install a LOS based rom (always been on CAM/LOS) and I'm wondering:
1, I use the NFC on this phone, does android pay work on an unlocked bootloader and a custom ROM?
2, What is the camera quality looking like on the custom ROM's?
3, I've briefly looked into the magisk thing in regards to banking apps etc, anyone had any joy getting them working?
4, finally, all Bluetooth working ok? I have the Moto 360 so need to ensure this works too.
Thanks in advance, like I said it's a rather unusual post for me but I just wanted to get some answers
Cheers guys and girls
Honestly I haven't even had the need to mess with the software on this thing yet. I'm getting insane battery life and great performance. Now later on the year I might go the custom ROM route but for right now it's pretty damn good stock. Very few things I miss from having root/ROM now
I'm at the same point to be fair, it's like an itch that needs scratching lol. Just missing the themes really more than anything.
Thank you for taking the time to reply
Bettry life and performance in stock rom is great and rom is near stock with some useful enhancement so i think atleast for me there is no need to install any custom rom.Battery life is insane in stock rom and you will not face any kind of issue in stock rom
My pixel and g5+ remain unrooted. I was in the same boat for previous phones (and tablets) and rooting them. At this point, I would have to struggle to think of a reason to root.
Priezti said:
This is a very unusual post for me but here we go:
I've been rooting, installing custom ROM's etc for about 6/7 years now, no phone has been saved from the rooting process but after the G4 plus I had failed I'm err'ing on the side of caution and after some questions answering with as definite an answer as possible to back up my own research:
I'm looking to install a LOS based rom (always been on CAM/LOS) and I'm wondering:
1, I use the NFC on this phone, does android pay work on an unlocked bootloader and a custom ROM?
2, What is the camera quality looking like on the custom ROM's?
3, I've briefly looked into the magisk thing in regards to banking apps etc, anyone had any joy getting them working?
4, finally, all Bluetooth working ok? I have the Moto 360 so need to ensure this works too.
Thanks in advance, like I said it's a rather unusual post for me but I just wanted to get some answers
Cheers guys and girls
Click to expand...
Click to collapse
Most of the custom roms do not comes with root now a days sl
Android pay should work if you dont root
If you use camera a lot than you will not be satisfied with camera in custom roms
Bluetooth works fine
Again banking apps will not work if you root...
I tried pretty much every custom rom available for this phone. The camera on all of them is a bit iffy. Mostly trouble focusing (especially manual focus and macro shots). After manual focus, sometimes the camera will crash. This is the case for most roms.
I did have some bluetooth issues too. The phone connected to the car without any problems, but I couldn't make any phone calls. It wouldn't connect to the dialer to actually place the call.
I went back to the stock rom: rooted, Pixel launcher as system app so I have Google Now cards and flashed the mod that corrects the aggressive sharpening of pictures. Couldn't be happier. Really excellent phone.
Just an update for anyone in the same predicament.
I took the plunge as the itch got the better of me. I went for the AOSPExtended ROM. Here is some feedback thus far:
Camera: tried the stock camera and the google one. Autofocus is pretty much crap as reported. It's OK sometimes and not the next. Not had chance to try too many shots to be fair so can't give a comment on quality.
Bluetooth for android wear and connecting to a phone kit seems fine, I've not made any calls via the handsfree kit however.
Performance and battery seem OK. Nothing to really report there.
I have root via magisk and the magisk hide let's me use Android pay, Netflix and my banking app. They all previously picked up on the unlocked bootloader.
On the whole its not bad at all. Camera is a bit annoying however I'm sure it will be sorted soon. Verdict is out on if it i s worth the hassle or not yet.
Hey Folks,
I just ordered a XZ Premium yesterday, which will come till this Weekend. First Thing to do is updating and unlocking the Bootloader, before checking out how actual SONY Stock Firmware looks like nowadys (My last SONY was a Z3). After that comes the next important Step. Contributing to the XZ Premium Forums.
I'm not sure what will be better or makes more Sense. The Options are:
-A new AOSP based Project for Xperia Devices
-A new Stock ROM Project (Snappatch Xperia Stock Exclusive)
-A new Patch for a own AOSP based Project (Combing the first two Options somehow)
If You want to know what the Patch is, just check out My Signature where You will find the Link to My actual Thread. I'm just really happy to get a XZ Premium (Since i don't like the XZ2 and prefer the XZP Design over the XZ1 Design), and can't wait to work with it and share the Results with You! Let Me know what You think which is mostly needed or what would make the biggest difference (Upgrade) to Your Device...
BR
Miustone said:
Hey Folks,
I just ordered a XZ Premium yesterday, which will come till this Weekend. First Thing to do is updating and unlocking the Bootloader, before checking out how actual SONY Stock Firmware looks like nowadys (My last SONY was a Z3). After that comes the next important Step. Contributing to the XZ Premium Forums.
I'm not sure what will be better or makes more Sense. The Options are:
-A new AOSP based Project for Xperia Devices
-A new Stock ROM Project (Snappatch Xperia Stock Exclusive)
-A new Patch for a own AOSP based Project (Combing the first two Options somehow)
If You want to know what the Patch is, just check out My Signature where You will find the Link to My actual Thread. I'm just really happy to get a XZ Premium (Since i don't like the XZ2 and prefer the XZP Design over the XZ1 Design), and can't wait to work with it and share the Results with You! Let Me know what You think which is mostly needed or what would make the biggest difference (Upgrade) to Your Device...
BR
Click to expand...
Click to collapse
I gotta say im very happy to hear that!
well most of the community here just want google camera working properly without losing drm keys and to have a native 4k screen option or 1080p/120hz hdr and all that stuff
so as i understood unlocking bootloader loses drm keys so flashing aosp roms with google camera doesnt make the camera better due to loss of drm (as noise reduction is lost along with the drm)
if its just possible a way to keep drm while having aosp that way we would have a God level of a camera, coming with 4k/1080p-120hz options that would do it! this phone would be the best for long time
but i guess its impossible to combine those features together which hurts me a lot knowing what potential this device has but cannot be used to the fullest...
any way thank you for joining in i love how developers here are very helpful and doing a great job
so to show my love to them im willing to donate cash to whoever makes a rom with all these features up and running, and there are other people too who are willing to do the same
so good luck dev <3 much love
madshark2009 said:
I gotta say im very happy to hear that!
well most of the community here just want google camera working properly without losing drm keys and to have a native 4k screen option or 1080p/120hz hdr and all that stuff
so as i understood unlocking bootloader loses drm keys so flashing aosp roms with google camera doesnt make the camera better due to loss of drm (as noise reduction is lost along with the drm)
if its just possible a way to keep drm while having aosp that way we would have a God level of a camera, coming with 4k/1080p-120hz options that would do it! this phone would be the best for long time
but i guess its impossible to combine those features together which hurts me a lot knowing what potential this device has but cannot be used to the fullest...
any way thank you for joining in i love how developers here are very helpful and doing a great job
so to show my love to them im willing to donate cash to whoever makes a rom with all these features up and running, and there are other people too who are willing to do the same
so good luck dev <3 much love
Click to expand...
Click to collapse
Thanks for the nice and quick response! As a ex Xperia Usera am i aware of the benefits and cons of unlocking the Bootloader. I remeber well how the Camera stopped working on the Z1 after unlocking the Bootloader and the lack the of Camera2 API. And it looks like it isn't much better these Days.
A thing i really miss here is the choice to have a locked Bootloader with at least Root to save the DRMs and to be able to use modified Stock. With My Patch would this End in endless Options and Ways of Optimizing/Customizing the Firmware without loosing any Features. But this is something i don't count on anymore (Android is a Fort Knox since Marshmallow/Nougat)...
How does it actually looks like on AOSP? The Camera works and has legacy Camera2 API Support? Lost Features are the Super Slow Motion Recording and Noise Reduction? The added 120Hz Mode and 4K / HDR Features seem to be there...!?
Well, i'm still not sure what to do. I see a lack of Stock ROMs on the Xperia Forums (I worked on this last Night but was unable to extract the sin Files), but i see also how AOSP has enhanced on Xperia Devices. We don't have treble Support on the XZ Premium but the XZ1 is already able to use Unified AOSP Builds and almost everything is working well thanks to the great Devs and of course SONY. And i'm sure AOSP will ever be a important alternative to Stock (Smaller, faster, fresher)...
So which Way should i go? I'm planning for Years to create a AOSP based close to Google Firmware like OS, but Stock is just looking great too on Xperias. And the DRM Fix is allowing to use all the Features on Stock for now!?
Hmm... Sorry for the many Questions! :angel:
first welcome..great to see devs have an interest in this device. I'm sure you will love it. only thing i would wish for is to have google camera work on it. as for custom roms ,not well versed in that scene,, its my first ever android device to still getting to grips with it.
kibet85 said:
first welcome..great to see devs have an interest in this device. I'm sure you will love it. only thing i would wish for is to have google camera work on it. as for custom roms ,not well versed in that scene,, its my first ever android device to still getting to grips with it.
Click to expand...
Click to collapse
Thanks
Couldn't live without a unlocked Android anymore. Android User since around 8 Years here (Made some Holidays on iOS and Windows). And i'm glad to be back on Xperia. Hope You enjoy it as much as i do and will with the XZP But to understand that right, what's the actual Point with the Google Camera? I managed to gain some extra functionalities in the Past, but how does it actually looks like after installing the Stock Google Camera (Or even the Modded Ones)?
Is it full functional? Are the Pixel (2) Configs working? Differences between Stock and AOSP? Would love to take a look on the Camera Part overall. I want to shoot great Results with My new Baby so it's also important for Me...
Miustone said:
Thanks for the nice and quick response! As a ex Xperia Usera am i aware of the benefits and cons of unlocking the Bootloader. I remeber well how the Camera stopped working on the Z1 after unlocking the Bootloader and the lack the of Camera2 API. And it looks like it isn't much better these Days.
A thing i really miss here is the choice to have a locked Bootloader with at least Root to save the DRMs and to be able to use modified Stock. With My Patch would this End in endless Options and Ways of Optimizing/Customizing the Firmware without loosing any Features. But this is something i don't count on anymore (Android is a Fort Knox since Marshmallow/Nougat)...
How does it actually looks like on AOSP? The Camera works and has legacy Camera2 API Support? Lost Features are the Super Slow Motion Recording and Noise Reduction? The added 120Hz Mode and 4K / HDR Features seem to be there...!?
Well, i'm still not sure what to do. I see a lack of Stock ROMs on the Xperia Forums (I worked on this last Night but was unable to extract the sin Files), but i see also how AOSP has enhanced on Xperia Devices. We don't have treble Support on the XZ Premium but the XZ1 is already able to use Unified AOSP Builds and almost everything is working well thanks to the great Devs and of course SONY. And i'm sure AOSP will ever be a important alternative to Stock (Smaller, faster, fresher)...
So which Way should i go? I'm planning for Years to create a AOSP based close to Google Firmware like OS, but Stock is just looking great too on Xperias. And the DRM Fix is allowing to use all the Features on Stock for now!?
Hmm... Sorry for the many Questions! :angel:
Click to expand...
Click to collapse
thats the thing, what I understood is aosp doesnt have legace camera2 API support, no super slow mo, no noise reduction (as drm is lost).
as for screen options 4k HDR or 1080p 120hz seem to show in options but people and devs say its not actually working, as after they choose an option and restart they claim to nothing changing.
these are the main reasons why people here hesitate unlocking the bootloader, as there is no camera2 API support on aosp so you get google camera but lose noise reduction and so many other camera features.
and there is no additional features that aosp give, neither of 4k nor 120hz work, so there is really no point of unlocking, if any thing its not just useless but also worsens...
and while still having drm, google camera has no support for max resolution (only 8mp) and does not have HDR+ option
so here to sum up:
2 thing that will make this community love you so much
1) fully working google camera while still having drm (or drm patch for that matter if its impossible to backup drm)
2) screen options of [email protected] or [email protected]
if you can do that in aosp build thats the best
if you can do it in stock based build, also great
but as I saw your snappatch rom it looks very nice but yet again, unless it has those 2 things, unlocking bootloader and going through this much trouble is useless in my opinion
so good luck bro I really appreciate your collaboration
Miustone said:
Thanks
Couldn't live without a unlocked Android anymore. Android User since around 8 Years here (Made some Holidays on iOS and Windows). And i'm glad to be back on Xperia. Hope You enjoy it as much as i do and will with the XZP But to understand that right, what's the actual Point with the Google Camera? I managed to gain some extra functionalities in the Past, but how does it actually looks like after installing the Stock Google Camera (Or even the Modded Ones)?
Is it full functional? Are the Pixel (2) Configs working? Differences between Stock and AOSP? Would love to take a look on the Camera Part overall. I want to shoot great Results with My new Baby so it's also important for Me...
Click to expand...
Click to collapse
the thing about google camera is in the HDR+ algorithm. its an incredibly easy way to produce some stunning photos. for HDR+ to work,, it needs the full camera2api and support of RAW images. currently, Sony use some kind of legacy camera2api and doesn't support RAW, So most ports are limited to 8mp and HDR+ doesn't work.
madshark2009 said:
thats the thing, what I understood is aosp doesnt have legace camera2 API support, no super slow mo, no noise reduction (as drm is lost).
as for screen options 4k HDR or 1080p 120hz seem to show in options but people and devs say its not actually working, as after they choose an option and restart they claim to nothing changing.
these are the main reasons why people here hesitate unlocking the bootloader, as there is no camera2 API support on aosp so you get google camera but lose noise reduction and so many other camera features.
and there is no additional features that aosp give, neither of 4k nor 120hz work, so there is really no point of unlocking, if any thing its not just useless but also worsens...
and while still having drm, google camera has no support for max resolution (only 8mp) and does not have HDR+ option
so here to sum up:
2 thing that will make this community love you so much
1) fully working google camera while still having drm (or drm patch for that matter if its impossible to backup drm)
2) screen options of [email protected] or [email protected]
if you can do that in aosp build thats the best
if you can do it in stock based build, also great
but as I saw your snappatch rom it looks very nice but yet again, unless it has those 2 things, unlocking bootloader and going through this much trouble is useless in my opinion
so good luck bro I really appreciate your collaboration
Click to expand...
Click to collapse
kibet85 said:
the thing about google camera is in the HDR+ algorithm. its an incredibly easy way to produce some stunning photos. for HDR+ to work,, it needs the full camera2api and support of RAW images. currently, Sony use some kind of legacy camera2api and doesn't support RAW, So most ports are limited to 8mp and HDR+ doesn't work.
Click to expand...
Click to collapse
SONY really HAS to include Camera HAL3 in the Future... Looks like the XZ2 will have the same Issues, but i wonder how hard it can be to change the Software of the own produced Hardware!? The Xperia Cameras would be outstanding against Others running AOSP, but even with all the Developer Support are they missing this Important Point...
I really hope i can gain some nice Results on Stock, otherwise would i like to try out Porting the SONY Camera App(s) to AOSP (With working Noise Reduction) which would even without HAL3 Support end in better Results as without HAL3 on AOSP/Google Camera Apps. Could be something for Xperia Cross Device Development, but i don't know yet if this is even possible without Porting the half of the Xperia Stock Systems to AOSP...
Can't wait to get My Hands on the XZP... Checking the Shipping State all 10 Minutes
https://nolp.dhl.de/nextt-online-public/set_identcodes.do?lang=de&idc=JJD1405123613478
Bit worried about the coming Camera Quality but i'm looking forward to get the best out of our Devices! Treble would also be something nice to have... Has anyone checked the Partition Table of the XZ Premium to see if there is a chance for a Vendor Partition!?
I think if you create a stock based rom with ported xz2 features and native 4k, you are doing the best and it most be easier and more stable than a aosp.
Blackghosthm said:
I think if you create a stock based rom with ported xz2 features and native 4k, you are doing the best and it most be easier and more stable than a aosp.
Click to expand...
Click to collapse
Yeha, i was thinking about to deliver Stock again (Since SONY Stock is also really good except of the End of Support with Updates at any Point). But that means pretty Device Specific Work (Lot of Work). I could ease the Things on Stock up if i would deliver real Stock (Barely Debloated) flashable ZIPs for Xperia Devices besides doing the Snappatch for Xperia (Debloating, Adding, Root, Features, Google App Replacements, Mods and such).
I see there is also actually no alternative to this "Turbo ROM" i've taken a look on. And to be honestly, i don't see Me using this ROM. So a Stock Flashable with some Extra Features and deep going Optimizations from the Patch could be something great in My Eyes. I could also extend the Support with that up to other Xperia Devices like the XZ1 and XZ2 (If the need is there).
Let's see what i'm able to do after getting My new Baby. I'm full of Hopes that i rock this Device for all of us here :fingers-crossed:
madshark2009 said:
due to loss of drm (as noise reduction is lost
Click to expand...
Click to collapse
I used to run an old build of AOSP to test out the 120 hz feature (though it's bugged. Sony devs are aware of this and I filed an issue in their github). The noise reduction was albeit the same. AFAIK the pictures you take will just show a green picture if you don't have the drm keys (at least the fix). But the noise reduction is still quite the same. However, I did not test that completely, just from memory.
As for topic, I'd rather go stock. The google camera isn't really something I'm after, but that's just me. I'm slowly teaching myself how to port stuff from other phones, specifically the new XZ2. I'd rather have stock + your patch + xz2 goodies, maybe?
iArvee said:
I used to run an old build of AOSP to test out the 120 hz feature (though it's bugged. Sony devs are aware of this and I filed an issue in their github). The noise reduction was albeit the same. AFAIK the pictures you take will just show a green picture if you don't have the drm keys (at least the fix). But the noise reduction is still quite the same. However, I did not test that completely, just from memory.
As for topic, I'd rather go stock. The google camera isn't really something I'm after, but that's just me. I'm slowly teaching myself how to port stuff from other phones, specifically the new XZ2. I'd rather have stock + your patch + xz2 goodies, maybe?
Click to expand...
Click to collapse
Yah in stock based the fix works good
But in aosp that doesnt work
iArvee said:
I used to run an old build of AOSP to test out the 120 hz feature (though it's bugged. Sony devs are aware of this and I filed an issue in their github). The noise reduction was albeit the same. AFAIK the pictures you take will just show a green picture if you don't have the drm keys (at least the fix). But the noise reduction is still quite the same. However, I did not test that completely, just from memory.
As for topic, I'd rather go stock. The google camera isn't really something I'm after, but that's just me. I'm slowly teaching myself how to port stuff from other phones, specifically the new XZ2. I'd rather have stock + your patch + xz2 goodies, maybe?
Click to expand...
Click to collapse
Getting XZ2 Features on the XZ Premium sounds Good to Me. Smart would be to integrate the Ported Content into the Patch so People can add it or just keep it Original with a untouched Stock Firmware (System+Boot). But i wonder...
madshark2009 said:
Yah in stock based the fix works good
But in aosp that doesnt work
Click to expand...
Click to collapse
Does it mean that the Camera does not work without this DRM Fix (Which isn't TWRP flashable (Without a PC))?
And AOSP has a working Camera out of the Box but without Camera2 API and with Noisy Pictures!? Just want to make sure i got it right before flaming about the lack of a mobile DRM Fix (Which could be included in ROMs, or simple be a Flashable ZIP for on the go)
Something i don't want is the need for a PC after flashing anything. I test so often My changes with Clean Flashs over the Day that it would kill Me to use Windows with this DRM Fix over and over again >.<
When you wana fix drm keys on stock or stock based rom you need twrp+flashable kernel (you can find it in afs)+flashable magisk+drm fix flashable file thats all so quickly without pc.
Im do it all the time in all oreo firmware.
Blackghosthm said:
When you wana fix drm keys on stock or stock based rom you need twrp+flashable kernel (you can find it in afs)+flashable magisk+drm fix flashable file thats all so quickly without pc.
Im do it all the time in all oreo firmware.
Click to expand...
Click to collapse
So there no need for the XperiFix Tool all the Time? Can You give Me any Links to it? I don't see the need to include it into the ROMs itself, but i would really like to take a look on what it does (Especially since Magisk in involved somehow). Maybe is there a way to get the Noise Reduction on a AOSP Port of the SONY Camera App. Can't say anything about this yet...
Kernel link:https://androidfilehost.com/?fid=673791459329069491
Drm fix link:https://mega.nz/#!LRoFkSDA!bOsnRRE1gRpAZ0su-bZMfUjvMB7aRkLEc3V63bOuKnM
You dont need xperifix but if you flash stock rom with flashtool you need to flash twrp in fastboot and if you want twrp you can download it from here:https://dl.twrp.me/maple/twrp-3.2.1-0-maple.img.html
Blackghosthm said:
Kernel link:https://androidfilehost.com/?fid=673791459329069491
Drm fix link:https://mega.nz/#!LRoFkSDA!bOsnRRE1gRpAZ0su-bZMfUjvMB7aRkLEc3V63bOuKnM
You dont need xperifix but if you flash stock rom with flashtool you need to flash twrp in fastboot and if you want twrp you can download it from here:https://dl.twrp.me/maple/twrp-3.2.1-0-maple.img.html
Click to expand...
Click to collapse
Thanks for sharing this with Me! Since this includes a Kernel am i wondering what's changed on the boot.img to get the Fix working. And it's dated on 2017 and still working on newer Firmwares?
I just extracted the latest G8414 .145 Firmware. Would be cool if i could Patch the kernel for the fix so that we can run the latest Kernel with it...
Yes it works,this is canbe good.
Miustone said:
So there no need for the XperiFix Tool all the Time? Can You give Me any Links to it? I don't see the need to include it into the ROMs itself, but i would really like to take a look on what it does (Especially since Magisk in involved somehow). Maybe is there a way to get the Noise Reduction on a AOSP Port of the SONY Camera App. Can't say anything about this yet...
Click to expand...
Click to collapse
Yes and no. On an old version of the hack, you can just flash the drmfix. However, on the new xperifix software, it seems to also change a few file attributes. Not really sure about that though.
Androplus' kernel (kernel.andro.plus) is always updated to the latest version. You can flash that and do the old method of the drmfix (flashing) instead of the xperifix. I've tried that before but it seems to not work. I probably missed a step anyways.
iArvee said:
Yes and no. On an old version of the hack, you can just flash the drmfix. However, on the new xperifix software, it seems to also change a few file attributes. Not really sure about that though.
Androplus' kernel (kernel.andro.plus) is always updated to the latest version. You can flash that and do the old method of the drmfix (flashing) instead of the xperifix. I've tried that before but it seems to not work. I probably missed a step anyways.
Click to expand...
Click to collapse
Im tried androplus kernel and it doesn't fix drm keys.