yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Anthonayy:
Derek, the Desire Kingdom build has released v3 with camera and weather fixes. Have you implemented that to this upcoming build? Or will that come in a few days?

It looks like dungphp's ahead in the Kingdom port, he's got weather and camera fixed up and is modding his build off of, guess what? The one you are, HTC Kingdom from the Desire dev forums. :)
[HD2 Android NAND Development] casemandan:
well dungphp's rom has the weather somewhat fixed, but it wont let me install titanium and restarts so i'm going back to this one. Its too stable not to lol. And who cares about the weather.

Hopefully once derek updates to the same build as dung, his will let me restore my apps thru titanium.
[HD2 Android NAND Development] Derek0228:
Yeah, I know, it's kinda weird that he chose to use the same base as me, well of course, it's the best base, but it wasn't, innovative or whatever? Anyways, no hard feelings with him, he's a great dev, much more experienced than me. But my port will be different than his. You'll see. As for the fixes, I have implemented them , I'm testing the rom right now. Plus, my Rom now fits on both EU and TMoUS NAND. ;D

Edit: Camera works. I'm trying to see why WIFI errors out on me. I always have some kind of problem. :/

/offtopic That was a great party! :D
[HD2 Android NAND Development] Anthonayy:
nice, looking forward to your build. ALOT.
[HD2 Android NAND Development] Anthonayy:
I've tried out dungphp's build. And it should be nearly identical as yours (considering they were both ports).

(On dungphp's port)

But when I try to download from the market, the phone automically reboots before the app is installed, thus preventing installation of any app whatsoever. But that was after gfx was applied.

(On your port)

I was downloading apps before the gfx-fix without a problem. But I have yet to dl after applying it, as it really gave me some issues.

Is the app download an issue with yours perhaps?

EDIT: According to other testers, it's not. GOGOGO! How did you fix that issue?
[HD2 Android NAND Development] Derek0228:
On the old version, not, on this one, I haven't checked. Still in testing stages. Trying to make it as perfect as possible.
[HD2 Android NAND Development] Anthonayy:
Also, dung's port doesn't have fc issues at startup.

Were you able to fix those fc issues in what you're currently testing? (HTC Locations)
[HD2 Android NAND Development] Derek0228:
Yes, in fact I removed HTC Locations. I personally don't use them, so i deleted them.

No more questions til the Rom arrives please :)

And no ETA yet.
[HD2 Android NAND Development] daman215:
just one more question Derek can you put in the transparent rosie if its not to much
[G Tablet Q&A, Help & Troubleshooting] jlooky:
Hey gang-

I've learned alot in 48 hrs. I rooted my phone and added vegaN gingerbread.

I have a problem with my clock not being correct after each reboot. Could anyone help me out.

Also was curious what music player likes intunes for ipod that you guys use to store and create playlists in.

And what movie player works best for avi movies I download.

THANKS, Love the fact I have a tablet that I paid $225 for and it is getting massive use! oh, oh, oh how do you check your speed like I see everyone posting. 1900 etc.
[G1 Q&A, Help & Troubleshooting] Dheano:
I used to have a 4GB class 6 Micro SD Card. One day my phone crashed and I had to remove the battery in order to reboot. When I reboot, the SD Card is damaged and I had SD-Ext with alot of apps on.

I then got a 2GB class 6 Micro SD Card. Today the same thing happened.

