yashsingh1/xdaforums huggingface dataset:
[HD2 Android SD Development] SuperXM1ke:
With ACA nand working as smoothly as it is on the HD2 I hope they never make a phone as good as ours, so Cope and War will always make these great builds. One day, I'm gonna stop being poor, and you guys are gonna get some beer money! Thanks
[HD2 Android SD Development] baybay317:
Thanks kushXmaster for showing me how to uninstall the market latest update. I had Force Close for the new market and I am glad to know how to turn it back to older verison.
[HD2 Android SD Development] atlaswing:
Yes, i'm using ACA 7/29 SD build, i've set the market apps to manually update, but regardless of whether I'm using a new data.img or the TitaniumBackup data of old 6/23 build, the Android Market would auto-update to 3.0.27 and immediately force close when I try to download anything. I'd then have to go to settings-applications and uninstall update, or go to TitaniumBackup again to revert to the old 2.3.6 Market from ACA 6/23. I'm able to download one program, and again, market auto-updates to black 3.0.27 and force closes. rinse and repeat. So is there a way to prevent this newer useless AndroidMarket 3.0.27 from popping up automatically every time I open the old 2.3.6 market? This is only happening in the 7/29 ACA Sd build(my last one is 6/23 SD, no problems at all). Must be an easy setting that I can't find.
[HD2 Android SD Development] pwhitrow:
It has? Did I miss something? :o
[HD2 Android SD Development] kushXmaster:
Ok. What you can do now is with a file explorer with root access (like es file explorer) navigate to the cache folder. Should be the second folder in phone memory...long press, select properties>where it says permissions there is a button that says change. Press that. Make sure all nine boxes have a check mark. Reboot. This should fix it.
[HD2 Android SD Development] jadrobe:
On 072911 build...no popup to disable alarm! Couldn't sleep again after that! Lol! Couldn't shut off the alarm and was forced to restart

sent from my Blackberry HD2 using tapsilog
[HD2 Android SD Development] daniel_kiefer:
In my case I didn't have to reboot for it to work. Rebooting actually reverted the fix.
[HD2 Android SD Development] kushXmaster:
For me the fix is still there even after rebooting. Weird that yours doesn't stay...have you tried doing the terminal method?

No problem :) I don't mind helping people out...I know what its like to not know how to do something and not be able to find any reliable info on it.

You can also try the cache folder mod to get the new market working, if you like. Or use the old one. Whichever you prefer.
[HD2 Android SD Development] copenhagen:
UPDATE

(please don't quote the following links anywhere)

http://www.multiupload.com/8OLH97TW39 - clk update

http://www.multiupload.com/G7X0UDOSFI - magldr update
[HD2 Android SD Development] prattjo:
What do you mean by "(there is no more copy root folder over technique)"

Is it not possible to add a library which isn't included in the build?
[HD2 Android SD Development] prattjo:
Cope your link for SD 08012011 is not working. Thanks
[HD2 Android SD Development] atlaswing:
Thanks Kush, I see, this cache rwxrwxrwx permissions trick allows the new 3.0.27 market to work temporarily, but as daniel_kiefer said above, it's also not permanent, permissions are lost again when you reboot. As to the original question, I still have not figured out how to disable the Market itself from auto updating to the black 3.0.27, even though all other market programs can be set to disable autoupdate. Whenever I reload the Market_2.3.6_APK, it would only last a few minutes and auto-update to 3.0.27.

So for now, I'm going back to my 6/23 SD build, with its bad battery life, but which has the trusty green 2.3.6 Market that does not auto update and has no need to change permissions every time I open it. I only fire up Android once a month, so I can put up with the older version and its short battery life, but still, there must be a simple solution to why the 7/29 SD build 3.0.27Market's auto-update cannot be turned off.
[HD2 Android SD Development] JustX:
I have had the same issues as you guys. It's weird how some do and some don't. Though, I think the ones that say it doesn't happen are all NAND users.
[HD2 Android SD Development] cariocap:
For me it's working, at least with megaupload link
[HD2 Android SD Development] prattjo:
Cope I just installed the 08012011 SD version. Is it possible that it doesn't reboot after first boot. It means only 1 boot needed in order to update?

After first boot everything seems to be OK. LCD as I chose in the startup.txt the same for gps region, I didn't change the size of the data.img.

Is the first run file redundant and is the 240buildprop directory on the SD redundant too?
[HD2 Android SD Development] cariocap:
first test result:

using data_size=1024 it creates 2Gb data.img
[HD2 Android SD Development] cariocap:
mine doesn't reboot too
[HD2 Android SD Development] mv:-):
080111 build test

