Development [PROJECT] LineageOS 20 development for the Edge 40 Pro / Edge+ (2023) / Moto X40 - Motorola Edge 40 Pro / Moto X40 (China)

Hello,
Basically i brought some people together, it consists of:
- @ThE_MarD, Developer (first attempt)
- @npjohnson, Developer (second attempt) / to work together with Marc
- @mxz55 (as device sponsor & eventually to help coordinate the project)
There's been a bunch of discussion where this plan got incubated, but it was in the Edge 30 forum (not the right place), hence im creating a dedicated topic here.
Previous discussion examples:
1) https://forum.xda-developers.com/t/...la-edge-30-dubai.4536169/page-6#post-88509185 with less relevant posts before it, and more relevant posts after it, such as: here, here, and here
This new topic will be used to clarify the state of things, and post any updates for those that are interested in LineageOS for this device. FIrst of all, to the state there's some updates:
09-05-2023: Motorola rejected the device sample request, so we will fall back to what was intended and i will source it
10-05-2023: The device can't be purchased in Canada yet (country of ThE_MarD) and will likely be released in Canada & US rebranded as Edge+ (2023), with the same codename lyriq.
As it's essentially the same hardware (except for battery and fast charging), a LineageOS ROM should be compatible with both variants (likely also Moto X40, if not after a conversion process) and therefore development can be based on Edge 40 Pro.
To not lose time on that, i've ordered the Edge 40 Pro to my house, and tomorrow i will ship it on to ThE_MarD in Canada, using priority shipping that's likely to take 3-7 days. Of course, i will include a Type A & Type B power adapter in the box.
Roadmap expectations:
11-05-2023 / 12-05-2023: Scheduled shipment to Canada
After it arrives, The_MarD will attempt to add LineageOS support for the Motorola Edge 40 Pro. Device has released sources for an older firmware version which would be sufficient to have official LineageOS support, even though another pending request for release of the latest firmware version sources would be beneficial on the long term, or maybe the precompiled kernel can even lead to unofficial side builds in case anyone experiences bugs that have already been fixed.
As you can read from the previous discussion links, there's a comprehensive plan for this project, like in the case that The_MarD is unsuccessful to get LineageOS running on this device, another experienced developer can be next up to try. In this case, The_MarD will ship the device on to said developer (at my costs, as sponsor) and that would be @npjohnson as said here, when we got him on board. Even though it's likely to not be needed, to say that @ThE_MarD can accomplish it. And the final gesture from me as sponsor is that the developer who accomplishes it, gets to keep the device. I will re-buy an Edge 40 Pro for myself to run LOS on, in case we succeed.
Except for the few odd posts from me, this thread shall be used by the main Developer to share progress updates with the community. It is likely to turn into a development tag thread (when device arrives and the LOS attempt commences) and where if the main Developer needs to, testers/help from other devs on XDA can be requested
I'll put some information on what bringing support to this device means to me (why i wanted it so bad, that im willing to fork so much money and effort towards the cause) below in Post #2.

My story about why i want this so badly:
The combination of these things form what type of user i am:
- I never settle for anything less than a custom ROM like LineageOS / AOSP
Even if the stock ROM is decent and relatively clear of bloat (and they promise a certain amount of large updates and security patches), you won't have the degree of freedom, control, privacy and security that a custom ROM can provide (of course, in the right hands). With everything, standard apps included, being opensource, you know what is running on your device and can audit if it's secure. Unlike with stock ROM's, where unknown, proprietary code is running.
In my eyes, a ROM line LineageOS is the only way to perceive the full power of latest flagship-gen hardware, as it's the lightest & bloat-free you can get. When someone has the latest phone with a lot of performance, it feels more than good enough with the stock ROM due to high raw performance, but that might come back to "just not knowing any better".
So now, an important aspect of why im doing all this effort and spending a significant amount of money: to have the greatest, the earliest. This device has the latest Qualcomm chipset, Snapdragon 8 Gen 2 (sm8550) that is making its way to today's flagships, having been launched around December 2022. If we can get LineageOS up and running here, it will be a prime occasion for the entire custom ROM scene, to have something like LOS on the latest chipset so fast. I have a knack for always wanting to use the latest tech, but it can be difficult to do so on your own terms (like having full control, as LineageOS provides)
Luckily, Motorola is a development friendly brand and has good recovery tools (it can even restore a full brick on the firmware level). I also spotted someone who is in the LineageOS implementation process for the same chipset with Samsung modifications (Galaxy S23 range): see it (along with "samsung-sm8550-dev" org) if you're interested. Developers are clearly setting their gaze on sm8550, and the samsung variant is close enough to main one, to possibly be useful in our scenario as well.

