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]CM10 Flinny Test build

Hi XDA,
I'm currently running latest Flinny CM10 test build (125), and an issue I've had for a while is that even when the phone is locked, but screen is on, I can pull down the notification bar and do actions. Is this normal? Is there a setting somewhere that needs to be switched off? I am using Apex launcher.
Cheers.

As far as I know this is a standard behavior since android 4.0 (ICS). There is no settings to disable it.
Someone correct me if I’m wrong
EDIT: If you have enabled screen security (pattern, PIN, password) you should not be able to pull down the notification bar. You should be able to pull it down only with slide lock.

I enabled a simple gesture unlock and yes now I can't pull down the notification bar.
It still seems strange that this is normal behaviour.
Thanks heaps!

yup... That's normal...
I also face some issue which is the ROM could not connect to external gps device... I think that's issue exist in CM10 since have same issue with galaxy smtd...

Yeah I don't have working orientation, light or gyro sensors still. It seems like some people have this problem and others don't depending on hardware revision.

Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010

Vauvenal7 said:
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Click to expand...
Click to collapse
Just wondering... Do u install gapps? If not, you should do that when u install it for the first time (after you install the rom).

Vauvenal7 said:
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Click to expand...
Click to collapse
As with every CM build after 4.1.11.1 on the G1, ALWAYS FLASH GAPPS AFTER FLASHING THE ROM.

cm made a 4.2 donut where the base was flashed first still, so starting with eclair gapps where flashed after
Sent from my HTC Vision using xda premium

blackknightavalon said:
As with every CM build after 4.1.11.1 on the G1, ALWAYS FLASH GAPPS AFTER FLASHING THE ROM.
Click to expand...
Click to collapse
I did, yet ther was no camera app pre installed
Even the icon on the unlock streen existed, but when i unlocked it with the cam symbol nothing happened, it just went back to the lockscreen
I had mimicry before and therefore i got used to flash gapps, so did i with this jb rom too
Sent from my GT-N8010

I love this ROM, everything I generally use on a regular basis works fine. My only real problem is this ROM is a serious power drain, within an hour of being unplugged in the morning I have already lost 10% of the battery, by mid afternoon I am forced to plug the phone back in, this is something of an issue as I work at hospitals and plugging appliances into the mains is a violation of health and safety regulations, but I need my phone so I do what ya gotta do. Is there any way to reduce the drain from this ROM as I am fairly sure it is not any applications I have installed causing it, as none are running in the background when I check running apps.

plug it in to a computer with a logcat running, see what is going on that way. or if you aren't able to sit in front of a computer for a while watchdog is a nice app for this (keep in mind it should be for testing basis and be removed later as it to will always be running in the background)
Sent from my HTC Vision using xda premium

evernote makes phone slow
I am using this rom (build 124) and I have and after restoring all my apps it became really slow. After some try/error I found that uninstalling some apps solved the problem. After that I started installing my apps again one by one and I found installing evernote make the phone near unusable.
Anybody is experiencing this? it also happen if I install "camera 360".

I am running build 127 of this ROM which definitely seems faster than build 126 which was the first one I tried and seems to be quick enough to actually use it most of the time.
When things do go slow it seems to be when switching to a new app and seems more likely to happen is the new or old app is big.
Regarding more apps slowing things down I wonder if it is actually more widgets and background services. If this is, as I suspect, do to with how many apps can be cached in RAM for fast switching then the more apps have something running in the background, for example to sync with a cloud service or to keep a widget updated, the less RAM there will be for the apps you are trying to use and there will therefore be a greater chance the app you are trying to start has to be started from scratch.

These threads really need to stop, Flinny's test build is just that A TEST BUILD problems/issues are expected.

I think it's normal...anyway it don't obstruct me

tarroyo said:
These threads really need to stop, Flinny's test build is just that A TEST BUILD problems/issues are expected.
Click to expand...
Click to collapse
In my case I am certainly NOT contributing in order to criticise. Of course I know a test build may have issues but, like many others I suspect, I am happy to try the latest thing. When things don't work quite right it is worth discussing it. If we can understand what is happening we can help each other mitigate the issue and maybe even have something useful to feed back to developers.
I was running build 127 and things had become very slow. I have now updated to build 128 and the phone is fast again. At this stage I am not sure if this has anything to do with the new build or whether it is down to apps. I have all 45 apps installed but for many of those that sync to cloud services I have not yet got round to setting up the username/password for that to happen so this may be limiting the amount of background activity to a level where it doesn't get in the way. I'll try setting some of them up and see what happens.

[Q] Playstore on Chinese One V

Hi there, I’ve got the Chinese version of the One V and like most Chinese phones these days, Google account functionality has been removed.
I have rooted my phone and most of the Google apps that did not work before do work now (g-mail, Google maps ect.) Unfortunately the plays store is still inoperable. I can install now but it crashes shortly after launch. If anyone has experience with using playstore on a Chinese phone I would love to know what i need to be doing right.
Otherwise I am guessing I could use a rom from another region. my only worry is that it may not be compatible as there is some hardware variation, the Chinese version have an extra button on the front for quick access to weibo(Chinese twitter) I don’t know if that’s the only difference but it’s the only one I can see.
Any way if you have some advice on how I should proceed I would very much appreciate it.

