Is there anything that predicts developers will take more interest in the Galaxy S23 range, so we can finally have a custom ROM scene for Galaxy?
Maybe because the S23 (all devices: S23, S23 Ultra, S23 Plus) ditch Exynos in favour of a Qualcomm SM8550-AC, an S23-exclusive version of the Snapdragon 8 Gen 2
Did we need a change of wind to make things turn out differently for this device versus earlier Galaxy S ranges? I really hope it's time for renewal, as if im not wrong, the last one that had a nice ROM scene & development going on was the Galaxy S5+ which is so many years ago..
I am talking about a sizable custom ROM scene (all recent devices were dealt a bad hand, or completely lacked it) and the least that would make me very happy: the entry of LineageOS, something that's not been there for years, surely for reasons.
Due to having been away from Galaxy as a result of the lack of ROM scenes in prior devices, I am out of the loop regarding Samsung Galaxy platforms for development support, can anyone state what the main things holding it back have been in recent years? Things being locked down too much, like with other major brands? For what the main blockers are, is there reason to believe that the S23, or the move from Exynos to Qualcomm chips on the other hand, will make a difference? Because as far i know, Qualcomm is the proficient & preferred platform for most devs.
Well as much as Samsung makes everything depend on Knox not being tripped, I doubt it.
I noticed that something may be ongoing when it comes to custom ROM (LineageOS, chipset) work for Galaxy S23+, see: https://forum.xda-developers.com/t/lineageos-progress.4582781/
Development there can benefit S23 Ultra vice versa, as it's similar and also sm8550-ac, who knows if that person succeeds they'll move on to S23 Ultra afterwards. I know it's speculation, but in my book these are hopeful signs.
Rom scene has been dull on this side due to Samsung Crippling devices when rooted (Knox being permanently tripped - hence killing resale value) and Dev's losing interest in Samung. We have 2 roms and 2 devs actively supporting the development here which is nothing like the Galaxy S5 or Note 4 Days.
Aside to the above, The stock devices are so good, that there's nothing more you can achieve by rooting which can outweigh the cons of rooting.
JazonX said:
... We have 2 roms and 2 devs actively supporting the development here...
Click to expand...
Click to collapse
There exist at least 2 other very good and stable Roms with lots of mods for the Ultra.
ATN Rom and VN Rom.
just noticed this thread about gsis on the s23 range : https://forum.xda-developers.com/t/how-to-gsi-on-s23-ultra.4564249/#post-88279455 (seems to be interesting)
(also noticed a discussion on installing other gsis on the xiaomi 13 : https://forum.xda-developers.com/t/xiaomi-13-gsi.4572035 )
seems to be interesting to me ... maybe I ll buy an S23 to try (I saw a used one that was not too expensive) but maybe I am not avanced enough to succeed
pierro78 said:
seems to be interesting to me ... maybe I ll buy an S23 to try (I saw a used one that was not too expensive) but maybe I am not avanced enough to succeed
Click to expand...
Click to collapse
Nice, i was mainly interested in LineageOS/for development to get going on something like the latest Snapdragon 8 Gen 2 (sm8550) chipsets, if only we can get a flagship from today in the best possible software package which is where i won't settle for anything less than LineageOS. Not in any case, no matter how good the stock ROM is - it's about freedom, control, privacy & security - where in LOS everything is opensource and auditable (as opposed to OEM.. you don't know what may be running and how secure it is). Not to speak of even faster security patch levels than from any vendor. I also believe you won't feel the true power of your high end hardware until you're running an OS that's practically as clean as AOSP, such as LOS. It's like people dont know any better, and that raw performance (flagships..) offsets your perception anyways.
Since this topic, i've set my gaze on a new device with the same chipset (sm8550) as the Galaxy S23 range - the Motorola Edge 40 Pro, a flagship.. even if chaptsand (as per https://forum.xda-developers.com/t/lineageos-progress.4582781/) can pull it off for Galaxy, i found a way to kickstart the effort for Moto Edge 40 Pro as well, by sponsoring it and bringing a few devs together. If you're interested in that effort, read some comments before and after this one: https://forum.xda-developers.com/t/...-motorola-edge-30-dubai.4536169/post-88509185, and it still has to be moved into its own topic. But if that gets accomplished and for Galaxy it doesn't turn out well, at least ill have something to recommend to anyone that wants LineageOS on a latest tech flagship. For those that think like me, and won't ever settle for less.
mxz55 said:
Since this topic, i've set my gaze on a new device with the same chipset (sm8550) as the Galaxy S23 range - the Motorola Edge 40 Pro, a flagship.. even if chaptsand (as per https://forum.xda-developers.com/t/lineageos-progress.4582781/) can pull it off for Galaxy, i found a way to kickstart the effort for Moto Edge 40 Pro as well, by sponsoring it and bringing a few devs together. If you're interested in that effort, read some comments before and after this one: https://forum.xda-developers.com/t/...-motorola-edge-30-dubai.4536169/post-88509185, and it still has to be moved into its own topic. But if that gets accomplished and for Galaxy it doesn't turn out well, at least ill have something to recommend to anyone that wants LineageOS on a latest tech flagship. For those that think like me, and won't ever settle for less.
Click to expand...
Click to collapse
thanks ! very interesting and generous from you !!
but I must say I am more interested in a hardware with a "flater" screen than the Edge 40 Pro.
an inconvenience with the S23 is that you are losing OTA with stock rom if you root it ( https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-samsung-galaxy-s23/ )
so, unless there is some AOSP rom with updates for the S23, it seems safer to me to go for the Xiaomi 13 (after I had a look at this guide : https://forum.xda-developers.com/t/...bootloader-root-flash-twrp-flash-rom.4538433/ ) ... or maybe I ll go for the Poco F5 pro 12/256 as it should start with an early bird price of 499E tomorrow, although it s an SD 8+ gen 1 instead of an SD 8 gen 2 (oh it will be 479E with the 20E coupon on https://ams.event.mi.com/fr/poco-f5-series-product-launch ) ...
good luck !
Related
Hi! This is my first post on XDA.
As a user of CM for more than a year ago on my i9300, and after enduring a lot of bugs, I wonder: What happens to CM?
It's a known fact that the Exynos platform is a headache for developers because there is no documentation or open sources from Samsung. So, things like the camera, the sound system, the HDMI output and the GPU do not work as they should.
However, here are many good developers who have fixed these bugs, or at least improve them a bit. And most of these fixes are open source and accessible by everyone on Github.
So, what is waiting CM to implement them? Giving credit to their authors, obviously.
CyanogenMod announces itself as an alternative to the stock firmware that lets you take full advantage of your smartphone, making it better and more stable. Now they are also a company: Cyanogen Inc. As a reputable brand, it should offer a higher quality firmware. ROMs like Nameless (I'm using it right now) works better even being "not official".
This is just an opinion as a user. I'm not criticizing or forcing anyone to do anything. But if there are hundreds of people using a ROM with bugs that were fixed, why not implement them? I would be the first to help, but my skills are just about webdev.
Respect and thanks for i9300 developers on XDA, and sorry about my bad English. When I use my native language I express myself MUCH better. Trust me. lol
Thanks for reading.
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
Thanks for answering my topic. The opinion of a developer like you is very appreciated.
This situation only seems to give more reasons for not buy a Samsung phone again. This lack of support from the manufacturer is a disrespect to the user's investment. And fragmentation strikes again. Sad but true.
Thanks again for your great work of keeping this device alive for all of us.
StephenJSweeney said:
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
Click to expand...
Click to collapse
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
ouch01 said:
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
Click to expand...
Click to collapse
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
i feel you
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
StephenJSweeney said:
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
Click to expand...
Click to collapse
The thing with Motorola is that their stock roms are basically just stock android. No laggy touchwiz skins, just a google launcher. Bloatware is at a minimum. A low spec phone like the moto G still is great because of how vanilla its experience is.
Rumours have it that the galaxy S6 international variant will have an exynos processor. I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch. As it is now, phone's are so fast, that it's very hard to find a way of improving them. Like who compares app opening times nowadays? That will be much the case for 2015's flagships as well. I doubt I'd be disappointed if I had the next Samsung release if I thought I'd be in for a laggy UI, it's just whether I can tolerate the touchwiz experience or if I wanna switch to a vanilla aosp rom. That's where the problem arises.
arashvenus said:
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
Click to expand...
Click to collapse
But only in your imagination. There is noone at slimrom. Just check their gerrit.
whatsgood said:
Rumours have it that the galaxy S6 international variant will have an exynos processor .... I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch.
Click to expand...
Click to collapse
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Correct.
Eleve11 said:
Correct.
Click to expand...
Click to collapse
Well then, no more Samsung phones for me, then. Not unless they use Qualcomm..!
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
whatsgood said:
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
Click to expand...
Click to collapse
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
JustArchi said:
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
Click to expand...
Click to collapse
Yeah +1 for that. My next Phone will be definitly a Sony or a One plus. I think both are the developer friendliest in android ...
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
khanmein said:
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
Click to expand...
Click to collapse
Yeah you are right but i think the most decent phone is the htc one......i would buy a windows phone rather than an iPhone
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
whatsgood said:
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
Click to expand...
Click to collapse
its useless even if they port it to our i9300..1gb of ram..maybe its time to upgrade to more stronger phone..
The Z4 Tablet is possibly my dream tablet, it has a great screen, microSD slot, good battery life and it seems dev-friendly.
I've got no Sony experience and I see surprisingly little custom ROM development. How 'dev-friendly' is this tablet? Does Sony provide source codes, drivers? Are they easy in unlocking bootloaders and flashing stuff like radios? Does it seem likely custom post-Marshmallow ROMs will be cooked in 1,5-2 years from now on?
do some research!
e.g. here "Anybody work on root?" much off topic posts unfortunately
there are two section with the title "Development" here ...
look at the phones: Z3+ and Z5 (nearly the same sources)
and all you need with almost useful documentation in SONY's Developer world:
http://developer.sonymobile.com/
DHGE said:
e.g. here "Anybody work on root?" much off topic posts unfortunately
there are two section with the title "Development" here ...
look at the phones: Z3+ and Z5 (nearly the same sources)
and all you need with almost useful documentation in SONY's Developer world:
http://developer.sonymobile.com/
Click to expand...
Click to collapse
I admit my question was a bit lazy, but it'd be pretty easy for people like you with lots of experience/knowledge on this Sony platform to give me a general idea.
I ordered a Z4T, but while reading this subforom while waiting for the shipment, things start to itch me a bit.
I'll anwer my own questions the way I see it now: Sony is pretty developer-friendly by providing source code and build instructions, but it's pretty buggy and there are very few developers doing stuff for the Z4T. I guess it's because of the bad availability of the device and the relatively small user base. The people @ FXP build ROMs, but I haven't heard much about how useful these builds are. If anything, I heard people downgrading from the 5.1.1 build. Rooting is only possible by unlocking the bootloader and flashing @AndroPlus' custom kernel. His current TWRP build has a bug that makes it impossible to restore a device backup.
Sony provides the option for unlocking the bootloader, but you'll completely lose your warranty. Furthermore, the TA partition will be irreverably changed and you'll lose functionality.
Marhsmallow has been announced, so there's that.
SONY's devices are good compromise for me
@jelbo
Good summary!
My opinion:
The SONY devices are good hardware. I like them because they are water resistant since I lost a phone after cycling in heavy rain.
I have a Tablet xperia Z with CyanogenMod on it. Android 5.1
The start with that 3rd party ROM was slow and it was quite buggy. Also battery life was worse than with stock ROM.
I have a SAMSUNG Galxy S5 phone. They have Knox-protection on their devices. Quite evil compared to SONY. Because it was released with Kitkat I could root it via exploit and keep Knox untriggered. I could get CyanogenMod, even Marshmallow Alphas for the phone. But the drivers are not that good and the battery life with stock is very good (up to four days for me).
So I will keep that phone on stock and I used Titanium Backup to get rid of SAMSUNG's bloatware.
SAMSUNG do not provide documentation and many of their SOCs are proprietary - no chance to do any development for these devices.
Long post short: SONY is very open and relatively easy to hack on their devices.
Better (now) in price and features than the Nexus devices IMO. I would never buy a device without any chance to do development on it.
I think the bug in TWRP will get fixed soon (has bitten me once).
Thanks for your kind reply
DHGE said:
@jelbo
Good summary!
My opinion:
The SONY devices are good hardware. I like them because they are water resistant since I lost a phone after cycling in heavy rain.
I have a Tablet xperia Z with CyanogenMod on it. Android 5.1
The start with that 3rd party ROM was slow and it was quite buggy. Also battery life was worse than with stock ROM.
Click to expand...
Click to collapse
Sounds familiar. In my experience with the last few phones I've had, AOSP-based ROMs were always a tad slower and less battery-friendly than stock or stock based ROMs. For example, the stock 'Google Play Edition' ROMs ran like a dream on my HTC One m7, but others were always less smooth / battery friendly.
So, for the Z4T I'm not partularly worried about the lack of 3rd party ROMs. I'll be fine with stock rooted. But for the longer term, because of the unpopularity, I think it's unlikely to see much going on in a year from now on and that kind of makes me doubt my purchase.
I have a SAMSUNG Galxy S5 phone. They have Knox-protection on their devices. Quite evil compared to SONY.
Click to expand...
Click to collapse
Yes, but not more evil than Sony I think. Samsung's bootloader unlock 'trips' Knox and it'll disable features like secure storage and services that depend on it. It's also irreversible. It's an awful lot like Sony's irreversible TA partition 'tripping'.
Because it was released with Kitkat I could root it via exploit and keep Knox untriggered. I could get CyanogenMod, even Marshmallow Alphas for the phone. But the drivers are not that good and the battery life with stock is very good (up to four days for me).
Click to expand...
Click to collapse
I could root my Galaxy S6 using an exploit, without tripping Knox. I'm running 5.1.1 with an engineering bootloader, while still having my Knox untriggered. It's a luxury I'm not gonna have on the Z4T, unless an exploit will be found.
SAMSUNG do not provide documentation and many of their SOCs are proprietary - no chance to do any development for these devices.
Click to expand...
Click to collapse
Yes, it's one of the reasons I want to avoid a Samsung as my new tablet. Exynos is a black box, so custom, stock-based ROMs will be the best you can get. BUT, I'm doubting now. Custom, stock-based ROMs are fine with me - as you mention, battery life is great. And on top of that, Samsung is so popular that lots of development is being done. I think chances are bigger to see the Marshmallow successor being ported for older Samsung devices than we'll see on this Sony Z4 Tablet in the future. But that's an assumption, I don't have Sony experience, but I see things re pretty dead here, even though the device was released quite a long time ago.
Long post short: SONY is very open and relatively easy to hack on their devices.
Click to expand...
Click to collapse
I'm not really seeing that yet, but again, I've only looked at the Z4T now.
Better (now) in price and features than the Nexus devices IMO. I would never buy a device without any chance to do development on it.
Click to expand...
Click to collapse
The microSD is an essential part for me. If the Pixel C would have had a microSD-slot I'd have chosen that. Development and future updates are a huge selling point for Nexus devices.
I think the bug in TWRP will get fixed soon (has bitten me once).
Click to expand...
Click to collapse
Let's hope so.
Hopefully the Z4T will get some more love soon, as I have just sent my Pixel C back and taken a punt at a open box Amazon warehouse deal last night with 40% off the LTE
I love my Z3CT, Z3C and Ultra, which have had great support from the devs, so am expecting the Z4 to be the best hardware of the lot, but would also love a root method while keeping the bootloader locked for now.
Heres to hoping perhaps MM will lead to some kernel exploits.
scoobydu said:
[...] as I have just sent my Pixel C back [...]
Click to expand...
Click to collapse
What made you return your Pixel C?
I love my Z3CT, Z3C and Ultra, which have had great support from the devs [...]
Click to expand...
Click to collapse
Did it take a while to get to that point? Do you think the Z4T will have the same support?
jelbo said:
What made you return your Pixel C?
Did it take a while to get to that point? Do you think the Z4T will have the same support?
Click to expand...
Click to collapse
Dont get me started on the Pixel C from Google UK pricing error on day 1 and their refusal for a week to refund or swapout 32g for 64g devices, due to their error; then I had a hardware fault with the screen not responding after 24hrs of use. I found their support just awful More issues were being reported in the xda forum and I decided I wasn't going to spend £550 to beta test for google. Nice solid device but heavier that the Z4 and sliding the keybard across the keyboard to remove it, just made me nervous of scratching something everytime I did it.
To be honest the Z4 forums are very quiet, but so were the pixel c's; as a few people were commenting.
I had to root my Z3 Tab by loading the Z3 phone firmware and rooting that, as that had a kernel vunerability and the kernel on the Z3 tab didn't.
Once the Z3 phone firmware was loaded and rooted, I could backup my TA partition and reload the Z3 tab firmware, rooted.
Its generally the phones that get root and the tabs have to utilise what they can, unless of course a dev has the tab.
The tab forums got much busier once the device had a less risky root method.
Sad to see that Nut hasn't got a recovery done, but I am assuming that due to root only being available by unlocking and losing TA, so limited testers, but haven't had time to read the history yet.
I have to say though that the Z4 is fantastic in comparison to the Pixel C and I am very glad I have reverted to the device that I know especially at £360 for the LTE version + keyboard on Amazon open box. First time using and the device is pristine. To be fair the Z4 is many iterations of getting it right and the Pixel is googles first try. Once its at Pixel C v4 it will probably be very good!
Heres to hoping MM is officially released soon, so the chances of rooting may get better.
from Nut
This is the reason why I didn't release XZDR for the Z3+/Z4/TabZ4 yet, too much difference with the Shinano and older device trees.
Edit:
That should be solved with 2.9 though...
Click to expand...
Click to collapse
Seems the 64 bits is a material change, so things need to progress in 2.9 from my early readings.
scoobydu said:
Dont get me started on the Pixel C from Google UK pricing error on day 1 and their refusal for a week to refund or swapout 32g for 64g devices, due to their error; then I had a hardware fault with the screen not responding after 24hrs of use. I found their support just awful More issues were being reported in the xda forum and I decided I wasn't going to spend £550 to beta test for google. Nice solid device but heavier that the Z4 and sliding the keybard across the keyboard to remove it, just made me nervous of scratching something everytime I did it.
To be honest the Z4 forums are very quiet, but so were the pixel c's; as a few people were commenting.
I had to root my Z3 Tab by loading the Z3 phone firmware and rooting that, as that had a kernel vunerability and the kernel on the Z3 tab didn't.
Once the Z3 phone firmware was loaded and rooted, I could backup my TA partition and reload the Z3 tab firmware, rooted.
Its generally the phones that get root and the tabs have to utilise what they can, unless of course a dev has the tab.
The tab forums got much busier once the device had a less risky root method.
Sad to see that Nut hasn't got a recovery done, but I am assuming that due to root only being available by unlocking and losing TA, so limited testers, but haven't had time to read the history yet.
I have to say though that the Z4 is fantastic in comparison to the Pixel C and I am very glad I have reverted to the device that I know especially at £360 for the LTE version + keyboard on Amazon open box. First time using and the device is pristine. To be fair the Z4 is many iterations of getting it right and the Pixel is googles first try. Once its at Pixel C v4 it will probably be very good!
Heres to hoping MM is officially released soon, so the chances of rooting may get better.
Click to expand...
Click to collapse
Thanks for your reply, good info. I'm glad to hear some reassuring comments on the Z4T. Looks like you had a great deal as well. In the Netherlands they're hard to get. I payed €635 for the WiFi model... I'm still doubting a little bit to go for a discounted Samsung Galaxy Tab S 10.5 for €380 though. I read it'll even get Marshmallow in April. Price difference is pretty big and there's lots of stuff for it already.
I'll have a look in some Xperia phone subforums on XDA.
jelbo said:
Thanks for your reply, good info. I'm glad to hear some reassuring comments on the Z4T. Looks like you had a great deal as well. In the Netherlands they're hard to get. I payed €635 for the WiFi model... I'm still doubting a little bit to go for a discounted Samsung Galaxy Tab S 10.5 for €380 though. I read it'll even get Marshmallow in April. Price difference is pretty big and there's lots of stuff for it already.
I'll have a look in some Xperia phone subforums on XDA.
Click to expand...
Click to collapse
Yes there are no deals on the Z4 Tab in the UK and all the new prices are the same retail price.
Thats why I decided to take a chance on the Amazon one, as I could return it if it was damaged or anything; and normal 12 months warranty with Amazon.
For me I haven't had a Samsung since my Tab 7.7 and wouldn't personally have another, but each to their own. The devs were always complaining at Samsung not releasing all the source code to their SoC's, wheereas Sony seemed to be more dev friendly.
The Z3 Tab is fantastic if you didn't mind the 8inch, but I am hoping once the Z3+ root is forthcoming and general 64bit root/recovery is done, then we will have some progress; he says, not being able to help the devs on whats seems a lot of work.
jelbo said:
I've got no Sony experience and I see surprisingly little custom ROM development. How 'dev-friendly' is this tablet? Does Sony provide source codes, drivers? Are they easy in unlocking bootloaders and flashing stuff like radios? Does it seem likely custom post-Marshmallow ROMs will be cooked in 1,5-2 years from now on?
Click to expand...
Click to collapse
It's a shame that such a good device is so low supported by free developers even though it seems it's more open by the Sony in comparison with Samsung.
I noticed that some people think in the thread that not so much users have this device. I have an old phone so called HTC desire HD which was released in the faraway 2010, it is excellent supported as it even has the contemporary android 6.0. I don't believe that there are more HTC decide HD users rather than xperia tablet z4 users. Moreover, I see as my comrade-users of our device crying ? everyday on a Russian 4pda.ru site, that we wait but there's no a good root method, there is no a good description or a video showing us how does the only custom ROM work. What works and what is broken. And just not seeing good news over the course of several months. Of course, I am very disappointed in dramatic fashion, but I hope The change will come.
Thank you for attention!)
cut the drama
- you should not compare a phone to a tablet (numberwise)
- look into the fora for phones Z3+/Z4 and Z5
they have nearly identical SoCs, differences a sometimes build options
- there is a HUGE xperia cross devices forum here with tons of additional info
- the Z4 Tablet became available in June 2015
- the first sources from SONY showed up in .... June 2015
- I rooted the device in July - having done no Android programming or rooting before
- I ordered the device after researching (see below) and before there was root available because my findings showed that there would be sources and documentation from SONY so that if all else fails I would get later a custom rom or could even roll my own
- a video for "seeing" developing/hacking? Dream on...
- there is lots of documentation (even video) available, maybe no video on how to do a web search or an xda search
- searching (and reading and trying things out) worked for me - coming from SAMSUNG phones with no prior development experience on Android ... TRY IT
DHGE said:
- you should not compare a phone to a tablet (numberwise)
- look into the fora for phones Z3+/Z4 and Z5
they have nearly identical SoCs, differences a sometimes build options
- there is a HUGE xperia cross devices forum here with tons of additional info
- the Z4 Tablet became available in June 2015
- the first sources from SONY showed up in .... June 2015
- I rooted the device in July - having done no Android programming or rooting before
- I ordered the device after researching (see below) and before there was root available because my findings showed that there would be sources and documentation from SONY so that if all else fails I would get later a custom rom or could even roll my own
- a video for "seeing" developing/hacking? Dream on...
- there is lots of documentation (even video) available, maybe no video on how to do a web search or an xda search
- searching (and reading and trying things out) worked for me - coming from SAMSUNG phones with no prior development experience on Android ... TRY IT
Click to expand...
Click to collapse
Good summary.
Small point, but the rooting element is by unlocking the bootloader, which not all will want to do. It is though an option that exists and we are thankful for those that have done so in order to progress the dev support.
Hi
I was figuring buying a Spark X. I see the Spark series have no entry here, so I wander I had a good idea. Although, following various links here I think I found the man Porridgek3 works on this X model from a somewhat old COS13.0.2 (comparing to COS13.1.4 for others, e.g. Swift series).
Not being a coder myself I can't read the code at github, so I'd like if this is not stupid question/request to read a thread about what are the changes from stock COS13 to the Porridge custom CM13.
Thank you and happy new year to everyboby at XDA.
The Spark devices are pretty poor. They all have Mediatek processors and updates are much slower than for other Wileyfox devices.
flibblesan said:
The Spark devices are pretty poor. They all have Mediatek processors and updates are much slower than for other Wileyfox devices.
Click to expand...
Click to collapse
My aim is not to have a speed daemon. I search something with good and removable battery (Spark X has one and as about same hardware than Spark/Spark+, I guess the autonomy would be better), and I could easily remove the bloatware (stock CN13 would help, I believe, to switch to CMod if exists).
I currently have a Liquid-MT (my first smartphone) for which by chance there was a custom ROM available based on GB-2.3.6, and it was so difficult for me to jailbreak it that I decided to keep it as is until now when mechanical problems with the internal microphone make replacement nearly mandatory.
Also, I'm focused to keep as far away as possible from google and GAFAs I have no confidence in Samsung so I don't even try to know if their devices are easy to make free. That's why I was so happy to discover my target from a single European manufacturer (at least designer) that ships his own with CN, and I easily accept to have a poor camera inside, only 802.11bg and basic 4G. I also know that the Spark X has poor dpi compared to other Sparks because of larger screen, and accept this as a consequence of my decision on battery... an so on...
Not being very much aware in ROMs, I don't know by which tail to catch the beast. I don't really choose for a model, instead I exclude others: GAFA, big Broth, God keeps me away! High end... for tainted kids (or their backward parents), out! Chinese, let's them make phones for ... themselves. So what does remain? Here is my way.
SparkX continued
Hi, how did things go with the sparkx ? I have one here and after no updates for a long time the updates arrived and bumped to nougat and I began to feel like i was signing my life away.
A while back I found an old release of sailfish for my ZTE open C so ive been making steps towards porting sailfish to the sparkx. still in early stages but i am confident it is possible.
1stStep said:
My aim is not to have a speed daemon. I search something with good and removable battery (Spark X has one and as about same hardware than Spark/Spark+, I guess the autonomy would be better), and I could easily remove the bloatware (stock CN13 would help, I believe, to switch to CMod if exists).
I currently have a Liquid-MT (my first smartphone) for which by chance there was a custom ROM available based on GB-2.3.6, and it was so difficult for me to jailbreak it that I decided to keep it as is until now when mechanical problems with the internal microphone make replacement nearly mandatory.
Also, I'm focused to keep as far away as possible from google and GAFAs I have no confidence in Samsung so I don't even try to know if their devices are easy to make free. That's why I was so happy to discover my target from a single European manufacturer (at least designer) that ships his own with CN, and I easily accept to have a poor camera inside, only 802.11bg and basic 4G. I also know that the Spark X has poor dpi compared to other Sparks because of larger screen, and accept this as a consequence of my decision on battery... an so on...
Not being very much aware in ROMs, I don't know by which tail to catch the beast. I don't really choose for a model, instead I exclude others: GAFA, big Broth, God keeps me away! High end... for tainted kids (or their backward parents), out! Chinese, let's them make phones for ... themselves. So what does remain? Here is my way.
Click to expand...
Click to collapse
https://www.dropbox.com/s/bgce2efur8tq1ot/Screenshot_2017-05-13-17-13-44.png?dl=0 She said it was not compatible yet it got the wifi alliance http://www.wi-fi.org/content/search-page?keys=SM-A310F :confused: I think it's true because only the a5 2016 and a7 2016 got it but the a3 2016 hasn't?:crying:
Based on the existence of the certificate the update exists and is/was already under testing.
The only possible reason not to release it if they f*cked up the optimization of touchwiz for nougat like they did before a few times, resulting in failure to release updates to below flagship devices (like S4 mini).
The A36 is marketed as an ultra mid range device, so if it happens again despite their promises they could probably say goodbye to mid range buyers for once.
Let me explain: power users know Android. They (we) know that with every major update it's more and more optimized and less demanding on hardware, but Samsung seems to have a trouble following that trend with tw. They almost do the opposite, while people demand updates, and it's also in the interest of Google, so they have already warned manufacturers to do their best on the matter, specially Samsung after their past neglections. This topic has a great influence on our preferences and despite the other fields Samsung devices excelling in our eyes, it could change the situation. Now, most simple users choose devices based on our opinions. They ask us for advices. If I prefer Samsung devices, 100-150 people around me will prefer Samsung too based on my opinion; but if I prefer another brand instead, they will buy their devices instead. Now imagine how the numbers come with a lot more power users exisiting in the world, not just me.
The nougat update for A36 (having the broadest market amongst other A and J series devices thanks to it's handy size, yet powerful hw and quality housing) is a big opportunity to show us they have changed their attitude towards mid-range users, something people and Google are waiting for a long time, so they know it would be a disaster for them to back out from it in the final moments. I hope they won't.
I hope they release it but it explains why a7 and a5 2016 got nougat before the a3
link is broken
...if I get Nougat on my A3 2016...I won't ever enter this forum again.
Spreading negative information like this by pointing broken links as source is 3rd grade child stupidity.
It's not my fault if it doesn't work I saw it myself
Anyway if you want the link it's here https://www.dropbox.com/s/p9w3d54sk2fvguj/Screenshot_2017-05-18-18-20-37.png?dl=0. Next time don't swear at me.
arif8912 said:
Anyway if you want the link it's here https://www.dropbox.com/s/p9w3d54sk2fvguj/Screenshot_2017-05-18-18-20-37.png?dl=0. Next time don't swear at me.
Click to expand...
Click to collapse
These support guys don't know what they are saying... "I'm afraid it's not compatible" => there is no such thing. If they make a compatible build than it is compatible, simple as that. Also, when I've asked them, I got the response that IT IS GOOGLE WHO MAKES THE UPDATES, THEN THE CARRIERS REVIEW IT AND RELEASE IT. Yes, this is how it should be ideally if there would be a flexible hardware abstraction layer, but sadly it is Samsung who has to build the update after Google releases the source, and before carriers can deploy it... When I had to rate the conversation I wrote them that their support department has no access to proper information even about HOW updates work which is very troubling for conscious users who chose Samsung because of Android (+their quality hardware) and expect them to properly provide updates for their ultra mid range devices too, not just for their overpriced flagships.
http://www.samsung.com/tr/support/newsalert/100061 A3 2016 update got delayed to 29th may-2nd june
I'd like to get to as close to vanilla as possible. Not a fan of Samsung's ui or bloat. I'm coming from the tab s1 which had some pretty good roms. There are none for this device and it's almost 6 months old. I would make one myself but lack the necessary skills
Most of the newer top end Samsung Tablets get very little developer support since they cost so much. Happens with every new tablet having people asking where the developer support is for it. Samsung newer UI much nicer and any vanilla roms would take away most of the functionality that makes the tablets great. Apparently the S5e has some dev support.
Problem is Samsung seems to be super slow with there updates for the S7.
I've owned the S7+ SM-T970 for like just a week and I'm already feeling impatient waiting still running off the Oct. update while I keep hearing about about UI 3.0 update hitting there flagship phones.
Do you think at some point down the road when or before OEM support ends we can look forward to some working roms or Treble GSI options ?
Markeee said:
Problem is Samsung seems to be super slow with there updates for the S7.
I've owned the S7+ SM-T970 for like just a week and I'm already feeling impatient waiting still running off the Oct. update while I keep hearing about about UI 3.0 update hitting there flagship phones.
Do you think at some point down the road when or before OEM support ends we can look forward to some working roms or Treble GSI options ?
Click to expand...
Click to collapse
Not everyone gets the update at the same time (don't know how they handle when and who should receive the update). I only got a November update a few days ago (though some claimed to have already gotten it) and it offered few improvements. The tablet still feels the same as usual.
As one must choose between custom ROMs and Knox (especially warranty), I'm currently at a loss myself, and for the time being I haven't heard of anyone trying (or succeeded in) booting a GSI on S7/S7+ probably because of this, although it's theoretically possible (again thanks to Treble). At least we now have TWRP... it might be better if one day custom kernels become available.
So far this is the only tablet I know that can offer 120Hz display. My current phone (Razer Phone 2 which is also 120Hz-capable) still doesn't have a specialized ROM but I can already run GSIs on it with adequate performance. For new devices, going for GSI might be easier, but performance-wise it still has a way to go compared to specialized ROMs.
Think it has to do with the fact that snapdragon is locked on samsung