[ROM][EXPERIMENTAL][6.0.1 r43][tate] Bliss Rom 6.4 by Team Bliss - 7" Kindle Fire HD General

This thread was a mistake and has been marked to be deleted. Please find actual release thread here: http://forum.xda-developers.com/kindle-fire-hd/7-development/rom-bliss-rom-6-4-team-bliss-t3400567

Reserved
This thread was a mistake and has been marked to be deleted. Please find actual release thread here: http://forum.xda-developers.com/kindle-fire-hd/7-development/rom-bliss-rom-6-4-team-bliss-t3400567

Reserved
This thread was a mistake and has been marked to be deleted. Please find actual release thread here: http://forum.xda-developers.com/kindle-fire-hd/7-development/rom-bliss-rom-6-4-team-bliss-t3400567

electrikjesus said:
GUIDE, FAQ and Useful Links
Much of what follows applies to many ROMs. If you have suggestions for things to be added to this guide or find any errors then please let me know.
Purpose and Rules of XDA
XDA is a development site. It is for learning and sharing. It is not here to "provide" apps or support to users. Most of the people that develop or help or support do so in their free time. No one "owes" you anything. You are not "entitled" to anything. Those that help others, are polite and try to help themselves will be more likely receive helpful and polite assistance.
Rule number one of XDA is : Search
Other rules include:
Be respectful
Be tolerant
Be helpful
Don't be an ass
Q&A or Dev Thread?
There is a separate development thread and Q&A/Discussion thread. Right now, I am happy for you to report all issues in the development thread.
But as it is a development thread, you should provide logs where ever possible and only report bugs if you have clean flashed. Telling others there may be an issue if you dirty flash is acceptable but please word it as such not a bug.
A little banter is accepted in the development thread, but please don't turn the thread into a chat room. Let's keep it fun but not so long nobody can be bothered to read, otherwise I'll have to revert to using the Q&A.
The Q&A is still there and available and is more "free".
Flashing
You should clean install for best results. If you "dirty flash" then at least wipe cache and dalvik/ART and you MUST provide logs with any issues.
Clean v Dirty Flash
There are a number of interpretations of clean flash. In recovery you should factory reset or wip everything except internal storage. This will wipe your apps and most app settings.
Whilst there are ways of backing up your settings they are not recommended because they can cause issues when there are changes to the ROM which affect how settings are stored or recorded. Do not restore system data: this often leads to forced closes and constant error messages.
You can use a backup app like Titanium Backup or Parcel. Sometimes restored apps can cause issues, and it is better and cleaner to re-download them, although not everyone has the time or inclination to do this.
If you do not wipe as per above, then you are dirty flashing. This is quicker and often works. But because things are left behind from the previous flash this can result in weird issues. When you dirty flash you really should wipe cache and dalvik/ART, so that there aren't residual
Reporting Issues
Before Reporting Issues
If you have issues with your new flashed system there are a few things to do before you report them.
First, if you have dirty flashed then try a clean flash to see if the issue remains - many issues are cleared this way. Also, it is very difficult to pin-point certain issues after a dirty flash.
Also, if you have Xposed installed then remove that before reporting. This is because Xposed can change things deep within the OS and make things behave differently, which in turn makes it very difficult to troubleshoot and resolve issues. This is Xposed hate - many devs require this and will not offer any support if Xposed is installed.
Reboot. It's surprising how many issues can be resolved by this simple step. Especially if an app is misbehaving or using a lot of battery.
How to Report An Issue
The biggest bugbear of those trying to help with issues is when they are not properly reported and require to have the same questions answered over and over. The circumstances may require different information, but here are a few common items to consider posting:
Version. Often people miss this and are reporting something that was solved days or weeks ago. Others say "latest" when it may not be. Quote the version number and/or build date.
Firmware. Again, quote the date or source.
GApps. The GApps version can affect which version of Google Play Services and PlayStore, amongst others that are used. Whilst often GApps can be "out of date" without any issue, when there is a lot of development by CM this can be very relevant.
Whether you clean or dirty flashed.
A log. Necessary if you dirty flashed, very useful even if you clean flashed. See below for how to do this.
How to replicate the issue. The more specific about how the issue arises and when, the more likely you are to get a quick resolution. If no one can replicate the issue it is unlikely they can resolve the issue.
How to Take a Log
This is an excellent guide.
Some kernels have their own log/bug report option to make things easier.
Useful Links
Google and the XDA search bar are your friends.
Whatever you want to ask or find, it's probaly already there. This is why you often see replies just saying "Search!"
XDA: RULES - MOD HELP - SUMMED UP 1 - SUMMED UP 2 - BEST WAY TO GET A LOG
Frequently Asked Questions
No one answered my question.
Maybe no one has read it yet - you may need to give it time. Maybe no one knows the answer yet. Have you already tried to solve the issue? Were you polite? Did you give enough information? There is no need to keep bumping your post.
Which folder does the OTA file get downloaded to? Is it the full file or just the incremental update? Are there nightlies?
/sdcard/Download and it's the full file. They aren't nightly but they are normally very frequent.
Does BlissPop support Layers / RRO?
No. It has the CM theme engine.
Which kernel is best for....?
Stock is really quite good, so I'm not going to suggest any others, as there aren't many now and are easy to find on XDA. So much depends on you: your setup, apps, usage, signal. The list goes on. The real best way to find out is try them for yourself; give each one a few days to settle and you can observe battery usage, smoothness, speed, tweakability etc. But there is no Holy Grail kernel - one that gives the best of everything for everybody. "Performance" and "battery" aren't mutually exclusive, but most kernels are biased towards one or the other. Kernel governors and hotplugs also have an effect. If you are interested in a kernel, read some of the kernel thread.
One last point. When there are changes from CM the date and commits of a kernel can be important so the kernel and ROM aren't out of sync.
How is Battery Life
This often gets asked, but there is no clear answer that suits everyone. So lets start of by saying the team finds battery life to be very good.
There are however many things affecting battery life. Your apps, settings and signal all have a big effect. As does how often your apps are updating and whether over wifi or mobile data. Additionally, which kernel and it's settings also have an effect. As does screen brightness. Certain social and messaging apps can have a huge drain. How often you flash a new ROM has a big effect too. Ideally, from a battery life perspective, you should allow everything to settle and go through a couple of charge cycles. With the frequency of BlissPop updates I have never achieved this!
So every user will have different battery life and typical screen on time. Make sure when doing comparisons you really do it on a like for like basis.
If you want to investigate battery usage, consider apps like Wakelock Detector (WLD) and Better Battery Stats (BBS) as well as GSAM Battery Monitor. These will often pinpoint where battery is being consumed and what is waking your device. Quite often you will see an app misbehaving which can often be resolved with a simple reboot.
?
?
Click to expand...
Click to collapse
Wow! It's even official! This thread should be in 7" KINDLE FIRE HD ANDROID DEVELOPMENT section, by the way. Thanks man. I'll try it soon.

