support for x86 devices motoroloa razr i - General Omni Discussion

Support for x86 devices like the motoroloa razr i ?

up !

The usual answer: If a maintainer who *owns the device* does the work.
Nearly all of the Omni team are already too busy with devices we already own. (I haven't brought up the Moto G or Xperia Z Ultra despite owning them simply due to lack of time as it is in my case...) New competent maintainers are, of course, welcome.

Related

Development is going to be good!

Alot of Developers have bought this phone!! development for Xperia T / TX and V is going to be good! so far we have 2 elite developers 2 recog developers,, correct me if i am wrong
FXP have 4 members
Bin4ry, Defer, Kali, Jerpelea
Codeworkx!
Tilal6991 too for paranoid android
Gok for kernel is gonna be beast.
Lol @ 4. Good start but not exactly a lot. Yet.
...
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
well this is my first sony device, but looks promising, if sony stays open and doesn't screw up like samsung did, even if they are on updates, we'll have CM team for regural updates. actually, i hope this is first device i'll have for more than a year.
we'll see.
Sent from my Xperia T
Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
^aha your right
hello developer!
i think xperia t will get popular because it is the bond phone and the tx looks great in terms of design so it will get popular
Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah. The Infuse was a less popular device, and as a result, the developer community was highly cooperative for a while. Unfortunately, the device itself was a nightmare to work with so it was ditched by many. Although, interestingly enough, now that some of the worst aspects of this device development-wise have been identified, the Infuse is becoming kind of fun to work with again.
In the case of the T - all evidence seems to indicate that it's going to be a highly pleasant device to work with, AND if it's not a super-popular device, it may have a more pleasant development community than some of the more popular devices.
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.
AvRS said:
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.
Click to expand...
Click to collapse
I will have to decide on December 1st what phone I'm going to myself.
I personally understand the appeal of a quieter forum where the same issues aren't asked every couple of minutes.. Once or twice, I've actually had trouble finding a solution wading through the, "How do I ________" and most of them had the response, "do a search" :silly:
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah.... there are a lot of ungrateful members. I find myself in an awkward position because, I'm not skilled enough to develop a ROM but, I'm know I'm reliant on whatever XDA puts out to stay up to date with the latest ROMs.
Entropy512 said:
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
Click to expand...
Click to collapse
If I were in a position to take that stance, I would myself.
[/QUOTE]
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
[/Quote]
That unfortunately isn't really entirely an option for me. I'm on a family plan and have no capability of getting out of it at the moment. I don't have enough data to make 16 gigs with no SD card feasible.
I really got lucky when my Captivate had identical hardware to the Nexus S and Samsung was actually good about supporting the devs.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.
Click to expand...
Click to collapse
Do you think that may have some weight on why Google decided to hop to LG for a Nexus device?
Either way, it sounds like I'll be on the Xperia TL or LG Optimus G this upgrade. The decision isn't exactly becoming easier to make though. At least I managed to scratch off the HOX+
i chose xperia phones becase developers say they are not hard to develop , i have an xperia ray and i have a buttload of roms to choose from... i cant decide so i need to fash every 2week!! (flashaholic :l)
also because sony provides solution for bootloader unlock
Here's what I know so far for the TL. Keep in mind none of this is official, and it is preliminary, so could change.
1) The bootloader will NOT be unlockable on any device that has an active SIMlock. e.g. any device sold on AT&T with a contract subsidy is not going to have an unlockable bootloader. This is almost 100% definite.
2) The bootloader should be unlockable for users who pay full price for the device from AT&T, e.g. anyone who can receive an immediate SIM unlock with AT&T's policies. That said, while AT&T says that any person with a full-price device should be able to immediately remove SIMlocks, often it's a major hassle, and I worry that the bootloader unlock "allowability" process will be even less integrated. Don't count on unlocking your bootloader if you purchase full-price directly from AT&T.
3) Sony may sell the device directly (again - they MAY do it, it's not guaranteed), direct-purchase devices will almost surely have an unlockable bootloader (Not guaranteed, but very likely).
Well,TX seems doesn't support for the rom made to T:crying:
niuzhd said:
Well,TX seems doesn't support for the rom made to T:crying:
Click to expand...
Click to collapse
of course not. It's a different device
Coming from laggy XS, now holding TX,
Sony is doing it right this time, TX design and ICS are so smooth, fast and bug free( at least haven't encounter any yet), TBH I don't have any intention to flash Rom or wait for update (JB).
Sent from my LT29i using xda app-developers app
Waiting for my first room tanks all
Envoyé depuis mon LT30p avec Tapatalk

[q] wtf fxp ?????

If you didnt know yesterday the FXP team announced that it would begin lollipop nightlies for 12 Xperia devices, in which our SP isnt included. While reading the list with the 12 devices i realised that devices that are WAY less powerfull like the E3 will get support, and our device which in my expierience seems to run lollipop with ease doesnt get support.
This really frustrated me, as i dont understand why would they do that. Does anyone have an explanation ???
Btw happy holidays everyone
Different phones = different problems. Some phones are more easy to make ports. And other fact is what the XSP developer community is not too big, we don't have much developers working on our phone. More popular phones have more developers, bringing ports more quickly. We have some devs working to bring Lollipop to us, already have a almost fully working build of 5.0 for LBL, which is more harder to port. Unlocked BL only maybe is coming soon. What rest for us is only wait. If someone can't wait is easy: just learn how to develop a ROM and build it for yourself.
Dammer Martins said:
Different phones = different problems. Some phones are more easy to make ports. And other fact is what the XSP developer community is not too big, we don't have much developers working on our phone. More popular phones have more developers, bringing ports more quickly. We have some devs working to bring Lollipop to us, already have a almost fully working build of 5.0 for LBL, which is more harder to port. Unlocked BL only maybe is coming soon. What rest for us is only wait. If someone can't wait is easy: just learn how to develop a ROM and build it for yourself.
Click to expand...
Click to collapse
If it works for LBL, it will definitely for UBL Just saying
bamiasHELLAS said:
If you didnt know yesterday the FXP team announced that it would begin lollipop nightlies for 12 Xperia devices, in which our SP isnt included. While reading the list with the 12 devices i realised that devices that are WAY less powerfull like the E3 will get support, and our device which in my expierience seems to run lollipop with ease doesnt get support.
This really frustrated me, as i dont understand why would they do that. Does anyone have an explanation ???
Btw happy holidays everyone
Click to expand...
Click to collapse
Newer devices first.Even XZ is not listed,so there is no way SP could make up in the list.

Community development strength

You're a power user. Can the Sony Xperia X keep up? Rate this thread to express how "healthy" the development scene is for the Sony Xperia X. A higher rating indicates available root methods, kernels, and custom ROMs.
Then, drop a comment if you have anything to add!
really bad comparing to other devices
I don't agree. We got official Paranoid omni and lineageOs, some stock custom rom with mods and some very talented dev into open Xperia device community. This phone has the lastest OS given by Google and enhanced by Sony (aosp source availaable even for 7.1.1).
We will have Android 8 and, with it the new update system... That means more custom rom possibility.
Gazatus said:
I don't agree. We got official Paranoid omni and lineageOs, some stock custom rom with mods and some very talented dev into open Xperia device community. This phone has the lastest OS given by Google and enhanced by Sony (aosp source availaable even for 7.1.1).
We will have Android 8 and, with it the new update system... That means more custom rom possibility.
Click to expand...
Click to collapse
lineageos? is there any?
coconutxyz said:
lineageos? is there any?
Click to expand...
Click to collapse
LINEAGE ?????
Where is?
No official Lineage. I hope, the official SailfishOS port will arrive soon.
And when this happens, the X will rise.
Dev community pretty bad as of right now... There's a lot of hope but still years behind dev community behind motorola/oneplus/etc
mase76 said:
No official Lineage. I hope, the official SailfishOS port will arrive soon.
And when this happens, the X will rise.
Click to expand...
Click to collapse
SailfishOS is an absolute deal breaker for me, as you will have to pay for SailfishOS for the Xperia X.
I don't see a reason why I should pay for a OS, which still lacks of features and probably will be released anyway when the xperia x is completly death.
Did you ever try SFOS? The usage is much cooler than
Android. And there will be an runtime env for Android apps.
I don't have a problem to pay for good things. But nobody
forces you to buy an Xperia X or pay for an alternative OS.
And you know, that an Android with Google services isn't
as free as you think?
Ok, it is getting offtopic.
If we'll could talk with Xiaomi Redmi Note 3 dev community, maybe we have other expectations with the development for this and Xperia X Compact device(s).
BTW, I been wanted show you that: https://forum.xda-developers.com/redmi-note-3/development/rom-aosp-oreo-t3664605
Regards.
Very bad compared to my 3 years old Asus Zenfone
This even getting Oreo
https://forum.xda-developers.com/zenfone-5/development/rom-aosp-oreo-tank0412-t3663733
Their Snapdragon 650 is a good SoC for Development, more, searching fix some errors that Sony let...
The problem is our own Dev here, is very low...
IDK why.
We'll should to port some things from Xiaomi's Phones (Xiaomi Redmi Note 3 Snapdragon and Xiaomi Mi Max), or, fuse our Dev with them Dev for making "bigger" to Snapdragon 650 SoC, at least.
SahilCrazy said:
SailfishOS is an absolute deal breaker for me, as you will have to pay for SailfishOS for the Xperia X.
I don't see a reason why I should pay for a OS, which still lacks of features and probably will be released anyway when the xperia x is completly death.
Click to expand...
Click to collapse
u know that jolla give you the option to compile sailfish x for yourself right? And you know that they need to make money because they paid sony for licenses etc. and have taxes and coworker etc.? It's not like that jolla is a one-man show in a cellar like some others here like to think or are by themself
Guys please don't say our dev community strength sucks that's just unfair and of poor taste. WHY? Because.
Sony Xperia X wasn't much of a hit phone anyway it was expensive and was reviewed as a poor excuse for a flagship phone when it was released so nobody even bothered buy one there were better options back then and this phone did not deserve any attention in fact I only bought this phone because it was so damn cheap when I bought it last year. (from a 2nd hand seller for 150$)
I won't expect lots of devs and variety on custom ROMs for this phone, but I'm happy and grateful that we still got great devs here even if there's only a few.
cyanides13 said:
Guys please don't say our dev community strength sucks that's just unfair and of poor taste. WHY? Because.
Sony Xperia X wasn't much of a hit phone anyway it was expensive and was reviewed as a poor excuse for a flagship phone when it was released so nobody even bothered buy one there were better options back then and this phone did not deserve any attention in fact I only bought this phone because it was so damn cheap when I bought it last year. (from a 2nd hand seller for 150$)
I won't expect lots of devs and variety on custom ROMs for this phone, but I'm happy and grateful that we still got great devs here even if there's only a few.
Click to expand...
Click to collapse
Now, is the "most seller" together to the Xiaomi A1.
With this, maybe we could see something for make to develop even more for this SoC.
Community development is bad, but not the worst. Unfortunately, "Bootloader unlock allowed" is "No" on my phone so I can't use anything community developed/maintained regardless.
IMO it's alright. We're still under cover of Sony's AOSP and various official projects (Omni and PA), and outside of that there are Unofficial LOS and Treble by Chippa_ahttps://forum.xda-developers.com/member.php?u=6994234 and Sjll respectively. Some of those ROMs are usable as daily driver.
Props to any and all developers who have been keeping this phone alive.

Request to RESPECTED DEV'S

Respected developers, we custom Rom users solely depend on you & your efforts whenever we are fooled by multi millionaire companies like Sony, Samsung... By stopping the updates for any device whenever they feel. Its you guys, who keeps the device and our hopes alive here @ xda.
Respected devs,I've a request to make on behalf of all the Indian users With this device.it has been a long time since a telecom company RELIANCE JIO,introduced voLTE in India. But among the z series devices, it's only this device which hasn't received fully functional voLTE feature. As a disadvantage, due to lack of voLTE,we have following genuine problems::
1.we can't use JIO SIM CARDS ( cheapest service provider in India)
2. If we want to use them, we have to use an app JIO4G VOICE,which needs to kept ON & FUNCTIONAL all the time, we can't even hibernate it..... Our battery juice is sucked up by this app.
3.We have to keep our MOBILE DATA -- always ON, inorder to receive calls.... Which again consumes battery.
Through this post,I would like to request each & every developer for this device to please give some amount of your valuable time in creating a zip or rom,,,by which we can have FULLY FUNCTIONAL voLTE in our device.
Any help will be a real blessing for us all.
Thanks alot.
Absolutely Agree, sad to see there isn't much support for this device, i don't live in India but i wish there were more Custom ROMs for this device, this phone has a Snapdragon 810 and Adreno 4xx series - which is better than most pre 2015 and some after 2015 phones, yet those phones have Oreo or Pie, but the Xperia Z3+/Z4 doesn't.
spyroz540 said:
Absolutely Agree, sad to see there isn't much support for this device, i don't live in India but i wish there were more Custom ROMs for this device, this phone has a Snapdragon 810 and Adreno 4xx series - which is better than most pre 2015 and some after 2015 phones, yet those phones have Oreo or Pie, but the Xperia Z3+/Z4 doesn't.
Click to expand...
Click to collapse
Devs are very few for this device @Quarx, @ olivier, @venkat kamesh and another one @machao.thats it. Out of them I don't think anyone is solely interested in z3+/z4. As their primary developments are for some other device. What we get, is just left over part of their hard work.
M-Rom and Lineage Os are only 2 currently maintained roms/threads for this device.M-Rom is not maintained by the developer himself at xda,as he @machao) updates his thread @ bbs.gfan only.
Without voLTE, we are really suffering in India as we are not able to use the cheapest simcard.
spyroz540 said:
Absolutely Agree, sad to see there isn't much support for this device, i don't live in India but i wish there were more Custom ROMs for this device, this phone has a Snapdragon 810 and Adreno 4xx series - which is better than most pre 2015 and some after 2015 phones, yet those phones have Oreo or Pie, but the Xperia Z3+/Z4 doesn't.
Click to expand...
Click to collapse
Devs are very few for this device @Quarx, @ olivier, @venkat kamesh and another one @machao.thats it. Out of them I don't think anyone is solely interested in z3+/z4. As their primary developments are for some other device. What we get, is just left over part of their hard work.
M-Rom and Lineage Os are only 2 currently maintained roms/threads for this device.M-Rom is not maintained by the developer himself at xda,as he @machao) updates his thread @ bbs.gfan only.
Without voLTE, we are really suffering in India as we are not able to use the cheapest simcard.
you are very much right sir,if we could have volte in our device then our device will be the perfect device for today age mobile phones.jio4g voice software take up very much battery of my phone .