Reserved Post #2 (for later roadmap updates)
Update (11-05): device shipped to Marc in Canada, i had received it
Takes approx 2-5 days to get there

Heyyo! I'm definitely looking forward to this challenge! Yeah in the future we can try to point testers here as we go and post some milestones too

Update (11-05): device shipped to Marc in Canada, i had received it
Takes approx 2-5 days to get there

So I've started a GitHub organization for these development efforts here:
Motorola Edge 40 Pro / Edge+ (2023) / Moto X40 development
Motorola Edge 40 Pro / Edge+ (2023) / Moto X40 development has 5 repositories available. Follow their code on GitHub.
github.com
So far it's just the initial work of rebranding and updating eqs (Edge 30 Ultra) trees for rtwo, but it's a start!
Update: I also saw that rtwo codename is shared for both Edge 40 Pro and Edge Plus (2023) so that makes life easier.
Update2: I was told that Edge X40 is also rtwo so it sounds like we can do unified trees which is nice

I made an inquiry with Motorola on the kernel source code for rtwo as I'm not sure if we are missing some repos or if they are unused
GPL | Source request for Motorola Edge 40 Pro (rtwo) XT2301-4 - T1TR33.43-20-28 · Issue #503 · MotorolaMobilityLLC/kernel-msm
Please release the kernel tree, device tree and all the necessary audio/video/display techpack for Motorola Edge 40 Pro (rtwo) version T1TR33.43-20-28 Model number: XT2301-4 Codename: rtwo cc @chen...
github.com

I have two products
CN version!!
Is it possible to install Lineage ROM?
Lineage Development Team, I love you so much!!!

Heyyo @Kkjin , these are English forums, please use a translator to post in English as well
Google Translate
Google's service, offered free of charge, instantly translates words, phrases, and web pages between English and over 100 other languages.
translate.google.com
The plan is to support all 3 models of rtwo. Edge 40 Pro, Edge+ (2023) and Moto X40. It is currently under development and a test build isn't released yet... but once a test build is ready it will be posted in this forum thread.

ThE_MarD said:
I made an inquiry with Motorola on the kernel source code for rtwo as I'm not sure if we are missing some repos or if they are unused
GPL | Source request for Motorola Edge 40 Pro (rtwo) XT2301-4 - T1TR33.43-20-28 · Issue #503 · MotorolaMobilityLLC/kernel-msm
Please release the kernel tree, device tree and all the necessary audio/video/display techpack for Motorola Edge 40 Pro (rtwo) version T1TR33.43-20-28 Model number: XT2301-4 Codename: rtwo cc @chen...
github.com
Click to expand...
Click to collapse
Yeah we are definitely missing the repos... Audio device tree and display are proprietary so they apparently won't even be available on CLO... So either Motorola needs to release them or they need to be backwards engineered... I'm inquiring with Cosmin Tanislav as he did so for eqs (Edge 30 Ultra / Moto X30 Pro) so maybe he has some advice for us?

@Kkjin there is development on eqs (Edge 30 Ultra, Moto X30 Pro) but I am unsure where those builds are shared. I would recommend checking Telegram for Edge 30 Ultra or Moto X30 Pro communities and ask there

I wish I could get someone to walk me thru installing this once I get my new phone, right now I'm on the unlocked T-Mobile Edge and will be updating soon, probably next month, to the Edge+23.

ThE_MarD said:
Yeah we are definitely missing the repos... Audio device tree and display are proprietary so they apparently won't even be available on CLO... So either Motorola needs to release them or they need to be backwards engineered... I'm inquiring with Cosmin Tanislav as he did so for eqs (Edge 30 Ultra / Moto X30 Pro) so maybe he has some advice for us?
Click to expand...
Click to collapse
damn, i hope it will work out, or else we may need to make unofficial builds for a while (precompiled kernel). Does it seem like he wants to help? Also, it seems kinda random how Motorola treats the releasing of said things, as not all phones have stumbled on roadblocks like that, i still hope they will show goodwill on your github post and make the next release that's requested with those trees included.
I really hope Motorola doesn't abandon its growing reputation for being a developer friendly brand, let's see what happens.
In other news, the package arrived to Marc's city (per the tracking info) but is yet to be directed to his address from the depot. Canada Post is being slow, but it is what it is and we're not in a hurry or anything. He'll probably be able to really explore what the options are, once he got the device in front of him soon.
Ray.Marx said:
I wish I could get someone to walk me thru installing this once I get my new phone, right now I'm on the unlocked T-Mobile Edge and will be updating soon, probably next month, to the Edge+23.
Click to expand...
Click to collapse
It's not ready, and there is no guarantee it will be next month. Getting flashable test builds that boot is the first step, as soon they work for Marc and me they could be shared to testers in here.