alexander_32 said:
Wow! It's even official! This thread should be in 7" KINDLE FIRE HD ANDROID DEVELOPMENT section, by the way. Thanks man. I'll try it soon.
Click to expand...
Click to collapse
I just moved it there, Thanks!

Related

Description requests

Hi guys,
I've been reading this forum for almost a month now (since I got my Epic), and I still haven't seen any description for a lot of the software you're using. I'm not an idiot here, I made a joeykrim exploit uninstaller of my own shortly after noobnl posted the one click exploit. Still, I'm not a mind reader. How do you guys even keep up with this?
ClockworkMod - The website describes it as, "An open source recovery image used by many phones". Not very helpful. There's a post on their forums asking what it does, with no response.
Andromeda - Apparently a ROM Manager with built in root. Not very helpful. Starting from the top, why would I need a ROM manager? Does this run on the phone? Why would I want a ROM manager on my phone? Doesn't this serve the same function as ClockworkMod?
AOSP Magic and Tha Boss ROM - Neither of these have any instructions. Tha Boss ROM actually includes a download link, while AOSP Magic eschews the link in favor of a video review. The video review is nice, as it contains the first instructions I've seen so far, brief as they may be.
A few lines of description on your releases would really help the new people. Really, you'd have to be a fool to download these programs and flash/fry your phone without description or instruction! You're pushing away the more cautious people who might otherwise join in.
Netop said:
Hi guys,
I've been reading this forum for almost a month now (since I got my Epic), and I still haven't seen any description for a lot of the software you're using. I'm not an idiot here, I made a joeykrim exploit uninstaller of my own shortly after noobnl posted the one click exploit. Still, I'm not a mind reader. How do you guys even keep up with this?
ClockworkMod - The website describes it as, "An open source recovery image used by many phones". Not very helpful. There's a post on their forums asking what it does, with no response.
Andromeda - Apparently a ROM Manager with built in root. Not very helpful. Starting from the top, why would I need a ROM manager? Does this run on the phone? Why would I want a ROM manager on my phone? Doesn't this serve the same function as ClockworkMod?
AOSP Magic and Tha Boss ROM - Neither of these have any instructions. Tha Boss ROM actually includes a download link, while AOSP Magic eschews the link in favor of a video review. The video review is nice, as it contains the first instructions I've seen so far, brief as they may be.
A few lines of description on your releases would really help the new people. Really, you'd have to be a fool to download these programs and flash/fry your phone without description or instruction! You're pushing away the more cautious people who might otherwise join in.
Click to expand...
Click to collapse
clockwork rom manager is an app on your phone that requires root access, allows you to flash roms under the android OS and is nice and GUI (graphic user interface)
clockwork recovery is at the boot level, before the android OS loads, it's used as a minimal menu to do lower level functions such as flashing roms to your phone, clockwork rom manager uses this as it's backend for flashing roms.
androidmedia, boss rom and aosp magic are all roms (entire custom android OS packages) flashable though clockwork recovery
everything listed as a kernel is only a chunk of the OS that controls the hardware and such... they can overclock the device and improve battery etc. applications and favorites and other user data stuff is uneffected.
the weird names are just what the developers are naming their software. What you should be paying attention to are key terms like
ROM, KERNEL, RECOVERY those are the different parts that are being modified...
That being said.... for someone that researched for over a month, you don't seem to be quite getting it, also this doesn't need to be in developer forum, and all this is in the hundreds of WIKI's posted on other android devices.. also a quick google search would answer most of your questions you're having
Netop said:
ClockworkMod -
Andromeda -
AOSP Magic and Tha Boss ROM
Click to expand...
Click to collapse
ClockworkMod - makes a custom recovery, along with many other programs and apps, that makes flashing custom rom's and kernels much easier. Add Clockwork Recovery to your phone and you can load any custom rom or kernel you want by simply booting into recovery. Instructions to install it on your phone are in the OP (original post) of the clockwork recovery thread.
Andromeda - It is a group of custom programs noobnl has made. He made a custom kernel (this overclocks (makes faster) your cpu and undervolts (adds battery life)). His kernel also installs rom manager and super user to make make rooting more functional. Noobnl also has an andromeda rom that modifies touchwiz to be a little different with some different features. In both cases read the OP of the two threads and you will find easy installation instructions (using clockworkmod recovery) and a description of what they both do.
Aosp Magic and Tha Boss - These are both custom roms that in some way change how your phone looks and functions. Custom roms are all just ways to personalize your phone. For the most part they all install easily with clockwork recovery. Read the OP of any rom and it tells what they have done, what they do with each update, and how to install it.
Not trying to be mean or anything, but reading the OP pretty much always explains everything. I have only been doing this since they epic came out and have just learned by trying things out. It is very difficult to fully brick your phone. Most the time if you can't get your phone to work you can use Odin (see the thread for more info) to flash back to stock and start over.
Just my two cents but people who are pushed away isn't a bad thing. If they don't know what they are doing they don't need to be doing this. There are several terminology threads on this site...pushing them away means a lot less clutter in the dev threads and else where. Not that I'm saying they shouldn't be here at all, but read read read read....read....and then read some more. And if all else fails bash it with a hammer and turn it in on insurance.
Sent from my SPH-D700 using XDA App
See, its hard to really complain on this because some people are doing some cool stuff on their own effort and time, but I will agree with the OP on this. I agree that only a few lines of descriptions would not only help new users but cut a LOT of threads and posts from people interested but unsure of what do or what something is. And in fairness, it sounds pretty bad when u say that if people aren't that familiar with stuff they shouldn't try it. We don't all know everything and sometimes a little info goes a long way. But that's just my opinion.
Sent from my SPH-D700 using XDA App
Unfortunately if you can't search, read, and understand all the info that is posted you'll have only one option to customize your phone...Sprint ID(which will cost you $$). I've found that none of the processes, such as rooting or flashing kernels, are difficult to perform. In fact sometimes the amount of information already provided becomes confusing to some. I understand the issue devs have with the clutter in this section of the forum. Maybe mods can help by moving topics to the general section and maybe preserving the cleanliness of this section. On the other hand, why all the rage against people asking questions? If I'm not mistaken everyone isn't magically born with all the knowledge required to customize their phone. That's why there are forums like these to provide a community where people seeking knowledge can find it. Personally I find the forums for any piece of hardware from my Directv box to my Epic to be absolutely the most valuable "manual" I can have. Its nice to rely on actual intelligent users for information and not a low paid csr with a script on the other end of the phone.
zetterwing said:
Unfortunately if you can't search, read, and understand all the info that is posted you'll have only one option to customize your phone...Sprint ID(which will cost you $$). I've found that none of the processes, such as rooting or flashing kernels, are difficult to perform. In fact sometimes the amount of information already provided becomes confusing to some. I understand the issue devs have with the clutter in this section of the forum. Maybe mods can help by moving topics to the general section and maybe preserving the cleanliness of this section. On the other hand, why all the rage against people asking questions? If I'm not mistaken everyone isn't magically born with all the knowledge required to customize their phone. That's why there are forums like these to provide a community where people seeking knowledge can find it. Personally I find the forums for any piece of hardware from my Directv box to my Epic to be absolutely the most valuable "manual" I can have. Its nice to rely on actual intelligent users for information and not a low paid csr with a script on the other end of the phone.
Click to expand...
Click to collapse
no problem with the questions, it's just where it's being asked is the problem. People don't think their question will be answered if asked in the general section, or the thread that relates to their problem and decides... I'll just post in the dev section.. there's smart people in that forum!
I've seen it more than once, people don't want to search, or research... or read.. they want to ask a question and have someone answer it directly without having to dig back through posts that don't relate to the question they're asking. Like I said I seen it more than once and the mentality is easy to pick up on.
Don't worry I'm on your side. I've just seen some pretty rough treatment of someone asking a question...in this forum actually(not this thread). They were posting in the wrong place but there's a better way to direct someone to the right place than to berate them. That being said go to the Search and type in "root my phone" without quotes and THIS thread shows up higher in the list than one-click-root. Tends to throw people off the search function. I know it's a faulty way of searching but it's the way people do things. Many forums have problems with their search though. A google search for root Epic 4g has similar problems...the top results link to outdated information and the one click is halfway down the page.
People don't always read the rules of a forum either...it's just human nature. At least the people that make it here are finding the smartest people to answer their questions
Thread moved to General. Please stop flaming the OP.

