Related
Since there are a lot of questions that get asked repeatedly, I'm going to start up a FAQ thread.
Q: Why doesn't multiwindow work?
A: Multiwindow is still a work in progress. It's 90% working but that last 10% (such as the fact that it breaks Google+ layout) is proving to be much more difficult to polish than expected, and everyone who was working on it has been very busy keeping on top of community contributions and core project work. Progress can be followed at https://gerrit.omnirom.org/#/c/1510/ - Please do not comment there unless you are able to build Omni with the patch yourself have a specific suggestion on how to improve the code. (No UI/UX suggestions please, only code - finishing the code is difficult enough as it is.)
Q: Is my device officially supported?
A: Check http://dl.omnirom.org/ - The device support page sometimes is out of date, while the downloads page is ALWAYS current.
Q: Is my device unofficially supported?
A: Check your device's own communities, don't ask in the general omni communities. Sadly, many unofficial maintainers don't communicate with the team at all, or do so very poorly. If your device becomes supported, support is going to come from a maintainer in your device's development community, not from the core Omni project unless you're lucky and have a device that one of the team is interested in for their own personal reasons.
Q: Where do I report bugs?
A: The official bug reporting system is at http://jira.omnirom.org/ - This is only for devices in the list on dl.omnirom.org
Q: Will you support my device?
A: Just like with other projects, for a device to be supported requires that it have a maintainer. We're already short on maintainers and spread a bit thin, so your best bet is to go to your device's own forums here on XDA. Any device support requests posted in the general Omni forums will be reported to the moderators for moving to device-specific forums.
Q: Why don't I have root?
A: We were planning on integrating an opensource version of SuperSU but Chainfire hasn't had the time to finish that up. The rest of us have been pretty busy too. The recommended approach is to install SuperSU from recovery (If you were able to flash Omni, you have a custom recovery capable of flashing SuperSU) and then choose the "Install backup script" option in SuperSU's settings. (The ease of flashing SuperSU is why most of us haven't put too much effort into getting this cleaned up.)
In addition to this, apps which block usage on rooted devices are proliferating, and many corporate policies forbid using a device that is rooted on their network. It's easier for users who need root to flash SuperSU or another solution in recovery than it is to try and remove root. (I realize that as of July 2014, Omni is partially rooted - 'adb root' and 'adb remount' work, we'll be looking into removing this for nightlies eventually in order to allow more users to run Omni when connected to a corporate network.)
Q: What happened to nightlies for jflteatt/jfltexx/other jflte carrier-specific variants?
A: They were replaced by a unified jflte build. jflte supports all individual variants that previously received their own builds. You must manually transition to the new builds by downloading from http://dl.omnirom.org/ before resuming usage of OpenDelta
Q: When will *foo* happen?
A: We do not give ETAs. This is because usually, if we knew exactly what was needed to finish something, we'd likely have already finished it.
Q: Why am I not getting updates for my device with OpenDelta?
A: There are a few possible causes for this. One could be that your device's name changed or it was unified into another device build. (Carrier variants of t0lte and jflte are in this category. Carrier-specific builds such as jflteatt and jfltexx stopped when the unified jflte build started) Another could be that the OpenDelta "update chain" was broken - it happens sometimes. For example anyone stuck on a February 17 build of t0lte or n7100 needs to manually update from dl.omnirom.org
http://dl.omnirom.org/ is always the definitive place to find the latest official build for a device
Q: What are the official IRC channels for Omni?
Development - #omni
Users - #omnirom
Q: I sat in an IRC channel for 30 minutes and got no response, why doesn't anyone talk to me?
A: Many of us are hardcore idlers that never log out even when we leave the house for more than a day. If you ask a question and log out before we return to the keyboard, you won't get an answer. I strongly suggest you learn the Art of the Idler like most of us have. It could take a few hours for someone who knows the answer to your question to see it and respond.
Q: I PMed a developer on IRC and got no response, why?
A: See above about us being hardcore idlers. In addition many of us might not see a PM because it's buried way down on our channel list.
In general, unless it ABSOLUTELY has to be private for some reason, you should not be PMing any developer. For one, the Omni team believes in transparency - we want to keep as much discussion in the open as we can. For another, often someone other than the person you PMed could help you.
Also, in general, when pinging people or asking a question, don't ask if you can ask a question - get straight to it. Most of the developers don't like "naked pings" (pings without any real information or question) - see http://blogs.gnome.org/markmc/2014/02/20/naked-pings/ for a great writeup of why.
e.g.
Code:
<someuser> ping Entropy512
is not an efficient way to communicate
but
Code:
<someuser> ping Entropy512 re: https://gerrit.omnirom.org/#/c/7373/
is MUCH better
*reserved 1*
*reserved 2*
*reserved 3*
What is an omni rom whats its specifications? Can any one suggest link or info page?
Thanks
Sent from my N9000W using Tapatalk
Entropy512 said:
Since there are a lot of questions that get asked repeatedly, I'm going to start up a FAQ thread.
Q: Why doesn't multiwindow work?
A: Multiwindow is still a work in progress. It's 90% working but that last 10% (such as the fact that it breaks Google+ layout) is proving to be much more difficult to polish than expected, and everyone who was working on it has been very busy keeping on top of community contributions and core project work. Progress can be followed at https://gerrit.omnirom.org/#/c/1510/ - Please do not comment there unless you are able to build Omni with the patch yourself have a specific suggestion on how to improve the code. (No UI/UX suggestions please, only code - finishing the code is difficult enough as it is.)
Q: Is my device officially supported?
A: Check http://dl.omnirom.org/ - The device support page sometimes is out of date, while the downloads page is ALWAYS current.
Q: Is my device unofficially supported?
A: Check your device's own communities, don't ask in the general omni communities. Sadly, many unofficial maintainers don't communicate with the team at all, or do so very poorly. If your device becomes supported, support is going to come from a maintainer in your device's development community, not from the core Omni project unless you're lucky and have a device that one of the team is interested in for their own personal reasons.
Q: Where do I report bugs?
A: The official bug reporting system is at http://jira.omnirom.org/ - This is only for devices in the list on dl.omnirom.org
Q: Will you support my device?
A: Just like with other projects, for a device to be supported requires that it have a maintainer. We're already short on maintainers and spread a bit thin, so your best bet is to go to your device's own forums here on XDA. Any device support requests posted in the general Omni forums will be reported to the moderators for moving to device-specific forums.
Q: Why don't I have root?
A: We were planning on integrating an opensource version of SuperSU but Chainfire hasn't had the time to finish that up. The rest of us have been pretty busy too. The recommended approach is to install SuperSU from recovery (If you were able to flash Omni, you have a custom recovery capable of flashing SuperSU) and then choose the "Install backup script" option in SuperSU's settings. (The ease of flashing SuperSU is why most of us haven't put too much effort into getting this cleaned up.)
In addition to this, apps which block usage on rooted devices are proliferating, and many corporate policies forbid using a device that is rooted on their network. It's easier for users who need root to flash SuperSU or another solution in recovery than it is to try and remove root. (I realize that as of July 2014, Omni is partially rooted - 'adb root' and 'adb remount' work, we'll be looking into removing this for nightlies eventually in order to allow more users to run Omni when connected to a corporate network.)
Q: What happened to nightlies for jflteatt/jfltexx/other jflte carrier-specific variants?
A: They were replaced by a unified jflte build. jflte supports all individual variants that previously received their own builds. You must manually transition to the new builds by downloading from http://dl.omnirom.org/ before resuming usage of OpenDelta
Q: When will *foo* happen?
A: We do not give ETAs. This is because usually, if we knew exactly what was needed to finish something, we'd likely have already finished it.
Q: Why am I not getting updates for my device with OpenDelta?
A: There are a few possible causes for this. One could be that your device's name changed or it was unified into another device build. (Carrier variants of t0lte and jflte are in this category. Carrier-specific builds such as jflteatt and jfltexx stopped when the unified jflte build started) Another could be that the OpenDelta "update chain" was broken - it happens sometimes. For example anyone stuck on a February 17 build of t0lte or n7100 needs to manually update from dl.omnirom.org
http://dl.ominrom.org/ is always the definitive place to find the latest official build for a device
Q: What are the official IRC channels for Omni?
Development - #omni
Users - #omnirom
Q: I sat in an IRC channel for 30 minutes and got no response, why doesn't anyone talk to me?
A: Many of us are hardcore idlers that never log out even when we leave the house for more than a day. If you ask a question and log out before we return to the keyboard, you won't get an answer. I strongly suggest you learn the Art of the Idler like most of us have. It could take a few hours for someone who knows the answer to your question to see it and respond.
Q: I PMed a developer on IRC and got no response, why?
A: See above about us being hardcore idlers. In addition many of us might not see a PM because it's buried way down on our channel list.
In general, unless it ABSOLUTELY has to be private for some reason, you should not be PMing any developer. For one, the Omni team believes in transparency - we want to keep as much discussion in the open as we can. For another, often someone other than the person you PMed could help you.
Also, in general, when pinging people or asking a question, don't ask if you can ask a question - get straight to it. Most of the developers don't like "naked pings" (pings without any real information or question) - see http://blogs.gnome.org/markmc/2014/02/20/naked-pings/ for a great writeup of why.
e.g.
Code:
<someuser> ping Entropy512
is not an efficient way to communicate
but
Code:
<someuser> ping Entropy512 re: https://gerrit.omnirom.org/#/c/7373/
is MUCH better
Click to expand...
Click to collapse
The link to to omni ROM website doesn't work
^ There's just a typo on the last (bottom) link to omni downloads page.
The others work fine : http://dl.omnirom.org/
AngryHapposai said:
^ There's just a typo on the last (bottom) link to omni downloads page.
The others work fine : http://dl.omnirom.org/
Click to expand...
Click to collapse
Good catch, thanks for specifying which specific link was broken. Should be fixed now.
Hello! This will be a quick post about how it was good earlier and how it can be better today, so please, stay with me.
I've been using Sony's for a while now, starting with small and cute Sony Ericsson k510i, then k550i, then wt19i (LWW), and then Xperia SP. My "flashing career" started after I've lost warranty on my k510. At that time there wasn't a lot you can do to your phone - there were several official firmwares, various customization options, and a lot of custom patches. No competition, one latest official firmware, a big library of patches that you could port to your device, if someone didn't do it already. The only competing area were a lot of graphical patches, but you could compile them together on your phone. Like today, if you were doing something wrong with your phone - you'll get a brick and it's your fault. But for every device there was an instruction, a beautifully crafted instruction on what to do and how to do everything, step by step. Almost every thread included a complete set of links to get you started. If you needed to flash a customisation after installing something, there would be a link on how to flash custom right there.
Today I have my XSP and try to do something to it. So I open one link (non-sticky, needed to bookmark it), see a lot of ROMs, part of which are no longer maintained. Finally open one of them based on performance rating, and see that it needs some kernel. So I go to kernel list, and see that it can't be flashed without recovery. What recovery? One specific recovery, because another one can't flash it. Now how do I flash recovery in the first place? I need a manual for that. Now I go to kernel and ROM page and see that no manual is available for them, too. So I open main device page and don't see any manual, so I open a sticky thread. And guess what? I don't see manual there. And that's when I start a new thread, type my problem in, and see a non-sticky thread with last post made 2nd of May 2015, and no pages link to that thread at all.
Is that how it goes this days? A newbie comes in, spends whole evening, opens 10 tabs, and still can't find anything relevant? I think we need to do something with this, revisit old threads, compile a new one-for-all guide, or at least a list of guides. And stick it, so people can actually see it. Otherwise there will be small closed community of those who already can develop and flash, and all the others who either got brick or is afraid to get a brick. Thanks.
---
UPD: And then I see that the kernel which I almost decided to flash is closed and all developers migrated to another one. I'm talking about tangerine and helium. Again, no info in the first post. And main developer openly says to users of his work - if it didn't work for you, don't use it. What's wrong with you people...
I'm deeply sorry if I offended somebody with my previous post. I'm happy that you guys do such amazing things with this 3 year phone. But damn, FULL INSTALLATION took about 10 minutes, counting PC reboot into linuxes to get fastboot working. In case someone struggles like me, use CyanogenMod instruction to get to Cyanogen Recovery; download TWRP Recovery, ROM of choice and GApps of choice; place all three ZIPs onto your sdcard; go to recovery, flash TWRP, reboot into TWRP (by pressing volume rockers while loading), do Wipe - Factory Wipe, flash ROM, flash GApps, reboot to normal. Wait for about 5 minutes (black screen is normal, there will be dots flying after a minute or so to keep you entertained).
Yes, It's that simple nowadays, so why bothering typing so much? I was in that situation with my SP, too, but if the are so many answers to these questions and so many threads... "You have to read" is the answer! A lot! It's for your own good, trust me. Now I can do anything I want with my phone with nohow! So a little reading and searching here and there is just positive experience for you. Don't complain, the people here ( well a part of them) are hardcore coders or themers or whatever. You can't just ask them to tell you all the stuff. If want help I'm always available.
Thank you for linking to my very dusty and lonely Flash ROM guide hahaha
No you didn't offend anyone at all. The guides are actually there, like how to use Flashtool, how to unlock bootloader, how to flash recovery and everything, it is just that they are buried deep with time as the development goes. The thread are there, in the General section and are awaiting to be searched. Though some are outdated, some are not and you can benefit from there.
Some searching will normally do, but if it didn't, just ask in the threads, someone will probably answer to you!
I always have my eyes on the General and Q&A subforums of the Xperia SP, and I will usually respond to a help-able problems. So if you have any problems, feel free to post in the Q&A subforum, and if not me, someone will help you. If there are nobody, don't feel offended. Maybe people don't know what to help or suggest (but lets just hope that is not what it will be )
About recovery, PhilZ and CWM is way outdated, and its time for everyone to make TWRP as a standard as it is a still updated recovery. Cyanogen Recovery in my opinion is crap as there are far too less feature plus, it enforce on signed flashable zips.
About the thread on Tangerine, the developer said dont use if it doesn't work is because of the norm of the Kernel. The kernel is made by using an AnyKernel template, hence render support for almost all Lollipop ROMs. Since ROMs can be updated and all ROMs have different sources, a simple change in the system part can render Tangerine unsupported, and the developer cannot do anything (definitely his choice, please respect that) to only fix the problem on one ROM which could possibly break support for the majority of the ROMs! This also appplies to Helium. Therefore, his words of "dont user it if it doesn't work" has a meaning, and it is not something to degrade new users and so.
kojata said:
If want help I'm always available.
Click to expand...
Click to collapse
TechnoSparks said:
I always have my eyes on the General and Q&A subforums of the Xperia SP, and I will usually respond to a help-able problems. So if you have any problems, feel free to post in the Q&A subforum, and if not me, someone will help you. If there are nobody, don't feel offended. Maybe people don't know what to help or suggest (but lets just hope that is not what it will be )
Click to expand...
Click to collapse
Thanks for the answers and offering help, happily I was able to install my ROM of choice and it still works flawlessly, I was even able to squeeze 20 battery days from my old XSP.
Thinking about it, I start to understand why that dev answered like that. I was a python dev in the past and know how one feature can kill two others. Just in my head there is one current linux kernel, and all things that are developed should work with that particular kernel. Kernel comes before OS, if you will. Isn't it the case with ROMs and droid kernels?
About TWRP and reading: I honestly did read a lot of info before doing something, because it's my only phone these days. But it's so hard to find information on whether something is deprecated or not. As a new user, you wouldn't just google "is this deprecated and no longer used?", because that search will not provide any info. That is why during that evening and following morning I lost count of how many times I just shaked my head asking which recovery/kernel should I use and how do I install it? Latest being the easy one, because I already found TechnoSparks thread by that time.
In case anybody is interested, I installed Candy 5 on default kernel. But I still don't know if installing android 5 on a kernel used with android 4.2 was a good idea. It went well, however.
CarbonDev said:
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained whenever possible and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Click to expand...
Click to collapse
These builds are for the Samsung Galaxy Exhibit and the Samsung Galaxy Ace 2e.
Models:
SGH-T599
SGH-T599N
SGH-T599V
Download: meticulus.co.vu
GApps here
Known issues:
Screenrecording locks up device. ( do not use )
Moving apps to SD does not work. Reports "not enough space" or something similar. FIXED! see here
OTG Host mode only works once per boot.
If GApps are not flashed there is a ramdom reboot issue due to issue with gps blog. Not an issue as long as you flash GApps.
Setting a govenor via "PerformanceControl" may not work due to "Usecase" control.
Offline Charger options via "Extras" do not work.
Root is disabled by default. Some options in "Extras" and "Performance" depend on root. Enable in "Developer Options"
Thanks for all your work.
Good to see you back at it on the T599.
Tried you latest. Seems to work quite well.
Thanks again.
Sent from my BN Nook HD using XDA Free mobile app
Moving apps to the SD card is FIXED! see here
New Build!
New Build: http://www.meticulus.co.vu/2016/07/new-build-carbon-lp-511-for-galaxy.html
Update released : http://www.meticulus.co.vu/2016/07/carbon-lp-511-for-galaxy-exhibit-ace2e.html
Several bug fixes...
Another Update Release: http://www.meticulus.co.vu/2016/08/carbon-lp-511-for-galaxy-exhibit-ace2e.html
Encryption fixed.
Hang at "Finishing Boot" fixed.
...
Progress on MM: http://www.meticulus.co.vu/2016/09/progress-on-marshmallow-for-codinalte.html
WOWWW you are back! I thought this phone was already forgotten. Let me try this on my old t599n with stock laggy tw 4.1.2 with internal memory for only 2 or 3 apps.
Can't wait for MM rom.
Great work and welcome back!!
Update: Hi @Meticulus , I am using this rom and I like it. I got just some little issues:
First: Is the Carbon sources updated? I ask this because i see in my language (portuguese) there are lot of words not translated (when i was on cm 12.1 in my s5 didnt face this issue), i see that the security patch is November 2015 (a bit old no?)
Second: I don't know why but i can't install facebook... it took like 5 minutes to install and then it fails with error -504 on playstore
BTW great work man, I really wanna try your CM 13 on this machine
Keep it up
If anyone is reading this, I've noticed http://www.meticulus.co.vu is down (probably for years). Is there any way to obtain the 5.11 Carbon ROM ? I have two old T599N devices that I want to "resurrect/upgrade". I've googled a lot but could not find any download links for the 5.1.1 Carbon ROM created by Meticulus for this device. I also tried searching for this in DC hubs but without success. Thank you!
Checklist of Things to Do w/ Axon 7
1. Unlock Bootloader - DONE
2. Flash TWRP - DONE
3. Get Root Access, along with Root apps - DONE
4. Flash Cyanogenmod 13.1 - PENDING
Who is interested in seeing Cyanogenmod 13.1 running on the ZTE Axon 7 as much as I am? If so, please post on this thread. Hopefully, the right people will check this out and get the ball rolling on this project.
Why don't you build it ? ?
We are never happy ... let the devs work ... on the other hand they have a life and bills to pay !
Sent from my SAMSUNG-SM-N900A using XDA-Developers mobile app
like tupirujp says.
If you want your question answered just contact Cyanogen directly.
***Thread Cleaned*** (removed negative, counterproductive comments/quotes, for a fresh start)
Some concerned users brought this thread to the attention of Moderation staff.
A good practice is to have the dev needing the device (Unjustified Dev) set up their own donation link, express their desire to dev for the device, and put out a little description of the work they intend to do for that device (ie; unlock bootloader, Roms , Kernels, etc)...
Otherwise, third party donation links usually only raise suspicion, mistrust, and rarely accomplish the goal of helping the dev get a device.
I applaud those who want to support developers (they certainly deserve the support), let's make sure we do it in a way that isn't counterproductive to the goal or the donation process.
Thanks for your cooperation.
Well, in order to build a rom you need:
Device Tree
Kernel
Vendor/Proprietary files
We have versions of the first two already loaded on GitHub. It's a (hard) matter of someone figuring out what proprietary files we need and then going through the iterative testing to ensure all the hardware components are working. So, let the devs have time with the phone to see what they can figure out and we'll start seeing development.
Please Cyanogenmod come to this device..
Introducing Motorola Moto G22 (hawaiip) developer community, this is an initiative to bring testers under the same roof for the betterment of development for Hawaiip
I advise people with the device to come forth as testers, please take note that it is only with your support that development with flourish. Regardless of the number of developers, there's no point when there's no one to test.
Requirements to be added as a tester:
1. Must have the device with an unlocked bootloader.
2. Must be knowledgeable and experienced enough with custom ROMs flashing.
3. A reliable internet connection is recommended.
4. Access to a pc would be beneficial for obtaining logs, but isn't necessary.
5. Should be active. You will be removed if inactive for longer periods.
6. Should be loyal to the team. If found to be leaking builds or even mere screenshots, you will be removed.
{Mod edit} If you meet all the necessary requirements and are interested to volunteer as a tester. Answer this post
@kaike_ I've moved your thread out of
Miscellaneous Android Development
For ROMs, kernels, tools and scripts only (devices that do not have a forum on XDA)
forum.xda-developers.com
Please note the subtitle of that forum but also
[ATTN] : Read before posting - Any questions posted here will be MOVED or CLOSED
Please read the below before posting. Any questions not development related will be moved or closed. Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread) Forum Rules Forum Search Google Forum...
forum.xda-developers.com
It has been moved to
Android Software Development
Discussion about Android-specific software development
forum.xda-developers.com
Additionally, I've removed the link to Telegram! Regarding social media links please observe that as an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads and if thorough support is provided in the thread. These conditions obviously don't apply to this thread as it doesn't qualify as a development thread. Additional information is also available here:
Telegram Chat Channels - Way Forward
WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...
forum.xda-developers.com
Please refrain for sharing of social media references unless within your own development threads!
And as a friendly warning: Never ever edit something that a moderator has added or edited without prior approval of a moderator.
Thanks for your future cooperation.
Regards
Oswald Boelcke
Senior Moderator
Ok, sorry, I'm not common using XDA posts
im volunteer as a tester for the further devlopement for the moto g22 i have experience 1 year in flashing these custom rom and stuff and also a random guy named MACKEN has booted gsi on hawaiip
kaike_ said:
Introducing Motorola Moto G22 (hawaiip) developer community, this is an initiative to bring testers under the same roof for the betterment of development for Hawaiip
I advise people with the device to come forth as testers, please take note that it is only with your support that development with flourish. Regardless of the number of developers, there's no point when there's no one to test.
Requirements to be added as a tester:
1. Must have the device with an unlocked bootloader.
2. Must be knowledgeable and experienced enough with custom ROMs flashing.
3. A reliable internet connection is recommended.
4. Access to a pc would be beneficial for obtaining logs, but isn't necessary.
5. Should be active. You will be removed if inactive for longer periods.
6. Should be loyal to the team. If found to be leaking builds or even mere screenshots, you will be removed.
{Mod edit} If you meet all the necessary requirements and are interested to volunteer as a tester. Answer this post
Click to expand...
Click to collapse
Hi , i would like to be a tester , i dont have much knowledge in flashing (but i have some basic knowledge and i alr flashed roms on other devices) other than that , i have everything required , where should i contact you? Over discord or in this thread?
Hi. I would like to be a tester. I have many years of basic custom-rom flashing experience on three mobile phones. Can follow any instructions for debugging/taking debug-logs.
Why they don't add our device into the devices list? There's the G20 but not out G22
i would like to be a tester , I have many years flashing roms whit moto g22 have 1 year and ready for give help if it possible
I would love to. I've got a spare hawaiip i'm not using at the moment, and feel quite comfortable with the task as I used to cook my own roms.
kaike_ said:
Introducing Motorola Moto G22 (hawaiip) developer community, this is an initiative to bring testers under the same roof for the betterment of development for Hawaiip
I advise people with the device to come forth as testers, please take note that it is only with your support that development with flourish. Regardless of the number of developers, there's no point when there's no one to test.
Requirements to be added as a tester:
1. Must have the device with an unlocked bootloader.
2. Must be knowledgeable and experienced enough with custom ROMs flashing.
3. A reliable internet connection is recommended.
4. Access to a pc would be beneficial for obtaining logs, but isn't necessary.
5. Should be active. You will be removed if inactive for longer periods.
6. Should be loyal to the team. If found to be leaking builds or even mere screenshots, you will be removed.
{Mod edit} If you meet all the necessary requirements and are interested to volunteer as a tester. Answer this post
Click to expand...
Click to collapse
just one thing,will there be custom things? (custom roms and recoveries) cause thats what im searching for the G22.
Similarly here, i have flashing experience all the way back to the htc dream and have dome it man times before.
I would like to see a version of LoS for our device, preferably based on android 13 or newer depending on when it is made.