I've searched all over today, but I have only found a couple of threads on the issue, none of which seemed to give a clear answer. I now have my first Android phone (Atrix). I love the customization potential of the platform, but it seems a little choppy at times on the graphical side of things. What I want to know is this: is it possible to create an Android rotation effect, such as the iPhone has when switching between portrait and landscape modes? Can this be achieved with simple root access and development, or would it take a custom kernel? Are there any themes or ROMs which provide this possibilty. I know I can't run a custom kernel on the Atrix, but I'd still like to know, for future referenece. Thanks!
Only thing I've ever heard is that as it's a feature of honeycomb do we may see it added either in honeycomb roms or ported into gingerbread from honeycomb. Obviously we'd need Google to release the code first.
Sent from my DHD
Okay, thanks. That's good to know.
Related
And searching for them here brings up all kinds of posts that just... blow my mind.
Background:
I rooted my NC a couple days ago using Autonooter 3.0 for 1.1
My questions are:
1. Is there much of a difference between this and Honeycomb? I mean i'm aware of visual differences but does one run better or have any advantages?
2. What are all the different variations on the developer page? Not clockwork recovery but if you click over the entire first page is just a long list of different versions/different ways to root. Any of those better than the other? Or is it just 20 different ways of accomplishing the same thing.
3. Do any of those versions support web video? I know I now have a youtube app but I still can't watch videos on any other sites.
4. Why don't all apps show up in the marketplace? Is there a workaround for this? For example the first time I rooted from 1.0.1 I could access Angry Birds. Now the only one that shows up is the seasonal one...
5. If I go ahead and install the newest version of Froyo (6.6) will I have access to the Market from the start or am I going to have to go into command line and all that other stuff? I'm comfortable with the flashing and installing but as soon as you get into that I might as well be reading Russian...
I know I have more questions but I can't think of them currently. Any and all help is much appreciated.
jrob9583 said:
And searching for them here brings up all kinds of posts that just... blow my mind.
Background:
I rooted my NC a couple days ago using Autonooter 3.0 for 1.1
My questions are:
1. Is there much of a difference between this and Honeycomb? I mean i'm aware of visual differences but does one run better or have any advantages?
2. What are all the different variations on the developer page? Not clockwork recovery but if you click over the entire first page is just a long list of different versions/different ways to root. Any of those better than the other? Or is it just 20 different ways of accomplishing the same thing.
3. Do any of those versions support web video? I know I now have a youtube app but I still can't watch videos on any other sites.
4. Why don't all apps show up in the marketplace? Is there a workaround for this? For example the first time I rooted from 1.0.1 I could access Angry Birds. Now the only one that shows up is the seasonal one...
5. If I go ahead and install the newest version of Froyo (6.6) will I have access to the Market from the start or am I going to have to go into command line and all that other stuff? I'm comfortable with the flashing and installing but as soon as you get into that I might as well be reading Russian...
I know I have more questions but I can't think of them currently. Any and all help is much appreciated.
Click to expand...
Click to collapse
I won't be too helpful here but since you have no replies yet...
1. Honeycomb is more functional for tablet devices, it has the notification bar on the bottom with back and menu buttons by default, it has multipane apps and new widgets and other new functions.
2. I am not sure what you are talking about here.
3. Froyo and newer support web video via flash player 10. If you can get it installed, some people have difficulties.
4. It has to do with your device ID. Google for some reason can block apps that they don't think you need on your particular device. It's good for somethings because you don't want to see GPS centric apps on a device with no GPS but it blocks lots of useful apps too. There is a way to fix it by tricking the market into thinking you have a phone like DROID. Not sure why devs don't do it thought.
5. Rom makers aren't putting the market into their roms. Google has a problem with it and has sent Cease and Desist letters to people who do it. You can install the market afterwards.
Any thoughts on why the OTA ICS upgrade enables the Develop option menu? Possibly AT&T mistakenly pushed it out, or did so on an extremely limited basis for testing purposes? Surely they wouldn't want just anybody messing with those settings. The Android version number is strange too, 4.0.3 710RD, when I see RD makes me think research & development.
No problems here, just wondering out loud.
I have seen this option on the Galaxy Nexus. I do believe it is a standard option for ICS.
Oh, I had assumed from the nature of the options inside and the fact that it seems to be at best awkwardly translated that it was a menu which was normally unavailable. A lot of older phones used to have secret menus like that unlocked by some convoluted series of actions.
ransack said:
Any thoughts on why the OTA ICS upgrade enables the Develop option menu? Possibly AT&T mistakenly pushed it out, or did so on an extremely limited basis for testing purposes? Surely they wouldn't want just anybody messing with those settings. The Android version number is strange too, 4.0.3 710RD, when I see RD makes me think research & development.
No problems here, just wondering out loud.
Click to expand...
Click to collapse
I've been wondering about the version myself...
Not sure if enabling it was intentional, but I know I found the "Stay Awake" option to be useful. Keeps the screen on while charging unless I turn it off using the power button.
It helps when using the phone at my desk as an audio player.
-Brett.
Also if u mess with the window animations and the other one below it ....u can turn it up to like 5x I believe it makes cool transitions on the windows and menus..
It's intentional, a feature (if you will) built into ICS. It's a part of AOSP builds as wel so it's ultimately up to the Mobile phone companies to leave it or not.
These are pretty standard on just about every ROM out there for pretty much all phones since Jelly Bean, and yet we still dont have the ability to add in more nav buttons or change around the order of them or anything on a single Nexus 6 ROM. We just barely seem to be getting the ability to change the height and I even saw one ROM that could change what happens on long press to one of the buttons. Yet no significant customization for even moving around the order of the 3 stock buttons. Do we have some issue on the N6 that is causing developers to not be able to implement this feature?
It'll come. But jeepers, the device is only a month and change in people's hands.
The feature is coming into the works, there are more important features than customizing the navigation bars.
The developers do the work as a hobby and for free. If you wanted to, you can contribute, otherwise wait.
EniGmA1987 said:
Do we have some issue on the N6 that is causing developers to not be able to implement this feature?
Click to expand...
Click to collapse
Probably a few issues causing this.
First the phone came out a bit over a month ago, and was quite hard to get for a large portion of that time. Some devs didn't get their device until recently.
Second, they perhaps haven't had a lot of time recently to get to working on their custom ROM. This isn't their job, they have families, jobs, school and perhaps other things that are more important than working on their ROM. There have been a lot of holidays the past month or so, which also impedes them.
Third they need to plan. Look at what Lollipop has changed, what new things they can work on + what things they should bring back from their previous work. Perhaps they don't see navigation bar customization as a priority over the stuff they are working on. There is a lot of things that I would like to see that custom ROMs haven't touched for the most part. Reorganize the notification toggles for example. Navring edits. Lockscreen customization. And probably 50 other things that were standard on many 4.X ROMs. I am sure we will see eventually, that were included in many custom ROMs for Kitkat and other older OSes plus some new fun things (Ambient Display customization maybe).
Perhaps they are buying into the rumors that 5.1 is coming very early next year. And don't want to risk putting a lot of effort into 5.0.X when 5.1 could break whatever it is they have done. While this isn't likely a real cause in this instance, in other forms of development this has given some developers pause.
tl;dr: Patience is your friend. Hide the navbar and get a navbar replacement if you can't wait, I think LMT works.
zephiK said:
The feature is coming into the works, there are more important features than customizing the navigation bars.
The developers do the work as a hobby and for free. If you wanted to, you can contribute, otherwise wait.
Click to expand...
Click to collapse
No need to be a ****, I was asking a serious question on if there were some limitations of the N6 framework that other devices dont have to deal with. Its not a complaint exactly, but a request for information on the issue. I have been through a LOT of devices over the last few years and all other devices I have seen get the feature even when they are brand new within a week or two of being unlocked. So it just seems like maybe there was an issue with significant changes to the OS framework causing developers to not be able to copy most of the code or something.If it is simply that no developer thinks it is a priority then that's fine, I was just wondering the reason.
Softkeyz (app in the play store) is working on adding lollipop support. It's a great nab bar app that I used on my Nexus 7.
EniGmA1987 said:
No need to be a ****, I was asking a serious question on if there were some limitations of the N6 framework that other devices dont have to deal with. Its not a complaint exactly, but a request for information on the issue. I have been through a LOT of devices over the last few years and all other devices I have seen get the feature even when they are brand new within a week or two of being unlocked. So it just seems like maybe there was an issue with significant changes to the OS framework causing developers to not be able to copy most of the code or something.If it is simply that no developer thinks it is a priority then that's fine, I was just wondering the reason.
Click to expand...
Click to collapse
I wasn't being one. Users tend to criticize or be impatient for certain features that isn't present. @cupfulloflol said the same thing I did but elaborated more into detail so if the lack of details is what makes me what you call me then I apologize. I was getting straight to the point without the bonuses.
All I'm saying is that these developers are working for free and doing what they do as a hobby without being motivated by a salary. Features are being incorporated on a day-to-day basis, you just have to wait. Its one of the trade offs of having the newest and latest, you'll have to wait.
My point still stands, if you want to contribute and implement the customization for navigation bar then you can do so. There are tutorial guides on how to remap the buttons on the navigation bar in the themes & apps section, you can do them yourselves or port code from Kit Kat onto Lollipop on navigation bar customizations.
Hi, i was wondering if you guys think there will be a modded apk for you phone that unlocks certain features,
such as being able to handle it while driving, screen mirroring, and opening other apps that a not natively approved(youtube comes to mind).
Thanks in advance.
First of all, I'm not a developer, so if my comments don't contribute, it's just me being blond.
I'm was just looking for a Waze/Android Auto solution, as it looks like their announcement to come "soon" takes ages, if it ever will ...
And found this :
slideshare.net/j796160836/first-meet-with-android-auto?next_slideshow=1
github.com/googlesamples
github.com/googlesamples/android-UniversalMusicPlayer
github.com/googlesamples/android-MediaBrowserService
github.com/googlesamples/android-MessagingService
So it looks like it is possible to build your own Android Auto application.
If so, there should be a way to decompile fi Waze and add the necessary code, no ?
Many people complain about this and seems like few know about the issue. I should say that I'm not a dev, I just figured it out and tired of writing it after each complaint, which is why I write it as a new thread.
So, in short, there are ways in which gcam speaks with the camera. With RN8(t), we need the app use raw10 rather than raw_sensor for us to be able to have photos. This means that you need a version which either shoots with raw10 by default, or lets you switch from raw_sensor to raw10.
Sadly(?) there are not many that allows this, and almost all are version 6.x ones except Nikita's. The modders I found that allow switch or use raw10 are Nikita, overwhelmer, fu24, wyroczen, and trCam of tigr. There can be others, these are just those that I found. and I did not try each and every one of them. So if you are suffering from this problem, go for these modders' versions.
I may add that I like to use Parrot043's mod, as its output is practically what I want, yet unfortunately it is not usable without raw_sensor. Like his/hers, Arnova8G2's, BSG's, and many others' mods don't (didnt?) work. Yet as they are making new builds every now and then, maybe they will include a switch later on.
I should note that neither of those that I tried can do (good) astrophoto - or it was the case for me. Also none of these managed to produce good shadows (shadows in both Photoshop sense, shadows as shadows, and the transitive area between blacks and whites). On the other hand, it can be a problem with my device as I have seen people shooting pretty fine photos with these - including, interestingly, astrophotos. I just try and wrote my experience. Do NOT rely solely on my experience. Go and try for yourselves. This is just a starting point for those of you that have the problem, not an ultimate guide.
About auxiliary cameras, I cannot say much as I had them working at some point (with a fix from PA devs, I forgot the name of the dev and the patch sadly, and with fu24's version), yet now again they are broken. Funny part is that Paranoid Android claims to have them all working from the start, and other than me, I saw no one complaining that wide and macro don't work. Probably something is broken with my mobile, which is why I cannot say much on the issue.
Of the custom ROMs, I have found only Paranoid Android allowing shooting with raw_sensor. It might be the case with some other ROMs, so you better go check it out for yourselves as well. I can confirm that Pixel Experience and LineageOS did not allow shooting with raw_sensor, but it can change as well. Everything, as we know, comes down to the devs. This is just my experience, and I do not test each and every ROM every other day.
I hope that this will be useful for you, and there won't be complaints about pink/purple lines. This is because of GCam, not ROM builders as such. You can, surely, "force" the ROM builders to include raw_sensor shooting, yet it's up/down to them to do it or not.
So, I hope that this will help you to have a better idea about the problem, and you can solve it easily/easier.