[Roll up] Important threads for: T-Mobile HTC One (M8) - T-Mobile HTC One (M8)

GREETINGS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SOME GUIDES REGARDING S-OFF AND FLASHING WILL BE ALLOWED IN DEVELOPMENT BUT MOST WILL BE LINKED TO THIS THREAD.
"COLLECTIONS", "REFERENCES" "LIBRARIES/INDEXES" and HOW TOS BELONG IN GENERAL SECTION.​
Try to keep the development forum CLEAN! No offtopic posting and no questions.
Use the report button in an offending post to let us mods know we need to take action. Dont take matters into your own hands!!!
Sources need to be posted for all kernels!!!
You need to use TAGS like [ROM] or [KERNEL] and so on as used in all dev forums throughout XDA
Any disputes between developers should be handled by pm. No public posting in a dev thread regarding these matters
Rom issues should be discussed within their respective threads, or in a corrisponding Q&A thread
Thread titles should ALWAYS coincide with ROMS ALREADY AVAILABLE FOR DOWNLOAD!!! No advance notification of incoming ROM through thread title. A changelog for the yet unreleased Rom can be included in the OP or in another post CLEARLY MARKED as EXPECTED CHANGELOG
Posting in the development section means automatic ACCEPTANCE of the above Rules
Forum specifics:
Attention all Android Developers - GPL
Forum Rules
Forum Search
Preset Google search for XDA Developers.
FAQ:
Not yet created
Indexes:
[COLLECTION][FIRMWARE][RUU][BACKUPS] T-Mobile US - Release Builds
[OTA/RECOVERY/RUUS/FIRMWARE/DUMPS] T-Mobile HTC M8 - AndroidFileHost
Guides/How to:
[GUIDE] [T-Mobile] Unlock Bootloader, Install Custom Recovery, Root, S-Off
[how to] remove your "tampered" banner
[how to] change your MID without an eng bootloader
[how to] lock/unlock your bootloader without htcdev(s-off required)
[MOD] Hboot 3.16.0.000 without red text on custom kernels.
Tools:
Set up Android SDK (ADB) for Windows 8 / 8.1 / [ADB][Bootloader][Fastboot]
[TOOL] HTC One 2014 (M8) All-In-One Toolkit V1.0.1 [4-8-2014] [PERM ROOT]
Attention developers or those just starting out
How do I determine if my work belongs in Original Development?​
These are the determining factors:
~The following are most likely “Original Development”:
Official releases of highly original and upstream custom ROMs (built from the ground up with significant original development within them
Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.
A significant “first” in development for a device. Significant is subjective, but it is likely something which took considerable time/effort, and is generally accepted by developers to be significant and non-trivial.
Kernels which are built with beneficial changes that are not simply pulled from other kernels already available. Some element of original work is expected.
Tools and utilities with a clear purpose, and which are well-made, and useful to users. They should have an element of originality, either in purpose or through significant improvement in the means of operation.
Significant port of a ROM from one device to another, giving enhanced features or functionality to users of the target device. The port should be beneficial (a port from two virtually identical devices isn’t original development, it’s winzipping, and nobody really benefits from this, as it’s not development)
~The following are most likely not “Original Development”, and should be posted in the “Android Development” sub forum:
Your own “unofficial” stock build of your favourite original, source-built (or otherwise) ROM, particularly where an official or maintainer-endorsed thread exists already.
Minor derivatives of other ROMs with little or no changes, or ROMs consisting of “placebo” features as a main constituent or claim.
Renames or rebadges of others’ work – these don’t belong on XDA at all! Refer to rule 12 for more information.
Reposts of existing ROMs with small changes (i.e. kitchen work, such as adding a couple of apps). If you could realistically distribute your changes as an “addon pack” above and beyond a ROM, you should do so. In addition, your “ROM” would not be original development as it would be substantially identical to the original ROM.
A thread created with unrealistic goals that are clearly unachievable by those starting the thread. This is not intended to discourage high aspirations, rather to prevent threads porting Windows Phone 8 to the HTC Wallaby. This is pretty much common sense.
A ROM where a main or significant claim/feature is graphical changes to the user interface (ie. Themed ROM)
Forum section rules:
To help keep this forum section tidy and easy to use, here are some rules and guidelines.
Only the following topics are allowed in the DEVELOPMENT area:
[DEV] - Development for any projects or Apps.
[ROM] - Custom ROMs.
[KERNEL] - Custom Kernels.
[MOD] - Hack & Modifications for the phone. (See below for more details)
[FIX] - Fixes for known issues & bugs.
[R&D] - Research & Development for Devs only, when gathering data for a new projects.
Please keep all non Development relevant chatter out of development threads, It is recommended to make a separate thread in the Q&A section for non Development related comments and questions, valid replies within a development thread are: BUG Reports, Problem, Troubleshooting Steps & Logs.
Note: If you are unsure where your new topic should go, then please post it in General.
For more information on the Original Android Development section check out this portal post
All kinds of Best Rom/Kernel/etc threads are unwelcome and they will be closed. Read, research and make your own mind up, as the question is very subjective.
Please Include Screen Shots for ROM / MOD / THEME / Apps & Games, when possible as it's expected by our members.
[MOD]'s that are primarily theming related or simply adjust stock application or framework functionality or behavior belong in the themes and apps section rather than the development section.
Unmodified Stock ROM and Source Codes does not count as a DEVELOPMENT project unless it's part of an active project you have already started, and so should be posted in the general section.
Placeholder threads posted in the development section will be removed or moved.
Howto's and Guides should be posted in the general section.
Password must be provided for all password protected files.
Direct download links preferred, due to stipulations stated in forum rule #11
11. Don’t post with the intention of selling something.
[*] Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and offer support, but not to post with the intention of selling. This includes promoting sites similar/substantially similar to XDA-Developers.com.
[*] Do not post press releases, announcements, links to trial software, or commercial services. unless you’re posting an exclusive release for XDA-Developers.com.
[*] Encouraging members to participate in forum activities on other phone related sites is prohibited.
[*] Off-site downloads are permitted if the site is non-commercial and does not require registration.
[*] Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if the following conditions are met:
A) the site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership who actively maintains XDA-Developers' support thread(s) / posts, related to the download,
B) the site is a relatively small personal website without commercial advertising/links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)
Click to expand...
Click to collapse
Extra emphasis on rule #12
12. Using the work of others.
If you are developing something that is based on the work of another Member, you MUST first seek their permission, and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails then you may contact a moderator with clear evidence that the work was created by you.
Convincing evidence will result in copied work being removed. If there is no clear evidence you created the work then in the spirit of sharing all work will remain posted on the forums.
These rules apply to all software posted on XDA unless that software comes with a license that waives these rules.
Click to expand...
Click to collapse
... and Please! keep all your personal bickering via PMs, do not pollute the forum with your personal indifferences.
If you have a problem with a specific member please contact the Moderators for help, that's what we're here for, but we are not babysitters, we are here to gather, organize and provide useful information for our over priced phones
...for additional details please read the full Forum & Marketplace Rules
Thank you for your cooperation.
[SIZE=+1]If there are new threads needing to be added from either the Q&A or General sections, please contact one of the Moderators. Your Moderators can be found at the top of each sub category. General, Q&A, Help & Troubleshooting, Android Development etc...
~Thank you~[/SIZE]​