I'm using FroyoByLaszlo 5.2 and I want to know if there's a solution to this problem (as in, stopping the phone from breaking my SD Cards - they must be reformatted before they will work now).
[G1 Q&A, Help & Troubleshooting] z0k:
i am not sure if thats a genuine warning.i get it all the time every time i reboot,i just think thats cos i dont have an ext4 partition.all i do is remount the card
[G1 Q&A, Help & Troubleshooting] Dheano:
I have Ext4 partition though. And if I attempt to launch an app (they usually have the default app green logo) it says 'Could not launch the requested activity'...
[G1 Q&A, Help & Troubleshooting] louisJJ:
same problem here, with froyobylaszlo, did you find a solution? thanks
[G1 Q&A, Help & Troubleshooting] BeenAndroidized:
Reformat/partition your SD Card. ;)
[G1 Q&A, Help & Troubleshooting] louisJJ:
did that already, and then after a while the error comes back
[G1 Q&A, Help & Troubleshooting] ldrifta:
it's the rom... you need to reflash it.. i had an issue like that.. dropped my phone and sd card fell out so no matter what i did it wouldn't fix, had to reflash rom..
[G1 Q&A, Help & Troubleshooting] BeenAndroidized:
yep! That is what needs to be done after that.
[G1 Q&A, Help & Troubleshooting] louisJJ:
ok... thank you very much for your help.
[G1 Q&A, Help & Troubleshooting] GeneralG2:
I was wondering if the reflashing worked for more people? I reflashed like 3 times now and it still pops up.

Before when I switched my apps to the SD card, they died there and didn't work anymore. Otherwise it was fine (except with that annoying notification that would never leave).

Now I have formatted everything like 4 times and still no luck. This all happened after I got froyo by laszlo.
[G1 Q&A, Help & Troubleshooting] ldrifta:
did you un partition it?

you need to un partition via recovery (set swap and ext values to: 0mb)

then remove from device, insert to pc and re format to FAT32

now do wipe of everything(flash superwipe) re partition your sd card than re flash rom.
[EVO 4G General] plmiller0905:
I was thinking about getting the EVO 3D but I think I'm gonna wait..especially after reading this:

http://www.engadget.com/2011/05/13/htc-sensation-looks-to-have-signed-bootloader-custom-roms-look/

If the HTC Sensation appears to have a locked bootloader, I'm sure the EVO 3D will as well. But hopefully the Devs can unlock it if it is locked down. I bought the Atrix and it's still locked down. That's why I sold it....

here's a better link: http://www.androidpolice.com/2011/0...d-bootloader-custom-rom-support-is-in-danger/

The engadget article is kinda vague.
[EVO 4G General] teh roxxorz:
I think it most likely will have a locked bootloader. It can be unlocked, but going to take a lot more time.
[EVO 4G General] CheesyNutz:
http://xdaforums.com/showthread.php?t=1077184
[EVO 4G General] craigbailey1986:
Isn't it true that only phones that are encrypted so far are Verizon's phones? When a sprint one comes out encrypted then we should be scared.

Right now chalk it up to big red demanding it be done...
[EVO 4G General] cesarcerros31:
Correct me if I'm wrong but didn't the evo have some type of bootloader and troops some time to unlock it

sent from my HTC evolution running a freshly baked gingerbread with the 4gs in it
[EVO 4G General] plmiller0905:
I don't know...

But I'm hoping this thing isn't locked down like the Atrix. I think it'll be unlocked over time...
[EVO 4G General] mattykinsx:
Don't be so logical, it breaks forum rules. ;)

