Develop Bugs

A good reason not to upgrade to the new Market in Froyo

Market filters:
When a user searches or browses in Android Market, the results are filtered, and some applications might not be visible. For example, if an application requires a trackball (as specified in the manifest file), then Android Market will not show the app on any device that does not have a trackball.
The manifest file and the device's hardware and features are only part of how applications are filtered — filtering also depends on the country and carrier, the presence or absence of a SIM card, and other factors.
Changes to the Android Market filters are independent of changes to the Android platform itself. This document will be updated periodically to reflect any changes that occur.
Click to expand...
Click to collapse
Does anyone have any idea what the market filters are checking against?

That's not really a good reason to do anything, let alone not using 2.2

dik23 said:
That's not really a good reason to do anything, let alone not using 2.2
Click to expand...
Click to collapse
Not being able to get apps? Did you read the link? Doubtful. Uh sure. Have fun with vanilla 2.2 and 0.0 apps.

I'm sorry, did you read your own link? If you had scrolled down, it shows several examples of what can be filtered. The filters are implemented by the application developer themselves, and if they don't, they still show up in the market.
Besides, filtering by the application has been in Android since 2.0. Any application that deems a device incapable of running it (for example, a lack of a light sensor) can stop itself from running.

some kind of filter (the ones I've heard of so far are incompatible screen resolution, unverified builds, and protected apps) is already being applied to 2.1 in the AOSP build. I couldnt see Yelp, the Android Community and TMZ apps for whatever reason

cashless said:
Not being able to get apps? Did you read the link? Doubtful. Uh sure. Have fun with vanilla 2.2 and 0.0 apps.
Click to expand...
Click to collapse
Oh yeah, how suspicious. French people couldn't possibly prefer apps in French and people with that new Dell pad thing probably still want SMS and contact apps.
Yeah

so you are saying not upgrade to 2.2 because marketplace will filter apps for our phone, but stick with 2.1 because it doesn't?
well genius, why don't you go and install http://www.appbrain.com/app/com.yelp.android on your phone and let us know how that 'no filtering' works out for you.

When I was running my Vougue we ran into this problem as well, its not a big deal at all. from what I remember it was checking about the build.prob and screen size that is setup in your startup. what I used to do was set my phone to my the specs for the G1, then install the apps after adjusting the density to fit everything on screen and then reboot using factory startup. it worked pretty well for most of the apps since many only blocked off whatever border the developer had.
heres the problem though but with the pace we are going it wont come up for a while, once we decide we have a rom stable enough to flash we lost the abilty to change the settings since WM is copletely gone and no haret was used. I switched over to the Touch Pro and we had the exact same problem which was solved in the EXACT way but we were not flashed still(TP2 still has a LOOOONG way to go sad to say), kept the touch pro 2 for only a few weeks before they replaced my Sprint Line TP with a Touch pro 2 due to all the TP1 problems and i'm still saddened by the slow progress. I am a developer myself and even an avid budsmoker and was still able to help out. now Refer has done a great job but from my understanding he is just doing most changes to the Android Filesystem, theirs a couple other guys working on the kernels which would be were all the hardware problems are going to be fixed from. no matter what build we use something in the kernel is either not right, or we dont have the driver in place for Android itself and since we have few Hardware level developers working on these things it seems to be low progress.

[Q] Why is my phone cooler than my tablet?

Why is my phone cooler than my Kindle Fire tablet? I don't mean hardware. My phone has obviously better hardware than the Kindle. What I mean is why do apps behave differently, in fact better, on my phone than on my KF?
As an example, the Kindle Reader app on my phone shows a book browser within the app when I search for books. On the KF when I want to browse books, the app opens up Amazon's web site in a browser (not the nicest of interfaces for a small screen).
Another example is the Dolphin browser. On my phone, pressing the back button (on this web site for example) actually goes to the previous page whereas on the KF I have to press the back button at least twice and often more in order to get to the previous page; sometimes I have to time it just right, too.
There are a lot of little things like those examples that make my phone cooler in spite of its significantly smaller screen.
In case it matters, I have CM10.1 Android 4.2.2 on the KF and the phone has stock Google Android 4.2.2 that came with the phone. All the apps are presumably the same, having been download from the Play Store.
Can anyone explain this difference? Thanks.

pfederighi said:
Why is my phone cooler than my Kindle Fire tablet? I don't mean hardware. My phone has obviously better hardware than the Kindle. What I mean is why do apps behave differently, in fact better, on my phone than on my KF?
As an example, the Kindle Reader app on my phone shows a book browser within the app when I search for books. On the KF when I want to browse books, the app opens up Amazon's web site in a browser (not the nicest of interfaces for a small screen).
Another example is the Dolphin browser. On my phone, pressing the back button (on this web site for example) actually goes to the previous page whereas on the KF I have to press the back button at least twice and often more in order to get to the previous page; sometimes I have to time it just right, too.
There are a lot of little things like those examples that make my phone cooler in spite of its significantly smaller screen.
In case it matters, I have CM10.1 Android 4.2.2 on the KF and the phone has stock Google Android 4.2.2 that came with the phone. All the apps are presumably the same, having been download from the Play Store.
Can anyone explain this difference? Thanks.
Click to expand...
Click to collapse
The phone's hardware was designed with 4.2.2 in mind and the Kindle was designed for a forked rendition of GB.

Guitarman2010 said:
The phone's hardware was designed with 4.2.2 in mind and the Kindle was designed for a forked rendition of GB.
Click to expand...
Click to collapse
Then perhaps I do not understand what Android is. I was under the impression it was an OS with a defined API such that it would look (theming aside) and behave the same on different hardware (with obvious exceptions like not having bluetooth functionality on KF). Your statement would indicate that it is very heavily hardware dependent and that somehow app developers take into account the plethora of different hardware platforms and choose to behave in different manners on different devices. If this is the case, then it's an illogically designed system.

pfederighi said:
Then perhaps I do not understand what Android is. I was under the impression it was an OS with a defined API such that it would look (theming aside) and behave the same on different hardware (with obvious exceptions like not having bluetooth functionality on KF). Your statement would indicate that it is very heavily hardware dependent and that somehow app developers take into account the plethora of different hardware platforms and choose to behave in different manners on different devices. If this is the case, then it's an illogically designed system.
Click to expand...
Click to collapse
Running 4.2.2 on a system that was meant for GB results in some things not working right....

pfederighi said:
Why is my phone cooler than my Kindle Fire tablet?
...
Another example is the Dolphin browser. On my phone, pressing the back button (on this web site for example) actually goes to the previous page whereas on the KF I have to press the back button at least twice and often more in order to get to the previous page; sometimes I have to time it just right, too.
...
Can anyone explain this difference? Thanks.
Click to expand...
Click to collapse
The browser thing I think can be explained. If you are zoomed in on a page, if you press the back button, it will zoom out to the whole page. The second tap of the back button takes you back to the previous page.
Does this help / make sense?
sent from The Muffinator (it's a kindle fire running cm10.1)
using Tapatalk 4 beta, and loving it!

jma9454 said:
The browser thing I think can be explained. If you are zoomed in on a page, if you press the back button, it will zoom out to the whole page. The second tap of the back button takes you back to the previous page.
Does this help / make sense?
sent from The Muffinator (it's a kindle fire running cm10.1)
using Tapatalk 4 beta, and loving it!
Click to expand...
Click to collapse
That would make sense if it was the same behavior on my phone. Thanks, though.

pfederighi said:
Then perhaps I do not understand what Android is. I was under the impression it was an OS with a defined API such that it would look (theming aside) and behave the same on different hardware (with obvious exceptions like not having bluetooth functionality on KF). Your statement would indicate that it is very heavily hardware dependent and that somehow app developers take into account the plethora of different hardware platforms and choose to behave in different manners on different devices. If this is the case, then it's an illogically designed system.
Click to expand...
Click to collapse
pfederighi said:
That would make sense if it was the same behavior on my phone. Thanks, though.
Click to expand...
Click to collapse
I think you're missing the point. The Kindle Fire was never made to run apps from the Google app store, and Google Play apps are rarely made for a modified Kindle Fire, running JB, and a custom kernel made from the ground up. Android is versatile, but it's not perfect. There are many apps that work well on some devices but not others. Looking at the reviews of any app in the Play store should be enough to convince you of that.

Guitarman2010 said:
Running 4.2.2 on a system that was meant for GB results in some things not working right....
Click to expand...
Click to collapse
Why? Does the Android code really have such code as:
if (running_on_older_hardware)
{
make_all_apps_less_cool(); // because we only like newer hardware, even if it's possible for the older hardware to function
}
What little I know of OS design is that if you want your OS to be used aon a wide variety of hardware (which seems to be the design goal of Google in their relentless pursuit of world domination), the API should be as hardware independent as possible and that all hardware access should be done through the API. The very fact that (most) apps are written in Java and compiled to bytecode dictate that they have to use the API. Is the functionality difference because there is some sort of proprietary ROM that Android and certain apps know about that doesn't exist on the KF? And this ROM makes apps behave cooler?
Is it a memory issue? Does 4.2.2 expect to have a different memory/segmentation model? Or a different cache model? Or simply ungodly amounts more memory?
The only runtime software difference I could tell between my phone and my KF is that the per app memory limit on the KF is set to 256 MB whereas on the phone it is 512 MB.
Are there dynamic libraries/frameworks/apks on my phone that are not included in stock/CM10.1 4.2.2 that most apps are aware of and use? Can I copy them to the KF?
Thanks.

pfederighi said:
Why? Does the Android code really have such code as:
if (running_on_older_hardware)
{
make_all_apps_less_cool(); // because we only like newer hardware, even if it's possible for the older hardware to function
}
What little I know of OS design is that if you want your OS to be used aon a wide variety of hardware (which seems to be the design goal of Google in their relentless pursuit of world domination), the API should be as hardware independent as possible and that all hardware access should be done through the API. The very fact that (most) apps are written in Java and compiled to bytecode dictate that they have to use the API. Is the functionality difference because there is some sort of proprietary ROM that Android and certain apps know about that doesn't exist on the KF? And this ROM makes apps behave cooler?
Is it a memory issue? Does 4.2.2 expect to have a different memory/segmentation model? Or a different cache model? Or simply ungodly amounts more memory?
The only runtime software difference I could tell between my phone and my KF is that the per app memory limit on the KF is set to 256 MB whereas on the phone it is 512 MB.
Are there dynamic libraries/frameworks/apks on my phone that are not included in stock/CM10.1 4.2.2 that most apps are aware of and use? Can I copy them to the KF?
Thanks.
Click to expand...
Click to collapse
Proper communication between the API and the hardware is still dependent on the kernel. Considering your phone's kernel was likely produced by a team of paid programmers and the KF's 3.0.x kernel was made by maybe a small handful of people with most of the work done by one man, for FREE, I'm sure there is plenty of possibility for something not working as efficiently as it could.

soupmagnet said:
Proper communication between the API and the hardware is still dependent on the kernel. Considering your phone's kernel was likely produced by a team of paid programmers and the KF's 3.0.x kernel was made by maybe a small handful of people with most of the work done by one man, for FREE, I'm sure there is plenty of possibility for something not working as efficiently as it could.
Click to expand...
Click to collapse
And I truly do appreciate the hard work of the many hackers who put together kernels, boot loaders, recovery programs, apps, etc. I hope someday to join their ranks.
I was under the impression that there was a stock kernel as well as a stock OS and that the only real difference from one system to another was the boot procedure and the selection of drivers (with stubs or emulation for missing hardware/features). I take it that then this not the case.

General GNex(GSM) help

I do not do too much in the way of making anything.
Although, i do seek out whatever files such as
¤ROM's
¤Radios
¤Boot loader
¤Apps
¤Kernels
¤Recoveries
¤Programs(tool kits, auto-root, Odin, etc.)
¤ADB too
¤Boot Animations
I do keep most of what i find for the GNex(GSM Google play "edition").
I am always flashing and running tests against things that need to see how well they work where i live(tx) for t-mobile which is the same, of course, as at&t,and metro PCS in my area.
¤¤I just keep a fresh ROM which i feel it gives me the ability to help people who are just starting out on flashing and rooting.
Message me for important questions.
Post for general "troubleshooting".
I wont link in board. arrangements can be made though.
I will do my best to keep an eye on here.I don't plan on using the App but A am just a browser away.

What I keep "constant".
The screen shots i took show a few constants.
¤Keep to newer ROM's mainly because i was gathering too many Gigs.
¤I did not notice any big change in boot loaders so i stick to the newest one
¤I use the the newest RIL and Base Band (there are apps to help)
i did notice i change in changing these in *#*#4636#*#*.
i wouldn't go digging around in there if you don't know what to look for
¤No Google framework flashed.(too much signing in) i use 3rd party apps to keep updates
i also save my phone book to a .vcf and import it to phone.
*not suggested*
¤Total-commander app and windows or Linux program help.
¤AOSP is a must for a back up ROM.
¤I found a kernel i personally like. i find a way each time to get it to work with changing ROM's

What I have broken and fixed
Last but not least...what i have put this phone through, and what i have brought it back from.
¤Hard-Bricked in all sorts of ways
¤Soft-Bricked even more ways
¤Failed ROM flashes due to missing a step
¤¤*when i first started learning i lost my radios network info. required to connect to anything through RIL....
¤¤*figured out a way that worked on getting it back without racking my head inside files sifting through code*
¤i know a few work around when it comes kernels
¤i don't use Google framework anymore, there are benefit.
¤rooted every way i could find, including ADB pushes.
¤some tool-kits(though not suggested). the GUI is normally easier to manage.
¤Odin of course. Heimdall when applicable
¤Apps for Apps....without too many Apps slowing do the phone
*~*~*~AOSP*~*~*~AOSP. i cannot stress that enough.
I have put this phone through whatever i can find and it still work just fine.coming out on top with this phone is the only option.
Ask, ask, ask....many of us (i believe) do this because its interesting.

[Q] Un-Root My aftv?

I bought two rootable FireTVs the day after xmas at Staples, and promptly rooted one. The other is safely tucked away in my *doomsday bunker* still sealed, waiting for armageddon.
During the rooting process I determined that I lack the attention span / ambition to install the necessary boot menu / rom manager and manually update the firmware in order to have an up-to-date stb. So, my question is twofold:
1) If I re-enable updates and remove the dns blocking, will my aftv gracefully update itself? I've already uninstalled SuperSU as I don't believe I need it.
2) Assuming the box is running the latest official rom, will the following (sideloaded) apps still work?
MXPlayer
FiredTv
DirecTV App
Android Terminal Emulator
I have also built my own simple smb folder navigation app, so obviously the ability to run apps from unknown sources is needed also. Correct me if I'm wrong, but I believe that's available on all FireOS versions.
I guess I have low standards, but this is really all I need for the box to be useful to me. I absolutely love the thing, save for the fact that the DirecTV App doesn't like the android version presumably because I never applied any updates.

spfautsch said:
I bought two rootable FireTVs the day after xmas at Staples, and promptly rooted one. The other is safely tucked away in my *doomsday bunker* still sealed, waiting for armageddon.
During the rooting process I determined that I lack the attention span / ambition to install the necessary boot menu / rom manager and manually update the firmware in order to have an up-to-date stb. So, my question is twofold:
1) If I re-enable updates and remove the dns blocking, will my aftv gracefully update itself? I've already uninstalled SuperSU as I don't believe I need it.
2) Assuming the box is running the latest official rom, will the following (sideloaded) apps still work?
MXPlayer
FiredTv
DirecTV App
Android Terminal Emulator
I have also built my own simple smb folder navigation app, so obviously the ability to run apps from unknown sources is needed also. Correct me if I'm wrong, but I believe that's available on all FireOS versions.
I guess I have low standards, but this is really all I need for the box to be useful to me. I absolutely love the thing, save for the fact that the DirecTV App doesn't like the android version presumably because I never applied any updates.
Click to expand...
Click to collapse
Be careful with the doomsday bunker firetv. If that is Series 2 in serial, you may not be able to root it. If its series 3. Ex (70900305 or 303) then you can do the Ethernet trick and root it. I'd say remove that out, root it as soon as possible and put it back in the safe. I've done just that.
Now to answer your question. I doubt you need root for what you are doing but someone else may clarify. I highly recommend keep and follow up with root. Android Rom is around the corner and features like quick support for remote desktop etc have immense benefits.

