yashsingh1/xdaforums huggingface dataset:
[Nook Color General] skwalas:
Poison wolf and jgaf:

Came home, checked market to ensure it was still flawless (had some updates too!) searched and found repligo, paid and l installed, closed market and then went back to my apps, opened, annotated a PDF for fun, and uninstalled for the refund (it is super nice but I haven't needed to annotate a PDF in a long time). No problems with it.

Going on 7+ days with flawless market at 240. Time to put on my Google hat and research the market filters so we can maybe kill this dragon once and for all.
[Nook Color General] DizzyDen:
Some research on what google has been doing....

About their "Ecosystem"

http://android-developers.blogspot.com/2010/05/on-android-compatibility.html

Gotta love this at the bottom:

Seems to me they are taking the bolded portion out of the equation... narrowing dev's audience ;)

About their "Compatability program"

http://source.android.com/compatibility/index.html

MANY devices seem to have new market issues:

http://www.google.com/support/forum/p/Android+Market/thread?tid=19cb650df0883404&hl=en

I still hold hope in FOOLING them ;)
[Nook Color General] skwalas:
Well, I seem to be fooling them just fine, I just have to deal with oversized icons at 240.

(Day 8 of flawless market, including auto updates of flash and Google+)
[Nook Color General] joenathane:
I'm trying to think through this whole thing logically...

When our Markets go bonkey all we have to do is clear the Markets data and we are all good to go again for a little while. What I think must be happening is the Markets data is getting corrupted somehow. I pulled the Markets cache folder while everything was working and then I pulled it again once it stopped. I can't full well make sense out of all the files as they are mostly compiled, but there is some clear text in most... anyway the market_assets.db from the borked Market contains an additional 100 more lines of code than the good one.

So the question I'm left wondering is what about the dpi causes the data to corrupt? I don't think this is a device filtering issue because all of our apps shouldn't disappear and it works well enough from the beginning it's not like it collects additional device data as it goes on.

Also I noticed that while using the ro. property instead of the qemu. that the "Thumb Keyboard" application breaks, you can't open the settings menu from the keyboard any longer and depending on which theme you use the letters might not show up at all.

I think the answer to all of this lies somewhere deeper into the OS or drivers or interaction between those things.

/ramblings
[Nook Color General] nismopc:
My thoughts...

Why don't they just add the option for end users to allow potentially incompatible apps to there devices instead of trying to determine on their own which do and don't work.

They already have the option for Unknown sources (non-Market apps) built in. Why not add this option as well?

I see it this way. It was said that Angry Birds would NEVER work on the HTC Eris (as well as many other devices) but guess what, it does. Maybe not as the developers intended, but hey it works...

...and is useable.
[Nook Color General] woot1524:
I believe the decision to integrate device checks into the market was to relieve developers of the major hassle of possibly thousands of support claims and returns due to actual device incompatibility. Also the main reason: fighting fragmentation of the OS. With honeycomb out and IC coming out soon, and no doubt android 4.0 in the works; Google needs, like really needs, the older versions to die. What better way to kill them than by slowly cutting off the availability of new apps or upgrades.
[Nook Color General] skwalas:
I am thinking along the same lines, and DESPERATELY wishing I had the linux programming skills to work on this myself. The problem we experience at 160 does NOT feel like a device-check/market problem, but something going on at our end. That I can continue to have a flawless market at 240 is intriguing and at least proves that it should be feasible to set up a flawless market at 160, if we can figure out why 160 breaks.

Please correct me if i'm wrong in any of this, my version of rambling.

Build.prop is a list of setpoints/constants that are read into runtime during bootup. Once read in, the build.prop doesn't do anything, and all those settings (like lcd density) become runtime settings. this would be one reason why (for example) the lcddensity app can change our density after a hot reboot, but does not persist through a full reboot: it changes the actual runtime setting in the OS, not the build.prop setpoint.

I imagine that there are multiple elements of android constantly calling or referencing those runtime setting. I am guessing that this is what the market looks for: the actual runtime setting for lcd density, among other things. I have wondered if it might be possible to rename that runtime setting to something else to make it invisible to the market, the idea being that the renamed setting can be set to 160 with build.prop upon boot and used within the OS, and the "properly named" constant can be set at 240 and found by the market. This might require hunting down every instance where that setting is called/referenced and changing that as well, which i don't think is feasible (everything would still be trying to find the "properly named" version otherwise).