that's me! :)

mine (for first test, set data size to 1.5GB just to check whether it will create the size -- there might still be some remnants of the old code, i.e., default creation of 1gb... ;)):

set cmdline "rel_path=Android nand_boot=0 lcd_density=202 gps_zone=us data_size=1536"

first test: * did a "fresh install" -- renamed 072911 "Android" folder and copied the "Android" folder (080111) to my sd card *

-- despite setting data size to 1.5 gb, a 2.0 gb data was created. :(

-- lcd density at 202. :)

-- gps zone set to "us." :)

-- time zone was set at GMT+00.00 (not where i'm in), despite the checked "network-provided values." no big deal, either a restart will fix this or a manual entry.

-- boot took longer, of course, because of the data size.

-- non-responsive lockscreen. had to do the on-off-on-off workaround several times.

-- didn't make any further tests... :cool:

second test: * copied my 072911 data.img file, to see if usable on this build *

-- 072911 data.img working so far... :) will still be using this until i encounter some big issues.

-- lockscreen was responsive (first time around, that is, after first boot; and therafter...), as it was with previous build.

-- didn't make any further tests... but will see (and report, of course!) if i get any issues by using an old data.img.
[HD2 Android SD Development] prattjo:
For me using the same as you, using data_size=1024, I have a data.img of 1 GB, but is it possible that for both of us it wasn't created but used the existing one for me 1GB and for you 2GB
[HD2 Android SD Development] ecb5:
I've amended my gps conf as you stated in a previous post.(13131)

I still can't get a fast fix . Sometimes no fix. Should i change north america to ca.

Thanks
[HD2 Android SD Development] cariocap:
After the first 2Gb data.img I copied my old 072911 data.img without problem until now, not used too much yet.
[HD2 Android SD Development] cariocap:
Yes, my first attempt was a fresh one (no data.img) and it creates a 2Gb file.
[HD2 Android SD Development] RobE.:
fwiw... It doesn't happen. I'm an SD ACA user. :p :)
[HD2 Android SD Development] clarkg:
Don't worry, that still works (just tested it).
[HD2 Android SD Development] cariocap:
Im using SD version and my GPS wasn't fixing too.

In my case to solve it I have to applied GPS Libraries v1.9 with AGPS support for HD2 Gingerbread.

I checked the files and found that Americandroid version 080111 don't have GPS Libraries v1.9.

I installed the NMEA version and now it fix in seconds.
[HD2 Android SD Development] prattjo:
1) How dod you know it was not included I remember UZI saying it was in the 0729 SD version?

2) To install it did you create a root folder and if not how did you do it?

Thanks
[HD2 Android SD Development] cariocap:
I compared the date of the files of 080111 and they are older then v1.9.

Yes, inside Android folder I created root folder and copied system folder from v1.9 inside the new root folder. For SD, you only need system folder. Don't know if you need to copy the META-INF. If you in doubt, also copy the META-INF folder.
[HD2 Android SD Development] Ev0luti0n_:
hello! i've tried using this rom, and after a few minutes the phone is very hot! i don't even get to play anything! it becomes super hot just browsing the menus! does it also happen to you folks?
[HD2 Android SD Development] kushXmaster:
Hmmm that is odd. Only thing I could suggest now is maybe one of the builds since 722...they seemed to have considerably better battery life. I think builds after 725 have a fix for the proxy issue after calls.

Anyways, good luck and sorry I couldn't help more.

I've never had my phone get to more than 110 degrees Fahrenheit internal temp.
[HD2 Android SD Development] satan!:
check 0801

as I said

need to revise the code.

Experiment in the terminal emulator for android

dd if=/dev/zero of=Test10_data.img bs=10 count=1024

or

dd if=/dev/zero of=Test_10data.img bs=1024 count=10

for quick results 10

and see what will be a newly created file size

if [ ! -f $card/data.img ] ; then
DATA_SIZE=1024
if ( grep "data_size=" /proc/cmdline > /dev/null );
then
DATA_SIZE=`awk 'BEGIN { FS = "data_size=" } ; /data_size/ {print $2;}' /proc/cmdline | awk '{print $1;}'`
fi

[ $? -lt 256 ] || DATA_SIZE=256
[ $? -gt 2048 ] || DATA_SIZE=[COLOR=Black]2048[/COLOR]