I would suggest something, separate the roms with sense from the roms without sense, it's a mess search for roms with sense in the One S section.

rgvelez said:
I would suggest something, separate the roms with sense from the roms without sense, it's a mess search for roms with sense in the One S section.
Click to expand...
Click to collapse
This is not for ROMs or kernels. Threads consolidating these things will be found in the General section, when sombody decides to create it :good:

In the OP it says that info about S-OFF will be added to this guide (via a link I assume). If there's a way to still do that I'd be grateful. I've been combing the forums and interwebs trying to get a good handle on whether I need S-OFF to update my firmware. I'm also coming to the conclusion that the only way to get S-OFF is to purchase Sunshine for $25....I'd love to know if any of that is accurate or not.

zerozed99 said:
In the OP it says that info about S-OFF will be added to this guide (via a link I assume). If there's a way to still do that I'd be grateful. I've been combing the forums and interwebs trying to get a good handle on whether I need S-OFF to update my firmware. I'm also coming to the conclusion that the only way to get S-OFF is to purchase Sunshine for $25....I'd love to know if any of that is accurate or not.
Click to expand...
Click to collapse
There is no tmobile 4.4.3 firmware as of yet. So in order to update drivers for 4.4.3 you need to s-off. If firewater does not work for you, then sunshine is your only option.

Related

[ROM] AUG 05 2010 - Cronos Droid Version 2.1.3 Fully Stable