another possibility. I understand all apks have a manifest file that includes requirements and dependencies. Is it possible to access the vendor.apk manifest and see if some setting in that file can be tweaked to disable the need to check lcd density?

edit: continuing along the idea of renaming the lcd density setting... what if instead of renaming the setting, we could program some kind of "trap" that catches all calls for that setting from the vendor.apk, which then sends back a fake setting of 240? somethign that catches the call, provides a canned response of 240 dpi, sends it back to vendor.apk, and keeps the actual setting invisible to vendor.apk?
[Nook Color General] pastordl:
Google batting a zero with both market and you tube app. No new google apps for me till they get their act (apps) together.
[Nook Color General] japzone:
~~~delete-me~~~

____________________________________________________

Sent from NookColor CM7 uSD using Tapatalk
[Nook Color General] joenathane:
I have made another observation which has led to another theory. When all the workarounds are in place and the market is working great on my Nook, i can go on my computer to market.android.com and install all the apps I want, but when the market on the Nook screws up and the apps disappear the market.android.com doesn't let me install some apps, they are listed as incompatible but right when I clear the data for market on my Nook, the market.android.com starts allowing me to install any app I want to again.

So, I think that this may indeed have to do with the product filtering Google has put into place, I think that the Market does it's own little checks based on the build.prop but then also checks with Googles servers for additional "verification", at that point I think is where we have problems....

So I am trying a hybrid solution, the new market with the build.prop changes and with the marketupdater.apk extension changed to bak and so far so good.

I will post if I am successful...
[Nook Color General] skwalas:
Hey, can any devs provide any insight into kmobs market workaround commit in the latest nightly?

http://review.cyanogenmod.com/#change,7546
[Nook Color General] DizzyDen:
What I see looking at it:

In AndroidManifest.xml they are changing the android version from 1.0 to 1.1

and uncommenting category android:name="android.intent.category.LAUNCHER" line

In StartupActivity.java:

Added lines:

23	import android.content.pm.PackageInfo;
;
25	import android.content.pm.PackageManager.NameNotFoundException;
26	import android.net.Uri;

And rewrite of the StartupActivity function.. can go more in depth of that if you want.
[Nook Color General] skwalas:
I got that bit looking at the side-by-sides, I just don't have any sense for the relevance of the changes. Nothing stands out as being an actual fix, so its either a workaround to a different problem or I'm missing something...
[Nook Color General] DizzyDen:
Actually, the function rewrite looks to be where the fix is at... it calls some settings etc. that initializes market differently... sort of...

Look at the StartupActivity function rewrites... it initializes some of the items.
[Nook Color General] skwalas:
Well, nothing related to density. Still, we already know that 160 works fine at first, so the break may not have anything to do with the density per se, but rather with one of these inits after the app data is first created.

In any case I've already flashed it to see. Market is still limited at 161, but am now testing whether my apps disappear while at 160.
[Nook Color General] skwalas:
So my apps list was still around this morning while at 160. Seems promising...
[Nook Color General] japzone:
I'm using this method too, but just to warn you, you must wipe your Market data frequently. I use this method myself because I don't like the Oversized UI of 240dpi.

____________________________________________________

Sent from NookColor CM7 uSD using Tapatalk
[Nook Color General] joenathane:
It looks like the market fix that landed has helped but has not completely alleviated our market problems, instead of the market becoming empty after a while at 160 dpi, now a good number of apps will have a yellow banner stating something along the lines of "your device is incompatible with this app" although once clearing the market data, all apps become "compatible" again. This "Market fix" is a step forward though...

As a note, something else I've tried but has not helped... I remembered that our device fingerprint was lifted from the Nexus and thought that we were having issues because of the mismatch between our "fingerprint" and our model type and number, so I changed my build prop to match Nexus S "fingerprint" and model, manufacturer, etc... but that ultimately didn't help...
[Nook Color General] skwalas:
You're way behind the times. I'm testing the market workaround that was built into the newest nightly. The hope is that we don't have to clear data anymore.
[Nook Color General] skwalas:
I saw this too, and couldn't figure out what was going on at first.

Also, interesting observation: in the new (v 3.1.3) market, when dpi is at 160, there is a "staff picks for tablets" category. when dpi is at 240, there is just a "staff picks" category. The default recommendations that show up in the market home screen are also different between the two dpi's.

As always, two steps forward, one step back.
[Nook Color General] boxcar8028:
can you see movies and tablet apps? I can see all my apps okay but can't see movies or tablet apps.