navigates said:
Be careful with the the doomsday bunker firetv. If that is Series 2 in serial, you may not be able to root it.
Click to expand...
Click to collapse
Not sure how much more careful I can be with it than setting on a shelf above my bourbon collection.
But seriously, its serial starts w/ 70900201XXXXX, are you saying its too old of firmware? If so, it sounds to me like I should let it update and put the rooted one on the shelf.
navigates said:
I highly recommend keep and follow up with root. Android Rom is around the corner and features like quick support for remote desktop etc have immense benefits.
Click to expand...
Click to collapse
I'm not sure we're on the same page w/ this. I'm very much wanting to "set it and forget it". Periodically flashing roms seems to me like the polar opposite. Reminds me of the good old days of the h-card. Life is too short to run in that exercise wheel again.

spfautsch said:
Not sure how much more careful I can be with it than setting on a shelf above my bourbon collection.
But seriously, its serial starts w/ 70900201XXXXX, are you saying its too old of firmware? If so, it sounds to me like I should let it update and put the rooted one on the shelf.
I'm not sure we're on the same page w/ this. I'm very much wanting to "set it and forget it". Periodically flashing roms seems to me like the polar opposite. Reminds me of the good old days of the h-card. Life is too short to run in that exercise wheel again.
Click to expand...
Click to collapse
Agreed with your point of view, but for my needs, I primarily need root as I use Kodi all the time. I also use quick support for remote support for my family and friends so that wouldn't work without root. Once you've got it setup with root, it stays there unless you mess it up or forgot the block or disable step. I've made a total of 22 firetv's and not one has gotten updated after I've disabled the com update.
As for the Series 2, If you try to update, it will take you to the latest version of the firmware. In old days, it would increment one. Secondly, you cannot do the removal of the Ethernet trick to make it think there is no update. If you block the updates, it will give you an error but will enforce the update. Last week, I had to make 3 firetv's for family. I had a combination of series 2 and 3. I couldn't do any of the 2's. All 3's so far were good.
The good news is that bestbuy versions are mostly series 3. The downside to series 3 is that you have to downgrade first and then go up.