MOD EDIT
Here at XDA, we try very hard to work with everyone to resolve issues before they result in actions such as banning or locking threads. Unfortunately, hard as we try, we are not always able to meet those goals via ways that would be more desirable and seemingly more peaceful.
Here recently we have been having some issues with some Android devs who work with the Android Kernel. While we were able to work out the issues with quite a few devs we were sadly unable to reach such a peaceful settlement with the Android ROM dev Feeyo.
Before we go any farther into the underlying problems that we have had getting these issues resolved with this particular Android Dev, lets go over real quick what the main concern is about.
The Android kernel which is present in EVERY single ROM is an ever-growing community project. Android devs from all around the world have put their hard work into an open source project simply in an attempt to make the Android project better as a whole. While I am sure that all of these Android devs made these contributions to the kernels as a result of things that they wanted or needed to see develop within Android, they made their work available to ALL of us so that we could ALL benefit from their talents.
That being said, the Linux kernel is released under what is called the GNU GPL. (General Public License)
Basically this license allows for the Android kernel to be freely used and modified under the condition that the source of the kernel be released to the public. This "release" can be handled two ways, by either providing a direct link to the source where it can be downloaded, modified and reused under the GNU GPL, or by a written statement that offers the to provide the kernel source to anyone whom requests it. While I realize that I have only outlined a small portion of the GNU GPL, the bottom line here is that the COMPLETE and WORKING kernel source that was MODIFIED by anyone MUST be provided to the community, for any version of publicly released software.
You can find the full text of the GNU GPL licence here:
Herein, lies our problem. We here at XDA have had MULTIPLE interactions with the Android ROM dev, Feeyo, in regards to the specific problem that he has not followed these GNU GPL guidelines. There have been multiple instances where users have requested his Kernel source and he has continually refused to provide this source, or he has provided us with non working and otherwise incomplete source, or invalid or unmodified source.
The first thing we need to show is that Feeyo was MODIFYING the Android kernel source. Below is a screenshot that proves just that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Above, you can see the Kernel version says "2.6.29-opt-40-Cronos [email protected]#1", The only known way to put you name there, in the kernel, is to modify and compile the kernel yourself. You have to edit a file within the kernel source called .config.
We also have proof by Feeyo’s own release notes in his ROMs that he has modified the kernel source code as well. For example, the changelog for his kernel below shows the changes made between versions.
Here is another screenshot where he talks of changes he made to his kernel:
All of that being said, Feeyo has definitely made various improvements to the Android Kernel source by modifying that source and he has publicly released this kernel to the community.
In an attempt to resolve this matter we made various outreaches to Feeyo, including a moderator by the name of 12aon making several attempts to get this resolved... I’ve added some screenshots of the dialog that they exchanged...
Here we can see that we were trying to resolve the issue with Feeyo and he stated that he would no longer provide or distribute the 2.6.32 Kernel that he was working on because he didn’t intend on releasing code with he labeled as “messy”.
Feeyo did indeed stop providing that 2.6.32 kernel as far as we know, however he then continued to modify the 2.6.29 kernel source and distribute that in his ROMs again without following the GNU GPL guidelines.The sources for this 2.6.32 kernel were never released.
It is the decision of the XDA moderators that since Feeyo has no rights to use or distribute the Linux kernel without making available his valid source code and modifications, his ROMs and associated kernel releases will be treated as warez under forum rule 6
Here in this screenshot we are again trying to get him to post the sources to his Kernel after he released a ROM that mention various enhancements or modifications to the Android Kernel that he was providing in his ROM. Feeyo then sent us another PM as shown below:
In this PM Feeyo is stating that he did provide his sources... However, it was not complete and was missing many things that were needed to compile the Android Kernel in such a fashion that it would run on the Hero. Additionally, as these sources are not kept up to date, they do not meet the requirements of the GPL to release sources as used to compile the distributed binary kernel.Below is the link to the thread that he posted containing his supposed kernel source:
Supposed Sources used in Cronos Droid early releases
That thread was locked to preserve proof to the fact that the source he provided was not complete. In fact, on post #11 within that thread he even confirms that the source is not complete, again this is not following the GNU GPL guidelines.
Additionally, the screenshots below show occasions where Feeyo acknowledged he would not provide complete sources, by deliberately withholding the entire kernel source or constituent parts.
We have made this long explanation of recent events available to you, the community, for two reasons.
First of all, we realize that Feeyo is a talented dev and that his ROMs are well liked within the community. With this in mind, we wanted it to be known that the decisions that we have made here today are not decisions that have been taken lightly or irrationally made. This decision included opinions from AT LEAST 5 other Senior mods here at XDA. We feel that a full explanation of our actions is something that we owe the community and we truly regret that it has come down to this.
Secondly, this will be a marking point, I don’t want to say that this is an example because it was never intended to be an example. However the fact remains that this incident has caused quite a stir within XDA and from this point on we will be making sure whenever possible that any Android dev that modifies and publicly releases the Android kernel is following the GNU GPL guidelines.
The GNU GPL guidelines are important because they ensure that credit is given where credit is due and it also ensures that continued improvement, advancement, and development of such products under the GNU GPL continue to ensue. As part of the Android community, which is an OPEN SOURCE community, we owe it to ourselves and the ENTIRE community to make sure that we are staying true to the notion of an open source platform. Keeping your sources to yourself while working on a project that is open source and released under the GNU GPL is not staying true to what being open source is all about.
At this point in time, Feeyo has received a 30 day temporary ban for refusing to help us resolve this matter in a peaceful manner and for ultimately violating Rule #6 and Rule #9 which state:
6. Do not post warez.
If a piece of software requires you to pay to use it, either pay or find your cracks and serials somewhere else. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained.
9. Don't get us in trouble.
Don't post copyrighted materials or do other things that will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably don't want to do it here either. This does not mean we agree with everything the software piracy lobby try to impose on us, it simply means you cannot break any laws here, since we'll end up dealing with legal hassle caused by you. Please use common sense: respect the forum, its users, and those that write great code.
Click to expand...
Click to collapse
Furthermore, at this time, all ROMs posted by Feeyo that do not follow the GNU GPL where applicable will be locked and the links to the ROMs removed.
During this time that Feeyo is away, we sincerely hope that he will come around and upon his return, which we thoroughly hope for, he will post the sources to his Android kernel changes in the spirit of the open source community and the GNU GPL and participate in a more supporting manner.
Best Regards,
The XDA Moderator team
Thank you for sharing. Are you gonna post screenshots, this makes it more interesting to download.
thanks finish downloading now and will report back when flashing
Sure downloading app now.
forget the screenshots, how did you get the kernel? is it/can it be overclocked? Can it be used with other ROMs (CM5.0.7 etc.)
it sounds very interesting let me test it and tell u .
downloading now, hope it is true what you're saying...
What about the kernel?
cyberkid2002 said:
forget the screenshots, how did you get the kernel? is it/can it be overclocked? Can it be used with other ROMs (CM5.0.7 etc.)
Click to expand...
Click to collapse
I have not added any overclock options into the kernel. I think its fast enough the way it is. But try it out and let me know. Maybe I will add some patches so that you can overclock it
How did you get the 2.6.29 hero kernel sources?
this sounds great! ima try it now, is this kernel the kernel everyone's been waiting for?
I can't get it working, did a full wipe and keeps hanging on HERO logo.
Downloading and feed back
Flashing within 2 min
Get some sleep, or try it out? Guess?
started up, runs fine so long
RaduG said:
How did you get the 2.6.29 hero kernel sources?
Click to expand...
Click to collapse
From my understanding, all the OP did was take the Eris .29 kernel source & ported anything needed for the GSM Hero to run.
Is this a sense rom?
Downloading now,, hope this is the one I have been searching for....
reidefors82 said:
Flashing within 2 min
Get some sleep, or try it out? Guess?
Click to expand...
Click to collapse
Getting some sleep
Added screenshots.
Is the green/bad autofocus camera bug fixed?