꼭 성공하시길 바래요!! 모토로라의 장점인 터치샘플링 360Hz 기능도 있었으면 좋겠습니다. 개발에 도움을 주신 mxz55님 감사합니다...!"
Mod translation: I wish you success!! I wish there was also a touch sampling 360Hz function, which is an advantage of Motorola. Thank you mxz55 for helping us develop...!"

My wife received the Edge 40 Pro for me! I'm stuck out of town doing a training course tomorrow morning and then driving 6 hours home afterwards lol oof, I asked her to check it over and make sure the contents are ok and then if she wants she can rebox it for me lol...
Update: I decided to get her to power it on and set it up for me so that it can start the timer for the OEM unlock that I'll need
Special that is again @mxz55 !!! I can't wait to give it a shot!

I'm home! This thing is absolutely beautiful!!! Snapdragon 8 Gen 2 is seriously impressive on performance and it seems energy efficiency too!
Hopefully Motorola will check my new GitHub issue request instead of commenting on that other dude's request
GPL | Missing Source request for Motorola Edge 40 Pro (rtwo) XT2301-4 - T1TR33.43-20-15 · Issue #509 · MotorolaMobilityLLC/kernel-msm
Hello, I noticed for Motorola Edge 40 Pro (rtwo) XT2301-4 - T1TR33.43-20-15 kernel source release that a few repos are missing and I am humbly requesting they get released and if I missed any can y...
github.com

Nice, and i hope so too.. this is Motorola's chance to reaffirm their position as the development friendly brand that they have purported to be. It opens a significant market (advanced users) and allowing early adoption will only boost it further.
If it won't happen, i guess you'll wait out the bootloader lock period, which is 7 days for rtwo, and just start experimenting with what we've got, (or perhaps can have with Cosmin's help), knowing that a brick is easy to recover from with Lenovo Rescue & Smart Assistant tool.
Any word from Cosmin yet if he's interested to help, btw?
ThE_MarD said:
I'm home! This thing is absolutely beautiful!!! Snapdragon 8 Gen 2 is seriously impressive on performance and it seems energy efficiency too!
Click to expand...
Click to collapse
Let's get hyped up, because as we know, if you accomplish this, you can have it as your daily driver.. who wouldn't like a flagship as this one for it? I hope you like the size in hand btw, in many ways it's not comparable to say an Edge 30. Even the display quality & feel is quadtripled.

@mxz55 yeah this thing is definitely bigger and better than the Edge 30 in every regard lol, it's super impressive!
Unfortunately it seems Cosmin is a bit afk as I haven't gotten a reply from him, but tbh his activity is kinda sporadic as tbh I'm unsure what his work and personal life is like so he might have a bunch of stuff always on the go so this hobby doesn't always get time
Yeah the plan will be for meow to get a prebuilt kernel hopefully booting and then try to duplicate what eqs achieved and later get a source built kernel working

ThE_MarD said:
@mxz55 yeah this thing is definitely bigger and better than the Edge 30 in every regard lol, it's super impressive!
Unfortunately it seems Cosmin is a bit afk as I haven't gotten a reply from him, but tbh his activity is kinda sporadic as tbh I'm unsure what his work and personal life is like so he might have a bunch of stuff always on the go so this hobby doesn't always get time
Yeah the plan will be for meow to get a prebuilt kernel hopefully booting and then try to duplicate what eqs achieved and later get a source built kernel working
Click to expand...
Click to collapse
Try contacting him on telegram.

@keaheng I did try via Telegram but I didn't get a reply, I might try again in a few days as I don't want to push my luck
I did see Kkjin from here on Telegram in an rtwo group though hehe

Related

This is possibly my dream tablet; how 'dev-friendly' is it?

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.

No Nougat Update for a3 2016?

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

Custom ROMs