Sounds like I was on base w/ the notion of letting my untouched box update and benching the rooted one until I know how my needs are served w/o superuser.
I've toyed with xbmc since well, the days when my I had to fight my kids to use their original xboxes. While I can't scoff at the quality and sheer amount of work that's been put into it, for my tastes it's always come across as an application consisting of a ton of fluff, a pound of functionality, and a half ounce of useability. I just want to watch movies. It shouldnt take 7 button presses to get to them. :-/

Security-wise, what are my options?

Hey,
I'm 100% new to doing any sort of custom stuff with my Android devices, so please forgive my dumb questions.
I've known for a while now that my Nexus 7 was vulnerable since it stopped receiving security updates in August 2016, but I wasn't terribly concerned at the time since I use it so casually. With this recent WPA2 news, though, I'm kinda anxious.
Is there any way at all to make my device secure? Google doesn't give a **** so I know there's no chance in hell it gets an official patch, so I assume I have to go with a custom ROM, but I have no idea where to start.
If I went with a custom version, will I still be able to use the apps I own? Will I still be able to use stuff like Chrome and Drive as well? Also, if I'm using a custom ROM, is there actually any guarantee that it is actually secure? How do I ensure it receives security updates in an unofficial setting?
tl;dr version: Just hoping for a way to use my Android device mostly in the same way I already do, but with actual security updates going forward, since Google are a-holes.