echo "Creating a new Data store"
dd if=/dev/zero of=$card/data.img bs=[COLOR=Red][B]1048576[/B][/COLOR] count=[COLOR=Red][B]$DATA_SIZE[/B][/COLOR]
[ $? -eq 0 ] || fail "Failed to allocate the storage"
mke2fs -F $card/data.img
[ $? -eq 0 ] || fail "Failed to format the storage"
fi

no verification code in the lcd_density.

gps_zone code is missing.

I generally told what to do at all check the minimum and maximum values ​​lcd_density, data_size

+ Need a check whether there are values ​​in startup.txt, if not, then the default value lcd_density = data_size = 167 1024

in other words if you do not register the keys in it and startup.txt lcd is 167, and data will be 1Gb

(safe surplus-shortage)

(check all that from uncomprehending)
[HD2 Android SD Development] clarkg:
I can help you test stuff for a standard pptp/l2tp vpn if you want. I've got my own VPN server so troubleshooting is easy to do. All you need to do is let me know what you want me to try.
[HD2 Android SD Development] dttung80:
Dear Cop,

I'm using 29711 SD build with old data.img file.

I already have 1 SOD and to day heavy rain, i have alot off drop call. From 1min-2min, my phone auto drop call.

Any one have same issue ?
[HD2 Android SD Development] satan!:
it all depends on your carrier
[HD2 Android SD Development] shost:
data_size

I'm sorry, it is stupid error in checking data size limits. There should be DATA_SIZE not $? I'm always saying don't copy&paste :(

if [ ! -f $card/data.img ] ; then
DATA_SIZE=1024
if ( grep "data_size=" /proc/cmdline > /dev/null );
then
DATA_SIZE=`awk 'BEGIN { FS = "data_size=" } ; /data_size/ {print $2;}' /proc/cmdline | awk '{print $1;}'`
fi

[ [COLOR="Red"]DATA_SIZE[/COLOR] -lt 256 ] || DATA_SIZE=256
[ [COLOR="Red"]DATA_SIZE[/COLOR] -gt 2048 ] || DATA_SIZE=2048

echo "Creating a new Data store"
dd if=/dev/zero of=$card/data.img bs=1048576 count=$DATA_SIZE
[ $? -eq 0 ] || fail "Failed to allocate the storage"
mke2fs -F $card/data.img
[ $? -eq 0 ] || fail "Failed to format the storage"
fi
[HD2 Android SD Development] cykeltossen:
hallo

i com from MCCM and BOXMAX and I whant to try somthing new, and this sound like a nice rom, but after i have install the ROM, every thing is small, how com? what can i do?
[HD2 Android SD Development] copenhagen:
the 1.9 libs are infact included. AND the date? what date did you see exactly? 2008? does that mean the whole build is from 2008? cause id suggest you look at all the file's dates.
[HD2 Android SD Development] satan!:
thanks, and still recommend to indulge :

Experiment in the terminal emulator for android

dd if=/dev/zero of=Test10_data.img bs=10 count=1024

or

dd if=/dev/zero of=Test_10data.img bs=1024 count=10

for quick results 10

and see what will be a newly created file size
[HD2 Android SD Development] PlayStation:
Nice to see you Cope.... Downloading the 1st August build now will give feedback. I hope it will work with my old data and avoid the issue discussed above with different size of data created. I am not sure what exactly needs to be edited as indicated by satan.... :eek:
[HD2 Android SD Development] RobE.:
If you're using the newest (0801) SD build, you need to edit the startup.txt file... and change the lcd_density=167 to the number 240 instead. I don't know if this will change the pixel size after the fact - but a reinstall is simple enough.
[HD2 Android SD Development] copenhagen:
ahem. serves me right for not checking the code before including it. I assume you are checking this before you submit it?

if [ ! -f $card/data.img ] ; then
DATA_SIZE=1024;
if ( grep "data_size=" /proc/cmdline > /dev/null );
then
DATA_SIZE=`awk 'BEGIN { FS = "data_size=" } ; /data_size/ {print $2;}' /proc/cmdline | awk '{print $1;}'`;
fi;

[B]if [ [COLOR="Red"]$[/COLOR]DATA_SIZE -lt 256 ]; then DATA_SIZE=256;fi;
if [ [COLOR="Red"]$[/COLOR]DATA_SIZE -gt 2048 ]; then DATA_SIZE=2048;fi;[/B]