[ROM] AUG 10 2010 - Cronos 2.2 (Froyo) 0.2

MOD EDIT
Here at XDA, we try very hard to work with everyone to resolve issues before they result in actions such as banning or locking threads. Unfortunately, hard as we try, we are not always able to meet those goals via ways that would be more desirable and seemingly more peaceful.
Here recently we have been having some issues with some Android devs who work with the Android Kernel. While we were able to work out the issues with quite a few devs we were sadly unable to reach such a peaceful settlement with the Android ROM dev Feeyo.
Before we go any farther into the underlying problems that we have had getting these issues resolved with this particular Android Dev, lets go over real quick what the main concern is about.
The Android kernel which is present in EVERY single ROM is an ever-growing community project. Android devs from all around the world have put their hard work into an open source project simply in an attempt to make the Android project better as a whole. While I am sure that all of these Android devs made these contributions to the kernels as a result of things that they wanted or needed to see develop within Android, they made their work available to ALL of us so that we could ALL benefit from their talents.
That being said, the Linux kernel is released under what is called the GNU GPL. (General Public License)
Basically this license allows for the Android kernel to be freely used and modified under the condition that the source of the kernel be released to the public. This "release" can be handled two ways, by either providing a direct link to the source where it can be downloaded, modified and reused under the GNU GPL, or by a written statement that offers the to provide the kernel source to anyone whom requests it. While I realize that I have only outlined a small portion of the GNU GPL, the bottom line here is that the COMPLETE and WORKING kernel source that was MODIFIED by anyone MUST be provided to the community, for any version of publicly released software.
You can find the full text of the GNU GPL licence here:
Herein, lies our problem. We here at XDA have had MULTIPLE interactions with the Android ROM dev, Feeyo, in regards to the specific problem that he has not followed these GNU GPL guidelines. There have been multiple instances where users have requested his Kernel source and he has continually refused to provide this source, or he has provided us with non working and otherwise incomplete source, or invalid or unmodified source.
The first thing we need to show is that Feeyo was MODIFYING the Android kernel source. Below is a screenshot that proves just that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Above, you can see the Kernel version says "2.6.29-opt-40-Cronos [email protected]#1", The only known way to put you name there, in the kernel, is to modify and compile the kernel yourself. You have to edit a file within the kernel source called .config.
We also have proof by Feeyo’s own release notes in his ROMs that he has modified the kernel source code as well. For example, the changelog for his kernel below shows the changes made between versions.
Here is another screenshot where he talks of changes he made to his kernel:
All of that being said, Feeyo has definitely made various improvements to the Android Kernel source by modifying that source and he has publicly released this kernel to the community.
In an attempt to resolve this matter we made various outreaches to Feeyo, including a moderator by the name of 12aon making several attempts to get this resolved... I’ve added some screenshots of the dialog that they exchanged...
Here we can see that we were trying to resolve the issue with Feeyo and he stated that he would no longer provide or distribute the 2.6.32 Kernel that he was working on because he didn’t intend on releasing code with he labeled as “messy”.
Feeyo did indeed stop providing that 2.6.32 kernel as far as we know, however he then continued to modify the 2.6.29 kernel source and distribute that in his ROMs again without following the GNU GPL guidelines.The sources for this 2.6.32 kernel were never released.
It is the decision of the XDA moderators that since Feeyo has no rights to use or distribute the Linux kernel without making available his valid source code and modifications, his ROMs and associated kernel releases will be treated as warez under forum rule 6
Here in this screenshot we are again trying to get him to post the sources to his Kernel after he released a ROM that mention various enhancements or modifications to the Android Kernel that he was providing in his ROM. Feeyo then sent us another PM as shown below:
In this PM Feeyo is stating that he did provide his sources... However, it was not complete and was missing many things that were needed to compile the Android Kernel in such a fashion that it would run on the Hero. Additionally, as these sources are not kept up to date, they do not meet the requirements of the GPL to release sources as used to compile the distributed binary kernel.Below is the link to the thread that he posted containing his supposed kernel source:
Supposed Sources used in Cronos Droid early releases
That thread was locked to preserve proof to the fact that the source he provided was not complete. In fact, on post #11 within that thread he even confirms that the source is not complete, again this is not following the GNU GPL guidelines.
Additionally, the screenshots below show occasions where Feeyo acknowledged he would not provide complete sources, by deliberately withholding the entire kernel source or constituent parts.
We have made this long explanation of recent events available to you, the community, for two reasons.
First of all, we realize that Feeyo is a talented dev and that his ROMs are well liked within the community. With this in mind, we wanted it to be known that the decisions that we have made here today are not decisions that have been taken lightly or irrationally made. This decision included opinions from AT LEAST 5 other Senior mods here at XDA. We feel that a full explanation of our actions is something that we owe the community and we truly regret that it has come down to this.
Secondly, this will be a marking point, I don’t want to say that this is an example because it was never intended to be an example. However the fact remains that this incident has caused quite a stir within XDA and from this point on we will be making sure whenever possible that any Android dev that modifies and publicly releases the Android kernel is following the GNU GPL guidelines.
The GNU GPL guidelines are important because they ensure that credit is given where credit is due and it also ensures that continued improvement, advancement, and development of such products under the GNU GPL continue to ensue. As part of the Android community, which is an OPEN SOURCE community, we owe it to ourselves and the ENTIRE community to make sure that we are staying true to the notion of an open source platform. Keeping your sources to yourself while working on a project that is open source and released under the GNU GPL is not staying true to what being open source is all about.
At this point in time, Feeyo has received a 30 day temporary ban for refusing to help us resolve this matter in a peaceful manner and for ultimately violating Rule #6 and Rule #9 which state:
6. Do not post warez.
If a piece of software requires you to pay to use it, either pay or find your cracks and serials somewhere else. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained.
9. Don't get us in trouble.
Don't post copyrighted materials or do other things that will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably don't want to do it here either. This does not mean we agree with everything the software piracy lobby try to impose on us, it simply means you cannot break any laws here, since we'll end up dealing with legal hassle caused by you. Please use common sense: respect the forum, its users, and those that write great code.
Click to expand...
Click to collapse
Furthermore, at this time, all ROMs posted by Feeyo that do not follow the GNU GPL where applicable will be locked and the links to the ROMs removed.
During this time that Feeyo is away, we sincerely hope that he will come around and upon his return, which we thoroughly hope for, he will post the sources to his Android kernel changes in the spirit of the open source community and the GNU GPL and participate in a more supporting manner.
Best Regards,
The XDA Moderator team
finally i download now...fastttttttt..
no greek support?
thank you sooooo much! i've been waiting for this for a loooong time... finally i have it...thanks again...
oh you made it!
Going to flash now and see if it is an improvement to the fusion!rom
Going to try it now
How about the google applications? did you include them?
Going to give it a go now. Will post impressions.
cokbok said:
How about the google applications? did you include them?
Click to expand...
Click to collapse
Yes they are included.
pornogeroc said:
finally i download now...fastttttttt..
no greek support?
Click to expand...
Click to collapse
Sorry. Language list is not complete. Greek is supported.
Does anyone else have a notification about a blank SD card due to unsupported file system?
Brooks316 said:
Does anyone else have a notification about a blank SD card due to unsupported file system?
Click to expand...
Click to collapse
EXT partitions are not supported. Froyo will see it as an unsupported Filesystem and wants to Format it. Backup your data first and then let Froyo do the formatting please.
this is a very good begin, but i wanna know, how i can enable jit, thanks for your work guy
Sow said:
this is a very good begin, but i wanna know, how i can enable jit, thanks for your work guy
Click to expand...
Click to collapse
JIT is enabled. Hardcoded into the DalvikVM sources I compiled.
Feeyo said:
Sorry. Language list is not complete. Greek is supported.
Click to expand...
Click to collapse
What other languages are missing? How about norwegian?
... and thanks for the ROM, btw!
skandahle said:
What other languages are missing? How about norwegian?
... and thanks for the ROM, btw!
Click to expand...
Click to collapse
Supported.
Great to see a new Froyo ROM on the scene! Look forward to seeing it grow into one of the best...
For now, my early impressions are that it suffers from the same problems as other Froyo ROMs have / do.
To name two (and aside from the obvious):
* LED notifications
* Google Mail App displays at incorrect resolution for Hero
It might be a funny question but... All other Froyo releases I tried have been getting really laggy after installing all the applications I like and then 3-4 hours of usage. I use a task manager to kill applications so that a lot of memory is always free.
Would I have the same problem with this ROM? I am sure you have been using it for a couple of days at least before going public.
I would test it out by myself but formatting my SD card is going to take a lot of time for backing up, etc.
BR.
cokbok said:
It might be a funny question but... All other Froyo releases I tried have been getting really laggy after installing all the applications I like and then 3-4 hours of usage. I use a task manager to kill applications so that a lot of memory is always free.
Would I have the same problem with this ROM? I am sure you have been using it for a couple of days at least before going public.
I would test it out by myself but formatting my SD card is going to take a lot of time for backing up, etc.
BR.
Click to expand...
Click to collapse
I have not yet run this build for a few days at it just came out of the oven...
But I did run some of the older builds of mine a few days and for me it stayed at the same performance. Although I do not have a lot of apps installed..
After installing apps you will need to give it a reboot to optimize the freshly installed packages.
Feeyo said:
I have not yet run this build for a few days at it just came out of the oven...
But I did run some of the older builds of mine a few days and for me it stayed at the same performance. Although I do not have a lot of apps installed..
After installing apps you will need to give it a reboot to optimize the freshly installed packages.
Click to expand...
Click to collapse
Thank you for the speedy response and support. Appreciated.
I have a few questions in addition to the ones I've already asked.
1) When you long press a textbox and select "Input Method" option, the keyboard appears twice. Is it normal?
2) The news and weather application cannot find "Sofia" or "Sofia, Bulgaria" as a location. Do you think that might be a bug in the ROM or in the application itself?
BR.

