Proceed to http://www.asus.com/us/Phones/ASUS_PadFone_X_US/HelpDesk_Download/
Android 4.4.2 KK OS (V11.10.8.16)
The new kernel code has just been posted to compliment the recent update many of us received. still however, we cannot do much unless we can get our devices boot loader unlocked.
Related
Asus has posted source code for the Padfone X. While it's not possible to fastboot flash, you can "dd" a kernel to the proper block.
ASUS PadFone X Kernel Code for Android 4.4.2 KK OS (V11.10.8.7)
http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_X/PadFoneX_11_10_8_7_kernel.zip
You can also get to the above link by navigating through their support downloads http://www.service.asus.com/#!downloads/c1wax
Hellzzzz yeah...
So are you starting up donations yet to get your hands on Padfone X to start dev on a modded kernel ?
I can't wait to put different ROMs on here!
I bought a Xperia C, a fairly popular model here in Brazil, but I just found out that it's bootloader was locked until some months ago, when Sony decided it was time to let people unlock it.s bootloader.
But now I see the phone has never receveid an update after Jelly Bean 4.2.x and no Custom ROM was ever developed for it (all ROM's that I found are just themed versions of the OEM 4.2 Jelly Bean).
So I decided that maybe I could build CM or AOSP for this device but after reading about the process I discovered that there's no device tree or vendor or kernel info available anywhere for this device.
I think this is all because Sony allowed the bootloader to be unlocked just now the phone is discontinued, so the possible developers this phone had moved away from it too quickly...
It's a shame, because it's indeed a good device, but it's stuck in a old firmware because of Sony's lack of support - same thing happened to the Xperia SP, another excellent device, which at least had an unlocked bootloader which allowed a lot of Custom ROM's to be developed.
So, I wish to know if there's any salvation for this device or if I should give up on it...
PS: I am a software developer, but I don't understand anything about android or Java. I'm willing to learn and develop ROM's for this device with someone's else help... I'll just need to find time to do that...
if your bootloader is unlocked the first step is compile a custom recovery, normally twrp that you can find tutorials in here. the kernel source code is always provided because of the linux open source license, I'm on the cellphone so I cant post links but search for the twrp compiling guide in here. i hope this helps
Hello!
I have been following annual Google I/O 2017 and heard about all the benefits of Google's Project Treble.
I cannot help but wonder how are developers (for example here at XDA) able to create custom roms or unofficial Android updates. Why Google can't make official Android Nougat update for Nexus 7 2013, but you here at XDA can. What is different between your work and Google's when it comes to these things, as far as neither has access to hardware manufacturer's code support.
I have to say I am not a professional software developer, so I understand if this topic is beyond my comprehension.
Thank you!
"Why Google can't make official Android Nougat update for Nexus 7 2013"
Planned obsolescence.
"neither has access to hardware manufacturer's code support"
Google is obliged to release kernel source code because Linux(the kernel powering Android) is released under the GPL. The kernel is responsible for letting Android "talk" to the hardware. Developers at XDA can then modify the open-source kernel to "fit" newer versions of Android.
I'd like to chime in on this.
Let's use the Nexus 7 2013 as an example. The difference between what an official build of Nougat from Google would be and what a build of Nougat from XDA is that the Google released one will have updated devices drivers that are made specifically for Nougat, while the XDA released one simply uses the older device drivers and hope they work. In some cases they work flawlessly (mostly on Nexus devices), however other times there are things that don't work so they either need to be disabled or worked around. So essentially a Google released OS has everything updated and tested to work with the new OS, while XDA releases are more 'hacked' together to work (simply because the device drivers aren't Open Source). Google may not have access to the hardware drivers, but they still get them updated.
Now let's touch on Project Treble (and why I am so excited about it). Instead of each and every device driver needing to be upgraded and tested for each new OS version, the OS version will specify which version of the drivers (HAL's) will work with the OS. This means there will be a separate space where all the device drivers will reside, and the OS will simply load those when booting (no more proprietary binary blobs to include in the ROM! hopefully...).
This means on any Project Treble compatible device (all phones that ship with Oreo, and some that update to Oreo) with an unlocked bootloader, a user can simply compile AOSP and flash it directly to the device with no modifications and have the device work. I believe this is actually a requirement to pass Google's certification process for new devices with Oreo. That means, say, with the LG v30 if the bootloader is unlocked, there can be an AOSP ROM on day one of its release.
So instead of Android being strictly a per device compile, it is just a general compile (sans device specific features). However, this doesn't remove the old driver issue. If the drivers in their respective partition no longer are updated by the manufacturer, the later AOSP code will need to be modified to work around these (and accept them). This is still easier in my opinion than the binary blobs.
As for official updates, Project Treble allows device hardware manufacturers to work on updating the device drivers while the OS Dev (Samsung, etc) works on updating their OS. So it is a parallel development instead of a serial one (hardware AND os instead of hardware THEN os).
A question.
Do the Nexus 5X devices have the Treble system or project incorporated with Oreo?
I do not understand the other manufacturers that cheaper excuses are giving, it is true that they are not obliged but I think it would be good practice, maybe they think as before that you will not buy them a phone.
Does someone make a Change.org or similar campaign to ask all Android manufacturers to make a minimum effort?
Method to unlock bootloader
The device tree
The kernel (source code)
Proprietary blobs
Any other necessary repos
We recently completed a successful Kickstarter campaign for a minimalist smartphone running a modified version of LineageOS.
For that first version, we used the Xiaomi Mi A1 as the base phone. It’s a nice phone, official build and so straightforward to work with.
We would like to shift to a new phone, ideally something smaller, a bit cheaper (it doesn’t need to be super high spec). This new phone will need to be able to run Lineage (and so our modified version of Lineage).
I'm trying to figure out what we will need to ask for from suppliers so that we know that we can get a build working.
List above is what I have figured out so far. Would appreciate any comments.
In the past I would take it for granted that a device associated with XDA would come with an unlocked or unlockable boot loader and that the ROM, kernel and source for both the LineageOS and Ubuntu builds would be made available so that owners could try out both or mix their own. Being today's XDA and since I've not seen mention of it anywhere I have to ask whether an unlocked bootloader and fully open ROMS are part of the plan or are there steps in motion to lock people into the OS they choose at time of purchase?