echo "Creating a new Data store - $DATA_SIZE";
dd if=/dev/zero of=$card/data.img bs=1048576 count=$DATA_SIZE;
[ $? -eq 0 ] || fail "Failed to allocate the storage";
mke2fs -F $card/data.img;
[ $? -eq 0 ] || fail "Failed to format the storage";
fi;

this works.

i just did a test run on the vbox using different values of DATA_SIZE=XXX

each time it creates the correct sized data.img as per the code limits / and or the value initially set by the DATA_SIZE statement.

okay so some test runs via terminal prove to pull the correct info from the startup.txt

so ... this should now be working... ill update the dl link in a few minutes.
[HD2 Android SD Development] geenyous:
SOD

I had one SOD yesterday (a real one, no reaction, waited 10mins twice before trying again, pressed buttons various times) and then after I rebooted some 15mins later the phone would reboot after I plugged it into the charger.

I haven't experienced the dropped calls though.

But I am on a custom set up, so there might be various issues that cause this, but still, never had an SOD on t10 before or on the 070711 build which I used for 21 days.
[HD2 Android SD Development] uzi2:
I'm sure the auto agps routine will be useful for SD users, but Ithis build wasn't suffering from the "GPS on off bug" and so the last line is not needed.

It was only the cLK build that had these issues and only the early cLK builds that had data issues. Perhaps these are connected in some way.

Tytung provides the source to fix the bug in his post.

http://xdaforums.com/showpost.php?p=16168508&postcount=1832
[HD2 Android SD Development] PlayStation:
Just out of curiosity why are you still on T10 when Warren's works perfectly? :confused:
[HD2 Android SD Development] geenyous:
Because I really missed BT on all the time before I discovered t10.

I made it work by creating an automation with tasker that would enable BT as soon as I go into car mode (after I press the car mode icon) and that would disable it as soon as I exited car mode. But its just not the same. With BT on all the time, I just sit in my car, put my phone in the dock and car mode starts automatically as you can set it to start when it discovers a known BT device. Since I haven't found one thing I miss on t10 so far I decided to stick with it.

This is no "do this too" post, you asked and I answered. We had the BT fix implemented and we all saw how that worked. It is apparently more than just that line of code that is different and I have heard from ppl that weren't able to connect to their BT device or had wifi issues on t10 (though I still think it was mostly because of wrong copying of files). So I think this is a good situation now, if you need low BT and your BT devices work, take t10, if you have problems with wifi or connecting to your device or don't need BT then use warren-latest.

Two warren kernels to choose from would be even better, then at least we all could post veritable and accepted "bug" reports... :D

But since only very few use t10 it might not be worth the extra work.
[HD2 Android SD Development] PlayStation:
Somebody please help me out here. I see the following system info provided by Titanium Backup:-

System Rom: 192 MB (8.17 MB free)

Internal: 1.06 GB (495 MB free)

SD Card 15.9 GB (8.58 Gb free)

So now clearly I seem to be running out of space with "System Rom". I am using WinPhone 7 and 32 GB Sd card. What is the System Rom here - Winphone 7 or Android. And why around 200 MB total in entire System rom? :confused:

Somebody please enlighten me and let me know whether there is something I can do to increase the System rom. I may add here though that everything works perfectly without any lags including the Windows phone 7 rom in nand......
[HD2 Android SD Development] kushXmaster:
I had one SOD using 727 magldr NAND...haven't had one yet with the 729 cLK release.

I wouldn't expect too much help considering that you are using a different kernel...plus it doesn't really help the rest of us who actually use a full ACA set up. Maybe there should be a thread for all the people that still use the t10 kernel, I'm sure there are a few people still...
[HD2 Android SD Development] copenhagen:
https://github.com/CyanogenMod/andr...mmit/64c835840d6f49d1d541c1e48052b1fbddb683a0

march 8th my friend.
[HD2 Android SD Development] copenhagen:
good lord. you do NOT need to change the size of the system.ext2

the more **** you put into the system.ext2 the more system ram thats gonna get eaten up when your device mounts the OS files. ANYTHING EXTRA that you need to add to a build can PEACEFULLY live in your adjustable size data.img

if it was meant to be messed with the information on how to do it would be readily available. there is absolutely NO reason WHAT SO EVER that you need to change the size.. at all.

"And why around 200 MB total in entire System rom? :confused:"

Because thats the size I allot it when I create the system.ext2... 190mb to be exact.

@ boot time.. the system sets the system.ext2 (after mounting it) to read only.

so nothing ever gets written to it... when you install something.. it gets written to the data.img -- only people that would be changing system files in / out should be messing with the system.ext2
[HD2 Android SD Development] uzi2:
I knew the SD build didn't have this problem, but it has somehow found it's way into the cLK version as the behaviour is fixed by the line in gps.conf