Ckatt said:
Hi there, I’ve got the Chinese version of the One V and like most Chinese phones these days, Google account functionality has been removed.
I have rooted my phone and most of the Google apps that did not work before do work now (g-mail, Google maps ect.) Unfortunately the plays store is still inoperable. I can install now but it crashes shortly after launch. If anyone has experience with using playstore on a Chinese phone I would love to know what i need to be doing right.
Otherwise I am guessing I could use a rom from another region. my only worry is that it may not be compatible as there is some hardware variation, the Chinese version have an extra button on the front for quick access to weibo(Chinese twitter) I don’t know if that’s the only difference but it’s the only one I can see.
Any way if you have some advice on how I should proceed I would very much appreciate it.
Click to expand...
Click to collapse
what rom are you running in your phone?

I think he's running stock rom. But like he said the phone may have different hardware than our One V's
So we would need a list of the specs so we can compare them to ours if the hardware is the same u can just use our roms, but if it isn't than our roms will brick your phone.
Sent from my HTC One V using xda premium

Yes, it is the stock rom. I do beleve the specs on the phone are the same, i recall checking it out before i ordered it from Amazon, but i will dubble check to be sure.
Thanks

It’s a bit tough to find the information but as far as i can tell the hardware is the same. There doesn’t really seem to be a distention model number wise and the only way i can tell witch version a given site is talking about is based on the picture where i can see the extra button. So assuming the hardware is the same in all other respects does it matter which rom I install?

In that case it shouldn't. The extra button wont work than but apart from that it should work.
Sent from my HTC One V using xda premium

[Q] Small inconvenience

Hello, extreme newbie here, with practically 0 experience with roms and various tweaks and stuff like that (I played around with these things a little back when gingerbread was THE thing, never touched Android since, till recently).
I've been using a One X for the past 6 months or so and I decided to finally get rid of all the gaming problems (due to HTC's power management, etc) and to benefit from various improvements that helped improve the experience for lots of people, unlocked it, rooted and installed the latest JB sense ARHD without a single problem + the advanced power menu and the mod pack. Everything works fine and seems like it'll work no problem, but there is only one small problem, the phone is now recognized as EndeavorU instead of One X, in the phone specs, on HTC sync and google account, it's a little annoying to see it named like that and my question is, or should I say questions:
1. Is this name change relevant to the overall functionality of the phone, in other words, did I mess something up that needs to be repaired?
2. Can it be changed back to its brand name instead of code name without having to restore the stock settings?
Thanks for the possible solutions and sorry if this has been asked before, couldn't find much info about this, only one random thread on some other forum where a guy had his phone revert to One X after a reboot, then back to EndeavorU and finally back to One X when he connected it to HTC sync, none of that worked for me.

The name EndeavorU is the official name of out phone. It doesnt matter and no need to be "fixed" .
Yes you can by editing the build.prop in system. You can use build.prop editor from play market for this. ( ROM toolbox includes this feature ).
But you need to find the actual variable you need to edit and it can be a bit confusing.
ADVICE : Leave everything as it is. It doesnt matter

Thanks for the answer, was mostly worried about it affecting the app compatibility detection (no idea how complex Google's database is with their devices and various names), but doesn't seem to be the case so far and if you say it does no harm to the functionality then I'll probably leave it like that, thanks again.
Couldn't help it , wanted to know more about this, got informed a little and understood especially that I shouldn't tweak what I don't know enough about because it might damage the phone, with the app you suggested it only took a minute to back up the original file and edit the name, yet another thanks.

[Q] Will Editing The Device Name in the build.prop cause a brick?

Hey,
Got a nexus 7 2013. I bought Modern Combat 3 for it a while ago, and never got it to start. I had the same problem for my Galaxy Nexus, but I fixed it by installing a previous version of the app through an apk. Whilst it worked flawlessly for my Gnex, when installed on my N7 it tells me that my device is incompatible. I know this is not true as I downloaded the app from the playstore and installed it no problems; running it was the issue.
So I need to ask if changing the device name in the build.prop, letting the game install then putting it back has a possible chance of causing a brick. Either way, please let me know asap.
If there is a different way to get the game working, or to make the app think I have a compatible device, please also let me know.
I'm rooted, running stock 4.4.2 with Xposed.
Thanks,
-Riku

For the most part anything under ro.build and ro.product is safe to edit, they're generally for display purposes or for market to do app compatibility checks like what you might be having issues with.
The exceptions are
ro.product.cpu.* (I simply have not tested changing these)
ro.board.platform (this will definitely break booting if you change it)
Whether or not this actually helps you though, I dont know.

TheManii said:
For the most part anything under ro.build and ro.product is safe to edit, they're generally for display purposes or for market to do app compatibility checks like what you might be having issues with.
The exceptions are
ro.product.cpu.* (I simply have not tested changing these)
ro.board.platform (this will definitely break booting if you change it)
Whether or not this actually helps you though, I dont know.
Click to expand...
Click to collapse
This is useful and I will apply that to future questions, but i just want a solid answer. If you have a N7, would you main testing it and seeing if it still boots? If you don't, is there a way you could confirm an answer for me?
Your help is greatly appreciated.
-Roku