Devs, Please don't hide your Known Issues

I really don't want this to come across wrong, but I just have to say it.
Developers, I appreciate all your hard work. I understand this is all beta/test/etc. I understand it is free of cost, even to those who did donate to one dev or another. You do it because you want to, not because you have to.
But please, for the love of all that's good - keep an updated list of Known Issues!
It sucks having to read 50 pages of posts to try to figure out if a particular release is reliable or not, to find out if there's a key feature broken or buggy. What makes it worse is you can't tell when reading these threads which users are on which release, because many still post issues after they've been resolved. Others post things that aren't really "issues" but user error.
You know what your issues are, you read the threads and you fix the issues. But trying to find a decent rom to flash is very, very difficult when your OP says "No known problems" and the thread that follows show that to be very untrue. It generates a lot of extra posts with people posting things you already know about, and it generates a lot of bad will when someone flashes something only to find that there are a number of game breaking issues.
All it takes is to update a post, say #2, in your thread, with KNOWN ISSUES. Once you confirm a bug, whether you intend to fix it on your next release or not, add it to that thread. It helps you, as a dev keep track of the bug, and it helps potential downloaders know what bugs have been confirmed and make an educated decision as to whether they want to install your release.
Hiding known issues is something I don't think anyone does intentionally, but it feels that way sometimes. It feels like devs are in a popularity contest, and any admission of flaws in their particular ROM is a weakness. Well, to tell the truth, I and many others are sick of installing something that was CLAIMED to be working perfectly, only to have glaring problems that have been there for many versions.
For a civil and productive development community. Please. Be honest with your known issues. It will go a long way in building trust with the people who you're providing ROMs to, and will mean fewer posts for YOU to wade through of users reporting known issues, without having read 500 posts first.
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
They don't care to list them. It's beneath some of them.
Maybe AirBus should list "midair exploding engines" as a known issue too...
kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
Click to expand...
Click to collapse
+1. Hell, at work I run a $100,000.00+ software suite and even that company won't do what the OP suggests!
If you have a problem with them stop using their roms go back to stock and see how much better theirs is even with a few bugs, not one of you has any right to complain. They do damn good work for free with some donations that do not come close to what they should be paid for it but they do not whine at all.
The problem I find is the "spammy" and useless comments average and pretentious users make which is both hard for the developer and the end user to read the threads. A dev releases a ROM and there is a guaranteed "Oh I can't wait to flash this" comment that will pop up. And there are some issues that are minor and are sometimes not related to the release that are posted and some pretentious loser who extends his ego by trying to make simple matters complicated. This forum didn't much of this problem before and I could quickly flash ROMs easily since I could clearly grasp the status on the ROM project.
I wish they would start a new thread with new releases. It's a pain to try to read through a 500 page thread, and you comments about this or that, and you have no idea which version the person is talking about. I gave up on custom roms and just using the leaked tmo 2.2, thanks for that Eugene
kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
Click to expand...
Click to collapse
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Update: Here is the link for the WIKI page.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
swehes said:
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Click to expand...
Click to collapse
You are in a heap of trouble, a lot of people don't read, and you are gonna get 1000000000000000000000000000000000000000000000 repeats of the same issue.
"OMG! MY SD CAR DONES"T MOUNT< HELP ME!11!!111"
chui101 said:
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
Click to expand...
Click to collapse
The issue here is really that a forum is not the ideal place to manage software releases. A list of bugs emerges from community testing, but there's nowhere to "post" that list of issues, or attach it to a specific release. Since there's no way for the community to add such documentation, it falls on the ROM builder, who probably has other priorities.
This kind of project could be well served by using a real software project management software solution, such as say google code, which has an issue tracker and other useful features. But XDA does already give us a better tool than the forum - the XDA wiki!
I wish people would use the XDA wiki more extensively. This would be a good place to keep updated documentation such as this, without requiring the OP to keep a forum post updated with the latest findings. All the OP needs to do is link to the wiki page, and other people can help maintain it.
OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
swehes said:
OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
Click to expand...
Click to collapse
Depends on the project. The Linux kernel is GPLv2, so any kernels fall under that license. AOSP as a whole uses both GPL and apache code.
The issue with ROMs is that unless they're AOSP derived (like cyanogenmod) they often include binaries for which the license situation is murky at best, so google code isn't really an ideal fit for a "ROM" that's only ever released as a binary.
Really I was throwing google code out there as a well known example, there are tons of other ways to track issues. There are dedicated issue tracking systems such as trac, bugzilla, etc, but they require hosting. Most of the freely available hosted services require that you're running an open source project, which isn't necessarily true for the ROMs here.
IMO a serious project could very well benefit from such tools, but just using an XDA wiki page which community members can freely update is a great first step.
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.
Stargazer3777 said:
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.
Click to expand...
Click to collapse
Thanks. On both accounts.
Maybe this should be a post to Microsoft
To quote "there are known, unknowns and unknown, knowns and and even sometimes unknown,unknowns............but.........
Developers ----develop they do not become a bookkeeper of their development.........that is coordinating work...........good luck getting any developer in ANY Specialty to do that............. reporting bugs........
---Maybe this should be a post to Microsoft---
N8ter said:
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
Click to expand...
Click to collapse
I have yet to see a REAL (completely dead) "bricked" vibrant from flashing a released Rom alone. I have seen a lot of user error cause boot loops or "soft-bricks" & HWL phones become unflashable because the end user didn't take the time to research though. As far as devs being "lazy" I dont really see that when the developer is coming here for us to tell him what else we find wrong. They are coding, you flash, you report back with a logcat. This is how development is made to my understanding. If ppl are to lazy to JUST do this then why shouldn't the developer discount long winded post or something they are not experiencing? If they know there is a bug its in the OP.
If you guys can change the interwebz & how 500 post per update are made completely useless please feel free to do so....
swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
I think it's a pretty awesome start for sure
As a matter of personal taste, I think having an individual wiki page per ROM (with the known issues and other detailed info) might be nice, although I'm not sure what the policy on new pages is with the XDA wiki.
Speaking from professional experience, the most challenging aspect of any documentation system is always convincing people to use it. It's great to compile the information, but unless ROM builders and devs post a link to the wiki in the forum threads nobody will ever see it. Having good, community based documentation is a benefit to everybody though, so hopefully people will recognize the utility of it and encourage its growth!

