Related
Hy all,
inspired by this thread I spend some spare time in compiling OMFGB sources for use with the hero gsm.
Because of the fact, that I did not manage to successfully compile the OMFGB sources directly for the hero gsm (compiling was OK but could not get rom to boot) I did it the other way.
I compiled the sources for the hero cdma (heroc) and afterwards ported it to hero gsm.
I integrated Erasmux fly-kernel 13 since I used it with all other hero roms before.
After testing the rom for ~1 week (also my son is quite satisfied with it) I decided to share it.
I took out some apps that were not usable (for example God Mode) and put in minimal gapps so that it's possible to sign in on google account and run market.
Also I replaced the LatinIME.apk with the CMs one to get other keyboard layouts than querty.
I'd recommend to install morelocale2 to be able to dial 123456 instead of 123-456.
What I have to say is that I'm by far no developer (at least not on android platform).
Download
OMFGB-Hero -www.2shared.com
OMFGB-Hero - www.mediafire.com
Thanks and credits go to
OMFGB Team for their sources
Erasmux for the kernel
stritfajt and bharat_goku for their patients and giving me directions
i'll take a look at this when i've got some spare time
Thanks for the ROM but OMFGB without God mode? its like CM7 without CM settings lol D
cartman333 said:
Thanks for the ROM but OMFGB without God mode? its like CM7 without CM settings lol D
Click to expand...
Click to collapse
God mode seems not to be compatible with hero, all menu entries were grayed out, so I decided to delete it from package.
Maybe someone has a clue how to get it run
Can you upload it to some other site? I can't seem to download from 2shared.
aca89 said:
Can you upload it to some other site? I can't seem to download from 2shared.
Click to expand...
Click to collapse
Uploaded to mediafire
Just checked the zip,replace the heroc files in use/keylayout,keychars wit similar files from a hero rom,basically key functionality
Sent from my Hero using xda premium
bharat_goku said:
Just checked the zip,replace the heroc files in use/keylayout,keychars wit similar files from a hero rom,basically key functionality
Sent from my Hero using xda premium
Click to expand...
Click to collapse
I ported and tested the rom step by step.
Since all keys work as they should, I skipped this step.
I gave it a go. Not bad, for some reason I had extremely good wifi reception using this ROM, so that's good. Really missed some kind of advanced settings 'cause I use a lot of options from there and that was a dealbreaker . Also a2ext didn't work, so I had to flash darktremor script which caused i few random reboots. All in all, a solid ROM which could be much improved.
Cheers
aca89 said:
I gave it a go. Not bad, for some reason I had extremely good wifi reception using this ROM, so that's good. Really missed some kind of advanced settings 'cause I use a lot of options from there and that was a dealbreaker . Also a2ext didn't work, so I had to flash darktremor script which caused i few random reboots. All in all, a solid ROM which could be much improved.
Cheers
Click to expand...
Click to collapse
For the advanced settings, I could not get the God_Mode fully working so far.
For a2ext, I don't use it since I don't need it.
My son, which has a hero too, uses a lot of games.
For him I did custom mtd layout, much faster than a2ext cause it's kept all internal.
Please add the Russian.
I just ported the Sensation Rom, using the dsixda kitchen. Everything seemed to be going fine until I flashed ROM and is giving me, "Can't open....... (bad)". thru the FAQ on the kitchen post it was stated I need to change the recovery menu, (I'm a flashaholic.. not a dev yet ) so how do I change the RM.....
Please help I would like to post this alpha tonight
*****if anyone wants the link******
it's the new sense 3.6 ics 4.0 Rom All help welcome
Now I'm probably totally wrong....
But looks to me like either a bad download or that things aren't signed properly.
I guess we'll both wait till someone more knowledgeable comes along
~ I'm a fungi
a senile fungus said:
Now I'm probably totally wrong....
But looks to me like either a bad download or that things aren't signed properly.
I guess we'll both wait till someone more knowledgeable comes along
~ I'm a fungi
Click to expand...
Click to collapse
OK will look at them again ...... and try to redo them...... thankss
(Do you think I should try to post in development forum also? )
ku_ said:
OK will look at them again ...... and try to redo them...... thankss
(Do you think I should try to post in development forum also? )
Click to expand...
Click to collapse
No, don't post in the Development forum, as this isn't Development (yet) - it's still a question.
I'll download your file and see what's going on.
EDIT: Well first off, the ROM is WAYYYYY too big. Did you remove anything from it? Did you set up any symlinks to the Data partition to make up for the space the EVO lacks on /system? How exactly did you port it? Did you only use the tools in the kitchen? Not only won't that give you a complete working (or booting, even) port, but you'll end up having duplicate files, for multiple devices. What kernel are you using? There isn't an ICS Sense kernel for the EVO, so I'm curious to know how you were able to mod the existing GB Sense kernel code (or maybe the modified ICS AOSP code?) to get it working.
EDIT 2: I see you're using the build.prop from the Sensation, which will cause problems. Also, the Sensation is a qHD device - did you resize anything for our WVGA screen? You're better off starting with trying to port the new Primo leak, but even then, you'll never get it to boot without an ICS Sense kernel.
Captain_Throwback said:
No, don't post in the Development forum, as this isn't Development (yet) - it's still a question.
I'll download your file and see what's going on.
EDIT: Well first off, the ROM is WAYYYYY too big. Did you remove anything from it? Did you set up any symlinks to the Data partition to make up for the space the EVO lacks on /system? How exactly did you port it? Did you only use the tools in the kitchen? Not only won't that give you a complete working (or booting, even) port, but you'll end up having duplicate files, for multiple devices. What kernel are you using? There isn't an ICS Sense kernel for the EVO, so I'm curious to know how you were able to mod the existing GB Sense kernel code (or maybe the modified ICS AOSP code?) to get it working.
EDIT 2: I see you're using the build.prop from the Sensation, which will cause problems. Also, the Sensation is a qHD device - did you resize anything for our WVGA screen? You're better off starting with trying to port the new Primo leak, but even then, you'll never get it to boot without an ICS Sense kernel.
Click to expand...
Click to collapse
Holy Shyznit batman!!!!!! ok i'm still learning Just wayy to eager to help out .... Capt.
I used the tools in the kitchen, this would've /is the alpha - all resizing and tweaks would have been done from alpha 1.0 (this 1) through the final.
Is there another kitchen I could use that will make this easier on the kid....lol
ku_ said:
Holy Shyznit batman!!!!!! ok i'm still learning Just wayy to eager to help out .... Capt.
I used the tools in the kitchen, this would've /is the alpha - all resizing and tweaks would have been done from alpha 1.0 (this 1) through the final.
Is there another kitchen I could use that will make this easier on the kid....lol
Click to expand...
Click to collapse
No. If you're just starting out porting, it's best to start with something that actually has a chance at working, so that you can understand how everything works and what everything does. Technically, you don't even need the kitchen to port a ROM - it makes it about as easy as it can, while recognizing that it's an experimental feature with limitations.
There's a thread about porting different versions of Sense that should help you with the files that you actually need to move, and the content in the (now closed) kitchen thread should help out if you have any issues (sd card won't mount, sound doesn't work, etc.).
I recommend you first try to port something close to the EVO, like a Shift ROM. Try to get Sense 2.1 working on the latest OTA. I bet that'll take a whole lot of work, if you can do it at all (different versions of GB). If you do, you'll definitely have some skills/tools that can help you in your quest for ICS Sense.
ku_ said:
Please help I would like to post this alpha tonight
Click to expand...
Click to collapse
Take it from someone who had cooked and posted literally hundreds of rums for multiple devices, and don't post anything until you've built at least 20 different (semi-)working roms for yourself first. You are opening the door to major criticisms (*****ing) and a lot of support work (which you may not be ready for) if you make your work public too prematurely.
Captain_Throwback said:
No. If you're just starting out porting, it's best to start with something that actually has a chance at working, so that you can understand how everything works and what everything does. Technically, you don't even need the kitchen to port a ROM - it makes it about as easy as it can, while recognizing that it's an experimental feature with limitations.
There's a thread about porting different versions of Sense that should help you with the files that you actually need to move, and the content in the (now closed) kitchen thread should help out if you have any issues (sd card won't mount, sound doesn't work, etc.).
I recommend you first try to port something close to the EVO, like a Shift ROM. Try to get Sense 2.1 working on the latest OTA. I bet that'll take a whole lot of work, if you can do it at all (different versions of GB). If you do, you'll definitely have some skills/tools that can help you in your quest for ICS Sense.
Click to expand...
Click to collapse
ok will do if I have a question or need help could I call you up, through gtalk?
indagroove said:
Take it from someone who had cooked and posted literally hundreds of rums for multiple devices, and don't post anything until you've built at least 20 different (semi-)working roms for yourself first. You are opening the door to major criticisms (*****ing) and a lot of support work (which you may not be ready for) if you make your work public too prematurely.
Click to expand...
Click to collapse
shhhhhooooooot *****ing ain't nothing new ..... lol I have tough skin But I do heed the warning and is grateful for the insight..... if night call you up also if possible.
haha you see?
I told you somebody more knowledgeable than me would come around...
Thanks guys
~ I'm a fungi
One major problem is there's not a fully functional kernel to boot ICSense soooo that's the first issue here, next would be if the dpi and images haven't been resized to match the evo's resolution there will be major visual flaws and possible won't boot, if you really want to start porting roms I'd suggest starting with a GB rom since they are stable and there's alot more info and tools out there to get it ported
________________________________
{We are legion, for we are many}
>Sent from my Anonymous DeathStar in the depths of GalaXy S2<
-Coming soon to an Evo4G near you?: [AoSP]EViL-MoD_FReEvO v0.1[Free your phone]-
Hi,
I am really full of compliments about the good work of some guys that have done a good job in building the actual CyanogenMod versions for Wildfire S.
Thank you sooo much!!
But what I currently do not completly understand...
Why are most of the CM users really happy about version 10.2 or version 11.0 (like orig. CyanogenMod or WFSY) when those versions - last version of CM 9.2.2 included - do not even have GooglePlay/PlayStore and Data2SD (or Link2SD) installed?...
The last (and obviously most advanced CM version) CM9 (alpha9, v.9.2.2) would already be a wonderful solution for the WFS phone (I tested it!!) and it is said to be nearly finished (even video camera is working now at the version of Olivier) BUT both mentioned, absolutly necessary components are missing (and nobody mentioned it yet). Or what can I do with a phone where I cannot install new apps at all?..
So what is it that I misunderstand?...
I would be very happy if anybody could inform me about how I can find a version that has a complete set of system apps or how/where I can find both missing components to complete them by myself. (and even more happy if the cyanogenmod update function would still find some updates)
Otherwise I would guess that not any of the existing CM-based versions for Wildfire S can be used at all...
Should all the past work for creating a CM version (Android 4.x !!) for the (unfortunately!) one and only COMPACT smartphone on the world, 'Wildfire S' (I must admit, it is in fact!!) should have been completly in vain ???... I couldn't believe it.
Thank you guys very much for your nice explanations!
All the best to this wonderful community,
from Falk
CyanogenMod said:
Google Apps are the proprietary Google-branded applications that come pre-installed with most Android devices, such as the Play Store, Gmail, Maps, etc. Due to licensing restrictions, these apps cannot come pre-installed with CyanogenMod and must be installed separately.
Click to expand...
Click to collapse
Gesendet von meinem Xperia Z mit Tapatalk
Hi Olivier,
many thanks for your tip. You did not mention the point directly but I could answer most of my questions by mayself then.
Now I installed CM9 'cm-9-20140720-Olivier-marvel' together with 'CronMod-INT2EXT+_signed'. Works pretty fine!
Only little questions have been left now...
1.) How can I sort my app icons by subjects/folders (s. HTC Sense)? This Trebuchet launcher does not seem to support anything like that. If there is no chance, which launcher would you suggest instead?
2.) There is no really 'useful' version of CM10 or CM11 for WFS yet, is there? I couldn't find. Do you think there will be s.o. still working for a final version next time?... (why is Wildfire but not Wildfire S an official CM development?)
2b.) At your current version CM9, is there any problem left that should still be fixed? Everything works fine here yet...
3.) Therefore the OTA updater for CM would be a fine feature like in CM9 vers. 9.1.0 (but no updates found yet!). But your current CM9 version does not support it any more. Any reason for that?
3a.) Are updates possible anyway without flashing the whole ROM?
3b.) Is there anybody managing OTA any update of CM (v. 9..11) for WFS?
3c.) Are OTA updates from cm9 to cm11 possible?
4.) Skype does not react when clicking the icon to start it. Any idea what is the problem?...
5.) Some system programs (e.g. contacts or call manager) do not have that nice design than before. There is no chance/choice to exchange them?... (if yes, how and where to find alternatives?)
Thank you again for your final responses!
First of all this really does not belong in the development section, in Q&A perhaps.
And you just can't ask every single think that comes up in your mind, you gotta search a little bit and try it out for yourself.
Now, 1. Trebuchet does support folders but not auto-arranging. Most of the popular launchers support this.
2. The current CM10 and CM11 are perfectly functional and working. Though they lag a bit (which is fair considering our old device). And the wildfire only had an official CM7 which is very old now.
2b. If you don't have a problem it does not contain a problem.
3. OTA is working for CM11. But for CM9 a OTA makes less sense considering that its stable now.
4. No idea.
5. Again you have to look for yourself, nobody can babysit you all the time.
thanks very much!
Okay, maybe question 1 might belong to Q&A. That's it. Sorry.
To make you understanding (sorry to write again so much!)...
to 1.) Did not expect that it would support it. So I did not even search for!... Thanks, this drag/drop solution is more than perfect!!
to 2.) Sorry, then I am not able to find them. I searched a lot and found actual version like 'WFSY11.0-WFS-V5.5, 20140723' or 'cm-11-20140726-NIGHTLY-marvel' where not even back button or Android option menu worked. Lots of functions are missing. I did not try 'cm-11-20140810-NIGHTLY-marvel' but do not expect more within one month. The same with cm version 10.2. In a thread I read that it was give up because cm11 is already working better.
**** So would you please give me the link to the finished versions of cm10 and cm11, please? ****
(a patch for the video camera problem seems to be existing shortly now...)
to 2b.) My first problem I saw was missing updater in cm9 for version 10 and 11. And the strange Skype problem. And video problem was fixed JUST before!! BT seems to have restrictions as well. So there is good reason to ask this question!?..
to 3.) It seems as if simple updating from Android 4.0 to 4.2 (cm10) and 4.4 (cm11) isn't possible!?... Officially it seems to work. E.g. OTA of Samsung offered update from 4.2.2 to 4.4. Strange!... How/why does it work here?...
Remark: So I suppose it is CyanogenMod which does not support it... It will not work without 'Titanium Backup' here...
to 4.) I suppose you will have the same problem!? Maybe you have opportunity to try out quickly!?... Skype really does not seem to run on WFS cm9+INT2EXT+. Isn't that strange?... (I reinstalled it already. No chance.)
to 5.) I asked this HERE because it belongs to SYSTEM apps (contacts or call manager) that cannot easily be exchanged, as far as I know!... Can they?...
There is one thing I would like to add, after your remarks to my point 2... Maybe I could not find the right sources. But this is because there is no resource pool (about WFS at XDA anywhere. Instead there just appear 'lonely' links in some threads. And instead of telling/explaining the systematics (if there is one) you guys generally just mention the fact (e.g. a link). So this makes it hard for non-insiders. You understand what I mean?...
(so e.g. I will have to ask (in another thread) how I can find the 'FM radio' app (no streaming!) which is missing in CM9 - instead of just looking at the right page where they are collected)
I would be really happy to get to know at least where you guys have found the informations for all what you do when 'cooking' new versions, etc.!...
Cause then I would have read about all that much more!... Instead of blaming me. Sorry, if I do not have that general info that you got already.
Maybe you understand better now!?... Would be fine.
Anyway, thanks a lot for your short repsonses. Have a nice day!
Again only things that are directly related to development are to be placed in development section. And NO if you have a problem with a rom you have to ask it in Q&A. Read the development forum rules in the stickies attached to the top of the section.
And you could also try reading through the stickies in the general section. It will give you some understanding.
Now CM10 and CM11 works, the threads are pretty high in the development section, you can find them if you look. The version of CM11 you used is the right one (the NIGHTLY) and back button does work. Try the later versions. Officially updating to a higher version is different and large corporations can spend time and money to make it work. But it just is not possible (or rather safe) with the variety of unofficial roms. You could try but most probably fail. You can install different apps for call and messaging and they will work. Search for those apps. CM9/10 works fine and have very less amount of problems. Now remember that this is a very old device and the devs are doing it NOT as a profession. So every single thing will never work.
Now as a last your largest problem is you think everything will be written somewhere in front of your eyes. It will not be. You have to use Google before asking a question. And also you just have to calm down and fix your attitude.
aWFSuser said:
First of all this really does not belong in the development section, in Q&A perhaps.
Click to expand...
Click to collapse
That was my fault, I'd moved this out of a thread and mistakenly put it in the Development section. All sorted now.
thanks again for your time to answer!!
I know, I sound as if I would not know which hard work you guys do. But I do, aWF Suser. And I mentioned that already in the beginning.
And I have heard already from your collegues that it would be a good idea if things could be organised some better. The official cm versions e.g have a central resource pool. Or the android-Wiki and CM-Wiki notes are all out-dated (from 2012) !!... Etc.
But PLEASE understand this more as a suggestion than a criticism - from a user that in your eyes only expects and criticises but cannot give. This is not the case!
Thank you!
I know it is an old smartphone I have. And I would have bought a new one already a long time ago. But even Samsung Galaxy Mini is too big in size and some important functions you will only find in the big version. Why is that so? Nobody can explain!... (i would pay the same price for a small phone!!! Handy devices must not be worse and more expensive than big ones!!)
The WFS is just the only really COMPACT smartphone all over. And I am sad that the industry detected a trend to bigger displays. The opposite is the trueth. Nearly all my friends e.g. like to have a compact phone but those always a beginner versions/hardware which cannot be understood at all.
Really sad. It is a big strange hole in products on market, isn't it?...
Unfortunately you did not give me tips how I could find a way to get more familiar with what and how you guys are doing. Is it a secret? I could imagine to do some work here as well. I am very interested in how you are doing your development work!...
Thank you again...
Now it is sure...
Olivier's last CM9 version still has bugs, not only the problem with lgCamera and Skype but also at the akku loading status.
It seems as if it is not correctly refreshing. The loading curve (s. settings) slows down a lot and shows e.g. after 4 hours loading still 43%. But after rebooting it changed to the right value finally: 100%.
So again my question before, as Olivier unfortunately put away the OTA update function (but ment that it is not necessary anymore):
How can this version be fixed?
As far as I know you don't offer patches but only complete ROMs...
Okay first sorry for being rude as posting in the development section was not your fault.
Now the main problem with our device is not that its old but that it has a armv6 cpu which is not supported by later android versions. So development for developers is tougher and bugs will remain. I mentioned the general stickies before there you can find some useful guides.
And have you installed GAPPS in CM9 because some apps depend on it and won't work without it.
And just to be clear, I'm not really a developer but just a user like you.
I never said CM9 doesn't have bugs. It's is clearly stated in its OP that:
modpunk said:
This ROM is not meant for daily use!
Click to expand...
Click to collapse
Hallo Olivier,
never mind. But I just understood it like that. As you gave the reason for the OTA non-support in your ROM.
So if I misunderstood you... what is your reason then?...
In fact it would bring us forward if you could please comment my questions and/or give tips to solve the mentioned problem.
@so please give me a chance to fix the akku status bug. This is really annoying.
Can you confirm that problem? And if so will you fix it?
And if so how can I update it by OTA updater? Or alternatively at least by a patch but not by a new complete ROM !?...
@TO the Skype problem...
First of all: can you confirm my problem?...
To your question: I used your ROM from 20th Aug. (119.518 KB) This one contains already gapps, I suppose. Cause Google Play and the other stuff was already installed!...
@TO lgCamera...
This wonderful camera app worked fine with EQDKP (v.2.3.5) but now it is too slow and hops a lot. Can you confirm that?
And if so do you have any idea why this is a problem?...
@how can I add FM Radio (analog) support?...
Thank you very much for your feedback!
PS: So if the last version of CM9 is not ment for daily use... which CMx version is it then? Is there none?...
Currently your cm9 works fine. Only those three problems so far...
Do you care for my bug messages?... (or where can I post them?)
Hallo aWF Suser,
yes, I know the problem with the arm version. You must not excuse for any bug in CM.
I do not have problems with bugs. I have more problems when they cannot be fixed easily (missing OTA updater) or errors are not heard or cared for so that bugfixes will not be available at all...
By the way the phone Wildfire (without 'S') is supported by Standard CyanogenMod and also has an ArmV6 processor!...
You mean I should read again the forum rules?... What is it that is is still annoying you in my style of writing?...
Olivier's ROM I used (s. previous message) obviously contained GAPPs already. GooglePlay atc. was already installed. So this should not be the reason, should it?...
First of all: can you confirm my Skype problem, aWF Suser?... I expect it to be in each CM9 version!...
Thank you very much for your support!
PS: By the way, I have compatibility problems when flashing ROMs. For nearly each ROM I have to change the recovery. Is there any that can read all 'formats' of zip files?...
Falk2 said:
Hallo aWF Suser,
yes, I know the problem with the arm version. So you must not excuse for any bug in CM.
I do not have problems with bugs. I have more problems when they cannot be fixed easily (missing OTA updater) or bugfixes are not available at all...
By the way the phone Wildfire (without 'S') is normally supported at CyanogenMod and also has an ArmV6 processor!...
You mean I should read again the forum rules?... What is it that is is still annoying you in my style of writing?...
Olivier's ROM I used (s. next message) obviously contained GAPPs already. GooglePlay atc. was already installed.
So this should not be the reason, should it?...
First of all: can you confirm my Skype problem, aWF Suser?... I expect it to be in each CM9 version!...
Thank you very much for your support!
PS: By the way, I have compatibility problems with ROMs. For every second ROM I have to change the Recovery. Is there any that can read all 'formats' of zip files?...
Click to expand...
Click to collapse
The Wildfire is listed officially only for CM7 (gingerbread) . After that it has not been supported. I am not asking you to read the rules, in the stickies in general section there is a thread that lists some guides to some useful things. And is OTA that necessary because in most cases a dirty flash is enough to upgrade from one version to another as long as its the same android version. Upgrades between different android version would not be possible even with OTA (as lots of things change, it will probably end in a bootloop). I am not using CM9 currently so can't speak for that.
So then which CM version are you using on your WFS? And why?
I flashed cm11 shortly but it still has too many problems. E.g. the camera app crashes after successfully recording a video, the launcher only has two pages, launcher does not seem to support folders, etc.
Do you know where I can find the actual todo list? (AndroidWiki unfortunately is not maintained anymore!)
I will give Paranoid 4.45 a try yet. Maybe this is better!?...
Otherwise I will keep cm9 and hope that we can find out why Skype is not running.
Oooh, that is important... I can make a 'dirt flash'? This is very fine!! Then OTA is not that necessary, of course. But there is still no reason to left it away, is it? Especially because all this observing and searching for the update is NOT necessary! Can't understand Olivier here...
Could you comment my PS as well, please?...
(error log: "cannot load volume /misc. Can't partition non-vfat: /sto .. (vfat)")
http://forum.xda-developers.com/htc-wildfire-s/development/cyanogenmod-10-t2908631
is there any better rom than this rom? how can i improve battery life with screen on? i want it for daily driver, i do not use bluetooth ad2p but i dont know what armv7 features means...
for me its affordable atm and give a new life to the oldie and shiny wfs
Which rom is the most stable for everyday use?
(With working wi-fi tethering)
I've searching for karthick111's cm11 folder, then i saw a folder called "cm14.1" with a zip called "cm14.1-20161220UNNOFICIAL-nevisp" and i downloaded and flashed it but it bootloops :'v
Does anybody know if it's usable or a wip?
Pd. There a bootable cm13 rom that i'm using to write this :v
I'm sorry if i had a bad engish, i'm a mexican :v
armando121504 said:
I've searching for karthick111's cm11 folder, then i saw a folder called "cm14.1" with a zip called "cm14.1-20161220UNNOFICIAL-nevisp" and i downloaded and flashed it but it bootloops :'v
Does anybody know if it's usable or a wip?
Click to expand...
Click to collapse
Yeah... I have just flashed it, but it has been in a bootloop for 20+ minutes already. Needless to say, this is probably a test/WIP CM14.1 build that @karthick mostwanted is testing for the Galaxy Fame to see if it will work at all. From what I am aware of, later CM ROMs (CM13, 14, and 14.1) will not work as well as they should on this device as it is low-end and doesn't have the RAM or processing power that is required, however, CM13 is fairly usable from what I have tried, but I still find the CM11 (KitKat 4.4.4) ROMs to be the best. Then again, it is always good to keep and eye on and test the latest builds that the developers release, as I have seen some older devices get ROMs which shouldn't work on them because of their hardware, but do, because the developer is able to configure it to make it work.
I'm disappointed
I don't know why everyone being stalkers
The work is not even done yet and u guys are posting it here without my permissions
Yes in next build I will try to brick the device badly if this persists again
If the work is done I will share it for sure
Don't irritate developers by doing this way
karthick mostwanted said:
I'm disappointed
I don't know why everyone being stalkers
The work is not even done yet and u guys are posting it here without my permissions
Yes in next build I will try to brick the device badly if this persists again
If the work is done I will share it for sure
Don't irritate developers by doing this way
Click to expand...
Click to collapse
Fair enough, but I assumed that since it was publicly available to view and download, then it should be okay to publicly discuss about the development surrounding the ROM/s, but I guess not.
Thank you for the time and effort you put into these builds and the continuation of custom ROM development for this device.
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
kpmohamedhussain said:
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
Click to expand...
Click to collapse
really ...anyone who gets a brick because of not reading a thread certainly shouldnt be xda or even messing around with the phone in the first place. just stay stock if you wont read
We survived finely when Nougat was still new, so what makes Oreo special?
There's simply no good point to making a whole section for a particular version of Android. The same thing can be done simply with a proper thread title.
The problem isn't purely on the lack of separation of sections — It's the 5 seconds attention span that most seems to have because they can't read the first post of the thread they're in or they're too busy looking at butterflies and they ended up destroying their device and/or data inside the device.
I know we can't fix people, but that doesn't make for a good argument for creating a new section.
kpmohamedhussain said:
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
Click to expand...
Click to collapse
As stated. This is not gonna happen. If you cant do the proper research needed for what you are doing then you shouldnt be doing it in the first place.
I disagree with OP - there shouldn't be separate section for Oreo stuff. Ask yourself - what would happen, if released mod would be compatible with Marshmallow, Nougat and Oreo?
Okay, now that's not going to happen. But what can happen is in every thread the op can state the supported android versions first or the rom's android version first and then state what is the thread for (rom, mod, source code...). Something like "[7.1.1][ROM] Resurrection Remix 5.8.4 SomethingTweaks Edition" and not "[OH YEAH BABY WE SUPPORT COLOR ENGINE] CrazyManiacLunatic Tweaks". All the OPs should first give the supported android version or the rom android version then state what is the thread about and then write the rom that they are based on then write the name that they've given. But they MUST write the android version and the thread's reason to exist at first. Because this way when you are looking for an oreo rom you just have to look inside the first bracket and find it quickly instead of checking each thread's name to first find out where is the version and then looking at the version.
charackthe said:
Okay, now that's not going to happen. But what can happen is in every thread the op can state the supported android versions first or the rom's android version first and then state what is the thread for (rom, mod, source code...). Something like "[7.1.1][ROM] Resurrection Remix 5.8.4 SomethingTweaks Edition" and not "[OH YEAH BABY WE SUPPORT COLOR ENGINE] CrazyManiacLunatic Tweaks". All the OPs should first give the supported android version or the rom android version then state what is the thread about and then write the rom that they are based on then write the name that they've given. But they MUST write the android version and the thread's reason to exist at first. Because this way when you are looking for an oreo rom you just have to look inside the first bracket and find it quickly instead of checking each thread's name to first find out where is the version and then looking at the version.
Click to expand...
Click to collapse
Yeah that is not gonna happen either. This gets brought up every few years and the answer is always the same. The devs can name their threads anything and any way they want. Heck they don't have to encludes any info at all.
People seem to forget that this is a developers site. Not a rom site or a support site. You are expected to do your own homework and have all the info you need before flashing. That encludes how to use command line to recover from something bad happening.
zelendel said:
Yeah that is not gonna happen either. This gets brought up every few years and the answer is always the same. The devs can name their threads anything and any way they want. Heck they don't have to encludes any info at all.
People seem to forget that this is a developers site. Not a rom site or a support site. You are expected to do your own homework and have all the info you need before flashing. That encludes how to use command line to recover from something bad happening.
Click to expand...
Click to collapse
Well, developers love mentioning how they won't take responsibility if anything happens in every single thread over a million times but they seem to forget that people are looking for most basic info in the OP post. Developing can only be achieved if you acknowledge something and share it with others. The progress can not be achieved without information. I'm not going to flash a rom just to see if it is a Nougat or an Oreo rom. And I'm not going to flash all versions of modems to see which is the right one. Developers and maintainers must inform casual users or other developers about what is they are looking at. Sharing is caring. Not everybody likes to use something they don't know.
charackthe said:
Well, developers love mentioning how they won't take responsibility if anything happens in every single thread over a million times but they seem to forget that people are looking for most basic info in the OP post. Developing can only be achieved if you acknowledge something and share it with others. The progress can not be achieved without information. I'm not going to flash a rom just to see if it is a Nougat or an Oreo rom. And I'm not going to flash all versions of modems to see which is the right one. Developers and maintainers must inform casual users or other developers about what is they are looking at. Sharing is caring. Not everybody likes to use something they don't know.
Click to expand...
Click to collapse
And that is what a Gerrit is for.
To be honest. Causal users are not the focus here.
zelendel said:
And that is what a Gerrit is for.
To be honest. Causal users are not the focus here.
Click to expand...
Click to collapse
I see you all over the place! You are retired? You post on here like its full time lol
ZVNexus said:
I see you all over the place! You are retired? You post on here like its full time lol
Click to expand...
Click to collapse
I am a retired mod. My job allows for me to always be lurking around. Every couple of hours or so I check my email and catch up.
Been that way for as long as I can remember. Heck I used to be on far more in the early years.