But, the Sensation is on T-Mobile. [They've gone to the dark side lately anyway]
[EVO 4G General] swaze:
Yes, thats exactly how mostly all phones come, except google phones. THEY ALL ARE LOCKED, and most of the time root is achieved before the phone is released.
[EVO 4G General] mattykinsx:
Well yeah but we have a word usage issue here.

When people are saying "locked" they are meaning "signed."

Such as the Droids.
[EVO 4G General] adeyo:
it was locked but it was rooted before it even came to market...a few of the awesome dev's around here got it from the google conference and had it rooted within a couple days well before sprint stores etc got them.
[EVO 4G General] sgt. slaughter:
But full NAND unlock didn't come until the ENG bootloader surfaced right? or were their phones given at the conf. already with the ENG bootloader?
[Hero CDMA General] gangaskan:
i'd like to say to everyone goodbye, as i just received my Nexus :D

this phone was and still is great to me, and i congratulate everyone on their hard efforts on making this phone what it is today. :)
[Hero CDMA General] oohaylima:
Awesome. Send me your phone if you don't have a home for it. I recycle Hero's to less fortunate people who can't upgrade due to financial reasons.
[Hero CDMA General] gangaskan:
i wish i could :( corporate phone.
[Hero CDMA General] oohaylima:
Lol I feel ya. Hopefully they.recycle it.
[Hero CDMA General] Bierce22:
"we had a great ride" that sounds something dewey cox would say lol.
[Legend General] abhishek_turbo911:
The ringtone volume of htc legend running on 2.2 automatically lowers when i travel to some 'other' place. Like i was at college (which is at a different district) and ive come home for holidays. This is not a once issue , this has been happening everytime i visit home , whereas at coll , the ringtone volume is fine ! :confused::confused:
[Legend General] thugzie:
I have the same issue (which was fixed by 2.2) when I flashed my legend with blaYo rom.

If you have gsm - change to WCDMA - if you have WCDMA - change to GSM and se if it helps.
[Legend General] abhishek_turbo911:
No :( does not work :( the moment i clicl decline for one moment , just ONE moment the ringtone is full volume and by then it cuts :( :confused:
[Legend General] cyRq:
Your so called problem is the proximity sensor. Either its screwed (less possible) or something wrong with your ROM (more possible). Unfortunately you've didn't mention what kind of ROM you're using.
[Legend General] abhishek_turbo911:
Its Superuser,Keep It Simple ROM @ 2.2
[Legend General] abhishek_turbo911:
Some help guys !?
[Legend General] bonesy:
There is a feature to lower call volume when the phone is moved,maybe thats the problem?
[Legend General] abhishek_turbo911:
Come on. I wouldn't take the trouble of posting this topic if it was just a noob-ish issue. Thats not the case.
[Legend General] Arab330:
Problem or in the sensor, unless of course you have not tried to change the firmware
[Galaxy Tab Q&A, Help & Troubleshooting] elierfr2:
Hi,

I want to upgrade overcome V1.3.0 to V1.6.4

Acording to this post : http://xdaforums.com/showthread.php?t=932082

I've to upgrade to V1.4.0 before and after to V1.4.7 etc...

But i cant find any Updater for the v1.3.0

Is there anyone who can help me ?

Thanks ;-)
[Galaxy Tab Q&A, Help & Troubleshooting] TheATHEiST:
You cant.

You can only upgrade between revisions like 1.3.1 > 1.3.x or 1.4.1 to 1.4.x

To upgrade your device you should do a titanium backup of all your user apps/data, Flash your device to Android 2.3 (READ THE GUIDE!!!) and then restore your apps/data back.

Also remember to backup your data from internal sd.
[Galaxy Tab Q&A, Help & Troubleshooting] Clark K:
Why would you stop at v 1.6.4.

You should go directly to 2.0.b2. This rom is amazing.

Just go on Overcome thread, download and READ the guide.

Then enjoy!!!
[Xperia Arc General] Milne_Rangers:
I have the midnight blue and was thinking of buying a silver back anyone else got this to let me know how it looks.

Cheeers
[Xperia Arc General] rein_hiryu:
Well I have Misty Silver and I want the Midnight Blue's back cover, but the problem is I live in Indonesia :p
[Xperia Arc General] hieudd:
ebay sells about $20 for original back cover
[myTouch 4G Q&A, Help & Troubleshooting] acsi007:
Edit: whoops, I meant to post this in Q&A - feel free to move it there if more appropriate.

So the surge in cant mount cache E errors peaked a last week it seems. The problems and solutions were all over the map. Where it came from, what caused it, how people recovered, what they were doing when it all started. Even in the dev forums, it's still a partial unknown. (Good ideas as to how to fix/avoid, but no nailed-down cause other than circumstantial evidence)

So the bottom line from what my still-beginner's eye tells me is that clockwork recovery is borked, it's linked with using rom manager, and previously having used the gfree rooting method, an much of this happens after flashing a new rom (and possibly not wiping every cache?).

In the main gfree thread

http://xdaforums.com/showthread.php?t=858996

it does say that recovery might get borked (and you need to pull the battery to reboot) but you can fix it by reinstalling recovery through clockwork. Well, I never had a problem needing to pull the battery. Well, wait a minute. I did.

What I did:

visionary11 to temp

abd gfree files over

terminal: etc gfree -f, worked fine.

rebooted and say s=off at hboot screen

knew i wasnt rooted yet until i did visionary again, so i did.

black screen for too long, didnt come back as rooted, hung on black screen

Rebooted by taking battery out, did vis11 again and then it returned to the vis screen, and i was su ok in terminal.

now- that time i had to pull that battery, and having previously used gfree - do i have a borked cwm and i dont even know it?

i can boot into hboot then pick recovery, i even made nandroid. but the proof is when you do a restore or flash a new rom, im almost afraid to do a nandroid restore.... Ive just flashed a single time-- RG1.6 (working great)

now, are we supposed to ALWAYS, as a prevantative measure, reflash recovery 3.0.2.4 even if we havent had a problem?

Have those who received this error at one point or another-- have they ALL reflashed 3024 after using gfree to root?

my point is, that warning in the gfree root thread (second red text line) means more to me now that I know more of the moving parts. Is avoiding this soft/hard brick as easy as making it mandatory to reinstall/reflash a fresh CWM3024 after rooting or after every flash of a rom?

I know about pd15immg and part7 working for many people to restore from the error. i also know about the earlier ext3 CWM 2.x recovery version being needed to reflash pd15img with less problems than 3024. but those solutions, while a good bet, are still not shown to be slam dunk.

im just trying to come up with some steps that will almost guarantee avoidance of the cache error loop to begin with...
[myTouch 4G Q&A, Help & Troubleshooting] dacquesta1:
well for starters, i think that anyone who doesn't do a nandroid backup and then a full wipe before flashing a rom is asking for trouble. I run clockwork 3.0.2.4 and have had ZERO issues. here is what i do:

wipe...

/dalvik-cache

/cache

/data

/system

then...

factory data reset...no issues and i flash too often lol.
[myTouch 4G Q&A, Help & Troubleshooting] h22aboi:
According to trueblue_drew he says to do this as far as wiping your stuff...

This is how you should wipe:

Main Recovery Menu:

1. Wipe data / factory reset

2. wipe cache partition

Advanced Recovery Menu:

3. Wipe Dalvik Cache

Mounts and Storage Recovery Menu:

4. Format System
[myTouch 4G Q&A, Help & Troubleshooting] kimbernator:
It only happens to gfree users i think. If they reflash recovery after using gfree the issue is basically avoided.
[myTouch 4G Q&A, Help & Troubleshooting] acsi007:
1. i'm not super focused on the wiping part, so i dont want to make this thread into a wiping thread, although it is important. im trying to wrap my head around the entire gamut of causes and get some main ansers that are solid

2. "reflash recovery after using gfree the issue is basically avoided.". I'd like to get some data on this, and I'm hoping that people who DID reflash CWM after gfree ( reflashed it a second time after wiping everything and flashing a rom-- if they STILL got the error. I'm betting that only a small minority flashed CWM recovery TWICE. I'm hoping to find out if any of them STILL got the error ( i'm hoping not). I"m also wondering how many didnt reflash CWM (because there was nothing acting up to cause them to do so) but they still may have a latent problem there, waiting to creep up after some incomplete data wipe, or some SD card anomaly, and then surface...
[myTouch 4G Q&A, Help & Troubleshooting] cmdmilitia13:
I had the error once & had to replace the phone.. I made the mistake by usin recovery 3.0.0.5(this was before 3.0.0.6 & 3.0 2.4 came out)to go bck to a froyo rom but only because cm7 rc2 wasnt allowin me to do anythin with the phone(all forcecloses) so booted recovery wipe everythin & flashed froyo rom & there goes my phone.Fried.lol my mistake for not READING before flashin.. Anyway ive been readin lately that people have been tryin to restore apps & data with titanium,big no-no,with restorin data frm other roms...

Mytouch 4g-White

Root Method-gfree

Permrooted s=off

CWR-3.0.2.4

Rom-Royalginger v2.0

Kernel-ckisgen-smartass-v1.1
[myTouch 4G Q&A, Help & Troubleshooting] xdviper:
I pulled that same mistake also when CM7 alpha previews first came out, I had the 3.0.0.5 recovery, installed the preview to test out,and then I restored a nandroid backup of my Iced Glacier rom and instead of being stuck at the mytouch screen or not booting up, I just got bootloops until I flashed the froyo capable version of Clockwork through adb. Mind you, that's when I had used the first method of gaining S-OFF. I haven't been using gfree method until I got this, my third replacement and first method wouldn't stick so I ended up using gfree.

I'm soo leaning over the gfree method being the culprit and ****ing up the paritions.

I have the same thread over in the general section and user "_ice_" said that gfree also alters you dev partition block which can also cause problems.

I'm also very scared to flash roms, I've tried flashing the new virtous rom the other day, my heart just dropped after it got stuck at the mytouch screen for 5 minutes, i wiped everything, and it still wouldn't boot, I did a nandroid it wouldn't pass the mytouch, obviously I could still enter the recovery so I knew I was good and had no errors about not being able to mount. I just flashed CM7 all over again after wiping system, data, cache, dalvik etc and then advanced restored data and it booted back up.
[myTouch 4G Q&A, Help & Troubleshooting] kimbernator:
Here is what i would say.

To avoid these issues, do these things:

1. If you used gfree, reflash cwm recovery at least once. Preferably twice to make it stick.

2. If you used the visionary method with root.sh, don't worry about it as much. Reflashing cwm recovery isn't required, but it can't hurt.

Because of this I would recommend the root.sh method unless you want carrier unlock.
[myTouch 4G Q&A, Help & Troubleshooting] xdviper:
What if the root.sh method doesn't stick? Many have said if it doesn't work twice, then do a factory reset.

I'll be unrooting and trying the root.sh method again, and I'll update this thread as well as mine with how I did it and a step by step tutorial. Even though we have one, I feel like its vague and doesn't give much advice.

And also, this has been happening with G2 users as well, G2 users are looking into it and seems as there is a batch of chips that are bad and get corrupted after a while. That's just a possibility as what about the users who aren't rooted and or rooted with root.sh.

And also, those users were rooted via gfree. I'm going to read the logs from the irc channel and post a summary on my thread later on with my findings.
[myTouch 4G Q&A, Help & Troubleshooting] cmdmilitia13:
What do u mean by reflashin cwr? Sorry for the dumb question..

Mytouch 4g-White

Root Method-gfree

Permrooted s=off

CWR-3.0.2.4

Rom-Royalginger v2.0

Kernel-ckisgen-smartass-v1.1
[myTouch 4G Q&A, Help & Troubleshooting] xdviper:
Rom manager, and the top will say current recovery, click on it, confirm mytouch 4g, and then it'll flash. But the thing is, we still haven't been able to rule out and say that the recovery is causing this problem.
[myTouch 4G Q&A, Help & Troubleshooting] cmdmilitia13:
I thought that was what that meant lol.. I been on 3.0.2.4 since day 1 it came out & havent ran into those nasty forcecloses then the dreaded error YET.. Before I flash a rom now I always reflash recovery,then power off phone & go into recovery manually,then I wipe by 1st wiping data then cache then dalvik then format system(i do this 2 or 3 times dependin what rom im gonna flash)then I flash the rom..Another thing I never do is restore apps,i rather just dwnload them again..I dnt do nandroid restores cause I dnt trust it but always do bckups(would only nandroid restore if ABSOLUTELY have too) With my other mytouch that I screwed up,i wasnt careful enough now I make sure I have an empty phone before I flash

Mytouch 4g-White

Root Method-gfree

Permrooted s=off

CWR-3.0.2.4

Rom-Royalginger v2.0

Kernel-ckisgen-smartass-v1.1
[myTouch 4G Q&A, Help & Troubleshooting] acsi007:
Funny, right after I posted this, bam!, like 3-4 threads appeared in various places talking about variants of this. This is what I was trying to improve upon, but oh well, we'll jump around from thread to thread I guess...
[Desire HD Q&A, Help & Troubleshooting] baco200:
Hi, is it necessary or recomanded to do a full wipe before restore a rom with clockworkMod??
[Desire HD Q&A, Help & Troubleshooting] Mr_JMM:
Yes, full factory wipe and cache and don't forget the Dalvik-Cache in advanced settings. D-C wipe might be overkill but once in a while I see Market issues and wiping Dalvik-Cache should help prevent them.
[Desire HD Q&A, Help & Troubleshooting] medmed12:
Necessary, because if you do the restore of the nandroid backup of Coredroid on MIUI ( exemple ) you going to have some issues
[Desire HD Q&A, Help & Troubleshooting] baco200:
thanks, loud and clear:)
[Thunderbolt Android Development] mike919:
If you took the leak you may notice that if you check for software updates, the official OTA will still be waiting there for you to download and update.

To get rid of this, download my build prop and copy it to /system via root explorer (or how ever you want to do it) and reboot.

Check for updates again, and it should say you are up to date. Enjoy.

http://db.tt/94jWrtq

**note, i didn't plan on releasing this but more people have noticed they are still being notified for update... my build prop increased wifi scan interval to 120 and Dalvik heap was changed to 48m from 24m

EDIT!!!!

I just chatted with Jcase, and before copying this over, check your software update in menu, settings to see if it still prompts you after installing the leak. if it doesn't, you do not need this file as you have the leak with the clean build.prop. If it does still ask you to update, you can just copy it like the directions say. The ONLY thing changed is the build and project numbers. Nothing else. (other then the wifi and dalvik mentioned)
[Thunderbolt Android Development] jlouang:
Thanks
[Thunderbolt Android Development] allchannels99:
Link is down
[Nook Color General] akarol:
Guys, I am selling my beloved NC + Case on eBay and I am wondering if I should unroot prior to doing so? I see that a lot of NCs on there come rooted and seem to add a bit more value to the final price. However, I'm reluctant to getting a negative feedback due to instability, etc. What do you guys think?
[Nook Color General] zombieflanders:
How much of a premium is it getting? If it's just a couple dollars, I say unroot it to stock 1.2 just to be safe. That way if there are any problems (a) you can't really be held responsible by the buyer, and (b) any problems can be fixed by B&N if necessary.
[Nook Color General] SoCalTiger:
Put a note in the item description saying that by default you will ship it with the stock 1.2 ROM but you will flash it to whatever ROM the buyer prefers but only if they email you within 24 hours of the sale. Be sure to put your email in the item description for them.

I'd also put a disclaimer about how if they request you to flash it you can't guarantee stability and B&N would not accept it for warranty claims in that state.
[Nook Color General] akarol:
That's a great idea! Thanks!

While in the topic, I've noticed that the volume + button takes a lot of pressure to be recognized by the device. Some others seem to have similar issues so I never bothered to do anything about it. I'm concerned that the buyer might notice and give me a negative feedback because of it. Should I mention this issue or no? I was going to be sending it to B&N to get it repaired, but I figured it wasn't that big a deal and the buyer can do it him/herself.