Kasionate daily update

This thread created in order to keep community informed on Kaoscinate development progress. Please DO NOT POST HERE.
I will try to come up with some sort of format short and informative enough to general public, so people do not need to go to IRC, tweeter or other means to gather information.
Would be cool is admin can make it sticky. And also correct spelling in title :-(
Q. What is Kaoscinate?
A. This rom is CM6 for the Verizon Fascinates, its Froyo based on the CyanogenMOD codebase. It is not GB.
Q. Where I can find more information.
A. Punkkaos twitter is main source of information.
Q. Is there other threads on this topic?
A. Yes.
Thread created by Kaos.
Kaoscinate BUG list in development.
Q. What is the reason of this thread existence?
A. I would like to keep newcomers and inexperienced users informed to reduce burden on developers. I will try to do daily updates and provide some additional information up to what is mentioned in Kaos twits if possible.
Q. Where I can find kaoscinate source code.
A. Kaos git.
Q. Where I can download binaries?
A. Download links available at the head of that thread.
Q. I'm excited about this particular development! Where I can donate?
A. One can donate here
Q. What is the current state of development?
A. It is ALPHA version. A lot of stuff doesn't work! See this thread on daily progress. Do not try it at home if you do not understand what are you doing. It might brick your phone.
01.14.11
V2 is up. It has working lock screen, headphones. Kaos reported some problems with JIT, so do not turn it on.
Search for Wi-Fi access point doesn't work yet.
01.15.11
Bluetooth is pairing but doesn't work with headset. Kaos says that it is some issues with RFCOMM
01.17.11
Work goes on. System is able to obtain IP address and it is verifiable in shell. However Android framework is not aware that network is properly configured. DHCP is to blame. Also Kaos has some issues with RFS (which is Samsung proprietary file system), but he is aware of the problem and work on fixing it.
01.18.11
Wi-Fi is working. Camera work in progress. v3 is coming?
Is Kaos' thread about it not enough? We need more than one place to look for new updates?
There is a bug thread and a Kaos thread, why do we need another one?
There seems to be plenty of info on xda already in regards to what kaos is doing and what his progress is....seems redundant to me
+1 to previous posts, but good effort
Let me continue some time. Let people have some choice. I'll try to provide links to educational resources and my goal to create high level picture of effort. Development thread might be used for bug postings etc.

Dev Issues, rom prefrences?

Hey guys and gals,
Just wanted to know if you have Dev rom issues with them working for a while then all of a sudden it either FC on you with super user or installing apps. I have to this point, had a lot of problems with the roms at times. Even when i change the write permissions I've had issues through CWM. I support all the Devs here to making and updating ROMS for the best phone that Tmo has at this point.
Another question is what is the LONGEST rom you have used and had it work for longer than 3+ months? Not only a stable release but a great kernal for batt life and efficient app/program running you have come across? This thread is in no way to put Devs against each other but more to learn on the strengths/weaknesses the MT4G (Glacier) has and how to deal with such issues.
Personally, I feel that all the devs can make a "same export file" for the contacts list instead of gumming up your sd card full of contact info with multiple vcf files of the sort.
One more issue i have is the Super user not being able to update in accordance with the other files on the rom/Device itself, and yet running smoothly without it FC on the rom i'm currently running, which at this time is "Beat Sense".
Do any of you have the same issues as I do or is it just me? Please let me know what you think of this thread and post your finds and issues, both positive and negative. Thanks.
jay4mont78 said:
Hey guys and gals,
Just wanted to know if you have Dev rom issues with them working for a while then all of a sudden it either FC on you with super user or installing apps. I have to this point, had a lot of problems with the roms at times. Even when i change the write permissions I've had issues through CWM. I support all the Devs here to making and updating ROMS for the best phone that Tmo has at this point.
Another question is what is the LONGEST rom you have used and had it work for longer than 3+ months? Not only a stable release but a great kernal for batt life and efficient app/program running you have come across? This thread is in no way to put Devs against each other but more to learn on the strengths/weaknesses the MT4G (Glacier) has and how to deal with such issues.
Personally, I feel that all the devs can make a "same export file" for the contacts list instead of gumming up your sd card full of contact info with multiple vcf files of the sort.
One more issue i have is the Super user not being able to update in accordance with the other files on the rom/Device itself, and yet running smoothly without it FC on the rom i'm currently running, which at this time is "Beat Sense".
Do any of you have the same issues as I do or is it just me? Please let me know what you think of this thread and post your finds and issues, both positive and negative. Thanks.
Click to expand...
Click to collapse
Questions belong in the Q & A section. Thank You.
http://forum.xda-developers.com/sho...Section**Thread Deleted/Locked Please Read **
A member since 2010 should know this.
Sent from my HTC Glacier using Tapatalk
sckboy78 said:
http://forum.xda-developers.com/sho...Section**Thread Deleted/Locked Please Read **
A member since 2010 should know this.
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
What he said....
If I helped, give thanks, if you please.
Sent from my fist to your nuts, enjoy!
jay4mont78 said:
Hey guys and gals,
Just wanted to know if you have Dev rom issues with them working for a while then all of a sudden it either FC on you with super user or installing apps. I have to this point, had a lot of problems with the roms at times. Even when i change the write permissions I've had issues through CWM. I support all the Devs here to making and updating ROMS for the best phone that Tmo has at this point.
Another question is what is the LONGEST rom you have used and had it work for longer than 3+ months? Not only a stable release but a great kernal for batt life and efficient app/program running you have come across? This thread is in no way to put Devs against each other but more to learn on the strengths/weaknesses the MT4G (Glacier) has and how to deal with such issues.
Personally, I feel that all the devs can make a "same export file" for the contacts list instead of gumming up your sd card full of contact info with multiple vcf files of the sort.
One more issue i have is the Super user not being able to update in accordance with the other files on the rom/Device itself, and yet running smoothly without it FC on the rom i'm currently running, which at this time is "Beat Sense".
Do any of you have the same issues as I do or is it just me? Please let me know what you think of this thread and post your finds and issues, both positive and negative. Thanks.
Click to expand...
Click to collapse
I've been modding since the G1 and one thing I've learned is to leave well enough alone. The ROM I'm using has been smooth for me for months, so much so that I don't bother to update it when new versions come out. A lot of times new versions post speed improvements or new features but if its not an entirely new ROM or something huge, I stick with what I've got. I dont mean to imply that the dev's put out bad builds but stuff happens. Could be my fault, could be a bad flash. There have been lots of times where ROMs work perfectly for me but others are having all sorts of problems.
What I'm saying is, find something that works for you and stick with it as long as you can.
Thread moved to Q&A.......

Rooted Lollipop, want to try Marshmallow.

Hey all, I've spent a couple hours sifting through these pages to find an answer I cannot see. Or, I'm not reading correctly.
I am currently running Jasmine Rom on my rooted/unlocked OF1 Note 3. After several months of everything working fine but slow here and there, I would like to try one of two things. If anyone has some insight (Google certainly doesn't ) that may or may not help me, I'd very much appreciate you...
1- Is unrooting as lollipo to update to marshmallow a good or bad idea? Why?
2- If good, could you point me to a page that I don't have to read 700 posts to find clear instructions to do so?
3- If bad, I will stick with what I have...BUT, I'd really like to get rid of the bloatware (permanently, if possible). Is this possible? NOTE: I've sifted through countless pages of safe to remove bloat, so I'm asking if there's a way to do this upon fresh rom installation?
4- I love this place. I've rooted many a phone with all of your help. I must say that this note 3 vzw section is a WRECK. How can non-devs possibly sort through all this to find working answers? I'm legit asking, not being a smartass...there's active threads from 1983, and how's a regular Joe who wants to play with his toys too supposed to make sense of the endless this-one-works no-it-doesn't mess?
I'm sincerely seeking some final, working answers to the above questions, any help would be appreciated. Thank you in advance.
There is no "update to marshmallow" AFAIK.
OF1 is Lolipop.
XDA has zero threshold to entry, so the postings here are from both geniuses and idiots. You get to sort through them.
Postings are made while the phones are in play - which is to say while stock firmware is changing constantly, and devs and hackers are making changes, revising their stuff and learning new tricks.
So in addition to info which is correct - and stays correct, there is also information that becomes incorrect with new software... or never was correct in the first place.
So yeah, XDA is a mess. But you are missing the point - that it's a hot mess.
Your expectation of perfectly curated data, 100% correct and up-to-date instructions that minimize your time (at the expense of others, naturally) is unreasonable for this simple reason: it doesn't exist anywhere else.
So... step up or step out.
All this stuff is optional behavior. If you don't have time for it, well... then you don't have time for it.
If you want to try marshmallow on your device flash this rom using TWRP : [ROM][CM13][6.0.1_r43][VZW][OTA-Updates] Temasek's UNOFFICIAL.
I'm using version V10.8 on my unlocked OF1 Note 3 and everything works, here is the thread: http://forum.xda-developers.com/ver...opment/rom-temaseks-unofficial-build-t3364382
bftb0 said:
There is no "update to marshmallow" AFAIK.
OF1 is Lolipop.
XDA has zero threshold to entry, so the postings here are from both geniuses and idiots. You get to sort through them.
Postings are made while the phones are in play - which is to say while stock firmware is changing constantly, and devs and hackers are making changes, revising their stuff and learning new tricks.
So in addition to info which is correct - and stays correct, there is also information that becomes incorrect with new software... or never was correct in the first place.
So yeah, XDA is a mess. But you are missing the point - that it's a hot mess.
Your expectation of perfectly curated data, 100% correct and up-to-date instructions that minimize your time (at the expense of others, naturally) is unreasonable for this simple reason: it doesn't exist anywhere else.
So... step up or step out.
All this stuff is optional behavior. If you don't have time for it, well... then you don't have time for it.
Click to expand...
Click to collapse
Thank you for the reply. I must say, though, there's a clear difference between everything being perfectly organized to my taste and organized for the everyman who doesn't have all day to sort through everything in the forum on a particular phone. Im not demanding anything, nor am I accusing anyone of laziness or ignorance. There's wasn't anything implying anyone should do anything. Rather, a question was posed to understand the processes. I get the point of this forum, and more to the point, I APPRECIATE this forum. But I will say that at some point clean up might be a good idea. That's an opinion, not a demand. It is silly to me how unkempt this PARTICULAR part of XDA is.
That said, I will continue to use it happily, messy, hot, or otherwise, and I appreciate everyone's work on these devices for the everyman to experience the full range of possibilities with our devices.
Thanks for the answers.
aaroon200 said:
If you want to try marshmallow on your device flash this rom using TWRP : [ROM][CM13][6.0.1_r43][VZW][OTA-Updates] Temasek's UNOFFICIAL.
I'm using version V10.8 on my unlocked OF1 Note 3 and everything works, here is the thread: http://forum.xda-developers.com/ver...opment/rom-temaseks-unofficial-build-t3364382
Click to expand...
Click to collapse
Awesome, I will check out it.
Forgive my tone on my original post, XDA. I believe I came across as *****y, and I didn't mean any offense.

Categories

Resources