Do you think this device will get custom rom support considering the price I reckon it will the only issue is the device is only available in india that being said oneplus only sells to a select group of countries
It will get custom roms, this phone will be available also in Europe and India.
I am planning to get this device. Earlier I was hell bent on getting Asus Zenfone 5Z which boasts of same configuration as OPO6, POCO F1. But then I saw how there is absolutely no development going on for the device! I am just hoping it doesn't happen with POCO F1.
Edit : https://www.xda-developers.com/xiaomi-poco-f1-developer-community/
Sounds promising. It's upto the developers now if they think this device deserves some Custom ROMs love ?
Easier bootloader unlocking, Kernel sources on Day 1 and Flagship specs at the cheapest available price... Surely it will get Custom ROMs once a few flash sales are over and the device ends up in a few experienced developers' hands... It surely will be the Best selling SD845 mobile in India for the coming months since other competing phones are a bit old and costly... Expect to have really healthy development considering Xiaomi phones generally have a very active community for Custom ROMs...
Dang. I just bought a mint condition Oneplus 5T for $320. Did I make the wrong decision? xD
This thing will get a lot of custom roms!
I'll be honest. The best hope this device has is Indian developers. Mostly because they will need VOLTE which is not open source. Also most of the main developers for the major teams are based in the US where this device will not be, meaning that US devs wont be getting it, nor has xiaomi been forgiven by most of the devs here on XDA.
I think by the end of next month there will be lot of custom roms for Poco F1. Good gesture from Xiaomi. Supporting developer community.
No question about that, custom ROMs are coming, definitely. Just think about this - the max 2 has already been treble-ized and a custom ROM based on android 9 is in development.
Xiaomi will be releasing GSIs for this which will be very easily kangd into custom ROMs. No good reason why there won't be loads of development
thesoupthief said:
Xiaomi will be releasing GSIs for this which will be very easily kangd into custom ROMs. No good reason why there won't be loads of development
Click to expand...
Click to collapse
There is a difference in custom roms and development. They are not the same. Xiaomi always has roms. But none are developing on the device or working directly for that device.
Also the gsi don't do any good. Not for custom roms. Those will be still have to be built per device.
zelendel said:
I'll be honest. The best hope this device has is Indian developers. Mostly because they will need VOLTE which is not open source. Also most of the main developers for the major teams are based in the US where this device will not be, meaning that US devs wont be getting it, nor has xiaomi been forgiven by most of the devs here on XDA.
Click to expand...
Click to collapse
Those in NA might import it, but the deciding factor will likely be availability of source, and 3G/LTE band support on global variant. Americans don't incur an "import" fee/tax like in other countries, so price shouldn't be an issue.
Kernel source is due for release on August 29th.
Reportedly compatible with the following US networks (covering most bases, I reckon):
T-Mobile 3G, T-Mobile 4G, AT&T 4G, Plateau Wireless 3G, Union Wireless 3G, Viaero Wireless 3G, West Central Wireless 3G, U.S. Cellular 4G, Verizon 4G, C Spire 4G, ClearTalk 4G, iWireless 4G, Limitless Mobile 4G, Mosaic Telecom 4G
This phone is treble enabled, so you can directly flash GSI on this and will work flawlessly (as far i think)
I will try android pie gsi as someone releases treble enabled twrp for it. It will be on xda as soon people started getting phones
zelendel said:
I'll be honest. The best hope this device has is Indian developers. Mostly because they will need VOLTE which is not open source. Also most of the main developers for the major teams are based in the US where this device will not be, meaning that US devs wont be getting it, nor has xiaomi been forgiven by most of the devs here on XDA.
Click to expand...
Click to collapse
Unavailability in US has been the case for almost all Xiaomi phones but the thing is Xiaomi mobiles in XDA has one of the most active development... Many device has recieved unofficial Treble ports and already about 10 or more device has working Android Pie builds... Considering Poco F1's price and specs it shouldn't be a surprise if it ever has the most active development in XDA...
I think many Indian devs are good as any other devs outside. And even if the phone is launching in India only, many devs living outside would also try to get there hands on global version because of how much this phone offers for the price. Also Xiaomi releasing kernel source is a great move to motivate devs and upcoming devs to build custom roms.
bharathulaganathan said:
Unavailability in US has been the case for almost all Xiaomi phones but the thing is Xiaomi mobiles in XDA has one of the most active development... Many device has recieved unofficial Treble ports and already about 10 or more device has working Android Pie builds... Considering Poco F1's price and specs it shouldn't be a surprise if it ever has the most active development in XDA...
Click to expand...
Click to collapse
Getting ports is not development.
Price doesn't mean much in many places.
You are right. It has been and that is why none of the main developers of teams ever get the device.
I still have hope for this oem but we will see. They have a lot to make up for here with developers.
As for the most development. That sadly will belong to the pixel line. Which is what all the top developers get.
zelendel said:
Getting ports is not development.
Price doesn't mean much in many places.
You are right. It has been and that is why none of the main developers of teams ever get the device.
I still have hope for this oem but we will see. They have a lot to make up for here with developers.
As for the most development. That sadly will belong to the pixel line. Which is what all the top developers get.
Click to expand...
Click to collapse
In India, price means a lot... That is why most Apple has such a bad market in India and companies like Xiaomi with value for money products have such a huge market here... There are really skilled Indian Developers who opt to buy such cheap but Good devices...
They themselves stated about bootloader unlocking and custom ROM flashing in the launch event... Xiaomi is one of those very few companies who encourage rooting and stuffs without voiding the warranty...
In My personal experience, Xiaomi devices have very strong community support in XDA, I personally have Redmi 3S, Redmi Note 5 Pro and Redmi 5A... My Friends have a wide range of Redmi devices and They all have a Great custom ROM supply...
Its all from My knowledge and thoughts, just a healthy change of idea...
bharathulaganathan said:
In India, price means a lot... That is why most Apple has such a bad market in India and companies like Xiaomi with value for money products have such a huge market here... There are really skilled Indian Developers who opt to buy such cheap but Good devices...
They themselves stated about bootloader unlocking and custom ROM flashing in the launch event... Xiaomi is one of those very few companies who encourage rooting and stuffs without voiding the warranty...
In My personal experience, Xiaomi devices have very strong community support in XDA, I personally have Redmi 3S, Redmi Note 5 Pro and Redmi 5A... My Friends have a wide range of Redmi devices and They all have a Great custom ROM supply...
Its all from My knowledge and thoughts, just a healthy change of idea...
Click to expand...
Click to collapse
They are doing the same thing OEM have done before. Not to mention that they require to unlock the bootloader is bs.
To be honest, the only reason most devs even get the device is because xda buys it for them. That is why Franco supports the OEM.
I understand that is the way it is in India. That is why I said that it will most likely be developers from there that will need to focus on development. Not to mention that VOLTE is really needed in India and not anywhere else. Nor is it part of open source. So that will take an Indian dev to work on or there will be thousands of posts asking why VOLTE doesnt work. I talked to a few of the lead devs from different teams about the device and I got the same answer from all of them, they have zero interest in the device let alone the OEM. So one of their users will have to get the device and maintain it. Hell most wont even support this oem officially. But then you really cant blame the devs after what this company has done here.
I cant say about the device as I know zero people with the device and there is less then 1% chance that I even know anyone with the device form the OEM. But that could also be part of my job as they are banned along with ZTE and hauwei.
No 9.0 PIE ports for sd845?
I checked some sd845 phones like op6, mix2s, 5z, they dont have any custom roms based on 9.0. And they dont have too much custom roms like redmi note 5 pro or a1 etc. Can somebody guide me ??