STOP!! Before You Post, Read This NOW!! UPDATED: 10/29/10

Thinking of posting a new thread???
Use the search button on the top bar between "New Posts" and "Quick Links"
Threads posted in the wrong fora will be moved initially; however, for repeat offenders, the moderating team will look to take action to rectify the situation in a manner it believes is appropriate
WITHOUT FURTHER NOTICE.
It is the responsibility of all users to keep the fora organised and clean. We need you to do your bit to keep things orderly.
To the dedicated members that care to keep this forum, subforums included, clean and organized and grouped.
Please start reporting threads to the mods to take action. Please use the REPORT button to do so.
Thank You and happy easy searching.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread)
Forum Rules - http://forum.xda-developers.com/announcement.php?f=642
Forum Search - http://forum.xda-developers.com/search.php
Google Forum Search - http://forum.xda-developers.com/showthread.php?t=304582
Advanced Searching - http://wiki.xda-developers.com/index.php?pagename=How%20to%20use%20Advanced%20Search%20on%20XDA-Developers%20Forum
XDA "Mantra" - http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
Post What Where:
General - general technical discussion items, news, anything else that does not fit into the other fora categories.
Q&A (Questions and Answers) - all questions, irrespective of type, get posted in here whether they be theme related, accessory related, technical, etc.
Accessories - any items to do with components and/or accessories relating to your device.
Rom Development - only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here.
Themes & Apps - anything to do directly with the development of themes and/or applications. Nothing else goes in here.
WB
MOD EDIT: BEFORE POSTING ANY THREAD IN THE DEVELOPMENT SECTION, PLEASE READ THE FOLLOWING:
If you have developed a ROM, or are working with others to do so, the development forum is somewhere to discuss and share ideas, post useful feedback and logs or crash dumps, and to discuss a common goal developers are trying to achieve.
It is NOT the place to post your question because it gets higher traffic, or because more experienced users frequent it. Doing this just annoys those who are working on the device, and drives them away. Developers don't want to wade through 20 threads of "Help me urgently" to find their threads for porting and fixing camera issues etc. Similarly, if a thread is designated as discussion for developers say, porting a camera fix, please do not post in there asking "When will it be ready?", "Can I flash this yet?" etc. This is both completely disrespectful to those working on the project (you evidently haven't read the important posts in the thread), and also is making it harder for developers to find comments from other developers or testers when required.
Similarly, don't make loads of "Thanks for your work here" posts in an active development thread. It's just as annoying to developers as asking when something will be ready. If a ROM is complete, then go ahead and thank the developer if you wish, but don't go into threads for devs only, and interrupt it to post "thanks". It's basically spamming, and is treated as such.
If you are posting in development, you should have read every sticky and notice there, and should be actively developing or helping in the development of something. Developing isn't installing a ROM, or using a tweak, it's creating a ROM or other hack or tweak. If you haven't read for several days before starting out on XDA, you are likely about to ask something already solved. I registered on XDA when I first wanted to post, and that was to join in a discussion on something. Sure, join up and ask a question, but read the information available in General and Q&A first, as your question will have been asked before. Search is your friend here, become familiar with it.
Regarding when to post in development if you are not actually developing something, there is one occasion where it's acceptable. If you find a leak of a new ROM, which isn't already posted, and you verify it's legitimacy via either running it, or based on the source you obtained it from, then this is assisting in development, and should be posted in development. If you want to ask when a leak will be available use search first, then if not already in discussion, open a thread in general or Q&A.
If you have a problem flashing a ROM, this is NOT related to development. It's up to you to determine if it is specific to a particular ROM, and post useful information in that developer's existing thread for the ROM. If it happens on more than one ROM, and isn't a known issue (remember you should read several times more words than you post), then find out what you are doing wrong. Check guides written by others, try to repeat the problem and see if it happens every time. Something needs to be reproducible to be fixed effectively.
Once you have identified what you need help with go to the device Q&A forum (general if device lacks one), and make a clear, informative thread that explains the issue, and what you have tried doing to fix it. Did you re-download the ROM? Did you ask a friend to flash it for you, to reduce chance of user error? What steps (exactly) did you follow? What errors did you see (exact wording)? Did you double check all the steps? Did you do a wipe or hard reset?
If you make a clear, concise, yet detailed post, you will find help forthcoming, and should get the problem sorted very quickly. If someone suggests you try something, report back on what happened, did it work etc. Then, next time someone has this issue and searches, they will find this and have a verified and tested solution.
So remember... before you start a thread in development, ask yourself what you are developing. If you can't answer, then stop, step away from the post button, and think about where you are posting. Would it be better in General or Q&A, or is some more time with your best friend, search, required?

