Hi everyone
I would like to present you, in compliance with forum rules (paragraph 11), project that I started more than a year ago, when wallpapers suited for tablet computers practically didnt exist, and I would like your feedback (do you like it, what to change, and most importantly does it work for your tablet,...)
Website/application can be found at tabletwallpapers.org , or specifically for Nexus 7: tabletwallpapers.org/google-nexus-7-wallpapers/
Website was designed specially for each tablet device, so every image was hand-edited to suite screen resolution of "any" given tablet device. After you choose your device, website will show only relevant wallpapers and backgrounds, and website will offer download in best resolution for detected device.
I hope you like it, and hope to hear some feedback from you. Thanks.
Related
Hi,
I would like to request a feature which I think would be real help either on XDA-developers.com or wiki.xda-developers.com[
There is an excellent matrix of differences between the different HTC models & the names different phone providers give them.
I've tried using searching terms like 'comparison' or 'differences' (between XDA's) to find it, but the search engine does not seem to be speaking my language.
1.
I think having a better main page hotlink to such a comparison Matrix would be REALLy helpful, PARTICULARLY as the matrix is (hopefully) updated regularly and has lots of hotlinks to the various models.
2.
The second request is to somehow display details in a list of phones as they are released so that I can see whether the XDA I'm waiting for (or similar) has been released.
Thanks for an EXCELLENT site
This is a short summary of some important general points for posting new ROM's.
It should be considered as an optional "add-on" to the general thread:
"Galaxy S I9000 Android Development **STICKY THREAD** Read here first!"
The number of man hours spent working and developing new custom ROMs are astronomical! So why then, is it that so few new ROMs are successful? Basically because of lack of information and poor public visibility/involvement of the developers themselves. It's just like in any other successful business, you have to make your product or service stand out from the rest. Either by making an amazing product or by being a great inspiration for others to follow. Here I will try to explain and list some fundamental ideas, in order to make your ROM better and more popular.
When a would be ROM flasher is looking around for a new ROM, he searches the web and the XDA-forums for threads, usually beginning with the text "[ROM]". Next he/she look at the FIRST page where the developer (and his/her team) is presenting the various features of their new design. What is presented there will often be a decision maker for whether or not someone wants to try it out.
There are a few things that consistently differs between "good" ROMs and "bad/poor" ROM's. These things are often and naturally related to the amount of information available around the ROM in question. Someone who have put down enough mind, sweat and hart into the production (cooking) of a ROM, would also like to share his/her effort in the best possible way, not minding writing a detailed and useful description about their product. The items found below are part of some of these things that do MAKE A DIFFERENCE.
- Primary Purpose:
Essentially a description why you want to provide this ROM and why you think it is needed. What are the main features and driving forces for providing this ROM?
- Ultimate Gaming Experience
- Super stability
- Super Compatibility
- Great Battery Duration
- Minimalistic User Interface (UI)
- Simple to use functionality
- Latest and coolest never seen before interface behavior
- Fully loaded with ultimate editions of absolutely everything
- Mobile Penetration Testing Platform
- or perhaps just for educational or experimental purposes etc...
- Up-to-date Maintenance:
That means an active developer (or group of) who are readily available to answer questions from users of all levels, new or advanced! Often that they should be inhumanly available at all times of the day & night!
- Up-to-date Firmware Release:
That means the the source of your ROM is preferably based on the latest, but publicly available code/firmware. Not on some hidden leaks or old hacked code. When I say "hidden leaks" here, I mean the kind where the origin of the code (compiled or not) cannot be verified or downloaded. (BMW doesn't make car/sales advertisements using 2 year old engines from unknown/secret sources!)
- Detailed CHANGE-LOG:
People want to know that what they flash on their phones, is as close as possible to what they would like to see and use. Also from a paranoia perspective most of us would like to know that it doesn't contain 3rd party or other strange applications that we will never use, or which will give us trouble when we want to add/update applications, at a later time. A description of the various applications is also very useful. Most people would wonder what the "DarkBotSendHelper.apk" is doing on a phone.
A change-log would ideally consist of a list with:
- Title: Change Date and the custom ROM Version the changes apply to
- Full application name
- Full application version
- Short application description
- Link to application source-code, if available
- Link to application on "Android Market"
- Reference to what hacks has been made, if any
- Reason for why the hack is needed
- Unresolved BUG-LOG:
A brief log of bugs and unresolved issues that affects the current release. It is hard to explain without cussing how annoying it is to flash a new ROM, just to find out that some WiFi issue has not yet been resolved, which was posted on page 456/1200! If people post bugs/issues, that cannot be immediately resolved, please add those issues to the BUG-LOG, on the front page.
- Screen Shots! Updated Screen Shots!
The importance of good screen shots can never be enough emphasized! Many ROMs are updated continuously and if the screen-shots doesn't match what the user installs, he's gonna go WTF!, and will start to peppering your support threads with questions about how to install this and that, and how to get the same themes you are using in those screenshots, or from another different ROM altogether! You wouldn't be able to sell a new BMW with a picture of an old Volvo, would you? So why do you think a ROM would be any different? Also include a brief caption about the essential feature(s) shown, for each picture.
- Detailed Installation Instructions
This hardly need more explanation apart for making sure you also say something about:
- WIPE/No-WIPE
- Bootloader Requirements
- Recommended Procedure
- Detailed Device Compatibility List
Yes, the same gross model name/number of a particular device, may very well have some minor variations that can render the device completely incompatible with software from it's apparent twin-brother. Or even certain Firmwares may not be compatible to slight manufacturing variation. See for example the "Samsung Galaxy S" with their sub-models GT-I9000(B/M/T), and to complicate things further, even within the same model there may be slight differences, like in the PCB of the USB-port of the SGS2 GT-I9100.
- Detailed Language Compatibility
What do people use their phones for? Communication! Sure, some use them as a game pad, but after all it is primarily a browsing and communication device. So if you can't use your primary languages with your device, it is useless! Although some network operators are only beginning to understand that most of the connected world is at least bi-lingual and often much more. Thus it is of essence that your phone's keyboard, screen-reader and web-browser can read, display and understand most characters and alphabets around. (I.e. I still fail to understand why it is virtually impossible to find a phone with Russian, English, Spanish and Norwegian keyboard layouts/character sets or at least let me select these my self!) In addition it is very confusing for a first-time ROM flasher to understand the need for all the various PDA/PHONE and CSC region settings, which are often modified and re-packaged for a well cooked ROM, and thus no longer adhere to the original regional code.
So when you cook your ROM, please provide as much information as possible regarding how the user can adapt their phone to his/her own languages. This information includes at least:
- What languages are available for basic operation (the operating system)
- What languages are available for the keyboard mappings
- What keyboard applications can use these languages (Swype, Samsung Keyboard etc.)
- Simple instructions how to include, use and set the phone languages
- List of Technical Terms and Definitions that describe the ROM
The world of mobile device development is packed by technical jargon and abbreviated terms. Many times they are also abbreviated and used in the wrong context, although some the community know what it means. Simplify your vocabulary and clearly define your terms and stay with community standard ones!
- General Presentation
Like any other business presentation, please skip the HUGE fonts in a zillion colors. Most of us are neither blind nor illiterate, but you may risk to come across as being both, with those type of fonts. Remember "KISS"? - Keep It Simple Stupid.
- SPELL CHECK!!
It's embarrassing and very annoying to read descriptions of how great, professional and how well maintained a particular ROM is, when the text is riddled with misspellings, wrong words and childish grammatical errors. Although most of us are very understanding that we are living in a multicultural and multilingual society, sometimes all I think about is, how a person who doesn't know how to spell check, could ever be able to cook a mobile phone ROM. Most text editors feature at least some basic spell checking, bloody hell, USE IT!
- CREDITS
Most of the Android development community is completely driven by voluntary and open source work. Make sure to include the correct credits to those persons who have contributed to the various info/hacks/software that you include in your ROM. Use a separate list for the credits, that include the name (handle) and how/what he/she did to contribute.
2 Good Examples:
http://forum.xda-developers.com/showthread.php?t=1350763
http://forum.xda-developers.com/showthread.php?t=1155776
Final Words:
It is very likely I have missed something here, or that you (as a developer or moderator) disagree on something I have written here, if so, please provide your constructive comments how I can improve this list and post.
In Great Expectations and Hope for Many New Amazing ROMs!
- E:V:A -
PS. This was posted in the "Developer Section" as it applies only to new ROM development threads, and I wouldn't consider this neither as "Q/A" nor "General". But if OP/MOD know of a better suited place, please just move it there...
Also I am not aware of a similar post to this one, even after searching XDA quite a lot. So if it already exists, it is not easy to find and should be reposted or stickied!
<Reserved>
@E:V:A
The only thing that I missed so far is a thread like yours.
Agree on all requirements of released software.
Sometimes I wonder how some "devs" priorities are stacked regarding quality control vs. early delivery on pay-per-download sites.
Not sure what is best place for this thread. Counting # of posts in General asking Q already answered in stickies, it's kind of accepted to skip reading what's there. :-\
Perhaps keep it alive as hottest thread here?
Tapatalked - There's a Thanks button somewhere
I like this
One thing you must add while promoting your ROM.. That is CREDITS.
Rahulrulez said:
I like this
One thing you must add while promoting your ROM.. That is CREDITS.
Click to expand...
Click to collapse
YES! Not giving credit where due is horrible, basically just forgetting all the hard work another individual has put in to the "feature" of your ROM. Also, this should probably be in general.
Hello.
Recently I made a remote control solution which can control your Android-based phone on PC. Server runs on Windows-based PC only for now. (Server is based on MFC) Client(Your phone) should able to get root permission.
We verified this solution works on Galaxy S, Galaxy S2, Galaxy Note. But not yet tested on the other devices due to lack of devices.
If you have interests controlling your phone on PC, please check this out and leave us feedback. If you are willing to make this project better, feel free contact to us. Remoteroid will get better than ever, with your supports and contribution.
Project site:
- Since I'm new user to XDA, I can't leave URL for project page.
just google 'remoteroid'! (remoteroid on Google Code)
Brief build instructions (For client):
Checkout both 'ActionbarSherlockLib' and 'android' into your workspace, make sure Android 4.0.3 System image exists on your system and latest ADT has installed.
Once all prerequisites are fulfilled, just press 'Run' button on Eclipse to install Remoteroid on your phone.
Please test on Galaxy Nexus for us. If not working I will request this thread be taken down.
Thank You.
Bro, your post should be in the Android Apps and Games or Android Software Development. There is nothing Galaxy Nexus specific in your product or post.
Hey guys! I was paging through the forums and had what could be an awesome idea. I'm by no means a aerospace engineer nor a computer scientist, but I was trying to figure out how hard it would be to take a standalone Attitude and Heading Reference System (AHRS) system like the iLevil 3 Sport, and display it on something like the EPSON BT-300. Im sure it would have to be a simplified display, but in theory couldn't we get something like a fighter jet HUD directly in front of your face?!
The reason I have chosen these two pieces of hardware (iLevil 3 Sport and EPSON BT-300) is to try and simplify the problem at hand. Through programs like ixGyro, AHRS Utility by iLevil, and Xavion, to name a few (all of which are compatible with the iLevel, and available to download directly to any Android system), you already have all of the information in tablet form.
The AHRS device has all of the hardware required and outputs the information via WiFi. These programs have already proven that this information can be successfully displayed. It seems as through that the only problem now is the GUI. I don't have either of these two products so I can't say for certain, but I'm willing to bet that the BT-300, running Android 5.1, can display this information almost the exact same as on your phone or tablet! I propose that we simply delete the background so you have a true augmented reality while you fly!
Hello, guys:
I used the official bottom package to make a rom. I don't know whether you like it. If you don't like it, please go out and turn left. If you don't want to see me, please delete my post. Thank you. But if you are interested, please continue to look.
First of all, it is not a so-called os. Because I do not have that ability, it is only a rom modified through the official system. So if you don't like it, please turn left. If you do not want to see me, please delete my post, thank you.
Disclaimer: All patches for the camera were not developed by me. Later on, I will list all the perfect developers on this list. Thank you.
Summary: 1. It is called Hand ui, not os. Thank you!
************2. Based on the official firmware, thank you!
************3, brush machine code is not written by me, thank you!
************4, Hand ui uses the lewa part of the code, thank you!
************5, brush Hand ui1.0 need your first line brush 205, thank you!
************6, it is just the rom of my hobbies and interests. Yes, you can modify the content inside. What do you love?
***********7, brush machine is a high-risk operation, which means that you have any risk in the writing process I do not bear, thank you!
*********8, you want to write Hand ui phone must unlock the BL, and brush a third-party recovery module, thank you!
*********9, although it is called Hand ui, but it is actually nothing, I just put everything that feels good together, nothing more! Thank you!
*******10, Hand ui built-in simple system upgrade program, can be upgraded later in use.
11. It supports the touch id similar to the iPhone, slide down the desktop icon.
12. Supports desktop with drawer and single-layer desktop mode, which can be adjusted in desktop settings.
13, carefully selected free application built-in rom (compass, calculator, flashlight, etc.).
14. Here, I assure you that Handui does not have any promotional applications or advertisements. There will not be any later. Including built-in applications and no advertisements, and even about nothing, feel free to use.
Related issues: Well, there are no bug issues at the moment. The camera works fine and does not require any patches. Thanks to russel5 for all this credit, of course I don't know who developed the dm patch. I would especially like to thank him if I knew it.
download
https:// mega.nz/
#F!67BAgIRR!jU9aa8GdVBQ8OhQIEw7P_Q
Acknowledgements:
names not listed in order:
Special thanks to russel5
Android x86 founder Huang Zhiwei
Yiming Technology
Jide remix os
Lewa
Oppo
M-rom
Peking University Yiming Software Center
Openthos
Screenshots
https://
mega.nz/
#F!bqpxhRIb!iid5eg0GZqowKdScfTbp8g
Interesting, which languages are available ?
It supports global languages because I am Chinese, so I am sorry for the Chinese language of my screenshots.：牛仔：;）
thx for the info.
It looks nearly like miui from xiaomi.
the most western aosp designs looks most like default android look and feel and this is very different from them.
if TWRP backups and restore would work, I would give it a test.
is root possible, and works substratum with the interesting ui?
Zhiyoo fans come to support !:highfive:
At startup after installation there is no keyboard, only voice input
installed a gaps keyboard did not appear
set the keyboard separately (via TRWP) the keyboard does not appear at startup
Unable to log into the account at startup, it's impossible to create a new one ...
What are the ideas?
@wsprh123 Can you pls upload screenshots of it here I can't seem to find any
niubility