Be aware that some apps will refuse to run on a rooted device. You also won't be able to use Google Pay.
You can mitigate the security issue somewhat by using a VPN service; all your communications will be encrypted, so a MITM attack should fail unless they can also decrypt your communications stream.
I use PrivateInternetAccess myself; one of their app's features is the ability to bypass VPN for selected apps, so for example I can run Pokemon Go (which won't run on VPN) and avoid running video streams through VPN (I don't really care if they can see me watching Hill Street Blues on Hulu and I'd rather avoid the performance hit). YMMV and I'd recommend doing your own research, and VPN isn't a magic bullet. But it makes the WPA2 problem less urgent without a lot of work and without having to root your device.
Mind you, I'm saying all this while perusing the forums to discover what custom ROMs are available for my Nexus 7, as I'm considering rooting it.
---------- Post added at 07:49 PM ---------- Previous post was at 07:36 PM ----------
To address a different part of your question, aside from the "some things won't run rooted" issue I already mentioned, the rest of your apps should run fine. You'll want to install some version of Open GApps to get Google functionality. That's probably covered in the instructions for the custom ROM.
Two favorites are LineageOS, which has a lot of neat features added, and AOSP, which is the bare Google Android experience with neither bells nor whistles.
Keep in mind that if you don't like what you get, you can always change. So if LineageOS isn't for you, you can try AOSP, or something else if you find it. I'm assuming that somebody has the base ROM available; it should even be possible to put the stock ROM back and unroot the device. Know that I'm speaking from inexperience, sorta... I haven't done this with a Nexus yet, but I've done it lots of times with a Galaxy S4. So I'm not really an authority but I figured I could get you started in the right direction, at least. Just remember to back up everything on your device before you start.
Really, really be sure you back up before you start.

I'm having this conundrum as well. I currently use MM on my Nexus 7 2013 due to better idle time and more reliable WiFi. It seems like there is no way to fix this vulnerability without moving to Nougat.

Lineage OS is a good rom to start with. It receives security updates OTA, and it doesn't come with root binaries, so most apps should work.

anzianzi said:
Lineage OS is a good rom to start with. It receives security updates OTA, and it doesn't come with root binaries, so most apps should work.
Click to expand...
Click to collapse
+1