[ROM][RMX1921][9.0.0][UNOFFICIAL] LineageOS 16.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Back camera
Front camera
Audio
Sensors
Flash
GPS
VoLTE
Known issues :
Selinux permissive
Fingerprint may not work properly
Report with logcat if found any
Instructions :
Download the latest build
Reboot to recovery
Make sure you're using stock unmodified vendor.
Wipe data, cache, system ( Don't wipe vendor )
Flash the latest build and GApps
Reboot
Downloads :
Unofficial Builds : Click Here
Source :
Device tree
Kernel tree
Credits :
@SagarMakhar for his work on Realme X
Thanks to all testers who helped in testing
XDA:DevDB Information
[ROM][RMX1921][9.0.0][UNOFFICIAL] LineageOS 16.0, ROM for the Realme XT
Contributors
thesprintster, SagarMakhar
Source Code: https://github.com/thesprintster/device_realme_RMX1921
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP
Based On: Lineage OS
Version Information
Status: Beta
Created 2019-10-17
Last Updated 2019-10-17
Screenshots
Changelog:
20191014: Initial build
wow! nice to see rXT development was fast after 3 days kernel source released!
can't wait to try this on rXT after 28 Oct (because Indonesia's rXT launched on 23 Oct lol)
Why screenshot has fingerprint icon on it?
Thanks for ROM and your efforts. :good::good::good:
Great to see ROMs popping
Thanks ? for such an amazing work , is there any telegram group for discussion ?
btw is there any way to revert back to stock rom ?
Waiting for stable one
naandha114 said:
Waiting for stable one
Click to expand...
Click to collapse
Yes , you should
wow amazing that development has started.. hope more roms comes.. waiting for RR Rom and Liquid remix roms with more stability..
can some one using this Rom, please take a video and show to us
Finally custom rom development has started. Hope to see more stable android 10 roms.
MOD EDIT: Quote full OP
hi
can use this rom for realme x2?
Wow! Now waiting for reviews.. Then will try it.
Hi,
I have removed some off topic posts from this thread. Please remember to post your comment according our rules. Thanks.
Rule refresher:
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.
3. Post using a clear and descriptive subject and message.
You're most likely to receive a helpful answer to your question, if you use a short subject title that describes your problem and a message that explains in detail, what your problem is and what you've done to try solving it.
Jerry
Forum Moderator
jerryhou85 said:
Hi,
I have removed some off topic posts from this thread. Please remember to post your comment according our rules. Thanks.
Rule refresher:
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.
3. Post using a clear and descriptive subject and message.
You're most likely to receive a helpful answer to your question, if you use a short subject title that describes your problem and a message that explains in detail, what your problem is and what you've done to try solving it.
Jerry
Forum Moderator
Click to expand...
Click to collapse
Ok i'm sorry
---------- Post added at 06:37 PM ---------- Previous post was at 05:57 PM ----------
h4mid said:
MOD EDIT: Quote full OP
hi
can use this rom for realme x2?
Click to expand...
Click to collapse
Different hardware , so you can't
Custom rom 243 said:
btw is there any way to revert back to stock rom ?
Click to expand...
Click to collapse
Go through this official page for stock rom flashing...
https://www.realme.com/in/support/software-update
I've read that if u unlock your bootloader the Widevine L1 certificate will go boom! Is this true? There is no way we could bring it back on custom ROM?
thanks for your great development work
Lol what the use of scribbling ,if it's clrealy visible your number inss