market v3.1.3

screen dpi cm default 161
[Nook Color General] skwalas:
Yes, I see the movies tab, and can rent individual movies. "tablet" apps (listed as "HD" or similar) show up at 160 (although that doesn't mean they're truly tablet-specific, i.e. requiring honeycomb; those will forever remain hidden to us while we're on GB).

Market is severely limited at 161 even with fix. No movies, no flash, no facebook, no "tablet" apps, etc.

have not yet confirmed that individual tablet apps can be found at 240, but based on my previous observations, all other problematic apps do show up.
[Nook Color General] boxcar8028:
thanks skwalas,

just change my density from cm default dpi 161 to 160 and now I can see movies and tablet apps. i hope this fix will stick. but the odd thing is that my htc aria screen default dpi is 160 and I still cant see movies or any of the staff and editors picks. but all of my apps are showing up just fine.

this new market is weird :rolleyes:
[Nook Color General] skwalas:
Came home and found the my apps list empty. Not only that but it also reverted to the 161-style limited market. I had been using lcddensity to switch and left the build.prop at 161. Its almost as if build.prop was read again at some point such that the market picked up the default 161 setting.

Regardless, market workaround does not fix market at 160.

Looks like its "pick your poison": severely limited but functional market at 161 (or any other nonstandard density), OR tablet-optimized full market that breaks eventually at 160, OR flawless full market without tablet-style apps at 240.

Guess I'm sticking with the flawed market at 160 density for now, personally.
[Nook Color General] Deltabear:
hmmmmmm

:confused: :confused: :confused:

OK, I set lcddensity to 240, attempt reboot with the daemon, it does not work, changed to killall, it rebooted the nook, but at the nook color startup screen it makes it to the O in color, occasionally to the L, and starts the logo over. It will continue this until the battery dies. Any suggestions would be GREATLY appreciated, I've completely redone the nook as I'm not sure how to get back to where I need to be to even boot.

I have adb access while it's in the boot mode so I can update anything with shell if you can give me instructions. I'm not a high end developer, learning and trying, so any help again is appreciated.

Thanks,

DB
[Nook Color General] joenathane:
What build are you running? I would try replacing the build.prop as a first step if I were you. I've attached mine, in case you dont have access to a good one, be aware I am running nightly 176.
[Nook Color General] Deltabear:
I'm running MN on 1.3, nothing special. It looks like I'm going to have to go back to 1.2 and update the build.prop so it thinks I'm on 1.3...

I'll try diff'ing your build.prop to mine and see if I can tell anything WAY out of the ordinary.

Thanks!

DB

EDIT: Scratch that...LOL everything's different. I'll see if I can get back to 1.2 and block update, thanks for trying though!!!
[Nook Color General] Homer_S_xda:
Uh,

What market workaround in which nightly?

Homer
[Nook Color General] boxcar8028:
yes sir, my screen density reverted back to 161 all by itself. now my market is back to limited 161. i guess i can always redo the 160 fix just to update apps. but what a pain in the ars :mad:
[Nook Color General] koopakid08:
http://review.cyanogenmod.com/#change,7546
[Nook Color General] Homer_S_xda:
Thanks,

Found it here as well. Search for Market (hint it is in 176 forward).

I seem to be stable on the 3.1.3 market now. I finally had to uninstall 3.0.2x, install 3.1.3 and then clear the markets data a time or two as I was hitting force closes like crazy. Now it seems happy and videos show. Stock build.prop btw.

Homer
[Bada Software and Hacking General] marcin205:
Hello im have Samsung S8500 XXKF3 im try update to XPKH2 latest bada 2.0 beta

and im got multiloader v 5.65 problem can't open ffs file or ShpApp im try lot times extracting and redownload and evrytime this same any idea ?
[Bada Software and Hacking General] spacks:
Please make sure you are using the multiloader 5.65 included with bada 2.0 firmwares. Also make sure you have successfully installed the drivers also included in the bada 2.0 package.

You may likely experience "serial port" error if you had previously flashed a bada 1.2 firmware and now wish to flash to bada 2.0. If this is the case, just unplug USB and reconnect phone again. Your PC will automatically pick the right port by now.

If the problem is with the firmware, try to redownload the firmware from samfirmware.

Best of luck.
[Bada Software and Hacking General] toxicdust:
KH2 dont have the USB drivers included last time I checked.

Just saying
[Bada Software and Hacking General] marcin205:
yes im use new drivers and this same @ KF3
[Bada Software and Hacking General] spacks:
Install the drivers that came with bada 2.0 beta firmwares (S8500XPKH3). Restart pc. Then try again. I expect it should work fine as long as all needed drivers are installed successfully.
[Bada Software and Hacking General] marcin205:
ye it was worked ^^
[HD2 Android Q&A, Help & Troubleshooting and Genera] raffinator:
Hi,

I have very often Problems with my Android Nand Version for my HD2 .

I have the typhoon cyanogenmod 7 flashed

Its now the third time that i have the Failure:"1E FATAL HIT 1" by booting.

It was always like this : first it was often not possible to press or do anything and after i reboot it worked normally. After a time it got more worse with the freezes ,they came very often and then after a new reboot the failure came.

After the first and the second time i done everything new with task 29,hspl magdlr and clockwork mod.At the moment its not possible to get into ad recovery, so i also cant make a backup.The usb storage is not shown proper on my pc , i just can see the drive with a programm like minitool partition magic.

I dried other builds but they were all to slow or had more freezes.

So what can i do now , making everything new and maybe after it , it will be the same again .I even think about going back to windows mobile.

What can be the problem .

Thank you for your help
[HD2 Android Q&A, Help & Troubleshooting and Genera] :
Did yo u solved the Problem?

Hi, i know your post is old a little but i have here the same Prolbem now. The Funny thing is, i and my wife have the same Phone: HD2. I change very often the rom or reinstall it and i dont have (Lucky) no errors. But now i installed the 3rd rom on the Phone from my wife. and now she get this error. So, it would be great if there is a soloution for this problem.

Thanks and Kind Regards

Kleiner Kobold
[HD2 Android Q&A, Help & Troubleshooting and Genera] :
solved

I use now clk and no problems any more

Kind Regards

Kleiner Kobold
[HTC Sensation] lightninbug:
......ummm trying out now...:confused::confused:

Dunno whats so different from whats out there...only thing i notice is updated apps, that I can easily update on my own.

thank you soooo much anyways...still trying this out!

edit: Might want to save the first couple posts next time for screenshots/changelog/yadda yadda yadda
[HTC Sensation] bigpercaso:
THX for trying out! yah the rom is up to date and not much different from the other ROMs here.

what I want is to create a ROM that runs smoothly and looks good. But first must work well, the ROM,

then I make the special design...
[HTC Sensation] Dano79:
A rom made my an Ital has to be good downloading now
[HTC Sensation] Docmjldds:
Could almost say that about ALL the ROMs on the Sensation. Sure, you have Coredroid, my favorite for themeing, or ExtremeSensless, which I run with Coredroid themeing but basically, till we get CM7, and the MIUI hopefully, just about all these ROMs are the same old same old. Just change themes and add ons and they all do the same, or run Sensless scripts and use ADW EX for more of a stock non sense look.
[HTC Sensation] jerrylzy:
I love this picture and i wanna set it as my wallpaper,could you please provide one?Thanks!
[HTC Sensation] forelli:
Thanks for this ROM. I will try it because when I saw your pic, I thougt of the WM 6.5.5 good old days ;)