Could it be that there are gremlins at work with the cLK build, which have also caused the previous issues?
[HD2 Android SD Development] copenhagen:
the cleanup fix that I mentioned i added to the newest sd build... is in the new clk build... i just havnt uploaded it yet. i think is the answer to your question -- or maybe the way you were going with that is --> perhaps the clk build is different?

no. they are identical. (for the most part.. at least where this issue is concerned)
[HD2 Android SD Development] PlayStation:
Dont worry Cope. I am absolutely not changing anything. I simply did not know how that 200 Mb system rom works but now I undertand that is the system.ext2. So dont cane the student who asks a stupid question. I think I have never previously given that Titanium Backup System info attention before but I am now the wiser...... :rolleyes:
[HD2 Android SD Development] uzi2:
Yes, I am suggesting that the cLK build is different? If one doesn't need the gps.conf workaround, then neither should the other.

I realise that they are both compiled from the same source and this should not happen, but the fact that the cLK version has had issues previously which did not appear in the other builds suggests that something is different.
[HD2 Android SD Development] uzi2:
Now if that were an EU HD2 you would have no internal storage left..
[HD2 Android SD Development] copenhagen:
no they are identical. but from the timeline....

-gps libs are updated (thus beginning our gps gremlin issue)

-all 3 builds are updated

-users report that on / off bug exists

-tytung reports that 1. a commit was to be made to the frameworks base

& 2. a cleanup entry added to the gps.conf to fix the solution

-cleanup entry added to build (framework code had been updated in march)

-updated sd 080111 build released....

its understandable why the clk build is still showing the symptoms.

cause:

-updated clk build released has not happened yet.

am i on the right track?
[HD2 Android SD Development] copenhagen:
SD USERS who have updated to 080111 i attached some new root fs to the same post (in my sig) as the 080111 dl post. please update yours.

they should now correctly create the right size data.img as per the setting in your startup.txt (sorry about the release ones.. i didnt do my homework before releasing them) these new ones have been checked and double checked.

-word.

That said... 080111 CLK & Magldr (your updates will be here shortly)

Links

->click the link in my sig
[HD2 Android SD Development] uzi2:
No, because it is only cLK users who have reported the GPS issues. The SD build has always worked well with whatever gps libs were thrown at it and the cLK build has had the issue from day 1. The early builds of cLK had no mobile data. This didn't affect the other builds either.

So out of the three builds all released at the same time, it is only the cLK build that has the issues.

The "gps on off bug" should only affect builds compiled before March 8, but it is present in all of the cLK test builds.
[HD2 Android SD Development] PlayStation:
Yes mine is EU HD2. I thought that info refers to the 1024 data image ...... :confused:
[HD2 Android SD Development] uzi2:
Yeah.. sorry... now we're all confused :confused:

My internal is only 224MB as this is what's left after the system ROM has taken it's 200MB - this is true Internal as I'm using a nand build.

With SD Internal = data.img and System ROM = system.ext2 - the true internal is not used as in your case it has your WP7 stuff on it.
[HD2 Android SD Development] copenhagen:
the 1024 data.img is not related to how much internal mem your device has.

it is coincidential that your device has 1024 mb of intermal mem.

on a regular android device there is a lot more internal mem.

IN that internal mem under normal circumstances android creates a data partition

and this is where all your added in stuff gets saved... this is the data.img

however, since we dont have enough ram to facilitate an actual data partition,

we trick the system by mounting a file AS a partition.... and thus your data.img has life.

clearing it up ?

nand builds actually create a data partition... and quickly fill it up with apps and such. which is why we need to install as much (or MOVE as much as we can app wise) to the sdcard... in settings, you can change the default location to install apps to sdcard. you can also move via check box all your existing apps to the sdcard... and (playstation....) if you were to make the system.ext2 larger... you would actually decrease the size of this data partition and have even LESS room to install apps etc to.cause not only is the data partition mounted .. but also cache, and system as well. its a delicate thing juggling all this on the hd2. ;) we are getting there tho. (aca i mean.. others have been here for a while lol)
[HD2 Android SD Development] linstit:
thanx for all work but i still have vpn problem :( using 072911
[HD2 Android SD Development] PlayStation:
Cope I changed the LCD density to 240 in the Startup Txt but even after replacing the new Rootfs the screen is still the default 160. What do I need to do to get 240 instead of 160?