Any rumors about when update to Android 9 for Huawai Mate 10 (pro) will come?

As Huawei Mate 10 pro was shipped with Android 8 last year I believe Mate 10 Pro also was a part of the Project Treble initiative. If that is so, is it correct to assume that we will soon see an OTA update for Android 9 to the Huawei Mate 10 Pro? And if so, does anyone know anything about the timeline? Like when can we expect to receive Android 9?
Project Treble is a major re-architecture in the way Android works. In essence, it separates the Android operating system (the Android 'framework') from the vendor Hardware Abstraction Layers ('HALs') that allow for the OS to work with the device's hardware
Click to expand...
Click to collapse
There have been a few OTA updates including safety patches until August 2019. So that is all good, but when I look in the "About Phone" in settings I am still on Android 8. As I am running this Mate 10 unrooted with a stock ROM I am really looking forward to Android 9 update, and have been checking frequently for new updates without luck.
Anyone knows more about this? Any set date or rumors about an upcoming update to Android 9 for the Mate 10 (pro)?
Currently there is Public beta going on if you are lucky for it to be available.
Date unknown. Probably sometime after the Mate 20 released.
Im in the same boat. Waiting for updates to alot of promised features
that are still lacking in the Mate 10. If Huawei released Android 8.1 for people outside of
China we would already have them.
Instead they are quick to release PUBG and GPU turbo fixes cause we would rather have that than updates for
Camera and Slow Mo 960fps etc.
Second beta was just released. Will update on Friday.
Information from the official Huawei forum in Serbia says that rollout of the official EMUI 9.0 for Mate10 Pro will start on December 14th.
So the Emui is equal to the Android version as in when Huawei update/bump their EMUI to 9.0 that means they will also bump the core to android 9?
Ok, probably just me that have read to much into the Project Treble an the separation of HAL. Since I first read about the HAL last year I kind of figured that the mobile devices that shipped with Android 8 would get a really timely bump to Android 9, like within weeks only after the android bump. So in my mind I kind of expected the roll out of new Android to be almost close to equal to the end of beta for Android 9.
On a semi related question, iirc the back story of the Project Treble was that Google wanted to address the fact that manufacturers did not commit to keep their Android devices updated, and that most of the manufacturers has a short life span of updates. Which combined lead to ie some bad press regarding vulnerability for many older Android devices, along with a less desirable user experiences with aging Android devices. Not to mention the lack of abilities to take advantage of all the newer software improvements that follows each Android update each fall. There have been a couple of Google initiatives prior to Project Treble, without hardly any traction and without Google being able to force manufacturers to stay committed.
So with the Project Treble Google did from what I can remember,make it mandatory for join the Project Treble for those who shipped their devices with Android 8. In my mind that translated to all kinds of things. Like Google putting down minimum requirements for number of updates manufacturers had to commit to, the speed of which they release updates etc.
However, did Google in fact put any of those requirements into Project Treble? Can we in fact look forward to having ie set number of supported updates from manufacturers in the future? Or will the big brands still be able to ignore their customer base rapidly and push forward with new models and focus their energy towards people updating their devices and buying the next year model rather then keeping their previous model with less overall waste, less economic impact and a more sustainable hardware update factor?
Treble means it would be much quicker and easier for oems to update to the newest version of Android, but it would still have to be the OEM making the update and pushing it out to your phone (unless it's an Android one or pixel phone I don't think Google themselves creates the updates)
There are no mandatory commitments to speed or number of updates, I think the only requirement was must be able to boot aosp (but unless your bootloader is unlocked you can't flash aosp anyway)
They will not release the 9 in the near future because they will launch mate 20 in less than a month.... they don't want to hurt sales.
avatar_ro said:
They will not release the 9 in the near future because they will launch mate 20 in less than a month.... they don't want to hurt sales.
Click to expand...
Click to collapse
Yeah but not the final version we need the beta at least ?
punkerEVO said:
Treble means it would be much quicker and easier for oems to update to the newest version of Android, but it would still have to be the OEM making the update and pushing it out to your phone (unless it's an Android one or pixel phone I don't think Google themselves creates the updates)
There are no mandatory commitments to speed or number of updates, I think the only requirement was must be able to boot aosp (but unless your bootloader is unlocked you can't flash aosp anyway)
Click to expand...
Click to collapse
Well if Google didn't take any steps to enforce manufacturers to actually keep updating they should keep their mouth shut about it later when we will see as usual that android devices are lagging behind in version numbers.
I really thought Google went balls in and was brave last last year with Project Treble and put down some new ground rules for their OEM's. But now it seems treble is just as weak hearted as the previous attempts from Google. Well I guess the solution is custom ROM's.
Manufacturers will never keep updating unless they are pressured to do so, they will always chase the sale of the next device and try to maximize profit rather then committing to last years hardware is up to date. So I guess project treble was a nice idea but google lacked the balls to actually lay down the law and demand dedication. Spineless. And to think they once lived by the catchphrase "don't be evil".
Can you test in Europe? I know that the next person in China is testing k.b 1500 users !?
---------- Post added at 08:31 PM ---------- Previous post was at 08:30 PM ----------
Sorry Google translator is not the best.
:laugh:
hondasoma said:
Can you test in Europe? I know that the next person in China is testing k.b 1500 users !?
---------- Post added at 08:31 PM ---------- Previous post was at 08:30 PM ----------
Sorry Google translator is not the best.
Click to expand...
Click to collapse
Beta test in Europe is already opened. 101 per country

Question will the Galaxy S23 range have a ROM scene?

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 !

Categories

Resources