Hi guys and girls Ok well i've been lurking around on these forums for some time now. Recently I rooted my Nexus 5 and I must say I love it! I'm aiming to make this thread somewhat of a one stop for people who have just rooted or are considering rooting to see what is possible once you root your phone!
Alright so first things first, before you go any further you are going to need:
A rooted Nexus 5!
A fair amount of time.
if you are unsure of how to go about doing this please read through this thread made by the wonderful Chromium_:
http://forum.xda-developers.com/showthread.php?t=2507905
OK, so from this point on i'm going to assume you have all the requisites you need so lets get into it shall we
Block adverts while browsing the web.
So i'm pretty sure that most of us have been blocking those frustrating pop ups and banner adverts while browsing the web on our PCs or Macs for years now right? (Yes, I am looking at you Mr. 888 Poker! ) But for some reason this is not possible to do on our phones. Not anymore! With your rooted phone you can install the superb adaway and wave those adverts goodbye!
Adaway is not however available from the playstore. Don't fear though you can get it here!
http://forum.xda-developers.com/showthread.php?t=2190753
NB: If for some reason you are not currently blocking ads on your PC or Mac. I recommend the add on - adblockplus.
https://adblockplus.org
Install custom Lockrings, softkeys and more.
Bored of the standard android lockscreen? Don't want to have to mess around with apps such as widgetlocker which often prove to be quite unstable at times? Now you don't have to!
Check out this thread created by matthew0776
http://forum.xda-developers.com/showthread.php?t=2514238
With the files included in that thread you can have whatever look you could possibly want! As the thread states however, in order to flash them on your device you will need the application ZipThemer.
ZipThemer is a simple enough application to use and is available from the playstore.
https://play.google.com/store/apps/details?id=kellinwood.zipthemer
In order to use ZipThemer the steps are as follows:
1) Open the ZipThemer application and press Update Edify, you will find this in the drop down menu which appears when you press the 3 dots in the top corner of the right hand side of the screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Once you press Update Edify you should be greeted with this screen:
3) Press 'Browse'
4) Select the firmware file you are currently using. It could be called, for example, pa_hammerhead-4.0-BETA6-20140217.zip
5) Press 'Configure' A message at the bottom of the screen should pop up at this point which says 'success'.
6) Press the back key once. You should end up at this screen:
7) Once at the screen above press '+Theme' You should then be presented with this screen:
8) Press the green back arrow on the screen above and browse to the location of your lockring/sofkey .zip file you downloaded and placed on your device earlier.
9) Press 'Build It!' and make sure you select the option to make a backup/undo so you can always switch back to stock easily or if there is any issues.
10) Boot device into recovery (CWM or TWRP) Select install Zip from SD card and install it! You will find your file in the root of your SD card for easy access.
ZipThemer not working? Don't worry all hope is not lost! The method above works for the vast majority but if you are one of the unfortunate few there is a solution!
Follow the steps above as usual but when you get to step #4 (Browse for firmware file) Select this file:
http://d-h.st/CgG
Instead of whatever firmware file you are currently running on your device.
Again all credit goes to matthew0776 here. I have simply tried to rephrase the instructions he provided in the thread here:
http://forum.xda-developers.com/showpost.php?p=39572221&postcount=18&nocache=1&z=5376182028558105
To make them easier to understand
Change your boot animation.
Alright so did you know now that you've rooted your phone you can change the boot animation to whatever you like? Well you can! And below i'm going to try my best to explain how.
Ok, now there are a few ways to do this. Personally I like to do things manually however so that's the way i'm going to demonstrate here. If however you don't fancy doing the legwork yourself though (and don't mind paying a small sum) I am aware of a option in the awesome ROM Toolbox pro which does pretty much the same thing. You can get ROM Toolbox pro from the playstore here:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
So, you've decided to stick with me then?! Alright cool, well here is how to do it the good old fashioned way then
You will need:
Root Explorer: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
A custom boot animation: http://forum.xda-developers.com/showthread.php?t=2577081 (Thanks to thor6577)
1) Open Root Explorer and navigate your way to: system/media.
2) Here you will find a file called bootanimation.zip Select this file (press the tick to the right of it) and rename it. To do this press the 3 dots in the top corner of the right hand side of the screen once you have selected it and press 'Rename' You may be greeted with a warning at this stage asking if you wish to change the file system from read-only to read-write the answer is YES.
3) Rename the file to bottanimation.zip1 . This is essentially making a backup
4) Browse to wherever you have saved your new custom boot animation and copy it over to this directory (system/media)
NOTE: Your custom boot animation MUST BE called bootanimation.zip or it will not work.
5) Reboot and enjoy
Change your LCD screen density.
The Nexus 5 has absolutely gorgeous 5" display but in my opinion it does not make the most of it out the box! With a rooted phone however you can change the LCD density of the screen to whatever you like!
In simple terms changing the density effects how large icons and widgets will appear on your screen. This means the lower the density the more you can fit on one screen
Changing the screen density on a rooted phone is an incredibly simple Build.prop tweak. Certain custom ROMs come with this feature already nicely packaged into the ROM for example the ROM I am using AOSB 1.3.1 does.
http://forum.xda-developers.com/showthread.php?t=2615590
But, if your ROM doesn't or you have decided to stay on stock don't worry To change you LCD Density follow the steps below:
1) Open Root Explorer and navigate your way to system.
2) Select build.prop (Press the blue tick)
3) Click on the three dots on the top right of the screen and select 'Open in Text Editor' You may be greeted with a prompt here which 'WARNING' file system read-only, switch to read-write? (I'm paraphrasing) The answer is of course YES.
4) Find the entry ro.sf.LCD_density.
5) Change the number directly after the '=' to what you want the screen density to be. You can go anywhere from 300 - 480 before apps such as the Playstore start to break. Personally I use 340 dpi and I think its perfect, its all personal preference though
6) Press the three bars in the top right corner and select save changes.
7) Reboot your phone and enjoy
For more information on LCD density and discussion please check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517311
mmmm PIE!
PIE is a nice little feature you may have stumbled across browsing these forums. If you haven't already it looks like this:
Pretty cool right?! Well I thought so anyway. Well with your rooted phone now you can have it to Now there are two ways (which I know of) how you can get this. The first way is the simplest by far. Many ROMS come with this nice feature already installed. To find out if yours does just check out the features page. Often you don't even have to do that its actually written in the title of whatever ROM you are using. To check out all the custom ROMs available for the Nexus 5 on XDA check out these two forums:
http://forum.xda-developers.com/google-nexus-5/development
http://forum.xda-developers.com/google-nexus-5/orig-development
Now if your ROM does come with PIE baked into it. Your already all set, just go to your settings page and you will find the options for it in there. However if you are still running stock don't worry you can have PIE too thanks to noname81. To get it visit here:
http://forum.xda-developers.com/showthread.php?t=1330150
noname81's app couldn't be simpler to use either, simply download the latest build and place it somewhere easily accessible on your device, for example, Download. Then browse for it using whatever file manager you like (there's loads on the Playstore) however personally I like ES File manager the most if you just cant make your mind up. Its free and you can get it here:
https://play.google.com/store/apps/details?id=com.estrongs.android.pop
Once you've found it click on the apk and hit install.
NOTE: YOU MUST ALLOW INSTALLATION OF APPS FROM UNKNOWN SOURCES.
To do this:
1) Go to settings.
2) Scroll down to 'Personal' and press on 'Security'.
3) Scroll down to 'Device Administration'
4) Press the check box located to the right of the entry 'unknown sources'.
AppBar (Xposed Framework)
Ok, well the options really are somewhat limitless with this so i'm not going to go through all of them. Instead i'm just going to focus on one of my personal favorites, The AppBar. If you are wondering what AppBar is, it's a little feature which looks like this:
AppBar is not permanently on show like the picture above however. It simply slides into frame when you touch a certain area of the screen which you can personally set up to your liking (much like PIE above).
Ok, so i'm going to put in a slight warning here, in terms of actually installing the app, this one is slightly more work than the others I have mentioned. It's still nothing to challenging though, I promise!
To get AppBar. The first thing you are going to need to do is install the Xposed Framework. You can get it here:
http://repo.xposed.info/module/de.robv.android.xposed.installer
1) Once, you've installed the apk above you should be greeted with this screen (if you are not, navigate your way to it):
2) Once at the screen above, press Install/Update and let it do its thing.
3) Reboot phone.
4) Once you've rebooted, go back into the Xposed installer and press the tab on the top left of the screen.
5) Select 'Download' from the drop down menu which appears. You should be landed at this screen:
6) Scroll down until you find XBlast Tools and install the correct version for whatever version of android you are running.
7) Press on the entry and hit download.
8) Once it's finished you will get a notification which says something along the lines of 'Xposed module is not active yet'
9) Open your notification bar and press on the notification.
10) You will end up at this screen:
11) Press the check box to the right of XBlast Tools [1.8.0]
12) Reboot.
Once you've rebooted you should see a new icon in your app draw called XBlast Tools, open it.
1) Scroll down to the entry AppBar .
2) Enable it using the slider.
3) To set up what you want in you appbar content go to 'Setup Appbar content'
4) You will be taken to this screen:
5) Drag and drop apps into the bar on the left
6) You can adjust the trigger position, height, width and transparency using the sliders on the first screen.
Note: Thanks to femblack (Riyajudeen Mohamed yousuf) for XBlast tools if you which to support him you can buy XBlast tools from the Playstore here:
https://play.google.com/store/apps/details?id=ind.fem.black.xposed.mods
Flash a custom kernel.
NOTE: You must have a custom recovery installed (Dont have one? Check the top of this thread )
Ok, well there are quite a few reasons why to install a custom kernel. In short (very short) You can install a custom Kernel for one of these 3 reasons.
1) To improve battery life. (Undervolting)
2) To improve performance. (Overclocking)
3) Fancy features such as double tab screen to wake device (My personal favorite). Swipe across screen to sleep device etc etc.
Installing a custom kernel is actually remarkably easy especially thanks to the developers who have included AROMA installers. All you have to do is put the zip file on your SDcard boot into recovery and follow the on screen instructions.
For the purpose of this post i'm going to point you towards the ElementalX as it is the Kernel I am currently running and I have had no issues with it personally. it is also incredibly easy to set up and seems like it would serve as a good starting point for newcomers. You can find it here:
http://forum.xda-developers.com/showthread.php?t=2519607 (Thanks to flar2)
Please note that this is far from the only option when it comes to kernels its just the easiest in my opinion. if you want to see more kernels for the Nexus 5 and decide for yourself have a browse around this forum:
http://forum.xda-developers.com/google-nexus-5/orig-development
IMPORTANT: When flashing any custom kernel you must be sure you have the right build for whatever base you are running. Some ROMs are CM based others are AOSP based and so on. ALWAYS CHECK FIRST.
Thats it for now everyone! Hope this thread is of some use. Plan to add information on HALO and MultiWindow when possible as well as a few other things.
More to come!
[RESERVED
Quite nice thread for newcomers, and it might, as it grows, be a go-to for those of us who have been rooted for ages in case we forgot about some of the stuff we can do/achieve with root
One question though, why not use the features included in Rom Toolsbox Pro, since you're already using it. I has a root explorer, if you swipe once to the left in the main menu, you'll get to a Build.prop editor and one more swipe will bring you to the Boot Animations "switcher". Think about it
Nice thread, changing dpi is the first thing i do when i root, but I don't think its appropriate to call that "changing the screen resolution" , we are simply changing dpi, not resolution.
I like where this thread is going, thanks for your time just adding my support. I'm rooted. Flashed Faux Kernel but still stock. I'm still waiting for AOKP or Paranoid put out their hand even more.
Used to run carbon on my n4. But I'm just neat picky about by clock position, battery icon, toggles *torch, extended boot menu and Navbar. My main reasons I used custom ROMs.
Sent from my Nexus 5 using xda app-developers app
Gormsen said:
Quite nice thread for newcomers, and it might, as it grows, be a go-to for those of us who have been rooted for ages in case we forgot about some of the stuff we can do/achieve with root
One question though, why not use the features included in Rom Toolsbox Pro, since you're already using it. I has a root explorer, if you swipe once to the left in the main menu, you'll get to a Build.prop editor and one more swipe will bring you to the Boot Animations "switcher". Think about it
Click to expand...
Click to collapse
Honestly there is no real reason not to this, I just learnt how to do it the old fashioned way first and old habits and all that. Also the above method can be done for free using any root explorer whereas for ROM toolbox you have to pay. Also i've found that using ROM toolboxes boot animations are quite often not scaled to fit the screen properly!
Dakura said:
Nice thread, changing dpi is the first thing i do when i root, but I don't think its appropriate to call that "changing the screen resolution" , we are simply changing dpi, not resolution.
Click to expand...
Click to collapse
Thankyou, and yes you are correct, fixed it
Michael-1993 said:
Honestly there is no real reason not to this, I just learnt how to do it the old fashioned way first and old habits and all that. Also the above method can be done for free using any root explorer whereas for ROM toolbox you have to pay. Also i've found that using ROM toolboxes boot animations are quite often not scaled to fit the screen properly!
Thankyou, and yes you are correct, fixed it
Click to expand...
Click to collapse
I'm also a fan of doing things manually, so no arguing there
My though was that, when being a noob at all of this, there's a lot to handle, a lot of words and a lot of tools to use. Rom Toolbox gathers a lot of options in a single app, and might simplify things for the slow learning newcomer.
You could also teach him to set his kernel using scripts, but using an app like Trickster og System Tuner simplifies things, a lot!
Sent from my Nexus 5 using Tapatalk
Gormsen said:
I'm also a fan of doing things manually, so no arguing there
My though was that, when being a noob at all of this, there's a lot to handle, a lot of words and a lot of tools to use. Rom Toolbox gathers a lot of options in a single app, and might simplify things for the slow learning newcomer.
You could also teach him to set his kernel using scripts, but using an app like Trickster og System Tuner simplifies things, a lot!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
That's a great idea! Ill add it as soon as I get time
And yeah, you're right it is a lot to take in at first I suppose, I am trying my best to make the thread as simple as possible though I promise! i'm also planning on adding how to backup applications and accounts as well as how to dual boot multiple ROMS at some point. But yeah ROM Toolbox really is a a great tool. I may add a section dedicated just to the main features on that as well
Michael-1993 said:
That's a great idea! Ill add it as soon as I get time
And yeah, you're right it is a lot to take in at first I suppose, I am trying my best to make the thread as simple as possible though I promise! i'm also planning on adding how to backup applications and accounts as well as how to dual boot multiple ROMS at some point. But yeah ROM Toolbox really is a a great tool. I may add a section dedicated just to the main features on that as well
Click to expand...
Click to collapse
And you're doing a great job so, the OP has really grown a lot in just a couple of days.
A couple of suggestions:
1. You might wanna consider making an index, since this thread is going to grow a lot and it might end up being hard to get an overview.
2. How about a dedicated Xposed section since the possibilities with this are almost endless?
I know all of this takes time, so just get to it as you see fit. Keep up the good work
Sent from my Nexus 5 using Tapatalk
Hey Thanks for such informative thread, I subscribed to your thread and look forward to learn more.
I am interested in changing the DPI of my phone especially to the level that is on Samsung Note 2. This is purely because of the game 8 ball pool from Miniclip as the game looks different on Note 2 and different on N5. Do you have any idea what is the DPI of Note 2 v/s our phone.
Thanks.
kailashnj said:
Hey Thanks for such informative thread, I subscribed to your thread and look forward to learn more.
I am interested in changing the DPI of my phone especially to the level that is on Samsung Note 2. This is purely because of the game 8 ball pool from Miniclip as the game looks different on Note 2 and different on N5. Do you have any idea what is the DPI of Note 2 v/s our phone.
Thanks.
Click to expand...
Click to collapse
Yeah well the Note 2's DPI is set at 320 by default, but the general consensus seems to be 240 DPI looks sharpest on that phone. Bare in mind the Note 2 has a 5.5" screen though which is somewhat larger than the Nexus 5 so it may not work quite so well for you, give it ago though! Would be cool to see what you think, like I said i struggle to tolerate anything lower than 340 myself but its all personal prefrence
Thanks to joyo22 for the information. Thread is here:
http://forum.xda-developers.com/showthread.php?t=2243799
Related
Ported to Motorola Droid 1 also :O
CAN SOMEBODY PLEASE TAKE A LOOK @ THIS ROM?
DOWNLOAD LINK MOTOROLA DROID ROM
http://zen-droid.googlecode.com/files/Zen_MIUI-v2.zip
If you run into a dialer force close issue, check out this fix. Simply flash the file in Clockwork just as you did with the ROM. No wipe necessary.
http://www.droidforums.net/forum/at...i-droid-1-transparent_smoked_glass_dialer.zip
Source: Zen-Droid
http://www.youtube.com/watch?v=x6yY53Kcc0w
Is it possible to port this to Milestone? It looks very great and fast! WOW
http://androidandme.com/2010/09/hac...oidandme+(Android+and+Me)&utm_content=Twitter
dammm this UI its fkn great!!! i want this on mi milestone
i think it is possible because milestone has a lot of users in China
its looks great but there are some bugs as i read in different forum..
i think its possible to be on our milestones cuz its based on Cyanogen rom
i wonder if " kabaldan " can develop it to compatible with our device
mytouch11 said:
its looks great but there are some bugs as i read in different forum..
i think its possible to be on our milestones cuz its based on Cyanogen rom
i wonder if " kabaldan " can develop it to compatible with our device
Click to expand...
Click to collapse
let kabaldan finish it's cm6 first ... if he commits his sources to a public repository, other developers may jump in and change our milestones
i´ve seen this is ported to droid so porting the home app to milestone it shouldn´t be that hard i would love to give this a try !
Ported to Motorola Droid 1 also :O
CAN SOMEBODY PLEASE TAKE A LOOK @ THIS ROM?
DOWNLOAD LINK MOTOROLA DROID ROM
http://zen-droid.googlecode.com/files/Zen_MIUI-v2.zip
Source: Zen-Droid
http://www.youtube.com/watch?v=x6yY53Kcc0w
mousiope said:
i´ve seen this is ported to droid so porting the home app to milestone it shouldn´t be that hard i would love to give this a try !
Click to expand...
Click to collapse
what you see in front of you , is not always "just a launcher", so beware, it can be a lot harder to make it work on milestone, as droid has no strange baseband problems(12+ different variantions + drivers changes), no bt,gps,gki system as backend to handle communication.
and finally, it might have less memory and can look nice, but reloads alot. which is not a problem on droid with swap and compcache options enabled.
someone please tell me what dialer this is using..
that looks like the perfect smartdialer for me
Doesn't look anything special anyway? :/
Sent from my Milestone using XDA App
i know some people are gonna kill me but i like the iphone look a like icons where can i get those for launcher pro ?
This is off topic, dude
TheSSJ said:
This is off topic, dude
Click to expand...
Click to collapse
yes please stay on topic, we need to know if someone wants
to try to port this to our Motorola Milestone, the UI looks very nice
and fast to me + this ROM looks like no other so we got more different
options to choose from to install
Hopefully kabaldan can take a look at this thread and the Droid ROM
provided
Wow that is a sweet ROM ... its kinda like what I imagined Android should be (iOS + widgets + Google stuff).
Its awesome because it basically borrows the strengths of both Andriod and iOS and makes it into a hybrid: very intuitive user experience that supports advanced features.
I really dig the whole layout: just one place where you scroll pages (not double like Galaxy S's TouchJizz).
I think its awesome how you:
+ have only one main area where you scroll (unlike Galaxy S)
+ you have a cool looking arrow (that indicates which screen you're at)
+ the arrow is positioned in a great location
+ the arrow allows you to quickly scroll between them (your fingers dont need exercise!)
+ can have unlimited "Home" screens
+ easily rearrange them (so you can move groups of Apps easily)
+ can manually choose the main home screen is also awesome
+ can easily delete Apps from the home screen (that rubbish bin at the top is so cool)
+ enter "edit" mode on the homescreen (displays the boxes)
+ add Widgets in this weird but wonderful way
+ easily rearrange Apps and folders
- too bad you can't place folders inside folders (which isn't a big deal and actually helps keep things simple, but I still prefer having the option)
- too bad you can't make shortcuts of Apps (making it impossible to launch Apps from several places/homescreens)
- too bad it doesn't support haptic response (...that would be so cool!)
- too bad it doesn't work in landscape mode (I have an idea how this can be implemented in a great way, I will make a mock-up if requested*)
I also dig the intuitiveness of:
+ the controls/shortcuts for wateva screen is always located on the bottom (familiarity/cleaness)
+ Apps automatically get a coloured backing like on TouchWiz, to make each App look more familiar (retains order) but with its curved sides it still retain some funk (reminds some of the iPhone, in a good way)
+ I like how the page bounces when it hits the end, while kinetic-scrolling
+ the transitioning (page quickly zooms in when opening/zooms and fades out when closing)
+ I like how the Widgets/startbar/notifications tab are transparent (requires a theme that can change these collectively)
+ like the space to put 0-6 Apps to launch from the App-dock and re-arrange them easily
+ like the large icons on the bottom of the Contacts page
+ like the large icons on the bottom of the Dialer
- the Music App has the same thing but its located on the top row (they forgot?)
- the App-dock doesn't let you put any folders into it, shame (but probably an easy fix)
- the dialer could've been improved by taking some cues from the the Galaxy S... if requested I will make you a mock-up**
- the settings page is just stock Android, they could've decorated it slightly like on the HTC Sense ROMs (probably an easy fix)
I loved how you can scroll the "functions" buttons in the notifications tray but overall I didn't like it as much as the Galaxy S's, its great but I see some areas of improvement:
- i think they should've have 4-larger "functions" displayed instead of 5 smaller ones
- i think somewhere in the Settings they should've made an option to Add/Remove some of those functions and arrange the order according to the user (like having a second App-dock but instead for system tools, a Tool-dock!)
- i think it needs the controls for music/movies (the media player) in the notifications tray like the Galaxy S (that's actually awesome)
Other things that would make a killer experience on an Android phone is if they also had
1) the "hibernate" function that intiates when you switch off your device (new HTC Sense),
2) a customizable theme that's consistent throughout Widgets/Folders/Pages,
3) and 3 main buttons (no need for trackball) to make the experience intuitive;
Left button***
= press is back (works the same way already in Android)
= hold (1.5sec) is Force-Close the app (which is so handy in Android that its not funny)
Middle button***
= press directs you directly to the "main" homescreen
= hold (1.5sec) opens you another page that "previews all currently running applications" (which is great for speedy multitasking)****
= See this just as an example for what happens when you hold the Home button http://farm5.static.flickr.com/4013/4355688804_68ccaca964.jpg
Right button***
= press initiates the Menu function
= hold (1.5sec) initiates the Search function (just like on the Galaxy S)
And arranging the buttons in this order allows easier use for users because it is intuitive (majority read left-right, buttons function in that same order ... WP7 actually got this right)
I think that is the best way to go about Android ROM's (with my slight improvements) as a Froyo build. So yeah, this is about 90% finished of what I envisioned/want from Android (for the DEXT/Milestone2/GalaxyS). If you want to visually see what I mean at the (*)'s, I can do so if you are wanting
Hmmm nobody interested in this porting it to Milestone??
hanslast said:
Hmmm nobody interested in this porting it to Milestone??
Click to expand...
Click to collapse
Ask Dext3r / nadlabak
http://modmymobile.com/forums/563-m...-sep-2010-motofrenzy-froyo-2-2-milestone.html
http://modmymobile.com/forums/563-m...yanogenmod-6-milestone-bastardized-2-2-a.html
It might be possible to get Milestone + 1.2GHz + froyo + MIUI + gamegripper ... hehehe!
ekin said:
Ask Dext3r / nadlabak
http://modmymobile.com/forums/563-m...-sep-2010-motofrenzy-froyo-2-2-milestone.html
http://modmymobile.com/forums/563-m...yanogenmod-6-milestone-bastardized-2-2-a.html
It might be possible to get Milestone + 1.2GHz + froyo + MIUI + gamegripper ... hehehe!
Click to expand...
Click to collapse
yeah allready did, Dexter replied that someone else has to take a look at it, because he is too busy with his own custom roms. Kabaldan/Nadlabak did not even reply to my personal message... guess we will never see this rom on our Milestone (
hanslast said:
yeah allready did, Dexter replied that someone else has to take a look at it, because he is too busy with his own custom roms. Kabaldan/Nadlabak did not even reply to my personal message... guess we will never see this rom on our Milestone (
Click to expand...
Click to collapse
Oh
I would so develop this myself, I've got the time ... but I know nothing of coding!
hanslast said:
yeah allready did, Dexter replied that someone else has to take a look at it, because he is too busy with his own custom roms. Kabaldan/Nadlabak did not even reply to my personal message... guess we will never see this rom on our Milestone (
Click to expand...
Click to collapse
Sorry for that, I guess that I decided to postpone my reply and then forgot. Sometimes I'm not in the social mood, my friends are used to it .
I hardly find the time to focus on the bugfixing and improving of the CM6 port. I will not start any other project anytime soon, otherwise I could loose my wife, daughter and job .
believe me that if you just take 15-30 each day you will make it...and i'll be happy to know that someone's working on that
By the way YOUR ROM ROCK!!!
Since the same questions seem to be getting asked a lot, here are some methods for getting past stock NookColor ROM limitations in a single thread:
1. How do I keep wifi from turning off when the screen goes to sleep?
- download Spare Parts from the market and set wifi sleep policy to never.
. . . mixed results have been reported with this method, but this appears to be the best known fix at the moment.
2. I restored and re-rooted, now I can't log in to my B&N account!
- get NookColorTools app (if not installed during root, it's on xda). Under All Settings, open the 2nd (of 3) setting called Wireless near the bottom. This will begin their registration process again.
3. How do I install a different keyboard?
- if it's in the market, first purchase/install it-- if it's a stand-alone apk, skip that and move on to the next paragraph. If you just downloaded it from the market, find the apk somewhere in data/app/ and copy from there.
Now place the app's apk (Root Explorer works great) in system/app (mount system as r-w first). Look at the file's permissions (long hold on it and choose Permissions from the menu), and match it to the permissions of the other files in that folder. Reboot. Then open your trusty NookColorTools, select keyboard, and you should be able to switch to it. Not all keyboards are currently working, but this is a great way to find out if it does that doesn't require renaming or deleting your current keyboard.
4. How do I get Swype on here?
- right now, you can't. Swype requires a copy that matches your device's resolution, and the only version of Swype that matches ours (1024x600) is the copy that ships with the Galaxy Tab, but, to my knowledge, nobody has gotten it completely working on here without causing major system crashes (not to mention the apk couldn't be posted on xda even if it was eventually hacked to work).
SlideIT keyboard is another trace keyboard that DOES work on the NookColor, and I've been very happy with it (it's come a long way since I tried it last summer and quickly uninstalled it). The method in #3 above should work to install it.
5. Wait, I can't copy and paste on the NookColor??
- not through the OS, no. There is a solution though. It involves getting an app called Copy Paste It from the market (paid, but there's a trial version). You'll probably need to set it to rotate clockwise (in settings), or it'll get screwy.
When you want to copy, activate the function from the notification, and it'll let you frame the text to copy:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The second part, pasting, requires having a keyboard with a Paste setting in it. Again, SlideIT has this on the special characters keyboard (I'm not a troll for SlideIT, just a happy customer). I'm not sure which other keyboards have this feature, if any (if you know, post, and I'll update this). Assuming you have a keyboard with paste, it'll paste what the Copy Paste It app copied.
6. Why is everything on my screen so small?
- this is because the NookColor's stock LCD density is 169.333, which is pretty low (Galaxy Tab is 240). Unlike resolution, which is hardware-based, density is software-based and can be changed. If you search the market for LCD density, there are a couple apps that will do this--a free one that won't survive a hard reboot, and a paid one that (supposedly) will.
If you want to make it permanent for free, you can edit your build.prop file. Again, use Root Explorer to open system/build.prop (BACKUP FIRST!), find the following two lines:
ro.sf.lcd_density.xdpi=169.33333
ro.sf.lcd_density.ydpi=169.33333
If you wanted your density to be 250, you'd replace them with the following single line:
ro.sf.lcd_density=250
Save the edited file, and reboot.
Here are two of my Galaxy Tab-esque homescreens set to 250:
. . . Now, jacking up your LCD density much above 200 will make your status bar look wonky and cut-off. One solution for this is to set it to 250, like above (by changing build.prop - I think the apps I mentioned only allow multiples of 20), which will make it look clean (as long as wifi is on). The only problem there is that you'll lose your status bar clock and Notifications in portrait mode . . .
. . . the solution for THIS is to get two apps: hellostatusbar, and quick launch. Set quick launch to open hellostatusbar on a home- button double press, and it will display your Notifications.
Also note that raising the density can cut-off parts of the stock Barnes & Noble software (they're designed for the lower density), so this mod is probably better for people like me who use the Kindle app and ezPDF for reading.
7. If I don't want to use softkeys, can I remap the hardware buttons to do something different?
Yes. In Root Explorer, navigate to system/usr/keylayout, make a backup of TWL4030_Keypad.kl, then open the original with text editor and change the entry for key 115 ( volume up) and/or key 114 (volume down) with something like BACK, MENU, or SEARCH. Save the file. Reboot, and they'll be whatever you changed the entry to.
If you want easy volume controls after remapping these buttons, a market app called Volumer++ can be set to live in your notifications for easy access. Otherwise, you can change them from settings.
8. How do I set my wallpaper so that the resolution looks good?
- I used a market app called Wallpaper Set & Save. It's easy, and resolution looks great. I think it cuts off the image a little bit, but not much. I think this method will suffice for many people, but if you want it to be sized perfectly, do the following (credit to swapdotavi for the instructions):
[Get an image that is at least 1200x1024, crop it (without scaling) to 1200x1024. If you're using Photoshop, copy the entire image, then create a new file sized 1200x1024. Then paste the image and use the arrow to drag it around to whatever looks best to you. Save the file as a .png, transfer to your nook, and use Wallpaper Set & Save to choose the new file.]
. . . Since we share the same resolution with the Galaxy Tab, the wallpapers that came with it look phenomenal (in my opinion) on the NookColor. Follow this link to pick them up:
http://galaxytabwallpapers.net/original-galaxy-tab/
9. Can I change the lockscreen slider to look like stock Android or Sense?
- yes - get an app called WidgetLocker. Set it to look how you want. Then, under Behavior, set Homehelper as your system home. Still under Behavior, go to Home to Launch, and pick your real launcher (Launcherpro, ADW, etc.). Also, under Advanced, be sure to check both the Root Bypass of 5 Second Rule, and Retain Keyguard.
10. My NookColor seems sluggish - is there a way to speed it up?
Most of you will already know this, but Setcpu is a market app that can speed things up and improve battery life. CPU Tuner is a free alternative that's similar, but I've had more experience with setcpu, and can vouch much more for it.
My recommended settings:
Min 600
Max 800
Governor: OnDemand*
check 'set on boot'
... And one profile enabled:
Screen Off
Min 300
Max 600
Governor: Ondemand
... And another optional setting (for even a little more extra zip):
under Advanced:
change "Up Threshold" to 35
* for the fastest setting, set the governor in the main CPU setting to Performance (with 800 max). It may drain your battery quicker, but mine still holds up surprisingly well on performance--and the nook is very fast.
These are just settings that work for me. Feel free to experiment. Also, some people were having their Nook randomly reboot, and changing the governor from conservative to ondemand helped.
11. Any other battery-saving tips?
In case you missed the rival xda threads arguing over who thought of it first, there was a potentially useful battery-saving trick in there:
Go back in Root Explorer, and in system/app, mount as r-w and rename Phone.apk and TelephonyProvider.apk to anything else (adding .bak onto the end would be fine).
Basically, you're removing android system files that may be wasting juice looking for a non-existent cell service. It's unsure if or how much this actually improves battery life, but it very well could, and it certainly won't hurt anything changing their names.
12. Why aren't my favorite live wallpapers working?
I'm not sure, but here's how to get the rest of them going:
Download this file: http://db.tt/ur0c98s
It will fail installing, but if you use Root Explorer, copy it from your download directory, go to system/app, set as r-w... Then long-press on any file in that directory, and look at its permissions. Now paste your LiveWallpapers.apk there and change its permissions to match the others. Your live wallpapers should work now!
The Nexus wallpaper won't work, but just install Nexus Revamped from the market - it's identical, it's free, and it has customization.
If you're using one of the more system-intensive Live Wallpapers (like "Water"), I'd recommend using all of the Setcpu changes from #10 above to keep things snappy (also know that LWP's can drain battery quicker).
13. How can I get my Google contacts in here?
If you aren't concerned with them showing up in the B&N Contacts app, and are more interested in having them come up as auto-suggestions when typing an email address or Google Voice text number, there's a way (credit to jadambpharm):
- Go to gmail on the web, click on contacts (left side), then More Actions, then Export. Choose .vcard format. Transfer that file to your SD card.
- get a Market app on your Nook called Import Contacts. Point it to the contacts.vcard file you just got, and they'll now come up for auto-fill suggestions!
14. How can I prevent the Nook from automatically updating the firmware?
- Change the name of etc/security/otacerts.zip to anything else (doing this in Root Explorer works fine). So far, this had looked pretty solid in successfully disabling OTA updates.
15. Why won't YouTube play videos in HD?
For some reason, the YouTube that's installed from rooting won't do it. To get a version that plays HD:
- uninstall your current YouTube via Titanium Backup
- download this version from the Evo (credit aludal): http://db.tt/y5vVvI2
- rather than installing this one, rename it youtube.apk and copy it into system/app (w/permissions matching the other apk's in that folder)
It should be there now, ready to play HQ clips. If not, reboot first.
I'll update as I think of more. Enjoy your modestly-priced, unintentional Android tablets!
Reserved 10 chars
How about "What size should wallpaper images be?"
I suggest this because I dont know
swapdotavi said:
How about "What size should wallpaper images be?"
I suggest this because I dont know
Click to expand...
Click to collapse
I didn't resize them manually, I just used an app - will update OP in a minute with that, and again later when I get the chance to research manually setting them . . .
I don't know either, but I've had good luck with searching for 'wallpaper' on Google images with size set to 1024*1024 and then using 'set as wallpaper' from dolphin browser HD.
Sent from my NOOKcolor using XDA App
pest789 said:
I don't know either, but I've had good luck with searching for 'wallpaper' on Google images with size set to 1024*1024 and then using 'set as wallpaper' from dolphin browser HD.
Sent from my NOOKcolor using XDA App
Click to expand...
Click to collapse
The Galaxy Tab wallpapers I've used all look phenomenal too. Same resolution, so its tailor-made. Easy to find them with a google search.
For some reason changing the lcd density didn't do a damn thing through build.prob after reboot. What did I do wrong?
Edit:
And I did save it before rebooting so I'm not sure what I did wrong...
wvcachi said:
3. How do I install a different keyboard?
- if it's in the market, first purchase/install it-- if it's a stand-alone apk, skip that and move on to the next paragraph. If you just downloaded it from the market, find the apk somewhere in data/app/ and copy from there.
Now place the app's apk (Root Explorer works great) in system/app (set system as r-w first). Reboot. Then open your trusty NookColorTools, select keyboard, and you should be able to switch to it. Not all keyboards are currently working, but this is a great way to find out if it does that doesn't require renaming or deleting your current keyboard.
Can you please explain the 'set system as r-w'?
Thanks
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@beejis - make sure you're losing the xdpi and ydpi parts and merging it into a single entry. Look closely at the example in the OP. Also, make sure you're editing the entry that isn't commented out (don't bother editing the lcddensity entry with a # in front of it) a few lines earlier. If for some reason that didn't work, then use the free app from the market to change it.
@k8108 - if you're using Root Explorer, it's a little button up top when you're navigating system/, which lets you toggle mounting system as 'read-write' and 'read-only.'
Beejis said:
For some reason changing the lcd density didn't do a damn thing through build.prob after reboot. What did I do wrong?
Edit:
And I did save it before rebooting so I'm not sure what I did wrong...
Click to expand...
Click to collapse
Comment out these lines (add # to beginning):
# ro.sf.lcd_density.xdpi=169.3333
# ro.sf.lcd_density.ydpi=169.3333
Add this line:
ro.sf.lcd_density=254
I already had a line similar that I uncommented, and I run mine at 254.
169.3333 / 2 = 84.6666
169.3333 + 84.6666 = 254
I am probably overthinking it, but it looks good. You can make that number 250 if you want.
The Program LCD Density lets you select specific densities as well, but is only soft. Nice for testing.
k8108 said:
Can you please explain the 'set system as r-w'?
Thanks
Click to expand...
Click to collapse
http://nookdevs.com/NookColor_Making_system_partition_Read-Write
From adb shell, run this code:
Code:
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
ThrowingKs said:
http://nookdevs.com/NookColor_Making_system_partition_Read-Write
From adb shell, run this code:
Code:
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
Click to expand...
Click to collapse
...I got the impression he was using Root Explorer, in which case it's a little button that says r-w.
I have used the free market app to change the lcd density and it makes most of the interface fantastic except for a couple things. As noted the status bar doe mess up but that I am not worried about but the screen density change to, 250 in my case, really screws up the formating of my nook library and shop. I use them quite a lot to read newspapers and such so if anyone else has this experience let me know how/if you deal with it.
Sent from my LogicPD Zoom2 using XDA App
foethalove said:
I have used the free market app to change the lcd density and it makes most of the interface fantastic except for a couple things. As noted the status bar doe mess up but that I am not worried about but the screen density change to, 250 in my case, really screws up the formating of my nook library and shop. I use them quite a lot to read newspapers and such so if anyone else has this experience let me know how/if you deal with it.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
Good point - I'll note that in the OP. I don't use the B&N stuff, so it's easy for me to forget that not everyone on xda is in the same boat.
Where does the SlideIT.apk go after you install it from the market? I can't put it in the system/app folder because i can't find it. Any ideas?
NookColor+ XDA 4 ever
cgtombstone said:
Where does the SlideIT.apk go after you install it from the market? I can't put it in the system/app folder because i can't find it. Any ideas?
NookColor+ XDA 4 ever
Click to expand...
Click to collapse
Look in data/app, and find the file named com.dasur.slideit.apk. Copy/paste that into system/app (hit r-w first of course), then reboot and switch keyboards via NookColorTools.
My bad I was searching for it in root explorer and I gues the search function was skipping the data folder for some reason ( or I'm missing something). Thanks anyway.
NookColor+ XDA 4 ever
Thanks bookmarking this thread
wvcachi said:
I didn't resize them manually, I just used an app - will update OP in a minute with that, and again later when I get the chance to research manually setting them . . .
Click to expand...
Click to collapse
Ah perfect did not see your update. I see you found Set and Save, but you mentioned you might update with exact size instructions later. I actually went and did a bit of research, so maybe I can save you some time
To get an perfect wallpaper using 5 screens, like in ADW:
- Get an image that is at least 1200x1024
- Crop (dont scale) it to 1200x1024. A really easily way to do this is open the file in Photoshop, copy the entire image, then create a new file that's exactly 1200x1024. Then just paste the image and use the arrow to drag it around to whatever looks best to you.
- Save the file as a .png
- Get it on to your nook. (SD card transfer, email and download, whatever)
- Open Wallpaper Set & Save
- Point it towards the folder you have your wallpapers in
- Select the wallpaper you want
- Hit apply
Bam. Perfect wallpaper, no stretching, no compression. Looks great! I'll post screens later today if I remember
I used a 1920x1200 wallpaper I had on my PC, cropped it, emailed it to myself, then used Set & Save to place my wallpaper. It's really crisp.
edit: And thanks for the lock screen information! Going to do that tonight; sick of the stock screen
MOD, can we get this stickied? Lots of good info!
Hi all,
I'm a LeeDroid HD user, and I've spent some time over the last few weeks tweaking the auto-brightness settings to maximise battery life. I've reached a point where I haven't found any problems with my settings for 4 or 5 days now, which I think is a pretty good test. It's on the low side under most light conditions, but I've tried to find a point where I can comfortably read the screen without holding it up to my face, and when outside, this includes wearing sunglasses.
Obviously screen brightness is a very personal thing, so you might not like where I've ended up. When you want to impress your friends with your awesome DHD, you can always override the auto setting and just crank up the brightness control manually
Sharing my settings is also not simple either, since it requires a mod to res-framework.apk, which is used for themes. So ... what I will do is show you a graph of my changes to so you can see what I'm doing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Left side of graph is a dark room, right side is the harsh West Australian sun)
And make a flashable zip available for Lee's default ROM, with no themes installed (Base_LeeDroid_Lower_Auto_Brightness_Patch).
And another flashable zip to use if you've installed the "LeeDrOiD Notification power widget" from the LeeDroid HD OP (LeeDroid-PNW-Lower_Auto_Brightness_Patch).
And I've already had a request to make one for the "Stock 1.84" theme from here, so that's also attached (Stock_1.84-Lower_Auto_Brightness_Patch).
If you have another theme/mod installed, I think that flashing the above will wreck it ... be warned!
If you have a specific theme/mod you're using and want to try my settings, just send me a link to it and I'll cook up a flashable zip for it ... it doesn't take long. Alternatively if you know what you're doing, I can provide my arrays.xml file and you can do it yourself.
ALL files in this post are to be flashed with cwm 2.5.1.3 ... I haven't tested with any other version.
Even though I've tested all these patches myself, I'm not an expert at this, so PLEASE PLEASE PLEASE take a nandroid backup first in case I've done something fundamentally wrong.
If you don't like my settings, you can either restore your nandroid backup, or if it was a theme specific patch, you could just apply the theme again.
If it all goes pear-shaped ... I TAKE NO RESPONSIBILITY!
Hope somebody (other than myself) can benefit from my experimenting
If any themers want to incorporate my settings, it's just a change to arrays.xml inside framework-res.apk, nothing else. I'll also attach my arrays.xml (zipped), feel free to use it. As a courtesy, please credit me for the auto-brightness settings If you use them.
As mentioned above, if anyone would like to patch this on top of a specific theme/ROM you have already flashed, just ask and I can cook it up. If you feel like making it easier for me, all I need is framework-res.apk, so if you have a link to just download that, you'll get your patch quicker than if I have to download the entire theme
If anyone has arrived here from the LeeDroid thread, be aware that these are NEW versions of the files, as the ones in that thread were based on the wrong version (they were too low in the 40-90-160 range).
Cheers all, any feedback is appreciated
I have since put together a DIY guide on how to mod the auto-brightness settings inside framework-res.apk yourself. Thanks to those who contributed. Here's the guide!
This was all done on myWindows XP SP3 machine.
1. Download and install a recent Java Runtime Environment (JRE), if you don't already have one. I won't go through those steps, google it. If you're unsure, you can always come back to this step later if it's not working.
2. Download APK Manager from here: http://forum.xda-developers.com/showthread.php?t=695701 ... there's probably lots of good info in this thread if you have questions later about this tool.
3. Unzip the file wherever you want, mine is just on my desktop.
4. I was advised to replace the version of apktool.exe in the 'other' folder with an earlier version. I don't know if this is necessary, and I don't know what version I now have ... possibly 1.3. ** Multiple people have needed to downgrade to the older apktool.exe that I use, so I have attached it to this post. Just extract apktool.exe from the zip and place it in the 'other' folder, replacing the existing apktool.exe.
5. OK, now you should be ready to go! Grab your framework-res.apk either from your phone, or straight from the ROM you've flashed if you haven't applied any themes. framework-res.apk can be found in /system/framework.
6. Copy your framework-res.apk into the "place-apk-here-for-modding" folder.
7. Run script.bat. If you see a text menu pop up then all is good. If you get an error then you've done something wrong! Probably related to your JRE.
8. Choose Option 9 - Decompile apk. Wait until it finishes. Minimise this window now, we'll come back to it later.
9. Go into your projects folder, and you will have a new folder there called framework-res.apk, double click it.
10. Navigate to res/values
11. Open up arrays.xml in a text editor such as Notepad++. Using Windows built in notepad app could cause issues due to Windows -> Linux compatibility issues.
12. Scroll down to the section where it says "<integer-array name="config_autoBrightnessLevels">". This is the section that defines the steps of the ambient light sensor. You probably won't need to adjust these values for now.
13. The next section down should be "<integer-array name="config_autoBrightnessLcdBacklightValues">", this is where the tweaks really begin. The values here relate directly to how bright the screen is at the steps defined in the section above. Minimum value is 1, maximum value seems to be 249, but that could be incorrect. Would make more sense for it to be 255.
14. Change these values as you wish, but change them to the same thing in all these 3 sections - config_autoBrightnessLcdBacklightValues, config_autoBrightnessLcdBacklightValuesUp, config_autoBrightnessLcdBacklightValuesDown.
15. The next 2 sections - config_autoBrightnessButtonBacklightValues, and config_autoBrightnessKeyboardBacklightValues do the same thing, except for the hardware buttons, and keyboard buttons (if present) respectively. Adjust these if you wish.
16. Save the file.
17. Navigate back to the root of the APK Manager directory.
18. Return to your APK Manager window.
19. Choose option 11 - compile APK.
20. When prompted if this is a system APK, type y. Hit Enter.
21. When prompted if you want to copy additional files, type n. Hit Enter.
22. Choose option 22 - Set Current Project
23. Choose option 2 - unsignedframework-res.apk
24. Choose Option 5 - Zipalign apk
25. Choose Option 24 - Quit. On my script version you have to choose option 24 twice. I assume it's a bug on my version, hopefully you won't have to do the same thing.
26. Congrats! You now have a modded framework-res.apk!! You'll find it in the folder "place-apk-here-for-modding", with the new name "unsignedframework-res.apk". Copy it somewhere else (eg. desktop) and rename it to framework-res.apk.
*** If you know how to copy the modded file into a pre-existing flasheable zip, then by all means go for it. If not, continue following the steps below to create a flashable zip in the UOT Kitchen ***
27. Go to the UOT Kitchen - http://uot.dakra.lt/kitchen/ Hopefully it's not busy and it lets you in! If not, you'll have to wait.
28. Go to the file upload tab and upload your new framework-res.apk file.
29. If this is a FROYO ROM that you're modding, then that's it! If it's a GINGERBREAD ROM, then you also have to grab SystemUI.apk and com.htc.resources.apk from your ROM or phone and upload these also. SystemUI.apk can be found in /system/app and com.htc.resources.apk can be found in /system/framework
30. Go back to the Summary tab, then click "Submit Work to Kitchen".
31. When it's done, download the file, boot into cwm, ***DO A NANDROID BACKUP***, then flash your file!
If you've done it right, you're auto-brightness settings should be applied!
If you get stuck in a boot loop, or it just doesn't boot at all ... lucky you have a nandroid backup!
Please note that as this thread progresses, newer versions of the files get posted which makes these ones in the OP redundant. I'll leave them up for now just in case someone needs them, but in general, you'll want to dig deeper into the thread to get flashable files for newer versions of ROMS.
Excellent post.
I will take a look at your final arrays.xml, but I'm happy (so far) with the one I've cooked up with modified at the dimmer end of the scale.
Over the next day or so, I'm going to try and add extra steps (double) into the array, making a more linear or at least a smoother curve. As you said in Lee's thread, not sure if it's up to the build of the kernel.
Even if I can successfully add the extra values and flash, maybe I won't notice if its really working and the values are applied or they are just ignored by the ROM or kernel? What's the worst that can happen? Backup...........
Using the GPS Status & Lux Meter I was able to double check the phone light sensor invrements in:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>
UpInTheAir said:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Click to expand...
Click to collapse
That looks right to me, I've not noticed any others in my testing
UpInTheAir said:
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Click to expand...
Click to collapse
Yep, I believe that's right. New drivers would need to be compiled into the kernel, and then the array modified accordingly. This is still something I'm not 100% sure on though, since their could also be a hardware limitation here.
UpInTheAir said:
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>
Click to expand...
Click to collapse
The way it works is, if the light sensor returns a value of 10 (which is < 21), then it returns the first value of the array. If it's 40 ( 40 > 21 and 40 < 42) then it'll use the 2nd value ... and so on. that's why there's one extra value in the backlight values arrays than there is in the brightness level arrays, because it's the in betweens, plus less than the first value, plus greater than the last value.
Does that answer your question? Or did I mis-understand?
Thanks for the reply. Confirmed what I had thought.
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system. I run W7, so that's no an option right now. It still is a little beyond my scope of knowledge, but I'm learning bit by bit and also a lot of reading what others have said and researching Mr. Google.
Another useful app is Sensor List, which can graph the changes in lx, but the values are the same as above.
Looks like I'll be keeping this PC when I eventually upgrade so I can run Linux on it to play around...........
UpInTheAir said:
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system.
Click to expand...
Click to collapse
No need to de-compile it dude ... Lee publishes his kernel source code on github!
https://github.com/LeeDroid-/htc-kernel-ace
As for making changes and then re-compiling it ... I have no idea either
Thanks, will check it out and see if I can find out anything useful.
I don't really want to bother Lee as he's either quite busy or having some well deserved time 'off' before the official GB release.
It's not that big a deal to me (as you said, could be hardware limitation, so no chance anyway), but more of having a play, seeing where things are and what happens and why.
Hi mate,
Sorry, I'm late...
Great thread.
Just few questions:
The value I got (have ever seen) in my GPS status are: 10-40-90-160-220(5)?-640-10240
I have not seen these readings: 320, 1280 and 2600.
So, do I need to download and flash arrays.xml.zip first?
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
I had a thorough test on the one slopppy posted for me in LeeDrOid's thread. I works great except when the reading is at 40. At 40, the brightness is lowered to minimum. I know this as the button light has lit up. (My phone got 40-90-160 under fluorescent light, so if brightness is lowered to minimum at 40, it means it goes too low [for me].) Apart from this, everything works fine.
Sitting in the car under the sun, the brightness works well. Screen is readable even with sunglasses on. Walking out from the car, under direct sunlight, brightness still works fine.
Like what I said before, may be we should not be too particular about how it works under the sun as it maybe too bright an environment for our eyes to notice the difference.
So bro slopppy, what should I do now if I want to try them out now?
Regards!
So, do I need to download and flash arrays.xml.zip first?
Click to expand...
Click to collapse
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid but no themes/battery mods etc on top of it
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid and then installed the "Notification Power Widget" from the OP of the LeeDroid HD thread.
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
Click to expand...
Click to collapse
Yep, this is the one you should flash mate
works great except when the reading is at 40. At 40, the brightness is lowered to minimum.
Click to expand...
Click to collapse
I think that 40 isn't a value I come across in my daily life! haha ... I've only ever seen it when I mess around with the sensor to try and make it hit different readings. Couldn't hurt to up it a little I guess.
So bro slopppy, what should I do now if I want to try them out now?
Click to expand...
Click to collapse
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go
slopppy said:
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
...
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go
Click to expand...
Click to collapse
Thanks mate. Will do a thorough test again for this.
Value 40 is when I'm sitting at the corner and the phone facing away (opposite) the light. My eyes did not notice any much difference in brightness but my phone's sensor did.
Thanks more for the last sentence of your previous post... (maybe push it up a little to 8%-10%? frankly, me too not sure whether it will suit me more... my suggestion, 40 - 8-10%, 90 - 10-12% and 160 - 12-15%)
Edit: Oh, luckily I'm patient enough to wait for your reply this time...lol
Quick feedback for indoor test:
My personal opinion:
at 40, the brightness is a lowered to minimum and button light turn on, hence, a little too low.
at 90, didn't notice any difference in brightness. However, the button light turned off. So there must be an increment but not noticeable to my eyes. Still too low. (the one posted for me in LeeDrOid thread doesn't have this issue)
at 160, a little (really little only) too bright. Few percent reduction is better.
Will again update my feedback for outdoor test.
Regards!
HoneyHD Theme.
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813
What about Kalagas theme...i would be very appriciate
Is this for Froyo only because i can't find arrays.xml inside GB framework-res.apk
Yes, sloppy should be a bit more specific, but in his defence, he does mention in the first post cwm recovery 2.5.1.3,...... relative only to LeeDrOiD Froyo.
Sent from my Desire HD using XDA App
Yep, good point, sorry about that. It's for Froyo SENSE ROMs only.
Anyone know how I can modify the title of the thread??
I'll get on to the requests now.
Cheers,
hamurabi1 said:
What about Kalagas theme...i would be very appriciate
Click to expand...
Click to collapse
Which version of Kalagas theme are you running? There seems to be a zillion of them
kennykenneth said:
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813
Click to expand...
Click to collapse
Hi,
The framework-res.apk from Honey HD doesn't want to play ball. It gets a couple of errors when I decompile it, then totally flips out when I try to recompile it. It's an intense theme ... maybe he's doing some things which are incompatible with the way I'm going about my changes.
You could always see if the developer is nice enough to cook you up a version using my arrays.xml from the OP. He has other changes in his arrays.xml as well, so he would have to make sure he just uses the auto-brightness section.
Sorry mate!
slopppy said:
Which version of Kalagas theme are you running? There seems to be a zillion of them
Click to expand...
Click to collapse
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].
Thank you!
hamurabi1 said:
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].!
Click to expand...
Click to collapse
Here you mate
As stated in the OP, please do a nandroid backup first ... better safe than sorry ...
[AOSP]LiquidMetal for the Incredible
First I need to thank Jermaine151 for allowing me (to attempt) to continue his work on the LiquidMetal For the Incredible port. Which goes to say I have to thank BigRushDog for his ROCK SOLID Metal build that the RC1 for the Incredible was based off of. I would like to also thank Sac23 and bmxerkid954 for allowing me to use their work and port their build to the Incredible, and were used for Jermaine151's previous versions of this rom. BIG thanks to Koush and the Cyanogen tam for their CM6 files and all they do. Thanks to Koush for his kernel and too many contributions to name. A thanks to gmichaelow for answering questions asked by Jermaine151. A special thanks to Incredibledoes for the original Liquid port. Thanks to jrummy for his ROM Toolbox (look into the donate version.) A thanks to 3MX10 for helping me out with all my stupid questions and helping me pick up where Jermaine151 left off. A special thanks to ALL the testers that have been involved with this project (before or now) for their time and trust that their phones wouldnt get bricked.
If i forgot anyone, it wasn't intentional. PM me and i will update this (this was based off Jermaine151's thread on XDA).
BigRushDog's thread- http://forum.xda-developers.com/showthread.php?t=870944
Sac23 and bmxerkid954's thread- http://forum.xda-developers.com/showthread.php?t=903470
Jermaine151's thread- http://forum.xda-developers.com/showthread.php?t=920804
This ROM is based on Android 2.2 (Froyo) and is built from the Android Open Source Project Code (AOSP) With the Acer Liquid Metal UI on top. (continuing where Jermaine151 left off)
*This rom was not intended for the INC, it is a port and has bugs; it is built off the Metal base. Close to it original source code, just modified for the your phone*
-Proximity Sensor doesn't turn the screen off immediately, but prevents buttons from being pressed when the phones against your face and eventually does turn the screen off. (Works perfectly on LiquidLight)
-Location and Security FC's (Crazy workaround: Rename Phone.apk to Phone.apk.bak, reboot, go intomenu and make changes, rename back and reboot - thanks iceman99393)
-No LEDs for notifications (I'll see what I can do. Any help is appreciated)
-LED flashes orange when charging and turns solid orange when fully charged
-No TV Out
-Changing the Dolby Mobile settings could throw you for a loop.
-CarHome doesn't play nice and will not be included.
-Light sensor (Rom includes Brightness widget)
PLEASE READ - Tips & Tricks:
-To Drag Icons to Other Screens Faster
Drag the icon to the numbers at the bottom of the app drawer
-To Dial *228 for Activation or PRL update (*228 FC's on some AOSP roms)
Dial *228+ (long press the numeral zero key to add the plus sign)
-To Hide the Whole Dock or Half of it
Drag ALL of your icons for the launcher into the app drawer and the notification bar will rest at the bottom of the screen.
Leave just 4 icons in the top row of the launcher and the dock will become half size.
-To Do Normal Reboot/Recovery Reboot
Use Quick Boot app.
-To Make the Weather More Accurate
Open your widgets app (either with the icon or by long pressing the home button, while the screen is unlocked).
Long press the weather widget and drag it to the trash can in the bottom left.
Hit the "+" button and add weather again. It will let you search for your specific city.
-If You don't Like all of the Vibration Feedback, You Can Turn it Off
For Buttons: Settings-->Sound-->Haptic feedback
For Stock Keyboard: Settings-->Language and Keyboard-->XT9 Text Input-->Preferences-->Vibrate on Keypress
-If You Don't Like the Transitions, You Can Turn Them Off
Settings-->Display-->Animation-->Some or None
-If You Don't Like the Launcher, Install Your Favorite Launcher (FIRST!!!!) and THEN Change it
Settings-->Applications-->User Interface. After rebooting it will ask your to choose you launcher (DO NOT CHOOSE LAUNCHER2) (Thanks cooljames2186 for finding this)
If you don't install another launcher before doing this, you may end up in a bootloop
-If You Select Custom Wallpapers and No Longer Want Them Displayed in the Wallpaper (Home Decor) app
Use Root Explorer (or your favorite file manager) and navigate to here: /data/data/com.acer.android.breeze.launcher/wallpapers/user/
Delete any of the numbered folders (i.e. 1, 2, etc)and they will immediately disappear from the wallpaper app.
What's Included:
MMS (Send/Receive)
720P Camcorder
8MP Camera
GPS works
Bluetooth works (Wiimote should work but I can't test that)
Working Wi-fi
Wireless Tether (I've tested with included kernel)
Koush's kernel from CM6.1 (Thanks Koush!)
Gingerbread Keyboard is the default
Google Talk
AdFree
Brightness Widget
T9 Dialing like SENSE!!!
MORE Acer Bloatware Removed
Zipaligned and Deodexed
VERY Fast System (Please allow it to settle down after first flashing)
New widgets
Verizon apps show up in the market
and much, much, more..
Instructions:
1. Download the Rom to your SD card.
2. Nandroid
3. Wipe data/factory reset, Wipe cache, wipe dalvik cache (i recomment formating /boot and /system in advanced menu)
3. Flash the rom zip via recovery.
4. Boot it fully (You shouldn't get a FC if you hit back arrow at region selection, but the FC doesn't hurt anything).
5. Go through set up or skip though it.
6. Set up your Gmail account, let it sync, get your updates from the market.
It may be sluggish after your first boot (Rom's take time to settle in). 7.Please give it 15 mins or more (depending on how much media you have on internal memory and your sdcard) because the media scanner is going through all of your media, adding it into it's database and creating thumbnails.
8. Enjoy!
**PLEASE do not ask for ETA's on updates (I will do what I can with the help i'm able to get)**
***Market 3.2 is included (ICS leak)***
****Netflix is confirmed working (if interested)****
*****I HIGHLY recommend Ziggy471's bfs/havs kernels (one will be attached)*****
******DISCLAIMER: By downloading you agree that I will not, nor will anyone else but you, take responsibility for the results of you flashing any of the files below.******
*******If you have ANY questions or concerns feel free to find me on twitter (@markhoj, or gtalk/gmail MarkHoj08)*******
MD5- 1c5900f5a7802f26f24266688d414976(new)
Ziggy471 BFS HAVS 041011 kernel (optional but not necessary)- http://www.ziggy471.com/downloads/ztest-INC-BFS-HAVS-041011.zip
LiquidMetal_v02 http://dev-host.org/egk9fjkc8quy/LiquidMetal_2.zip
Changes: Build.prop edits, edited some scripts to help with speed, updated market, "fixed" reboot on dolby settings (settings fc now) fixed gtalk, updated superuser and binary, added titanium backup (thank you), might be a couple more things, but i can't think of them right now.
Kick @ss Dude! I hope I didn't steal your second post.
EDIT: Cool. I gave the first thanks on this too!
honestly i forgot all about it. i've been up for like 20 hours straight. I went through, updated all the apps and tried to slim it down a little. I added the ziggy kernel, and it's so smooth (if it's possible to be more than it was.) thanks again.
I'll update OP with changes in the future.
Thanks again to all that helped me out, and were involved before I came along.
---------- Post added at 12:08 PM ---------- Previous post was at 11:52 AM ----------
Rom boots and runs GREAT. Able to be used as a daily, i'm calling alpha because i plan to do a lot of work.
Interesting. I will have to try this out later. Hopefully it'll be a slow day at work lol
Please do, and let me know what you think.
Sent from my LiquidMetal using XDA App
Have you tested this with Chad's Froyo Incredikernel? If not, I'll flash that after I get around to flashing this ROM and report back.
EDIT: After I test the ROM with the kernel you use, of course.
No I haven't tried his incredikernel yet, but as long as its an aosp froyo compatible kernel it should work. I'll download now and try.
Sent from my LiquidMetal using XDA App
Edit:
Installed and running just as smooth, i'm not a benchmark guy anymore. If you want to compare with quadrant go right ahead.
Ok cool. I've been on my phone a decent amount today and am waiting on a couple calls, so if I can't get to it today I'll get it tonight. Looks really cool. I am running NilsP's 3.5. Gingersense at the moment which is really good. I would prefer an AOSP ROM but the stock look is too boring to me and MIUI is too iPhone like, although it has some really cool looking themes. This may be just what I'm looking for lol
Thanks for trying. All credit goes to those listed in OP. right now its just updated (apps) and slimmed down. But there are things in motion. Hopefully this takes off again.
Sent from my LiquidMetal using XDA App
gatormark08 said:
Thanks for trying. All credit goes to those listed in OP. right now its just updated (apps) and slimmed down. But there are things in motion. Hopefully this takes off again.
Sent from my LiquidMetal using XDA App
Click to expand...
Click to collapse
Yep, no problem. And by stock look, I meant like what you would get on a Nexus or a standard AOSP ROM, not this. Hope I didn't cause any confusion.
Man this is awesome so far, I have tried a lot of different roms and this is by far the one I like the most. Thank you
@Bull, I figured that was what you meant.
@Dark, I was away from the Inc for a while. But this was my favorite ROM. I'm hoping to get it bug free. And i'm going to try my hardest to get a GB version, if we can get a system dump. I've got a couple emails out.
Sent from my LiquidMetal using XDA App
Just flashed it and I've let it settle in a bit. This is great so far. I'll play around with it later on tonight and report back any bugs or suggestions, but so far so good. android.process FC'd when it first booted up but, like you said, it didn't affect anything.
Bull_Moose said:
Just flashed it and I've let it settle in a bit. This is great so far. I'll play around with it later on tonight and report back any bugs or suggestions, but so far so good. android.process FC'd when it first booted up but, like you said, it didn't affect anything.
Click to expand...
Click to collapse
if you press back button when language selection screen pops up, English is default and you wont get the FC. but it doesn't affect anything.
So far the only issue I've seen is GPS doesn't work in navigation, unless it takes a while to lock on and I just want patient enough. Other than that it's rock solid.
Sent from my LiquidMetal using XDA App
I noticed that to, I think its a little sluggish for lock on. I use foursquare and wasn't pinpoint like usual
Sent from my LiquidMetal using XDA App
gatormark08 said:
I noticed that to, I think its a little sluggish for lock on. I use foursquare and wasn't pinpoint like usual
Sent from my LiquidMetal using XDA App
Click to expand...
Click to collapse
Have you tried it using the "Faster Fix" app on the market? That may help it.
Sent from my ADR6300 using Tapatalk
dtraini7 said:
Have you tried it using the "Faster Fix" app on the market? That may help it.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I'll look into it. If it works good, i'll contact the Dev and try to include it in the next release if GPS isn't 100%
that was with light to moderate use, about 50 text (sent and received) and periodic facebook/ twitter checks/updates.
Acer Iconia Gingerbread system dump:
http://android.modaco.com/topic/341241-acer-iconia-smart-need-help-rooting/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For
Motorola Atrix
ROM INFO
Latest MIUI Version: 2.12.28
AOKP Version: Milestone 1 FINAL
NOTE!!! THIS VERSION HAS THE MIUI TOOLBOX
Click to expand...
Click to collapse
How To Flash
Place ROM onto phone storage
Reboot to recovery
Make a Nandroid
Install Rom: Wipe INSIDE ROM
When you select "Reboot Not", you'll get a CWM error, IGNORE IT
Install OPTIONS or Gapps
WIKI/FAQ Located: To be reworked
Click to expand...
Click to collapse
Bugs??:
KNOWN ISSUES:
Videocamera : Use VideoCam Illusion
Slight Lag possible on screen transitions
USB tether
Some theme bits cause FC.
The graphics related issues are due to not having proper drivers to use for this. Don't ask for an ETA on a fix. Moto won't be giving us the drivers, so there is no fix
If you need to report a NEW bug, report it once, and the next TWO people VERIFY it. I don't need everyone reporting same bug 20 times. I you can, provide me the following information:
Version you're using
What type of fwipe you did and what ROM you came from
Have you restored any data from something like Titanium Backup
What app is misbehaving and what you were doing when it started
Logcats<--THIS IS PREFERRED.
If you don't know how to logcat, go HERE and learn. This really nice guy took the time to write out a good how to
When you have a LOGCAT and would like to post it, please go to pastebin and post it in there, then LINK that location in this thread...I don't want to see them posted directly in here.
Click to expand...
Click to collapse
Downloads:
Rom file is located HERE
Options Chooser is Located HERE
My latest CWM: V1 as well as Aroma-Prep
can be downloaded HERE
Click to expand...
Click to collapse
Credits:
MIUI.us-For this most Excellent Rom
scott.hart.bi=for helping me with source building
Jokersax11-for being my initial inspiration on Photon, being a cool guy, and helping me along in my early days
Amarullz=for creating the Aroma Installer
Spleef-for collaborating on those first builds that got me into Android and initial MIUI Ports
Stevendeb25-for his help with my first ports in Atrix
Alcapone263-for donating an Atrix coming to a home near me
Proxisuser-For the Guide we initially used on these builds
All my testers and users (especially ATRIXXIRTA, LoanerDave, and Unforgivenmercy)
Anyone else I may have forgotten
Click to expand...
Click to collapse
Kernel Source: HERE
Click to expand...
Click to collapse
See Post 2 for More Info
CHANGELOG
Remember Everyone...not ALL of these will apply to our devices
2.12.7
Full changelog MIUI ROM 2.12.7
[Phone]
Optimization reduced the volume of notification tone during a call
Optimization country code is prohibited from inputting while customizing attribution
Fixed inaccurate call duration shown during a call
Fixed keyboard cannot pop up during the “Call before editing” function
[Messaging]
Fixed SMS type prompt error in the SMS input box in some cases
Fixed insufficient number of contacts are recommended while creating a new message
[Lock screen, status bar, notification bar]
Fixed lock screen music interface playback status display error
Fixed lock screen variety frame display error caused by zooming
[Theme]
Optimized batch conversion processing of old theme packages
Optimized reduce the size of the storage space occupied by imported themes
Optimized sorting of recently downloaded local resource list
Optimized theme list loading speed
Fixed pages sometimes can not be loaded after clicking on recommended themes
Fixed inconsistencies between local themes state and online theme state
Fixed old files are not deleted when updating
Fixed user is not prompted to restart the phone when applying a new font
Fixed current application is not displayed correctly while running mix and match modules
Fixed in some cases clicking the "Write a review" button does not give any response
Fixed quickly switching ringtone length results in a display error
Fixed setting the lock screen wallpaper to the same as your desktop wallpaper causes the desktop wallpaper enlarged
Fixed local ringtones list page is not in accordance with the ringtones in "My Downloads" and “Default ringtones”
[Gallery]
Added the blacklist mechanism to automatically filter and hide common ads and cache albums
[Compass]
Fixed calibration failure in some non-Xiaomi phones
[Anti-disturb]
Fixed when adding the blacklist and importing log, inadvertently tapping the screen leads to cancel the import
[Notes]
Fixed when alarm volume is muted, notes reminder will FC
Click to expand...
Click to collapse
2.11.30
Update highlights of MIUI 2.11.30
1. New location services on MIUI Voice Assistant (for Chinese users)
2. Enhanced lock screen loading speed (less lag than previously, wallpaper will not show before unlock)
3. Search history can be shown in App Market.(for Chinese users)
Full changelog:
[Messaging]
Fix MMS thumbnail display problems in certain circumstances
Optimised E-mail, URL sent via SMS can be added to the contact info of senders easily
[Themes]
Fix photo frame and clock skin cannot be changed
Added support for the theme ratings and reviews
Optimise to hide theme temporary files to prevent images in the temporary files folder appearing in the gallery
Fix in some cases, theme status displays incorrectly after being downloaded
Fix some theme modules fail to be applied
[Lock screen, status bar, notification bar]
New variety lock screen framework support, delay unlock (animation playback before unlocking)
Fix variety lock screen framework, the sliding control state results in errors in some cases
Optimised lock screen loading speed
New in variety lock screen framework, added state variables of sliding components unlocking target point variables
Click to expand...
Click to collapse
screenshots
screenshots
Click to expand...
Click to collapse
* also a big thanks to qbking77 for putting together review and how to videos for us his channel can be found here: http://www.youtube.com/user/qbking77/featured
how to video:
review video:
Wow.. briliant mod...
beautiful work as always bud
Sent from my MB855 using xda premium
thanks for your work
i will test and keep reporting
thanks
First off love the ROM.
So in the other thread someone was saying how TiBu was requesting root over and over. I've actually seen the same issue since 2.5.4. It appears Superuser isn't remembering who it gave access to. Just to prove it I downloaded easy root checker. Clicked Verify root. Superuser prompted for permission on behalf of root checker (and I left remember this app checked) and I clicked ok. I clicked verify root again and it prompted again. Previous to 2.5.4 it seemed like superuser wasn't in use, and Permission Manager was the default root management on MIUI. Permission Manager requests root upon every reboot, and with the manage root option selected doesn't manage root. If you'd like any other information just lemme know (I feel bad just asking seeing as I'm a developer, but have zero experience in the Android ROM world and don't know where to start)
Edit:
Forgot to mention I've done no wipe, full wipe, Aroma, and Standard and I'm still seeing the issue. I'm going to try switching ROMs and switching back now to see what happens.
I use the standard version, and got the Super User permission loop error. I tried open Titanium Backup Pro and was promted to allow/deny the request. However I decide, it just keep pop up asking, and only stop when I FC the app. When I check the Super User permission, it have like 10 entries of the same app.
That's the 1st impression for 5 min with the new build
Th3bill, I would do a log of the wifi error but I already went back to my cm7 rc1. What do I do to log so next time I test, I can do it for you guys?
fakeasdf said:
First off love the ROM.
So in the other thread someone was saying how TiBu was requesting root over and over. I've actually seen the same issue since 2.5.4. It appears Superuser isn't remembering who it gave access to. Just to prove it I downloaded easy root checker. Clicked Verify root. Superuser prompted for permission on behalf of root checker (and I left remember this app checked) and I clicked ok. I clicked verify root again and it prompted again. Previous to 2.5.4 it seemed like superuser wasn't in use, and Permission Manager was the default root management on MIUI. Permission Manager requests root upon every reboot, and with the manage root option selected doesn't manage root. If you'd like any other information just lemme know (I feel bad just asking seeing as I'm a developer, but have zero experience in the Android ROM world and don't know where to start)
Edit:
Forgot to mention I've done no wipe, full wipe, Aroma, and Standard and I'm still seeing the issue. I'm going to try switching ROMs and switching back now to see what happens.
Click to expand...
Click to collapse
I just noticed that myself. I'm working on some stuff for Kitchen Sink, then I will devote some time to this issue. It seems like the permission gets granted for the given session, then forgets. I even checked the log within the superuser apk, and it shows it requesting my permission and granting root explorer permission the 6 times I just did...LOL
Don't feel bad making a recommendation. That's how I got to doing what I am now. 3 months ago, I didn't know any of this, so ya never know...maybe you'll be dev-ing before you know it I am open to any and all RESPECTFUL comments or concerns. That is my one requirement...
Do themes fully work on this one? I remember the past version didn't.
Your work is brilliant and the ROM is amazing, but here are some issues i found, which you could add to the 'not working' in the first post.
-The fingerprint sensor doesn't work (no surprise)
-The camera force closes when switching to the camera to the front and back (but when you open the camera app again, it has changed the camera to the front/back)
kantm said:
I use the standard version, and got the Super User permission loop error. I tried open Titanium Backup Pro and was promted to allow/deny the request. However I decide, it just keep pop up asking, and only stop when I FC the app. When I check the Super User permission, it have like 10 entries of the same app.
That's the 1st impression for 5 min with the new build
Click to expand...
Click to collapse
I will work on it as soon as I get a chance. Sorry about this
berryman13 said:
Do themes fully work on this one? I remember the past version didn't.
Click to expand...
Click to collapse
SOME of the themes work. There are very few FULLY functioning V4 themes at this time. 2 were posted on the old thread. If you look there, you can see them
Th3Bill said:
SOME of the themes work. There are very few FULLY functioning V4 themes at this time. 2 were posted on the old thread. If you look there, you can see them
Click to expand...
Click to collapse
thanks for the quick response
HMZX said:
Your work is brilliant and the ROM is amazing, but here are some issues i found, which you could add to the 'not working' in the first post.
-The fingerprint sensor doesn't work (no surprise)
-The camera force closes when switching to the camera to the front and back (but when you open the camera app again, it has changed the camera to the front/back)
Click to expand...
Click to collapse
I just realized that I put the camera from the Photon build in it. I will replace the apk when I re-up for the su issue that I am working on as well. It will take till this evening, as I am at work and the wifi here sucks
Thanks for being patient everyone. Rest assured I will work on all the issues as I get a chance
Th3Bill said:
I just realized that I put the camera from the Photon build in it. I will replace the apk when I re-up for the su issue that I am working on as well. It will take till this evening, as I am at work and the wifi here sucks
Thanks for being patient everyone. Rest assured I will work on all the issues as I get a chance
Click to expand...
Click to collapse
I will flash the instant you get the new build up, very excited to try miui again!
FIXES ARE UP!
Camera
SU (this one I tested on Photon...fixes the issue with recurrent SU requests)
Jokersax.com under the Mods section of Th3Bill (look in Atrix mods)
CHEERS!
I have the build redone and will be re-upping it tonight. For now, these 2 fixes should correct the issues
here's one fully functional theme that im using http://miuiandroid.com/community/th...01-for-miui-ics-builds-update-02-05-12.16417/
For some reason memory card access on PC won't work?
Also overall the rom feels quite laggy, though I know it's supposed to be as smooth as butter. Help anybody?