About me

Hi folks!
I'm Technocat (or Techno for short) and I've been hanging around the XDA forums since 2016.
I honestly find it pretty crazy that I've been here for over 4 years and this is only my 4th post (I think I used to have more, but I assume the original threads have since been deleted). I'm sure I would probably have been a senior member by now had I been signed in every time I've stopped by, but I'm sure none of you really care about that. I'm eternally grateful to the awesome devs on XDA who spend their time creating tools and custom ROMs for interested people like me, but I am moreso grateful to everyone who contributes to this amazing community we have! (Huge shoutout to @raschad and @Sjll. I've daily driven custom ROMs of yours on my Xperia Z2 and Xperia XZ respectively. You guys rock!)
On a slightly unrelated note, I own a lot of phones. Ssince XDA is primarily focused on Android devices, I'll try to stick to only listing those. My current daily driver is a Sony Xperia XZ running LineageOS 18.1. Prior to owning my XZ, I had been using an Xperia Z2 running AICP 14.0 which served me very well. I did use a Samsung Galaxy S4 for a few years running Android 5.0.1, but in my opinion, it wasn't a great phone. However, my XDA journey started in 2015 with my Sony Ericsson Xperia Arc S, when I tried to install LegacyXperia (CyanogenMod 11) on my phone, all while being around 11 years old and having no experience whatsoever. The installation went about as well as you'd expect it to go (which is not very well at all), and all I could do is watch in what felt like slow motion as my beloved phone refused to boot.
I think that is enough about me for now though. Thanks again to all of the people who make this community what it is. I'm looking forward to hopefully sharing the knowledge I've acquired throughout my years here wherever and whenever I can.
-Technocat
GeelongLing said:
Hi folks!
I'm Technocat (or Techno for short) and I've been hanging around the XDA forums since 2016.
I honestly find it pretty crazy that I've been here for over 4 years and this is only my 4th post (I think I used to have more, but I assume the original threads have since been deleted). I'm sure I would probably have been a senior member by now had I been signed in every time I've stopped by, but I'm sure none of you really care about that. I'm eternally grateful to the awesome devs on XDA who spend their time creating tools and custom ROMs for interested people like me, but I am moreso grateful to everyone who contributes to this amazing community we have! (Huge shoutout to @raschad and @Sjll. I've daily driven custom ROMs of yours on my Xperia Z2 and Xperia XZ respectively. You guys rock!)
On a slightly unrelated note, I own a lot of phones. Ssince XDA is primarily focused on Android devices, I'll try to stick to only listing those. My current daily driver is a Sony Xperia XZ running LineageOS 18.1. Prior to owning my XZ, I had been using an Xperia Z2 running AICP 14.0 which served me very well. I did use a Samsung Galaxy S4 for a few years running Android 5.0.1, but in my opinion, it wasn't a great phone. However, my XDA journey started in 2015 with my Sony Ericsson Xperia Arc S, when I tried to install LegacyXperia (CyanogenMod 11) on my phone, all while being around 11 years old and having no experience whatsoever. The installation went about as well as you'd expect it to go (which is not very well at all), and all I could do is watch in what felt like slow motion as my beloved phone refused to boot.
I think that is enough about me for now though. Thanks again to all of the people who make this community what it is. I'm looking forward to hopefully sharing the knowledge I've acquired throughout my years here wherever and whenever I can.
-Technocat
Click to expand...
Click to collapse
Welcome to XDA, again!

Categories

Resources