f.
[HTC Sensation] bigpercaso:
here we go...
[HTC Sensation] Archie The Leper:
Thanks mate, 42hrs and powersaver only just came on, keep up the good work
[HTC Sensation] bigpercaso:
percasoROM 2.5 blackICE uploadet...
[HTC Sensation] nerlim:
Hooooo ita la prov subit (ho scritto in ita pechè non so l'ingese)
[HTC Sensation] jlevy73:
Did you actually use the device during those 42 hours? Please tell me your display time
[HTC Sensation] nerlim:
I try with English .......... The camera mod is built?
[HTC Sensation] Archie The Leper:
Normal use, did nothing different from any of the other ROMs that I can barely get a day out of
[HTC Sensation] bigpercaso:
New ROM uploaded....
[HTC Sensation] cgingermany:
Why is this thread so quiet?
[HTC Sensation] Pinepig:
Dunno, I'm going to give it a try tonight, love the look of it.
[HTC Sensation] cgingermany:
I flashed it earlier today and honestly, very nice. Smooth, very attractive, I'm a fan of colorful and this puppy has a nice touch to everything thus far. Battery life has been average(comparing it to IC which is where I'm.flashing from). It's running nice so far. Actually I had to do a fix permissions, when using my TB to restore my stuff it was giving me a force close but I ran a fix permissions from CWM and VOILA. I'm liking so far.
[HTC Sensation] BlackVision:
I would like to see this Dev keep working on his vision for this ROM.
[HTC Sensation] jmwils3:
same here. He has some really unique tweaks and theming that other roms just dont have :/ only wish to see him expand upon the awesomeness he already has, perhaps incorporating some of the tweaks from other roms like insertcoin and bulletproof, and updating the rom base to 1.73 (sensation xe release RUU)
[HTC Sensation] d_matt20:
Yea , so that's the problem lol
[HTC Sensation] Chance Ill:
Yes sir! ;)
[HTC Sensation] Chance Ill:
Why is this thread so quite? :confused:
[HTC Sensation] Suprize3131:
Yeah it usually is great work but the op doesn't comment/interact as much as other devs (shrugs) lol XD
[HTC Sensation] Chance Ill:
As a result, his work won't get the recognition it deserves and the thread will eventually die. It's unfortunately as this is hands down one of the best ICS Roms to date.
[HTC Sensation] d_matt20:
+1