GSI AOSP 10 ROM For S20 & S20 Pro Ultra // stable [All model!]

Hello we are sharing a new union brush for the localised version of the S20 Planets
S20 is a fast phone with Multi Core CPU and top of the-line Large AMOLED panel.
What Works:
Wifi
Fingerprints
Touch
Brightness
GPS
Mobile data
Call
Speakers
Sounds
Camera
Videos
Recording
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download at: Mod edit--link removed.
Download Link it
Use Odin or Twrp brusher
Brush to AP slot @ ODIN
Brush to super partition @ TWRP
Format data to begin boot.
Have intact a Vendor image.
Credits :
Google
phhusson
Source: https://github.com/phhusson/treble_experimentations
Learn & extras added on : https://source.android.com/setup/build/gsi
Could someone share some screenshots or a video review? Does Gcam work?
TWRP ? where ?
Orphee said:
TWRP ? where ?
Click to expand...
Click to collapse
Exactly......
Sent from my SM-G965F using XDA-Developers Legacy app
pro199282 said:
Thanks for use my Rom
You use a different brush if you are not found TWRP.
Gcam support
Screenshot support
Click to expand...
Click to collapse
Is this a joke? We dont have twrp yet and what the heck is a different brush?!
speedyjay said:
Is this a joke? We dont have twrp yet and what the heck is a different brush?!
Click to expand...
Click to collapse
I think he is saying use Odin. I tired Odin and it got stuck.
pro199282 said:
are you kidding there is twrp
because u didnt enabled nand erase on odin to clean it though :laugh::laugh:
Click to expand...
Click to collapse
Erase nand? Are you joking? I wouldnt trust this....
pro199282 said:
its clean flash due encryption and then use my kernel its my Djraz mix NEMSIS so you dont need that again
and use twrp just format data easy flash my kernel in odin or twrp after patched it on magisk MOST fastest s20 pro or s20
Click to expand...
Click to collapse
Dude, with the greatest of respect - you come here with 25 posts, no pevious ROMs, nobody to verify this actually works and you want us to play guinea pig with our £1,400 phones? Can you post some screenshots or photos of your phone to show this actually works? Or, we're just going to have a really expensive paperweight...
pro199282 said:
without that understand you look i post picture odin how flash it btw
Click to expand...
Click to collapse
Okay, but thats not evidence that this actually works.
Do you know what a nand erase does buddy? It erases:
boot
recovery
kernel
system
data
cache
.android_secure
sd-ext
datadata
wimax
efs
If people get this wrong then they're going to have a useless device. You have to show us that this actually works.
pro199282 said:
offtopic my thread i guess
nand erase = only userdata erase
look at download mode that same time you do it it show in blue letter erasing userdata and use my new Twrp and nemeses kernel btw its soo nicceee
Click to expand...
Click to collapse
No, you're wrong. Nand erase erases EVERYTHING!! If you dont know this mate, then you shouldnt be making ROMs. I wont be trying this one.
pro199282 said:
like there it shows literallly cant belive it
Click to expand...
Click to collapse
Okay, if you've proven that this works - why isnt your Knox tripped?
Also, please go back to the main page and read the rules. It clearly states you need screenshots of the ROM working on your device.
I know we all have busy lives and don't have time to go through a list of long winded rules, so here's a shortened version to make your life easier
Only the following topics are allowed in DEVELOPMENT area:
[DEV] - Development for any special projects or Apps
[ROM] - Custom ROMs
[KERNEL] - Custom Kernels (usually found in Original Development)
[MOD] - Hack & Modifications for the phone with code only, zips go in themes and apps
[FIX] - Fixes for known issues & bugs
[R&D] - Research & Development for Devs only, when gathering data for a new projects
[HOWTO] / [GUIDE] - How to instructions and Guides (Most of the time should be in General)
Note: If you are unsure where your new topic should go, then please post it to General
Please Include Screen Shots for ROM / MOD / THEME / Apps & Games, when possible as it's expected by our members
DEV Support for ROM / KERNEL / MOD / THEME must be provided within XDA thread posted by the Developer, otherwise it won't count as a Development, and in turn it'll be considered [INFO]rmation / [REF]erence and moved to General
Unmodified Stock ROM and Source Codes does not count as a DEVELOPMENT project unless it's part of an active project you have already started
Password must be provided for all password protected files
Direct download links preferred, due to stipulations stated in forum rule #11
Extra emphasis on rule #12
All ROM / MOD / DEV / etc... found in the DEV section not created by the DEV themselves does not qualify as a development and will be moved to General. It should be properly tagged as [INFO] or [REF], with links to the source website were it was found
Please keep all non Development relevant chatter off the DEV project topics, feel free to create a new topic in General for non Development comments about specific ROM / MOD / THEME / etc... valid replies within a DEV project are: BUG Reports, Problem, Troubleshooting Steps & Logs.
... and Please! keep all your personal bickering via PMs, do not pollute the forum with your personal indifferences.
If you have a problem with a specific member please contact the Moderators for help, that's what we're here for, but we are not babysitters, we are here to gather, organize and provide useful information for our over priced phones
pro199282 said:
you learn what is nand erase https://www.sammobile.com/forum/thr...ase-All-option-as-one-suggested-me-to-do-that
he didnt broke it your the bad here your the bad in my post that you will be delete of my post Just belive that developers like am developer i know what i say its true
Click to expand...
Click to collapse
To be honest too, I really appreciate the effort. But it's quite hard for me to understand your posts... and as already said too, I'm not willing to try and untested rom/twrp/kernel on a 1k€ phone...
You really should explain how to flash, what are the impacts (data loss etc...)
pro199282 said:
ONLY data removed on NAND ERASE to you Moderation will block your account all your account that are you haves more if you have more accounts for what in my post here all everything its closed from my post You so bad
Click to expand...
Click to collapse
man nand erase will wipe everything and now your wanting us to use your gsi rom with zero proof it works as you dont have device
Orphee said:
To be honest too, I really appreciate the effort. But it's quite hard for me to understand your posts... and as already said too, I'm not willing to try and untested rom/twrp/kernel on a 1k€ phone...
You really should explain how to flash, what are the impacts (data loss etc...)
Click to expand...
Click to collapse
twrp cant mount super image stay clear
Thread permanently closed.
--Badger50

Categories

Resources