10 chara
[HTC Sensation] jwgizmo:
Do I have to have root access to install this ROM? I have not been able to root this dang thing. I tried SDK version, but my phone just sits there waiting for the get token identifier screen... I gave up.
[HTC Sensation] Chance Ill:
Have you unlocked the bootloader? (s-off)
[HTC Sensation] Suprize3131:
Totally agree
[HTC Sensation] jwgizmo:
No, I am having the hardest time with this Sensation, It was much easier with my HD2. Any suggestions. When I enter it reads

***LOCKED*** highlighted in pink

Pyramid PVT SHIP S-On RL

HBOOT-1.18.0000

eMMC-boot

Aug 2 2011

I selected FASTBOOT and BOTLOADER

ran the SKD stuff from the CMD screen

and It just sits there.

Is there an easier way?

This is frustrating... uggh!

:mad:

EDIT: I was trying to S-OFF (so I thought)
[HTC Sensation] Chance Ill:
There is no other way that Im aware of. What exactly is it you cant figure out? Do you have the drivers installed?
[HTC Sensation] jwgizmo:
The HTC drivers? I think that is the problem. dling them now.

EDIT: Installed the HTC drivers (duhh) and ran the SDK. All went well. Now reads UNLOCKED. (wahoo).

Finally... Rooty-Toot-Tooted

Root success!
[HTC Sensation] pauleley:
Has this Rom got Advanced Power Menu ???
[HTC Sensation] bigpercaso:
Many thanks

it is because I have to work much, I have unfortunately not so much time.

I've been working on "bI 4.1" ...runs much better
[HTC Sensation] jwgizmo:
Yes read above
[HTC Sensation] Sylus87:
Ou quando voglio scaricare la rom mi scarica Solo 10 kb.

When i download the rom, its download only 10 kb i need New mirror
[HTC Sensation] Chance Ill:
Good job. Glad I could help
[HTC Sensation] Chance Ill:
Use a laptop/desktop. For one reason or another, using a phone doesn't play nice
[HTC Sensation] d_matt20:
yes cant wait love your roms
[HTC Sensation] jwgizmo:
I installed this ROM yesterday evening. There is a bug with the backlight on the 4 function keys. Most of the time they are not on. Everything else appears to run fine. Nice build. Will report back

Any ideas or suggestions?
[HTC Sensation] bigpercaso:
happy new year

Come all well into the new year and good luck for 2012​
[HTC Sensation] Chance Ill:
Not having that problem. Try reflashing using a super wipe script.
[HTC Sensation] jwgizmo:
Problem Solved

No need. Took a simple approach and wiped Dalvik.. Problem solved.

Thanks for the suggestion. I was going to try that if Dalvik didn't work

HAPPY NEW YEAR
[HTC Sensation] jahmezis45:
i like this rom but it does have some graphic issues. and since no ics roms have wifi calling i had to revert back to an older rom. to me this was the best ics rom out there look wise.
[HTC Sensation] d_matt20:
Love the Rom can't wait for the up date
[HTC Sensation] Mc_Kill:
Can't Wait Anymore :D
[HTC Sensation] tommy781:
utilizzo con grande soddisfazione la 3.8 e sto attendendo di passare alla 4 per motivi di gioventù del sistema ma trovo le tue rom estremamente gradevoli visivamente e molto stabili, complimenti!